1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
5 Changes in version 0.3.2.10 - 2018-03-03
6 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
7 backports a number of bugfixes, including important fixes for security
10 It includes an important security fix for a remote crash attack
11 against directory authorities, tracked as TROVE-2018-001.
13 Additionally, it backports a fix for a bug whose severity we have
14 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
15 triggered in order to crash relays with a use-after-free pattern. As
16 such, we are now tracking that bug as TROVE-2018-002 and
17 CVE-2018-0491, and backporting it to earlier releases. This bug
18 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
21 This release also backports our new system for improved resistance to
22 denial-of-service attacks against relays.
24 This release also fixes several minor bugs and annoyances from
27 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
28 today, for the fix to TROVE-2018-002. Directory authorities should
29 also upgrade. (Relays on earlier versions might want to update too for
32 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
33 - Fix a protocol-list handling bug that could be used to remotely crash
34 directory authorities with a null-pointer exception. Fixes bug 25074;
35 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
38 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
39 - Avoid adding the same channel twice in the KIST scheduler pending
40 list, which could lead to remote denial-of-service use-after-free
41 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
43 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
44 - Give relays some defenses against the recent network overload. We
45 start with three defenses (default parameters in parentheses).
46 First: if a single client address makes too many concurrent
47 connections (>100), hang up on further connections. Second: if a
48 single client address makes circuits too quickly (more than 3 per
49 second, with an allowed burst of 90) while also having too many
50 connections open (3), refuse new create cells for the next while
51 (1-2 hours). Third: if a client asks to establish a rendezvous
52 point to you directly, ignore the request. These defenses can be
53 manually controlled by new torrc options, but relays will also
54 take guidance from consensus parameters, so there's no need to
55 configure anything manually. Implements ticket 24902.
57 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
58 - Fix an "off by 2" error in counting rendezvous failures on the
59 onion service side. While we thought we would stop the rendezvous
60 attempt after one failed circuit, we were actually making three
61 circuit attempts before giving up. Now switch to a default of 2,
62 and allow the consensus parameter "hs_service_max_rdv_failures" to
63 override. Fixes bug 24895; bugfix on 0.0.6.
64 - New-style (v3) onion services now obey the "max rendezvous circuit
65 attempts" logic. Previously they would make as many rendezvous
66 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
67 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
69 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
70 - Add Link protocol version 5 to the supported protocols list. Fixes
71 bug 25070; bugfix on 0.3.1.1-alpha.
73 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
74 - Fix a set of false positives where relays would consider
75 connections to other relays as being client-only connections (and
76 thus e.g. deserving different link padding schemes) if those
77 relays fell out of the consensus briefly. Now we look only at the
78 initial handshake and whether the connection authenticated as a
79 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
81 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
82 - The scheduler subsystem was failing to promptly notice changes in
83 consensus parameters, making it harder to switch schedulers
84 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
86 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
87 - Make our OOM handler aware of the geoip client history cache so it
88 doesn't fill up the memory. This check is important for IPv6 and
89 our DoS mitigation subsystem. Closes ticket 25122.
91 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
92 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
93 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
94 since they neither disabled TLS 1.3 nor enabled any of the
95 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
98 o Minor features (geoip):
99 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
102 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
103 - When logging a failure to check a hidden service's certificate,
104 also log what the problem with the certificate was. Diagnostic
107 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
108 - Use the actual observed address of an incoming relay connection,
109 not the canonical address of the relay from its descriptor, when
110 making decisions about how to handle the incoming connection.
111 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
113 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
114 - Fix a possible crash on malformed consensus. If a consensus had
115 contained an unparseable protocol line, it could have made clients
116 and relays crash with a null-pointer exception. To exploit this
117 issue, however, an attacker would need to be able to subvert the
118 directory authority system. Fixes bug 25251; bugfix on
119 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
121 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
122 - Directory authorities, when refusing a descriptor from a rejected
123 relay, now explicitly tell the relay (in its logs) to set a valid
124 ContactInfo address and contact the bad-relays@ mailing list.
125 Fixes bug 25170; bugfix on 0.2.9.1.
127 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
128 - When building with Rust on OSX, link against libresolv, to work
129 around the issue at https://github.com/rust-lang/rust/issues/46797.
130 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
132 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
133 - Remove a BUG() statement when a client fetches an onion descriptor
134 that has a lower revision counter than the one in its cache. This
135 can happen in normal circumstances due to HSDir desync. Fixes bug
136 24976; bugfix on 0.3.2.1-alpha.
138 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
139 - Don't treat inability to store a cached consensus object as a bug:
140 it can happen normally when we are out of disk space. Fixes bug
141 24859; bugfix on 0.3.1.1-alpha.
143 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
144 - Improve the performance of our consensus-diff application code
145 when Tor is built with the --enable-fragile-hardening option set.
146 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
148 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
149 - Don't exit the Tor process if setrlimit() fails to change the file
150 limit (which can happen sometimes on some versions of OSX). Fixes
151 bug 21074; bugfix on 0.0.9pre5.
153 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
154 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
156 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
157 bugfix on 0.2.9.4-alpha.
159 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
160 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
161 25005; bugfix on 0.3.2.7-rc.
163 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
164 - Look at the "HSRend" protocol version, not the "HSDir" protocol
165 version, when deciding whether a consensus entry can support the
166 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
167 bugfix on 0.3.2.1-alpha.
169 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
170 - Update the "rust dependencies" submodule to be a project-level
171 repository, rather than a user repository. Closes ticket 25323.
173 o Documentation (backport from 0.3.3.1-alpha)
174 - Document that operators who run more than one relay or bridge are
175 expected to set MyFamily and ContactInfo correctly. Closes
179 Changes in version 0.3.1.10 - 2018-03-03
180 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
183 It includes an important security fix for a remote crash attack
184 against directory authorities, tracked as TROVE-2018-001.
186 This release also backports our new system for improved resistance to
187 denial-of-service attacks against relays.
189 This release also fixes several minor bugs and annoyances from
192 All directory authorities should upgrade to one of the versions
193 released today. Relays running 0.3.1.x may wish to update to one of
194 the versions released today, for the DoS mitigations.
196 Please note: according to our release calendar, Tor 0.3.1 will no
197 longer be supported after 1 July 2018. If you will be running Tor
198 after that date, you should make sure to plan to upgrade to the latest
199 stable version, or downgrade to 0.2.9 (which will receive long-term
202 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
203 - Fix a protocol-list handling bug that could be used to remotely crash
204 directory authorities with a null-pointer exception. Fixes bug 25074;
205 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
208 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
209 - Give relays some defenses against the recent network overload. We
210 start with three defenses (default parameters in parentheses).
211 First: if a single client address makes too many concurrent
212 connections (>100), hang up on further connections. Second: if a
213 single client address makes circuits too quickly (more than 3 per
214 second, with an allowed burst of 90) while also having too many
215 connections open (3), refuse new create cells for the next while
216 (1-2 hours). Third: if a client asks to establish a rendezvous
217 point to you directly, ignore the request. These defenses can be
218 manually controlled by new torrc options, but relays will also
219 take guidance from consensus parameters, so there's no need to
220 configure anything manually. Implements ticket 24902.
222 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
223 - Update the sandbox rules so that they should now work correctly
224 with Glibc 2.26. Closes ticket 24315.
226 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
227 - Fix an "off by 2" error in counting rendezvous failures on the
228 onion service side. While we thought we would stop the rendezvous
229 attempt after one failed circuit, we were actually making three
230 circuit attempts before giving up. Now switch to a default of 2,
231 and allow the consensus parameter "hs_service_max_rdv_failures" to
232 override. Fixes bug 24895; bugfix on 0.0.6.
234 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
235 - Add Link protocol version 5 to the supported protocols list. Fixes
236 bug 25070; bugfix on 0.3.1.1-alpha.
238 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
239 - Fix a set of false positives where relays would consider
240 connections to other relays as being client-only connections (and
241 thus e.g. deserving different link padding schemes) if those
242 relays fell out of the consensus briefly. Now we look only at the
243 initial handshake and whether the connection authenticated as a
244 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
246 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
247 - Make our OOM handler aware of the geoip client history cache so it
248 doesn't fill up the memory. This check is important for IPv6 and
249 our DoS mitigation subsystem. Closes ticket 25122.
251 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
252 - Change relay bandwidth reporting stats interval from 4 hours to 24
253 hours in order to reduce the efficiency of guard discovery
254 attacks. Fixes ticket 23856.
256 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
257 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
258 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
259 since they neither disabled TLS 1.3 nor enabled any of the
260 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
263 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
264 - The fallback directory list has been re-generated based on the
265 current status of the network. Tor uses fallback directories to
266 bootstrap when it doesn't yet have up-to-date directory
267 information. Closes ticket 24801.
268 - Make the default DirAuthorityFallbackRate 0.1, so that clients
269 prefer to bootstrap from fallback directory mirrors. This is a
270 follow-up to 24679, which removed weights from the default
271 fallbacks. Implements ticket 24681.
273 o Minor features (geoip):
274 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
277 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
278 - Use the actual observed address of an incoming relay connection,
279 not the canonical address of the relay from its descriptor, when
280 making decisions about how to handle the incoming connection.
281 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
283 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
284 - Directory authorities, when refusing a descriptor from a rejected
285 relay, now explicitly tell the relay (in its logs) to set a valid
286 ContactInfo address and contact the bad-relays@ mailing list.
287 Fixes bug 25170; bugfix on 0.2.9.1.
289 o Minor bugfixes (address selection, backport from 0.3.2.9):
290 - When the fascist_firewall_choose_address_ functions don't find a
291 reachable address, set the returned address to the null address
292 and port. This is a precautionary measure, because some callers do
293 not check the return value. Fixes bug 24736; bugfix
296 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
297 - Fetch descriptors aggressively whenever we lack enough to build
298 circuits, regardless of how many descriptors we are missing.
299 Previously, we would delay launching the fetch when we had fewer
300 than 15 missing descriptors, even if some of those descriptors
301 were blocking circuits from building. Fixes bug 23985; bugfix on
302 0.1.1.11-alpha. The effects of this bug became worse in
303 0.3.0.3-alpha, when we began treating missing descriptors from our
304 primary guards as a reason to delay circuits.
305 - Don't try fetching microdescriptors from relays that have failed
306 to deliver them in the past. Fixes bug 23817; bugfix
309 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
310 - Fix a signed/unsigned comparison warning introduced by our fix to
311 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
313 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
314 - Avoid a crash when attempting to use the seccomp2 sandbox together
315 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
318 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
319 - Fix a possible crash on malformed consensus. If a consensus had
320 contained an unparseable protocol line, it could have made clients
321 and relays crash with a null-pointer exception. To exploit this
322 issue, however, an attacker would need to be able to subvert the
323 directory authority system. Fixes bug 25251; bugfix on
324 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
326 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
327 - Recover better from empty or corrupt files in the consensus cache
328 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
329 - When a consensus diff calculation is only partially successful,
330 only record the successful parts as having succeeded. Partial
331 success can happen if (for example) one compression method fails
332 but the others succeed. Previously we misrecorded all the
333 calculations as having succeeded, which would later cause a
334 nonfatal assertion failure. Fixes bug 24086; bugfix
337 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
338 - Tor now updates its guard state when it reads a consensus
339 regardless of whether it's missing descriptors. That makes tor use
340 its primary guards to fetch descriptors in some edge cases where
341 it would previously have used fallback directories. Fixes bug
342 23862; bugfix on 0.3.0.1-alpha.
344 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
345 - Don't treat inability to store a cached consensus object as a bug:
346 it can happen normally when we are out of disk space. Fixes bug
347 24859; bugfix on 0.3.1.1-alpha.
349 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
350 - When queuing DESTROY cells on a channel, only queue the circuit-id
351 and reason fields: not the entire 514-byte cell. This fix should
352 help mitigate any bugs or attacks that fill up these queues, and
353 free more RAM for other uses. Fixes bug 24666; bugfix
356 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
357 - When closing a connection via close_connection_immediately(), we
358 mark it as "not blocked on bandwidth", to prevent later calls from
359 trying to unblock it, and give it permission to read. This fixes a
360 backtrace warning that can happen on relays under various
361 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
363 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
364 - When selecting relays by bandwidth, avoid a rounding error that
365 could sometimes cause load to be imbalanced incorrectly.
366 Previously, we would always round upwards; now, we round towards
367 the nearest integer. This had the biggest effect when a relay's
368 weight adjustments should have given it weight 0, but it got
369 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
370 - When calculating the fraction of nodes that have descriptors, and
371 all nodes in the network have zero bandwidths, count the number of
372 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
373 - Actually log the total bandwidth in compute_weighted_bandwidths().
374 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
376 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
377 - Improve the performance of our consensus-diff application code
378 when Tor is built with the --enable-fragile-hardening option set.
379 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
381 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
382 - Don't exit the Tor process if setrlimit() fails to change the file
383 limit (which can happen sometimes on some versions of OSX). Fixes
384 bug 21074; bugfix on 0.0.9pre5.
386 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
387 - Fix a bug in the bit-counting parts of our timing-wheel code on
388 MSVC. (Note that MSVC is still not a supported build platform, due
389 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
392 o Minor bugfixes (relay, partial backport):
393 - Make the internal channel_is_client() function look at what sort
394 of connection handshake the other side used, rather than whether
395 the other side ever sent a create_fast cell to us. Backports part
396 of the fixes from bugs 22805 and 24898.
398 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
399 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
401 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
402 bugfix on 0.2.9.4-alpha.
404 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
405 - Update the "rust dependencies" submodule to be a project-level
406 repository, rather than a user repository. Closes ticket 25323.
408 Changes in version 0.2.9.15 - 2018-03-03
409 Tor 0.2.9.15 backports important security and stability bugfixes from
412 It includes an important security fix for a remote crash attack
413 against directory authorities, tracked as TROVE-2018-001.
415 This release also backports our new system for improved resistance to
416 denial-of-service attacks against relays.
418 This release also fixes several minor bugs and annoyances from
421 All directory authorities should upgrade to one of the versions
422 released today. Relays running 0.2.9.x may wish to update to one of
423 the versions released today, for the DoS mitigations.
425 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
426 - Fix a protocol-list handling bug that could be used to remotely crash
427 directory authorities with a null-pointer exception. Fixes bug 25074;
428 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
431 o Major features (denial-of-service mitigation):
432 - Give relays some defenses against the recent network overload. We
433 start with three defenses (default parameters in parentheses).
434 First: if a single client address makes too many concurrent
435 connections (>100), hang up on further connections. Second: if a
436 single client address makes circuits too quickly (more than 3 per
437 second, with an allowed burst of 90) while also having too many
438 connections open (3), refuse new create cells for the next while
439 (1-2 hours). Third: if a client asks to establish a rendezvous
440 point to you directly, ignore the request. These defenses can be
441 manually controlled by new torrc options, but relays will also
442 take guidance from consensus parameters, so there's no need to
443 configure anything manually. Implements ticket 24902.
445 o Major bugfixes (bootstrapping):
446 - Fetch descriptors aggressively whenever we lack enough to build
447 circuits, regardless of how many descriptors we are missing.
448 Previously, we would delay launching the fetch when we had fewer
449 than 15 missing descriptors, even if some of those descriptors
450 were blocking circuits from building. Fixes bug 23985; bugfix on
451 0.1.1.11-alpha. The effects of this bug became worse in
452 0.3.0.3-alpha, when we began treating missing descriptors from our
453 primary guards as a reason to delay circuits.
455 o Major bugfixes (onion services, retry behavior):
456 - Fix an "off by 2" error in counting rendezvous failures on the
457 onion service side. While we thought we would stop the rendezvous
458 attempt after one failed circuit, we were actually making three
459 circuit attempts before giving up. Now switch to a default of 2,
460 and allow the consensus parameter "hs_service_max_rdv_failures" to
461 override. Fixes bug 24895; bugfix on 0.0.6.
463 o Minor feature (relay statistics):
464 - Change relay bandwidth reporting stats interval from 4 hours to 24
465 hours in order to reduce the efficiency of guard discovery
466 attacks. Fixes ticket 23856.
468 o Minor features (compatibility, OpenSSL):
469 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
470 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
471 since they neither disabled TLS 1.3 nor enabled any of the
472 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
475 o Minor features (denial-of-service avoidance):
476 - Make our OOM handler aware of the geoip client history cache so it
477 doesn't fill up the memory. This check is important for IPv6 and
478 our DoS mitigation subsystem. Closes ticket 25122.
480 o Minor features (fallback directory mirrors):
481 - The fallback directory list has been re-generated based on the
482 current status of the network. Tor uses fallback directories to
483 bootstrap when it doesn't yet have up-to-date directory
484 information. Closes ticket 24801.
485 - Make the default DirAuthorityFallbackRate 0.1, so that clients
486 prefer to bootstrap from fallback directory mirrors. This is a
487 follow-up to 24679, which removed weights from the default
488 fallbacks. Implements ticket 24681.
490 o Minor features (geoip):
491 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
494 o Minor features (linux seccomp2 sandbox):
495 - Update the sandbox rules so that they should now work correctly
496 with Glibc 2.26. Closes ticket 24315.
498 o Minor bugfix (channel connection):
499 - Use the actual observed address of an incoming relay connection,
500 not the canonical address of the relay from its descriptor, when
501 making decisions about how to handle the incoming connection.
502 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
504 o Minor bugfix (directory authority):
505 - Directory authorities, when refusing a descriptor from a rejected
506 relay, now explicitly tell the relay (in its logs) to set a valid
507 ContactInfo address and contact the bad-relays@ mailing list.
508 Fixes bug 25170; bugfix on 0.2.9.1.
510 o Minor bugfixes (address selection):
511 - When the fascist_firewall_choose_address_ functions don't find a
512 reachable address, set the returned address to the null address
513 and port. This is a precautionary measure, because some callers do
514 not check the return value. Fixes bug 24736; bugfix
517 o Minor bugfixes (compilation):
518 - Fix a signed/unsigned comparison warning introduced by our fix to
519 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
521 o Minor bugfixes (control port, linux seccomp2 sandbox):
522 - Avoid a crash when attempting to use the seccomp2 sandbox together
523 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
526 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
527 - Fix a possible crash on malformed consensus. If a consensus had
528 contained an unparseable protocol line, it could have made clients
529 and relays crash with a null-pointer exception. To exploit this
530 issue, however, an attacker would need to be able to subvert the
531 directory authority system. Fixes bug 25251; bugfix on
532 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
534 o Minor bugfixes (memory usage):
535 - When queuing DESTROY cells on a channel, only queue the circuit-id
536 and reason fields: not the entire 514-byte cell. This fix should
537 help mitigate any bugs or attacks that fill up these queues, and
538 free more RAM for other uses. Fixes bug 24666; bugfix
541 o Minor bugfixes (network layer):
542 - When closing a connection via close_connection_immediately(), we
543 mark it as "not blocked on bandwidth", to prevent later calls from
544 trying to unblock it, and give it permission to read. This fixes a
545 backtrace warning that can happen on relays under various
546 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
548 o Minor bugfixes (OSX):
549 - Don't exit the Tor process if setrlimit() fails to change the file
550 limit (which can happen sometimes on some versions of OSX). Fixes
551 bug 21074; bugfix on 0.0.9pre5.
553 o Minor bugfixes (path selection):
554 - When selecting relays by bandwidth, avoid a rounding error that
555 could sometimes cause load to be imbalanced incorrectly.
556 Previously, we would always round upwards; now, we round towards
557 the nearest integer. This had the biggest effect when a relay's
558 weight adjustments should have given it weight 0, but it got
559 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
560 - When calculating the fraction of nodes that have descriptors, and
561 all nodes in the network have zero bandwidths, count the number of
562 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
563 - Actually log the total bandwidth in compute_weighted_bandwidths().
564 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
566 o Minor bugfixes (portability, msvc):
567 - Fix a bug in the bit-counting parts of our timing-wheel code on
568 MSVC. (Note that MSVC is still not a supported build platform, due
569 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
572 o Minor bugfixes (relay):
573 - Make the internal channel_is_client() function look at what sort
574 of connection handshake the other side used, rather than whether
575 the other side ever sent a create_fast cell to us. Backports part
576 of the fixes from bugs 22805 and 24898.
578 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
579 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
581 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
582 bugfix on 0.2.9.4-alpha.
585 Changes in version 0.3.2.9 - 2018-01-09
586 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
588 The 0.3.2 series includes our long-anticipated new onion service
589 design, with numerous security features. (For more information, see
590 our blog post at https://blog.torproject.org/fall-harvest.) We also
591 have a new circuit scheduler algorithm for improved performance on
592 relays everywhere (see https://blog.torproject.org/kist-and-tell),
593 along with many smaller features and bugfixes.
595 Per our stable release policy, we plan to support each stable release
596 series for at least the next nine months, or for three months after
597 the first stable release of the next series: whichever is longer. If
598 you need a release with long-term support, we recommend that you stay
599 with the 0.2.9 series.
601 Below is a list of the changes since 0.3.1.7. For a list of all
602 changes since 0.3.2.8-rc, see the ChangeLog file.
604 o Directory authority changes:
605 - Add "Bastet" as a ninth directory authority to the default list.
607 - The directory authority "Longclaw" has changed its IP address.
609 - Remove longclaw's IPv6 address, as it will soon change. Authority
610 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
611 3/8 directory authorities with IPv6 addresses, but there are also
612 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
613 - Add an IPv6 address for the "bastet" directory authority. Closes
616 o Major features (next-generation onion services):
617 - Tor now supports the next-generation onion services protocol for
618 clients and services! As part of this release, the core of
619 proposal 224 has been implemented and is available for
620 experimentation and testing by our users. This newer version of
621 onion services ("v3") features many improvements over the legacy
624 a) Better crypto (replaced SHA1/DH/RSA1024
625 with SHA3/ed25519/curve25519)
627 b) Improved directory protocol, leaking much less information to
630 c) Improved directory protocol, with smaller surface for
633 d) Better onion address security against impersonation.
635 e) More extensible introduction/rendezvous protocol.
637 f) A cleaner and more modular codebase.
639 You can identify a next-generation onion address by its length:
640 they are 56 characters long, as in
641 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
643 In the future, we will release more options and features for v3
644 onion services, but we first need a testing period, so that the
645 current codebase matures and becomes more robust. Planned features
646 include: offline keys, advanced client authorization, improved
647 guard algorithms, and statistics. For full details, see
650 Legacy ("v2") onion services will still work for the foreseeable
651 future, and will remain the default until this new codebase gets
652 tested and hardened. Service operators who want to experiment with
653 the new system can use the 'HiddenServiceVersion 3' torrc
654 directive along with the regular onion service configuration
655 options. For more information, see our blog post at
656 "https://blog.torproject.org/fall-harvest". Enjoy!
658 o Major feature (scheduler, channel):
659 - Tor now uses new schedulers to decide which circuits should
660 deliver cells first, in order to improve congestion at relays. The
661 first type is called "KIST" ("Kernel Informed Socket Transport"),
662 and is only available on Linux-like systems: it uses feedback from
663 the kernel to prevent the kernel's TCP buffers from growing too
664 full. The second new scheduler type is called "KISTLite": it
665 behaves the same as KIST, but runs on systems without kernel
666 support for inspecting TCP implementation details. The old
667 scheduler is still available, under the name "Vanilla". To change
668 the default scheduler preference order, use the new "Schedulers"
669 option. (The default preference order is "KIST,KISTLite,Vanilla".)
671 Matt Traudt implemented KIST, based on research by Rob Jansen,
672 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
673 more information, see the design paper at
674 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
675 followup implementation paper at https://arxiv.org/abs/1709.01044.
676 Closes ticket 12541. For more information, see our blog post at
677 "https://blog.torproject.org/kist-and-tell".
679 o Major bugfixes (security, general):
680 - Fix a denial of service bug where an attacker could use a
681 malformed directory object to cause a Tor instance to pause while
682 OpenSSL would try to read a passphrase from the terminal. (Tor
683 instances run without a terminal, which is the case for most Tor
684 packages, are not impacted.) Fixes bug 24246; bugfix on every
685 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
686 Found by OSS-Fuzz as testcase 6360145429790720.
688 o Major bugfixes (security, directory authority):
689 - Fix a denial of service issue where an attacker could crash a
690 directory authority using a malformed router descriptor. Fixes bug
691 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
694 o Major bugfixes (security, onion service v2):
695 - Fix a use-after-free error that could crash v2 Tor onion services
696 when they failed to open circuits while expiring introduction
697 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
698 also tracked as TROVE-2017-013 and CVE-2017-8823.
699 - When checking for replays in the INTRODUCE1 cell data for a
700 (legacy) onion service, correctly detect replays in the RSA-
701 encrypted part of the cell. We were previously checking for
702 replays on the entire cell, but those can be circumvented due to
703 the malleability of Tor's legacy hybrid encryption. This fix helps
704 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
705 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
708 o Major bugfixes (security, relay):
709 - When running as a relay, make sure that we never build a path
710 through ourselves, even in the case where we have somehow lost the
711 version of our descriptor appearing in the consensus. Fixes part
712 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
713 as TROVE-2017-012 and CVE-2017-8822.
714 - When running as a relay, make sure that we never choose ourselves
715 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
716 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
718 o Major bugfixes (bootstrapping):
719 - Fetch descriptors aggressively whenever we lack enough to build
720 circuits, regardless of how many descriptors we are missing.
721 Previously, we would delay launching the fetch when we had fewer
722 than 15 missing descriptors, even if some of those descriptors
723 were blocking circuits from building. Fixes bug 23985; bugfix on
724 0.1.1.11-alpha. The effects of this bug became worse in
725 0.3.0.3-alpha, when we began treating missing descriptors from our
726 primary guards as a reason to delay circuits.
727 - Don't try fetching microdescriptors from relays that have failed
728 to deliver them in the past. Fixes bug 23817; bugfix
731 o Major bugfixes (circuit prediction):
732 - Fix circuit prediction logic so that a client doesn't treat a port
733 as being "handled" by a circuit if that circuit already has
734 isolation settings on it. This change should make Tor clients more
735 responsive by improving their chances of having a pre-created
736 circuit ready for use when a request arrives. Fixes bug 18859;
737 bugfix on 0.2.3.3-alpha.
739 o Major bugfixes (exit relays, DNS):
740 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
741 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
742 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
743 identifying and finding a workaround to this bug and to Moritz,
744 Arthur Edelstein, and Roger for helping to track it down and
747 o Major bugfixes (relay, crash, assertion failure):
748 - Fix a timing-based assertion failure that could occur when the
749 circuit out-of-memory handler freed a connection's output buffer.
750 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
752 o Major bugfixes (usability, control port):
753 - Report trusted clock skew indications as bootstrap errors, so
754 controllers can more easily alert users when their clocks are
755 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
757 o Minor features (bridge):
758 - Bridge relays can now set the BridgeDistribution config option to
759 add a "bridge-distribution-request" line to their bridge
760 descriptor, which tells BridgeDB how they'd like their bridge
761 address to be given out. (Note that as of Oct 2017, BridgeDB does
762 not yet implement this feature.) As a side benefit, this feature
763 provides a way to distinguish bridge descriptors from non-bridge
764 descriptors. Implements tickets 18329.
765 - When handling the USERADDR command on an ExtOrPort, warn when the
766 transports provides a USERADDR with no port. In a future version,
767 USERADDR commands of this format may be rejected. Detects problems
768 related to ticket 23080.
770 o Minor features (bug detection):
771 - Log a warning message with a stack trace for any attempt to call
772 get_options() during option validation. This pattern has caused
773 subtle bugs in the past. Closes ticket 22281.
775 o Minor features (build, compilation):
776 - The "check-changes" feature is now part of the "make check" tests;
777 we'll use it to try to prevent misformed changes files from
778 accumulating. Closes ticket 23564.
779 - Tor builds should now fail if there are any mismatches between the
780 C type representing a configuration variable and the C type the
781 data-driven parser uses to store a value there. Previously, we
782 needed to check these by hand, which sometimes led to mistakes.
785 o Minor features (client):
786 - You can now use Tor as a tunneled HTTP proxy: use the new
787 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
788 requests. Closes ticket 22407.
789 - Add an extra check to make sure that we always use the newer guard
790 selection code for picking our guards. Closes ticket 22779.
791 - When downloading (micro)descriptors, don't split the list into
792 multiple requests unless we want at least 32 descriptors.
793 Previously, we split at 4, not 32, which led to significant
794 overhead in HTTP request size and degradation in compression
795 performance. Closes ticket 23220.
796 - Improve log messages when missing descriptors for primary guards.
797 Resolves ticket 23670.
799 o Minor features (command line):
800 - Add a new commandline option, --key-expiration, which prints when
801 the current signing key is going to expire. Implements ticket
802 17639; patch by Isis Lovecruft.
804 o Minor features (control port):
805 - If an application tries to use the control port as an HTTP proxy,
806 respond with a meaningful "This is the Tor control port" message,
807 and log the event. Closes ticket 1667. Patch from Ravi
809 - Provide better error message for GETINFO desc/(id|name) when not
810 fetching router descriptors. Closes ticket 5847. Patch by
812 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
813 whether Tor will try to download router descriptors and
814 microdescriptors respectively. Closes ticket 22684.
815 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
816 so controllers can tell whether the geoip databases are loaded.
818 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
819 events. Closes ticket 19254. Patch by "DonnchaC".
821 o Minor features (development support):
822 - Developers can now generate a call-graph for Tor using the
823 "calltool" python program, which post-processes object dumps. It
824 should work okay on many Linux and OSX platforms, and might work
825 elsewhere too. To run it, install calltool from
826 https://gitweb.torproject.org/user/nickm/calltool.git and run
827 "make callgraph". Closes ticket 19307.
829 o Minor features (directory authority):
830 - Make the "Exit" flag assignment only depend on whether the exit
831 policy allows connections to ports 80 and 443. Previously relays
832 would get the Exit flag if they allowed connections to one of
833 these ports and also port 6667. Resolves ticket 23637.
835 o Minor features (ed25519):
836 - Add validation function to checks for torsion components in
837 ed25519 public keys, used by prop224 client-side code. Closes
838 ticket 22006. Math help by Ian Goldberg.
840 o Minor features (exit relay, DNS):
841 - Improve the clarity and safety of the log message from evdns when
842 receiving an apparently spoofed DNS reply. Closes ticket 3056.
844 o Minor features (fallback directory mirrors):
845 - The fallback directory list has been re-generated based on the
846 current status of the network. Tor uses fallback directories to
847 bootstrap when it doesn't yet have up-to-date directory
848 information. Closes ticket 24801.
849 - Make the default DirAuthorityFallbackRate 0.1, so that clients
850 prefer to bootstrap from fallback directory mirrors. This is a
851 follow-up to 24679, which removed weights from the default
852 fallbacks. Implements ticket 24681.
854 o Minor features (geoip):
855 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
858 o Minor features (integration, hardening):
859 - Add a new NoExec option to prevent Tor from running other
860 programs. When this option is set to 1, Tor will never try to run
861 another program, regardless of the settings of
862 PortForwardingHelper, ClientTransportPlugin, or
863 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
864 without restarting Tor. Closes ticket 22976.
866 o Minor features (linux seccomp2 sandbox):
867 - Update the sandbox rules so that they should now work correctly
868 with Glibc 2.26. Closes ticket 24315.
870 o Minor features (logging):
871 - Provide better warnings when the getrandom() syscall fails. Closes
873 - Downgrade a pair of log messages that could occur when an exit's
874 resolver gave us an unusual (but not forbidden) response. Closes
876 - Improve the message we log when re-enabling circuit build timeouts
877 after having received a consensus. Closes ticket 20963.
878 - Log more circuit information whenever we are about to try to
879 package a relay cell on a circuit with a nonexistent n_chan.
880 Attempt to diagnose ticket 8185.
881 - Improve info-level log identification of particular circuits, to
882 help with debugging. Closes ticket 23645.
883 - Improve the warning message for specifying a relay by nickname.
884 The previous message implied that nickname registration was still
885 part of the Tor network design, which it isn't. Closes
887 - If the sandbox filter fails to load, suggest to the user that
888 their kernel might not support seccomp2. Closes ticket 23090.
890 o Minor features (onion service, circuit, logging):
891 - Improve logging of many callsite in the circuit subsystem to print
892 the circuit identifier(s).
893 - Log when we cleanup an intro point from a service so we know when
894 and for what reason it happened. Closes ticket 23604.
896 o Minor features (portability):
897 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
898 (It doesn't yet work with the sandbox enabled.) Closes
900 - Check at configure time whether uint8_t is the same type as
901 unsigned char. Lots of existing code already makes this
902 assumption, and there could be strict aliasing issues if the
903 assumption is violated. Closes ticket 22410.
905 o Minor features (relay):
906 - When choosing which circuits can be expired as unused, consider
907 circuits from clients even if those clients used regular CREATE
908 cells to make them; and do not consider circuits from relays even
909 if they were made with CREATE_FAST. Part of ticket 22805.
910 - Reject attempts to use relative file paths when RunAsDaemon is
911 set. Previously, Tor would accept these, but the directory-
912 changing step of RunAsDaemon would give strange and/or confusing
913 results. Closes ticket 22731.
915 o Minor features (relay statistics):
916 - Change relay bandwidth reporting stats interval from 4 hours to 24
917 hours in order to reduce the efficiency of guard discovery
918 attacks. Fixes ticket 23856.
920 o Minor features (reverted deprecations):
921 - The ClientDNSRejectInternalAddresses flag can once again be set in
922 non-testing Tor networks, so long as they do not use the default
923 directory authorities. This change also removes the deprecation of
924 this flag from 0.2.9.2-alpha. Closes ticket 21031.
926 o Minor features (robustness):
927 - Change several fatal assertions when flushing buffers into non-
928 fatal assertions, to prevent any recurrence of 23690.
930 o Minor features (startup, safety):
931 - When configured to write a PID file, Tor now exits if it is unable
932 to do so. Previously, it would warn and continue. Closes
935 o Minor features (static analysis):
936 - The BUG() macro has been changed slightly so that Coverity no
937 longer complains about dead code if the bug is impossible. Closes
940 o Minor features (testing):
941 - Our fuzzing tests now test the encrypted portions of v3 onion
942 service descriptors. Implements more of 21509.
943 - Add a unit test to make sure that our own generated platform
944 string will be accepted by directory authorities. Closes
946 - The default chutney network tests now include tests for the v3
947 onion service design. Make sure you have the latest version of
948 chutney if you want to run these. Closes ticket 22437.
949 - Add a unit test to verify that we can parse a hardcoded v2 onion
950 service descriptor. Closes ticket 15554.
952 o Minor bugfixes (address selection):
953 - When the fascist_firewall_choose_address_ functions don't find a
954 reachable address, set the returned address to the null address
955 and port. This is a precautionary measure, because some callers do
956 not check the return value. Fixes bug 24736; bugfix
959 o Minor bugfixes (bootstrapping):
960 - When warning about state file clock skew, report the correct
961 direction for the detected skew. Fixes bug 23606; bugfix
964 o Minor bugfixes (bridge clients, bootstrap):
965 - Retry directory downloads when we get our first bridge descriptor
966 during bootstrap or while reconnecting to the network. Keep
967 retrying every time we get a bridge descriptor, until we have a
968 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
969 - Stop delaying bridge descriptor fetches when we have cached bridge
970 descriptors. Instead, only delay bridge descriptor fetches when we
971 have at least one reachable bridge. Fixes part of bug 24367;
972 bugfix on 0.2.0.3-alpha.
973 - Stop delaying directory fetches when we have cached bridge
974 descriptors. Instead, only delay bridge descriptor fetches when
975 all our bridges are definitely unreachable. Fixes part of bug
976 24367; bugfix on 0.2.0.3-alpha.
978 o Minor bugfixes (bridge):
979 - Overwrite the bridge address earlier in the process of retrieving
980 its descriptor, to make sure we reach it on the configured
981 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
983 o Minor bugfixes (build, compilation):
984 - Fix a compilation warning when building with zstd support on
985 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
986 and fixed by Andreas Stieger.
987 - When searching for OpenSSL, don't accept any OpenSSL library that
988 lacks TLSv1_1_method(): Tor doesn't build with those versions.
989 Additionally, look in /usr/local/opt/openssl, if it's present.
990 These changes together repair the default build on OSX systems
991 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
992 - Fix a signed/unsigned comparison warning introduced by our fix to
993 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
994 - Fix a memory leak warning in one of the libevent-related
995 configuration tests that could occur when manually specifying
996 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
997 Found and patched by Alex Xu.
998 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
999 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1001 o Minor bugfixes (certificate handling):
1002 - Fix a time handling bug in Tor certificates set to expire after
1003 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
1004 Coverity as CID 1415728.
1006 o Minor bugfixes (client):
1007 - By default, do not enable storage of client-side DNS values. These
1008 values were unused by default previously, but they should not have
1009 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
1011 o Minor bugfixes (client, usability):
1012 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
1013 SOCKS4a requests that contain IP address strings, even when
1014 SafeSocks in enabled, as this prevents user from connecting to
1015 known IP addresses without relying on DNS for resolving. SafeSocks
1016 still rejects SOCKS connections that connect to IP addresses when
1017 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
1018 bugfix on Tor 0.2.6.2-alpha.
1020 o Minor bugfixes (code correctness):
1021 - Call htons() in extend_cell_format() for encoding a 16-bit value.
1022 Previously we used ntohs(), which happens to behave the same on
1023 all the platforms we support, but which isn't really correct.
1024 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
1025 - For defense-in-depth, make the controller's write_escaped_data()
1026 function robust to extremely long inputs. Fixes bug 19281; bugfix
1027 on 0.1.1.1-alpha. Reported by Guido Vranken.
1028 - Fix several places in our codebase where a C compiler would be
1029 likely to eliminate a check, based on assuming that undefined
1030 behavior had not happened elsewhere in the code. These cases are
1031 usually a sign of redundant checking or dubious arithmetic. Found
1032 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
1033 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
1036 o Minor bugfixes (compression):
1037 - Handle a pathological case when decompressing Zstandard data when
1038 the output buffer size is zero. Fixes bug 23551; bugfix
1041 o Minor bugfixes (consensus expiry):
1042 - Check for adequate directory information correctly. Previously, Tor
1043 would reconsider whether it had sufficient directory information
1044 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
1046 o Minor bugfixes (control port, linux seccomp2 sandbox):
1047 - Avoid a crash when attempting to use the seccomp2 sandbox together
1048 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1051 o Minor bugfixes (control port, onion services):
1052 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
1053 HS_DESC event when a service is not able to upload a descriptor.
1054 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
1056 o Minor bugfixes (directory cache):
1057 - Recover better from empty or corrupt files in the consensus cache
1058 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1059 - When a consensus diff calculation is only partially successful,
1060 only record the successful parts as having succeeded. Partial
1061 success can happen if (for example) one compression method fails
1062 but the others succeed. Previously we misrecorded all the
1063 calculations as having succeeded, which would later cause a
1064 nonfatal assertion failure. Fixes bug 24086; bugfix
1067 o Minor bugfixes (directory client):
1068 - On failure to download directory information, delay retry attempts
1069 by a random amount based on the "decorrelated jitter" algorithm.
1070 Our previous delay algorithm tended to produce extra-long delays
1071 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
1073 o Minor bugfixes (directory protocol):
1074 - Directory servers now include a "Date:" http header for response
1075 codes other than 200. Clients starting with a skewed clock and a
1076 recent consensus were getting "304 Not modified" responses from
1077 directory authorities, so without the Date header, the client
1078 would never hear about a wrong clock. Fixes bug 23499; bugfix
1080 - Make clients wait for 6 seconds before trying to download a
1081 consensus from an authority. Fixes bug 17750; bugfix
1084 o Minor bugfixes (documentation):
1085 - Document better how to read gcov, and what our gcov postprocessing
1086 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
1087 - Fix manpage to not refer to the obsolete (and misspelled)
1088 UseEntryGuardsAsDirectoryGuards parameter in the description of
1089 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
1091 o Minor bugfixes (DoS-resistance):
1092 - If future code asks if there are any running bridges, without
1093 checking if bridges are enabled, log a BUG warning rather than
1094 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
1096 o Minor bugfixes (entry guards):
1097 - Tor now updates its guard state when it reads a consensus
1098 regardless of whether it's missing descriptors. That makes tor use
1099 its primary guards to fetch descriptors in some edge cases where
1100 it would previously have used fallback directories. Fixes bug
1101 23862; bugfix on 0.3.0.1-alpha.
1103 o Minor bugfixes (format strictness):
1104 - Restrict several data formats to decimal. Previously, the
1105 BuildTimeHistogram entries in the state file, the "bw=" entries in
1106 the bandwidth authority file, and the process IDs passed to the
1107 __OwningControllerProcess option could all be specified in hex or
1108 octal as well as in decimal. This was not an intentional feature.
1109 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
1112 o Minor bugfixes (heartbeat):
1113 - If we fail to write a heartbeat message, schedule a retry for the
1114 minimum heartbeat interval number of seconds in the future. Fixes
1115 bug 19476; bugfix on 0.2.3.1-alpha.
1117 o Minor bugfixes (logging):
1118 - Suppress a log notice when relay descriptors arrive. We already
1119 have a bootstrap progress for this so no need to log notice
1120 everytime tor receives relay descriptors. Microdescriptors behave
1121 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
1122 - Remove duplicate log messages regarding opening non-local
1123 SocksPorts upon parsing config and opening listeners at startup.
1124 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
1125 - Use a more comprehensible log message when telling the user
1126 they've excluded every running exit node. Fixes bug 7890; bugfix
1128 - When logging the number of descriptors we intend to download per
1129 directory request, do not log a number higher than then the number
1130 of descriptors we're fetching in total. Fixes bug 19648; bugfix
1132 - When warning about a directory owned by the wrong user, log the
1133 actual name of the user owning the directory. Previously, we'd log
1134 the name of the process owner twice. Fixes bug 23487; bugfix
1136 - Fix some messages on unexpected errors from the seccomp2 library.
1137 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
1138 - The tor specification says hop counts are 1-based, so fix two log
1139 messages that mistakenly logged 0-based hop counts. Fixes bug
1140 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
1141 Credit to Xiaofan Li for reporting this issue.
1143 o Minor bugfixes (logging, relay shutdown, annoyance):
1144 - When a circuit is marked for close, do not attempt to package any
1145 cells for channels on that circuit. Previously, we would detect
1146 this condition lower in the call stack, when we noticed that the
1147 circuit had no attached channel, and log an annoying message.
1148 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1150 o Minor bugfixes (memory safety, defensive programming):
1151 - Clear the target address when node_get_prim_orport() returns
1152 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1154 o Minor bugfixes (memory usage):
1155 - When queuing DESTROY cells on a channel, only queue the circuit-id
1156 and reason fields: not the entire 514-byte cell. This fix should
1157 help mitigate any bugs or attacks that fill up these queues, and
1158 free more RAM for other uses. Fixes bug 24666; bugfix
1161 o Minor bugfixes (network layer):
1162 - When closing a connection via close_connection_immediately(), we
1163 mark it as "not blocked on bandwidth", to prevent later calls from
1164 trying to unblock it, and give it permission to read. This fixes a
1165 backtrace warning that can happen on relays under various
1166 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1168 o Minor bugfixes (onion services):
1169 - The introduction circuit was being timed out too quickly while
1170 waiting for the rendezvous circuit to complete. Keep the intro
1171 circuit around longer instead of timing out and reopening new ones
1172 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
1173 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1174 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1176 - When handling multiple SOCKS request for the same .onion address,
1177 only fetch the service descriptor once.
1178 - Avoid a possible double close of a circuit by the intro point on
1179 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1180 bugfix on 0.3.0.1-alpha.
1181 - When reloading configured onion services, copy all information
1182 from the old service object. Previously, some data was omitted,
1183 causing delays in descriptor upload, and other bugs. Fixes bug
1184 23790; bugfix on 0.2.1.9-alpha.
1186 o Minor bugfixes (path selection):
1187 - When selecting relays by bandwidth, avoid a rounding error that
1188 could sometimes cause load to be imbalanced incorrectly.
1189 Previously, we would always round upwards; now, we round towards
1190 the nearest integer. This had the biggest effect when a relay's
1191 weight adjustments should have given it weight 0, but it got
1192 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1193 - When calculating the fraction of nodes that have descriptors, and
1194 all nodes in the network have zero bandwidths, count the number of
1195 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1196 - Actually log the total bandwidth in compute_weighted_bandwidths().
1197 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1199 o Minor bugfixes (portability):
1200 - Stop using the PATH_MAX variable, which is not defined on GNU
1201 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
1202 - Fix a bug in the bit-counting parts of our timing-wheel code on
1203 MSVC. (Note that MSVC is still not a supported build platform, due
1204 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1207 o Minor bugfixes (relay):
1208 - When uploading our descriptor for the first time after startup,
1209 report the reason for uploading as "Tor just started" rather than
1210 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
1211 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1212 relays, to prevent spurious address resolutions and descriptor
1213 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1214 bugfix on in 0.2.8.1-alpha.
1215 - Avoid a crash when transitioning from client mode to bridge mode.
1216 Previously, we would launch the worker threads whenever our
1217 "public server" mode changed, but not when our "server" mode
1218 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1220 o Minor bugfixes (testing):
1221 - Fix a spurious fuzzing-only use of an uninitialized value. Found
1222 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
1223 - Test that IPv6-only clients can use microdescriptors when running
1224 "make test-network-all". Requires chutney master 61c28b9 or later.
1225 Closes ticket 24109.
1226 - Prevent scripts/test/coverage from attempting to move gcov output
1227 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
1228 - Capture and detect several "Result does not fit" warnings in unit
1229 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
1231 - Fix additional channelpadding unit test failures by using mocked
1232 time instead of actual time for all tests. Fixes bug 23608; bugfix
1234 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
1235 to correctly handle cases where a caller gives it an RSA key of
1236 under 160 bits. (This is not actually a bug in Tor itself, but
1237 rather in our fuzzing code.) Fixes bug 24247; bugfix on
1238 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
1239 - Fix a broken unit test for the OutboundAddress option: the parsing
1240 function was never returning an error on failure. Fixes bug 23366;
1241 bugfix on 0.3.0.3-alpha.
1242 - Fix a signed-integer overflow in the unit tests for
1243 dir/download_status_random_backoff, which was untriggered until we
1244 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1246 o Minor bugfixes (usability, control port):
1247 - Stop making an unnecessary routerlist check in NETINFO clock skew
1248 detection; this was preventing clients from reporting NETINFO clock
1249 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1251 o Code simplification and refactoring:
1252 - Remove various ways of testing circuits and connections for
1253 "clientness"; instead, favor channel_is_client(). Part of
1255 - Extract the code for handling newly-open channels into a separate
1256 function from the general code to handle channel state
1257 transitions. This change simplifies our callgraph, reducing the
1258 size of the largest strongly connected component by roughly a
1259 factor of two. Closes ticket 22608.
1260 - Remove dead code for largely unused statistics on the number of
1261 times we've attempted various public key operations. Fixes bug
1262 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1263 - Remove several now-obsolete functions for asking about old
1264 variants directory authority status. Closes ticket 22311; patch
1266 - Remove some of the code that once supported "Named" and "Unnamed"
1267 routers. Authorities no longer vote for these flags. Closes
1269 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1270 and old hidden services, to indicate that they aren't suitable for
1271 new protocols or formats. Closes ticket 23026.
1272 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1273 22521. Patch from Neel Chauhan.
1274 - Split the enormous circuit_send_next_onion_skin() function into
1275 multiple subfunctions. Closes ticket 22804.
1276 - Split the portions of the buffer.c module that handle particular
1277 protocols into separate modules. Part of ticket 23149.
1278 - Use our test macros more consistently, to produce more useful
1279 error messages when our unit tests fail. Add coccinelle patches to
1280 allow us to re-check for test macro uses. Closes ticket 22497.
1282 o Deprecated features:
1283 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
1284 now deprecated; they do not apply to relays, and they have had no
1285 effect on clients since 0.2.8.x. Closes ticket 19704.
1286 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1287 only applies to direct unencrypted HTTP connections to your
1288 directory server, which your Tor probably isn't using. Closes
1292 - Add notes in man page regarding OS support for the various
1293 scheduler types. Attempt to use less jargon in the scheduler
1294 section. Closes ticket 24254.
1295 - Clarify that the Address option is entirely about setting an
1296 advertised IPv4 address. Closes ticket 18891.
1297 - Clarify the manpage's use of the term "address" to clarify what
1298 kind of address is intended. Closes ticket 21405.
1299 - Document that onion service subdomains are allowed, and ignored.
1300 Closes ticket 18736.
1301 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1302 kernels. Closes ticket 22677.
1303 - Document all values of PublishServerDescriptor in the manpage.
1304 Closes ticket 15645.
1305 - Improve the documentation for the directory port part of the
1306 DirAuthority line. Closes ticket 20152.
1307 - Restore documentation for the authorities' "approved-routers"
1308 file. Closes ticket 21148.
1311 - The AllowDotExit option has been removed as unsafe. It has been
1312 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1313 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1314 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1315 Closes ticket 21031.
1316 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1317 nobody was using it any longer. Closes ticket 22377.
1320 Changes in version 0.3.1.9 - 2017-12-01:
1321 Tor 0.3.1.9 backports important security and stability fixes from the
1322 0.3.2 development series. All Tor users should upgrade to this
1323 release, or to another of the releases coming out today.
1325 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1326 - Fix a denial of service bug where an attacker could use a
1327 malformed directory object to cause a Tor instance to pause while
1328 OpenSSL would try to read a passphrase from the terminal. (Tor
1329 instances run without a terminal, which is the case for most Tor
1330 packages, are not impacted.) Fixes bug 24246; bugfix on every
1331 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1332 Found by OSS-Fuzz as testcase 6360145429790720.
1333 - Fix a denial of service issue where an attacker could crash a
1334 directory authority using a malformed router descriptor. Fixes bug
1335 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1337 - When checking for replays in the INTRODUCE1 cell data for a
1338 (legacy) onion service, correctly detect replays in the RSA-
1339 encrypted part of the cell. We were previously checking for
1340 replays on the entire cell, but those can be circumvented due to
1341 the malleability of Tor's legacy hybrid encryption. This fix helps
1342 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1343 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1346 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1347 - Fix a use-after-free error that could crash v2 Tor onion services
1348 when they failed to open circuits while expiring introduction
1349 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1350 also tracked as TROVE-2017-013 and CVE-2017-8823.
1352 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1353 - When running as a relay, make sure that we never build a path
1354 through ourselves, even in the case where we have somehow lost the
1355 version of our descriptor appearing in the consensus. Fixes part
1356 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1357 as TROVE-2017-012 and CVE-2017-8822.
1358 - When running as a relay, make sure that we never choose ourselves
1359 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1360 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1362 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1363 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1364 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1365 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1366 identifying and finding a workaround to this bug and to Moritz,
1367 Arthur Edelstein, and Roger for helping to track it down and
1370 o Minor features (bridge):
1371 - Bridges now include notice in their descriptors that they are
1372 bridges, and notice of their distribution status, based on their
1373 publication settings. Implements ticket 18329. For more fine-
1374 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1377 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1378 - Add an IPv6 address for the "bastet" directory authority. Closes
1381 o Minor features (geoip):
1382 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1385 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1386 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1387 relays, to prevent spurious address resolutions and descriptor
1388 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1389 bugfix on in 0.2.8.1-alpha.
1391 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1392 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1393 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1395 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1396 - When a circuit is marked for close, do not attempt to package any
1397 cells for channels on that circuit. Previously, we would detect
1398 this condition lower in the call stack, when we noticed that the
1399 circuit had no attached channel, and log an annoying message.
1400 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1402 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
1403 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1404 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1407 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1408 - Avoid a crash when transitioning from client mode to bridge mode.
1409 Previously, we would launch the worker threads whenever our
1410 "public server" mode changed, but not when our "server" mode
1411 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1414 Changes in version 0.3.0.13 - 2017-12-01
1415 Tor 0.3.0.13 backports important security and stability bugfixes from
1416 later Tor releases. All Tor users should upgrade to this release, or
1417 to another of the releases coming out today.
1419 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1420 2018. If you need a release with long-term support, please stick with
1421 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1423 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1424 - Fix a denial of service bug where an attacker could use a
1425 malformed directory object to cause a Tor instance to pause while
1426 OpenSSL would try to read a passphrase from the terminal. (Tor
1427 instances run without a terminal, which is the case for most Tor
1428 packages, are not impacted.) Fixes bug 24246; bugfix on every
1429 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1430 Found by OSS-Fuzz as testcase 6360145429790720.
1431 - Fix a denial of service issue where an attacker could crash a
1432 directory authority using a malformed router descriptor. Fixes bug
1433 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1435 - When checking for replays in the INTRODUCE1 cell data for a
1436 (legacy) onion service, correctly detect replays in the RSA-
1437 encrypted part of the cell. We were previously checking for
1438 replays on the entire cell, but those can be circumvented due to
1439 the malleability of Tor's legacy hybrid encryption. This fix helps
1440 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1441 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1444 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1445 - Fix a use-after-free error that could crash v2 Tor onion services
1446 when they failed to open circuits while expiring introduction
1447 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1448 also tracked as TROVE-2017-013 and CVE-2017-8823.
1450 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1451 - When running as a relay, make sure that we never build a path
1452 through ourselves, even in the case where we have somehow lost the
1453 version of our descriptor appearing in the consensus. Fixes part
1454 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1455 as TROVE-2017-012 and CVE-2017-8822.
1456 - When running as a relay, make sure that we never choose ourselves
1457 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1458 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1460 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1461 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1462 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1463 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1464 identifying and finding a workaround to this bug and to Moritz,
1465 Arthur Edelstein, and Roger for helping to track it down and
1468 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1469 - Enable a couple of pieces of Windows hardening: one
1470 (HeapEnableTerminationOnCorruption) that has been on-by-default
1471 since Windows 8, and unavailable before Windows 7; and one
1472 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1473 affect us, but shouldn't do any harm. Closes ticket 21953.
1475 o Minor features (bridge, backport from 0.3.1.9):
1476 - Bridges now include notice in their descriptors that they are
1477 bridges, and notice of their distribution status, based on their
1478 publication settings. Implements ticket 18329. For more fine-
1479 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1482 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1483 - Add an IPv6 address for the "bastet" directory authority. Closes
1486 o Minor features (geoip):
1487 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1490 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1491 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1492 relays, to prevent spurious address resolutions and descriptor
1493 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1494 bugfix on in 0.2.8.1-alpha.
1496 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1497 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1498 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1500 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1501 - When a circuit is marked for close, do not attempt to package any
1502 cells for channels on that circuit. Previously, we would detect
1503 this condition lower in the call stack, when we noticed that the
1504 circuit had no attached channel, and log an annoying message.
1505 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1507 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1508 - Avoid a crash when transitioning from client mode to bridge mode.
1509 Previously, we would launch the worker threads whenever our
1510 "public server" mode changed, but not when our "server" mode
1511 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1513 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1514 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1515 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1518 Changes in version 0.2.9.14 - 2017-12-01
1519 Tor 0.3.0.13 backports important security and stability bugfixes from
1520 later Tor releases. All Tor users should upgrade to this release, or
1521 to another of the releases coming out today.
1523 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1524 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1525 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1526 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1527 identifying and finding a workaround to this bug and to Moritz,
1528 Arthur Edelstein, and Roger for helping to track it down and
1531 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1532 - Fix a denial of service bug where an attacker could use a
1533 malformed directory object to cause a Tor instance to pause while
1534 OpenSSL would try to read a passphrase from the terminal. (Tor
1535 instances run without a terminal, which is the case for most Tor
1536 packages, are not impacted.) Fixes bug 24246; bugfix on every
1537 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1538 Found by OSS-Fuzz as testcase 6360145429790720.
1539 - Fix a denial of service issue where an attacker could crash a
1540 directory authority using a malformed router descriptor. Fixes bug
1541 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1543 - When checking for replays in the INTRODUCE1 cell data for a
1544 (legacy) onion service, correctly detect replays in the RSA-
1545 encrypted part of the cell. We were previously checking for
1546 replays on the entire cell, but those can be circumvented due to
1547 the malleability of Tor's legacy hybrid encryption. This fix helps
1548 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1549 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1552 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1553 - Fix a use-after-free error that could crash v2 Tor onion services
1554 when they failed to open circuits while expiring introduction
1555 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1556 also tracked as TROVE-2017-013 and CVE-2017-8823.
1558 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1559 - When running as a relay, make sure that we never build a path
1560 through ourselves, even in the case where we have somehow lost the
1561 version of our descriptor appearing in the consensus. Fixes part
1562 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1563 as TROVE-2017-012 and CVE-2017-8822.
1565 o Minor features (bridge, backport from 0.3.1.9):
1566 - Bridges now include notice in their descriptors that they are
1567 bridges, and notice of their distribution status, based on their
1568 publication settings. Implements ticket 18329. For more fine-
1569 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1572 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1573 - Add an IPv6 address for the "bastet" directory authority. Closes
1576 o Minor features (geoip):
1577 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1580 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1581 - Enable a couple of pieces of Windows hardening: one
1582 (HeapEnableTerminationOnCorruption) that has been on-by-default
1583 since Windows 8, and unavailable before Windows 7; and one
1584 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1585 affect us, but shouldn't do any harm. Closes ticket 21953.
1587 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1588 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1589 relays, to prevent spurious address resolutions and descriptor
1590 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1591 bugfix on in 0.2.8.1-alpha.
1593 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1594 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1595 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1597 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1598 - When a circuit is marked for close, do not attempt to package any
1599 cells for channels on that circuit. Previously, we would detect
1600 this condition lower in the call stack, when we noticed that the
1601 circuit had no attached channel, and log an annoying message.
1602 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1604 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1605 - Avoid a crash when transitioning from client mode to bridge mode.
1606 Previously, we would launch the worker threads whenever our
1607 "public server" mode changed, but not when our "server" mode
1608 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1610 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1611 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1612 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1615 Changes in version 0.2.8.17 - 2017-12-01
1616 Tor 0.2.8.17 backports important security and stability bugfixes from
1617 later Tor releases. All Tor users should upgrade to this release, or
1618 to another of the releases coming out today.
1620 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1621 2018. If you need a release with long-term support, please upgrade with
1622 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1624 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1625 - Fix a denial of service bug where an attacker could use a
1626 malformed directory object to cause a Tor instance to pause while
1627 OpenSSL would try to read a passphrase from the terminal. (Tor
1628 instances run without a terminal, which is the case for most Tor
1629 packages, are not impacted.) Fixes bug 24246; bugfix on every
1630 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1631 Found by OSS-Fuzz as testcase 6360145429790720.
1632 - When checking for replays in the INTRODUCE1 cell data for a
1633 (legacy) onion service, correctly detect replays in the RSA-
1634 encrypted part of the cell. We were previously checking for
1635 replays on the entire cell, but those can be circumvented due to
1636 the malleability of Tor's legacy hybrid encryption. This fix helps
1637 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1638 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1641 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1642 - Fix a use-after-free error that could crash v2 Tor onion services
1643 when they failed to open circuits while expiring introduction
1644 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1645 also tracked as TROVE-2017-013 and CVE-2017-8823.
1647 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1648 - When running as a relay, make sure that we never build a path through
1649 ourselves, even in the case where we have somehow lost the version of
1650 our descriptor appearing in the consensus. Fixes part of bug 21534;
1651 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
1654 o Minor features (bridge, backport from 0.3.1.9):
1655 - Bridges now include notice in their descriptors that they are
1656 bridges, and notice of their distribution status, based on their
1657 publication settings. Implements ticket 18329. For more fine-
1658 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1661 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1662 - Add an IPv6 address for the "bastet" directory authority. Closes
1665 o Minor features (geoip):
1666 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1669 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1670 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1671 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1674 Changes in version 0.2.5.16 - 2017-12-01
1675 Tor 0.2.5.13 backports important security and stability bugfixes from
1676 later Tor releases. All Tor users should upgrade to this release, or
1677 to another of the releases coming out today.
1679 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1680 2018. If you need a release with long-term support, please upgrade to
1681 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1683 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1684 - Fix a denial of service bug where an attacker could use a
1685 malformed directory object to cause a Tor instance to pause while
1686 OpenSSL would try to read a passphrase from the terminal. (Tor
1687 instances run without a terminal, which is the case for most Tor
1688 packages, are not impacted.) Fixes bug 24246; bugfix on every
1689 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1690 Found by OSS-Fuzz as testcase 6360145429790720.
1691 - When checking for replays in the INTRODUCE1 cell data for a
1692 (legacy) onion service, correctly detect replays in the RSA-
1693 encrypted part of the cell. We were previously checking for
1694 replays on the entire cell, but those can be circumvented due to
1695 the malleability of Tor's legacy hybrid encryption. This fix helps
1696 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1697 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1700 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1701 - When running as a relay, make sure that we never build a path
1702 through ourselves, even in the case where we have somehow lost the
1703 version of our descriptor appearing in the consensus. Fixes part
1704 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1705 as TROVE-2017-012 and CVE-2017-8822.
1707 o Minor features (bridge, backport from 0.3.1.9):
1708 - Bridges now include notice in their descriptors that they are
1709 bridges, and notice of their distribution status, based on their
1710 publication settings. Implements ticket 18329. For more fine-
1711 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1714 o Minor features (geoip):
1715 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1719 Changes in version 0.2.5.15 - 2017-10-25
1720 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
1721 series. It also adds a new directory authority, Bastet.
1723 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1724 2018. If you need a release with long-term support, please upgrade to
1725 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1727 o Directory authority changes:
1728 - Add "Bastet" as a ninth directory authority to the default list.
1729 Closes ticket 23910.
1730 - The directory authority "Longclaw" has changed its IP address.
1731 Closes ticket 23592.
1733 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1734 - Avoid an assertion failure bug affecting our implementation of
1735 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1736 handling of "0xx" differs from what we had expected. Fixes bug
1737 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1739 o Minor features (geoip):
1740 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1743 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1744 - Fix a memset() off the end of an array when packing cells. This
1745 bug should be harmless in practice, since the corrupted bytes are
1746 still in the same structure, and are always padding bytes,
1747 ignored, or immediately overwritten, depending on compiler
1748 behavior. Nevertheless, because the memset()'s purpose is to make
1749 sure that any other cell-handling bugs can't expose bytes to the
1750 network, we need to fix it. Fixes bug 22737; bugfix on
1751 0.2.4.11-alpha. Fixes CID 1401591.
1753 o Build features (backport from 0.3.1.5-alpha):
1754 - Tor's repository now includes a Travis Continuous Integration (CI)
1755 configuration file (.travis.yml). This is meant to help new
1756 developers and contributors who fork Tor to a Github repository be
1757 better able to test their changes, and understand what we expect
1758 to pass. To use this new build feature, you must fork Tor to your
1759 Github account, then go into the "Integrations" menu in the
1760 repository settings for your fork and enable Travis, then push
1761 your changes. Closes ticket 22636.
1764 Changes in version 0.2.8.16 - 2017-10-25
1765 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
1766 series, including a bugfix for a crash issue that had affected relays
1767 under memory pressure. It also adds a new directory authority, Bastet.
1769 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1770 2018. If you need a release with long-term support, please stick with
1771 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1773 o Directory authority changes:
1774 - Add "Bastet" as a ninth directory authority to the default list.
1775 Closes ticket 23910.
1776 - The directory authority "Longclaw" has changed its IP address.
1777 Closes ticket 23592.
1779 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1780 - Fix a timing-based assertion failure that could occur when the
1781 circuit out-of-memory handler freed a connection's output buffer.
1782 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1784 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1785 - Remove longclaw's IPv6 address, as it will soon change. Authority
1786 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1787 3/8 directory authorities with IPv6 addresses, but there are also
1788 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1790 o Minor features (geoip):
1791 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1795 Changes in version 0.2.9.13 - 2017-10-25
1796 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
1797 series, including a bugfix for a crash issue that had affected relays
1798 under memory pressure. It also adds a new directory authority, Bastet.
1800 o Directory authority changes:
1801 - Add "Bastet" as a ninth directory authority to the default list.
1802 Closes ticket 23910.
1803 - The directory authority "Longclaw" has changed its IP address.
1804 Closes ticket 23592.
1806 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1807 - Fix a timing-based assertion failure that could occur when the
1808 circuit out-of-memory handler freed a connection's output buffer.
1809 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1811 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1812 - Remove longclaw's IPv6 address, as it will soon change. Authority
1813 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1814 3/8 directory authorities with IPv6 addresses, but there are also
1815 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1817 o Minor features (geoip):
1818 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1821 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1822 - When a directory authority rejects a descriptor or extrainfo with
1823 a given digest, mark that digest as undownloadable, so that we do
1824 not attempt to download it again over and over. We previously
1825 tried to avoid downloading such descriptors by other means, but we
1826 didn't notice if we accidentally downloaded one anyway. This
1827 behavior became problematic in 0.2.7.2-alpha, when authorities
1828 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1831 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1832 - Clear the address when node_get_prim_orport() returns early.
1833 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1835 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1836 - When running as a Windows service, set the ID of the main thread
1837 correctly. Failure to do so made us fail to send log messages to
1838 the controller in 0.2.1.16-rc, slowed down controller event
1839 delivery in 0.2.7.3-rc and later, and crash with an assertion
1840 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1841 Patch and diagnosis from "Vort".
1844 Changes in version 0.3.0.12 - 2017-10-25
1845 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
1846 series, including a bugfix for a crash issue that had affected relays
1847 under memory pressure. It also adds a new directory authority, Bastet.
1849 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1850 2018. If you need a release with long-term support, please stick with
1851 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1853 o Directory authority changes:
1854 - Add "Bastet" as a ninth directory authority to the default list.
1855 Closes ticket 23910.
1856 - The directory authority "Longclaw" has changed its IP address.
1857 Closes ticket 23592.
1859 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1860 - Fix a timing-based assertion failure that could occur when the
1861 circuit out-of-memory handler freed a connection's output buffer.
1862 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1864 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1865 - Remove longclaw's IPv6 address, as it will soon change. Authority
1866 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1867 3/8 directory authorities with IPv6 addresses, but there are also
1868 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1870 o Minor features (geoip):
1871 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1874 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1875 - When a directory authority rejects a descriptor or extrainfo with
1876 a given digest, mark that digest as undownloadable, so that we do
1877 not attempt to download it again over and over. We previously
1878 tried to avoid downloading such descriptors by other means, but we
1879 didn't notice if we accidentally downloaded one anyway. This
1880 behavior became problematic in 0.2.7.2-alpha, when authorities
1881 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1884 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1885 - Avoid a possible double close of a circuit by the intro point on
1886 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1887 bugfix on 0.3.0.1-alpha.
1889 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1890 - Clear the address when node_get_prim_orport() returns early.
1891 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1893 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1894 - When running as a Windows service, set the ID of the main thread
1895 correctly. Failure to do so made us fail to send log messages to
1896 the controller in 0.2.1.16-rc, slowed down controller event
1897 delivery in 0.2.7.3-rc and later, and crash with an assertion
1898 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1899 Patch and diagnosis from "Vort".
1902 Changes in version 0.3.1.8 - 2017-10-25
1903 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
1904 It includes several bugfixes, including a bugfix for a crash issue
1905 that had affected relays under memory pressure. It also adds
1906 a new directory authority, Bastet.
1908 o Directory authority changes:
1909 - Add "Bastet" as a ninth directory authority to the default list.
1910 Closes ticket 23910.
1911 - The directory authority "Longclaw" has changed its IP address.
1912 Closes ticket 23592.
1914 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1915 - Fix a timing-based assertion failure that could occur when the
1916 circuit out-of-memory handler freed a connection's output buffer.
1917 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1919 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1920 - Remove longclaw's IPv6 address, as it will soon change. Authority
1921 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1922 3/8 directory authorities with IPv6 addresses, but there are also
1923 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1925 o Minor features (geoip):
1926 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1929 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
1930 - Fix a compilation warning when building with zstd support on
1931 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1932 and fixed by Andreas Stieger.
1934 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
1935 - Handle a pathological case when decompressing Zstandard data when
1936 the output buffer size is zero. Fixes bug 23551; bugfix
1939 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
1940 - Remove the length limit on HTTP status lines that authorities can
1941 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
1943 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1944 - Avoid a possible double close of a circuit by the intro point on
1945 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1946 bugfix on 0.3.0.1-alpha.
1948 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1949 - Clear the address when node_get_prim_orport() returns early.
1950 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1952 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
1953 - Fix additional channelpadding unit test failures by using mocked
1954 time instead of actual time for all tests. Fixes bug 23608; bugfix
1958 Changes in version 0.2.8.15 - 2017-09-18
1959 Tor 0.2.8.15 backports a collection of bugfixes from later
1962 Most significantly, it includes a fix for TROVE-2017-008, a
1963 security bug that affects hidden services running with the
1964 SafeLogging option disabled. For more information, see
1965 https://trac.torproject.org/projects/tor/ticket/23490
1967 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
1968 2018. We suggest that you upgrade to the latest stable release if
1969 possible. If you can't, we recommend that you upgrade at least to
1970 0.2.9, which will be supported until 2020.
1972 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1973 - Avoid an assertion failure bug affecting our implementation of
1974 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1975 handling of "0xx" differs from what we had expected. Fixes bug
1976 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1979 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1982 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1983 - Backport a fix for an "unused variable" warning that appeared
1984 in some versions of mingw. Fixes bug 22838; bugfix on
1987 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1988 - Fix a memset() off the end of an array when packing cells. This
1989 bug should be harmless in practice, since the corrupted bytes are
1990 still in the same structure, and are always padding bytes,
1991 ignored, or immediately overwritten, depending on compiler
1992 behavior. Nevertheless, because the memset()'s purpose is to make
1993 sure that any other cell-handling bugs can't expose bytes to the
1994 network, we need to fix it. Fixes bug 22737; bugfix on
1995 0.2.4.11-alpha. Fixes CID 1401591.
1997 o Build features (backport from 0.3.1.5-alpha):
1998 - Tor's repository now includes a Travis Continuous Integration (CI)
1999 configuration file (.travis.yml). This is meant to help new
2000 developers and contributors who fork Tor to a Github repository be
2001 better able to test their changes, and understand what we expect
2002 to pass. To use this new build feature, you must fork Tor to your
2003 Github account, then go into the "Integrations" menu in the
2004 repository settings for your fork and enable Travis, then push
2005 your changes. Closes ticket 22636.
2008 Changes in version 0.2.9.12 - 2017-09-18
2009 Tor 0.2.9.12 backports a collection of bugfixes from later
2012 Most significantly, it includes a fix for TROVE-2017-008, a
2013 security bug that affects hidden services running with the
2014 SafeLogging option disabled. For more information, see
2015 https://trac.torproject.org/projects/tor/ticket/23490
2017 o Major features (security, backport from 0.3.0.2-alpha):
2018 - Change the algorithm used to decide DNS TTLs on client and server
2019 side, to better resist DNS-based correlation attacks like the
2020 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2021 Feamster. Now relays only return one of two possible DNS TTL
2022 values, and clients are willing to believe DNS TTL values up to 3
2023 hours long. Closes ticket 19769.
2025 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
2026 - Fix a rare crash when sending a begin cell on a circuit whose
2027 linked directory connection had already been closed. Fixes bug
2028 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
2030 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
2031 - Fix a bug that prevented exit nodes from caching DNS records for
2032 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2034 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2035 - Fix a typo that had prevented TPROXY-based transparent proxying
2036 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2037 Patch from "d4fq0fQAgoJ".
2039 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2040 - Avoid an assertion failure bug affecting our implementation of
2041 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2042 handling of "0xx" differs from what we had expected. Fixes bug
2043 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2045 o Minor features (code style, backport from 0.3.1.3-alpha):
2046 - Add "Falls through" comments to our codebase, in order to silence
2047 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2048 Stieger. Closes ticket 22446.
2050 o Minor features (geoip):
2051 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2054 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
2055 - Roll over monthly accounting at the configured hour and minute,
2056 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2057 Found by Andrey Karpov with PVS-Studio.
2059 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
2060 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2061 bugfix on 0.2.8.1-alpha.
2062 - Fix warnings when building with libscrypt and openssl scrypt support
2063 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2064 - When building with certain versions the mingw C header files, avoid
2065 float-conversion warnings when calling the C functions isfinite(),
2066 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
2068 o Minor bugfixes (compilation, backport from 0.3.1.7):
2069 - Avoid compiler warnings in the unit tests for running tor_sscanf()
2070 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2072 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2073 - Backport a fix for an "unused variable" warning that appeared
2074 in some versions of mingw. Fixes bug 22838; bugfix on
2077 o Minor bugfixes (controller, backport from 0.3.1.7):
2078 - Do not crash when receiving a HSPOST command with an empty body.
2079 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2080 - Do not crash when receiving a POSTDESCRIPTOR command with an
2081 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2083 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2084 - Avoid Coverity build warnings related to our BUG() macro. By
2085 default, Coverity treats BUG() as the Linux kernel does: an
2086 instant abort(). We need to override that so our BUG() macro
2087 doesn't prevent Coverity from analyzing functions that use it.
2088 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2090 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2091 - Fix a memset() off the end of an array when packing cells. This
2092 bug should be harmless in practice, since the corrupted bytes are
2093 still in the same structure, and are always padding bytes,
2094 ignored, or immediately overwritten, depending on compiler
2095 behavior. Nevertheless, because the memset()'s purpose is to make
2096 sure that any other cell-handling bugs can't expose bytes to the
2097 network, we need to fix it. Fixes bug 22737; bugfix on
2098 0.2.4.11-alpha. Fixes CID 1401591.
2100 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2101 - When setting the maximum number of connections allowed by the OS,
2102 always allow some extra file descriptors for other files. Fixes
2103 bug 22797; bugfix on 0.2.0.10-alpha.
2105 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2106 - Avoid a sandbox failure when trying to re-bind to a socket and
2107 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2109 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2110 - Permit the fchmod system call, to avoid crashing on startup when
2111 starting with the seccomp2 sandbox and an unexpected set of
2112 permissions on the data directory or its contents. Fixes bug
2113 22516; bugfix on 0.2.5.4-alpha.
2115 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
2116 - Avoid a double-marked-circuit warning that could happen when we
2117 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
2120 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2121 - Reject version numbers with non-numeric prefixes (such as +, -, or
2122 whitespace). Disallowing whitespace prevents differential version
2123 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2124 and part of 21508; bugfix on 0.0.8pre1.
2126 o Build features (backport from 0.3.1.5-alpha):
2127 - Tor's repository now includes a Travis Continuous Integration (CI)
2128 configuration file (.travis.yml). This is meant to help new
2129 developers and contributors who fork Tor to a Github repository be
2130 better able to test their changes, and understand what we expect
2131 to pass. To use this new build feature, you must fork Tor to your
2132 Github account, then go into the "Integrations" menu in the
2133 repository settings for your fork and enable Travis, then push
2134 your changes. Closes ticket 22636.
2137 Changes in version 0.3.0.11 - 2017-09-18
2138 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
2141 Most significantly, it includes a fix for TROVE-2017-008, a
2142 security bug that affects hidden services running with the
2143 SafeLogging option disabled. For more information, see
2144 https://trac.torproject.org/projects/tor/ticket/23490
2146 o Minor features (code style, backport from 0.3.1.7):
2147 - Add "Falls through" comments to our codebase, in order to silence
2148 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2149 Stieger. Closes ticket 22446.
2152 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2155 o Minor bugfixes (compilation, backport from 0.3.1.7):
2156 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2157 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2159 o Minor bugfixes (controller, backport from 0.3.1.7):
2160 - Do not crash when receiving a HSPOST command with an empty body.
2161 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2162 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2163 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2165 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2166 - When setting the maximum number of connections allowed by the OS,
2167 always allow some extra file descriptors for other files. Fixes
2168 bug 22797; bugfix on 0.2.0.10-alpha.
2170 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
2171 - Remove a forgotten debugging message when an introduction point
2172 successfully establishes a hidden service prop224 circuit with
2174 - Change three other log_warn() for an introduction point to
2175 protocol warnings, because they can be failure from the network
2176 and are not relevant to the operator. Fixes bug 23078; bugfix on
2177 0.3.0.1-alpha and 0.3.0.2-alpha.
2180 Changes in version 0.3.1.7 - 2017-09-18
2181 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
2183 With the 0.3.1 series, Tor now serves and downloads directory
2184 information in more compact formats, to save on bandwidth overhead. It
2185 also contains a new padding system to resist netflow-based traffic
2186 analysis, and experimental support for building parts of Tor in Rust
2187 (though no parts of Tor are in Rust yet). There are also numerous
2188 small features, bugfixes on earlier release series, and groundwork for
2189 the hidden services revamp of 0.3.2.
2191 This release also includes a fix for TROVE-2017-008, a security bug
2192 that affects hidden services running with the SafeLogging option
2193 disabled. For more information, see
2194 https://trac.torproject.org/projects/tor/ticket/23490
2196 Per our stable release policy, we plan to support each stable release
2197 series for at least the next nine months, or for three months after
2198 the first stable release of the next series: whichever is longer. If
2199 you need a release with long-term support, we recommend that you stay
2200 with the 0.2.9 series.
2202 Below is a list of the changes since 0.3.0. For a list of all
2203 changes since 0.3.1.6-rc, see the ChangeLog file.
2206 - To build with zstd and lzma support, Tor now requires the
2207 pkg-config tool at build time.
2209 o Major bugfixes (security, hidden services, loggging):
2210 - Fix a bug where we could log uninitialized stack when a certain
2211 hidden service error occurred while SafeLogging was disabled.
2212 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
2213 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
2215 o Major features (build system, continuous integration):
2216 - Tor's repository now includes a Travis Continuous Integration (CI)
2217 configuration file (.travis.yml). This is meant to help new
2218 developers and contributors who fork Tor to a Github repository be
2219 better able to test their changes, and understand what we expect
2220 to pass. To use this new build feature, you must fork Tor to your
2221 Github account, then go into the "Integrations" menu in the
2222 repository settings for your fork and enable Travis, then push
2223 your changes. Closes ticket 22636.
2225 o Major features (directory protocol):
2226 - Tor relays and authorities can now serve clients an abbreviated
2227 version of the consensus document, containing only the changes
2228 since an older consensus document that the client holds. Clients
2229 now request these documents when available. When both client and
2230 server use this new protocol, they will use far less bandwidth (up
2231 to 94% less) to keep the client's consensus up-to-date. Implements
2232 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2233 - Tor can now compress directory traffic with lzma or with zstd
2234 compression algorithms, which can deliver better bandwidth
2235 performance. Because lzma is computationally expensive, it's only
2236 used for documents that can be compressed once and served many
2237 times. Support for these algorithms requires that tor is built
2238 with the libzstd and/or liblzma libraries available. Implements
2239 proposal 278; closes ticket 21662.
2240 - Relays now perform the more expensive compression operations, and
2241 consensus diff generation, in worker threads. This separation
2242 avoids delaying the main thread when a new consensus arrives.
2244 o Major features (experimental):
2245 - Tor can now build modules written in Rust. To turn this on, pass
2246 the "--enable-rust" flag to the configure script. It's not time to
2247 get excited yet: currently, there is no actual Rust functionality
2248 beyond some simple glue code, and a notice at startup to tell you
2249 that Rust is running. Still, we hope that programmers and
2250 packagers will try building Tor with Rust support, so that we can
2251 find issues and solve portability problems. Closes ticket 22106.
2253 o Major features (traffic analysis resistance):
2254 - Connections between clients and relays now send a padding cell in
2255 each direction every 1.5 to 9.5 seconds (tunable via consensus
2256 parameters). This padding will not resist specialized
2257 eavesdroppers, but it should be enough to make many ISPs' routine
2258 network flow logging less useful in traffic analysis against
2261 Padding is negotiated using Tor's link protocol, so both relays
2262 and clients must upgrade for this to take effect. Clients may
2263 still send padding despite the relay's version by setting
2264 ConnectionPadding 1 in torrc, and may disable padding by setting
2265 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2266 users with the torrc option ReducedConnectionPadding. Implements
2267 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2268 - Relays will publish 24 hour totals of padding and non-padding cell
2269 counts to their extra-info descriptors, unless PaddingStatistics 0
2270 is set in torrc. These 24 hour totals are also rounded to
2273 o Major bugfixes (hidden service, relay, security):
2274 - Fix a remotely triggerable assertion failure when a hidden service
2275 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2276 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2277 - Fix a remotely triggerable assertion failure caused by receiving a
2278 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2279 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2282 o Major bugfixes (path selection, security):
2283 - When choosing which guard to use for a circuit, avoid the exit's
2284 family along with the exit itself. Previously, the new guard
2285 selection logic avoided the exit, but did not consider its family.
2286 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2287 006 and CVE-2017-0377.
2289 o Major bugfixes (connection usage):
2290 - We use NETINFO cells to try to determine if both relays involved
2291 in a connection will agree on the canonical status of that
2292 connection. We prefer the connections where this is the case for
2293 extend cells, and try to close connections where relays disagree
2294 on their canonical status early. Also, we now prefer the oldest
2295 valid connection for extend cells. These two changes should reduce
2296 the number of long-term connections that are kept open between
2297 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2298 - Relays now log hourly statistics (look for
2299 "channel_check_for_duplicates" lines) on the total number of
2300 connections to other relays. If the number of connections per
2301 relay is unexpectedly large, this log message is at notice level.
2302 Otherwise it is at info.
2304 o Major bugfixes (entry guards):
2305 - When starting with an old consensus, do not add new entry guards
2306 unless the consensus is "reasonably live" (under 1 day old). Fixes
2307 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2308 - Don't block bootstrapping when a primary bridge is offline and we
2309 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2310 21969; bugfix on 0.3.0.3-alpha.
2312 o Major bugfixes (linux TPROXY support):
2313 - Fix a typo that had prevented TPROXY-based transparent proxying
2314 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2315 Patch from "d4fq0fQAgoJ".
2317 o Major bugfixes (openbsd, denial-of-service):
2318 - Avoid an assertion failure bug affecting our implementation of
2319 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2320 handling of "0xx" differs from what we had expected. Fixes bug
2321 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2323 o Major bugfixes (relay, link handshake):
2324 - When performing the v3 link handshake on a TLS connection, report
2325 that we have the x509 certificate that we actually used on that
2326 connection, even if we have changed certificates since that
2327 connection was first opened. Previously, we would claim to have
2328 used our most recent x509 link certificate, which would sometimes
2329 make the link handshake fail. Fixes one case of bug 22460; bugfix
2332 o Major bugfixes (relays, key management):
2333 - Regenerate link and authentication certificates whenever the key
2334 that signs them changes; also, regenerate link certificates
2335 whenever the signed key changes. Previously, these processes were
2336 only weakly coupled, and we relays could (for minutes to hours)
2337 wind up with an inconsistent set of keys and certificates, which
2338 other relays would not accept. Fixes two cases of bug 22460;
2339 bugfix on 0.3.0.1-alpha.
2340 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2341 send the certificate that matches the x509 certificate that we
2342 used on the TLS connection. Previously, there was a race condition
2343 if the TLS context rotated after we began the TLS handshake but
2344 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2347 o Minor features (security, windows):
2348 - Enable a couple of pieces of Windows hardening: one
2349 (HeapEnableTerminationOnCorruption) that has been on-by-default
2350 since Windows 8, and unavailable before Windows 7; and one
2351 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2352 affect us, but shouldn't do any harm. Closes ticket 21953.
2354 o Minor features (bridge authority):
2355 - Add "fingerprint" lines to the networkstatus-bridges file produced
2356 by bridge authorities. Closes ticket 22207.
2358 o Minor features (code style):
2359 - Add "Falls through" comments to our codebase, in order to silence
2360 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2361 Stieger. Closes ticket 22446.
2363 o Minor features (config options):
2364 - Allow "%include" directives in torrc configuration files. These
2365 directives import the settings from other files, or from all the
2366 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
2367 - Make SAVECONF return an error when overwriting a torrc that has
2368 includes. Using SAVECONF with the FORCE option will allow it to
2369 overwrite torrc even if includes are used. Related to ticket 1922.
2370 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
2371 will work without the FORCE option. Related to ticket 1922.
2373 o Minor features (controller):
2374 - Warn the first time that a controller requests data in the long-
2375 deprecated 'GETINFO network-status' format. Closes ticket 21703.
2377 o Minor features (defaults):
2378 - The default value for UseCreateFast is now 0: clients which
2379 haven't yet received a consensus document will now use a proper
2380 ntor handshake to talk to their directory servers whenever they
2381 can. Closes ticket 21407.
2382 - Onion key rotation and expiry intervals are now defined as a
2383 network consensus parameter, per proposal 274. The default
2384 lifetime of an onion key is increased from 7 to 28 days. Old onion
2385 keys will expire after 7 days by default. This change will make
2386 consensus diffs much smaller, and save significant bandwidth.
2387 Closes ticket 21641.
2389 o Minor features (defensive programming):
2390 - Create a pair of consensus parameters, nf_pad_tor2web and
2391 nf_pad_single_onion, to disable netflow padding in the consensus
2392 for non-anonymous connections in case the overhead is high. Closes
2395 o Minor features (diagnostic):
2396 - Add a stack trace to the bug warnings that can be logged when
2397 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
2398 attempt for bug 23105.
2399 - Add logging messages to try to diagnose a rare bug that seems to
2400 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
2401 think this is happening because of incorrect system clocks, but
2402 we'd like to know for certain. Diagnostic for bug 22466.
2403 - Avoid an assertion failure, and log a better error message, when
2404 unable to remove a file from the consensus cache on Windows.
2405 Attempts to mitigate and diagnose bug 22752.
2407 o Minor features (directory authority):
2408 - Improve the message that authorities report to relays that present
2409 RSA/Ed25519 keypairs that conflict with previously pinned keys.
2410 Closes ticket 22348.
2412 o Minor features (directory cache, consensus diff):
2413 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
2414 operators with low-resource environments to adjust the number of
2415 consensuses they'll store and generate diffs from. Most cache
2416 operators should leave it unchanged. Helps to work around
2419 o Minor features (fallback directory list):
2420 - Update the fallback directory mirror whitelist and blacklist based
2421 on operator emails. Closes task 21121.
2422 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2423 December 2016 (of which ~126 were still functional) with a list of
2424 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2425 2017. Resolves ticket 21564.
2427 o Minor features (geoip):
2428 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2431 o Minor features (hidden services, logging):
2432 - Log a message when a hidden service descriptor has fewer
2433 introduction points than specified in
2434 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
2435 - Log a message when a hidden service reaches its introduction point
2436 circuit limit, and when that limit is reset. Follow up to ticket
2437 21594; closes ticket 21622.
2438 - Warn user if multiple entries in EntryNodes and at least one
2439 HiddenService are used together. Pinning EntryNodes along with a
2440 hidden service can be possibly harmful; for instance see ticket
2441 14917 or 21155. Closes ticket 21155.
2443 o Minor features (linux seccomp2 sandbox):
2444 - We now have a document storage backend compatible with the Linux
2445 seccomp2 sandbox. This backend is used for consensus documents and
2446 diffs between them; in the long term, we'd like to use it for
2447 unparseable directory material too. Closes ticket 21645
2448 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
2449 from 1MB to 16MB. This was necessary with the glibc allocator in
2450 order to allow worker threads to allocate more memory -- which in
2451 turn is necessary because of our new use of worker threads for
2452 compression. Closes ticket 22096.
2454 o Minor features (logging):
2455 - Log files are no longer created world-readable by default.
2456 (Previously, most distributors would store the logs in a non-
2457 world-readable location to prevent inappropriate access. This
2458 change is an extra precaution.) Closes ticket 21729; patch
2461 o Minor features (performance):
2462 - Our Keccak (SHA-3) implementation now accesses memory more
2463 efficiently, especially on little-endian systems. Closes
2465 - Add an O(1) implementation of channel_find_by_global_id(), to
2466 speed some controller functions.
2468 o Minor features (relay, configuration):
2469 - The MyFamily option may now be repeated as many times as desired,
2470 for relays that want to configure large families. Closes ticket
2471 4998; patch by Daniel Pinto.
2473 o Minor features (relay, performance):
2474 - Always start relays with at least two worker threads, to prevent
2475 priority inversion on slow tasks. Part of the fix for bug 22883.
2476 - Allow background work to be queued with different priorities, so
2477 that a big pile of slow low-priority jobs will not starve out
2478 higher priority jobs. This lays the groundwork for a fix for
2481 o Minor features (safety):
2482 - Add an explicit check to extrainfo_parse_entry_from_string() for
2483 NULL inputs. We don't believe this can actually happen, but it may
2484 help silence a warning from the Clang analyzer. Closes
2487 o Minor features (testing):
2488 - Add more tests for compression backend initialization. Closes
2490 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
2491 When Tor is compiled with this option, we disable a number of
2492 redundant memory-safety failsafes that are intended to stop bugs
2493 from becoming security issues. This makes it easier to hunt for
2494 bugs that would be security issues without the failsafes turned
2495 on. Closes ticket 21439.
2496 - Add a general event-tracing instrumentation support to Tor. This
2497 subsystem will enable developers and researchers to add fine-
2498 grained instrumentation to their Tor instances, for use when
2499 examining Tor network performance issues. There are no trace
2500 events yet, and event-tracing is off by default unless enabled at
2501 compile time. Implements ticket 13802.
2502 - Improve our version parsing tests: add tests for typical version
2503 components, add tests for invalid versions, including numeric
2504 range and non-numeric prefixes. Unit tests 21278, 21450, and
2505 21507. Partially implements 21470.
2507 o Minor bugfixes (bandwidth accounting):
2508 - Roll over monthly accounting at the configured hour and minute,
2509 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2510 Found by Andrey Karpov with PVS-Studio.
2512 o Minor bugfixes (code correctness):
2513 - Accurately identify client connections by their lack of peer
2514 authentication. This means that we bail out earlier if asked to
2515 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
2518 o Minor bugfixes (compilation warnings):
2519 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
2520 22915; bugfix on 0.2.8.1-alpha.
2521 - Fix warnings when building with libscrypt and openssl scrypt
2522 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2523 - When building with certain versions of the mingw C header files,
2524 avoid float-conversion warnings when calling the C functions
2525 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2528 o Minor bugfixes (compilation):
2529 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2530 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2532 o Minor bugfixes (compression):
2533 - When spooling compressed data to an output buffer, don't try to
2534 spool more data when there is no more data to spool and we are not
2535 trying to flush the input. Previously, we would sometimes launch
2536 compression requests with nothing to do, which interferes with our
2537 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
2539 o Minor bugfixes (configuration):
2540 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2541 bug 22252; bugfix on 0.2.9.3-alpha.
2543 o Minor bugfixes (connection lifespan):
2544 - Allow more control over how long TLS connections are kept open:
2545 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
2546 single option called CircuitsAvailableTimeout. Also, allow the
2547 consensus to control the default values for both this preference
2548 and the lifespan of relay-to-relay connections. Fixes bug 17592;
2549 bugfix on 0.2.5.5-alpha.
2550 - Increase the initial circuit build timeout testing frequency, to
2551 help ensure that ReducedConnectionPadding clients finish learning
2552 a timeout before their orconn would expire. The initial testing
2553 rate was set back in the days of TAP and before the Tor Browser
2554 updater, when we had to be much more careful about new clients
2555 making lots of circuits. With this change, a circuit build timeout
2556 is learned in about 15-20 minutes, instead of 100-120 minutes.
2558 o Minor bugfixes (controller):
2559 - Do not crash when receiving a HSPOST command with an empty body.
2560 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2561 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2562 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2563 - GETINFO onions/current and onions/detached no longer respond with
2564 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
2565 - Trigger HS descriptor events on the control port when the client
2566 fails to pick a hidden service directory for a hidden service.
2567 This can happen if all the hidden service directories are in
2568 ExcludeNodes, or they have all been queried within the last 15
2569 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
2571 o Minor bugfixes (correctness):
2572 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2573 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2575 o Minor bugfixes (coverity build support):
2576 - Avoid Coverity build warnings related to our BUG() macro. By
2577 default, Coverity treats BUG() as the Linux kernel does: an
2578 instant abort(). We need to override that so our BUG() macro
2579 doesn't prevent Coverity from analyzing functions that use it.
2580 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2582 o Minor bugfixes (defensive programming):
2583 - Detect and break out of infinite loops in our compression code. We
2584 don't think that any such loops exist now, but it's best to be
2585 safe. Closes ticket 22672.
2586 - Fix a memset() off the end of an array when packing cells. This
2587 bug should be harmless in practice, since the corrupted bytes are
2588 still in the same structure, and are always padding bytes,
2589 ignored, or immediately overwritten, depending on compiler
2590 behavior. Nevertheless, because the memset()'s purpose is to make
2591 sure that any other cell-handling bugs can't expose bytes to the
2592 network, we need to fix it. Fixes bug 22737; bugfix on
2593 0.2.4.11-alpha. Fixes CID 1401591.
2595 o Minor bugfixes (directory authority):
2596 - When a directory authority rejects a descriptor or extrainfo with
2597 a given digest, mark that digest as undownloadable, so that we do
2598 not attempt to download it again over and over. We previously
2599 tried to avoid downloading such descriptors by other means, but we
2600 didn't notice if we accidentally downloaded one anyway. This
2601 behavior became problematic in 0.2.7.2-alpha, when authorities
2602 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2604 - When rejecting a router descriptor for running an obsolete version
2605 of Tor without ntor support, warn about the obsolete tor version,
2606 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2607 - Prevent the shared randomness subsystem from asserting when
2608 initialized by a bridge authority with an incomplete configuration
2609 file. Fixes bug 21586; bugfix on 0.2.9.8.
2611 o Minor bugfixes (error reporting, windows):
2612 - When formatting Windows error messages, use the English format to
2613 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2616 o Minor bugfixes (exit-side DNS):
2617 - Fix an untriggerable assertion that checked the output of a
2618 libevent DNS error, so that the assertion actually behaves as
2619 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
2620 Karpov using PVS-Studio.
2622 o Minor bugfixes (fallback directories):
2623 - Make the usage example in updateFallbackDirs.py actually work, and
2624 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
2625 - Decrease the guard flag average required to be a fallback. This
2626 allows us to keep relays that have their guard flag removed when
2627 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2628 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
2629 bugfix on 0.2.8.1-alpha.
2630 - Make sure fallback directory mirrors have the same address, port,
2631 and relay identity key for at least 30 days before they are
2632 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2634 o Minor bugfixes (file limits, osx):
2635 - When setting the maximum number of connections allowed by the OS,
2636 always allow some extra file descriptors for other files. Fixes
2637 bug 22797; bugfix on 0.2.0.10-alpha.
2639 o Minor bugfixes (hidden services):
2640 - Increase the number of circuits that a service is allowed to
2641 open over a specific period of time. The value was lower than it
2642 should be (8 vs 12) in the normal case of 3 introduction points.
2643 Fixes bug 22159; bugfix on 0.3.0.5-rc.
2644 - Fix a BUG warning during HSv3 descriptor decoding that could be
2645 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
2646 on 0.3.0.1-alpha. Bug found by "haxxpop".
2647 - Stop printing a cryptic warning when a hidden service gets a
2648 request to connect to a virtual port that it hasn't configured.
2649 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
2650 - Simplify hidden service descriptor creation by using an existing
2651 flag to check if an introduction point is established. Fixes bug
2652 21599; bugfix on 0.2.7.2-alpha.
2654 o Minor bugfixes (link handshake):
2655 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2656 months, and regenerate it when it is within one month of expiring.
2657 Previously, we had generated this certificate at startup with a
2658 ten-year lifetime, but that could lead to weird behavior when Tor
2659 was started with a grossly inaccurate clock. Mitigates bug 22466;
2660 mitigation on 0.3.0.1-alpha.
2662 o Minor bugfixes (linux seccomp2 sandbox):
2663 - Avoid a sandbox failure when trying to re-bind to a socket and
2664 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2665 - Permit the fchmod system call, to avoid crashing on startup when
2666 starting with the seccomp2 sandbox and an unexpected set of
2667 permissions on the data directory or its contents. Fixes bug
2668 22516; bugfix on 0.2.5.4-alpha.
2670 o Minor bugfixes (logging):
2671 - When decompressing, do not warn if we fail to decompress using a
2672 compression method that we merely guessed. Fixes part of bug
2673 22670; bugfix on 0.1.1.14-alpha.
2674 - When decompressing, treat mismatch between content-encoding and
2675 actual compression type as a protocol warning. Fixes part of bug
2676 22670; bugfix on 0.1.1.9-alpha.
2677 - Downgrade "assigned_to_cpuworker failed" message to info-level
2678 severity. In every case that can reach it, either a better warning
2679 has already been logged, or no warning is warranted. Fixes bug
2680 22356; bugfix on 0.2.6.3-alpha.
2681 - Log a better message when a directory authority replies to an
2682 upload with an unexpected status code. Fixes bug 11121; bugfix
2684 - Downgrade a log statement about unexpected relay cells from "bug"
2685 to "protocol warning", because there is at least one use case
2686 where it can be triggered by a buggy tor implementation. Fixes bug
2687 21293; bugfix on 0.1.1.14-alpha.
2689 o Minor bugfixes (logging, relay):
2690 - Remove a forgotten debugging message when an introduction point
2691 successfully establishes a hidden service prop224 circuit with
2693 - Change three other log_warn() for an introduction point to
2694 protocol warnings, because they can be failure from the network
2695 and are not relevant to the operator. Fixes bug 23078; bugfix on
2696 0.3.0.1-alpha and 0.3.0.2-alpha.
2698 o Minor bugfixes (relay):
2699 - Inform the geoip and rephist modules about all requests, even on
2700 relays that are only fetching microdescriptors. Fixes a bug
2701 related to 21585; bugfix on 0.3.0.1-alpha.
2703 o Minor bugfixes (memory leaks):
2704 - Fix a small memory leak at exit from the backtrace handler code.
2705 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
2706 - When directory authorities reject a router descriptor due to
2707 keypinning, free the router descriptor rather than leaking the
2708 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2709 - Fix a small memory leak when validating a configuration that uses
2710 two or more AF_UNIX sockets for the same port type. Fixes bug
2711 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2713 o Minor bugfixes (process behavior):
2714 - When exiting because of an error, always exit with a nonzero exit
2715 status. Previously, we would fail to report an error in our exit
2716 status in cases related to __OwningControllerProcess failure,
2717 lockfile contention, and Ed25519 key initialization. Fixes bug
2718 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
2719 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
2722 o Minor bugfixes (robustness, error handling):
2723 - Improve our handling of the cases where OpenSSL encounters a
2724 memory error while encoding keys and certificates. We haven't
2725 observed these errors in the wild, but if they do happen, we now
2726 detect and respond better. Fixes bug 19418; bugfix on all versions
2727 of Tor. Reported by Guido Vranken.
2729 o Minor bugfixes (testing):
2730 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2731 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2732 - Use unbuffered I/O for utility functions around the
2733 process_handle_t type. This fixes unit test failures reported on
2734 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
2735 - Make display of captured unit test log messages consistent. Fixes
2736 bug 21510; bugfix on 0.2.9.3-alpha.
2737 - Make test-network.sh always call chutney's test-network.sh.
2738 Previously, this only worked on systems which had bash installed,
2739 due to some bash-specific code in the script. Fixes bug 19699;
2740 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
2741 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2742 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2743 - The unit tests now pass on systems where localhost is misconfigured
2744 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
2747 o Minor bugfixes (voting consistency):
2748 - Reject version numbers with non-numeric prefixes (such as +, -, or
2749 whitespace). Disallowing whitespace prevents differential version
2750 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2751 and part of 21508; bugfix on 0.0.8pre1.
2753 o Minor bugfixes (Windows service):
2754 - When running as a Windows service, set the ID of the main thread
2755 correctly. Failure to do so made us fail to send log messages to
2756 the controller in 0.2.1.16-rc, slowed down controller event
2757 delivery in 0.2.7.3-rc and later, and crash with an assertion
2758 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2759 Patch and diagnosis from "Vort".
2761 o Minor bugfixes (windows, relay):
2762 - Resolve "Failure from drain_fd: No error" warnings on Windows
2763 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
2765 o Code simplification and refactoring:
2766 - Break up the 630-line function connection_dir_client_reached_eof()
2767 into a dozen smaller functions. This change should help
2768 maintainability and readability of the client directory code.
2769 - Isolate our use of the openssl headers so that they are only
2770 included from our crypto wrapper modules, and from tests that
2771 examine those modules' internals. Closes ticket 21841.
2772 - Simplify our API to launch directory requests, making it more
2773 extensible and less error-prone. Now it's easier to add extra
2774 headers to directory requests. Closes ticket 21646.
2775 - Our base64 decoding functions no longer overestimate the output
2776 space that they need when parsing unpadded inputs. Closes
2778 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
2779 Resolves ticket 22213.
2780 - The logic that directory caches use to spool request to clients,
2781 serving them one part at a time so as not to allocate too much
2782 memory, has been refactored for consistency. Previously there was
2783 a separate spooling implementation per type of spoolable data. Now
2784 there is one common spooling implementation, with extensible data
2785 types. Closes ticket 21651.
2786 - Tor's compression module now supports multiple backends. Part of
2787 the implementation for proposal 278; closes ticket 21663.
2790 - Add a manpage description for the key-pinning-journal file. Closes
2792 - Correctly note that bandwidth accounting values are stored in the
2793 state file, and the bw_accounting file is now obsolete. Closes
2795 - Document more of the files in the Tor data directory, including
2796 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
2797 approved-routers, sr-random, and diff-cache. Found while fixing
2799 - Clarify the manpage for the (deprecated) torify script. Closes
2801 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
2802 Closes ticket 21873.
2803 - Correct documentation about the default DataDirectory value.
2804 Closes ticket 21151.
2805 - Document the default behavior of NumEntryGuards and
2806 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
2808 - Document key=value pluggable transport arguments for Bridge lines
2809 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
2810 - Note that bandwidth-limiting options don't affect TCP headers or
2811 DNS. Closes ticket 17170.
2813 o Removed features (configuration options, all in ticket 22060):
2814 - These configuration options are now marked Obsolete, and no longer
2815 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
2816 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
2817 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
2818 in 0.2.9.2-alpha and have now been removed. The previous default
2819 behavior is now always chosen; the previous (less secure) non-
2820 default behavior is now unavailable.
2821 - CloseHSClientCircuitsImmediatelyOnTimeout and
2822 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
2823 0.2.9.2-alpha and now have been removed. HS circuits never close
2824 on circuit build timeout; they have a longer timeout period.
2825 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
2826 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
2827 (and others) to configure listen-only and advertise-only addresses.
2829 o Removed features (tools):
2830 - We've removed the tor-checkkey tool from src/tools. Long ago, we
2831 used it to help people detect RSA keys that were generated by
2832 versions of Debian affected by CVE-2008-0166. But those keys have
2833 been out of circulation for ages, and this tool is no longer
2834 required. Closes ticket 21842.
2837 Changes in version 0.3.0.10 - 2017-08-02
2838 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
2839 from the current Tor alpha series. OpenBSD users and TPROXY users
2840 should upgrade; others are probably okay sticking with 0.3.0.9.
2842 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
2843 - Tor's repository now includes a Travis Continuous Integration (CI)
2844 configuration file (.travis.yml). This is meant to help new
2845 developers and contributors who fork Tor to a Github repository be
2846 better able to test their changes, and understand what we expect
2847 to pass. To use this new build feature, you must fork Tor to your
2848 Github account, then go into the "Integrations" menu in the
2849 repository settings for your fork and enable Travis, then push
2850 your changes. Closes ticket 22636.
2852 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2853 - Fix a typo that had prevented TPROXY-based transparent proxying
2854 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2855 Patch from "d4fq0fQAgoJ".
2857 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2858 - Avoid an assertion failure bug affecting our implementation of
2859 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2860 handling of "0xbar" differs from what we had expected. Fixes bug
2861 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2863 o Minor features (backport from 0.3.1.5-alpha):
2864 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2867 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
2868 - Roll over monthly accounting at the configured hour and minute,
2869 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2870 Found by Andrey Karpov with PVS-Studio.
2872 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
2873 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2874 bugfix on 0.2.8.1-alpha.
2875 - Fix warnings when building with libscrypt and openssl scrypt
2876 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2877 - When building with certain versions of the mingw C header files,
2878 avoid float-conversion warnings when calling the C functions
2879 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2882 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2883 - Backport a fix for an "unused variable" warning that appeared
2884 in some versions of mingw. Fixes bug 22838; bugfix on
2887 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2888 - Avoid Coverity build warnings related to our BUG() macro. By
2889 default, Coverity treats BUG() as the Linux kernel does: an
2890 instant abort(). We need to override that so our BUG() macro
2891 doesn't prevent Coverity from analyzing functions that use it.
2892 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2894 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
2895 - When rejecting a router descriptor for running an obsolete version
2896 of Tor without ntor support, warn about the obsolete tor version,
2897 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2899 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2900 - Avoid a sandbox failure when trying to re-bind to a socket and
2901 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2903 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
2904 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2905 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2908 Changes in version 0.3.0.9 - 2017-06-29
2909 Tor 0.3.0.9 fixes a path selection bug that would allow a client
2910 to use a guard that was in the same network family as a chosen exit
2911 relay. This is a security regression; all clients running earlier
2912 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
2915 This release also backports several other bugfixes from the 0.3.1.x
2918 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
2919 - When choosing which guard to use for a circuit, avoid the exit's
2920 family along with the exit itself. Previously, the new guard
2921 selection logic avoided the exit, but did not consider its family.
2922 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2923 006 and CVE-2017-0377.
2925 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
2926 - Don't block bootstrapping when a primary bridge is offline and we
2927 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2928 21969; bugfix on 0.3.0.3-alpha.
2930 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
2931 - When starting with an old consensus, do not add new entry guards
2932 unless the consensus is "reasonably live" (under 1 day old). Fixes
2933 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2935 o Minor features (geoip):
2936 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2939 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2940 - Reject version numbers with non-numeric prefixes (such as +, -, or
2941 whitespace). Disallowing whitespace prevents differential version
2942 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2943 and part of 21508; bugfix on 0.0.8pre1.
2945 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2946 - Permit the fchmod system call, to avoid crashing on startup when
2947 starting with the seccomp2 sandbox and an unexpected set of
2948 permissions on the data directory or its contents. Fixes bug
2949 22516; bugfix on 0.2.5.4-alpha.
2951 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
2952 - Fix a memset() off the end of an array when packing cells. This
2953 bug should be harmless in practice, since the corrupted bytes are
2954 still in the same structure, and are always padding bytes,
2955 ignored, or immediately overwritten, depending on compiler
2956 behavior. Nevertheless, because the memset()'s purpose is to make
2957 sure that any other cell-handling bugs can't expose bytes to the
2958 network, we need to fix it. Fixes bug 22737; bugfix on
2959 0.2.4.11-alpha. Fixes CID 1401591.
2962 Changes in version 0.3.0.8 - 2017-06-08
2963 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
2964 remotely crash a hidden service with an assertion failure. Anyone
2965 running a hidden service should upgrade to this version, or to some
2966 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2968 Tor 0.3.0.8 also includes fixes for several key management bugs
2969 that sometimes made relays unreliable, as well as several other
2970 bugfixes described below.
2972 o Major bugfixes (hidden service, relay, security, backport
2973 from 0.3.1.3-alpha):
2974 - Fix a remotely triggerable assertion failure when a hidden service
2975 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2976 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2977 - Fix a remotely triggerable assertion failure caused by receiving a
2978 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2979 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2982 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2983 - When performing the v3 link handshake on a TLS connection, report
2984 that we have the x509 certificate that we actually used on that
2985 connection, even if we have changed certificates since that
2986 connection was first opened. Previously, we would claim to have
2987 used our most recent x509 link certificate, which would sometimes
2988 make the link handshake fail. Fixes one case of bug 22460; bugfix
2991 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
2992 - Regenerate link and authentication certificates whenever the key
2993 that signs them changes; also, regenerate link certificates
2994 whenever the signed key changes. Previously, these processes were
2995 only weakly coupled, and we relays could (for minutes to hours)
2996 wind up with an inconsistent set of keys and certificates, which
2997 other relays would not accept. Fixes two cases of bug 22460;
2998 bugfix on 0.3.0.1-alpha.
2999 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3000 send the certificate that matches the x509 certificate that we
3001 used on the TLS connection. Previously, there was a race condition
3002 if the TLS context rotated after we began the TLS handshake but
3003 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3006 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
3007 - Stop rejecting v3 hidden service descriptors because their size
3008 did not match an old padding rule. Fixes bug 22447; bugfix on
3011 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3012 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3013 December 2016 (of which ~126 were still functional) with a list of
3014 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3015 2017. Resolves ticket 21564.
3017 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
3018 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3019 bug 22252; bugfix on 0.2.9.3-alpha.
3021 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3022 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3023 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3025 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
3026 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3027 months, and regenerate it when it is within one month of expiring.
3028 Previously, we had generated this certificate at startup with a
3029 ten-year lifetime, but that could lead to weird behavior when Tor
3030 was started with a grossly inaccurate clock. Mitigates bug 22466;
3031 mitigation on 0.3.0.1-alpha.
3033 o Minor bugfixes (memory leak, directory authority, backport from
3035 - When directory authorities reject a router descriptor due to
3036 keypinning, free the router descriptor rather than leaking the
3037 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3040 Changes in version 0.2.9.11 - 2017-06-08
3041 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
3042 remotely crash a hidden service with an assertion failure. Anyone
3043 running a hidden service should upgrade to this version, or to some
3044 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3045 are not affected by TROVE-2017-004.)
3047 Tor 0.2.9.11 also backports fixes for several key management bugs
3048 that sometimes made relays unreliable, as well as several other
3049 bugfixes described below.
3051 o Major bugfixes (hidden service, relay, security, backport
3052 from 0.3.1.3-alpha):
3053 - Fix a remotely triggerable assertion failure caused by receiving a
3054 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3055 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3058 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3059 - When performing the v3 link handshake on a TLS connection, report
3060 that we have the x509 certificate that we actually used on that
3061 connection, even if we have changed certificates since that
3062 connection was first opened. Previously, we would claim to have
3063 used our most recent x509 link certificate, which would sometimes
3064 make the link handshake fail. Fixes one case of bug 22460; bugfix
3067 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3068 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3069 December 2016 (of which ~126 were still functional) with a list of
3070 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3071 2017. Resolves ticket 21564.
3073 o Minor features (future-proofing, backport from 0.3.0.7):
3074 - Tor no longer refuses to download microdescriptors or descriptors if
3075 they are listed as "published in the future". This change will
3076 eventually allow us to stop listing meaningful "published" dates
3077 in microdescriptor consensuses, and thereby allow us to reduce the
3078 resources required to download consensus diffs by over 50%.
3079 Implements part of ticket 21642; implements part of proposal 275.
3081 o Minor features (directory authorities, backport from 0.3.0.4-rc)
3082 - Directory authorities now reject relays running versions
3083 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3084 suffer from bug 20499 and don't keep their consensus cache
3085 up-to-date. Resolves ticket 20509.
3087 o Minor features (geoip):
3088 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3091 o Minor bugfixes (control port, backport from 0.3.0.6):
3092 - The GETINFO extra-info/digest/<digest> command was broken because
3093 of a wrong base16 decode return value check, introduced when
3094 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3096 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3097 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3098 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3100 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
3101 - The getpid() system call is now permitted under the Linux seccomp2
3102 sandbox, to avoid crashing with versions of OpenSSL (and other
3103 libraries) that attempt to learn the process's PID by using the
3104 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3107 o Minor bugfixes (memory leak, directory authority, backport
3108 from 0.3.1.2-alpha):
3109 - When directory authorities reject a router descriptor due to
3110 keypinning, free the router descriptor rather than leaking the
3111 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3113 Changes in version 0.2.8.14 - 2017-06-08
3114 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3115 remotely crash a hidden service with an assertion failure. Anyone
3116 running a hidden service should upgrade to this version, or to some
3117 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3118 are not affected by TROVE-2017-004.)
3120 o Major bugfixes (hidden service, relay, security):
3121 - Fix a remotely triggerable assertion failure caused by receiving a
3122 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3123 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3126 o Minor features (geoip):
3127 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3130 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3131 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3132 December 2016 (of which ~126 were still functional) with a list of
3133 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3134 2017. Resolves ticket 21564.
3136 o Minor bugfixes (correctness):
3137 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3138 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3140 Changes in version 0.2.7.8 - 2017-06-08
3141 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3142 remotely crash a hidden service with an assertion failure. Anyone
3143 running a hidden service should upgrade to this version, or to some
3144 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3145 are not affected by TROVE-2017-004.)
3147 o Major bugfixes (hidden service, relay, security):
3148 - Fix a remotely triggerable assertion failure caused by receiving a
3149 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3150 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3153 o Minor features (geoip):
3154 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3157 o Minor bugfixes (correctness):
3158 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3159 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3162 Changes in version 0.2.6.12 - 2017-06-08
3163 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
3164 remotely crash a hidden service with an assertion failure. Anyone
3165 running a hidden service should upgrade to this version, or to some
3166 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3167 are not affected by TROVE-2017-004.)
3169 o Major bugfixes (hidden service, relay, security):
3170 - Fix a remotely triggerable assertion failure caused by receiving a
3171 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3172 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3175 o Minor features (geoip):
3176 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3179 o Minor bugfixes (correctness):
3180 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3181 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3183 Changes in version 0.2.5.14 - 2017-06-08
3184 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
3185 remotely crash a hidden service with an assertion failure. Anyone
3186 running a hidden service should upgrade to this version, or to some
3187 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3188 are not affected by TROVE-2017-004.)
3190 o Major bugfixes (hidden service, relay, security):
3191 - Fix a remotely triggerable assertion failure caused by receiving a
3192 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3193 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3196 o Minor features (geoip):
3197 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3200 o Minor bugfixes (correctness):
3201 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3202 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3204 Changes in version 0.2.4.29 - 2017-06-08
3205 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
3206 remotely crash a hidden service with an assertion failure. Anyone
3207 running a hidden service should upgrade to this version, or to some
3208 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3209 are not affected by TROVE-2017-004.)
3211 o Major bugfixes (hidden service, relay, security):
3212 - Fix a remotely triggerable assertion failure caused by receiving a
3213 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3214 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3217 o Minor features (geoip):
3218 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3221 o Minor bugfixes (correctness):
3222 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3223 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3226 Changes in version 0.3.0.7 - 2017-05-15
3227 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3228 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3229 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3230 clients are not affected.
3232 o Major bugfixes (hidden service directory, security):
3233 - Fix an assertion failure in the hidden service directory code, which
3234 could be used by an attacker to remotely cause a Tor relay process to
3235 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3236 should upgrade. This security issue is tracked as TROVE-2017-002.
3237 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3240 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3243 o Minor features (future-proofing):
3244 - Tor no longer refuses to download microdescriptors or descriptors
3245 if they are listed as "published in the future". This change will
3246 eventually allow us to stop listing meaningful "published" dates
3247 in microdescriptor consensuses, and thereby allow us to reduce the
3248 resources required to download consensus diffs by over 50%.
3249 Implements part of ticket 21642; implements part of proposal 275.
3251 o Minor bugfixes (Linux seccomp2 sandbox):
3252 - The getpid() system call is now permitted under the Linux seccomp2
3253 sandbox, to avoid crashing with versions of OpenSSL (and other
3254 libraries) that attempt to learn the process's PID by using the
3255 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3259 Changes in version 0.3.0.6 - 2017-04-26
3260 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3262 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3263 authenticate their link connections to relays, rather than the old
3264 RSA1024 keys that they used before. (Circuit crypto has been
3265 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3266 the guard selection and replacement algorithm to behave more robustly
3267 in the presence of unreliable networks, and to resist guard-
3270 This series also includes numerous other small features and bugfixes,
3271 along with more groundwork for the upcoming hidden-services revamp.
3273 Per our stable release policy, we plan to support the Tor 0.3.0
3274 release series for at least the next nine months, or for three months
3275 after the first stable release of the 0.3.1 series: whichever is
3276 longer. If you need a release with long-term support, we recommend
3277 that you stay with the 0.2.9 series.
3279 Below are the changes since 0.2.9.10. For a list of only the changes
3280 since 0.3.0.5-rc, see the ChangeLog file.
3282 o Major features (directory authority, security):
3283 - The default for AuthDirPinKeys is now 1: directory authorities
3284 will reject relays where the RSA identity key matches a previously
3285 seen value, but the Ed25519 key has changed. Closes ticket 18319.
3287 o Major features (guard selection algorithm):
3288 - Tor's guard selection algorithm has been redesigned from the
3289 ground up, to better support unreliable networks and restrictive
3290 sets of entry nodes, and to better resist guard-capture attacks by
3291 hostile local networks. Implements proposal 271; closes
3294 o Major features (next-generation hidden services):
3295 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
3296 prop224 aka "Next Generation Hidden Services". Service and clients
3297 don't use this functionality yet. Closes ticket 19043. Based on
3298 initial code by Alec Heifetz.
3299 - Relays now support the HSDir version 3 protocol, so that they can
3300 can store and serve v3 descriptors. This is part of the next-
3301 generation onion service work detailed in proposal 224. Closes
3304 o Major features (protocol, ed25519 identity keys):
3305 - Clients now support including Ed25519 identity keys in the EXTEND2
3306 cells they generate. By default, this is controlled by a consensus
3307 parameter, currently disabled. You can turn this feature on for
3308 testing by setting ExtendByEd25519ID in your configuration. This
3309 might make your traffic appear different than the traffic
3310 generated by other users, however. Implements part of ticket
3311 15056; part of proposal 220.
3312 - Relays now understand requests to extend to other relays by their
3313 Ed25519 identity keys. When an Ed25519 identity key is included in
3314 an EXTEND2 cell, the relay will only extend the circuit if the
3315 other relay can prove ownership of that identity. Implements part
3316 of ticket 15056; part of proposal 220.
3317 - Relays now use Ed25519 to prove their Ed25519 identities and to
3318 one another, and to clients. This algorithm is faster and more
3319 secure than the RSA-based handshake we've been doing until now.
3320 Implements the second big part of proposal 220; Closes
3323 o Major features (security):
3324 - Change the algorithm used to decide DNS TTLs on client and server
3325 side, to better resist DNS-based correlation attacks like the
3326 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3327 Feamster. Now relays only return one of two possible DNS TTL
3328 values, and clients are willing to believe DNS TTL values up to 3
3329 hours long. Closes ticket 19769.
3331 o Major bugfixes (client, onion service, also in 0.2.9.9):
3332 - Fix a client-side onion service reachability bug, where multiple
3333 socks requests to an onion service (or a single slow request)
3334 could cause us to mistakenly mark some of the service's
3335 introduction points as failed, and we cache that failure so
3336 eventually we run out and can't reach the service. Also resolves a
3337 mysterious "Remote server sent bogus reason code 65021" log
3338 warning. The bug was introduced in ticket 17218, where we tried to
3339 remember the circuit end reason as a uint16_t, which mangled
3340 negative values. Partially fixes bug 21056 and fixes bug 20307;
3341 bugfix on 0.2.8.1-alpha.
3343 o Major bugfixes (crash, directory connections):
3344 - Fix a rare crash when sending a begin cell on a circuit whose
3345 linked directory connection had already been closed. Fixes bug
3346 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3348 o Major bugfixes (directory authority):
3349 - During voting, when marking a relay as a probable sybil, do not
3350 clear its BadExit flag: sybils can still be bad in other ways
3351 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3354 o Major bugfixes (DNS):
3355 - Fix a bug that prevented exit nodes from caching DNS records for
3356 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3358 o Major bugfixes (IPv6 Exits):
3359 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3360 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3361 exit policy rejects that port on more than an IPv6 /16 of
3362 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3363 which rejected a relay's own IPv6 address by default. Fixes bug
3364 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3366 o Major bugfixes (parsing):
3367 - Fix an integer underflow bug when comparing malformed Tor
3368 versions. This bug could crash Tor when built with
3369 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3370 0.2.9.8, which were built with -ftrapv by default. In other cases
3371 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3372 on 0.0.8pre1. Found by OSS-Fuzz.
3373 - When parsing a malformed content-length field from an HTTP
3374 message, do not read off the end of the buffer. This bug was a
3375 potential remote denial-of-service attack against Tor clients and
3376 relays. A workaround was released in October 2016, to prevent this
3377 bug from crashing Tor. This is a fix for the underlying issue,
3378 which should no longer matter (if you applied the earlier patch).
3379 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
3380 using AFL (http://lcamtuf.coredump.cx/afl/).
3382 o Major bugfixes (scheduler):
3383 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
3384 caused the channel scheduler to behave more or less randomly,
3385 rather than preferring channels with higher-priority circuits.
3386 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
3388 o Major bugfixes (security, also in 0.2.9.9):
3389 - Downgrade the "-ftrapv" option from "always on" to "only on when
3390 --enable-expensive-hardening is provided." This hardening option,
3391 like others, can turn survivable bugs into crashes--and having it
3392 on by default made a (relatively harmless) integer overflow bug
3393 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
3394 bugfix on 0.2.9.1-alpha.
3396 o Minor feature (client):
3397 - Enable IPv6 traffic on the SocksPort by default. To disable this,
3398 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
3400 o Minor feature (fallback scripts):
3401 - Add a check_existing mode to updateFallbackDirs.py, which checks
3402 if fallbacks in the hard-coded list are working. Closes ticket
3403 20174. Patch by haxxpop.
3405 o Minor feature (protocol versioning):
3406 - Add new protocol version for proposal 224. HSIntro now advertises
3407 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
3409 o Minor features (ciphersuite selection):
3410 - Allow relays to accept a wider range of ciphersuites, including
3411 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
3412 - Clients now advertise a list of ciphersuites closer to the ones
3413 preferred by Firefox. Closes part of ticket 15426.
3415 o Minor features (controller):
3416 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
3417 shared-random values to the controller. Closes ticket 19925.
3418 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
3419 rather than "unrecognized." Closes ticket 20389; patch from
3422 o Minor features (controller, configuration):
3423 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
3424 and so on, now comes with a __*Port variant that will not be saved
3425 to the torrc file by the controller's SAVECONF command. This
3426 change allows TorBrowser to set up a single-use domain socket for
3427 each time it launches Tor. Closes ticket 20956.
3428 - The GETCONF command can now query options that may only be
3429 meaningful in context-sensitive lists. This allows the controller
3430 to query the mixed SocksPort/__SocksPort style options introduced
3431 in feature 20956. Implements ticket 21300.
3433 o Minor features (diagnostic, directory client):
3434 - Warn when we find an unexpected inconsistency in directory
3435 download status objects. Prevents some negative consequences of
3438 o Minor features (directory authorities):
3439 - Directory authorities now reject descriptors that claim to be
3440 malformed versions of Tor. Helps prevent exploitation of
3442 - Reject version numbers with components that exceed INT32_MAX.
3443 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3444 Fixes bug 21450; bugfix on 0.0.8pre1.
3446 o Minor features (directory authority):
3447 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
3448 default) to control whether authorities should try to probe relays
3449 by their Ed25519 link keys. This option will go away in a few
3450 releases--unless we encounter major trouble in our ed25519 link
3451 protocol rollout, in which case it will serve as a safety option.
3453 o Minor features (directory cache):
3454 - Relays and bridges will now refuse to serve the consensus they
3455 have if they know it is too old for a client to use. Closes
3458 o Minor features (ed25519 link handshake):
3459 - Advertise support for the ed25519 link handshake using the
3460 subprotocol-versions mechanism, so that clients can tell which
3461 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
3463 o Minor features (entry guards):
3464 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
3465 break regression tests.
3466 - Require UseEntryGuards when UseBridges is set, in order to make
3467 sure bridges aren't bypassed. Resolves ticket 20502.
3469 o Minor features (fallback directories):
3470 - Allow 3 fallback relays per operator, which is safe now that we
3471 are choosing 200 fallback relays. Closes ticket 20912.
3472 - Annotate updateFallbackDirs.py with the bandwidth and consensus
3473 weight for each candidate fallback. Closes ticket 20878.
3474 - Display the relay fingerprint when downloading consensuses from
3475 fallbacks. Closes ticket 20908.
3476 - Exclude relays affected by bug 20499 from the fallback list.
3477 Exclude relays from the fallback list if they are running versions
3478 known to be affected by bug 20499, or if in our tests they deliver
3479 a stale consensus (i.e. one that expired more than 24 hours ago).
3480 Closes ticket 20539.
3481 - Make it easier to change the output sort order of fallbacks.
3482 Closes ticket 20822.
3483 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
3485 - Require fallback directories to have the same address and port for
3486 7 days (now that we have enough relays with this stability).
3487 Relays whose OnionOO stability timer is reset on restart by bug
3488 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
3489 this issue. Closes ticket 20880; maintains short-term fix
3491 - Require fallbacks to have flags for 90% of the time (weighted
3492 decaying average), rather than 95%. This allows at least 73% of
3493 clients to bootstrap in the first 5 seconds without contacting an
3494 authority. Part of ticket 18828.
3495 - Select 200 fallback directories for each release. Closes
3498 o Minor features (fingerprinting resistance, authentication):
3499 - Extend the length of RSA keys used for TLS link authentication to
3500 2048 bits. (These weren't used for forward secrecy; for forward
3501 secrecy, we used P256.) Closes ticket 13752.
3503 o Minor features (geoip):
3504 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
3507 o Minor features (geoip, also in 0.2.9.9):
3508 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
3511 o Minor features (infrastructure):
3512 - Implement smartlist_add_strdup() function. Replaces the use of
3513 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
3515 o Minor features (linting):
3516 - Enhance the changes file linter to warn on Tor versions that are
3517 prefixed with "tor-". Closes ticket 21096.
3519 o Minor features (logging):
3520 - In several places, describe unset ed25519 keys as "<unset>",
3521 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
3523 o Minor features (portability, compilation):
3524 - Autoconf now checks to determine if OpenSSL structures are opaque,
3525 instead of explicitly checking for OpenSSL version numbers. Part
3527 - Support building with recent LibreSSL code that uses opaque
3528 structures. Closes ticket 21359.
3530 o Minor features (relay):
3531 - We now allow separation of exit and relay traffic to different
3532 source IP addresses, using the OutboundBindAddressExit and
3533 OutboundBindAddressOR options respectively. Closes ticket 17975.
3534 Written by Michael Sonntag.
3536 o Minor features (reliability, crash):
3537 - Try better to detect problems in buffers where they might grow (or
3538 think they have grown) over 2 GB in size. Diagnostic for
3541 o Minor features (testing):
3542 - During 'make test-network-all', if tor logs any warnings, ask
3543 chutney to output them. Requires a recent version of chutney with
3544 the 21572 patch. Implements 21570.
3546 o Minor bugfix (control protocol):
3547 - The reply to a "GETINFO config/names" request via the control
3548 protocol now spells the type "Dependent" correctly. This is a
3549 breaking change in the control protocol. (The field seems to be
3550 ignored by the most common known controllers.) Fixes bug 18146;
3551 bugfix on 0.1.1.4-alpha.
3552 - The GETINFO extra-info/digest/<digest> command was broken because
3553 of a wrong base16 decode return value check, introduced when
3554 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3556 o Minor bugfix (logging):
3557 - Don't recommend the use of Tor2web in non-anonymous mode.
3558 Recommending Tor2web is a bad idea because the client loses all
3559 anonymity. Tor2web should only be used in specific cases by users
3560 who *know* and understand the issues. Fixes bug 21294; bugfix
3563 o Minor bugfixes (bug resilience):
3564 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
3565 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
3566 Hans Jerry Illikainen.
3568 o Minor bugfixes (build):
3569 - Replace obsolete Autoconf macros with their modern equivalent and
3570 prevent similar issues in the future. Fixes bug 20990; bugfix
3573 o Minor bugfixes (certificate expiration time):
3574 - Avoid using link certificates that don't become valid till some
3575 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
3577 o Minor bugfixes (client):
3578 - Always recover from failures in extend_info_from_node(), in an
3579 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
3580 bugfix on 0.2.3.1-alpha.
3581 - When clients that use bridges start up with a cached consensus on
3582 disk, they were ignoring it and downloading a new one. Now they
3583 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
3585 o Minor bugfixes (code correctness):
3586 - Repair a couple of (unreachable or harmless) cases of the risky
3587 comparison-by-subtraction pattern that caused bug 21278.
3589 o Minor bugfixes (config):
3590 - Don't assert on startup when trying to get the options list and
3591 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
3592 options so of course they aren't ready yet. Fixes bug 21062;
3593 bugfix on 0.2.9.3-alpha.
3595 o Minor bugfixes (configuration):
3596 - Accept non-space whitespace characters after the severity level in
3597 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
3598 - Support "TByte" and "TBytes" units in options given in bytes.
3599 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
3600 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
3602 o Minor bugfixes (configure, autoconf):
3603 - Rename the configure option --enable-expensive-hardening to
3604 --enable-fragile-hardening. Expensive hardening makes the tor
3605 daemon abort when some kinds of issues are detected. Thus, it
3606 makes tor more at risk of remote crashes but safer against RCE or
3607 heartbleed bug category. We now try to explain this issue in a
3608 message from the configure script. Fixes bug 21290; bugfix
3611 o Minor bugfixes (consensus weight):
3612 - Add new consensus method that initializes bw weights to 1 instead
3613 of 0. This prevents a zero weight from making it all the way to
3614 the end (happens in small testing networks) and causing an error.
3615 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
3617 o Minor bugfixes (crash prevention):
3618 - Fix an (currently untriggerable, but potentially dangerous) crash
3619 bug when base32-encoding inputs whose sizes are not a multiple of
3620 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3622 o Minor bugfixes (dead code):
3623 - Remove a redundant check for PidFile changes at runtime in
3624 options_transition_allowed(): this check is already performed
3625 regardless of whether the sandbox is active. Fixes bug 21123;
3626 bugfix on 0.2.5.4-alpha.
3628 o Minor bugfixes (descriptors):
3629 - Correctly recognise downloaded full descriptors as valid, even
3630 when using microdescriptors as circuits. This affects clients with
3631 FetchUselessDescriptors set, and may affect directory authorities.
3632 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
3634 o Minor bugfixes (directory mirrors):
3635 - Allow relays to use directory mirrors without a DirPort: these
3636 relays need to be contacted over their ORPorts using a begindir
3637 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3638 - Clarify the message logged when a remote relay is unexpectedly
3639 missing an ORPort or DirPort: users were confusing this with a
3640 local port. Fixes another case of bug 20711; bugfix
3643 o Minor bugfixes (directory system):
3644 - Bridges and relays now use microdescriptors (like clients do)
3645 rather than old-style router descriptors. Now bridges will blend
3646 in with clients in terms of the circuits they build. Fixes bug
3647 6769; bugfix on 0.2.3.2-alpha.
3648 - Download all consensus flavors, descriptors, and authority
3649 certificates when FetchUselessDescriptors is set, regardless of
3650 whether tor is a directory cache or not. Fixes bug 20667; bugfix
3651 on all recent tor versions.
3653 o Minor bugfixes (documentation):
3654 - Update the tor manual page to document every option that can not
3655 be changed while tor is running. Fixes bug 21122.
3657 o Minor bugfixes (ed25519 certificates):
3658 - Correctly interpret ed25519 certificates that would expire some
3659 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
3661 o Minor bugfixes (fallback directories):
3662 - Avoid checking fallback candidates' DirPorts if they are down in
3663 OnionOO. When a relay operator has multiple relays, this
3664 prioritizes relays that are up over relays that are down. Fixes
3665 bug 20926; bugfix on 0.2.8.3-alpha.
3666 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
3667 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
3668 - Stop failing when a relay has no uptime data in
3669 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
3671 o Minor bugfixes (hidden service):
3672 - Clean up the code for expiring intro points with no associated
3673 circuits. It was causing, rarely, a service with some expiring
3674 introduction points to not open enough additional introduction
3675 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
3676 - Resolve two possible underflows which could lead to creating and
3677 closing a lot of introduction point circuits in a non-stop loop.
3678 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
3679 - Stop setting the torrc option HiddenServiceStatistics to "0" just
3680 because we're not a bridge or relay. Instead, we preserve whatever
3681 value the user set (or didn't set). Fixes bug 21150; bugfix
3684 o Minor bugfixes (hidden services):
3685 - Make hidden services check for failed intro point connections,
3686 even when they have exceeded their intro point creation limit.
3687 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
3688 - Make hidden services with 8 to 10 introduction points check for
3689 failed circuits immediately after startup. Previously, they would
3690 wait for 5 minutes before performing their first checks. Fixes bug
3691 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
3692 - Stop ignoring misconfigured hidden services. Instead, refuse to
3693 start tor until the misconfigurations have been corrected. Fixes
3694 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
3697 o Minor bugfixes (IPv6):
3698 - Make IPv6-using clients try harder to find an IPv6 directory
3699 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
3700 - When IPv6 addresses have not been downloaded yet (microdesc
3701 consensus documents don't list relay IPv6 addresses), use hard-
3702 coded addresses for authorities, fallbacks, and configured
3703 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
3704 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
3706 o Minor bugfixes (memory leak at exit):
3707 - Fix a small harmless memory leak at exit of the previously unused
3708 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
3711 o Minor bugfixes (onion services):
3712 - Allow the number of introduction points to be as low as 0, rather
3713 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
3715 o Minor bugfixes (portability):
3716 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
3717 It is supported by OpenBSD itself, and also by most OpenBSD
3718 variants (such as Bitrig). Fixes bug 20980; bugfix
3721 o Minor bugfixes (portability, also in 0.2.9.9):
3722 - Avoid crashing when Tor is built using headers that contain
3723 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3724 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3726 - Fix Libevent detection on platforms without Libevent 1 headers
3727 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3729 o Minor bugfixes (relay):
3730 - Avoid a double-marked-circuit warning that could happen when we
3731 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3733 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
3734 initializing the keys would reset the DataDirectory to 0700
3735 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
3736 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
3738 o Minor bugfixes (testing):
3739 - Fix Raspbian build issues related to missing socket errno in
3740 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
3741 - Remove undefined behavior from the backtrace generator by removing
3742 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
3743 - Use bash in src/test/test-network.sh. This ensures we reliably
3744 call chutney's newer tools/test-network.sh when available. Fixes
3745 bug 21562; bugfix on 0.2.9.1-alpha.
3747 o Minor bugfixes (tor-resolve):
3748 - The tor-resolve command line tool now rejects hostnames over 255
3749 characters in length. Previously, it would silently truncate them,
3750 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3751 Patch by "junglefowl".
3753 o Minor bugfixes (unit tests):
3754 - Allow the unit tests to pass even when DNS lookups of bogus
3755 addresses do not fail as expected. Fixes bug 20862 and 20863;
3756 bugfix on unit tests introduced in 0.2.8.1-alpha
3757 through 0.2.9.4-alpha.
3759 o Minor bugfixes (util):
3760 - When finishing writing a file to disk, if we were about to replace
3761 the file with the temporary file created before and we fail to
3762 replace it, remove the temporary file so it doesn't stay on disk.
3763 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
3765 o Minor bugfixes (Windows services):
3766 - Be sure to initialize the monotonic time subsystem before using
3767 it, even when running as an NT service. Fixes bug 21356; bugfix
3770 o Minor bugfixes (Windows):
3771 - Check for getpagesize before using it to mmap files. This fixes
3772 compilation in some MinGW environments. Fixes bug 20530; bugfix on
3773 0.1.2.1-alpha. Reported by "ice".
3775 o Code simplification and refactoring:
3776 - Abolish all global guard context in entrynodes.c; replace with new
3777 guard_selection_t structure as preparation for proposal 271.
3778 Closes ticket 19858.
3779 - Extract magic numbers in circuituse.c into defined variables.
3780 - Introduce rend_service_is_ephemeral() that tells if given onion
3781 service is ephemeral. Replace unclear NULL-checkings for service
3782 directory with this function. Closes ticket 20526.
3783 - Refactor circuit_is_available_for_use to remove unnecessary check.
3784 - Refactor circuit_predict_and_launch_new for readability and
3785 testability. Closes ticket 18873.
3786 - Refactor code to manipulate global_origin_circuit_list into
3787 separate functions. Closes ticket 20921.
3788 - Refactor large if statement in purpose_needs_anonymity to use
3789 switch statement instead. Closes part of ticket 20077.
3790 - Refactor the hashing API to return negative values for errors, as
3791 is done as throughout the codebase. Closes ticket 20717.
3792 - Remove data structures that were used to index or_connection
3793 objects by their RSA identity digests. These structures are fully
3794 redundant with the similar structures used in the
3795 channel abstraction.
3796 - Remove duplicate code in the channel_write_*cell() functions.
3797 Closes ticket 13827; patch from Pingl.
3798 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
3799 use only purpose_needs_anonymity. Closes part of ticket 20077.
3800 - The code to generate and parse EXTEND and EXTEND2 cells has been
3801 replaced with code automatically generated by the
3804 o Documentation (formatting):
3805 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
3806 blocks were incorrectly appearing. Closes ticket 20885.
3808 o Documentation (man page):
3809 - Clarify many options in tor.1 and add some min/max values for
3810 HiddenService options. Closes ticket 21058.
3813 - Change '1' to 'weight_scale' in consensus bw weights calculation
3814 comments, as that is reality. Closes ticket 20273. Patch
3816 - Clarify that when ClientRejectInternalAddresses is enabled (which
3817 is the default), multicast DNS hostnames for machines on the local
3818 network (of the form *.local) are also rejected. Closes
3820 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
3821 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
3822 - Include the "TBits" unit in Tor's man page. Fixes part of bug
3823 20622; bugfix on 0.2.5.1-alpha.
3824 - Small fixes to the fuzzing documentation. Closes ticket 21472.
3825 - Stop the man page from incorrectly stating that HiddenServiceDir
3826 must already exist. Fixes 20486.
3827 - Update the description of the directory server options in the
3828 manual page, to clarify that a relay no longer needs to set
3829 DirPort in order to be a directory cache. Closes ticket 21720.
3832 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
3833 limit for relays running on a single IP applies to authority IP
3834 addresses as well as to non-authority IP addresses. Closes
3836 - The UseDirectoryGuards torrc option no longer exists: all users
3837 that use entry guards will also use directory guards. Related to
3838 proposal 271; implements part of ticket 20831.
3841 - Add tests for networkstatus_compute_bw_weights_v10.
3842 - Add unit tests circuit_predict_and_launch_new.
3843 - Extract dummy_origin_circuit_new so it can be used by other
3845 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
3846 from "overcaffeinated".
3847 - Perform the coding style checks when running the tests and fail
3848 when coding style violations are found. Closes ticket 5500.
3851 Changes in version 0.2.8.13 - 2017-03-03
3852 Tor 0.2.8.13 backports a security fix from later Tor
3853 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
3854 this release, if for some reason they cannot upgrade to a later
3855 release series, and if they build Tor with the --enable-expensive-hardening
3858 Note that support for Tor 0.2.8.x is ending next year: we will not issue
3859 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
3860 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3862 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3863 - Fix an integer underflow bug when comparing malformed Tor
3864 versions. This bug could crash Tor when built with
3865 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3866 0.2.9.8, which were built with -ftrapv by default. In other cases
3867 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3868 on 0.0.8pre1. Found by OSS-Fuzz.
3870 o Minor features (geoip):
3871 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3875 Changes in version 0.2.7.7 - 2017-03-03
3876 Tor 0.2.7.7 backports a number of security fixes from later Tor
3877 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
3878 this release, if for some reason they cannot upgrade to a later
3881 Note that support for Tor 0.2.7.x is ending this year: we will not issue
3882 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
3883 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3885 o Directory authority changes (backport from 0.2.8.5-rc):
3886 - Urras is no longer a directory authority. Closes ticket 19271.
3888 o Directory authority changes (backport from 0.2.9.2-alpha):
3889 - The "Tonga" bridge authority has been retired; the new bridge
3890 authority is "Bifroest". Closes tickets 19728 and 19690.
3892 o Directory authority key updates (backport from 0.2.8.1-alpha):
3893 - Update the V3 identity key for the dannenberg directory authority:
3894 it was changed on 18 November 2015. Closes task 17906. Patch
3897 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3898 - Fix a bug in parsing that could cause clients to read a single
3899 byte past the end of an allocated region. This bug could be used
3900 to cause hardened clients (built with --enable-expensive-hardening)
3901 to crash if they tried to visit a hostile hidden service. Non-
3902 hardened clients are only affected depending on the details of
3903 their platform's memory allocator. Fixes bug 21018; bugfix on
3904 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3905 2016-12-002 and as CVE-2016-1254.
3907 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3908 - Stop a crash that could occur when a client running with DNSPort
3909 received a query with multiple address types, and the first
3910 address type was not supported. Found and fixed by Scott Dial.
3911 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3912 - Prevent a class of security bugs caused by treating the contents
3913 of a buffer chunk as if they were a NUL-terminated string. At
3914 least one such bug seems to be present in all currently used
3915 versions of Tor, and would allow an attacker to remotely crash
3916 most Tor instances, especially those compiled with extra compiler
3917 hardening. With this defense in place, such bugs can't crash Tor,
3918 though we should still fix them as they occur. Closes ticket
3919 20384 (TROVE-2016-10-001).
3921 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3922 - Avoid a difficult-to-trigger heap corruption attack when extending
3923 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3924 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3925 Reported by Guido Vranken.
3927 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3928 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3929 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3931 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3932 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3933 pointer to the previous (uninitialized) key value. The impact here
3934 should be limited to a difficult-to-trigger crash, if OpenSSL is
3935 running an engine that makes key generation failures possible, or
3936 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3937 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3940 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3941 - Fix an integer underflow bug when comparing malformed Tor
3942 versions. This bug could crash Tor when built with
3943 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3944 0.2.9.8, which were built with -ftrapv by default. In other cases
3945 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3946 on 0.0.8pre1. Found by OSS-Fuzz.
3948 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3949 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3950 zero size. Check size argument to memwipe() for underflow. Fixes
3951 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3954 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3955 - Make Tor survive errors involving connections without a
3956 corresponding event object. Previously we'd fail with an
3957 assertion; now we produce a log message. Related to bug 16248.
3959 o Minor features (geoip):
3960 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3964 Changes in version 0.2.6.11 - 2017-03-03
3965 Tor 0.2.6.11 backports a number of security fixes from later Tor
3966 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
3967 this release, if for some reason they cannot upgrade to a later
3970 Note that support for Tor 0.2.6.x is ending this year: we will not issue
3971 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
3972 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3974 o Directory authority changes (backport from 0.2.8.5-rc):
3975 - Urras is no longer a directory authority. Closes ticket 19271.
3977 o Directory authority changes (backport from 0.2.9.2-alpha):
3978 - The "Tonga" bridge authority has been retired; the new bridge
3979 authority is "Bifroest". Closes tickets 19728 and 19690.
3981 o Directory authority key updates (backport from 0.2.8.1-alpha):
3982 - Update the V3 identity key for the dannenberg directory authority:
3983 it was changed on 18 November 2015. Closes task 17906. Patch
3986 o Major features (security fixes, backport from 0.2.9.4-alpha):
3987 - Prevent a class of security bugs caused by treating the contents
3988 of a buffer chunk as if they were a NUL-terminated string. At
3989 least one such bug seems to be present in all currently used
3990 versions of Tor, and would allow an attacker to remotely crash
3991 most Tor instances, especially those compiled with extra compiler
3992 hardening. With this defense in place, such bugs can't crash Tor,
3993 though we should still fix them as they occur. Closes ticket
3994 20384 (TROVE-2016-10-001).
3996 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3997 - Fix a bug in parsing that could cause clients to read a single
3998 byte past the end of an allocated region. This bug could be used
3999 to cause hardened clients (built with --enable-expensive-hardening)
4000 to crash if they tried to visit a hostile hidden service. Non-
4001 hardened clients are only affected depending on the details of
4002 their platform's memory allocator. Fixes bug 21018; bugfix on
4003 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4004 2016-12-002 and as CVE-2016-1254.
4006 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4007 - Stop a crash that could occur when a client running with DNSPort
4008 received a query with multiple address types, and the first
4009 address type was not supported. Found and fixed by Scott Dial.
4010 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4012 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4013 - Fix an error that could cause us to read 4 bytes before the
4014 beginning of an openssl string. This bug could be used to cause
4015 Tor to crash on systems with unusual malloc implementations, or
4016 systems with unusual hardening installed. Fixes bug 17404; bugfix
4019 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4020 - Avoid a difficult-to-trigger heap corruption attack when extending
4021 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4022 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4023 Reported by Guido Vranken.
4025 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4026 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4027 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4029 o Major bugfixes (guard selection, backport from 0.2.7.6):
4030 - Actually look at the Guard flag when selecting a new directory
4031 guard. When we implemented the directory guard design, we
4032 accidentally started treating all relays as if they have the Guard
4033 flag during guard selection, leading to weaker anonymity and worse
4034 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4037 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4038 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4039 pointer to the previous (uninitialized) key value. The impact here
4040 should be limited to a difficult-to-trigger crash, if OpenSSL is
4041 running an engine that makes key generation failures possible, or
4042 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4043 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4046 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4047 - Fix an integer underflow bug when comparing malformed Tor
4048 versions. This bug could crash Tor when built with
4049 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4050 0.2.9.8, which were built with -ftrapv by default. In other cases
4051 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4052 on 0.0.8pre1. Found by OSS-Fuzz.
4054 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4055 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4056 zero size. Check size argument to memwipe() for underflow. Fixes
4057 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4060 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4061 - Make Tor survive errors involving connections without a
4062 corresponding event object. Previously we'd fail with an
4063 assertion; now we produce a log message. Related to bug 16248.
4065 o Minor features (geoip):
4066 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4069 o Minor bugfixes (compilation, backport from 0.2.7.6):
4070 - Fix a compilation warning with Clang 3.6: Do not check the
4071 presence of an address which can never be NULL. Fixes bug 17781.
4074 Changes in version 0.2.5.13 - 2017-03-03
4075 Tor 0.2.5.13 backports a number of security fixes from later Tor
4076 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
4077 this release, if for some reason they cannot upgrade to a later
4080 Note that support for Tor 0.2.5.x is ending next year: we will not issue
4081 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
4082 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4084 o Directory authority changes (backport from 0.2.8.5-rc):
4085 - Urras is no longer a directory authority. Closes ticket 19271.
4087 o Directory authority changes (backport from 0.2.9.2-alpha):
4088 - The "Tonga" bridge authority has been retired; the new bridge
4089 authority is "Bifroest". Closes tickets 19728 and 19690.
4091 o Directory authority key updates (backport from 0.2.8.1-alpha):
4092 - Update the V3 identity key for the dannenberg directory authority:
4093 it was changed on 18 November 2015. Closes task 17906. Patch
4096 o Major features (security fixes, backport from 0.2.9.4-alpha):
4097 - Prevent a class of security bugs caused by treating the contents
4098 of a buffer chunk as if they were a NUL-terminated string. At
4099 least one such bug seems to be present in all currently used
4100 versions of Tor, and would allow an attacker to remotely crash
4101 most Tor instances, especially those compiled with extra compiler
4102 hardening. With this defense in place, such bugs can't crash Tor,
4103 though we should still fix them as they occur. Closes ticket
4104 20384 (TROVE-2016-10-001).
4106 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4107 - Fix a bug in parsing that could cause clients to read a single
4108 byte past the end of an allocated region. This bug could be used
4109 to cause hardened clients (built with --enable-expensive-hardening)
4110 to crash if they tried to visit a hostile hidden service. Non-
4111 hardened clients are only affected depending on the details of
4112 their platform's memory allocator. Fixes bug 21018; bugfix on
4113 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4114 2016-12-002 and as CVE-2016-1254.
4116 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4117 - Stop a crash that could occur when a client running with DNSPort
4118 received a query with multiple address types, and the first
4119 address type was not supported. Found and fixed by Scott Dial.
4120 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4122 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4123 - Fix an error that could cause us to read 4 bytes before the
4124 beginning of an openssl string. This bug could be used to cause
4125 Tor to crash on systems with unusual malloc implementations, or
4126 systems with unusual hardening installed. Fixes bug 17404; bugfix
4129 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4130 - Avoid a difficult-to-trigger heap corruption attack when extending
4131 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4132 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4133 Reported by Guido Vranken.
4135 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4136 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4137 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4139 o Major bugfixes (guard selection, backport from 0.2.7.6):
4140 - Actually look at the Guard flag when selecting a new directory
4141 guard. When we implemented the directory guard design, we
4142 accidentally started treating all relays as if they have the Guard
4143 flag during guard selection, leading to weaker anonymity and worse
4144 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4147 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4148 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4149 pointer to the previous (uninitialized) key value. The impact here
4150 should be limited to a difficult-to-trigger crash, if OpenSSL is
4151 running an engine that makes key generation failures possible, or
4152 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4153 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4156 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4157 - Fix an integer underflow bug when comparing malformed Tor
4158 versions. This bug could crash Tor when built with
4159 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4160 0.2.9.8, which were built with -ftrapv by default. In other cases
4161 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4162 on 0.0.8pre1. Found by OSS-Fuzz.
4164 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4165 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4166 zero size. Check size argument to memwipe() for underflow. Fixes
4167 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4170 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4171 - Make Tor survive errors involving connections without a
4172 corresponding event object. Previously we'd fail with an
4173 assertion; now we produce a log message. Related to bug 16248.
4175 o Minor features (geoip):
4176 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4179 o Minor bugfixes (compilation, backport from 0.2.7.6):
4180 - Fix a compilation warning with Clang 3.6: Do not check the
4181 presence of an address which can never be NULL. Fixes bug 17781.
4183 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
4184 - Check for failures from crypto_early_init, and refuse to continue.
4185 A previous typo meant that we could keep going with an
4186 uninitialized crypto library, and would have OpenSSL initialize
4187 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4188 when implementing ticket 4900. Patch by "teor".
4190 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4191 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4192 a client authorized hidden service. Fixes bug 15823; bugfix
4196 Changes in version 0.2.4.28 - 2017-03-03
4197 Tor 0.2.4.28 backports a number of security fixes from later Tor
4198 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
4199 this release, if for some reason they cannot upgrade to a later
4202 Note that support for Tor 0.2.4.x is ending soon: we will not issue
4203 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
4204 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
4206 o Directory authority changes (backport from 0.2.8.5-rc):
4207 - Urras is no longer a directory authority. Closes ticket 19271.
4209 o Directory authority changes (backport from 0.2.9.2-alpha):
4210 - The "Tonga" bridge authority has been retired; the new bridge
4211 authority is "Bifroest". Closes tickets 19728 and 19690.
4213 o Directory authority key updates (backport from 0.2.8.1-alpha):
4214 - Update the V3 identity key for the dannenberg directory authority:
4215 it was changed on 18 November 2015. Closes task 17906. Patch
4218 o Major features (security fixes, backport from 0.2.9.4-alpha):
4219 - Prevent a class of security bugs caused by treating the contents
4220 of a buffer chunk as if they were a NUL-terminated string. At
4221 least one such bug seems to be present in all currently used
4222 versions of Tor, and would allow an attacker to remotely crash
4223 most Tor instances, especially those compiled with extra compiler
4224 hardening. With this defense in place, such bugs can't crash Tor,
4225 though we should still fix them as they occur. Closes ticket
4226 20384 (TROVE-2016-10-001).
4228 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4229 - Fix a bug in parsing that could cause clients to read a single
4230 byte past the end of an allocated region. This bug could be used
4231 to cause hardened clients (built with --enable-expensive-hardening)
4232 to crash if they tried to visit a hostile hidden service. Non-
4233 hardened clients are only affected depending on the details of
4234 their platform's memory allocator. Fixes bug 21018; bugfix on
4235 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4236 2016-12-002 and as CVE-2016-1254.
4238 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4239 - Fix an error that could cause us to read 4 bytes before the
4240 beginning of an openssl string. This bug could be used to cause
4241 Tor to crash on systems with unusual malloc implementations, or
4242 systems with unusual hardening installed. Fixes bug 17404; bugfix
4245 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4246 - Avoid a difficult-to-trigger heap corruption attack when extending
4247 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4248 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4249 Reported by Guido Vranken.
4251 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4252 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4253 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4255 o Major bugfixes (guard selection, backport from 0.2.7.6):
4256 - Actually look at the Guard flag when selecting a new directory
4257 guard. When we implemented the directory guard design, we
4258 accidentally started treating all relays as if they have the Guard
4259 flag during guard selection, leading to weaker anonymity and worse
4260 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4263 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4264 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4265 pointer to the previous (uninitialized) key value. The impact here
4266 should be limited to a difficult-to-trigger crash, if OpenSSL is
4267 running an engine that makes key generation failures possible, or
4268 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4269 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4272 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4273 - Fix an integer underflow bug when comparing malformed Tor
4274 versions. This bug could crash Tor when built with
4275 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4276 0.2.9.8, which were built with -ftrapv by default. In other cases
4277 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4278 on 0.0.8pre1. Found by OSS-Fuzz.
4280 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4281 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4282 zero size. Check size argument to memwipe() for underflow. Fixes
4283 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4286 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4287 - Make Tor survive errors involving connections without a
4288 corresponding event object. Previously we'd fail with an
4289 assertion; now we produce a log message. Related to bug 16248.
4291 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
4292 - Make it harder for attackers to overload hidden services with
4293 introductions, by blocking multiple introduction requests on the
4294 same circuit. Resolves ticket 15515.
4296 o Minor features (geoip):
4297 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4300 o Minor bugfixes (compilation, backport from 0.2.7.6):
4301 - Fix a compilation warning with Clang 3.6: Do not check the
4302 presence of an address which can never be NULL. Fixes bug 17781.
4304 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4305 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4306 a client authorized hidden service. Fixes bug 15823; bugfix
4310 Changes in version 0.2.9.10 - 2017-03-01
4311 Tor 0.2.9.10 backports a security fix from later Tor release. It also
4312 includes fixes for some major issues affecting directory authorities,
4313 LibreSSL compatibility, and IPv6 correctness.
4315 The Tor 0.2.9.x release series is now marked as a long-term-support
4316 series. We intend to backport security fixes to 0.2.9.x until at
4317 least January of 2020.
4319 o Major bugfixes (directory authority, 0.3.0.3-alpha):
4320 - During voting, when marking a relay as a probable sybil, do not
4321 clear its BadExit flag: sybils can still be bad in other ways
4322 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4325 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
4326 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4327 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4328 exit policy rejects that port on more than an IPv6 /16 of
4329 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4330 which rejected a relay's own IPv6 address by default. Fixes bug
4331 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4333 o Major bugfixes (parsing, also in 0.3.0.4-rc):
4334 - Fix an integer underflow bug when comparing malformed Tor
4335 versions. This bug could crash Tor when built with
4336 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4337 0.2.9.8, which were built with -ftrapv by default. In other cases
4338 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4339 on 0.0.8pre1. Found by OSS-Fuzz.
4341 o Minor features (directory authorities, also in 0.3.0.4-rc):
4342 - Directory authorities now reject descriptors that claim to be
4343 malformed versions of Tor. Helps prevent exploitation of
4345 - Reject version numbers with components that exceed INT32_MAX.
4346 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
4347 Fixes bug 21450; bugfix on 0.0.8pre1.
4349 o Minor features (geoip):
4350 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4353 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
4354 - Autoconf now checks to determine if OpenSSL structures are opaque,
4355 instead of explicitly checking for OpenSSL version numbers. Part
4357 - Support building with recent LibreSSL code that uses opaque
4358 structures. Closes ticket 21359.
4360 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
4361 - Repair a couple of (unreachable or harmless) cases of the risky
4362 comparison-by-subtraction pattern that caused bug 21278.
4364 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
4365 - The tor-resolve command line tool now rejects hostnames over 255
4366 characters in length. Previously, it would silently truncate them,
4367 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4368 Patch by "junglefowl".
4371 Changes in version 0.2.9.9 - 2017-01-23
4372 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
4373 cause relays and clients to crash, even if they were not built with
4374 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4375 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4376 version should upgrade.
4378 This release also resolves a client-side onion service reachability
4379 bug, and resolves a pair of small portability issues.
4381 o Major bugfixes (security):
4382 - Downgrade the "-ftrapv" option from "always on" to "only on when
4383 --enable-expensive-hardening is provided." This hardening option,
4384 like others, can turn survivable bugs into crashes -- and having
4385 it on by default made a (relatively harmless) integer overflow bug
4386 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4387 bugfix on 0.2.9.1-alpha.
4389 o Major bugfixes (client, onion service):
4390 - Fix a client-side onion service reachability bug, where multiple
4391 socks requests to an onion service (or a single slow request)
4392 could cause us to mistakenly mark some of the service's
4393 introduction points as failed, and we cache that failure so
4394 eventually we run out and can't reach the service. Also resolves a
4395 mysterious "Remote server sent bogus reason code 65021" log
4396 warning. The bug was introduced in ticket 17218, where we tried to
4397 remember the circuit end reason as a uint16_t, which mangled
4398 negative values. Partially fixes bug 21056 and fixes bug 20307;
4399 bugfix on 0.2.8.1-alpha.
4401 o Minor features (geoip):
4402 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4405 o Minor bugfixes (portability):
4406 - Avoid crashing when Tor is built using headers that contain
4407 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4408 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4410 - Fix Libevent detection on platforms without Libevent 1 headers
4411 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4414 Changes in version 0.2.8.12 - 2016-12-19
4415 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
4416 below) where Tor clients could crash when attempting to visit a
4417 hostile hidden service. Clients are recommended to upgrade as packages
4418 become available for their systems.
4420 It also includes an updated list of fallback directories, backported
4423 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
4424 backported to 0.2.8 in the future.
4426 o Major bugfixes (parsing, security, backported from 0.2.9.8):
4427 - Fix a bug in parsing that could cause clients to read a single
4428 byte past the end of an allocated region. This bug could be used
4429 to cause hardened clients (built with --enable-expensive-hardening)
4430 to crash if they tried to visit a hostile hidden service. Non-
4431 hardened clients are only affected depending on the details of
4432 their platform's memory allocator. Fixes bug 21018; bugfix on
4433 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4434 2016-12-002 and as CVE-2016-1254.
4436 o Minor features (fallback directory list, backported from 0.2.9.8):
4437 - Replace the 81 remaining fallbacks of the 100 originally
4438 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4439 fallbacks (123 new, 54 existing, 27 removed) generated in December
4440 2016. Resolves ticket 20170.
4442 o Minor features (geoip, backported from 0.2.9.7-rc):
4443 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4447 Changes in version 0.2.9.8 - 2016-12-19
4448 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
4450 The Tor 0.2.9 series makes mandatory a number of security features
4451 that were formerly optional. It includes support for a new shared-
4452 randomness protocol that will form the basis for next generation
4453 hidden services, includes a single-hop hidden service mode for
4454 optimizing .onion services that don't actually want to be hidden,
4455 tries harder not to overload the directory authorities with excessive
4456 downloads, and supports a better protocol versioning scheme for
4457 improved compatibility with other implementations of the Tor protocol.
4459 And of course, there are numerous other bugfixes and improvements.
4461 This release also includes a fix for a medium-severity issue (bug
4462 21018 below) where Tor clients could crash when attempting to visit a
4463 hostile hidden service. Clients are recommended to upgrade as packages
4464 become available for their systems.
4466 Below are listed the changes since Tor 0.2.8.11. For a list of
4467 changes since 0.2.9.7-rc, see the ChangeLog file.
4469 o New system requirements:
4470 - When building with OpenSSL, Tor now requires version 1.0.1 or
4471 later. OpenSSL 1.0.0 and earlier are no longer supported by the
4472 OpenSSL team, and should not be used. Closes ticket 20303.
4473 - Tor now requires Libevent version 2.0.10-stable or later. Older
4474 versions of Libevent have less efficient backends for several
4475 platforms, and lack the DNS code that we use for our server-side
4476 DNS support. This implements ticket 19554.
4477 - Tor now requires zlib version 1.2 or later, for security,
4478 efficiency, and (eventually) gzip support. (Back when we started,
4479 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
4480 released in 2003. We recommend the latest version.)
4482 o Deprecated features:
4483 - A number of DNS-cache-related sub-options for client ports are now
4484 deprecated for security reasons, and may be removed in a future
4485 version of Tor. (We believe that client-side DNS caching is a bad
4486 idea for anonymity, and you should not turn it on.) The options
4487 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
4488 UseIPv4Cache, and UseIPv6Cache.
4489 - A number of options are deprecated for security reasons, and may
4490 be removed in a future version of Tor. The options are:
4491 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
4492 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
4493 CloseHSClientCircuitsImmediatelyOnTimeout,
4494 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
4495 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
4496 UseNTorHandshake, and WarnUnsafeSocks.
4497 - The *ListenAddress options are now deprecated as unnecessary: the
4498 corresponding *Port options should be used instead. These options
4499 may someday be removed. The affected options are:
4500 ControlListenAddress, DNSListenAddress, DirListenAddress,
4501 NATDListenAddress, ORListenAddress, SocksListenAddress,
4502 and TransListenAddress.
4504 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
4505 - Fix a bug in parsing that could cause clients to read a single
4506 byte past the end of an allocated region. This bug could be used
4507 to cause hardened clients (built with --enable-expensive-hardening)
4508 to crash if they tried to visit a hostile hidden service. Non-
4509 hardened clients are only affected depending on the details of
4510 their platform's memory allocator. Fixes bug 21018; bugfix on
4511 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4512 2016-12-002 and as CVE-2016-1254.
4514 o Major features (build, hardening):
4515 - Tor now builds with -ftrapv by default on compilers that support
4516 it. This option detects signed integer overflow (which C forbids),
4517 and turns it into a hard-failure. We do not apply this option to
4518 code that needs to run in constant time to avoid side-channels;
4519 instead, we use -fwrapv in that code. Closes ticket 17983.
4520 - When --enable-expensive-hardening is selected, stop applying the
4521 clang/gcc sanitizers to code that needs to run in constant time.
4522 Although we are aware of no introduced side-channels, we are not
4523 able to prove that there are none. Related to ticket 17983.
4525 o Major features (circuit building, security):
4526 - Authorities, relays, and clients now require ntor keys in all
4527 descriptors, for all hops (except for rare hidden service protocol
4528 cases), for all circuits, and for all other roles. Part of
4530 - Authorities, relays, and clients only use ntor, except for
4531 rare cases in the hidden service protocol. Part of ticket 19163.
4533 o Major features (compilation):
4534 - Our big list of extra GCC warnings is now enabled by default when
4535 building with GCC (or with anything like Clang that claims to be
4536 GCC-compatible). To make all warnings into fatal compilation
4537 errors, pass --enable-fatal-warnings to configure. Closes
4539 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
4540 turn on C and POSIX extensions. (Previously, we attempted to do
4541 this on an ad hoc basis.) Closes ticket 19139.
4543 o Major features (directory authorities, hidden services):
4544 - Directory authorities can now perform the shared randomness
4545 protocol specified by proposal 250. Using this protocol, directory
4546 authorities generate a global fresh random value every day. In the
4547 future, this value will be used by hidden services to select
4548 HSDirs. This release implements the directory authority feature;
4549 the hidden service side will be implemented in the future as part
4550 of proposal 224. Resolves ticket 16943; implements proposal 250.
4552 o Major features (downloading, random exponential backoff):
4553 - When we fail to download an object from a directory service, wait
4554 for an (exponentially increasing) randomized amount of time before
4555 retrying, rather than a fixed interval as we did before. This
4556 prevents a group of Tor instances from becoming too synchronized,
4557 or a single Tor instance from becoming too predictable, in its
4558 download schedule. Closes ticket 15942.
4560 o Major features (resource management):
4561 - Tor can now notice it is about to run out of sockets, and
4562 preemptively close connections of lower priority. (This feature is
4563 off by default for now, since the current prioritizing method is
4564 yet not mature enough. You can enable it by setting
4565 "DisableOOSCheck 0", but watch out: it might close some sockets
4566 you would rather have it keep.) Closes ticket 18640.
4568 o Major features (single-hop "hidden" services):
4569 - Add experimental HiddenServiceSingleHopMode and
4570 HiddenServiceNonAnonymousMode options. When both are set to 1,
4571 every hidden service on that Tor instance becomes a non-anonymous
4572 Single Onion Service. Single Onions make one-hop (direct)
4573 connections to their introduction and rendezvous points. One-hop
4574 circuits make Single Onion servers easily locatable, but clients
4575 remain location-anonymous. This is compatible with the existing
4576 hidden service implementation, and works on the current Tor
4577 network without any changes to older relays or clients. Implements
4578 proposal 260, completes ticket 17178. Patch by teor and asn.
4580 o Major features (subprotocol versions):
4581 - Tor directory authorities now vote on a set of recommended
4582 "subprotocol versions", and on a set of required subprotocol
4583 versions. Clients and relays that lack support for a _required_
4584 subprotocol version will not start; those that lack support for a
4585 _recommended_ subprotocol version will warn the user to upgrade.
4586 This change allows compatible implementations of the Tor protocol(s)
4587 to exist without pretending to be 100% bug-compatible with
4588 particular releases of Tor itself. Closes ticket 19958; implements
4589 part of proposal 264.
4591 o Major bugfixes (circuit building):
4592 - Hidden service client-to-intro-point and service-to-rendezvous-
4593 point circuits use the TAP key supplied by the protocol, to avoid
4594 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
4596 o Major bugfixes (download scheduling):
4597 - Avoid resetting download status for consensuses hourly, since we
4598 already have another, smarter retry mechanism. Fixes bug 8625;
4599 bugfix on 0.2.0.9-alpha.
4600 - If a consensus expires while we are waiting for certificates to
4601 download, stop waiting for certificates.
4602 - If we stop waiting for certificates less than a minute after we
4603 started downloading them, do not consider the certificate download
4604 failure a separate failure. Fixes bug 20533; bugfix
4606 - When using exponential backoff in test networks, use a lower
4607 exponent, so the delays do not vary as much. This helps test
4608 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4610 o Major bugfixes (exit policies):
4611 - Avoid disclosing exit outbound bind addresses, configured port
4612 bind addresses, and local interface addresses in relay descriptors
4613 by default under ExitPolicyRejectPrivate. Instead, only reject
4614 these (otherwise unlisted) addresses if
4615 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
4616 0.2.7.2-alpha. Patch by teor.
4618 o Major bugfixes (hidden services):
4619 - Allow Tor clients with appropriate controllers to work with
4620 FetchHidServDescriptors set to 0. Previously, this option also
4621 disabled descriptor cache lookup, thus breaking hidden services
4622 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
4623 - Clients now require hidden services to include the TAP keys for
4624 their intro points in the hidden service descriptor. This prevents
4625 an inadvertent upgrade to ntor, which a malicious hidden service
4626 could use to distinguish clients by consensus version. Fixes bug
4627 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
4629 o Major bugfixes (relay, resolver, logging):
4630 - For relays that don't know their own address, avoid attempting a
4631 local hostname resolve for each descriptor we download. This
4632 will cut down on the number of "Success: chose address 'x.x.x.x'"
4633 log lines, and also avoid confusing clock jumps if the resolver
4634 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4636 o Minor features (port flags):
4637 - Add new flags to the *Port options to give finer control over which
4638 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
4639 and the synthetic flag OnionTrafficOnly, which is equivalent to
4640 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
4641 18693; patch by "teor".
4643 o Minor features (build, hardening):
4644 - Detect and work around a libclang_rt problem that would prevent
4645 clang from finding __mulodi4() on some 32-bit platforms, and thus
4646 keep -ftrapv from linking on those systems. Closes ticket 19079.
4647 - When building on a system without runtime support for the runtime
4648 hardening options, try to log a useful warning at configuration
4649 time, rather than an incomprehensible warning at link time. If
4650 expensive hardening was requested, this warning becomes an error.
4651 Closes ticket 18895.
4653 o Minor features (client, directory):
4654 - Since authorities now omit all routers that lack the Running and
4655 Valid flags, we assume that any relay listed in the consensus must
4656 have those flags. Closes ticket 20001; implements part of
4659 o Minor features (code safety):
4660 - In our integer-parsing functions, ensure that the maximum value we
4661 allow is no smaller than the minimum value. Closes ticket 19063;
4662 patch from "U+039b".
4664 o Minor features (compilation, portability):
4665 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4668 o Minor features (config):
4669 - Warn users when descriptor and port addresses are inconsistent.
4670 Mitigates bug 13953; patch by teor.
4672 o Minor features (controller):
4673 - Allow controllers to configure basic client authorization on
4674 hidden services when they create them with the ADD_ONION controller
4675 command. Implements ticket 15588. Patch by "special".
4676 - Fire a STATUS_SERVER controller event whenever the hibernation
4677 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
4678 - Implement new GETINFO queries for all downloads that use
4679 download_status_t to schedule retries. This allows controllers to
4680 examine the schedule for pending downloads. Closes ticket 19323.
4682 o Minor features (development tools, etags):
4683 - Teach the "make tags" Makefile target how to correctly find
4684 "MOCK_IMPL" function definitions. Patch from nherring; closes
4687 o Minor features (directory authority):
4688 - After voting, if the authorities decide that a relay is not
4689 "Valid", they no longer include it in the consensus at all. Closes
4690 ticket 20002; implements part of proposal 272.
4691 - Directory authorities now only give the Guard flag to a relay if
4692 they are also giving it the Stable flag. This change allows us to
4693 simplify path selection for clients. It should have minimal effect
4694 in practice, since >99% of Guards already have the Stable flag.
4695 Implements ticket 18624.
4696 - Directory authorities now write their v3-status-votes file out to
4697 disk earlier in the consensus process, so we have a record of the
4698 votes even if we abort the consensus process. Resolves
4701 o Minor features (fallback directory list, new since 0.2.9.7-rc):
4702 - Replace the 81 remaining fallbacks of the 100 originally
4703 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4704 fallbacks (123 new, 54 existing, 27 removed) generated in December
4705 2016. Resolves ticket 20170.
4707 o Minor features (hidden service):
4708 - Stop being so strict about the payload length of "rendezvous1"
4709 cells. We used to be locked in to the "TAP" handshake length, and
4710 now we can handle better handshakes like "ntor". Resolves
4713 o Minor features (infrastructure, time):
4714 - Tor now includes an improved timer backend, so that we can
4715 efficiently support tens or hundreds of thousands of concurrent
4716 timers, as will be needed for some of our planned anti-traffic-
4717 analysis work. This code is based on William Ahern's "timeout.c"
4718 project, which implements a "tickless hierarchical timing wheel".
4719 Closes ticket 18365.
4720 - Tor now uses the operating system's monotonic timers (where
4721 available) for internal fine-grained timing. Previously we would
4722 look at the system clock, and then attempt to compensate for the
4723 clock running backwards. Closes ticket 18908.
4725 o Minor features (logging):
4726 - Add a set of macros to check nonfatal assertions, for internal
4727 use. Migrating more of our checks to these should help us avoid
4728 needless crash bugs. Closes ticket 18613.
4729 - Provide a more useful warning message when configured with an
4730 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
4731 - When dumping unparseable router descriptors, optionally store them
4732 in separate files, named by digest, up to a configurable size
4733 limit. You can change the size limit by setting the
4734 MaxUnparseableDescSizeToLog option, and disable this feature by
4735 setting that option to 0. Closes ticket 18322.
4737 o Minor features (performance):
4738 - Change the "optimistic data" extension from "off by default" to
4739 "on by default". The default was ordinarily overridden by a
4740 consensus option, but when clients were bootstrapping for the
4741 first time, they would not have a consensus to get the option
4742 from. Changing this default saves a round-trip during startup.
4743 Closes ticket 18815.
4745 o Minor features (relay, usability):
4746 - When the directory authorities refuse a bad relay's descriptor,
4747 encourage the relay operator to contact us. Many relay operators
4748 won't notice this line in their logs, but it's a win if even a few
4749 learn why we don't like what their relay was doing. Resolves
4752 o Minor features (security, TLS):
4753 - Servers no longer support clients that lack AES ciphersuites.
4754 (3DES is no longer considered an acceptable cipher.) We believe
4755 that no such Tor clients currently exist, since Tor has required
4756 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
4758 o Minor features (testing):
4759 - Disable memory protections on OpenBSD when performing our unit
4760 tests for memwipe(). The test deliberately invokes undefined
4761 behavior, and the OpenBSD protections interfere with this. Patch
4762 from "rubiate". Closes ticket 20066.
4763 - Move the test-network.sh script to chutney, and modify tor's test-
4764 network.sh to call the (newer) chutney version when available.
4765 Resolves ticket 19116. Patch by teor.
4766 - Use the lcov convention for marking lines as unreachable, so that
4767 we don't count them when we're generating test coverage data.
4768 Update our coverage tools to understand this convention. Closes
4770 - Our link-handshake unit tests now check that when invalid
4771 handshakes fail, they fail with the error messages we expected.
4772 - Our unit testing code that captures log messages no longer
4773 prevents them from being written out if the user asked for them
4774 (by passing --debug or --info or --notice or --warn to the "test"
4775 binary). This change prevents us from missing unexpected log
4776 messages simply because we were looking for others. Related to
4778 - The unit tests now log all warning messages with the "BUG" flag.
4779 Previously, they only logged errors by default. This change will
4780 help us make our testing code more correct, and make sure that we
4781 only hit this code when we mean to. In the meantime, however,
4782 there will be more warnings in the unit test logs than before.
4783 This is preparatory work for ticket 19999.
4784 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
4785 assertion as a test failure.
4786 - We've done significant work to make the unit tests run faster.
4788 o Minor features (testing, ipv6):
4789 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
4790 tests. Remove bridges+hs, as it's somewhat redundant. This
4791 requires a recent chutney version that supports IPv6 clients,
4792 relays, and authorities. Closes ticket 20069; patch by teor.
4793 - Add the single-onion and single-onion-ipv6 chutney targets to
4794 "make test-network-all". This requires a recent chutney version
4795 with the single onion network flavors (git c72a652 or later).
4796 Closes ticket 20072; patch by teor.
4798 o Minor features (Tor2web):
4799 - Make Tor2web clients respect ReachableAddresses. This feature was
4800 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
4801 0.2.8.7. Implements feature 20034. Patch by teor.
4803 o Minor features (unix domain sockets):
4804 - When configuring a unix domain socket for a SocksPort,
4805 ControlPort, or Hidden service, you can now wrap the address in
4806 quotes, using C-style escapes inside the quotes. This allows unix
4807 domain socket paths to contain spaces. Resolves ticket 18753.
4809 o Minor features (user interface):
4810 - Tor now supports the ability to declare options deprecated, so
4811 that we can recommend that people stop using them. Previously, this
4812 was done in an ad-hoc way. There is a new --list-deprecated-options
4813 command-line option to list all of the deprecated options. Closes
4816 o Minor features (virtual addresses):
4817 - Increase the maximum number of bits for the IPv6 virtual network
4818 prefix from 16 to 104. In this way, the condition for address
4819 allocation is less restrictive. Closes ticket 20151; feature
4822 o Minor bug fixes (circuits):
4823 - Use the CircuitBuildTimeout option whenever
4824 LearnCircuitBuildTimeout is disabled. Previously, we would respect
4825 the option when a user disabled it, but not when it was disabled
4826 because some other option was set. Fixes bug 20073; bugfix on
4827 0.2.4.12-alpha. Patch by teor.
4829 o Minor bugfixes (build):
4830 - The current Git revision when building from a local repository is
4831 now detected correctly when using git worktrees. Fixes bug 20492;
4832 bugfix on 0.2.3.9-alpha.
4834 o Minor bugfixes (relay address discovery):
4835 - Stop reordering IP addresses returned by the OS. This makes it
4836 more likely that Tor will guess the same relay IP address every
4837 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
4838 Reported by René Mayrhofer, patch by "cypherpunks".
4840 o Minor bugfixes (memory allocation):
4841 - Change how we allocate memory for large chunks on buffers, to
4842 avoid a (currently impossible) integer overflow, and to waste less
4843 space when allocating unusually large chunks. Fixes bug 20081;
4844 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
4846 o Minor bugfixes (bootstrap):
4847 - Remember the directory server we fetched the consensus or previous
4848 certificates from, and use it to fetch future authority
4849 certificates. This change improves bootstrapping performance.
4850 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
4852 o Minor bugfixes (circuits):
4853 - Make sure extend_info_from_router() is only called on servers.
4854 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
4856 o Minor bugfixes (client, fascistfirewall):
4857 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
4858 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
4860 o Minor bugfixes (client, unix domain sockets):
4861 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
4862 the client address is meaningless. Fixes bug 20261; bugfix
4865 o Minor bugfixes (code style):
4866 - Fix an integer signedness conversion issue in the case conversion
4867 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
4869 o Minor bugfixes (compilation):
4870 - Build correctly on versions of libevent2 without support for
4871 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
4873 - When building with Clang, use a full set of GCC warnings.
4874 (Previously, we included only a subset, because of the way we
4875 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
4876 - Detect Libevent2 functions correctly on systems that provide
4877 libevent2, but where libevent1 is linked with -levent. Fixes bug
4878 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
4879 - Run correctly when built on Windows build environments that
4880 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
4882 o Minor bugfixes (configuration):
4883 - When parsing quoted configuration values from the torrc file,
4884 handle Windows line endings correctly. Fixes bug 19167; bugfix on
4885 0.2.0.16-alpha. Patch from "Pingl".
4887 o Minor bugfixes (directory authority):
4888 - Authorities now sort the "package" lines in their votes, for ease
4889 of debugging. (They are already sorted in consensus documents.)
4890 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
4891 - Die with a more useful error when the operator forgets to place
4892 the authority_signing_key file into the keys directory. This
4893 avoids an uninformative assert & traceback about having an invalid
4894 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
4895 - When allowing private addresses, mark Exits that only exit to
4896 private locations as such. Fixes bug 20064; bugfix
4898 - When parsing a detached signature, make sure we use the length of
4899 the digest algorithm instead of a hardcoded DIGEST256_LEN in
4900 order to avoid comparing bytes out-of-bounds with a smaller digest
4901 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
4903 o Minor bugfixes (getpass):
4904 - Defensively fix a non-triggerable heap corruption at do_getpass()
4905 to protect ourselves from mistakes in the future. Fixes bug
4906 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
4909 o Minor bugfixes (guard selection):
4910 - Don't mark guards as unreachable if connection_connect() fails.
4911 That function fails for local reasons, so it shouldn't reveal
4912 anything about the status of the guard. Fixes bug 14334; bugfix
4914 - Use a single entry guard even if the NumEntryGuards consensus
4915 parameter is not provided. Fixes bug 17688; bugfix
4918 o Minor bugfixes (hidden services):
4919 - Increase the minimum number of internal circuits we preemptively
4920 build from 2 to 3, so a circuit is available when a client
4921 connects to another onion service. Fixes bug 13239; bugfix
4923 - Allow hidden services to run on IPv6 addresses even when the
4924 IPv6Exit option is not set. Fixes bug 18357; bugfix
4926 - Stop logging intro point details to the client log on certain
4927 error conditions. Fixed as part of bug 20012; bugfix on
4928 0.2.4.8-alpha. Patch by teor.
4929 - When deleting an ephemeral hidden service, close its intro points
4930 even if they are not completely open. Fixes bug 18604; bugfix
4932 - When configuring hidden services, check every hidden service
4933 directory's permissions. Previously, we only checked the last
4934 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
4936 o Minor bugfixes (IPv6, testing):
4937 - Check for IPv6 correctly on Linux when running test networks.
4938 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
4940 o Minor bugfixes (Linux seccomp2 sandbox):
4941 - Add permission to run the sched_yield() and sigaltstack() system
4942 calls, in order to support versions of Tor compiled with asan or
4943 ubsan code that use these calls. Now "sandbox 1" and
4944 "--enable-expensive-hardening" should be compatible on more
4945 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
4947 o Minor bugfixes (logging):
4948 - Downgrade a harmless log message about the
4949 pending_entry_connections list from "warn" to "info". Mitigates
4951 - Log a more accurate message when we fail to dump a microdescriptor.
4952 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
4953 - When logging a directory ownership mismatch, log the owning
4954 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
4955 - When we are unable to remove the bw_accounting file, do not warn
4956 if the reason we couldn't remove it was that it didn't exist.
4957 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
4959 o Minor bugfixes (memory leak):
4960 - Fix a series of slow memory leaks related to parsing torrc files
4961 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
4962 - Avoid a small memory leak when informing worker threads about
4963 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
4964 - Fix a small memory leak when receiving AF_UNIX connections on a
4965 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
4966 - When moving a signed descriptor object from a source to an
4967 existing destination, free the allocated memory inside that
4968 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
4969 - Fix a memory leak and use-after-free error when removing entries
4970 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
4971 0.2.5.5-alpha. Patch from "cypherpunks".
4972 - Fix a small, uncommon memory leak that could occur when reading a
4973 truncated ed25519 key file. Fixes bug 18956; bugfix
4976 o Minor bugfixes (option parsing):
4977 - Count unix sockets when counting client listeners (SOCKS, Trans,
4978 NATD, and DNS). This has no user-visible behavior changes: these
4979 options are set once, and never read. Required for correct
4980 behavior in ticket 17178. Fixes bug 19677; bugfix on
4981 0.2.6.3-alpha. Patch by teor.
4983 o Minor bugfixes (options):
4984 - Check the consistency of UseEntryGuards and EntryNodes more
4985 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
4987 - Stop changing the configured value of UseEntryGuards on
4988 authorities and Tor2web clients. Fixes bug 20074; bugfix on
4989 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
4992 o Minor bugfixes (relay):
4993 - Ensure relays don't make multiple connections during bootstrap.
4994 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
4995 - Do not try to parallelize workers more than 16x without the user
4996 explicitly configuring us to do so, even if we do detect more than
4997 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4999 o Minor bugfixes (testing):
5000 - The test-stem and test-network makefile targets now depend only on
5001 the tor binary that they are testing. Previously, they depended on
5002 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
5003 patch from "cypherpunks".
5004 - Allow clients to retry HSDirs much faster in test networks. Fixes
5005 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5006 - Avoid a unit test failure on systems with over 16 detectable CPU
5007 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5008 - Let backtrace tests work correctly under AddressSanitizer:
5009 disable ASAN's detection of segmentation faults while running
5010 test_bt.sh, so that we can make sure that our own backtrace
5011 generation code works. Fixes bug 18934; bugfix
5012 on 0.2.5.2-alpha. Patch from "cypherpunks".
5013 - Fix the test-network-all target on out-of-tree builds by using the
5014 correct path to the test driver script. Fixes bug 19421; bugfix
5016 - Stop spurious failures in the local interface address discovery
5017 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
5019 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
5020 removed the ECDH ciphers which caused the tests to fail on
5021 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
5022 - The tor_tls_server_info_callback unit test no longer crashes when
5023 debug-level logging is turned on. Fixes bug 20041; bugfix
5026 o Minor bugfixes (time):
5027 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5028 bugfix on all released tor versions.
5029 - When computing the difference between two times in milliseconds,
5030 we now round to the nearest millisecond correctly. Previously, we
5031 could sometimes round in the wrong direction. Fixes bug 19428;
5032 bugfix on 0.2.2.2-alpha.
5034 o Minor bugfixes (Tor2web):
5035 - Prevent Tor2web clients from running hidden services: these services
5036 are not anonymous due to the one-hop client paths. Fixes bug
5037 19678. Patch by teor.
5039 o Minor bugfixes (user interface):
5040 - Display a more accurate number of suppressed messages in the log
5041 rate-limiter. Previously, there was a potential integer overflow
5042 in the counter. Now, if the number of messages hits a maximum, the
5043 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5045 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5046 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5048 o Code simplification and refactoring:
5049 - Remove redundant declarations of the MIN macro. Closes
5051 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5052 Closes ticket 18462; patch from "icanhasaccount".
5053 - Split the 600-line directory_handle_command_get function into
5054 separate functions for different URL types. Closes ticket 16698.
5057 - Add module-level internal documentation for 36 C files that
5058 previously didn't have a high-level overview. Closes ticket 20385.
5059 - Correct the IPv6 syntax in our documentation for the
5060 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
5061 - Correct the minimum bandwidth value in torrc.sample, and queue a
5062 corresponding change for torrc.minimal. Closes ticket 20085.
5063 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5064 ticket 19153. Patch from "U+039b".
5065 - Module-level documentation for several more modules. Closes
5066 tickets 19287 and 19290.
5067 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5068 19504; bugfix on 0.2.7.3-rc.
5069 - Document the default PathsNeededToBuildCircuits value that's used
5070 by clients when the directory authorities don't set
5071 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
5072 Patch by teor, reported by Jesse V.
5073 - Fix manual for the User option: it takes a username, not a UID.
5074 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5076 - Fix the description of the --passphrase-fd option in the
5077 tor-gencert manpage. The option is used to pass the number of a
5078 file descriptor to read the passphrase from, not to read the file
5079 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5082 - We no longer include the (dead, deprecated) bufferevent code in
5083 Tor. Closes ticket 19450. Based on a patch from "U+039b".
5086 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5087 "GETINFO dir-usage" controller request, which were only available
5088 via a compile-time option in Tor anyway. Feature was added in
5089 0.2.2.1-alpha. Resolves ticket 19035.
5090 - There is no longer a compile-time option to disable support for
5091 TransPort. (If you don't want TransPort, just don't use it.) Patch
5092 from "U+039b". Closes ticket 19449.
5095 - Run more workqueue tests as part of "make check". These had
5096 previously been implemented, but you needed to know special
5097 command-line options to enable them.
5098 - We now have unit tests for our code to reject zlib "compression
5099 bombs". (Fortunately, the code works fine.)
5102 Changes in version 0.2.8.11 - 2016-12-08
5103 Tor 0.2.8.11 backports fixes for additional portability issues that
5104 could prevent Tor from building correctly on OSX Sierra, or with
5105 OpenSSL 1.1. Affected users should upgrade; others can safely stay
5108 o Minor bugfixes (portability):
5109 - Avoid compilation errors when building on OSX Sierra. Sierra began
5110 to support the getentropy() and clock_gettime() APIs, but created
5111 a few problems in doing so. Tor 0.2.9 has a more thorough set of
5112 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
5113 monotonic time interfaces. Fixes bug 20865. Bugfix
5116 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5117 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
5118 architectures. Closes ticket 20588.
5121 Changes in version 0.2.8.10 - 2016-12-02
5122 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
5123 unusable after they left standby mode. It also backports fixes for
5124 a few portability issues and a small but problematic memory leak.
5126 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
5127 - When Tor leaves standby because of a new application request, open
5128 circuits as needed to serve that request. Previously, we would
5129 potentially wait a very long time. Fixes part of bug 19969; bugfix
5132 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
5133 - Clients now respond to new application stream requests immediately
5134 when they arrive, rather than waiting up to one second before
5135 starting to handle them. Fixes part of bug 19969; bugfix
5138 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
5139 - Work around a bug in the OSX 10.12 SDK that would prevent us from
5140 successfully targeting earlier versions of OSX. Resolves
5143 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5144 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
5145 20551; bugfix on 0.2.1.1-alpha.
5147 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
5148 - Work around a memory leak in OpenSSL 1.1 when encoding public
5149 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
5151 o Minor features (geoip):
5152 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
5156 Changes in version 0.2.8.9 - 2016-10-17
5157 Tor 0.2.8.9 backports a fix for a security hole in previous versions
5158 of Tor that would allow a remote attacker to crash a Tor client,
5159 hidden service, relay, or authority. All Tor users should upgrade to
5160 this version, or to 0.2.9.4-alpha. Patches will be released for older
5163 o Major features (security fixes, also in 0.2.9.4-alpha):
5164 - Prevent a class of security bugs caused by treating the contents
5165 of a buffer chunk as if they were a NUL-terminated string. At
5166 least one such bug seems to be present in all currently used
5167 versions of Tor, and would allow an attacker to remotely crash
5168 most Tor instances, especially those compiled with extra compiler
5169 hardening. With this defense in place, such bugs can't crash Tor,
5170 though we should still fix them as they occur. Closes ticket
5171 20384 (TROVE-2016-10-001).
5173 o Minor features (geoip):
5174 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
5178 Changes in version 0.2.8.8 - 2016-09-23
5179 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
5180 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
5181 who select public relays as their bridges.
5183 o Major bugfixes (crash):
5184 - Fix a complicated crash bug that could affect Tor clients
5185 configured to use bridges when replacing a networkstatus consensus
5186 in which one of their bridges was mentioned. OpenBSD users saw
5187 more crashes here, but all platforms were potentially affected.
5188 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5190 o Major bugfixes (relay, OOM handler):
5191 - Fix a timing-dependent assertion failure that could occur when we
5192 tried to flush from a circuit after having freed its cells because
5193 of an out-of-memory condition. Fixes bug 20203; bugfix on
5194 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5197 o Minor feature (fallback directories):
5198 - Remove broken fallbacks from the hard-coded fallback directory
5199 list. Closes ticket 20190; patch by teor.
5201 o Minor features (geoip):
5202 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5206 Changes in version 0.2.8.7 - 2016-08-24
5207 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
5208 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
5209 who sets the ReachableAddresses option, and all bridges, are strongly
5210 encouraged to upgrade.
5212 o Directory authority changes:
5213 - The "Tonga" bridge authority has been retired; the new bridge
5214 authority is "Bifroest". Closes tickets 19728 and 19690.
5216 o Major bugfixes (client, security):
5217 - Only use the ReachableAddresses option to restrict the first hop
5218 in a path. In earlier versions of 0.2.8.x, it would apply to
5219 every hop in the path, with a possible degradation in anonymity
5220 for anyone using an uncommon ReachableAddress setting. Fixes bug
5221 19973; bugfix on 0.2.8.2-alpha.
5223 o Minor features (geoip):
5224 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5227 o Minor bugfixes (compilation):
5228 - Remove an inappropriate "inline" in tortls.c that was causing
5229 warnings on older versions of GCC. Fixes bug 19903; bugfix
5232 o Minor bugfixes (fallback directories):
5233 - Avoid logging a NULL string pointer when loading fallback
5234 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5235 and 0.2.8.1-alpha. Report and patch by "rubiate".
5238 Changes in version 0.2.8.6 - 2016-08-02
5240 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5242 The Tor 0.2.8 series improves client bootstrapping performance,
5243 completes the authority-side implementation of improved identity
5244 keys for relays, and includes numerous bugfixes and performance
5245 improvements throughout the program. This release continues to
5246 improve the coverage of Tor's test suite. For a full list of
5247 changes since Tor 0.2.7, see the ReleaseNotes file.
5249 Below is a list of the changes since Tor 0.2.7.
5251 o New system requirements:
5252 - Tor no longer attempts to support platforms where the "time_t"
5253 type is unsigned. (To the best of our knowledge, only OpenVMS does
5254 this, and Tor has never actually built on OpenVMS.) Closes
5256 - Tor no longer supports versions of OpenSSL with a broken
5257 implementation of counter mode. (This bug was present in OpenSSL
5258 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
5259 longer runs with, these versions.
5260 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
5261 later (released in 2008 and 2009 respectively). If you are
5262 building Tor from the git repository instead of from the source
5263 distribution, and your tools are older than this, you will need to
5264 upgrade. Closes ticket 17732.
5266 o Directory authority changes:
5267 - Update the V3 identity key for the dannenberg directory authority:
5268 it was changed on 18 November 2015. Closes task 17906. Patch
5270 - Urras is no longer a directory authority. Closes ticket 19271.
5272 o Major features (directory system):
5273 - Include a trial list of default fallback directories, based on an
5274 opt-in survey of suitable relays. Doing this should make clients
5275 bootstrap more quickly and reliably, and reduce the load on the
5276 directory authorities. Closes ticket 15775. Patch by teor.
5277 Candidates identified using an OnionOO script by weasel, teor,
5278 gsathya, and karsten.
5279 - Previously only relays that explicitly opened a directory port
5280 (DirPort) accepted directory requests from clients. Now all
5281 relays, with and without a DirPort, accept and serve tunneled
5282 directory requests that they receive through their ORPort. You can
5283 disable this behavior using the new DirCache option. Closes
5285 - When bootstrapping multiple consensus downloads at a time, use the
5286 first one that starts downloading, and close the rest. This
5287 reduces failures when authorities or fallback directories are slow
5288 or down. Together with the code for feature 15775, this feature
5289 should reduces failures due to fallback churn. Implements ticket
5290 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
5293 o Major features (security, Linux):
5294 - When Tor starts as root on Linux and is told to switch user ID, it
5295 can now retain the capability to bind to low ports. By default,
5296 Tor will do this only when it's switching user ID and some low
5297 ports have been configured. You can change this behavior with the
5298 new option KeepBindCapabilities. Closes ticket 8195.
5300 o Major bugfixes (client, bootstrapping):
5301 - Check if bootstrap consensus downloads are still needed when the
5302 linked connection attaches. This prevents tor making unnecessary
5303 begindir-style connections, which are the only directory
5304 connections tor clients make since the fix for 18483 was merged.
5305 - Fix some edge cases where consensus download connections may not
5306 have been closed, even though they were not needed. Related to fix
5308 - Make relays retry consensus downloads the correct number of times,
5309 rather than the more aggressive client retry count. Fixes part of
5312 o Major bugfixes (dns proxy mode, crash):
5313 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5314 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5316 o Major bugfixes (ed25519, voting):
5317 - Actually enable support for authorities to match routers by their
5318 Ed25519 identities. Previously, the code had been written, but
5319 some debugging code that had accidentally been left in the
5320 codebase made it stay turned off. Fixes bug 17702; bugfix
5322 - When collating votes by Ed25519 identities, authorities now
5323 include a "NoEdConsensus" flag if the ed25519 value (or lack
5324 thereof) for a server does not reflect the majority consensus.
5325 Related to bug 17668; bugfix on 0.2.7.2-alpha.
5326 - When generating a vote with keypinning disabled, never include two
5327 entries for the same ed25519 identity. This bug was causing
5328 authorities to generate votes that they could not parse when a
5329 router violated key pinning by changing its RSA identity but
5330 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
5331 18318. Bugfix on 0.2.7.2-alpha.
5333 o Major bugfixes (key management):
5334 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5335 pointer to the previous (uninitialized) key value. The impact here
5336 should be limited to a difficult-to-trigger crash, if OpenSSL is
5337 running an engine that makes key generation failures possible, or
5338 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5339 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5342 o Major bugfixes (security, client, DNS proxy):
5343 - Stop a crash that could occur when a client running with DNSPort
5344 received a query with multiple address types, and the first
5345 address type was not supported. Found and fixed by Scott Dial.
5346 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5348 o Major bugfixes (security, compilation):
5349 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
5350 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
5351 cause a compiler warning, thereby making other checks fail, and
5352 needlessly disabling compiler-hardening support. Fixes one case of
5353 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
5354 - Repair hardened builds under the clang compiler. Previously, our
5355 use of _FORTIFY_SOURCE would conflict with clang's address
5356 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
5358 o Major bugfixes (security, pointers):
5359 - Avoid a difficult-to-trigger heap corruption attack when extending
5360 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5361 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5362 Reported by Guido Vranken.
5364 o Major bugfixes (testing):
5365 - Fix a bug that would block 'make test-network-all' on systems where
5366 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
5368 o Major bugfixes (user interface):
5369 - Correctly give a warning in the cases where a relay is specified
5370 by nickname, and one such relay is found, but it is not officially
5371 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
5373 o Minor features (accounting):
5374 - Added two modes to the AccountingRule option: One for limiting
5375 only the number of bytes sent ("AccountingRule out"), and one for
5376 limiting only the number of bytes received ("AccountingRule in").
5377 Closes ticket 15989; patch from "unixninja92".
5379 o Minor features (bug-resistance):
5380 - Make Tor survive errors involving connections without a
5381 corresponding event object. Previously we'd fail with an
5382 assertion; now we produce a log message. Related to bug 16248.
5383 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
5384 level code, to harden against accidental failures to NUL-
5385 terminate. Part of ticket 17852. Patch from jsturgix. Found
5388 o Minor features (build):
5389 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
5390 as having possible IPFW support. Closes ticket 18448. Patch from
5392 - Since our build process now uses "make distcheck", we no longer
5393 force "make dist" to depend on "make check". Closes ticket 17893;
5394 patch from "cypherpunks".
5395 - Tor now builds once again with the recent OpenSSL 1.1 development
5396 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
5397 tracking OpenSSL 1.1 development as it has progressed, and fixing
5398 numerous compatibility issues as they arose. See tickets
5399 17549, 17921, 17984, 19499, and 18286.
5400 - When building manual pages, set the timezone to "UTC", so that the
5401 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
5402 Patch from intrigeri.
5404 o Minor features (clients):
5405 - Make clients, onion services, and bridge relays always use an
5406 encrypted begindir connection for directory requests. Resolves
5407 ticket 18483. Patch by teor.
5409 o Minor features (controller):
5410 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
5411 controllers can examine the the reject rules added by
5412 ExitPolicyRejectPrivate. This makes it easier for stem to display
5414 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
5415 tickets 16774 and 17817. Patch by George Tankersley.
5416 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
5417 service descriptor from a service's local hidden service
5418 descriptor cache. Closes ticket 14846.
5420 o Minor features (crypto):
5421 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
5422 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
5424 - Improve performance when hashing non-multiple of 8 sized buffers,
5425 based on Andrew Moon's public domain SipHash-2-4 implementation.
5426 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
5427 - Validate the hard-coded Diffie-Hellman parameters and ensure that
5428 p is a safe prime, and g is a suitable generator. Closes
5430 - When allocating a digest state object, allocate no more space than
5431 we actually need. Previously, we would allocate as much space as
5432 the state for the largest algorithm would need. This change saves
5433 up to 672 bytes per circuit. Closes ticket 17796.
5435 o Minor features (directory downloads):
5436 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
5437 directory mirrors. The default is 1; set it to 0 to disable
5438 fallbacks. Implements ticket 17576. Patch by teor.
5439 - Wait for busy authorities and fallback directories to become non-
5440 busy when bootstrapping. (A similar change was made in 6c443e987d
5441 for directory caches chosen from the consensus.) Closes ticket
5442 17864; patch by teor.
5444 o Minor features (geoip):
5445 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
5448 o Minor features (hidden service directory):
5449 - Streamline relay-side hsdir handling: when relays consider whether
5450 to accept an uploaded hidden service descriptor, they no longer
5451 check whether they are one of the relays in the network that is
5452 "supposed" to handle that descriptor. Implements ticket 18332.
5454 o Minor features (IPv6):
5455 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
5456 to 1, tor prefers IPv6 directory addresses.
5457 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
5458 avoids using IPv4 for client OR and directory connections.
5459 - Add address policy assume_action support for IPv6 addresses.
5460 - Add an argument 'ipv6=address:orport' to the DirAuthority and
5461 FallbackDir torrc options, to specify an IPv6 address for an
5462 authority or fallback directory. Add hard-coded ipv6 addresses for
5463 directory authorities that have them. Closes ticket 17327; patch
5464 from Nick Mathewson and teor.
5465 - Allow users to configure directory authorities and fallback
5466 directory servers with IPv6 addresses and ORPorts. Resolves
5468 - Limit IPv6 mask bits to 128.
5469 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
5470 17638; bugfix on 0.0.2pre8. Patch by teor.
5471 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
5472 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
5473 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
5474 - Warn when comparing against an AF_UNSPEC address in a policy, it's
5475 almost always a bug. Closes ticket 17863; patch by teor.
5476 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
5477 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
5479 o Minor features (Linux seccomp2 sandbox):
5480 - Reject attempts to change our Address with "Sandbox 1" enabled.
5481 Changing Address with Sandbox turned on would never actually work,
5482 but previously it would fail in strange and confusing ways. Found
5485 o Minor features (logging):
5486 - When logging to syslog, allow a tag to be added to the syslog
5487 identity (the string prepended to every log message). The tag can
5488 be configured with SyslogIdentityTag and defaults to none. Setting
5489 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
5492 o Minor features (portability):
5493 - Use timingsafe_memcmp() where available. Closes ticket 17944;
5494 patch from <logan@hackers.mu>.
5496 o Minor features (relay, address discovery):
5497 - Add a family argument to get_interface_addresses_raw() and
5498 subfunctions to make network interface address interogation more
5499 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
5500 types of interfaces from the operating system. Resolves
5502 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
5503 fails to enumerate interface addresses using the platform-specific
5504 API, have it rely on the UDP socket fallback technique to try and
5505 find out what IP addresses (both IPv4 and IPv6) our machine has.
5506 Resolves ticket 17951.
5508 o Minor features (replay cache):
5509 - The replay cache now uses SHA256 instead of SHA1. Implements
5510 feature 8961. Patch by teor, issue reported by rransom.
5512 o Minor features (robustness):
5513 - Exit immediately with an error message if the code attempts to use
5514 Libevent without having initialized it. This should resolve some
5515 frequently-made mistakes in our unit tests. Closes ticket 18241.
5517 o Minor features (security, clock):
5518 - Warn when the system clock appears to move back in time (when the
5519 state file was last written in the future). Tor doesn't know that
5520 consensuses have expired if the clock is in the past. Patch by
5521 teor. Implements ticket 17188.
5523 o Minor features (security, exit policies):
5524 - ExitPolicyRejectPrivate now rejects more private addresses by
5525 default. Specifically, it now rejects the relay's outbound bind
5526 addresses (if configured), and the relay's configured port
5527 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
5528 0.2.0.11-alpha. Patch by teor.
5530 o Minor features (security, memory erasure):
5531 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5532 zero size. Check size argument to memwipe() for underflow. Fixes
5533 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5535 - Set the unused entries in a smartlist to NULL. This helped catch
5536 a (harmless) bug, and shouldn't affect performance too much.
5537 Implements ticket 17026.
5538 - Use SecureMemoryWipe() function to securely clean memory on
5539 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
5540 Implements feature 17986.
5541 - Use explicit_bzero or memset_s when present. Previously, we'd use
5542 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
5543 from <logan@hackers.mu> and <selven@hackers.mu>.
5545 o Minor features (security, RNG):
5546 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
5547 positively are not allowed to fail. Previously we depended on
5548 internal details of OpenSSL's behavior. Closes ticket 17686.
5549 - Never use the system entropy output directly for anything besides
5550 seeding the PRNG. When we want to generate important keys, instead
5551 of using system entropy directly, we now hash it with the PRNG
5552 stream. This may help resist certain attacks based on broken OS
5553 entropy implementations. Closes part of ticket 17694.
5554 - Use modern system calls (like getentropy() or getrandom()) to
5555 generate strong entropy on platforms that have them. Closes
5558 o Minor features (security, win32):
5559 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
5560 attack. Fixes bug 18123; bugfix on all tor versions. Patch
5563 o Minor features (unix domain sockets):
5564 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
5565 Unix domain sockets without checking the permissions on the parent
5566 directory. (Tor checks permissions by default because some
5567 operating systems only check permissions on the parent directory.
5568 However, some operating systems do look at permissions on the
5569 socket, and tor's default check is unneeded.) Closes ticket 18458.
5572 o Minor features (unix file permissions):
5573 - Defer creation of Unix sockets until after setuid. This avoids
5574 needing CAP_CHOWN and CAP_FOWNER when using systemd's
5575 CapabilityBoundingSet, or chown and fowner when using SELinux.
5576 Implements part of ticket 17562. Patch from Jamie Nguyen.
5577 - If any directory created by Tor is marked as group readable, the
5578 filesystem group is allowed to be either the default GID or the
5579 root user. Allowing root to read the DataDirectory prevents the
5580 need for CAP_READ_SEARCH when using systemd's
5581 CapabilityBoundingSet, or dac_read_search when using SELinux.
5582 Implements part of ticket 17562. Patch from Jamie Nguyen.
5583 - Introduce a new DataDirectoryGroupReadable option. If it is set to
5584 1, the DataDirectory will be made readable by the default GID.
5585 Implements part of ticket 17562. Patch from Jamie Nguyen.
5587 o Minor bugfixes (accounting):
5588 - The max bandwidth when using 'AccountRule sum' is now correctly
5589 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
5592 o Minor bugfixes (assert, portability):
5593 - Fix an assertion failure in memarea.c on systems where "long" is
5594 shorter than the size of a pointer. Fixes bug 18716; bugfix
5597 o Minor bugfixes (bootstrap):
5598 - Consistently use the consensus download schedule for authority
5599 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5601 o Minor bugfixes (build):
5602 - Avoid spurious failures from configure files related to calling
5603 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
5604 0.2.0.1-alpha. Patch from "cypherpunks".
5605 - Do not link the unit tests against both the testing and non-
5606 testing versions of the static libraries. Fixes bug 18490; bugfix
5608 - Resolve warnings when building on systems that are concerned with
5609 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5611 - Silence spurious clang-scan warnings in the ed25519_donna code by
5612 explicitly initializing some objects. Fixes bug 18384; bugfix on
5613 0.2.7.2-alpha. Patch by teor.
5614 - When libscrypt.h is found, but no libscrypt library can be linked,
5615 treat libscrypt as absent. Fixes bug 19161; bugfix
5617 - Cause the unit tests to compile correctly on mingw64 versions that
5618 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5619 - Don't try to use the pthread_condattr_setclock() function unless
5620 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
5621 17819; bugfix on 0.2.6.3-alpha.
5622 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
5624 - Fix search for libevent libraries on OpenBSD (and other systems
5625 that install libevent 1 and libevent 2 in parallel). Fixes bug
5626 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
5627 - Isolate environment variables meant for tests from the rest of the
5628 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
5629 - Mark all object files that include micro-revision.i as depending
5630 on it, so as to make parallel builds more reliable. Fixes bug
5631 17826; bugfix on 0.2.5.1-alpha.
5632 - Remove config.log only from make distclean, not from make clean.
5633 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
5634 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
5636 - Remove an #endif from configure.ac so that we correctly detect the
5637 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
5640 o Minor bugfixes (client, bootstrap):
5641 - Count receipt of new microdescriptors as progress towards
5642 bootstrapping. Previously, with EntryNodes set, Tor might not
5643 successfully repopulate the guard set on bootstrapping. Fixes bug
5644 16825; bugfix on 0.2.3.1-alpha.
5646 o Minor bugfixes (code correctness):
5647 - Fix a bad memory handling bug that would occur if we had queued a
5648 cell on a channel's incoming queue. Fortunately, we can't actually
5649 queue a cell like that as our code is constructed today, but it's
5650 best to avoid this kind of error, even if there isn't any code
5651 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
5652 - Assert that allocated memory held by the reputation code is freed
5653 according to its internal counters. Fixes bug 17753; bugfix
5655 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
5657 - Update to the latest version of Trunnel, which tries harder to
5658 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
5659 by clang address sanitizer. Fixes bug 18373; bugfix
5661 - When closing an entry connection, generate a warning if we should
5662 have sent an end cell for it but we haven't. Fixes bug 17876;
5663 bugfix on 0.2.3.2-alpha.
5665 o Minor bugfixes (configuration):
5666 - Fix a tiny memory leak when parsing a port configuration ending in
5667 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
5669 o Minor bugfixes (containers):
5670 - If we somehow attempt to construct a heap with more than
5671 1073741822 elements, avoid an integer overflow when maintaining
5672 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
5674 o Minor bugfixes (controller, microdescriptors):
5675 - Make GETINFO dir/status-vote/current/consensus conform to the
5676 control specification by returning "551 Could not open cached
5677 consensus..." when not caching consensuses. Fixes bug 18920;
5678 bugfix on 0.2.2.6-alpha.
5680 o Minor bugfixes (crypto):
5681 - Check the return value of HMAC() and assert on failure. Fixes bug
5682 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
5684 o Minor bugfixes (directories):
5685 - When fetching extrainfo documents, compare their SHA256 digests
5686 and Ed25519 signing key certificates with the routerinfo that led
5687 us to fetch them, rather than with the most recent routerinfo.
5688 Otherwise we generate many spurious warnings about mismatches.
5689 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
5690 - When generating a URL for a directory server on an IPv6 address,
5691 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
5692 on 0.2.3.9-alpha. Patch from Malek.
5694 o Minor bugfixes (downloading):
5695 - Predict more correctly whether we'll be downloading over HTTP when
5696 we determine the maximum length of a URL. This should avoid a
5697 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5700 o Minor bugfixes (exit policies, security):
5701 - Refresh an exit relay's exit policy when interface addresses
5702 change. Previously, tor only refreshed the exit policy when the
5703 configured external address changed. Fixes bug 18208; bugfix on
5704 0.2.7.3-rc. Patch by teor.
5706 o Minor bugfixes (fallback directories):
5707 - Mark fallbacks as "too busy" when they return a 503 response,
5708 rather than just marking authorities. Fixes bug 17572; bugfix on
5709 0.2.4.7-alpha. Patch by teor.
5710 - When requesting extrainfo descriptors from a trusted directory
5711 server, check whether it is an authority or a fallback directory
5712 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
5713 0.2.4.7-alpha. Reported by atagar, patch by teor.
5715 o Minor bugfixes (hidden service, client):
5716 - Handle the case where the user makes several fast consecutive
5717 requests to the same .onion address. Previously, the first six
5718 requests would each trigger a descriptor fetch, each picking a
5719 directory (there are 6 overall) and the seventh one would fail
5720 because no directories were left, thereby triggering a close on
5721 all current directory connections asking for the hidden service.
5722 The solution here is to not close the connections if we have
5723 pending directory fetches. Fixes bug 15937; bugfix
5726 o Minor bugfixes (hidden service, control port):
5727 - Add the onion address to the HS_DESC event for the UPLOADED action
5728 both on success or failure. It was previously hardcoded with
5729 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
5731 o Minor bugfixes (hidden service, directory):
5732 - Bridges now refuse "rendezvous2" (hidden service descriptor)
5733 publish attempts. Suggested by ticket 18332.
5735 o Minor bugfixes (IPv6):
5736 - Update the limits in max_dl_per_request for IPv6 address length.
5737 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
5739 o Minor bugfixes (Linux seccomp2 sandbox):
5740 - Allow more syscalls when running with "Sandbox 1" enabled:
5741 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5742 some systems, these are required for Tor to start. Fixes bug
5743 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5744 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5745 so that get_interface_address6_via_udp_socket_hack() can work.
5746 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5747 - Allow the setrlimit syscall, and the prlimit and prlimit64
5748 syscalls, which some libc implementations use under the hood.
5749 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
5750 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
5751 enabled and no DNS resolvers configured. This should help TAILS
5752 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
5753 - Fix a crash when using offline master ed25519 keys with the Linux
5754 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
5755 - Allow statistics to be written to disk when "Sandbox 1" is
5756 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5757 0.2.6.1-alpha respectively.
5759 o Minor bugfixes (logging):
5760 - In log messages that include a function name, use __FUNCTION__
5761 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
5762 with clang __PRETTY_FUNCTION__ has extra information we don't
5763 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
5765 - Remove needless quotes from a log message about unparseable
5766 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
5767 - Scrub service name in "unrecognized service ID" log messages.
5768 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
5769 - When logging information about an unparsable networkstatus vote or
5770 consensus, do not say "vote" when we mean consensus. Fixes bug
5771 18368; bugfix on 0.2.0.8-alpha.
5772 - When we can't generate a signing key because OfflineMasterKey is
5773 set, do not imply that we should have been able to load it. Fixes
5774 bug 18133; bugfix on 0.2.7.2-alpha.
5775 - When logging a malformed hostname received through socks4, scrub
5776 it if SafeLogging says we should. Fixes bug 17419; bugfix
5779 o Minor bugfixes (memory safety):
5780 - Avoid freeing an uninitialized pointer when opening a socket fails
5781 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
5782 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
5784 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
5785 18672; bugfix on 0.2.5.1-alpha.
5786 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
5789 o Minor bugfixes (pluggable transports):
5790 - Avoid reporting a spurious error when we decide that we don't need
5791 to terminate a pluggable transport because it has already exited.
5792 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
5794 o Minor bugfixes (pointer arithmetic):
5795 - Fix a bug in memarea_alloc() that could have resulted in remote
5796 heap write access, if Tor had ever passed an unchecked size to
5797 memarea_alloc(). Fortunately, all the sizes we pass to
5798 memarea_alloc() are pre-checked to be less than 128 kilobytes.
5799 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
5802 o Minor bugfixes (private directory):
5803 - Prevent a race condition when creating private directories. Fixes
5804 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
5805 Patch from jsturgix. Found with Flawfinder.
5807 o Minor bugfixes (relays):
5808 - Check that both the ORPort and DirPort (if present) are reachable
5809 before publishing a relay descriptor. Otherwise, relays publish a
5810 descriptor with DirPort 0 when the DirPort reachability test takes
5811 longer than the ORPort reachability test. Fixes bug 18050; bugfix
5812 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
5813 - Resolve some edge cases where we might launch an ORPort
5814 reachability check even when DisableNetwork is set. Noticed while
5815 fixing bug 18616; bugfix on 0.2.3.9-alpha.
5817 o Minor bugfixes (relays, hidden services):
5818 - Refuse connection requests to private OR addresses unless
5819 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
5820 then refuse to send any cells to a private address. Fixes bugs
5821 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
5823 o Minor bugfixes (security, hidden services):
5824 - Prevent hidden services connecting to client-supplied rendezvous
5825 addresses that are reserved as internal or multicast. Fixes bug
5826 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
5828 o Minor bugfixes (statistics):
5829 - Consistently check for overflow in round_*_to_next_multiple_of
5830 functions, and add unit tests with additional and maximal values.
5831 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
5832 - Handle edge cases in the laplace functions: avoid division by
5833 zero, avoid taking the log of zero, and silence clang type
5834 conversion warnings using round and trunc. Add unit tests for edge
5835 cases with maximal values. Fixes part of bug 13192; bugfix
5837 - We now include consensus downloads via IPv6 in our directory-
5838 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
5840 o Minor bugfixes (test networks, IPv6):
5841 - Allow internal IPv6 addresses in descriptors in test networks.
5842 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
5845 o Minor bugfixes (testing):
5846 - Check the full results of SHA256 and SHA512 digests in the unit
5847 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
5848 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
5850 - Fix a small memory leak that would occur when the
5851 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
5852 bugfix on 0.2.5.2-alpha.
5853 - Make unit tests pass on IPv6-only systems, and systems without
5854 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
5855 bugfix on 0.2.7.3-rc. Patch by teor.
5856 - The test for log_heartbeat was incorrectly failing in timezones
5857 with non-integer offsets. Instead of comparing the end of the time
5858 string against a constant, compare it to the output of
5859 format_local_iso_time when given the correct input. Fixes bug
5860 18039; bugfix on 0.2.5.4-alpha.
5861 - We no longer disable assertions in the unit tests when coverage is
5862 enabled. Instead, we require you to say --disable-asserts-in-tests
5863 to the configure script if you need assertions disabled in the
5864 unit tests (for example, if you want to perform branch coverage).
5865 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
5867 o Minor bugfixes (time handling):
5868 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
5869 field. Otherwise, our unit tests crash on Windows. Fixes bug
5870 18977; bugfix on 0.2.2.25-alpha.
5871 - Avoid overflow in tor_timegm when parsing dates in and after 2038
5872 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
5873 0.0.2pre14. Patch by teor.
5875 o Minor bugfixes (tor-gencert):
5876 - Correctly handle the case where an authority operator enters a
5877 passphrase but sends an EOF before sending a newline. Fixes bug
5878 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
5880 o Code simplification and refactoring:
5881 - Clean up a little duplicated code in
5882 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
5884 - Decouple the list of streams waiting to be attached to circuits
5885 from the overall connection list. This change makes it possible to
5886 attach streams quickly while simplifying Tor's callgraph and
5887 avoiding O(N) scans of the entire connection list. Closes
5889 - Extract the more complicated parts of circuit_mark_for_close()
5890 into a new function that we run periodically before circuits are
5891 freed. This change removes more than half of the functions
5892 currently in the "blob". Closes ticket 17218.
5893 - Move logging of redundant policy entries in
5894 policies_parse_exit_policy_internal into its own function. Closes
5895 ticket 17608; patch from "juce".
5896 - Quote all the string interpolations in configure.ac -- even those
5897 which we are pretty sure can't contain spaces. Closes ticket
5898 17744. Patch from zerosion.
5899 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
5900 use them. Closes ticket 17926.
5901 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
5902 inplace, so there's no need to have a separate implementation for
5903 the non-inplace code. Closes ticket 18258. Patch from Malek.
5904 - Simplify return types for some crypto functions that can't
5905 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
5906 - When a direct directory request fails immediately on launch,
5907 instead of relaunching that request from inside the code that
5908 launches it, instead mark the connection for teardown. This change
5909 simplifies Tor's callback and prevents the directory-request
5910 launching code from invoking itself recursively. Closes
5914 - Add a description of the correct use of the '--keygen' command-
5915 line option. Closes ticket 17583; based on text by 's7r'.
5916 - Change build messages to refer to "Fedora" instead of "Fedora
5917 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
5918 Patches from "icanhasaccount" and "cypherpunks".
5919 - Document the contents of the 'datadir/keys' subdirectory in the
5920 manual page. Closes ticket 17621.
5921 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
5922 - Explain actual minima for BandwidthRate. Closes ticket 16382.
5923 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
5924 - Mention torspec URL in the manpage and point the reader to it
5925 whenever we mention a document that belongs in torspce. Fixes
5927 - Stop recommending use of nicknames to identify relays in our
5928 MapAddress documentation. Closes ticket 18312.
5931 - Remove client-side support for connecting to Tor relays running
5932 versions of Tor before 0.2.3.6-alpha. These relays didn't support
5933 the v3 TLS handshake protocol, and are no longer allowed on the
5934 Tor network. Implements the client side of ticket 11150. Based on
5935 patches by Tom van der Woerdt.
5936 - We no longer maintain an internal freelist in memarea.c.
5937 Allocators should be good enough to make this code unnecessary,
5938 and it's doubtful that it ever had any performance benefit.
5941 - Add unit tests to check for common RNG failure modes, such as
5942 returning all zeroes, identical values, or incrementing values
5943 (OpenSSL's rand_predictable feature). Patch by teor.
5944 - Always test both ed25519 backends, so that we can be sure that our
5945 batch-open replacement code works. Part of ticket 16794.
5946 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
5947 portion of ticket 16831.
5948 - Fix several warnings from clang's address sanitizer produced in
5950 - Log more information when the backtrace tests fail. Closes ticket
5951 17892. Patch from "cypherpunks."
5952 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
5953 util_format.c, directory.c, and options_validate.c. Closes tickets
5954 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
5956 - Treat backtrace test failures as expected on FreeBSD until we
5957 solve bug 17808. Closes ticket 18204.
5958 - Unit tests for directory_handle_command_get. Closes ticket 17004.
5959 Patch from Reinaldo de Souza Jr.
5962 Changes in version 0.2.7.6 - 2015-12-10
5963 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
5964 well as a minor bug in hidden service reliability.
5966 o Major bugfixes (guard selection):
5967 - Actually look at the Guard flag when selecting a new directory
5968 guard. When we implemented the directory guard design, we
5969 accidentally started treating all relays as if they have the Guard
5970 flag during guard selection, leading to weaker anonymity and worse
5971 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5974 o Minor features (geoip):
5975 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
5978 o Minor bugfixes (compilation):
5979 - When checking for net/pfvar.h, include netinet/in.h if possible.
5980 This fixes transparent proxy detection on OpenBSD. Fixes bug
5981 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
5982 - Fix a compilation warning with Clang 3.6: Do not check the
5983 presence of an address which can never be NULL. Fixes bug 17781.
5985 o Minor bugfixes (correctness):
5986 - When displaying an IPv6 exit policy, include the mask bits
5987 correctly even when the number is greater than 31. Fixes bug
5988 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
5989 - The wrong list was used when looking up expired intro points in a
5990 rend service object, causing what we think could be reachability
5991 issues for hidden services, and triggering a BUG log. Fixes bug
5992 16702; bugfix on 0.2.7.2-alpha.
5993 - Fix undefined behavior in the tor_cert_checksig function. Fixes
5994 bug 17722; bugfix on 0.2.7.2-alpha.
5997 Changes in version 0.2.7.5 - 2015-11-20
5998 The Tor 0.2.7 release series is dedicated to the memory of Tor user
5999 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6000 tirelessly to advocate human rights regardless of national borders,
6001 and oppose the encroachments of mass surveillance. He opposed national
6002 exceptionalism, he brought clarity to legal and policy debates, he
6003 understood and predicted the impact of mass surveillance on the world,
6004 and he laid the groundwork for resisting it. While serving on the Tor
6005 Project's board of directors, he brought us his uncompromising focus
6006 on technical excellence in the service of humankind. Caspar was an
6007 inimitable force for good and a wonderful friend. He was kind,
6008 humorous, generous, gallant, and believed we should protect one
6009 another without exception. We honor him here for his ideals, his
6010 efforts, and his accomplishments. Please honor his memory with works
6011 that would make him proud.
6013 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6015 The 0.2.7 series adds a more secure identity key type for relays,
6016 improves cryptography performance, resolves several longstanding
6017 hidden-service performance issues, improves controller support for
6018 hidden services, and includes small bugfixes and performance
6019 improvements throughout the program. This release series also includes
6020 more tests than before, and significant simplifications to which parts
6021 of Tor invoke which others. For a full list of changes, see below.
6023 o New system requirements:
6024 - Tor no longer includes workarounds to support Libevent versions
6025 before 1.3e. Libevent 2.0 or later is recommended. Closes
6027 - Tor no longer supports copies of OpenSSL that are missing support
6028 for Elliptic Curve Cryptography. (We began using ECC when
6029 available in 0.2.4.8-alpha, for more safe and efficient key
6030 negotiation.) In particular, support for at least one of P256 or
6031 P224 is now required, with manual configuration needed if only
6032 P224 is available. Resolves ticket 16140.
6033 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
6034 on an operating system that has not upgraded to OpenSSL 1.0 or
6035 later, and you compile Tor from source, you will need to install a
6036 more recent OpenSSL to link Tor against.) These versions of
6037 OpenSSL are still supported by the OpenSSL, but the numerous
6038 cryptographic improvements in later OpenSSL releases makes them a
6039 clear choice. Resolves ticket 16034.
6041 o Major features (controller):
6042 - Add the ADD_ONION and DEL_ONION commands that allow the creation
6043 and management of hidden services via the controller. Closes
6045 - New "GETINFO onions/current" and "GETINFO onions/detached"
6046 commands to get information about hidden services created via the
6047 controller. Part of ticket 6411.
6048 - New HSFETCH command to launch a request for a hidden service
6049 descriptor. Closes ticket 14847.
6050 - New HSPOST command to upload a hidden service descriptor. Closes
6051 ticket 3523. Patch by "DonnchaC".
6053 o Major features (Ed25519 identity keys, Proposal 220):
6054 - Add support for offline encrypted Ed25519 master keys. To use this
6055 feature on your tor relay, run "tor --keygen" to make a new master
6056 key (or to make a new signing key if you already have a master
6057 key). Closes ticket 13642.
6058 - All relays now maintain a stronger identity key, using the Ed25519
6059 elliptic curve signature format. This master key is designed so
6060 that it can be kept offline. Relays also generate an online
6061 signing key, and a set of other Ed25519 keys and certificates.
6062 These are all automatically regenerated and rotated as needed.
6063 Implements part of ticket 12498.
6064 - Directory authorities now vote on Ed25519 identity keys along with
6065 RSA1024 keys. Implements part of ticket 12498.
6066 - Directory authorities track which Ed25519 identity keys have been
6067 used with which RSA1024 identity keys, and do not allow them to
6068 vary freely. Implements part of ticket 12498.
6069 - Microdescriptors now include Ed25519 identity keys. Implements
6070 part of ticket 12498.
6071 - Add a --newpass option to allow changing or removing the
6072 passphrase of an encrypted key with tor --keygen. Implements part
6074 - Add a new OfflineMasterKey option to tell Tor never to try loading
6075 or generating a secret Ed25519 identity key. You can use this in
6076 combination with tor --keygen to manage offline and/or encrypted
6077 Ed25519 keys. Implements ticket 16944.
6078 - On receiving a HUP signal, check to see whether the Ed25519
6079 signing key has changed, and reload it if so. Closes ticket 16790.
6080 - Significant usability improvements for Ed25519 key management. Log
6081 messages are better, and the code can recover from far more
6082 failure conditions. Thanks to "s7r" for reporting and diagnosing
6085 o Major features (ECC performance):
6086 - Improve the runtime speed of Ed25519 signature verification by
6087 using Ed25519-donna's batch verification support. Implements
6089 - Improve the speed of Ed25519 operations and Curve25519 keypair
6090 generation when built targeting 32 bit x86 platforms with SSE2
6091 available. Implements ticket 16535.
6092 - Improve the runtime speed of Ed25519 operations by using the
6093 public-domain Ed25519-donna by Andrew M. ("floodyberry").
6094 Implements ticket 16467.
6095 - Improve the runtime speed of the ntor handshake by using an
6096 optimized curve25519 basepoint scalarmult implementation from the
6097 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
6098 ideas by Adam Langley. Implements ticket 9663.
6100 o Major features (Hidden services):
6101 - Hidden services, if using the EntryNodes option, are required to
6102 use more than one EntryNode, in order to avoid a guard discovery
6103 attack. (This would only affect people who had configured hidden
6104 services and manually specified the EntryNodes option with a
6105 single entry-node. The impact was that it would be easy to
6106 remotely identify the guard node used by such a hidden service.
6107 See ticket for more information.) Fixes ticket 14917.
6108 - Add the torrc option HiddenServiceNumIntroductionPoints, to
6109 specify a fixed number of introduction points. Its maximum value
6110 is 10 and default is 3. Using this option can increase a hidden
6111 service's reliability under load, at the cost of making it more
6112 visible that the hidden service is facing extra load. Closes
6114 - Remove the adaptive algorithm for choosing the number of
6115 introduction points, which used to change the number of
6116 introduction points (poorly) depending on the number of
6117 connections the HS sees. Closes ticket 4862.
6119 o Major features (onion key cross-certification):
6120 - Relay descriptors now include signatures of their own identity
6121 keys, made using the TAP and ntor onion keys. These signatures
6122 allow relays to prove ownership of their own onion keys. Because
6123 of this change, microdescriptors will no longer need to include
6124 RSA identity keys. Implements proposal 228; closes ticket 12499.
6126 o Major bugfixes (client-side privacy, also in 0.2.6.9):
6127 - Properly separate out each SOCKSPort when applying stream
6128 isolation. The error occurred because each port's session group
6129 was being overwritten by a default value when the listener
6130 connection was initialized. Fixes bug 16247; bugfix on
6131 0.2.6.3-alpha. Patch by "jojelino".
6133 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
6134 - Stop refusing to store updated hidden service descriptors on a
6135 client. This reverts commit 9407040c59218 (which indeed fixed bug
6136 14219, but introduced a major hidden service reachability
6137 regression detailed in bug 16381). This is a temporary fix since
6138 we can live with the minor issue in bug 14219 (it just results in
6139 some load on the network) but the regression of 16381 is too much
6140 of a setback. First-round fix for bug 16381; bugfix
6143 o Major bugfixes (hidden services):
6144 - Revert commit that made directory authorities assign the HSDir
6145 flag to relays without a DirPort; this was bad because such relays
6146 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6148 - When cannibalizing a circuit for an introduction point, always
6149 extend to the chosen exit node (creating a 4 hop circuit).
6150 Previously Tor would use the current circuit exit node, which
6151 changed the original choice of introduction point, and could cause
6152 the hidden service to skip excluded introduction points or
6153 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
6156 o Major bugfixes (memory leaks):
6157 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6158 17398; bugfix on 0.2.6.1-alpha.
6160 o Major bugfixes (open file limit):
6161 - The open file limit wasn't checked before calling
6162 tor_accept_socket_nonblocking(), which would make Tor exceed the
6163 limit. Now, before opening a new socket, Tor validates the open
6164 file limit just before, and if the max has been reached, return an
6165 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
6167 o Major bugfixes (security, correctness):
6168 - Fix an error that could cause us to read 4 bytes before the
6169 beginning of an openssl string. This bug could be used to cause
6170 Tor to crash on systems with unusual malloc implementations, or
6171 systems with unusual hardening installed. Fixes bug 17404; bugfix
6174 o Major bugfixes (stability, also in 0.2.6.10):
6175 - Stop crashing with an assertion failure when parsing certain kinds
6176 of malformed or truncated microdescriptors. Fixes bug 16400;
6177 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6178 by "cypherpunks_backup".
6179 - Stop random client-side assertion failures that could occur when
6180 connecting to a busy hidden service, or connecting to a hidden
6181 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6184 o Minor features (client, SOCKS):
6185 - Add GroupWritable and WorldWritable options to unix-socket based
6186 SocksPort and ControlPort options. These options apply to a single
6187 socket, and override {Control,Socks}SocketsGroupWritable. Closes
6189 - Relax the validation done to hostnames in SOCKS5 requests, and
6190 allow a single trailing '.' to cope with clients that pass FQDNs
6191 using that syntax to explicitly indicate that the domain name is
6192 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
6193 - Relax the validation of hostnames in SOCKS5 requests, allowing the
6194 character '_' to appear, in order to cope with domains observed in
6195 the wild that are serving non-RFC compliant records. Resolves
6198 o Minor features (client-side privacy):
6199 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6200 lifespan when IsolateSOCKSAuth and streams with SOCKS
6201 authentication are attached to the circuit. This allows
6202 applications like TorBrowser to manage circuit lifetime on their
6203 own. Implements feature 15482.
6204 - When logging malformed hostnames from SOCKS5 requests, respect
6205 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6207 o Minor features (clock-jump tolerance):
6208 - Recover better when our clock jumps back many hours, like might
6209 happen for Tails or Whonix users who start with a very wrong
6210 hardware clock, use Tor to discover a more accurate time, and then
6211 fix their clock. Resolves part of ticket 8766.
6213 o Minor features (command-line interface):
6214 - Make --hash-password imply --hush to prevent unnecessary noise.
6215 Closes ticket 15542. Patch from "cypherpunks".
6216 - Print a warning whenever we find a relative file path being used
6217 as torrc option. Resolves issue 14018.
6219 o Minor features (compilation):
6220 - Give a warning as early as possible when trying to build with an
6221 unsupported OpenSSL version. Closes ticket 16901.
6222 - Use C99 variadic macros when the compiler is not GCC. This avoids
6223 failing compilations on MSVC, and fixes a log-file-based race
6224 condition in our old workarounds. Original patch from Gisle Vanem.
6226 o Minor features (control protocol):
6227 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
6228 the control protocol. Resolves ticket 15358.
6230 o Minor features (controller):
6231 - Add DirAuthority lines for default directory authorities to the
6232 output of the "GETINFO config/defaults" command if not already
6233 present. Implements ticket 14840.
6234 - Controllers can now use "GETINFO hs/client/desc/id/..." to
6235 retrieve items from the client's hidden service descriptor cache.
6236 Closes ticket 14845.
6237 - Implement a new controller command "GETINFO status/fresh-relay-
6238 descs" to fetch a descriptor/extrainfo pair that was generated on
6239 demand just for the controller's use. Implements ticket 14784.
6241 o Minor features (directory authorities):
6242 - Directory authorities no longer vote against the "Fast", "Stable",
6243 and "HSDir" flags just because they were going to vote against
6244 "Running": if the consensus turns out to be that the router was
6245 running, then the authority's vote should count. Patch from Peter
6246 Retzlaff; closes issue 8712.
6248 o Minor features (directory authorities, security, also in 0.2.6.9):
6249 - The HSDir flag given by authorities now requires the Stable flag.
6250 For the current network, this results in going from 2887 to 2806
6251 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6252 attack by raising the effort for a relay to become Stable to
6253 require at the very least 7 days, while maintaining the 96 hours
6254 uptime requirement for HSDir. Implements ticket 8243.
6256 o Minor features (DoS-resistance):
6257 - Make it harder for attackers to overload hidden services with
6258 introductions, by blocking multiple introduction requests on the
6259 same circuit. Resolves ticket 15515.
6261 o Minor features (geoip):
6262 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6265 o Minor features (hidden services):
6266 - Add the new options "HiddenServiceMaxStreams" and
6267 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
6268 limit the maximum number of simultaneous streams per circuit, and
6269 optionally tear down the circuit when the limit is exceeded. Part
6271 - Client now uses an introduction point failure cache to know when
6272 to fetch or keep a descriptor in their cache. Previously, failures
6273 were recorded implicitly, but not explicitly remembered. Closes
6275 - Relays need to have the Fast flag to get the HSDir flag. As this
6276 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6277 drop. This change should make some attacks against the hidden
6278 service directory system harder. Fixes ticket 15963.
6279 - Turn on hidden service statistics collection by setting the torrc
6280 option HiddenServiceStatistics to "1" by default. (This keeps
6281 track only of the fraction of traffic used by hidden services, and
6282 the total number of hidden services in existence.) Closes
6284 - To avoid leaking HS popularity, don't cycle the introduction point
6285 when we've handled a fixed number of INTRODUCE2 cells but instead
6286 cycle it when a random number of introductions is reached, thus
6287 making it more difficult for an attacker to find out the amount of
6288 clients that have used the introduction point for a specific HS.
6289 Closes ticket 15745.
6291 o Minor features (logging):
6292 - Include the Tor version in all LD_BUG log messages, since people
6293 tend to cut and paste those into the bugtracker. Implements
6296 o Minor features (pluggable transports):
6297 - When launching managed pluggable transports on Linux systems,
6298 attempt to have the kernel deliver a SIGTERM on tor exit if the
6299 pluggable transport process is still running. Resolves
6301 - When launching managed pluggable transports, setup a valid open
6302 stdin in the child process that can be used to detect if tor has
6303 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
6304 can be used by implementations to detect this new behavior.
6305 Resolves ticket 15435.
6307 o Minor bugfixes (torrc exit policies):
6308 - In each instance above, usage advice is provided to avoid the
6309 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
6310 16069; bugfix on 0.2.4.7-alpha.
6311 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6312 produce IPv6 wildcard addresses. Previously they would produce
6313 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6314 of bug 16069; bugfix on 0.2.4.7-alpha.
6315 - When parsing torrc ExitPolicies, we now issue an info-level
6316 message when expanding an "accept/reject *" line to include both
6317 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
6318 - When parsing torrc ExitPolicies, we now warn for a number of cases
6319 where the user's intent is likely to differ from Tor's actual
6320 behavior. These include: using an IPv4 address with an accept6 or
6321 reject6 line; using "private" on an accept6 or reject6 line; and
6322 including any ExitPolicy lines after accept *:* or reject *:*.
6323 Related to ticket 16069.
6325 o Minor bugfixes (command-line interface):
6326 - When "--quiet" is provided along with "--validate-config", do not
6327 write anything to stdout on success. Fixes bug 14994; bugfix
6329 - When complaining about bad arguments to "--dump-config", use
6331 - Print usage information for --dump-config when it is used without
6332 an argument. Also, fix the error message to use different wording
6333 and add newline at the end. Fixes bug 15541; bugfix
6336 o Minor bugfixes (compilation):
6337 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6338 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6339 - Repair compilation with the most recent (unreleased, alpha)
6340 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
6342 o Minor bugfixes (compilation, also in 0.2.6.9):
6343 - Build with --enable-systemd correctly when libsystemd is
6344 installed, but systemd is not. Fixes bug 16164; bugfix on
6345 0.2.6.3-alpha. Patch from Peter Palfrader.
6347 o Minor bugfixes (configuration, unit tests):
6348 - Only add the default fallback directories when the DirAuthorities,
6349 AlternateDirAuthority, and FallbackDir directory config options
6350 are set to their defaults. The default fallback directory list is
6351 currently empty, this fix will only change tor's behavior when it
6352 has default fallback directories. Includes unit tests for
6353 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
6354 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
6356 o Minor bugfixes (controller):
6357 - Add the descriptor ID in each HS_DESC control event. It was
6358 missing, but specified in control-spec.txt. Fixes bug 15881;
6359 bugfix on 0.2.5.2-alpha.
6361 o Minor bugfixes (correctness):
6362 - For correctness, avoid modifying a constant string in
6363 handle_control_postdescriptor. Fixes bug 15546; bugfix
6365 - Remove side-effects from tor_assert() calls. This was harmless,
6366 because we never disable assertions, but it is bad style and
6367 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
6369 - When calling channel_free_list(), avoid calling smartlist_remove()
6370 while inside a FOREACH loop. This partially reverts commit
6371 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
6372 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
6374 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
6375 - Check for failures from crypto_early_init, and refuse to continue.
6376 A previous typo meant that we could keep going with an
6377 uninitialized crypto library, and would have OpenSSL initialize
6378 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6379 when implementing ticket 4900. Patch by "teor".
6381 o Minor bugfixes (hidden service):
6382 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6383 a client authorized hidden service. Fixes bug 15823; bugfix
6385 - Remove an extraneous newline character from the end of hidden
6386 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
6388 o Minor bugfixes (Linux seccomp2 sandbox):
6389 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
6390 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
6391 - Allow bridge authorities to run correctly under the seccomp2
6392 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
6393 - Add the "hidserv-stats" filename to our sandbox filter for the
6394 HiddenServiceStatistics option to work properly. Fixes bug 17354;
6395 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
6397 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
6398 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6399 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6400 on 0.2.6.3-alpha. Patch from "teor".
6402 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
6403 - Allow systemd connections to work with the Linux seccomp2 sandbox
6404 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6406 - Fix sandboxing to work when running as a relay, by allowing the
6407 renaming of secret_id_key, and allowing the eventfd2 and futex
6408 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
6411 o Minor bugfixes (logging):
6412 - When building Tor under Clang, do not include an extra set of
6413 parentheses in log messages that include function names. Fixes bug
6414 15269; bugfix on every released version of Tor when compiled with
6415 recent enough Clang.
6417 o Minor bugfixes (network):
6418 - When attempting to use fallback technique for network interface
6419 lookup, disregard loopback and multicast addresses since they are
6420 unsuitable for public communications.
6422 o Minor bugfixes (open file limit):
6423 - Fix set_max_file_descriptors() to set by default the max open file
6424 limit to the current limit when setrlimit() fails. Fixes bug
6425 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
6427 o Minor bugfixes (portability):
6428 - Check correctly for Windows socket errors in the workqueue
6429 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
6430 - Try harder to normalize the exit status of the Tor process to the
6431 standard-provided range. Fixes bug 16975; bugfix on every version
6433 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
6434 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
6436 o Minor bugfixes (relay):
6437 - Ensure that worker threads actually exit when a fatal error or
6438 shutdown is indicated. This fix doesn't currently affect the
6439 behavior of Tor, because Tor workers never indicates fatal error
6440 or shutdown except in the unit tests. Fixes bug 16868; bugfix
6442 - Fix a rarely-encountered memory leak when failing to initialize
6443 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
6445 - Unblock threads before releasing the work queue mutex to ensure
6446 predictable scheduling behavior. Fixes bug 16644; bugfix
6449 o Minor bugfixes (security, exit policies):
6450 - ExitPolicyRejectPrivate now also rejects the relay's published
6451 IPv6 address (if any), and any publicly routable IPv4 or IPv6
6452 addresses on any local interfaces. ticket 17027. Patch by "teor".
6453 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
6455 o Minor bugfixes (statistics):
6456 - Disregard the ConnDirectionStatistics torrc options when Tor is
6457 not a relay since in that mode of operation no sensible data is
6458 being collected and because Tor might run into measurement hiccups
6459 when running as a client for some time, then becoming a relay.
6460 Fixes bug 15604; bugfix on 0.2.2.35.
6462 o Minor bugfixes (systemd):
6463 - Tor's systemd unit file no longer contains extraneous spaces.
6464 These spaces would sometimes confuse tools like deb-systemd-
6465 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
6467 o Minor bugfixes (test networks):
6468 - When self-testing reachability, use ExtendAllowPrivateAddresses to
6469 determine if local/private addresses imply reachability. The
6470 previous fix used TestingTorNetwork, which implies
6471 ExtendAllowPrivateAddresses, but this excluded rare configurations
6472 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
6473 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
6474 issue discovered by CJ Ess.
6476 o Minor bugfixes (tests, also in 0.2.6.9):
6477 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6478 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6480 o Code simplification and refactoring:
6481 - Change the function that's called when we need to retry all
6482 downloads so that it only reschedules the downloads to happen
6483 immediately, rather than launching them all at once itself. This
6484 further simplifies Tor's callgraph.
6485 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
6486 to ensure they remain consistent and visible everywhere.
6487 - Move some format-parsing functions out of crypto.c and
6488 crypto_curve25519.c into crypto_format.c and/or util_format.c.
6489 - Move the client-only parts of init_keys() into a separate
6490 function. Closes ticket 16763.
6491 - Move the hacky fallback code out of get_interface_address6() into
6492 separate function and get it covered with unit-tests. Resolves
6494 - Refactor hidden service client-side cache lookup to intelligently
6495 report its various failure cases, and disentangle failure cases
6496 involving a lack of introduction points. Closes ticket 14391.
6497 - Remove some vestigial workarounds for the MSVC6 compiler. We
6498 haven't supported that in ages.
6499 - Remove the unused "nulterminate" argument from buf_pullup().
6500 - Simplify the microdesc_free() implementation so that it no longer
6501 appears (to code analysis tools) to potentially invoke a huge
6502 suite of other microdesc functions.
6503 - Simply the control graph further by deferring the inner body of
6504 directory_all_unreachable() into a callback. Closes ticket 16762.
6505 - The link authentication code has been refactored for better
6506 testability and reliability. It now uses code generated with the
6507 "trunnel" binary encoding generator, to reduce the risk of bugs
6508 due to programmer error. Done as part of ticket 12498.
6509 - Treat the loss of an owning controller as equivalent to a SIGTERM
6510 signal. This removes a tiny amount of duplicated code, and
6511 simplifies our callgraph. Closes ticket 16788.
6512 - Use our own Base64 encoder instead of OpenSSL's, to allow more
6513 control over the output. Part of ticket 15652.
6514 - When generating an event to send to the controller, we no longer
6515 put the event over the network immediately. Instead, we queue
6516 these events, and use a Libevent callback to deliver them. This
6517 change simplifies Tor's callgraph by reducing the number of
6518 functions from which all other Tor functions are reachable. Closes
6520 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
6521 that try to scan or compile every file on Unix won't decide that
6525 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
6526 - Improve the descriptions of statistics-related torrc options in
6527 the manpage to describe rationale and possible uses cases. Fixes
6529 - Improve the layout and formatting of ./configure --help messages.
6530 Closes ticket 15024. Patch from "cypherpunks".
6531 - Include a specific and (hopefully) accurate documentation of the
6532 torrc file's meta-format in doc/torrc_format.txt. This is mainly
6533 of interest to people writing programs to parse or generate torrc
6534 files. This document is not a commitment to long-term
6535 compatibility; some aspects of the current format are a bit
6536 ridiculous. Closes ticket 2325.
6537 - Include the TUNING document in our source tarball. It is referred
6538 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
6540 - Note that HiddenServicePorts can take a unix domain socket. Closes
6542 - Recommend a 40 GB example AccountingMax in torrc.sample rather
6543 than a 4 GB max. Closes ticket 16742.
6544 - Standardize on the term "server descriptor" in the manual page.
6545 Previously, we had used "router descriptor", "server descriptor",
6546 and "relay descriptor" interchangeably. Part of ticket 14987.
6547 - Advise users on how to configure separate IPv4 and IPv6 exit
6548 policies in the manpage and sample torrcs. Related to ticket 16069.
6549 - Fix an error in the manual page and comments for
6550 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
6551 required "ORPort connectivity". While this is true, it is in no
6552 way unique to the HSDir flag. Of all the flags, only HSDirs need a
6553 DirPort configured in order for the authorities to assign that
6554 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
6556 - Fix the usage message of tor-resolve(1) so that it no longer lists
6557 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
6560 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
6561 and always use the internal Base64 decoder. The internal decoder
6562 has been part of tor since 0.2.0.10-alpha, and no one should
6563 be using the OpenSSL one. Part of ticket 15652.
6564 - Remove the 'tor_strclear()' function; use memwipe() instead.
6565 Closes ticket 14922.
6566 - Remove the code that would try to aggressively flush controller
6567 connections while writing to them. This code was introduced in
6568 0.1.2.7-alpha, in order to keep output buffers from exceeding
6569 their limits. But there is no longer a maximum output buffer size,
6570 and flushing data in this way caused some undesirable recursions
6571 in our call graph. Closes ticket 16480.
6572 - The internal pure-C tor-fw-helper tool is now removed from the Tor
6573 distribution, in favor of the pure-Go clone available from
6574 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
6575 used by the C tor-fw-helper are not, in our opinion, very
6576 confidence- inspiring in their secure-programming techniques.
6577 Closes ticket 13338.
6580 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
6581 fingerprinting we now recommend pluggable transports; for forward-
6582 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
6583 - Remove the HidServDirectoryV2 option. Now all relays offer to
6584 store hidden service descriptors. Related to 16543.
6585 - Remove the VoteOnHidServDirectoriesV2 option, since all
6586 authorities have long set it to 1. Closes ticket 16543.
6587 - Remove the undocumented "--digests" command-line option. It
6588 complicated our build process, caused subtle build issues on
6589 multiple platforms, and is now redundant since we started
6590 including git version identifiers. Closes ticket 14742.
6591 - Tor no longer contains checks for ancient directory cache versions
6592 that didn't know about microdescriptors.
6593 - Tor no longer contains workarounds for stat files generated by
6594 super-old versions of Tor that didn't choose guards sensibly.
6597 - The test-network.sh script now supports performance testing.
6598 Requires corresponding chutney performance testing changes. Patch
6599 by "teor". Closes ticket 14175.
6600 - Add a new set of callgraph analysis scripts that use clang to
6601 produce a list of which Tor functions are reachable from which
6602 other Tor functions. We're planning to use these to help simplify
6603 our code structure by identifying illogical dependencies.
6604 - Add new 'test-full' and 'test-full-online' targets to run all
6605 tests, including integration tests with stem and chutney.
6606 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
6607 by-side in the same parent directory. Closes ticket 16903. Patch
6609 - Document use of coverity, clang static analyzer, and clang dynamic
6610 undefined behavior and address sanitizers in doc/HACKING. Include
6611 detailed usage instructions in the blacklist. Patch by "teor".
6612 Closes ticket 15817.
6613 - Make "bridges+hs" the default test network. This tests almost all
6614 tor functionality during make test-network, while allowing tests
6615 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
6616 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
6617 (chutney). Patches by "teor".
6618 - Make the test-workqueue test work on Windows by initializing the
6619 network before we begin.
6620 - New make target (make test-network-all) to run multiple applicable
6621 chutney test cases. Patch from Teor; closes 16953.
6622 - Now that OpenSSL has its own scrypt implementation, add an unit
6623 test that checks for interoperability between libscrypt_scrypt()
6624 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
6625 and rely on EVP_PBE_scrypt() whenever possible. Resolves
6627 - The link authentication protocol code now has extensive tests.
6628 - The relay descriptor signature testing code now has
6630 - The test_workqueue program now runs faster, and is enabled by
6631 default as a part of "make check".
6632 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
6633 functions in dns.c. Implements a portion of ticket 16831.
6634 - Use environment variables rather than autoconf substitutions to
6635 send variables from the build system to the test scripts. This
6636 change should be easier to maintain, and cause 'make distcheck' to
6637 work better than before. Fixes bug 17148.
6638 - When building Tor with testing coverage enabled, run Chutney tests
6639 (if any) using the 'tor-cov' coverage binary.
6640 - When running test-network or test-stem, check for the absence of
6641 stem/chutney before doing any build operations.
6642 - Add a test to verify that the compiler does not eliminate our
6643 memwipe() implementation. Closes ticket 15377.
6644 - Add make rule `check-changes` to verify the format of changes
6645 files. Closes ticket 15180.
6646 - Add unit tests for control_event_is_interesting(). Add a compile-
6647 time check that the number of events doesn't exceed the capacity
6648 of control_event_t.event_mask. Closes ticket 15431, checks for
6649 bugs similar to 13085. Patch by "teor".
6650 - Command-line argument tests moved to Stem. Resolves ticket 14806.
6651 - Integrate the ntor, backtrace, and zero-length keys tests into the
6652 automake test suite. Closes ticket 15344.
6653 - Remove assertions during builds to determine Tor's test coverage.
6654 We don't want to trigger these even in assertions, so including
6655 them artificially makes our branch coverage look worse than it is.
6656 This patch provides the new test-stem-full and coverage-html-full
6657 configure options. Implements ticket 15400.
6658 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6659 explicitly manage consensus flags in testing networks. Patch by
6660 "robgjansen", modified by "teor". Implements part of ticket 14882.
6661 - Check for matching value in server response in ntor_ref.py. Fixes
6662 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
6664 - Set the severity correctly when testing
6665 get_interface_addresses_ifaddrs() and
6666 get_interface_addresses_win32(), so that the tests fail gracefully
6667 instead of triggering an assertion. Fixes bug 15759; bugfix on
6668 0.2.6.3-alpha. Reported by Nicolas Derive.
6670 Changes in version 0.2.6.10 - 2015-07-12
6671 Tor version 0.2.6.10 fixes some significant stability and hidden
6672 service client bugs, bulletproofs the cryptography init process, and
6673 fixes a bug when using the sandbox code with some older versions of
6674 Linux. Everyone running an older version, especially an older version
6675 of 0.2.6, should upgrade.
6677 o Major bugfixes (hidden service clients, stability):
6678 - Stop refusing to store updated hidden service descriptors on a
6679 client. This reverts commit 9407040c59218 (which indeed fixed bug
6680 14219, but introduced a major hidden service reachability
6681 regression detailed in bug 16381). This is a temporary fix since
6682 we can live with the minor issue in bug 14219 (it just results in
6683 some load on the network) but the regression of 16381 is too much
6684 of a setback. First-round fix for bug 16381; bugfix
6687 o Major bugfixes (stability):
6688 - Stop crashing with an assertion failure when parsing certain kinds
6689 of malformed or truncated microdescriptors. Fixes bug 16400;
6690 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6691 by "cypherpunks_backup".
6692 - Stop random client-side assertion failures that could occur when
6693 connecting to a busy hidden service, or connecting to a hidden
6694 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6697 o Minor features (geoip):
6698 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
6699 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
6701 o Minor bugfixes (crypto error-handling):
6702 - Check for failures from crypto_early_init, and refuse to continue.
6703 A previous typo meant that we could keep going with an
6704 uninitialized crypto library, and would have OpenSSL initialize
6705 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6706 when implementing ticket 4900. Patch by "teor".
6708 o Minor bugfixes (Linux seccomp2 sandbox):
6709 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6710 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6711 on 0.2.6.3-alpha. Patch from "teor".
6714 Changes in version 0.2.6.9 - 2015-06-11
6715 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
6716 requirements for receiving an HSDir flag, and addresses some other small
6717 bugs in the systemd and sandbox code. Clients using circuit isolation
6718 should upgrade; all directory authorities should upgrade.
6720 o Major bugfixes (client-side privacy):
6721 - Properly separate out each SOCKSPort when applying stream
6722 isolation. The error occurred because each port's session group was
6723 being overwritten by a default value when the listener connection
6724 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
6727 o Minor feature (directory authorities, security):
6728 - The HSDir flag given by authorities now requires the Stable flag.
6729 For the current network, this results in going from 2887 to 2806
6730 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6731 attack by raising the effort for a relay to become Stable which
6732 takes at the very least 7 days to do so and by keeping the 96
6733 hours uptime requirement for HSDir. Implements ticket 8243.
6735 o Minor bugfixes (compilation):
6736 - Build with --enable-systemd correctly when libsystemd is
6737 installed, but systemd is not. Fixes bug 16164; bugfix on
6738 0.2.6.3-alpha. Patch from Peter Palfrader.
6740 o Minor bugfixes (Linux seccomp2 sandbox):
6741 - Fix sandboxing to work when running as a relaymby renaming of
6742 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
6743 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
6744 - Allow systemd connections to work with the Linux seccomp2 sandbox
6745 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6748 o Minor bugfixes (tests):
6749 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6750 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6753 Changes in version 0.2.6.8 - 2015-05-21
6754 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
6755 fixes an authority-side bug in assigning the HSDir flag. All directory
6756 authorities should upgrade.
6758 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
6759 - Revert commit that made directory authorities assign the HSDir
6760 flag to relays without a DirPort; this was bad because such relays
6761 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6764 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
6765 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6766 a client authorized hidden service. Fixes bug 15823; bugfix
6769 o Minor features (geoip):
6770 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6771 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
6775 Changes in version 0.2.6.7 - 2015-04-06
6776 Tor 0.2.6.7 fixes two security issues that could be used by an
6777 attacker to crash hidden services, or crash clients visiting hidden
6778 services. Hidden services should upgrade as soon as possible; clients
6779 should upgrade whenever packages become available.
6781 This release also contains two simple improvements to make hidden
6782 services a bit less vulnerable to denial-of-service attacks.
6784 o Major bugfixes (security, hidden service):
6785 - Fix an issue that would allow a malicious client to trigger an
6786 assertion failure and halt a hidden service. Fixes bug 15600;
6787 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6788 - Fix a bug that could cause a client to crash with an assertion
6789 failure when parsing a malformed hidden service descriptor. Fixes
6790 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6792 o Minor features (DoS-resistance, hidden service):
6793 - Introduction points no longer allow multiple INTRODUCE1 cells to
6794 arrive on the same circuit. This should make it more expensive for
6795 attackers to overwhelm hidden services with introductions.
6796 Resolves ticket 15515.
6797 - Decrease the amount of reattempts that a hidden service performs
6798 when its rendezvous circuits fail. This reduces the computational
6799 cost for running a hidden service under heavy load. Resolves
6803 Changes in version 0.2.5.12 - 2015-04-06
6804 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
6805 could be used by an attacker to crash hidden services, or crash clients
6806 visiting hidden services. Hidden services should upgrade as soon as
6807 possible; clients should upgrade whenever packages become available.
6809 This release also backports a simple improvement to make hidden
6810 services a bit less vulnerable to denial-of-service attacks.
6812 o Major bugfixes (security, hidden service):
6813 - Fix an issue that would allow a malicious client to trigger an
6814 assertion failure and halt a hidden service. Fixes bug 15600;
6815 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6816 - Fix a bug that could cause a client to crash with an assertion
6817 failure when parsing a malformed hidden service descriptor. Fixes
6818 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6820 o Minor features (DoS-resistance, hidden service):
6821 - Introduction points no longer allow multiple INTRODUCE1 cells to
6822 arrive on the same circuit. This should make it more expensive for
6823 attackers to overwhelm hidden services with introductions.
6824 Resolves ticket 15515.
6827 Changes in version 0.2.4.27 - 2015-04-06
6828 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
6829 could be used by an attacker to crash hidden services, or crash clients
6830 visiting hidden services. Hidden services should upgrade as soon as
6831 possible; clients should upgrade whenever packages become available.
6833 This release also backports a simple improvement to make hidden
6834 services a bit less vulnerable to denial-of-service attacks.
6836 o Major bugfixes (security, hidden service):
6837 - Fix an issue that would allow a malicious client to trigger an
6838 assertion failure and halt a hidden service. Fixes bug 15600;
6839 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6840 - Fix a bug that could cause a client to crash with an assertion
6841 failure when parsing a malformed hidden service descriptor. Fixes
6842 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6844 o Minor features (DoS-resistance, hidden service):
6845 - Introduction points no longer allow multiple INTRODUCE1 cells to
6846 arrive on the same circuit. This should make it more expensive for
6847 attackers to overwhelm hidden services with introductions.
6848 Resolves ticket 15515.
6851 Changes in version 0.2.6.6 - 2015-03-24
6852 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
6854 It adds numerous safety, security, correctness, and performance
6855 improvements. Client programs can be configured to use more kinds of
6856 sockets, AutomapHosts works better, the multithreading backend is
6857 improved, cell transmission is refactored, test coverage is much
6858 higher, more denial-of-service attacks are handled, guard selection is
6859 improved to handle long-term guards better, pluggable transports
6860 should work a bit better, and some annoying hidden service performance
6861 bugs should be addressed.
6863 o New compiler and system requirements:
6864 - Tor 0.2.6.x requires that your compiler support more of the C99
6865 language standard than before. The 'configure' script now detects
6866 whether your compiler supports C99 mid-block declarations and
6867 designated initializers. If it does not, Tor will not compile.
6869 We may revisit this requirement if it turns out that a significant
6870 number of people need to build Tor with compilers that don't
6871 bother implementing a 15-year-old standard. Closes ticket 13233.
6872 - Tor no longer supports systems without threading support. When we
6873 began working on Tor, there were several systems that didn't have
6874 threads, or where the thread support wasn't able to run the
6875 threads of a single process on multiple CPUs. That no longer
6876 holds: every system where Tor needs to run well now has threading
6877 support. Resolves ticket 12439.
6879 o Deprecated versions and removed support:
6880 - Tor relays older than 0.2.4.18-rc are no longer allowed to
6881 advertise themselves on the network. Closes ticket 13555.
6882 - Tor clients no longer support connecting to hidden services
6883 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
6884 option has been removed. (There shouldn't be any hidden services
6885 running these versions on the network.) Closes ticket 7803.
6887 o Directory authority changes:
6888 - The directory authority Faravahar has a new IP address. This
6889 closes ticket 14487.
6890 - Remove turtles as a directory authority.
6891 - Add longclaw as a new (v3) directory authority. This implements
6892 ticket 13296. This keeps the directory authority count at 9.
6894 o Major features (bridges):
6895 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
6896 transports if they are configured via the "TOR_PT_PROXY"
6897 environment variable. Implements proposal 232. Resolves
6900 o Major features (changed defaults):
6901 - Prevent relay operators from unintentionally running exits: When a
6902 relay is configured as an exit node, we now warn the user unless
6903 the "ExitRelay" option is set to 1. We warn even more loudly if
6904 the relay is configured with the default exit policy, since this
6905 can indicate accidental misconfiguration. Setting "ExitRelay 0"
6906 stops Tor from running as an exit relay. Closes ticket 10067.
6908 o Major features (client performance, hidden services):
6909 - Allow clients to use optimistic data when connecting to a hidden
6910 service, which should remove a round-trip from hidden service
6911 initialization. See proposal 181 for details. Implements
6914 o Major features (directory system):
6915 - Upon receiving an unparseable directory object, if its digest
6916 matches what we expected, then don't try to download it again.
6917 Previously, when we got a descriptor we didn't like, we would keep
6918 trying to download it over and over. Closes ticket 11243.
6919 - When downloading server- or microdescriptors from a directory
6920 server, we no longer launch multiple simultaneous requests to the
6921 same server. This reduces load on the directory servers,
6922 especially when directory guards are in use. Closes ticket 9969.
6923 - When downloading server- or microdescriptors over a tunneled
6924 connection, do not limit the length of our requests to what the
6925 Squid proxy is willing to handle. Part of ticket 9969.
6926 - Authorities can now vote on the correct digests and latest
6927 versions for different software packages. This allows packages
6928 that include Tor to use the Tor authority system as a way to get
6929 notified of updates and their correct digests. Implements proposal
6930 227. Closes ticket 10395.
6932 o Major features (guards):
6933 - Introduce the Guardfraction feature to improves load balancing on
6934 guard nodes. Specifically, it aims to reduce the traffic gap that
6935 guard nodes experience when they first get the Guard flag. This is
6936 a required step if we want to increase the guard lifetime to 9
6937 months or greater. Closes ticket 9321.
6939 o Major features (hidden services):
6940 - Make HS port scanning more difficult by immediately closing the
6941 circuit when a user attempts to connect to a nonexistent port.
6942 Closes ticket 13667.
6943 - Add a HiddenServiceStatistics option that allows Tor relays to
6944 gather and publish statistics about the overall size and volume of
6945 hidden service usage. Specifically, when this option is turned on,
6946 an HSDir will publish an approximate number of hidden services
6947 that have published descriptors to it the past 24 hours. Also, if
6948 a relay has acted as a hidden service rendezvous point, it will
6949 publish the approximate amount of rendezvous cells it has relayed
6950 the past 24 hours. The statistics themselves are obfuscated so
6951 that the exact values cannot be derived. For more details see
6952 proposal 238, "Better hidden service stats from Tor relays". This
6953 feature is currently disabled by default. Implements feature 13192.
6955 o Major features (performance):
6956 - Make the CPU worker implementation more efficient by avoiding the
6957 kernel and lengthening pipelines. The original implementation used
6958 sockets to transfer data from the main thread to the workers, and
6959 didn't allow any thread to be assigned more than a single piece of
6960 work at once. The new implementation avoids communications
6961 overhead by making requests in shared memory, avoiding kernel IO
6962 where possible, and keeping more requests in flight at once.
6963 Implements ticket 9682.
6965 o Major features (relay):
6966 - Raise the minimum acceptable configured bandwidth rate for bridges
6967 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
6968 20 KiB/sec.) Closes ticket 13822.
6969 - Complete revision of the code that relays use to decide which cell
6970 to send next. Formerly, we selected the best circuit to write on
6971 each channel, but we didn't select among channels in any
6972 sophisticated way. Now, we choose the best circuits globally from
6973 among those whose channels are ready to deliver traffic.
6975 This patch implements a new inter-cmux comparison API, a global
6976 high/low watermark mechanism and a global scheduler loop for
6977 transmission prioritization across all channels as well as among
6978 circuits on one channel. This schedule is currently tuned to
6979 (tolerantly) avoid making changes in network performance, but it
6980 should form the basis for major circuit performance increases in
6981 the future. Code by Andrea; tuning by Rob Jansen; implements
6984 o Major features (sample torrc):
6985 - Add a new, infrequently-changed "torrc.minimal". This file is
6986 similar to torrc.sample, but it will change as infrequently as
6987 possible, for the benefit of users whose systems prompt them for
6988 intervention whenever a default configuration file is changed.
6989 Making this change allows us to update torrc.sample to be a more
6990 generally useful "sample torrc".
6992 o Major features (security, unix domain sockets):
6993 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
6994 applications can reach Tor without having to create AF_INET or
6995 AF_INET6 sockets, meaning they can completely disable their
6996 ability to make non-Tor network connections. To create a socket of
6997 this type, use "SocksPort unix:/path/to/socket". Implements
6999 - Support mapping hidden service virtual ports to AF_UNIX sockets.
7000 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
7001 Implements ticket 11485.
7003 o Major bugfixes (client, automap):
7004 - Repair automapping with IPv6 addresses. This automapping should
7005 have worked previously, but one piece of debugging code that we
7006 inserted to detect a regression actually caused the regression to
7007 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
7008 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
7011 o Major bugfixes (crash, OSX, security):
7012 - Fix a remote denial-of-service opportunity caused by a bug in
7013 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7016 o Major bugfixes (directory authorities):
7017 - Do not assign the HSDir flag to relays if they are not Valid, or
7018 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
7020 o Major bugfixes (directory bandwidth performance):
7021 - Don't flush the zlib buffer aggressively when compressing
7022 directory information for clients. This should save about 7% of
7023 the bandwidth currently used for compressed descriptors and
7024 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
7026 o Major bugfixes (exit node stability):
7027 - Fix an assertion failure that could occur under high DNS load.
7028 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7029 diagnosed and fixed by "cypherpunks".
7031 o Major bugfixes (FreeBSD IPFW transparent proxy):
7032 - Fix address detection with FreeBSD transparent proxies, when
7033 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
7036 o Major bugfixes (hidden services):
7037 - When closing an introduction circuit that was opened in parallel
7038 with others, don't mark the introduction point as unreachable.
7039 Previously, the first successful connection to an introduction
7040 point would make the other introduction points get marked as
7041 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
7043 o Major bugfixes (Linux seccomp2 sandbox):
7044 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7045 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7046 0.2.5.1-alpha. Patch from "sanic".
7048 o Major bugfixes (mixed relay-client operation):
7049 - When running as a relay and client at the same time (not
7050 recommended), if we decide not to use a new guard because we want
7051 to retry older guards, only close the locally-originating circuits
7052 passing through that guard. Previously we would close all the
7053 circuits through that guard. Fixes bug 9819; bugfix on
7054 0.2.1.1-alpha. Reported by "skruffy".
7056 o Major bugfixes (pluggable transports):
7057 - Initialize the extended OR Port authentication cookie before
7058 launching pluggable transports. This prevents a race condition
7059 that occurred when server-side pluggable transports would cache the
7060 authentication cookie before it has been (re)generated. Fixes bug
7061 15240; bugfix on 0.2.5.1-alpha.
7063 o Major bugfixes (relay, stability, possible security):
7064 - Fix a bug that could lead to a relay crashing with an assertion
7065 failure if a buffer of exactly the wrong layout is passed to
7066 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7067 0.2.0.10-alpha. Patch from "cypherpunks".
7068 - Do not assert if the 'data' pointer on a buffer is advanced to the
7069 very end of the buffer; log a BUG message instead. Only assert if
7070 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7072 o Minor features (build):
7073 - New --disable-system-torrc compile-time option to prevent Tor from
7074 looking for the system-wide torrc or torrc-defaults files.
7075 Resolves ticket 13037.
7077 o Minor features (client):
7078 - Clients are now willing to send optimistic data (before they
7079 receive a 'connected' cell) to relays of any version. (Relays
7080 without support for optimistic data are no longer supported on the
7081 Tor network.) Resolves ticket 13153.
7083 o Minor features (client):
7084 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
7085 is enabled, reject requests with IP addresses as hostnames.
7086 Resolves ticket 13315.
7088 o Minor features (controller):
7089 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
7090 write an unscheduled heartbeat message to the log. Implements
7092 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
7093 events so controllers can observe circuit isolation inputs. Closes
7095 - ControlPort now supports the unix:/path/to/socket syntax as an
7096 alternative to the ControlSocket option, for consistency with
7097 SocksPort and HiddenServicePort. Closes ticket 14451.
7098 - New "GETINFO bw-event-cache" to get information about recent
7099 bandwidth events. Closes ticket 14128. Useful for controllers to
7100 get recent bandwidth history after the fix for ticket 13988.
7101 - Messages about problems in the bootstrap process now include
7102 information about the server we were trying to connect to when we
7103 noticed the problem. Closes ticket 15006.
7105 o Minor features (Denial of service resistance):
7106 - Count the total number of bytes used storing hidden service
7107 descriptors against the value of MaxMemInQueues. If we're low on
7108 memory, and more than 20% of our memory is used holding hidden
7109 service descriptors, free them until no more than 10% of our
7110 memory holds hidden service descriptors. Free the least recently
7111 fetched descriptors first. Resolves ticket 13806.
7112 - When we have recently been under memory pressure (over 3/4 of
7113 MaxMemInQueues is allocated), then allocate smaller zlib objects
7114 for small requests. Closes ticket 11791.
7116 o Minor features (directory authorities):
7117 - Don't list relays with a bandwidth estimate of 0 in the consensus.
7118 Implements a feature proposed during discussion of bug 13000.
7119 - In tor-gencert, report an error if the user provides the same
7120 argument more than once.
7121 - If a directory authority can't find a best consensus method in the
7122 votes that it holds, it now falls back to its favorite consensus
7123 method. Previously, it fell back to method 1. Neither of these is
7124 likely to get enough signatures, but "fall back to favorite"
7125 doesn't require us to maintain support an obsolete consensus
7126 method. Implements part of proposal 215.
7128 o Minor features (geoip):
7129 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7130 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7133 o Minor features (guard nodes):
7134 - Reduce the time delay before saving guard status to disk from 10
7135 minutes to 30 seconds (or from one hour to 10 minutes if
7136 AvoidDiskWrites is set). Closes ticket 12485.
7138 o Minor features (heartbeat):
7139 - On relays, report how many connections we negotiated using each
7140 version of the Tor link protocols. This information will let us
7141 know if removing support for very old versions of the Tor
7142 protocols is harming the network. Closes ticket 15212.
7144 o Minor features (hidden service):
7145 - Make Sybil attacks against hidden services harder by changing the
7146 minimum time required to get the HSDir flag from 25 hours up to 96
7147 hours. Addresses ticket 14149.
7148 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
7149 services to disable the anti-scanning feature introduced in
7150 0.2.6.2-alpha. With this option not set, a connection to an
7151 unlisted port closes the circuit. With this option set, only a
7152 RELAY_DONE cell is sent. Closes ticket 14084.
7153 - When re-enabling the network, don't try to build introduction
7154 circuits until we have successfully built a circuit. This makes
7155 hidden services come up faster when the network is re-enabled.
7156 Patch from "akwizgran". Closes ticket 13447.
7157 - When we fail to retrieve a hidden service descriptor, send the
7158 controller an "HS_DESC FAILED" controller event. Implements
7160 - New HiddenServiceDirGroupReadable option to cause hidden service
7161 directories and hostname files to be created group-readable. Patch
7162 from "anon", David Stainton, and "meejah". Closes ticket 11291.
7164 o Minor features (interface):
7165 - Implement "-f -" command-line option to read torrc configuration
7166 from standard input, if you don't want to store the torrc file in
7167 the file system. Implements feature 13865.
7169 o Minor features (logging):
7170 - Add a count of unique clients to the bridge heartbeat message.
7171 Resolves ticket 6852.
7172 - Suppress "router info incompatible with extra info" message when
7173 reading extrainfo documents from cache. (This message got loud
7174 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
7176 - Elevate hidden service authorized-client message from DEBUG to
7177 INFO. Closes ticket 14015.
7178 - On Unix-like systems, you can now use named pipes as the target of
7179 the Log option, and other options that try to append to files.
7180 Closes ticket 12061. Patch from "carlo von lynX".
7181 - When opening a log file at startup, send it every log message that
7182 we generated between startup and opening it. Previously, log
7183 messages that were generated before opening the log file were only
7184 logged to stdout. Closes ticket 6938.
7185 - Add a TruncateLogFile option to overwrite logs instead of
7186 appending to them. Closes ticket 5583.
7187 - Quiet some log messages in the heartbeat and at startup. Closes
7190 o Minor features (portability, Solaris):
7191 - Threads are no longer disabled by default on Solaris; we believe
7192 that the versions of Solaris with broken threading support are all
7193 obsolete by now. Resolves ticket 9495.
7195 o Minor features (relay):
7196 - Re-check our address after we detect a changed IP address from
7197 getsockname(). This ensures that the controller command "GETINFO
7198 address" will report the correct value. Resolves ticket 11582.
7200 - A new AccountingRule option lets Relays set whether they'd like
7201 AccountingMax to be applied separately to inbound and outbound
7202 traffic, or applied to the sum of inbound and outbound traffic.
7203 Resolves ticket 961. Patch by "chobe".
7204 - When identity keypair is generated for first time, log a
7205 congratulatory message that links to the new relay lifecycle
7206 document. Implements feature 10427.
7208 o Minor features (security, memory wiping):
7209 - Ensure we securely wipe keys from memory after
7210 crypto_digest_get_digest and init_curve25519_keypair_from_file
7211 have finished using them. Resolves ticket 13477.
7213 o Minor features (security, out-of-memory handling):
7214 - When handling an out-of-memory condition, allocate less memory for
7215 temporary data structures. Fixes issue 10115.
7216 - When handling an out-of-memory condition, consider more types of
7217 buffers, including those on directory connections, and zlib
7218 buffers. Resolves ticket 11792.
7220 o Minor features (stability):
7221 - Add assertions in our hash-table iteration code to check for
7222 corrupted values that could cause infinite loops. Closes
7225 o Minor features (systemd):
7226 - Various improvements and modernizations in systemd hardening
7227 support. Closes ticket 13805. Patch from Craig Andrews.
7228 - Where supported, when running with systemd, report successful
7229 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
7230 - When running with systemd, support systemd watchdog messages. Part
7231 of ticket 11016. Patch by Michael Scherer.
7233 o Minor features (testing networks):
7234 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
7235 the "Exit" flag regardless of their uptime, bandwidth, or exit
7236 policy. TestingTorNetwork must be set for this option to have any
7237 effect. Previously, authorities would take up to 35 minutes to
7238 give nodes the Exit flag in a test network. Partially implements
7240 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
7241 and the default on a testing network to 2 minutes. Drop the
7242 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
7243 keep the default on a testing network at 30 seconds. This reduces
7244 HS bootstrap time to around 25 seconds. Also, change the default
7245 time in test-network.sh to match. Closes ticket 13401. Patch
7247 - Create TestingDirAuthVoteHSDir to correspond to
7248 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
7249 HSDir flag for the listed relays regardless of uptime or ORPort
7250 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
7251 Partial implementation for ticket 14067. Patch by "teor".
7253 o Minor features (tor2web mode):
7254 - Introduce the config option Tor2webRendezvousPoints, which allows
7255 clients in Tor2webMode to select a specific Rendezvous Point to be
7256 used in HS circuits. This might allow better performance for
7257 Tor2Web nodes. Implements ticket 12844.
7259 o Minor features (transparent proxy):
7260 - Update the transparent proxy option checks to allow for both ipfw
7261 and pf on OS X. Closes ticket 14002.
7262 - Use the correct option when using IPv6 with transparent proxy
7263 support on Linux. Resolves 13808. Patch by Francisco Blas
7266 o Minor features (validation):
7267 - Check all date/time values passed to tor_timegm and
7268 parse_rfc1123_time for validity, taking leap years into account.
7269 Improves HTTP header validation. Implemented with bug 13476.
7270 - In correct_tm(), limit the range of values returned by system
7271 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
7272 This means we don't have to deal with negative or too large dates,
7273 even if a clock is wrong. Otherwise we might fail to read a file
7274 written by us which includes such a date. Fixes bug 13476.
7275 - Stop allowing invalid address patterns like "*/24" that contain
7276 both a wildcard address and a bit prefix length. This affects all
7277 our address-range parsing code. Fixes bug 7484; bugfix
7280 o Minor bugfixes (bridge clients):
7281 - When configured to use a bridge without an identity digest (not
7282 recommended), avoid launching an extra channel to it when
7283 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
7285 o Minor bugfixes (bridges):
7286 - When DisableNetwork is set, do not launch pluggable transport
7287 plugins, and if any are running, terminate them. Fixes bug 13213;
7288 bugfix on 0.2.3.6-alpha.
7290 o Minor bugfixes (C correctness):
7291 - Fix several instances of possible integer overflow/underflow/NaN.
7292 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
7294 - In circuit_build_times_calculate_timeout() in circuitstats.c,
7295 avoid dividing by zero in the pareto calculations. This traps
7296 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
7298 - Fix an integer overflow in format_time_interval(). Fixes bug
7299 13393; bugfix on 0.2.0.10-alpha.
7300 - Set the correct day of year value when the system's localtime(_r)
7301 or gmtime(_r) functions fail to set struct tm. Not externally
7302 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
7303 - Avoid unlikely signed integer overflow in tor_timegm on systems
7304 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
7306 o Minor bugfixes (certificate handling):
7307 - If an authority operator accidentally makes a signing certificate
7308 with a future publication time, do not discard its real signing
7309 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
7310 - Remove any old authority certificates that have been superseded
7311 for at least two days. Previously, we would keep superseded
7312 certificates until they expired, if they were published close in
7313 time to the certificate that superseded them. Fixes bug 11454;
7314 bugfix on 0.2.1.8-alpha.
7316 o Minor bugfixes (client):
7317 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
7318 BadExit flag are not considered worthy candidates. Fixes bug
7319 13066; bugfix on 0.1.2.3-alpha.
7320 - Use the consensus schedule for downloading consensuses, and not
7321 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
7322 - Handle unsupported or malformed SOCKS5 requests properly by
7323 responding with the appropriate error message before closing the
7324 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
7326 o Minor bugfixes (client, automapping):
7327 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7328 no value follows the option. Fixes bug 14142; bugfix on
7329 0.2.4.7-alpha. Patch by "teor".
7330 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7331 14195; bugfix on 0.1.0.1-rc.
7332 - Prevent changes to other options from removing the wildcard value
7333 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
7335 - Allow MapAddress and AutomapHostsOnResolve to work together when
7336 an address is mapped into another address type (like .onion) that
7337 must be automapped at resolve time. Fixes bug 7555; bugfix
7340 o Minor bugfixes (client, bridges):
7341 - When we are using bridges and we had a network connectivity
7342 problem, only retry connecting to our currently configured
7343 bridges, not all bridges we know about and remember using. Fixes
7344 bug 14216; bugfix on 0.2.2.17-alpha.
7346 o Minor bugfixes (client, DNS):
7347 - Report the correct cached DNS expiration times on SOCKS port or in
7348 DNS replies. Previously, we would report everything as "never
7349 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
7350 - Avoid a small memory leak when we find a cached answer for a
7351 reverse DNS lookup in a client-side DNS cache. (Remember, client-
7352 side DNS caching is off by default, and is not recommended.) Fixes
7353 bug 14259; bugfix on 0.2.0.1-alpha.
7355 o Minor bugfixes (client, IPv6):
7356 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
7357 flag is not set; and not because the NoIPv4Traffic flag was set.
7358 Previously we'd looked at the NoIPv4Traffic flag for both types of
7359 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
7361 o Minor bugfixes (client, microdescriptors):
7362 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
7363 computing which microdescriptors to download. This keeps us from
7364 erroneous download behavior if two microdescriptor digests ever
7365 have the same first 160 bits. Fixes part of bug 13399; bugfix
7367 - Reset a router's status if its microdescriptor digest changes,
7368 even if the first 160 bits remain the same. Fixes part of bug
7369 13399; bugfix on 0.2.3.1-alpha.
7371 o Minor bugfixes (client, torrc):
7372 - Stop modifying the value of our DirReqStatistics torrc option just
7373 because we're not a bridge or relay. This bug was causing Tor
7374 Browser users to write "DirReqStatistics 0" in their torrc files
7375 as if they had chosen to change the config. Fixes bug 4244; bugfix
7377 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
7378 that our options have changed every time we SIGHUP. Fixes bug
7379 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
7381 o Minor bugfixes (compilation):
7382 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
7384 - Silence clang warnings under --enable-expensive-hardening,
7385 including implicit truncation of 64 bit values to 32 bit, const
7386 char assignment to self, tautological compare, and additional
7387 parentheses around equality tests. Fixes bug 13577; bugfix
7389 - Fix a clang warning about checking whether an address in the
7390 middle of a structure is NULL. Fixes bug 14001; bugfix
7392 - The address of an array in the middle of a structure will always
7393 be non-NULL. clang recognises this and complains. Disable the
7394 tautologous and redundant check to silence this warning. Fixes bug
7395 14001; bugfix on 0.2.1.2-alpha.
7396 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
7397 Addresses ticket 14188.
7398 - Build without warnings with the stock OpenSSL srtp.h header, which
7399 has a duplicate declaration of SSL_get_selected_srtp_profile().
7400 Fixes bug 14220; this is OpenSSL's bug, not ours.
7401 - Do not compile any code related to Tor2Web mode when Tor2Web mode
7402 is not enabled at compile time. Previously, this code was included
7403 in a disabled state. See discussion on ticket 12844.
7404 - Allow our configure script to build correctly with autoconf 2.62
7405 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
7406 - Improve the error message from ./configure to make it clear that
7407 when asciidoc has not been found, the user will have to either add
7408 --disable-asciidoc argument or install asciidoc. Resolves
7411 o Minor bugfixes (controller):
7412 - Report "down" in response to the "GETINFO entry-guards" command
7413 when relays are down with an unreachable_since value. Previously,
7414 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
7415 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
7416 14116; bugfix on 0.2.2.9-alpha.
7418 o Minor bugfixes (controller):
7419 - Return an error when the second or later arguments of the
7420 "setevents" controller command are invalid events. Previously we
7421 would return success while silently skipping invalid events. Fixes
7422 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
7424 o Minor bugfixes (directory authority):
7425 - Allow directory authorities to fetch more data from one another if
7426 they find themselves missing lots of votes. Previously, they had
7427 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7428 bugfix on 0.1.2.5-alpha.
7429 - Do not attempt to download extrainfo documents which we will be
7430 unable to validate with a matching server descriptor. Fixes bug
7431 13762; bugfix on 0.2.0.1-alpha.
7432 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
7433 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
7434 - Enlarge the buffer to read bwauth generated files to avoid an
7435 issue when parsing the file in dirserv_read_measured_bandwidths().
7436 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7437 - When running as a v3 directory authority, advertise that you serve
7438 extra-info documents so that clients who want them can find them
7439 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
7441 o Minor bugfixes (directory system):
7442 - Always believe that v3 directory authorities serve extra-info
7443 documents, whether they advertise "caches-extra-info" or not.
7444 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
7445 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
7446 Previously, directories offering BRIDGE_DIRINFO and some other
7447 flag (i.e. microdescriptors or extrainfo) would be ignored when
7448 looking for bridges. Partially fixes bug 13163; bugfix
7451 o Minor bugfixes (file handling):
7452 - Stop failing when key files are zero-length. Instead, generate new
7453 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
7454 on all versions of Tor. Patch by "teor".
7455 - Stop generating a fresh .old RSA onion key file when the .old file
7456 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
7457 - Avoid overwriting .old key files with empty key files.
7458 - Skip loading zero-length extrainfo store, router store, stats,
7459 state, and key files.
7460 - Avoid crashing when trying to reload a torrc specified as a
7461 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
7464 o Minor bugfixes (hidden services):
7465 - Close the introduction circuit when we have no more usable intro
7466 points, instead of waiting for it to time out. This also ensures
7467 that no follow-up HS descriptor fetch is triggered when the
7468 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
7469 - When fetching a hidden service descriptor for a down service that
7470 was recently up, do not keep refetching until we try the same
7471 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
7472 - Correctly send a controller event when we find that a rendezvous
7473 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
7474 - Pre-check directory permissions for new hidden-services to avoid
7475 at least one case of "Bug: Acting on config options left us in a
7476 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
7477 - When fetching hidden service descriptors, we now check not only
7478 for whether we got the hidden service we had in mind, but also
7479 whether we got the particular descriptors we wanted. This prevents
7480 a class of inefficient but annoying DoS attacks by hidden service
7481 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
7484 o Minor bugfixes (Linux seccomp2 sandbox):
7485 - Make transparent proxy support work along with the seccomp2
7486 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
7487 by Francisco Blas Izquierdo Riera.
7488 - Fix a memory leak in tor-resolve when running with the sandbox
7489 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
7490 - Allow glibc fatal errors to be sent to stderr before Tor exits.
7491 Previously, glibc would try to write them to /dev/tty, and the
7492 sandbox would trap the call and make Tor exit prematurely. Fixes
7493 bug 14759; bugfix on 0.2.5.1-alpha.
7495 o Minor bugfixes (logging):
7496 - Avoid crashing when there are more log domains than entries in
7497 domain_list. Bugfix on 0.2.3.1-alpha.
7498 - Downgrade warnings about RSA signature failures to info log level.
7499 Emit a warning when an extra info document is found incompatible
7500 with a corresponding router descriptor. Fixes bug 9812; bugfix
7502 - Make connection_ap_handshake_attach_circuit() log the circuit ID
7503 correctly. Fixes bug 13701; bugfix on 0.0.6.
7505 o Minor bugfixes (networking):
7506 - Check for orconns and use connection_or_close_for_error() rather
7507 than connection_mark_for_close() directly in the getsockopt()
7508 failure case of connection_handle_write_impl(). Fixes bug 11302;
7509 bugfix on 0.2.4.4-alpha.
7511 o Minor bugfixes (parsing):
7512 - Stop accepting milliseconds (or other junk) at the end of
7513 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
7514 - Support two-number and three-number version numbers correctly, in
7515 case we change the Tor versioning system in the future. Fixes bug
7516 13661; bugfix on 0.0.8pre1.
7518 o Minor bugfixes (portability):
7519 - Fix the ioctl()-based network interface lookup code so that it
7520 will work on systems that have variable-length struct ifreq, for
7522 - Use the correct datatype in the SipHash-2-4 function to prevent
7523 compilers from assuming any sort of alignment. Fixes bug 15436;
7524 bugfix on 0.2.5.3-alpha.
7526 o Minor bugfixes (preventative security, C safety):
7527 - When reading a hexadecimal, base-32, or base-64 encoded value from
7528 a string, always overwrite the whole output buffer. This prevents
7529 some bugs where we would look at (but fortunately, not reveal)
7530 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7532 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
7533 just the part that's used. This makes it harder for data leak bugs
7534 to occur in the event of other programming failures. Resolves
7537 o Minor bugfixes (relay):
7538 - When generating our family list, remove spaces from around the
7539 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
7540 - If our previous bandwidth estimate was 0 bytes, allow publishing a
7541 new relay descriptor immediately. Fixes bug 13000; bugfix
7544 o Minor bugfixes (shutdown):
7545 - When shutting down, always call event_del() on lingering read or
7546 write events before freeing them. Otherwise, we risk double-frees
7547 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
7550 o Minor bugfixes (small memory leaks):
7551 - Avoid leaking memory when using IPv6 virtual address mappings.
7552 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
7555 o Minor bugfixes (statistics):
7556 - Increase period over which bandwidth observations are aggregated
7557 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7559 o Minor bugfixes (systemd support):
7560 - Run correctly under systemd with the RunAsDaemon option set. Fixes
7561 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
7562 - Inform the systemd supervisor about more changes in the Tor
7563 process status. Implements part of ticket 14141. Patch from
7566 o Minor bugfixes (testing networks):
7567 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
7568 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
7569 - Stop using the default authorities in networks which provide both
7570 AlternateDirAuthority and AlternateBridgeAuthority. Partially
7571 fixes bug 13163; bugfix on 0.2.0.13-alpha.
7573 o Minor bugfixes (testing networks, fast startup):
7574 - Allow Tor to build circuits using a consensus with no exits. If
7575 the consensus has no exits (typical of a bootstrapping test
7576 network), allow Tor to build circuits once enough descriptors have
7577 been downloaded. This assists in bootstrapping a testing Tor
7578 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
7580 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
7581 header to directory servers. This allows us to obtain consensuses
7582 promptly when the consensus interval is very short. This assists
7583 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
7584 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
7585 - Stop assuming that private addresses are local when checking
7586 reachability in a TestingTorNetwork. Instead, when testing, assume
7587 all OR connections are remote. (This is necessary due to many test
7588 scenarios running all relays on localhost.) This assists in
7589 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
7590 0.1.0.1-rc. Patch by "teor".
7591 - Avoid building exit circuits from a consensus with no exits. Now
7592 thanks to our fix for 13718, we accept a no-exit network as not
7593 wholly lost, but we need to remember not to try to build exit
7594 circuits on it. Closes ticket 13814; patch by "teor".
7595 - Stop requiring exits to have non-zero bandwithcapacity in a
7596 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
7597 ignore exit bandwidthcapacity. This assists in bootstrapping a
7598 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
7599 on 0.2.0.3-alpha. Patch by "teor".
7600 - Add "internal" to some bootstrap statuses when no exits are
7601 available. If the consensus does not contain Exits, Tor will only
7602 build internal circuits. In this case, relevant statuses will
7603 contain the word "internal" as indicated in the Tor control-
7604 spec.txt. When bootstrap completes, Tor will be ready to build
7605 internal circuits. If a future consensus contains Exits, exit
7606 circuits may become available. Fixes part of bug 13718; bugfix on
7607 0.2.4.10-alpha. Patch by "teor".
7608 - Decrease minimum consensus interval to 10 seconds when
7609 TestingTorNetwork is set, or 5 seconds for the first consensus.
7610 Fix assumptions throughout the code that assume larger intervals.
7611 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
7613 - Avoid excluding guards from path building in minimal test
7614 networks, when we're in a test network and excluding guards would
7615 exclude all relays. This typically occurs in incredibly small tor
7616 networks, and those using "TestingAuthVoteGuard *". Fixes part of
7617 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
7619 o Minor bugfixes (testing):
7620 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
7621 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
7622 - Stop spawn test failures due to a race condition between the
7623 SIGCHLD handler updating the process status, and the test reading
7624 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
7625 - Avoid passing an extra backslash when creating a temporary
7626 directory for running the unit tests on Windows. Fixes bug 12392;
7627 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
7629 o Minor bugfixes (TLS):
7630 - Check more thoroughly throughout the TLS code for possible
7631 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
7633 o Minor bugfixes (transparent proxy):
7634 - Use getsockname, not getsockopt, to retrieve the address for a
7635 TPROXY-redirected connection. Fixes bug 13796; bugfix
7638 o Minor bugfixes (windows):
7639 - Remove code to special-case handling of NTE_BAD_KEYSET when
7640 acquiring windows CryptoAPI context. This error can't actually
7641 occur for the parameters we're providing. Fixes bug 10816; bugfix
7644 o Minor bugfixes (zlib):
7645 - Avoid truncating a zlib stream when trying to finalize it with an
7646 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
7648 o Code simplification and refactoring:
7649 - Change the entry_is_live() function to take named bitfield
7650 elements instead of an unnamed list of booleans. Closes
7652 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
7653 Resolves ticket 12205.
7654 - Use calloc and reallocarray functions instead of multiply-
7655 then-malloc. This makes it less likely for us to fall victim to an
7656 integer overflow attack when allocating. Resolves ticket 12855.
7657 - Use the standard macro name SIZE_MAX, instead of our
7659 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
7660 functions which take them as arguments. Replace 0 with NO_DIRINFO
7661 in a function call for clarity. Seeks to prevent future issues
7663 - Avoid 4 null pointer errors under clang static analysis by using
7664 tor_assert() to prove that the pointers aren't null. Fixes
7666 - Rework the API of policies_parse_exit_policy() to use a bitmask to
7667 represent parsing options, instead of a confusing mess of
7668 booleans. Resolves ticket 8197.
7669 - Introduce a helper function to parse ExitPolicy in
7670 or_options_t structure.
7671 - Move fields related to isolating and configuring client ports into
7672 a shared structure. Previously, they were duplicated across
7673 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
7674 to copy them correctly had been the cause of at least one bug in
7675 the past. Closes ticket 8546.
7676 - Refactor the get_interface_addresses_raw() doom-function into
7677 multiple smaller and simpler subfunctions. Cover the resulting
7678 subfunctions with unit-tests. Fixes a significant portion of
7680 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
7681 only for version <= 0.2.2.24 which is now deprecated. Closes
7683 - Remove a test for a long-defunct broken version-one
7685 - Refactor main loop to extract the 'loop' part. This makes it
7686 easier to run Tor under Shadow. Closes ticket 15176.
7687 - Stop using can_complete_circuits as a global variable; access it
7688 with a function instead.
7689 - Avoid using operators directly as macro arguments: this lets us
7690 apply coccinelle transformations to our codebase more directly.
7691 Closes ticket 13172.
7692 - Combine the functions used to parse ClientTransportPlugin and
7693 ServerTransportPlugin into a single function. Closes ticket 6456.
7694 - Add inline functions and convenience macros for inspecting channel
7695 state. Refactor the code to use convenience macros instead of
7696 checking channel state directly. Fixes issue 7356.
7697 - Document all members of was_router_added_t and rename
7698 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
7699 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
7700 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
7701 constant instead of hardcoded value. Fixes issue 13840.
7702 - Refactor our generic strmap and digestmap types into a single
7703 implementation, so that we can add a new digest256map
7707 - Add a doc/TUNING document with tips for handling large numbers of
7708 TCP connections when running busy Tor relay. Update the warning
7709 message to point to this file when running out of sockets
7710 operating system is allowing to use simultaneously. Resolves
7712 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
7713 for writing the OpenBSD-specific tips. Resolves ticket 13702.
7714 - Make the tor-resolve documentation match its help string and its
7715 options. Resolves part of ticket 14325.
7716 - Log a more useful error message from tor-resolve when failing to
7717 look up a hidden service address. Resolves part of ticket 14325.
7718 - Document the bridge-authority-only 'networkstatus-bridges' file.
7719 Closes ticket 13713; patch from "tom".
7720 - Fix typo in PredictedPortsRelevanceTime option description in
7721 manpage. Resolves issue 13707.
7722 - Stop suggesting that users specify relays by nickname: it isn't a
7723 good idea. Also, properly cross-reference how to specify relays in
7724 all parts of manual documenting options that take a list of
7725 relays. Closes ticket 13381.
7726 - Clarify the HiddenServiceDir option description in manpage to make
7727 it clear that relative paths are taken with respect to the current
7728 working directory. Also clarify that this behavior is not
7729 guaranteed to remain indefinitely. Fixes issue 13913.
7731 o Distribution (systemd):
7732 - systemd unit file: only allow tor to write to /var/lib/tor and
7733 /var/log/tor. The rest of the filesystem is accessible for reading
7734 only. Patch by intrigeri; resolves ticket 12751.
7735 - systemd unit file: ensure that the process and all its children
7736 can never gain new privileges. Patch by intrigeri; resolves
7738 - systemd unit file: set up /var/run/tor as writable for the Tor
7739 service. Patch by intrigeri; resolves ticket 13196.
7741 o Downgraded warnings:
7742 - Don't warn when we've attempted to contact a relay using the wrong
7743 ntor onion key. Closes ticket 9635.
7746 - Remove some lingering dead code that once supported mempools.
7747 Mempools were disabled by default in 0.2.5, and removed entirely
7748 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
7751 o Removed features (directory authorities):
7752 - Remove code that prevented authorities from listing Tor relays
7753 affected by CVE-2011-2769 as guards. These relays are already
7754 rejected altogether due to the minimum version requirement of
7755 0.2.3.16-alpha. Closes ticket 13152.
7756 - The "AuthDirRejectUnlisted" option no longer has any effect, as
7757 the fingerprints file (approved-routers) has been deprecated.
7758 - Directory authorities do not support being Naming dirauths anymore.
7759 The "NamingAuthoritativeDir" config option is now obsolete.
7760 - Directory authorities do not support giving out the BadDirectory
7762 - Directory authorities no longer advertise or support consensus
7763 methods 1 through 12 inclusive. These consensus methods were
7764 obsolete and/or insecure: maintaining the ability to support them
7765 served no good purpose. Implements part of proposal 215; closes
7769 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
7770 longer silently accepted as an alias for "ExitNodes".
7771 - The --enable-mempool and --enable-buf-freelists options, which
7772 were originally created to work around bad malloc implementations,
7773 no longer exist. They were off-by-default in 0.2.5. Closes
7775 - We no longer remind the user about configuration options that have
7776 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
7777 - Remove our old, non-weighted bandwidth-based node selection code.
7778 Previously, we used it as a fallback when we couldn't perform
7779 weighted bandwidth-based node selection. But that would only
7780 happen in the cases where we had no consensus, or when we had a
7781 consensus generated by buggy or ancient directory authorities. In
7782 either case, it's better to use the more modern, better maintained
7783 algorithm, with reasonable defaults for the weights. Closes
7785 - Remove the --disable-curve25519 configure option. Relays and
7786 clients now are required to support curve25519 and the
7788 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
7789 used to be deprecated synonyms for "StrictNodes", are now marked
7790 obsolete. Resolves ticket 12226.
7791 - Clients don't understand the BadDirectory flag in the consensus
7792 anymore, and ignore it.
7794 o Removed platform support:
7795 - We no longer include special code to build on Windows CE; as far
7796 as we know, nobody has used Tor on Windows CE in a very long time.
7797 Closes ticket 11446.
7799 o Testing (test-network.sh):
7800 - Stop using "echo -n", as some shells' built-in echo doesn't
7801 support "-n". Instead, use "/bin/echo -n". Partially fixes
7803 - Stop an apparent test-network hang when used with make -j2. Fixes
7805 - Add a --delay option to test-network.sh, which configures the
7806 delay before the chutney network tests for data transmission.
7807 Partially implements ticket 13161.
7810 - Test that tor does not fail when key files are zero-length. Check
7811 that tor generates new keys, and overwrites the empty key files.
7812 - Test that tor generates new keys when keys are missing
7813 (existing behavior).
7814 - Test that tor does not overwrite key files that already contain
7815 data (existing behavior). Tests bug 13111. Patch by "teor".
7816 - New "make test-stem" target to run stem integration tests.
7817 Requires that the "STEM_SOURCE_DIR" environment variable be set.
7818 Closes ticket 14107.
7819 - Make the test_cmdline_args.py script work correctly on Windows.
7820 Patch from Gisle Vanem.
7821 - Move the slower unit tests into a new "./src/test/test-slow"
7822 binary that can be run independently of the other tests. Closes
7824 - New tests for many parts of channel, relay, and circuitmux
7825 functionality. Code by Andrea; part of 9262.
7826 - New tests for parse_transport_line(). Part of ticket 6456.
7827 - In the unit tests, use chgrp() to change the group of the unit
7828 test temporary directory to the current user, so that the sticky
7829 bit doesn't interfere with tests that check directory groups.
7831 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
7833 - Refactor the function that chooses guard nodes so that it can more
7834 easily be tested; write some tests for it.
7835 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
7836 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
7837 - Create unit tests for format_time_interval(). With bug 13393.
7838 - Add unit tests for tor_timegm signed overflow, tor_timegm and
7839 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
7840 tests (visible) fixes in bug 13476.
7841 - Add a "coverage-html" make target to generate HTML-visualized
7842 coverage results when building with --enable-coverage. (Requires
7843 lcov.) Patch from Kevin Murray.
7844 - Enable the backtrace handler (where supported) when running the
7846 - Revise all unit tests that used the legacy test_* macros to
7847 instead use the recommended tt_* macros. This patch was generated
7848 with coccinelle, to avoid manual errors. Closes ticket 13119.
7850 Changes in version 0.2.5.11 - 2015-03-17
7851 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
7853 It backports several bugfixes from the 0.2.6 branch, including a
7854 couple of medium-level security fixes for relays and exit nodes.
7855 It also updates the list of directory authorities.
7857 o Directory authority changes:
7858 - Remove turtles as a directory authority.
7859 - Add longclaw as a new (v3) directory authority. This implements
7860 ticket 13296. This keeps the directory authority count at 9.
7861 - The directory authority Faravahar has a new IP address. This
7862 closes ticket 14487.
7864 o Major bugfixes (crash, OSX, security):
7865 - Fix a remote denial-of-service opportunity caused by a bug in
7866 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7869 o Major bugfixes (relay, stability, possible security):
7870 - Fix a bug that could lead to a relay crashing with an assertion
7871 failure if a buffer of exactly the wrong layout was passed to
7872 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7873 0.2.0.10-alpha. Patch from 'cypherpunks'.
7874 - Do not assert if the 'data' pointer on a buffer is advanced to the
7875 very end of the buffer; log a BUG message instead. Only assert if
7876 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7878 o Major bugfixes (exit node stability):
7879 - Fix an assertion failure that could occur under high DNS load.
7880 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7881 diagnosed and fixed by "cypherpunks".
7883 o Major bugfixes (Linux seccomp2 sandbox):
7884 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7885 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7886 0.2.5.1-alpha. Patch from "sanic".
7888 o Minor features (controller):
7889 - New "GETINFO bw-event-cache" to get information about recent
7890 bandwidth events. Closes ticket 14128. Useful for controllers to
7891 get recent bandwidth history after the fix for ticket 13988.
7893 o Minor features (geoip):
7894 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7895 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7898 o Minor bugfixes (client, automapping):
7899 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7900 no value follows the option. Fixes bug 14142; bugfix on
7901 0.2.4.7-alpha. Patch by "teor".
7902 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7903 14195; bugfix on 0.1.0.1-rc.
7905 o Minor bugfixes (compilation):
7906 - Build without warnings with the stock OpenSSL srtp.h header, which
7907 has a duplicate declaration of SSL_get_selected_srtp_profile().
7908 Fixes bug 14220; this is OpenSSL's bug, not ours.
7910 o Minor bugfixes (directory authority):
7911 - Allow directory authorities to fetch more data from one another if
7912 they find themselves missing lots of votes. Previously, they had
7913 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7914 bugfix on 0.1.2.5-alpha.
7915 - Enlarge the buffer to read bwauth generated files to avoid an
7916 issue when parsing the file in dirserv_read_measured_bandwidths().
7917 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7919 o Minor bugfixes (statistics):
7920 - Increase period over which bandwidth observations are aggregated
7921 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7923 o Minor bugfixes (preventative security, C safety):
7924 - When reading a hexadecimal, base-32, or base-64 encoded value from
7925 a string, always overwrite the whole output buffer. This prevents
7926 some bugs where we would look at (but fortunately, not reveal)
7927 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7931 Changes in version 0.2.4.26 - 2015-03-17
7932 Tor 0.2.4.26 includes an updated list of directory authorities. It
7933 also backports a couple of stability and security bugfixes from 0.2.5
7936 o Directory authority changes:
7937 - Remove turtles as a directory authority.
7938 - Add longclaw as a new (v3) directory authority. This implements
7939 ticket 13296. This keeps the directory authority count at 9.
7940 - The directory authority Faravahar has a new IP address. This
7941 closes ticket 14487.
7943 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
7944 - Fix an assertion failure that could occur under high DNS load.
7945 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7946 diagnosed and fixed by "cypherpunks".
7948 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
7949 - Fix a bug that could lead to a relay crashing with an assertion
7950 failure if a buffer of exactly the wrong layout was passed to
7951 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7952 0.2.0.10-alpha. Patch from 'cypherpunks'.
7953 - Do not assert if the 'data' pointer on a buffer is advanced to the
7954 very end of the buffer; log a BUG message instead. Only assert if
7955 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7957 o Minor features (geoip):
7958 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7959 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7962 Changes in version 0.2.5.10 - 2014-10-24
7963 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
7965 It adds several new security features, including improved
7966 denial-of-service resistance for relays, new compiler hardening
7967 options, and a system-call sandbox for hardened installations on Linux
7968 (requires seccomp2). The controller protocol has several new features,
7969 resolving IPv6 addresses should work better than before, and relays
7970 should be a little more CPU-efficient. We've added support for more
7971 OpenBSD and FreeBSD transparent proxy types. We've improved the build
7972 system and testing infrastructure to allow unit testing of more parts
7973 of the Tor codebase. Finally, we've addressed several nagging pluggable
7974 transport usability issues, and included numerous other small bugfixes
7975 and features mentioned below.
7977 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
7978 have accumulated many known flaws; everyone should upgrade.
7980 o Major features (security):
7981 - The ntor handshake is now on-by-default, no matter what the
7982 directory authorities recommend. Implements ticket 8561.
7983 - Make the "tor-gencert" tool used by directory authority operators
7984 create 2048-bit signing keys by default (rather than 1024-bit, since
7985 1024-bit is uncomfortably small these days). Addresses ticket 10324.
7986 - Warn about attempts to run hidden services and relays in the same
7987 process: that's probably not a good idea. Closes ticket 12908.
7988 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
7989 today support TLS 1.0 or later, so we can safely turn off support
7990 for this old (and insecure) protocol. Fixes bug 13426.
7992 o Major features (relay security, DoS-resistance):
7993 - When deciding whether we have run out of memory and we need to
7994 close circuits, also consider memory allocated in buffers for
7995 streams attached to each circuit.
7997 This change, which extends an anti-DoS feature introduced in
7998 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
7999 better resist more memory-based DoS attacks than before. Since the
8000 MaxMemInCellQueues option now applies to all queues, it is renamed
8001 to MaxMemInQueues. This feature fixes bug 10169.
8002 - Avoid hash-flooding denial-of-service attacks by using the secure
8003 SipHash-2-4 hash function for our hashtables. Without this
8004 feature, an attacker could degrade performance of a targeted
8005 client or server by flooding their data structures with a large
8006 number of entries to be stored at the same hash table position,
8007 thereby slowing down the Tor instance. With this feature, hash
8008 table positions are derived from a randomized cryptographic key,
8009 and an attacker cannot predict which entries will collide. Closes
8011 - If you don't specify MaxMemInQueues yourself, Tor now tries to
8012 pick a good value based on your total system memory. Previously,
8013 the default was always 8 GB. You can still override the default by
8014 setting MaxMemInQueues yourself. Resolves ticket 11396.
8016 o Major features (bridges and pluggable transports):
8017 - Add support for passing arguments to managed pluggable transport
8018 proxies. Implements ticket 3594.
8019 - Bridges now track GeoIP information and the number of their users
8020 even when pluggable transports are in use, and report usage
8021 statistics in their extra-info descriptors. Resolves tickets 4773
8023 - Don't launch pluggable transport proxies if we don't have any
8024 bridges configured that would use them. Now we can list many
8025 pluggable transports, and Tor will dynamically start one when it
8026 hears a bridge address that needs it. Resolves ticket 5018.
8027 - The bridge directory authority now assigns status flags (Stable,
8028 Guard, etc) to bridges based on thresholds calculated over all
8029 Running bridges. Now bridgedb can finally make use of its features
8030 to e.g. include at least one Stable bridge in its answers. Fixes
8033 o Major features (controller):
8034 - Extend ORCONN controller event to include an "ID" parameter,
8035 and add four new controller event types CONN_BW, CIRC_BW,
8036 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
8037 The new events are emitted in private Tor networks only, with the
8038 goal of being able to better track performance and load during
8039 full-network simulations. Implements proposal 218 and ticket 7359.
8041 o Major features (relay performance):
8042 - Speed up server-side lookups of rendezvous and introduction point
8043 circuits by using hashtables instead of linear searches. These
8044 functions previously accounted between 3 and 7% of CPU usage on
8045 some busy relays. Resolves ticket 9841.
8046 - Avoid wasting CPU when extending a circuit over a channel that is
8047 nearly out of circuit IDs. Previously, we would do a linear scan
8048 over possible circuit IDs before finding one or deciding that we
8049 had exhausted our possibilities. Now, we try at most 64 random
8050 circuit IDs before deciding that we probably won't succeed. Fixes
8051 a possible root cause of ticket 11553.
8053 o Major features (seccomp2 sandbox, Linux only):
8054 - Use the seccomp2 syscall filtering facility on Linux to limit
8055 which system calls Tor can invoke. This is an experimental,
8056 Linux-only feature to provide defense-in-depth against unknown
8057 attacks. To try turning it on, set "Sandbox 1" in your torrc
8058 file. Please be ready to report bugs. We hope to add support
8059 for better sandboxing in the future, including more fine-grained
8060 filters, better division of responsibility, and support for more
8061 platforms. This work has been done by Cristian-Matei Toader for
8062 Google Summer of Code. Resolves tickets 11351 and 11465.
8064 o Major features (testing networks):
8065 - Make testing Tor networks bootstrap better: lower directory fetch
8066 retry schedules and maximum interval without directory requests,
8067 and raise maximum download tries. Implements ticket 6752.
8068 - Add make target 'test-network' to run tests on a Chutney network.
8069 Implements ticket 8530.
8071 o Major features (other):
8072 - On some platforms (currently: recent OSX versions, glibc-based
8073 platforms that support the ELF format, and a few other
8074 Unix-like operating systems), Tor can now dump stack traces
8075 when a crash occurs or an assertion fails. By default, traces
8076 are dumped to stderr (if possible) and to any logs that are
8077 reporting errors. Implements ticket 9299.
8079 o Deprecated versions:
8080 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
8081 attention for some while.
8083 o Major bugfixes (security, directory authorities):
8084 - Directory authorities now include a digest of each relay's
8085 identity key as a part of its microdescriptor.
8087 This is a workaround for bug 11743 (reported by "cypherpunks"),
8088 where Tor clients do not support receiving multiple
8089 microdescriptors with the same SHA256 digest in the same
8090 consensus. When clients receive a consensus like this, they only
8091 use one of the relays. Without this fix, a hostile relay could
8092 selectively disable some client use of target relays by
8093 constructing a router descriptor with a different identity and the
8094 same microdescriptor parameters and getting the authorities to
8095 list it in a microdescriptor consensus. This fix prevents an
8096 attacker from causing a microdescriptor collision, because the
8097 router's identity is not forgeable.
8099 o Major bugfixes (openssl bug workaround):
8100 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8101 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
8102 bug 13471. This is a workaround for an OpenSSL bug.
8104 o Major bugfixes (client):
8105 - Perform circuit cleanup operations even when circuit
8106 construction operations are disabled (because the network is
8107 disabled, or because there isn't enough directory information).
8108 Previously, when we were not building predictive circuits, we
8109 were not closing expired circuits either. Fixes bug 8387; bugfix on
8110 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
8111 became more strict about when we have "enough directory information
8114 o Major bugfixes (client, pluggable transports):
8115 - When managing pluggable transports, use OS notification facilities
8116 to learn if they have crashed, and don't attempt to kill any
8117 process that has already exited. Fixes bug 8746; bugfix
8120 o Major bugfixes (relay denial of service):
8121 - Instead of writing destroy cells directly to outgoing connection
8122 buffers, queue them and intersperse them with other outgoing cells.
8123 This can prevent a set of resource starvation conditions where too
8124 many pending destroy cells prevent data cells from actually getting
8125 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
8126 bugfix on 0.2.0.1-alpha.
8128 o Major bugfixes (relay):
8129 - Avoid queuing or sending destroy cells for circuit ID zero when we
8130 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
8131 Found and fixed by "cypherpunks".
8132 - Fix ORPort reachability detection on relays running behind a
8133 proxy, by correctly updating the "local" mark on the controlling
8134 channel when changing the address of an or_connection_t after the
8135 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
8136 - Use a direct dirport connection when uploading non-anonymous
8137 descriptors to the directory authorities. Previously, relays would
8138 incorrectly use tunnel connections under a fairly wide variety of
8139 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
8140 - When a circuit accidentally has the same circuit ID for its
8141 forward and reverse direction, correctly detect the direction of
8142 cells using that circuit. Previously, this bug made roughly one
8143 circuit in a million non-functional. Fixes bug 12195; this is a
8144 bugfix on every version of Tor.
8146 o Minor features (security):
8147 - New --enable-expensive-hardening option to enable security
8148 hardening options that consume nontrivial amounts of CPU and
8149 memory. Right now, this includes AddressSanitizer and UbSan, which
8150 are supported in newer versions of GCC and Clang. Closes ticket
8152 - Authorities now assign the Guard flag to the fastest 25% of the
8153 network (it used to be the fastest 50%). Also raise the consensus
8154 weight that guarantees the Guard flag from 250 to 2000. For the
8155 current network, this results in about 1100 guards, down from 2500.
8156 This step paves the way for moving the number of entry guards
8157 down to 1 (proposal 236) while still providing reasonable expected
8158 performance for most users. Implements ticket 12690.
8160 o Minor features (security, memory management):
8161 - Memory allocation tricks (mempools and buffer freelists) are now
8162 disabled by default. You can turn them back on with
8163 --enable-mempools and --enable-buf-freelists respectively. We're
8164 disabling these features because malloc performance is good enough
8165 on most platforms, and a similar feature in OpenSSL exacerbated
8166 exploitation of the Heartbleed attack. Resolves ticket 11476.
8168 o Minor features (bridge client):
8169 - Report a more useful failure message when we can't connect to a
8170 bridge because we don't have the right pluggable transport
8171 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
8173 o Minor features (bridge):
8174 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
8175 cookie file for the ExtORPort g+r by default.
8177 o Minor features (bridges, pluggable transports):
8178 - Bridges now write the SHA1 digest of their identity key
8179 fingerprint (that is, a hash of a hash of their public key) to
8180 notice-level logs, and to a new hashed-fingerprint file. This
8181 information will help bridge operators look up their bridge in
8182 Globe and similar tools. Resolves ticket 10884.
8183 - Improve the message that Tor displays when running as a bridge
8184 using pluggable transports without an Extended ORPort listener.
8185 Also, log the message in the log file too. Resolves ticket 11043.
8186 - Add threshold cutoffs to the networkstatus document created by
8187 the Bridge Authority. Fixes bug 1117.
8188 - On Windows, spawn background processes using the CREATE_NO_WINDOW
8189 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
8190 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
8191 Vidalia set this option for us.) Implements ticket 10297.
8193 o Minor features (build):
8194 - The configure script has a --disable-seccomp option to turn off
8195 support for libseccomp on systems that have it, in case it (or
8196 Tor's use of it) is broken. Resolves ticket 11628.
8197 - Assume that a user using ./configure --host wants to cross-compile,
8198 and give an error if we cannot find a properly named
8199 tool-chain. Add a --disable-tool-name-check option to proceed
8200 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
8201 - If we run ./configure and the compiler recognizes -fstack-protector
8202 but the linker rejects it, warn the user about a potentially missing
8203 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
8204 - Add support for `--library-versions` flag. Implements ticket 6384.
8205 - Return the "unexpected sendme" warnings to a warn severity, but make
8206 them rate limited, to help diagnose ticket 8093.
8207 - Detect a missing asciidoc, and warn the user about it, during
8208 configure rather than at build time. Fixes issue 6506. Patch from
8211 o Minor features (client):
8212 - Add a new option, PredictedPortsRelevanceTime, to control how long
8213 after having received a request to connect to a given port Tor
8214 will try to keep circuits ready in anticipation of future requests
8215 for that port. Patch from "unixninja92"; implements ticket 9176.
8217 o Minor features (config options and command line):
8218 - Add an --allow-missing-torrc commandline option that tells Tor to
8219 run even if the configuration file specified by -f is not available.
8220 Implements ticket 10060.
8221 - Add support for the TPROXY transparent proxying facility on Linux.
8222 See documentation for the new TransProxyType option for more
8223 details. Implementation by "thomo". Closes ticket 10582.
8225 o Minor features (config options):
8226 - Config (torrc) lines now handle fingerprints which are missing
8227 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
8228 - Support a --dump-config option to print some or all of the
8229 configured options. Mainly useful for debugging the command-line
8230 option parsing code. Helps resolve ticket 4647.
8231 - Raise awareness of safer logging: notify user of potentially
8232 unsafe config options, like logging more verbosely than severity
8233 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
8234 - Add a new configuration option TestingV3AuthVotingStartOffset
8235 that bootstraps a network faster by changing the timing for
8236 consensus votes. Addresses ticket 8532.
8237 - Add a new torrc option "ServerTransportOptions" that allows
8238 bridge operators to pass configuration parameters to their
8239 pluggable transports. Resolves ticket 8929.
8240 - The config (torrc) file now accepts bandwidth and space limits in
8241 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
8242 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
8245 o Minor features (controller):
8246 - Make the entire exit policy available from the control port via
8247 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
8249 - Because of the fix for ticket 11396, the real limit for memory
8250 usage may no longer match the configured MaxMemInQueues value. The
8251 real limit is now exposed via GETINFO limits/max-mem-in-queues.
8252 - Add a new "HS_DESC" controller event that reports activities
8253 related to hidden service descriptors. Resolves ticket 8510.
8254 - New "DROPGUARDS" controller command to forget all current entry
8255 guards. Not recommended for ordinary use, since replacing guards
8256 too frequently makes several attacks easier. Resolves ticket 9934;
8258 - Implement the TRANSPORT_LAUNCHED control port event that
8259 notifies controllers about new launched pluggable
8260 transports. Resolves ticket 5609.
8262 o Minor features (diagnostic):
8263 - When logging a warning because of bug 7164, additionally check the
8264 hash table for consistency (as proposed on ticket 11737). This may
8265 help diagnose bug 7164.
8266 - When we log a heartbeat, log how many one-hop circuits we have
8267 that are at least 30 minutes old, and log status information about
8268 a few of them. This is an attempt to track down bug 8387.
8269 - When encountering an unexpected CR while writing text to a file on
8270 Windows, log the name of the file. Should help diagnosing
8272 - Give more specific warnings when a client notices that an onion
8273 handshake has failed. Fixes ticket 9635.
8274 - Add significant new logging code to attempt to diagnose bug 12184,
8275 where relays seem to run out of available circuit IDs.
8276 - Improve the diagnostic log message for bug 8387 even further to
8277 try to improve our odds of figuring out why one-hop directory
8278 circuits sometimes do not get closed.
8279 - Add more log messages to diagnose bug 7164, which causes
8280 intermittent "microdesc_free() called but md was still referenced"
8281 warnings. We now include more information, to figure out why we
8282 might be cleaning a microdescriptor for being too old if it's
8283 still referenced by a live node_t object.
8284 - Log current accounting state (bytes sent and received + remaining
8285 time for the current accounting period) in the relay's heartbeat
8286 message. Implements ticket 5526; patch from Peter Retzlaff.
8288 o Minor features (geoip):
8289 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8292 o Minor features (interface):
8293 - Generate a warning if any ports are listed in the SocksPolicy,
8294 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
8295 AuthDirBadExit options. (These options only support address
8296 ranges.) Fixes part of ticket 11108.
8298 o Minor features (kernel API usage):
8299 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
8300 sockets in a single system call. Implements ticket 5129.
8302 o Minor features (log messages):
8303 - When ServerTransportPlugin is set on a bridge, Tor can write more
8304 useful statistics about bridge use in its extrainfo descriptors,
8305 but only if the Extended ORPort ("ExtORPort") is set too. Add a
8306 log message to inform the user in this case. Resolves ticket 9651.
8307 - When receiving a new controller connection, log the origin address.
8308 Resolves ticket 9698; patch from "sigpipe".
8309 - When logging OpenSSL engine status at startup, log the status of
8310 more engines. Fixes ticket 10043; patch from Joshua Datko.
8312 o Minor features (log verbosity):
8313 - Demote the message that we give when a flushing connection times
8314 out for too long from NOTICE to INFO. It was usually meaningless.
8315 Resolves ticket 5286.
8316 - Don't log so many notice-level bootstrapping messages at startup
8317 about downloading descriptors. Previously, we'd log a notice
8318 whenever we learned about more routers. Now, we only log a notice
8319 at every 5% of progress. Fixes bug 9963.
8320 - Warn less verbosely when receiving a malformed
8321 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
8323 o Minor features (performance):
8324 - If we're using the pure-C 32-bit curve25519_donna implementation
8325 of curve25519, build it with the -fomit-frame-pointer option to
8326 make it go faster on register-starved hosts. This improves our
8327 handshake performance by about 6% on i386 hosts without nacl.
8330 o Minor features (relay):
8331 - If a circuit timed out for at least 3 minutes, check if we have a
8332 new external IP address, and publish a new descriptor with the new
8333 IP address if it changed. Resolves ticket 2454.
8335 o Minor features (testing):
8336 - If Python is installed, "make check" now runs extra tests beyond
8337 the unit test scripts.
8338 - When bootstrapping a test network, sometimes very few relays get
8339 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
8340 specify a set of relays which should be voted Guard regardless of
8341 their uptime or bandwidth. Addresses ticket 9206.
8343 o Minor features (transparent proxy, *BSD):
8344 - Support FreeBSD's ipfw firewall interface for TransPort ports on
8345 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
8346 10267; patch from "yurivict".
8347 - Support OpenBSD's divert-to rules with the pf firewall for
8348 transparent proxy ports. To enable it, set "TransProxyType
8349 pf-divert". This allows Tor to run a TransPort transparent proxy
8350 port on OpenBSD 4.4 or later without root privileges. See the
8351 pf.conf(5) manual page for information on configuring pf to use
8352 divert-to rules. Closes ticket 10896; patch from Dana Koch.
8354 o Minor bugfixes (bridge client):
8355 - Stop accepting bridge lines containing hostnames. Doing so would
8356 cause clients to perform DNS requests on the hostnames, which was
8357 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
8359 o Minor bugfixes (bridges):
8360 - Avoid potential crashes or bad behavior when launching a
8361 server-side managed proxy with ORPort or ExtORPort temporarily
8362 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
8363 - Fix a bug where the first connection works to a bridge that uses a
8364 pluggable transport with client-side parameters, but we don't send
8365 the client-side parameters on subsequent connections. (We don't
8366 use any pluggable transports with client-side parameters yet,
8367 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
8368 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
8370 o Minor bugfixes (build, auxiliary programs):
8371 - Stop preprocessing the "torify" script with autoconf, since
8372 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
8374 - The tor-fw-helper program now follows the standard convention and
8375 exits with status code "0" on success. Fixes bug 9030; bugfix on
8376 0.2.3.1-alpha. Patch by Arlo Breault.
8377 - Corrected ./configure advice for what openssl dev package you should
8378 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
8380 o Minor bugfixes (client):
8381 - Avoid "Tried to open a socket with DisableNetwork set" warnings
8382 when starting a client with bridges configured and DisableNetwork
8383 set. (Tor launcher starts Tor with DisableNetwork set the first
8384 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
8385 - Improve the log message when we can't connect to a hidden service
8386 because all of the hidden service directory nodes hosting its
8387 descriptor are excluded. Improves on our fix for bug 10722, which
8388 was a bugfix on 0.2.0.10-alpha.
8389 - Raise a control port warning when we fail to connect to all of
8390 our bridges. Previously, we didn't inform the controller, and
8391 the bootstrap process would stall. Fixes bug 11069; bugfix on
8393 - Exit immediately when a process-owning controller exits.
8394 Previously, tor relays would wait for a little while after their
8395 controller exited, as if they had gotten an INT signal -- but this
8396 was problematic, since there was no feedback for the user. To do a
8397 clean shutdown, controllers should send an INT signal and give Tor
8398 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
8399 - Stop attempting to connect to bridges before our pluggable
8400 transports are configured (harmless but resulted in some erroneous
8401 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
8402 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
8403 generating incorrect SOCKS5 responses, and confusing client
8404 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
8406 o Minor bugfixes (client, DNSPort):
8407 - When using DNSPort, try to respond to AAAA requests with AAAA
8408 answers. Previously, we hadn't looked at the request type when
8409 deciding which answer type to prefer. Fixes bug 10468; bugfix on
8411 - When receiving a DNS query for an unsupported record type, reply
8412 with no answer rather than with a NOTIMPL error. This behavior
8413 isn't correct either, but it will break fewer client programs, we
8414 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
8417 o Minor bugfixes (client, logging during bootstrap):
8418 - Only report the first fatal bootstrap error on a given OR
8419 connection. This stops us from telling the controller bogus error
8420 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
8421 - Avoid generating spurious warnings when starting with
8422 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
8425 o Minor bugfixes (closing OR connections):
8426 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
8427 check if it's an or_connection_t and correctly call
8428 connection_or_close_for_error() rather than
8429 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
8431 - When closing all connections on setting DisableNetwork to 1, use
8432 connection_or_close_normally() rather than closing OR connections
8433 out from under the channel layer. Fixes bug 11306; bugfix on
8436 o Minor bugfixes (code correctness):
8437 - Previously we used two temporary files when writing descriptors to
8438 disk; now we only use one. Fixes bug 1376.
8439 - Remove an erroneous (but impossible and thus harmless) pointer
8440 comparison that would have allowed compilers to skip a bounds
8441 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
8442 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
8443 - Fix an always-true assertion in pluggable transports code so it
8444 actually checks what it was trying to check. Fixes bug 10046;
8445 bugfix on 0.2.3.9-alpha. Found by "dcb".
8447 o Minor bugfixes (command line):
8448 - Use a single command-line parser for parsing torrc options on the
8449 command line and for finding special command-line options to avoid
8450 inconsistent behavior for torrc option arguments that have the same
8451 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
8453 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
8454 9573; bugfix on 0.0.9pre5.
8456 o Minor bugfixes (compilation):
8457 - Compile correctly with builds and forks of OpenSSL (such as
8458 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
8459 0.2.1.1-alpha. Patch from "dhill".
8460 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
8461 turned off (that is, without support for v2 link handshakes). Fixes
8462 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
8463 - In routerlist_assert_ok(), don't take the address of a
8464 routerinfo's cache_info member unless that routerinfo is non-NULL.
8465 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
8466 - Fix a large number of false positive warnings from the clang
8467 analyzer static analysis tool. This should make real warnings
8468 easier for clang analyzer to find. Patch from "teor". Closes
8470 - Resolve GCC complaints on OpenBSD about discarding constness in
8471 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
8472 on 0.1.1.23. Patch from Dana Koch.
8473 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
8474 treatment of long and time_t as comparable types. Fixes part of
8475 bug 11633. Patch from Dana Koch.
8476 - When deciding whether to build the 64-bit curve25519
8477 implementation, detect platforms where we can compile 128-bit
8478 arithmetic but cannot link it. Fixes bug 11729; bugfix on
8479 0.2.4.8-alpha. Patch from "conradev".
8480 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
8481 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
8482 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
8484 - Build and run correctly on systems like OpenBSD-current that have
8485 patched OpenSSL to remove get_cipher_by_char and/or its
8486 implementations. Fixes issue 13325.
8488 o Minor bugfixes (controller and command-line):
8489 - If changing a config option via "setconf" fails in a recoverable
8490 way, we used to nonetheless write our new control ports to the
8491 file described by the "ControlPortWriteToFile" option. Now we only
8492 write out that file if we successfully switch to the new config
8493 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
8495 o Minor bugfixes (directory server):
8496 - No longer accept malformed http headers when parsing urls from
8497 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
8498 bugfix on 0.0.6pre1.
8499 - When sending a compressed set of descriptors or microdescriptors,
8500 make sure to finalize the zlib stream. Previously, we would write
8501 all the compressed data, but if the last descriptor we wanted to
8502 send was missing or too old, we would not mark the stream as
8503 finished. This caused problems for decompression tools. Fixes bug
8504 11648; bugfix on 0.1.1.23.
8506 o Minor bugfixes (hidden service):
8507 - Only retry attempts to connect to a chosen rendezvous point 8
8508 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
8510 o Minor bugfixes (interface):
8511 - Reject relative control socket paths and emit a warning. Previously,
8512 single-component control socket paths would be rejected, but Tor
8513 would not log why it could not validate the config. Fixes bug 9258;
8514 bugfix on 0.2.3.16-alpha.
8516 o Minor bugfixes (log messages):
8517 - Fix a bug where clients using bridges would report themselves
8518 as 50% bootstrapped even without a live consensus document.
8519 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
8520 - Suppress a warning where, if there's only one directory authority
8521 in the network, we would complain that votes and signatures cannot
8522 be uploaded to other directory authorities. Fixes bug 10842;
8523 bugfix on 0.2.2.26-beta.
8524 - Report bootstrapping progress correctly when we're downloading
8525 microdescriptors. We had updated our "do we have enough microdescs
8526 to begin building circuits?" logic most recently in 0.2.4.10-alpha
8527 (see bug 5956), but we left the bootstrap status event logic at
8528 "how far through getting 1/4 of them are we?" Fixes bug 9958;
8529 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
8531 o Minor bugfixes (logging):
8532 - Downgrade "Unexpected onionskin length after decryption" warning
8533 to a protocol-warn, since there's nothing relay operators can do
8534 about a client that sends them a malformed create cell. Resolves
8535 bug 12996; bugfix on 0.0.6rc1.
8536 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
8537 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
8538 - When logging information about an EXTEND2 or EXTENDED2 cell, log
8539 their names correctly. Fixes part of bug 12700; bugfix
8541 - When logging information about a relay cell whose command we don't
8542 recognize, log its command as an integer. Fixes part of bug 12700;
8543 bugfix on 0.2.1.10-alpha.
8544 - Escape all strings from the directory connection before logging
8545 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
8546 - Squelch a spurious LD_BUG message "No origin circuit for
8547 successful SOCKS stream" in certain hidden service failure cases;
8549 - Downgrade the severity of the 'unexpected sendme cell from client'
8550 from 'warn' to 'protocol warning'. Closes ticket 8093.
8552 o Minor bugfixes (misc code correctness):
8553 - In munge_extrainfo_into_routerinfo(), check the return value of
8554 memchr(). This would have been a serious issue if we ever passed
8555 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
8557 - On the chance that somebody manages to build Tor on a
8558 platform where time_t is unsigned, correct the way that
8559 microdesc_add_to_cache() handles negative time arguments.
8560 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
8561 - Fix various instances of undefined behavior in channeltls.c,
8562 tor_memmem(), and eventdns.c that would cause us to construct
8563 pointers to memory outside an allocated object. (These invalid
8564 pointers were not accessed, but C does not even allow them to
8565 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
8566 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
8567 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
8568 fix some miscellaneous errors in our tests and codebase. Fixes bug
8569 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
8570 - Always check return values for unlink, munmap, UnmapViewOfFile;
8571 check strftime return values more often. In some cases all we can
8572 do is report a warning, but this may help prevent deeper bugs from
8573 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
8575 - Fix numerous warnings from the clang "scan-build" static analyzer.
8576 Some of these are programming style issues; some of them are false
8577 positives that indicated awkward code; some are undefined behavior
8578 cases related to constructing (but not using) invalid pointers;
8579 some are assumptions about API behavior; some are (harmlessly)
8580 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
8581 correct; and one or two are genuine bugs that weren't reachable
8582 from the rest of the program. Fixes bug 8793; bugfixes on many,
8585 o Minor bugfixes (node selection):
8586 - If ExcludeNodes is set, consider non-excluded hidden service
8587 directory servers before excluded ones. Do not consider excluded
8588 hidden service directory servers at all if StrictNodes is
8589 set. (Previously, we would sometimes decide to connect to those
8590 servers, and then realize before we initiated a connection that
8591 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
8593 - If we set the ExitNodes option but it doesn't include any nodes
8594 that have the Exit flag, we would choose not to bootstrap. Now we
8595 bootstrap so long as ExitNodes includes nodes which can exit to
8596 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
8598 o Minor bugfixes (performance):
8599 - Avoid a bug where every successful connection made us recompute
8600 the flag telling us whether we have sufficient information to
8601 build circuits. Previously, we would forget our cached value
8602 whenever we successfully opened a channel (or marked a router as
8603 running or not running for any other reason), regardless of
8604 whether we had previously believed the router to be running. This
8605 forced us to run an expensive update operation far too often.
8606 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
8607 - Avoid using tor_memeq() for checking relay cell integrity. This
8608 removes a possible performance bottleneck. Fixes part of bug
8609 12169; bugfix on 0.2.1.31.
8611 o Minor bugfixes (platform-specific):
8612 - When dumping a malformed directory object to disk, save it in
8613 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
8615 - Don't report failures from make_socket_reuseable() on incoming
8616 sockets on OSX: this can happen when incoming connections close
8617 early. Fixes bug 10081.
8619 o Minor bugfixes (pluggable transports):
8620 - Avoid another 60-second delay when starting Tor in a pluggable-
8621 transport-using configuration when we already have cached
8622 descriptors for our bridges. Fixes bug 11965; bugfix
8625 o Minor bugfixes (protocol correctness):
8626 - When receiving a VERSIONS cell with an odd number of bytes, close
8627 the connection immediately since the cell is malformed. Fixes bug
8628 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
8631 o Minor bugfixes (relay, other):
8632 - We now drop CREATE cells for already-existent circuit IDs and for
8633 zero-valued circuit IDs, regardless of other factors that might
8634 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
8636 - When rejecting DATA cells for stream_id zero, still count them
8637 against the circuit's deliver window so that we don't fail to send
8638 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
8640 o Minor bugfixes (relay, threading):
8641 - Check return code on spawn_func() in cpuworker code, so that we
8642 don't think we've spawned a nonworking cpuworker and write junk to
8643 it forever. Fix related to bug 4345; bugfix on all released Tor
8644 versions. Found by "skruffy".
8645 - Use a pthread_attr to make sure that spawn_func() cannot return an
8646 error while at the same time launching a thread. Fix related to
8647 bug 4345; bugfix on all released Tor versions. Reported
8650 o Minor bugfixes (relays and bridges):
8651 - Avoid crashing on a malformed resolv.conf file when running a
8652 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
8653 - Non-exit relays no longer launch mock DNS requests to check for
8654 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
8655 non-exit relays stopped servicing DNS requests. Fixes bug 965;
8656 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
8657 - Bridges now report complete directory request statistics. Related
8658 to bug 5824; bugfix on 0.2.2.1-alpha.
8659 - Bridges now never collect statistics that were designed for
8660 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
8662 o Minor bugfixes (testing):
8663 - Fix all valgrind warnings produced by the unit tests. There were
8664 over a thousand memory leak warnings previously, mostly produced
8665 by forgetting to free things in the unit test code. Fixes bug
8666 11618, bugfixes on many versions of Tor.
8668 o Minor bugfixes (tor-fw-helper):
8669 - Give a correct log message when tor-fw-helper fails to launch.
8670 (Previously, we would say something like "tor-fw-helper sent us a
8671 string we could not parse".) Fixes bug 9781; bugfix
8674 o Minor bugfixes (trivial memory leaks):
8675 - Fix a small memory leak when signing a directory object. Fixes bug
8676 11275; bugfix on 0.2.4.13-alpha.
8677 - Resolve some memory leaks found by coverity in the unit tests, on
8678 exit in tor-gencert, and on a failure to compute digests for our
8679 own keys when generating a v3 networkstatus vote. These leaks
8680 should never have affected anyone in practice.
8682 o Code simplification and refactoring:
8683 - Remove some old fallback code designed to keep Tor clients working
8684 in a network with only two working relays. Elsewhere in the code we
8685 have long since stopped supporting such networks, so there wasn't
8686 much point in keeping it around. Addresses ticket 9926.
8687 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
8688 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
8689 - Extract the common duplicated code for creating a subdirectory
8690 of the data directory and writing to a file in it. Fixes ticket
8691 4282; patch from Peter Retzlaff.
8692 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
8693 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
8694 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
8695 - Add a set of accessor functions for the circuit timeout data
8696 structure. Fixes ticket 6153; patch from "piet".
8697 - Clean up exit paths from connection_listener_new(). Closes ticket
8698 8789. Patch from Arlo Breault.
8699 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
8700 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
8701 - Use a doubly-linked list to implement the global circuit list.
8702 Resolves ticket 9108. Patch from Marek Majkowski.
8703 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
8704 - Remove constants and tests for PKCS1 padding; it's insecure and
8705 shouldn't be used for anything new. Fixes bug 8792; patch
8707 - Remove instances of strcpy() from the unit tests. They weren't
8708 hurting anything, since they were only in the unit tests, but it's
8709 embarrassing to have strcpy() in the code at all, and some analysis
8710 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
8711 0.2.3.8-alpha. Patch from Arlo Breault.
8712 - Remove is_internal_IP() function. Resolves ticket 4645.
8713 - Remove unused function circuit_dump_by_chan from circuitlist.c.
8714 Closes issue 9107; patch from "marek".
8715 - Change our use of the ENUM_BF macro to avoid declarations that
8717 - Get rid of router->address, since in all cases it was just the
8718 string representation of router->addr. Resolves ticket 5528.
8721 - Adjust the URLs in the README to refer to the new locations of
8722 several documents on the website. Fixes bug 12830. Patch from
8724 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
8726 - Update manpage to describe some of the files you can expect to
8727 find in Tor's DataDirectory. Addresses ticket 9839.
8728 - Clean up several option names in the manpage to match their real
8729 names, add the missing documentation for a couple of testing and
8730 directory authority options, remove the documentation for a
8731 V2-directory fetching option that no longer exists. Resolves
8733 - Correct the documentation so that it lists the correct directory
8734 for the stats files. (They are in a subdirectory called "stats",
8736 - In the manpage, move more authority-only options into the
8737 directory authority section so that operators of regular directory
8738 caches don't get confused.
8739 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
8740 11061; bugfix on 0.2.4.7-alpha.
8741 - Resolve warnings from Doxygen.
8742 - Document in the manpage that "KBytes" may also be written as
8743 "kilobytes" or "KB", that "Kbits" may also be written as
8744 "kilobits", and so forth. Closes ticket 9222.
8745 - Document that the ClientOnly config option overrides ORPort.
8746 Our old explanation made ClientOnly sound as though it did
8747 nothing at all. Resolves bug 9059.
8748 - Explain that SocksPolicy, DirPolicy, and similar options don't
8749 take port arguments. Fixes the other part of ticket 11108.
8750 - Fix a comment about the rend_server_descriptor_t.protocols field
8751 to more accurately describe its range. Also, make that field
8752 unsigned, to more accurately reflect its usage. Fixes bug 9099;
8753 bugfix on 0.2.1.5-alpha.
8754 - Fix the manpage's description of HiddenServiceAuthorizeClient:
8755 the maximum client name length is 16, not 19. Fixes bug 11118;
8756 bugfix on 0.2.1.6-alpha.
8759 - The contrib directory has been sorted and tidied. Before, it was
8760 an unsorted dumping ground for useful and not-so-useful things.
8761 Now, it is divided based on functionality, and the items which
8762 seemed to be nonfunctional or useless have been removed. Resolves
8763 ticket 8966; based on patches from "rl1987".
8765 o Removed code and features:
8766 - Clients now reject any directory authority certificates lacking
8767 a dir-key-crosscert element. These have been included since
8768 0.2.1.9-alpha, so there's no real reason for them to be optional
8769 any longer. Completes proposal 157. Resolves ticket 10162.
8770 - Remove all code that existed to support the v2 directory system,
8771 since there are no longer any v2 directory authorities. Resolves
8773 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
8774 options, which were used for designating authorities as "Hidden
8775 service authorities". There has been no use of hidden service
8776 authorities since 0.2.2.1-alpha, when we stopped uploading or
8777 downloading v0 hidden service descriptors. Fixes bug 10881; also
8778 part of a fix for bug 10841.
8779 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
8780 and MTBF calculations, but that nobody was using. Fixes bug 11742.
8781 - The TunnelDirConns and PreferTunnelledDirConns options no longer
8782 exist; tunneled directory connections have been available since
8783 0.1.2.5-alpha, and turning them off is not a good idea. This is a
8784 brute-force fix for 10849, where "TunnelDirConns 0" would break
8786 - Remove all code for the long unused v1 directory protocol.
8787 Resolves ticket 11070.
8788 - Remove all remaining code related to version-0 hidden service
8789 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
8790 the rest of bug 10841.
8791 - Remove migration code from when we renamed the "cached-routers"
8792 file to "cached-descriptors" back in 0.2.0.8-alpha. This
8793 incidentally resolves ticket 6502 by cleaning up the related code
8794 a bit. Patch from Akshay Hebbar.
8796 o Test infrastructure:
8797 - Tor now builds each source file in two modes: a mode that avoids
8798 exposing identifiers needlessly, and another mode that exposes
8799 more identifiers for testing. This lets the compiler do better at
8800 optimizing the production code, while enabling us to take more
8801 radical measures to let the unit tests test things.
8802 - The production builds no longer include functions used only in
8803 the unit tests; all functions exposed from a module only for
8804 unit-testing are now static in production builds.
8805 - Add an --enable-coverage configuration option to make the unit
8806 tests (and a new src/or/tor-cov target) to build with gcov test
8808 - Update to the latest version of tinytest.
8809 - Improve the tinytest implementation of string operation tests so
8810 that comparisons with NULL strings no longer crash the tests; they
8811 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
8812 - New macros in test.h to simplify writing mock-functions for unit
8813 tests. Part of ticket 11507. Patch from Dana Koch.
8814 - We now have rudimentary function mocking support that our unit
8815 tests can use to test functions in isolation. Function mocking
8816 lets the tests temporarily replace a function's dependencies with
8817 stub functions, so that the tests can check the function without
8818 invoking the other functions it calls.
8821 - Complete tests for the status.c module. Resolves ticket 11507.
8822 Patch from Dana Koch.
8823 - Add more unit tests for the <circid,channel>->circuit map, and
8824 the destroy-cell-tracking code to fix bug 7912.
8825 - Unit tests for failing cases of the TAP onion handshake.
8826 - More unit tests for address-manipulation functions.
8828 o Distribution (systemd):
8829 - Include a tor.service file in contrib/dist for use with systemd.
8830 Some distributions will be able to use this file unmodified;
8831 others will need to tweak it, or write their own. Patch from Jamie
8832 Nguyen; resolves ticket 8368.
8833 - Verify configuration file via ExecStartPre in the systemd unit
8834 file. Patch from intrigeri; resolves ticket 12730.
8835 - Explicitly disable RunAsDaemon in the systemd unit file. Our
8836 current systemd unit uses "Type = simple", so systemd does not
8837 expect tor to fork. If the user has "RunAsDaemon 1" in their
8838 torrc, then things won't work as expected. This is e.g. the case
8839 on Debian (and derivatives), since there we pass "--defaults-torrc
8840 /usr/share/tor/tor-service-defaults-torrc" (that contains
8841 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
8845 Changes in version 0.2.4.25 - 2014-10-20
8846 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
8847 (even though POODLE does not affect Tor). It also works around a crash
8848 bug caused by some operating systems' response to the "POODLE" attack
8849 (which does affect Tor).
8851 o Major security fixes (also in 0.2.5.9-rc):
8852 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8853 today support TLS 1.0 or later, so we can safely turn off support
8854 for this old (and insecure) protocol. Fixes bug 13426.
8856 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
8857 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8858 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
8859 13471. This is a workaround for an OpenSSL bug.
8862 Changes in version 0.2.4.24 - 2014-09-22
8863 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
8864 connecting to hidden services, and it updates the location of one of
8865 the directory authorities.
8868 - Clients now send the correct address for their chosen rendezvous
8869 point when trying to access a hidden service. They used to send
8870 the wrong address, which would still work some of the time because
8871 they also sent the identity digest of the rendezvous point, and if
8872 the hidden service happened to try connecting to the rendezvous
8873 point from a relay that already had a connection open to it,
8874 the relay would reuse that connection. Now connections to hidden
8875 services should be more robust and faster. Also, this bug meant
8876 that clients were leaking to the hidden service whether they were
8877 on a little-endian (common) or big-endian (rare) system, which for
8878 some users might have reduced their anonymity. Fixes bug 13151;
8879 bugfix on 0.2.1.5-alpha.
8881 o Directory authority changes:
8882 - Change IP address for gabelmoo (v3 directory authority).
8884 o Minor features (geoip):
8885 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8889 Changes in version 0.2.4.23 - 2014-07-28
8890 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
8891 guard rotation, and also backports several important fixes from the
8892 Tor 0.2.5 alpha release series.
8895 - Clients now look at the "usecreatefast" consensus parameter to
8896 decide whether to use CREATE_FAST or CREATE cells for the first hop
8897 of their circuit. This approach can improve security on connections
8898 where Tor's circuit handshake is stronger than the available TLS
8899 connection security levels, but the tradeoff is more computational
8900 load on guard relays. Implements proposal 221. Resolves ticket 9386.
8901 - Make the number of entry guards configurable via a new
8902 NumEntryGuards consensus parameter, and the number of directory
8903 guards configurable via a new NumDirectoryGuards consensus
8904 parameter. Implements ticket 12688.
8907 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
8908 implementation that caused incorrect results on 32-bit
8909 implementations when certain malformed inputs were used along with
8910 a small class of private ntor keys. This bug does not currently
8911 appear to allow an attacker to learn private keys or impersonate a
8912 Tor server, but it could provide a means to distinguish 32-bit Tor
8913 implementations from 64-bit Tor implementations. Fixes bug 12694;
8914 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
8918 - Warn and drop the circuit if we receive an inbound 'relay early'
8919 cell. Those used to be normal to receive on hidden service circuits
8920 due to bug 1038, but the buggy Tor versions are long gone from
8921 the network so we can afford to resume watching for them. Resolves
8922 the rest of bug 1038; bugfix on 0.2.1.19.
8923 - Correct a confusing error message when trying to extend a circuit
8924 via the control protocol but we don't know a descriptor or
8925 microdescriptor for one of the specified relays. Fixes bug 12718;
8926 bugfix on 0.2.3.1-alpha.
8927 - Avoid an illegal read from stack when initializing the TLS
8928 module using a version of OpenSSL without all of the ciphers
8929 used by the v2 link handshake. Fixes bug 12227; bugfix on
8930 0.2.4.8-alpha. Found by "starlight".
8933 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
8937 Changes in version 0.2.4.22 - 2014-05-16
8938 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
8939 alpha release series. These include blocking all authority signing
8940 keys that may have been affected by the OpenSSL "heartbleed" bug,
8941 choosing a far more secure set of TLS ciphersuites by default, closing
8942 a couple of memory leaks that could be used to run a target relay out
8943 of RAM, and several others.
8945 o Major features (security, backport from 0.2.5.4-alpha):
8946 - Block authority signing keys that were used on authorities
8947 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
8948 don't have any evidence that these keys _were_ compromised; we're
8949 doing this to be prudent.) Resolves ticket 11464.
8951 o Major bugfixes (security, OOM):
8952 - Fix a memory leak that could occur if a microdescriptor parse
8953 fails during the tokenizing step. This bug could enable a memory
8954 exhaustion attack by directory servers. Fixes bug 11649; bugfix
8957 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
8958 - The relay ciphersuite list is now generated automatically based on
8959 uniform criteria, and includes all OpenSSL ciphersuites with
8960 acceptable strength and forward secrecy. Previously, we had left
8961 some perfectly fine ciphersuites unsupported due to omission or
8962 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
8963 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
8964 - Relays now trust themselves to have a better view than clients of
8965 which TLS ciphersuites are better than others. (Thanks to bug
8966 11513, the relay list is now well-considered, whereas the client
8967 list has been chosen mainly for anti-fingerprinting purposes.)
8968 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
8969 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
8970 AES128. Resolves ticket 11528.
8971 - Clients now try to advertise the same list of ciphersuites as
8972 Firefox 28. This change enables selection of (fast) GCM
8973 ciphersuites, disables some strange old ciphers, and stops
8974 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
8975 Resolves ticket 11438.
8977 o Minor bugfixes (configuration, security):
8978 - When running a hidden service, do not allow TunneledDirConns 0:
8979 trying to set that option together with a hidden service would
8980 otherwise prevent the hidden service from running, and also make
8981 it publish its descriptors directly over HTTP. Fixes bug 10849;
8982 bugfix on 0.2.1.1-alpha.
8984 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
8985 - Avoid sending a garbage value to the controller when a circuit is
8986 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
8988 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
8989 - Stop leaking memory when we successfully resolve a PTR record.
8990 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
8992 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
8993 - Avoid 60-second delays in the bootstrapping process when Tor is
8994 launching for a second time while using bridges. Fixes bug 9229;
8995 bugfix on 0.2.0.3-alpha.
8997 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
8998 - Give the correct URL in the warning message when trying to run a
8999 relay on an ancient version of Windows. Fixes bug 9393.
9001 o Minor bugfixes (compilation):
9002 - Fix a compilation error when compiling with --disable-curve25519.
9003 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9006 - Downgrade the warning severity for the the "md was still
9007 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9008 for trying to diagnose this bug, and the current warning in
9009 earlier versions of tor achieves nothing useful. Addresses warning
9012 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9013 - When we run out of usable circuit IDs on a channel, log only one
9014 warning for the whole channel, and describe how many circuits
9015 there were on the channel. Fixes part of ticket 11553.
9017 o Minor features (security, backport from 0.2.5.4-alpha):
9018 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9019 leave the default at 8GBytes), to better support Raspberry Pi
9020 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9022 o Documentation (backport from 0.2.5.4-alpha):
9023 - Correctly document that we search for a system torrc file before
9024 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9028 Changes in version 0.2.4.21 - 2014-02-28
9029 Tor 0.2.4.21 further improves security against potential adversaries who
9030 find breaking 1024-bit crypto doable, and backports several stability
9031 and robustness patches from the 0.2.5 branch.
9033 o Major features (client security):
9034 - When we choose a path for a 3-hop circuit, make sure it contains
9035 at least one relay that supports the NTor circuit extension
9036 handshake. Otherwise, there is a chance that we're building
9037 a circuit that's worth attacking by an adversary who finds
9038 breaking 1024-bit crypto doable, and that chance changes the game
9039 theory. Implements ticket 9777.
9042 - Do not treat streams that fail with reason
9043 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
9044 since it could also indicate an ENETUNREACH connection error. Fixes
9045 part of bug 10777; bugfix on 0.2.4.8-alpha.
9047 o Code simplification and refactoring:
9048 - Remove data structures which were introduced to implement the
9049 CellStatistics option: they are now redundant with the new timestamp
9050 field in the regular packed_cell_t data structure, which we did
9051 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
9054 - Always clear OpenSSL bignums before freeing them -- even bignums
9055 that don't contain secrets. Resolves ticket 10793. Patch by
9057 - Build without warnings under clang 3.4. (We have some macros that
9058 define static functions only some of which will get used later in
9059 the module. Starting with clang 3.4, these give a warning unless the
9060 unused attribute is set on them.) Resolves ticket 10904.
9061 - Update geoip and geoip6 files to the February 7 2014 Maxmind
9062 GeoLite2 Country database.
9065 - Set the listen() backlog limit to the largest actually supported
9066 on the system, not to the value in a header file. Fixes bug 9716;
9067 bugfix on every released Tor.
9068 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
9069 exit node as a NOROUTE error, not an INTERNAL error, since they
9070 can apparently happen when trying to connect to the wrong sort
9071 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
9072 - Fix build warnings about missing "a2x" comment when building the
9073 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
9074 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
9075 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
9076 not entirely remove it from the connection lists. Fixes bug 9602;
9077 bugfix on 0.2.4.4-alpha.
9078 - Fix a segmentation fault in our benchmark code when running with
9079 Fedora's OpenSSL package, or any other OpenSSL that provides
9080 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
9081 - Turn "circuit handshake stats since last time" log messages into a
9082 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
9084 o Documentation fixes:
9085 - Document that all but one DirPort entry must have the NoAdvertise
9086 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
9089 Changes in version 0.2.4.20 - 2013-12-22
9090 Tor 0.2.4.20 fixes potentially poor random number generation for users
9091 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
9092 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
9093 and 4) have no state file in their DataDirectory (as would happen on
9094 first start). Users who generated relay or hidden service identity
9095 keys in such a situation should discard them and generate new ones.
9097 This release also fixes a logic error that caused Tor clients to build
9098 many more preemptive circuits than they actually need.
9101 - Do not allow OpenSSL engines to replace the PRNG, even when
9102 HardwareAccel is set. The only default builtin PRNG engine uses
9103 the Intel RDRAND instruction to replace the entire PRNG, and
9104 ignores all attempts to seed it with more entropy. That's
9105 cryptographically stupid: the right response to a new alleged
9106 entropy source is never to discard all previously used entropy
9107 sources. Fixes bug 10402; works around behavior introduced in
9108 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
9110 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
9111 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
9112 - Avoid launching spurious extra circuits when a stream is pending.
9113 This fixes a bug where any circuit that _wasn't_ unusable for new
9114 streams would be treated as if it were, causing extra circuits to
9115 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
9118 - Avoid a crash bug when starting with a corrupted microdescriptor
9119 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
9120 - If we fail to dump a previously cached microdescriptor to disk, avoid
9121 freeing duplicate data later on. Fixes bug 10423; bugfix on
9122 0.2.4.13-alpha. Spotted by "bobnomnom".
9125 Changes in version 0.2.4.19 - 2013-12-11
9126 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
9127 (1986-2013). Aaron worked on diverse projects including helping to guide
9128 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
9129 transparency to the U.S government's PACER documents, and contributing
9130 design and development for Tor and Tor2Web. Aaron was one of the latest
9131 martyrs in our collective fight for civil liberties and human rights,
9132 and his death is all the more painful because he was one of us.
9134 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
9135 a new circuit handshake and link encryption that use ECC to provide
9136 better security and efficiency; makes relays better manage circuit
9137 creation requests; uses "directory guards" to reduce client enumeration
9138 risks; makes bridges collect and report statistics about the pluggable
9139 transports they support; cleans up and improves our geoip database;
9140 gets much closer to IPv6 support for clients, bridges, and relays; makes
9141 directory authorities use measured bandwidths rather than advertised
9142 ones when computing flags and thresholds; disables client-side DNS
9143 caching to reduce tracking risks; and fixes a big bug in bridge
9144 reachability testing. This release introduces two new design
9145 abstractions in the code: a new "channel" abstraction between circuits
9146 and or_connections to allow for implementing alternate relay-to-relay
9147 transports, and a new "circuitmux" abstraction storing the queue of
9148 circuits for a channel. The release also includes many stability,
9149 security, and privacy fixes.
9151 o Major features (new circuit handshake):
9152 - Tor now supports a new circuit extension handshake designed by Ian
9153 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
9154 circuit extension handshake, later called "TAP", was a bit slow
9155 (especially on the relay side), had a fragile security proof, and
9156 used weaker keys than we'd now prefer. The new circuit handshake
9157 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
9158 function, making it significantly more secure than the older
9159 handshake, and significantly faster. Tor can use one of two built-in
9160 pure-C curve25519-donna implementations by Adam Langley, or it
9161 can link against the "nacl" library for a tuned version if present.
9163 The built-in version is very fast for 64-bit systems when building
9164 with GCC. The built-in 32-bit version is still faster than the
9165 old TAP protocol, but using libnacl is better on most such hosts.
9167 Implements proposal 216; closes ticket 7202.
9169 o Major features (better link encryption):
9170 - Relays can now enable the ECDHE TLS ciphersuites when available
9171 and appropriate. These ciphersuites let us negotiate forward-secure
9172 TLS secret keys more safely and more efficiently than with our
9173 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
9174 public relays prefer the (faster) P224 group, and bridges prefer
9175 the (more common) P256 group; you can override this with the
9178 This feature requires clients running 0.2.3.17-beta or later,
9179 and requires both sides to be running OpenSSL 1.0.0 or later
9180 with ECC support. OpenSSL 1.0.1, with the compile-time option
9181 "enable-ec_nistp_64_gcc_128", is highly recommended.
9183 Implements the relay side of proposal 198; closes ticket 7200.
9185 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
9186 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
9187 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
9188 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
9189 them to solve bug 6033.)
9191 o Major features (relay performance):
9192 - Instead of limiting the number of queued onionskins (aka circuit
9193 create requests) to a fixed, hard-to-configure number, we limit
9194 the size of the queue based on how many we expect to be able to
9195 process in a given amount of time. We estimate the time it will
9196 take to process an onionskin based on average processing time
9197 of previous onionskins. Closes ticket 7291. You'll never have to
9198 configure MaxOnionsPending again.
9199 - Relays process the new "NTor" circuit-level handshake requests
9200 with higher priority than the old "TAP" circuit-level handshake
9201 requests. We still process some TAP requests to not totally starve
9202 0.2.3 clients when NTor becomes popular. A new consensus parameter
9203 "NumNTorsPerTAP" lets us tune the balance later if we need to.
9204 Implements ticket 9574.
9206 o Major features (client bootstrapping resilience):
9207 - Add a new "FallbackDir" torrc option to use when we can't use
9208 a directory mirror from the consensus (either because we lack a
9209 consensus, or because they're all down). Currently, all authorities
9210 are fallbacks by default, and there are no other default fallbacks,
9211 but that will change. This option will allow us to give clients a
9212 longer list of servers to try to get a consensus from when first
9213 connecting to the Tor network, and thereby reduce load on the
9214 directory authorities. Implements proposal 206, "Preconfigured
9215 directory sources for bootstrapping". We also removed the old
9216 "FallbackNetworkstatus" option, since we never got it working well
9217 enough to use it. Closes bug 572.
9218 - If we have no circuits open, use a relaxed timeout (the
9219 95th-percentile cutoff) until a circuit succeeds. This heuristic
9220 should allow Tor to succeed at building circuits even when the
9221 network connection drastically changes. Should help with bug 3443.
9223 o Major features (use of guards):
9224 - Support directory guards (proposal 207): when possible, clients now
9225 use their entry guards for non-anonymous directory requests. This
9226 can help prevent client enumeration. Note that this behavior only
9227 works when we have a usable consensus directory, and when options
9228 about what to download are more or less standard. In the future we
9229 should re-bootstrap from our guards, rather than re-bootstrapping
9230 from the preconfigured list of directory sources that ships with
9231 Tor. Resolves ticket 6526.
9232 - Raise the default time that a client keeps an entry guard from
9233 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
9234 2012 paper. (We would make it even longer, but we need better client
9235 load balancing first.) Also, make the guard lifetime controllable
9236 via a new GuardLifetime torrc option and a GuardLifetime consensus
9237 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9239 o Major features (bridges with pluggable transports):
9240 - Bridges now report the pluggable transports they support to the
9241 bridge authority, so it can pass the supported transports on to
9242 bridgedb and/or eventually do reachability testing. Implements
9244 - Automatically forward the TCP ports of pluggable transport
9245 proxies using tor-fw-helper if PortForwarding is enabled. Implements
9248 o Major features (geoip database):
9249 - Maxmind began labelling Tor relays as being in country "A1",
9250 which breaks by-country node selection inside Tor. Now we use a
9251 script to replace "A1" ("Anonymous Proxy") entries in our geoip
9252 file with real country codes. This script fixes about 90% of "A1"
9253 entries automatically and uses manual country code assignments to
9254 fix the remaining 10%. See src/config/README.geoip for details.
9256 - Add GeoIP database for IPv6 addresses. The new config option
9258 - Update to the October 2 2013 Maxmind GeoLite Country database.
9260 o Major features (IPv6):
9261 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
9262 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
9263 to happen. Implements ticket 5535.
9264 - All kind of relays, not just bridges, can now advertise an IPv6
9265 OR port. Implements ticket 6362.
9266 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
9267 connectivity, then set the IPv6Exit flag to 1. Also make sure your
9268 exit policy reads as you would like: the address * applies to all
9269 address families, whereas *4 is IPv4 address only, and *6 is IPv6
9270 addresses only. On the client side, you'll need to wait for enough
9271 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
9272 and use Socks5. Closes ticket 5547, implements proposal 117 as
9273 revised in proposal 208.
9274 - Bridge authorities now accept IPv6 bridge addresses and include
9275 them in network status documents. Implements ticket 5534.
9276 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
9278 o Major features (directory authorities):
9279 - Directory authorities now prefer using measured bandwidths to
9280 advertised ones when computing flags and thresholds. Resolves
9282 - Directory authorities that vote measured bandwidths about more
9283 than a threshold number of relays now treat relays with
9284 unmeasured bandwidths as having bandwidth 0 when computing their
9285 flags. Resolves ticket 8435.
9286 - Directory authorities now support a new consensus method (17)
9287 where they cap the published bandwidth of relays for which
9288 insufficient bandwidth measurements exist. Fixes part of bug 2286.
9289 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
9290 serve any v2 directory information. Now we can test disabling the
9291 old deprecated v2 directory format, and see whether doing so has
9292 any effect on network load. Begins to fix bug 6783.
9294 o Major features (build and portability):
9295 - Switch to a nonrecursive Makefile structure. Now instead of each
9296 Makefile.am invoking other Makefile.am's, there is a master
9297 Makefile.am that includes the others. This change makes our build
9298 process slightly more maintainable, and improves parallelism for
9299 building with make -j. Original patch by Stewart Smith; various
9300 fixes by Jim Meyering.
9301 - Where available, we now use automake's "silent" make rules by
9302 default, so that warnings are easier to spot. You can get the old
9303 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
9304 - Resume building correctly with MSVC and Makefile.nmake. This patch
9305 resolves numerous bugs and fixes reported by ultramage, including
9306 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
9308 o Security features:
9309 - Switch to a completely time-invariant approach for picking nodes
9310 weighted by bandwidth. Our old approach would run through the
9311 part of the loop after it had made its choice slightly slower
9312 than it ran through the part of the loop before it had made its
9313 choice. Addresses ticket 6538.
9314 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
9315 by tor2web clients allows hidden services to identify tor2web
9316 clients through their repeated selection of the same rendezvous
9317 and introduction point circuit endpoints (their guards). Resolves
9320 o Major bugfixes (relay denial of service):
9321 - When we have too much memory queued in circuits (according to a new
9322 MaxMemInCellQueues option), close the circuits that have the oldest
9323 queued cells, on the theory that those are most responsible for
9324 us running low on memory. This prevents us from running out of
9325 memory as a relay if circuits fill up faster than they can be
9326 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
9327 Tor. This bug is a further fix beyond bug 6252, whose fix was
9328 merged into 0.2.3.21-rc.
9329 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
9330 ID: these could be used to create unexpected streams and circuits
9331 which would count as "present" to some parts of Tor but "absent"
9332 to others, leading to zombie circuits and streams or to a bandwidth
9333 denial-of-service. Fixes bug 7889; bugfix on every released version
9334 of Tor. Reported by "oftc_must_be_destroyed".
9335 - Avoid a bug where our response to TLS renegotiation under certain
9336 network conditions could lead to a busy-loop, with 100% CPU
9337 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
9339 o Major bugfixes (asserts, crashes, leaks):
9340 - Prevent the get_freelists() function from running off the end of
9341 the list of freelists if it somehow gets an unrecognized
9342 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
9344 - Avoid a memory leak where we would leak a consensus body when we
9345 find that a consensus which we couldn't previously verify due to
9346 missing certificates is now verifiable. Fixes bug 8719; bugfix
9348 - If we are unable to save a microdescriptor to the journal, do not
9349 drop it from memory and then reattempt downloading it. Fixes bug
9350 9645; bugfix on 0.2.2.6-alpha.
9351 - Fix an assertion failure that would occur when disabling the
9352 ORPort setting on a running Tor process while accounting was
9353 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
9354 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
9355 when an exit connection with optimistic data succeeds immediately
9356 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
9358 - Fix a memory leak that would occur whenever a configuration
9359 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
9361 o Major bugfixes (relay rate limiting):
9362 - When a TLS write is partially successful but incomplete, remember
9363 that the flushed part has been flushed, and notice that bytes were
9364 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
9365 bugfix on Tor 0.1.0.5-rc.
9366 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
9367 to 1GB/1GB. The previous defaults were intended to be "basically
9368 infinite", but it turns out they're now limiting our 100mbit+
9369 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
9370 last time we raised it).
9371 - No longer stop reading or writing on cpuworker connections when
9372 our rate limiting buckets go empty. Now we should handle circuit
9373 handshake requests more promptly. Resolves bug 9731.
9375 o Major bugfixes (client-side privacy):
9376 - When we mark a circuit as unusable for new circuits, have it
9377 continue to be unusable for new circuits even if MaxCircuitDirtiness
9378 is increased too much at the wrong time, or the system clock jumps
9379 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
9380 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
9381 which have resolved to internal addresses") is set, apply that
9382 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
9383 - When an exit relay rejects a stream with reason "exit policy", but
9384 we only know an exit policy summary (e.g. from the microdesc
9385 consensus) for it, do not mark the relay as useless for all exiting.
9386 Instead, mark just the circuit as unsuitable for that particular
9387 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
9389 o Major bugfixes (stream isolation):
9390 - Allow applications to get proper stream isolation with
9391 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
9392 username/password authentication also offer "no authentication". Tor
9393 had previously preferred "no authentication", so the applications
9394 never actually sent Tor their auth details. Now Tor selects
9395 username/password authentication if it's offered. You can disable
9396 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
9397 bug 8117; bugfix on 0.2.3.3-alpha.
9398 - Follow the socks5 protocol when offering username/password
9399 authentication. The fix for bug 8117 exposed this bug, and it
9400 turns out real-world applications like Pidgin do care. Bugfix on
9401 0.2.3.2-alpha; fixes bug 8879.
9403 o Major bugfixes (client circuit building):
9404 - Alter circuit build timeout measurement to start at the point
9405 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
9406 initialization). This should make our timeout measurements more
9407 uniform. Previously, we were sometimes including ORconn setup time
9408 in our circuit build time measurements. Should resolve bug 3443.
9409 - If the circuit build timeout logic is disabled (via the consensus,
9410 or because we are an authority), then don't build testing circuits.
9411 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
9413 o Major bugfixes (client-side DNS):
9414 - Turn off the client-side DNS cache by default. Updating and using
9415 the DNS cache is now configurable on a per-client-port
9416 level. SOCKSPort, DNSPort, etc lines may now contain
9417 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
9418 cache these types of DNS answers when we receive them from an
9419 exit node in response to an application request on this port, and
9420 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
9421 cached DNS answers of these types, we shouldn't use them. It's
9422 potentially risky to use cached DNS answers at the client, since
9423 doing so can indicate to one exit what answers we've gotten
9424 for DNS lookups in the past. With IPv6, this becomes especially
9425 problematic. Using cached DNS answers for requests on the same
9426 circuit would present less linkability risk, since all traffic
9427 on a circuit is already linkable, but it would also provide
9428 little performance benefit: the exit node caches DNS replies
9429 too. Implements a simplified version of Proposal 205. Implements
9432 o Major bugfixes (hidden service privacy):
9433 - Limit hidden service descriptors to at most ten introduction
9434 points, to slow one kind of guard enumeration. Fixes bug 9002;
9435 bugfix on 0.1.1.11-alpha.
9437 o Major bugfixes (directory fetching):
9438 - If the time to download the next old-style networkstatus is in
9439 the future, do not decline to consider whether to download the
9440 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
9442 - We used to always request authority certificates by identity digest,
9443 meaning we'd get the newest one even when we wanted one with a
9444 different signing key. Then we would complain about being given
9445 a certificate we already had, and never get the one we really
9446 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
9447 resource to request the one we want. Fixes bug 5595; bugfix on
9450 o Major bugfixes (bridge reachability):
9451 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
9452 previously they did not, which prevented them from receiving
9453 successful connections from relays for self-test or bandwidth
9454 testing. Also, when a relay is extending a circuit to a bridge,
9455 it needs to send a NETINFO cell, even when the bridge hasn't sent
9456 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
9458 o Major bugfixes (control interface):
9459 - When receiving a new configuration file via the control port's
9460 LOADCONF command, do not treat the defaults file as absent.
9461 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
9463 o Major bugfixes (directory authorities):
9464 - Stop marking every relay as having been down for one hour every
9465 time we restart a directory authority. These artificial downtimes
9466 were messing with our Stable and Guard flag calculations. Fixes
9467 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
9468 - When computing directory thresholds, ignore any rejected-as-sybil
9469 nodes during the computation so that they can't influence Fast,
9470 Guard, etc. (We should have done this for proposal 109.) Fixes
9472 - When marking a node as a likely sybil, reset its uptime metrics
9473 to zero, so that it cannot time towards getting marked as Guard,
9474 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
9476 - Fix a bug in the voting algorithm that could yield incorrect results
9477 when a non-naming authority declared too many flags. Fixes bug 9200;
9478 bugfix on 0.2.0.3-alpha.
9480 o Internal abstraction features:
9481 - Introduce new channel_t abstraction between circuits and
9482 or_connection_t to allow for implementing alternate OR-to-OR
9483 transports. A channel_t is an abstract object which can either be a
9484 cell-bearing channel, which is responsible for authenticating and
9485 handshaking with the remote OR and transmitting cells to and from
9486 it, or a listening channel, which spawns new cell-bearing channels
9487 at the request of remote ORs. Implements part of ticket 6465.
9488 - Make a channel_tls_t subclass of channel_t, adapting it to the
9489 existing or_connection_t code. The V2/V3 protocol handshaking
9490 code which formerly resided in command.c has been moved below the
9491 channel_t abstraction layer and may be found in channeltls.c now.
9492 Implements the rest of ticket 6465.
9493 - Introduce new circuitmux_t storing the queue of circuits for
9494 a channel; this encapsulates and abstracts the queue logic and
9495 circuit selection policy, and allows the latter to be overridden
9496 easily by switching out a policy object. The existing EWMA behavior
9497 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
9499 o New build requirements:
9500 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
9501 strongly recommended.
9502 - Tor maintainers now require Automake version 1.9 or later to build
9503 Tor from the Git repository. (Automake is not required when building
9504 from a source distribution.)
9506 o Minor features (protocol):
9507 - No longer include the "opt" prefix when generating routerinfos
9508 or v2 directories: it has been needless since Tor 0.1.2. Closes
9510 - Reject EXTEND cells sent to nonexistent streams. According to the
9511 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
9512 we were only checking for stream IDs that were currently in use.
9513 Found while hunting for more instances of bug 6271. Bugfix on
9514 0.0.2pre8, which introduced incremental circuit construction.
9515 - Tor relays and clients now support a better CREATE/EXTEND cell
9516 format, allowing the sender to specify multiple address, identity,
9517 and handshake types. Implements Robert Ransom's proposal 200;
9519 - Reject as invalid most directory objects containing a NUL.
9520 Belt-and-suspender fix for bug 8037.
9522 o Minor features (security):
9523 - Clear keys and key-derived material left on the stack in
9524 rendservice.c and rendclient.c. Check return value of
9525 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
9526 These fixes should make us more forward-secure against cold-boot
9527 attacks and the like. Fixes bug 2385.
9528 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
9529 Irix's random() only return 15 bits; Solaris's random() returns more
9530 bits but its RAND_MAX says it only returns 15, and so on. Motivated
9531 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
9533 o Minor features (control protocol):
9534 - Add a "GETINFO signal/names" control port command. Implements
9536 - Provide default values for all options via "GETINFO config/defaults".
9537 Implements ticket 4971.
9538 - Allow an optional $ before the node identity digest in the
9539 controller command GETINFO ns/id/<identity>, for consistency with
9540 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
9541 - Add CACHED keyword to ADDRMAP events in the control protocol
9542 to indicate whether a DNS result will be cached or not. Resolves
9544 - Generate bootstrapping status update events correctly when fetching
9545 microdescriptors. Fixes bug 9927.
9547 o Minor features (path selection):
9548 - When deciding whether we have enough descriptors to build circuits,
9549 instead of looking at raw relay counts, look at which fraction
9550 of (bandwidth-weighted) paths we're able to build. This approach
9551 keeps clients from building circuits if their paths are likely to
9552 stand out statistically. The default fraction of paths needed is
9553 taken from the consensus directory; you can override it with the
9554 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
9555 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
9556 and we have GeoIP information, also exclude all nodes with unknown
9557 countries "??" and "A1". This behavior is controlled by the
9558 new GeoIPExcludeUnknown option: you can make such nodes always
9559 excluded with "GeoIPExcludeUnknown 1", and disable the feature
9560 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
9561 gets you the default behavior. Implements feature 7706.
9563 o Minor features (hidden services):
9564 - Improve circuit build timeout handling for hidden services.
9565 In particular: adjust build timeouts more accurately depending
9566 upon the number of hop-RTTs that a particular circuit type
9567 undergoes. Additionally, launch intro circuits in parallel
9568 if they timeout, and take the first one to reply as valid.
9569 - The Tor client now ignores sub-domain components of a .onion
9570 address. This change makes HTTP "virtual" hosting
9571 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
9572 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
9573 hosted on the same hidden service. Implements proposal 204.
9574 - Enable Tor to read configuration, state, and key information from
9575 a FIFO. Previously Tor would only read from files with a positive
9576 stat.st_size. Code from meejah; fixes bug 6044.
9578 o Minor features (clients):
9579 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
9580 microdescriptor-related dir requests, and only fall back to normal
9581 descriptors if none of their bridges can handle microdescriptors
9582 (as opposed to the fix in ticket 4013, which caused them to fall
9583 back to normal descriptors if *any* of their bridges preferred
9584 them). Resolves ticket 4994.
9585 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
9586 TCP ports to forward. In the past it only accepted two ports:
9587 the ORPort and the DirPort.
9589 o Minor features (protecting client timestamps):
9590 - Clients no longer send timestamps in their NETINFO cells. These were
9591 not used for anything, and they provided one small way for clients
9592 to be distinguished from each other as they moved from network to
9593 network or behind NAT. Implements part of proposal 222.
9594 - Clients now round timestamps in INTRODUCE cells down to the nearest
9595 10 minutes. If a new Support022HiddenServices option is set to 0, or
9596 if it's set to "auto" and the feature is disabled in the consensus,
9597 the timestamp is sent as 0 instead. Implements part of proposal 222.
9598 - Stop sending timestamps in AUTHENTICATE cells. This is not such
9599 a big deal from a security point of view, but it achieves no actual
9600 good purpose, and isn't needed. Implements part of proposal 222.
9601 - Reduce down accuracy of timestamps in hidden service descriptors.
9602 Implements part of proposal 222.
9604 o Minor features (bridges):
9605 - Make bridge relays check once a minute for whether their IP
9606 address has changed, rather than only every 15 minutes. Resolves
9608 - Bridge statistics now count bridge clients connecting over IPv6:
9609 bridge statistics files now list "bridge-ip-versions" and
9610 extra-info documents list "geoip6-db-digest". The control protocol
9611 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
9612 implementation by "shkoo", addressing ticket 5055.
9613 - Add a new torrc option "ServerTransportListenAddr" to let bridge
9614 operators select the address where their pluggable transports will
9615 listen for connections. Resolves ticket 7013.
9616 - Randomize the lifetime of our SSL link certificate, so censors can't
9617 use the static value for filtering Tor flows. Resolves ticket 8443;
9618 related to ticket 4014 which was included in 0.2.2.33.
9620 o Minor features (relays):
9621 - Option OutboundBindAddress can be specified multiple times and
9622 accepts IPv6 addresses. Resolves ticket 6876.
9624 o Minor features (IPv6, client side):
9625 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
9626 prefer to hand out virtual IPv6 addresses, since there are more of
9627 them and we can't run out. To override this behavior and make IPv4
9628 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
9629 or DNSPort you're using for resolving. Implements ticket 7571.
9630 - AutomapHostsOnResolve responses are now randomized, to avoid
9631 annoying situations where Tor is restarted and applications
9632 connect to the wrong addresses.
9633 - Never try more than 1000 times to pick a new virtual address when
9634 AutomapHostsOnResolve is set. That's good enough so long as we
9635 aren't close to handing out our entire virtual address space;
9636 if you're getting there, it's best to switch to IPv6 virtual
9639 o Minor features (IPv6, relay/authority side):
9640 - New config option "AuthDirHasIPv6Connectivity 1" that directory
9641 authorities should set if they have IPv6 connectivity and want to
9642 do reachability tests for IPv6 relays. Implements feature 5974.
9643 - A relay with an IPv6 OR port now sends that address in NETINFO
9644 cells (in addition to its other address). Implements ticket 6364.
9646 o Minor features (directory authorities):
9647 - Directory authorities no long accept descriptors for any version of
9648 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
9649 These versions are insecure, unsupported, or both. Implements
9651 - When directory authorities are computing thresholds for flags,
9652 never let the threshold for the Fast flag fall below 4096
9653 bytes. Also, do not consider nodes with extremely low bandwidths
9654 when deciding thresholds for various directory flags. This change
9655 should raise our threshold for Fast relays, possibly in turn
9656 improving overall network performance; see ticket 1854. Resolves
9658 - Directory authorities now include inside each vote a statement of
9659 the performance thresholds they used when assigning flags.
9660 Implements ticket 8151.
9661 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
9662 in directory authority votes to describe whether they have enough
9663 measured bandwidths to ignore advertised (relay descriptor)
9664 bandwidth claims. Resolves ticket 8711.
9666 o Minor features (path bias detection):
9667 - Path Use Bias: Perform separate accounting for successful circuit
9668 use. Keep separate statistics on stream attempt rates versus stream
9669 success rates for each guard. Provide configurable thresholds to
9670 determine when to emit log messages or disable use of guards that
9671 fail too many stream attempts. Resolves ticket 7802.
9672 - Create three levels of Path Bias log messages, as opposed to just
9673 two. These are configurable via consensus as well as via the torrc
9674 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
9675 The default values are 0.70, 0.50, and 0.30 respectively.
9676 - Separate the log message levels from the decision to drop guards,
9677 which also is available via torrc option PathBiasDropGuards.
9678 PathBiasDropGuards still defaults to 0 (off).
9679 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
9680 in combination with PathBiasExtremeRate.
9681 - Increase the default values for PathBiasScaleThreshold and
9682 PathBiasCircThreshold from (200, 20) to (300, 150).
9683 - Add in circuit usage accounting to path bias. If we try to use a
9684 built circuit but fail for any reason, it counts as path bias.
9685 Certain classes of circuits where the adversary gets to pick your
9686 destination node are exempt from this accounting. Usage accounting
9687 can be specifically disabled via consensus parameter or torrc.
9688 - Convert all internal path bias state to double-precision floating
9689 point, to avoid roundoff error and other issues.
9690 - Only record path bias information for circuits that have completed
9691 *two* hops. Assuming end-to-end tagging is the attack vector, this
9692 makes us more resilient to ambient circuit failure without any
9693 detection capability loss.
9695 o Minor features (build):
9696 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
9697 dhill. Resolves ticket 6982.
9698 - Compile on win64 using mingw64. Fixes bug 7260; patches from
9700 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
9701 separate error codes; or at least, don't break for that reason.
9702 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
9704 o Build improvements (autotools):
9705 - Warn if building on a platform with an unsigned time_t: there
9706 are too many places where Tor currently assumes that time_t can
9707 hold negative values. We'd like to fix them all, but probably
9709 - Do not report status verbosely from autogen.sh unless the -v flag
9710 is specified. Fixes issue 4664. Patch from Onizuka.
9711 - Detect and reject attempts to build Tor with threading support
9712 when OpenSSL has been compiled without threading support.
9714 - Try to detect if we are ever building on a platform where
9715 memset(...,0,...) does not set the value of a double to 0.0. Such
9716 platforms are permitted by the C standard, though in practice
9717 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
9718 currently support them, but it's better to detect them and fail
9719 than to perform erroneously.
9720 - We no longer warn so much when generating manpages from their
9722 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
9723 the signs of types during autoconf. This is better than our old
9724 approach, which didn't work when cross-compiling.
9726 o Minor features (log messages, warnings):
9727 - Detect when we're running with a version of OpenSSL other than the
9728 one we compiled with. This conflict has occasionally given people
9729 hard-to-track-down errors.
9730 - Warn users who run hidden services on a Tor client with
9731 UseEntryGuards disabled that their hidden services will be
9732 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
9733 attack which motivated Tor to support entry guards in the first
9734 place). Resolves ticket 6889.
9735 - Warn when we are binding low ports when hibernation is enabled;
9736 previously we had warned when we were _advertising_ low ports with
9737 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
9738 - Issue a warning when running with the bufferevents backend enabled.
9739 It's still not stable, and people should know that they're likely
9740 to hit unexpected problems. Closes ticket 9147.
9742 o Minor features (log messages, notices):
9743 - Refactor resolve_my_address() so it returns the method by which we
9744 decided our public IP address (explicitly configured, resolved from
9745 explicit hostname, guessed from interfaces, learned by gethostname).
9746 Now we can provide more helpful log messages when a relay guesses
9747 its IP address incorrectly (e.g. due to unexpected lines in
9748 /etc/hosts). Resolves ticket 2267.
9749 - Track how many "TAP" and "NTor" circuit handshake requests we get,
9750 and how many we complete, and log it every hour to help relay
9751 operators follow trends in network load. Addresses ticket 9658.
9753 o Minor features (log messages, diagnostics):
9754 - If we fail to free a microdescriptor because of bug 7164, log
9755 the filename and line number from which we tried to free it.
9756 - We compute the overhead from passing onionskins back and forth to
9757 cpuworkers, and report it when dumping statistics in response to
9758 SIGUSR1. Supports ticket 7291.
9759 - Add another diagnostic to the heartbeat message: track and log
9760 overhead that TLS is adding to the data we write. If this is
9761 high, we are sending too little data to SSL_write at a time.
9762 Diagnostic for bug 7707.
9763 - Log packaged cell fullness as part of the heartbeat message.
9764 Diagnosis to try to determine the extent of bug 7743.
9765 - Add more detail to a log message about relaxed timeouts, to help
9767 - When learning a fingerprint for a bridge, log its corresponding
9768 transport type. Implements ticket 7896.
9769 - Warn more aggressively when flushing microdescriptors to a
9770 microdescriptor cache fails, in an attempt to mitigate bug 8031,
9771 or at least make it more diagnosable.
9772 - Improve the log message when "Bug/attack: unexpected sendme cell
9773 from client" occurs, to help us track bug 8093.
9774 - Improve debugging output to help track down bug 8185 ("Bug:
9775 outgoing relay cell has n_chan==NULL. Dropping.")
9777 o Minor features (log messages, quieter bootstrapping):
9778 - Log fewer lines at level "notice" about our OpenSSL and Libevent
9779 versions and capabilities when everything is going right. Resolves
9780 part of ticket 6736.
9781 - Omit the first heartbeat log message, because it never has anything
9782 useful to say, and it clutters up the bootstrapping messages.
9783 Resolves ticket 6758.
9784 - Don't log about reloading the microdescriptor cache at startup. Our
9785 bootstrap warnings are supposed to tell the user when there's a
9786 problem, and our bootstrap notices say when there isn't. Resolves
9787 ticket 6759; bugfix on 0.2.2.6-alpha.
9788 - Don't log "I learned some more directory information" when we're
9789 reading cached directory information. Reserve it for when new
9790 directory information arrives in response to a fetch. Resolves
9792 - Don't complain about bootstrapping problems while hibernating.
9793 These complaints reflect a general code problem, but not one
9794 with any problematic effects (no connections are actually
9795 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
9797 o Minor features (testing):
9798 - In our testsuite, create temporary directories with a bit more
9799 entropy in their name to make name collisions less likely. Fixes
9801 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
9802 (P-256) Diffie-Hellman handshakes to src/or/bench.
9803 - Add benchmark functions to test onion handshake performance.
9806 - The DirServer option is now DirAuthority, for consistency with
9807 current naming patterns. You can still use the old DirServer form.
9809 o Minor bugfixes (protocol):
9810 - Fix the handling of a TRUNCATE cell when it arrives while the
9811 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
9812 - When a Tor client gets a "truncated" relay cell, the first byte of
9813 its payload specifies why the circuit was truncated. We were
9814 ignoring this 'reason' byte when tearing down the circuit, resulting
9815 in the controller not being told why the circuit closed. Now we
9816 pass the reason from the truncated cell to the controller. Bugfix
9817 on 0.1.2.3-alpha; fixes bug 7039.
9818 - Fix a misframing issue when reading the version numbers in a
9819 VERSIONS cell. Previously we would recognize [00 01 00 02] as
9820 'version 1, version 2, and version 0x100', when it should have
9821 only included versions 1 and 2. Fixes bug 8059; bugfix on
9822 0.2.0.10-alpha. Reported pseudonymously.
9823 - Make the format and order of STREAM events for DNS lookups
9824 consistent among the various ways to launch DNS lookups. Fixes
9825 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
9827 o Minor bugfixes (syscalls and disk interaction):
9828 - Always check the return values of functions fcntl() and
9829 setsockopt(). We don't believe these are ever actually failing in
9830 practice, but better safe than sorry. Also, checking these return
9831 values should please analysis tools like Coverity. Patch from
9832 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
9833 - Avoid double-closing the listener socket in our socketpair()
9834 replacement (used on Windows) in the case where the addresses on
9835 our opened sockets don't match what we expected. Fixes bug 9400;
9836 bugfix on 0.0.2pre7. Found by Coverity.
9837 - Correctly store microdescriptors and extrainfo descriptors that
9838 include an internal NUL byte. Fixes bug 8037; bugfix on
9839 0.2.0.1-alpha. Bug reported by "cypherpunks".
9840 - If for some reason we fail to write a microdescriptor while
9841 rebuilding the cache, do not let the annotations from that
9842 microdescriptor linger in the cache file, and do not let the
9843 microdescriptor stay recorded as present in its old location.
9844 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
9845 - Use direct writes rather than stdio when building microdescriptor
9846 caches, in an attempt to mitigate bug 8031, or at least make it
9849 o Minor fixes (config options):
9850 - Warn and fail if a server is configured not to advertise any
9851 ORPorts at all. (We need *something* to put in our descriptor,
9852 or we just won't work.)
9853 - Behave correctly when the user disables LearnCircuitBuildTimeout
9854 but doesn't tell us what they would like the timeout to be. Fixes
9855 bug 6304; bugfix on 0.2.2.14-alpha.
9856 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
9857 to start with a triple-underscore so the controller won't touch it.
9858 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
9859 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
9860 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
9861 - When autodetecting the number of CPUs, use the number of available
9862 CPUs in preference to the number of configured CPUs. Inform the
9863 user if this reduces the number of available CPUs. Fixes bug 8002;
9864 bugfix on 0.2.3.1-alpha.
9865 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
9866 - Make it an error when you set EntryNodes but disable UseGuardNodes,
9867 since it will (surprisingly to some users) ignore EntryNodes. Fixes
9868 bug 8180; bugfix on 0.2.3.11-alpha.
9869 - Avoid overflows when the user sets MaxCircuitDirtiness to a
9870 ridiculously high value, by imposing a (ridiculously high) 30-day
9871 maximum on MaxCircuitDirtiness.
9873 o Minor bugfixes (control protocol):
9874 - Stop sending a stray "(null)" in some cases for the server status
9875 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
9877 - The ADDRMAP command can no longer generate an ill-formed error
9878 code on a failed MAPADDRESS. It now says "internal" rather than
9879 an English sentence fragment with spaces in the middle. Bugfix on
9882 o Minor bugfixes (clients / edges):
9883 - When we receive a RELAY_END cell with the reason DONE, or with no
9884 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
9885 status as "connection refused". Previously we reported these cases
9886 as success but then immediately closed the connection. Fixes bug
9887 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
9888 - If the guard we choose first doesn't answer, we would try the
9889 second guard, but once we connected to the second guard we would
9890 abandon it and retry the first one, slowing down bootstrapping.
9891 The fix is to treat all our initially chosen guards as acceptable
9892 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
9893 - When choosing which stream on a formerly stalled circuit to wake
9894 first, make better use of the platform's weak RNG. Previously,
9895 we had been using the % ("modulo") operator to try to generate a
9896 1/N chance of picking each stream, but this behaves badly with
9897 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
9900 o Minor bugfixes (path bias detection):
9901 - If the state file's path bias counts are invalid (presumably from a
9902 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
9903 additional checks and log messages to the scaling of Path Bias
9904 counts, in case there still are remaining issues with scaling.
9905 Should help resolve bug 8235.
9906 - Prevent rounding error in path bias counts when scaling
9907 them down, and use the correct scale factor default. Also demote
9908 some path bias related log messages down a level and make others
9909 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
9910 - Remove a source of rounding error during path bias count scaling;
9911 don't count cannibalized circuits as used for path bias until we
9912 actually try to use them; and fix a circuit_package_relay_cell()
9913 warning message about n_chan==NULL. Fixes bug 7802.
9914 - Paste the description for PathBias parameters from the man
9915 page into or.h, so the code documents them too. Fixes bug 7982;
9916 bugfix on 0.2.3.17-beta.
9918 o Minor bugfixes (relays):
9919 - Stop trying to resolve our hostname so often (e.g. every time we
9920 think about doing a directory fetch). Now we reuse the cached
9921 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
9922 and 2410 (bugfix on 0.1.2.2-alpha).
9923 - When examining the list of network interfaces to find our address,
9924 do not consider non-running or disabled network interfaces. Fixes
9925 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
9927 o Minor bugfixes (blocking resistance):
9928 - Only disable TLS session ticket support when running as a TLS
9929 server. Now clients will blend better with regular Firefox
9930 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
9932 o Minor bugfixes (IPv6):
9933 - Use square brackets around IPv6 addresses in numerous places
9934 that needed them, including log messages, HTTPS CONNECT proxy
9935 requests, TransportProxy statefile entries, and pluggable transport
9936 extra-info lines. Fixes bug 7011; patch by David Fifield.
9938 o Minor bugfixes (directory authorities):
9939 - Reject consensus votes with more than 64 known-flags. We aren't even
9940 close to that limit yet, and our code doesn't handle it correctly.
9941 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
9942 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
9943 bugfix on 0.2.0.3-alpha.
9945 o Minor bugfixes (memory leaks):
9946 - Avoid leaking memory if we fail to compute a consensus signature
9947 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
9948 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
9949 on 0.2.1.1-alpha; fixes bug 7816.
9950 - Fix a memory leak during safe-cookie controller authentication.
9951 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
9952 - Free some more still-in-use memory at exit, to make hunting for
9953 memory leaks easier. Resolves bug 7029.
9955 o Minor bugfixes (code correctness):
9956 - Increase the width of the field used to remember a connection's
9957 link protocol version to two bytes. Harmless for now, since the
9958 only currently recognized versions are one byte long. Reported
9959 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
9960 - Fix a crash when debugging unit tests on Windows: deallocate a
9961 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
9962 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
9963 - When detecting the largest possible file descriptor (in order to
9964 close all file descriptors when launching a new program), actually
9965 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
9966 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
9968 - Avoid a crash if we fail to generate an extrainfo descriptor.
9969 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
9971 - Avoid an off-by-one error when checking buffer boundaries when
9972 formatting the exit status of a pluggable transport helper.
9973 This is probably not an exploitable bug, but better safe than
9974 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
9976 - Get rid of a couple of harmless clang warnings, where we compared
9977 enums to ints. These warnings are newly introduced in clang 3.2.
9979 o Minor bugfixes (code cleanliness):
9980 - Avoid use of reserved identifiers in our C code. The C standard
9981 doesn't like us declaring anything that starts with an
9982 underscore, so let's knock it off before we get in trouble. Fix
9983 for bug 1031; bugfix on the first Tor commit.
9984 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
9985 with large values. This situation was untriggered, but nevertheless
9986 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
9987 - Fix an impossible buffer overrun in the AES unit tests. Fixes
9988 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
9989 - Fix handling of rendezvous client authorization types over 8.
9990 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
9991 - Remove a couple of extraneous semicolons that were upsetting the
9992 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
9993 bugfix on 0.2.2.1-alpha.
9994 - When complaining about a client port on a public address, log
9995 which address we're complaining about. Fixes bug 4020; bugfix on
9996 0.2.3.3-alpha. Patch by Tom Fitzhenry.
9998 o Minor bugfixes (log messages, warnings):
9999 - If we encounter a write failure on a SOCKS connection before we
10000 finish our SOCKS handshake, don't warn that we closed the
10001 connection before we could send a SOCKS reply. Fixes bug 8427;
10002 bugfix on 0.1.0.1-rc.
10003 - Fix a directory authority warn caused when we have a large amount
10004 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
10005 - Downgrade "Failed to hand off onionskin" messages to "debug"
10006 severity, since they're typically redundant with the "Your computer
10007 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
10008 - Avoid spurious warnings when configuring multiple client ports of
10009 which only some are nonlocal. Previously, we had claimed that some
10010 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
10013 o Minor bugfixes (log messages, other):
10014 - Fix log messages and comments to avoid saying "GMT" when we mean
10015 "UTC". Fixes bug 6113.
10016 - When rejecting a configuration because we were unable to parse a
10017 quoted string, log an actual error message. Fixes bug 7950; bugfix
10019 - Correctly recognize that [::1] is a loopback address. Fixes
10020 bug 8377; bugfix on 0.2.1.3-alpha.
10021 - Don't log inappropriate heartbeat messages when hibernating: a
10022 hibernating node is _expected_ to drop out of the consensus,
10023 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
10024 bugfix on 0.2.3.1-alpha.
10025 - Eliminate several instances where we use "Nickname=ID" to refer to
10026 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
10027 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
10030 o Minor bugfixes (build):
10031 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
10032 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
10033 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
10035 o Documentation fixes:
10036 - Make the torify manpage no longer refer to tsocks; torify hasn't
10037 supported tsocks since 0.2.3.14-alpha.
10038 - Make the tor manpage no longer reference tsocks.
10039 - Fix the GeoIPExcludeUnknown documentation to refer to
10040 ExcludeExitNodes rather than the currently nonexistent
10041 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
10042 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
10044 - Say "KBytes" rather than "KB" in the man page (for various values
10045 of K), to further reduce confusion about whether Tor counts in
10046 units of memory or fractions of units of memory. Resolves ticket 7054.
10047 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
10048 names match. Fixes bug 7768.
10049 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
10050 message is logged at notice, not at info.
10051 - Clarify the usage and risks of setting the ContactInfo torrc line
10052 for your relay or bridge. Resolves ticket 9854.
10053 - Add anchors to the manpage so we can link to the html version of
10054 the documentation for specific options. Resolves ticket 9866.
10055 - Replace remaining references to DirServer in man page and
10056 log entries. Resolves ticket 10124.
10058 o Removed features:
10059 - Stop exporting estimates of v2 and v3 directory traffic shares
10060 in extrainfo documents. They were unneeded and sometimes inaccurate.
10061 Also stop exporting any v2 directory request statistics. Resolves
10063 - Drop support for detecting and warning about versions of Libevent
10064 before 1.3e. Nothing reasonable ships with them any longer; warning
10065 the user about them shouldn't be needed. Resolves ticket 6826.
10066 - Now that all versions before 0.2.2.x are disallowed, we no longer
10067 need to work around their missing features. Remove a bunch of
10068 compatibility code.
10071 - The tor-tsocks.conf is no longer distributed or installed. We
10072 recommend that tsocks users use torsocks instead. Resolves
10074 - Remove some of the older contents of doc/ as obsolete; move others
10075 to torspec.git. Fixes bug 8965.
10077 o Code simplification:
10078 - Avoid using character buffers when constructing most directory
10079 objects: this approach was unwieldy and error-prone. Instead,
10080 build smartlists of strings, and concatenate them when done.
10081 - Rename "isin" functions to "contains", for grammar. Resolves
10083 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
10084 with the natural logarithm function from the system libm. Resolves
10086 - Start using OpenBSD's implementation of queue.h, so that we don't
10087 need to hand-roll our own pointer and list structures whenever we
10088 need them. (We can't rely on a sys/queue.h, since some operating
10089 systems don't have them, and the ones that do have them don't all
10090 present the same extensions.)
10091 - Start using OpenBSD's implementation of queue.h (originally by
10093 - Enhance our internal sscanf replacement so that we can eliminate
10094 the last remaining uses of the system sscanf. (Though those uses
10095 of sscanf were safe, sscanf itself is generally error prone, so
10096 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
10098 - Replace all calls to snprintf() outside of src/ext with
10099 tor_snprintf(). Also remove the #define to replace snprintf with
10100 _snprintf on Windows; they have different semantics, and all of
10101 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
10104 - Add a wrapper function for the common "log a message with a
10106 - Split the onion.c file into separate modules for the onion queue
10107 and the different handshakes it supports.
10108 - Move the client-side address-map/virtual-address/DNS-cache code
10109 out of connection_edge.c into a new addressmap.c module.
10110 - Move the entry node code from circuitbuild.c to its own file.
10111 - Move the circuit build timeout tracking code from circuitbuild.c
10113 - Source files taken from other packages now reside in src/ext;
10114 previously they were scattered around the rest of Tor.
10115 - Move the generic "config" code into a new file, and have "config.c"
10116 hold only torrc- and state-related code. Resolves ticket 6823.
10117 - Move the core of our "choose a weighted element at random" logic
10118 into its own function, and give it unit tests. Now the logic is
10119 testable, and a little less fragile too.
10120 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
10121 - Move last_reachable and testing_since from routerinfo_t to node_t.
10122 Implements ticket 5529.
10123 - Add replaycache_t structure, functions and unit tests, then refactor
10124 rend_service_introduce() to be more clear to read, improve, debug,
10125 and test. Resolves bug 6177.
10128 - Remove some now-needless code that tried to aggressively flush
10129 OR connections as data was added to them. Since 0.2.0.1-alpha, our
10130 cell queue logic has saved us from the failure mode that this code
10131 was supposed to prevent. Removing this code will limit the number
10132 of baroque control flow paths through Tor's network logic. Reported
10133 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
10134 - Remove unused code for parsing v1 directories and "running routers"
10135 documents. Fixes bug 6887.
10136 - Remove the marshalling/unmarshalling code for sending requests to
10137 cpuworkers over a socket, and instead just send structs. The
10138 recipient will always be the same Tor binary as the sender, so
10139 any encoding is overkill.
10140 - Remove the testing_since field of node_t, which hasn't been used
10141 for anything since 0.2.0.9-alpha.
10142 - Finally remove support for malloc_good_size and malloc_usable_size.
10143 We had hoped that these functions would let us eke a little more
10144 memory out of our malloc implementation. Unfortunately, the only
10145 implementations that provided these functions are also ones that
10146 are already efficient about not overallocation: they never got us
10147 more than 7 or so bytes per allocation. Removing them saves us a
10148 little code complexity and a nontrivial amount of build complexity.
10151 Changes in version 0.2.3.25 - 2012-11-19
10152 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
10153 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
10154 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
10155 programmer, and friend. Unstinting in his dedication to the cause of
10156 freedom, he inspired and helped many of us as we began our work on
10157 anonymity, and inspires us still. Please honor his memory by writing
10158 software to protect people's freedoms, and by helping others to do so.
10160 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
10161 significantly reduced directory overhead (via microdescriptors),
10162 enormous crypto performance improvements for fast relays on new
10163 enough hardware, a new v3 TLS handshake protocol that can better
10164 resist fingerprinting, support for protocol obfuscation plugins (aka
10165 pluggable transports), better scalability for hidden services, IPv6
10166 support for bridges, performance improvements like allowing clients
10167 to skip the first round-trip on the circuit ("optimistic data") and
10168 refilling token buckets more often, a new "stream isolation" design
10169 to isolate different applications on different circuits, and many
10170 stability, security, and privacy fixes.
10172 Major features (v3 directory protocol):
10173 - Clients now use microdescriptors instead of regular descriptors
10174 to build circuits. Microdescriptors are authority-generated
10175 summaries of regular descriptors' contents, designed to change very
10176 rarely (see proposal 158 for details). This feature is designed
10177 to save bandwidth, especially for clients on slow internet
10178 connections. Use "UseMicrodescriptors 0" to disable it.
10179 - Caches now download, cache, and serve microdescriptors, as well
10180 as multiple "flavors" of the consensus, including a flavor that
10181 describes microdescriptors.
10183 o Major features (build hardening):
10184 - Enable gcc and ld hardening by default. Resolves ticket 5210.
10186 o Major features (relay scaling):
10187 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
10188 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
10189 vectorized AES implementations as appropriate. These can be much,
10190 much faster than other AES implementations.
10191 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
10192 implementation. It makes AES_CTR about 7% faster than our old one
10193 (which was about 10% faster than the one OpenSSL used to provide).
10194 Resolves ticket 4526.
10195 - Use OpenSSL's EVP interface for AES encryption, so that all AES
10196 operations can use hardware acceleration (if present). Resolves
10198 - Unconditionally use OpenSSL's AES implementation instead of our
10199 old built-in one. OpenSSL's AES has been better for a while, and
10200 relatively few servers should still be on any version of OpenSSL
10201 that doesn't have good optimized assembly AES.
10203 o Major features (blocking resistance):
10204 - Update TLS cipher list to match Firefox 8 and later. Resolves
10206 - Remove support for clients falsely claiming to support standard
10207 ciphersuites that they can actually provide. As of modern OpenSSL
10208 versions, it's not necessary to fake any standard ciphersuite,
10209 and doing so prevents us from using better ciphersuites in the
10210 future, since servers can't know whether an advertised ciphersuite
10211 is really supported or not. Some hosts -- notably, ones with very
10212 old versions of OpenSSL or where OpenSSL has been built with ECC
10213 disabled -- will stand out because of this change; TBB users should
10214 not be affected. Implements the client side of proposal 198.
10215 - Implement a new handshake protocol (v3) for authenticating Tors to
10216 each other over TLS. It should be more resistant to fingerprinting
10217 than previous protocols, and should require less TLS hacking for
10218 future Tor implementations. Implements proposal 176.
10219 - Allow variable-length padding cells, to disguise the length of
10220 Tor's TLS records. Implements part of proposal 184.
10221 - While we're trying to bootstrap, record how many TLS connections
10222 fail in each state, and report which states saw the most failures
10223 in response to any bootstrap failures. This feature may speed up
10224 diagnosis of censorship events. Implements ticket 3116.
10226 o Major features (pluggable transports):
10227 - Clients and bridges can now be configured to use a separate
10228 "transport" proxy. This approach makes the censorship arms race
10229 easier by allowing bridges to use protocol obfuscation plugins.
10230 Implements proposal 180 (tickets 2841 and 3472).
10232 o Major features (DoS resistance):
10233 - Now that Tor 0.2.0.x is completely deprecated, enable the final
10234 part of "Proposal 110: Avoiding infinite length circuits" by
10235 refusing all circuit-extend requests that do not use a relay_early
10236 cell. This change helps Tor resist a class of denial-of-service
10237 attacks by limiting the maximum circuit length.
10238 - Tear down the circuit if we get an unexpected SENDME cell. Clients
10239 could use this trick to make their circuits receive cells faster
10240 than our flow control would have allowed, or to gum up the network,
10241 or possibly to do targeted memory denial-of-service attacks on
10242 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
10243 from July 2002, before the release of Tor 0.0.0.
10245 o Major features (hidden services):
10246 - Adjust the number of introduction points that a hidden service
10247 will try to maintain based on how long its introduction points
10248 remain in use and how many introductions they handle. Fixes
10250 - Add a "tor2web mode" for clients that want to connect to hidden
10251 services non-anonymously (and possibly more quickly). As a safety
10252 measure to try to keep users from turning this on without knowing
10253 what they are doing, tor2web mode must be explicitly enabled at
10254 compile time, and a copy of Tor compiled to run in tor2web mode
10255 cannot be used as a normal Tor client. Implements feature 2553.
10257 o Major features (IPv6):
10258 - Clients can now connect to private bridges over IPv6. Bridges
10259 still need at least one IPv4 address in order to connect to
10260 other relays. Note that we don't yet handle the case where the
10261 user has two bridge lines for the same bridge (one IPv4, one
10262 IPv6). Implements parts of proposal 186.
10264 o Major features (directory authorities):
10265 - Use a more secure consensus parameter voting algorithm. Now at
10266 least three directory authorities or a majority of them must
10267 vote on a given parameter before it will be included in the
10268 consensus. Implements proposal 178.
10269 - Remove the artificially low cutoff of 20KB to guarantee the Fast
10270 flag. In the past few years the average relay speed has picked
10271 up, and while the "top 7/8 of the network get the Fast flag" and
10272 "all relays with 20KB or more of capacity get the Fast flag" rules
10273 used to have the same result, now the top 7/8 of the network has
10274 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
10276 o Major features (performance):
10277 - Exit nodes now accept and queue data on not-yet-connected streams.
10278 Previously, the client wasn't allowed to send data until the
10279 stream was connected, which slowed down all connections. This
10280 change will enable clients to perform a "fast-start" on streams
10281 and send data without having to wait for a confirmation that the
10282 stream has opened. Patch from Ian Goldberg; implements the server
10283 side of Proposal 174.
10284 - When using an exit relay running 0.2.3.x, clients can now
10285 "optimistically" send data before the exit relay reports that
10286 the stream has opened. This saves a round trip when starting
10287 connections where the client speaks first (such as web browsing).
10288 This behavior is controlled by a consensus parameter (currently
10289 disabled). To turn it on or off manually, use the "OptimisticData"
10290 torrc option. Implements proposal 181; code by Ian Goldberg.
10291 - Add a new TokenBucketRefillInterval option to refill token buckets
10292 more frequently than once per second. This should improve network
10293 performance, alleviate queueing problems, and make traffic less
10294 bursty. Implements proposal 183; closes ticket 3630. Design by
10295 Florian Tschorsch and Björn Scheuermann; implementation by
10297 - Raise the threshold of server descriptors needed (75%) and exit
10298 server descriptors needed (50%) before we will declare ourselves
10299 bootstrapped. This will make clients start building circuits a
10300 little later, but makes the initially constructed circuits less
10301 skewed and less in conflict with further directory fetches. Fixes
10304 o Major features (relays):
10305 - Relays now try regenerating and uploading their descriptor more
10306 frequently if they are not listed in the consensus, or if the
10307 version of their descriptor listed in the consensus is too
10308 old. This fix should prevent situations where a server declines
10309 to re-publish itself because it has done so too recently, even
10310 though the authorities decided not to list its recent-enough
10311 descriptor. Fix for bug 3327.
10313 o Major features (stream isolation):
10314 - You can now configure Tor so that streams from different
10315 applications are isolated on different circuits, to prevent an
10316 attacker who sees your streams as they leave an exit node from
10317 linking your sessions to one another. To do this, choose some way
10318 to distinguish the applications: have them connect to different
10319 SocksPorts, or have one of them use SOCKS4 while the other uses
10320 SOCKS5, or have them pass different authentication strings to the
10321 SOCKS proxy. Then, use the new SocksPort syntax to configure the
10322 degree of isolation you need. This implements Proposal 171.
10323 - There's a new syntax for specifying multiple client ports (such as
10324 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
10325 multiple *Port entries with full addr:port syntax on each.
10326 The old *ListenAddress format is still supported, but you can't
10327 mix it with the new *Port syntax.
10329 o Major features (bufferevents):
10330 - Tor can now optionally build with the "bufferevents" buffered IO
10331 backend provided by Libevent 2. To use this feature, make sure you
10332 have the latest possible version of Libevent, and pass the
10333 --enable-bufferevents flag to configure when building Tor from
10334 source. This feature will make our networking code more flexible,
10335 let us stack layers on each other, and let us use more efficient
10336 zero-copy transports where available.
10337 - Add experimental support for running on Windows with IOCP and no
10338 kernel-space socket buffers. This feature is controlled by a new
10339 "UserspaceIOCPBuffers" config option (off by default), which has
10340 no effect unless Tor has been built with bufferevents enabled,
10341 you're running on Windows, and you've set "DisableIOCP 0". In the
10342 long run, this may help solve or mitigate bug 98.
10344 o Major features (path selection):
10345 - The EntryNodes option can now include country codes like {de} or IP
10346 addresses or network masks. Previously we had disallowed these
10347 options because we didn't have an efficient way to keep the list up
10348 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
10351 o Major features (port forwarding):
10352 - Add support for automatic port mapping on the many home routers
10353 that support NAT-PMP or UPnP. To build the support code, you'll
10354 need to have the libnatpnp library and/or the libminiupnpc library,
10355 and you'll need to enable the feature specifically by passing
10356 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
10357 it on, use the new PortForwarding option.
10359 o Major features (logging):
10360 - Add a new 'Heartbeat' log message type to periodically log a message
10361 describing Tor's status at level Notice. This feature is meant for
10362 operators who log at notice, and want to make sure that their Tor
10363 server is still working. Implementation by George Kadianakis.
10364 - Make logging resolution configurable with a new LogTimeGranularity
10365 option, and change the default from 1 millisecond to 1 second.
10366 Implements enhancement 1668.
10368 o Major features (other):
10369 - New "DisableNetwork" config option to prevent Tor from launching any
10370 connections or accepting any connections except on a control port.
10371 Bundles and controllers can set this option before letting Tor talk
10372 to the rest of the network, for example to prevent any connections
10373 to a non-bridge address. Packages like Orbot can also use this
10374 option to instruct Tor to save power when the network is off.
10375 - Try to use system facilities for enumerating local interface
10376 addresses, before falling back to our old approach (which was
10377 binding a UDP socket, and calling getsockname() on it). That
10378 approach was scaring OS X users whose draconian firewall
10379 software warned about binding to UDP sockets regardless of
10380 whether packets were sent. Now we try to use getifaddrs(),
10381 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
10382 system supports. Resolves ticket 1827.
10383 - Add experimental support for a "defaults" torrc file to be parsed
10384 before the regular torrc. Torrc options override the defaults file's
10385 options in the same way that the command line overrides the torrc.
10386 The SAVECONF controller command saves only those options which
10387 differ between the current configuration and the defaults file. HUP
10388 reloads both files. Implements task 4552.
10390 o New directory authorities:
10391 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
10392 authority. Closes ticket 5749.
10394 o Security/privacy fixes:
10395 - Avoid read-from-freed-memory and double-free bugs that could occur
10396 when a DNS request fails while launching it. Fixes bug 6480;
10397 bugfix on 0.2.0.1-alpha.
10398 - Reject any attempt to extend to an internal address. Without
10399 this fix, a router could be used to probe addresses on an internal
10400 network to see whether they were accepting connections. Fixes bug
10401 6710; bugfix on 0.0.8pre1.
10402 - Close any connection that sends unrecognized junk before the TLS
10403 handshake. Solves an issue noted in bug 4369.
10404 - The advertised platform of a relay now includes only its operating
10405 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
10406 its service pack level (for Windows) or its CPU architecture
10407 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
10408 can insert an extra string in the platform line by setting the
10409 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
10410 - Disable TLS session tickets. OpenSSL's implementation was giving
10411 our TLS session keys the lifetime of our TLS context objects, when
10412 perfect forward secrecy would want us to discard anything that
10413 could decrypt a link connection as soon as the link connection
10414 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10415 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10416 - Tor tries to wipe potentially sensitive data after using it, so
10417 that if some subsequent security failure exposes Tor's memory,
10418 the damage will be limited. But we had a bug where the compiler
10419 was eliminating these wipe operations when it decided that the
10420 memory was no longer visible to a (correctly running) program,
10421 hence defeating our attempt at defense in depth. We fix that
10422 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
10423 is unlikely to optimize away. Future versions of Tor may use
10424 a less ridiculously heavy approach for this. Fixes bug 7352.
10425 Reported in an article by Andrey Karpov.
10427 o Major bugfixes (crashes and asserts):
10428 - Avoid a pair of double-free and use-after-mark bugs that can
10429 occur with certain timings in canceled and re-received DNS
10430 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
10431 - Fix a denial of service attack by which any directory authority
10432 could crash all the others, or by which a single v2 directory
10433 authority could crash everybody downloading v2 directory
10434 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
10435 - Fix an assert that directory authorities could trigger on sighup
10436 during some configuration state transitions. We now don't treat
10437 it as a fatal error when the new descriptor we just generated in
10438 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
10439 - Avoid segfault when starting up having run with an extremely old
10440 version of Tor and parsing its state file. Fixes bug 6801; bugfix
10443 o Major bugfixes (clients):
10444 - If we are unable to find any exit that supports our predicted ports,
10445 stop calling them predicted, so that we don't loop and build
10446 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
10447 which introduced predicted ports.
10448 - Check at each new consensus whether our entry guards were picked
10449 long enough ago that we should rotate them. Previously, we only
10450 did this check at startup, which could lead to us holding a guard
10451 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
10452 - When fetching a bridge descriptor from a bridge authority,
10453 always do so anonymously, whether we have been able to open
10454 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
10455 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
10456 but we'll need to wait for bug 6010 before it's actually usable.
10458 o Major bugfixes (directory voting):
10459 - Check more thoroughly to prevent a rogue authority from
10460 double-voting on any consensus directory parameter. Previously,
10461 authorities would crash in this case if the total number of
10462 votes for any parameter exceeded the number of active voters,
10463 but would let it pass otherwise. Partially fixes bug 5786; bugfix
10465 - When computing weight parameters, behave more robustly in the
10466 presence of a bad bwweightscale value. Previously, the authorities
10467 would crash if they agreed on a sufficiently broken weight_scale
10468 value; now, they use a reasonable default and carry on. Fixes the
10469 rest of bug 5786; bugfix on 0.2.2.17-alpha.
10470 - If authorities are unable to get a v2 consensus document from other
10471 directory authorities, they no longer fall back to fetching
10472 them from regular directory caches. Fixes bug 5635; bugfix on
10473 0.2.2.26-beta, where routers stopped downloading v2 consensus
10474 documents entirely.
10476 o Major bugfixes (relays):
10477 - Fix a bug handling SENDME cells on nonexistent streams that could
10478 result in bizarre window values. Report and patch contributed
10479 pseudonymously. Fixes part of bug 6271. This bug was introduced
10480 before the first Tor release, in svn commit r152.
10481 - Don't update the AccountingSoftLimitHitAt state file entry whenever
10482 tor gets started. This prevents a wrong average bandwidth
10483 estimate, which would cause relays to always start a new accounting
10484 interval at the earliest possible moment. Fixes bug 2003; bugfix
10485 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
10486 immensely in tracking this bug down.
10487 - Fix a possible crash bug when checking for deactivated circuits
10488 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10489 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
10490 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
10491 connections. This change should allow busy exit relays to stop
10492 running out of available sockets as quickly. Fixes bug 4950;
10493 bugfix on 0.2.2.26-beta.
10495 o Major bugfixes (blocking resistance):
10496 - Bridges no longer include their address in NETINFO cells on outgoing
10497 OR connections, to allow them to blend in better with clients.
10498 Removes another avenue for enumerating bridges. Reported by
10499 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
10500 cells were introduced.
10501 - Warn the user when HTTPProxy, but no other proxy type, is
10502 configured. This can cause surprising behavior: it doesn't send
10503 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
10504 directory traffic only. Resolves ticket 4663.
10506 o Major bugfixes (hidden services):
10507 - Improve hidden service robustness: when an attempt to connect to
10508 a hidden service ends, be willing to refetch its hidden service
10509 descriptors from each of the HSDir relays responsible for them
10510 immediately. Previously, we would not consider refetching the
10511 service's descriptors from each HSDir for 15 minutes after the last
10512 fetch, which was inconvenient if the hidden service was not running
10513 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
10514 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
10515 They used to check that the timestamp was within 30 minutes
10516 of their system clock, so they could cap the size of their
10517 replay-detection cache, but that approach unnecessarily refused
10518 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
10519 the v3 intro-point protocol (the first one which sent a timestamp
10520 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
10521 - When one of a hidden service's introduction points appears to be
10522 unreachable, stop trying it. Previously, we would keep trying
10523 to build circuits to the introduction point until we lost the
10524 descriptor, usually because the user gave up and restarted Tor.
10525 Fixes part of bug 3825.
10527 o Changes to default torrc file:
10528 - Stop listing "socksport 9050" in torrc.sample. We open a socks
10529 port on 9050 by default anyway, so this should not change anything
10531 - Stop mentioning the deprecated *ListenAddress options in
10532 torrc.sample. Fixes bug 5438.
10533 - Document unit of bandwidth-related options in sample torrc.
10535 - Fix broken URLs in the sample torrc file, and tell readers about
10536 the OutboundBindAddress, ExitPolicyRejectPrivate, and
10537 PublishServerDescriptor options. Addresses bug 4652.
10539 o Minor features (directory authorities):
10540 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
10541 change when the authority is deciding whether to accept a newly
10542 uploaded descriptor. Implements ticket 6423.
10543 - Directory authorities are now a little more lenient at accepting
10544 older router descriptors, or newer router descriptors that don't
10545 make big changes. This should help ameliorate past and future
10546 issues where routers think they have uploaded valid descriptors,
10547 but the authorities don't think so. Fix for ticket 2479.
10548 - Authority operators can now vote for all relays in a given
10549 set of countries to be BadDir/BadExit/Invalid/Rejected.
10550 - Provide two consensus parameters (FastFlagMinThreshold and
10551 FastFlagMaxThreshold) to control the range of allowable bandwidths
10552 for the Fast directory flag. These allow authorities to run
10553 experiments on appropriate requirements for being a "Fast" node.
10554 The AuthDirFastGuarantee config value still applies. Implements
10557 o Minor features (bridges / bridge authorities):
10558 - Make bridge SSL certificates a bit more stealthy by using random
10559 serial numbers, in the same fashion as OpenSSL when generating
10560 self-signed certificates. Implements ticket 4584.
10561 - Tag a bridge's descriptor as "never to be sent unencrypted".
10562 This shouldn't matter, since bridges don't open non-anonymous
10563 connections to the bridge authority and don't allow unencrypted
10564 directory connections from clients, but we might as well make
10565 sure. Closes bug 5139.
10566 - The Bridge Authority now writes statistics on how many bridge
10567 descriptors it gave out in total, and how many unique descriptors
10568 it gave out. It also lists how often the most and least commonly
10569 fetched descriptors were given out, as well as the median and
10570 25th/75th percentile. Implements tickets 4200 and 4294.
10572 o Minor features (IPv6):
10573 - Make the code that clients use to detect an address change be
10574 IPv6-aware, so that it won't fill clients' logs with error
10575 messages when trying to get the IPv4 address of an IPv6
10576 connection. Implements ticket 5537.
10577 - Relays now understand an IPv6 address when they get one from a
10578 directory server. Resolves ticket 4875.
10580 o Minor features (hidden services):
10581 - Expire old or over-used hidden service introduction points.
10582 Required by fix for bug 3460.
10583 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
10584 public key replay-detection cache from 60 minutes to 5 minutes. This
10585 replay-detection cache is now used only to detect multiple
10586 INTRODUCE2 cells specifying the same rendezvous point, so we can
10587 avoid launching multiple simultaneous attempts to connect to it.
10588 - When a hidden service's introduction point times out, consider
10589 trying it again during the next attempt to connect to the
10590 HS. Previously, we would not try it again unless a newly fetched
10591 descriptor contained it. Required by fixes for bugs 1297 and 3825.
10593 o Minor features (relays):
10594 - Relays now include a reason for regenerating their descriptors
10595 in an HTTP header when uploading to the authorities. This will
10596 make it easier to debug descriptor-upload issues in the future.
10597 - Turn on directory request statistics by default and include them in
10598 extra-info descriptors. Don't break if we have no GeoIP database.
10599 - Replace files in stats/ rather than appending to them. Now that we
10600 include statistics in extra-info descriptors, it makes no sense to
10601 keep old statistics forever. Implements ticket 2930.
10602 - Relays that set "ConnDirectionStatistics 1" write statistics on the
10603 bidirectional use of connections to disk every 24 hours.
10604 - Add a GeoIP file digest to the extra-info descriptor. Implements
10607 o Minor features (new config options):
10608 - New config option "DynamicDHGroups" (disabled by default) provides
10609 each bridge with a unique prime DH modulus to be used during
10610 SSL handshakes. This option attempts to help against censors
10611 who might use the Apache DH modulus as a static identifier for
10612 bridges. Addresses ticket 4548.
10613 - New config option "DisableDebuggerAttachment" (on by default)
10614 to prevent basic debugging attachment attempts by other processes.
10615 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
10616 - Ordinarily, Tor does not count traffic from private addresses (like
10617 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
10618 There is now a new option, CountPrivateBandwidth, to disable this
10619 behavior. Patch from Daniel Cagara.
10621 o Minor features (different behavior for old config options):
10622 - Allow MapAddress directives to specify matches against super-domains,
10623 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
10624 Implements issue 933.
10625 - Don't disable the DirPort when we cannot exceed our AccountingMax
10626 limit during this interval because the effective bandwidthrate is
10627 low enough. This is useful in a situation where AccountMax is only
10628 used as an additional safeguard or to provide statistics.
10629 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
10630 implements ticket 3439.
10631 - When configuring a large set of nodes in EntryNodes, and there are
10632 enough of them listed as Guard so that we don't need to consider
10633 the non-guard entries, prefer the ones listed with the Guard flag.
10634 - If you set the NumCPUs option to 0, Tor will now try to detect how
10635 many CPUs you have. This is the new default behavior.
10636 - The NodeFamily option -- which let you declare that you want to
10637 consider nodes to be part of a family whether they list themselves
10638 that way or not -- now allows IP address ranges and country codes.
10640 o Minor features (new command-line config behavior):
10641 - Slightly change behavior of "list" options (that is, config
10642 options that can appear more than once) when they appear both in
10643 torrc and on the command line. Previously, the command-line options
10644 would be appended to the ones from torrc. Now, the command-line
10645 options override the torrc options entirely. This new behavior
10646 allows the user to override list options (like exit policies and
10647 ports to listen on) from the command line, rather than simply
10648 appending to the list.
10649 - You can get the old (appending) command-line behavior for "list"
10650 options by prefixing the option name with a "+".
10651 - You can remove all the values for a "list" option from the command
10652 line without adding any new ones by prefixing the option name
10655 o Minor features (controller, new events):
10656 - Extend the control protocol to report flags that control a circuit's
10657 path selection in CIRC events and in replies to 'GETINFO
10658 circuit-status'. Implements part of ticket 2411.
10659 - Extend the control protocol to report the hidden service address
10660 and current state of a hidden-service-related circuit in CIRC
10661 events and in replies to 'GETINFO circuit-status'. Implements part
10663 - Include the creation time of a circuit in CIRC and CIRC2
10664 control-port events and the list produced by the 'GETINFO
10665 circuit-status' control-port command.
10666 - Add a new CONF_CHANGED event so that controllers can be notified
10667 of any configuration changes made by other controllers, or by the
10668 user. Implements ticket 1692.
10669 - Add a new SIGNAL event to the controller interface so that
10670 controllers can be notified when Tor handles a signal. Resolves
10671 issue 1955. Patch by John Brooks.
10673 o Minor features (controller, new getinfo options):
10674 - Expose our view of whether we have gone dormant to the controller,
10675 via a new "GETINFO dormant" value. Torbutton and other controllers
10676 can use this to avoid doing periodic requests through Tor while
10677 it's dormant (bug 4718). Resolves ticket 5954.
10678 - Add a new GETINFO option to get total bytes read and written. Patch
10679 from pipe, revised by atagar. Resolves ticket 2345.
10680 - Implement new GETINFO controller fields to provide information about
10681 the Tor process's pid, euid, username, and resource limits.
10683 o Minor features (controller, other):
10684 - Allow controllers to request an event notification whenever a
10685 circuit is cannibalized or its purpose is changed. Implements
10686 part of ticket 3457.
10687 - Use absolute path names when reporting the torrc filename in the
10688 control protocol, so a controller can more easily find the torrc
10689 file. Resolves bug 1101.
10690 - When reporting the path to the cookie file to the controller,
10691 give an absolute path. Resolves ticket 4881.
10693 o Minor features (log messages):
10694 - Add more information to a log statement that might help track down
10695 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
10696 non-IP address" messages (or any Bug messages, for that matter!),
10697 please let us know about it.
10698 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
10699 EntryNodes will have no effect. Resolves issue 2571.
10700 - Try to make the introductory warning message that Tor prints on
10701 startup more useful for actually finding help and information.
10702 Resolves ticket 2474.
10703 - When the system call to create a listener socket fails, log the
10704 error message explaining why. This may help diagnose bug 4027.
10706 o Minor features (other):
10707 - When we fail to initialize Libevent, retry with IOCP disabled so we
10708 don't need to turn on multi-threading support in Libevent, which in
10709 turn requires a working socketpair(). This is a workaround for bug
10710 4457, which affects Libevent versions from 2.0.1-alpha through
10712 - When starting as root and then changing our UID via the User
10713 control option, and we have a ControlSocket configured, make sure
10714 that the ControlSocket is owned by the same account that Tor will
10715 run under. Implements ticket 3421; fix by Jérémy Bobbio.
10716 - Accept attempts to include a password authenticator in the
10717 handshake, as supported by SOCKS5. This handles SOCKS clients that
10718 don't know how to omit a password when authenticating. Resolves
10720 - Check for and recover from inconsistency in the microdescriptor
10721 cache. This will make it harder for us to accidentally free a
10722 microdescriptor without removing it from the appropriate data
10723 structures. Fixes issue 3135; issue noted by "wanoskarnet".
10724 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
10726 o Minor bugfixes (code security):
10727 - Prevent a null-pointer dereference when receiving a data cell
10728 for a nonexistent stream when the circuit in question has an
10729 empty deliver window. We don't believe this is triggerable,
10730 since we don't currently allow deliver windows to become empty,
10731 but the logic is tricky enough that it's better to make the code
10732 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
10733 - Fix a (harmless) integer overflow in cell statistics reported by
10734 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
10735 - Fix our implementation of crypto_random_hostname() so it can't
10736 overflow on ridiculously large inputs. (No Tor version has ever
10737 provided this kind of bad inputs, but let's be correct in depth.)
10738 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
10739 - Add a (probably redundant) memory clear between iterations of
10740 the router status voting loop, to prevent future coding errors
10741 where data might leak between iterations of the loop. Resolves
10744 o Minor bugfixes (wrapper functions):
10745 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
10746 utility function used in the control-port code). This shouldn't
10747 ever happen unless Tor is completely out of memory, but if it did
10748 happen and Tor somehow recovered from it, Tor could have sent a log
10749 message to a control port in the middle of a reply to a controller
10750 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
10751 - Fix some (not actually triggerable) buffer size checks in usage of
10752 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
10754 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
10755 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
10756 - Enforce correct return behavior of tor_vsscanf() when the '%%'
10757 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
10758 - Make our replacement implementation of strtok_r() compatible with
10759 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
10760 bugfix on 0.2.2.1-alpha.
10761 - Find more places in the code that should have been testing for
10762 invalid sockets using the SOCKET_OK macro. Required for a fix
10763 for bug 4533. Bugfix on 0.2.2.28-beta.
10765 o Minor bugfixes (code correctness):
10766 - Check return value of fputs() when writing authority certificate
10767 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
10768 - When building Tor on Windows with -DUNICODE (not default), ensure
10769 that error messages, filenames, and DNS server names are always
10770 NUL-terminated when we convert them to a single-byte encoding.
10771 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
10772 - Fix a memory leak when trying to launch a DNS request when the
10773 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
10775 - Correct file sizes when reading binary files on Cygwin, to avoid
10776 a bug where Tor would fail to read its state file. Fixes bug 6844;
10777 bugfix on 0.1.2.7-alpha.
10778 - Make sure to set *socket_error in all error cases in
10779 connection_connect(), so it can't produce a warning about
10780 errno being zero from errno_to_orconn_end_reason(). Bugfix on
10781 0.2.1.1-alpha; resolves ticket 6028.
10782 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
10783 bug 4532; found by "troll_un".
10785 o Minor bugfixes (clients):
10786 - Allow one-hop directory-fetching circuits the full "circuit build
10787 timeout" period, rather than just half of it, before failing them
10788 and marking the relay down. This fix should help reduce cases where
10789 clients declare relays (or worse, bridges) unreachable because
10790 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
10791 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
10793 - Ensure we don't cannibalize circuits that are longer than three hops
10794 already, so we don't end up making circuits with 5 or more
10795 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
10796 0.1.0.1-rc which introduced cannibalization.
10798 o Minor bugfixes (relays):
10799 - Don't publish a new relay descriptor when we reload our onion key,
10800 unless the onion key has actually changed. Fixes bug 3263 and
10801 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
10802 - When relays refuse a "create" cell because their queue of pending
10803 create cells is too big (typically because their cpu can't keep up
10804 with the arrival rate), send back reason "resource limit" rather
10805 than reason "internal", so network measurement scripts can get a
10806 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
10807 - Exit nodes don't need to fetch certificates for authorities that
10808 they don't recognize; only directory authorities, bridges,
10809 and caches need to do that. Fixes part of bug 2297; bugfix on
10812 o Minor bugfixes (directory authority / mirrors):
10813 - Avoid O(n^2) performance characteristics when parsing a large
10814 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
10815 - Authorities no longer include any router in their microdescriptor
10816 consensuses for which they couldn't generate or agree on a
10817 microdescriptor. Fixes the second piece of bug 6404; fix on
10819 - When checking for requested signatures on the latest consensus
10820 before serving it to a client, make sure to check the right
10821 consensus flavor. Bugfix on 0.2.2.6-alpha.
10822 - Fix an edge case where TestingTorNetwork is set but the authorities
10823 and relays all have an uptime of zero, so the private Tor network
10824 could briefly lack support for hidden services. Fixes bug 3886;
10825 bugfix on 0.2.2.18-alpha.
10826 - Directory caches no longer refuse to clean out descriptors because
10827 of missing v2 networkstatus documents, unless they're configured
10828 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
10829 0.2.2.26-beta. Patch by Daniel Bryg.
10830 - Don't serve or accept v2 hidden service descriptors over a relay's
10831 DirPort. It's never correct to do so, and disabling it might
10832 make it more annoying to exploit any bugs that turn up in the
10833 descriptor-parsing code. Fixes bug 7149.
10835 o Minor bugfixes (hidden services, client-side):
10836 - Assert that hidden-service-related operations are not performed
10837 using single-hop circuits. Previously, Tor would assert that
10838 client-side streams are not attached to single-hop circuits,
10839 but not that other sensitive operations on the client and service
10840 side are not performed using single-hop circuits. Fixes bug 3332;
10842 - Avoid undefined behavior when parsing the list of supported
10843 rendezvous/introduction protocols in a hidden service descriptor.
10844 Previously, Tor would have confused (as-yet-unused) protocol version
10845 numbers greater than 32 with lower ones on many platforms. Fixes
10846 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
10847 - Don't close hidden service client circuits which have almost
10848 finished connecting to their destination when they reach
10849 the normal circuit-build timeout. Previously, we would close
10850 introduction circuits which are waiting for an acknowledgement
10851 from the introduction point, and rendezvous circuits which have
10852 been specified in an INTRODUCE1 cell sent to a hidden service,
10853 after the normal CBT. Now, we mark them as 'timed out', and launch
10854 another rendezvous attempt in parallel. This behavior change can
10855 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
10856 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
10858 o Minor bugfixes (hidden services, service-side):
10859 - Don't close hidden-service-side rendezvous circuits when they
10860 reach the normal circuit-build timeout. This behavior change can
10861 be disabled using the new
10862 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
10863 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
10864 - Don't launch more than 10 service-side introduction-point circuits
10865 for a hidden service in five minutes. Previously, we would consider
10866 launching more introduction-point circuits if at least one second
10867 had passed without any introduction-point circuits failing. Fixes
10868 bug 4607; bugfix on 0.0.7pre1.
10870 o Minor bugfixes (config option behavior):
10871 - If the user tries to set MyFamily on a bridge, refuse to
10872 do so, and warn about the security implications. Fixes bug 4657;
10873 bugfix on 0.2.0.3-alpha.
10874 - The "--quiet" and "--hush" options now apply not only to Tor's
10875 behavior before logs are configured, but also to Tor's behavior in
10876 the absence of configured logs. Fixes bug 3550; bugfix on
10878 - Change the AllowDotExit rules so they should actually work.
10879 We now enforce AllowDotExit only immediately after receiving an
10880 address via SOCKS or DNSPort: other sources are free to provide
10881 .exit addresses after the resolution occurs. Fixes bug 3940;
10882 bugfix on 0.2.2.1-alpha.
10883 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
10884 don't depend on the consensus parameters or compute adaptive
10885 timeouts when it is disabled. Fixes bug 5049; bugfix on
10887 - After we pick a directory mirror, we would refuse to use it if
10888 it's in our ExcludeExitNodes list, resulting in mysterious failures
10889 to bootstrap for people who just wanted to avoid exiting from
10890 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
10891 - When told to add a bridge with the same digest as a preexisting
10892 bridge but a different addr:port, change the addr:port as
10893 requested. Previously we would not notice the change. Fixes half
10894 of bug 5603; fix on 0.2.2.26-beta.
10896 o Minor bugfixes (controller):
10897 - Allow manual 'authenticate' commands to the controller interface
10898 from netcat (nc) as well as telnet. We were rejecting them because
10899 they didn't come with the expected whitespace at the end of the
10900 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
10901 - Report a real bootstrap problem to the controller on router
10902 identity mismatch. Previously we just said "foo", which probably
10903 made a lot of sense at the time. Fixes bug 4169; bugfix on
10905 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
10906 option is set to 0 (which Vidalia version 0.2.16 now does when
10907 a SAVECONF attempt fails), perform other actions that SIGHUP
10908 usually causes (like reopening the logs). Fixes bug 5095; bugfix
10910 - Correctly handle checking the permissions on the parent
10911 directory of a control socket in the root directory. Bug found
10912 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
10914 - End AUTHCHALLENGE error messages (in the control protocol) with
10915 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
10917 o Minor bugfixes (network reading/writing):
10918 - Disable writing on marked-for-close connections when they are
10919 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
10920 bug 5263; bugfix on 0.0.2pre13, where we first added a special
10921 case for flushing marked connections.
10922 - Make sure that there are no unhandled pending TLS errors before
10923 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
10924 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
10925 Bugfix on 0.1.0.5-rc; fixes bug 4528.
10926 - Detect SSL handshake even when the initial attempt to write the
10927 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
10928 - If the client fails to set a reasonable set of ciphersuites
10929 during its v2 handshake renegotiation, allow the renegotiation to
10930 continue nevertheless (i.e. send all the required certificates).
10931 Fixes bug 4591; bugfix on 0.2.0.20-rc.
10933 o Minor bugfixes (other):
10934 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
10935 resource exhaustion, so that clients can adjust their load to
10936 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
10937 started using END_STREAM_REASON_RESOURCELIMIT.
10938 - Don't check for whether the address we're using for outbound
10939 connections has changed until after the outbound connection has
10940 completed. On Windows, getsockname() doesn't succeed until the
10941 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
10942 - Don't hold a Windows file handle open for every file mapping;
10943 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
10945 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
10946 bugfix on 0.2.1.10-alpha.
10947 - If we fail to write a microdescriptor to the disk cache, do not
10948 continue replacing the old microdescriptor file. Fixes bug 2954;
10949 bugfix on 0.2.2.6-alpha.
10951 o Minor bugfixes (log messages, path selection):
10952 - Downgrade "set buildtimeout to low value" messages to "info"
10953 severity; they were never an actual problem, there was never
10954 anything reasonable to do about them, and they tended to spam logs
10955 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
10956 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
10957 more information to it, so that we can track it down in case it
10958 returns again. Mitigates bug 5235.
10959 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
10960 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
10961 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
10962 - Issue a log message if a guard completes less than 40% of your
10963 circuits. Threshold is configurable by torrc option
10964 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
10965 additional, off-by-default code to disable guards which fail too
10966 many circuits. Addresses ticket 5458.
10968 o Minor bugfixes (log messages, client):
10969 - Downgrade "Got a certificate, but we already have it" log messages
10970 from warning to info, except when we're a dirauth. Fixes bug 5238;
10971 bugfix on 0.2.1.7-alpha.
10972 - Fix the log message describing how we work around discovering
10973 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
10974 4837; bugfix on 0.2.2.9-alpha.
10975 - When logging about a disallowed .exit name, do not also call it
10976 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
10977 - Fix a log message suggesting that people contact a non-existent
10978 email address. Fixes bug 3448.
10979 - Rephrase the log message emitted if the TestSocks check is
10980 successful. Patch from Fabian Keil; fixes bug 4094.
10981 - Log (at debug level) whenever a circuit's purpose is changed.
10982 - Log SSL state transitions at log level DEBUG, log domain
10983 HANDSHAKE. This can be useful for debugging censorship events.
10984 Implements ticket 3264.
10985 - We now log which torrc file we're using on startup. Implements
10987 - Rate-limit log messages when asked to connect anonymously to
10988 a private address. When these hit, they tended to hit fast and
10989 often. Also, don't bother trying to connect to addresses that we
10990 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
10991 reply makes us think we have been lied to, even when the address the
10992 client tried to connect to was "localhost." Resolves ticket 2822.
10994 o Minor bugfixes (log messages, non-client):
10995 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
10996 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
10997 - Don't log that we have "decided to publish new relay descriptor"
10998 unless we are actually publishing a descriptor. Fixes bug 3942;
10999 bugfix on 0.2.2.28-beta.
11000 - Log which authority we're missing votes from when we go to fetch
11001 them from the other auths.
11002 - Replace "Sending publish request" log messages with "Launching
11003 upload", so that they no longer confusingly imply that we're
11004 sending something to a directory we might not even be connected
11005 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
11006 - Warn when Tor is configured to use accounting in a way that can
11007 link a hidden service to some other hidden service or public
11008 address. Resolves ticket 6490.
11009 - Fix a minor formatting issue in one of tor-gencert's error messages.
11013 - Update to the latest version of the tinytest unit testing framework.
11014 This includes a couple of bugfixes that can be relevant for
11015 running forked unit tests on Windows, and removes all reserved
11017 - Avoid a false positive in the util/threads unit test by increasing
11018 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
11019 - Make it possible to set the TestingTorNetwork configuration
11020 option using AlternateDirAuthority and AlternateBridgeAuthority
11021 as an alternative to setting DirServer. Addresses ticket 6377.
11022 - Add a unit test for the environment_variable_names_equal() function.
11023 - A wide variety of new unit tests by Esteban Manchado Velázquez.
11024 - Numerous new unit tests for functions in util.c and address.c by
11026 - The long-disabled benchmark tests are now split into their own
11027 ./src/test/bench binary.
11028 - The benchmark tests can now use more accurate timers than
11029 gettimeofday() when such timers are available.
11030 - Use tt_assert(), not tor_assert(), for checking for test failures.
11031 This makes the unit tests more able to go on in the event that
11034 o Build improvements:
11035 - Use the dead_strip option when building Tor on OS X. This reduces
11036 binary size by almost 19% when linking openssl and libevent
11037 statically, which we do for Tor Browser Bundle.
11038 - Provide a better error message about possible OSX Asciidoc failure
11039 reasons. Fixes bug 6436.
11040 - Detect attempts to build Tor on (as yet hypothetical) versions
11041 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
11042 fix for bug 4533. Bugfix on 0.2.2.28-beta.
11043 - On Windows, we now define the _WIN32_WINNT macros only if they
11044 are not already defined. This lets the person building Tor decide,
11045 if they want, to require a later version of Windows.
11046 - Our autogen.sh script now uses autoreconf to launch autoconf,
11047 automake, and so on. This is more robust against some of the failure
11048 modes associated with running the autotools pieces on their own.
11049 - Running "make version" now displays the version of Tor that
11050 we're about to build. Idea from katmagic; resolves issue 4400.
11051 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
11052 on 0.2.2.4-alpha; fixes bug 3427.
11053 - New --enable-static-tor configure option for building Tor as
11054 statically as possible. Idea, general hackery and thoughts from
11055 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
11057 - Limited, experimental support for building with nmake and MSVC.
11059 o Build requirements:
11060 - Building Tor with bufferevent support now requires Libevent
11061 2.0.13-stable or later. Previous versions of Libevent had bugs in
11062 SSL-related bufferevents and related issues that would make Tor
11063 work badly with bufferevents. Requiring 2.0.13-stable also allows
11064 Tor with bufferevents to take advantage of Libevent APIs
11065 introduced after 2.0.8-rc.
11066 - Our build system requires automake 1.6 or later to create the
11067 Makefile.in files. Previously, you could have used 1.4.
11068 This only affects developers and people building Tor from git;
11069 people who build Tor from the source distribution without changing
11070 the Makefile.am files should be fine.
11071 - Detect when we try to build on a platform that doesn't define
11072 AF_UNSPEC to 0. We don't work there, so refuse to compile.
11074 o Build fixes (compile/link):
11075 - Format more doubles with %f, not %lf. Patch from grarpamp to make
11076 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
11078 - When building with --enable-static-tor on OpenBSD, do not
11079 erroneously attempt to link -lrt. Fixes bug 5103.
11080 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
11081 that IPv6 stuff will compile on MSVC, and compilation issues
11082 will be easier to track down. Fixes bug 5861.
11083 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
11084 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
11085 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
11086 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
11088 o Build fixes (other):
11089 - Use the _WIN32 macro throughout our code to detect Windows.
11090 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
11092 - Properly handle the case where the build-tree is not the same
11093 as the source tree when generating src/common/common_sha1.i,
11094 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
11095 bugfix on 0.2.0.1-alpha.
11096 - During configure, search for library containing cos function as
11097 libm lives in libcore on some platforms (BeOS/Haiku). Linking
11098 against libm was hard-coded before. Fixes the first part of bug
11099 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
11101 - Prevent a false positive from the check-spaces script, by disabling
11102 the "whitespace between function name and (" check for functions
11105 o Packaging (RPM) changes:
11106 - Update our default RPM spec files to work with mock and rpmbuild
11107 on RHEL/Fedora. They have an updated set of dependencies and
11108 conflicts, a fix for an ancient typo when creating the "_tor"
11109 user, and better instructions. Thanks to Ondrej Mikle for the
11110 patch series. Fixes bug 6043.
11111 - On OpenSUSE, create the /var/run/tor directory on startup if it
11112 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
11114 o Code refactoring (safety):
11115 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
11116 10 lines. Also, don't nest them. Doing so in the past has
11117 led to hard-to-debug code. The new style is to use the
11118 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
11119 - Use macros to indicate OpenSSL versions, so we don't need to worry
11120 about accidental hexadecimal bit shifts.
11121 - Use tor_sscanf() in place of scanf() in more places through the
11122 code. This makes us a little more locale-independent, and
11123 should help shut up code-analysis tools that can't tell
11124 a safe sscanf string from a dangerous one.
11125 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
11126 - Use the smartlist_add_asprintf() alias more consistently.
11128 o Code refactoring (consolidate):
11129 - A major revision to our internal node-selecting and listing logic.
11130 Tor already had at least two major ways to look at the question of
11131 "which Tor servers do we know about": a list of router descriptors,
11132 and a list of entries in the current consensus. With
11133 microdescriptors, we're adding a third. Having so many systems
11134 without an abstraction layer over them was hurting the codebase.
11135 Now, we have a new "node_t" abstraction that presents a consistent
11136 interface to a client's view of a Tor node, and holds (nearly) all
11137 of the mutable state formerly in routerinfo_t and routerstatus_t.
11138 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
11139 Libevent's notion of cached time when possible.
11140 - Remove duplicate code for invoking getrlimit() from control.c.
11141 - Use OpenSSL's built-in SSL_state_string_long() instead of our
11142 own homebrewed ssl_state_to_string() replacement. Patch from
11143 Emile Snyder. Fixes bug 4653.
11144 - Change the symmetric cipher interface so that creating and
11145 initializing a stream cipher are no longer separate functions.
11147 o Code refactoring (separate):
11148 - Make a new "entry connection" struct as an internal subtype of "edge
11149 connection", to simplify the code and make exit connections smaller.
11150 - Split connection_about_to_close() into separate functions for each
11152 - Rewrite the listener-selection logic so that parsing which ports
11153 we want to listen on is now separate from binding to the ports
11156 o Code refactoring (name changes):
11157 - Rename a handful of old identifiers, mostly related to crypto
11158 structures and crypto functions. By convention, our "create an
11159 object" functions are called "type_new()", our "free an object"
11160 functions are called "type_free()", and our types indicate that
11161 they are types only with a final "_t". But a handful of older
11162 types and functions broke these rules, with function names like
11163 "type_create" or "subsystem_op_type", or with type names like
11165 - Rename Tor functions that turn strings into addresses, so that
11166 "parse" indicates that no hostname resolution occurs, and
11167 "lookup" indicates that hostname resolution may occur. This
11168 should help prevent mistakes in the future. Fixes bug 3512.
11169 - Use the name "CERTS" consistently to refer to the new cell type;
11170 we were calling it CERT in some places and CERTS in others.
11171 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
11172 invalid value, rather than just -1.
11173 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
11174 can pick them up when the tests aren't disabled. Bugfix on
11175 0.2.2.4-alpha which introduced tinytest.
11177 o Code refactoring (other):
11178 - Defensively refactor rend_mid_rendezvous() so that protocol
11179 violations and length checks happen in the beginning. Fixes
11181 - Remove the pure attribute from all functions that used it
11182 previously. In many cases we assigned it incorrectly, because the
11183 functions might assert or call impure functions, and we don't have
11184 evidence that keeping the pure attribute is worthwhile. Implements
11185 changes suggested in ticket 4421.
11186 - Move the replay-detection cache for the RSA-encrypted parts of
11187 INTRODUCE2 cells to the introduction point data structures.
11188 Previously, we would use one replay-detection cache per hidden
11189 service. Required by fix for bug 3460.
11190 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
11191 no longer link against Libevent: they never used it, but
11192 our library structure used to force them to link it.
11194 o Removed features and files:
11195 - Remove all internal support for unpadded RSA. We never used it, and
11196 it would be a bad idea to start.
11197 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
11199 - Remove some redundant #include directives throughout the code.
11200 Patch from Andrea Gelmini.
11201 - Remove some old code to remember statistics about which descriptors
11202 we've served as a directory mirror. The feature wasn't used and
11203 is outdated now that microdescriptors are around.
11204 - Remove some old code to work around even older versions of Tor that
11205 used forked processes to handle DNS requests. Such versions of Tor
11206 are no longer in use as relays.
11207 - The "torify" script no longer supports the "tsocks" socksifier
11208 tool, since tsocks doesn't support DNS and UDP right for Tor.
11209 Everyone should be using torsocks instead. Fixes bugs 3530 and
11210 5180. Based on a patch by "ugh".
11211 - Remove the torrc.bridge file: we don't use it for anything, and
11212 it had become badly desynchronized from torrc.sample. Resolves
11216 - Begin a doc/state-contents.txt file to explain the contents of
11217 the Tor state file. Fixes bug 2987.
11218 - Clarify the documentation for the Alternate*Authority options.
11220 - Document the --defaults-torrc option, and the new semantics for
11221 overriding, extending, and clearing lists of options. Closes
11223 - Add missing man page documentation for consensus and microdesc
11224 files. Resolves ticket 6732.
11225 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
11227 o Documentation fixes:
11228 - Improve the manual's documentation for the NT Service command-line
11229 options. Addresses ticket 3964.
11230 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
11231 - Document the changes to the ORPort and DirPort options, and the
11232 fact that {OR/Dir}ListenAddress is now unnecessary (and
11233 therefore deprecated). Resolves ticket 5597.
11234 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
11235 - Clarify that hidden services are TCP only. Fixes bug 6024.
11238 Changes in version 0.2.2.39 - 2012-09-11
11239 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
11243 - Fix an assertion failure in tor_timegm() that could be triggered
11244 by a badly formatted directory object. Bug found by fuzzing with
11245 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11246 - Do not crash when comparing an address with port value 0 to an
11247 address policy. This bug could have been used to cause a remote
11248 assertion failure by or against directory authorities, or to
11249 allow some applications to crash clients. Fixes bug 6690; bugfix
11253 Changes in version 0.2.2.38 - 2012-08-12
11254 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
11255 attack that could in theory leak path information.
11258 - Avoid an uninitialized memory read when reading a vote or consensus
11259 document that has an unrecognized flavor name. This read could
11260 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
11261 - Try to leak less information about what relays a client is
11262 choosing to a side-channel attacker. Previously, a Tor client would
11263 stop iterating through the list of available relays as soon as it
11264 had chosen one, thus finishing a little earlier when it picked
11265 a router earlier in the list. If an attacker can recover this
11266 timing information (nontrivial but not proven to be impossible),
11267 they could learn some coarse-grained information about which relays
11268 a client was picking (middle nodes in particular are likelier to
11269 be affected than exits). The timing attack might be mitigated by
11270 other factors (see bug 6537 for some discussion), but it's best
11271 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
11274 Changes in version 0.2.2.37 - 2012-06-06
11275 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
11276 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11280 - Work around a bug in OpenSSL that broke renegotiation with TLS
11281 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11282 the v2 Tor connection protocol when both sides were using OpenSSL
11283 1.0.1 would fail. Resolves ticket 6033.
11284 - When waiting for a client to renegotiate, don't allow it to add
11285 any bytes to the input buffer. This fixes a potential DoS issue.
11286 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11287 - Fix an edge case where if we fetch or publish a hidden service
11288 descriptor, we might build a 4-hop circuit and then use that circuit
11289 for exiting afterwards -- even if the new last hop doesn't obey our
11290 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11293 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11294 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11297 - Tell GCC and Clang to check for any errors in format strings passed
11298 to the tor_v*(print|scan)f functions.
11301 Changes in version 0.2.2.36 - 2012-05-24
11302 Tor 0.2.2.36 updates the addresses for two of the eight directory
11303 authorities, fixes some potential anonymity and security issues,
11304 and fixes several crash bugs.
11306 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
11307 known flaws, and nobody should be using them. You should upgrade. If
11308 you're using a Linux or BSD and its packages are obsolete, stop using
11309 those packages and upgrade anyway.
11311 o Directory authority changes:
11312 - Change IP address for maatuska (v3 directory authority).
11313 - Change IP address for ides (v3 directory authority), and rename
11317 - When building or running with any version of OpenSSL earlier
11318 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11319 versions have a bug (CVE-2011-4576) in which their block cipher
11320 padding includes uninitialized data, potentially leaking sensitive
11321 information to any peer with whom they make a SSLv3 connection. Tor
11322 does not use SSL v3 by default, but a hostile client or server
11323 could force an SSLv3 connection in order to gain information that
11324 they shouldn't have been able to get. The best solution here is to
11325 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
11326 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
11327 to make sure that the bug can't happen.
11328 - Never use a bridge or a controller-supplied node as an exit, even
11329 if its exit policy allows it. Found by wanoskarnet. Fixes bug
11330 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
11331 and 0.2.0.3-alpha (for bridge-purpose descriptors).
11332 - Only build circuits if we have a sufficient threshold of the total
11333 descriptors that are marked in the consensus with the "Exit"
11334 flag. This mitigates an attack proposed by wanoskarnet, in which
11335 all of a client's bridges collude to restrict the exit nodes that
11336 the client knows about. Fixes bug 5343.
11337 - Provide controllers with a safer way to implement the cookie
11338 authentication mechanism. With the old method, if another locally
11339 running program could convince a controller that it was the Tor
11340 process, then that program could trick the controller into telling
11341 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
11342 authentication method uses a challenge-response approach to prevent
11343 this attack. Fixes bug 5185; implements proposal 193.
11346 - Avoid logging uninitialized data when unable to decode a hidden
11347 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
11348 - Avoid a client-side assertion failure when receiving an INTRODUCE2
11349 cell on a general purpose circuit. Fixes bug 5644; bugfix on
11351 - Fix builds when the path to sed, openssl, or sha1sum contains
11352 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
11354 - Correct our replacements for the timeradd() and timersub() functions
11355 on platforms that lack them (for example, Windows). The timersub()
11356 function is used when expiring circuits, while timeradd() is
11357 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
11358 bugfix on 0.2.2.24-alpha.
11359 - Fix the SOCKET_OK test that we use to tell when socket
11360 creation fails so that it works on Win64. Fixes part of bug 4533;
11361 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
11364 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
11365 Fixes bug 5346; bugfix on 0.0.8pre3.
11366 - Make our number-parsing functions always treat too-large values
11367 as an error, even when those values exceed the width of the
11368 underlying type. Previously, if the caller provided these
11369 functions with minima or maxima set to the extreme values of the
11370 underlying integer type, these functions would return those
11371 values on overflow rather than treating overflow as an error.
11372 Fixes part of bug 5786; bugfix on 0.0.9.
11373 - Older Linux kernels erroneously respond to strange nmap behavior
11374 by having accept() return successfully with a zero-length
11375 socket. When this happens, just close the connection. Previously,
11376 we would try harder to learn the remote address: but there was
11377 no such remote address to learn, and our method for trying to
11378 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
11379 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
11380 - Correct parsing of certain date types in parse_http_time().
11381 Without this patch, If-Modified-Since would behave
11382 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
11383 Esteban Manchado Velázques.
11384 - Change the BridgePassword feature (part of the "bridge community"
11385 design, which is not yet implemented) to use a time-independent
11386 comparison. The old behavior might have allowed an adversary
11387 to use timing to guess the BridgePassword value. Fixes bug 5543;
11388 bugfix on 0.2.0.14-alpha.
11389 - Detect and reject certain misformed escape sequences in
11390 configuration values. Previously, these values would cause us
11391 to crash if received in a torrc file or over an authenticated
11392 control port. Bug found by Esteban Manchado Velázquez, and
11393 independently by Robert Connolly from Matta Consulting who further
11394 noted that it allows a post-authentication heap overflow. Patch
11395 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
11396 bugfix on 0.2.0.16-alpha.
11397 - Fix a compile warning when using the --enable-openbsd-malloc
11398 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
11399 - During configure, detect when we're building with clang version
11400 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
11401 CFLAGS. clang doesn't support them yet.
11402 - When sending an HTTP/1.1 proxy request, include a Host header.
11403 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
11404 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
11405 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
11406 - If we hit the error case where routerlist_insert() replaces an
11407 existing (old) server descriptor, make sure to remove that
11408 server descriptor from the old_routers list. Fix related to bug
11409 1776. Bugfix on 0.2.2.18-alpha.
11411 o Minor bugfixes (documentation and log messages):
11412 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
11413 Fixes bug 4856; bugfix on Tor 0.0.6.
11414 - Update "ClientOnly" man page entry to explain that there isn't
11415 really any point to messing with it. Resolves ticket 5005.
11416 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
11417 directory authority option (introduced in Tor 0.2.2.34).
11418 - Downgrade the "We're missing a certificate" message from notice
11419 to info: people kept mistaking it for a real problem, whereas it
11420 is seldom the problem even when we are failing to bootstrap. Fixes
11421 bug 5067; bugfix on 0.2.0.10-alpha.
11422 - Correctly spell "connect" in a log message on failure to create a
11423 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
11424 - Clarify the behavior of MaxCircuitDirtiness with hidden service
11425 circuits. Fixes issue 5259.
11428 - Directory authorities now reject versions of Tor older than
11429 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
11430 inclusive. These versions accounted for only a small fraction of
11431 the Tor network, and have numerous known security issues. Resolves
11433 - Update to the May 1 2012 Maxmind GeoLite Country database.
11436 - When sending or relaying a RELAY_EARLY cell, we used to convert
11437 it to a RELAY cell if the connection was using the v1 link
11438 protocol. This was a workaround for older versions of Tor, which
11439 didn't handle RELAY_EARLY cells properly. Now that all supported
11440 versions can handle RELAY_EARLY cells, and now that we're enforcing
11441 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
11442 remove this workaround. Addresses bug 4786.
11445 Changes in version 0.2.2.35 - 2011-12-16
11446 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
11447 buffers code. Absolutely everybody should upgrade.
11449 The bug relied on an incorrect calculation when making data continuous
11450 in one of our IO buffers, if the first chunk of the buffer was
11451 misaligned by just the wrong amount. The miscalculation would allow an
11452 attacker to overflow a piece of heap-allocated memory. To mount this
11453 attack, the attacker would need to either open a SOCKS connection to
11454 Tor's SocksPort (usually restricted to localhost), or target a Tor
11455 instance configured to make its connections through a SOCKS proxy
11456 (which Tor does not do by default).
11458 Good security practice requires that all heap-overflow bugs should be
11459 presumed to be exploitable until proven otherwise, so we are treating
11460 this as a potential code execution attack. Please upgrade immediately!
11461 This bug does not affect bufferevents-based builds of Tor. Special
11462 thanks to "Vektor" for reporting this issue to us!
11464 Tor 0.2.2.35 also fixes several bugs in previous versions, including
11465 crash bugs for unusual configurations, and a long-term bug that
11466 would prevent Tor from starting on Windows machines with draconian
11469 With this release, we remind everyone that 0.2.0.x has reached its
11470 formal end-of-life. Those Tor versions have many known flaws, and
11471 nobody should be using them. You should upgrade -- ideally to the
11472 0.2.2.x series. If you're using a Linux or BSD and its packages are
11473 obsolete, stop using those packages and upgrade anyway.
11475 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
11476 longer receive support after some time in early 2012.
11479 - Fix a heap overflow bug that could occur when trying to pull
11480 data into the first chunk of a buffer, when that chunk had
11481 already had some data drained from it. Fixes CVE-2011-2778;
11482 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11483 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
11484 that it doesn't attempt to allocate a socketpair. This could cause
11485 some problems on Windows systems with overzealous firewalls. Fix for
11486 bug 4457; workaround for Libevent versions 2.0.1-alpha through
11488 - If we mark an OR connection for close based on a cell we process,
11489 don't process any further cells on it. We already avoid further
11490 reads on marked-for-close connections, but now we also discard the
11491 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
11492 which was the first version where we might mark a connection for
11493 close based on processing a cell on it.
11494 - Correctly sanity-check that we don't underflow on a memory
11495 allocation (and then assert) for hidden service introduction
11496 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11497 bugfix on 0.2.1.5-alpha.
11498 - Fix a memory leak when we check whether a hidden service
11499 descriptor has any usable introduction points left. Fixes bug
11500 4424. Bugfix on 0.2.2.25-alpha.
11501 - Don't crash when we're running as a relay and don't have a GeoIP
11502 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
11503 we've had in the 0.2.3.x branch already.
11504 - When running as a client, do not print a misleading (and plain
11505 wrong) log message that we're collecting "directory request"
11506 statistics: clients don't collect statistics. Also don't create a
11507 useless (because empty) stats file in the stats/ directory. Fixes
11508 bug 4353; bugfix on 0.2.2.34.
11511 - Detect failure to initialize Libevent. This fix provides better
11512 detection for future instances of bug 4457.
11513 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
11514 function. This was eating up hideously large amounts of time on some
11515 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
11516 - Resolve an integer overflow bug in smartlist_ensure_capacity().
11517 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
11519 - Don't warn about unused log_mutex in log.c when building with
11520 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
11521 0.1.0.6-rc which introduced --disable-threads.
11522 - When configuring, starting, or stopping an NT service, stop
11523 immediately after the service configuration attempt has succeeded
11524 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
11525 - When sending a NETINFO cell, include the original address
11526 received for the other side, not its canonical address. Found
11527 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
11528 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
11529 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
11530 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
11531 occurred when a client tried to fetch a descriptor for a bridge
11532 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
11533 - Backport fixes for a pair of compilation warnings on Windows.
11534 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
11535 - If we had ever tried to call tor_addr_to_str on an address of
11536 unknown type, we would have done a strdup on an uninitialized
11537 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
11538 Reported by "troll_un".
11539 - Correctly detect and handle transient lookup failures from
11540 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
11541 Reported by "troll_un".
11542 - Fix null-pointer access that could occur if TLS allocation failed.
11543 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
11544 - Use tor_socket_t type for listener argument to accept(). Fixes bug
11545 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
11548 - Add two new config options for directory authorities:
11549 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
11550 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
11551 that is always sufficient to satisfy the bandwidth requirement for
11552 the Guard flag. Now it will be easier for researchers to simulate
11553 Tor networks with different values. Resolves ticket 4484.
11554 - When Tor ignores a hidden service specified in its configuration,
11555 include the hidden service's directory in the warning message.
11556 Previously, we would only tell the user that some hidden service
11557 was ignored. Bugfix on 0.0.6; fixes bug 4426.
11558 - Update to the December 6 2011 Maxmind GeoLite Country database.
11560 o Packaging changes:
11561 - Make it easier to automate expert package builds on Windows,
11562 by removing an absolute path from makensis.exe command.
11565 Changes in version 0.2.1.32 - 2011-12-16
11566 Tor 0.2.1.32 backports important security and privacy fixes for
11567 oldstable. This release is intended only for package maintainers and
11568 others who cannot use the 0.2.2 stable series. All others should be
11569 using Tor 0.2.2.x or newer.
11571 The Tor 0.2.1.x series will reach formal end-of-life some time in
11572 early 2012; we will stop releasing patches for it then.
11574 o Major bugfixes (also included in 0.2.2.x):
11575 - Correctly sanity-check that we don't underflow on a memory
11576 allocation (and then assert) for hidden service introduction
11577 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11578 bugfix on 0.2.1.5-alpha.
11579 - Fix a heap overflow bug that could occur when trying to pull
11580 data into the first chunk of a buffer, when that chunk had
11581 already had some data drained from it. Fixes CVE-2011-2778;
11582 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11585 - Update to the December 6 2011 Maxmind GeoLite Country database.
11588 Changes in version 0.2.2.34 - 2011-10-26
11589 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
11590 can deanonymize Tor users. Everybody should upgrade.
11592 The attack relies on four components: 1) Clients reuse their TLS cert
11593 when talking to different relays, so relays can recognize a user by
11594 the identity key in her cert. 2) An attacker who knows the client's
11595 identity key can probe each guard relay to see if that identity key
11596 is connected to that guard relay right now. 3) A variety of active
11597 attacks in the literature (starting from "Low-Cost Traffic Analysis
11598 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
11599 discover the guard relays that a Tor user visiting the website is using.
11600 4) Clients typically pick three guards at random, so the set of guards
11601 for a given user could well be a unique fingerprint for her. This
11602 release fixes components #1 and #2, which is enough to block the attack;
11603 the other two remain as open research problems. Special thanks to
11604 "frosty_un" for reporting the issue to us!
11606 Clients should upgrade so they are no longer recognizable by the TLS
11607 certs they present. Relays should upgrade so they no longer allow a
11608 remote attacker to probe them to test whether unpatched clients are
11609 currently connected to them.
11611 This release also fixes several vulnerabilities that allow an attacker
11612 to enumerate bridge relays. Some bridge enumeration attacks still
11613 remain; see for example proposal 188.
11615 o Privacy/anonymity fixes (clients):
11616 - Clients and bridges no longer send TLS certificate chains on
11617 outgoing OR connections. Previously, each client or bridge would
11618 use the same cert chain for all outgoing OR connections until
11619 its IP address changes, which allowed any relay that the client
11620 or bridge contacted to determine which entry guards it is using.
11621 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11622 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11623 no longer considers that connection as suitable for satisfying a
11624 circuit EXTEND request. Now relays can protect clients from the
11625 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11626 - Directory authorities no longer assign the Guard flag to relays
11627 that haven't upgraded to the above "refuse EXTEND requests
11628 to client connections" fix. Now directory authorities can
11629 protect clients from the CVE-2011-2768 issue even if neither
11630 the clients nor the relays have upgraded yet. There's a new
11631 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
11632 to let us transition smoothly, else tomorrow there would be no
11635 o Privacy/anonymity fixes (bridge enumeration):
11636 - Bridge relays now do their directory fetches inside Tor TLS
11637 connections, like all the other clients do, rather than connecting
11638 directly to the DirPort like public relays do. Removes another
11639 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
11640 - Bridges relays now build circuits for themselves in a more similar
11641 way to how clients build them. Removes another avenue for
11642 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
11643 when bridges were introduced.
11644 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11645 that they initiated. Relays could distinguish incoming bridge
11646 connections from client connections, creating another avenue for
11647 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11648 Found by "frosty_un".
11651 - Fix a crash bug when changing node restrictions while a DNS lookup
11652 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
11654 - Don't launch a useless circuit after failing to use one of a
11655 hidden service's introduction points. Previously, we would
11656 launch a new introduction circuit, but not set the hidden service
11657 which that circuit was intended to connect to, so it would never
11658 actually be used. A different piece of code would then create a
11659 new introduction circuit correctly. Bug reported by katmagic and
11660 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
11663 - Change an integer overflow check in the OpenBSD_Malloc code so
11664 that GCC is less likely to eliminate it as impossible. Patch
11665 from Mansour Moufid. Fixes bug 4059.
11666 - When a hidden service turns an extra service-side introduction
11667 circuit into a general-purpose circuit, free the rend_data and
11668 intro_key fields first, so we won't leak memory if the circuit
11669 is cannibalized for use as another service-side introduction
11670 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
11671 - Bridges now skip DNS self-tests, to act a little more stealthily.
11672 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
11673 bridges. Patch by "warms0x".
11674 - Fix internal bug-checking logic that was supposed to catch
11675 failures in digest generation so that it will fail more robustly
11676 if we ask for a nonexistent algorithm. Found by Coverity Scan.
11677 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
11678 - Report any failure in init_keys() calls launched because our
11679 IP address has changed. Spotted by Coverity Scan. Bugfix on
11680 0.1.1.4-alpha; fixes CID 484.
11682 o Minor bugfixes (log messages and documentation):
11683 - Remove a confusing dollar sign from the example fingerprint in the
11684 man page, and also make the example fingerprint a valid one. Fixes
11685 bug 4309; bugfix on 0.2.1.3-alpha.
11686 - The next version of Windows will be called Windows 8, and it has
11687 a major version of 6, minor version of 2. Correctly identify that
11688 version instead of calling it "Very recent version". Resolves
11689 ticket 4153; reported by funkstar.
11690 - Downgrade log messages about circuit timeout calibration from
11691 "notice" to "info": they don't require or suggest any human
11692 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
11693 bugfix on 0.2.2.14-alpha.
11696 - Turn on directory request statistics by default and include them in
11697 extra-info descriptors. Don't break if we have no GeoIP database.
11698 Backported from 0.2.3.1-alpha; implements ticket 3951.
11699 - Update to the October 4 2011 Maxmind GeoLite Country database.
11702 Changes in version 0.2.1.31 - 2011-10-26
11703 Tor 0.2.1.31 backports important security and privacy fixes for
11704 oldstable. This release is intended only for package maintainers and
11705 others who cannot use the 0.2.2 stable series. All others should be
11706 using Tor 0.2.2.x or newer.
11708 o Security fixes (also included in 0.2.2.x):
11709 - Replace all potentially sensitive memory comparison operations
11710 with versions whose runtime does not depend on the data being
11711 compared. This will help resist a class of attacks where an
11712 adversary can use variations in timing information to learn
11713 sensitive data. Fix for one case of bug 3122. (Safe memcmp
11714 implementation by Robert Ransom based partially on code by DJB.)
11715 - Fix an assert in parsing router descriptors containing IPv6
11716 addresses. This one took down the directory authorities when
11717 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
11719 o Privacy/anonymity fixes (also included in 0.2.2.x):
11720 - Clients and bridges no longer send TLS certificate chains on
11721 outgoing OR connections. Previously, each client or bridge would
11722 use the same cert chain for all outgoing OR connections until
11723 its IP address changes, which allowed any relay that the client
11724 or bridge contacted to determine which entry guards it is using.
11725 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11726 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11727 no longer considers that connection as suitable for satisfying a
11728 circuit EXTEND request. Now relays can protect clients from the
11729 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11730 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11731 that they initiated. Relays could distinguish incoming bridge
11732 connections from client connections, creating another avenue for
11733 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11734 Found by "frosty_un".
11735 - When receiving a hidden service descriptor, check that it is for
11736 the hidden service we wanted. Previously, Tor would store any
11737 hidden service descriptors that a directory gave it, whether it
11738 wanted them or not. This wouldn't have let an attacker impersonate
11739 a hidden service, but it did let directories pre-seed a client
11740 with descriptors that it didn't want. Bugfix on 0.0.6.
11741 - Avoid linkability based on cached hidden service descriptors: forget
11742 all hidden service descriptors cached as a client when processing a
11743 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
11744 - Make the bridge directory authority refuse to answer directory
11745 requests for "all" descriptors. It used to include bridge
11746 descriptors in its answer, which was a major information leak.
11747 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
11748 - Don't attach new streams to old rendezvous circuits after SIGNAL
11749 NEWNYM. Previously, we would keep using an existing rendezvous
11750 circuit if it remained open (i.e. if it were kept open by a
11751 long-lived stream, or if a new stream were attached to it before
11752 Tor could notice that it was old and no longer in use). Bugfix on
11753 0.1.1.15-rc; fixes bug 3375.
11755 o Minor bugfixes (also included in 0.2.2.x):
11756 - When we restart our relay, we might get a successful connection
11757 from the outside before we've started our reachability tests,
11758 triggering a warning: "ORPort found reachable, but I have no
11759 routerinfo yet. Failing to inform controller of success." This
11760 bug was harmless unless Tor is running under a controller
11761 like Vidalia, in which case the controller would never get a
11762 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
11764 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11765 enabled. Fixes bug 1526.
11766 - Remove undocumented option "-F" from tor-resolve: it hasn't done
11767 anything since 0.2.1.16-rc.
11768 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
11769 None of the cases where we did this before were wrong, but by making
11770 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
11771 - Fix a rare crash bug that could occur when a client was configured
11772 with a large number of bridges. Fixes bug 2629; bugfix on
11773 0.2.1.2-alpha. Bugfix by trac user "shitlei".
11774 - Correct the warning displayed when a rendezvous descriptor exceeds
11775 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
11777 - Fix an uncommon assertion failure when running with DNSPort under
11778 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
11779 - When warning about missing zlib development packages during compile,
11780 give the correct package names. Bugfix on 0.2.0.1-alpha.
11781 - Require that introduction point keys and onion keys have public
11782 exponent 65537. Bugfix on 0.2.0.10-alpha.
11783 - Do not crash when our configuration file becomes unreadable, for
11784 example due to a permissions change, between when we start up
11785 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
11787 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
11789 - Always NUL-terminate the sun_path field of a sockaddr_un before
11790 passing it to the kernel. (Not a security issue: kernels are
11791 smart enough to reject bad sockaddr_uns.) Found by Coverity;
11792 CID #428. Bugfix on Tor 0.2.0.3-alpha.
11793 - Don't stack-allocate the list of supplementary GIDs when we're
11794 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
11795 could take up to 256K, which is way too much stack. Found by
11796 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
11798 o Minor bugfixes (only in 0.2.1.x):
11799 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
11800 rely on them. Bugfix on 0.2.1.30.
11801 - Use git revisions instead of svn revisions when generating our
11802 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
11804 o Minor features (also included in 0.2.2.x):
11805 - Adjust the expiration time on our SSL session certificates to
11806 better match SSL certs seen in the wild. Resolves ticket 4014.
11807 - Allow nameservers with IPv6 address. Resolves bug 2574.
11808 - Update to the October 4 2011 Maxmind GeoLite Country database.
11811 Changes in version 0.2.2.33 - 2011-09-13
11812 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
11813 TLS handshake that makes relays and bridges that run this new version
11814 reachable from Iran again.
11817 - Avoid an assertion failure when reloading a configuration with
11818 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
11819 3923; bugfix on 0.2.2.25-alpha.
11821 o Minor features (security):
11822 - Check for replays of the public-key encrypted portion of an
11823 INTRODUCE1 cell, in addition to the current check for replays of
11824 the g^x value. This prevents a possible class of active attacks
11825 by an attacker who controls both an introduction point and a
11826 rendezvous point, and who uses the malleability of AES-CTR to
11827 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
11828 that these attacks are infeasible (requiring the attacker to send
11829 on the order of zettabytes of altered cells in a short interval),
11830 but we'd rather block them off in case there are any classes of
11831 this attack that we missed. Reported by Willem Pinckaers.
11834 - Adjust the expiration time on our SSL session certificates to
11835 better match SSL certs seen in the wild. Resolves ticket 4014.
11836 - Change the default required uptime for a relay to be accepted as
11837 a HSDir (hidden service directory) from 24 hours to 25 hours.
11838 Improves on 0.2.0.10-alpha; resolves ticket 2649.
11839 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
11840 authorities to abstain from voting on assignment of the HSDir
11841 consensus flag. Related to bug 2649.
11842 - Update to the September 6 2011 Maxmind GeoLite Country database.
11844 o Minor bugfixes (documentation and log messages):
11845 - Correct the man page to explain that HashedControlPassword and
11846 CookieAuthentication can both be set, in which case either method
11847 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
11848 when we decided to allow these config options to both be set. Issue
11849 raised by bug 3898.
11850 - Demote the 'replay detected' log message emitted when a hidden
11851 service receives the same Diffie-Hellman public key in two different
11852 INTRODUCE2 cells to info level. A normal Tor client can cause that
11853 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
11854 fixes part of bug 2442.
11855 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
11856 level. There is nothing that a hidden service's operator can do
11857 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
11859 - Clarify a log message specifying the characters permitted in
11860 HiddenServiceAuthorizeClient client names. Previously, the log
11861 message said that "[A-Za-z0-9+-_]" were permitted; that could have
11862 given the impression that every ASCII character between "+" and "_"
11863 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
11866 - Provide a substitute implementation of lround() for MSVC, which
11867 apparently lacks it. Patch from Gisle Vanem.
11868 - Clean up some code issues that prevented Tor from building on older
11869 BSDs. Fixes bug 3894; reported by "grarpamp".
11870 - Search for a platform-specific version of "ar" when cross-compiling.
11871 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
11874 Changes in version 0.2.2.32 - 2011-08-27
11875 The Tor 0.2.2 release series is dedicated to the memory of Andreas
11876 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
11877 a founder of the PETS community, a leader in our field, a mentor,
11878 and a friend. He left us with these words: "I had the possibility
11879 to contribute to this world that is not as it should be. I hope I
11880 could help in some areas to make the world a better place, and that
11881 I could also encourage other people to be engaged in improving the
11882 world. Please, stay engaged. This world needs you, your love, your
11883 initiative -- now I cannot be part of that anymore."
11885 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
11886 ready. More than two years in the making, this release features improved
11887 client performance and hidden service reliability, better compatibility
11888 for Android, correct behavior for bridges that listen on more than
11889 one address, more extensible and flexible directory object handling,
11890 better reporting of network statistics, improved code security, and
11891 many many other features and bugfixes.
11893 o Major features (client performance):
11894 - When choosing which cells to relay first, relays now favor circuits
11895 that have been quiet recently, to provide lower latency for
11896 low-volume circuits. By default, relays enable or disable this
11897 feature based on a setting in the consensus. They can override
11898 this default by using the new "CircuitPriorityHalflife" config
11899 option. Design and code by Ian Goldberg, Can Tang, and Chris
11901 - Directory authorities now compute consensus weightings that instruct
11902 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
11903 and no flag. Clients use these weightings to distribute network load
11904 more evenly across these different relay types. The weightings are
11905 in the consensus so we can change them globally in the future. Extra
11906 thanks to "outofwords" for finding some nasty security bugs in
11907 the first implementation of this feature.
11909 o Major features (client performance, circuit build timeout):
11910 - Tor now tracks how long it takes to build client-side circuits
11911 over time, and adapts its timeout to local network performance.
11912 Since a circuit that takes a long time to build will also provide
11913 bad performance, we get significant latency improvements by
11914 discarding the slowest 20% of circuits. Specifically, Tor creates
11915 circuits more aggressively than usual until it has enough data
11916 points for a good timeout estimate. Implements proposal 151.
11917 - Circuit build timeout constants can be controlled by consensus
11918 parameters. We set good defaults for these parameters based on
11919 experimentation on broadband and simulated high-latency links.
11920 - Circuit build time learning can be disabled via consensus parameter
11921 or by the client via a LearnCircuitBuildTimeout config option. We
11922 also automatically disable circuit build time calculation if either
11923 AuthoritativeDirectory is set, or if we fail to write our state
11924 file. Implements ticket 1296.
11926 o Major features (relays use their capacity better):
11927 - Set SO_REUSEADDR socket option on all sockets, not just
11928 listeners. This should help busy exit nodes avoid running out of
11929 useable ports just because all the ports have been used in the
11930 near past. Resolves issue 2850.
11931 - Relays now save observed peak bandwidth throughput rates to their
11932 state file (along with total usage, which was already saved),
11933 so that they can determine their correct estimated bandwidth on
11934 restart. Resolves bug 1863, where Tor relays would reset their
11935 estimated bandwidth to 0 after restarting.
11936 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
11937 should give us approximately 40-50% more Guard-flagged nodes,
11938 improving the anonymity the Tor network can provide and also
11939 decreasing the dropoff in throughput that relays experience when
11940 they first get the Guard flag.
11941 - Directory authorities now take changes in router IP address and
11942 ORPort into account when determining router stability. Previously,
11943 if a router changed its IP or ORPort, the authorities would not
11944 treat it as having any downtime for the purposes of stability
11945 calculation, whereas clients would experience downtime since the
11946 change would take a while to propagate to them. Resolves issue 1035.
11947 - New AccelName and AccelDir options add support for dynamic OpenSSL
11948 hardware crypto acceleration engines.
11950 o Major features (relays control their load better):
11951 - Exit relays now try harder to block exit attempts from unknown
11952 relays, to make it harder for people to use them as one-hop proxies
11953 a la tortunnel. Controlled by the refuseunknownexits consensus
11954 parameter (currently enabled), or you can override it on your
11955 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
11956 based on a variant of proposal 163.
11957 - Add separate per-conn write limiting to go with the per-conn read
11958 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11959 but never per-conn write limits.
11960 - New consensus params "bwconnrate" and "bwconnburst" to let us
11961 rate-limit client connections as they enter the network. It's
11962 controlled in the consensus so we can turn it on and off for
11963 experiments. It's starting out off. Based on proposal 163.
11965 o Major features (controllers):
11966 - Export GeoIP information on bridge usage to controllers even if we
11967 have not yet been running for 24 hours. Now Vidalia bridge operators
11968 can get more accurate and immediate feedback about their
11969 contributions to the network.
11970 - Add an __OwningControllerProcess configuration option and a
11971 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
11972 that when it exits, Tor will shut down. Implements feature 3049.
11974 o Major features (directory authorities):
11975 - Directory authorities now create, vote on, and serve multiple
11976 parallel formats of directory data as part of their voting process.
11977 Partially implements Proposal 162: "Publish the consensus in
11979 - Directory authorities now agree on and publish small summaries
11980 of router information that clients can use in place of regular
11981 server descriptors. This transition will allow Tor 0.2.3 clients
11982 to use far less bandwidth for downloading information about the
11983 network. Begins the implementation of Proposal 158: "Clients
11984 download consensus + microdescriptors".
11985 - The directory voting system is now extensible to use multiple hash
11986 algorithms for signatures and resource selection. Newer formats
11987 are signed with SHA256, with a possibility for moving to a better
11988 hash algorithm in the future.
11989 - Directory authorities can now vote on arbitrary integer values as
11990 part of the consensus process. This is designed to help set
11991 network-wide parameters. Implements proposal 167.
11993 o Major features and bugfixes (node selection):
11994 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
11995 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
11996 options. Previously, we had been ambiguous in describing what
11997 counted as an "exit" node, and what operations exactly "StrictNodes
11998 0" would permit. This created confusion when people saw nodes built
11999 through unexpected circuits, and made it hard to tell real bugs from
12000 surprises. Now the intended behavior is:
12001 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
12002 a node that delivers user traffic outside the Tor network.
12003 . "Entry", in the context of EntryNodes, means a node used as the
12004 first hop of a multihop circuit. It doesn't include direct
12005 connections to directory servers.
12006 . "ExcludeNodes" applies to all nodes.
12007 . "StrictNodes" changes the behavior of ExcludeNodes only. When
12008 StrictNodes is set, Tor should avoid all nodes listed in
12009 ExcludeNodes, even when it will make user requests fail. When
12010 StrictNodes is *not* set, then Tor should follow ExcludeNodes
12011 whenever it can, except when it must use an excluded node to
12012 perform self-tests, connect to a hidden service, provide a
12013 hidden service, fulfill a .exit request, upload directory
12014 information, or fetch directory information.
12015 Collectively, the changes to implement the behavior fix bug 1090.
12016 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
12017 change during a config reload, mark and discard all our origin
12018 circuits. This fix should address edge cases where we change the
12019 config options and but then choose a circuit that we created before
12021 - Make EntryNodes config option much more aggressive even when
12022 StrictNodes is not set. Before it would prepend your requested
12023 entrynodes to your list of guard nodes, but feel free to use others
12024 after that. Now it chooses only from your EntryNodes if any of
12025 those are available, and only falls back to others if a) they're
12026 all down and b) StrictNodes is not set.
12027 - Now we refresh your entry guards from EntryNodes at each consensus
12028 fetch -- rather than just at startup and then they slowly rot as
12029 the network changes.
12030 - Add support for the country code "{??}" in torrc options like
12031 ExcludeNodes, to indicate all routers of unknown country. Closes
12033 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
12034 a node is listed in both, it's treated as excluded.
12035 - ExcludeNodes now applies to directory nodes -- as a preference if
12036 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
12037 Don't exclude all the directory authorities and set StrictNodes to 1
12038 unless you really want your Tor to break.
12039 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
12040 - ExcludeExitNodes now overrides .exit requests.
12041 - We don't use bridges listed in ExcludeNodes.
12042 - When StrictNodes is 1:
12043 . We now apply ExcludeNodes to hidden service introduction points
12044 and to rendezvous points selected by hidden service users. This
12045 can make your hidden service less reliable: use it with caution!
12046 . If we have used ExcludeNodes on ourself, do not try relay
12047 reachability self-tests.
12048 . If we have excluded all the directory authorities, we will not
12049 even try to upload our descriptor if we're a relay.
12050 . Do not honor .exit requests to an excluded node.
12051 - When the set of permitted nodes changes, we now remove any mappings
12052 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
12054 - We never cannibalize a circuit that had excluded nodes on it, even
12055 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
12056 - Improve log messages related to excluded nodes.
12058 o Major features (misc):
12059 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
12060 to help Tor build correctly for Android phones.
12061 - The options SocksPort, ControlPort, and so on now all accept a
12062 value "auto" that opens a socket on an OS-selected port. A
12063 new ControlPortWriteToFile option tells Tor to write its
12064 actual control port or ports to a chosen file. If the option
12065 ControlPortFileGroupReadable is set, the file is created as
12066 group-readable. Now users can run two Tor clients on the same
12067 system without needing to manually mess with parameters. Resolves
12068 part of ticket 3076.
12069 - Tor now supports tunneling all of its outgoing connections over
12070 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12071 configuration options. Code by Christopher Davis.
12073 o Code security improvements:
12074 - Replace all potentially sensitive memory comparison operations
12075 with versions whose runtime does not depend on the data being
12076 compared. This will help resist a class of attacks where an
12077 adversary can use variations in timing information to learn
12078 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12079 implementation by Robert Ransom based partially on code by DJB.)
12080 - Enable Address Space Layout Randomization (ASLR) and Data Execution
12081 Prevention (DEP) by default on Windows to make it harder for
12082 attackers to exploit vulnerabilities. Patch from John Brooks.
12083 - New "--enable-gcc-hardening" ./configure flag (off by default)
12084 to turn on gcc compile time hardening options. It ensures
12085 that signed ints have defined behavior (-fwrapv), enables
12086 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
12087 with canaries (-fstack-protector-all), turns on ASLR protection if
12088 supported by the kernel (-fPIE, -pie), and adds additional security
12089 related warnings. Verified to work on Mac OS X and Debian Lenny.
12090 - New "--enable-linker-hardening" ./configure flag (off by default)
12091 to turn on ELF specific hardening features (relro, now). This does
12092 not work with Mac OS X or any other non-ELF binary format.
12093 - Always search the Windows system directory for system DLLs, and
12094 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
12095 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
12096 current and future memory pages via mlockall(). On supported
12097 platforms (modern Linux and probably BSD but not Windows or OS X),
12098 this should effectively disable any and all attempts to page out
12099 memory. This option requires that you start your Tor as root --
12100 if you use DisableAllSwap, please consider using the User option
12101 to properly reduce the privileges of your Tor.
12103 o Major bugfixes (crashes):
12104 - Fix crash bug on platforms where gmtime and localtime can return
12105 NULL. Windows 7 users were running into this one. Fixes part of bug
12106 2077. Bugfix on all versions of Tor. Found by boboper.
12107 - Introduce minimum/maximum values that clients will believe
12108 from the consensus. Now we'll have a better chance to avoid crashes
12109 or worse when a consensus param has a weird value.
12110 - Fix a rare crash bug that could occur when a client was configured
12111 with a large number of bridges. Fixes bug 2629; bugfix on
12112 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12113 - Do not crash when our configuration file becomes unreadable, for
12114 example due to a permissions change, between when we start up
12115 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12117 - If we're in the pathological case where there's no exit bandwidth
12118 but there is non-exit bandwidth, or no guard bandwidth but there
12119 is non-guard bandwidth, don't crash during path selection. Bugfix
12121 - Fix a crash bug when trying to initialize the evdns module in
12122 Libevent 2. Bugfix on 0.2.1.16-rc.
12124 o Major bugfixes (stability):
12125 - Fix an assert in parsing router descriptors containing IPv6
12126 addresses. This one took down the directory authorities when
12127 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12128 - Fix an uncommon assertion failure when running with DNSPort under
12129 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12130 - Treat an unset $HOME like an empty $HOME rather than triggering an
12131 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
12132 - More gracefully handle corrupt state files, removing asserts
12133 in favor of saving a backup and resetting state.
12134 - Instead of giving an assertion failure on an internal mismatch
12135 on estimated freelist size, just log a BUG warning and try later.
12136 Mitigates but does not fix bug 1125.
12137 - Fix an assert that got triggered when using the TestingTorNetwork
12138 configuration option and then issuing a GETINFO config-text control
12139 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
12140 - If the cached cert file is unparseable, warn but don't exit.
12142 o Privacy fixes (relays/bridges):
12143 - Don't list Windows capabilities in relay descriptors. We never made
12144 use of them, and maybe it's a bad idea to publish them. Bugfix
12146 - If the Nickname configuration option isn't given, Tor would pick a
12147 nickname based on the local hostname as the nickname for a relay.
12148 Because nicknames are not very important in today's Tor and the
12149 "Unnamed" nickname has been implemented, this is now problematic
12150 behavior: It leaks information about the hostname without being
12151 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
12152 introduced the Unnamed nickname. Reported by tagnaq.
12153 - Maintain separate TLS contexts and certificates for incoming and
12154 outgoing connections in bridge relays. Previously we would use the
12155 same TLS contexts and certs for incoming and outgoing connections.
12156 Bugfix on 0.2.0.3-alpha; addresses bug 988.
12157 - Maintain separate identity keys for incoming and outgoing TLS
12158 contexts in bridge relays. Previously we would use the same
12159 identity keys for incoming and outgoing TLS contexts. Bugfix on
12160 0.2.0.3-alpha; addresses the other half of bug 988.
12161 - Make the bridge directory authority refuse to answer directory
12162 requests for "all descriptors". It used to include bridge
12163 descriptors in its answer, which was a major information leak.
12164 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12166 o Privacy fixes (clients):
12167 - When receiving a hidden service descriptor, check that it is for
12168 the hidden service we wanted. Previously, Tor would store any
12169 hidden service descriptors that a directory gave it, whether it
12170 wanted them or not. This wouldn't have let an attacker impersonate
12171 a hidden service, but it did let directories pre-seed a client
12172 with descriptors that it didn't want. Bugfix on 0.0.6.
12173 - Start the process of disabling ".exit" address notation, since it
12174 can be used for a variety of esoteric application-level attacks
12175 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12177 - Reject attempts at the client side to open connections to private
12178 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
12179 a randomly chosen exit node. Attempts to do so are always
12180 ill-defined, generally prevented by exit policies, and usually
12181 in error. This will also help to detect loops in transparent
12182 proxy configurations. You can disable this feature by setting
12183 "ClientRejectInternalAddresses 0" in your torrc.
12184 - Log a notice when we get a new control connection. Now it's easier
12185 for security-conscious users to recognize when a local application
12186 is knocking on their controller door. Suggested by bug 1196.
12188 o Privacy fixes (newnym):
12189 - Avoid linkability based on cached hidden service descriptors: forget
12190 all hidden service descriptors cached as a client when processing a
12191 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12192 - On SIGHUP, do not clear out all TrackHostExits mappings, client
12193 DNS cache entries, and virtual address mappings: that's what
12194 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
12195 - Don't attach new streams to old rendezvous circuits after SIGNAL
12196 NEWNYM. Previously, we would keep using an existing rendezvous
12197 circuit if it remained open (i.e. if it were kept open by a
12198 long-lived stream, or if a new stream were attached to it before
12199 Tor could notice that it was old and no longer in use). Bugfix on
12200 0.1.1.15-rc; fixes bug 3375.
12202 o Major bugfixes (relay bandwidth accounting):
12203 - Fix a bug that could break accounting on 64-bit systems with large
12204 time_t values, making them hibernate for impossibly long intervals.
12205 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
12206 - Fix a bug in bandwidth accounting that could make us use twice
12207 the intended bandwidth when our interval start changes due to
12208 daylight saving time. Now we tolerate skew in stored vs computed
12209 interval starts: if the start of the period changes by no more than
12210 50% of the period's duration, we remember bytes that we transferred
12211 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
12213 o Major bugfixes (bridges):
12214 - Bridges now use "reject *:*" as their default exit policy. Bugfix
12215 on 0.2.0.3-alpha. Fixes bug 1113.
12216 - If you configure your bridge with a known identity fingerprint,
12217 and the bridge authority is unreachable (as it is in at least
12218 one country now), fall back to directly requesting the descriptor
12219 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
12221 - Fix a bug where bridge users who configure the non-canonical
12222 address of a bridge automatically switch to its canonical
12223 address. If a bridge listens at more than one address, it
12224 should be able to advertise those addresses independently and
12225 any non-blocked addresses should continue to work. Bugfix on Tor
12226 0.2.0.3-alpha. Fixes bug 2510.
12227 - If you configure Tor to use bridge A, and then quit and
12228 configure Tor to use bridge B instead (or if you change Tor
12229 to use bridge B via the controller), it would happily continue
12230 to use bridge A if it's still reachable. While this behavior is
12231 a feature if your goal is connectivity, in some scenarios it's a
12232 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
12233 - When the controller configures a new bridge, don't wait 10 to 60
12234 seconds before trying to fetch its descriptor. Bugfix on
12235 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
12237 o Major bugfixes (directory authorities):
12238 - Many relays have been falling out of the consensus lately because
12239 not enough authorities know about their descriptor for them to get
12240 a majority of votes. When we deprecated the v2 directory protocol,
12241 we got rid of the only way that v3 authorities can hear from each
12242 other about other descriptors. Now authorities examine every v3
12243 vote for new descriptors, and fetch them from that authority. Bugfix
12245 - Authorities could be tricked into giving out the Exit flag to relays
12246 that didn't allow exiting to any ports. This bug could screw
12247 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
12248 1238. Bug discovered by Martin Kowalczyk.
12249 - If all authorities restart at once right before a consensus vote,
12250 nobody will vote about "Running", and clients will get a consensus
12251 with no usable relays. Instead, authorities refuse to build a
12252 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
12254 o Major bugfixes (stream-level fairness):
12255 - When receiving a circuit-level SENDME for a blocked circuit, try
12256 to package cells fairly from all the streams that had previously
12257 been blocked on that circuit. Previously, we had started with the
12258 oldest stream, and allowed each stream to potentially exhaust
12259 the circuit's package window. This gave older streams on any
12260 given circuit priority over newer ones. Fixes bug 1937. Detected
12261 originally by Camilo Viecco. This bug was introduced before the
12262 first Tor release, in svn commit r152: it is the new winner of
12263 the longest-lived bug prize.
12264 - Fix a stream fairness bug that would cause newer streams on a given
12265 circuit to get preference when reading bytes from the origin or
12266 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
12267 introduced before the first Tor release, in svn revision r152.
12268 - When the exit relay got a circuit-level sendme cell, it started
12269 reading on the exit streams, even if had 500 cells queued in the
12270 circuit queue already, so the circuit queue just grew and grew in
12271 some cases. We fix this by not re-enabling reading on receipt of a
12272 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
12273 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
12275 - Newly created streams were allowed to read cells onto circuits,
12276 even if the circuit's cell queue was blocked and waiting to drain.
12277 This created potential unfairness, as older streams would be
12278 blocked, but newer streams would gladly fill the queue completely.
12279 We add code to detect this situation and prevent any stream from
12280 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
12283 o Major bugfixes (hidden services):
12284 - Apply circuit timeouts to opened hidden-service-related circuits
12285 based on the correct start time. Previously, we would apply the
12286 circuit build timeout based on time since the circuit's creation;
12287 it was supposed to be applied based on time since the circuit
12288 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
12289 - Improve hidden service robustness: When we find that we have
12290 extended a hidden service's introduction circuit to a relay not
12291 listed as an introduction point in the HS descriptor we currently
12292 have, retry with an introduction point from the current
12293 descriptor. Previously we would just give up. Fixes bugs 1024 and
12294 1930; bugfix on 0.2.0.10-alpha.
12295 - Directory authorities now use data collected from their own
12296 uptime observations when choosing whether to assign the HSDir flag
12297 to relays, instead of trusting the uptime value the relay reports in
12298 its descriptor. This change helps prevent an attack where a small
12299 set of nodes with frequently-changing identity keys can blackhole
12300 a hidden service. (Only authorities need upgrade; others will be
12301 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
12302 - Stop assigning the HSDir flag to relays that disable their
12303 DirPort (and thus will refuse to answer directory requests). This
12304 fix should dramatically improve the reachability of hidden services:
12305 hidden services and hidden service clients pick six HSDir relays
12306 to store and retrieve the hidden service descriptor, and currently
12307 about half of the HSDir relays will refuse to work. Bugfix on
12308 0.2.0.10-alpha; fixes part of bug 1693.
12310 o Major bugfixes (misc):
12311 - Clients now stop trying to use an exit node associated with a given
12312 destination by TrackHostExits if they fail to reach that exit node.
12313 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
12314 - Fix a regression that caused Tor to rebind its ports if it receives
12315 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
12316 - Remove an extra pair of quotation marks around the error
12317 message in control-port STATUS_GENERAL BUG events. Bugfix on
12318 0.1.2.6-alpha; fixes bug 3732.
12320 o Minor features (relays):
12321 - Ensure that no empty [dirreq-](read|write)-history lines are added
12322 to an extrainfo document. Implements ticket 2497.
12323 - When bandwidth accounting is enabled, be more generous with how
12324 much bandwidth we'll use up before entering "soft hibernation".
12325 Previously, we'd refuse new connections and circuits once we'd
12326 used up 95% of our allotment. Now, we use up 95% of our allotment,
12327 AND make sure that we have no more than 500MB (or 3 hours of
12328 expected traffic, whichever is lower) remaining before we enter
12330 - Relays now log the reason for publishing a new relay descriptor,
12331 so we have a better chance of hunting down instances of bug 1810.
12332 Resolves ticket 3252.
12333 - Log a little more clearly about the times at which we're no longer
12334 accepting new connections (e.g. due to hibernating). Resolves
12336 - When AllowSingleHopExits is set, print a warning to explain to the
12337 relay operator why most clients are avoiding her relay.
12338 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
12339 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
12340 clients are already deprecated because of security bugs.
12342 o Minor features (network statistics):
12343 - Directory mirrors that set "DirReqStatistics 1" write statistics
12344 about directory requests to disk every 24 hours. As compared to the
12345 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
12346 improvements: 1) stats are written to disk exactly every 24 hours;
12347 2) estimated shares of v2 and v3 requests are determined as mean
12348 values, not at the end of a measurement period; 3) unresolved
12349 requests are listed with country code '??'; 4) directories also
12350 measure download times.
12351 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
12352 number of exit streams and transferred bytes per port to disk every
12354 - Relays that set "CellStatistics 1" write statistics on how long
12355 cells spend in their circuit queues to disk every 24 hours.
12356 - Entry nodes that set "EntryStatistics 1" write statistics on the
12357 rough number and origins of connecting clients to disk every 24
12359 - Relays that write any of the above statistics to disk and set
12360 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
12361 their extra-info documents. Implements proposal 166.
12363 o Minor features (GeoIP and statistics):
12364 - Provide a log message stating which geoip file we're parsing
12365 instead of just stating that we're parsing the geoip file.
12366 Implements ticket 2432.
12367 - Make sure every relay writes a state file at least every 12 hours.
12368 Previously, a relay could go for weeks without writing its state
12369 file, and on a crash could lose its bandwidth history, capacity
12370 estimates, client country statistics, and so on. Addresses bug 3012.
12371 - Relays report the number of bytes spent on answering directory
12372 requests in extra-info descriptors similar to {read,write}-history.
12373 Implements enhancement 1790.
12374 - Report only the top 10 ports in exit-port stats in order not to
12375 exceed the maximum extra-info descriptor length of 50 KB. Implements
12377 - If writing the state file to disk fails, wait up to an hour before
12378 retrying again, rather than trying again each second. Fixes bug
12379 2346; bugfix on Tor 0.1.1.3-alpha.
12380 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
12381 when we switch from being a public relay to a bridge. Otherwise
12382 there will still be clients that see the relay in their consensus,
12383 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
12385 - Update to the August 2 2011 Maxmind GeoLite Country database.
12387 o Minor features (clients):
12388 - When expiring circuits, use microsecond timers rather than
12389 one-second timers. This can avoid an unpleasant situation where a
12390 circuit is launched near the end of one second and expired right
12391 near the beginning of the next, and prevent fluctuations in circuit
12393 - If we've configured EntryNodes and our network goes away and/or all
12394 our entrynodes get marked down, optimistically retry them all when
12395 a new socks application request appears. Fixes bug 1882.
12396 - Always perform router selections using weighted relay bandwidth,
12397 even if we don't need a high capacity circuit at the time. Non-fast
12398 circuits now only differ from fast ones in that they can use relays
12399 not marked with the Fast flag. This "feature" could turn out to
12400 be a horrible bug; we should investigate more before it goes into
12402 - When we run out of directory information such that we can't build
12403 circuits, but then get enough that we can build circuits, log when
12404 we actually construct a circuit, so the user has a better chance of
12405 knowing what's going on. Fixes bug 1362.
12406 - Log SSL state transitions at debug level during handshake, and
12407 include SSL states in error messages. This may help debug future
12408 SSL handshake issues.
12410 o Minor features (directory authorities):
12411 - When a router changes IP address or port, authorities now launch
12412 a new reachability test for it. Implements ticket 1899.
12413 - Directory authorities now reject relays running any versions of
12414 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
12415 known bugs that keep RELAY_EARLY cells from working on rendezvous
12416 circuits. Followup to fix for bug 2081.
12417 - Directory authorities now reject relays running any version of Tor
12418 older than 0.2.0.26-rc. That version is the earliest that fetches
12419 current directory information correctly. Fixes bug 2156.
12420 - Directory authorities now do an immediate reachability check as soon
12421 as they hear about a new relay. This change should slightly reduce
12422 the time between setting up a relay and getting listed as running
12423 in the consensus. It should also improve the time between setting
12424 up a bridge and seeing use by bridge users.
12425 - Directory authorities no longer launch a TLS connection to every
12426 relay as they startup. Now that we have 2k+ descriptors cached,
12427 the resulting network hiccup is becoming a burden. Besides,
12428 authorities already avoid voting about Running for the first half
12429 hour of their uptime.
12430 - Directory authorities now log the source of a rejected POSTed v3
12431 networkstatus vote, so we can track failures better.
12432 - Backport code from 0.2.3.x that allows directory authorities to
12433 clean their microdescriptor caches. Needed to resolve bug 2230.
12435 o Minor features (hidden services):
12436 - Use computed circuit-build timeouts to decide when to launch
12437 parallel introduction circuits for hidden services. (Previously,
12438 we would retry after 15 seconds.)
12439 - Don't allow v0 hidden service authorities to act as clients.
12440 Required by fix for bug 3000.
12441 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
12442 by fix for bug 3000.
12443 - Make hidden services work better in private Tor networks by not
12444 requiring any uptime to join the hidden service descriptor
12445 DHT. Implements ticket 2088.
12446 - Log (at info level) when purging pieces of hidden-service-client
12447 state because of SIGNAL NEWNYM.
12449 o Minor features (controller interface):
12450 - New "GETINFO net/listeners/(type)" controller command to return
12451 a list of addresses and ports that are bound for listeners for a
12452 given connection type. This is useful when the user has configured
12453 "SocksPort auto" and the controller needs to know which port got
12454 chosen. Resolves another part of ticket 3076.
12455 - Have the controller interface give a more useful message than
12456 "Internal Error" in response to failed GETINFO requests.
12457 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
12458 event, to give information on the current rate of circuit timeouts
12459 over our stored history.
12460 - The 'EXTENDCIRCUIT' control port command can now be used with
12461 a circ id of 0 and no path. This feature will cause Tor to build
12462 a new 'fast' general purpose circuit using its own path selection
12464 - Added a BUILDTIMEOUT_SET controller event to describe changes
12465 to the circuit build timeout.
12466 - New controller command "getinfo config-text". It returns the
12467 contents that Tor would write if you send it a SAVECONF command,
12468 so the controller can write the file to disk itself.
12470 o Minor features (controller protocol):
12471 - Add a new ControlSocketsGroupWritable configuration option: when
12472 it is turned on, ControlSockets are group-writeable by the default
12473 group of the current user. Patch by Jérémy Bobbio; implements
12475 - Tor now refuses to create a ControlSocket in a directory that is
12476 world-readable (or group-readable if ControlSocketsGroupWritable
12477 is 0). This is necessary because some operating systems do not
12478 enforce permissions on an AF_UNIX sockets. Permissions on the
12479 directory holding the socket, however, seems to work everywhere.
12480 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
12481 not. This would lead to a cookie that is still not group readable.
12482 Closes bug 1843. Suggested by katmagic.
12483 - Future-proof the controller protocol a bit by ignoring keyword
12484 arguments we do not recognize.
12486 o Minor features (more useful logging):
12487 - Revise most log messages that refer to nodes by nickname to
12488 instead use the "$key=nickname at address" format. This should be
12489 more useful, especially since nicknames are less and less likely
12490 to be unique. Resolves ticket 3045.
12491 - When an HTTPS proxy reports "403 Forbidden", we now explain
12492 what it means rather than calling it an unexpected status code.
12493 Closes bug 2503. Patch from Michael Yakubovich.
12494 - Rate-limit a warning about failures to download v2 networkstatus
12495 documents. Resolves part of bug 1352.
12496 - Rate-limit the "your application is giving Tor only an IP address"
12497 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
12498 - Rate-limit "Failed to hand off onionskin" warnings.
12499 - When logging a rate-limited warning, we now mention how many messages
12500 got suppressed since the last warning.
12501 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
12502 2 no signature, 4 required" messages about consensus signatures
12503 easier to read, and make sure they get logged at the same severity
12504 as the messages explaining which keys are which. Fixes bug 1290.
12505 - Don't warn when we have a consensus that we can't verify because
12506 of missing certificates, unless those certificates are ones
12507 that we have been trying and failing to download. Fixes bug 1145.
12509 o Minor features (log domains):
12510 - Add documentation for configuring logging at different severities in
12511 different log domains. We've had this feature since 0.2.1.1-alpha,
12512 but for some reason it never made it into the manpage. Fixes
12514 - Make it simpler to specify "All log domains except for A and B".
12515 Previously you needed to say "[*,~A,~B]". Now you can just say
12517 - Add a "LogMessageDomains 1" option to include the domains of log
12518 messages along with the messages. Without this, there's no way
12519 to use log domains without reading the source or doing a lot
12521 - Add a new "Handshake" log domain for activities that happen
12522 during the TLS handshake.
12524 o Minor features (build process):
12525 - Make compilation with clang possible when using
12526 "--enable-gcc-warnings" by removing two warning options that clang
12527 hasn't implemented yet and by fixing a few warnings. Resolves
12529 - Detect platforms that brokenly use a signed size_t, and refuse to
12530 build there. Found and analyzed by doorss and rransom.
12531 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
12533 - Add support for statically linking zlib by specifying
12534 "--enable-static-zlib", to go with our support for statically
12535 linking openssl and libevent. Resolves bug 1358.
12536 - Instead of adding the svn revision to the Tor version string, report
12537 the git commit (when we're building from a git checkout).
12538 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
12540 - New --digests command-line switch to output the digests of the
12541 source files Tor was built with.
12542 - Generate our manpage and HTML documentation using Asciidoc. This
12543 change should make it easier to maintain the documentation, and
12544 produce nicer HTML. The build process fails if asciidoc cannot
12545 be found and building with asciidoc isn't disabled (via the
12546 "--disable-asciidoc" argument to ./configure. Skipping the manpage
12547 speeds up the build considerably.
12549 o Minor features (options / torrc):
12550 - Warn when the same option is provided more than once in a torrc
12551 file, on the command line, or in a single SETCONF statement, and
12552 the option is one that only accepts a single line. Closes bug 1384.
12553 - Warn when the user configures two HiddenServiceDir lines that point
12554 to the same directory. Bugfix on 0.0.6 (the version introducing
12555 HiddenServiceDir); fixes bug 3289.
12556 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
12557 do individual connection-level rate limiting of clients. The torrc
12558 config options with the same names trump the consensus params, if
12559 both are present. Replaces the old "bwconnrate" and "bwconnburst"
12560 consensus params which were broken from 0.2.2.7-alpha through
12561 0.2.2.14-alpha. Closes bug 1947.
12562 - New config option "WarnUnsafeSocks 0" disables the warning that
12563 occurs whenever Tor receives a socks handshake using a version of
12564 the socks protocol that can only provide an IP address (rather
12565 than a hostname). Setups that do DNS locally over Tor are fine,
12566 and we shouldn't spam the logs in that case.
12567 - New config option "CircuitStreamTimeout" to override our internal
12568 timeout schedule for how many seconds until we detach a stream from
12569 a circuit and try a new circuit. If your network is particularly
12570 slow, you might want to set this to a number like 60.
12571 - New options for SafeLogging to allow scrubbing only log messages
12572 generated while acting as a relay. Specify "SafeLogging relay" if
12573 you want to ensure that only messages known to originate from
12574 client use of the Tor process will be logged unsafely.
12575 - Time and memory units in the configuration file can now be set to
12576 fractional units. For example, "2.5 GB" is now a valid value for
12578 - Support line continuations in the torrc config file. If a line
12579 ends with a single backslash character, the newline is ignored, and
12580 the configuration value is treated as continuing on the next line.
12583 o Minor features (unit tests):
12584 - Revise our unit tests to use the "tinytest" framework, so we
12585 can run tests in their own processes, have smarter setup/teardown
12586 code, and so on. The unit test code has moved to its own
12587 subdirectory, and has been split into multiple modules.
12588 - Add a unit test for cross-platform directory-listing code.
12589 - Add some forgotten return value checks during unit tests. Found
12591 - Use GetTempDir to find the proper temporary directory location on
12592 Windows when generating temporary files for the unit tests. Patch
12595 o Minor features (misc):
12596 - The "torify" script now uses torsocks where available.
12597 - Make Libevent log messages get delivered to controllers later,
12598 and not from inside the Libevent log handler. This prevents unsafe
12599 reentrant Libevent calls while still letting the log messages
12601 - Certain Tor clients (such as those behind check.torproject.org) may
12602 want to fetch the consensus in an extra early manner. To enable this
12603 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12604 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12605 as only certain clients who must have this information sooner should
12607 - Expand homedirs passed to tor-checkkey. This should silence a
12608 coverity complaint about passing a user-supplied string into
12609 open() without checking it.
12610 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
12611 used on bridges, and it makes bridge scanning somewhat easier.
12612 - Create the /var/run/tor directory on startup on OpenSUSE if it is
12613 not already created. Patch from Andreas Stieger. Fixes bug 2573.
12615 o Minor bugfixes (relays):
12616 - When a relay decides that its DNS is too broken for it to serve
12617 as an exit server, it advertised itself as a non-exit, but
12618 continued to act as an exit. This could create accidental
12619 partitioning opportunities for users. Instead, if a relay is
12620 going to advertise reject *:* as its exit policy, it should
12621 really act with exit policy "reject *:*". Fixes bug 2366.
12622 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
12623 - Publish a router descriptor even if generating an extra-info
12624 descriptor fails. Previously we would not publish a router
12625 descriptor without an extra-info descriptor; this can cause fast
12626 exit relays collecting exit-port statistics to drop from the
12627 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
12628 - When we're trying to guess whether we know our IP address as
12629 a relay, we would log various ways that we failed to guess
12630 our address, but never log that we ended up guessing it
12631 successfully. Now add a log line to help confused and anxious
12632 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
12633 - For bandwidth accounting, calculate our expected bandwidth rate
12634 based on the time during which we were active and not in
12635 soft-hibernation during the last interval. Previously, we were
12636 also considering the time spent in soft-hibernation. If this
12637 was a long time, we would wind up underestimating our bandwidth
12638 by a lot, and skewing our wakeup time towards the start of the
12639 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
12640 - Demote a confusing TLS warning that relay operators might get when
12641 someone tries to talk to their ORPort. It is not the operator's
12642 fault, nor can they do anything about it. Fixes bug 1364; bugfix
12644 - Change "Application request when we're believed to be offline."
12645 notice to "Application request when we haven't used client
12646 functionality lately.", to clarify that it's not an error. Bugfix
12647 on 0.0.9.3; fixes bug 1222.
12649 o Minor bugfixes (bridges):
12650 - When a client starts or stops using bridges, never use a circuit
12651 that was built before the configuration change. This behavior could
12652 put at risk a user who uses bridges to ensure that her traffic
12653 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
12655 - Do not reset the bridge descriptor download status every time we
12656 re-parse our configuration or get a configuration change. Fixes
12657 bug 3019; bugfix on 0.2.0.3-alpha.
12658 - Users couldn't configure a regular relay to be their bridge. It
12659 didn't work because when Tor fetched the bridge descriptor, it found
12660 that it already had it, and didn't realize that the purpose of the
12661 descriptor had changed. Now we replace routers with a purpose other
12662 than bridge with bridge descriptors when fetching them. Bugfix on
12663 0.1.1.9-alpha. Fixes bug 1776.
12664 - In the special case where you configure a public exit relay as your
12665 bridge, Tor would be willing to use that exit relay as the last
12666 hop in your circuit as well. Now we fail that circuit instead.
12667 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
12669 o Minor bugfixes (clients):
12670 - We now ask the other side of a stream (the client or the exit)
12671 for more data on that stream when the amount of queued data on
12672 that stream dips low enough. Previously, we wouldn't ask the
12673 other side for more data until either it sent us more data (which
12674 it wasn't supposed to do if it had exhausted its window!) or we
12675 had completely flushed all our queued data. This flow control fix
12676 should improve throughput. Fixes bug 2756; bugfix on the earliest
12677 released versions of Tor (svn commit r152).
12678 - When a client finds that an origin circuit has run out of 16-bit
12679 stream IDs, we now mark it as unusable for new streams. Previously,
12680 we would try to close the entire circuit. Bugfix on 0.0.6.
12681 - Make it explicit that we don't cannibalize one-hop circuits. This
12682 happens in the wild, but doesn't turn out to be a problem because
12683 we fortunately don't use those circuits. Many thanks to outofwords
12684 for the initial analysis and to swissknife who confirmed that
12685 two-hop circuits are actually created.
12686 - Resolve an edge case in path weighting that could make us misweight
12687 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
12688 - Make the DNSPort option work with libevent 2.x. Don't alter the
12689 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
12691 o Minor bugfixes (directory authorities):
12692 - Make directory authorities more accurate at recording when
12693 relays that have failed several reachability tests became
12694 unreachable, so we can provide more accuracy at assigning Stable,
12695 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
12696 - Directory authorities are now more robust to hops back in time
12697 when calculating router stability. Previously, if a run of uptime
12698 or downtime appeared to be negative, the calculation could give
12699 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
12701 - Directory authorities will now attempt to download consensuses
12702 if their own efforts to make a live consensus have failed. This
12703 change means authorities that restart will fetch a valid
12704 consensus, and it means authorities that didn't agree with the
12705 current consensus will still fetch and serve it if it has enough
12706 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
12707 - Never vote for a server as "Running" if we have a descriptor for
12708 it claiming to be hibernating, and that descriptor was published
12709 more recently than our last contact with the server. Bugfix on
12710 0.2.0.3-alpha; fixes bug 911.
12711 - Directory authorities no longer change their opinion of, or vote on,
12712 whether a router is Running, unless they have themselves been
12713 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12716 o Minor bugfixes (hidden services):
12717 - Log malformed requests for rendezvous descriptors as protocol
12718 warnings, not warnings. Also, use a more informative log message
12719 in case someone sees it at log level warning without prior
12720 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
12721 - Accept hidden service descriptors if we think we might be a hidden
12722 service directory, regardless of what our consensus says. This
12723 helps robustness, since clients and hidden services can sometimes
12724 have a more up-to-date view of the network consensus than we do,
12725 and if they think that the directory authorities list us a HSDir,
12726 we might actually be one. Related to bug 2732; bugfix on
12728 - Correct the warning displayed when a rendezvous descriptor exceeds
12729 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12731 - Clients and hidden services now use HSDir-flagged relays for hidden
12732 service descriptor downloads and uploads even if the relays have no
12733 DirPort set and the client has disabled TunnelDirConns. This will
12734 eventually allow us to give the HSDir flag to relays with no
12735 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
12736 - Only limit the lengths of single HS descriptors, even when multiple
12737 HS descriptors are published to an HSDir relay in a single POST
12738 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
12740 o Minor bugfixes (controllers):
12741 - Allow GETINFO fingerprint to return a fingerprint even when
12742 we have not yet built a router descriptor. Fixes bug 3577;
12743 bugfix on 0.2.0.1-alpha.
12744 - Send a SUCCEEDED stream event to the controller when a reverse
12745 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
12746 discovered by katmagic.
12747 - Remove a trailing asterisk from "exit-policy/default" in the
12748 output of the control port command "GETINFO info/names". Bugfix
12750 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
12751 2917. Bugfix on 0.1.1.1-alpha.
12752 - When we restart our relay, we might get a successful connection
12753 from the outside before we've started our reachability tests,
12754 triggering a warning: "ORPort found reachable, but I have no
12755 routerinfo yet. Failing to inform controller of success." This
12756 bug was harmless unless Tor is running under a controller
12757 like Vidalia, in which case the controller would never get a
12758 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12760 - When a controller changes TrackHostExits, remove mappings for
12761 hosts that should no longer have their exits tracked. Bugfix on
12763 - When a controller changes VirtualAddrNetwork, remove any mappings
12764 for hosts that were automapped to the old network. Bugfix on
12766 - When a controller changes one of the AutomapHosts* options, remove
12767 any mappings for hosts that should no longer be automapped. Bugfix
12769 - Fix an off-by-one error in calculating some controller command
12770 argument lengths. Fortunately, this mistake is harmless since
12771 the controller code does redundant NUL termination too. Found by
12772 boboper. Bugfix on 0.1.1.1-alpha.
12773 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
12774 would return "551 Internal error" rather than "552 Unrecognized key
12775 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
12776 - Don't spam the controller with events when we have no file
12777 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
12778 for log messages was already solved from bug 748.)
12779 - Emit a GUARD DROPPED controller event for a case we missed.
12780 - Ensure DNS requests launched by "RESOLVE" commands from the
12781 controller respect the __LeaveStreamsUnattached setconf options. The
12782 same goes for requests launched via DNSPort or transparent
12783 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
12785 o Minor bugfixes (config options):
12786 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
12787 Change the limit to 512 characters by removing base64 newlines.
12788 Fixes bug 2752. Fix by Michael Yakubovich.
12789 - Complain if PublishServerDescriptor is given multiple arguments that
12790 include 0 or 1. This configuration will be rejected in the future.
12791 Bugfix on 0.2.0.1-alpha; closes bug 1107.
12792 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
12793 Bugfix on 0.2.0.13-alpha; closes bug 928.
12795 o Minor bugfixes (log subsystem fixes):
12796 - When unable to format an address as a string, report its value
12797 as "???" rather than reusing the last formatted address. Bugfix
12799 - Be more consistent in our treatment of file system paths. "~" should
12800 get expanded to the user's home directory in the Log config option.
12801 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
12802 feature for the -f and --DataDirectory options.
12804 o Minor bugfixes (memory management):
12805 - Don't stack-allocate the list of supplementary GIDs when we're
12806 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12807 could take up to 256K, which is way too much stack. Found by
12808 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12809 - Save a couple bytes in memory allocation every time we escape
12810 certain characters in a string. Patch from Florian Zumbiehl.
12812 o Minor bugfixes (protocol correctness):
12813 - When checking for 1024-bit keys, check for 1024 bits, not 128
12814 bytes. This allows Tor to correctly discard keys of length 1017
12815 through 1023. Bugfix on 0.0.9pre5.
12816 - Require that introduction point keys and onion handshake keys
12817 have a public exponent of 65537. Starts to fix bug 3207; bugfix
12819 - Handle SOCKS messages longer than 128 bytes long correctly, rather
12820 than waiting forever for them to finish. Fixes bug 2330; bugfix
12821 on 0.2.0.16-alpha. Found by doorss.
12822 - Never relay a cell for a circuit we have already destroyed.
12823 Between marking a circuit as closeable and finally closing it,
12824 it may have been possible for a few queued cells to get relayed,
12825 even though they would have been immediately dropped by the next
12826 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
12827 - Never queue a cell for a circuit that's already been marked
12829 - Fix a spec conformance issue: the network-status-version token
12830 must be the first token in a v3 consensus or vote. Discovered by
12831 "parakeep". Bugfix on 0.2.0.3-alpha.
12832 - A networkstatus vote must contain exactly one signature. Spec
12833 conformance issue. Bugfix on 0.2.0.3-alpha.
12834 - When asked about a DNS record type we don't support via a
12835 client DNSPort, reply with NOTIMPL rather than an empty
12836 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
12837 - Make more fields in the controller protocol case-insensitive, since
12838 control-spec.txt said they were.
12840 o Minor bugfixes (log messages):
12841 - Fix a log message that said "bits" while displaying a value in
12842 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
12844 - Downgrade "no current certificates known for authority" message from
12845 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
12846 - Correctly describe errors that occur when generating a TLS object.
12847 Previously we would attribute them to a failure while generating a
12848 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
12850 - Fix an instance where a Tor directory mirror might accidentally
12851 log the IP address of a misbehaving Tor client. Bugfix on
12853 - Stop logging at severity 'warn' when some other Tor client tries
12854 to establish a circuit with us using weak DH keys. It's a protocol
12855 violation, but that doesn't mean ordinary users need to hear about
12856 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
12857 - If your relay can't keep up with the number of incoming create
12858 cells, it would log one warning per failure into your logs. Limit
12859 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
12861 o Minor bugfixes (build fixes):
12862 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12863 - When warning about missing zlib development packages during compile,
12864 give the correct package names. Bugfix on 0.2.0.1-alpha.
12865 - Fix warnings that newer versions of autoconf produce during
12866 ./autogen.sh. These warnings appear to be harmless in our case,
12867 but they were extremely verbose. Fixes bug 2020.
12868 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
12871 o Minor bugfixes (portability):
12872 - Write several files in text mode, on OSes that distinguish text
12873 mode from binary mode (namely, Windows). These files are:
12874 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
12875 that collect those statistics; 'client_keys' and 'hostname' for
12876 hidden services that use authentication; and (in the tor-gencert
12877 utility) newly generated identity and signing keys. Previously,
12878 we wouldn't specify text mode or binary mode, leading to an
12879 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
12880 the DirRecordUsageByCountry option which would have triggered
12881 the assertion failure was added), although this assertion failure
12882 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
12883 - Selectively disable deprecation warnings on OS X because Lion
12884 started deprecating the shipped copy of openssl. Fixes bug 3643.
12885 - Use a wide type to hold sockets when built for 64-bit Windows.
12887 - Fix an issue that prevented static linking of libevent on
12888 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
12889 where we introduced the "--with-static-libevent" configure option.
12890 - Fix a bug with our locking implementation on Windows that couldn't
12891 correctly detect when a file was already locked. Fixes bug 2504,
12892 bugfix on 0.2.1.6-alpha.
12893 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
12895 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
12896 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
12899 o Minor bugfixes (code correctness):
12900 - Always NUL-terminate the sun_path field of a sockaddr_un before
12901 passing it to the kernel. (Not a security issue: kernels are
12902 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12903 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12904 - Make connection_printf_to_buf()'s behavior sane. Its callers
12905 expect it to emit a CRLF iff the format string ends with CRLF;
12906 it actually emitted a CRLF iff (a) the format string ended with
12907 CRLF or (b) the resulting string was over 1023 characters long or
12908 (c) the format string did not end with CRLF *and* the resulting
12909 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
12910 fixes part of bug 3407.
12911 - Make send_control_event_impl()'s behavior sane. Its callers
12912 expect it to always emit a CRLF at the end of the string; it
12913 might have emitted extra control characters as well. Bugfix on
12914 0.1.1.9-alpha; fixes another part of bug 3407.
12915 - Make crypto_rand_int() check the value of its input correctly.
12916 Previously, it accepted values up to UINT_MAX, but could return a
12917 negative number if given a value above INT_MAX+1. Found by George
12918 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
12919 - Fix a potential null-pointer dereference while computing a
12920 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
12922 - If we fail to compute the identity digest of a v3 legacy keypair,
12923 warn, and don't use a buffer-full of junk instead. Bugfix on
12924 0.2.1.1-alpha; fixes bug 3106.
12925 - Resolve an untriggerable issue in smartlist_string_num_isin(),
12926 where if the function had ever in the future been used to check
12927 for the presence of a too-large number, it would have given an
12928 incorrect result. (Fortunately, we only used it for 16-bit
12929 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
12930 - Be more careful about reporting the correct error from a failed
12931 connect() system call. Under some circumstances, it was possible to
12932 look at an incorrect value for errno when sending the end reason.
12933 Bugfix on 0.1.0.1-rc.
12934 - Correctly handle an "impossible" overflow cases in connection byte
12935 counting, where we write or read more than 4GB on an edge connection
12936 in a single second. Bugfix on 0.1.2.8-beta.
12937 - Avoid a double mark-for-free warning when failing to attach a
12938 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
12940 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
12941 found by "cypherpunks". This bug was introduced before the first
12942 Tor release, in svn commit r110.
12943 - Fix a bug in bandwidth history state parsing that could have been
12944 triggered if a future version of Tor ever changed the timing
12945 granularity at which bandwidth history is measured. Bugfix on
12946 Tor 0.1.1.11-alpha.
12947 - Add assertions to check for overflow in arguments to
12948 base32_encode() and base32_decode(); fix a signed-unsigned
12949 comparison there too. These bugs are not actually reachable in Tor,
12950 but it's good to prevent future errors too. Found by doorss.
12951 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
12953 - Set target port in get_interface_address6() correctly. Bugfix
12954 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
12955 - Fix an impossible-to-actually-trigger buffer overflow in relay
12956 descriptor generation. Bugfix on 0.1.0.15.
12957 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
12959 o Minor bugfixes (code improvements):
12960 - After we free an internal connection structure, overwrite it
12961 with a different memory value than we use for overwriting a freed
12962 internal circuit structure. Should help with debugging. Suggested
12964 - If OpenSSL fails to make a duplicate of a private or public key, log
12965 an error message and try to exit cleanly. May help with debugging
12966 if bug 1209 ever remanifests.
12967 - Some options used different conventions for uppercasing of acronyms
12968 when comparing manpage and source. Fix those in favor of the
12969 manpage, as it makes sense to capitalize acronyms.
12970 - Take a first step towards making or.h smaller by splitting out
12971 function definitions for all source files in src/or/. Leave
12972 structures and defines in or.h for now.
12973 - Remove a few dead assignments during router parsing. Found by
12975 - Don't use 1-bit wide signed bit fields. Found by coverity.
12976 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12977 None of the cases where we did this before were wrong, but by making
12978 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12979 - The memarea code now uses a sentinel value at the end of each area
12980 to make sure nothing writes beyond the end of an area. This might
12981 help debug some conceivable causes of bug 930.
12982 - Always treat failure to allocate an RSA key as an unrecoverable
12984 - Add some more defensive programming for architectures that can't
12985 handle unaligned integer accesses. We don't know of any actual bugs
12986 right now, but that's the best time to fix them. Fixes bug 1943.
12988 o Minor bugfixes (misc):
12989 - Fix a rare bug in rend_fn unit tests: we would fail a test when
12990 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
12991 on 0.2.0.10-alpha; fixes bug 1808.
12992 - Where available, use Libevent 2.0's periodic timers so that our
12993 once-per-second cleanup code gets called even more closely to
12994 once per second than it would otherwise. Fixes bug 943.
12995 - Ignore OutboundBindAddress when connecting to localhost.
12996 Connections to localhost need to come _from_ localhost, or else
12997 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
12999 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
13001 - If any of the v3 certs we download are unparseable, we should
13002 actually notice the failure so we don't retry indefinitely. Bugfix
13003 on 0.2.0.x; reported by "rotator".
13004 - When Tor fails to parse a descriptor of any kind, dump it to disk.
13005 Might help diagnosing bug 1051.
13006 - Make our 'torify' script more portable; if we have only one of
13007 'torsocks' or 'tsocks' installed, don't complain to the user;
13008 and explain our warning about tsocks better.
13009 - Fix some urls in the exit notice file and make it XHTML1.1 strict
13010 compliant. Based on a patch from Christian Kujau.
13012 o Documentation changes:
13013 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
13014 - Resolve all doxygen warnings except those for missing documentation.
13016 - Add doxygen documentation for more functions, fields, and types.
13017 - Convert the HACKING file to asciidoc, and add a few new sections
13018 to it, explaining how we use Git, how we make changelogs, and
13019 what should go in a patch.
13020 - Document the default socks host and port (127.0.0.1:9050) for
13022 - Removed some unnecessary files from the source distribution. The
13023 AUTHORS file has now been merged into the people page on the
13024 website. The roadmaps and design doc can now be found in the
13025 projects directory in svn.
13027 o Deprecated and removed features (config):
13028 - Remove the torrc.complete file. It hasn't been kept up to date
13029 and users will have better luck checking out the manpage.
13030 - Remove the HSAuthorityRecordStats option that version 0 hidden
13031 service authorities could use to track statistics of overall v0
13032 hidden service usage.
13033 - Remove the obsolete "NoPublish" option; it has been flagged
13034 as obsolete and has produced a warning since 0.1.1.18-rc.
13035 - Caches no longer download and serve v2 networkstatus documents
13036 unless FetchV2Networkstatus flag is set: these documents haven't
13037 haven't been used by clients or relays since 0.2.0.x. Resolves
13040 o Deprecated and removed features (controller):
13041 - The controller no longer accepts the old obsolete "addr-mappings/"
13042 or "unregistered-servers-" GETINFO values.
13043 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
13044 always on; using them is necessary for correct forward-compatible
13047 o Deprecated and removed features (misc):
13048 - Hidden services no longer publish version 0 descriptors, and clients
13049 do not request or use version 0 descriptors. However, the old hidden
13050 service authorities still accept and serve version 0 descriptors
13051 when contacted by older hidden services/clients.
13052 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13053 anything since 0.2.1.16-rc.
13054 - Remove everything related to building the expert bundle for OS X.
13055 It has confused many users, doesn't work right on OS X 10.6,
13056 and is hard to get rid of once installed. Resolves bug 1274.
13057 - Remove support for .noconnect style addresses. Nobody was using
13058 them, and they provided another avenue for detecting Tor users
13059 via application-level web tricks.
13060 - When we fixed bug 1038 we had to put in a restriction not to send
13061 RELAY_EARLY cells on rend circuits. This was necessary as long
13062 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
13063 active. Now remove this obsolete check. Resolves bug 2081.
13064 - Remove workaround code to handle directory responses from servers
13065 that had bug 539 (they would send HTTP status 503 responses _and_
13066 send a body too). Since only server versions before
13067 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
13068 keep the workaround in place.
13069 - Remove the old 'fuzzy time' logic. It was supposed to be used for
13070 handling calculations where we have a known amount of clock skew and
13071 an allowed amount of unknown skew. But we only used it in three
13072 places, and we never adjusted the known/unknown skew values. This is
13073 still something we might want to do someday, but if we do, we'll
13074 want to do it differently.
13075 - Remove the "--enable-iphone" option to ./configure. According to
13076 reports from Marco Bonetti, Tor builds fine without any special
13077 tweaking on recent iPhone SDK versions.
13080 Changes in version 0.2.1.30 - 2011-02-23
13081 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
13082 change is a slight tweak to Tor's TLS handshake that makes relays
13083 and bridges that run this new version reachable from Iran again.
13084 We don't expect this tweak will win the arms race long-term, but it
13085 buys us time until we roll out a better solution.
13088 - Stop sending a CLOCK_SKEW controller status event whenever
13089 we fetch directory information from a relay that has a wrong clock.
13090 Instead, only inform the controller when it's a trusted authority
13091 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
13092 the rest of bug 1074.
13093 - Fix a bounds-checking error that could allow an attacker to
13094 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
13095 Found by "piebeer".
13096 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
13097 Tor would ignore their RelayBandwidthBurst setting,
13098 potentially using more bandwidth than expected. Bugfix on
13099 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
13100 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
13101 hidserv" in her torrc. The 'hidserv' argument never controlled
13102 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
13105 - Adjust our TLS Diffie-Hellman parameters to match those used by
13107 - Update to the February 1 2011 Maxmind GeoLite Country database.
13110 - Check for and reject overly long directory certificates and
13111 directory tokens before they have a chance to hit any assertions.
13112 Bugfix on 0.2.1.28. Found by "doorss".
13113 - Bring the logic that gathers routerinfos and assesses the
13114 acceptability of circuits into line. This prevents a Tor OP from
13115 getting locked in a cycle of choosing its local OR as an exit for a
13116 path (due to a .exit request) and then rejecting the circuit because
13117 its OR is not listed yet. It also prevents Tor clients from using an
13118 OR running in the same instance as an exit (due to a .exit request)
13119 if the OR does not meet the same requirements expected of an OR
13120 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
13122 o Packaging changes:
13123 - Stop shipping the Tor specs files and development proposal documents
13124 in the tarball. They are now in a separate git repository at
13125 git://git.torproject.org/torspec.git
13126 - Do not include Git version tags as though they are SVN tags when
13127 generating a tarball from inside a repository that has switched
13128 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
13131 Changes in version 0.2.1.29 - 2011-01-15
13132 Tor 0.2.1.29 continues our recent code security audit work. The main
13133 fix resolves a remote heap overflow vulnerability that can allow remote
13134 code execution. Other fixes address a variety of assert and crash bugs,
13135 most of which we think are hard to exploit remotely.
13137 o Major bugfixes (security):
13138 - Fix a heap overflow bug where an adversary could cause heap
13139 corruption. This bug probably allows remote code execution
13140 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
13142 - Prevent a denial-of-service attack by disallowing any
13143 zlib-compressed data whose compression factor is implausibly
13144 high. Fixes part of bug 2324; reported by "doorss".
13145 - Zero out a few more keys in memory before freeing them. Fixes
13146 bug 2384 and part of bug 2385. These key instances found by
13147 "cypherpunks", based on Andrew Case's report about being able
13148 to find sensitive data in Tor's memory space if you have enough
13149 permissions. Bugfix on 0.0.2pre9.
13151 o Major bugfixes (crashes):
13152 - Prevent calls to Libevent from inside Libevent log handlers.
13153 This had potential to cause a nasty set of crashes, especially
13154 if running Libevent with debug logging enabled, and running
13155 Tor with a controller watching for low-severity log messages.
13156 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
13157 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
13158 underflow errors there too. Fixes the other part of bug 2324.
13159 - Fix a bug where we would assert if we ever had a
13160 cached-descriptors.new file (or another file read directly into
13161 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
13162 on 0.2.1.25. Found by doorss.
13163 - Fix some potential asserts and parsing issues with grossly
13164 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
13167 o Minor bugfixes (other):
13168 - Fix a bug with handling misformed replies to reverse DNS lookup
13169 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
13170 bug reported by doorss.
13171 - Fix compilation on mingw when a pthreads compatibility library
13172 has been installed. (We don't want to use it, so we shouldn't
13173 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
13174 - Fix a bug where we would declare that we had run out of virtual
13175 addresses when the address space was only half-exhausted. Bugfix
13177 - Correctly handle the case where AutomapHostsOnResolve is set but
13178 no virtual addresses are available. Fixes bug 2328; bugfix on
13179 0.1.2.1-alpha. Bug found by doorss.
13180 - Correctly handle wrapping around when we run out of virtual
13181 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
13184 - Update to the January 1 2011 Maxmind GeoLite Country database.
13185 - Introduce output size checks on all of our decryption functions.
13188 - Tor does not build packages correctly with Automake 1.6 and earlier;
13189 added a check to Makefile.am to make sure that we're building with
13190 Automake 1.7 or later.
13191 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
13192 because we built it with a too-old version of automake. Thus that
13193 release broke ./configure --enable-openbsd-malloc, which is popular
13194 among really fast exit relays on Linux.
13197 Changes in version 0.2.1.28 - 2010-12-17
13198 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
13199 exploitable bugs. We also took this opportunity to change the IP address
13200 for one of our directory authorities, and to update the geoip database
13204 - Fix a remotely exploitable bug that could be used to crash instances
13205 of Tor remotely by overflowing on the heap. Remote-code execution
13206 hasn't been confirmed, but can't be ruled out. Everyone should
13207 upgrade. Bugfix on the 0.1.1 series and later.
13209 o Directory authority changes:
13210 - Change IP address and ports for gabelmoo (v3 directory authority).
13213 - Update to the December 1 2010 Maxmind GeoLite Country database.
13216 Changes in version 0.2.1.27 - 2010-11-23
13217 Yet another OpenSSL security patch broke its compatibility with Tor:
13218 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
13219 also took this opportunity to fix several crash bugs, integrate a new
13220 directory authority, and update the bundled GeoIP database.
13223 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
13224 No longer set the tlsext_host_name extension on server SSL objects;
13225 but continue to set it on client SSL objects. Our goal in setting
13226 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
13227 bugfix on 0.2.1.1-alpha.
13228 - Do not log messages to the controller while shrinking buffer
13229 freelists. Doing so would sometimes make the controller connection
13230 try to allocate a buffer chunk, which would mess up the internals
13231 of the freelist and cause an assertion failure. Fixes bug 1125;
13232 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
13233 - Learn our external IP address when we're a relay or bridge, even if
13234 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
13235 where we introduced bridge relays that don't need to publish to
13236 be useful. Fixes bug 2050.
13237 - Do even more to reject (and not just ignore) annotations on
13238 router descriptors received anywhere but from the cache. Previously
13239 we would ignore such annotations at first, but cache them to disk
13240 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
13241 - When you're using bridges and your network goes away and your
13242 bridges get marked as down, recover when you attempt a new socks
13243 connection (if the network is back), rather than waiting up to an
13244 hour to try fetching new descriptors for your bridges. Bugfix on
13245 0.2.0.3-alpha; fixes bug 1981.
13248 - Move to the November 2010 Maxmind GeoLite country db (rather
13249 than the June 2009 ip-to-country GeoIP db) for our statistics that
13250 count how many users relays are seeing from each country. Now we'll
13251 have more accurate data, especially for many African countries.
13253 o New directory authorities:
13254 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
13258 - Fix an assertion failure that could occur in directory caches or
13259 bridge users when using a very short voting interval on a testing
13260 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
13262 - Enforce multiplicity rules when parsing annotations. Bugfix on
13263 0.2.0.8-alpha. Found by piebeer.
13264 - Allow handshaking OR connections to take a full KeepalivePeriod
13265 seconds to handshake. Previously, we would close them after
13266 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
13267 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
13269 - When building with --enable-gcc-warnings on OpenBSD, disable
13270 warnings in system headers. This makes --enable-gcc-warnings
13271 pass on OpenBSD 4.8.
13274 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
13275 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
13276 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
13277 Servers can start sending this code when enough clients recognize
13278 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
13279 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
13280 Patch from mingw-san.
13283 - Remove the old debian/ directory from the main Tor distribution.
13284 The official Tor-for-debian git repository lives at the URL
13285 https://git.torproject.org/debian/tor.git
13286 - Stop shipping the old doc/website/ directory in the tarball. We
13287 changed the website format in late 2010, and what we shipped in
13288 0.2.1.26 really wasn't that useful anyway.
13291 Changes in version 0.2.1.26 - 2010-05-02
13292 Tor 0.2.1.26 addresses the recent connection and memory overload
13293 problems we've been seeing on relays, especially relays with their
13294 DirPort open. If your relay has been crashing, or you turned it off
13295 because it used too many resources, give this release a try.
13297 This release also fixes yet another instance of broken OpenSSL libraries
13298 that was causing some relays to drop out of the consensus.
13301 - Teach relays to defend themselves from connection overload. Relays
13302 now close idle circuits early if it looks like they were intended
13303 for directory fetches. Relays are also more aggressive about closing
13304 TLS connections that have no circuits on them. Such circuits are
13305 unlikely to be re-used, and tens of thousands of them were piling
13306 up at the fast relays, causing the relays to run out of sockets
13307 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
13308 their directory fetches over TLS).
13309 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
13310 that claim to be earlier than 0.9.8m, but which have in reality
13311 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
13312 behavior. Possible fix for some cases of bug 1346.
13313 - Directory mirrors were fetching relay descriptors only from v2
13314 directory authorities, rather than v3 authorities like they should.
13315 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
13316 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
13319 - Finally get rid of the deprecated and now harmful notion of "clique
13320 mode", where directory authorities maintain TLS connections to
13324 - In the util/threads test, no longer free the test_mutex before all
13325 worker threads have finished. Bugfix on 0.2.1.6-alpha.
13326 - The master thread could starve the worker threads quite badly on
13327 certain systems, causing them to run only partially in the allowed
13328 window. This resulted in test failures. Now the master thread sleeps
13329 occasionally for a few microseconds while the two worker-threads
13330 compete for the mutex. Bugfix on 0.2.0.1-alpha.
13333 Changes in version 0.2.1.25 - 2010-03-16
13334 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
13335 prevent relays from guessing their IP address correctly. It also fixes
13336 several minor potential security bugs.
13339 - Fix a regression from our patch for bug 1244 that caused relays
13340 to guess their IP address incorrectly if they didn't set Address
13341 in their torrc and/or their address fails to resolve. Bugfix on
13342 0.2.1.23; fixes bug 1269.
13343 - When freeing a session key, zero it out completely. We only zeroed
13344 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
13345 patched by ekir. Fixes bug 1254.
13348 - Fix a dereference-then-NULL-check sequence when publishing
13349 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
13351 - Fix another dereference-then-NULL-check sequence. Bugfix on
13352 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
13353 - Make sure we treat potentially not NUL-terminated strings correctly.
13354 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
13357 Changes in version 0.2.1.24 - 2010-02-21
13358 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
13362 - Work correctly out-of-the-box with even more vendor-patched versions
13363 of OpenSSL. In particular, make it so Debian and OS X don't need
13364 customized patches to run/build.
13367 Changes in version 0.2.1.23 - 2010-02-13
13368 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
13369 again on the latest OS X, and updates the location of a directory
13372 o Major bugfixes (performance):
13373 - We were selecting our guards uniformly at random, and then weighting
13374 which of our guards we'd use uniformly at random. This imbalance
13375 meant that Tor clients were severely limited on throughput (and
13376 probably latency too) by the first hop in their circuit. Now we
13377 select guards weighted by currently advertised bandwidth. We also
13378 automatically discard guards picked using the old algorithm. Fixes
13379 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
13382 - Make Tor work again on the latest OS X: when deciding whether to
13383 use strange flags to turn TLS renegotiation on, detect the OpenSSL
13384 version at run-time, not compile time. We need to do this because
13385 Apple doesn't update its dev-tools headers when it updates its
13386 libraries in a security patch.
13387 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
13388 that could happen on 32-bit platforms with 64-bit time_t. Also fix
13389 a memory leak when requesting a hidden service descriptor we've
13390 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
13394 - Refactor resolve_my_address() to not use gethostbyname() anymore.
13395 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
13398 - Avoid a mad rush at the beginning of each month when each client
13399 rotates half of its guards. Instead we spread the rotation out
13400 throughout the month, but we still avoid leaving a precise timestamp
13401 in the state file about when we first picked the guard. Improves
13402 over the behavior introduced in 0.1.2.17.
13405 Changes in version 0.2.1.22 - 2010-01-19
13406 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
13407 authorities -- it would tell you its whole history of bridge descriptors
13408 if you make the right directory request. This stable update also
13409 rotates two of the seven v3 directory authority keys and locations.
13411 o Directory authority changes:
13412 - Rotate keys (both v3 identity and relay identity) for moria1
13416 - Stop bridge directory authorities from answering dbg-stability.txt
13417 directory queries, which would let people fetch a list of all
13418 bridge identities they track. Bugfix on 0.2.1.6-alpha.
13421 Changes in version 0.2.1.21 - 2009-12-21
13422 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
13423 library. If you use Tor on Linux / Unix and you're getting SSL
13424 renegotiation errors, upgrading should help. We also recommend an
13425 upgrade if you're an exit relay.
13428 - Work around a security feature in OpenSSL 0.9.8l that prevents our
13429 handshake from working unless we explicitly tell OpenSSL that we
13430 are using SSL renegotiation safely. We are, of course, but OpenSSL
13431 0.9.8l won't work unless we say we are.
13432 - Avoid crashing if the client is trying to upload many bytes and the
13433 circuit gets torn down at the same time, or if the flip side
13434 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
13437 - Do not refuse to learn about authority certs and v2 networkstatus
13438 documents that are older than the latest consensus. This bug might
13439 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
13440 Spotted and fixed by xmux.
13441 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
13442 trigger platform-specific option misparsing case found by Coverity
13444 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
13445 trigger assert. Fixes bug 1173.
13448 Changes in version 0.2.1.20 - 2009-10-15
13449 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
13450 services at once, prepares for more performance improvements, and
13451 fixes a bunch of smaller bugs.
13453 The Windows and OS X bundles also include a more recent Vidalia,
13454 and switch from Privoxy to Polipo.
13456 The OS X installers are now drag and drop. It's best to un-install
13457 Tor/Vidalia and then install this new bundle, rather than upgrade. If
13458 you want to upgrade, you'll need to update the paths for Tor and Polipo
13459 in the Vidalia Settings window.
13462 - Send circuit or stream sendme cells when our window has decreased
13463 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
13464 by Karsten when testing the "reduce circuit window" performance
13465 patch. Bugfix on the 54th commit on Tor -- from July 2002,
13466 before the release of Tor 0.0.0. This is the new winner of the
13468 - Fix a remotely triggerable memory leak when a consensus document
13469 contains more than one signature from the same voter. Bugfix on
13471 - Avoid segfault in rare cases when finishing an introduction circuit
13472 as a client and finding out that we don't have an introduction key
13473 for it. Fixes bug 1073. Reported by Aaron Swartz.
13476 - Tor now reads the "circwindow" parameter out of the consensus,
13477 and uses that value for its circuit package window rather than the
13478 default of 1000 cells. Begins the implementation of proposal 168.
13480 o New directory authorities:
13481 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
13483 - Move moria1 and tonga to alternate IP addresses.
13486 - Fix a signed/unsigned compile warning in 0.2.1.19.
13487 - Fix possible segmentation fault on directory authorities. Bugfix on
13489 - Fix an extremely rare infinite recursion bug that could occur if
13490 we tried to log a message after shutting down the log subsystem.
13491 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
13492 - Fix an obscure bug where hidden services on 64-bit big-endian
13493 systems might mis-read the timestamp in v3 introduce cells, and
13494 refuse to connect back to the client. Discovered by "rotor".
13495 Bugfix on 0.2.1.6-alpha.
13496 - We were triggering a CLOCK_SKEW controller status event whenever
13497 we connect via the v2 connection protocol to any relay that has
13498 a wrong clock. Instead, we should only inform the controller when
13499 it's a trusted authority that claims our clock is wrong. Bugfix
13500 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
13501 - We were telling the controller about CHECKING_REACHABILITY and
13502 REACHABILITY_FAILED status events whenever we launch a testing
13503 circuit or notice that one has failed. Instead, only tell the
13504 controller when we want to inform the user of overall success or
13505 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
13507 - Don't warn when we're using a circuit that ends with a node
13508 excluded in ExcludeExitNodes, but the circuit is not used to access
13509 the outside world. This should help fix bug 1090. Bugfix on
13511 - Work around a small memory leak in some versions of OpenSSL that
13512 stopped the memory used by the hostname TLS extension from being
13516 - Add a "getinfo status/accepted-server-descriptor" controller
13517 command, which is the recommended way for controllers to learn
13518 whether our server descriptor has been successfully received by at
13519 least on directory authority. Un-recommend good-server-descriptor
13520 getinfo and status events until we have a better design for them.
13523 Changes in version 0.2.1.19 - 2009-07-28
13524 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
13528 - Make accessing hidden services on 0.2.1.x work right again.
13529 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
13530 part of patch provided by "optimist".
13533 - When a relay/bridge is writing out its identity key fingerprint to
13534 the "fingerprint" file and to its logs, write it without spaces. Now
13535 it will look like the fingerprints in our bridges documentation,
13536 and confuse fewer users.
13539 - Relays no longer publish a new server descriptor if they change
13540 their MaxAdvertisedBandwidth config option but it doesn't end up
13541 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
13542 fixes bug 1026. Patch from Sebastian.
13543 - Avoid leaking memory every time we get a create cell but we have
13544 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
13545 fixes bug 1034. Reported by BarkerJr.
13548 Changes in version 0.2.1.18 - 2009-07-24
13549 Tor 0.2.1.18 lays the foundations for performance improvements,
13550 adds status events to help users diagnose bootstrap problems, adds
13551 optional authentication/authorization for hidden services, fixes a
13552 variety of potential anonymity problems, and includes a huge pile of
13553 other features and bug fixes.
13555 o Major features (clients):
13556 - Start sending "bootstrap phase" status events to the controller,
13557 so it can keep the user informed of progress fetching directory
13558 information and establishing circuits. Also inform the controller
13559 if we think we're stuck at a particular bootstrap phase. Implements
13561 - Clients replace entry guards that were chosen more than a few months
13562 ago. This change should significantly improve client performance,
13563 especially once more people upgrade, since relays that have been
13564 a guard for a long time are currently overloaded.
13565 - Network status consensus documents and votes now contain bandwidth
13566 information for each relay. Clients use the bandwidth values
13567 in the consensus, rather than the bandwidth values in each
13568 relay descriptor. This approach opens the door to more accurate
13569 bandwidth estimates once the directory authorities start doing
13570 active measurements. Implements part of proposal 141.
13572 o Major features (relays):
13573 - Disable and refactor some debugging checks that forced a linear scan
13574 over the whole server-side DNS cache. These accounted for over 50%
13575 of CPU time on a relatively busy exit node's gprof profile. Also,
13576 disable some debugging checks that appeared in exit node profile
13577 data. Found by Jacob.
13578 - New DirPortFrontPage option that takes an html file and publishes
13579 it as "/" on the DirPort. Now relay operators can provide a
13580 disclaimer without needing to set up a separate webserver. There's
13581 a sample disclaimer in contrib/tor-exit-notice.html.
13583 o Major features (hidden services):
13584 - Make it possible to build hidden services that only certain clients
13585 are allowed to connect to. This is enforced at several points,
13586 so that unauthorized clients are unable to send INTRODUCE cells
13587 to the service, or even (depending on the type of authentication)
13588 to learn introduction points. This feature raises the bar for
13589 certain kinds of active attacks against hidden services. Design
13590 and code by Karsten Loesing. Implements proposal 121.
13591 - Relays now store and serve v2 hidden service descriptors by default,
13592 i.e., the new default value for HidServDirectoryV2 is 1. This is
13593 the last step in proposal 114, which aims to make hidden service
13594 lookups more reliable.
13596 o Major features (path selection):
13597 - ExitNodes and Exclude*Nodes config options now allow you to restrict
13598 by country code ("{US}") or IP address or address pattern
13599 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
13600 refinement to decide what config options should take priority if
13601 you ask to both use a particular node and exclude it.
13603 o Major features (misc):
13604 - When building a consensus, do not include routers that are down.
13605 This cuts down 30% to 40% on consensus size. Implements proposal
13607 - New TestingTorNetwork config option to allow adjustment of
13608 previously constant values that could slow bootstrapping. Implements
13609 proposal 135. Patch from Karsten.
13610 - Convert many internal address representations to optionally hold
13611 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
13612 elements. Make resolver code handle nameservers located at IPv6
13614 - More work on making our TLS handshake blend in: modify the list
13615 of ciphers advertised by OpenSSL in client mode to even more
13616 closely resemble a common web browser. We cheat a little so that
13617 we can advertise ciphers that the locally installed OpenSSL doesn't
13619 - Use the TLS1 hostname extension to more closely resemble browser
13622 o Security fixes (anonymity/entropy):
13623 - Never use a connection with a mismatched address to extend a
13624 circuit, unless that connection is canonical. A canonical
13625 connection is one whose address is authenticated by the router's
13626 identity key, either in a NETINFO cell or in a router descriptor.
13627 - Implement most of proposal 110: The first K cells to be sent
13628 along a circuit are marked as special "early" cells; only K "early"
13629 cells will be allowed. Once this code is universal, we can block
13630 certain kinds of denial-of-service attack by requiring that EXTEND
13631 commands must be sent using an "early" cell.
13632 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13633 cross-platform entropy collection again. We used to use it, then
13634 stopped using it because of a bug that could crash systems that
13635 called RAND_poll when they had a lot of fds open. It looks like the
13636 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13637 at startup, and to call RAND_poll() when we reseed later only if
13638 we have a non-buggy OpenSSL version.
13639 - When the client is choosing entry guards, now it selects at most
13640 one guard from a given relay family. Otherwise we could end up with
13641 all of our entry points into the network run by the same operator.
13642 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13643 - Do not use or believe expired v3 authority certificates. Patch
13644 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13645 - Drop begin cells to a hidden service if they come from the middle
13646 of a circuit. Patch from lark.
13647 - When we erroneously receive two EXTEND cells for the same circuit
13648 ID on the same connection, drop the second. Patch from lark.
13649 - Authorities now vote for the Stable flag for any router whose
13650 weighted MTBF is at least 5 days, regardless of the mean MTBF.
13651 - Clients now never report any stream end reason except 'MISC'.
13652 Implements proposal 148.
13654 o Major bugfixes (crashes):
13655 - Parse dates and IPv4 addresses in a locale- and libc-independent
13656 manner, to avoid platform-dependent behavior on malformed input.
13657 - Fix a crash that occurs on exit nodes when a nameserver request
13658 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
13659 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
13661 - Do not assume that a stack-allocated character array will be
13662 64-bit aligned on platforms that demand that uint64_t access is
13663 aligned. Possible fix for bug 604.
13664 - Resolve a very rare crash bug that could occur when the user forced
13665 a nameserver reconfiguration during the middle of a nameserver
13666 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
13667 - Avoid a "0 divided by 0" calculation when calculating router uptime
13668 at directory authorities. Bugfix on 0.2.0.8-alpha.
13669 - Fix an assertion bug in parsing policy-related options; possible fix
13671 - Rate-limit too-many-sockets messages: when they happen, they happen
13672 a lot and end up filling up the disk. Resolves bug 748.
13673 - Fix a race condition that could cause crashes or memory corruption
13674 when running as a server with a controller listening for log
13676 - Avoid crashing when we have a policy specified in a DirPolicy or
13677 SocksPolicy or ReachableAddresses option with ports set on it,
13678 and we re-load the policy. May fix bug 996.
13679 - Fix an assertion failure on 64-bit platforms when we allocated
13680 memory right up to the end of a memarea, then realigned the memory
13681 one step beyond the end. Fixes a possible cause of bug 930.
13682 - Protect the count of open sockets with a mutex, so we can't
13683 corrupt it when two threads are closing or opening sockets at once.
13684 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
13686 o Major bugfixes (clients):
13687 - Discard router descriptors as we load them if they are more than
13688 five days old. Otherwise if Tor is off for a long time and then
13689 starts with cached descriptors, it will try to use the onion keys
13690 in those obsolete descriptors when building circuits. Fixes bug 887.
13691 - When we choose to abandon a new entry guard because we think our
13692 older ones might be better, close any circuits pending on that
13693 new entry guard connection. This fix should make us recover much
13694 faster when our network is down and then comes back. Bugfix on
13695 0.1.2.8-beta; found by lodger.
13696 - When Tor clients restart after 1-5 days, they discard all their
13697 cached descriptors as too old, but they still use the cached
13698 consensus document. This approach is good for robustness, but
13699 bad for performance: since they don't know any bandwidths, they
13700 end up choosing at random rather than weighting their choice by
13701 speed. Fixed by the above feature of putting bandwidths in the
13704 o Major bugfixes (relays):
13705 - Relays were falling out of the networkstatus consensus for
13706 part of a day if they changed their local config but the
13707 authorities discarded their new descriptor as "not sufficiently
13708 different". Now directory authorities accept a descriptor as changed
13709 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
13710 patch by Sebastian.
13711 - Ensure that two circuits can never exist on the same connection
13712 with the same circuit ID, even if one is marked for close. This
13713 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13714 - Directory authorities were neglecting to mark relays down in their
13715 internal histories if the relays fall off the routerlist without
13716 ever being found unreachable. So there were relays in the histories
13717 that haven't been seen for eight months, and are listed as being
13718 up for eight months. This wreaked havoc on the "median wfu" and
13719 "median mtbf" calculations, in turn making Guard and Stable flags
13720 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
13723 o Major bugfixes (hidden services):
13724 - When establishing a hidden service, introduction points that
13725 originate from cannibalized circuits were completely ignored
13726 and not included in rendezvous service descriptors. This might
13727 have been another reason for delay in making a hidden service
13728 available. Bugfix from long ago (0.0.9.x?)
13730 o Major bugfixes (memory and resource management):
13731 - Fixed some memory leaks -- some quite frequent, some almost
13732 impossible to trigger -- based on results from Coverity.
13733 - Speed up parsing and cut down on memory fragmentation by using
13734 stack-style allocations for parsing directory objects. Previously,
13735 this accounted for over 40% of allocations from within Tor's code
13736 on a typical directory cache.
13737 - Use a Bloom filter rather than a digest-based set to track which
13738 descriptors we need to keep around when we're cleaning out old
13739 router descriptors. This speeds up the computation significantly,
13740 and may reduce fragmentation.
13742 o New/changed config options:
13743 - Now NodeFamily and MyFamily config options allow spaces in
13744 identity fingerprints, so it's easier to paste them in.
13745 Suggested by Lucky Green.
13746 - Allow ports 465 and 587 in the default exit policy again. We had
13747 rejected them in 0.1.0.15, because back in 2005 they were commonly
13748 misconfigured and ended up as spam targets. We hear they are better
13749 locked down these days.
13750 - Make TrackHostExit mappings expire a while after their last use, not
13751 after their creation. Patch from Robert Hogan.
13752 - Add an ExcludeExitNodes option so users can list a set of nodes
13753 that should be be excluded from the exit node position, but
13754 allowed elsewhere. Implements proposal 151.
13755 - New --hush command-line option similar to --quiet. While --quiet
13756 disables all logging to the console on startup, --hush limits the
13757 output to messages of warning and error severity.
13758 - New configure/torrc options (--enable-geoip-stats,
13759 DirRecordUsageByCountry) to record how many IPs we've served
13760 directory info to in each country code, how many status documents
13761 total we've sent to each country code, and what share of the total
13762 directory requests we should expect to see.
13763 - Make outbound DNS packets respect the OutboundBindAddress setting.
13764 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
13765 - Allow separate log levels to be configured for different logging
13766 domains. For example, this allows one to log all notices, warnings,
13767 or errors, plus all memory management messages of level debug or
13768 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13769 - Update to the "June 3 2009" ip-to-country file.
13771 o Minor features (relays):
13772 - Raise the minimum rate limiting to be a relay from 20000 bytes
13773 to 20480 bytes (aka 20KB/s), to match our documentation. Also
13774 update directory authorities so they always assign the Fast flag
13775 to relays with 20KB/s of capacity. Now people running relays won't
13776 suddenly find themselves not seeing any use, if the network gets
13778 - If we're a relay and we change our IP address, be more verbose
13779 about the reason that made us change. Should help track down
13780 further bugs for relays on dynamic IP addresses.
13781 - Exit servers can now answer resolve requests for ip6.arpa addresses.
13782 - Implement most of Proposal 152: allow specialized servers to permit
13783 single-hop circuits, and clients to use those servers to build
13784 single-hop circuits when using a specialized controller. Patch
13785 from Josh Albrecht. Resolves feature request 768.
13786 - When relays do their initial bandwidth measurement, don't limit
13787 to just our entry guards for the test circuits. Otherwise we tend
13788 to have multiple test circuits going through a single entry guard,
13789 which makes our bandwidth test less accurate. Fixes part of bug 654;
13790 patch contributed by Josh Albrecht.
13792 o Minor features (directory authorities):
13793 - Try not to open more than one descriptor-downloading connection
13794 to an authority at once. This should reduce load on directory
13795 authorities. Fixes bug 366.
13796 - Add cross-certification to newly generated certificates, so that
13797 a signing key is enough information to look up a certificate. Start
13798 serving certificates by <identity digest, signing key digest>
13799 pairs. Implements proposal 157.
13800 - When a directory authority downloads a descriptor that it then
13801 immediately rejects, do not retry downloading it right away. Should
13802 save some bandwidth on authorities. Fix for bug 888. Patch by
13804 - Directory authorities now serve a /tor/dbg-stability.txt URL to
13805 help debug WFU and MTBF calculations.
13806 - In directory authorities' approved-routers files, allow
13807 fingerprints with or without space.
13809 o Minor features (directory mirrors):
13810 - When a download gets us zero good descriptors, do not notify
13811 Tor that new directory information has arrived.
13812 - Servers support a new URL scheme for consensus downloads that
13813 allows the client to specify which authorities are trusted.
13814 The server then only sends the consensus if the client will trust
13815 it. Otherwise a 404 error is sent back. Clients use this
13816 new scheme when the server supports it (meaning it's running
13817 0.2.1.1-alpha or later). Implements proposal 134.
13819 o Minor features (bridges):
13820 - If the bridge config line doesn't specify a port, assume 443.
13821 This makes bridge lines a bit smaller and easier for users to
13823 - If we're using bridges and our network goes away, be more willing
13824 to forgive our bridges and try again when we get an application
13827 o Minor features (hidden services):
13828 - When the client launches an introduction circuit, retry with a
13829 new circuit after 30 seconds rather than 60 seconds.
13830 - Launch a second client-side introduction circuit in parallel
13831 after a delay of 15 seconds (based on work by Christian Wilms).
13832 - Hidden services start out building five intro circuits rather
13833 than three, and when the first three finish they publish a service
13834 descriptor using those. Now we publish our service descriptor much
13835 faster after restart.
13836 - Drop the requirement to have an open dir port for storing and
13837 serving v2 hidden service descriptors.
13839 o Minor features (build and packaging):
13840 - On Linux, use the prctl call to re-enable core dumps when the User
13842 - Try to make sure that the version of Libevent we're running with
13843 is binary-compatible with the one we built with. May address bug
13845 - Add a new --enable-local-appdata configuration switch to change
13846 the default location of the datadir on win32 from APPDATA to
13847 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
13848 entirely. Patch from coderman.
13849 - Build correctly against versions of OpenSSL 0.9.8 or later that
13850 are built without support for deprecated functions.
13851 - On platforms with a maximum syslog string length, truncate syslog
13852 messages to that length ourselves, rather than relying on the
13853 system to do it for us.
13854 - Automatically detect MacOSX versions earlier than 10.4.0, and
13855 disable kqueue from inside Tor when running with these versions.
13856 We previously did this from the startup script, but that was no
13857 help to people who didn't use the startup script. Resolves bug 863.
13858 - Build correctly when configured to build outside the main source
13859 path. Patch from Michael Gold.
13860 - Disable GCC's strict alias optimization by default, to avoid the
13861 likelihood of its introducing subtle bugs whenever our code violates
13862 the letter of C99's alias rules.
13863 - Change the contrib/tor.logrotate script so it makes the new
13864 logs as "_tor:_tor" rather than the default, which is generally
13865 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
13866 - Change our header file guard macros to be less likely to conflict
13867 with system headers. Adam Langley noticed that we were conflicting
13868 with log.h on Android.
13869 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
13870 and stop using a warning that had become unfixably verbose under
13872 - Use a lockfile to make sure that two Tor processes are not
13873 simultaneously running with the same datadir.
13874 - Allow OpenSSL to use dynamic locks if it wants.
13875 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
13877 o Minor features (controllers):
13878 - When generating circuit events with verbose nicknames for
13879 controllers, try harder to look up nicknames for routers on a
13880 circuit. (Previously, we would look in the router descriptors we had
13881 for nicknames, but not in the consensus.) Partial fix for bug 941.
13882 - New controller event NEWCONSENSUS that lists the networkstatus
13883 lines for every recommended relay. Now controllers like Torflow
13884 can keep up-to-date on which relays they should be using.
13885 - New controller event "clients_seen" to report a geoip-based summary
13886 of which countries we've seen clients from recently. Now controllers
13887 like Vidalia can show bridge operators that they're actually making
13889 - Add a 'getinfo status/clients-seen' controller command, in case
13890 controllers want to hear clients_seen events but connect late.
13891 - New CONSENSUS_ARRIVED event to note when a new consensus has
13892 been fetched and validated.
13893 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
13894 controllers to prevent SIGHUP from reloading the configuration.
13896 - Return circuit purposes in response to GETINFO circuit-status.
13898 - Serve the latest v3 networkstatus consensus via the control
13899 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
13900 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13901 controller can query our current bootstrap state in case it attaches
13902 partway through and wants to catch up.
13903 - Provide circuit purposes along with circuit events to the controller.
13905 o Minor features (tools):
13906 - Do not have tor-resolve automatically refuse all .onion addresses;
13907 if AutomapHostsOnResolve is set in your torrc, this will work fine.
13908 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13909 people find host:port too confusing.
13910 - Print the SOCKS5 error message string as well as the error code
13911 when a tor-resolve request fails. Patch from Jacob.
13913 o Minor bugfixes (memory and resource management):
13914 - Clients no longer cache certificates for authorities they do not
13915 recognize. Bugfix on 0.2.0.9-alpha.
13916 - Do not use C's stdio library for writing to log files. This will
13917 improve logging performance by a minute amount, and will stop
13918 leaking fds when our disk is full. Fixes bug 861.
13919 - Stop erroneous use of O_APPEND in cases where we did not in fact
13920 want to re-seek to the end of a file before every last write().
13921 - Fix a small alignment and memory-wasting bug on buffer chunks.
13923 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13924 to avoid unused RAM in buffer chunks and memory pools.
13925 - Reduce the default smartlist size from 32 to 16; it turns out that
13926 most smartlists hold around 8-12 elements tops.
13927 - Make dumpstats() log the fullness and size of openssl-internal
13929 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13930 patch to their OpenSSL, turn it on to save memory on servers. This
13931 patch will (with any luck) get included in a mainline distribution
13933 - Fix a memory leak when v3 directory authorities load their keys
13934 and cert from disk. Bugfix on 0.2.0.1-alpha.
13935 - Stop using malloc_usable_size() to use more area than we had
13936 actually allocated: it was safe, but made valgrind really unhappy.
13937 - Make the assert_circuit_ok() function work correctly on circuits that
13938 have already been marked for close.
13939 - Fix uninitialized size field for memory area allocation: may improve
13940 memory performance during directory parsing.
13942 o Minor bugfixes (clients):
13943 - Stop reloading the router list from disk for no reason when we
13944 run out of reachable directory mirrors. Once upon a time reloading
13945 it would set the 'is_running' flag back to 1 for them. It hasn't
13946 done that for a long time.
13947 - When we had picked an exit node for a connection, but marked it as
13948 "optional", and it turned out we had no onion key for the exit,
13949 stop wanting that exit and try again. This situation may not
13950 be possible now, but will probably become feasible with proposal
13951 158. Spotted by rovv. Fixes another case of bug 752.
13952 - Fix a bug in address parsing that was preventing bridges or hidden
13953 service targets from being at IPv6 addresses.
13954 - Do not remove routers as too old if we do not have any consensus
13955 document. Bugfix on 0.2.0.7-alpha.
13956 - When an exit relay resolves a stream address to a local IP address,
13957 do not just keep retrying that same exit relay over and
13958 over. Instead, just close the stream. Addresses bug 872. Bugfix
13959 on 0.2.0.32. Patch from rovv.
13960 - Made Tor a little less aggressive about deleting expired
13961 certificates. Partial fix for bug 854.
13962 - Treat duplicate certificate fetches as failures, so that we do
13963 not try to re-fetch an expired certificate over and over and over.
13964 - Do not say we're fetching a certificate when we'll in fact skip it
13965 because of a pending download.
13966 - If we have correct permissions on $datadir, we complain to stdout
13967 and fail to start. But dangerous permissions on
13968 $datadir/cached-status/ would cause us to open a log and complain
13969 there. Now complain to stdout and fail to start in both cases. Fixes
13970 bug 820, reported by seeess.
13972 o Minor bugfixes (bridges):
13973 - When we made bridge authorities stop serving bridge descriptors over
13974 unencrypted links, we also broke DirPort reachability testing for
13975 bridges. So bridges with a non-zero DirPort were printing spurious
13976 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
13977 - Don't allow a bridge to publish its router descriptor to a
13978 non-bridge directory authority. Fixes part of bug 932.
13979 - When we change to or from being a bridge, reset our counts of
13980 client usage by country. Fixes bug 932.
13982 o Minor bugfixes (relays):
13983 - Log correct error messages for DNS-related network errors on
13985 - Actually return -1 in the error case for read_bandwidth_usage().
13986 Harmless bug, since we currently don't care about the return value
13987 anywhere. Bugfix on 0.2.0.9-alpha.
13988 - Provide a more useful log message if bug 977 (related to buffer
13989 freelists) ever reappears, and do not crash right away.
13990 - We were already rejecting relay begin cells with destination port
13991 of 0. Now also reject extend cells with destination port or address
13992 of 0. Suggested by lark.
13993 - When we can't transmit a DNS request due to a network error, retry
13994 it after a while, and eventually transmit a failing response to
13995 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
13996 - Solve a bug that kept hardware crypto acceleration from getting
13997 enabled when accounting was turned on. Fixes bug 907. Bugfix on
13999 - When a canonical connection appears later in our internal list
14000 than a noncanonical one for a given OR ID, always use the
14001 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
14003 - Avoid some nasty corner cases in the logic for marking connections
14004 as too old or obsolete or noncanonical for circuits. Partial
14006 - Fix another interesting corner-case of bug 891 spotted by rovv:
14007 Previously, if two hosts had different amounts of clock drift, and
14008 one of them created a new connection with just the wrong timing,
14009 the other might decide to deprecate the new connection erroneously.
14010 Bugfix on 0.1.1.13-alpha.
14011 - If one win32 nameserver fails to get added, continue adding the
14012 rest, and don't automatically fail.
14013 - Fix a bug where an unreachable relay would establish enough
14014 reachability testing circuits to do a bandwidth test -- if
14015 we already have a connection to the middle hop of the testing
14016 circuit, then it could establish the last hop by using the existing
14017 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
14018 circuits no longer use entry guards in 0.2.1.3-alpha.
14020 o Minor bugfixes (directory authorities):
14021 - Limit uploaded directory documents to be 16M rather than 500K.
14022 The directory authorities were refusing v3 consensus votes from
14023 other authorities, since the votes are now 504K. Fixes bug 959;
14024 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
14025 - Directory authorities should never send a 503 "busy" response to
14026 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
14028 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
14029 headers. Bugfix on 0.2.0.10-alpha.
14031 o Minor bugfixes (hidden services):
14032 - When we can't find an intro key for a v2 hidden service descriptor,
14033 fall back to the v0 hidden service descriptor and log a bug message.
14034 Workaround for bug 1024.
14035 - In very rare situations new hidden service descriptors were
14036 published earlier than 30 seconds after the last change to the
14037 service. (We currently think that a hidden service descriptor
14038 that's been stable for 30 seconds is worth publishing.)
14039 - If a hidden service sends us an END cell, do not consider
14040 retrying the connection; just close it. Patch from rovv.
14041 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
14042 service directories if they have no advertised dir port. Bugfix
14045 o Minor bugfixes (tools):
14046 - In the torify(1) manpage, mention that tsocks will leak your
14049 o Minor bugfixes (controllers):
14050 - If the controller claimed responsibility for a stream, but that
14051 stream never finished making its connection, it would live
14052 forever in circuit_wait state. Now we close it after SocksTimeout
14053 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
14054 - Make DNS resolved controller events into "CLOSED", not
14055 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
14057 - The control port would close the connection before flushing long
14058 replies, such as the network consensus, if a QUIT command was issued
14059 before the reply had completed. Now, the control port flushes all
14060 pending replies before closing the connection. Also fix a spurious
14061 warning when a QUIT command is issued after a malformed or rejected
14062 AUTHENTICATE command, but before the connection was closed. Patch
14063 by Marcus Griep. Fixes bugs 1015 and 1016.
14064 - Fix a bug that made stream bandwidth get misreported to the
14067 o Deprecated and removed features:
14068 - The old "tor --version --version" command, which would print out
14069 the subversion "Id" of most of the source files, is now removed. It
14070 turned out to be less useful than we'd expected, and harder to
14072 - RedirectExits has been removed. It was deprecated since
14074 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
14075 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
14076 - Cell pools are now always enabled; --disable-cell-pools is ignored.
14077 - Directory mirrors no longer fetch the v1 directory or
14078 running-routers files. They are obsolete, and nobody asks for them
14079 anymore. This is the first step to making v1 authorities obsolete.
14080 - Take out the TestVia config option, since it was a workaround for
14081 a bug that was fixed in Tor 0.1.1.21.
14082 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
14083 HiddenServiceExcludeNodes as obsolete: they never worked properly,
14084 and nobody seems to be using them. Fixes bug 754. Bugfix on
14085 0.1.0.1-rc. Patch from Christian Wilms.
14086 - Remove all backward-compatibility code for relays running
14087 versions of Tor so old that they no longer work at all on the
14090 o Code simplifications and refactoring:
14091 - Tool-assisted documentation cleanup. Nearly every function or
14092 static variable in Tor should have its own documentation now.
14093 - Rename the confusing or_is_obsolete field to the more appropriate
14094 is_bad_for_new_circs, and move it to or_connection_t where it
14096 - Move edge-only flags from connection_t to edge_connection_t: not
14097 only is this better coding, but on machines of plausible alignment,
14098 it should save 4-8 bytes per connection_t. "Every little bit helps."
14099 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
14100 for consistency; keep old option working for backward compatibility.
14101 - Simplify the code for finding connections to use for a circuit.
14102 - Revise the connection_new functions so that a more typesafe variant
14103 exists. This will work better with Coverity, and let us find any
14104 actual mistakes we're making here.
14105 - Refactor unit testing logic so that dmalloc can be used sensibly
14106 with unit tests to check for memory leaks.
14107 - Move all hidden-service related fields from connection and circuit
14108 structure to substructures: this way they won't eat so much memory.
14109 - Squeeze 2-5% out of client performance (according to oprofile) by
14110 improving the implementation of some policy-manipulation functions.
14111 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
14112 be more efficient. Formerly it was quadratic in the number of
14113 servers; now it should be linear. Fixes bug 509.
14114 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
14115 and n_conn_id_digest fields into a separate structure that's
14116 only needed when the circuit has not yet attached to an n_conn.
14117 - Optimize out calls to time(NULL) that occur for every IO operation,
14118 or for every cell. On systems like Windows where time() is a
14119 slow syscall, this fix will be slightly helpful.
14122 Changes in version 0.2.0.35 - 2009-06-24
14124 - Avoid crashing in the presence of certain malformed descriptors.
14125 Found by lark, and by automated fuzzing.
14126 - Fix an edge case where a malicious exit relay could convince a
14127 controller that the client's DNS question resolves to an internal IP
14128 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
14131 - Finally fix the bug where dynamic-IP relays disappear when their
14132 IP address changes: directory mirrors were mistakenly telling
14133 them their old address if they asked via begin_dir, so they
14134 never got an accurate answer about their new address, so they
14135 just vanished after a day. For belt-and-suspenders, relays that
14136 don't set Address in their config now avoid using begin_dir for
14137 all direct connections. Should fix bugs 827, 883, and 900.
14138 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
14139 that would occur on some exit nodes when DNS failures and timeouts
14140 occurred in certain patterns. Fix for bug 957.
14143 - When starting with a cache over a few days old, do not leak
14144 memory for the obsolete router descriptors in it. Bugfix on
14145 0.2.0.33; fixes bug 672.
14146 - Hidden service clients didn't use a cached service descriptor that
14147 was older than 15 minutes, but wouldn't fetch a new one either,
14148 because there was already one in the cache. Now, fetch a v2
14149 descriptor unless the same descriptor was added to the cache within
14150 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
14153 Changes in version 0.2.0.34 - 2009-02-08
14154 Tor 0.2.0.34 features several more security-related fixes. You should
14155 upgrade, especially if you run an exit relay (remote crash) or a
14156 directory authority (remote infinite loop), or you're on an older
14157 (pre-XP) or not-recently-patched Windows (remote exploit).
14159 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
14160 have many known flaws, and nobody should be using them. You should
14161 upgrade. If you're using a Linux or BSD and its packages are obsolete,
14162 stop using those packages and upgrade anyway.
14165 - Fix an infinite-loop bug on handling corrupt votes under certain
14166 circumstances. Bugfix on 0.2.0.8-alpha.
14167 - Fix a temporary DoS vulnerability that could be performed by
14168 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
14169 - Avoid a potential crash on exit nodes when processing malformed
14170 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
14171 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
14172 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
14175 - Fix compilation on systems where time_t is a 64-bit integer.
14176 Patch from Matthias Drochner.
14177 - Don't consider expiring already-closed client connections. Fixes
14178 bug 893. Bugfix on 0.0.2pre20.
14181 Changes in version 0.2.0.33 - 2009-01-21
14182 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
14183 useful to users. It also finally fixes a bug where a relay or client
14184 that's been off for many days would take a long time to bootstrap.
14186 This update also fixes an important security-related bug reported by
14187 Ilja van Sprundel. You should upgrade. (We'll send out more details
14188 about the bug once people have had some time to upgrade.)
14191 - Fix a heap-corruption bug that may be remotely triggerable on
14192 some platforms. Reported by Ilja van Sprundel.
14195 - When a stream at an exit relay is in state "resolving" or
14196 "connecting" and it receives an "end" relay cell, the exit relay
14197 would silently ignore the end cell and not close the stream. If
14198 the client never closes the circuit, then the exit relay never
14199 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
14200 reported by "wood".
14201 - When sending CREATED cells back for a given circuit, use a 64-bit
14202 connection ID to find the right connection, rather than an addr:port
14203 combination. Now that we can have multiple OR connections between
14204 the same ORs, it is no longer possible to use addr:port to uniquely
14205 identify a connection.
14206 - Bridge relays that had DirPort set to 0 would stop fetching
14207 descriptors shortly after startup, and then briefly resume
14208 after a new bandwidth test and/or after publishing a new bridge
14209 descriptor. Bridge users that try to bootstrap from them would
14210 get a recent networkstatus but would get descriptors from up to
14211 18 hours earlier, meaning most of the descriptors were obsolete
14212 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
14213 - Prevent bridge relays from serving their 'extrainfo' document
14214 to anybody who asks, now that extrainfo docs include potentially
14215 sensitive aggregated client geoip summaries. Bugfix on
14217 - If the cached networkstatus consensus is more than five days old,
14218 discard it rather than trying to use it. In theory it could be
14219 useful because it lists alternate directory mirrors, but in practice
14220 it just means we spend many minutes trying directory mirrors that
14221 are long gone from the network. Also discard router descriptors as
14222 we load them if they are more than five days old, since the onion
14223 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
14226 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
14227 could make gcc generate non-functional binary search code. Bugfix
14229 - Build correctly on platforms without socklen_t.
14230 - Compile without warnings on solaris.
14231 - Avoid potential crash on internal error during signature collection.
14232 Fixes bug 864. Patch from rovv.
14233 - Correct handling of possible malformed authority signing key
14234 certificates with internal signature types. Fixes bug 880.
14235 Bugfix on 0.2.0.3-alpha.
14236 - Fix a hard-to-trigger resource leak when logging credential status.
14238 - When we can't initialize DNS because the network is down, do not
14239 automatically stop Tor from starting. Instead, we retry failed
14240 dns_init() every 10 minutes, and change the exit policy to reject
14241 *:* until one succeeds. Fixes bug 691.
14242 - Use 64 bits instead of 32 bits for connection identifiers used with
14243 the controller protocol, to greatly reduce risk of identifier reuse.
14244 - When we're choosing an exit node for a circuit, and we have
14245 no pending streams, choose a good general exit rather than one that
14246 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
14247 - Fix another case of assuming, when a specific exit is requested,
14248 that we know more than the user about what hosts it allows.
14249 Fixes one case of bug 752. Patch from rovv.
14250 - Clip the MaxCircuitDirtiness config option to a minimum of 10
14251 seconds. Warn the user if lower values are given in the
14252 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
14253 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
14254 user if lower values are given in the configuration. Bugfix on
14255 0.1.1.17-rc. Patch by Sebastian.
14256 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
14257 the cache because we already had a v0 descriptor with the same ID.
14258 Bugfix on 0.2.0.18-alpha.
14259 - Fix a race condition when freeing keys shared between main thread
14260 and CPU workers that could result in a memory leak. Bugfix on
14261 0.1.0.1-rc. Fixes bug 889.
14262 - Send a valid END cell back when a client tries to connect to a
14263 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
14264 840. Patch from rovv.
14265 - Check which hops rendezvous stream cells are associated with to
14266 prevent possible guess-the-streamid injection attacks from
14267 intermediate hops. Fixes another case of bug 446. Based on patch
14269 - If a broken client asks a non-exit router to connect somewhere,
14270 do not even do the DNS lookup before rejecting the connection.
14271 Fixes another case of bug 619. Patch from rovv.
14272 - When a relay gets a create cell it can't decrypt (e.g. because it's
14273 using the wrong onion key), we were dropping it and letting the
14274 client time out. Now actually answer with a destroy cell. Fixes
14275 bug 904. Bugfix on 0.0.2pre8.
14277 o Minor bugfixes (hidden services):
14278 - Do not throw away existing introduction points on SIGHUP. Bugfix on
14279 0.0.6pre1. Patch by Karsten. Fixes bug 874.
14282 - Report the case where all signatures in a detached set are rejected
14283 differently than the case where there is an error handling the
14285 - When we realize that another process has modified our cached
14286 descriptors, print out a more useful error message rather than
14287 triggering an assertion. Fixes bug 885. Patch from Karsten.
14288 - Implement the 0x20 hack to better resist DNS poisoning: set the
14289 case on outgoing DNS requests randomly, and reject responses that do
14290 not match the case correctly. This logic can be disabled with the
14291 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
14292 of servers that do not reliably preserve case in replies. See
14293 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
14295 - Check DNS replies for more matching fields to better resist DNS
14297 - Never use OpenSSL compression: it wastes RAM and CPU trying to
14298 compress cells, which are basically all encrypted, compressed, or
14302 Changes in version 0.2.0.32 - 2008-11-20
14303 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
14304 packages (and maybe other packages) noticed by Theo de Raadt, fixes
14305 a smaller security flaw that might allow an attacker to access local
14306 services, further improves hidden service performance, and fixes a
14307 variety of other issues.
14310 - The "User" and "Group" config options did not clear the
14311 supplementary group entries for the Tor process. The "User" option
14312 is now more robust, and we now set the groups to the specified
14313 user's primary group. The "Group" option is now ignored. For more
14314 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
14315 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
14316 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
14317 - The "ClientDNSRejectInternalAddresses" config option wasn't being
14318 consistently obeyed: if an exit relay refuses a stream because its
14319 exit policy doesn't allow it, we would remember what IP address
14320 the relay said the destination address resolves to, even if it's
14321 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
14324 - Fix a DOS opportunity during the voting signature collection process
14325 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
14327 o Major bugfixes (hidden services):
14328 - When fetching v0 and v2 rendezvous service descriptors in parallel,
14329 we were failing the whole hidden service request when the v0
14330 descriptor fetch fails, even if the v2 fetch is still pending and
14331 might succeed. Similarly, if the last v2 fetch fails, we were
14332 failing the whole hidden service request even if a v0 fetch is
14333 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
14334 - When extending a circuit to a hidden service directory to upload a
14335 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
14336 requests failed, because the router descriptor has not been
14337 downloaded yet. In these cases, do not attempt to upload the
14338 rendezvous descriptor, but wait until the router descriptor is
14339 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
14340 descriptor from a hidden service directory for which the router
14341 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
14345 - Fix several infrequent memory leaks spotted by Coverity.
14346 - When testing for libevent functions, set the LDFLAGS variable
14347 correctly. Found by Riastradh.
14348 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
14349 bootstrapping with tunneled directory connections. Bugfix on
14350 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
14351 - When asked to connect to A.B.exit:80, if we don't know the IP for A
14352 and we know that server B rejects most-but-not all connections to
14353 port 80, we would previously reject the connection. Now, we assume
14354 the user knows what they were asking for. Fixes bug 752. Bugfix
14355 on 0.0.9rc5. Diagnosed by BarkerJr.
14356 - If we overrun our per-second write limits a little, count this as
14357 having used up our write allocation for the second, and choke
14358 outgoing directory writes. Previously, we had only counted this when
14359 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
14360 Bugfix on 0.2.0.x (??).
14361 - Remove the old v2 directory authority 'lefkada' from the default
14362 list. It has been gone for many months.
14363 - Stop doing unaligned memory access that generated bus errors on
14364 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
14365 - Make USR2 log-level switch take effect immediately. Bugfix on
14368 o Minor bugfixes (controller):
14369 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
14370 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
14373 Changes in version 0.2.0.31 - 2008-09-03
14374 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
14375 a big bug we're seeing where in rare cases traffic from one Tor stream
14376 gets mixed into another stream, and fixes a variety of smaller issues.
14379 - Make sure that two circuits can never exist on the same connection
14380 with the same circuit ID, even if one is marked for close. This
14381 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
14382 - Relays now reject risky extend cells: if the extend cell includes
14383 a digest of all zeroes, or asks to extend back to the relay that
14384 sent the extend cell, tear down the circuit. Ideas suggested
14386 - If not enough of our entry guards are available so we add a new
14387 one, we might use the new one even if it overlapped with the
14388 current circuit's exit relay (or its family). Anonymity bugfix
14389 pointed out by rovv.
14392 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
14393 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
14394 - Correctly detect the presence of the linux/netfilter_ipv4.h header
14395 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
14396 - Pick size of default geoip filename string correctly on windows.
14397 Fixes bug 806. Bugfix on 0.2.0.30.
14398 - Make the autoconf script accept the obsolete --with-ssl-dir
14399 option as an alias for the actually-working --with-openssl-dir
14400 option. Fix the help documentation to recommend --with-openssl-dir.
14401 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
14402 - When using the TransPort option on OpenBSD, and using the User
14403 option to change UID and drop privileges, make sure to open
14404 /dev/pf before dropping privileges. Fixes bug 782. Patch from
14405 Christopher Davis. Bugfix on 0.1.2.1-alpha.
14406 - Try to attach connections immediately upon receiving a RENDEZVOUS2
14407 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
14408 on the client side when connecting to a hidden service. Bugfix
14409 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
14410 - When closing an application-side connection because its circuit is
14411 getting torn down, generate the stream event correctly. Bugfix on
14412 0.1.2.x. Anonymous patch.
14415 Changes in version 0.2.0.30 - 2008-07-15
14416 This new stable release switches to a more efficient directory
14417 distribution design, adds features to make connections to the Tor
14418 network harder to block, allows Tor to act as a DNS proxy, adds separate
14419 rate limiting for relayed traffic to make it easier for clients to
14420 become relays, fixes a variety of potential anonymity problems, and
14421 includes the usual huge pile of other features and bug fixes.
14423 o New v3 directory design:
14424 - Tor now uses a new way to learn about and distribute information
14425 about the network: the directory authorities vote on a common
14426 network status document rather than each publishing their own
14427 opinion. Now clients and caches download only one networkstatus
14428 document to bootstrap, rather than downloading one for each
14429 authority. Clients only download router descriptors listed in
14430 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
14432 - Set up moria1, tor26, and dizum as v3 directory authorities
14433 in addition to being v2 authorities. Also add three new ones:
14434 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
14435 dannenberg (run by CCC).
14436 - Switch to multi-level keys for directory authorities: now their
14437 long-term identity key can be kept offline, and they periodically
14438 generate a new signing key. Clients fetch the "key certificates"
14439 to keep up to date on the right keys. Add a standalone tool
14440 "tor-gencert" to generate key certificates. Implements proposal 103.
14441 - Add a new V3AuthUseLegacyKey config option to make it easier for
14442 v3 authorities to change their identity keys if another bug like
14443 Debian's OpenSSL RNG flaw appears.
14444 - Authorities and caches fetch the v2 networkstatus documents
14445 less often, now that v3 is recommended.
14447 o Make Tor connections stand out less on the wire:
14448 - Use an improved TLS handshake designed by Steven Murdoch in proposal
14449 124, as revised in proposal 130. The new handshake is meant to
14450 be harder for censors to fingerprint, and it adds the ability
14451 to detect certain kinds of man-in-the-middle traffic analysis
14452 attacks. The new handshake format includes version negotiation for
14453 OR connections as described in proposal 105, which will allow us
14454 to improve Tor's link protocol more safely in the future.
14455 - Enable encrypted directory connections by default for non-relays,
14456 so censor tools that block Tor directory connections based on their
14457 plaintext patterns will no longer work. This means Tor works in
14458 certain censored countries by default again.
14459 - Stop including recognizeable strings in the commonname part of
14460 Tor's x509 certificates.
14462 o Implement bridge relays:
14463 - Bridge relays (or "bridges" for short) are Tor relays that aren't
14464 listed in the main Tor directory. Since there is no complete public
14465 list of them, even an ISP that is filtering connections to all the
14466 known Tor relays probably won't be able to block all the bridges.
14467 See doc/design-paper/blocking.pdf and proposal 125 for details.
14468 - New config option BridgeRelay that specifies you want to be a
14469 bridge relay rather than a normal relay. When BridgeRelay is set
14470 to 1, then a) you cache dir info even if your DirPort ins't on,
14471 and b) the default for PublishServerDescriptor is now "bridge"
14472 rather than "v2,v3".
14473 - New config option "UseBridges 1" for clients that want to use bridge
14474 relays instead of ordinary entry guards. Clients then specify
14475 bridge relays by adding "Bridge" lines to their config file. Users
14476 can learn about a bridge relay either manually through word of
14477 mouth, or by one of our rate-limited mechanisms for giving out
14478 bridge addresses without letting an attacker easily enumerate them
14479 all. See https://www.torproject.org/bridges for details.
14480 - Bridge relays behave like clients with respect to time intervals
14481 for downloading new v3 consensus documents -- otherwise they
14482 stand out. Bridge users now wait until the end of the interval,
14483 so their bridge relay will be sure to have a new consensus document.
14485 o Implement bridge directory authorities:
14486 - Bridge authorities are like normal directory authorities, except
14487 they don't serve a list of known bridges. Therefore users that know
14488 a bridge's fingerprint can fetch a relay descriptor for that bridge,
14489 including fetching updates e.g. if the bridge changes IP address,
14490 yet an attacker can't just fetch a list of all the bridges.
14491 - Set up Tonga as the default bridge directory authority.
14492 - Bridge authorities refuse to serve bridge descriptors or other
14493 bridge information over unencrypted connections (that is, when
14494 responding to direct DirPort requests rather than begin_dir cells.)
14495 - Bridge directory authorities do reachability testing on the
14496 bridges they know. They provide router status summaries to the
14497 controller via "getinfo ns/purpose/bridge", and also dump summaries
14498 to a file periodically, so we can keep internal stats about which
14499 bridges are functioning.
14500 - If bridge users set the UpdateBridgesFromAuthority config option,
14501 but the digest they ask for is a 404 on the bridge authority,
14502 they fall back to contacting the bridge directly.
14503 - Bridges always use begin_dir to publish their server descriptor to
14504 the bridge authority using an anonymous encrypted tunnel.
14505 - Early work on a "bridge community" design: if bridge authorities set
14506 the BridgePassword config option, they will serve a snapshot of
14507 known bridge routerstatuses from their DirPort to anybody who
14508 knows that password. Unset by default.
14509 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
14510 report sanitized aggregated summaries in their extra-info documents
14511 privately to the bridge authority, listing which countries are
14512 able to reach them. We hope this mechanism will let us learn when
14513 certain countries start trying to block bridges.
14514 - Bridge authorities write bridge descriptors to disk, so they can
14515 reload them after a reboot. They can also export the descriptors
14516 to other programs, so we can distribute them to blocked users via
14517 the BridgeDB interface, e.g. via https://bridges.torproject.org/
14518 and bridges@torproject.org.
14520 o Tor can be a DNS proxy:
14521 - The new client-side DNS proxy feature replaces the need for
14522 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
14523 for DNS requests on port 9999, use the Tor network to resolve them
14524 anonymously, and send the reply back like a regular DNS server.
14525 The code still only implements a subset of DNS.
14526 - Add a new AutomapHostsOnResolve option: when it is enabled, any
14527 resolve request for hosts matching a given pattern causes Tor to
14528 generate an internal virtual address mapping for that host. This
14529 allows DNSPort to work sensibly with hidden service users. By
14530 default, .exit and .onion addresses are remapped; the list of
14531 patterns can be reconfigured with AutomapHostsSuffixes.
14532 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14533 address. Thanks to the AutomapHostsOnResolve option, this is no
14534 longer a completely silly thing to do.
14536 o Major features (relay usability):
14537 - New config options RelayBandwidthRate and RelayBandwidthBurst:
14538 a separate set of token buckets for relayed traffic. Right now
14539 relayed traffic is defined as answers to directory requests, and
14540 OR connections that don't have any local circuits on them. See
14541 proposal 111 for details.
14542 - Create listener connections before we setuid to the configured
14543 User and Group. Now non-Windows users can choose port values
14544 under 1024, start Tor as root, and have Tor bind those ports
14545 before it changes to another UID. (Windows users could already
14547 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14548 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14549 on "vserver" accounts. Patch from coderman.
14551 o Major features (directory authorities):
14552 - Directory authorities track weighted fractional uptime and weighted
14553 mean-time-between failures for relays. WFU is suitable for deciding
14554 whether a node is "usually up", while MTBF is suitable for deciding
14555 whether a node is "likely to stay up." We need both, because
14556 "usually up" is a good requirement for guards, while "likely to
14557 stay up" is a good requirement for long-lived connections.
14558 - Directory authorities use a new formula for selecting which relays
14559 to advertise as Guards: they must be in the top 7/8 in terms of
14560 how long we have known about them, and above the median of those
14561 nodes in terms of weighted fractional uptime.
14562 - Directory authorities use a new formula for selecting which relays
14563 to advertise as Stable: when we have 4 or more days of data, use
14564 median measured MTBF rather than median declared uptime. Implements
14566 - Directory authorities accept and serve "extra info" documents for
14567 routers. Routers now publish their bandwidth-history lines in the
14568 extra-info docs rather than the main descriptor. This step saves
14569 60% (!) on compressed router descriptor downloads. Servers upload
14570 extra-info docs to any authority that accepts them; directory
14571 authorities now allow multiple router descriptors and/or extra
14572 info documents to be uploaded in a single go. Authorities, and
14573 caches that have been configured to download extra-info documents,
14574 download them as needed. Implements proposal 104.
14575 - Authorities now list relays who have the same nickname as
14576 a different named relay, but list them with a new flag:
14577 "Unnamed". Now we can make use of relays that happen to pick the
14578 same nickname as a server that registered two years ago and then
14579 disappeared. Implements proposal 122.
14580 - Store routers in a file called cached-descriptors instead of in
14581 cached-routers. Initialize cached-descriptors from cached-routers
14582 if the old format is around. The new format allows us to store
14583 annotations along with descriptors, to record the time we received
14584 each descriptor, its source, and its purpose: currently one of
14585 general, controller, or bridge.
14587 o Major features (other):
14588 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14589 Tor can warn and/or refuse connections to ports commonly used with
14590 vulnerable-plaintext protocols. Currently we warn on ports 23,
14591 109, 110, and 143, but we don't reject any. Based on proposal 129
14592 by Kevin Bauer and Damon McCoy.
14593 - Integrate Karsten Loesing's Google Summer of Code project to publish
14594 hidden service descriptors on a set of redundant relays that are a
14595 function of the hidden service address. Now we don't have to rely
14596 on three central hidden service authorities for publishing and
14597 fetching every hidden service descriptor. Implements proposal 114.
14598 - Allow tunnelled directory connections to ask for an encrypted
14599 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14600 connection independently. Now we can make anonymized begin_dir
14601 connections for (e.g.) more secure hidden service posting and
14604 o Major bugfixes (crashes and assert failures):
14605 - Stop imposing an arbitrary maximum on the number of file descriptors
14606 used for busy servers. Bug reported by Olaf Selke; patch from
14608 - Avoid possible failures when generating a directory with routers
14609 with over-long versions strings, or too many flags set.
14610 - Fix a rare assert error when we're closing one of our threads:
14611 use a mutex to protect the list of logs, so we never write to the
14612 list as it's being freed. Fixes the very rare bug 575, which is
14613 kind of the revenge of bug 222.
14614 - Avoid segfault in the case where a badly behaved v2 versioning
14615 directory sends a signed networkstatus with missing client-versions.
14616 - When we hit an EOF on a log (probably because we're shutting down),
14617 don't try to remove the log from the list: just mark it as
14618 unusable. (Bulletproofs against bug 222.)
14620 o Major bugfixes (code security fixes):
14621 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14623 - Rewrite directory tokenization code to never run off the end of
14624 a string. Fixes bug 455. Patch from croup.
14625 - Be more paranoid about overwriting sensitive memory on free(),
14626 as a defensive programming tactic to ensure forward secrecy.
14628 o Major bugfixes (anonymity fixes):
14629 - Reject requests for reverse-dns lookup of names that are in
14630 a private address space. Patch from lodger.
14631 - Never report that we've used more bandwidth than we're willing to
14632 relay: it leaks how much non-relay traffic we're using. Resolves
14634 - As a client, do not believe any server that tells us that an
14635 address maps to an internal address space.
14636 - Warn about unsafe ControlPort configurations.
14637 - Directory authorities now call routers Fast if their bandwidth is
14638 at least 100KB/s, and consider their bandwidth adequate to be a
14639 Guard if it is at least 250KB/s, no matter the medians. This fix
14640 complements proposal 107.
14641 - Directory authorities now never mark more than 2 servers per IP as
14642 Valid and Running (or 5 on addresses shared by authorities).
14643 Implements proposal 109, by Kevin Bauer and Damon McCoy.
14644 - If we're a relay, avoid picking ourselves as an introduction point,
14645 a rendezvous point, or as the final hop for internal circuits. Bug
14646 reported by taranis and lodger.
14647 - Exit relays that are used as a client can now reach themselves
14648 using the .exit notation, rather than just launching an infinite
14649 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
14650 - Fix a bug where, when we were choosing the 'end stream reason' to
14651 put in our relay end cell that we send to the exit relay, Tor
14652 clients on Windows were sometimes sending the wrong 'reason'. The
14653 anonymity problem is that exit relays may be able to guess whether
14654 the client is running Windows, thus helping partition the anonymity
14655 set. Down the road we should stop sending reasons to exit relays,
14656 or otherwise prevent future versions of this bug.
14657 - Only update guard status (usable / not usable) once we have
14658 enough directory information. This was causing us to discard all our
14659 guards on startup if we hadn't been running for a few weeks. Fixes
14661 - When our directory information has been expired for a while, stop
14662 being willing to build circuits using it. Fixes bug 401.
14664 o Major bugfixes (peace of mind for relay operators)
14665 - Non-exit relays no longer answer "resolve" relay cells, so they
14666 can't be induced to do arbitrary DNS requests. (Tor clients already
14667 avoid using non-exit relays for resolve cells, but now servers
14668 enforce this too.) Fixes bug 619. Patch from lodger.
14669 - When we setconf ClientOnly to 1, close any current OR and Dir
14670 listeners. Reported by mwenge.
14672 o Major bugfixes (other):
14673 - If we only ever used Tor for hidden service lookups or posts, we
14674 would stop building circuits and start refusing connections after
14675 24 hours, since we falsely believed that Tor was dormant. Reported
14677 - Add a new __HashedControlSessionPassword option for controllers
14678 to use for one-off session password hashes that shouldn't get
14679 saved to disk by SAVECONF --- Vidalia users were accumulating a
14680 pile of HashedControlPassword lines in their torrc files, one for
14681 each time they had restarted Tor and then clicked Save. Make Tor
14682 automatically convert "HashedControlPassword" to this new option but
14683 only when it's given on the command line. Partial fix for bug 586.
14684 - Patch from "Andrew S. Lists" to catch when we contact a directory
14685 mirror at IP address X and he says we look like we're coming from
14686 IP address X. Otherwise this would screw up our address detection.
14687 - Reject uploaded descriptors and extrainfo documents if they're
14688 huge. Otherwise we'll cache them all over the network and it'll
14689 clog everything up. Suggested by Aljosha Judmayer.
14690 - When a hidden service was trying to establish an introduction point,
14691 and Tor *did* manage to reuse one of the preemptively built
14692 circuits, it didn't correctly remember which one it used,
14693 so it asked for another one soon after, until there were no
14694 more preemptive circuits, at which point it launched one from
14695 scratch. Bugfix on 0.0.9.x.
14697 o Rate limiting and load balancing improvements:
14698 - When we add data to a write buffer in response to the data on that
14699 write buffer getting low because of a flush, do not consider the
14700 newly added data as a candidate for immediate flushing, but rather
14701 make it wait until the next round of writing. Otherwise, we flush
14702 and refill recursively, and a single greedy TLS connection can
14703 eat all of our bandwidth.
14704 - When counting the number of bytes written on a TLS connection,
14705 look at the BIO actually used for writing to the network, not
14706 at the BIO used (sometimes) to buffer data for the network.
14707 Looking at different BIOs could result in write counts on the
14708 order of ULONG_MAX. Fixes bug 614.
14709 - If we change our MaxAdvertisedBandwidth and then reload torrc,
14710 Tor won't realize it should publish a new relay descriptor. Fixes
14711 bug 688, reported by mfr.
14712 - Avoid using too little bandwidth when our clock skips a few seconds.
14713 - Choose which bridge to use proportional to its advertised bandwidth,
14714 rather than uniformly at random. This should speed up Tor for
14715 bridge users. Also do this for people who set StrictEntryNodes.
14717 o Bootstrapping faster and building circuits more intelligently:
14718 - Fix bug 660 that was preventing us from knowing that we should
14719 preemptively build circuits to handle expected directory requests.
14720 - When we're checking if we have enough dir info for each relay
14721 to begin establishing circuits, make sure that we actually have
14722 the descriptor listed in the consensus, not just any descriptor.
14723 - Correctly notify one-hop connections when a circuit build has
14724 failed. Possible fix for bug 669. Found by lodger.
14725 - Clients now hold circuitless TLS connections open for 1.5 times
14726 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14727 rebuild a new circuit over them within that timeframe. Previously,
14728 they held them open only for KeepalivePeriod (5 minutes).
14730 o Performance improvements (memory):
14731 - Add OpenBSD malloc code from "phk" as an optional malloc
14732 replacement on Linux: some glibc libraries do very poorly with
14733 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
14734 ./configure to get the replacement malloc code.
14735 - Switch our old ring buffer implementation for one more like that
14736 used by free Unix kernels. The wasted space in a buffer with 1mb
14737 of data will now be more like 8k than 1mb. The new implementation
14738 also avoids realloc();realloc(); patterns that can contribute to
14739 memory fragmentation.
14740 - Change the way that Tor buffers data that it is waiting to write.
14741 Instead of queueing data cells in an enormous ring buffer for each
14742 client->OR or OR->OR connection, we now queue cells on a separate
14743 queue for each circuit. This lets us use less slack memory, and
14744 will eventually let us be smarter about prioritizing different kinds
14746 - Reference-count and share copies of address policy entries; only 5%
14747 of them were actually distinct.
14748 - Tune parameters for cell pool allocation to minimize amount of
14750 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14751 for every single inactive connection_t. Free items from the
14752 4k/16k-buffer free lists when they haven't been used for a while.
14753 - Make memory debugging information describe more about history
14754 of cell allocation, so we can help reduce our memory use.
14755 - Be even more aggressive about releasing RAM from small
14756 empty buffers. Thanks to our free-list code, this shouldn't be too
14757 performance-intensive.
14758 - Log malloc statistics from mallinfo() on platforms where it exists.
14759 - Use memory pools to allocate cells with better speed and memory
14760 efficiency, especially on platforms where malloc() is inefficient.
14761 - Add a --with-tcmalloc option to the configure script to link
14762 against tcmalloc (if present). Does not yet search for non-system
14765 o Performance improvements (socket management):
14766 - Count the number of open sockets separately from the number of
14767 active connection_t objects. This will let us avoid underusing
14768 our allocated connection limit.
14769 - We no longer use socket pairs to link an edge connection to an
14770 anonymous directory connection or a DirPort test connection.
14771 Instead, we track the link internally and transfer the data
14772 in-process. This saves two sockets per "linked" connection (at the
14773 client and at the server), and avoids the nasty Windows socketpair()
14775 - We were leaking a file descriptor if Tor started with a zero-length
14776 cached-descriptors file. Patch by "freddy77".
14778 o Performance improvements (CPU use):
14779 - Never walk through the list of logs if we know that no log target
14780 is interested in a given message.
14781 - Call routerlist_remove_old_routers() much less often. This should
14782 speed startup, especially on directory caches.
14783 - Base64 decoding was actually showing up on our profile when parsing
14784 the initial descriptor file; switch to an in-process all-at-once
14785 implementation that's about 3.5x times faster than calling out to
14787 - Use a slightly simpler string hashing algorithm (copying Python's
14788 instead of Java's) and optimize our digest hashing algorithm to take
14789 advantage of 64-bit platforms and to remove some possibly-costly
14791 - When implementing AES counter mode, update only the portions of the
14792 counter buffer that need to change, and don't keep separate
14793 network-order and host-order counters on big-endian hosts (where
14794 they are the same).
14795 - Add an in-place version of aes_crypt() so that we can avoid doing a
14796 needless memcpy() call on each cell payload.
14797 - Use Critical Sections rather than Mutexes for synchronizing threads
14798 on win32; Mutexes are heavier-weight, and designed for synchronizing
14801 o Performance improvements (bandwidth use):
14802 - Don't try to launch new descriptor downloads quite so often when we
14803 already have enough directory information to build circuits.
14804 - Version 1 directories are no longer generated in full. Instead,
14805 authorities generate and serve "stub" v1 directories that list
14806 no servers. This will stop Tor versions 0.1.0.x and earlier from
14807 working, but (for security reasons) nobody should be running those
14809 - Avoid going directly to the directory authorities even if you're a
14810 relay, if you haven't found yourself reachable yet or if you've
14811 decided not to advertise your dirport yet. Addresses bug 556.
14812 - If we've gone 12 hours since our last bandwidth check, and we
14813 estimate we have less than 50KB bandwidth capacity but we could
14814 handle more, do another bandwidth test.
14815 - Support "If-Modified-Since" when answering HTTP requests for
14816 directories, running-routers documents, and v2 and v3 networkstatus
14817 documents. (There's no need to support it for router descriptors,
14818 since those are downloaded by descriptor digest.)
14819 - Stop fetching directory info so aggressively if your DirPort is
14820 on but your ORPort is off; stop fetching v2 dir info entirely.
14821 You can override these choices with the new FetchDirInfoEarly
14824 o Changed config option behavior (features):
14825 - Configuration files now accept C-style strings as values. This
14826 helps encode characters not allowed in the current configuration
14827 file format, such as newline or #. Addresses bug 557.
14828 - Add hidden services and DNSPorts to the list of things that make
14829 Tor accept that it has running ports. Change starting Tor with no
14830 ports from a fatal error to a warning; we might change it back if
14831 this turns out to confuse anybody. Fixes bug 579.
14832 - Make PublishServerDescriptor default to 1, so the default doesn't
14833 have to change as we invent new directory protocol versions.
14834 - Allow people to say PreferTunnelledDirConns rather than
14835 PreferTunneledDirConns, for those alternate-spellers out there.
14836 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
14837 accommodate the growing number of servers that use the default
14838 and are reaching it.
14839 - Make it possible to enable HashedControlPassword and
14840 CookieAuthentication at the same time.
14841 - When a TrackHostExits-chosen exit fails too many times in a row,
14842 stop using it. Fixes bug 437.
14844 o Changed config option behavior (bugfixes):
14845 - Do not read the configuration file when we've only been told to
14846 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
14847 based on patch from Sebastian Hahn.
14848 - Actually validate the options passed to AuthDirReject,
14849 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
14850 - Make "ClientOnly 1" config option disable directory ports too.
14851 - Don't stop fetching descriptors when FetchUselessDescriptors is
14852 set, even if we stop asking for circuits. Bug reported by tup
14854 - Servers used to decline to publish their DirPort if their
14855 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
14856 they look only at BandwidthRate and RelayBandwidthRate.
14857 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14858 minus 1 byte: the actual maximum declared bandwidth.
14859 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
14860 - Make the NodeFamilies config option work. (Reported by
14861 lodger -- it has never actually worked, even though we added it
14863 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14864 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14866 o New config options:
14867 - New configuration options AuthDirMaxServersPerAddr and
14868 AuthDirMaxServersperAuthAddr to override default maximum number
14869 of servers allowed on a single IP address. This is important for
14870 running a test network on a single host.
14871 - Three new config options (AlternateDirAuthority,
14872 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
14873 user selectively replace the default directory authorities by type,
14874 rather than the all-or-nothing replacement that DirServer offers.
14875 - New config options AuthDirBadDir and AuthDirListBadDirs for
14876 authorities to mark certain relays as "bad directories" in the
14877 networkstatus documents. Also supports the "!baddir" directive in
14878 the approved-routers file.
14879 - New config option V2AuthoritativeDirectory that all v2 directory
14880 authorities must set. This lets v3 authorities choose not to serve
14881 v2 directory information.
14883 o Minor features (other):
14884 - When we're not serving v2 directory information, there is no reason
14885 to actually keep any around. Remove the obsolete files and directory
14886 on startup if they are very old and we aren't going to serve them.
14887 - When we negotiate a v2 link-layer connection (not yet implemented),
14888 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14889 negotiated a v1 connection for their next step. Initial steps for
14891 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14892 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14893 we can start out knowing some directory caches. We don't ship with
14894 a fallback consensus by default though, because it was making
14895 bootstrapping take too long while we tried many down relays.
14896 - Authorities send back an X-Descriptor-Not-New header in response to
14897 an accepted-but-discarded descriptor upload. Partially implements
14899 - If we find a cached-routers file that's been sitting around for more
14900 than 28 days unmodified, then most likely it's a leftover from
14901 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
14903 - When we (as a cache) download a descriptor because it was listed
14904 in a consensus, remember when the consensus was supposed to expire,
14905 and don't expire the descriptor until then.
14906 - Optionally (if built with -DEXPORTMALLINFO) export the output
14907 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14909 - Tag every guard node in our state file with the version that
14910 we believe added it, or with our own version if we add it. This way,
14911 if a user temporarily runs an old version of Tor and then switches
14912 back to a new one, she doesn't automatically lose her guards.
14913 - When somebody requests a list of statuses or servers, and we have
14914 none of those, return a 404 rather than an empty 200.
14915 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
14917 - Add an HSAuthorityRecordStats option that hidden service authorities
14918 can use to track statistics of overall hidden service usage without
14919 logging information that would be as useful to an attacker.
14920 - Allow multiple HiddenServicePort directives with the same virtual
14921 port; when they occur, the user is sent round-robin to one
14922 of the target ports chosen at random. Partially fixes bug 393 by
14923 adding limited ad-hoc round-robining.
14924 - Revamp file-writing logic so we don't need to have the entire
14925 contents of a file in memory at once before we write to disk. Tor,
14928 o Minor bugfixes (other):
14929 - Alter the code that tries to recover from unhandled write
14930 errors, to not try to flush onto a socket that's given us
14932 - Directory mirrors no longer include a guess at the client's IP
14933 address if the connection appears to be coming from the same /24
14934 network; it was producing too many wrong guesses.
14935 - If we're trying to flush the last bytes on a connection (for
14936 example, when answering a directory request), reset the
14937 time-to-give-up timeout every time we manage to write something
14939 - Reject router descriptors with out-of-range bandwidthcapacity or
14940 bandwidthburst values.
14941 - If we can't expand our list of entry guards (e.g. because we're
14942 using bridges or we have StrictEntryNodes set), don't mark relays
14943 down when they fail a directory request. Otherwise we're too quick
14944 to mark all our entry points down.
14945 - Authorities no longer send back "400 you're unreachable please fix
14946 it" errors to Tor servers that aren't online all the time. We're
14947 supposed to tolerate these servers now.
14948 - Let directory authorities startup even when they can't generate
14949 a descriptor immediately, e.g. because they don't know their
14951 - Correctly enforce that elements of directory objects do not appear
14952 more often than they are allowed to appear.
14953 - Stop allowing hibernating servers to be "stable" or "fast".
14954 - On Windows, we were preventing other processes from reading
14955 cached-routers while Tor was running. (Reported by janbar)
14956 - Check return values from pthread_mutex functions.
14957 - When opening /dev/null in finish_daemonize(), do not pass the
14958 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
14959 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
14961 o Controller features:
14962 - The GETCONF command now escapes and quotes configuration values
14963 that don't otherwise fit into the torrc file.
14964 - The SETCONF command now handles quoted values correctly.
14965 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14966 ask about source, timestamp of arrival, purpose, etc. We need
14967 something like this to help Vidalia not do GeoIP lookups on bridge
14969 - Allow multiple HashedControlPassword config lines, to support
14970 multiple controller passwords.
14971 - Accept LF instead of CRLF on controller, since some software has a
14972 hard time generating real Internet newlines.
14973 - Add GETINFO values for the server status events
14974 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
14976 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14977 GETINFO for Torstat to use until it can switch to using extrainfos.
14978 - New config option CookieAuthFile to choose a new location for the
14979 cookie authentication file, and config option
14980 CookieAuthFileGroupReadable to make it group-readable.
14981 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
14982 match requests to applications. Patch from Robert Hogan.
14983 - Add a RESOLVE command to launch hostname lookups. Original patch
14985 - Add GETINFO status/enough-dir-info to let controllers tell whether
14986 Tor has downloaded sufficient directory information. Patch from Tup.
14987 - You can now use the ControlSocket option to tell Tor to listen for
14988 controller connections on Unix domain sockets on systems that
14989 support them. Patch from Peter Palfrader.
14990 - New "GETINFO address-mappings/*" command to get address mappings
14991 with expiry information. "addr-mappings/*" is now deprecated.
14993 - Add a new config option __DisablePredictedCircuits designed for
14994 use by the controller, when we don't want Tor to build any circuits
14996 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
14997 so we can exit from the middle of the circuit.
14998 - Implement "getinfo status/circuit-established".
14999 - Implement "getinfo status/version/..." so a controller can tell
15000 whether the current version is recommended, and whether any versions
15001 are good, and how many authorities agree. Patch from "shibz".
15002 - Controllers should now specify cache=no or cache=yes when using
15003 the +POSTDESCRIPTOR command.
15004 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
15005 Robert Hogan. Fixes the first part of bug 681.
15006 - When reporting clock skew, and we know that the clock is _at least
15007 as skewed_ as some value, but we don't know the actual value,
15008 report the value as a "minimum skew."
15010 o Controller bugfixes:
15011 - Generate "STATUS_SERVER" events rather than misspelled
15012 "STATUS_SEVER" events. Caught by mwenge.
15013 - Reject controller commands over 1MB in length, so rogue
15014 processes can't run us out of memory.
15015 - Change the behavior of "getinfo status/good-server-descriptor"
15016 so it doesn't return failure when any authority disappears.
15017 - Send NAMESERVER_STATUS messages for a single failed nameserver
15019 - When the DANGEROUS_VERSION controller status event told us we're
15020 running an obsolete version, it used the string "OLD" to describe
15021 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
15022 "OBSOLETE" in both cases.
15023 - Respond to INT and TERM SIGNAL commands before we execute the
15024 signal, in case the signal shuts us down. We had a patch in
15025 0.1.2.1-alpha that tried to do this by queueing the response on
15026 the connection's buffer before shutting down, but that really
15027 isn't the same thing at all. Bug located by Matt Edman.
15028 - Provide DNS expiry times in GMT, not in local time. For backward
15029 compatibility, ADDRMAP events only provide GMT expiry in an extended
15030 field. "GETINFO address-mappings" always does the right thing.
15031 - Use CRLF line endings properly in NS events.
15032 - Make 'getinfo fingerprint' return a 551 error if we're not a
15033 server, so we match what the control spec claims we do. Reported
15035 - Fix a typo in an error message when extendcircuit fails that
15036 caused us to not follow the \r\n-based delimiter protocol. Reported
15038 - When tunneling an encrypted directory connection, and its first
15039 circuit fails, do not leave it unattached and ask the controller
15040 to deal. Fixes the second part of bug 681.
15041 - Treat some 403 responses from directory servers as INFO rather than
15042 WARN-severity events.
15044 o Portability / building / compiling:
15045 - When building with --enable-gcc-warnings, check for whether Apple's
15046 warning "-Wshorten-64-to-32" is available.
15047 - Support compilation to target iPhone; patch from cjacker huang.
15048 To build for iPhone, pass the --enable-iphone option to configure.
15049 - Port Tor to build and run correctly on Windows CE systems, using
15050 the wcecompat library. Contributed by Valerio Lupi.
15051 - Detect non-ASCII platforms (if any still exist) and refuse to
15052 build there: some of our code assumes that 'A' is 65 and so on.
15053 - Clear up some MIPSPro compiler warnings.
15054 - Make autoconf search for libevent, openssl, and zlib consistently.
15055 - Update deprecated macros in configure.in.
15056 - When warning about missing headers, tell the user to let us
15057 know if the compile succeeds anyway, so we can downgrade the
15059 - Include the current subversion revision as part of the version
15060 string: either fetch it directly if we're in an SVN checkout, do
15061 some magic to guess it if we're in an SVK checkout, or use
15062 the last-detected version if we're building from a .tar.gz.
15063 Use this version consistently in log messages.
15064 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15065 - Read resolv.conf files correctly on platforms where read() returns
15066 partial results on small file reads.
15067 - Build without verbose warnings even on gcc 4.2 and 4.3.
15068 - On Windows, correctly detect errors when listing the contents of
15069 a directory. Fix from lodger.
15070 - Run 'make test' as part of 'make dist', so we stop releasing so
15071 many development snapshots that fail their unit tests.
15072 - Add support to detect Libevent versions in the 1.4.x series
15074 - Add command-line arguments to unit-test executable so that we can
15075 invoke any chosen test from the command line rather than having
15076 to run the whole test suite at once; and so that we can turn on
15077 logging for the unit tests.
15078 - Do not automatically run configure from autogen.sh. This
15079 non-standard behavior tended to annoy people who have built other
15081 - Fix a macro/CPP interaction that was confusing some compilers:
15082 some GCCs don't like #if/#endif pairs inside macro arguments.
15084 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
15085 Fixes bug 704; fix from Steven Murdoch.
15086 - Correctly detect transparent proxy support on Linux hosts that
15087 require in.h to be included before netfilter_ipv4.h. Patch
15090 o Logging improvements:
15091 - When we haven't had any application requests lately, don't bother
15092 logging that we have expired a bunch of descriptors.
15093 - When attempting to open a logfile fails, tell us why.
15094 - Only log guard node status when guard node status has changed.
15095 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
15096 make "INFO" 75% less verbose.
15097 - When SafeLogging is disabled, log addresses along with all TLS
15099 - Report TLS "zero return" case as a "clean close" and "IO error"
15100 as a "close". Stop calling closes "unexpected closes": existing
15101 Tors don't use SSL_close(), so having a connection close without
15102 the TLS shutdown handshake is hardly unexpected.
15103 - When we receive a consensus from the future, warn about skew.
15104 - Make "not enough dir info yet" warnings describe *why* Tor feels
15105 it doesn't have enough directory info yet.
15106 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
15107 consumers. (We already do this on HUP.)
15108 - Give more descriptive well-formedness errors for out-of-range
15109 hidden service descriptor/protocol versions.
15110 - Stop recommending that every server operator send mail to tor-ops.
15111 Resolves bug 597. Bugfix on 0.1.2.x.
15112 - Improve skew reporting: try to give the user a better log message
15113 about how skewed they are, and how much this matters.
15114 - New --quiet command-line option to suppress the default console log.
15115 Good in combination with --hash-password.
15116 - Don't complain that "your server has not managed to confirm that its
15117 ports are reachable" if we haven't been able to build any circuits
15119 - Detect the reason for failing to mmap a descriptor file we just
15120 wrote, and give a more useful log message. Fixes bug 533.
15121 - Always prepend "Bug: " to any log message about a bug.
15122 - When dumping memory usage, list bytes used in buffer memory
15124 - When running with dmalloc, dump more stats on hup and on exit.
15125 - Put a platform string (e.g. "Linux i686") in the startup log
15126 message, so when people paste just their logs, we know if it's
15127 OpenBSD or Windows or what.
15128 - When logging memory usage, break down memory used in buffers by
15130 - When we are reporting the DirServer line we just parsed, we were
15131 logging the second stanza of the key fingerprint, not the first.
15132 - Even though Windows is equally happy with / and \ as path separators,
15133 try to use \ consistently on Windows and / consistently on Unix: it
15134 makes the log messages nicer.
15135 - On OSX, stop warning the user that kqueue support in libevent is
15136 "experimental", since it seems to have worked fine for ages.
15138 o Contributed scripts and tools:
15139 - Update linux-tor-prio.sh script to allow QoS based on the uid of
15140 the Tor process. Patch from Marco Bonetti with tweaks from Mike
15142 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15143 Unix users an easy way to script their Tor process (e.g. by
15144 adjusting bandwidth based on the time of the day).
15145 - In the exitlist script, only consider the most recently published
15146 server descriptor for each server. Also, when the user requests
15147 a list of servers that _reject_ connections to a given address,
15148 explicitly exclude the IPs that also have servers that accept
15149 connections to that address. Resolves bug 405.
15150 - Include a new contrib/tor-exit-notice.html file that exit relay
15151 operators can put on their website to help reduce abuse queries.
15153 o Newly deprecated features:
15154 - The status/version/num-versioning and status/version/num-concurring
15155 GETINFO controller options are no longer useful in the v3 directory
15156 protocol: treat them as deprecated, and warn when they're used.
15157 - The RedirectExits config option is now deprecated.
15159 o Removed features:
15160 - Drop the old code to choke directory connections when the
15161 corresponding OR connections got full: thanks to the cell queue
15162 feature, OR conns don't get full any more.
15163 - Remove the old "dns worker" server DNS code: it hasn't been default
15164 since 0.1.2.2-alpha, and all the servers are using the new
15166 - Remove the code to generate the oldest (v1) directory format.
15167 - Remove support for the old bw_accounting file: we've been storing
15168 bandwidth accounting information in the state file since
15169 0.1.2.5-alpha. This may result in bandwidth accounting errors
15170 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15171 downgrade to 0.1.1.x or earlier.
15172 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
15173 it, it had no AES, and it hasn't seen any security patches since
15175 - Stop overloading the circuit_t.onionskin field for both "onionskin
15176 from a CREATE cell that we are waiting for a cpuworker to be
15177 assigned" and "onionskin from an EXTEND cell that we are going to
15178 send to an OR as soon as we are connected". Might help with bug 600.
15179 - Remove the tor_strpartition() function: its logic was confused,
15180 and it was only used for one thing that could be implemented far
15182 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15183 and TorControl.py, as they use the old v0 controller protocol,
15184 and are obsoleted by TorFlow anyway.
15185 - Drop support for v1 rendezvous descriptors, since we never used
15186 them anyway, and the code has probably rotted by now. Based on
15187 patch from Karsten Loesing.
15188 - Stop allowing address masks that do not correspond to bit prefixes.
15189 We have warned about these for a really long time; now it's time
15190 to reject them. (Patch from croup.)
15191 - Remove an optimization in the AES counter-mode code that assumed
15192 that the counter never exceeded 2^68. When the counter can be set
15193 arbitrarily as an IV (as it is by Karsten's new hidden services
15194 code), this assumption no longer holds.
15195 - Disable the SETROUTERPURPOSE controller command: it is now
15199 Changes in version 0.1.2.19 - 2008-01-17
15200 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
15201 exit policy a little bit more conservative so it's safer to run an
15202 exit relay on a home system, and fixes a variety of smaller issues.
15205 - Exit policies now reject connections that are addressed to a
15206 relay's public (external) IP address too, unless
15207 ExitPolicyRejectPrivate is turned off. We do this because too
15208 many relays are running nearby to services that trust them based
15209 on network address.
15212 - When the clock jumps forward a lot, do not allow the bandwidth
15213 buckets to become negative. Fixes bug 544.
15214 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
15215 on every successful resolve. Reported by Mike Perry.
15216 - Purge old entries from the "rephist" database and the hidden
15217 service descriptor database even when DirPort is zero.
15218 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
15219 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
15220 crashing or mis-answering these requests.
15221 - When we decide to send a 503 response to a request for servers, do
15222 not then also send the server descriptors: this defeats the whole
15223 purpose. Fixes bug 539.
15226 - Changing the ExitPolicyRejectPrivate setting should cause us to
15227 rebuild our server descriptor.
15228 - Fix handling of hex nicknames when answering controller requests for
15229 networkstatus by name, or when deciding whether to warn about
15230 unknown routers in a config option. (Patch from mwenge.)
15231 - Fix a couple of hard-to-trigger autoconf problems that could result
15232 in really weird results on platforms whose sys/types.h files define
15233 nonstandard integer types.
15234 - Don't try to create the datadir when running --verify-config or
15235 --hash-password. Resolves bug 540.
15236 - If we were having problems getting a particular descriptor from the
15237 directory caches, and then we learned about a new descriptor for
15238 that router, we weren't resetting our failure count. Reported
15240 - Although we fixed bug 539 (where servers would send HTTP status 503
15241 responses _and_ send a body too), there are still servers out there
15242 that haven't upgraded. Therefore, make clients parse such bodies
15243 when they receive them.
15244 - Run correctly on systems where rlim_t is larger than unsigned long.
15245 This includes some 64-bit systems.
15246 - Run correctly on platforms (like some versions of OS X 10.5) where
15247 the real limit for number of open files is OPEN_FILES, not rlim_max
15248 from getrlimit(RLIMIT_NOFILES).
15249 - Avoid a spurious free on base64 failure.
15250 - Avoid segfaults on certain complex invocations of
15251 router_get_by_hexdigest().
15252 - Fix rare bug on REDIRECTSTREAM control command when called with no
15253 port set: it could erroneously report an error when none had
15257 Changes in version 0.1.2.18 - 2007-10-28
15258 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
15259 hidden service introduction that were causing huge delays, and a big
15260 bug that was causing some servers to disappear from the network status
15261 lists for a few hours each day.
15263 o Major bugfixes (crashes):
15264 - If a connection is shut down abruptly because of something that
15265 happened inside connection_flushed_some(), do not call
15266 connection_finished_flushing(). Should fix bug 451:
15267 "connection_stop_writing: Assertion conn->write_event failed"
15268 Bugfix on 0.1.2.7-alpha.
15269 - Fix possible segfaults in functions called from
15270 rend_process_relay_cell().
15272 o Major bugfixes (hidden services):
15273 - Hidden services were choosing introduction points uniquely by
15274 hexdigest, but when constructing the hidden service descriptor
15275 they merely wrote the (potentially ambiguous) nickname.
15276 - Clients now use the v2 intro format for hidden service
15277 connections: they specify their chosen rendezvous point by identity
15278 digest rather than by (potentially ambiguous) nickname. These
15279 changes could speed up hidden service connections dramatically.
15281 o Major bugfixes (other):
15282 - Stop publishing a new server descriptor just because we get a
15283 HUP signal. This led (in a roundabout way) to some servers getting
15284 dropped from the networkstatus lists for a few hours each day.
15285 - When looking for a circuit to cannibalize, consider family as well
15286 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15287 circuit cannibalization).
15288 - When a router wasn't listed in a new networkstatus, we were leaving
15289 the flags for that router alone -- meaning it remained Named,
15290 Running, etc -- even though absence from the networkstatus means
15291 that it shouldn't be considered to exist at all anymore. Now we
15292 clear all the flags for routers that fall out of the networkstatus
15293 consensus. Fixes bug 529.
15296 - Don't try to access (or alter) the state file when running
15297 --list-fingerprint or --verify-config or --hash-password. Resolves
15299 - When generating information telling us how to extend to a given
15300 router, do not try to include the nickname if it is
15301 absent. Resolves bug 467.
15302 - Fix a user-triggerable segfault in expand_filename(). (There isn't
15303 a way to trigger this remotely.)
15304 - When sending a status event to the controller telling it that an
15305 OR address is reachable, set the port correctly. (Previously we
15306 were reporting the dir port.)
15307 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15308 command. Bugfix on 0.1.2.17.
15309 - When loading bandwidth history, do not believe any information in
15310 the future. Fixes bug 434.
15311 - When loading entry guard information, do not believe any information
15313 - When we have our clock set far in the future and generate an
15314 onion key, then re-set our clock to be correct, we should not stop
15315 the onion key from getting rotated.
15316 - On some platforms, accept() can return a broken address. Detect
15317 this more quietly, and deal accordingly. Fixes bug 483.
15318 - It's not actually an error to find a non-pending entry in the DNS
15319 cache when canceling a pending resolve. Don't log unless stuff
15320 is fishy. Resolves bug 463.
15321 - Don't reset trusted dir server list when we set a configuration
15322 option. Patch from Robert Hogan.
15325 Changes in version 0.1.2.17 - 2007-08-30
15326 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
15327 X bundles. Vidalia 0.0.14 makes authentication required for the
15328 ControlPort in the default configuration, which addresses important
15329 security risks. Everybody who uses Vidalia (or another controller)
15332 In addition, this Tor update fixes major load balancing problems with
15333 path selection, which should speed things up a lot once many people
15336 o Major bugfixes (security):
15337 - We removed support for the old (v0) control protocol. It has been
15338 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
15339 become more of a headache than it's worth.
15341 o Major bugfixes (load balancing):
15342 - When choosing nodes for non-guard positions, weight guards
15343 proportionally less, since they already have enough load. Patch
15345 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15346 will allow fast Tor servers to get more attention.
15347 - When we're upgrading from an old Tor version, forget our current
15348 guards and pick new ones according to the new weightings. These
15349 three load balancing patches could raise effective network capacity
15350 by a factor of four. Thanks to Mike Perry for measurements.
15352 o Major bugfixes (stream expiration):
15353 - Expire not-yet-successful application streams in all cases if
15354 they've been around longer than SocksTimeout. Right now there are
15355 some cases where the stream will live forever, demanding a new
15356 circuit every 15 seconds. Fixes bug 454; reported by lodger.
15358 o Minor features (controller):
15359 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15360 is valid before any authentication has been received. It tells
15361 a controller what kind of authentication is expected, and what
15362 protocol is spoken. Implements proposal 119.
15364 o Minor bugfixes (performance):
15365 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
15366 greatly speeding up loading cached-routers from disk on startup.
15367 - Disable sentinel-based debugging for buffer code: we squashed all
15368 the bugs that this was supposed to detect a long time ago, and now
15369 its only effect is to change our buffer sizes from nice powers of
15370 two (which platform mallocs tend to like) to values slightly over
15371 powers of two (which make some platform mallocs sad).
15373 o Minor bugfixes (misc):
15374 - If exit bandwidth ever exceeds one third of total bandwidth, then
15375 use the correct formula to weight exit nodes when choosing paths.
15376 Based on patch from Mike Perry.
15377 - Choose perfectly fairly among routers when choosing by bandwidth and
15378 weighting by fraction of bandwidth provided by exits. Previously, we
15379 would choose with only approximate fairness, and correct ourselves
15380 if we ran off the end of the list.
15381 - If we require CookieAuthentication but we fail to write the
15382 cookie file, we would warn but not exit, and end up in a state
15383 where no controller could authenticate. Now we exit.
15384 - If we require CookieAuthentication, stop generating a new cookie
15385 every time we change any piece of our config.
15386 - Refuse to start with certain directory authority keys, and
15387 encourage people using them to stop.
15388 - Terminate multi-line control events properly. Original patch
15390 - Fix a minor memory leak when we fail to find enough suitable
15391 servers to choose a circuit.
15392 - Stop leaking part of the descriptor when we run into a particularly
15393 unparseable piece of it.
15396 Changes in version 0.1.2.16 - 2007-08-01
15397 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
15398 remote attacker in certain situations to rewrite the user's torrc
15399 configuration file. This can completely compromise anonymity of users
15400 in most configurations, including those running the Vidalia bundles,
15401 TorK, etc. Or worse.
15403 o Major security fixes:
15404 - Close immediately after missing authentication on control port;
15405 do not allow multiple authentication attempts.
15408 Changes in version 0.1.2.15 - 2007-07-17
15409 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
15410 problems, fixes compilation on BSD, and fixes a variety of other
15411 bugs. Everybody should upgrade.
15413 o Major bugfixes (compilation):
15414 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
15416 o Major bugfixes (crashes):
15417 - Try even harder not to dereference the first character after
15418 an mmap(). Reported by lodger.
15419 - Fix a crash bug in directory authorities when we re-number the
15420 routerlist while inserting a new router.
15421 - When the cached-routers file is an even multiple of the page size,
15422 don't run off the end and crash. (Fixes bug 455; based on idea
15424 - Fix eventdns.c behavior on Solaris: It is critical to include
15425 orconfig.h _before_ sys/types.h, so that we can get the expected
15426 definition of _FILE_OFFSET_BITS.
15428 o Major bugfixes (security):
15429 - Fix a possible buffer overrun when using BSD natd support. Bug
15431 - When sending destroy cells from a circuit's origin, don't include
15432 the reason for tearing down the circuit. The spec says we didn't,
15433 and now we actually don't. Reported by lodger.
15434 - Keep streamids from different exits on a circuit separate. This
15435 bug may have allowed other routers on a given circuit to inject
15436 cells into streams. Reported by lodger; fixes bug 446.
15437 - If there's a never-before-connected-to guard node in our list,
15438 never choose any guards past it. This way we don't expand our
15439 guard list unless we need to.
15441 o Minor bugfixes (guard nodes):
15442 - Weight guard selection by bandwidth, so that low-bandwidth nodes
15443 don't get overused as guards.
15445 o Minor bugfixes (directory):
15446 - Correctly count the number of authorities that recommend each
15447 version. Previously, we were under-counting by 1.
15448 - Fix a potential crash bug when we load many server descriptors at
15449 once and some of them make others of them obsolete. Fixes bug 458.
15451 o Minor bugfixes (hidden services):
15452 - Stop tearing down the whole circuit when the user asks for a
15453 connection to a port that the hidden service didn't configure.
15456 o Minor bugfixes (misc):
15457 - On Windows, we were preventing other processes from reading
15458 cached-routers while Tor was running. Reported by janbar.
15459 - Fix a possible (but very unlikely) bug in picking routers by
15460 bandwidth. Add a log message to confirm that it is in fact
15461 unlikely. Patch from lodger.
15462 - Backport a couple of memory leak fixes.
15463 - Backport miscellaneous cosmetic bugfixes.
15466 Changes in version 0.1.2.14 - 2007-05-25
15467 Tor 0.1.2.14 changes the addresses of two directory authorities (this
15468 change especially affects those who serve or use hidden services),
15469 and fixes several other crash- and security-related bugs.
15471 o Directory authority changes:
15472 - Two directory authorities (moria1 and moria2) just moved to new
15473 IP addresses. This change will particularly affect those who serve
15474 or use hidden services.
15476 o Major bugfixes (crashes):
15477 - If a directory server runs out of space in the connection table
15478 as it's processing a begin_dir request, it will free the exit stream
15479 but leave it attached to the circuit, leading to unpredictable
15480 behavior. (Reported by seeess, fixes bug 425.)
15481 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15482 to corrupt memory under some really unlikely scenarios.
15483 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15484 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15487 o Major bugfixes (security):
15488 - When choosing an entry guard for a circuit, avoid using guards
15489 that are in the same family as the chosen exit -- not just guards
15490 that are exactly the chosen exit. (Reported by lodger.)
15492 o Major bugfixes (resource management):
15493 - If a directory authority is down, skip it when deciding where to get
15494 networkstatus objects or descriptors. Otherwise we keep asking
15495 every 10 seconds forever. Fixes bug 384.
15496 - Count it as a failure if we fetch a valid network-status but we
15497 don't want to keep it. Otherwise we'll keep fetching it and keep
15498 not wanting to keep it. Fixes part of bug 422.
15499 - If all of our dirservers have given us bad or no networkstatuses
15500 lately, then stop hammering them once per minute even when we
15501 think they're failed. Fixes another part of bug 422.
15504 - Actually set the purpose correctly for descriptors inserted with
15505 purpose=controller.
15506 - When we have k non-v2 authorities in our DirServer config,
15507 we ignored the last k authorities in the list when updating our
15509 - Correctly back-off from requesting router descriptors that we are
15510 having a hard time downloading.
15511 - Read resolv.conf files correctly on platforms where read() returns
15512 partial results on small file reads.
15513 - Don't rebuild the entire router store every time we get 32K of
15514 routers: rebuild it when the journal gets very large, or when
15515 the gaps in the store get very large.
15518 - When routers publish SVN revisions in their router descriptors,
15519 authorities now include those versions correctly in networkstatus
15521 - Warn when using a version of libevent before 1.3b to run a server on
15522 OSX or BSD: these versions interact badly with userspace threads.
15525 Changes in version 0.1.2.13 - 2007-04-24
15526 This release features some major anonymity fixes, such as safer path
15527 selection; better client performance; faster bootstrapping, better
15528 address detection, and better DNS support for servers; write limiting as
15529 well as read limiting to make servers easier to run; and a huge pile of
15530 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15532 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15533 of the Freenode IRC network, remembering his patience and vision for
15534 free speech on the Internet.
15536 o Major features, client performance:
15537 - Weight directory requests by advertised bandwidth. Now we can
15538 let servers enable write limiting but still allow most clients to
15539 succeed at their directory requests. (We still ignore weights when
15540 choosing a directory authority; I hope this is a feature.)
15541 - Stop overloading exit nodes -- avoid choosing them for entry or
15542 middle hops when the total bandwidth available from non-exit nodes
15543 is much higher than the total bandwidth available from exit nodes.
15544 - Rather than waiting a fixed amount of time between retrying
15545 application connections, we wait only 10 seconds for the first,
15546 10 seconds for the second, and 15 seconds for each retry after
15547 that. Hopefully this will improve the expected user experience.
15548 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15549 to open a stream fails; now we do in more cases. This should
15550 make clients able to find a good exit faster in some cases, since
15551 unhandleable requests will now get an error rather than timing out.
15553 o Major features, client functionality:
15554 - Implement BEGIN_DIR cells, so we can connect to a directory
15555 server via TLS to do encrypted directory requests rather than
15556 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15557 config options if you like. For now, this feature only works if
15558 you already have a descriptor for the destination dirserver.
15559 - Add support for transparent application connections: this basically
15560 bundles the functionality of trans-proxy-tor into the Tor
15561 mainline. Now hosts with compliant pf/netfilter implementations
15562 can redirect TCP connections straight to Tor without diverting
15563 through SOCKS. (Based on patch from tup.)
15564 - Add support for using natd; this allows FreeBSDs earlier than
15565 5.1.2 to have ipfw send connections through Tor without using
15566 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15568 o Major features, servers:
15569 - Setting up a dyndns name for your server is now optional: servers
15570 with no hostname or IP address will learn their IP address by
15571 asking the directory authorities. This code only kicks in when you
15572 would normally have exited with a "no address" error. Nothing's
15573 authenticated, so use with care.
15574 - Directory servers now spool server descriptors, v1 directories,
15575 and v2 networkstatus objects to buffers as needed rather than en
15576 masse. They also mmap the cached-routers files. These steps save
15578 - Stop requiring clients to have well-formed certificates, and stop
15579 checking nicknames in certificates. (Clients have certificates so
15580 that they can look like Tor servers, but in the future we might want
15581 to allow them to look like regular TLS clients instead. Nicknames
15582 in certificates serve no purpose other than making our protocol
15583 easier to recognize on the wire.) Implements proposal 106.
15585 o Improvements on DNS support:
15586 - Add "eventdns" asynchronous dns library originally based on code
15587 from Adam Langley. Now we can discard the old rickety dnsworker
15588 concept, and support a wider variety of DNS functions. Allows
15589 multithreaded builds on NetBSD and OpenBSD again.
15590 - Add server-side support for "reverse" DNS lookups (using PTR
15591 records so clients can determine the canonical hostname for a given
15592 IPv4 address). Only supported by servers using eventdns; servers
15593 now announce in their descriptors if they don't support eventdns.
15594 - Workaround for name servers (like Earthlink's) that hijack failing
15595 DNS requests and replace the no-such-server answer with a "helpful"
15596 redirect to an advertising-driven search portal. Also work around
15597 DNS hijackers who "helpfully" decline to hijack known-invalid
15598 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15599 lets you turn it off.
15600 - Servers now check for the case when common DNS requests are going to
15601 wildcarded addresses (i.e. all getting the same answer), and change
15602 their exit policy to reject *:* if it's happening.
15603 - When asked to resolve a hostname, don't use non-exit servers unless
15604 requested to do so. This allows servers with broken DNS to be
15605 useful to the network.
15606 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15607 useless IPv6 DNS resolves.
15608 - Specify and implement client-side SOCKS5 interface for reverse DNS
15609 lookups (see doc/socks-extensions.txt). Also cache them.
15610 - When we change nameservers or IP addresses, reset and re-launch
15611 our tests for DNS hijacking.
15613 o Improvements on reachability testing:
15614 - Servers send out a burst of long-range padding cells once they've
15615 established that they're reachable. Spread them over 4 circuits,
15616 so hopefully a few will be fast. This exercises bandwidth and
15617 bootstraps them into the directory more quickly.
15618 - When we find our DirPort to be reachable, publish a new descriptor
15619 so we'll tell the world (reported by pnx).
15620 - Directory authorities now only decide that routers are reachable
15621 if their identity keys are as expected.
15622 - Do DirPort reachability tests less often, since a single test
15623 chews through many circuits before giving up.
15624 - Avoid some false positives during reachability testing: don't try
15625 to test via a server that's on the same /24 network as us.
15626 - Start publishing one minute or so after we find our ORPort
15627 to be reachable. This will help reduce the number of descriptors
15628 we have for ourselves floating around, since it's quite likely
15629 other things (e.g. DirPort) will change during that minute too.
15630 - Routers no longer try to rebuild long-term connections to directory
15631 authorities, and directory authorities no longer try to rebuild
15632 long-term connections to all servers. We still don't hang up
15633 connections in these two cases though -- we need to look at it
15634 more carefully to avoid flapping, and we likely need to wait til
15635 0.1.1.x is obsolete.
15637 o Improvements on rate limiting:
15638 - Enable write limiting as well as read limiting. Now we sacrifice
15639 capacity if we're pushing out lots of directory traffic, rather
15640 than overrunning the user's intended bandwidth limits.
15641 - Include TLS overhead when counting bandwidth usage; previously, we
15642 would count only the bytes sent over TLS, but not the bytes used
15644 - Servers decline directory requests much more aggressively when
15645 they're low on bandwidth. Otherwise they end up queueing more and
15646 more directory responses, which can't be good for latency.
15647 - But never refuse directory requests from local addresses.
15648 - Be willing to read or write on local connections (e.g. controller
15649 connections) even when the global rate limiting buckets are empty.
15650 - Flush local controller connection buffers periodically as we're
15651 writing to them, so we avoid queueing 4+ megabytes of data before
15653 - Revise and clean up the torrc.sample that we ship with; add
15654 a section for BandwidthRate and BandwidthBurst.
15656 o Major features, NT services:
15657 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15658 command-line flag so that admins can override the default by saying
15659 "tor --service install --user "SomeUser"". This will not affect
15660 existing installed services. Also, warn the user that the service
15661 will look for its configuration file in the service user's
15662 %appdata% directory. (We can't do the "hardwire the user's appdata
15663 directory" trick any more, since we may not have read access to that
15665 - Support running the Tor service with a torrc not in the same
15666 directory as tor.exe and default to using the torrc located in
15667 the %appdata%\Tor\ of the user who installed the service. Patch
15669 - Add an --ignore-missing-torrc command-line option so that we can
15670 get the "use sensible defaults if the configuration file doesn't
15671 exist" behavior even when specifying a torrc location on the
15673 - When stopping an NT service, wait up to 10 sec for it to actually
15674 stop. (Patch from Matt Edman; resolves bug 295.)
15676 o Directory authority improvements:
15677 - Stop letting hibernating or obsolete servers affect uptime and
15679 - Stop listing hibernating servers in the v1 directory.
15680 - Authorities no longer recommend exits as guards if this would shift
15681 too much load to the exit nodes.
15682 - Authorities now specify server versions in networkstatus. This adds
15683 about 2% to the size of compressed networkstatus docs, and allows
15684 clients to tell which servers support BEGIN_DIR and which don't.
15685 The implementation is forward-compatible with a proposed future
15686 protocol version scheme not tied to Tor versions.
15687 - DirServer configuration lines now have an orport= option so
15688 clients can open encrypted tunnels to the authorities without
15689 having downloaded their descriptors yet. Enabled for moria1,
15690 moria2, tor26, and lefkada now in the default configuration.
15691 - Add a BadDirectory flag to network status docs so that authorities
15692 can (eventually) tell clients about caches they believe to be
15693 broken. Not used yet.
15694 - Allow authorities to list nodes as bad exits in their
15695 approved-routers file by fingerprint or by address. If most
15696 authorities set a BadExit flag for a server, clients don't think
15697 of it as a general-purpose exit. Clients only consider authorities
15698 that advertise themselves as listing bad exits.
15699 - Patch from Steve Hildrey: Generate network status correctly on
15700 non-versioning dirservers.
15701 - Have directory authorities allow larger amounts of drift in uptime
15702 without replacing the server descriptor: previously, a server that
15703 restarted every 30 minutes could have 48 "interesting" descriptors
15705 - Reserve the nickname "Unnamed" for routers that can't pick
15706 a hostname: any router can call itself Unnamed; directory
15707 authorities will never allocate Unnamed to any particular router;
15708 clients won't believe that any router is the canonical Unnamed.
15710 o Directory mirrors and clients:
15711 - Discard any v1 directory info that's over 1 month old (for
15712 directories) or over 1 week old (for running-routers lists).
15713 - Clients track responses with status 503 from dirservers. After a
15714 dirserver has given us a 503, we try not to use it until an hour has
15715 gone by, or until we have no dirservers that haven't given us a 503.
15716 - When we get a 503 from a directory, and we're not a server, we no
15717 longer count the failure against the total number of failures
15718 allowed for the object we're trying to download.
15719 - Prepare for servers to publish descriptors less often: never
15720 discard a descriptor simply for being too old until either it is
15721 recommended by no authorities, or until we get a better one for
15722 the same router. Make caches consider retaining old recommended
15723 routers for even longer.
15724 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15725 headers for content, so that we can work better in the presence of
15726 caching HTTP proxies.
15727 - Stop fetching descriptors if you're not a dir mirror and you
15728 haven't tried to establish any circuits lately. (This currently
15729 causes some dangerous behavior, because when you start up again
15730 you'll use your ancient server descriptors.)
15732 o Major fixes, crashes:
15733 - Stop crashing when the controller asks us to resetconf more than
15734 one config option at once. (Vidalia 0.0.11 does this.)
15735 - Fix a longstanding obscure crash bug that could occur when we run
15736 out of DNS worker processes, if we're not using eventdns. (Resolves
15738 - Fix an assert that could trigger if a controller quickly set then
15739 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
15740 - Avoid crash when telling controller about stream-status and a
15741 stream is detached.
15742 - Avoid sending junk to controllers or segfaulting when a controller
15743 uses EVENT_NEW_DESC with verbose nicknames.
15744 - Stop triggering asserts if the controller tries to extend hidden
15745 service circuits (reported by mwenge).
15746 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15747 and hup, stop triggering an assert based on an empty onion_key.
15748 - Mask out all signals in sub-threads; only the libevent signal
15749 handler should be processing them. This should prevent some crashes
15750 on some machines using pthreads. (Patch from coderman.)
15751 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15753 o Major fixes, anonymity/security:
15754 - Automatically avoid picking more than one node from the same
15755 /16 network when constructing a circuit. Add an
15756 "EnforceDistinctSubnets" option to let people disable it if they
15757 want to operate private test networks on a single subnet.
15758 - When generating bandwidth history, round down to the nearest
15759 1k. When storing accounting data, round up to the nearest 1k.
15760 - When we're running as a server, remember when we last rotated onion
15761 keys, so that we will rotate keys once they're a week old even if
15762 we never stay up for a week ourselves.
15763 - If a client asked for a server by name, and there's a named server
15764 in our network-status but we don't have its descriptor yet, we
15765 could return an unnamed server instead.
15766 - Reject (most) attempts to use Tor circuits with length one. (If
15767 many people start using Tor as a one-hop proxy, exit nodes become
15768 a more attractive target for compromise.)
15769 - Just because your DirPort is open doesn't mean people should be
15770 able to remotely teach you about hidden service descriptors. Now
15771 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15772 - Fix a potential race condition in the rpm installer. Found by
15774 - Do not log IPs with TLS failures for incoming TLS
15775 connections. (Fixes bug 382.)
15777 o Major fixes, other:
15778 - If our system clock jumps back in time, don't publish a negative
15779 uptime in the descriptor.
15780 - When we start during an accounting interval before it's time to wake
15781 up, remember to wake up at the correct time. (May fix bug 342.)
15782 - Previously, we would cache up to 16 old networkstatus documents
15783 indefinitely, if they came from nontrusted authorities. Now we
15784 discard them if they are more than 10 days old.
15785 - When we have a state file we cannot parse, tell the user and
15786 move it aside. Now we avoid situations where the user starts
15787 Tor in 1904, Tor writes a state file with that timestamp in it,
15788 the user fixes her clock, and Tor refuses to start.
15789 - Publish a new descriptor after we hup/reload. This is important
15790 if our config has changed such that we'll want to start advertising
15791 our DirPort now, etc.
15792 - If we are using an exit enclave and we can't connect, e.g. because
15793 its webserver is misconfigured to not listen on localhost, then
15794 back off and try connecting from somewhere else before we fail.
15796 o New config options or behaviors:
15797 - When EntryNodes are configured, rebuild the guard list to contain,
15798 in order: the EntryNodes that were guards before; the rest of the
15799 EntryNodes; the nodes that were guards before.
15800 - Do not warn when individual nodes in the configuration's EntryNodes,
15801 ExitNodes, etc are down: warn only when all possible nodes
15802 are down. (Fixes bug 348.)
15803 - Put a lower-bound on MaxAdvertisedBandwidth.
15804 - Start using the state file to store bandwidth accounting data:
15805 the bw_accounting file is now obsolete. We'll keep generating it
15806 for a while for people who are still using 0.1.2.4-alpha.
15807 - Try to batch changes to the state file so that we do as few
15808 disk writes as possible while still storing important things in
15810 - The state file and the bw_accounting file get saved less often when
15811 the AvoidDiskWrites config option is set.
15812 - Make PIDFile work on Windows.
15813 - Add internal descriptions for a bunch of configuration options:
15814 accessible via controller interface and in comments in saved
15816 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15817 NNTP by default, so this seems like a sensible addition.
15818 - Clients now reject hostnames with invalid characters. This should
15819 avoid some inadvertent info leaks. Add an option
15820 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15821 is running a private network with hosts called @, !, and #.
15822 - Check for addresses with invalid characters at the exit as well,
15823 and warn less verbosely when they fail. You can override this by
15824 setting ServerDNSAllowNonRFC953Addresses to 1.
15825 - Remove some options that have been deprecated since at least
15826 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15827 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15828 to set log options. Mark PathlenCoinWeight as obsolete.
15829 - Stop accepting certain malformed ports in configured exit policies.
15830 - When the user uses bad syntax in the Log config line, stop
15831 suggesting other bad syntax as a replacement.
15832 - Add new config option "ResolvConf" to let the server operator
15833 choose an alternate resolve.conf file when using eventdns.
15834 - If one of our entry guards is on the ExcludeNodes list, or the
15835 directory authorities don't think it's a good guard, treat it as
15836 if it were unlisted: stop using it as a guard, and throw it off
15837 the guards list if it stays that way for a long time.
15838 - Allow directory authorities to be marked separately as authorities
15839 for the v1 directory protocol, the v2 directory protocol, and
15840 as hidden service directories, to make it easier to retire old
15841 authorities. V1 authorities should set "HSAuthoritativeDir 1"
15842 to continue being hidden service authorities too.
15843 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
15844 - Make TrackExitHosts case-insensitive, and fix the behavior of
15845 ".suffix" TrackExitHosts items to avoid matching in the middle of
15847 - New DirPort behavior: if you have your dirport set, you download
15848 descriptors aggressively like a directory mirror, whether or not
15849 your ORPort is set.
15852 - Create a new file ReleaseNotes which was the old ChangeLog. The
15853 new ChangeLog file now includes the notes for all development
15855 - Add a new address-spec.txt document to describe our special-case
15856 addresses: .exit, .onion, and .noconnnect.
15857 - Fork the v1 directory protocol into its own spec document,
15858 and mark dir-spec.txt as the currently correct (v2) spec.
15860 o Packaging, porting, and contrib
15861 - "tor --verify-config" now exits with -1(255) or 0 depending on
15862 whether the config options are bad or good.
15863 - The Debian package now uses --verify-config when (re)starting,
15864 to distinguish configuration errors from other errors.
15865 - Adapt a patch from goodell to let the contrib/exitlist script
15866 take arguments rather than require direct editing.
15867 - Prevent the contrib/exitlist script from printing the same
15868 result more than once.
15869 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15870 - In the hidden service example in torrc.sample, stop recommending
15871 esoteric and discouraged hidden service options.
15872 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
15873 values before failing, and always enables eventdns.
15874 - Try to detect Windows correctly when cross-compiling.
15875 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
15876 Try to fix this in configure.in by checking for most functions
15877 before we check for libevent.
15878 - Update RPMs to require libevent 1.2.
15879 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15880 or later. Log when we are doing this, so we can diagnose it when
15881 it fails. (Also, recommend libevent 1.1b for kqueue and
15882 win32 methods; deprecate libevent 1.0b harder; make libevent
15883 recommendation system saner.)
15884 - Build with recent (1.3+) libevents on platforms that do not
15885 define the nonstandard types "u_int8_t" and friends.
15886 - Remove architecture from OS X builds. The official builds are
15887 now universal binaries.
15888 - Run correctly on OS X platforms with case-sensitive filesystems.
15889 - Correctly set maximum connection limit on Cygwin. (This time
15891 - Start compiling on MinGW on Windows (patches from Mike Chiussi
15893 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15894 - Finally fix the openssl warnings from newer gccs that believe that
15895 ignoring a return value is okay, but casting a return value and
15896 then ignoring it is a sign of madness.
15897 - On architectures where sizeof(int)>4, still clamp declarable
15898 bandwidth to INT32_MAX.
15900 o Minor features, controller:
15901 - Warn the user when an application uses the obsolete binary v0
15902 control protocol. We're planning to remove support for it during
15903 the next development series, so it's good to give people some
15905 - Add STREAM_BW events to report per-entry-stream bandwidth
15906 use. (Patch from Robert Hogan.)
15907 - Rate-limit SIGNEWNYM signals in response to controllers that
15908 impolitely generate them for every single stream. (Patch from
15909 mwenge; closes bug 394.)
15910 - Add a REMAP status to stream events to note that a stream's
15911 address has changed because of a cached address or a MapAddress
15913 - Make REMAP stream events have a SOURCE (cache or exit), and
15914 make them generated in every case where we get a successful
15915 connected or resolved cell.
15916 - Track reasons for OR connection failure; make these reasons
15917 available via the controller interface. (Patch from Mike Perry.)
15918 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15919 can learn when clients are sending malformed hostnames to Tor.
15920 - Specify and implement some of the controller status events.
15921 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15922 - Reimplement GETINFO so that info/names stays in sync with the
15924 - Implement "GETINFO fingerprint".
15925 - Implement "SETEVENTS GUARD" so controllers can get updates on
15926 entry guard status as it changes.
15927 - Make all connections to addresses of the form ".noconnect"
15928 immediately get closed. This lets application/controller combos
15929 successfully test whether they're talking to the same Tor by
15930 watching for STREAM events.
15931 - Add a REASON field to CIRC events; for backward compatibility, this
15932 field is sent only to controllers that have enabled the extended
15933 event format. Also, add additional reason codes to explain why
15934 a given circuit has been destroyed or truncated. (Patches from
15936 - Add a REMOTE_REASON field to extended CIRC events to tell the
15937 controller why a remote OR told us to close a circuit.
15938 - Stream events also now have REASON and REMOTE_REASON fields,
15939 working much like those for circuit events.
15940 - There's now a GETINFO ns/... field so that controllers can ask Tor
15941 about the current status of a router.
15942 - A new event type "NS" to inform a controller when our opinion of
15943 a router's status has changed.
15944 - Add a GETINFO events/names and GETINFO features/names so controllers
15945 can tell which events and features are supported.
15946 - A new CLEARDNSCACHE signal to allow controllers to clear the
15947 client-side DNS cache without expiring circuits.
15948 - Fix CIRC controller events so that controllers can learn the
15949 identity digests of non-Named servers used in circuit paths.
15950 - Let controllers ask for more useful identifiers for servers. Instead
15951 of learning identity digests for un-Named servers and nicknames
15952 for Named servers, the new identifiers include digest, nickname,
15953 and indication of Named status. Off by default; see control-spec.txt
15954 for more information.
15955 - Add a "getinfo address" controller command so it can display Tor's
15956 best guess to the user.
15957 - New controller event to alert the controller when our server
15958 descriptor has changed.
15959 - Give more meaningful errors on controller authentication failure.
15960 - Export the default exit policy via the control port, so controllers
15961 don't need to guess what it is / will be later.
15963 o Minor bugfixes, controller:
15964 - When creating a circuit via the controller, send a 'launched'
15965 event when we're done, so we follow the spec better.
15966 - Correct the control spec to match how the code actually responds
15967 to 'getinfo addr-mappings/*'. Reported by daejees.
15968 - The control spec described a GUARDS event, but the code
15969 implemented a GUARD event. Standardize on GUARD, but let people
15970 ask for GUARDS too. Reported by daejees.
15971 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15972 clear the corresponding on_circuit variable, and remember later
15973 that we don't need to send a redundant CLOSED event. (Resolves part
15975 - Report events where a resolve succeeded or where we got a socks
15976 protocol error correctly, rather than calling both of them
15978 - Change reported stream target addresses to IP consistently when
15979 we finally get the IP from an exit node.
15980 - Send log messages to the controller even if they happen to be very
15982 - Flush ERR-level controller status events just like we currently
15983 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15984 the controller from learning about current events.
15985 - Report the circuit number correctly in STREAM CLOSED events. Bug
15986 reported by Mike Perry.
15987 - Do not report bizarre values for results of accounting GETINFOs
15988 when the last second's write or read exceeds the allotted bandwidth.
15989 - Report "unrecognized key" rather than an empty string when the
15990 controller tries to fetch a networkstatus that doesn't exist.
15991 - When the controller does a "GETINFO network-status", tell it
15992 about even those routers whose descriptors are very old, and use
15993 long nicknames where appropriate.
15994 - Fix handling of verbose nicknames with ORCONN controller events:
15995 make them show up exactly when requested, rather than exactly when
15997 - Controller signals now work on non-Unix platforms that don't define
15998 SIGUSR1 and SIGUSR2 the way we expect.
15999 - Respond to SIGNAL command before we execute the signal, in case
16000 the signal shuts us down. Suggested by Karsten Loesing.
16001 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16003 o Minor features, code performance:
16004 - Major performance improvement on inserting descriptors: change
16005 algorithm from O(n^2) to O(n).
16006 - Do not rotate onion key immediately after setting it for the first
16008 - Call router_have_min_dir_info half as often. (This is showing up in
16009 some profiles, but not others.)
16010 - When using GCC, make log_debug never get called at all, and its
16011 arguments never get evaluated, when no debug logs are configured.
16012 (This is showing up in some profiles, but not others.)
16013 - Statistics dumped by -USR2 now include a breakdown of public key
16014 operations, for profiling.
16015 - Make the common memory allocation path faster on machines where
16016 malloc(0) returns a pointer.
16017 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16018 split connection_t into edge, or, dir, control, and base structs.
16019 These will save quite a bit of memory on busy servers, and they'll
16020 also help us track down bugs in the code and bugs in the spec.
16021 - Use OpenSSL's AES implementation on platforms where it's faster.
16022 This could save us as much as 10% CPU usage.
16024 o Minor features, descriptors and descriptor handling:
16025 - Avoid duplicate entries on MyFamily line in server descriptor.
16026 - When Tor receives a router descriptor that it asked for, but
16027 no longer wants (because it has received fresh networkstatuses
16028 in the meantime), do not warn the user. Cache the descriptor if
16029 we're a cache; drop it if we aren't.
16030 - Servers no longer ever list themselves in their "family" line,
16031 even if configured to do so. This makes it easier to configure
16032 family lists conveniently.
16034 o Minor fixes, confusing/misleading log messages:
16035 - Display correct results when reporting which versions are
16036 recommended, and how recommended they are. (Resolves bug 383.)
16037 - Inform the server operator when we decide not to advertise a
16038 DirPort due to AccountingMax enabled or a low BandwidthRate.
16039 - Only include function names in log messages for info/debug messages.
16040 For notice/warn/err, the content of the message should be clear on
16041 its own, and printing the function name only confuses users.
16042 - Remove even more protocol-related warnings from Tor server logs,
16043 such as bad TLS handshakes and malformed begin cells.
16044 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16045 when the IP address is mapped through MapAddress to a hostname.
16046 - Fix misleading log messages: an entry guard that is "unlisted",
16047 as well as not known to be "down" (because we've never heard
16048 of it), is not therefore "up".
16050 o Minor fixes, old/obsolete behavior:
16051 - Start assuming we can use a create_fast cell if we don't know
16052 what version a router is running.
16053 - We no longer look for identity and onion keys in "identity.key" and
16054 "onion.key" -- these were replaced by secret_id_key and
16055 secret_onion_key in 0.0.8pre1.
16056 - We no longer require unrecognized directory entries to be
16058 - Drop compatibility with obsolete Tors that permit create cells
16059 to have the wrong circ_id_type.
16060 - Remove code to special-case "-cvs" ending, since it has not
16061 actually mattered since 0.0.9.
16062 - Don't re-write the fingerprint file every restart, unless it has
16065 o Minor fixes, misc client-side behavior:
16066 - Always remove expired routers and networkstatus docs before checking
16067 whether we have enough information to build circuits. (Fixes
16069 - When computing clock skew from directory HTTP headers, consider what
16070 time it was when we finished asking for the directory, not what
16072 - Make our socks5 handling more robust to broken socks clients:
16073 throw out everything waiting on the buffer in between socks
16074 handshake phases, since they can't possibly (so the theory
16075 goes) have predicted what we plan to respond to them.
16076 - Expire socks connections if they spend too long waiting for the
16077 handshake to finish. Previously we would let them sit around for
16078 days, if the connecting application didn't close them either.
16079 - And if the socks handshake hasn't started, don't send a
16080 "DNS resolve socks failed" handshake reply; just close it.
16081 - If the user asks to use invalid exit nodes, be willing to use
16083 - Track unreachable entry guards correctly: don't conflate
16084 'unreachable by us right now' with 'listed as down by the directory
16085 authorities'. With the old code, if a guard was unreachable by us
16086 but listed as running, it would clog our guard list forever.
16087 - Behave correctly in case we ever have a network with more than
16088 2GB/s total advertised capacity.
16089 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16090 - Fix a memory leak when we ask for "all" networkstatuses and we
16091 get one we don't recognize.
16094 Changes in version 0.1.1.26 - 2006-12-14
16095 o Security bugfixes:
16096 - Stop sending the HttpProxyAuthenticator string to directory
16097 servers when directory connections are tunnelled through Tor.
16098 - Clients no longer store bandwidth history in the state file.
16099 - Do not log introduction points for hidden services if SafeLogging
16103 - Fix an assert failure when a directory authority sets
16104 AuthDirRejectUnlisted and then receives a descriptor from an
16105 unlisted router (reported by seeess).
16108 Changes in version 0.1.1.25 - 2006-11-04
16110 - When a client asks us to resolve (rather than connect to)
16111 an address, and we have a cached answer, give them the cached
16112 answer. Previously, we would give them no answer at all.
16113 - We were building exactly the wrong circuits when we predict
16114 hidden service requirements, meaning Tor would have to build all
16115 its circuits on demand.
16116 - If none of our live entry guards have a high uptime, but we
16117 require a guard with a high uptime, try adding a new guard before
16118 we give up on the requirement. This patch should make long-lived
16119 connections more stable on average.
16120 - When testing reachability of our DirPort, don't launch new
16121 tests when there's already one in progress -- unreachable
16122 servers were stacking up dozens of testing streams.
16124 o Security bugfixes:
16125 - When the user sends a NEWNYM signal, clear the client-side DNS
16126 cache too. Otherwise we continue to act on previous information.
16129 - Avoid a memory corruption bug when creating a hash table for
16131 - Avoid possibility of controller-triggered crash when misusing
16132 certain commands from a v0 controller on platforms that do not
16133 handle printf("%s",NULL) gracefully.
16134 - Avoid infinite loop on unexpected controller input.
16135 - Don't log spurious warnings when we see a circuit close reason we
16136 don't recognize; it's probably just from a newer version of Tor.
16137 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16138 Tor/Privoxy we also uninstall Vidalia.
16141 Changes in version 0.1.1.24 - 2006-09-29
16143 - Allow really slow clients to not hang up five minutes into their
16144 directory downloads (suggested by Adam J. Richter).
16145 - Fix major performance regression from 0.1.0.x: instead of checking
16146 whether we have enough directory information every time we want to
16147 do something, only check when the directory information has changed.
16148 This should improve client CPU usage by 25-50%.
16149 - Don't crash if, after a server has been running for a while,
16150 it can't resolve its hostname.
16151 - When a client asks us to resolve (not connect to) an address,
16152 and we have a cached answer, give them the cached answer.
16153 Previously, we would give them no answer at all.
16156 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16157 - Don't crash when the controller receives a third argument to an
16158 "extendcircuit" request.
16159 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16160 response; fix error code when "getinfo dir/status/" fails.
16161 - Fix configure.in to not produce broken configure files with
16162 more recent versions of autoconf. Thanks to Clint for his auto*
16164 - Fix security bug on NetBSD that could allow someone to force
16165 uninitialized RAM to be sent to a server's DNS resolver. This
16166 only affects NetBSD and other platforms that do not bounds-check
16168 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16169 methods: these are known to be buggy.
16170 - If we're a directory mirror and we ask for "all" network status
16171 documents, we would discard status documents from authorities
16172 we don't recognize.
16175 Changes in version 0.1.1.23 - 2006-07-30
16177 - Fast Tor servers, especially exit nodes, were triggering asserts
16178 due to a bug in handling the list of pending DNS resolves. Some
16179 bugs still remain here; we're hunting them.
16180 - Entry guards could crash clients by sending unexpected input.
16181 - More fixes on reachability testing: if you find yourself reachable,
16182 then don't ever make any client requests (so you stop predicting
16183 circuits), then hup or have your clock jump, then later your IP
16184 changes, you won't think circuits are working, so you won't try to
16185 test reachability, so you won't publish.
16188 - Avoid a crash if the controller does a resetconf firewallports
16189 and then a setconf fascistfirewall=1.
16190 - Avoid an integer underflow when the dir authority decides whether
16191 a router is stable: we might wrongly label it stable, and compute
16192 a slightly wrong median stability, when a descriptor is published
16194 - Fix a place where we might trigger an assert if we can't build our
16195 own server descriptor yet.
16198 Changes in version 0.1.1.22 - 2006-07-05
16200 - Fix a big bug that was causing servers to not find themselves
16201 reachable if they changed IP addresses. Since only 0.1.1.22+
16202 servers can do reachability testing correctly, now we automatically
16203 make sure to test via one of these.
16204 - Fix to allow clients and mirrors to learn directory info from
16205 descriptor downloads that get cut off partway through.
16206 - Directory authorities had a bug in deciding if a newly published
16207 descriptor was novel enough to make everybody want a copy -- a few
16208 servers seem to be publishing new descriptors many times a minute.
16210 - Fix a rare bug that was causing some servers to complain about
16211 "closing wedged cpuworkers" and skip some circuit create requests.
16212 - Make the Exit flag in directory status documents actually work.
16215 Changes in version 0.1.1.21 - 2006-06-10
16216 o Crash and assert fixes from 0.1.1.20:
16217 - Fix a rare crash on Tor servers that have enabled hibernation.
16218 - Fix a seg fault on startup for Tor networks that use only one
16219 directory authority.
16220 - Fix an assert from a race condition that occurs on Tor servers
16221 while exiting, where various threads are trying to log that they're
16222 exiting, and delete the logs, at the same time.
16223 - Make our unit tests pass again on certain obscure platforms.
16226 - Add support for building SUSE RPM packages.
16227 - Speed up initial bootstrapping for clients: if we are making our
16228 first ever connection to any entry guard, then don't mark it down
16230 - When only one Tor server in the network is labelled as a guard,
16231 and we've already picked him, we would cycle endlessly picking him
16232 again, being unhappy about it, etc. Now we specifically exclude
16233 current guards when picking a new guard.
16234 - Servers send create cells more reliably after the TLS connection
16235 is established: we were sometimes forgetting to send half of them
16236 when we had more than one pending.
16237 - If we get a create cell that asks us to extend somewhere, but the
16238 Tor server there doesn't match the expected digest, we now send
16239 a destroy cell back, rather than silently doing nothing.
16240 - Make options->RedirectExit work again.
16241 - Make cookie authentication for the controller work again.
16242 - Stop being picky about unusual characters in the arguments to
16243 mapaddress. It's none of our business.
16244 - Add a new config option "TestVia" that lets you specify preferred
16245 middle hops to use for test circuits. Perhaps this will let me
16246 debug the reachability problems better.
16248 o Log / documentation fixes:
16249 - If we're a server and some peer has a broken TLS certificate, don't
16250 log about it unless ProtocolWarnings is set, i.e., we want to hear
16251 about protocol violations by others.
16252 - Fix spelling of VirtualAddrNetwork in man page.
16253 - Add a better explanation at the top of the autogenerated torrc file
16254 about what happened to our old torrc.
16257 Changes in version 0.1.1.20 - 2006-05-23
16258 o Crash and assert fixes from 0.1.0.17:
16259 - Fix assert bug in close_logs() on exit: when we close and delete
16260 logs, remove them all from the global "logfiles" list.
16261 - Fix an assert error when we're out of space in the connection_list
16262 and we try to post a hidden service descriptor (reported by Peter
16264 - Fix a rare assert error when we've tried all intro points for
16265 a hidden service and we try fetching the service descriptor again:
16266 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
16267 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
16268 out and refuse the setconf if it would fail.
16269 - If you specify a relative torrc path and you set RunAsDaemon in
16270 your torrc, then it chdir()'s to the new directory. If you then
16271 HUP, it tries to load the new torrc location, fails, and exits.
16272 The fix: no longer allow a relative path to torrc when using -f.
16273 - Check for integer overflows in more places, when adding elements
16274 to smartlists. This could possibly prevent a buffer overflow
16275 on malicious huge inputs.
16277 o Security fixes, major:
16278 - When we're printing strings from the network, don't try to print
16279 non-printable characters. Now we're safer against shell escape
16280 sequence exploits, and also against attacks to fool users into
16281 misreading their logs.
16282 - Implement entry guards: automatically choose a handful of entry
16283 nodes and stick with them for all circuits. Only pick new guards
16284 when the ones you have are unsuitable, and if the old guards
16285 become suitable again, switch back. This will increase security
16286 dramatically against certain end-point attacks. The EntryNodes
16287 config option now provides some hints about which entry guards you
16288 want to use most; and StrictEntryNodes means to only use those.
16289 Fixes CVE-2006-0414.
16290 - Implement exit enclaves: if we know an IP address for the
16291 destination, and there's a running Tor server at that address
16292 which allows exit to the destination, then extend the circuit to
16293 that exit first. This provides end-to-end encryption and end-to-end
16294 authentication. Also, if the user wants a .exit address or enclave,
16295 use 4 hops rather than 3, and cannibalize a general circ for it
16297 - Obey our firewall options more faithfully:
16298 . If we can't get to a dirserver directly, try going via Tor.
16299 . Don't ever try to connect (as a client) to a place our
16300 firewall options forbid.
16301 . If we specify a proxy and also firewall options, obey the
16302 firewall options even when we're using the proxy: some proxies
16303 can only proxy to certain destinations.
16304 - Make clients regenerate their keys when their IP address changes.
16305 - For the OS X package's modified privoxy config file, comment
16306 out the "logfile" line so we don't log everything passed
16308 - Our TLS handshakes were generating a single public/private
16309 keypair for the TLS context, rather than making a new one for
16310 each new connection. Oops. (But we were still rotating them
16311 periodically, so it's not so bad.)
16312 - When we were cannibalizing a circuit with a particular exit
16313 node in mind, we weren't checking to see if that exit node was
16314 already present earlier in the circuit. Now we are.
16315 - Require server descriptors to list IPv4 addresses -- hostnames
16316 are no longer allowed. This also fixes potential vulnerabilities
16317 to servers providing hostnames as their address and then
16318 preferentially resolving them so they can partition users.
16319 - Our logic to decide if the OR we connected to was the right guy
16320 was brittle and maybe open to a mitm for invalid routers.
16322 o Security fixes, minor:
16323 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
16324 Ian Goldberg can prove things about our handshake protocol more
16326 - Make directory authorities generate a separate "guard" flag to
16327 mean "would make a good entry guard". Clients now honor the
16328 is_guard flag rather than looking at is_fast or is_stable.
16329 - Try to list MyFamily elements by key, not by nickname, and warn
16330 if we've not heard of a server.
16331 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16332 OpenSSL. Also, reseed our entropy every hour, not just at
16333 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
16334 - Refuse server descriptors where the fingerprint line doesn't match
16335 the included identity key. Tor doesn't care, but other apps (and
16336 humans) might actually be trusting the fingerprint line.
16337 - We used to kill the circuit when we receive a relay command we
16338 don't recognize. Now we just drop that cell.
16339 - Fix a bug found by Lasse Overlier: when we were making internal
16340 circuits (intended to be cannibalized later for rendezvous and
16341 introduction circuits), we were picking them so that they had
16342 useful exit nodes. There was no need for this, and it actually
16343 aids some statistical attacks.
16344 - Start treating internal circuits and exit circuits separately.
16345 It's important to keep them separate because internal circuits
16346 have their last hops picked like middle hops, rather than like
16347 exit hops. So exiting on them will break the user's expectations.
16348 - Fix a possible way to DoS dirservers.
16349 - When the client asked for a rendezvous port that the hidden
16350 service didn't want to provide, we were sending an IP address
16351 back along with the end cell. Fortunately, it was zero. But stop
16354 o Packaging improvements:
16355 - Implement --with-libevent-dir option to ./configure. Improve
16356 search techniques to find libevent, and use those for openssl too.
16357 - Fix a couple of bugs in OpenSSL detection. Deal better when
16358 there are multiple SSLs installed with different versions.
16359 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16360 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
16362 - Make unit tests (and other invocations that aren't the real Tor)
16363 run without launching listeners, creating subdirectories, and so on.
16364 - The OS X installer was adding a symlink for tor_resolve but
16365 the binary was called tor-resolve (reported by Thomas Hardly).
16366 - Now we can target arch and OS in rpm builds (contributed by
16367 Phobos). Also make the resulting dist-rpm filename match the
16369 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16370 if you log to syslog and want something other than LOG_DAEMON.
16371 - Fix the torify (tsocks) config file to not use Tor for localhost
16373 - Start shipping socks-extensions.txt, tor-doc-unix.html,
16374 tor-doc-server.html, and stylesheet.css in the tarball.
16375 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
16376 They are useless now.
16377 - Add Peter Palfrader's contributed check-tor script. It lets you
16378 easily check whether a given server (referenced by nickname)
16379 is reachable by you.
16380 - Add BSD-style contributed startup script "rc.subr" from Peter
16383 o Directory improvements -- new directory protocol:
16384 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
16385 - Authorities and caches publish individual descriptors (by
16386 digest, by fingerprint, by "all", and by "tell me yours").
16387 - Clients don't download or use the old directory anymore. Now they
16388 download network-statuses from the directory authorities, and
16389 fetch individual server descriptors as needed from mirrors.
16390 - Clients don't download descriptors of non-running servers.
16391 - Download descriptors by digest, not by fingerprint. Caches try to
16392 download all listed digests from authorities; clients try to
16393 download "best" digests from caches. This avoids partitioning
16394 and isolating attacks better.
16395 - Only upload a new server descriptor when options change, 18
16396 hours have passed, uptime is reset, or bandwidth changes a lot.
16397 - Directory authorities silently throw away new descriptors that
16398 haven't changed much if the timestamps are similar. We do this to
16399 tolerate older Tor servers that upload a new descriptor every 15
16400 minutes. (It seemed like a good idea at the time.)
16401 - Clients choose directory servers from the network status lists,
16402 not from their internal list of router descriptors. Now they can
16403 go to caches directly rather than needing to go to authorities
16404 to bootstrap the first set of descriptors.
16405 - When picking a random directory, prefer non-authorities if any
16407 - Add a new flag to network-status indicating whether the server
16408 can answer v2 directory requests too.
16409 - Directory mirrors now cache up to 16 unrecognized network-status
16410 docs, so new directory authorities will be cached too.
16411 - Stop parsing, storing, or using running-routers output (but
16412 mirrors still cache and serve it).
16413 - Clients consider a threshold of "versioning" directory authorities
16414 before deciding whether to warn the user that he's obsolete.
16415 - Authorities publish separate sorted lists of recommended versions
16416 for clients and for servers.
16417 - Change DirServers config line to note which dirs are v1 authorities.
16418 - Put nicknames on the DirServer line, so we can refer to them
16419 without requiring all our users to memorize their IP addresses.
16420 - Remove option when getting directory cache to see whether they
16421 support running-routers; they all do now. Replace it with one
16422 to see whether caches support v2 stuff.
16423 - Stop listing down or invalid nodes in the v1 directory. This
16424 reduces its bulk by about 1/3, and reduces load on mirrors.
16425 - Mirrors no longer cache the v1 directory as often.
16426 - If we as a directory mirror don't know of any v1 directory
16427 authorities, then don't try to cache any v1 directories.
16429 o Other directory improvements:
16430 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
16431 fifth authoritative directory servers.
16432 - Directory authorities no longer require an open connection from
16433 a server to consider him "reachable". We need this change because
16434 when we add new directory authorities, old servers won't know not
16435 to hang up on them.
16436 - Dir authorities now do their own external reachability testing
16437 of each server, and only list as running the ones they found to
16438 be reachable. We also send back warnings to the server's logs if
16439 it uploads a descriptor that we already believe is unreachable.
16440 - Spread the directory authorities' reachability testing over the
16441 entire testing interval, so we don't try to do 500 TLS's at once
16443 - Make the "stable" router flag in network-status be the median of
16444 the uptimes of running valid servers, and make clients pay
16445 attention to the network-status flags. Thus the cutoff adapts
16446 to the stability of the network as a whole, making IRC, IM, etc
16447 connections more reliable.
16448 - Make the v2 dir's "Fast" flag based on relative capacity, just
16449 like "Stable" is based on median uptime. Name everything in the
16450 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
16451 - Retry directory requests if we fail to get an answer we like
16452 from a given dirserver (we were retrying before, but only if
16453 we fail to connect).
16454 - Return a robots.txt on our dirport to discourage google indexing.
16456 o Controller protocol improvements:
16457 - Revised controller protocol (version 1) that uses ascii rather
16458 than binary: tor/doc/control-spec.txt. Add supporting libraries
16459 in python and java and c# so you can use the controller from your
16460 applications without caring how our protocol works.
16461 - Allow the DEBUG controller event to work again. Mark certain log
16462 entries as "don't tell this to controllers", so we avoid cycles.
16463 - New controller function "getinfo accounting", to ask how
16464 many bytes we've used in this time period.
16465 - Add a "resetconf" command so you can set config options like
16466 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16467 a config option in the torrc with no value, then it clears it
16468 entirely (rather than setting it to its default).
16469 - Add a "getinfo config-file" to tell us where torrc is. Also
16470 expose guard nodes, config options/names.
16471 - Add a "quit" command (when when using the controller manually).
16472 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
16473 stop using any currently-dirty circuits for new streams, so we
16474 don't link new actions to old actions. This also occurs on HUP
16475 or "signal reload".
16476 - If we would close a stream early (e.g. it asks for a .exit that
16477 we know would refuse it) but the LeaveStreamsUnattached config
16478 option is set by the controller, then don't close it.
16479 - Add a new controller event type "authdir_newdescs" that allows
16480 controllers to get all server descriptors that were uploaded to
16481 a router in its role as directory authority.
16482 - New controller option "getinfo desc/all-recent" to fetch the
16483 latest server descriptor for every router that Tor knows about.
16484 - Fix the controller's "attachstream 0" command to treat conn like
16485 it just connected, doing address remapping, handling .exit and
16486 .onion idioms, and so on. Now we're more uniform in making sure
16487 that the controller hears about new and closing connections.
16488 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
16489 the controller. Also, rotate dns and cpu workers if the controller
16490 changes options that will affect them; and initialize the dns
16491 worker cache tree whether or not we start out as a server.
16492 - Add a new circuit purpose 'controller' to let the controller ask
16493 for a circuit that Tor won't try to use. Extend the "extendcircuit"
16494 controller command to let you specify the purpose if you're starting
16495 a new circuit. Add a new "setcircuitpurpose" controller command to
16496 let you change a circuit's purpose after it's been created.
16497 - Let the controller ask for "getinfo dir/server/foo" so it can ask
16498 directly rather than connecting to the dir port. "getinfo
16499 dir/status/foo" also works, but currently only if your DirPort
16501 - Let the controller tell us about certain router descriptors
16502 that it doesn't want Tor to use in circuits. Implement
16503 "setrouterpurpose" and modify "+postdescriptor" to do this.
16504 - If the controller's *setconf commands fail, collect an error
16505 message in a string and hand it back to the controller -- don't
16506 just tell them to go read their logs.
16508 o Scalability, resource management, and performance:
16509 - Fix a major load balance bug: we were round-robin reading in 16 KB
16510 chunks, and servers with bandwidthrate of 20 KB, while downloading
16511 a 600 KB directory, would starve their other connections. Now we
16512 try to be a bit more fair.
16513 - Be more conservative about whether to advertise our DirPort.
16514 The main change is to not advertise if we're running at capacity
16515 and either a) we could hibernate ever or b) our capacity is low
16516 and we're using a default DirPort.
16517 - We weren't cannibalizing circuits correctly for
16518 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16519 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16520 build those from scratch. This should make hidden services faster.
16521 - Predict required circuits better, with an eye toward making hidden
16522 services faster on the service end.
16523 - Compress exit policies even more: look for duplicate lines and
16525 - Generate 18.0.0.0/8 address policy format in descs when we can;
16526 warn when the mask is not reducible to a bit-prefix.
16527 - There used to be two ways to specify your listening ports in a
16528 server descriptor: on the "router" line and with a separate "ports"
16529 line. Remove support for the "ports" line.
16530 - Reduce memory requirements in our structs by changing the order
16531 of fields. Replace balanced trees with hash tables. Inline
16532 bottleneck smartlist functions. Add a "Map from digest to void*"
16533 abstraction so we can do less hex encoding/decoding, and use it
16534 in router_get_by_digest(). Many other CPU and memory improvements.
16535 - Allow tor_gzip_uncompress to extract as much as possible from
16536 truncated compressed data. Try to extract as many
16537 descriptors as possible from truncated http responses (when
16538 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
16539 - Make circ->onionskin a pointer, not a static array. moria2 was using
16540 125000 circuit_t's after it had been up for a few weeks, which
16541 translates to 20+ megs of wasted space.
16542 - The private half of our EDH handshake keys are now chosen out
16543 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
16544 - Stop doing the complex voodoo overkill checking for insecure
16545 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16546 - Do round-robin writes for TLS of at most 16 kB per write. This
16547 might be more fair on loaded Tor servers.
16548 - Do not use unaligned memory access on alpha, mips, or mipsel.
16549 It *works*, but is very slow, so we treat them as if it doesn't.
16551 o Other bugfixes and improvements:
16552 - Start storing useful information to $DATADIR/state, so we can
16553 remember things across invocations of Tor. Retain unrecognized
16554 lines so we can be forward-compatible, and write a TorVersion line
16555 so we can be backward-compatible.
16556 - If ORPort is set, Address is not explicitly set, and our hostname
16557 resolves to a private IP address, try to use an interface address
16558 if it has a public address. Now Windows machines that think of
16559 themselves as localhost can guess their address.
16560 - Regenerate our local descriptor if it's dirty and we try to use
16561 it locally (e.g. if it changes during reachability detection).
16562 This was causing some Tor servers to keep publishing the same
16563 initial descriptor forever.
16564 - Tor servers with dynamic IP addresses were needing to wait 18
16565 hours before they could start doing reachability testing using
16566 the new IP address and ports. This is because they were using
16567 the internal descriptor to learn what to test, yet they were only
16568 rebuilding the descriptor once they decided they were reachable.
16569 - It turns out we couldn't bootstrap a network since we added
16570 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16571 has never gone down. Add an AssumeReachable config option to let
16572 servers and authorities bootstrap. When we're trying to build a
16573 high-uptime or high-bandwidth circuit but there aren't enough
16574 suitable servers, try being less picky rather than simply failing.
16575 - Newly bootstrapped Tor networks couldn't establish hidden service
16576 circuits until they had nodes with high uptime. Be more tolerant.
16577 - Really busy servers were keeping enough circuits open on stable
16578 connections that they were wrapping around the circuit_id
16579 space. (It's only two bytes.) This exposed a bug where we would
16580 feel free to reuse a circuit_id even if it still exists but has
16581 been marked for close. Try to fix this bug. Some bug remains.
16582 - When we fail to bind or listen on an incoming or outgoing
16583 socket, we now close it before refusing, rather than just
16584 leaking it. (Thanks to Peter Palfrader for finding.)
16585 - Fix a file descriptor leak in start_daemon().
16586 - On Windows, you can't always reopen a port right after you've
16587 closed it. So change retry_listeners() to only close and re-open
16588 ports that have changed.
16589 - Workaround a problem with some http proxies that refuse GET
16590 requests that specify "Content-Length: 0". Reported by Adrian.
16591 - Recover better from TCP connections to Tor servers that are
16592 broken but don't tell you (it happens!); and rotate TLS
16593 connections once a week.
16594 - Fix a scary-looking but apparently harmless bug where circuits
16595 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16596 servers, and never switch to state CIRCUIT_STATE_OPEN.
16597 - Check for even more Windows version flags when writing the platform
16598 string in server descriptors, and note any we don't recognize.
16599 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16600 get a better idea of why their circuits failed. Not used yet.
16601 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16602 We don't use them yet, but maybe one day our DNS resolver will be
16603 able to discover them.
16604 - Let people type "tor --install" as well as "tor -install" when they
16605 want to make it an NT service.
16606 - Looks like we were never delivering deflated (i.e. compressed)
16607 running-routers lists, even when asked. Oops.
16608 - We were leaking some memory every time the client changed IPs.
16609 - Clean up more of the OpenSSL memory when exiting, so we can detect
16610 memory leaks better.
16611 - Never call free() on tor_malloc()d memory. This will help us
16612 use dmalloc to detect memory leaks.
16613 - Some Tor servers process billions of cells per day. These
16614 statistics are now uint64_t's.
16615 - Check [X-]Forwarded-For headers in HTTP requests when generating
16616 log messages. This lets people run dirservers (and caches) behind
16617 Apache but still know which IP addresses are causing warnings.
16618 - Fix minor integer overflow in calculating when we expect to use up
16619 our bandwidth allocation before hibernating.
16620 - Lower the minimum required number of file descriptors to 1000,
16621 so we can have some overhead for Valgrind on Linux, where the
16622 default ulimit -n is 1024.
16623 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16624 and its existence is confusing some users.
16626 o Config option fixes:
16627 - Add a new config option ExitPolicyRejectPrivate which defaults
16628 to on. Now all exit policies will begin with rejecting private
16629 addresses, unless the server operator explicitly turns it off.
16630 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
16631 - Add new ReachableORAddresses and ReachableDirAddresses options
16632 that understand address policies. FascistFirewall is now a synonym
16633 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
16634 - Start calling it FooListenAddress rather than FooBindAddress,
16635 since few of our users know what it means to bind an address
16637 - If the user gave Tor an odd number of command-line arguments,
16638 we were silently ignoring the last one. Now we complain and fail.
16639 This wins the oldest-bug prize -- this bug has been present since
16640 November 2002, as released in Tor 0.0.0.
16641 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16642 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16643 it would silently ignore the 6668.
16644 - If we get a linelist or linelist_s config option from the torrc,
16645 e.g. ExitPolicy, and it has no value, warn and skip rather than
16646 silently resetting it to its default.
16647 - Setconf was appending items to linelists, not clearing them.
16648 - Add MyFamily to torrc.sample in the server section, so operators
16649 will be more likely to learn that it exists.
16650 - Make ContactInfo mandatory for authoritative directory servers.
16651 - MaxConn has been obsolete for a while now. Document the ConnLimit
16652 config option, which is a *minimum* number of file descriptors
16653 that must be available else Tor refuses to start.
16654 - Get rid of IgnoreVersion undocumented config option, and make us
16655 only warn, never exit, when we're running an obsolete version.
16656 - Make MonthlyAccountingStart config option truly obsolete now.
16657 - Correct the man page entry on TrackHostExitsExpire.
16658 - Let directory authorities start even if they don't specify an
16659 Address config option.
16660 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16661 reflect the updated flags in our v2 dir protocol.
16663 o Config option features:
16664 - Add a new config option FastFirstHopPK (on by default) so clients
16665 do a trivial crypto handshake for their first hop, since TLS has
16666 already taken care of confidentiality and authentication.
16667 - Let the user set ControlListenAddress in the torrc. This can be
16668 dangerous, but there are some cases (like a secured LAN) where it
16670 - New config options to help controllers: FetchServerDescriptors
16671 and FetchHidServDescriptors for whether to fetch server
16672 info and hidserv info or let the controller do it, and
16673 PublishServerDescriptor and PublishHidServDescriptors.
16674 - Also let the controller set the __AllDirActionsPrivate config
16675 option if you want all directory fetches/publishes to happen via
16676 Tor (it assumes your controller bootstraps your circuits).
16677 - Add "HardwareAccel" config option: support for crypto hardware
16678 accelerators via OpenSSL. Off by default, until we find somebody
16679 smart who can test it for us. (It appears to produce seg faults
16680 in at least some cases.)
16681 - New config option "AuthDirRejectUnlisted" for directory authorities
16682 as a panic button: if we get flooded with unusable servers we can
16683 revert to only listing servers in the approved-routers file.
16684 - Directory authorities can now reject/invalidate by key and IP,
16685 with the config options "AuthDirInvalid" and "AuthDirReject", or
16686 by marking a fingerprint as "!reject" or "!invalid" (as its
16687 nickname) in the approved-routers file. This is useful since
16688 currently we automatically list servers as running and usable
16689 even if we know they're jerks.
16690 - Add a new config option TestSocks so people can see whether their
16691 applications are using socks4, socks4a, socks5-with-ip, or
16692 socks5-with-fqdn. This way they don't have to keep mucking
16693 with tcpdump and wondering if something got cached somewhere.
16694 - Add "private:*" as an alias in configuration for policies. Now
16695 you can simplify your exit policy rather than needing to list
16696 every single internal or nonroutable network space.
16697 - Accept "private:*" in routerdesc exit policies; not generated yet
16698 because older Tors do not understand it.
16699 - Add configuration option "V1AuthoritativeDirectory 1" which
16700 moria1, moria2, and tor26 have set.
16701 - Implement an option, VirtualAddrMask, to set which addresses
16702 get handed out in response to mapaddress requests. This works
16703 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16704 - Add a new config option FetchUselessDescriptors, off by default,
16705 for when you plan to run "exitlist" on your client and you want
16706 to know about even the non-running descriptors.
16707 - SocksTimeout: How long do we let a socks connection wait
16708 unattached before we fail it?
16709 - CircuitBuildTimeout: Cull non-open circuits that were born
16710 at least this many seconds ago.
16711 - CircuitIdleTimeout: Cull open clean circuits that were born
16712 at least this many seconds ago.
16713 - New config option SafeSocks to reject all application connections
16714 using unsafe socks protocols. Defaults to off.
16716 o Improved and clearer log messages:
16717 - Reduce clutter in server logs. We're going to try to make
16718 them actually usable now. New config option ProtocolWarnings that
16719 lets you hear about how _other Tors_ are breaking the protocol. Off
16721 - Divide log messages into logging domains. Once we put some sort
16722 of interface on this, it will let people looking at more verbose
16723 log levels specify the topics they want to hear more about.
16724 - Log server fingerprint on startup, so new server operators don't
16725 have to go hunting around their filesystem for it.
16726 - Provide dire warnings to any users who set DirServer manually;
16727 move it out of torrc.sample and into torrc.complete.
16728 - Make the log message less scary when all the dirservers are
16729 temporarily unreachable.
16730 - When tor_socketpair() fails in Windows, give a reasonable
16731 Windows-style errno back.
16732 - Improve tor_gettimeofday() granularity on windows.
16733 - We were printing the number of idle dns workers incorrectly when
16735 - Handle duplicate lines in approved-routers files without warning.
16736 - We were whining about using socks4 or socks5-with-local-lookup
16737 even when it's an IP address in the "virtual" range we designed
16738 exactly for this case.
16739 - Check for named servers when looking them up by nickname;
16740 warn when we're calling a non-named server by its nickname;
16741 don't warn twice about the same name.
16742 - Downgrade the dirserver log messages when whining about
16744 - Correct "your server is reachable" log entries to indicate that
16745 it was self-testing that told us so.
16746 - If we're trying to be a Tor server and running Windows 95/98/ME
16747 as a server, explain that we'll likely crash.
16748 - Provide a more useful warn message when our onion queue gets full:
16749 the CPU is too slow or the exit policy is too liberal.
16750 - Don't warn when we receive a 503 from a dirserver/cache -- this
16751 will pave the way for them being able to refuse if they're busy.
16752 - When we fail to bind a listener, try to provide a more useful
16753 log message: e.g., "Is Tor already running?"
16754 - Only start testing reachability once we've established a
16755 circuit. This will make startup on dir authorities less noisy.
16756 - Don't try to upload hidden service descriptors until we have
16757 established a circuit.
16758 - Tor didn't warn when it failed to open a log file.
16759 - Warn when listening on a public address for socks. We suspect a
16760 lot of people are setting themselves up as open socks proxies,
16761 and they have no idea that jerks on the Internet are using them,
16762 since they simply proxy the traffic into the Tor network.
16763 - Give a useful message when people run Tor as the wrong user,
16764 rather than telling them to start chowning random directories.
16765 - Fix a harmless bug that was causing Tor servers to log
16766 "Got an end because of misc error, but we're not an AP. Closing."
16767 - Fix wrong log message when you add a "HiddenServiceNodes" config
16768 line without any HiddenServiceDir line (reported by Chris Thomas).
16769 - Directory authorities now stop whining so loudly about bad
16770 descriptors that they fetch from other dirservers. So when there's
16771 a log complaint, it's for sure from a freshly uploaded descriptor.
16772 - When logging via syslog, include the pid whenever we provide
16773 a log entry. Suggested by Todd Fries.
16774 - When we're shutting down and we do something like try to post a
16775 server descriptor or rendezvous descriptor, don't complain that
16776 we seem to be unreachable. Of course we are, we're shutting down.
16777 - Change log line for unreachability to explicitly suggest /etc/hosts
16778 as the culprit. Also make it clearer what IP address and ports we're
16779 testing for reachability.
16780 - Put quotes around user-supplied strings when logging so users are
16781 more likely to realize if they add bad characters (like quotes)
16783 - NT service patch from Matt Edman to improve error messages on Win32.
16786 Changes in version 0.1.0.17 - 2006-02-17
16787 o Crash bugfixes on 0.1.0.x:
16788 - When servers with a non-zero DirPort came out of hibernation,
16789 sometimes they would trigger an assert.
16791 o Other important bugfixes:
16792 - On platforms that don't have getrlimit (like Windows), we were
16793 artificially constraining ourselves to a max of 1024
16794 connections. Now just assume that we can handle as many as 15000
16795 connections. Hopefully this won't cause other problems.
16797 o Backported features:
16798 - When we're a server, a client asks for an old-style directory,
16799 and our write bucket is empty, don't give it to him. This way
16800 small servers can continue to serve the directory *sometimes*,
16801 without getting overloaded.
16802 - Whenever you get a 503 in response to a directory fetch, try
16803 once more. This will become important once servers start sending
16804 503's whenever they feel busy.
16805 - Fetch a new directory every 120 minutes, not every 40 minutes.
16806 Now that we have hundreds of thousands of users running the old
16807 directory algorithm, it's starting to hurt a lot.
16808 - Bump up the period for forcing a hidden service descriptor upload
16809 from 20 minutes to 1 hour.
16812 Changes in version 0.1.0.16 - 2006-01-02
16813 o Crash bugfixes on 0.1.0.x:
16814 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16815 corrupting the heap, losing FDs, or crashing when we need to resize
16816 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16817 - It turns out sparc64 platforms crash on unaligned memory access
16818 too -- so detect and avoid this.
16819 - Handle truncated compressed data correctly (by detecting it and
16821 - Fix possible-but-unlikely free(NULL) in control.c.
16822 - When we were closing connections, there was a rare case that
16823 stomped on memory, triggering seg faults and asserts.
16824 - Avoid potential infinite recursion when building a descriptor. (We
16825 don't know that it ever happened, but better to fix it anyway.)
16826 - We were neglecting to unlink marked circuits from soon-to-close OR
16827 connections, which caused some rare scribbling on freed memory.
16828 - Fix a memory stomping race bug when closing the joining point of two
16829 rendezvous circuits.
16830 - Fix an assert in time parsing found by Steven Murdoch.
16832 o Other bugfixes on 0.1.0.x:
16833 - When we're doing reachability testing, provide more useful log
16834 messages so the operator knows what to expect.
16835 - Do not check whether DirPort is reachable when we are suppressing
16836 advertising it because of hibernation.
16837 - When building with -static or on Solaris, we sometimes needed -ldl.
16838 - One of the dirservers (tor26) changed its IP address.
16839 - When we're deciding whether a stream has enough circuits around
16840 that can handle it, count the freshly dirty ones and not the ones
16841 that are so dirty they won't be able to handle it.
16842 - When we're expiring old circuits, we had a logic error that caused
16843 us to close new rendezvous circuits rather than old ones.
16844 - Give a more helpful log message when you try to change ORPort via
16845 the controller: you should upgrade Tor if you want that to work.
16846 - We were failing to parse Tor versions that start with "Tor ".
16847 - Tolerate faulty streams better: when a stream fails for reason
16848 exitpolicy, stop assuming that the router is lying about his exit
16849 policy. When a stream fails for reason misc, allow it to retry just
16850 as if it was resolvefailed. When a stream has failed three times,
16851 reset its failure count so we can try again and get all three tries.
16854 Changes in version 0.1.0.15 - 2005-09-23
16855 o Bugfixes on 0.1.0.x:
16856 - Reject ports 465 and 587 (spam targets) in default exit policy.
16857 - Don't crash when we don't have any spare file descriptors and we
16858 try to spawn a dns or cpu worker.
16859 - Get rid of IgnoreVersion undocumented config option, and make us
16860 only warn, never exit, when we're running an obsolete version.
16861 - Don't try to print a null string when your server finds itself to
16862 be unreachable and the Address config option is empty.
16863 - Make the numbers in read-history and write-history into uint64s,
16864 so they don't overflow and publish negatives in the descriptor.
16865 - Fix a minor memory leak in smartlist_string_remove().
16866 - We were only allowing ourselves to upload a server descriptor at
16867 most every 20 minutes, even if it changed earlier than that.
16868 - Clean up log entries that pointed to old URLs.
16871 Changes in version 0.1.0.14 - 2005-08-08
16872 o Bugfixes on 0.1.0.x:
16873 - Fix the other half of the bug with crypto handshakes
16875 - Fix an assert trigger if you send a 'signal term' via the
16876 controller when it's listening for 'event info' messages.
16879 Changes in version 0.1.0.13 - 2005-08-04
16880 o Bugfixes on 0.1.0.x:
16881 - Fix a critical bug in the security of our crypto handshakes.
16882 - Fix a size_t underflow in smartlist_join_strings2() that made
16883 it do bad things when you hand it an empty smartlist.
16884 - Fix Windows installer to ship Tor license (thanks to Aphex for
16885 pointing out this oversight) and put a link to the doc directory
16887 - Explicitly set no-unaligned-access for sparc: it turns out the
16888 new gcc's let you compile broken code, but that doesn't make it
16892 Changes in version 0.1.0.12 - 2005-07-18
16893 o New directory servers:
16894 - tor26 has changed IP address.
16896 o Bugfixes on 0.1.0.x:
16897 - Fix a possible double-free in tor_gzip_uncompress().
16898 - When --disable-threads is set, do not search for or link against
16899 pthreads libraries.
16900 - Don't trigger an assert if an authoritative directory server
16901 claims its dirport is 0.
16902 - Fix bug with removing Tor as an NT service: some people were
16903 getting "The service did not return an error." Thanks to Matt
16907 Changes in version 0.1.0.11 - 2005-06-30
16908 o Bugfixes on 0.1.0.x:
16909 - Fix major security bug: servers were disregarding their
16910 exit policies if clients behaved unexpectedly.
16911 - Make OS X init script check for missing argument, so we don't
16912 confuse users who invoke it incorrectly.
16913 - Fix a seg fault in "tor --hash-password foo".
16914 - The MAPADDRESS control command was broken.
16917 Changes in version 0.1.0.10 - 2005-06-14
16919 - Make NT services work and start on startup on Win32 (based on
16920 patch by Matt Edman). See the FAQ entry for details.
16921 - Make 'platform' string in descriptor more accurate for Win32
16922 servers, so it's not just "unknown platform".
16923 - REUSEADDR on normal platforms means you can rebind to the port
16924 right after somebody else has let it go. But REUSEADDR on Win32
16925 means you can bind to the port _even when somebody else already
16926 has it bound_! So, don't do that on Win32.
16927 - Clean up the log messages when starting on Win32 with no config
16929 - Allow seeding the RNG on Win32 even when you're not running as
16930 Administrator. If seeding the RNG on Win32 fails, quit.
16932 o Assert / crash bugs:
16933 - Refuse relay cells that claim to have a length larger than the
16934 maximum allowed. This prevents a potential attack that could read
16935 arbitrary memory (e.g. keys) from an exit server's process
16937 - If unofficial Tor clients connect and send weird TLS certs, our
16938 Tor server triggers an assert. Stop asserting, and start handling
16939 TLS errors better in other situations too.
16940 - Fix a race condition that can trigger an assert when we have a
16941 pending create cell and an OR connection attempt fails.
16944 - Use pthreads for worker processes rather than forking. This was
16945 forced because when we forked, we ended up wasting a lot of
16946 duplicate ram over time.
16947 - Also switch to foo_r versions of some library calls to allow
16948 reentry and threadsafeness.
16949 - Implement --disable-threads configure option. Disable threads on
16950 netbsd and openbsd by default, because they have no reentrant
16951 resolver functions (!), and on solaris since it has other
16953 - Fix possible bug on threading platforms (e.g. win32) which was
16954 leaking a file descriptor whenever a cpuworker or dnsworker died.
16955 - Fix a minor memory leak when somebody establishes an introduction
16956 point at your Tor server.
16957 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
16959 - Add ./configure --with-dmalloc option, to track memory leaks.
16960 - And try to free all memory on closing, so we can detect what
16963 o Protocol correctness:
16964 - When we've connected to an OR and handshaked but didn't like
16965 the result, we were closing the conn without sending destroy
16966 cells back for pending circuits. Now send those destroys.
16967 - Start sending 'truncated' cells back rather than destroy cells
16968 if the circuit closes in front of you. This means we won't have
16969 to abandon partially built circuits.
16970 - Handle changed router status correctly when dirserver reloads
16971 fingerprint file. We used to be dropping all unverified descriptors
16972 right then. The bug was hidden because we would immediately
16973 fetch a directory from another dirserver, which would include the
16974 descriptors we just dropped.
16975 - Revise tor-spec to add more/better stream end reasons.
16976 - Revise all calls to connection_edge_end to avoid sending 'misc',
16977 and to take errno into account where possible.
16978 - Client now retries when streams end early for 'hibernating' or
16979 'resource limit' reasons, rather than failing them.
16980 - Try to be more zealous about calling connection_edge_end when
16981 things go bad with edge conns in connection.c.
16983 o Robustness improvements:
16984 - Better handling for heterogeneous / unreliable nodes:
16985 - Annotate circuits with whether they aim to contain high uptime
16986 nodes and/or high capacity nodes. When building circuits, choose
16988 - This means that every single node in an intro rend circuit,
16989 not just the last one, will have a minimum uptime.
16990 - New config option LongLivedPorts to indicate application streams
16991 that will want high uptime circuits.
16992 - Servers reset uptime when a dir fetch entirely fails. This
16993 hopefully reflects stability of the server's network connectivity.
16994 - If somebody starts his tor server in Jan 2004 and then fixes his
16995 clock, don't make his published uptime be a year.
16996 - Reset published uptime when we wake up from hibernation.
16997 - Introduce a notion of 'internal' circs, which are chosen without
16998 regard to the exit policy of the last hop. Intro and rendezvous
16999 circs must be internal circs, to avoid leaking information. Resolve
17000 and connect streams can use internal circs if they want.
17001 - New circuit pooling algorithm: keep track of what destination ports
17002 we've used recently (start out assuming we'll want to use 80), and
17003 make sure to have enough circs around to satisfy these ports. Also
17004 make sure to have 2 internal circs around if we've required internal
17005 circs lately (and with high uptime if we've seen that lately too).
17006 - Turn addr_policy_compare from a tristate to a quadstate; this should
17007 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17008 for google.com" problem.
17009 - When a client asks us for a dir mirror and we don't have one,
17010 launch an attempt to get a fresh one.
17011 - First cut at support for "create-fast" cells. Clients can use
17012 these when extending to their first hop, since the TLS already
17013 provides forward secrecy and authentication. Not enabled on
17016 o Reachability testing.
17017 - Your Tor server will automatically try to see if its ORPort and
17018 DirPort are reachable from the outside, and it won't upload its
17019 descriptor until it decides at least ORPort is reachable (when
17020 DirPort is not yet found reachable, publish it as zero).
17021 - When building testing circs for ORPort testing, use only
17022 high-bandwidth nodes, so fewer circuits fail.
17023 - Notice when our IP changes, and reset stats/uptime/reachability.
17024 - Authdirservers don't do ORPort reachability detection, since
17025 they're in clique mode, so it will be rare to find a server not
17026 already connected to them.
17027 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
17031 - Now we allow two unverified servers with the same nickname
17032 but different keys. But if a nickname is verified, only that
17033 nickname+key are allowed.
17034 - If you're an authdirserver connecting to an address:port,
17035 and it's not the OR you were expecting, forget about that
17036 descriptor. If he *was* the one you were expecting, then forget
17037 about all other descriptors for that address:port.
17038 - Allow servers to publish descriptors from 12 hours in the future.
17039 Corollary: only whine about clock skew from the dirserver if
17040 he's a trusted dirserver (since now even verified servers could
17041 have quite wrong clocks).
17042 - Require servers that use the default dirservers to have public IP
17043 addresses. We have too many servers that are configured with private
17044 IPs and their admins never notice the log entries complaining that
17045 their descriptors are being rejected.
17047 o Efficiency improvements:
17048 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
17049 and /dev/poll), and hopefully work better on Windows too.
17050 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
17051 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
17052 - Find libevent even if it's hiding in /usr/local/ and your
17053 CFLAGS and LDFLAGS don't tell you to look there.
17054 - Be able to link with libevent as a shared library (the default
17055 after 1.0d), even if it's hiding in /usr/local/lib and even
17056 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17057 assuming you're running gcc. Otherwise fail and give a useful
17059 - Switch to a new buffer management algorithm, which tries to avoid
17060 reallocing and copying quite as much. In first tests it looks like
17061 it uses *more* memory on average, but less cpu.
17062 - Switch our internal buffers implementation to use a ring buffer,
17063 to hopefully improve performance for fast servers a lot.
17064 - Reenable the part of the code that tries to flush as soon as an
17065 OR outbuf has a full TLS record available. Perhaps this will make
17066 OR outbufs not grow as huge except in rare cases, thus saving lots
17067 of CPU time plus memory.
17068 - Improve performance for dirservers: stop re-parsing the whole
17069 directory every time you regenerate it.
17070 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17071 it much faster to look up a circuit for each relay cell.
17072 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17073 since they're eating our cpu on exit nodes.
17074 - Stop wasting time doing a case insensitive comparison for every
17075 dns name every time we do any lookup. Canonicalize the names to
17076 lowercase when you first see them.
17079 - Handle unavailable hidden services better. Handle slow or busy
17080 hidden services better.
17081 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17082 circ as necessary, if there are any completed ones lying around
17083 when we try to launch one.
17084 - Make hidden services try to establish a rendezvous for 30 seconds
17085 after fetching the descriptor, rather than for n (where n=3)
17086 attempts to build a circuit.
17087 - Adjust maximum skew and age for rendezvous descriptors: let skew
17088 be 48 hours rather than 90 minutes.
17089 - Reject malformed .onion addresses rather then passing them on as
17090 normal web requests.
17093 - More Tor controller support. See
17094 http://tor.eff.org/doc/control-spec.txt for all the new features,
17095 including signals to emulate unix signals from any platform;
17096 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17097 closestream; closecircuit; etc.
17098 - Encode hashed controller passwords in hex instead of base64,
17099 to make it easier to write controllers.
17100 - Revise control spec and implementation to allow all log messages to
17101 be sent to controller with their severities intact (suggested by
17102 Matt Edman). Disable debug-level logs while delivering a debug-level
17103 log to the controller, to prevent loop. Update TorControl to handle
17104 new log event types.
17106 o New config options/defaults:
17107 - Begin scrubbing sensitive strings from logs by default. Turn off
17108 the config option SafeLogging if you need to do debugging.
17109 - New exit policy: accept most low-numbered ports, rather than
17110 rejecting most low-numbered ports.
17111 - Put a note in the torrc about abuse potential with the default
17113 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17115 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
17116 based on patch from Adam Langley (basic auth only).
17117 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17118 the fast servers that have been joining lately. (Clients are now
17119 willing to load balance over up to 2 MB of advertised bandwidth
17121 - New config option MaxAdvertisedBandwidth which lets you advertise
17122 a low bandwidthrate (to not attract as many circuits) while still
17123 allowing a higher bandwidthrate in reality.
17124 - Require BandwidthRate to be at least 20kB/s for servers.
17125 - Add a NoPublish config option, so you can be a server (e.g. for
17126 testing running Tor servers in other Tor networks) without
17127 publishing your descriptor to the primary dirservers.
17128 - Add a new AddressMap config directive to rewrite incoming socks
17129 addresses. This lets you, for example, declare an implicit
17130 required exit node for certain sites.
17131 - Add a new TrackHostExits config directive to trigger addressmaps
17132 for certain incoming socks addresses -- for sites that break when
17133 your exit keeps changing (based on patch from Mike Perry).
17134 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17135 which describes how often we retry making new circuits if current
17136 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17137 how long we're willing to make use of an already-dirty circuit.
17138 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
17139 a config option "ShutdownWaitLength" (when using kill -INT on
17141 - Fix an edge case in parsing config options: if they say "--"
17142 on the commandline, it's not a config option (thanks weasel).
17143 - New config option DirAllowPrivateAddresses for authdirservers.
17144 Now by default they refuse router descriptors that have non-IP or
17145 private-IP addresses.
17146 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17147 smart" default value: low for servers and high for clients.
17148 - Some people were putting "Address " in their torrc, and they had
17149 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17150 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17151 LOCALSTATEDIR/tor instead.
17152 - Implement --verify-config command-line option to check if your torrc
17153 is valid without actually launching Tor.
17155 o Logging improvements:
17156 - When dirservers refuse a server descriptor, we now log its
17157 contactinfo, platform, and the poster's IP address.
17158 - Only warn once per nickname from add_nickname_list_to_smartlist()
17159 per failure, so an entrynode or exitnode choice that's down won't
17161 - When we're connecting to an OR and he's got a different nickname/key
17162 than we were expecting, only complain loudly if we're an OP or a
17163 dirserver. Complaining loudly to the OR admins just confuses them.
17164 - Whine at you if you're a server and you don't set your contactinfo.
17165 - Warn when exit policy implicitly allows local addresses.
17166 - Give a better warning when some other server advertises an
17167 ORPort that is actually an apache running ssl.
17168 - If we get an incredibly skewed timestamp from a dirserver mirror
17169 that isn't a verified OR, don't warn -- it's probably him that's
17171 - When a dirserver causes you to give a warn, mention which dirserver
17173 - Initialize libevent later in the startup process, so the logs are
17174 already established by the time we start logging libevent warns.
17175 - Use correct errno on win32 if libevent fails.
17176 - Check and warn about known-bad/slow libevent versions.
17177 - Stop warning about sigpipes in the logs. We're going to
17178 pretend that getting these occasionally is normal and fine.
17180 o New contrib scripts:
17181 - New experimental script tor/contrib/exitlist: a simple python
17182 script to parse directories and find Tor nodes that exit to listed
17184 - New experimental script tor/contrib/ExerciseServer.py (needs more
17185 work) that uses the controller interface to build circuits and
17186 fetch pages over them. This will help us bootstrap servers that
17187 have lots of capacity but haven't noticed it yet.
17188 - New experimental script tor/contrib/PathDemo.py (needs more work)
17189 that uses the controller interface to let you choose whole paths
17191 "<hostname>.<path,separated by dots>.<length of path>.path"
17192 - New contributed script "privoxy-tor-toggle" to toggle whether
17193 Privoxy uses Tor. Seems to be configured for Debian by default.
17194 - Have torctl.in/tor.sh.in check for location of su binary (needed
17198 - chdir() to your datadirectory at the *end* of the daemonize process,
17199 not the beginning. This was a problem because the first time you
17200 run tor, if your datadir isn't there, and you have runasdaemon set
17201 to 1, it will try to chdir to it before it tries to create it. Oops.
17202 - Fix several double-mark-for-close bugs, e.g. where we were finding
17203 a conn for a cell even if that conn is already marked for close.
17204 - Stop most cases of hanging up on a socks connection without sending
17206 - Fix a bug in the RPM package: set home directory for _tor to
17207 something more reasonable when first installing.
17208 - Stop putting nodename in the Platform string in server descriptors.
17209 It doesn't actually help, and it is confusing/upsetting some people.
17210 - When using preferred entry or exit nodes, ignore whether the
17211 circuit wants uptime or capacity. They asked for the nodes, they
17213 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17214 artificially capped at 500kB.
17215 - Cache local dns resolves correctly even when they're .exit
17217 - If we're hibernating and we get a SIGINT, exit immediately.
17218 - tor-resolve requests were ignoring .exit if there was a working circuit
17219 they could use instead.
17220 - Pay more attention to the ClientOnly config option.
17221 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
17222 installer screens; and don't put stuff into StartupItems unless
17223 the user asks you to.
17226 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
17227 rather than just rejecting it.
17228 - If our clock jumps forward by 100 seconds or more, assume something
17229 has gone wrong with our network and abandon all not-yet-used circs.
17230 - When an application is using socks5, give him the whole variety of
17231 potential socks5 responses (connect refused, host unreachable, etc),
17232 rather than just "success" or "failure".
17233 - A more sane version numbering system. See
17234 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17235 - Change version parsing logic: a version is "obsolete" if it is not
17236 recommended and (1) there is a newer recommended version in the
17237 same series, or (2) there are no recommended versions in the same
17238 series, but there are some recommended versions in a newer series.
17239 A version is "new" if it is newer than any recommended version in
17241 - Report HTTP reasons to client when getting a response from directory
17242 servers -- so you can actually know what went wrong.
17243 - Reject odd-looking addresses at the client (e.g. addresses that
17244 contain a colon), rather than having the server drop them because
17246 - Stop publishing socksport in the directory, since it's not
17247 actually meant to be public. For compatibility, publish a 0 there
17249 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17250 cookies to disk and doesn't log each web request to disk. (Thanks
17251 to Brett Carrington for pointing this out.)
17252 - Add OSX uninstall instructions. An actual uninstall script will
17254 - Add "opt hibernating 1" to server descriptor to make it clearer
17255 whether the server is hibernating.
17258 Changes in version 0.0.9.10 - 2005-06-16
17259 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17260 - Refuse relay cells that claim to have a length larger than the
17261 maximum allowed. This prevents a potential attack that could read
17262 arbitrary memory (e.g. keys) from an exit server's process
17266 Changes in version 0.0.9.9 - 2005-04-23
17267 o Bugfixes on 0.0.9.x:
17268 - If unofficial Tor clients connect and send weird TLS certs, our
17269 Tor server triggers an assert. This release contains a minimal
17270 backport from the broader fix that we put into 0.1.0.4-rc.
17273 Changes in version 0.0.9.8 - 2005-04-07
17274 o Bugfixes on 0.0.9.x:
17275 - We have a bug that I haven't found yet. Sometimes, very rarely,
17276 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17277 thinks of itself as idle. This meant that no new circuits ever got
17278 established. Here's a workaround to kill any cpuworker that's been
17279 busy for more than 100 seconds.
17282 Changes in version 0.0.9.7 - 2005-04-01
17283 o Bugfixes on 0.0.9.x:
17284 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17285 - Compare identity to identity, not to nickname, when extending to
17286 a router not already in the directory. This was preventing us from
17287 extending to unknown routers. Oops.
17288 - Make sure to create OS X Tor user in <500 range, so we aren't
17289 creating actual system users.
17290 - Note where connection-that-hasn't-sent-end was marked, and fix
17291 a few really loud instances of this harmless bug (it's fixed more
17295 Changes in version 0.0.9.6 - 2005-03-24
17296 o Bugfixes on 0.0.9.x (crashes and asserts):
17297 - Add new end stream reasons to maintenance branch. Fix bug where
17298 reason (8) could trigger an assert. Prevent bug from recurring.
17299 - Apparently win32 stat wants paths to not end with a slash.
17300 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17301 blowing away the circuit that conn->cpath_layer points to, then
17302 checking to see if the circ is well-formed. Backport check to make
17303 sure we dont use the cpath on a closed connection.
17304 - Prevent circuit_resume_edge_reading_helper() from trying to package
17305 inbufs for marked-for-close streams.
17306 - Don't crash on hup if your options->address has become unresolvable.
17307 - Some systems (like OS X) sometimes accept() a connection and tell
17308 you the remote host is 0.0.0.0:0. If this happens, due to some
17309 other mis-features, we get confused; so refuse the conn for now.
17311 o Bugfixes on 0.0.9.x (other):
17312 - Fix harmless but scary "Unrecognized content encoding" warn message.
17313 - Add new stream error reason: TORPROTOCOL reason means "you are not
17314 speaking a version of Tor I understand; say bye-bye to your stream."
17315 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17316 into the future, now that we are more tolerant of skew. This
17317 resolves a bug where a Tor server would refuse to cache a directory
17318 because all the directories it gets are too far in the future;
17319 yet the Tor server never logs any complaints about clock skew.
17320 - Mac packaging magic: make man pages useable, and do not overwrite
17321 existing torrc files.
17322 - Make OS X log happily to /var/log/tor/tor.log
17325 Changes in version 0.0.9.5 - 2005-02-22
17326 o Bugfixes on 0.0.9.x:
17327 - Fix an assert race at exit nodes when resolve requests fail.
17328 - Stop picking unverified dir mirrors--it only leads to misery.
17329 - Patch from Matt Edman to make NT services work better. Service
17330 support is still not compiled into the executable by default.
17331 - Patch from Dmitri Bely so the Tor service runs better under
17332 the win32 SYSTEM account.
17333 - Make tor-resolve actually work (?) on Win32.
17334 - Fix a sign bug when getrlimit claims to have 4+ billion
17335 file descriptors available.
17336 - Stop refusing to start when bandwidthburst == bandwidthrate.
17337 - When create cells have been on the onion queue more than five
17338 seconds, just send back a destroy and take them off the list.
17341 Changes in version 0.0.9.4 - 2005-02-03
17342 o Bugfixes on 0.0.9:
17343 - Fix an assert bug that took down most of our servers: when
17344 a server claims to have 1 GB of bandwidthburst, don't
17346 - Don't crash as badly if we have spawned the max allowed number
17347 of dnsworkers, or we're out of file descriptors.
17348 - Block more file-sharing ports in the default exit policy.
17349 - MaxConn is now automatically set to the hard limit of max
17350 file descriptors we're allowed (ulimit -n), minus a few for
17352 - Give a clearer message when servers need to raise their
17353 ulimit -n when they start running out of file descriptors.
17354 - SGI Compatibility patches from Jan Schaumann.
17355 - Tolerate a corrupt cached directory better.
17356 - When a dirserver hasn't approved your server, list which one.
17357 - Go into soft hibernation after 95% of the bandwidth is used,
17358 not 99%. This is especially important for daily hibernators who
17359 have a small accounting max. Hopefully it will result in fewer
17360 cut connections when the hard hibernation starts.
17361 - Load-balance better when using servers that claim more than
17362 800kB/s of capacity.
17363 - Make NT services work (experimental, only used if compiled in).
17366 Changes in version 0.0.9.3 - 2005-01-21
17367 o Bugfixes on 0.0.9:
17368 - Backport the cpu use fixes from main branch, so busy servers won't
17369 need as much processor time.
17370 - Work better when we go offline and then come back, or when we
17371 run Tor at boot before the network is up. We do this by
17372 optimistically trying to fetch a new directory whenever an
17373 application request comes in and we think we're offline -- the
17374 human is hopefully a good measure of when the network is back.
17375 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17376 long as you keep using them; actually publish hidserv descriptors
17377 shortly after they change, rather than waiting 20-40 minutes.
17378 - Enable Mac startup script by default.
17379 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17380 - When you update AllowUnverifiedNodes or FirewallPorts via the
17381 controller's setconf feature, we were always appending, never
17383 - When you update HiddenServiceDir via setconf, it was screwing up
17384 the order of reading the lines, making it fail.
17385 - Do not rewrite a cached directory back to the cache; otherwise we
17386 will think it is recent and not fetch a newer one on startup.
17387 - Workaround for webservers that lie about Content-Encoding: Tor
17388 now tries to autodetect compressed directories and compression
17389 itself. This lets us Proxypass dir fetches through apache.
17392 Changes in version 0.0.9.2 - 2005-01-04
17393 o Bugfixes on 0.0.9 (crashes and asserts):
17394 - Fix an assert on startup when the disk is full and you're logging
17396 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17397 style address, then we'd crash.
17398 - Fix an assert trigger when the running-routers string we get from
17399 a dirserver is broken.
17400 - Make worker threads start and run on win32. Now win32 servers
17402 - Bandaid (not actually fix, but now it doesn't crash) an assert
17403 where the dns worker dies mysteriously and the main Tor process
17404 doesn't remember anything about the address it was resolving.
17406 o Bugfixes on 0.0.9 (Win32):
17407 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17408 name out of the warning/assert messages.
17409 - Fix a superficial "unhandled error on read" bug on win32.
17410 - The win32 installer no longer requires a click-through for our
17411 license, since our Free Software license grants rights but does not
17413 - Win32: When connecting to a dirserver fails, try another one
17414 immediately. (This was already working for non-win32 Tors.)
17415 - Stop trying to parse $HOME on win32 when hunting for default
17417 - Make tor-resolve.c work on win32 by calling network_init().
17419 o Bugfixes on 0.0.9 (other):
17420 - Make 0.0.9.x build on Solaris again.
17421 - Due to a fencepost error, we were blowing away the \n when reporting
17422 confvalue items in the controller. So asking for multiple config
17423 values at once couldn't work.
17424 - When listing circuits that are pending on an opening OR connection,
17425 if we're an OR we were listing circuits that *end* at us as
17426 being pending on every listener, dns/cpu worker, etc. Stop that.
17427 - Dirservers were failing to create 'running-routers' or 'directory'
17428 strings if we had more than some threshold of routers. Fix them so
17429 they can handle any number of routers.
17430 - Fix a superficial "Duplicate mark for close" bug.
17431 - Stop checking for clock skew for OR connections, even for servers.
17432 - Fix a fencepost error that was chopping off the last letter of any
17433 nickname that is the maximum allowed nickname length.
17434 - Update URLs in log messages so they point to the new website.
17435 - Fix a potential problem in mangling server private keys while
17436 writing to disk (not triggered yet, as far as we know).
17437 - Include the licenses for other free software we include in Tor,
17438 now that we're shipping binary distributions more regularly.
17441 Changes in version 0.0.9.1 - 2004-12-15
17442 o Bugfixes on 0.0.9:
17443 - Make hibernation actually work.
17444 - Make HashedControlPassword config option work.
17445 - When we're reporting event circuit status to a controller,
17446 don't use the stream status code.
17449 Changes in version 0.0.9 - 2004-12-12
17450 o Bugfixes on 0.0.8.1 (Crashes and asserts):
17451 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17452 write() call will fail and we handle it there.
17453 - When we run out of disk space, or other log writing error, don't
17454 crash. Just stop logging to that log and continue.
17455 - Fix isspace() and friends so they still make Solaris happy
17456 but also so they don't trigger asserts on win32.
17457 - Fix assert failure on malformed socks4a requests.
17458 - Fix an assert bug where a hidden service provider would fail if
17459 the first hop of his rendezvous circuit was down.
17460 - Better handling of size_t vs int, so we're more robust on 64
17463 o Bugfixes on 0.0.8.1 (Win32):
17464 - Make windows sockets actually non-blocking (oops), and handle
17465 win32 socket errors better.
17466 - Fix parse_iso_time on platforms without strptime (eg win32).
17467 - win32: when being multithreaded, leave parent fdarray open.
17468 - Better handling of winsock includes on non-MSV win32 compilers.
17469 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17471 - Make unit tests work on win32.
17473 o Bugfixes on 0.0.8.1 (Path selection and streams):
17474 - Calculate timeout for waiting for a connected cell from the time
17475 we sent the begin cell, not from the time the stream started. If
17476 it took a long time to establish the circuit, we would time out
17477 right after sending the begin cell.
17478 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17479 of * as always matching, so we were picking reject *:* nodes as
17480 exit nodes too. Oops.
17481 - When read() failed on a stream, we would close it without sending
17482 back an end. So 'connection refused' would simply be ignored and
17483 the user would get no response.
17484 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17485 we shouldn't hold-open-until-flush if the eof arrived first.
17486 - Let resolve conns retry/expire also, rather than sticking around
17488 - Fix more dns related bugs: send back resolve_failed and end cells
17489 more reliably when the resolve fails, rather than closing the
17490 circuit and then trying to send the cell. Also attach dummy resolve
17491 connections to a circuit *before* calling dns_resolve(), to fix
17492 a bug where cached answers would never be sent in RESOLVED cells.
17494 o Bugfixes on 0.0.8.1 (Circuits):
17495 - Finally fix a bug that's been plaguing us for a year:
17496 With high load, circuit package window was reaching 0. Whenever
17497 we got a circuit-level sendme, we were reading a lot on each
17498 socket, but only writing out a bit. So we would eventually reach
17499 eof. This would be noticed and acted on even when there were still
17500 bytes sitting in the inbuf.
17501 - Use identity comparison, not nickname comparison, to choose which
17502 half of circuit-ID-space each side gets to use. This is needed
17503 because sometimes we think of a router as a nickname, and sometimes
17504 as a hex ID, and we can't predict what the other side will do.
17506 o Bugfixes on 0.0.8.1 (Other):
17507 - Fix a whole slew of memory leaks.
17508 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17509 - If we are using select, make sure we stay within FD_SETSIZE.
17510 - When poll() is interrupted, we shouldn't believe the revents values.
17511 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17512 and smartlist_len, which are two major profiling offenders.
17513 - If do_hup fails, actually notice.
17514 - Flush the log file descriptor after we print "Tor opening log file",
17515 so we don't see those messages days later.
17516 - Hidden service operators now correctly handle version 1 style
17517 INTRODUCE1 cells (nobody generates them still, so not a critical
17519 - Handle more errnos from accept() without closing the listener.
17520 Some OpenBSD machines were closing their listeners because
17521 they ran out of file descriptors.
17522 - Some people had wrapped their tor client/server in a script
17523 that would restart it whenever it died. This did not play well
17524 with our "shut down if your version is obsolete" code. Now people
17525 don't fetch a new directory if their local cached version is
17527 - Make our autogen.sh work on ksh as well as bash.
17528 - Better torrc example lines for dirbindaddress and orbindaddress.
17529 - Improved bounds checking on parsed ints (e.g. config options and
17530 the ones we find in directories.)
17531 - Stop using separate defaults for no-config-file and
17532 empty-config-file. Now you have to explicitly turn off SocksPort,
17533 if you don't want it open.
17534 - We were starting to daemonize before we opened our logs, so if
17535 there were any problems opening logs, we would complain to stderr,
17536 which wouldn't work, and then mysteriously exit.
17537 - If a verified OR connects to us before he's uploaded his descriptor,
17538 or we verify him and hup but he still has the original TLS
17539 connection, then conn->nickname is still set like he's unverified.
17541 o Code security improvements, inspired by Ilja:
17542 - tor_snprintf wrapper over snprintf with consistent (though not C99)
17544 - Replace sprintf with tor_snprintf. (I think they were all safe, but
17546 - Replace strcpy/strncpy with strlcpy in more places.
17547 - Avoid strcat; use tor_snprintf or strlcat instead.
17549 o Features (circuits and streams):
17550 - New circuit building strategy: keep a list of ports that we've
17551 used in the past 6 hours, and always try to have 2 circuits open
17552 or on the way that will handle each such port. Seed us with port
17553 80 so web users won't complain that Tor is "slow to start up".
17554 - Make kill -USR1 dump more useful stats about circuits.
17555 - When warning about retrying or giving up, print the address, so
17556 the user knows which one it's talking about.
17557 - If you haven't used a clean circuit in an hour, throw it away,
17558 just to be on the safe side. (This means after 6 hours a totally
17559 unused Tor client will have no circuits open.)
17560 - Support "foo.nickname.exit" addresses, to let Alice request the
17561 address "foo" as viewed by exit node "nickname". Based on a patch
17562 from Geoff Goodell.
17563 - If your requested entry or exit node has advertised bandwidth 0,
17565 - Be more greedy about filling up relay cells -- we try reading again
17566 once we've processed the stuff we read, in case enough has arrived
17567 to fill the last cell completely.
17568 - Refuse application socks connections to port 0.
17569 - Use only 0.0.9pre1 and later servers for resolve cells.
17571 o Features (bandwidth):
17572 - Hibernation: New config option "AccountingMax" lets you
17573 set how many bytes per month (in each direction) you want to
17574 allow your server to consume. Rather than spreading those
17575 bytes out evenly over the month, we instead hibernate for some
17576 of the month and pop up at a deterministic time, work until
17577 the bytes are consumed, then hibernate again. Config option
17578 "MonthlyAccountingStart" lets you specify which day of the month
17579 your billing cycle starts on.
17580 - Implement weekly/monthly/daily accounting: now you specify your
17581 hibernation properties by
17582 AccountingMax N bytes|KB|MB|GB|TB
17583 AccountingStart day|week|month [day] HH:MM
17584 Defaults to "month 1 0:00".
17585 - Let bandwidth and interval config options be specified as 5 bytes,
17586 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17588 o Features (directories):
17589 - New "router-status" line in directory, to better bind each verified
17590 nickname to its identity key.
17591 - Clients can ask dirservers for /dir.z to get a compressed version
17592 of the directory. Only works for servers running 0.0.9, of course.
17593 - Make clients cache directories and use them to seed their router
17594 lists at startup. This means clients have a datadir again.
17595 - Respond to content-encoding headers by trying to uncompress as
17597 - Clients and servers now fetch running-routers; cache
17598 running-routers; compress running-routers; serve compressed
17600 - Make moria2 advertise a dirport of 80, so people behind firewalls
17601 will be able to get a directory.
17602 - Http proxy support
17603 - Dirservers translate requests for http://%s:%d/x to /x
17604 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17605 be routed through this host.
17606 - Clients ask for /tor/x rather than /x for new enough dirservers.
17607 This way we can one day coexist peacefully with apache.
17608 - Clients specify a "Host: %s%d" http header, to be compatible
17609 with more proxies, and so running squid on an exit node can work.
17610 - Protect dirservers from overzealous descriptor uploading -- wait
17611 10 seconds after directory gets dirty, before regenerating.
17613 o Features (packages and install):
17614 - Add NSI installer contributed by J Doe.
17615 - Apply NT service patch from Osamu Fujino. Still needs more work.
17616 - Commit VC6 and VC7 workspace/project files.
17617 - Commit a tor.spec for making RPM files, with help from jbash.
17618 - Add contrib/torctl.in contributed by Glenn Fink.
17619 - Make expand_filename handle ~ and ~username.
17620 - Use autoconf to enable largefile support where necessary. Use
17621 ftello where available, since ftell can fail at 2GB.
17622 - Ship src/win32/ in the tarball, so people can use it to build.
17623 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17626 o Features (ui controller):
17627 - Control interface: a separate program can now talk to your
17628 client/server over a socket, and get/set config options, receive
17629 notifications of circuits and streams starting/finishing/dying,
17630 bandwidth used, etc. The next step is to get some GUIs working.
17631 Let us know if you want to help out. See doc/control-spec.txt .
17632 - Ship a contrib/tor-control.py as an example script to interact
17633 with the control port.
17634 - "tor --hash-password zzyxz" will output a salted password for
17635 use in authenticating to the control interface.
17636 - Implement the control-spec's SAVECONF command, to write your
17637 configuration to torrc.
17638 - Get cookie authentication for the controller closer to working.
17639 - When set_conf changes our server descriptor, upload a new copy.
17640 But don't upload it too often if there are frequent changes.
17642 o Features (config and command-line):
17643 - Deprecate unofficial config option abbreviations, and abbreviations
17644 not on the command line.
17645 - Configuration infrastructure support for warning on obsolete
17647 - Give a slightly more useful output for "tor -h".
17648 - Break DirFetchPostPeriod into:
17649 - DirFetchPeriod for fetching full directory,
17650 - StatusFetchPeriod for fetching running-routers,
17651 - DirPostPeriod for posting server descriptor,
17652 - RendPostPeriod for posting hidden service descriptors.
17653 - New log format in config:
17654 "Log minsev[-maxsev] stdout|stderr|syslog" or
17655 "Log minsev[-maxsev] file /var/foo"
17656 - DirPolicy config option, to let people reject incoming addresses
17657 from their dirserver.
17658 - "tor --list-fingerprint" will list your identity key fingerprint
17660 - Make tor --version --version dump the cvs Id of every file.
17661 - New 'MyFamily nick1,...' config option for a server to
17662 specify other servers that shouldn't be used in the same circuit
17663 with it. Only believed if nick1 also specifies us.
17664 - New 'NodeFamily nick1,nick2,...' config option for a client to
17665 specify nodes that it doesn't want to use in the same circuit.
17666 - New 'Redirectexit pattern address:port' config option for a
17667 server to redirect exit connections, e.g. to a local squid.
17668 - Add "pass" target for RedirectExit, to make it easier to break
17669 out of a sequence of RedirectExit rules.
17670 - Make the dirservers file obsolete.
17671 - Include a dir-signing-key token in directories to tell the
17672 parsing entity which key is being used to sign.
17673 - Remove the built-in bulky default dirservers string.
17674 - New config option "Dirserver %s:%d [fingerprint]", which can be
17675 repeated as many times as needed. If no dirservers specified,
17676 default to moria1,moria2,tor26.
17677 - Make 'Routerfile' config option obsolete.
17678 - Discourage people from setting their dirfetchpostperiod more often
17679 than once per minute.
17681 o Features (other):
17682 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17683 get back to normal.)
17684 - Accept *:706 (silc) in default exit policy.
17685 - Implement new versioning format for post 0.1.
17686 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17687 log more informatively.
17688 - Check clock skew for verified servers, but allow unverified
17689 servers and clients to have any clock skew.
17690 - Make sure the hidden service descriptors are at a random offset
17691 from each other, to hinder linkability.
17692 - Clients now generate a TLS cert too, in preparation for having
17693 them act more like real nodes.
17694 - Add a pure-C tor-resolve implementation.
17695 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17696 1024) file descriptors.
17697 - Raise the max dns workers from 50 to 100.
17700 Changes in version 0.0.8.1 - 2004-10-13
17702 - Fix a seg fault that can be triggered remotely for Tor
17703 clients/servers with an open dirport.
17704 - Fix a rare assert trigger, where routerinfos for entries in
17705 our cpath would expire while we're building the path.
17706 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17707 - Fix a rare seg fault for people running hidden services on
17708 intermittent connections.
17709 - Fix a bug in parsing opt keywords with objects.
17710 - Fix a stale pointer assert bug when a stream detaches and
17712 - Fix a string format vulnerability (probably not exploitable)
17713 in reporting stats locally.
17714 - Fix an assert trigger: sometimes launching circuits can fail
17715 immediately, e.g. because too many circuits have failed recently.
17716 - Fix a compile warning on 64 bit platforms.
17719 Changes in version 0.0.8 - 2004-08-25
17721 - Made our unit tests compile again on OpenBSD 3.5, and tor
17722 itself compile again on OpenBSD on a sparc64.
17723 - We were neglecting milliseconds when logging on win32, so
17724 everything appeared to happen at the beginning of each second.
17725 - Check directory signature _before_ you decide whether you're
17726 you're running an obsolete version and should exit.
17727 - Check directory signature _before_ you parse the running-routers
17728 list to decide who's running.
17729 - Check return value of fclose while writing to disk, so we don't
17730 end up with broken files when servers run out of disk space.
17731 - Port it to SunOS 5.9 / Athena
17732 - Fix two bugs in saving onion keys to disk when rotating, so
17733 hopefully we'll get fewer people using old onion keys.
17734 - Remove our mostly unused -- and broken -- hex_encode()
17735 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17736 for pointing out this bug.)
17737 - Only pick and establish intro points after we've gotten a
17739 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17740 don't put it into the client dns cache.
17741 - If a begin failed due to exit policy, but we believe the IP
17742 address should have been allowed, switch that router to exitpolicy
17743 reject *:* until we get our next directory.
17745 o Protocol changes:
17746 - 'Extend' relay cell payloads now include the digest of the
17747 intended next hop's identity key. Now we can verify that we're
17748 extending to the right router, and also extend to routers we
17749 hadn't heard of before.
17752 - Tor nodes can now act as relays (with an advertised ORPort)
17753 without being manually verified by the dirserver operators.
17754 - Uploaded descriptors of unverified routers are now accepted
17755 by the dirservers, and included in the directory.
17756 - Verified routers are listed by nickname in the running-routers
17757 list; unverified routers are listed as "$<fingerprint>".
17758 - We now use hash-of-identity-key in most places rather than
17759 nickname or addr:port, for improved security/flexibility.
17760 - AllowUnverifiedNodes config option to let circuits choose no-name
17761 routers in entry,middle,exit,introduction,rendezvous positions.
17762 Allow middle and rendezvous positions by default.
17763 - When picking unverified routers, skip those with low uptime and/or
17764 low bandwidth, depending on what properties you care about.
17765 - ClientOnly option for nodes that never want to become servers.
17766 - Directory caching.
17767 - "AuthoritativeDir 1" option for the official dirservers.
17768 - Now other nodes (clients and servers) will cache the latest
17769 directory they've pulled down.
17770 - They can enable their DirPort to serve it to others.
17771 - Clients will pull down a directory from any node with an open
17772 DirPort, and check the signature/timestamp correctly.
17773 - Authoritative dirservers now fetch directories from other
17774 authdirservers, to stay better synced.
17775 - Running-routers list tells who's down also, along with noting
17776 if they're verified (listed by nickname) or unverified (listed
17778 - Allow dirservers to serve running-router list separately.
17779 This isn't used yet.
17780 - You can now fetch $DIRURL/running-routers to get just the
17781 running-routers line, not the whole descriptor list. (But
17782 clients don't use this yet.)
17783 - Clients choose nodes proportional to advertised bandwidth.
17784 - Clients avoid using nodes with low uptime as introduction points.
17785 - Handle servers with dynamic IP addresses: don't just replace
17786 options->Address with the resolved one at startup, and
17787 detect our address right before we make a routerinfo each time.
17788 - 'FascistFirewall' option to pick dirservers and ORs on specific
17789 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17790 which ports are open. (Defaults to 80,443)
17791 - Try other dirservers immediately if the one you try is down. This
17792 should tolerate down dirservers better now.
17793 - ORs connect-on-demand to other ORs
17794 - If you get an extend cell to an OR you're not connected to,
17795 connect, handshake, and forward the create cell.
17796 - The authoritative dirservers stay connected to everybody,
17797 and everybody stays connected to 0.0.7 servers, but otherwise
17798 clients/servers expire unused connections after 5 minutes.
17799 - When servers get a sigint, they delay 30 seconds (refusing new
17800 connections) then exit. A second sigint causes immediate exit.
17801 - File and name management:
17802 - Look for .torrc if no CONFDIR "torrc" is found.
17803 - If no datadir is defined, then choose, make, and secure ~/.tor
17805 - If torrc not found, exitpolicy reject *:*.
17806 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
17807 - If no nickname is defined, derive default from hostname.
17808 - Rename secret key files, e.g. identity.key -> secret_id_key,
17809 to discourage people from mailing their identity key to tor-ops.
17810 - Refuse to build a circuit before the directory has arrived --
17811 it won't work anyway, since you won't know the right onion keys
17813 - Parse tor version numbers so we can do an is-newer-than check
17814 rather than an is-in-the-list check.
17815 - New socks command 'resolve', to let us shim gethostbyname()
17817 - A 'tor_resolve' script to access the socks resolve functionality.
17818 - A new socks-extensions.txt doc file to describe our
17819 interpretation and extensions to the socks protocols.
17820 - Add a ContactInfo option, which gets published in descriptor.
17821 - Write tor version at the top of each log file
17822 - New docs in the tarball:
17824 - Document that you should proxy your SSL traffic too.
17825 - Log a warning if the user uses an unsafe socks variant, so people
17826 are more likely to learn about privoxy or socat.
17827 - Log a warning if you're running an unverified server, to let you
17828 know you might want to get it verified.
17829 - Change the default exit policy to reject the default edonkey,
17830 kazaa, gnutella ports.
17831 - Add replace_file() to util.[ch] to handle win32's rename().
17832 - Publish OR uptime in descriptor (and thus in directory) too.
17833 - Remember used bandwidth (both in and out), and publish 15-minute
17834 snapshots for the past day into our descriptor.
17835 - Be more aggressive about trying to make circuits when the network
17836 has changed (e.g. when you unsuspend your laptop).
17837 - Check for time skew on http headers; report date in response to
17839 - If the entrynode config line has only one node, don't pick it as
17841 - Add strict{entry|exit}nodes config options. If set to 1, then
17842 we refuse to build circuits that don't include the specified entry
17844 - OutboundBindAddress config option, to bind to a specific
17845 IP address for outgoing connect()s.
17846 - End truncated log entries (e.g. directories) with "[truncated]".
17849 Changes in version 0.0.7.3 - 2004-08-12
17850 o Stop dnsworkers from triggering an assert failure when you
17851 ask them to resolve the host "".
17854 Changes in version 0.0.7.2 - 2004-07-07
17855 o A better fix for the 0.0.0.0 problem, that will hopefully
17856 eliminate the remaining related assertion failures.
17859 Changes in version 0.0.7.1 - 2004-07-04
17860 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
17861 since internally we use 0.0.0.0 to signify "not yet resolved".
17864 Changes in version 0.0.7 - 2004-06-07
17865 o Fixes for crashes and other obnoxious bugs:
17866 - Fix an epipe bug: sometimes when directory connections failed
17867 to connect, we would give them a chance to flush before closing
17869 - When we detached from a circuit because of resolvefailed, we
17870 would immediately try the same circuit twice more, and then
17871 give up on the resolve thinking we'd tried three different
17873 - Limit the number of intro circuits we'll attempt to build for a
17874 hidden service per 15-minute period.
17875 - Check recommended-software string *early*, before actually parsing
17876 the directory. Thus we can detect an obsolete version and exit,
17877 even if the new directory format doesn't parse.
17878 o Fixes for security bugs:
17879 - Remember which nodes are dirservers when you startup, and if a
17880 random OR enables his dirport, don't automatically assume he's
17881 a trusted dirserver.
17883 - Directory connections were asking the wrong poll socket to
17884 start writing, and not asking themselves to start writing.
17885 - When we detached from a circuit because we sent a begin but
17886 didn't get a connected, we would use it again the first time;
17887 but after that we would correctly switch to a different one.
17888 - Stop warning when the first onion decrypt attempt fails; they
17889 will sometimes legitimately fail now that we rotate keys.
17890 - Override unaligned-access-ok check when $host_cpu is ia64 or
17891 arm. Apparently they allow it but the kernel whines.
17892 - Dirservers try to reconnect periodically too, in case connections
17894 - Fix some memory leaks in directory servers.
17895 - Allow backslash in Win32 filenames.
17896 - Made Tor build complain-free on FreeBSD, hopefully without
17897 breaking other BSD builds. We'll see.
17898 - Check directory signatures based on name of signer, not on whom
17899 we got the directory from. This will let us cache directories more
17901 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
17904 - Doxygen markup on all functions and global variables.
17905 - Make directory functions update routerlist, not replace it. So
17906 now directory disagreements are not so critical a problem.
17907 - Remove the upper limit on number of descriptors in a dirserver's
17908 directory (not that we were anywhere close).
17909 - Allow multiple logfiles at different severity ranges.
17910 - Allow *BindAddress to specify ":port" rather than setting *Port
17911 separately. Allow multiple instances of each BindAddress config
17912 option, so you can bind to multiple interfaces if you want.
17913 - Allow multiple exit policy lines, which are processed in order.
17914 Now we don't need that huge line with all the commas in it.
17915 - Enable accept/reject policies on SOCKS connections, so you can bind
17916 to 0.0.0.0 but still control who can use your OP.
17917 - Updated the man page to reflect these features.
17920 Changes in version 0.0.6.2 - 2004-05-16
17921 o Our integrity-checking digest was checking only the most recent cell,
17922 not the previous cells like we'd thought.
17923 Thanks to Stefan Mark for finding the flaw!
17926 Changes in version 0.0.6.1 - 2004-05-06
17927 o Fix two bugs in our AES counter-mode implementation (this affected
17928 onion-level stream encryption, but not TLS-level). It turns
17929 out we were doing something much more akin to a 16-character
17930 polyalphabetic cipher. Oops.
17931 Thanks to Stefan Mark for finding the flaw!
17932 o Retire moria3 as a directory server, and add tor26 as a directory
17936 Changes in version 0.0.6 - 2004-05-02
17938 - Hidden services and rendezvous points are implemented. Go to
17939 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
17940 hidden services. (This only works via a socks4a proxy such as
17941 Privoxy, and currently it's quite slow.)
17942 - We now rotate link (tls context) keys and onion keys.
17943 - CREATE cells now include oaep padding, so you can tell
17944 if you decrypted them correctly.
17945 - Retry stream correctly when we fail to connect because of
17946 exit-policy-reject (should try another) or can't-resolve-address.
17947 - When we hup a dirserver and we've *removed* a server from the
17948 approved-routers list, now we remove that server from the
17949 in-memory directories too.
17950 - Add bandwidthburst to server descriptor.
17951 - Directories now say which dirserver signed them.
17952 - Use a tor_assert macro that logs failed assertions too.
17953 - Since we don't support truncateds much, don't bother sending them;
17954 just close the circ.
17955 - Fetch randomness from /dev/urandom better (not via fopen/fread)
17956 - Better debugging for tls errors
17957 - Set Content-Type on the directory and hidserv descriptor.
17958 - Remove IVs from cipher code, since AES-ctr has none.
17960 - Fix an assert trigger for exit nodes that's been plaguing us since
17961 the days of 0.0.2prexx (thanks weasel!)
17962 - Fix a bug where we were closing tls connections intermittently.
17963 It turns out openssl keeps its errors around -- so if an error
17964 happens, and you don't ask about it, and then another openssl
17965 operation happens and succeeds, and you ask if there was an error,
17966 it tells you about the first error.
17967 - Fix a bug that's been lurking since 27 may 03 (!)
17968 When passing back a destroy cell, we would use the wrong circ id.
17969 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
17970 - Some versions of openssl have an SSL_pending function that erroneously
17971 returns bytes when there is a non-application record pending.
17972 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
17973 o We were using an array of length zero in a few places.
17974 o Win32's gethostbyname can't resolve an IP to an IP.
17975 o Win32's close can't close a socket.
17976 o Handle windows socket errors correctly.
17978 - check for <sys/limits.h> so we build on FreeBSD again, and
17979 <machine/limits.h> for NetBSD.
17982 Changes in version 0.0.5 - 2004-03-30
17983 o Install torrc as torrc.sample -- we no longer clobber your
17985 o Fix mangled-state bug in directory fetching (was causing sigpipes).
17986 o Only build circuits after we've fetched the directory: clients were
17987 using only the directory servers before they'd fetched a directory.
17988 This also means longer startup time; so it goes.
17989 o Fix an assert trigger where an OP would fail to handshake, and we'd
17990 expect it to have a nickname.
17991 o Work around a tsocks bug: do a socks reject when AP connection dies
17992 early, else tsocks goes into an infinite loop.
17993 o Hold socks connection open until reply is flushed (if possible)
17994 o Make exit nodes resolve IPs to IPs immediately, rather than asking
17995 the dns farm to do it.
17996 o Fix c99 aliasing warnings in rephist.c
17997 o Don't include server descriptors that are older than 24 hours in the
17999 o Give socks 'reject' replies their whole 15s to attempt to flush,
18000 rather than seeing the 60s timeout and assuming the flush had failed.
18001 o Clean automake droppings from the cvs repository
18002 o Add in a 'notice' log level for things the operator should hear
18003 but that aren't warnings
18006 Changes in version 0.0.4 - 2004-03-26
18007 o When connecting to a dirserver or OR and the network is down,
18011 Changes in version 0.0.3 - 2004-03-26
18012 o Warn and fail if server chose a nickname with illegal characters
18013 o Port to Solaris and Sparc:
18014 - include missing header fcntl.h
18015 - have autoconf find -lsocket -lnsl automatically
18016 - deal with hardware word alignment
18017 - make uname() work (solaris has a different return convention)
18018 - switch from using signal() to sigaction()
18019 o Preliminary work on reputation system:
18020 - Keep statistics on success/fail of connect attempts; they're published
18021 by kill -USR1 currently.
18022 - Add a RunTesting option to try to learn link state by creating test
18023 circuits, even when SocksPort is off.
18024 - Remove unused open circuits when there are too many.
18027 Changes in version 0.0.2 - 2004-03-19
18028 - Include strlcpy and strlcat for safer string ops
18029 - define INADDR_NONE so we compile (but still not run) on solaris
18032 Changes in version 0.0.2pre27 - 2004-03-14
18034 - Allow internal tor networks (we were rejecting internal IPs,
18035 now we allow them if they're set explicitly).
18036 - And fix a few endian issues.
18039 Changes in version 0.0.2pre26 - 2004-03-14
18041 - If a stream times out after 15s without a connected cell, don't
18042 try that circuit again: try a new one.
18043 - Retry streams at most 4 times. Then give up.
18044 - When a dirserver gets a descriptor from an unknown router, it
18045 logs its fingerprint (so the dirserver operator can choose to
18046 accept it even without mail from the server operator).
18047 - Inform unapproved servers when we reject their descriptors.
18048 - Make tor build on Windows again. It works as a client, who knows
18050 - Clearer instructions in the torrc for how to set up a server.
18051 - Be more efficient about reading fd's when our global token bucket
18052 (used for rate limiting) becomes empty.
18054 - Stop asserting that computers always go forward in time. It's
18056 - When we sent a cell (e.g. destroy) and then marked an OR connection
18057 expired, we might close it before finishing a flush if the other
18058 side isn't reading right then.
18059 - Don't allow dirservers to start if they haven't defined
18060 RecommendedVersions
18061 - We were caching transient dns failures. Oops.
18062 - Prevent servers from publishing an internal IP as their address.
18063 - Address a strcat vulnerability in circuit.c
18066 Changes in version 0.0.2pre25 - 2004-03-04
18068 - Put the OR's IP in its router descriptor, not its fqdn. That way
18069 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18072 - If the user typed in an address that didn't resolve, the server
18076 Changes in version 0.0.2pre24 - 2004-03-03
18078 - Fix an assertion failure in dns.c, where we were trying to dequeue
18079 a pending dns resolve even if it wasn't pending
18080 - Fix a spurious socks5 warning about still trying to write after the
18081 connection is finished.
18082 - Hold certain marked_for_close connections open until they're finished
18083 flushing, rather than losing bytes by closing them too early.
18084 - Correctly report the reason for ending a stream
18085 - Remove some duplicate calls to connection_mark_for_close
18086 - Put switch_id and start_daemon earlier in the boot sequence, so it
18087 will actually try to chdir() to options.DataDirectory
18088 - Make 'make test' exit(1) if a test fails; fix some unit tests
18089 - Make tor fail when you use a config option it doesn't know about,
18090 rather than warn and continue.
18091 - Make --version work
18092 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18095 Changes in version 0.0.2pre23 - 2004-02-29
18097 - Print a statement when the first circ is finished, so the user
18098 knows it's working.
18099 - If a relay cell is unrecognized at the end of the circuit,
18100 send back a destroy. (So attacks to mutate cells are more
18102 - New config option 'excludenodes' to avoid certain nodes for circuits.
18103 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18104 so you can collect coredumps there.
18106 - Fix a bug in tls flushing where sometimes data got wedged and
18107 didn't flush until more data got sent. Hopefully this bug was
18108 a big factor in the random delays we were seeing.
18109 - Make 'connected' cells include the resolved IP, so the client
18110 dns cache actually gets populated.
18111 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18112 - When we time-out on a stream and detach from the circuit, send an
18113 end cell down it first.
18114 - Only warn about an unknown router (in exitnodes, entrynodes,
18115 excludenodes) after we've fetched a directory.
18118 Changes in version 0.0.2pre22 - 2004-02-26
18120 - Servers publish less revealing uname information in descriptors.
18121 - More memory tracking and assertions, to crash more usefully when
18123 - If the default torrc isn't there, just use some default defaults.
18124 Plus provide an internal dirservers file if they don't have one.
18125 - When the user tries to use Tor as an http proxy, give them an http
18126 501 failure explaining that we're a socks proxy.
18127 - Dump a new router.desc on hup, to help confused people who change
18128 their exit policies and then wonder why router.desc doesn't reflect
18130 - Clean up the generic tor.sh init script that we ship with.
18132 - If the exit stream is pending on the resolve, and a destroy arrives,
18133 then the stream wasn't getting removed from the pending list. I
18134 think this was the one causing recent server crashes.
18135 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18136 - When it couldn't resolve any dirservers, it was useless from then on.
18137 Now it reloads the RouterFile (or default dirservers) if it has no
18139 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18140 many users don't even *have* a /usr/local/sbin/.
18143 Changes in version 0.0.2pre21 - 2004-02-18
18145 - There's a ChangeLog file that actually reflects the changelog.
18146 - There's a 'torify' wrapper script, with an accompanying
18147 tor-tsocks.conf, that simplifies the process of using tsocks for
18148 tor. It even has a man page.
18149 - The tor binary gets installed to sbin rather than bin now.
18150 - Retry streams where the connected cell hasn't arrived in 15 seconds
18151 - Clean up exit policy handling -- get the default out of the torrc,
18152 so we can update it without forcing each server operator to fix
18154 - Allow imaps and pop3s in default exit policy
18156 - Prevent picking middleman nodes as the last node in the circuit
18159 Changes in version 0.0.2pre20 - 2004-01-30
18161 - We now have a deb package, and it's in debian unstable. Go to
18162 it, apt-getters. :)
18163 - I've split the TotalBandwidth option into BandwidthRate (how many
18164 bytes per second you want to allow, long-term) and
18165 BandwidthBurst (how many bytes you will allow at once before the cap
18166 kicks in). This better token bucket approach lets you, say, set
18167 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18168 performance while not exceeding your monthly bandwidth quota.
18169 - Push out a tls record's worth of data once you've got it, rather
18170 than waiting until you've read everything waiting to be read. This
18171 may improve performance by pipelining better. We'll see.
18172 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18173 from failed circuits (if they haven't been connected yet) and attach
18175 - Expire old streams that haven't managed to connect. Some day we'll
18176 have them reattach to new circuits instead.
18179 - Fix several memory leaks that were causing servers to become bloated
18181 - Fix a few very rare assert triggers. A few more remain.
18182 - Setuid to User _before_ complaining about running as root.
18185 Changes in version 0.0.2pre19 - 2004-01-07
18187 - Fix deadlock condition in dns farm. We were telling a child to die by
18188 closing the parent's file descriptor to him. But newer children were
18189 inheriting the open file descriptor from the parent, and since they
18190 weren't closing it, the socket never closed, so the child never read
18191 eof, so he never knew to exit. Similarly, dns workers were holding
18192 open other sockets, leading to all sorts of chaos.
18193 - New cleaner daemon() code for forking and backgrounding.
18194 - If you log to a file, it now prints an entry at the top of the
18195 logfile so you know it's working.
18196 - The onionskin challenge length was 30 bytes longer than necessary.
18197 - Started to patch up the spec so it's not quite so out of date.
18200 Changes in version 0.0.2pre18 - 2004-01-02
18202 - Fix endian issues with the 'integrity' field in the relay header.
18203 - Fix a potential bug where connections in state
18204 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18207 Changes in version 0.0.2pre17 - 2003-12-30
18209 - Made --debuglogfile (or any second log file, actually) work.
18210 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18211 adversary could force us into an infinite loop.
18214 - Each onionskin handshake now includes a hash of the computed key,
18215 to prove the server's identity and help perfect forward secrecy.
18216 - Changed cell size from 256 to 512 bytes (working toward compatibility
18218 - Changed cell length to 2 bytes, and moved it to the relay header.
18219 - Implemented end-to-end integrity checking for the payloads of
18221 - Separated streamid from 'recognized' (otherwise circuits will get
18222 messed up when we try to have streams exit from the middle). We
18223 use the integrity-checking to confirm that a cell is addressed to
18225 - Randomize the initial circid and streamid values, so an adversary who
18226 breaks into a node can't learn how many circuits or streams have
18230 Changes in version 0.0.2pre16 - 2003-12-14
18232 - Fixed a bug that made HUP trigger an assert
18233 - Fixed a bug where a circuit that immediately failed wasn't being
18234 counted as a failed circuit in counting retries.
18237 - Now we close the circuit when we get a truncated cell: otherwise we're
18238 open to an anonymity attack where a bad node in the path truncates
18239 the circuit and then we open streams at him.
18240 - Add port ranges to exit policies
18241 - Add a conservative default exit policy
18242 - Warn if you're running tor as root
18243 - on HUP, retry OR connections and close/rebind listeners
18244 - options.EntryNodes: try these nodes first when picking the first node
18245 - options.ExitNodes: if your best choices happen to include any of
18246 your preferred exit nodes, you choose among just those preferred
18248 - options.ExcludedNodes: nodes that are never picked in path building
18251 Changes in version 0.0.2pre15 - 2003-12-03
18252 o Robustness and bugfixes:
18253 - Sometimes clients would cache incorrect DNS resolves, which would
18254 really screw things up.
18255 - An OP that goes offline would slowly leak all its sockets and stop
18257 - A wide variety of bugfixes in exit node selection, exit policy
18258 handling, and processing pending streams when a new circuit is
18260 - Pick nodes for a path only from those the directory says are up
18261 - Choose randomly from all running dirservers, not always the first one
18262 - Increase allowed http header size for directory fetch.
18263 - Stop writing to stderr (if we're daemonized it will be closed).
18264 - Enable -g always, so cores will be more useful to me.
18265 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18268 - Wrote a man page. It lists commonly used options.
18271 - Change default loglevel to warn.
18272 - Make PidFile default to null rather than littering in your CWD.
18273 - OnionRouter config option is now obsolete. Instead it just checks
18275 - Moved to a single unified torrc file for both clients and servers.
18278 Changes in version 0.0.2pre14 - 2003-11-29
18279 o Robustness and bugfixes:
18280 - Force the admin to make the DataDirectory himself
18281 - to get ownership/permissions right
18282 - so clients no longer make a DataDirectory and then never use it
18283 - fix bug where a client who was offline for 45 minutes would never
18284 pull down a directory again
18285 - fix (or at least hide really well) the dns assert bug that was
18286 causing server crashes
18287 - warnings and improved robustness wrt clockskew for certs
18288 - use the native daemon(3) to daemonize, when available
18289 - exit if bind() fails
18290 - exit if neither socksport nor orport is defined
18291 - include our own tor_timegm (Win32 doesn't have its own)
18292 - bugfix for win32 with lots of connections
18293 - fix minor bias in PRNG
18294 - make dirserver more robust to corrupt cached directory
18297 - Wrote the design document (woo)
18299 o Circuit building and exit policies:
18300 - Circuits no longer try to use nodes that the directory has told them
18302 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18303 bitcounts (18.0.0.0/8).
18304 - Make AP connections standby for a circuit if no suitable circuit
18305 exists, rather than failing
18306 - Circuits choose exit node based on addr/port, exit policies, and
18307 which AP connections are standing by
18308 - Bump min pathlen from 2 to 3
18309 - Relay end cells have a payload to describe why the stream ended.
18310 - If the stream failed because of exit policy, try again with a new
18312 - Clients have a dns cache to remember resolved addresses.
18313 - Notice more quickly when we have no working circuits
18316 - APPort is now called SocksPort
18317 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18319 - RecommendedVersions is now a config variable rather than
18320 hardcoded (for dirservers)
18321 - Reloads config on HUP
18322 - Usage info on -h or --help
18323 - If you set User and Group config vars, it'll setu/gid to them.
18325 Changes in version 0.0.2pre13 - 2003-10-19
18326 o General stability:
18327 - SSL_write no longer fails when it returns WANTWRITE and the number
18328 of bytes in the buf has changed by the next SSL_write call.
18329 - Fix segfault fetching directory when network is down
18330 - Fix a variety of minor memory leaks
18331 - Dirservers reload the fingerprints file on HUP, so I don't have
18332 to take down the network when I approve a new router
18333 - Default server config file has explicit Address line to specify fqdn
18336 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18337 - Make listener connections not ever alloc bufs
18339 o Autoconf improvements:
18340 - don't clobber an external CFLAGS in ./configure
18341 - Make install now works
18342 - create var/lib/tor on make install
18343 - autocreate a tor.sh initscript to help distribs
18344 - autocreate the torrc and sample-server-torrc with correct paths
18346 o Log files and Daemonizing now work:
18347 - If --DebugLogFile is specified, log to it at -l debug
18348 - If --LogFile is specified, use it instead of commandline
18349 - If --RunAsDaemon is set, tor forks and backgrounds on startup