1 Changes in version 0.3.3.4-alpha - 2018-03-29
2 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
3 the alpha testing of earlier releases in its series. We are
4 approaching a stable 0.3.3 release: more testing is welcome!
6 o New system requirements:
7 - When built with Rust, Tor now depends on version 0.2.39 of the
8 libc crate. Closes tickets 25310 and 25664.
10 o Major bugfixes (relay, connection):
11 - If we have failed to connect to a relay and received a connection
12 refused, timeout, or similar error (at the TCP level), do not try
13 that same address/port again for 60 seconds after the failure has
14 occurred. Fixes bug 24767; bugfix on 0.0.6.
16 o Minor features (geoip):
17 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
18 Country database. Closes ticket 25469.
20 o Minor features (log messages):
21 - Improve log message in the out-of-memory handler to include
22 information about memory usage from the different compression
23 backends. Closes ticket 25372.
25 o Minor features (sandbox):
26 - Explicitly permit the poll() system call when the Linux
27 seccomp2-based sandbox is enabled: apparently, some versions of
28 libc use poll() when calling getpwnam(). Closes ticket 25313.
30 o Minor bugfixes (C correctness):
31 - Fix a very unlikely (impossible, we believe) null pointer
32 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
33 Coverity; this is CID 1430932.
35 o Minor bugfixes (channel, client):
36 - Better identify client connection when reporting to the geoip
37 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
39 o Minor bugfixes (compilation):
40 - Fix a C99 compliance issue in our configuration script that caused
41 compilation issues when compiling Tor with certain versions of
42 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
44 o Minor bugfixes (controller, reliability):
45 - Avoid a (nonfatal) assertion failure when extending a one-hop
46 circuit from the controller to become a multihop circuit. Fixes
47 bug 24903; bugfix on 0.2.5.2-alpha.
49 o Minor bugfixes (networking):
50 - Tor will no longer reject IPv6 address strings from TorBrowser
51 when they are passed as hostnames in SOCKS5 requests. Fixes bug
52 25036, bugfix on Tor 0.3.1.2.
53 - string_is_valid_hostname() will not consider IP strings to be
54 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
56 o Minor bugfixes (onion service v3):
57 - Avoid an assertion failure when the next the next onion service
58 descriptor rotation type is out of sync with the consensus's
59 valid-after time. Instead, log a warning message with extra
60 information, so we can better hunt down the cause of this
61 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
63 o Minor bugfixes (testing):
64 - Avoid intermittent test failures due to a test that had relied on
65 onion service introduction point creation finishing within 5
66 seconds of real clock time. Fixes bug 25450; bugfix
68 - Rust crates are now automatically detected and tested. Previously,
69 some crates were not tested by `make test-rust` due to a static
70 string in the `src/test/test_rust.sh` script specifying which
71 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
73 o Minor bugfixes (testing, benchmarks):
74 - Fix a crash when running benchmark tests on win32 systems. The
75 crash was due to a mutex that wasn't initialized before logging
76 and options were initialized. Fixes bug 25479; bugfix
79 o Minor bugfixes (warnings, ipv6):
80 - Avoid a bug warning that could occur when trying to connect to a
81 relay over IPv6. This warning would occur on a Tor instance that
82 downloads router descriptors, but prefers to use microdescriptors.
83 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
85 o Code simplification and refactoring:
86 - Remove the old (deterministic) directory retry logic entirely:
87 We've used exponential backoff exclusively for some time. Closes
91 - Improved the documentation of AccountingStart parameter. Closes
93 - Update the documentation for "Log" to include the current list of
94 logging domains. Closes ticket 25378.
97 Changes in version 0.3.3.3-alpha - 2018-03-03
98 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
99 It includes an important security fix for a remote crash attack
100 against directory authorities tracked as TROVE-2018-001.
102 Additionally, with this release, we are upgrading the severity of a
103 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
104 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
105 a use-after-free pattern. As such, we are now tracking that bug as
106 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
107 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
109 This release also fixes several minor bugs and annoyances from
112 Relays running 0.3.2.x should upgrade to one of the versions released
113 today, for the fix to TROVE-2018-002. Directory authorities should
114 also upgrade. (Relays on earlier versions might want to update too for
115 the DoS mitigations.)
117 o Major bugfixes (denial-of-service, directory authority):
118 - Fix a protocol-list handling bug that could be used to remotely crash
119 directory authorities with a null-pointer exception. Fixes bug 25074;
120 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
123 o Minor features (compatibility, OpenSSL):
124 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
125 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
126 since they neither disabled TLS 1.3 nor enabled any of the
127 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
130 o Minor features (logging):
131 - Clarify the log messages produced when getrandom() or a related
132 entropy-generation mechanism gives an error. Closes ticket 25120.
134 o Minor features (testing):
135 - Add a "make test-rust" target to run the rust tests only. Closes
138 o Minor bugfixes (denial-of-service):
139 - Fix a possible crash on malformed consensus. If a consensus had
140 contained an unparseable protocol line, it could have made clients
141 and relays crash with a null-pointer exception. To exploit this
142 issue, however, an attacker would need to be able to subvert the
143 directory authority system. Fixes bug 25251; bugfix on
144 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
146 o Minor bugfixes (DoS mitigation):
147 - Add extra safety checks when refilling the circuit creation bucket
148 to ensure we never set a value above the allowed maximum burst.
149 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
150 - When a new consensus arrives, don't update our DoS-mitigation
151 parameters if we aren't a public relay. Fixes bug 25223; bugfix
154 o Minor bugfixes (man page, SocksPort):
155 - Remove dead code from the old "SocksSocket" option, and rename
156 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
157 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
159 o Minor bugfixes (performance):
160 - Reduce the number of circuits that will be opened at once during
161 the circuit build timeout phase. This is done by increasing the
162 idle timeout to 3 minutes, and lowering the maximum number of
163 concurrent learning circuits to 10. Fixes bug 24769; bugfix
166 o Minor bugfixes (spec conformance):
167 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
169 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
170 bugfix on 0.2.9.4-alpha.
172 o Minor bugfixes (spec conformance, rust):
173 - Resolve a denial-of-service issue caused by an infinite loop in
174 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
175 Also tracked as TROVE-2018-003.
177 o Code simplification and refactoring:
178 - Update the "rust dependencies" submodule to be a project-level
179 repository, rather than a user repository. Closes ticket 25323.
182 Changes in version 0.3.2.10 - 2018-03-03
183 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
184 backports a number of bugfixes, including important fixes for security
187 It includes an important security fix for a remote crash attack
188 against directory authorities, tracked as TROVE-2018-001.
190 Additionally, it backports a fix for a bug whose severity we have
191 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
192 triggered in order to crash relays with a use-after-free pattern. As
193 such, we are now tracking that bug as TROVE-2018-002 and
194 CVE-2018-0491, and backporting it to earlier releases. This bug
195 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
198 This release also backports our new system for improved resistance to
199 denial-of-service attacks against relays.
201 This release also fixes several minor bugs and annoyances from
204 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
205 today, for the fix to TROVE-2018-002. Directory authorities should
206 also upgrade. (Relays on earlier versions might want to update too for
207 the DoS mitigations.)
209 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
210 - Fix a protocol-list handling bug that could be used to remotely crash
211 directory authorities with a null-pointer exception. Fixes bug 25074;
212 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
215 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
216 - Avoid adding the same channel twice in the KIST scheduler pending
217 list, which could lead to remote denial-of-service use-after-free
218 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
220 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
221 - Give relays some defenses against the recent network overload. We
222 start with three defenses (default parameters in parentheses).
223 First: if a single client address makes too many concurrent
224 connections (>100), hang up on further connections. Second: if a
225 single client address makes circuits too quickly (more than 3 per
226 second, with an allowed burst of 90) while also having too many
227 connections open (3), refuse new create cells for the next while
228 (1-2 hours). Third: if a client asks to establish a rendezvous
229 point to you directly, ignore the request. These defenses can be
230 manually controlled by new torrc options, but relays will also
231 take guidance from consensus parameters, so there's no need to
232 configure anything manually. Implements ticket 24902.
234 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
235 - Fix an "off by 2" error in counting rendezvous failures on the
236 onion service side. While we thought we would stop the rendezvous
237 attempt after one failed circuit, we were actually making three
238 circuit attempts before giving up. Now switch to a default of 2,
239 and allow the consensus parameter "hs_service_max_rdv_failures" to
240 override. Fixes bug 24895; bugfix on 0.0.6.
241 - New-style (v3) onion services now obey the "max rendezvous circuit
242 attempts" logic. Previously they would make as many rendezvous
243 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
244 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
246 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
247 - Add Link protocol version 5 to the supported protocols list. Fixes
248 bug 25070; bugfix on 0.3.1.1-alpha.
250 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
251 - Fix a set of false positives where relays would consider
252 connections to other relays as being client-only connections (and
253 thus e.g. deserving different link padding schemes) if those
254 relays fell out of the consensus briefly. Now we look only at the
255 initial handshake and whether the connection authenticated as a
256 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
258 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
259 - The scheduler subsystem was failing to promptly notice changes in
260 consensus parameters, making it harder to switch schedulers
261 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
263 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
264 - Make our OOM handler aware of the geoip client history cache so it
265 doesn't fill up the memory. This check is important for IPv6 and
266 our DoS mitigation subsystem. Closes ticket 25122.
268 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
269 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
270 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
271 since they neither disabled TLS 1.3 nor enabled any of the
272 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
275 o Minor features (geoip):
276 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
279 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
280 - When logging a failure to check a hidden service's certificate,
281 also log what the problem with the certificate was. Diagnostic
284 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
285 - Use the actual observed address of an incoming relay connection,
286 not the canonical address of the relay from its descriptor, when
287 making decisions about how to handle the incoming connection.
288 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
290 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
291 - Fix a possible crash on malformed consensus. If a consensus had
292 contained an unparseable protocol line, it could have made clients
293 and relays crash with a null-pointer exception. To exploit this
294 issue, however, an attacker would need to be able to subvert the
295 directory authority system. Fixes bug 25251; bugfix on
296 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
298 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
299 - Directory authorities, when refusing a descriptor from a rejected
300 relay, now explicitly tell the relay (in its logs) to set a valid
301 ContactInfo address and contact the bad-relays@ mailing list.
302 Fixes bug 25170; bugfix on 0.2.9.1.
304 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
305 - When building with Rust on OSX, link against libresolv, to work
306 around the issue at https://github.com/rust-lang/rust/issues/46797.
307 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
309 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
310 - Remove a BUG() statement when a client fetches an onion descriptor
311 that has a lower revision counter than the one in its cache. This
312 can happen in normal circumstances due to HSDir desync. Fixes bug
313 24976; bugfix on 0.3.2.1-alpha.
315 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
316 - Don't treat inability to store a cached consensus object as a bug:
317 it can happen normally when we are out of disk space. Fixes bug
318 24859; bugfix on 0.3.1.1-alpha.
320 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
321 - Improve the performance of our consensus-diff application code
322 when Tor is built with the --enable-fragile-hardening option set.
323 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
325 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
326 - Don't exit the Tor process if setrlimit() fails to change the file
327 limit (which can happen sometimes on some versions of OSX). Fixes
328 bug 21074; bugfix on 0.0.9pre5.
330 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
331 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
333 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
334 bugfix on 0.2.9.4-alpha.
336 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
337 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
338 25005; bugfix on 0.3.2.7-rc.
340 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
341 - Look at the "HSRend" protocol version, not the "HSDir" protocol
342 version, when deciding whether a consensus entry can support the
343 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
344 bugfix on 0.3.2.1-alpha.
346 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
347 - Update the "rust dependencies" submodule to be a project-level
348 repository, rather than a user repository. Closes ticket 25323.
350 o Documentation (backport from 0.3.3.1-alpha)
351 - Document that operators who run more than one relay or bridge are
352 expected to set MyFamily and ContactInfo correctly. Closes
356 Changes in version 0.3.1.10 - 2018-03-03
357 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
360 It includes an important security fix for a remote crash attack
361 against directory authorities, tracked as TROVE-2018-001.
363 This release also backports our new system for improved resistance to
364 denial-of-service attacks against relays.
366 This release also fixes several minor bugs and annoyances from
369 All directory authorities should upgrade to one of the versions
370 released today. Relays running 0.3.1.x may wish to update to one of
371 the versions released today, for the DoS mitigations.
373 Please note: according to our release calendar, Tor 0.3.1 will no
374 longer be supported after 1 July 2018. If you will be running Tor
375 after that date, you should make sure to plan to upgrade to the latest
376 stable version, or downgrade to 0.2.9 (which will receive long-term
379 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
380 - Fix a protocol-list handling bug that could be used to remotely crash
381 directory authorities with a null-pointer exception. Fixes bug 25074;
382 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
385 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
386 - Give relays some defenses against the recent network overload. We
387 start with three defenses (default parameters in parentheses).
388 First: if a single client address makes too many concurrent
389 connections (>100), hang up on further connections. Second: if a
390 single client address makes circuits too quickly (more than 3 per
391 second, with an allowed burst of 90) while also having too many
392 connections open (3), refuse new create cells for the next while
393 (1-2 hours). Third: if a client asks to establish a rendezvous
394 point to you directly, ignore the request. These defenses can be
395 manually controlled by new torrc options, but relays will also
396 take guidance from consensus parameters, so there's no need to
397 configure anything manually. Implements ticket 24902.
399 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
400 - Update the sandbox rules so that they should now work correctly
401 with Glibc 2.26. Closes ticket 24315.
403 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
404 - Fix an "off by 2" error in counting rendezvous failures on the
405 onion service side. While we thought we would stop the rendezvous
406 attempt after one failed circuit, we were actually making three
407 circuit attempts before giving up. Now switch to a default of 2,
408 and allow the consensus parameter "hs_service_max_rdv_failures" to
409 override. Fixes bug 24895; bugfix on 0.0.6.
411 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
412 - Add Link protocol version 5 to the supported protocols list. Fixes
413 bug 25070; bugfix on 0.3.1.1-alpha.
415 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
416 - Fix a set of false positives where relays would consider
417 connections to other relays as being client-only connections (and
418 thus e.g. deserving different link padding schemes) if those
419 relays fell out of the consensus briefly. Now we look only at the
420 initial handshake and whether the connection authenticated as a
421 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
423 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
424 - Make our OOM handler aware of the geoip client history cache so it
425 doesn't fill up the memory. This check is important for IPv6 and
426 our DoS mitigation subsystem. Closes ticket 25122.
428 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
429 - Change relay bandwidth reporting stats interval from 4 hours to 24
430 hours in order to reduce the efficiency of guard discovery
431 attacks. Fixes ticket 23856.
433 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
434 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
435 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
436 since they neither disabled TLS 1.3 nor enabled any of the
437 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
440 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
441 - The fallback directory list has been re-generated based on the
442 current status of the network. Tor uses fallback directories to
443 bootstrap when it doesn't yet have up-to-date directory
444 information. Closes ticket 24801.
445 - Make the default DirAuthorityFallbackRate 0.1, so that clients
446 prefer to bootstrap from fallback directory mirrors. This is a
447 follow-up to 24679, which removed weights from the default
448 fallbacks. Implements ticket 24681.
450 o Minor features (geoip):
451 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
454 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
455 - Use the actual observed address of an incoming relay connection,
456 not the canonical address of the relay from its descriptor, when
457 making decisions about how to handle the incoming connection.
458 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
460 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
461 - Directory authorities, when refusing a descriptor from a rejected
462 relay, now explicitly tell the relay (in its logs) to set a valid
463 ContactInfo address and contact the bad-relays@ mailing list.
464 Fixes bug 25170; bugfix on 0.2.9.1.
466 o Minor bugfixes (address selection, backport from 0.3.2.9):
467 - When the fascist_firewall_choose_address_ functions don't find a
468 reachable address, set the returned address to the null address
469 and port. This is a precautionary measure, because some callers do
470 not check the return value. Fixes bug 24736; bugfix
473 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
474 - Fetch descriptors aggressively whenever we lack enough to build
475 circuits, regardless of how many descriptors we are missing.
476 Previously, we would delay launching the fetch when we had fewer
477 than 15 missing descriptors, even if some of those descriptors
478 were blocking circuits from building. Fixes bug 23985; bugfix on
479 0.1.1.11-alpha. The effects of this bug became worse in
480 0.3.0.3-alpha, when we began treating missing descriptors from our
481 primary guards as a reason to delay circuits.
482 - Don't try fetching microdescriptors from relays that have failed
483 to deliver them in the past. Fixes bug 23817; bugfix
486 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
487 - Fix a signed/unsigned comparison warning introduced by our fix to
488 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
490 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
491 - Avoid a crash when attempting to use the seccomp2 sandbox together
492 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
495 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
496 - Fix a possible crash on malformed consensus. If a consensus had
497 contained an unparseable protocol line, it could have made clients
498 and relays crash with a null-pointer exception. To exploit this
499 issue, however, an attacker would need to be able to subvert the
500 directory authority system. Fixes bug 25251; bugfix on
501 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
503 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
504 - Recover better from empty or corrupt files in the consensus cache
505 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
506 - When a consensus diff calculation is only partially successful,
507 only record the successful parts as having succeeded. Partial
508 success can happen if (for example) one compression method fails
509 but the others succeed. Previously we misrecorded all the
510 calculations as having succeeded, which would later cause a
511 nonfatal assertion failure. Fixes bug 24086; bugfix
514 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
515 - Tor now updates its guard state when it reads a consensus
516 regardless of whether it's missing descriptors. That makes tor use
517 its primary guards to fetch descriptors in some edge cases where
518 it would previously have used fallback directories. Fixes bug
519 23862; bugfix on 0.3.0.1-alpha.
521 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
522 - Don't treat inability to store a cached consensus object as a bug:
523 it can happen normally when we are out of disk space. Fixes bug
524 24859; bugfix on 0.3.1.1-alpha.
526 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
527 - When queuing DESTROY cells on a channel, only queue the circuit-id
528 and reason fields: not the entire 514-byte cell. This fix should
529 help mitigate any bugs or attacks that fill up these queues, and
530 free more RAM for other uses. Fixes bug 24666; bugfix
533 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
534 - When closing a connection via close_connection_immediately(), we
535 mark it as "not blocked on bandwidth", to prevent later calls from
536 trying to unblock it, and give it permission to read. This fixes a
537 backtrace warning that can happen on relays under various
538 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
540 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
541 - When selecting relays by bandwidth, avoid a rounding error that
542 could sometimes cause load to be imbalanced incorrectly.
543 Previously, we would always round upwards; now, we round towards
544 the nearest integer. This had the biggest effect when a relay's
545 weight adjustments should have given it weight 0, but it got
546 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
547 - When calculating the fraction of nodes that have descriptors, and
548 all nodes in the network have zero bandwidths, count the number of
549 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
550 - Actually log the total bandwidth in compute_weighted_bandwidths().
551 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
553 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
554 - Improve the performance of our consensus-diff application code
555 when Tor is built with the --enable-fragile-hardening option set.
556 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
558 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
559 - Don't exit the Tor process if setrlimit() fails to change the file
560 limit (which can happen sometimes on some versions of OSX). Fixes
561 bug 21074; bugfix on 0.0.9pre5.
563 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
564 - Fix a bug in the bit-counting parts of our timing-wheel code on
565 MSVC. (Note that MSVC is still not a supported build platform, due
566 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
569 o Minor bugfixes (relay, partial backport):
570 - Make the internal channel_is_client() function look at what sort
571 of connection handshake the other side used, rather than whether
572 the other side ever sent a create_fast cell to us. Backports part
573 of the fixes from bugs 22805 and 24898.
575 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
576 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
578 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
579 bugfix on 0.2.9.4-alpha.
581 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
582 - Update the "rust dependencies" submodule to be a project-level
583 repository, rather than a user repository. Closes ticket 25323.
586 Changes in version 0.2.9.15 - 2018-03-03
587 Tor 0.2.9.15 backports important security and stability bugfixes from
590 It includes an important security fix for a remote crash attack
591 against directory authorities, tracked as TROVE-2018-001.
593 This release also backports our new system for improved resistance to
594 denial-of-service attacks against relays.
596 This release also fixes several minor bugs and annoyances from
599 All directory authorities should upgrade to one of the versions
600 released today. Relays running 0.2.9.x may wish to update to one of
601 the versions released today, for the DoS mitigations.
603 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
604 - Fix a protocol-list handling bug that could be used to remotely crash
605 directory authorities with a null-pointer exception. Fixes bug 25074;
606 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
609 o Major features (denial-of-service mitigation):
610 - Give relays some defenses against the recent network overload. We
611 start with three defenses (default parameters in parentheses).
612 First: if a single client address makes too many concurrent
613 connections (>100), hang up on further connections. Second: if a
614 single client address makes circuits too quickly (more than 3 per
615 second, with an allowed burst of 90) while also having too many
616 connections open (3), refuse new create cells for the next while
617 (1-2 hours). Third: if a client asks to establish a rendezvous
618 point to you directly, ignore the request. These defenses can be
619 manually controlled by new torrc options, but relays will also
620 take guidance from consensus parameters, so there's no need to
621 configure anything manually. Implements ticket 24902.
623 o Major bugfixes (bootstrapping):
624 - Fetch descriptors aggressively whenever we lack enough to build
625 circuits, regardless of how many descriptors we are missing.
626 Previously, we would delay launching the fetch when we had fewer
627 than 15 missing descriptors, even if some of those descriptors
628 were blocking circuits from building. Fixes bug 23985; bugfix on
629 0.1.1.11-alpha. The effects of this bug became worse in
630 0.3.0.3-alpha, when we began treating missing descriptors from our
631 primary guards as a reason to delay circuits.
633 o Major bugfixes (onion services, retry behavior):
634 - Fix an "off by 2" error in counting rendezvous failures on the
635 onion service side. While we thought we would stop the rendezvous
636 attempt after one failed circuit, we were actually making three
637 circuit attempts before giving up. Now switch to a default of 2,
638 and allow the consensus parameter "hs_service_max_rdv_failures" to
639 override. Fixes bug 24895; bugfix on 0.0.6.
641 o Minor feature (relay statistics):
642 - Change relay bandwidth reporting stats interval from 4 hours to 24
643 hours in order to reduce the efficiency of guard discovery
644 attacks. Fixes ticket 23856.
646 o Minor features (compatibility, OpenSSL):
647 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
648 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
649 since they neither disabled TLS 1.3 nor enabled any of the
650 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
653 o Minor features (denial-of-service avoidance):
654 - Make our OOM handler aware of the geoip client history cache so it
655 doesn't fill up the memory. This check is important for IPv6 and
656 our DoS mitigation subsystem. Closes ticket 25122.
658 o Minor features (fallback directory mirrors):
659 - The fallback directory list has been re-generated based on the
660 current status of the network. Tor uses fallback directories to
661 bootstrap when it doesn't yet have up-to-date directory
662 information. Closes ticket 24801.
663 - Make the default DirAuthorityFallbackRate 0.1, so that clients
664 prefer to bootstrap from fallback directory mirrors. This is a
665 follow-up to 24679, which removed weights from the default
666 fallbacks. Implements ticket 24681.
668 o Minor features (geoip):
669 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
672 o Minor features (linux seccomp2 sandbox):
673 - Update the sandbox rules so that they should now work correctly
674 with Glibc 2.26. Closes ticket 24315.
676 o Minor bugfix (channel connection):
677 - Use the actual observed address of an incoming relay connection,
678 not the canonical address of the relay from its descriptor, when
679 making decisions about how to handle the incoming connection.
680 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
682 o Minor bugfix (directory authority):
683 - Directory authorities, when refusing a descriptor from a rejected
684 relay, now explicitly tell the relay (in its logs) to set a valid
685 ContactInfo address and contact the bad-relays@ mailing list.
686 Fixes bug 25170; bugfix on 0.2.9.1.
688 o Minor bugfixes (address selection):
689 - When the fascist_firewall_choose_address_ functions don't find a
690 reachable address, set the returned address to the null address
691 and port. This is a precautionary measure, because some callers do
692 not check the return value. Fixes bug 24736; bugfix
695 o Minor bugfixes (compilation):
696 - Fix a signed/unsigned comparison warning introduced by our fix to
697 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
699 o Minor bugfixes (control port, linux seccomp2 sandbox):
700 - Avoid a crash when attempting to use the seccomp2 sandbox together
701 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
704 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
705 - Fix a possible crash on malformed consensus. If a consensus had
706 contained an unparseable protocol line, it could have made clients
707 and relays crash with a null-pointer exception. To exploit this
708 issue, however, an attacker would need to be able to subvert the
709 directory authority system. Fixes bug 25251; bugfix on
710 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
712 o Minor bugfixes (memory usage):
713 - When queuing DESTROY cells on a channel, only queue the circuit-id
714 and reason fields: not the entire 514-byte cell. This fix should
715 help mitigate any bugs or attacks that fill up these queues, and
716 free more RAM for other uses. Fixes bug 24666; bugfix
719 o Minor bugfixes (network layer):
720 - When closing a connection via close_connection_immediately(), we
721 mark it as "not blocked on bandwidth", to prevent later calls from
722 trying to unblock it, and give it permission to read. This fixes a
723 backtrace warning that can happen on relays under various
724 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
726 o Minor bugfixes (OSX):
727 - Don't exit the Tor process if setrlimit() fails to change the file
728 limit (which can happen sometimes on some versions of OSX). Fixes
729 bug 21074; bugfix on 0.0.9pre5.
731 o Minor bugfixes (path selection):
732 - When selecting relays by bandwidth, avoid a rounding error that
733 could sometimes cause load to be imbalanced incorrectly.
734 Previously, we would always round upwards; now, we round towards
735 the nearest integer. This had the biggest effect when a relay's
736 weight adjustments should have given it weight 0, but it got
737 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
738 - When calculating the fraction of nodes that have descriptors, and
739 all nodes in the network have zero bandwidths, count the number of
740 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
741 - Actually log the total bandwidth in compute_weighted_bandwidths().
742 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
744 o Minor bugfixes (portability, msvc):
745 - Fix a bug in the bit-counting parts of our timing-wheel code on
746 MSVC. (Note that MSVC is still not a supported build platform, due
747 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
750 o Minor bugfixes (relay):
751 - Make the internal channel_is_client() function look at what sort
752 of connection handshake the other side used, rather than whether
753 the other side ever sent a create_fast cell to us. Backports part
754 of the fixes from bugs 22805 and 24898.
756 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
757 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
759 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
760 bugfix on 0.2.9.4-alpha.
763 Changes in version 0.3.3.2-alpha - 2018-02-10
764 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
765 introduces a mechanism to handle the high loads that many relay
766 operators have been reporting recently. It also fixes several bugs in
767 older releases. If this new code proves reliable, we plan to backport
768 it to older supported release series.
770 o Major features (denial-of-service mitigation):
771 - Give relays some defenses against the recent network overload. We
772 start with three defenses (default parameters in parentheses).
773 First: if a single client address makes too many concurrent
774 connections (>100), hang up on further connections. Second: if a
775 single client address makes circuits too quickly (more than 3 per
776 second, with an allowed burst of 90) while also having too many
777 connections open (3), refuse new create cells for the next while
778 (1-2 hours). Third: if a client asks to establish a rendezvous
779 point to you directly, ignore the request. These defenses can be
780 manually controlled by new torrc options, but relays will also
781 take guidance from consensus parameters, so there's no need to
782 configure anything manually. Implements ticket 24902.
784 o Major bugfixes (netflow padding):
785 - Stop adding unneeded channel padding right after we finish
786 flushing to a connection that has been trying to flush for many
787 seconds. Instead, treat all partial or complete flushes as
788 activity on the channel, which will defer the time until we need
789 to add padding. This fix should resolve confusing and scary log
790 messages like "Channel padding timeout scheduled 221453ms in the
791 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
793 o Major bugfixes (protocol versions):
794 - Add Link protocol version 5 to the supported protocols list. Fixes
795 bug 25070; bugfix on 0.3.1.1-alpha.
797 o Major bugfixes (scheduler, consensus):
798 - The scheduler subsystem was failing to promptly notice changes in
799 consensus parameters, making it harder to switch schedulers
800 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
802 o Minor features (denial-of-service avoidance):
803 - Make our OOM handler aware of the geoip client history cache so it
804 doesn't fill up the memory. This check is important for IPv6 and
805 our DoS mitigation subsystem. Closes ticket 25122.
807 o Minor features (directory authority):
808 - When directory authorities are unable to add signatures to a
809 pending consensus, log the reason why. Closes ticket 24849.
811 o Minor features (geoip):
812 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
815 o Minor features (logging, diagnostic):
816 - When logging a failure to create an onion service's descriptor,
817 also log what the problem with the descriptor was. Diagnostic for
820 o Minor bugfix (channel connection):
821 - Use the actual observed address of an incoming relay connection,
822 not the canonical address of the relay from its descriptor, when
823 making decisions about how to handle the incoming connection.
824 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
826 o Minor bugfix (directory authority):
827 - Directory authorities, when refusing a descriptor from a rejected
828 relay, now explicitly tell the relay (in its logs) to set a valid
829 ContactInfo address and contact the bad-relays@ mailing list.
830 Fixes bug 25170; bugfix on 0.2.9.1.
832 o Minor bugfixes (all versions of Tor):
833 - Use the "misspell" tool to detect and fix typos throughout the
834 source code. Fixes bug 23650; bugfix on various versions of Tor.
835 Patch from Deepesh Pathak.
837 o Minor bugfixes (circuit, cannibalization):
838 - Don't cannibalize preemptively-built circuits if we no longer
839 recognize their first hop. This situation can happen if our Guard
840 relay went off the consensus after the circuit was created. Fixes
841 bug 24469; bugfix on 0.0.6.
843 o Minor bugfixes (correctness):
844 - Remove a nonworking, unnecessary check to see whether a circuit
845 hop's identity digest was set when the circuit failed. Fixes bug
846 24927; bugfix on 0.2.4.4-alpha.
848 o Minor bugfixes (logging):
849 - Don't treat inability to store a cached consensus object as a bug:
850 it can happen normally when we are out of disk space. Fixes bug
851 24859; bugfix on 0.3.1.1-alpha.
852 - Fix a (mostly harmless) race condition when invoking
853 LOG_PROTOCOL_WARN message from a subthread while the torrc options
854 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
856 o Minor bugfixes (onion services):
857 - Remove a BUG() statement when a client fetches an onion descriptor
858 that has a lower revision counter than the one in its cache. This
859 can happen in normal circumstances due to HSDir desync. Fixes bug
860 24976; bugfix on 0.3.2.1-alpha.
861 - If we are configured to offer a single onion service, don't log
862 long-term established one hop rendezvous points in the heartbeat.
863 Fixes bug 25116; bugfix on 0.2.9.6-rc.
865 o Minor bugfixes (performance):
866 - Avoid calling protocol_list_supports_protocol() from inside tight
867 loops when running with cached routerinfo_t objects. Instead,
868 summarize the relevant protocols as flags in the routerinfo_t, as
869 we do for routerstatus_t objects. This change simplifies our code
870 a little, and saves a large amount of short-term memory allocation
871 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
873 o Minor bugfixes (Rust FFI):
874 - Fix a minor memory leak which would happen whenever the C code
875 would call the Rust implementation of
876 protover_get_supported_protocols(). This was due to the C version
877 returning a static string, whereas the Rust version newly allocated
878 a CString to pass accross the FFI boundary. Consequently, the C
879 code was not expecting to need to free() what it was given. Fixes
880 bug 25127; bugfix on 0.3.2.1-alpha.
882 o Minor bugfixes (scheduler, KIST):
883 - Avoid adding the same channel twice in the KIST scheduler pending
884 list, which would waste CPU cycles. Fixes bug 24700; bugfix
887 o Minor bugfixes (unit test, monotonic time):
888 - Increase a constant (1msec to 10msec) in the monotonic time test
889 that makes sure the nsec/usec/msec times read are synchronized.
890 This change was needed to accommodate slow systems like armel or
891 when the clock_gettime() is not a VDSO on the running kernel.
892 Fixes bug 25113; bugfix on 0.2.9.1.
894 o Minor bugfixes (v3 onion services):
895 - Look at the "HSRend" protocol version, not the "HSDir" protocol
896 version, when deciding whether a consensus entry can support the
897 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
898 bugfix on 0.3.2.1-alpha.
900 o Code simplification and refactoring:
901 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
903 - Remove a series of counters used to track circuit extend attempts
904 and connection status but that in reality we aren't using for
905 anything other than stats logged by a SIGUSR1 signal. Closes
908 o Documentation (man page):
909 - The HiddenServiceVersion torrc option accepts only one number:
910 either version 2 or 3. Closes ticket 25026; bugfix
914 Changes in version 0.3.3.1-alpha - 2018-01-25
915 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
916 several new features to Tor, including several improvements to
917 bootstrapping, and support for an experimental "vanguards" feature to
918 resist guard discovery attacks. This series also includes better
919 support for applications that need to embed Tor or manage v3
922 o Major features (embedding):
923 - There is now a documented stable API for programs that need to
924 embed Tor. See tor_api.h for full documentation and known bugs.
926 - Tor now has support for restarting in the same process.
927 Controllers that run Tor using the "tor_api.h" interface can now
928 restart Tor after Tor has exited. This support is incomplete,
929 however: we fixed crash bugs that prevented it from working at
930 all, but many bugs probably remain, including a possibility of
931 security issues. Implements ticket 24581.
933 o Major features (IPv6, directory documents):
934 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
935 consensus. This information makes it easier for IPv6 clients to
936 bootstrap and choose reachable entry guards. Implements 23826.
937 - Add consensus method 28, which removes IPv6 ORPorts from
938 microdescriptors. Now that the consensus contains IPv6 ORPorts,
939 they are redundant in microdescs. This change will be used by Tor
940 clients on 0.2.8.x and later. (That is to say, with all Tor
941 clients having IPv6 bootstrap and guard support.) Implements 23828.
942 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
943 set by different numbers of authorities. Fixes 23870
946 o Major features (onion service v3, control port):
947 - The control port now supports commands and events for v3 onion
948 services. It is now possible to create ephemeral v3 services using
949 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
950 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
951 DEL_ONION) have been extended to support v3 onion services. Closes
952 ticket 20699; implements proposal 284.
954 o Major features (onion services):
955 - Provide torrc options to pin the second and third hops of onion
956 service circuits to a list of nodes. The option HSLayer2Guards
957 pins the second hop, and the option HSLayer3Guards pins the third
958 hop. These options are for use in conjunction with experiments
959 with "vanguards" for preventing guard enumeration attacks. Closes
962 o Major features (rust, portability, experimental):
963 - Tor now ships with an optional implementation of one of its
964 smaller modules (protover.c) in the Rust programming language. To
965 try it out, install a Rust build environment, and configure Tor
966 with "--enable-rust --enable-cargo-online-mode". This should not
967 cause any user-visible changes, but should help us gain more
968 experience with Rust, and plan future Rust integration work.
969 Implementation by Chelsea Komlo. Closes ticket 22840.
971 o Major features (storage, configuration):
972 - Users can store cached directory documents somewhere other than
973 the DataDirectory by using the CacheDirectory option. Similarly,
974 the storage location for relay's keys can be overridden with the
975 KeyDirectory option. Closes ticket 22703.
977 o Major features (v3 onion services, ipv6):
978 - When v3 onion service clients send introduce cells, they now
979 include the IPv6 address of the rendezvous point, if it has one.
980 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
981 in future Tor versions, IPv6-only v3 single onion services will be
982 able to use IPv6 addresses to connect directly to the rendezvous
983 point. Closes ticket 23577. Patch by Neel Chauhan.
985 o Major bugfixes (onion services, retry behavior):
986 - Fix an "off by 2" error in counting rendezvous failures on the
987 onion service side. While we thought we would stop the rendezvous
988 attempt after one failed circuit, we were actually making three
989 circuit attempts before giving up. Now switch to a default of 2,
990 and allow the consensus parameter "hs_service_max_rdv_failures" to
991 override. Fixes bug 24895; bugfix on 0.0.6.
992 - New-style (v3) onion services now obey the "max rendezvous circuit
993 attempts" logic. Previously they would make as many rendezvous
994 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
995 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
997 o Major bugfixes (relays):
998 - Fix a set of false positives where relays would consider
999 connections to other relays as being client-only connections (and
1000 thus e.g. deserving different link padding schemes) if those
1001 relays fell out of the consensus briefly. Now we look only at the
1002 initial handshake and whether the connection authenticated as a
1003 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1005 o Minor feature (IPv6):
1006 - Make IPv6-only clients wait for microdescs for relays, even if we
1007 were previously using descriptors (or were using them as a bridge)
1008 and have a cached descriptor for them. Implements 23827.
1009 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
1010 them, rather than waiting to download microdescriptors.
1013 o Minor features (cleanup):
1014 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
1015 when it stops. Closes ticket 23271.
1017 o Minor features (defensive programming):
1018 - Most of the functions in Tor that free objects have been replaced
1019 with macros that free the objects and set the corresponding
1020 pointers to NULL. This change should help prevent a large class of
1021 dangling pointer bugs. Closes ticket 24337.
1022 - Where possible, the tor_free() macro now only evaluates its input
1023 once. Part of ticket 24337.
1024 - Check that microdesc ed25519 ids are non-zero in
1025 node_get_ed25519_id() before returning them. Implements 24001,
1026 patch by "aruna1234".
1028 o Minor features (directory authority):
1029 - Make the "Exit" flag assignment only depend on whether the exit
1030 policy allows connections to ports 80 and 443. Previously relays
1031 would get the Exit flag if they allowed connections to one of
1032 these ports and also port 6667. Resolves ticket 23637.
1034 o Minor features (embedding):
1035 - Tor can now start with a preauthenticated control connection
1036 created by the process that launched it. This feature is meant for
1037 use by programs that want to launch and manage a Tor process
1038 without allowing other programs to manage it as well. For more
1039 information, see the __OwningControllerFD option documented in
1040 control-spec.txt. Closes ticket 23900.
1041 - On most errors that would cause Tor to exit, it now tries to
1042 return from the tor_main() function, rather than calling the
1043 system exit() function. Most users won't notice a difference here,
1044 but it should make a significant for programs that run Tor inside
1045 a separate thread: they should now be able to survive Tor's exit
1046 conditions rather than having Tor shut down the entire process.
1047 Closes ticket 23848.
1048 - Applications that want to embed Tor can now tell Tor not to
1049 register any of its own POSIX signal handlers, using the
1050 __DisableSignalHandlers option. Closes ticket 24588.
1052 o Minor features (fallback directory list):
1053 - Avoid selecting fallbacks that change their IP addresses too
1054 often. Select more fallbacks by ignoring the Guard flag, and
1055 allowing lower cutoffs for the Running and V2Dir flags. Also allow
1056 a lower bandwidth, and a higher number of fallbacks per operator
1057 (5% of the list). Implements ticket 24785.
1058 - Update the fallback whitelist and blacklist based on opt-ins and
1059 relay changes. Closes tickets 22321, 24678, 22527, 24135,
1062 o Minor features (fallback directory mirror configuration):
1063 - Add a nickname to each fallback in a C comment. This makes it
1064 easier for operators to find their relays, and allows stem to use
1065 nicknames to identify fallbacks. Implements ticket 24600.
1066 - Add a type and version header to the fallback directory mirror
1067 file. Also add a delimiter to the end of each fallback entry. This
1068 helps external parsers like stem and Relay Search. Implements
1070 - Add an extrainfo cache flag for each fallback in a C comment. This
1071 allows stem to use fallbacks to fetch extra-info documents, rather
1072 than using authorities. Implements ticket 22759.
1073 - Add the generateFallbackDirLine.py script for automatically
1074 generating fallback directory mirror lines from relay fingerprints.
1075 No more typos! Add the lookupFallbackDirContact.py script for
1076 automatically looking up operator contact info from relay
1077 fingerprints. Implements ticket 24706, patch by teor and atagar.
1078 - Reject any fallback directory mirror that serves an expired
1079 consensus. Implements ticket 20942, patch by "minik".
1080 - Remove commas and equals signs from external string inputs to the
1081 fallback list. This avoids format confusion attacks. Implements
1083 - Remove the "weight=10" line from fallback directory mirror
1084 entries. Ticket 24681 will maintain the current fallback weights
1085 by changing Tor's default fallback weight to 10. Implements
1087 - Stop logging excessive information about fallback netblocks.
1088 Implements ticket 24791.
1090 o Minor features (forward-compatibility):
1091 - If a relay supports some link authentication protocol that we do
1092 not recognize, then include that relay's ed25519 key when telling
1093 other relays to extend to it. Previously, we treated future
1094 versions as if they were too old to support ed25519 link
1095 authentication. Closes ticket 20895.
1097 o Minor features (heartbeat):
1098 - Add onion service information to our heartbeat logs, displaying
1099 stats about the activity of configured onion services. Closes
1102 o Minor features (instrumentation, development):
1103 - Add the MainloopStats option to allow developers to get
1104 instrumentation information from the main event loop via the
1105 heartbeat messages. We hope to use this to improve Tor's behavior
1106 when it's trying to sleep. Closes ticket 24605.
1108 o Minor features (log messages):
1109 - Improve a warning message that happens when we fail to re-parse an
1110 old router because of an expired certificate. Closes ticket 20020.
1111 - Make the log more quantitative when we hit MaxMemInQueues
1112 threshold exposing some values. Closes ticket 24501.
1114 o Minor features (logging, android):
1115 - Added support for the Android logging subsystem. Closes
1118 o Minor features (performance):
1119 - Support predictive circuit building for onion service circuits
1120 with multiple layers of guards. Closes ticket 23101.
1121 - Use stdatomic.h where available, rather than mutexes, to implement
1122 atomic_counter_t. Closes ticket 23953.
1124 o Minor features (performance, 32-bit):
1125 - Improve performance on 32-bit systems by avoiding 64-bit division
1126 when calculating the timestamp in milliseconds for channel padding
1127 computations. Implements ticket 24613.
1128 - Improve performance on 32-bit systems by avoiding 64-bit division
1129 when timestamping cells and buffer chunks for OOM calculations.
1130 Implements ticket 24374.
1132 o Minor features (performance, OSX, iOS):
1133 - Use the mach_approximate_time() function (when available) to
1134 implement coarse monotonic time. Having a coarse time function
1135 should avoid a large number of system calls, and improve
1136 performance slightly, especially under load. Closes ticket 24427.
1138 o Minor features (performance, windows):
1139 - Improve performance on Windows Vista and Windows 7 by adjusting
1140 TCP send window size according to the recommendation from
1141 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
1144 o Minor features (relay):
1145 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
1146 operator to use a more reasonable ("reduced") exit policy, rather
1147 than the default one. If you want to run an exit node without
1148 thinking too hard about which ports to allow, this one is for you.
1149 Closes ticket 13605. Patch from Neel Chauhan.
1151 o Minor features (testing, debugging, embedding):
1152 - For development purposes, Tor now has a mode in which it runs for
1153 a few seconds, then stops, and starts again without exiting the
1154 process. This mode is meant to help us debug various issues with
1155 ticket 23847. To use this feature, compile with
1156 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
1157 environment variable. This is expected to crash a lot, and is
1158 really meant for developers only. It will likely be removed in a
1159 future release. Implements ticket 24583.
1161 o Minor bugfix (network IPv6 test):
1162 - Tor's test scripts now check if "ping -6 ::1" works when the user
1163 runs "make test-network-all". Fixes bug 24677; bugfix on
1164 0.2.9.3-alpha. Patch by "ffmancera".
1166 o Minor bugfixes (build, rust):
1167 - Fix output of autoconf checks to display success messages for Rust
1168 dependencies and a suitable rustc compiler version. Fixes bug
1169 24612; bugfix on 0.3.1.3-alpha.
1170 - When building with Rust on OSX, link against libresolv, to work
1171 around the issue at https://github.com/rust-lang/rust/issues/46797.
1172 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1173 - Don't pass the --quiet option to cargo: it seems to suppress some
1174 errors, which is not what we want to do when building. Fixes bug
1175 24518; bugfix on 0.3.1.7.
1176 - Build correctly when building from outside Tor's source tree with
1177 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
1180 o Minor bugfixes (directory authorities, IPv6):
1181 - When creating a routerstatus (vote) from a routerinfo (descriptor),
1182 set the IPv6 address to the unspecified IPv6 address, and
1183 explicitly initialize the port to zero. Fixes bug 24488; bugfix
1186 o Minor bugfixes (fallback directory mirrors):
1187 - Make updateFallbackDirs.py search harder for python. (Some OSs
1188 don't put it in /usr/bin.) Fixes bug 24708; bugfix
1191 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
1192 - When hibernating, close connections normally and allow them to
1193 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
1195 - Do not attempt to launch self-reachability tests when entering
1196 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1197 - Resolve several bugs related to descriptor fetching on bridge
1198 clients with bandwidth accounting enabled. (This combination is
1199 not recommended!) Fixes a case of bug 12062; bugfix
1201 - When hibernating, do not attempt to launch DNS checks. Fixes a
1202 case of bug 12062; bugfix on 0.1.2.2-alpha.
1203 - When hibernating, do not try to upload or download descriptors.
1204 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1206 o Minor bugfixes (IPv6, bridges):
1207 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
1208 bugfix on 0.2.8.2-alpha.
1209 - Tor now sets IPv6 address in the routerstatus as well as in the
1210 router descriptors when updating addresses for a bridge. Closes
1211 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
1213 o Minor bugfixes (linux seccomp2 sandbox):
1214 - When running with the sandbox enabled, reload configuration files
1215 correctly even when %include was used. Previously we would crash.
1216 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
1218 o Minor bugfixes (memory leaks):
1219 - Avoid possible at-exit memory leaks related to use of Libevent's
1220 event_base_once() function. (This function tends to leak memory if
1221 the event_base is closed before the event fires.) Fixes bug 24584;
1222 bugfix on 0.2.8.1-alpha.
1223 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
1226 o Minor bugfixes (OSX):
1227 - Don't exit the Tor process if setrlimit() fails to change the file
1228 limit (which can happen sometimes on some versions of OSX). Fixes
1229 bug 21074; bugfix on 0.0.9pre5.
1231 o Minor bugfixes (performance, fragile-hardening):
1232 - Improve the performance of our consensus-diff application code
1233 when Tor is built with the --enable-fragile-hardening option set.
1234 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1236 o Minor bugfixes (performance, timeouts):
1237 - Consider circuits for timeout as soon as they complete a hop. This
1238 is more accurate than applying the timeout in
1239 circuit_expire_building() because that function is only called
1240 once per second, which is now too slow for typical timeouts on the
1241 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
1242 - Use onion service circuits (and other circuits longer than 3 hops)
1243 to calculate a circuit build timeout. Previously, Tor only
1244 calculated its build timeout based on circuits that planned to be
1245 exactly 3 hops long. With this change, we include measurements
1246 from all circuits at the point where they complete their third
1247 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
1249 o Minor bugfixes (testing):
1250 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
1251 bugfix on 0.2.3.1-alpha.
1252 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1253 25005; bugfix on 0.3.2.7-rc.
1255 o Code simplification and refactoring:
1256 - Remove /usr/athena from search path in configure.ac. Closes
1258 - Remove duplicate code in node_has_curve25519_onion_key() and
1259 node_get_curve25519_onion_key(), and add a check for a zero
1260 microdesc curve25519 onion key. Closes ticket 23966, patch by
1261 "aruna1234" and teor.
1262 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
1263 memory allocations with large numbers of OR connections (e.g.
1264 relays). Closes ticket 24119.
1265 - Separate the function that deletes ephemeral files when Tor
1267 - Small changes to Tor's buf_t API to make it suitable for use as a
1268 general-purpose safe string constructor. Closes ticket 22342.
1269 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
1270 avoid source code identifier confusion. Closes ticket 24467.
1271 - The tor_git_revision[] constant no longer needs to be redeclared
1272 by everything that links against the rest of Tor. Done as part of
1273 ticket 23845, to simplify our external API.
1274 - We make extend_info_from_node() use node_get_curve25519_onion_key()
1275 introduced in ticket 23577 to access the curve25519 public keys
1276 rather than accessing it directly. Closes ticket 23760. Patch by
1278 - Add a function to log channels' scheduler state changes to aid
1279 debugging efforts. Closes ticket 24531.
1282 - Add documentation on how to build tor with Rust dependencies
1283 without having to be online. Closes ticket 22907; bugfix
1285 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
1286 traffic. Closes ticket 24318.
1287 - Document that OutboundBindAddress doesn't apply to DNS requests.
1288 Closes ticket 22145. Patch from Aruna Maurya.
1289 - Document that operators who run more than one relay or bridge are
1290 expected to set MyFamily and ContactInfo correctly. Closes
1293 o Code simplification and refactoring (channels):
1294 - Remove the incoming and outgoing channel queues. These were never
1295 used, but still took up a step in our fast path.
1296 - The majority of the channel unit tests have been rewritten and the
1297 code coverage has now been raised to 83.6% for channel.c. Closes
1299 - Remove other dead code from the channel subsystem: All together,
1300 this cleanup has removed more than 1500 lines of code overall and
1301 adding very little except for unit test.
1303 o Code simplification and refactoring (circuit rendezvous):
1304 - Split the client-size rendezvous circuit lookup into two
1305 functions: one that returns only established circuits and another
1306 that returns all kinds of circuits. Closes ticket 23459.
1308 o Code simplification and refactoring (controller):
1309 - Make most of the variables in networkstatus_getinfo_by_purpose()
1310 const. Implements ticket 24489.
1313 Changes in version 0.3.2.9 - 2018-01-09
1314 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
1316 The 0.3.2 series includes our long-anticipated new onion service
1317 design, with numerous security features. (For more information, see
1318 our blog post at https://blog.torproject.org/fall-harvest.) We also
1319 have a new circuit scheduler algorithm for improved performance on
1320 relays everywhere (see https://blog.torproject.org/kist-and-tell),
1321 along with many smaller features and bugfixes.
1323 Per our stable release policy, we plan to support each stable release
1324 series for at least the next nine months, or for three months after
1325 the first stable release of the next series: whichever is longer. If
1326 you need a release with long-term support, we recommend that you stay
1327 with the 0.2.9 series.
1329 Below is a list of the changes since 0.3.2.8-rc. For a list of all
1330 changes since 0.3.1, see the ReleaseNotes file.
1332 o Minor features (fallback directory mirrors):
1333 - The fallback directory list has been re-generated based on the
1334 current status of the network. Tor uses fallback directories to
1335 bootstrap when it doesn't yet have up-to-date directory
1336 information. Closes ticket 24801.
1337 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1338 prefer to bootstrap from fallback directory mirrors. This is a
1339 follow-up to 24679, which removed weights from the default
1340 fallbacks. Implements ticket 24681.
1342 o Minor features (geoip):
1343 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
1346 o Minor bugfixes (address selection):
1347 - When the fascist_firewall_choose_address_ functions don't find a
1348 reachable address, set the returned address to the null address
1349 and port. This is a precautionary measure, because some callers do
1350 not check the return value. Fixes bug 24736; bugfix
1353 o Minor bugfixes (compilation):
1354 - Resolve a few shadowed-variable warnings in the onion service
1355 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
1357 o Minor bugfixes (portability, msvc):
1358 - Fix a bug in the bit-counting parts of our timing-wheel code on
1359 MSVC. (Note that MSVC is still not a supported build platform, due
1360 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1364 Changes in version 0.3.2.8-rc - 2017-12-21
1365 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
1366 schedulers that had led servers under heavy load to overload their
1367 outgoing connections. All relay operators running earlier 0.3.2.x
1368 versions should upgrade. This version also includes a mitigation for
1369 over-full DESTROY queues leading to out-of-memory conditions: if it
1370 works, we will soon backport it to earlier release series.
1372 This is the second release candidate in the 0.3.2 series. If we find
1373 no new bugs or regression here, then the first stable 0.3.2 release
1374 will be nearly identical to this.
1376 o Major bugfixes (KIST, scheduler):
1377 - The KIST scheduler did not correctly account for data already
1378 enqueued in each connection's send socket buffer, particularly in
1379 cases when the TCP/IP congestion window was reduced between
1380 scheduler calls. This situation lead to excessive per-connection
1381 buffering in the kernel, and a potential memory DoS. Fixes bug
1382 24665; bugfix on 0.3.2.1-alpha.
1384 o Minor features (geoip):
1385 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
1388 o Minor bugfixes (hidden service v3):
1389 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
1390 the probability of reaching a service for a client missing
1391 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
1393 o Minor bugfixes (memory usage):
1394 - When queuing DESTROY cells on a channel, only queue the circuit-id
1395 and reason fields: not the entire 514-byte cell. This fix should
1396 help mitigate any bugs or attacks that fill up these queues, and
1397 free more RAM for other uses. Fixes bug 24666; bugfix
1400 o Minor bugfixes (scheduler, KIST):
1401 - Use a sane write limit for KISTLite when writing onto a connection
1402 buffer instead of using INT_MAX and shoving as much as it can.
1403 Because the OOM handler cleans up circuit queues, we are better
1404 off at keeping them in that queue instead of the connection's
1405 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
1408 Changes in version 0.3.2.7-rc - 2017-12-14
1409 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
1410 including some that could affect reliability or correctness.
1412 This is the first release candidate in the 0.3.2 series. If we find no
1413 new bugs or regression here, then the first stable 0.3.2. release will
1414 be nearly identical to this.
1416 o Major bugfixes (circuit prediction):
1417 - Fix circuit prediction logic so that a client doesn't treat a port
1418 as being "handled" by a circuit if that circuit already has
1419 isolation settings on it. This change should make Tor clients more
1420 responsive by improving their chances of having a pre-created
1421 circuit ready for use when a request arrives. Fixes bug 18859;
1422 bugfix on 0.2.3.3-alpha.
1424 o Minor features (logging):
1425 - Provide better warnings when the getrandom() syscall fails. Closes
1428 o Minor features (portability):
1429 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
1430 (It doesn't yet work with the sandbox enabled.) Closes
1433 o Minor bugfixes (bridge clients, bootstrap):
1434 - Retry directory downloads when we get our first bridge descriptor
1435 during bootstrap or while reconnecting to the network. Keep
1436 retrying every time we get a bridge descriptor, until we have a
1437 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
1438 - Stop delaying bridge descriptor fetches when we have cached bridge
1439 descriptors. Instead, only delay bridge descriptor fetches when we
1440 have at least one reachable bridge. Fixes part of bug 24367;
1441 bugfix on 0.2.0.3-alpha.
1442 - Stop delaying directory fetches when we have cached bridge
1443 descriptors. Instead, only delay bridge descriptor fetches when
1444 all our bridges are definitely unreachable. Fixes part of bug
1445 24367; bugfix on 0.2.0.3-alpha.
1447 o Minor bugfixes (compilation):
1448 - Fix a signed/unsigned comparison warning introduced by our fix to
1449 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1451 o Minor bugfixes (correctness):
1452 - Fix several places in our codebase where a C compiler would be
1453 likely to eliminate a check, based on assuming that undefined
1454 behavior had not happened elsewhere in the code. These cases are
1455 usually a sign of redundant checking or dubious arithmetic. Found
1456 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
1457 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
1460 o Minor bugfixes (onion service v3):
1461 - Fix a race where an onion service would launch a new intro circuit
1462 after closing an old one, but fail to register it before freeing
1463 the previously closed circuit. This bug was making the service
1464 unable to find the established intro circuit and thus not upload
1465 its descriptor, thus making a service unavailable for up to 24
1466 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
1468 o Minor bugfixes (scheduler, KIST):
1469 - Properly set the scheduler state of an unopened channel in the
1470 KIST scheduler main loop. This prevents a harmless but annoying
1471 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
1472 - Avoid a possible integer overflow when computing the available
1473 space on the TCP buffer of a channel. This had no security
1474 implications; but could make KIST allow too many cells on a
1475 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
1476 - Downgrade to "info" a harmless warning about the monotonic time
1477 moving backwards: This can happen on platform not supporting
1478 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
1481 Changes in version 0.3.2.6-alpha - 2017-12-01
1482 This version of Tor is the latest in the 0.3.2 alpha series. It
1483 includes fixes for several important security issues. All Tor users
1484 should upgrade to this release, or to one of the other releases coming
1487 o Major bugfixes (security):
1488 - Fix a denial of service bug where an attacker could use a
1489 malformed directory object to cause a Tor instance to pause while
1490 OpenSSL would try to read a passphrase from the terminal. (Tor
1491 instances run without a terminal, which is the case for most Tor
1492 packages, are not impacted.) Fixes bug 24246; bugfix on every
1493 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1494 Found by OSS-Fuzz as testcase 6360145429790720.
1495 - Fix a denial of service issue where an attacker could crash a
1496 directory authority using a malformed router descriptor. Fixes bug
1497 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1499 - When checking for replays in the INTRODUCE1 cell data for a
1500 (legacy) onion service, correctly detect replays in the RSA-
1501 encrypted part of the cell. We were previously checking for
1502 replays on the entire cell, but those can be circumvented due to
1503 the malleability of Tor's legacy hybrid encryption. This fix helps
1504 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1505 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1508 o Major bugfixes (security, onion service v2):
1509 - Fix a use-after-free error that could crash v2 Tor onion services
1510 when they failed to open circuits while expiring introduction
1511 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1512 also tracked as TROVE-2017-013 and CVE-2017-8823.
1514 o Major bugfixes (security, relay):
1515 - When running as a relay, make sure that we never build a path
1516 through ourselves, even in the case where we have somehow lost the
1517 version of our descriptor appearing in the consensus. Fixes part
1518 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1519 as TROVE-2017-012 and CVE-2017-8822.
1520 - When running as a relay, make sure that we never choose ourselves
1521 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1522 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1524 o Minor feature (relay statistics):
1525 - Change relay bandwidth reporting stats interval from 4 hours to 24
1526 hours in order to reduce the efficiency of guard discovery
1527 attacks. Fixes ticket 23856.
1529 o Minor features (directory authority):
1530 - Add an IPv6 address for the "bastet" directory authority. Closes
1533 o Minor bugfixes (client):
1534 - By default, do not enable storage of client-side DNS values. These
1535 values were unused by default previously, but they should not have
1536 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
1539 Changes in version 0.3.1.9 - 2017-12-01:
1540 Tor 0.3.1.9 backports important security and stability fixes from the
1541 0.3.2 development series. All Tor users should upgrade to this
1542 release, or to another of the releases coming out today.
1544 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1545 - Fix a denial of service bug where an attacker could use a
1546 malformed directory object to cause a Tor instance to pause while
1547 OpenSSL would try to read a passphrase from the terminal. (Tor
1548 instances run without a terminal, which is the case for most Tor
1549 packages, are not impacted.) Fixes bug 24246; bugfix on every
1550 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1551 Found by OSS-Fuzz as testcase 6360145429790720.
1552 - Fix a denial of service issue where an attacker could crash a
1553 directory authority using a malformed router descriptor. Fixes bug
1554 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1556 - When checking for replays in the INTRODUCE1 cell data for a
1557 (legacy) onion service, correctly detect replays in the RSA-
1558 encrypted part of the cell. We were previously checking for
1559 replays on the entire cell, but those can be circumvented due to
1560 the malleability of Tor's legacy hybrid encryption. This fix helps
1561 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1562 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1565 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1566 - Fix a use-after-free error that could crash v2 Tor onion services
1567 when they failed to open circuits while expiring introduction
1568 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1569 also tracked as TROVE-2017-013 and CVE-2017-8823.
1571 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1572 - When running as a relay, make sure that we never build a path
1573 through ourselves, even in the case where we have somehow lost the
1574 version of our descriptor appearing in the consensus. Fixes part
1575 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1576 as TROVE-2017-012 and CVE-2017-8822.
1577 - When running as a relay, make sure that we never choose ourselves
1578 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1579 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1581 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1582 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1583 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1584 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1585 identifying and finding a workaround to this bug and to Moritz,
1586 Arthur Edelstein, and Roger for helping to track it down and
1589 o Minor features (bridge):
1590 - Bridges now include notice in their descriptors that they are
1591 bridges, and notice of their distribution status, based on their
1592 publication settings. Implements ticket 18329. For more fine-
1593 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1596 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1597 - Add an IPv6 address for the "bastet" directory authority. Closes
1600 o Minor features (geoip):
1601 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1604 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1605 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1606 relays, to prevent spurious address resolutions and descriptor
1607 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1608 bugfix on in 0.2.8.1-alpha.
1610 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1611 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1612 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1614 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1615 - When a circuit is marked for close, do not attempt to package any
1616 cells for channels on that circuit. Previously, we would detect
1617 this condition lower in the call stack, when we noticed that the
1618 circuit had no attached channel, and log an annoying message.
1619 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1621 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
1622 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1623 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1626 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1627 - Avoid a crash when transitioning from client mode to bridge mode.
1628 Previously, we would launch the worker threads whenever our
1629 "public server" mode changed, but not when our "server" mode
1630 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1633 Changes in version 0.3.0.13 - 2017-12-01
1634 Tor 0.3.0.13 backports important security and stability bugfixes from
1635 later Tor releases. All Tor users should upgrade to this release, or
1636 to another of the releases coming out today.
1638 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1639 2018. If you need a release with long-term support, please stick with
1640 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1642 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1643 - Fix a denial of service bug where an attacker could use a
1644 malformed directory object to cause a Tor instance to pause while
1645 OpenSSL would try to read a passphrase from the terminal. (Tor
1646 instances run without a terminal, which is the case for most Tor
1647 packages, are not impacted.) Fixes bug 24246; bugfix on every
1648 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1649 Found by OSS-Fuzz as testcase 6360145429790720.
1650 - Fix a denial of service issue where an attacker could crash a
1651 directory authority using a malformed router descriptor. Fixes bug
1652 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1654 - When checking for replays in the INTRODUCE1 cell data for a
1655 (legacy) onion service, correctly detect replays in the RSA-
1656 encrypted part of the cell. We were previously checking for
1657 replays on the entire cell, but those can be circumvented due to
1658 the malleability of Tor's legacy hybrid encryption. This fix helps
1659 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1660 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1663 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1664 - Fix a use-after-free error that could crash v2 Tor onion services
1665 when they failed to open circuits while expiring introduction
1666 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1667 also tracked as TROVE-2017-013 and CVE-2017-8823.
1669 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1670 - When running as a relay, make sure that we never build a path
1671 through ourselves, even in the case where we have somehow lost the
1672 version of our descriptor appearing in the consensus. Fixes part
1673 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1674 as TROVE-2017-012 and CVE-2017-8822.
1675 - When running as a relay, make sure that we never choose ourselves
1676 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1677 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1679 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1680 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1681 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1682 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1683 identifying and finding a workaround to this bug and to Moritz,
1684 Arthur Edelstein, and Roger for helping to track it down and
1687 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1688 - Enable a couple of pieces of Windows hardening: one
1689 (HeapEnableTerminationOnCorruption) that has been on-by-default
1690 since Windows 8, and unavailable before Windows 7; and one
1691 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1692 affect us, but shouldn't do any harm. Closes ticket 21953.
1694 o Minor features (bridge, backport from 0.3.1.9):
1695 - Bridges now include notice in their descriptors that they are
1696 bridges, and notice of their distribution status, based on their
1697 publication settings. Implements ticket 18329. For more fine-
1698 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1701 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1702 - Add an IPv6 address for the "bastet" directory authority. Closes
1705 o Minor features (geoip):
1706 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1709 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1710 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1711 relays, to prevent spurious address resolutions and descriptor
1712 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1713 bugfix on in 0.2.8.1-alpha.
1715 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1716 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1717 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1719 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1720 - When a circuit is marked for close, do not attempt to package any
1721 cells for channels on that circuit. Previously, we would detect
1722 this condition lower in the call stack, when we noticed that the
1723 circuit had no attached channel, and log an annoying message.
1724 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1726 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1727 - Avoid a crash when transitioning from client mode to bridge mode.
1728 Previously, we would launch the worker threads whenever our
1729 "public server" mode changed, but not when our "server" mode
1730 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1732 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1733 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1734 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1737 Changes in version 0.2.9.14 - 2017-12-01
1738 Tor 0.3.0.13 backports important security and stability bugfixes from
1739 later Tor releases. All Tor users should upgrade to this release, or
1740 to another of the releases coming out today.
1742 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1743 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1744 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1745 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1746 identifying and finding a workaround to this bug and to Moritz,
1747 Arthur Edelstein, and Roger for helping to track it down and
1750 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1751 - Fix a denial of service bug where an attacker could use a
1752 malformed directory object to cause a Tor instance to pause while
1753 OpenSSL would try to read a passphrase from the terminal. (Tor
1754 instances run without a terminal, which is the case for most Tor
1755 packages, are not impacted.) Fixes bug 24246; bugfix on every
1756 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1757 Found by OSS-Fuzz as testcase 6360145429790720.
1758 - Fix a denial of service issue where an attacker could crash a
1759 directory authority using a malformed router descriptor. Fixes bug
1760 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1762 - When checking for replays in the INTRODUCE1 cell data for a
1763 (legacy) onion service, correctly detect replays in the RSA-
1764 encrypted part of the cell. We were previously checking for
1765 replays on the entire cell, but those can be circumvented due to
1766 the malleability of Tor's legacy hybrid encryption. This fix helps
1767 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1768 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1771 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1772 - Fix a use-after-free error that could crash v2 Tor onion services
1773 when they failed to open circuits while expiring introduction
1774 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1775 also tracked as TROVE-2017-013 and CVE-2017-8823.
1777 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1778 - When running as a relay, make sure that we never build a path
1779 through ourselves, even in the case where we have somehow lost the
1780 version of our descriptor appearing in the consensus. Fixes part
1781 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1782 as TROVE-2017-012 and CVE-2017-8822.
1784 o Minor features (bridge, backport from 0.3.1.9):
1785 - Bridges now include notice in their descriptors that they are
1786 bridges, and notice of their distribution status, based on their
1787 publication settings. Implements ticket 18329. For more fine-
1788 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1791 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1792 - Add an IPv6 address for the "bastet" directory authority. Closes
1795 o Minor features (geoip):
1796 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1799 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1800 - Enable a couple of pieces of Windows hardening: one
1801 (HeapEnableTerminationOnCorruption) that has been on-by-default
1802 since Windows 8, and unavailable before Windows 7; and one
1803 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1804 affect us, but shouldn't do any harm. Closes ticket 21953.
1806 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1807 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1808 relays, to prevent spurious address resolutions and descriptor
1809 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1810 bugfix on in 0.2.8.1-alpha.
1812 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1813 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1814 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1816 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1817 - When a circuit is marked for close, do not attempt to package any
1818 cells for channels on that circuit. Previously, we would detect
1819 this condition lower in the call stack, when we noticed that the
1820 circuit had no attached channel, and log an annoying message.
1821 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1823 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1824 - Avoid a crash when transitioning from client mode to bridge mode.
1825 Previously, we would launch the worker threads whenever our
1826 "public server" mode changed, but not when our "server" mode
1827 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1829 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1830 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1831 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1834 Changes in version 0.2.8.17 - 2017-12-01
1835 Tor 0.2.8.17 backports important security and stability bugfixes from
1836 later Tor releases. All Tor users should upgrade to this release, or
1837 to another of the releases coming out today.
1839 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1840 2018. If you need a release with long-term support, please upgrade with
1841 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1843 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1844 - Fix a denial of service bug where an attacker could use a
1845 malformed directory object to cause a Tor instance to pause while
1846 OpenSSL would try to read a passphrase from the terminal. (Tor
1847 instances run without a terminal, which is the case for most Tor
1848 packages, are not impacted.) Fixes bug 24246; bugfix on every
1849 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1850 Found by OSS-Fuzz as testcase 6360145429790720.
1851 - When checking for replays in the INTRODUCE1 cell data for a
1852 (legacy) onion service, correctly detect replays in the RSA-
1853 encrypted part of the cell. We were previously checking for
1854 replays on the entire cell, but those can be circumvented due to
1855 the malleability of Tor's legacy hybrid encryption. This fix helps
1856 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1857 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1860 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1861 - Fix a use-after-free error that could crash v2 Tor onion services
1862 when they failed to open circuits while expiring introduction
1863 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1864 also tracked as TROVE-2017-013 and CVE-2017-8823.
1866 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1867 - When running as a relay, make sure that we never build a path through
1868 ourselves, even in the case where we have somehow lost the version of
1869 our descriptor appearing in the consensus. Fixes part of bug 21534;
1870 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
1873 o Minor features (bridge, backport from 0.3.1.9):
1874 - Bridges now include notice in their descriptors that they are
1875 bridges, and notice of their distribution status, based on their
1876 publication settings. Implements ticket 18329. For more fine-
1877 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1880 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1881 - Add an IPv6 address for the "bastet" directory authority. Closes
1884 o Minor features (geoip):
1885 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1888 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1889 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1890 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1893 Changes in version 0.2.5.16 - 2017-12-01
1894 Tor 0.2.5.13 backports important security and stability bugfixes from
1895 later Tor releases. All Tor users should upgrade to this release, or
1896 to another of the releases coming out today.
1898 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1899 2018. If you need a release with long-term support, please upgrade to
1900 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1902 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1903 - Fix a denial of service bug where an attacker could use a
1904 malformed directory object to cause a Tor instance to pause while
1905 OpenSSL would try to read a passphrase from the terminal. (Tor
1906 instances run without a terminal, which is the case for most Tor
1907 packages, are not impacted.) Fixes bug 24246; bugfix on every
1908 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1909 Found by OSS-Fuzz as testcase 6360145429790720.
1910 - When checking for replays in the INTRODUCE1 cell data for a
1911 (legacy) onion service, correctly detect replays in the RSA-
1912 encrypted part of the cell. We were previously checking for
1913 replays on the entire cell, but those can be circumvented due to
1914 the malleability of Tor's legacy hybrid encryption. This fix helps
1915 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1916 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1919 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1920 - When running as a relay, make sure that we never build a path
1921 through ourselves, even in the case where we have somehow lost the
1922 version of our descriptor appearing in the consensus. Fixes part
1923 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1924 as TROVE-2017-012 and CVE-2017-8822.
1926 o Minor features (bridge, backport from 0.3.1.9):
1927 - Bridges now include notice in their descriptors that they are
1928 bridges, and notice of their distribution status, based on their
1929 publication settings. Implements ticket 18329. For more fine-
1930 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1933 o Minor features (geoip):
1934 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1938 Changes in version 0.3.2.5-alpha - 2017-11-22
1939 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
1940 fixes several stability and reliability bugs, including a fix for
1941 intermittent bootstrapping failures that some people have been seeing
1942 since the 0.3.0.x series.
1944 Please test this alpha out -- many of these fixes will soon be
1945 backported to stable Tor versions if no additional bugs are found
1948 o Major bugfixes (bootstrapping):
1949 - Fetch descriptors aggressively whenever we lack enough to build
1950 circuits, regardless of how many descriptors we are missing.
1951 Previously, we would delay launching the fetch when we had fewer
1952 than 15 missing descriptors, even if some of those descriptors
1953 were blocking circuits from building. Fixes bug 23985; bugfix on
1954 0.1.1.11-alpha. The effects of this bug became worse in
1955 0.3.0.3-alpha, when we began treating missing descriptors from our
1956 primary guards as a reason to delay circuits.
1957 - Don't try fetching microdescriptors from relays that have failed
1958 to deliver them in the past. Fixes bug 23817; bugfix
1961 o Minor features (directory authority):
1962 - Make the "Exit" flag assignment only depend on whether the exit
1963 policy allows connections to ports 80 and 443. Previously relays
1964 would get the Exit flag if they allowed connections to one of
1965 these ports and also port 6667. Resolves ticket 23637.
1967 o Minor features (geoip):
1968 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1971 o Minor features (linux seccomp2 sandbox):
1972 - Update the sandbox rules so that they should now work correctly
1973 with Glibc 2.26. Closes ticket 24315.
1975 o Minor features (logging):
1976 - Downgrade a pair of log messages that could occur when an exit's
1977 resolver gave us an unusual (but not forbidden) response. Closes
1979 - Improve the message we log when re-enabling circuit build timeouts
1980 after having received a consensus. Closes ticket 20963.
1982 o Minor bugfixes (compilation):
1983 - Fix a memory leak warning in one of the libevent-related
1984 configuration tests that could occur when manually specifying
1985 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
1986 Found and patched by Alex Xu.
1987 - When detecting OpenSSL on Windows from our configure script, make
1988 sure to try linking with the ws2_32 library. Fixes bug 23783;
1989 bugfix on 0.3.2.2-alpha.
1991 o Minor bugfixes (control port, linux seccomp2 sandbox):
1992 - Avoid a crash when attempting to use the seccomp2 sandbox together
1993 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1996 o Minor bugfixes (control port, onion services):
1997 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
1998 HS_DESC event when a service is not able to upload a descriptor.
1999 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
2001 o Minor bugfixes (directory cache):
2002 - Recover better from empty or corrupt files in the consensus cache
2003 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2004 - When a consensus diff calculation is only partially successful,
2005 only record the successful parts as having succeeded. Partial
2006 success can happen if (for example) one compression method fails
2007 but the others succeed. Previously we misrecorded all the
2008 calculations as having succeeded, which would later cause a
2009 nonfatal assertion failure. Fixes bug 24086; bugfix
2012 o Minor bugfixes (logging):
2013 - Only log once if we notice that KIST support is gone. Fixes bug
2014 24158; bugfix on 0.3.2.1-alpha.
2015 - Suppress a log notice when relay descriptors arrive. We already
2016 have a bootstrap progress for this so no need to log notice
2017 everytime tor receives relay descriptors. Microdescriptors behave
2018 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
2020 o Minor bugfixes (network layer):
2021 - When closing a connection via close_connection_immediately(), we
2022 mark it as "not blocked on bandwidth", to prevent later calls from
2023 trying to unblock it, and give it permission to read. This fixes a
2024 backtrace warning that can happen on relays under various
2025 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2027 o Minor bugfixes (onion services):
2028 - The introduction circuit was being timed out too quickly while
2029 waiting for the rendezvous circuit to complete. Keep the intro
2030 circuit around longer instead of timing out and reopening new ones
2031 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
2032 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2033 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2035 - Silence a warning about failed v3 onion descriptor uploads that
2036 can happen naturally under certain edge cases. Fixes part of bug
2037 23662; bugfix on 0.3.2.1-alpha.
2039 o Minor bugfixes (tests):
2040 - Fix a memory leak in one of the bridge-distribution test cases.
2041 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
2042 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
2043 to correctly handle cases where a caller gives it an RSA key of
2044 under 160 bits. (This is not actually a bug in Tor itself, but
2045 rather in our fuzzing code.) Fixes bug 24247; bugfix on
2046 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
2049 - Add notes in man page regarding OS support for the various
2050 scheduler types. Attempt to use less jargon in the scheduler
2051 section. Closes ticket 24254.
2054 Changes in version 0.3.2.4-alpha - 2017-11-08
2055 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
2056 It fixes several stability and reliability bugs, especially including
2057 a major reliability issue that has been plaguing fast exit relays in
2060 o Major bugfixes (exit relays, DNS):
2061 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2062 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2063 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2064 identifying and finding a workaround to this bug and to Moritz,
2065 Arthur Edelstein, and Roger for helping to track it down and
2068 o Major bugfixes (scheduler, channel):
2069 - Stop processing scheduled channels if they closed while flushing
2070 cells. This can happen if the write on the connection fails
2071 leading to the channel being closed while in the scheduler loop.
2072 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
2074 o Minor features (logging, scheduler):
2075 - Introduce a SCHED_BUG() function to log extra information about
2076 the scheduler state if we ever catch a bug in the scheduler.
2077 Closes ticket 23753.
2079 o Minor features (removed deprecations):
2080 - The ClientDNSRejectInternalAddresses flag can once again be set in
2081 non-testing Tor networks, so long as they do not use the default
2082 directory authorities. This change also removes the deprecation of
2083 this flag from 0.2.9.2-alpha. Closes ticket 21031.
2085 o Minor features (testing):
2086 - Our fuzzing tests now test the encrypted portions of v3 onion
2087 service descriptors. Implements more of 21509.
2089 o Minor bugfixes (directory client):
2090 - On failure to download directory information, delay retry attempts
2091 by a random amount based on the "decorrelated jitter" algorithm.
2092 Our previous delay algorithm tended to produce extra-long delays
2093 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
2095 o Minor bugfixes (IPv6, v3 single onion services):
2096 - Remove buggy code for IPv6-only v3 single onion services, and
2097 reject attempts to configure them. This release supports IPv4,
2098 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
2099 stack v3 single onion services. Fixes bug 23820; bugfix
2102 o Minor bugfixes (logging, relay):
2103 - Give only a protocol warning when the ed25519 key is not
2104 consistent between the descriptor and microdescriptor of a relay.
2105 This can happen, for instance, if the relay has been flagged
2106 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
2108 o Minor bugfixes (manpage, onion service):
2109 - Document that the HiddenServiceNumIntroductionPoints option is
2110 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
2111 bugfix on 0.3.2.1-alpha.
2113 o Minor bugfixes (memory leaks):
2114 - Fix a minor memory leak at exit in the KIST scheduler. This bug
2115 should have no user-visible impact. Fixes bug 23774; bugfix
2117 - Fix a memory leak when decrypting a badly formatted v3 onion
2118 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
2119 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
2121 o Minor bugfixes (onion services):
2122 - Cache some needed onion service client information instead of
2123 constantly computing it over and over again. Fixes bug 23623;
2124 bugfix on 0.3.2.1-alpha.
2125 - Properly retry HSv3 descriptor fetches when missing required
2126 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
2128 o Minor bugfixes (path selection):
2129 - When selecting relays by bandwidth, avoid a rounding error that
2130 could sometimes cause load to be imbalanced incorrectly.
2131 Previously, we would always round upwards; now, we round towards
2132 the nearest integer. This had the biggest effect when a relay's
2133 weight adjustments should have given it weight 0, but it got
2134 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2135 - When calculating the fraction of nodes that have descriptors, and
2136 all nodes in the network have zero bandwidths, count the number of
2137 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2138 - Actually log the total bandwidth in compute_weighted_bandwidths().
2139 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2141 o Minor bugfixes (relay, crash):
2142 - Avoid a crash when transitioning from client mode to bridge mode.
2143 Previously, we would launch the worker threads whenever our
2144 "public server" mode changed, but not when our "server" mode
2145 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2147 o Minor bugfixes (testing):
2148 - Fix a spurious fuzzing-only use of an uninitialized value. Found
2149 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
2150 - Test that IPv6-only clients can use microdescriptors when running
2151 "make test-network-all". Requires chutney master 61c28b9 or later.
2152 Closes ticket 24109.
2155 Changes in version 0.3.2.3-alpha - 2017-10-27
2156 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
2157 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
2158 directory authority, Bastet.
2160 o Directory authority changes:
2161 - Add "Bastet" as a ninth directory authority to the default list.
2162 Closes ticket 23910.
2163 - The directory authority "Longclaw" has changed its IP address.
2164 Closes ticket 23592.
2166 o Minor features (bridge):
2167 - Bridge relays can now set the BridgeDistribution config option to
2168 add a "bridge-distribution-request" line to their bridge
2169 descriptor, which tells BridgeDB how they'd like their bridge
2170 address to be given out. (Note that as of Oct 2017, BridgeDB does
2171 not yet implement this feature.) As a side benefit, this feature
2172 provides a way to distinguish bridge descriptors from non-bridge
2173 descriptors. Implements tickets 18329.
2175 o Minor features (client, entry guards):
2176 - Improve log messages when missing descriptors for primary guards.
2177 Resolves ticket 23670.
2179 o Minor features (geoip):
2180 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2183 o Minor bugfixes (bridge):
2184 - Overwrite the bridge address earlier in the process of retrieving
2185 its descriptor, to make sure we reach it on the configured
2186 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
2188 o Minor bugfixes (documentation):
2189 - Document better how to read gcov, and what our gcov postprocessing
2190 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
2192 o Minor bugfixes (entry guards):
2193 - Tor now updates its guard state when it reads a consensus
2194 regardless of whether it's missing descriptors. That makes tor use
2195 its primary guards to fetch descriptors in some edge cases where
2196 it would previously have used fallback directories. Fixes bug
2197 23862; bugfix on 0.3.0.1-alpha.
2199 o Minor bugfixes (hidden service client):
2200 - When handling multiple SOCKS request for the same .onion address,
2201 only fetch the service descriptor once.
2202 - When a descriptor fetch fails with a non-recoverable error, close
2203 all pending SOCKS requests for that .onion. Fixes bug 23653;
2204 bugfix on 0.3.2.1-alpha.
2206 o Minor bugfixes (hidden service):
2207 - Always regenerate missing hidden service public key files. Prior
2208 to this, if the public key was deleted from disk, it wouldn't get
2209 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
2211 - Make sure that we have a usable ed25519 key when the intro point
2212 relay supports ed25519 link authentication. Fixes bug 24002;
2213 bugfix on 0.3.2.1-alpha.
2215 o Minor bugfixes (hidden service, v2):
2216 - When reloading configured hidden services, copy all information
2217 from the old service object. Previously, some data was omitted,
2218 causing delays in descriptor upload, and other bugs. Fixes bug
2219 23790; bugfix on 0.2.1.9-alpha.
2221 o Minor bugfixes (memory safety, defensive programming):
2222 - Clear the target address when node_get_prim_orport() returns
2223 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2225 o Minor bugfixes (relay):
2226 - Avoid a BUG warning when receiving a dubious CREATE cell while an
2227 option transition is in progress. Fixes bug 23952; bugfix
2230 o Minor bugfixes (testing):
2231 - Adjust the GitLab CI configuration to more closely match that of
2232 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
2233 - Prevent scripts/test/coverage from attempting to move gcov output
2234 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
2235 - When running unit tests as root, skip a test that would fail
2236 because it expects a permissions error. This affects some
2237 continuous integration setups. Fixes bug 23758; bugfix
2239 - Stop unconditionally mirroring the tor repository in GitLab CI.
2240 This prevented developers from enabling GitLab CI on master. Fixes
2241 bug 23755; bugfix on 0.3.2.2-alpha.
2242 - Fix the hidden service v3 descriptor decoding fuzzing to use the
2243 latest decoding API correctly. Fixes bug 21509; bugfix
2246 o Minor bugfixes (warnings):
2247 - When we get an HTTP request on a SOCKS port, tell the user about
2248 the new HTTPTunnelPort option. Previously, we would give a "Tor is
2249 not an HTTP Proxy" message, which stopped being true when
2250 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
2254 Changes in version 0.2.5.15 - 2017-10-25
2255 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
2256 series. It also adds a new directory authority, Bastet.
2258 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2259 2018. If you need a release with long-term support, please upgrade to
2260 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2262 o Directory authority changes:
2263 - Add "Bastet" as a ninth directory authority to the default list.
2264 Closes ticket 23910.
2265 - The directory authority "Longclaw" has changed its IP address.
2266 Closes ticket 23592.
2268 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2269 - Avoid an assertion failure bug affecting our implementation of
2270 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2271 handling of "0xx" differs from what we had expected. Fixes bug
2272 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2274 o Minor features (geoip):
2275 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2278 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2279 - Fix a memset() off the end of an array when packing cells. This
2280 bug should be harmless in practice, since the corrupted bytes are
2281 still in the same structure, and are always padding bytes,
2282 ignored, or immediately overwritten, depending on compiler
2283 behavior. Nevertheless, because the memset()'s purpose is to make
2284 sure that any other cell-handling bugs can't expose bytes to the
2285 network, we need to fix it. Fixes bug 22737; bugfix on
2286 0.2.4.11-alpha. Fixes CID 1401591.
2288 o Build features (backport from 0.3.1.5-alpha):
2289 - Tor's repository now includes a Travis Continuous Integration (CI)
2290 configuration file (.travis.yml). This is meant to help new
2291 developers and contributors who fork Tor to a Github repository be
2292 better able to test their changes, and understand what we expect
2293 to pass. To use this new build feature, you must fork Tor to your
2294 Github account, then go into the "Integrations" menu in the
2295 repository settings for your fork and enable Travis, then push
2296 your changes. Closes ticket 22636.
2299 Changes in version 0.2.8.16 - 2017-10-25
2300 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
2301 series, including a bugfix for a crash issue that had affected relays
2302 under memory pressure. It also adds a new directory authority, Bastet.
2304 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2305 2018. If you need a release with long-term support, please stick with
2306 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2308 o Directory authority changes:
2309 - Add "Bastet" as a ninth directory authority to the default list.
2310 Closes ticket 23910.
2311 - The directory authority "Longclaw" has changed its IP address.
2312 Closes ticket 23592.
2314 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2315 - Fix a timing-based assertion failure that could occur when the
2316 circuit out-of-memory handler freed a connection's output buffer.
2317 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2319 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2320 - Remove longclaw's IPv6 address, as it will soon change. Authority
2321 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2322 3/8 directory authorities with IPv6 addresses, but there are also
2323 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2325 o Minor features (geoip):
2326 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2330 Changes in version 0.2.9.13 - 2017-10-25
2331 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
2332 series, including a bugfix for a crash issue that had affected relays
2333 under memory pressure. It also adds a new directory authority, Bastet.
2335 o Directory authority changes:
2336 - Add "Bastet" as a ninth directory authority to the default list.
2337 Closes ticket 23910.
2338 - The directory authority "Longclaw" has changed its IP address.
2339 Closes ticket 23592.
2341 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2342 - Fix a timing-based assertion failure that could occur when the
2343 circuit out-of-memory handler freed a connection's output buffer.
2344 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2346 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2347 - Remove longclaw's IPv6 address, as it will soon change. Authority
2348 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2349 3/8 directory authorities with IPv6 addresses, but there are also
2350 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2352 o Minor features (geoip):
2353 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2356 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2357 - When a directory authority rejects a descriptor or extrainfo with
2358 a given digest, mark that digest as undownloadable, so that we do
2359 not attempt to download it again over and over. We previously
2360 tried to avoid downloading such descriptors by other means, but we
2361 didn't notice if we accidentally downloaded one anyway. This
2362 behavior became problematic in 0.2.7.2-alpha, when authorities
2363 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2366 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2367 - Clear the address when node_get_prim_orport() returns early.
2368 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2370 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2371 - When running as a Windows service, set the ID of the main thread
2372 correctly. Failure to do so made us fail to send log messages to
2373 the controller in 0.2.1.16-rc, slowed down controller event
2374 delivery in 0.2.7.3-rc and later, and crash with an assertion
2375 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2376 Patch and diagnosis from "Vort".
2379 Changes in version 0.3.0.12 - 2017-10-25
2380 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
2381 series, including a bugfix for a crash issue that had affected relays
2382 under memory pressure. It also adds a new directory authority, Bastet.
2384 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2385 2018. If you need a release with long-term support, please stick with
2386 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2388 o Directory authority changes:
2389 - Add "Bastet" as a ninth directory authority to the default list.
2390 Closes ticket 23910.
2391 - The directory authority "Longclaw" has changed its IP address.
2392 Closes ticket 23592.
2394 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2395 - Fix a timing-based assertion failure that could occur when the
2396 circuit out-of-memory handler freed a connection's output buffer.
2397 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2399 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2400 - Remove longclaw's IPv6 address, as it will soon change. Authority
2401 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2402 3/8 directory authorities with IPv6 addresses, but there are also
2403 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2405 o Minor features (geoip):
2406 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2409 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2410 - When a directory authority rejects a descriptor or extrainfo with
2411 a given digest, mark that digest as undownloadable, so that we do
2412 not attempt to download it again over and over. We previously
2413 tried to avoid downloading such descriptors by other means, but we
2414 didn't notice if we accidentally downloaded one anyway. This
2415 behavior became problematic in 0.2.7.2-alpha, when authorities
2416 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2419 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2420 - Avoid a possible double close of a circuit by the intro point on
2421 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2422 bugfix on 0.3.0.1-alpha.
2424 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2425 - Clear the address when node_get_prim_orport() returns early.
2426 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2428 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2429 - When running as a Windows service, set the ID of the main thread
2430 correctly. Failure to do so made us fail to send log messages to
2431 the controller in 0.2.1.16-rc, slowed down controller event
2432 delivery in 0.2.7.3-rc and later, and crash with an assertion
2433 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2434 Patch and diagnosis from "Vort".
2437 Changes in version 0.3.1.8 - 2017-10-25
2438 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
2439 It includes several bugfixes, including a bugfix for a crash issue
2440 that had affected relays under memory pressure. It also adds
2441 a new directory authority, Bastet.
2443 o Directory authority changes:
2444 - Add "Bastet" as a ninth directory authority to the default list.
2445 Closes ticket 23910.
2446 - The directory authority "Longclaw" has changed its IP address.
2447 Closes ticket 23592.
2449 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2450 - Fix a timing-based assertion failure that could occur when the
2451 circuit out-of-memory handler freed a connection's output buffer.
2452 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2454 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2455 - Remove longclaw's IPv6 address, as it will soon change. Authority
2456 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2457 3/8 directory authorities with IPv6 addresses, but there are also
2458 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2460 o Minor features (geoip):
2461 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2464 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
2465 - Fix a compilation warning when building with zstd support on
2466 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2467 and fixed by Andreas Stieger.
2469 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
2470 - Handle a pathological case when decompressing Zstandard data when
2471 the output buffer size is zero. Fixes bug 23551; bugfix
2474 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
2475 - Remove the length limit on HTTP status lines that authorities can
2476 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
2478 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2479 - Avoid a possible double close of a circuit by the intro point on
2480 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2481 bugfix on 0.3.0.1-alpha.
2483 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2484 - Clear the address when node_get_prim_orport() returns early.
2485 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2487 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
2488 - Fix additional channelpadding unit test failures by using mocked
2489 time instead of actual time for all tests. Fixes bug 23608; bugfix
2493 Changes in version 0.3.2.2-alpha - 2017-09-29
2494 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
2495 release fixes several minor bugs in the new scheduler and next-
2496 generation onion services; both features were newly added in the 0.3.2
2497 series. Other fixes in this alpha include several fixes for non-fatal
2498 tracebacks which would appear in logs.
2500 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
2501 alpha does not contain any substantial new features. Minor features
2502 include better testing and logging.
2504 The following comprises the complete list of changes included
2505 in tor-0.3.2.2-alpha:
2507 o Major bugfixes (relay, crash, assertion failure):
2508 - Fix a timing-based assertion failure that could occur when the
2509 circuit out-of-memory handler freed a connection's output buffer.
2510 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2512 o Major bugfixes (scheduler):
2513 - If a channel is put into the scheduler's pending list, then it
2514 starts closing, and then if the scheduler runs before it finishes
2515 closing, the scheduler will get stuck trying to flush its cells
2516 while the lower layers refuse to cooperate. Fix that race
2517 condition by giving the scheduler an escape method. Fixes bug
2518 23676; bugfix on 0.3.2.1-alpha.
2520 o Minor features (build, compilation):
2521 - The "check-changes" feature is now part of the "make check" tests;
2522 we'll use it to try to prevent misformed changes files from
2523 accumulating. Closes ticket 23564.
2524 - Tor builds should now fail if there are any mismatches between the
2525 C type representing a configuration variable and the C type the
2526 data-driven parser uses to store a value there. Previously, we
2527 needed to check these by hand, which sometimes led to mistakes.
2528 Closes ticket 23643.
2530 o Minor features (directory authorities):
2531 - Remove longclaw's IPv6 address, as it will soon change. Authority
2532 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2533 3/8 directory authorities with IPv6 addresses, but there are also
2534 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2536 o Minor features (hidden service, circuit, logging):
2537 - Improve logging of many callsite in the circuit subsystem to print
2538 the circuit identifier(s).
2539 - Log when we cleanup an intro point from a service so we know when
2540 and for what reason it happened. Closes ticket 23604.
2542 o Minor features (logging):
2543 - Log more circuit information whenever we are about to try to
2544 package a relay cell on a circuit with a nonexistent n_chan.
2545 Attempt to diagnose ticket 8185.
2546 - Improve info-level log identification of particular circuits, to
2547 help with debugging. Closes ticket 23645.
2549 o Minor features (relay):
2550 - When choosing which circuits can be expired as unused, consider
2551 circuits from clients even if those clients used regular CREATE
2552 cells to make them; and do not consider circuits from relays even
2553 if they were made with CREATE_FAST. Part of ticket 22805.
2555 o Minor features (robustness):
2556 - Change several fatal assertions when flushing buffers into non-
2557 fatal assertions, to prevent any recurrence of 23690.
2559 o Minor features (spec conformance, bridge, diagnostic):
2560 - When handling the USERADDR command on an ExtOrPort, warn when the
2561 transports provides a USERADDR with no port. In a future version,
2562 USERADDR commands of this format may be rejected. Detects problems
2563 related to ticket 23080.
2565 o Minor features (testing):
2566 - Add a unit test to make sure that our own generated platform
2567 string will be accepted by directory authorities. Closes
2570 o Minor bugfixes (bootstrapping):
2571 - When warning about state file clock skew, report the correct
2572 direction for the detected skew. Fixes bug 23606; bugfix
2574 - Avoid an assertion failure when logging a state file clock skew
2575 very early in bootstrapping. Fixes bug 23607; bugfix
2578 o Minor bugfixes (build, compilation):
2579 - Fix a compilation warning when building with zstd support on
2580 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2581 and fixed by Andreas Stieger.
2582 - When searching for OpenSSL, don't accept any OpenSSL library that
2583 lacks TLSv1_1_method(): Tor doesn't build with those versions.
2584 Additionally, look in /usr/local/opt/openssl, if it's present.
2585 These changes together repair the default build on OSX systems
2586 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
2588 o Minor bugfixes (compression):
2589 - Handle a pathological case when decompressing Zstandard data when
2590 the output buffer size is zero. Fixes bug 23551; bugfix
2593 o Minor bugfixes (documentation):
2594 - Fix manpage to not refer to the obsolete (and misspelled)
2595 UseEntryGuardsAsDirectoryGuards parameter in the description of
2596 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
2598 o Minor bugfixes (hidden service v3):
2599 - Don't log an assertion failure when we can't find the right
2600 information to extend to an introduction point. In rare cases,
2601 this could happen, causing a warning, even though tor would
2602 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
2603 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
2604 much bigger so the rendezvous point can't distinguish which hidden
2605 service protocol is being used. Fixes bug 23420; bugfix
2608 o Minor bugfixes (hidden service, relay):
2609 - Avoid a possible double close of a circuit by the intro point on
2610 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2611 bugfix on 0.3.0.1-alpha.
2613 o Minor bugfixes (logging, relay shutdown, annoyance):
2614 - When a circuit is marked for close, do not attempt to package any
2615 cells for channels on that circuit. Previously, we would detect
2616 this condition lower in the call stack, when we noticed that the
2617 circuit had no attached channel, and log an annoying message.
2618 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2620 o Minor bugfixes (scheduler):
2621 - When switching schedulers due to a consensus change, we didn't
2622 give the new scheduler a chance to react to the consensus. Fix
2623 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
2624 - Make the KISTSchedRunInterval option a non negative value. With
2625 this, the way to disable KIST through the consensus is to set it
2626 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
2627 - Only notice log the selected scheduler when we switch scheduler
2628 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
2629 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
2630 by a different tv_usec data type. Fixes bug 23575; bugfix
2632 - Make a hard exit if tor is unable to pick a scheduler which can
2633 happen if the user specifies a scheduler type that is not
2634 supported and not other types in Schedulers. Fixes bug 23581;
2635 bugfix on 0.3.2.1-alpha.
2636 - Properly initialize the scheduler last run time counter so it is
2637 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
2639 o Minor bugfixes (testing):
2640 - Capture and detect several "Result does not fit" warnings in unit
2641 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
2643 - Fix additional channelpadding unit test failures by using mocked
2644 time instead of actual time for all tests. Fixes bug 23608; bugfix
2646 - The removal of some old scheduler options caused some tests to
2647 fail on BSD systems. Assume current behavior is correct and make
2648 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
2650 o Code simplification and refactoring:
2651 - Remove various ways of testing circuits and connections for
2652 "clientness"; instead, favor channel_is_client(). Part of
2655 o Deprecated features:
2656 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
2657 now deprecated; they do not apply to relays, and they have had no
2658 effect on clients since 0.2.8.x. Closes ticket 19704.
2661 - HiddenServiceVersion man page entry wasn't mentioning the now
2662 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
2663 - Clarify that the Address option is entirely about setting an
2664 advertised IPv4 address. Closes ticket 18891.
2665 - Clarify the manpage's use of the term "address" to clarify what
2666 kind of address is intended. Closes ticket 21405.
2667 - Document that onion service subdomains are allowed, and ignored.
2668 Closes ticket 18736.
2671 Changes in version 0.3.2.1-alpha - 2017-09-18
2672 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
2673 includes support for our next-generation ("v3") onion service
2674 protocol, and adds a new circuit scheduler for more responsive
2675 forwarding decisions from relays. There are also numerous other small
2676 features and bugfixes here.
2678 Below are the changes since Tor 0.3.1.7.
2680 o Major feature (scheduler, channel):
2681 - Tor now uses new schedulers to decide which circuits should
2682 deliver cells first, in order to improve congestion at relays. The
2683 first type is called "KIST" ("Kernel Informed Socket Transport"),
2684 and is only available on Linux-like systems: it uses feedback from
2685 the kernel to prevent the kernel's TCP buffers from growing too
2686 full. The second new scheduler type is called "KISTLite": it
2687 behaves the same as KIST, but runs on systems without kernel
2688 support for inspecting TCP implementation details. The old
2689 scheduler is still available, under the name "Vanilla". To change
2690 the default scheduler preference order, use the new "Schedulers"
2691 option. (The default preference order is "KIST,KISTLite,Vanilla".)
2693 Matt Traudt implemented KIST, based on research by Rob Jansen,
2694 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
2695 more information, see the design paper at
2696 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
2697 followup implementation paper at https://arxiv.org/abs/1709.01044.
2698 Closes ticket 12541.
2700 o Major features (next-generation onion services):
2701 - Tor now supports the next-generation onion services protocol for
2702 clients and services! As part of this release, the core of
2703 proposal 224 has been implemented and is available for
2704 experimentation and testing by our users. This newer version of
2705 onion services ("v3") features many improvements over the legacy
2708 a) Better crypto (replaced SHA1/DH/RSA1024
2709 with SHA3/ed25519/curve25519)
2711 b) Improved directory protocol, leaking much less information to
2714 c) Improved directory protocol, with smaller surface for
2717 d) Better onion address security against impersonation.
2719 e) More extensible introduction/rendezvous protocol.
2721 f) A cleaner and more modular codebase.
2723 You can identify a next-generation onion address by its length:
2724 they are 56 characters long, as in
2725 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
2727 In the future, we will release more options and features for v3
2728 onion services, but we first need a testing period, so that the
2729 current codebase matures and becomes more robust. Planned features
2730 include: offline keys, advanced client authorization, improved
2731 guard algorithms, and statistics. For full details, see
2734 Legacy ("v2") onion services will still work for the foreseeable
2735 future, and will remain the default until this new codebase gets
2736 tested and hardened. Service operators who want to experiment with
2737 the new system can use the 'HiddenServiceVersion 3' torrc
2738 directive along with the regular onion service configuration
2739 options. We will publish a blog post about this new feature
2742 o Major bugfixes (usability, control port):
2743 - Report trusted clock skew indications as bootstrap errors, so
2744 controllers can more easily alert users when their clocks are
2745 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
2747 o Minor features (bug detection):
2748 - Log a warning message with a stack trace for any attempt to call
2749 get_options() during option validation. This pattern has caused
2750 subtle bugs in the past. Closes ticket 22281.
2752 o Minor features (client):
2753 - You can now use Tor as a tunneled HTTP proxy: use the new
2754 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
2755 requests. Closes ticket 22407.
2756 - Add an extra check to make sure that we always use the newer guard
2757 selection code for picking our guards. Closes ticket 22779.
2758 - When downloading (micro)descriptors, don't split the list into
2759 multiple requests unless we want at least 32 descriptors.
2760 Previously, we split at 4, not 32, which led to significant
2761 overhead in HTTP request size and degradation in compression
2762 performance. Closes ticket 23220.
2764 o Minor features (command line):
2765 - Add a new commandline option, --key-expiration, which prints when
2766 the current signing key is going to expire. Implements ticket
2767 17639; patch by Isis Lovecruft.
2769 o Minor features (control port):
2770 - If an application tries to use the control port as an HTTP proxy,
2771 respond with a meaningful "This is the Tor control port" message,
2772 and log the event. Closes ticket 1667. Patch from Ravi
2774 - Provide better error message for GETINFO desc/(id|name) when not
2775 fetching router descriptors. Closes ticket 5847. Patch by
2777 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
2778 whether Tor will try to download router descriptors and
2779 microdescriptors respectively. Closes ticket 22684.
2780 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
2781 so controllers can tell whether the geoip databases are loaded.
2782 Closes ticket 23237.
2783 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
2784 events. Closes ticket 19254. Patch by "DonnchaC".
2786 o Minor features (development support):
2787 - Developers can now generate a call-graph for Tor using the
2788 "calltool" python program, which post-processes object dumps. It
2789 should work okay on many Linux and OSX platforms, and might work
2790 elsewhere too. To run it, install calltool from
2791 https://gitweb.torproject.org/user/nickm/calltool.git and run
2792 "make callgraph". Closes ticket 19307.
2794 o Minor features (ed25519):
2795 - Add validation function to checks for torsion components in
2796 ed25519 public keys, used by prop224 client-side code. Closes
2797 ticket 22006. Math help by Ian Goldberg.
2799 o Minor features (exit relay, DNS):
2800 - Improve the clarity and safety of the log message from evdns when
2801 receiving an apparently spoofed DNS reply. Closes ticket 3056.
2803 o Minor features (integration, hardening):
2804 - Add a new NoExec option to prevent Tor from running other
2805 programs. When this option is set to 1, Tor will never try to run
2806 another program, regardless of the settings of
2807 PortForwardingHelper, ClientTransportPlugin, or
2808 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
2809 without restarting Tor. Closes ticket 22976.
2811 o Minor features (logging):
2812 - Improve the warning message for specifying a relay by nickname.
2813 The previous message implied that nickname registration was still
2814 part of the Tor network design, which it isn't. Closes
2816 - If the sandbox filter fails to load, suggest to the user that
2817 their kernel might not support seccomp2. Closes ticket 23090.
2819 o Minor features (portability):
2820 - Check at configure time whether uint8_t is the same type as
2821 unsigned char. Lots of existing code already makes this
2822 assumption, and there could be strict aliasing issues if the
2823 assumption is violated. Closes ticket 22410.
2825 o Minor features (relay, configuration):
2826 - Reject attempts to use relative file paths when RunAsDaemon is
2827 set. Previously, Tor would accept these, but the directory-
2828 changing step of RunAsDaemon would give strange and/or confusing
2829 results. Closes ticket 22731.
2831 o Minor features (startup, safety):
2832 - When configured to write a PID file, Tor now exits if it is unable
2833 to do so. Previously, it would warn and continue. Closes
2836 o Minor features (static analysis):
2837 - The BUG() macro has been changed slightly so that Coverity no
2838 longer complains about dead code if the bug is impossible. Closes
2841 o Minor features (testing):
2842 - The default chutney network tests now include tests for the v3
2843 hidden service design. Make sure you have the latest version of
2844 chutney if you want to run these. Closes ticket 22437.
2845 - Add a unit test to verify that we can parse a hardcoded v2 hidden
2846 service descriptor. Closes ticket 15554.
2848 o Minor bugfixes (certificate handling):
2849 - Fix a time handling bug in Tor certificates set to expire after
2850 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
2851 Coverity as CID 1415728.
2853 o Minor bugfixes (client, usability):
2854 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
2855 SOCKS4a requests that contain IP address strings, even when
2856 SafeSocks in enabled, as this prevents user from connecting to
2857 known IP addresses without relying on DNS for resolving. SafeSocks
2858 still rejects SOCKS connections that connect to IP addresses when
2859 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
2860 bugfix on Tor 0.2.6.2-alpha.
2862 o Minor bugfixes (code correctness):
2863 - Call htons() in extend_cell_format() for encoding a 16-bit value.
2864 Previously we used ntohs(), which happens to behave the same on
2865 all the platforms we support, but which isn't really correct.
2866 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
2867 - For defense-in-depth, make the controller's write_escaped_data()
2868 function robust to extremely long inputs. Fixes bug 19281; bugfix
2869 on 0.1.1.1-alpha. Reported by Guido Vranken.
2871 o Minor bugfixes (compilation):
2872 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
2873 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2875 o Minor bugfixes (consensus expiry):
2876 - Check for adequate directory information correctly. Previously, Tor
2877 would reconsider whether it had sufficient directory information
2878 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
2880 o Minor bugfixes (directory protocol):
2881 - Directory servers now include a "Date:" http header for response
2882 codes other than 200. Clients starting with a skewed clock and a
2883 recent consensus were getting "304 Not modified" responses from
2884 directory authorities, so without the Date header, the client
2885 would never hear about a wrong clock. Fixes bug 23499; bugfix
2887 - Make clients wait for 6 seconds before trying to download a
2888 consensus from an authority. Fixes bug 17750; bugfix
2891 o Minor bugfixes (DoS-resistance):
2892 - If future code asks if there are any running bridges, without
2893 checking if bridges are enabled, log a BUG warning rather than
2894 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
2896 o Minor bugfixes (format strictness):
2897 - Restrict several data formats to decimal. Previously, the
2898 BuildTimeHistogram entries in the state file, the "bw=" entries in
2899 the bandwidth authority file, and the process IDs passed to the
2900 __OwningControllerProcess option could all be specified in hex or
2901 octal as well as in decimal. This was not an intentional feature.
2902 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
2905 o Minor bugfixes (heartbeat):
2906 - If we fail to write a heartbeat message, schedule a retry for the
2907 minimum heartbeat interval number of seconds in the future. Fixes
2908 bug 19476; bugfix on 0.2.3.1-alpha.
2910 o Minor bugfixes (linux seccomp2 sandbox, logging):
2911 - Fix some messages on unexpected errors from the seccomp2 library.
2912 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
2914 o Minor bugfixes (logging):
2915 - Remove duplicate log messages regarding opening non-local
2916 SocksPorts upon parsing config and opening listeners at startup.
2917 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
2918 - Use a more comprehensible log message when telling the user
2919 they've excluded every running exit node. Fixes bug 7890; bugfix
2921 - When logging the number of descriptors we intend to download per
2922 directory request, do not log a number higher than then the number
2923 of descriptors we're fetching in total. Fixes bug 19648; bugfix
2925 - When warning about a directory owned by the wrong user, log the
2926 actual name of the user owning the directory. Previously, we'd log
2927 the name of the process owner twice. Fixes bug 23487; bugfix
2929 - The tor specification says hop counts are 1-based, so fix two log
2930 messages that mistakenly logged 0-based hop counts. Fixes bug
2931 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
2932 Credit to Xiaofan Li for reporting this issue.
2934 o Minor bugfixes (portability):
2935 - Stop using the PATH_MAX variable, which is not defined on GNU
2936 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
2938 o Minor bugfixes (relay):
2939 - When uploading our descriptor for the first time after startup,
2940 report the reason for uploading as "Tor just started" rather than
2941 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
2942 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2943 relays, to prevent spurious address resolutions and descriptor
2944 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2945 bugfix on in 0.2.8.1-alpha.
2947 o Minor bugfixes (tests):
2948 - Fix a broken unit test for the OutboundAddress option: the parsing
2949 function was never returning an error on failure. Fixes bug 23366;
2950 bugfix on 0.3.0.3-alpha.
2951 - Fix a signed-integer overflow in the unit tests for
2952 dir/download_status_random_backoff, which was untriggered until we
2953 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
2955 o Minor bugfixes (usability, control port):
2956 - Stop making an unnecessary routerlist check in NETINFO clock skew
2957 detection; this was preventing clients from reporting NETINFO clock
2958 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
2960 o Code simplification and refactoring:
2961 - Extract the code for handling newly-open channels into a separate
2962 function from the general code to handle channel state
2963 transitions. This change simplifies our callgraph, reducing the
2964 size of the largest strongly connected component by roughly a
2965 factor of two. Closes ticket 22608.
2966 - Remove dead code for largely unused statistics on the number of
2967 times we've attempted various public key operations. Fixes bug
2968 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
2969 - Remove several now-obsolete functions for asking about old
2970 variants directory authority status. Closes ticket 22311; patch
2972 - Remove some of the code that once supported "Named" and "Unnamed"
2973 routers. Authorities no longer vote for these flags. Closes
2975 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
2976 and old hidden services, to indicate that they aren't suitable for
2977 new protocols or formats. Closes ticket 23026.
2978 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
2979 22521. Patch from Neel Chauhan.
2980 - Split the enormous circuit_send_next_onion_skin() function into
2981 multiple subfunctions. Closes ticket 22804.
2982 - Split the portions of the buffer.c module that handle particular
2983 protocols into separate modules. Part of ticket 23149.
2984 - Use our test macros more consistently, to produce more useful
2985 error messages when our unit tests fail. Add coccinelle patches to
2986 allow us to re-check for test macro uses. Closes ticket 22497.
2988 o Deprecated features:
2989 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
2990 only applies to direct unencrypted HTTP connections to your
2991 directory server, which your Tor probably isn't using. Closes
2995 - Clarify in the manual that "Sandbox 1" is only supported on Linux
2996 kernels. Closes ticket 22677.
2997 - Document all values of PublishServerDescriptor in the manpage.
2998 Closes ticket 15645.
2999 - Improve the documentation for the directory port part of the
3000 DirAuthority line. Closes ticket 20152.
3001 - Restore documentation for the authorities' "approved-routers"
3002 file. Closes ticket 21148.
3005 - The AllowDotExit option has been removed as unsafe. It has been
3006 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
3007 - The ClientDNSRejectInternalAddresses flag can no longer be set on
3008 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
3009 Closes ticket 21031.
3010 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
3011 nobody was using it any longer. Closes ticket 22377.
3014 Changes in version 0.2.8.15 - 2017-09-18
3015 Tor 0.2.8.15 backports a collection of bugfixes from later
3018 Most significantly, it includes a fix for TROVE-2017-008, a
3019 security bug that affects hidden services running with the
3020 SafeLogging option disabled. For more information, see
3021 https://trac.torproject.org/projects/tor/ticket/23490
3023 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
3024 2018. We suggest that you upgrade to the latest stable release if
3025 possible. If you can't, we recommend that you upgrade at least to
3026 0.2.9, which will be supported until 2020.
3028 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3029 - Avoid an assertion failure bug affecting our implementation of
3030 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3031 handling of "0xx" differs from what we had expected. Fixes bug
3032 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3035 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3038 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3039 - Backport a fix for an "unused variable" warning that appeared
3040 in some versions of mingw. Fixes bug 22838; bugfix on
3043 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3044 - Fix a memset() off the end of an array when packing cells. This
3045 bug should be harmless in practice, since the corrupted bytes are
3046 still in the same structure, and are always padding bytes,
3047 ignored, or immediately overwritten, depending on compiler
3048 behavior. Nevertheless, because the memset()'s purpose is to make
3049 sure that any other cell-handling bugs can't expose bytes to the
3050 network, we need to fix it. Fixes bug 22737; bugfix on
3051 0.2.4.11-alpha. Fixes CID 1401591.
3053 o Build features (backport from 0.3.1.5-alpha):
3054 - Tor's repository now includes a Travis Continuous Integration (CI)
3055 configuration file (.travis.yml). This is meant to help new
3056 developers and contributors who fork Tor to a Github repository be
3057 better able to test their changes, and understand what we expect
3058 to pass. To use this new build feature, you must fork Tor to your
3059 Github account, then go into the "Integrations" menu in the
3060 repository settings for your fork and enable Travis, then push
3061 your changes. Closes ticket 22636.
3064 Changes in version 0.2.9.12 - 2017-09-18
3065 Tor 0.2.9.12 backports a collection of bugfixes from later
3068 Most significantly, it includes a fix for TROVE-2017-008, a
3069 security bug that affects hidden services running with the
3070 SafeLogging option disabled. For more information, see
3071 https://trac.torproject.org/projects/tor/ticket/23490
3073 o Major features (security, backport from 0.3.0.2-alpha):
3074 - Change the algorithm used to decide DNS TTLs on client and server
3075 side, to better resist DNS-based correlation attacks like the
3076 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3077 Feamster. Now relays only return one of two possible DNS TTL
3078 values, and clients are willing to believe DNS TTL values up to 3
3079 hours long. Closes ticket 19769.
3081 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
3082 - Fix a rare crash when sending a begin cell on a circuit whose
3083 linked directory connection had already been closed. Fixes bug
3084 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3086 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
3087 - Fix a bug that prevented exit nodes from caching DNS records for
3088 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3090 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3091 - Fix a typo that had prevented TPROXY-based transparent proxying
3092 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3093 Patch from "d4fq0fQAgoJ".
3095 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3096 - Avoid an assertion failure bug affecting our implementation of
3097 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3098 handling of "0xx" differs from what we had expected. Fixes bug
3099 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3101 o Minor features (code style, backport from 0.3.1.3-alpha):
3102 - Add "Falls through" comments to our codebase, in order to silence
3103 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3104 Stieger. Closes ticket 22446.
3106 o Minor features (geoip):
3107 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3110 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
3111 - Roll over monthly accounting at the configured hour and minute,
3112 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3113 Found by Andrey Karpov with PVS-Studio.
3115 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
3116 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3117 bugfix on 0.2.8.1-alpha.
3118 - Fix warnings when building with libscrypt and openssl scrypt support
3119 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3120 - When building with certain versions the mingw C header files, avoid
3121 float-conversion warnings when calling the C functions isfinite(),
3122 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
3124 o Minor bugfixes (compilation, backport from 0.3.1.7):
3125 - Avoid compiler warnings in the unit tests for running tor_sscanf()
3126 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3128 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3129 - Backport a fix for an "unused variable" warning that appeared
3130 in some versions of mingw. Fixes bug 22838; bugfix on
3133 o Minor bugfixes (controller, backport from 0.3.1.7):
3134 - Do not crash when receiving a HSPOST command with an empty body.
3135 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3136 - Do not crash when receiving a POSTDESCRIPTOR command with an
3137 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3139 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3140 - Avoid Coverity build warnings related to our BUG() macro. By
3141 default, Coverity treats BUG() as the Linux kernel does: an
3142 instant abort(). We need to override that so our BUG() macro
3143 doesn't prevent Coverity from analyzing functions that use it.
3144 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3146 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3147 - Fix a memset() off the end of an array when packing cells. This
3148 bug should be harmless in practice, since the corrupted bytes are
3149 still in the same structure, and are always padding bytes,
3150 ignored, or immediately overwritten, depending on compiler
3151 behavior. Nevertheless, because the memset()'s purpose is to make
3152 sure that any other cell-handling bugs can't expose bytes to the
3153 network, we need to fix it. Fixes bug 22737; bugfix on
3154 0.2.4.11-alpha. Fixes CID 1401591.
3156 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3157 - When setting the maximum number of connections allowed by the OS,
3158 always allow some extra file descriptors for other files. Fixes
3159 bug 22797; bugfix on 0.2.0.10-alpha.
3161 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3162 - Avoid a sandbox failure when trying to re-bind to a socket and
3163 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3165 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3166 - Permit the fchmod system call, to avoid crashing on startup when
3167 starting with the seccomp2 sandbox and an unexpected set of
3168 permissions on the data directory or its contents. Fixes bug
3169 22516; bugfix on 0.2.5.4-alpha.
3171 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
3172 - Avoid a double-marked-circuit warning that could happen when we
3173 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3176 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3177 - Reject version numbers with non-numeric prefixes (such as +, -, or
3178 whitespace). Disallowing whitespace prevents differential version
3179 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3180 and part of 21508; bugfix on 0.0.8pre1.
3182 o Build features (backport from 0.3.1.5-alpha):
3183 - Tor's repository now includes a Travis Continuous Integration (CI)
3184 configuration file (.travis.yml). This is meant to help new
3185 developers and contributors who fork Tor to a Github repository be
3186 better able to test their changes, and understand what we expect
3187 to pass. To use this new build feature, you must fork Tor to your
3188 Github account, then go into the "Integrations" menu in the
3189 repository settings for your fork and enable Travis, then push
3190 your changes. Closes ticket 22636.
3193 Changes in version 0.3.0.11 - 2017-09-18
3194 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
3197 Most significantly, it includes a fix for TROVE-2017-008, a
3198 security bug that affects hidden services running with the
3199 SafeLogging option disabled. For more information, see
3200 https://trac.torproject.org/projects/tor/ticket/23490
3202 o Minor features (code style, backport from 0.3.1.7):
3203 - Add "Falls through" comments to our codebase, in order to silence
3204 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3205 Stieger. Closes ticket 22446.
3208 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3211 o Minor bugfixes (compilation, backport from 0.3.1.7):
3212 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3213 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3215 o Minor bugfixes (controller, backport from 0.3.1.7):
3216 - Do not crash when receiving a HSPOST command with an empty body.
3217 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3218 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3219 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3221 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3222 - When setting the maximum number of connections allowed by the OS,
3223 always allow some extra file descriptors for other files. Fixes
3224 bug 22797; bugfix on 0.2.0.10-alpha.
3226 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
3227 - Remove a forgotten debugging message when an introduction point
3228 successfully establishes a hidden service prop224 circuit with
3230 - Change three other log_warn() for an introduction point to
3231 protocol warnings, because they can be failure from the network
3232 and are not relevant to the operator. Fixes bug 23078; bugfix on
3233 0.3.0.1-alpha and 0.3.0.2-alpha.
3236 Changes in version 0.3.1.7 - 2017-09-18
3237 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
3239 With the 0.3.1 series, Tor now serves and downloads directory
3240 information in more compact formats, to save on bandwidth overhead. It
3241 also contains a new padding system to resist netflow-based traffic
3242 analysis, and experimental support for building parts of Tor in Rust
3243 (though no parts of Tor are in Rust yet). There are also numerous
3244 small features, bugfixes on earlier release series, and groundwork for
3245 the hidden services revamp of 0.3.2.
3247 This release also includes a fix for TROVE-2017-008, a security bug
3248 that affects hidden services running with the SafeLogging option
3249 disabled. For more information, see
3250 https://trac.torproject.org/projects/tor/ticket/23490
3252 Per our stable release policy, we plan to support each stable release
3253 series for at least the next nine months, or for three months after
3254 the first stable release of the next series: whichever is longer. If
3255 you need a release with long-term support, we recommend that you stay
3256 with the 0.2.9 series.
3258 Below is a list of the changes since 0.3.1.6-rc. For a list of all
3259 changes since 0.3.0, see the ReleaseNotes file.
3261 o Major bugfixes (security, hidden services, loggging):
3262 - Fix a bug where we could log uninitialized stack when a certain
3263 hidden service error occurred while SafeLogging was disabled.
3264 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
3265 TROVE-2017-008 and CVE-2017-0380.
3267 o Minor features (defensive programming):
3268 - Create a pair of consensus parameters, nf_pad_tor2web and
3269 nf_pad_single_onion, to disable netflow padding in the consensus
3270 for non-anonymous connections in case the overhead is high. Closes
3273 o Minor features (diagnostic):
3274 - Add a stack trace to the bug warnings that can be logged when
3275 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
3276 attempt for bug 23105.
3278 o Minor features (geoip):
3279 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3282 o Minor bugfixes (compilation):
3283 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3284 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3286 o Minor bugfixes (controller):
3287 - Do not crash when receiving a HSPOST command with an empty body.
3288 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3289 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3290 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3292 o Minor bugfixes (relay):
3293 - Inform the geoip and rephist modules about all requests, even on
3294 relays that are only fetching microdescriptors. Fixes a bug
3295 related to 21585; bugfix on 0.3.0.1-alpha.
3297 o Minor bugfixes (unit tests):
3298 - Fix a channelpadding unit test failure on slow systems by using
3299 mocked time instead of actual time. Fixes bug 23077; bugfix
3303 Changes in version 0.3.1.6-rc - 2017-09-05
3304 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
3305 release series, including a bug that produced weird behavior on
3306 Windows directory caches.
3308 This is the first release candidate in the Tor 0.3.1 series. If we
3309 find no new bugs or regressions here, the first stable 0.3.1 release
3310 will be nearly identical to it.
3312 o Major bugfixes (windows, directory cache):
3313 - On Windows, do not try to delete cached consensus documents and
3314 diffs before they are unmapped from memory--Windows won't allow
3315 that. Instead, allow the consensus cache directory to grow larger,
3316 to hold files that might need to stay around longer. Fixes bug
3317 22752; bugfix on 0.3.1.1-alpha.
3319 o Minor features (directory authority):
3320 - Improve the message that authorities report to relays that present
3321 RSA/Ed25519 keypairs that conflict with previously pinned keys.
3322 Closes ticket 22348.
3324 o Minor features (geoip):
3325 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
3328 o Minor features (testing):
3329 - Add more tests for compression backend initialization. Closes
3332 o Minor bugfixes (directory cache):
3333 - Fix a memory leak when recovering space in the consensus cache.
3334 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
3336 o Minor bugfixes (hidden service):
3337 - Increase the number of circuits that a service is allowed to
3338 open over a specific period of time. The value was lower than it
3339 should be (8 vs 12) in the normal case of 3 introduction points.
3340 Fixes bug 22159; bugfix on 0.3.0.5-rc.
3341 - Fix a BUG warning during HSv3 descriptor decoding that could be
3342 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
3343 on 0.3.0.1-alpha. Bug found by "haxxpop".
3344 - Rate-limit the log messages if we exceed the maximum number of
3345 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
3347 o Minor bugfixes (logging, relay):
3348 - Remove a forgotten debugging message when an introduction point
3349 successfully establishes a hidden service prop224 circuit with
3351 - Change three other log_warn() for an introduction point to
3352 protocol warnings, because they can be failure from the network
3353 and are not relevant to the operator. Fixes bug 23078; bugfix on
3354 0.3.0.1-alpha and 0.3.0.2-alpha.
3356 o Minor bugfixes (relay):
3357 - When a relay is not running as a directory cache, it will no
3358 longer generate compressed consensuses and consensus diff
3359 information. Previously, this was a waste of disk and CPU. Fixes
3360 bug 23275; bugfix on 0.3.1.1-alpha.
3362 o Minor bugfixes (robustness, error handling):
3363 - Improve our handling of the cases where OpenSSL encounters a
3364 memory error while encoding keys and certificates. We haven't
3365 observed these errors in the wild, but if they do happen, we now
3366 detect and respond better. Fixes bug 19418; bugfix on all versions
3367 of Tor. Reported by Guido Vranken.
3369 o Minor bugfixes (stability):
3370 - Avoid crashing on a double-free when unable to load or process an
3371 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
3372 with the clang static analyzer.
3374 o Minor bugfixes (testing):
3375 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3376 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3377 - Port the hs_ntor handshake test to work correctly with recent
3378 versions of the pysha3 module. Fixes bug 23071; bugfix
3381 o Minor bugfixes (Windows service):
3382 - When running as a Windows service, set the ID of the main thread
3383 correctly. Failure to do so made us fail to send log messages to
3384 the controller in 0.2.1.16-rc, slowed down controller event
3385 delivery in 0.2.7.3-rc and later, and crash with an assertion
3386 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3387 Patch and diagnosis from "Vort".
3390 Changes in version 0.3.0.10 - 2017-08-02
3391 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
3392 from the current Tor alpha series. OpenBSD users and TPROXY users
3393 should upgrade; others are probably okay sticking with 0.3.0.9.
3395 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
3396 - Tor's repository now includes a Travis Continuous Integration (CI)
3397 configuration file (.travis.yml). This is meant to help new
3398 developers and contributors who fork Tor to a Github repository be
3399 better able to test their changes, and understand what we expect
3400 to pass. To use this new build feature, you must fork Tor to your
3401 Github account, then go into the "Integrations" menu in the
3402 repository settings for your fork and enable Travis, then push
3403 your changes. Closes ticket 22636.
3405 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3406 - Fix a typo that had prevented TPROXY-based transparent proxying
3407 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3408 Patch from "d4fq0fQAgoJ".
3410 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3411 - Avoid an assertion failure bug affecting our implementation of
3412 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3413 handling of "0xbar" differs from what we had expected. Fixes bug
3414 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3416 o Minor features (backport from 0.3.1.5-alpha):
3417 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
3420 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
3421 - Roll over monthly accounting at the configured hour and minute,
3422 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3423 Found by Andrey Karpov with PVS-Studio.
3425 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
3426 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3427 bugfix on 0.2.8.1-alpha.
3428 - Fix warnings when building with libscrypt and openssl scrypt
3429 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3430 - When building with certain versions of the mingw C header files,
3431 avoid float-conversion warnings when calling the C functions
3432 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3435 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3436 - Backport a fix for an "unused variable" warning that appeared
3437 in some versions of mingw. Fixes bug 22838; bugfix on
3440 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3441 - Avoid Coverity build warnings related to our BUG() macro. By
3442 default, Coverity treats BUG() as the Linux kernel does: an
3443 instant abort(). We need to override that so our BUG() macro
3444 doesn't prevent Coverity from analyzing functions that use it.
3445 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3447 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
3448 - When rejecting a router descriptor for running an obsolete version
3449 of Tor without ntor support, warn about the obsolete tor version,
3450 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3452 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3453 - Avoid a sandbox failure when trying to re-bind to a socket and
3454 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3456 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
3457 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3458 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3461 Changes in version 0.3.1.5-alpha - 2017-08-01
3462 Tor 0.3.1.5-alpha improves the performance of consensus diff
3463 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
3464 several other bugs. If no serious bugs are found in this version, the
3465 next version will be a release candidate.
3467 This release also marks the end of support for the Tor 0.2.4.x,
3468 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
3469 further bug or security fixes. Anyone still running or distributing
3470 one of those versions should upgrade.
3472 o Major features (build system, continuous integration):
3473 - Tor's repository now includes a Travis Continuous Integration (CI)
3474 configuration file (.travis.yml). This is meant to help new
3475 developers and contributors who fork Tor to a Github repository be
3476 better able to test their changes, and understand what we expect
3477 to pass. To use this new build feature, you must fork Tor to your
3478 Github account, then go into the "Integrations" menu in the
3479 repository settings for your fork and enable Travis, then push
3480 your changes. Closes ticket 22636.
3482 o Major bugfixes (openbsd, denial-of-service):
3483 - Avoid an assertion failure bug affecting our implementation of
3484 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3485 handling of "0xbar" differs from what we had expected. Fixes bug
3486 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3488 o Major bugfixes (relay, performance):
3489 - Perform circuit handshake operations at a higher priority than we
3490 use for consensus diff creation and compression. This should
3491 prevent circuits from starving when a relay or bridge receives a
3492 new consensus, especially on lower-powered machines. Fixes bug
3493 22883; bugfix on 0.3.1.1-alpha.
3495 o Minor features (bridge authority):
3496 - Add "fingerprint" lines to the networkstatus-bridges file produced
3497 by bridge authorities. Closes ticket 22207.
3499 o Minor features (directory cache, consensus diff):
3500 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
3501 operators with low-resource environments to adjust the number of
3502 consensuses they'll store and generate diffs from. Most cache
3503 operators should leave it unchanged. Helps to work around
3506 o Minor features (geoip):
3507 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
3510 o Minor features (relay, performance):
3511 - Always start relays with at least two worker threads, to prevent
3512 priority inversion on slow tasks. Part of the fix for bug 22883.
3513 - Allow background work to be queued with different priorities, so
3514 that a big pile of slow low-priority jobs will not starve out
3515 higher priority jobs. This lays the groundwork for a fix for
3518 o Minor bugfixes (build system, rust):
3519 - Fix a problem where Rust toolchains were not being found when
3520 building without --enable-cargo-online-mode, due to setting the
3521 $HOME environment variable instead of $CARGO_HOME. Fixes bug
3522 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
3524 o Minor bugfixes (compatibility, zstd):
3525 - Write zstd epilogues correctly when the epilogue requires
3526 reallocation of the output buffer, even with zstd 1.3.0.
3527 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
3528 22927; bugfix on 0.3.1.1-alpha.
3530 o Minor bugfixes (compilation warnings):
3531 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
3532 22915; bugfix on 0.2.8.1-alpha.
3533 - Fix warnings when building with libscrypt and openssl scrypt
3534 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3535 - Compile correctly when both openssl 1.1.0 and libscrypt are
3536 detected. Previously this would cause an error. Fixes bug 22892;
3537 bugfix on 0.3.1.1-alpha.
3538 - When building with certain versions of the mingw C header files,
3539 avoid float-conversion warnings when calling the C functions
3540 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3543 o Minor bugfixes (coverity build support):
3544 - Avoid Coverity build warnings related to our BUG() macro. By
3545 default, Coverity treats BUG() as the Linux kernel does: an
3546 instant abort(). We need to override that so our BUG() macro
3547 doesn't prevent Coverity from analyzing functions that use it.
3548 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3550 o Minor bugfixes (directory authority):
3551 - When a directory authority rejects a descriptor or extrainfo with
3552 a given digest, mark that digest as undownloadable, so that we do
3553 not attempt to download it again over and over. We previously
3554 tried to avoid downloading such descriptors by other means, but we
3555 didn't notice if we accidentally downloaded one anyway. This
3556 behavior became problematic in 0.2.7.2-alpha, when authorities
3557 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3560 o Minor bugfixes (error reporting, windows):
3561 - When formatting Windows error messages, use the English format to
3562 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
3565 o Minor bugfixes (file limits, osx):
3566 - When setting the maximum number of connections allowed by the OS,
3567 always allow some extra file descriptors for other files. Fixes
3568 bug 22797; bugfix on 0.2.0.10-alpha.
3570 o Minor bugfixes (linux seccomp2 sandbox):
3571 - Avoid a sandbox failure when trying to re-bind to a socket and
3572 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3574 o Minor bugfixes (memory leaks):
3575 - Fix a small memory leak when validating a configuration that uses
3576 two or more AF_UNIX sockets for the same port type. Fixes bug
3577 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
3579 o Minor bugfixes (unit tests):
3580 - test_consdiff_base64cmp would fail on OS X because while OS X
3581 follows the standard of (less than zero/zero/greater than zero),
3582 it doesn't follow the convention of (-1/0/+1). Make the test
3583 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
3584 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3585 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3588 Changes in version 0.3.1.4-alpha - 2017-06-29
3589 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
3590 to use a guard that was in the same network family as a chosen exit
3591 relay. This is a security regression; all clients running earlier
3592 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
3595 This release also fixes several other bugs introduced in 0.3.0.x
3596 and 0.3.1.x, including others that can affect bandwidth usage
3600 - To build with zstd and lzma support, Tor now requires the
3601 pkg-config tool at build time. (This requirement was new in
3602 0.3.1.1-alpha, but was not noted at the time. Noting it here to
3603 close ticket 22623.)
3605 o Major bugfixes (path selection, security):
3606 - When choosing which guard to use for a circuit, avoid the exit's
3607 family along with the exit itself. Previously, the new guard
3608 selection logic avoided the exit, but did not consider its family.
3609 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3610 006 and CVE-2017-0377.
3612 o Major bugfixes (compression, zstd):
3613 - Correctly detect a full buffer when decompressing a large zstd-
3614 compressed input. Previously, we would sometimes treat a full
3615 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
3617 o Major bugfixes (directory protocol):
3618 - Ensure that we send "304 Not modified" as HTTP status code when a
3619 client is attempting to fetch a consensus or consensus diff, and
3620 the best one we can send them is one they already have. Fixes bug
3621 22702; bugfix on 0.3.1.1-alpha.
3623 o Major bugfixes (entry guards):
3624 - When starting with an old consensus, do not add new entry guards
3625 unless the consensus is "reasonably live" (under 1 day old). Fixes
3626 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3628 o Minor features (bug mitigation, diagnostics, logging):
3629 - Avoid an assertion failure, and log a better error message, when
3630 unable to remove a file from the consensus cache on Windows.
3631 Attempts to mitigate and diagnose bug 22752.
3633 o Minor features (geoip):
3634 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3637 o Minor bugfixes (compression):
3638 - When compressing or decompressing a buffer, check for a failure to
3639 create a compression object. Fixes bug 22626; bugfix
3641 - When decompressing a buffer, check for extra data after the end of
3642 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
3643 - When decompressing an object received over an anonymous directory
3644 connection, if we have already decompressed it using an acceptable
3645 compression method, do not reject it for looking like an
3646 unacceptable compression method. Fixes part of bug 22670; bugfix
3648 - When serving directory votes compressed with zlib, do not claim to
3649 have compressed them with zstd. Fixes bug 22669; bugfix
3651 - When spooling compressed data to an output buffer, don't try to
3652 spool more data when there is no more data to spool and we are not
3653 trying to flush the input. Previously, we would sometimes launch
3654 compression requests with nothing to do, which interferes with our
3655 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
3657 o Minor bugfixes (defensive programming):
3658 - Detect and break out of infinite loops in our compression code. We
3659 don't think that any such loops exist now, but it's best to be
3660 safe. Closes ticket 22672.
3661 - Fix a memset() off the end of an array when packing cells. This
3662 bug should be harmless in practice, since the corrupted bytes are
3663 still in the same structure, and are always padding bytes,
3664 ignored, or immediately overwritten, depending on compiler
3665 behavior. Nevertheless, because the memset()'s purpose is to make
3666 sure that any other cell-handling bugs can't expose bytes to the
3667 network, we need to fix it. Fixes bug 22737; bugfix on
3668 0.2.4.11-alpha. Fixes CID 1401591.
3670 o Minor bugfixes (linux seccomp2 sandbox):
3671 - Permit the fchmod system call, to avoid crashing on startup when
3672 starting with the seccomp2 sandbox and an unexpected set of
3673 permissions on the data directory or its contents. Fixes bug
3674 22516; bugfix on 0.2.5.4-alpha.
3675 - Fix a crash in the LZMA module, when the sandbox was enabled, and
3676 liblzma would allocate more than 16 MB of memory. We solve this by
3677 bumping the mprotect() limit in the sandbox module from 16 MB to
3678 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
3680 o Minor bugfixes (logging):
3681 - When decompressing, do not warn if we fail to decompress using a
3682 compression method that we merely guessed. Fixes part of bug
3683 22670; bugfix on 0.1.1.14-alpha.
3684 - When decompressing, treat mismatch between content-encoding and
3685 actual compression type as a protocol warning. Fixes part of bug
3686 22670; bugfix on 0.1.1.9-alpha.
3687 - Downgrade "assigned_to_cpuworker failed" message to info-level
3688 severity. In every case that can reach it, either a better warning
3689 has already been logged, or no warning is warranted. Fixes bug
3690 22356; bugfix on 0.2.6.3-alpha.
3691 - Demote a warn that was caused by libevent delays to info if
3692 netflow padding is less than 4.5 seconds late, or to notice
3693 if it is more (4.5 seconds is the amount of time that a netflow
3694 record might be emitted after, if we chose the maximum timeout).
3695 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
3697 o Minor bugfixes (process behavior):
3698 - When exiting because of an error, always exit with a nonzero exit
3699 status. Previously, we would fail to report an error in our exit
3700 status in cases related to __OwningControllerProcess failure,
3701 lockfile contention, and Ed25519 key initialization. Fixes bug
3702 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
3703 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
3707 - Add a manpage description for the key-pinning-journal file. Closes
3709 - Correctly note that bandwidth accounting values are stored in the
3710 state file, and the bw_accounting file is now obsolete. Closes
3712 - Document more of the files in the Tor data directory, including
3713 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
3714 approved-routers, sr-random, and diff-cache. Found while fixing
3718 Changes in version 0.3.0.9 - 2017-06-29
3719 Tor 0.3.0.9 fixes a path selection bug that would allow a client
3720 to use a guard that was in the same network family as a chosen exit
3721 relay. This is a security regression; all clients running earlier
3722 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
3725 This release also backports several other bugfixes from the 0.3.1.x
3728 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
3729 - When choosing which guard to use for a circuit, avoid the exit's
3730 family along with the exit itself. Previously, the new guard
3731 selection logic avoided the exit, but did not consider its family.
3732 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3733 006 and CVE-2017-0377.
3735 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
3736 - Don't block bootstrapping when a primary bridge is offline and we
3737 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3738 21969; bugfix on 0.3.0.3-alpha.
3740 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
3741 - When starting with an old consensus, do not add new entry guards
3742 unless the consensus is "reasonably live" (under 1 day old). Fixes
3743 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3745 o Minor features (geoip):
3746 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3749 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3750 - Reject version numbers with non-numeric prefixes (such as +, -, or
3751 whitespace). Disallowing whitespace prevents differential version
3752 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3753 and part of 21508; bugfix on 0.0.8pre1.
3755 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3756 - Permit the fchmod system call, to avoid crashing on startup when
3757 starting with the seccomp2 sandbox and an unexpected set of
3758 permissions on the data directory or its contents. Fixes bug
3759 22516; bugfix on 0.2.5.4-alpha.
3761 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
3762 - Fix a memset() off the end of an array when packing cells. This
3763 bug should be harmless in practice, since the corrupted bytes are
3764 still in the same structure, and are always padding bytes,
3765 ignored, or immediately overwritten, depending on compiler
3766 behavior. Nevertheless, because the memset()'s purpose is to make
3767 sure that any other cell-handling bugs can't expose bytes to the
3768 network, we need to fix it. Fixes bug 22737; bugfix on
3769 0.2.4.11-alpha. Fixes CID 1401591.
3772 Changes in version 0.3.1.3-alpha - 2017-06-08
3773 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
3774 remotely crash a hidden service with an assertion failure. Anyone
3775 running a hidden service should upgrade to this version, or to some
3776 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3778 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
3779 that sometimes made relays unreliable, as well as several other
3780 bugfixes described below.
3782 o Major bugfixes (hidden service, relay, security):
3783 - Fix a remotely triggerable assertion failure when a hidden service
3784 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3785 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3786 - Fix a remotely triggerable assertion failure caused by receiving a
3787 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3788 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3791 o Major bugfixes (relay, link handshake):
3792 - When performing the v3 link handshake on a TLS connection, report
3793 that we have the x509 certificate that we actually used on that
3794 connection, even if we have changed certificates since that
3795 connection was first opened. Previously, we would claim to have
3796 used our most recent x509 link certificate, which would sometimes
3797 make the link handshake fail. Fixes one case of bug 22460; bugfix
3800 o Major bugfixes (relays, key management):
3801 - Regenerate link and authentication certificates whenever the key
3802 that signs them changes; also, regenerate link certificates
3803 whenever the signed key changes. Previously, these processes were
3804 only weakly coupled, and we relays could (for minutes to hours)
3805 wind up with an inconsistent set of keys and certificates, which
3806 other relays would not accept. Fixes two cases of bug 22460;
3807 bugfix on 0.3.0.1-alpha.
3808 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3809 send the certificate that matches the x509 certificate that we
3810 used on the TLS connection. Previously, there was a race condition
3811 if the TLS context rotated after we began the TLS handshake but
3812 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3815 o Major bugfixes (torrc, crash):
3816 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
3817 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
3819 o Minor features (code style):
3820 - Add "Falls through" comments to our codebase, in order to silence
3821 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3822 Stieger. Closes ticket 22446.
3824 o Minor features (diagnostic):
3825 - Add logging messages to try to diagnose a rare bug that seems to
3826 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
3827 think this is happening because of incorrect system clocks, but
3828 we'd like to know for certain. Diagnostic for bug 22466.
3830 o Minor bugfixes (correctness):
3831 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3832 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3834 o Minor bugfixes (directory protocol):
3835 - Check for libzstd >= 1.1, because older versions lack the
3836 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
3838 o Minor bugfixes (link handshake):
3839 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3840 months, and regenerate it when it is within one month of expiring.
3841 Previously, we had generated this certificate at startup with a
3842 ten-year lifetime, but that could lead to weird behavior when Tor
3843 was started with a grossly inaccurate clock. Mitigates bug 22466;
3844 mitigation on 0.3.0.1-alpha.
3846 o Minor bugfixes (storage directories):
3847 - Always check for underflows in the cached storage directory usage.
3848 If the usage does underflow, re-calculate it. Also, avoid a
3849 separate underflow when the usage is not known. Fixes bug 22424;
3850 bugfix on 0.3.1.1-alpha.
3852 o Minor bugfixes (unit tests):
3853 - The unit tests now pass on systems where localhost is misconfigured
3854 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
3858 - Clarify the manpage for the (deprecated) torify script. Closes
3861 Changes in version 0.3.0.8 - 2017-06-08
3862 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
3863 remotely crash a hidden service with an assertion failure. Anyone
3864 running a hidden service should upgrade to this version, or to some
3865 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3867 Tor 0.3.0.8 also includes fixes for several key management bugs
3868 that sometimes made relays unreliable, as well as several other
3869 bugfixes described below.
3871 o Major bugfixes (hidden service, relay, security, backport
3872 from 0.3.1.3-alpha):
3873 - Fix a remotely triggerable assertion failure when a hidden service
3874 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3875 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3876 - Fix a remotely triggerable assertion failure caused by receiving a
3877 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3878 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3881 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3882 - When performing the v3 link handshake on a TLS connection, report
3883 that we have the x509 certificate that we actually used on that
3884 connection, even if we have changed certificates since that
3885 connection was first opened. Previously, we would claim to have
3886 used our most recent x509 link certificate, which would sometimes
3887 make the link handshake fail. Fixes one case of bug 22460; bugfix
3890 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
3891 - Regenerate link and authentication certificates whenever the key
3892 that signs them changes; also, regenerate link certificates
3893 whenever the signed key changes. Previously, these processes were
3894 only weakly coupled, and we relays could (for minutes to hours)
3895 wind up with an inconsistent set of keys and certificates, which
3896 other relays would not accept. Fixes two cases of bug 22460;
3897 bugfix on 0.3.0.1-alpha.
3898 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3899 send the certificate that matches the x509 certificate that we
3900 used on the TLS connection. Previously, there was a race condition
3901 if the TLS context rotated after we began the TLS handshake but
3902 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3905 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
3906 - Stop rejecting v3 hidden service descriptors because their size
3907 did not match an old padding rule. Fixes bug 22447; bugfix on
3910 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3911 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3912 December 2016 (of which ~126 were still functional) with a list of
3913 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3914 2017. Resolves ticket 21564.
3916 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
3917 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3918 bug 22252; bugfix on 0.2.9.3-alpha.
3920 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3921 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3922 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3924 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
3925 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3926 months, and regenerate it when it is within one month of expiring.
3927 Previously, we had generated this certificate at startup with a
3928 ten-year lifetime, but that could lead to weird behavior when Tor
3929 was started with a grossly inaccurate clock. Mitigates bug 22466;
3930 mitigation on 0.3.0.1-alpha.
3932 o Minor bugfixes (memory leak, directory authority, backport from
3934 - When directory authorities reject a router descriptor due to
3935 keypinning, free the router descriptor rather than leaking the
3936 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3939 Changes in version 0.2.9.11 - 2017-06-08
3940 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
3941 remotely crash a hidden service with an assertion failure. Anyone
3942 running a hidden service should upgrade to this version, or to some
3943 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3944 are not affected by TROVE-2017-004.)
3946 Tor 0.2.9.11 also backports fixes for several key management bugs
3947 that sometimes made relays unreliable, as well as several other
3948 bugfixes described below.
3950 o Major bugfixes (hidden service, relay, security, backport
3951 from 0.3.1.3-alpha):
3952 - Fix a remotely triggerable assertion failure caused by receiving a
3953 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3954 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3957 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3958 - When performing the v3 link handshake on a TLS connection, report
3959 that we have the x509 certificate that we actually used on that
3960 connection, even if we have changed certificates since that
3961 connection was first opened. Previously, we would claim to have
3962 used our most recent x509 link certificate, which would sometimes
3963 make the link handshake fail. Fixes one case of bug 22460; bugfix
3966 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3967 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3968 December 2016 (of which ~126 were still functional) with a list of
3969 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3970 2017. Resolves ticket 21564.
3972 o Minor features (future-proofing, backport from 0.3.0.7):
3973 - Tor no longer refuses to download microdescriptors or descriptors if
3974 they are listed as "published in the future". This change will
3975 eventually allow us to stop listing meaningful "published" dates
3976 in microdescriptor consensuses, and thereby allow us to reduce the
3977 resources required to download consensus diffs by over 50%.
3978 Implements part of ticket 21642; implements part of proposal 275.
3980 o Minor features (directory authorities, backport from 0.3.0.4-rc)
3981 - Directory authorities now reject relays running versions
3982 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3983 suffer from bug 20499 and don't keep their consensus cache
3984 up-to-date. Resolves ticket 20509.
3986 o Minor features (geoip):
3987 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3990 o Minor bugfixes (control port, backport from 0.3.0.6):
3991 - The GETINFO extra-info/digest/<digest> command was broken because
3992 of a wrong base16 decode return value check, introduced when
3993 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3995 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3996 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3997 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3999 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
4000 - The getpid() system call is now permitted under the Linux seccomp2
4001 sandbox, to avoid crashing with versions of OpenSSL (and other
4002 libraries) that attempt to learn the process's PID by using the
4003 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4006 o Minor bugfixes (memory leak, directory authority, backport
4007 from 0.3.1.2-alpha):
4008 - When directory authorities reject a router descriptor due to
4009 keypinning, free the router descriptor rather than leaking the
4010 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4012 Changes in version 0.2.8.14 - 2017-06-08
4013 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4014 remotely crash a hidden service with an assertion failure. Anyone
4015 running a hidden service should upgrade to this version, or to some
4016 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4017 are not affected by TROVE-2017-004.)
4019 o Major bugfixes (hidden service, relay, security):
4020 - Fix a remotely triggerable assertion failure caused by receiving a
4021 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4022 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4025 o Minor features (geoip):
4026 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4029 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4030 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4031 December 2016 (of which ~126 were still functional) with a list of
4032 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4033 2017. Resolves ticket 21564.
4035 o Minor bugfixes (correctness):
4036 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4037 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4039 Changes in version 0.2.7.8 - 2017-06-08
4040 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4041 remotely crash a hidden service with an assertion failure. Anyone
4042 running a hidden service should upgrade to this version, or to some
4043 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4044 are not affected by TROVE-2017-004.)
4046 o Major bugfixes (hidden service, relay, security):
4047 - Fix a remotely triggerable assertion failure caused by receiving a
4048 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4049 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4052 o Minor features (geoip):
4053 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4056 o Minor bugfixes (correctness):
4057 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4058 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4061 Changes in version 0.2.6.12 - 2017-06-08
4062 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
4063 remotely crash a hidden service with an assertion failure. Anyone
4064 running a hidden service should upgrade to this version, or to some
4065 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4066 are not affected by TROVE-2017-004.)
4068 o Major bugfixes (hidden service, relay, security):
4069 - Fix a remotely triggerable assertion failure caused by receiving a
4070 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4071 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4074 o Minor features (geoip):
4075 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4078 o Minor bugfixes (correctness):
4079 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4080 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4082 Changes in version 0.2.5.14 - 2017-06-08
4083 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
4084 remotely crash a hidden service with an assertion failure. Anyone
4085 running a hidden service should upgrade to this version, or to some
4086 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4087 are not affected by TROVE-2017-004.)
4089 o Major bugfixes (hidden service, relay, security):
4090 - Fix a remotely triggerable assertion failure caused by receiving a
4091 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4092 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4095 o Minor features (geoip):
4096 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4099 o Minor bugfixes (correctness):
4100 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4101 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4103 Changes in version 0.2.4.29 - 2017-06-08
4104 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
4105 remotely crash a hidden service with an assertion failure. Anyone
4106 running a hidden service should upgrade to this version, or to some
4107 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4108 are not affected by TROVE-2017-004.)
4110 o Major bugfixes (hidden service, relay, security):
4111 - Fix a remotely triggerable assertion failure caused by receiving a
4112 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4113 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4116 o Minor features (geoip):
4117 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4120 o Minor bugfixes (correctness):
4121 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4122 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4125 Changes in version 0.3.1.2-alpha - 2017-05-26
4126 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
4127 fixes a few bugs found while testing 0.3.1.1-alpha, including a
4128 memory corruption bug that affected relay stability.
4130 o Major bugfixes (crash, relay):
4131 - Fix a memory-corruption bug in relays that set MyFamily.
4132 Previously, they would double-free MyFamily elements when making
4133 the next descriptor or when changing their configuration. Fixes
4134 bug 22368; bugfix on 0.3.1.1-alpha.
4136 o Minor bugfixes (logging):
4137 - Log a better message when a directory authority replies to an
4138 upload with an unexpected status code. Fixes bug 11121; bugfix
4141 o Minor bugfixes (memory leak, directory authority):
4142 - When directory authorities reject a router descriptor due to
4143 keypinning, free the router descriptor rather than leaking the
4144 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4147 Changes in version 0.3.1.1-alpha - 2017-05-22
4148 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
4149 reduces the bandwidth usage for Tor's directory protocol, adds some
4150 basic padding to resist netflow-based traffic analysis and to serve as
4151 the basis of other padding in the future, and adds rust support to the
4154 It also contains numerous other small features and improvements to
4155 security, correctness, and performance.
4157 Below are the changes since 0.3.0.7.
4159 o Major features (directory protocol):
4160 - Tor relays and authorities can now serve clients an abbreviated
4161 version of the consensus document, containing only the changes
4162 since an older consensus document that the client holds. Clients
4163 now request these documents when available. When both client and
4164 server use this new protocol, they will use far less bandwidth (up
4165 to 94% less) to keep the client's consensus up-to-date. Implements
4166 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
4167 - Tor can now compress directory traffic with lzma or with zstd
4168 compression algorithms, which can deliver better bandwidth
4169 performance. Because lzma is computationally expensive, it's only
4170 used for documents that can be compressed once and served many
4171 times. Support for these algorithms requires that tor is built
4172 with the libzstd and/or liblzma libraries available. Implements
4173 proposal 278; closes ticket 21662.
4174 - Relays now perform the more expensive compression operations, and
4175 consensus diff generation, in worker threads. This separation
4176 avoids delaying the main thread when a new consensus arrives.
4178 o Major features (experimental):
4179 - Tor can now build modules written in Rust. To turn this on, pass
4180 the "--enable-rust" flag to the configure script. It's not time to
4181 get excited yet: currently, there is no actual Rust functionality
4182 beyond some simple glue code, and a notice at startup to tell you
4183 that Rust is running. Still, we hope that programmers and
4184 packagers will try building Tor with Rust support, so that we can
4185 find issues and solve portability problems. Closes ticket 22106.
4187 o Major features (traffic analysis resistance):
4188 - Connections between clients and relays now send a padding cell in
4189 each direction every 1.5 to 9.5 seconds (tunable via consensus
4190 parameters). This padding will not resist specialized
4191 eavesdroppers, but it should be enough to make many ISPs' routine
4192 network flow logging less useful in traffic analysis against
4195 Padding is negotiated using Tor's link protocol, so both relays
4196 and clients must upgrade for this to take effect. Clients may
4197 still send padding despite the relay's version by setting
4198 ConnectionPadding 1 in torrc, and may disable padding by setting
4199 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
4200 users with the torrc option ReducedConnectionPadding. Implements
4201 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
4202 - Relays will publish 24 hour totals of padding and non-padding cell
4203 counts to their extra-info descriptors, unless PaddingStatistics 0
4204 is set in torrc. These 24 hour totals are also rounded to
4207 o Major bugfixes (connection usage):
4208 - We use NETINFO cells to try to determine if both relays involved
4209 in a connection will agree on the canonical status of that
4210 connection. We prefer the connections where this is the case for
4211 extend cells, and try to close connections where relays disagree
4212 on their canonical status early. Also, we now prefer the oldest
4213 valid connection for extend cells. These two changes should reduce
4214 the number of long-term connections that are kept open between
4215 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
4216 - Relays now log hourly statistics (look for
4217 "channel_check_for_duplicates" lines) on the total number of
4218 connections to other relays. If the number of connections per
4219 relay is unexpectedly large, this log message is at notice level.
4220 Otherwise it is at info.
4222 o Major bugfixes (entry guards):
4223 - Don't block bootstrapping when a primary bridge is offline and we
4224 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4225 21969; bugfix on 0.3.0.3-alpha.
4227 o Major bugfixes (linux TPROXY support):
4228 - Fix a typo that had prevented TPROXY-based transparent proxying
4229 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4230 Patch from "d4fq0fQAgoJ".
4232 o Minor features (security, windows):
4233 - Enable a couple of pieces of Windows hardening: one
4234 (HeapEnableTerminationOnCorruption) that has been on-by-default
4235 since Windows 8, and unavailable before Windows 7; and one
4236 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4237 affect us, but shouldn't do any harm. Closes ticket 21953.
4239 o Minor features (config options):
4240 - Allow "%include" directives in torrc configuration files. These
4241 directives import the settings from other files, or from all the
4242 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
4243 - Make SAVECONF return an error when overwriting a torrc that has
4244 includes. Using SAVECONF with the FORCE option will allow it to
4245 overwrite torrc even if includes are used. Related to ticket 1922.
4246 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
4247 will work without the FORCE option. Related to ticket 1922.
4249 o Minor features (controller):
4250 - Warn the first time that a controller requests data in the long-
4251 deprecated 'GETINFO network-status' format. Closes ticket 21703.
4253 o Minor features (defaults):
4254 - The default value for UseCreateFast is now 0: clients which
4255 haven't yet received a consensus document will now use a proper
4256 ntor handshake to talk to their directory servers whenever they
4257 can. Closes ticket 21407.
4258 - Onion key rotation and expiry intervals are now defined as a
4259 network consensus parameter, per proposal 274. The default
4260 lifetime of an onion key is increased from 7 to 28 days. Old onion
4261 keys will expire after 7 days by default. This change will make
4262 consensus diffs much smaller, and save significant bandwidth.
4263 Closes ticket 21641.
4265 o Minor features (fallback directory list):
4266 - Update the fallback directory mirror whitelist and blacklist based
4267 on operator emails. Closes task 21121.
4268 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4269 December 2016 (of which ~126 were still functional) with a list of
4270 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4271 2017. Resolves ticket 21564.
4273 o Minor features (hidden services, logging):
4274 - Log a message when a hidden service descriptor has fewer
4275 introduction points than specified in
4276 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
4277 - Log a message when a hidden service reaches its introduction point
4278 circuit limit, and when that limit is reset. Follow up to ticket
4279 21594; closes ticket 21622.
4280 - Warn user if multiple entries in EntryNodes and at least one
4281 HiddenService are used together. Pinning EntryNodes along with a
4282 hidden service can be possibly harmful; for instance see ticket
4283 14917 or 21155. Closes ticket 21155.
4285 o Minor features (linux seccomp2 sandbox):
4286 - We now have a document storage backend compatible with the Linux
4287 seccomp2 sandbox. This backend is used for consensus documents and
4288 diffs between them; in the long term, we'd like to use it for
4289 unparseable directory material too. Closes ticket 21645
4290 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
4291 from 1MB to 16MB. This was necessary with the glibc allocator in
4292 order to allow worker threads to allocate more memory -- which in
4293 turn is necessary because of our new use of worker threads for
4294 compression. Closes ticket 22096.
4296 o Minor features (logging):
4297 - Log files are no longer created world-readable by default.
4298 (Previously, most distributors would store the logs in a non-
4299 world-readable location to prevent inappropriate access. This
4300 change is an extra precaution.) Closes ticket 21729; patch
4303 o Minor features (performance):
4304 - Our Keccak (SHA-3) implementation now accesses memory more
4305 efficiently, especially on little-endian systems. Closes
4307 - Add an O(1) implementation of channel_find_by_global_id(), to
4308 speed some controller functions.
4310 o Minor features (relay, configuration):
4311 - The MyFamily option may now be repeated as many times as desired,
4312 for relays that want to configure large families. Closes ticket
4313 4998; patch by Daniel Pinto.
4315 o Minor features (safety):
4316 - Add an explicit check to extrainfo_parse_entry_from_string() for
4317 NULL inputs. We don't believe this can actually happen, but it may
4318 help silence a warning from the Clang analyzer. Closes
4321 o Minor features (testing):
4322 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
4323 When Tor is compiled with this option, we disable a number of
4324 redundant memory-safety failsafes that are intended to stop bugs
4325 from becoming security issues. This makes it easier to hunt for
4326 bugs that would be security issues without the failsafes turned
4327 on. Closes ticket 21439.
4328 - Add a general event-tracing instrumentation support to Tor. This
4329 subsystem will enable developers and researchers to add fine-
4330 grained instrumentation to their Tor instances, for use when
4331 examining Tor network performance issues. There are no trace
4332 events yet, and event-tracing is off by default unless enabled at
4333 compile time. Implements ticket 13802.
4334 - Improve our version parsing tests: add tests for typical version
4335 components, add tests for invalid versions, including numeric
4336 range and non-numeric prefixes. Unit tests 21278, 21450, and
4337 21507. Partially implements 21470.
4339 o Minor bugfixes (bandwidth accounting):
4340 - Roll over monthly accounting at the configured hour and minute,
4341 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4342 Found by Andrey Karpov with PVS-Studio.
4344 o Minor bugfixes (code correctness):
4345 - Accurately identify client connections by their lack of peer
4346 authentication. This means that we bail out earlier if asked to
4347 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
4350 o Minor bugfixes (configuration):
4351 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4352 bug 22252; bugfix on 0.2.9.3-alpha.
4354 o Minor bugfixes (connection lifespan):
4355 - Allow more control over how long TLS connections are kept open:
4356 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
4357 single option called CircuitsAvailableTimeout. Also, allow the
4358 consensus to control the default values for both this preference
4359 and the lifespan of relay-to-relay connections. Fixes bug 17592;
4360 bugfix on 0.2.5.5-alpha.
4361 - Increase the initial circuit build timeout testing frequency, to
4362 help ensure that ReducedConnectionPadding clients finish learning
4363 a timeout before their orconn would expire. The initial testing
4364 rate was set back in the days of TAP and before the Tor Browser
4365 updater, when we had to be much more careful about new clients
4366 making lots of circuits. With this change, a circuit build timeout
4367 is learned in about 15-20 minutes, instead of 100-120 minutes.
4369 o Minor bugfixes (controller):
4370 - GETINFO onions/current and onions/detached no longer respond with
4371 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
4372 - Trigger HS descriptor events on the control port when the client
4373 fails to pick a hidden service directory for a hidden service.
4374 This can happen if all the hidden service directories are in
4375 ExcludeNodes, or they have all been queried within the last 15
4376 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
4378 o Minor bugfixes (directory authority):
4379 - When rejecting a router descriptor for running an obsolete version
4380 of Tor without ntor support, warn about the obsolete tor version,
4381 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4382 - Prevent the shared randomness subsystem from asserting when
4383 initialized by a bridge authority with an incomplete configuration
4384 file. Fixes bug 21586; bugfix on 0.2.9.8.
4386 o Minor bugfixes (exit-side DNS):
4387 - Fix an untriggerable assertion that checked the output of a
4388 libevent DNS error, so that the assertion actually behaves as
4389 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
4390 Karpov using PVS-Studio.
4392 o Minor bugfixes (fallback directories):
4393 - Make the usage example in updateFallbackDirs.py actually work, and
4394 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
4395 - Decrease the guard flag average required to be a fallback. This
4396 allows us to keep relays that have their guard flag removed when
4397 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
4398 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
4399 bugfix on 0.2.8.1-alpha.
4400 - Make sure fallback directory mirrors have the same address, port,
4401 and relay identity key for at least 30 days before they are
4402 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
4404 o Minor bugfixes (hidden services):
4405 - Stop printing a cryptic warning when a hidden service gets a
4406 request to connect to a virtual port that it hasn't configured.
4407 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
4408 - Simplify hidden service descriptor creation by using an existing
4409 flag to check if an introduction point is established. Fixes bug
4410 21599; bugfix on 0.2.7.2-alpha.
4412 o Minor bugfixes (memory leak):
4413 - Fix a small memory leak at exit from the backtrace handler code.
4414 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
4416 o Minor bugfixes (protocol, logging):
4417 - Downgrade a log statement about unexpected relay cells from "bug"
4418 to "protocol warning", because there is at least one use case
4419 where it can be triggered by a buggy tor implementation. Fixes bug
4420 21293; bugfix on 0.1.1.14-alpha.
4422 o Minor bugfixes (testing):
4423 - Use unbuffered I/O for utility functions around the
4424 process_handle_t type. This fixes unit test failures reported on
4425 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
4426 - Make display of captured unit test log messages consistent. Fixes
4427 bug 21510; bugfix on 0.2.9.3-alpha.
4428 - Make test-network.sh always call chutney's test-network.sh.
4429 Previously, this only worked on systems which had bash installed,
4430 due to some bash-specific code in the script. Fixes bug 19699;
4431 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
4433 o Minor bugfixes (voting consistency):
4434 - Reject version numbers with non-numeric prefixes (such as +, -, or
4435 whitespace). Disallowing whitespace prevents differential version
4436 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4437 and part of 21508; bugfix on 0.0.8pre1.
4439 o Minor bugfixes (windows, relay):
4440 - Resolve "Failure from drain_fd: No error" warnings on Windows
4441 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
4443 o Code simplification and refactoring:
4444 - Break up the 630-line function connection_dir_client_reached_eof()
4445 into a dozen smaller functions. This change should help
4446 maintainability and readability of the client directory code.
4447 - Isolate our use of the openssl headers so that they are only
4448 included from our crypto wrapper modules, and from tests that
4449 examine those modules' internals. Closes ticket 21841.
4450 - Simplify our API to launch directory requests, making it more
4451 extensible and less error-prone. Now it's easier to add extra
4452 headers to directory requests. Closes ticket 21646.
4453 - Our base64 decoding functions no longer overestimate the output
4454 space that they need when parsing unpadded inputs. Closes
4456 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
4457 Resolves ticket 22213.
4458 - The logic that directory caches use to spool request to clients,
4459 serving them one part at a time so as not to allocate too much
4460 memory, has been refactored for consistency. Previously there was
4461 a separate spooling implementation per type of spoolable data. Now
4462 there is one common spooling implementation, with extensible data
4463 types. Closes ticket 21651.
4464 - Tor's compression module now supports multiple backends. Part of
4465 the implementation for proposal 278; closes ticket 21663.
4468 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
4469 Closes ticket 21873.
4470 - Correct documentation about the default DataDirectory value.
4471 Closes ticket 21151.
4472 - Document the default behavior of NumEntryGuards and
4473 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
4475 - Document key=value pluggable transport arguments for Bridge lines
4476 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
4477 - Note that bandwidth-limiting options don't affect TCP headers or
4478 DNS. Closes ticket 17170.
4480 o Removed features (configuration options, all in ticket 22060):
4481 - These configuration options are now marked Obsolete, and no longer
4482 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
4483 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
4484 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
4485 in 0.2.9.2-alpha and have now been removed. The previous default
4486 behavior is now always chosen; the previous (less secure) non-
4487 default behavior is now unavailable.
4488 - CloseHSClientCircuitsImmediatelyOnTimeout and
4489 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
4490 0.2.9.2-alpha and now have been removed. HS circuits never close
4491 on circuit build timeout; they have a longer timeout period.
4492 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
4493 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
4494 (and others) to configure listen-only and advertise-only addresses.
4496 o Removed features (tools):
4497 - We've removed the tor-checkkey tool from src/tools. Long ago, we
4498 used it to help people detect RSA keys that were generated by
4499 versions of Debian affected by CVE-2008-0166. But those keys have
4500 been out of circulation for ages, and this tool is no longer
4501 required. Closes ticket 21842.
4504 Changes in version 0.3.0.7 - 2017-05-15
4505 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
4506 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
4507 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
4508 clients are not affected.
4510 o Major bugfixes (hidden service directory, security):
4511 - Fix an assertion failure in the hidden service directory code, which
4512 could be used by an attacker to remotely cause a Tor relay process to
4513 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
4514 should upgrade. This security issue is tracked as TROVE-2017-002.
4515 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
4518 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4521 o Minor features (future-proofing):
4522 - Tor no longer refuses to download microdescriptors or descriptors
4523 if they are listed as "published in the future". This change will
4524 eventually allow us to stop listing meaningful "published" dates
4525 in microdescriptor consensuses, and thereby allow us to reduce the
4526 resources required to download consensus diffs by over 50%.
4527 Implements part of ticket 21642; implements part of proposal 275.
4529 o Minor bugfixes (Linux seccomp2 sandbox):
4530 - The getpid() system call is now permitted under the Linux seccomp2
4531 sandbox, to avoid crashing with versions of OpenSSL (and other
4532 libraries) that attempt to learn the process's PID by using the
4533 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4537 Changes in version 0.3.0.6 - 2017-04-26
4538 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
4540 With the 0.3.0 series, clients and relays now use Ed25519 keys to
4541 authenticate their link connections to relays, rather than the old
4542 RSA1024 keys that they used before. (Circuit crypto has been
4543 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
4544 the guard selection and replacement algorithm to behave more robustly
4545 in the presence of unreliable networks, and to resist guard-
4548 This series also includes numerous other small features and bugfixes,
4549 along with more groundwork for the upcoming hidden-services revamp.
4551 Per our stable release policy, we plan to support the Tor 0.3.0
4552 release series for at least the next nine months, or for three months
4553 after the first stable release of the 0.3.1 series: whichever is
4554 longer. If you need a release with long-term support, we recommend
4555 that you stay with the 0.2.9 series.
4557 Below are the changes since 0.3.0.5-rc. For a list of all changes
4558 since 0.2.9, see the ReleaseNotes file.
4560 o Minor features (geoip):
4561 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
4564 o Minor bugfixes (control port):
4565 - The GETINFO extra-info/digest/<digest> command was broken because
4566 of a wrong base16 decode return value check, introduced when
4567 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4569 o Minor bugfixes (crash prevention):
4570 - Fix a (currently untriggerable, but potentially dangerous) crash
4571 bug when base32-encoding inputs whose sizes are not a multiple of
4572 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
4575 Changes in version 0.3.0.5-rc - 2017-04-05
4576 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
4577 0.3.0 release series.
4579 This is the second release candidate in the Tor 0.3.0 series, and has
4580 much fewer changes than the first. If we find no new bugs or
4581 regressions here, the first stable 0.3.0 release will be nearly
4584 o Major bugfixes (crash, directory connections):
4585 - Fix a rare crash when sending a begin cell on a circuit whose
4586 linked directory connection had already been closed. Fixes bug
4587 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
4589 o Major bugfixes (guard selection):
4590 - Fix a guard selection bug where Tor would refuse to bootstrap in
4591 some cases if the user swapped a bridge for another bridge in
4592 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
4593 Reported by "torvlnt33r".
4595 o Minor features (geoip):
4596 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
4599 o Minor bugfix (compilation):
4600 - Fix a warning when compiling hs_service.c. Previously, it had no
4601 exported symbols when compiled for libor.a, resulting in a
4602 compilation warning from clang. Fixes bug 21825; bugfix
4605 o Minor bugfixes (hidden services):
4606 - Make hidden services check for failed intro point connections,
4607 even when they have exceeded their intro point creation limit.
4608 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
4609 - Make hidden services with 8 to 10 introduction points check for
4610 failed circuits immediately after startup. Previously, they would
4611 wait for 5 minutes before performing their first checks. Fixes bug
4612 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
4614 o Minor bugfixes (memory leaks):
4615 - Fix a memory leak when using GETCONF on a port option. Fixes bug
4616 21682; bugfix on 0.3.0.3-alpha.
4618 o Minor bugfixes (relay):
4619 - Avoid a double-marked-circuit warning that could happen when we
4620 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
4623 o Minor bugfixes (tests):
4624 - Run the entry_guard_parse_from_state_full() test with the time set
4625 to a specific date. (The guard state that this test was parsing
4626 contained guards that had expired since the test was first
4627 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
4630 - Update the description of the directory server options in the
4631 manual page, to clarify that a relay no longer needs to set
4632 DirPort in order to be a directory cache. Closes ticket 21720.
4636 Changes in version 0.2.8.13 - 2017-03-03
4637 Tor 0.2.8.13 backports a security fix from later Tor
4638 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
4639 this release, if for some reason they cannot upgrade to a later
4640 release series, and if they build Tor with the --enable-expensive-hardening
4643 Note that support for Tor 0.2.8.x is ending next year: we will not issue
4644 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
4645 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4647 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4648 - Fix an integer underflow bug when comparing malformed Tor
4649 versions. This bug could crash Tor when built with
4650 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4651 0.2.9.8, which were built with -ftrapv by default. In other cases
4652 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4653 on 0.0.8pre1. Found by OSS-Fuzz.
4655 o Minor features (geoip):
4656 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4660 Changes in version 0.2.7.7 - 2017-03-03
4661 Tor 0.2.7.7 backports a number of security fixes from later Tor
4662 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
4663 this release, if for some reason they cannot upgrade to a later
4666 Note that support for Tor 0.2.7.x is ending this year: we will not issue
4667 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
4668 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4670 o Directory authority changes (backport from 0.2.8.5-rc):
4671 - Urras is no longer a directory authority. Closes ticket 19271.
4673 o Directory authority changes (backport from 0.2.9.2-alpha):
4674 - The "Tonga" bridge authority has been retired; the new bridge
4675 authority is "Bifroest". Closes tickets 19728 and 19690.
4677 o Directory authority key updates (backport from 0.2.8.1-alpha):
4678 - Update the V3 identity key for the dannenberg directory authority:
4679 it was changed on 18 November 2015. Closes task 17906. Patch
4682 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4683 - Fix a bug in parsing that could cause clients to read a single
4684 byte past the end of an allocated region. This bug could be used
4685 to cause hardened clients (built with --enable-expensive-hardening)
4686 to crash if they tried to visit a hostile hidden service. Non-
4687 hardened clients are only affected depending on the details of
4688 their platform's memory allocator. Fixes bug 21018; bugfix on
4689 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4690 2016-12-002 and as CVE-2016-1254.
4692 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4693 - Stop a crash that could occur when a client running with DNSPort
4694 received a query with multiple address types, and the first
4695 address type was not supported. Found and fixed by Scott Dial.
4696 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4697 - Prevent a class of security bugs caused by treating the contents
4698 of a buffer chunk as if they were a NUL-terminated string. At
4699 least one such bug seems to be present in all currently used
4700 versions of Tor, and would allow an attacker to remotely crash
4701 most Tor instances, especially those compiled with extra compiler
4702 hardening. With this defense in place, such bugs can't crash Tor,
4703 though we should still fix them as they occur. Closes ticket
4704 20384 (TROVE-2016-10-001).
4706 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4707 - Avoid a difficult-to-trigger heap corruption attack when extending
4708 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4709 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4710 Reported by Guido Vranken.
4712 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4713 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4714 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4716 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4717 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4718 pointer to the previous (uninitialized) key value. The impact here
4719 should be limited to a difficult-to-trigger crash, if OpenSSL is
4720 running an engine that makes key generation failures possible, or
4721 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4722 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4725 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4726 - Fix an integer underflow bug when comparing malformed Tor
4727 versions. This bug could crash Tor when built with
4728 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4729 0.2.9.8, which were built with -ftrapv by default. In other cases
4730 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4731 on 0.0.8pre1. Found by OSS-Fuzz.
4733 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4734 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4735 zero size. Check size argument to memwipe() for underflow. Fixes
4736 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4739 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4740 - Make Tor survive errors involving connections without a
4741 corresponding event object. Previously we'd fail with an
4742 assertion; now we produce a log message. Related to bug 16248.
4744 o Minor features (geoip):
4745 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4749 Changes in version 0.2.6.11 - 2017-03-03
4750 Tor 0.2.6.11 backports a number of security fixes from later Tor
4751 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
4752 this release, if for some reason they cannot upgrade to a later
4755 Note that support for Tor 0.2.6.x is ending this year: we will not issue
4756 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
4757 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4759 o Directory authority changes (backport from 0.2.8.5-rc):
4760 - Urras is no longer a directory authority. Closes ticket 19271.
4762 o Directory authority changes (backport from 0.2.9.2-alpha):
4763 - The "Tonga" bridge authority has been retired; the new bridge
4764 authority is "Bifroest". Closes tickets 19728 and 19690.
4766 o Directory authority key updates (backport from 0.2.8.1-alpha):
4767 - Update the V3 identity key for the dannenberg directory authority:
4768 it was changed on 18 November 2015. Closes task 17906. Patch
4771 o Major features (security fixes, backport from 0.2.9.4-alpha):
4772 - Prevent a class of security bugs caused by treating the contents
4773 of a buffer chunk as if they were a NUL-terminated string. At
4774 least one such bug seems to be present in all currently used
4775 versions of Tor, and would allow an attacker to remotely crash
4776 most Tor instances, especially those compiled with extra compiler
4777 hardening. With this defense in place, such bugs can't crash Tor,
4778 though we should still fix them as they occur. Closes ticket
4779 20384 (TROVE-2016-10-001).
4781 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4782 - Fix a bug in parsing that could cause clients to read a single
4783 byte past the end of an allocated region. This bug could be used
4784 to cause hardened clients (built with --enable-expensive-hardening)
4785 to crash if they tried to visit a hostile hidden service. Non-
4786 hardened clients are only affected depending on the details of
4787 their platform's memory allocator. Fixes bug 21018; bugfix on
4788 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4789 2016-12-002 and as CVE-2016-1254.
4791 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4792 - Stop a crash that could occur when a client running with DNSPort
4793 received a query with multiple address types, and the first
4794 address type was not supported. Found and fixed by Scott Dial.
4795 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4797 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4798 - Fix an error that could cause us to read 4 bytes before the
4799 beginning of an openssl string. This bug could be used to cause
4800 Tor to crash on systems with unusual malloc implementations, or
4801 systems with unusual hardening installed. Fixes bug 17404; bugfix
4804 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4805 - Avoid a difficult-to-trigger heap corruption attack when extending
4806 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4807 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4808 Reported by Guido Vranken.
4810 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4811 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4812 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4814 o Major bugfixes (guard selection, backport from 0.2.7.6):
4815 - Actually look at the Guard flag when selecting a new directory
4816 guard. When we implemented the directory guard design, we
4817 accidentally started treating all relays as if they have the Guard
4818 flag during guard selection, leading to weaker anonymity and worse
4819 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4822 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4823 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4824 pointer to the previous (uninitialized) key value. The impact here
4825 should be limited to a difficult-to-trigger crash, if OpenSSL is
4826 running an engine that makes key generation failures possible, or
4827 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4828 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4831 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4832 - Fix an integer underflow bug when comparing malformed Tor
4833 versions. This bug could crash Tor when built with
4834 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4835 0.2.9.8, which were built with -ftrapv by default. In other cases
4836 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4837 on 0.0.8pre1. Found by OSS-Fuzz.
4839 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4840 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4841 zero size. Check size argument to memwipe() for underflow. Fixes
4842 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4845 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4846 - Make Tor survive errors involving connections without a
4847 corresponding event object. Previously we'd fail with an
4848 assertion; now we produce a log message. Related to bug 16248.
4850 o Minor features (geoip):
4851 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4854 o Minor bugfixes (compilation, backport from 0.2.7.6):
4855 - Fix a compilation warning with Clang 3.6: Do not check the
4856 presence of an address which can never be NULL. Fixes bug 17781.
4859 Changes in version 0.2.5.13 - 2017-03-03
4860 Tor 0.2.5.13 backports a number of security fixes from later Tor
4861 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
4862 this release, if for some reason they cannot upgrade to a later
4865 Note that support for Tor 0.2.5.x is ending next year: we will not issue
4866 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
4867 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4869 o Directory authority changes (backport from 0.2.8.5-rc):
4870 - Urras is no longer a directory authority. Closes ticket 19271.
4872 o Directory authority changes (backport from 0.2.9.2-alpha):
4873 - The "Tonga" bridge authority has been retired; the new bridge
4874 authority is "Bifroest". Closes tickets 19728 and 19690.
4876 o Directory authority key updates (backport from 0.2.8.1-alpha):
4877 - Update the V3 identity key for the dannenberg directory authority:
4878 it was changed on 18 November 2015. Closes task 17906. Patch
4881 o Major features (security fixes, backport from 0.2.9.4-alpha):
4882 - Prevent a class of security bugs caused by treating the contents
4883 of a buffer chunk as if they were a NUL-terminated string. At
4884 least one such bug seems to be present in all currently used
4885 versions of Tor, and would allow an attacker to remotely crash
4886 most Tor instances, especially those compiled with extra compiler
4887 hardening. With this defense in place, such bugs can't crash Tor,
4888 though we should still fix them as they occur. Closes ticket
4889 20384 (TROVE-2016-10-001).
4891 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4892 - Fix a bug in parsing that could cause clients to read a single
4893 byte past the end of an allocated region. This bug could be used
4894 to cause hardened clients (built with --enable-expensive-hardening)
4895 to crash if they tried to visit a hostile hidden service. Non-
4896 hardened clients are only affected depending on the details of
4897 their platform's memory allocator. Fixes bug 21018; bugfix on
4898 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4899 2016-12-002 and as CVE-2016-1254.
4901 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4902 - Stop a crash that could occur when a client running with DNSPort
4903 received a query with multiple address types, and the first
4904 address type was not supported. Found and fixed by Scott Dial.
4905 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4907 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4908 - Fix an error that could cause us to read 4 bytes before the
4909 beginning of an openssl string. This bug could be used to cause
4910 Tor to crash on systems with unusual malloc implementations, or
4911 systems with unusual hardening installed. Fixes bug 17404; bugfix
4914 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4915 - Avoid a difficult-to-trigger heap corruption attack when extending
4916 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4917 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4918 Reported by Guido Vranken.
4920 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4921 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4922 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4924 o Major bugfixes (guard selection, backport from 0.2.7.6):
4925 - Actually look at the Guard flag when selecting a new directory
4926 guard. When we implemented the directory guard design, we
4927 accidentally started treating all relays as if they have the Guard
4928 flag during guard selection, leading to weaker anonymity and worse
4929 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4932 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4933 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4934 pointer to the previous (uninitialized) key value. The impact here
4935 should be limited to a difficult-to-trigger crash, if OpenSSL is
4936 running an engine that makes key generation failures possible, or
4937 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4938 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4941 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4942 - Fix an integer underflow bug when comparing malformed Tor
4943 versions. This bug could crash Tor when built with
4944 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4945 0.2.9.8, which were built with -ftrapv by default. In other cases
4946 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4947 on 0.0.8pre1. Found by OSS-Fuzz.
4949 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4950 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4951 zero size. Check size argument to memwipe() for underflow. Fixes
4952 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4955 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4956 - Make Tor survive errors involving connections without a
4957 corresponding event object. Previously we'd fail with an
4958 assertion; now we produce a log message. Related to bug 16248.
4960 o Minor features (geoip):
4961 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4964 o Minor bugfixes (compilation, backport from 0.2.7.6):
4965 - Fix a compilation warning with Clang 3.6: Do not check the
4966 presence of an address which can never be NULL. Fixes bug 17781.
4968 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
4969 - Check for failures from crypto_early_init, and refuse to continue.
4970 A previous typo meant that we could keep going with an
4971 uninitialized crypto library, and would have OpenSSL initialize
4972 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4973 when implementing ticket 4900. Patch by "teor".
4975 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4976 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4977 a client authorized hidden service. Fixes bug 15823; bugfix
4981 Changes in version 0.2.4.28 - 2017-03-03
4982 Tor 0.2.4.28 backports a number of security fixes from later Tor
4983 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
4984 this release, if for some reason they cannot upgrade to a later
4987 Note that support for Tor 0.2.4.x is ending soon: we will not issue
4988 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
4989 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
4991 o Directory authority changes (backport from 0.2.8.5-rc):
4992 - Urras is no longer a directory authority. Closes ticket 19271.
4994 o Directory authority changes (backport from 0.2.9.2-alpha):
4995 - The "Tonga" bridge authority has been retired; the new bridge
4996 authority is "Bifroest". Closes tickets 19728 and 19690.
4998 o Directory authority key updates (backport from 0.2.8.1-alpha):
4999 - Update the V3 identity key for the dannenberg directory authority:
5000 it was changed on 18 November 2015. Closes task 17906. Patch
5003 o Major features (security fixes, backport from 0.2.9.4-alpha):
5004 - Prevent a class of security bugs caused by treating the contents
5005 of a buffer chunk as if they were a NUL-terminated string. At
5006 least one such bug seems to be present in all currently used
5007 versions of Tor, and would allow an attacker to remotely crash
5008 most Tor instances, especially those compiled with extra compiler
5009 hardening. With this defense in place, such bugs can't crash Tor,
5010 though we should still fix them as they occur. Closes ticket
5011 20384 (TROVE-2016-10-001).
5013 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5014 - Fix a bug in parsing that could cause clients to read a single
5015 byte past the end of an allocated region. This bug could be used
5016 to cause hardened clients (built with --enable-expensive-hardening)
5017 to crash if they tried to visit a hostile hidden service. Non-
5018 hardened clients are only affected depending on the details of
5019 their platform's memory allocator. Fixes bug 21018; bugfix on
5020 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5021 2016-12-002 and as CVE-2016-1254.
5023 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5024 - Fix an error that could cause us to read 4 bytes before the
5025 beginning of an openssl string. This bug could be used to cause
5026 Tor to crash on systems with unusual malloc implementations, or
5027 systems with unusual hardening installed. Fixes bug 17404; bugfix
5030 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5031 - Avoid a difficult-to-trigger heap corruption attack when extending
5032 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5033 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5034 Reported by Guido Vranken.
5036 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5037 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5038 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5040 o Major bugfixes (guard selection, backport from 0.2.7.6):
5041 - Actually look at the Guard flag when selecting a new directory
5042 guard. When we implemented the directory guard design, we
5043 accidentally started treating all relays as if they have the Guard
5044 flag during guard selection, leading to weaker anonymity and worse
5045 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5048 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5049 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5050 pointer to the previous (uninitialized) key value. The impact here
5051 should be limited to a difficult-to-trigger crash, if OpenSSL is
5052 running an engine that makes key generation failures possible, or
5053 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5054 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5057 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5058 - Fix an integer underflow bug when comparing malformed Tor
5059 versions. This bug could crash Tor when built with
5060 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5061 0.2.9.8, which were built with -ftrapv by default. In other cases
5062 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5063 on 0.0.8pre1. Found by OSS-Fuzz.
5065 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5066 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5067 zero size. Check size argument to memwipe() for underflow. Fixes
5068 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5071 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5072 - Make Tor survive errors involving connections without a
5073 corresponding event object. Previously we'd fail with an
5074 assertion; now we produce a log message. Related to bug 16248.
5076 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
5077 - Make it harder for attackers to overload hidden services with
5078 introductions, by blocking multiple introduction requests on the
5079 same circuit. Resolves ticket 15515.
5081 o Minor features (geoip):
5082 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5085 o Minor bugfixes (compilation, backport from 0.2.7.6):
5086 - Fix a compilation warning with Clang 3.6: Do not check the
5087 presence of an address which can never be NULL. Fixes bug 17781.
5089 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5090 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5091 a client authorized hidden service. Fixes bug 15823; bugfix
5095 Changes in version 0.3.0.4-rc - 2017-03-01
5096 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
5097 0.3.0 release series, and introduces a few reliability features to
5098 keep them from coming back.
5100 This is the first release candidate in the Tor 0.3.0 series. If we
5101 find no new bugs or regressions here, the first stable 0.3.0 release
5102 will be nearly identical to it.
5104 o Major bugfixes (bridges):
5105 - When the same bridge is configured multiple times with the same
5106 identity, but at different address:port combinations, treat those
5107 bridge instances as separate guards. This fix restores the ability
5108 of clients to configure the same bridge with multiple pluggable
5109 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
5111 o Major bugfixes (hidden service directory v3):
5112 - Stop crashing on a failed v3 hidden service descriptor lookup
5113 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
5115 o Major bugfixes (parsing):
5116 - When parsing a malformed content-length field from an HTTP
5117 message, do not read off the end of the buffer. This bug was a
5118 potential remote denial-of-service attack against Tor clients and
5119 relays. A workaround was released in October 2016, to prevent this
5120 bug from crashing Tor. This is a fix for the underlying issue,
5121 which should no longer matter (if you applied the earlier patch).
5122 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
5123 using AFL (http://lcamtuf.coredump.cx/afl/).
5124 - Fix an integer underflow bug when comparing malformed Tor
5125 versions. This bug could crash Tor when built with
5126 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5127 0.2.9.8, which were built with -ftrapv by default. In other cases
5128 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5129 on 0.0.8pre1. Found by OSS-Fuzz.
5131 o Minor feature (protocol versioning):
5132 - Add new protocol version for proposal 224. HSIntro now advertises
5133 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
5135 o Minor features (directory authorities):
5136 - Directory authorities now reject descriptors that claim to be
5137 malformed versions of Tor. Helps prevent exploitation of
5139 - Reject version numbers with components that exceed INT32_MAX.
5140 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5141 Fixes bug 21450; bugfix on 0.0.8pre1.
5142 - Directory authorities now reject relays running versions
5143 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
5144 suffer from bug 20499 and don't keep their consensus cache
5145 up-to-date. Resolves ticket 20509.
5147 o Minor features (geoip):
5148 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5151 o Minor features (reliability, crash):
5152 - Try better to detect problems in buffers where they might grow (or
5153 think they have grown) over 2 GB in size. Diagnostic for
5156 o Minor features (testing):
5157 - During 'make test-network-all', if tor logs any warnings, ask
5158 chutney to output them. Requires a recent version of chutney with
5159 the 21572 patch. Implements 21570.
5161 o Minor bugfixes (certificate expiration time):
5162 - Avoid using link certificates that don't become valid till some
5163 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
5165 o Minor bugfixes (code correctness):
5166 - Repair a couple of (unreachable or harmless) cases of the risky
5167 comparison-by-subtraction pattern that caused bug 21278.
5168 - Remove a redundant check for the UseEntryGuards option from the
5169 options_transition_affects_guards() function. Fixes bug 21492;
5170 bugfix on 0.3.0.1-alpha.
5172 o Minor bugfixes (directory mirrors):
5173 - Allow relays to use directory mirrors without a DirPort: these
5174 relays need to be contacted over their ORPorts using a begindir
5175 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
5176 - Clarify the message logged when a remote relay is unexpectedly
5177 missing an ORPort or DirPort: users were confusing this with a
5178 local port. Fixes another case of bug 20711; bugfix
5181 o Minor bugfixes (guards):
5182 - Don't warn about a missing guard state on timeout-measurement
5183 circuits: they aren't supposed to be using guards. Fixes an
5184 instance of bug 21007; bugfix on 0.3.0.1-alpha.
5185 - Silence a BUG() warning when attempting to use a guard whose
5186 descriptor we don't know, and make this scenario less likely to
5187 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
5189 o Minor bugfixes (hidden service):
5190 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
5191 cells. Previously, we were using sizeof() on a pointer, instead of
5192 the real destination buffer. Fortunately, that value was only used
5193 to double-check that there was enough room--which was already
5194 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
5196 o Minor bugfixes (testing):
5197 - Fix Raspbian build issues related to missing socket errno in
5198 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
5200 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
5201 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
5202 - Use bash in src/test/test-network.sh. This ensures we reliably
5203 call chutney's newer tools/test-network.sh when available. Fixes
5204 bug 21562; bugfix on 0.2.9.1-alpha.
5207 - Small fixes to the fuzzing documentation. Closes ticket 21472.
5210 Changes in version 0.2.9.10 - 2017-03-01
5211 Tor 0.2.9.10 backports a security fix from later Tor release. It also
5212 includes fixes for some major issues affecting directory authorities,
5213 LibreSSL compatibility, and IPv6 correctness.
5215 The Tor 0.2.9.x release series is now marked as a long-term-support
5216 series. We intend to backport security fixes to 0.2.9.x until at
5217 least January of 2020.
5219 o Major bugfixes (directory authority, 0.3.0.3-alpha):
5220 - During voting, when marking a relay as a probable sybil, do not
5221 clear its BadExit flag: sybils can still be bad in other ways
5222 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5225 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
5226 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5227 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5228 exit policy rejects that port on more than an IPv6 /16 of
5229 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5230 which rejected a relay's own IPv6 address by default. Fixes bug
5231 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5233 o Major bugfixes (parsing, also in 0.3.0.4-rc):
5234 - Fix an integer underflow bug when comparing malformed Tor
5235 versions. This bug could crash Tor when built with
5236 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5237 0.2.9.8, which were built with -ftrapv by default. In other cases
5238 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5239 on 0.0.8pre1. Found by OSS-Fuzz.
5241 o Minor features (directory authorities, also in 0.3.0.4-rc):
5242 - Directory authorities now reject descriptors that claim to be
5243 malformed versions of Tor. Helps prevent exploitation of
5245 - Reject version numbers with components that exceed INT32_MAX.
5246 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5247 Fixes bug 21450; bugfix on 0.0.8pre1.
5249 o Minor features (geoip):
5250 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5253 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
5254 - Autoconf now checks to determine if OpenSSL structures are opaque,
5255 instead of explicitly checking for OpenSSL version numbers. Part
5257 - Support building with recent LibreSSL code that uses opaque
5258 structures. Closes ticket 21359.
5260 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
5261 - Repair a couple of (unreachable or harmless) cases of the risky
5262 comparison-by-subtraction pattern that caused bug 21278.
5264 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
5265 - The tor-resolve command line tool now rejects hostnames over 255
5266 characters in length. Previously, it would silently truncate them,
5267 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5268 Patch by "junglefowl".
5271 Changes in version 0.3.0.3-alpha - 2017-02-03
5272 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
5273 0.3.0.x development series, including some that could cause
5274 authorities to behave badly. There is also a fix for a longstanding
5275 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
5276 includes some smaller features and bugfixes.
5278 The Tor 0.3.0.x release series is now in patch-freeze: no additional
5279 features will be considered for inclusion in 0.3.0.x. We suspect that
5280 some bugs will probably remain, however, and we encourage people to
5283 o Major bugfixes (directory authority):
5284 - During voting, when marking a relay as a probable sybil, do not
5285 clear its BadExit flag: sybils can still be bad in other ways
5286 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5288 - When deciding whether we have just found a router to be reachable,
5289 do not penalize it for not having performed an Ed25519 link
5290 handshake if it does not claim to support an Ed25519 handshake.
5291 Previously, we would treat such relays as non-running. Fixes bug
5292 21107; bugfix on 0.3.0.1-alpha.
5294 o Major bugfixes (entry guards):
5295 - Stop trying to build circuits through entry guards for which we
5296 have no descriptor. Also, stop crashing in the case that we *do*
5297 accidentally try to build a circuit in such a state. Fixes bug
5298 21242; bugfix on 0.3.0.1-alpha.
5300 o Major bugfixes (IPv6 Exits):
5301 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5302 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5303 exit policy rejects that port on more than an IPv6 /16 of
5304 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5305 which rejected a relay's own IPv6 address by default. Fixes bug
5306 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5308 o Minor feature (client):
5309 - Enable IPv6 traffic on the SocksPort by default. To disable this,
5310 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
5312 o Minor feature (fallback scripts):
5313 - Add a check_existing mode to updateFallbackDirs.py, which checks
5314 if fallbacks in the hard-coded list are working. Closes ticket
5315 20174. Patch by haxxpop.
5317 o Minor features (ciphersuite selection):
5318 - Clients now advertise a list of ciphersuites closer to the ones
5319 preferred by Firefox. Closes part of ticket 15426.
5320 - Allow relays to accept a wider range of ciphersuites, including
5321 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
5323 o Minor features (controller, configuration):
5324 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
5325 and so on, now comes with a __*Port variant that will not be saved
5326 to the torrc file by the controller's SAVECONF command. This
5327 change allows TorBrowser to set up a single-use domain socket for
5328 each time it launches Tor. Closes ticket 20956.
5329 - The GETCONF command can now query options that may only be
5330 meaningful in context-sensitive lists. This allows the controller
5331 to query the mixed SocksPort/__SocksPort style options introduced
5332 in feature 20956. Implements ticket 21300.
5334 o Minor features (portability, compilation):
5335 - Autoconf now checks to determine if OpenSSL structures are opaque,
5336 instead of explicitly checking for OpenSSL version numbers. Part
5338 - Support building with recent LibreSSL code that uses opaque
5339 structures. Closes ticket 21359.
5341 o Minor features (relay):
5342 - We now allow separation of exit and relay traffic to different
5343 source IP addresses, using the OutboundBindAddressExit and
5344 OutboundBindAddressOR options respectively. Closes ticket 17975.
5345 Written by Michael Sonntag.
5347 o Minor bugfix (logging):
5348 - Don't recommend the use of Tor2web in non-anonymous mode.
5349 Recommending Tor2web is a bad idea because the client loses all
5350 anonymity. Tor2web should only be used in specific cases by users
5351 who *know* and understand the issues. Fixes bug 21294; bugfix
5354 o Minor bugfixes (client):
5355 - Always recover from failures in extend_info_from_node(), in an
5356 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
5357 bugfix on 0.2.3.1-alpha.
5359 o Minor bugfixes (client, entry guards):
5360 - Fix a bug warning (with backtrace) when we fail a channel that
5361 circuits to fallback directories on it. Fixes bug 21128; bugfix
5363 - Fix a spurious bug warning (with backtrace) when removing an
5364 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
5365 - Fix a bug of the new guard algorithm where tor could stall for up
5366 to 10 minutes before retrying a guard after a long period of no
5367 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
5368 - Do not try to build circuits until we have descriptors for our
5369 primary entry guards. Related to fix for bug 21242.
5371 o Minor bugfixes (configure, autoconf):
5372 - Rename the configure option --enable-expensive-hardening to
5373 --enable-fragile-hardening. Expensive hardening makes the tor
5374 daemon abort when some kinds of issues are detected. Thus, it
5375 makes tor more at risk of remote crashes but safer against RCE or
5376 heartbleed bug category. We now try to explain this issue in a
5377 message from the configure script. Fixes bug 21290; bugfix
5380 o Minor bugfixes (controller):
5381 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
5382 20824; bugfix on 0.3.0.1-alpha.
5384 o Minor bugfixes (hidden service):
5385 - Clean up the code for expiring intro points with no associated
5386 circuits. It was causing, rarely, a service with some expiring
5387 introduction points to not open enough additional introduction
5388 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
5389 - Stop setting the torrc option HiddenServiceStatistics to "0" just
5390 because we're not a bridge or relay. Instead, we preserve whatever
5391 value the user set (or didn't set). Fixes bug 21150; bugfix
5393 - Resolve two possible underflows which could lead to creating and
5394 closing a lot of introduction point circuits in a non-stop loop.
5395 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
5397 o Minor bugfixes (portability):
5398 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
5399 It is supported by OpenBSD itself, and also by most OpenBSD
5400 variants (such as Bitrig). Fixes bug 20980; bugfix
5402 - When mapping a file of length greater than SIZE_MAX, do not
5403 silently truncate its contents. This issue could occur on 32 bit
5404 systems with large file support and files which are larger than 4
5405 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
5407 o Minor bugfixes (tor-resolve):
5408 - The tor-resolve command line tool now rejects hostnames over 255
5409 characters in length. Previously, it would silently truncate them,
5410 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5411 Patch by "junglefowl".
5413 o Minor bugfixes (Windows services):
5414 - Be sure to initialize the monotonic time subsystem before using
5415 it, even when running as an NT service. Fixes bug 21356; bugfix
5419 Changes in version 0.3.0.2-alpha - 2017-01-23
5420 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
5421 cause relays and clients to crash, even if they were not built with
5422 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5423 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5424 version should upgrade.
5426 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
5427 time-to-live values, makes directory authorities enforce the 1-to-1
5428 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
5429 client-side onion service reachability bug, does better at selecting
5430 the set of fallback directories, and more.
5432 o Major bugfixes (security, also in 0.2.9.9):
5433 - Downgrade the "-ftrapv" option from "always on" to "only on when
5434 --enable-expensive-hardening is provided." This hardening option, like
5435 others, can turn survivable bugs into crashes--and having it on by
5436 default made a (relatively harmless) integer overflow bug into a
5437 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
5440 o Major features (security):
5441 - Change the algorithm used to decide DNS TTLs on client and server
5442 side, to better resist DNS-based correlation attacks like the
5443 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
5444 Feamster. Now relays only return one of two possible DNS TTL
5445 values, and clients are willing to believe DNS TTL values up to 3
5446 hours long. Closes ticket 19769.
5448 o Major features (directory authority, security):
5449 - The default for AuthDirPinKeys is now 1: directory authorities
5450 will reject relays where the RSA identity key matches a previously
5451 seen value, but the Ed25519 key has changed. Closes ticket 18319.
5453 o Major bugfixes (client, guard, crash):
5454 - In circuit_get_global_origin_list(), return the actual list of
5455 origin circuits. The previous version of this code returned the
5456 list of all the circuits, and could have caused strange bugs,
5457 including possible crashes. Fixes bug 21118; bugfix
5460 o Major bugfixes (client, onion service, also in 0.2.9.9):
5461 - Fix a client-side onion service reachability bug, where multiple
5462 socks requests to an onion service (or a single slow request)
5463 could cause us to mistakenly mark some of the service's
5464 introduction points as failed, and we cache that failure so
5465 eventually we run out and can't reach the service. Also resolves a
5466 mysterious "Remote server sent bogus reason code 65021" log
5467 warning. The bug was introduced in ticket 17218, where we tried to
5468 remember the circuit end reason as a uint16_t, which mangled
5469 negative values. Partially fixes bug 21056 and fixes bug 20307;
5470 bugfix on 0.2.8.1-alpha.
5472 o Major bugfixes (DNS):
5473 - Fix a bug that prevented exit nodes from caching DNS records for
5474 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
5476 o Minor features (controller):
5477 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
5478 shared-random values to the controller. Closes ticket 19925.
5480 o Minor features (entry guards):
5481 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
5482 break regression tests.
5483 - Require UseEntryGuards when UseBridges is set, in order to make
5484 sure bridges aren't bypassed. Resolves ticket 20502.
5486 o Minor features (fallback directories):
5487 - Select 200 fallback directories for each release. Closes
5489 - Allow 3 fallback relays per operator, which is safe now that we
5490 are choosing 200 fallback relays. Closes ticket 20912.
5491 - Exclude relays affected by bug 20499 from the fallback list.
5492 Exclude relays from the fallback list if they are running versions
5493 known to be affected by bug 20499, or if in our tests they deliver
5494 a stale consensus (i.e. one that expired more than 24 hours ago).
5495 Closes ticket 20539.
5496 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
5498 - Require fallback directories to have the same address and port for
5499 7 days (now that we have enough relays with this stability).
5500 Relays whose OnionOO stability timer is reset on restart by bug
5501 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
5502 this issue. Closes ticket 20880; maintains short-term fix
5504 - Require fallbacks to have flags for 90% of the time (weighted
5505 decaying average), rather than 95%. This allows at least 73% of
5506 clients to bootstrap in the first 5 seconds without contacting an
5507 authority. Part of ticket 18828.
5508 - Annotate updateFallbackDirs.py with the bandwidth and consensus
5509 weight for each candidate fallback. Closes ticket 20878.
5510 - Make it easier to change the output sort order of fallbacks.
5511 Closes ticket 20822.
5512 - Display the relay fingerprint when downloading consensuses from
5513 fallbacks. Closes ticket 20908.
5515 o Minor features (geoip, also in 0.2.9.9):
5516 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5519 o Minor features (next-gen onion service directories):
5520 - Remove the "EnableOnionServicesV3" consensus parameter that we
5521 introduced in 0.3.0.1-alpha: relays are now always willing to act
5522 as v3 onion service directories. Resolves ticket 19899.
5524 o Minor features (linting):
5525 - Enhance the changes file linter to warn on Tor versions that are
5526 prefixed with "tor-". Closes ticket 21096.
5528 o Minor features (logging):
5529 - In several places, describe unset ed25519 keys as "<unset>",
5530 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
5532 o Minor bugfix (control protocol):
5533 - The reply to a "GETINFO config/names" request via the control
5534 protocol now spells the type "Dependent" correctly. This is a
5535 breaking change in the control protocol. (The field seems to be
5536 ignored by the most common known controllers.) Fixes bug 18146;
5537 bugfix on 0.1.1.4-alpha.
5539 o Minor bugfixes (bug resilience):
5540 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
5541 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
5542 Hans Jerry Illikainen.
5544 o Minor bugfixes (build):
5545 - Replace obsolete Autoconf macros with their modern equivalent and
5546 prevent similar issues in the future. Fixes bug 20990; bugfix
5549 o Minor bugfixes (client, guards):
5550 - Fix bug where Tor would think that there are circuits waiting for
5551 better guards even though those circuits have been freed. Fixes
5552 bug 21142; bugfix on 0.3.0.1-alpha.
5554 o Minor bugfixes (config):
5555 - Don't assert on startup when trying to get the options list and
5556 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
5557 options so of course they aren't ready yet. Fixes bug 21062;
5558 bugfix on 0.2.9.3-alpha.
5560 o Minor bugfixes (controller):
5561 - Make the GETINFO interface for inquiring about entry guards
5562 support the new guards backend. Fixes bug 20823; bugfix
5565 o Minor bugfixes (dead code):
5566 - Remove a redundant check for PidFile changes at runtime in
5567 options_transition_allowed(): this check is already performed
5568 regardless of whether the sandbox is active. Fixes bug 21123;
5569 bugfix on 0.2.5.4-alpha.
5571 o Minor bugfixes (documentation):
5572 - Update the tor manual page to document every option that can not
5573 be changed while tor is running. Fixes bug 21122.
5575 o Minor bugfixes (fallback directories):
5576 - Stop failing when a relay has no uptime data in
5577 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
5578 - Avoid checking fallback candidates' DirPorts if they are down in
5579 OnionOO. When a relay operator has multiple relays, this
5580 prioritizes relays that are up over relays that are down. Fixes
5581 bug 20926; bugfix on 0.2.8.3-alpha.
5582 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
5583 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
5585 o Minor bugfixes (guards, bootstrapping):
5586 - When connecting to a directory guard during bootstrap, do not mark
5587 the guard as successful until we receive a good-looking directory
5588 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
5590 o Minor bugfixes (onion services):
5591 - Fix the config reload pruning of old vs new services so it
5592 actually works when both ephemeral and non-ephemeral services are
5593 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
5594 - Allow the number of introduction points to be as low as 0, rather
5595 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
5597 o Minor bugfixes (IPv6):
5598 - Make IPv6-using clients try harder to find an IPv6 directory
5599 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
5600 - When IPv6 addresses have not been downloaded yet (microdesc
5601 consensus documents don't list relay IPv6 addresses), use hard-
5602 coded addresses for authorities, fallbacks, and configured
5603 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
5604 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
5606 o Minor bugfixes (memory leaks):
5607 - Fix a memory leak when configuring hidden services. Fixes bug
5608 20987; bugfix on 0.3.0.1-alpha.
5610 o Minor bugfixes (portability, also in 0.2.9.9):
5611 - Avoid crashing when Tor is built using headers that contain
5612 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5613 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5615 - Fix Libevent detection on platforms without Libevent 1 headers
5616 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5618 o Minor bugfixes (relay):
5619 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
5620 initializing the keys would reset the DataDirectory to 0700
5621 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
5622 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
5624 o Minor bugfixes (testing):
5625 - Remove undefined behavior from the backtrace generator by removing
5626 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
5628 o Minor bugfixes (unit tests):
5629 - Allow the unit tests to pass even when DNS lookups of bogus
5630 addresses do not fail as expected. Fixes bug 20862 and 20863;
5631 bugfix on unit tests introduced in 0.2.8.1-alpha
5632 through 0.2.9.4-alpha.
5634 o Code simplification and refactoring:
5635 - Refactor code to manipulate global_origin_circuit_list into
5636 separate functions. Closes ticket 20921.
5638 o Documentation (formatting):
5639 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
5640 blocks were incorrectly appearing. Closes ticket 20885.
5642 o Documentation (man page):
5643 - Clarify many options in tor.1 and add some min/max values for
5644 HiddenService options. Closes ticket 21058.
5647 Changes in version 0.2.9.9 - 2017-01-23
5648 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
5649 cause relays and clients to crash, even if they were not built with
5650 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5651 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5652 version should upgrade.
5654 This release also resolves a client-side onion service reachability
5655 bug, and resolves a pair of small portability issues.
5657 o Major bugfixes (security):
5658 - Downgrade the "-ftrapv" option from "always on" to "only on when
5659 --enable-expensive-hardening is provided." This hardening option,
5660 like others, can turn survivable bugs into crashes -- and having
5661 it on by default made a (relatively harmless) integer overflow bug
5662 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
5663 bugfix on 0.2.9.1-alpha.
5665 o Major bugfixes (client, onion service):
5666 - Fix a client-side onion service reachability bug, where multiple
5667 socks requests to an onion service (or a single slow request)
5668 could cause us to mistakenly mark some of the service's
5669 introduction points as failed, and we cache that failure so
5670 eventually we run out and can't reach the service. Also resolves a
5671 mysterious "Remote server sent bogus reason code 65021" log
5672 warning. The bug was introduced in ticket 17218, where we tried to
5673 remember the circuit end reason as a uint16_t, which mangled
5674 negative values. Partially fixes bug 21056 and fixes bug 20307;
5675 bugfix on 0.2.8.1-alpha.
5677 o Minor features (geoip):
5678 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5681 o Minor bugfixes (portability):
5682 - Avoid crashing when Tor is built using headers that contain
5683 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5684 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5686 - Fix Libevent detection on platforms without Libevent 1 headers
5687 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5690 Changes in version 0.3.0.1-alpha - 2016-12-19
5691 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
5692 series. It strengthens Tor's link and circuit handshakes by
5693 identifying relays by their Ed25519 keys, improves the algorithm that
5694 clients use to choose and maintain their list of guards, and includes
5695 additional backend support for the next-generation hidden service
5696 design. It also contains numerous other small features and
5697 improvements to security, correctness, and performance.
5699 Below are the changes since 0.2.9.8.
5701 o Major features (guard selection algorithm):
5702 - Tor's guard selection algorithm has been redesigned from the
5703 ground up, to better support unreliable networks and restrictive
5704 sets of entry nodes, and to better resist guard-capture attacks by
5705 hostile local networks. Implements proposal 271; closes
5708 o Major features (next-generation hidden services):
5709 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
5710 prop224 aka "Next Generation Hidden Services". Service and clients
5711 don't use this functionality yet. Closes ticket 19043. Based on
5712 initial code by Alec Heifetz.
5713 - Relays now support the HSDir version 3 protocol, so that they can
5714 can store and serve v3 descriptors. This is part of the next-
5715 generation onion service work detailed in proposal 224. Closes
5718 o Major features (protocol, ed25519 identity keys):
5719 - Relays now use Ed25519 to prove their Ed25519 identities and to
5720 one another, and to clients. This algorithm is faster and more
5721 secure than the RSA-based handshake we've been doing until now.
5722 Implements the second big part of proposal 220; Closes
5724 - Clients now support including Ed25519 identity keys in the EXTEND2
5725 cells they generate. By default, this is controlled by a consensus
5726 parameter, currently disabled. You can turn this feature on for
5727 testing by setting ExtendByEd25519ID in your configuration. This
5728 might make your traffic appear different than the traffic
5729 generated by other users, however. Implements part of ticket
5730 15056; part of proposal 220.
5731 - Relays now understand requests to extend to other relays by their
5732 Ed25519 identity keys. When an Ed25519 identity key is included in
5733 an EXTEND2 cell, the relay will only extend the circuit if the
5734 other relay can prove ownership of that identity. Implements part
5735 of ticket 15056; part of proposal 220.
5737 o Major bugfixes (scheduler):
5738 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
5739 caused the channel scheduler to behave more or less randomly,
5740 rather than preferring channels with higher-priority circuits.
5741 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
5743 o Minor features (controller):
5744 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
5745 rather than "unrecognized." Closes ticket 20389; patch from
5748 o Minor features (diagnostic, directory client):
5749 - Warn when we find an unexpected inconsistency in directory
5750 download status objects. Prevents some negative consequences of
5753 o Minor features (directory authority):
5754 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
5755 default) to control whether authorities should try to probe relays
5756 by their Ed25519 link keys. This option will go away in a few
5757 releases--unless we encounter major trouble in our ed25519 link
5758 protocol rollout, in which case it will serve as a safety option.
5760 o Minor features (directory cache):
5761 - Relays and bridges will now refuse to serve the consensus they
5762 have if they know it is too old for a client to use. Closes
5765 o Minor features (ed25519 link handshake):
5766 - Advertise support for the ed25519 link handshake using the
5767 subprotocol-versions mechanism, so that clients can tell which
5768 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
5770 o Minor features (fingerprinting resistance, authentication):
5771 - Extend the length of RSA keys used for TLS link authentication to
5772 2048 bits. (These weren't used for forward secrecy; for forward
5773 secrecy, we used P256.) Closes ticket 13752.
5775 o Minor features (infrastructure):
5776 - Implement smartlist_add_strdup() function. Replaces the use of
5777 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
5779 o Minor bugfixes (client):
5780 - When clients that use bridges start up with a cached consensus on
5781 disk, they were ignoring it and downloading a new one. Now they
5782 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
5784 o Minor bugfixes (configuration):
5785 - Accept non-space whitespace characters after the severity level in
5786 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
5787 - Support "TByte" and "TBytes" units in options given in bytes.
5788 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
5789 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
5791 o Minor bugfixes (consensus weight):
5792 - Add new consensus method that initializes bw weights to 1 instead
5793 of 0. This prevents a zero weight from making it all the way to
5794 the end (happens in small testing networks) and causing an error.
5795 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
5797 o Minor bugfixes (descriptors):
5798 - Correctly recognise downloaded full descriptors as valid, even
5799 when using microdescriptors as circuits. This affects clients with
5800 FetchUselessDescriptors set, and may affect directory authorities.
5801 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
5803 o Minor bugfixes (directory system):
5804 - Download all consensus flavors, descriptors, and authority
5805 certificates when FetchUselessDescriptors is set, regardless of
5806 whether tor is a directory cache or not. Fixes bug 20667; bugfix
5807 on all recent tor versions.
5808 - Bridges and relays now use microdescriptors (like clients do)
5809 rather than old-style router descriptors. Now bridges will blend
5810 in with clients in terms of the circuits they build. Fixes bug
5811 6769; bugfix on 0.2.3.2-alpha.
5813 o Minor bugfixes (ed25519 certificates):
5814 - Correctly interpret ed25519 certificates that would expire some
5815 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
5817 o Minor bugfixes (hidden services):
5818 - Stop ignoring misconfigured hidden services. Instead, refuse to
5819 start tor until the misconfigurations have been corrected. Fixes
5820 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
5823 o Minor bugfixes (memory leak at exit):
5824 - Fix a small harmless memory leak at exit of the previously unused
5825 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
5828 o Minor bugfixes (util):
5829 - When finishing writing a file to disk, if we were about to replace
5830 the file with the temporary file created before and we fail to
5831 replace it, remove the temporary file so it doesn't stay on disk.
5832 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
5834 o Minor bugfixes (Windows):
5835 - Check for getpagesize before using it to mmap files. This fixes
5836 compilation in some MinGW environments. Fixes bug 20530; bugfix on
5837 0.1.2.1-alpha. Reported by "ice".
5839 o Code simplification and refactoring:
5840 - Abolish all global guard context in entrynodes.c; replace with new
5841 guard_selection_t structure as preparation for proposal 271.
5842 Closes ticket 19858.
5843 - Introduce rend_service_is_ephemeral() that tells if given onion
5844 service is ephemeral. Replace unclear NULL-checkings for service
5845 directory with this function. Closes ticket 20526.
5846 - Extract magic numbers in circuituse.c into defined variables.
5847 - Refactor circuit_is_available_for_use to remove unnecessary check.
5848 - Refactor circuit_predict_and_launch_new for readability and
5849 testability. Closes ticket 18873.
5850 - Refactor large if statement in purpose_needs_anonymity to use
5851 switch statement instead. Closes part of ticket 20077.
5852 - Refactor the hashing API to return negative values for errors, as
5853 is done as throughout the codebase. Closes ticket 20717.
5854 - Remove data structures that were used to index or_connection
5855 objects by their RSA identity digests. These structures are fully
5856 redundant with the similar structures used in the
5857 channel abstraction.
5858 - Remove duplicate code in the channel_write_*cell() functions.
5859 Closes ticket 13827; patch from Pingl.
5860 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
5861 use only purpose_needs_anonymity. Closes part of ticket 20077.
5862 - The code to generate and parse EXTEND and EXTEND2 cells has been
5863 replaced with code automatically generated by the
5867 - Include the "TBits" unit in Tor's man page. Fixes part of bug
5868 20622; bugfix on tor-0.2.5.1-alpha.
5869 - Change '1' to 'weight_scale' in consensus bw weights calculation
5870 comments, as that is reality. Closes ticket 20273. Patch
5872 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
5873 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
5874 on tor-0.2.5.6-alpha.
5875 - Stop the man page from incorrectly stating that HiddenServiceDir
5876 must already exist. Fixes 20486.
5877 - Clarify that when ClientRejectInternalAddresses is enabled (which
5878 is the default), multicast DNS hostnames for machines on the local
5879 network (of the form *.local) are also rejected. Closes
5883 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
5884 limit for relays running on a single IP applies to authority IP
5885 addresses as well as to non-authority IP addresses. Closes
5887 - The UseDirectoryGuards torrc option no longer exists: all users
5888 that use entry guards will also use directory guards. Related to
5889 proposal 271; implements part of ticket 20831.
5892 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
5893 from "overcaffeinated".
5894 - Perform the coding style checks when running the tests and fail
5895 when coding style violations are found. Closes ticket 5500.
5896 - Add tests for networkstatus_compute_bw_weights_v10.
5897 - Add unit tests circuit_predict_and_launch_new.
5898 - Extract dummy_origin_circuit_new so it can be used by other
5902 Changes in version 0.2.8.12 - 2016-12-19
5903 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
5904 below) where Tor clients could crash when attempting to visit a
5905 hostile hidden service. Clients are recommended to upgrade as packages
5906 become available for their systems.
5908 It also includes an updated list of fallback directories, backported
5911 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
5912 backported to 0.2.8 in the future.
5914 o Major bugfixes (parsing, security, backported from 0.2.9.8):
5915 - Fix a bug in parsing that could cause clients to read a single
5916 byte past the end of an allocated region. This bug could be used
5917 to cause hardened clients (built with --enable-expensive-hardening)
5918 to crash if they tried to visit a hostile hidden service. Non-
5919 hardened clients are only affected depending on the details of
5920 their platform's memory allocator. Fixes bug 21018; bugfix on
5921 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5922 2016-12-002 and as CVE-2016-1254.
5924 o Minor features (fallback directory list, backported from 0.2.9.8):
5925 - Replace the 81 remaining fallbacks of the 100 originally
5926 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5927 fallbacks (123 new, 54 existing, 27 removed) generated in December
5928 2016. Resolves ticket 20170.
5930 o Minor features (geoip, backported from 0.2.9.7-rc):
5931 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
5935 Changes in version 0.2.9.8 - 2016-12-19
5936 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
5938 The Tor 0.2.9 series makes mandatory a number of security features
5939 that were formerly optional. It includes support for a new shared-
5940 randomness protocol that will form the basis for next generation
5941 hidden services, includes a single-hop hidden service mode for
5942 optimizing .onion services that don't actually want to be hidden,
5943 tries harder not to overload the directory authorities with excessive
5944 downloads, and supports a better protocol versioning scheme for
5945 improved compatibility with other implementations of the Tor protocol.
5947 And of course, there are numerous other bugfixes and improvements.
5949 This release also includes a fix for a medium-severity issue (bug
5950 21018 below) where Tor clients could crash when attempting to visit a
5951 hostile hidden service. Clients are recommended to upgrade as packages
5952 become available for their systems.
5954 Below are the changes since 0.2.9.7-rc. For a list of all changes
5955 since 0.2.8, see the ReleaseNotes file.
5957 o Major bugfixes (parsing, security):
5958 - Fix a bug in parsing that could cause clients to read a single
5959 byte past the end of an allocated region. This bug could be used
5960 to cause hardened clients (built with --enable-expensive-hardening)
5961 to crash if they tried to visit a hostile hidden service. Non-
5962 hardened clients are only affected depending on the details of
5963 their platform's memory allocator. Fixes bug 21018; bugfix on
5964 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5965 2016-12-002 and as CVE-2016-1254.
5967 o Minor features (fallback directory list):
5968 - Replace the 81 remaining fallbacks of the 100 originally
5969 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5970 fallbacks (123 new, 54 existing, 27 removed) generated in December
5971 2016. Resolves ticket 20170.
5974 Changes in version 0.2.9.7-rc - 2016-12-12
5975 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
5976 including a few that had prevented tests from passing on
5979 o Minor features (geoip):
5980 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
5983 o Minor bugfix (build):
5984 - The current Git revision when building from a local repository is
5985 now detected correctly when using git worktrees. Fixes bug 20492;
5986 bugfix on 0.2.3.9-alpha.
5988 o Minor bugfixes (directory authority):
5989 - When computing old Tor protocol line version in protover, we were
5990 looking at 0.2.7.5 twice instead of a specific case for
5991 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
5993 o Minor bugfixes (download scheduling):
5994 - Resolve a "bug" warning when considering a download schedule whose
5995 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
5997 o Minor bugfixes (logging):
5998 - Downgrade a harmless log message about the
5999 pending_entry_connections list from "warn" to "info". Mitigates
6002 o Minor bugfixes (memory leak):
6003 - Fix a small memory leak when receiving AF_UNIX connections on a
6004 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
6005 - When moving a signed descriptor object from a source to an
6006 existing destination, free the allocated memory inside that
6007 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
6009 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
6010 - Fix a memory leak and use-after-free error when removing entries
6011 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
6012 0.2.5.5-alpha. Patch from "cypherpunks".
6014 o Minor bugfixes (portability):
6015 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
6016 Fixes bug 20935; bugfix on 0.2.9.6-rc.
6018 o Minor bugfixes (unit tests):
6019 - Stop expecting NetBSD unit tests to report success for ipfw. Part
6020 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
6021 - Fix tolerances in unit tests for monotonic time comparisons
6022 between nanoseconds and microseconds. Previously, we accepted a 10
6023 us difference only, which is not realistic on every platform's
6024 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
6025 - Remove a double-free in the single onion service unit test. Stop
6026 ignoring a return value. Make future changes less error-prone.
6027 Fixes bug 20864; bugfix on 0.2.9.6-rc.
6030 Changes in version 0.2.8.11 - 2016-12-08
6031 Tor 0.2.8.11 backports fixes for additional portability issues that
6032 could prevent Tor from building correctly on OSX Sierra, or with
6033 OpenSSL 1.1. Affected users should upgrade; others can safely stay
6036 o Minor bugfixes (portability):
6037 - Avoid compilation errors when building on OSX Sierra. Sierra began
6038 to support the getentropy() and clock_gettime() APIs, but created
6039 a few problems in doing so. Tor 0.2.9 has a more thorough set of
6040 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
6041 monotonic time interfaces. Fixes bug 20865. Bugfix
6044 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6045 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6046 architectures. Closes ticket 20588.
6049 Changes in version 0.2.8.10 - 2016-12-02
6050 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
6051 unusable after they left standby mode. It also backports fixes for
6052 a few portability issues and a small but problematic memory leak.
6054 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
6055 - When Tor leaves standby because of a new application request, open
6056 circuits as needed to serve that request. Previously, we would
6057 potentially wait a very long time. Fixes part of bug 19969; bugfix
6060 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
6061 - Clients now respond to new application stream requests immediately
6062 when they arrive, rather than waiting up to one second before
6063 starting to handle them. Fixes part of bug 19969; bugfix
6066 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
6067 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6068 successfully targeting earlier versions of OSX. Resolves
6071 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6072 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6073 20551; bugfix on 0.2.1.1-alpha.
6075 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
6076 - Work around a memory leak in OpenSSL 1.1 when encoding public
6077 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6079 o Minor features (geoip):
6080 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6083 Changes in version 0.2.9.6-rc - 2016-12-02
6084 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
6085 version. We hope that it will be ready to become stable soon, and we
6086 encourage everyone to test this release. If no showstopper bugs are
6087 found here, the next 0.2.9 release will be stable.
6089 o Major bugfixes (relay, resolver, logging):
6090 - For relays that don't know their own address, avoid attempting a
6091 local hostname resolve for each descriptor we download. This
6092 will cut down on the number of "Success: chose address 'x.x.x.x'"
6093 log lines, and also avoid confusing clock jumps if the resolver
6094 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
6096 o Minor bugfixes (client, fascistfirewall):
6097 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
6098 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
6100 o Minor bugfixes (hidden services):
6101 - Stop ignoring the anonymity status of saved keys for hidden
6102 services and single onion services when first starting tor.
6103 Instead, refuse to start tor if any hidden service key has been
6104 used in a different hidden service anonymity mode. Fixes bug
6105 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
6107 o Minor bugfixes (portability):
6108 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6109 successfully targeting earlier versions of OSX. Resolves
6111 - Run correctly when built on Windows build environments that
6112 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
6114 o Minor bugfixes (single onion services, Tor2web):
6115 - Stop complaining about long-term one-hop circuits deliberately
6116 created by single onion services and Tor2web. These log messages
6117 are intended to diagnose issue 8387, which relates to circuits
6118 hanging around forever for no reason. Fixes bug 20613; bugfix on
6119 0.2.9.1-alpha. Reported by "pastly".
6121 o Minor bugfixes (unit tests):
6122 - Stop spurious failures in the local interface address discovery
6123 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
6127 - Correct the minimum bandwidth value in torrc.sample, and queue a
6128 corresponding change for torrc.minimal. Closes ticket 20085.
6131 Changes in version 0.2.9.5-alpha - 2016-11-08
6132 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
6133 version. We believe one or two probably remain, and we encourage
6134 everyone to test this release.
6136 o Major bugfixes (client performance):
6137 - Clients now respond to new application stream requests immediately
6138 when they arrive, rather than waiting up to one second before
6139 starting to handle them. Fixes part of bug 19969; bugfix
6142 o Major bugfixes (client reliability):
6143 - When Tor leaves standby because of a new application request, open
6144 circuits as needed to serve that request. Previously, we would
6145 potentially wait a very long time. Fixes part of bug 19969; bugfix
6148 o Major bugfixes (download scheduling):
6149 - When using an exponential backoff schedule, do not give up on
6150 downloading just because we have failed a bunch of times. Since
6151 each delay is longer than the last, retrying indefinitely won't
6152 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
6153 - If a consensus expires while we are waiting for certificates to
6154 download, stop waiting for certificates.
6155 - If we stop waiting for certificates less than a minute after we
6156 started downloading them, do not consider the certificate download
6157 failure a separate failure. Fixes bug 20533; bugfix
6159 - Remove the maximum delay on exponential-backoff scheduling. Since
6160 we now allow an infinite number of failures (see ticket 20536), we
6161 must now allow the time to grow longer on each failure. Fixes part
6162 of bug 20534; bugfix on 0.2.9.1-alpha.
6163 - Make our initial download delays closer to those from 0.2.8. Fixes
6164 another part of bug 20534; bugfix on 0.2.9.1-alpha.
6165 - When determining when to download a directory object, handle times
6166 after 2038 if the operating system supports them. (Someday this
6167 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
6168 - When using exponential backoff in test networks, use a lower
6169 exponent, so the delays do not vary as much. This helps test
6170 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
6172 o Minor features (geoip):
6173 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6176 o Minor bugfixes (client directory scheduling):
6177 - Treat "relay too busy to answer request" as a failed request and a
6178 reason to back off on our retry frequency. This is safe now that
6179 exponential backoffs retry indefinitely, and avoids a bug where we
6180 would reset our download schedule erroneously. Fixes bug 20593;
6181 bugfix on 0.2.9.1-alpha.
6183 o Minor bugfixes (client, logging):
6184 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
6185 assume all nodes support EXTEND2. Use ntor whenever a key is
6186 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
6187 - On DNSPort, stop logging a BUG warning on a failed hostname
6188 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
6190 o Minor bugfixes (hidden services):
6191 - When configuring hidden services, check every hidden service
6192 directory's permissions. Previously, we only checked the last
6193 hidden service. Fixes bug 20529; bugfix the work to fix 13942
6196 o Minor bugfixes (portability):
6197 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6198 architectures. Closes ticket 20588.
6199 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
6200 removed the ECDH ciphers which caused the tests to fail on
6201 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
6202 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6203 20551; bugfix on 0.2.1.1-alpha.
6205 o Minor bugfixes (relay bootstrap):
6206 - Ensure relays don't make multiple connections during bootstrap.
6207 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
6209 o Minor bugfixes (relay):
6210 - Work around a memory leak in OpenSSL 1.1 when encoding public
6211 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6212 - Avoid a small memory leak when informing worker threads about
6213 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
6214 - Do not try to parallelize workers more than 16x without the user
6215 explicitly configuring us to do so, even if we do detect more than
6216 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6218 o Minor bugfixes (single onion services):
6219 - Start correctly when creating a single onion service in a
6220 directory that did not previously exist. Fixes bug 20484; bugfix
6223 o Minor bugfixes (testing):
6224 - Avoid a unit test failure on systems with over 16 detectable CPU
6225 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6228 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
6229 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
6230 - Module-level documentation for several more modules. Closes
6231 tickets 19287 and 19290.
6234 Changes in version 0.2.8.9 - 2016-10-17
6235 Tor 0.2.8.9 backports a fix for a security hole in previous versions
6236 of Tor that would allow a remote attacker to crash a Tor client,
6237 hidden service, relay, or authority. All Tor users should upgrade to
6238 this version, or to 0.2.9.4-alpha. Patches will be released for older
6241 o Major features (security fixes, also in 0.2.9.4-alpha):
6242 - Prevent a class of security bugs caused by treating the contents
6243 of a buffer chunk as if they were a NUL-terminated string. At
6244 least one such bug seems to be present in all currently used
6245 versions of Tor, and would allow an attacker to remotely crash
6246 most Tor instances, especially those compiled with extra compiler
6247 hardening. With this defense in place, such bugs can't crash Tor,
6248 though we should still fix them as they occur. Closes ticket
6249 20384 (TROVE-2016-10-001).
6251 o Minor features (geoip):
6252 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6256 Changes in version 0.2.9.4-alpha - 2016-10-17
6257 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
6258 that would allow a remote attacker to crash a Tor client, hidden
6259 service, relay, or authority. All Tor users should upgrade to this
6260 version, or to 0.2.8.9. Patches will be released for older versions
6263 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
6264 previous versions of Tor, including the implementation of a feature to
6265 future- proof the Tor ecosystem against protocol changes, some bug
6266 fixes necessary for Tor Browser to use unix domain sockets correctly,
6267 and several portability improvements. We anticipate that this will be
6268 the last alpha in the Tor 0.2.9 series, and that the next release will
6269 be a release candidate.
6271 o Major features (security fixes):
6272 - Prevent a class of security bugs caused by treating the contents
6273 of a buffer chunk as if they were a NUL-terminated string. At
6274 least one such bug seems to be present in all currently used
6275 versions of Tor, and would allow an attacker to remotely crash
6276 most Tor instances, especially those compiled with extra compiler
6277 hardening. With this defense in place, such bugs can't crash Tor,
6278 though we should still fix them as they occur. Closes ticket
6279 20384 (TROVE-2016-10-001).
6281 o Major features (subprotocol versions):
6282 - Tor directory authorities now vote on a set of recommended
6283 subprotocol versions, and on a set of required subprotocol
6284 versions. Clients and relays that lack support for a _required_
6285 subprotocol version will not start; those that lack support for a
6286 _recommended_ subprotocol version will warn the user to upgrade.
6287 Closes ticket 19958; implements part of proposal 264.
6288 - Tor now uses "subprotocol versions" to indicate compatibility.
6289 Previously, versions of Tor looked at the declared Tor version of
6290 a relay to tell whether they could use a given feature. Now, they
6291 should be able to rely on its declared subprotocol versions. This
6292 change allows compatible implementations of the Tor protocol(s) to
6293 exist without pretending to be 100% bug-compatible with particular
6294 releases of Tor itself. Closes ticket 19958; implements part of
6297 o Minor feature (fallback directories):
6298 - Remove broken fallbacks from the hard-coded fallback directory
6299 list. Closes ticket 20190; patch by teor.
6301 o Minor features (client, directory):
6302 - Since authorities now omit all routers that lack the Running and
6303 Valid flags, we assume that any relay listed in the consensus must
6304 have those flags. Closes ticket 20001; implements part of
6307 o Minor features (compilation, portability):
6308 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
6311 o Minor features (development tools, etags):
6312 - Teach the "make tags" Makefile target how to correctly find
6313 "MOCK_IMPL" function definitions. Patch from nherring; closes
6316 o Minor features (geoip):
6317 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6320 o Minor features (unix domain sockets):
6321 - When configuring a unix domain socket for a SocksPort,
6322 ControlPort, or Hidden service, you can now wrap the address in
6323 quotes, using C-style escapes inside the quotes. This allows unix
6324 domain socket paths to contain spaces.
6326 o Minor features (virtual addresses):
6327 - Increase the maximum number of bits for the IPv6 virtual network
6328 prefix from 16 to 104. In this way, the condition for address
6329 allocation is less restrictive. Closes ticket 20151; feature
6332 o Minor bugfixes (address discovery):
6333 - Stop reordering IP addresses returned by the OS. This makes it
6334 more likely that Tor will guess the same relay IP address every
6335 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
6336 Reported by René Mayrhofer, patch by "cypherpunks".
6338 o Minor bugfixes (client, unix domain sockets):
6339 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
6340 the client address is meaningless. Fixes bug 20261; bugfix
6343 o Minor bugfixes (compilation, OpenBSD):
6344 - Detect Libevent2 functions correctly on systems that provide
6345 libevent2, but where libevent1 is linked with -levent. Fixes bug
6346 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
6348 o Minor bugfixes (configuration):
6349 - When parsing quoted configuration values from the torrc file,
6350 handle windows line endings correctly. Fixes bug 19167; bugfix on
6351 0.2.0.16-alpha. Patch from "Pingl".
6353 o Minor bugfixes (getpass):
6354 - Defensively fix a non-triggerable heap corruption at do_getpass()
6355 to protect ourselves from mistakes in the future. Fixes bug
6356 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
6359 o Minor bugfixes (hidden service):
6360 - Allow hidden services to run on IPv6 addresses even when the
6361 IPv6Exit option is not set. Fixes bug 18357; bugfix
6365 - Add module-level internal documentation for 36 C files that
6366 previously didn't have a high-level overview. Closes ticket #20385.
6368 o Required libraries:
6369 - When building with OpenSSL, Tor now requires version 1.0.1 or
6370 later. OpenSSL 1.0.0 and earlier are no longer supported by the
6371 OpenSSL team, and should not be used. Closes ticket 20303.
6374 Changes in version 0.2.9.3-alpha - 2016-09-23
6375 Tor 0.2.9.3-alpha adds improved support for entities that want to make
6376 high-performance services available through the Tor .onion mechanism
6377 without themselves receiving anonymity as they host those services. It
6378 also tries harder to ensure that all steps on a circuit are using the
6379 strongest crypto possible, strengthens some TLS properties, and
6380 resolves several bugs -- including a pair of crash bugs from the 0.2.8
6381 series. Anybody running an earlier version of 0.2.9.x should upgrade.
6383 o Major bugfixes (crash, also in 0.2.8.8):
6384 - Fix a complicated crash bug that could affect Tor clients
6385 configured to use bridges when replacing a networkstatus consensus
6386 in which one of their bridges was mentioned. OpenBSD users saw
6387 more crashes here, but all platforms were potentially affected.
6388 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
6390 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
6391 - Fix a timing-dependent assertion failure that could occur when we
6392 tried to flush from a circuit after having freed its cells because
6393 of an out-of-memory condition. Fixes bug 20203; bugfix on
6394 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
6397 o Major features (circuit building, security):
6398 - Authorities, relays and clients now require ntor keys in all
6399 descriptors, for all hops (except for rare hidden service protocol
6400 cases), for all circuits, and for all other roles. Part of
6402 - Tor authorities, relays, and clients only use ntor, except for
6403 rare cases in the hidden service protocol. Part of ticket 19163.
6405 o Major features (single-hop "hidden" services):
6406 - Add experimental HiddenServiceSingleHopMode and
6407 HiddenServiceNonAnonymousMode options. When both are set to 1,
6408 every hidden service on a Tor instance becomes a non-anonymous
6409 Single Onion Service. Single Onions make one-hop (direct)
6410 connections to their introduction and renzedvous points. One-hop
6411 circuits make Single Onion servers easily locatable, but clients
6412 remain location-anonymous. This is compatible with the existing
6413 hidden service implementation, and works on the current tor
6414 network without any changes to older relays or clients. Implements
6415 proposal 260, completes ticket 17178. Patch by teor and asn.
6417 o Major features (resource management):
6418 - Tor can now notice it is about to run out of sockets, and
6419 preemptively close connections of lower priority. (This feature is
6420 off by default for now, since the current prioritizing method is
6421 yet not mature enough. You can enable it by setting
6422 "DisableOOSCheck 0", but watch out: it might close some sockets
6423 you would rather have it keep.) Closes ticket 18640.
6425 o Major bugfixes (circuit building):
6426 - Hidden service client-to-intro-point and service-to-rendezvous-
6427 point circuits use the TAP key supplied by the protocol, to avoid
6428 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
6430 o Major bugfixes (compilation, OpenBSD):
6431 - Fix a Libevent-detection bug in our autoconf script that would
6432 prevent Tor from linking successfully on OpenBSD. Patch from
6433 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
6435 o Major bugfixes (hidden services):
6436 - Clients now require hidden services to include the TAP keys for
6437 their intro points in the hidden service descriptor. This prevents
6438 an inadvertent upgrade to ntor, which a malicious hidden service
6439 could use to distinguish clients by consensus version. Fixes bug
6440 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
6442 o Minor features (security, TLS):
6443 - Servers no longer support clients that without AES ciphersuites.
6444 (3DES is no longer considered an acceptable cipher.) We believe
6445 that no such Tor clients currently exist, since Tor has required
6446 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
6448 o Minor feature (fallback directories):
6449 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
6450 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
6451 2016. Closes ticket 20190; patch by teor.
6453 o Minor features (geoip, also in 0.2.8.8):
6454 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
6457 o Minor feature (port flags):
6458 - Add new flags to the *Port options to finer control over which
6459 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
6460 and the synthetic flag OnionTrafficOnly, which is equivalent to
6461 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
6462 18693; patch by "teor".
6464 o Minor features (directory authority):
6465 - After voting, if the authorities decide that a relay is not
6466 "Valid", they no longer include it in the consensus at all. Closes
6467 ticket 20002; implements part of proposal 272.
6469 o Minor features (testing):
6470 - Disable memory protections on OpenBSD when performing our unit
6471 tests for memwipe(). The test deliberately invokes undefined
6472 behavior, and the OpenBSD protections interfere with this. Patch
6473 from "rubiate". Closes ticket 20066.
6475 o Minor features (testing, ipv6):
6476 - Add the single-onion and single-onion-ipv6 chutney targets to
6477 "make test-network-all". This requires a recent chutney version
6478 with the single onion network flavours (git c72a652 or later).
6479 Closes ticket 20072; patch by teor.
6480 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
6481 tests. Remove bridges+hs, as it's somewhat redundant. This
6482 requires a recent chutney version that supports IPv6 clients,
6483 relays, and authorities. Closes ticket 20069; patch by teor.
6485 o Minor features (Tor2web):
6486 - Make Tor2web clients respect ReachableAddresses. This feature was
6487 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
6488 0.2.8.7. Implements feature 20034. Patch by teor.
6490 o Minor features (unit tests):
6491 - We've done significant work to make the unit tests run faster.
6492 - Our link-handshake unit tests now check that when invalid
6493 handshakes fail, they fail with the error messages we expected.
6494 - Our unit testing code that captures log messages no longer
6495 prevents them from being written out if the user asked for them
6496 (by passing --debug or --info or or --notice --warn to the "test"
6497 binary). This change prevents us from missing unexpected log
6498 messages simply because we were looking for others. Related to
6500 - The unit tests now log all warning messages with the "BUG" flag.
6501 Previously, they only logged errors by default. This change will
6502 help us make our testing code more correct, and make sure that we
6503 only hit this code when we mean to. In the meantime, however,
6504 there will be more warnings in the unit test logs than before.
6505 This is preparatory work for ticket 19999.
6506 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
6507 assertion as a test failure.
6509 o Minor bug fixes (circuits):
6510 - Use the CircuitBuildTimeout option whenever
6511 LearnCircuitBuildTimeout is disabled. Previously, we would respect
6512 the option when a user disabled it, but not when it was disabled
6513 because some other option was set. Fixes bug 20073; bugfix on
6514 0.2.4.12-alpha. Patch by teor.
6516 o Minor bugfixes (allocation):
6517 - Change how we allocate memory for large chunks on buffers, to
6518 avoid a (currently impossible) integer overflow, and to waste less
6519 space when allocating unusually large chunks. Fixes bug 20081;
6520 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
6521 - Always include orconfig.h before including any other C headers.
6522 Sometimes, it includes macros that affect the behavior of the
6523 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
6524 first version to use AC_USE_SYSTEM_EXTENSIONS).
6525 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
6526 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
6527 Patch from Gisle Vanem.
6528 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
6529 They apparently require a set of annotations that we aren't
6530 currently using, and they create false positives in our pthreads
6531 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
6533 o Minor bugfixes (directory authority):
6534 - Die with a more useful error when the operator forgets to place
6535 the authority_signing_key file into the keys directory. This
6536 avoids an uninformative assert & traceback about having an invalid
6537 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
6538 - When allowing private addresses, mark Exits that only exit to
6539 private locations as such. Fixes bug 20064; bugfix
6542 o Minor bugfixes (documentation):
6543 - Document the default PathsNeededToBuildCircuits value that's used
6544 by clients when the directory authorities don't set
6545 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
6546 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
6547 - Fix manual for the User option: it takes a username, not a UID.
6548 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
6551 o Minor bugfixes (hidden services):
6552 - Stop logging intro point details to the client log on certain
6553 error conditions. Fixed as part of bug 20012; bugfix on
6554 0.2.4.8-alpha. Patch by teor.
6556 o Minor bugfixes (IPv6, testing):
6557 - Check for IPv6 correctly on Linux when running test networks.
6558 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
6560 o Minor bugfixes (Linux seccomp2 sandbox):
6561 - Add permission to run the sched_yield() and sigaltstack() system
6562 calls, in order to support versions of Tor compiled with asan or
6563 ubsan code that use these calls. Now "sandbox 1" and
6564 "--enable-expensive-hardening" should be compatible on more
6565 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
6567 o Minor bugfixes (logging):
6568 - When logging a message from the BUG() macro, be explicit about
6569 what we were asserting. Previously we were confusing what we were
6570 asserting with what the bug was. Fixes bug 20093; bugfix
6572 - When we are unable to remove the bw_accounting file, do not warn
6573 if the reason we couldn't remove it was that it didn't exist.
6574 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
6576 o Minor bugfixes (option parsing):
6577 - Count unix sockets when counting client listeners (SOCKS, Trans,
6578 NATD, and DNS). This has no user-visible behaviour changes: these
6579 options are set once, and never read. Required for correct
6580 behaviour in ticket 17178. Fixes bug 19677; bugfix on
6581 0.2.6.3-alpha. Patch by teor.
6583 o Minor bugfixes (options):
6584 - Check the consistency of UseEntryGuards and EntryNodes more
6585 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
6587 - Stop changing the configured value of UseEntryGuards on
6588 authorities and Tor2web clients. Fixes bug 20074; bugfix on
6589 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
6592 o Minor bugfixes (Tor2web):
6593 - Prevent Tor2web clients running hidden services, these services
6594 are not anonymous due to the one-hop client paths. Fixes bug
6595 19678. Patch by teor.
6597 o Minor bugfixes (unit tests):
6598 - Fix a shared-random unit test that was failing on big endian
6599 architectures due to internal representation of a integer copied
6600 to a buffer. The test is changed to take a full 32 bytes of data
6601 and use the output of a python script that make the COMMIT and
6602 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
6604 - The tor_tls_server_info_callback unit test no longer crashes when
6605 debug-level logging is turned on. Fixes bug 20041; bugfix
6609 Changes in version 0.2.8.8 - 2016-09-23
6610 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
6611 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
6612 who select public relays as their bridges.
6614 o Major bugfixes (crash):
6615 - Fix a complicated crash bug that could affect Tor clients
6616 configured to use bridges when replacing a networkstatus consensus
6617 in which one of their bridges was mentioned. OpenBSD users saw
6618 more crashes here, but all platforms were potentially affected.
6619 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
6621 o Major bugfixes (relay, OOM handler):
6622 - Fix a timing-dependent assertion failure that could occur when we
6623 tried to flush from a circuit after having freed its cells because
6624 of an out-of-memory condition. Fixes bug 20203; bugfix on
6625 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
6628 o Minor feature (fallback directories):
6629 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
6630 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
6631 2016. Closes ticket 20190; patch by teor.
6633 o Minor features (geoip):
6634 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
6638 Changes in version 0.2.9.2-alpha - 2016-08-24
6639 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
6640 several new features and bugfixes. It also includes an important
6641 authority update and an important bugfix from 0.2.8.7. Everyone who
6642 sets the ReachableAddresses option, and all bridges, are strongly
6643 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
6645 o Directory authority changes (also in 0.2.8.7):
6646 - The "Tonga" bridge authority has been retired; the new bridge
6647 authority is "Bifroest". Closes tickets 19728 and 19690.
6649 o Major bugfixes (client, security, also in 0.2.8.7):
6650 - Only use the ReachableAddresses option to restrict the first hop
6651 in a path. In earlier versions of 0.2.8.x, it would apply to
6652 every hop in the path, with a possible degradation in anonymity
6653 for anyone using an uncommon ReachableAddress setting. Fixes bug
6654 19973; bugfix on 0.2.8.2-alpha.
6656 o Major features (user interface):
6657 - Tor now supports the ability to declare options deprecated, so
6658 that we can recommend that people stop using them. Previously,
6659 this was done in an ad-hoc way. Closes ticket 19820.
6661 o Major bugfixes (directory downloads):
6662 - Avoid resetting download status for consensuses hourly, since we
6663 already have another, smarter retry mechanism. Fixes bug 8625;
6664 bugfix on 0.2.0.9-alpha.
6666 o Minor features (config):
6667 - Warn users when descriptor and port addresses are inconsistent.
6668 Mitigates bug 13953; patch by teor.
6670 o Minor features (geoip):
6671 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
6674 o Minor features (user interface):
6675 - There is a new --list-deprecated-options command-line option to
6676 list all of the deprecated options. Implemented as part of
6679 o Minor bugfixes (code style):
6680 - Fix an integer signedness conversion issue in the case conversion
6681 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
6683 o Minor bugfixes (compilation):
6684 - Build correctly on versions of libevent2 without support for
6685 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
6687 - Fix a compilation warning on GCC versions before 4.6. Our
6688 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
6689 when it is also required as an argument to the compiler pragma.
6690 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
6692 o Minor bugfixes (compilation, also in 0.2.8.7):
6693 - Remove an inappropriate "inline" in tortls.c that was causing
6694 warnings on older versions of GCC. Fixes bug 19903; bugfix
6697 o Minor bugfixes (fallback directories, also in 0.2.8.7):
6698 - Avoid logging a NULL string pointer when loading fallback
6699 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
6700 and 0.2.8.1-alpha. Report and patch by "rubiate".
6702 o Minor bugfixes (logging):
6703 - Log a more accurate message when we fail to dump a microdescriptor.
6704 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
6706 o Minor bugfixes (memory leak):
6707 - Fix a series of slow memory leaks related to parsing torrc files
6708 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
6710 o Deprecated features:
6711 - A number of DNS-cache-related sub-options for client ports are now
6712 deprecated for security reasons, and may be removed in a future
6713 version of Tor. (We believe that client-side DNS caching is a bad
6714 idea for anonymity, and you should not turn it on.) The options
6715 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
6716 UseIPv4Cache, and UseIPv6Cache.
6717 - A number of options are deprecated for security reasons, and may
6718 be removed in a future version of Tor. The options are:
6719 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
6720 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
6721 CloseHSClientCircuitsImmediatelyOnTimeout,
6722 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
6723 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
6724 UseNTorHandshake, and WarnUnsafeSocks.
6725 - The *ListenAddress options are now deprecated as unnecessary: the
6726 corresponding *Port options should be used instead. These options
6727 may someday be removed. The affected options are:
6728 ControlListenAddress, DNSListenAddress, DirListenAddress,
6729 NATDListenAddress, ORListenAddress, SocksListenAddress,
6730 and TransListenAddress.
6733 - Correct the IPv6 syntax in our documentation for the
6734 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
6737 - We no longer include the (dead, deprecated) bufferevent code in
6738 Tor. Closes ticket 19450. Based on a patch from U+039b.
6741 Changes in version 0.2.8.7 - 2016-08-24
6742 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
6743 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
6744 who sets the ReachableAddresses option, and all bridges, are strongly
6745 encouraged to upgrade.
6747 o Directory authority changes:
6748 - The "Tonga" bridge authority has been retired; the new bridge
6749 authority is "Bifroest". Closes tickets 19728 and 19690.
6751 o Major bugfixes (client, security):
6752 - Only use the ReachableAddresses option to restrict the first hop
6753 in a path. In earlier versions of 0.2.8.x, it would apply to
6754 every hop in the path, with a possible degradation in anonymity
6755 for anyone using an uncommon ReachableAddress setting. Fixes bug
6756 19973; bugfix on 0.2.8.2-alpha.
6758 o Minor features (geoip):
6759 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
6762 o Minor bugfixes (compilation):
6763 - Remove an inappropriate "inline" in tortls.c that was causing
6764 warnings on older versions of GCC. Fixes bug 19903; bugfix
6767 o Minor bugfixes (fallback directories):
6768 - Avoid logging a NULL string pointer when loading fallback
6769 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
6770 and 0.2.8.1-alpha. Report and patch by "rubiate".
6773 Changes in version 0.2.9.1-alpha - 2016-08-08
6774 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
6775 series. It improves our support for hardened builds and compiler
6776 warnings, deploys some critical infrastructure for improvements to
6777 hidden services, includes a new timing backend that we hope to use for
6778 better support for traffic padding, makes it easier for programmers to
6779 log unexpected events, and contains other small improvements to
6780 security, correctness, and performance.
6782 Below are the changes since 0.2.8.6.
6784 o New system requirements:
6785 - Tor now requires Libevent version 2.0.10-stable or later. Older
6786 versions of Libevent have less efficient backends for several
6787 platforms, and lack the DNS code that we use for our server-side
6788 DNS support. This implements ticket 19554.
6789 - Tor now requires zlib version 1.2 or later, for security,
6790 efficiency, and (eventually) gzip support. (Back when we started,
6791 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
6792 released in 2003. We recommend the latest version.)
6794 o Major features (build, hardening):
6795 - Tor now builds with -ftrapv by default on compilers that support
6796 it. This option detects signed integer overflow (which C forbids),
6797 and turns it into a hard-failure. We do not apply this option to
6798 code that needs to run in constant time to avoid side-channels;
6799 instead, we use -fwrapv in that code. Closes ticket 17983.
6800 - When --enable-expensive-hardening is selected, stop applying the
6801 clang/gcc sanitizers to code that needs to run in constant time.
6802 Although we are aware of no introduced side-channels, we are not
6803 able to prove that there are none. Related to ticket 17983.
6805 o Major features (compilation):
6806 - Our big list of extra GCC warnings is now enabled by default when
6807 building with GCC (or with anything like Clang that claims to be
6808 GCC-compatible). To make all warnings into fatal compilation
6809 errors, pass --enable-fatal-warnings to configure. Closes
6811 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
6812 turn on C and POSIX extensions. (Previously, we attempted to do
6813 this on an ad hoc basis.) Closes ticket 19139.
6815 o Major features (directory authorities, hidden services):
6816 - Directory authorities can now perform the shared randomness
6817 protocol specified by proposal 250. Using this protocol, directory
6818 authorities generate a global fresh random value every day. In the
6819 future, this value will be used by hidden services to select
6820 HSDirs. This release implements the directory authority feature;
6821 the hidden service side will be implemented in the future as part
6822 of proposal 224. Resolves ticket 16943; implements proposal 250.
6824 o Major features (downloading, random exponential backoff):
6825 - When we fail to download an object from a directory service, wait
6826 for an (exponentially increasing) randomized amount of time before
6827 retrying, rather than a fixed interval as we did before. This
6828 prevents a group of Tor instances from becoming too synchronized,
6829 or a single Tor instance from becoming too predictable, in its
6830 download schedule. Closes ticket 15942.
6832 o Major bugfixes (exit policies):
6833 - Avoid disclosing exit outbound bind addresses, configured port
6834 bind addresses, and local interface addresses in relay descriptors
6835 by default under ExitPolicyRejectPrivate. Instead, only reject
6836 these (otherwise unlisted) addresses if
6837 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
6838 0.2.7.2-alpha. Patch by teor.
6840 o Major bugfixes (hidden service client):
6841 - Allow Tor clients with appropriate controllers to work with
6842 FetchHidServDescriptors set to 0. Previously, this option also
6843 disabled descriptor cache lookup, thus breaking hidden services
6844 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
6846 o Minor features (build, hardening):
6847 - Detect and work around a libclang_rt problem that would prevent
6848 clang from finding __mulodi4() on some 32-bit platforms, and thus
6849 keep -ftrapv from linking on those systems. Closes ticket 19079.
6850 - When building on a system without runtime support for the runtime
6851 hardening options, try to log a useful warning at configuration
6852 time, rather than an incomprehensible warning at link time. If
6853 expensive hardening was requested, this warning becomes an error.
6854 Closes ticket 18895.
6856 o Minor features (code safety):
6857 - In our integer-parsing functions, ensure that maxiumum value we
6858 give is no smaller than the minimum value. Closes ticket 19063;
6861 o Minor features (controller):
6862 - Implement new GETINFO queries for all downloads that use
6863 download_status_t to schedule retries. This allows controllers to
6864 examine the schedule for pending downloads. Closes ticket 19323.
6865 - Allow controllers to configure basic client authorization on
6866 hidden services when they create them with the ADD_ONION control
6867 command. Implements ticket 15588. Patch by "special".
6868 - Fire a STATUS_SERVER controller event whenever the hibernation
6869 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
6871 o Minor features (directory authority):
6872 - Directory authorities now only give the Guard flag to a relay if
6873 they are also giving it the Stable flag. This change allows us to
6874 simplify path selection for clients. It should have minimal effect
6875 in practice, since >99% of Guards already have the Stable flag.
6876 Implements ticket 18624.
6877 - Directory authorities now write their v3-status-votes file out to
6878 disk earlier in the consensus process, so we have a record of the
6879 votes even if we abort the consensus process. Resolves
6882 o Minor features (hidden service):
6883 - Stop being so strict about the payload length of "rendezvous1"
6884 cells. We used to be locked in to the "TAP" handshake length, and
6885 now we can handle better handshakes like "ntor". Resolves
6888 o Minor features (infrastructure, time):
6889 - Tor now uses the operating system's monotonic timers (where
6890 available) for internal fine-grained timing. Previously we would
6891 look at the system clock, and then attempt to compensate for the
6892 clock running backwards. Closes ticket 18908.
6893 - Tor now includes an improved timer backend, so that we can
6894 efficiently support tens or hundreds of thousands of concurrent
6895 timers, as will be needed for some of our planned anti-traffic-
6896 analysis work. This code is based on William Ahern's "timeout.c"
6897 project, which implements a "tickless hierarchical timing wheel".
6898 Closes ticket 18365.
6900 o Minor features (logging):
6901 - Provide a more useful warning message when configured with an
6902 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
6903 - When dumping unparseable router descriptors, optionally store them
6904 in separate files, named by digest, up to a configurable size
6905 limit. You can change the size limit by setting the
6906 MaxUnparseableDescSizeToLog option, and disable this feature by
6907 setting that option to 0. Closes ticket 18322.
6908 - Add a set of macros to check nonfatal assertions, for internal
6909 use. Migrating more of our checks to these should help us avoid
6910 needless crash bugs. Closes ticket 18613.
6912 o Minor features (performance):
6913 - Changer the "optimistic data" extension from "off by default" to
6914 "on by default". The default was ordinarily overridden by a
6915 consensus option, but when clients were bootstrapping for the
6916 first time, they would not have a consensus to get the option
6917 from. Changing this default When fetching a consensus for the
6918 first time, use optimistic data. This saves a round-trip during
6919 startup. Closes ticket 18815.
6921 o Minor features (relay, usability):
6922 - When the directory authorities refuse a bad relay's descriptor,
6923 encourage the relay operator to contact us. Many relay operators
6924 won't notice this line in their logs, but it's a win if even a few
6925 learn why we don't like what their relay was doing. Resolves
6928 o Minor features (testing):
6929 - Let backtrace tests work correctly under AddressSanitizer. Fixes
6930 part of bug 18934; bugfix on 0.2.5.2-alpha.
6931 - Move the test-network.sh script to chutney, and modify tor's test-
6932 network.sh to call the (newer) chutney version when available.
6933 Resolves ticket 19116. Patch by teor.
6934 - Use the lcov convention for marking lines as unreachable, so that
6935 we don't count them when we're generating test coverage data.
6936 Update our coverage tools to understand this convention. Closes
6939 o Minor bugfixes (bootstrap):
6940 - Remember the directory we fetched the consensus or previous
6941 certificates from, and use it to fetch future authority
6942 certificates. This change improves bootstrapping performance.
6943 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
6945 o Minor bugfixes (build):
6946 - The test-stem and test-network makefile targets now depend only on
6947 the tor binary that they are testing. Previously, they depended on
6948 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
6949 patch from "cypherpunks".
6951 o Minor bugfixes (circuits):
6952 - Make sure extend_info_from_router() is only called on servers.
6953 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
6955 o Minor bugfixes (compilation):
6956 - When building with Clang, use a full set of GCC warnings.
6957 (Previously, we included only a subset, because of the way we
6958 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
6960 o Minor bugfixes (directory authority):
6961 - Authorities now sort the "package" lines in their votes, for ease
6962 of debugging. (They are already sorted in consensus documents.)
6963 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
6964 - When parsing a detached signature, make sure we use the length of
6965 the digest algorithm instead of an hardcoded DIGEST256_LEN in
6966 order to avoid comparing bytes out-of-bounds with a smaller digest
6967 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
6969 o Minor bugfixes (documentation):
6970 - Document the --passphrase-fd option in the tor manpage. Fixes bug
6971 19504; bugfix on 0.2.7.3-rc.
6972 - Fix the description of the --passphrase-fd option in the
6973 tor-gencert manpage. The option is used to pass the number of a
6974 file descriptor to read the passphrase from, not to read the file
6975 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
6977 o Minor bugfixes (ephemeral hidden service):
6978 - When deleting an ephemeral hidden service, close its intro points
6979 even if they are not completely open. Fixes bug 18604; bugfix
6982 o Minor bugfixes (guard selection):
6983 - Use a single entry guard even if the NumEntryGuards consensus
6984 parameter is not provided. Fixes bug 17688; bugfix
6986 - Don't mark guards as unreachable if connection_connect() fails.
6987 That function fails for local reasons, so it shouldn't reveal
6988 anything about the status of the guard. Fixes bug 14334; bugfix
6991 o Minor bugfixes (hidden service client):
6992 - Increase the minimum number of internal circuits we preemptively
6993 build from 2 to 3, so a circuit is available when a client
6994 connects to another onion service. Fixes bug 13239; bugfix
6997 o Minor bugfixes (logging):
6998 - When logging a directory ownership mismatch, log the owning
6999 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
7001 o Minor bugfixes (memory leaks):
7002 - Fix a small, uncommon memory leak that could occur when reading a
7003 truncated ed25519 key file. Fixes bug 18956; bugfix
7006 o Minor bugfixes (testing):
7007 - Allow clients to retry HSDirs much faster in test networks. Fixes
7008 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
7009 - Disable ASAN's detection of segmentation faults while running
7010 test_bt.sh, so that we can make sure that our own backtrace
7011 generation code works. Fixes another aspect of bug 18934; bugfix
7012 on 0.2.5.2-alpha. Patch from "cypherpunks".
7013 - Fix the test-network-all target on out-of-tree builds by using the
7014 correct path to the test driver script. Fixes bug 19421; bugfix
7017 o Minor bugfixes (time):
7018 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
7019 bugfix on all released tor versions.
7020 - When computing the difference between two times in milliseconds,
7021 we now round to the nearest millisecond correctly. Previously, we
7022 could sometimes round in the wrong direction. Fixes bug 19428;
7023 bugfix on 0.2.2.2-alpha.
7025 o Minor bugfixes (user interface):
7026 - Display a more accurate number of suppressed messages in the log
7027 rate-limiter. Previously, there was a potential integer overflow
7028 in the counter. Now, if the number of messages hits a maximum, the
7029 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
7031 - Fix a typo in the passphrase prompt for the ed25519 identity key.
7032 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
7034 o Code simplification and refactoring:
7035 - Remove redundant declarations of the MIN macro. Closes
7037 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
7038 Closes ticket 18462; patch from "icanhasaccount".
7039 - Split the 600-line directory_handle_command_get function into
7040 separate functions for different URL types. Closes ticket 16698.
7043 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
7044 ticket 19153. Patch from "U+039b".
7047 - Remove support for "GET /tor/bytes.txt" DirPort request, and
7048 "GETINFO dir-usage" controller request, which were only available
7049 via a compile-time option in Tor anyway. Feature was added in
7050 0.2.2.1-alpha. Resolves ticket 19035.
7051 - There is no longer a compile-time option to disable support for
7052 TransPort. (If you don't want TransPort; just don't use it.) Patch
7053 from "U+039b". Closes ticket 19449.
7056 - Run more workqueue tests as part of "make check". These had
7057 previously been implemented, but you needed to know special
7058 command-line options to enable them.
7059 - We now have unit tests for our code to reject zlib "compression
7060 bombs". (Fortunately, the code works fine.)
7063 Changes in version 0.2.8.6 - 2016-08-02
7065 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
7067 The Tor 0.2.8 series improves client bootstrapping performance,
7068 completes the authority-side implementation of improved identity
7069 keys for relays, and includes numerous bugfixes and performance
7070 improvements throughout the program. This release continues to
7071 improve the coverage of Tor's test suite. For a full list of
7072 changes since Tor 0.2.7, see the ReleaseNotes file.
7074 Changes since 0.2.8.5-rc:
7076 o Minor features (geoip):
7077 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
7080 o Minor bugfixes (compilation):
7081 - Fix a compilation warning in the unit tests on systems where char
7082 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
7084 o Minor bugfixes (fallback directories):
7085 - Remove 1 fallback that was on the hardcoded list, then opted-out,
7086 leaving 89 of the 100 fallbacks originally introduced in Tor
7087 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
7089 o Minor bugfixes (Linux seccomp2 sandbox):
7090 - Allow more syscalls when running with "Sandbox 1" enabled:
7091 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
7092 some systems, these are required for Tor to start. Fixes bug
7093 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
7094 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
7095 so that get_interface_address6_via_udp_socket_hack() can work.
7096 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
7099 Changes in version 0.2.8.5-rc - 2016-07-07
7100 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
7101 series. If we find no new bugs or regressions here, the first stable
7102 0.2.8 release will be identical to it. It has a few small bugfixes
7103 against previous versions.
7105 o Directory authority changes:
7106 - Urras is no longer a directory authority. Closes ticket 19271.
7108 o Major bugfixes (heartbeat):
7109 - Fix a regression that would crash Tor when the periodic
7110 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
7111 0.2.8.1-alpha. Reported by "kubaku".
7113 o Minor features (build):
7114 - Tor now again builds with the recent OpenSSL 1.1 development
7115 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
7116 - When building manual pages, set the timezone to "UTC", so that the
7117 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
7118 Patch from intrigeri.
7120 o Minor bugfixes (fallback directory selection):
7121 - Avoid errors during fallback selection if there are no eligible
7122 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
7125 o Minor bugfixes (IPv6, microdescriptors):
7126 - Don't check node addresses when we only have a routerstatus. This
7127 allows IPv6-only clients to bootstrap by fetching microdescriptors
7128 from fallback directory mirrors. (The microdescriptor consensus
7129 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
7132 o Minor bugfixes (logging):
7133 - Reduce pointlessly verbose log messages when directory servers
7134 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
7135 0.2.8.1-alpha. Patch by teor.
7136 - When a fallback directory changes its fingerprint from the hard-
7137 coded fingerprint, log a less severe, more explanatory log
7138 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
7140 o Minor bugfixes (Linux seccomp2 sandboxing):
7141 - Allow statistics to be written to disk when "Sandbox 1" is
7142 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
7143 0.2.6.1-alpha respectively.
7145 o Minor bugfixes (user interface):
7146 - Remove a warning message "Service [scrubbed] not found after
7147 descriptor upload". This message appears when one uses HSPOST
7148 control command to upload a service descriptor. Since there is
7149 only a descriptor and no service, showing this message is
7150 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
7152 o Fallback directory list:
7153 - Add a comment to the generated fallback directory list that
7154 explains how to comment out unsuitable fallbacks in a way that's
7155 compatible with the stem fallback parser.
7156 - Update fallback whitelist and blacklist based on relay operator
7157 emails. Blacklist unsuitable (non-working, over-volatile)
7158 fallbacks. Resolves ticket 19071. Patch by teor.
7159 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
7160 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
7161 ticket 19071; patch by teor.
7164 Changes in version 0.2.8.4-rc - 2016-06-15
7165 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
7166 If we find no new bugs or regressions here, the first stable 0.2.8
7167 release will be identical to it. It has a few small bugfixes against
7170 o Major bugfixes (user interface):
7171 - Correctly give a warning in the cases where a relay is specified
7172 by nickname, and one such relay is found, but it is not officially
7173 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
7175 o Minor features (build):
7176 - Tor now builds once again with the recent OpenSSL 1.1 development
7177 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
7179 o Minor features (geoip):
7180 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
7183 o Minor bugfixes (compilation):
7184 - Cause the unit tests to compile correctly on mingw64 versions that
7185 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
7187 o Minor bugfixes (downloading):
7188 - Predict more correctly whether we'll be downloading over HTTP when
7189 we determine the maximum length of a URL. This should avoid a
7190 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
7194 Changes in version 0.2.8.3-alpha - 2016-05-26
7195 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
7196 the course of the 0.2.8 development cycle. It improves the behavior of
7197 directory clients, fixes several crash bugs, fixes a gap in compiler
7198 hardening, and allows the full integration test suite to run on
7201 o Major bugfixes (security, client, DNS proxy):
7202 - Stop a crash that could occur when a client running with DNSPort
7203 received a query with multiple address types, and the first
7204 address type was not supported. Found and fixed by Scott Dial.
7205 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7207 o Major bugfixes (security, compilation):
7208 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
7209 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
7210 cause a compiler warning, thereby making other checks fail, and
7211 needlessly disabling compiler-hardening support. Fixes one case of
7212 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
7214 o Major bugfixes (security, directory authorities):
7215 - Fix a crash and out-of-bounds write during authority voting, when
7216 the list of relays includes duplicate ed25519 identity keys. Fixes
7217 bug 19032; bugfix on 0.2.8.2-alpha.
7219 o Major bugfixes (client, bootstrapping):
7220 - Check if bootstrap consensus downloads are still needed when the
7221 linked connection attaches. This prevents tor making unnecessary
7222 begindir-style connections, which are the only directory
7223 connections tor clients make since the fix for 18483 was merged.
7224 - Fix some edge cases where consensus download connections may not
7225 have been closed, even though they were not needed. Related to fix
7227 - Make relays retry consensus downloads the correct number of times,
7228 rather than the more aggressive client retry count. Fixes part of
7230 - Stop downloading consensuses when we have a consensus, even if we
7231 don't have all the certificates for it yet. Fixes bug 18809;
7232 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
7234 o Major bugfixes (directory mirrors):
7235 - Decide whether to advertise begindir support in the the same way
7236 we decide whether to advertise our DirPort. Allowing these
7237 decisions to become out-of-sync led to surprising behavior like
7238 advertising begindir support when hibernation made us not
7239 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
7242 o Major bugfixes (IPv6 bridges, client):
7243 - Actually use IPv6 addresses when selecting directory addresses for
7244 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
7247 o Major bugfixes (key management):
7248 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7249 pointer to the previous (uninitialized) key value. The impact here
7250 should be limited to a difficult-to-trigger crash, if OpenSSL is
7251 running an engine that makes key generation failures possible, or
7252 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7253 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7256 o Major bugfixes (testing):
7257 - Fix a bug that would block 'make test-network-all' on systems where
7258 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
7259 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
7260 bugfix on 0.2.8.1-alpha.
7262 o Minor features (clients):
7263 - Make clients, onion services, and bridge relays always use an
7264 encrypted begindir connection for directory requests. Resolves
7265 ticket 18483. Patch by "teor".
7267 o Minor features (fallback directory mirrors):
7268 - Give each fallback the same weight for client selection; restrict
7269 fallbacks to one per operator; report fallback directory detail
7270 changes when rebuilding list; add new fallback directory mirrors
7271 to the whitelist; and many other minor simplifications and fixes.
7272 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
7273 0.2.8.1-alpha; patch by "teor".
7274 - Replace the 21 fallbacks generated in January 2016 and included in
7275 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
7276 2016. Closes task 17158; patch by "teor".
7278 o Minor features (geoip):
7279 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
7282 o Minor bugfixes (assert, portability):
7283 - Fix an assertion failure in memarea.c on systems where "long" is
7284 shorter than the size of a pointer. Fixes bug 18716; bugfix
7287 o Minor bugfixes (bootstrap):
7288 - Consistently use the consensus download schedule for authority
7289 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
7291 o Minor bugfixes (build):
7292 - Remove a pair of redundant AM_CONDITIONAL declarations from
7293 configure.ac. Fixes one final case of bug 17744; bugfix
7295 - Resolve warnings when building on systems that are concerned with
7296 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
7298 - When libscrypt.h is found, but no libscrypt library can be linked,
7299 treat libscrypt as absent. Fixes bug 19161; bugfix
7302 o Minor bugfixes (client):
7303 - Turn all TestingClientBootstrap* into non-testing torrc options.
7304 This changes simply renames them by removing "Testing" in front of
7305 them and they do not require TestingTorNetwork to be enabled
7306 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
7307 - Make directory node selection more reliable, mainly for IPv6-only
7308 clients and clients with few reachable addresses. Fixes bug 18929;
7309 bugfix on 0.2.8.1-alpha. Patch by "teor".
7311 o Minor bugfixes (controller, microdescriptors):
7312 - Make GETINFO dir/status-vote/current/consensus conform to the
7313 control specification by returning "551 Could not open cached
7314 consensus..." when not caching consensuses. Fixes bug 18920;
7315 bugfix on 0.2.2.6-alpha.
7317 o Minor bugfixes (crypto, portability):
7318 - The SHA3 and SHAKE routines now produce the correct output on Big
7319 Endian systems. No code calls either algorithm yet, so this is
7320 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
7321 - Tor now builds again with the recent OpenSSL 1.1 development
7322 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
7325 o Minor bugfixes (directories):
7326 - When fetching extrainfo documents, compare their SHA256 digests
7327 and Ed25519 signing key certificates with the routerinfo that led
7328 us to fetch them, rather than with the most recent routerinfo.
7329 Otherwise we generate many spurious warnings about mismatches.
7330 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
7332 o Minor bugfixes (logging):
7333 - When we can't generate a signing key because OfflineMasterKey is
7334 set, do not imply that we should have been able to load it. Fixes
7335 bug 18133; bugfix on 0.2.7.2-alpha.
7336 - Stop periodic_event_dispatch() from blasting twelve lines per
7337 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
7338 - When rejecting a misformed INTRODUCE2 cell, only log at
7339 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
7341 o Minor bugfixes (pluggable transports):
7342 - Avoid reporting a spurious error when we decide that we don't need
7343 to terminate a pluggable transport because it has already exited.
7344 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
7346 o Minor bugfixes (pointer arithmetic):
7347 - Fix a bug in memarea_alloc() that could have resulted in remote
7348 heap write access, if Tor had ever passed an unchecked size to
7349 memarea_alloc(). Fortunately, all the sizes we pass to
7350 memarea_alloc() are pre-checked to be less than 128 kilobytes.
7351 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
7354 o Minor bugfixes (relays):
7355 - Consider more config options when relays decide whether to
7356 regenerate their descriptor. Fixes more of bug 12538; bugfix
7358 - Resolve some edge cases where we might launch an ORPort
7359 reachability check even when DisableNetwork is set. Noticed while
7360 fixing bug 18616; bugfix on 0.2.3.9-alpha.
7362 o Minor bugfixes (statistics):
7363 - We now include consensus downloads via IPv6 in our directory-
7364 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
7366 o Minor bugfixes (testing):
7367 - Allow directories in small networks to bootstrap by skipping
7368 DirPort checks when the consensus has no exits. Fixes bug 19003;
7369 bugfix on 0.2.8.1-alpha. Patch by teor.
7370 - Fix a small memory leak that would occur when the
7371 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
7372 bugfix on 0.2.5.2-alpha.
7374 o Minor bugfixes (time handling):
7375 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
7376 field. Otherwise, our unit tests crash on Windows. Fixes bug
7377 18977; bugfix on 0.2.2.25-alpha.
7380 - Document the contents of the 'datadir/keys' subdirectory in the
7381 manual page. Closes ticket 17621.
7382 - Stop recommending use of nicknames to identify relays in our
7383 MapAddress documentation. Closes ticket 18312.
7386 Changes in version 0.2.8.2-alpha - 2016-03-28
7387 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
7388 bugs in earlier versions of Tor, including some that prevented
7389 authorities using Tor 0.2.7.x from running correctly. IPv6 and
7390 directory support should also be much improved.
7392 o New system requirements:
7393 - Tor no longer supports versions of OpenSSL with a broken
7394 implementation of counter mode. (This bug was present in OpenSSL
7395 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
7396 longer runs with, these versions.
7397 - Tor no longer attempts to support platforms where the "time_t"
7398 type is unsigned. (To the best of our knowledge, only OpenVMS does
7399 this, and Tor has never actually built on OpenVMS.) Closes
7401 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
7402 later (released in 2008 and 2009 respectively). If you are
7403 building Tor from the git repository instead of from the source
7404 distribution, and your tools are older than this, you will need to
7405 upgrade. Closes ticket 17732.
7407 o Major bugfixes (security, pointers):
7408 - Avoid a difficult-to-trigger heap corruption attack when extending
7409 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7410 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7411 Reported by Guido Vranken.
7413 o Major bugfixes (bridges, pluggable transports):
7414 - Modify the check for OR connections to private addresses. Allow
7415 bridges on private addresses, including pluggable transports that
7416 ignore the (potentially private) address in the bridge line. Fixes
7417 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
7419 o Major bugfixes (compilation):
7420 - Repair hardened builds under the clang compiler. Previously, our
7421 use of _FORTIFY_SOURCE would conflict with clang's address
7422 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
7424 o Major bugfixes (crash on shutdown):
7425 - Correctly handle detaching circuits from muxes when shutting down.
7426 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
7427 - Fix an assert-on-exit bug related to counting memory usage in
7428 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
7430 o Major bugfixes (crash on startup):
7431 - Fix a segfault during startup: If a Unix domain socket was
7432 configured as listener (such as a ControlSocket or a SocksPort
7433 "unix:" socket), and tor was started as root but not configured to
7434 switch to another user, tor would segfault while trying to string
7435 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
7438 o Major bugfixes (dns proxy mode, crash):
7439 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7440 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7442 o Major bugfixes (relays, bridge clients):
7443 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
7444 bridge clients use the address configured in the bridge line.
7445 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
7448 o Major bugfixes (voting):
7449 - Actually enable support for authorities to match routers by their
7450 Ed25519 identities. Previously, the code had been written, but
7451 some debugging code that had accidentally been left in the
7452 codebase made it stay turned off. Fixes bug 17702; bugfix
7454 - When collating votes by Ed25519 identities, authorities now
7455 include a "NoEdConsensus" flag if the ed25519 value (or lack
7456 thereof) for a server does not reflect the majority consensus.
7457 Related to bug 17668; bugfix on 0.2.7.2-alpha.
7458 - When generating a vote with keypinning disabled, never include two
7459 entries for the same ed25519 identity. This bug was causing
7460 authorities to generate votes that they could not parse when a
7461 router violated key pinning by changing its RSA identity but
7462 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
7463 18318. Bugfix on 0.2.7.2-alpha.
7465 o Minor features (security, win32):
7466 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
7467 attack. Fixes bug 18123; bugfix on all tor versions. Patch
7470 o Minor features (bug-resistance):
7471 - Make Tor survive errors involving connections without a
7472 corresponding event object. Previously we'd fail with an
7473 assertion; now we produce a log message. Related to bug 16248.
7475 o Minor features (build):
7476 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
7477 as having possible IPFW support. Closes ticket 18448. Patch from
7480 o Minor features (code hardening):
7481 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
7482 level code, to harden against accidental failures to NUL-
7483 terminate. Part of ticket 17852. Patch from jsturgix. Found
7486 o Minor features (crypto):
7487 - Validate the hard-coded Diffie-Hellman parameters and ensure that
7488 p is a safe prime, and g is a suitable generator. Closes
7491 o Minor features (geoip):
7492 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
7495 o Minor features (hidden service directory):
7496 - Streamline relay-side hsdir handling: when relays consider whether
7497 to accept an uploaded hidden service descriptor, they no longer
7498 check whether they are one of the relays in the network that is
7499 "supposed" to handle that descriptor. Implements ticket 18332.
7501 o Minor features (IPv6):
7502 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
7503 to 1, tor prefers IPv6 directory addresses.
7504 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
7505 avoids using IPv4 for client OR and directory connections.
7506 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
7507 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
7508 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
7510 o Minor features (linux seccomp2 sandbox):
7511 - Reject attempts to change our Address with "Sandbox 1" enabled.
7512 Changing Address with Sandbox turned on would never actually work,
7513 but previously it would fail in strange and confusing ways. Found
7516 o Minor features (robustness):
7517 - Exit immediately with an error message if the code attempts to use
7518 Libevent without having initialized it. This should resolve some
7519 frequently-made mistakes in our unit tests. Closes ticket 18241.
7521 o Minor features (unix domain sockets):
7522 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
7523 Unix domain sockets without checking the permissions on the parent
7524 directory. (Tor checks permissions by default because some
7525 operating systems only check permissions on the parent directory.
7526 However, some operating systems do look at permissions on the
7527 socket, and tor's default check is unneeded.) Closes ticket 18458.
7530 o Minor bugfixes (exit policies, security):
7531 - Refresh an exit relay's exit policy when interface addresses
7532 change. Previously, tor only refreshed the exit policy when the
7533 configured external address changed. Fixes bug 18208; bugfix on
7534 0.2.7.3-rc. Patch by teor.
7536 o Minor bugfixes (security, hidden services):
7537 - Prevent hidden services connecting to client-supplied rendezvous
7538 addresses that are reserved as internal or multicast. Fixes bug
7539 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
7541 o Minor bugfixes (build):
7542 - Do not link the unit tests against both the testing and non-
7543 testing versions of the static libraries. Fixes bug 18490; bugfix
7545 - Avoid spurious failures from configure files related to calling
7546 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
7547 0.2.0.1-alpha. Patch from "cypherpunks".
7548 - Silence spurious clang-scan warnings in the ed25519_donna code by
7549 explicitly initializing some objects. Fixes bug 18384; bugfix on
7550 0.2.7.2-alpha. Patch by teor.
7552 o Minor bugfixes (client, bootstrap):
7553 - Count receipt of new microdescriptors as progress towards
7554 bootstrapping. Previously, with EntryNodes set, Tor might not
7555 successfully repopulate the guard set on bootstrapping. Fixes bug
7556 16825; bugfix on 0.2.3.1-alpha.
7558 o Minor bugfixes (code correctness):
7559 - Update to the latest version of Trunnel, which tries harder to
7560 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
7561 by clang address sanitizer. Fixes bug 18373; bugfix
7564 o Minor bugfixes (configuration):
7565 - Fix a tiny memory leak when parsing a port configuration ending in
7566 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
7568 o Minor bugfixes (containers):
7569 - If we somehow attempt to construct a heap with more than
7570 1073741822 elements, avoid an integer overflow when maintaining
7571 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
7573 o Minor bugfixes (correctness):
7574 - Fix a bad memory handling bug that would occur if we had queued a
7575 cell on a channel's incoming queue. Fortunately, we can't actually
7576 queue a cell like that as our code is constructed today, but it's
7577 best to avoid this kind of error, even if there isn't any code
7578 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
7580 o Minor bugfixes (directory):
7581 - When generating a URL for a directory server on an IPv6 address,
7582 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
7583 on 0.2.3.9-alpha. Patch from Malek.
7585 o Minor bugfixes (fallback directory mirrors):
7586 - When requesting extrainfo descriptors from a trusted directory
7587 server, check whether it is an authority or a fallback directory
7588 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
7589 0.2.4.7-alpha. Reported by atagar, patch by teor.
7591 o Minor bugfixes (hidden service, client):
7592 - Handle the case where the user makes several fast consecutive
7593 requests to the same .onion address. Previously, the first six
7594 requests would each trigger a descriptor fetch, each picking a
7595 directory (there are 6 overall) and the seventh one would fail
7596 because no directories were left, thereby triggering a close on
7597 all current directory connections asking for the hidden service.
7598 The solution here is to not close the connections if we have
7599 pending directory fetches. Fixes bug 15937; bugfix
7602 o Minor bugfixes (hidden service, control port):
7603 - Add the onion address to the HS_DESC event for the UPLOADED action
7604 both on success or failure. It was previously hardcoded with
7605 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
7607 o Minor bugfixes (hidden service, directory):
7608 - Bridges now refuse "rendezvous2" (hidden service descriptor)
7609 publish attempts. Suggested by ticket 18332.
7611 o Minor bugfixes (linux seccomp2 sandbox):
7612 - Allow the setrlimit syscall, and the prlimit and prlimit64
7613 syscalls, which some libc implementations use under the hood.
7614 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
7615 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
7616 enabled and no DNS resolvers configured. This should help TAILS
7617 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
7618 - Fix the sandbox's interoperability with unix domain sockets under
7619 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
7621 o Minor bugfixes (logging):
7622 - When logging information about an unparsable networkstatus vote or
7623 consensus, do not say "vote" when we mean consensus. Fixes bug
7624 18368; bugfix on 0.2.0.8-alpha.
7625 - Scrub service name in "unrecognized service ID" log messages.
7626 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
7627 - Downgrade logs and backtraces about IP versions to info-level.
7628 Only log backtraces once each time tor runs. Assists in diagnosing
7629 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
7630 Christian, patch by teor.
7632 o Minor bugfixes (memory safety):
7633 - Avoid freeing an uninitialized pointer when opening a socket fails
7634 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
7635 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
7637 - Correctly duplicate addresses in get_interface_address6_list().
7638 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
7639 patch by "cypherpunks".
7640 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
7642 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
7643 18672; bugfix on 0.2.5.1-alpha.
7645 o Minor bugfixes (private directory):
7646 - Prevent a race condition when creating private directories. Fixes
7647 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
7648 Patch from jsturgix. Found with Flawfinder.
7650 o Minor bugfixes (test networks, IPv6):
7651 - Allow internal IPv6 addresses in descriptors in test networks.
7652 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
7655 o Minor bugfixes (testing):
7656 - We no longer disable assertions in the unit tests when coverage is
7657 enabled. Instead, we require you to say --disable-asserts-in-tests
7658 to the configure script if you need assertions disabled in the
7659 unit tests (for example, if you want to perform branch coverage).
7660 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
7662 o Minor bugfixes (time parsing):
7663 - Avoid overflow in tor_timegm when parsing dates in and after 2038
7664 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
7665 0.0.2pre14. Patch by teor.
7667 o Minor bugfixes (tor-gencert):
7668 - Correctly handle the case where an authority operator enters a
7669 passphrase but sends an EOF before sending a newline. Fixes bug
7670 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
7672 o Code simplification and refactoring:
7673 - Quote all the string interpolations in configure.ac -- even those
7674 which we are pretty sure can't contain spaces. Closes ticket
7675 17744. Patch from zerosion.
7676 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
7677 inplace, so there's no need to have a separate implementation for
7678 the non-inplace code. Closes ticket 18258. Patch from Malek.
7679 - Simplify return types for some crypto functions that can't
7680 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
7683 - Change build messages to refer to "Fedora" instead of "Fedora
7684 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
7685 Patches from "icanhasaccount" and "cypherpunks".
7688 - We no longer maintain an internal freelist in memarea.c.
7689 Allocators should be good enough to make this code unnecessary,
7690 and it's doubtful that it ever had any performance benefit.
7693 - Fix several warnings from clang's address sanitizer produced in
7695 - Treat backtrace test failures as expected on FreeBSD until we
7696 solve bug 17808. Closes ticket 18204.
7699 Changes in version 0.2.8.1-alpha - 2016-02-04
7700 Tor 0.2.8.1-alpha is the first alpha release in its series. It
7701 includes numerous small features and bugfixes against previous Tor
7702 versions, and numerous small infrastructure improvements. The most
7703 notable features are a set of improvements to the directory subsystem.
7705 o Major features (security, Linux):
7706 - When Tor starts as root on Linux and is told to switch user ID, it
7707 can now retain the capability to bind to low ports. By default,
7708 Tor will do this only when it's switching user ID and some low
7709 ports have been configured. You can change this behavior with the
7710 new option KeepBindCapabilities. Closes ticket 8195.
7712 o Major features (directory system):
7713 - When bootstrapping multiple consensus downloads at a time, use the
7714 first one that starts downloading, and close the rest. This
7715 reduces failures when authorities or fallback directories are slow
7716 or down. Together with the code for feature 15775, this feature
7717 should reduces failures due to fallback churn. Implements ticket
7718 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
7719 "mikeperry" and "teor".
7720 - Include a trial list of 21 default fallback directories, generated
7721 in January 2016, based on an opt-in survey of suitable relays.
7722 Doing this should make clients bootstrap more quickly and reliably,
7723 and reduce the load on the directory authorities. Closes ticket
7724 15775. Patch by "teor".
7725 Candidates identified using an OnionOO script by "weasel", "teor",
7726 "gsathya", and "karsten".
7727 - Previously only relays that explicitly opened a directory port
7728 (DirPort) accepted directory requests from clients. Now all
7729 relays, with and without a DirPort, accept and serve tunneled
7730 directory requests that they receive through their ORPort. You can
7731 disable this behavior using the new DirCache option. Closes
7734 o Major key updates:
7735 - Update the V3 identity key for the dannenberg directory authority:
7736 it was changed on 18 November 2015. Closes task 17906. Patch
7739 o Minor features (security, clock):
7740 - Warn when the system clock appears to move back in time (when the
7741 state file was last written in the future). Tor doesn't know that
7742 consensuses have expired if the clock is in the past. Patch by
7743 "teor". Implements ticket 17188.
7745 o Minor features (security, exit policies):
7746 - ExitPolicyRejectPrivate now rejects more private addresses by
7747 default. Specifically, it now rejects the relay's outbound bind
7748 addresses (if configured), and the relay's configured port
7749 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
7750 0.2.0.11-alpha. Patch by "teor".
7752 o Minor features (security, memory erasure):
7753 - Set the unused entries in a smartlist to NULL. This helped catch
7754 a (harmless) bug, and shouldn't affect performance too much.
7755 Implements ticket 17026.
7756 - Use SecureMemoryWipe() function to securely clean memory on
7757 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
7758 Implements feature 17986.
7759 - Use explicit_bzero or memset_s when present. Previously, we'd use
7760 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
7761 from <logan@hackers.mu> and <selven@hackers.mu>.
7762 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7763 zero size. Check size argument to memwipe() for underflow. Fixes
7764 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7767 o Minor features (security, RNG):
7768 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
7769 positively are not allowed to fail. Previously we depended on
7770 internal details of OpenSSL's behavior. Closes ticket 17686.
7771 - Never use the system entropy output directly for anything besides
7772 seeding the PRNG. When we want to generate important keys, instead
7773 of using system entropy directly, we now hash it with the PRNG
7774 stream. This may help resist certain attacks based on broken OS
7775 entropy implementations. Closes part of ticket 17694.
7776 - Use modern system calls (like getentropy() or getrandom()) to
7777 generate strong entropy on platforms that have them. Closes
7780 o Minor features (accounting):
7781 - Added two modes to the AccountingRule option: One for limiting
7782 only the number of bytes sent ("AccountingRule out"), and one for
7783 limiting only the number of bytes received ("AccountingRule in").
7784 Closes ticket 15989; patch from "unixninja92".
7786 o Minor features (build):
7787 - Since our build process now uses "make distcheck", we no longer
7788 force "make dist" to depend on "make check". Closes ticket 17893;
7789 patch from "cypherpunks."
7790 - Tor now builds successfully with the recent OpenSSL 1.1
7791 development branch, and with the latest LibreSSL. Closes tickets
7792 17549, 17921, and 17984.
7794 o Minor features (controller):
7795 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
7796 tickets 16774 and 17817. Patch by George Tankersley.
7797 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
7798 service descriptor from a service's local hidden service
7799 descriptor cache. Closes ticket 14846.
7800 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
7801 controllers can examine the the reject rules added by
7802 ExitPolicyRejectPrivate. This makes it easier for stem to display
7805 o Minor features (crypto):
7806 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
7808 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
7809 - When allocating a digest state object, allocate no more space than
7810 we actually need. Previously, we would allocate as much space as
7811 the state for the largest algorithm would need. This change saves
7812 up to 672 bytes per circuit. Closes ticket 17796.
7813 - Improve performance when hashing non-multiple of 8 sized buffers,
7814 based on Andrew Moon's public domain SipHash-2-4 implementation.
7815 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
7817 o Minor features (directory downloads):
7818 - Wait for busy authorities and fallback directories to become non-
7819 busy when bootstrapping. (A similar change was made in 6c443e987d
7820 for directory caches chosen from the consensus.) Closes ticket
7821 17864; patch by "teor".
7822 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
7823 directory mirrors. The default is 1; set it to 0 to disable
7824 fallbacks. Implements ticket 17576. Patch by "teor".
7826 o Minor features (geoip):
7827 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
7830 o Minor features (IPv6):
7831 - Add an argument 'ipv6=address:orport' to the DirAuthority and
7832 FallbackDir torrc options, to specify an IPv6 address for an
7833 authority or fallback directory. Add hard-coded ipv6 addresses for
7834 directory authorities that have them. Closes ticket 17327; patch
7835 from Nick Mathewson and "teor".
7836 - Add address policy assume_action support for IPv6 addresses.
7837 - Limit IPv6 mask bits to 128.
7838 - Warn when comparing against an AF_UNSPEC address in a policy, it's
7839 almost always a bug. Closes ticket 17863; patch by "teor".
7840 - Allow users to configure directory authorities and fallback
7841 directory servers with IPv6 addresses and ORPorts. Resolves
7843 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
7844 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
7845 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
7846 17638; bugfix on 0.0.2pre8. Patch by "teor".
7848 o Minor features (logging):
7849 - When logging to syslog, allow a tag to be added to the syslog
7850 identity (the string prepended to every log message). The tag can
7851 be configured with SyslogIdentityTag and defaults to none. Setting
7852 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
7855 o Minor features (portability):
7856 - Use timingsafe_memcmp() where available. Closes ticket 17944;
7857 patch from <logan@hackers.mu>.
7859 o Minor features (relay, address discovery):
7860 - Add a family argument to get_interface_addresses_raw() and
7861 subfunctions to make network interface address interogation more
7862 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
7863 types of interfaces from the operating system. Resolves
7865 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
7866 fails to enumerate interface addresses using the platform-specific
7867 API, have it rely on the UDP socket fallback technique to try and
7868 find out what IP addresses (both IPv4 and IPv6) our machine has.
7869 Resolves ticket 17951.
7871 o Minor features (replay cache):
7872 - The replay cache now uses SHA256 instead of SHA1. Implements
7873 feature 8961. Patch by "teor", issue reported by "rransom".
7875 o Minor features (unix file permissions):
7876 - Defer creation of Unix sockets until after setuid. This avoids
7877 needing CAP_CHOWN and CAP_FOWNER when using systemd's
7878 CapabilityBoundingSet, or chown and fowner when using SELinux.
7879 Implements part of ticket 17562. Patch from Jamie Nguyen.
7880 - If any directory created by Tor is marked as group readable, the
7881 filesystem group is allowed to be either the default GID or the
7882 root user. Allowing root to read the DataDirectory prevents the
7883 need for CAP_READ_SEARCH when using systemd's
7884 CapabilityBoundingSet, or dac_read_search when using SELinux.
7885 Implements part of ticket 17562. Patch from Jamie Nguyen.
7886 - Introduce a new DataDirectoryGroupReadable option. If it is set to
7887 1, the DataDirectory will be made readable by the default GID.
7888 Implements part of ticket 17562. Patch from Jamie Nguyen.
7890 o Minor bugfixes (accounting):
7891 - The max bandwidth when using 'AccountRule sum' is now correctly
7892 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
7895 o Minor bugfixes (code correctness):
7896 - When closing an entry connection, generate a warning if we should
7897 have sent an end cell for it but we haven't. Fixes bug 17876;
7898 bugfix on 0.2.3.2-alpha.
7899 - Assert that allocated memory held by the reputation code is freed
7900 according to its internal counters. Fixes bug 17753; bugfix
7902 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
7905 o Minor bugfixes (compilation):
7906 - Mark all object files that include micro-revision.i as depending
7907 on it, so as to make parallel builds more reliable. Fixes bug
7908 17826; bugfix on 0.2.5.1-alpha.
7909 - Don't try to use the pthread_condattr_setclock() function unless
7910 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
7911 17819; bugfix on 0.2.6.3-alpha.
7912 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
7914 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
7915 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
7916 - Fix search for libevent libraries on OpenBSD (and other systems
7917 that install libevent 1 and libevent 2 in parallel). Fixes bug
7918 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
7919 - Isolate environment variables meant for tests from the rest of the
7920 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
7921 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
7923 - Remove config.log only from make distclean, not from make clean.
7924 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
7926 o Minor bugfixes (crypto):
7927 - Check the return value of HMAC() and assert on failure. Fixes bug
7928 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
7930 o Minor bugfixes (fallback directories):
7931 - Mark fallbacks as "too busy" when they return a 503 response,
7932 rather than just marking authorities. Fixes bug 17572; bugfix on
7933 0.2.4.7-alpha. Patch by "teor".
7935 o Minor bugfixes (IPv6):
7936 - Update the limits in max_dl_per_request for IPv6 address length.
7937 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
7939 o Minor bugfixes (linux seccomp2 sandbox):
7940 - Fix a crash when using offline master ed25519 keys with the Linux
7941 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
7943 o Minor bugfixes (logging):
7944 - In log messages that include a function name, use __FUNCTION__
7945 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
7946 with clang __PRETTY_FUNCTION__ has extra information we don't
7947 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
7949 - Remove needless quotes from a log message about unparseable
7950 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
7952 o Minor bugfixes (portability):
7953 - Remove an #endif from configure.ac so that we correctly detect the
7954 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
7957 o Minor bugfixes (relays):
7958 - Check that both the ORPort and DirPort (if present) are reachable
7959 before publishing a relay descriptor. Otherwise, relays publish a
7960 descriptor with DirPort 0 when the DirPort reachability test takes
7961 longer than the ORPort reachability test. Fixes bug 18050; bugfix
7962 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
7964 o Minor bugfixes (relays, hidden services):
7965 - Refuse connection requests to private OR addresses unless
7966 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
7967 then refuse to send any cells to a private address. Fixes bugs
7968 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
7970 o Minor bugfixes (safe logging):
7971 - When logging a malformed hostname received through socks4, scrub
7972 it if SafeLogging says we should. Fixes bug 17419; bugfix
7975 o Minor bugfixes (statistics code):
7976 - Consistently check for overflow in round_*_to_next_multiple_of
7977 functions, and add unit tests with additional and maximal values.
7978 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
7979 - Handle edge cases in the laplace functions: avoid division by
7980 zero, avoid taking the log of zero, and silence clang type
7981 conversion warnings using round and trunc. Add unit tests for edge
7982 cases with maximal values. Fixes part of bug 13192; bugfix
7985 o Minor bugfixes (testing):
7986 - The test for log_heartbeat was incorrectly failing in timezones
7987 with non-integer offsets. Instead of comparing the end of the time
7988 string against a constant, compare it to the output of
7989 format_local_iso_time when given the correct input. Fixes bug
7990 18039; bugfix on 0.2.5.4-alpha.
7991 - Make unit tests pass on IPv6-only systems, and systems without
7992 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
7993 bugfix on 0.2.7.3-rc. Patch by "teor".
7994 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
7996 - Check the full results of SHA256 and SHA512 digests in the unit
7997 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
7999 o Code simplification and refactoring:
8000 - Move logging of redundant policy entries in
8001 policies_parse_exit_policy_internal into its own function. Closes
8002 ticket 17608; patch from "juce".
8003 - Extract the more complicated parts of circuit_mark_for_close()
8004 into a new function that we run periodically before circuits are
8005 freed. This change removes more than half of the functions
8006 currently in the "blob". Closes ticket 17218.
8007 - Clean up a little duplicated code in
8008 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
8010 - Decouple the list of streams waiting to be attached to circuits
8011 from the overall connection list. This change makes it possible to
8012 attach streams quickly while simplifying Tor's callgraph and
8013 avoiding O(N) scans of the entire connection list. Closes
8015 - When a direct directory request fails immediately on launch,
8016 instead of relaunching that request from inside the code that
8017 launches it, instead mark the connection for teardown. This change
8018 simplifies Tor's callback and prevents the directory-request
8019 launching code from invoking itself recursively. Closes
8021 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
8022 use them. Closes ticket 17926.
8025 - Add a description of the correct use of the '--keygen' command-
8026 line option. Closes ticket 17583; based on text by 's7r'.
8027 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
8028 - Explain actual minima for BandwidthRate. Closes ticket 16382.
8029 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
8030 - Mention torspec URL in the manpage and point the reader to it
8031 whenever we mention a document that belongs in torspce. Fixes
8035 - Remove client-side support for connecting to Tor relays running
8036 versions of Tor before 0.2.3.6-alpha. These relays didn't support
8037 the v3 TLS handshake protocol, and are no longer allowed on the
8038 Tor network. Implements the client side of ticket 11150. Based on
8039 patches by Tom van der Woerdt.
8042 - Add unit tests to check for common RNG failure modes, such as
8043 returning all zeroes, identical values, or incrementing values
8044 (OpenSSL's rand_predictable feature). Patch by "teor".
8045 - Log more information when the backtrace tests fail. Closes ticket
8046 17892. Patch from "cypherpunks."
8047 - Always test both ed25519 backends, so that we can be sure that our
8048 batch-open replacement code works. Part of ticket 16794.
8049 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
8050 portion of ticket 16831.
8051 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
8052 util_format.c, directory.c, and options_validate.c. Closes tickets
8053 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
8055 - Unit tests for directory_handle_command_get. Closes ticket 17004.
8056 Patch from Reinaldo de Souza Jr.
8059 Changes in version 0.2.7.6 - 2015-12-10
8060 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
8061 well as a minor bug in hidden service reliability.
8063 o Major bugfixes (guard selection):
8064 - Actually look at the Guard flag when selecting a new directory
8065 guard. When we implemented the directory guard design, we
8066 accidentally started treating all relays as if they have the Guard
8067 flag during guard selection, leading to weaker anonymity and worse
8068 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8071 o Minor features (geoip):
8072 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
8075 o Minor bugfixes (compilation):
8076 - When checking for net/pfvar.h, include netinet/in.h if possible.
8077 This fixes transparent proxy detection on OpenBSD. Fixes bug
8078 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
8079 - Fix a compilation warning with Clang 3.6: Do not check the
8080 presence of an address which can never be NULL. Fixes bug 17781.
8082 o Minor bugfixes (correctness):
8083 - When displaying an IPv6 exit policy, include the mask bits
8084 correctly even when the number is greater than 31. Fixes bug
8085 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
8086 - The wrong list was used when looking up expired intro points in a
8087 rend service object, causing what we think could be reachability
8088 issues for hidden services, and triggering a BUG log. Fixes bug
8089 16702; bugfix on 0.2.7.2-alpha.
8090 - Fix undefined behavior in the tor_cert_checksig function. Fixes
8091 bug 17722; bugfix on 0.2.7.2-alpha.
8094 Changes in version 0.2.7.5 - 2015-11-20
8095 The Tor 0.2.7 release series is dedicated to the memory of Tor user
8096 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
8097 tirelessly to advocate human rights regardless of national borders,
8098 and oppose the encroachments of mass surveillance. He opposed national
8099 exceptionalism, he brought clarity to legal and policy debates, he
8100 understood and predicted the impact of mass surveillance on the world,
8101 and he laid the groundwork for resisting it. While serving on the Tor
8102 Project's board of directors, he brought us his uncompromising focus
8103 on technical excellence in the service of humankind. Caspar was an
8104 inimitable force for good and a wonderful friend. He was kind,
8105 humorous, generous, gallant, and believed we should protect one
8106 another without exception. We honor him here for his ideals, his
8107 efforts, and his accomplishments. Please honor his memory with works
8108 that would make him proud.
8110 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
8112 The 0.2.7 series adds a more secure identity key type for relays,
8113 improves cryptography performance, resolves several longstanding
8114 hidden-service performance issues, improves controller support for
8115 hidden services, and includes small bugfixes and performance
8116 improvements throughout the program. This release series also includes
8117 more tests than before, and significant simplifications to which parts
8118 of Tor invoke which others.
8120 (This release contains no code changes since 0.2.7.4-rc.)
8123 Changes in version 0.2.7.4-rc - 2015-10-21
8124 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
8125 fixes some important memory leaks, and a scary-looking (but mostly
8126 harmless in practice) invalid-read bug. It also has a few small
8127 bugfixes, notably fixes for compilation and portability on different
8128 platforms. If no further significant bounds are found, the next
8129 release will the the official stable release.
8131 o Major bugfixes (security, correctness):
8132 - Fix an error that could cause us to read 4 bytes before the
8133 beginning of an openssl string. This bug could be used to cause
8134 Tor to crash on systems with unusual malloc implementations, or
8135 systems with unusual hardening installed. Fixes bug 17404; bugfix
8138 o Major bugfixes (correctness):
8139 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
8140 bug 17401; bugfix on 0.2.7.3-rc.
8142 o Major bugfixes (memory leaks):
8143 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
8144 17398; bugfix on 0.2.6.1-alpha.
8145 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
8146 17402; bugfix on 0.2.7.3-rc.
8147 - Fix a memory leak when reading an expired signing key from disk.
8148 Fixes bug 17403; bugfix on 0.2.7.2-rc.
8150 o Minor features (geoIP):
8151 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
8154 o Minor bugfixes (compilation):
8155 - Repair compilation with the most recent (unreleased, alpha)
8156 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
8157 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
8158 17251; bugfix on 0.2.7.2-alpha.
8159 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
8160 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
8162 o Minor bugfixes (portability):
8163 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
8164 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
8167 o Minor bugfixes (sandbox):
8168 - Add the "hidserv-stats" filename to our sandbox filter for the
8169 HiddenServiceStatistics option to work properly. Fixes bug 17354;
8170 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
8172 o Minor bugfixes (testing):
8173 - Add unit tests for get_interface_address* failure cases. Fixes bug
8174 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
8175 - Fix breakage when running 'make check' with BSD make. Fixes bug
8176 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
8177 - Make the get_ifaddrs_* unit tests more tolerant of different
8178 network configurations. (Don't assume every test box has an IPv4
8179 address, and don't assume every test box has a non-localhost
8180 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
8181 - Skip backtrace tests when backtrace support is not compiled in.
8182 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
8186 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
8187 - Note that HiddenServicePorts can take a unix domain socket. Closes
8191 Changes in version 0.2.7.3-rc - 2015-09-25
8192 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
8193 contains numerous usability fixes for Ed25519 keys, safeguards against
8194 several misconfiguration problems, significant simplifications to
8195 Tor's callgraph, and numerous bugfixes and small features.
8197 This is the most tested release of Tor to date. The unit tests cover
8198 39.40% of the code, and the integration tests (accessible with "make
8199 test-full-online", requiring stem and chutney and a network
8200 connection) raise the coverage to 64.49%.
8202 o Major features (security, hidden services):
8203 - Hidden services, if using the EntryNodes option, are required to
8204 use more than one EntryNode, in order to avoid a guard discovery
8205 attack. (This would only affect people who had configured hidden
8206 services and manually specified the EntryNodes option with a
8207 single entry-node. The impact was that it would be easy to
8208 remotely identify the guard node used by such a hidden service.
8209 See ticket for more information.) Fixes ticket 14917.
8211 o Major features (Ed25519 keys, keypinning):
8212 - The key-pinning option on directory authorities is now advisory-
8213 only by default. In a future version, or when the AuthDirPinKeys
8214 option is set, pins are enforced again. Disabling key-pinning
8215 seemed like a good idea so that we can survive the fallout of any
8216 usability problems associated with Ed25519 keys. Closes
8219 o Major features (Ed25519 performance):
8220 - Improve the speed of Ed25519 operations and Curve25519 keypair
8221 generation when built targeting 32 bit x86 platforms with SSE2
8222 available. Implements ticket 16535.
8223 - Improve the runtime speed of Ed25519 signature verification by
8224 using Ed25519-donna's batch verification support. Implements
8227 o Major features (performance testing):
8228 - The test-network.sh script now supports performance testing.
8229 Requires corresponding chutney performance testing changes. Patch
8230 by "teor". Closes ticket 14175.
8232 o Major features (relay, Ed25519):
8233 - Significant usability improvements for Ed25519 key management. Log
8234 messages are better, and the code can recover from far more
8235 failure conditions. Thanks to "s7r" for reporting and diagnosing
8237 - Add a new OfflineMasterKey option to tell Tor never to try loading
8238 or generating a secret Ed25519 identity key. You can use this in
8239 combination with tor --keygen to manage offline and/or encrypted
8240 Ed25519 keys. Implements ticket 16944.
8241 - Add a --newpass option to allow changing or removing the
8242 passphrase of an encrypted key with tor --keygen. Implements part
8244 - On receiving a HUP signal, check to see whether the Ed25519
8245 signing key has changed, and reload it if so. Closes ticket 16790.
8247 o Major bugfixes (relay, Ed25519):
8248 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
8249 0.2.7.2-alpha. Reported by "s7r".
8250 - Improve handling of expired signing keys with offline master keys.
8251 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
8253 o Minor features (client-side privacy):
8254 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
8255 lifespan when IsolateSOCKSAuth and streams with SOCKS
8256 authentication are attached to the circuit. This allows
8257 applications like TorBrowser to manage circuit lifetime on their
8258 own. Implements feature 15482.
8259 - When logging malformed hostnames from SOCKS5 requests, respect
8260 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
8262 o Minor features (compilation):
8263 - Give a warning as early as possible when trying to build with an
8264 unsupported OpenSSL version. Closes ticket 16901.
8265 - Fail during configure if we're trying to build against an OpenSSL
8266 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
8267 which started requiring ECC.
8269 o Minor features (geoip):
8270 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
8273 o Minor features (hidden services):
8274 - Relays need to have the Fast flag to get the HSDir flag. As this
8275 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
8276 drop. This change should make some attacks against the hidden
8277 service directory system harder. Fixes ticket 15963.
8278 - Turn on hidden service statistics collection by setting the torrc
8279 option HiddenServiceStatistics to "1" by default. (This keeps
8280 track only of the fraction of traffic used by hidden services, and
8281 the total number of hidden services in existence.) Closes
8283 - Client now uses an introduction point failure cache to know when
8284 to fetch or keep a descriptor in their cache. Previously, failures
8285 were recorded implicitly, but not explicitly remembered. Closes
8288 o Minor features (testing, authorities, documentation):
8289 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
8290 explicitly manage consensus flags in testing networks. Patch by
8291 "robgjansen", modified by "teor". Implements part of ticket 14882.
8293 o Minor bugfixes (security, exit policies):
8294 - ExitPolicyRejectPrivate now also rejects the relay's published
8295 IPv6 address (if any), and any publicly routable IPv4 or IPv6
8296 addresses on any local interfaces. ticket 17027. Patch by "teor".
8297 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
8299 o Minor bug fixes (torrc exit policies):
8300 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
8301 produce IPv6 wildcard addresses. Previously they would produce
8302 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
8303 of bug 16069; bugfix on 0.2.4.7-alpha.
8304 - When parsing torrc ExitPolicies, we now warn for a number of cases
8305 where the user's intent is likely to differ from Tor's actual
8306 behavior. These include: using an IPv4 address with an accept6 or
8307 reject6 line; using "private" on an accept6 or reject6 line; and
8308 including any ExitPolicy lines after accept *:* or reject *:*.
8309 Related to ticket 16069.
8310 - When parsing torrc ExitPolicies, we now issue an info-level
8311 message when expanding an "accept/reject *" line to include both
8312 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
8313 - In each instance above, usage advice is provided to avoid the
8314 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
8315 16069; bugfix on 0.2.4.7-alpha.
8317 o Minor bugfixes (authority):
8318 - Don't assign "HSDir" to a router if it isn't Valid and Running.
8319 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
8320 - Downgrade log messages about Ed25519 key issues if they are in old
8321 cached router descriptors. Fixes part of bug 16286; bugfix
8323 - When we find an Ed25519 key issue in a cached descriptor, stop
8324 saying the descriptor was just "uploaded". Fixes another part of
8325 bug 16286; bugfix on 0.2.7.2-alpha.
8327 o Minor bugfixes (control port):
8328 - Repair a warning and a spurious result when getting the maximum
8329 number of file descriptors from the controller. Fixes bug 16697;
8330 bugfix on 0.2.7.2-alpha.
8332 o Minor bugfixes (correctness):
8333 - When calling channel_free_list(), avoid calling smartlist_remove()
8334 while inside a FOREACH loop. This partially reverts commit
8335 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
8336 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
8338 o Minor bugfixes (documentation):
8339 - Advise users on how to configure separate IPv4 and IPv6 exit
8340 policies in the manpage and sample torrcs. Related to ticket 16069.
8341 - Fix the usage message of tor-resolve(1) so that it no longer lists
8342 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
8343 - Fix an error in the manual page and comments for
8344 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
8345 required "ORPort connectivity". While this is true, it is in no
8346 way unique to the HSDir flag. Of all the flags, only HSDirs need a
8347 DirPort configured in order for the authorities to assign that
8348 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
8351 o Minor bugfixes (Ed25519):
8352 - Fix a memory leak when reading router descriptors with expired
8353 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
8355 o Minor bugfixes (linux seccomp2 sandbox):
8356 - Allow bridge authorities to run correctly under the seccomp2
8357 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
8358 - Allow routers with ed25519 keys to run correctly under the
8359 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
8361 o Minor bugfixes (open file limit):
8362 - Fix set_max_file_descriptors() to set by default the max open file
8363 limit to the current limit when setrlimit() fails. Fixes bug
8364 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
8366 o Minor bugfixes (portability):
8367 - Try harder to normalize the exit status of the Tor process to the
8368 standard-provided range. Fixes bug 16975; bugfix on every version
8370 - Check correctly for Windows socket errors in the workqueue
8371 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
8372 - Fix the behavior of crypto_rand_time_range() when told to consider
8373 times before 1970. (These times were possible when running in a
8374 simulated network environment where time()'s output starts at
8375 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
8376 - Restore correct operation of TLS client-cipher detection on
8377 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
8379 o Minor bugfixes (relay):
8380 - Ensure that worker threads actually exit when a fatal error or
8381 shutdown is indicated. This fix doesn't currently affect the
8382 behavior of Tor, because Tor workers never indicates fatal error
8383 or shutdown except in the unit tests. Fixes bug 16868; bugfix
8385 - Unblock threads before releasing the work queue mutex to ensure
8386 predictable scheduling behavior. Fixes bug 16644; bugfix
8389 o Code simplification and refactoring:
8390 - Change the function that's called when we need to retry all
8391 downloads so that it only reschedules the downloads to happen
8392 immediately, rather than launching them all at once itself. This
8393 further simplifies Tor's callgraph.
8394 - Move some format-parsing functions out of crypto.c and
8395 crypto_curve25519.c into crypto_format.c and/or util_format.c.
8396 - Move the client-only parts of init_keys() into a separate
8397 function. Closes ticket 16763.
8398 - Simplify the microdesc_free() implementation so that it no longer
8399 appears (to code analysis tools) to potentially invoke a huge
8400 suite of other microdesc functions.
8401 - Simply the control graph further by deferring the inner body of
8402 directory_all_unreachable() into a callback. Closes ticket 16762.
8403 - Treat the loss of an owning controller as equivalent to a SIGTERM
8404 signal. This removes a tiny amount of duplicated code, and
8405 simplifies our callgraph. Closes ticket 16788.
8406 - When generating an event to send to the controller, we no longer
8407 put the event over the network immediately. Instead, we queue
8408 these events, and use a Libevent callback to deliver them. This
8409 change simplifies Tor's callgraph by reducing the number of
8410 functions from which all other Tor functions are reachable. Closes
8412 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
8413 that try to scan or compile every file on Unix won't decide that
8415 - Remove the unused "nulterminate" argument from buf_pullup().
8418 - Recommend a 40 GB example AccountingMax in torrc.sample rather
8419 than a 4 GB max. Closes ticket 16742.
8420 - Include the TUNING document in our source tarball. It is referred
8421 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
8425 - The internal pure-C tor-fw-helper tool is now removed from the Tor
8426 distribution, in favor of the pure-Go clone available from
8427 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
8428 used by the C tor-fw-helper are not, in our opinion, very
8429 confidence- inspiring in their secure-programming techniques.
8430 Closes ticket 13338.
8431 - Remove the code that would try to aggressively flush controller
8432 connections while writing to them. This code was introduced in
8433 0.1.2.7-alpha, in order to keep output buffers from exceeding
8434 their limits. But there is no longer a maximum output buffer size,
8435 and flushing data in this way caused some undesirable recursions
8436 in our call graph. Closes ticket 16480.
8439 - Make "bridges+hs" the default test network. This tests almost all
8440 tor functionality during make test-network, while allowing tests
8441 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
8442 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
8443 (chutney). Patches by "teor".
8444 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
8445 by-side in the same parent directory. Closes ticket 16903. Patch
8447 - Use environment variables rather than autoconf substitutions to
8448 send variables from the build system to the test scripts. This
8449 change should be easier to maintain, and cause 'make distcheck' to
8450 work better than before. Fixes bug 17148.
8451 - Add a new set of callgraph analysis scripts that use clang to
8452 produce a list of which Tor functions are reachable from which
8453 other Tor functions. We're planning to use these to help simplify
8454 our code structure by identifying illogical dependencies.
8455 - Add new 'test-full' and 'test-full-online' targets to run all
8456 tests, including integration tests with stem and chutney.
8457 - Make the test-workqueue test work on Windows by initializing the
8458 network before we begin.
8459 - New make target (make test-network-all) to run multiple applicable
8460 chutney test cases. Patch from Teor; closes 16953.
8461 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
8462 functions in dns.c. Implements a portion of ticket 16831.
8463 - When building Tor with testing coverage enabled, run Chutney tests
8464 (if any) using the 'tor-cov' coverage binary.
8465 - When running test-network or test-stem, check for the absence of
8466 stem/chutney before doing any build operations.
8469 Changes in version 0.2.7.2-alpha - 2015-07-27
8470 This, the second alpha in the Tor 0.2.7 series, has a number of new
8471 features, including a way to manually pick the number of introduction
8472 points for hidden services, and the much stronger Ed25519 signing key
8473 algorithm for regular Tor relays (including support for encrypted
8474 offline identity keys in the new algorithm).
8476 Support for Ed25519 on relays is currently limited to signing router
8477 descriptors; later alphas in this series will extend Ed25519 key
8478 support to more parts of the Tor protocol.
8480 o Major features (Ed25519 identity keys, Proposal 220):
8481 - All relays now maintain a stronger identity key, using the Ed25519
8482 elliptic curve signature format. This master key is designed so
8483 that it can be kept offline. Relays also generate an online
8484 signing key, and a set of other Ed25519 keys and certificates.
8485 These are all automatically regenerated and rotated as needed.
8486 Implements part of ticket 12498.
8487 - Directory authorities now vote on Ed25519 identity keys along with
8488 RSA1024 keys. Implements part of ticket 12498.
8489 - Directory authorities track which Ed25519 identity keys have been
8490 used with which RSA1024 identity keys, and do not allow them to
8491 vary freely. Implements part of ticket 12498.
8492 - Microdescriptors now include Ed25519 identity keys. Implements
8493 part of ticket 12498.
8494 - Add support for offline encrypted Ed25519 master keys. To use this
8495 feature on your tor relay, run "tor --keygen" to make a new master
8496 key (or to make a new signing key if you already have a master
8497 key). Closes ticket 13642.
8499 o Major features (Hidden services):
8500 - Add the torrc option HiddenServiceNumIntroductionPoints, to
8501 specify a fixed number of introduction points. Its maximum value
8502 is 10 and default is 3. Using this option can increase a hidden
8503 service's reliability under load, at the cost of making it more
8504 visible that the hidden service is facing extra load. Closes
8506 - Remove the adaptive algorithm for choosing the number of
8507 introduction points, which used to change the number of
8508 introduction points (poorly) depending on the number of
8509 connections the HS sees. Closes ticket 4862.
8511 o Major features (onion key cross-certification):
8512 - Relay descriptors now include signatures of their own identity
8513 keys, made using the TAP and ntor onion keys. These signatures
8514 allow relays to prove ownership of their own onion keys. Because
8515 of this change, microdescriptors will no longer need to include
8516 RSA identity keys. Implements proposal 228; closes ticket 12499.
8518 o Major features (performance):
8519 - Improve the runtime speed of Ed25519 operations by using the
8520 public-domain Ed25519-donna by Andrew M. ("floodyberry").
8521 Implements ticket 16467.
8522 - Improve the runtime speed of the ntor handshake by using an
8523 optimized curve25519 basepoint scalarmult implementation from the
8524 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
8525 ideas by Adam Langley. Implements ticket 9663.
8527 o Major bugfixes (client-side privacy, also in 0.2.6.9):
8528 - Properly separate out each SOCKSPort when applying stream
8529 isolation. The error occurred because each port's session group
8530 was being overwritten by a default value when the listener
8531 connection was initialized. Fixes bug 16247; bugfix on
8532 0.2.6.3-alpha. Patch by "jojelino".
8534 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
8535 - Stop refusing to store updated hidden service descriptors on a
8536 client. This reverts commit 9407040c59218 (which indeed fixed bug
8537 14219, but introduced a major hidden service reachability
8538 regression detailed in bug 16381). This is a temporary fix since
8539 we can live with the minor issue in bug 14219 (it just results in
8540 some load on the network) but the regression of 16381 is too much
8541 of a setback. First-round fix for bug 16381; bugfix
8544 o Major bugfixes (hidden services):
8545 - When cannibalizing a circuit for an introduction point, always
8546 extend to the chosen exit node (creating a 4 hop circuit).
8547 Previously Tor would use the current circuit exit node, which
8548 changed the original choice of introduction point, and could cause
8549 the hidden service to skip excluded introduction points or
8550 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
8553 o Major bugfixes (open file limit):
8554 - The open file limit wasn't checked before calling
8555 tor_accept_socket_nonblocking(), which would make Tor exceed the
8556 limit. Now, before opening a new socket, Tor validates the open
8557 file limit just before, and if the max has been reached, return an
8558 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
8560 o Major bugfixes (stability, also in 0.2.6.10):
8561 - Stop crashing with an assertion failure when parsing certain kinds
8562 of malformed or truncated microdescriptors. Fixes bug 16400;
8563 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
8564 by "cypherpunks_backup".
8565 - Stop random client-side assertion failures that could occur when
8566 connecting to a busy hidden service, or connecting to a hidden
8567 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
8570 o Minor features (directory authorities, security, also in 0.2.6.9):
8571 - The HSDir flag given by authorities now requires the Stable flag.
8572 For the current network, this results in going from 2887 to 2806
8573 HSDirs. Also, it makes it harder for an attacker to launch a sybil
8574 attack by raising the effort for a relay to become Stable to
8575 require at the very least 7 days, while maintaining the 96 hours
8576 uptime requirement for HSDir. Implements ticket 8243.
8578 o Minor features (client):
8579 - Relax the validation of hostnames in SOCKS5 requests, allowing the
8580 character '_' to appear, in order to cope with domains observed in
8581 the wild that are serving non-RFC compliant records. Resolves
8583 - Relax the validation done to hostnames in SOCKS5 requests, and
8584 allow a single trailing '.' to cope with clients that pass FQDNs
8585 using that syntax to explicitly indicate that the domain name is
8586 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
8587 - Add GroupWritable and WorldWritable options to unix-socket based
8588 SocksPort and ControlPort options. These options apply to a single
8589 socket, and override {Control,Socks}SocketsGroupWritable. Closes
8592 o Minor features (control protocol):
8593 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
8594 the control protocol. Resolves ticket 15358.
8596 o Minor features (directory authorities):
8597 - Directory authorities no longer vote against the "Fast", "Stable",
8598 and "HSDir" flags just because they were going to vote against
8599 "Running": if the consensus turns out to be that the router was
8600 running, then the authority's vote should count. Patch from Peter
8601 Retzlaff; closes issue 8712.
8603 o Minor features (geoip, also in 0.2.6.10):
8604 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
8605 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
8607 o Minor features (hidden services):
8608 - Add the new options "HiddenServiceMaxStreams" and
8609 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
8610 limit the maximum number of simultaneous streams per circuit, and
8611 optionally tear down the circuit when the limit is exceeded. Part
8614 o Minor features (portability):
8615 - Use C99 variadic macros when the compiler is not GCC. This avoids
8616 failing compilations on MSVC, and fixes a log-file-based race
8617 condition in our old workarounds. Original patch from Gisle Vanem.
8619 o Minor bugfixes (compilation, also in 0.2.6.9):
8620 - Build with --enable-systemd correctly when libsystemd is
8621 installed, but systemd is not. Fixes bug 16164; bugfix on
8622 0.2.6.3-alpha. Patch from Peter Palfrader.
8624 o Minor bugfixes (controller):
8625 - Add the descriptor ID in each HS_DESC control event. It was
8626 missing, but specified in control-spec.txt. Fixes bug 15881;
8627 bugfix on 0.2.5.2-alpha.
8629 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
8630 - Check for failures from crypto_early_init, and refuse to continue.
8631 A previous typo meant that we could keep going with an
8632 uninitialized crypto library, and would have OpenSSL initialize
8633 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8634 when implementing ticket 4900. Patch by "teor".
8636 o Minor bugfixes (hidden services):
8637 - Fix a crash when reloading configuration while at least one
8638 configured and one ephemeral hidden service exists. Fixes bug
8639 16060; bugfix on 0.2.7.1-alpha.
8640 - Avoid crashing with a double-free bug when we create an ephemeral
8641 hidden service but adding it fails for some reason. Fixes bug
8642 16228; bugfix on 0.2.7.1-alpha.
8644 o Minor bugfixes (Linux seccomp2 sandbox):
8645 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
8646 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
8648 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
8649 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
8650 these when eventfd2() support is missing. Fixes bug 16363; bugfix
8651 on 0.2.6.3-alpha. Patch from "teor".
8653 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
8654 - Fix sandboxing to work when running as a relay, by allowing the
8655 renaming of secret_id_key, and allowing the eventfd2 and futex
8656 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
8658 - Allow systemd connections to work with the Linux seccomp2 sandbox
8659 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
8662 o Minor bugfixes (relay):
8663 - Fix a rarely-encountered memory leak when failing to initialize
8664 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
8667 o Minor bugfixes (systemd):
8668 - Fix an accidental formatting error that broke the systemd
8669 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
8670 - Tor's systemd unit file no longer contains extraneous spaces.
8671 These spaces would sometimes confuse tools like deb-systemd-
8672 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
8674 o Minor bugfixes (tests):
8675 - Use the configured Python executable when running test-stem-full.
8676 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
8678 o Minor bugfixes (tests, also in 0.2.6.9):
8679 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
8680 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
8682 o Minor bugfixes (threads, comments):
8683 - Always initialize return value in compute_desc_id in rendcommon.c
8684 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
8685 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
8686 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
8687 - Remove undefined directive-in-macro in test_util_writepid clang
8688 3.7 complains that using a preprocessor directive inside a macro
8689 invocation in test_util_writepid in test_util.c is undefined.
8690 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
8692 o Code simplification and refactoring:
8693 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
8694 to ensure they remain consistent and visible everywhere.
8695 - Remove some vestigial workarounds for the MSVC6 compiler. We
8696 haven't supported that in ages.
8697 - The link authentication code has been refactored for better
8698 testability and reliability. It now uses code generated with the
8699 "trunnel" binary encoding generator, to reduce the risk of bugs
8700 due to programmer error. Done as part of ticket 12498.
8703 - Include a specific and (hopefully) accurate documentation of the
8704 torrc file's meta-format in doc/torrc_format.txt. This is mainly
8705 of interest to people writing programs to parse or generate torrc
8706 files. This document is not a commitment to long-term
8707 compatibility; some aspects of the current format are a bit
8708 ridiculous. Closes ticket 2325.
8711 - Tor no longer supports copies of OpenSSL that are missing support
8712 for Elliptic Curve Cryptography. (We began using ECC when
8713 available in 0.2.4.8-alpha, for more safe and efficient key
8714 negotiation.) In particular, support for at least one of P256 or
8715 P224 is now required, with manual configuration needed if only
8716 P224 is available. Resolves ticket 16140.
8717 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
8718 on an operating system that has not upgraded to OpenSSL 1.0 or
8719 later, and you compile Tor from source, you will need to install a
8720 more recent OpenSSL to link Tor against.) These versions of
8721 OpenSSL are still supported by the OpenSSL, but the numerous
8722 cryptographic improvements in later OpenSSL releases makes them a
8723 clear choice. Resolves ticket 16034.
8724 - Remove the HidServDirectoryV2 option. Now all relays offer to
8725 store hidden service descriptors. Related to 16543.
8726 - Remove the VoteOnHidServDirectoriesV2 option, since all
8727 authorities have long set it to 1. Closes ticket 16543.
8730 - Document use of coverity, clang static analyzer, and clang dynamic
8731 undefined behavior and address sanitizers in doc/HACKING. Include
8732 detailed usage instructions in the blacklist. Patch by "teor".
8733 Closes ticket 15817.
8734 - The link authentication protocol code now has extensive tests.
8735 - The relay descriptor signature testing code now has
8737 - The test_workqueue program now runs faster, and is enabled by
8738 default as a part of "make check".
8739 - Now that OpenSSL has its own scrypt implementation, add an unit
8740 test that checks for interoperability between libscrypt_scrypt()
8741 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
8742 and rely on EVP_PBE_scrypt() whenever possible. Resolves
8746 Changes in version 0.2.6.10 - 2015-07-12
8747 Tor version 0.2.6.10 fixes some significant stability and hidden
8748 service client bugs, bulletproofs the cryptography init process, and
8749 fixes a bug when using the sandbox code with some older versions of
8750 Linux. Everyone running an older version, especially an older version
8751 of 0.2.6, should upgrade.
8753 o Major bugfixes (hidden service clients, stability):
8754 - Stop refusing to store updated hidden service descriptors on a
8755 client. This reverts commit 9407040c59218 (which indeed fixed bug
8756 14219, but introduced a major hidden service reachability
8757 regression detailed in bug 16381). This is a temporary fix since
8758 we can live with the minor issue in bug 14219 (it just results in
8759 some load on the network) but the regression of 16381 is too much
8760 of a setback. First-round fix for bug 16381; bugfix
8763 o Major bugfixes (stability):
8764 - Stop crashing with an assertion failure when parsing certain kinds
8765 of malformed or truncated microdescriptors. Fixes bug 16400;
8766 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
8767 by "cypherpunks_backup".
8768 - Stop random client-side assertion failures that could occur when
8769 connecting to a busy hidden service, or connecting to a hidden
8770 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
8773 o Minor features (geoip):
8774 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
8775 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
8777 o Minor bugfixes (crypto error-handling):
8778 - Check for failures from crypto_early_init, and refuse to continue.
8779 A previous typo meant that we could keep going with an
8780 uninitialized crypto library, and would have OpenSSL initialize
8781 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8782 when implementing ticket 4900. Patch by "teor".
8784 o Minor bugfixes (Linux seccomp2 sandbox):
8785 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
8786 these when eventfd2() support is missing. Fixes bug 16363; bugfix
8787 on 0.2.6.3-alpha. Patch from "teor".
8790 Changes in version 0.2.6.9 - 2015-06-11
8791 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
8792 requirements for receiving an HSDir flag, and addresses some other small
8793 bugs in the systemd and sandbox code. Clients using circuit isolation
8794 should upgrade; all directory authorities should upgrade.
8796 o Major bugfixes (client-side privacy):
8797 - Properly separate out each SOCKSPort when applying stream
8798 isolation. The error occurred because each port's session group was
8799 being overwritten by a default value when the listener connection
8800 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
8803 o Minor feature (directory authorities, security):
8804 - The HSDir flag given by authorities now requires the Stable flag.
8805 For the current network, this results in going from 2887 to 2806
8806 HSDirs. Also, it makes it harder for an attacker to launch a sybil
8807 attack by raising the effort for a relay to become Stable which
8808 takes at the very least 7 days to do so and by keeping the 96
8809 hours uptime requirement for HSDir. Implements ticket 8243.
8811 o Minor bugfixes (compilation):
8812 - Build with --enable-systemd correctly when libsystemd is
8813 installed, but systemd is not. Fixes bug 16164; bugfix on
8814 0.2.6.3-alpha. Patch from Peter Palfrader.
8816 o Minor bugfixes (Linux seccomp2 sandbox):
8817 - Fix sandboxing to work when running as a relaymby renaming of
8818 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
8819 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
8820 - Allow systemd connections to work with the Linux seccomp2 sandbox
8821 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
8824 o Minor bugfixes (tests):
8825 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
8826 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
8829 Changes in version 0.2.6.8 - 2015-05-21
8830 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
8831 fixes an authority-side bug in assigning the HSDir flag. All directory
8832 authorities should upgrade.
8834 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
8835 - Revert commit that made directory authorities assign the HSDir
8836 flag to relays without a DirPort; this was bad because such relays
8837 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
8840 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8841 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8842 a client authorized hidden service. Fixes bug 15823; bugfix
8845 o Minor features (geoip):
8846 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
8847 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
8851 Changes in version 0.2.7.1-alpha - 2015-05-12
8852 Tor 0.2.7.1-alpha is the first alpha release in its series. It
8853 includes numerous small features and bugfixes against previous Tor
8854 versions, and numerous small infrastructure improvements. The most
8855 notable features are several new ways for controllers to interact with
8856 the hidden services subsystem.
8858 o New system requirements:
8859 - Tor no longer includes workarounds to support Libevent versions
8860 before 1.3e. Libevent 2.0 or later is recommended. Closes
8863 o Major features (controller):
8864 - Add the ADD_ONION and DEL_ONION commands that allow the creation
8865 and management of hidden services via the controller. Closes
8867 - New "GETINFO onions/current" and "GETINFO onions/detached"
8868 commands to get information about hidden services created via the
8869 controller. Part of ticket 6411.
8870 - New HSFETCH command to launch a request for a hidden service
8871 descriptor. Closes ticket 14847.
8872 - New HSPOST command to upload a hidden service descriptor. Closes
8873 ticket 3523. Patch by "DonnchaC".
8875 o Major bugfixes (hidden services):
8876 - Revert commit that made directory authorities assign the HSDir
8877 flag to relays without a DirPort; this was bad because such relays
8878 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
8881 o Minor features (clock-jump tolerance):
8882 - Recover better when our clock jumps back many hours, like might
8883 happen for Tails or Whonix users who start with a very wrong
8884 hardware clock, use Tor to discover a more accurate time, and then
8885 fix their clock. Resolves part of ticket 8766.
8887 o Minor features (command-line interface):
8888 - Make --hash-password imply --hush to prevent unnecessary noise.
8889 Closes ticket 15542. Patch from "cypherpunks".
8890 - Print a warning whenever we find a relative file path being used
8891 as torrc option. Resolves issue 14018.
8893 o Minor features (controller):
8894 - Add DirAuthority lines for default directory authorities to the
8895 output of the "GETINFO config/defaults" command if not already
8896 present. Implements ticket 14840.
8897 - Controllers can now use "GETINFO hs/client/desc/id/..." to
8898 retrieve items from the client's hidden service descriptor cache.
8899 Closes ticket 14845.
8900 - Implement a new controller command "GETINFO status/fresh-relay-
8901 descs" to fetch a descriptor/extrainfo pair that was generated on
8902 demand just for the controller's use. Implements ticket 14784.
8904 o Minor features (DoS-resistance):
8905 - Make it harder for attackers to overload hidden services with
8906 introductions, by blocking multiple introduction requests on the
8907 same circuit. Resolves ticket 15515.
8909 o Minor features (geoip):
8910 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
8911 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
8914 o Minor features (HS popularity countermeasure):
8915 - To avoid leaking HS popularity, don't cycle the introduction point
8916 when we've handled a fixed number of INTRODUCE2 cells but instead
8917 cycle it when a random number of introductions is reached, thus
8918 making it more difficult for an attacker to find out the amount of
8919 clients that have used the introduction point for a specific HS.
8920 Closes ticket 15745.
8922 o Minor features (logging):
8923 - Include the Tor version in all LD_BUG log messages, since people
8924 tend to cut and paste those into the bugtracker. Implements
8927 o Minor features (pluggable transports):
8928 - When launching managed pluggable transports on Linux systems,
8929 attempt to have the kernel deliver a SIGTERM on tor exit if the
8930 pluggable transport process is still running. Resolves
8932 - When launching managed pluggable transports, setup a valid open
8933 stdin in the child process that can be used to detect if tor has
8934 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
8935 can be used by implementations to detect this new behavior.
8936 Resolves ticket 15435.
8938 o Minor features (testing):
8939 - Add a test to verify that the compiler does not eliminate our
8940 memwipe() implementation. Closes ticket 15377.
8941 - Add make rule `check-changes` to verify the format of changes
8942 files. Closes ticket 15180.
8943 - Add unit tests for control_event_is_interesting(). Add a compile-
8944 time check that the number of events doesn't exceed the capacity
8945 of control_event_t.event_mask. Closes ticket 15431, checks for
8946 bugs similar to 13085. Patch by "teor".
8947 - Command-line argument tests moved to Stem. Resolves ticket 14806.
8948 - Integrate the ntor, backtrace, and zero-length keys tests into the
8949 automake test suite. Closes ticket 15344.
8950 - Remove assertions during builds to determine Tor's test coverage.
8951 We don't want to trigger these even in assertions, so including
8952 them artificially makes our branch coverage look worse than it is.
8953 This patch provides the new test-stem-full and coverage-html-full
8954 configure options. Implements ticket 15400.
8956 o Minor bugfixes (build):
8957 - Improve out-of-tree builds by making non-standard rules work and
8958 clean up additional files and directories. Fixes bug 15053; bugfix
8961 o Minor bugfixes (command-line interface):
8962 - When "--quiet" is provided along with "--validate-config", do not
8963 write anything to stdout on success. Fixes bug 14994; bugfix
8965 - When complaining about bad arguments to "--dump-config", use
8968 o Minor bugfixes (configuration, unit tests):
8969 - Only add the default fallback directories when the DirAuthorities,
8970 AlternateDirAuthority, and FallbackDir directory config options
8971 are set to their defaults. The default fallback directory list is
8972 currently empty, this fix will only change tor's behavior when it
8973 has default fallback directories. Includes unit tests for
8974 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
8975 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
8977 o Minor bugfixes (correctness):
8978 - For correctness, avoid modifying a constant string in
8979 handle_control_postdescriptor. Fixes bug 15546; bugfix
8981 - Remove side-effects from tor_assert() calls. This was harmless,
8982 because we never disable assertions, but it is bad style and
8983 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
8986 o Minor bugfixes (hidden service):
8987 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8988 a client authorized hidden service. Fixes bug 15823; bugfix
8990 - Remove an extraneous newline character from the end of hidden
8991 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
8993 o Minor bugfixes (interface):
8994 - Print usage information for --dump-config when it is used without
8995 an argument. Also, fix the error message to use different wording
8996 and add newline at the end. Fixes bug 15541; bugfix
8999 o Minor bugfixes (logs):
9000 - When building Tor under Clang, do not include an extra set of
9001 parentheses in log messages that include function names. Fixes bug
9002 15269; bugfix on every released version of Tor when compiled with
9003 recent enough Clang.
9005 o Minor bugfixes (network):
9006 - When attempting to use fallback technique for network interface
9007 lookup, disregard loopback and multicast addresses since they are
9008 unsuitable for public communications.
9010 o Minor bugfixes (statistics):
9011 - Disregard the ConnDirectionStatistics torrc options when Tor is
9012 not a relay since in that mode of operation no sensible data is
9013 being collected and because Tor might run into measurement hiccups
9014 when running as a client for some time, then becoming a relay.
9015 Fixes bug 15604; bugfix on 0.2.2.35.
9017 o Minor bugfixes (test networks):
9018 - When self-testing reachability, use ExtendAllowPrivateAddresses to
9019 determine if local/private addresses imply reachability. The
9020 previous fix used TestingTorNetwork, which implies
9021 ExtendAllowPrivateAddresses, but this excluded rare configurations
9022 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
9023 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
9024 issue discovered by CJ Ess.
9026 o Minor bugfixes (testing):
9027 - Check for matching value in server response in ntor_ref.py. Fixes
9028 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
9030 - Set the severity correctly when testing
9031 get_interface_addresses_ifaddrs() and
9032 get_interface_addresses_win32(), so that the tests fail gracefully
9033 instead of triggering an assertion. Fixes bug 15759; bugfix on
9034 0.2.6.3-alpha. Reported by Nicolas Derive.
9036 o Code simplification and refactoring:
9037 - Move the hacky fallback code out of get_interface_address6() into
9038 separate function and get it covered with unit-tests. Resolves
9040 - Refactor hidden service client-side cache lookup to intelligently
9041 report its various failure cases, and disentangle failure cases
9042 involving a lack of introduction points. Closes ticket 14391.
9043 - Use our own Base64 encoder instead of OpenSSL's, to allow more
9044 control over the output. Part of ticket 15652.
9047 - Improve the descriptions of statistics-related torrc options in
9048 the manpage to describe rationale and possible uses cases. Fixes
9050 - Improve the layout and formatting of ./configure --help messages.
9051 Closes ticket 15024. Patch from "cypherpunks".
9052 - Standardize on the term "server descriptor" in the manual page.
9053 Previously, we had used "router descriptor", "server descriptor",
9054 and "relay descriptor" interchangeably. Part of ticket 14987.
9057 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
9058 and always use the internal Base64 decoder. The internal decoder
9059 has been part of tor since 0.2.0.10-alpha, and no one should
9060 be using the OpenSSL one. Part of ticket 15652.
9061 - Remove the 'tor_strclear()' function; use memwipe() instead.
9062 Closes ticket 14922.
9065 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
9066 fingerprinting we now recommend pluggable transports; for forward-
9067 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
9068 - Remove the undocumented "--digests" command-line option. It
9069 complicated our build process, caused subtle build issues on
9070 multiple platforms, and is now redundant since we started
9071 including git version identifiers. Closes ticket 14742.
9072 - Tor no longer contains checks for ancient directory cache versions
9073 that didn't know about microdescriptors.
9074 - Tor no longer contains workarounds for stat files generated by
9075 super-old versions of Tor that didn't choose guards sensibly.
9078 Changes in version 0.2.4.27 - 2015-04-06
9079 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
9080 could be used by an attacker to crash hidden services, or crash clients
9081 visiting hidden services. Hidden services should upgrade as soon as
9082 possible; clients should upgrade whenever packages become available.
9084 This release also backports a simple improvement to make hidden
9085 services a bit less vulnerable to denial-of-service attacks.
9087 o Major bugfixes (security, hidden service):
9088 - Fix an issue that would allow a malicious client to trigger an
9089 assertion failure and halt a hidden service. Fixes bug 15600;
9090 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9091 - Fix a bug that could cause a client to crash with an assertion
9092 failure when parsing a malformed hidden service descriptor. Fixes
9093 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9095 o Minor features (DoS-resistance, hidden service):
9096 - Introduction points no longer allow multiple INTRODUCE1 cells to
9097 arrive on the same circuit. This should make it more expensive for
9098 attackers to overwhelm hidden services with introductions.
9099 Resolves ticket 15515.
9102 Changes in version 0.2.5.12 - 2015-04-06
9103 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
9104 could be used by an attacker to crash hidden services, or crash clients
9105 visiting hidden services. Hidden services should upgrade as soon as
9106 possible; clients should upgrade whenever packages become available.
9108 This release also backports a simple improvement to make hidden
9109 services a bit less vulnerable to denial-of-service attacks.
9111 o Major bugfixes (security, hidden service):
9112 - Fix an issue that would allow a malicious client to trigger an
9113 assertion failure and halt a hidden service. Fixes bug 15600;
9114 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9115 - Fix a bug that could cause a client to crash with an assertion
9116 failure when parsing a malformed hidden service descriptor. Fixes
9117 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9119 o Minor features (DoS-resistance, hidden service):
9120 - Introduction points no longer allow multiple INTRODUCE1 cells to
9121 arrive on the same circuit. This should make it more expensive for
9122 attackers to overwhelm hidden services with introductions.
9123 Resolves ticket 15515.
9126 Changes in version 0.2.6.7 - 2015-04-06
9127 Tor 0.2.6.7 fixes two security issues that could be used by an
9128 attacker to crash hidden services, or crash clients visiting hidden
9129 services. Hidden services should upgrade as soon as possible; clients
9130 should upgrade whenever packages become available.
9132 This release also contains two simple improvements to make hidden
9133 services a bit less vulnerable to denial-of-service attacks.
9135 o Major bugfixes (security, hidden service):
9136 - Fix an issue that would allow a malicious client to trigger an
9137 assertion failure and halt a hidden service. Fixes bug 15600;
9138 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9139 - Fix a bug that could cause a client to crash with an assertion
9140 failure when parsing a malformed hidden service descriptor. Fixes
9141 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9143 o Minor features (DoS-resistance, hidden service):
9144 - Introduction points no longer allow multiple INTRODUCE1 cells to
9145 arrive on the same circuit. This should make it more expensive for
9146 attackers to overwhelm hidden services with introductions.
9147 Resolves ticket 15515.
9148 - Decrease the amount of reattempts that a hidden service performs
9149 when its rendezvous circuits fail. This reduces the computational
9150 cost for running a hidden service under heavy load. Resolves
9154 Changes in version 0.2.6.6 - 2015-03-24
9155 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
9157 It adds numerous safety, security, correctness, and performance
9158 improvements. Client programs can be configured to use more kinds of
9159 sockets, AutomapHosts works better, the multithreading backend is
9160 improved, cell transmission is refactored, test coverage is much
9161 higher, more denial-of-service attacks are handled, guard selection is
9162 improved to handle long-term guards better, pluggable transports
9163 should work a bit better, and some annoying hidden service performance
9164 bugs should be addressed.
9166 o Minor bugfixes (portability):
9167 - Use the correct datatype in the SipHash-2-4 function to prevent
9168 compilers from assuming any sort of alignment. Fixes bug 15436;
9169 bugfix on 0.2.5.3-alpha.
9171 Changes in version 0.2.6.5-rc - 2015-03-18
9172 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
9173 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
9175 o Major bugfixes (client):
9176 - Avoid crashing when making certain configuration option changes on
9177 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
9180 o Major bugfixes (pluggable transports):
9181 - Initialize the extended OR Port authentication cookie before
9182 launching pluggable transports. This prevents a race condition
9183 that occurred when server-side pluggable transports would cache the
9184 authentication cookie before it has been (re)generated. Fixes bug
9185 15240; bugfix on 0.2.5.1-alpha.
9187 o Major bugfixes (portability):
9188 - Do not crash on startup when running on Solaris. Fixes a bug
9189 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
9192 o Minor features (heartbeat):
9193 - On relays, report how many connections we negotiated using each
9194 version of the Tor link protocols. This information will let us
9195 know if removing support for very old versions of the Tor
9196 protocols is harming the network. Closes ticket 15212.
9198 o Code simplification and refactoring:
9199 - Refactor main loop to extract the 'loop' part. This makes it
9200 easier to run Tor under Shadow. Closes ticket 15176.
9203 Changes in version 0.2.5.11 - 2015-03-17
9204 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
9206 It backports several bugfixes from the 0.2.6 branch, including a
9207 couple of medium-level security fixes for relays and exit nodes.
9208 It also updates the list of directory authorities.
9210 o Directory authority changes:
9211 - Remove turtles as a directory authority.
9212 - Add longclaw as a new (v3) directory authority. This implements
9213 ticket 13296. This keeps the directory authority count at 9.
9214 - The directory authority Faravahar has a new IP address. This
9215 closes ticket 14487.
9217 o Major bugfixes (crash, OSX, security):
9218 - Fix a remote denial-of-service opportunity caused by a bug in
9219 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
9222 o Major bugfixes (relay, stability, possible security):
9223 - Fix a bug that could lead to a relay crashing with an assertion
9224 failure if a buffer of exactly the wrong layout was passed to
9225 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9226 0.2.0.10-alpha. Patch from 'cypherpunks'.
9227 - Do not assert if the 'data' pointer on a buffer is advanced to the
9228 very end of the buffer; log a BUG message instead. Only assert if
9229 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9231 o Major bugfixes (exit node stability):
9232 - Fix an assertion failure that could occur under high DNS load.
9233 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9234 diagnosed and fixed by "cypherpunks".
9236 o Major bugfixes (Linux seccomp2 sandbox):
9237 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
9238 crash during attempts to call wait4. Fixes bug 15088; bugfix on
9239 0.2.5.1-alpha. Patch from "sanic".
9241 o Minor features (controller):
9242 - New "GETINFO bw-event-cache" to get information about recent
9243 bandwidth events. Closes ticket 14128. Useful for controllers to
9244 get recent bandwidth history after the fix for ticket 13988.
9246 o Minor features (geoip):
9247 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9248 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9251 o Minor bugfixes (client, automapping):
9252 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
9253 no value follows the option. Fixes bug 14142; bugfix on
9254 0.2.4.7-alpha. Patch by "teor".
9255 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
9256 14195; bugfix on 0.1.0.1-rc.
9258 o Minor bugfixes (compilation):
9259 - Build without warnings with the stock OpenSSL srtp.h header, which
9260 has a duplicate declaration of SSL_get_selected_srtp_profile().
9261 Fixes bug 14220; this is OpenSSL's bug, not ours.
9263 o Minor bugfixes (directory authority):
9264 - Allow directory authorities to fetch more data from one another if
9265 they find themselves missing lots of votes. Previously, they had
9266 been bumping against the 10 MB queued data limit. Fixes bug 14261;
9267 bugfix on 0.1.2.5-alpha.
9268 - Enlarge the buffer to read bwauth generated files to avoid an
9269 issue when parsing the file in dirserv_read_measured_bandwidths().
9270 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
9272 o Minor bugfixes (statistics):
9273 - Increase period over which bandwidth observations are aggregated
9274 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9276 o Minor bugfixes (preventative security, C safety):
9277 - When reading a hexadecimal, base-32, or base-64 encoded value from
9278 a string, always overwrite the whole output buffer. This prevents
9279 some bugs where we would look at (but fortunately, not reveal)
9280 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
9284 Changes in version 0.2.4.26 - 2015-03-17
9285 Tor 0.2.4.26 includes an updated list of directory authorities. It
9286 also backports a couple of stability and security bugfixes from 0.2.5
9289 o Directory authority changes:
9290 - Remove turtles as a directory authority.
9291 - Add longclaw as a new (v3) directory authority. This implements
9292 ticket 13296. This keeps the directory authority count at 9.
9293 - The directory authority Faravahar has a new IP address. This
9294 closes ticket 14487.
9296 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
9297 - Fix an assertion failure that could occur under high DNS load.
9298 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9299 diagnosed and fixed by "cypherpunks".
9301 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
9302 - Fix a bug that could lead to a relay crashing with an assertion
9303 failure if a buffer of exactly the wrong layout was passed to
9304 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9305 0.2.0.10-alpha. Patch from 'cypherpunks'.
9306 - Do not assert if the 'data' pointer on a buffer is advanced to the
9307 very end of the buffer; log a BUG message instead. Only assert if
9308 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9310 o Minor features (geoip):
9311 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9312 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9315 Changes in version 0.2.6.4-rc - 2015-03-09
9316 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
9317 attacker might be able to use in order to crash certain Tor
9318 directories. It also resolves some minor issues left over from, or
9319 introduced in, Tor 0.2.6.3-alpha or earlier.
9321 o Major bugfixes (crash, OSX, security):
9322 - Fix a remote denial-of-service opportunity caused by a bug in
9323 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
9326 o Major bugfixes (relay, stability, possible security):
9327 - Fix a bug that could lead to a relay crashing with an assertion
9328 failure if a buffer of exactly the wrong layout is passed to
9329 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9330 0.2.0.10-alpha. Patch from "cypherpunks".
9331 - Do not assert if the 'data' pointer on a buffer is advanced to the
9332 very end of the buffer; log a BUG message instead. Only assert if
9333 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9335 o Major bugfixes (FreeBSD IPFW transparent proxy):
9336 - Fix address detection with FreeBSD transparent proxies, when
9337 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
9340 o Major bugfixes (Linux seccomp2 sandbox):
9341 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
9342 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
9344 - Allow AF_UNIX hidden services to be used with the seccomp2
9345 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
9346 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
9347 crash during attempts to call wait4. Fixes bug 15088; bugfix on
9348 0.2.5.1-alpha. Patch from "sanic".
9350 o Minor features (controller):
9351 - Messages about problems in the bootstrap process now include
9352 information about the server we were trying to connect to when we
9353 noticed the problem. Closes ticket 15006.
9355 o Minor features (geoip):
9356 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9357 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9360 o Minor features (logs):
9361 - Quiet some log messages in the heartbeat and at startup. Closes
9364 o Minor bugfixes (certificate handling):
9365 - If an authority operator accidentally makes a signing certificate
9366 with a future publication time, do not discard its real signing
9367 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
9368 - Remove any old authority certificates that have been superseded
9369 for at least two days. Previously, we would keep superseded
9370 certificates until they expired, if they were published close in
9371 time to the certificate that superseded them. Fixes bug 11454;
9372 bugfix on 0.2.1.8-alpha.
9374 o Minor bugfixes (compilation):
9375 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
9377 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
9380 o Minor bugfixes (testing):
9381 - Fix endianness issues in unit test for resolve_my_address() to
9382 have it pass on big endian systems. Fixes bug 14980; bugfix on
9384 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
9385 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
9386 - When running the new 'make test-stem' target, use the configured
9387 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
9389 - When running the zero-length-keys tests, do not use the default
9390 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
9393 o Directory authority IP change:
9394 - The directory authority Faravahar has a new IP address. This
9395 closes ticket 14487.
9398 - Remove some lingering dead code that once supported mempools.
9399 Mempools were disabled by default in 0.2.5, and removed entirely
9400 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
9404 Changes in version 0.2.6.3-alpha - 2015-02-19
9405 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
9406 the 0.2.6.x series. It introduces support for more kinds of sockets,
9407 makes it harder to accidentally run an exit, improves our
9408 multithreading backend, incorporates several fixes for the
9409 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
9411 If no major regressions or security holes are found in this version,
9412 the next version will be a release candidate.
9414 o Deprecated versions:
9415 - Tor relays older than 0.2.4.18-rc are no longer allowed to
9416 advertise themselves on the network. Closes ticket 13555.
9418 o Major features (security, unix domain sockets):
9419 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
9420 applications can reach Tor without having to create AF_INET or
9421 AF_INET6 sockets, meaning they can completely disable their
9422 ability to make non-Tor network connections. To create a socket of
9423 this type, use "SocksPort unix:/path/to/socket". Implements
9425 - Support mapping hidden service virtual ports to AF_UNIX sockets.
9426 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
9427 Implements ticket 11485.
9429 o Major features (changed defaults):
9430 - Prevent relay operators from unintentionally running exits: When a
9431 relay is configured as an exit node, we now warn the user unless
9432 the "ExitRelay" option is set to 1. We warn even more loudly if
9433 the relay is configured with the default exit policy, since this
9434 can indicate accidental misconfiguration. Setting "ExitRelay 0"
9435 stops Tor from running as an exit relay. Closes ticket 10067.
9437 o Major features (directory system):
9438 - When downloading server- or microdescriptors from a directory
9439 server, we no longer launch multiple simultaneous requests to the
9440 same server. This reduces load on the directory servers,
9441 especially when directory guards are in use. Closes ticket 9969.
9442 - When downloading server- or microdescriptors over a tunneled
9443 connection, do not limit the length of our requests to what the
9444 Squid proxy is willing to handle. Part of ticket 9969.
9445 - Authorities can now vote on the correct digests and latest
9446 versions for different software packages. This allows packages
9447 that include Tor to use the Tor authority system as a way to get
9448 notified of updates and their correct digests. Implements proposal
9449 227. Closes ticket 10395.
9451 o Major features (guards):
9452 - Introduce the Guardfraction feature to improves load balancing on
9453 guard nodes. Specifically, it aims to reduce the traffic gap that
9454 guard nodes experience when they first get the Guard flag. This is
9455 a required step if we want to increase the guard lifetime to 9
9456 months or greater. Closes ticket 9321.
9458 o Major features (performance):
9459 - Make the CPU worker implementation more efficient by avoiding the
9460 kernel and lengthening pipelines. The original implementation used
9461 sockets to transfer data from the main thread to the workers, and
9462 didn't allow any thread to be assigned more than a single piece of
9463 work at once. The new implementation avoids communications
9464 overhead by making requests in shared memory, avoiding kernel IO
9465 where possible, and keeping more requests in flight at once.
9466 Implements ticket 9682.
9468 o Major features (relay):
9469 - Raise the minimum acceptable configured bandwidth rate for bridges
9470 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
9471 20 KiB/sec.) Closes ticket 13822.
9473 o Major bugfixes (exit node stability):
9474 - Fix an assertion failure that could occur under high DNS load.
9475 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9476 diagnosed and fixed by "cypherpunks".
9478 o Major bugfixes (mixed relay-client operation):
9479 - When running as a relay and client at the same time (not
9480 recommended), if we decide not to use a new guard because we want
9481 to retry older guards, only close the locally-originating circuits
9482 passing through that guard. Previously we would close all the
9483 circuits through that guard. Fixes bug 9819; bugfix on
9484 0.2.1.1-alpha. Reported by "skruffy".
9486 o Minor features (build):
9487 - New --disable-system-torrc compile-time option to prevent Tor from
9488 looking for the system-wide torrc or torrc-defaults files.
9489 Resolves ticket 13037.
9491 o Minor features (controller):
9492 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
9493 events so controllers can observe circuit isolation inputs. Closes
9495 - ControlPort now supports the unix:/path/to/socket syntax as an
9496 alternative to the ControlSocket option, for consistency with
9497 SocksPort and HiddenServicePort. Closes ticket 14451.
9498 - New "GETINFO bw-event-cache" to get information about recent
9499 bandwidth events. Closes ticket 14128. Useful for controllers to
9500 get recent bandwidth history after the fix for ticket 13988.
9502 o Minor features (Denial of service resistance):
9503 - Count the total number of bytes used storing hidden service
9504 descriptors against the value of MaxMemInQueues. If we're low on
9505 memory, and more than 20% of our memory is used holding hidden
9506 service descriptors, free them until no more than 10% of our
9507 memory holds hidden service descriptors. Free the least recently
9508 fetched descriptors first. Resolves ticket 13806.
9509 - When we have recently been under memory pressure (over 3/4 of
9510 MaxMemInQueues is allocated), then allocate smaller zlib objects
9511 for small requests. Closes ticket 11791.
9513 o Minor features (geoip):
9514 - Update geoip and geoip6 files to the January 7 2015 Maxmind
9515 GeoLite2 Country database.
9517 o Minor features (guard nodes):
9518 - Reduce the time delay before saving guard status to disk from 10
9519 minutes to 30 seconds (or from one hour to 10 minutes if
9520 AvoidDiskWrites is set). Closes ticket 12485.
9522 o Minor features (hidden service):
9523 - Make Sybil attacks against hidden services harder by changing the
9524 minimum time required to get the HSDir flag from 25 hours up to 96
9525 hours. Addresses ticket 14149.
9526 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
9527 services to disable the anti-scanning feature introduced in
9528 0.2.6.2-alpha. With this option not set, a connection to an
9529 unlisted port closes the circuit. With this option set, only a
9530 RELAY_DONE cell is sent. Closes ticket 14084.
9532 o Minor features (interface):
9533 - Implement "-f -" command-line option to read torrc configuration
9534 from standard input, if you don't want to store the torrc file in
9535 the file system. Implements feature 13865.
9537 o Minor features (logging):
9538 - Add a count of unique clients to the bridge heartbeat message.
9539 Resolves ticket 6852.
9540 - Suppress "router info incompatible with extra info" message when
9541 reading extrainfo documents from cache. (This message got loud
9542 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
9544 - Elevate hidden service authorized-client message from DEBUG to
9545 INFO. Closes ticket 14015.
9547 o Minor features (stability):
9548 - Add assertions in our hash-table iteration code to check for
9549 corrupted values that could cause infinite loops. Closes
9552 o Minor features (systemd):
9553 - Various improvements and modernizations in systemd hardening
9554 support. Closes ticket 13805. Patch from Craig Andrews.
9556 o Minor features (testing networks):
9557 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
9558 and the default on a testing network to 2 minutes. Drop the
9559 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
9560 keep the default on a testing network at 30 seconds. This reduces
9561 HS bootstrap time to around 25 seconds. Also, change the default
9562 time in test-network.sh to match. Closes ticket 13401. Patch
9564 - Create TestingDirAuthVoteHSDir to correspond to
9565 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
9566 HSDir flag for the listed relays regardless of uptime or ORPort
9567 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
9568 Partial implementation for ticket 14067. Patch by "teor".
9570 o Minor features (tor2web mode):
9571 - Introduce the config option Tor2webRendezvousPoints, which allows
9572 clients in Tor2webMode to select a specific Rendezvous Point to be
9573 used in HS circuits. This might allow better performance for
9574 Tor2Web nodes. Implements ticket 12844.
9576 o Minor bugfixes (client DNS):
9577 - Report the correct cached DNS expiration times on SOCKS port or in
9578 DNS replies. Previously, we would report everything as "never
9579 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
9580 - Avoid a small memory leak when we find a cached answer for a
9581 reverse DNS lookup in a client-side DNS cache. (Remember, client-
9582 side DNS caching is off by default, and is not recommended.) Fixes
9583 bug 14259; bugfix on 0.2.0.1-alpha.
9585 o Minor bugfixes (client, automapping):
9586 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
9587 no value follows the option. Fixes bug 14142; bugfix on
9588 0.2.4.7-alpha. Patch by "teor".
9589 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
9590 14195; bugfix on 0.1.0.1-rc.
9591 - Prevent changes to other options from removing the wildcard value
9592 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
9594 - Allow MapAddress and AutomapHostsOnResolve to work together when
9595 an address is mapped into another address type (like .onion) that
9596 must be automapped at resolve time. Fixes bug 7555; bugfix
9599 o Minor bugfixes (client, bridges):
9600 - When we are using bridges and we had a network connectivity
9601 problem, only retry connecting to our currently configured
9602 bridges, not all bridges we know about and remember using. Fixes
9603 bug 14216; bugfix on 0.2.2.17-alpha.
9605 o Minor bugfixes (client, IPv6):
9606 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
9607 flag is not set; and not because the NoIPv4Traffic flag was set.
9608 Previously we'd looked at the NoIPv4Traffic flag for both types of
9609 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
9611 o Minor bugfixes (compilation):
9612 - The address of an array in the middle of a structure will always
9613 be non-NULL. clang recognises this and complains. Disable the
9614 tautologous and redundant check to silence this warning. Fixes bug
9615 14001; bugfix on 0.2.1.2-alpha.
9616 - Avoid warnings when building with systemd 209 or later. Fixes bug
9617 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
9618 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
9619 Addresses ticket 14188.
9620 - Build without warnings with the stock OpenSSL srtp.h header, which
9621 has a duplicate declaration of SSL_get_selected_srtp_profile().
9622 Fixes bug 14220; this is OpenSSL's bug, not ours.
9623 - Do not compile any code related to Tor2Web mode when Tor2Web mode
9624 is not enabled at compile time. Previously, this code was included
9625 in a disabled state. See discussion on ticket 12844.
9626 - Remove the --disable-threads configure option again. It was
9627 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
9628 14819; bugfix on 0.2.6.2-alpha.
9630 o Minor bugfixes (controller):
9631 - Report "down" in response to the "GETINFO entry-guards" command
9632 when relays are down with an unreachable_since value. Previously,
9633 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
9634 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
9635 14116; bugfix on 0.2.2.9-alpha.
9636 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
9637 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
9639 o Minor bugfixes (directory authority):
9640 - Allow directory authorities to fetch more data from one another if
9641 they find themselves missing lots of votes. Previously, they had
9642 been bumping against the 10 MB queued data limit. Fixes bug 14261;
9643 bugfix on 0.1.2.5-alpha.
9644 - Do not attempt to download extrainfo documents which we will be
9645 unable to validate with a matching server descriptor. Fixes bug
9646 13762; bugfix on 0.2.0.1-alpha.
9647 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
9648 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
9649 - Enlarge the buffer to read bwauth generated files to avoid an
9650 issue when parsing the file in dirserv_read_measured_bandwidths().
9651 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
9653 o Minor bugfixes (file handling):
9654 - Stop failing when key files are zero-length. Instead, generate new
9655 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
9656 on all versions of Tor. Patch by "teor".
9657 - Stop generating a fresh .old RSA onion key file when the .old file
9658 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
9659 - Avoid overwriting .old key files with empty key files.
9660 - Skip loading zero-length extrainfo store, router store, stats,
9661 state, and key files.
9662 - Avoid crashing when trying to reload a torrc specified as a
9663 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
9666 o Minor bugfixes (hidden services):
9667 - Close the introduction circuit when we have no more usable intro
9668 points, instead of waiting for it to time out. This also ensures
9669 that no follow-up HS descriptor fetch is triggered when the
9670 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
9671 - When fetching a hidden service descriptor for a down service that
9672 was recently up, do not keep refetching until we try the same
9673 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
9674 - Successfully launch Tor with a nonexistent hidden service
9675 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
9676 14106; bugfix on 0.2.6.2-alpha.
9678 o Minor bugfixes (logging):
9679 - Avoid crashing when there are more log domains than entries in
9680 domain_list. Bugfix on 0.2.3.1-alpha.
9681 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
9683 - Don't log messages to stdout twice when starting up. Fixes bug
9684 13993; bugfix on 0.2.6.1-alpha.
9686 o Minor bugfixes (parsing):
9687 - Stop accepting milliseconds (or other junk) at the end of
9688 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
9689 - Support two-number and three-number version numbers correctly, in
9690 case we change the Tor versioning system in the future. Fixes bug
9691 13661; bugfix on 0.0.8pre1.
9693 o Minor bugfixes (path counting):
9694 - When deciding whether the consensus lists any exit nodes, count
9695 the number listed in the consensus, not the number we have
9696 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
9697 - When deciding whether we have any exit nodes, only examine
9698 ExitNodes when the ExitNodes option is actually set. Fixes part of
9699 bug 14918; bugfix on 0.2.6.2-alpha.
9700 - Get rid of redundant and possibly scary warnings that we are
9701 missing directory information while we bootstrap. Fixes part of
9702 bug 14918; bugfix on 0.2.6.2-alpha.
9704 o Minor bugfixes (portability):
9705 - Fix the ioctl()-based network interface lookup code so that it
9706 will work on systems that have variable-length struct ifreq, for
9708 - Fix scheduler compilation on targets where char is unsigned. Fixes
9709 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
9711 o Minor bugfixes (sandbox):
9712 - Allow glibc fatal errors to be sent to stderr before Tor exits.
9713 Previously, glibc would try to write them to /dev/tty, and the
9714 sandbox would trap the call and make Tor exit prematurely. Fixes
9715 bug 14759; bugfix on 0.2.5.1-alpha.
9717 o Minor bugfixes (shutdown):
9718 - When shutting down, always call event_del() on lingering read or
9719 write events before freeing them. Otherwise, we risk double-frees
9720 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
9723 o Minor bugfixes (small memory leaks):
9724 - Avoid leaking memory when using IPv6 virtual address mappings.
9725 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
9728 o Minor bugfixes (statistics):
9729 - Increase period over which bandwidth observations are aggregated
9730 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9732 o Minor bugfixes (systemd support):
9733 - Fix detection and operation of systemd watchdog. Fixes part of bug
9734 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
9735 - Run correctly under systemd with the RunAsDaemon option set. Fixes
9736 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
9737 - Inform the systemd supervisor about more changes in the Tor
9738 process status. Implements part of ticket 14141. Patch from
9740 - Cause the "--disable-systemd" option to actually disable systemd
9741 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
9744 o Minor bugfixes (TLS):
9745 - Check more thoroughly throughout the TLS code for possible
9746 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
9748 o Minor bugfixes (transparent proxy):
9749 - Use getsockname, not getsockopt, to retrieve the address for a
9750 TPROXY-redirected connection. Fixes bug 13796; bugfix
9753 o Code simplification and refactoring:
9754 - Move fields related to isolating and configuring client ports into
9755 a shared structure. Previously, they were duplicated across
9756 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
9757 to copy them correctly had been the cause of at least one bug in
9758 the past. Closes ticket 8546.
9759 - Refactor the get_interface_addresses_raw() doom-function into
9760 multiple smaller and simpler subfunctions. Cover the resulting
9761 subfunctions with unit-tests. Fixes a significant portion of
9763 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
9764 only for version <= 0.2.2.24 which is now deprecated. Closes
9766 - Remove a test for a long-defunct broken version-one
9770 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
9771 for writing the OpenBSD-specific tips. Resolves ticket 13702.
9772 - Make the tor-resolve documentation match its help string and its
9773 options. Resolves part of ticket 14325.
9774 - Log a more useful error message from tor-resolve when failing to
9775 look up a hidden service address. Resolves part of ticket 14325.
9777 o Downgraded warnings:
9778 - Don't warn when we've attempted to contact a relay using the wrong
9779 ntor onion key. Closes ticket 9635.
9782 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
9783 longer silently accepted as an alias for "ExitNodes".
9784 - The --enable-mempool and --enable-buf-freelists options, which
9785 were originally created to work around bad malloc implementations,
9786 no longer exist. They were off-by-default in 0.2.5. Closes
9790 - Make the checkdir/perms test complete successfully even if the
9791 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
9792 - Test that tor does not fail when key files are zero-length. Check
9793 that tor generates new keys, and overwrites the empty key files.
9794 - Test that tor generates new keys when keys are missing
9795 (existing behavior).
9796 - Test that tor does not overwrite key files that already contain
9797 data (existing behavior). Tests bug 13111. Patch by "teor".
9798 - New "make test-stem" target to run stem integration tests.
9799 Requires that the "STEM_SOURCE_DIR" environment variable be set.
9800 Closes ticket 14107.
9801 - Make the test_cmdline_args.py script work correctly on Windows.
9802 Patch from Gisle Vanem.
9803 - Move the slower unit tests into a new "./src/test/test-slow"
9804 binary that can be run independently of the other tests. Closes
9806 - Avoid undefined behavior when sampling huge values from the
9807 Laplace distribution. This made unittests fail on Raspberry Pi.
9808 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
9811 Changes in version 0.2.6.2-alpha - 2014-12-31
9812 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
9813 It introduces a major new backend for deciding when to send cells on
9814 channels, which should lead down the road to big performance
9815 increases. It contains security and statistics features for better
9816 work on hidden services, and numerous bugfixes.
9818 This release contains many new unit tests, along with major
9819 performance improvements for running testing networks using Chutney.
9820 Thanks to a series of patches contributed by "teor", testing networks
9821 should now bootstrap in seconds, rather than minutes.
9823 o Major features (relay, infrastructure):
9824 - Complete revision of the code that relays use to decide which cell
9825 to send next. Formerly, we selected the best circuit to write on
9826 each channel, but we didn't select among channels in any
9827 sophisticated way. Now, we choose the best circuits globally from
9828 among those whose channels are ready to deliver traffic.
9830 This patch implements a new inter-cmux comparison API, a global
9831 high/low watermark mechanism and a global scheduler loop for
9832 transmission prioritization across all channels as well as among
9833 circuits on one channel. This schedule is currently tuned to
9834 (tolerantly) avoid making changes in network performance, but it
9835 should form the basis for major circuit performance increases in
9836 the future. Code by Andrea; tuning by Rob Jansen; implements
9839 o Major features (hidden services):
9840 - Make HS port scanning more difficult by immediately closing the
9841 circuit when a user attempts to connect to a nonexistent port.
9842 Closes ticket 13667.
9843 - Add a HiddenServiceStatistics option that allows Tor relays to
9844 gather and publish statistics about the overall size and volume of
9845 hidden service usage. Specifically, when this option is turned on,
9846 an HSDir will publish an approximate number of hidden services
9847 that have published descriptors to it the past 24 hours. Also, if
9848 a relay has acted as a hidden service rendezvous point, it will
9849 publish the approximate amount of rendezvous cells it has relayed
9850 the past 24 hours. The statistics themselves are obfuscated so
9851 that the exact values cannot be derived. For more details see
9852 proposal 238, "Better hidden service stats from Tor relays". This
9853 feature is currently disabled by default. Implements feature 13192.
9855 o Major bugfixes (client, automap):
9856 - Repair automapping with IPv6 addresses. This automapping should
9857 have worked previously, but one piece of debugging code that we
9858 inserted to detect a regression actually caused the regression to
9859 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
9860 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
9863 o Major bugfixes (hidden services):
9864 - When closing an introduction circuit that was opened in parallel
9865 with others, don't mark the introduction point as unreachable.
9866 Previously, the first successful connection to an introduction
9867 point would make the other introduction points get marked as
9868 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
9870 o Directory authority changes:
9871 - Remove turtles as a directory authority.
9872 - Add longclaw as a new (v3) directory authority. This implements
9873 ticket 13296. This keeps the directory authority count at 9.
9875 o Major removed features:
9876 - Tor clients no longer support connecting to hidden services
9877 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
9878 option has been removed. (There shouldn't be any hidden services
9879 running these versions on the network.) Closes ticket 7803.
9881 o Minor features (client):
9882 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
9883 is enabled, reject requests with IP addresses as hostnames.
9884 Resolves ticket 13315.
9886 o Minor features (controller):
9887 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
9888 write an unscheduled heartbeat message to the log. Implements
9891 o Minor features (geoip):
9892 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
9895 o Minor features (hidden services):
9896 - When re-enabling the network, don't try to build introduction
9897 circuits until we have successfully built a circuit. This makes
9898 hidden services come up faster when the network is re-enabled.
9899 Patch from "akwizgran". Closes ticket 13447.
9900 - When we fail to retrieve a hidden service descriptor, send the
9901 controller an "HS_DESC FAILED" controller event. Implements
9903 - New HiddenServiceDirGroupReadable option to cause hidden service
9904 directories and hostname files to be created group-readable. Patch
9905 from "anon", David Stainton, and "meejah". Closes ticket 11291.
9907 o Minor features (systemd):
9908 - Where supported, when running with systemd, report successful
9909 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
9910 - When running with systemd, support systemd watchdog messages. Part
9911 of ticket 11016. Patch by Michael Scherer.
9913 o Minor features (transparent proxy):
9914 - Update the transparent proxy option checks to allow for both ipfw
9915 and pf on OS X. Closes ticket 14002.
9916 - Use the correct option when using IPv6 with transparent proxy
9917 support on Linux. Resolves 13808. Patch by Francisco Blas
9920 o Minor bugfixes (preventative security, C safety):
9921 - When reading a hexadecimal, base-32, or base-64 encoded value from
9922 a string, always overwrite the whole output buffer. This prevents
9923 some bugs where we would look at (but fortunately, not reveal)
9924 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
9926 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
9927 just the part that's used. This makes it harder for data leak bugs
9928 to occur in the event of other programming failures. Resolves
9931 o Minor bugfixes (client, microdescriptors):
9932 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
9933 computing which microdescriptors to download. This keeps us from
9934 erroneous download behavior if two microdescriptor digests ever
9935 have the same first 160 bits. Fixes part of bug 13399; bugfix
9937 - Reset a router's status if its microdescriptor digest changes,
9938 even if the first 160 bits remain the same. Fixes part of bug
9939 13399; bugfix on 0.2.3.1-alpha.
9941 o Minor bugfixes (compilation):
9942 - Silence clang warnings under --enable-expensive-hardening,
9943 including implicit truncation of 64 bit values to 32 bit, const
9944 char assignment to self, tautological compare, and additional
9945 parentheses around equality tests. Fixes bug 13577; bugfix
9947 - Fix a clang warning about checking whether an address in the
9948 middle of a structure is NULL. Fixes bug 14001; bugfix
9951 o Minor bugfixes (hidden services):
9952 - Correctly send a controller event when we find that a rendezvous
9953 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
9954 - Pre-check directory permissions for new hidden-services to avoid
9955 at least one case of "Bug: Acting on config options left us in a
9956 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
9957 - When adding a new hidden service (for example, via SETCONF), Tor
9958 no longer congratulates the user for running a relay. Fixes bug
9959 13941; bugfix on 0.2.6.1-alpha.
9960 - When fetching hidden service descriptors, we now check not only
9961 for whether we got the hidden service we had in mind, but also
9962 whether we got the particular descriptors we wanted. This prevents
9963 a class of inefficient but annoying DoS attacks by hidden service
9964 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
9967 o Minor bugfixes (Linux seccomp2 sandbox):
9968 - Make transparent proxy support work along with the seccomp2
9969 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
9970 by Francisco Blas Izquierdo Riera.
9971 - Fix a memory leak in tor-resolve when running with the sandbox
9972 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
9974 o Minor bugfixes (logging):
9975 - Downgrade warnings about RSA signature failures to info log level.
9976 Emit a warning when an extra info document is found incompatible
9977 with a corresponding router descriptor. Fixes bug 9812; bugfix
9979 - Make connection_ap_handshake_attach_circuit() log the circuit ID
9980 correctly. Fixes bug 13701; bugfix on 0.0.6.
9982 o Minor bugfixes (misc):
9983 - Stop allowing invalid address patterns like "*/24" that contain
9984 both a wildcard address and a bit prefix length. This affects all
9985 our address-range parsing code. Fixes bug 7484; bugfix
9988 o Minor bugfixes (testing networks, fast startup):
9989 - Allow Tor to build circuits using a consensus with no exits. If
9990 the consensus has no exits (typical of a bootstrapping test
9991 network), allow Tor to build circuits once enough descriptors have
9992 been downloaded. This assists in bootstrapping a testing Tor
9993 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
9995 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
9996 header to directory servers. This allows us to obtain consensuses
9997 promptly when the consensus interval is very short. This assists
9998 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
9999 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
10000 - Stop assuming that private addresses are local when checking
10001 reachability in a TestingTorNetwork. Instead, when testing, assume
10002 all OR connections are remote. (This is necessary due to many test
10003 scenarios running all relays on localhost.) This assists in
10004 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
10005 0.1.0.1-rc. Patch by "teor".
10006 - Avoid building exit circuits from a consensus with no exits. Now
10007 thanks to our fix for 13718, we accept a no-exit network as not
10008 wholly lost, but we need to remember not to try to build exit
10009 circuits on it. Closes ticket 13814; patch by "teor".
10010 - Stop requiring exits to have non-zero bandwithcapacity in a
10011 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
10012 ignore exit bandwidthcapacity. This assists in bootstrapping a
10013 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
10014 on 0.2.0.3-alpha. Patch by "teor".
10015 - Add "internal" to some bootstrap statuses when no exits are
10016 available. If the consensus does not contain Exits, Tor will only
10017 build internal circuits. In this case, relevant statuses will
10018 contain the word "internal" as indicated in the Tor control-
10019 spec.txt. When bootstrap completes, Tor will be ready to build
10020 internal circuits. If a future consensus contains Exits, exit
10021 circuits may become available. Fixes part of bug 13718; bugfix on
10022 0.2.4.10-alpha. Patch by "teor".
10023 - Decrease minimum consensus interval to 10 seconds when
10024 TestingTorNetwork is set, or 5 seconds for the first consensus.
10025 Fix assumptions throughout the code that assume larger intervals.
10026 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
10028 - Avoid excluding guards from path building in minimal test
10029 networks, when we're in a test network and excluding guards would
10030 exclude all relays. This typically occurs in incredibly small tor
10031 networks, and those using "TestingAuthVoteGuard *". Fixes part of
10032 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
10034 o Code simplification and refactoring:
10035 - Stop using can_complete_circuits as a global variable; access it
10036 with a function instead.
10037 - Avoid using operators directly as macro arguments: this lets us
10038 apply coccinelle transformations to our codebase more directly.
10039 Closes ticket 13172.
10040 - Combine the functions used to parse ClientTransportPlugin and
10041 ServerTransportPlugin into a single function. Closes ticket 6456.
10042 - Add inline functions and convenience macros for inspecting channel
10043 state. Refactor the code to use convenience macros instead of
10044 checking channel state directly. Fixes issue 7356.
10045 - Document all members of was_router_added_t and rename
10046 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
10047 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
10048 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
10049 constant instead of hardcoded value. Fixes issue 13840.
10050 - Refactor our generic strmap and digestmap types into a single
10051 implementation, so that we can add a new digest256map
10055 - Document the bridge-authority-only 'networkstatus-bridges' file.
10056 Closes ticket 13713; patch from "tom".
10057 - Fix typo in PredictedPortsRelevanceTime option description in
10058 manpage. Resolves issue 13707.
10059 - Stop suggesting that users specify relays by nickname: it isn't a
10060 good idea. Also, properly cross-reference how to specify relays in
10061 all parts of manual documenting options that take a list of
10062 relays. Closes ticket 13381.
10063 - Clarify the HiddenServiceDir option description in manpage to make
10064 it clear that relative paths are taken with respect to the current
10065 working directory. Also clarify that this behavior is not
10066 guaranteed to remain indefinitely. Fixes issue 13913.
10069 - New tests for many parts of channel, relay, and circuitmux
10070 functionality. Code by Andrea; part of 9262.
10071 - New tests for parse_transport_line(). Part of ticket 6456.
10072 - In the unit tests, use chgrp() to change the group of the unit
10073 test temporary directory to the current user, so that the sticky
10074 bit doesn't interfere with tests that check directory groups.
10076 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
10080 Changes in version 0.2.6.1-alpha - 2014-10-30
10081 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
10082 includes numerous code cleanups and new tests, and fixes a large
10083 number of annoying bugs. Out-of-memory conditions are handled better
10084 than in 0.2.5, pluggable transports have improved proxy support, and
10085 clients now use optimistic data for contacting hidden services. Also,
10086 we are now more robust to changes in what we consider a parseable
10087 directory object, so that tightening restrictions does not have a risk
10088 of introducing infinite download loops.
10090 This is the first alpha release in a new series, so expect there to be
10091 bugs. Users who would rather test out a more stable branch should stay
10092 with 0.2.5.x for now.
10094 o New compiler and system requirements:
10095 - Tor 0.2.6.x requires that your compiler support more of the C99
10096 language standard than before. The 'configure' script now detects
10097 whether your compiler supports C99 mid-block declarations and
10098 designated initializers. If it does not, Tor will not compile.
10100 We may revisit this requirement if it turns out that a significant
10101 number of people need to build Tor with compilers that don't
10102 bother implementing a 15-year-old standard. Closes ticket 13233.
10103 - Tor no longer supports systems without threading support. When we
10104 began working on Tor, there were several systems that didn't have
10105 threads, or where the thread support wasn't able to run the
10106 threads of a single process on multiple CPUs. That no longer
10107 holds: every system where Tor needs to run well now has threading
10108 support. Resolves ticket 12439.
10110 o Removed platform support:
10111 - We no longer include special code to build on Windows CE; as far
10112 as we know, nobody has used Tor on Windows CE in a very long time.
10113 Closes ticket 11446.
10115 o Major features (bridges):
10116 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
10117 transports if they are configured via the "TOR_PT_PROXY"
10118 environment variable. Implements proposal 232. Resolves
10121 o Major features (client performance, hidden services):
10122 - Allow clients to use optimistic data when connecting to a hidden
10123 service, which should remove a round-trip from hidden service
10124 initialization. See proposal 181 for details. Implements
10127 o Major features (directory system):
10128 - Upon receiving an unparseable directory object, if its digest
10129 matches what we expected, then don't try to download it again.
10130 Previously, when we got a descriptor we didn't like, we would keep
10131 trying to download it over and over. Closes ticket 11243.
10133 o Major features (sample torrc):
10134 - Add a new, infrequently-changed "torrc.minimal". This file is
10135 similar to torrc.sample, but it will change as infrequently as
10136 possible, for the benefit of users whose systems prompt them for
10137 intervention whenever a default configuration file is changed.
10138 Making this change allows us to update torrc.sample to be a more
10139 generally useful "sample torrc".
10141 o Major bugfixes (directory authorities):
10142 - Do not assign the HSDir flag to relays if they are not Valid, or
10143 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
10145 o Major bugfixes (directory bandwidth performance):
10146 - Don't flush the zlib buffer aggressively when compressing
10147 directory information for clients. This should save about 7% of
10148 the bandwidth currently used for compressed descriptors and
10149 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
10151 o Minor features (security, memory wiping):
10152 - Ensure we securely wipe keys from memory after
10153 crypto_digest_get_digest and init_curve25519_keypair_from_file
10154 have finished using them. Resolves ticket 13477.
10156 o Minor features (security, out-of-memory handling):
10157 - When handling an out-of-memory condition, allocate less memory for
10158 temporary data structures. Fixes issue 10115.
10159 - When handling an out-of-memory condition, consider more types of
10160 buffers, including those on directory connections, and zlib
10161 buffers. Resolves ticket 11792.
10164 - When identity keypair is generated for first time, log a
10165 congratulatory message that links to the new relay lifecycle
10166 document. Implements feature 10427.
10168 o Minor features (client):
10169 - Clients are now willing to send optimistic data (before they
10170 receive a 'connected' cell) to relays of any version. (Relays
10171 without support for optimistic data are no longer supported on the
10172 Tor network.) Resolves ticket 13153.
10174 o Minor features (directory authorities):
10175 - Don't list relays with a bandwidth estimate of 0 in the consensus.
10176 Implements a feature proposed during discussion of bug 13000.
10177 - In tor-gencert, report an error if the user provides the same
10178 argument more than once.
10179 - If a directory authority can't find a best consensus method in the
10180 votes that it holds, it now falls back to its favorite consensus
10181 method. Previously, it fell back to method 1. Neither of these is
10182 likely to get enough signatures, but "fall back to favorite"
10183 doesn't require us to maintain support an obsolete consensus
10184 method. Implements part of proposal 215.
10186 o Minor features (logging):
10187 - On Unix-like systems, you can now use named pipes as the target of
10188 the Log option, and other options that try to append to files.
10189 Closes ticket 12061. Patch from "carlo von lynX".
10190 - When opening a log file at startup, send it every log message that
10191 we generated between startup and opening it. Previously, log
10192 messages that were generated before opening the log file were only
10193 logged to stdout. Closes ticket 6938.
10194 - Add a TruncateLogFile option to overwrite logs instead of
10195 appending to them. Closes ticket 5583.
10197 o Minor features (portability, Solaris):
10198 - Threads are no longer disabled by default on Solaris; we believe
10199 that the versions of Solaris with broken threading support are all
10200 obsolete by now. Resolves ticket 9495.
10202 o Minor features (relay):
10203 - Re-check our address after we detect a changed IP address from
10204 getsockname(). This ensures that the controller command "GETINFO
10205 address" will report the correct value. Resolves ticket 11582.
10207 - A new AccountingRule option lets Relays set whether they'd like
10208 AccountingMax to be applied separately to inbound and outbound
10209 traffic, or applied to the sum of inbound and outbound traffic.
10210 Resolves ticket 961. Patch by "chobe".
10212 o Minor features (testing networks):
10213 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
10214 the "Exit" flag regardless of their uptime, bandwidth, or exit
10215 policy. TestingTorNetwork must be set for this option to have any
10216 effect. Previously, authorities would take up to 35 minutes to
10217 give nodes the Exit flag in a test network. Partially implements
10220 o Minor features (validation):
10221 - Check all date/time values passed to tor_timegm and
10222 parse_rfc1123_time for validity, taking leap years into account.
10223 Improves HTTP header validation. Implemented with bug 13476.
10224 - In correct_tm(), limit the range of values returned by system
10225 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
10226 This means we don't have to deal with negative or too large dates,
10227 even if a clock is wrong. Otherwise we might fail to read a file
10228 written by us which includes such a date. Fixes bug 13476.
10230 o Minor bugfixes (bridge clients):
10231 - When configured to use a bridge without an identity digest (not
10232 recommended), avoid launching an extra channel to it when
10233 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
10235 o Minor bugfixes (bridges):
10236 - When DisableNetwork is set, do not launch pluggable transport
10237 plugins, and if any are running, terminate them. Fixes bug 13213;
10238 bugfix on 0.2.3.6-alpha.
10240 o Minor bugfixes (C correctness):
10241 - Fix several instances of possible integer overflow/underflow/NaN.
10242 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
10244 - In circuit_build_times_calculate_timeout() in circuitstats.c,
10245 avoid dividing by zero in the pareto calculations. This traps
10246 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
10248 - Fix an integer overflow in format_time_interval(). Fixes bug
10249 13393; bugfix on 0.2.0.10-alpha.
10250 - Set the correct day of year value when the system's localtime(_r)
10251 or gmtime(_r) functions fail to set struct tm. Not externally
10252 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
10253 - Avoid unlikely signed integer overflow in tor_timegm on systems
10254 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
10256 o Minor bugfixes (client):
10257 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
10258 BadExit flag are not considered worthy candidates. Fixes bug
10259 13066; bugfix on 0.1.2.3-alpha.
10260 - Use the consensus schedule for downloading consensuses, and not
10261 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
10262 - Handle unsupported or malformed SOCKS5 requests properly by
10263 responding with the appropriate error message before closing the
10264 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
10266 o Minor bugfixes (client, torrc):
10267 - Stop modifying the value of our DirReqStatistics torrc option just
10268 because we're not a bridge or relay. This bug was causing Tor
10269 Browser users to write "DirReqStatistics 0" in their torrc files
10270 as if they had chosen to change the config. Fixes bug 4244; bugfix
10272 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
10273 that our options have changed every time we SIGHUP. Fixes bug
10274 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
10276 o Minor bugfixes (controller):
10277 - Return an error when the second or later arguments of the
10278 "setevents" controller command are invalid events. Previously we
10279 would return success while silently skipping invalid events. Fixes
10280 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
10282 o Minor bugfixes (directory system):
10283 - Always believe that v3 directory authorities serve extra-info
10284 documents, whether they advertise "caches-extra-info" or not.
10285 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
10286 - When running as a v3 directory authority, advertise that you serve
10287 extra-info documents so that clients who want them can find them
10288 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
10289 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
10290 Previously, directories offering BRIDGE_DIRINFO and some other
10291 flag (i.e. microdescriptors or extrainfo) would be ignored when
10292 looking for bridges. Partially fixes bug 13163; bugfix
10295 o Minor bugfixes (networking):
10296 - Check for orconns and use connection_or_close_for_error() rather
10297 than connection_mark_for_close() directly in the getsockopt()
10298 failure case of connection_handle_write_impl(). Fixes bug 11302;
10299 bugfix on 0.2.4.4-alpha.
10301 o Minor bugfixes (relay):
10302 - When generating our family list, remove spaces from around the
10303 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
10304 - If our previous bandwidth estimate was 0 bytes, allow publishing a
10305 new relay descriptor immediately. Fixes bug 13000; bugfix
10308 o Minor bugfixes (testing networks):
10309 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
10310 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
10311 - Stop using the default authorities in networks which provide both
10312 AlternateDirAuthority and AlternateBridgeAuthority. Partially
10313 fixes bug 13163; bugfix on 0.2.0.13-alpha.
10315 o Minor bugfixes (testing):
10316 - Stop spawn test failures due to a race condition between the
10317 SIGCHLD handler updating the process status, and the test reading
10318 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
10320 o Minor bugfixes (testing, Windows):
10321 - Avoid passing an extra backslash when creating a temporary
10322 directory for running the unit tests on Windows. Fixes bug 12392;
10323 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
10325 o Minor bugfixes (windows):
10326 - Remove code to special-case handling of NTE_BAD_KEYSET when
10327 acquiring windows CryptoAPI context. This error can't actually
10328 occur for the parameters we're providing. Fixes bug 10816; bugfix
10331 o Minor bugfixes (zlib):
10332 - Avoid truncating a zlib stream when trying to finalize it with an
10333 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
10336 - Allow our configure script to build correctly with autoconf 2.62
10337 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
10338 - Improve the error message from ./configure to make it clear that
10339 when asciidoc has not been found, the user will have to either add
10340 --disable-asciidoc argument or install asciidoc. Resolves
10343 o Code simplification and refactoring:
10344 - Change the entry_is_live() function to take named bitfield
10345 elements instead of an unnamed list of booleans. Closes
10347 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
10348 Resolves ticket 12205.
10349 - Use calloc and reallocarray functions instead of multiply-
10350 then-malloc. This makes it less likely for us to fall victim to an
10351 integer overflow attack when allocating. Resolves ticket 12855.
10352 - Use the standard macro name SIZE_MAX, instead of our
10354 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
10355 functions which take them as arguments. Replace 0 with NO_DIRINFO
10356 in a function call for clarity. Seeks to prevent future issues
10358 - Avoid 4 null pointer errors under clang static analysis by using
10359 tor_assert() to prove that the pointers aren't null. Fixes
10361 - Rework the API of policies_parse_exit_policy() to use a bitmask to
10362 represent parsing options, instead of a confusing mess of
10363 booleans. Resolves ticket 8197.
10364 - Introduce a helper function to parse ExitPolicy in
10365 or_options_t structure.
10368 - Add a doc/TUNING document with tips for handling large numbers of
10369 TCP connections when running busy Tor relay. Update the warning
10370 message to point to this file when running out of sockets
10371 operating system is allowing to use simultaneously. Resolves
10374 o Removed features:
10375 - We no longer remind the user about configuration options that have
10376 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
10377 - Remove our old, non-weighted bandwidth-based node selection code.
10378 Previously, we used it as a fallback when we couldn't perform
10379 weighted bandwidth-based node selection. But that would only
10380 happen in the cases where we had no consensus, or when we had a
10381 consensus generated by buggy or ancient directory authorities. In
10382 either case, it's better to use the more modern, better maintained
10383 algorithm, with reasonable defaults for the weights. Closes
10385 - Remove the --disable-curve25519 configure option. Relays and
10386 clients now are required to support curve25519 and the
10388 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
10389 used to be deprecated synonyms for "StrictNodes", are now marked
10390 obsolete. Resolves ticket 12226.
10391 - Clients don't understand the BadDirectory flag in the consensus
10392 anymore, and ignore it.
10395 - Refactor the function that chooses guard nodes so that it can more
10396 easily be tested; write some tests for it.
10397 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
10398 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
10399 - Create unit tests for format_time_interval(). With bug 13393.
10400 - Add unit tests for tor_timegm signed overflow, tor_timegm and
10401 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
10402 tests (visible) fixes in bug 13476.
10403 - Add a "coverage-html" make target to generate HTML-visualized
10404 coverage results when building with --enable-coverage. (Requires
10405 lcov.) Patch from Kevin Murray.
10406 - Enable the backtrace handler (where supported) when running the
10408 - Revise all unit tests that used the legacy test_* macros to
10409 instead use the recommended tt_* macros. This patch was generated
10410 with coccinelle, to avoid manual errors. Closes ticket 13119.
10412 o Distribution (systemd):
10413 - systemd unit file: only allow tor to write to /var/lib/tor and
10414 /var/log/tor. The rest of the filesystem is accessible for reading
10415 only. Patch by intrigeri; resolves ticket 12751.
10416 - systemd unit file: ensure that the process and all its children
10417 can never gain new privileges. Patch by intrigeri; resolves
10419 - systemd unit file: set up /var/run/tor as writable for the Tor
10420 service. Patch by intrigeri; resolves ticket 13196.
10422 o Removed features (directory authorities):
10423 - Remove code that prevented authorities from listing Tor relays
10424 affected by CVE-2011-2769 as guards. These relays are already
10425 rejected altogether due to the minimum version requirement of
10426 0.2.3.16-alpha. Closes ticket 13152.
10427 - The "AuthDirRejectUnlisted" option no longer has any effect, as
10428 the fingerprints file (approved-routers) has been deprecated.
10429 - Directory authorities do not support being Naming dirauths anymore.
10430 The "NamingAuthoritativeDir" config option is now obsolete.
10431 - Directory authorities do not support giving out the BadDirectory
10433 - Directory authorities no longer advertise or support consensus
10434 methods 1 through 12 inclusive. These consensus methods were
10435 obsolete and/or insecure: maintaining the ability to support them
10436 served no good purpose. Implements part of proposal 215; closes
10439 o Testing (test-network.sh):
10440 - Stop using "echo -n", as some shells' built-in echo doesn't
10441 support "-n". Instead, use "/bin/echo -n". Partially fixes
10443 - Stop an apparent test-network hang when used with make -j2. Fixes
10445 - Add a --delay option to test-network.sh, which configures the
10446 delay before the chutney network tests for data transmission.
10447 Partially implements ticket 13161.
10450 Changes in version 0.2.5.10 - 2014-10-24
10451 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
10453 It adds several new security features, including improved
10454 denial-of-service resistance for relays, new compiler hardening
10455 options, and a system-call sandbox for hardened installations on Linux
10456 (requires seccomp2). The controller protocol has several new features,
10457 resolving IPv6 addresses should work better than before, and relays
10458 should be a little more CPU-efficient. We've added support for more
10459 OpenBSD and FreeBSD transparent proxy types. We've improved the build
10460 system and testing infrastructure to allow unit testing of more parts
10461 of the Tor codebase. Finally, we've addressed several nagging pluggable
10462 transport usability issues, and included numerous other small bugfixes
10463 and features mentioned below.
10465 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
10466 have accumulated many known flaws; everyone should upgrade.
10468 o Deprecated versions:
10469 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
10470 attention for some while.
10473 Changes in version 0.2.5.9-rc - 2014-10-20
10474 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
10475 series. It disables SSL3 in response to the recent "POODLE" attack
10476 (even though POODLE does not affect Tor). It also works around a crash
10477 bug caused by some operating systems' response to the "POODLE" attack
10478 (which does affect Tor). It also contains a few miscellaneous fixes.
10480 o Major security fixes:
10481 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
10482 today support TLS 1.0 or later, so we can safely turn off support
10483 for this old (and insecure) protocol. Fixes bug 13426.
10485 o Major bugfixes (openssl bug workaround):
10486 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
10487 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
10488 13471. This is a workaround for an OpenSSL bug.
10491 - Disable the sandbox name resolver cache when running tor-resolve:
10492 tor-resolve doesn't use the sandbox code, and turning it on was
10493 breaking attempts to do tor-resolve on a non-default server on
10494 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
10496 o Compilation fixes:
10497 - Build and run correctly on systems like OpenBSD-current that have
10498 patched OpenSSL to remove get_cipher_by_char and/or its
10499 implementations. Fixes issue 13325.
10501 o Downgraded warnings:
10502 - Downgrade the severity of the 'unexpected sendme cell from client'
10503 from 'warn' to 'protocol warning'. Closes ticket 8093.
10506 Changes in version 0.2.4.25 - 2014-10-20
10507 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
10508 (even though POODLE does not affect Tor). It also works around a crash
10509 bug caused by some operating systems' response to the "POODLE" attack
10510 (which does affect Tor).
10512 o Major security fixes (also in 0.2.5.9-rc):
10513 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
10514 today support TLS 1.0 or later, so we can safely turn off support
10515 for this old (and insecure) protocol. Fixes bug 13426.
10517 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
10518 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
10519 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
10520 13471. This is a workaround for an OpenSSL bug.
10523 Changes in version 0.2.5.8-rc - 2014-09-22
10524 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
10525 series. It fixes a bug that affects consistency and speed when
10526 connecting to hidden services, and it updates the location of one of
10527 the directory authorities.
10530 - Clients now send the correct address for their chosen rendezvous
10531 point when trying to access a hidden service. They used to send
10532 the wrong address, which would still work some of the time because
10533 they also sent the identity digest of the rendezvous point, and if
10534 the hidden service happened to try connecting to the rendezvous
10535 point from a relay that already had a connection open to it,
10536 the relay would reuse that connection. Now connections to hidden
10537 services should be more robust and faster. Also, this bug meant
10538 that clients were leaking to the hidden service whether they were
10539 on a little-endian (common) or big-endian (rare) system, which for
10540 some users might have reduced their anonymity. Fixes bug 13151;
10541 bugfix on 0.2.1.5-alpha.
10543 o Directory authority changes:
10544 - Change IP address for gabelmoo (v3 directory authority).
10547 Changes in version 0.2.4.24 - 2014-09-22
10548 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
10549 connecting to hidden services, and it updates the location of one of
10550 the directory authorities.
10553 - Clients now send the correct address for their chosen rendezvous
10554 point when trying to access a hidden service. They used to send
10555 the wrong address, which would still work some of the time because
10556 they also sent the identity digest of the rendezvous point, and if
10557 the hidden service happened to try connecting to the rendezvous
10558 point from a relay that already had a connection open to it,
10559 the relay would reuse that connection. Now connections to hidden
10560 services should be more robust and faster. Also, this bug meant
10561 that clients were leaking to the hidden service whether they were
10562 on a little-endian (common) or big-endian (rare) system, which for
10563 some users might have reduced their anonymity. Fixes bug 13151;
10564 bugfix on 0.2.1.5-alpha.
10566 o Directory authority changes:
10567 - Change IP address for gabelmoo (v3 directory authority).
10569 o Minor features (geoip):
10570 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
10574 Changes in version 0.2.5.7-rc - 2014-09-11
10575 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
10576 release series, and some long-standing bugs related to ORPort reachability
10577 testing and failure to send CREATE cells. It is the first release
10578 candidate for the Tor 0.2.5.x series.
10580 o Major bugfixes (client, startup):
10581 - Start making circuits as soon as DisabledNetwork is turned off.
10582 When Tor started with DisabledNetwork set, it would correctly
10583 conclude that it shouldn't build circuits, but it would mistakenly
10584 cache this conclusion, and continue believing it even when
10585 DisableNetwork is set to 0. Fixes the bug introduced by the fix
10586 for bug 11200; bugfix on 0.2.5.4-alpha.
10587 - Resume expanding abbreviations for command-line options. The fix
10588 for bug 4647 accidentally removed our hack from bug 586 that
10589 rewrote HashedControlPassword to __HashedControlSessionPassword
10590 when it appears on the commandline (which allowed the user to set
10591 her own HashedControlPassword in the torrc file while the
10592 controller generates a fresh session password for each run). Fixes
10593 bug 12948; bugfix on 0.2.5.1-alpha.
10594 - Warn about attempts to run hidden services and relays in the same
10595 process: that's probably not a good idea. Closes ticket 12908.
10597 o Major bugfixes (relay):
10598 - Avoid queuing or sending destroy cells for circuit ID zero when we
10599 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
10600 Found and fixed by "cypherpunks".
10601 - Fix ORPort reachability detection on relays running behind a
10602 proxy, by correctly updating the "local" mark on the controlling
10603 channel when changing the address of an or_connection_t after the
10604 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
10606 o Minor features (bridge):
10607 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
10608 cookie file for the ExtORPort g+r by default.
10610 o Minor features (geoip):
10611 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
10614 o Minor bugfixes (logging):
10615 - Reduce the log severity of the "Pluggable transport proxy does not
10616 provide any needed transports and will not be launched." message,
10617 since Tor Browser includes several ClientTransportPlugin lines in
10618 its torrc-defaults file, leading every Tor Browser user who looks
10619 at her logs to see these notices and wonder if they're dangerous.
10620 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
10621 - Downgrade "Unexpected onionskin length after decryption" warning
10622 to a protocol-warn, since there's nothing relay operators can do
10623 about a client that sends them a malformed create cell. Resolves
10624 bug 12996; bugfix on 0.0.6rc1.
10625 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
10626 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
10627 - When logging information about an EXTEND2 or EXTENDED2 cell, log
10628 their names correctly. Fixes part of bug 12700; bugfix
10630 - When logging information about a relay cell whose command we don't
10631 recognize, log its command as an integer. Fixes part of bug 12700;
10632 bugfix on 0.2.1.10-alpha.
10633 - Escape all strings from the directory connection before logging
10634 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
10636 o Minor bugfixes (controller):
10637 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
10638 bug 12864; bugfix on 0.2.5.1-alpha.
10639 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
10640 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
10643 o Minor bugfixes (compilation):
10644 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
10645 bugfix on 0.2.5.5-alpha.
10646 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
10647 0.2.5.1-alpha. Patch from "NewEraCracker".
10648 - In routerlist_assert_ok(), don't take the address of a
10649 routerinfo's cache_info member unless that routerinfo is non-NULL.
10650 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
10651 - Fix a large number of false positive warnings from the clang
10652 analyzer static analysis tool. This should make real warnings
10653 easier for clang analyzer to find. Patch from "teor". Closes
10656 o Distribution (systemd):
10657 - Verify configuration file via ExecStartPre in the systemd unit
10658 file. Patch from intrigeri; resolves ticket 12730.
10659 - Explicitly disable RunAsDaemon in the systemd unit file. Our
10660 current systemd unit uses "Type = simple", so systemd does not
10661 expect tor to fork. If the user has "RunAsDaemon 1" in their
10662 torrc, then things won't work as expected. This is e.g. the case
10663 on Debian (and derivatives), since there we pass "--defaults-torrc
10664 /usr/share/tor/tor-service-defaults-torrc" (that contains
10665 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
10669 - Adjust the URLs in the README to refer to the new locations of
10670 several documents on the website. Fixes bug 12830. Patch from
10672 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
10676 Changes in version 0.2.5.6-alpha - 2014-07-28
10677 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
10678 risk from guard rotation, and fixes a variety of other issues to get
10679 us closer to a release candidate.
10681 o Major features (also in 0.2.4.23):
10682 - Make the number of entry guards configurable via a new
10683 NumEntryGuards consensus parameter, and the number of directory
10684 guards configurable via a new NumDirectoryGuards consensus
10685 parameter. Implements ticket 12688.
10687 o Major bugfixes (also in 0.2.4.23):
10688 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
10689 implementation that caused incorrect results on 32-bit
10690 implementations when certain malformed inputs were used along with
10691 a small class of private ntor keys. This bug does not currently
10692 appear to allow an attacker to learn private keys or impersonate a
10693 Tor server, but it could provide a means to distinguish 32-bit Tor
10694 implementations from 64-bit Tor implementations. Fixes bug 12694;
10695 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
10699 - Perform circuit cleanup operations even when circuit
10700 construction operations are disabled (because the network is
10701 disabled, or because there isn't enough directory information).
10702 Previously, when we were not building predictive circuits, we
10703 were not closing expired circuits either. Fixes bug 8387; bugfix on
10704 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
10705 became more strict about when we have "enough directory information
10706 to build circuits".
10709 - Authorities now assign the Guard flag to the fastest 25% of the
10710 network (it used to be the fastest 50%). Also raise the consensus
10711 weight that guarantees the Guard flag from 250 to 2000. For the
10712 current network, this results in about 1100 guards, down from 2500.
10713 This step paves the way for moving the number of entry guards
10714 down to 1 (proposal 236) while still providing reasonable expected
10715 performance for most users. Implements ticket 12690.
10716 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
10718 - Slightly enhance the diagnostic message for bug 12184.
10720 o Minor bugfixes (also in 0.2.4.23):
10721 - Warn and drop the circuit if we receive an inbound 'relay early'
10722 cell. Those used to be normal to receive on hidden service circuits
10723 due to bug 1038, but the buggy Tor versions are long gone from
10724 the network so we can afford to resume watching for them. Resolves
10725 the rest of bug 1038; bugfix on 0.2.1.19.
10726 - Correct a confusing error message when trying to extend a circuit
10727 via the control protocol but we don't know a descriptor or
10728 microdescriptor for one of the specified relays. Fixes bug 12718;
10729 bugfix on 0.2.3.1-alpha.
10732 - Fix compilation when building with bufferevents enabled. (This
10733 configuration is still not expected to work, however.)
10734 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
10735 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
10737 - Compile correctly with builds and forks of OpenSSL (such as
10738 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
10739 0.2.1.1-alpha. Patch from "dhill".
10742 Changes in version 0.2.4.23 - 2014-07-28
10743 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
10744 guard rotation, and also backports several important fixes from the
10745 Tor 0.2.5 alpha release series.
10748 - Clients now look at the "usecreatefast" consensus parameter to
10749 decide whether to use CREATE_FAST or CREATE cells for the first hop
10750 of their circuit. This approach can improve security on connections
10751 where Tor's circuit handshake is stronger than the available TLS
10752 connection security levels, but the tradeoff is more computational
10753 load on guard relays. Implements proposal 221. Resolves ticket 9386.
10754 - Make the number of entry guards configurable via a new
10755 NumEntryGuards consensus parameter, and the number of directory
10756 guards configurable via a new NumDirectoryGuards consensus
10757 parameter. Implements ticket 12688.
10760 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
10761 implementation that caused incorrect results on 32-bit
10762 implementations when certain malformed inputs were used along with
10763 a small class of private ntor keys. This bug does not currently
10764 appear to allow an attacker to learn private keys or impersonate a
10765 Tor server, but it could provide a means to distinguish 32-bit Tor
10766 implementations from 64-bit Tor implementations. Fixes bug 12694;
10767 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
10771 - Warn and drop the circuit if we receive an inbound 'relay early'
10772 cell. Those used to be normal to receive on hidden service circuits
10773 due to bug 1038, but the buggy Tor versions are long gone from
10774 the network so we can afford to resume watching for them. Resolves
10775 the rest of bug 1038; bugfix on 0.2.1.19.
10776 - Correct a confusing error message when trying to extend a circuit
10777 via the control protocol but we don't know a descriptor or
10778 microdescriptor for one of the specified relays. Fixes bug 12718;
10779 bugfix on 0.2.3.1-alpha.
10780 - Avoid an illegal read from stack when initializing the TLS
10781 module using a version of OpenSSL without all of the ciphers
10782 used by the v2 link handshake. Fixes bug 12227; bugfix on
10783 0.2.4.8-alpha. Found by "starlight".
10786 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
10790 Changes in version 0.2.5.5-alpha - 2014-06-18
10791 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
10792 0.2.5.x release series, including a couple of DoS issues, some
10793 performance regressions, a large number of bugs affecting the Linux
10794 seccomp2 sandbox code, and various other bugfixes. It also adds
10795 diagnostic bugfixes for a few tricky issues that we're trying to
10798 o Major features (security, traffic analysis resistance):
10799 - Several major improvements to the algorithm used to decide when to
10800 close TLS connections. Previous versions of Tor closed connections
10801 at a fixed interval after the last time a non-padding cell was
10802 sent over the connection, regardless of the target of the
10803 connection. Now, we randomize the intervals by adding up to 50% of
10804 their base value, we measure the length of time since connection
10805 last had at least one circuit, and we allow connections to known
10806 ORs to remain open a little longer (15 minutes instead of 3
10807 minutes minimum). These changes should improve Tor's resistance
10808 against some kinds of traffic analysis, and lower some overhead
10809 from needlessly closed connections. Fixes ticket 6799.
10810 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
10812 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
10813 - Fix a memory leak that could occur if a microdescriptor parse
10814 fails during the tokenizing step. This bug could enable a memory
10815 exhaustion attack by directory servers. Fixes bug 11649; bugfix
10818 o Major bugfixes (security, directory authorities):
10819 - Directory authorities now include a digest of each relay's
10820 identity key as a part of its microdescriptor.
10822 This is a workaround for bug 11743 (reported by "cypherpunks"),
10823 where Tor clients do not support receiving multiple
10824 microdescriptors with the same SHA256 digest in the same
10825 consensus. When clients receive a consensus like this, they only
10826 use one of the relays. Without this fix, a hostile relay could
10827 selectively disable some client use of target relays by
10828 constructing a router descriptor with a different identity and the
10829 same microdescriptor parameters and getting the authorities to
10830 list it in a microdescriptor consensus. This fix prevents an
10831 attacker from causing a microdescriptor collision, because the
10832 router's identity is not forgeable.
10834 o Major bugfixes (relay):
10835 - Use a direct dirport connection when uploading non-anonymous
10836 descriptors to the directory authorities. Previously, relays would
10837 incorrectly use tunnel connections under a fairly wide variety of
10838 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
10839 - When a circuit accidentally has the same circuit ID for its
10840 forward and reverse direction, correctly detect the direction of
10841 cells using that circuit. Previously, this bug made roughly one
10842 circuit in a million non-functional. Fixes bug 12195; this is a
10843 bugfix on every version of Tor.
10845 o Major bugfixes (client, pluggable transports):
10846 - When managing pluggable transports, use OS notification facilities
10847 to learn if they have crashed, and don't attempt to kill any
10848 process that has already exited. Fixes bug 8746; bugfix
10851 o Minor features (diagnostic):
10852 - When logging a warning because of bug 7164, additionally check the
10853 hash table for consistency (as proposed on ticket 11737). This may
10854 help diagnose bug 7164.
10855 - When we log a heartbeat, log how many one-hop circuits we have
10856 that are at least 30 minutes old, and log status information about
10857 a few of them. This is an attempt to track down bug 8387.
10858 - When encountering an unexpected CR while writing text to a file on
10859 Windows, log the name of the file. Should help diagnosing
10861 - Give more specific warnings when a client notices that an onion
10862 handshake has failed. Fixes ticket 9635.
10863 - Add significant new logging code to attempt to diagnose bug 12184,
10864 where relays seem to run out of available circuit IDs.
10865 - Improve the diagnostic log message for bug 8387 even further to
10866 try to improve our odds of figuring out why one-hop directory
10867 circuits sometimes do not get closed.
10869 o Minor features (security, memory management):
10870 - Memory allocation tricks (mempools and buffer freelists) are now
10871 disabled by default. You can turn them back on with
10872 --enable-mempools and --enable-buf-freelists respectively. We're
10873 disabling these features because malloc performance is good enough
10874 on most platforms, and a similar feature in OpenSSL exacerbated
10875 exploitation of the Heartbleed attack. Resolves ticket 11476.
10877 o Minor features (security):
10878 - Apply the secure SipHash-2-4 function to the hash table mapping
10879 circuit IDs and channels to circuits. We missed this one when we
10880 were converting all the other hash functions to use SipHash back
10881 in 0.2.5.3-alpha. Resolves ticket 11750.
10883 o Minor features (build):
10884 - The configure script has a --disable-seccomp option to turn off
10885 support for libseccomp on systems that have it, in case it (or
10886 Tor's use of it) is broken. Resolves ticket 11628.
10888 o Minor features (other):
10889 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
10892 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
10893 - When running a hidden service, do not allow TunneledDirConns 0;
10894 this will keep the hidden service from running, and also
10895 make it publish its descriptors directly over HTTP. Fixes bug 10849;
10896 bugfix on 0.2.1.1-alpha.
10898 o Minor bugfixes (performance):
10899 - Avoid a bug where every successful connection made us recompute
10900 the flag telling us whether we have sufficient information to
10901 build circuits. Previously, we would forget our cached value
10902 whenever we successfully opened a channel (or marked a router as
10903 running or not running for any other reason), regardless of
10904 whether we had previously believed the router to be running. This
10905 forced us to run an expensive update operation far too often.
10906 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
10907 - Avoid using tor_memeq() for checking relay cell integrity. This
10908 removes a possible performance bottleneck. Fixes part of bug
10909 12169; bugfix on 0.2.1.31.
10911 o Minor bugfixes (compilation):
10912 - Fix compilation of test_status.c when building with MVSC. Bugfix
10913 on 0.2.5.4-alpha. Patch from Gisle Vanem.
10914 - Resolve GCC complaints on OpenBSD about discarding constness in
10915 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
10916 on 0.1.1.23. Patch from Dana Koch.
10917 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
10918 treatment of long and time_t as comparable types. Fixes part of
10919 bug 11633. Patch from Dana Koch.
10920 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
10921 11623; bugfix on 0.2.5.3-alpha.
10922 - When deciding whether to build the 64-bit curve25519
10923 implementation, detect platforms where we can compile 128-bit
10924 arithmetic but cannot link it. Fixes bug 11729; bugfix on
10925 0.2.4.8-alpha. Patch from "conradev".
10926 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
10927 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
10928 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
10931 o Minor bugfixes (Directory server):
10932 - When sending a compressed set of descriptors or microdescriptors,
10933 make sure to finalize the zlib stream. Previously, we would write
10934 all the compressed data, but if the last descriptor we wanted to
10935 send was missing or too old, we would not mark the stream as
10936 finished. This caused problems for decompression tools. Fixes bug
10937 11648; bugfix on 0.1.1.23.
10939 o Minor bugfixes (Linux seccomp sandbox):
10940 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
10941 11622; bugfix on 0.2.5.1-alpha.
10942 - Avoid crashing when re-opening listener ports with the seccomp
10943 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
10944 - Avoid crashing with the seccomp sandbox enabled along with
10945 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
10946 - When we receive a SIGHUP with the sandbox enabled, correctly
10947 support rotating our log files. Fixes bug 12032; bugfix
10949 - Avoid crash when running with sandboxing enabled and
10950 DirReqStatistics not disabled. Fixes bug 12035; bugfix
10952 - Fix a "BUG" warning when trying to write bridge-stats files with
10953 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
10955 - Prevent the sandbox from crashing on startup when run with the
10956 --enable-expensive-hardening configuration option. Fixes bug
10957 11477; bugfix on 0.2.5.4-alpha.
10958 - When running with DirPortFrontPage and sandboxing both enabled,
10959 reload the DirPortFrontPage correctly when restarting. Fixes bug
10960 12028; bugfix on 0.2.5.1-alpha.
10961 - Don't try to enable the sandbox when using the Tor binary to check
10962 its configuration, hash a passphrase, or so on. Doing so was
10963 crashing on startup for some users. Fixes bug 11609; bugfix
10965 - Avoid warnings when running with sandboxing and node statistics
10966 enabled at the same time. Fixes part of 12064; bugfix on
10967 0.2.5.1-alpha. Patch from Michael Wolf.
10968 - Avoid warnings when running with sandboxing enabled at the same
10969 time as cookie authentication, hidden services, or directory
10970 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
10971 - Do not allow options that require calls to exec to be enabled
10972 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
10973 bug 12043; bugfix on 0.2.5.1-alpha.
10974 - Handle failures in getpwnam()/getpwuid() when running with the
10975 User option set and the Linux syscall sandbox enabled. Fixes bug
10976 11946; bugfix on 0.2.5.1-alpha.
10977 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
10978 to avoid calling getaddrinfo() after installing the sandbox
10979 filters. Previously, it preloaded a cache with the IPv4 address
10980 for our hostname, and nothing else. Now, it loads the cache with
10981 every address that it used to initialize the Tor process. Fixes
10982 bug 11970; bugfix on 0.2.5.1-alpha.
10984 o Minor bugfixes (pluggable transports):
10985 - Enable the ExtORPortCookieAuthFile option, to allow changing the
10986 default location of the authentication token for the extended OR
10987 Port as used by sever-side pluggable transports. We had
10988 implemented this option before, but the code to make it settable
10989 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
10990 - Avoid another 60-second delay when starting Tor in a pluggable-
10991 transport-using configuration when we already have cached
10992 descriptors for our bridges. Fixes bug 11965; bugfix
10995 o Minor bugfixes (client):
10996 - Avoid "Tried to open a socket with DisableNetwork set" warnings
10997 when starting a client with bridges configured and DisableNetwork
10998 set. (Tor launcher starts Tor with DisableNetwork set the first
10999 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
11001 o Minor bugfixes (testing):
11002 - The Python parts of the test scripts now work on Python 3 as well
11003 as Python 2, so systems where '/usr/bin/python' is Python 3 will
11004 no longer have the tests break. Fixes bug 11608; bugfix
11006 - When looking for versions of python that we could run the tests
11007 with, check for "python2.7" and "python3.3"; previously we were
11008 only looking for "python", "python2", and "python3". Patch from
11009 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
11010 - Fix all valgrind warnings produced by the unit tests. There were
11011 over a thousand memory leak warnings previously, mostly produced
11012 by forgetting to free things in the unit test code. Fixes bug
11013 11618, bugfixes on many versions of Tor.
11015 o Minor bugfixes (tor-fw-helper):
11016 - Give a correct log message when tor-fw-helper fails to launch.
11017 (Previously, we would say something like "tor-fw-helper sent us a
11018 string we could not parse".) Fixes bug 9781; bugfix
11021 o Minor bugfixes (relay, threading):
11022 - Check return code on spawn_func() in cpuworker code, so that we
11023 don't think we've spawned a nonworking cpuworker and write junk to
11024 it forever. Fix related to bug 4345; bugfix on all released Tor
11025 versions. Found by "skruffy".
11026 - Use a pthread_attr to make sure that spawn_func() cannot return an
11027 error while at the same time launching a thread. Fix related to
11028 bug 4345; bugfix on all released Tor versions. Reported
11031 o Minor bugfixes (relay, oom prevention):
11032 - Correctly detect the total available system memory. We tried to do
11033 this in 0.2.5.4-alpha, but the code was set up to always return an
11034 error value, even on success. Fixes bug 11805; bugfix
11037 o Minor bugfixes (relay, other):
11038 - We now drop CREATE cells for already-existent circuit IDs and for
11039 zero-valued circuit IDs, regardless of other factors that might
11040 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
11042 - Avoid an illegal read from stack when initializing the TLS module
11043 using a version of OpenSSL without all of the ciphers used by the
11044 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
11046 - When rejecting DATA cells for stream_id zero, still count them
11047 against the circuit's deliver window so that we don't fail to send
11048 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
11050 o Minor bugfixes (logging):
11051 - Fix a misformatted log message about delayed directory fetches.
11052 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
11053 - Squelch a spurious LD_BUG message "No origin circuit for
11054 successful SOCKS stream" in certain hidden service failure cases;
11058 - Include a tor.service file in contrib/dist for use with systemd.
11059 Some distributions will be able to use this file unmodified;
11060 others will need to tweak it, or write their own. Patch from Jamie
11061 Nguyen; resolves ticket 8368.
11064 - Clean up several option names in the manpage to match their real
11065 names, add the missing documentation for a couple of testing and
11066 directory authority options, remove the documentation for a
11067 V2-directory fetching option that no longer exists. Resolves
11069 - Correct the documentation so that it lists the correct directory
11070 for the stats files. (They are in a subdirectory called "stats",
11072 - In the manpage, move more authority-only options into the
11073 directory authority section so that operators of regular directory
11074 caches don't get confused.
11077 - The contrib directory has been sorted and tidied. Before, it was
11078 an unsorted dumping ground for useful and not-so-useful things.
11079 Now, it is divided based on functionality, and the items which
11080 seemed to be nonfunctional or useless have been removed. Resolves
11081 ticket 8966; based on patches from "rl1987".
11084 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
11085 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
11086 - The TunnelDirConns and PreferTunnelledDirConns options no longer
11087 exist; tunneled directory connections have been available since
11088 0.1.2.5-alpha, and turning them off is not a good idea. This is a
11089 brute-force fix for 10849, where "TunnelDirConns 0" would break
11093 Changes in version 0.2.4.22 - 2014-05-16
11094 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
11095 alpha release series. These include blocking all authority signing
11096 keys that may have been affected by the OpenSSL "heartbleed" bug,
11097 choosing a far more secure set of TLS ciphersuites by default, closing
11098 a couple of memory leaks that could be used to run a target relay out
11099 of RAM, and several others.
11101 o Major features (security, backport from 0.2.5.4-alpha):
11102 - Block authority signing keys that were used on authorities
11103 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
11104 don't have any evidence that these keys _were_ compromised; we're
11105 doing this to be prudent.) Resolves ticket 11464.
11107 o Major bugfixes (security, OOM):
11108 - Fix a memory leak that could occur if a microdescriptor parse
11109 fails during the tokenizing step. This bug could enable a memory
11110 exhaustion attack by directory servers. Fixes bug 11649; bugfix
11113 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
11114 - The relay ciphersuite list is now generated automatically based on
11115 uniform criteria, and includes all OpenSSL ciphersuites with
11116 acceptable strength and forward secrecy. Previously, we had left
11117 some perfectly fine ciphersuites unsupported due to omission or
11118 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
11119 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
11120 - Relays now trust themselves to have a better view than clients of
11121 which TLS ciphersuites are better than others. (Thanks to bug
11122 11513, the relay list is now well-considered, whereas the client
11123 list has been chosen mainly for anti-fingerprinting purposes.)
11124 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
11125 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
11126 AES128. Resolves ticket 11528.
11127 - Clients now try to advertise the same list of ciphersuites as
11128 Firefox 28. This change enables selection of (fast) GCM
11129 ciphersuites, disables some strange old ciphers, and stops
11130 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
11131 Resolves ticket 11438.
11133 o Minor bugfixes (configuration, security):
11134 - When running a hidden service, do not allow TunneledDirConns 0:
11135 trying to set that option together with a hidden service would
11136 otherwise prevent the hidden service from running, and also make
11137 it publish its descriptors directly over HTTP. Fixes bug 10849;
11138 bugfix on 0.2.1.1-alpha.
11140 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
11141 - Avoid sending a garbage value to the controller when a circuit is
11142 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
11144 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
11145 - Stop leaking memory when we successfully resolve a PTR record.
11146 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
11148 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
11149 - Avoid 60-second delays in the bootstrapping process when Tor is
11150 launching for a second time while using bridges. Fixes bug 9229;
11151 bugfix on 0.2.0.3-alpha.
11153 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
11154 - Give the correct URL in the warning message when trying to run a
11155 relay on an ancient version of Windows. Fixes bug 9393.
11157 o Minor bugfixes (compilation):
11158 - Fix a compilation error when compiling with --disable-curve25519.
11159 Fixes bug 9700; bugfix on 0.2.4.17-rc.
11162 - Downgrade the warning severity for the the "md was still
11163 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
11164 for trying to diagnose this bug, and the current warning in
11165 earlier versions of tor achieves nothing useful. Addresses warning
11168 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
11169 - When we run out of usable circuit IDs on a channel, log only one
11170 warning for the whole channel, and describe how many circuits
11171 there were on the channel. Fixes part of ticket 11553.
11173 o Minor features (security, backport from 0.2.5.4-alpha):
11174 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
11175 leave the default at 8GBytes), to better support Raspberry Pi
11176 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
11178 o Documentation (backport from 0.2.5.4-alpha):
11179 - Correctly document that we search for a system torrc file before
11180 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
11184 Changes in version 0.2.5.4-alpha - 2014-04-25
11185 Tor 0.2.5.4-alpha includes several security and performance
11186 improvements for clients and relays, including blacklisting authority
11187 signing keys that were used while susceptible to the OpenSSL
11188 "heartbleed" bug, fixing two expensive functions on busy relays,
11189 improved TLS ciphersuite preference lists, support for run-time
11190 hardening on compilers that support AddressSanitizer, and more work on
11191 the Linux sandbox code.
11193 There are also several usability fixes for clients (especially clients
11194 that use bridges), two new TransPort protocols supported (one on
11195 OpenBSD, one on FreeBSD), and various other bugfixes.
11197 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
11198 have accumulated many known flaws; everyone should upgrade.
11200 o Major features (security):
11201 - If you don't specify MaxMemInQueues yourself, Tor now tries to
11202 pick a good value based on your total system memory. Previously,
11203 the default was always 8 GB. You can still override the default by
11204 setting MaxMemInQueues yourself. Resolves ticket 11396.
11205 - Block authority signing keys that were used on authorities
11206 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
11207 don't have any evidence that these keys _were_ compromised; we're
11208 doing this to be prudent.) Resolves ticket 11464.
11210 o Major features (relay performance):
11211 - Speed up server-side lookups of rendezvous and introduction point
11212 circuits by using hashtables instead of linear searches. These
11213 functions previously accounted between 3 and 7% of CPU usage on
11214 some busy relays. Resolves ticket 9841.
11215 - Avoid wasting CPU when extending a circuit over a channel that is
11216 nearly out of circuit IDs. Previously, we would do a linear scan
11217 over possible circuit IDs before finding one or deciding that we
11218 had exhausted our possibilities. Now, we try at most 64 random
11219 circuit IDs before deciding that we probably won't succeed. Fixes
11220 a possible root cause of ticket 11553.
11222 o Major features (seccomp2 sandbox, Linux only):
11223 - The seccomp2 sandbox can now run a test network for multiple hours
11224 without crashing. The sandbox is still experimental, and more bugs
11225 will probably turn up. To try it, enable "Sandbox 1" on a Linux
11226 host. Resolves ticket 11351.
11227 - Strengthen sandbox code: the sandbox can now test the arguments
11228 for rename(), and blocks _sysctl() entirely. Resolves another part
11230 - When the sandbox blocks a system call, it now tries to log a stack
11231 trace before exiting. Resolves ticket 11465.
11233 o Major bugfixes (TLS cipher selection):
11234 - The relay ciphersuite list is now generated automatically based on
11235 uniform criteria, and includes all OpenSSL ciphersuites with
11236 acceptable strength and forward secrecy. Previously, we had left
11237 some perfectly fine ciphersuites unsupported due to omission or
11238 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
11239 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
11240 - Relays now trust themselves to have a better view than clients of
11241 which TLS ciphersuites are better than others. (Thanks to bug
11242 11513, the relay list is now well-considered, whereas the client
11243 list has been chosen mainly for anti-fingerprinting purposes.)
11244 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
11245 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
11246 AES128. Resolves ticket 11528.
11247 - Clients now try to advertise the same list of ciphersuites as
11248 Firefox 28. This change enables selection of (fast) GCM
11249 ciphersuites, disables some strange old ciphers, and stops
11250 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
11251 Resolves ticket 11438.
11253 o Major bugfixes (bridge client):
11254 - Avoid 60-second delays in the bootstrapping process when Tor is
11255 launching for a second time while using bridges. Fixes bug 9229;
11256 bugfix on 0.2.0.3-alpha.
11258 o Minor features (transparent proxy, *BSD):
11259 - Support FreeBSD's ipfw firewall interface for TransPort ports on
11260 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
11261 10267; patch from "yurivict".
11262 - Support OpenBSD's divert-to rules with the pf firewall for
11263 transparent proxy ports. To enable it, set "TransProxyType
11264 pf-divert". This allows Tor to run a TransPort transparent proxy
11265 port on OpenBSD 4.4 or later without root privileges. See the
11266 pf.conf(5) manual page for information on configuring pf to use
11267 divert-to rules. Closes ticket 10896; patch from Dana Koch.
11269 o Minor features (security):
11270 - New --enable-expensive-hardening option to enable security
11271 hardening options that consume nontrivial amounts of CPU and
11272 memory. Right now, this includes AddressSanitizer and UbSan, which
11273 are supported in newer versions of GCC and Clang. Closes ticket
11276 o Minor features (log verbosity):
11277 - Demote the message that we give when a flushing connection times
11278 out for too long from NOTICE to INFO. It was usually meaningless.
11279 Resolves ticket 5286.
11280 - Don't log so many notice-level bootstrapping messages at startup
11281 about downloading descriptors. Previously, we'd log a notice
11282 whenever we learned about more routers. Now, we only log a notice
11283 at every 5% of progress. Fixes bug 9963.
11284 - Warn less verbosely when receiving a malformed
11285 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
11286 - When we run out of usable circuit IDs on a channel, log only one
11287 warning for the whole channel, and describe how many circuits
11288 there were on the channel. Fixes part of ticket 11553.
11290 o Minor features (relay):
11291 - If a circuit timed out for at least 3 minutes, check if we have a
11292 new external IP address, and publish a new descriptor with the new
11293 IP address if it changed. Resolves ticket 2454.
11295 o Minor features (controller):
11296 - Make the entire exit policy available from the control port via
11297 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
11299 - Because of the fix for ticket 11396, the real limit for memory
11300 usage may no longer match the configured MaxMemInQueues value. The
11301 real limit is now exposed via GETINFO limits/max-mem-in-queues.
11303 o Minor features (bridge client):
11304 - Report a more useful failure message when we can't connect to a
11305 bridge because we don't have the right pluggable transport
11306 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
11308 o Minor features (diagnostic):
11309 - Add more log messages to diagnose bug 7164, which causes
11310 intermittent "microdesc_free() called but md was still referenced"
11311 warnings. We now include more information, to figure out why we
11312 might be cleaning a microdescriptor for being too old if it's
11313 still referenced by a live node_t object.
11315 o Minor bugfixes (client, DNSPort):
11316 - When using DNSPort, try to respond to AAAA requests with AAAA
11317 answers. Previously, we hadn't looked at the request type when
11318 deciding which answer type to prefer. Fixes bug 10468; bugfix on
11320 - When receiving a DNS query for an unsupported record type, reply
11321 with no answer rather than with a NOTIMPL error. This behavior
11322 isn't correct either, but it will break fewer client programs, we
11323 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
11326 o Minor bugfixes (exit relay):
11327 - Stop leaking memory when we successfully resolve a PTR record.
11328 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
11330 o Minor bugfixes (bridge client):
11331 - Stop accepting bridge lines containing hostnames. Doing so would
11332 cause clients to perform DNS requests on the hostnames, which was
11333 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
11334 - Avoid a 60-second delay in the bootstrapping process when a Tor
11335 client with pluggable transports re-reads its configuration at
11336 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
11338 o Minor bugfixes (client, logging during bootstrap):
11339 - Warn only once if we start logging in an unsafe way. Previously,
11340 we complain as many times as we had problems. Fixes bug 9870;
11341 bugfix on 0.2.5.1-alpha.
11342 - Only report the first fatal bootstrap error on a given OR
11343 connection. This stops us from telling the controller bogus error
11344 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
11345 - Be more helpful when trying to run sandboxed on Linux without
11346 libseccomp. Instead of saying "Sandbox is not implemented on this
11347 platform", we now explain that we need to be built with
11348 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
11349 - Avoid generating spurious warnings when starting with
11350 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
11353 o Minor bugfixes (closing OR connections):
11354 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
11355 check if it's an or_connection_t and correctly call
11356 connection_or_close_for_error() rather than
11357 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
11359 - When closing all connections on setting DisableNetwork to 1, use
11360 connection_or_close_normally() rather than closing OR connections
11361 out from under the channel layer. Fixes bug 11306; bugfix on
11364 o Minor bugfixes (controller):
11365 - Avoid sending a garbage value to the controller when a circuit is
11366 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
11368 o Minor bugfixes (tor-fw-helper):
11369 - Allow tor-fw-helper to build again by adding src/ext to its
11370 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
11372 o Minor bugfixes (bridges):
11373 - Avoid potential crashes or bad behavior when launching a
11374 server-side managed proxy with ORPort or ExtORPort temporarily
11375 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
11377 o Minor bugfixes (platform-specific):
11378 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
11379 bug 11426; bugfix on 0.2.5.3-alpha.
11380 - When dumping a malformed directory object to disk, save it in
11381 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
11383 - Don't report failures from make_socket_reuseable() on incoming
11384 sockets on OSX: this can happen when incoming connections close
11385 early. Fixes bug 10081.
11387 o Minor bugfixes (trivial memory leaks):
11388 - Fix a small memory leak when signing a directory object. Fixes bug
11389 11275; bugfix on 0.2.4.13-alpha.
11390 - Free placeholder entries in our circuit table at exit; fixes a
11391 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
11392 - Don't re-initialize a second set of OpenSSL mutexes when starting
11393 up. Previously, we'd make one set of mutexes, and then immediately
11394 replace them with another. Fixes bug 11726; bugfix on
11396 - Resolve some memory leaks found by coverity in the unit tests, on
11397 exit in tor-gencert, and on a failure to compute digests for our
11398 own keys when generating a v3 networkstatus vote. These leaks
11399 should never have affected anyone in practice.
11401 o Minor bugfixes (hidden service):
11402 - Only retry attempts to connect to a chosen rendezvous point 8
11403 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
11405 o Minor bugfixes (misc code correctness):
11406 - Fix various instances of undefined behavior in channeltls.c,
11407 tor_memmem(), and eventdns.c that would cause us to construct
11408 pointers to memory outside an allocated object. (These invalid
11409 pointers were not accessed, but C does not even allow them to
11410 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
11411 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
11412 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
11413 fix some miscellaneous errors in our tests and codebase. Fixes bug
11414 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
11415 - Always check return values for unlink, munmap, UnmapViewOfFile;
11416 check strftime return values more often. In some cases all we can
11417 do is report a warning, but this may help prevent deeper bugs from
11418 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
11420 - Fix numerous warnings from the clang "scan-build" static analyzer.
11421 Some of these are programming style issues; some of them are false
11422 positives that indicated awkward code; some are undefined behavior
11423 cases related to constructing (but not using) invalid pointers;
11424 some are assumptions about API behavior; some are (harmlessly)
11425 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
11426 correct; and one or two are genuine bugs that weren't reachable
11427 from the rest of the program. Fixes bug 8793; bugfixes on many,
11431 - Build the torify.1 manpage again. Previously, we were only trying
11432 to build it when also building tor-fw-helper. That's why we didn't
11433 notice that we'd broken the ability to build it. Fixes bug 11321;
11434 bugfix on 0.2.5.1-alpha.
11435 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
11436 11061; bugfix on 0.2.4.7-alpha.
11437 - Correctly document that we search for a system torrc file before
11438 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
11440 - Resolve warnings from Doxygen.
11442 o Code simplifications and refactoring:
11443 - Remove is_internal_IP() function. Resolves ticket 4645.
11444 - Remove unused function circuit_dump_by_chan from circuitlist.c.
11445 Closes issue 9107; patch from "marek".
11446 - Change our use of the ENUM_BF macro to avoid declarations that
11449 o Deprecated versions:
11450 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
11451 attention for some while. Directory authorities no longer accept
11452 descriptors from relays running any version of Tor prior to Tor
11453 0.2.3.16-alpha. Resolves ticket 11149.
11456 - New macros in test.h to simplify writing mock-functions for unit
11457 tests. Part of ticket 11507. Patch from Dana Koch.
11458 - Complete tests for the status.c module. Resolves ticket 11507.
11459 Patch from Dana Koch.
11462 - Remove all code for the long unused v1 directory protocol.
11463 Resolves ticket 11070.
11466 Changes in version 0.2.5.3-alpha - 2014-03-22
11467 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
11468 two new anti-DoS features for Tor relays, resolves a bug that kept
11469 SOCKS5 support for IPv6 from working, fixes several annoying usability
11470 issues for bridge users, and removes more old code for unused
11473 The Tor 0.2.5.x release series is now in patch-freeze: no feature
11474 patches not already written will be considered for inclusion in 0.2.5.x.
11476 o Major features (relay security, DoS-resistance):
11477 - When deciding whether we have run out of memory and we need to
11478 close circuits, also consider memory allocated in buffers for
11479 streams attached to each circuit.
11481 This change, which extends an anti-DoS feature introduced in
11482 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
11483 better resist more memory-based DoS attacks than before. Since the
11484 MaxMemInCellQueues option now applies to all queues, it is renamed
11485 to MaxMemInQueues. This feature fixes bug 10169.
11486 - Avoid hash-flooding denial-of-service attacks by using the secure
11487 SipHash-2-4 hash function for our hashtables. Without this
11488 feature, an attacker could degrade performance of a targeted
11489 client or server by flooding their data structures with a large
11490 number of entries to be stored at the same hash table position,
11491 thereby slowing down the Tor instance. With this feature, hash
11492 table positions are derived from a randomized cryptographic key,
11493 and an attacker cannot predict which entries will collide. Closes
11495 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
11496 the default at 8GBytes), to better support Raspberry Pi users. Fixes
11497 bug 9686; bugfix on 0.2.4.14-alpha.
11499 o Minor features (bridges, pluggable transports):
11500 - Bridges now write the SHA1 digest of their identity key
11501 fingerprint (that is, a hash of a hash of their public key) to
11502 notice-level logs, and to a new hashed-fingerprint file. This
11503 information will help bridge operators look up their bridge in
11504 Globe and similar tools. Resolves ticket 10884.
11505 - Improve the message that Tor displays when running as a bridge
11506 using pluggable transports without an Extended ORPort listener.
11507 Also, log the message in the log file too. Resolves ticket 11043.
11509 o Minor features (other):
11510 - Add a new option, PredictedPortsRelevanceTime, to control how long
11511 after having received a request to connect to a given port Tor
11512 will try to keep circuits ready in anticipation of future requests
11513 for that port. Patch from "unixninja92"; implements ticket 9176.
11514 - Generate a warning if any ports are listed in the SocksPolicy,
11515 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
11516 AuthDirBadExit options. (These options only support address
11517 ranges.) Fixes part of ticket 11108.
11518 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
11521 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
11522 - Build without warnings under clang 3.4. (We have some macros that
11523 define static functions only some of which will get used later in
11524 the module. Starting with clang 3.4, these give a warning unless the
11525 unused attribute is set on them.) Resolves ticket 10904.
11526 - Fix build warnings about missing "a2x" comment when building the
11527 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
11528 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
11530 o Minor bugfixes (client):
11531 - Improve the log message when we can't connect to a hidden service
11532 because all of the hidden service directory nodes hosting its
11533 descriptor are excluded. Improves on our fix for bug 10722, which
11534 was a bugfix on 0.2.0.10-alpha.
11535 - Raise a control port warning when we fail to connect to all of
11536 our bridges. Previously, we didn't inform the controller, and
11537 the bootstrap process would stall. Fixes bug 11069; bugfix on
11539 - Exit immediately when a process-owning controller exits.
11540 Previously, tor relays would wait for a little while after their
11541 controller exited, as if they had gotten an INT signal -- but this
11542 was problematic, since there was no feedback for the user. To do a
11543 clean shutdown, controllers should send an INT signal and give Tor
11544 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
11545 - Stop attempting to connect to bridges before our pluggable
11546 transports are configured (harmless but resulted in some erroneous
11547 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
11548 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
11549 generating incorrect SOCKS5 responses, and confusing client
11550 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
11552 o Minor bugfixes (relays and bridges):
11553 - Avoid crashing on a malformed resolv.conf file when running a
11554 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
11555 - Non-exit relays no longer launch mock DNS requests to check for
11556 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
11557 non-exit relays stopped servicing DNS requests. Fixes bug 965;
11558 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
11559 - Bridges now report complete directory request statistics. Related
11560 to bug 5824; bugfix on 0.2.2.1-alpha.
11561 - Bridges now never collect statistics that were designed for
11562 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
11563 - Stop giving annoying warning messages when we decide not to launch
11564 a pluggable transport proxy that we don't need (because there are
11565 no bridges configured to use it). Resolves ticket 5018; bugfix
11567 - Give the correct URL in the warning message when trying to run a
11568 relay on an ancient version of Windows. Fixes bug 9393.
11570 o Minor bugfixes (backtrace support):
11571 - Support automatic backtraces on more platforms by using the
11572 "-fasynchronous-unwind-tables" compiler option. This option is
11573 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
11574 is on by default and table generation is not. This doesn't yet
11575 add Windows support; only Linux, OSX, and some BSDs are affected.
11576 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
11577 - Avoid strange behavior if two threads hit failed assertions at the
11578 same time and both try to log backtraces at once. (Previously, if
11579 this had happened, both threads would have stored their intermediate
11580 results in the same buffer, and generated junk outputs.) Reported by
11581 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
11582 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
11583 0.2.5.2-alpha; patch from Nick Hopper.
11585 o Minor bugfixes (unit tests):
11586 - Fix a small bug in the unit tests that might have made the tests
11587 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
11588 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
11591 - Remove all remaining code related to version-0 hidden service
11592 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
11593 the rest of bug 10841.
11596 - Document in the manpage that "KBytes" may also be written as
11597 "kilobytes" or "KB", that "Kbits" may also be written as
11598 "kilobits", and so forth. Closes ticket 9222.
11599 - Document that the ClientOnly config option overrides ORPort.
11600 Our old explanation made ClientOnly sound as though it did
11601 nothing at all. Resolves bug 9059.
11602 - Explain that SocksPolicy, DirPolicy, and similar options don't
11603 take port arguments. Fixes the other part of ticket 11108.
11604 - Fix a comment about the rend_server_descriptor_t.protocols field
11605 to more accurately describe its range. Also, make that field
11606 unsigned, to more accurately reflect its usage. Fixes bug 9099;
11607 bugfix on 0.2.1.5-alpha.
11608 - Fix the manpage's description of HiddenServiceAuthorizeClient:
11609 the maximum client name length is 16, not 19. Fixes bug 11118;
11610 bugfix on 0.2.1.6-alpha.
11612 o Code simplifications and refactoring:
11613 - Get rid of router->address, since in all cases it was just the
11614 string representation of router->addr. Resolves ticket 5528.
11616 o Test infrastructure:
11617 - Update to the latest version of tinytest.
11618 - Improve the tinytest implementation of string operation tests so
11619 that comparisons with NULL strings no longer crash the tests; they
11620 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
11623 Changes in version 0.2.4.21 - 2014-02-28
11624 Tor 0.2.4.21 further improves security against potential adversaries who
11625 find breaking 1024-bit crypto doable, and backports several stability
11626 and robustness patches from the 0.2.5 branch.
11628 o Major features (client security):
11629 - When we choose a path for a 3-hop circuit, make sure it contains
11630 at least one relay that supports the NTor circuit extension
11631 handshake. Otherwise, there is a chance that we're building
11632 a circuit that's worth attacking by an adversary who finds
11633 breaking 1024-bit crypto doable, and that chance changes the game
11634 theory. Implements ticket 9777.
11637 - Do not treat streams that fail with reason
11638 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
11639 since it could also indicate an ENETUNREACH connection error. Fixes
11640 part of bug 10777; bugfix on 0.2.4.8-alpha.
11642 o Code simplification and refactoring:
11643 - Remove data structures which were introduced to implement the
11644 CellStatistics option: they are now redundant with the new timestamp
11645 field in the regular packed_cell_t data structure, which we did
11646 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
11649 - Always clear OpenSSL bignums before freeing them -- even bignums
11650 that don't contain secrets. Resolves ticket 10793. Patch by
11652 - Build without warnings under clang 3.4. (We have some macros that
11653 define static functions only some of which will get used later in
11654 the module. Starting with clang 3.4, these give a warning unless the
11655 unused attribute is set on them.) Resolves ticket 10904.
11656 - Update geoip and geoip6 files to the February 7 2014 Maxmind
11657 GeoLite2 Country database.
11660 - Set the listen() backlog limit to the largest actually supported
11661 on the system, not to the value in a header file. Fixes bug 9716;
11662 bugfix on every released Tor.
11663 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
11664 exit node as a NOROUTE error, not an INTERNAL error, since they
11665 can apparently happen when trying to connect to the wrong sort
11666 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
11667 - Fix build warnings about missing "a2x" comment when building the
11668 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
11669 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
11670 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
11671 not entirely remove it from the connection lists. Fixes bug 9602;
11672 bugfix on 0.2.4.4-alpha.
11673 - Fix a segmentation fault in our benchmark code when running with
11674 Fedora's OpenSSL package, or any other OpenSSL that provides
11675 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
11676 - Turn "circuit handshake stats since last time" log messages into a
11677 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
11679 o Documentation fixes:
11680 - Document that all but one DirPort entry must have the NoAdvertise
11681 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
11684 Changes in version 0.2.5.2-alpha - 2014-02-13
11685 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
11686 like the "poor random number generation" fix and the "building too many
11687 circuits" fix. It also further improves security against potential
11688 adversaries who find breaking 1024-bit crypto doable, and launches
11689 pluggable transports on demand (which gets us closer to integrating
11690 pluggable transport support by default -- not to be confused with Tor
11691 bundles enabling pluggable transports and bridges by default).
11693 o Major features (client security):
11694 - When we choose a path for a 3-hop circuit, make sure it contains
11695 at least one relay that supports the NTor circuit extension
11696 handshake. Otherwise, there is a chance that we're building
11697 a circuit that's worth attacking by an adversary who finds
11698 breaking 1024-bit crypto doable, and that chance changes the game
11699 theory. Implements ticket 9777.
11700 - Clients now look at the "usecreatefast" consensus parameter to
11701 decide whether to use CREATE_FAST or CREATE cells for the first hop
11702 of their circuit. This approach can improve security on connections
11703 where Tor's circuit handshake is stronger than the available TLS
11704 connection security levels, but the tradeoff is more computational
11705 load on guard relays. Implements proposal 221. Resolves ticket 9386.
11707 o Major features (bridges):
11708 - Don't launch pluggable transport proxies if we don't have any
11709 bridges configured that would use them. Now we can list many
11710 pluggable transports, and Tor will dynamically start one when it
11711 hears a bridge address that needs it. Resolves ticket 5018.
11712 - The bridge directory authority now assigns status flags (Stable,
11713 Guard, etc) to bridges based on thresholds calculated over all
11714 Running bridges. Now bridgedb can finally make use of its features
11715 to e.g. include at least one Stable bridge in its answers. Fixes
11718 o Major features (other):
11719 - Extend ORCONN controller event to include an "ID" parameter,
11720 and add four new controller event types CONN_BW, CIRC_BW,
11721 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
11722 The new events are emitted in private Tor networks only, with the
11723 goal of being able to better track performance and load during
11724 full-network simulations. Implements proposal 218 and ticket 7359.
11725 - On some platforms (currently: recent OSX versions, glibc-based
11726 platforms that support the ELF format, and a few other
11727 Unix-like operating systems), Tor can now dump stack traces
11728 when a crash occurs or an assertion fails. By default, traces
11729 are dumped to stderr (if possible) and to any logs that are
11730 reporting errors. Implements ticket 9299.
11733 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
11734 not entirely remove it from the connection lists. Fixes bug 9602;
11735 bugfix on 0.2.4.4-alpha.
11736 - Do not treat streams that fail with reason
11737 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
11738 since it could also indicate an ENETUNREACH connection error. Fixes
11739 part of bug 10777; bugfix on 0.2.4.8-alpha.
11741 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
11742 - Do not allow OpenSSL engines to replace the PRNG, even when
11743 HardwareAccel is set. The only default builtin PRNG engine uses
11744 the Intel RDRAND instruction to replace the entire PRNG, and
11745 ignores all attempts to seed it with more entropy. That's
11746 cryptographically stupid: the right response to a new alleged
11747 entropy source is never to discard all previously used entropy
11748 sources. Fixes bug 10402; works around behavior introduced in
11749 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
11751 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
11752 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
11753 - Avoid launching spurious extra circuits when a stream is pending.
11754 This fixes a bug where any circuit that _wasn't_ unusable for new
11755 streams would be treated as if it were, causing extra circuits to
11756 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
11758 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11759 - No longer stop reading or writing on cpuworker connections when
11760 our rate limiting buckets go empty. Now we should handle circuit
11761 handshake requests more promptly. Resolves bug 9731.
11762 - Stop trying to bootstrap all our directory information from
11763 only our first guard. Discovered while fixing bug 9946; bugfix
11766 o Minor features (bridges, pluggable transports):
11767 - Add threshold cutoffs to the networkstatus document created by
11768 the Bridge Authority. Fixes bug 1117.
11769 - On Windows, spawn background processes using the CREATE_NO_WINDOW
11770 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
11771 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
11772 Vidalia set this option for us.) Implements ticket 10297.
11774 o Minor features (security):
11775 - Always clear OpenSSL bignums before freeing them -- even bignums
11776 that don't contain secrets. Resolves ticket 10793. Patch by
11777 Florent Daignière.
11779 o Minor features (config options and command line):
11780 - Add an --allow-missing-torrc commandline option that tells Tor to
11781 run even if the configuration file specified by -f is not available.
11782 Implements ticket 10060.
11783 - Add support for the TPROXY transparent proxying facility on Linux.
11784 See documentation for the new TransProxyType option for more
11785 details. Implementation by "thomo". Closes ticket 10582.
11787 o Minor features (controller):
11788 - Add a new "HS_DESC" controller event that reports activities
11789 related to hidden service descriptors. Resolves ticket 8510.
11790 - New "DROPGUARDS" controller command to forget all current entry
11791 guards. Not recommended for ordinary use, since replacing guards
11792 too frequently makes several attacks easier. Resolves ticket 9934;
11795 o Minor features (build):
11796 - Assume that a user using ./configure --host wants to cross-compile,
11797 and give an error if we cannot find a properly named
11798 tool-chain. Add a --disable-tool-name-check option to proceed
11799 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
11800 - If we run ./configure and the compiler recognizes -fstack-protector
11801 but the linker rejects it, warn the user about a potentially missing
11802 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
11804 o Minor features (testing):
11805 - If Python is installed, "make check" now runs extra tests beyond
11806 the unit test scripts.
11807 - When bootstrapping a test network, sometimes very few relays get
11808 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
11809 specify a set of relays which should be voted Guard regardless of
11810 their uptime or bandwidth. Addresses ticket 9206.
11812 o Minor features (log messages):
11813 - When ServerTransportPlugin is set on a bridge, Tor can write more
11814 useful statistics about bridge use in its extrainfo descriptors,
11815 but only if the Extended ORPort ("ExtORPort") is set too. Add a
11816 log message to inform the user in this case. Resolves ticket 9651.
11817 - When receiving a new controller connection, log the origin address.
11818 Resolves ticket 9698; patch from "sigpipe".
11819 - When logging OpenSSL engine status at startup, log the status of
11820 more engines. Fixes ticket 10043; patch from Joshua Datko.
11821 - Turn "circuit handshake stats since last time" log messages into a
11822 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
11824 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11825 - Improve the circuit queue out-of-memory handler. Previously, when
11826 we ran low on memory, we'd close whichever circuits had the most
11827 queued cells. Now, we close those that have the *oldest* queued
11828 cells, on the theory that those are most responsible for us
11829 running low on memory. Based on analysis from a forthcoming paper
11830 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
11831 - Generate bootstrapping status update events correctly when fetching
11832 microdescriptors. Fixes bug 9927.
11833 - Update to the October 2 2013 Maxmind GeoLite Country database.
11835 o Minor bugfixes (clients):
11836 - When closing a channel that has already been open, do not close
11837 pending circuits that were waiting to connect to the same relay.
11838 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
11841 o Minor bugfixes (relays):
11842 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
11843 exit node as a NOROUTE error, not an INTERNAL error, since they
11844 can apparently happen when trying to connect to the wrong sort
11845 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
11847 o Minor bugfixes (bridges):
11848 - Fix a bug where the first connection works to a bridge that uses a
11849 pluggable transport with client-side parameters, but we don't send
11850 the client-side parameters on subsequent connections. (We don't
11851 use any pluggable transports with client-side parameters yet,
11852 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
11853 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
11855 o Minor bugfixes (node selection):
11856 - If ExcludeNodes is set, consider non-excluded hidden service
11857 directory servers before excluded ones. Do not consider excluded
11858 hidden service directory servers at all if StrictNodes is
11859 set. (Previously, we would sometimes decide to connect to those
11860 servers, and then realize before we initiated a connection that
11861 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
11862 Reported by "mr-4".
11863 - If we set the ExitNodes option but it doesn't include any nodes
11864 that have the Exit flag, we would choose not to bootstrap. Now we
11865 bootstrap so long as ExitNodes includes nodes which can exit to
11866 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
11868 o Minor bugfixes (controller and command-line):
11869 - If changing a config option via "setconf" fails in a recoverable
11870 way, we used to nonetheless write our new control ports to the
11871 file described by the "ControlPortWriteToFile" option. Now we only
11872 write out that file if we successfully switch to the new config
11873 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
11874 - When a command-line option such as --version or --help that
11875 ordinarily implies --hush appears on the command line along with
11876 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
11877 only if it appeared later on the command line. Fixes bug 9578;
11878 bugfix on 0.2.5.1-alpha.
11880 o Minor bugfixes (code correctness):
11881 - Previously we used two temporary files when writing descriptors to
11882 disk; now we only use one. Fixes bug 1376.
11883 - Remove an erroneous (but impossible and thus harmless) pointer
11884 comparison that would have allowed compilers to skip a bounds
11885 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
11886 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
11887 - Fix an always-true assertion in pluggable transports code so it
11888 actually checks what it was trying to check. Fixes bug 10046;
11889 bugfix on 0.2.3.9-alpha. Found by "dcb".
11891 o Minor bugfixes (protocol correctness):
11892 - When receiving a VERSIONS cell with an odd number of bytes, close
11893 the connection immediately since the cell is malformed. Fixes bug
11894 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
11897 o Minor bugfixes (build):
11898 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
11899 turned off (that is, without support for v2 link handshakes). Fixes
11900 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
11901 - Fix compilation warnings and startup issues when running with
11902 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
11904 - Fix compilation on Solaris 9, which didn't like us having an
11905 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
11907 o Minor bugfixes (testing):
11908 - Fix a segmentation fault in our benchmark code when running with
11909 Fedora's OpenSSL package, or any other OpenSSL that provides
11910 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
11912 o Minor bugfixes (log messages):
11913 - Fix a bug where clients using bridges would report themselves
11914 as 50% bootstrapped even without a live consensus document.
11915 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
11916 - Suppress a warning where, if there's only one directory authority
11917 in the network, we would complain that votes and signatures cannot
11918 be uploaded to other directory authorities. Fixes bug 10842;
11919 bugfix on 0.2.2.26-beta.
11920 - Report bootstrapping progress correctly when we're downloading
11921 microdescriptors. We had updated our "do we have enough microdescs
11922 to begin building circuits?" logic most recently in 0.2.4.10-alpha
11923 (see bug 5956), but we left the bootstrap status event logic at
11924 "how far through getting 1/4 of them are we?" Fixes bug 9958;
11925 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
11927 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
11928 - Avoid a crash bug when starting with a corrupted microdescriptor
11929 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
11930 - If we fail to dump a previously cached microdescriptor to disk, avoid
11931 freeing duplicate data later on. Fixes bug 10423; bugfix on
11932 0.2.4.13-alpha. Spotted by "bobnomnom".
11934 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11935 - Correctly log long IPv6 exit policies, instead of truncating them
11936 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
11937 - Our default TLS ecdhe groups were backwards: we meant to be using
11938 P224 for relays (for performance win) and P256 for bridges (since
11939 it is more common in the wild). Instead we had it backwards. After
11940 reconsideration, we decided that the default should be P256 on all
11941 hosts, since its security is probably better, and since P224 is
11942 reportedly used quite little in the wild. Found by "skruffy" on
11943 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
11944 - Free directory authority certificate download statuses on exit
11945 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
11947 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11948 - If the guard we choose first doesn't answer, we would try the
11949 second guard, but once we connected to the second guard we would
11950 abandon it and retry the first one, slowing down bootstrapping.
11951 The fix is to treat all our initially chosen guards as acceptable
11952 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
11953 - Fix an assertion failure that would occur when disabling the
11954 ORPort setting on a running Tor process while accounting was
11955 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
11956 - When examining the list of network interfaces to find our address,
11957 do not consider non-running or disabled network interfaces. Fixes
11958 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
11959 - Avoid an off-by-one error when checking buffer boundaries when
11960 formatting the exit status of a pluggable transport helper.
11961 This is probably not an exploitable bug, but better safe than
11962 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
11965 o Removed code and features:
11966 - Clients now reject any directory authority certificates lacking
11967 a dir-key-crosscert element. These have been included since
11968 0.2.1.9-alpha, so there's no real reason for them to be optional
11969 any longer. Completes proposal 157. Resolves ticket 10162.
11970 - Remove all code that existed to support the v2 directory system,
11971 since there are no longer any v2 directory authorities. Resolves
11973 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
11974 options, which were used for designating authorities as "Hidden
11975 service authorities". There has been no use of hidden service
11976 authorities since 0.2.2.1-alpha, when we stopped uploading or
11977 downloading v0 hidden service descriptors. Fixes bug 10881; also
11978 part of a fix for bug 10841.
11980 o Code simplification and refactoring:
11981 - Remove some old fallback code designed to keep Tor clients working
11982 in a network with only two working relays. Elsewhere in the code we
11983 have long since stopped supporting such networks, so there wasn't
11984 much point in keeping it around. Addresses ticket 9926.
11985 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
11986 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
11987 - Remove data structures which were introduced to implement the
11988 CellStatistics option: they are now redundant with the addition
11989 of a timestamp to the regular packed_cell_t data structure, which
11990 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
11993 o Documentation (man page) fixes:
11994 - Update manpage to describe some of the files you can expect to
11995 find in Tor's DataDirectory. Addresses ticket 9839.
11996 - Document that all but one DirPort entry must have the NoAdvertise
11997 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
11999 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12000 - Clarify the usage and risks of setting the ContactInfo torrc line
12001 for your relay or bridge. Resolves ticket 9854.
12002 - Add anchors to the manpage so we can link to the html version of
12003 the documentation for specific options. Resolves ticket 9866.
12004 - Replace remaining references to DirServer in man page and
12005 log entries. Resolves ticket 10124.
12008 - Make the "tor-gencert" tool used by directory authority operators
12009 create 2048-bit signing keys by default (rather than 1024-bit, since
12010 1024-bit is uncomfortably small these days). Addresses ticket 10324.
12013 Changes in version 0.2.4.20 - 2013-12-22
12014 Tor 0.2.4.20 fixes potentially poor random number generation for users
12015 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
12016 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
12017 and 4) have no state file in their DataDirectory (as would happen on
12018 first start). Users who generated relay or hidden service identity
12019 keys in such a situation should discard them and generate new ones.
12021 This release also fixes a logic error that caused Tor clients to build
12022 many more preemptive circuits than they actually need.
12025 - Do not allow OpenSSL engines to replace the PRNG, even when
12026 HardwareAccel is set. The only default builtin PRNG engine uses
12027 the Intel RDRAND instruction to replace the entire PRNG, and
12028 ignores all attempts to seed it with more entropy. That's
12029 cryptographically stupid: the right response to a new alleged
12030 entropy source is never to discard all previously used entropy
12031 sources. Fixes bug 10402; works around behavior introduced in
12032 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12034 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12035 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12036 - Avoid launching spurious extra circuits when a stream is pending.
12037 This fixes a bug where any circuit that _wasn't_ unusable for new
12038 streams would be treated as if it were, causing extra circuits to
12039 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12042 - Avoid a crash bug when starting with a corrupted microdescriptor
12043 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12044 - If we fail to dump a previously cached microdescriptor to disk, avoid
12045 freeing duplicate data later on. Fixes bug 10423; bugfix on
12046 0.2.4.13-alpha. Spotted by "bobnomnom".
12049 Changes in version 0.2.4.19 - 2013-12-11
12050 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
12051 (1986-2013). Aaron worked on diverse projects including helping to guide
12052 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
12053 transparency to the U.S government's PACER documents, and contributing
12054 design and development for Tor and Tor2Web. Aaron was one of the latest
12055 martyrs in our collective fight for civil liberties and human rights,
12056 and his death is all the more painful because he was one of us.
12058 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
12059 a new circuit handshake and link encryption that use ECC to provide
12060 better security and efficiency; makes relays better manage circuit
12061 creation requests; uses "directory guards" to reduce client enumeration
12062 risks; makes bridges collect and report statistics about the pluggable
12063 transports they support; cleans up and improves our geoip database;
12064 gets much closer to IPv6 support for clients, bridges, and relays; makes
12065 directory authorities use measured bandwidths rather than advertised
12066 ones when computing flags and thresholds; disables client-side DNS
12067 caching to reduce tracking risks; and fixes a big bug in bridge
12068 reachability testing. This release introduces two new design
12069 abstractions in the code: a new "channel" abstraction between circuits
12070 and or_connections to allow for implementing alternate relay-to-relay
12071 transports, and a new "circuitmux" abstraction storing the queue of
12072 circuits for a channel. The release also includes many stability,
12073 security, and privacy fixes.
12076 Changes in version 0.2.4.18-rc - 2013-11-16
12077 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
12078 series. It takes a variety of fixes from the 0.2.5.x branch to improve
12079 stability, performance, and better handling of edge cases.
12082 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12083 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12084 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12085 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12086 them to solve bug 6033.)
12089 - No longer stop reading or writing on cpuworker connections when
12090 our rate limiting buckets go empty. Now we should handle circuit
12091 handshake requests more promptly. Resolves bug 9731.
12092 - If we are unable to save a microdescriptor to the journal, do not
12093 drop it from memory and then reattempt downloading it. Fixes bug
12094 9645; bugfix on 0.2.2.6-alpha.
12095 - Stop trying to bootstrap all our directory information from
12096 only our first guard. Discovered while fixing bug 9946; bugfix
12098 - The new channel code sometimes lost track of in-progress circuits,
12099 causing long-running clients to stop building new circuits. The
12100 fix is to always call circuit_n_chan_done(chan, 0) from
12101 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
12103 o Minor bugfixes (on 0.2.4.x):
12104 - Correctly log long IPv6 exit policies, instead of truncating them
12105 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
12106 - Our default TLS ecdhe groups were backwards: we meant to be using
12107 P224 for relays (for performance win) and P256 for bridges (since
12108 it is more common in the wild). Instead we had it backwards. After
12109 reconsideration, we decided that the default should be P256 on all
12110 hosts, since its security is probably better, and since P224 is
12111 reportedly used quite little in the wild. Found by "skruffy" on
12112 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
12113 - Free directory authority certificate download statuses on exit
12114 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
12116 o Minor bugfixes (on 0.2.3.x and earlier):
12117 - If the guard we choose first doesn't answer, we would try the
12118 second guard, but once we connected to the second guard we would
12119 abandon it and retry the first one, slowing down bootstrapping.
12120 The fix is to treat all our initially chosen guards as acceptable
12121 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
12122 - Fix an assertion failure that would occur when disabling the
12123 ORPort setting on a running Tor process while accounting was
12124 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
12125 - When examining the list of network interfaces to find our address,
12126 do not consider non-running or disabled network interfaces. Fixes
12127 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
12128 - Avoid an off-by-one error when checking buffer boundaries when
12129 formatting the exit status of a pluggable transport helper.
12130 This is probably not an exploitable bug, but better safe than
12131 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
12134 o Minor features (protecting client timestamps):
12135 - Clients no longer send timestamps in their NETINFO cells. These were
12136 not used for anything, and they provided one small way for clients
12137 to be distinguished from each other as they moved from network to
12138 network or behind NAT. Implements part of proposal 222.
12139 - Clients now round timestamps in INTRODUCE cells down to the nearest
12140 10 minutes. If a new Support022HiddenServices option is set to 0, or
12141 if it's set to "auto" and the feature is disabled in the consensus,
12142 the timestamp is sent as 0 instead. Implements part of proposal 222.
12143 - Stop sending timestamps in AUTHENTICATE cells. This is not such
12144 a big deal from a security point of view, but it achieves no actual
12145 good purpose, and isn't needed. Implements part of proposal 222.
12146 - Reduce down accuracy of timestamps in hidden service descriptors.
12147 Implements part of proposal 222.
12149 o Minor features (other):
12150 - Improve the circuit queue out-of-memory handler. Previously, when
12151 we ran low on memory, we'd close whichever circuits had the most
12152 queued cells. Now, we close those that have the *oldest* queued
12153 cells, on the theory that those are most responsible for us
12154 running low on memory. Based on analysis from a forthcoming paper
12155 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
12156 - Generate bootstrapping status update events correctly when fetching
12157 microdescriptors. Fixes bug 9927.
12158 - Update to the October 2 2013 Maxmind GeoLite Country database.
12160 o Documentation fixes:
12161 - Clarify the usage and risks of setting the ContactInfo torrc line
12162 for your relay or bridge. Resolves ticket 9854.
12163 - Add anchors to the manpage so we can link to the html version of
12164 the documentation for specific options. Resolves ticket 9866.
12165 - Replace remaining references to DirServer in man page and
12166 log entries. Resolves ticket 10124.
12169 Changes in version 0.2.5.1-alpha - 2013-10-02
12170 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
12171 on Linux, allows bridges that offer pluggable transports to report usage
12172 statistics, fixes many issues to make testing easier, and provides
12173 a pile of minor features and bugfixes that have been waiting for a
12174 release of the new branch.
12176 This is the first alpha release in a new series, so expect there to
12177 be bugs. Users who would rather test out a more stable branch should
12178 stay with 0.2.4.x for now.
12180 o Major features (security):
12181 - Use the seccomp2 syscall filtering facility on Linux to limit
12182 which system calls Tor can invoke. This is an experimental,
12183 Linux-only feature to provide defense-in-depth against unknown
12184 attacks. To try turning it on, set "Sandbox 1" in your torrc
12185 file. Please be ready to report bugs. We hope to add support
12186 for better sandboxing in the future, including more fine-grained
12187 filters, better division of responsibility, and support for more
12188 platforms. This work has been done by Cristian-Matei Toader for
12189 Google Summer of Code.
12190 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12191 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12192 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12193 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12194 them to solve bug 6033.)
12196 o Major features (other):
12197 - Add support for passing arguments to managed pluggable transport
12198 proxies. Implements ticket 3594.
12199 - Bridges now track GeoIP information and the number of their users
12200 even when pluggable transports are in use, and report usage
12201 statistics in their extra-info descriptors. Resolves tickets 4773
12203 - Make testing Tor networks bootstrap better: lower directory fetch
12204 retry schedules and maximum interval without directory requests,
12205 and raise maximum download tries. Implements ticket 6752.
12206 - Add make target 'test-network' to run tests on a Chutney network.
12207 Implements ticket 8530.
12208 - The ntor handshake is now on-by-default, no matter what the
12209 directory authorities recommend. Implements ticket 8561.
12212 - Instead of writing destroy cells directly to outgoing connection
12213 buffers, queue them and intersperse them with other outgoing cells.
12214 This can prevent a set of resource starvation conditions where too
12215 many pending destroy cells prevent data cells from actually getting
12216 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
12217 bugfix on 0.2.0.1-alpha.
12218 - If we are unable to save a microdescriptor to the journal, do not
12219 drop it from memory and then reattempt downloading it. Fixes bug
12220 9645; bugfix on 0.2.2.6-alpha.
12221 - The new channel code sometimes lost track of in-progress circuits,
12222 causing long-running clients to stop building new circuits. The
12223 fix is to always call circuit_n_chan_done(chan, 0) from
12224 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
12227 - Tor now builds each source file in two modes: a mode that avoids
12228 exposing identifiers needlessly, and another mode that exposes
12229 more identifiers for testing. This lets the compiler do better at
12230 optimizing the production code, while enabling us to take more
12231 radical measures to let the unit tests test things.
12232 - The production builds no longer include functions used only in
12233 the unit tests; all functions exposed from a module only for
12234 unit-testing are now static in production builds.
12235 - Add an --enable-coverage configuration option to make the unit
12236 tests (and a new src/or/tor-cov target) to build with gcov test
12240 - We now have rudimentary function mocking support that our unit
12241 tests can use to test functions in isolation. Function mocking
12242 lets the tests temporarily replace a function's dependencies with
12243 stub functions, so that the tests can check the function without
12244 invoking the other functions it calls.
12245 - Add more unit tests for the <circid,channel>->circuit map, and
12246 the destroy-cell-tracking code to fix bug 7912.
12247 - Unit tests for failing cases of the TAP onion handshake.
12248 - More unit tests for address-manipulation functions.
12250 o Minor features (protecting client timestamps):
12251 - Clients no longer send timestamps in their NETINFO cells. These were
12252 not used for anything, and they provided one small way for clients
12253 to be distinguished from each other as they moved from network to
12254 network or behind NAT. Implements part of proposal 222.
12255 - Clients now round timestamps in INTRODUCE cells down to the nearest
12256 10 minutes. If a new Support022HiddenServices option is set to 0, or
12257 if it's set to "auto" and the feature is disabled in the consensus,
12258 the timestamp is sent as 0 instead. Implements part of proposal 222.
12259 - Stop sending timestamps in AUTHENTICATE cells. This is not such
12260 a big deal from a security point of view, but it achieves no actual
12261 good purpose, and isn't needed. Implements part of proposal 222.
12262 - Reduce down accuracy of timestamps in hidden service descriptors.
12263 Implements part of proposal 222.
12265 o Minor features (config options):
12266 - Config (torrc) lines now handle fingerprints which are missing
12267 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
12268 - Support a --dump-config option to print some or all of the
12269 configured options. Mainly useful for debugging the command-line
12270 option parsing code. Helps resolve ticket 4647.
12271 - Raise awareness of safer logging: notify user of potentially
12272 unsafe config options, like logging more verbosely than severity
12273 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
12274 - Add a new configuration option TestingV3AuthVotingStartOffset
12275 that bootstraps a network faster by changing the timing for
12276 consensus votes. Addresses ticket 8532.
12277 - Add a new torrc option "ServerTransportOptions" that allows
12278 bridge operators to pass configuration parameters to their
12279 pluggable transports. Resolves ticket 8929.
12280 - The config (torrc) file now accepts bandwidth and space limits in
12281 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
12282 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
12285 o Minor features (build):
12286 - Add support for `--library-versions` flag. Implements ticket 6384.
12287 - Return the "unexpected sendme" warnings to a warn severity, but make
12288 them rate limited, to help diagnose ticket 8093.
12289 - Detect a missing asciidoc, and warn the user about it, during
12290 configure rather than at build time. Fixes issue 6506. Patch from
12293 o Minor features (other):
12294 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
12295 sockets in a single system call. Implements ticket 5129.
12296 - Log current accounting state (bytes sent and received + remaining
12297 time for the current accounting period) in the relay's heartbeat
12298 message. Implements ticket 5526; patch from Peter Retzlaff.
12299 - Implement the TRANSPORT_LAUNCHED control port event that
12300 notifies controllers about new launched pluggable
12301 transports. Resolves ticket 5609.
12302 - If we're using the pure-C 32-bit curve25519_donna implementation
12303 of curve25519, build it with the -fomit-frame-pointer option to
12304 make it go faster on register-starved hosts. This improves our
12305 handshake performance by about 6% on i386 hosts without nacl.
12306 Closes ticket 8109.
12307 - Update to the September 4 2013 Maxmind GeoLite Country database.
12310 - Set the listen() backlog limit to the largest actually supported
12311 on the system, not to the value in a header file. Fixes bug 9716;
12312 bugfix on every released Tor.
12313 - No longer accept malformed http headers when parsing urls from
12314 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
12315 bugfix on 0.0.6pre1.
12316 - In munge_extrainfo_into_routerinfo(), check the return value of
12317 memchr(). This would have been a serious issue if we ever passed
12318 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
12320 - On the chance that somebody manages to build Tor on a
12321 platform where time_t is unsigned, correct the way that
12322 microdesc_add_to_cache() handles negative time arguments.
12323 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
12324 - Reject relative control socket paths and emit a warning. Previously,
12325 single-component control socket paths would be rejected, but Tor
12326 would not log why it could not validate the config. Fixes bug 9258;
12327 bugfix on 0.2.3.16-alpha.
12329 o Minor bugfixes (command line):
12330 - Use a single command-line parser for parsing torrc options on the
12331 command line and for finding special command-line options to avoid
12332 inconsistent behavior for torrc option arguments that have the same
12333 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
12335 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
12336 9573; bugfix on 0.0.9pre5.
12338 o Minor fixes (build, auxiliary programs):
12339 - Stop preprocessing the "torify" script with autoconf, since
12340 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
12342 - The tor-fw-helper program now follows the standard convention and
12343 exits with status code "0" on success. Fixes bug 9030; bugfix on
12344 0.2.3.1-alpha. Patch by Arlo Breault.
12345 - Corrected ./configure advice for what openssl dev package you should
12346 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
12348 o Minor code improvements:
12349 - Remove constants and tests for PKCS1 padding; it's insecure and
12350 shouldn't be used for anything new. Fixes bug 8792; patch
12352 - Remove instances of strcpy() from the unit tests. They weren't
12353 hurting anything, since they were only in the unit tests, but it's
12354 embarrassing to have strcpy() in the code at all, and some analysis
12355 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
12356 0.2.3.8-alpha. Patch from Arlo Breault.
12358 o Removed features:
12359 - Remove migration code from when we renamed the "cached-routers"
12360 file to "cached-descriptors" back in 0.2.0.8-alpha. This
12361 incidentally resolves ticket 6502 by cleaning up the related code
12362 a bit. Patch from Akshay Hebbar.
12364 o Code simplification and refactoring:
12365 - Extract the common duplicated code for creating a subdirectory
12366 of the data directory and writing to a file in it. Fixes ticket
12367 4282; patch from Peter Retzlaff.
12368 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
12369 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
12370 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
12371 - Add a set of accessor functions for the circuit timeout data
12372 structure. Fixes ticket 6153; patch from "piet".
12373 - Clean up exit paths from connection_listener_new(). Closes ticket
12374 8789. Patch from Arlo Breault.
12375 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
12376 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
12377 - Use a doubly-linked list to implement the global circuit list.
12378 Resolves ticket 9108. Patch from Marek Majkowski.
12379 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
12382 Changes in version 0.2.4.17-rc - 2013-09-05
12383 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
12384 series. It adds an emergency step to help us tolerate the massive
12385 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
12386 circuit-level handshakes now effectively jump the queue compared to
12387 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
12388 big bug hindering bridge reachability tests.
12391 - Relays now process the new "NTor" circuit-level handshake requests
12392 with higher priority than the old "TAP" circuit-level handshake
12393 requests. We still process some TAP requests to not totally starve
12394 0.2.3 clients when NTor becomes popular. A new consensus parameter
12395 "NumNTorsPerTAP" lets us tune the balance later if we need to.
12396 Implements ticket 9574.
12399 - If the circuit build timeout logic is disabled (via the consensus,
12400 or because we are an authority), then don't build testing circuits.
12401 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
12402 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
12403 previously they did not, which prevented them from receiving
12404 successful connections from relays for self-test or bandwidth
12405 testing. Also, when a relay is extending a circuit to a bridge,
12406 it needs to send a NETINFO cell, even when the bridge hasn't sent
12407 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
12408 - If the time to download the next old-style networkstatus is in
12409 the future, do not decline to consider whether to download the
12410 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
12414 - Avoid double-closing the listener socket in our socketpair()
12415 replacement (used on Windows) in the case where the addresses on
12416 our opened sockets don't match what we expected. Fixes bug 9400;
12417 bugfix on 0.0.2pre7. Found by Coverity.
12419 o Minor fixes (config options):
12420 - Avoid overflows when the user sets MaxCircuitDirtiness to a
12421 ridiculously high value, by imposing a (ridiculously high) 30-day
12422 maximum on MaxCircuitDirtiness.
12423 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
12424 message is logged at notice, not at info.
12425 - Warn and fail if a server is configured not to advertise any
12426 ORPorts at all. (We need *something* to put in our descriptor,
12427 or we just won't work.)
12430 - Track how many "TAP" and "NTor" circuit handshake requests we get,
12431 and how many we complete, and log it every hour to help relay
12432 operators follow trends in network load. Addresses ticket 9658.
12433 - Update to the August 7 2013 Maxmind GeoLite Country database.
12436 Changes in version 0.2.4.16-rc - 2013-08-10
12437 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
12438 series. It fixes several crash bugs in the 0.2.4 branch.
12441 - Fix a bug in the voting algorithm that could yield incorrect results
12442 when a non-naming authority declared too many flags. Fixes bug 9200;
12443 bugfix on 0.2.0.3-alpha.
12444 - Fix an uninitialized read that could in some cases lead to a remote
12445 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
12446 Anybody running a hidden service on the experimental 0.2.4.x
12447 branch should upgrade. (This is, so far as we know, unrelated to
12449 - Avoid an assertion failure when processing DNS replies without the
12450 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
12451 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
12452 0.2.4.15-rc. Found by stem integration tests.
12455 - Fix an invalid memory read that occurred when a pluggable
12456 transport proxy failed its configuration protocol.
12457 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
12458 - When evaluating whether to use a connection that we haven't
12459 decided is canonical using a recent link protocol version,
12460 decide that it's canonical only if it used address _does_
12461 match the desired address. Fixes bug 9309; bugfix on
12462 0.2.4.4-alpha. Reported by skruffy.
12463 - Make the default behavior of NumDirectoryGuards be to track
12464 NumEntryGuards. Now a user who changes only NumEntryGuards will get
12465 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
12466 - Fix a spurious compilation warning with some older versions of
12467 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
12470 - Update to the July 3 2013 Maxmind GeoLite Country database.
12473 Changes in version 0.2.4.15-rc - 2013-07-01
12474 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
12475 series. It fixes a few smaller bugs, but generally appears stable.
12476 Please test it and let us know whether it is!
12479 - When receiving a new configuration file via the control port's
12480 LOADCONF command, do not treat the defaults file as absent.
12481 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
12484 - Issue a warning when running with the bufferevents backend enabled.
12485 It's still not stable, and people should know that they're likely
12486 to hit unexpected problems. Closes ticket 9147.
12489 Changes in version 0.2.4.14-alpha - 2013-06-18
12490 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
12491 present in 0.2.4.13-alpha.
12494 - When we have too much memory queued in circuits (according to a new
12495 MaxMemInCellQueues option), close the circuits consuming the most
12496 memory. This prevents us from running out of memory as a relay if
12497 circuits fill up faster than they can be drained. Fixes bug 9063;
12498 bugfix on the 54th commit of Tor. This bug is a further fix beyond
12499 bug 6252, whose fix was merged into 0.2.3.21-rc.
12501 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
12502 where we tried to solve this issue simply by imposing an upper limit
12503 on the number of queued cells for a single circuit. That approach
12504 proved to be problematic, since there are ways to provoke clients to
12505 send a number of cells in excess of any such reasonable limit. Fixes
12506 bug 9072; bugfix on 0.2.4.13-alpha.
12508 - Limit hidden service descriptors to at most ten introduction
12509 points, to slow one kind of guard enumeration. Fixes bug 9002;
12510 bugfix on 0.1.1.11-alpha.
12513 Changes in version 0.2.4.13-alpha - 2013-06-14
12514 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
12515 vulnerabilities, makes socks5 username/password circuit isolation
12516 actually actually work (this time for sure!), and cleans up a bunch
12517 of other issues in preparation for a release candidate.
12519 o Major bugfixes (robustness):
12520 - Close any circuit that has too many cells queued on it. Fixes
12521 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
12522 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
12523 - Prevent the get_freelists() function from running off the end of
12524 the list of freelists if it somehow gets an unrecognized
12525 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
12527 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
12528 when an exit connection with optimistic data succeeds immediately
12529 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
12531 - Fix a directory authority crash bug when building a consensus
12532 using an older consensus as its basis. Fixes bug 8833. Bugfix
12536 - Avoid a memory leak where we would leak a consensus body when we
12537 find that a consensus which we couldn't previously verify due to
12538 missing certificates is now verifiable. Fixes bug 8719; bugfix
12540 - We used to always request authority certificates by identity digest,
12541 meaning we'd get the newest one even when we wanted one with a
12542 different signing key. Then we would complain about being given
12543 a certificate we already had, and never get the one we really
12544 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
12545 resource to request the one we want. Fixes bug 5595; bugfix on
12547 - Follow the socks5 protocol when offering username/password
12548 authentication. The fix for bug 8117 exposed this bug, and it
12549 turns out real-world applications like Pidgin do care. Bugfix on
12550 0.2.3.2-alpha; fixes bug 8879.
12551 - Prevent failures on Windows Vista and later when rebuilding the
12552 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
12553 bugfix on 0.2.4.12-alpha.
12556 - Fix an impossible buffer overrun in the AES unit tests. Fixes
12557 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
12558 - If for some reason we fail to write a microdescriptor while
12559 rebuilding the cache, do not let the annotations from that
12560 microdescriptor linger in the cache file, and do not let the
12561 microdescriptor stay recorded as present in its old location.
12562 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
12563 - Fix a memory leak that would occur whenever a configuration
12564 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
12565 - Paste the description for PathBias parameters from the man
12566 page into or.h, so the code documents them too. Fixes bug 7982;
12567 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
12568 - Relays now treat a changed IPv6 ORPort as sufficient reason to
12569 publish an updated descriptor. Fixes bug 6026; bugfix on
12571 - When launching a resolve request on behalf of an AF_UNIX control
12572 socket, omit the address field of the new entry connection, used in
12573 subsequent controller events, rather than letting tor_dup_addr()
12574 set it to "<unknown address type>". Fixes bug 8639; bugfix on
12577 o Minor bugfixes (log messages):
12578 - Fix a scaling issue in the path bias accounting code that
12579 resulted in "Bug:" log messages from either
12580 pathbias_scale_close_rates() or pathbias_count_build_success().
12581 This represents a bugfix on a previous bugfix: the original fix
12582 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
12584 - Give a less useless error message when the user asks for an IPv4
12585 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
12589 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
12590 to tolerate bug 8093 for now.
12591 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
12592 in directory authority votes to describe whether they have enough
12593 measured bandwidths to ignore advertised (relay descriptor)
12594 bandwidth claims. Resolves ticket 8711.
12595 - Update to the June 5 2013 Maxmind GeoLite Country database.
12597 o Removed documentation:
12598 - Remove some of the older contents of doc/ as obsolete; move others
12599 to torspec.git. Fixes bug 8965.
12601 o Code simplification and refactoring:
12602 - Avoid using character buffers when constructing most directory
12603 objects: this approach was unwieldy and error-prone. Instead,
12604 build smartlists of strings, and concatenate them when done.
12607 Changes in version 0.2.4.12-alpha - 2013-04-18
12608 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
12609 process for lengthening the guard rotation period, makes directory
12610 authority opinions in the consensus a bit less gameable, makes socks5
12611 username/password circuit isolation actually work, and fixes a wide
12612 variety of other issues.
12615 - Raise the default time that a client keeps an entry guard from
12616 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
12617 2012 paper. (We would make it even longer, but we need better client
12618 load balancing first.) Also, make the guard lifetime controllable
12619 via a new GuardLifetime torrc option and a GuardLifetime consensus
12620 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
12621 - Directory authorities now prefer using measured bandwidths to
12622 advertised ones when computing flags and thresholds. Resolves
12624 - Directory authorities that have more than a threshold number
12625 of relays with measured bandwidths now treat relays with unmeasured
12626 bandwidths as having bandwidth 0. Resolves ticket 8435.
12628 o Major bugfixes (assert / resource use):
12629 - Avoid a bug where our response to TLS renegotiation under certain
12630 network conditions could lead to a busy-loop, with 100% CPU
12631 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
12632 - Avoid an assertion when we discover that we'd like to write a cell
12633 onto a closing connection: just discard the cell. Fixes another
12634 case of bug 7350; bugfix on 0.2.4.4-alpha.
12636 o Major bugfixes (client-side privacy):
12637 - When we mark a circuit as unusable for new circuits, have it
12638 continue to be unusable for new circuits even if MaxCircuitDirtiness
12639 is increased too much at the wrong time, or the system clock jumps
12640 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
12641 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
12642 which have resolved to internal addresses") is set, apply that
12643 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
12644 - When an exit relay rejects a stream with reason "exit policy", but
12645 we only know an exit policy summary (e.g. from the microdesc
12646 consensus) for it, do not mark the relay as useless for all exiting.
12647 Instead, mark just the circuit as unsuitable for that particular
12648 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
12649 - Allow applications to get proper stream isolation with
12650 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
12651 username/password authentication also offer "no authentication". Tor
12652 had previously preferred "no authentication", so the applications
12653 never actually sent Tor their auth details. Now Tor selects
12654 username/password authentication if it's offered. You can disable
12655 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
12656 bug 8117; bugfix on 0.2.3.3-alpha.
12658 o Major bugfixes (other):
12659 - When unable to find any working directory nodes to use as a
12660 directory guard, give up rather than adding the same non-working
12661 nodes to the directory guard list over and over. Fixes bug 8231;
12662 bugfix on 0.2.4.8-alpha.
12665 - Reject as invalid most directory objects containing a NUL.
12666 Belt-and-suspender fix for bug 8037.
12667 - In our testsuite, create temporary directories with a bit more
12668 entropy in their name to make name collisions less likely. Fixes
12670 - Add CACHED keyword to ADDRMAP events in the control protocol
12671 to indicate whether a DNS result will be cached or not. Resolves
12673 - Update to the April 3 2013 Maxmind GeoLite Country database.
12675 o Minor features (build):
12676 - Detect and reject attempts to build Tor with threading support
12677 when OpenSSL has been compiled without threading support.
12679 - Clarify that when autoconf is checking for nacl, it is checking
12680 specifically for nacl with a fast curve25519 implementation.
12682 - Warn if building on a platform with an unsigned time_t: there
12683 are too many places where Tor currently assumes that time_t can
12684 hold negative values. We'd like to fix them all, but probably
12687 o Minor bugfixes (build):
12688 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
12689 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
12690 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
12691 - Add the old src/or/micro-revision.i filename to CLEANFILES.
12692 On the off chance that somebody has one, it will go away as soon
12693 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
12694 - Build Tor correctly on 32-bit platforms where the compiler can build
12695 but not run code using the "uint128_t" construction. Fixes bug 8587;
12696 bugfix on 0.2.4.8-alpha.
12697 - Fix compilation warning with some versions of clang that would
12698 prefer the -Wswitch-enum compiler flag to warn about switch
12699 statements with missing enum values, even if those switch
12700 statements have a "default:" statement. Fixes bug 8598; bugfix
12703 o Minor bugfixes (protocol):
12704 - Fix the handling of a TRUNCATE cell when it arrives while the
12705 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
12706 - Fix a misframing issue when reading the version numbers in a
12707 VERSIONS cell. Previously we would recognize [00 01 00 02] as
12708 'version 1, version 2, and version 0x100', when it should have
12709 only included versions 1 and 2. Fixes bug 8059; bugfix on
12710 0.2.0.10-alpha. Reported pseudonymously.
12711 - Make the format and order of STREAM events for DNS lookups
12712 consistent among the various ways to launch DNS lookups. Fixes
12713 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
12714 - Correct our check for which versions of Tor support the EXTEND2
12715 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
12716 later, when support was really added in version 0.2.4.8-alpha.
12717 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
12719 o Minor bugfixes (other):
12720 - Correctly store microdescriptors and extrainfo descriptors with
12721 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
12722 Bug reported by "cypherpunks".
12723 - Increase the width of the field used to remember a connection's
12724 link protocol version to two bytes. Harmless for now, since the
12725 only currently recognized versions are one byte long. Reported
12726 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
12727 - If the state file's path bias counts are invalid (presumably from a
12728 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
12729 additional checks and log messages to the scaling of Path Bias
12730 counts, in case there still are remaining issues with scaling.
12731 Should help resolve bug 8235.
12732 - Eliminate several instances where we use "Nickname=ID" to refer to
12733 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
12734 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
12735 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
12737 o Minor bugfixes (syscalls):
12738 - Always check the return values of functions fcntl() and
12739 setsockopt(). We don't believe these are ever actually failing in
12740 practice, but better safe than sorry. Also, checking these return
12741 values should please analysis tools like Coverity. Patch from
12742 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
12743 - Use direct writes rather than stdio when building microdescriptor
12744 caches, in an attempt to mitigate bug 8031, or at least make it
12747 o Minor bugfixes (config):
12748 - When rejecting a configuration because we were unable to parse a
12749 quoted string, log an actual error message. Fixes bug 7950; bugfix
12751 - Behave correctly when the user disables LearnCircuitBuildTimeout
12752 but doesn't tell us what they would like the timeout to be. Fixes
12753 bug 6304; bugfix on 0.2.2.14-alpha.
12754 - When autodetecting the number of CPUs, use the number of available
12755 CPUs in preference to the number of configured CPUs. Inform the
12756 user if this reduces the number of available CPUs. Fixes bug 8002;
12757 bugfix on 0.2.3.1-alpha.
12758 - Make it an error when you set EntryNodes but disable UseGuardNodes,
12759 since it will (surprisingly to some users) ignore EntryNodes. Fixes
12760 bug 8180; bugfix on 0.2.3.11-alpha.
12761 - Allow TestingTorNetworks to override the 4096-byte minimum for
12762 the Fast threshold. Otherwise they can't bootstrap until they've
12763 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
12764 - Fix some logic errors when the user manually overrides the
12765 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
12768 o Minor bugfixes (log messages to help diagnose bugs):
12769 - If we fail to free a microdescriptor because of bug 7164, log
12770 the filename and line number from which we tried to free it.
12771 - Add another diagnostic to the heartbeat message: track and log
12772 overhead that TLS is adding to the data we write. If this is
12773 high, we are sending too little data to SSL_write at a time.
12774 Diagnostic for bug 7707.
12775 - Add more detail to a log message about relaxed timeouts, to help
12777 - Warn more aggressively when flushing microdescriptors to a
12778 microdescriptor cache fails, in an attempt to mitigate bug 8031,
12779 or at least make it more diagnosable.
12780 - Improve debugging output to help track down bug 8185 ("Bug:
12781 outgoing relay cell has n_chan==NULL. Dropping.")
12782 - Log the purpose of a path-bias testing circuit correctly.
12783 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
12785 o Minor bugfixes (0.2.4.x log messages that were too noisy):
12786 - Don't attempt to relax the timeout of already opened 1-hop circuits.
12787 They might never timeout. This should eliminate some/all cases of
12788 the relaxed timeout log message.
12789 - Use circuit creation time for network liveness evaluation. This
12790 should eliminate warning log messages about liveness caused
12791 by changes in timeout evaluation. Fixes bug 6572; bugfix on
12793 - Reduce a path bias length check from notice to info. The message
12794 is triggered when creating controller circuits. Fixes bug 8196;
12795 bugfix on 0.2.4.8-alpha.
12796 - Fix a path state issue that triggered a notice during relay startup.
12797 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
12798 - Reduce occurrences of warns about circuit purpose in
12799 connection_ap_expire_building(). Fixes bug 8477; bugfix on
12802 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
12803 - If we encounter a write failure on a SOCKS connection before we
12804 finish our SOCKS handshake, don't warn that we closed the
12805 connection before we could send a SOCKS reply. Fixes bug 8427;
12806 bugfix on 0.1.0.1-rc.
12807 - Correctly recognize that [::1] is a loopback address. Fixes
12808 bug 8377; bugfix on 0.2.1.3-alpha.
12809 - Fix a directory authority warn caused when we have a large amount
12810 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
12811 - Don't log inappropriate heartbeat messages when hibernating: a
12812 hibernating node is _expected_ to drop out of the consensus,
12813 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
12814 bugfix on 0.2.3.1-alpha.
12815 - Don't complain about bootstrapping problems while hibernating.
12816 These complaints reflect a general code problem, but not one
12817 with any problematic effects (no connections are actually
12818 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
12820 o Documentation fixes:
12821 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
12822 names match. Fixes bug 7768.
12823 - Make the torify manpage no longer refer to tsocks; torify hasn't
12824 supported tsocks since 0.2.3.14-alpha.
12825 - Make the tor manpage no longer reference tsocks.
12826 - Fix the GeoIPExcludeUnknown documentation to refer to
12827 ExcludeExitNodes rather than the currently nonexistent
12828 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
12831 - The tor-tsocks.conf is no longer distributed or installed. We
12832 recommend that tsocks users use torsocks instead. Resolves
12836 Changes in version 0.2.4.11-alpha - 2013-03-11
12837 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
12838 more robust, makes hidden service authentication work again, and
12839 resolves a DPI fingerprint for Tor's SSL transport.
12841 o Major features (directory authorities):
12842 - Directory authorities now support a new consensus method (17)
12843 where they cap the published bandwidth of servers for which
12844 insufficient bandwidth measurements exist. Fixes part of bug 2286.
12845 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
12846 serve any v2 directory information. Now we can test disabling the
12847 old deprecated v2 directory format, and see whether doing so has
12848 any effect on network load. Begins to fix bug 6783.
12849 - Directory authorities now include inside each vote a statement of
12850 the performance thresholds they used when assigning flags.
12851 Implements ticket 8151.
12853 o Major bugfixes (directory authorities):
12854 - Stop marking every relay as having been down for one hour every
12855 time we restart a directory authority. These artificial downtimes
12856 were messing with our Stable and Guard flag calculations. Fixes
12857 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
12859 o Major bugfixes (hidden services):
12860 - Allow hidden service authentication to succeed again. When we
12861 refactored the hidden service introduction code back
12862 in 0.2.4.1-alpha, we didn't update the code that checks
12863 whether authentication information is present, causing all
12864 authentication checks to return "false". Fix for bug 8207; bugfix
12865 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
12867 o Minor features (relays, bridges):
12868 - Make bridge relays check once a minute for whether their IP
12869 address has changed, rather than only every 15 minutes. Resolves
12870 bugs 1913 and 1992.
12871 - Refactor resolve_my_address() so it returns the method by which we
12872 decided our public IP address (explicitly configured, resolved from
12873 explicit hostname, guessed from interfaces, learned by gethostname).
12874 Now we can provide more helpful log messages when a relay guesses
12875 its IP address incorrectly (e.g. due to unexpected lines in
12876 /etc/hosts). Resolves ticket 2267.
12877 - Teach bridge-using clients to avoid 0.2.2 bridges when making
12878 microdescriptor-related dir requests, and only fall back to normal
12879 descriptors if none of their bridges can handle microdescriptors
12880 (as opposed to the fix in ticket 4013, which caused them to fall
12881 back to normal descriptors if *any* of their bridges preferred
12882 them). Resolves ticket 4994.
12883 - Randomize the lifetime of our SSL link certificate, so censors can't
12884 use the static value for filtering Tor flows. Resolves ticket 8443;
12885 related to ticket 4014 which was included in 0.2.2.33.
12886 - Support a new version of the link protocol that allows 4-byte circuit
12887 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
12888 a possible resource exhaustion issue. Closes ticket 7351; implements
12891 o Minor features (portability):
12892 - Tweak the curve25519-donna*.c implementations to tolerate systems
12893 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
12894 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
12895 the signs of types during autoconf. This is better than our old
12896 approach, which didn't work when cross-compiling.
12897 - Detect the sign of enum values, rather than assuming that MSC is the
12898 only compiler where enum types are all signed. Fixes bug 7727;
12899 bugfix on 0.2.4.10-alpha.
12901 o Minor features (other):
12902 - Say "KBytes" rather than "KB" in the man page (for various values
12903 of K), to further reduce confusion about whether Tor counts in
12904 units of memory or fractions of units of memory. Resolves ticket 7054.
12905 - Clear the high bit on curve25519 public keys before passing them to
12906 our backend, in case we ever wind up using a backend that doesn't do
12907 so itself. If we used such a backend, and *didn't* clear the high bit,
12908 we could wind up in a situation where users with such backends would
12909 be distinguishable from users without. Fixes bug 8121; bugfix on
12911 - Update to the March 6 2013 Maxmind GeoLite Country database.
12913 o Minor bugfixes (clients):
12914 - When we receive a RELAY_END cell with the reason DONE, or with no
12915 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
12916 status as "connection refused". Previously we reported these cases
12917 as success but then immediately closed the connection. Fixes bug
12918 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
12919 - Downgrade an assertion in connection_ap_expire_beginning to an
12920 LD_BUG message. The fix for bug 8024 should prevent this message
12921 from displaying, but just in case, a warn that we can diagnose
12922 is better than more assert crashes. Fixes bug 8065; bugfix on
12924 - Lower path use bias thresholds to .80 for notice and .60 for warn.
12925 Also make the rate limiting flags for the path use bias log messages
12926 independent from the original path bias flags. Fixes bug 8161;
12927 bugfix on 0.2.4.10-alpha.
12929 o Minor bugfixes (relays):
12930 - Stop trying to resolve our hostname so often (e.g. every time we
12931 think about doing a directory fetch). Now we reuse the cached
12932 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
12933 and 2410 (bugfix on 0.1.2.2-alpha).
12934 - Stop sending a stray "(null)" in some cases for the server status
12935 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
12937 - When choosing which stream on a formerly stalled circuit to wake
12938 first, make better use of the platform's weak RNG. Previously,
12939 we had been using the % ("modulo") operator to try to generate a
12940 1/N chance of picking each stream, but this behaves badly with
12941 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
12943 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
12944 Irix's random() only return 15 bits; Solaris's random() returns more
12945 bits but its RAND_MAX says it only returns 15, and so on. Motivated
12946 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
12948 o Minor bugfixes (directory authorities):
12949 - Directory authorities now use less space when formatting identical
12950 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
12953 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
12954 - Avoid leaking memory if we fail to compute a consensus signature
12955 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
12956 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
12958 - Fix a memory leak during safe-cookie controller authentication.
12959 Bugfix on 0.2.3.13-alpha.
12960 - Avoid memory leak of IPv6 policy content if we fail to format it into
12961 a router descriptor. Bugfix on 0.2.4.7-alpha.
12963 o Minor bugfixes (other code correctness issues):
12964 - Avoid a crash if we fail to generate an extrainfo descriptor.
12965 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
12966 this is CID 718634.
12967 - When detecting the largest possible file descriptor (in order to
12968 close all file descriptors when launching a new program), actually
12969 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
12970 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
12972 - Fix a copy-and-paste error when adding a missing A1 to a routerset
12973 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
12974 Bugfix on 0.2.4.10-alpha.
12975 - Fix an impossible-to-trigger integer overflow when estimating how
12976 long our onionskin queue would take. (This overflow would require us
12977 to accept 4 million onionskins before processing 100 of them.) Fixes
12978 bug 8210; bugfix on 0.2.4.10-alpha.
12980 o Code simplification and refactoring:
12981 - Add a wrapper function for the common "log a message with a
12985 Changes in version 0.2.4.10-alpha - 2013-02-04
12986 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
12987 certain attacks that flood the network with relays; changes the queue
12988 for circuit create requests from a sized-based limit to a time-based
12989 limit; resumes building with MSVC on Windows; and fixes a wide variety
12992 o Major bugfixes (directory authority):
12993 - When computing directory thresholds, ignore any rejected-as-sybil
12994 nodes during the computation so that they can't influence Fast,
12995 Guard, etc. (We should have done this for proposal 109.) Fixes
12997 - When marking a node as a likely sybil, reset its uptime metrics
12998 to zero, so that it cannot time towards getting marked as Guard,
12999 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
13003 - When a TLS write is partially successful but incomplete, remember
13004 that the flushed part has been flushed, and notice that bytes were
13005 actually written. Reported and fixed pseudonymously. Fixes bug
13006 7708; bugfix on Tor 0.1.0.5-rc.
13007 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
13008 ID: these could be used to create unexpected streams and circuits
13009 which would count as "present" to some parts of Tor but "absent"
13010 to others, leading to zombie circuits and streams or to a bandwidth
13011 denial-of-service. Fixes bug 7889; bugfix on every released version
13012 of Tor. Reported by "oftc_must_be_destroyed".
13013 - Rename all macros in our local copy of queue.h to begin with "TOR_".
13014 This change seems the only good way to permanently prevent conflicts
13015 with queue.h on various operating systems. Fixes bug 8107; bugfix
13018 o Major features (relay):
13019 - Instead of limiting the number of queued onionskins (aka circuit
13020 create requests) to a fixed, hard-to-configure number, we limit
13021 the size of the queue based on how many we expect to be able to
13022 process in a given amount of time. We estimate the time it will
13023 take to process an onionskin based on average processing time
13024 of previous onionskins. Closes ticket 7291. You'll never have to
13025 configure MaxOnionsPending again.
13027 o Major features (portability):
13028 - Resume building correctly with MSVC and Makefile.nmake. This patch
13029 resolves numerous bugs and fixes reported by ultramage, including
13030 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
13031 - Make the ntor and curve25519 code build correctly with MSVC.
13032 Fix on 0.2.4.8-alpha.
13035 - When directory authorities are computing thresholds for flags,
13036 never let the threshold for the Fast flag fall below 4096
13037 bytes. Also, do not consider nodes with extremely low bandwidths
13038 when deciding thresholds for various directory flags. This change
13039 should raise our threshold for Fast relays, possibly in turn
13040 improving overall network performance; see ticket 1854. Resolves
13042 - The Tor client now ignores sub-domain components of a .onion
13043 address. This change makes HTTP "virtual" hosting
13044 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
13045 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
13046 hosted on the same hidden service. Implements proposal 204.
13047 - We compute the overhead from passing onionskins back and forth to
13048 cpuworkers, and report it when dumping statistics in response to
13049 SIGUSR1. Supports ticket 7291.
13051 o Minor features (path selection):
13052 - When deciding whether we have enough descriptors to build circuits,
13053 instead of looking at raw relay counts, look at which fraction
13054 of (bandwidth-weighted) paths we're able to build. This approach
13055 keeps clients from building circuits if their paths are likely to
13056 stand out statistically. The default fraction of paths needed is
13057 taken from the consensus directory; you can override it with the
13058 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
13059 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
13060 and we have GeoIP information, also exclude all nodes with unknown
13061 countries "??" and "A1". This behavior is controlled by the
13062 new GeoIPExcludeUnknown option: you can make such nodes always
13063 excluded with "GeoIPExcludeUnknown 1", and disable the feature
13064 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
13065 gets you the default behavior. Implements feature 7706.
13066 - Path Use Bias: Perform separate accounting for successful circuit
13067 use. Keep separate statistics on stream attempt rates versus stream
13068 success rates for each guard. Provide configurable thresholds to
13069 determine when to emit log messages or disable use of guards that
13070 fail too many stream attempts. Resolves ticket 7802.
13072 o Minor features (log messages):
13073 - When learning a fingerprint for a bridge, log its corresponding
13074 transport type. Implements ticket 7896.
13075 - Improve the log message when "Bug/attack: unexpected sendme cell
13076 from client" occurs, to help us track bug 8093.
13079 - Remove a couple of extraneous semicolons that were upsetting the
13080 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
13081 bugfix on 0.2.2.1-alpha.
13082 - Remove a source of rounding error during path bias count scaling;
13083 don't count cannibalized circuits as used for path bias until we
13084 actually try to use them; and fix a circuit_package_relay_cell()
13085 warning message about n_chan==NULL. Fixes bug 7802.
13086 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
13087 actually link against nacl when we're configured to use it. Fixes
13088 bug 7972; bugfix on 0.2.4.8-alpha.
13089 - Compile correctly with the --disable-curve25519 option. Fixes
13090 bug 8153; bugfix on 0.2.4.8-alpha.
13092 o Build improvements:
13093 - Do not report status verbosely from autogen.sh unless the -v flag
13094 is specified. Fixes issue 4664. Patch from Onizuka.
13095 - Replace all calls to snprintf() outside of src/ext with
13096 tor_snprintf(). Also remove the #define to replace snprintf with
13097 _snprintf on Windows; they have different semantics, and all of
13098 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
13099 - Try to detect if we are ever building on a platform where
13100 memset(...,0,...) does not set the value of a double to 0.0. Such
13101 platforms are permitted by the C standard, though in practice
13102 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
13103 currently support them, but it's better to detect them and fail
13104 than to perform erroneously.
13106 o Removed features:
13107 - Stop exporting estimates of v2 and v3 directory traffic shares
13108 in extrainfo documents. They were unneeded and sometimes inaccurate.
13109 Also stop exporting any v2 directory request statistics. Resolves
13111 - Drop support for detecting and warning about versions of Libevent
13112 before 1.3e. Nothing reasonable ships with them any longer;
13113 warning the user about them shouldn't be needed. Resolves ticket
13116 o Code simplifications and refactoring:
13117 - Rename "isin" functions to "contains", for grammar. Resolves
13119 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
13120 with the natural logarithm function from the system libm. Resolves
13124 Changes in version 0.2.4.9-alpha - 2013-01-15
13125 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
13126 work more robustly.
13129 - Fix backward compatibility logic when receiving an embedded ntor
13130 handshake tunneled in a CREATE cell. This clears up the "Bug:
13131 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
13135 Changes in version 0.2.4.8-alpha - 2013-01-14
13136 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
13137 risks, adds a new stronger and faster circuit handshake, and offers
13138 stronger and faster link encryption when both sides support it.
13141 - Preliminary support for directory guards (proposal 207): when
13142 possible, clients now use their entry guards for non-anonymous
13143 directory requests. This can help prevent client enumeration. Note
13144 that this behavior only works when we have a usable consensus
13145 directory, and when options about what to download are more or less
13146 standard. In the future we should re-bootstrap from our guards,
13147 rather than re-bootstrapping from the preconfigured list of
13148 directory sources that ships with Tor. Resolves ticket 6526.
13149 - Tor relays and clients now support a better CREATE/EXTEND cell
13150 format, allowing the sender to specify multiple address, identity,
13151 and handshake types. Implements Robert Ransom's proposal 200;
13152 closes ticket 7199.
13154 o Major features (new circuit handshake):
13155 - Tor now supports a new circuit extension handshake designed by Ian
13156 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
13157 circuit extension handshake, later called "TAP", was a bit slow
13158 (especially on the relay side), had a fragile security proof, and
13159 used weaker keys than we'd now prefer. The new circuit handshake
13160 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
13161 function, making it significantly more secure than the older
13162 handshake, and significantly faster. Tor can use one of two built-in
13163 pure-C curve25519-donna implementations by Adam Langley, or it
13164 can link against the "nacl" library for a tuned version if present.
13166 The built-in version is very fast for 64-bit systems when building
13167 with GCC. The built-in 32-bit version is still faster than the
13168 old TAP protocol, but using libnacl is better on most such hosts.
13170 Clients don't currently use this protocol by default, since
13171 comparatively few clients support it so far. To try it, set
13172 UseNTorHandshake to 1.
13174 Implements proposal 216; closes ticket 7202.
13176 o Major features (better link encryption):
13177 - Relays can now enable the ECDHE TLS ciphersuites when available
13178 and appropriate. These ciphersuites let us negotiate forward-secure
13179 TLS secret keys more safely and more efficiently than with our
13180 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
13181 public relays prefer the (faster) P224 group, and bridges prefer
13182 the (more common) P256 group; you can override this with the
13185 Enabling these ciphers was a little tricky, since for a long time,
13186 clients had been claiming to support them without actually doing
13187 so, in order to foil fingerprinting. But with the client-side
13188 implementation of proposal 198 in 0.2.3.17-beta, clients can now
13189 match the ciphers from recent Firefox versions *and* list the
13190 ciphers they actually mean, so relays can believe such clients
13191 when they advertise ECDHE support in their TLS ClientHello messages.
13193 This feature requires clients running 0.2.3.17-beta or later,
13194 and requires both sides to be running OpenSSL 1.0.0 or later
13195 with ECC support. OpenSSL 1.0.1, with the compile-time option
13196 "enable-ec_nistp_64_gcc_128", is highly recommended.
13198 Implements the relay side of proposal 198; closes ticket 7200.
13201 - Avoid crashing when, as a relay without IPv6-exit support, a
13202 client insists on getting an IPv6 address or nothing. Fixes bug
13203 7814; bugfix on 0.2.4.7-alpha.
13206 - Improve circuit build timeout handling for hidden services.
13207 In particular: adjust build timeouts more accurately depending
13208 upon the number of hop-RTTs that a particular circuit type
13209 undergoes. Additionally, launch intro circuits in parallel
13210 if they timeout, and take the first one to reply as valid.
13211 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
13212 separate error codes; or at least, don't break for that reason.
13213 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
13214 - Update to the January 2 2013 Maxmind GeoLite Country database.
13216 o Minor features (testing):
13217 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
13218 (P-256) Diffie-Hellman handshakes to src/or/bench.
13219 - Add benchmark functions to test onion handshake performance.
13221 o Minor features (path bias detection):
13222 - Alter the Path Bias log messages to be more descriptive in terms
13223 of reporting timeouts and other statistics.
13224 - Create three levels of Path Bias log messages, as opposed to just
13225 two. These are configurable via consensus as well as via the torrc
13226 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
13227 The default values are 0.70, 0.50, and 0.30 respectively.
13228 - Separate the log message levels from the decision to drop guards,
13229 which also is available via torrc option PathBiasDropGuards.
13230 PathBiasDropGuards still defaults to 0 (off).
13231 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
13232 in combination with PathBiasExtremeRate.
13233 - Increase the default values for PathBiasScaleThreshold and
13234 PathBiasCircThreshold from (200, 20) to (300, 150).
13235 - Add in circuit usage accounting to path bias. If we try to use a
13236 built circuit but fail for any reason, it counts as path bias.
13237 Certain classes of circuits where the adversary gets to pick your
13238 destination node are exempt from this accounting. Usage accounting
13239 can be specifically disabled via consensus parameter or torrc.
13240 - Convert all internal path bias state to double-precision floating
13241 point, to avoid roundoff error and other issues.
13242 - Only record path bias information for circuits that have completed
13243 *two* hops. Assuming end-to-end tagging is the attack vector, this
13244 makes us more resilient to ambient circuit failure without any
13245 detection capability loss.
13247 o Minor bugfixes (log messages):
13248 - Rate-limit the "No circuits are opened. Relaxed timeout for a
13249 circuit with channel state open..." message to once per hour to
13250 keep it from filling the notice logs. Mitigates bug 7799 but does
13251 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
13252 - Avoid spurious warnings when configuring multiple client ports of
13253 which only some are nonlocal. Previously, we had claimed that some
13254 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
13257 o Code simplifications and refactoring:
13258 - Get rid of a couple of harmless clang warnings, where we compared
13259 enums to ints. These warnings are newly introduced in clang 3.2.
13260 - Split the onion.c file into separate modules for the onion queue
13261 and the different handshakes it supports.
13262 - Remove the marshalling/unmarshalling code for sending requests to
13263 cpuworkers over a socket, and instead just send structs. The
13264 recipient will always be the same Tor binary as the sender, so
13265 any encoding is overkill.
13268 Changes in version 0.2.4.7-alpha - 2012-12-24
13269 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
13270 directory mirrors for more robust bootstrapping; fixes more issues where
13271 clients with changing network conditions refuse to make any circuits;
13272 adds initial support for exiting to IPv6 addresses; resumes being able
13273 to update our GeoIP database, and includes the geoip6 file this time;
13274 turns off the client-side DNS cache by default due to privacy risks;
13275 and fixes a variety of other issues.
13277 o Major features (client resilience):
13278 - Add a new "FallbackDir" torrc option to use when we can't use
13279 a directory mirror from the consensus (either because we lack a
13280 consensus, or because they're all down). Currently, all authorities
13281 are fallbacks by default, and there are no other default fallbacks,
13282 but that will change. This option will allow us to give clients a
13283 longer list of servers to try to get a consensus from when first
13284 connecting to the Tor network, and thereby reduce load on the
13285 directory authorities. Implements proposal 206, "Preconfigured
13286 directory sources for bootstrapping". We also removed the old
13287 "FallbackNetworkstatus" option, since we never got it working well
13288 enough to use it. Closes bug 572.
13289 - If we have no circuits open, use a relaxed timeout (the
13290 95-percentile cutoff) until a circuit succeeds. This heuristic
13291 should allow Tor to succeed at building circuits even when the
13292 network connection drastically changes. Should help with bug 3443.
13294 o Major features (IPv6):
13295 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
13296 connectivity, then set the IPv6Exit flag to 1. Also make sure your
13297 exit policy reads as you would like: the address * applies to all
13298 address families, whereas *4 is IPv4 address only, and *6 is IPv6
13299 addresses only. On the client side, you'll need to wait until the
13300 authorities have upgraded, wait for enough exits to support IPv6,
13301 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
13302 ticket 5547, implements proposal 117 as revised in proposal 208.
13304 We DO NOT recommend that clients with actual anonymity needs start
13305 using IPv6 over Tor yet, since not enough exits support it yet.
13307 o Major features (geoip database):
13308 - Maxmind began labelling Tor relays as being in country "A1",
13309 which breaks by-country node selection inside Tor. Now we use a
13310 script to replace "A1" ("Anonymous Proxy") entries in our geoip
13311 file with real country codes. This script fixes about 90% of "A1"
13312 entries automatically and uses manual country code assignments to
13313 fix the remaining 10%. See src/config/README.geoip for details.
13314 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
13315 Country database, as modified above.
13317 o Major bugfixes (client-side DNS):
13318 - Turn off the client-side DNS cache by default. Updating and using
13319 the DNS cache is now configurable on a per-client-port
13320 level. SOCKSPort, DNSPort, etc lines may now contain
13321 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
13322 cache these types of DNS answers when we receive them from an
13323 exit node in response to an application request on this port, and
13324 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
13325 cached DNS answers of these types, we shouldn't use them. It's
13326 potentially risky to use cached DNS answers at the client, since
13327 doing so can indicate to one exit what answers we've gotten
13328 for DNS lookups in the past. With IPv6, this becomes especially
13329 problematic. Using cached DNS answers for requests on the same
13330 circuit would present less linkability risk, since all traffic
13331 on a circuit is already linkable, but it would also provide
13332 little performance benefit: the exit node caches DNS replies
13333 too. Implements a simplified version of Proposal 205. Implements
13336 o Major bugfixes (other):
13337 - Alter circuit build timeout measurement to start at the point
13338 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
13339 initialization). This should make our timeout measurements more
13340 uniform. Previously, we were sometimes including ORconn setup time
13341 in our circuit build time measurements. Should resolve bug 3443.
13342 - Fix an assertion that could trigger in hibernate_go_dormant() when
13343 closing an or_connection_t: call channel_mark_for_close() rather
13344 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
13346 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
13347 7655; bugfix on 0.2.4.6-alpha.
13350 - Add a new torrc option "ServerTransportListenAddr" to let bridge
13351 operators select the address where their pluggable transports will
13352 listen for connections. Resolves ticket 7013.
13353 - Allow an optional $ before the node identity digest in the
13354 controller command GETINFO ns/id/<identity>, for consistency with
13355 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
13356 - Log packaged cell fullness as part of the heartbeat message.
13357 Diagnosis to try to determine the extent of bug 7743.
13359 o Minor features (IPv6):
13360 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
13361 prefer to hand out virtual IPv6 addresses, since there are more of
13362 them and we can't run out. To override this behavior and make IPv4
13363 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
13364 or DNSPort you're using for resolving. Implements ticket 7571.
13365 - AutomapHostsOnResolve responses are now randomized, to avoid
13366 annoying situations where Tor is restarted and applications
13367 connect to the wrong addresses.
13368 - Never try more than 1000 times to pick a new virtual address when
13369 AutomapHostsOnResolve is set. That's good enough so long as we
13370 aren't close to handing out our entire virtual address space;
13371 if you're getting there, it's best to switch to IPv6 virtual
13375 - The ADDRMAP command can no longer generate an ill-formed error
13376 code on a failed MAPADDRESS. It now says "internal" rather than
13377 an English sentence fragment with spaces in the middle. Bugfix on
13378 Tor 0.2.0.19-alpha.
13379 - Fix log messages and comments to avoid saying "GMT" when we mean
13380 "UTC". Fixes bug 6113.
13381 - Compile on win64 using mingw64. Fixes bug 7260; patches from
13383 - Fix a crash when debugging unit tests on Windows: deallocate a
13384 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
13385 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
13388 - The DirServer option is now DirAuthority, for consistency with
13389 current naming patterns. You can still use the old DirServer form.
13391 o Code simplification and refactoring:
13392 - Move the client-side address-map/virtual-address/DNS-cache code
13393 out of connection_edge.c into a new addressmap.c module.
13394 - Remove unused code for parsing v1 directories and "running routers"
13395 documents. Fixes bug 6887.
13398 Changes in version 0.2.3.25 - 2012-11-19
13399 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
13400 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
13401 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
13402 programmer, and friend. Unstinting in his dedication to the cause of
13403 freedom, he inspired and helped many of us as we began our work on
13404 anonymity, and inspires us still. Please honor his memory by writing
13405 software to protect people's freedoms, and by helping others to do so.
13407 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
13408 significantly reduced directory overhead (via microdescriptors),
13409 enormous crypto performance improvements for fast relays on new
13410 enough hardware, a new v3 TLS handshake protocol that can better
13411 resist fingerprinting, support for protocol obfuscation plugins (aka
13412 pluggable transports), better scalability for hidden services, IPv6
13413 support for bridges, performance improvements like allowing clients
13414 to skip the first round-trip on the circuit ("optimistic data") and
13415 refilling token buckets more often, a new "stream isolation" design
13416 to isolate different applications on different circuits, and many
13417 stability, security, and privacy fixes.
13420 - Tor tries to wipe potentially sensitive data after using it, so
13421 that if some subsequent security failure exposes Tor's memory,
13422 the damage will be limited. But we had a bug where the compiler
13423 was eliminating these wipe operations when it decided that the
13424 memory was no longer visible to a (correctly running) program,
13425 hence defeating our attempt at defense in depth. We fix that
13426 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
13427 is unlikely to optimize away. Future versions of Tor may use
13428 a less ridiculously heavy approach for this. Fixes bug 7352.
13429 Reported in an article by Andrey Karpov.
13432 - Fix a harmless bug when opting against publishing a relay descriptor
13433 because DisableNetwork is set. Fixes bug 7464; bugfix on
13437 Changes in version 0.2.4.6-alpha - 2012-11-13
13438 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
13439 makes our defense-in-depth memory wiping more reliable, and begins to
13440 count IPv6 addresses in bridge statistics,
13443 - Fix an assertion failure that could occur when closing a connection
13444 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
13446 - Tor tries to wipe potentially sensitive data after using it, so
13447 that if some subsequent security failure exposes Tor's memory,
13448 the damage will be limited. But we had a bug where the compiler
13449 was eliminating these wipe operations when it decided that the
13450 memory was no longer visible to a (correctly running) program,
13451 hence defeating our attempt at defense in depth. We fix that
13452 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
13453 is unlikely to optimize away. Future versions of Tor may use
13454 a less ridiculously heavy approach for this. Fixes bug 7352.
13455 Reported in an article by Andrey Karpov.
13458 - Add GeoIP database for IPv6 addresses. The new config option
13460 - Bridge statistics now count bridge clients connecting over IPv6:
13461 bridge statistics files now list "bridge-ip-versions" and
13462 extra-info documents list "geoip6-db-digest". The control protocol
13463 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
13464 implementation by "shkoo", addressing ticket 5055.
13467 - Warn when we are binding low ports when hibernation is enabled;
13468 previously we had warned when we were _advertising_ low ports with
13469 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
13470 - Fix a harmless bug when opting against publishing a relay descriptor
13471 because DisableNetwork is set. Fixes bug 7464; bugfix on
13473 - Add warning message when a managed proxy dies during configuration.
13474 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
13475 - Fix a linking error when building tor-fw-helper without miniupnp.
13476 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
13477 - Check for closing an or_connection_t without going through correct
13478 channel functions; emit a warning and then call
13479 connection_or_close_for_error() so we don't assert as in bugs 7212
13481 - Compile correctly on compilers without C99 designated initializer
13482 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
13483 - Avoid a possible assert that can occur when channel_send_destroy() is
13484 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
13485 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
13486 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
13487 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
13488 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
13490 o Code simplification and refactoring:
13491 - Start using OpenBSD's implementation of queue.h, so that we don't
13492 need to hand-roll our own pointer and list structures whenever we
13493 need them. (We can't rely on a sys/queue.h, since some operating
13494 systems don't have them, and the ones that do have them don't all
13495 present the same extensions.)
13498 Changes in version 0.2.4.5-alpha - 2012-10-25
13499 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
13500 two important security vulnerabilities that could lead to remotely
13501 triggerable relay crashes, fix a major bug that was preventing clients
13502 from choosing suitable exit nodes, and refactor some of our code.
13504 o Major bugfixes (security, also in 0.2.3.24-rc):
13505 - Fix a group of remotely triggerable assertion failures related to
13506 incorrect link protocol negotiation. Found, diagnosed, and fixed
13507 by "some guy from France". Fix for CVE-2012-2250; bugfix on
13509 - Fix a denial of service attack by which any directory authority
13510 could crash all the others, or by which a single v2 directory
13511 authority could crash everybody downloading v2 directory
13512 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
13514 o Major bugfixes (also in 0.2.3.24-rc):
13515 - When parsing exit policy summaries from microdescriptors, we had
13516 previously been ignoring the last character in each one, so that
13517 "accept 80,443,8080" would be treated by clients as indicating
13518 a node that allows access to ports 80, 443, and 808. That would
13519 lead to clients attempting connections that could never work,
13520 and ignoring exit nodes that would support their connections. Now
13521 clients parse these exit policy summaries correctly. Fixes bug 7192;
13522 bugfix on 0.2.3.1-alpha.
13524 o Minor bugfixes (also in 0.2.3.24-rc):
13525 - Clients now consider the ClientRejectInternalAddresses config option
13526 when using a microdescriptor consensus stanza to decide whether
13527 an exit relay would allow exiting to an internal address. Fixes
13528 bug 7190; bugfix on 0.2.3.1-alpha.
13531 - Only disable TLS session ticket support when running as a TLS
13532 server. Now clients will blend better with regular Firefox
13533 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
13535 o Code simplification and refactoring:
13536 - Start using OpenBSD's implementation of queue.h (originally by
13538 - Move the entry node code from circuitbuild.c to its own file.
13539 - Move the circuit build timeout tracking code from circuitbuild.c
13543 Changes in version 0.2.3.24-rc - 2012-10-25
13544 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
13545 could lead to remotely triggerable relay crashes, and fixes
13546 a major bug that was preventing clients from choosing suitable exit
13549 o Major bugfixes (security):
13550 - Fix a group of remotely triggerable assertion failures related to
13551 incorrect link protocol negotiation. Found, diagnosed, and fixed
13552 by "some guy from France". Fix for CVE-2012-2250; bugfix on
13554 - Fix a denial of service attack by which any directory authority
13555 could crash all the others, or by which a single v2 directory
13556 authority could crash everybody downloading v2 directory
13557 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
13560 - When parsing exit policy summaries from microdescriptors, we had
13561 previously been ignoring the last character in each one, so that
13562 "accept 80,443,8080" would be treated by clients as indicating
13563 a node that allows access to ports 80, 443, and 808. That would
13564 lead to clients attempting connections that could never work,
13565 and ignoring exit nodes that would support their connections. Now
13566 clients parse these exit policy summaries correctly. Fixes bug 7192;
13567 bugfix on 0.2.3.1-alpha.
13570 - Clients now consider the ClientRejectInternalAddresses config option
13571 when using a microdescriptor consensus stanza to decide whether
13572 an exit relay would allow exiting to an internal address. Fixes
13573 bug 7190; bugfix on 0.2.3.1-alpha.
13576 Changes in version 0.2.4.4-alpha - 2012-10-20
13577 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
13578 vulnerability introduced by a change in OpenSSL, fixes a remotely
13579 triggerable assert, and adds new channel_t and circuitmux_t abstractions
13580 that will make it easier to test new connection transport and cell
13581 scheduling algorithms.
13583 o New directory authorities (also in 0.2.3.23-rc):
13584 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
13585 authority. Closes ticket 5749.
13587 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
13588 - Disable TLS session tickets. OpenSSL's implementation was giving
13589 our TLS session keys the lifetime of our TLS context objects, when
13590 perfect forward secrecy would want us to discard anything that
13591 could decrypt a link connection as soon as the link connection
13592 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
13593 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
13594 - Discard extraneous renegotiation attempts once the V3 link
13595 protocol has been initiated. Failure to do so left us open to
13596 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
13597 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
13599 o Internal abstraction features:
13600 - Introduce new channel_t abstraction between circuits and
13601 or_connection_t to allow for implementing alternate OR-to-OR
13602 transports. A channel_t is an abstract object which can either be a
13603 cell-bearing channel, which is responsible for authenticating and
13604 handshaking with the remote OR and transmitting cells to and from
13605 it, or a listening channel, which spawns new cell-bearing channels
13606 at the request of remote ORs. Implements part of ticket 6465.
13607 - Also new is the channel_tls_t subclass of channel_t, adapting it
13608 to the existing or_connection_t code. The V2/V3 protocol handshaking
13609 code which formerly resided in command.c has been moved below the
13610 channel_t abstraction layer and may be found in channeltls.c now.
13611 Implements the rest of ticket 6465.
13612 - Introduce new circuitmux_t storing the queue of circuits for
13613 a channel; this encapsulates and abstracts the queue logic and
13614 circuit selection policy, and allows the latter to be overridden
13615 easily by switching out a policy object. The existing EWMA behavior
13616 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
13618 o Required libraries:
13619 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
13620 strongly recommended.
13623 - Warn users who run hidden services on a Tor client with
13624 UseEntryGuards disabled that their hidden services will be
13625 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
13626 attack which motivated Tor to support entry guards in the first
13627 place). Resolves ticket 6889.
13628 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
13629 dhill. Resolves ticket 6982.
13630 - Option OutboundBindAddress can be specified multiple times and
13631 accepts IPv6 addresses. Resolves ticket 6876.
13633 o Minor bugfixes (also in 0.2.3.23-rc):
13634 - Don't serve or accept v2 hidden service descriptors over a
13635 relay's DirPort. It's never correct to do so, and disabling it
13636 might make it more annoying to exploit any bugs that turn up in the
13637 descriptor-parsing code. Fixes bug 7149.
13638 - Fix two cases in src/or/transports.c where we were calling
13639 fmt_addr() twice in a parameter list. Bug found by David
13640 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
13641 - Fix memory leaks whenever we logged any message about the "path
13642 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
13643 - When relays refuse a "create" cell because their queue of pending
13644 create cells is too big (typically because their cpu can't keep up
13645 with the arrival rate), send back reason "resource limit" rather
13646 than reason "internal", so network measurement scripts can get a
13647 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
13650 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
13651 - Free some more still-in-use memory at exit, to make hunting for
13652 memory leaks easier. Resolves bug 7029.
13653 - When a Tor client gets a "truncated" relay cell, the first byte of
13654 its payload specifies why the circuit was truncated. We were
13655 ignoring this 'reason' byte when tearing down the circuit, resulting
13656 in the controller not being told why the circuit closed. Now we
13657 pass the reason from the truncated cell to the controller. Bugfix
13658 on 0.1.2.3-alpha; fixes bug 7039.
13659 - Downgrade "Failed to hand off onionskin" messages to "debug"
13660 severity, since they're typically redundant with the "Your computer
13661 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
13662 - Make clients running with IPv6 bridges connect over IPv6 again,
13663 even without setting new config options ClientUseIPv6 and
13664 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
13665 - Use square brackets around IPv6 addresses in numerous places
13666 that needed them, including log messages, HTTPS CONNECT proxy
13667 requests, TransportProxy statefile entries, and pluggable transport
13668 extra-info lines. Fixes bug 7011; patch by David Fifield.
13670 o Code refactoring and cleanup:
13671 - Source files taken from other packages now reside in src/ext;
13672 previously they were scattered around the rest of Tor.
13673 - Avoid use of reserved identifiers in our C code. The C standard
13674 doesn't like us declaring anything that starts with an
13675 underscore, so let's knock it off before we get in trouble. Fix
13676 for bug 1031; bugfix on the first Tor commit.
13679 Changes in version 0.2.3.23-rc - 2012-10-20
13680 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
13681 vulnerability introduced by a change in OpenSSL, and fixes a variety
13682 of smaller bugs in preparation for the release.
13684 o New directory authorities:
13685 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
13686 authority. Closes ticket 5749.
13688 o Major bugfixes (security/privacy):
13689 - Disable TLS session tickets. OpenSSL's implementation was giving
13690 our TLS session keys the lifetime of our TLS context objects, when
13691 perfect forward secrecy would want us to discard anything that
13692 could decrypt a link connection as soon as the link connection
13693 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
13694 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
13695 - Discard extraneous renegotiation attempts once the V3 link
13696 protocol has been initiated. Failure to do so left us open to
13697 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
13698 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
13701 - Fix a possible crash bug when checking for deactivated circuits
13702 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
13703 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
13705 o Minor bugfixes (on 0.2.3.x):
13706 - Fix two cases in src/or/transports.c where we were calling
13707 fmt_addr() twice in a parameter list. Bug found by David
13708 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
13709 - Convert an assert in the pathbias code to a log message. The assert
13710 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
13711 bugfix on 0.2.3.17-beta.
13712 - Fix memory leaks whenever we logged any message about the "path
13713 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
13715 o Minor bugfixes (on 0.2.2.x and earlier):
13716 - Don't serve or accept v2 hidden service descriptors over a relay's
13717 DirPort. It's never correct to do so, and disabling it might
13718 make it more annoying to exploit any bugs that turn up in the
13719 descriptor-parsing code. Fixes bug 7149.
13720 - When relays refuse a "create" cell because their queue of pending
13721 create cells is too big (typically because their cpu can't keep up
13722 with the arrival rate), send back reason "resource limit" rather
13723 than reason "internal", so network measurement scripts can get a
13724 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
13725 - Correct file sizes when reading binary files on Cygwin, to avoid
13726 a bug where Tor would fail to read its state file. Fixes bug 6844;
13727 bugfix on 0.1.2.7-alpha.
13728 - Avoid undefined behavior when parsing the list of supported
13729 rendezvous/introduction protocols in a hidden service descriptor.
13730 Previously, Tor would have confused (as-yet-unused) protocol version
13731 numbers greater than 32 with lower ones on many platforms. Fixes
13732 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
13734 o Documentation fixes:
13735 - Clarify that hidden services are TCP only. Fixes bug 6024.
13738 Changes in version 0.2.4.3-alpha - 2012-09-22
13739 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
13740 assertion, resumes letting relays test reachability of their DirPort,
13741 and cleans up a bunch of smaller bugs.
13744 - Fix an assertion failure in tor_timegm() that could be triggered
13745 by a badly formatted directory object. Bug found by fuzzing with
13746 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
13749 - Fix a possible crash bug when checking for deactivated circuits
13750 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
13751 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
13752 - Allow routers to detect that their own DirPorts are running. When
13753 we removed support for versions_supports_begindir, we also
13754 accidentally removed the mechanism we used to self-test our
13755 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
13756 bugfix on 0.2.4.2-alpha.
13758 o Security features:
13759 - Switch to a completely time-invariant approach for picking nodes
13760 weighted by bandwidth. Our old approach would run through the
13761 part of the loop after it had made its choice slightly slower
13762 than it ran through the part of the loop before it had made its
13763 choice. Addresses ticket 6538.
13764 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
13765 by tor2web clients allows hidden services to identify tor2web
13766 clients through their repeated selection of the same rendezvous
13767 and introduction point circuit endpoints (their guards). Resolves
13771 - Enable Tor to read configuration, state, and key information from
13772 a FIFO. Previously Tor would only read from files with a positive
13773 stat.st_size. Code from meejah; fixes bug 6044.
13776 - Correct file sizes when reading binary files on Cygwin, to avoid
13777 a bug where Tor would fail to read its state file. Fixes bug 6844;
13778 bugfix on 0.1.2.7-alpha.
13779 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
13780 bugfix on 0.2.0.3-alpha.
13781 - When complaining about a client port on a public address, log
13782 which address we're complaining about. Fixes bug 4020; bugfix on
13783 0.2.3.3-alpha. Patch by Tom Fitzhenry.
13784 - Convert an assert in the pathbias code to a log message. The assert
13785 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
13786 bugfix on 0.2.3.17-beta.
13787 - Our new buildsystem was overzealous about rebuilding manpages: it
13788 would rebuild them all whenever any one of them changed. Now our
13789 dependency checking should be correct. Fixes bug 6843; bugfix on
13791 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
13792 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
13793 - Correct log printout about which address family is preferred
13794 when connecting to a bridge with both an IPv4 and IPv6 OR port.
13795 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
13797 o Minor bugfixes (code cleanliness):
13798 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
13799 with large values. This situation was untriggered, but nevertheless
13800 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
13801 - Reject consensus votes with more than 64 known-flags. We aren't even
13802 close to that limit yet, and our code doesn't handle it correctly.
13803 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
13804 - Avoid undefined behavior when parsing the list of supported
13805 rendezvous/introduction protocols in a hidden service descriptor.
13806 Previously, Tor would have confused (as-yet-unused) protocol version
13807 numbers greater than 32 with lower ones on many platforms. Fixes
13808 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
13809 - Fix handling of rendezvous client authorization types over 8.
13810 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
13811 - Fix building with older versions of GCC (2.95, for one) that don't
13812 like preprocessor directives inside macro arguments. Found by
13813 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
13814 - Switch weighted node selection rule from using a list of doubles
13815 to using a list of int64_t. This change should make the process
13816 slightly easier to debug and maintain. Needed to finish ticket 6538.
13818 o Code simplification and refactoring:
13819 - Move the generic "config" code into a new file, and have "config.c"
13820 hold only torrc- and state-related code. Resolves ticket 6823.
13821 - Move the core of our "choose a weighted element at random" logic
13822 into its own function, and give it unit tests. Now the logic is
13823 testable, and a little less fragile too.
13824 - Removed the testing_since field of node_t, which hasn't been used
13825 for anything since 0.2.0.9-alpha.
13827 o Documentation fixes:
13828 - Clarify that hidden services are TCP only. Fixes bug 6024.
13829 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
13833 Changes in version 0.2.3.22-rc - 2012-09-11
13834 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
13838 - Fix an assertion failure in tor_timegm() that could be triggered
13839 by a badly formatted directory object. Bug found by fuzzing with
13840 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
13843 - Avoid segfault when starting up having run with an extremely old
13844 version of Tor and parsing its state file. Fixes bug 6801; bugfix
13848 Changes in version 0.2.2.39 - 2012-09-11
13849 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
13853 - Fix an assertion failure in tor_timegm() that could be triggered
13854 by a badly formatted directory object. Bug found by fuzzing with
13855 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
13856 - Do not crash when comparing an address with port value 0 to an
13857 address policy. This bug could have been used to cause a remote
13858 assertion failure by or against directory authorities, or to
13859 allow some applications to crash clients. Fixes bug 6690; bugfix
13863 Changes in version 0.2.4.2-alpha - 2012-09-10
13864 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
13865 raises the default rate limiting even more, and makes the bootstrapping
13866 log messages less noisy.
13869 - Automatically forward the TCP ports of pluggable transport
13870 proxies using tor-fw-helper if PortForwarding is enabled. Implements
13874 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
13875 to 1GB/1GB. The previous defaults were intended to be "basically
13876 infinite", but it turns out they're now limiting our 100mbit+
13877 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
13878 last time we raised it).
13881 - Detect when we're running with a version of OpenSSL other than the
13882 one we compiled with. This has occasionally given people hard-to-
13884 - Log fewer lines at level "notice" about our OpenSSL and Libevent
13885 versions and capabilities when everything is going right. Resolves
13886 part of ticket 6736.
13887 - Directory authorities no long accept descriptors for any version of
13888 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
13889 These versions are insecure, unsupported, or both. Implements
13893 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
13894 to start with a triple-underscore so the controller won't touch it.
13895 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
13896 - Avoid segfault when starting up having run with an extremely old
13897 version of Tor and parsing its state file. Fixes bug 6801; bugfix
13899 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
13900 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
13901 - Don't follow the NULL pointer if microdescriptor generation fails.
13902 (This does not appear to be triggerable, but it's best to be safe.)
13903 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
13904 - Fix mis-declared dependencies on src/common/crypto.c and
13905 src/or/tor_main.c that could break out-of-tree builds under some
13906 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
13907 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
13908 6778; bugfix on 0.2.4.1-alpha.
13909 - Fix a harmless (in this case) build warning for implicitly
13910 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
13912 o Removed features:
13913 - Now that all versions before 0.2.2.x are disallowed, we no longer
13914 need to work around their missing features. Thus we can remove a
13915 bunch of compatibility code.
13917 o Code refactoring:
13918 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
13919 TCP ports to forward. In the past it only accepted two ports:
13920 the ORPort and the DirPort.
13923 Changes in version 0.2.4.1-alpha - 2012-09-05
13924 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
13925 bridgedb; lets relays use IPv6 addresses and directory authorities
13926 advertise them; and switches to a cleaner build interface.
13928 This is the first alpha release in a new series, so expect there to
13929 be bugs. Users who would rather test out a more stable branch should
13930 stay with 0.2.3.x for now.
13932 o Major features (bridges):
13933 - Bridges now report the pluggable transports they support to the
13934 bridge authority, so it can pass the supported transports on to
13935 bridgedb and/or eventually do reachability testing. Implements
13938 o Major features (IPv6):
13939 - Bridge authorities now accept IPv6 bridge addresses and include
13940 them in network status documents. Implements ticket 5534.
13941 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
13942 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
13943 to happen. Implements ticket 5535.
13944 - All kind of relays, not just bridges, can now advertise an IPv6
13945 OR port. Implements ticket 6362.
13946 - Directory authorities vote on IPv6 OR ports using the new consensus
13947 method 14. Implements ticket 6363.
13949 o Major features (build):
13950 - Switch to a nonrecursive Makefile structure. Now instead of each
13951 Makefile.am invoking other Makefile.am's, there is a master
13952 Makefile.am that includes the others. This change makes our build
13953 process slightly more maintainable, and improves parallelism for
13954 building with make -j. Original patch by Stewart Smith; various
13955 fixes by Jim Meyering.
13956 - Where available, we now use automake's "silent" make rules by
13957 default, so that warnings are easier to spot. You can get the old
13958 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
13960 o Minor features (code security and spec conformance):
13961 - Clear keys and key-derived material left on the stack in
13962 rendservice.c and rendclient.c. Check return value of
13963 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
13964 These fixes should make us more forward-secure against cold-boot
13965 attacks and the like. Fixes bug 2385.
13966 - Reject EXTEND cells sent to nonexistent streams. According to the
13967 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
13968 we were only checking for stream IDs that were currently in use.
13969 Found while hunting for more instances of bug 6271. Bugfix on
13970 0.0.2pre8, which introduced incremental circuit construction.
13972 o Minor features (streamlining);
13973 - No longer include the "opt" prefix when generating routerinfos
13974 or v2 directories: it has been needless since Tor 0.1.2. Closes
13976 - Remove some now-needless code that tried to aggressively flush
13977 OR connections as data was added to them. Since 0.2.0.1-alpha, our
13978 cell queue logic has saved us from the failure mode that this code
13979 was supposed to prevent. Removing this code will limit the number
13980 of baroque control flow paths through Tor's network logic. Reported
13981 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
13983 o Minor features (controller):
13984 - Add a "GETINFO signal/names" control port command. Implements
13986 - Provide default values for all options via "GETINFO config/defaults".
13987 Implements ticket 4971.
13989 o Minor features (IPv6):
13990 - New config option "AuthDirHasIPv6Connectivity 1" that directory
13991 authorities should set if they have IPv6 connectivity and want to
13992 do reachability tests for IPv6 relays. Implements feature 5974.
13993 - A relay with an IPv6 OR port now sends that address in NETINFO
13994 cells (in addition to its other address). Implements ticket 6364.
13996 o Minor features (log messages):
13997 - Omit the first heartbeat log message, because it never has anything
13998 useful to say, and it clutters up the bootstrapping messages.
13999 Resolves ticket 6758.
14000 - Don't log about reloading the microdescriptor cache at startup. Our
14001 bootstrap warnings are supposed to tell the user when there's a
14002 problem, and our bootstrap notices say when there isn't. Resolves
14003 ticket 6759; bugfix on 0.2.2.6-alpha.
14004 - Don't log "I learned some more directory information" when we're
14005 reading cached directory information. Reserve it for when new
14006 directory information arrives in response to a fetch. Resolves
14008 - Prevent rounding error in path bias counts when scaling
14009 them down, and use the correct scale factor default. Also demote
14010 some path bias related log messages down a level and make others
14011 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
14012 - We no longer warn so much when generating manpages from their
14015 o Code simplifications and refactoring:
14016 - Enhance our internal sscanf replacement so that we can eliminate
14017 the last remaining uses of the system sscanf. (Though those uses
14018 of sscanf were safe, sscanf itself is generally error prone, so
14019 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
14021 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
14022 - Move last_reachable and testing_since from routerinfo_t to node_t.
14023 Implements ticket 5529.
14024 - Add replaycache_t structure, functions and unit tests, then refactor
14025 rend_service_introduce() to be more clear to read, improve, debug,
14026 and test. Resolves bug 6177.
14027 - Finally remove support for malloc_good_size and malloc_usable_size.
14028 We had hoped that these functions would let us eke a little more
14029 memory out of our malloc implementation. Unfortunately, the only
14030 implementations that provided these functions are also ones that
14031 are already efficient about not overallocation: they never got us
14032 more than 7 or so bytes per allocation. Removing them saves us a
14033 little code complexity and a nontrivial amount of build complexity.
14035 o New requirements:
14036 - Tor maintainers now require Automake version 1.9 or later to build
14037 Tor from the Git repository. (Automake is not required when building
14038 from a source distribution.)
14041 Changes in version 0.2.3.21-rc - 2012-09-05
14042 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
14043 series. It fixes a trio of potential security bugs, fixes a bug where
14044 we were leaving some of the fast relays out of the microdescriptor
14045 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
14046 and cleans up other smaller issues.
14048 o Major bugfixes (security):
14049 - Tear down the circuit if we get an unexpected SENDME cell. Clients
14050 could use this trick to make their circuits receive cells faster
14051 than our flow control would have allowed, or to gum up the network,
14052 or possibly to do targeted memory denial-of-service attacks on
14053 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
14054 from July 2002, before the release of Tor 0.0.0. We had committed
14055 this patch previously, but we had to revert it because of bug 6271.
14056 Now that 6271 is fixed, this patch appears to work.
14057 - Reject any attempt to extend to an internal address. Without
14058 this fix, a router could be used to probe addresses on an internal
14059 network to see whether they were accepting connections. Fixes bug
14060 6710; bugfix on 0.0.8pre1.
14061 - Do not crash when comparing an address with port value 0 to an
14062 address policy. This bug could have been used to cause a remote
14063 assertion failure by or against directory authorities, or to
14064 allow some applications to crash clients. Fixes bug 6690; bugfix
14068 - Remove the upper bound on microdescriptor length. We were hitting
14069 the limit for routers with complex exit policies or family
14070 declarations, causing clients to not use them. Fixes the first
14071 piece of bug 6404; fix on 0.2.2.6-alpha.
14072 - Detect "ORPort 0" as meaning, uniformly, that we're not running
14073 as a relay. Previously, some of our code would treat the presence
14074 of any ORPort line as meaning that we should act like a relay,
14075 even though our new listener code would correctly not open any
14076 ORPorts for ORPort 0. Similar bugs in other Port options are also
14077 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
14080 - Avoid a pair of double-free and use-after-mark bugs that can
14081 occur with certain timings in canceled and re-received DNS
14082 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
14083 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
14084 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
14085 - Allow one-hop directory fetching circuits the full "circuit build
14086 timeout" period, rather than just half of it, before failing them
14087 and marking the relay down. This fix should help reduce cases where
14088 clients declare relays (or worse, bridges) unreachable because
14089 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
14090 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
14092 - Authorities no longer include any router in their microdescriptor
14093 consensuses for which they couldn't generate or agree on a
14094 microdescriptor. Fixes the second piece of bug 6404; fix on
14096 - Detect and reject attempts to specify both "FooPort" and
14097 "FooPort 0" in the same configuration domain. (It's still okay
14098 to have a FooPort in your configuration file, and use "FooPort 0"
14099 on the command line to disable it.) Fixes the second half of bug
14100 6507; bugfix on 0.2.3.3-alpha.
14101 - Make wildcarded addresses (that is, ones beginning with "*.") work
14102 when provided via the controller's MapAddress command. Previously,
14103 they were accepted, but we never actually noticed that they were
14104 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
14105 - Avoid crashing on a malformed state file where EntryGuardPathBias
14106 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
14107 - Add a (probably redundant) memory clear between iterations of
14108 the router status voting loop, to prevent future coding errors
14109 where data might leak between iterations of the loop. Resolves
14112 o Minor bugfixes (log messages):
14113 - Downgrade "set buildtimeout to low value" messages to "info"
14114 severity; they were never an actual problem, there was never
14115 anything reasonable to do about them, and they tended to spam logs
14116 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
14117 - Downgrade path-bias warning messages to "info". We'll try to get
14118 them working better in 0.2.4. Add internal circuit construction
14119 state to protect against the noisy warn message "Unexpectedly high
14120 circuit_successes". Also add some additional rate-limited notice
14121 messages to help determine the root cause of the warn. Fixes bug
14122 6475. Bugfix against 0.2.3.17-beta.
14123 - Move log message when unable to find a microdesc in a routerstatus
14124 entry to parse time. Previously we'd spam this warning every time
14125 we tried to figure out which microdescriptors to download. Fixes
14126 the third piece of bug 6404; fix on 0.2.3.18-rc.
14129 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
14130 change when the authority is deciding whether to accept a newly
14131 uploaded descriptor. Implements ticket 6423.
14132 - Add missing documentation for consensus and microdesc files.
14133 Resolves ticket 6732.
14136 Changes in version 0.2.2.38 - 2012-08-12
14137 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
14138 attack that could in theory leak path information.
14141 - Avoid an uninitialized memory read when reading a vote or consensus
14142 document that has an unrecognized flavor name. This read could
14143 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14144 - Try to leak less information about what relays a client is
14145 choosing to a side-channel attacker. Previously, a Tor client would
14146 stop iterating through the list of available relays as soon as it
14147 had chosen one, thus finishing a little earlier when it picked
14148 a router earlier in the list. If an attacker can recover this
14149 timing information (nontrivial but not proven to be impossible),
14150 they could learn some coarse-grained information about which relays
14151 a client was picking (middle nodes in particular are likelier to
14152 be affected than exits). The timing attack might be mitigated by
14153 other factors (see bug 6537 for some discussion), but it's best
14154 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14157 Changes in version 0.2.3.20-rc - 2012-08-05
14158 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
14159 series. It fixes a pair of code security bugs and a potential anonymity
14160 issue, updates our RPM spec files, and cleans up other smaller issues.
14163 - Avoid read-from-freed-memory and double-free bugs that could occur
14164 when a DNS request fails while launching it. Fixes bug 6480;
14165 bugfix on 0.2.0.1-alpha.
14166 - Avoid an uninitialized memory read when reading a vote or consensus
14167 document that has an unrecognized flavor name. This read could
14168 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14169 - Try to leak less information about what relays a client is
14170 choosing to a side-channel attacker. Previously, a Tor client would
14171 stop iterating through the list of available relays as soon as it
14172 had chosen one, thus finishing a little earlier when it picked
14173 a router earlier in the list. If an attacker can recover this
14174 timing information (nontrivial but not proven to be impossible),
14175 they could learn some coarse-grained information about which relays
14176 a client was picking (middle nodes in particular are likelier to
14177 be affected than exits). The timing attack might be mitigated by
14178 other factors (see bug 6537 for some discussion), but it's best
14179 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14182 - Try to make the warning when giving an obsolete SOCKSListenAddress
14183 a little more useful.
14184 - Terminate active server managed proxies if Tor stops being a
14185 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
14186 - Provide a better error message about possible OSX Asciidoc failure
14187 reasons. Fixes bug 6436.
14188 - Warn when Tor is configured to use accounting in a way that can
14189 link a hidden service to some other hidden service or public
14190 address. Resolves ticket 6490.
14193 - Check return value of fputs() when writing authority certificate
14194 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
14195 - Ignore ServerTransportPlugin lines when Tor is not configured as
14196 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
14197 - When disabling guards for having too high a proportion of failed
14198 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
14202 - Update our default RPM spec files to work with mock and rpmbuild
14203 on RHEL/Fedora. They have an updated set of dependencies and
14204 conflicts, a fix for an ancient typo when creating the "_tor"
14205 user, and better instructions. Thanks to Ondrej Mikle for the
14206 patch series. Fixes bug 6043.
14209 - Make it possible to set the TestingTorNetwork configuration
14210 option using AlternateDirAuthority and AlternateBridgeAuthority
14211 as an alternative to setting DirServer. Addresses ticket 6377.
14214 - Clarify the documentation for the Alternate*Authority options.
14216 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
14218 o Code simplification and refactoring:
14219 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
14220 10 lines. Also, don't nest them. Doing so in the past has
14221 led to hard-to-debug code. The new style is to use the
14222 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
14225 Changes in version 0.2.3.19-rc - 2012-07-06
14226 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
14227 series. It fixes the compile on Windows, reverts to a GeoIP database
14228 that isn't as broken, and fixes a flow control bug that has been around
14229 since the beginning of Tor.
14232 - Fix a bug handling SENDME cells on nonexistent streams that could
14233 result in bizarre window values. Report and patch contributed
14234 pseudonymously. Fixes part of bug 6271. This bug was introduced
14235 before the first Tor release, in svn commit r152.
14236 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
14237 June 2012 database, Maxmind marked many Tor relays as country "A1",
14238 which will cause risky behavior for clients that set EntryNodes
14239 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
14240 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
14241 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
14244 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
14245 bugfix on 0.2.1.10-alpha.
14248 Changes in version 0.2.3.18-rc - 2012-06-28
14249 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
14250 series. It fixes a few smaller bugs, but generally appears stable.
14251 Please test it and let us know whether it is!
14254 - Allow wildcarded mapaddress targets to be specified on the
14255 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
14256 - Make our linker option detection code more robust against linkers
14257 such as on FreeBSD 8, where a bad combination of options completes
14258 successfully but makes an unrunnable binary. Fixes bug 6173;
14259 bugfix on 0.2.3.17-beta.
14261 o Minor bugfixes (on 0.2.2.x and earlier):
14262 - Avoid a false positive in the util/threads unit test by increasing
14263 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
14264 - Replace "Sending publish request" log messages with "Launching
14265 upload", so that they no longer confusingly imply that we're
14266 sending something to a directory we might not even be connected
14267 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
14268 - Make sure to set *socket_error in all error cases in
14269 connection_connect(), so it can't produce a warning about
14270 errno being zero from errno_to_orconn_end_reason(). Bugfix on
14271 0.2.1.1-alpha; resolves ticket 6028.
14272 - Downgrade "Got a certificate, but we already have it" log messages
14273 from warning to info, except when we're a dirauth. Fixes bug 5238;
14274 bugfix on 0.2.1.7-alpha.
14275 - When checking for requested signatures on the latest consensus
14276 before serving it to a client, make sure to check the right
14277 consensus flavor. Bugfix on 0.2.2.6-alpha.
14278 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
14279 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
14281 o Minor bugfixes (on 0.2.3.x):
14282 - Make format_helper_exit_status() avoid unnecessary space padding
14283 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
14285 - Downgrade a message about cleaning the microdescriptor cache to
14286 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
14287 - Log a BUG message at severity INFO if we have a networkstatus with
14288 a missing entry for some microdescriptor. Continues on a patch
14290 - Improve the log message when a managed proxy fails to launch. Fixes
14291 bug 5099; bugfix on 0.2.3.6-alpha.
14292 - Don't do DNS lookups when parsing corrupted managed proxy protocol
14293 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
14294 - When formatting wildcarded address mappings for the controller,
14295 be sure to include "*." as appropriate. Partially fixes bug 6244;
14296 bugfix on 0.2.3.9-alpha.
14297 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
14298 Bugfix on 0.2.3.13-alpha.
14299 - Stop logging messages about running with circuit timeout learning
14300 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
14301 - Disable a spurious warning about reading on a marked and flushing
14302 connection. We shouldn't be doing that, but apparently we
14303 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
14304 - Fix a bug that stopped AllowDotExit from working on addresses
14305 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
14308 o Code simplification, refactoring, unit tests:
14309 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
14310 Libevent's notion of cached time when possible.
14311 - Remove duplicate code for invoking getrlimit() from control.c.
14312 - Add a unit test for the environment_variable_names_equal function.
14315 - Document the --defaults-torrc option, and the new (in 0.2.3)
14316 semantics for overriding, extending, and clearing lists of
14317 options. Closes bug 4748.
14320 Changes in version 0.2.3.17-beta - 2012-06-15
14321 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
14322 gets our TLS handshake back on track for being able to blend in with
14323 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
14324 with Vidalia, and otherwise continues to get us closer to a release
14328 - Enable gcc and ld hardening by default. Resolves ticket 5210.
14329 - Update TLS cipher list to match Firefox 8 and later. Resolves
14331 - Implement the client side of proposal 198: remove support for
14332 clients falsely claiming to support standard ciphersuites that
14333 they can actually provide. As of modern OpenSSL versions, it's not
14334 necessary to fake any standard ciphersuite, and doing so prevents
14335 us from using better ciphersuites in the future, since servers
14336 can't know whether an advertised ciphersuite is really supported or
14337 not. Some hosts -- notably, ones with very old versions of OpenSSL
14338 or where OpenSSL has been built with ECC disabled -- will stand
14339 out because of this change; TBB users should not be affected.
14342 - Change the default value for DynamicDHGroups (introduced in
14343 0.2.3.9-alpha) to 0. This feature can make Tor relays less
14344 identifiable by their use of the mod_ssl DH group, but at
14345 the cost of some usability (#4721) and bridge tracing (#6087)
14346 regressions. Resolves ticket 5598.
14347 - Send a CRLF at the end of each STATUS_* control protocol event. This
14348 bug tickled a bug in Vidalia which would make it freeze. Fixes
14349 bug 6094; bugfix on 0.2.3.16-alpha.
14352 - Disable writing on marked-for-close connections when they are
14353 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
14354 bug 5263; bugfix on 0.0.2pre13, where we first added a special
14355 case for flushing marked connections.
14356 - Detect SSL handshake even when the initial attempt to write the
14357 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
14358 - Change the AllowDotExit rules so they should actually work.
14359 We now enforce AllowDotExit only immediately after receiving an
14360 address via SOCKS or DNSPort: other sources are free to provide
14361 .exit addresses after the resolution occurs. Fixes bug 3940;
14362 bugfix on 0.2.2.1-alpha.
14363 - Fix a (harmless) integer overflow in cell statistics reported by
14364 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
14365 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
14366 right places and never depends on the consensus parameters or
14367 computes adaptive timeouts when it is disabled. Fixes bug 5049;
14368 bugfix on 0.2.2.14-alpha.
14369 - When building Tor on Windows with -DUNICODE (not default), ensure
14370 that error messages, filenames, and DNS server names are always
14371 NUL-terminated when we convert them to a single-byte encoding.
14372 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
14373 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
14374 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
14375 - Fix an edge case where TestingTorNetwork is set but the authorities
14376 and relays all have an uptime of zero, where the private Tor network
14377 could briefly lack support for hidden services. Fixes bug 3886;
14378 bugfix on 0.2.2.18-alpha.
14379 - Correct the manpage's descriptions for the default values of
14380 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
14382 - Fix the documentation for the --hush and --quiet command line
14383 options, which changed their behavior back in 0.2.3.3-alpha.
14384 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
14388 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
14389 more information to it, so that we can track it down in case it
14390 returns again. Mitigates bug 5235.
14391 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
14392 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
14393 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
14394 - Warn the user when HTTPProxy, but no other proxy type, is
14395 configured. This can cause surprising behavior: it doesn't send
14396 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
14397 directory traffic only. Resolves ticket 4663.
14398 - Issue a notice if a guard completes less than 40% of your circuits.
14399 Threshold is configurable by torrc option PathBiasNoticeRate and
14400 consensus parameter pb_noticepct. There is additional, off-by-
14401 default code to disable guards which fail too many circuits.
14402 Addresses ticket 5458.
14403 - Update to the June 6 2012 Maxmind GeoLite Country database.
14405 o Code simplifications and refactoring:
14406 - Remove validate_pluggable_transports_config(): its warning
14407 message is now handled by connection_or_connect().
14410 Changes in version 0.2.2.37 - 2012-06-06
14411 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
14412 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
14416 - Work around a bug in OpenSSL that broke renegotiation with TLS
14417 1.1 and TLS 1.2. Without this workaround, all attempts to speak
14418 the v2 Tor connection protocol when both sides were using OpenSSL
14419 1.0.1 would fail. Resolves ticket 6033.
14420 - When waiting for a client to renegotiate, don't allow it to add
14421 any bytes to the input buffer. This fixes a potential DoS issue.
14422 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
14423 - Fix an edge case where if we fetch or publish a hidden service
14424 descriptor, we might build a 4-hop circuit and then use that circuit
14425 for exiting afterwards -- even if the new last hop doesn't obey our
14426 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
14429 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
14430 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
14433 - Tell GCC and Clang to check for any errors in format strings passed
14434 to the tor_v*(print|scan)f functions.
14437 Changes in version 0.2.3.16-alpha - 2012-06-05
14438 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
14439 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
14440 currently). It also fixes a variety of smaller bugs and other cleanups
14441 that get us closer to a release candidate.
14443 o Major bugfixes (general):
14444 - Work around a bug in OpenSSL that broke renegotiation with TLS
14445 1.1 and TLS 1.2. Without this workaround, all attempts to speak
14446 the v2 Tor connection protocol when both sides were using OpenSSL
14447 1.0.1 would fail. Resolves ticket 6033.
14448 - When waiting for a client to renegotiate, don't allow it to add
14449 any bytes to the input buffer. This fixes a potential DoS issue.
14450 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
14451 - Pass correct OR address to managed proxies (like obfsproxy),
14452 even when ORListenAddress is used. Fixes bug 4865; bugfix on
14454 - The advertised platform of a router now includes only its operating
14455 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
14456 service pack level (for Windows) or its CPU architecture (for Unix).
14457 We also no longer include the "git-XYZ" tag in the version. Resolves
14460 o Major bugfixes (clients):
14461 - If we are unable to find any exit that supports our predicted ports,
14462 stop calling them predicted, so that we don't loop and build
14463 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
14464 which introduced predicted ports.
14465 - Fix an edge case where if we fetch or publish a hidden service
14466 descriptor, we might build a 4-hop circuit and then use that circuit
14467 for exiting afterwards -- even if the new last hop doesn't obey our
14468 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
14469 - Check at each new consensus whether our entry guards were picked
14470 long enough ago that we should rotate them. Previously, we only
14471 did this check at startup, which could lead to us holding a guard
14472 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
14473 - When fetching a bridge descriptor from a bridge authority,
14474 always do so anonymously, whether we have been able to open
14475 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
14476 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
14477 but we'll need to wait for bug 6010 before it's actually usable.
14479 o Major bugfixes (directory authorities):
14480 - When computing weight parameters, behave more robustly in the
14481 presence of a bad bwweightscale value. Previously, the authorities
14482 would crash if they agreed on a sufficiently broken weight_scale
14483 value: now, they use a reasonable default and carry on. Partial
14484 fix for 5786; bugfix on 0.2.2.17-alpha.
14485 - Check more thoroughly to prevent a rogue authority from
14486 double-voting on any consensus directory parameter. Previously,
14487 authorities would crash in this case if the total number of
14488 votes for any parameter exceeded the number of active voters,
14489 but would let it pass otherwise. Partial fix for bug 5786; bugfix
14493 - Rate-limit log messages when asked to connect anonymously to
14494 a private address. When these hit, they tended to hit fast and
14495 often. Also, don't bother trying to connect to addresses that we
14496 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
14497 reply makes us think we have been lied to, even when the address the
14498 client tried to connect to was "localhost." Resolves ticket 2822.
14499 - Allow packagers to insert an extra string in server descriptor
14500 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
14501 Resolves the rest of ticket 2988.
14502 - Raise the threshold of server descriptors needed (75%) and exit
14503 server descriptors needed (50%) before we will declare ourselves
14504 bootstrapped. This will make clients start building circuits a
14505 little later, but makes the initially constructed circuits less
14506 skewed and less in conflict with further directory fetches. Fixes
14508 - Close any connection that sends unrecognized junk before the
14509 handshake. Solves an issue noted in bug 4369.
14510 - Improve log messages about managed transports. Resolves ticket 5070.
14511 - Tag a bridge's descriptor as "never to be sent unencrypted".
14512 This shouldn't matter, since bridges don't open non-anonymous
14513 connections to the bridge authority and don't allow unencrypted
14514 directory connections from clients, but we might as well make
14515 sure. Closes bug 5139.
14516 - Expose our view of whether we have gone dormant to the controller,
14517 via a new "GETINFO dormant" value. Torbutton and other controllers
14518 can use this to avoid doing periodic requests through Tor while
14519 it's dormant (bug 4718). Fixes bug 5954.
14520 - Tell GCC and Clang to check for any errors in format strings passed
14521 to the tor_v*(print|scan)f functions.
14522 - Update to the May 1 2012 Maxmind GeoLite Country database.
14524 o Minor bugfixes (already included in 0.2.2.36):
14525 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
14526 Fixes bug 5346; bugfix on 0.0.8pre3.
14527 - Correct parsing of certain date types in parse_http_time().
14528 Without this patch, If-Modified-Since would behave
14529 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
14530 Esteban Manchado Velázques.
14531 - Make our number-parsing functions always treat too-large values
14532 as an error, even when those values exceed the width of the
14533 underlying type. Previously, if the caller provided these
14534 functions with minima or maxima set to the extreme values of the
14535 underlying integer type, these functions would return those
14536 values on overflow rather than treating overflow as an error.
14537 Fixes part of bug 5786; bugfix on 0.0.9.
14538 - If we hit the error case where routerlist_insert() replaces an
14539 existing (old) server descriptor, make sure to remove that
14540 server descriptor from the old_routers list. Fix related to bug
14541 1776. Bugfix on 0.2.2.18-alpha.
14542 - Clarify the behavior of MaxCircuitDirtiness with hidden service
14543 circuits. Fixes issue 5259.
14545 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
14546 - Prevent a null-pointer dereference when receiving a data cell
14547 for a nonexistent stream when the circuit in question has an
14548 empty deliver window. We don't believe this is triggerable,
14549 since we don't currently allow deliver windows to become empty,
14550 but the logic is tricky enough that it's better to make the code
14551 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
14552 - Fix a memory leak when trying to launch a DNS request when the
14553 network is disabled or the nameservers are unconfigurable. Fixes
14554 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
14555 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
14556 - Don't hold a Windows file handle open for every file mapping;
14557 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
14559 - Avoid O(n^2) performance characteristics when parsing a large
14560 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
14561 - Format more doubles with %f, not %lf. Patch from grarpamp to make
14562 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
14564 - Make our replacement implementation of strtok_r() compatible with
14565 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
14566 bugfix on 0.2.2.1-alpha.
14567 - Fix a NULL-pointer dereference on a badly formed
14568 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
14569 bugfix on 0.2.2.9-alpha.
14570 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
14571 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
14572 - Defensively refactor rend_mid_rendezvous() so that protocol
14573 violations and length checks happen in the beginning. Fixes
14575 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
14576 that IPv6 stuff will compile on MSVC, and compilation issues
14577 will be easier to track down. Fixes bug 5861.
14579 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
14580 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
14581 resource exhaustion, so that clients can adjust their load to
14582 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
14583 started using END_STREAM_REASON_RESOURCELIMIT.
14584 - Don't check for whether the address we're using for outbound
14585 connections has changed until after the outbound connection has
14586 completed. On Windows, getsockname() doesn't succeed until the
14587 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
14588 - If the configuration tries to set MyFamily on a bridge, refuse to
14589 do so, and warn about the security implications. Fixes bug 4657;
14590 bugfix on 0.2.0.3-alpha.
14591 - If the client fails to set a reasonable set of ciphersuites
14592 during its v2 handshake renegotiation, allow the renegotiation to
14593 continue nevertheless (i.e. send all the required certificates).
14594 Fixes bug 4591; bugfix on 0.2.0.20-rc.
14595 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
14596 option is set to 0 (which Vidalia version 0.2.16 now does when
14597 a SAVECONF attempt fails), perform other actions that SIGHUP
14598 usually causes (like reopening the logs). Fixes bug 5095; bugfix
14600 - If we fail to write a microdescriptor to the disk cache, do not
14601 continue replacing the old microdescriptor file. Fixes bug 2954;
14602 bugfix on 0.2.2.6-alpha.
14603 - Exit nodes don't need to fetch certificates for authorities that
14604 they don't recognize; only directory authorities, bridges,
14605 and caches need to do that. Fixes part of bug 2297; bugfix on
14607 - Correctly handle checking the permissions on the parent
14608 directory of a control socket in the root directory. Bug found
14609 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
14611 - When told to add a bridge with the same digest as a preexisting
14612 bridge but a different addr:port, change the addr:port as
14613 requested. Previously we would not notice the change. Fixes half
14614 of bug 5603; fix on 0.2.2.26-beta.
14615 - End AUTHCHALLENGE error messages (in the control protocol) with
14616 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
14618 o Minor bugfixes (on 0.2.3.x):
14619 - Turn an assertion (that the number of handshakes received as a
14620 server is not < 1) into a warning. Fixes bug 4873; bugfix on
14622 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
14623 we had reversed them when the answer was cached.) Fixes bug
14624 5723; bugfix on 0.2.3.1-alpha.
14625 - Work correctly on Linux systems with accept4 support advertised in
14626 their headers, but without accept4 support in the kernel. Fix
14627 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
14628 - When told to add a bridge with the same addr:port as a preexisting
14629 bridge but a different transport, change the transport as
14630 requested. Previously we would not notice the change. Fixes half
14631 of bug 5603; fix on 0.2.3.2-alpha.
14632 - Avoid a "double-reply" warning when replying to a SOCKS request
14633 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
14634 bugfix on 0.2.3.4-alpha.
14635 - Fix a bug where a bridge authority crashes if it has seen no
14636 directory requests when it's time to write statistics to disk.
14637 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
14639 - Don't try to open non-control listeners when DisableNetwork is set.
14640 Previously, we'd open all listeners, then immediately close them.
14641 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
14642 - Don't abort the managed proxy protocol if the managed proxy
14643 sends us an unrecognized line; ignore it instead. Fixes bug
14644 5910; bugfix on 0.2.3.9-alpha.
14645 - Fix a compile warning in crypto.c when compiling with clang 3.1.
14646 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
14647 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
14648 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
14649 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
14650 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
14651 - Resolve numerous small warnings and build issues with MSVC. Resolves
14654 o Documentation fixes:
14655 - Improve the manual's documentation for the NT Service command-line
14656 options. Addresses ticket 3964.
14657 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
14658 - Document the changes to the ORPort and DirPort options, and the
14659 fact that {OR/Dir}ListenAddress is now unnecessary (and
14660 therefore deprecated). Resolves ticket 5597.
14663 - Remove the torrc.bridge file: we don't use it for anything, and
14664 it had become badly desynchronized from torrc.sample. Resolves
14668 Changes in version 0.2.2.36 - 2012-05-24
14669 Tor 0.2.2.36 updates the addresses for two of the eight directory
14670 authorities, fixes some potential anonymity and security issues,
14671 and fixes several crash bugs.
14673 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
14674 known flaws, and nobody should be using them. You should upgrade. If
14675 you're using a Linux or BSD and its packages are obsolete, stop using
14676 those packages and upgrade anyway.
14678 o Directory authority changes:
14679 - Change IP address for maatuska (v3 directory authority).
14680 - Change IP address for ides (v3 directory authority), and rename
14684 - When building or running with any version of OpenSSL earlier
14685 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
14686 versions have a bug (CVE-2011-4576) in which their block cipher
14687 padding includes uninitialized data, potentially leaking sensitive
14688 information to any peer with whom they make a SSLv3 connection. Tor
14689 does not use SSL v3 by default, but a hostile client or server
14690 could force an SSLv3 connection in order to gain information that
14691 they shouldn't have been able to get. The best solution here is to
14692 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
14693 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
14694 to make sure that the bug can't happen.
14695 - Never use a bridge or a controller-supplied node as an exit, even
14696 if its exit policy allows it. Found by wanoskarnet. Fixes bug
14697 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
14698 and 0.2.0.3-alpha (for bridge-purpose descriptors).
14699 - Only build circuits if we have a sufficient threshold of the total
14700 descriptors that are marked in the consensus with the "Exit"
14701 flag. This mitigates an attack proposed by wanoskarnet, in which
14702 all of a client's bridges collude to restrict the exit nodes that
14703 the client knows about. Fixes bug 5343.
14704 - Provide controllers with a safer way to implement the cookie
14705 authentication mechanism. With the old method, if another locally
14706 running program could convince a controller that it was the Tor
14707 process, then that program could trick the controller into telling
14708 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
14709 authentication method uses a challenge-response approach to prevent
14710 this attack. Fixes bug 5185; implements proposal 193.
14713 - Avoid logging uninitialized data when unable to decode a hidden
14714 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
14715 - Avoid a client-side assertion failure when receiving an INTRODUCE2
14716 cell on a general purpose circuit. Fixes bug 5644; bugfix on
14718 - Fix builds when the path to sed, openssl, or sha1sum contains
14719 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
14721 - Correct our replacements for the timeradd() and timersub() functions
14722 on platforms that lack them (for example, Windows). The timersub()
14723 function is used when expiring circuits, while timeradd() is
14724 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
14725 bugfix on 0.2.2.24-alpha.
14726 - Fix the SOCKET_OK test that we use to tell when socket
14727 creation fails so that it works on Win64. Fixes part of bug 4533;
14728 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
14731 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
14732 Fixes bug 5346; bugfix on 0.0.8pre3.
14733 - Make our number-parsing functions always treat too-large values
14734 as an error, even when those values exceed the width of the
14735 underlying type. Previously, if the caller provided these
14736 functions with minima or maxima set to the extreme values of the
14737 underlying integer type, these functions would return those
14738 values on overflow rather than treating overflow as an error.
14739 Fixes part of bug 5786; bugfix on 0.0.9.
14740 - Older Linux kernels erroneously respond to strange nmap behavior
14741 by having accept() return successfully with a zero-length
14742 socket. When this happens, just close the connection. Previously,
14743 we would try harder to learn the remote address: but there was
14744 no such remote address to learn, and our method for trying to
14745 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
14746 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
14747 - Correct parsing of certain date types in parse_http_time().
14748 Without this patch, If-Modified-Since would behave
14749 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
14750 Esteban Manchado Velázques.
14751 - Change the BridgePassword feature (part of the "bridge community"
14752 design, which is not yet implemented) to use a time-independent
14753 comparison. The old behavior might have allowed an adversary
14754 to use timing to guess the BridgePassword value. Fixes bug 5543;
14755 bugfix on 0.2.0.14-alpha.
14756 - Detect and reject certain misformed escape sequences in
14757 configuration values. Previously, these values would cause us
14758 to crash if received in a torrc file or over an authenticated
14759 control port. Bug found by Esteban Manchado Velázquez, and
14760 independently by Robert Connolly from Matta Consulting who further
14761 noted that it allows a post-authentication heap overflow. Patch
14762 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
14763 bugfix on 0.2.0.16-alpha.
14764 - Fix a compile warning when using the --enable-openbsd-malloc
14765 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
14766 - During configure, detect when we're building with clang version
14767 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
14768 CFLAGS. clang doesn't support them yet.
14769 - When sending an HTTP/1.1 proxy request, include a Host header.
14770 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
14771 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
14772 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
14773 - If we hit the error case where routerlist_insert() replaces an
14774 existing (old) server descriptor, make sure to remove that
14775 server descriptor from the old_routers list. Fix related to bug
14776 1776. Bugfix on 0.2.2.18-alpha.
14778 o Minor bugfixes (documentation and log messages):
14779 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
14780 Fixes bug 4856; bugfix on Tor 0.0.6.
14781 - Update "ClientOnly" man page entry to explain that there isn't
14782 really any point to messing with it. Resolves ticket 5005.
14783 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
14784 directory authority option (introduced in Tor 0.2.2.34).
14785 - Downgrade the "We're missing a certificate" message from notice
14786 to info: people kept mistaking it for a real problem, whereas it
14787 is seldom the problem even when we are failing to bootstrap. Fixes
14788 bug 5067; bugfix on 0.2.0.10-alpha.
14789 - Correctly spell "connect" in a log message on failure to create a
14790 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
14791 - Clarify the behavior of MaxCircuitDirtiness with hidden service
14792 circuits. Fixes issue 5259.
14795 - Directory authorities now reject versions of Tor older than
14796 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
14797 inclusive. These versions accounted for only a small fraction of
14798 the Tor network, and have numerous known security issues. Resolves
14800 - Update to the May 1 2012 Maxmind GeoLite Country database.
14803 - When sending or relaying a RELAY_EARLY cell, we used to convert
14804 it to a RELAY cell if the connection was using the v1 link
14805 protocol. This was a workaround for older versions of Tor, which
14806 didn't handle RELAY_EARLY cells properly. Now that all supported
14807 versions can handle RELAY_EARLY cells, and now that we're enforcing
14808 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
14809 remove this workaround. Addresses bug 4786.
14812 Changes in version 0.2.3.15-alpha - 2012-04-30
14813 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
14814 the development branch build on Windows again.
14816 o Minor bugfixes (on 0.2.2.x and earlier):
14817 - Make sure that there are no unhandled pending TLS errors before
14818 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
14819 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
14820 Bugfix on 0.1.0.5-rc; fixes bug 4528.
14821 - Fix an assert that directory authorities could trigger on sighup
14822 during some configuration state transitions. We now don't treat
14823 it as a fatal error when the new descriptor we just generated in
14824 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
14825 - After we pick a directory mirror, we would refuse to use it if
14826 it's in our ExcludeExitNodes list, resulting in mysterious failures
14827 to bootstrap for people who just wanted to avoid exiting from
14828 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
14829 - When building with --enable-static-tor on OpenBSD, do not
14830 erroneously attempt to link -lrt. Fixes bug 5103.
14832 o Minor bugfixes (on 0.2.3.x):
14833 - When Tor is built with kernel headers from a recent (last few
14834 years) Linux kernel, do not fail to run on older (pre-2.6.28
14835 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
14836 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
14837 and 0.2.3.12-alpha.
14838 - Fix compilation with miniupnpc version 1.6; patch from
14839 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
14840 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
14841 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
14842 - Fix compilation on platforms without unistd.h, or where environ
14843 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
14846 - Directory authorities are now a little more lenient at accepting
14847 older router descriptors, or newer router descriptors that don't
14848 make big changes. This should help ameliorate past and future
14849 issues where routers think they have uploaded valid descriptors,
14850 but the authorities don't think so. Fix for ticket 2479.
14851 - Make the code that clients use to detect an address change be
14852 IPv6-aware, so that it won't fill clients' logs with error
14853 messages when trying to get the IPv4 address of an IPv6
14854 connection. Implements ticket 5537.
14856 o Removed features:
14857 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
14858 authorities needed to use it for a while to keep the network working
14859 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
14860 that was six months ago. As of now, it should no longer be needed
14864 Changes in version 0.2.3.14-alpha - 2012-04-23
14865 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
14866 candidate. It also dramatically speeds up AES: fast relays should
14867 consider switching to the newer OpenSSL library.
14869 o Directory authority changes:
14870 - Change IP address for ides (v3 directory authority), and rename
14874 - Avoid logging uninitialized data when unable to decode a hidden
14875 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
14876 - Avoid a client-side assertion failure when receiving an INTRODUCE2
14877 cell on a general purpose circuit. Fixes bug 5644; bugfix on
14879 - If authorities are unable to get a v2 consensus document from other
14880 directory authorities, they no longer fall back to fetching
14881 them from regular directory caches. Fixes bug 5635; bugfix on
14882 0.2.2.26-beta, where routers stopped downloading v2 consensus
14883 documents entirely.
14884 - When we start a Tor client with a normal consensus already cached,
14885 be willing to download a microdescriptor consensus. Fixes bug 4011;
14886 fix on 0.2.3.1-alpha.
14888 o Major features (performance):
14889 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
14890 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
14891 vectorized AES implementations as appropriate. These can be much,
14892 much faster than other AES implementations.
14894 o Minor bugfixes (0.2.2.x and earlier):
14895 - Don't launch more than 10 service-side introduction-point circuits
14896 for a hidden service in five minutes. Previously, we would consider
14897 launching more introduction-point circuits if at least one second
14898 had passed without any introduction-point circuits failing. Fixes
14899 bug 4607; bugfix on 0.0.7pre1.
14900 - Change the BridgePassword feature (part of the "bridge community"
14901 design, which is not yet implemented) to use a time-independent
14902 comparison. The old behavior might have allowed an adversary
14903 to use timing to guess the BridgePassword value. Fixes bug 5543;
14904 bugfix on 0.2.0.14-alpha.
14905 - Enforce correct return behavior of tor_vsscanf() when the '%%'
14906 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
14907 - When sending an HTTP/1.1 proxy request, include a Host header.
14908 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
14909 - Don't log that we have "decided to publish new relay descriptor"
14910 unless we are actually publishing a descriptor. Fixes bug 3942;
14911 bugfix on 0.2.2.28-beta.
14913 o Minor bugfixes (0.2.3.x):
14914 - Fix a bug where a bridge authority crashes (on a failed assert)
14915 if it has seen no directory requests when it's time to write
14916 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
14917 - Fix bug stomping on ORPort option NoListen and ignoring option
14918 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
14919 - In the testsuite, provide a large enough buffer in the tor_sscanf
14920 unit test. Otherwise we'd overrun that buffer and crash during
14921 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
14923 - Make sure we create the keys directory if it doesn't exist and we're
14924 about to store the dynamic Diffie-Hellman parameters. Fixes bug
14925 5572; bugfix on 0.2.3.13-alpha.
14926 - Fix a small memory leak when trying to decode incorrect base16
14927 authenticator during SAFECOOKIE authentication. Found by
14928 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
14931 - Add more information to a log statement that might help track down
14932 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
14933 non-IP address" messages (or any Bug messages, for that matter!),
14934 please let us know about it.
14935 - Relays now understand an IPv6 address when they get one from a
14936 directory server. Resolves ticket 4875.
14937 - Resolve IPv6 addresses in bridge and entry statistics to country
14938 code "??" which means we at least count them. Resolves ticket 5053;
14939 improves on 0.2.3.9-alpha.
14940 - Update to the April 3 2012 Maxmind GeoLite Country database.
14941 - Begin a doc/state-contents.txt file to explain the contents of
14942 the Tor state file. Fixes bug 2987.
14944 o Default torrc changes:
14945 - Stop listing "socksport 9050" in torrc.sample. We open a socks
14946 port on 9050 by default anyway, so this should not change anything
14948 - Stop mentioning the deprecated *ListenAddress options in
14949 torrc.sample. Fixes bug 5438.
14950 - Document unit of bandwidth related options in sample torrc.
14953 o Removed features:
14954 - The "torify" script no longer supports the "tsocks" socksifier
14955 tool, since tsocks doesn't support DNS and UDP right for Tor.
14956 Everyone should be using torsocks instead. Fixes bugs 3530 and
14957 5180. Based on a patch by "ugh".
14959 o Code refactoring:
14960 - Change the symmetric cipher interface so that creating and
14961 initializing a stream cipher are no longer separate functions.
14962 - Remove all internal support for unpadded RSA. We never used it, and
14963 it would be a bad idea to start.
14966 Changes in version 0.2.3.13-alpha - 2012-03-26
14967 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
14968 in managed pluggable transports, as well as providing other cleanups
14969 that get us closer to a release candidate.
14971 o Directory authority changes:
14972 - Change IP address for maatuska (v3 directory authority).
14975 - Provide controllers with a safer way to implement the cookie
14976 authentication mechanism. With the old method, if another locally
14977 running program could convince a controller that it was the Tor
14978 process, then that program could trick the controller into telling
14979 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
14980 authentication method uses a challenge-response approach to prevent
14981 this attack. Fixes bug 5185, implements proposal 193.
14982 - Never use a bridge or a controller-supplied node as an exit, even
14983 if its exit policy allows it. Found by wanoskarnet. Fixes bug
14984 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
14985 and 0.2.0.3-alpha (for bridge-purpose descriptors).
14986 - Only build circuits if we have a sufficient threshold of the total
14987 descriptors that are marked in the consensus with the "Exit"
14988 flag. This mitigates an attack proposed by wanoskarnet, in which
14989 all of a client's bridges collude to restrict the exit nodes that
14990 the client knows about. Fixes bug 5343.
14992 o Major bugfixes (on Tor 0.2.3.x):
14993 - Avoid an assert when managed proxies like obfsproxy are configured,
14994 and we receive HUP signals or setconf attempts too rapidly. This
14995 situation happens most commonly when Vidalia tries to attach to
14996 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
14997 bugfix on 0.2.3.6-alpha.
14998 - Fix a relay-side pluggable transports bug where managed proxies were
14999 unreachable from the Internet, because Tor asked them to bind on
15000 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
15001 - Stop discarding command-line arguments when TestingTorNetwork
15002 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
15003 0.2.3.9-alpha, where task 4552 added support for two layers of
15005 - Resume allowing the unit tests to run in gdb. This was accidentally
15006 made impossible when the DisableDebuggerAttachment option was
15007 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
15008 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
15009 0.2.3.11-alpha. Reported by Anthony G. Basile.
15011 o Minor bugfixes (on 0.2.2.x and earlier):
15012 - Ensure we don't cannibalize circuits that are longer than three hops
15013 already, so we don't end up making circuits with 5 or more
15014 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
15015 0.1.0.1-rc which introduced cannibalization.
15016 - Detect and reject certain misformed escape sequences in
15017 configuration values. Previously, these values would cause us
15018 to crash if received in a torrc file or over an authenticated
15019 control port. Bug found by Esteban Manchado Velázquez, and
15020 independently by Robert Connolly from Matta Consulting who further
15021 noted that it allows a post-authentication heap overflow. Patch
15022 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15023 bugfix on 0.2.0.16-alpha.
15024 - Fix a compile warning when using the --enable-openbsd-malloc
15025 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15026 - Directory caches no longer refuse to clean out descriptors because
15027 of missing v2 networkstatus documents, unless they're configured
15028 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
15029 0.2.2.26-beta. Patch by Daniel Bryg.
15030 - Update to the latest version of the tinytest unit testing framework.
15031 This includes a couple of bugfixes that can be relevant for
15032 running forked unit tests on Windows, and removes all reserved
15035 o Minor bugfixes (on 0.2.3.x):
15036 - On a failed pipe() call, don't leak file descriptors. Fixes bug
15037 4296; bugfix on 0.2.3.1-alpha.
15038 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
15039 until after we have received a CERTS cell. Fixes bug 4361; bugfix
15040 on 0.2.3.6-alpha. Patch by "frosty".
15041 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
15042 option, so that the IP stack doesn't decide to use it for IPv4
15043 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
15044 - Ensure that variables set in Tor's environment cannot override
15045 environment variables that Tor passes to a managed
15046 pluggable-transport proxy. Previously, Tor would pass every
15047 variable in its environment to managed proxies along with the new
15048 ones, in such a way that on many operating systems, the inherited
15049 environment variables would override those which Tor tried to
15050 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
15051 bugfix on 0.2.3.9-alpha for Windows.
15054 - A wide variety of new unit tests by Esteban Manchado Velázquez.
15055 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
15056 - Update to the March 6 2012 Maxmind GeoLite Country database.
15059 Changes in version 0.2.3.12-alpha - 2012-02-13
15060 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
15061 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
15062 when Tor is configured to use a pluggable transport like obfsproxy.
15065 - Fix builds when the path to sed, openssl, or sha1sum contains
15066 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15068 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
15069 connections. This change should allow busy exit relays to stop
15070 running out of available sockets as quickly. Fixes bug 4950;
15071 bugfix on 0.2.2.26-beta.
15072 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
15073 would ask the bridge for microdescriptors, which are only supported
15074 in 0.2.3.x, and then fail to bootstrap when it didn't get the
15075 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
15076 - Properly set up obfsproxy's environment when in managed mode. The
15077 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
15078 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
15079 5076 and 5082; bugfix on 0.2.3.6-alpha.
15082 - Use the dead_strip option when building Tor on OS X. This reduces
15083 binary size by almost 19% when linking openssl and libevent
15084 statically, which we do for Tor Browser Bundle.
15085 - Fix broken URLs in the sample torrc file, and tell readers about
15086 the OutboundBindAddress, ExitPolicyRejectPrivate, and
15087 PublishServerDescriptor options. Addresses bug 4652.
15088 - Update to the February 7 2012 Maxmind GeoLite Country database.
15091 - Downgrade the "We're missing a certificate" message from notice
15092 to info: people kept mistaking it for a real problem, whereas it
15093 is seldom the problem even when we are failing to bootstrap. Fixes
15094 bug 5067; bugfix on 0.2.0.10-alpha.
15095 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
15096 managed pluggable transport server proxy's environment.
15097 Previously, we would put it there, even though Tor doesn't
15098 implement an 'extended server port' yet, and even though Tor
15099 almost certainly isn't listening at that address. For now, we set
15100 it to an empty string to avoid crashing older obfsproxies. Bugfix
15102 - Log the heartbeat message every HeartbeatPeriod seconds, not every
15103 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
15104 0.2.3.1-alpha. Bug reported by Scott Bennett.
15105 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
15106 bugfix on 0.2.3.11-alpha.
15107 - Update "ClientOnly" man page entry to explain that there isn't
15108 really any point to messing with it. Resolves ticket 5005.
15109 - Use the correct CVE number for CVE-2011-4576 in our comments and
15110 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
15113 o Code simplifications and refactoring:
15114 - Use the _WIN32 macro throughout our code to detect Windows.
15115 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
15119 Changes in version 0.2.3.11-alpha - 2012-01-22
15120 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
15121 the last step of the plan to limit maximum circuit length, includes
15122 a wide variety of hidden service performance and correctness fixes,
15123 works around an OpenSSL security flaw if your distro is too stubborn
15124 to upgrade, and fixes a bunch of smaller issues.
15127 - Now that Tor 0.2.0.x is completely deprecated, enable the final
15128 part of "Proposal 110: Avoiding infinite length circuits" by
15129 refusing all circuit-extend requests that do not use a relay_early
15130 cell. This change helps Tor resist a class of denial-of-service
15131 attacks by limiting the maximum circuit length.
15132 - Adjust the number of introduction points that a hidden service
15133 will try to maintain based on how long its introduction points
15134 remain in use and how many introductions they handle. Fixes
15136 - Try to use system facilities for enumerating local interface
15137 addresses, before falling back to our old approach (which was
15138 binding a UDP socket, and calling getsockname() on it). That
15139 approach was scaring OS X users whose draconian firewall
15140 software warned about binding to UDP sockets, regardless of
15141 whether packets were sent. Now we try to use getifaddrs(),
15142 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
15143 system supports. Resolves ticket 1827.
15145 o Major security workaround:
15146 - When building or running with any version of OpenSSL earlier
15147 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15148 versions have a bug (CVE-2011-4576) in which their block cipher
15149 padding includes uninitialized data, potentially leaking sensitive
15150 information to any peer with whom they make a SSLv3 connection. Tor
15151 does not use SSL v3 by default, but a hostile client or server
15152 could force an SSLv3 connection in order to gain information that
15153 they shouldn't have been able to get. The best solution here is to
15154 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15155 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15156 to make sure that the bug can't happen.
15159 - Fix the SOCKET_OK test that we use to tell when socket
15160 creation fails so that it works on Win64. Fixes part of bug 4533;
15161 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15162 - Correct our replacements for the timeradd() and timersub() functions
15163 on platforms that lack them (for example, Windows). The timersub()
15164 function is used when expiring circuits, while timeradd() is
15165 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15166 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
15167 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
15168 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
15169 bug at runtime, not compile time, because some distributions hack
15170 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
15171 on 0.2.3.9-alpha. Found by Pascal.
15173 o Minor features (controller):
15174 - Use absolute path names when reporting the torrc filename in the
15175 control protocol, so a controller can more easily find the torrc
15176 file. Resolves bug 1101.
15177 - Extend the control protocol to report flags that control a circuit's
15178 path selection in CIRC events and in replies to 'GETINFO
15179 circuit-status'. Implements part of ticket 2411.
15180 - Extend the control protocol to report the hidden service address
15181 and current state of a hidden-service-related circuit in CIRC
15182 events and in replies to 'GETINFO circuit-status'. Implements part
15184 - When reporting the path to the cookie file to the controller,
15185 give an absolute path. Resolves ticket 4881.
15186 - Allow controllers to request an event notification whenever a
15187 circuit is cannibalized or its purpose is changed. Implements
15188 part of ticket 3457.
15189 - Include the creation time of a circuit in CIRC and CIRC2
15190 control-port events and the list produced by the 'GETINFO
15191 circuit-status' control-port command.
15193 o Minor features (directory authorities):
15194 - Directory authorities now reject versions of Tor older than
15195 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15196 inclusive. These versions accounted for only a small fraction of
15197 the Tor network, and have numerous known security issues. Resolves
15199 - Authority operators can now vote for all relays in a given
15200 set of countries to be BadDir/BadExit/Invalid/Rejected.
15201 - Provide two consensus parameters (FastFlagMinThreshold and
15202 FastFlagMaxThreshold) to control the range of allowable bandwidths
15203 for the Fast directory flag. These allow authorities to run
15204 experiments on appropriate requirements for being a "Fast" node.
15205 The AuthDirFastGuarantee config value still applies. Implements
15207 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15208 directory authority option (introduced in Tor 0.2.2.34).
15210 o Minor features (other):
15211 - Don't disable the DirPort when we cannot exceed our AccountingMax
15212 limit during this interval because the effective bandwidthrate is
15213 low enough. This is useful in a situation where AccountMax is only
15214 used as an additional safeguard or to provide statistics.
15215 - Prepend an informative header to generated dynamic_dh_params files.
15216 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
15217 EntryNodes will have no effect. Resolves issue 2571.
15218 - Log more useful messages when we fail to disable debugger
15220 - Log which authority we're missing votes from when we go to fetch
15221 them from the other auths.
15222 - Log (at debug level) whenever a circuit's purpose is changed.
15223 - Add missing documentation for the MaxClientCircuitsPending,
15224 UseMicrodescriptors, UserspaceIOCPBuffers, and
15225 _UseFilteringSSLBufferevents options, all introduced during
15226 the 0.2.3.x series.
15227 - Update to the January 3 2012 Maxmind GeoLite Country database.
15229 o Minor bugfixes (hidden services):
15230 - Don't close hidden service client circuits which have almost
15231 finished connecting to their destination when they reach
15232 the normal circuit-build timeout. Previously, we would close
15233 introduction circuits which are waiting for an acknowledgement
15234 from the introduction point, and rendezvous circuits which have
15235 been specified in an INTRODUCE1 cell sent to a hidden service,
15236 after the normal CBT. Now, we mark them as 'timed out', and launch
15237 another rendezvous attempt in parallel. This behavior change can
15238 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
15239 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
15240 - Don't close hidden-service-side rendezvous circuits when they
15241 reach the normal circuit-build timeout. This behavior change can
15242 be disabled using the new
15243 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
15244 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
15245 - Make sure we never mark the wrong rendezvous circuit as having
15246 had its introduction cell acknowledged by the introduction-point
15247 relay. Previously, when we received an INTRODUCE_ACK cell on a
15248 client-side hidden-service introduction circuit, we might have
15249 marked a rendezvous circuit other than the one we specified in
15250 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
15251 a warning message and interfered with the hidden service
15252 connection-establishment process. Fixes bug 4759; bugfix on
15253 0.2.3.3-alpha, when we added the stream-isolation feature which
15254 might cause Tor to open multiple rendezvous circuits for the same
15256 - Don't trigger an assertion failure when we mark a new client-side
15257 hidden-service introduction circuit for close during the process
15258 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
15261 o Minor bugfixes (log messages):
15262 - Correctly spell "connect" in a log message on failure to create a
15263 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
15265 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15266 Fixes bug 4856; bugfix on Tor 0.0.6.
15267 - Fix the log message describing how we work around discovering
15268 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
15269 4837; bugfix on 0.2.2.9-alpha.
15270 - When logging about a disallowed .exit name, do not also call it
15271 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
15273 o Minor bugfixes (build fixes):
15274 - During configure, detect when we're building with clang version
15275 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15276 CFLAGS. clang doesn't support them yet.
15277 - During configure, search for library containing cos function as
15278 libm lives in libcore on some platforms (BeOS/Haiku). Linking
15279 against libm was hard-coded before. Fixes the first part of bug
15280 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
15282 - Detect attempts to build Tor on (as yet hypothetical) versions
15283 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
15284 fix for bug 4533. Bugfix on 0.2.2.28-beta.
15285 - Preprocessor directives should not be put inside the arguments
15286 of a macro. This would break compilation with GCC releases prior
15287 to version 3.3. We would never recommend such an old GCC version,
15288 but it is apparently required for binary compatibility on some
15289 platforms (namely, certain builds of Haiku). Fixes the other part
15290 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
15293 o Minor bugfixes (other):
15294 - Older Linux kernels erroneously respond to strange nmap behavior
15295 by having accept() return successfully with a zero-length
15296 socket. When this happens, just close the connection. Previously,
15297 we would try harder to learn the remote address: but there was
15298 no such remote address to learn, and our method for trying to
15299 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15300 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15301 - Fix null-pointer access that could occur if TLS allocation failed.
15302 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
15303 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
15304 accidentally been reverted.
15305 - Fix our implementation of crypto_random_hostname() so it can't
15306 overflow on ridiculously large inputs. (No Tor version has ever
15307 provided this kind of bad inputs, but let's be correct in depth.)
15308 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
15309 - Find more places in the code that should have been testing for
15310 invalid sockets using the SOCKET_OK macro. Required for a fix
15311 for bug 4533. Bugfix on 0.2.2.28-beta.
15312 - Fix an assertion failure when, while running with bufferevents, a
15313 connection finishes connecting after it is marked for close, but
15314 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
15315 - test_util_spawn_background_ok() hardcoded the expected value
15316 for ENOENT to 2. This isn't portable as error numbers are
15317 platform specific, and particularly the hurd has ENOENT at
15318 0x40000002. Construct expected string at runtime, using the correct
15319 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
15320 - Reject attempts to disable DisableDebuggerAttachment while Tor is
15321 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
15322 - Use an appropriate-width type for sockets in tor-fw-helper on
15323 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
15326 - When sending or relaying a RELAY_EARLY cell, we used to convert
15327 it to a RELAY cell if the connection was using the v1 link
15328 protocol. This was a workaround for older versions of Tor, which
15329 didn't handle RELAY_EARLY cells properly. Now that all supported
15330 versions can handle RELAY_EARLY cells, and now that we're enforcing
15331 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
15332 remove this workaround. Addresses bug 4786.
15334 o Code simplifications and refactoring:
15335 - Use OpenSSL's built-in SSL_state_string_long() instead of our
15336 own homebrewed ssl_state_to_string() replacement. Patch from
15337 Emile Snyder. Fixes bug 4653.
15338 - Use macros to indicate OpenSSL versions, so we don't need to worry
15339 about accidental hexadecimal bit shifts.
15340 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
15342 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
15343 - Use the smartlist_add_asprintf() alias more consistently.
15344 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
15345 invalid value, rather than just -1.
15346 - Rename a handful of old identifiers, mostly related to crypto
15347 structures and crypto functions. By convention, our "create an
15348 object" functions are called "type_new()", our "free an object"
15349 functions are called "type_free()", and our types indicate that
15350 they are types only with a final "_t". But a handful of older
15351 types and functions broke these rules, with function names like
15352 "type_create" or "subsystem_op_type", or with type names like
15356 Changes in version 0.2.3.10-alpha - 2011-12-16
15357 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
15358 Tor's buffers code. Absolutely everybody should upgrade.
15360 The bug relied on an incorrect calculation when making data continuous
15361 in one of our IO buffers, if the first chunk of the buffer was
15362 misaligned by just the wrong amount. The miscalculation would allow an
15363 attacker to overflow a piece of heap-allocated memory. To mount this
15364 attack, the attacker would need to either open a SOCKS connection to
15365 Tor's SocksPort (usually restricted to localhost), or target a Tor
15366 instance configured to make its connections through a SOCKS proxy
15367 (which Tor does not do by default).
15369 Good security practice requires that all heap-overflow bugs should be
15370 presumed to be exploitable until proven otherwise, so we are treating
15371 this as a potential code execution attack. Please upgrade immediately!
15372 This bug does not affect bufferevents-based builds of Tor. Special
15373 thanks to "Vektor" for reporting this issue to us!
15375 This release also contains a few minor bugfixes for issues discovered
15379 - Fix a heap overflow bug that could occur when trying to pull
15380 data into the first chunk of a buffer, when that chunk had
15381 already had some data drained from it. Fixes CVE-2011-2778;
15382 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15385 - If we can't attach streams to a rendezvous circuit when we
15386 finish connecting to a hidden service, clear the rendezvous
15387 circuit's stream-isolation state and try to attach streams
15388 again. Previously, we cleared rendezvous circuits' isolation
15389 state either too early (if they were freshly built) or not at all
15390 (if they had been built earlier and were cannibalized). Bugfix on
15391 0.2.3.3-alpha; fixes bug 4655.
15392 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
15393 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
15394 - Fix an assertion failure when a relay with accounting enabled
15395 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
15398 - Update to the December 6 2011 Maxmind GeoLite Country database.
15401 Changes in version 0.2.2.35 - 2011-12-16
15402 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
15403 buffers code. Absolutely everybody should upgrade.
15405 The bug relied on an incorrect calculation when making data continuous
15406 in one of our IO buffers, if the first chunk of the buffer was
15407 misaligned by just the wrong amount. The miscalculation would allow an
15408 attacker to overflow a piece of heap-allocated memory. To mount this
15409 attack, the attacker would need to either open a SOCKS connection to
15410 Tor's SocksPort (usually restricted to localhost), or target a Tor
15411 instance configured to make its connections through a SOCKS proxy
15412 (which Tor does not do by default).
15414 Good security practice requires that all heap-overflow bugs should be
15415 presumed to be exploitable until proven otherwise, so we are treating
15416 this as a potential code execution attack. Please upgrade immediately!
15417 This bug does not affect bufferevents-based builds of Tor. Special
15418 thanks to "Vektor" for reporting this issue to us!
15420 Tor 0.2.2.35 also fixes several bugs in previous versions, including
15421 crash bugs for unusual configurations, and a long-term bug that
15422 would prevent Tor from starting on Windows machines with draconian
15425 With this release, we remind everyone that 0.2.0.x has reached its
15426 formal end-of-life. Those Tor versions have many known flaws, and
15427 nobody should be using them. You should upgrade -- ideally to the
15428 0.2.2.x series. If you're using a Linux or BSD and its packages are
15429 obsolete, stop using those packages and upgrade anyway.
15431 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
15432 longer receive support after some time in early 2012.
15435 - Fix a heap overflow bug that could occur when trying to pull
15436 data into the first chunk of a buffer, when that chunk had
15437 already had some data drained from it. Fixes CVE-2011-2778;
15438 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15439 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
15440 that it doesn't attempt to allocate a socketpair. This could cause
15441 some problems on Windows systems with overzealous firewalls. Fix for
15442 bug 4457; workaround for Libevent versions 2.0.1-alpha through
15444 - If we mark an OR connection for close based on a cell we process,
15445 don't process any further cells on it. We already avoid further
15446 reads on marked-for-close connections, but now we also discard the
15447 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
15448 which was the first version where we might mark a connection for
15449 close based on processing a cell on it.
15450 - Correctly sanity-check that we don't underflow on a memory
15451 allocation (and then assert) for hidden service introduction
15452 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
15453 bugfix on 0.2.1.5-alpha.
15454 - Fix a memory leak when we check whether a hidden service
15455 descriptor has any usable introduction points left. Fixes bug
15456 4424. Bugfix on 0.2.2.25-alpha.
15457 - Don't crash when we're running as a relay and don't have a GeoIP
15458 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
15459 we've had in the 0.2.3.x branch already.
15460 - When running as a client, do not print a misleading (and plain
15461 wrong) log message that we're collecting "directory request"
15462 statistics: clients don't collect statistics. Also don't create a
15463 useless (because empty) stats file in the stats/ directory. Fixes
15464 bug 4353; bugfix on 0.2.2.34.
15467 - Detect failure to initialize Libevent. This fix provides better
15468 detection for future instances of bug 4457.
15469 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
15470 function. This was eating up hideously large amounts of time on some
15471 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
15472 - Resolve an integer overflow bug in smartlist_ensure_capacity().
15473 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
15475 - Don't warn about unused log_mutex in log.c when building with
15476 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
15477 0.1.0.6-rc which introduced --disable-threads.
15478 - When configuring, starting, or stopping an NT service, stop
15479 immediately after the service configuration attempt has succeeded
15480 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
15481 - When sending a NETINFO cell, include the original address
15482 received for the other side, not its canonical address. Found
15483 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
15484 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
15485 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
15486 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
15487 occurred when a client tried to fetch a descriptor for a bridge
15488 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
15489 - Backport fixes for a pair of compilation warnings on Windows.
15490 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
15491 - If we had ever tried to call tor_addr_to_str on an address of
15492 unknown type, we would have done a strdup on an uninitialized
15493 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
15494 Reported by "troll_un".
15495 - Correctly detect and handle transient lookup failures from
15496 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
15497 Reported by "troll_un".
15498 - Fix null-pointer access that could occur if TLS allocation failed.
15499 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
15500 - Use tor_socket_t type for listener argument to accept(). Fixes bug
15501 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
15504 - Add two new config options for directory authorities:
15505 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
15506 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
15507 that is always sufficient to satisfy the bandwidth requirement for
15508 the Guard flag. Now it will be easier for researchers to simulate
15509 Tor networks with different values. Resolves ticket 4484.
15510 - When Tor ignores a hidden service specified in its configuration,
15511 include the hidden service's directory in the warning message.
15512 Previously, we would only tell the user that some hidden service
15513 was ignored. Bugfix on 0.0.6; fixes bug 4426.
15514 - Update to the December 6 2011 Maxmind GeoLite Country database.
15516 o Packaging changes:
15517 - Make it easier to automate expert package builds on Windows,
15518 by removing an absolute path from makensis.exe command.
15521 Changes in version 0.2.1.32 - 2011-12-16
15522 Tor 0.2.1.32 backports important security and privacy fixes for
15523 oldstable. This release is intended only for package maintainers and
15524 others who cannot use the 0.2.2 stable series. All others should be
15525 using Tor 0.2.2.x or newer.
15527 The Tor 0.2.1.x series will reach formal end-of-life some time in
15528 early 2012; we will stop releasing patches for it then.
15530 o Major bugfixes (also included in 0.2.2.x):
15531 - Correctly sanity-check that we don't underflow on a memory
15532 allocation (and then assert) for hidden service introduction
15533 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
15534 bugfix on 0.2.1.5-alpha.
15535 - Fix a heap overflow bug that could occur when trying to pull
15536 data into the first chunk of a buffer, when that chunk had
15537 already had some data drained from it. Fixes CVE-2011-2778;
15538 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15541 - Update to the December 6 2011 Maxmind GeoLite Country database.
15544 Changes in version 0.2.3.9-alpha - 2011-12-08
15545 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
15546 a "DisableNetwork" security feature that bundles can use to avoid
15547 touching the network until bridges are configured, moves forward on
15548 the pluggable transport design, fixes a flaw in the hidden service
15549 design that unnecessarily prevented clients with wrong clocks from
15550 reaching hidden services, and fixes a wide variety of other issues.
15553 - Clients can now connect to private bridges over IPv6. Bridges
15554 still need at least one IPv4 address in order to connect to
15555 other relays. Note that we don't yet handle the case where the
15556 user has two bridge lines for the same bridge (one IPv4, one
15557 IPv6). Implements parts of proposal 186.
15558 - New "DisableNetwork" config option to prevent Tor from launching any
15559 connections or accepting any connections except on a control port.
15560 Bundles and controllers can set this option before letting Tor talk
15561 to the rest of the network, for example to prevent any connections
15562 to a non-bridge address. Packages like Orbot can also use this
15563 option to instruct Tor to save power when the network is off.
15564 - Clients and bridges can now be configured to use a separate
15565 "transport" proxy. This approach makes the censorship arms race
15566 easier by allowing bridges to use protocol obfuscation plugins. It
15567 implements the "managed proxy" part of proposal 180 (ticket 3472).
15568 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
15569 implementation. It makes AES_CTR about 7% faster than our old one
15570 (which was about 10% faster than the one OpenSSL used to provide).
15571 Resolves ticket 4526.
15572 - Add a "tor2web mode" for clients that want to connect to hidden
15573 services non-anonymously (and possibly more quickly). As a safety
15574 measure to try to keep users from turning this on without knowing
15575 what they are doing, tor2web mode must be explicitly enabled at
15576 compile time, and a copy of Tor compiled to run in tor2web mode
15577 cannot be used as a normal Tor client. Implements feature 2553.
15578 - Add experimental support for running on Windows with IOCP and no
15579 kernel-space socket buffers. This feature is controlled by a new
15580 "UserspaceIOCPBuffers" config option (off by default), which has
15581 no effect unless Tor has been built with support for bufferevents,
15582 is running on Windows, and has enabled IOCP. This may, in the long
15583 run, help solve or mitigate bug 98.
15584 - Use a more secure consensus parameter voting algorithm. Now at
15585 least three directory authorities or a majority of them must
15586 vote on a given parameter before it will be included in the
15587 consensus. Implements proposal 178.
15590 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
15591 They used to check that the timestamp was within 30 minutes
15592 of their system clock, so they could cap the size of their
15593 replay-detection cache, but that approach unnecessarily refused
15594 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
15595 the v3 intro-point protocol (the first one which sent a timestamp
15596 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
15597 - Only use the EVP interface when AES acceleration is enabled,
15598 to avoid a 5-7% performance regression. Resolves issue 4525;
15599 bugfix on 0.2.3.8-alpha.
15601 o Privacy/anonymity features (bridge detection):
15602 - Make bridge SSL certificates a bit more stealthy by using random
15603 serial numbers, in the same fashion as OpenSSL when generating
15604 self-signed certificates. Implements ticket 4584.
15605 - Introduce a new config option "DynamicDHGroups", enabled by
15606 default, which provides each bridge with a unique prime DH modulus
15607 to be used during SSL handshakes. This option attempts to help
15608 against censors who might use the Apache DH modulus as a static
15609 identifier for bridges. Addresses ticket 4548.
15611 o Minor features (new/different config options):
15612 - New configuration option "DisableDebuggerAttachment" (on by default)
15613 to prevent basic debugging attachment attempts by other processes.
15614 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
15615 - Allow MapAddress directives to specify matches against super-domains,
15616 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
15617 Implements issue 933.
15618 - Slightly change behavior of "list" options (that is, config
15619 options that can appear more than once) when they appear both in
15620 torrc and on the command line. Previously, the command-line options
15621 would be appended to the ones from torrc. Now, the command-line
15622 options override the torrc options entirely. This new behavior
15623 allows the user to override list options (like exit policies and
15624 ports to listen on) from the command line, rather than simply
15625 appending to the list.
15626 - You can get the old (appending) command-line behavior for "list"
15627 options by prefixing the option name with a "+".
15628 - You can remove all the values for a "list" option from the command
15629 line without adding any new ones by prefixing the option name
15631 - Add experimental support for a "defaults" torrc file to be parsed
15632 before the regular torrc. Torrc options override the defaults file's
15633 options in the same way that the command line overrides the torrc.
15634 The SAVECONF controller command saves only those options which
15635 differ between the current configuration and the defaults file. HUP
15636 reloads both files. (Note: This is an experimental feature; its
15637 behavior will probably be refined in future 0.2.3.x-alpha versions
15638 to better meet packagers' needs.) Implements task 4552.
15641 - Try to make the introductory warning message that Tor prints on
15642 startup more useful for actually finding help and information.
15643 Resolves ticket 2474.
15644 - Running "make version" now displays the version of Tor that
15645 we're about to build. Idea from katmagic; resolves issue 4400.
15646 - Expire old or over-used hidden service introduction points.
15647 Required by fix for bug 3460.
15648 - Move the replay-detection cache for the RSA-encrypted parts of
15649 INTRODUCE2 cells to the introduction point data structures.
15650 Previously, we would use one replay-detection cache per hidden
15651 service. Required by fix for bug 3460.
15652 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
15653 public key replay-detection cache from 60 minutes to 5 minutes. This
15654 replay-detection cache is now used only to detect multiple
15655 INTRODUCE2 cells specifying the same rendezvous point, so we can
15656 avoid launching multiple simultaneous attempts to connect to it.
15658 o Minor bugfixes (on Tor 0.2.2.x and earlier):
15659 - Resolve an integer overflow bug in smartlist_ensure_capacity().
15660 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
15662 - Fix a minor formatting issue in one of tor-gencert's error messages.
15664 - Prevent a false positive from the check-spaces script, by disabling
15665 the "whitespace between function name and (" check for functions
15667 - Fix a log message suggesting that people contact a non-existent
15668 email address. Fixes bug 3448.
15669 - Fix null-pointer access that could occur if TLS allocation failed.
15670 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
15671 - Report a real bootstrap problem to the controller on router
15672 identity mismatch. Previously we just said "foo", which probably
15673 made a lot of sense at the time. Fixes bug 4169; bugfix on
15675 - If we had ever tried to call tor_addr_to_str() on an address of
15676 unknown type, we would have done a strdup() on an uninitialized
15677 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
15678 Reported by "troll_un".
15679 - Correctly detect and handle transient lookup failures from
15680 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
15681 Reported by "troll_un".
15682 - Use tor_socket_t type for listener argument to accept(). Fixes bug
15683 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
15684 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
15685 bug 4532; found by "troll_un".
15687 o Minor bugfixes (on Tor 0.2.3.x):
15688 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
15690 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
15691 circuit for use as a hidden service client's rendezvous point.
15692 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
15693 with help from wanoskarnet.
15694 - Restore behavior of overriding SocksPort, ORPort, and similar
15695 options from the command line. Bugfix on 0.2.3.3-alpha.
15698 - Properly handle the case where the build-tree is not the same
15699 as the source tree when generating src/common/common_sha1.i,
15700 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
15701 bugfix on 0.2.0.1-alpha.
15703 o Code simplifications, cleanups, and refactorings:
15704 - Remove the pure attribute from all functions that used it
15705 previously. In many cases we assigned it incorrectly, because the
15706 functions might assert or call impure functions, and we don't have
15707 evidence that keeping the pure attribute is worthwhile. Implements
15708 changes suggested in ticket 4421.
15709 - Remove some dead code spotted by coverity. Fixes cid 432.
15710 Bugfix on 0.2.3.1-alpha, closes bug 4637.
15713 Changes in version 0.2.3.8-alpha - 2011-11-22
15714 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
15715 socketpair-related bug that has been bothering Windows users. It adds
15716 support to serve microdescriptors to controllers, so Vidalia's network
15717 map can resume listing relays (once Vidalia implements its side),
15718 and adds better support for hardware AES acceleration. Finally, it
15719 starts the process of adjusting the bandwidth cutoff for getting the
15720 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
15721 that tiny relays harm performance more than they help network capacity.
15724 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
15725 that it doesn't attempt to allocate a socketpair. This could cause
15726 some problems on Windows systems with overzealous firewalls. Fix for
15727 bug 4457; workaround for Libevent versions 2.0.1-alpha through
15729 - Correctly sanity-check that we don't underflow on a memory
15730 allocation (and then assert) for hidden service introduction
15731 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
15732 bugfix on 0.2.1.5-alpha.
15733 - Remove the artificially low cutoff of 20KB to guarantee the Fast
15734 flag. In the past few years the average relay speed has picked
15735 up, and while the "top 7/8 of the network get the Fast flag" and
15736 "all relays with 20KB or more of capacity get the Fast flag" rules
15737 used to have the same result, now the top 7/8 of the network has
15738 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
15739 - Fix a rare assertion failure when checking whether a v0 hidden
15740 service descriptor has any usable introduction points left, and
15741 we don't have enough information to build a circuit to the first
15742 intro point named in the descriptor. The HS client code in
15743 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
15744 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
15745 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
15746 - Make bridge authorities not crash when they are asked for their own
15747 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
15748 - When running as a client, do not print a misleading (and plain
15749 wrong) log message that we're collecting "directory request"
15750 statistics: clients don't collect statistics. Also don't create a
15751 useless (because empty) stats file in the stats/ directory. Fixes
15752 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
15755 - Allow Tor controllers like Vidalia to obtain the microdescriptor
15756 for a relay by identity digest or nickname. Previously,
15757 microdescriptors were only available by their own digests, so a
15758 controller would have to ask for and parse the whole microdescriptor
15759 consensus in order to look up a single relay's microdesc. Fixes
15760 bug 3832; bugfix on 0.2.3.1-alpha.
15761 - Use OpenSSL's EVP interface for AES encryption, so that all AES
15762 operations can use hardware acceleration (if present). Resolves
15765 o Minor bugfixes (on 0.2.2.x and earlier):
15766 - Detect failure to initialize Libevent. This fix provides better
15767 detection for future instances of bug 4457.
15768 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
15769 function. This was eating up hideously large amounts of time on some
15770 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
15771 - Don't warn about unused log_mutex in log.c when building with
15772 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
15773 0.1.0.6-rc which introduced --disable-threads.
15774 - Allow manual 'authenticate' commands to the controller interface
15775 from netcat (nc) as well as telnet. We were rejecting them because
15776 they didn't come with the expected whitespace at the end of the
15777 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
15778 - Fix some (not actually triggerable) buffer size checks in usage of
15779 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
15781 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
15782 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
15783 - When configuring, starting, or stopping an NT service, stop
15784 immediately after the service configuration attempt has succeeded
15785 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
15786 - When sending a NETINFO cell, include the original address
15787 received for the other side, not its canonical address. Found
15788 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
15789 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
15790 can pick them up when the tests aren't disabled. Bugfix on
15791 0.2.2.4-alpha which introduced tinytest.
15792 - Fix a memory leak when we check whether a hidden service
15793 descriptor has any usable introduction points left. Fixes bug
15794 4424. Bugfix on 0.2.2.25-alpha.
15795 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
15796 occurred when a client tried to fetch a descriptor for a bridge
15797 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
15799 o Minor bugfixes (on 0.2.3.x):
15800 - Make util unit tests build correctly with MSVC. Bugfix on
15801 0.2.3.3-alpha. Patch by Gisle Vanem.
15802 - Successfully detect AUTH_CHALLENGE cells with no recognized
15803 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
15804 Found by frosty_un.
15805 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
15806 it should still send a NETINFO cell to allow the connection to
15807 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
15809 - Log less loudly when we get an invalid authentication certificate
15810 from a source other than a directory authority: it's not unusual
15811 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
15813 - Tolerate servers with more clock skew in their authentication
15814 certificates than previously. Fixes bug 4371; bugfix on
15816 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
15817 on 0.2.3.4-alpha and 0.2.3.6-alpha.
15820 - Add two new config options for directory authorities:
15821 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
15822 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
15823 that is always sufficient to satisfy the bandwidth requirement for
15824 the Guard flag. Now it will be easier for researchers to simulate
15825 Tor networks with different values. Resolves ticket 4484.
15826 - When Tor ignores a hidden service specified in its configuration,
15827 include the hidden service's directory in the warning message.
15828 Previously, we would only tell the user that some hidden service
15829 was ignored. Bugfix on 0.0.6; fixes bug 4426.
15830 - When we fail to initialize Libevent, retry with IOCP disabled so we
15831 don't need to turn on multi-threading support in Libevent, which in
15832 turn requires a working socketpair(). This is a workaround for bug
15833 4457, which affects Libevent versions from 2.0.1-alpha through
15835 - Detect when we try to build on a platform that doesn't define
15836 AF_UNSPEC to 0. We don't work there, so refuse to compile.
15837 - Update to the November 1 2011 Maxmind GeoLite Country database.
15839 o Packaging changes:
15840 - Make it easier to automate expert package builds on Windows,
15841 by removing an absolute path from makensis.exe command.
15843 o Code simplifications and refactoring:
15844 - Remove some redundant #include directives throughout the code.
15845 Patch from Andrea Gelmini.
15846 - Unconditionally use OpenSSL's AES implementation instead of our
15847 old built-in one. OpenSSL's AES has been better for a while, and
15848 relatively few servers should still be on any version of OpenSSL
15849 that doesn't have good optimized assembly AES.
15850 - Use the name "CERTS" consistently to refer to the new cell type;
15851 we were calling it CERT in some places and CERTS in others.
15854 - Numerous new unit tests for functions in util.c and address.c by
15856 - The long-disabled benchmark tests are now split into their own
15857 ./src/test/bench binary.
15858 - The benchmark tests can now use more accurate timers than
15859 gettimeofday() when such timers are available.
15862 Changes in version 0.2.3.7-alpha - 2011-10-30
15863 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
15864 the new v3 handshake. It also resolves yet another bridge address
15868 - If we mark an OR connection for close based on a cell we process,
15869 don't process any further cells on it. We already avoid further
15870 reads on marked-for-close connections, but now we also discard the
15871 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
15872 which was the first version where we might mark a connection for
15873 close based on processing a cell on it.
15874 - Fix a double-free bug that would occur when we received an invalid
15875 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
15876 bugfix on 0.2.3.6-alpha.
15877 - Bridges no longer include their address in NETINFO cells on outgoing
15878 OR connections, to allow them to blend in better with clients.
15879 Removes another avenue for enumerating bridges. Reported by
15880 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
15881 cells were introduced.
15884 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
15885 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
15888 Changes in version 0.2.3.6-alpha - 2011-10-26
15889 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
15890 anonymity vulnerability where an attacker can deanonymize Tor
15891 users. Everybody should upgrade.
15893 This release also features support for a new v3 connection handshake
15894 protocol, and fixes to make hidden service connections more robust.
15897 - Implement a new handshake protocol (v3) for authenticating Tors to
15898 each other over TLS. It should be more resistant to fingerprinting
15899 than previous protocols, and should require less TLS hacking for
15900 future Tor implementations. Implements proposal 176.
15901 - Allow variable-length padding cells to disguise the length of
15902 Tor's TLS records. Implements part of proposal 184.
15904 o Privacy/anonymity fixes (clients):
15905 - Clients and bridges no longer send TLS certificate chains on
15906 outgoing OR connections. Previously, each client or bridge would
15907 use the same cert chain for all outgoing OR connections until
15908 its IP address changes, which allowed any relay that the client
15909 or bridge contacted to determine which entry guards it is using.
15910 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
15911 - If a relay receives a CREATE_FAST cell on a TLS connection, it
15912 no longer considers that connection as suitable for satisfying a
15913 circuit EXTEND request. Now relays can protect clients from the
15914 CVE-2011-2768 issue even if the clients haven't upgraded yet.
15915 - Directory authorities no longer assign the Guard flag to relays
15916 that haven't upgraded to the above "refuse EXTEND requests
15917 to client connections" fix. Now directory authorities can
15918 protect clients from the CVE-2011-2768 issue even if neither
15919 the clients nor the relays have upgraded yet. There's a new
15920 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
15921 to let us transition smoothly, else tomorrow there would be no
15924 o Major bugfixes (hidden services):
15925 - Improve hidden service robustness: when an attempt to connect to
15926 a hidden service ends, be willing to refetch its hidden service
15927 descriptors from each of the HSDir relays responsible for them
15928 immediately. Previously, we would not consider refetching the
15929 service's descriptors from each HSDir for 15 minutes after the last
15930 fetch, which was inconvenient if the hidden service was not running
15931 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
15932 - When one of a hidden service's introduction points appears to be
15933 unreachable, stop trying it. Previously, we would keep trying
15934 to build circuits to the introduction point until we lost the
15935 descriptor, usually because the user gave up and restarted Tor.
15936 Partly fixes bug 3825.
15937 - Don't launch a useless circuit after failing to use one of a
15938 hidden service's introduction points. Previously, we would
15939 launch a new introduction circuit, but not set the hidden service
15940 which that circuit was intended to connect to, so it would never
15941 actually be used. A different piece of code would then create a
15942 new introduction circuit correctly. Bug reported by katmagic and
15943 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
15945 o Major bugfixes (other):
15946 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
15947 that they initiated. Relays could distinguish incoming bridge
15948 connections from client connections, creating another avenue for
15949 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
15950 Found by "frosty_un".
15951 - Don't update the AccountingSoftLimitHitAt state file entry whenever
15952 tor gets started. This prevents a wrong average bandwidth
15953 estimate, which would cause relays to always start a new accounting
15954 interval at the earliest possible moment. Fixes bug 2003; bugfix
15955 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
15956 immensely in tracking this bug down.
15957 - Fix a crash bug when changing node restrictions while a DNS lookup
15958 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
15961 o Minor bugfixes (on 0.2.2.x and earlier):
15962 - When a hidden service turns an extra service-side introduction
15963 circuit into a general-purpose circuit, free the rend_data and
15964 intro_key fields first, so we won't leak memory if the circuit
15965 is cannibalized for use as another service-side introduction
15966 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
15967 - Rephrase the log message emitted if the TestSocks check is
15968 successful. Patch from Fabian Keil; fixes bug 4094.
15969 - Bridges now skip DNS self-tests, to act a little more stealthily.
15970 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
15971 bridges. Patch by "warms0x".
15972 - Remove a confusing dollar sign from the example fingerprint in the
15973 man page, and also make the example fingerprint a valid one. Fixes
15974 bug 4309; bugfix on 0.2.1.3-alpha.
15975 - Fix internal bug-checking logic that was supposed to catch
15976 failures in digest generation so that it will fail more robustly
15977 if we ask for a nonexistent algorithm. Found by Coverity Scan.
15978 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
15979 - Report any failure in init_keys() calls launched because our
15980 IP address has changed. Spotted by Coverity Scan. Bugfix on
15981 0.1.1.4-alpha; fixes CID 484.
15983 o Minor bugfixes (on 0.2.3.x):
15984 - Fix a bug in configure.in that kept it from building a configure
15985 script with autoconf versions earlier than 2.61. Fixes bug 2430;
15986 bugfix on 0.2.3.1-alpha.
15987 - Don't warn users that they are exposing a client port to the
15988 Internet if they have specified an RFC1918 address. Previously,
15989 we would warn if the user had specified any non-loopback
15990 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
15991 - Fix memory leaks in the failing cases of the new SocksPort and
15992 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
15993 fixes coverity CIDs 485, 486, and 487.
15996 - When a hidden service's introduction point times out, consider
15997 trying it again during the next attempt to connect to the
15998 HS. Previously, we would not try it again unless a newly fetched
15999 descriptor contained it. Required by fixes for bugs 1297 and 3825.
16000 - The next version of Windows will be called Windows 8, and it has
16001 a major version of 6, minor version of 2. Correctly identify that
16002 version instead of calling it "Very recent version". Resolves
16003 ticket 4153; reported by funkstar.
16004 - The Bridge Authority now writes statistics on how many bridge
16005 descriptors it gave out in total, and how many unique descriptors
16006 it gave out. It also lists how often the most and least commonly
16007 fetched descriptors were given out, as well as the median and
16008 25th/75th percentile. Implements tickets 4200 and 4294.
16009 - Update to the October 4 2011 Maxmind GeoLite Country database.
16011 o Code simplifications and refactoring:
16012 - Remove some old code to remember statistics about which descriptors
16013 we've served as a directory mirror. The feature wasn't used and
16014 is outdated now that microdescriptors are around.
16015 - Rename Tor functions that turn strings into addresses, so that
16016 "parse" indicates that no hostname resolution occurs, and
16017 "lookup" indicates that hostname resolution may occur. This
16018 should help prevent mistakes in the future. Fixes bug 3512.
16021 Changes in version 0.2.2.34 - 2011-10-26
16022 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
16023 can deanonymize Tor users. Everybody should upgrade.
16025 The attack relies on four components: 1) Clients reuse their TLS cert
16026 when talking to different relays, so relays can recognize a user by
16027 the identity key in her cert. 2) An attacker who knows the client's
16028 identity key can probe each guard relay to see if that identity key
16029 is connected to that guard relay right now. 3) A variety of active
16030 attacks in the literature (starting from "Low-Cost Traffic Analysis
16031 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
16032 discover the guard relays that a Tor user visiting the website is using.
16033 4) Clients typically pick three guards at random, so the set of guards
16034 for a given user could well be a unique fingerprint for her. This
16035 release fixes components #1 and #2, which is enough to block the attack;
16036 the other two remain as open research problems. Special thanks to
16037 "frosty_un" for reporting the issue to us!
16039 Clients should upgrade so they are no longer recognizable by the TLS
16040 certs they present. Relays should upgrade so they no longer allow a
16041 remote attacker to probe them to test whether unpatched clients are
16042 currently connected to them.
16044 This release also fixes several vulnerabilities that allow an attacker
16045 to enumerate bridge relays. Some bridge enumeration attacks still
16046 remain; see for example proposal 188.
16048 o Privacy/anonymity fixes (clients):
16049 - Clients and bridges no longer send TLS certificate chains on
16050 outgoing OR connections. Previously, each client or bridge would
16051 use the same cert chain for all outgoing OR connections until
16052 its IP address changes, which allowed any relay that the client
16053 or bridge contacted to determine which entry guards it is using.
16054 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16055 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16056 no longer considers that connection as suitable for satisfying a
16057 circuit EXTEND request. Now relays can protect clients from the
16058 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16059 - Directory authorities no longer assign the Guard flag to relays
16060 that haven't upgraded to the above "refuse EXTEND requests
16061 to client connections" fix. Now directory authorities can
16062 protect clients from the CVE-2011-2768 issue even if neither
16063 the clients nor the relays have upgraded yet. There's a new
16064 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16065 to let us transition smoothly, else tomorrow there would be no
16068 o Privacy/anonymity fixes (bridge enumeration):
16069 - Bridge relays now do their directory fetches inside Tor TLS
16070 connections, like all the other clients do, rather than connecting
16071 directly to the DirPort like public relays do. Removes another
16072 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16073 - Bridges relays now build circuits for themselves in a more similar
16074 way to how clients build them. Removes another avenue for
16075 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16076 when bridges were introduced.
16077 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16078 that they initiated. Relays could distinguish incoming bridge
16079 connections from client connections, creating another avenue for
16080 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16081 Found by "frosty_un".
16084 - Fix a crash bug when changing node restrictions while a DNS lookup
16085 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16087 - Don't launch a useless circuit after failing to use one of a
16088 hidden service's introduction points. Previously, we would
16089 launch a new introduction circuit, but not set the hidden service
16090 which that circuit was intended to connect to, so it would never
16091 actually be used. A different piece of code would then create a
16092 new introduction circuit correctly. Bug reported by katmagic and
16093 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16096 - Change an integer overflow check in the OpenBSD_Malloc code so
16097 that GCC is less likely to eliminate it as impossible. Patch
16098 from Mansour Moufid. Fixes bug 4059.
16099 - When a hidden service turns an extra service-side introduction
16100 circuit into a general-purpose circuit, free the rend_data and
16101 intro_key fields first, so we won't leak memory if the circuit
16102 is cannibalized for use as another service-side introduction
16103 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16104 - Bridges now skip DNS self-tests, to act a little more stealthily.
16105 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16106 bridges. Patch by "warms0x".
16107 - Fix internal bug-checking logic that was supposed to catch
16108 failures in digest generation so that it will fail more robustly
16109 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16110 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16111 - Report any failure in init_keys() calls launched because our
16112 IP address has changed. Spotted by Coverity Scan. Bugfix on
16113 0.1.1.4-alpha; fixes CID 484.
16115 o Minor bugfixes (log messages and documentation):
16116 - Remove a confusing dollar sign from the example fingerprint in the
16117 man page, and also make the example fingerprint a valid one. Fixes
16118 bug 4309; bugfix on 0.2.1.3-alpha.
16119 - The next version of Windows will be called Windows 8, and it has
16120 a major version of 6, minor version of 2. Correctly identify that
16121 version instead of calling it "Very recent version". Resolves
16122 ticket 4153; reported by funkstar.
16123 - Downgrade log messages about circuit timeout calibration from
16124 "notice" to "info": they don't require or suggest any human
16125 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
16126 bugfix on 0.2.2.14-alpha.
16129 - Turn on directory request statistics by default and include them in
16130 extra-info descriptors. Don't break if we have no GeoIP database.
16131 Backported from 0.2.3.1-alpha; implements ticket 3951.
16132 - Update to the October 4 2011 Maxmind GeoLite Country database.
16135 Changes in version 0.2.1.31 - 2011-10-26
16136 Tor 0.2.1.31 backports important security and privacy fixes for
16137 oldstable. This release is intended only for package maintainers and
16138 others who cannot use the 0.2.2 stable series. All others should be
16139 using Tor 0.2.2.x or newer.
16141 o Security fixes (also included in 0.2.2.x):
16142 - Replace all potentially sensitive memory comparison operations
16143 with versions whose runtime does not depend on the data being
16144 compared. This will help resist a class of attacks where an
16145 adversary can use variations in timing information to learn
16146 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16147 implementation by Robert Ransom based partially on code by DJB.)
16148 - Fix an assert in parsing router descriptors containing IPv6
16149 addresses. This one took down the directory authorities when
16150 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16152 o Privacy/anonymity fixes (also included in 0.2.2.x):
16153 - Clients and bridges no longer send TLS certificate chains on
16154 outgoing OR connections. Previously, each client or bridge would
16155 use the same cert chain for all outgoing OR connections until
16156 its IP address changes, which allowed any relay that the client
16157 or bridge contacted to determine which entry guards it is using.
16158 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16159 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16160 no longer considers that connection as suitable for satisfying a
16161 circuit EXTEND request. Now relays can protect clients from the
16162 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16163 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16164 that they initiated. Relays could distinguish incoming bridge
16165 connections from client connections, creating another avenue for
16166 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16167 Found by "frosty_un".
16168 - When receiving a hidden service descriptor, check that it is for
16169 the hidden service we wanted. Previously, Tor would store any
16170 hidden service descriptors that a directory gave it, whether it
16171 wanted them or not. This wouldn't have let an attacker impersonate
16172 a hidden service, but it did let directories pre-seed a client
16173 with descriptors that it didn't want. Bugfix on 0.0.6.
16174 - Avoid linkability based on cached hidden service descriptors: forget
16175 all hidden service descriptors cached as a client when processing a
16176 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
16177 - Make the bridge directory authority refuse to answer directory
16178 requests for "all" descriptors. It used to include bridge
16179 descriptors in its answer, which was a major information leak.
16180 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16181 - Don't attach new streams to old rendezvous circuits after SIGNAL
16182 NEWNYM. Previously, we would keep using an existing rendezvous
16183 circuit if it remained open (i.e. if it were kept open by a
16184 long-lived stream, or if a new stream were attached to it before
16185 Tor could notice that it was old and no longer in use). Bugfix on
16186 0.1.1.15-rc; fixes bug 3375.
16188 o Minor bugfixes (also included in 0.2.2.x):
16189 - When we restart our relay, we might get a successful connection
16190 from the outside before we've started our reachability tests,
16191 triggering a warning: "ORPort found reachable, but I have no
16192 routerinfo yet. Failing to inform controller of success." This
16193 bug was harmless unless Tor is running under a controller
16194 like Vidalia, in which case the controller would never get a
16195 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16197 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
16198 enabled. Fixes bug 1526.
16199 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16200 anything since 0.2.1.16-rc.
16201 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16202 None of the cases where we did this before were wrong, but by making
16203 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16204 - Fix a rare crash bug that could occur when a client was configured
16205 with a large number of bridges. Fixes bug 2629; bugfix on
16206 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16207 - Correct the warning displayed when a rendezvous descriptor exceeds
16208 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16210 - Fix an uncommon assertion failure when running with DNSPort under
16211 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
16212 - When warning about missing zlib development packages during compile,
16213 give the correct package names. Bugfix on 0.2.0.1-alpha.
16214 - Require that introduction point keys and onion keys have public
16215 exponent 65537. Bugfix on 0.2.0.10-alpha.
16216 - Do not crash when our configuration file becomes unreadable, for
16217 example due to a permissions change, between when we start up
16218 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
16220 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16222 - Always NUL-terminate the sun_path field of a sockaddr_un before
16223 passing it to the kernel. (Not a security issue: kernels are
16224 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16225 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16226 - Don't stack-allocate the list of supplementary GIDs when we're
16227 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16228 could take up to 256K, which is way too much stack. Found by
16229 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16231 o Minor bugfixes (only in 0.2.1.x):
16232 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
16233 rely on them. Bugfix on 0.2.1.30.
16234 - Use git revisions instead of svn revisions when generating our
16235 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16237 o Minor features (also included in 0.2.2.x):
16238 - Adjust the expiration time on our SSL session certificates to
16239 better match SSL certs seen in the wild. Resolves ticket 4014.
16240 - Allow nameservers with IPv6 address. Resolves bug 2574.
16241 - Update to the October 4 2011 Maxmind GeoLite Country database.
16244 Changes in version 0.2.3.5-alpha - 2011-09-28
16245 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
16246 bridge relays; fixes an assertion error that many users started hitting
16247 today; and adds the ability to refill token buckets more often than
16248 once per second, allowing significant performance improvements.
16251 - Bridge relays now do their directory fetches inside Tor TLS
16252 connections, like all the other clients do, rather than connecting
16253 directly to the DirPort like public relays do. Removes another
16254 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16255 - Bridges relays now build circuits for themselves in a more similar
16256 way to how clients build them. Removes another avenue for
16257 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16258 when bridges were introduced.
16261 - Fix an "Assertion md->held_by_node == 1 failed" error that could
16262 occur when the same microdescriptor was referenced by two node_t
16263 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
16265 o Major features (networking):
16266 - Add a new TokenBucketRefillInterval option to refill token buckets
16267 more frequently than once per second. This should improve network
16268 performance, alleviate queueing problems, and make traffic less
16269 bursty. Implements proposal 183; closes ticket 3630. Design by
16270 Florian Tschorsch and Björn Scheuermann; implementation by
16274 - Change an integer overflow check in the OpenBSD_Malloc code so
16275 that GCC is less likely to eliminate it as impossible. Patch
16276 from Mansour Moufid. Fixes bug 4059.
16278 o Minor bugfixes (usability):
16279 - Downgrade log messages about circuit timeout calibration from
16280 "notice" to "info": they don't require or suggest any human
16281 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
16282 bugfix on 0.2.2.14-alpha.
16284 o Minor features (diagnostics):
16285 - When the system call to create a listener socket fails, log the
16286 error message explaining why. This may help diagnose bug 4027.
16289 Changes in version 0.2.3.4-alpha - 2011-09-13
16290 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
16291 tweak to Tor's TLS handshake that makes relays and bridges that run
16292 this new version reachable from Iran again. It also fixes a few new
16293 bugs in 0.2.3.x, and teaches relays to recognize when they're not
16294 listed in the network consensus and republish.
16296 o Major bugfixes (also part of 0.2.2.33):
16297 - Avoid an assertion failure when reloading a configuration with
16298 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
16299 3923; bugfix on 0.2.2.25-alpha.
16301 o Minor features (security, also part of 0.2.2.33):
16302 - Check for replays of the public-key encrypted portion of an
16303 INTRODUCE1 cell, in addition to the current check for replays of
16304 the g^x value. This prevents a possible class of active attacks
16305 by an attacker who controls both an introduction point and a
16306 rendezvous point, and who uses the malleability of AES-CTR to
16307 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
16308 that these attacks are infeasible (requiring the attacker to send
16309 on the order of zettabytes of altered cells in a short interval),
16310 but we'd rather block them off in case there are any classes of
16311 this attack that we missed. Reported by Willem Pinckaers.
16313 o Minor features (also part of 0.2.2.33):
16314 - Adjust the expiration time on our SSL session certificates to
16315 better match SSL certs seen in the wild. Resolves ticket 4014.
16316 - Change the default required uptime for a relay to be accepted as
16317 a HSDir (hidden service directory) from 24 hours to 25 hours.
16318 Improves on 0.2.0.10-alpha; resolves ticket 2649.
16319 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
16320 authorities to abstain from voting on assignment of the HSDir
16321 consensus flag. Related to bug 2649.
16322 - Update to the September 6 2011 Maxmind GeoLite Country database.
16324 o Minor bugfixes (also part of 0.2.2.33):
16325 - Demote the 'replay detected' log message emitted when a hidden
16326 service receives the same Diffie-Hellman public key in two different
16327 INTRODUCE2 cells to info level. A normal Tor client can cause that
16328 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
16329 fixes part of bug 2442.
16330 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
16331 level. There is nothing that a hidden service's operator can do
16332 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
16334 - Clarify a log message specifying the characters permitted in
16335 HiddenServiceAuthorizeClient client names. Previously, the log
16336 message said that "[A-Za-z0-9+-_]" were permitted; that could have
16337 given the impression that every ASCII character between "+" and "_"
16338 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
16340 o Build fixes (also part of 0.2.2.33):
16341 - Clean up some code issues that prevented Tor from building on older
16342 BSDs. Fixes bug 3894; reported by "grarpamp".
16343 - Search for a platform-specific version of "ar" when cross-compiling.
16344 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
16347 - Fix a bug where the SocksPort option (for example) would get
16348 ignored and replaced by the default if a SocksListenAddress
16349 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
16353 - Relays now try regenerating and uploading their descriptor more
16354 frequently if they are not listed in the consensus, or if the
16355 version of their descriptor listed in the consensus is too
16356 old. This fix should prevent situations where a server declines
16357 to re-publish itself because it has done so too recently, even
16358 though the authorities decided not to list its recent-enough
16359 descriptor. Fix for bug 3327.
16362 - Relays now include a reason for regenerating their descriptors
16363 in an HTTP header when uploading to the authorities. This will
16364 make it easier to debug descriptor-upload issues in the future.
16365 - When starting as root and then changing our UID via the User
16366 control option, and we have a ControlSocket configured, make sure
16367 that the ControlSocket is owned by the same account that Tor will
16368 run under. Implements ticket 3421; fix by Jérémy Bobbio.
16371 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
16372 utility function used in the control-port code). This shouldn't
16373 ever happen unless Tor is completely out of memory, but if it did
16374 happen and Tor somehow recovered from it, Tor could have sent a log
16375 message to a control port in the middle of a reply to a controller
16376 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
16377 - Make 'FetchUselessDescriptors' cause all descriptor types and
16378 all consensus types (including microdescriptors) to get fetched.
16379 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
16381 o Code refactoring:
16382 - Make a new "entry connection" struct as an internal subtype of "edge
16383 connection", to simplify the code and make exit connections smaller.
16386 Changes in version 0.2.2.33 - 2011-09-13
16387 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
16388 TLS handshake that makes relays and bridges that run this new version
16389 reachable from Iran again.
16392 - Avoid an assertion failure when reloading a configuration with
16393 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
16394 3923; bugfix on 0.2.2.25-alpha.
16396 o Minor features (security):
16397 - Check for replays of the public-key encrypted portion of an
16398 INTRODUCE1 cell, in addition to the current check for replays of
16399 the g^x value. This prevents a possible class of active attacks
16400 by an attacker who controls both an introduction point and a
16401 rendezvous point, and who uses the malleability of AES-CTR to
16402 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
16403 that these attacks are infeasible (requiring the attacker to send
16404 on the order of zettabytes of altered cells in a short interval),
16405 but we'd rather block them off in case there are any classes of
16406 this attack that we missed. Reported by Willem Pinckaers.
16409 - Adjust the expiration time on our SSL session certificates to
16410 better match SSL certs seen in the wild. Resolves ticket 4014.
16411 - Change the default required uptime for a relay to be accepted as
16412 a HSDir (hidden service directory) from 24 hours to 25 hours.
16413 Improves on 0.2.0.10-alpha; resolves ticket 2649.
16414 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
16415 authorities to abstain from voting on assignment of the HSDir
16416 consensus flag. Related to bug 2649.
16417 - Update to the September 6 2011 Maxmind GeoLite Country database.
16419 o Minor bugfixes (documentation and log messages):
16420 - Correct the man page to explain that HashedControlPassword and
16421 CookieAuthentication can both be set, in which case either method
16422 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
16423 when we decided to allow these config options to both be set. Issue
16424 raised by bug 3898.
16425 - Demote the 'replay detected' log message emitted when a hidden
16426 service receives the same Diffie-Hellman public key in two different
16427 INTRODUCE2 cells to info level. A normal Tor client can cause that
16428 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
16429 fixes part of bug 2442.
16430 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
16431 level. There is nothing that a hidden service's operator can do
16432 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
16434 - Clarify a log message specifying the characters permitted in
16435 HiddenServiceAuthorizeClient client names. Previously, the log
16436 message said that "[A-Za-z0-9+-_]" were permitted; that could have
16437 given the impression that every ASCII character between "+" and "_"
16438 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
16441 - Provide a substitute implementation of lround() for MSVC, which
16442 apparently lacks it. Patch from Gisle Vanem.
16443 - Clean up some code issues that prevented Tor from building on older
16444 BSDs. Fixes bug 3894; reported by "grarpamp".
16445 - Search for a platform-specific version of "ar" when cross-compiling.
16446 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
16449 Changes in version 0.2.3.3-alpha - 2011-09-01
16450 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
16451 security, and provides client-side support for the microdescriptor
16452 and optimistic data features introduced earlier in the 0.2.3.x
16453 series. It also includes numerous critical bugfixes in the (optional)
16454 bufferevent-based networking backend.
16456 o Major features (stream isolation):
16457 - You can now configure Tor so that streams from different
16458 applications are isolated on different circuits, to prevent an
16459 attacker who sees your streams as they leave an exit node from
16460 linking your sessions to one another. To do this, choose some way
16461 to distinguish the applications: have them connect to different
16462 SocksPorts, or have one of them use SOCKS4 while the other uses
16463 SOCKS5, or have them pass different authentication strings to the
16464 SOCKS proxy. Then, use the new SocksPort syntax to configure the
16465 degree of isolation you need. This implements Proposal 171.
16466 - There's a new syntax for specifying multiple client ports (such as
16467 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
16468 multiple *Port entries with full addr:port syntax on each.
16469 The old *ListenAddress format is still supported, but you can't
16470 mix it with the new *Port syntax.
16472 o Major features (other):
16473 - Enable microdescriptor fetching by default for clients. This allows
16474 clients to download a much smaller amount of directory information.
16475 To disable it (and go back to the old-style consensus and
16476 descriptors), set "UseMicrodescriptors 0" in your torrc file.
16477 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
16478 "PortForwarding" config option), now supports Windows.
16479 - When using an exit relay running 0.2.3.x, clients can now
16480 "optimistically" send data before the exit relay reports that
16481 the stream has opened. This saves a round trip when starting
16482 connections where the client speaks first (such as web browsing).
16483 This behavior is controlled by a consensus parameter (currently
16484 disabled). To turn it on or off manually, use the "OptimisticData"
16485 torrc option. Implements proposal 181; code by Ian Goldberg.
16487 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
16488 - When using IOCP on Windows, we need to enable Libevent windows
16490 - The IOCP backend now works even when the user has not specified
16491 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
16492 Fixes part of bug 3752.
16493 - Correctly record the bytes we've read and written when using
16494 bufferevents, so that we can include them in our bandwidth history
16495 and advertised bandwidth. Fixes bug 3803.
16496 - Apply rate-limiting only at the bottom of a chain of filtering
16497 bufferevents. This prevents us from filling up internal read
16498 buffers and violating rate-limits when filtering bufferevents
16499 are enabled. Fixes part of bug 3804.
16500 - Add high-watermarks to the output buffers for filtered
16501 bufferevents. This prevents us from filling up internal write
16502 buffers and wasting CPU cycles when filtering bufferevents are
16503 enabled. Fixes part of bug 3804.
16504 - Correctly notice when data has been written from a bufferevent
16505 without flushing it completely. Fixes bug 3805.
16506 - Fix a bug where server-side tunneled bufferevent-based directory
16507 streams would get closed prematurely. Fixes bug 3814.
16508 - Fix a use-after-free error with per-connection rate-limiting
16509 buckets. Fixes bug 3888.
16511 o Major bugfixes (also part of 0.2.2.31-rc):
16512 - If we're configured to write our ControlPorts to disk, only write
16513 them after switching UID and creating the data directory. This way,
16514 we don't fail when starting up with a nonexistent DataDirectory
16515 and a ControlPortWriteToFile setting based on that directory. Fixes
16516 bug 3747; bugfix on Tor 0.2.2.26-beta.
16519 - Added a new CONF_CHANGED event so that controllers can be notified
16520 of any configuration changes made by other controllers, or by the
16521 user. Implements ticket 1692.
16522 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
16523 leak when using bufferevents, and lets Libevent worry about how to
16524 best copy data out of a buffer.
16525 - Replace files in stats/ rather than appending to them. Now that we
16526 include statistics in extra-info descriptors, it makes no sense to
16527 keep old statistics forever. Implements ticket 2930.
16529 o Minor features (build compatibility):
16530 - Limited, experimental support for building with nmake and MSVC.
16531 - Provide a substitute implementation of lround() for MSVC, which
16532 apparently lacks it. Patch from Gisle Vanem.
16534 o Minor features (also part of 0.2.2.31-rc):
16535 - Update to the August 2 2011 Maxmind GeoLite Country database.
16537 o Minor bugfixes (on 0.2.3.x-alpha):
16538 - Fix a spurious warning when parsing SOCKS requests with
16539 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
16540 - Get rid of a harmless warning that could happen on relays running
16541 with bufferevents. The warning was caused by someone doing an http
16542 request to a relay's orport. Also don't warn for a few related
16543 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
16545 o Minor bugfixes (on 2.2.x and earlier):
16546 - Correct the man page to explain that HashedControlPassword and
16547 CookieAuthentication can both be set, in which case either method
16548 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
16549 when we decided to allow these config options to both be set. Issue
16550 raised by bug 3898.
16551 - The "--quiet" and "--hush" options now apply not only to Tor's
16552 behavior before logs are configured, but also to Tor's behavior in
16553 the absence of configured logs. Fixes bug 3550; bugfix on
16556 o Minor bugfixes (also part of 0.2.2.31-rc):
16557 - Write several files in text mode, on OSes that distinguish text
16558 mode from binary mode (namely, Windows). These files are:
16559 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
16560 that collect those statistics; 'client_keys' and 'hostname' for
16561 hidden services that use authentication; and (in the tor-gencert
16562 utility) newly generated identity and signing keys. Previously,
16563 we wouldn't specify text mode or binary mode, leading to an
16564 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
16565 the DirRecordUsageByCountry option which would have triggered
16566 the assertion failure was added), although this assertion failure
16567 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
16568 - Selectively disable deprecation warnings on OS X because Lion
16569 started deprecating the shipped copy of openssl. Fixes bug 3643.
16570 - Remove an extra pair of quotation marks around the error
16571 message in control-port STATUS_GENERAL BUG events. Bugfix on
16572 0.1.2.6-alpha; fixes bug 3732.
16573 - When unable to format an address as a string, report its value
16574 as "???" rather than reusing the last formatted address. Bugfix
16577 o Code simplifications and refactoring:
16578 - Rewrite the listener-selection logic so that parsing which ports
16579 we want to listen on is now separate from binding to the ports
16583 - Building Tor with bufferevent support now requires Libevent
16584 2.0.13-stable or later. Previous versions of Libevent had bugs in
16585 SSL-related bufferevents and related issues that would make Tor
16586 work badly with bufferevents. Requiring 2.0.13-stable also allows
16587 Tor with bufferevents to take advantage of Libevent APIs
16588 introduced after 2.0.8-rc.
16591 Changes in version 0.2.2.32 - 2011-08-27
16592 The Tor 0.2.2 release series is dedicated to the memory of Andreas
16593 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
16594 a founder of the PETS community, a leader in our field, a mentor,
16595 and a friend. He left us with these words: "I had the possibility
16596 to contribute to this world that is not as it should be. I hope I
16597 could help in some areas to make the world a better place, and that
16598 I could also encourage other people to be engaged in improving the
16599 world. Please, stay engaged. This world needs you, your love, your
16600 initiative -- now I cannot be part of that anymore."
16602 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
16603 ready. More than two years in the making, this release features improved
16604 client performance and hidden service reliability, better compatibility
16605 for Android, correct behavior for bridges that listen on more than
16606 one address, more extensible and flexible directory object handling,
16607 better reporting of network statistics, improved code security, and
16608 many many other features and bugfixes.
16611 Changes in version 0.2.2.31-rc - 2011-08-17
16612 Tor 0.2.2.31-rc is the second and hopefully final release candidate
16613 for the Tor 0.2.2.x series.
16616 - Remove an extra pair of quotation marks around the error
16617 message in control-port STATUS_GENERAL BUG events. Bugfix on
16618 0.1.2.6-alpha; fixes bug 3732.
16619 - If we're configured to write our ControlPorts to disk, only write
16620 them after switching UID and creating the data directory. This way,
16621 we don't fail when starting up with a nonexistent DataDirectory
16622 and a ControlPortWriteToFile setting based on that directory. Fixes
16623 bug 3747; bugfix on Tor 0.2.2.26-beta.
16626 - Update to the August 2 2011 Maxmind GeoLite Country database.
16629 - Allow GETINFO fingerprint to return a fingerprint even when
16630 we have not yet built a router descriptor. Fixes bug 3577;
16631 bugfix on 0.2.0.1-alpha.
16632 - Write several files in text mode, on OSes that distinguish text
16633 mode from binary mode (namely, Windows). These files are:
16634 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
16635 that collect those statistics; 'client_keys' and 'hostname' for
16636 hidden services that use authentication; and (in the tor-gencert
16637 utility) newly generated identity and signing keys. Previously,
16638 we wouldn't specify text mode or binary mode, leading to an
16639 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
16640 the DirRecordUsageByCountry option which would have triggered
16641 the assertion failure was added), although this assertion failure
16642 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
16643 - Selectively disable deprecation warnings on OS X because Lion
16644 started deprecating the shipped copy of openssl. Fixes bug 3643.
16645 - When unable to format an address as a string, report its value
16646 as "???" rather than reusing the last formatted address. Bugfix
16650 Changes in version 0.2.3.2-alpha - 2011-07-18
16651 Tor 0.2.3.2-alpha introduces two new experimental features:
16652 microdescriptors and pluggable transports. It also continues cleaning
16653 up a variety of recently introduced features.
16656 - Clients can now use microdescriptors instead of regular descriptors
16657 to build circuits. Microdescriptors are authority-generated
16658 summaries of regular descriptors' contents, designed to change
16659 very rarely (see proposal 158 for details). This feature is
16660 designed to save bandwidth, especially for clients on slow internet
16661 connections. It's off by default for now, since nearly no caches
16662 support it, but it will be on-by-default for clients in a future
16663 version. You can use the UseMicrodescriptors option to turn it on.
16664 - Tor clients using bridges can now be configured to use a separate
16665 'transport' proxy for each bridge. This approach helps to resist
16666 censorship by allowing bridges to use protocol obfuscation
16667 plugins. It implements part of proposal 180. Implements ticket 2841.
16668 - While we're trying to bootstrap, record how many TLS connections
16669 fail in each state, and report which states saw the most failures
16670 in response to any bootstrap failures. This feature may speed up
16671 diagnosis of censorship events. Implements ticket 3116.
16673 o Major bugfixes (on 0.2.3.1-alpha):
16674 - When configuring a large set of nodes in EntryNodes (as with
16675 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
16676 random subset to be guards, and choose them in random
16677 order. Fixes bug 2798.
16678 - Tor could crash when remembering a consensus in a non-used consensus
16679 flavor without having a current consensus set. Fixes bug 3361.
16680 - Comparing an unknown address to a microdescriptor's shortened exit
16681 policy would always give a "rejected" result. Fixes bug 3599.
16682 - Using microdescriptors as a client no longer prevents Tor from
16683 uploading and downloading hidden service descriptors. Fixes
16687 - Allow nameservers with IPv6 address. Resolves bug 2574.
16688 - Accept attempts to include a password authenticator in the
16689 handshake, as supported by SOCKS5. This handles SOCKS clients that
16690 don't know how to omit a password when authenticating. Resolves
16692 - When configuring a large set of nodes in EntryNodes, and there are
16693 enough of them listed as Guard so that we don't need to consider
16694 the non-guard entries, prefer the ones listed with the Guard flag.
16695 - Check for and recover from inconsistency in the microdescriptor
16696 cache. This will make it harder for us to accidentally free a
16697 microdescriptor without removing it from the appropriate data
16698 structures. Fixes issue 3135; issue noted by "wanoskarnet".
16699 - Log SSL state transitions at log level DEBUG, log domain
16700 HANDSHAKE. This can be useful for debugging censorship events.
16701 Implements ticket 3264.
16702 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
16703 implements ticket 3439.
16705 o Minor bugfixes (on 0.2.3.1-alpha):
16706 - Do not free all general-purpose regular descriptors just
16707 because microdescriptor use is enabled. Fixes bug 3113.
16708 - Correctly link libevent_openssl when --enable-static-libevent
16709 is passed to configure. Fixes bug 3118.
16710 - Bridges should not complain during their heartbeat log messages that
16711 they are unlisted in the consensus: that's more or less the point
16712 of being a bridge. Fixes bug 3183.
16713 - Report a SIGNAL event to controllers when acting on a delayed
16714 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
16715 event to the controller if we acted on a SIGNAL NEWNYM command
16716 immediately, and otherwise not report a SIGNAL event for the
16717 command at all. Fixes bug 3349.
16718 - Fix a crash when handling the SIGNAL controller command or
16719 reporting ERR-level status events with bufferevents enabled. Found
16720 by Robert Ransom. Fixes bug 3367.
16721 - Always ship the tor-fw-helper manpage in our release tarballs.
16722 Fixes bug 3389. Reported by Stephen Walker.
16723 - Fix a class of double-mark-for-close bugs when bufferevents
16724 are enabled. Fixes bug 3403.
16725 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
16726 - Add SIGNAL to the list returned by the 'GETINFO events/names'
16727 control-port command. Fixes part of bug 3465.
16728 - Prevent using negative indices during unit test runs when read_all()
16729 fails. Spotted by coverity.
16730 - Fix a rare memory leak when checking the nodelist without it being
16731 present. Found by coverity.
16732 - Only try to download a microdescriptor-flavored consensus from
16733 a directory cache that provides them.
16735 o Minor bugfixes (on 0.2.2.x and earlier):
16736 - Assert that hidden-service-related operations are not performed
16737 using single-hop circuits. Previously, Tor would assert that
16738 client-side streams are not attached to single-hop circuits,
16739 but not that other sensitive operations on the client and service
16740 side are not performed using single-hop circuits. Fixes bug 3332;
16742 - Don't publish a new relay descriptor when we reload our onion key,
16743 unless the onion key has actually changed. Fixes bug 3263 and
16744 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
16745 - Allow GETINFO fingerprint to return a fingerprint even when
16746 we have not yet built a router descriptor. Fixes bug 3577;
16747 bugfix on 0.2.0.1-alpha.
16748 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
16749 on 0.2.2.4-alpha; fixes bug 3427.
16751 o Code simplification and refactoring:
16752 - Use tor_sscanf() in place of scanf() in more places through the
16753 code. This makes us a little more locale-independent, and
16754 should help shut up code-analysis tools that can't tell
16755 a safe sscanf string from a dangerous one.
16756 - Use tt_assert(), not tor_assert(), for checking for test failures.
16757 This makes the unit tests more able to go on in the event that
16759 - Split connection_about_to_close() into separate functions for each
16763 - On Windows, we now define the _WIN32_WINNT macros only if they
16764 are not already defined. This lets the person building Tor decide,
16765 if they want, to require a later version of Windows.
16768 Changes in version 0.2.2.30-rc - 2011-07-07
16769 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
16770 series. It fixes a few smaller bugs, but generally appears stable.
16771 Please test it and let us know whether it is!
16774 - Send a SUCCEEDED stream event to the controller when a reverse
16775 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
16776 discovered by katmagic.
16777 - Always NUL-terminate the sun_path field of a sockaddr_un before
16778 passing it to the kernel. (Not a security issue: kernels are
16779 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16780 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16781 - Don't stack-allocate the list of supplementary GIDs when we're
16782 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16783 could take up to 256K, which is way too much stack. Found by
16784 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16785 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
16786 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
16787 fixes part of bug 3465.
16788 - Fix a memory leak when receiving a descriptor for a hidden
16789 service we didn't ask for. Found by Coverity; CID #30. Bugfix
16793 - Update to the July 1 2011 Maxmind GeoLite Country database.
16796 Changes in version 0.2.2.29-beta - 2011-06-20
16797 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
16798 have bridge lines in their torrc but don't want to use them; gets
16799 us closer to having the control socket feature working on Debian;
16800 and fixes a variety of smaller bugs.
16803 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
16804 When we changed the default behavior to "use bridges if any
16805 are listed in the torrc", we surprised users who had bridges
16806 in their torrc files but who didn't actually want to use them.
16807 Partial resolution for bug 3354.
16810 - Don't attach new streams to old rendezvous circuits after SIGNAL
16811 NEWNYM. Previously, we would keep using an existing rendezvous
16812 circuit if it remained open (i.e. if it were kept open by a
16813 long-lived stream, or if a new stream were attached to it before
16814 Tor could notice that it was old and no longer in use). Bugfix on
16815 0.1.1.15-rc; fixes bug 3375.
16818 - Fix a bug when using ControlSocketsGroupWritable with User. The
16819 directory's group would be checked against the current group, not
16820 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
16821 bugfix on 0.2.2.26-beta.
16822 - Make connection_printf_to_buf()'s behavior sane. Its callers
16823 expect it to emit a CRLF iff the format string ends with CRLF;
16824 it actually emitted a CRLF iff (a) the format string ended with
16825 CRLF or (b) the resulting string was over 1023 characters long or
16826 (c) the format string did not end with CRLF *and* the resulting
16827 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
16828 fixes part of bug 3407.
16829 - Make send_control_event_impl()'s behavior sane. Its callers
16830 expect it to always emit a CRLF at the end of the string; it
16831 might have emitted extra control characters as well. Bugfix on
16832 0.1.1.9-alpha; fixes another part of bug 3407.
16833 - Make crypto_rand_int() check the value of its input correctly.
16834 Previously, it accepted values up to UINT_MAX, but could return a
16835 negative number if given a value above INT_MAX+1. Found by George
16836 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
16837 - Avoid a segfault when reading a malformed circuit build state
16838 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
16840 - When asked about a DNS record type we don't support via a
16841 client DNSPort, reply with NOTIMPL rather than an empty
16842 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
16843 - Fix a rare memory leak during stats writing. Found by coverity.
16846 - Update to the June 1 2011 Maxmind GeoLite Country database.
16848 o Code simplifications and refactoring:
16849 - Remove some dead code as indicated by coverity.
16850 - Remove a few dead assignments during router parsing. Found by
16852 - Add some forgotten return value checks during unit tests. Found
16854 - Don't use 1-bit wide signed bit fields. Found by coverity.
16857 Changes in version 0.2.2.28-beta - 2011-06-04
16858 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
16859 fixed a big bug in whether relays stay in the consensus consistently,
16860 we moved closer to handling bridges and hidden services correctly,
16861 and we started the process of better handling the dreaded "my Vidalia
16862 died, and now my Tor demands a password when I try to reconnect to it"
16866 - Don't decide to make a new descriptor when receiving a HUP signal.
16867 This bug has caused a lot of 0.2.2.x relays to disappear from the
16868 consensus periodically. Fixes the most common case of triggering
16869 bug 1810; bugfix on 0.2.2.7-alpha.
16870 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
16871 - Don't try to build descriptors if "ORPort auto" is set and we
16872 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
16874 - Resolve a crash that occurred when setting BridgeRelay to 1 with
16875 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
16876 - Apply circuit timeouts to opened hidden-service-related circuits
16877 based on the correct start time. Previously, we would apply the
16878 circuit build timeout based on time since the circuit's creation;
16879 it was supposed to be applied based on time since the circuit
16880 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
16881 - Use the same circuit timeout for client-side introduction
16882 circuits as for other four-hop circuits, rather than the timeout
16883 for single-hop directory-fetch circuits; the shorter timeout may
16884 have been appropriate with the static circuit build timeout in
16885 0.2.1.x and earlier, but caused many hidden service access attempts
16886 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
16887 on 0.2.2.2-alpha; fixes another part of bug 1297.
16888 - In ticket 2511 we fixed a case where you could use an unconfigured
16889 bridge if you had configured it as a bridge the last time you ran
16890 Tor. Now fix another edge case: if you had configured it as a bridge
16891 but then switched to a different bridge via the controller, you
16892 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
16896 - Add an __OwningControllerProcess configuration option and a
16897 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
16898 that when it exits, Tor will shut down. Implements feature 3049.
16899 - If "UseBridges 1" is set and no bridges are configured, Tor will
16900 now refuse to build any circuits until some bridges are set.
16901 If "UseBridges auto" is set, Tor will use bridges if they are
16902 configured and we are not running as a server, but otherwise will
16903 make circuits as usual. The new default is "auto". Patch by anonym,
16904 so the Tails LiveCD can stop automatically revealing you as a Tor
16908 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16909 - Remove a trailing asterisk from "exit-policy/default" in the
16910 output of the control port command "GETINFO info/names". Bugfix
16912 - Use a wide type to hold sockets when built for 64-bit Windows builds.
16914 - Warn when the user configures two HiddenServiceDir lines that point
16915 to the same directory. Bugfix on 0.0.6 (the version introducing
16916 HiddenServiceDir); fixes bug 3289.
16917 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
16918 part of bug 2748; bugfix on 0.2.0.10-alpha.
16919 - Log malformed requests for rendezvous descriptors as protocol
16920 warnings, not warnings. Also, use a more informative log message
16921 in case someone sees it at log level warning without prior
16922 info-level messages. Fixes the other part of bug 2748; bugfix
16924 - Clear the table recording the time of the last request for each
16925 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
16926 Previously, we would clear our HS descriptor cache on SIGNAL
16927 NEWNYM, but if we had previously retrieved a descriptor (or tried
16928 to) from every directory responsible for it, we would refuse to
16929 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
16931 - Fix a log message that said "bits" while displaying a value in
16932 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
16934 - When checking for 1024-bit keys, check for 1024 bits, not 128
16935 bytes. This allows Tor to correctly discard keys of length 1017
16936 through 1023. Bugfix on 0.0.9pre5.
16939 - Relays now log the reason for publishing a new relay descriptor,
16940 so we have a better chance of hunting down instances of bug 1810.
16941 Resolves ticket 3252.
16942 - Revise most log messages that refer to nodes by nickname to
16943 instead use the "$key=nickname at address" format. This should be
16944 more useful, especially since nicknames are less and less likely
16945 to be unique. Resolves ticket 3045.
16946 - Log (at info level) when purging pieces of hidden-service-client
16947 state because of SIGNAL NEWNYM.
16950 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16951 anything since 0.2.1.16-rc.
16954 Changes in version 0.2.2.27-beta - 2011-05-18
16955 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
16956 release, and also adds a few more general bugfixes.
16959 - Fix a crash bug when changing bridges in a running Tor process.
16960 Fixes bug 3213; bugfix on 0.2.2.26-beta.
16961 - When the controller configures a new bridge, don't wait 10 to 60
16962 seconds before trying to fetch its descriptor. Bugfix on
16963 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
16966 - Require that onion keys have exponent 65537 in microdescriptors too.
16967 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
16968 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
16969 Changed the limit to 512 characters by removing base64 newlines.
16970 Fixes bug 2752. Fix by Michael Yakubovich.
16971 - When a client starts or stops using bridges, never use a circuit
16972 that was built before the configuration change. This behavior could
16973 put at risk a user who uses bridges to ensure that her traffic
16974 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
16978 Changes in version 0.2.2.26-beta - 2011-05-17
16979 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
16980 also introduces a new "socksport auto" approach that should make it
16981 easier to run multiple Tors on the same system, and does a lot of
16982 cleanup to get us closer to a release candidate.
16984 o Security/privacy fixes:
16985 - Replace all potentially sensitive memory comparison operations
16986 with versions whose runtime does not depend on the data being
16987 compared. This will help resist a class of attacks where an
16988 adversary can use variations in timing information to learn
16989 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16990 implementation by Robert Ransom based partially on code by DJB.)
16991 - When receiving a hidden service descriptor, check that it is for
16992 the hidden service we wanted. Previously, Tor would store any
16993 hidden service descriptors that a directory gave it, whether it
16994 wanted them or not. This wouldn't have let an attacker impersonate
16995 a hidden service, but it did let directories pre-seed a client
16996 with descriptors that it didn't want. Bugfix on 0.0.6.
16997 - On SIGHUP, do not clear out all TrackHostExits mappings, client
16998 DNS cache entries, and virtual address mappings: that's what
16999 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
17002 - The options SocksPort, ControlPort, and so on now all accept a
17003 value "auto" that opens a socket on an OS-selected port. A
17004 new ControlPortWriteToFile option tells Tor to write its
17005 actual control port or ports to a chosen file. If the option
17006 ControlPortFileGroupReadable is set, the file is created as
17007 group-readable. Now users can run two Tor clients on the same
17008 system without needing to manually mess with parameters. Resolves
17009 part of ticket 3076.
17010 - Set SO_REUSEADDR on all sockets, not just listeners. This should
17011 help busy exit nodes avoid running out of useable ports just
17012 because all the ports have been used in the near past. Resolves
17016 - New "GETINFO net/listeners/(type)" controller command to return
17017 a list of addresses and ports that are bound for listeners for a
17018 given connection type. This is useful when the user has configured
17019 "SocksPort auto" and the controller needs to know which port got
17020 chosen. Resolves another part of ticket 3076.
17021 - Add a new ControlSocketsGroupWritable configuration option: when
17022 it is turned on, ControlSockets are group-writeable by the default
17023 group of the current user. Patch by Jérémy Bobbio; implements
17025 - Tor now refuses to create a ControlSocket in a directory that is
17026 world-readable (or group-readable if ControlSocketsGroupWritable
17027 is 0). This is necessary because some operating systems do not
17028 enforce permissions on an AF_UNIX sockets. Permissions on the
17029 directory holding the socket, however, seems to work everywhere.
17030 - Rate-limit a warning about failures to download v2 networkstatus
17031 documents. Resolves part of bug 1352.
17032 - Backport code from 0.2.3.x that allows directory authorities to
17033 clean their microdescriptor caches. Needed to resolve bug 2230.
17034 - When an HTTPS proxy reports "403 Forbidden", we now explain
17035 what it means rather than calling it an unexpected status code.
17036 Closes bug 2503. Patch from Michael Yakubovich.
17037 - Update to the May 1 2011 Maxmind GeoLite Country database.
17040 - Authorities now clean their microdesc cache periodically and when
17041 reading from disk initially, not only when adding new descriptors.
17042 This prevents a bug where we could lose microdescriptors. Bugfix
17043 on 0.2.2.6-alpha. Fixes bug 2230.
17044 - Do not crash when our configuration file becomes unreadable, for
17045 example due to a permissions change, between when we start up
17046 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
17048 - Avoid a bug that would keep us from replacing a microdescriptor
17049 cache on Windows. (We would try to replace the file while still
17050 holding it open. That's fine on Unix, but Windows doesn't let us
17051 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
17052 - Add missing explanations for the authority-related torrc options
17053 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
17054 man page. Resolves issue 2379.
17055 - As an authority, do not upload our own vote or signature set to
17056 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
17057 it would get flagged as a duplicate. Resolves bug 3026.
17058 - Accept hidden service descriptors if we think we might be a hidden
17059 service directory, regardless of what our consensus says. This
17060 helps robustness, since clients and hidden services can sometimes
17061 have a more up-to-date view of the network consensus than we do,
17062 and if they think that the directory authorities list us a HSDir,
17063 we might actually be one. Related to bug 2732; bugfix on
17065 - When a controller changes TrackHostExits, remove mappings for
17066 hosts that should no longer have their exits tracked. Bugfix on
17068 - When a controller changes VirtualAddrNetwork, remove any mappings
17069 for hosts that were automapped to the old network. Bugfix on
17071 - When a controller changes one of the AutomapHosts* options, remove
17072 any mappings for hosts that should no longer be automapped. Bugfix
17074 - Do not reset the bridge descriptor download status every time we
17075 re-parse our configuration or get a configuration change. Fixes
17076 bug 3019; bugfix on 0.2.0.3-alpha.
17078 o Minor bugfixes (code cleanup):
17079 - When loading the microdesc journal, remember its current size.
17080 In 0.2.2, this helps prevent the microdesc journal from growing
17081 without limit on authorities (who are the only ones to use it in
17082 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
17083 Fix posted by "cypherpunks."
17084 - The microdesc journal is supposed to get rebuilt only if it is
17085 at least _half_ the length of the store, not _twice_ the length
17086 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
17087 - Fix a potential null-pointer dereference while computing a
17088 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
17090 - Avoid a possible null-pointer dereference when rebuilding the mdesc
17091 cache without actually having any descriptors to cache. Bugfix on
17092 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
17093 - If we fail to compute the identity digest of a v3 legacy keypair,
17094 warn, and don't use a buffer-full of junk instead. Bugfix on
17095 0.2.1.1-alpha; fixes bug 3106.
17096 - Resolve an untriggerable issue in smartlist_string_num_isin(),
17097 where if the function had ever in the future been used to check
17098 for the presence of a too-large number, it would have given an
17099 incorrect result. (Fortunately, we only used it for 16-bit
17100 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
17101 - Require that introduction point keys and onion handshake keys
17102 have a public exponent of 65537. Starts to fix bug 3207; bugfix
17105 o Removed features:
17106 - Caches no longer download and serve v2 networkstatus documents
17107 unless FetchV2Networkstatus flag is set: these documents haven't
17108 haven't been used by clients or relays since 0.2.0.x. Resolves
17112 Changes in version 0.2.3.1-alpha - 2011-05-05
17113 Tor 0.2.3.1-alpha adds some new experimental features, including support
17114 for an improved network IO backend, IOCP networking on Windows,
17115 microdescriptor caching, "fast-start" support for streams, and automatic
17116 home router configuration. There are also numerous internal improvements
17117 to try to make the code easier for developers to work with.
17119 This is the first alpha release in a new series, so expect there to be
17120 bugs. Users who would rather test out a more stable branch should
17121 stay with 0.2.2.x for now.
17124 - Tor can now optionally build with the "bufferevents" buffered IO
17125 backend provided by Libevent 2. To use this feature, make sure you
17126 have the latest possible version of Libevent, and pass the
17127 --enable-bufferevents flag to configure when building Tor from
17128 source. This feature will make our networking code more flexible,
17129 let us stack layers on each other, and let us use more efficient
17130 zero-copy transports where available.
17131 - As an experimental feature, Tor can use IOCP for networking on Windows.
17132 Once this code is tuned and optimized, it promises much better
17133 performance than the select-based backend we've used in the past. To
17134 try this feature, you must build Tor with Libevent 2, configure Tor
17135 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
17136 your torrc. There are known bugs here: only try this if you can help
17137 debug it as it breaks.
17138 - The EntryNodes option can now include country codes like {de} or IP
17139 addresses or network masks. Previously we had disallowed these options
17140 because we didn't have an efficient way to keep the list up to
17141 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
17142 - Exit nodes now accept and queue data on not-yet-connected streams.
17143 Previously, the client wasn't allowed to send data until the stream was
17144 connected, which slowed down all connections. This change will enable
17145 clients to perform a "fast-start" on streams and send data without
17146 having to wait for a confirmation that the stream has opened. (Patch
17147 from Ian Goldberg; implements the server side of Proposal 174.)
17148 - Tor now has initial support for automatic port mapping on the many
17149 home routers that support NAT-PMP or UPnP. (Not yet supported on
17150 Windows). To build the support code, you'll need to have libnatpnp
17151 library and/or the libminiupnpc library, and you'll need to enable the
17152 feature specifically by passing "--enable-upnp" and/or
17153 "--enable-natpnp" to configure. To turn it on, use the new
17154 PortForwarding option.
17155 - Caches now download, cache, and serve multiple "flavors" of the
17156 consensus, including a flavor that describes microdescriptors.
17157 - Caches now download, cache, and serve microdescriptors -- small
17158 summaries of router descriptors that are authenticated by all of the
17159 directory authorities. Once enough caches are running this code,
17160 clients will be able to save significant amounts of directory bandwidth
17161 by downloading microdescriptors instead of router descriptors.
17164 - Make logging resolution configurable with a new LogTimeGranularity
17165 option, and change the default from 1 millisecond to 1 second.
17166 Implements enhancement 1668.
17167 - We log which torrc file we're using on startup. Implements ticket
17169 - Ordinarily, Tor does not count traffic from private addresses (like
17170 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
17171 There is now a new option, CountPrivateBandwidth, to disable this
17172 behavior. Patch from Daniel Cagara.
17173 - New --enable-static-tor configure option for building Tor as
17174 statically as possible. Idea, general hackery and thoughts from
17175 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
17177 - If you set the NumCPUs option to 0, Tor will now try to detect how
17178 many CPUs you have. This is the new default behavior.
17179 - Turn on directory request statistics by default and include them in
17180 extra-info descriptors. Don't break if we have no GeoIP database.
17181 - Relays that set "ConnDirectionStatistics 1" write statistics on the
17182 bidirectional use of connections to disk every 24 hours.
17183 - Add a GeoIP file digest to the extra-info descriptor. Implements
17185 - The NodeFamily option -- which let you declare that you want to
17186 consider nodes to be part of a family whether they list themselves
17187 that way or not -- now allows IP address ranges and country codes.
17188 - Add a new 'Heartbeat' log message type to periodically log a message
17189 describing Tor's status at level Notice. This feature is meant for
17190 operators who log at notice, and want to make sure that their Tor
17191 server is still working. Implementation by George Kadianakis.
17193 o Minor bugfixes (on 0.2.2.25-alpha):
17194 - When loading the microdesc journal, remember its current size.
17195 In 0.2.2, this helps prevent the microdesc journal from growing
17196 without limit on authorities (who are the only ones to use it in
17197 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
17198 Fix posted by "cypherpunks."
17199 - The microdesc journal is supposed to get rebuilt only if it is
17200 at least _half_ the length of the store, not _twice_ the length
17201 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
17202 - If as an authority we fail to compute the identity digest of a v3
17203 legacy keypair, warn, and don't use a buffer-full of junk instead.
17204 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
17205 - Authorities now clean their microdesc cache periodically and when
17206 reading from disk initially, not only when adding new descriptors.
17207 This prevents a bug where we could lose microdescriptors. Bugfix
17210 o Minor features (controller):
17211 - Add a new SIGNAL event to the controller interface so that
17212 controllers can be notified when Tor handles a signal. Resolves
17213 issue 1955. Patch by John Brooks.
17214 - Add a new GETINFO option to get total bytes read and written. Patch
17215 from pipe, revised by atagar. Resolves ticket 2345.
17216 - Implement some GETINFO controller fields to provide information about
17217 the Tor process's pid, euid, username, and resource limits.
17220 - Our build system requires automake 1.6 or later to create the
17221 Makefile.in files. Previously, you could have used 1.4.
17222 This only affects developers and people building Tor from git;
17223 people who build Tor from the source distribution without changing
17224 the Makefile.am files should be fine.
17225 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
17226 so on. This is more robust against some of the failure modes
17227 associated with running the autotools pieces on their own.
17229 o Minor packaging issues:
17230 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
17231 already created. Patch from Andreas Stieger. Fixes bug 2573.
17233 o Code simplifications and refactoring:
17234 - A major revision to our internal node-selecting and listing logic.
17235 Tor already had at least two major ways to look at the question of
17236 "which Tor servers do we know about": a list of router descriptors,
17237 and a list of entries in the current consensus. With
17238 microdescriptors, we're adding a third. Having so many systems
17239 without an abstraction layer over them was hurting the codebase.
17240 Now, we have a new "node_t" abstraction that presents a consistent
17241 interface to a client's view of a Tor node, and holds (nearly) all
17242 of the mutable state formerly in routerinfo_t and routerstatus_t.
17243 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
17244 no longer link against Libevent: they never used it, but
17245 our library structure used to force them to link it.
17247 o Removed features:
17248 - Remove some old code to work around even older versions of Tor that
17249 used forked processes to handle DNS requests. Such versions of Tor
17250 are no longer in use as servers.
17252 o Documentation fixes:
17253 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
17254 - Add missing documentation for the authority-related torrc options
17255 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
17259 Changes in version 0.2.2.25-alpha - 2011-04-29
17260 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
17261 robust, routers no longer overreport their bandwidth, Win7 should crash
17262 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
17263 now prevents hidden service-related activity from being linkable. It
17264 provides more information to Vidalia so you can see if your bridge is
17265 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
17266 StrictNodes configuration options to make them more reliable, more
17267 understandable, and more regularly applied. If you use those options,
17268 please see the revised documentation for them in the manual page.
17271 - Relays were publishing grossly inflated bandwidth values because
17272 they were writing their state files wrong--now they write the
17273 correct value. Also, resume reading bandwidth history from the
17274 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
17275 - Improve hidden service robustness: When we find that we have
17276 extended a hidden service's introduction circuit to a relay not
17277 listed as an introduction point in the HS descriptor we currently
17278 have, retry with an introduction point from the current
17279 descriptor. Previously we would just give up. Fixes bugs 1024 and
17280 1930; bugfix on 0.2.0.10-alpha.
17281 - Clients now stop trying to use an exit node associated with a given
17282 destination by TrackHostExits if they fail to reach that exit node.
17283 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
17284 - Fix crash bug on platforms where gmtime and localtime can return
17285 NULL. Windows 7 users were running into this one. Fixes part of bug
17286 2077. Bugfix on all versions of Tor. Found by boboper.
17288 o Security and stability fixes:
17289 - Don't double-free a parsable, but invalid, microdescriptor, even if
17290 it is followed in the blob we're parsing by an unparsable
17291 microdescriptor. Fixes an issue reported in a comment on bug 2954.
17292 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
17293 - If the Nickname configuration option isn't given, Tor would pick a
17294 nickname based on the local hostname as the nickname for a relay.
17295 Because nicknames are not very important in today's Tor and the
17296 "Unnamed" nickname has been implemented, this is now problematic
17297 behavior: It leaks information about the hostname without being
17298 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
17299 introduced the Unnamed nickname. Reported by tagnaq.
17300 - Fix an uncommon assertion failure when running with DNSPort under
17301 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
17302 - Avoid linkability based on cached hidden service descriptors: forget
17303 all hidden service descriptors cached as a client when processing a
17304 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
17307 - Export GeoIP information on bridge usage to controllers even if we
17308 have not yet been running for 24 hours. Now Vidalia bridge operators
17309 can get more accurate and immediate feedback about their
17310 contributions to the network.
17312 o Major features and bugfixes (node selection):
17313 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
17314 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
17315 options. Previously, we had been ambiguous in describing what
17316 counted as an "exit" node, and what operations exactly "StrictNodes
17317 0" would permit. This created confusion when people saw nodes built
17318 through unexpected circuits, and made it hard to tell real bugs from
17319 surprises. Now the intended behavior is:
17320 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
17321 a node that delivers user traffic outside the Tor network.
17322 . "Entry", in the context of EntryNodes, means a node used as the
17323 first hop of a multihop circuit. It doesn't include direct
17324 connections to directory servers.
17325 . "ExcludeNodes" applies to all nodes.
17326 . "StrictNodes" changes the behavior of ExcludeNodes only. When
17327 StrictNodes is set, Tor should avoid all nodes listed in
17328 ExcludeNodes, even when it will make user requests fail. When
17329 StrictNodes is *not* set, then Tor should follow ExcludeNodes
17330 whenever it can, except when it must use an excluded node to
17331 perform self-tests, connect to a hidden service, provide a
17332 hidden service, fulfill a .exit request, upload directory
17333 information, or fetch directory information.
17334 Collectively, the changes to implement the behavior fix bug 1090.
17335 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
17336 a node is listed in both, it's treated as excluded.
17337 - ExcludeNodes now applies to directory nodes -- as a preference if
17338 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
17339 Don't exclude all the directory authorities and set StrictNodes to 1
17340 unless you really want your Tor to break.
17341 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
17342 - ExcludeExitNodes now overrides .exit requests.
17343 - We don't use bridges listed in ExcludeNodes.
17344 - When StrictNodes is 1:
17345 . We now apply ExcludeNodes to hidden service introduction points
17346 and to rendezvous points selected by hidden service users. This
17347 can make your hidden service less reliable: use it with caution!
17348 . If we have used ExcludeNodes on ourself, do not try relay
17349 reachability self-tests.
17350 . If we have excluded all the directory authorities, we will not
17351 even try to upload our descriptor if we're a relay.
17352 . Do not honor .exit requests to an excluded node.
17353 - Remove a misfeature that caused us to ignore the Fast/Stable flags
17354 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
17355 - When the set of permitted nodes changes, we now remove any mappings
17356 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
17358 - We never cannibalize a circuit that had excluded nodes on it, even
17359 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
17360 - Revert a change where we would be laxer about attaching streams to
17361 circuits than when building the circuits. This was meant to prevent
17362 a set of bugs where streams were never attachable, but our improved
17363 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
17364 - Keep track of how many times we launch a new circuit to handle a
17365 given stream. Too many launches could indicate an inconsistency
17366 between our "launch a circuit to handle this stream" logic and our
17367 "attach this stream to one of the available circuits" logic.
17368 - Improve log messages related to excluded nodes.
17371 - Fix a spurious warning when moving from a short month to a long
17372 month on relays with month-based BandwidthAccounting. Bugfix on
17373 0.2.2.17-alpha; fixes bug 3020.
17374 - When a client finds that an origin circuit has run out of 16-bit
17375 stream IDs, we now mark it as unusable for new streams. Previously,
17376 we would try to close the entire circuit. Bugfix on 0.0.6.
17377 - Add a forgotten cast that caused a compile warning on OS X 10.6.
17378 Bugfix on 0.2.2.24-alpha.
17379 - Be more careful about reporting the correct error from a failed
17380 connect() system call. Under some circumstances, it was possible to
17381 look at an incorrect value for errno when sending the end reason.
17382 Bugfix on 0.1.0.1-rc.
17383 - Correctly handle an "impossible" overflow cases in connection byte
17384 counting, where we write or read more than 4GB on an edge connection
17385 in a single second. Bugfix on 0.1.2.8-beta.
17386 - Correct the warning displayed when a rendezvous descriptor exceeds
17387 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
17389 - Clients and hidden services now use HSDir-flagged relays for hidden
17390 service descriptor downloads and uploads even if the relays have no
17391 DirPort set and the client has disabled TunnelDirConns. This will
17392 eventually allow us to give the HSDir flag to relays with no
17393 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
17394 - Downgrade "no current certificates known for authority" message from
17395 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
17396 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
17397 2917. Bugfix on 0.1.1.1-alpha.
17398 - Only limit the lengths of single HS descriptors, even when multiple
17399 HS descriptors are published to an HSDir relay in a single POST
17400 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
17401 - Write the current time into the LastWritten line in our state file,
17402 rather than the time from the previous write attempt. Also, stop
17403 trying to use a time of -1 in our log statements. Fixes bug 3039;
17404 bugfix on 0.2.2.14-alpha.
17405 - Be more consistent in our treatment of file system paths. "~" should
17406 get expanded to the user's home directory in the Log config option.
17407 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
17408 feature for the -f and --DataDirectory options.
17411 - Make sure every relay writes a state file at least every 12 hours.
17412 Previously, a relay could go for weeks without writing its state
17413 file, and on a crash could lose its bandwidth history, capacity
17414 estimates, client country statistics, and so on. Addresses bug 3012.
17415 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
17416 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
17417 clients are already deprecated because of security bugs.
17418 - Don't allow v0 hidden service authorities to act as clients.
17419 Required by fix for bug 3000.
17420 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
17421 by fix for bug 3000.
17422 - Ensure that no empty [dirreq-](read|write)-history lines are added
17423 to an extrainfo document. Implements ticket 2497.
17425 o Code simplification and refactoring:
17426 - Remove workaround code to handle directory responses from servers
17427 that had bug 539 (they would send HTTP status 503 responses _and_
17428 send a body too). Since only server versions before
17429 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
17430 keep the workaround in place.
17431 - Remove the old 'fuzzy time' logic. It was supposed to be used for
17432 handling calculations where we have a known amount of clock skew and
17433 an allowed amount of unknown skew. But we only used it in three
17434 places, and we never adjusted the known/unknown skew values. This is
17435 still something we might want to do someday, but if we do, we'll
17436 want to do it differently.
17437 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
17438 None of the cases where we did this before were wrong, but by making
17439 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
17440 - Use GetTempDir to find the proper temporary directory location on
17441 Windows when generating temporary files for the unit tests. Patch by
17445 Changes in version 0.2.2.24-alpha - 2011-04-08
17446 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
17447 prevented Tor clients from effectively using "multihomed" bridges,
17448 that is, bridges that listen on multiple ports or IP addresses so users
17449 can continue to use some of their addresses even if others get blocked.
17452 - Fix a bug where bridge users who configure the non-canonical
17453 address of a bridge automatically switch to its canonical
17454 address. If a bridge listens at more than one address, it should be
17455 able to advertise those addresses independently and any non-blocked
17456 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
17458 - If you configured Tor to use bridge A, and then quit and
17459 configured Tor to use bridge B instead, it would happily continue
17460 to use bridge A if it's still reachable. While this behavior is
17461 a feature if your goal is connectivity, in some scenarios it's a
17462 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
17463 - Directory authorities now use data collected from their own
17464 uptime observations when choosing whether to assign the HSDir flag
17465 to relays, instead of trusting the uptime value the relay reports in
17466 its descriptor. This change helps prevent an attack where a small
17467 set of nodes with frequently-changing identity keys can blackhole
17468 a hidden service. (Only authorities need upgrade; others will be
17469 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
17472 - When we restart our relay, we might get a successful connection
17473 from the outside before we've started our reachability tests,
17474 triggering a warning: "ORPort found reachable, but I have no
17475 routerinfo yet. Failing to inform controller of success." This
17476 bug was harmless unless Tor is running under a controller
17477 like Vidalia, in which case the controller would never get a
17478 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
17480 - Make directory authorities more accurate at recording when
17481 relays that have failed several reachability tests became
17482 unreachable, so we can provide more accuracy at assigning Stable,
17483 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
17484 - Fix an issue that prevented static linking of libevent on
17485 some platforms (notably Linux). Fixes bug 2698; bugfix on
17486 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
17487 the --with-static-libevent configure option).
17488 - We now ask the other side of a stream (the client or the exit)
17489 for more data on that stream when the amount of queued data on
17490 that stream dips low enough. Previously, we wouldn't ask the
17491 other side for more data until either it sent us more data (which
17492 it wasn't supposed to do if it had exhausted its window!) or we
17493 had completely flushed all our queued data. This flow control fix
17494 should improve throughput. Fixes bug 2756; bugfix on the earliest
17495 released versions of Tor (svn commit r152).
17496 - Avoid a double-mark-for-free warning when failing to attach a
17497 transparent proxy connection. (We thought we had fixed this in
17498 0.2.2.23-alpha, but it turns out our fix was checking the wrong
17499 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
17500 bug) and 0.2.2.23-alpha (the incorrect fix).
17501 - When warning about missing zlib development packages during compile,
17502 give the correct package names. Bugfix on 0.2.0.1-alpha.
17505 - Directory authorities now log the source of a rejected POSTed v3
17506 networkstatus vote.
17507 - Make compilation with clang possible when using
17508 --enable-gcc-warnings by removing two warning options that clang
17509 hasn't implemented yet and by fixing a few warnings. Implements
17511 - When expiring circuits, use microsecond timers rather than
17512 one-second timers. This can avoid an unpleasant situation where a
17513 circuit is launched near the end of one second and expired right
17514 near the beginning of the next, and prevent fluctuations in circuit
17516 - Use computed circuit-build timeouts to decide when to launch
17517 parallel introduction circuits for hidden services. (Previously,
17518 we would retry after 15 seconds.)
17519 - Update to the April 1 2011 Maxmind GeoLite Country database.
17522 - Create the /var/run/tor directory on startup on OpenSUSE if it is
17523 not already created. Patch from Andreas Stieger. Fixes bug 2573.
17525 o Documentation changes:
17526 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
17527 - Resolve all doxygen warnings except those for missing documentation.
17529 - Add doxygen documentation for more functions, fields, and types.
17532 Changes in version 0.2.2.23-alpha - 2011-03-08
17533 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
17534 they restart they don't lose their bandwidth capacity estimate. This
17535 release also fixes a diverse set of user-facing bugs, ranging from
17536 relays overrunning their rate limiting to clients falsely warning about
17537 clock skew to bridge descriptor leaks by our bridge directory authority.
17540 - Stop sending a CLOCK_SKEW controller status event whenever
17541 we fetch directory information from a relay that has a wrong clock.
17542 Instead, only inform the controller when it's a trusted authority
17543 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
17544 the rest of bug 1074.
17545 - Fix an assert in parsing router descriptors containing IPv6
17546 addresses. This one took down the directory authorities when
17547 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
17548 - Make the bridge directory authority refuse to answer directory
17549 requests for "all" descriptors. It used to include bridge
17550 descriptors in its answer, which was a major information leak.
17551 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
17552 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
17553 Tor would ignore their RelayBandwidthBurst setting,
17554 potentially using more bandwidth than expected. Bugfix on
17555 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
17556 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
17557 hidserv" in her torrc. The 'hidserv' argument never controlled
17558 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
17561 - Relays now save observed peak bandwidth throughput rates to their
17562 state file (along with total usage, which was already saved)
17563 so that they can determine their correct estimated bandwidth on
17564 restart. Resolves bug 1863, where Tor relays would reset their
17565 estimated bandwidth to 0 after restarting.
17566 - Directory authorities now take changes in router IP address and
17567 ORPort into account when determining router stability. Previously,
17568 if a router changed its IP or ORPort, the authorities would not
17569 treat it as having any downtime for the purposes of stability
17570 calculation, whereas clients would experience downtime since the
17571 change could take a while to propagate to them. Resolves issue 1035.
17572 - Enable Address Space Layout Randomization (ASLR) and Data Execution
17573 Prevention (DEP) by default on Windows to make it harder for
17574 attackers to exploit vulnerabilities. Patch from John Brooks.
17576 o Minor bugfixes (on 0.2.1.x and earlier):
17577 - Fix a rare crash bug that could occur when a client was configured
17578 with a large number of bridges. Fixes bug 2629; bugfix on
17579 0.2.1.2-alpha. Bugfix by trac user "shitlei".
17580 - Avoid a double mark-for-free warning when failing to attach a
17581 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
17583 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
17584 found by "cypherpunks". This bug was introduced before the first
17585 Tor release, in svn commit r110.
17586 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
17587 don't mention them in the manpage. Fixes bug 2450; issue
17588 spotted by keb and G-Lo.
17589 - Fix a bug in bandwidth history state parsing that could have been
17590 triggered if a future version of Tor ever changed the timing
17591 granularity at which bandwidth history is measured. Bugfix on
17592 Tor 0.1.1.11-alpha.
17593 - When a relay decides that its DNS is too broken for it to serve
17594 as an exit server, it advertised itself as a non-exit, but
17595 continued to act as an exit. This could create accidental
17596 partitioning opportunities for users. Instead, if a relay is
17597 going to advertise reject *:* as its exit policy, it should
17598 really act with exit policy "reject *:*". Fixes bug 2366.
17599 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
17600 - In the special case where you configure a public exit relay as your
17601 bridge, Tor would be willing to use that exit relay as the last
17602 hop in your circuit as well. Now we fail that circuit instead.
17603 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
17604 - Fix a bug with our locking implementation on Windows that couldn't
17605 correctly detect when a file was already locked. Fixes bug 2504,
17606 bugfix on 0.2.1.6-alpha.
17607 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
17608 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
17610 - Set target port in get_interface_address6() correctly. Bugfix
17611 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
17612 - Directory authorities are now more robust to hops back in time
17613 when calculating router stability. Previously, if a run of uptime
17614 or downtime appeared to be negative, the calculation could give
17615 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
17617 - Fix an assert that got triggered when using the TestingTorNetwork
17618 configuration option and then issuing a GETINFO config-text control
17619 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
17621 o Minor bugfixes (on 0.2.2.x):
17622 - Clients should not weight BadExit nodes as Exits in their node
17623 selection. Similarly, directory authorities should not count BadExit
17624 bandwidth as Exit bandwidth when computing bandwidth-weights.
17625 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
17626 - Correctly clear our dir_read/dir_write history when there is an
17627 error parsing any bw history value from the state file. Bugfix on
17628 Tor 0.2.2.15-alpha.
17629 - Resolve a bug in verifying signatures of directory objects
17630 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
17631 Fixes bug 2409. Found by "piebeer".
17632 - Bridge authorities no longer crash on SIGHUP when they try to
17633 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
17637 - Log less aggressively about circuit timeout changes, and improve
17638 some other circuit timeout messages. Resolves bug 2004.
17639 - Log a little more clearly about the times at which we're no longer
17640 accepting new connections. Resolves bug 2181.
17641 - Reject attempts at the client side to open connections to private
17642 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
17643 a randomly chosen exit node. Attempts to do so are always
17644 ill-defined, generally prevented by exit policies, and usually
17645 in error. This will also help to detect loops in transparent
17646 proxy configurations. You can disable this feature by setting
17647 "ClientRejectInternalAddresses 0" in your torrc.
17648 - Always treat failure to allocate an RSA key as an unrecoverable
17650 - Update to the March 1 2011 Maxmind GeoLite Country database.
17652 o Minor features (log subsystem):
17653 - Add documentation for configuring logging at different severities in
17654 different log domains. We've had this feature since 0.2.1.1-alpha,
17655 but for some reason it never made it into the manpage. Fixes
17657 - Make it simpler to specify "All log domains except for A and B".
17658 Previously you needed to say "[*,~A,~B]". Now you can just say
17660 - Add a "LogMessageDomains 1" option to include the domains of log
17661 messages along with the messages. Without this, there's no way
17662 to use log domains without reading the source or doing a lot
17665 o Packaging changes:
17666 - Stop shipping the Tor specs files and development proposal documents
17667 in the tarball. They are now in a separate git repository at
17668 git://git.torproject.org/torspec.git
17671 Changes in version 0.2.1.30 - 2011-02-23
17672 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
17673 change is a slight tweak to Tor's TLS handshake that makes relays
17674 and bridges that run this new version reachable from Iran again.
17675 We don't expect this tweak will win the arms race long-term, but it
17676 buys us time until we roll out a better solution.
17679 - Stop sending a CLOCK_SKEW controller status event whenever
17680 we fetch directory information from a relay that has a wrong clock.
17681 Instead, only inform the controller when it's a trusted authority
17682 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
17683 the rest of bug 1074.
17684 - Fix a bounds-checking error that could allow an attacker to
17685 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
17686 Found by "piebeer".
17687 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
17688 Tor would ignore their RelayBandwidthBurst setting,
17689 potentially using more bandwidth than expected. Bugfix on
17690 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
17691 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
17692 hidserv" in her torrc. The 'hidserv' argument never controlled
17693 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
17696 - Adjust our TLS Diffie-Hellman parameters to match those used by
17698 - Update to the February 1 2011 Maxmind GeoLite Country database.
17701 - Check for and reject overly long directory certificates and
17702 directory tokens before they have a chance to hit any assertions.
17703 Bugfix on 0.2.1.28. Found by "doorss".
17704 - Bring the logic that gathers routerinfos and assesses the
17705 acceptability of circuits into line. This prevents a Tor OP from
17706 getting locked in a cycle of choosing its local OR as an exit for a
17707 path (due to a .exit request) and then rejecting the circuit because
17708 its OR is not listed yet. It also prevents Tor clients from using an
17709 OR running in the same instance as an exit (due to a .exit request)
17710 if the OR does not meet the same requirements expected of an OR
17711 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
17713 o Packaging changes:
17714 - Stop shipping the Tor specs files and development proposal documents
17715 in the tarball. They are now in a separate git repository at
17716 git://git.torproject.org/torspec.git
17717 - Do not include Git version tags as though they are SVN tags when
17718 generating a tarball from inside a repository that has switched
17719 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
17722 Changes in version 0.2.2.22-alpha - 2011-01-25
17723 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
17724 main other change is a slight tweak to Tor's TLS handshake that makes
17725 relays and bridges that run this new version reachable from Iran again.
17726 We don't expect this tweak will win the arms race long-term, but it
17727 will buy us a bit more time until we roll out a better solution.
17730 - Fix a bounds-checking error that could allow an attacker to
17731 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
17732 Found by "piebeer".
17733 - Don't assert when changing from bridge to relay or vice versa
17734 via the controller. The assert happened because we didn't properly
17735 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
17736 bug 2433. Reported by bastik.
17739 - Adjust our TLS Diffie-Hellman parameters to match those used by
17741 - Provide a log message stating which geoip file we're parsing
17742 instead of just stating that we're parsing the geoip file.
17743 Implements ticket 2432.
17746 - Check for and reject overly long directory certificates and
17747 directory tokens before they have a chance to hit any assertions.
17748 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
17751 Changes in version 0.2.2.21-alpha - 2011-01-15
17752 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
17753 continues our recent code security audit work. The main fix resolves
17754 a remote heap overflow vulnerability that can allow remote code
17755 execution (CVE-2011-0427). Other fixes address a variety of assert
17756 and crash bugs, most of which we think are hard to exploit remotely.
17758 o Major bugfixes (security), also included in 0.2.1.29:
17759 - Fix a heap overflow bug where an adversary could cause heap
17760 corruption. This bug probably allows remote code execution
17761 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
17763 - Prevent a denial-of-service attack by disallowing any
17764 zlib-compressed data whose compression factor is implausibly
17765 high. Fixes part of bug 2324; reported by "doorss".
17766 - Zero out a few more keys in memory before freeing them. Fixes
17767 bug 2384 and part of bug 2385. These key instances found by
17768 "cypherpunks", based on Andrew Case's report about being able
17769 to find sensitive data in Tor's memory space if you have enough
17770 permissions. Bugfix on 0.0.2pre9.
17772 o Major bugfixes (crashes), also included in 0.2.1.29:
17773 - Prevent calls to Libevent from inside Libevent log handlers.
17774 This had potential to cause a nasty set of crashes, especially
17775 if running Libevent with debug logging enabled, and running
17776 Tor with a controller watching for low-severity log messages.
17777 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
17778 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
17779 underflow errors there too. Fixes the other part of bug 2324.
17780 - Fix a bug where we would assert if we ever had a
17781 cached-descriptors.new file (or another file read directly into
17782 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
17783 on 0.2.1.25. Found by doorss.
17784 - Fix some potential asserts and parsing issues with grossly
17785 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
17788 o Minor bugfixes (other), also included in 0.2.1.29:
17789 - Fix a bug with handling misformed replies to reverse DNS lookup
17790 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
17791 bug reported by doorss.
17792 - Fix compilation on mingw when a pthreads compatibility library
17793 has been installed. (We don't want to use it, so we shouldn't
17794 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
17795 - Fix a bug where we would declare that we had run out of virtual
17796 addresses when the address space was only half-exhausted. Bugfix
17798 - Correctly handle the case where AutomapHostsOnResolve is set but
17799 no virtual addresses are available. Fixes bug 2328; bugfix on
17800 0.1.2.1-alpha. Bug found by doorss.
17801 - Correctly handle wrapping around when we run out of virtual
17802 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
17804 o Minor features, also included in 0.2.1.29:
17805 - Update to the January 1 2011 Maxmind GeoLite Country database.
17806 - Introduce output size checks on all of our decryption functions.
17808 o Build changes, also included in 0.2.1.29:
17809 - Tor does not build packages correctly with Automake 1.6 and earlier;
17810 added a check to Makefile.am to make sure that we're building with
17811 Automake 1.7 or later.
17812 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
17813 because we built it with a too-old version of automake. Thus that
17814 release broke ./configure --enable-openbsd-malloc, which is popular
17815 among really fast exit relays on Linux.
17817 o Major bugfixes, new in 0.2.2.21-alpha:
17818 - Prevent crash/heap corruption when the cbtnummodes consensus
17819 parameter is set to 0 or large values. Fixes bug 2317; bugfix
17822 o Major features, new in 0.2.2.21-alpha:
17823 - Introduce minimum/maximum values that clients will believe
17824 from the consensus. Now we'll have a better chance to avoid crashes
17825 or worse when a consensus param has a weird value.
17827 o Minor features, new in 0.2.2.21-alpha:
17828 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
17829 used on bridges, and it makes bridge scanning somewhat easier.
17830 - If writing the state file to disk fails, wait up to an hour before
17831 retrying again, rather than trying again each second. Fixes bug
17832 2346; bugfix on Tor 0.1.1.3-alpha.
17833 - Make Libevent log messages get delivered to controllers later,
17834 and not from inside the Libevent log handler. This prevents unsafe
17835 reentrant Libevent calls while still letting the log messages
17837 - Detect platforms that brokenly use a signed size_t, and refuse to
17838 build there. Found and analyzed by doorss and rransom.
17839 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
17842 o Minor bugfixes, new in 0.2.2.21-alpha:
17843 - Handle SOCKS messages longer than 128 bytes long correctly, rather
17844 than waiting forever for them to finish. Fixes bug 2330; bugfix
17845 on 0.2.0.16-alpha. Found by doorss.
17846 - Add assertions to check for overflow in arguments to
17847 base32_encode() and base32_decode(); fix a signed-unsigned
17848 comparison there too. These bugs are not actually reachable in Tor,
17849 but it's good to prevent future errors too. Found by doorss.
17850 - Correctly detect failures to create DNS requests when using Libevent
17851 versions before v2. (Before Libevent 2, we used our own evdns
17852 implementation. Its return values for Libevent's evdns_resolve_*()
17853 functions are not consistent with those from Libevent.) Fixes bug
17854 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
17856 o Documentation, new in 0.2.2.21-alpha:
17857 - Document the default socks host and port (127.0.0.1:9050) for
17861 Changes in version 0.2.1.29 - 2011-01-15
17862 Tor 0.2.1.29 continues our recent code security audit work. The main
17863 fix resolves a remote heap overflow vulnerability that can allow remote
17864 code execution. Other fixes address a variety of assert and crash bugs,
17865 most of which we think are hard to exploit remotely.
17867 o Major bugfixes (security):
17868 - Fix a heap overflow bug where an adversary could cause heap
17869 corruption. This bug probably allows remote code execution
17870 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
17872 - Prevent a denial-of-service attack by disallowing any
17873 zlib-compressed data whose compression factor is implausibly
17874 high. Fixes part of bug 2324; reported by "doorss".
17875 - Zero out a few more keys in memory before freeing them. Fixes
17876 bug 2384 and part of bug 2385. These key instances found by
17877 "cypherpunks", based on Andrew Case's report about being able
17878 to find sensitive data in Tor's memory space if you have enough
17879 permissions. Bugfix on 0.0.2pre9.
17881 o Major bugfixes (crashes):
17882 - Prevent calls to Libevent from inside Libevent log handlers.
17883 This had potential to cause a nasty set of crashes, especially
17884 if running Libevent with debug logging enabled, and running
17885 Tor with a controller watching for low-severity log messages.
17886 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
17887 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
17888 underflow errors there too. Fixes the other part of bug 2324.
17889 - Fix a bug where we would assert if we ever had a
17890 cached-descriptors.new file (or another file read directly into
17891 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
17892 on 0.2.1.25. Found by doorss.
17893 - Fix some potential asserts and parsing issues with grossly
17894 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
17897 o Minor bugfixes (other):
17898 - Fix a bug with handling misformed replies to reverse DNS lookup
17899 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
17900 bug reported by doorss.
17901 - Fix compilation on mingw when a pthreads compatibility library
17902 has been installed. (We don't want to use it, so we shouldn't
17903 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
17904 - Fix a bug where we would declare that we had run out of virtual
17905 addresses when the address space was only half-exhausted. Bugfix
17907 - Correctly handle the case where AutomapHostsOnResolve is set but
17908 no virtual addresses are available. Fixes bug 2328; bugfix on
17909 0.1.2.1-alpha. Bug found by doorss.
17910 - Correctly handle wrapping around to when we run out of virtual
17911 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
17912 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
17913 because we built it with a too-old version of automake. Thus that
17914 release broke ./configure --enable-openbsd-malloc, which is popular
17915 among really fast exit relays on Linux.
17918 - Update to the January 1 2011 Maxmind GeoLite Country database.
17919 - Introduce output size checks on all of our decryption functions.
17922 - Tor does not build packages correctly with Automake 1.6 and earlier;
17923 added a check to Makefile.am to make sure that we're building with
17924 Automake 1.7 or later.
17927 Changes in version 0.2.2.20-alpha - 2010-12-17
17928 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
17929 exploitable bugs. We also fix a variety of other significant bugs,
17930 change the IP address for one of our directory authorities, and update
17931 the minimum version that Tor relays must run to join the network.
17934 - Fix a remotely exploitable bug that could be used to crash instances
17935 of Tor remotely by overflowing on the heap. Remote-code execution
17936 hasn't been confirmed, but can't be ruled out. Everyone should
17937 upgrade. Bugfix on the 0.1.1 series and later.
17938 - Fix a bug that could break accounting on 64-bit systems with large
17939 time_t values, making them hibernate for impossibly long intervals.
17940 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
17941 - Fix a logic error in directory_fetches_from_authorities() that
17942 would cause all _non_-exits refusing single-hop-like circuits
17943 to fetch from authorities, when we wanted to have _exits_ fetch
17944 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
17946 - Fix a stream fairness bug that would cause newer streams on a given
17947 circuit to get preference when reading bytes from the origin or
17948 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
17949 introduced before the first Tor release, in svn revision r152.
17951 o Directory authority changes:
17952 - Change IP address and ports for gabelmoo (v3 directory authority).
17955 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
17956 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
17957 - Fix an off-by-one error in calculating some controller command
17958 argument lengths. Fortunately, this mistake is harmless since
17959 the controller code does redundant NUL termination too. Found by
17960 boboper. Bugfix on 0.1.1.1-alpha.
17961 - Do not dereference NULL if a bridge fails to build its
17962 extra-info descriptor. Found by an anonymous commenter on
17963 Trac. Bugfix on 0.2.2.19-alpha.
17966 - Update to the December 1 2010 Maxmind GeoLite Country database.
17967 - Directory authorities now reject relays running any versions of
17968 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
17969 known bugs that keep RELAY_EARLY cells from working on rendezvous
17970 circuits. Followup to fix for bug 2081.
17971 - Directory authorities now reject relays running any version of Tor
17972 older than 0.2.0.26-rc. That version is the earliest that fetches
17973 current directory information correctly. Fixes bug 2156.
17974 - Report only the top 10 ports in exit-port stats in order not to
17975 exceed the maximum extra-info descriptor length of 50 KB. Implements
17979 Changes in version 0.2.1.28 - 2010-12-17
17980 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
17981 exploitable bugs. We also took this opportunity to change the IP address
17982 for one of our directory authorities, and to update the geoip database
17986 - Fix a remotely exploitable bug that could be used to crash instances
17987 of Tor remotely by overflowing on the heap. Remote-code execution
17988 hasn't been confirmed, but can't be ruled out. Everyone should
17989 upgrade. Bugfix on the 0.1.1 series and later.
17991 o Directory authority changes:
17992 - Change IP address and ports for gabelmoo (v3 directory authority).
17995 - Update to the December 1 2010 Maxmind GeoLite Country database.
17998 Changes in version 0.2.1.27 - 2010-11-23
17999 Yet another OpenSSL security patch broke its compatibility with Tor:
18000 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
18001 also took this opportunity to fix several crash bugs, integrate a new
18002 directory authority, and update the bundled GeoIP database.
18005 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18006 No longer set the tlsext_host_name extension on server SSL objects;
18007 but continue to set it on client SSL objects. Our goal in setting
18008 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18009 bugfix on 0.2.1.1-alpha.
18010 - Do not log messages to the controller while shrinking buffer
18011 freelists. Doing so would sometimes make the controller connection
18012 try to allocate a buffer chunk, which would mess up the internals
18013 of the freelist and cause an assertion failure. Fixes bug 1125;
18014 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18015 - Learn our external IP address when we're a relay or bridge, even if
18016 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18017 where we introduced bridge relays that don't need to publish to
18018 be useful. Fixes bug 2050.
18019 - Do even more to reject (and not just ignore) annotations on
18020 router descriptors received anywhere but from the cache. Previously
18021 we would ignore such annotations at first, but cache them to disk
18022 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18023 - When you're using bridges and your network goes away and your
18024 bridges get marked as down, recover when you attempt a new socks
18025 connection (if the network is back), rather than waiting up to an
18026 hour to try fetching new descriptors for your bridges. Bugfix on
18027 0.2.0.3-alpha; fixes bug 1981.
18030 - Move to the November 2010 Maxmind GeoLite country db (rather
18031 than the June 2009 ip-to-country GeoIP db) for our statistics that
18032 count how many users relays are seeing from each country. Now we'll
18033 have more accurate data, especially for many African countries.
18035 o New directory authorities:
18036 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
18040 - Fix an assertion failure that could occur in directory caches or
18041 bridge users when using a very short voting interval on a testing
18042 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
18044 - Enforce multiplicity rules when parsing annotations. Bugfix on
18045 0.2.0.8-alpha. Found by piebeer.
18046 - Allow handshaking OR connections to take a full KeepalivePeriod
18047 seconds to handshake. Previously, we would close them after
18048 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
18049 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
18051 - When building with --enable-gcc-warnings on OpenBSD, disable
18052 warnings in system headers. This makes --enable-gcc-warnings
18053 pass on OpenBSD 4.8.
18056 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
18057 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
18058 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
18059 Servers can start sending this code when enough clients recognize
18060 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
18061 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
18062 Patch from mingw-san.
18065 - Remove the old debian/ directory from the main Tor distribution.
18066 The official Tor-for-debian git repository lives at the URL
18067 https://git.torproject.org/debian/tor.git
18068 - Stop shipping the old doc/website/ directory in the tarball. We
18069 changed the website format in late 2010, and what we shipped in
18070 0.2.1.26 really wasn't that useful anyway.
18073 Changes in version 0.2.2.19-alpha - 2010-11-22
18074 Yet another OpenSSL security patch broke its compatibility with Tor:
18075 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
18078 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18079 No longer set the tlsext_host_name extension on server SSL objects;
18080 but continue to set it on client SSL objects. Our goal in setting
18081 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18082 bugfix on 0.2.1.1-alpha.
18085 - Try harder not to exceed the maximum length of 50 KB when writing
18086 statistics to extra-info descriptors. This bug was triggered by very
18087 fast relays reporting exit-port, entry, and dirreq statistics.
18088 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
18089 - Publish a router descriptor even if generating an extra-info
18090 descriptor fails. Previously we would not publish a router
18091 descriptor without an extra-info descriptor; this can cause fast
18092 exit relays collecting exit-port statistics to drop from the
18093 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
18096 Changes in version 0.2.2.18-alpha - 2010-11-16
18097 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
18098 us lately, makes unpublished bridge relays able to detect their IP
18099 address, and fixes a wide variety of other bugs to get us much closer
18100 to a stable release.
18103 - Do even more to reject (and not just ignore) annotations on
18104 router descriptors received anywhere but from the cache. Previously
18105 we would ignore such annotations at first, but cache them to disk
18106 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18107 - Do not log messages to the controller while shrinking buffer
18108 freelists. Doing so would sometimes make the controller connection
18109 try to allocate a buffer chunk, which would mess up the internals
18110 of the freelist and cause an assertion failure. Fixes bug 1125;
18111 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18112 - Learn our external IP address when we're a relay or bridge, even if
18113 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18114 where we introduced bridge relays that don't need to publish to
18115 be useful. Fixes bug 2050.
18116 - Maintain separate TLS contexts and certificates for incoming and
18117 outgoing connections in bridge relays. Previously we would use the
18118 same TLS contexts and certs for incoming and outgoing connections.
18119 Bugfix on 0.2.0.3-alpha; addresses bug 988.
18120 - Maintain separate identity keys for incoming and outgoing TLS
18121 contexts in bridge relays. Previously we would use the same
18122 identity keys for incoming and outgoing TLS contexts. Bugfix on
18123 0.2.0.3-alpha; addresses the other half of bug 988.
18124 - Avoid an assertion failure when we as an authority receive a
18125 duplicate upload of a router descriptor that we already have,
18126 but which we previously considered an obsolete descriptor.
18127 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
18128 - Avoid a crash bug triggered by looking at a dangling pointer while
18129 setting the network status consensus. Found by Robert Ransom.
18130 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
18131 - Fix a logic error where servers that _didn't_ act as exits would
18132 try to keep their server lists more aggressively up to date than
18133 exits, when it was supposed to be the other way around. Bugfix
18136 o Minor bugfixes (on Tor 0.2.1.x and earlier):
18137 - When we're trying to guess whether we know our IP address as
18138 a relay, we would log various ways that we failed to guess
18139 our address, but never log that we ended up guessing it
18140 successfully. Now add a log line to help confused and anxious
18141 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
18142 - Bring the logic that gathers routerinfos and assesses the
18143 acceptability of circuits into line. This prevents a Tor OP from
18144 getting locked in a cycle of choosing its local OR as an exit for a
18145 path (due to a .exit request) and then rejecting the circuit because
18146 its OR is not listed yet. It also prevents Tor clients from using an
18147 OR running in the same instance as an exit (due to a .exit request)
18148 if the OR does not meet the same requirements expected of an OR
18149 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
18150 - Correctly describe errors that occur when generating a TLS object.
18151 Previously we would attribute them to a failure while generating a
18152 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
18154 - Enforce multiplicity rules when parsing annotations. Bugfix on
18155 0.2.0.8-alpha. Found by piebeer.
18156 - Fix warnings that newer versions of autoconf produced during
18157 ./autogen.sh. These warnings appear to be harmless in our case,
18158 but they were extremely verbose. Fixes bug 2020.
18160 o Minor bugfixes (on Tor 0.2.2.x):
18161 - Enable protection of small arrays whenever we build with gcc
18162 hardening features, not only when also building with warnings
18163 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
18166 - Make hidden services work better in private Tor networks by not
18167 requiring any uptime to join the hidden service descriptor
18168 DHT. Implements ticket 2088.
18169 - Rate-limit the "your application is giving Tor only an IP address"
18170 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
18171 - When AllowSingleHopExits is set, print a warning to explain to the
18172 relay operator why most clients are avoiding her relay.
18173 - Update to the November 1 2010 Maxmind GeoLite Country database.
18175 o Code simplifications and refactoring:
18176 - When we fixed bug 1038 we had to put in a restriction not to send
18177 RELAY_EARLY cells on rend circuits. This was necessary as long
18178 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
18179 active. Now remove this obsolete check. Resolves bug 2081.
18180 - Some options used different conventions for uppercasing of acronyms
18181 when comparing manpage and source. Fix those in favor of the
18182 manpage, as it makes sense to capitalize acronyms.
18183 - Remove the torrc.complete file. It hasn't been kept up to date
18184 and users will have better luck checking out the manpage.
18185 - Remove the obsolete "NoPublish" option; it has been flagged
18186 as obsolete and has produced a warning since 0.1.1.18-rc.
18187 - Remove everything related to building the expert bundle for OS X.
18188 It has confused many users, doesn't work right on OS X 10.6,
18189 and is hard to get rid of once installed. Resolves bug 1274.
18192 Changes in version 0.2.2.17-alpha - 2010-09-30
18193 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
18194 to use one-hop circuits (which can put the exit relays at higher risk,
18195 plus unbalance the network); fixes a big bug in bandwidth accounting
18196 for relays that want to limit their monthly bandwidth use; fixes a
18197 big pile of bugs in how clients tolerate temporary network failure;
18198 and makes our adaptive circuit build timeout feature (which improves
18199 client performance if your network is fast while not breaking things
18200 if your network is slow) better handle bad networks.
18203 - Exit relays now try harder to block exit attempts from unknown
18204 relays, to make it harder for people to use them as one-hop proxies
18205 a la tortunnel. Controlled by the refuseunknownexits consensus
18206 parameter (currently enabled), or you can override it on your
18207 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
18209 o Major bugfixes (0.2.1.x and earlier):
18210 - Fix a bug in bandwidth accounting that could make us use twice
18211 the intended bandwidth when our interval start changes due to
18212 daylight saving time. Now we tolerate skew in stored vs computed
18213 interval starts: if the start of the period changes by no more than
18214 50% of the period's duration, we remember bytes that we transferred
18215 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
18216 - Always search the Windows system directory for system DLLs, and
18217 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
18218 - When you're using bridges and your network goes away and your
18219 bridges get marked as down, recover when you attempt a new socks
18220 connection (if the network is back), rather than waiting up to an
18221 hour to try fetching new descriptors for your bridges. Bugfix on
18222 0.2.0.3-alpha; fixes bug 1981.
18224 o Major bugfixes (on 0.2.2.x):
18225 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
18227 - Fix a segfault that could happen when operating a bridge relay with
18228 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
18229 - The consensus bandwidth-weights (used by clients to choose fast
18230 relays) entered an unexpected edge case in September where
18231 Exits were much scarcer than Guards, resulting in bad weight
18232 recommendations. Now we compute them using new constraints that
18233 should succeed in all cases. Also alter directory authorities to
18234 not include the bandwidth-weights line if they fail to produce
18235 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
18236 - When weighting bridges during path selection, we used to trust
18237 the bandwidths they provided in their descriptor, only capping them
18238 at 10MB/s. This turned out to be problematic for two reasons:
18239 Bridges could claim to handle a lot more traffic then they
18240 actually would, thus making more clients pick them and have a
18241 pretty effective DoS attack. The other issue is that new bridges
18242 that might not have a good estimate for their bw capacity yet
18243 would not get used at all unless no other bridges are available
18244 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
18246 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
18247 - Ignore cannibalized circuits when recording circuit build times.
18248 This should provide for a minor performance improvement for hidden
18249 service users using 0.2.2.14-alpha, and should remove two spurious
18250 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
18251 - Simplify the logic that causes us to decide if the network is
18252 unavailable for purposes of recording circuit build times. If we
18253 receive no cells whatsoever for the entire duration of a circuit's
18254 full measured lifetime, the network is probably down. Also ignore
18255 one-hop directory fetching circuit timeouts when calculating our
18256 circuit build times. These changes should hopefully reduce the
18257 cases where we see ridiculous circuit build timeouts for people
18258 with spotty wireless connections. Fixes part of bug 1772; bugfix
18260 - Prevent the circuit build timeout from becoming larger than
18261 the maximum build time we have ever seen. Also, prevent the time
18262 period for measurement circuits from becoming larger than twice that
18263 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
18266 - When we run out of directory information such that we can't build
18267 circuits, but then get enough that we can build circuits, log when
18268 we actually construct a circuit, so the user has a better chance of
18269 knowing what's going on. Fixes bug 1362.
18270 - Be more generous with how much bandwidth we'd use up (with
18271 accounting enabled) before entering "soft hibernation". Previously,
18272 we'd refuse new connections and circuits once we'd used up 95% of
18273 our allotment. Now, we use up 95% of our allotment, AND make sure
18274 that we have no more than 500MB (or 3 hours of expected traffic,
18275 whichever is lower) remaining before we enter soft hibernation.
18276 - If we've configured EntryNodes and our network goes away and/or all
18277 our entrynodes get marked down, optimistically retry them all when
18278 a new socks application request appears. Fixes bug 1882.
18279 - Add some more defensive programming for architectures that can't
18280 handle unaligned integer accesses. We don't know of any actual bugs
18281 right now, but that's the best time to fix them. Fixes bug 1943.
18282 - Support line continuations in the torrc config file. If a line
18283 ends with a single backslash character, the newline is ignored, and
18284 the configuration value is treated as continuing on the next line.
18287 o Minor bugfixes (on 0.2.1.x and earlier):
18288 - For bandwidth accounting, calculate our expected bandwidth rate
18289 based on the time during which we were active and not in
18290 soft-hibernation during the last interval. Previously, we were
18291 also considering the time spent in soft-hibernation. If this
18292 was a long time, we would wind up underestimating our bandwidth
18293 by a lot, and skewing our wakeup time towards the start of the
18294 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
18296 o Minor bugfixes (on 0.2.2.x):
18297 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
18298 which were disabled by the circuit build timeout changes in
18299 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
18300 - Make sure we don't warn about missing bandwidth weights when
18301 choosing bridges or other relays not in the consensus. Bugfix on
18302 0.2.2.10-alpha; fixes bug 1805.
18303 - In our logs, do not double-report signatures from unrecognized
18304 authorities both as "from unknown authority" and "not
18305 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
18308 Changes in version 0.2.2.16-alpha - 2010-09-17
18309 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
18310 evident at exit relays), and also continues to resolve all the little
18311 bugs that have been filling up trac lately.
18313 o Major bugfixes (stream-level fairness):
18314 - When receiving a circuit-level SENDME for a blocked circuit, try
18315 to package cells fairly from all the streams that had previously
18316 been blocked on that circuit. Previously, we had started with the
18317 oldest stream, and allowed each stream to potentially exhaust
18318 the circuit's package window. This gave older streams on any
18319 given circuit priority over newer ones. Fixes bug 1937. Detected
18320 originally by Camilo Viecco. This bug was introduced before the
18321 first Tor release, in svn commit r152: it is the new winner of
18322 the longest-lived bug prize.
18323 - When the exit relay got a circuit-level sendme cell, it started
18324 reading on the exit streams, even if had 500 cells queued in the
18325 circuit queue already, so the circuit queue just grew and grew in
18326 some cases. We fix this by not re-enabling reading on receipt of a
18327 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
18328 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
18330 - Newly created streams were allowed to read cells onto circuits,
18331 even if the circuit's cell queue was blocked and waiting to drain.
18332 This created potential unfairness, as older streams would be
18333 blocked, but newer streams would gladly fill the queue completely.
18334 We add code to detect this situation and prevent any stream from
18335 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
18339 - Update to the September 1 2010 Maxmind GeoLite Country database.
18340 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
18341 not. This would lead to a cookie that is still not group readable.
18342 Closes bug 1843. Suggested by katmagic.
18343 - When logging a rate-limited warning, we now mention how many messages
18344 got suppressed since the last warning.
18345 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
18346 do individual connection-level rate limiting of clients. The torrc
18347 config options with the same names trump the consensus params, if
18348 both are present. Replaces the old "bwconnrate" and "bwconnburst"
18349 consensus params which were broken from 0.2.2.7-alpha through
18350 0.2.2.14-alpha. Closes bug 1947.
18351 - When a router changes IP address or port, authorities now launch
18352 a new reachability test for it. Implements ticket 1899.
18353 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
18354 2 no signature, 4 required" messages about consensus signatures
18355 easier to read, and make sure they get logged at the same severity
18356 as the messages explaining which keys are which. Fixes bug 1290.
18357 - Don't warn when we have a consensus that we can't verify because
18358 of missing certificates, unless those certificates are ones
18359 that we have been trying and failing to download. Fixes bug 1145.
18360 - If you configure your bridge with a known identity fingerprint,
18361 and the bridge authority is unreachable (as it is in at least
18362 one country now), fall back to directly requesting the descriptor
18363 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
18365 - When building with --enable-gcc-warnings on OpenBSD, disable
18366 warnings in system headers. This makes --enable-gcc-warnings
18367 pass on OpenBSD 4.8.
18369 o Minor bugfixes (on 0.2.1.x and earlier):
18370 - Authorities will now attempt to download consensuses if their
18371 own efforts to make a live consensus have failed. This change
18372 means authorities that restart will fetch a valid consensus, and
18373 it means authorities that didn't agree with the current consensus
18374 will still fetch and serve it if it has enough signatures. Bugfix
18375 on 0.2.0.9-alpha; fixes bug 1300.
18376 - Ensure DNS requests launched by "RESOLVE" commands from the
18377 controller respect the __LeaveStreamsUnattached setconf options. The
18378 same goes for requests launched via DNSPort or transparent
18379 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
18380 - Allow handshaking OR connections to take a full KeepalivePeriod
18381 seconds to handshake. Previously, we would close them after
18382 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
18383 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
18385 - Rate-limit "Failed to hand off onionskin" warnings.
18386 - Never relay a cell for a circuit we have already destroyed.
18387 Between marking a circuit as closeable and finally closing it,
18388 it may have been possible for a few queued cells to get relayed,
18389 even though they would have been immediately dropped by the next
18390 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
18391 - Never queue a cell for a circuit that's already been marked
18393 - Never vote for a server as "Running" if we have a descriptor for
18394 it claiming to be hibernating, and that descriptor was published
18395 more recently than our last contact with the server. Bugfix on
18396 0.2.0.3-alpha; fixes bug 911.
18397 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
18400 o Minor bugfixes (on 0.2.2.x):
18401 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
18402 down if a directory fetch fails and you've configured either
18403 bridges or EntryNodes. The intent was to mark the relay as down
18404 _unless_ you're using bridges or EntryNodes, since if you are
18405 then you could quickly run out of entry points.
18406 - Fix the Windows directory-listing code. A bug introduced in
18407 0.2.2.14-alpha could make Windows directory servers forget to load
18408 some of their cached v2 networkstatus files.
18409 - Really allow clients to use relays as bridges. Fixes bug 1776;
18410 bugfix on 0.2.2.15-alpha.
18411 - Demote a warn to info that happens when the CellStatistics option
18412 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
18413 Reported by Moritz Bartl.
18414 - On Windows, build correctly either with or without Unicode support.
18415 This is necessary so that Tor can support fringe platforms like
18416 Windows 98 (which has no Unicode), or Windows CE (which has no
18417 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
18420 - Add a unit test for cross-platform directory-listing code.
18423 Changes in version 0.2.2.15-alpha - 2010-08-18
18424 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
18425 fixes a variety of other bugs that were preventing performance
18426 experiments from moving forward, fixes several bothersome memory leaks,
18427 and generally closes a lot of smaller bugs that have been filling up
18431 - Stop assigning the HSDir flag to relays that disable their
18432 DirPort (and thus will refuse to answer directory requests). This
18433 fix should dramatically improve the reachability of hidden services:
18434 hidden services and hidden service clients pick six HSDir relays
18435 to store and retrieve the hidden service descriptor, and currently
18436 about half of the HSDir relays will refuse to work. Bugfix on
18437 0.2.0.10-alpha; fixes part of bug 1693.
18438 - The PerConnBWRate and Burst config options, along with the
18439 bwconnrate and bwconnburst consensus params, initialized each conn's
18440 token bucket values only when the connection is established. Now we
18441 update them if the config options change, and update them every time
18442 we get a new consensus. Otherwise we can encounter an ugly edge
18443 case where we initialize an OR conn to client-level bandwidth,
18444 but then later the relay joins the consensus and we leave it
18445 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
18446 - Fix a regression that caused Tor to rebind its ports if it receives
18447 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
18450 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
18451 should give us approximately 40-50% more Guard-flagged nodes,
18452 improving the anonymity the Tor network can provide and also
18453 decreasing the dropoff in throughput that relays experience when
18454 they first get the Guard flag.
18455 - Allow enabling or disabling the *Statistics config options while
18459 - Update to the August 1 2010 Maxmind GeoLite Country database.
18460 - Have the controller interface give a more useful message than
18461 "Internal Error" in response to failed GETINFO requests.
18462 - Warn when the same option is provided more than once in a torrc
18463 file, on the command line, or in a single SETCONF statement, and
18464 the option is one that only accepts a single line. Closes bug 1384.
18465 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
18466 Patch from mingw-san.
18467 - Add support for the country code "{??}" in torrc options like
18468 ExcludeNodes, to indicate all routers of unknown country. Closes
18470 - Relays report the number of bytes spent on answering directory
18471 requests in extra-info descriptors similar to {read,write}-history.
18472 Implements enhancement 1790.
18474 o Minor bugfixes (on 0.2.1.x and earlier):
18475 - Complain if PublishServerDescriptor is given multiple arguments that
18476 include 0 or 1. This configuration will be rejected in the future.
18477 Bugfix on 0.2.0.1-alpha; closes bug 1107.
18478 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
18479 Bugfix on 0.2.0.13-alpha; closes bug 928.
18480 - Change "Application request when we're believed to be offline."
18481 notice to "Application request when we haven't used client
18482 functionality lately.", to clarify that it's not an error. Bugfix
18483 on 0.0.9.3; fixes bug 1222.
18484 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
18485 would return "551 Internal error" rather than "552 Unrecognized key
18486 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
18487 - Users can't configure a regular relay to be their bridge. It didn't
18488 work because when Tor fetched the bridge descriptor, it found
18489 that it already had it, and didn't realize that the purpose of the
18490 descriptor had changed. Now we replace routers with a purpose other
18491 than bridge with bridge descriptors when fetching them. Bugfix on
18492 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
18493 refetch the descriptor with router purpose 'general', disabling
18495 - Fix a rare bug in rend_fn unit tests: we would fail a test when
18496 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
18497 on 0.2.0.10-alpha; fixes bug 1808.
18498 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
18499 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
18500 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
18501 Servers can start sending this code when enough clients recognize
18502 it. Also update the spec to reflect this new reason. Bugfix on
18503 0.1.0.1-rc; fixes part of bug 1793.
18504 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
18505 when we switch from being a public relay to a bridge. Otherwise
18506 there will still be clients that see the relay in their consensus,
18507 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
18509 - Instead of giving an assertion failure on an internal mismatch
18510 on estimated freelist size, just log a BUG warning and try later.
18511 Mitigates but does not fix bug 1125.
18512 - Fix an assertion failure that could occur in caches or bridge users
18513 when using a very short voting interval on a testing network.
18514 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
18516 o Minor bugfixes (on 0.2.2.x):
18517 - Alter directory authorities to always consider Exit-flagged nodes
18518 as potential Guard nodes in their votes. The actual decision to
18519 use Exits as Guards is done in the consensus bandwidth weights.
18520 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
18521 - When the controller is reporting the purpose of circuits that
18522 didn't finish building before the circuit build timeout, it was
18523 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
18524 - Our libevent version parsing code couldn't handle versions like
18525 1.4.14b-stable and incorrectly warned the user about using an
18526 old and broken version of libevent. Treat 1.4.14b-stable like
18527 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
18529 - Don't use substitution references like $(VAR:MOD) when
18530 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
18531 '$(:x)' to 'x' rather than the empty string. This bites us in
18532 doc/ when configured with --disable-asciidoc. Bugfix on
18533 0.2.2.9-alpha; fixes bug 1773.
18534 - Remove a spurious hidden service server-side log notice about
18535 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
18537 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
18539 - Correctly report written bytes on linked connections. Found while
18540 implementing 1790. Bugfix on 0.2.2.4-alpha.
18541 - Fix three memory leaks: one in circuit_build_times_parse_state(),
18542 one in dirvote_add_signatures_to_pending_consensus(), and one every
18543 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
18544 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
18546 o Code simplifications and refactoring:
18547 - Take a first step towards making or.h smaller by splitting out
18548 function definitions for all source files in src/or/. Leave
18549 structures and defines in or.h for now.
18550 - Remove a bunch of unused function declarations as well as a block of
18551 #if 0'd code from the unit tests. Closes bug 1824.
18552 - New unit tests for exit-port history statistics; refactored exit
18553 statistics code to be more easily tested.
18554 - Remove the old debian/ directory from the main Tor distribution.
18555 The official Tor-for-debian git repository lives at the URL
18556 https://git.torproject.org/debian/tor.git
18559 Changes in version 0.2.2.14-alpha - 2010-07-12
18560 Tor 0.2.2.14-alpha greatly improves client-side handling of
18561 circuit build timeouts, which are used to estimate speed and improve
18562 performance. We also move to a much better GeoIP database, port Tor to
18563 Windows CE, introduce new compile flags that improve code security,
18564 add an eighth v3 directory authority, and address a lot of more
18568 - Tor directory authorities no longer crash when started with a
18569 cached-microdesc-consensus file in their data directory. Bugfix
18570 on 0.2.2.6-alpha; fixes bug 1532.
18571 - Treat an unset $HOME like an empty $HOME rather than triggering an
18572 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
18573 - Ignore negative and large circuit build timeout values that can
18574 happen during a suspend or hibernate. These values caused various
18575 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
18576 - Alter calculation of Pareto distribution parameter 'Xm' for
18577 Circuit Build Timeout learning to use the weighted average of the
18578 top N=3 modes (because we have three entry guards). Considering
18579 multiple modes should improve the timeout calculation in some cases,
18580 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
18582 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
18583 right censored distribution model. This approach improves over the
18584 synthetic timeout generation approach that was producing insanely
18585 high timeout values. Now we calculate build timeouts using truncated
18586 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
18587 - Do not close circuits that are under construction when they reach
18588 the circuit build timeout. Instead, leave them building (but do not
18589 use them) for up until the time corresponding to the 95th percentile
18590 on the Pareto CDF or 60 seconds, whichever is greater. This is done
18591 to provide better data for the new Pareto model. This percentile
18592 can be controlled by the consensus.
18595 - Move to the June 2010 Maxmind GeoLite country db (rather than the
18596 June 2009 ip-to-country GeoIP db) for our statistics that count
18597 how many users relays are seeing from each country. Now we have
18598 more accurate data for many African countries.
18599 - Port Tor to build and run correctly on Windows CE systems, using
18600 the wcecompat library. Contributed by Valerio Lupi.
18601 - New "--enable-gcc-hardening" ./configure flag (off by default)
18602 to turn on gcc compile time hardening options. It ensures
18603 that signed ints have defined behavior (-fwrapv), enables
18604 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
18605 with canaries (-fstack-protector-all), turns on ASLR protection if
18606 supported by the kernel (-fPIE, -pie), and adds additional security
18607 related warnings. Verified to work on Mac OS X and Debian Lenny.
18608 - New "--enable-linker-hardening" ./configure flag (off by default)
18609 to turn on ELF specific hardening features (relro, now). This does
18610 not work with Mac OS X or any other non-ELF binary format.
18612 o New directory authorities:
18613 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
18617 - New config option "WarnUnsafeSocks 0" disables the warning that
18618 occurs whenever Tor receives a socks handshake using a version of
18619 the socks protocol that can only provide an IP address (rather
18620 than a hostname). Setups that do DNS locally over Tor are fine,
18621 and we shouldn't spam the logs in that case.
18622 - Convert the HACKING file to asciidoc, and add a few new sections
18623 to it, explaining how we use Git, how we make changelogs, and
18624 what should go in a patch.
18625 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
18626 event, to give information on the current rate of circuit timeouts
18627 over our stored history.
18628 - Add ability to disable circuit build time learning via consensus
18629 parameter and via a LearnCircuitBuildTimeout config option. Also
18630 automatically disable circuit build time calculation if we are
18631 either a AuthoritativeDirectory, or if we fail to write our state
18632 file. Fixes bug 1296.
18633 - More gracefully handle corrupt state files, removing asserts
18634 in favor of saving a backup and resetting state.
18635 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
18639 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
18641 - When a2x fails, mention that the user could disable manpages instead
18642 of trying to fix their asciidoc installation.
18643 - Where available, use Libevent 2.0's periodic timers so that our
18644 once-per-second cleanup code gets called even more closely to
18645 once per second than it would otherwise. Fixes bug 943.
18646 - If you run a bridge that listens on multiple IP addresses, and
18647 some user configures a bridge address that uses a different IP
18648 address than your bridge writes in its router descriptor, and the
18649 user doesn't specify an identity key, their Tor would discard the
18650 descriptor because "it isn't one of our configured bridges", and
18651 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
18652 Bugfix on 0.2.0.3-alpha.
18653 - If OpenSSL fails to make a duplicate of a private or public key, log
18654 an error message and try to exit cleanly. May help with debugging
18655 if bug 1209 ever remanifests.
18656 - Save a couple bytes in memory allocation every time we escape
18657 certain characters in a string. Patch from Florian Zumbiehl.
18658 - Make it explicit that we don't cannibalize one-hop circuits. This
18659 happens in the wild, but doesn't turn out to be a problem because
18660 we fortunately don't use those circuits. Many thanks to outofwords
18661 for the initial analysis and to swissknife who confirmed that
18662 two-hop circuits are actually created.
18663 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
18664 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
18665 - Eliminate a case where a circuit build time warning was displayed
18666 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
18669 Changes in version 0.2.1.26 - 2010-05-02
18670 Tor 0.2.1.26 addresses the recent connection and memory overload
18671 problems we've been seeing on relays, especially relays with their
18672 DirPort open. If your relay has been crashing, or you turned it off
18673 because it used too many resources, give this release a try.
18675 This release also fixes yet another instance of broken OpenSSL libraries
18676 that was causing some relays to drop out of the consensus.
18679 - Teach relays to defend themselves from connection overload. Relays
18680 now close idle circuits early if it looks like they were intended
18681 for directory fetches. Relays are also more aggressive about closing
18682 TLS connections that have no circuits on them. Such circuits are
18683 unlikely to be re-used, and tens of thousands of them were piling
18684 up at the fast relays, causing the relays to run out of sockets
18685 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
18686 their directory fetches over TLS).
18687 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
18688 that claim to be earlier than 0.9.8m, but which have in reality
18689 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
18690 behavior. Possible fix for some cases of bug 1346.
18691 - Directory mirrors were fetching relay descriptors only from v2
18692 directory authorities, rather than v3 authorities like they should.
18693 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
18694 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
18697 - Finally get rid of the deprecated and now harmful notion of "clique
18698 mode", where directory authorities maintain TLS connections to
18702 - In the util/threads test, no longer free the test_mutex before all
18703 worker threads have finished. Bugfix on 0.2.1.6-alpha.
18704 - The master thread could starve the worker threads quite badly on
18705 certain systems, causing them to run only partially in the allowed
18706 window. This resulted in test failures. Now the master thread sleeps
18707 occasionally for a few microseconds while the two worker-threads
18708 compete for the mutex. Bugfix on 0.2.0.1-alpha.
18711 Changes in version 0.2.2.13-alpha - 2010-04-24
18712 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
18713 problems we've been seeing on relays, especially relays with their
18714 DirPort open. If your relay has been crashing, or you turned it off
18715 because it used too many resources, give this release a try.
18718 - Teach relays to defend themselves from connection overload. Relays
18719 now close idle circuits early if it looks like they were intended
18720 for directory fetches. Relays are also more aggressive about closing
18721 TLS connections that have no circuits on them. Such circuits are
18722 unlikely to be re-used, and tens of thousands of them were piling
18723 up at the fast relays, causing the relays to run out of sockets
18724 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
18725 their directory fetches over TLS).
18728 - Finally get rid of the deprecated and now harmful notion of "clique
18729 mode", where directory authorities maintain TLS connections to
18731 - Directory authorities now do an immediate reachability check as soon
18732 as they hear about a new relay. This change should slightly reduce
18733 the time between setting up a relay and getting listed as running
18734 in the consensus. It should also improve the time between setting
18735 up a bridge and seeing use by bridge users.
18736 - Directory authorities no longer launch a TLS connection to every
18737 relay as they startup. Now that we have 2k+ descriptors cached,
18738 the resulting network hiccup is becoming a burden. Besides,
18739 authorities already avoid voting about Running for the first half
18740 hour of their uptime.
18743 Changes in version 0.2.2.12-alpha - 2010-04-20
18744 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
18745 handle and vote on descriptors. It was causing relays to drop out of
18749 - Many relays have been falling out of the consensus lately because
18750 not enough authorities know about their descriptor for them to get
18751 a majority of votes. When we deprecated the v2 directory protocol,
18752 we got rid of the only way that v3 authorities can hear from each
18753 other about other descriptors. Now authorities examine every v3
18754 vote for new descriptors, and fetch them from that authority. Bugfix
18756 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
18757 and a warning in or.h related to bandwidth_weight_rule_t that
18758 prevented clean compile on OS X. Fixes bug 1363; bugfix on
18760 - Fix a segfault on relays when DirReqStatistics is enabled
18761 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
18765 - Demote a confusing TLS warning that relay operators might get when
18766 someone tries to talk to their OrPort. It is neither the operator's
18767 fault nor can they do anything about it. Fixes bug 1364; bugfix
18771 Changes in version 0.2.2.11-alpha - 2010-04-15
18772 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
18773 libraries that was causing some relays to drop out of the consensus.
18776 - Directory mirrors were fetching relay descriptors only from v2
18777 directory authorities, rather than v3 authorities like they should.
18778 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
18779 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
18780 - Fix a parsing error that made every possible value of
18781 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
18782 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
18783 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
18784 about the option without breaking older ones.
18785 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
18786 that claim to be earlier than 0.9.8m, but which have in reality
18787 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
18788 behavior. Possible fix for some cases of bug 1346.
18791 - Experiment with a more aggressive approach to preventing clients
18792 from making one-hop exit streams. Exit relays who want to try it
18793 out can set "RefuseUnknownExits 1" in their torrc, and then look
18794 for "Attempt by %s to open a stream" log messages. Let us know
18796 - Add support for statically linking zlib by specifying
18797 --enable-static-zlib, to go with our support for statically linking
18798 openssl and libevent. Resolves bug 1358.
18801 - Fix a segfault that happens whenever a Tor client that is using
18802 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
18804 - When we cleaned up the contrib/tor-exit-notice.html file, we left
18805 out the first line. Fixes bug 1295.
18806 - When building the manpage from a tarball, we required asciidoc, but
18807 the asciidoc -> roff/html conversion was already done for the
18808 tarball. Make 'make' complain only when we need asciidoc (either
18809 because we're compiling directly from git, or because we altered
18810 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
18811 - When none of the directory authorities vote on any params, Tor
18812 segfaulted when trying to make the consensus from the votes. We
18813 didn't trigger the bug in practice, because authorities do include
18814 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
18817 - In the util/threads test, no longer free the test_mutex before all
18818 worker threads have finished. Bugfix on 0.2.1.6-alpha.
18819 - The master thread could starve the worker threads quite badly on
18820 certain systems, causing them to run only partially in the allowed
18821 window. This resulted in test failures. Now the master thread sleeps
18822 occasionally for a few microseconds while the two worker-threads
18823 compete for the mutex. Bugfix on 0.2.0.1-alpha.
18826 Changes in version 0.2.2.10-alpha - 2010-03-07
18827 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
18828 could prevent relays from guessing their IP address correctly. It also
18829 starts the groundwork for another client-side performance boost, since
18830 currently we're not making efficient use of relays that have both the
18831 Guard flag and the Exit flag.
18834 - Fix a regression from our patch for bug 1244 that caused relays
18835 to guess their IP address incorrectly if they didn't set Address
18836 in their torrc and/or their address fails to resolve. Bugfix on
18837 0.2.2.9-alpha; fixes bug 1269.
18839 o Major features (performance):
18840 - Directory authorities now compute consensus weightings that instruct
18841 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
18842 and no flag. Clients that use these weightings will distribute
18843 network load more evenly across these different relay types. The
18844 weightings are in the consensus so we can change them globally in
18845 the future. Extra thanks to "outofwords" for finding some nasty
18846 security bugs in the first implementation of this feature.
18848 o Minor features (performance):
18849 - Always perform router selections using weighted relay bandwidth,
18850 even if we don't need a high capacity circuit at the time. Non-fast
18851 circuits now only differ from fast ones in that they can use relays
18852 not marked with the Fast flag. This "feature" could turn out to
18853 be a horrible bug; we should investigate more before it goes into
18857 - Allow disabling building of the manpages. Skipping the manpage
18858 speeds up the build considerably.
18860 o Minor bugfixes (on 0.2.2.x):
18861 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
18862 Bugfix on 0.2.2.9-alpha.
18863 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
18864 config option. Bugfix on 0.2.2.7-alpha.
18865 - Ship the asciidoc-helper file in the tarball, so that people can
18866 build from source if they want to, and touching the .1.txt files
18867 doesn't break the build. Bugfix on 0.2.2.9-alpha.
18869 o Minor bugfixes (on 0.2.1.x or earlier):
18870 - Fix a dereference-then-NULL-check sequence when publishing
18871 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
18873 - Fix another dereference-then-NULL-check sequence. Bugfix on
18874 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
18875 - Make sure we treat potentially not NUL-terminated strings correctly.
18876 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
18878 o Code simplifications and refactoring:
18879 - Fix some urls in the exit notice file and make it XHTML1.1 strict
18880 compliant. Based on a patch from Christian Kujau.
18881 - Don't use sed in asciidoc-helper anymore.
18882 - Make the build process fail if asciidoc cannot be found and
18883 building with asciidoc isn't disabled.
18886 Changes in version 0.2.2.9-alpha - 2010-02-22
18887 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
18888 location of a directory authority, and cleans up a bunch of small bugs.
18890 o Directory authority changes:
18891 - Change IP address for dannenberg (v3 directory authority), and
18892 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
18893 service directory authority) from the list.
18896 - Make Tor work again on the latest OS X: when deciding whether to
18897 use strange flags to turn TLS renegotiation on, detect the OpenSSL
18898 version at run-time, not compile time. We need to do this because
18899 Apple doesn't update its dev-tools headers when it updates its
18900 libraries in a security patch.
18901 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
18902 that could happen on 32-bit platforms with 64-bit time_t. Also fix
18903 a memory leak when requesting a hidden service descriptor we've
18904 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
18906 - Authorities could be tricked into giving out the Exit flag to relays
18907 that didn't allow exiting to any ports. This bug could screw
18908 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
18909 1238. Bug discovered by Martin Kowalczyk.
18910 - When freeing a session key, zero it out completely. We only zeroed
18911 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
18912 patched by ekir. Fixes bug 1254.
18915 - Fix static compilation by listing the openssl libraries in the right
18916 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
18917 - Resume handling .exit hostnames in a special way: originally we
18918 stripped the .exit part and used the requested exit relay. In
18919 0.2.2.1-alpha we stopped treating them in any special way, meaning
18920 if you use a .exit address then Tor will pass it on to the exit
18921 relay. Now we reject the .exit stream outright, since that behavior
18922 might be more expected by the user. Found and diagnosed by Scott
18923 Bennett and Downie on or-talk.
18924 - Don't spam the controller with events when we have no file
18925 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
18926 for log messages was already solved from bug 748.)
18927 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
18929 - Make the DNSPort option work with libevent 2.x. Don't alter the
18930 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
18931 - Emit a GUARD DROPPED controller event for a case we missed.
18932 - Make more fields in the controller protocol case-insensitive, since
18933 control-spec.txt said they were.
18934 - Refactor resolve_my_address() to not use gethostbyname() anymore.
18935 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
18936 - Fix a spec conformance issue: the network-status-version token
18937 must be the first token in a v3 consensus or vote. Discovered by
18938 parakeep. Bugfix on 0.2.0.3-alpha.
18940 o Code simplifications and refactoring:
18941 - Generate our manpage and HTML documentation using Asciidoc. This
18942 change should make it easier to maintain the documentation, and
18943 produce nicer HTML.
18944 - Remove the --enable-iphone option. According to reports from Marco
18945 Bonetti, Tor builds fine without any special tweaking on recent
18946 iPhone SDK versions.
18947 - Removed some unnecessary files from the source distribution. The
18948 AUTHORS file has now been merged into the people page on the
18949 website. The roadmaps and design doc can now be found in the
18950 projects directory in svn.
18951 - Enabled various circuit build timeout constants to be controlled
18952 by consensus parameters. Also set better defaults for these
18953 parameters based on experimentation on broadband and simulated
18954 high latency links.
18957 - The 'EXTENDCIRCUIT' control port command can now be used with
18958 a circ id of 0 and no path. This feature will cause Tor to build
18959 a new 'fast' general purpose circuit using its own path selection
18961 - Added a BUILDTIMEOUT_SET controller event to describe changes
18962 to the circuit build timeout.
18963 - Future-proof the controller protocol a bit by ignoring keyword
18964 arguments we do not recognize.
18965 - Expand homedirs passed to tor-checkkey. This should silence a
18966 coverity complaint about passing a user-supplied string into
18967 open() without checking it.
18970 Changes in version 0.2.1.25 - 2010-03-16
18971 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
18972 prevent relays from guessing their IP address correctly. It also fixes
18973 several minor potential security bugs.
18976 - Fix a regression from our patch for bug 1244 that caused relays
18977 to guess their IP address incorrectly if they didn't set Address
18978 in their torrc and/or their address fails to resolve. Bugfix on
18979 0.2.1.23; fixes bug 1269.
18980 - When freeing a session key, zero it out completely. We only zeroed
18981 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
18982 patched by ekir. Fixes bug 1254.
18985 - Fix a dereference-then-NULL-check sequence when publishing
18986 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
18988 - Fix another dereference-then-NULL-check sequence. Bugfix on
18989 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
18990 - Make sure we treat potentially not NUL-terminated strings correctly.
18991 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
18995 Changes in version 0.2.1.24 - 2010-02-21
18996 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
19000 - Work correctly out-of-the-box with even more vendor-patched versions
19001 of OpenSSL. In particular, make it so Debian and OS X don't need
19002 customized patches to run/build.
19005 Changes in version 0.2.1.23 - 2010-02-13
19006 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
19007 again on the latest OS X, and updates the location of a directory
19010 o Major bugfixes (performance):
19011 - We were selecting our guards uniformly at random, and then weighting
19012 which of our guards we'd use uniformly at random. This imbalance
19013 meant that Tor clients were severely limited on throughput (and
19014 probably latency too) by the first hop in their circuit. Now we
19015 select guards weighted by currently advertised bandwidth. We also
19016 automatically discard guards picked using the old algorithm. Fixes
19017 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19020 - Make Tor work again on the latest OS X: when deciding whether to
19021 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19022 version at run-time, not compile time. We need to do this because
19023 Apple doesn't update its dev-tools headers when it updates its
19024 libraries in a security patch.
19025 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19026 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19027 a memory leak when requesting a hidden service descriptor we've
19028 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19031 o Directory authority changes:
19032 - Change IP address for dannenberg (v3 directory authority), and
19033 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19034 service directory authority) from the list.
19037 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19038 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19041 - Avoid a mad rush at the beginning of each month when each client
19042 rotates half of its guards. Instead we spread the rotation out
19043 throughout the month, but we still avoid leaving a precise timestamp
19044 in the state file about when we first picked the guard. Improves
19045 over the behavior introduced in 0.1.2.17.
19048 Changes in version 0.2.2.8-alpha - 2010-01-26
19049 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
19050 causing bridge relays to disappear. If you're running a bridge,
19054 - Fix a memory corruption bug on bridges that occurred during the
19055 inclusion of stats data in extra-info descriptors. Also fix the
19056 interface for geoip_get_bridge_stats* to prevent similar bugs in
19057 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
19058 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
19061 - Ignore OutboundBindAddress when connecting to localhost.
19062 Connections to localhost need to come _from_ localhost, or else
19063 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
19067 Changes in version 0.2.2.7-alpha - 2010-01-19
19068 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
19069 as laying the groundwork for further relay-side performance fixes. It
19070 also starts cleaning up client behavior with respect to the EntryNodes,
19071 ExitNodes, and StrictNodes config options.
19073 This release also rotates two directory authority keys, due to a
19074 security breach of some of the Torproject servers.
19076 o Directory authority changes:
19077 - Rotate keys (both v3 identity and relay identity) for moria1
19080 o Major features (performance):
19081 - We were selecting our guards uniformly at random, and then weighting
19082 which of our guards we'd use uniformly at random. This imbalance
19083 meant that Tor clients were severely limited on throughput (and
19084 probably latency too) by the first hop in their circuit. Now we
19085 select guards weighted by currently advertised bandwidth. We also
19086 automatically discard guards picked using the old algorithm. Fixes
19087 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19088 - When choosing which cells to relay first, relays can now favor
19089 circuits that have been quiet recently, to provide lower latency
19090 for low-volume circuits. By default, relays enable or disable this
19091 feature based on a setting in the consensus. You can override
19092 this default by using the new "CircuitPriorityHalflife" config
19093 option. Design and code by Ian Goldberg, Can Tang, and Chris
19095 - Add separate per-conn write limiting to go with the per-conn read
19096 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
19097 but never per-conn write limits.
19098 - New consensus params "bwconnrate" and "bwconnburst" to let us
19099 rate-limit client connections as they enter the network. It's
19100 controlled in the consensus so we can turn it on and off for
19101 experiments. It's starting out off. Based on proposal 163.
19103 o Major features (relay selection options):
19104 - Switch to a StrictNodes config option, rather than the previous
19105 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
19106 "StrictExcludeNodes" option.
19107 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
19108 change during a config reload, mark and discard all our origin
19109 circuits. This fix should address edge cases where we change the
19110 config options and but then choose a circuit that we created before
19112 - If EntryNodes or ExitNodes are set, be more willing to use an
19113 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
19115 - Make EntryNodes config option much more aggressive even when
19116 StrictNodes is not set. Before it would prepend your requested
19117 entrynodes to your list of guard nodes, but feel free to use others
19118 after that. Now it chooses only from your EntryNodes if any of
19119 those are available, and only falls back to others if a) they're
19120 all down and b) StrictNodes is not set.
19121 - Now we refresh your entry guards from EntryNodes at each consensus
19122 fetch -- rather than just at startup and then they slowly rot as
19123 the network changes.
19126 - Stop bridge directory authorities from answering dbg-stability.txt
19127 directory queries, which would let people fetch a list of all
19128 bridge identities they track. Bugfix on 0.2.1.6-alpha.
19131 - Log a notice when we get a new control connection. Now it's easier
19132 for security-conscious users to recognize when a local application
19133 is knocking on their controller door. Suggested by bug 1196.
19134 - New config option "CircuitStreamTimeout" to override our internal
19135 timeout schedule for how many seconds until we detach a stream from
19136 a circuit and try a new circuit. If your network is particularly
19137 slow, you might want to set this to a number like 60.
19138 - New controller command "getinfo config-text". It returns the
19139 contents that Tor would write if you send it a SAVECONF command,
19140 so the controller can write the file to disk itself.
19141 - New options for SafeLogging to allow scrubbing only log messages
19142 generated while acting as a relay.
19143 - Ship the bridges spec file in the tarball too.
19144 - Avoid a mad rush at the beginning of each month when each client
19145 rotates half of its guards. Instead we spread the rotation out
19146 throughout the month, but we still avoid leaving a precise timestamp
19147 in the state file about when we first picked the guard. Improves
19148 over the behavior introduced in 0.1.2.17.
19150 o Minor bugfixes (compiling):
19151 - Fix compilation on OS X 10.3, which has a stub mlockall() but
19152 hides it. Bugfix on 0.2.2.6-alpha.
19153 - Fix compilation on Solaris by removing support for the
19154 DisableAllSwap config option. Solaris doesn't have an rlimit for
19155 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
19158 o Minor bugfixes (crashes):
19159 - Do not segfault when writing buffer stats when we haven't observed
19160 a single circuit to report about. Found by Fabian Lanze. Bugfix on
19162 - If we're in the pathological case where there's no exit bandwidth
19163 but there is non-exit bandwidth, or no guard bandwidth but there
19164 is non-guard bandwidth, don't crash during path selection. Bugfix
19166 - Fix an impossible-to-actually-trigger buffer overflow in relay
19167 descriptor generation. Bugfix on 0.1.0.15.
19169 o Minor bugfixes (privacy):
19170 - Fix an instance where a Tor directory mirror might accidentally
19171 log the IP address of a misbehaving Tor client. Bugfix on
19173 - Don't list Windows capabilities in relay descriptors. We never made
19174 use of them, and maybe it's a bad idea to publish them. Bugfix
19177 o Minor bugfixes (other):
19178 - Resolve an edge case in path weighting that could make us misweight
19179 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
19180 - Fix statistics on client numbers by country as seen by bridges that
19181 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
19182 intervals instead of variable 12-to-48-hour intervals.
19183 - After we free an internal connection structure, overwrite it
19184 with a different memory value than we use for overwriting a freed
19185 internal circuit structure. Should help with debugging. Suggested
19187 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
19190 o Removed features:
19191 - Remove the HSAuthorityRecordStats option that version 0 hidden
19192 service authorities could have used to track statistics of overall
19193 hidden service usage.
19196 Changes in version 0.2.1.22 - 2010-01-19
19197 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
19198 authorities -- it would tell you its whole history of bridge descriptors
19199 if you make the right directory request. This stable update also
19200 rotates two of the seven v3 directory authority keys and locations.
19202 o Directory authority changes:
19203 - Rotate keys (both v3 identity and relay identity) for moria1
19207 - Stop bridge directory authorities from answering dbg-stability.txt
19208 directory queries, which would let people fetch a list of all
19209 bridge identities they track. Bugfix on 0.2.1.6-alpha.
19212 Changes in version 0.2.1.21 - 2009-12-21
19213 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
19214 library. If you use Tor on Linux / Unix and you're getting SSL
19215 renegotiation errors, upgrading should help. We also recommend an
19216 upgrade if you're an exit relay.
19219 - Work around a security feature in OpenSSL 0.9.8l that prevents our
19220 handshake from working unless we explicitly tell OpenSSL that we
19221 are using SSL renegotiation safely. We are, of course, but OpenSSL
19222 0.9.8l won't work unless we say we are.
19223 - Avoid crashing if the client is trying to upload many bytes and the
19224 circuit gets torn down at the same time, or if the flip side
19225 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
19228 - Do not refuse to learn about authority certs and v2 networkstatus
19229 documents that are older than the latest consensus. This bug might
19230 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
19231 Spotted and fixed by xmux.
19232 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
19233 trigger platform-specific option misparsing case found by Coverity
19235 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
19236 trigger assert. Fixes bug 1173.
19239 Changes in version 0.2.2.6-alpha - 2009-11-19
19240 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
19241 support for the new lower-footprint "microdescriptor" directory design,
19242 future-proofing our consensus format against new hash functions or
19243 other changes, and an Android port. It also makes Tor compatible with
19244 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
19247 - Directory authorities can now create, vote on, and serve multiple
19248 parallel formats of directory data as part of their voting process.
19249 Partially implements Proposal 162: "Publish the consensus in
19251 - Directory authorities can now agree on and publish small summaries
19252 of router information that clients can use in place of regular
19253 server descriptors. This transition will eventually allow clients
19254 to use far less bandwidth for downloading information about the
19255 network. Begins the implementation of Proposal 158: "Clients
19256 download consensus + microdescriptors".
19257 - The directory voting system is now extensible to use multiple hash
19258 algorithms for signatures and resource selection. Newer formats
19259 are signed with SHA256, with a possibility for moving to a better
19260 hash algorithm in the future.
19261 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
19262 current and future memory pages via mlockall(). On supported
19263 platforms (modern Linux and probably BSD but not Windows or OS X),
19264 this should effectively disable any and all attempts to page out
19265 memory. This option requires that you start your Tor as root --
19266 if you use DisableAllSwap, please consider using the User option
19267 to properly reduce the privileges of your Tor.
19268 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
19269 to help Tor build correctly for Android phones.
19272 - Work around a security feature in OpenSSL 0.9.8l that prevents our
19273 handshake from working unless we explicitly tell OpenSSL that we
19274 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
19275 won't work unless we say we are.
19278 - Fix a crash bug when trying to initialize the evdns module in
19279 Libevent 2. Bugfix on 0.2.1.16-rc.
19280 - Stop logging at severity 'warn' when some other Tor client tries
19281 to establish a circuit with us using weak DH keys. It's a protocol
19282 violation, but that doesn't mean ordinary users need to hear about
19283 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
19284 - Do not refuse to learn about authority certs and v2 networkstatus
19285 documents that are older than the latest consensus. This bug might
19286 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
19287 Spotted and fixed by xmux.
19288 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
19289 - If all authorities restart at once right before a consensus vote,
19290 nobody will vote about "Running", and clients will get a consensus
19291 with no usable relays. Instead, authorities refuse to build a
19292 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
19293 - If your relay can't keep up with the number of incoming create
19294 cells, it would log one warning per failure into your logs. Limit
19295 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
19296 - Bridges now use "reject *:*" as their default exit policy. Bugfix
19297 on 0.2.0.3-alpha; fixes bug 1113.
19298 - Fix a memory leak on directory authorities during voting that was
19299 introduced in 0.2.2.1-alpha. Found via valgrind.
19302 Changes in version 0.2.1.20 - 2009-10-15
19303 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
19304 services at once, prepares for more performance improvements, and
19305 fixes a bunch of smaller bugs.
19307 The Windows and OS X bundles also include a more recent Vidalia,
19308 and switch from Privoxy to Polipo.
19310 The OS X installers are now drag and drop. It's best to un-install
19311 Tor/Vidalia and then install this new bundle, rather than upgrade. If
19312 you want to upgrade, you'll need to update the paths for Tor and Polipo
19313 in the Vidalia Settings window.
19316 - Send circuit or stream sendme cells when our window has decreased
19317 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
19318 by Karsten when testing the "reduce circuit window" performance
19319 patch. Bugfix on the 54th commit on Tor -- from July 2002,
19320 before the release of Tor 0.0.0. This is the new winner of the
19322 - Fix a remotely triggerable memory leak when a consensus document
19323 contains more than one signature from the same voter. Bugfix on
19325 - Avoid segfault in rare cases when finishing an introduction circuit
19326 as a client and finding out that we don't have an introduction key
19327 for it. Fixes bug 1073. Reported by Aaron Swartz.
19330 - Tor now reads the "circwindow" parameter out of the consensus,
19331 and uses that value for its circuit package window rather than the
19332 default of 1000 cells. Begins the implementation of proposal 168.
19334 o New directory authorities:
19335 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
19337 - Move moria1 and tonga to alternate IP addresses.
19340 - Fix a signed/unsigned compile warning in 0.2.1.19.
19341 - Fix possible segmentation fault on directory authorities. Bugfix on
19343 - Fix an extremely rare infinite recursion bug that could occur if
19344 we tried to log a message after shutting down the log subsystem.
19345 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
19346 - Fix an obscure bug where hidden services on 64-bit big-endian
19347 systems might mis-read the timestamp in v3 introduce cells, and
19348 refuse to connect back to the client. Discovered by "rotor".
19349 Bugfix on 0.2.1.6-alpha.
19350 - We were triggering a CLOCK_SKEW controller status event whenever
19351 we connect via the v2 connection protocol to any relay that has
19352 a wrong clock. Instead, we should only inform the controller when
19353 it's a trusted authority that claims our clock is wrong. Bugfix
19354 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
19355 - We were telling the controller about CHECKING_REACHABILITY and
19356 REACHABILITY_FAILED status events whenever we launch a testing
19357 circuit or notice that one has failed. Instead, only tell the
19358 controller when we want to inform the user of overall success or
19359 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
19361 - Don't warn when we're using a circuit that ends with a node
19362 excluded in ExcludeExitNodes, but the circuit is not used to access
19363 the outside world. This should help fix bug 1090. Bugfix on
19365 - Work around a small memory leak in some versions of OpenSSL that
19366 stopped the memory used by the hostname TLS extension from being
19370 - Add a "getinfo status/accepted-server-descriptor" controller
19371 command, which is the recommended way for controllers to learn
19372 whether our server descriptor has been successfully received by at
19373 least on directory authority. Un-recommend good-server-descriptor
19374 getinfo and status events until we have a better design for them.
19377 Changes in version 0.2.2.5-alpha - 2009-10-11
19378 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
19381 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
19383 o Directory authorities:
19384 - Temporarily (just for this release) move dizum to an alternate
19388 Changes in version 0.2.2.4-alpha - 2009-10-10
19389 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
19390 introduces a new unit test framework, shifts directry authority
19391 addresses around to reduce the impact from recent blocking events,
19392 and fixes a few smaller bugs.
19395 - Fix several more asserts in the circuit_build_times code, for
19396 example one that causes Tor to fail to start once we have
19397 accumulated 5000 build times in the state file. Bugfixes on
19398 0.2.2.2-alpha; fixes bug 1108.
19400 o New directory authorities:
19401 - Move moria1 and Tonga to alternate IP addresses.
19404 - Log SSL state transitions at debug level during handshake, and
19405 include SSL states in error messages. This may help debug future
19406 SSL handshake issues.
19407 - Add a new "Handshake" log domain for activities that happen
19408 during the TLS handshake.
19409 - Revert to the "June 3 2009" ip-to-country file. The September one
19410 seems to have removed most US IP addresses.
19411 - Directory authorities now reject Tor relays with versions less than
19412 0.1.2.14. This step cuts out four relays from the current network,
19413 none of which are very big.
19416 - Fix a couple of smaller issues with gathering statistics. Bugfixes
19418 - Fix two memory leaks in the error case of
19419 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
19420 - Don't count one-hop circuits when we're estimating how long it
19421 takes circuits to build on average. Otherwise we'll set our circuit
19422 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
19423 - Directory authorities no longer change their opinion of, or vote on,
19424 whether a router is Running, unless they have themselves been
19425 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
19428 o Code simplifications and refactoring:
19429 - Revise our unit tests to use the "tinytest" framework, so we
19430 can run tests in their own processes, have smarter setup/teardown
19431 code, and so on. The unit test code has moved to its own
19432 subdirectory, and has been split into multiple modules.
19435 Changes in version 0.2.2.3-alpha - 2009-09-23
19436 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
19439 - Fix an overzealous assert in our new circuit build timeout code.
19440 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
19443 - If the networkstatus consensus tells us that we should use a
19444 negative circuit package window, ignore it. Otherwise we'll
19445 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
19448 Changes in version 0.2.2.2-alpha - 2009-09-21
19449 Tor 0.2.2.2-alpha introduces our latest performance improvement for
19450 clients: Tor tracks the average time it takes to build a circuit, and
19451 avoids using circuits that take too long to build. For fast connections,
19452 this feature can cut your expected latency in half. For slow or flaky
19453 connections, it could ruin your Tor experience. Let us know if it does!
19456 - Tor now tracks how long it takes to build client-side circuits
19457 over time, and adapts its timeout to local network performance.
19458 Since a circuit that takes a long time to build will also provide
19459 bad performance, we get significant latency improvements by
19460 discarding the slowest 20% of circuits. Specifically, Tor creates
19461 circuits more aggressively than usual until it has enough data
19462 points for a good timeout estimate. Implements proposal 151.
19463 We are especially looking for reports (good and bad) from users with
19464 both EDGE and broadband connections that can move from broadband
19465 to EDGE and find out if the build-time data in the .tor/state gets
19466 reset without loss of Tor usability. You should also see a notice
19467 log message telling you that Tor has reset its timeout.
19468 - Directory authorities can now vote on arbitrary integer values as
19469 part of the consensus process. This is designed to help set
19470 network-wide parameters. Implements proposal 167.
19471 - Tor now reads the "circwindow" parameter out of the consensus,
19472 and uses that value for its circuit package window rather than the
19473 default of 1000 cells. Begins the implementation of proposal 168.
19476 - Fix a remotely triggerable memory leak when a consensus document
19477 contains more than one signature from the same voter. Bugfix on
19481 - Fix an extremely rare infinite recursion bug that could occur if
19482 we tried to log a message after shutting down the log subsystem.
19483 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
19484 - Fix parsing for memory or time units given without a space between
19485 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
19486 - A networkstatus vote must contain exactly one signature. Spec
19487 conformance issue. Bugfix on 0.2.0.3-alpha.
19488 - Fix an obscure bug where hidden services on 64-bit big-endian
19489 systems might mis-read the timestamp in v3 introduce cells, and
19490 refuse to connect back to the client. Discovered by "rotor".
19491 Bugfix on 0.2.1.6-alpha.
19492 - We were triggering a CLOCK_SKEW controller status event whenever
19493 we connect via the v2 connection protocol to any relay that has
19494 a wrong clock. Instead, we should only inform the controller when
19495 it's a trusted authority that claims our clock is wrong. Bugfix
19496 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
19497 - We were telling the controller about CHECKING_REACHABILITY and
19498 REACHABILITY_FAILED status events whenever we launch a testing
19499 circuit or notice that one has failed. Instead, only tell the
19500 controller when we want to inform the user of overall success or
19501 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
19503 - Don't warn when we're using a circuit that ends with a node
19504 excluded in ExcludeExitNodes, but the circuit is not used to access
19505 the outside world. This should help fix bug 1090, but more problems
19506 remain. Bugfix on 0.2.1.6-alpha.
19507 - Work around a small memory leak in some versions of OpenSSL that
19508 stopped the memory used by the hostname TLS extension from being
19510 - Make our 'torify' script more portable; if we have only one of
19511 'torsocks' or 'tsocks' installed, don't complain to the user;
19512 and explain our warning about tsocks better.
19515 - Add a "getinfo status/accepted-server-descriptor" controller
19516 command, which is the recommended way for controllers to learn
19517 whether our server descriptor has been successfully received by at
19518 least on directory authority. Un-recommend good-server-descriptor
19519 getinfo and status events until we have a better design for them.
19520 - Update to the "September 4 2009" ip-to-country file.
19523 Changes in version 0.2.2.1-alpha - 2009-08-26
19524 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
19525 Tor clients to bootstrap on networks where only port 80 is reachable,
19526 makes it more straightforward to support hardware crypto accelerators,
19527 and starts the groundwork for gathering stats safely at relays.
19530 - Start the process of disabling ".exit" address notation, since it
19531 can be used for a variety of esoteric application-level attacks
19532 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
19535 o New directory authorities:
19536 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
19540 - New AccelName and AccelDir options add support for dynamic OpenSSL
19541 hardware crypto acceleration engines.
19542 - Tor now supports tunneling all of its outgoing connections over
19543 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
19544 configuration options. Code by Christopher Davis.
19547 - Send circuit or stream sendme cells when our window has decreased
19548 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
19549 by Karsten when testing the "reduce circuit window" performance
19550 patch. Bugfix on the 54th commit on Tor -- from July 2002,
19551 before the release of Tor 0.0.0. This is the new winner of the
19554 o New options for gathering stats safely:
19555 - Directory mirrors that set "DirReqStatistics 1" write statistics
19556 about directory requests to disk every 24 hours. As compared to the
19557 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
19558 1) stats are written to disk exactly every 24 hours; 2) estimated
19559 shares of v2 and v3 requests are determined as mean values, not at
19560 the end of a measurement period; 3) unresolved requests are listed
19561 with country code '??'; 4) directories also measure download times.
19562 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
19563 number of exit streams and transferred bytes per port to disk every
19565 - Relays that set "CellStatistics 1" write statistics on how long
19566 cells spend in their circuit queues to disk every 24 hours.
19567 - Entry nodes that set "EntryStatistics 1" write statistics on the
19568 rough number and origins of connecting clients to disk every 24
19570 - Relays that write any of the above statistics to disk and set
19571 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
19572 their extra-info documents.
19575 - New --digests command-line switch to output the digests of the
19576 source files Tor was built with.
19577 - The "torify" script now uses torsocks where available.
19578 - The memarea code now uses a sentinel value at the end of each area
19579 to make sure nothing writes beyond the end of an area. This might
19580 help debug some conceivable causes of bug 930.
19581 - Time and memory units in the configuration file can now be set to
19582 fractional units. For example, "2.5 GB" is now a valid value for
19584 - Certain Tor clients (such as those behind check.torproject.org) may
19585 want to fetch the consensus in an extra early manner. To enable this
19586 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
19587 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
19588 as only certain clients who must have this information sooner should
19590 - Instead of adding the svn revision to the Tor version string, report
19591 the git commit (when we're building from a git checkout).
19594 - If any of the v3 certs we download are unparseable, we should
19595 actually notice the failure so we don't retry indefinitely. Bugfix
19596 on 0.2.0.x; reported by "rotator".
19597 - If the cached cert file is unparseable, warn but don't exit.
19598 - Fix possible segmentation fault on directory authorities. Bugfix on
19600 - When Tor fails to parse a descriptor of any kind, dump it to disk.
19601 Might help diagnosing bug 1051.
19603 o Deprecated and removed features:
19604 - The controller no longer accepts the old obsolete "addr-mappings/"
19605 or "unregistered-servers-" GETINFO values.
19606 - Hidden services no longer publish version 0 descriptors, and clients
19607 do not request or use version 0 descriptors. However, the old hidden
19608 service authorities still accept and serve version 0 descriptors
19609 when contacted by older hidden services/clients.
19610 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
19611 always on; using them is necessary for correct forward-compatible
19613 - Remove support for .noconnect style addresses. Nobody was using
19614 them, and they provided another avenue for detecting Tor users
19615 via application-level web tricks.
19617 o Packaging changes:
19618 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
19619 installer bundles. See
19620 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
19621 for details of what's new in Vidalia 0.2.3.
19622 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
19623 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
19624 configuration file, rather than the old Privoxy.
19625 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
19626 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
19627 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
19628 better compatibility with OS X 10.6, aka Snow Leopard.
19629 - OS X Vidalia Bundle: The multi-package installer is now replaced
19630 by a simple drag and drop to the /Applications folder. This change
19631 occurred with the upgrade to Vidalia 0.2.3.
19634 Changes in version 0.2.1.19 - 2009-07-28
19635 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
19636 services on Tor 0.2.1.3-alpha through 0.2.1.18.
19639 - Make accessing hidden services on 0.2.1.x work right again.
19640 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
19641 part of patch provided by "optimist".
19644 - When a relay/bridge is writing out its identity key fingerprint to
19645 the "fingerprint" file and to its logs, write it without spaces. Now
19646 it will look like the fingerprints in our bridges documentation,
19647 and confuse fewer users.
19650 - Relays no longer publish a new server descriptor if they change
19651 their MaxAdvertisedBandwidth config option but it doesn't end up
19652 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
19653 fixes bug 1026. Patch from Sebastian.
19654 - Avoid leaking memory every time we get a create cell but we have
19655 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
19656 fixes bug 1034. Reported by BarkerJr.
19659 Changes in version 0.2.1.18 - 2009-07-24
19660 Tor 0.2.1.18 lays the foundations for performance improvements,
19661 adds status events to help users diagnose bootstrap problems, adds
19662 optional authentication/authorization for hidden services, fixes a
19663 variety of potential anonymity problems, and includes a huge pile of
19664 other features and bug fixes.
19667 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
19670 Changes in version 0.2.1.17-rc - 2009-07-07
19671 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
19672 candidate for the 0.2.1.x series. It lays the groundwork for further
19673 client performance improvements, and also fixes a big bug with directory
19674 authorities that were causing them to assign Guard and Stable flags
19677 The Windows bundles also finally include the geoip database that we
19678 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
19679 should actually install Torbutton rather than giving you a cryptic
19680 failure message (oops).
19683 - Clients now use the bandwidth values in the consensus, rather than
19684 the bandwidth values in each relay descriptor. This approach opens
19685 the door to more accurate bandwidth estimates once the directory
19686 authorities start doing active measurements. Implements more of
19690 - When Tor clients restart after 1-5 days, they discard all their
19691 cached descriptors as too old, but they still use the cached
19692 consensus document. This approach is good for robustness, but
19693 bad for performance: since they don't know any bandwidths, they
19694 end up choosing at random rather than weighting their choice by
19695 speed. Fixed by the above feature of putting bandwidths in the
19696 consensus. Bugfix on 0.2.0.x.
19697 - Directory authorities were neglecting to mark relays down in their
19698 internal histories if the relays fall off the routerlist without
19699 ever being found unreachable. So there were relays in the histories
19700 that haven't been seen for eight months, and are listed as being
19701 up for eight months. This wreaked havoc on the "median wfu"
19702 and "median mtbf" calculations, in turn making Guard and Stable
19703 flags very wrong, hurting network performance. Fixes bugs 696 and
19704 969. Bugfix on 0.2.0.6-alpha.
19707 - Serve the DirPortFrontPage page even when we have been approaching
19708 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
19709 - The control port would close the connection before flushing long
19710 replies, such as the network consensus, if a QUIT command was issued
19711 before the reply had completed. Now, the control port flushes all
19712 pending replies before closing the connection. Also fixed a spurious
19713 warning when a QUIT command is issued after a malformed or rejected
19714 AUTHENTICATE command, but before the connection was closed. Patch
19715 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
19716 - When we can't find an intro key for a v2 hidden service descriptor,
19717 fall back to the v0 hidden service descriptor and log a bug message.
19718 Workaround for bug 1024.
19719 - Fix a log message that did not respect the SafeLogging option.
19723 - If we're a relay and we change our IP address, be more verbose
19724 about the reason that made us change. Should help track down
19725 further bugs for relays on dynamic IP addresses.
19728 Changes in version 0.2.0.35 - 2009-06-24
19730 - Avoid crashing in the presence of certain malformed descriptors.
19731 Found by lark, and by automated fuzzing.
19732 - Fix an edge case where a malicious exit relay could convince a
19733 controller that the client's DNS question resolves to an internal IP
19734 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
19737 - Finally fix the bug where dynamic-IP relays disappear when their
19738 IP address changes: directory mirrors were mistakenly telling
19739 them their old address if they asked via begin_dir, so they
19740 never got an accurate answer about their new address, so they
19741 just vanished after a day. For belt-and-suspenders, relays that
19742 don't set Address in their config now avoid using begin_dir for
19743 all direct connections. Should fix bugs 827, 883, and 900.
19744 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
19745 that would occur on some exit nodes when DNS failures and timeouts
19746 occurred in certain patterns. Fix for bug 957.
19749 - When starting with a cache over a few days old, do not leak
19750 memory for the obsolete router descriptors in it. Bugfix on
19751 0.2.0.33; fixes bug 672.
19752 - Hidden service clients didn't use a cached service descriptor that
19753 was older than 15 minutes, but wouldn't fetch a new one either,
19754 because there was already one in the cache. Now, fetch a v2
19755 descriptor unless the same descriptor was added to the cache within
19756 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
19759 Changes in version 0.2.1.16-rc - 2009-06-20
19760 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
19761 a bunch of minor bugs.
19764 - Fix an edge case where a malicious exit relay could convince a
19765 controller that the client's DNS question resolves to an internal IP
19766 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
19768 o Major performance improvements (on 0.2.0.x):
19769 - Disable and refactor some debugging checks that forced a linear scan
19770 over the whole server-side DNS cache. These accounted for over 50%
19771 of CPU time on a relatively busy exit node's gprof profile. Found
19773 - Disable some debugging checks that appeared in exit node profile
19777 - Update to the "June 3 2009" ip-to-country file.
19778 - Do not have tor-resolve automatically refuse all .onion addresses;
19779 if AutomapHostsOnResolve is set in your torrc, this will work fine.
19781 o Minor bugfixes (on 0.2.0.x):
19782 - Log correct error messages for DNS-related network errors on
19784 - Fix a race condition that could cause crashes or memory corruption
19785 when running as a server with a controller listening for log
19787 - Avoid crashing when we have a policy specified in a DirPolicy or
19788 SocksPolicy or ReachableAddresses option with ports set on it,
19789 and we re-load the policy. May fix bug 996.
19790 - Hidden service clients didn't use a cached service descriptor that
19791 was older than 15 minutes, but wouldn't fetch a new one either,
19792 because there was already one in the cache. Now, fetch a v2
19793 descriptor unless the same descriptor was added to the cache within
19794 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
19796 o Minor bugfixes (on 0.2.1.x):
19797 - Don't warn users about low port and hibernation mix when they
19798 provide a *ListenAddress directive to fix that. Bugfix on
19800 - When switching back and forth between bridge mode, do not start
19801 gathering GeoIP data until two hours have passed.
19802 - Do not complain that the user has requested an excluded node as
19803 an exit when the node is not really an exit. This could happen
19804 because the circuit was for testing, or an introduction point.
19808 Changes in version 0.2.1.15-rc - 2009-05-25
19809 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
19810 series. It fixes a major bug on fast exit relays, as well as a variety
19811 of more minor bugs.
19813 o Major bugfixes (on 0.2.0.x):
19814 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
19815 that would occur on some exit nodes when DNS failures and timeouts
19816 occurred in certain patterns. Fix for bug 957.
19818 o Minor bugfixes (on 0.2.0.x):
19819 - Actually return -1 in the error case for read_bandwidth_usage().
19820 Harmless bug, since we currently don't care about the return value
19821 anywhere. Bugfix on 0.2.0.9-alpha.
19822 - Provide a more useful log message if bug 977 (related to buffer
19823 freelists) ever reappears, and do not crash right away.
19824 - Fix an assertion failure on 64-bit platforms when we allocated
19825 memory right up to the end of a memarea, then realigned the memory
19826 one step beyond the end. Fixes a possible cause of bug 930.
19827 - Protect the count of open sockets with a mutex, so we can't
19828 corrupt it when two threads are closing or opening sockets at once.
19829 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
19830 - Don't allow a bridge to publish its router descriptor to a
19831 non-bridge directory authority. Fixes part of bug 932.
19832 - When we change to or from being a bridge, reset our counts of
19833 client usage by country. Fixes bug 932.
19834 - Fix a bug that made stream bandwidth get misreported to the
19836 - Stop using malloc_usable_size() to use more area than we had
19837 actually allocated: it was safe, but made valgrind really unhappy.
19838 - Fix a memory leak when v3 directory authorities load their keys
19839 and cert from disk. Bugfix on 0.2.0.1-alpha.
19841 o Minor bugfixes (on 0.2.1.x):
19842 - Fix use of freed memory when deciding to mark a non-addable
19843 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
19846 Changes in version 0.2.1.14-rc - 2009-04-12
19847 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
19848 series. It begins fixing some major performance problems, and also
19849 finally addresses the bug that was causing relays on dynamic IP
19850 addresses to fall out of the directory.
19853 - Clients replace entry guards that were chosen more than a few months
19854 ago. This change should significantly improve client performance,
19855 especially once more people upgrade, since relays that have been
19856 a guard for a long time are currently overloaded.
19858 o Major bugfixes (on 0.2.0):
19859 - Finally fix the bug where dynamic-IP relays disappear when their
19860 IP address changes: directory mirrors were mistakenly telling
19861 them their old address if they asked via begin_dir, so they
19862 never got an accurate answer about their new address, so they
19863 just vanished after a day. For belt-and-suspenders, relays that
19864 don't set Address in their config now avoid using begin_dir for
19865 all direct connections. Should fix bugs 827, 883, and 900.
19866 - Relays were falling out of the networkstatus consensus for
19867 part of a day if they changed their local config but the
19868 authorities discarded their new descriptor as "not sufficiently
19869 different". Now directory authorities accept a descriptor as changed
19870 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
19871 patch by Sebastian.
19872 - Avoid crashing in the presence of certain malformed descriptors.
19873 Found by lark, and by automated fuzzing.
19876 - When generating circuit events with verbose nicknames for
19877 controllers, try harder to look up nicknames for routers on a
19878 circuit. (Previously, we would look in the router descriptors we had
19879 for nicknames, but not in the consensus.) Partial fix for bug 941.
19880 - If the bridge config line doesn't specify a port, assume 443.
19881 This makes bridge lines a bit smaller and easier for users to
19883 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
19884 bytes (aka 20KB/s), to match our documentation. Also update
19885 directory authorities so they always assign the Fast flag to relays
19886 with 20KB/s of capacity. Now people running relays won't suddenly
19887 find themselves not seeing any use, if the network gets faster
19889 - Update to the "April 3 2009" ip-to-country file.
19892 - Avoid trying to print raw memory to the logs when we decide to
19893 give up on downloading a given relay descriptor. Bugfix on
19895 - In tor-resolve, when the Tor client to use is specified by
19896 <hostname>:<port>, actually use the specified port rather than
19897 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
19898 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
19899 - When starting with a cache over a few days old, do not leak
19900 memory for the obsolete router descriptors in it. Bugfix on
19902 - Avoid double-free on list of successfully uploaded hidden
19903 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
19904 - Change memarea_strndup() implementation to work even when
19905 duplicating a string at the end of a page. This bug was
19906 harmless for now, but could have meant crashes later. Fix by
19907 lark. Bugfix on 0.2.1.1-alpha.
19908 - Limit uploaded directory documents to be 16M rather than 500K.
19909 The directory authorities were refusing v3 consensus votes from
19910 other authorities, since the votes are now 504K. Fixes bug 959;
19911 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
19912 - Directory authorities should never send a 503 "busy" response to
19913 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
19917 Changes in version 0.2.1.13-alpha - 2009-03-09
19918 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
19919 cleanups. We're finally getting close to a release candidate.
19922 - Correctly update the list of which countries we exclude as
19923 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
19924 lark. Bugfix on 0.2.1.6-alpha.
19926 o Minor bugfixes (on 0.2.0.x and earlier):
19927 - Automatically detect MacOSX versions earlier than 10.4.0, and
19928 disable kqueue from inside Tor when running with these versions.
19929 We previously did this from the startup script, but that was no
19930 help to people who didn't use the startup script. Resolves bug 863.
19931 - When we had picked an exit node for a connection, but marked it as
19932 "optional", and it turned out we had no onion key for the exit,
19933 stop wanting that exit and try again. This situation may not
19934 be possible now, but will probably become feasible with proposal
19935 158. Spotted by rovv. Fixes another case of bug 752.
19936 - Clients no longer cache certificates for authorities they do not
19937 recognize. Bugfix on 0.2.0.9-alpha.
19938 - When we can't transmit a DNS request due to a network error, retry
19939 it after a while, and eventually transmit a failing response to
19940 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
19941 - If the controller claimed responsibility for a stream, but that
19942 stream never finished making its connection, it would live
19943 forever in circuit_wait state. Now we close it after SocksTimeout
19944 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
19945 - Drop begin cells to a hidden service if they come from the middle
19946 of a circuit. Patch from lark.
19947 - When we erroneously receive two EXTEND cells for the same circuit
19948 ID on the same connection, drop the second. Patch from lark.
19949 - Fix a crash that occurs on exit nodes when a nameserver request
19950 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
19951 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
19953 - Do not assume that a stack-allocated character array will be
19954 64-bit aligned on platforms that demand that uint64_t access is
19955 aligned. Possible fix for bug 604.
19956 - Parse dates and IPv4 addresses in a locale- and libc-independent
19957 manner, to avoid platform-dependent behavior on malformed input.
19958 - Build correctly when configured to build outside the main source
19959 path. Patch from Michael Gold.
19960 - We were already rejecting relay begin cells with destination port
19961 of 0. Now also reject extend cells with destination port or address
19962 of 0. Suggested by lark.
19964 o Minor bugfixes (on 0.2.1.x):
19965 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
19966 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
19967 - If we're an exit node, scrub the IP address to which we are exiting
19968 in the logs. Bugfix on 0.2.1.8-alpha.
19971 - On Linux, use the prctl call to re-enable core dumps when the user
19973 - New controller event NEWCONSENSUS that lists the networkstatus
19974 lines for every recommended relay. Now controllers like Torflow
19975 can keep up-to-date on which relays they should be using.
19976 - Update to the "February 26 2009" ip-to-country file.
19979 Changes in version 0.2.0.34 - 2009-02-08
19980 Tor 0.2.0.34 features several more security-related fixes. You should
19981 upgrade, especially if you run an exit relay (remote crash) or a
19982 directory authority (remote infinite loop), or you're on an older
19983 (pre-XP) or not-recently-patched Windows (remote exploit).
19985 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
19986 have many known flaws, and nobody should be using them. You should
19987 upgrade. If you're using a Linux or BSD and its packages are obsolete,
19988 stop using those packages and upgrade anyway.
19991 - Fix an infinite-loop bug on handling corrupt votes under certain
19992 circumstances. Bugfix on 0.2.0.8-alpha.
19993 - Fix a temporary DoS vulnerability that could be performed by
19994 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
19995 - Avoid a potential crash on exit nodes when processing malformed
19996 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
19997 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
19998 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20001 - Fix compilation on systems where time_t is a 64-bit integer.
20002 Patch from Matthias Drochner.
20003 - Don't consider expiring already-closed client connections. Fixes
20004 bug 893. Bugfix on 0.0.2pre20.
20007 Changes in version 0.2.1.12-alpha - 2009-02-08
20008 Tor 0.2.1.12-alpha features several more security-related fixes. You
20009 should upgrade, especially if you run an exit relay (remote crash) or
20010 a directory authority (remote infinite loop), or you're on an older
20011 (pre-XP) or not-recently-patched Windows (remote exploit). It also
20012 includes a big pile of minor bugfixes and cleanups.
20015 - Fix an infinite-loop bug on handling corrupt votes under certain
20016 circumstances. Bugfix on 0.2.0.8-alpha.
20017 - Fix a temporary DoS vulnerability that could be performed by
20018 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20019 - Avoid a potential crash on exit nodes when processing malformed
20020 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
20023 - Let controllers actually ask for the "clients_seen" event for
20024 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
20025 reported by Matt Edman.
20026 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
20028 - Fix a bug in address parsing that was preventing bridges or hidden
20029 service targets from being at IPv6 addresses.
20030 - Solve a bug that kept hardware crypto acceleration from getting
20031 enabled when accounting was turned on. Fixes bug 907. Bugfix on
20033 - Remove a bash-ism from configure.in to build properly on non-Linux
20034 platforms. Bugfix on 0.2.1.1-alpha.
20035 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
20036 headers. Bugfix on 0.2.0.10-alpha.
20037 - Don't consider expiring already-closed client connections. Fixes
20038 bug 893. Bugfix on 0.0.2pre20.
20039 - Fix another interesting corner-case of bug 891 spotted by rovv:
20040 Previously, if two hosts had different amounts of clock drift, and
20041 one of them created a new connection with just the wrong timing,
20042 the other might decide to deprecate the new connection erroneously.
20043 Bugfix on 0.1.1.13-alpha.
20044 - Resolve a very rare crash bug that could occur when the user forced
20045 a nameserver reconfiguration during the middle of a nameserver
20046 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
20047 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
20048 Bugfix on 0.2.1.7-alpha.
20049 - If we're using bridges and our network goes away, be more willing
20050 to forgive our bridges and try again when we get an application
20051 request. Bugfix on 0.2.0.x.
20054 - Support platforms where time_t is 64 bits long. (Congratulations,
20055 NetBSD!) Patch from Matthias Drochner.
20056 - Add a 'getinfo status/clients-seen' controller command, in case
20057 controllers want to hear clients_seen events but connect late.
20060 - Disable GCC's strict alias optimization by default, to avoid the
20061 likelihood of its introducing subtle bugs whenever our code violates
20062 the letter of C99's alias rules.
20065 Changes in version 0.2.0.33 - 2009-01-21
20066 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
20067 useful to users. It also finally fixes a bug where a relay or client
20068 that's been off for many days would take a long time to bootstrap.
20070 This update also fixes an important security-related bug reported by
20071 Ilja van Sprundel. You should upgrade. (We'll send out more details
20072 about the bug once people have had some time to upgrade.)
20075 - Fix a heap-corruption bug that may be remotely triggerable on
20076 some platforms. Reported by Ilja van Sprundel.
20079 - When a stream at an exit relay is in state "resolving" or
20080 "connecting" and it receives an "end" relay cell, the exit relay
20081 would silently ignore the end cell and not close the stream. If
20082 the client never closes the circuit, then the exit relay never
20083 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
20084 reported by "wood".
20085 - When sending CREATED cells back for a given circuit, use a 64-bit
20086 connection ID to find the right connection, rather than an addr:port
20087 combination. Now that we can have multiple OR connections between
20088 the same ORs, it is no longer possible to use addr:port to uniquely
20089 identify a connection.
20090 - Bridge relays that had DirPort set to 0 would stop fetching
20091 descriptors shortly after startup, and then briefly resume
20092 after a new bandwidth test and/or after publishing a new bridge
20093 descriptor. Bridge users that try to bootstrap from them would
20094 get a recent networkstatus but would get descriptors from up to
20095 18 hours earlier, meaning most of the descriptors were obsolete
20096 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
20097 - Prevent bridge relays from serving their 'extrainfo' document
20098 to anybody who asks, now that extrainfo docs include potentially
20099 sensitive aggregated client geoip summaries. Bugfix on
20101 - If the cached networkstatus consensus is more than five days old,
20102 discard it rather than trying to use it. In theory it could be
20103 useful because it lists alternate directory mirrors, but in practice
20104 it just means we spend many minutes trying directory mirrors that
20105 are long gone from the network. Also discard router descriptors as
20106 we load them if they are more than five days old, since the onion
20107 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
20110 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
20111 could make gcc generate non-functional binary search code. Bugfix
20113 - Build correctly on platforms without socklen_t.
20114 - Compile without warnings on solaris.
20115 - Avoid potential crash on internal error during signature collection.
20116 Fixes bug 864. Patch from rovv.
20117 - Correct handling of possible malformed authority signing key
20118 certificates with internal signature types. Fixes bug 880.
20119 Bugfix on 0.2.0.3-alpha.
20120 - Fix a hard-to-trigger resource leak when logging credential status.
20122 - When we can't initialize DNS because the network is down, do not
20123 automatically stop Tor from starting. Instead, we retry failed
20124 dns_init() every 10 minutes, and change the exit policy to reject
20125 *:* until one succeeds. Fixes bug 691.
20126 - Use 64 bits instead of 32 bits for connection identifiers used with
20127 the controller protocol, to greatly reduce risk of identifier reuse.
20128 - When we're choosing an exit node for a circuit, and we have
20129 no pending streams, choose a good general exit rather than one that
20130 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
20131 - Fix another case of assuming, when a specific exit is requested,
20132 that we know more than the user about what hosts it allows.
20133 Fixes one case of bug 752. Patch from rovv.
20134 - Clip the MaxCircuitDirtiness config option to a minimum of 10
20135 seconds. Warn the user if lower values are given in the
20136 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
20137 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
20138 user if lower values are given in the configuration. Bugfix on
20139 0.1.1.17-rc. Patch by Sebastian.
20140 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
20141 the cache because we already had a v0 descriptor with the same ID.
20142 Bugfix on 0.2.0.18-alpha.
20143 - Fix a race condition when freeing keys shared between main thread
20144 and CPU workers that could result in a memory leak. Bugfix on
20145 0.1.0.1-rc. Fixes bug 889.
20146 - Send a valid END cell back when a client tries to connect to a
20147 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
20148 840. Patch from rovv.
20149 - Check which hops rendezvous stream cells are associated with to
20150 prevent possible guess-the-streamid injection attacks from
20151 intermediate hops. Fixes another case of bug 446. Based on patch
20153 - If a broken client asks a non-exit router to connect somewhere,
20154 do not even do the DNS lookup before rejecting the connection.
20155 Fixes another case of bug 619. Patch from rovv.
20156 - When a relay gets a create cell it can't decrypt (e.g. because it's
20157 using the wrong onion key), we were dropping it and letting the
20158 client time out. Now actually answer with a destroy cell. Fixes
20159 bug 904. Bugfix on 0.0.2pre8.
20161 o Minor bugfixes (hidden services):
20162 - Do not throw away existing introduction points on SIGHUP. Bugfix on
20163 0.0.6pre1. Patch by Karsten. Fixes bug 874.
20166 - Report the case where all signatures in a detached set are rejected
20167 differently than the case where there is an error handling the
20169 - When we realize that another process has modified our cached
20170 descriptors, print out a more useful error message rather than
20171 triggering an assertion. Fixes bug 885. Patch from Karsten.
20172 - Implement the 0x20 hack to better resist DNS poisoning: set the
20173 case on outgoing DNS requests randomly, and reject responses that do
20174 not match the case correctly. This logic can be disabled with the
20175 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
20176 of servers that do not reliably preserve case in replies. See
20177 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
20179 - Check DNS replies for more matching fields to better resist DNS
20181 - Never use OpenSSL compression: it wastes RAM and CPU trying to
20182 compress cells, which are basically all encrypted, compressed, or
20186 Changes in version 0.2.1.11-alpha - 2009-01-20
20187 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
20188 week it will take a long time to bootstrap again" bug. It also fixes
20189 an important security-related bug reported by Ilja van Sprundel. You
20190 should upgrade. (We'll send out more details about the bug once people
20191 have had some time to upgrade.)
20194 - Fix a heap-corruption bug that may be remotely triggerable on
20195 some platforms. Reported by Ilja van Sprundel.
20198 - Discard router descriptors as we load them if they are more than
20199 five days old. Otherwise if Tor is off for a long time and then
20200 starts with cached descriptors, it will try to use the onion
20201 keys in those obsolete descriptors when building circuits. Bugfix
20202 on 0.2.0.x. Fixes bug 887.
20205 - Try to make sure that the version of Libevent we're running with
20206 is binary-compatible with the one we built with. May address bug
20208 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
20209 for bug 905. Bugfix on 0.2.1.7-alpha.
20210 - Add a new --enable-local-appdata configuration switch to change
20211 the default location of the datadir on win32 from APPDATA to
20212 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
20213 entirely. Patch from coderman.
20216 - Make outbound DNS packets respect the OutboundBindAddress setting.
20217 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
20218 - When our circuit fails at the first hop (e.g. we get a destroy
20219 cell back), avoid using that OR connection anymore, and also
20220 tell all the one-hop directory requests waiting for it that they
20221 should fail. Bugfix on 0.2.1.3-alpha.
20222 - In the torify(1) manpage, mention that tsocks will leak your
20226 Changes in version 0.2.1.10-alpha - 2009-01-06
20227 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
20228 would make the bridge relay not so useful if it had DirPort set to 0,
20229 and one that could let an attacker learn a little bit of information
20230 about the bridge's users), and a bug that would cause your Tor relay
20231 to ignore a circuit create request it can't decrypt (rather than reply
20232 with an error). It also fixes a wide variety of other bugs.
20235 - If the cached networkstatus consensus is more than five days old,
20236 discard it rather than trying to use it. In theory it could
20237 be useful because it lists alternate directory mirrors, but in
20238 practice it just means we spend many minutes trying directory
20239 mirrors that are long gone from the network. Helps bug 887 a bit;
20241 - Bridge relays that had DirPort set to 0 would stop fetching
20242 descriptors shortly after startup, and then briefly resume
20243 after a new bandwidth test and/or after publishing a new bridge
20244 descriptor. Bridge users that try to bootstrap from them would
20245 get a recent networkstatus but would get descriptors from up to
20246 18 hours earlier, meaning most of the descriptors were obsolete
20247 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
20248 - Prevent bridge relays from serving their 'extrainfo' document
20249 to anybody who asks, now that extrainfo docs include potentially
20250 sensitive aggregated client geoip summaries. Bugfix on
20254 - New controller event "clients_seen" to report a geoip-based summary
20255 of which countries we've seen clients from recently. Now controllers
20256 like Vidalia can show bridge operators that they're actually making
20258 - Build correctly against versions of OpenSSL 0.9.8 or later built
20259 without support for deprecated functions.
20260 - Update to the "December 19 2008" ip-to-country file.
20262 o Minor bugfixes (on 0.2.0.x):
20263 - Authorities now vote for the Stable flag for any router whose
20264 weighted MTBF is at least 5 days, regardless of the mean MTBF.
20265 - Do not remove routers as too old if we do not have any consensus
20266 document. Bugfix on 0.2.0.7-alpha.
20267 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
20268 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20269 - When an exit relay resolves a stream address to a local IP address,
20270 do not just keep retrying that same exit relay over and
20271 over. Instead, just close the stream. Addresses bug 872. Bugfix
20272 on 0.2.0.32. Patch from rovv.
20273 - If a hidden service sends us an END cell, do not consider
20274 retrying the connection; just close it. Patch from rovv.
20275 - When we made bridge authorities stop serving bridge descriptors over
20276 unencrypted links, we also broke DirPort reachability testing for
20277 bridges. So bridges with a non-zero DirPort were printing spurious
20278 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
20279 - When a relay gets a create cell it can't decrypt (e.g. because it's
20280 using the wrong onion key), we were dropping it and letting the
20281 client time out. Now actually answer with a destroy cell. Fixes
20282 bug 904. Bugfix on 0.0.2pre8.
20283 - Squeeze 2-5% out of client performance (according to oprofile) by
20284 improving the implementation of some policy-manipulation functions.
20286 o Minor bugfixes (on 0.2.1.x):
20287 - Make get_interface_address() function work properly again; stop
20288 guessing the wrong parts of our address as our address.
20289 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
20290 send on that circuit. Otherwise we might violate the proposal-110
20291 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
20293 - When we're sending non-EXTEND cells to the first hop in a circuit,
20294 for example to use an encrypted directory connection, we don't need
20295 to use RELAY_EARLY cells: the first hop knows what kind of cell
20296 it is, and nobody else can even see the cell type. Conserving
20297 RELAY_EARLY cells makes it easier to cannibalize circuits like
20299 - Stop logging nameserver addresses in reverse order.
20300 - If we are retrying a directory download slowly over and over, do
20301 not automatically give up after the 254th failure. Bugfix on
20303 - Resume reporting accurate "stream end" reasons to the local control
20304 port. They were lost in the changes for Proposal 148. Bugfix on
20307 o Deprecated and removed features:
20308 - The old "tor --version --version" command, which would print out
20309 the subversion "Id" of most of the source files, is now removed. It
20310 turned out to be less useful than we'd expected, and harder to
20313 o Code simplifications and refactoring:
20314 - Change our header file guard macros to be less likely to conflict
20315 with system headers. Adam Langley noticed that we were conflicting
20316 with log.h on Android.
20317 - Tool-assisted documentation cleanup. Nearly every function or
20318 static variable in Tor should have its own documentation now.
20321 Changes in version 0.2.1.9-alpha - 2008-12-25
20322 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
20324 o New directory authorities:
20325 - gabelmoo (the authority run by Karsten Loesing) now has a new
20329 - Never use a connection with a mismatched address to extend a
20330 circuit, unless that connection is canonical. A canonical
20331 connection is one whose address is authenticated by the router's
20332 identity key, either in a NETINFO cell or in a router descriptor.
20333 - Avoid a possible memory corruption bug when receiving hidden service
20334 descriptors. Bugfix on 0.2.1.6-alpha.
20337 - Fix a logic error that would automatically reject all but the first
20338 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
20339 part of bug 813/868. Bug spotted by coderman.
20340 - When a stream at an exit relay is in state "resolving" or
20341 "connecting" and it receives an "end" relay cell, the exit relay
20342 would silently ignore the end cell and not close the stream. If
20343 the client never closes the circuit, then the exit relay never
20344 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
20345 reported by "wood".
20346 - When we can't initialize DNS because the network is down, do not
20347 automatically stop Tor from starting. Instead, retry failed
20348 dns_init() every 10 minutes, and change the exit policy to reject
20349 *:* until one succeeds. Fixes bug 691.
20352 - Give a better error message when an overzealous init script says
20353 "sudo -u username tor --user username". Makes Bug 882 easier for
20355 - When a directory authority gives us a new guess for our IP address,
20356 log which authority we used. Hopefully this will help us debug
20357 the recent complaints about bad IP address guesses.
20358 - Detect svn revision properly when we're using git-svn.
20359 - Try not to open more than one descriptor-downloading connection
20360 to an authority at once. This should reduce load on directory
20361 authorities. Fixes bug 366.
20362 - Add cross-certification to newly generated certificates, so that
20363 a signing key is enough information to look up a certificate.
20364 Partial implementation of proposal 157.
20365 - Start serving certificates by <identity digest, signing key digest>
20366 pairs. Partial implementation of proposal 157.
20367 - Clients now never report any stream end reason except 'MISC'.
20368 Implements proposal 148.
20369 - On platforms with a maximum syslog string length, truncate syslog
20370 messages to that length ourselves, rather than relying on the
20371 system to do it for us.
20372 - Optimize out calls to time(NULL) that occur for every IO operation,
20373 or for every cell. On systems where time() is a slow syscall,
20374 this fix will be slightly helpful.
20375 - Exit servers can now answer resolve requests for ip6.arpa addresses.
20376 - When we download a descriptor that we then immediately (as
20377 a directory authority) reject, do not retry downloading it right
20378 away. Should save some bandwidth on authorities. Fix for bug
20379 888. Patch by Sebastian Hahn.
20380 - When a download gets us zero good descriptors, do not notify
20381 Tor that new directory information has arrived.
20382 - Avoid some nasty corner cases in the logic for marking connections
20383 as too old or obsolete or noncanonical for circuits. Partial
20386 o Minor features (controller):
20387 - New CONSENSUS_ARRIVED event to note when a new consensus has
20388 been fetched and validated.
20389 - When we realize that another process has modified our cached
20390 descriptors file, print out a more useful error message rather
20391 than triggering an assertion. Fixes bug 885. Patch from Karsten.
20392 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
20393 controllers to prevent SIGHUP from reloading the
20394 configuration. Fixes bug 856.
20397 - Resume using the correct "REASON=" stream when telling the
20398 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
20399 - When a canonical connection appears later in our internal list
20400 than a noncanonical one for a given OR ID, always use the
20401 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
20403 - Clip the MaxCircuitDirtiness config option to a minimum of 10
20404 seconds. Warn the user if lower values are given in the
20405 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
20406 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
20407 user if lower values are given in the configuration. Bugfix on
20408 0.1.1.17-rc. Patch by Sebastian.
20409 - Fix a race condition when freeing keys shared between main thread
20410 and CPU workers that could result in a memory leak. Bugfix on
20411 0.1.0.1-rc. Fixes bug 889.
20413 o Minor bugfixes (hidden services):
20414 - Do not throw away existing introduction points on SIGHUP (bugfix on
20415 0.0.6pre1); also, do not stall hidden services because we're
20416 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
20417 by John Brooks. Patch by Karsten. Fixes bug 874.
20418 - Fix a memory leak when we decline to add a v2 rendezvous
20419 descriptor to the cache because we already had a v0 descriptor
20420 with the same ID. Bugfix on 0.2.0.18-alpha.
20422 o Deprecated and removed features:
20423 - RedirectExits has been removed. It was deprecated since
20425 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
20426 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
20427 - Cell pools are now always enabled; --disable-cell-pools is ignored.
20429 o Code simplifications and refactoring:
20430 - Rename the confusing or_is_obsolete field to the more appropriate
20431 is_bad_for_new_circs, and move it to or_connection_t where it
20433 - Move edge-only flags from connection_t to edge_connection_t: not
20434 only is this better coding, but on machines of plausible alignment,
20435 it should save 4-8 bytes per connection_t. "Every little bit helps."
20436 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
20437 for consistency; keep old option working for backward compatibility.
20438 - Simplify the code for finding connections to use for a circuit.
20441 Changes in version 0.2.1.8-alpha - 2008-12-08
20442 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
20443 builds better on unusual platforms like Solaris and old OS X, and
20444 fixes a variety of other issues.
20447 - New DirPortFrontPage option that takes an html file and publishes
20448 it as "/" on the DirPort. Now relay operators can provide a
20449 disclaimer without needing to set up a separate webserver. There's
20450 a sample disclaimer in contrib/tor-exit-notice.html.
20453 - When the client is choosing entry guards, now it selects at most
20454 one guard from a given relay family. Otherwise we could end up with
20455 all of our entry points into the network run by the same operator.
20456 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
20459 - Fix a DOS opportunity during the voting signature collection process
20460 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
20461 - Fix a possible segfault when establishing an exit connection. Bugfix
20465 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
20467 - Made Tor a little less aggressive about deleting expired
20468 certificates. Partial fix for bug 854.
20469 - Stop doing unaligned memory access that generated bus errors on
20470 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
20471 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
20472 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
20473 - Make USR2 log-level switch take effect immediately. Bugfix on
20475 - If one win32 nameserver fails to get added, continue adding the
20476 rest, and don't automatically fail.
20477 - Use fcntl() for locking when flock() is not available. Should fix
20478 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
20479 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
20480 could make gcc generate non-functional binary search code. Bugfix
20482 - Build correctly on platforms without socklen_t.
20483 - Avoid potential crash on internal error during signature collection.
20484 Fixes bug 864. Patch from rovv.
20485 - Do not use C's stdio library for writing to log files. This will
20486 improve logging performance by a minute amount, and will stop
20487 leaking fds when our disk is full. Fixes bug 861.
20488 - Stop erroneous use of O_APPEND in cases where we did not in fact
20489 want to re-seek to the end of a file before every last write().
20490 - Correct handling of possible malformed authority signing key
20491 certificates with internal signature types. Fixes bug 880. Bugfix
20493 - Fix a hard-to-trigger resource leak when logging credential status.
20497 - Directory mirrors no longer fetch the v1 directory or
20498 running-routers files. They are obsolete, and nobody asks for them
20499 anymore. This is the first step to making v1 authorities obsolete.
20501 o Minor features (controller):
20502 - Return circuit purposes in response to GETINFO circuit-status. Fixes
20506 Changes in version 0.2.0.32 - 2008-11-20
20507 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
20508 packages (and maybe other packages) noticed by Theo de Raadt, fixes
20509 a smaller security flaw that might allow an attacker to access local
20510 services, further improves hidden service performance, and fixes a
20511 variety of other issues.
20514 - The "User" and "Group" config options did not clear the
20515 supplementary group entries for the Tor process. The "User" option
20516 is now more robust, and we now set the groups to the specified
20517 user's primary group. The "Group" option is now ignored. For more
20518 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
20519 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
20520 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
20521 - The "ClientDNSRejectInternalAddresses" config option wasn't being
20522 consistently obeyed: if an exit relay refuses a stream because its
20523 exit policy doesn't allow it, we would remember what IP address
20524 the relay said the destination address resolves to, even if it's
20525 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
20528 - Fix a DOS opportunity during the voting signature collection process
20529 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
20531 o Major bugfixes (hidden services):
20532 - When fetching v0 and v2 rendezvous service descriptors in parallel,
20533 we were failing the whole hidden service request when the v0
20534 descriptor fetch fails, even if the v2 fetch is still pending and
20535 might succeed. Similarly, if the last v2 fetch fails, we were
20536 failing the whole hidden service request even if a v0 fetch is
20537 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
20538 - When extending a circuit to a hidden service directory to upload a
20539 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
20540 requests failed, because the router descriptor has not been
20541 downloaded yet. In these cases, do not attempt to upload the
20542 rendezvous descriptor, but wait until the router descriptor is
20543 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
20544 descriptor from a hidden service directory for which the router
20545 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
20549 - Fix several infrequent memory leaks spotted by Coverity.
20550 - When testing for libevent functions, set the LDFLAGS variable
20551 correctly. Found by Riastradh.
20552 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
20553 bootstrapping with tunneled directory connections. Bugfix on
20554 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
20555 - When asked to connect to A.B.exit:80, if we don't know the IP for A
20556 and we know that server B rejects most-but-not all connections to
20557 port 80, we would previously reject the connection. Now, we assume
20558 the user knows what they were asking for. Fixes bug 752. Bugfix
20559 on 0.0.9rc5. Diagnosed by BarkerJr.
20560 - If we overrun our per-second write limits a little, count this as
20561 having used up our write allocation for the second, and choke
20562 outgoing directory writes. Previously, we had only counted this when
20563 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
20564 Bugfix on 0.2.0.x (??).
20565 - Remove the old v2 directory authority 'lefkada' from the default
20566 list. It has been gone for many months.
20567 - Stop doing unaligned memory access that generated bus errors on
20568 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
20569 - Make USR2 log-level switch take effect immediately. Bugfix on
20572 o Minor bugfixes (controller):
20573 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
20574 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
20577 Changes in version 0.2.1.7-alpha - 2008-11-08
20578 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
20579 packages (and maybe other packages) noticed by Theo de Raadt, fixes
20580 a smaller security flaw that might allow an attacker to access local
20581 services, adds better defense against DNS poisoning attacks on exit
20582 relays, further improves hidden service performance, and fixes a
20583 variety of other issues.
20586 - The "ClientDNSRejectInternalAddresses" config option wasn't being
20587 consistently obeyed: if an exit relay refuses a stream because its
20588 exit policy doesn't allow it, we would remember what IP address
20589 the relay said the destination address resolves to, even if it's
20590 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
20591 - The "User" and "Group" config options did not clear the
20592 supplementary group entries for the Tor process. The "User" option
20593 is now more robust, and we now set the groups to the specified
20594 user's primary group. The "Group" option is now ignored. For more
20595 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
20596 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
20597 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
20598 - Do not use or believe expired v3 authority certificates. Patch
20599 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
20602 - Now NodeFamily and MyFamily config options allow spaces in
20603 identity fingerprints, so it's easier to paste them in.
20604 Suggested by Lucky Green.
20605 - Implement the 0x20 hack to better resist DNS poisoning: set the
20606 case on outgoing DNS requests randomly, and reject responses that do
20607 not match the case correctly. This logic can be disabled with the
20608 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
20609 of servers that do not reliably preserve case in replies. See
20610 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
20612 - Preserve case in replies to DNSPort requests in order to support
20613 the 0x20 hack for resisting DNS poisoning attacks.
20615 o Hidden service performance improvements:
20616 - When the client launches an introduction circuit, retry with a
20617 new circuit after 30 seconds rather than 60 seconds.
20618 - Launch a second client-side introduction circuit in parallel
20619 after a delay of 15 seconds (based on work by Christian Wilms).
20620 - Hidden services start out building five intro circuits rather
20621 than three, and when the first three finish they publish a service
20622 descriptor using those. Now we publish our service descriptor much
20623 faster after restart.
20626 - Minor fix in the warning messages when you're having problems
20627 bootstrapping; also, be more forgiving of bootstrap problems when
20628 we're still making incremental progress on a given bootstrap phase.
20629 - When we're choosing an exit node for a circuit, and we have
20630 no pending streams, choose a good general exit rather than one that
20631 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
20632 - Send a valid END cell back when a client tries to connect to a
20633 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
20634 840. Patch from rovv.
20635 - If a broken client asks a non-exit router to connect somewhere,
20636 do not even do the DNS lookup before rejecting the connection.
20637 Fixes another case of bug 619. Patch from rovv.
20638 - Fix another case of assuming, when a specific exit is requested,
20639 that we know more than the user about what hosts it allows.
20640 Fixes another case of bug 752. Patch from rovv.
20641 - Check which hops rendezvous stream cells are associated with to
20642 prevent possible guess-the-streamid injection attacks from
20643 intermediate hops. Fixes another case of bug 446. Based on patch
20645 - Avoid using a negative right-shift when comparing 32-bit
20646 addresses. Possible fix for bug 845 and bug 811.
20647 - Make the assert_circuit_ok() function work correctly on circuits that
20648 have already been marked for close.
20649 - Fix read-off-the-end-of-string error in unit tests when decoding
20650 introduction points.
20651 - Fix uninitialized size field for memory area allocation: may improve
20652 memory performance during directory parsing.
20653 - Treat duplicate certificate fetches as failures, so that we do
20654 not try to re-fetch an expired certificate over and over and over.
20655 - Do not say we're fetching a certificate when we'll in fact skip it
20656 because of a pending download.
20659 Changes in version 0.2.1.6-alpha - 2008-09-30
20660 Tor 0.2.1.6-alpha further improves performance and robustness of
20661 hidden services, starts work on supporting per-country relay selection,
20662 and fixes a variety of smaller issues.
20665 - Implement proposal 121: make it possible to build hidden services
20666 that only certain clients are allowed to connect to. This is
20667 enforced at several points, so that unauthorized clients are unable
20668 to send INTRODUCE cells to the service, or even (depending on the
20669 type of authentication) to learn introduction points. This feature
20670 raises the bar for certain kinds of active attacks against hidden
20671 services. Code by Karsten Loesing.
20672 - Relays now store and serve v2 hidden service descriptors by default,
20673 i.e., the new default value for HidServDirectoryV2 is 1. This is
20674 the last step in proposal 114, which aims to make hidden service
20675 lookups more reliable.
20676 - Start work to allow node restrictions to include country codes. The
20677 syntax to exclude nodes in a country with country code XX is
20678 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
20679 refinement to decide what config options should take priority if
20680 you ask to both use a particular node and exclude it.
20681 - Allow ExitNodes list to include IP ranges and country codes, just
20682 like the Exclude*Nodes lists. Patch from Robert Hogan.
20685 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
20686 Tor to fail to start if you had it configured to use a bridge
20687 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
20688 - When extending a circuit to a hidden service directory to upload a
20689 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
20690 requests failed, because the router descriptor had not been
20691 downloaded yet. In these cases, we now wait until the router
20692 descriptor is downloaded, and then retry. Likewise, clients
20693 now skip over a hidden service directory if they don't yet have
20694 its router descriptor, rather than futilely requesting it and
20695 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
20697 - When fetching v0 and v2 rendezvous service descriptors in parallel,
20698 we were failing the whole hidden service request when the v0
20699 descriptor fetch fails, even if the v2 fetch is still pending and
20700 might succeed. Similarly, if the last v2 fetch fails, we were
20701 failing the whole hidden service request even if a v0 fetch is
20702 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
20703 - DNS replies need to have names matching their requests, but
20704 these names should be in the questions section, not necessarily
20705 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
20708 - Update to the "September 1 2008" ip-to-country file.
20709 - Allow ports 465 and 587 in the default exit policy again. We had
20710 rejected them in 0.1.0.15, because back in 2005 they were commonly
20711 misconfigured and ended up as spam targets. We hear they are better
20712 locked down these days.
20713 - Use a lockfile to make sure that two Tor processes are not
20714 simultaneously running with the same datadir.
20715 - Serve the latest v3 networkstatus consensus via the control
20716 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
20717 - Better logging about stability/reliability calculations on directory
20719 - Drop the requirement to have an open dir port for storing and
20720 serving v2 hidden service descriptors.
20721 - Directory authorities now serve a /tor/dbg-stability.txt URL to
20722 help debug WFU and MTBF calculations.
20723 - Implement most of Proposal 152: allow specialized servers to permit
20724 single-hop circuits, and clients to use those servers to build
20725 single-hop circuits when using a specialized controller. Patch
20726 from Josh Albrecht. Resolves feature request 768.
20727 - Add a -p option to tor-resolve for specifying the SOCKS port: some
20728 people find host:port too confusing.
20729 - Make TrackHostExit mappings expire a while after their last use, not
20730 after their creation. Patch from Robert Hogan.
20731 - Provide circuit purposes along with circuit events to the controller.
20734 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
20736 - Fixed some memory leaks -- some quite frequent, some almost
20737 impossible to trigger -- based on results from Coverity.
20738 - When testing for libevent functions, set the LDFLAGS variable
20739 correctly. Found by Riastradh.
20740 - Fix an assertion bug in parsing policy-related options; possible fix
20742 - Catch and report a few more bootstrapping failure cases when Tor
20743 fails to establish a TCP connection. Cleanup on 0.2.1.x.
20744 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
20745 bootstrapping with tunneled directory connections. Bugfix on
20746 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
20747 - When asked to connect to A.B.exit:80, if we don't know the IP for A
20748 and we know that server B rejects most-but-not all connections to
20749 port 80, we would previously reject the connection. Now, we assume
20750 the user knows what they were asking for. Fixes bug 752. Bugfix
20751 on 0.0.9rc5. Diagnosed by BarkerJr.
20752 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
20753 service directories if they have no advertised dir port. Bugfix
20755 - If we overrun our per-second write limits a little, count this as
20756 having used up our write allocation for the second, and choke
20757 outgoing directory writes. Previously, we had only counted this when
20758 we had met our limits precisely. Fixes bug 824. Patch by rovv.
20759 Bugfix on 0.2.0.x (??).
20760 - Avoid a "0 divided by 0" calculation when calculating router uptime
20761 at directory authorities. Bugfix on 0.2.0.8-alpha.
20762 - Make DNS resolved controller events into "CLOSED", not
20763 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
20765 - Fix a bug where an unreachable relay would establish enough
20766 reachability testing circuits to do a bandwidth test -- if
20767 we already have a connection to the middle hop of the testing
20768 circuit, then it could establish the last hop by using the existing
20769 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
20770 circuits no longer use entry guards in 0.2.1.3-alpha.
20771 - If we have correct permissions on $datadir, we complain to stdout
20772 and fail to start. But dangerous permissions on
20773 $datadir/cached-status/ would cause us to open a log and complain
20774 there. Now complain to stdout and fail to start in both cases. Fixes
20775 bug 820, reported by seeess.
20776 - Remove the old v2 directory authority 'lefkada' from the default
20777 list. It has been gone for many months.
20779 o Code simplifications and refactoring:
20780 - Revise the connection_new functions so that a more typesafe variant
20781 exists. This will work better with Coverity, and let us find any
20782 actual mistakes we're making here.
20783 - Refactor unit testing logic so that dmalloc can be used sensibly
20784 with unit tests to check for memory leaks.
20785 - Move all hidden-service related fields from connection and circuit
20786 structure to substructures: this way they won't eat so much memory.
20789 Changes in version 0.2.0.31 - 2008-09-03
20790 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
20791 a big bug we're seeing where in rare cases traffic from one Tor stream
20792 gets mixed into another stream, and fixes a variety of smaller issues.
20795 - Make sure that two circuits can never exist on the same connection
20796 with the same circuit ID, even if one is marked for close. This
20797 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
20798 - Relays now reject risky extend cells: if the extend cell includes
20799 a digest of all zeroes, or asks to extend back to the relay that
20800 sent the extend cell, tear down the circuit. Ideas suggested
20802 - If not enough of our entry guards are available so we add a new
20803 one, we might use the new one even if it overlapped with the
20804 current circuit's exit relay (or its family). Anonymity bugfix
20805 pointed out by rovv.
20808 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
20809 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
20810 - Correctly detect the presence of the linux/netfilter_ipv4.h header
20811 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
20812 - Pick size of default geoip filename string correctly on windows.
20813 Fixes bug 806. Bugfix on 0.2.0.30.
20814 - Make the autoconf script accept the obsolete --with-ssl-dir
20815 option as an alias for the actually-working --with-openssl-dir
20816 option. Fix the help documentation to recommend --with-openssl-dir.
20817 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
20818 - When using the TransPort option on OpenBSD, and using the User
20819 option to change UID and drop privileges, make sure to open
20820 /dev/pf before dropping privileges. Fixes bug 782. Patch from
20821 Christopher Davis. Bugfix on 0.1.2.1-alpha.
20822 - Try to attach connections immediately upon receiving a RENDEZVOUS2
20823 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
20824 on the client side when connecting to a hidden service. Bugfix
20825 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
20826 - When closing an application-side connection because its circuit is
20827 getting torn down, generate the stream event correctly. Bugfix on
20828 0.1.2.x. Anonymous patch.
20831 Changes in version 0.2.1.5-alpha - 2008-08-31
20832 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
20833 in a lot of the infrastructure for adding authorization to hidden
20834 services, lays the groundwork for having clients read their load
20835 balancing information out of the networkstatus consensus rather than
20836 the individual router descriptors, addresses two potential anonymity
20837 issues, and fixes a variety of smaller issues.
20840 - Convert many internal address representations to optionally hold
20842 - Generate and accept IPv6 addresses in many protocol elements.
20843 - Make resolver code handle nameservers located at ipv6 addresses.
20844 - Begin implementation of proposal 121 ("Client authorization for
20845 hidden services"): configure hidden services with client
20846 authorization, publish descriptors for them, and configure
20847 authorization data for hidden services at clients. The next
20848 step is to actually access hidden services that perform client
20850 - More progress toward proposal 141: Network status consensus
20851 documents and votes now contain bandwidth information for each
20852 router and a summary of that router's exit policy. Eventually this
20853 will be used by clients so that they do not have to download every
20854 known descriptor before building circuits.
20856 o Major bugfixes (on 0.2.0.x and before):
20857 - When sending CREATED cells back for a given circuit, use a 64-bit
20858 connection ID to find the right connection, rather than an addr:port
20859 combination. Now that we can have multiple OR connections between
20860 the same ORs, it is no longer possible to use addr:port to uniquely
20861 identify a connection.
20862 - Relays now reject risky extend cells: if the extend cell includes
20863 a digest of all zeroes, or asks to extend back to the relay that
20864 sent the extend cell, tear down the circuit. Ideas suggested
20866 - If not enough of our entry guards are available so we add a new
20867 one, we might use the new one even if it overlapped with the
20868 current circuit's exit relay (or its family). Anonymity bugfix
20869 pointed out by rovv.
20872 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
20873 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
20874 - When using the TransPort option on OpenBSD, and using the User
20875 option to change UID and drop privileges, make sure to open /dev/pf
20876 before dropping privileges. Fixes bug 782. Patch from Christopher
20877 Davis. Bugfix on 0.1.2.1-alpha.
20878 - Correctly detect the presence of the linux/netfilter_ipv4.h header
20879 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
20880 - Add a missing safe_str() call for a debug log message.
20881 - Use 64 bits instead of 32 bits for connection identifiers used with
20882 the controller protocol, to greatly reduce risk of identifier reuse.
20883 - Make the autoconf script accept the obsolete --with-ssl-dir
20884 option as an alias for the actually-working --with-openssl-dir
20885 option. Fix the help documentation to recommend --with-openssl-dir.
20886 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
20889 - Rate-limit too-many-sockets messages: when they happen, they happen
20890 a lot. Resolves bug 748.
20891 - Resist DNS poisoning a little better by making sure that names in
20892 answer sections match.
20893 - Print the SOCKS5 error message string as well as the error code
20894 when a tor-resolve request fails. Patch from Jacob.
20897 Changes in version 0.2.1.4-alpha - 2008-08-04
20898 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
20901 - The address part of exit policies was not correctly written
20902 to router descriptors. This generated router descriptors that failed
20903 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
20905 - Tor triggered a false assert when extending a circuit to a relay
20906 but we already have a connection open to that relay. Noticed by
20907 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
20910 - Fix a hidden service logging bug: in some edge cases, the router
20911 descriptor of a previously picked introduction point becomes
20912 obsolete and we need to give up on it rather than continually
20913 complaining that it has become obsolete. Observed by xiando. Bugfix
20916 o Removed features:
20917 - Take out the TestVia config option, since it was a workaround for
20918 a bug that was fixed in Tor 0.1.1.21.
20921 Changes in version 0.2.1.3-alpha - 2008-08-03
20922 Tor 0.2.1.3-alpha implements most of the pieces to prevent
20923 infinite-length circuit attacks (see proposal 110); fixes a bug that
20924 might cause exit relays to corrupt streams they send back; allows
20925 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
20926 ExcludeExitNodes config options; and fixes a big pile of bugs.
20928 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
20929 - Send a bootstrap problem "warn" event on the first problem if the
20930 reason is NO_ROUTE (that is, our network is down).
20933 - Implement most of proposal 110: The first K cells to be sent
20934 along a circuit are marked as special "early" cells; only K "early"
20935 cells will be allowed. Once this code is universal, we can block
20936 certain kinds of DOS attack by requiring that EXTEND commands must
20937 be sent using an "early" cell.
20940 - Try to attach connections immediately upon receiving a RENDEZVOUS2
20941 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
20942 on the client side when connecting to a hidden service. Bugfix
20943 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
20944 - Ensure that two circuits can never exist on the same connection
20945 with the same circuit ID, even if one is marked for close. This
20946 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
20949 - When relays do their initial bandwidth measurement, don't limit
20950 to just our entry guards for the test circuits. Otherwise we tend
20951 to have multiple test circuits going through a single entry guard,
20952 which makes our bandwidth test less accurate. Fixes part of bug 654;
20953 patch contributed by Josh Albrecht.
20954 - Add an ExcludeExitNodes option so users can list a set of nodes
20955 that should be be excluded from the exit node position, but
20956 allowed elsewhere. Implements proposal 151.
20957 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
20958 ExcludeNodes and ExcludeExitNodes lists.
20959 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
20960 be more efficient. Formerly it was quadratic in the number of
20961 servers; now it should be linear. Fixes bug 509.
20962 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
20963 and n_conn_id_digest fields into a separate structure that's
20964 only needed when the circuit has not yet attached to an n_conn.
20967 - Change the contrib/tor.logrotate script so it makes the new
20968 logs as "_tor:_tor" rather than the default, which is generally
20969 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
20970 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
20971 warnings (occasionally), but it can also cause the compiler to
20972 eliminate error-checking code. Suggested by Peter Gutmann.
20973 - When a hidden service is giving up on an introduction point candidate
20974 that was not included in the last published rendezvous descriptor,
20975 don't reschedule publication of the next descriptor. Fixes bug 763.
20977 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
20978 HiddenServiceExcludeNodes as obsolete: they never worked properly,
20979 and nobody claims to be using them. Fixes bug 754. Bugfix on
20980 0.1.0.1-rc. Patch from Christian Wilms.
20981 - Fix a small alignment and memory-wasting bug on buffer chunks.
20984 o Minor bugfixes (controller):
20985 - When closing an application-side connection because its circuit
20986 is getting torn down, generate the stream event correctly.
20987 Bugfix on 0.1.2.x. Anonymous patch.
20989 o Removed features:
20990 - Remove all backward-compatibility code to support relays running
20991 versions of Tor so old that they no longer work at all on the
20995 Changes in version 0.2.0.30 - 2008-07-15
20997 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
20998 warnings (occasionally), but it can also cause the compiler to
20999 eliminate error-checking code. Suggested by Peter Gutmann.
21002 Changes in version 0.2.0.29-rc - 2008-07-08
21003 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
21004 hidden-service performance bugs, and fixes a bunch of smaller bugs.
21007 - If you have more than one bridge but don't know their keys,
21008 you would only launch a request for the descriptor of the first one
21009 on your list. (Tor considered launching requests for the others, but
21010 found that it already had a connection on the way for $0000...0000
21011 so it didn't open another.) Bugfix on 0.2.0.x.
21012 - If you have more than one bridge but don't know their keys, and the
21013 connection to one of the bridges failed, you would cancel all
21014 pending bridge connections. (After all, they all have the same
21015 digest.) Bugfix on 0.2.0.x.
21016 - When a hidden service was trying to establish an introduction point,
21017 and Tor had built circuits preemptively for such purposes, we
21018 were ignoring all the preemptive circuits and launching a new one
21019 instead. Bugfix on 0.2.0.14-alpha.
21020 - When a hidden service was trying to establish an introduction point,
21021 and Tor *did* manage to reuse one of the preemptively built
21022 circuits, it didn't correctly remember which one it used,
21023 so it asked for another one soon after, until there were no
21024 more preemptive circuits, at which point it launched one from
21025 scratch. Bugfix on 0.0.9.x.
21026 - Make directory servers include the X-Your-Address-Is: http header in
21027 their responses even for begin_dir conns. Now clients who only
21028 ever use begin_dir connections still have a way to learn their IP
21029 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
21032 - Fix a macro/CPP interaction that was confusing some compilers:
21033 some GCCs don't like #if/#endif pairs inside macro arguments.
21035 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
21036 Fixes bug 704; fix from Steven Murdoch.
21037 - When opening /dev/null in finish_daemonize(), do not pass the
21038 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
21039 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
21040 - Correctly detect transparent proxy support on Linux hosts that
21041 require in.h to be included before netfilter_ipv4.h. Patch
21043 - Disallow session resumption attempts during the renegotiation
21044 stage of the v2 handshake protocol. Clients should never be trying
21045 session resumption at this point, but apparently some did, in
21046 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
21047 found by Geoff Goodell.
21050 Changes in version 0.2.1.2-alpha - 2008-06-20
21051 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
21052 make it easier to set up your own private Tor network; fixes several
21053 big bugs with using more than one bridge relay; fixes a big bug with
21054 offering hidden services quickly after Tor starts; and uses a better
21055 API for reporting potential bootstrapping problems to the controller.
21058 - New TestingTorNetwork config option to allow adjustment of
21059 previously constant values that, while reasonable, could slow
21060 bootstrapping. Implements proposal 135. Patch from Karsten.
21063 - If you have more than one bridge but don't know their digests,
21064 you would only learn a request for the descriptor of the first one
21065 on your list. (Tor considered launching requests for the others, but
21066 found that it already had a connection on the way for $0000...0000
21067 so it didn't open another.) Bugfix on 0.2.0.x.
21068 - If you have more than one bridge but don't know their digests,
21069 and the connection to one of the bridges failed, you would cancel
21070 all pending bridge connections. (After all, they all have the
21071 same digest.) Bugfix on 0.2.0.x.
21072 - When establishing a hidden service, introduction points that
21073 originate from cannibalized circuits are completely ignored and not
21074 included in rendezvous service descriptors. This might be another
21075 reason for delay in making a hidden service available. Bugfix
21076 from long ago (0.0.9.x?)
21079 - Allow OpenSSL to use dynamic locks if it wants.
21080 - When building a consensus, do not include routers that are down.
21081 This will cut down 30% to 40% on consensus size. Implements
21083 - In directory authorities' approved-routers files, allow
21084 fingerprints with or without space.
21085 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
21086 controller can query our current bootstrap state in case it attaches
21087 partway through and wants to catch up.
21088 - Send an initial "Starting" bootstrap status event, so we have a
21089 state to start out in.
21092 - Asking for a conditional consensus at .../consensus/<fingerprints>
21093 would crash a dirserver if it did not already have a
21094 consensus. Bugfix on 0.2.1.1-alpha.
21095 - Clean up some macro/CPP interactions: some GCC versions don't like
21096 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
21099 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
21100 - Directory authorities shouldn't complain about bootstrapping
21101 problems just because they do a lot of reachability testing and
21102 some of the connection attempts fail.
21103 - Start sending "count" and "recommendation" key/value pairs in
21104 bootstrap problem status events, so the controller can hear about
21105 problems even before Tor decides they're worth reporting for sure.
21106 - If you're using bridges, generate "bootstrap problem" warnings
21107 as soon as you run out of working bridges, rather than waiting
21108 for ten failures -- which will never happen if you have less than
21110 - If we close our OR connection because there's been a circuit
21111 pending on it for too long, we were telling our bootstrap status
21112 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
21115 Changes in version 0.2.1.1-alpha - 2008-06-13
21116 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
21117 were making the Tor process bloat especially on Linux; makes our TLS
21118 handshake blend in better; sends "bootstrap phase" status events to
21119 the controller, so it can keep the user informed of progress (and
21120 problems) fetching directory information and establishing circuits;
21121 and adds a variety of smaller features.
21124 - More work on making our TLS handshake blend in: modify the list
21125 of ciphers advertised by OpenSSL in client mode to even more
21126 closely resemble a common web browser. We cheat a little so that
21127 we can advertise ciphers that the locally installed OpenSSL doesn't
21129 - Start sending "bootstrap phase" status events to the controller,
21130 so it can keep the user informed of progress fetching directory
21131 information and establishing circuits. Also inform the controller
21132 if we think we're stuck at a particular bootstrap phase. Implements
21134 - Resume using OpenSSL's RAND_poll() for better (and more portable)
21135 cross-platform entropy collection again. We used to use it, then
21136 stopped using it because of a bug that could crash systems that
21137 called RAND_poll when they had a lot of fds open. It looks like the
21138 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
21139 at startup, and to call RAND_poll() when we reseed later only if
21140 we have a non-buggy OpenSSL version.
21143 - When we choose to abandon a new entry guard because we think our
21144 older ones might be better, close any circuits pending on that
21145 new entry guard connection. This fix should make us recover much
21146 faster when our network is down and then comes back. Bugfix on
21147 0.1.2.8-beta; found by lodger.
21149 o Memory fixes and improvements:
21150 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
21151 to avoid unused RAM in buffer chunks and memory pools.
21152 - Speed up parsing and cut down on memory fragmentation by using
21153 stack-style allocations for parsing directory objects. Previously,
21154 this accounted for over 40% of allocations from within Tor's code
21155 on a typical directory cache.
21156 - Use a Bloom filter rather than a digest-based set to track which
21157 descriptors we need to keep around when we're cleaning out old
21158 router descriptors. This speeds up the computation significantly,
21159 and may reduce fragmentation.
21160 - Reduce the default smartlist size from 32 to 16; it turns out that
21161 most smartlists hold around 8-12 elements tops.
21162 - Make dumpstats() log the fullness and size of openssl-internal
21164 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
21165 patch to their OpenSSL, turn it on to save memory on servers. This
21166 patch will (with any luck) get included in a mainline distribution
21168 - Never use OpenSSL compression: it wastes RAM and CPU trying to
21169 compress cells, which are basically all encrypted, compressed,
21173 - Stop reloading the router list from disk for no reason when we
21174 run out of reachable directory mirrors. Once upon a time reloading
21175 it would set the 'is_running' flag back to 1 for them. It hasn't
21176 done that for a long time.
21177 - In very rare situations new hidden service descriptors were
21178 published earlier than 30 seconds after the last change to the
21179 service. (We currently think that a hidden service descriptor
21180 that's been stable for 30 seconds is worth publishing.)
21183 - Allow separate log levels to be configured for different logging
21184 domains. For example, this allows one to log all notices, warnings,
21185 or errors, plus all memory management messages of level debug or
21186 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
21187 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
21188 and stop using a warning that had become unfixably verbose under
21190 - New --hush command-line option similar to --quiet. While --quiet
21191 disables all logging to the console on startup, --hush limits the
21192 output to messages of warning and error severity.
21193 - Servers support a new URL scheme for consensus downloads that
21194 allows the client to specify which authorities are trusted.
21195 The server then only sends the consensus if the client will trust
21196 it. Otherwise a 404 error is sent back. Clients use this
21197 new scheme when the server supports it (meaning it's running
21198 0.2.1.1-alpha or later). Implements proposal 134.
21199 - New configure/torrc options (--enable-geoip-stats,
21200 DirRecordUsageByCountry) to record how many IPs we've served
21201 directory info to in each country code, how many status documents
21202 total we've sent to each country code, and what share of the total
21203 directory requests we should expect to see.
21204 - Use the TLS1 hostname extension to more closely resemble browser
21206 - Lots of new unit tests.
21207 - Add a macro to implement the common pattern of iterating through
21208 two parallel lists in lockstep.
21211 Changes in version 0.2.0.28-rc - 2008-06-13
21212 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
21213 performance bug, and fixes a bunch of smaller bugs.
21216 - Fix a bug where, when we were choosing the 'end stream reason' to
21217 put in our relay end cell that we send to the exit relay, Tor
21218 clients on Windows were sometimes sending the wrong 'reason'. The
21219 anonymity problem is that exit relays may be able to guess whether
21220 the client is running Windows, thus helping partition the anonymity
21221 set. Down the road we should stop sending reasons to exit relays,
21222 or otherwise prevent future versions of this bug.
21225 - While setting up a hidden service, some valid introduction circuits
21226 were overlooked and abandoned. This might be the reason for
21227 the long delay in making a hidden service available. Bugfix on
21231 - Update to the "June 9 2008" ip-to-country file.
21232 - Run 'make test' as part of 'make dist', so we stop releasing so
21233 many development snapshots that fail their unit tests.
21236 - When we're checking if we have enough dir info for each relay
21237 to begin establishing circuits, make sure that we actually have
21238 the descriptor listed in the consensus, not just any descriptor.
21240 - Bridge relays no longer print "xx=0" in their extrainfo document
21241 for every single country code in the geoip db. Bugfix on
21243 - Only warn when we fail to load the geoip file if we were planning to
21244 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
21245 - If we change our MaxAdvertisedBandwidth and then reload torrc,
21246 Tor won't realize it should publish a new relay descriptor. Fixes
21247 bug 688, reported by mfr. Bugfix on 0.1.2.x.
21248 - When we haven't had any application requests lately, don't bother
21249 logging that we have expired a bunch of descriptors. Bugfix
21251 - Make relay cells written on a connection count as non-padding when
21252 tracking how long a connection has been in use. Bugfix on
21253 0.2.0.1-alpha. Spotted by lodger.
21254 - Fix unit tests in 0.2.0.27-rc.
21255 - Fix compile on Windows.
21258 Changes in version 0.2.0.27-rc - 2008-06-03
21259 Tor 0.2.0.27-rc adds a few features we left out of the earlier
21260 release candidates. In particular, we now include an IP-to-country
21261 GeoIP database, so controllers can easily look up what country a
21262 given relay is in, and so bridge relays can give us some sanitized
21263 summaries about which countries are making use of bridges. (See proposal
21264 126-geoip-fetching.txt for details.)
21267 - Include an IP-to-country GeoIP file in the tarball, so bridge
21268 relays can report sanitized summaries of the usage they're seeing.
21271 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
21272 Robert Hogan. Fixes the first part of bug 681.
21273 - Make bridge authorities never serve extrainfo docs.
21274 - Add support to detect Libevent versions in the 1.4.x series
21276 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
21277 - Include a new contrib/tor-exit-notice.html file that exit relay
21278 operators can put on their website to help reduce abuse queries.
21281 - When tunneling an encrypted directory connection, and its first
21282 circuit fails, do not leave it unattached and ask the controller
21283 to deal. Fixes the second part of bug 681.
21284 - Make bridge authorities correctly expire old extrainfo documents
21288 Changes in version 0.2.0.26-rc - 2008-05-13
21289 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
21290 in Debian's OpenSSL packages. All users running any 0.2.0.x version
21291 should upgrade, whether they're running Debian or not.
21293 o Major security fixes:
21294 - Use new V3 directory authority keys on the tor26, gabelmoo, and
21295 moria1 V3 directory authorities. The old keys were generated with
21296 a vulnerable version of Debian's OpenSSL package, and must be
21297 considered compromised. Other authorities' keys were not generated
21298 with an affected version of OpenSSL.
21301 - List authority signatures as "unrecognized" based on DirServer
21302 lines, not on cert cache. Bugfix on 0.2.0.x.
21305 - Add a new V3AuthUseLegacyKey option to make it easier for
21306 authorities to change their identity keys if they have to.
21309 Changes in version 0.2.0.25-rc - 2008-04-23
21310 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
21313 - Remember to initialize threading before initializing logging.
21314 Otherwise, many BSD-family implementations will crash hard on
21315 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
21318 - Authorities correctly free policies on bad servers on
21319 exit. Fixes bug 672. Bugfix on 0.2.0.x.
21322 Changes in version 0.2.0.24-rc - 2008-04-22
21323 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
21324 v3 directory authority, makes relays with dynamic IP addresses and no
21325 DirPort notice more quickly when their IP address changes, fixes a few
21326 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
21328 o New directory authorities:
21329 - Take lefkada out of the list of v3 directory authorities, since
21330 it has been down for months.
21331 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
21335 - Detect address changes more quickly on non-directory mirror
21336 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
21338 o Minor features (security):
21339 - Reject requests for reverse-dns lookup of names that are in
21340 a private address space. Patch from lodger.
21341 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
21344 o Minor bugfixes (crashes):
21345 - Avoid a rare assert that can trigger when Tor doesn't have much
21346 directory information yet and it tries to fetch a v2 hidden
21347 service descriptor. Fixes bug 651, reported by nwf.
21348 - Initialize log mutex before initializing dmalloc. Otherwise,
21349 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
21350 - Use recursive pthread mutexes in order to avoid deadlock when
21351 logging debug-level messages to a controller. Bug spotted by nwf,
21352 bugfix on 0.2.0.16-alpha.
21354 o Minor bugfixes (resource management):
21355 - Keep address policies from leaking memory: start their refcount
21356 at 1, not 2. Bugfix on 0.2.0.16-alpha.
21357 - Free authority certificates on exit, so they don't look like memory
21358 leaks. Bugfix on 0.2.0.19-alpha.
21359 - Free static hashtables for policy maps and for TLS connections on
21360 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
21361 - Avoid allocating extra space when computing consensuses on 64-bit
21362 platforms. Bug spotted by aakova.
21364 o Minor bugfixes (misc):
21365 - Do not read the configuration file when we've only been told to
21366 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
21367 based on patch from Sebastian Hahn.
21368 - Exit relays that are used as a client can now reach themselves
21369 using the .exit notation, rather than just launching an infinite
21370 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
21371 - When attempting to open a logfile fails, tell us why.
21372 - Fix a dumb bug that was preventing us from knowing that we should
21373 preemptively build circuits to handle expected directory requests.
21374 Fixes bug 660. Bugfix on 0.1.2.x.
21375 - Warn less verbosely about clock skew from netinfo cells from
21376 untrusted sources. Fixes bug 663.
21377 - Make controller stream events for DNS requests more consistent,
21378 by adding "new stream" events for DNS requests, and removing
21379 spurious "stream closed" events" for cached reverse resolves.
21380 Patch from mwenge. Fixes bug 646.
21381 - Correctly notify one-hop connections when a circuit build has
21382 failed. Possible fix for bug 669. Found by lodger.
21385 Changes in version 0.2.0.23-rc - 2008-03-24
21386 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
21387 makes bootstrapping faster if the first directory mirror you contact
21388 is down. The bundles also include the new Vidalia 0.1.2 release.
21391 - When a tunneled directory request is made to a directory server
21392 that's down, notice after 30 seconds rather than 120 seconds. Also,
21393 fail any begindir streams that are pending on it, so they can
21394 retry elsewhere. This was causing multi-minute delays on bootstrap.
21397 Changes in version 0.2.0.22-rc - 2008-03-18
21398 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
21399 enables encrypted directory connections by default for non-relays, fixes
21400 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
21401 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
21404 - Enable encrypted directory connections by default for non-relays,
21405 so censor tools that block Tor directory connections based on their
21406 plaintext patterns will no longer work. This means Tor works in
21407 certain censored countries by default again.
21410 - Make sure servers always request certificates from clients during
21411 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
21412 - Do not enter a CPU-eating loop when a connection is closed in
21413 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
21414 diagnosed by lodger; bugfix on 0.2.0.20-rc.
21415 - Fix assertion failure that could occur when a blocked circuit
21416 became unblocked, and it had pending client DNS requests. Bugfix
21417 on 0.2.0.1-alpha. Fixes bug 632.
21419 o Minor bugfixes (on 0.1.2.x):
21420 - Generate "STATUS_SERVER" events rather than misspelled
21421 "STATUS_SEVER" events. Caught by mwenge.
21422 - When counting the number of bytes written on a TLS connection,
21423 look at the BIO actually used for writing to the network, not
21424 at the BIO used (sometimes) to buffer data for the network.
21425 Looking at different BIOs could result in write counts on the
21426 order of ULONG_MAX. Fixes bug 614.
21427 - On Windows, correctly detect errors when listing the contents of
21428 a directory. Fix from lodger.
21430 o Minor bugfixes (on 0.2.0.x):
21431 - Downgrade "sslv3 alert handshake failure" message to INFO.
21432 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
21433 left BandwidthRate and BandwidthBurst at the default, we would be
21434 silently limited by those defaults. Now raise them to match the
21435 RelayBandwidth* values.
21436 - Fix the SVK version detection logic to work correctly on a branch.
21437 - Make --enable-openbsd-malloc work correctly on Linux with alpha
21438 CPUs. Fixes bug 625.
21439 - Logging functions now check that the passed severity is sane.
21440 - Use proper log levels in the testsuite call of
21441 get_interface_address6().
21442 - When using a nonstandard malloc, do not use the platform values for
21443 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
21444 - Make the openbsd malloc code use 8k pages on alpha CPUs and
21446 - Detect mismatched page sizes when using --enable-openbsd-malloc.
21447 - Avoid double-marked-for-close warning when certain kinds of invalid
21448 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
21449 for bug 617. Bugfix on 0.2.0.1-alpha.
21450 - Make sure that the "NULL-means-reject *:*" convention is followed by
21451 all the policy manipulation functions, avoiding some possible crash
21452 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
21453 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
21454 actually works, and doesn't warn about every single reverse lookup.
21455 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
21458 - Only log guard node status when guard node status has changed.
21459 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
21460 make "INFO" 75% less verbose.
21463 Changes in version 0.2.0.21-rc - 2008-03-02
21464 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
21465 makes Tor work well with Vidalia again, fixes a rare assert bug,
21466 and fixes a pair of more minor bugs. The bundles also include Vidalia
21467 0.1.0 and Torbutton 1.1.16.
21470 - The control port should declare that it requires password auth
21471 when HashedControlSessionPassword is set too. Patch from Matt Edman;
21472 bugfix on 0.2.0.20-rc. Fixes bug 615.
21473 - Downgrade assert in connection_buckets_decrement() to a log message.
21474 This may help us solve bug 614, and in any case will make its
21475 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
21476 - We were sometimes miscounting the number of bytes read from the
21477 network, causing our rate limiting to not be followed exactly.
21478 Bugfix on 0.2.0.16-alpha. Reported by lodger.
21481 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
21482 OpenSSL versions should have been working fine. Diagnosis and patch
21483 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
21484 Bugfix on 0.2.0.20-rc.
21487 Changes in version 0.2.0.20-rc - 2008-02-24
21488 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
21489 makes more progress towards normalizing Tor's TLS handshake, makes
21490 hidden services work better again, helps relays bootstrap if they don't
21491 know their IP address, adds optional support for linking in openbsd's
21492 allocator or tcmalloc, allows really fast relays to scale past 15000
21493 sockets, and fixes a bunch of minor bugs reported by Veracode.
21496 - Enable the revised TLS handshake based on the one designed by
21497 Steven Murdoch in proposal 124, as revised in proposal 130. It
21498 includes version negotiation for OR connections as described in
21499 proposal 105. The new handshake is meant to be harder for censors
21500 to fingerprint, and it adds the ability to detect certain kinds of
21501 man-in-the-middle traffic analysis attacks. The version negotiation
21502 feature will allow us to improve Tor's link protocol more safely
21504 - Choose which bridge to use proportional to its advertised bandwidth,
21505 rather than uniformly at random. This should speed up Tor for
21506 bridge users. Also do this for people who set StrictEntryNodes.
21507 - When a TrackHostExits-chosen exit fails too many times in a row,
21508 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
21511 - Resolved problems with (re-)fetching hidden service descriptors.
21512 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
21513 and 0.2.0.19-alpha.
21514 - If we only ever used Tor for hidden service lookups or posts, we
21515 would stop building circuits and start refusing connections after
21516 24 hours, since we falsely believed that Tor was dormant. Reported
21517 by nwf; bugfix on 0.1.2.x.
21518 - Servers that don't know their own IP address should go to the
21519 authorities for their first directory fetch, even if their DirPort
21520 is off or if they don't know they're reachable yet. This will help
21521 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
21522 - When counting the number of open sockets, count not only the number
21523 of sockets we have received from the socket() call, but also
21524 the number we've gotten from accept() and socketpair(). This bug
21525 made us fail to count all sockets that we were using for incoming
21526 connections. Bugfix on 0.2.0.x.
21527 - Fix code used to find strings within buffers, when those strings
21528 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
21529 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
21530 - Add a new __HashedControlSessionPassword option for controllers
21531 to use for one-off session password hashes that shouldn't get
21532 saved to disk by SAVECONF --- Vidalia users were accumulating a
21533 pile of HashedControlPassword lines in their torrc files, one for
21534 each time they had restarted Tor and then clicked Save. Make Tor
21535 automatically convert "HashedControlPassword" to this new option but
21536 only when it's given on the command line. Partial fix for bug 586.
21538 o Minor features (performance):
21539 - Tune parameters for cell pool allocation to minimize amount of
21541 - Add OpenBSD malloc code from phk as an optional malloc
21542 replacement on Linux: some glibc libraries do very poorly
21543 with Tor's memory allocation patterns. Pass
21544 --enable-openbsd-malloc to get the replacement malloc code.
21545 - Add a --with-tcmalloc option to the configure script to link
21546 against tcmalloc (if present). Does not yet search for
21547 non-system include paths.
21548 - Stop imposing an arbitrary maximum on the number of file descriptors
21549 used for busy servers. Bug reported by Olaf Selke; patch from
21552 o Minor features (other):
21553 - When SafeLogging is disabled, log addresses along with all TLS
21555 - When building with --enable-gcc-warnings, check for whether Apple's
21556 warning "-Wshorten-64-to-32" is available.
21557 - Add a --passphrase-fd argument to the tor-gencert command for
21560 o Minor bugfixes (memory leaks and code problems):
21561 - We were leaking a file descriptor if Tor started with a zero-length
21562 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
21563 - Detect size overflow in zlib code. Reported by Justin Ferguson and
21565 - We were comparing the raw BridgePassword entry with a base64'ed
21566 version of it, when handling a "/tor/networkstatus-bridges"
21567 directory request. Now compare correctly. Noticed by Veracode.
21568 - Recover from bad tracked-since value in MTBF-history file.
21569 Should fix bug 537.
21570 - Alter the code that tries to recover from unhandled write
21571 errors, to not try to flush onto a socket that's given us
21572 unhandled errors. Bugfix on 0.1.2.x.
21573 - Make Unix controlsockets work correctly on OpenBSD. Patch from
21574 tup. Bugfix on 0.2.0.3-alpha.
21576 o Minor bugfixes (other):
21577 - If we have an extra-info document for our server, always make
21578 it available on the control port, even if we haven't gotten
21579 a copy of it from an authority yet. Patch from mwenge.
21580 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
21581 - Directory mirrors no longer include a guess at the client's IP
21582 address if the connection appears to be coming from the same /24
21583 network; it was producing too many wrong guesses.
21584 - Make the new hidden service code respect the SafeLogging setting.
21585 Bugfix on 0.2.0.x. Patch from Karsten.
21586 - When starting as an authority, do not overwrite all certificates
21587 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
21588 - If we're trying to flush the last bytes on a connection (for
21589 example, when answering a directory request), reset the
21590 time-to-give-up timeout every time we manage to write something
21591 on the socket. Bugfix on 0.1.2.x.
21592 - Change the behavior of "getinfo status/good-server-descriptor"
21593 so it doesn't return failure when any authority disappears.
21594 - Even though the man page said that "TrackHostExits ." should
21595 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
21596 - Report TLS "zero return" case as a "clean close" and "IO error"
21597 as a "close". Stop calling closes "unexpected closes": existing
21598 Tors don't use SSL_close(), so having a connection close without
21599 the TLS shutdown handshake is hardly unexpected.
21600 - Send NAMESERVER_STATUS messages for a single failed nameserver
21603 o Code simplifications and refactoring:
21604 - Remove the tor_strpartition function: its logic was confused,
21605 and it was only used for one thing that could be implemented far
21609 Changes in version 0.2.0.19-alpha - 2008-02-09
21610 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
21611 handshake, makes path selection for relays more secure and IP address
21612 guessing more robust, and generally fixes a lot of bugs in preparation
21613 for calling the 0.2.0 branch stable.
21616 - Do not include recognizeable strings in the commonname part of
21617 Tor's x509 certificates.
21620 - If we're a relay, avoid picking ourselves as an introduction point,
21621 a rendezvous point, or as the final hop for internal circuits. Bug
21622 reported by taranis and lodger. Bugfix on 0.1.2.x.
21623 - Patch from "Andrew S. Lists" to catch when we contact a directory
21624 mirror at IP address X and he says we look like we're coming from
21625 IP address X. Bugfix on 0.1.2.x.
21627 o Minor features (security):
21628 - Be more paranoid about overwriting sensitive memory on free(),
21629 as a defensive programming tactic to ensure forward secrecy.
21631 o Minor features (directory authority):
21632 - Actually validate the options passed to AuthDirReject,
21633 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
21634 - Reject router descriptors with out-of-range bandwidthcapacity or
21635 bandwidthburst values.
21637 o Minor features (controller):
21638 - Reject controller commands over 1MB in length. This keeps rogue
21639 processes from running us out of memory.
21641 o Minor features (misc):
21642 - Give more descriptive well-formedness errors for out-of-range
21643 hidden service descriptor/protocol versions.
21644 - Make memory debugging information describe more about history
21645 of cell allocation, so we can help reduce our memory use.
21647 o Deprecated features (controller):
21648 - The status/version/num-versioning and status/version/num-concurring
21649 GETINFO options are no longer useful in the v3 directory protocol:
21650 treat them as deprecated, and warn when they're used.
21653 - When our consensus networkstatus has been expired for a while, stop
21654 being willing to build circuits using it. Fixes bug 401. Bugfix
21656 - Directory caches now fetch certificates from all authorities
21657 listed in a networkstatus consensus, even when they do not
21658 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
21659 - When connecting to a bridge without specifying its key, insert
21660 the connection into the identity-to-connection map as soon as
21661 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
21662 - Detect versions of OS X where malloc_good_size() is present in the
21663 library but never actually declared. Resolves bug 587. Bugfix
21665 - Stop incorrectly truncating zlib responses to directory authority
21666 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
21667 - Stop recommending that every server operator send mail to tor-ops.
21668 Resolves bug 597. Bugfix on 0.1.2.x.
21669 - Don't trigger an assert if we start a directory authority with a
21670 private IP address (like 127.0.0.1).
21671 - Avoid possible failures when generating a directory with routers
21672 with over-long versions strings, or too many flags set. Bugfix
21674 - If an attempt to launch a DNS resolve request over the control
21675 port fails because we have overrun the limit on the number of
21676 connections, tell the controller that the request has failed.
21677 - Avoid using too little bandwidth when our clock skips a few
21678 seconds. Bugfix on 0.1.2.x.
21679 - Fix shell error when warning about missing packages in configure
21680 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
21681 - Do not become confused when receiving a spurious VERSIONS-like
21682 cell from a confused v1 client. Bugfix on 0.2.0.x.
21683 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
21684 introduction points for a hidden service have failed. Patch from
21685 Karsten Loesing. Bugfix on 0.2.0.x.
21687 o Code simplifications and refactoring:
21688 - Remove some needless generality from cpuworker code, for improved
21690 - Stop overloading the circuit_t.onionskin field for both "onionskin
21691 from a CREATE cell that we are waiting for a cpuworker to be
21692 assigned" and "onionskin from an EXTEND cell that we are going to
21693 send to an OR as soon as we are connected". Might help with bug 600.
21694 - Add an in-place version of aes_crypt() so that we can avoid doing a
21695 needless memcpy() call on each cell payload.
21698 Changes in version 0.2.0.18-alpha - 2008-01-25
21699 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
21700 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
21701 that can warn or reject connections to ports generally associated with
21702 vulnerable-plaintext protocols.
21704 o New directory authorities:
21705 - Set up dannenberg (run by CCC) as the sixth v3 directory
21709 - Fix a major memory leak when attempting to use the v2 TLS
21710 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
21711 - We accidentally enabled the under-development v2 TLS handshake
21712 code, which was causing log entries like "TLS error while
21713 renegotiating handshake". Disable it again. Resolves bug 590.
21714 - We were computing the wrong Content-Length: header for directory
21715 responses that need to be compressed on the fly, causing clients
21716 asking for those items to always fail. Bugfix on 0.2.0.x; partially
21720 - Avoid going directly to the directory authorities even if you're a
21721 relay, if you haven't found yourself reachable yet or if you've
21722 decided not to advertise your dirport yet. Addresses bug 556.
21723 - If we've gone 12 hours since our last bandwidth check, and we
21724 estimate we have less than 50KB bandwidth capacity but we could
21725 handle more, do another bandwidth test.
21726 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
21727 Tor can warn and/or refuse connections to ports commonly used with
21728 vulnerable-plaintext protocols. Currently we warn on ports 23,
21729 109, 110, and 143, but we don't reject any.
21732 - When we setconf ClientOnly to 1, close any current OR and Dir
21733 listeners. Reported by mwenge.
21734 - When we get a consensus that's been signed by more people than
21735 we expect, don't log about it; it's not a big deal. Reported
21739 - Don't answer "/tor/networkstatus-bridges" directory requests if
21740 the request isn't encrypted.
21741 - Make "ClientOnly 1" config option disable directory ports too.
21742 - Patches from Karsten Loesing to make v2 hidden services more
21743 robust: work even when there aren't enough HSDir relays available;
21744 retry when a v2 rend desc fetch fails; but don't retry if we
21745 already have a usable v0 rend desc.
21748 Changes in version 0.2.0.17-alpha - 2008-01-17
21749 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
21752 - Make the tor-gencert man page get included correctly in the tarball.
21755 Changes in version 0.2.0.16-alpha - 2008-01-17
21756 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
21757 Loesing, and generally cleans up a lot of features and minor bugs.
21759 o New directory authorities:
21760 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
21763 o Major performance improvements:
21764 - Switch our old ring buffer implementation for one more like that
21765 used by free Unix kernels. The wasted space in a buffer with 1mb
21766 of data will now be more like 8k than 1mb. The new implementation
21767 also avoids realloc();realloc(); patterns that can contribute to
21768 memory fragmentation.
21771 - Configuration files now accept C-style strings as values. This
21772 helps encode characters not allowed in the current configuration
21773 file format, such as newline or #. Addresses bug 557.
21774 - Although we fixed bug 539 (where servers would send HTTP status 503
21775 responses _and_ send a body too), there are still servers out
21776 there that haven't upgraded. Therefore, make clients parse such
21777 bodies when they receive them.
21778 - When we're not serving v2 directory information, there is no reason
21779 to actually keep any around. Remove the obsolete files and directory
21780 on startup if they are very old and we aren't going to serve them.
21782 o Minor performance improvements:
21783 - Reference-count and share copies of address policy entries; only 5%
21784 of them were actually distinct.
21785 - Never walk through the list of logs if we know that no log is
21786 interested in a given message.
21789 - When an authority has not signed a consensus, do not try to
21790 download a nonexistent "certificate with key 00000000". Bugfix
21791 on 0.2.0.x. Fixes bug 569.
21792 - Fix a rare assert error when we're closing one of our threads:
21793 use a mutex to protect the list of logs, so we never write to the
21794 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
21795 bug 575, which is kind of the revenge of bug 222.
21796 - Patch from Karsten Loesing to complain less at both the client
21797 and the relay when a relay used to have the HSDir flag but doesn't
21798 anymore, and we try to upload a hidden service descriptor.
21799 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
21801 - Do not try to download missing certificates until we have tried
21802 to check our fallback consensus. Fixes bug 583.
21803 - Make bridges round reported GeoIP stats info up to the nearest
21804 estimate, not down. Now we can distinguish between "0 people from
21805 this country" and "1 person from this country".
21806 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
21807 - Avoid possible segfault if key generation fails in
21808 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
21809 - Avoid segfault in the case where a badly behaved v2 versioning
21810 directory sends a signed networkstatus with missing client-versions.
21812 - Avoid segfaults on certain complex invocations of
21813 router_get_by_hexdigest(). Bugfix on 0.1.2.
21814 - Correct bad index on array access in parse_http_time(). Bugfix
21816 - Fix possible bug in vote generation when server versions are present
21817 but client versions are not.
21818 - Fix rare bug on REDIRECTSTREAM control command when called with no
21819 port set: it could erroneously report an error when none had
21821 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
21822 compressing large objects and find ourselves with more than 4k
21823 left over. Bugfix on 0.2.0.
21824 - Fix a small memory leak when setting up a hidden service.
21825 - Fix a few memory leaks that could in theory happen under bizarre
21827 - Fix an assert if we post a general-purpose descriptor via the
21828 control port but that descriptor isn't mentioned in our current
21829 network consensus. Bug reported by Jon McLachlan; bugfix on
21832 o Minor features (controller):
21833 - Get NS events working again. Patch from tup.
21834 - The GETCONF command now escapes and quotes configuration values
21835 that don't otherwise fit into the torrc file.
21836 - The SETCONF command now handles quoted values correctly.
21838 o Minor features (directory authorities):
21839 - New configuration options to override default maximum number of
21840 servers allowed on a single IP address. This is important for
21841 running a test network on a single host.
21842 - Actually implement the -s option to tor-gencert.
21843 - Add a manual page for tor-gencert.
21845 o Minor features (bridges):
21846 - Bridge authorities no longer serve bridge descriptors over
21847 unencrypted connections.
21849 o Minor features (other):
21850 - Add hidden services and DNSPorts to the list of things that make
21851 Tor accept that it has running ports. Change starting Tor with no
21852 ports from a fatal error to a warning; we might change it back if
21853 this turns out to confuse anybody. Fixes bug 579.
21856 Changes in version 0.1.2.19 - 2008-01-17
21857 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
21858 exit policy a little bit more conservative so it's safer to run an
21859 exit relay on a home system, and fixes a variety of smaller issues.
21862 - Exit policies now reject connections that are addressed to a
21863 relay's public (external) IP address too, unless
21864 ExitPolicyRejectPrivate is turned off. We do this because too
21865 many relays are running nearby to services that trust them based
21866 on network address.
21869 - When the clock jumps forward a lot, do not allow the bandwidth
21870 buckets to become negative. Fixes bug 544.
21871 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
21872 on every successful resolve. Reported by Mike Perry.
21873 - Purge old entries from the "rephist" database and the hidden
21874 service descriptor database even when DirPort is zero.
21875 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
21876 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
21877 crashing or mis-answering these requests.
21878 - When we decide to send a 503 response to a request for servers, do
21879 not then also send the server descriptors: this defeats the whole
21880 purpose. Fixes bug 539.
21883 - Changing the ExitPolicyRejectPrivate setting should cause us to
21884 rebuild our server descriptor.
21885 - Fix handling of hex nicknames when answering controller requests for
21886 networkstatus by name, or when deciding whether to warn about
21887 unknown routers in a config option. (Patch from mwenge.)
21888 - Fix a couple of hard-to-trigger autoconf problems that could result
21889 in really weird results on platforms whose sys/types.h files define
21890 nonstandard integer types.
21891 - Don't try to create the datadir when running --verify-config or
21892 --hash-password. Resolves bug 540.
21893 - If we were having problems getting a particular descriptor from the
21894 directory caches, and then we learned about a new descriptor for
21895 that router, we weren't resetting our failure count. Reported
21897 - Although we fixed bug 539 (where servers would send HTTP status 503
21898 responses _and_ send a body too), there are still servers out there
21899 that haven't upgraded. Therefore, make clients parse such bodies
21900 when they receive them.
21901 - Run correctly on systems where rlim_t is larger than unsigned long.
21902 This includes some 64-bit systems.
21903 - Run correctly on platforms (like some versions of OS X 10.5) where
21904 the real limit for number of open files is OPEN_FILES, not rlim_max
21905 from getrlimit(RLIMIT_NOFILES).
21906 - Avoid a spurious free on base64 failure.
21907 - Avoid segfaults on certain complex invocations of
21908 router_get_by_hexdigest().
21909 - Fix rare bug on REDIRECTSTREAM control command when called with no
21910 port set: it could erroneously report an error when none had
21914 Changes in version 0.2.0.15-alpha - 2007-12-25
21915 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
21916 features added in 0.2.0.13-alpha.
21919 - Fix several remotely triggerable asserts based on DirPort requests
21920 for a v2 or v3 networkstatus object before we were prepared. This
21921 was particularly bad for 0.2.0.13 and later bridge relays, who
21922 would never have a v2 networkstatus and would thus always crash
21923 when used. Bugfixes on 0.2.0.x.
21924 - Estimate the v3 networkstatus size more accurately, rather than
21925 estimating it at zero bytes and giving it artificially high priority
21926 compared to other directory requests. Bugfix on 0.2.0.x.
21929 - Fix configure.in logic for cross-compilation.
21930 - When we load a bridge descriptor from the cache, and it was
21931 previously unreachable, mark it as retriable so we won't just
21932 ignore it. Also, try fetching a new copy immediately. Bugfixes
21934 - The bridge GeoIP stats were counting other relays, for example
21935 self-reachability and authority-reachability tests.
21938 - Support compilation to target iPhone; patch from cjacker huang.
21939 To build for iPhone, pass the --enable-iphone option to configure.
21942 Changes in version 0.2.0.14-alpha - 2007-12-23
21944 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
21945 without a datadirectory from a previous Tor install. Reported
21947 - Fix a crash when we fetch a descriptor that turns out to be
21948 unexpected (it used to be in our networkstatus when we started
21949 fetching it, but it isn't in our current networkstatus), and we
21950 aren't using bridges. Bugfix on 0.2.0.x.
21951 - Fix a crash when accessing hidden services: it would work the first
21952 time you use a given introduction point for your service, but
21953 on subsequent requests we'd be using garbage memory. Fixed by
21954 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
21955 - Fix a crash when we load a bridge descriptor from disk but we don't
21956 currently have a Bridge line for it in our torrc. Bugfix on
21960 - If bridge authorities set BridgePassword, they will serve a
21961 snapshot of known bridge routerstatuses from their DirPort to
21962 anybody who knows that password. Unset by default.
21965 - Make the unit tests build again.
21966 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
21967 - Make PublishServerDescriptor default to 1, so the default doesn't
21968 have to change as we invent new directory protocol versions.
21969 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
21970 be included unless sys/time.h is already included. Fixes
21971 bug 553. Bugfix on 0.2.0.x.
21972 - If we receive a general-purpose descriptor and then receive an
21973 identical bridge-purpose descriptor soon after, don't discard
21974 the next one as a duplicate.
21977 - If BridgeRelay is set to 1, then the default for
21978 PublishServerDescriptor is now "bridge" rather than "v2,v3".
21979 - If the user sets RelayBandwidthRate but doesn't set
21980 RelayBandwidthBurst, then make them equal rather than erroring out.
21983 Changes in version 0.2.0.13-alpha - 2007-12-21
21984 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
21985 Goodell, fixes many more bugs, and adds a lot of infrastructure for
21988 o New directory authorities:
21989 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
21993 - Only update guard status (usable / not usable) once we have
21994 enough directory information. This was causing us to always pick
21995 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
21996 causing us to discard all our guards on startup if we hadn't been
21997 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
21998 - Purge old entries from the "rephist" database and the hidden
21999 service descriptor databases even when DirPort is zero. Bugfix
22001 - We were ignoring our RelayBandwidthRate for the first 30 seconds
22002 after opening a circuit -- even a relayed circuit. Bugfix on
22004 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22005 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22006 crashing or mis-answering these types of requests.
22007 - Relays were publishing their server descriptor to v1 and v2
22008 directory authorities, but they didn't try publishing to v3-only
22009 authorities. Fix this; and also stop publishing to v1 authorities.
22011 - When we were reading router descriptors from cache, we were ignoring
22012 the annotations -- so for example we were reading in bridge-purpose
22013 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
22014 - When we decided to send a 503 response to a request for servers, we
22015 were then also sending the server descriptors: this defeats the
22016 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
22019 - Bridge relays now behave like clients with respect to time
22020 intervals for downloading new consensus documents -- otherwise they
22021 stand out. Bridge users now wait until the end of the interval,
22022 so their bridge relay will be sure to have a new consensus document.
22023 - Three new config options (AlternateDirAuthority,
22024 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
22025 user selectively replace the default directory authorities by type,
22026 rather than the all-or-nothing replacement that DirServer offers.
22027 - Tor can now be configured to read a GeoIP file from disk in one
22028 of two formats. This can be used by controllers to map IP addresses
22029 to countries. Eventually, it may support exit-by-country.
22030 - When possible, bridge relays remember which countries users
22031 are coming from, and report aggregate information in their
22032 extra-info documents, so that the bridge authorities can learn
22033 where Tor is blocked.
22034 - Bridge directory authorities now do reachability testing on the
22035 bridges they know. They provide router status summaries to the
22036 controller via "getinfo ns/purpose/bridge", and also dump summaries
22037 to a file periodically.
22038 - Stop fetching directory info so aggressively if your DirPort is
22039 on but your ORPort is off; stop fetching v2 dir info entirely.
22040 You can override these choices with the new FetchDirInfoEarly
22044 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
22045 consensus documents when there are too many relays at a single
22046 IP address. Now clear it in v2 network status documents too, and
22047 also clear it in routerinfo_t when the relay is no longer listed
22048 in the relevant networkstatus document.
22049 - Don't crash if we get an unexpected value for the
22050 PublishServerDescriptor config option. Reported by Matt Edman;
22051 bugfix on 0.2.0.9-alpha.
22052 - Our new v2 hidden service descriptor format allows descriptors
22053 that have no introduction points. But Tor crashed when we tried
22054 to build a descriptor with no intro points (and it would have
22055 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
22056 by Karsten Loesing.
22057 - Fix building with dmalloc 5.5.2 with glibc.
22058 - Reject uploaded descriptors and extrainfo documents if they're
22059 huge. Otherwise we'll cache them all over the network and it'll
22060 clog everything up. Reported by Aljosha Judmayer.
22061 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
22062 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
22063 - When the DANGEROUS_VERSION controller status event told us we're
22064 running an obsolete version, it used the string "OLD" to describe
22065 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
22066 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
22067 - If we can't expand our list of entry guards (e.g. because we're
22068 using bridges or we have StrictEntryNodes set), don't mark relays
22069 down when they fail a directory request. Otherwise we're too quick
22070 to mark all our entry points down. Bugfix on 0.1.2.x.
22071 - Fix handling of hex nicknames when answering controller requests for
22072 networkstatus by name, or when deciding whether to warn about unknown
22073 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
22074 - Fix a couple of hard-to-trigger autoconf problems that could result
22075 in really weird results on platforms whose sys/types.h files define
22076 nonstandard integer types. Bugfix on 0.1.2.x.
22077 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
22078 - Don't crash on name lookup when we have no current consensus. Fixes
22079 bug 538; bugfix on 0.2.0.x.
22080 - Only Tors that want to mirror the v2 directory info should
22081 create the "cached-status" directory in their datadir. (All Tors
22082 used to create it.) Bugfix on 0.2.0.9-alpha.
22083 - Directory authorities should only automatically download Extra Info
22084 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
22087 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
22088 consumers. (We already do this on HUP.)
22089 - Authorities and caches fetch the v2 networkstatus documents
22090 less often, now that v3 is encouraged.
22091 - Add a new config option BridgeRelay that specifies you want to
22092 be a bridge relay. Right now the only difference is that it makes
22093 you answer begin_dir requests, and it makes you cache dir info,
22094 even if your DirPort isn't on.
22095 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
22096 ask about source, timestamp of arrival, purpose, etc. We need
22097 something like this to help Vidalia not do GeoIP lookups on bridge
22099 - Allow multiple HashedControlPassword config lines, to support
22100 multiple controller passwords.
22101 - Authorities now decide whether they're authoritative for a given
22102 router based on the router's purpose.
22103 - New config options AuthDirBadDir and AuthDirListBadDirs for
22104 authorities to mark certain relays as "bad directories" in the
22105 networkstatus documents. Also supports the "!baddir" directive in
22106 the approved-routers file.
22109 Changes in version 0.2.0.12-alpha - 2007-11-16
22110 This twelfth development snapshot fixes some more build problems as
22111 well as a few minor bugs.
22114 - Make it build on OpenBSD again. Patch from tup.
22115 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
22116 package-building for Red Hat, OS X, etc.
22118 o Minor bugfixes (on 0.1.2.x):
22119 - Changing the ExitPolicyRejectPrivate setting should cause us to
22120 rebuild our server descriptor.
22122 o Minor bugfixes (on 0.2.0.x):
22123 - When we're lacking a consensus, don't try to perform rendezvous
22124 operations. Reported by Karsten Loesing.
22125 - Fix a small memory leak whenever we decide against using a
22126 newly picked entry guard. Reported by Mike Perry.
22127 - When authorities detected more than two relays running on the same
22128 IP address, they were clearing all the status flags but forgetting
22129 to clear the "hsdir" flag. So clients were being told that a
22130 given relay was the right choice for a v2 hsdir lookup, yet they
22131 never had its descriptor because it was marked as 'not running'
22133 - If we're trying to fetch a bridge descriptor and there's no way
22134 the bridge authority could help us (for example, we don't know
22135 a digest, or there is no bridge authority), don't be so eager to
22136 fall back to asking the bridge authority.
22137 - If we're using bridges or have strictentrynodes set, and our
22138 chosen exit is in the same family as all our bridges/entry guards,
22139 then be flexible about families.
22142 - When we negotiate a v2 link-layer connection (not yet implemented),
22143 accept RELAY_EARLY cells and turn them into RELAY cells if we've
22144 negotiated a v1 connection for their next step. Initial code for
22148 Changes in version 0.2.0.11-alpha - 2007-11-12
22149 This eleventh development snapshot fixes some build problems with
22150 the previous snapshot. It also includes a more secure-by-default exit
22151 policy for relays, fixes an enormous memory leak for exit relays, and
22152 fixes another bug where servers were falling out of the directory list.
22155 - Exit policies now reject connections that are addressed to a
22156 relay's public (external) IP address too, unless
22157 ExitPolicyRejectPrivate is turned off. We do this because too
22158 many relays are running nearby to services that trust them based
22159 on network address. Bugfix on 0.1.2.x.
22162 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22163 on every successful resolve. Reported by Mike Perry; bugfix
22165 - On authorities, never downgrade to old router descriptors simply
22166 because they're listed in the consensus. This created a catch-22
22167 where we wouldn't list a new descriptor because there was an
22168 old one in the consensus, and we couldn't get the new one in the
22169 consensus because we wouldn't list it. Possible fix for bug 548.
22170 Also, this might cause bug 543 to appear on authorities; if so,
22171 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
22173 o Packaging fixes on 0.2.0.10-alpha:
22174 - We were including instructions about what to do with the
22175 src/config/fallback-consensus file, but we weren't actually
22176 including it in the tarball. Disable all of that for now.
22179 - Allow people to say PreferTunnelledDirConns rather than
22180 PreferTunneledDirConns, for those alternate-spellers out there.
22183 - Don't reevaluate all the information from our consensus document
22184 just because we've downloaded a v2 networkstatus that we intend
22185 to cache. Fixes bug 545; bugfix on 0.2.0.x.
22188 Changes in version 0.2.0.10-alpha - 2007-11-10
22189 This tenth development snapshot adds a third v3 directory authority
22190 run by Mike Perry, adds most of Karsten Loesing's new hidden service
22191 descriptor format, fixes a bad crash bug and new bridge bugs introduced
22192 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
22193 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
22194 addresses many more minor issues.
22196 o New directory authorities:
22197 - Set up ides (run by Mike Perry) as the third v3 directory authority.
22200 - Allow tunnelled directory connections to ask for an encrypted
22201 "begin_dir" connection or an anonymized "uses a full Tor circuit"
22202 connection independently. Now we can make anonymized begin_dir
22203 connections for (e.g.) more secure hidden service posting and
22205 - More progress on proposal 114: code from Karsten Loesing to
22206 implement new hidden service descriptor format.
22207 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
22208 accommodate the growing number of servers that use the default
22209 and are reaching it.
22210 - Directory authorities use a new formula for selecting which nodes
22211 to advertise as Guards: they must be in the top 7/8 in terms of
22212 how long we have known about them, and above the median of those
22213 nodes in terms of weighted fractional uptime.
22214 - Make "not enough dir info yet" warnings describe *why* Tor feels
22215 it doesn't have enough directory info yet.
22218 - Stop servers from crashing if they set a Family option (or
22219 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
22221 - Make bridge users work again -- the move to v3 directories in
22222 0.2.0.9-alpha had introduced a number of bugs that made bridges
22223 no longer work for clients.
22224 - When the clock jumps forward a lot, do not allow the bandwidth
22225 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
22227 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
22228 - When the consensus lists a router descriptor that we previously were
22229 mirroring, but that we considered non-canonical, reload the
22230 descriptor as canonical. This fixes bug 543 where Tor servers
22231 would start complaining after a few days that they don't have
22232 enough directory information to build a circuit.
22233 - Consider replacing the current consensus when certificates arrive
22234 that make the pending consensus valid. Previously, we were only
22235 considering replacement when the new certs _didn't_ help.
22236 - Fix an assert error on startup if we didn't already have the
22237 consensus and certs cached in our datadirectory: we were caching
22238 the consensus in consensus_waiting_for_certs but then free'ing it
22240 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
22241 Request) if we need more v3 certs but we've already got pending
22242 requests for all of them.
22243 - Correctly back off from failing certificate downloads. Fixes
22245 - Authorities don't vote on the Running flag if they have been running
22246 for less than 30 minutes themselves. Fixes bug 547, where a newly
22247 started authority would vote that everyone was down.
22249 o New requirements:
22250 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
22251 it, it had no AES, and it hasn't seen any security patches since
22255 - Clients now hold circuitless TLS connections open for 1.5 times
22256 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
22257 rebuild a new circuit over them within that timeframe. Previously,
22258 they held them open only for KeepalivePeriod (5 minutes).
22259 - Use "If-Modified-Since" to avoid retrieving consensus
22260 networkstatuses that we already have.
22261 - When we have no consensus, check FallbackNetworkstatusFile (defaults
22262 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
22263 we start knowing some directory caches.
22264 - When we receive a consensus from the future, warn about skew.
22265 - Improve skew reporting: try to give the user a better log message
22266 about how skewed they are, and how much this matters.
22267 - When we have a certificate for an authority, believe that
22268 certificate's claims about the authority's IP address.
22269 - New --quiet command-line option to suppress the default console log.
22270 Good in combination with --hash-password.
22271 - Authorities send back an X-Descriptor-Not-New header in response to
22272 an accepted-but-discarded descriptor upload. Partially implements
22274 - Make the log message for "tls error. breaking." more useful.
22275 - Better log messages about certificate downloads, to attempt to
22276 track down the second incarnation of bug 546.
22278 o Minor features (bridges):
22279 - If bridge users set UpdateBridgesFromAuthority, but the digest
22280 they ask for is a 404 from the bridge authority, they now fall
22281 back to trying the bridge directly.
22282 - Bridges now use begin_dir to publish their server descriptor to
22283 the bridge authority, even when they haven't set TunnelDirConns.
22285 o Minor features (controller):
22286 - When reporting clock skew, and we know that the clock is _at least
22287 as skewed_ as some value, but we don't know the actual value,
22288 report the value as a "minimum skew."
22291 - Update linux-tor-prio.sh script to allow QoS based on the uid of
22292 the Tor process. Patch from Marco Bonetti with tweaks from Mike
22296 - Refuse to start if both ORPort and UseBridges are set. Bugfix
22297 on 0.2.0.x, suggested by Matt Edman.
22298 - Don't stop fetching descriptors when FetchUselessDescriptors is
22299 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
22300 reported by tup and ioerror.
22301 - Better log message on vote from unknown authority.
22302 - Don't log "Launching 0 request for 0 router" message.
22304 o Minor bugfixes (memory leaks):
22305 - Stop leaking memory every time we parse a v3 certificate. Bugfix
22307 - Stop leaking memory every time we load a v3 certificate. Bugfix
22308 on 0.2.0.1-alpha. Fixes bug 536.
22309 - Stop leaking a cached networkstatus on exit. Bugfix on
22311 - Stop leaking voter information every time we free a consensus.
22312 Bugfix on 0.2.0.3-alpha.
22313 - Stop leaking signed data every time we check a voter signature.
22314 Bugfix on 0.2.0.3-alpha.
22315 - Stop leaking a signature every time we fail to parse a consensus or
22316 a vote. Bugfix on 0.2.0.3-alpha.
22317 - Stop leaking v2_download_status_map on shutdown. Bugfix on
22319 - Stop leaking conn->nickname every time we make a connection to a
22320 Tor relay without knowing its expected identity digest (e.g. when
22321 using bridges). Bugfix on 0.2.0.3-alpha.
22323 - Minor bugfixes (portability):
22324 - Run correctly on platforms where rlim_t is larger than unsigned
22325 long, and/or where the real limit for number of open files is
22326 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
22327 particular, these may be needed for OS X 10.5.
22330 Changes in version 0.1.2.18 - 2007-10-28
22331 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
22332 hidden service introduction that were causing huge delays, and a big
22333 bug that was causing some servers to disappear from the network status
22334 lists for a few hours each day.
22336 o Major bugfixes (crashes):
22337 - If a connection is shut down abruptly because of something that
22338 happened inside connection_flushed_some(), do not call
22339 connection_finished_flushing(). Should fix bug 451:
22340 "connection_stop_writing: Assertion conn->write_event failed"
22341 Bugfix on 0.1.2.7-alpha.
22342 - Fix possible segfaults in functions called from
22343 rend_process_relay_cell().
22345 o Major bugfixes (hidden services):
22346 - Hidden services were choosing introduction points uniquely by
22347 hexdigest, but when constructing the hidden service descriptor
22348 they merely wrote the (potentially ambiguous) nickname.
22349 - Clients now use the v2 intro format for hidden service
22350 connections: they specify their chosen rendezvous point by identity
22351 digest rather than by (potentially ambiguous) nickname. These
22352 changes could speed up hidden service connections dramatically.
22354 o Major bugfixes (other):
22355 - Stop publishing a new server descriptor just because we get a
22356 HUP signal. This led (in a roundabout way) to some servers getting
22357 dropped from the networkstatus lists for a few hours each day.
22358 - When looking for a circuit to cannibalize, consider family as well
22359 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
22360 circuit cannibalization).
22361 - When a router wasn't listed in a new networkstatus, we were leaving
22362 the flags for that router alone -- meaning it remained Named,
22363 Running, etc -- even though absence from the networkstatus means
22364 that it shouldn't be considered to exist at all anymore. Now we
22365 clear all the flags for routers that fall out of the networkstatus
22366 consensus. Fixes bug 529.
22369 - Don't try to access (or alter) the state file when running
22370 --list-fingerprint or --verify-config or --hash-password. Resolves
22372 - When generating information telling us how to extend to a given
22373 router, do not try to include the nickname if it is
22374 absent. Resolves bug 467.
22375 - Fix a user-triggerable segfault in expand_filename(). (There isn't
22376 a way to trigger this remotely.)
22377 - When sending a status event to the controller telling it that an
22378 OR address is reachable, set the port correctly. (Previously we
22379 were reporting the dir port.)
22380 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
22381 command. Bugfix on 0.1.2.17.
22382 - When loading bandwidth history, do not believe any information in
22383 the future. Fixes bug 434.
22384 - When loading entry guard information, do not believe any information
22386 - When we have our clock set far in the future and generate an
22387 onion key, then re-set our clock to be correct, we should not stop
22388 the onion key from getting rotated.
22389 - On some platforms, accept() can return a broken address. Detect
22390 this more quietly, and deal accordingly. Fixes bug 483.
22391 - It's not actually an error to find a non-pending entry in the DNS
22392 cache when canceling a pending resolve. Don't log unless stuff
22393 is fishy. Resolves bug 463.
22394 - Don't reset trusted dir server list when we set a configuration
22395 option. Patch from Robert Hogan.
22396 - Don't try to create the datadir when running --verify-config or
22397 --hash-password. Resolves bug 540.
22400 Changes in version 0.2.0.9-alpha - 2007-10-24
22401 This ninth development snapshot switches clients to the new v3 directory
22402 system; allows servers to be listed in the network status even when they
22403 have the same nickname as a registered server; and fixes many other
22404 bugs including a big one that was causing some servers to disappear
22405 from the network status lists for a few hours each day.
22407 o Major features (directory system):
22408 - Clients now download v3 consensus networkstatus documents instead
22409 of v2 networkstatus documents. Clients and caches now base their
22410 opinions about routers on these consensus documents. Clients only
22411 download router descriptors listed in the consensus.
22412 - Authorities now list servers who have the same nickname as
22413 a different named server, but list them with a new flag,
22414 "Unnamed". Now we can list servers that happen to pick the same
22415 nickname as a server that registered two years ago and then
22416 disappeared. Partially implements proposal 122.
22417 - If the consensus lists a router as "Unnamed", the name is assigned
22418 to a different router: do not identify the router by that name.
22419 Partially implements proposal 122.
22420 - Authorities can now come to a consensus on which method to use to
22421 compute the consensus. This gives us forward compatibility.
22424 - Stop publishing a new server descriptor just because we HUP or
22425 when we find our DirPort to be reachable but won't actually publish
22426 it. New descriptors without any real changes are dropped by the
22427 authorities, and can screw up our "publish every 18 hours" schedule.
22429 - When a router wasn't listed in a new networkstatus, we were leaving
22430 the flags for that router alone -- meaning it remained Named,
22431 Running, etc -- even though absence from the networkstatus means
22432 that it shouldn't be considered to exist at all anymore. Now we
22433 clear all the flags for routers that fall out of the networkstatus
22434 consensus. Fixes bug 529; bugfix on 0.1.2.x.
22435 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
22436 extrainfo documents and then discard them immediately for not
22437 matching the latest router. Bugfix on 0.2.0.1-alpha.
22439 o Minor features (v3 directory protocol):
22440 - Allow tor-gencert to generate a new certificate without replacing
22442 - Allow certificates to include an address.
22443 - When we change our directory-cache settings, reschedule all voting
22444 and download operations.
22445 - Reattempt certificate downloads immediately on failure, as long as
22446 we haven't failed a threshold number of times yet.
22447 - Delay retrying consensus downloads while we're downloading
22448 certificates to verify the one we just got. Also, count getting a
22449 consensus that we already have (or one that isn't valid) as a failure,
22450 and count failing to get the certificates after 20 minutes as a
22452 - Build circuits and download descriptors even if our consensus is a
22453 little expired. (This feature will go away once authorities are
22456 o Minor features (router descriptor cache):
22457 - If we find a cached-routers file that's been sitting around for more
22458 than 28 days unmodified, then most likely it's a leftover from
22459 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
22461 - When we (as a cache) download a descriptor because it was listed
22462 in a consensus, remember when the consensus was supposed to expire,
22463 and don't expire the descriptor until then.
22465 o Minor features (performance):
22466 - Call routerlist_remove_old_routers() much less often. This should
22467 speed startup, especially on directory caches.
22468 - Don't try to launch new descriptor downloads quite so often when we
22469 already have enough directory information to build circuits.
22470 - Base64 decoding was actually showing up on our profile when parsing
22471 the initial descriptor file; switch to an in-process all-at-once
22472 implementation that's about 3.5x times faster than calling out to
22475 o Minor features (compilation):
22476 - Detect non-ASCII platforms (if any still exist) and refuse to
22477 build there: some of our code assumes that 'A' is 65 and so on.
22479 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
22480 - Make the "next period" votes into "current period" votes immediately
22481 after publishing the consensus; avoid a heisenbug that made them
22482 stick around indefinitely.
22483 - When we discard a vote as a duplicate, do not report this as
22485 - Treat missing v3 keys or certificates as an error when running as a
22486 v3 directory authority.
22487 - When we're configured to be a v3 authority, but we're only listed
22488 as a non-v3 authority in our DirServer line for ourself, correct
22490 - If an authority doesn't have a qualified hostname, just put
22491 its address in the vote. This fixes the problem where we referred to
22492 "moria on moria:9031."
22493 - Distinguish between detached signatures for the wrong period, and
22494 detached signatures for a divergent vote.
22495 - Fix a small memory leak when computing a consensus.
22496 - When there's no consensus, we were forming a vote every 30
22497 minutes, but writing the "valid-after" line in our vote based
22498 on our configured V3AuthVotingInterval: so unless the intervals
22499 matched up, we immediately rejected our own vote because it didn't
22500 start at the voting interval that caused us to construct a vote.
22502 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
22503 - Delete unverified-consensus when the real consensus is set.
22504 - Consider retrying a consensus networkstatus fetch immediately
22505 after one fails: don't wait 60 seconds to notice.
22506 - When fetching a consensus as a cache, wait until a newer consensus
22507 should exist before trying to replace the current one.
22508 - Use a more forgiving schedule for retrying failed consensus
22509 downloads than for other types.
22511 o Minor bugfixes (other directory issues):
22512 - Correct the implementation of "download votes by digest." Bugfix on
22514 - Authorities no longer send back "400 you're unreachable please fix
22515 it" errors to Tor servers that aren't online all the time. We're
22516 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
22518 o Minor bugfixes (controller):
22519 - Don't reset trusted dir server list when we set a configuration
22520 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
22521 - Respond to INT and TERM SIGNAL commands before we execute the
22522 signal, in case the signal shuts us down. We had a patch in
22523 0.1.2.1-alpha that tried to do this by queueing the response on
22524 the connection's buffer before shutting down, but that really
22525 isn't the same thing at all. Bug located by Matt Edman.
22527 o Minor bugfixes (misc):
22528 - Correctly check for bad options to the "PublishServerDescriptor"
22529 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
22530 - Stop leaking memory on failing case of base32_decode, and make
22531 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
22532 - Don't try to download extrainfo documents when we're trying to
22533 fetch enough directory info to build a circuit: having enough
22534 info should get priority. Bugfix on 0.2.0.x.
22535 - Don't complain that "your server has not managed to confirm that its
22536 ports are reachable" if we haven't been able to build any circuits
22537 yet. Bug found by spending four hours without a v3 consensus. Bugfix
22539 - Detect the reason for failing to mmap a descriptor file we just
22540 wrote, and give a more useful log message. Fixes bug 533. Bugfix
22543 o Code simplifications and refactoring:
22544 - Remove support for the old bw_accounting file: we've been storing
22545 bandwidth accounting information in the state file since
22546 0.1.2.5-alpha. This may result in bandwidth accounting errors
22547 if you try to upgrade from 0.1.1.x or earlier, or if you try to
22548 downgrade to 0.1.1.x or earlier.
22549 - New convenience code to locate a file within the DataDirectory.
22550 - Move non-authority functionality out of dirvote.c.
22551 - Refactor the arguments for router_pick_{directory_|trusteddir}server
22552 so that they all take the same named flags.
22555 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
22556 Unix users an easy way to script their Tor process (e.g. by
22557 adjusting bandwidth based on the time of the day).
22560 Changes in version 0.2.0.8-alpha - 2007-10-12
22561 This eighth development snapshot fixes a crash bug that's been bothering
22562 us since February 2007, lets bridge authorities store a list of bridge
22563 descriptors they've seen, gets v3 directory voting closer to working,
22564 starts caching v3 directory consensus documents on directory mirrors,
22565 and fixes a variety of smaller issues including some minor memory leaks.
22567 o Major features (router descriptor cache):
22568 - Store routers in a file called cached-descriptors instead of in
22569 cached-routers. Initialize cached-descriptors from cached-routers
22570 if the old format is around. The new format allows us to store
22571 annotations along with descriptors.
22572 - Use annotations to record the time we received each descriptor, its
22573 source, and its purpose.
22574 - Disable the SETROUTERPURPOSE controller command: it is now
22576 - Controllers should now specify cache=no or cache=yes when using
22577 the +POSTDESCRIPTOR command.
22578 - Bridge authorities now write bridge descriptors to disk, meaning
22579 we can export them to other programs and begin distributing them
22582 o Major features (directory authorities):
22583 - When a v3 authority is missing votes or signatures, it now tries
22585 - Directory authorities track weighted fractional uptime as well as
22586 weighted mean-time-between failures. WFU is suitable for deciding
22587 whether a node is "usually up", while MTBF is suitable for deciding
22588 whether a node is "likely to stay up." We need both, because
22589 "usually up" is a good requirement for guards, while "likely to
22590 stay up" is a good requirement for long-lived connections.
22592 o Major features (v3 directory system):
22593 - Caches now download v3 network status documents as needed,
22594 and download the descriptors listed in them.
22595 - All hosts now attempt to download and keep fresh v3 authority
22596 certificates, and re-attempt after failures.
22597 - More internal-consistency checks for vote parsing.
22599 o Major bugfixes (crashes):
22600 - If a connection is shut down abruptly because of something that
22601 happened inside connection_flushed_some(), do not call
22602 connection_finished_flushing(). Should fix bug 451. Bugfix on
22605 o Major bugfixes (performance):
22606 - Fix really bad O(n^2) performance when parsing a long list of
22607 routers: Instead of searching the entire list for an "extra-info "
22608 string which usually wasn't there, once for every routerinfo
22609 we read, just scan lines forward until we find one we like.
22611 - When we add data to a write buffer in response to the data on that
22612 write buffer getting low because of a flush, do not consider the
22613 newly added data as a candidate for immediate flushing, but rather
22614 make it wait until the next round of writing. Otherwise, we flush
22615 and refill recursively, and a single greedy TLS connection can
22616 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
22618 o Minor features (v3 authority system):
22619 - Add more ways for tools to download the votes that lead to the
22621 - Send a 503 when low on bandwidth and a vote, consensus, or
22622 certificate is requested.
22623 - If-modified-since is now implemented properly for all kinds of
22624 certificate requests.
22626 o Minor bugfixes (network statuses):
22627 - Tweak the implementation of proposal 109 slightly: allow at most
22628 two Tor servers on the same IP address, except if it's the location
22629 of a directory authority, in which case allow five. Bugfix on
22632 o Minor bugfixes (controller):
22633 - When sending a status event to the controller telling it that an
22634 OR address is reachable, set the port correctly. (Previously we
22635 were reporting the dir port.) Bugfix on 0.1.2.x.
22637 o Minor bugfixes (v3 directory system):
22638 - Fix logic to look up a cert by its signing key digest. Bugfix on
22640 - Only change the reply to a vote to "OK" if it's not already
22641 set. This gets rid of annoying "400 OK" log messages, which may
22642 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
22643 - When we get a valid consensus, recompute the voting schedule.
22644 - Base the valid-after time of a vote on the consensus voting
22645 schedule, not on our preferred schedule.
22646 - Make the return values and messages from signature uploads and
22647 downloads more sensible.
22648 - Fix a memory leak when serving votes and consensus documents, and
22649 another when serving certificates.
22651 o Minor bugfixes (performance):
22652 - Use a slightly simpler string hashing algorithm (copying Python's
22653 instead of Java's) and optimize our digest hashing algorithm to take
22654 advantage of 64-bit platforms and to remove some possibly-costly
22656 - Fix a minor memory leak whenever we parse guards from our state
22657 file. Bugfix on 0.2.0.7-alpha.
22658 - Fix a minor memory leak whenever we write out a file. Bugfix on
22660 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
22661 command. Bugfix on 0.2.0.5-alpha.
22663 o Minor bugfixes (portability):
22664 - On some platforms, accept() can return a broken address. Detect
22665 this more quietly, and deal accordingly. Fixes bug 483.
22666 - Stop calling tor_strlower() on uninitialized memory in some cases.
22667 Bugfix in 0.2.0.7-alpha.
22669 o Minor bugfixes (usability):
22670 - Treat some 403 responses from directory servers as INFO rather than
22671 WARN-severity events.
22672 - It's not actually an error to find a non-pending entry in the DNS
22673 cache when canceling a pending resolve. Don't log unless stuff is
22674 fishy. Resolves bug 463.
22676 o Minor bugfixes (anonymity):
22677 - Never report that we've used more bandwidth than we're willing to
22678 relay: it leaks how much non-relay traffic we're using. Resolves
22680 - When looking for a circuit to cannibalize, consider family as well
22681 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
22682 circuit cannibalization).
22684 o Code simplifications and refactoring:
22685 - Make a bunch of functions static. Remove some dead code.
22686 - Pull out about a third of the really big routerlist.c; put it in a
22687 new module, networkstatus.c.
22688 - Merge the extra fields in local_routerstatus_t back into
22689 routerstatus_t: we used to need one routerstatus_t for each
22690 authority's opinion, plus a local_routerstatus_t for the locally
22691 computed consensus opinion. To save space, we put the locally
22692 modified fields into local_routerstatus_t, and only the common
22693 stuff into routerstatus_t. But once v3 directories are in use,
22694 clients and caches will no longer need to hold authority opinions;
22695 thus, the rationale for keeping the types separate is now gone.
22696 - Make the code used to reschedule and reattempt downloads more
22698 - Turn all 'Are we a directory server/mirror?' logic into a call to
22700 - Remove the code to generate the oldest (v1) directory format.
22701 The code has been disabled since 0.2.0.5-alpha.
22704 Changes in version 0.2.0.7-alpha - 2007-09-21
22705 This seventh development snapshot makes bridges work again, makes bridge
22706 authorities work for the first time, fixes two huge performance flaws
22707 in hidden services, and fixes a variety of minor issues.
22709 o New directory authorities:
22710 - Set up moria1 and tor26 as the first v3 directory authorities. See
22711 doc/spec/dir-spec.txt for details on the new directory design.
22713 o Major bugfixes (crashes):
22714 - Fix possible segfaults in functions called from
22715 rend_process_relay_cell(). Bugfix on 0.1.2.x.
22717 o Major bugfixes (bridges):
22718 - Fix a bug that made servers send a "404 Not found" in response to
22719 attempts to fetch their server descriptor. This caused Tor servers
22720 to take many minutes to establish reachability for their DirPort,
22721 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
22722 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
22723 users configure that and specify a bridge with an identity
22724 fingerprint, now they will lookup the bridge descriptor at the
22725 default bridge authority via a one-hop tunnel, but once circuits
22726 are established they will switch to a three-hop tunnel for later
22727 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
22729 o Major bugfixes (hidden services):
22730 - Hidden services were choosing introduction points uniquely by
22731 hexdigest, but when constructing the hidden service descriptor
22732 they merely wrote the (potentially ambiguous) nickname.
22733 - Clients now use the v2 intro format for hidden service
22734 connections: they specify their chosen rendezvous point by identity
22735 digest rather than by (potentially ambiguous) nickname. Both
22736 are bugfixes on 0.1.2.x, and they could speed up hidden service
22737 connections dramatically. Thanks to Karsten Loesing.
22739 o Minor features (security):
22740 - As a client, do not believe any server that tells us that an
22741 address maps to an internal address space.
22742 - Make it possible to enable HashedControlPassword and
22743 CookieAuthentication at the same time.
22745 o Minor features (guard nodes):
22746 - Tag every guard node in our state file with the version that
22747 we believe added it, or with our own version if we add it. This way,
22748 if a user temporarily runs an old version of Tor and then switches
22749 back to a new one, she doesn't automatically lose her guards.
22751 o Minor features (speed):
22752 - When implementing AES counter mode, update only the portions of the
22753 counter buffer that need to change, and don't keep separate
22754 network-order and host-order counters when they are the same (i.e.,
22755 on big-endian hosts.)
22757 o Minor features (controller):
22758 - Accept LF instead of CRLF on controller, since some software has a
22759 hard time generating real Internet newlines.
22760 - Add GETINFO values for the server status events
22761 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
22764 o Removed features:
22765 - Routers no longer include bandwidth-history lines in their
22766 descriptors; this information is already available in extra-info
22767 documents, and including it in router descriptors took up 60%
22768 (!) of compressed router descriptor downloads. Completes
22769 implementation of proposal 104.
22770 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
22771 and TorControl.py, as they use the old v0 controller protocol,
22772 and are obsoleted by TorFlow anyway.
22773 - Drop support for v1 rendezvous descriptors, since we never used
22774 them anyway, and the code has probably rotted by now. Based on
22775 patch from Karsten Loesing.
22776 - On OSX, stop warning the user that kqueue support in libevent is
22777 "experimental", since it seems to have worked fine for ages.
22780 - When generating information telling us how to extend to a given
22781 router, do not try to include the nickname if it is absent. Fixes
22782 bug 467. Bugfix on 0.2.0.3-alpha.
22783 - Fix a user-triggerable (but not remotely-triggerable) segfault
22784 in expand_filename(). Bugfix on 0.1.2.x.
22785 - Fix a memory leak when freeing incomplete requests from DNSPort.
22786 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
22787 - Don't try to access (or alter) the state file when running
22788 --list-fingerprint or --verify-config or --hash-password. (Resolves
22789 bug 499.) Bugfix on 0.1.2.x.
22790 - Servers used to decline to publish their DirPort if their
22791 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
22792 were below a threshold. Now they only look at BandwidthRate and
22793 RelayBandwidthRate. Bugfix on 0.1.2.x.
22794 - Remove an optimization in the AES counter-mode code that assumed
22795 that the counter never exceeded 2^68. When the counter can be set
22796 arbitrarily as an IV (as it is by Karsten's new hidden services
22797 code), this assumption no longer holds. Bugfix on 0.1.2.x.
22798 - Resume listing "AUTHORITY" flag for authorities in network status.
22799 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
22801 o Code simplifications and refactoring:
22802 - Revamp file-writing logic so we don't need to have the entire
22803 contents of a file in memory at once before we write to disk. Tor,
22805 - Turn "descriptor store" into a full-fledged type.
22806 - Move all NT services code into a separate source file.
22807 - Unify all code that computes medians, percentile elements, etc.
22808 - Get rid of a needless malloc when parsing address policies.
22811 Changes in version 0.1.2.17 - 2007-08-30
22812 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
22813 X bundles. Vidalia 0.0.14 makes authentication required for the
22814 ControlPort in the default configuration, which addresses important
22815 security risks. Everybody who uses Vidalia (or another controller)
22818 In addition, this Tor update fixes major load balancing problems with
22819 path selection, which should speed things up a lot once many people
22822 o Major bugfixes (security):
22823 - We removed support for the old (v0) control protocol. It has been
22824 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
22825 become more of a headache than it's worth.
22827 o Major bugfixes (load balancing):
22828 - When choosing nodes for non-guard positions, weight guards
22829 proportionally less, since they already have enough load. Patch
22831 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
22832 will allow fast Tor servers to get more attention.
22833 - When we're upgrading from an old Tor version, forget our current
22834 guards and pick new ones according to the new weightings. These
22835 three load balancing patches could raise effective network capacity
22836 by a factor of four. Thanks to Mike Perry for measurements.
22838 o Major bugfixes (stream expiration):
22839 - Expire not-yet-successful application streams in all cases if
22840 they've been around longer than SocksTimeout. Right now there are
22841 some cases where the stream will live forever, demanding a new
22842 circuit every 15 seconds. Fixes bug 454; reported by lodger.
22844 o Minor features (controller):
22845 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
22846 is valid before any authentication has been received. It tells
22847 a controller what kind of authentication is expected, and what
22848 protocol is spoken. Implements proposal 119.
22850 o Minor bugfixes (performance):
22851 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
22852 greatly speeding up loading cached-routers from disk on startup.
22853 - Disable sentinel-based debugging for buffer code: we squashed all
22854 the bugs that this was supposed to detect a long time ago, and now
22855 its only effect is to change our buffer sizes from nice powers of
22856 two (which platform mallocs tend to like) to values slightly over
22857 powers of two (which make some platform mallocs sad).
22859 o Minor bugfixes (misc):
22860 - If exit bandwidth ever exceeds one third of total bandwidth, then
22861 use the correct formula to weight exit nodes when choosing paths.
22862 Based on patch from Mike Perry.
22863 - Choose perfectly fairly among routers when choosing by bandwidth and
22864 weighting by fraction of bandwidth provided by exits. Previously, we
22865 would choose with only approximate fairness, and correct ourselves
22866 if we ran off the end of the list.
22867 - If we require CookieAuthentication but we fail to write the
22868 cookie file, we would warn but not exit, and end up in a state
22869 where no controller could authenticate. Now we exit.
22870 - If we require CookieAuthentication, stop generating a new cookie
22871 every time we change any piece of our config.
22872 - Refuse to start with certain directory authority keys, and
22873 encourage people using them to stop.
22874 - Terminate multi-line control events properly. Original patch
22876 - Fix a minor memory leak when we fail to find enough suitable
22877 servers to choose a circuit.
22878 - Stop leaking part of the descriptor when we run into a particularly
22879 unparseable piece of it.
22882 Changes in version 0.2.0.6-alpha - 2007-08-26
22883 This sixth development snapshot features a new Vidalia version in the
22884 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
22885 the ControlPort in the default configuration, which addresses important
22888 In addition, this snapshot fixes major load balancing problems
22889 with path selection, which should speed things up a lot once many
22890 people have upgraded. The directory authorities also use a new
22891 mean-time-between-failure approach to tracking which servers are stable,
22892 rather than just looking at the most recent uptime.
22894 o New directory authorities:
22895 - Set up Tonga as the default bridge directory authority.
22898 - Directory authorities now track servers by weighted
22899 mean-times-between-failures. When we have 4 or more days of data,
22900 use measured MTBF rather than declared uptime to decide whether
22901 to call a router Stable. Implements proposal 108.
22903 o Major bugfixes (load balancing):
22904 - When choosing nodes for non-guard positions, weight guards
22905 proportionally less, since they already have enough load. Patch
22907 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
22908 will allow fast Tor servers to get more attention.
22909 - When we're upgrading from an old Tor version, forget our current
22910 guards and pick new ones according to the new weightings. These
22911 three load balancing patches could raise effective network capacity
22912 by a factor of four. Thanks to Mike Perry for measurements.
22914 o Major bugfixes (descriptor parsing):
22915 - Handle unexpected whitespace better in malformed descriptors. Bug
22916 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
22919 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
22920 GETINFO for Torstat to use until it can switch to using extrainfos.
22921 - Optionally (if built with -DEXPORTMALLINFO) export the output
22922 of mallinfo via http, as tor/mallinfo.txt. Only accessible
22926 - Do not intermix bridge routers with controller-added
22927 routers. (Bugfix on 0.2.0.x)
22928 - Do not fail with an assert when accept() returns an unexpected
22929 address family. Addresses but does not wholly fix bug 483. (Bugfix
22931 - Let directory authorities startup even when they can't generate
22932 a descriptor immediately, e.g. because they don't know their
22934 - Stop putting the authentication cookie in a file called "0"
22935 in your working directory if you don't specify anything for the
22936 new CookieAuthFile option. Reported by Matt Edman.
22937 - Make it possible to read the PROTOCOLINFO response in a way that
22938 conforms to our control-spec. Reported by Matt Edman.
22939 - Fix a minor memory leak when we fail to find enough suitable
22940 servers to choose a circuit. Bugfix on 0.1.2.x.
22941 - Stop leaking part of the descriptor when we run into a particularly
22942 unparseable piece of it. Bugfix on 0.1.2.x.
22943 - Unmap the extrainfo cache file on exit.
22946 Changes in version 0.2.0.5-alpha - 2007-08-19
22947 This fifth development snapshot fixes compilation on Windows again;
22948 fixes an obnoxious client-side bug that slowed things down and put
22949 extra load on the network; gets us closer to using the v3 directory
22950 voting scheme; makes it easier for Tor controllers to use cookie-based
22951 authentication; and fixes a variety of other bugs.
22953 o Removed features:
22954 - Version 1 directories are no longer generated in full. Instead,
22955 authorities generate and serve "stub" v1 directories that list
22956 no servers. This will stop Tor versions 0.1.0.x and earlier from
22957 working, but (for security reasons) nobody should be running those
22960 o Major bugfixes (compilation, 0.2.0.x):
22961 - Try to fix Win32 compilation again: improve checking for IPv6 types.
22962 - Try to fix MSVC compilation: build correctly on platforms that do
22963 not define s6_addr16 or s6_addr32.
22964 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
22967 o Major bugfixes (stream expiration):
22968 - Expire not-yet-successful application streams in all cases if
22969 they've been around longer than SocksTimeout. Right now there are
22970 some cases where the stream will live forever, demanding a new
22971 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
22972 reported by lodger.
22974 o Minor features (directory servers):
22975 - When somebody requests a list of statuses or servers, and we have
22976 none of those, return a 404 rather than an empty 200.
22978 o Minor features (directory voting):
22979 - Store v3 consensus status consensuses on disk, and reload them
22982 o Minor features (security):
22983 - Warn about unsafe ControlPort configurations.
22984 - Refuse to start with certain directory authority keys, and
22985 encourage people using them to stop.
22987 o Minor features (controller):
22988 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
22989 is valid before any authentication has been received. It tells
22990 a controller what kind of authentication is expected, and what
22991 protocol is spoken. Implements proposal 119.
22992 - New config option CookieAuthFile to choose a new location for the
22993 cookie authentication file, and config option
22994 CookieAuthFileGroupReadable to make it group-readable.
22996 o Minor features (unit testing):
22997 - Add command-line arguments to unit-test executable so that we can
22998 invoke any chosen test from the command line rather than having
22999 to run the whole test suite at once; and so that we can turn on
23000 logging for the unit tests.
23002 o Minor bugfixes (on 0.1.2.x):
23003 - If we require CookieAuthentication but we fail to write the
23004 cookie file, we would warn but not exit, and end up in a state
23005 where no controller could authenticate. Now we exit.
23006 - If we require CookieAuthentication, stop generating a new cookie
23007 every time we change any piece of our config.
23008 - When loading bandwidth history, do not believe any information in
23009 the future. Fixes bug 434.
23010 - When loading entry guard information, do not believe any information
23012 - When we have our clock set far in the future and generate an
23013 onion key, then re-set our clock to be correct, we should not stop
23014 the onion key from getting rotated.
23015 - Clean up torrc sample config file.
23016 - Do not automatically run configure from autogen.sh. This
23017 non-standard behavior tended to annoy people who have built other
23020 o Minor bugfixes (on 0.2.0.x):
23021 - Fix a bug with AutomapHostsOnResolve that would always cause
23022 the second request to fail. Bug reported by Kate. Bugfix on
23024 - Fix a bug in ADDRMAP controller replies that would sometimes
23025 try to print a NULL. Patch from tup.
23026 - Read v3 directory authority keys from the right location.
23027 - Numerous bugfixes to directory voting code.
23030 Changes in version 0.1.2.16 - 2007-08-01
23031 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
23032 remote attacker in certain situations to rewrite the user's torrc
23033 configuration file. This can completely compromise anonymity of users
23034 in most configurations, including those running the Vidalia bundles,
23035 TorK, etc. Or worse.
23037 o Major security fixes:
23038 - Close immediately after missing authentication on control port;
23039 do not allow multiple authentication attempts.
23042 Changes in version 0.2.0.4-alpha - 2007-08-01
23043 This fourth development snapshot fixes a critical security vulnerability
23044 for most users, specifically those running Vidalia, TorK, etc. Everybody
23045 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
23047 o Major security fixes:
23048 - Close immediately after missing authentication on control port;
23049 do not allow multiple authentication attempts.
23051 o Major bugfixes (compilation):
23052 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
23055 o Minor features (performance):
23056 - Be even more aggressive about releasing RAM from small
23057 empty buffers. Thanks to our free-list code, this shouldn't be too
23058 performance-intensive.
23059 - Disable sentinel-based debugging for buffer code: we squashed all
23060 the bugs that this was supposed to detect a long time ago, and
23061 now its only effect is to change our buffer sizes from nice
23062 powers of two (which platform mallocs tend to like) to values
23063 slightly over powers of two (which make some platform mallocs sad).
23064 - Log malloc statistics from mallinfo() on platforms where it
23068 Changes in version 0.2.0.3-alpha - 2007-07-29
23069 This third development snapshot introduces new experimental
23070 blocking-resistance features and a preliminary version of the v3
23071 directory voting design, and includes many other smaller features
23075 - The first pieces of our "bridge" design for blocking-resistance
23076 are implemented. People can run bridge directory authorities;
23077 people can run bridges; and people can configure their Tor clients
23078 with a set of bridges to use as the first hop into the Tor network.
23079 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
23081 - Create listener connections before we setuid to the configured
23082 User and Group. Now non-Windows users can choose port values
23083 under 1024, start Tor as root, and have Tor bind those ports
23084 before it changes to another UID. (Windows users could already
23086 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
23087 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
23088 on "vserver" accounts. (Patch from coderman.)
23089 - Be even more aggressive about separating local traffic from relayed
23090 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
23092 o Major features (experimental):
23093 - First cut of code for "v3 dir voting": directory authorities will
23094 vote on a common network status document rather than each publishing
23095 their own opinion. This code needs more testing and more corner-case
23096 handling before it's ready for use.
23099 - Directory authorities now call routers Fast if their bandwidth is
23100 at least 100KB/s, and consider their bandwidth adequate to be a
23101 Guard if it is at least 250KB/s, no matter the medians. This fix
23102 complements proposal 107. [Bugfix on 0.1.2.x]
23103 - Directory authorities now never mark more than 3 servers per IP as
23104 Valid and Running. (Implements proposal 109, by Kevin Bauer and
23106 - Minor change to organizationName and commonName generation
23107 procedures in TLS certificates during Tor handshakes, to invalidate
23108 some earlier censorware approaches. This is not a long-term
23109 solution, but applying it will give us a bit of time to look into
23110 the epidemiology of countermeasures as they spread.
23112 o Major bugfixes (directory):
23113 - Rewrite directory tokenization code to never run off the end of
23114 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
23116 o Minor features (controller):
23117 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
23118 match requests to applications. (Patch from Robert Hogan.)
23119 - Report address and port correctly on connections to DNSPort. (Patch
23120 from Robert Hogan.)
23121 - Add a RESOLVE command to launch hostname lookups. (Original patch
23122 from Robert Hogan.)
23123 - Add GETINFO status/enough-dir-info to let controllers tell whether
23124 Tor has downloaded sufficient directory information. (Patch
23126 - You can now use the ControlSocket option to tell Tor to listen for
23127 controller connections on Unix domain sockets on systems that
23128 support them. (Patch from Peter Palfrader.)
23129 - STREAM NEW events are generated for DNSPort requests and for
23130 tunneled directory connections. (Patch from Robert Hogan.)
23131 - New "GETINFO address-mappings/*" command to get address mappings
23132 with expiry information. "addr-mappings/*" is now deprecated.
23135 o Minor features (misc):
23136 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
23138 - The tor-gencert tool for v3 directory authorities now creates all
23139 files as readable to the file creator only, and write-protects
23140 the authority identity key.
23141 - When dumping memory usage, list bytes used in buffer memory
23143 - When running with dmalloc, dump more stats on hup and on exit.
23144 - Directory authorities now fail quickly and (relatively) harmlessly
23145 if they generate a network status document that is somehow
23148 o Traffic load balancing improvements:
23149 - If exit bandwidth ever exceeds one third of total bandwidth, then
23150 use the correct formula to weight exit nodes when choosing paths.
23151 (Based on patch from Mike Perry.)
23152 - Choose perfectly fairly among routers when choosing by bandwidth and
23153 weighting by fraction of bandwidth provided by exits. Previously, we
23154 would choose with only approximate fairness, and correct ourselves
23155 if we ran off the end of the list. [Bugfix on 0.1.2.x]
23157 o Performance improvements:
23158 - Be more aggressive with freeing buffer RAM or putting it on the
23160 - Use Critical Sections rather than Mutexes for synchronizing threads
23161 on win32; Mutexes are heavier-weight, and designed for synchronizing
23164 o Deprecated and removed features:
23165 - RedirectExits is now deprecated.
23166 - Stop allowing address masks that do not correspond to bit prefixes.
23167 We have warned about these for a really long time; now it's time
23168 to reject them. (Patch from croup.)
23170 o Minor bugfixes (directory):
23171 - Fix another crash bug related to extra-info caching. (Bug found by
23172 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
23173 - Directories no longer return a "304 not modified" when they don't
23174 have the networkstatus the client asked for. Also fix a memory
23175 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
23176 - We had accidentally labelled 0.1.2.x directory servers as not
23177 suitable for begin_dir requests, and had labelled no directory
23178 servers as suitable for uploading extra-info documents. [Bugfix
23181 o Minor bugfixes (dns):
23182 - Fix a crash when DNSPort is set more than once. (Patch from Robert
23183 Hogan.) [Bugfix on 0.2.0.2-alpha]
23184 - Add DNSPort connections to the global connection list, so that we
23185 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
23187 - Fix a dangling reference that could lead to a crash when DNSPort is
23188 changed or closed (Patch from Robert Hogan.) [Bugfix on
23191 o Minor bugfixes (controller):
23192 - Provide DNS expiry times in GMT, not in local time. For backward
23193 compatibility, ADDRMAP events only provide GMT expiry in an extended
23194 field. "GETINFO address-mappings" always does the right thing.
23195 - Use CRLF line endings properly in NS events.
23196 - Terminate multi-line control events properly. (Original patch
23197 from tup.) [Bugfix on 0.1.2.x-alpha]
23198 - Do not include spaces in SOURCE_ADDR fields in STREAM
23199 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
23202 Changes in version 0.1.2.15 - 2007-07-17
23203 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
23204 problems, fixes compilation on BSD, and fixes a variety of other
23205 bugs. Everybody should upgrade.
23207 o Major bugfixes (compilation):
23208 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
23210 o Major bugfixes (crashes):
23211 - Try even harder not to dereference the first character after
23212 an mmap(). Reported by lodger.
23213 - Fix a crash bug in directory authorities when we re-number the
23214 routerlist while inserting a new router.
23215 - When the cached-routers file is an even multiple of the page size,
23216 don't run off the end and crash. (Fixes bug 455; based on idea
23218 - Fix eventdns.c behavior on Solaris: It is critical to include
23219 orconfig.h _before_ sys/types.h, so that we can get the expected
23220 definition of _FILE_OFFSET_BITS.
23222 o Major bugfixes (security):
23223 - Fix a possible buffer overrun when using BSD natd support. Bug
23225 - When sending destroy cells from a circuit's origin, don't include
23226 the reason for tearing down the circuit. The spec says we didn't,
23227 and now we actually don't. Reported by lodger.
23228 - Keep streamids from different exits on a circuit separate. This
23229 bug may have allowed other routers on a given circuit to inject
23230 cells into streams. Reported by lodger; fixes bug 446.
23231 - If there's a never-before-connected-to guard node in our list,
23232 never choose any guards past it. This way we don't expand our
23233 guard list unless we need to.
23235 o Minor bugfixes (guard nodes):
23236 - Weight guard selection by bandwidth, so that low-bandwidth nodes
23237 don't get overused as guards.
23239 o Minor bugfixes (directory):
23240 - Correctly count the number of authorities that recommend each
23241 version. Previously, we were under-counting by 1.
23242 - Fix a potential crash bug when we load many server descriptors at
23243 once and some of them make others of them obsolete. Fixes bug 458.
23245 o Minor bugfixes (hidden services):
23246 - Stop tearing down the whole circuit when the user asks for a
23247 connection to a port that the hidden service didn't configure.
23250 o Minor bugfixes (misc):
23251 - On Windows, we were preventing other processes from reading
23252 cached-routers while Tor was running. Reported by janbar.
23253 - Fix a possible (but very unlikely) bug in picking routers by
23254 bandwidth. Add a log message to confirm that it is in fact
23255 unlikely. Patch from lodger.
23256 - Backport a couple of memory leak fixes.
23257 - Backport miscellaneous cosmetic bugfixes.
23260 Changes in version 0.2.0.2-alpha - 2007-06-02
23261 o Major bugfixes on 0.2.0.1-alpha:
23262 - Fix an assertion failure related to servers without extra-info digests.
23263 Resolves bugs 441 and 442.
23265 o Minor features (directory):
23266 - Support "If-Modified-Since" when answering HTTP requests for
23267 directories, running-routers documents, and network-status documents.
23268 (There's no need to support it for router descriptors, since those
23269 are downloaded by descriptor digest.)
23271 o Minor build issues:
23272 - Clear up some MIPSPro compiler warnings.
23273 - When building from a tarball on a machine that happens to have SVK
23274 installed, report the micro-revision as whatever version existed
23275 in the tarball, not as "x".
23278 Changes in version 0.2.0.1-alpha - 2007-06-01
23279 This early development snapshot provides new features for people running
23280 Tor as both a client and a server (check out the new RelayBandwidth
23281 config options); lets Tor run as a DNS proxy; and generally moves us
23282 forward on a lot of fronts.
23284 o Major features, server usability:
23285 - New config options RelayBandwidthRate and RelayBandwidthBurst:
23286 a separate set of token buckets for relayed traffic. Right now
23287 relayed traffic is defined as answers to directory requests, and
23288 OR connections that don't have any local circuits on them.
23290 o Major features, client usability:
23291 - A client-side DNS proxy feature to replace the need for
23292 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
23293 for DNS requests on port 9999, use the Tor network to resolve them
23294 anonymously, and send the reply back like a regular DNS server.
23295 The code still only implements a subset of DNS.
23296 - Make PreferTunneledDirConns and TunnelDirConns work even when
23297 we have no cached directory info. This means Tor clients can now
23298 do all of their connections protected by TLS.
23300 o Major features, performance and efficiency:
23301 - Directory authorities accept and serve "extra info" documents for
23302 routers. These documents contain fields from router descriptors
23303 that aren't usually needed, and that use a lot of excess
23304 bandwidth. Once these fields are removed from router descriptors,
23305 the bandwidth savings should be about 60%. [Partially implements
23307 - Servers upload extra-info documents to any authority that accepts
23308 them. Authorities (and caches that have been configured to download
23309 extra-info documents) download them as needed. [Partially implements
23311 - Change the way that Tor buffers data that it is waiting to write.
23312 Instead of queueing data cells in an enormous ring buffer for each
23313 client->OR or OR->OR connection, we now queue cells on a separate
23314 queue for each circuit. This lets us use less slack memory, and
23315 will eventually let us be smarter about prioritizing different kinds
23317 - Use memory pools to allocate cells with better speed and memory
23318 efficiency, especially on platforms where malloc() is inefficient.
23319 - Stop reading on edge connections when their corresponding circuit
23320 buffers are full; start again as the circuits empty out.
23322 o Major features, other:
23323 - Add an HSAuthorityRecordStats option that hidden service authorities
23324 can use to track statistics of overall hidden service usage without
23325 logging information that would be very useful to an attacker.
23326 - Start work implementing multi-level keys for directory authorities:
23327 Add a standalone tool to generate key certificates. (Proposal 103.)
23330 - Directory authorities now call routers Stable if they have an
23331 uptime of at least 30 days, even if that's not the median uptime
23332 in the network. Implements proposal 107, suggested by Kevin Bauer
23335 o Minor fixes (resource management):
23336 - Count the number of open sockets separately from the number
23337 of active connection_t objects. This will let us avoid underusing
23338 our allocated connection limit.
23339 - We no longer use socket pairs to link an edge connection to an
23340 anonymous directory connection or a DirPort test connection.
23341 Instead, we track the link internally and transfer the data
23342 in-process. This saves two sockets per "linked" connection (at the
23343 client and at the server), and avoids the nasty Windows socketpair()
23345 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
23346 for every single inactive connection_t. Free items from the
23347 4k/16k-buffer free lists when they haven't been used for a while.
23349 o Minor features (build):
23350 - Make autoconf search for libevent, openssl, and zlib consistently.
23351 - Update deprecated macros in configure.in.
23352 - When warning about missing headers, tell the user to let us
23353 know if the compile succeeds anyway, so we can downgrade the
23355 - Include the current subversion revision as part of the version
23356 string: either fetch it directly if we're in an SVN checkout, do
23357 some magic to guess it if we're in an SVK checkout, or use
23358 the last-detected version if we're building from a .tar.gz.
23359 Use this version consistently in log messages.
23361 o Minor features (logging):
23362 - Always prepend "Bug: " to any log message about a bug.
23363 - Put a platform string (e.g. "Linux i686") in the startup log
23364 message, so when people paste just their logs, we know if it's
23365 OpenBSD or Windows or what.
23366 - When logging memory usage, break down memory used in buffers by
23369 o Minor features (directory system):
23370 - New config option V2AuthoritativeDirectory that all directory
23371 authorities should set. This will let future authorities choose
23372 not to serve V2 directory information.
23373 - Directory authorities allow multiple router descriptors and/or extra
23374 info documents to be uploaded in a single go. This will make
23375 implementing proposal 104 simpler.
23377 o Minor features (controller):
23378 - Add a new config option __DisablePredictedCircuits designed for
23379 use by the controller, when we don't want Tor to build any circuits
23381 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
23382 so we can exit from the middle of the circuit.
23383 - Implement "getinfo status/circuit-established".
23384 - Implement "getinfo status/version/..." so a controller can tell
23385 whether the current version is recommended, and whether any versions
23386 are good, and how many authorities agree. (Patch from shibz.)
23388 o Minor features (hidden services):
23389 - Allow multiple HiddenServicePort directives with the same virtual
23390 port; when they occur, the user is sent round-robin to one
23391 of the target ports chosen at random. Partially fixes bug 393 by
23392 adding limited ad-hoc round-robining.
23394 o Minor features (other):
23396 - Add a new AutomapHostsOnResolve option: when it is enabled, any
23397 resolve request for hosts matching a given pattern causes Tor to
23398 generate an internal virtual address mapping for that host. This
23399 allows DNSPort to work sensibly with hidden service users. By
23400 default, .exit and .onion addresses are remapped; the list of
23401 patterns can be reconfigured with AutomapHostsSuffixes.
23402 - Add an "-F" option to tor-resolve to force a resolve for a .onion
23403 address. Thanks to the AutomapHostsOnResolve option, this is no
23404 longer a completely silly thing to do.
23405 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
23406 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
23407 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
23408 minus 1 byte: the actual maximum declared bandwidth.
23410 o Removed features:
23411 - Removed support for the old binary "version 0" controller protocol.
23412 This has been deprecated since 0.1.1, and warnings have been issued
23413 since 0.1.2. When we encounter a v0 control message, we now send
23414 back an error and close the connection.
23415 - Remove the old "dns worker" server DNS code: it hasn't been default
23416 since 0.1.2.2-alpha, and all the servers seem to be using the new
23419 o Minor bugfixes (portability):
23420 - Even though Windows is equally happy with / and \ as path separators,
23421 try to use \ consistently on Windows and / consistently on Unix: it
23422 makes the log messages nicer.
23423 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
23424 - Read resolv.conf files correctly on platforms where read() returns
23425 partial results on small file reads.
23427 o Minor bugfixes (directory):
23428 - Correctly enforce that elements of directory objects do not appear
23429 more often than they are allowed to appear.
23430 - When we are reporting the DirServer line we just parsed, we were
23431 logging the second stanza of the key fingerprint, not the first.
23433 o Minor bugfixes (logging):
23434 - When we hit an EOF on a log (probably because we're shutting down),
23435 don't try to remove the log from the list: just mark it as
23436 unusable. (Bulletproofs against bug 222.)
23438 o Minor bugfixes (other):
23439 - In the exitlist script, only consider the most recently published
23440 server descriptor for each server. Also, when the user requests
23441 a list of servers that _reject_ connections to a given address,
23442 explicitly exclude the IPs that also have servers that accept
23443 connections to that address. (Resolves bug 405.)
23444 - Stop allowing hibernating servers to be "stable" or "fast".
23445 - On Windows, we were preventing other processes from reading
23446 cached-routers while Tor was running. (Reported by janbar)
23447 - Make the NodeFamilies config option work. (Reported by
23448 lodger -- it has never actually worked, even though we added it
23450 - Check return values from pthread_mutex functions.
23451 - Don't save non-general-purpose router descriptors to the disk cache,
23452 because we have no way of remembering what their purpose was when
23454 - Add even more asserts to hunt down bug 417.
23455 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
23456 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
23457 Add a log message to confirm that it is in fact unlikely.
23459 o Minor bugfixes (controller):
23460 - Make 'getinfo fingerprint' return a 551 error if we're not a
23461 server, so we match what the control spec claims we do. Reported
23463 - Fix a typo in an error message when extendcircuit fails that
23464 caused us to not follow the \r\n-based delimiter protocol. Reported
23467 o Code simplifications and refactoring:
23468 - Stop passing around circuit_t and crypt_path_t pointers that are
23469 implicit in other procedure arguments.
23470 - Drop the old code to choke directory connections when the
23471 corresponding OR connections got full: thanks to the cell queue
23472 feature, OR conns don't get full any more.
23473 - Make dns_resolve() handle attaching connections to circuits
23474 properly, so the caller doesn't have to.
23475 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
23476 - Keep the connection array as a dynamic smartlist_t, rather than as
23477 a fixed-sized array. This is important, as the number of connections
23478 is becoming increasingly decoupled from the number of sockets.
23481 Changes in version 0.1.2.14 - 2007-05-25
23482 Tor 0.1.2.14 changes the addresses of two directory authorities (this
23483 change especially affects those who serve or use hidden services),
23484 and fixes several other crash- and security-related bugs.
23486 o Directory authority changes:
23487 - Two directory authorities (moria1 and moria2) just moved to new
23488 IP addresses. This change will particularly affect those who serve
23489 or use hidden services.
23491 o Major bugfixes (crashes):
23492 - If a directory server runs out of space in the connection table
23493 as it's processing a begin_dir request, it will free the exit stream
23494 but leave it attached to the circuit, leading to unpredictable
23495 behavior. (Reported by seeess, fixes bug 425.)
23496 - Fix a bug in dirserv_remove_invalid() that would cause authorities
23497 to corrupt memory under some really unlikely scenarios.
23498 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
23499 - Avoid segfaults when reading from mmaped descriptor file. (Reported
23502 o Major bugfixes (security):
23503 - When choosing an entry guard for a circuit, avoid using guards
23504 that are in the same family as the chosen exit -- not just guards
23505 that are exactly the chosen exit. (Reported by lodger.)
23507 o Major bugfixes (resource management):
23508 - If a directory authority is down, skip it when deciding where to get
23509 networkstatus objects or descriptors. Otherwise we keep asking
23510 every 10 seconds forever. Fixes bug 384.
23511 - Count it as a failure if we fetch a valid network-status but we
23512 don't want to keep it. Otherwise we'll keep fetching it and keep
23513 not wanting to keep it. Fixes part of bug 422.
23514 - If all of our dirservers have given us bad or no networkstatuses
23515 lately, then stop hammering them once per minute even when we
23516 think they're failed. Fixes another part of bug 422.
23519 - Actually set the purpose correctly for descriptors inserted with
23520 purpose=controller.
23521 - When we have k non-v2 authorities in our DirServer config,
23522 we ignored the last k authorities in the list when updating our
23524 - Correctly back-off from requesting router descriptors that we are
23525 having a hard time downloading.
23526 - Read resolv.conf files correctly on platforms where read() returns
23527 partial results on small file reads.
23528 - Don't rebuild the entire router store every time we get 32K of
23529 routers: rebuild it when the journal gets very large, or when
23530 the gaps in the store get very large.
23533 - When routers publish SVN revisions in their router descriptors,
23534 authorities now include those versions correctly in networkstatus
23536 - Warn when using a version of libevent before 1.3b to run a server on
23537 OSX or BSD: these versions interact badly with userspace threads.
23540 Changes in version 0.1.2.13 - 2007-04-24
23541 This release features some major anonymity fixes, such as safer path
23542 selection; better client performance; faster bootstrapping, better
23543 address detection, and better DNS support for servers; write limiting as
23544 well as read limiting to make servers easier to run; and a huge pile of
23545 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
23547 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
23548 of the Freenode IRC network, remembering his patience and vision for
23549 free speech on the Internet.
23552 - Fix a memory leak when we ask for "all" networkstatuses and we
23553 get one we don't recognize.
23554 - Add more asserts to hunt down bug 417.
23555 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
23558 Changes in version 0.1.2.12-rc - 2007-03-16
23560 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
23561 directory information requested inside Tor connections (i.e. via
23562 begin_dir cells). It only triggered when the same connection was
23563 serving other data at the same time. Reported by seeess.
23566 - When creating a circuit via the controller, send a 'launched'
23567 event when we're done, so we follow the spec better.
23570 Changes in version 0.1.2.11-rc - 2007-03-15
23571 o Minor bugfixes (controller), reported by daejees:
23572 - Correct the control spec to match how the code actually responds
23573 to 'getinfo addr-mappings/*'.
23574 - The control spec described a GUARDS event, but the code
23575 implemented a GUARD event. Standardize on GUARD, but let people
23576 ask for GUARDS too.
23579 Changes in version 0.1.2.10-rc - 2007-03-07
23580 o Major bugfixes (Windows):
23581 - Do not load the NT services library functions (which may not exist)
23582 just to detect if we're a service trying to shut down. Now we run
23583 on Win98 and friends again.
23585 o Minor bugfixes (other):
23586 - Clarify a couple of log messages.
23587 - Fix a misleading socks5 error number.
23590 Changes in version 0.1.2.9-rc - 2007-03-02
23591 o Major bugfixes (Windows):
23592 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
23593 of the usual GCC "%llu". This prevents a bug when saving 64-bit
23594 int configuration values: the high-order 32 bits would get
23595 truncated. In particular, we were being bitten by the default
23596 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
23597 and maybe also bug 397.)
23599 o Minor bugfixes (performance):
23600 - Use OpenSSL's AES implementation on platforms where it's faster.
23601 This could save us as much as 10% CPU usage.
23603 o Minor bugfixes (server):
23604 - Do not rotate onion key immediately after setting it for the first
23607 o Minor bugfixes (directory authorities):
23608 - Stop calling servers that have been hibernating for a long time
23609 "stable". Also, stop letting hibernating or obsolete servers affect
23610 uptime and bandwidth cutoffs.
23611 - Stop listing hibernating servers in the v1 directory.
23613 o Minor bugfixes (hidden services):
23614 - Upload hidden service descriptors slightly less often, to reduce
23615 load on authorities.
23617 o Minor bugfixes (other):
23618 - Fix an assert that could trigger if a controller quickly set then
23619 cleared EntryNodes. Bug found by Udo van den Heuvel.
23620 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
23622 - Fix a potential race condition in the rpm installer. Found by
23624 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
23625 of 2 as indicating that the server is completely bad; it sometimes
23626 means that the server is just bad for the request in question. (may fix
23627 the last of bug 326.)
23628 - Disable encrypted directory connections when we don't have a server
23629 descriptor for the destination. We'll get this working again in
23633 Changes in version 0.1.2.8-beta - 2007-02-26
23634 o Major bugfixes (crashes):
23635 - Stop crashing when the controller asks us to resetconf more than
23636 one config option at once. (Vidalia 0.0.11 does this.)
23637 - Fix a crash that happened on Win98 when we're given command-line
23638 arguments: don't try to load NT service functions from advapi32.dll
23639 except when we need them. (Bug introduced in 0.1.2.7-alpha;
23641 - Fix a longstanding obscure crash bug that could occur when
23642 we run out of DNS worker processes. (Resolves bug 390.)
23644 o Major bugfixes (hidden services):
23645 - Correctly detect whether hidden service descriptor downloads are
23646 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
23648 o Major bugfixes (accounting):
23649 - When we start during an accounting interval before it's time to wake
23650 up, remember to wake up at the correct time. (May fix bug 342.)
23652 o Minor bugfixes (controller):
23653 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
23654 clear the corresponding on_circuit variable, and remember later
23655 that we don't need to send a redundant CLOSED event. Resolves part
23657 - Report events where a resolve succeeded or where we got a socks
23658 protocol error correctly, rather than calling both of them
23660 - Change reported stream target addresses to IP consistently when
23661 we finally get the IP from an exit node.
23662 - Send log messages to the controller even if they happen to be very
23665 o Minor bugfixes (other):
23666 - Display correct results when reporting which versions are
23667 recommended, and how recommended they are. (Resolves bug 383.)
23668 - Improve our estimates for directory bandwidth to be less random:
23669 guess that an unrecognized directory will have the average bandwidth
23670 from all known directories, not that it will have the average
23671 bandwidth from those directories earlier than it on the list.
23672 - If we start a server with ClientOnly 1, then set ClientOnly to 0
23673 and hup, stop triggering an assert based on an empty onion_key.
23674 - On platforms with no working mmap() equivalent, don't warn the
23675 user when cached-routers doesn't exist.
23676 - Warn the user when mmap() [or its equivalent] fails for some reason
23677 other than file-not-found.
23678 - Don't warn the user when cached-routers.new doesn't exist: that's
23679 perfectly fine when starting up for the first time.
23680 - When EntryNodes are configured, rebuild the guard list to contain,
23681 in order: the EntryNodes that were guards before; the rest of the
23682 EntryNodes; the nodes that were guards before.
23683 - Mask out all signals in sub-threads; only the libevent signal
23684 handler should be processing them. This should prevent some crashes
23685 on some machines using pthreads. (Patch from coderman.)
23686 - Fix switched arguments on memset in the implementation of
23687 tor_munmap() for systems with no mmap() call.
23688 - When Tor receives a router descriptor that it asked for, but
23689 no longer wants (because it has received fresh networkstatuses
23690 in the meantime), do not warn the user. Cache the descriptor if
23691 we're a cache; drop it if we aren't.
23692 - Make earlier entry guards _really_ get retried when the network
23694 - On a malformed DNS reply, always give an error to the corresponding
23696 - Build with recent libevents on platforms that do not define the
23697 nonstandard types "u_int8_t" and friends.
23699 o Minor features (controller):
23700 - Warn the user when an application uses the obsolete binary v0
23701 control protocol. We're planning to remove support for it during
23702 the next development series, so it's good to give people some
23704 - Add STREAM_BW events to report per-entry-stream bandwidth
23705 use. (Patch from Robert Hogan.)
23706 - Rate-limit SIGNEWNYM signals in response to controllers that
23707 impolitely generate them for every single stream. (Patch from
23708 mwenge; closes bug 394.)
23709 - Make REMAP stream events have a SOURCE (cache or exit), and
23710 make them generated in every case where we get a successful
23711 connected or resolved cell.
23713 o Minor bugfixes (performance):
23714 - Call router_have_min_dir_info half as often. (This is showing up in
23715 some profiles, but not others.)
23716 - When using GCC, make log_debug never get called at all, and its
23717 arguments never get evaluated, when no debug logs are configured.
23718 (This is showing up in some profiles, but not others.)
23721 - Remove some never-implemented options. Mark PathlenCoinWeight as
23723 - Implement proposal 106: Stop requiring clients to have well-formed
23724 certificates; stop checking nicknames in certificates. (Clients
23725 have certificates so that they can look like Tor servers, but in
23726 the future we might want to allow them to look like regular TLS
23727 clients instead. Nicknames in certificates serve no purpose other
23728 than making our protocol easier to recognize on the wire.)
23729 - Revise messages on handshake failure again to be even more clear about
23730 which are incoming connections and which are outgoing.
23731 - Discard any v1 directory info that's over 1 month old (for
23732 directories) or over 1 week old (for running-routers lists).
23733 - Do not warn when individual nodes in the configuration's EntryNodes,
23734 ExitNodes, etc are down: warn only when all possible nodes
23735 are down. (Fixes bug 348.)
23736 - Always remove expired routers and networkstatus docs before checking
23737 whether we have enough information to build circuits. (Fixes
23739 - Put a lower-bound on MaxAdvertisedBandwidth.
23742 Changes in version 0.1.2.7-alpha - 2007-02-06
23743 o Major bugfixes (rate limiting):
23744 - Servers decline directory requests much more aggressively when
23745 they're low on bandwidth. Otherwise they end up queueing more and
23746 more directory responses, which can't be good for latency.
23747 - But never refuse directory requests from local addresses.
23748 - Fix a memory leak when sending a 503 response for a networkstatus
23750 - Be willing to read or write on local connections (e.g. controller
23751 connections) even when the global rate limiting buckets are empty.
23752 - If our system clock jumps back in time, don't publish a negative
23753 uptime in the descriptor. Also, don't let the global rate limiting
23754 buckets go absurdly negative.
23755 - Flush local controller connection buffers periodically as we're
23756 writing to them, so we avoid queueing 4+ megabytes of data before
23759 o Major bugfixes (NT services):
23760 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
23761 command-line flag so that admins can override the default by saying
23762 "tor --service install --user "SomeUser"". This will not affect
23763 existing installed services. Also, warn the user that the service
23764 will look for its configuration file in the service user's
23765 %appdata% directory. (We can't do the 'hardwire the user's appdata
23766 directory' trick any more, since we may not have read access to that
23769 o Major bugfixes (other):
23770 - Previously, we would cache up to 16 old networkstatus documents
23771 indefinitely, if they came from nontrusted authorities. Now we
23772 discard them if they are more than 10 days old.
23773 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
23775 - Detect and reject malformed DNS responses containing circular
23777 - If exits are rare enough that we're not marking exits as guards,
23778 ignore exit bandwidth when we're deciding the required bandwidth
23780 - When we're handling a directory connection tunneled over Tor,
23781 don't fill up internal memory buffers with all the data we want
23782 to tunnel; instead, only add it if the OR connection that will
23783 eventually receive it has some room for it. (This can lead to
23784 slowdowns in tunneled dir connections; a better solution will have
23785 to wait for 0.2.0.)
23787 o Minor bugfixes (dns):
23788 - Add some defensive programming to eventdns.c in an attempt to catch
23789 possible memory-stomping bugs.
23790 - Detect and reject DNS replies containing IPv4 or IPv6 records with
23791 an incorrect number of bytes. (Previously, we would ignore the
23793 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
23794 in the correct order, and doesn't crash.
23795 - Free memory held in recently-completed DNS lookup attempts on exit.
23796 This was not a memory leak, but may have been hiding memory leaks.
23797 - Handle TTL values correctly on reverse DNS lookups.
23798 - Treat failure to parse resolv.conf as an error.
23800 o Minor bugfixes (other):
23801 - Fix crash with "tor --list-fingerprint" (reported by seeess).
23802 - When computing clock skew from directory HTTP headers, consider what
23803 time it was when we finished asking for the directory, not what
23805 - Expire socks connections if they spend too long waiting for the
23806 handshake to finish. Previously we would let them sit around for
23807 days, if the connecting application didn't close them either.
23808 - And if the socks handshake hasn't started, don't send a
23809 "DNS resolve socks failed" handshake reply; just close it.
23810 - Stop using C functions that OpenBSD's linker doesn't like.
23811 - Don't launch requests for descriptors unless we have networkstatuses
23812 from at least half of the authorities. This delays the first
23813 download slightly under pathological circumstances, but can prevent
23814 us from downloading a bunch of descriptors we don't need.
23815 - Do not log IPs with TLS failures for incoming TLS
23816 connections. (Fixes bug 382.)
23817 - If the user asks to use invalid exit nodes, be willing to use
23819 - Stop using the reserved ac_cv namespace in our configure script.
23820 - Call stat() slightly less often; use fstat() when possible.
23821 - Refactor the way we handle pending circuits when an OR connection
23822 completes or fails, in an attempt to fix a rare crash bug.
23823 - Only rewrite a conn's address based on X-Forwarded-For: headers
23824 if it's a parseable public IP address; and stop adding extra quotes
23825 to the resulting address.
23828 - Weight directory requests by advertised bandwidth. Now we can
23829 let servers enable write limiting but still allow most clients to
23830 succeed at their directory requests. (We still ignore weights when
23831 choosing a directory authority; I hope this is a feature.)
23834 - Create a new file ReleaseNotes which was the old ChangeLog. The
23835 new ChangeLog file now includes the summaries for all development
23837 - Check for addresses with invalid characters at the exit as well
23838 as at the client, and warn less verbosely when they fail. You can
23839 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
23840 - Adapt a patch from goodell to let the contrib/exitlist script
23841 take arguments rather than require direct editing.
23842 - Inform the server operator when we decide not to advertise a
23843 DirPort due to AccountingMax enabled or a low BandwidthRate. It
23844 was confusing Zax, so now we're hopefully more helpful.
23845 - Bring us one step closer to being able to establish an encrypted
23846 directory tunnel without knowing a descriptor first. Still not
23847 ready yet. As part of the change, now assume we can use a
23848 create_fast cell if we don't know anything about a router.
23849 - Allow exit nodes to use nameservers running on ports other than 53.
23850 - Servers now cache reverse DNS replies.
23851 - Add an --ignore-missing-torrc command-line option so that we can
23852 get the "use sensible defaults if the configuration file doesn't
23853 exist" behavior even when specifying a torrc location on the command
23856 o Minor features (controller):
23857 - Track reasons for OR connection failure; make these reasons
23858 available via the controller interface. (Patch from Mike Perry.)
23859 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
23860 can learn when clients are sending malformed hostnames to Tor.
23861 - Clean up documentation for controller status events.
23862 - Add a REMAP status to stream events to note that a stream's
23863 address has changed because of a cached address or a MapAddress
23867 Changes in version 0.1.2.6-alpha - 2007-01-09
23869 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
23870 connection handles more than 4 gigs in either direction, we crash.
23871 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
23872 advertised exit node, somebody might try to exit from us when
23873 we're bootstrapping and before we've built our descriptor yet.
23874 Refuse the connection rather than crashing.
23877 - Warn if we (as a server) find that we've resolved an address that we
23878 weren't planning to resolve.
23879 - Warn that using select() on any libevent version before 1.1 will be
23880 unnecessarily slow (even for select()).
23881 - Flush ERR-level controller status events just like we currently
23882 flush ERR-level log events, so that a Tor shutdown doesn't prevent
23883 the controller from learning about current events.
23885 o Minor features (more controller status events):
23886 - Implement EXTERNAL_ADDRESS server status event so controllers can
23887 learn when our address changes.
23888 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
23889 can learn when directories reject our descriptor.
23890 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
23891 can learn when a client application is speaking a non-socks protocol
23893 - Implement DANGEROUS_SOCKS client status event so controllers
23894 can learn when a client application is leaking DNS addresses.
23895 - Implement BUG general status event so controllers can learn when
23896 Tor is unhappy about its internal invariants.
23897 - Implement CLOCK_SKEW general status event so controllers can learn
23898 when Tor thinks the system clock is set incorrectly.
23899 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
23900 server status events so controllers can learn when their descriptors
23901 are accepted by a directory.
23902 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
23903 server status events so controllers can learn about Tor's progress in
23904 deciding whether it's reachable from the outside.
23905 - Implement BAD_LIBEVENT general status event so controllers can learn
23906 when we have a version/method combination in libevent that needs to
23908 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
23909 and DNS_USELESS server status events so controllers can learn
23910 about changes to DNS server status.
23912 o Minor features (directory):
23913 - Authorities no longer recommend exits as guards if this would shift
23914 too much load to the exit nodes.
23917 Changes in version 0.1.2.5-alpha - 2007-01-06
23919 - Enable write limiting as well as read limiting. Now we sacrifice
23920 capacity if we're pushing out lots of directory traffic, rather
23921 than overrunning the user's intended bandwidth limits.
23922 - Include TLS overhead when counting bandwidth usage; previously, we
23923 would count only the bytes sent over TLS, but not the bytes used
23925 - Support running the Tor service with a torrc not in the same
23926 directory as tor.exe and default to using the torrc located in
23927 the %appdata%\Tor\ of the user who installed the service. Patch
23929 - Servers now check for the case when common DNS requests are going to
23930 wildcarded addresses (i.e. all getting the same answer), and change
23931 their exit policy to reject *:* if it's happening.
23932 - Implement BEGIN_DIR cells, so we can connect to the directory
23933 server via TLS to do encrypted directory requests rather than
23934 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
23935 config options if you like.
23937 o Minor features (config and docs):
23938 - Start using the state file to store bandwidth accounting data:
23939 the bw_accounting file is now obsolete. We'll keep generating it
23940 for a while for people who are still using 0.1.2.4-alpha.
23941 - Try to batch changes to the state file so that we do as few
23942 disk writes as possible while still storing important things in
23944 - The state file and the bw_accounting file get saved less often when
23945 the AvoidDiskWrites config option is set.
23946 - Make PIDFile work on Windows (untested).
23947 - Add internal descriptions for a bunch of configuration options:
23948 accessible via controller interface and in comments in saved
23950 - Reject *:563 (NNTPS) in the default exit policy. We already reject
23951 NNTP by default, so this seems like a sensible addition.
23952 - Clients now reject hostnames with invalid characters. This should
23953 avoid some inadvertent info leaks. Add an option
23954 AllowNonRFC953Hostnames to disable this behavior, in case somebody
23955 is running a private network with hosts called @, !, and #.
23956 - Add a maintainer script to tell us which options are missing
23957 documentation: "make check-docs".
23958 - Add a new address-spec.txt document to describe our special-case
23959 addresses: .exit, .onion, and .noconnnect.
23961 o Minor features (DNS):
23962 - Ongoing work on eventdns infrastructure: now it has dns server
23963 and ipv6 support. One day Tor will make use of it.
23964 - Add client-side caching for reverse DNS lookups.
23965 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
23966 - When we change nameservers or IP addresses, reset and re-launch
23967 our tests for DNS hijacking.
23969 o Minor features (directory):
23970 - Authorities now specify server versions in networkstatus. This adds
23971 about 2% to the size of compressed networkstatus docs, and allows
23972 clients to tell which servers support BEGIN_DIR and which don't.
23973 The implementation is forward-compatible with a proposed future
23974 protocol version scheme not tied to Tor versions.
23975 - DirServer configuration lines now have an orport= option so
23976 clients can open encrypted tunnels to the authorities without
23977 having downloaded their descriptors yet. Enabled for moria1,
23978 moria2, tor26, and lefkada now in the default configuration.
23979 - Directory servers are more willing to send a 503 "busy" if they
23980 are near their write limit, especially for v1 directory requests.
23981 Now they can use their limited bandwidth for actual Tor traffic.
23982 - Clients track responses with status 503 from dirservers. After a
23983 dirserver has given us a 503, we try not to use it until an hour has
23984 gone by, or until we have no dirservers that haven't given us a 503.
23985 - When we get a 503 from a directory, and we're not a server, we don't
23986 count the failure against the total number of failures allowed
23987 for the thing we're trying to download.
23988 - Report X-Your-Address-Is correctly from tunneled directory
23989 connections; don't report X-Your-Address-Is when it's an internal
23990 address; and never believe reported remote addresses when they're
23992 - Protect against an unlikely DoS attack on directory servers.
23993 - Add a BadDirectory flag to network status docs so that authorities
23994 can (eventually) tell clients about caches they believe to be
23997 o Minor features (controller):
23998 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
23999 - Reimplement GETINFO so that info/names stays in sync with the
24001 - Implement "GETINFO fingerprint".
24002 - Implement "SETEVENTS GUARD" so controllers can get updates on
24003 entry guard status as it changes.
24005 o Minor features (clean up obsolete pieces):
24006 - Remove some options that have been deprecated since at least
24007 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
24008 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
24009 to set log options.
24010 - We no longer look for identity and onion keys in "identity.key" and
24011 "onion.key" -- these were replaced by secret_id_key and
24012 secret_onion_key in 0.0.8pre1.
24013 - We no longer require unrecognized directory entries to be
24016 o Major bugfixes (security):
24017 - Stop sending the HttpProxyAuthenticator string to directory
24018 servers when directory connections are tunnelled through Tor.
24019 - Clients no longer store bandwidth history in the state file.
24020 - Do not log introduction points for hidden services if SafeLogging
24022 - When generating bandwidth history, round down to the nearest
24023 1k. When storing accounting data, round up to the nearest 1k.
24024 - When we're running as a server, remember when we last rotated onion
24025 keys, so that we will rotate keys once they're a week old even if
24026 we never stay up for a week ourselves.
24028 o Major bugfixes (other):
24029 - Fix a longstanding bug in eventdns that prevented the count of
24030 timed-out resolves from ever being reset. This bug caused us to
24031 give up on a nameserver the third time it timed out, and try it
24032 10 seconds later... and to give up on it every time it timed out
24034 - Take out the '5 second' timeout from the connection retry
24035 schedule. Now the first connect attempt will wait a full 10
24036 seconds before switching to a new circuit. Perhaps this will help
24037 a lot. Based on observations from Mike Perry.
24038 - Fix a bug on the Windows implementation of tor_mmap_file() that
24039 would prevent the cached-routers file from ever loading. Reported
24043 - Fix an assert failure when a directory authority sets
24044 AuthDirRejectUnlisted and then receives a descriptor from an
24045 unlisted router. Reported by seeess.
24046 - Avoid a double-free when parsing malformed DirServer lines.
24047 - Fix a bug when a BSD-style PF socket is first used. Patch from
24049 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
24050 to resolve an address at a given exit node even when they ask for
24052 - Servers no longer ever list themselves in their "family" line,
24053 even if configured to do so. This makes it easier to configure
24054 family lists conveniently.
24055 - When running as a server, don't fall back to 127.0.0.1 when no
24056 nameservers are configured in /etc/resolv.conf; instead, make the
24057 user fix resolv.conf or specify nameservers explicitly. (Resolves
24059 - Stop accepting certain malformed ports in configured exit policies.
24060 - Don't re-write the fingerprint file every restart, unless it has
24062 - Stop warning when a single nameserver fails: only warn when _all_ of
24063 our nameservers have failed. Also, when we only have one nameserver,
24064 raise the threshold for deciding that the nameserver is dead.
24065 - Directory authorities now only decide that routers are reachable
24066 if their identity keys are as expected.
24067 - When the user uses bad syntax in the Log config line, stop
24068 suggesting other bad syntax as a replacement.
24069 - Correctly detect ipv6 DNS capability on OpenBSD.
24071 o Minor bugfixes (controller):
24072 - Report the circuit number correctly in STREAM CLOSED events. Bug
24073 reported by Mike Perry.
24074 - Do not report bizarre values for results of accounting GETINFOs
24075 when the last second's write or read exceeds the allotted bandwidth.
24076 - Report "unrecognized key" rather than an empty string when the
24077 controller tries to fetch a networkstatus that doesn't exist.
24080 Changes in version 0.1.1.26 - 2006-12-14
24081 o Security bugfixes:
24082 - Stop sending the HttpProxyAuthenticator string to directory
24083 servers when directory connections are tunnelled through Tor.
24084 - Clients no longer store bandwidth history in the state file.
24085 - Do not log introduction points for hidden services if SafeLogging
24089 - Fix an assert failure when a directory authority sets
24090 AuthDirRejectUnlisted and then receives a descriptor from an
24091 unlisted router (reported by seeess).
24094 Changes in version 0.1.2.4-alpha - 2006-12-03
24096 - Add support for using natd; this allows FreeBSDs earlier than
24097 5.1.2 to have ipfw send connections through Tor without using
24098 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
24101 - Make all connections to addresses of the form ".noconnect"
24102 immediately get closed. This lets application/controller combos
24103 successfully test whether they're talking to the same Tor by
24104 watching for STREAM events.
24105 - Make cross.sh cross-compilation script work even when autogen.sh
24106 hasn't been run. (Patch from Michael Mohr.)
24107 - Statistics dumped by -USR2 now include a breakdown of public key
24108 operations, for profiling.
24111 - Fix a major leak when directory authorities parse their
24112 approved-routers list, a minor memory leak when we fail to pick
24113 an exit node, and a few rare leaks on errors.
24114 - Handle TransPort connections even when the server sends data before
24115 the client sends data. Previously, the connection would just hang
24116 until the client sent data. (Patch from tup based on patch from
24118 - Avoid assert failure when our cached-routers file is empty on
24122 - Don't log spurious warnings when we see a circuit close reason we
24123 don't recognize; it's probably just from a newer version of Tor.
24124 - Have directory authorities allow larger amounts of drift in uptime
24125 without replacing the server descriptor: previously, a server that
24126 restarted every 30 minutes could have 48 "interesting" descriptors
24128 - Start linking to the Tor specification and Tor reference manual
24129 correctly in the Windows installer.
24130 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24131 Tor/Privoxy we also uninstall Vidalia.
24132 - Resume building on Irix64, and fix a lot of warnings from its
24133 MIPSpro C compiler.
24134 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
24135 when we're running as a client.
24138 Changes in version 0.1.1.25 - 2006-11-04
24140 - When a client asks us to resolve (rather than connect to)
24141 an address, and we have a cached answer, give them the cached
24142 answer. Previously, we would give them no answer at all.
24143 - We were building exactly the wrong circuits when we predict
24144 hidden service requirements, meaning Tor would have to build all
24145 its circuits on demand.
24146 - If none of our live entry guards have a high uptime, but we
24147 require a guard with a high uptime, try adding a new guard before
24148 we give up on the requirement. This patch should make long-lived
24149 connections more stable on average.
24150 - When testing reachability of our DirPort, don't launch new
24151 tests when there's already one in progress -- unreachable
24152 servers were stacking up dozens of testing streams.
24154 o Security bugfixes:
24155 - When the user sends a NEWNYM signal, clear the client-side DNS
24156 cache too. Otherwise we continue to act on previous information.
24159 - Avoid a memory corruption bug when creating a hash table for
24161 - Avoid possibility of controller-triggered crash when misusing
24162 certain commands from a v0 controller on platforms that do not
24163 handle printf("%s",NULL) gracefully.
24164 - Avoid infinite loop on unexpected controller input.
24165 - Don't log spurious warnings when we see a circuit close reason we
24166 don't recognize; it's probably just from a newer version of Tor.
24167 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24168 Tor/Privoxy we also uninstall Vidalia.
24171 Changes in version 0.1.2.3-alpha - 2006-10-29
24173 - Prepare for servers to publish descriptors less often: never
24174 discard a descriptor simply for being too old until either it is
24175 recommended by no authorities, or until we get a better one for
24176 the same router. Make caches consider retaining old recommended
24177 routers for even longer.
24178 - If most authorities set a BadExit flag for a server, clients
24179 don't think of it as a general-purpose exit. Clients only consider
24180 authorities that advertise themselves as listing bad exits.
24181 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
24182 headers for content, so that we can work better in the presence of
24183 caching HTTP proxies.
24184 - Allow authorities to list nodes as bad exits by fingerprint or by
24187 o Minor features, controller:
24188 - Add a REASON field to CIRC events; for backward compatibility, this
24189 field is sent only to controllers that have enabled the extended
24190 event format. Also, add additional reason codes to explain why
24191 a given circuit has been destroyed or truncated. (Patches from
24193 - Add a REMOTE_REASON field to extended CIRC events to tell the
24194 controller about why a remote OR told us to close a circuit.
24195 - Stream events also now have REASON and REMOTE_REASON fields,
24196 working much like those for circuit events.
24197 - There's now a GETINFO ns/... field so that controllers can ask Tor
24198 about the current status of a router.
24199 - A new event type "NS" to inform a controller when our opinion of
24200 a router's status has changed.
24201 - Add a GETINFO events/names and GETINFO features/names so controllers
24202 can tell which events and features are supported.
24203 - A new CLEARDNSCACHE signal to allow controllers to clear the
24204 client-side DNS cache without expiring circuits.
24206 o Security bugfixes:
24207 - When the user sends a NEWNYM signal, clear the client-side DNS
24208 cache too. Otherwise we continue to act on previous information.
24211 - Avoid sending junk to controllers or segfaulting when a controller
24212 uses EVENT_NEW_DESC with verbose nicknames.
24213 - Stop triggering asserts if the controller tries to extend hidden
24214 service circuits (reported by mwenge).
24215 - Avoid infinite loop on unexpected controller input.
24216 - When the controller does a "GETINFO network-status", tell it
24217 about even those routers whose descriptors are very old, and use
24218 long nicknames where appropriate.
24219 - Change NT service functions to be loaded on demand. This lets us
24220 build with MinGW without breaking Tor for Windows 98 users.
24221 - Do DirPort reachability tests less often, since a single test
24222 chews through many circuits before giving up.
24223 - In the hidden service example in torrc.sample, stop recommending
24224 esoteric and discouraged hidden service options.
24225 - When stopping an NT service, wait up to 10 sec for it to actually
24226 stop. Patch from Matt Edman; resolves bug 295.
24227 - Fix handling of verbose nicknames with ORCONN controller events:
24228 make them show up exactly when requested, rather than exactly when
24230 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
24231 printing a duplicate "$" in the keys we send (reported by mwenge).
24232 - Correctly set maximum connection limit on Cygwin. (This time
24234 - Try to detect Windows correctly when cross-compiling.
24235 - Detect the size of the routers file correctly even if it is
24236 corrupted (on systems without mmap) or not page-aligned (on systems
24237 with mmap). This bug was harmless.
24238 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
24239 to open a stream fails; now we do in more cases. This should
24240 make clients able to find a good exit faster in some cases, since
24241 unhandleable requests will now get an error rather than timing out.
24242 - Resolve two memory leaks when rebuilding the on-disk router cache
24243 (reported by fookoowa).
24244 - Clean up minor code warnings suggested by the MIPSpro C compiler,
24245 and reported by some Centos users.
24246 - Controller signals now work on non-Unix platforms that don't define
24247 SIGUSR1 and SIGUSR2 the way we expect.
24248 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
24249 values before failing, and always enables eventdns.
24250 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
24251 Try to fix this in configure.in by checking for most functions
24252 before we check for libevent.
24255 Changes in version 0.1.2.2-alpha - 2006-10-07
24257 - Make our async eventdns library on-by-default for Tor servers,
24258 and plan to deprecate the separate dnsworker threads.
24259 - Add server-side support for "reverse" DNS lookups (using PTR
24260 records so clients can determine the canonical hostname for a given
24261 IPv4 address). Only supported by servers using eventdns; servers
24262 now announce in their descriptors whether they support eventdns.
24263 - Specify and implement client-side SOCKS5 interface for reverse DNS
24264 lookups (see doc/socks-extensions.txt).
24265 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
24266 connect to directory servers through Tor. Previously, clients needed
24267 to find Tor exits to make private connections to directory servers.
24268 - Avoid choosing Exit nodes for entry or middle hops when the
24269 total bandwidth available from non-Exit nodes is much higher than
24270 the total bandwidth available from Exit nodes.
24271 - Workaround for name servers (like Earthlink's) that hijack failing
24272 DNS requests and replace the no-such-server answer with a "helpful"
24273 redirect to an advertising-driven search portal. Also work around
24274 DNS hijackers who "helpfully" decline to hijack known-invalid
24275 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
24276 lets you turn it off.
24277 - Send out a burst of long-range padding cells once we've established
24278 that we're reachable. Spread them over 4 circuits, so hopefully
24279 a few will be fast. This exercises our bandwidth and bootstraps
24280 us into the directory more quickly.
24282 o New/improved config options:
24283 - Add new config option "ResolvConf" to let the server operator
24284 choose an alternate resolve.conf file when using eventdns.
24285 - Add an "EnforceDistinctSubnets" option to control our "exclude
24286 servers on the same /16" behavior. It's still on by default; this
24287 is mostly for people who want to operate private test networks with
24288 all the machines on the same subnet.
24289 - If one of our entry guards is on the ExcludeNodes list, or the
24290 directory authorities don't think it's a good guard, treat it as
24291 if it were unlisted: stop using it as a guard, and throw it off
24292 the guards list if it stays that way for a long time.
24293 - Allow directory authorities to be marked separately as authorities
24294 for the v1 directory protocol, the v2 directory protocol, and
24295 as hidden service directories, to make it easier to retire old
24296 authorities. V1 authorities should set "HSAuthoritativeDir 1"
24297 to continue being hidden service authorities too.
24298 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
24300 o Minor features, controller:
24301 - Fix CIRC controller events so that controllers can learn the
24302 identity digests of non-Named servers used in circuit paths.
24303 - Let controllers ask for more useful identifiers for servers. Instead
24304 of learning identity digests for un-Named servers and nicknames
24305 for Named servers, the new identifiers include digest, nickname,
24306 and indication of Named status. Off by default; see control-spec.txt
24307 for more information.
24308 - Add a "getinfo address" controller command so it can display Tor's
24309 best guess to the user.
24310 - New controller event to alert the controller when our server
24311 descriptor has changed.
24312 - Give more meaningful errors on controller authentication failure.
24314 o Minor features, other:
24315 - When asked to resolve a hostname, don't use non-exit servers unless
24316 requested to do so. This allows servers with broken DNS to be
24317 useful to the network.
24318 - Divide eventdns log messages into warn and info messages.
24319 - Reserve the nickname "Unnamed" for routers that can't pick
24320 a hostname: any router can call itself Unnamed; directory
24321 authorities will never allocate Unnamed to any particular router;
24322 clients won't believe that any router is the canonical Unnamed.
24323 - Only include function names in log messages for info/debug messages.
24324 For notice/warn/err, the content of the message should be clear on
24325 its own, and printing the function name only confuses users.
24326 - Avoid some false positives during reachability testing: don't try
24327 to test via a server that's on the same /24 as us.
24328 - If we fail to build a circuit to an intended enclave, and it's
24329 not mandatory that we use that enclave, stop wanting it.
24330 - When eventdns is enabled, allow multithreaded builds on NetBSD and
24331 OpenBSD. (We had previously disabled threads on these platforms
24332 because they didn't have working thread-safe resolver functions.)
24334 o Major bugfixes, anonymity/security:
24335 - If a client asked for a server by name, and there's a named server
24336 in our network-status but we don't have its descriptor yet, we
24337 could return an unnamed server instead.
24338 - Fix NetBSD bug that could allow someone to force uninitialized RAM
24339 to be sent to a server's DNS resolver. This only affects NetBSD
24340 and other platforms that do not bounds-check tolower().
24341 - Reject (most) attempts to use Tor circuits with length one. (If
24342 many people start using Tor as a one-hop proxy, exit nodes become
24343 a more attractive target for compromise.)
24344 - Just because your DirPort is open doesn't mean people should be
24345 able to remotely teach you about hidden service descriptors. Now
24346 only accept rendezvous posts if you've got HSAuthoritativeDir set.
24348 o Major bugfixes, other:
24349 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
24350 - When a client asks the server to resolve (not connect to)
24351 an address, and it has a cached answer, give them the cached answer.
24352 Previously, the server would give them no answer at all.
24353 - Allow really slow clients to not hang up five minutes into their
24354 directory downloads (suggested by Adam J. Richter).
24355 - We were building exactly the wrong circuits when we anticipated
24356 hidden service requirements, meaning Tor would have to build all
24357 its circuits on demand.
24358 - Avoid crashing when we mmap a router cache file of size 0.
24359 - When testing reachability of our DirPort, don't launch new
24360 tests when there's already one in progress -- unreachable
24361 servers were stacking up dozens of testing streams.
24363 o Minor bugfixes, correctness:
24364 - If we're a directory mirror and we ask for "all" network status
24365 documents, we would discard status documents from authorities
24366 we don't recognize.
24367 - Avoid a memory corruption bug when creating a hash table for
24369 - Avoid controller-triggered crash when misusing certain commands
24370 from a v0 controller on platforms that do not handle
24371 printf("%s",NULL) gracefully.
24372 - Don't crash when a controller sends a third argument to an
24373 "extendcircuit" request.
24374 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
24375 response; fix error code when "getinfo dir/status/" fails.
24376 - Avoid crash when telling controller stream-status and a stream
24378 - Patch from Adam Langley to fix assert() in eventdns.c.
24379 - Fix a debug log message in eventdns to say "X resolved to Y"
24380 instead of "X resolved to X".
24381 - Make eventdns give strings for DNS errors, not just error numbers.
24382 - Track unreachable entry guards correctly: don't conflate
24383 'unreachable by us right now' with 'listed as down by the directory
24384 authorities'. With the old code, if a guard was unreachable by
24385 us but listed as running, it would clog our guard list forever.
24386 - Behave correctly in case we ever have a network with more than
24387 2GB/s total advertised capacity.
24388 - Make TrackExitHosts case-insensitive, and fix the behavior of
24389 ".suffix" TrackExitHosts items to avoid matching in the middle of
24391 - Finally fix the openssl warnings from newer gccs that believe that
24392 ignoring a return value is okay, but casting a return value and
24393 then ignoring it is a sign of madness.
24394 - Prevent the contrib/exitlist script from printing the same
24395 result more than once.
24396 - Patch from Steve Hildrey: Generate network status correctly on
24397 non-versioning dirservers.
24398 - Don't listen to the X-Your-Address-Is hint if you did the lookup
24399 via Tor; otherwise you'll think you're the exit node's IP address.
24401 o Minor bugfixes, performance:
24402 - Two small performance improvements on parsing descriptors.
24403 - Major performance improvement on inserting descriptors: change
24404 algorithm from O(n^2) to O(n).
24405 - Make the common memory allocation path faster on machines where
24406 malloc(0) returns a pointer.
24407 - Start remembering X-Your-Address-Is directory hints even if you're
24408 a client, so you can become a server more smoothly.
24409 - Avoid duplicate entries on MyFamily line in server descriptor.
24411 o Packaging, features:
24412 - Remove architecture from OS X builds. The official builds are
24413 now universal binaries.
24414 - The Debian package now uses --verify-config when (re)starting,
24415 to distinguish configuration errors from other errors.
24416 - Update RPMs to require libevent 1.1b.
24418 o Packaging, bugfixes:
24419 - Patches so Tor builds with MinGW on Windows.
24420 - Patches so Tor might run on Cygwin again.
24421 - Resume building on non-gcc compilers and ancient gcc. Resume
24422 building with the -O0 compile flag. Resume building cleanly on
24424 - Run correctly on OS X platforms with case-sensitive filesystems.
24425 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
24426 - Add autoconf checks so Tor can build on Solaris x86 again.
24429 - Documented (and renamed) ServerDNSSearchDomains and
24430 ServerDNSResolvConfFile options.
24431 - Be clearer that the *ListenAddress directives can be repeated
24435 Changes in version 0.1.1.24 - 2006-09-29
24437 - Allow really slow clients to not hang up five minutes into their
24438 directory downloads (suggested by Adam J. Richter).
24439 - Fix major performance regression from 0.1.0.x: instead of checking
24440 whether we have enough directory information every time we want to
24441 do something, only check when the directory information has changed.
24442 This should improve client CPU usage by 25-50%.
24443 - Don't crash if, after a server has been running for a while,
24444 it can't resolve its hostname.
24447 - Allow Tor to start when RunAsDaemon is set but no logs are set.
24448 - Don't crash when the controller receives a third argument to an
24449 "extendcircuit" request.
24450 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
24451 response; fix error code when "getinfo dir/status/" fails.
24452 - Fix configure.in to not produce broken configure files with
24453 more recent versions of autoconf. Thanks to Clint for his auto*
24455 - Fix security bug on NetBSD that could allow someone to force
24456 uninitialized RAM to be sent to a server's DNS resolver. This
24457 only affects NetBSD and other platforms that do not bounds-check
24459 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
24460 methods: these are known to be buggy.
24461 - If we're a directory mirror and we ask for "all" network status
24462 documents, we would discard status documents from authorities
24463 we don't recognize.
24466 Changes in version 0.1.2.1-alpha - 2006-08-27
24468 - Add "eventdns" async dns library from Adam Langley, tweaked to
24469 build on OSX and Windows. Only enabled if you pass the
24470 --enable-eventdns argument to configure.
24471 - Allow servers with no hostname or IP address to learn their
24472 IP address by asking the directory authorities. This code only
24473 kicks in when you would normally have exited with a "no address"
24474 error. Nothing's authenticated, so use with care.
24475 - Rather than waiting a fixed amount of time between retrying
24476 application connections, we wait only 5 seconds for the first,
24477 10 seconds for the second, and 15 seconds for each retry after
24478 that. Hopefully this will improve the expected user experience.
24479 - Patch from Tup to add support for transparent AP connections:
24480 this basically bundles the functionality of trans-proxy-tor
24481 into the Tor mainline. Now hosts with compliant pf/netfilter
24482 implementations can redirect TCP connections straight to Tor
24483 without diverting through SOCKS. Needs docs.
24484 - Busy directory servers save lots of memory by spooling server
24485 descriptors, v1 directories, and v2 networkstatus docs to buffers
24486 as needed rather than en masse. Also mmap the cached-routers
24487 files, so we don't need to keep the whole thing in memory too.
24488 - Automatically avoid picking more than one node from the same
24489 /16 network when constructing a circuit.
24490 - Revise and clean up the torrc.sample that we ship with; add
24491 a section for BandwidthRate and BandwidthBurst.
24494 - Split circuit_t into origin_circuit_t and or_circuit_t, and
24495 split connection_t into edge, or, dir, control, and base structs.
24496 These will save quite a bit of memory on busy servers, and they'll
24497 also help us track down bugs in the code and bugs in the spec.
24498 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
24499 or later. Log when we are doing this, so we can diagnose it when
24500 it fails. (Also, recommend libevent 1.1b for kqueue and
24501 win32 methods; deprecate libevent 1.0b harder; make libevent
24502 recommendation system saner.)
24503 - Start being able to build universal binaries on OS X (thanks
24505 - Export the default exit policy via the control port, so controllers
24506 don't need to guess what it is / will be later.
24507 - Add a man page entry for ProtocolWarnings.
24508 - Add TestVia config option to the man page.
24509 - Remove even more protocol-related warnings from Tor server logs,
24510 such as bad TLS handshakes and malformed begin cells.
24511 - Stop fetching descriptors if you're not a dir mirror and you
24512 haven't tried to establish any circuits lately. [This currently
24513 causes some dangerous behavior, because when you start up again
24514 you'll use your ancient server descriptors.]
24515 - New DirPort behavior: if you have your dirport set, you download
24516 descriptors aggressively like a directory mirror, whether or not
24517 your ORPort is set.
24518 - Get rid of the router_retry_connections notion. Now routers
24519 no longer try to rebuild long-term connections to directory
24520 authorities, and directory authorities no longer try to rebuild
24521 long-term connections to all servers. We still don't hang up
24522 connections in these two cases though -- we need to look at it
24523 more carefully to avoid flapping, and we likely need to wait til
24524 0.1.1.x is obsolete.
24525 - Drop compatibility with obsolete Tors that permit create cells
24526 to have the wrong circ_id_type.
24527 - Re-enable per-connection rate limiting. Get rid of the "OP
24528 bandwidth" concept. Lay groundwork for "bandwidth classes" --
24529 separate global buckets that apply depending on what sort of conn
24531 - Start publishing one minute or so after we find our ORPort
24532 to be reachable. This will help reduce the number of descriptors
24533 we have for ourselves floating around, since it's quite likely
24534 other things (e.g. DirPort) will change during that minute too.
24535 - Fork the v1 directory protocol into its own spec document,
24536 and mark dir-spec.txt as the currently correct (v2) spec.
24539 - When we find our DirPort to be reachable, publish a new descriptor
24540 so we'll tell the world (reported by pnx).
24541 - Publish a new descriptor after we hup/reload. This is important
24542 if our config has changed such that we'll want to start advertising
24543 our DirPort now, etc.
24544 - Allow Tor to start when RunAsDaemon is set but no logs are set.
24545 - When we have a state file we cannot parse, tell the user and
24546 move it aside. Now we avoid situations where the user starts
24547 Tor in 1904, Tor writes a state file with that timestamp in it,
24548 the user fixes her clock, and Tor refuses to start.
24549 - Fix configure.in to not produce broken configure files with
24550 more recent versions of autoconf. Thanks to Clint for his auto*
24552 - "tor --verify-config" now exits with -1(255) or 0 depending on
24553 whether the config options are bad or good.
24554 - Resolve bug 321 when using dnsworkers: append a period to every
24555 address we resolve at the exit node, so that we do not accidentally
24556 pick up local addresses, and so that failing searches are retried
24557 in the resolver search domains. (This is already solved for
24558 eventdns.) (This breaks Blossom servers for now.)
24559 - If we are using an exit enclave and we can't connect, e.g. because
24560 its webserver is misconfigured to not listen on localhost, then
24561 back off and try connecting from somewhere else before we fail.
24564 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
24565 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
24566 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
24567 when the IP address is mapped through MapAddress to a hostname.
24568 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
24569 useless IPv6 DNS resolves.
24570 - Patch suggested by Karsten Loesing: respond to SIGNAL command
24571 before we execute the signal, in case the signal shuts us down.
24572 - Clean up AllowInvalidNodes man page entry.
24573 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
24574 - Add more asserts to track down an assert error on a windows Tor
24575 server with connection_add being called with socket == -1.
24576 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
24577 - Fix misleading log messages: an entry guard that is "unlisted",
24578 as well as not known to be "down" (because we've never heard
24579 of it), is not therefore "up".
24580 - Remove code to special-case "-cvs" ending, since it has not
24581 actually mattered since 0.0.9.
24582 - Make our socks5 handling more robust to broken socks clients:
24583 throw out everything waiting on the buffer in between socks
24584 handshake phases, since they can't possibly (so the theory
24585 goes) have predicted what we plan to respond to them.
24588 Changes in version 0.1.1.23 - 2006-07-30
24590 - Fast Tor servers, especially exit nodes, were triggering asserts
24591 due to a bug in handling the list of pending DNS resolves. Some
24592 bugs still remain here; we're hunting them.
24593 - Entry guards could crash clients by sending unexpected input.
24594 - More fixes on reachability testing: if you find yourself reachable,
24595 then don't ever make any client requests (so you stop predicting
24596 circuits), then hup or have your clock jump, then later your IP
24597 changes, you won't think circuits are working, so you won't try to
24598 test reachability, so you won't publish.
24601 - Avoid a crash if the controller does a resetconf firewallports
24602 and then a setconf fascistfirewall=1.
24603 - Avoid an integer underflow when the dir authority decides whether
24604 a router is stable: we might wrongly label it stable, and compute
24605 a slightly wrong median stability, when a descriptor is published
24607 - Fix a place where we might trigger an assert if we can't build our
24608 own server descriptor yet.
24611 Changes in version 0.1.1.22 - 2006-07-05
24613 - Fix a big bug that was causing servers to not find themselves
24614 reachable if they changed IP addresses. Since only 0.1.1.22+
24615 servers can do reachability testing correctly, now we automatically
24616 make sure to test via one of these.
24617 - Fix to allow clients and mirrors to learn directory info from
24618 descriptor downloads that get cut off partway through.
24619 - Directory authorities had a bug in deciding if a newly published
24620 descriptor was novel enough to make everybody want a copy -- a few
24621 servers seem to be publishing new descriptors many times a minute.
24623 - Fix a rare bug that was causing some servers to complain about
24624 "closing wedged cpuworkers" and skip some circuit create requests.
24625 - Make the Exit flag in directory status documents actually work.
24628 Changes in version 0.1.1.21 - 2006-06-10
24629 o Crash and assert fixes from 0.1.1.20:
24630 - Fix a rare crash on Tor servers that have enabled hibernation.
24631 - Fix a seg fault on startup for Tor networks that use only one
24632 directory authority.
24633 - Fix an assert from a race condition that occurs on Tor servers
24634 while exiting, where various threads are trying to log that they're
24635 exiting, and delete the logs, at the same time.
24636 - Make our unit tests pass again on certain obscure platforms.
24639 - Add support for building SUSE RPM packages.
24640 - Speed up initial bootstrapping for clients: if we are making our
24641 first ever connection to any entry guard, then don't mark it down
24643 - When only one Tor server in the network is labelled as a guard,
24644 and we've already picked him, we would cycle endlessly picking him
24645 again, being unhappy about it, etc. Now we specifically exclude
24646 current guards when picking a new guard.
24647 - Servers send create cells more reliably after the TLS connection
24648 is established: we were sometimes forgetting to send half of them
24649 when we had more than one pending.
24650 - If we get a create cell that asks us to extend somewhere, but the
24651 Tor server there doesn't match the expected digest, we now send
24652 a destroy cell back, rather than silently doing nothing.
24653 - Make options->RedirectExit work again.
24654 - Make cookie authentication for the controller work again.
24655 - Stop being picky about unusual characters in the arguments to
24656 mapaddress. It's none of our business.
24657 - Add a new config option "TestVia" that lets you specify preferred
24658 middle hops to use for test circuits. Perhaps this will let me
24659 debug the reachability problems better.
24661 o Log / documentation fixes:
24662 - If we're a server and some peer has a broken TLS certificate, don't
24663 log about it unless ProtocolWarnings is set, i.e., we want to hear
24664 about protocol violations by others.
24665 - Fix spelling of VirtualAddrNetwork in man page.
24666 - Add a better explanation at the top of the autogenerated torrc file
24667 about what happened to our old torrc.
24670 Changes in version 0.1.1.20 - 2006-05-23
24672 - Downgrade a log severity where servers complain that they're
24674 - Avoid a compile warning on FreeBSD.
24675 - Remove string size limit on NEWDESC messages; solve bug 291.
24676 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
24677 more thoroughly when we're running on windows.
24680 Changes in version 0.1.1.19-rc - 2006-05-03
24682 - Regenerate our local descriptor if it's dirty and we try to use
24683 it locally (e.g. if it changes during reachability detection).
24684 - If we setconf our ORPort to 0, we continued to listen on the
24685 old ORPort and receive connections.
24686 - Avoid a second warning about machine/limits.h on Debian
24688 - Be willing to add our own routerinfo into the routerlist.
24689 Now authorities will include themselves in their directories
24690 and network-statuses.
24691 - Stop trying to upload rendezvous descriptors to every
24692 directory authority: only try the v1 authorities.
24693 - Servers no longer complain when they think they're not
24694 registered with the directory authorities. There were too many
24696 - Backport dist-rpm changes so rpms can be built without errors.
24699 - Implement an option, VirtualAddrMask, to set which addresses
24700 get handed out in response to mapaddress requests. This works
24701 around a bug in tsocks where 127.0.0.0/8 is never socksified.
24704 Changes in version 0.1.1.18-rc - 2006-04-10
24706 - Work harder to download live network-statuses from all the
24707 directory authorities we know about. Improve the threshold
24708 decision logic so we're more robust to edge cases.
24709 - When fetching rendezvous descriptors, we were willing to ask
24710 v2 authorities too, which would always return 404.
24713 - Stop listing down or invalid nodes in the v1 directory. This will
24714 reduce its bulk by about 1/3, and reduce load on directory
24716 - When deciding whether a router is Fast or Guard-worthy, consider
24717 his advertised BandwidthRate and not just the BandwidthCapacity.
24718 - No longer ship INSTALL and README files -- they are useless now.
24719 - Force rpmbuild to behave and honor target_cpu.
24720 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
24721 - Start to include translated versions of the tor-doc-*.html
24722 files, along with the screenshots. Still needs more work.
24723 - Start sending back 512 and 451 errors if mapaddress fails,
24724 rather than not sending anything back at all.
24725 - When we fail to bind or listen on an incoming or outgoing
24726 socket, we should close it before failing. otherwise we just
24727 leak it. (thanks to weasel for finding.)
24728 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
24729 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
24730 - Make NoPublish (even though deprecated) work again.
24731 - Fix a minor security flaw where a versioning auth dirserver
24732 could list a recommended version many times in a row to make
24733 clients more convinced that it's recommended.
24734 - Fix crash bug if there are two unregistered servers running
24735 with the same nickname, one of them is down, and you ask for
24736 them by nickname in your EntryNodes or ExitNodes. Also, try
24737 to pick the one that's running rather than an arbitrary one.
24738 - Fix an infinite loop we could hit if we go offline for too long.
24739 - Complain when we hit WSAENOBUFS on recv() or write() too.
24740 Perhaps this will help us hunt the bug.
24741 - If you're not a versioning dirserver, don't put the string
24742 "client-versions \nserver-versions \n" in your network-status.
24743 - Lower the minimum required number of file descriptors to 1000,
24744 so we can have some overhead for Valgrind on Linux, where the
24745 default ulimit -n is 1024.
24748 - Add tor.dizum.com as the fifth authoritative directory server.
24749 - Add a new config option FetchUselessDescriptors, off by default,
24750 for when you plan to run "exitlist" on your client and you want
24751 to know about even the non-running descriptors.
24754 Changes in version 0.1.1.17-rc - 2006-03-28
24756 - Clients and servers since 0.1.1.10-alpha have been expiring
24757 connections whenever they are idle for 5 minutes and they *do*
24758 have circuits on them. Oops. With this new version, clients will
24759 discard their previous entry guard choices and avoid choosing
24760 entry guards running these flawed versions.
24761 - Fix memory leak when uncompressing concatenated zlib streams. This
24762 was causing substantial leaks over time on Tor servers.
24763 - The v1 directory was including servers as much as 48 hours old,
24764 because that's how the new routerlist->routers works. Now only
24765 include them if they're 20 hours old or less.
24768 - Resume building on irix64, netbsd 2.0, etc.
24769 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
24771 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
24772 and it is confusing some users.
24773 - Mirrors stop caching the v1 directory so often.
24774 - Make the max number of old descriptors that a cache will hold
24775 rise with the number of directory authorities, so we can scale.
24776 - Change our win32 uname() hack to be more forgiving about what
24777 win32 versions it thinks it's found.
24780 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
24782 - When the controller's *setconf commands fail, collect an error
24783 message in a string and hand it back to the controller.
24784 - Make the v2 dir's "Fast" flag based on relative capacity, just
24785 like "Stable" is based on median uptime. Name everything in the
24786 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
24787 - Log server fingerprint on startup, so new server operators don't
24788 have to go hunting around their filesystem for it.
24789 - Return a robots.txt on our dirport to discourage google indexing.
24790 - Let the controller ask for GETINFO dir/status/foo so it can ask
24791 directly rather than connecting to the dir port. Only works when
24792 dirport is set for now.
24794 o New config options rather than constants in the code:
24795 - SocksTimeout: How long do we let a socks connection wait
24796 unattached before we fail it?
24797 - CircuitBuildTimeout: Cull non-open circuits that were born
24798 at least this many seconds ago.
24799 - CircuitIdleTimeout: Cull open clean circuits that were born
24800 at least this many seconds ago.
24803 Changes in version 0.1.1.16-rc - 2006-03-18
24804 o Bugfixes on 0.1.1.15-rc:
24805 - Fix assert when the controller asks to attachstream a connect-wait
24806 or resolve-wait stream.
24807 - Now do address rewriting when the controller asks us to attach
24808 to a particular circuit too. This will let Blossom specify
24809 "moria2.exit" without having to learn what moria2's IP address is.
24810 - Make the "tor --verify-config" command-line work again, so people
24811 can automatically check if their torrc will parse.
24812 - Authoritative dirservers no longer require an open connection from
24813 a server to consider him "reachable". We need this change because
24814 when we add new auth dirservers, old servers won't know not to
24816 - Let Tor build on Sun CC again.
24817 - Fix an off-by-one buffer size in dirserv.c that magically never
24818 hit our three authorities but broke sjmurdoch's own tor network.
24819 - If we as a directory mirror don't know of any v1 directory
24820 authorities, then don't try to cache any v1 directories.
24821 - Stop warning about unknown servers in our family when they are
24822 given as hex digests.
24823 - Stop complaining as quickly to the server operator that he
24824 hasn't registered his nickname/key binding.
24825 - Various cleanups so we can add new V2 Auth Dirservers.
24826 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
24827 reflect the updated flags in our v2 dir protocol.
24828 - Resume allowing non-printable characters for exit streams (both
24829 for connecting and for resolving). Now we tolerate applications
24830 that don't follow the RFCs. But continue to block malformed names
24833 o Bugfixes on 0.1.0.x:
24834 - Fix assert bug in close_logs(): when we close and delete logs,
24835 remove them all from the global "logfiles" list.
24836 - Fix minor integer overflow in calculating when we expect to use up
24837 our bandwidth allocation before hibernating.
24838 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
24839 there are multiple SSLs installed with different versions.
24840 - When we try to be a server and Address is not explicitly set and
24841 our hostname resolves to a private IP address, try to use an
24842 interface address if it has a public address. Now Windows machines
24843 that think of themselves as localhost can work by default.
24846 - Let the controller ask for GETINFO dir/server/foo so it can ask
24847 directly rather than connecting to the dir port.
24848 - Let the controller tell us about certain router descriptors
24849 that it doesn't want Tor to use in circuits. Implement
24850 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
24851 - New config option SafeSocks to reject all application connections
24852 using unsafe socks protocols. Defaults to off.
24855 Changes in version 0.1.1.15-rc - 2006-03-11
24856 o Bugfixes and cleanups:
24857 - When we're printing strings from the network, don't try to print
24858 non-printable characters. This protects us against shell escape
24859 sequence exploits, and also against attacks to fool humans into
24860 misreading their logs.
24861 - Fix a bug where Tor would fail to establish any connections if you
24862 left it off for 24 hours and then started it: we were happy with
24863 the obsolete network statuses, but they all referred to router
24864 descriptors that were too old to fetch, so we ended up with no
24865 valid router descriptors.
24866 - Fix a seg fault in the controller's "getinfo orconn-status"
24867 command while listing status on incoming handshaking connections.
24868 Introduce a status name "NEW" for these connections.
24869 - If we get a linelist or linelist_s config option from the torrc
24870 (e.g. ExitPolicy) and it has no value, warn and skip rather than
24871 silently resetting it to its default.
24872 - Don't abandon entry guards until they've been down or gone for
24874 - Cleaner and quieter log messages.
24877 - New controller signal NEWNYM that makes new application requests
24878 use clean circuits.
24879 - Add a new circuit purpose 'controller' to let the controller ask
24880 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
24881 controller command to let you specify the purpose if you're
24882 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
24883 command to let you change a circuit's purpose after it's been
24885 - Accept "private:*" in routerdesc exit policies; not generated yet
24886 because older Tors do not understand it.
24887 - Add BSD-style contributed startup script "rc.subr" from Peter
24891 Changes in version 0.1.1.14-alpha - 2006-02-20
24892 o Bugfixes on 0.1.1.x:
24893 - Don't die if we ask for a stdout or stderr log (even implicitly)
24894 and we're set to RunAsDaemon -- just warn.
24895 - We still had a few bugs in the OR connection rotation code that
24896 caused directory servers to slowly aggregate connections to other
24897 fast Tor servers. This time for sure!
24898 - Make log entries on Win32 include the name of the function again.
24899 - We were treating a pair of exit policies if they were equal even
24900 if one said accept and the other said reject -- causing us to
24901 not always publish a new descriptor since we thought nothing
24903 - Retry pending server downloads as well as pending networkstatus
24904 downloads when we unexpectedly get a socks request.
24905 - We were ignoring the IS_FAST flag in the directory status,
24906 meaning we were willing to pick trivial-bandwidth nodes for "fast"
24908 - If the controller's SAVECONF command fails (e.g. due to file
24909 permissions), let the controller know that it failed.
24912 - If we're trying to be a Tor server and running Windows 95/98/ME
24913 as a server, explain that we'll likely crash.
24914 - When we're a server, a client asks for an old-style directory,
24915 and our write bucket is empty, don't give it to him. This way
24916 small servers can continue to serve the directory *sometimes*,
24917 without getting overloaded.
24918 - Compress exit policies even more -- look for duplicate lines
24920 - Clients now honor the "guard" flag in the router status when
24921 picking entry guards, rather than looking at is_fast or is_stable.
24922 - Retain unrecognized lines in $DATADIR/state file, so that we can
24923 be forward-compatible.
24924 - Generate 18.0.0.0/8 address policy format in descs when we can;
24925 warn when the mask is not reducible to a bit-prefix.
24926 - Let the user set ControlListenAddress in the torrc. This can be
24927 dangerous, but there are some cases (like a secured LAN) where it
24929 - Split ReachableAddresses into ReachableDirAddresses and
24930 ReachableORAddresses, so we can restrict Dir conns to port 80
24931 and OR conns to port 443.
24932 - Now we can target arch and OS in rpm builds (contributed by
24933 Phobos). Also make the resulting dist-rpm filename match the
24935 - New config options to help controllers: FetchServerDescriptors
24936 and FetchHidServDescriptors for whether to fetch server
24937 info and hidserv info or let the controller do it, and
24938 PublishServerDescriptor and PublishHidServDescriptors.
24939 - Also let the controller set the __AllDirActionsPrivate config
24940 option if you want all directory fetches/publishes to happen via
24941 Tor (it assumes your controller bootstraps your circuits).
24944 Changes in version 0.1.0.17 - 2006-02-17
24945 o Crash bugfixes on 0.1.0.x:
24946 - When servers with a non-zero DirPort came out of hibernation,
24947 sometimes they would trigger an assert.
24949 o Other important bugfixes:
24950 - On platforms that don't have getrlimit (like Windows), we were
24951 artificially constraining ourselves to a max of 1024
24952 connections. Now just assume that we can handle as many as 15000
24953 connections. Hopefully this won't cause other problems.
24955 o Backported features:
24956 - When we're a server, a client asks for an old-style directory,
24957 and our write bucket is empty, don't give it to him. This way
24958 small servers can continue to serve the directory *sometimes*,
24959 without getting overloaded.
24960 - Whenever you get a 503 in response to a directory fetch, try
24961 once more. This will become important once servers start sending
24962 503's whenever they feel busy.
24963 - Fetch a new directory every 120 minutes, not every 40 minutes.
24964 Now that we have hundreds of thousands of users running the old
24965 directory algorithm, it's starting to hurt a lot.
24966 - Bump up the period for forcing a hidden service descriptor upload
24967 from 20 minutes to 1 hour.
24970 Changes in version 0.1.1.13-alpha - 2006-02-09
24971 o Crashes in 0.1.1.x:
24972 - When you tried to setconf ORPort via the controller, Tor would
24973 crash. So people using TorCP to become a server were sad.
24974 - Solve (I hope) the stack-smashing bug that we were seeing on fast
24975 servers. The problem appears to be something do with OpenSSL's
24976 random number generation, or how we call it, or something. Let me
24977 know if the crashes continue.
24978 - Turn crypto hardware acceleration off by default, until we find
24979 somebody smart who can test it for us. (It appears to produce
24980 seg faults in at least some cases.)
24981 - Fix a rare assert error when we've tried all intro points for
24982 a hidden service and we try fetching the service descriptor again:
24983 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
24986 - Fix a major load balance bug: we were round-robining in 16 KB
24987 chunks, and servers with bandwidthrate of 20 KB, while downloading
24988 a 600 KB directory, would starve their other connections. Now we
24989 try to be a bit more fair.
24990 - Dir authorities and mirrors were never expiring the newest
24991 descriptor for each server, causing memory and directory bloat.
24992 - Fix memory-bloating and connection-bloating bug on servers: We
24993 were never closing any connection that had ever had a circuit on
24994 it, because we were checking conn->n_circuits == 0, yet we had a
24995 bug that let it go negative.
24996 - Make Tor work using squid as your http proxy again -- squid
24997 returns an error if you ask for a URL that's too long, and it uses
24998 a really generic error message. Plus, many people are behind a
24999 transparent squid so they don't even realize it.
25000 - On platforms that don't have getrlimit (like Windows), we were
25001 artificially constraining ourselves to a max of 1024
25002 connections. Now just assume that we can handle as many as 15000
25003 connections. Hopefully this won't cause other problems.
25004 - Add a new config option ExitPolicyRejectPrivate which defaults to
25005 1. This means all exit policies will begin with rejecting private
25006 addresses, unless the server operator explicitly turns it off.
25009 - Clients no longer download descriptors for non-running
25011 - Before we add new directory authorities, we should make it
25012 clear that only v1 authorities should receive/publish hidden
25013 service descriptors.
25016 - As soon as we've fetched some more directory info, immediately
25017 try to download more server descriptors. This way we don't have
25018 a 10 second pause during initial bootstrapping.
25019 - Remove even more loud log messages that the server operator can't
25021 - When we're running an obsolete or un-recommended version, make
25022 the log message more clear about what the problem is and what
25023 versions *are* still recommended.
25024 - Provide a more useful warn message when our onion queue gets full:
25025 the CPU is too slow or the exit policy is too liberal.
25026 - Don't warn when we receive a 503 from a dirserver/cache -- this
25027 will pave the way for them being able to refuse if they're busy.
25028 - When we fail to bind a listener, try to provide a more useful
25029 log message: e.g., "Is Tor already running?"
25030 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
25031 Goldberg can prove things about our handshake protocol more
25033 - MaxConn has been obsolete for a while now. Document the ConnLimit
25034 config option, which is a *minimum* number of file descriptors
25035 that must be available else Tor refuses to start.
25036 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
25037 if you log to syslog and want something other than LOG_DAEMON.
25038 - Make dirservers generate a separate "guard" flag to mean,
25039 "would make a good entry guard". Make clients parse it and vote
25040 on it. Not used by clients yet.
25041 - Implement --with-libevent-dir option to ./configure. Also, improve
25042 search techniques to find libevent, and use those for openssl too.
25043 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
25044 - Only start testing reachability once we've established a
25045 circuit. This will make startup on dirservers less noisy.
25046 - Don't try to upload hidden service descriptors until we have
25047 established a circuit.
25048 - Fix the controller's "attachstream 0" command to treat conn like
25049 it just connected, doing address remapping, handling .exit and
25050 .onion idioms, and so on. Now we're more uniform in making sure
25051 that the controller hears about new and closing connections.
25054 Changes in version 0.1.1.12-alpha - 2006-01-11
25055 o Bugfixes on 0.1.1.x:
25056 - The fix to close duplicate server connections was closing all
25057 Tor client connections if they didn't establish a circuit
25058 quickly enough. Oops.
25059 - Fix minor memory issue (double-free) that happened on exit.
25061 o Bugfixes on 0.1.0.x:
25062 - Tor didn't warn when it failed to open a log file.
25065 Changes in version 0.1.1.11-alpha - 2006-01-10
25066 o Crashes in 0.1.1.x:
25067 - Include all the assert/crash fixes from 0.1.0.16.
25068 - If you start Tor and then quit very quickly, there were some
25069 races that tried to free things that weren't allocated yet.
25070 - Fix a rare memory stomp if you're running hidden services.
25071 - Fix segfault when specifying DirServer in config without nickname.
25072 - Fix a seg fault when you finish connecting to a server but at
25073 that moment you dump his server descriptor.
25074 - Extendcircuit and Attachstream controller commands would
25075 assert/crash if you don't give them enough arguments.
25076 - Fix an assert error when we're out of space in the connection_list
25077 and we try to post a hidden service descriptor (reported by weasel).
25078 - If you specify a relative torrc path and you set RunAsDaemon in
25079 your torrc, then it chdir()'s to the new directory. If you HUP,
25080 it tries to load the new torrc location, fails, and exits.
25081 The fix: no longer allow a relative path to torrc using -f.
25084 - Implement "entry guards": automatically choose a handful of entry
25085 nodes and stick with them for all circuits. Only pick new guards
25086 when the ones you have are unsuitable, and if the old guards
25087 become suitable again, switch back. This will increase security
25088 dramatically against certain end-point attacks. The EntryNodes
25089 config option now provides some hints about which entry guards you
25090 want to use most; and StrictEntryNodes means to only use those.
25091 - New directory logic: download by descriptor digest, not by
25092 fingerprint. Caches try to download all listed digests from
25093 authorities; clients try to download "best" digests from caches.
25094 This avoids partitioning and isolating attacks better.
25095 - Make the "stable" router flag in network-status be the median of
25096 the uptimes of running valid servers, and make clients pay
25097 attention to the network-status flags. Thus the cutoff adapts
25098 to the stability of the network as a whole, making IRC, IM, etc
25099 connections more reliable.
25102 - Tor servers with dynamic IP addresses were needing to wait 18
25103 hours before they could start doing reachability testing using
25104 the new IP address and ports. This is because they were using
25105 the internal descriptor to learn what to test, yet they were only
25106 rebuilding the descriptor once they decided they were reachable.
25107 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
25108 to download certain server descriptors, throw them away, and then
25109 fetch them again after 30 minutes. Now mirrors throw away these
25110 server descriptors so clients can't get them.
25111 - We were leaving duplicate connections to other ORs open for a week,
25112 rather than closing them once we detect a duplicate. This only
25113 really affected authdirservers, but it affected them a lot.
25114 - Spread the authdirservers' reachability testing over the entire
25115 testing interval, so we don't try to do 500 TLS's at once every
25119 - If the network is down, and we try to connect to a conn because
25120 we have a circuit in mind, and we timeout (30 seconds) because the
25121 network never answers, we were expiring the circuit, but we weren't
25122 obsoleting the connection or telling the entry_guards functions.
25123 - Some Tor servers process billions of cells per day. These statistics
25124 need to be uint64_t's.
25125 - Check for integer overflows in more places, when adding elements
25126 to smartlists. This could possibly prevent a buffer overflow
25127 on malicious huge inputs. I don't see any, but I haven't looked
25129 - ReachableAddresses kept growing new "reject *:*" lines on every
25131 - When you "setconf log" via the controller, it should remove all
25132 logs. We were automatically adding back in a "log notice stdout".
25133 - Newly bootstrapped Tor networks couldn't establish hidden service
25134 circuits until they had nodes with high uptime. Be more tolerant.
25135 - We were marking servers down when they could not answer every piece
25136 of the directory request we sent them. This was far too harsh.
25137 - Fix the torify (tsocks) config file to not use Tor for localhost
25139 - Directory authorities now go to the proper authority when asking for
25140 a networkstatus, even when they want a compressed one.
25141 - Fix a harmless bug that was causing Tor servers to log
25142 "Got an end because of misc error, but we're not an AP. Closing."
25143 - Authorities were treating their own descriptor changes as cosmetic,
25144 meaning the descriptor available in the network-status and the
25145 descriptor that clients downloaded were different.
25146 - The OS X installer was adding a symlink for tor_resolve but
25147 the binary was called tor-resolve (reported by Thomas Hardly).
25148 - Workaround a problem with some http proxies where they refuse GET
25149 requests that specify "Content-Length: 0" (reported by Adrian).
25150 - Fix wrong log message when you add a "HiddenServiceNodes" config
25151 line without any HiddenServiceDir line (reported by Chris Thomas).
25154 - Write the TorVersion into the state file so we have a prayer of
25155 keeping forward and backward compatibility.
25156 - Revive the FascistFirewall config option rather than eliminating it:
25157 now it's a synonym for ReachableAddresses *:80,*:443.
25158 - Clients choose directory servers from the network status lists,
25159 not from their internal list of router descriptors. Now they can
25160 go to caches directly rather than needing to go to authorities
25162 - Directory authorities ignore router descriptors that have only
25163 cosmetic differences: do this for 0.1.0.x servers now too.
25164 - Add a new flag to network-status indicating whether the server
25165 can answer v2 directory requests too.
25166 - Authdirs now stop whining so loudly about bad descriptors that
25167 they fetch from other dirservers. So when there's a log complaint,
25168 it's for sure from a freshly uploaded descriptor.
25169 - Reduce memory requirements in our structs by changing the order
25171 - There used to be two ways to specify your listening ports in a
25172 server descriptor: on the "router" line and with a separate "ports"
25173 line. Remove support for the "ports" line.
25174 - New config option "AuthDirRejectUnlisted" for auth dirservers as
25175 a panic button: if we get flooded with unusable servers we can
25176 revert to only listing servers in the approved-routers file.
25177 - Auth dir servers can now mark a fingerprint as "!reject" or
25178 "!invalid" in the approved-routers file (as its nickname), to
25179 refuse descriptors outright or include them but marked as invalid.
25180 - Servers store bandwidth history across restarts/crashes.
25181 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
25182 get a better idea of why their circuits failed. Not used yet.
25183 - Directory mirrors now cache up to 16 unrecognized network-status
25184 docs. Now we can add new authdirservers and they'll be cached too.
25185 - When picking a random directory, prefer non-authorities if any
25187 - New controller option "getinfo desc/all-recent" to fetch the
25188 latest server descriptor for every router that Tor knows about.
25191 Changes in version 0.1.0.16 - 2006-01-02
25192 o Crash bugfixes on 0.1.0.x:
25193 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25194 corrupting the heap, losing FDs, or crashing when we need to resize
25195 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25196 - It turns out sparc64 platforms crash on unaligned memory access
25197 too -- so detect and avoid this.
25198 - Handle truncated compressed data correctly (by detecting it and
25200 - Fix possible-but-unlikely free(NULL) in control.c.
25201 - When we were closing connections, there was a rare case that
25202 stomped on memory, triggering seg faults and asserts.
25203 - Avoid potential infinite recursion when building a descriptor. (We
25204 don't know that it ever happened, but better to fix it anyway.)
25205 - We were neglecting to unlink marked circuits from soon-to-close OR
25206 connections, which caused some rare scribbling on freed memory.
25207 - Fix a memory stomping race bug when closing the joining point of two
25208 rendezvous circuits.
25209 - Fix an assert in time parsing found by Steven Murdoch.
25211 o Other bugfixes on 0.1.0.x:
25212 - When we're doing reachability testing, provide more useful log
25213 messages so the operator knows what to expect.
25214 - Do not check whether DirPort is reachable when we are suppressing
25215 advertising it because of hibernation.
25216 - When building with -static or on Solaris, we sometimes needed -ldl.
25217 - When we're deciding whether a stream has enough circuits around
25218 that can handle it, count the freshly dirty ones and not the ones
25219 that are so dirty they won't be able to handle it.
25220 - When we're expiring old circuits, we had a logic error that caused
25221 us to close new rendezvous circuits rather than old ones.
25222 - Give a more helpful log message when you try to change ORPort via
25223 the controller: you should upgrade Tor if you want that to work.
25224 - We were failing to parse Tor versions that start with "Tor ".
25225 - Tolerate faulty streams better: when a stream fails for reason
25226 exitpolicy, stop assuming that the router is lying about his exit
25227 policy. When a stream fails for reason misc, allow it to retry just
25228 as if it was resolvefailed. When a stream has failed three times,
25229 reset its failure count so we can try again and get all three tries.
25232 Changes in version 0.1.1.10-alpha - 2005-12-11
25233 o Correctness bugfixes on 0.1.0.x:
25234 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25235 corrupting the heap, losing FDs, or crashing when we need to resize
25236 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25237 - Stop doing the complex voodoo overkill checking for insecure
25238 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
25239 - When we were closing connections, there was a rare case that
25240 stomped on memory, triggering seg faults and asserts.
25241 - We were neglecting to unlink marked circuits from soon-to-close OR
25242 connections, which caused some rare scribbling on freed memory.
25243 - When we're deciding whether a stream has enough circuits around
25244 that can handle it, count the freshly dirty ones and not the ones
25245 that are so dirty they won't be able to handle it.
25246 - Recover better from TCP connections to Tor servers that are
25247 broken but don't tell you (it happens!); and rotate TLS
25248 connections once a week.
25249 - When we're expiring old circuits, we had a logic error that caused
25250 us to close new rendezvous circuits rather than old ones.
25251 - Fix a scary-looking but apparently harmless bug where circuits
25252 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
25253 servers, and never switch to state CIRCUIT_STATE_OPEN.
25254 - When building with -static or on Solaris, we sometimes needed to
25256 - Give a useful message when people run Tor as the wrong user,
25257 rather than telling them to start chowning random directories.
25258 - We were failing to inform the controller about new .onion streams.
25260 o Security bugfixes on 0.1.0.x:
25261 - Refuse server descriptors if the fingerprint line doesn't match
25262 the included identity key. Tor doesn't care, but other apps (and
25263 humans) might actually be trusting the fingerprint line.
25264 - We used to kill the circuit when we receive a relay command we
25265 don't recognize. Now we just drop it.
25266 - Start obeying our firewall options more rigorously:
25267 . If we can't get to a dirserver directly, try going via Tor.
25268 . Don't ever try to connect (as a client) to a place our
25269 firewall options forbid.
25270 . If we specify a proxy and also firewall options, obey the
25271 firewall options even when we're using the proxy: some proxies
25272 can only proxy to certain destinations.
25273 - Fix a bug found by Lasse Overlier: when we were making internal
25274 circuits (intended to be cannibalized later for rendezvous and
25275 introduction circuits), we were picking them so that they had
25276 useful exit nodes. There was no need for this, and it actually
25277 aids some statistical attacks.
25278 - Start treating internal circuits and exit circuits separately.
25279 It's important to keep them separate because internal circuits
25280 have their last hops picked like middle hops, rather than like
25281 exit hops. So exiting on them will break the user's expectations.
25283 o Bugfixes on 0.1.1.x:
25284 - Take out the mis-feature where we tried to detect IP address
25285 flapping for people with DynDNS, and chose not to upload a new
25286 server descriptor sometimes.
25287 - Try to be compatible with OpenSSL 0.9.6 again.
25288 - Log fix: when the controller is logging about .onion addresses,
25289 sometimes it didn't include the ".onion" part of the address.
25290 - Don't try to modify options->DirServers internally -- if the
25291 user didn't specify any, just add the default ones directly to
25292 the trusted dirserver list. This fixes a bug where people running
25293 controllers would use SETCONF on some totally unrelated config
25294 option, and Tor would start yelling at them about changing their
25296 - Let the controller's redirectstream command specify a port, in
25297 case the controller wants to change that too.
25298 - When we requested a pile of server descriptors, we sometimes
25299 accidentally launched a duplicate request for the first one.
25300 - Bugfix for trackhostexits: write down the fingerprint of the
25301 chosen exit, not its nickname, because the chosen exit might not
25303 - When parsing foo.exit, if foo is unknown, and we are leaving
25304 circuits unattached, set the chosen_exit field and leave the
25305 address empty. This matters because controllers got confused
25307 - Directory authorities no longer try to download server
25308 descriptors that they know they will reject.
25310 o Features and updates:
25311 - Replace balanced trees with hash tables: this should make stuff
25312 significantly faster.
25313 - Resume using the AES counter-mode implementation that we ship,
25314 rather than OpenSSL's. Ours is significantly faster.
25315 - Many other CPU and memory improvements.
25316 - Add a new config option FastFirstHopPK (on by default) so clients
25317 do a trivial crypto handshake for their first hop, since TLS has
25318 already taken care of confidentiality and authentication.
25319 - Add a new config option TestSocks so people can see if their
25320 applications are using socks4, socks4a, socks5-with-ip, or
25321 socks5-with-hostname. This way they don't have to keep mucking
25322 with tcpdump and wondering if something got cached somewhere.
25323 - Warn when listening on a public address for socks. I suspect a
25324 lot of people are setting themselves up as open socks proxies,
25325 and they have no idea that jerks on the Internet are using them,
25326 since they simply proxy the traffic into the Tor network.
25327 - Add "private:*" as an alias in configuration for policies. Now
25328 you can simplify your exit policy rather than needing to list
25329 every single internal or nonroutable network space.
25330 - Add a new controller event type that allows controllers to get
25331 all server descriptors that were uploaded to a router in its role
25332 as authoritative dirserver.
25333 - Start shipping socks-extensions.txt, tor-doc-unix.html,
25334 tor-doc-server.html, and stylesheet.css in the tarball.
25335 - Stop shipping tor-doc.html in the tarball.
25338 Changes in version 0.1.1.9-alpha - 2005-11-15
25339 o Usability improvements:
25340 - Start calling it FooListenAddress rather than FooBindAddress,
25341 since few of our users know what it means to bind an address
25343 - Reduce clutter in server logs. We're going to try to make
25344 them actually usable now. New config option ProtocolWarnings that
25345 lets you hear about how _other Tors_ are breaking the protocol. Off
25347 - Divide log messages into logging domains. Once we put some sort
25348 of interface on this, it will let people looking at more verbose
25349 log levels specify the topics they want to hear more about.
25350 - Make directory servers return better http 404 error messages
25351 instead of a generic "Servers unavailable".
25352 - Check for even more Windows version flags when writing the platform
25353 string in server descriptors, and note any we don't recognize.
25354 - Clean up more of the OpenSSL memory when exiting, so we can detect
25355 memory leaks better.
25356 - Make directory authorities be non-versioning, non-naming by
25357 default. Now we can add new directory servers without requiring
25358 their operators to pay close attention.
25359 - When logging via syslog, include the pid whenever we provide
25360 a log entry. Suggested by Todd Fries.
25362 o Performance improvements:
25363 - Directory servers now silently throw away new descriptors that
25364 haven't changed much if the timestamps are similar. We do this to
25365 tolerate older Tor servers that upload a new descriptor every 15
25366 minutes. (It seemed like a good idea at the time.)
25367 - Inline bottleneck smartlist functions; use fast versions by default.
25368 - Add a "Map from digest to void*" abstraction digestmap_t so we
25369 can do less hex encoding/decoding. Use it in router_get_by_digest()
25370 to resolve a performance bottleneck.
25371 - Allow tor_gzip_uncompress to extract as much as possible from
25372 truncated compressed data. Try to extract as many
25373 descriptors as possible from truncated http responses (when
25374 DIR_PURPOSE_FETCH_ROUTERDESC).
25375 - Make circ->onionskin a pointer, not a static array. moria2 was using
25376 125000 circuit_t's after it had been up for a few weeks, which
25377 translates to 20+ megs of wasted space.
25378 - The private half of our EDH handshake keys are now chosen out
25379 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
25381 o Security improvements:
25382 - Start making directory caches retain old routerinfos, so soon
25383 clients can start asking by digest of descriptor rather than by
25384 fingerprint of server.
25385 - Add half our entropy from RAND_poll in OpenSSL. This knows how
25386 to use egd (if present), openbsd weirdness (if present), vms/os2
25387 weirdness (if we ever port there), and more in the future.
25389 o Bugfixes on 0.1.0.x:
25390 - Do round-robin writes of at most 16 kB per write. This might be
25391 more fair on loaded Tor servers, and it might resolve our Windows
25392 crash bug. It might also slow things down.
25393 - Our TLS handshakes were generating a single public/private
25394 keypair for the TLS context, rather than making a new one for
25395 each new connections. Oops. (But we were still rotating them
25396 periodically, so it's not so bad.)
25397 - When we were cannibalizing a circuit with a particular exit
25398 node in mind, we weren't checking to see if that exit node was
25399 already present earlier in the circuit. Oops.
25400 - When a Tor server's IP changes (e.g. from a dyndns address),
25401 upload a new descriptor so clients will learn too.
25402 - Really busy servers were keeping enough circuits open on stable
25403 connections that they were wrapping around the circuit_id
25404 space. (It's only two bytes.) This exposed a bug where we would
25405 feel free to reuse a circuit_id even if it still exists but has
25406 been marked for close. Try to fix this bug. Some bug remains.
25407 - If we would close a stream early (e.g. it asks for a .exit that
25408 we know would refuse it) but the LeaveStreamsUnattached config
25409 option is set by the controller, then don't close it.
25411 o Bugfixes on 0.1.1.8-alpha:
25412 - Fix a big pile of memory leaks, some of them serious.
25413 - Do not try to download a routerdesc if we would immediately reject
25415 - Resume inserting a newline between all router descriptors when
25416 generating (old style) signed directories, since our spec says
25418 - When providing content-type application/octet-stream for
25419 server descriptors using .z, we were leaving out the
25420 content-encoding header. Oops. (Everything tolerated this just
25421 fine, but that doesn't mean we need to be part of the problem.)
25422 - Fix a potential seg fault in getconf and getinfo using version 1
25423 of the controller protocol.
25424 - Avoid crash: do not check whether DirPort is reachable when we
25425 are suppressing it because of hibernation.
25426 - Make --hash-password not crash on exit.
25429 Changes in version 0.1.1.8-alpha - 2005-10-07
25430 o New features (major):
25431 - Clients don't download or use the directory anymore. Now they
25432 download and use network-statuses from the trusted dirservers,
25433 and fetch individual server descriptors as needed from mirrors.
25434 See dir-spec.txt for all the gory details.
25435 - Be more conservative about whether to advertise our DirPort.
25436 The main change is to not advertise if we're running at capacity
25437 and either a) we could hibernate or b) our capacity is low and
25438 we're using a default DirPort.
25439 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
25441 o New features (minor):
25442 - Try to be smart about when to retry network-status and
25443 server-descriptor fetches. Still needs some tuning.
25444 - Stop parsing, storing, or using running-routers output (but
25445 mirrors still cache and serve it).
25446 - Consider a threshold of versioning dirservers (dirservers who have
25447 an opinion about which Tor versions are still recommended) before
25448 deciding whether to warn the user that he's obsolete.
25449 - Dirservers can now reject/invalidate by key and IP, with the
25450 config options "AuthDirInvalid" and "AuthDirReject". This is
25451 useful since currently we automatically list servers as running
25452 and usable even if we know they're jerks.
25453 - Provide dire warnings to any users who set DirServer; move it out
25454 of torrc.sample and into torrc.complete.
25455 - Add MyFamily to torrc.sample in the server section.
25456 - Add nicknames to the DirServer line, so we can refer to them
25457 without requiring all our users to memorize their IP addresses.
25458 - When we get an EOF or a timeout on a directory connection, note
25459 how many bytes of serverdesc we are dropping. This will help
25460 us determine whether it is smart to parse incomplete serverdesc
25462 - Add a new function to "change pseudonyms" -- that is, to stop
25463 using any currently-dirty circuits for new streams, so we don't
25464 link new actions to old actions. Currently it's only called on
25465 HUP (or SIGNAL RELOAD).
25466 - On sighup, if UseHelperNodes changed to 1, use new circuits.
25467 - Start using RAND_bytes rather than RAND_pseudo_bytes from
25468 OpenSSL. Also, reseed our entropy every hour, not just at
25469 startup. And entropy in 512-bit chunks, not 160-bit chunks.
25471 o Fixes on 0.1.1.7-alpha:
25472 - Nobody ever implemented EVENT_ADDRMAP for control protocol
25473 version 0, so don't let version 0 controllers ask for it.
25474 - If you requested something with too many newlines via the
25475 v1 controller protocol, you could crash tor.
25476 - Fix a number of memory leaks, including some pretty serious ones.
25477 - Re-enable DirPort testing again, so Tor servers will be willing
25478 to advertise their DirPort if it's reachable.
25479 - On TLS handshake, only check the other router's nickname against
25480 its expected nickname if is_named is set.
25482 o Fixes forward-ported from 0.1.0.15:
25483 - Don't crash when we don't have any spare file descriptors and we
25484 try to spawn a dns or cpu worker.
25485 - Make the numbers in read-history and write-history into uint64s,
25486 so they don't overflow and publish negatives in the descriptor.
25488 o Fixes on 0.1.0.x:
25489 - For the OS X package's modified privoxy config file, comment
25490 out the "logfile" line so we don't log everything passed
25492 - We were whining about using socks4 or socks5-with-local-lookup
25493 even when it's an IP in the "virtual" range we designed exactly
25495 - We were leaking some memory every time the client changes IPs.
25496 - Never call free() on tor_malloc()d memory. This will help us
25497 use dmalloc to detect memory leaks.
25498 - Check for named servers when looking them up by nickname;
25499 warn when we'recalling a non-named server by its nickname;
25500 don't warn twice about the same name.
25501 - Try to list MyFamily elements by key, not by nickname, and warn
25502 if we've not heard of the server.
25503 - Make windows platform detection (uname equivalent) smarter.
25504 - It turns out sparc64 doesn't like unaligned access either.
25507 Changes in version 0.1.0.15 - 2005-09-23
25508 o Bugfixes on 0.1.0.x:
25509 - Reject ports 465 and 587 (spam targets) in default exit policy.
25510 - Don't crash when we don't have any spare file descriptors and we
25511 try to spawn a dns or cpu worker.
25512 - Get rid of IgnoreVersion undocumented config option, and make us
25513 only warn, never exit, when we're running an obsolete version.
25514 - Don't try to print a null string when your server finds itself to
25515 be unreachable and the Address config option is empty.
25516 - Make the numbers in read-history and write-history into uint64s,
25517 so they don't overflow and publish negatives in the descriptor.
25518 - Fix a minor memory leak in smartlist_string_remove().
25519 - We were only allowing ourselves to upload a server descriptor at
25520 most every 20 minutes, even if it changed earlier than that.
25521 - Clean up log entries that pointed to old URLs.
25524 Changes in version 0.1.1.7-alpha - 2005-09-14
25525 o Fixes on 0.1.1.6-alpha:
25526 - Exit servers were crashing when people asked them to make a
25527 connection to an address not in their exit policy.
25528 - Looking up a non-existent stream for a v1 control connection would
25530 - Fix a seg fault if we ask a dirserver for a descriptor by
25531 fingerprint but he doesn't know about him.
25532 - SETCONF was appending items to linelists, not clearing them.
25533 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
25534 out and refuse the setconf if it would fail.
25535 - Downgrade the dirserver log messages when whining about
25539 - Add Peter Palfrader's check-tor script to tor/contrib/
25540 It lets you easily check whether a given server (referenced by
25541 nickname) is reachable by you.
25542 - Numerous changes to move towards client-side v2 directories. Not
25545 o Fixes on 0.1.0.x:
25546 - If the user gave tor an odd number of command-line arguments,
25547 we were silently ignoring the last one. Now we complain and fail.
25548 [This wins the oldest-bug prize -- this bug has been present since
25549 November 2002, as released in Tor 0.0.0.]
25550 - Do not use unaligned memory access on alpha, mips, or mipsel.
25551 It *works*, but is very slow, so we treat them as if it doesn't.
25552 - Retry directory requests if we fail to get an answer we like
25553 from a given dirserver (we were retrying before, but only if
25554 we fail to connect).
25555 - When writing the RecommendedVersions line, sort them first.
25556 - When the client asked for a rendezvous port that the hidden
25557 service didn't want to provide, we were sending an IP address
25558 back along with the end cell. Fortunately, it was zero. But stop
25560 - Correct "your server is reachable" log entries to indicate that
25561 it was self-testing that told us so.
25564 Changes in version 0.1.1.6-alpha - 2005-09-09
25565 o Fixes on 0.1.1.5-alpha:
25566 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
25567 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
25568 - Fix bug with tor_memmem finding a match at the end of the string.
25569 - Make unit tests run without segfaulting.
25570 - Resolve some solaris x86 compile warnings.
25571 - Handle duplicate lines in approved-routers files without warning.
25572 - Fix bug where as soon as a server refused any requests due to his
25573 exit policy (e.g. when we ask for localhost and he tells us that's
25574 127.0.0.1 and he won't do it), we decided he wasn't obeying his
25575 exit policy using him for any exits.
25576 - Only do openssl hardware accelerator stuff if openssl version is
25579 o New controller features/fixes:
25580 - Add a "RESETCONF" command so you can set config options like
25581 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
25582 a config option in the torrc with no value, then it clears it
25583 entirely (rather than setting it to its default).
25584 - Add a "GETINFO config-file" to tell us where torrc is.
25585 - Avoid sending blank lines when GETINFO replies should be empty.
25586 - Add a QUIT command for the controller (for using it manually).
25587 - Fix a bug in SAVECONF that was adding default dirservers and
25588 other redundant entries to the torrc file.
25590 o Start on the new directory design:
25591 - Generate, publish, cache, serve new network-status format.
25592 - Publish individual descriptors (by fingerprint, by "all", and by
25594 - Publish client and server recommended versions separately.
25595 - Allow tor_gzip_uncompress() to handle multiple concatenated
25596 compressed strings. Serve compressed groups of router
25597 descriptors. The compression logic here could be more
25599 - Distinguish v1 authorities (all currently trusted directories)
25600 from v2 authorities (all trusted directories).
25601 - Change DirServers config line to note which dirs are v1 authorities.
25602 - Add configuration option "V1AuthoritativeDirectory 1" which
25603 moria1, moria2, and tor26 should set.
25604 - Remove option when getting directory cache to see whether they
25605 support running-routers; they all do now. Replace it with one
25606 to see whether caches support v2 stuff.
25609 - Dirservers now do their own external reachability testing of each
25610 Tor server, and only list them as running if they've been found to
25611 be reachable. We also send back warnings to the server's logs if
25612 it uploads a descriptor that we already believe is unreachable.
25613 - Implement exit enclaves: if we know an IP address for the
25614 destination, and there's a running Tor server at that address
25615 which allows exit to the destination, then extend the circuit to
25616 that exit first. This provides end-to-end encryption and end-to-end
25617 authentication. Also, if the user wants a .exit address or enclave,
25618 use 4 hops rather than 3, and cannibalize a general circ for it
25620 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
25621 controller. Also, rotate dns and cpu workers if the controller
25622 changes options that will affect them; and initialize the dns
25623 worker cache tree whether or not we start out as a server.
25624 - Only upload a new server descriptor when options change, 18
25625 hours have passed, uptime is reset, or bandwidth changes a lot.
25626 - Check [X-]Forwarded-For headers in HTTP requests when generating
25627 log messages. This lets people run dirservers (and caches) behind
25628 Apache but still know which IP addresses are causing warnings.
25630 o Config option changes:
25631 - Replace (Fascist)Firewall* config options with a new
25632 ReachableAddresses option that understands address policies.
25633 For example, "ReachableAddresses *:80,*:443"
25634 - Get rid of IgnoreVersion undocumented config option, and make us
25635 only warn, never exit, when we're running an obsolete version.
25636 - Make MonthlyAccountingStart config option truly obsolete now.
25638 o Fixes on 0.1.0.x:
25639 - Reject ports 465 and 587 in the default exit policy, since
25640 people have started using them for spam too.
25641 - It turns out we couldn't bootstrap a network since we added
25642 reachability detection in 0.1.0.1-rc. Good thing the Tor network
25643 has never gone down. Add an AssumeReachable config option to let
25644 servers and dirservers bootstrap. When we're trying to build a
25645 high-uptime or high-bandwidth circuit but there aren't enough
25646 suitable servers, try being less picky rather than simply failing.
25647 - Our logic to decide if the OR we connected to was the right guy
25648 was brittle and maybe open to a mitm for unverified routers.
25649 - We weren't cannibalizing circuits correctly for
25650 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
25651 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
25652 build those from scratch. This should make hidden services faster.
25653 - Predict required circuits better, with an eye toward making hidden
25654 services faster on the service end.
25655 - Retry streams if the exit node sends back a 'misc' failure. This
25656 should result in fewer random failures. Also, after failing
25657 from resolve failed or misc, reset the num failures, so we give
25658 it a fair shake next time we try.
25659 - Clean up the rendezvous warn log msgs, and downgrade some to info.
25660 - Reduce severity on logs about dns worker spawning and culling.
25661 - When we're shutting down and we do something like try to post a
25662 server descriptor or rendezvous descriptor, don't complain that
25663 we seem to be unreachable. Of course we are, we're shutting down.
25664 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
25665 We don't use them yet, but maybe one day our DNS resolver will be
25666 able to discover them.
25667 - Make ContactInfo mandatory for authoritative directory servers.
25668 - Require server descriptors to list IPv4 addresses -- hostnames
25669 are no longer allowed. This also fixes some potential security
25670 problems with people providing hostnames as their address and then
25671 preferentially resolving them to partition users.
25672 - Change log line for unreachability to explicitly suggest /etc/hosts
25673 as the culprit. Also make it clearer what IP address and ports we're
25674 testing for reachability.
25675 - Put quotes around user-supplied strings when logging so users are
25676 more likely to realize if they add bad characters (like quotes)
25678 - Let auth dir servers start without specifying an Address config
25680 - Make unit tests (and other invocations that aren't the real Tor)
25681 run without launching listeners, creating subdirectories, and so on.
25684 Changes in version 0.1.1.5-alpha - 2005-08-08
25685 o Bugfixes included in 0.1.0.14.
25687 o Bugfixes on 0.1.0.x:
25688 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
25689 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
25690 it would silently using ignore the 6668.
25693 Changes in version 0.1.0.14 - 2005-08-08
25694 o Bugfixes on 0.1.0.x:
25695 - Fix the other half of the bug with crypto handshakes
25697 - Fix an assert trigger if you send a 'signal term' via the
25698 controller when it's listening for 'event info' messages.
25701 Changes in version 0.1.1.4-alpha - 2005-08-04
25702 o Bugfixes included in 0.1.0.13.
25705 - Improve tor_gettimeofday() granularity on windows.
25706 - Make clients regenerate their keys when their IP address changes.
25707 - Implement some more GETINFO goodness: expose helper nodes, config
25708 options, getinfo keys.
25711 Changes in version 0.1.0.13 - 2005-08-04
25712 o Bugfixes on 0.1.0.x:
25713 - Fix a critical bug in the security of our crypto handshakes.
25714 - Fix a size_t underflow in smartlist_join_strings2() that made
25715 it do bad things when you hand it an empty smartlist.
25716 - Fix Windows installer to ship Tor license (thanks to Aphex for
25717 pointing out this oversight) and put a link to the doc directory
25719 - Explicitly set no-unaligned-access for sparc: it turns out the
25720 new gcc's let you compile broken code, but that doesn't make it
25724 Changes in version 0.1.1.3-alpha - 2005-07-23
25725 o Bugfixes on 0.1.1.2-alpha:
25726 - Fix a bug in handling the controller's "post descriptor"
25728 - Fix several bugs in handling the controller's "extend circuit"
25730 - Fix a bug in handling the controller's "stream status" event.
25731 - Fix an assert failure if we have a controller listening for
25732 circuit events and we go offline.
25733 - Re-allow hidden service descriptors to publish 0 intro points.
25734 - Fix a crash when generating your hidden service descriptor if
25735 you don't have enough intro points already.
25737 o New features on 0.1.1.2-alpha:
25738 - New controller function "getinfo accounting", to ask how
25739 many bytes we've used in this time period.
25740 - Experimental support for helper nodes: a lot of the risk from
25741 a small static adversary comes because users pick new random
25742 nodes every time they rebuild a circuit. Now users will try to
25743 stick to the same small set of entry nodes if they can. Not
25744 enabled by default yet.
25746 o Bugfixes on 0.1.0.12:
25747 - If you're an auth dir server, always publish your dirport,
25748 even if you haven't yet found yourself to be reachable.
25749 - Fix a size_t underflow in smartlist_join_strings2() that made
25750 it do bad things when you hand it an empty smartlist.
25753 Changes in version 0.1.0.12 - 2005-07-18
25754 o New directory servers:
25755 - tor26 has changed IP address.
25757 o Bugfixes on 0.1.0.x:
25758 - Fix a possible double-free in tor_gzip_uncompress().
25759 - When --disable-threads is set, do not search for or link against
25760 pthreads libraries.
25761 - Don't trigger an assert if an authoritative directory server
25762 claims its dirport is 0.
25763 - Fix bug with removing Tor as an NT service: some people were
25764 getting "The service did not return an error." Thanks to Matt
25768 Changes in version 0.1.1.2-alpha - 2005-07-15
25769 o New directory servers:
25770 - tor26 has changed IP address.
25772 o Bugfixes on 0.1.0.x, crashes/leaks:
25773 - Port the servers-not-obeying-their-exit-policies fix from
25775 - Fix an fd leak in start_daemon().
25776 - On Windows, you can't always reopen a port right after you've
25777 closed it. So change retry_listeners() to only close and re-open
25778 ports that have changed.
25779 - Fix a possible double-free in tor_gzip_uncompress().
25781 o Bugfixes on 0.1.0.x, usability:
25782 - When tor_socketpair() fails in Windows, give a reasonable
25783 Windows-style errno back.
25784 - Let people type "tor --install" as well as "tor -install" when
25786 want to make it an NT service.
25787 - NT service patch from Matt Edman to improve error messages.
25788 - When the controller asks for a config option with an abbreviated
25789 name, give the full name in our response.
25790 - Correct the man page entry on TrackHostExitsExpire.
25791 - Looks like we were never delivering deflated (i.e. compressed)
25792 running-routers lists, even when asked. Oops.
25793 - When --disable-threads is set, do not search for or link against
25794 pthreads libraries.
25796 o Bugfixes on 0.1.1.x:
25797 - Fix a seg fault with autodetecting which controller version is
25801 - New hidden service descriptor format: put a version in it, and
25802 let people specify introduction/rendezvous points that aren't
25803 in "the directory" (which is subjective anyway).
25804 - Allow the DEBUG controller event to work again. Mark certain log
25805 entries as "don't tell this to controllers", so we avoid cycles.
25808 Changes in version 0.1.0.11 - 2005-06-30
25809 o Bugfixes on 0.1.0.x:
25810 - Fix major security bug: servers were disregarding their
25811 exit policies if clients behaved unexpectedly.
25812 - Make OS X init script check for missing argument, so we don't
25813 confuse users who invoke it incorrectly.
25814 - Fix a seg fault in "tor --hash-password foo".
25815 - The MAPADDRESS control command was broken.
25818 Changes in version 0.1.1.1-alpha - 2005-06-29
25820 - Make OS X init script check for missing argument, so we don't
25821 confuse users who invoke it incorrectly.
25822 - Fix a seg fault in "tor --hash-password foo".
25823 - Fix a possible way to DoS dirservers.
25824 - When we complain that your exit policy implicitly allows local or
25825 private address spaces, name them explicitly so operators can
25827 - Make the log message less scary when all the dirservers are
25828 temporarily unreachable.
25829 - We were printing the number of idle dns workers incorrectly when
25833 - Revised controller protocol (version 1) that uses ascii rather
25834 than binary. Add supporting libraries in python and java so you
25835 can use the controller from your applications without caring how
25836 our protocol works.
25837 - Spiffy new support for crypto hardware accelerators. Can somebody
25841 Changes in version 0.0.9.10 - 2005-06-16
25842 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
25843 - Refuse relay cells that claim to have a length larger than the
25844 maximum allowed. This prevents a potential attack that could read
25845 arbitrary memory (e.g. keys) from an exit server's process
25849 Changes in version 0.1.0.10 - 2005-06-14
25850 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
25851 libevent before 1.1a.
25854 Changes in version 0.1.0.9-rc - 2005-06-09
25856 - Reset buf->highwater every time buf_shrink() is called, not just on
25857 a successful shrink. This was causing significant memory bloat.
25858 - Fix buffer overflow when checking hashed passwords.
25859 - Security fix: if seeding the RNG on Win32 fails, quit.
25860 - Allow seeding the RNG on Win32 even when you're not running as
25862 - Disable threading on Solaris too. Something is wonky with it,
25863 cpuworkers, and reentrant libs.
25864 - Reenable the part of the code that tries to flush as soon as an
25865 OR outbuf has a full TLS record available. Perhaps this will make
25866 OR outbufs not grow as huge except in rare cases, thus saving lots
25867 of CPU time plus memory.
25868 - Reject malformed .onion addresses rather then passing them on as
25869 normal web requests.
25870 - Adapt patch from Adam Langley: fix possible memory leak in
25871 tor_lookup_hostname().
25872 - Initialize libevent later in the startup process, so the logs are
25873 already established by the time we start logging libevent warns.
25874 - Use correct errno on win32 if libevent fails.
25875 - Check and warn about known-bad/slow libevent versions.
25876 - Pay more attention to the ClientOnly config option.
25877 - Have torctl.in/tor.sh.in check for location of su binary (needed
25879 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
25880 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
25881 HttpProxyAuthenticator
25882 - Stop warning about sigpipes in the logs. We're going to
25883 pretend that getting these occasionally is normal and fine.
25884 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
25886 installer screens; and don't put stuff into StartupItems unless
25887 the user asks you to.
25888 - Require servers that use the default dirservers to have public IP
25889 addresses. We have too many servers that are configured with private
25890 IPs and their admins never notice the log entries complaining that
25891 their descriptors are being rejected.
25892 - Add OSX uninstall instructions. An actual uninstall script will
25896 Changes in version 0.1.0.8-rc - 2005-05-23
25898 - It turns out that kqueue on OS X 10.3.9 was causing kernel
25899 panics. Disable kqueue on all OS X Tors.
25900 - Fix RPM: remove duplicate line accidentally added to the rpm
25902 - Disable threads on openbsd too, since its gethostaddr is not
25904 - Tolerate libevent 0.8 since it still works, even though it's
25906 - Enable building on Red Hat 9.0 again.
25907 - Allow the middle hop of the testing circuit to be running any
25908 version, now that most of them have the bugfix to let them connect
25909 to unknown servers. This will allow reachability testing to work
25910 even when 0.0.9.7-0.0.9.9 become obsolete.
25911 - Handle relay cells with rh.length too large. This prevents
25912 a potential attack that could read arbitrary memory (maybe even
25913 keys) from the exit server's process.
25914 - We screwed up the dirport reachability testing when we don't yet
25915 have a cached version of the directory. Hopefully now fixed.
25916 - Clean up router_load_single_router() (used by the controller),
25917 so it doesn't seg fault on error.
25918 - Fix a minor memory leak when somebody establishes an introduction
25919 point at your Tor server.
25920 - If a socks connection ends because read fails, don't warn that
25921 you're not sending a socks reply back.
25924 - Add HttpProxyAuthenticator config option too, that works like
25925 the HttpsProxyAuthenticator config option.
25926 - Encode hashed controller passwords in hex instead of base64,
25927 to make it easier to write controllers.
25930 Changes in version 0.1.0.7-rc - 2005-05-17
25932 - Fix a bug in the OS X package installer that prevented it from
25933 installing on Tiger.
25934 - Fix a script bug in the OS X package installer that made it
25935 complain during installation.
25936 - Find libevent even if it's hiding in /usr/local/ and your
25937 CFLAGS and LDFLAGS don't tell you to look there.
25938 - Be able to link with libevent as a shared library (the default
25939 after 1.0d), even if it's hiding in /usr/local/lib and even
25940 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
25941 assuming you're running gcc. Otherwise fail and give a useful
25943 - Fix a bug in the RPM packager: set home directory for _tor to
25944 something more reasonable when first installing.
25945 - Free a minor amount of memory that is still reachable on exit.
25948 Changes in version 0.1.0.6-rc - 2005-05-14
25950 - Implement --disable-threads configure option. Disable threads on
25951 netbsd by default, because it appears to have no reentrant resolver
25953 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
25954 release (1.1) detects and disables kqueue if it's broken.
25955 - Append default exit policy before checking for implicit internal
25956 addresses. Now we don't log a bunch of complaints on startup
25957 when using the default exit policy.
25958 - Some people were putting "Address " in their torrc, and they had
25959 a buggy resolver that resolved " " to 0.0.0.0. Oops.
25960 - If DataDir is ~/.tor, and that expands to /.tor, then default to
25961 LOCALSTATEDIR/tor instead.
25962 - Fix fragmented-message bug in TorControl.py.
25963 - Resolve a minor bug which would prevent unreachable dirports
25964 from getting suppressed in the published descriptor.
25965 - When the controller gave us a new descriptor, we weren't resolving
25966 it immediately, so Tor would think its address was 0.0.0.0 until
25967 we fetched a new directory.
25968 - Fix an uppercase/lowercase case error in suppressing a bogus
25969 libevent warning on some Linuxes.
25972 - Begin scrubbing sensitive strings from logs by default. Turn off
25973 the config option SafeLogging if you need to do debugging.
25974 - Switch to a new buffer management algorithm, which tries to avoid
25975 reallocing and copying quite as much. In first tests it looks like
25976 it uses *more* memory on average, but less cpu.
25977 - First cut at support for "create-fast" cells. Clients can use
25978 these when extending to their first hop, since the TLS already
25979 provides forward secrecy and authentication. Not enabled on
25981 - When dirservers refuse a router descriptor, we now log its
25982 contactinfo, platform, and the poster's IP address.
25983 - Call tor_free_all instead of connections_free_all after forking, to
25984 save memory on systems that need to fork.
25985 - Whine at you if you're a server and you don't set your contactinfo.
25986 - Implement --verify-config command-line option to check if your torrc
25987 is valid without actually launching Tor.
25988 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
25989 rather than just rejecting it.
25992 Changes in version 0.1.0.5-rc - 2005-04-27
25994 - Stop trying to print a null pointer if an OR conn fails because
25995 we didn't like its cert.
25997 - Switch our internal buffers implementation to use a ring buffer,
25998 to hopefully improve performance for fast servers a lot.
25999 - Add HttpsProxyAuthenticator support (basic auth only), based
26000 on patch from Adam Langley.
26001 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
26002 the fast servers that have been joining lately.
26003 - Give hidden service accesses extra time on the first attempt,
26004 since 60 seconds is often only barely enough. This might improve
26006 - Improve performance for dirservers: stop re-parsing the whole
26007 directory every time you regenerate it.
26008 - Add more debugging info to help us find the weird dns freebsd
26009 pthreads bug; cleaner debug messages to help track future issues.
26012 Changes in version 0.0.9.9 - 2005-04-23
26013 o Bugfixes on 0.0.9.x:
26014 - If unofficial Tor clients connect and send weird TLS certs, our
26015 Tor server triggers an assert. This release contains a minimal
26016 backport from the broader fix that we put into 0.1.0.4-rc.
26019 Changes in version 0.1.0.4-rc - 2005-04-23
26021 - If unofficial Tor clients connect and send weird TLS certs, our
26022 Tor server triggers an assert. Stop asserting, and start handling
26023 TLS errors better in other situations too.
26024 - When the controller asks us to tell it about all the debug-level
26025 logs, it turns out we were generating debug-level logs while
26026 telling it about them, which turns into a bad loop. Now keep
26027 track of whether you're sending a debug log to the controller,
26028 and don't log when you are.
26029 - Fix the "postdescriptor" feature of the controller interface: on
26030 non-complete success, only say "done" once.
26032 - Clients are now willing to load balance over up to 2mB, not 1mB,
26033 of advertised bandwidth capacity.
26034 - Add a NoPublish config option, so you can be a server (e.g. for
26035 testing running Tor servers in other Tor networks) without
26036 publishing your descriptor to the primary dirservers.
26039 Changes in version 0.1.0.3-rc - 2005-04-08
26040 o Improvements on 0.1.0.2-rc:
26041 - Client now retries when streams end early for 'hibernating' or
26042 'resource limit' reasons, rather than failing them.
26043 - More automated handling for dirserver operators:
26044 - Automatically approve nodes running 0.1.0.2-rc or later,
26045 now that the the reachability detection stuff is working.
26046 - Now we allow two unverified servers with the same nickname
26047 but different keys. But if a nickname is verified, only that
26048 nickname+key are allowed.
26049 - If you're an authdirserver connecting to an address:port,
26050 and it's not the OR you were expecting, forget about that
26051 descriptor. If he *was* the one you were expecting, then forget
26052 about all other descriptors for that address:port.
26053 - Allow servers to publish descriptors from 12 hours in the future.
26054 Corollary: only whine about clock skew from the dirserver if
26055 he's a trusted dirserver (since now even verified servers could
26056 have quite wrong clocks).
26057 - Adjust maximum skew and age for rendezvous descriptors: let skew
26058 be 48 hours rather than 90 minutes.
26059 - Efficiency improvements:
26060 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
26061 it much faster to look up a circuit for each relay cell.
26062 - Remove most calls to assert_all_pending_dns_resolves_ok(),
26063 since they're eating our cpu on exit nodes.
26064 - Stop wasting time doing a case insensitive comparison for every
26065 dns name every time we do any lookup. Canonicalize the names to
26066 lowercase and be done with it.
26067 - Start sending 'truncated' cells back rather than destroy cells,
26068 if the circuit closes in front of you. This means we won't have
26069 to abandon partially built circuits.
26070 - Only warn once per nickname from add_nickname_list_to_smartlist
26071 per failure, so an entrynode or exitnode choice that's down won't
26073 - Put a note in the torrc about abuse potential with the default
26075 - Revise control spec and implementation to allow all log messages to
26076 be sent to controller with their severities intact (suggested by
26077 Matt Edman). Update TorControl to handle new log event types.
26078 - Provide better explanation messages when controller's POSTDESCRIPTOR
26080 - Stop putting nodename in the Platform string in server descriptors.
26081 It doesn't actually help, and it is confusing/upsetting some people.
26083 o Bugfixes on 0.1.0.2-rc:
26084 - We were printing the host mask wrong in exit policies in server
26085 descriptors. This isn't a critical bug though, since we were still
26086 obeying the exit policy internally.
26087 - Fix Tor when compiled with libevent but without pthreads: move
26088 connection_unregister() from _connection_free() to
26090 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
26091 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
26092 when we look through the connection array, we'll find any of the
26093 cpu/dnsworkers. This is no good.
26095 o Bugfixes on 0.0.9.8:
26096 - Fix possible bug on threading platforms (e.g. win32) which was
26097 leaking a file descriptor whenever a cpuworker or dnsworker died.
26098 - When using preferred entry or exit nodes, ignore whether the
26099 circuit wants uptime or capacity. They asked for the nodes, they
26101 - chdir() to your datadirectory at the *end* of the daemonize process,
26102 not the beginning. This was a problem because the first time you
26103 run tor, if your datadir isn't there, and you have runasdaemon set
26104 to 1, it will try to chdir to it before it tries to create it. Oops.
26105 - Handle changed router status correctly when dirserver reloads
26106 fingerprint file. We used to be dropping all unverified descriptors
26107 right then. The bug was hidden because we would immediately
26108 fetch a directory from another dirserver, which would include the
26109 descriptors we just dropped.
26110 - When we're connecting to an OR and he's got a different nickname/key
26111 than we were expecting, only complain loudly if we're an OP or a
26112 dirserver. Complaining loudly to the OR admins just confuses them.
26113 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
26114 artificially capped at 500kB.
26117 Changes in version 0.0.9.8 - 2005-04-07
26118 o Bugfixes on 0.0.9.x:
26119 - We have a bug that I haven't found yet. Sometimes, very rarely,
26120 cpuworkers get stuck in the 'busy' state, even though the cpuworker
26121 thinks of itself as idle. This meant that no new circuits ever got
26122 established. Here's a workaround to kill any cpuworker that's been
26123 busy for more than 100 seconds.
26126 Changes in version 0.1.0.2-rc - 2005-04-01
26127 o Bugfixes on 0.1.0.1-rc:
26128 - Fixes on reachability detection:
26129 - Don't check for reachability while hibernating.
26130 - If ORPort is reachable but DirPort isn't, still publish the
26131 descriptor, but zero out DirPort until it's found reachable.
26132 - When building testing circs for ORPort testing, use only
26133 high-bandwidth nodes, so fewer circuits fail.
26134 - Complain about unreachable ORPort separately from unreachable
26135 DirPort, so the user knows what's going on.
26136 - Make sure we only conclude ORPort reachability if we didn't
26137 initiate the conn. Otherwise we could falsely conclude that
26138 we're reachable just because we connected to the guy earlier
26139 and he used that same pipe to extend to us.
26140 - Authdirservers shouldn't do ORPort reachability detection,
26141 since they're in clique mode, so it will be rare to find a
26142 server not already connected to them.
26143 - When building testing circuits, always pick middle hops running
26144 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
26145 bug. (This is a kludge; it will go away when 0.0.9.x becomes
26147 - When we decide we're reachable, actually publish our descriptor
26149 - Fix bug in redirectstream in the controller.
26150 - Fix the state descriptor strings so logs don't claim edge streams
26151 are in a different state than they actually are.
26152 - Use recent libevent features when possible (this only really affects
26153 win32 and osx right now, because the new libevent with these
26154 features hasn't been released yet). Add code to suppress spurious
26156 - Prevent possible segfault in connection_close_unattached_ap().
26157 - Fix newlines on torrc in win32.
26158 - Improve error msgs when tor-resolve fails.
26160 o Improvements on 0.0.9.x:
26161 - New experimental script tor/contrib/ExerciseServer.py (needs more
26162 work) that uses the controller interface to build circuits and
26163 fetch pages over them. This will help us bootstrap servers that
26164 have lots of capacity but haven't noticed it yet.
26165 - New experimental script tor/contrib/PathDemo.py (needs more work)
26166 that uses the controller interface to let you choose whole paths
26168 "<hostname>.<path,separated by dots>.<length of path>.path"
26169 - When we've connected to an OR and handshaked but didn't like
26170 the result, we were closing the conn without sending destroy
26171 cells back for pending circuits. Now send those destroys.
26174 Changes in version 0.0.9.7 - 2005-04-01
26175 o Bugfixes on 0.0.9.x:
26176 - Fix another race crash bug (thanks to Glenn Fink for reporting).
26177 - Compare identity to identity, not to nickname, when extending to
26178 a router not already in the directory. This was preventing us from
26179 extending to unknown routers. Oops.
26180 - Make sure to create OS X Tor user in <500 range, so we aren't
26181 creating actual system users.
26182 - Note where connection-that-hasn't-sent-end was marked, and fix
26183 a few really loud instances of this harmless bug (it's fixed more
26187 Changes in version 0.1.0.1-rc - 2005-03-28
26189 - Add reachability testing. Your Tor server will automatically try
26190 to see if its ORPort and DirPort are reachable from the outside,
26191 and it won't upload its descriptor until it decides they are.
26192 - Handle unavailable hidden services better. Handle slow or busy
26193 hidden services better.
26194 - Add support for CONNECTing through https proxies, with "HttpsProxy"
26196 - New exit policy: accept most low-numbered ports, rather than
26197 rejecting most low-numbered ports.
26198 - More Tor controller support (still experimental). See
26199 http://tor.eff.org/doc/control-spec.txt for all the new features,
26200 including signals to emulate unix signals from any platform;
26201 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
26202 closestream; closecircuit; etc.
26203 - Make nt services work and start on startup on win32 (based on
26204 patch by Matt Edman).
26205 - Add a new AddressMap config directive to rewrite incoming socks
26206 addresses. This lets you, for example, declare an implicit
26207 required exit node for certain sites.
26208 - Add a new TrackHostExits config directive to trigger addressmaps
26209 for certain incoming socks addresses -- for sites that break when
26210 your exit keeps changing (based on patch by Mike Perry).
26211 - Redo the client-side dns cache so it's just an addressmap too.
26212 - Notice when our IP changes, and reset stats/uptime/reachability.
26213 - When an application is using socks5, give him the whole variety of
26214 potential socks5 responses (connect refused, host unreachable, etc),
26215 rather than just "success" or "failure".
26216 - A more sane version numbering system. See
26217 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
26218 - New contributed script "exitlist": a simple python script to
26219 parse directories and find Tor nodes that exit to listed
26221 - New contributed script "privoxy-tor-toggle" to toggle whether
26222 Privoxy uses Tor. Seems to be configured for Debian by default.
26223 - Report HTTP reasons to client when getting a response from directory
26224 servers -- so you can actually know what went wrong.
26225 - New config option MaxAdvertisedBandwidth which lets you advertise
26226 a low bandwidthrate (to not attract as many circuits) while still
26227 allowing a higher bandwidthrate in reality.
26229 o Robustness/stability fixes:
26230 - Make Tor use Niels Provos's libevent instead of its current
26231 poll-but-sometimes-select mess. This will let us use faster async
26232 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
26234 - pthread support now too. This was forced because when we forked,
26235 we ended up wasting a lot of duplicate ram over time. Also switch
26236 to foo_r versions of some library calls to allow reentry and
26238 - Better handling for heterogeneous / unreliable nodes:
26239 - Annotate circuits w/ whether they aim to contain high uptime nodes
26240 and/or high capacity nodes. When building circuits, choose
26242 - This means that every single node in an intro rend circuit,
26243 not just the last one, will have a minimum uptime.
26244 - New config option LongLivedPorts to indicate application streams
26245 that will want high uptime circuits.
26246 - Servers reset uptime when a dir fetch entirely fails. This
26247 hopefully reflects stability of the server's network connectivity.
26248 - If somebody starts his tor server in Jan 2004 and then fixes his
26249 clock, don't make his published uptime be a year.
26250 - Reset published uptime when you wake up from hibernation.
26251 - Introduce a notion of 'internal' circs, which are chosen without
26252 regard to the exit policy of the last hop. Intro and rendezvous
26253 circs must be internal circs, to avoid leaking information. Resolve
26254 and connect streams can use internal circs if they want.
26255 - New circuit pooling algorithm: make sure to have enough circs around
26256 to satisfy any predicted ports, and also make sure to have 2 internal
26257 circs around if we've required internal circs lately (and with high
26258 uptime if we've seen that lately too).
26259 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
26260 which describes how often we retry making new circuits if current
26261 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
26262 how long we're willing to make use of an already-dirty circuit.
26263 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
26264 circ as necessary, if there are any completed ones lying around
26265 when we try to launch one.
26266 - Make hidden services try to establish a rendezvous for 30 seconds,
26267 rather than for n (where n=3) attempts to build a circuit.
26268 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
26269 "ShutdownWaitLength".
26270 - Try to be more zealous about calling connection_edge_end when
26271 things go bad with edge conns in connection.c.
26272 - Revise tor-spec to add more/better stream end reasons.
26273 - Revise all calls to connection_edge_end to avoid sending "misc",
26274 and to take errno into account where possible.
26277 - Fix a race condition that can trigger an assert, when we have a
26278 pending create cell and an OR connection fails right then.
26279 - Fix several double-mark-for-close bugs, e.g. where we were finding
26280 a conn for a cell even if that conn is already marked for close.
26281 - Make sequence of log messages when starting on win32 with no config
26282 file more reasonable.
26283 - When choosing an exit node for a new non-internal circ, don't take
26284 into account whether it'll be useful for any pending x.onion
26285 addresses -- it won't.
26286 - Turn addr_policy_compare from a tristate to a quadstate; this should
26287 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
26288 for google.com" problem.
26289 - Make "platform" string in descriptor more accurate for Win32 servers,
26290 so it's not just "unknown platform".
26291 - Fix an edge case in parsing config options (thanks weasel).
26292 If they say "--" on the commandline, it's not an option.
26293 - Reject odd-looking addresses at the client (e.g. addresses that
26294 contain a colon), rather than having the server drop them because
26296 - tor-resolve requests were ignoring .exit if there was a working circuit
26297 they could use instead.
26298 - REUSEADDR on normal platforms means you can rebind to the port
26299 right after somebody else has let it go. But REUSEADDR on win32
26300 means to let you bind to the port _even when somebody else
26301 already has it bound_! So, don't do that on Win32.
26302 - Change version parsing logic: a version is "obsolete" if it is not
26303 recommended and (1) there is a newer recommended version in the
26304 same series, or (2) there are no recommended versions in the same
26305 series, but there are some recommended versions in a newer series.
26306 A version is "new" if it is newer than any recommended version in
26308 - Stop most cases of hanging up on a socks connection without sending
26312 - Require BandwidthRate to be at least 20kB/s for servers.
26313 - When a dirserver causes you to give a warn, mention which dirserver
26315 - New config option DirAllowPrivateAddresses for authdirservers.
26316 Now by default they refuse router descriptors that have non-IP or
26317 private-IP addresses.
26318 - Stop publishing socksport in the directory, since it's not
26319 actually meant to be public. For compatibility, publish a 0 there
26321 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
26322 smart" value, that is low for servers and high for clients.
26323 - If our clock jumps forward by 100 seconds or more, assume something
26324 has gone wrong with our network and abandon all not-yet-used circs.
26325 - Warn when exit policy implicitly allows local addresses.
26326 - If we get an incredibly skewed timestamp from a dirserver mirror
26327 that isn't a verified OR, don't warn -- it's probably him that's
26329 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
26330 cookies to disk and doesn't log each web request to disk. (Thanks
26331 to Brett Carrington for pointing this out.)
26332 - When a client asks us for a dir mirror and we don't have one,
26333 launch an attempt to get a fresh one.
26334 - If we're hibernating and we get a SIGINT, exit immediately.
26335 - Add --with-dmalloc ./configure option, to track memory leaks.
26336 - And try to free all memory on closing, so we can detect what
26338 - Cache local dns resolves correctly even when they're .exit
26340 - Give a better warning when some other server advertises an
26341 ORPort that is actually an apache running ssl.
26342 - Add "opt hibernating 1" to server descriptor to make it clearer
26343 whether the server is hibernating.
26346 Changes in version 0.0.9.6 - 2005-03-24
26347 o Bugfixes on 0.0.9.x (crashes and asserts):
26348 - Add new end stream reasons to maintenance branch. Fix bug where
26349 reason (8) could trigger an assert. Prevent bug from recurring.
26350 - Apparently win32 stat wants paths to not end with a slash.
26351 - Fix assert triggers in assert_cpath_layer_ok(), where we were
26352 blowing away the circuit that conn->cpath_layer points to, then
26353 checking to see if the circ is well-formed. Backport check to make
26354 sure we dont use the cpath on a closed connection.
26355 - Prevent circuit_resume_edge_reading_helper() from trying to package
26356 inbufs for marked-for-close streams.
26357 - Don't crash on hup if your options->address has become unresolvable.
26358 - Some systems (like OS X) sometimes accept() a connection and tell
26359 you the remote host is 0.0.0.0:0. If this happens, due to some
26360 other mis-features, we get confused; so refuse the conn for now.
26362 o Bugfixes on 0.0.9.x (other):
26363 - Fix harmless but scary "Unrecognized content encoding" warn message.
26364 - Add new stream error reason: TORPROTOCOL reason means "you are not
26365 speaking a version of Tor I understand; say bye-bye to your stream."
26366 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
26367 into the future, now that we are more tolerant of skew. This
26368 resolves a bug where a Tor server would refuse to cache a directory
26369 because all the directories it gets are too far in the future;
26370 yet the Tor server never logs any complaints about clock skew.
26371 - Mac packaging magic: make man pages useable, and do not overwrite
26372 existing torrc files.
26373 - Make OS X log happily to /var/log/tor/tor.log
26376 Changes in version 0.0.9.5 - 2005-02-22
26377 o Bugfixes on 0.0.9.x:
26378 - Fix an assert race at exit nodes when resolve requests fail.
26379 - Stop picking unverified dir mirrors--it only leads to misery.
26380 - Patch from Matt Edman to make NT services work better. Service
26381 support is still not compiled into the executable by default.
26382 - Patch from Dmitri Bely so the Tor service runs better under
26383 the win32 SYSTEM account.
26384 - Make tor-resolve actually work (?) on Win32.
26385 - Fix a sign bug when getrlimit claims to have 4+ billion
26386 file descriptors available.
26387 - Stop refusing to start when bandwidthburst == bandwidthrate.
26388 - When create cells have been on the onion queue more than five
26389 seconds, just send back a destroy and take them off the list.
26392 Changes in version 0.0.9.4 - 2005-02-03
26393 o Bugfixes on 0.0.9:
26394 - Fix an assert bug that took down most of our servers: when
26395 a server claims to have 1 GB of bandwidthburst, don't
26397 - Don't crash as badly if we have spawned the max allowed number
26398 of dnsworkers, or we're out of file descriptors.
26399 - Block more file-sharing ports in the default exit policy.
26400 - MaxConn is now automatically set to the hard limit of max
26401 file descriptors we're allowed (ulimit -n), minus a few for
26403 - Give a clearer message when servers need to raise their
26404 ulimit -n when they start running out of file descriptors.
26405 - SGI Compatibility patches from Jan Schaumann.
26406 - Tolerate a corrupt cached directory better.
26407 - When a dirserver hasn't approved your server, list which one.
26408 - Go into soft hibernation after 95% of the bandwidth is used,
26409 not 99%. This is especially important for daily hibernators who
26410 have a small accounting max. Hopefully it will result in fewer
26411 cut connections when the hard hibernation starts.
26412 - Load-balance better when using servers that claim more than
26413 800kB/s of capacity.
26414 - Make NT services work (experimental, only used if compiled in).
26417 Changes in version 0.0.9.3 - 2005-01-21
26418 o Bugfixes on 0.0.9:
26419 - Backport the cpu use fixes from main branch, so busy servers won't
26420 need as much processor time.
26421 - Work better when we go offline and then come back, or when we
26422 run Tor at boot before the network is up. We do this by
26423 optimistically trying to fetch a new directory whenever an
26424 application request comes in and we think we're offline -- the
26425 human is hopefully a good measure of when the network is back.
26426 - Backport some minimal hidserv bugfixes: keep rend circuits open as
26427 long as you keep using them; actually publish hidserv descriptors
26428 shortly after they change, rather than waiting 20-40 minutes.
26429 - Enable Mac startup script by default.
26430 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
26431 - When you update AllowUnverifiedNodes or FirewallPorts via the
26432 controller's setconf feature, we were always appending, never
26434 - When you update HiddenServiceDir via setconf, it was screwing up
26435 the order of reading the lines, making it fail.
26436 - Do not rewrite a cached directory back to the cache; otherwise we
26437 will think it is recent and not fetch a newer one on startup.
26438 - Workaround for webservers that lie about Content-Encoding: Tor
26439 now tries to autodetect compressed directories and compression
26440 itself. This lets us Proxypass dir fetches through apache.
26443 Changes in version 0.0.9.2 - 2005-01-04
26444 o Bugfixes on 0.0.9 (crashes and asserts):
26445 - Fix an assert on startup when the disk is full and you're logging
26447 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
26448 style address, then we'd crash.
26449 - Fix an assert trigger when the running-routers string we get from
26450 a dirserver is broken.
26451 - Make worker threads start and run on win32. Now win32 servers
26453 - Bandaid (not actually fix, but now it doesn't crash) an assert
26454 where the dns worker dies mysteriously and the main Tor process
26455 doesn't remember anything about the address it was resolving.
26457 o Bugfixes on 0.0.9 (Win32):
26458 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
26459 name out of the warning/assert messages.
26460 - Fix a superficial "unhandled error on read" bug on win32.
26461 - The win32 installer no longer requires a click-through for our
26462 license, since our Free Software license grants rights but does not
26464 - Win32: When connecting to a dirserver fails, try another one
26465 immediately. (This was already working for non-win32 Tors.)
26466 - Stop trying to parse $HOME on win32 when hunting for default
26468 - Make tor-resolve.c work on win32 by calling network_init().
26470 o Bugfixes on 0.0.9 (other):
26471 - Make 0.0.9.x build on Solaris again.
26472 - Due to a fencepost error, we were blowing away the \n when reporting
26473 confvalue items in the controller. So asking for multiple config
26474 values at once couldn't work.
26475 - When listing circuits that are pending on an opening OR connection,
26476 if we're an OR we were listing circuits that *end* at us as
26477 being pending on every listener, dns/cpu worker, etc. Stop that.
26478 - Dirservers were failing to create 'running-routers' or 'directory'
26479 strings if we had more than some threshold of routers. Fix them so
26480 they can handle any number of routers.
26481 - Fix a superficial "Duplicate mark for close" bug.
26482 - Stop checking for clock skew for OR connections, even for servers.
26483 - Fix a fencepost error that was chopping off the last letter of any
26484 nickname that is the maximum allowed nickname length.
26485 - Update URLs in log messages so they point to the new website.
26486 - Fix a potential problem in mangling server private keys while
26487 writing to disk (not triggered yet, as far as we know).
26488 - Include the licenses for other free software we include in Tor,
26489 now that we're shipping binary distributions more regularly.
26492 Changes in version 0.0.9.1 - 2004-12-15
26493 o Bugfixes on 0.0.9:
26494 - Make hibernation actually work.
26495 - Make HashedControlPassword config option work.
26496 - When we're reporting event circuit status to a controller,
26497 don't use the stream status code.
26500 Changes in version 0.0.9 - 2004-12-12
26502 - Clean up manpage and torrc.sample file.
26503 - Clean up severities and text of log warnings.
26505 - Make servers trigger an assert when they enter hibernation.
26508 Changes in version 0.0.9rc7 - 2004-12-08
26509 o Bugfixes on 0.0.9rc:
26510 - Fix a stack-trashing crash when an exit node begins hibernating.
26511 - Avoid looking at unallocated memory while considering which
26512 ports we need to build circuits to cover.
26513 - Stop a sigpipe: when an 'end' cell races with eof from the app,
26514 we shouldn't hold-open-until-flush if the eof arrived first.
26515 - Fix a bug with init_cookie_authentication() in the controller.
26516 - When recommending new-format log lines, if the upper bound is
26517 LOG_ERR, leave it implicit.
26519 o Bugfixes on 0.0.8.1:
26520 - Fix a whole slew of memory leaks.
26521 - Fix isspace() and friends so they still make Solaris happy
26522 but also so they don't trigger asserts on win32.
26523 - Fix parse_iso_time on platforms without strptime (eg win32).
26524 - win32: tolerate extra "readable" events better.
26525 - win32: when being multithreaded, leave parent fdarray open.
26526 - Make unit tests work on win32.
26529 Changes in version 0.0.9rc6 - 2004-12-06
26530 o Bugfixes on 0.0.9pre:
26531 - Clean up some more integer underflow opportunities (not exploitable
26533 - While hibernating, hup should not regrow our listeners.
26534 - Send an end to the streams we close when we hibernate, rather
26535 than just chopping them off.
26536 - React to eof immediately on non-open edge connections.
26538 o Bugfixes on 0.0.8.1:
26539 - Calculate timeout for waiting for a connected cell from the time
26540 we sent the begin cell, not from the time the stream started. If
26541 it took a long time to establish the circuit, we would time out
26542 right after sending the begin cell.
26543 - Fix router_compare_addr_to_addr_policy: it was not treating a port
26544 of * as always matching, so we were picking reject *:* nodes as
26545 exit nodes too. Oops.
26548 - New circuit building strategy: keep a list of ports that we've
26549 used in the past 6 hours, and always try to have 2 circuits open
26550 or on the way that will handle each such port. Seed us with port
26551 80 so web users won't complain that Tor is "slow to start up".
26552 - Make kill -USR1 dump more useful stats about circuits.
26553 - When warning about retrying or giving up, print the address, so
26554 the user knows which one it's talking about.
26555 - If you haven't used a clean circuit in an hour, throw it away,
26556 just to be on the safe side. (This means after 6 hours a totally
26557 unused Tor client will have no circuits open.)
26560 Changes in version 0.0.9rc5 - 2004-12-01
26561 o Bugfixes on 0.0.8.1:
26562 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
26563 - Let resolve conns retry/expire also, rather than sticking around
26565 - If we are using select, make sure we stay within FD_SETSIZE.
26567 o Bugfixes on 0.0.9pre:
26568 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
26569 but doesn't seem to be currently; thanks to Ilja van Sprundel for
26571 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
26572 instead. Impose minima and maxima for all *Period options; impose
26573 even tighter maxima for fetching if we are a caching dirserver.
26574 Clip rather than rejecting.
26575 - Fetch cached running-routers from servers that serve it (that is,
26576 authdirservers and servers running 0.0.9rc5-cvs or later.)
26579 - Accept *:706 (silc) in default exit policy.
26580 - Implement new versioning format for post 0.1.
26581 - Support "foo.nickname.exit" addresses, to let Alice request the
26582 address "foo" as viewed by exit node "nickname". Based on a patch
26584 - Make tor --version --version dump the cvs Id of every file.
26587 Changes in version 0.0.9rc4 - 2004-11-28
26588 o Bugfixes on 0.0.8.1:
26589 - Make windows sockets actually non-blocking (oops), and handle
26590 win32 socket errors better.
26592 o Bugfixes on 0.0.9rc1:
26593 - Actually catch the -USR2 signal.
26596 Changes in version 0.0.9rc3 - 2004-11-25
26597 o Bugfixes on 0.0.8.1:
26598 - Flush the log file descriptor after we print "Tor opening log file",
26599 so we don't see those messages days later.
26601 o Bugfixes on 0.0.9rc1:
26602 - Make tor-resolve work again.
26603 - Avoid infinite loop in tor-resolve if tor hangs up on it.
26604 - Fix an assert trigger for clients/servers handling resolves.
26607 Changes in version 0.0.9rc2 - 2004-11-24
26608 o Bugfixes on 0.0.9rc1:
26609 - I broke socks5 support while fixing the eof bug.
26610 - Allow unitless bandwidths and intervals; they default to bytes
26612 - New servers don't start out hibernating; they are active until
26613 they run out of bytes, so they have a better estimate of how
26614 long it takes, and so their operators can know they're working.
26617 Changes in version 0.0.9rc1 - 2004-11-23
26618 o Bugfixes on 0.0.8.1:
26619 - Finally fix a bug that's been plaguing us for a year:
26620 With high load, circuit package window was reaching 0. Whenever
26621 we got a circuit-level sendme, we were reading a lot on each
26622 socket, but only writing out a bit. So we would eventually reach
26623 eof. This would be noticed and acted on even when there were still
26624 bytes sitting in the inbuf.
26625 - When poll() is interrupted, we shouldn't believe the revents values.
26627 o Bugfixes on 0.0.9pre6:
26628 - Fix hibernate bug that caused pre6 to be broken.
26629 - Don't keep rephist info for routers that haven't had activity for
26630 24 hours. (This matters now that clients have keys, since we track
26632 - Never call close_temp_logs while validating log options.
26633 - Fix backslash-escaping on tor.sh.in and torctl.in.
26636 - Implement weekly/monthly/daily accounting: now you specify your
26637 hibernation properties by
26638 AccountingMax N bytes|KB|MB|GB|TB
26639 AccountingStart day|week|month [day] HH:MM
26640 Defaults to "month 1 0:00".
26641 - Let bandwidth and interval config options be specified as 5 bytes,
26642 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
26643 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
26644 get back to normal.)
26645 - If your requested entry or exit node has advertised bandwidth 0,
26647 - Be more greedy about filling up relay cells -- we try reading again
26648 once we've processed the stuff we read, in case enough has arrived
26649 to fill the last cell completely.
26650 - Apply NT service patch from Osamu Fujino. Still needs more work.
26653 Changes in version 0.0.9pre6 - 2004-11-15
26654 o Bugfixes on 0.0.8.1:
26655 - Fix assert failure on malformed socks4a requests.
26656 - Use identity comparison, not nickname comparison, to choose which
26657 half of circuit-ID-space each side gets to use. This is needed
26658 because sometimes we think of a router as a nickname, and sometimes
26659 as a hex ID, and we can't predict what the other side will do.
26660 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
26661 write() call will fail and we handle it there.
26662 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
26663 and smartlist_len, which are two major profiling offenders.
26665 o Bugfixes on 0.0.9pre5:
26666 - Fix a bug in read_all that was corrupting config files on windows.
26667 - When we're raising the max number of open file descriptors to
26668 'unlimited', don't log that we just raised it to '-1'.
26669 - Include event code with events, as required by control-spec.txt.
26670 - Don't give a fingerprint when clients do --list-fingerprint:
26671 it's misleading, because it will never be the same again.
26672 - Stop using strlcpy in tor_strndup, since it was slowing us
26674 - Remove warn on startup about missing cached-directory file.
26675 - Make kill -USR1 work again.
26676 - Hibernate if we start tor during the "wait for wakeup-time" phase
26677 of an accounting interval. Log our hibernation plans better.
26678 - Authoritative dirservers now also cache their directory, so they
26679 have it on start-up.
26682 - Fetch running-routers; cache running-routers; compress
26683 running-routers; serve compressed running-routers.z
26684 - Add NSI installer script contributed by J Doe.
26685 - Commit VC6 and VC7 workspace/project files.
26686 - Commit a tor.spec for making RPM files, with help from jbash.
26687 - Add contrib/torctl.in contributed by Glenn Fink.
26688 - Implement the control-spec's SAVECONF command, to write your
26689 configuration to torrc.
26690 - Get cookie authentication for the controller closer to working.
26691 - Include control-spec.txt in the tarball.
26692 - When set_conf changes our server descriptor, upload a new copy.
26693 But don't upload it too often if there are frequent changes.
26694 - Document authentication config in man page, and document signals
26696 - Clean up confusing parts of man page and torrc.sample.
26697 - Make expand_filename handle ~ and ~username.
26698 - Use autoconf to enable largefile support where necessary. Use
26699 ftello where available, since ftell can fail at 2GB.
26700 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
26701 log more informatively.
26702 - Give a slightly more useful output for "tor -h".
26703 - Refuse application socks connections to port 0.
26704 - Check clock skew for verified servers, but allow unverified
26705 servers and clients to have any clock skew.
26706 - Break DirFetchPostPeriod into:
26707 - DirFetchPeriod for fetching full directory,
26708 - StatusFetchPeriod for fetching running-routers,
26709 - DirPostPeriod for posting server descriptor,
26710 - RendPostPeriod for posting hidden service descriptors.
26711 - Make sure the hidden service descriptors are at a random offset
26712 from each other, to hinder linkability.
26715 Changes in version 0.0.9pre5 - 2004-11-09
26716 o Bugfixes on 0.0.9pre4:
26717 - Fix a seg fault in unit tests (doesn't affect main program).
26718 - Fix an assert bug where a hidden service provider would fail if
26719 the first hop of his rendezvous circuit was down.
26720 - Hidden service operators now correctly handle version 1 style
26721 INTRODUCE1 cells (nobody generates them still, so not a critical
26723 - If do_hup fails, actually notice.
26724 - Handle more errnos from accept() without closing the listener.
26725 Some OpenBSD machines were closing their listeners because
26726 they ran out of file descriptors.
26727 - Send resolve cells to exit routers that are running a new
26728 enough version of the resolve code to work right.
26729 - Better handling of winsock includes on non-MSV win32 compilers.
26730 - Some people had wrapped their tor client/server in a script
26731 that would restart it whenever it died. This did not play well
26732 with our "shut down if your version is obsolete" code. Now people
26733 don't fetch a new directory if their local cached version is
26735 - Make our autogen.sh work on ksh as well as bash.
26738 - Hibernation: New config option "AccountingMaxKB" lets you
26739 set how many KBytes per month you want to allow your server to
26740 consume. Rather than spreading those bytes out evenly over the
26741 month, we instead hibernate for some of the month and pop up
26742 at a deterministic time, work until the bytes are consumed, then
26743 hibernate again. Config option "MonthlyAccountingStart" lets you
26744 specify which day of the month your billing cycle starts on.
26745 - Control interface: a separate program can now talk to your
26746 client/server over a socket, and get/set config options, receive
26747 notifications of circuits and streams starting/finishing/dying,
26748 bandwidth used, etc. The next step is to get some GUIs working.
26749 Let us know if you want to help out. See doc/control-spec.txt .
26750 - Ship a contrib/tor-control.py as an example script to interact
26751 with the control port.
26752 - "tor --hash-password zzyxz" will output a salted password for
26753 use in authenticating to the control interface.
26754 - New log format in config:
26755 "Log minsev[-maxsev] stdout|stderr|syslog" or
26756 "Log minsev[-maxsev] file /var/foo"
26759 - DirPolicy config option, to let people reject incoming addresses
26760 from their dirserver.
26761 - "tor --list-fingerprint" will list your identity key fingerprint
26763 - Add "pass" target for RedirectExit, to make it easier to break
26764 out of a sequence of RedirectExit rules.
26765 - Clients now generate a TLS cert too, in preparation for having
26766 them act more like real nodes.
26767 - Ship src/win32/ in the tarball, so people can use it to build.
26768 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
26770 - New "router-status" line in directory, to better bind each verified
26771 nickname to its identity key.
26772 - Deprecate unofficial config option abbreviations, and abbreviations
26773 not on the command line.
26774 - Add a pure-C tor-resolve implementation.
26775 - Use getrlimit and friends to ensure we can reach MaxConn (currently
26776 1024) file descriptors.
26778 o Code security improvements, inspired by Ilja:
26779 - Replace sprintf with snprintf. (I think they were all safe, but
26781 - Replace strcpy/strncpy with strlcpy in more places.
26782 - Avoid strcat; use snprintf or strlcat instead.
26783 - snprintf wrapper with consistent (though not C99) overflow behavior.
26786 Changes in version 0.0.9pre4 - 2004-10-17
26787 o Bugfixes on 0.0.9pre3:
26788 - If the server doesn't specify an exit policy, use the real default
26789 exit policy, not reject *:*.
26790 - Ignore fascistfirewall when uploading/downloading hidden service
26791 descriptors, since we go through Tor for those; and when using
26792 an HttpProxy, since we assume it can reach them all.
26793 - When looking for an authoritative dirserver, use only the ones
26794 configured at boot. Don't bother looking in the directory.
26795 - The rest of the fix for get_default_conf_file() on older win32.
26796 - Make 'Routerfile' config option obsolete.
26799 - New 'MyFamily nick1,...' config option for a server to
26800 specify other servers that shouldn't be used in the same circuit
26801 with it. Only believed if nick1 also specifies us.
26802 - New 'NodeFamily nick1,nick2,...' config option for a client to
26803 specify nodes that it doesn't want to use in the same circuit.
26804 - New 'Redirectexit pattern address:port' config option for a
26805 server to redirect exit connections, e.g. to a local squid.
26808 Changes in version 0.0.9pre3 - 2004-10-13
26809 o Bugfixes on 0.0.8.1:
26810 - Better torrc example lines for dirbindaddress and orbindaddress.
26811 - Improved bounds checking on parsed ints (e.g. config options and
26812 the ones we find in directories.)
26813 - Better handling of size_t vs int, so we're more robust on 64
26815 - Fix the rest of the bug where a newly started OR would appear
26816 as unverified even after we've added his fingerprint and hupped
26818 - Fix a bug from 0.0.7: when read() failed on a stream, we would
26819 close it without sending back an end. So 'connection refused'
26820 would simply be ignored and the user would get no response.
26822 o Bugfixes on 0.0.9pre2:
26823 - Serving the cached-on-disk directory to people is bad. We now
26824 provide no directory until we've fetched a fresh one.
26825 - Workaround for bug on windows where cached-directories get crlf
26827 - Make get_default_conf_file() work on older windows too.
26828 - If we write a *:* exit policy line in the descriptor, don't write
26829 any more exit policy lines.
26832 - Use only 0.0.9pre1 and later servers for resolve cells.
26833 - Make the dirservers file obsolete.
26834 - Include a dir-signing-key token in directories to tell the
26835 parsing entity which key is being used to sign.
26836 - Remove the built-in bulky default dirservers string.
26837 - New config option "Dirserver %s:%d [fingerprint]", which can be
26838 repeated as many times as needed. If no dirservers specified,
26839 default to moria1,moria2,tor26.
26840 - Make moria2 advertise a dirport of 80, so people behind firewalls
26841 will be able to get a directory.
26842 - Http proxy support
26843 - Dirservers translate requests for http://%s:%d/x to /x
26844 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
26845 be routed through this host.
26846 - Clients ask for /tor/x rather than /x for new enough dirservers.
26847 This way we can one day coexist peacefully with apache.
26848 - Clients specify a "Host: %s%d" http header, to be compatible
26849 with more proxies, and so running squid on an exit node can work.
26852 Changes in version 0.0.8.1 - 2004-10-13
26854 - Fix a seg fault that can be triggered remotely for Tor
26855 clients/servers with an open dirport.
26856 - Fix a rare assert trigger, where routerinfos for entries in
26857 our cpath would expire while we're building the path.
26858 - Fix a bug in OutboundBindAddress so it (hopefully) works.
26859 - Fix a rare seg fault for people running hidden services on
26860 intermittent connections.
26861 - Fix a bug in parsing opt keywords with objects.
26862 - Fix a stale pointer assert bug when a stream detaches and
26864 - Fix a string format vulnerability (probably not exploitable)
26865 in reporting stats locally.
26866 - Fix an assert trigger: sometimes launching circuits can fail
26867 immediately, e.g. because too many circuits have failed recently.
26868 - Fix a compile warning on 64 bit platforms.
26871 Changes in version 0.0.9pre2 - 2004-10-03
26873 - Make fetching a cached directory work for 64-bit platforms too.
26874 - Make zlib.h a required header, not an optional header.
26877 Changes in version 0.0.9pre1 - 2004-10-01
26879 - Stop using separate defaults for no-config-file and
26880 empty-config-file. Now you have to explicitly turn off SocksPort,
26881 if you don't want it open.
26882 - Fix a bug in OutboundBindAddress so it (hopefully) works.
26883 - Improve man page to mention more of the 0.0.8 features.
26884 - Fix a rare seg fault for people running hidden services on
26885 intermittent connections.
26886 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
26888 - Fix more dns related bugs: send back resolve_failed and end cells
26889 more reliably when the resolve fails, rather than closing the
26890 circuit and then trying to send the cell. Also attach dummy resolve
26891 connections to a circuit *before* calling dns_resolve(), to fix
26892 a bug where cached answers would never be sent in RESOLVED cells.
26893 - When we run out of disk space, or other log writing error, don't
26894 crash. Just stop logging to that log and continue.
26895 - We were starting to daemonize before we opened our logs, so if
26896 there were any problems opening logs, we would complain to stderr,
26897 which wouldn't work, and then mysteriously exit.
26898 - Fix a rare bug where sometimes a verified OR would connect to us
26899 before he'd uploaded his descriptor, which would cause us to
26900 assign conn->nickname as though he's unverified. Now we look through
26901 the fingerprint list to see if he's there.
26902 - Fix a rare assert trigger, where routerinfos for entries in
26903 our cpath would expire while we're building the path.
26906 - Clients can ask dirservers for /dir.z to get a compressed version
26907 of the directory. Only works for servers running 0.0.9, of course.
26908 - Make clients cache directories and use them to seed their router
26909 lists at startup. This means clients have a datadir again.
26910 - Configuration infrastructure support for warning on obsolete
26912 - Respond to content-encoding headers by trying to uncompress as
26914 - Reply with a deflated directory when a client asks for "dir.z".
26915 We could use allow-encodings instead, but allow-encodings isn't
26916 specified in HTTP 1.0.
26917 - Raise the max dns workers from 50 to 100.
26918 - Discourage people from setting their dirfetchpostperiod more often
26919 than once per minute.
26920 - Protect dirservers from overzealous descriptor uploading -- wait
26921 10 seconds after directory gets dirty, before regenerating.
26924 Changes in version 0.0.8 - 2004-08-25
26925 o Port it to SunOS 5.9 / Athena
26928 Changes in version 0.0.8rc2 - 2004-08-20
26929 o Make it compile on cygwin again.
26930 o When picking unverified routers, skip those with low uptime and/or
26931 low bandwidth, depending on what properties you care about.
26934 Changes in version 0.0.8rc1 - 2004-08-18
26935 o Changes from 0.0.7.3:
26937 - Fix assert triggers: if the other side returns an address 0.0.0.0,
26938 don't put it into the client dns cache.
26939 - If a begin failed due to exit policy, but we believe the IP address
26940 should have been allowed, switch that router to exitpolicy reject *:*
26941 until we get our next directory.
26943 - Clients choose nodes proportional to advertised bandwidth.
26944 - Avoid using nodes with low uptime as introduction points.
26945 - Handle servers with dynamic IP addresses: don't replace
26946 options->Address with the resolved one at startup, and
26947 detect our address right before we make a routerinfo each time.
26948 - 'FascistFirewall' option to pick dirservers and ORs on specific
26949 ports; plus 'FirewallPorts' config option to tell FascistFirewall
26950 which ports are open. (Defaults to 80,443)
26951 - Be more aggressive about trying to make circuits when the network
26952 has changed (e.g. when you unsuspend your laptop).
26953 - Check for time skew on http headers; report date in response to
26955 - If the entrynode config line has only one node, don't pick it as
26957 - Add strict{entry|exit}nodes config options. If set to 1, then
26958 we refuse to build circuits that don't include the specified entry
26960 - OutboundBindAddress config option, to bind to a specific
26961 IP address for outgoing connect()s.
26962 - End truncated log entries (e.g. directories) with "[truncated]".
26964 o Patches to 0.0.8preX:
26966 - Patches to compile and run on win32 again (maybe)?
26967 - Fix crash when looking for ~/.torrc with no $HOME set.
26968 - Fix a race bug in the unit tests.
26969 - Handle verified/unverified name collisions better when new
26970 routerinfo's arrive in a directory.
26971 - Sometimes routers were getting entered into the stats before
26972 we'd assigned their identity_digest. Oops.
26973 - Only pick and establish intro points after we've gotten a
26976 - AllowUnverifiedNodes config option to let circuits choose no-name
26977 routers in entry,middle,exit,introduction,rendezvous positions.
26978 Allow middle and rendezvous positions by default.
26979 - Add a man page for tor-resolve.
26982 Changes in version 0.0.7.3 - 2004-08-12
26983 o Stop dnsworkers from triggering an assert failure when you
26984 ask them to resolve the host "".
26987 Changes in version 0.0.8pre3 - 2004-08-09
26988 o Changes from 0.0.7.2:
26989 - Allow multiple ORs with same nickname in routerlist -- now when
26990 people give us one identity key for a nickname, then later
26991 another, we don't constantly complain until the first expires.
26992 - Remember used bandwidth (both in and out), and publish 15-minute
26993 snapshots for the past day into our descriptor.
26994 - You can now fetch $DIRURL/running-routers to get just the
26995 running-routers line, not the whole descriptor list. (But
26996 clients don't use this yet.)
26997 - When people mistakenly use Tor as an http proxy, point them
26998 at the tor-doc.html rather than the INSTALL.
26999 - Remove our mostly unused -- and broken -- hex_encode()
27000 function. Use base16_encode() instead. (Thanks to Timo Lindfors
27001 for pointing out this bug.)
27002 - Rotate onion keys every 12 hours, not every 2 hours, so we have
27003 fewer problems with people using the wrong key.
27004 - Change the default exit policy to reject the default edonkey,
27005 kazaa, gnutella ports.
27006 - Add replace_file() to util.[ch] to handle win32's rename().
27008 o Changes from 0.0.8preX:
27009 - Fix two bugs in saving onion keys to disk when rotating, so
27010 hopefully we'll get fewer people using old onion keys.
27011 - Fix an assert error that was making SocksPolicy not work.
27012 - Be willing to expire routers that have an open dirport -- it's
27013 just the authoritative dirservers we want to not forget.
27014 - Reject tor-resolve requests for .onion addresses early, so we
27015 don't build a whole rendezvous circuit and then fail.
27016 - When you're warning a server that he's unverified, don't cry
27017 wolf unpredictably.
27018 - Fix a race condition: don't try to extend onto a connection
27019 that's still handshaking.
27020 - For servers in clique mode, require the conn to be open before
27021 you'll choose it for your path.
27022 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
27023 end relay cell, etc.
27024 - Measure bandwidth capacity over the last 24 hours, not just 12
27025 - Bugfix: authoritative dirservers were making and signing a new
27026 directory for each client, rather than reusing the cached one.
27029 Changes in version 0.0.8pre2 - 2004-08-04
27030 o Changes from 0.0.7.2:
27032 - Check directory signature _before_ you decide whether you're
27033 you're running an obsolete version and should exit.
27034 - Check directory signature _before_ you parse the running-routers
27035 list to decide who's running or verified.
27036 - Bugfixes and features:
27037 - Check return value of fclose while writing to disk, so we don't
27038 end up with broken files when servers run out of disk space.
27039 - Log a warning if the user uses an unsafe socks variant, so people
27040 are more likely to learn about privoxy or socat.
27041 - Dirservers now include RFC1123-style dates in the HTTP headers,
27042 which one day we will use to better detect clock skew.
27044 o Changes from 0.0.8pre1:
27045 - Make it compile without warnings again on win32.
27046 - Log a warning if you're running an unverified server, to let you
27047 know you might want to get it verified.
27048 - Only pick a default nickname if you plan to be a server.
27051 Changes in version 0.0.8pre1 - 2004-07-23
27053 - Made our unit tests compile again on OpenBSD 3.5, and tor
27054 itself compile again on OpenBSD on a sparc64.
27055 - We were neglecting milliseconds when logging on win32, so
27056 everything appeared to happen at the beginning of each second.
27058 o Protocol changes:
27059 - 'Extend' relay cell payloads now include the digest of the
27060 intended next hop's identity key. Now we can verify that we're
27061 extending to the right router, and also extend to routers we
27062 hadn't heard of before.
27065 - Tor nodes can now act as relays (with an advertised ORPort)
27066 without being manually verified by the dirserver operators.
27067 - Uploaded descriptors of unverified routers are now accepted
27068 by the dirservers, and included in the directory.
27069 - Verified routers are listed by nickname in the running-routers
27070 list; unverified routers are listed as "$<fingerprint>".
27071 - We now use hash-of-identity-key in most places rather than
27072 nickname or addr:port, for improved security/flexibility.
27073 - To avoid Sybil attacks, paths still use only verified servers.
27074 But now we have a chance to play around with hybrid approaches.
27075 - Nodes track bandwidth usage to estimate capacity (not used yet).
27076 - ClientOnly option for nodes that never want to become servers.
27077 - Directory caching.
27078 - "AuthoritativeDir 1" option for the official dirservers.
27079 - Now other nodes (clients and servers) will cache the latest
27080 directory they've pulled down.
27081 - They can enable their DirPort to serve it to others.
27082 - Clients will pull down a directory from any node with an open
27083 DirPort, and check the signature/timestamp correctly.
27084 - Authoritative dirservers now fetch directories from other
27085 authdirservers, to stay better synced.
27086 - Running-routers list tells who's down also, along with noting
27087 if they're verified (listed by nickname) or unverified (listed
27089 - Allow dirservers to serve running-router list separately.
27090 This isn't used yet.
27091 - ORs connect-on-demand to other ORs
27092 - If you get an extend cell to an OR you're not connected to,
27093 connect, handshake, and forward the create cell.
27094 - The authoritative dirservers stay connected to everybody,
27095 and everybody stays connected to 0.0.7 servers, but otherwise
27096 clients/servers expire unused connections after 5 minutes.
27097 - When servers get a sigint, they delay 30 seconds (refusing new
27098 connections) then exit. A second sigint causes immediate exit.
27099 - File and name management:
27100 - Look for .torrc if no CONFDIR "torrc" is found.
27101 - If no datadir is defined, then choose, make, and secure ~/.tor
27103 - If torrc not found, exitpolicy reject *:*.
27104 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
27105 - If no nickname is defined, derive default from hostname.
27106 - Rename secret key files, e.g. identity.key -> secret_id_key,
27107 to discourage people from mailing their identity key to tor-ops.
27108 - Refuse to build a circuit before the directory has arrived --
27109 it won't work anyway, since you won't know the right onion keys
27111 - Try other dirservers immediately if the one you try is down. This
27112 should tolerate down dirservers better now.
27113 - Parse tor version numbers so we can do an is-newer-than check
27114 rather than an is-in-the-list check.
27115 - New socks command 'resolve', to let us shim gethostbyname()
27117 - A 'tor_resolve' script to access the socks resolve functionality.
27118 - A new socks-extensions.txt doc file to describe our
27119 interpretation and extensions to the socks protocols.
27120 - Add a ContactInfo option, which gets published in descriptor.
27121 - Publish OR uptime in descriptor (and thus in directory) too.
27122 - Write tor version at the top of each log file
27123 - New docs in the tarball:
27125 - Document that you should proxy your SSL traffic too.
27128 Changes in version 0.0.7.2 - 2004-07-07
27129 o A better fix for the 0.0.0.0 problem, that will hopefully
27130 eliminate the remaining related assertion failures.
27133 Changes in version 0.0.7.1 - 2004-07-04
27134 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
27135 since internally we use 0.0.0.0 to signify "not yet resolved".
27138 Changes in version 0.0.7 - 2004-06-07
27139 o Updated the man page to reflect the new features.
27142 Changes in version 0.0.7rc2 - 2004-06-06
27143 o Changes from 0.0.7rc1:
27144 - Make it build on Win32 again.
27145 o Changes from 0.0.6.2:
27146 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
27150 Changes in version 0.0.7rc1 - 2004-06-02
27152 - On sighup, we were adding another log without removing the first
27153 one. So log messages would get duplicated n times for n sighups.
27154 - Several cases of using a connection after we'd freed it. The
27155 problem was that connections that are pending resolve are in both
27156 the pending_resolve tree, and also the circuit's resolving_streams
27157 list. When you want to remove one, you must remove it from both.
27158 - Fix a double-mark-for-close where an end cell arrived for a
27159 resolving stream, and then the resolve failed.
27160 - Check directory signatures based on name of signer, not on whom
27161 we got the directory from. This will let us cache directories more
27164 - Crank up some of our constants to handle more users.
27167 Changes in version 0.0.7pre1 - 2004-06-02
27168 o Fixes for crashes and other obnoxious bugs:
27169 - Fix an epipe bug: sometimes when directory connections failed
27170 to connect, we would give them a chance to flush before closing
27172 - When we detached from a circuit because of resolvefailed, we
27173 would immediately try the same circuit twice more, and then
27174 give up on the resolve thinking we'd tried three different
27176 - Limit the number of intro circuits we'll attempt to build for a
27177 hidden service per 15-minute period.
27178 - Check recommended-software string *early*, before actually parsing
27179 the directory. Thus we can detect an obsolete version and exit,
27180 even if the new directory format doesn't parse.
27181 o Fixes for security bugs:
27182 - Remember which nodes are dirservers when you startup, and if a
27183 random OR enables his dirport, don't automatically assume he's
27184 a trusted dirserver.
27186 - Directory connections were asking the wrong poll socket to
27187 start writing, and not asking themselves to start writing.
27188 - When we detached from a circuit because we sent a begin but
27189 didn't get a connected, we would use it again the first time;
27190 but after that we would correctly switch to a different one.
27191 - Stop warning when the first onion decrypt attempt fails; they
27192 will sometimes legitimately fail now that we rotate keys.
27193 - Override unaligned-access-ok check when $host_cpu is ia64 or
27194 arm. Apparently they allow it but the kernel whines.
27195 - Dirservers try to reconnect periodically too, in case connections
27197 - Fix some memory leaks in directory servers.
27198 - Allow backslash in Win32 filenames.
27199 - Made Tor build complain-free on FreeBSD, hopefully without
27200 breaking other BSD builds. We'll see.
27202 - Doxygen markup on all functions and global variables.
27203 - Make directory functions update routerlist, not replace it. So
27204 now directory disagreements are not so critical a problem.
27205 - Remove the upper limit on number of descriptors in a dirserver's
27206 directory (not that we were anywhere close).
27207 - Allow multiple logfiles at different severity ranges.
27208 - Allow *BindAddress to specify ":port" rather than setting *Port
27209 separately. Allow multiple instances of each BindAddress config
27210 option, so you can bind to multiple interfaces if you want.
27211 - Allow multiple exit policy lines, which are processed in order.
27212 Now we don't need that huge line with all the commas in it.
27213 - Enable accept/reject policies on SOCKS connections, so you can bind
27214 to 0.0.0.0 but still control who can use your OP.
27217 Changes in version 0.0.6.2 - 2004-05-16
27218 o Our integrity-checking digest was checking only the most recent cell,
27219 not the previous cells like we'd thought.
27220 Thanks to Stefan Mark for finding the flaw!
27223 Changes in version 0.0.6.1 - 2004-05-06
27224 o Fix two bugs in our AES counter-mode implementation (this affected
27225 onion-level stream encryption, but not TLS-level). It turns
27226 out we were doing something much more akin to a 16-character
27227 polyalphabetic cipher. Oops.
27228 Thanks to Stefan Mark for finding the flaw!
27229 o Retire moria3 as a directory server, and add tor26 as a directory
27233 Changes in version 0.0.6 - 2004-05-02
27234 [version bump only]
27237 Changes in version 0.0.6rc4 - 2004-05-01
27238 o Update the built-in dirservers list to use the new directory format
27239 o Fix a rare seg fault: if a node offering a hidden service attempts
27240 to build a circuit to Alice's rendezvous point and fails before it
27241 reaches the last hop, it retries with a different circuit, but
27243 o Handle windows socket errors correctly.
27246 Changes in version 0.0.6rc3 - 2004-04-28
27247 o Don't expire non-general excess circuits (if we had enough
27248 circuits open, we were expiring rendezvous circuits -- even
27249 when they had a stream attached. oops.)
27250 o Fetch randomness from /dev/urandom better (not via fopen/fread)
27251 o Better debugging for tls errors
27252 o Some versions of openssl have an SSL_pending function that erroneously
27253 returns bytes when there is a non-application record pending.
27254 o Set Content-Type on the directory and hidserv descriptor.
27255 o Remove IVs from cipher code, since AES-ctr has none.
27256 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
27257 o We were using an array of length zero in a few places.
27258 o win32's gethostbyname can't resolve an IP to an IP.
27259 o win32's close can't close a socket.
27262 Changes in version 0.0.6rc2 - 2004-04-26
27263 o Fix a bug where we were closing tls connections intermittently.
27264 It turns out openssl keeps its errors around -- so if an error
27265 happens, and you don't ask about it, and then another openssl
27266 operation happens and succeeds, and you ask if there was an error,
27267 it tells you about the first error. Fun fun.
27268 o Fix a bug that's been lurking since 27 may 03 (!)
27269 When passing back a destroy cell, we would use the wrong circ id.
27270 'Mostly harmless', but still worth fixing.
27271 o Since we don't support truncateds much, don't bother sending them;
27272 just close the circ.
27273 o check for <machine/limits.h> so we build on NetBSD again (I hope).
27274 o don't crash if a conn that sent a begin has suddenly lost its circuit
27275 (this was quite rare).
27278 Changes in version 0.0.6rc1 - 2004-04-25
27279 o We now rotate link (tls context) keys and onion keys.
27280 o CREATE cells now include oaep padding, so you can tell
27281 if you decrypted them correctly.
27282 o Add bandwidthburst to server descriptor.
27283 o Directories now say which dirserver signed them.
27284 o Use a tor_assert macro that logs failed assertions too.
27287 Changes in version 0.0.6pre5 - 2004-04-18
27288 o changes from 0.0.6pre4:
27289 - make tor build on broken freebsd 5.2 installs
27290 - fix a failed assert when you try an intro point, get a nack, and try
27291 a second one and it works.
27292 - when alice uses a port that the hidden service doesn't accept,
27293 it now sends back an end cell (denied by exit policy). otherwise
27294 alice would just have to wait to time out.
27295 - fix another rare bug: when we had tried all the intro
27296 points for a hidden service, we fetched the descriptor
27297 again, but we left our introcirc thinking it had already
27298 sent an intro, so it kept waiting for a response...
27299 - bugfix: when you sleep your hidden-service laptop, as soon
27300 as it wakes up it tries to upload a service descriptor, but
27301 socketpair fails for some reason (localhost not up yet?).
27302 now we simply give up on that upload, and we'll try again later.
27303 i'd still like to find the bug though.
27304 - if an intro circ waiting for an ack dies before getting one, then
27306 - we were reusing stale service descriptors and refetching usable
27310 Changes in version 0.0.6pre4 - 2004-04-14
27311 o changes from 0.0.6pre3:
27312 - when bob fails to connect to the rendezvous point, and his
27313 circ didn't fail because of the rendezvous point itself, then
27314 he retries a couple of times
27315 - we expire introduction and rendezvous circs more thoroughly
27316 (sometimes they were hanging around forever)
27317 - we expire unattached rendezvous streams that have been around
27318 too long (they were sticking around forever).
27319 - fix a measly fencepost error that was crashing everybody with
27323 Changes in version 0.0.6pre3 - 2004-04-14
27324 o changes from 0.0.6pre2:
27325 - make hup work again
27326 - fix some memory leaks for dirservers
27327 - allow more skew in rendezvous descriptor timestamps, to help
27328 handle people like blanu who don't know what time it is
27329 - normal circs are 3 hops, but some rend/intro circs are 4, if
27330 the initiator doesn't get to choose the last hop
27331 - send acks for introductions, so alice can know whether to try
27333 - bob publishes intro points more correctly
27334 o changes from 0.0.5:
27335 - fix an assert trigger that's been plaguing us since the days
27336 of 0.0.2prexx (thanks weasel!)
27337 - retry stream correctly when we fail to connect because of
27338 exit-policy-reject (should try another) or can't-resolve-address
27339 (also should try another, because dns on random internet servers
27341 - when we hup a dirserver and we've *removed* a server from the
27342 approved-routers list, now we remove that server from the
27343 in-memory directories too
27346 Changes in version 0.0.6pre2 - 2004-04-08
27347 o We fixed our base32 implementation. Now it works on all architectures.
27350 Changes in version 0.0.6pre1 - 2004-04-08
27352 - Hidden services and rendezvous points are implemented. Go to
27353 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
27354 hidden services. (This only works via a socks4a proxy such as
27355 Privoxy, and currently it's quite slow.)
27358 Changes in version 0.0.5 - 2004-03-30
27359 [version bump only]
27362 Changes in version 0.0.5rc3 - 2004-03-29
27363 o Install torrc as torrc.sample -- we no longer clobber your
27365 o Re-enable recommendedversion checking (we broke it in rc2, oops)
27366 o Add in a 'notice' log level for things the operator should hear
27367 but that aren't warnings
27370 Changes in version 0.0.5rc2 - 2004-03-29
27371 o Hold socks connection open until reply is flushed (if possible)
27372 o Make exit nodes resolve IPs to IPs immediately, rather than asking
27373 the dns farm to do it.
27374 o Fix c99 aliasing warnings in rephist.c
27375 o Don't include server descriptors that are older than 24 hours in the
27377 o Give socks 'reject' replies their whole 15s to attempt to flush,
27378 rather than seeing the 60s timeout and assuming the flush had failed.
27379 o Clean automake droppings from the cvs repository
27382 Changes in version 0.0.5rc1 - 2004-03-28
27383 o Fix mangled-state bug in directory fetching (was causing sigpipes).
27384 o Only build circuits after we've fetched the directory: clients were
27385 using only the directory servers before they'd fetched a directory.
27386 This also means longer startup time; so it goes.
27387 o Fix an assert trigger where an OP would fail to handshake, and we'd
27388 expect it to have a nickname.
27389 o Work around a tsocks bug: do a socks reject when AP connection dies
27390 early, else tsocks goes into an infinite loop.
27393 Changes in version 0.0.4 - 2004-03-26
27394 o When connecting to a dirserver or OR and the network is down,
27398 Changes in version 0.0.3 - 2004-03-26
27399 o Warn and fail if server chose a nickname with illegal characters
27400 o Port to Solaris and Sparc:
27401 - include missing header fcntl.h
27402 - have autoconf find -lsocket -lnsl automatically
27403 - deal with hardware word alignment
27404 - make uname() work (solaris has a different return convention)
27405 - switch from using signal() to sigaction()
27406 o Preliminary work on reputation system:
27407 - Keep statistics on success/fail of connect attempts; they're published
27408 by kill -USR1 currently.
27409 - Add a RunTesting option to try to learn link state by creating test
27410 circuits, even when SocksPort is off.
27411 - Remove unused open circuits when there are too many.
27414 Changes in version 0.0.2 - 2004-03-19
27415 - Include strlcpy and strlcat for safer string ops
27416 - define INADDR_NONE so we compile (but still not run) on solaris
27419 Changes in version 0.0.2pre27 - 2004-03-14
27421 - Allow internal tor networks (we were rejecting internal IPs,
27422 now we allow them if they're set explicitly).
27423 - And fix a few endian issues.
27426 Changes in version 0.0.2pre26 - 2004-03-14
27428 - If a stream times out after 15s without a connected cell, don't
27429 try that circuit again: try a new one.
27430 - Retry streams at most 4 times. Then give up.
27431 - When a dirserver gets a descriptor from an unknown router, it
27432 logs its fingerprint (so the dirserver operator can choose to
27433 accept it even without mail from the server operator).
27434 - Inform unapproved servers when we reject their descriptors.
27435 - Make tor build on Windows again. It works as a client, who knows
27437 - Clearer instructions in the torrc for how to set up a server.
27438 - Be more efficient about reading fd's when our global token bucket
27439 (used for rate limiting) becomes empty.
27441 - Stop asserting that computers always go forward in time. It's
27443 - When we sent a cell (e.g. destroy) and then marked an OR connection
27444 expired, we might close it before finishing a flush if the other
27445 side isn't reading right then.
27446 - Don't allow dirservers to start if they haven't defined
27447 RecommendedVersions
27448 - We were caching transient dns failures. Oops.
27449 - Prevent servers from publishing an internal IP as their address.
27450 - Address a strcat vulnerability in circuit.c
27453 Changes in version 0.0.2pre25 - 2004-03-04
27455 - Put the OR's IP in its router descriptor, not its fqdn. That way
27456 we'll stop being stalled by gethostbyname for nodes with flaky dns,
27459 - If the user typed in an address that didn't resolve, the server
27463 Changes in version 0.0.2pre24 - 2004-03-03
27465 - Fix an assertion failure in dns.c, where we were trying to dequeue
27466 a pending dns resolve even if it wasn't pending
27467 - Fix a spurious socks5 warning about still trying to write after the
27468 connection is finished.
27469 - Hold certain marked_for_close connections open until they're finished
27470 flushing, rather than losing bytes by closing them too early.
27471 - Correctly report the reason for ending a stream
27472 - Remove some duplicate calls to connection_mark_for_close
27473 - Put switch_id and start_daemon earlier in the boot sequence, so it
27474 will actually try to chdir() to options.DataDirectory
27475 - Make 'make test' exit(1) if a test fails; fix some unit tests
27476 - Make tor fail when you use a config option it doesn't know about,
27477 rather than warn and continue.
27478 - Make --version work
27479 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
27482 Changes in version 0.0.2pre23 - 2004-02-29
27484 - Print a statement when the first circ is finished, so the user
27485 knows it's working.
27486 - If a relay cell is unrecognized at the end of the circuit,
27487 send back a destroy. (So attacks to mutate cells are more
27489 - New config option 'excludenodes' to avoid certain nodes for circuits.
27490 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
27491 so you can collect coredumps there.
27493 - Fix a bug in tls flushing where sometimes data got wedged and
27494 didn't flush until more data got sent. Hopefully this bug was
27495 a big factor in the random delays we were seeing.
27496 - Make 'connected' cells include the resolved IP, so the client
27497 dns cache actually gets populated.
27498 - Disallow changing from ORPort=0 to ORPort>0 on hup.
27499 - When we time-out on a stream and detach from the circuit, send an
27500 end cell down it first.
27501 - Only warn about an unknown router (in exitnodes, entrynodes,
27502 excludenodes) after we've fetched a directory.
27505 Changes in version 0.0.2pre22 - 2004-02-26
27507 - Servers publish less revealing uname information in descriptors.
27508 - More memory tracking and assertions, to crash more usefully when
27510 - If the default torrc isn't there, just use some default defaults.
27511 Plus provide an internal dirservers file if they don't have one.
27512 - When the user tries to use Tor as an http proxy, give them an http
27513 501 failure explaining that we're a socks proxy.
27514 - Dump a new router.desc on hup, to help confused people who change
27515 their exit policies and then wonder why router.desc doesn't reflect
27517 - Clean up the generic tor.sh init script that we ship with.
27519 - If the exit stream is pending on the resolve, and a destroy arrives,
27520 then the stream wasn't getting removed from the pending list. I
27521 think this was the one causing recent server crashes.
27522 - Use a more robust poll on OSX 10.3, since their poll is flaky.
27523 - When it couldn't resolve any dirservers, it was useless from then on.
27524 Now it reloads the RouterFile (or default dirservers) if it has no
27526 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
27527 many users don't even *have* a /usr/local/sbin/.
27530 Changes in version 0.0.2pre21 - 2004-02-18
27532 - There's a ChangeLog file that actually reflects the changelog.
27533 - There's a 'torify' wrapper script, with an accompanying
27534 tor-tsocks.conf, that simplifies the process of using tsocks for
27535 tor. It even has a man page.
27536 - The tor binary gets installed to sbin rather than bin now.
27537 - Retry streams where the connected cell hasn't arrived in 15 seconds
27538 - Clean up exit policy handling -- get the default out of the torrc,
27539 so we can update it without forcing each server operator to fix
27541 - Allow imaps and pop3s in default exit policy
27543 - Prevent picking middleman nodes as the last node in the circuit
27546 Changes in version 0.0.2pre20 - 2004-01-30
27548 - We now have a deb package, and it's in debian unstable. Go to
27549 it, apt-getters. :)
27550 - I've split the TotalBandwidth option into BandwidthRate (how many
27551 bytes per second you want to allow, long-term) and
27552 BandwidthBurst (how many bytes you will allow at once before the cap
27553 kicks in). This better token bucket approach lets you, say, set
27554 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
27555 performance while not exceeding your monthly bandwidth quota.
27556 - Push out a tls record's worth of data once you've got it, rather
27557 than waiting until you've read everything waiting to be read. This
27558 may improve performance by pipelining better. We'll see.
27559 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
27560 from failed circuits (if they haven't been connected yet) and attach
27562 - Expire old streams that haven't managed to connect. Some day we'll
27563 have them reattach to new circuits instead.
27566 - Fix several memory leaks that were causing servers to become bloated
27568 - Fix a few very rare assert triggers. A few more remain.
27569 - Setuid to User _before_ complaining about running as root.
27572 Changes in version 0.0.2pre19 - 2004-01-07
27574 - Fix deadlock condition in dns farm. We were telling a child to die by
27575 closing the parent's file descriptor to him. But newer children were
27576 inheriting the open file descriptor from the parent, and since they
27577 weren't closing it, the socket never closed, so the child never read
27578 eof, so he never knew to exit. Similarly, dns workers were holding
27579 open other sockets, leading to all sorts of chaos.
27580 - New cleaner daemon() code for forking and backgrounding.
27581 - If you log to a file, it now prints an entry at the top of the
27582 logfile so you know it's working.
27583 - The onionskin challenge length was 30 bytes longer than necessary.
27584 - Started to patch up the spec so it's not quite so out of date.
27587 Changes in version 0.0.2pre18 - 2004-01-02
27589 - Fix endian issues with the 'integrity' field in the relay header.
27590 - Fix a potential bug where connections in state
27591 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
27594 Changes in version 0.0.2pre17 - 2003-12-30
27596 - Made --debuglogfile (or any second log file, actually) work.
27597 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
27598 adversary could force us into an infinite loop.
27601 - Each onionskin handshake now includes a hash of the computed key,
27602 to prove the server's identity and help perfect forward secrecy.
27603 - Changed cell size from 256 to 512 bytes (working toward compatibility
27605 - Changed cell length to 2 bytes, and moved it to the relay header.
27606 - Implemented end-to-end integrity checking for the payloads of
27608 - Separated streamid from 'recognized' (otherwise circuits will get
27609 messed up when we try to have streams exit from the middle). We
27610 use the integrity-checking to confirm that a cell is addressed to
27612 - Randomize the initial circid and streamid values, so an adversary who
27613 breaks into a node can't learn how many circuits or streams have
27617 Changes in version 0.0.2pre16 - 2003-12-14
27619 - Fixed a bug that made HUP trigger an assert
27620 - Fixed a bug where a circuit that immediately failed wasn't being
27621 counted as a failed circuit in counting retries.
27624 - Now we close the circuit when we get a truncated cell: otherwise we're
27625 open to an anonymity attack where a bad node in the path truncates
27626 the circuit and then we open streams at him.
27627 - Add port ranges to exit policies
27628 - Add a conservative default exit policy
27629 - Warn if you're running tor as root
27630 - on HUP, retry OR connections and close/rebind listeners
27631 - options.EntryNodes: try these nodes first when picking the first node
27632 - options.ExitNodes: if your best choices happen to include any of
27633 your preferred exit nodes, you choose among just those preferred
27635 - options.ExcludedNodes: nodes that are never picked in path building
27638 Changes in version 0.0.2pre15 - 2003-12-03
27639 o Robustness and bugfixes:
27640 - Sometimes clients would cache incorrect DNS resolves, which would
27641 really screw things up.
27642 - An OP that goes offline would slowly leak all its sockets and stop
27644 - A wide variety of bugfixes in exit node selection, exit policy
27645 handling, and processing pending streams when a new circuit is
27647 - Pick nodes for a path only from those the directory says are up
27648 - Choose randomly from all running dirservers, not always the first one
27649 - Increase allowed http header size for directory fetch.
27650 - Stop writing to stderr (if we're daemonized it will be closed).
27651 - Enable -g always, so cores will be more useful to me.
27652 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
27655 - Wrote a man page. It lists commonly used options.
27658 - Change default loglevel to warn.
27659 - Make PidFile default to null rather than littering in your CWD.
27660 - OnionRouter config option is now obsolete. Instead it just checks
27662 - Moved to a single unified torrc file for both clients and servers.
27665 Changes in version 0.0.2pre14 - 2003-11-29
27666 o Robustness and bugfixes:
27667 - Force the admin to make the DataDirectory himself
27668 - to get ownership/permissions right
27669 - so clients no longer make a DataDirectory and then never use it
27670 - fix bug where a client who was offline for 45 minutes would never
27671 pull down a directory again
27672 - fix (or at least hide really well) the dns assert bug that was
27673 causing server crashes
27674 - warnings and improved robustness wrt clockskew for certs
27675 - use the native daemon(3) to daemonize, when available
27676 - exit if bind() fails
27677 - exit if neither socksport nor orport is defined
27678 - include our own tor_timegm (Win32 doesn't have its own)
27679 - bugfix for win32 with lots of connections
27680 - fix minor bias in PRNG
27681 - make dirserver more robust to corrupt cached directory
27684 - Wrote the design document (woo)
27686 o Circuit building and exit policies:
27687 - Circuits no longer try to use nodes that the directory has told them
27689 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
27690 bitcounts (18.0.0.0/8).
27691 - Make AP connections standby for a circuit if no suitable circuit
27692 exists, rather than failing
27693 - Circuits choose exit node based on addr/port, exit policies, and
27694 which AP connections are standing by
27695 - Bump min pathlen from 2 to 3
27696 - Relay end cells have a payload to describe why the stream ended.
27697 - If the stream failed because of exit policy, try again with a new
27699 - Clients have a dns cache to remember resolved addresses.
27700 - Notice more quickly when we have no working circuits
27703 - APPort is now called SocksPort
27704 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
27706 - RecommendedVersions is now a config variable rather than
27707 hardcoded (for dirservers)
27708 - Reloads config on HUP
27709 - Usage info on -h or --help
27710 - If you set User and Group config vars, it'll setu/gid to them.
27713 Changes in version 0.0.2pre13 - 2003-10-19
27714 o General stability:
27715 - SSL_write no longer fails when it returns WANTWRITE and the number
27716 of bytes in the buf has changed by the next SSL_write call.
27717 - Fix segfault fetching directory when network is down
27718 - Fix a variety of minor memory leaks
27719 - Dirservers reload the fingerprints file on HUP, so I don't have
27720 to take down the network when I approve a new router
27721 - Default server config file has explicit Address line to specify fqdn
27724 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
27725 - Make listener connections not ever alloc bufs
27727 o Autoconf improvements:
27728 - don't clobber an external CFLAGS in ./configure
27729 - Make install now works
27730 - create var/lib/tor on make install
27731 - autocreate a tor.sh initscript to help distribs
27732 - autocreate the torrc and sample-server-torrc with correct paths
27734 o Log files and Daemonizing now work:
27735 - If --DebugLogFile is specified, log to it at -l debug
27736 - If --LogFile is specified, use it instead of commandline
27737 - If --RunAsDaemon is set, tor forks and backgrounds on startup