1 Changes in version 0.4.3.3-alpha - 2020-03-18
2 Tor 0.4.3.3-alpha fixes several bugs in previous releases, including
3 TROVE-2020-002, a major denial-of-service vulnerability that affected
4 all released Tor instances since 0.2.1.5-alpha. Using this
5 vulnerability, an attacker could cause Tor instances to consume a huge
6 amount of CPU, disrupting their operations for several seconds or
7 minutes. This attack could be launched by anybody against a relay, or
8 by a directory cache against any client that had connected to it. The
9 attacker could launch this attack as much as they wanted, thereby
10 disrupting service or creating patterns that could aid in traffic
11 analysis. This issue was found by OSS-Fuzz, and is also tracked
14 We do not have reason to believe that this attack is currently being
15 exploited in the wild, but nonetheless we advise everyone to upgrade
16 as soon as packages are available.
18 o Major bugfixes (security, denial-of-service):
19 - Fix a denial-of-service bug that could be used by anyone to
20 consume a bunch of CPU on any Tor relay or authority, or by
21 directories to consume a bunch of CPU on clients or hidden
22 services. Because of the potential for CPU consumption to
23 introduce observable timing patterns, we are treating this as a
24 high-severity security issue. Fixes bug 33119; bugfix on
25 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
26 as TROVE-2020-002 and CVE-2020-10592.
28 o Major bugfixes (circuit padding, memory leak):
29 - Avoid a remotely triggered memory leak in the case that a circuit
30 padding machine is somehow negotiated twice on the same circuit.
31 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
32 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
34 o Major bugfixes (directory authority):
35 - Directory authorities will now send a 503 (not enough bandwidth)
36 code to clients when under bandwidth pressure. Known relays and
37 other authorities will always be answered regardless of the
38 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
40 o Minor features (diagnostic):
41 - Improve assertions and add some memory-poisoning code to try to
42 track down possible causes of a rare crash (32564) in the EWMA
43 code. Closes ticket 33290.
45 o Minor features (directory authorities):
46 - Directory authorities now reject descriptors from relays running
47 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
48 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
50 o Minor features (usability):
51 - Include more information when failing to parse a configuration
52 value. This should make it easier to tell what's going wrong when
53 a configuration file doesn't parse. Closes ticket 33460.
55 o Minor bugfix (relay, configuration):
56 - Warn if the ContactInfo field is not set, and tell the relay
57 operator that not having a ContactInfo field set might cause their
58 relay to get rejected in the future. Fixes bug 33361; bugfix
61 o Minor bugfixes (coding best practices checks):
62 - Allow the "practracker" script to read unicode files when using
63 Python 2. We made the script use unicode literals in 0.4.3.1-alpha,
64 but didn't change the codec for opening files. Fixes bug 33374;
65 bugfix on 0.4.3.1-alpha.
67 o Minor bugfixes (continuous integration):
68 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
71 o Minor bugfixes (onion service v3, client):
72 - Remove a BUG() warning that would cause a stack trace if an onion
73 service descriptor was freed while we were waiting for a
74 rendezvous circuit to complete. Fixes bug 28992; bugfix
77 o Minor bugfixes (onion services v3):
78 - Fix an assertion failure that could result from a corrupted
79 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
80 bugfix on 0.3.3.1-alpha. This issue is also tracked
83 o Documentation (manpage):
84 - Alphabetize the Server and Directory server sections of the tor
85 manpage. Also split Statistics options into their own section of
86 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
87 Google Season of Docs.
88 - Document the __OwningControllerProcess torrc option and specify
89 its polling interval. Resolves issue 32971.
91 o Testing (Travis CI):
92 - Remove a redundant distcheck job. Closes ticket 33194.
93 - Sort the Travis jobs in order of speed: putting the slowest jobs
94 first takes full advantage of Travis job concurrency. Closes
96 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
97 previously configured to fast_finish (which requires
98 allow_failure), to speed up the build. Closes ticket 33195.
99 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
100 tool to produce detailed diagnostic output. Closes ticket 32792.
103 Changes in version 0.4.2.7 - 2020-03-18
104 This is the third stable release in the 0.4.2.x series. It backports
105 numerous fixes from later releases, including a fix for TROVE-2020-
106 002, a major denial-of-service vulnerability that affected all
107 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
108 an attacker could cause Tor instances to consume a huge amount of CPU,
109 disrupting their operations for several seconds or minutes. This
110 attack could be launched by anybody against a relay, or by a directory
111 cache against any client that had connected to it. The attacker could
112 launch this attack as much as they wanted, thereby disrupting service
113 or creating patterns that could aid in traffic analysis. This issue
114 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
116 We do not have reason to believe that this attack is currently being
117 exploited in the wild, but nonetheless we advise everyone to upgrade
118 as soon as packages are available.
120 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
121 - Fix a denial-of-service bug that could be used by anyone to
122 consume a bunch of CPU on any Tor relay or authority, or by
123 directories to consume a bunch of CPU on clients or hidden
124 services. Because of the potential for CPU consumption to
125 introduce observable timing patterns, we are treating this as a
126 high-severity security issue. Fixes bug 33119; bugfix on
127 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
128 as TROVE-2020-002 and CVE-2020-10592.
130 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
131 - Avoid a remotely triggered memory leak in the case that a circuit
132 padding machine is somehow negotiated twice on the same circuit.
133 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
134 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
136 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
137 - Directory authorities will now send a 503 (not enough bandwidth)
138 code to clients when under bandwidth pressure. Known relays and
139 other authorities will always be answered regardless of the
140 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
142 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
143 - Stop allowing failures on the Travis CI stem tests job. It looks
144 like all the stem hangs we were seeing before are now fixed.
147 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
148 - Lowercase the configured value of BridgeDistribution before adding
149 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
151 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
152 - If we encounter a bug when flushing a buffer to a TLS connection,
153 only log the bug once per invocation of the Tor process.
154 Previously we would log with every occurrence, which could cause
155 us to run out of disk space. Fixes bug 33093; bugfix
158 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
159 - Fix an assertion failure that could result from a corrupted
160 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
161 bugfix on 0.3.3.1-alpha. This issue is also tracked
164 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
165 - Fix a syntax warning given by newer versions of Rust that was
166 creating problems for our continuous integration. Fixes bug 33212;
167 bugfix on 0.3.5.1-alpha.
169 o Testing (Travis CI, backport from 0.4.3.3-alpha):
170 - Remove a redundant distcheck job. Closes ticket 33194.
171 - Sort the Travis jobs in order of speed: putting the slowest jobs
172 first takes full advantage of Travis job concurrency. Closes
174 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
175 previously configured to fast_finish (which requires
176 allow_failure), to speed up the build. Closes ticket 33195.
177 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
178 tool to produce detailed diagnostic output. Closes ticket 32792.
181 Changes in version 0.4.1.9 - 2020-03-18
182 Tor 0.4.1.9 backports important fixes from later Tor releases,
183 including a fix for TROVE-2020-002, a major denial-of-service
184 vulnerability that affected all released Tor instances since
185 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
186 instances to consume a huge amount of CPU, disrupting their operations
187 for several seconds or minutes. This attack could be launched by
188 anybody against a relay, or by a directory cache against any client
189 that had connected to it. The attacker could launch this attack as
190 much as they wanted, thereby disrupting service or creating patterns
191 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
192 and is also tracked as CVE-2020-10592.
194 We do not have reason to believe that this attack is currently being
195 exploited in the wild, but nonetheless we advise everyone to upgrade
196 as soon as packages are available.
198 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
199 - Fix a denial-of-service bug that could be used by anyone to
200 consume a bunch of CPU on any Tor relay or authority, or by
201 directories to consume a bunch of CPU on clients or hidden
202 services. Because of the potential for CPU consumption to
203 introduce observable timing patterns, we are treating this as a
204 high-severity security issue. Fixes bug 33119; bugfix on
205 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
206 as TROVE-2020-002 and CVE-2020-10592.
208 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
209 - Avoid a remotely triggered memory leak in the case that a circuit
210 padding machine is somehow negotiated twice on the same circuit.
211 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
212 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
214 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
215 - Lowercase the configured value of BridgeDistribution before adding
216 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
218 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
219 - If we encounter a bug when flushing a buffer to a TLS connection,
220 only log the bug once per invocation of the Tor process.
221 Previously we would log with every occurrence, which could cause
222 us to run out of disk space. Fixes bug 33093; bugfix
225 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
226 - Fix an assertion failure that could result from a corrupted
227 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
228 bugfix on 0.3.3.1-alpha. This issue is also tracked
231 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
232 - Fix a syntax warning given by newer versions of Rust that was
233 creating problems for our continuous integration. Fixes bug 33212;
234 bugfix on 0.3.5.1-alpha.
236 o Testing (Travis CI, backport from 0.4.3.3-alpha):
237 - Remove a redundant distcheck job. Closes ticket 33194.
238 - Sort the Travis jobs in order of speed: putting the slowest jobs
239 first takes full advantage of Travis job concurrency. Closes
241 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
242 previously configured to fast_finish (which requires
243 allow_failure), to speed up the build. Closes ticket 33195.
244 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
245 tool to produce detailed diagnostic output. Closes ticket 32792.
248 Changes in version 0.3.5.10 - 2020-03-18
249 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
250 fix for TROVE-2020-002, a major denial-of-service vulnerability that
251 affected all released Tor instances since 0.2.1.5-alpha. Using this
252 vulnerability, an attacker could cause Tor instances to consume a huge
253 amount of CPU, disrupting their operations for several seconds or
254 minutes. This attack could be launched by anybody against a relay, or
255 by a directory cache against any client that had connected to it. The
256 attacker could launch this attack as much as they wanted, thereby
257 disrupting service or creating patterns that could aid in traffic
258 analysis. This issue was found by OSS-Fuzz, and is also tracked
261 We do not have reason to believe that this attack is currently being
262 exploited in the wild, but nonetheless we advise everyone to upgrade
263 as soon as packages are available.
265 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
266 - Fix a denial-of-service bug that could be used by anyone to
267 consume a bunch of CPU on any Tor relay or authority, or by
268 directories to consume a bunch of CPU on clients or hidden
269 services. Because of the potential for CPU consumption to
270 introduce observable timing patterns, we are treating this as a
271 high-severity security issue. Fixes bug 33119; bugfix on
272 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
273 as TROVE-2020-002 and CVE-2020-10592.
275 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
276 - Correct how we use libseccomp. Particularly, stop assuming that
277 rules are applied in a particular order or that more rules are
278 processed after the first match. Neither is the case! In
279 libseccomp <2.4.0 this lead to some rules having no effect.
280 libseccomp 2.4.0 changed how rules are generated, leading to a
281 different ordering, which in turn led to a fatal crash during
282 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
285 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
286 - Stop allowing failures on the Travis CI stem tests job. It looks
287 like all the stem hangs we were seeing before are now fixed.
290 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
291 - Lowercase the configured value of BridgeDistribution before adding
292 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
294 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
295 - When running Tor with an option like --verify-config or
296 --dump-config that does not start the event loop, avoid crashing
297 if we try to exit early because of an error. Fixes bug 32407;
298 bugfix on 0.3.3.1-alpha.
300 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
301 - If we encounter a bug when flushing a buffer to a TLS connection,
302 only log the bug once per invocation of the Tor process.
303 Previously we would log with every occurrence, which could cause
304 us to run out of disk space. Fixes bug 33093; bugfix
307 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
308 - Fix an assertion failure that could result from a corrupted
309 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
310 bugfix on 0.3.3.1-alpha. This issue is also tracked
313 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
314 - Fix a syntax warning given by newer versions of Rust that was
315 creating problems for our continuous integration. Fixes bug 33212;
316 bugfix on 0.3.5.1-alpha.
318 o Testing (backport from 0.4.3.1-alpha):
319 - Re-enable the Travis CI macOS Chutney build, but don't let it
320 prevent the Travis job from finishing. (The Travis macOS jobs are
321 slow, so we don't want to have it delay the whole CI process.)
323 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
324 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
325 fix the sandbox errors in 32722. Closes ticket 32240.
327 o Testing (continuous integration, backport from 0.4.3.1-alpha):
328 - Use zstd in our Travis Linux builds. Closes ticket 32242.
330 o Testing (Travis CI, backport from 0.4.3.3-alpha):
331 - Remove a redundant distcheck job. Closes ticket 33194.
332 - Sort the Travis jobs in order of speed: putting the slowest jobs
333 first takes full advantage of Travis job concurrency. Closes
335 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
336 previously configured to fast_finish (which requires
337 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
338 tool to produce detailed diagnostic output. Closes ticket 32792.
341 Changes in version 0.4.3.2-alpha - 2020-02-10
342 This is the second stable alpha release in the Tor 0.4.3.x series. It
343 fixes several bugs present in the previous alpha release. Anybody
344 running the previous alpha should upgrade, and look for bugs in this
347 o Major bugfixes (onion service client, authorization):
348 - On a NEWNYM signal, purge entries from the ephemeral client
349 authorization cache. The permanent ones are kept. Fixes bug 33139;
350 bugfix on 0.4.3.1-alpha.
352 o Minor features (best practices tracker):
353 - Practracker now supports a --regen-overbroad option to regenerate
354 the exceptions file, but only to revise exceptions to be _less_
355 tolerant of best-practices violations. Closes ticket 32372.
357 o Minor features (continuous integration):
358 - Run Doxygen Makefile target on Travis, so we can learn about
359 regressions in our internal documentation. Closes ticket 32455.
360 - Stop allowing failures on the Travis CI stem tests job. It looks
361 like all the stem hangs we were seeing before are now fixed.
364 o Minor bugfixes (build system):
365 - Revise configure options that were either missing or incorrect in
366 the configure summary. Fixes bug 32230; bugfix on 0.4.3.1-alpha.
368 o Minor bugfixes (controller protocol):
369 - Fix a memory leak introduced by refactoring of control reply
370 formatting code. Fixes bug 33039; bugfix on 0.4.3.1-alpha.
371 - Fix a memory leak in GETINFO responses. Fixes bug 33103; bugfix
373 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
374 report them as SIGNAL events. Previously we would log a bug
375 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
377 o Minor bugfixes (logging):
378 - If we encounter a bug when flushing a buffer to a TLS connection,
379 only log the bug once per invocation of the Tor process.
380 Previously we would log with every occurrence, which could cause
381 us to run out of disk space. Fixes bug 33093; bugfix
383 - When logging a bug, do not say "Future instances of this warning
384 will be silenced" unless we are actually going to silence them.
385 Previously we would say this whenever a BUG() check failed in the
386 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
388 o Minor bugfixes (onion service v2):
389 - Move a series of v2 onion service warnings to protocol-warning
390 level because they can all be triggered remotely by a malformed
391 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
393 o Minor bugfixes (onion service v3, client authorization):
394 - When removing client authorization credentials using the control
395 port, also remove the associated descriptor, so the onion service
396 can no longer be contacted. Fixes bug 33148; bugfix
399 o Minor bugfixes (pluggable transports):
400 - When receiving a message on standard error from a pluggable
401 transport, log it at info level, rather than as a warning. Fixes
402 bug 33005; bugfix on 0.4.0.1-alpha.
404 o Minor bugfixes (rust, build):
405 - Fix a syntax warning given by newer versions of Rust that was
406 creating problems for our continuous integration. Fixes bug 33212;
407 bugfix on 0.3.5.1-alpha.
409 o Minor bugfixes (TLS bug handling):
410 - When encountering a bug in buf_read_from_tls(), return a "MISC"
411 error code rather than "WANTWRITE". This change might help avoid
412 some CPU-wasting loops if the bug is ever triggered. Bug reported
413 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
415 o Code simplification and refactoring (mainloop):
416 - Simplify the ip_address_changed() function by removing redundant
417 checks. Closes ticket 33091.
419 o Documentation (manpage):
420 - Split "Circuit Timeout" options and "Node Selection" options into
421 their own sections of the tor manpage. Closes tickets 32928 and
422 32929. Work by Swati Thacker as part of Google Season of Docs.
425 Changes in version 0.4.2.6 - 2020-01-30
426 This is the second stable release in the 0.4.2.x series. It backports
427 several bugfixes from 0.4.3.1-alpha, including some that had affected
428 the Linux seccomp2 sandbox or Windows services. If you're running with
429 one of those configurations, you'll probably want to upgrade;
430 otherwise, you should be fine with 0.4.2.5.
432 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
433 - Correct how we use libseccomp. Particularly, stop assuming that
434 rules are applied in a particular order or that more rules are
435 processed after the first match. Neither is the case! In
436 libseccomp <2.4.0 this led to some rules having no effect.
437 libseccomp 2.4.0 changed how rules are generated, leading to a
438 different ordering, which in turn led to a fatal crash during
439 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
441 - Fix crash when reloading logging configuration while the
442 experimental sandbox is enabled. Fixes bug 32841; bugfix on
443 0.4.1.7. Patch by Peter Gerber.
445 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
446 - Use GCC/Clang's printf-checking feature to make sure that
447 tor_assertf() arguments are correctly typed. Fixes bug 32765;
448 bugfix on 0.4.1.1-alpha.
450 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
451 - Avoid a possible crash when trying to log a (fatal) assertion
452 failure about mismatched magic numbers in configuration objects.
453 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
455 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
456 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
457 test_practracker.sh script. Doing so caused a test failure. Fixes
458 bug 32705; bugfix on 0.4.2.1-alpha.
459 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
460 skipping practracker checks. Fixes bug 32705; bugfix
463 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
464 - Initialize the publish/subscribe system when running as a windows
465 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
467 o Testing (backport from 0.4.3.1-alpha):
468 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
469 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
470 fix the sandbox errors in 32722. Closes ticket 32240.
471 - Re-enable the Travis CI macOS Chutney build, but don't let it
472 prevent the Travis job from finishing. (The Travis macOS jobs are
473 slow, so we don't want to have it delay the whole CI process.)
476 o Testing (continuous integration, backport from 0.4.3.1-alpha):
477 - Use zstd in our Travis Linux builds. Closes ticket 32242.
480 Changes in version 0.4.1.8 - 2020-01-30
481 This release backports several bugfixes from later release series,
482 including some that had affected the Linux seccomp2 sandbox or Windows
483 services. If you're running with one of those configurations, you'll
484 probably want to upgrade; otherwise, you should be fine with your
485 current version of 0.4.1.x.
487 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
488 - Correct how we use libseccomp. Particularly, stop assuming that
489 rules are applied in a particular order or that more rules are
490 processed after the first match. Neither is the case! In
491 libseccomp <2.4.0 this led to some rules having no effect.
492 libseccomp 2.4.0 changed how rules are generated, leading to a
493 different ordering, which in turn led to a fatal crash during
494 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
496 - Fix crash when reloading logging configuration while the
497 experimental sandbox is enabled. Fixes bug 32841; bugfix on
498 0.4.1.7. Patch by Peter Gerber.
500 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
501 - When running Tor with an option like --verify-config or
502 --dump-config that does not start the event loop, avoid crashing
503 if we try to exit early because of an error. Fixes bug 32407;
504 bugfix on 0.3.3.1-alpha.
506 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
507 - Initialize the publish/subscribe system when running as a windows
508 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
510 o Testing (backport from 0.4.3.1-alpha):
511 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
512 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
513 fix the sandbox errors in 32722. Closes ticket 32240.
514 - Re-enable the Travis CI macOS Chutney build, but don't let it
515 prevent the Travis job from finishing. (The Travis macOS jobs are
516 slow, so we don't want to have it delay the whole CI process.)
519 o Testing (continuous integration, backport from 0.4.3.1-alpha):
520 - Use zstd in our Travis Linux builds. Closes ticket 32242.
523 Changes in version 0.4.3.1-alpha - 2020-01-22
524 This is the first alpha release in the 0.4.3.x series. It includes
525 improved support for application integration of onion services, support
526 for building in a client-only mode, and newly improved internal
527 documentation (online at https://src-ref.docs.torproject.org/tor/). It
528 also has numerous other small bugfixes and features, as well as
529 improvements to our code's internal organization that should help us
530 write better code in the future.
532 o New system requirements:
533 - When building Tor, you now need to have Python 3 in order to run
534 the integration tests. (Python 2 is officially unsupported
535 upstream, as of 1 Jan 2020.) Closes ticket 32608.
537 o Major features (build system):
538 - The relay code can now be disabled using the --disable-module-relay
539 configure option. When this option is set, we also disable the
540 dirauth module. Closes ticket 32123.
541 - When Tor is compiled --disable-module-relay, we also omit the code
542 used to act as a directory cache. Closes ticket 32487.
544 o Major features (directory authority, ed25519):
545 - Add support for banning a relay's ed25519 keys in the approved-
546 routers file. This will help us migrate away from RSA keys in the
547 future. Previously, only RSA keys could be banned in approved-
548 routers. Resolves ticket 22029. Patch by Neel Chauhan.
550 o Major features (onion service, controller):
551 - New control port commands to manage client-side onion service
552 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
553 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
554 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
556 o Major features (onion service, SOCKS5):
557 - Introduce a new SocksPort flag, ExtendedErrors, to support more
558 detailed error codes in information for applications that support
559 them. Closes ticket 30382; implements proposal 304.
561 o Major features (proxy):
562 - In addition to its current supported proxy types (HTTP CONNECT,
563 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
564 HAProxy server. A new torrc option was added to specify the
565 address/port of the server: TCPProxy <protocol> <host>:<port>.
566 Currently the only supported protocol for the option is haproxy.
567 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
569 o Major bugfixes (linux seccomp sandbox):
570 - Correct how we use libseccomp. Particularly, stop assuming that
571 rules are applied in a particular order or that more rules are
572 processed after the first match. Neither is the case! In
573 libseccomp <2.4.0 this led to some rules having no effect.
574 libseccomp 2.4.0 changed how rules are generated, leading to a
575 different ordering, which in turn led to a fatal crash during
576 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
578 - Fix crash when reloading logging configuration while the
579 experimental sandbox is enabled. Fixes bug 32841; bugfix on
580 0.4.1.7. Patch by Peter Gerber.
582 o Major bugfixes (networking):
583 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
584 and accept strings as well as binary addresses. Fixes bug 32315;
585 bugfix on 0.3.5.1-alpha.
587 o Major bugfixes (onion service):
588 - Report HS circuit failure back into the HS subsystem so we take
589 appropriate action with regards to the client introduction point
590 failure cache. This improves reachability of onion services, since
591 now clients notice failing introduction circuits properly. Fixes
592 bug 32020; bugfix on 0.3.2.1-alpha.
594 o Minor feature (configure, build system):
595 - Output a list of enabled/disabled features at the end of the
596 configure process in a pleasing way. Closes ticket 31373.
598 o Minor feature (heartbeat, onion service):
599 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
600 message. Closes ticket 31371.
602 o Minor features (configuration validation):
603 - Configuration validation can now be done by per-module callbacks,
604 rather than a global validation function. This will let us reduce
605 the size of config.c and some of its more cumbersome functions.
608 o Minor features (configuration):
609 - If a configured hardware crypto accelerator in AccelName is
610 prefixed with "!", Tor now exits when it cannot be found. Closes
612 - We now use flag-driven logic to warn about obsolete configuration
613 fields, so that we can include their names. In 0.4.2, we used a
614 special type, which prevented us from generating good warnings.
615 Implements ticket 32404.
617 o Minor features (controller):
618 - Add stream isolation data to STREAM event. Closes ticket 19859.
619 - Implement a new GETINFO command to fetch microdescriptor
620 consensus. Closes ticket 31684.
622 o Minor features (debugging, directory system):
623 - Don't crash when we find a non-guard with a guard-fraction value
624 set. Instead, log a bug warning, in an attempt to figure out how
625 this happened. Diagnostic for ticket 32868.
627 o Minor features (defense in depth):
628 - Add additional checks around tor_vasprintf() usage, in case the
629 function returns an error. Patch by Tobias Stoeckmann. Fixes
632 o Minor features (developer tooling):
633 - Remove the 0.2.9.x series branches from git scripts (git-merge-
634 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
637 o Minor features (developer tools):
638 - Add a check_cocci_parse.sh script that checks that new code is
639 parseable by Coccinelle. Add an exceptions file for unparseable
640 files, and run the script from travis CI. Closes ticket 31919.
641 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
642 target. Closes ticket 31919.
643 - Add a rename_c_identifiers.py tool to rename a bunch of C
644 identifiers at once, and generate a well-formed commit message
645 describing the change. This should help with refactoring. Closes
647 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
648 semantic patching tool with the correct flags. These flags are
649 fairly easy to forget, and these scripts should help us use
650 Coccinelle more effectively in the future. Closes ticket 31705.
652 o Minor features (Doxygen):
653 - Update Doxygen configuration file to a more recent template (from
654 1.8.15). Closes ticket 32110.
655 - "make doxygen" now works with out-of-tree builds. Closes
657 - Make sure that doxygen outputs documentation for all of our C
658 files. Previously, some were missing @file declarations, causing
659 them to be ignored. Closes ticket 32307.
660 - Our "make doxygen" target now respects --enable-fatal-warnings by
661 default, and does not warn about items that are missing
662 documentation. To warn about missing documentation, run configure
663 with the "--enable-missing-doc-warnings" flag: doing so suspends
664 fatal warnings for doxygen. Closes ticket 32385.
666 o Minor features (git scripts):
667 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
668 customisation. Closes ticket 32347.
669 - Add git-setup-dirs.sh, which sets up an upstream git repository
670 and worktrees for tor maintainers. Closes ticket 29603.
671 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
672 remote. Closes ticket 32347.
673 - Call the check_cocci_parse.sh script from the git commit and push
674 hooks. Closes ticket 31919.
675 - Make git-push-all.sh skip unchanged branches when pushing to
676 upstream. The script already skipped unchanged test branches.
678 - Make git-setup-dirs.sh create a master symlink in the worktree
679 directory. Closes ticket 32347.
680 - Skip unmodified source files when doing some existing git hook
681 checks. Related to ticket 31919.
683 o Minor features (IPv6, client):
684 - Make Tor clients tell dual-stack exits that they prefer IPv6
685 connections. This change is equivalent to setting the PreferIPv6
686 flag on SOCKSPorts (and most other listener ports). Tor Browser
687 has been setting this flag for some time, and we want to remove a
688 client distinguisher at exits. Closes ticket 32637.
690 o Minor features (portability, android):
691 - When building for Android, disable some tests that depend on $HOME
692 and/or pwdb, which Android doesn't have. Closes ticket 32825.
693 Patch from Hans-Christoph Steiner.
695 o Minor features (relay modularity):
696 - Split the relay and server pluggable transport config code into
697 separate files in the relay module. Disable this code when the
698 relay module is disabled. Closes part of ticket 32213.
699 - When the relay module is disabled, reject attempts to set the
700 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
701 ServerTransport* options, rather than ignoring the values of these
702 options. Closes part of ticket 32213.
704 o Minor features (relay):
705 - When the relay module is disabled, change the default config so
706 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
708 o Minor features (release tools):
709 - Port our ChangeLog formatting and sorting tools to Python 3.
712 o Minor features (testing):
713 - Detect some common failure cases for test_parseconf.sh in
714 src/test/conf_failures. Closes ticket 32451.
715 - Allow test_parseconf.sh to test expected log outputs for successful
716 configs, as well as failed configs. Closes ticket 32451.
717 - The test_parseconf.sh script now supports result variants for any
718 combination of the optional libraries lzma, nss, and zstd. Closes
721 o Minor features (tests, Android):
722 - When running the unit tests on Android, create temporary files in
723 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
724 patch from Hans-Christoph Steiner.
726 o Minor bugfixes (bridges):
727 - Lowercase the configured value of BridgeDistribution before adding
728 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
730 o Minor bugfixes (build system):
731 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
732 bugfix on 0.4.1.2-alpha.
734 o Minor bugfixes (configuration handling):
735 - Make control_event_conf_changed() take in a config_line_t instead
736 of a smartlist of alternating key/value entries. Fixes bug 31531;
737 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
739 o Minor bugfixes (configuration):
740 - Check for multiplication overflow when parsing memory units inside
741 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
742 - When dumping the configuration, stop adding a trailing space after
743 the option name when there is no option value. This issue only
744 affects options that accept an empty value or list. (Most options
745 reject empty values, or delete the entire line from the dumped
746 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
747 - Avoid changing the user's value of HardwareAccel as stored by
748 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
749 bug 32382; bugfix on 0.2.2.1-alpha.
750 - When creating a KeyDirectory with the same location as the
751 DataDirectory (not recommended), respect the DataDirectory's
752 group-readable setting if one has not been set for the
753 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
755 o Minor bugfixes (controller):
756 - In routerstatus_has_changed(), check all the fields that are
757 output over the control port. Fixes bug 20218; bugfix
760 o Minor bugfixes (correctness checks):
761 - Use GCC/Clang's printf-checking feature to make sure that
762 tor_assertf() arguments are correctly typed. Fixes bug 32765;
763 bugfix on 0.4.1.1-alpha.
765 o Minor bugfixes (developer tools):
766 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
767 31336; bugfix on 0.4.1.2-alpha.
769 o Minor bugfixes (dirauth module):
770 - Split the dirauth config code into a separate file in the dirauth
771 module. Disable this code when the dirauth module is disabled.
773 - When the dirauth module is disabled, reject attempts to set the
774 AuthoritativeDir option, rather than ignoring the value of the
775 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
777 o Minor bugfixes (embedded Tor):
778 - When starting Tor any time after the first time in a process,
779 register the thread in which it is running as the main thread.
780 Previously, we only did this on Windows, which could lead to bugs
781 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
784 o Minor bugfixes (git scripts):
785 - Avoid sleeping before the last push in git-push-all.sh. Closes
787 - Forward all unrecognised arguments in git-push-all.sh to git push.
790 o Minor bugfixes (hidden service v3):
791 - Do not rely on a "circuit established" flag for intro circuits but
792 instead always query the HS circuit map. This is to avoid sync
793 issue with that flag and the map. Fixes bug 32094; bugfix
796 o Minor bugfixes (logging, crash):
797 - Avoid a possible crash when trying to log a (fatal) assertion
798 failure about mismatched magic numbers in configuration objects.
799 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
801 o Minor bugfixes (onion service v2):
802 - When sending the INTRO cell for a v2 Onion Service, look at the
803 failure cache alongside timeout values to check if the intro point
804 is marked as failed. Previously, we only looked at the relay
805 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
808 o Minor bugfixes (onion services v3, client):
809 - Properly handle the client rendezvous circuit timeout. Previously
810 Tor would sometimes timeout a rendezvous circuit awaiting the
811 introduction ACK, and find itself unable to re-establish all
812 circuits because the rendezvous circuit timed out too early. Fixes
813 bug 32021; bugfix on 0.3.2.1-alpha.
815 o Minor bugfixes (onion services):
816 - In cancel_descriptor_fetches(), use
817 connection_list_by_type_purpose() instead of
818 connection_list_by_type_state(). Fixes bug 32639; bugfix on
819 0.3.2.1-alpha. Patch by Neel Chauhan.
821 o Minor bugfixes (scripts):
822 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
823 bugfix on 0.4.0.1-alpha.
825 o Minor bugfixes (test):
826 - Use the same code to find the tor binary in all of our test
827 scripts. This change makes sure we are always using the coverage
828 binary when coverage is enabled. Fixes bug 32368; bugfix
831 o Minor bugfixes (testing):
832 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
833 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
834 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
835 test_practracker.sh script. Doing so caused a test failure. Fixes
836 bug 32705; bugfix on 0.4.2.1-alpha.
837 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
838 skipping practracker checks. Fixes bug 32705; bugfix
841 o Minor bugfixes (tests):
842 - Our option-validation tests no longer depend on specially
843 configured non-default, non-passing sets of options. Previously,
844 the tests had been written to assume that options would _not_ be
845 set to their defaults, which led to needless complexity and
846 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
848 o Minor bugfixes (windows service):
849 - Initialize the publish/subscribe system when running as a windows
850 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
852 o Deprecated features:
853 - Deprecate the ClientAutoIPv6ORPort option. This option was not
854 true "Happy Eyeballs", and often failed on connections that
855 weren't reliably dual-stack. Closes ticket 32942. Patch by
859 - Provide a quickstart guide for a Circuit Padding Framework, and
860 documentation for researchers to implement and study circuit
861 padding machines. Closes ticket 28804.
862 - Add documentation in 'HelpfulTools.md' to describe how to build a
863 tag file. Closes ticket 32779.
864 - Create a high-level description of the long-term software
865 architecture goals. Closes ticket 32206.
866 - Describe the --dump-config command in the manual page. Closes
868 - Unite coding advice from this_not_that.md in torguts repo into our
869 coding standards document. Resolves ticket 31853.
872 - Our Doxygen configuration no longer generates LaTeX output. The
873 reference manual produced by doing this was over 4000 pages long,
874 and generally unusable. Closes ticket 32099.
875 - The option "TestingEstimatedDescriptorPropagationTime" is now
876 marked as obsolete. It has had no effect since 0.3.0.7, when
877 clients stopped rejecting consensuses "from the future". Closes
879 - We no longer support consensus methods before method 28; these
880 methods were only used by authorities running versions of Tor that
881 are now at end-of-life. In effect, this means that clients,
882 relays, and authorities now assume that authorities will be
883 running version 0.3.5.x or later. Closes ticket 32695.
886 - Add more test cases for tor's UTF-8 validation function. Also,
887 check the arguments passed to the function for consistency. Closes
889 - Improve test coverage for relay and dirauth config code, focusing
890 on option validation and normalization. Closes ticket 32213.
891 - Improve the consistency of test_parseconf.sh output, and run all
892 the tests, even if one fails. Closes ticket 32213.
893 - Re-enable the Travis CI macOS Chutney build, but don't let it
894 prevent the Travis job from finishing. (The Travis macOS jobs are
895 slow, so we don't want to have it delay the whole CI process.)
897 - Run the practracker unit tests in the pre-commit git hook. Closes
899 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
900 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
901 fix the sandbox errors in 32722. Closes ticket 32240.
903 o Code simplification and refactoring (channel):
904 - Channel layer had a variable length cell handler that was not used
905 and thus removed. Closes ticket 32892.
907 o Code simplification and refactoring (configuration):
908 - Immutability is now implemented as a flag on individual
909 configuration options rather than as part of the option-transition
910 checking code. Closes ticket 32344.
911 - Instead of keeping a list of configuration options to check for
912 relative paths, check all the options whose type is "FILENAME".
913 Solves part of ticket 32339.
914 - Our default log (which ordinarily sends NOTICE-level messages to
915 standard output) is now handled in a more logical manner.
916 Previously, we replaced the configured log options if they were
917 empty. Now, we interpret an empty set of log options as meaning
918 "use the default log". Closes ticket 31999.
919 - Remove some unused arguments from the options_validate() function,
920 to simplify our code and tests. Closes ticket 32187.
921 - Simplify the options_validate() code so that it looks at the
922 default options directly, rather than taking default options as an
923 argument. This change lets us simplify its interface. Closes
925 - Use our new configuration architecture to move most authority-
926 related options to the directory authority module. Closes
928 - When parsing the command line, handle options that determine our
929 "quiet level" and our mode of operation (e.g., --dump-config and
930 so on) all in one table. Closes ticket 32003.
932 o Code simplification and refactoring (controller):
933 - Create a new abstraction for formatting control protocol reply
934 lines based on key-value pairs. Refactor some existing control
935 protocol code to take advantage of this. Closes ticket 30984.
936 - Create a helper function that can fetch network status or
937 microdesc consensuses. Closes ticket 31684.
939 o Code simplification and refactoring (dirauth modularization):
940 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
942 - Replace some confusing identifiers in process_descs.c. Closes
944 - Simplify some relay and dirauth config code. Closes ticket 32213.
946 o Code simplification and refactoring (misc):
947 - Make all the structs we declare follow the same naming convention
948 of ending with "_t". Closes ticket 32415.
949 - Move and rename some configuration-related code for clarity.
951 - Our include.am files are now broken up by subdirectory.
952 Previously, src/core/include.am covered all of the subdirectories
953 in "core", "feature", and "app". Closes ticket 32137.
954 - Remove underused NS*() macros from test code: they make our tests
955 more confusing, especially for code-formatting tools. Closes
958 o Code simplification and refactoring (relay modularization):
959 - Disable relay_periodic when the relay module is disabled. Closes
961 - Disable relay_sys when the relay module is disabled. Closes
964 o Code simplification and refactoring (tool support):
965 - Add numerous missing dependencies to our include files, so that
966 they can be included in different reasonable orders and still
967 compile. Addresses part of ticket 32764.
968 - Fix some parts of our code that were difficult for Coccinelle to
969 parse. Related to ticket 31705.
970 - Fix some small issues in our code that prevented automatic
971 formatting tools from working. Addresses part of ticket 32764.
973 o Documentation (manpage):
974 - Alphabetize the Client Options section of the tor manpage. Closes
976 - Alphabetize the General Options section of the tor manpage. Closes
978 - In the tor(1) manpage, reword and improve formatting of the
979 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
980 32277. Based on work by Swati Thacker as part of Google Season
982 - In the tor(1) manpage, reword and improve formatting of the FILES,
983 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
984 Swati Thacker as part of Google Season of Docs.
986 o Testing (circuit, EWMA):
987 - Add unit tests for circuitmux and EWMA subsystems. Closes
990 o Testing (continuous integration):
991 - Use zstd in our Travis Linux builds. Closes ticket 32242.
994 Changes in version 0.4.2.5 - 2019-12-09
995 This is the first stable release in the 0.4.2.x series. This series
996 improves reliability and stability, and includes several stability and
997 correctness improvements for onion services. It also fixes many smaller
998 bugs present in previous series.
1000 Per our support policy, we will support the 0.4.2.x series for nine
1001 months, or until three months after the release of a stable 0.4.3.x:
1002 whichever is longer. If you need longer-term support, please stick
1003 with 0.3.5.x, which will we plan to support until Feb 2022.
1005 Per our support policy, we will support the 0.4.2.x series for nine
1006 months, or until three months after the release of a stable 0.4.3.x:
1007 whichever is longer. If you need longer-term support, please stick
1008 with 0.3.5.x, which will we plan to support until Feb 2022.
1010 Below are the changes since 0.4.1.4-rc. For a complete list of changes
1011 since 0.4.1.5, see the ReleaseNotes file.
1013 o Minor features (geoip):
1014 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1015 Country database. Closes ticket 32685.
1018 - Require C99 standards-conforming code in Travis CI, but allow GNU
1019 gcc extensions. Also activates clang's -Wtypedef-redefinition
1020 warnings. Build some jobs with -std=gnu99, and some jobs without.
1021 Closes ticket 32500.
1024 Changes in version 0.4.1.7 - 2019-12-09
1025 This release backports several bugfixes to improve stability and
1026 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
1027 including all relays relying on AccountingMax, should upgrade.
1029 o Major features (directory authorities, backport from 0.4.2.2-alpha):
1030 - Directory authorities now reject relays running all currently
1031 deprecated release series. The currently supported release series
1032 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1034 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
1035 - Avoid a possible crash when restarting Tor in embedded mode and
1036 enabling a different set of publish/subscribe messages. Fixes bug
1037 31898; bugfix on 0.4.1.1-alpha.
1039 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1040 - Relays now respect their AccountingMax bandwidth again. When
1041 relays entered "soft" hibernation (which typically starts when
1042 we've hit 90% of our AccountingMax), we had stopped checking
1043 whether we should enter hard hibernation. Soft hibernation refuses
1044 new connections and new circuits, but the existing circuits can
1045 continue, meaning that relays could have exceeded their configured
1046 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1048 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1049 - Stop ignoring torrc options after an %include directive, when the
1050 included directory ends with a file that does not contain any
1051 config options (but does contain comments or whitespace). Fixes
1052 bug 31408; bugfix on 0.3.1.1-alpha.
1054 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1055 - Onion services now always use the exact number of intro points
1056 configured with the HiddenServiceNumIntroductionPoints option (or
1057 fewer if nodes are excluded). Before, a service could sometimes
1058 pick more intro points than configured. Fixes bug 31548; bugfix
1061 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1062 - When building on Appveyor and Travis, pass the "-k" flag to make,
1063 so that we are informed of all compilation failures, not just the
1064 first one or two. Closes ticket 31372.
1066 o Minor features (geoip, backport from 0.4.2.5):
1067 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1068 Country database. Closes ticket 32685.
1070 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1071 - Avoid spurious errors when Appveyor CI fails before the install step.
1072 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1074 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1075 - Fix a BUG() assertion that occurs within a very small race window
1076 between when a client intro circuit opens and when its descriptor
1077 gets cleaned up from the cache. The circuit is now closed early,
1078 which will trigger a re-fetch of the descriptor and continue the
1079 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1081 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1082 - Avoid trying to read data from closed connections, which can cause
1083 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1084 30344; bugfix on 0.1.1.1-alpha.
1086 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1087 - On abort, try harder to flush the output buffers of log messages.
1088 On some platforms (macOS), log messages could be discarded when
1089 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1090 - Report the tor version whenever an assertion fails. Previously, we
1091 only reported the Tor version on some crashes, and some non-fatal
1092 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1093 - When tor aborts due to an error, close log file descriptors before
1094 aborting. Closing the logs makes some OSes flush log file buffers,
1095 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1098 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1099 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1100 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1101 - Disable backtrace signal handlers when shutting down tor. Fixes
1102 bug 31614; bugfix on 0.2.5.2-alpha.
1103 - Rate-limit our the logging message about the obsolete .exit
1104 notation. Previously, there was no limit on this warning, which
1105 could potentially be triggered many times by a hostile website.
1106 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1108 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1109 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1110 cell on a connection using the obsolete v1 link protocol. Log a
1111 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1113 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1114 - Reset the periodic events' "enabled" flag when Tor is shut down
1115 cleanly. Previously, this flag was left on, which caused periodic
1116 events not to be re-enabled when Tor was relaunched in-process
1117 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1120 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
1121 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1122 31736; bugfix on 0.0.7.
1124 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1125 - Remove overly strict assertions that triggered when a pluggable
1126 transport failed to launch. Fixes bug 31091; bugfix
1128 - Remove an assertion in the Unix process backend. This assertion
1129 would trigger when we failed to find the executable for a child
1130 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1132 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1133 - Avoid crashing when starting with a corrupt keys directory where
1134 the old ntor key and the new ntor key are identical. Fixes bug
1135 30916; bugfix on 0.2.4.8-alpha.
1137 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1138 - When testing port rebinding, don't busy-wait for tor to log.
1139 Instead, actually sleep for a short time before polling again.
1140 Also improve the formatting of control commands and log messages.
1141 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1143 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
1144 - Avoid a map_anon_nofork test failure due to a signed/unsigned
1145 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
1147 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1148 - Log bugs about the TLS read buffer's length only once, rather than
1149 filling the logs with similar warnings. Fixes bug 31939; bugfix
1152 o Documentation (backport from 0.4.2.2-alpha):
1153 - Explain why we can't destroy the backtrace buffer mutex. Explain
1154 why we don't need to destroy the log mutex. Closes ticket 31736.
1156 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1157 - Disable all but one Travis CI macOS build, to mitigate slow
1158 scheduling of Travis macOS jobs. Closes ticket 32177.
1159 - Run the chutney IPv6 networks as part of Travis CI. Closes
1161 - Simplify the Travis CI build matrix, and optimise for build time.
1162 Closes ticket 31859.
1163 - Use Windows Server 2019 instead of Windows Server 2016 in our
1164 Appveyor builds. Closes ticket 32086.
1166 o Testing (continuous integration, backport from 0.4.2.4-rc):
1167 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1168 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1169 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1170 until we can fix some Bionic permissions issues (see ticket
1171 32240). Related to ticket 31919.
1172 - Install the mingw OpenSSL package in Appveyor. This makes sure
1173 that the OpenSSL headers and libraries match in Tor's Appveyor
1174 builds. (This bug was triggered by an Appveyor image update.)
1175 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1177 o Testing (continuous integration, backport from 0.4.2.5):
1178 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1179 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1180 Build some jobs with -std=gnu99, and some jobs without.
1181 Closes ticket 32500.
1184 Changes in version 0.4.0.6 - 2019-12-09
1185 This is the second stable release in the 0.4.0.x series. This release
1186 backports several bugfixes to improve stability and correctness. Anyone
1187 experiencing build problems or crashes with 0.4.0.5, including all relays
1188 relying on AccountingMax, should upgrade.
1190 Note that, per our support policy, support for the 0.4.0.x series will end
1191 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
1192 latest stable release, or downgrade to 0.3.5.x, which will get long-term
1193 support until 1 Feb 2022.
1195 o Directory authority changes (backport from 0.4.1.5):
1196 - The directory authority "dizum" has a new IP address. Closes
1199 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
1200 - Consider our directory information to have changed when our list
1201 of bridges changes. Previously, Tor would not re-compute the
1202 status of its directory information when bridges changed, and
1203 therefore would not realize that it was no longer able to build
1204 circuits. Fixes part of bug 29875.
1205 - Do not count previously configured working bridges towards our
1206 total of working bridges. Previously, when Tor's list of bridges
1207 changed, it would think that the old bridges were still usable,
1208 and delay fetching router descriptors for the new ones. Fixes part
1209 of bug 29875; bugfix on 0.3.0.1-alpha.
1211 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
1212 - When considering upgrading circuits from "waiting for guard" to
1213 "open", always ignore circuits that are marked for close. Otherwise,
1214 we can end up in the situation where a subsystem is notified that
1215 a closing circuit has just opened, leading to undesirable
1216 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1218 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
1219 - Properly clean up the introduction point map when circuits change
1220 purpose from onion service circuits to pathbias, measurement, or
1221 other circuit types. This should fix some service-side instances
1222 of introduction point failure. Fixes bug 29034; bugfix
1225 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
1226 - Fix an unreachable bug in which an introduction point could try to
1227 send an INTRODUCE_ACK with a status code that Trunnel would refuse
1228 to encode, leading the relay to assert(). We've consolidated the
1229 ABI values into Trunnel now. Fixes bug 30454; bugfix
1231 - Clients can now handle unknown status codes from INTRODUCE_ACK
1232 cells. (The NACK behavior will stay the same.) This will allow us
1233 to extend status codes in the future without breaking the normal
1234 client behavior. Fixes another part of bug 30454; bugfix
1237 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1238 - Relays now respect their AccountingMax bandwidth again. When
1239 relays entered "soft" hibernation (which typically starts when
1240 we've hit 90% of our AccountingMax), we had stopped checking
1241 whether we should enter hard hibernation. Soft hibernation refuses
1242 new connections and new circuits, but the existing circuits can
1243 continue, meaning that relays could have exceeded their configured
1244 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1246 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1247 - Stop ignoring torrc options after an %include directive, when the
1248 included directory ends with a file that does not contain any
1249 config options (but does contain comments or whitespace). Fixes
1250 bug 31408; bugfix on 0.3.1.1-alpha.
1252 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1253 - Onion services now always use the exact number of intro points
1254 configured with the HiddenServiceNumIntroductionPoints option (or
1255 fewer if nodes are excluded). Before, a service could sometimes
1256 pick more intro points than configured. Fixes bug 31548; bugfix
1259 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
1260 - Add a "--list-modules" command to print a list of which compile-
1261 time modules are enabled. Closes ticket 30452.
1263 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
1264 - Remove sudo configuration lines from .travis.yml as they are no
1265 longer needed with current Travis build environment. Resolves
1268 o Minor features (continuous integration, backport from 0.4.1.4-rc):
1269 - Our Travis configuration now uses Chutney to run some network
1270 integration tests automatically. Closes ticket 29280.
1272 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1273 - When building on Appveyor and Travis, pass the "-k" flag to make,
1274 so that we are informed of all compilation failures, not just the
1275 first one or two. Closes ticket 31372.
1277 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
1278 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1279 in December 2018 (of which ~122 were still functional), with a
1280 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1281 in June 2019. Closes ticket 28795.
1283 o Minor features (geoip, backport from 0.4.2.5):
1284 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1285 Country database. Closes ticket 32685.
1287 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1288 - Change "make test-stem" so it only runs the stem tests that use
1289 tor. This change makes test-stem faster and more reliable. Closes
1292 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1293 - Avoid spurious errors when Appveyor CI fails before the install step.
1294 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1296 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1297 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1298 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1300 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
1301 - Fix a logic error that prevented the SessionGroup sub-option from
1302 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1304 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
1305 - On relays, properly check that a padding machine is absent before
1306 logging a warning about it being absent. Fixes bug 30649; bugfix
1309 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1310 - Fix a BUG() assertion that occurs within a very small race window
1311 between when a client intro circuit opens and when its descriptor
1312 gets cleaned up from the cache. The circuit is now closed early,
1313 which will trigger a re-fetch of the descriptor and continue the
1314 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1316 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
1317 - Don't believe clock skew results from NETINFO cells that appear to
1318 arrive before we sent the VERSIONS cells they are responding to.
1319 Previously, we would accept them up to 3 minutes "in the past".
1320 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1322 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
1323 - Fix a compilation warning on Windows about casting a function
1324 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1327 o Minor bugfixes (compilation, backport from 0.4.1.5):
1328 - Avoid using labs() on time_t, which can cause compilation warnings
1329 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1331 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1332 - Suppress spurious float-conversion warnings from GCC when calling
1333 floating-point classifier functions on FreeBSD. Fixes part of bug
1334 31687; bugfix on 0.3.1.5-alpha.
1336 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
1337 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
1338 due to missing declarations of abort(), and prevent other such
1339 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
1341 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1342 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1343 want authentication along with configured (but unused!)
1344 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1346 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1347 - Avoid trying to read data from closed connections, which can cause
1348 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1349 30344; bugfix on 0.1.1.1-alpha.
1351 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1352 - Allow the test-stem job to fail in Travis, because it sometimes
1353 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1354 - Skip test_rebind on macOS in Travis, because it is unreliable on
1355 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1356 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1357 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1359 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1360 - Avoid a set of possible code paths that could try to use freed
1361 memory in routerlist_free() while Tor was exiting. Fixes bug
1362 31003; bugfix on 0.1.2.2-alpha.
1364 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1365 - Stop crashing after parsing an unknown descriptor purpose
1366 annotation. We think this bug can only be triggered by modifying a
1367 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1369 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1370 - Move the "bandwidth-file-headers" line in directory authority
1371 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1374 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1375 - On abort, try harder to flush the output buffers of log messages.
1376 On some platforms (macOS), log messages could be discarded when
1377 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1378 - Report the tor version whenever an assertion fails. Previously, we
1379 only reported the Tor version on some crashes, and some non-fatal
1380 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1382 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1383 - When extracting an IPv6 address from a PF-based proxy, verify that
1384 we are actually configured to receive an IPv6 address, and log an
1385 internal error if not. Fixes part of bug 31687; bugfix
1388 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1389 - When tor is missing descriptors for some primary entry guards,
1390 make the log message less alarming. It's normal for descriptors to
1391 expire, as long as tor fetches new ones soon after. Fixes bug
1392 31657; bugfix on 0.3.3.1-alpha.
1394 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1395 - Do not log a warning when running with an OpenSSL version other
1396 than the one Tor was compiled with, if the two versions should be
1397 compatible. Previously, we would warn whenever the version was
1398 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1400 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1401 - Change log level of message "Hash of session info was not as
1402 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1405 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1406 - Rate-limit our the logging message about the obsolete .exit
1407 notation. Previously, there was no limit on this warning, which
1408 could potentially be triggered many times by a hostile website.
1409 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1411 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1412 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1413 cell on a connection using the obsolete v1 link protocol. Log a
1414 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1416 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1417 - Reset the periodic events' "enabled" flag when Tor is shut down
1418 cleanly. Previously, this flag was left on, which caused periodic
1419 events not to be re-enabled when Tor was relaunched in-process
1420 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1423 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
1424 - Avoid a minor memory leak that could occur on relays when failing
1425 to create a "keys" directory. Fixes bug 30148; bugfix
1428 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
1429 - Fix a trivial memory leak when parsing an invalid value
1430 from a download schedule in the configuration. Fixes bug
1431 30894; bugfix on 0.3.4.1-alpha.
1433 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
1434 - Fix usage of minherit() on NetBSD and other platforms that define
1435 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
1436 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
1438 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
1439 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
1440 implemenation) when failing to load an onion service client
1441 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
1443 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
1444 - When purging the DNS cache because of an out-of-memory condition,
1445 try purging just the older entries at first. Previously, we would
1446 always purge the whole thing. Fixes bug 29617; bugfix
1449 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
1450 - Avoid crashing in our tor_vasprintf() implementation on systems
1451 that define neither vasprintf() nor _vscprintf(). (This bug has
1452 been here long enough that we question whether people are running
1453 Tor on such systems, but we're applying the fix out of caution.)
1454 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
1457 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1458 - Remove overly strict assertions that triggered when a pluggable
1459 transport failed to launch. Fixes bug 31091; bugfix
1461 - Remove an assertion in the Unix process backend. This assertion
1462 would trigger when we failed to find the executable for a child
1463 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1465 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1466 - Avoid crashing when starting with a corrupt keys directory where
1467 the old ntor key and the new ntor key are identical. Fixes bug
1468 30916; bugfix on 0.2.4.8-alpha.
1470 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1471 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1472 31463; bugfix on 0.3.5.4-alpha.
1474 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1475 - When testing port rebinding, don't busy-wait for tor to log.
1476 Instead, actually sleep for a short time before polling again.
1477 Also improve the formatting of control commands and log messages.
1478 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1480 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1481 - Log bugs about the TLS read buffer's length only once, rather than
1482 filling the logs with similar warnings. Fixes bug 31939; bugfix
1485 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
1486 - Always retry v2 single onion service intro and rend circuits with
1487 a 3-hop path. Previously, v2 single onion services used a 3-hop
1488 path when rendezvous circuits were retried after a remote or
1489 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1490 23818; bugfix on 0.2.9.3-alpha.
1491 - Make v3 single onion services fall back to a 3-hop intro, when all
1492 intro points are unreachable via a 1-hop path. Previously, v3
1493 single onion services failed when all intro nodes were unreachable
1494 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1496 o Documentation (backport from 0.4.2.1-alpha):
1497 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1498 notice.html so that operators no longer have to host it
1499 themselves. Closes ticket 31089.
1501 o Testing (backport from 0.4.1.2-alpha):
1502 - Specify torrc paths (with empty files) when launching tor in
1503 integration tests; refrain from reading user and system torrcs.
1504 Resolves issue 29702.
1506 o Testing (continuous integration, backport from 0.4.1.1-alpha):
1507 - In Travis, show stem's tor log after failure. Closes ticket 30234.
1509 o Testing (continuous integration, backport from 0.4.1.5):
1510 - In Travis, make stem log a controller trace to the console, and
1511 tail stem's tor log after failure. Closes ticket 30591.
1512 - In Travis, only run the stem tests that use a tor binary. Closes
1515 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1516 - Disable all but one Travis CI macOS build, to mitigate slow
1517 scheduling of Travis macOS jobs. Closes ticket 32177.
1518 - Run the chutney IPv6 networks as part of Travis CI. Closes
1520 - Simplify the Travis CI build matrix, and optimise for build time.
1521 Closes ticket 31859.
1522 - Use Windows Server 2019 instead of Windows Server 2016 in our
1523 Appveyor builds. Closes ticket 32086.
1525 o Testing (continuous integration, backport from 0.4.2.4-rc):
1526 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1527 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1528 until we can fix some Bionic permissions issues (see ticket
1529 32240). Related to ticket 31919.
1530 - Install the mingw OpenSSL package in Appveyor. This makes sure
1531 that the OpenSSL headers and libraries match in Tor's Appveyor
1532 builds. (This bug was triggered by an Appveyor image update.)
1533 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1534 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1536 o Testing (continuous integration, backport from 0.4.2.5):
1537 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1538 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1539 Build some jobs with -std=gnu99, and some jobs without.
1540 Closes ticket 32500.
1542 Changes in version 0.3.5.9 - 2019-12-09
1543 Tor 0.3.5.9 backports serveral fixes from later releases, including
1544 several that affect bridge users, relay stability, onion services,
1547 o Directory authority changes (backport from 0.4.1.5):
1548 - The directory authority "dizum" has a new IP address. Closes
1551 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
1552 - Consider our directory information to have changed when our list
1553 of bridges changes. Previously, Tor would not re-compute the
1554 status of its directory information when bridges changed, and
1555 therefore would not realize that it was no longer able to build
1556 circuits. Fixes part of bug 29875.
1557 - Do not count previously configured working bridges towards our
1558 total of working bridges. Previously, when Tor's list of bridges
1559 changed, it would think that the old bridges were still usable,
1560 and delay fetching router descriptors for the new ones. Fixes part
1561 of bug 29875; bugfix on 0.3.0.1-alpha.
1563 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
1564 - When considering upgrading circuits from "waiting for guard" to
1565 "open", always ignore circuits that are marked for close. Otherwise,
1566 we can end up in the situation where a subsystem is notified that
1567 a closing circuit has just opened, leading to undesirable
1568 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1570 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
1571 - When running with NSS, disable TLS 1.2 ciphersuites that use
1572 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
1573 these ciphersuites don't work -- which caused relays to fail to
1574 handshake with one another when these ciphersuites were enabled.
1575 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
1577 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
1578 - Properly clean up the introduction point map when circuits change
1579 purpose from onion service circuits to pathbias, measurement, or
1580 other circuit types. This should fix some service-side instances
1581 of introduction point failure. Fixes bug 29034; bugfix
1584 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
1585 - Fix an unreachable bug in which an introduction point could try to
1586 send an INTRODUCE_ACK with a status code that Trunnel would refuse
1587 to encode, leading the relay to assert(). We've consolidated the
1588 ABI values into Trunnel now. Fixes bug 30454; bugfix
1590 - Clients can now handle unknown status codes from INTRODUCE_ACK
1591 cells. (The NACK behavior will stay the same.) This will allow us
1592 to extend status codes in the future without breaking the normal
1593 client behavior. Fixes another part of bug 30454; bugfix
1596 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1597 - Stop ignoring torrc options after an %include directive, when the
1598 included directory ends with a file that does not contain any
1599 config options (but does contain comments or whitespace). Fixes
1600 bug 31408; bugfix on 0.3.1.1-alpha.
1602 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1603 - Onion services now always use the exact number of intro points
1604 configured with the HiddenServiceNumIntroductionPoints option (or
1605 fewer if nodes are excluded). Before, a service could sometimes
1606 pick more intro points than configured. Fixes bug 31548; bugfix
1609 o Minor features (address selection, backport from 0.4.0.3-alpha):
1610 - Treat the subnet 100.64.0.0/10 as public for some purposes;
1611 private for others. This subnet is the RFC 6598 (Carrier Grade
1612 NAT) IP range, and is deployed by many ISPs as an alternative to
1613 RFC 1918 that does not break existing internal networks. Tor now
1614 blocks SOCKS and control ports on these addresses and warns users
1615 if client ports or ExtORPorts are listening on a RFC 6598 address.
1616 Closes ticket 28525. Patch by Neel Chauhan.
1618 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
1619 - Make bandwidth authorities ignore relays that are reported in the
1620 bandwidth file with the flag "vote=0". This change allows us to
1621 report unmeasured relays for diagnostic reasons without including
1622 their bandwidth in the bandwidth authorities' vote. Closes
1625 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
1626 - Add a "--list-modules" command to print a list of which compile-
1627 time modules are enabled. Closes ticket 30452.
1629 o Minor features (continuous integration, backport from 0.4.0.4-rc):
1630 - On Travis Rust builds, cleanup Rust registry and refrain from
1631 caching the "target/" directory to speed up builds. Resolves
1634 o Minor features (continuous integration, backport from 0.4.0.5):
1635 - In Travis, tell timelimit to use stem's backtrace signals, and
1636 launch python directly from timelimit, so python receives the
1637 signals from timelimit, rather than make. Closes ticket 30117.
1639 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
1640 - Remove sudo configuration lines from .travis.yml as they are no
1641 longer needed with current Travis build environment. Resolves
1644 o Minor features (continuous integration, backport from 0.4.1.4-rc):
1645 - Our Travis configuration now uses Chutney to run some network
1646 integration tests automatically. Closes ticket 29280.
1648 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1649 - When building on Appveyor and Travis, pass the "-k" flag to make,
1650 so that we are informed of all compilation failures, not just the
1651 first one or two. Closes ticket 31372.
1653 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
1654 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1655 in December 2018 (of which ~122 were still functional), with a
1656 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1657 in June 2019. Closes ticket 28795.
1659 o Minor features (geoip, backport from 0.4.2.5):
1660 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1661 Country database. Closes ticket 32685.
1663 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
1664 - Try to log an error from NSS (if there is any) and a more useful
1665 description of our situation if we are using NSS and a call to
1666 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
1668 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1669 - Change "make test-stem" so it only runs the stem tests that use
1670 tor. This change makes test-stem faster and more reliable. Closes
1673 o Minor bugfixes (security, backport from 0.4.0.4-rc):
1674 - Verify in more places that we are not about to create a buffer
1675 with more than INT_MAX bytes, to avoid possible OOB access in the
1676 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
1677 fixed by Tobias Stoeckmann.
1678 - Fix a potential double free bug when reading huge bandwidth files.
1679 The issue is not exploitable in the current Tor network because
1680 the vulnerable code is only reached when directory authorities
1681 read bandwidth files, but bandwidth files come from a trusted
1682 source (usually the authorities themselves). Furthermore, the
1683 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
1684 which are not used by any of the current authorities. Fixes bug
1685 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
1688 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
1689 - Reset coverage state on disk after Travis CI has finished. This
1690 should prevent future coverage merge errors from causing the test
1691 suite for the "process" subsystem to fail. The process subsystem
1692 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
1694 - Terminate test-stem if it takes more than 9.5 minutes to run.
1695 (Travis terminates the job after 10 minutes of no output.)
1696 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
1698 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1699 - Avoid spurious errors when Appveyor CI fails before the install step.
1700 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1702 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1703 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1704 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1706 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
1707 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
1708 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
1711 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
1712 - Fix a logic error that prevented the SessionGroup sub-option from
1713 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1715 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1716 - Fix a BUG() assertion that occurs within a very small race window
1717 between when a client intro circuit opens and when its descriptor
1718 gets cleaned up from the cache. The circuit is now closed early,
1719 which will trigger a re-fetch of the descriptor and continue the
1720 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1722 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
1723 - Don't believe clock skew results from NETINFO cells that appear to
1724 arrive before we sent the VERSIONS cells they are responding to.
1725 Previously, we would accept them up to 3 minutes "in the past".
1726 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1728 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
1729 - Fix a compilation warning on Windows about casting a function
1730 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1733 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
1734 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1735 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1737 o Minor bugfixes (compilation, backport from 0.4.1.5):
1738 - Avoid using labs() on time_t, which can cause compilation warnings
1739 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1741 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1742 - Suppress spurious float-conversion warnings from GCC when calling
1743 floating-point classifier functions on FreeBSD. Fixes part of bug
1744 31687; bugfix on 0.3.1.5-alpha.
1746 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
1747 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
1748 due to missing declarations of abort(), and prevent other such
1749 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
1751 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1752 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1753 want authentication along with configured (but unused!)
1754 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1756 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1757 - Avoid trying to read data from closed connections, which can cause
1758 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1759 30344; bugfix on 0.1.1.1-alpha.
1761 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1762 - Allow the test-stem job to fail in Travis, because it sometimes
1763 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1764 - Skip test_rebind on macOS in Travis, because it is unreliable on
1765 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1766 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1767 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1769 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1770 - Avoid a set of possible code paths that could try to use freed
1771 memory in routerlist_free() while Tor was exiting. Fixes bug
1772 31003; bugfix on 0.1.2.2-alpha.
1774 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1775 - Stop crashing after parsing an unknown descriptor purpose
1776 annotation. We think this bug can only be triggered by modifying a
1777 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1779 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1780 - Move the "bandwidth-file-headers" line in directory authority
1781 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1784 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1785 - On abort, try harder to flush the output buffers of log messages.
1786 On some platforms (macOS), log messages could be discarded when
1787 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1788 - Report the tor version whenever an assertion fails. Previously, we
1789 only reported the Tor version on some crashes, and some non-fatal
1790 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1792 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1793 - When extracting an IPv6 address from a PF-based proxy, verify that
1794 we are actually configured to receive an IPv6 address, and log an
1795 internal error if not. Fixes part of bug 31687; bugfix
1798 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1799 - When tor is missing descriptors for some primary entry guards,
1800 make the log message less alarming. It's normal for descriptors to
1801 expire, as long as tor fetches new ones soon after. Fixes bug
1802 31657; bugfix on 0.3.3.1-alpha.
1804 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
1805 - Avoid logging that we are relaxing a circuit timeout when that
1806 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1808 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
1809 - Correct a misleading error message when IPv4Only or IPv6Only is
1810 used but the resolved address can not be interpreted as an address
1811 of the specified IP version. Fixes bug 13221; bugfix on
1812 0.2.3.9-alpha. Patch from Kris Katterjohn.
1813 - Log the correct port number for listening sockets when "auto" is
1814 used to let Tor pick the port number. Previously, port 0 was
1815 logged instead of the actual port number. Fixes bug 29144; bugfix
1816 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1817 - Stop logging a BUG() warning when Tor is waiting for exit
1818 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
1820 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1821 - Do not log a warning when running with an OpenSSL version other
1822 than the one Tor was compiled with, if the two versions should be
1823 compatible. Previously, we would warn whenever the version was
1824 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1826 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1827 - Change log level of message "Hash of session info was not as
1828 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1831 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1832 - Rate-limit our the logging message about the obsolete .exit
1833 notation. Previously, there was no limit on this warning, which
1834 could potentially be triggered many times by a hostile website.
1835 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1837 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1838 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1839 cell on a connection using the obsolete v1 link protocol. Log a
1840 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1842 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1843 - Reset the periodic events' "enabled" flag when Tor is shut down
1844 cleanly. Previously, this flag was left on, which caused periodic
1845 events not to be re-enabled when Tor was relaunched in-process
1846 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1849 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
1850 - Avoid a minor memory leak that could occur on relays when failing
1851 to create a "keys" directory. Fixes bug 30148; bugfix
1854 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
1855 - Fix a trivial memory leak when parsing an invalid value
1856 from a download schedule in the configuration. Fixes bug
1857 30894; bugfix on 0.3.4.1-alpha.
1859 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
1860 - Refactor the shared random state's memory management so that it
1861 actually takes ownership of the shared random value pointers.
1862 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
1864 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
1865 - Stop leaking parts of the shared random state in the shared-random
1866 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
1868 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
1869 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
1870 implemenation) when failing to load an onion service client
1871 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
1873 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
1874 - When purging the DNS cache because of an out-of-memory condition,
1875 try purging just the older entries at first. Previously, we would
1876 always purge the whole thing. Fixes bug 29617; bugfix
1879 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
1880 - Avoid crashing in our tor_vasprintf() implementation on systems
1881 that define neither vasprintf() nor _vscprintf(). (This bug has
1882 been here long enough that we question whether people are running
1883 Tor on such systems, but we're applying the fix out of caution.)
1884 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
1887 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1888 - Avoid crashing when starting with a corrupt keys directory where
1889 the old ntor key and the new ntor key are identical. Fixes bug
1890 30916; bugfix on 0.2.4.8-alpha.
1892 o Minor bugfixes (rust, backport from 0.4.0.5):
1893 - Abort on panic in all build profiles, instead of potentially
1894 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
1896 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1897 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1898 31463; bugfix on 0.3.5.4-alpha.
1900 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
1901 - Allow connections to single onion services to remain idle without
1902 being disconnected. Previously, relays acting as rendezvous points
1903 for single onion services were mistakenly closing idle rendezvous
1904 circuits after 60 seconds, thinking that they were unused
1905 directory-fetching circuits that had served their purpose. Fixes
1906 bug 29665; bugfix on 0.2.1.26.
1908 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
1909 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
1910 relay and bridge extra-info documents. Fixes bug 29017; bugfix
1913 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
1914 - Downgrade some LOG_ERR messages in the address/* tests to
1915 warnings. The LOG_ERR messages were occurring when we had no
1916 configured network. We were failing the unit tests, because we
1917 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
1918 29530; bugfix on 0.3.5.8.
1919 - Fix our gcov wrapper script to look for object files at the
1920 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
1922 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
1923 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
1924 recent test-network.sh to use new chutney features in CI. Fixes
1925 bug 29703; bugfix on 0.2.9.1-alpha.
1926 - Fix a test failure on Windows caused by an unexpected "BUG"
1927 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
1930 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1931 - When testing port rebinding, don't busy-wait for tor to log.
1932 Instead, actually sleep for a short time before polling again.
1933 Also improve the formatting of control commands and log messages.
1934 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1936 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
1937 - When classifying a client's selection of TLS ciphers, if the
1938 client ciphers are not yet available, do not cache the result.
1939 Previously, we had cached the unavailability of the cipher list
1940 and never looked again, which in turn led us to assume that the
1941 client only supported the ancient V1 link protocol. This, in turn,
1942 was causing Stem integration tests to stall in some cases. Fixes
1943 bug 30021; bugfix on 0.2.4.8-alpha.
1945 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1946 - Log bugs about the TLS read buffer's length only once, rather than
1947 filling the logs with similar warnings. Fixes bug 31939; bugfix
1950 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
1951 - Always retry v2 single onion service intro and rend circuits with
1952 a 3-hop path. Previously, v2 single onion services used a 3-hop
1953 path when rendezvous circuits were retried after a remote or
1954 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1955 23818; bugfix on 0.2.9.3-alpha.
1956 - Make v3 single onion services fall back to a 3-hop intro, when all
1957 intro points are unreachable via a 1-hop path. Previously, v3
1958 single onion services failed when all intro nodes were unreachable
1959 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1961 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
1962 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
1963 Windows Server 2012 R2 job. The remaining 2 jobs still provide
1964 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
1965 fast_finish, so failed jobs terminate the build immediately. Fixes
1966 bug 29601; bugfix on 0.3.5.4-alpha.
1968 o Documentation (backport from 0.4.2.1-alpha):
1969 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1970 notice.html so that operators no longer have to host it
1971 themselves. Closes ticket 31089.
1973 o Testing (backport from 0.4.1.2-alpha):
1974 - Specify torrc paths (with empty files) when launching tor in
1975 integration tests; refrain from reading user and system torrcs.
1976 Resolves issue 29702.
1978 o Testing (continuous integration, backport from 0.4.1.1-alpha):
1979 - In Travis, show stem's tor log after failure. Closes ticket 30234.
1981 o Testing (continuous integration, backport from 0.4.1.5):
1982 - In Travis, make stem log a controller trace to the console, and
1983 tail stem's tor log after failure. Closes ticket 30591.
1984 - In Travis, only run the stem tests that use a tor binary. Closes
1987 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1988 - Disable all but one Travis CI macOS build, to mitigate slow
1989 scheduling of Travis macOS jobs. Closes ticket 32177.
1990 - Run the chutney IPv6 networks as part of Travis CI. Closes
1992 - Simplify the Travis CI build matrix, and optimise for build time.
1993 Closes ticket 31859.
1994 - Use Windows Server 2019 instead of Windows Server 2016 in our
1995 Appveyor builds. Closes ticket 32086.
1997 o Testing (continuous integration, backport from 0.4.2.4-rc):
1998 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1999 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2000 until we can fix some Bionic permissions issues (see ticket
2001 32240). Related to ticket 31919.
2002 - Install the mingw OpenSSL package in Appveyor. This makes sure
2003 that the OpenSSL headers and libraries match in Tor's Appveyor
2004 builds. (This bug was triggered by an Appveyor image update.)
2005 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2006 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2008 o Testing (continuous integration, backport from 0.4.2.5):
2009 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2010 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2011 Build some jobs with -std=gnu99, and some jobs without.
2012 Closes ticket 32500.
2014 Changes in version 0.4.2.4-rc - 2019-11-15
2015 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
2016 several bugs from earlier versions, including a few that would result in
2017 stack traces or incorrect behavior.
2019 o Minor features (build system):
2020 - Make pkg-config use --prefix when cross-compiling, if
2021 PKG_CONFIG_PATH is not set. Closes ticket 32191.
2023 o Minor features (geoip):
2024 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
2025 Country database. Closes ticket 32440.
2027 o Minor bugfixes (client, onion service v3):
2028 - Fix a BUG() assertion that occurs within a very small race window
2029 between when a client intro circuit opens and when its descriptor
2030 gets cleaned up from the cache. The circuit is now closed early,
2031 which will trigger a re-fetch of the descriptor and continue the
2032 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2034 o Minor bugfixes (code quality):
2035 - Fix "make check-includes" so it runs correctly on out-of-tree
2036 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
2038 o Minor bugfixes (configuration):
2039 - Log the option name when skipping an obsolete option. Fixes bug
2040 32295; bugfix on 0.4.2.1-alpha.
2042 o Minor bugfixes (crash):
2043 - When running Tor with an option like --verify-config or
2044 --dump-config that does not start the event loop, avoid crashing
2045 if we try to exit early because of an error. Fixes bug 32407;
2046 bugfix on 0.3.3.1-alpha.
2048 o Minor bugfixes (directory):
2049 - When checking if a directory connection is anonymous, test if the
2050 circuit was marked for close before looking at its channel. This
2051 avoids a BUG() stacktrace if the circuit was previously closed.
2052 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
2054 o Minor bugfixes (shellcheck):
2055 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
2056 32402; bugfix on 0.4.2.1-alpha.
2057 - Start checking most scripts for shellcheck errors again. Fixes bug
2058 32402; bugfix on 0.4.2.1-alpha.
2060 o Testing (continuous integration):
2061 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2062 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2063 until we can fix some Bionic permissions issues (see ticket
2064 32240). Related to ticket 31919.
2065 - Install the mingw OpenSSL package in Appveyor. This makes sure
2066 that the OpenSSL headers and libraries match in Tor's Appveyor
2067 builds. (This bug was triggered by an Appveyor image update.)
2068 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2069 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2072 Changes in version 0.4.2.3-alpha - 2019-10-24
2073 This release fixes several bugs from the previous alpha release, and
2074 from earlier versions of Tor.
2076 o Major bugfixes (relay):
2077 - Relays now respect their AccountingMax bandwidth again. When
2078 relays entered "soft" hibernation (which typically starts when
2079 we've hit 90% of our AccountingMax), we had stopped checking
2080 whether we should enter hard hibernation. Soft hibernation refuses
2081 new connections and new circuits, but the existing circuits can
2082 continue, meaning that relays could have exceeded their configured
2083 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2085 o Major bugfixes (v3 onion services):
2086 - Onion services now always use the exact number of intro points
2087 configured with the HiddenServiceNumIntroductionPoints option (or
2088 fewer if nodes are excluded). Before, a service could sometimes
2089 pick more intro points than configured. Fixes bug 31548; bugfix
2092 o Minor feature (onion services, control port):
2093 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
2094 (v3) onion services. Previously it defaulted to RSA1024 (v2).
2095 Closes ticket 29669.
2097 o Minor features (testing):
2098 - When running tests that attempt to look up hostnames, replace the
2099 libc name lookup functions with ones that do not actually touch
2100 the network. This way, the tests complete more quickly in the
2101 presence of a slow or missing DNS resolver. Closes ticket 31841.
2103 o Minor features (testing, continuous integration):
2104 - Disable all but one Travis CI macOS build, to mitigate slow
2105 scheduling of Travis macOS jobs. Closes ticket 32177.
2106 - Run the chutney IPv6 networks as part of Travis CI. Closes
2108 - Simplify the Travis CI build matrix, and optimise for build time.
2109 Closes ticket 31859.
2110 - Use Windows Server 2019 instead of Windows Server 2016 in our
2111 Appveyor builds. Closes ticket 32086.
2113 o Minor bugfixes (build system):
2114 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
2115 32124; bugfix on 0.3.4.1-alpha.
2116 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
2118 - Stop failing when jemalloc is requested, but tcmalloc is not
2119 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
2120 - When pkg-config is not installed, or a library that depends on
2121 pkg-config is not found, tell the user what to do to fix the
2122 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
2124 o Minor bugfixes (connections):
2125 - Avoid trying to read data from closed connections, which can cause
2126 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2127 30344; bugfix on 0.1.1.1-alpha.
2129 o Minor bugfixes (error handling):
2130 - Always lock the backtrace buffer before it is used. Fixes bug
2131 31734; bugfix on 0.2.5.3-alpha.
2133 o Minor bugfixes (mainloop, periodic events, in-process API):
2134 - Reset the periodic events' "enabled" flag when Tor is shut down
2135 cleanly. Previously, this flag was left on, which caused periodic
2136 events not to be re-enabled when Tor was relaunched in-process
2137 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2140 o Minor bugfixes (process management):
2141 - Remove overly strict assertions that triggered when a pluggable
2142 transport failed to launch. Fixes bug 31091; bugfix
2144 - Remove an assertion in the Unix process backend. This assertion
2145 would trigger when we failed to find the executable for a child
2146 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2148 o Minor bugfixes (testing):
2149 - Avoid intermittent test failures due to a test that had relied on
2150 inconsistent timing sources. Fixes bug 31995; bugfix
2152 - When testing port rebinding, don't busy-wait for tor to log.
2153 Instead, actually sleep for a short time before polling again.
2154 Also improve the formatting of control commands and log messages.
2155 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2157 o Minor bugfixes (tls, logging):
2158 - Log bugs about the TLS read buffer's length only once, rather than
2159 filling the logs with similar warnings. Fixes bug 31939; bugfix
2162 o Minor bugfixes (v3 onion services):
2163 - Fix an implicit conversion from ssize_t to size_t discovered by
2164 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
2165 - Fix a memory leak in an unlikely error code path when encoding HS
2166 DoS establish intro extension cell. Fixes bug 32063; bugfix
2168 - When cleaning up intro circuits for a v3 onion service, don't
2169 remove circuits that have an established or pending circuit, even
2170 if they ran out of retries. This way, we don't remove a circuit on
2171 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
2174 - Correct the description of "GuardLifetime". Fixes bug 31189;
2175 bugfix on 0.3.0.1-alpha.
2176 - Make clear in the man page, in both the bandwidth section and the
2177 AccountingMax section, that Tor counts in powers of two, not
2178 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
2179 bytes. Resolves ticket 32106.
2182 Changes in version 0.4.2.2-alpha - 2019-10-07
2183 This release fixes several bugs from the previous alpha release, and
2184 from earlier versions. It also includes a change in authorities, so
2185 that they begin to reject the currently unsupported release series.
2187 o Major features (directory authorities):
2188 - Directory authorities now reject relays running all currently
2189 deprecated release series. The currently supported release series
2190 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2192 o Major bugfixes (embedded Tor):
2193 - Avoid a possible crash when restarting Tor in embedded mode and
2194 enabling a different set of publish/subscribe messages. Fixes bug
2195 31898; bugfix on 0.4.1.1-alpha.
2197 o Major bugfixes (torrc parsing):
2198 - Stop ignoring torrc options after an %include directive, when the
2199 included directory ends with a file that does not contain any
2200 config options (but does contain comments or whitespace). Fixes
2201 bug 31408; bugfix on 0.3.1.1-alpha.
2203 o Minor features (auto-formatting scripts):
2204 - When annotating C macros, never generate a line that our check-
2205 spaces script would reject. Closes ticket 31759.
2206 - When annotating C macros, try to remove cases of double-negation.
2207 Closes ticket 31779.
2209 o Minor features (continuous integration):
2210 - When building on Appveyor and Travis, pass the "-k" flag to make,
2211 so that we are informed of all compilation failures, not just the
2212 first one or two. Closes ticket 31372.
2214 o Minor features (geoip):
2215 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
2216 Country database. Closes ticket 31931.
2218 o Minor features (maintenance scripts):
2219 - Add a Coccinelle script to detect bugs caused by incrementing or
2220 decrementing a variable inside a call to log_debug(). Since
2221 log_debug() is a macro whose arguments are conditionally
2222 evaluated, it is usually an error to do this. One such bug was
2223 30628, in which SENDME cells were miscounted by a decrement
2224 operator inside a log_debug() call. Closes ticket 30743.
2226 o Minor features (onion services v3):
2227 - Assist users who try to setup v2 client authorization in v3 onion
2228 services by pointing them to the right documentation. Closes
2231 o Minor bugfixes (Appveyor continuous integration):
2232 - Avoid spurious errors when Appveyor CI fails before the install
2233 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2235 o Minor bugfixes (best practices tracker):
2236 - When listing overbroad exceptions, do not also list problems, and
2237 do not list insufficiently broad exceptions. Fixes bug 31338;
2238 bugfix on 0.4.2.1-alpha.
2240 o Minor bugfixes (controller protocol):
2241 - Fix the MAPADDRESS controller command to accept one or more
2242 arguments. Previously, it required two or more arguments, and
2243 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2245 o Minor bugfixes (logging):
2246 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2247 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2248 - Disable backtrace signal handlers when shutting down tor. Fixes
2249 bug 31614; bugfix on 0.2.5.2-alpha.
2250 - Rate-limit our the logging message about the obsolete .exit
2251 notation. Previously, there was no limit on this warning, which
2252 could potentially be triggered many times by a hostile website.
2253 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2254 - When initialising log domain masks, only set known log domains.
2255 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
2257 o Minor bugfixes (logging, protocol violations):
2258 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2259 cell on a connection using the obsolete v1 link protocol. Log a
2260 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2262 o Minor bugfixes (modules):
2263 - Explain what the optional Directory Authority module is, and what
2264 happens when it is disabled. Fixes bug 31825; bugfix
2267 o Minor bugfixes (multithreading):
2268 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2269 31736; bugfix on 0.0.7.
2271 o Minor bugfixes (relay):
2272 - Avoid crashing when starting with a corrupt keys directory where
2273 the old ntor key and the new ntor key are identical. Fixes bug
2274 30916; bugfix on 0.2.4.8-alpha.
2276 o Minor bugfixes (tests, SunOS):
2277 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2278 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2280 o Code simplification and refactoring:
2281 - Refactor connection_control_process_inbuf() to reduce the size of
2282 a practracker exception. Closes ticket 31840.
2283 - Refactor the microdescs_parse_from_string() function into smaller
2284 pieces, for better comprehensibility. Closes ticket 31675.
2285 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
2286 tests and fuzzers, rather than using hard-coded values. Closes
2288 - Interface for function `decrypt_desc_layer` cleaned up. Closes
2292 - Document the signal-safe logging behaviour in the tor man page.
2293 Also add some comments to the relevant functions. Closes
2295 - Explain why we can't destroy the backtrace buffer mutex. Explain
2296 why we don't need to destroy the log mutex. Closes ticket 31736.
2297 - The Tor source code repository now includes a (somewhat dated)
2298 description of Tor's modular architecture, in doc/HACKING/design.
2299 This is based on the old "tor-guts.git" repository, which we are
2300 adopting and superseding. Closes ticket 31849.
2303 Changes in version 0.4.1.6 - 2019-09-19
2304 This release backports several bugfixes to improve stability and
2305 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
2306 or experiencing reliability issues with single onion services, should
2309 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
2310 - Tolerate systems (including some Android installations) where
2311 madvise and MADV_DONTDUMP are available at build-time, but not at
2312 run time. Previously, these systems would notice a failed syscall
2313 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2314 - Tolerate systems (including some Linux installations) where
2315 madvise and/or MADV_DONTFORK are available at build-time, but not
2316 at run time. Previously, these systems would notice a failed
2317 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2319 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2320 - Change "make test-stem" so it only runs the stem tests that use
2321 tor. This change makes test-stem faster and more reliable. Closes
2324 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2325 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2326 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2328 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2329 - Add more stub functions to fix compilation on Android with link-
2330 time optimization when --disable-module-dirauth is used.
2331 Previously, these compilation settings would make the compiler
2332 look for functions that didn't exist. Fixes bug 31552; bugfix
2334 - Suppress spurious float-conversion warnings from GCC when calling
2335 floating-point classifier functions on FreeBSD. Fixes part of bug
2336 31687; bugfix on 0.3.1.5-alpha.
2338 o Minor bugfixes (controller protocol):
2339 - Fix the MAPADDRESS controller command to accept one or more
2340 arguments. Previously, it required two or more arguments, and ignored
2341 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2343 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2344 - When extracting an IPv6 address from a PF-based proxy, verify that
2345 we are actually configured to receive an IPv6 address, and log an
2346 internal error if not. Fixes part of bug 31687; bugfix
2349 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2350 - When tor is missing descriptors for some primary entry guards,
2351 make the log message less alarming. It's normal for descriptors to
2352 expire, as long as tor fetches new ones soon after. Fixes bug
2353 31657; bugfix on 0.3.3.1-alpha.
2355 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2356 - Change log level of message "Hash of session info was not as
2357 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2360 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2361 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2362 31463; bugfix on 0.3.5.4-alpha.
2364 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2365 - Always retry v2 single onion service intro and rend circuits with
2366 a 3-hop path. Previously, v2 single onion services used a 3-hop
2367 path when rendezvous circuits were retried after a remote or
2368 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2369 23818; bugfix on 0.2.9.3-alpha.
2371 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
2372 - Always retry v3 single onion service intro and rend circuits with
2373 a 3-hop path. Previously, v3 single onion services used a 3-hop
2374 path when rend circuits were retried after a remote or delayed
2375 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2376 bugfix on 0.3.2.1-alpha.
2377 - Make v3 single onion services fall back to a 3-hop intro, when all
2378 intro points are unreachable via a 1-hop path. Previously, v3
2379 single onion services failed when all intro nodes were unreachable
2380 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2382 o Documentation (backport from 0.4.2.1-alpha):
2383 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2384 notice.html so that operators no longer have to host it
2385 themselves. Closes ticket 31089.
2388 Changes in version 0.4.2.1-alpha - 2019-09-17
2389 This is the first alpha release in the 0.4.2.x series. It adds new
2390 defenses for denial-of-service attacks against onion services. It also
2391 includes numerous kinds of bugfixes and refactoring to help improve
2392 Tor's stability and ease of development.
2394 o Major features (onion service v3, denial of service):
2395 - Add onion service introduction denial of service defenses. Intro
2396 points can now rate-limit client introduction requests, using
2397 parameters that can be sent by the service within the
2398 ESTABLISH_INTRO cell. If the cell extension for this is not used,
2399 the intro point will honor the consensus parameters. Closes
2402 o Major bugfixes (circuit build, guard):
2403 - When considering upgrading circuits from "waiting for guard" to
2404 "open", always ignore circuits that are marked for close.
2405 Previously we could end up in the situation where a subsystem is
2406 notified of a circuit opening, but the circuit is still marked for
2407 close, leading to undesirable behavior. Fixes bug 30871; bugfix
2410 o Major bugfixes (crash, Linux, Android):
2411 - Tolerate systems (including some Android installations) where
2412 madvise and MADV_DONTDUMP are available at build-time, but not at
2413 run time. Previously, these systems would notice a failed syscall
2414 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2415 - Tolerate systems (including some Linux installations) where
2416 madvise and/or MADV_DONTFORK are available at build-time, but not
2417 at run time. Previously, these systems would notice a failed
2418 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2420 o Minor features (best practices tracker):
2421 - Our best-practices tracker now integrates with our include-checker
2422 tool to keep track of how many layering violations we have not yet
2423 fixed. We hope to reduce this number over time to improve Tor's
2424 modularity. Closes ticket 31176.
2425 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
2426 practracker from the environment. We may want this for continuous
2427 integration. Closes ticket 31309.
2428 - Give a warning rather than an error when a practracker exception
2429 is violated by a small amount, add a --list-overbroad option to
2430 practracker that lists exceptions that are stricter than they need
2431 to be, and provide an environment variable for disabling
2432 practracker. Closes ticket 30752.
2433 - Our best-practices tracker now looks at headers as well as C
2434 files. Closes ticket 31175.
2436 o Minor features (build system):
2437 - Add --disable-manpage and --disable-html-manual options to
2438 configure script. This will enable shortening build times by not
2439 building documentation. Resolves issue 19381.
2441 o Minor features (compilation):
2442 - Log a more useful error message when we are compiling and one of
2443 the compile-time hardening options we have selected can be linked
2444 but not executed. Closes ticket 27530.
2446 o Minor features (configuration):
2447 - The configuration code has been extended to allow splitting
2448 configuration data across multiple objects. Previously, all
2449 configuration data needed to be kept in a single object, which
2450 tended to become bloated. Closes ticket 31240.
2452 o Minor features (continuous integration):
2453 - When running CI builds on Travis, put some random data in
2454 ~/.torrc, to make sure no tests are reading the Tor configuration
2455 file from its default location. Resolves issue 30102.
2457 o Minor features (debugging):
2458 - Log a nonfatal assertion failure if we encounter a configuration
2459 line whose command is "CLEAR" but which has a nonempty value. This
2460 should be impossible, according to the rules of our configuration
2461 line parsing. Closes ticket 31529.
2463 o Minor features (git hooks):
2464 - Our pre-commit git hook now checks for a special file before
2465 running practracker, so that practracker only runs on branches
2466 that are based on master. Since the pre-push hook calls the pre-
2467 commit hook, practracker will also only run before pushes of
2468 branches based on master. Closes ticket 30979.
2470 o Minor features (git scripts):
2471 - Add a "--" command-line argument, to separate git-push-all.sh
2472 script arguments from arguments that are passed through to git
2473 push. Closes ticket 31314.
2474 - Add a -r <remote-name> argument to git-push-all.sh, so the script
2475 can push test branches to a personal remote. Closes ticket 31314.
2476 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
2477 git-push-all.sh, which makes these scripts create, merge forward,
2478 and push test branches. Closes ticket 31314.
2479 - Add a -u argument to git-merge-forward.sh, so that the script can
2480 re-use existing test branches after a merge failure and fix.
2481 Closes ticket 31314.
2482 - Add a TOR_GIT_PUSH env var, which sets the default git push
2483 command and arguments for git-push-all.sh. Closes ticket 31314.
2484 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
2485 script push master and maint branches with a delay between each
2486 branch. These delays trigger the CI jobs in a set order, which
2487 should show the most likely failures first. Also make pushes
2488 atomic by default, and make the script pass any command-line
2489 arguments to git push. Closes ticket 29879.
2490 - Call the shellcheck script from the pre-commit hook. Closes
2492 - Skip pushing test branches that are the same as a remote
2493 maint/release/master branch in git-push-all.sh by default. Add a
2494 -s argument, so git-push-all.sh can push all test branches. Closes
2497 o Minor features (IPv6, logging):
2498 - Log IPv6 addresses as well as IPv4 addresses when describing
2499 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
2501 o Minor features (onion service v3):
2502 - Do not allow single hop clients to fetch or post an HS descriptor
2503 from an HSDir. Closes ticket 24964.
2505 o Minor features (onion service):
2506 - Disallow single-hop clients at the introduction point. We've
2507 removed Tor2web support a while back and single-hop rendezvous
2508 attempts are blocked at the relays. This change should remove load
2509 off the network from spammy clients. Close ticket 24963.
2511 o Minor features (stem tests):
2512 - Change "make test-stem" so it only runs the stem tests that use
2513 tor. This change makes test-stem faster and more reliable. Closes
2516 o Minor features (testing):
2517 - Add a script to invoke "tor --dump-config" and "tor
2518 --verify-config" with various configuration options, and see
2519 whether tor's resulting configuration or error messages are what
2520 we expect. Use it for integration testing of our +Option and
2521 /Option flags. Closes ticket 31637.
2522 - Improve test coverage for our existing configuration parsing and
2523 management API. Closes ticket 30893.
2524 - Add integration tests to make sure that practracker gives the
2525 outputs we expect. Closes ticket 31477.
2526 - The practracker self-tests are now run as part of the Tor test
2527 suite. Closes ticket 31304.
2529 o Minor features (token bucket):
2530 - Implement a generic token bucket that uses a single counter, for
2531 use in anti-DoS onion service work. Closes ticket 30687.
2533 o Minor bugfixes (best practices tracker):
2534 - Fix a few issues in the best-practices script, including tests,
2535 tab tolerance, error reporting, and directory-exclusion logic.
2536 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
2537 - When running check-best-practices, only consider files in the src
2538 subdirectory. Previously we had recursively considered all
2539 subdirectories, which made us get confused by the temporary
2540 directories made by "make distcheck". Fixes bug 31578; bugfix
2543 o Minor bugfixes (build system):
2544 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2545 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2547 o Minor bugfixes (chutney, makefiles, documentation):
2548 - "make test-network-all" now shows the warnings from each test-
2549 network.sh run on the console, so developers see new warnings
2550 early. We've also improved the documentation for this feature, and
2551 renamed a Makefile variable so the code is self-documenting. Fixes
2552 bug 30455; bugfix on 0.3.0.4-rc.
2554 o Minor bugfixes (compilation):
2555 - Add more stub functions to fix compilation on Android with link-
2556 time optimization when --disable-module-dirauth is used.
2557 Previously, these compilation settings would make the compiler
2558 look for functions that didn't exist. Fixes bug 31552; bugfix
2560 - Suppress spurious float-conversion warnings from GCC when calling
2561 floating-point classifier functions on FreeBSD. Fixes part of bug
2562 31687; bugfix on 0.3.1.5-alpha.
2564 o Minor bugfixes (configuration):
2565 - Invalid floating-point values in the configuration file are now
2566 treated as errors in the configuration. Previously, they were
2567 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
2569 o Minor bugfixes (coverity):
2570 - Add an assertion when parsing a BEGIN cell so that coverity can be
2571 sure that we are not about to dereference a NULL address. Fixes
2572 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
2573 - In our siphash implementation, when building for coverity, use
2574 memcpy in place of a switch statement, so that coverity can tell
2575 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
2576 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
2577 - Fix several coverity warnings from our unit tests. Fixes bug
2578 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
2580 o Minor bugfixes (developer tooling):
2581 - Only log git script changes in the post-merge script when the
2582 merge was to the master branch. Fixes bug 31040; bugfix
2585 o Minor bugfixes (directory authorities):
2586 - Return a distinct status when formatting annotations fails. Fixes
2587 bug 30780; bugfix on 0.2.0.8-alpha.
2589 o Minor bugfixes (error handling):
2590 - On abort, try harder to flush the output buffers of log messages.
2591 On some platforms (macOS), log messages could be discarded when
2592 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2593 - Report the tor version whenever an assertion fails. Previously, we
2594 only reported the Tor version on some crashes, and some non-fatal
2595 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2596 - When tor aborts due to an error, close log file descriptors before
2597 aborting. Closing the logs makes some OSes flush log file buffers,
2598 rather than deleting buffered log lines. Fixes bug 31594; bugfix
2601 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
2602 - When extracting an IPv6 address from a PF-based proxy, verify that
2603 we are actually configured to receive an IPv6 address, and log an
2604 internal error if not. Fixes part of bug 31687; bugfix
2607 o Minor bugfixes (git hooks):
2608 - Remove a duplicate call to practracker from the pre-push hook. The
2609 pre-push hook already calls the pre-commit hook, which calls
2610 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
2612 o Minor bugfixes (git scripts):
2613 - Stop hard-coding the bash path in the git scripts. Some OSes don't
2614 have bash in /usr/bin, others have an ancient bash at this path.
2615 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
2616 - Stop hard-coding the tor master branch name and worktree path in
2617 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
2618 - Allow git-push-all.sh to be run from any directory. Previously,
2619 the script only worked if run from an upstream worktree directory.
2620 Closes ticket 31678.
2622 o Minor bugfixes (guards):
2623 - When tor is missing descriptors for some primary entry guards,
2624 make the log message less alarming. It's normal for descriptors to
2625 expire, as long as tor fetches new ones soon after. Fixes bug
2626 31657; bugfix on 0.3.3.1-alpha.
2628 o Minor bugfixes (ipv6):
2629 - Check for private IPv6 addresses alongside their IPv4 equivalents
2630 when authorities check descriptors. Previously, we only checked
2631 for private IPv4 addresses. Fixes bug 31088; bugfix on
2632 0.2.3.21-rc. Patch by Neel Chauhan.
2633 - When parsing microdescriptors, we should check the IPv6 exit
2634 policy alongside IPv4. Previously, we checked both exit policies
2635 for only router info structures, while microdescriptors were
2636 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
2639 o Minor bugfixes (logging):
2640 - Change log level of message "Hash of session info was not as
2641 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2643 - Fix a code issue that would have broken our parsing of log domains
2644 as soon as we had 33 of them. Fortunately, we still only have 29.
2645 Fixes bug 31451; bugfix on 0.4.1.4-rc.
2647 o Minor bugfixes (memory management):
2648 - Stop leaking a small amount of memory in nt_service_install(), in
2649 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
2652 o Minor bugfixes (networking, IP addresses):
2653 - When parsing addresses via Tor's internal DNS lookup API, reject
2654 IPv4 addresses in square brackets, and accept IPv6 addresses in
2655 square brackets. This change completes the work started in 23082,
2656 making address parsing consistent between tor's internal DNS
2657 lookup and address parsing APIs. Fixes bug 30721; bugfix
2659 - When parsing addresses via Tor's internal address:port parsing and
2660 DNS lookup APIs, require IPv6 addresses with ports to have square
2661 brackets. But allow IPv6 addresses without ports, whether or not
2662 they have square brackets. Fixes bug 30721; bugfix
2665 o Minor bugfixes (onion service v3):
2666 - When purging the client descriptor cache, close any introduction
2667 point circuits associated with purged cache entries. This avoids
2668 picking those circuits later when connecting to the same
2669 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
2671 o Minor bugfixes (onion services):
2672 - In the hs_ident_circuit_t data structure, remove the unused field
2673 circuit_type and the respective argument in hs_ident_circuit_new().
2674 This field was set by clients (for introduction) and services (for
2675 introduction and rendezvous) but was never used afterwards. Fixes
2676 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
2678 o Minor bugfixes (operator tools):
2679 - Make tor-print-ed-signing-cert(1) print certificate expiration
2680 date in RFC 1123 and UNIX timestamp formats, to make output
2681 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
2683 o Minor bugfixes (rust):
2684 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2685 31463; bugfix on 0.3.5.4-alpha.
2686 - Raise the minimum rustc version to 1.31.0, as checked by configure
2687 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
2689 o Minor bugfixes (sendme, code structure):
2690 - Rename the trunnel SENDME file definition from sendme.trunnel to
2691 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
2692 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
2694 o Minor bugfixes (statistics):
2695 - Stop removing the ed25519 signature if the extra info file is too
2696 big. If the signature data was removed, but the keyword was kept,
2697 this could result in an unparseable extra info file. Fixes bug
2698 30958; bugfix on 0.2.7.2-alpha.
2700 o Minor bugfixes (subsystems):
2701 - Make the subsystem init order match the subsystem module
2702 dependencies. Call windows process security APIs as early as
2703 possible. Initialize logging before network and time, so that
2704 network and time can use logging. Fixes bug 31615; bugfix
2707 o Minor bugfixes (testing):
2708 - Teach the util/socketpair_ersatz test to work correctly when we
2709 have no network stack configured. Fixes bug 30804; bugfix
2712 o Minor bugfixes (v2 single onion services):
2713 - Always retry v2 single onion service intro and rend circuits with
2714 a 3-hop path. Previously, v2 single onion services used a 3-hop
2715 path when rendezvous circuits were retried after a remote or
2716 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2717 23818; bugfix on 0.2.9.3-alpha.
2719 o Minor bugfixes (v3 single onion services):
2720 - Always retry v3 single onion service intro and rend circuits with
2721 a 3-hop path. Previously, v3 single onion services used a 3-hop
2722 path when rend circuits were retried after a remote or delayed
2723 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2724 bugfix on 0.3.2.1-alpha.
2725 - Make v3 single onion services fall back to a 3-hop intro, when all
2726 intro points are unreachable via a 1-hop path. Previously, v3
2727 single onion services failed when all intro nodes were unreachable
2728 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2731 - Improve documentation in circuit padding subsystem. Patch by
2732 Tobias Pulls. Closes ticket 31113.
2733 - Include an example usage for IPv6 ORPort in our sample torrc.
2734 Closes ticket 31320; patch from Ali Raheem.
2735 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2736 notice.html so that operators no longer have to host it
2737 themselves. Closes ticket 31089.
2740 - No longer include recommended package digests in votes as detailed
2741 in proposal 301. The RecommendedPackages torrc option is
2742 deprecated and will no longer have any effect. "package" lines
2743 will still be considered when computing consensuses for consensus
2744 methods that include them. (This change has no effect on the list
2745 of recommended Tor versions, which is still in use.) Closes
2747 - Remove torctl.in from contrib/dist directory. Resolves
2751 - Run shellcheck for all non-third-party shell scripts that are
2752 shipped with Tor. Closes ticket 29533.
2753 - When checking shell scripts, ignore any user-created directories.
2754 Closes ticket 30967.
2756 o Code simplification and refactoring (config handling):
2757 - Extract our variable manipulation code from confparse.c to a new
2758 lower-level typedvar.h module. Closes ticket 30864.
2759 - Lower another layer of object management from confparse.c to a
2760 more general tool. Now typed structure members are accessible via
2761 an abstract type. Implements ticket 30914.
2762 - Move our backend logic for working with configuration and state
2763 files into a lower-level library, since it no longer depends on
2764 any tor-specific functionality. Closes ticket 31626.
2765 - Numerous simplifications in configuration-handling logic: remove
2766 duplicated macro definitions, replace magical names with flags,
2767 and refactor "TestingTorNetwork" to use the same default-option
2768 logic as the rest of Tor. Closes ticket 30935.
2769 - Replace our ad-hoc set of flags for configuration variables and
2770 configuration variable types with fine-grained orthogonal flags
2771 corresponding to the actual behavior we want. Closes ticket 31625.
2773 o Code simplification and refactoring (misc):
2774 - Eliminate some uses of lower-level control reply abstractions,
2775 primarily in the onion_helper functions. Closes ticket 30889.
2776 - Rework bootstrap tracking to use the new publish-subscribe
2777 subsystem. Closes ticket 29976.
2778 - Rewrite format_node_description() and router_get_verbose_nickname()
2779 to use strlcpy() and strlcat(). The previous implementation used
2780 memcpy() and pointer arithmetic, which was error-prone. Closes
2781 ticket 31545. This is CID 1452819.
2782 - Split extrainfo_dump_to_string() into smaller functions. Closes
2784 - Use the ptrdiff_t type consistently for expressing variable
2785 offsets and pointer differences. Previously we incorrectly (but
2786 harmlessly) used int and sometimes off_t for these cases. Closes
2788 - Use the subsystems mechanism to manage the main event loop code.
2789 Closes ticket 30806.
2790 - Various simplifications and minor improvements to the circuit
2791 padding machines. Patch by Tobias Pulls. Closes tickets 31112
2794 o Documentation (hard-coded directories):
2795 - Improve the documentation for the DirAuthority and FallbackDir
2796 torrc options. Closes ticket 30955.
2798 o Documentation (tor.1 man page):
2799 - Fix typo in tor.1 man page: the option is "--help", not "-help".
2800 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
2803 Changes in version 0.4.1.5 - 2019-08-20
2804 This is the first stable release in the 0.4.1.x series. This series
2805 adds experimental circuit-level padding, authenticated SENDME cells to
2806 defend against certain attacks, and several performance improvements
2807 to save on CPU consumption. It fixes bugs in bootstrapping and v3
2808 onion services. It also includes numerous smaller features and
2809 bugfixes on earlier versions.
2811 Per our support policy, we will support the 0.4.1.x series for nine
2812 months, or until three months after the release of a stable 0.4.2.x:
2813 whichever is longer. If you need longer-term support, please stick
2814 with 0.3.5.x, which will we plan to support until Feb 2022.
2816 Below are the changes since 0.4.1.4-rc. For a complete list of changes
2817 since 0.4.0.5, see the ReleaseNotes file.
2819 o Directory authority changes:
2820 - The directory authority "dizum" has a new IP address. Closes
2823 o Minor features (circuit padding logging):
2824 - Demote noisy client-side warn logs about circuit padding to
2825 protocol warnings. Add additional log messages and circuit ID
2826 fields to help with bug 30992 and any other future issues.
2828 o Minor bugfixes (circuit padding negotiation):
2829 - Bump the circuit padding protocol version to explicitly signify
2830 that the HS setup machine support is finalized in 0.4.1.x-stable.
2831 This also means that 0.4.1.x-alpha clients will not negotiate
2832 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
2833 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
2834 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
2836 o Minor bugfixes (circuit padding):
2837 - Ignore non-padding cells on padding circuits. This addresses
2838 various warning messages from subsystems that were not expecting
2839 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
2841 o Minor bugfixes (clock skew detection):
2842 - Don't believe clock skew results from NETINFO cells that appear to
2843 arrive before we sent the VERSIONS cells they are responding to.
2844 Previously, we would accept them up to 3 minutes "in the past".
2845 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2847 o Minor bugfixes (compatibility, standards compliance):
2848 - Fix a bug that would invoke undefined behavior on certain
2849 operating systems when trying to asprintf() a string exactly
2850 INT_MAX bytes long. We don't believe this is exploitable, but it's
2851 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
2852 Found and fixed by Tobias Stoeckmann.
2854 o Minor bugfixes (compilation warning):
2855 - Fix a compilation warning on Windows about casting a function
2856 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2859 o Minor bugfixes (compilation):
2860 - Avoid using labs() on time_t, which can cause compilation warnings
2861 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2863 o Minor bugfixes (distribution):
2864 - Do not ship any temporary files found in the
2865 scripts/maint/practracker directory. Fixes bug 31311; bugfix
2868 o Testing (continuous integration):
2869 - In Travis, make stem log a controller trace to the console, and
2870 tail stem's tor log after failure. Closes ticket 30591.
2871 - In Travis, only run the stem tests that use a tor binary. Closes
2875 Changes in version 0.4.1.4-rc - 2019-07-25
2876 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
2877 updates to a new list of fallback directories. If no new bugs are
2878 found, the next release in the 0.4.1.x serious should be stable.
2880 o Major bugfixes (circuit build, guard):
2881 - When considering upgrading circuits from "waiting for guard" to
2882 "open", always ignore circuits that are marked for close. Otherwise,
2883 we can end up in the situation where a subsystem is notified that
2884 a closing circuit has just opened, leading to undesirable
2885 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2887 o Minor features (continuous integration):
2888 - Our Travis configuration now uses Chutney to run some network
2889 integration tests automatically. Closes ticket 29280.
2891 o Minor features (fallback directory list):
2892 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2893 in December 2018 (of which ~122 were still functional), with a
2894 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2895 in June 2019. Closes ticket 28795.
2897 o Minor bugfixes (circuit padding):
2898 - On relays, properly check that a padding machine is absent before
2899 logging a warning about it being absent. Fixes bug 30649; bugfix
2901 - Add two NULL checks in unreachable places to silence Coverity (CID
2902 144729 and 1447291) and better future-proof ourselves. Fixes bug
2903 31024; bugfix on 0.4.1.1-alpha.
2905 o Minor bugfixes (crash on exit):
2906 - Avoid a set of possible code paths that could try to use freed
2907 memory in routerlist_free() while Tor was exiting. Fixes bug
2908 31003; bugfix on 0.1.2.2-alpha.
2910 o Minor bugfixes (logging):
2911 - Fix a conflict between the flag used for messaging-domain log
2912 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
2915 o Minor bugfixes (memory leaks):
2916 - Fix a trivial memory leak when parsing an invalid value from a
2917 download schedule in the configuration. Fixes bug 30894; bugfix
2920 o Code simplification and refactoring:
2921 - Remove some dead code from circpad_machine_remove_token() to fix
2922 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
2926 Changes in version 0.4.1.3-alpha - 2019-06-25
2927 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
2928 alpha, most of them from earlier release series.
2930 o Major bugfixes (Onion service reachability):
2931 - Properly clean up the introduction point map when circuits change
2932 purpose from onion service circuits to pathbias, measurement, or
2933 other circuit types. This should fix some service-side instances
2934 of introduction point failure. Fixes bug 29034; bugfix
2937 o Minor features (geoip):
2938 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
2939 Country database. Closes ticket 30852.
2941 o Minor features (logging):
2942 - Give a more useful assertion failure message if we think we have
2943 minherit() but we fail to make a region non-inheritable. Give a
2944 compile-time warning if our support for minherit() is incomplete.
2945 Closes ticket 30686.
2947 o Minor bugfixes (circuit isolation):
2948 - Fix a logic error that prevented the SessionGroup sub-option from
2949 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2951 o Minor bugfixes (continuous integration):
2952 - Allow the test-stem job to fail in Travis, because it sometimes
2953 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
2954 - Skip test_rebind on macOS in Travis, because it is unreliable on
2955 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2956 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
2957 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2959 o Minor bugfixes (directory authorities):
2960 - Stop crashing after parsing an unknown descriptor purpose
2961 annotation. We think this bug can only be triggered by modifying a
2962 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
2964 o Minor bugfixes (pluggable transports):
2965 - When running as a bridge with pluggable transports, always publish
2966 pluggable transport information in our extrainfo descriptor, even
2967 if ExtraInfoStatistics is 0. This information is needed by
2968 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
2971 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
2972 Closes ticket 30630.
2975 Changes in version 0.4.1.2-alpha - 2019-06-06
2976 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
2977 previous alpha, and some much older. It also contains minor testing
2978 improvements, and an improvement to the security of our authenticated
2979 SENDME implementation.
2981 o Major bugfixes (bridges):
2982 - Consider our directory information to have changed when our list
2983 of bridges changes. Previously, Tor would not re-compute the
2984 status of its directory information when bridges changed, and
2985 therefore would not realize that it was no longer able to build
2986 circuits. Fixes part of bug 29875.
2987 - Do not count previously configured working bridges towards our
2988 total of working bridges. Previously, when Tor's list of bridges
2989 changed, it would think that the old bridges were still usable,
2990 and delay fetching router descriptors for the new ones. Fixes part
2991 of bug 29875; bugfix on 0.3.0.1-alpha.
2993 o Major bugfixes (flow control, SENDME):
2994 - Decrement the stream-level package window after packaging a cell.
2995 Previously, it was done inside a log_debug() call, meaning that if
2996 debug logs were not enabled, the decrement would never happen, and
2997 thus the window would be out of sync with the other end point.
2998 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
3000 o Major bugfixes (onion service reachability):
3001 - Properly clean up the introduction point map and associated state
3002 when circuits change purpose from onion service circuits to
3003 pathbias, measurement, or other circuit types. This may fix some
3004 instances of introduction point failure. Fixes bug 29034; bugfix
3007 o Minor features (authenticated SENDME):
3008 - Ensure that there is enough randomness on every circuit to prevent
3009 an attacker from successfully predicting the hashes they will need
3010 to include in authenticated SENDME cells. At a random interval, if
3011 we have not sent randomness already, we now leave some extra space
3012 at the end of a cell that we can fill with random bytes. Closes
3015 o Minor features (continuous integration):
3016 - When running coverage builds on Travis, we now set
3017 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
3020 o Minor features (maintenance):
3021 - Add a new "make autostyle" target that developers can use to apply
3022 all automatic Tor style and consistency conversions to the
3023 codebase. Closes ticket 30539.
3025 o Minor features (testing):
3026 - The circuitpadding tests now use a reproducible RNG implementation,
3027 so that if a test fails, we can learn why. Part of ticket 28878.
3028 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
3029 to set the RNG seed for tests that use a reproducible RNG. Part of
3031 - When running tests in coverage mode, take additional care to make
3032 our coverage deterministic, so that we can accurately track
3033 changes in code coverage. Closes ticket 30519.
3035 o Minor bugfixes (configuration, proxies):
3036 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3037 want authentication along with configured (but unused!)
3038 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3040 o Minor bugfixes (controller):
3041 - POSTDESCRIPTOR requests should work again. Previously, they were
3042 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
3044 - Repair the HSFETCH command so that it works again. Previously, it
3045 expected a body when it shouldn't have. Fixes bug 30646; bugfix
3048 o Minor bugfixes (developer tooling):
3049 - Fix pre-push hook to allow fixup and squash commits when pushing
3050 to non-upstream git remote. Fixes bug 30286; bugfix
3053 o Minor bugfixes (directory authority):
3054 - Move the "bandwidth-file-headers" line in directory authority
3055 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3058 o Minor bugfixes (NetBSD):
3059 - Fix usage of minherit() on NetBSD and other platforms that define
3060 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3061 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3063 o Minor bugfixes (out-of-memory handler):
3064 - When purging the DNS cache because of an out-of-memory condition,
3065 try purging just the older entries at first. Previously, we would
3066 always purge the whole thing. Fixes bug 29617; bugfix
3069 o Minor bugfixes (portability):
3070 - Avoid crashing in our tor_vasprintf() implementation on systems
3071 that define neither vasprintf() nor _vscprintf(). (This bug has
3072 been here long enough that we question whether people are running
3073 Tor on such systems, but we're applying the fix out of caution.)
3074 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3077 o Minor bugfixes (shutdown, libevent, memory safety):
3078 - Avoid use-after-free bugs when shutting down, by making sure that
3079 we shut down libevent only after shutting down all of its users.
3080 We believe these are harmless in practice, since they only occur
3081 on the shutdown path, and do not involve any attacker-controlled
3082 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
3084 o Minor bugfixes (static analysis):
3085 - Fix several spurious Coverity warnings about the unit tests, to
3086 lower our chances of missing real warnings in the future. Fixes
3087 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
3090 - Specify torrc paths (with empty files) when launching tor in
3091 integration tests; refrain from reading user and system torrcs.
3092 Resolves issue 29702.
3095 Changes in version 0.4.1.1-alpha - 2019-05-22
3096 This is the first alpha in the 0.4.1.x series. It introduces
3097 lightweight circuit padding to make some onion-service circuits harder
3098 to distinguish, includes a new "authenticated SENDME" feature to make
3099 certain denial-of-service attacks more difficult, and improves
3100 performance in several areas.
3102 o Major features (circuit padding):
3103 - Onion service clients now add padding cells at the start of their
3104 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
3105 look more like general purpose Exit traffic. The overhead for this
3106 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
3107 extra upstream cell and 10 downstream cells for INTRODUCE
3108 circuits. This feature is only enabled when also supported by the
3109 circuit's middle node. (Clients may specify fixed middle nodes
3110 with the MiddleNodes option, and may force-disable this feature
3111 with the CircuitPadding option.) Closes ticket 28634.
3113 o Major features (code organization):
3114 - Tor now includes a generic publish-subscribe message-passing
3115 subsystem that we can use to organize intermodule dependencies. We
3116 hope to use this to reduce dependencies between modules that don't
3117 need to be related, and to generally simplify our codebase. Closes
3120 o Major features (controller protocol):
3121 - Controller commands are now parsed using a generalized parsing
3122 subsystem. Previously, each controller command was responsible for
3123 parsing its own input, which led to strange inconsistencies.
3124 Closes ticket 30091.
3126 o Major features (flow control):
3127 - Implement authenticated SENDMEs as detailed in proposal 289. A
3128 SENDME cell now includes the digest of the traffic that it
3129 acknowledges, so that once an end point receives the SENDME, it
3130 can confirm the other side's knowledge of the previous cells that
3131 were sent, and prevent certain types of denial-of-service attacks.
3132 This behavior is controlled by two new consensus parameters: see
3133 the proposal for more details. Fixes ticket 26288.
3135 o Major features (performance):
3136 - Our node selection algorithm now excludes nodes in linear time.
3137 Previously, the algorithm was quadratic, which could slow down
3138 heavily used onion services. Closes ticket 30307.
3140 o Major features (performance, RNG):
3141 - Tor now constructs a fast secure pseudorandom number generator for
3142 each thread, to use when performance is critical. This PRNG is
3143 based on AES-CTR, using a buffering construction similar to
3144 libottery and the (newer) OpenBSD arc4random() code. It
3145 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
3146 small outputs. Although we believe it to be cryptographically
3147 strong, we are only using it when necessary for performance.
3148 Implements tickets 29023 and 29536.
3150 o Major bugfixes (onion service v3):
3151 - Fix an unreachable bug in which an introduction point could try to
3152 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3153 to encode, leading the relay to assert(). We've consolidated the
3154 ABI values into Trunnel now. Fixes bug 30454; bugfix
3156 - Clients can now handle unknown status codes from INTRODUCE_ACK
3157 cells. (The NACK behavior will stay the same.) This will allow us
3158 to extend status codes in the future without breaking the normal
3159 client behavior. Fixes another part of bug 30454; bugfix
3162 o Minor features (circuit padding):
3163 - We now use a fast PRNG when scheduling circuit padding. Part of
3165 - Allow the padding machine designer to pick the edges of their
3166 histogram instead of trying to compute them automatically using an
3167 exponential formula. Resolves some undefined behavior in the case
3168 of small histograms and allows greater flexibility on machine
3169 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
3170 - Allow circuit padding machines to hold a circuit open until they
3171 are done padding it. Closes ticket 28780.
3173 o Minor features (compile-time modules):
3174 - Add a "--list-modules" command to print a list of which compile-
3175 time modules are enabled. Closes ticket 30452.
3177 o Minor features (continuous integration):
3178 - Remove sudo configuration lines from .travis.yml as they are no
3179 longer needed with current Travis build environment. Resolves
3181 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3183 o Minor features (controller):
3184 - Add onion service version 3 support to the HSFETCH command.
3185 Previously, only version 2 onion services were supported. Closes
3186 ticket 25417. Patch by Neel Chauhan.
3188 o Minor features (debugging):
3189 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
3190 logging of additional information during assert failure. Now we
3191 can use format strings to include information for trouble
3192 shooting. Resolves ticket 29662.
3194 o Minor features (defense in depth):
3195 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
3196 case a bug causes them to be used later. Closes ticket 30176.
3197 Patch from Tobias Stoeckmann.
3198 - Tor now uses a cryptographically strong PRNG even for decisions
3199 that we do not believe are security-sensitive. Previously, for
3200 performance reasons, we had used a trivially predictable linear
3201 congruential generator algorithm for certain load-balancing and
3202 statistical sampling decisions. Now we use our fast RNG in those
3203 cases. Closes ticket 29542.
3205 o Minor features (developer tools):
3206 - Tor's "practracker" test script now checks for files and functions
3207 that seem too long and complicated. Existing overlong functions
3208 and files are accepted for now, but should eventually be
3209 refactored. Closes ticket 29221.
3210 - Add some scripts used for git maintenance to scripts/git. Closes
3212 - Call practracker from pre-push and pre-commit git hooks to let
3213 developers know if they made any code style violations. Closes
3215 - Add a script to check that each header has a well-formed and
3216 unique guard macro. Closes ticket 29756.
3218 o Minor features (geoip):
3219 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
3220 Country database. Closes ticket 30522.
3222 o Minor features (HTTP tunnel):
3223 - Return an informative web page when the HTTPTunnelPort is used as
3224 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
3226 o Minor features (IPv6, v3 onion services):
3227 - Make v3 onion services put IPv6 addresses in service descriptors.
3228 Before this change, service descriptors only contained IPv4
3229 addresses. Implements 26992.
3231 o Minor features (modularity):
3232 - The "--disable-module-dirauth" compile-time option now disables
3233 even more dirauth-only code. Closes ticket 30345.
3235 o Minor features (performance):
3236 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
3237 1.1.1 and later), since they tend to be faster than tiny-keccak.
3238 Closes ticket 28837.
3240 o Minor features (testing):
3241 - Tor's unit test code now contains helper functions to replace the
3242 PRNG with a deterministic or reproducible version for testing.
3243 Previously, various tests implemented this in various ways.
3244 Implements ticket 29732.
3245 - We now have a script, cov-test-determinism.sh, to identify places
3246 where our unit test coverage has become nondeterministic. Closes
3248 - Check that representative subsets of values of `int` and `unsigned
3249 int` can be represented by `void *`. Resolves issue 29537.
3251 o Minor bugfixes (bridge authority):
3252 - Bridge authorities now set bridges as running or non-running when
3253 about to dump their status to a file. Previously, they set bridges
3254 as running in response to a GETINFO command, but those shouldn't
3255 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
3256 Patch by Neel Chauhan.
3258 o Minor bugfixes (channel padding statistics):
3259 - Channel padding write totals and padding-enabled totals are now
3260 counted properly in relay extrainfo descriptors. Fixes bug 29231;
3261 bugfix on 0.3.1.1-alpha.
3263 o Minor bugfixes (circuit padding):
3264 - Add a "CircuitPadding" torrc option to disable circuit padding.
3265 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
3266 - Allow circuit padding machines to specify that they do not
3267 contribute much overhead, and provide consensus flags and torrc
3268 options to force clients to only use these low overhead machines.
3269 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
3270 - Provide a consensus parameter to fully disable circuit padding, to
3271 be used in emergency network overload situations. Fixes bug 30173;
3272 bugfix on 0.4.0.1-alpha.
3273 - The circuit padding subsystem will no longer schedule padding if
3274 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
3275 - Inspect a circuit-level cell queue before sending padding, to
3276 avoid sending padding while too much data is already queued. Fixes
3277 bug 29204; bugfix on 0.4.0.1-alpha.
3278 - Avoid calling monotime_absolute_usec() in circuit padding machines
3279 that do not use token removal or circuit RTT estimation. Fixes bug
3280 29085; bugfix on 0.4.0.1-alpha.
3282 o Minor bugfixes (compilation, unusual configurations):
3283 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3284 due to missing declarations of abort(), and prevent other such
3285 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3287 o Minor bugfixes (controller protocol):
3288 - Teach the controller parser to distinguish an object preceded by
3289 an argument list from one without. Previously, it couldn't
3290 distinguish an argument list from the first line of a multiline
3291 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
3293 o Minor bugfixes (directory authority, ipv6):
3294 - Directory authorities with IPv6 support now always mark themselves
3295 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
3296 Patch by Neel Chauhan.
3298 o Minor bugfixes (documentation):
3299 - Improve the documentation for using MapAddress with ".exit". Fixes
3300 bug 30109; bugfix on 0.1.0.1-rc.
3301 - Improve the monotonic time module and function documentation to
3302 explain what "monotonic" actually means, and document some results
3303 that have surprised people. Fixes bug 29640; bugfix
3305 - Use proper formatting when providing an example on quoting options
3306 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
3308 o Minor bugfixes (logging):
3309 - Do not log a warning when running with an OpenSSL version other
3310 than the one Tor was compiled with, if the two versions should be
3311 compatible. Previously, we would warn whenever the version was
3312 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3313 - Warn operators when the MyFamily option is set but ContactInfo is
3314 missing, as the latter should be set too. Fixes bug 25110; bugfix
3317 o Minor bugfixes (memory leak):
3318 - Avoid a minor memory leak that could occur on relays when failing
3319 to create a "keys" directory. Fixes bug 30148; bugfix
3322 o Minor bugfixes (onion services):
3323 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3324 implemenation) when failing to load an onion service client
3325 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3326 - When refusing to launch a controller's HSFETCH request because of
3327 rate-limiting, respond to the controller with a new response,
3328 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
3329 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
3331 - When relaunching a circuit to a rendezvous service, mark the
3332 circuit as needing high-uptime routers as appropriate. Fixes bug
3333 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
3334 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
3335 (IPv6 support for v3 onion services is still incomplete: see
3336 ticket 23493 for details.) Fixes bug 23588; bugfix on
3337 0.3.2.1-alpha. Patch by Neel Chauhan.
3339 o Minor bugfixes (onion services, performance):
3340 - When building circuits to onion services, call tor_addr_parse()
3341 less often. Previously, we called tor_addr_parse() in
3342 circuit_is_acceptable() even if its output wasn't used. This
3343 change should improve performance when building circuits. Fixes
3344 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
3346 o Minor bugfixes (performance):
3347 - When checking whether a node is a bridge, use a fast check to make
3348 sure that its identity is set. Previously, we used a constant-time
3349 check, which is not necessary in this case. Fixes bug 30308;
3350 bugfix on 0.3.5.1-alpha.
3352 o Minor bugfixes (pluggable transports):
3353 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
3354 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
3356 o Minor bugfixes (probability distributions):
3357 - Refactor and improve parts of the probability distribution code
3358 that made Coverity complain. Fixes bug 29805; bugfix
3361 o Minor bugfixes (python):
3362 - Stop assuming that /usr/bin/python3 exists. For scripts that work
3363 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
3364 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
3366 o Minor bugfixes (relay):
3367 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
3368 is auto, act as if ExitRelay is 1. Previously, we would ignore
3369 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
3370 0.3.5.1-alpha. Patch by Neel Chauhan.
3372 o Minor bugfixes (stats):
3373 - When ExtraInfoStatistics is 0, stop including bandwidth usage
3374 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
3375 bridge statistics by country in extra-info documents. Fixes bug
3376 29018; bugfix on 0.2.4.1-alpha.
3378 o Minor bugfixes (testing):
3379 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
3380 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
3381 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
3382 - Fix some incorrect code in the v3 onion service unit tests. Fixes
3383 bug 29243; bugfix on 0.3.2.1-alpha.
3384 - In the "routerkeys/*" tests, check the return values of mkdir()
3385 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
3386 Found by Coverity as CID 1444254.
3387 - Split test_utils_general() into several smaller test functions.
3388 This makes it easier to perform resource deallocation on assert
3389 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
3390 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
3392 o Minor bugfixes (tor-resolve):
3393 - Fix a memory leak in tor-resolve that could happen if Tor gave it
3394 a malformed SOCKS response. (Memory leaks in tor-resolve don't
3395 actually matter, but it's good to fix them anyway.) Fixes bug
3396 30151; bugfix on 0.4.0.1-alpha.
3398 o Code simplification and refactoring:
3399 - Abstract out the low-level formatting of replies on the control
3400 port. Implements ticket 30007.
3401 - Add several assertions in an attempt to fix some Coverity
3402 warnings. Closes ticket 30149.
3403 - Introduce a connection_dir_buf_add() helper function that checks
3404 for compress_state of dir_connection_t and automatically writes a
3405 string to directory connection with or without compression.
3406 Resolves issue 28816.
3407 - Make the base32_decode() API return the number of bytes written,
3408 for consistency with base64_decode(). Closes ticket 28913.
3409 - Move most relay-only periodic events out of mainloop.c into the
3410 relay subsystem. Closes ticket 30414.
3411 - Refactor and encapsulate parts of the codebase that manipulate
3412 crypt_path_t objects. Resolves issue 30236.
3413 - Refactor several places in our code that Coverity incorrectly
3414 believed might have memory leaks. Closes ticket 30147.
3415 - Remove redundant return values in crypto_format, and the
3416 associated return value checks elsewhere in the code. Make the
3417 implementations in crypto_format consistent, and remove redundant
3418 code. Resolves ticket 29660.
3419 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
3420 it is not a constant-time function. Closes ticket 30309.
3421 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
3422 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
3423 bugfix on 0.3.2.1-alpha.
3424 - Simplify v3 onion service link specifier handling code. Fixes bug
3425 23576; bugfix on 0.3.2.1-alpha.
3426 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
3427 code. Resolves ticket 29108.
3428 - Split control.c into several submodules, in preparation for
3429 distributing its current responsibilities throughout the codebase.
3430 Closes ticket 29894.
3431 - Start to move responsibility for knowing about periodic events to
3432 the appropriate subsystems, so that the mainloop doesn't need to
3433 know all the periodic events in the rest of the codebase.
3434 Implements tickets 30293 and 30294.
3437 - Document how to find git commits and tags for bug fixes in
3438 CodingStandards.md. Update some file documentation. Closes
3442 - Remove the linux-tor-prio.sh script from contrib/operator-tools
3443 directory. Resolves issue 29434.
3444 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
3445 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
3448 o Code simplification and refactoring (shell scripts):
3449 - Clean up many of our shell scripts to fix shellcheck warnings.
3450 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
3451 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
3452 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
3453 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
3454 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
3455 nagios-check-tor-authority-cert (ticket 29071),
3456 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
3457 (ticket 29060), test_key_expiration.sh (ticket 30002),
3458 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
3461 o Testing (chutney):
3462 - In "make test-network-all", test IPv6-only v3 single onion
3463 services, using the chutney network single-onion-v23-ipv6-md.
3464 Closes ticket 27251.
3467 Changes in version 0.4.0.5 - 2019-05-02
3468 This is the first stable release in the 0.4.0.x series. It contains
3469 improvements for power management and bootstrap reporting, as well as
3470 preliminary backend support for circuit padding to prevent some kinds
3471 of traffic analysis. It also continues our work in refactoring Tor for
3472 long-term maintainability.
3474 Per our support policy, we will support the 0.4.0.x series for nine
3475 months, or until three months after the release of a stable 0.4.1.x:
3476 whichever is longer. If you need longer-term support, please stick
3477 with 0.3.5.x, which will we plan to support until Feb 2022.
3479 Below are the changes since 0.4.0.4-rc. For a complete list of changes
3480 since 0.3.5.7, see the ReleaseNotes file.
3482 o Minor features (continuous integration):
3483 - In Travis, tell timelimit to use stem's backtrace signals, and
3484 launch python directly from timelimit, so python receives the
3485 signals from timelimit, rather than make. Closes ticket 30117.
3487 o Minor features (diagnostic):
3488 - Add more diagnostic log messages in an attempt to solve the issue
3489 of NUL bytes appearing in a microdescriptor cache. Related to
3492 o Minor features (testing):
3493 - Use the approx_time() function when setting the "Expires" header
3494 in directory replies, to make them more testable. Needed for
3497 o Minor bugfixes (rust):
3498 - Abort on panic in all build profiles, instead of potentially
3499 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
3501 o Minor bugfixes (shellcheck):
3502 - Look for scripts in their correct locations during "make
3503 shellcheck". Previously we had looked in the wrong place during
3504 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
3506 o Minor bugfixes (testing):
3507 - Check the time in the "Expires" header using approx_time(). Fixes
3508 bug 30001; bugfix on 0.4.0.4-rc.
3510 o Minor bugfixes (UI):
3511 - Lower log level of unlink() errors during bootstrap. Fixes bug
3512 29930; bugfix on 0.4.0.1-alpha.
3515 Changes in version 0.4.0.4-rc - 2019-04-11
3516 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
3517 several bugs from earlier versions, including some that had affected
3518 stability, and one that prevented relays from working with NSS.
3520 o Major bugfixes (NSS, relay):
3521 - When running with NSS, disable TLS 1.2 ciphersuites that use
3522 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3523 these ciphersuites don't work -- which caused relays to fail to
3524 handshake with one another when these ciphersuites were enabled.
3525 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3527 o Minor features (bandwidth authority):
3528 - Make bandwidth authorities ignore relays that are reported in the
3529 bandwidth file with the flag "vote=0". This change allows us to
3530 report unmeasured relays for diagnostic reasons without including
3531 their bandwidth in the bandwidth authorities' vote. Closes
3533 - When a directory authority is using a bandwidth file to obtain the
3534 bandwidth values that will be included in the next vote, serve
3535 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
3538 o Minor features (circuit padding):
3539 - Stop warning about undefined behavior in the probability
3540 distribution tests. Float division by zero may technically be
3541 undefined behavior in C, but it's well defined in IEEE 754.
3542 Partial backport of 29298. Closes ticket 29527; bugfix
3545 o Minor features (continuous integration):
3546 - On Travis Rust builds, cleanup Rust registry and refrain from
3547 caching the "target/" directory to speed up builds. Resolves
3550 o Minor features (dormant mode):
3551 - Add a DormantCanceledByStartup option to tell Tor that it should
3552 treat a startup event as cancelling any previous dormant state.
3553 Integrators should use this option with caution: it should only be
3554 used if Tor is being started because of something that the user
3555 did, and not if Tor is being automatically started in the
3556 background. Closes ticket 29357.
3558 o Minor features (geoip):
3559 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
3560 Country database. Closes ticket 29992.
3562 o Minor features (NSS, diagnostic):
3563 - Try to log an error from NSS (if there is any) and a more useful
3564 description of our situation if we are using NSS and a call to
3565 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
3567 o Minor bugfixes (security):
3568 - Fix a potential double free bug when reading huge bandwidth files.
3569 The issue is not exploitable in the current Tor network because
3570 the vulnerable code is only reached when directory authorities
3571 read bandwidth files, but bandwidth files come from a trusted
3572 source (usually the authorities themselves). Furthermore, the
3573 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
3574 which are not used by any of the current authorities. Fixes bug
3575 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
3577 - Verify in more places that we are not about to create a buffer
3578 with more than INT_MAX bytes, to avoid possible OOB access in the
3579 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
3580 fixed by Tobias Stoeckmann.
3582 o Minor bugfix (continuous integration):
3583 - Reset coverage state on disk after Travis CI has finished. This
3584 should prevent future coverage merge errors from causing the test
3585 suite for the "process" subsystem to fail. The process subsystem
3586 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
3588 - Terminate test-stem if it takes more than 9.5 minutes to run.
3589 (Travis terminates the job after 10 minutes of no output.)
3590 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
3592 o Minor bugfixes (bootstrap reporting):
3593 - During bootstrap reporting, correctly distinguish pluggable
3594 transports from plain proxies. Fixes bug 28925; bugfix
3597 o Minor bugfixes (C correctness):
3598 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
3599 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
3602 o Minor bugfixes (circuitpadding testing):
3603 - Minor tweaks to avoid rare test failures related to timers and
3604 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
3606 o Minor bugfixes (directory authorities):
3607 - Actually include the bandwidth-file-digest line in directory
3608 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
3610 o Minor bugfixes (logging):
3611 - On Windows, when errors cause us to reload a consensus from disk,
3612 tell the user that we are retrying at log level "notice".
3613 Previously we only logged this information at "info", which was
3614 confusing because the errors themselves were logged at "warning".
3615 Improves previous fix for 28614. Fixes bug 30004; bugfix
3618 o Minor bugfixes (pluggable transports):
3619 - Restore old behavior when it comes to discovering the path of a
3620 given Pluggable Transport executable file. A change in
3621 0.4.0.1-alpha had broken this behavior on paths containing a
3622 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
3624 o Minor bugfixes (testing):
3625 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
3626 recent test-network.sh to use new chutney features in CI. Fixes
3627 bug 29703; bugfix on 0.2.9.1-alpha.
3628 - Fix a test failure on Windows caused by an unexpected "BUG"
3629 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
3632 o Minor bugfixes (TLS protocol):
3633 - When classifying a client's selection of TLS ciphers, if the
3634 client ciphers are not yet available, do not cache the result.
3635 Previously, we had cached the unavailability of the cipher list
3636 and never looked again, which in turn led us to assume that the
3637 client only supported the ancient V1 link protocol. This, in turn,
3638 was causing Stem integration tests to stall in some cases. Fixes
3639 bug 30021; bugfix on 0.2.4.8-alpha.
3641 o Code simplification and refactoring:
3642 - Introduce a connection_dir_buf_add() helper function that detects
3643 whether compression is in use, and adds a string accordingly.
3644 Resolves issue 28816.
3645 - Refactor handle_get_next_bandwidth() to use
3646 connection_dir_buf_add(). Implements ticket 29897.
3649 - Clarify that Tor performs stream isolation among *Port listeners
3650 by default. Resolves issue 29121.
3653 Changes in version 0.4.0.3-alpha - 2019-03-22
3654 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
3655 bugs from earlier versions.
3657 o Minor features (address selection):
3658 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3659 private for others. This subnet is the RFC 6598 (Carrier Grade
3660 NAT) IP range, and is deployed by many ISPs as an alternative to
3661 RFC 1918 that does not break existing internal networks. Tor now
3662 blocks SOCKS and control ports on these addresses and warns users
3663 if client ports or ExtORPorts are listening on a RFC 6598 address.
3664 Closes ticket 28525. Patch by Neel Chauhan.
3666 o Minor features (geoip):
3667 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
3668 Country database. Closes ticket 29666.
3670 o Minor bugfixes (circuitpadding):
3671 - Inspect the circuit-level cell queue before sending padding, to
3672 avoid sending padding when too much data is queued. Fixes bug
3673 29204; bugfix on 0.4.0.1-alpha.
3675 o Minor bugfixes (logging):
3676 - Correct a misleading error message when IPv4Only or IPv6Only is
3677 used but the resolved address can not be interpreted as an address
3678 of the specified IP version. Fixes bug 13221; bugfix on
3679 0.2.3.9-alpha. Patch from Kris Katterjohn.
3680 - Log the correct port number for listening sockets when "auto" is
3681 used to let Tor pick the port number. Previously, port 0 was
3682 logged instead of the actual port number. Fixes bug 29144; bugfix
3683 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3684 - Stop logging a BUG() warning when Tor is waiting for exit
3685 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3687 o Minor bugfixes (memory management):
3688 - Refactor the shared random state's memory management so that it
3689 actually takes ownership of the shared random value pointers.
3690 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
3692 o Minor bugfixes (memory management, testing):
3693 - Stop leaking parts of the shared random state in the shared-random
3694 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
3696 o Minor bugfixes (pluggable transports):
3697 - Fix an assertion failure crash bug when a pluggable transport is
3698 terminated during the bootstrap phase. Fixes bug 29562; bugfix
3701 o Minor bugfixes (Rust, protover):
3702 - Add a missing "Padding" value to the Rust implementation of
3703 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
3705 o Minor bugfixes (single onion services):
3706 - Allow connections to single onion services to remain idle without
3707 being disconnected. Previously, relays acting as rendezvous points
3708 for single onion services were mistakenly closing idle rendezvous
3709 circuits after 60 seconds, thinking that they were unused
3710 directory-fetching circuits that had served their purpose. Fixes
3711 bug 29665; bugfix on 0.2.1.26.
3713 o Minor bugfixes (stats):
3714 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
3715 relay and bridge extra-info documents. Fixes bug 29017; bugfix
3718 o Minor bugfixes (testing):
3719 - Downgrade some LOG_ERR messages in the address/* tests to
3720 warnings. The LOG_ERR messages were occurring when we had no
3721 configured network. We were failing the unit tests, because we
3722 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
3723 29530; bugfix on 0.3.5.8.
3724 - Fix our gcov wrapper script to look for object files at the
3725 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
3726 - Decrease the false positive rate of stochastic probability
3727 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
3729 o Minor bugfixes (Windows, CI):
3730 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
3731 Windows Server 2012 R2 job. The remaining 2 jobs still provide
3732 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
3733 fast_finish, so failed jobs terminate the build immediately. Fixes
3734 bug 29601; bugfix on 0.3.5.4-alpha.
3737 Changes in version 0.3.5.8 - 2019-02-21
3738 Tor 0.3.5.8 backports several fixes from later releases, including fixes
3739 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
3742 It also includes a fix for a medium-severity security bug affecting Tor
3743 0.3.2.1-alpha and later. All Tor instances running an affected release
3744 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3746 o Major bugfixes (cell scheduler, KIST, security):
3747 - Make KIST consider the outbuf length when computing what it can
3748 put in the outbuf. Previously, KIST acted as though the outbuf
3749 were empty, which could lead to the outbuf becoming too full. It
3750 is possible that an attacker could exploit this bug to cause a Tor
3751 client or relay to run out of memory and crash. Fixes bug 29168;
3752 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3753 TROVE-2019-001 and CVE-2019-8955.
3755 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
3756 - Gracefully handle empty username/password fields in SOCKS5
3757 username/password auth message and allow SOCKS5 handshake to
3758 continue. Previously, we had rejected these handshakes, breaking
3759 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3761 o Minor features (compilation, backport from 0.4.0.2-alpha):
3762 - Compile correctly when OpenSSL is built with engine support
3763 disabled, or with deprecated APIs disabled. Closes ticket 29026.
3764 Patches from "Mangix".
3766 o Minor features (geoip):
3767 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3768 Country database. Closes ticket 29478.
3770 o Minor features (testing, backport from 0.4.0.2-alpha):
3771 - Treat all unexpected ERR and BUG messages as test failures. Closes
3774 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
3775 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
3776 connection waiting for a descriptor that we actually have in the
3777 cache. It turns out that this can actually happen, though it is
3778 rare. Now, tor will recover and retry the descriptor. Fixes bug
3779 28669; bugfix on 0.3.2.4-alpha.
3781 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
3782 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
3783 IPv6 socket was bound using an address family of AF_INET instead
3784 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
3787 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3788 - Update Cargo.lock file to match the version made by the latest
3789 version of Rust, so that "make distcheck" will pass again. Fixes
3790 bug 29244; bugfix on 0.3.3.4-alpha.
3792 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
3793 - Select guards even if the consensus has expired, as long as the
3794 consensus is still reasonably live. Fixes bug 24661; bugfix
3797 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
3798 - Compile correctly on OpenBSD; previously, we were missing some
3799 headers required in order to detect it properly. Fixes bug 28938;
3800 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3802 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
3803 - Describe the contents of the v3 onion service client authorization
3804 files correctly: They hold public keys, not private keys. Fixes
3805 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3807 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
3808 - Rework rep_hist_log_link_protocol_counts() to iterate through all
3809 link protocol versions when logging incoming/outgoing connection
3810 counts. Tor no longer skips version 5, and we won't have to
3811 remember to update this function when new link protocol version is
3812 developed. Fixes bug 28920; bugfix on 0.2.6.10.
3814 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
3815 - Log more information at "warning" level when unable to read a
3816 private key; log more information at "info" level when unable to
3817 read a public key. We had warnings here before, but they were lost
3818 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
3820 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
3821 - The amount of total available physical memory is now determined
3822 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
3823 when it is defined and a 64-bit variant is not available. Fixes
3824 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
3826 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3827 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
3828 than one private key for a hidden service. Fixes bug 29040; bugfix
3830 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
3831 "debug" level. Tor used to log it as a warning, which caused very
3832 long log lines to appear for some users. Fixes bug 29135; bugfix
3834 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3835 as a warning. Instead, log it as a protocol warning, because there
3836 is nothing that relay operators can do to fix it. Fixes bug 29029;
3837 bugfix on 0.2.5.7-rc.
3839 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
3840 - Mark outdated dirservers when Tor only has a reasonably live
3841 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
3843 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
3844 - Detect and suppress "bug" warnings from the util/time test on
3845 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
3846 - Do not log an error-level message if we fail to find an IPv6
3847 network interface from the unit tests. Fixes bug 29160; bugfix
3850 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
3851 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
3852 Some users took this phrasing to mean that the mentioned guard was
3853 under their control or responsibility, which it is not. Fixes bug
3854 28895; bugfix on Tor 0.3.0.1-alpha.
3857 Changes in version 0.3.4.11 - 2019-02-21
3858 Tor 0.3.4.11 is the third stable release in its series. It includes
3859 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
3860 later. All Tor instances running an affected release should upgrade to
3861 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3863 o Major bugfixes (cell scheduler, KIST, security):
3864 - Make KIST consider the outbuf length when computing what it can
3865 put in the outbuf. Previously, KIST acted as though the outbuf
3866 were empty, which could lead to the outbuf becoming too full. It
3867 is possible that an attacker could exploit this bug to cause a Tor
3868 client or relay to run out of memory and crash. Fixes bug 29168;
3869 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3870 TROVE-2019-001 and CVE-2019-8955.
3872 o Minor features (geoip):
3873 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3874 Country database. Closes ticket 29478.
3876 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3877 - Update Cargo.lock file to match the version made by the latest
3878 version of Rust, so that "make distcheck" will pass again. Fixes
3879 bug 29244; bugfix on 0.3.3.4-alpha.
3881 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3882 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3883 as a warning. Instead, log it as a protocol warning, because there
3884 is nothing that relay operators can do to fix it. Fixes bug 29029;
3885 bugfix on 0.2.5.7-rc.
3888 Changes in version 0.3.3.12 - 2019-02-21
3889 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
3890 0.3.2.1-alpha and later. All Tor instances running an affected release
3891 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3893 This release marks the end of support for the Tor 0.3.3.x series. We
3894 recommend that users switch to either the Tor 0.3.4 series (supported
3895 until at least 10 June 2019), or the Tor 0.3.5 series, which will
3896 receive long-term support until at least 1 Feb 2022.
3898 o Major bugfixes (cell scheduler, KIST, security):
3899 - Make KIST consider the outbuf length when computing what it can
3900 put in the outbuf. Previously, KIST acted as though the outbuf
3901 were empty, which could lead to the outbuf becoming too full. It
3902 is possible that an attacker could exploit this bug to cause a Tor
3903 client or relay to run out of memory and crash. Fixes bug 29168;
3904 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3905 TROVE-2019-001 and CVE-2019-8955.
3907 o Minor features (geoip):
3908 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3909 Country database. Closes ticket 29478.
3911 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3912 - Update Cargo.lock file to match the version made by the latest
3913 version of Rust, so that "make distcheck" will pass again. Fixes
3914 bug 29244; bugfix on 0.3.3.4-alpha.
3916 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3917 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3918 as a warning. Instead, log it as a protocol warning, because there
3919 is nothing that relay operators can do to fix it. Fixes bug 29029;
3920 bugfix on 0.2.5.7-rc.
3923 Changes in version 0.4.0.2-alpha - 2019-02-21
3924 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
3925 bugs from earlier versions, including several that had broken
3926 backward compatibility.
3928 It also includes a fix for a medium-severity security bug affecting Tor
3929 0.3.2.1-alpha and later. All Tor instances running an affected release
3930 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3932 o Major bugfixes (cell scheduler, KIST, security):
3933 - Make KIST consider the outbuf length when computing what it can
3934 put in the outbuf. Previously, KIST acted as though the outbuf
3935 were empty, which could lead to the outbuf becoming too full. It
3936 is possible that an attacker could exploit this bug to cause a Tor
3937 client or relay to run out of memory and crash. Fixes bug 29168;
3938 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3939 TROVE-2019-001 and CVE-2019-8955.
3941 o Major bugfixes (networking):
3942 - Gracefully handle empty username/password fields in SOCKS5
3943 username/password auth messsage and allow SOCKS5 handshake to
3944 continue. Previously, we had rejected these handshakes, breaking
3945 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3947 o Major bugfixes (windows, startup):
3948 - When reading a consensus file from disk, detect whether it was
3949 written in text mode, and re-read it in text mode if so. Always
3950 write consensus files in binary mode so that we can map them into
3951 memory later. Previously, we had written in text mode, which
3952 confused us when we tried to map the file on windows. Fixes bug
3953 28614; bugfix on 0.4.0.1-alpha.
3955 o Minor features (compilation):
3956 - Compile correctly when OpenSSL is built with engine support
3957 disabled, or with deprecated APIs disabled. Closes ticket 29026.
3958 Patches from "Mangix".
3960 o Minor features (developer tooling):
3961 - Check that bugfix versions in changes files look like Tor versions
3962 from the versions spec. Warn when bugfixes claim to be on a future
3963 release. Closes ticket 27761.
3964 - Provide a git pre-commit hook that disallows committing if we have
3965 any failures in our code and changelog formatting checks. It is
3966 now available in scripts/maint/pre-commit.git-hook. Implements
3969 o Minor features (directory authority):
3970 - When a directory authority is using a bandwidth file to obtain
3971 bandwidth values, include the digest of that file in the vote.
3972 Closes ticket 26698.
3974 o Minor features (geoip):
3975 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3976 Country database. Closes ticket 29478.
3978 o Minor features (testing):
3979 - Treat all unexpected ERR and BUG messages as test failures. Closes
3982 o Minor bugfixes (build, compatibility, rust):
3983 - Update Cargo.lock file to match the version made by the latest
3984 version of Rust, so that "make distcheck" will pass again. Fixes
3985 bug 29244; bugfix on 0.3.3.4-alpha.
3987 o Minor bugfixes (compilation):
3988 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
3989 29169; bugfix on 0.4.0.1-alpha.
3990 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
3991 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3993 o Minor bugfixes (documentation):
3994 - Describe the contents of the v3 onion service client authorization
3995 files correctly: They hold public keys, not private keys. Fixes
3996 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3998 o Minor bugfixes (linux seccomp sandbox):
3999 - Fix startup crash when experimental sandbox support is enabled.
4000 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
4002 o Minor bugfixes (logging):
4003 - Avoid logging that we are relaxing a circuit timeout when that
4004 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
4005 - Log more information at "warning" level when unable to read a
4006 private key; log more information at "info" level when unable to
4007 read a public key. We had warnings here before, but they were lost
4008 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4010 o Minor bugfixes (misc):
4011 - The amount of total available physical memory is now determined
4012 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4013 when it is defined and a 64-bit variant is not available. Fixes
4014 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4016 o Minor bugfixes (onion services):
4017 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4018 than one private key for a hidden service. Fixes bug 29040; bugfix
4020 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4021 "debug" level. Tor used to log it as a warning, which caused very
4022 long log lines to appear for some users. Fixes bug 29135; bugfix
4024 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4025 as a warning. Instead, log it as a protocol warning, because there
4026 is nothing that relay operators can do to fix it. Fixes bug 29029;
4027 bugfix on 0.2.5.7-rc.
4029 o Minor bugfixes (scheduler):
4030 - When re-adding channels to the pending list, check the correct
4031 channel's sched_heap_idx. This issue has had no effect in mainline
4032 Tor, but could have led to bugs down the road in improved versions
4033 of our circuit scheduling code. Fixes bug 29508; bugfix
4036 o Minor bugfixes (tests):
4037 - Fix intermittent failures on an adaptive padding test. Fixes one
4038 case of bug 29122; bugfix on 0.4.0.1-alpha.
4039 - Disable an unstable circuit-padding test that was failing
4040 intermittently because of an ill-defined small histogram. Such
4041 histograms will be allowed again after 29298 is implemented. Fixes
4042 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
4043 - Detect and suppress "bug" warnings from the util/time test on
4044 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4045 - Do not log an error-level message if we fail to find an IPv6
4046 network interface from the unit tests. Fixes bug 29160; bugfix
4050 - In the manpage entry describing MapAddress torrc setting, use
4051 example IP addresses from ranges specified for use in documentation
4052 by RFC 5737. Resolves issue 28623.
4055 - Remove the old check-tor script. Resolves issue 29072.
4058 Changes in version 0.4.0.1-alpha - 2019-01-18
4059 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
4060 introduces improved features for power and bandwidth conservation,
4061 more accurate reporting of bootstrap progress for user interfaces, and
4062 an experimental backend for an exciting new adaptive padding feature.
4063 There is also the usual assortment of bugfixes and minor features, all
4066 o Major features (battery management, client, dormant mode):
4067 - When Tor is running as a client, and it is unused for a long time,
4068 it can now enter a "dormant" state. When Tor is dormant, it avoids
4069 network and CPU activity until it is reawoken either by a user
4070 request or by a controller command. For more information, see the
4071 configuration options starting with "Dormant". Implements tickets
4073 - The client's memory of whether it is "dormant", and how long it
4074 has spent idle, persists across invocations. Implements
4076 - There is a DormantOnFirstStartup option that integrators can use
4077 if they expect that in many cases, Tor will be installed but
4080 o Major features (bootstrap reporting):
4081 - When reporting bootstrap progress, report the first connection
4082 uniformly, regardless of whether it's a connection for building
4083 application circuits. This allows finer-grained reporting of early
4084 progress than previously possible, with the improvements of ticket
4085 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
4086 - When reporting bootstrap progress, treat connecting to a proxy or
4087 pluggable transport as separate from having successfully used that
4088 proxy or pluggable transport to connect to a relay. Closes tickets
4091 o Major features (circuit padding):
4092 - Implement preliminary support for the circuit padding portion of
4093 Proposal 254. The implementation supports Adaptive Padding (aka
4094 WTF-PAD) state machines for use between experimental clients and
4095 relays. Support is also provided for APE-style state machines that
4096 use probability distributions instead of histograms to specify
4097 inter-packet delay. At the moment, Tor does not provide any
4098 padding state machines that are used in normal operation: for now,
4099 this feature exists solely for experimentation. Closes
4102 o Major features (refactoring):
4103 - Tor now uses an explicit list of its own subsystems when
4104 initializing and shutting down. Previously, these systems were
4105 managed implicitly in various places throughout the codebase.
4106 (There may still be some subsystems using the old system.) Closes
4109 o Minor features (bootstrap reporting):
4110 - When reporting bootstrap progress, stop distinguishing between
4111 situations where only internal paths are available and situations
4112 where external paths are available. Previously, Tor would often
4113 erroneously report that it had only internal paths. Closes
4116 o Minor features (continuous integration):
4117 - Log Python version during each Travis CI job. Resolves
4120 o Minor features (controller):
4121 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
4122 Implements ticket 28843.
4124 o Minor features (developer tooling):
4125 - Provide a git hook script to prevent "fixup!" and "squash!"
4126 commits from ending up in the master branch, as scripts/main/pre-
4127 push.git-hook. Closes ticket 27993.
4129 o Minor features (directory authority):
4130 - Directory authorities support a new consensus algorithm, under
4131 which the family lines in microdescriptors are encoded in a
4132 canonical form. This change makes family lines more compressible
4133 in transit, and on the client. Closes ticket 28266; implements
4136 o Minor features (directory authority, relay):
4137 - Authorities now vote on a "StaleDesc" flag to indicate that a
4138 relay's descriptor is so old that the relay should upload again
4139 soon. Relays treat this flag as a signal to upload a new
4140 descriptor. This flag will eventually let us remove the
4141 'published' date from routerstatus entries, and make our consensus
4142 diffs much smaller. Closes ticket 26770; implements proposal 293.
4144 o Minor features (fallback directory mirrors):
4145 - Update the fallback whitelist based on operator opt-ins and opt-
4146 outs. Closes ticket 24805, patch by Phoul.
4148 o Minor features (FreeBSD):
4149 - On FreeBSD-based systems, warn relay operators if the
4150 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
4151 Closes ticket 28518.
4153 o Minor features (HTTP standards compliance):
4154 - Stop sending the header "Content-type: application/octet-stream"
4155 along with transparently compressed documents: this confused
4156 browsers. Closes ticket 28100.
4158 o Minor features (IPv6):
4159 - We add an option ClientAutoIPv6ORPort, to make clients randomly
4160 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
4161 every time a node is loaded from a new consensus or bridge config.
4162 We expect that this option will enable clients to bootstrap more
4163 quickly without having to determine whether they support IPv4,
4164 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
4165 - When using addrs_in_same_network_family(), avoid choosing circuit
4166 paths that pass through the same IPv6 subnet more than once.
4167 Previously, we only checked IPv4 subnets. Closes ticket 24393.
4168 Patch by Neel Chauhan.
4170 o Minor features (log messages):
4171 - Improve log message in v3 onion services that could print out
4172 negative revision counters. Closes ticket 27707. Patch
4175 o Minor features (memory usage):
4176 - Save memory by storing microdescriptor family lists with a more
4177 compact representation. Closes ticket 27359.
4178 - Tor clients now use mmap() to read consensus files from disk, so
4179 that they no longer need keep the full text of a consensus in
4180 memory when parsing it or applying a diff. Closes ticket 27244.
4182 o Minor features (parsing):
4183 - Directory authorities now validate that router descriptors and
4184 ExtraInfo documents are in a valid subset of UTF-8, and reject
4185 them if they are not. Closes ticket 27367.
4187 o Minor features (performance):
4188 - Cache the results of summarize_protocol_flags(), so that we don't
4189 have to parse the same protocol-versions string over and over.
4190 This should save us a huge number of malloc calls on startup, and
4191 may reduce memory fragmentation with some allocators. Closes
4193 - Remove a needless memset() call from get_token_arguments, thereby
4194 speeding up the tokenization of directory objects by about 20%.
4195 Closes ticket 28852.
4196 - Replace parse_short_policy() with a faster implementation, to
4197 improve microdescriptor parsing time. Closes ticket 28853.
4198 - Speed up directory parsing a little by avoiding use of the non-
4199 inlined strcmp_len() function. Closes ticket 28856.
4200 - Speed up microdescriptor parsing by about 30%, to help improve
4201 startup time. Closes ticket 28839.
4203 o Minor features (pluggable transports):
4204 - Add support for emitting STATUS updates to Tor's control port from
4205 a pluggable transport process. Closes ticket 28846.
4206 - Add support for logging to Tor's logging subsystem from a
4207 pluggable transport process. Closes ticket 28180.
4209 o Minor features (process management):
4210 - Add a new process API for handling child processes. This new API
4211 allows Tor to have bi-directional communication with child
4212 processes on both Unix and Windows. Closes ticket 28179.
4213 - Use the subsystem manager to initialize and shut down the process
4214 module. Closes ticket 28847.
4216 o Minor features (relay):
4217 - When listing relay families, list them in canonical form including
4218 the relay's own identity, and try to give a more useful set of
4219 warnings. Part of ticket 28266 and proposal 298.
4221 o Minor features (required protocols):
4222 - Before exiting because of a missing required protocol, Tor will
4223 now check the publication time of the consensus, and not exit
4224 unless the consensus is newer than the Tor program's own release
4225 date. Previously, Tor would not check the consensus publication
4226 time, and so might exit because of a missing protocol that might
4227 no longer be required in a current consensus. Implements proposal
4228 297; closes ticket 27735.
4230 o Minor features (testing):
4231 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
4232 networks. Closes ticket 28840. Patch by Rob Jansen.
4234 o Minor bugfixes (client, clock skew):
4235 - Bootstrap successfully even when Tor's clock is behind the clocks
4236 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
4237 - Select guards even if the consensus has expired, as long as the
4238 consensus is still reasonably live. Fixes bug 24661; bugfix
4241 o Minor bugfixes (compilation):
4242 - Compile correctly on OpenBSD; previously, we were missing some
4243 headers required in order to detect it properly. Fixes bug 28938;
4244 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4246 o Minor bugfixes (directory clients):
4247 - Mark outdated dirservers when Tor only has a reasonably live
4248 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4250 o Minor bugfixes (directory mirrors):
4251 - Even when a directory mirror's clock is behind the clocks on the
4252 authorities, we now allow the mirror to serve "future"
4253 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
4255 o Minor bugfixes (DNS):
4256 - Gracefully handle an empty or absent resolve.conf file by falling
4257 back to using "localhost" as a DNS server (and hoping it works).
4258 Previously, we would just stop running as an exit. Fixes bug
4259 21900; bugfix on 0.2.1.10-alpha.
4261 o Minor bugfixes (guards):
4262 - In count_acceptable_nodes(), the minimum number is now one bridge
4263 or guard node, and two non-guard nodes for a circuit. Previously,
4264 we had added up the sum of all nodes with a descriptor, but that
4265 could cause us to build failing circuits when we had either too
4266 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
4267 0.2.3.1-alpha. Patch by Neel Chauhan.
4269 o Minor bugfixes (IPv6):
4270 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4271 IPv6 socket was bound using an address family of AF_INET instead
4272 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4275 o Minor bugfixes (logging):
4276 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4277 link protocol versions when logging incoming/outgoing connection
4278 counts. Tor no longer skips version 5, and we won't have to
4279 remember to update this function when new link protocol version is
4280 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4282 o Minor bugfixes (networking):
4283 - Introduce additional checks into tor_addr_parse() to reject
4284 certain incorrect inputs that previously were not detected. Fixes
4285 bug 23082; bugfix on 0.2.0.10-alpha.
4287 o Minor bugfixes (onion service v3, client):
4288 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4289 connection waiting for a descriptor that we actually have in the
4290 cache. It turns out that this can actually happen, though it is
4291 rare. Now, tor will recover and retry the descriptor. Fixes bug
4292 28669; bugfix on 0.3.2.4-alpha.
4294 o Minor bugfixes (periodic events):
4295 - Refrain from calling routerlist_remove_old_routers() from
4296 check_descriptor_callback(). Instead, create a new hourly periodic
4297 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
4299 o Minor bugfixes (pluggable transports):
4300 - Make sure that data is continously read from standard output and
4301 standard error pipes of a pluggable transport child-process, to
4302 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
4303 bugfix on 0.2.3.6-alpha.
4305 o Minor bugfixes (unit tests):
4306 - Instead of relying on hs_free_all() to clean up all onion service
4307 objects in test_build_descriptors(), we now deallocate them one by
4308 one. This lets Coverity know that we are not leaking memory there
4309 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
4311 o Minor bugfixes (usability):
4312 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4313 Some users took this phrasing to mean that the mentioned guard was
4314 under their control or responsibility, which it is not. Fixes bug
4315 28895; bugfix on Tor 0.3.0.1-alpha.
4317 o Code simplification and refactoring:
4318 - Reimplement NETINFO cell parsing and generation to rely on
4319 trunnel-generated wire format handling code. Closes ticket 27325.
4320 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
4322 - Rework SOCKS wire format handling to rely on trunnel-generated
4323 parsing/generation code. Resolves ticket 27620.
4324 - Split out bootstrap progress reporting from control.c into a
4325 separate file. Part of ticket 27402.
4326 - The .may_include files that we use to describe our directory-by-
4327 directory dependency structure now describe a noncircular
4328 dependency graph over the directories that they cover. Our
4329 checkIncludes.py tool now enforces this noncircularity. Closes
4333 - Mention that you cannot add a new onion service if Tor is already
4334 running with Sandbox enabled. Closes ticket 28560.
4335 - Improve ControlPort documentation. Mention that it accepts
4336 address:port pairs, and can be used multiple times. Closes
4338 - Document the exact output of "tor --version". Closes ticket 28889.
4341 - Stop responding to the 'GETINFO status/version/num-concurring' and
4342 'GETINFO status/version/num-versioning' control port commands, as
4343 those were deprecated back in 0.2.0.30. Also stop listing them in
4344 output of 'GETINFO info/names'. Resolves ticket 28757.
4345 - The scripts used to generate and maintain the list of fallback
4346 directories have been extracted into a new "fallback-scripts"
4347 repository. Closes ticket 27914.
4350 - Run shellcheck for scripts in the in scripts/ directory. Closes
4352 - Add unit tests for tokenize_string() and get_next_token()
4353 functions. Resolves ticket 27625.
4355 o Code simplification and refactoring (onion service v3):
4356 - Consolidate the authorized client descriptor cookie computation
4357 code from client and service into one function. Closes
4360 o Code simplification and refactoring (shell scripts):
4361 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
4363 - Fix issues that shellcheck found in chutney-git-bisect.sh.
4364 Resolves ticket 28006.
4365 - Fix issues that shellcheck found in updateRustDependencies.sh.
4366 Resolves ticket 28012.
4367 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
4368 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
4369 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
4370 - Fix shellcheck warnings in scripts/test/coverage. Resolves
4374 Changes in version 0.3.3.11 - 2019-01-07
4375 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
4376 numerous fixes, including an important fix for anyone using OpenSSL
4377 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
4378 to this version, or to a later series.
4380 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
4381 We anticipate that this will be the last release of Tor 0.3.3, unless
4382 some major bug is before then. Some time between now and then, users
4383 should switch to either the Tor 0.3.4 series (supported until at least
4384 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
4385 support until at least 1 Feb 2022.
4387 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4388 - Fix our usage of named groups when running as a TLS 1.3 client in
4389 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4390 running as a relay, which caused clients to fail to negotiate TLS
4391 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4394 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4395 - Fix a use-after-free error that could be caused by passing Tor an
4396 impossible set of options that would fail during options_act().
4397 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4399 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4400 - Only run one online rust build in Travis, to reduce network
4401 errors. Skip offline rust builds on Travis for Linux gcc, because
4402 they're redundant. Implements ticket 27252.
4403 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4404 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4405 Linux with default settings, because all the non-default builds
4406 use gcc on Linux. Implements ticket 27252.
4408 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4409 - Use the Travis Homebrew addon to install packages on macOS during
4410 Travis CI. The package list is the same, but the Homebrew addon
4411 does not do a `brew update` by default. Implements ticket 27738.
4413 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4414 - Replace the 150 fallbacks originally introduced in Tor
4415 0.3.3.1-alpha in January 2018 (of which ~115 were still
4416 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4417 removed) generated in December 2018. Closes ticket 24803.
4419 o Minor features (geoip):
4420 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4421 Country database. Closes ticket 29012.
4423 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4424 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4425 key export function from handling long labels. When this bug is
4426 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4427 version of OpenSSL without this bug when it becomes available.
4428 Closes ticket 28973.
4430 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4431 - Update relay descriptor on bandwidth changes only when the uptime
4432 is smaller than 24h, in order to reduce the efficiency of guard
4433 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4435 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
4436 - Avoid undefined behavior in an end-of-string check when parsing
4437 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4440 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4441 - Rewrite our assertion macros so that they no longer suppress the
4442 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4444 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4445 - Initialize a variable unconditionally in aes_new_cipher(), since
4446 some compilers cannot tell that we always initialize it before
4447 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4449 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
4450 - Log additional info when we get a relay that shares an ed25519 ID
4451 with a different relay, instead making a BUG() warning. Fixes bug
4452 27800; bugfix on 0.3.2.1-alpha.
4454 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4455 - When a user requests a group-readable DataDirectory, give it to
4456 them. Previously, when the DataDirectory and the CacheDirectory
4457 were the same, the default setting (0) for
4458 CacheDirectoryGroupReadable would override the setting for
4459 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4462 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4463 - When the onion service directory can't be created or has the wrong
4464 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4467 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4468 - Close all SOCKS request (for the same .onion) if the newly fetched
4469 descriptor is unusable. Before that, we would close only the first
4470 one leaving the other hanging and let to time out by themselves.
4471 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4473 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4474 - Don't warn so loudly when Tor is unable to decode an onion
4475 descriptor. This can now happen as a normal use case if a client
4476 gets a descriptor with client authorization but the client is not
4477 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4479 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4480 - When deleting an ephemeral onion service (DEL_ONION), do not close
4481 any rendezvous circuits in order to let the existing client
4482 connections finish by themselves or closed by the application. The
4483 HS v2 is doing that already so now we have the same behavior for
4484 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4486 o Minor bugfixes (HTTP tunnel):
4487 - Fix a bug warning when closing an HTTP tunnel connection due to
4488 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
4491 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4492 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4493 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4495 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4496 - Ensure circuitmux queues are empty before scheduling or sending
4497 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4499 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4500 - Reject protocol names containing bytes other than alphanumeric
4501 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4504 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4505 - Compute protover votes correctly in the rust version of the
4506 protover code. Previously, the protover rewrite in 24031 allowed
4507 repeated votes from the same voter for the same protocol version
4508 to be counted multiple times in protover_compute_vote(). Fixes bug
4509 27649; bugfix on 0.3.3.5-rc.
4510 - Reject protover names that contain invalid characters. Fixes bug
4511 27687; bugfix on 0.3.3.1-alpha.
4513 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4514 - protover_all_supported() would attempt to allocate up to 16GB on
4515 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4516 bugfix on 0.3.3.5-rc.
4518 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
4519 - Fix a potential null dereference in protover_all_supported(). Add
4520 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4521 - Return a string that can be safely freed by C code, not one
4522 created by the rust allocator, in protover_all_supported(). Fixes
4523 bug 27740; bugfix on 0.3.3.1-alpha.
4524 - Fix an API mismatch in the rust implementation of
4525 protover_compute_vote(). This bug could have caused crashes on any
4526 directory authorities running Tor with Rust (which we do not yet
4527 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4529 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4530 - If a unit test running in a subprocess exits abnormally or with a
4531 nonzero status code, treat the test as having failed, even if the
4532 test reported success. Without this fix, memory leaks don't cause
4533 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4534 bugfix on 0.2.2.4-alpha.
4536 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
4537 - Treat backtrace test failures as expected on BSD-derived systems
4538 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4539 (FreeBSD failures have been treated as expected since 18204 in
4540 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4542 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4543 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4544 bugfix on 0.3.0.1-alpha.
4547 Changes in version 0.3.4.10 - 2019-01-07
4548 Tor 0.3.4.9 is the second stable release in its series; it backports
4549 numerous fixes, including an important fix for relays, and for anyone
4550 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
4553 As a reminder, the Tor 0.3.4 series will be supported until 10 June
4554 2019. Some time between now and then, users should switch to the Tor
4555 0.3.5 series, which will receive long-term support until at least 1
4558 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4559 - Fix our usage of named groups when running as a TLS 1.3 client in
4560 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4561 running as a relay, which caused clients to fail to negotiate TLS
4562 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4565 o Major bugfixes (relay, directory, backport from 0.3.5.7):
4566 - Always reactivate linked connections in the main loop so long as
4567 any linked connection has been active. Previously, connections
4568 serving directory information wouldn't get reactivated after the
4569 first chunk of data was sent (usually 32KB), which would prevent
4570 clients from bootstrapping. Fixes bug 28912; bugfix on
4571 0.3.4.1-alpha. Patch by "cypherpunks3".
4573 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
4574 - Always show the configure and test logs, and upload them as build
4575 artifacts, when building for Windows using Appveyor CI.
4578 o Minor features (controller, backport from 0.3.5.1-alpha):
4579 - For purposes of CIRC_BW-based dropped cell detection, track half-
4580 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4581 bias check cells to arrive without counting it as dropped until
4582 either the END arrives, or the windows are empty. Closes
4585 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4586 - Replace the 150 fallbacks originally introduced in Tor
4587 0.3.3.1-alpha in January 2018 (of which ~115 were still
4588 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4589 removed) generated in December 2018. Closes ticket 24803.
4591 o Minor features (geoip):
4592 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4593 Country database. Closes ticket 28395.
4595 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4596 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4597 key export function from handling long labels. When this bug is
4598 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4599 version of OpenSSL without this bug when it becomes available.
4600 Closes ticket 28973.
4602 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4603 - Initialize a variable unconditionally in aes_new_cipher(), since
4604 some compilers cannot tell that we always initialize it before
4605 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4607 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
4608 - Avoid a logging a BUG() stacktrace when closing connection held
4609 open because the write side is rate limited but not the read side.
4610 Now, the connection read side is simply shut down until Tor is
4611 able to flush the connection and close it. Fixes bug 27750; bugfix
4614 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
4615 - Manually configure the zstd compiler options, when building using
4616 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4617 not come with a pkg-config file. Fixes bug 28454; bugfix
4619 - Stop using an external OpenSSL install, and stop installing MSYS2
4620 packages, when building using mingw on Appveyor Windows CI. Fixes
4621 bug 28399; bugfix on 0.3.4.1-alpha.
4623 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
4624 - Explicitly specify the path to the OpenSSL library and do not
4625 download OpenSSL from Pacman, but instead use the library that is
4626 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4628 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4629 - When a user requests a group-readable DataDirectory, give it to
4630 them. Previously, when the DataDirectory and the CacheDirectory
4631 were the same, the default setting (0) for
4632 CacheDirectoryGroupReadable would override the setting for
4633 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4636 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4637 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4638 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4640 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4641 - Don't warn so loudly when Tor is unable to decode an onion
4642 descriptor. This can now happen as a normal use case if a client
4643 gets a descriptor with client authorization but the client is not
4644 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4646 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4647 - When deleting an ephemeral onion service (DEL_ONION), do not close
4648 any rendezvous circuits in order to let the existing client
4649 connections finish by themselves or closed by the application. The
4650 HS v2 is doing that already so now we have the same behavior for
4651 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4653 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4654 - Update relay descriptor on bandwidth changes only when the uptime
4655 is smaller than 24h, in order to reduce the efficiency of guard
4656 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4658 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4659 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4660 bugfix on 0.3.0.1-alpha.
4663 Changes in version 0.3.5.7 - 2019-01-07
4664 Tor 0.3.5.7 is the first stable release in its series; it includes
4665 compilation and portability fixes, and a fix for a severe problem
4666 affecting directory caches.
4668 The Tor 0.3.5 series includes several new features and performance
4669 improvements, including client authorization for v3 onion services,
4670 cleanups to bootstrap reporting, support for improved bandwidth-
4671 measurement tools, experimental support for NSS in place of OpenSSL,
4672 and much more. It also begins a full reorganization of Tor's code
4673 layout, for improved modularity and maintainability in the future.
4674 Finally, there is the usual set of performance improvements and
4675 bugfixes that we try to do in every release series.
4677 There are a couple of changes in the 0.3.5 that may affect
4678 compatibility. First, the default version for newly created onion
4679 services is now v3. Use the HiddenServiceVersion option if you want to
4680 override this. Second, some log messages related to bootstrapping have
4681 changed; if you use stem, you may need to update to the latest version
4682 so it will recognize them.
4684 We have designated 0.3.5 as a "long-term support" (LTS) series: we
4685 will continue to patch major bugs in typical configurations of 0.3.5
4686 until at least 1 Feb 2022. (We do not plan to provide long-term
4687 support for embedding, Rust support, NSS support, running a directory
4688 authority, or unsupported platforms. For these, you will need to stick
4689 with the latest stable release.)
4691 Below are the changes since 0.3.5.6-rc. For a complete list of changes
4692 since 0.3.4.9, see the ReleaseNotes file.
4694 o Major bugfixes (relay, directory):
4695 - Always reactivate linked connections in the main loop so long as
4696 any linked connection has been active. Previously, connections
4697 serving directory information wouldn't get reactivated after the
4698 first chunk of data was sent (usually 32KB), which would prevent
4699 clients from bootstrapping. Fixes bug 28912; bugfix on
4700 0.3.4.1-alpha. Patch by "cypherpunks3".
4702 o Minor features (compilation):
4703 - When possible, place our warning flags in a separate file, to
4704 avoid flooding verbose build logs. Closes ticket 28924.
4706 o Minor features (geoip):
4707 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4708 Country database. Closes ticket 29012.
4710 o Minor features (OpenSSL bug workaround):
4711 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4712 key export function from handling long labels. When this bug is
4713 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4714 version of OpenSSL without this bug when it becomes available.
4715 Closes ticket 28973.
4717 o Minor features (performance):
4718 - Remove about 96% of the work from the function that we run at
4719 startup to test our curve25519_basepoint implementation. Since
4720 this function has yet to find an actual failure, we now only run
4721 it for 8 iterations instead of 200. Based on our profile
4722 information, this change should save around 8% of our startup time
4723 on typical desktops, and may have a similar effect on other
4724 platforms. Closes ticket 28838.
4725 - Stop re-validating our hardcoded Diffie-Hellman parameters on
4726 every startup. Doing this wasted time and cycles, especially on
4727 low-powered devices. Closes ticket 28851.
4729 o Minor bugfixes (compilation):
4730 - Fix compilation for Android by adding a missing header to
4731 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
4733 o Minor bugfixes (correctness):
4734 - Fix an unreached code path where we checked the value of
4735 "hostname" inside send_resolved_hostname_cell(). Previously, we
4736 used it before checking it; now we check it first. Fixes bug
4737 28879; bugfix on 0.1.2.7-alpha.
4739 o Minor bugfixes (testing):
4740 - Make sure that test_rebind.py actually obeys its timeout, even
4741 when it receives a large number of log messages. Fixes bug 28883;
4742 bugfix on 0.3.5.4-alpha.
4743 - Stop running stem's unit tests as part of "make test-stem", but
4744 continue to run stem's unit and online tests during "make test-
4745 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
4747 o Minor bugfixes (windows services):
4748 - Make Tor start correctly as an NT service again: previously it was
4749 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
4751 o Code simplification and refactoring:
4752 - When parsing a port configuration, make it more obvious to static
4753 analyzer tools that we always initialize the address. Closes
4757 Changes in version 0.3.5.6-rc - 2018-12-18
4758 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
4759 It is the first release candidate in the 0.3.5.x series; if no further
4760 huge bugs are found, our next release may be the stable 0.3.5.x.
4762 o Minor features (continuous integration, Windows):
4763 - Always show the configure and test logs, and upload them as build
4764 artifacts, when building for Windows using Appveyor CI.
4767 o Minor features (fallback directory list):
4768 - Replace the 150 fallbacks originally introduced in Tor
4769 0.3.3.1-alpha in January 2018 (of which ~115 were still
4770 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4771 removed) generated in December 2018. Closes ticket 24803.
4773 o Minor features (geoip):
4774 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
4775 Country database. Closes ticket 28744.
4777 o Minor bugfixes (compilation):
4778 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
4779 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
4781 o Minor bugfixes (continuous integration, Windows):
4782 - Explicitly specify the path to the OpenSSL library and do not
4783 download OpenSSL from Pacman, but instead use the library that is
4784 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4786 o Minor bugfixes (onion service v3):
4787 - When deleting an ephemeral onion service (DEL_ONION), do not close
4788 any rendezvous circuits in order to let the existing client
4789 connections finish by themselves or closed by the application. The
4790 HS v2 is doing that already so now we have the same behavior for
4791 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4793 o Minor bugfixes (restart-in-process, boostrap):
4794 - Add missing resets of bootstrap tracking state when shutting down
4795 (regression caused by ticket 27169). Fixes bug 28524; bugfix
4798 o Minor bugfixes (testing):
4799 - Use a separate DataDirectory for the test_rebind script.
4800 Previously, this script would run using the default DataDirectory,
4801 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
4802 Patch from Taylor R Campbell.
4803 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4804 bugfix on 0.3.0.1-alpha.
4806 o Minor bugfixes (Windows):
4807 - Correctly identify Windows 8.1, Windows 10, and Windows Server
4808 2008 and later from their NT versions. Fixes bug 28096; bugfix on
4809 0.2.2.34; reported by Keifer Bly.
4810 - On recent Windows versions, the GetVersionEx() function may report
4811 an earlier Windows version than the running OS. To avoid user
4812 confusion, add "[or later]" to Tor's version string on affected
4813 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
4815 - Remove Windows versions that were never supported by the
4816 GetVersionEx() function. Stop duplicating the latest Windows
4817 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
4818 reported by Keifer Bly.
4821 - Increase logging and tag all log entries with timestamps in
4822 test_rebind.py. Provides diagnostics for issue 28229.
4824 o Code simplification and refactoring (shared random, dirauth):
4825 - Change many tor_assert() to use BUG() instead. The idea is to not
4826 crash a dirauth but rather scream loudly with a stacktrace and let
4827 it continue run. The shared random subsystem is very resilient and
4828 if anything wrong happens with it, at worst a non coherent value
4829 will be put in the vote and discarded by the other authorities.
4830 Closes ticket 19566.
4832 o Documentation (onion services):
4833 - Document in the man page that changing ClientOnionAuthDir value or
4834 adding a new file in the directory will not work at runtime upon
4835 sending a HUP if Sandbox 1. Closes ticket 28128.
4836 - Note in the man page that the only real way to fully revoke an
4837 onion service v3 client authorization is by restarting the tor
4838 process. Closes ticket 28275.
4841 Changes in version 0.3.5.5-alpha - 2018-11-16
4842 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
4843 including several that we hope to backport to older release series in
4846 o Major bugfixes (OpenSSL, portability):
4847 - Fix our usage of named groups when running as a TLS 1.3 client in
4848 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4849 running as a relay, which caused clients to fail to negotiate TLS
4850 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4853 o Minor features (geoip):
4854 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4855 Country database. Closes ticket 28395.
4857 o Minor bugfixes (compilation):
4858 - Initialize a variable unconditionally in aes_new_cipher(), since
4859 some compilers cannot tell that we always initialize it before
4860 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4862 o Minor bugfixes (connection, relay):
4863 - Avoid a logging a BUG() stacktrace when closing connection held
4864 open because the write side is rate limited but not the read side.
4865 Now, the connection read side is simply shut down until Tor is
4866 able to flush the connection and close it. Fixes bug 27750; bugfix
4869 o Minor bugfixes (continuous integration, Windows):
4870 - Manually configure the zstd compiler options, when building using
4871 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4872 not come with a pkg-config file. Fixes bug 28454; bugfix
4874 - Stop using an external OpenSSL install, and stop installing MSYS2
4875 packages, when building using mingw on Appveyor Windows CI. Fixes
4876 bug 28399; bugfix on 0.3.4.1-alpha.
4878 o Minor bugfixes (documentation):
4879 - Make Doxygen work again after the code movement in the 0.3.5
4880 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
4882 o Minor bugfixes (Linux seccomp2 sandbox):
4883 - Permit the "shutdown()" system call, which is apparently used by
4884 OpenSSL under some circumstances. Fixes bug 28183; bugfix
4887 o Minor bugfixes (logging):
4888 - Stop talking about the Named flag in log messages. Clients have
4889 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
4892 o Minor bugfixes (memory leaks):
4893 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4894 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4896 o Minor bugfixes (onion services):
4897 - On an intro point for a version 3 onion service, stop closing
4898 introduction circuits on an NACK. This lets the client decide
4899 whether to reuse the circuit or discard it. Previously, we closed
4900 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
4901 0.3.2.1-alpha. Patch by Neel Chaunan.
4902 - When replacing a descriptor in the client cache, make sure to
4903 close all client introduction circuits for the old descriptor, so
4904 we don't end up with unusable leftover circuits. Fixes bug 27471;
4905 bugfix on 0.3.2.1-alpha.
4908 Changes in version 0.3.5.4-alpha - 2018-11-08
4909 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
4910 improves our continuous integration support. It continues our attempts
4911 to stabilize this alpha branch and build it into a foundation for an
4912 acceptable long-term-support release.
4914 o Major bugfixes (compilation, rust):
4915 - Rust tests can now build and run successfully with the
4916 --enable-fragile-hardening option enabled. Doing this currently
4917 requires the rust beta channel; it will be possible with stable
4918 rust once Rust version 1.31 is released. Patch from Alex Crichton.
4919 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
4921 o Major bugfixes (embedding, main loop):
4922 - When DisableNetwork becomes set, actually disable periodic events
4923 that are already enabled. (Previously, we would refrain from
4924 enabling new ones, but we would leave the old ones turned on.)
4925 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
4927 o Minor features (continuous integration):
4928 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
4930 - Add new CI job to Travis configuration to run stem-based
4931 integration tests. Closes ticket 27913.
4933 o Minor features (Windows, continuous integration):
4934 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
4935 Appveyor's CI. Closes ticket 28318.
4937 o Minor bugfixes (C correctness, also in 0.3.4.9):
4938 - Avoid undefined behavior in an end-of-string check when parsing
4939 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4942 o Minor bugfixes (compilation):
4943 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
4944 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4946 o Minor bugfixes (compilation, OpenSolaris):
4947 - Fix compilation on OpenSolaris and its descendants by adding a
4948 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
4951 o Minor bugfixes (configuration):
4952 - Refuse to start with relative file paths and RunAsDaemon set
4953 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
4956 o Minor bugfixes (directory authority, also in 0.3.4.9):
4957 - Log additional info when we get a relay that shares an ed25519 ID
4958 with a different relay, instead of a BUG() warning with a
4959 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
4961 o Minor bugfixes (onion service v3):
4962 - Build the service descriptor's signing key certificate before
4963 uploading, so we always have a fresh one: leaving no chances for
4964 it to expire service side. Fixes bug 27838; bugfix
4967 o Minor bugfixes (onion service v3, client authorization):
4968 - Fix an assert() when adding a client authorization for the first
4969 time and then sending a HUP signal to the service. Before that,
4970 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
4972 o Minor bugfixes (onion services):
4973 - Unless we have explicitly set HiddenServiceVersion, detect the
4974 onion service version and then look for invalid options.
4975 Previously, we did the reverse, but that broke existing configs
4976 which were pointed to a v2 service and had options like
4977 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
4978 0.3.5.1-alpha. Patch by Neel Chauhan.
4980 o Minor bugfixes (portability):
4981 - Make the OPE code (which is used for v3 onion services) run
4982 correctly on big-endian platforms. Fixes bug 28115; bugfix
4985 o Minor bugfixes (protover, rust):
4986 - Reject extra commas in version strings. Fixes bug 27197; bugfix
4989 o Minor bugfixes (relay shutdown, systemd):
4990 - Notify systemd of ShutdownWaitLength so it can be set to longer
4991 than systemd's TimeoutStopSec. In Tor's systemd service file, set
4992 TimeoutSec to 60 seconds to allow Tor some time to shut down.
4993 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
4995 o Minor bugfixes (rust, also in 0.3.4.9):
4996 - Fix a potential null dereference in protover_all_supported(). Add
4997 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4998 - Return a string that can be safely freed by C code, not one
4999 created by the rust allocator, in protover_all_supported(). Fixes
5000 bug 27740; bugfix on 0.3.3.1-alpha.
5002 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
5003 - Fix an API mismatch in the rust implementation of
5004 protover_compute_vote(). This bug could have caused crashes on any
5005 directory authorities running Tor with Rust (which we do not yet
5006 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5008 o Minor bugfixes (testing):
5009 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
5010 27968; bugfix on 0.3.5.1-alpha.
5012 o Minor bugfixes (testing, also in 0.3.4.9):
5013 - Treat backtrace test failures as expected on BSD-derived systems
5014 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5015 (FreeBSD failures have been treated as expected since 18204 in
5016 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5018 o Documentation (onion service manpage):
5019 - Improve HSv3 client authorization by making some options more
5020 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
5023 Changes in version 0.3.4.9 - 2018-11-02
5024 Tor 0.3.4.9 is the second stable release in its series; it backports
5025 numerous fixes, including a fix for a bandwidth management bug that
5026 was causing memory exhaustion on relays. Anyone running an earlier
5027 version of Tor 0.3.4.9 should upgrade.
5029 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
5030 - Fix compilation on ARM (and other less-used CPUs) when compiling
5031 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5033 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
5034 - Make sure Tor bootstraps and works properly if only the
5035 ControlPort is set. Prior to this fix, Tor would only bootstrap
5036 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5037 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5039 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
5040 - When our write bandwidth limit is exhausted, stop writing on the
5041 connection. Previously, we had a typo in the code that would make
5042 us stop reading instead, leading to relay connections being stuck
5043 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5046 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
5047 - Fix a use-after-free error that could be caused by passing Tor an
5048 impossible set of options that would fail during options_act().
5049 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5051 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
5052 - Don't do a distcheck with --disable-module-dirauth in Travis.
5053 Implements ticket 27252.
5054 - Only run one online rust build in Travis, to reduce network
5055 errors. Skip offline rust builds on Travis for Linux gcc, because
5056 they're redundant. Implements ticket 27252.
5057 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5058 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5059 Linux with default settings, because all the non-default builds
5060 use gcc on Linux. Implements ticket 27252.
5062 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5063 - Use the Travis Homebrew addon to install packages on macOS during
5064 Travis CI. The package list is the same, but the Homebrew addon
5065 does not do a `brew update` by default. Implements ticket 27738.
5067 o Minor features (geoip):
5068 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5069 Country database. Closes ticket 27991.
5071 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
5072 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5073 difference algorithm for 32-bit Apple platforms. Previously, it
5074 would overflow when calculating the difference between two times
5075 more than 47 days apart. Fixes part of bug 27139; bugfix
5077 - Improve the precision of our 32-bit millisecond difference
5078 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5079 bugfix on 0.3.4.1-alpha.
5080 - Relax the tolerance on the mainloop/update_time_jumps test when
5081 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5084 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
5085 - Avoid undefined behavior in an end-of-string check when parsing
5086 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5089 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
5090 - Only install the necessary mingw packages during our appveyor
5091 builds. This change makes the build a little faster, and prevents
5092 a conflict with a preinstalled mingw openssl that appveyor now
5093 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
5095 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5096 - Rewrite our assertion macros so that they no longer suppress the
5097 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5099 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
5100 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5101 27464; bugfix on 0.3.4.1-alpha.
5103 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
5104 - Log additional info when we get a relay that shares an ed25519 ID
5105 with a different relay, instead making a BUG() warning. Fixes bug
5106 27800; bugfix on 0.3.2.1-alpha.
5108 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
5109 - Avoid a double-close when shutting down a stalled directory
5110 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5112 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
5113 - Fix a bug warning when closing an HTTP tunnel connection due to an
5114 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5117 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5118 - Ensure circuitmux queues are empty before scheduling or sending
5119 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5121 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5122 - When the onion service directory can't be created or has the wrong
5123 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5126 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5127 - Close all SOCKS request (for the same .onion) if the newly fetched
5128 descriptor is unusable. Before that, we would close only the first
5129 one leaving the other hanging and let to time out by themselves.
5130 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5132 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5133 - When selecting a v3 rendezvous point, don't only look at the
5134 protover, but also check whether the curve25519 onion key is
5135 present. This way we avoid picking a relay that supports the v3
5136 rendezvous but for which we don't have the microdescriptor. Fixes
5137 bug 27797; bugfix on 0.3.2.1-alpha.
5139 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5140 - Reject protocol names containing bytes other than alphanumeric
5141 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5144 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5145 - Compute protover votes correctly in the rust version of the
5146 protover code. Previously, the protover rewrite in 24031 allowed
5147 repeated votes from the same voter for the same protocol version
5148 to be counted multiple times in protover_compute_vote(). Fixes bug
5149 27649; bugfix on 0.3.3.5-rc.
5150 - Reject protover names that contain invalid characters. Fixes bug
5151 27687; bugfix on 0.3.3.1-alpha.
5153 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5154 - protover_all_supported() would attempt to allocate up to 16GB on
5155 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5156 bugfix on 0.3.3.5-rc.
5158 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
5159 - Fix an API mismatch in the rust implementation of
5160 protover_compute_vote(). This bug could have caused crashes on any
5161 directory authorities running Tor with Rust (which we do not yet
5162 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5164 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
5165 - Fix a potential null dereference in protover_all_supported(). Add
5166 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5167 - Return a string that can be safely freed by C code, not one
5168 created by the rust allocator, in protover_all_supported(). Fixes
5169 bug 27740; bugfix on 0.3.3.1-alpha.
5171 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5172 - If a unit test running in a subprocess exits abnormally or with a
5173 nonzero status code, treat the test as having failed, even if the
5174 test reported success. Without this fix, memory leaks don't cause
5175 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5176 bugfix on 0.2.2.4-alpha.
5178 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
5179 - Make the hs_service tests use the same time source when creating
5180 the introduction point and when testing it. Now tests work better
5181 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5184 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
5185 - Treat backtrace test failures as expected on BSD-derived systems
5186 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5187 (FreeBSD failures have been treated as expected since 18204 in
5188 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5191 Changes in version 0.3.5.3-alpha - 2018-10-17
5192 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
5193 versions. One important fix for relays addresses a problem with rate-
5194 limiting code from back in 0.3.4.x: If the fix works out, we'll be
5195 backporting it soon. This release is still an alpha, but we hope it's
5196 getting closer and closer to stability.
5198 o Major features (onion services):
5199 - Version 3 onion services can now use the per-service
5200 HiddenServiceExportCircuitID option to differentiate client
5201 circuits. It communicates with the service by using the HAProxy
5202 protocol to assign virtual IP addresses to inbound client
5203 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
5205 o Major bugfixes (compilation):
5206 - Fix compilation on ARM (and other less-used CPUs) when compiling
5207 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5209 o Major bugfixes (initialization, crash):
5210 - Fix an assertion crash that would stop Tor from starting up if it
5211 tried to activate a periodic event too early. Fixes bug 27861;
5212 bugfix on 0.3.5.1-alpha.
5214 o Major bugfixes (mainloop, bootstrap):
5215 - Make sure Tor bootstraps and works properly if only the
5216 ControlPort is set. Prior to this fix, Tor would only bootstrap
5217 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5218 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5220 o Major bugfixes (relay):
5221 - When our write bandwidth limit is exhausted, stop writing on the
5222 connection. Previously, we had a typo in the code that would make
5223 us stop reading instead, leading to relay connections being stuck
5224 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5227 o Minor features (continuous integration):
5228 - Use the Travis Homebrew addon to install packages on macOS during
5229 Travis CI. The package list is the same, but the Homebrew addon
5230 does not do a `brew update` by default. Implements ticket 27738.
5231 - Report what program produced the mysterious core file that we
5232 occasionally see on Travis CI during make distcheck. Closes
5235 o Minor features (geoip):
5236 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5237 Country database. Closes ticket 27991.
5239 o Minor bugfixes (code safety):
5240 - Rewrite our assertion macros so that they no longer suppress the
5241 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5244 o Minor bugfixes (compilation):
5245 - Compile the ed25519-donna code with a correct declaration of
5246 crypto_strongest_rand(). Previously, we built it with one type,
5247 but linked it against another in the unit tests, which caused
5248 compilation failures with LTO enabled. This could have caused
5249 other undefined behavior in the tests. Fixes bug 27728; bugfix
5252 o Minor bugfixes (compilation, netbsd):
5253 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
5256 o Minor bugfixes (continuous integration, appveyor):
5257 - Install only the necessary mingw packages during our appveyor
5258 builds. This change makes the build a little faster, and prevents
5259 a conflict with a preinstalled mingw openssl that appveyor now
5260 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
5262 o Minor bugfixes (directory permissions):
5263 - When a user requests a group-readable DataDirectory, give it to
5264 them. Previously, when the DataDirectory and the CacheDirectory
5265 were the same, the default setting (0) for
5266 CacheDirectoryGroupReadable would override the setting for
5267 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5270 o Minor bugfixes (memory leaks):
5271 - Fix a small memory leak when calling Tor with --dump-config. Fixes
5272 bug 27893; bugfix on 0.3.2.1-alpha.
5274 o Minor bugfixes (networking):
5275 - In retry_listeners_ports(), make sure that we're removing a member
5276 of old_conns smartlist at most once. Fixes bug 27808; bugfix
5278 - Refrain from attempting socket rebinding when old and new
5279 listeners are in different address families. Fixes bug 27928;
5280 bugfix on 0.3.5.1-alpha.
5282 o Minor bugfixes (onion service v3):
5283 - Stop dumping a stack trace when trying to connect to an intro
5284 point without having a descriptor for it. Fixes bug 27774; bugfix
5286 - Don't warn so loudly when Tor is unable to decode an onion
5287 descriptor. This can now happen as a normal use case if a client
5288 gets a descriptor with client authorization but the client is not
5289 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5290 - When selecting a v3 rendezvous point, don't only look at the
5291 protover, but also check whether the curve25519 onion key is
5292 present. This way we avoid picking a relay that supports the v3
5293 rendezvous but for which we don't have the microdescriptor. Fixes
5294 bug 27797; bugfix on 0.3.2.1-alpha.
5296 o Minor bugfixes (protover):
5297 - Reject protocol names containing bytes other than alphanumeric
5298 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5301 o Minor bugfixes (testing):
5302 - Make the hs_service tests use the same time source when creating
5303 the introduction point and when testing it. Now tests work better
5304 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5306 - In test_rebind.py, check if the Python version is in the supported
5307 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
5309 o Code simplification and refactoring:
5310 - Divide more large Tor source files -- especially ones that span
5311 multiple areas of functionality -- into smaller parts, including
5312 onion.c and main.c. Closes ticket 26747.
5313 - Divide the "routerparse.c" module into separate modules for each
5314 group of parsed objects. Closes ticket 27924.
5315 - Move protover_rust.c to the same place protover.c was moved to.
5316 Closes ticket 27814.
5317 - Split directory.c into separate pieces for client, server, and
5318 common functionality. Closes ticket 26744.
5319 - Split the non-statistics-related parts from the rephist.c and
5320 geoip.c modules. Closes ticket 27892.
5321 - Split the router.c file into relay-only and shared components, to
5322 help with future modularization. Closes ticket 27864.
5325 - In the tor-resolve(1) manpage, fix the reference to socks-
5326 extensions.txt by adding a web URL. Resolves ticket 27853.
5327 - Mention that we require Python to be 2.7 or newer for some
5328 integration tests that we ship with Tor. Resolves ticket 27677.
5331 Changes in version 0.3.5.2-alpha - 2018-09-21
5332 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
5333 that made Tor think it had run out of sockets. Anybody running a relay
5334 or an onion service on 0.3.5.1-alpha should upgrade.
5336 o Major bugfixes (relay bandwidth statistics):
5337 - When we close relayed circuits, report the data in the circuit
5338 queues as being written in our relay bandwidth stats. This
5339 mitigates guard discovery and other attacks that close circuits
5340 for the explicit purpose of noticing this discrepancy in
5341 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
5343 o Major bugfixes (socket accounting):
5344 - In our socket accounting code, count a socket as closed even when
5345 it is closed indirectly by the TLS layer. Previously, we would
5346 count these sockets as still in use, and incorrectly believe that
5347 we had run out of sockets. Fixes bug 27795; bugfix
5350 o Minor bugfixes (32-bit OSX and iOS, timing):
5351 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5352 difference algorithm for 32-bit Apple platforms. Previously, it
5353 would overflow when calculating the difference between two times
5354 more than 47 days apart. Fixes part of bug 27139; bugfix
5356 - Improve the precision of our 32-bit millisecond difference
5357 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5358 bugfix on 0.3.4.1-alpha.
5359 - Relax the tolerance on the mainloop/update_time_jumps test when
5360 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5363 o Minor bugfixes (onion service v3):
5364 - Close all SOCKS request (for the same .onion) if the newly fetched
5365 descriptor is unusable. Before that, we would close only the first
5366 one leaving the other hanging and let to time out by themselves.
5367 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5369 o Minor bugfixes (memory leak):
5370 - Fix an unlikely memory leak when trying to read a private key from
5371 a ridiculously large file. Fixes bug 27764; bugfix on
5372 0.3.5.1-alpha. This is CID 1439488.
5374 o Minor bugfixes (NSS):
5375 - Correctly detect failure to open a dummy TCP socket when stealing
5376 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
5379 o Minor bugfixes (rust):
5380 - protover_all_supported() would attempt to allocate up to 16GB on
5381 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5382 bugfix on 0.3.3.5-rc.
5384 o Minor bugfixes (testing):
5385 - Revise the "conditionvar_timeout" test so that it succeeds even on
5386 heavily loaded systems where the test threads are not scheduled
5387 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
5389 o Code simplification and refactoring:
5390 - Divide the routerlist.c and dirserv.c modules into smaller parts.
5391 Closes ticket 27799.
5394 Changes in version 0.3.5.1-alpha - 2018-09-18
5395 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
5396 client authorization for modern (v3) onion services, improves
5397 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
5398 support for NSS in place of OpenSSL, and much more.
5400 o Major features (onion services, UI change):
5401 - For a newly created onion service, the default version is now 3.
5402 Tor still supports existing version 2 services, but the operator
5403 now needs to set "HiddenServiceVersion 2" in order to create a new
5404 version 2 service. For existing services, Tor now learns the
5405 version by reading the key file. Closes ticket 27215.
5407 o Major features (relay, UI change):
5408 - Relays no longer run as exits by default. If the "ExitRelay"
5409 option is auto (or unset), and no exit policy is specified with
5410 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
5411 Previously in this case, we allowed exit traffic and logged a
5412 warning message. Closes ticket 21530. Patch by Neel Chauhan.
5413 - Tor now validates that the ContactInfo config option is valid UTF-
5414 8 when parsing torrc. Closes ticket 27428.
5416 o Major features (bootstrap):
5417 - Don't report directory progress until after a connection to a
5418 relay or bridge has succeeded. Previously, we'd report 80%
5419 progress based on cached directory information when we couldn't
5420 even connect to the network. Closes ticket 27169.
5422 o Major features (new code layout):
5423 - Nearly all of Tor's source code has been moved around into more
5424 logical places. The "common" directory is now divided into a set
5425 of libraries in "lib", and files in the "or" directory have been
5426 split into "core" (logic absolutely needed for onion routing),
5427 "feature" (independent modules in Tor), and "app" (to configure
5428 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
5429 more information. Closes ticket 26481.
5431 This refactoring is not complete: although the libraries have been
5432 refactored to be acyclic, the main body of Tor is still too
5433 interconnected. We will attempt to improve this in the future.
5435 o Major features (onion services v3):
5436 - Implement onion service client authorization at the descriptor
5437 level: only authorized clients can decrypt a service's descriptor
5438 to find out how to contact it. A new torrc option was added to
5439 control this client side: ClientOnionAuthDir <path>. On the
5440 service side, if the "authorized_clients/" directory exists in the
5441 onion service directory path, client configurations are read from
5442 the files within. See the manpage for more details. Closes ticket
5443 27547. Patch done by Suphanat Chunhapanya (haxxpop).
5444 - Improve revision counter generation in next-gen onion services.
5445 Onion services can now scale by hosting multiple instances on
5446 different hosts without synchronization between them, which was
5447 previously impossible because descriptors would get rejected by
5448 HSDirs. Addresses ticket 25552.
5450 o Major features (portability, cryptography, experimental, TLS):
5451 - Tor now has the option to compile with the NSS library instead of
5452 OpenSSL. This feature is experimental, and we expect that bugs may
5453 remain. It is mainly intended for environments where Tor's
5454 performance is not CPU-bound, and where NSS is already known to be
5455 installed. To try it out, configure Tor with the --enable-nss
5456 flag. Closes tickets 26631, 26815, and 26816.
5458 If you are experimenting with this option and using an old cached
5459 consensus, Tor may fail to start. To solve this, delete your
5460 "cached-consensus" and "cached-microdesc-consensus" files,
5461 (if present), and restart Tor.
5463 o Major bugfixes (directory authority):
5464 - Actually check that the address we get from DirAuthority
5465 configuration line is valid IPv4. Explicitly disallow DirAuthority
5466 address to be a DNS hostname. Fixes bug 26488; bugfix
5469 o Major bugfixes (restart-in-process):
5470 - Fix a use-after-free error that could be caused by passing Tor an
5471 impossible set of options that would fail during options_act().
5472 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5474 o Minor features (admin tools):
5475 - Add a new --key-expiration option to print the expiration date of
5476 the signing cert in an ed25519_signing_cert file. Resolves
5479 o Minor features (build):
5480 - If you pass the "--enable-pic" option to configure, Tor will try
5481 to tell the compiler to build position-independent code suitable
5482 to link into a dynamic library. (The default remains -fPIE, for
5483 code suitable for a relocatable executable.) Closes ticket 23846.
5485 o Minor features (code correctness, testing):
5486 - Tor's build process now includes a "check-includes" make target to
5487 verify that no module of Tor relies on any headers from a higher-
5488 level module. We hope to use this feature over time to help
5489 refactor our codebase. Closes ticket 26447.
5491 o Minor features (code layout):
5492 - We have a new "lowest-level" error-handling API for use by code
5493 invoked from within the logging module. With this interface, the
5494 logging code is no longer at risk of calling into itself if a
5495 failure occurs while it is trying to log something. Closes
5498 o Minor features (compilation):
5499 - Tor's configure script now supports a --with-malloc= option to
5500 select your malloc implementation. Supported options are
5501 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
5502 default). Addresses part of ticket 20424. Based on a patch from
5505 o Minor features (config):
5506 - The "auto" keyword in torrc is now case-insensitive. Closes
5509 o Minor features (continuous integration):
5510 - Don't do a distcheck with --disable-module-dirauth in Travis.
5511 Implements ticket 27252.
5512 - Install libcap-dev and libseccomp2-dev so these optional
5513 dependencies get tested on Travis CI. Closes ticket 26560.
5514 - Only run one online rust build in Travis, to reduce network
5515 errors. Skip offline rust builds on Travis for Linux gcc, because
5516 they're redundant. Implements ticket 27252.
5517 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5518 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5519 Linux with default settings, because all the non-default builds
5520 use gcc on Linux. Implements ticket 27252.
5522 o Minor features (controller):
5523 - Emit CIRC_BW events as soon as we detect that we processed an
5524 invalid or otherwise dropped cell on a circuit. This allows
5525 vanguards and other controllers to react more quickly to dropped
5526 cells. Closes ticket 27678.
5527 - For purposes of CIRC_BW-based dropped cell detection, track half-
5528 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
5529 bias check cells to arrive without counting it as dropped until
5530 either the END arrives, or the windows are empty. Closes
5532 - Implement a 'GETINFO md/all' controller command to enable getting
5533 all known microdescriptors. Closes ticket 8323.
5534 - The GETINFO command now support an "uptime" argument, to return
5535 Tor's uptime in seconds. Closes ticket 25132.
5537 o Minor features (denial-of-service avoidance):
5538 - Make our OOM handler aware of the DNS cache so that it doesn't
5539 fill up the memory. This check is important for our DoS mitigation
5540 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
5542 o Minor features (development):
5543 - Tor's makefile now supports running the "clippy" Rust style tool
5544 on our Rust code. Closes ticket 22156.
5546 o Minor features (directory authority):
5547 - There is no longer an artificial upper limit on the length of
5548 bandwidth lines. Closes ticket 26223.
5549 - When a bandwidth file is used to obtain the bandwidth measurements,
5550 include this bandwidth file headers in the votes. Closes
5552 - Improved support for networks with only a single authority or a
5553 single fallback directory. Patch from Gabriel Somlo. Closes
5556 o Minor features (embedding API):
5557 - The Tor controller API now supports a function to launch Tor with
5558 a preconstructed owning controller FD, so that embedding
5559 applications don't need to manage controller ports and
5560 authentication. Closes ticket 24204.
5561 - The Tor controller API now has a function that returns the name
5562 and version of the backend implementing the API. Closes
5565 o Minor features (geoip):
5566 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
5567 Country database. Closes ticket 27631.
5569 o Minor features (memory management):
5570 - Get Libevent to use the same memory allocator as Tor, by calling
5571 event_set_mem_functions() during initialization. Resolves
5574 o Minor features (memory usage):
5575 - When not using them, store legacy TAP public onion keys in DER-
5576 encoded format, rather than as expanded public keys. This should
5577 save several megabytes on typical clients. Closes ticket 27246.
5579 o Minor features (OpenSSL):
5580 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
5581 than our own. Resolves ticket 19979.
5583 o Minor features (Rust, code quality):
5584 - Improve rust code quality in the rust protover implementation by
5585 making it more idiomatic. Includes changing an internal API to
5586 take &str instead of &String. Closes ticket 26492.
5588 o Minor features (testing):
5589 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
5590 chutney. Implements ticket 27211.
5592 o Minor features (tor-resolve):
5593 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
5594 Side-effect of the refactoring for ticket 26526.
5596 o Minor features (UI):
5597 - Log each included configuration file or directory as we read it,
5598 to provide more visibility about where Tor is reading from. Patch
5599 from Unto Sten; closes ticket 27186.
5600 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
5601 Closes ticket 26703.
5603 o Minor bugfixes (bootstrap):
5604 - Try harder to get descriptors in non-exit test networks, by using
5605 the mid weight for the third hop when there are no exits. Fixes
5606 bug 27237; bugfix on 0.2.6.2-alpha.
5608 o Minor bugfixes (C correctness):
5609 - Avoid casting smartlist index to int implicitly, as it may trigger
5610 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
5611 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
5612 - Use time_t for all values in
5613 predicted_ports_prediction_time_remaining(). Rework the code that
5614 computes difference between durations/timestamps. Fixes bug 27165;
5615 bugfix on 0.3.1.1-alpha.
5617 o Minor bugfixes (client, memory usage):
5618 - When not running as a directory cache, there is no need to store
5619 the text of the current consensus networkstatus in RAM.
5620 Previously, however, clients would store it anyway, at a cost of
5621 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
5624 o Minor bugfixes (client, reachableaddresses):
5625 - Instead of adding a "reject *:*" line to ReachableAddresses when
5626 loading the configuration, add one to the policy after parsing it
5627 in parse_reachable_addresses(). This prevents extra "reject *.*"
5628 lines from accumulating on reloads. Fixes bug 20874; bugfix on
5629 0.1.1.5-alpha. Patch by Neel Chauhan.
5631 o Minor bugfixes (code quality):
5632 - Rename sandbox_getaddrinfo() and other functions to no longer
5633 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
5634 bugfix on 0.2.7.1-alpha.
5636 o Minor bugfixes (configuration, Onion Services):
5637 - In rend_service_parse_port_config(), disallow any input to remain
5638 after address-port pair was parsed. This will catch address and
5639 port being whitespace-separated by mistake of the user. Fixes bug
5640 27044; bugfix on 0.2.9.10.
5642 o Minor bugfixes (continuous integration):
5643 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5644 27464; bugfix on 0.3.4.1-alpha.
5646 o Minor bugfixes (controller):
5647 - Consider all routerinfo errors other than "not a server" to be
5648 transient for the purpose of "GETINFO exit-policy/*" controller
5649 request. Print stacktrace in the unlikely case of failing to
5650 recompute routerinfo digest. Fixes bug 27034; bugfix
5653 o Minor bugfixes (directory connection shutdown):
5654 - Avoid a double-close when shutting down a stalled directory
5655 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5657 o Minor bugfixes (HTTP tunnel):
5658 - Fix a bug warning when closing an HTTP tunnel connection due to an
5659 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5662 o Minor bugfixes (ipv6):
5663 - In addrs_in_same_network_family(), we choose the subnet size based
5664 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
5665 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
5666 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
5668 o Minor bugfixes (logging):
5669 - As a precaution, do an early return from log_addr_has_changed() if
5670 Tor is running as client. Also, log a stack trace for debugging as
5671 this function should only be called when Tor runs as server. Fixes
5672 bug 26892; bugfix on 0.1.1.9-alpha.
5673 - Refrain from mentioning bug 21018 in the logs, as it is already
5674 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
5676 o Minor bugfixes (logging, documentation):
5677 - When SafeLogging is enabled, scrub IP address in
5678 channel_tls_process_netinfo_cell(). Also, add a note to manpage
5679 that scrubbing is not guaranteed on loglevels below Notice. Fixes
5680 bug 26882; bugfix on 0.2.4.10-alpha.
5682 o Minor bugfixes (netflow padding):
5683 - Ensure circuitmux queues are empty before scheduling or sending
5684 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5686 o Minor bugfixes (onion service v2):
5687 - Log at level "info", not "warning", in the case that we do not
5688 have a consensus when a .onion request comes in. This can happen
5689 normally while bootstrapping. Fixes bug 27040; bugfix
5692 o Minor bugfixes (onion service v3):
5693 - When the onion service directory can't be created or has the wrong
5694 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5697 o Minor bugfixes (OS compatibility):
5698 - Properly handle configuration changes that move a listener to/from
5699 wildcard IP address. If the first attempt to bind a socket fails,
5700 close the old listener and try binding the socket again. Fixes bug
5701 17873; bugfix on 0.0.8pre-1.
5703 o Minor bugfixes (performance)::
5704 - Rework node_is_a_configured_bridge() to no longer call
5705 node_get_all_orports(), which was performing too many memory
5706 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
5708 o Minor bugfixes (relay statistics):
5709 - Update relay descriptor on bandwidth changes only when the uptime
5710 is smaller than 24h, in order to reduce the efficiency of guard
5711 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5713 o Minor bugfixes (relays):
5714 - Consider the fact that we'll be making direct connections to our
5715 entry and guard nodes when computing the fraction of nodes that
5716 have their descriptors. Also, if we are using bridges and there is
5717 at least one bridge with a full descriptor, treat the fraction of
5718 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
5719 Patch by Neel Chauhan.
5720 - Update the message logged on relays when DirCache is disabled.
5721 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
5722 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
5724 o Minor bugfixes (rust, protover):
5725 - Compute protover votes correctly in the rust version of the
5726 protover code. Previously, the protover rewrite in 24031 allowed
5727 repeated votes from the same voter for the same protocol version
5728 to be counted multiple times in protover_compute_vote(). Fixes bug
5729 27649; bugfix on 0.3.3.5-rc.
5730 - Reject protover names that contain invalid characters. Fixes bug
5731 27687; bugfix on 0.3.3.1-alpha.
5733 o Minor bugfixes (testing):
5734 - Fix two unit tests to work when HOME environment variable is not
5735 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
5736 - If a unit test running in a subprocess exits abnormally or with a
5737 nonzero status code, treat the test as having failed, even if the
5738 test reported success. Without this fix, memory leaks don't cause
5739 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5740 bugfix on 0.2.2.4-alpha.
5741 - When logging a version mismatch in our openssl_version tests,
5742 report the actual offending version strings. Fixes bug 26152;
5743 bugfix on 0.2.9.1-alpha.
5744 - Fix forking tests on Windows when there is a space somewhere in
5745 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
5747 o Code simplification and refactoring:
5748 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
5749 longer needed. Closes ticket 26502.
5750 - Include paths to header files within Tor are now qualified by
5751 directory within the top-level src directory.
5752 - Many structures have been removed from the centralized "or.h"
5753 header, and moved into their own headers. This will allow us to
5754 reduce the number of places in the code that rely on each
5755 structure's contents and layout. Closes ticket 26383.
5756 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
5757 - Remove GetAdaptersAddresses_fn_t. The code that used it was
5758 removed as part of the 26481 refactor. Closes ticket 27467.
5759 - Rework Tor SOCKS server code to use Trunnel and benefit from
5760 autogenerated functions for parsing and generating SOCKS wire
5761 format. New implementation is cleaner, more maintainable and
5762 should be less prone to heartbleed-style vulnerabilities.
5763 Implements a significant fraction of ticket 3569.
5764 - Split sampled_guards_update_from_consensus() and
5765 select_entry_guard_for_circuit() into subfunctions. In
5766 entry_guards_update_primary() unite three smartlist enumerations
5767 into one and move smartlist comparison code out of the function.
5768 Closes ticket 21349.
5769 - Tor now assumes that you have standards-conformant stdint.h and
5770 inttypes.h headers when compiling. Closes ticket 26626.
5771 - Unify our bloom filter logic. Previously we had two copies of this
5772 code: one for routerlist filtering, and one for address set
5773 calculations. Closes ticket 26510.
5774 - Use the simpler strcmpstart() helper in
5775 rend_parse_v2_service_descriptor instead of strncmp(). Closes
5777 - Utility functions that can perform a DNS lookup are now wholly
5778 separated from those that can't, in separate headers and C
5779 modules. Closes ticket 26526.
5782 - Copy paragraph and URL to Tor's code of conduct document from
5783 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
5784 - Remove old instructions from INSTALL document. Closes ticket 26588.
5785 - Warn users that they should not include MyFamily line(s) in their
5786 torrc when running Tor bridge. Closes ticket 26908.
5789 - Tor no longer supports building with the dmalloc library. For
5790 debugging memory issues, we suggest using gperftools or msan
5791 instead. Closes ticket 26426.
5792 - Tor no longer attempts to run on Windows environments without the
5793 GetAdaptersAddresses() function. This function has existed since
5794 Windows XP, which is itself already older than we support.
5795 - Remove Tor2web functionality for version 2 onion services. The
5796 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
5797 (This feature was never shipped in vanilla Tor and it was only
5798 possible to use this feature by building the support at compile
5799 time. Tor2webMode is not implemented for version 3 onion services.)
5800 Closes ticket 26367.
5803 Changes in version 0.2.9.17 - 2018-09-10
5804 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
5806 o Minor features (compatibility, backport from 0.3.4.8):
5807 - Tell OpenSSL to maintain backward compatibility with previous
5808 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5809 ciphers are disabled by default. Closes ticket 27344.
5811 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5812 - Enable macOS builds in our Travis CI configuration. Closes
5814 - Install libcap-dev and libseccomp2-dev so these optional
5815 dependencies get tested on Travis CI. Closes ticket 26560.
5816 - Run asciidoc during Travis CI. Implements ticket 27087.
5817 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5819 o Minor features (geoip):
5820 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5821 Country database. Closes ticket 27089.
5823 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5824 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5825 tell the compiler not to include the system malloc implementation.
5826 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5828 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5829 - Silence a spurious compiler warning on the GetAdaptersAddresses
5830 function pointer cast. This issue is already fixed by 26481 in
5831 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5832 bugfix on 0.2.3.11-alpha.
5833 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5834 supported, and always fails. Some compilers warn about the
5835 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5838 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5839 - Don't link or search for pthreads when building for Windows, even
5840 if we are using build environment (like mingw) that provides a
5841 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5843 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5844 - Skip a pair of unreliable key generation tests on Windows, until
5845 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5846 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5848 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5849 - Pass the module flags to distcheck configure, and log the flags
5850 before running configure. (Backported to 0.2.9 and later as a
5851 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5853 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5854 - When a Travis build fails, and showing a log fails, keep trying to
5855 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5856 - When we use echo in Travis, don't pass a --flag as the first
5857 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5859 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5860 - When voting for recommended versions, make sure that all of the
5861 versions are well-formed and parsable. Fixes bug 26485; bugfix
5864 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5865 - Fix a bug in out sandboxing rules for the openat() syscall.
5866 Previously, no openat() call would be permitted, which would break
5867 filesystem operations on recent glibc versions. Fixes bug 25440;
5868 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5870 o Minor bugfixes (onion services, backport from 0.3.4.8):
5871 - Silence a spurious compiler warning in
5872 rend_client_send_introduction(). Fixes bug 27463; bugfix
5875 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5876 - Log a protocol warning when single onion services or Tor2web clients
5877 fail to authenticate direct connections to relays.
5878 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5880 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5881 - Disable core dumps in test_bt.sh, to avoid failures in "make
5882 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5884 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5885 - Before running make test-network-all, delete old logs and test
5886 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5889 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5890 - Our "tortls/cert_matches_key" unit test no longer relies on
5891 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5892 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5893 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5895 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5896 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5897 27185; bugfix on 0.2.2.2-alpha.
5900 Changes in version 0.3.2.12 - 2018-09-10
5901 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
5903 o Minor features (compatibility, backport from 0.3.4.8):
5904 - Tell OpenSSL to maintain backward compatibility with previous
5905 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5906 ciphers are disabled by default. Closes ticket 27344.
5908 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5909 - Enable macOS builds in our Travis CI configuration. Closes
5911 - Install libcap-dev and libseccomp2-dev so these optional
5912 dependencies get tested on Travis CI. Closes ticket 26560.
5913 - Run asciidoc during Travis CI. Implements ticket 27087.
5914 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5916 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5917 - Use cargo cache in our Travis CI configuration. Closes
5920 o Minor features (controller, backport from 0.3.4.6-rc):
5921 - The control port now exposes the list of HTTPTunnelPorts and
5922 ExtOrPorts via GETINFO net/listeners/httptunnel and
5923 net/listeners/extor respectively. Closes ticket 26647.
5925 o Minor features (directory authorities, backport from 0.3.4.7-rc):
5926 - Authorities no longer vote to make the subprotocol version
5927 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5928 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5930 o Minor features (geoip):
5931 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5932 Country database. Closes ticket 27089.
5934 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5935 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5936 tell the compiler not to include the system malloc implementation.
5937 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5938 - Don't try to use a pragma to temporarily disable the
5939 -Wunused-const-variable warning if the compiler doesn't support
5940 it. Fixes bug 26785; bugfix on 0.3.2.11.
5942 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5943 - Silence a spurious compiler warning on the GetAdaptersAddresses
5944 function pointer cast. This issue is already fixed by 26481 in
5945 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5946 bugfix on 0.2.3.11-alpha.
5947 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5948 supported, and always fails. Some compilers warn about the
5949 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5952 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5953 - Don't link or search for pthreads when building for Windows, even
5954 if we are using build environment (like mingw) that provides a
5955 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5957 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5958 - Skip a pair of unreliable key generation tests on Windows, until
5959 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5960 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5962 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5963 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5964 - Pass the module flags to distcheck configure, and log the flags
5965 before running configure. (Backported to 0.2.9 and later as a
5966 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5968 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5969 - When a Travis build fails, and showing a log fails, keep trying to
5970 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5971 - When we use echo in Travis, don't pass a --flag as the first
5972 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5974 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5975 - When voting for recommended versions, make sure that all of the
5976 versions are well-formed and parsable. Fixes bug 26485; bugfix
5979 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5980 - Fix a bug in out sandboxing rules for the openat() syscall.
5981 Previously, no openat() call would be permitted, which would break
5982 filesystem operations on recent glibc versions. Fixes bug 25440;
5983 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5985 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
5986 - Improve the log message when connection initiators fail to
5987 authenticate direct connections to relays. Fixes bug 26927; bugfix
5990 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
5991 - Fix bug that causes services to not ever rotate their descriptors
5992 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5995 o Minor bugfixes (onion services, backport from 0.3.4.8):
5996 - Silence a spurious compiler warning in
5997 rend_client_send_introduction(). Fixes bug 27463; bugfix
6000 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6001 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6003 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6004 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6005 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6006 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6008 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6009 - Log a protocol warning when single onion services or Tor2web clients
6010 fail to authenticate direct connections to relays.
6011 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6013 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6014 - Disable core dumps in test_bt.sh, to avoid failures in "make
6015 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6017 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6018 - When running make test-network-all, use the mixed+hs-v2 network.
6019 (A previous fix to chutney removed v3 onion services from the
6020 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6021 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6022 - Before running make test-network-all, delete old logs and test
6023 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6026 o Minor bugfixes (testing, openssl compatibility):
6027 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
6028 internals. Previously, it relied on unsupported OpenSSL behavior in
6029 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
6030 bugfix on 0.2.5.1-alpha.
6032 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6033 - Our "tortls/cert_matches_key" unit test no longer relies on
6034 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6035 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6036 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6038 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6039 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6040 27185; bugfix on 0.2.2.2-alpha.
6043 Changes in version 0.3.3.10 - 2018-09-10
6044 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
6046 o Minor features (bug workaround, backport from 0.3.4.7-rc):
6047 - Compile correctly on systems that provide the C11 stdatomic.h
6048 header, but where C11 atomic functions don't actually compile.
6049 Closes ticket 26779; workaround for Debian issue 903709.
6051 o Minor features (compatibility, backport from 0.3.4.8):
6052 - Tell OpenSSL to maintain backward compatibility with previous
6053 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6054 ciphers are disabled by default. Closes ticket 27344.
6056 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6057 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6058 - Enable macOS builds in our Travis CI configuration. Closes
6060 - Install libcap-dev and libseccomp2-dev so these optional
6061 dependencies get tested on Travis CI. Closes ticket 26560.
6062 - Run asciidoc during Travis CI. Implements ticket 27087.
6063 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6065 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6066 - Use cargo cache in our Travis CI configuration. Closes
6069 o Minor features (controller, backport from 0.3.4.6-rc):
6070 - The control port now exposes the list of HTTPTunnelPorts and
6071 ExtOrPorts via GETINFO net/listeners/httptunnel and
6072 net/listeners/extor respectively. Closes ticket 26647.
6074 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6075 - Authorities no longer vote to make the subprotocol version
6076 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6077 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6079 o Minor features (geoip):
6080 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6081 Country database. Closes ticket 27089.
6083 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6084 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6085 tell the compiler not to include the system malloc implementation.
6086 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6087 - Don't try to use a pragma to temporarily disable the
6088 -Wunused-const-variable warning if the compiler doesn't support
6089 it. Fixes bug 26785; bugfix on 0.3.2.11.
6091 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6092 - Silence a spurious compiler warning on the GetAdaptersAddresses
6093 function pointer cast. This issue is already fixed by 26481 in
6094 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6095 bugfix on 0.2.3.11-alpha.
6096 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6097 supported, and always fails. Some compilers warn about the
6098 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6101 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6102 - Don't link or search for pthreads when building for Windows, even
6103 if we are using build environment (like mingw) that provides a
6104 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6106 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6107 - Skip a pair of unreliable key generation tests on Windows, until
6108 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6109 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6111 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6112 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6113 - Pass the module flags to distcheck configure, and log the flags
6114 before running configure. (Backported to 0.2.9 and later as a
6115 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6117 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6118 - When a Travis build fails, and showing a log fails, keep trying to
6119 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6120 - When we use echo in Travis, don't pass a --flag as the first
6121 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6123 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6124 - When voting for recommended versions, make sure that all of the
6125 versions are well-formed and parsable. Fixes bug 26485; bugfix
6128 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
6129 - Always call tor_free_all() when leaving tor_run_main(). When we
6130 did not, restarting tor in-process would cause an assertion
6131 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6133 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6134 - Fix a bug in our sandboxing rules for the openat() syscall.
6135 Previously, no openat() call would be permitted, which would break
6136 filesystem operations on recent glibc versions. Fixes bug 25440;
6137 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6139 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6140 - Improve the log message when connection initiators fail to
6141 authenticate direct connections to relays. Fixes bug 26927; bugfix
6144 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6145 - Fix bug that causes services to not ever rotate their descriptors
6146 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6149 o Minor bugfixes (onion services, backport from 0.3.4.8):
6150 - Silence a spurious compiler warning in
6151 rend_client_send_introduction(). Fixes bug 27463; bugfix
6154 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
6155 - Work around two different bugs in the OS X 10.10 and later SDKs
6156 that would prevent us from successfully targeting earlier versions
6157 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6159 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
6160 - Fix compilation of the unit tests on GNU/Hurd, which does not
6161 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6164 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6165 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6167 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6168 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6169 - Protover parsing was accepting the presence of whitespace in
6170 version strings, which the C implementation would choke on, e.g.
6171 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6172 - Protover parsing was ignoring a 2nd hyphen and everything after
6173 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6175 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6176 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6177 - cd to ${abs_top_builddir}/src/rust before running cargo in
6178 src/test/test_rust.sh. This makes the working directory consistent
6179 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6181 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6182 - Log a protocol warning when single onion services or Tor2web clients
6183 fail to authenticate direct connections to relays.
6184 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6186 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6187 - Disable core dumps in test_bt.sh, to avoid failures in "make
6188 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6190 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6191 - When running make test-network-all, use the mixed+hs-v2 network.
6192 (A previous fix to chutney removed v3 onion services from the
6193 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6194 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6195 - Before running make test-network-all, delete old logs and test
6196 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6199 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6200 - Our "tortls/cert_matches_key" unit test no longer relies on
6201 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6202 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6203 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6205 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
6206 - Stop sending ed25519 link specifiers in v3 onion service introduce
6207 cells and descriptors, when the rendezvous or introduction point
6208 doesn't support ed25519 link authentication. Fixes bug 26627;
6209 bugfix on 0.3.2.4-alpha.
6211 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6212 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6213 27185; bugfix on 0.2.2.2-alpha.
6216 Changes in version 0.3.4.8 - 2018-09-10
6217 Tor 0.3.4.8 is the first stable release in its series; it includes
6218 compilation and portability fixes.
6220 The Tor 0.3.4 series includes improvements for running Tor in
6221 low-power and embedded environments, which should help performance in
6222 general. We've begun work on better modularity, and included preliminary
6223 changes on the directory authority side to accommodate a new bandwidth
6224 measurement system. We've also integrated more continuous-integration
6225 systems into our development process, and made corresponding changes to
6226 Tor's testing infrastructure. Finally, we've continued to refine
6227 our anti-denial-of-service code.
6229 Below are the changes since 0.3.4.7-rc. For a complete list of changes
6230 since 0.3.3.9, see the ReleaseNotes file.
6232 o Minor features (compatibility):
6233 - Tell OpenSSL to maintain backward compatibility with previous
6234 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6235 ciphers are disabled by default. Closes ticket 27344.
6237 o Minor features (continuous integration):
6238 - Log the compiler path and version during Appveyor builds.
6239 Implements ticket 27449.
6240 - Show config.log and test-suite.log after failed Appveyor builds.
6241 Also upload the zipped full logs as a build artifact. Implements
6244 o Minor bugfixes (compilation):
6245 - Silence a spurious compiler warning on the GetAdaptersAddresses
6246 function pointer cast. This issue is already fixed by 26481 in
6247 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6248 bugfix on 0.2.3.11-alpha.
6249 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6250 supported, and always fails. Some compilers warn about the
6251 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6254 o Minor bugfixes (continuous integration):
6255 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
6256 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
6257 Executables compiled for 64-bit Windows with this version of gcc
6258 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
6259 27460; bugfix on 0.3.4.1-alpha.
6260 - When a Travis build fails, and showing a log fails, keep trying to
6261 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6262 - When we use echo in Travis, don't pass a --flag as the first
6263 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6265 o Minor bugfixes (onion services):
6266 - Silence a spurious compiler warning in
6267 rend_client_send_introduction(). Fixes bug 27463; bugfix
6270 o Minor bugfixes (testing, chutney):
6271 - When running make test-network-all, use the mixed+hs-v2 network.
6272 (A previous fix to chutney removed v3 onion services from the
6273 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6274 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6275 - Before running make test-network-all, delete old logs and test
6276 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6279 Changes in version 0.3.4.7-rc - 2018-08-24
6280 Tor 0.3.4.7-rc fixes several small compilation, portability, and
6281 correctness issues in previous versions of Tor. This version is a
6282 release candidate: if no serious bugs are found, we expect that the
6283 stable 0.3.4 release will be (almost) the same as this release.
6285 o Minor features (bug workaround):
6286 - Compile correctly on systems that provide the C11 stdatomic.h
6287 header, but where C11 atomic functions don't actually compile.
6288 Closes ticket 26779; workaround for Debian issue 903709.
6290 o Minor features (continuous integration):
6291 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6292 - Enable macOS builds in our Travis CI configuration. Closes
6294 - Install libcap-dev and libseccomp2-dev so these optional
6295 dependencies get tested on Travis CI. Closes ticket 26560.
6296 - Only post Appveyor IRC notifications when the build fails.
6297 Implements ticket 27275.
6298 - Run asciidoc during Travis CI. Implements ticket 27087.
6299 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6301 o Minor features (continuous integration, rust):
6302 - Use cargo cache in our Travis CI configuration. Closes
6305 o Minor features (directory authorities):
6306 - Authorities no longer vote to make the subprotocol version
6307 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6308 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6310 o Minor features (geoip):
6311 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6312 Country database. Closes ticket 27089.
6314 o Minor bugfixes (compilation, windows):
6315 - Don't link or search for pthreads when building for Windows, even
6316 if we are using build environment (like mingw) that provides a
6317 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6319 o Minor bugfixes (continuous integration):
6320 - Improve Appveyor CI IRC logging. Generate correct branches and
6321 URLs for pull requests and tags. Use unambiguous short commits.
6322 Fixes bug 26979; bugfix on master.
6323 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6324 - Pass the module flags to distcheck configure, and log the flags
6325 before running configure. (Backported to 0.2.9 and later as a
6326 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6328 o Minor bugfixes (in-process restart):
6329 - Always call tor_free_all() when leaving tor_run_main(). When we
6330 did not, restarting tor in-process would cause an assertion
6331 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6333 o Minor bugfixes (linux seccomp2 sandbox):
6334 - Fix a bug in out sandboxing rules for the openat() syscall.
6335 Previously, no openat() call would be permitted, which would break
6336 filesystem operations on recent glibc versions. Fixes bug 25440;
6337 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6339 o Minor bugfixes (onion services):
6340 - Fix bug that causes services to not ever rotate their descriptors
6341 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6344 o Minor bugfixes (portability):
6345 - Fix compilation of the unit tests on GNU/Hurd, which does not
6346 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6349 o Minor bugfixes (rust):
6350 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6352 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6353 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6354 - Protover parsing was accepting the presence of whitespace in
6355 version strings, which the C implementation would choke on, e.g.
6356 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6357 - Protover parsing was ignoring a 2nd hyphen and everything after
6358 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6360 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6361 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6362 - cd to ${abs_top_builddir}/src/rust before running cargo in
6363 src/test/test_rust.sh. This makes the working directory consistent
6364 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6366 o Minor bugfixes (testing, bootstrap):
6367 - When calculating bootstrap progress, check exit policies and the
6368 exit flag. Previously, Tor would only check the exit flag, which
6369 caused race conditions in small and fast networks like chutney.
6370 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
6372 o Minor bugfixes (testing, openssl compatibility):
6373 - Our "tortls/cert_matches_key" unit test no longer relies on
6374 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6375 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6376 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6378 o Minor bugfixes (Windows, compilation):
6379 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6380 27185; bugfix on 0.2.2.2-alpha.
6383 Changes in version 0.3.4.6-rc - 2018-08-06
6384 Tor 0.3.4.6-rc fixes several small compilation, portability, and
6385 correctness issues in previous versions of Tor. This version is a
6386 release candidate: if no serious bugs are found, we expect that the
6387 stable 0.3.4 release will be (almost) the same as this release.
6389 o Major bugfixes (event scheduler):
6390 - When we enable a periodic event, schedule it in the event loop
6391 rather than running it immediately. Previously, we would re-run
6392 periodic events immediately in the middle of (for example)
6393 changing our options, with unpredictable effects. Fixes bug 27003;
6394 bugfix on 0.3.4.1-alpha.
6396 o Minor features (compilation):
6397 - When building Tor, prefer to use Python 3 over Python 2, and more
6398 recent (contemplated) versions over older ones. Closes
6400 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6401 tell the compiler not to include the system malloc implementation.
6402 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6403 - Don't try to use a pragma to temporarily disable the
6404 -Wunused-const-variable warning if the compiler doesn't support
6405 it. Fixes bug 26785; bugfix on 0.3.2.11.
6407 o Minor bugfixes (continuous integration):
6408 - Skip a pair of unreliable key generation tests on Windows, until
6409 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6410 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6412 o Minor features (controller):
6413 - The control port now exposes the list of HTTPTunnelPorts and
6414 ExtOrPorts via GETINFO net/listeners/httptunnel and
6415 net/listeners/extor respectively. Closes ticket 26647.
6417 o Minor bugfixes (directory authority):
6418 - When voting for recommended versions, make sure that all of the
6419 versions are well-formed and parsable. Fixes bug 26485; bugfix
6422 o Minor features (geoip):
6423 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6424 Country database. Closes ticket 26674.
6426 o Minor features (Rust, portability):
6427 - Rust cross-compilation is now supported. Closes ticket 25895.
6429 o Minor bugfixes (compilation):
6430 - Update build system so that tor builds again with --disable-unittests
6431 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
6432 - Fix a compilation warning on some versions of GCC when building
6433 code that calls routerinfo_get_my_routerinfo() twice, assuming
6434 that the second call will succeed if the first one did. Fixes bug
6435 26269; bugfix on 0.2.8.2-alpha.
6437 o Minor bugfixes (controller):
6438 - Report the port correctly when a port is configured to bind to
6439 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
6440 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
6441 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
6442 on 0.3.3.1-alpha. Patch by "akwizgran".
6444 o Minor bugfixes (correctness, flow control):
6445 - Upon receiving a stream-level SENDME cell, verify that our window
6446 has not grown too large. Fixes bug 26214; bugfix on svn
6449 o Minor bugfixes (memory, correctness):
6450 - Fix a number of small memory leaks identified by coverity. Fixes
6451 bug 26467; bugfix on numerous Tor versions.
6453 o Minor bugfixes (logging):
6454 - Improve the log message when connection initiators fail to
6455 authenticate direct connections to relays. Fixes bug 26927; bugfix
6458 o Minor bugfixes (portability):
6459 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
6460 26994; bugfix on 0.3.4.1-alpha.
6461 - Work around two different bugs in the OS X 10.10 and later SDKs
6462 that would prevent us from successfully targeting earlier versions
6463 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6465 o Minor bugfixes (single onion services, Tor2web):
6466 - Log a protocol warning when single onion services or Tor2web
6467 clients fail to authenticate direct connections to relays. Fixes
6468 bug 26924; bugfix on 0.2.9.1-alpha.
6470 o Minor bugfixes (testing):
6471 - Disable core dumps in test_bt.sh, to avoid failures in "make
6472 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6474 o Minor bugfixes (testing, compatibility):
6475 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
6476 only to pass strings (rather than "bytes" objects) to the Python
6477 subprocess module. Python 3 on Windows seems to require this.
6478 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
6479 0.3.1.1-alpha (for hs_ntor_ref.py).
6481 o Minor bugfixes (v3 onion services):
6482 - Stop sending ed25519 link specifiers in v3 onion service introduce
6483 cells and descriptors, when the rendezvous or introduction point
6484 doesn't support ed25519 link authentication. Fixes bug 26627;
6485 bugfix on 0.3.2.4-alpha.
6488 Changes in version 0.3.4.5-rc - 2018-07-13
6489 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
6490 bridge relays should upgrade.
6492 o Directory authority changes:
6493 - The "Bifroest" bridge authority has been retired; the new bridge
6494 authority is "Serge", and it is operated by George from the
6495 TorBSD project. Closes ticket 26771.
6498 Changes in version 0.3.3.9 - 2018-07-13
6499 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
6500 bridge relays should upgrade.
6502 o Directory authority changes:
6503 - The "Bifroest" bridge authority has been retired; the new bridge
6504 authority is "Serge", and it is operated by George from the
6505 TorBSD project. Closes ticket 26771.
6508 Changes in version 0.3.2.11 - 2018-07-13
6509 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
6510 bridge relays should upgrade. We also take this opportunity to backport
6513 o Directory authority changes:
6514 - The "Bifroest" bridge authority has been retired; the new bridge
6515 authority is "Serge", and it is operated by George from the
6516 TorBSD project. Closes ticket 26771.
6518 o Directory authority changes (backport from 0.3.3.7):
6519 - Add an IPv6 address for the "dannenberg" directory authority.
6520 Closes ticket 26343.
6522 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6523 - When directory authorities read a zero-byte bandwidth file, they
6524 would previously log a warning with the contents of an
6525 uninitialised buffer. They now log a warning about the empty file
6526 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6528 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6529 - Correctly detect when onion services get disabled after HUP. Fixes
6530 bug 25761; bugfix on 0.3.2.1.
6532 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6533 - Explicitly permit the poll() system call when the Linux
6534 seccomp2-based sandbox is enabled: apparently, some versions of
6535 libc use poll() when calling getpwnam(). Closes ticket 25313.
6537 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
6538 - Update the Travis CI configuration to use the stable Rust channel,
6539 now that we have decided to require that. Closes ticket 25714.
6541 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6542 - Our .travis.yml configuration now includes support for testing the
6543 results of "make distcheck". (It's not uncommon for "make check"
6544 to pass but "make distcheck" to fail.) Closes ticket 25814.
6545 - Our Travis CI configuration now integrates with the Coveralls
6546 coverage analysis tool. Closes ticket 25818.
6548 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6549 - Add several checks to detect whether Tor relays are uploading
6550 their descriptors without specifying why they regenerated them.
6551 Diagnostic for ticket 25686.
6553 o Minor features (compilation, backport from 0.3.4.4-rc):
6554 - When building Tor, prefer to use Python 3 over Python 2, and more
6555 recent (contemplated) versions over older ones. Closes
6558 o Minor features (geoip):
6559 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6560 Country database. Closes ticket 26674.
6562 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6563 - Upon receiving a malformed connected cell, stop processing the
6564 cell immediately. Previously we would mark the connection for
6565 close, but continue processing the cell as if the connection were
6566 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6568 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6569 - Allow the nanosleep() system call, which glibc uses to implement
6570 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6572 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6573 - When running the hs_ntor_ref.py test, make sure only to pass
6574 strings (rather than "bytes" objects) to the Python subprocess
6575 module. Python 3 on Windows seems to require this. Fixes bug
6576 26535; bugfix on 0.3.1.1-alpha.
6577 - When running the ntor_ref.py test, make sure only to pass strings
6578 (rather than "bytes" objects) to the Python subprocess module.
6579 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6582 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6583 - Work around a change in OpenSSL 1.1.1 where return values that
6584 would previously indicate "no password" now indicate an empty
6585 password. Without this workaround, Tor instances running with
6586 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6587 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6589 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
6590 - Document that the PerConnBW{Rate,Burst} options will fall back to
6591 their corresponding consensus parameters only if those parameters
6592 are set. Previously we had claimed that these values would always
6593 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
6595 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6596 - Fix a compilation warning on some versions of GCC when building
6597 code that calls routerinfo_get_my_routerinfo() twice, assuming
6598 that the second call will succeed if the first one did. Fixes bug
6599 26269; bugfix on 0.2.8.2-alpha.
6601 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6602 - Don't consider Tor running as a client if the ControlPort is open,
6603 but no actual client ports are open. Fixes bug 26062; bugfix
6606 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6607 - Prevent a possible out-of-bounds smartlist read in
6608 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6610 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6611 - Fix a very unlikely (impossible, we believe) null pointer
6612 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6613 Coverity; this is CID 1430932.
6615 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6616 - Fix a memory leak when a v3 onion service is configured and gets a
6617 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6618 - When parsing the descriptor signature, look for the token plus an
6619 extra white-space at the end. This is more correct but also will
6620 allow us to support new fields that might start with "signature".
6621 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6623 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6624 - Relays now correctly block attempts to re-extend to the previous
6625 relay by Ed25519 identity. Previously they would warn in this
6626 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6629 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6630 - Avoid a crash when running with DirPort set but ORPort turned off.
6631 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6633 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6634 - Silence unused-const-variable warnings in zstd.h with some GCC
6635 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6637 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
6638 - Avoid intermittent test failures due to a test that had relied on
6639 onion service introduction point creation finishing within 5
6640 seconds of real clock time. Fixes bug 25450; bugfix
6643 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
6644 - Fix a C99 compliance issue in our configuration script that caused
6645 compilation issues when compiling Tor with certain versions of
6646 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
6648 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6649 - Fix a number of small memory leaks identified by coverity. Fixes
6650 bug 26467; bugfix on numerous Tor versions.
6652 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6653 - Move the list of default directory authorities to its own file.
6654 Closes ticket 24854. Patch by "beastr0".
6657 Changes in version 0.2.9.16 - 2018-07-13
6658 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
6659 bridge relays should upgrade. We also take this opportunity to backport
6662 o Directory authority changes:
6663 - The "Bifroest" bridge authority has been retired; the new bridge
6664 authority is "Serge", and it is operated by George from the
6665 TorBSD project. Closes ticket 26771.
6667 o Directory authority changes (backport from 0.3.3.7):
6668 - Add an IPv6 address for the "dannenberg" directory authority.
6669 Closes ticket 26343.
6671 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6672 - When directory authorities read a zero-byte bandwidth file, they
6673 would previously log a warning with the contents of an
6674 uninitialised buffer. They now log a warning about the empty file
6675 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6677 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6678 - Explicitly permit the poll() system call when the Linux
6679 seccomp2-based sandbox is enabled: apparently, some versions of
6680 libc use poll() when calling getpwnam(). Closes ticket 25313.
6682 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6683 - Our .travis.yml configuration now includes support for testing the
6684 results of "make distcheck". (It's not uncommon for "make check"
6685 to pass but "make distcheck" to fail.) Closes ticket 25814.
6686 - Our Travis CI configuration now integrates with the Coveralls
6687 coverage analysis tool. Closes ticket 25818.
6689 o Minor features (compilation, backport from 0.3.4.4-rc):
6690 - When building Tor, prefer to use Python 3 over Python 2, and more
6691 recent (contemplated) versions over older ones. Closes
6694 o Minor features (geoip):
6695 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6696 Country database. Closes ticket 26674.
6698 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6699 - Upon receiving a malformed connected cell, stop processing the
6700 cell immediately. Previously we would mark the connection for
6701 close, but continue processing the cell as if the connection were
6702 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6704 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6705 - Allow the nanosleep() system call, which glibc uses to implement
6706 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6708 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6709 - When running the ntor_ref.py test, make sure only to pass strings
6710 (rather than "bytes" objects) to the Python subprocess module.
6711 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6714 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6715 - Work around a change in OpenSSL 1.1.1 where return values that
6716 would previously indicate "no password" now indicate an empty
6717 password. Without this workaround, Tor instances running with
6718 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6719 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6721 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6722 - Fix a compilation warning on some versions of GCC when building
6723 code that calls routerinfo_get_my_routerinfo() twice, assuming
6724 that the second call will succeed if the first one did. Fixes bug
6725 26269; bugfix on 0.2.8.2-alpha.
6727 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6728 - Don't consider Tor running as a client if the ControlPort is open,
6729 but no actual client ports are open. Fixes bug 26062; bugfix
6732 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6733 - Prevent a possible out-of-bounds smartlist read in
6734 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6736 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6737 - Fix a very unlikely (impossible, we believe) null pointer
6738 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6739 Coverity; this is CID 1430932.
6741 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6742 - Fix a number of small memory leaks identified by coverity. Fixes
6743 bug 26467; bugfix on numerous Tor versions.
6745 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6746 - Move the list of default directory authorities to its own file.
6747 Closes ticket 24854. Patch by "beastr0".
6750 Changes in version 0.3.4.4-rc - 2018-07-09
6751 Tor 0.3.4.4-rc fixes several small compilation, portability, and
6752 correctness issues in previous versions of Tor. This version is a
6753 release candidate: if no serious bugs are found, we expect that the
6754 stable 0.3.4 release will be (almost) the same as this release.
6756 o Minor features (compilation):
6757 - When building Tor, prefer to use Python 3 over Python 2, and more
6758 recent (contemplated) versions over older ones. Closes
6761 o Minor features (geoip):
6762 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6763 Country database. Closes ticket 26674.
6765 o Minor features (Rust, portability):
6766 - Rust cross-compilation is now supported. Closes ticket 25895.
6768 o Minor bugfixes (compilation):
6769 - Fix a compilation warning on some versions of GCC when building
6770 code that calls routerinfo_get_my_routerinfo() twice, assuming
6771 that the second call will succeed if the first one did. Fixes bug
6772 26269; bugfix on 0.2.8.2-alpha.
6774 o Minor bugfixes (control port):
6775 - Report the port correctly when a port is configured to bind to
6776 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
6777 - Handle the HSADDRESS= argument to the HSPOST command properly.
6778 (Previously, this argument was misparsed and thus ignored.) Fixes
6779 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6781 o Minor bugfixes (correctness, flow control):
6782 - Upon receiving a stream-level SENDME cell, verify that our window
6783 has not grown too large. Fixes bug 26214; bugfix on svn
6786 o Minor bugfixes (memory, correctness):
6787 - Fix a number of small memory leaks identified by coverity. Fixes
6788 bug 26467; bugfix on numerous Tor versions.
6790 o Minor bugfixes (testing, compatibility):
6791 - When running the hs_ntor_ref.py test, make sure only to pass
6792 strings (rather than "bytes" objects) to the Python subprocess
6793 module. Python 3 on Windows seems to require this. Fixes bug
6794 26535; bugfix on 0.3.1.1-alpha.
6795 - When running the ntor_ref.py test, make sure only to pass strings
6796 (rather than "bytes" objects) to the Python subprocess module.
6797 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6801 Changes in version 0.3.3.8 - 2018-07-09
6802 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
6803 fixes for a memory leak affecting directory authorities.
6805 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
6806 - Stop leaking memory on directory authorities when planning to
6807 vote. This bug was crashing authorities by exhausting their
6808 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6810 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
6811 - Make sure that failing tests in Rust will actually cause the build
6812 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6815 o Minor features (compilation, backport from 0.3.4.4-rc):
6816 - When building Tor, prefer to use Python 3 over Python 2, and more
6817 recent (contemplated) versions over older ones. Closes
6820 o Minor features (geoip):
6821 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6822 Country database. Closes ticket 26674.
6824 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6825 - Add several checks to detect whether Tor relays are uploading
6826 their descriptors without specifying why they regenerated them.
6827 Diagnostic for ticket 25686.
6829 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
6830 - Don't count path selection failures as circuit build failures.
6831 This change should eliminate cases where Tor blames its guard or
6832 the network for situations like insufficient microdescriptors
6833 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
6836 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6837 - Fix a compilation warning on some versions of GCC when building
6838 code that calls routerinfo_get_my_routerinfo() twice, assuming
6839 that the second call will succeed if the first one did. Fixes bug
6840 26269; bugfix on 0.2.8.2-alpha.
6842 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
6843 - Handle the HSADDRESS= argument to the HSPOST command properly.
6844 (Previously, this argument was misparsed and thus ignored.) Fixes
6845 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6847 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6848 - Fix a number of small memory leaks identified by coverity. Fixes
6849 bug 26467; bugfix on numerous Tor versions.
6851 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6852 - Relays now correctly block attempts to re-extend to the previous
6853 relay by Ed25519 identity. Previously they would warn in this
6854 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6857 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
6858 - When shutting down, Tor now clears all the flags in the control.c
6859 module. This should prevent a bug where authentication cookies are
6860 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
6862 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6863 - When running the hs_ntor_ref.py test, make sure only to pass
6864 strings (rather than "bytes" objects) to the Python subprocess
6865 module. Python 3 on Windows seems to require this. Fixes bug
6866 26535; bugfix on 0.3.1.1-alpha.
6867 - When running the ntor_ref.py test, make sure only to pass strings
6868 (rather than "bytes" objects) to the Python subprocess module.
6869 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6873 Changes in version 0.3.4.3-alpha - 2018-06-26
6874 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
6875 one that was causing stability issues on directory authorities.
6877 o Major bugfixes (directory authority):
6878 - Stop leaking memory on directory authorities when planning to
6879 vote. This bug was crashing authorities by exhausting their
6880 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6882 o Major bugfixes (rust, testing):
6883 - Make sure that failing tests in Rust will actually cause the build
6884 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6887 o Minor feature (directory authorities):
6888 - Stop warning about incomplete bw lines before the first complete
6889 bw line has been found, so that additional header lines can be
6890 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
6892 o Minor features (relay, diagnostic):
6893 - Add several checks to detect whether Tor relays are uploading
6894 their descriptors without specifying why they regenerated them.
6895 Diagnostic for ticket 25686.
6897 o Minor features (unit tests):
6898 - Test complete bandwidth measurements files, and test that
6899 incomplete bandwidth lines only give warnings when the end of the
6900 header has not been detected. Fixes bug 25947; bugfix
6903 o Minor bugfixes (compilation):
6904 - Refrain from compiling unit testing related object files when
6905 --disable-unittests is set to configure script. Fixes bug 24891;
6906 bugfix on 0.2.5.1-alpha.
6907 - When linking the libtor_testing.a library, only include the
6908 dirauth object files once. Previously, they were getting added
6909 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
6910 - The --enable-fatal-warnings flag now affects Rust code as well.
6911 Closes ticket 26245.
6913 o Minor bugfixes (onion services):
6914 - Recompute some consensus information after detecting a clock jump,
6915 or after transitioning from a non-live consensus to a live
6916 consensus. We do this to avoid having an outdated state, and
6917 miscalculating the index for next-generation onion services. Fixes
6918 bug 24977; bugfix on 0.3.2.1-alpha.
6920 o Minor bugfixes (relay):
6921 - Relays now correctly block attempts to re-extend to the previous
6922 relay by Ed25519 identity. Previously they would warn in this
6923 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6926 o Minor bugfixes (testing):
6927 - Fix compilation of the doctests in the Rust crypto crate. Fixes
6928 bug 26415; bugfix on 0.3.4.1-alpha.
6929 - Instead of trying to read the geoip configuration files from
6930 within the unit tests, instead create our own ersatz files with
6931 just enough geoip data in the format we expect. Trying to read
6932 from the source directory created problems on Windows with mingw,
6933 where the build system's paths are not the same as the platform's
6934 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
6935 - Refrain from trying to get an item from an empty smartlist in
6936 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
6937 to catch improper smartlist usage. Furthermore, enable
6938 DEBUG_SMARTLIST globally when build is configured with fragile
6939 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
6942 Changes in version 0.3.3.7 - 2018-06-12
6943 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
6944 fixes for bugs affecting compatibility and stability.
6946 o Directory authority changes:
6947 - Add an IPv6 address for the "dannenberg" directory authority.
6948 Closes ticket 26343.
6950 o Minor features (geoip):
6951 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
6952 Country database. Closes ticket 26351.
6954 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6955 - Work around a change in OpenSSL 1.1.1 where return values that
6956 would previously indicate "no password" now indicate an empty
6957 password. Without this workaround, Tor instances running with
6958 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6959 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6961 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6962 - Silence unused-const-variable warnings in zstd.h with some GCC
6963 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6965 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
6966 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
6967 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
6968 miscounting the total number of circuits for these field values.)
6969 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
6971 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6972 - Prevent a possible out-of-bounds smartlist read in
6973 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6975 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
6976 - Only select relays when they have the descriptors we prefer to use
6977 for them. This change fixes a bug where we could select a relay
6978 because it had _some_ descriptor, but reject it later with a
6979 nonfatal assertion error because it didn't have the exact one we
6980 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
6983 Changes in version 0.3.4.2-alpha - 2018-06-12
6984 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
6985 release, and forward-ports an authority-only security fix from 0.3.3.6.
6987 o Directory authority changes:
6988 - Add an IPv6 address for the "dannenberg" directory authority.
6989 Closes ticket 26343.
6991 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
6992 - Fix a bug that could have allowed an attacker to force a directory
6993 authority to use up all its RAM by passing it a maliciously
6994 crafted protocol versions string. Fixes bug 25517; bugfix on
6995 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
6997 o Minor features (continuous integration):
6998 - Add the necessary configuration files for continuous integration
6999 testing on Windows, via the Appveyor platform. Closes ticket
7000 25549. Patches from Marcin Cieślak and Isis Lovecruft.
7002 o Minor features (geoip):
7003 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
7004 Country database. Closes ticket 26351.
7006 o Minor bugfixes (compatibility, openssl):
7007 - Work around a change in OpenSSL 1.1.1 where return values that
7008 would previously indicate "no password" now indicate an empty
7009 password. Without this workaround, Tor instances running with
7010 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7011 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7013 o Minor bugfixes (compilation):
7014 - Silence unused-const-variable warnings in zstd.h with some GCC
7015 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7016 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
7017 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
7018 - Avoid a compiler warning when casting the return value of
7019 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
7020 26283; bugfix on 0.2.4.10-alpha.
7022 o Minor bugfixes (control port):
7023 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
7024 CIRC_BW events. Previously, such cells were counted entirely in
7025 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
7028 o Minor bugfixes (controller):
7029 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
7030 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
7031 miscounting the total number of circuits for these field values.)
7032 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
7034 o Minor bugfixes (hardening):
7035 - Prevent a possible out-of-bounds smartlist read in
7036 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7038 o Minor bugfixes (onion services):
7039 - Fix a bug that blocked the creation of ephemeral v3 onion
7040 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
7042 o Minor bugfixes (test coverage tools):
7043 - Update our "cov-diff" script to handle output from the latest
7044 version of gcov, and to remove extraneous timestamp information
7045 from its output. Fixes bugs 26101 and 26102; bugfix
7049 Changes in version 0.3.3.6 - 2018-05-22
7050 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
7051 backports several important fixes from the 0.3.4.1-alpha.
7053 The Tor 0.3.3 series includes controller support and other
7054 improvements for v3 onion services, official support for embedding Tor
7055 within other applications, and our first non-trivial module written in
7056 the Rust programming language. (Rust is still not enabled by default
7057 when building Tor.) And as usual, there are numerous other smaller
7058 bugfixes, features, and improvements.
7060 Below are the changes since 0.3.3.5-rc. For a list of all changes
7061 since 0.3.2.10, see the ReleaseNotes file.
7063 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
7064 - When directory authorities read a zero-byte bandwidth file, they
7065 would previously log a warning with the contents of an
7066 uninitialised buffer. They now log a warning about the empty file
7067 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7069 o Major bugfixes (security, directory authority, denial-of-service):
7070 - Fix a bug that could have allowed an attacker to force a directory
7071 authority to use up all its RAM by passing it a maliciously
7072 crafted protocol versions string. Fixes bug 25517; bugfix on
7073 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
7075 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
7076 - Avoid a rare assertion failure in the circuit build timeout code
7077 if we fail to allow any circuits to actually complete. Fixes bug
7078 25733; bugfix on 0.2.2.2-alpha.
7080 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7081 - Avoid a crash when testing router reachability on a router that
7082 could have an ed25519 ID, but which does not. Fixes bug 25415;
7083 bugfix on 0.3.3.2-alpha.
7085 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
7086 - Correctly detect when onion services get disabled after HUP. Fixes
7087 bug 25761; bugfix on 0.3.2.1.
7089 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
7090 - Impose a limit on circuit cell queue size. The limit can be
7091 controlled by a consensus parameter. Fixes bug 25226; bugfix
7094 o Minor features (compatibility, backport from 0.3.4.1-alpha):
7095 - Avoid some compilation warnings with recent versions of LibreSSL.
7096 Closes ticket 26006.
7098 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7099 - Our .travis.yml configuration now includes support for testing the
7100 results of "make distcheck". (It's not uncommon for "make check"
7101 to pass but "make distcheck" to fail.) Closes ticket 25814.
7102 - Our Travis CI configuration now integrates with the Coveralls
7103 coverage analysis tool. Closes ticket 25818.
7105 o Minor features (geoip):
7106 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7107 database. Closes ticket 26104.
7109 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7110 - Don't consider Tor running as a client if the ControlPort is open,
7111 but no actual client ports are open. Fixes bug 26062; bugfix
7114 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7115 - Upon receiving a malformed connected cell, stop processing the
7116 cell immediately. Previously we would mark the connection for
7117 close, but continue processing the cell as if the connection were
7118 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7120 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
7121 - Stop saying in the manual that clients cache ipv4 dns answers from
7122 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7123 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7124 we forgot to say so in the man page. Fixes bug 26052; bugfix
7127 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7128 - Allow the nanosleep() system call, which glibc uses to implement
7129 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7131 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7132 - Fix a memory leak when a v3 onion service is configured and gets a
7133 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7134 - When parsing the descriptor signature, look for the token plus an
7135 extra white-space at the end. This is more correct but also will
7136 allow us to support new fields that might start with "signature".
7137 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7139 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7140 - Avoid a crash when running with DirPort set but ORPort turned off.
7141 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7143 o Documentation (backport from 0.3.4.1-alpha):
7144 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7145 ticket 25857. Patch from "CTassisF".
7148 Changes in version 0.3.4.1-alpha - 2018-05-17
7149 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
7150 includes refactoring to begin reducing Tor's binary size and idle CPU
7151 usage on mobile, along with prep work for new bandwidth scanners,
7152 improvements to the experimental "vanguards" feature, and numerous
7153 other small features and bugfixes.
7155 o New system requirements:
7156 - Tor no longer tries to support old operating systems without
7157 mmap() or some local equivalent. Apparently, compilation on such
7158 systems has been broken for some time, without anybody noticing or
7159 complaining. Closes ticket 25398.
7161 o Major feature (directory authority, modularization):
7162 - The directory authority subsystem has been modularized. The code
7163 is now located in src/or/dirauth/, and is compiled in by default.
7164 To disable the module, the configure option
7165 --disable-module-dirauth has been added. This module may be
7166 disabled by default in some future release. Closes ticket 25610.
7168 o Major features (main loop, CPU usage):
7169 - When Tor is disabled (via DisableNetwork or via hibernation), it
7170 no longer needs to run any per-second events. This change should
7171 make it easier for mobile applications to disable Tor while the
7172 device is sleeping, or Tor is not running. Closes ticket 26063.
7173 - Tor no longer enables all of its periodic events by default.
7174 Previously, Tor would enable all possible main loop events,
7175 regardless of whether it needed them. Furthermore, many of these
7176 events are now disabled with Tor is hibernating or DisableNetwork
7177 is set. This is a big step towards reducing client CPU usage by
7178 reducing the amount of wake-ups the daemon does. Closes ticket
7180 - The bandwidth-limitation logic has been refactored so that
7181 bandwidth calculations are performed on-demand, rather than every
7182 TokenBucketRefillInterval milliseconds. This change should improve
7183 the granularity of our bandwidth calculations, and limit the
7184 number of times that the Tor process needs to wake up when it is
7185 idle. Closes ticket 25373.
7186 - Move responsibility for many operations from a once-per-second
7187 callback to a callback that is only scheduled as needed. Moving
7188 this functionality has allowed us to disable the callback when
7189 Tor's network is disabled. Once enough items are removed from our
7190 once-per-second callback, we can eliminate it entirely to conserve
7191 CPU when idle. The functionality removed includes: closing
7192 connections, circuits, and channels (ticket 25932); consensus
7193 voting (25937); flushing log callbacks (25951); honoring delayed
7194 SIGNEWNYM requests (25949); rescanning the consensus cache
7195 (25931); saving the state file to disk (25948); warning relay
7196 operators about unreachable ports (25952); and keeping track of
7197 Tor's uptime (26009).
7199 o Major bugfixes (directory authorities, security):
7200 - When directory authorities read a zero-byte bandwidth file, they
7201 would previously log a warning with the contents of an
7202 uninitialised buffer. They now log a warning about the empty file
7203 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7205 o Major bugfixes (crash):
7206 - Avoid a rare assertion failure in the circuit build timeout code
7207 if we fail to allow any circuits to actually complete. Fixes bug
7208 25733; bugfix on 0.2.2.2-alpha.
7210 o Major bugfixes (directory authority):
7211 - Avoid a crash when testing router reachability on a router that
7212 could have an ed25519 ID, but which does not. Fixes bug 25415;
7213 bugfix on 0.3.3.2-alpha.
7215 o Major bugfixes (onion service):
7216 - Correctly detect when onion services get disabled after HUP. Fixes
7217 bug 25761; bugfix on 0.3.2.1.
7219 o Major bugfixes (protover, voting):
7220 - Revise Rust implementation of protover to use a more memory-
7221 efficient voting algorithm and corresponding data structures, thus
7222 avoiding a potential (but small impact) DoS attack where specially
7223 crafted protocol strings would expand to several potential
7224 megabytes in memory. In the process, several portions of code were
7225 revised to be methods on new, custom types, rather than functions
7226 taking interchangeable types, thus increasing type safety of the
7227 module. Custom error types and handling were added as well, in
7228 order to facilitate better error dismissal/handling in outside
7229 crates and avoid mistakenly passing an internal error string to C
7230 over the FFI boundary. Many tests were added, and some previous
7231 differences between the C and Rust implementations have been
7232 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
7234 o Major bugfixes (relay, denial of service):
7235 - Impose a limit on circuit cell queue size. The limit can be
7236 controlled by a consensus parameter. Fixes bug 25226; bugfix
7239 o Minor features (accounting):
7240 - When Tor becomes dormant, it now uses a scheduled event to wake up
7241 at the right time. Previously, we would use the per-second timer
7242 to check whether to wake up, but we no longer have any per-second
7243 timers enabled when the network is disabled. Closes ticket 26064.
7245 o Minor features (code quality):
7246 - Add optional spell-checking for the Tor codebase, using the
7247 "misspell" program. To use this feature, run "make check-typos".
7248 Closes ticket 25024.
7250 o Minor features (compatibility):
7251 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
7252 the no-deprecated option, and builds correctly with them. Closes
7253 tickets 19429, 19981, and 25353.
7254 - Avoid some compilation warnings with recent versions of LibreSSL.
7255 Closes ticket 26006.
7257 o Minor features (compression, zstd):
7258 - When running with zstd, Tor now considers using advanced functions
7259 that the zstd maintainers have labeled as potentially unstable. To
7260 prevent breakage, Tor will only use this functionality when the
7261 runtime version of the zstd library matches the version with which
7262 Tor was compiled. Closes ticket 25162.
7264 o Minor features (configuration):
7265 - The "DownloadSchedule" options have been renamed to end with
7266 "DownloadInitialDelay". The old names are still allowed, but will
7267 produce a warning. Comma-separated lists are still permitted for
7268 these options, but all values after the first are ignored (as they
7269 have been since 0.2.9). Closes ticket 23354.
7271 o Minor features (continuous integration):
7272 - Our .travis.yml configuration now includes support for testing the
7273 results of "make distcheck". (It's not uncommon for "make check"
7274 to pass but "make distcheck" to fail.) Closes ticket 25814.
7275 - Our Travis CI configuration now integrates with the Coveralls
7276 coverage analysis tool. Closes ticket 25818.
7278 o Minor features (control port):
7279 - Introduce GETINFO "current-time/{local,utc}" to return the local
7280 and UTC times respectively in ISO format. This helps a controller
7281 like Tor Browser detect a time-related error. Closes ticket 25511.
7282 Patch by Neel Chauhan.
7283 - Introduce new fields to the CIRC_BW event. There are two new
7284 fields in each of the read and written directions. The DELIVERED
7285 fields report the total valid data on the circuit, as measured by
7286 the payload sizes of verified and error-checked relay command
7287 cells. The OVERHEAD fields report the total unused bytes in each
7288 of these cells. Closes ticket 25903.
7290 o Minor features (directory authority):
7291 - Directory authorities now open their key-pinning files as O_SYNC,
7292 to limit their chances of accidentally writing partial lines.
7293 Closes ticket 23909.
7295 o Minor features (directory authority, forward compatibility):
7296 - Make the lines of the measured bandwidth file able to contain
7297 their entries in any order. Previously, the node_id entry needed
7298 to come first. Closes ticket 26004.
7300 o Minor features (entry guards):
7301 - Introduce a new torrc option NumPrimaryGuards for controlling the
7302 number of primary guards. Closes ticket 25843.
7304 o Minor features (geoip):
7305 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7306 database. Closes ticket 26104.
7308 o Minor features (performance):
7309 - Avoid a needless call to malloc() when processing an incoming
7310 relay cell. Closes ticket 24914.
7311 - Make our timing-wheel code run a tiny bit faster on 32-bit
7312 platforms, by preferring 32-bit math to 64-bit. Closes
7314 - Avoid a needless malloc()/free() pair every time we handle an ntor
7315 handshake. Closes ticket 25150.
7317 o Minor features (testing):
7318 - Add a unit test for voting_schedule_get_start_of_next_interval().
7319 Closes ticket 26014, and helps make unit test coverage
7321 - A new unittests module specifically for testing the functions in
7322 the (new-ish) bridges.c module has been created with new
7323 unittests, raising the code coverage percentages. Closes 25425.
7324 - We now have improved testing for addressmap_get_virtual_address()
7325 function. This should improve our test coverage, and make our test
7326 coverage more deterministic. Closes ticket 25993.
7328 o Minor features (timekeeping, circuit scheduling):
7329 - When keeping track of how busy each circuit have been recently on
7330 a given connection, use coarse-grained monotonic timers rather
7331 than gettimeofday(). This change should marginally increase
7332 accuracy and performance. Implements part of ticket 25927.
7334 o Minor bugfixes (bandwidth management):
7335 - Consider ourselves "low on write bandwidth" if we have exhausted
7336 our write bandwidth some time in the last second. This was the
7337 documented behavior before, but the actual behavior was to change
7338 this value every TokenBucketRefillInterval. Fixes bug 25828;
7339 bugfix on 0.2.3.5-alpha.
7341 o Minor bugfixes (C correctness):
7342 - Add a missing lock acquisition in the shutdown code of the control
7343 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
7344 Coverity; this is CID 1433643.
7346 o Minor bugfixes (circuit path selection):
7347 - Don't count path selection failures as circuit build failures.
7348 This change should eliminate cases where Tor blames its guard or
7349 the network for situations like insufficient microdescriptors
7350 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
7353 o Minor bugfixes (client):
7354 - Don't consider Tor running as a client if the ControlPort is open,
7355 but no actual client ports are open. Fixes bug 26062; bugfix
7358 o Minor bugfixes (code style):
7359 - Fixed multiple includes of transports.h in src/or/connection.c
7360 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
7361 - Remove the unused variable n_possible from the function
7362 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
7364 o Minor bugfixes (control interface):
7365 - Respond with more human-readable error messages to GETINFO exit-
7366 policy/* requests. Also, let controller know if an error is
7367 transient (response code 551) or not (response code 552). Fixes
7368 bug 25852; bugfix on 0.2.8.1-alpha.
7370 o Minor bugfixes (controller):
7371 - Make CIRC_BW event reflect the total of all data sent on a
7372 circuit, including padding and dropped cells. Also fix a mis-
7373 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
7374 bugfix on 0.2.5.2-alpha.
7376 o Minor bugfixes (correctness, client):
7377 - Upon receiving a malformed connected cell, stop processing the cell
7378 immediately. Previously we would mark the connection for close, but
7379 continue processing the cell as if the connection were open. Fixes bug
7380 26072; bugfix on 0.2.4.7-alpha.
7382 o Minor bugfixes (directory client):
7383 - When unverified-consensus is verified, rename it to cached-
7384 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
7385 - Fixed launching a certificate fetch always during the scheduled
7386 periodic consensus fetch by fetching only in those cases when
7387 consensus are waiting for certs. Fixes bug 24740; bugfix
7390 o Minor bugfixes (documentation):
7391 - Stop saying in the manual that clients cache ipv4 dns answers from
7392 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7393 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7394 we forgot to say so in the man page. Fixes bug 26052; bugfix
7397 o Minor bugfixes (error reporting):
7398 - Improve tolerance for directory authorities with skewed clocks.
7399 Previously, an authority with a clock more than 60 seconds ahead
7400 could cause a client with a correct clock to warn that the
7401 client's clock was behind. Now the clocks of a majority of
7402 directory authorities have to be ahead of the client before this
7403 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
7405 o Minor bugfixes (Linux seccomp2 sandbox):
7406 - Allow the nanosleep() system call, which glibc uses to implement
7407 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7409 o Minor bugfixes (onion service):
7410 - Fix a memory leak when a v3 onion service is configured and gets a
7411 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7412 - When parsing the descriptor signature, look for the token plus an
7413 extra white-space at the end. This is more correct but also will
7414 allow us to support new fields that might start with "signature".
7415 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7417 o Minor bugfixes (path selection):
7418 - Only select relays when they have the descriptors we prefer to use
7419 for them. This change fixes a bug where we could select a relay
7420 because it had _some_ descriptor, but reject it later with a
7421 nonfatal assertion error because it didn't have the exact one we
7422 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
7424 o Minor bugfixes (portability):
7425 - Do not align mmap length, as it is not required by POSIX, and the
7426 getpagesize function is deprecated. Fixes bug 25399; bugfix
7429 o Minor bugfixes (portability, FreeBSD):
7430 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
7431 does not stringify on FreeBSD, so we switch to tor_asprintf().
7432 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
7434 o Minor bugfixes (relay statistics):
7435 - When a relay is collecting internal statistics about how many
7436 create cell requests it has seen of each type, accurately count
7437 the requests from relays that temporarily fall out of the
7438 consensus. (To be extra conservative, we were already ignoring
7439 requests from clients in our counts, and we continue ignoring them
7440 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
7442 o Minor bugfixes (relay, crash):
7443 - Avoid a crash when running with DirPort set but ORPort turned off.
7444 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7446 o Minor bugfixes (restart-in-process):
7447 - When shutting down, Tor now clears all the flags in the control.c
7448 module. This should prevent a bug where authentication cookies are
7449 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
7451 o Minor bugfixes (testing):
7452 - When testing workqueue event-cancellation, make sure that we
7453 actually cancel an event, and that cancel each event with equal
7454 probability. (It was previously possible, though extremely
7455 unlikely, for our event-canceling test not to cancel any events.)
7456 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
7457 - Repeat part of the test in test_client_pick_intro() a number of
7458 times, to give it consistent coverage. Fixes bug 25996; bugfix
7460 - Remove randomness from the hs_common/responsible_hsdirs test, so
7461 that it always takes the same path through the function it tests.
7462 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
7463 - Change the behavior of the "channel/outbound" test so that it
7464 never causes a 10-second rollover for the EWMA circuitmux code.
7465 Previously, this behavior would happen randomly, and result in
7466 fluctuating test coverage. Fixes bug 25994; bugfix
7468 - Use X509_new() to allocate certificates that will be freed later
7469 with X509_free(). Previously, some parts of the unit tests had
7470 used tor_malloc_zero(), which is incorrect, and which caused test
7471 failures on Windows when they were built with extra hardening.
7472 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
7474 - While running the circuit_timeout test, fix the PRNG to a
7475 deterministic AES stream, so that the test coverage from this test
7476 will itself be deterministic. Fixes bug 25995; bugfix
7479 o Minor bugfixes (vanguards):
7480 - Allow the last hop in a vanguard circuit to be the same as our
7481 first, to prevent the adversary from influencing guard node choice
7482 by choice of last hop. Also prevent the creation of A - B - A
7483 paths, or A - A paths, which are forbidden by relays. Fixes bug
7484 25870; bugfix on 0.3.3.1-alpha.
7486 o Code simplification and refactoring:
7487 - Remove duplicate code in parse_{c,s}method_line and bootstrap
7488 their functionalities into a single function. Fixes bug 6236;
7489 bugfix on 0.2.3.6-alpha.
7490 - We remove the PortForwarding and PortForwardingHelper options,
7491 related functions, and the port_forwarding tests. These options
7492 were used by the now-deprecated Vidalia to help ordinary users
7493 become Tor relays or bridges. Closes ticket 25409. Patch by
7495 - In order to make the OR and dir checking function in router.c less
7496 confusing we renamed some functions and
7497 consider_testing_reachability() has been split into
7498 router_should_check_reachability() and
7499 router_do_reachability_checks(). Also we improved the documentation
7500 in some functions. Closes ticket 18918.
7501 - Initial work to isolate Libevent usage to a handful of modules in
7502 our codebase, to simplify our call structure, and so that we can
7503 more easily change event loops in the future if needed. Closes
7505 - Introduce a function to call getsockname() and return tor_addr_t,
7506 to save a little complexity throughout the codebase. Closes
7508 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
7509 as hsdir_index is always present. Also, we move hsdir_index_t into
7510 or.h. Closes ticket 23094. Patch by Neel Chauhan.
7511 - Merge functions used for describing nodes and suppress the
7512 functions that do not allocate memory for the output buffer
7513 string. NODE_DESC_BUF_LEN constant and format_node_description()
7514 function cannot be used externally from router.c module anymore.
7515 Closes ticket 25432. Patch by valentecaio.
7516 - Our main loop has been simplified so that all important operations
7517 happen inside events. Previously, some operations had to happen
7518 outside the event loop, to prevent infinite sequences of event
7519 activations. Closes ticket 25374.
7520 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
7521 it in register_intro_circ() and service_intro_point_new(). This
7522 prevents the digest from being re-calculated each time. Closes
7523 ticket 23107. Patch by Neel Chauhan.
7524 - Refactor token-bucket implementations to use a common backend.
7525 Closes ticket 25766.
7526 - Remove extern declaration of stats_n_seconds_working variable from
7527 main, protecting its accesses with get_uptime() and reset_uptime()
7528 functions. Closes ticket 25081, patch by “valentecaio”.
7529 - Remove our previous logic for "cached gettimeofday()" -- our
7530 coarse monotonic timers are fast enough for this purpose, and far
7531 less error-prone. Implements part of ticket 25927.
7532 - Remove the return value for fascist_firewall_choose_address_base(),
7533 and sister functions such as fascist_firewall_choose_address_node()
7534 and fascist_firewall_choose_address_rs(). Also, while we're here,
7535 initialize the ap argument as leaving it uninitialized can pose a
7536 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
7537 - Rename two fields of connection_t struct. timestamp_lastwritten is
7538 renamed to timestamp_last_write_allowed and timestamp_lastread is
7539 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
7541 - Since Tor requires C99, remove our old workaround code for libc
7542 implementations where free(NULL) doesn't work. Closes ticket 24484.
7543 - Use our standard rate-limiting code to deal with excessive
7544 libevent failures, rather than the hand-rolled logic we had
7545 before. Closes ticket 26016.
7546 - We remove the return value of node_get_prim_orport() and
7547 node_get_prim_dirport(), and introduce node_get_prim_orport() in
7548 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
7549 check for a null address. Closes ticket 23873. Patch by
7551 - We switch to should_record_bridge_info() in
7552 geoip_note_client_seen() and options_need_geoip_info() instead of
7553 accessing the configuration values directly. Fixes bug 25290;
7554 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
7556 o Deprecated features:
7557 - As we are not recommending 0.2.5 anymore, we require relays that
7558 once had an ed25519 key associated with their RSA key to always
7559 have that key, instead of allowing them to drop back to a version
7560 that didn't support ed25519. This means they need to use a new RSA
7561 key if they want to downgrade to an older version of tor without
7562 ed25519. Closes ticket 20522.
7565 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7566 ticket 25857. Patch from "CTassisF".
7569 - Directory authorities will no longer support voting according to
7570 any consensus method before consensus method 25. This keeps
7571 authorities compatible with all authorities running 0.2.9.8 and
7572 later, and does not break any clients or relays. Implements ticket
7573 24378 and proposal 290.
7574 - The PortForwarding and PortForwardingHelper features have been
7575 removed. The reasoning is, given that implementations of NAT
7576 traversal protocols within common consumer grade routers are
7577 frequently buggy, and that the target audience for a NAT punching
7578 feature is a perhaps less-technically-inclined relay operator,
7579 when the helper fails to setup traversal the problems are usually
7580 deep, ugly, and very router specific, making them horrendously
7581 impossible for technical support to reliable assist with, and thus
7582 resulting in frustration all around. Unfortunately, relay
7583 operators who would like to run relays behind NATs will need to
7584 become more familiar with the port forwarding configurations on
7585 their local router. Closes 25409.
7586 - The TestingEnableTbEmptyEvent option has been removed. It was used
7587 in testing simulations to measure how often connection buckets
7588 were emptied, in order to improve our scheduling, but it has not
7589 been actively used in years. Closes ticket 25760.
7590 - The old "round-robin" circuit multiplexer (circuitmux)
7591 implementation has been removed, along with a fairly large set of
7592 code that existed to support it. It has not been the default
7593 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
7594 but it still required an unreasonable amount of memory and CPU.
7595 Closes ticket 25268.
7598 Changes in version 0.3.3.5-rc - 2018-04-15
7599 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
7600 including some that could affect reliability or correctness.
7602 This is the first release candidate in the 0.3.3 series. If we find no
7603 new bugs or regression here, then the first stable 0.3.3 release will
7604 be nearly identical to this one.
7606 o Major bugfixes (security, protover, voting):
7607 - Revise Rust implementation of protover to use a more memory-
7608 efficient voting algorithm and corresponding data structures, thus
7609 avoiding a potential memory-based DoS attack where specially
7610 crafted protocol strings would expand to fill available memory.
7611 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
7613 o Major bugfixes (performance, load balancing):
7614 - Directory authorities no longer vote in favor of the Guard flag
7615 for relays without directory support. Starting in Tor
7616 0.3.0.1-alpha, clients have been avoiding using such relays in the
7617 Guard position, leading to increasingly broken load balancing for
7618 the 5%-or-so of Guards that don't advertise directory support.
7619 Fixes bug 22310; bugfix on 0.3.0.6.
7621 o Minor feature (continuous integration):
7622 - Update the Travis CI configuration to use the stable Rust channel,
7623 now that we have decided to require that. Closes ticket 25714.
7625 o Minor features (config options):
7626 - Change the way the default value for MaxMemInQueues is calculated.
7627 We now use 40% of the hardware RAM if the system has 8 GB RAM or
7628 more. Otherwise we use the former value of 75%. Closes
7631 o Minor features (geoip):
7632 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
7633 Country database. Closes ticket 25718.
7635 o Minor bugfixes (client):
7636 - When using a listed relay as a bridge, and also using
7637 microdescriptors, and considering that relay as a non-bridge in a
7638 circuit, treat its microdescriptor as a valid source of
7639 information about that relay. This change should prevent a non-
7640 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
7642 o Minor bugfixes (controller):
7643 - Restore the correct operation of the RESOLVE command, which had
7644 been broken since we added the ability to enable/disable DNS on
7645 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
7647 o Minor bugfixes (distribution, compilation, rust):
7648 - Build correctly when the rust dependencies submodule is loaded,
7649 but the TOR_RUST_DEPENDENCIES environment variable is not set.
7650 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
7651 - Actually include all of our Rust source in our source
7652 distributions. (Previously, a few of the files were accidentally
7653 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
7655 o Minor bugfixes (documentation):
7656 - Document that the PerConnBW{Rate,Burst} options will fall back to
7657 their corresponding consensus parameters only if those parameters
7658 are set. Previously we had claimed that these values would always
7659 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7660 - Revert a misformatting issue in the ExitPolicy documentation.
7661 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
7663 o Minor bugfixes (exit relay DNS retries):
7664 - Re-attempt timed-out DNS queries 3 times before failure, since our
7665 timeout is 5 seconds for them, but clients wait 10-15. Also allow
7666 slightly more timeouts per resolver when an exit has multiple
7667 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
7669 o Minor bugfixes (onion services):
7670 - Re-instate counting the client HSDir fetch circuits against the
7671 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
7673 - Remove underscores from the _HSLayer{2,3}Nodes options. This
7674 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
7675 Fixes bug 25581; bugfix on 0.3.3.1-alpha
7677 o Code simplification and refactoring:
7678 - Move the list of default directory authorities to its own file.
7679 Closes ticket 24854. Patch by "beastr0".
7681 o Documentation (manpage, denial of service):
7682 - Provide more detail about the denial-of-service options, by
7683 listing each mitigation and explaining how they relate. Closes
7687 Changes in version 0.3.3.4-alpha - 2018-03-29
7688 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
7689 the alpha testing of earlier releases in its series. We are
7690 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
7692 o New system requirements:
7693 - When built with Rust, Tor now depends on version 0.2.39 of the
7694 libc crate. Closes tickets 25310 and 25664.
7696 o Major bugfixes (relay, connection):
7697 - If we have failed to connect to a relay and received a connection
7698 refused, timeout, or similar error (at the TCP level), do not try
7699 that same address/port again for 60 seconds after the failure has
7700 occurred. Fixes bug 24767; bugfix on 0.0.6.
7702 o Minor features (geoip):
7703 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
7704 Country database. Closes ticket 25469.
7706 o Minor features (log messages):
7707 - Improve log message in the out-of-memory handler to include
7708 information about memory usage from the different compression
7709 backends. Closes ticket 25372.
7711 o Minor features (sandbox):
7712 - Explicitly permit the poll() system call when the Linux
7713 seccomp2-based sandbox is enabled: apparently, some versions of
7714 libc use poll() when calling getpwnam(). Closes ticket 25313.
7716 o Minor bugfixes (C correctness):
7717 - Fix a very unlikely (impossible, we believe) null pointer
7718 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7719 Coverity; this is CID 1430932.
7721 o Minor bugfixes (channel, client):
7722 - Better identify client connection when reporting to the geoip
7723 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
7725 o Minor bugfixes (compilation):
7726 - Fix a C99 compliance issue in our configuration script that caused
7727 compilation issues when compiling Tor with certain versions of
7728 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7730 o Minor bugfixes (controller, reliability):
7731 - Avoid a (nonfatal) assertion failure when extending a one-hop
7732 circuit from the controller to become a multihop circuit. Fixes
7733 bug 24903; bugfix on 0.2.5.2-alpha.
7735 o Major bugfixes (networking):
7736 - Tor will no longer reject IPv6 address strings from Tor Browser
7737 when they are passed as hostnames in SOCKS5 requests. Fixes bug
7738 25036, bugfix on Tor 0.3.1.2.
7740 o Minor bugfixes (networking):
7741 - string_is_valid_hostname() will not consider IP strings to be
7742 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
7744 o Minor bugfixes (onion service v3):
7745 - Avoid an assertion failure when the next onion service
7746 descriptor rotation type is out of sync with the consensus's
7747 valid-after time. Instead, log a warning message with extra
7748 information, so we can better hunt down the cause of this
7749 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
7751 o Minor bugfixes (testing):
7752 - Avoid intermittent test failures due to a test that had relied on
7753 onion service introduction point creation finishing within 5
7754 seconds of real clock time. Fixes bug 25450; bugfix
7756 - Rust crates are now automatically detected and tested. Previously,
7757 some crates were not tested by `make test-rust` due to a static
7758 string in the `src/test/test_rust.sh` script specifying which
7759 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
7761 o Minor bugfixes (testing, benchmarks):
7762 - Fix a crash when running benchmark tests on win32 systems. The
7763 crash was due to a mutex that wasn't initialized before logging
7764 and options were initialized. Fixes bug 25479; bugfix
7767 o Minor bugfixes (warnings, ipv6):
7768 - Avoid a bug warning that could occur when trying to connect to a
7769 relay over IPv6. This warning would occur on a Tor instance that
7770 downloads router descriptors, but prefers to use microdescriptors.
7771 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
7773 o Code simplification and refactoring:
7774 - Remove the old (deterministic) directory retry logic entirely:
7775 We've used exponential backoff exclusively for some time. Closes
7779 - Improved the documentation of AccountingStart parameter. Closes
7781 - Update the documentation for "Log" to include the current list of
7782 logging domains. Closes ticket 25378.
7785 Changes in version 0.3.1.10 - 2018-03-03
7786 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
7789 It includes an important security fix for a remote crash attack
7790 against directory authorities, tracked as TROVE-2018-001.
7792 This release also backports our new system for improved resistance to
7793 denial-of-service attacks against relays.
7795 This release also fixes several minor bugs and annoyances from
7798 All directory authorities should upgrade to one of the versions
7799 released today. Relays running 0.3.1.x may wish to update to one of
7800 the versions released today, for the DoS mitigations.
7802 Please note: according to our release calendar, Tor 0.3.1 will no
7803 longer be supported after 1 July 2018. If you will be running Tor
7804 after that date, you should make sure to plan to upgrade to the latest
7805 stable version, or downgrade to 0.2.9 (which will receive long-term
7808 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7809 - Fix a protocol-list handling bug that could be used to remotely crash
7810 directory authorities with a null-pointer exception. Fixes bug 25074;
7811 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7814 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7815 - Give relays some defenses against the recent network overload. We
7816 start with three defenses (default parameters in parentheses).
7817 First: if a single client address makes too many concurrent
7818 connections (>100), hang up on further connections. Second: if a
7819 single client address makes circuits too quickly (more than 3 per
7820 second, with an allowed burst of 90) while also having too many
7821 connections open (3), refuse new create cells for the next while
7822 (1-2 hours). Third: if a client asks to establish a rendezvous
7823 point to you directly, ignore the request. These defenses can be
7824 manually controlled by new torrc options, but relays will also
7825 take guidance from consensus parameters, so there's no need to
7826 configure anything manually. Implements ticket 24902.
7828 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7829 - Update the sandbox rules so that they should now work correctly
7830 with Glibc 2.26. Closes ticket 24315.
7832 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7833 - Fix an "off by 2" error in counting rendezvous failures on the
7834 onion service side. While we thought we would stop the rendezvous
7835 attempt after one failed circuit, we were actually making three
7836 circuit attempts before giving up. Now switch to a default of 2,
7837 and allow the consensus parameter "hs_service_max_rdv_failures" to
7838 override. Fixes bug 24895; bugfix on 0.0.6.
7840 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7841 - Add Link protocol version 5 to the supported protocols list. Fixes
7842 bug 25070; bugfix on 0.3.1.1-alpha.
7844 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7845 - Fix a set of false positives where relays would consider
7846 connections to other relays as being client-only connections (and
7847 thus e.g. deserving different link padding schemes) if those
7848 relays fell out of the consensus briefly. Now we look only at the
7849 initial handshake and whether the connection authenticated as a
7850 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7852 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7853 - Make our OOM handler aware of the geoip client history cache so it
7854 doesn't fill up the memory. This check is important for IPv6 and
7855 our DoS mitigation subsystem. Closes ticket 25122.
7857 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
7858 - Change relay bandwidth reporting stats interval from 4 hours to 24
7859 hours in order to reduce the efficiency of guard discovery
7860 attacks. Fixes ticket 23856.
7862 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7863 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7864 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7865 since they neither disabled TLS 1.3 nor enabled any of the
7866 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7867 Closes ticket 24978.
7869 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
7870 - The fallback directory list has been re-generated based on the
7871 current status of the network. Tor uses fallback directories to
7872 bootstrap when it doesn't yet have up-to-date directory
7873 information. Closes ticket 24801.
7874 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7875 prefer to bootstrap from fallback directory mirrors. This is a
7876 follow-up to 24679, which removed weights from the default
7877 fallbacks. Implements ticket 24681.
7879 o Minor features (geoip):
7880 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7883 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7884 - Use the actual observed address of an incoming relay connection,
7885 not the canonical address of the relay from its descriptor, when
7886 making decisions about how to handle the incoming connection.
7887 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7889 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7890 - Directory authorities, when refusing a descriptor from a rejected
7891 relay, now explicitly tell the relay (in its logs) to set a valid
7892 ContactInfo address and contact the bad-relays@ mailing list.
7893 Fixes bug 25170; bugfix on 0.2.9.1.
7895 o Minor bugfixes (address selection, backport from 0.3.2.9):
7896 - When the fascist_firewall_choose_address_ functions don't find a
7897 reachable address, set the returned address to the null address
7898 and port. This is a precautionary measure, because some callers do
7899 not check the return value. Fixes bug 24736; bugfix
7902 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
7903 - Fetch descriptors aggressively whenever we lack enough to build
7904 circuits, regardless of how many descriptors we are missing.
7905 Previously, we would delay launching the fetch when we had fewer
7906 than 15 missing descriptors, even if some of those descriptors
7907 were blocking circuits from building. Fixes bug 23985; bugfix on
7908 0.1.1.11-alpha. The effects of this bug became worse in
7909 0.3.0.3-alpha, when we began treating missing descriptors from our
7910 primary guards as a reason to delay circuits.
7911 - Don't try fetching microdescriptors from relays that have failed
7912 to deliver them in the past. Fixes bug 23817; bugfix
7915 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
7916 - Fix a signed/unsigned comparison warning introduced by our fix to
7917 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7919 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7920 - Avoid a crash when attempting to use the seccomp2 sandbox together
7921 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
7924 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7925 - Fix a possible crash on malformed consensus. If a consensus had
7926 contained an unparseable protocol line, it could have made clients
7927 and relays crash with a null-pointer exception. To exploit this
7928 issue, however, an attacker would need to be able to subvert the
7929 directory authority system. Fixes bug 25251; bugfix on
7930 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7932 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
7933 - Recover better from empty or corrupt files in the consensus cache
7934 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
7935 - When a consensus diff calculation is only partially successful,
7936 only record the successful parts as having succeeded. Partial
7937 success can happen if (for example) one compression method fails
7938 but the others succeed. Previously we misrecorded all the
7939 calculations as having succeeded, which would later cause a
7940 nonfatal assertion failure. Fixes bug 24086; bugfix
7943 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
7944 - Tor now updates its guard state when it reads a consensus
7945 regardless of whether it's missing descriptors. That makes tor use
7946 its primary guards to fetch descriptors in some edge cases where
7947 it would previously have used fallback directories. Fixes bug
7948 23862; bugfix on 0.3.0.1-alpha.
7950 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
7951 - Don't treat inability to store a cached consensus object as a bug:
7952 it can happen normally when we are out of disk space. Fixes bug
7953 24859; bugfix on 0.3.1.1-alpha.
7955 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
7956 - When queuing DESTROY cells on a channel, only queue the circuit-id
7957 and reason fields: not the entire 514-byte cell. This fix should
7958 help mitigate any bugs or attacks that fill up these queues, and
7959 free more RAM for other uses. Fixes bug 24666; bugfix
7962 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
7963 - When closing a connection via close_connection_immediately(), we
7964 mark it as "not blocked on bandwidth", to prevent later calls from
7965 trying to unblock it, and give it permission to read. This fixes a
7966 backtrace warning that can happen on relays under various
7967 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
7969 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
7970 - When selecting relays by bandwidth, avoid a rounding error that
7971 could sometimes cause load to be imbalanced incorrectly.
7972 Previously, we would always round upwards; now, we round towards
7973 the nearest integer. This had the biggest effect when a relay's
7974 weight adjustments should have given it weight 0, but it got
7975 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7976 - When calculating the fraction of nodes that have descriptors, and
7977 all nodes in the network have zero bandwidths, count the number of
7978 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7979 - Actually log the total bandwidth in compute_weighted_bandwidths().
7980 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7982 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
7983 - Improve the performance of our consensus-diff application code
7984 when Tor is built with the --enable-fragile-hardening option set.
7985 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
7987 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
7988 - Don't exit the Tor process if setrlimit() fails to change the file
7989 limit (which can happen sometimes on some versions of OSX). Fixes
7990 bug 21074; bugfix on 0.0.9pre5.
7992 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
7993 - Fix a bug in the bit-counting parts of our timing-wheel code on
7994 MSVC. (Note that MSVC is still not a supported build platform, due
7995 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
7998 o Minor bugfixes (relay, partial backport):
7999 - Make the internal channel_is_client() function look at what sort
8000 of connection handshake the other side used, rather than whether
8001 the other side ever sent a create_fast cell to us. Backports part
8002 of the fixes from bugs 22805 and 24898.
8004 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8005 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8007 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8008 bugfix on 0.2.9.4-alpha.
8010 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8011 - Update the "rust dependencies" submodule to be a project-level
8012 repository, rather than a user repository. Closes ticket 25323.
8015 Changes in version 0.2.9.15 - 2018-03-03
8016 Tor 0.2.9.15 backports important security and stability bugfixes from
8019 It includes an important security fix for a remote crash attack
8020 against directory authorities, tracked as TROVE-2018-001.
8022 This release also backports our new system for improved resistance to
8023 denial-of-service attacks against relays.
8025 This release also fixes several minor bugs and annoyances from
8028 All directory authorities should upgrade to one of the versions
8029 released today. Relays running 0.2.9.x may wish to update to one of
8030 the versions released today, for the DoS mitigations.
8032 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8033 - Fix a protocol-list handling bug that could be used to remotely crash
8034 directory authorities with a null-pointer exception. Fixes bug 25074;
8035 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8038 o Major features (denial-of-service mitigation):
8039 - Give relays some defenses against the recent network overload. We
8040 start with three defenses (default parameters in parentheses).
8041 First: if a single client address makes too many concurrent
8042 connections (>100), hang up on further connections. Second: if a
8043 single client address makes circuits too quickly (more than 3 per
8044 second, with an allowed burst of 90) while also having too many
8045 connections open (3), refuse new create cells for the next while
8046 (1-2 hours). Third: if a client asks to establish a rendezvous
8047 point to you directly, ignore the request. These defenses can be
8048 manually controlled by new torrc options, but relays will also
8049 take guidance from consensus parameters, so there's no need to
8050 configure anything manually. Implements ticket 24902.
8052 o Major bugfixes (bootstrapping):
8053 - Fetch descriptors aggressively whenever we lack enough to build
8054 circuits, regardless of how many descriptors we are missing.
8055 Previously, we would delay launching the fetch when we had fewer
8056 than 15 missing descriptors, even if some of those descriptors
8057 were blocking circuits from building. Fixes bug 23985; bugfix on
8058 0.1.1.11-alpha. The effects of this bug became worse in
8059 0.3.0.3-alpha, when we began treating missing descriptors from our
8060 primary guards as a reason to delay circuits.
8062 o Major bugfixes (onion services, retry behavior):
8063 - Fix an "off by 2" error in counting rendezvous failures on the
8064 onion service side. While we thought we would stop the rendezvous
8065 attempt after one failed circuit, we were actually making three
8066 circuit attempts before giving up. Now switch to a default of 2,
8067 and allow the consensus parameter "hs_service_max_rdv_failures" to
8068 override. Fixes bug 24895; bugfix on 0.0.6.
8070 o Minor feature (relay statistics):
8071 - Change relay bandwidth reporting stats interval from 4 hours to 24
8072 hours in order to reduce the efficiency of guard discovery
8073 attacks. Fixes ticket 23856.
8075 o Minor features (compatibility, OpenSSL):
8076 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8077 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8078 since they neither disabled TLS 1.3 nor enabled any of the
8079 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8080 Closes ticket 24978.
8082 o Minor features (denial-of-service avoidance):
8083 - Make our OOM handler aware of the geoip client history cache so it
8084 doesn't fill up the memory. This check is important for IPv6 and
8085 our DoS mitigation subsystem. Closes ticket 25122.
8087 o Minor features (fallback directory mirrors):
8088 - The fallback directory list has been re-generated based on the
8089 current status of the network. Tor uses fallback directories to
8090 bootstrap when it doesn't yet have up-to-date directory
8091 information. Closes ticket 24801.
8092 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8093 prefer to bootstrap from fallback directory mirrors. This is a
8094 follow-up to 24679, which removed weights from the default
8095 fallbacks. Implements ticket 24681.
8097 o Minor features (geoip):
8098 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8101 o Minor features (linux seccomp2 sandbox):
8102 - Update the sandbox rules so that they should now work correctly
8103 with Glibc 2.26. Closes ticket 24315.
8105 o Minor bugfix (channel connection):
8106 - Use the actual observed address of an incoming relay connection,
8107 not the canonical address of the relay from its descriptor, when
8108 making decisions about how to handle the incoming connection.
8109 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8111 o Minor bugfix (directory authority):
8112 - Directory authorities, when refusing a descriptor from a rejected
8113 relay, now explicitly tell the relay (in its logs) to set a valid
8114 ContactInfo address and contact the bad-relays@ mailing list.
8115 Fixes bug 25170; bugfix on 0.2.9.1.
8117 o Minor bugfixes (address selection):
8118 - When the fascist_firewall_choose_address_ functions don't find a
8119 reachable address, set the returned address to the null address
8120 and port. This is a precautionary measure, because some callers do
8121 not check the return value. Fixes bug 24736; bugfix
8124 o Minor bugfixes (compilation):
8125 - Fix a signed/unsigned comparison warning introduced by our fix to
8126 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8128 o Minor bugfixes (control port, linux seccomp2 sandbox):
8129 - Avoid a crash when attempting to use the seccomp2 sandbox together
8130 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8133 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8134 - Fix a possible crash on malformed consensus. If a consensus had
8135 contained an unparseable protocol line, it could have made clients
8136 and relays crash with a null-pointer exception. To exploit this
8137 issue, however, an attacker would need to be able to subvert the
8138 directory authority system. Fixes bug 25251; bugfix on
8139 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8141 o Minor bugfixes (memory usage):
8142 - When queuing DESTROY cells on a channel, only queue the circuit-id
8143 and reason fields: not the entire 514-byte cell. This fix should
8144 help mitigate any bugs or attacks that fill up these queues, and
8145 free more RAM for other uses. Fixes bug 24666; bugfix
8148 o Minor bugfixes (network layer):
8149 - When closing a connection via close_connection_immediately(), we
8150 mark it as "not blocked on bandwidth", to prevent later calls from
8151 trying to unblock it, and give it permission to read. This fixes a
8152 backtrace warning that can happen on relays under various
8153 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8155 o Minor bugfixes (OSX):
8156 - Don't exit the Tor process if setrlimit() fails to change the file
8157 limit (which can happen sometimes on some versions of OSX). Fixes
8158 bug 21074; bugfix on 0.0.9pre5.
8160 o Minor bugfixes (path selection):
8161 - When selecting relays by bandwidth, avoid a rounding error that
8162 could sometimes cause load to be imbalanced incorrectly.
8163 Previously, we would always round upwards; now, we round towards
8164 the nearest integer. This had the biggest effect when a relay's
8165 weight adjustments should have given it weight 0, but it got
8166 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8167 - When calculating the fraction of nodes that have descriptors, and
8168 all nodes in the network have zero bandwidths, count the number of
8169 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8170 - Actually log the total bandwidth in compute_weighted_bandwidths().
8171 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8173 o Minor bugfixes (portability, msvc):
8174 - Fix a bug in the bit-counting parts of our timing-wheel code on
8175 MSVC. (Note that MSVC is still not a supported build platform, due
8176 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8179 o Minor bugfixes (relay):
8180 - Make the internal channel_is_client() function look at what sort
8181 of connection handshake the other side used, rather than whether
8182 the other side ever sent a create_fast cell to us. Backports part
8183 of the fixes from bugs 22805 and 24898.
8185 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8186 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8188 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8189 bugfix on 0.2.9.4-alpha.
8192 Changes in version 0.3.2.10 - 2018-03-03
8193 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
8194 backports a number of bugfixes, including important fixes for security
8197 It includes an important security fix for a remote crash attack
8198 against directory authorities, tracked as TROVE-2018-001.
8200 Additionally, it backports a fix for a bug whose severity we have
8201 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
8202 triggered in order to crash relays with a use-after-free pattern. As
8203 such, we are now tracking that bug as TROVE-2018-002 and
8204 CVE-2018-0491, and backporting it to earlier releases. This bug
8205 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
8208 This release also backports our new system for improved resistance to
8209 denial-of-service attacks against relays.
8211 This release also fixes several minor bugs and annoyances from
8214 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
8215 today, for the fix to TROVE-2018-002. Directory authorities should
8216 also upgrade. (Relays on earlier versions might want to update too for
8217 the DoS mitigations.)
8219 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8220 - Fix a protocol-list handling bug that could be used to remotely crash
8221 directory authorities with a null-pointer exception. Fixes bug 25074;
8222 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8225 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
8226 - Avoid adding the same channel twice in the KIST scheduler pending
8227 list, which could lead to remote denial-of-service use-after-free
8228 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
8230 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
8231 - Give relays some defenses against the recent network overload. We
8232 start with three defenses (default parameters in parentheses).
8233 First: if a single client address makes too many concurrent
8234 connections (>100), hang up on further connections. Second: if a
8235 single client address makes circuits too quickly (more than 3 per
8236 second, with an allowed burst of 90) while also having too many
8237 connections open (3), refuse new create cells for the next while
8238 (1-2 hours). Third: if a client asks to establish a rendezvous
8239 point to you directly, ignore the request. These defenses can be
8240 manually controlled by new torrc options, but relays will also
8241 take guidance from consensus parameters, so there's no need to
8242 configure anything manually. Implements ticket 24902.
8244 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
8245 - Fix an "off by 2" error in counting rendezvous failures on the
8246 onion service side. While we thought we would stop the rendezvous
8247 attempt after one failed circuit, we were actually making three
8248 circuit attempts before giving up. Now switch to a default of 2,
8249 and allow the consensus parameter "hs_service_max_rdv_failures" to
8250 override. Fixes bug 24895; bugfix on 0.0.6.
8251 - New-style (v3) onion services now obey the "max rendezvous circuit
8252 attempts" logic. Previously they would make as many rendezvous
8253 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8254 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8256 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
8257 - Add Link protocol version 5 to the supported protocols list. Fixes
8258 bug 25070; bugfix on 0.3.1.1-alpha.
8260 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
8261 - Fix a set of false positives where relays would consider
8262 connections to other relays as being client-only connections (and
8263 thus e.g. deserving different link padding schemes) if those
8264 relays fell out of the consensus briefly. Now we look only at the
8265 initial handshake and whether the connection authenticated as a
8266 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8268 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
8269 - The scheduler subsystem was failing to promptly notice changes in
8270 consensus parameters, making it harder to switch schedulers
8271 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8273 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
8274 - Make our OOM handler aware of the geoip client history cache so it
8275 doesn't fill up the memory. This check is important for IPv6 and
8276 our DoS mitigation subsystem. Closes ticket 25122.
8278 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
8279 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8280 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8281 since they neither disabled TLS 1.3 nor enabled any of the
8282 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8283 Closes ticket 24978.
8285 o Minor features (geoip):
8286 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8289 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
8290 - When logging a failure to create an onion service's descriptor,
8291 also log what the problem with the descriptor was. Diagnostic
8294 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
8295 - Use the actual observed address of an incoming relay connection,
8296 not the canonical address of the relay from its descriptor, when
8297 making decisions about how to handle the incoming connection.
8298 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8300 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8301 - Fix a possible crash on malformed consensus. If a consensus had
8302 contained an unparseable protocol line, it could have made clients
8303 and relays crash with a null-pointer exception. To exploit this
8304 issue, however, an attacker would need to be able to subvert the
8305 directory authority system. Fixes bug 25251; bugfix on
8306 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8308 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
8309 - Directory authorities, when refusing a descriptor from a rejected
8310 relay, now explicitly tell the relay (in its logs) to set a valid
8311 ContactInfo address and contact the bad-relays@ mailing list.
8312 Fixes bug 25170; bugfix on 0.2.9.1.
8314 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
8315 - When building with Rust on OSX, link against libresolv, to work
8316 around the issue at https://github.com/rust-lang/rust/issues/46797.
8317 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8319 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
8320 - Remove a BUG() statement when a client fetches an onion descriptor
8321 that has a lower revision counter than the one in its cache. This
8322 can happen in normal circumstances due to HSDir desync. Fixes bug
8323 24976; bugfix on 0.3.2.1-alpha.
8325 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8326 - Don't treat inability to store a cached consensus object as a bug:
8327 it can happen normally when we are out of disk space. Fixes bug
8328 24859; bugfix on 0.3.1.1-alpha.
8330 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8331 - Improve the performance of our consensus-diff application code
8332 when Tor is built with the --enable-fragile-hardening option set.
8333 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8335 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8336 - Don't exit the Tor process if setrlimit() fails to change the file
8337 limit (which can happen sometimes on some versions of OSX). Fixes
8338 bug 21074; bugfix on 0.0.9pre5.
8340 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8341 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8343 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8344 bugfix on 0.2.9.4-alpha.
8346 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
8347 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8348 25005; bugfix on 0.3.2.7-rc.
8350 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
8351 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8352 version, when deciding whether a consensus entry can support the
8353 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8354 bugfix on 0.3.2.1-alpha.
8356 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8357 - Update the "rust dependencies" submodule to be a project-level
8358 repository, rather than a user repository. Closes ticket 25323.
8360 o Documentation (backport from 0.3.3.1-alpha)
8361 - Document that operators who run more than one relay or bridge are
8362 expected to set MyFamily and ContactInfo correctly. Closes
8366 Changes in version 0.3.3.3-alpha - 2018-03-03
8367 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
8368 It includes an important security fix for a remote crash attack
8369 against directory authorities tracked as TROVE-2018-001.
8371 Additionally, with this release, we are upgrading the severity of a
8372 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
8373 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
8374 a use-after-free pattern. As such, we are now tracking that bug as
8375 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
8376 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
8378 This release also fixes several minor bugs and annoyances from
8381 Relays running 0.3.2.x should upgrade to one of the versions released
8382 today, for the fix to TROVE-2018-002. Directory authorities should
8383 also upgrade. (Relays on earlier versions might want to update too for
8384 the DoS mitigations.)
8386 o Major bugfixes (denial-of-service, directory authority):
8387 - Fix a protocol-list handling bug that could be used to remotely crash
8388 directory authorities with a null-pointer exception. Fixes bug 25074;
8389 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8392 o Minor features (compatibility, OpenSSL):
8393 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8394 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8395 since they neither disabled TLS 1.3 nor enabled any of the
8396 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8397 Closes ticket 24978.
8399 o Minor features (logging):
8400 - Clarify the log messages produced when getrandom() or a related
8401 entropy-generation mechanism gives an error. Closes ticket 25120.
8403 o Minor features (testing):
8404 - Add a "make test-rust" target to run the rust tests only. Closes
8407 o Minor bugfixes (denial-of-service):
8408 - Fix a possible crash on malformed consensus. If a consensus had
8409 contained an unparseable protocol line, it could have made clients
8410 and relays crash with a null-pointer exception. To exploit this
8411 issue, however, an attacker would need to be able to subvert the
8412 directory authority system. Fixes bug 25251; bugfix on
8413 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8415 o Minor bugfixes (DoS mitigation):
8416 - Add extra safety checks when refilling the circuit creation bucket
8417 to ensure we never set a value above the allowed maximum burst.
8418 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
8419 - When a new consensus arrives, don't update our DoS-mitigation
8420 parameters if we aren't a public relay. Fixes bug 25223; bugfix
8423 o Minor bugfixes (man page, SocksPort):
8424 - Remove dead code from the old "SocksSocket" option, and rename
8425 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
8426 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
8428 o Minor bugfixes (performance):
8429 - Reduce the number of circuits that will be opened at once during
8430 the circuit build timeout phase. This is done by increasing the
8431 idle timeout to 3 minutes, and lowering the maximum number of
8432 concurrent learning circuits to 10. Fixes bug 24769; bugfix
8435 o Minor bugfixes (spec conformance):
8436 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8438 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8439 bugfix on 0.2.9.4-alpha.
8441 o Minor bugfixes (spec conformance, rust):
8442 - Resolve a denial-of-service issue caused by an infinite loop in
8443 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
8444 Also tracked as TROVE-2018-003.
8446 o Code simplification and refactoring:
8447 - Update the "rust dependencies" submodule to be a project-level
8448 repository, rather than a user repository. Closes ticket 25323.
8451 Changes in version 0.3.3.2-alpha - 2018-02-10
8452 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
8453 introduces a mechanism to handle the high loads that many relay
8454 operators have been reporting recently. It also fixes several bugs in
8455 older releases. If this new code proves reliable, we plan to backport
8456 it to older supported release series.
8458 o Major features (denial-of-service mitigation):
8459 - Give relays some defenses against the recent network overload. We
8460 start with three defenses (default parameters in parentheses).
8461 First: if a single client address makes too many concurrent
8462 connections (>100), hang up on further connections. Second: if a
8463 single client address makes circuits too quickly (more than 3 per
8464 second, with an allowed burst of 90) while also having too many
8465 connections open (3), refuse new create cells for the next while
8466 (1-2 hours). Third: if a client asks to establish a rendezvous
8467 point to you directly, ignore the request. These defenses can be
8468 manually controlled by new torrc options, but relays will also
8469 take guidance from consensus parameters, so there's no need to
8470 configure anything manually. Implements ticket 24902.
8472 o Major bugfixes (netflow padding):
8473 - Stop adding unneeded channel padding right after we finish
8474 flushing to a connection that has been trying to flush for many
8475 seconds. Instead, treat all partial or complete flushes as
8476 activity on the channel, which will defer the time until we need
8477 to add padding. This fix should resolve confusing and scary log
8478 messages like "Channel padding timeout scheduled 221453ms in the
8479 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8481 o Major bugfixes (protocol versions):
8482 - Add Link protocol version 5 to the supported protocols list. Fixes
8483 bug 25070; bugfix on 0.3.1.1-alpha.
8485 o Major bugfixes (scheduler, consensus):
8486 - The scheduler subsystem was failing to promptly notice changes in
8487 consensus parameters, making it harder to switch schedulers
8488 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8490 o Minor features (denial-of-service avoidance):
8491 - Make our OOM handler aware of the geoip client history cache so it
8492 doesn't fill up the memory. This check is important for IPv6 and
8493 our DoS mitigation subsystem. Closes ticket 25122.
8495 o Minor features (directory authority):
8496 - When directory authorities are unable to add signatures to a
8497 pending consensus, log the reason why. Closes ticket 24849.
8499 o Minor features (geoip):
8500 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8503 o Minor features (logging, diagnostic):
8504 - When logging a failure to create an onion service's descriptor,
8505 also log what the problem with the descriptor was. Diagnostic for
8508 o Minor bugfix (channel connection):
8509 - Use the actual observed address of an incoming relay connection,
8510 not the canonical address of the relay from its descriptor, when
8511 making decisions about how to handle the incoming connection.
8512 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8514 o Minor bugfix (directory authority):
8515 - Directory authorities, when refusing a descriptor from a rejected
8516 relay, now explicitly tell the relay (in its logs) to set a valid
8517 ContactInfo address and contact the bad-relays@ mailing list.
8518 Fixes bug 25170; bugfix on 0.2.9.1.
8520 o Minor bugfixes (all versions of Tor):
8521 - Use the "misspell" tool to detect and fix typos throughout the
8522 source code. Fixes bug 23650; bugfix on various versions of Tor.
8523 Patch from Deepesh Pathak.
8525 o Minor bugfixes (circuit, cannibalization):
8526 - Don't cannibalize preemptively-built circuits if we no longer
8527 recognize their first hop. This situation can happen if our Guard
8528 relay went off the consensus after the circuit was created. Fixes
8529 bug 24469; bugfix on 0.0.6.
8531 o Minor bugfixes (correctness):
8532 - Remove a nonworking, unnecessary check to see whether a circuit
8533 hop's identity digest was set when the circuit failed. Fixes bug
8534 24927; bugfix on 0.2.4.4-alpha.
8536 o Minor bugfixes (logging):
8537 - Don't treat inability to store a cached consensus object as a bug:
8538 it can happen normally when we are out of disk space. Fixes bug
8539 24859; bugfix on 0.3.1.1-alpha.
8540 - Fix a (mostly harmless) race condition when invoking
8541 LOG_PROTOCOL_WARN message from a subthread while the torrc options
8542 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
8544 o Minor bugfixes (onion services):
8545 - Remove a BUG() statement when a client fetches an onion descriptor
8546 that has a lower revision counter than the one in its cache. This
8547 can happen in normal circumstances due to HSDir desync. Fixes bug
8548 24976; bugfix on 0.3.2.1-alpha.
8549 - If we are configured to offer a single onion service, don't log
8550 long-term established one hop rendezvous points in the heartbeat.
8551 Fixes bug 25116; bugfix on 0.2.9.6-rc.
8553 o Minor bugfixes (performance):
8554 - Avoid calling protocol_list_supports_protocol() from inside tight
8555 loops when running with cached routerinfo_t objects. Instead,
8556 summarize the relevant protocols as flags in the routerinfo_t, as
8557 we do for routerstatus_t objects. This change simplifies our code
8558 a little, and saves a large amount of short-term memory allocation
8559 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
8561 o Minor bugfixes (Rust FFI):
8562 - Fix a minor memory leak which would happen whenever the C code
8563 would call the Rust implementation of
8564 protover_get_supported_protocols(). This was due to the C version
8565 returning a static string, whereas the Rust version newly allocated
8566 a CString to pass across the FFI boundary. Consequently, the C
8567 code was not expecting to need to free() what it was given. Fixes
8568 bug 25127; bugfix on 0.3.2.1-alpha.
8570 o Minor bugfixes (scheduler, KIST):
8571 - Avoid adding the same channel twice in the KIST scheduler pending
8572 list, which would waste CPU cycles. Fixes bug 24700; bugfix
8575 o Minor bugfixes (unit test, monotonic time):
8576 - Increase a constant (1msec to 10msec) in the monotonic time test
8577 that makes sure the nsec/usec/msec times read are synchronized.
8578 This change was needed to accommodate slow systems like armel or
8579 when the clock_gettime() is not a VDSO on the running kernel.
8580 Fixes bug 25113; bugfix on 0.2.9.1.
8582 o Minor bugfixes (v3 onion services):
8583 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8584 version, when deciding whether a consensus entry can support the
8585 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8586 bugfix on 0.3.2.1-alpha.
8588 o Code simplification and refactoring:
8589 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
8591 - Remove a series of counters used to track circuit extend attempts
8592 and connection status but that in reality we aren't using for
8593 anything other than stats logged by a SIGUSR1 signal. Closes
8596 o Documentation (man page):
8597 - The HiddenServiceVersion torrc option accepts only one number:
8598 either version 2 or 3. Closes ticket 25026; bugfix
8602 Changes in version 0.3.3.1-alpha - 2018-01-25
8603 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
8604 several new features to Tor, including several improvements to
8605 bootstrapping, and support for an experimental "vanguards" feature to
8606 resist guard discovery attacks. This series also includes better
8607 support for applications that need to embed Tor or manage v3
8610 o Major features (embedding):
8611 - There is now a documented stable API for programs that need to
8612 embed Tor. See tor_api.h for full documentation and known bugs.
8613 Closes ticket 23684.
8614 - Tor now has support for restarting in the same process.
8615 Controllers that run Tor using the "tor_api.h" interface can now
8616 restart Tor after Tor has exited. This support is incomplete,
8617 however: we fixed crash bugs that prevented it from working at
8618 all, but many bugs probably remain, including a possibility of
8619 security issues. Implements ticket 24581.
8621 o Major features (IPv6, directory documents):
8622 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
8623 consensus. This information makes it easier for IPv6 clients to
8624 bootstrap and choose reachable entry guards. Implements ticket 23826.
8625 - Add consensus method 28, which removes IPv6 ORPorts from
8626 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
8627 are redundant in microdescs. This change will be used by Tor clients
8628 on 0.2.8.x and later. (That is to say, with all Tor clients that
8629 have IPv6 bootstrap and guard support.) Implements ticket 23828.
8630 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
8631 set by different numbers of authorities. Fixes 23870
8634 o Major features (onion service v3, control port):
8635 - The control port now supports commands and events for v3 onion
8636 services. It is now possible to create ephemeral v3 services using
8637 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
8638 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
8639 DEL_ONION) have been extended to support v3 onion services. Closes
8640 ticket 20699; implements proposal 284.
8642 o Major features (onion services):
8643 - Provide torrc options to pin the second and third hops of onion
8644 service circuits to a list of nodes. The option HSLayer2Guards
8645 pins the second hop, and the option HSLayer3Guards pins the third
8646 hop. These options are for use in conjunction with experiments
8647 with "vanguards" for preventing guard enumeration attacks. Closes
8650 o Major features (rust, portability, experimental):
8651 - Tor now ships with an optional implementation of one of its
8652 smaller modules (protover.c) in the Rust programming language. To
8653 try it out, install a Rust build environment, and configure Tor
8654 with "--enable-rust --enable-cargo-online-mode". This should not
8655 cause any user-visible changes, but should help us gain more
8656 experience with Rust, and plan future Rust integration work.
8657 Implementation by Chelsea Komlo. Closes ticket 22840.
8659 o Minor features (storage, configuration):
8660 - Users can store cached directory documents somewhere other than
8661 the DataDirectory by using the CacheDirectory option. Similarly,
8662 the storage location for relay's keys can be overridden with the
8663 KeyDirectory option. Closes ticket 22703.
8665 o Major features (v3 onion services, ipv6):
8666 - When v3 onion service clients send introduce cells, they now
8667 include the IPv6 address of the rendezvous point, if it has one.
8668 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
8669 in future Tor versions, IPv6-only v3 single onion services will be
8670 able to use IPv6 addresses to connect directly to the rendezvous
8671 point. Closes ticket 23577. Patch by Neel Chauhan.
8673 o Major bugfixes (onion services, retry behavior):
8674 - Fix an "off by 2" error in counting rendezvous failures on the
8675 onion service side. While we thought we would stop the rendezvous
8676 attempt after one failed circuit, we were actually making three
8677 circuit attempts before giving up. Now switch to a default of 2,
8678 and allow the consensus parameter "hs_service_max_rdv_failures" to
8679 override. Fixes bug 24895; bugfix on 0.0.6.
8680 - New-style (v3) onion services now obey the "max rendezvous circuit
8681 attempts" logic. Previously they would make as many rendezvous
8682 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8683 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8685 o Major bugfixes (relays):
8686 - Fix a set of false positives where relays would consider
8687 connections to other relays as being client-only connections (and
8688 thus e.g. deserving different link padding schemes) if those
8689 relays fell out of the consensus briefly. Now we look only at the
8690 initial handshake and whether the connection authenticated as a
8691 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8693 o Minor feature (IPv6):
8694 - Make IPv6-only clients wait for microdescs for relays, even if we
8695 were previously using descriptors (or were using them as a bridge)
8696 and have a cached descriptor for them. Implements ticket 23827.
8697 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
8698 them, rather than waiting to download microdescriptors.
8699 Implements ticket 23827.
8701 o Minor features (cleanup):
8702 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
8703 when it stops. Closes ticket 23271.
8705 o Minor features (defensive programming):
8706 - Most of the functions in Tor that free objects have been replaced
8707 with macros that free the objects and set the corresponding
8708 pointers to NULL. This change should help prevent a large class of
8709 dangling pointer bugs. Closes ticket 24337.
8710 - Where possible, the tor_free() macro now only evaluates its input
8711 once. Part of ticket 24337.
8712 - Check that microdesc ed25519 ids are non-zero in
8713 node_get_ed25519_id() before returning them. Implements ticket
8714 24001, patch by "aruna1234".
8716 o Minor features (embedding):
8717 - Tor can now start with a preauthenticated control connection
8718 created by the process that launched it. This feature is meant for
8719 use by programs that want to launch and manage a Tor process
8720 without allowing other programs to manage it as well. For more
8721 information, see the __OwningControllerFD option documented in
8722 control-spec.txt. Closes ticket 23900.
8723 - On most errors that would cause Tor to exit, it now tries to
8724 return from the tor_main() function, rather than calling the
8725 system exit() function. Most users won't notice a difference here,
8726 but it should be significant for programs that run Tor inside
8727 a separate thread: they should now be able to survive Tor's exit
8728 conditions rather than having Tor shut down the entire process.
8729 Closes ticket 23848.
8730 - Applications that want to embed Tor can now tell Tor not to
8731 register any of its own POSIX signal handlers, using the
8732 __DisableSignalHandlers option. Closes ticket 24588.
8734 o Minor features (fallback directory list):
8735 - Avoid selecting fallbacks that change their IP addresses too
8736 often. Select more fallbacks by ignoring the Guard flag, and
8737 allowing lower cutoffs for the Running and V2Dir flags. Also allow
8738 a lower bandwidth, and a higher number of fallbacks per operator
8739 (5% of the list). Implements ticket 24785.
8740 - Update the fallback whitelist and blacklist based on opt-ins and
8741 relay changes. Closes tickets 22321, 24678, 22527, 24135,
8744 o Minor features (fallback directory mirror configuration):
8745 - Add a nickname to each fallback in a C comment. This makes it
8746 easier for operators to find their relays, and allows stem to use
8747 nicknames to identify fallbacks. Implements ticket 24600.
8748 - Add a type and version header to the fallback directory mirror
8749 file. Also add a delimiter to the end of each fallback entry. This
8750 helps external parsers like stem and Relay Search. Implements
8752 - Add an extrainfo cache flag for each fallback in a C comment. This
8753 allows stem to use fallbacks to fetch extra-info documents, rather
8754 than using authorities. Implements ticket 22759.
8755 - Add the generateFallbackDirLine.py script for automatically
8756 generating fallback directory mirror lines from relay fingerprints.
8757 No more typos! Add the lookupFallbackDirContact.py script for
8758 automatically looking up operator contact info from relay
8759 fingerprints. Implements ticket 24706, patch by teor and atagar.
8760 - Reject any fallback directory mirror that serves an expired
8761 consensus. Implements ticket 20942, patch by "minik".
8762 - Remove commas and equals signs from external string inputs to the
8763 fallback list. This avoids format confusion attacks. Implements
8765 - Remove the "weight=10" line from fallback directory mirror
8766 entries. Ticket 24681 will maintain the current fallback weights
8767 by changing Tor's default fallback weight to 10. Implements
8769 - Stop logging excessive information about fallback netblocks.
8770 Implements ticket 24791.
8772 o Minor features (forward-compatibility):
8773 - If a relay supports some link authentication protocol that we do
8774 not recognize, then include that relay's ed25519 key when telling
8775 other relays to extend to it. Previously, we treated future
8776 versions as if they were too old to support ed25519 link
8777 authentication. Closes ticket 20895.
8779 o Minor features (heartbeat):
8780 - Add onion service information to our heartbeat logs, displaying
8781 stats about the activity of configured onion services. Closes
8784 o Minor features (instrumentation, development):
8785 - Add the MainloopStats option to allow developers to get
8786 instrumentation information from the main event loop via the
8787 heartbeat messages. We hope to use this to improve Tor's behavior
8788 when it's trying to sleep. Closes ticket 24605.
8790 o Minor features (log messages):
8791 - Improve a warning message that happens when we fail to re-parse an
8792 old router because of an expired certificate. Closes ticket 20020.
8793 - Make the log more quantitative when we hit MaxMemInQueues
8794 threshold exposing some values. Closes ticket 24501.
8796 o Minor features (logging, android):
8797 - Added support for the Android logging subsystem. Closes
8800 o Minor features (performance):
8801 - Support predictive circuit building for onion service circuits
8802 with multiple layers of guards. Closes ticket 23101.
8803 - Use stdatomic.h where available, rather than mutexes, to implement
8804 atomic_counter_t. Closes ticket 23953.
8806 o Minor features (performance, 32-bit):
8807 - Improve performance on 32-bit systems by avoiding 64-bit division
8808 when calculating the timestamp in milliseconds for channel padding
8809 computations. Implements ticket 24613.
8810 - Improve performance on 32-bit systems by avoiding 64-bit division
8811 when timestamping cells and buffer chunks for OOM calculations.
8812 Implements ticket 24374.
8814 o Minor features (performance, OSX, iOS):
8815 - Use the mach_approximate_time() function (when available) to
8816 implement coarse monotonic time. Having a coarse time function
8817 should avoid a large number of system calls, and improve
8818 performance slightly, especially under load. Closes ticket 24427.
8820 o Minor features (performance, windows):
8821 - Improve performance on Windows Vista and Windows 7 by adjusting
8822 TCP send window size according to the recommendation from
8823 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
8826 o Major features (relay):
8827 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
8828 operator to use a more reasonable ("reduced") exit policy, rather
8829 than the default one. If you want to run an exit node without
8830 thinking too hard about which ports to allow, this one is for you.
8831 Closes ticket 13605. Patch from Neel Chauhan.
8833 o Minor features (testing, debugging, embedding):
8834 - For development purposes, Tor now has a mode in which it runs for
8835 a few seconds, then stops, and starts again without exiting the
8836 process. This mode is meant to help us debug various issues with
8837 ticket 23847. To use this feature, compile with
8838 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
8839 environment variable. This is expected to crash a lot, and is
8840 really meant for developers only. It will likely be removed in a
8841 future release. Implements ticket 24583.
8843 o Minor bugfix (network IPv6 test):
8844 - Tor's test scripts now check if "ping -6 ::1" works when the user
8845 runs "make test-network-all". Fixes bug 24677; bugfix on
8846 0.2.9.3-alpha. Patch by "ffmancera".
8848 o Minor bugfixes (build, rust):
8849 - Fix output of autoconf checks to display success messages for Rust
8850 dependencies and a suitable rustc compiler version. Fixes bug
8851 24612; bugfix on 0.3.1.3-alpha.
8852 - When building with Rust on OSX, link against libresolv, to work
8853 around the issue at https://github.com/rust-lang/rust/issues/46797.
8854 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8855 - Don't pass the --quiet option to cargo: it seems to suppress some
8856 errors, which is not what we want to do when building. Fixes bug
8857 24518; bugfix on 0.3.1.7.
8858 - Build correctly when building from outside Tor's source tree with
8859 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
8862 o Minor bugfixes (directory authorities, IPv6):
8863 - When creating a routerstatus (vote) from a routerinfo (descriptor),
8864 set the IPv6 address to the unspecified IPv6 address, and
8865 explicitly initialize the port to zero. Fixes bug 24488; bugfix
8868 o Minor bugfixes (fallback directory mirrors):
8869 - Make updateFallbackDirs.py search harder for python. (Some OSs
8870 don't put it in /usr/bin.) Fixes bug 24708; bugfix
8873 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
8874 - When hibernating, close connections normally and allow them to
8875 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
8877 - Do not attempt to launch self-reachability tests when entering
8878 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8879 - Resolve several bugs related to descriptor fetching on bridge
8880 clients with bandwidth accounting enabled. (This combination is
8881 not recommended!) Fixes a case of bug 12062; bugfix
8883 - When hibernating, do not attempt to launch DNS checks. Fixes a
8884 case of bug 12062; bugfix on 0.1.2.2-alpha.
8885 - When hibernating, do not try to upload or download descriptors.
8886 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8888 o Minor bugfixes (IPv6, bridges):
8889 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
8890 bugfix on 0.2.8.2-alpha.
8891 - Tor now sets IPv6 address in the routerstatus as well as in the
8892 router descriptors when updating addresses for a bridge. Closes
8893 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
8895 o Minor bugfixes (linux seccomp2 sandbox):
8896 - When running with the sandbox enabled, reload configuration files
8897 correctly even when %include was used. Previously we would crash.
8898 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
8900 o Minor bugfixes (memory leaks):
8901 - Avoid possible at-exit memory leaks related to use of Libevent's
8902 event_base_once() function. (This function tends to leak memory if
8903 the event_base is closed before the event fires.) Fixes bug 24584;
8904 bugfix on 0.2.8.1-alpha.
8905 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
8908 o Minor bugfixes (OSX):
8909 - Don't exit the Tor process if setrlimit() fails to change the file
8910 limit (which can happen sometimes on some versions of OSX). Fixes
8911 bug 21074; bugfix on 0.0.9pre5.
8913 o Minor bugfixes (performance, fragile-hardening):
8914 - Improve the performance of our consensus-diff application code
8915 when Tor is built with the --enable-fragile-hardening option set.
8916 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8918 o Minor bugfixes (performance, timeouts):
8919 - Consider circuits for timeout as soon as they complete a hop. This
8920 is more accurate than applying the timeout in
8921 circuit_expire_building() because that function is only called
8922 once per second, which is now too slow for typical timeouts on the
8923 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
8924 - Use onion service circuits (and other circuits longer than 3 hops)
8925 to calculate a circuit build timeout. Previously, Tor only
8926 calculated its build timeout based on circuits that planned to be
8927 exactly 3 hops long. With this change, we include measurements
8928 from all circuits at the point where they complete their third
8929 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
8931 o Minor bugfixes (testing):
8932 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
8933 bugfix on 0.2.3.1-alpha.
8934 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8935 25005; bugfix on 0.3.2.7-rc.
8937 o Code simplification and refactoring:
8938 - Remove /usr/athena from search path in configure.ac. Closes
8940 - Remove duplicate code in node_has_curve25519_onion_key() and
8941 node_get_curve25519_onion_key(), and add a check for a zero
8942 microdesc curve25519 onion key. Closes ticket 23966, patch by
8943 "aruna1234" and teor.
8944 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
8945 memory allocations with large numbers of OR connections (e.g.
8946 relays). Closes ticket 24119.
8947 - Separate the function that deletes ephemeral files when Tor
8949 - Small changes to Tor's buf_t API to make it suitable for use as a
8950 general-purpose safe string constructor. Closes ticket 22342.
8951 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
8952 avoid source code identifier confusion. Closes ticket 24467.
8953 - The tor_git_revision[] constant no longer needs to be redeclared
8954 by everything that links against the rest of Tor. Done as part of
8955 ticket 23845, to simplify our external API.
8956 - We make extend_info_from_node() use node_get_curve25519_onion_key()
8957 introduced in ticket 23577 to access the curve25519 public keys
8958 rather than accessing it directly. Closes ticket 23760. Patch by
8960 - Add a function to log channels' scheduler state changes to aid
8961 debugging efforts. Closes ticket 24531.
8964 - Add documentation on how to build tor with Rust dependencies
8965 without having to be online. Closes ticket 22907; bugfix
8967 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
8968 traffic. Closes ticket 24318.
8969 - Document that OutboundBindAddress doesn't apply to DNS requests.
8970 Closes ticket 22145. Patch from Aruna Maurya.
8971 - Document that operators who run more than one relay or bridge are
8972 expected to set MyFamily and ContactInfo correctly. Closes
8975 o Code simplification and refactoring (channels):
8976 - Remove the incoming and outgoing channel queues. These were never
8977 used, but still took up a step in our fast path.
8978 - The majority of the channel unit tests have been rewritten and the
8979 code coverage has now been raised to 83.6% for channel.c. Closes
8981 - Remove other dead code from the channel subsystem: All together,
8982 this cleanup has removed more than 1500 lines of code overall and
8983 adding very little except for unit test.
8985 o Code simplification and refactoring (circuit rendezvous):
8986 - Split the client-side rendezvous circuit lookup into two
8987 functions: one that returns only established circuits and another
8988 that returns all kinds of circuits. Closes ticket 23459.
8990 o Code simplification and refactoring (controller):
8991 - Make most of the variables in networkstatus_getinfo_by_purpose()
8992 const. Implements ticket 24489.
8995 Changes in version 0.3.2.9 - 2018-01-09
8996 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
8998 The 0.3.2 series includes our long-anticipated new onion service
8999 design, with numerous security features. (For more information, see
9000 our blog post at https://blog.torproject.org/fall-harvest.) We also
9001 have a new circuit scheduler algorithm for improved performance on
9002 relays everywhere (see https://blog.torproject.org/kist-and-tell),
9003 along with many smaller features and bugfixes.
9005 Per our stable release policy, we plan to support each stable release
9006 series for at least the next nine months, or for three months after
9007 the first stable release of the next series: whichever is longer. If
9008 you need a release with long-term support, we recommend that you stay
9009 with the 0.2.9 series.
9011 Below is a list of the changes since 0.3.2.8-rc. For a list of all
9012 changes since 0.3.1, see the ReleaseNotes file.
9014 o Minor features (fallback directory mirrors):
9015 - The fallback directory list has been re-generated based on the
9016 current status of the network. Tor uses fallback directories to
9017 bootstrap when it doesn't yet have up-to-date directory
9018 information. Closes ticket 24801.
9019 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9020 prefer to bootstrap from fallback directory mirrors. This is a
9021 follow-up to 24679, which removed weights from the default
9022 fallbacks. Implements ticket 24681.
9024 o Minor features (geoip):
9025 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
9028 o Minor bugfixes (address selection):
9029 - When the fascist_firewall_choose_address_ functions don't find a
9030 reachable address, set the returned address to the null address
9031 and port. This is a precautionary measure, because some callers do
9032 not check the return value. Fixes bug 24736; bugfix
9035 o Minor bugfixes (compilation):
9036 - Resolve a few shadowed-variable warnings in the onion service
9037 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
9039 o Minor bugfixes (portability, msvc):
9040 - Fix a bug in the bit-counting parts of our timing-wheel code on
9041 MSVC. (Note that MSVC is still not a supported build platform, due
9042 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9046 Changes in version 0.3.2.8-rc - 2017-12-21
9047 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
9048 schedulers that had led servers under heavy load to overload their
9049 outgoing connections. All relay operators running earlier 0.3.2.x
9050 versions should upgrade. This version also includes a mitigation for
9051 over-full DESTROY queues leading to out-of-memory conditions: if it
9052 works, we will soon backport it to earlier release series.
9054 This is the second release candidate in the 0.3.2 series. If we find
9055 no new bugs or regression here, then the first stable 0.3.2 release
9056 will be nearly identical to this.
9058 o Major bugfixes (KIST, scheduler):
9059 - The KIST scheduler did not correctly account for data already
9060 enqueued in each connection's send socket buffer, particularly in
9061 cases when the TCP/IP congestion window was reduced between
9062 scheduler calls. This situation lead to excessive per-connection
9063 buffering in the kernel, and a potential memory DoS. Fixes bug
9064 24665; bugfix on 0.3.2.1-alpha.
9066 o Minor features (geoip):
9067 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
9070 o Minor bugfixes (hidden service v3):
9071 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
9072 the probability of reaching a service for a client missing
9073 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
9075 o Minor bugfixes (memory usage):
9076 - When queuing DESTROY cells on a channel, only queue the circuit-id
9077 and reason fields: not the entire 514-byte cell. This fix should
9078 help mitigate any bugs or attacks that fill up these queues, and
9079 free more RAM for other uses. Fixes bug 24666; bugfix
9082 o Minor bugfixes (scheduler, KIST):
9083 - Use a sane write limit for KISTLite when writing onto a connection
9084 buffer instead of using INT_MAX and shoving as much as it can.
9085 Because the OOM handler cleans up circuit queues, we are better
9086 off at keeping them in that queue instead of the connection's
9087 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
9090 Changes in version 0.3.2.7-rc - 2017-12-14
9091 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
9092 including some that could affect reliability or correctness.
9094 This is the first release candidate in the 0.3.2 series. If we find no
9095 new bugs or regression here, then the first stable 0.3.2. release will
9096 be nearly identical to this.
9098 o Major bugfixes (circuit prediction):
9099 - Fix circuit prediction logic so that a client doesn't treat a port
9100 as being "handled" by a circuit if that circuit already has
9101 isolation settings on it. This change should make Tor clients more
9102 responsive by improving their chances of having a pre-created
9103 circuit ready for use when a request arrives. Fixes bug 18859;
9104 bugfix on 0.2.3.3-alpha.
9106 o Minor features (logging):
9107 - Provide better warnings when the getrandom() syscall fails. Closes
9110 o Minor features (portability):
9111 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
9112 (It doesn't yet work with the sandbox enabled.) Closes
9115 o Minor bugfixes (bridge clients, bootstrap):
9116 - Retry directory downloads when we get our first bridge descriptor
9117 during bootstrap or while reconnecting to the network. Keep
9118 retrying every time we get a bridge descriptor, until we have a
9119 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
9120 - Stop delaying bridge descriptor fetches when we have cached bridge
9121 descriptors. Instead, only delay bridge descriptor fetches when we
9122 have at least one reachable bridge. Fixes part of bug 24367;
9123 bugfix on 0.2.0.3-alpha.
9124 - Stop delaying directory fetches when we have cached bridge
9125 descriptors. Instead, only delay bridge descriptor fetches when
9126 all our bridges are definitely unreachable. Fixes part of bug
9127 24367; bugfix on 0.2.0.3-alpha.
9129 o Minor bugfixes (compilation):
9130 - Fix a signed/unsigned comparison warning introduced by our fix to
9131 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9133 o Minor bugfixes (correctness):
9134 - Fix several places in our codebase where a C compiler would be
9135 likely to eliminate a check, based on assuming that undefined
9136 behavior had not happened elsewhere in the code. These cases are
9137 usually a sign of redundant checking or dubious arithmetic. Found
9138 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
9139 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
9142 o Minor bugfixes (onion service v3):
9143 - Fix a race where an onion service would launch a new intro circuit
9144 after closing an old one, but fail to register it before freeing
9145 the previously closed circuit. This bug was making the service
9146 unable to find the established intro circuit and thus not upload
9147 its descriptor, thus making a service unavailable for up to 24
9148 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
9150 o Minor bugfixes (scheduler, KIST):
9151 - Properly set the scheduler state of an unopened channel in the
9152 KIST scheduler main loop. This prevents a harmless but annoying
9153 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
9154 - Avoid a possible integer overflow when computing the available
9155 space on the TCP buffer of a channel. This had no security
9156 implications; but could make KIST allow too many cells on a
9157 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
9158 - Downgrade to "info" a harmless warning about the monotonic time
9159 moving backwards: This can happen on platform not supporting
9160 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
9163 Changes in version 0.3.2.6-alpha - 2017-12-01
9164 This version of Tor is the latest in the 0.3.2 alpha series. It
9165 includes fixes for several important security issues. All Tor users
9166 should upgrade to this release, or to one of the other releases coming
9169 o Major bugfixes (security):
9170 - Fix a denial of service bug where an attacker could use a
9171 malformed directory object to cause a Tor instance to pause while
9172 OpenSSL would try to read a passphrase from the terminal. (Tor
9173 instances run without a terminal, which is the case for most Tor
9174 packages, are not impacted.) Fixes bug 24246; bugfix on every
9175 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9176 Found by OSS-Fuzz as testcase 6360145429790720.
9177 - Fix a denial of service issue where an attacker could crash a
9178 directory authority using a malformed router descriptor. Fixes bug
9179 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9181 - When checking for replays in the INTRODUCE1 cell data for a
9182 (legacy) onion service, correctly detect replays in the RSA-
9183 encrypted part of the cell. We were previously checking for
9184 replays on the entire cell, but those can be circumvented due to
9185 the malleability of Tor's legacy hybrid encryption. This fix helps
9186 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9187 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9190 o Major bugfixes (security, onion service v2):
9191 - Fix a use-after-free error that could crash v2 Tor onion services
9192 when they failed to open circuits while expiring introduction
9193 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9194 also tracked as TROVE-2017-013 and CVE-2017-8823.
9196 o Major bugfixes (security, relay):
9197 - When running as a relay, make sure that we never build a path
9198 through ourselves, even in the case where we have somehow lost the
9199 version of our descriptor appearing in the consensus. Fixes part
9200 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9201 as TROVE-2017-012 and CVE-2017-8822.
9202 - When running as a relay, make sure that we never choose ourselves
9203 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9204 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9206 o Minor feature (relay statistics):
9207 - Change relay bandwidth reporting stats interval from 4 hours to 24
9208 hours in order to reduce the efficiency of guard discovery
9209 attacks. Fixes ticket 23856.
9211 o Minor features (directory authority):
9212 - Add an IPv6 address for the "bastet" directory authority. Closes
9215 o Minor bugfixes (client):
9216 - By default, do not enable storage of client-side DNS values. These
9217 values were unused by default previously, but they should not have
9218 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
9221 Changes in version 0.3.1.9 - 2017-12-01:
9222 Tor 0.3.1.9 backports important security and stability fixes from the
9223 0.3.2 development series. All Tor users should upgrade to this
9224 release, or to another of the releases coming out today.
9226 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9227 - Fix a denial of service bug where an attacker could use a
9228 malformed directory object to cause a Tor instance to pause while
9229 OpenSSL would try to read a passphrase from the terminal. (Tor
9230 instances run without a terminal, which is the case for most Tor
9231 packages, are not impacted.) Fixes bug 24246; bugfix on every
9232 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9233 Found by OSS-Fuzz as testcase 6360145429790720.
9234 - Fix a denial of service issue where an attacker could crash a
9235 directory authority using a malformed router descriptor. Fixes bug
9236 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9238 - When checking for replays in the INTRODUCE1 cell data for a
9239 (legacy) onion service, correctly detect replays in the RSA-
9240 encrypted part of the cell. We were previously checking for
9241 replays on the entire cell, but those can be circumvented due to
9242 the malleability of Tor's legacy hybrid encryption. This fix helps
9243 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9244 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9247 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9248 - Fix a use-after-free error that could crash v2 Tor onion services
9249 when they failed to open circuits while expiring introduction
9250 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9251 also tracked as TROVE-2017-013 and CVE-2017-8823.
9253 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9254 - When running as a relay, make sure that we never build a path
9255 through ourselves, even in the case where we have somehow lost the
9256 version of our descriptor appearing in the consensus. Fixes part
9257 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9258 as TROVE-2017-012 and CVE-2017-8822.
9259 - When running as a relay, make sure that we never choose ourselves
9260 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9261 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9263 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9264 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9265 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9266 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9267 identifying and finding a workaround to this bug and to Moritz,
9268 Arthur Edelstein, and Roger for helping to track it down and
9271 o Minor features (bridge):
9272 - Bridges now include notice in their descriptors that they are
9273 bridges, and notice of their distribution status, based on their
9274 publication settings. Implements ticket 18329. For more fine-
9275 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9278 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9279 - Add an IPv6 address for the "bastet" directory authority. Closes
9282 o Minor features (geoip):
9283 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9286 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9287 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9288 relays, to prevent spurious address resolutions and descriptor
9289 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9290 bugfix on in 0.2.8.1-alpha.
9292 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9293 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9294 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9296 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9297 - When a circuit is marked for close, do not attempt to package any
9298 cells for channels on that circuit. Previously, we would detect
9299 this condition lower in the call stack, when we noticed that the
9300 circuit had no attached channel, and log an annoying message.
9301 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9303 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
9304 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9305 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9308 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9309 - Avoid a crash when transitioning from client mode to bridge mode.
9310 Previously, we would launch the worker threads whenever our
9311 "public server" mode changed, but not when our "server" mode
9312 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9315 Changes in version 0.3.0.13 - 2017-12-01
9316 Tor 0.3.0.13 backports important security and stability bugfixes from
9317 later Tor releases. All Tor users should upgrade to this release, or
9318 to another of the releases coming out today.
9320 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9321 2018. If you need a release with long-term support, please stick with
9322 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9324 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9325 - Fix a denial of service bug where an attacker could use a
9326 malformed directory object to cause a Tor instance to pause while
9327 OpenSSL would try to read a passphrase from the terminal. (Tor
9328 instances run without a terminal, which is the case for most Tor
9329 packages, are not impacted.) Fixes bug 24246; bugfix on every
9330 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9331 Found by OSS-Fuzz as testcase 6360145429790720.
9332 - Fix a denial of service issue where an attacker could crash a
9333 directory authority using a malformed router descriptor. Fixes bug
9334 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9336 - When checking for replays in the INTRODUCE1 cell data for a
9337 (legacy) onion service, correctly detect replays in the RSA-
9338 encrypted part of the cell. We were previously checking for
9339 replays on the entire cell, but those can be circumvented due to
9340 the malleability of Tor's legacy hybrid encryption. This fix helps
9341 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9342 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9345 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9346 - Fix a use-after-free error that could crash v2 Tor onion services
9347 when they failed to open circuits while expiring introduction
9348 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9349 also tracked as TROVE-2017-013 and CVE-2017-8823.
9351 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9352 - When running as a relay, make sure that we never build a path
9353 through ourselves, even in the case where we have somehow lost the
9354 version of our descriptor appearing in the consensus. Fixes part
9355 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9356 as TROVE-2017-012 and CVE-2017-8822.
9357 - When running as a relay, make sure that we never choose ourselves
9358 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9359 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9361 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9362 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9363 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9364 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9365 identifying and finding a workaround to this bug and to Moritz,
9366 Arthur Edelstein, and Roger for helping to track it down and
9369 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9370 - Enable a couple of pieces of Windows hardening: one
9371 (HeapEnableTerminationOnCorruption) that has been on-by-default
9372 since Windows 8, and unavailable before Windows 7; and one
9373 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9374 affect us, but shouldn't do any harm. Closes ticket 21953.
9376 o Minor features (bridge, backport from 0.3.1.9):
9377 - Bridges now include notice in their descriptors that they are
9378 bridges, and notice of their distribution status, based on their
9379 publication settings. Implements ticket 18329. For more fine-
9380 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9383 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9384 - Add an IPv6 address for the "bastet" directory authority. Closes
9387 o Minor features (geoip):
9388 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9391 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9392 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9393 relays, to prevent spurious address resolutions and descriptor
9394 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9395 bugfix on in 0.2.8.1-alpha.
9397 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9398 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9399 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9401 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9402 - When a circuit is marked for close, do not attempt to package any
9403 cells for channels on that circuit. Previously, we would detect
9404 this condition lower in the call stack, when we noticed that the
9405 circuit had no attached channel, and log an annoying message.
9406 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9408 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9409 - Avoid a crash when transitioning from client mode to bridge mode.
9410 Previously, we would launch the worker threads whenever our
9411 "public server" mode changed, but not when our "server" mode
9412 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9414 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9415 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9416 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9419 Changes in version 0.2.9.14 - 2017-12-01
9420 Tor 0.3.0.13 backports important security and stability bugfixes from
9421 later Tor releases. All Tor users should upgrade to this release, or
9422 to another of the releases coming out today.
9424 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9425 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9426 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9427 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9428 identifying and finding a workaround to this bug and to Moritz,
9429 Arthur Edelstein, and Roger for helping to track it down and
9432 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9433 - Fix a denial of service bug where an attacker could use a
9434 malformed directory object to cause a Tor instance to pause while
9435 OpenSSL would try to read a passphrase from the terminal. (Tor
9436 instances run without a terminal, which is the case for most Tor
9437 packages, are not impacted.) Fixes bug 24246; bugfix on every
9438 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9439 Found by OSS-Fuzz as testcase 6360145429790720.
9440 - Fix a denial of service issue where an attacker could crash a
9441 directory authority using a malformed router descriptor. Fixes bug
9442 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9444 - When checking for replays in the INTRODUCE1 cell data for a
9445 (legacy) onion service, correctly detect replays in the RSA-
9446 encrypted part of the cell. We were previously checking for
9447 replays on the entire cell, but those can be circumvented due to
9448 the malleability of Tor's legacy hybrid encryption. This fix helps
9449 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9450 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9453 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9454 - Fix a use-after-free error that could crash v2 Tor onion services
9455 when they failed to open circuits while expiring introduction
9456 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9457 also tracked as TROVE-2017-013 and CVE-2017-8823.
9459 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9460 - When running as a relay, make sure that we never build a path
9461 through ourselves, even in the case where we have somehow lost the
9462 version of our descriptor appearing in the consensus. Fixes part
9463 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9464 as TROVE-2017-012 and CVE-2017-8822.
9466 o Minor features (bridge, backport from 0.3.1.9):
9467 - Bridges now include notice in their descriptors that they are
9468 bridges, and notice of their distribution status, based on their
9469 publication settings. Implements ticket 18329. For more fine-
9470 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9473 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9474 - Add an IPv6 address for the "bastet" directory authority. Closes
9477 o Minor features (geoip):
9478 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9481 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9482 - Enable a couple of pieces of Windows hardening: one
9483 (HeapEnableTerminationOnCorruption) that has been on-by-default
9484 since Windows 8, and unavailable before Windows 7; and one
9485 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9486 affect us, but shouldn't do any harm. Closes ticket 21953.
9488 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9489 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9490 relays, to prevent spurious address resolutions and descriptor
9491 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9492 bugfix on in 0.2.8.1-alpha.
9494 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9495 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9496 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9498 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9499 - When a circuit is marked for close, do not attempt to package any
9500 cells for channels on that circuit. Previously, we would detect
9501 this condition lower in the call stack, when we noticed that the
9502 circuit had no attached channel, and log an annoying message.
9503 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9505 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9506 - Avoid a crash when transitioning from client mode to bridge mode.
9507 Previously, we would launch the worker threads whenever our
9508 "public server" mode changed, but not when our "server" mode
9509 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9511 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9512 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9513 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9516 Changes in version 0.2.8.17 - 2017-12-01
9517 Tor 0.2.8.17 backports important security and stability bugfixes from
9518 later Tor releases. All Tor users should upgrade to this release, or
9519 to another of the releases coming out today.
9521 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9522 2018. If you need a release with long-term support, please upgrade with
9523 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9525 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9526 - Fix a denial of service bug where an attacker could use a
9527 malformed directory object to cause a Tor instance to pause while
9528 OpenSSL would try to read a passphrase from the terminal. (Tor
9529 instances run without a terminal, which is the case for most Tor
9530 packages, are not impacted.) Fixes bug 24246; bugfix on every
9531 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9532 Found by OSS-Fuzz as testcase 6360145429790720.
9533 - When checking for replays in the INTRODUCE1 cell data for a
9534 (legacy) onion service, correctly detect replays in the RSA-
9535 encrypted part of the cell. We were previously checking for
9536 replays on the entire cell, but those can be circumvented due to
9537 the malleability of Tor's legacy hybrid encryption. This fix helps
9538 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9539 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9542 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9543 - Fix a use-after-free error that could crash v2 Tor onion services
9544 when they failed to open circuits while expiring introduction
9545 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9546 also tracked as TROVE-2017-013 and CVE-2017-8823.
9548 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9549 - When running as a relay, make sure that we never build a path through
9550 ourselves, even in the case where we have somehow lost the version of
9551 our descriptor appearing in the consensus. Fixes part of bug 21534;
9552 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
9555 o Minor features (bridge, backport from 0.3.1.9):
9556 - Bridges now include notice in their descriptors that they are
9557 bridges, and notice of their distribution status, based on their
9558 publication settings. Implements ticket 18329. For more fine-
9559 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9562 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9563 - Add an IPv6 address for the "bastet" directory authority. Closes
9566 o Minor features (geoip):
9567 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9570 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9571 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9572 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9575 Changes in version 0.2.5.16 - 2017-12-01
9576 Tor 0.2.5.13 backports important security and stability bugfixes from
9577 later Tor releases. All Tor users should upgrade to this release, or
9578 to another of the releases coming out today.
9580 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9581 2018. If you need a release with long-term support, please upgrade to
9582 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9584 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9585 - Fix a denial of service bug where an attacker could use a
9586 malformed directory object to cause a Tor instance to pause while
9587 OpenSSL would try to read a passphrase from the terminal. (Tor
9588 instances run without a terminal, which is the case for most Tor
9589 packages, are not impacted.) Fixes bug 24246; bugfix on every
9590 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9591 Found by OSS-Fuzz as testcase 6360145429790720.
9592 - When checking for replays in the INTRODUCE1 cell data for a
9593 (legacy) onion service, correctly detect replays in the RSA-
9594 encrypted part of the cell. We were previously checking for
9595 replays on the entire cell, but those can be circumvented due to
9596 the malleability of Tor's legacy hybrid encryption. This fix helps
9597 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9598 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9601 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9602 - When running as a relay, make sure that we never build a path
9603 through ourselves, even in the case where we have somehow lost the
9604 version of our descriptor appearing in the consensus. Fixes part
9605 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9606 as TROVE-2017-012 and CVE-2017-8822.
9608 o Minor features (bridge, backport from 0.3.1.9):
9609 - Bridges now include notice in their descriptors that they are
9610 bridges, and notice of their distribution status, based on their
9611 publication settings. Implements ticket 18329. For more fine-
9612 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9615 o Minor features (geoip):
9616 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9620 Changes in version 0.3.2.5-alpha - 2017-11-22
9621 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
9622 fixes several stability and reliability bugs, including a fix for
9623 intermittent bootstrapping failures that some people have been seeing
9624 since the 0.3.0.x series.
9626 Please test this alpha out -- many of these fixes will soon be
9627 backported to stable Tor versions if no additional bugs are found
9630 o Major bugfixes (bootstrapping):
9631 - Fetch descriptors aggressively whenever we lack enough to build
9632 circuits, regardless of how many descriptors we are missing.
9633 Previously, we would delay launching the fetch when we had fewer
9634 than 15 missing descriptors, even if some of those descriptors
9635 were blocking circuits from building. Fixes bug 23985; bugfix on
9636 0.1.1.11-alpha. The effects of this bug became worse in
9637 0.3.0.3-alpha, when we began treating missing descriptors from our
9638 primary guards as a reason to delay circuits.
9639 - Don't try fetching microdescriptors from relays that have failed
9640 to deliver them in the past. Fixes bug 23817; bugfix
9643 o Minor features (directory authority):
9644 - Make the "Exit" flag assignment only depend on whether the exit
9645 policy allows connections to ports 80 and 443. Previously relays
9646 would get the Exit flag if they allowed connections to one of
9647 these ports and also port 6667. Resolves ticket 23637.
9649 o Minor features (geoip):
9650 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9653 o Minor features (linux seccomp2 sandbox):
9654 - Update the sandbox rules so that they should now work correctly
9655 with Glibc 2.26. Closes ticket 24315.
9657 o Minor features (logging):
9658 - Downgrade a pair of log messages that could occur when an exit's
9659 resolver gave us an unusual (but not forbidden) response. Closes
9661 - Improve the message we log when re-enabling circuit build timeouts
9662 after having received a consensus. Closes ticket 20963.
9664 o Minor bugfixes (compilation):
9665 - Fix a memory leak warning in one of the libevent-related
9666 configuration tests that could occur when manually specifying
9667 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
9668 Found and patched by Alex Xu.
9669 - When detecting OpenSSL on Windows from our configure script, make
9670 sure to try linking with the ws2_32 library. Fixes bug 23783;
9671 bugfix on 0.3.2.2-alpha.
9673 o Minor bugfixes (control port, linux seccomp2 sandbox):
9674 - Avoid a crash when attempting to use the seccomp2 sandbox together
9675 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9678 o Minor bugfixes (control port, onion services):
9679 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
9680 HS_DESC event when a service is not able to upload a descriptor.
9681 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
9683 o Minor bugfixes (directory cache):
9684 - Recover better from empty or corrupt files in the consensus cache
9685 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
9686 - When a consensus diff calculation is only partially successful,
9687 only record the successful parts as having succeeded. Partial
9688 success can happen if (for example) one compression method fails
9689 but the others succeed. Previously we misrecorded all the
9690 calculations as having succeeded, which would later cause a
9691 nonfatal assertion failure. Fixes bug 24086; bugfix
9694 o Minor bugfixes (logging):
9695 - Only log once if we notice that KIST support is gone. Fixes bug
9696 24158; bugfix on 0.3.2.1-alpha.
9697 - Suppress a log notice when relay descriptors arrive. We already
9698 have a bootstrap progress for this so no need to log notice
9699 everytime tor receives relay descriptors. Microdescriptors behave
9700 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
9702 o Minor bugfixes (network layer):
9703 - When closing a connection via close_connection_immediately(), we
9704 mark it as "not blocked on bandwidth", to prevent later calls from
9705 trying to unblock it, and give it permission to read. This fixes a
9706 backtrace warning that can happen on relays under various
9707 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9709 o Minor bugfixes (onion services):
9710 - The introduction circuit was being timed out too quickly while
9711 waiting for the rendezvous circuit to complete. Keep the intro
9712 circuit around longer instead of timing out and reopening new ones
9713 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
9714 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9715 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9717 - Silence a warning about failed v3 onion descriptor uploads that
9718 can happen naturally under certain edge cases. Fixes part of bug
9719 23662; bugfix on 0.3.2.1-alpha.
9721 o Minor bugfixes (tests):
9722 - Fix a memory leak in one of the bridge-distribution test cases.
9723 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
9724 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
9725 to correctly handle cases where a caller gives it an RSA key of
9726 under 160 bits. (This is not actually a bug in Tor itself, but
9727 rather in our fuzzing code.) Fixes bug 24247; bugfix on
9728 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
9731 - Add notes in man page regarding OS support for the various
9732 scheduler types. Attempt to use less jargon in the scheduler
9733 section. Closes ticket 24254.
9736 Changes in version 0.3.2.4-alpha - 2017-11-08
9737 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
9738 It fixes several stability and reliability bugs, especially including
9739 a major reliability issue that has been plaguing fast exit relays in
9742 o Major bugfixes (exit relays, DNS):
9743 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9744 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9745 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9746 identifying and finding a workaround to this bug and to Moritz,
9747 Arthur Edelstein, and Roger for helping to track it down and
9750 o Major bugfixes (scheduler, channel):
9751 - Stop processing scheduled channels if they closed while flushing
9752 cells. This can happen if the write on the connection fails
9753 leading to the channel being closed while in the scheduler loop.
9754 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
9756 o Minor features (logging, scheduler):
9757 - Introduce a SCHED_BUG() function to log extra information about
9758 the scheduler state if we ever catch a bug in the scheduler.
9759 Closes ticket 23753.
9761 o Minor features (removed deprecations):
9762 - The ClientDNSRejectInternalAddresses flag can once again be set in
9763 non-testing Tor networks, so long as they do not use the default
9764 directory authorities. This change also removes the deprecation of
9765 this flag from 0.2.9.2-alpha. Closes ticket 21031.
9767 o Minor features (testing):
9768 - Our fuzzing tests now test the encrypted portions of v3 onion
9769 service descriptors. Implements more of 21509.
9771 o Minor bugfixes (directory client):
9772 - On failure to download directory information, delay retry attempts
9773 by a random amount based on the "decorrelated jitter" algorithm.
9774 Our previous delay algorithm tended to produce extra-long delays
9775 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
9777 o Minor bugfixes (IPv6, v3 single onion services):
9778 - Remove buggy code for IPv6-only v3 single onion services, and
9779 reject attempts to configure them. This release supports IPv4,
9780 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
9781 stack v3 single onion services. Fixes bug 23820; bugfix
9784 o Minor bugfixes (logging, relay):
9785 - Give only a protocol warning when the ed25519 key is not
9786 consistent between the descriptor and microdescriptor of a relay.
9787 This can happen, for instance, if the relay has been flagged
9788 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
9790 o Minor bugfixes (manpage, onion service):
9791 - Document that the HiddenServiceNumIntroductionPoints option is
9792 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
9793 bugfix on 0.3.2.1-alpha.
9795 o Minor bugfixes (memory leaks):
9796 - Fix a minor memory leak at exit in the KIST scheduler. This bug
9797 should have no user-visible impact. Fixes bug 23774; bugfix
9799 - Fix a memory leak when decrypting a badly formatted v3 onion
9800 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
9801 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
9803 o Minor bugfixes (onion services):
9804 - Cache some needed onion service client information instead of
9805 constantly computing it over and over again. Fixes bug 23623;
9806 bugfix on 0.3.2.1-alpha.
9807 - Properly retry HSv3 descriptor fetches when missing required
9808 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
9810 o Minor bugfixes (path selection):
9811 - When selecting relays by bandwidth, avoid a rounding error that
9812 could sometimes cause load to be imbalanced incorrectly.
9813 Previously, we would always round upwards; now, we round towards
9814 the nearest integer. This had the biggest effect when a relay's
9815 weight adjustments should have given it weight 0, but it got
9816 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9817 - When calculating the fraction of nodes that have descriptors, and
9818 all nodes in the network have zero bandwidths, count the number of
9819 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9820 - Actually log the total bandwidth in compute_weighted_bandwidths().
9821 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9823 o Minor bugfixes (relay, crash):
9824 - Avoid a crash when transitioning from client mode to bridge mode.
9825 Previously, we would launch the worker threads whenever our
9826 "public server" mode changed, but not when our "server" mode
9827 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9829 o Minor bugfixes (testing):
9830 - Fix a spurious fuzzing-only use of an uninitialized value. Found
9831 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
9832 - Test that IPv6-only clients can use microdescriptors when running
9833 "make test-network-all". Requires chutney master 61c28b9 or later.
9834 Closes ticket 24109.
9837 Changes in version 0.3.2.3-alpha - 2017-10-27
9838 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
9839 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
9840 directory authority, Bastet.
9842 o Directory authority changes:
9843 - Add "Bastet" as a ninth directory authority to the default list.
9844 Closes ticket 23910.
9845 - The directory authority "Longclaw" has changed its IP address.
9846 Closes ticket 23592.
9848 o Minor features (bridge):
9849 - Bridge relays can now set the BridgeDistribution config option to
9850 add a "bridge-distribution-request" line to their bridge
9851 descriptor, which tells BridgeDB how they'd like their bridge
9852 address to be given out. (Note that as of Oct 2017, BridgeDB does
9853 not yet implement this feature.) As a side benefit, this feature
9854 provides a way to distinguish bridge descriptors from non-bridge
9855 descriptors. Implements tickets 18329.
9857 o Minor features (client, entry guards):
9858 - Improve log messages when missing descriptors for primary guards.
9859 Resolves ticket 23670.
9861 o Minor features (geoip):
9862 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9865 o Minor bugfixes (bridge):
9866 - Overwrite the bridge address earlier in the process of retrieving
9867 its descriptor, to make sure we reach it on the configured
9868 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
9870 o Minor bugfixes (documentation):
9871 - Document better how to read gcov, and what our gcov postprocessing
9872 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
9874 o Minor bugfixes (entry guards):
9875 - Tor now updates its guard state when it reads a consensus
9876 regardless of whether it's missing descriptors. That makes tor use
9877 its primary guards to fetch descriptors in some edge cases where
9878 it would previously have used fallback directories. Fixes bug
9879 23862; bugfix on 0.3.0.1-alpha.
9881 o Minor bugfixes (hidden service client):
9882 - When handling multiple SOCKS request for the same .onion address,
9883 only fetch the service descriptor once.
9884 - When a descriptor fetch fails with a non-recoverable error, close
9885 all pending SOCKS requests for that .onion. Fixes bug 23653;
9886 bugfix on 0.3.2.1-alpha.
9888 o Minor bugfixes (hidden service):
9889 - Always regenerate missing hidden service public key files. Prior
9890 to this, if the public key was deleted from disk, it wouldn't get
9891 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
9893 - Make sure that we have a usable ed25519 key when the intro point
9894 relay supports ed25519 link authentication. Fixes bug 24002;
9895 bugfix on 0.3.2.1-alpha.
9897 o Minor bugfixes (hidden service, v2):
9898 - When reloading configured hidden services, copy all information
9899 from the old service object. Previously, some data was omitted,
9900 causing delays in descriptor upload, and other bugs. Fixes bug
9901 23790; bugfix on 0.2.1.9-alpha.
9903 o Minor bugfixes (memory safety, defensive programming):
9904 - Clear the target address when node_get_prim_orport() returns
9905 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9907 o Minor bugfixes (relay):
9908 - Avoid a BUG warning when receiving a dubious CREATE cell while an
9909 option transition is in progress. Fixes bug 23952; bugfix
9912 o Minor bugfixes (testing):
9913 - Adjust the GitLab CI configuration to more closely match that of
9914 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
9915 - Prevent scripts/test/coverage from attempting to move gcov output
9916 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
9917 - When running unit tests as root, skip a test that would fail
9918 because it expects a permissions error. This affects some
9919 continuous integration setups. Fixes bug 23758; bugfix
9921 - Stop unconditionally mirroring the tor repository in GitLab CI.
9922 This prevented developers from enabling GitLab CI on master. Fixes
9923 bug 23755; bugfix on 0.3.2.2-alpha.
9924 - Fix the hidden service v3 descriptor decoding fuzzing to use the
9925 latest decoding API correctly. Fixes bug 21509; bugfix
9928 o Minor bugfixes (warnings):
9929 - When we get an HTTP request on a SOCKS port, tell the user about
9930 the new HTTPTunnelPort option. Previously, we would give a "Tor is
9931 not an HTTP Proxy" message, which stopped being true when
9932 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
9936 Changes in version 0.2.5.15 - 2017-10-25
9937 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
9938 series. It also adds a new directory authority, Bastet.
9940 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9941 2018. If you need a release with long-term support, please upgrade to
9942 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9944 o Directory authority changes:
9945 - Add "Bastet" as a ninth directory authority to the default list.
9946 Closes ticket 23910.
9947 - The directory authority "Longclaw" has changed its IP address.
9948 Closes ticket 23592.
9950 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9951 - Avoid an assertion failure bug affecting our implementation of
9952 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9953 handling of "0xx" differs from what we had expected. Fixes bug
9954 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9956 o Minor features (geoip):
9957 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9960 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9961 - Fix a memset() off the end of an array when packing cells. This
9962 bug should be harmless in practice, since the corrupted bytes are
9963 still in the same structure, and are always padding bytes,
9964 ignored, or immediately overwritten, depending on compiler
9965 behavior. Nevertheless, because the memset()'s purpose is to make
9966 sure that any other cell-handling bugs can't expose bytes to the
9967 network, we need to fix it. Fixes bug 22737; bugfix on
9968 0.2.4.11-alpha. Fixes CID 1401591.
9970 o Build features (backport from 0.3.1.5-alpha):
9971 - Tor's repository now includes a Travis Continuous Integration (CI)
9972 configuration file (.travis.yml). This is meant to help new
9973 developers and contributors who fork Tor to a Github repository be
9974 better able to test their changes, and understand what we expect
9975 to pass. To use this new build feature, you must fork Tor to your
9976 Github account, then go into the "Integrations" menu in the
9977 repository settings for your fork and enable Travis, then push
9978 your changes. Closes ticket 22636.
9981 Changes in version 0.2.8.16 - 2017-10-25
9982 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
9983 series, including a bugfix for a crash issue that had affected relays
9984 under memory pressure. It also adds a new directory authority, Bastet.
9986 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9987 2018. If you need a release with long-term support, please stick with
9988 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9990 o Directory authority changes:
9991 - Add "Bastet" as a ninth directory authority to the default list.
9992 Closes ticket 23910.
9993 - The directory authority "Longclaw" has changed its IP address.
9994 Closes ticket 23592.
9996 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9997 - Fix a timing-based assertion failure that could occur when the
9998 circuit out-of-memory handler freed a connection's output buffer.
9999 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10001 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10002 - Remove longclaw's IPv6 address, as it will soon change. Authority
10003 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10004 3/8 directory authorities with IPv6 addresses, but there are also
10005 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10007 o Minor features (geoip):
10008 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10012 Changes in version 0.2.9.13 - 2017-10-25
10013 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
10014 series, including a bugfix for a crash issue that had affected relays
10015 under memory pressure. It also adds a new directory authority, Bastet.
10017 o Directory authority changes:
10018 - Add "Bastet" as a ninth directory authority to the default list.
10019 Closes ticket 23910.
10020 - The directory authority "Longclaw" has changed its IP address.
10021 Closes ticket 23592.
10023 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10024 - Fix a timing-based assertion failure that could occur when the
10025 circuit out-of-memory handler freed a connection's output buffer.
10026 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10028 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10029 - Remove longclaw's IPv6 address, as it will soon change. Authority
10030 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10031 3/8 directory authorities with IPv6 addresses, but there are also
10032 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10034 o Minor features (geoip):
10035 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10038 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10039 - When a directory authority rejects a descriptor or extrainfo with
10040 a given digest, mark that digest as undownloadable, so that we do
10041 not attempt to download it again over and over. We previously
10042 tried to avoid downloading such descriptors by other means, but we
10043 didn't notice if we accidentally downloaded one anyway. This
10044 behavior became problematic in 0.2.7.2-alpha, when authorities
10045 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10048 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10049 - Clear the address when node_get_prim_orport() returns early.
10050 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10052 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10053 - When running as a Windows service, set the ID of the main thread
10054 correctly. Failure to do so made us fail to send log messages to
10055 the controller in 0.2.1.16-rc, slowed down controller event
10056 delivery in 0.2.7.3-rc and later, and crash with an assertion
10057 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10058 Patch and diagnosis from "Vort".
10061 Changes in version 0.3.0.12 - 2017-10-25
10062 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
10063 series, including a bugfix for a crash issue that had affected relays
10064 under memory pressure. It also adds a new directory authority, Bastet.
10066 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
10067 2018. If you need a release with long-term support, please stick with
10068 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10070 o Directory authority changes:
10071 - Add "Bastet" as a ninth directory authority to the default list.
10072 Closes ticket 23910.
10073 - The directory authority "Longclaw" has changed its IP address.
10074 Closes ticket 23592.
10076 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10077 - Fix a timing-based assertion failure that could occur when the
10078 circuit out-of-memory handler freed a connection's output buffer.
10079 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10081 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10082 - Remove longclaw's IPv6 address, as it will soon change. Authority
10083 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10084 3/8 directory authorities with IPv6 addresses, but there are also
10085 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10087 o Minor features (geoip):
10088 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10091 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10092 - When a directory authority rejects a descriptor or extrainfo with
10093 a given digest, mark that digest as undownloadable, so that we do
10094 not attempt to download it again over and over. We previously
10095 tried to avoid downloading such descriptors by other means, but we
10096 didn't notice if we accidentally downloaded one anyway. This
10097 behavior became problematic in 0.2.7.2-alpha, when authorities
10098 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10101 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10102 - Avoid a possible double close of a circuit by the intro point on
10103 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10104 bugfix on 0.3.0.1-alpha.
10106 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10107 - Clear the address when node_get_prim_orport() returns early.
10108 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10110 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10111 - When running as a Windows service, set the ID of the main thread
10112 correctly. Failure to do so made us fail to send log messages to
10113 the controller in 0.2.1.16-rc, slowed down controller event
10114 delivery in 0.2.7.3-rc and later, and crash with an assertion
10115 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10116 Patch and diagnosis from "Vort".
10119 Changes in version 0.3.1.8 - 2017-10-25
10120 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
10121 It includes several bugfixes, including a bugfix for a crash issue
10122 that had affected relays under memory pressure. It also adds
10123 a new directory authority, Bastet.
10125 o Directory authority changes:
10126 - Add "Bastet" as a ninth directory authority to the default list.
10127 Closes ticket 23910.
10128 - The directory authority "Longclaw" has changed its IP address.
10129 Closes ticket 23592.
10131 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10132 - Fix a timing-based assertion failure that could occur when the
10133 circuit out-of-memory handler freed a connection's output buffer.
10134 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10136 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10137 - Remove longclaw's IPv6 address, as it will soon change. Authority
10138 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10139 3/8 directory authorities with IPv6 addresses, but there are also
10140 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10142 o Minor features (geoip):
10143 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10146 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
10147 - Fix a compilation warning when building with zstd support on
10148 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10149 and fixed by Andreas Stieger.
10151 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
10152 - Handle a pathological case when decompressing Zstandard data when
10153 the output buffer size is zero. Fixes bug 23551; bugfix
10156 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
10157 - Remove the length limit on HTTP status lines that authorities can
10158 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
10160 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10161 - Avoid a possible double close of a circuit by the intro point on
10162 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10163 bugfix on 0.3.0.1-alpha.
10165 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10166 - Clear the address when node_get_prim_orport() returns early.
10167 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10169 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
10170 - Fix additional channelpadding unit test failures by using mocked
10171 time instead of actual time for all tests. Fixes bug 23608; bugfix
10175 Changes in version 0.3.2.2-alpha - 2017-09-29
10176 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
10177 release fixes several minor bugs in the new scheduler and next-
10178 generation onion services; both features were newly added in the 0.3.2
10179 series. Other fixes in this alpha include several fixes for non-fatal
10180 tracebacks which would appear in logs.
10182 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
10183 alpha does not contain any substantial new features. Minor features
10184 include better testing and logging.
10186 The following comprises the complete list of changes included
10189 o Major bugfixes (relay, crash, assertion failure):
10190 - Fix a timing-based assertion failure that could occur when the
10191 circuit out-of-memory handler freed a connection's output buffer.
10192 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10194 o Major bugfixes (scheduler):
10195 - If a channel is put into the scheduler's pending list, then it
10196 starts closing, and then if the scheduler runs before it finishes
10197 closing, the scheduler will get stuck trying to flush its cells
10198 while the lower layers refuse to cooperate. Fix that race
10199 condition by giving the scheduler an escape method. Fixes bug
10200 23676; bugfix on 0.3.2.1-alpha.
10202 o Minor features (build, compilation):
10203 - The "check-changes" feature is now part of the "make check" tests;
10204 we'll use it to try to prevent misformed changes files from
10205 accumulating. Closes ticket 23564.
10206 - Tor builds should now fail if there are any mismatches between the
10207 C type representing a configuration variable and the C type the
10208 data-driven parser uses to store a value there. Previously, we
10209 needed to check these by hand, which sometimes led to mistakes.
10210 Closes ticket 23643.
10212 o Minor features (directory authorities):
10213 - Remove longclaw's IPv6 address, as it will soon change. Authority
10214 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10215 3/8 directory authorities with IPv6 addresses, but there are also
10216 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10218 o Minor features (hidden service, circuit, logging):
10219 - Improve logging of many callsite in the circuit subsystem to print
10220 the circuit identifier(s).
10221 - Log when we cleanup an intro point from a service so we know when
10222 and for what reason it happened. Closes ticket 23604.
10224 o Minor features (logging):
10225 - Log more circuit information whenever we are about to try to
10226 package a relay cell on a circuit with a nonexistent n_chan.
10227 Attempt to diagnose ticket 8185.
10228 - Improve info-level log identification of particular circuits, to
10229 help with debugging. Closes ticket 23645.
10231 o Minor features (relay):
10232 - When choosing which circuits can be expired as unused, consider
10233 circuits from clients even if those clients used regular CREATE
10234 cells to make them; and do not consider circuits from relays even
10235 if they were made with CREATE_FAST. Part of ticket 22805.
10237 o Minor features (robustness):
10238 - Change several fatal assertions when flushing buffers into non-
10239 fatal assertions, to prevent any recurrence of 23690.
10241 o Minor features (spec conformance, bridge, diagnostic):
10242 - When handling the USERADDR command on an ExtOrPort, warn when the
10243 transports provides a USERADDR with no port. In a future version,
10244 USERADDR commands of this format may be rejected. Detects problems
10245 related to ticket 23080.
10247 o Minor features (testing):
10248 - Add a unit test to make sure that our own generated platform
10249 string will be accepted by directory authorities. Closes
10252 o Minor bugfixes (bootstrapping):
10253 - When warning about state file clock skew, report the correct
10254 direction for the detected skew. Fixes bug 23606; bugfix
10256 - Avoid an assertion failure when logging a state file clock skew
10257 very early in bootstrapping. Fixes bug 23607; bugfix
10260 o Minor bugfixes (build, compilation):
10261 - Fix a compilation warning when building with zstd support on
10262 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10263 and fixed by Andreas Stieger.
10264 - When searching for OpenSSL, don't accept any OpenSSL library that
10265 lacks TLSv1_1_method(): Tor doesn't build with those versions.
10266 Additionally, look in /usr/local/opt/openssl, if it's present.
10267 These changes together repair the default build on OSX systems
10268 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
10270 o Minor bugfixes (compression):
10271 - Handle a pathological case when decompressing Zstandard data when
10272 the output buffer size is zero. Fixes bug 23551; bugfix
10275 o Minor bugfixes (documentation):
10276 - Fix manpage to not refer to the obsolete (and misspelled)
10277 UseEntryGuardsAsDirectoryGuards parameter in the description of
10278 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
10280 o Minor bugfixes (hidden service v3):
10281 - Don't log an assertion failure when we can't find the right
10282 information to extend to an introduction point. In rare cases,
10283 this could happen, causing a warning, even though tor would
10284 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
10285 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
10286 much bigger so the rendezvous point can't distinguish which hidden
10287 service protocol is being used. Fixes bug 23420; bugfix
10290 o Minor bugfixes (hidden service, relay):
10291 - Avoid a possible double close of a circuit by the intro point on
10292 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10293 bugfix on 0.3.0.1-alpha.
10295 o Minor bugfixes (logging, relay shutdown, annoyance):
10296 - When a circuit is marked for close, do not attempt to package any
10297 cells for channels on that circuit. Previously, we would detect
10298 this condition lower in the call stack, when we noticed that the
10299 circuit had no attached channel, and log an annoying message.
10300 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10302 o Minor bugfixes (scheduler):
10303 - When switching schedulers due to a consensus change, we didn't
10304 give the new scheduler a chance to react to the consensus. Fix
10305 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
10306 - Make the KISTSchedRunInterval option a non negative value. With
10307 this, the way to disable KIST through the consensus is to set it
10308 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
10309 - Only notice log the selected scheduler when we switch scheduler
10310 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
10311 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
10312 by a different tv_usec data type. Fixes bug 23575; bugfix
10314 - Make a hard exit if tor is unable to pick a scheduler which can
10315 happen if the user specifies a scheduler type that is not
10316 supported and not other types in Schedulers. Fixes bug 23581;
10317 bugfix on 0.3.2.1-alpha.
10318 - Properly initialize the scheduler last run time counter so it is
10319 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
10321 o Minor bugfixes (testing):
10322 - Capture and detect several "Result does not fit" warnings in unit
10323 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
10325 - Fix additional channelpadding unit test failures by using mocked
10326 time instead of actual time for all tests. Fixes bug 23608; bugfix
10328 - The removal of some old scheduler options caused some tests to
10329 fail on BSD systems. Assume current behavior is correct and make
10330 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
10332 o Code simplification and refactoring:
10333 - Remove various ways of testing circuits and connections for
10334 "clientness"; instead, favor channel_is_client(). Part of
10337 o Deprecated features:
10338 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
10339 now deprecated; they do not apply to relays, and they have had no
10340 effect on clients since 0.2.8.x. Closes ticket 19704.
10343 - HiddenServiceVersion man page entry wasn't mentioning the now
10344 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
10345 - Clarify that the Address option is entirely about setting an
10346 advertised IPv4 address. Closes ticket 18891.
10347 - Clarify the manpage's use of the term "address" to clarify what
10348 kind of address is intended. Closes ticket 21405.
10349 - Document that onion service subdomains are allowed, and ignored.
10350 Closes ticket 18736.
10353 Changes in version 0.3.2.1-alpha - 2017-09-18
10354 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
10355 includes support for our next-generation ("v3") onion service
10356 protocol, and adds a new circuit scheduler for more responsive
10357 forwarding decisions from relays. There are also numerous other small
10358 features and bugfixes here.
10360 Below are the changes since Tor 0.3.1.7.
10362 o Major feature (scheduler, channel):
10363 - Tor now uses new schedulers to decide which circuits should
10364 deliver cells first, in order to improve congestion at relays. The
10365 first type is called "KIST" ("Kernel Informed Socket Transport"),
10366 and is only available on Linux-like systems: it uses feedback from
10367 the kernel to prevent the kernel's TCP buffers from growing too
10368 full. The second new scheduler type is called "KISTLite": it
10369 behaves the same as KIST, but runs on systems without kernel
10370 support for inspecting TCP implementation details. The old
10371 scheduler is still available, under the name "Vanilla". To change
10372 the default scheduler preference order, use the new "Schedulers"
10373 option. (The default preference order is "KIST,KISTLite,Vanilla".)
10375 Matt Traudt implemented KIST, based on research by Rob Jansen,
10376 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
10377 more information, see the design paper at
10378 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
10379 followup implementation paper at https://arxiv.org/abs/1709.01044.
10380 Closes ticket 12541.
10382 o Major features (next-generation onion services):
10383 - Tor now supports the next-generation onion services protocol for
10384 clients and services! As part of this release, the core of
10385 proposal 224 has been implemented and is available for
10386 experimentation and testing by our users. This newer version of
10387 onion services ("v3") features many improvements over the legacy
10390 a) Better crypto (replaced SHA1/DH/RSA1024
10391 with SHA3/ed25519/curve25519)
10393 b) Improved directory protocol, leaking much less information to
10396 c) Improved directory protocol, with smaller surface for
10399 d) Better onion address security against impersonation.
10401 e) More extensible introduction/rendezvous protocol.
10403 f) A cleaner and more modular codebase.
10405 You can identify a next-generation onion address by its length:
10406 they are 56 characters long, as in
10407 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
10409 In the future, we will release more options and features for v3
10410 onion services, but we first need a testing period, so that the
10411 current codebase matures and becomes more robust. Planned features
10412 include: offline keys, advanced client authorization, improved
10413 guard algorithms, and statistics. For full details, see
10416 Legacy ("v2") onion services will still work for the foreseeable
10417 future, and will remain the default until this new codebase gets
10418 tested and hardened. Service operators who want to experiment with
10419 the new system can use the 'HiddenServiceVersion 3' torrc
10420 directive along with the regular onion service configuration
10421 options. We will publish a blog post about this new feature
10424 o Major bugfixes (usability, control port):
10425 - Report trusted clock skew indications as bootstrap errors, so
10426 controllers can more easily alert users when their clocks are
10427 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
10429 o Minor features (bug detection):
10430 - Log a warning message with a stack trace for any attempt to call
10431 get_options() during option validation. This pattern has caused
10432 subtle bugs in the past. Closes ticket 22281.
10434 o Minor features (client):
10435 - You can now use Tor as a tunneled HTTP proxy: use the new
10436 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
10437 requests. Closes ticket 22407.
10438 - Add an extra check to make sure that we always use the newer guard
10439 selection code for picking our guards. Closes ticket 22779.
10440 - When downloading (micro)descriptors, don't split the list into
10441 multiple requests unless we want at least 32 descriptors.
10442 Previously, we split at 4, not 32, which led to significant
10443 overhead in HTTP request size and degradation in compression
10444 performance. Closes ticket 23220.
10446 o Minor features (command line):
10447 - Add a new commandline option, --key-expiration, which prints when
10448 the current signing key is going to expire. Implements ticket
10449 17639; patch by Isis Lovecruft.
10451 o Minor features (control port):
10452 - If an application tries to use the control port as an HTTP proxy,
10453 respond with a meaningful "This is the Tor control port" message,
10454 and log the event. Closes ticket 1667. Patch from Ravi
10456 - Provide better error message for GETINFO desc/(id|name) when not
10457 fetching router descriptors. Closes ticket 5847. Patch by
10459 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
10460 whether Tor will try to download router descriptors and
10461 microdescriptors respectively. Closes ticket 22684.
10462 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
10463 so controllers can tell whether the geoip databases are loaded.
10464 Closes ticket 23237.
10465 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
10466 events. Closes ticket 19254. Patch by "DonnchaC".
10468 o Minor features (development support):
10469 - Developers can now generate a call-graph for Tor using the
10470 "calltool" python program, which post-processes object dumps. It
10471 should work okay on many Linux and OSX platforms, and might work
10472 elsewhere too. To run it, install calltool from
10473 https://gitweb.torproject.org/user/nickm/calltool.git and run
10474 "make callgraph". Closes ticket 19307.
10476 o Minor features (ed25519):
10477 - Add validation function to checks for torsion components in
10478 ed25519 public keys, used by prop224 client-side code. Closes
10479 ticket 22006. Math help by Ian Goldberg.
10481 o Minor features (exit relay, DNS):
10482 - Improve the clarity and safety of the log message from evdns when
10483 receiving an apparently spoofed DNS reply. Closes ticket 3056.
10485 o Minor features (integration, hardening):
10486 - Add a new NoExec option to prevent Tor from running other
10487 programs. When this option is set to 1, Tor will never try to run
10488 another program, regardless of the settings of
10489 PortForwardingHelper, ClientTransportPlugin, or
10490 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
10491 without restarting Tor. Closes ticket 22976.
10493 o Minor features (logging):
10494 - Improve the warning message for specifying a relay by nickname.
10495 The previous message implied that nickname registration was still
10496 part of the Tor network design, which it isn't. Closes
10498 - If the sandbox filter fails to load, suggest to the user that
10499 their kernel might not support seccomp2. Closes ticket 23090.
10501 o Minor features (portability):
10502 - Check at configure time whether uint8_t is the same type as
10503 unsigned char. Lots of existing code already makes this
10504 assumption, and there could be strict aliasing issues if the
10505 assumption is violated. Closes ticket 22410.
10507 o Minor features (relay, configuration):
10508 - Reject attempts to use relative file paths when RunAsDaemon is
10509 set. Previously, Tor would accept these, but the directory-
10510 changing step of RunAsDaemon would give strange and/or confusing
10511 results. Closes ticket 22731.
10513 o Minor features (startup, safety):
10514 - When configured to write a PID file, Tor now exits if it is unable
10515 to do so. Previously, it would warn and continue. Closes
10518 o Minor features (static analysis):
10519 - The BUG() macro has been changed slightly so that Coverity no
10520 longer complains about dead code if the bug is impossible. Closes
10523 o Minor features (testing):
10524 - The default chutney network tests now include tests for the v3
10525 hidden service design. Make sure you have the latest version of
10526 chutney if you want to run these. Closes ticket 22437.
10527 - Add a unit test to verify that we can parse a hardcoded v2 hidden
10528 service descriptor. Closes ticket 15554.
10530 o Minor bugfixes (certificate handling):
10531 - Fix a time handling bug in Tor certificates set to expire after
10532 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
10533 Coverity as CID 1415728.
10535 o Minor bugfixes (client, usability):
10536 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
10537 SOCKS4a requests that contain IP address strings, even when
10538 SafeSocks in enabled, as this prevents user from connecting to
10539 known IP addresses without relying on DNS for resolving. SafeSocks
10540 still rejects SOCKS connections that connect to IP addresses when
10541 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
10542 bugfix on Tor 0.2.6.2-alpha.
10544 o Minor bugfixes (code correctness):
10545 - Call htons() in extend_cell_format() for encoding a 16-bit value.
10546 Previously we used ntohs(), which happens to behave the same on
10547 all the platforms we support, but which isn't really correct.
10548 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
10549 - For defense-in-depth, make the controller's write_escaped_data()
10550 function robust to extremely long inputs. Fixes bug 19281; bugfix
10551 on 0.1.1.1-alpha. Reported by Guido Vranken.
10553 o Minor bugfixes (compilation):
10554 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
10555 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10557 o Minor bugfixes (consensus expiry):
10558 - Check for adequate directory information correctly. Previously, Tor
10559 would reconsider whether it had sufficient directory information
10560 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
10562 o Minor bugfixes (directory protocol):
10563 - Directory servers now include a "Date:" http header for response
10564 codes other than 200. Clients starting with a skewed clock and a
10565 recent consensus were getting "304 Not modified" responses from
10566 directory authorities, so without the Date header, the client
10567 would never hear about a wrong clock. Fixes bug 23499; bugfix
10569 - Make clients wait for 6 seconds before trying to download a
10570 consensus from an authority. Fixes bug 17750; bugfix
10573 o Minor bugfixes (DoS-resistance):
10574 - If future code asks if there are any running bridges, without
10575 checking if bridges are enabled, log a BUG warning rather than
10576 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
10578 o Minor bugfixes (format strictness):
10579 - Restrict several data formats to decimal. Previously, the
10580 BuildTimeHistogram entries in the state file, the "bw=" entries in
10581 the bandwidth authority file, and the process IDs passed to the
10582 __OwningControllerProcess option could all be specified in hex or
10583 octal as well as in decimal. This was not an intentional feature.
10584 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
10587 o Minor bugfixes (heartbeat):
10588 - If we fail to write a heartbeat message, schedule a retry for the
10589 minimum heartbeat interval number of seconds in the future. Fixes
10590 bug 19476; bugfix on 0.2.3.1-alpha.
10592 o Minor bugfixes (linux seccomp2 sandbox, logging):
10593 - Fix some messages on unexpected errors from the seccomp2 library.
10594 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
10596 o Minor bugfixes (logging):
10597 - Remove duplicate log messages regarding opening non-local
10598 SocksPorts upon parsing config and opening listeners at startup.
10599 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
10600 - Use a more comprehensible log message when telling the user
10601 they've excluded every running exit node. Fixes bug 7890; bugfix
10603 - When logging the number of descriptors we intend to download per
10604 directory request, do not log a number higher than then the number
10605 of descriptors we're fetching in total. Fixes bug 19648; bugfix
10607 - When warning about a directory owned by the wrong user, log the
10608 actual name of the user owning the directory. Previously, we'd log
10609 the name of the process owner twice. Fixes bug 23487; bugfix
10611 - The tor specification says hop counts are 1-based, so fix two log
10612 messages that mistakenly logged 0-based hop counts. Fixes bug
10613 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
10614 Credit to Xiaofan Li for reporting this issue.
10616 o Minor bugfixes (portability):
10617 - Stop using the PATH_MAX variable, which is not defined on GNU
10618 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
10620 o Minor bugfixes (relay):
10621 - When uploading our descriptor for the first time after startup,
10622 report the reason for uploading as "Tor just started" rather than
10623 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
10624 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10625 relays, to prevent spurious address resolutions and descriptor
10626 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10627 bugfix on in 0.2.8.1-alpha.
10629 o Minor bugfixes (tests):
10630 - Fix a broken unit test for the OutboundAddress option: the parsing
10631 function was never returning an error on failure. Fixes bug 23366;
10632 bugfix on 0.3.0.3-alpha.
10633 - Fix a signed-integer overflow in the unit tests for
10634 dir/download_status_random_backoff, which was untriggered until we
10635 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
10637 o Minor bugfixes (usability, control port):
10638 - Stop making an unnecessary routerlist check in NETINFO clock skew
10639 detection; this was preventing clients from reporting NETINFO clock
10640 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
10642 o Code simplification and refactoring:
10643 - Extract the code for handling newly-open channels into a separate
10644 function from the general code to handle channel state
10645 transitions. This change simplifies our callgraph, reducing the
10646 size of the largest strongly connected component by roughly a
10647 factor of two. Closes ticket 22608.
10648 - Remove dead code for largely unused statistics on the number of
10649 times we've attempted various public key operations. Fixes bug
10650 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
10651 - Remove several now-obsolete functions for asking about old
10652 variants directory authority status. Closes ticket 22311; patch
10654 - Remove some of the code that once supported "Named" and "Unnamed"
10655 routers. Authorities no longer vote for these flags. Closes
10657 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
10658 and old hidden services, to indicate that they aren't suitable for
10659 new protocols or formats. Closes ticket 23026.
10660 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
10661 22521. Patch from Neel Chauhan.
10662 - Split the enormous circuit_send_next_onion_skin() function into
10663 multiple subfunctions. Closes ticket 22804.
10664 - Split the portions of the buffer.c module that handle particular
10665 protocols into separate modules. Part of ticket 23149.
10666 - Use our test macros more consistently, to produce more useful
10667 error messages when our unit tests fail. Add coccinelle patches to
10668 allow us to re-check for test macro uses. Closes ticket 22497.
10670 o Deprecated features:
10671 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
10672 only applies to direct unencrypted HTTP connections to your
10673 directory server, which your Tor probably isn't using. Closes
10677 - Clarify in the manual that "Sandbox 1" is only supported on Linux
10678 kernels. Closes ticket 22677.
10679 - Document all values of PublishServerDescriptor in the manpage.
10680 Closes ticket 15645.
10681 - Improve the documentation for the directory port part of the
10682 DirAuthority line. Closes ticket 20152.
10683 - Restore documentation for the authorities' "approved-routers"
10684 file. Closes ticket 21148.
10686 o Removed features:
10687 - The AllowDotExit option has been removed as unsafe. It has been
10688 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
10689 - The ClientDNSRejectInternalAddresses flag can no longer be set on
10690 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
10691 Closes ticket 21031.
10692 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
10693 nobody was using it any longer. Closes ticket 22377.
10696 Changes in version 0.2.8.15 - 2017-09-18
10697 Tor 0.2.8.15 backports a collection of bugfixes from later
10700 Most significantly, it includes a fix for TROVE-2017-008, a
10701 security bug that affects hidden services running with the
10702 SafeLogging option disabled. For more information, see
10703 https://trac.torproject.org/projects/tor/ticket/23490
10705 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
10706 2018. We suggest that you upgrade to the latest stable release if
10707 possible. If you can't, we recommend that you upgrade at least to
10708 0.2.9, which will be supported until 2020.
10710 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10711 - Avoid an assertion failure bug affecting our implementation of
10712 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10713 handling of "0xx" differs from what we had expected. Fixes bug
10714 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10717 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10720 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10721 - Backport a fix for an "unused variable" warning that appeared
10722 in some versions of mingw. Fixes bug 22838; bugfix on
10725 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10726 - Fix a memset() off the end of an array when packing cells. This
10727 bug should be harmless in practice, since the corrupted bytes are
10728 still in the same structure, and are always padding bytes,
10729 ignored, or immediately overwritten, depending on compiler
10730 behavior. Nevertheless, because the memset()'s purpose is to make
10731 sure that any other cell-handling bugs can't expose bytes to the
10732 network, we need to fix it. Fixes bug 22737; bugfix on
10733 0.2.4.11-alpha. Fixes CID 1401591.
10735 o Build features (backport from 0.3.1.5-alpha):
10736 - Tor's repository now includes a Travis Continuous Integration (CI)
10737 configuration file (.travis.yml). This is meant to help new
10738 developers and contributors who fork Tor to a Github repository be
10739 better able to test their changes, and understand what we expect
10740 to pass. To use this new build feature, you must fork Tor to your
10741 Github account, then go into the "Integrations" menu in the
10742 repository settings for your fork and enable Travis, then push
10743 your changes. Closes ticket 22636.
10746 Changes in version 0.2.9.12 - 2017-09-18
10747 Tor 0.2.9.12 backports a collection of bugfixes from later
10750 Most significantly, it includes a fix for TROVE-2017-008, a
10751 security bug that affects hidden services running with the
10752 SafeLogging option disabled. For more information, see
10753 https://trac.torproject.org/projects/tor/ticket/23490
10755 o Major features (security, backport from 0.3.0.2-alpha):
10756 - Change the algorithm used to decide DNS TTLs on client and server
10757 side, to better resist DNS-based correlation attacks like the
10758 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10759 Feamster. Now relays only return one of two possible DNS TTL
10760 values, and clients are willing to believe DNS TTL values up to 3
10761 hours long. Closes ticket 19769.
10763 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
10764 - Fix a rare crash when sending a begin cell on a circuit whose
10765 linked directory connection had already been closed. Fixes bug
10766 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
10768 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
10769 - Fix a bug that prevented exit nodes from caching DNS records for
10770 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10772 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10773 - Fix a typo that had prevented TPROXY-based transparent proxying
10774 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10775 Patch from "d4fq0fQAgoJ".
10777 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10778 - Avoid an assertion failure bug affecting our implementation of
10779 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10780 handling of "0xx" differs from what we had expected. Fixes bug
10781 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10783 o Minor features (code style, backport from 0.3.1.3-alpha):
10784 - Add "Falls through" comments to our codebase, in order to silence
10785 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10786 Stieger. Closes ticket 22446.
10788 o Minor features (geoip):
10789 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10792 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
10793 - Roll over monthly accounting at the configured hour and minute,
10794 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10795 Found by Andrey Karpov with PVS-Studio.
10797 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
10798 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10799 bugfix on 0.2.8.1-alpha.
10800 - Fix warnings when building with libscrypt and openssl scrypt support
10801 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10802 - When building with certain versions the mingw C header files, avoid
10803 float-conversion warnings when calling the C functions isfinite(),
10804 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
10806 o Minor bugfixes (compilation, backport from 0.3.1.7):
10807 - Avoid compiler warnings in the unit tests for running tor_sscanf()
10808 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10810 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10811 - Backport a fix for an "unused variable" warning that appeared
10812 in some versions of mingw. Fixes bug 22838; bugfix on
10815 o Minor bugfixes (controller, backport from 0.3.1.7):
10816 - Do not crash when receiving a HSPOST command with an empty body.
10817 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10818 - Do not crash when receiving a POSTDESCRIPTOR command with an
10819 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10821 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10822 - Avoid Coverity build warnings related to our BUG() macro. By
10823 default, Coverity treats BUG() as the Linux kernel does: an
10824 instant abort(). We need to override that so our BUG() macro
10825 doesn't prevent Coverity from analyzing functions that use it.
10826 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10828 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10829 - Fix a memset() off the end of an array when packing cells. This
10830 bug should be harmless in practice, since the corrupted bytes are
10831 still in the same structure, and are always padding bytes,
10832 ignored, or immediately overwritten, depending on compiler
10833 behavior. Nevertheless, because the memset()'s purpose is to make
10834 sure that any other cell-handling bugs can't expose bytes to the
10835 network, we need to fix it. Fixes bug 22737; bugfix on
10836 0.2.4.11-alpha. Fixes CID 1401591.
10838 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10839 - When setting the maximum number of connections allowed by the OS,
10840 always allow some extra file descriptors for other files. Fixes
10841 bug 22797; bugfix on 0.2.0.10-alpha.
10843 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10844 - Avoid a sandbox failure when trying to re-bind to a socket and
10845 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10847 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10848 - Permit the fchmod system call, to avoid crashing on startup when
10849 starting with the seccomp2 sandbox and an unexpected set of
10850 permissions on the data directory or its contents. Fixes bug
10851 22516; bugfix on 0.2.5.4-alpha.
10853 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
10854 - Avoid a double-marked-circuit warning that could happen when we
10855 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
10858 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10859 - Reject version numbers with non-numeric prefixes (such as +, -, or
10860 whitespace). Disallowing whitespace prevents differential version
10861 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10862 and part of 21508; bugfix on 0.0.8pre1.
10864 o Build features (backport from 0.3.1.5-alpha):
10865 - Tor's repository now includes a Travis Continuous Integration (CI)
10866 configuration file (.travis.yml). This is meant to help new
10867 developers and contributors who fork Tor to a Github repository be
10868 better able to test their changes, and understand what we expect
10869 to pass. To use this new build feature, you must fork Tor to your
10870 Github account, then go into the "Integrations" menu in the
10871 repository settings for your fork and enable Travis, then push
10872 your changes. Closes ticket 22636.
10875 Changes in version 0.3.0.11 - 2017-09-18
10876 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
10879 Most significantly, it includes a fix for TROVE-2017-008, a
10880 security bug that affects hidden services running with the
10881 SafeLogging option disabled. For more information, see
10882 https://trac.torproject.org/projects/tor/ticket/23490
10884 o Minor features (code style, backport from 0.3.1.7):
10885 - Add "Falls through" comments to our codebase, in order to silence
10886 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10887 Stieger. Closes ticket 22446.
10890 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10893 o Minor bugfixes (compilation, backport from 0.3.1.7):
10894 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10895 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10897 o Minor bugfixes (controller, backport from 0.3.1.7):
10898 - Do not crash when receiving a HSPOST command with an empty body.
10899 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10900 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10901 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10903 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10904 - When setting the maximum number of connections allowed by the OS,
10905 always allow some extra file descriptors for other files. Fixes
10906 bug 22797; bugfix on 0.2.0.10-alpha.
10908 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
10909 - Remove a forgotten debugging message when an introduction point
10910 successfully establishes a hidden service prop224 circuit with
10912 - Change three other log_warn() for an introduction point to
10913 protocol warnings, because they can be failure from the network
10914 and are not relevant to the operator. Fixes bug 23078; bugfix on
10915 0.3.0.1-alpha and 0.3.0.2-alpha.
10918 Changes in version 0.3.1.7 - 2017-09-18
10919 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
10921 With the 0.3.1 series, Tor now serves and downloads directory
10922 information in more compact formats, to save on bandwidth overhead. It
10923 also contains a new padding system to resist netflow-based traffic
10924 analysis, and experimental support for building parts of Tor in Rust
10925 (though no parts of Tor are in Rust yet). There are also numerous
10926 small features, bugfixes on earlier release series, and groundwork for
10927 the hidden services revamp of 0.3.2.
10929 This release also includes a fix for TROVE-2017-008, a security bug
10930 that affects hidden services running with the SafeLogging option
10931 disabled. For more information, see
10932 https://trac.torproject.org/projects/tor/ticket/23490
10934 Per our stable release policy, we plan to support each stable release
10935 series for at least the next nine months, or for three months after
10936 the first stable release of the next series: whichever is longer. If
10937 you need a release with long-term support, we recommend that you stay
10938 with the 0.2.9 series.
10940 Below is a list of the changes since 0.3.1.6-rc. For a list of all
10941 changes since 0.3.0, see the ReleaseNotes file.
10943 o Major bugfixes (security, hidden services, loggging):
10944 - Fix a bug where we could log uninitialized stack when a certain
10945 hidden service error occurred while SafeLogging was disabled.
10946 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
10947 TROVE-2017-008 and CVE-2017-0380.
10949 o Minor features (defensive programming):
10950 - Create a pair of consensus parameters, nf_pad_tor2web and
10951 nf_pad_single_onion, to disable netflow padding in the consensus
10952 for non-anonymous connections in case the overhead is high. Closes
10955 o Minor features (diagnostic):
10956 - Add a stack trace to the bug warnings that can be logged when
10957 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
10958 attempt for bug 23105.
10960 o Minor features (geoip):
10961 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10964 o Minor bugfixes (compilation):
10965 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10966 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10968 o Minor bugfixes (controller):
10969 - Do not crash when receiving a HSPOST command with an empty body.
10970 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10971 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10972 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10974 o Minor bugfixes (relay):
10975 - Inform the geoip and rephist modules about all requests, even on
10976 relays that are only fetching microdescriptors. Fixes a bug
10977 related to 21585; bugfix on 0.3.0.1-alpha.
10979 o Minor bugfixes (unit tests):
10980 - Fix a channelpadding unit test failure on slow systems by using
10981 mocked time instead of actual time. Fixes bug 23077; bugfix
10985 Changes in version 0.3.1.6-rc - 2017-09-05
10986 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
10987 release series, including a bug that produced weird behavior on
10988 Windows directory caches.
10990 This is the first release candidate in the Tor 0.3.1 series. If we
10991 find no new bugs or regressions here, the first stable 0.3.1 release
10992 will be nearly identical to it.
10994 o Major bugfixes (windows, directory cache):
10995 - On Windows, do not try to delete cached consensus documents and
10996 diffs before they are unmapped from memory--Windows won't allow
10997 that. Instead, allow the consensus cache directory to grow larger,
10998 to hold files that might need to stay around longer. Fixes bug
10999 22752; bugfix on 0.3.1.1-alpha.
11001 o Minor features (directory authority):
11002 - Improve the message that authorities report to relays that present
11003 RSA/Ed25519 keypairs that conflict with previously pinned keys.
11004 Closes ticket 22348.
11006 o Minor features (geoip):
11007 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
11010 o Minor features (testing):
11011 - Add more tests for compression backend initialization. Closes
11014 o Minor bugfixes (directory cache):
11015 - Fix a memory leak when recovering space in the consensus cache.
11016 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
11018 o Minor bugfixes (hidden service):
11019 - Increase the number of circuits that a service is allowed to
11020 open over a specific period of time. The value was lower than it
11021 should be (8 vs 12) in the normal case of 3 introduction points.
11022 Fixes bug 22159; bugfix on 0.3.0.5-rc.
11023 - Fix a BUG warning during HSv3 descriptor decoding that could be
11024 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
11025 on 0.3.0.1-alpha. Bug found by "haxxpop".
11026 - Rate-limit the log messages if we exceed the maximum number of
11027 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
11029 o Minor bugfixes (logging, relay):
11030 - Remove a forgotten debugging message when an introduction point
11031 successfully establishes a hidden service prop224 circuit with
11033 - Change three other log_warn() for an introduction point to
11034 protocol warnings, because they can be failure from the network
11035 and are not relevant to the operator. Fixes bug 23078; bugfix on
11036 0.3.0.1-alpha and 0.3.0.2-alpha.
11038 o Minor bugfixes (relay):
11039 - When a relay is not running as a directory cache, it will no
11040 longer generate compressed consensuses and consensus diff
11041 information. Previously, this was a waste of disk and CPU. Fixes
11042 bug 23275; bugfix on 0.3.1.1-alpha.
11044 o Minor bugfixes (robustness, error handling):
11045 - Improve our handling of the cases where OpenSSL encounters a
11046 memory error while encoding keys and certificates. We haven't
11047 observed these errors in the wild, but if they do happen, we now
11048 detect and respond better. Fixes bug 19418; bugfix on all versions
11049 of Tor. Reported by Guido Vranken.
11051 o Minor bugfixes (stability):
11052 - Avoid crashing on a double-free when unable to load or process an
11053 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
11054 with the clang static analyzer.
11056 o Minor bugfixes (testing):
11057 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11058 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11059 - Port the hs_ntor handshake test to work correctly with recent
11060 versions of the pysha3 module. Fixes bug 23071; bugfix
11063 o Minor bugfixes (Windows service):
11064 - When running as a Windows service, set the ID of the main thread
11065 correctly. Failure to do so made us fail to send log messages to
11066 the controller in 0.2.1.16-rc, slowed down controller event
11067 delivery in 0.2.7.3-rc and later, and crash with an assertion
11068 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11069 Patch and diagnosis from "Vort".
11072 Changes in version 0.3.0.10 - 2017-08-02
11073 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
11074 from the current Tor alpha series. OpenBSD users and TPROXY users
11075 should upgrade; others are probably okay sticking with 0.3.0.9.
11077 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
11078 - Tor's repository now includes a Travis Continuous Integration (CI)
11079 configuration file (.travis.yml). This is meant to help new
11080 developers and contributors who fork Tor to a Github repository be
11081 better able to test their changes, and understand what we expect
11082 to pass. To use this new build feature, you must fork Tor to your
11083 Github account, then go into the "Integrations" menu in the
11084 repository settings for your fork and enable Travis, then push
11085 your changes. Closes ticket 22636.
11087 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11088 - Fix a typo that had prevented TPROXY-based transparent proxying
11089 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11090 Patch from "d4fq0fQAgoJ".
11092 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11093 - Avoid an assertion failure bug affecting our implementation of
11094 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11095 handling of "0xbar" differs from what we had expected. Fixes bug
11096 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11098 o Minor features (backport from 0.3.1.5-alpha):
11099 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11102 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
11103 - Roll over monthly accounting at the configured hour and minute,
11104 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11105 Found by Andrey Karpov with PVS-Studio.
11107 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
11108 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11109 bugfix on 0.2.8.1-alpha.
11110 - Fix warnings when building with libscrypt and openssl scrypt
11111 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11112 - When building with certain versions of the mingw C header files,
11113 avoid float-conversion warnings when calling the C functions
11114 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11117 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11118 - Backport a fix for an "unused variable" warning that appeared
11119 in some versions of mingw. Fixes bug 22838; bugfix on
11122 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
11123 - Avoid Coverity build warnings related to our BUG() macro. By
11124 default, Coverity treats BUG() as the Linux kernel does: an
11125 instant abort(). We need to override that so our BUG() macro
11126 doesn't prevent Coverity from analyzing functions that use it.
11127 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11129 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
11130 - When rejecting a router descriptor for running an obsolete version
11131 of Tor without ntor support, warn about the obsolete tor version,
11132 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11134 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
11135 - Avoid a sandbox failure when trying to re-bind to a socket and
11136 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11138 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
11139 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11140 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11143 Changes in version 0.3.1.5-alpha - 2017-08-01
11144 Tor 0.3.1.5-alpha improves the performance of consensus diff
11145 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
11146 several other bugs. If no serious bugs are found in this version, the
11147 next version will be a release candidate.
11149 This release also marks the end of support for the Tor 0.2.4.x,
11150 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
11151 further bug or security fixes. Anyone still running or distributing
11152 one of those versions should upgrade.
11154 o Major features (build system, continuous integration):
11155 - Tor's repository now includes a Travis Continuous Integration (CI)
11156 configuration file (.travis.yml). This is meant to help new
11157 developers and contributors who fork Tor to a Github repository be
11158 better able to test their changes, and understand what we expect
11159 to pass. To use this new build feature, you must fork Tor to your
11160 Github account, then go into the "Integrations" menu in the
11161 repository settings for your fork and enable Travis, then push
11162 your changes. Closes ticket 22636.
11164 o Major bugfixes (openbsd, denial-of-service):
11165 - Avoid an assertion failure bug affecting our implementation of
11166 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11167 handling of "0xbar" differs from what we had expected. Fixes bug
11168 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11170 o Major bugfixes (relay, performance):
11171 - Perform circuit handshake operations at a higher priority than we
11172 use for consensus diff creation and compression. This should
11173 prevent circuits from starving when a relay or bridge receives a
11174 new consensus, especially on lower-powered machines. Fixes bug
11175 22883; bugfix on 0.3.1.1-alpha.
11177 o Minor features (bridge authority):
11178 - Add "fingerprint" lines to the networkstatus-bridges file produced
11179 by bridge authorities. Closes ticket 22207.
11181 o Minor features (directory cache, consensus diff):
11182 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
11183 operators with low-resource environments to adjust the number of
11184 consensuses they'll store and generate diffs from. Most cache
11185 operators should leave it unchanged. Helps to work around
11188 o Minor features (geoip):
11189 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11192 o Minor features (relay, performance):
11193 - Always start relays with at least two worker threads, to prevent
11194 priority inversion on slow tasks. Part of the fix for bug 22883.
11195 - Allow background work to be queued with different priorities, so
11196 that a big pile of slow low-priority jobs will not starve out
11197 higher priority jobs. This lays the groundwork for a fix for
11200 o Minor bugfixes (build system, rust):
11201 - Fix a problem where Rust toolchains were not being found when
11202 building without --enable-cargo-online-mode, due to setting the
11203 $HOME environment variable instead of $CARGO_HOME. Fixes bug
11204 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
11206 o Minor bugfixes (compatibility, zstd):
11207 - Write zstd epilogues correctly when the epilogue requires
11208 reallocation of the output buffer, even with zstd 1.3.0.
11209 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
11210 22927; bugfix on 0.3.1.1-alpha.
11212 o Minor bugfixes (compilation warnings):
11213 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
11214 22915; bugfix on 0.2.8.1-alpha.
11215 - Fix warnings when building with libscrypt and openssl scrypt
11216 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11217 - Compile correctly when both openssl 1.1.0 and libscrypt are
11218 detected. Previously this would cause an error. Fixes bug 22892;
11219 bugfix on 0.3.1.1-alpha.
11220 - When building with certain versions of the mingw C header files,
11221 avoid float-conversion warnings when calling the C functions
11222 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11225 o Minor bugfixes (coverity build support):
11226 - Avoid Coverity build warnings related to our BUG() macro. By
11227 default, Coverity treats BUG() as the Linux kernel does: an
11228 instant abort(). We need to override that so our BUG() macro
11229 doesn't prevent Coverity from analyzing functions that use it.
11230 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11232 o Minor bugfixes (directory authority):
11233 - When a directory authority rejects a descriptor or extrainfo with
11234 a given digest, mark that digest as undownloadable, so that we do
11235 not attempt to download it again over and over. We previously
11236 tried to avoid downloading such descriptors by other means, but we
11237 didn't notice if we accidentally downloaded one anyway. This
11238 behavior became problematic in 0.2.7.2-alpha, when authorities
11239 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11242 o Minor bugfixes (error reporting, windows):
11243 - When formatting Windows error messages, use the English format to
11244 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
11247 o Minor bugfixes (file limits, osx):
11248 - When setting the maximum number of connections allowed by the OS,
11249 always allow some extra file descriptors for other files. Fixes
11250 bug 22797; bugfix on 0.2.0.10-alpha.
11252 o Minor bugfixes (linux seccomp2 sandbox):
11253 - Avoid a sandbox failure when trying to re-bind to a socket and
11254 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11256 o Minor bugfixes (memory leaks):
11257 - Fix a small memory leak when validating a configuration that uses
11258 two or more AF_UNIX sockets for the same port type. Fixes bug
11259 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
11261 o Minor bugfixes (unit tests):
11262 - test_consdiff_base64cmp would fail on OS X because while OS X
11263 follows the standard of (less than zero/zero/greater than zero),
11264 it doesn't follow the convention of (-1/0/+1). Make the test
11265 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
11266 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11267 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11270 Changes in version 0.3.1.4-alpha - 2017-06-29
11271 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
11272 to use a guard that was in the same network family as a chosen exit
11273 relay. This is a security regression; all clients running earlier
11274 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
11277 This release also fixes several other bugs introduced in 0.3.0.x
11278 and 0.3.1.x, including others that can affect bandwidth usage
11281 o New dependencies:
11282 - To build with zstd and lzma support, Tor now requires the
11283 pkg-config tool at build time. (This requirement was new in
11284 0.3.1.1-alpha, but was not noted at the time. Noting it here to
11285 close ticket 22623.)
11287 o Major bugfixes (path selection, security):
11288 - When choosing which guard to use for a circuit, avoid the exit's
11289 family along with the exit itself. Previously, the new guard
11290 selection logic avoided the exit, but did not consider its family.
11291 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11292 006 and CVE-2017-0377.
11294 o Major bugfixes (compression, zstd):
11295 - Correctly detect a full buffer when decompressing a large zstd-
11296 compressed input. Previously, we would sometimes treat a full
11297 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
11299 o Major bugfixes (directory protocol):
11300 - Ensure that we send "304 Not modified" as HTTP status code when a
11301 client is attempting to fetch a consensus or consensus diff, and
11302 the best one we can send them is one they already have. Fixes bug
11303 22702; bugfix on 0.3.1.1-alpha.
11305 o Major bugfixes (entry guards):
11306 - When starting with an old consensus, do not add new entry guards
11307 unless the consensus is "reasonably live" (under 1 day old). Fixes
11308 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11310 o Minor features (bug mitigation, diagnostics, logging):
11311 - Avoid an assertion failure, and log a better error message, when
11312 unable to remove a file from the consensus cache on Windows.
11313 Attempts to mitigate and diagnose bug 22752.
11315 o Minor features (geoip):
11316 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11319 o Minor bugfixes (compression):
11320 - When compressing or decompressing a buffer, check for a failure to
11321 create a compression object. Fixes bug 22626; bugfix
11323 - When decompressing a buffer, check for extra data after the end of
11324 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
11325 - When decompressing an object received over an anonymous directory
11326 connection, if we have already decompressed it using an acceptable
11327 compression method, do not reject it for looking like an
11328 unacceptable compression method. Fixes part of bug 22670; bugfix
11330 - When serving directory votes compressed with zlib, do not claim to
11331 have compressed them with zstd. Fixes bug 22669; bugfix
11333 - When spooling compressed data to an output buffer, don't try to
11334 spool more data when there is no more data to spool and we are not
11335 trying to flush the input. Previously, we would sometimes launch
11336 compression requests with nothing to do, which interferes with our
11337 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
11339 o Minor bugfixes (defensive programming):
11340 - Detect and break out of infinite loops in our compression code. We
11341 don't think that any such loops exist now, but it's best to be
11342 safe. Closes ticket 22672.
11343 - Fix a memset() off the end of an array when packing cells. This
11344 bug should be harmless in practice, since the corrupted bytes are
11345 still in the same structure, and are always padding bytes,
11346 ignored, or immediately overwritten, depending on compiler
11347 behavior. Nevertheless, because the memset()'s purpose is to make
11348 sure that any other cell-handling bugs can't expose bytes to the
11349 network, we need to fix it. Fixes bug 22737; bugfix on
11350 0.2.4.11-alpha. Fixes CID 1401591.
11352 o Minor bugfixes (linux seccomp2 sandbox):
11353 - Permit the fchmod system call, to avoid crashing on startup when
11354 starting with the seccomp2 sandbox and an unexpected set of
11355 permissions on the data directory or its contents. Fixes bug
11356 22516; bugfix on 0.2.5.4-alpha.
11357 - Fix a crash in the LZMA module, when the sandbox was enabled, and
11358 liblzma would allocate more than 16 MB of memory. We solve this by
11359 bumping the mprotect() limit in the sandbox module from 16 MB to
11360 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
11362 o Minor bugfixes (logging):
11363 - When decompressing, do not warn if we fail to decompress using a
11364 compression method that we merely guessed. Fixes part of bug
11365 22670; bugfix on 0.1.1.14-alpha.
11366 - When decompressing, treat mismatch between content-encoding and
11367 actual compression type as a protocol warning. Fixes part of bug
11368 22670; bugfix on 0.1.1.9-alpha.
11369 - Downgrade "assigned_to_cpuworker failed" message to info-level
11370 severity. In every case that can reach it, either a better warning
11371 has already been logged, or no warning is warranted. Fixes bug
11372 22356; bugfix on 0.2.6.3-alpha.
11373 - Demote a warn that was caused by libevent delays to info if
11374 netflow padding is less than 4.5 seconds late, or to notice
11375 if it is more (4.5 seconds is the amount of time that a netflow
11376 record might be emitted after, if we chose the maximum timeout).
11377 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
11379 o Minor bugfixes (process behavior):
11380 - When exiting because of an error, always exit with a nonzero exit
11381 status. Previously, we would fail to report an error in our exit
11382 status in cases related to __OwningControllerProcess failure,
11383 lockfile contention, and Ed25519 key initialization. Fixes bug
11384 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
11385 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
11389 - Add a manpage description for the key-pinning-journal file. Closes
11391 - Correctly note that bandwidth accounting values are stored in the
11392 state file, and the bw_accounting file is now obsolete. Closes
11394 - Document more of the files in the Tor data directory, including
11395 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
11396 approved-routers, sr-random, and diff-cache. Found while fixing
11400 Changes in version 0.3.0.9 - 2017-06-29
11401 Tor 0.3.0.9 fixes a path selection bug that would allow a client
11402 to use a guard that was in the same network family as a chosen exit
11403 relay. This is a security regression; all clients running earlier
11404 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
11407 This release also backports several other bugfixes from the 0.3.1.x
11410 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
11411 - When choosing which guard to use for a circuit, avoid the exit's
11412 family along with the exit itself. Previously, the new guard
11413 selection logic avoided the exit, but did not consider its family.
11414 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11415 006 and CVE-2017-0377.
11417 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
11418 - Don't block bootstrapping when a primary bridge is offline and we
11419 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11420 21969; bugfix on 0.3.0.3-alpha.
11422 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
11423 - When starting with an old consensus, do not add new entry guards
11424 unless the consensus is "reasonably live" (under 1 day old). Fixes
11425 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11427 o Minor features (geoip):
11428 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11431 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
11432 - Reject version numbers with non-numeric prefixes (such as +, -, or
11433 whitespace). Disallowing whitespace prevents differential version
11434 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11435 and part of 21508; bugfix on 0.0.8pre1.
11437 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
11438 - Permit the fchmod system call, to avoid crashing on startup when
11439 starting with the seccomp2 sandbox and an unexpected set of
11440 permissions on the data directory or its contents. Fixes bug
11441 22516; bugfix on 0.2.5.4-alpha.
11443 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
11444 - Fix a memset() off the end of an array when packing cells. This
11445 bug should be harmless in practice, since the corrupted bytes are
11446 still in the same structure, and are always padding bytes,
11447 ignored, or immediately overwritten, depending on compiler
11448 behavior. Nevertheless, because the memset()'s purpose is to make
11449 sure that any other cell-handling bugs can't expose bytes to the
11450 network, we need to fix it. Fixes bug 22737; bugfix on
11451 0.2.4.11-alpha. Fixes CID 1401591.
11454 Changes in version 0.3.1.3-alpha - 2017-06-08
11455 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
11456 remotely crash a hidden service with an assertion failure. Anyone
11457 running a hidden service should upgrade to this version, or to some
11458 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11460 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
11461 that sometimes made relays unreliable, as well as several other
11462 bugfixes described below.
11464 o Major bugfixes (hidden service, relay, security):
11465 - Fix a remotely triggerable assertion failure when a hidden service
11466 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11467 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11468 - Fix a remotely triggerable assertion failure caused by receiving a
11469 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11470 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11473 o Major bugfixes (relay, link handshake):
11474 - When performing the v3 link handshake on a TLS connection, report
11475 that we have the x509 certificate that we actually used on that
11476 connection, even if we have changed certificates since that
11477 connection was first opened. Previously, we would claim to have
11478 used our most recent x509 link certificate, which would sometimes
11479 make the link handshake fail. Fixes one case of bug 22460; bugfix
11482 o Major bugfixes (relays, key management):
11483 - Regenerate link and authentication certificates whenever the key
11484 that signs them changes; also, regenerate link certificates
11485 whenever the signed key changes. Previously, these processes were
11486 only weakly coupled, and we relays could (for minutes to hours)
11487 wind up with an inconsistent set of keys and certificates, which
11488 other relays would not accept. Fixes two cases of bug 22460;
11489 bugfix on 0.3.0.1-alpha.
11490 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11491 send the certificate that matches the x509 certificate that we
11492 used on the TLS connection. Previously, there was a race condition
11493 if the TLS context rotated after we began the TLS handshake but
11494 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11497 o Major bugfixes (torrc, crash):
11498 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
11499 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
11501 o Minor features (code style):
11502 - Add "Falls through" comments to our codebase, in order to silence
11503 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11504 Stieger. Closes ticket 22446.
11506 o Minor features (diagnostic):
11507 - Add logging messages to try to diagnose a rare bug that seems to
11508 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
11509 think this is happening because of incorrect system clocks, but
11510 we'd like to know for certain. Diagnostic for bug 22466.
11512 o Minor bugfixes (correctness):
11513 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11514 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11516 o Minor bugfixes (directory protocol):
11517 - Check for libzstd >= 1.1, because older versions lack the
11518 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
11520 o Minor bugfixes (link handshake):
11521 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11522 months, and regenerate it when it is within one month of expiring.
11523 Previously, we had generated this certificate at startup with a
11524 ten-year lifetime, but that could lead to weird behavior when Tor
11525 was started with a grossly inaccurate clock. Mitigates bug 22466;
11526 mitigation on 0.3.0.1-alpha.
11528 o Minor bugfixes (storage directories):
11529 - Always check for underflows in the cached storage directory usage.
11530 If the usage does underflow, re-calculate it. Also, avoid a
11531 separate underflow when the usage is not known. Fixes bug 22424;
11532 bugfix on 0.3.1.1-alpha.
11534 o Minor bugfixes (unit tests):
11535 - The unit tests now pass on systems where localhost is misconfigured
11536 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
11540 - Clarify the manpage for the (deprecated) torify script. Closes
11543 Changes in version 0.3.0.8 - 2017-06-08
11544 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
11545 remotely crash a hidden service with an assertion failure. Anyone
11546 running a hidden service should upgrade to this version, or to some
11547 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11549 Tor 0.3.0.8 also includes fixes for several key management bugs
11550 that sometimes made relays unreliable, as well as several other
11551 bugfixes described below.
11553 o Major bugfixes (hidden service, relay, security, backport
11554 from 0.3.1.3-alpha):
11555 - Fix a remotely triggerable assertion failure when a hidden service
11556 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11557 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11558 - Fix a remotely triggerable assertion failure caused by receiving a
11559 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11560 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11563 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11564 - When performing the v3 link handshake on a TLS connection, report
11565 that we have the x509 certificate that we actually used on that
11566 connection, even if we have changed certificates since that
11567 connection was first opened. Previously, we would claim to have
11568 used our most recent x509 link certificate, which would sometimes
11569 make the link handshake fail. Fixes one case of bug 22460; bugfix
11572 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
11573 - Regenerate link and authentication certificates whenever the key
11574 that signs them changes; also, regenerate link certificates
11575 whenever the signed key changes. Previously, these processes were
11576 only weakly coupled, and we relays could (for minutes to hours)
11577 wind up with an inconsistent set of keys and certificates, which
11578 other relays would not accept. Fixes two cases of bug 22460;
11579 bugfix on 0.3.0.1-alpha.
11580 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11581 send the certificate that matches the x509 certificate that we
11582 used on the TLS connection. Previously, there was a race condition
11583 if the TLS context rotated after we began the TLS handshake but
11584 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11587 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
11588 - Stop rejecting v3 hidden service descriptors because their size
11589 did not match an old padding rule. Fixes bug 22447; bugfix on
11592 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11593 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11594 December 2016 (of which ~126 were still functional) with a list of
11595 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11596 2017. Resolves ticket 21564.
11598 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
11599 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11600 bug 22252; bugfix on 0.2.9.3-alpha.
11602 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11603 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11604 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11606 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
11607 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11608 months, and regenerate it when it is within one month of expiring.
11609 Previously, we had generated this certificate at startup with a
11610 ten-year lifetime, but that could lead to weird behavior when Tor
11611 was started with a grossly inaccurate clock. Mitigates bug 22466;
11612 mitigation on 0.3.0.1-alpha.
11614 o Minor bugfixes (memory leak, directory authority, backport from
11616 - When directory authorities reject a router descriptor due to
11617 keypinning, free the router descriptor rather than leaking the
11618 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11621 Changes in version 0.2.9.11 - 2017-06-08
11622 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
11623 remotely crash a hidden service with an assertion failure. Anyone
11624 running a hidden service should upgrade to this version, or to some
11625 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11626 are not affected by TROVE-2017-004.)
11628 Tor 0.2.9.11 also backports fixes for several key management bugs
11629 that sometimes made relays unreliable, as well as several other
11630 bugfixes described below.
11632 o Major bugfixes (hidden service, relay, security, backport
11633 from 0.3.1.3-alpha):
11634 - Fix a remotely triggerable assertion failure caused by receiving a
11635 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11636 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11639 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11640 - When performing the v3 link handshake on a TLS connection, report
11641 that we have the x509 certificate that we actually used on that
11642 connection, even if we have changed certificates since that
11643 connection was first opened. Previously, we would claim to have
11644 used our most recent x509 link certificate, which would sometimes
11645 make the link handshake fail. Fixes one case of bug 22460; bugfix
11648 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11649 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11650 December 2016 (of which ~126 were still functional) with a list of
11651 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11652 2017. Resolves ticket 21564.
11654 o Minor features (future-proofing, backport from 0.3.0.7):
11655 - Tor no longer refuses to download microdescriptors or descriptors if
11656 they are listed as "published in the future". This change will
11657 eventually allow us to stop listing meaningful "published" dates
11658 in microdescriptor consensuses, and thereby allow us to reduce the
11659 resources required to download consensus diffs by over 50%.
11660 Implements part of ticket 21642; implements part of proposal 275.
11662 o Minor features (directory authorities, backport from 0.3.0.4-rc)
11663 - Directory authorities now reject relays running versions
11664 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
11665 suffer from bug 20499 and don't keep their consensus cache
11666 up-to-date. Resolves ticket 20509.
11668 o Minor features (geoip):
11669 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11672 o Minor bugfixes (control port, backport from 0.3.0.6):
11673 - The GETINFO extra-info/digest/<digest> command was broken because
11674 of a wrong base16 decode return value check, introduced when
11675 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11677 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11678 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11679 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11681 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
11682 - The getpid() system call is now permitted under the Linux seccomp2
11683 sandbox, to avoid crashing with versions of OpenSSL (and other
11684 libraries) that attempt to learn the process's PID by using the
11685 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11688 o Minor bugfixes (memory leak, directory authority, backport
11689 from 0.3.1.2-alpha):
11690 - When directory authorities reject a router descriptor due to
11691 keypinning, free the router descriptor rather than leaking the
11692 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11694 Changes in version 0.2.8.14 - 2017-06-08
11695 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11696 remotely crash a hidden service with an assertion failure. Anyone
11697 running a hidden service should upgrade to this version, or to some
11698 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11699 are not affected by TROVE-2017-004.)
11701 o Major bugfixes (hidden service, relay, security):
11702 - Fix a remotely triggerable assertion failure caused by receiving a
11703 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11704 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11707 o Minor features (geoip):
11708 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11711 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11712 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11713 December 2016 (of which ~126 were still functional) with a list of
11714 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11715 2017. Resolves ticket 21564.
11717 o Minor bugfixes (correctness):
11718 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11719 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11721 Changes in version 0.2.7.8 - 2017-06-08
11722 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11723 remotely crash a hidden service with an assertion failure. Anyone
11724 running a hidden service should upgrade to this version, or to some
11725 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11726 are not affected by TROVE-2017-004.)
11728 o Major bugfixes (hidden service, relay, security):
11729 - Fix a remotely triggerable assertion failure caused by receiving a
11730 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11731 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11734 o Minor features (geoip):
11735 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11738 o Minor bugfixes (correctness):
11739 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11740 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11743 Changes in version 0.2.6.12 - 2017-06-08
11744 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
11745 remotely crash a hidden service with an assertion failure. Anyone
11746 running a hidden service should upgrade to this version, or to some
11747 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11748 are not affected by TROVE-2017-004.)
11750 o Major bugfixes (hidden service, relay, security):
11751 - Fix a remotely triggerable assertion failure caused by receiving a
11752 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11753 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11756 o Minor features (geoip):
11757 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11760 o Minor bugfixes (correctness):
11761 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11762 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11764 Changes in version 0.2.5.14 - 2017-06-08
11765 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
11766 remotely crash a hidden service with an assertion failure. Anyone
11767 running a hidden service should upgrade to this version, or to some
11768 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11769 are not affected by TROVE-2017-004.)
11771 o Major bugfixes (hidden service, relay, security):
11772 - Fix a remotely triggerable assertion failure caused by receiving a
11773 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11774 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11777 o Minor features (geoip):
11778 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11781 o Minor bugfixes (correctness):
11782 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11783 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11785 Changes in version 0.2.4.29 - 2017-06-08
11786 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
11787 remotely crash a hidden service with an assertion failure. Anyone
11788 running a hidden service should upgrade to this version, or to some
11789 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11790 are not affected by TROVE-2017-004.)
11792 o Major bugfixes (hidden service, relay, security):
11793 - Fix a remotely triggerable assertion failure caused by receiving a
11794 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11795 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11798 o Minor features (geoip):
11799 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11802 o Minor bugfixes (correctness):
11803 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11804 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11807 Changes in version 0.3.1.2-alpha - 2017-05-26
11808 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
11809 fixes a few bugs found while testing 0.3.1.1-alpha, including a
11810 memory corruption bug that affected relay stability.
11812 o Major bugfixes (crash, relay):
11813 - Fix a memory-corruption bug in relays that set MyFamily.
11814 Previously, they would double-free MyFamily elements when making
11815 the next descriptor or when changing their configuration. Fixes
11816 bug 22368; bugfix on 0.3.1.1-alpha.
11818 o Minor bugfixes (logging):
11819 - Log a better message when a directory authority replies to an
11820 upload with an unexpected status code. Fixes bug 11121; bugfix
11823 o Minor bugfixes (memory leak, directory authority):
11824 - When directory authorities reject a router descriptor due to
11825 keypinning, free the router descriptor rather than leaking the
11826 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11829 Changes in version 0.3.1.1-alpha - 2017-05-22
11830 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
11831 reduces the bandwidth usage for Tor's directory protocol, adds some
11832 basic padding to resist netflow-based traffic analysis and to serve as
11833 the basis of other padding in the future, and adds rust support to the
11836 It also contains numerous other small features and improvements to
11837 security, correctness, and performance.
11839 Below are the changes since 0.3.0.7.
11841 o Major features (directory protocol):
11842 - Tor relays and authorities can now serve clients an abbreviated
11843 version of the consensus document, containing only the changes
11844 since an older consensus document that the client holds. Clients
11845 now request these documents when available. When both client and
11846 server use this new protocol, they will use far less bandwidth (up
11847 to 94% less) to keep the client's consensus up-to-date. Implements
11848 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
11849 - Tor can now compress directory traffic with lzma or with zstd
11850 compression algorithms, which can deliver better bandwidth
11851 performance. Because lzma is computationally expensive, it's only
11852 used for documents that can be compressed once and served many
11853 times. Support for these algorithms requires that tor is built
11854 with the libzstd and/or liblzma libraries available. Implements
11855 proposal 278; closes ticket 21662.
11856 - Relays now perform the more expensive compression operations, and
11857 consensus diff generation, in worker threads. This separation
11858 avoids delaying the main thread when a new consensus arrives.
11860 o Major features (experimental):
11861 - Tor can now build modules written in Rust. To turn this on, pass
11862 the "--enable-rust" flag to the configure script. It's not time to
11863 get excited yet: currently, there is no actual Rust functionality
11864 beyond some simple glue code, and a notice at startup to tell you
11865 that Rust is running. Still, we hope that programmers and
11866 packagers will try building Tor with Rust support, so that we can
11867 find issues and solve portability problems. Closes ticket 22106.
11869 o Major features (traffic analysis resistance):
11870 - Connections between clients and relays now send a padding cell in
11871 each direction every 1.5 to 9.5 seconds (tunable via consensus
11872 parameters). This padding will not resist specialized
11873 eavesdroppers, but it should be enough to make many ISPs' routine
11874 network flow logging less useful in traffic analysis against
11877 Padding is negotiated using Tor's link protocol, so both relays
11878 and clients must upgrade for this to take effect. Clients may
11879 still send padding despite the relay's version by setting
11880 ConnectionPadding 1 in torrc, and may disable padding by setting
11881 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
11882 users with the torrc option ReducedConnectionPadding. Implements
11883 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
11884 - Relays will publish 24 hour totals of padding and non-padding cell
11885 counts to their extra-info descriptors, unless PaddingStatistics 0
11886 is set in torrc. These 24 hour totals are also rounded to
11887 multiples of 10000.
11889 o Major bugfixes (connection usage):
11890 - We use NETINFO cells to try to determine if both relays involved
11891 in a connection will agree on the canonical status of that
11892 connection. We prefer the connections where this is the case for
11893 extend cells, and try to close connections where relays disagree
11894 on their canonical status early. Also, we now prefer the oldest
11895 valid connection for extend cells. These two changes should reduce
11896 the number of long-term connections that are kept open between
11897 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
11898 - Relays now log hourly statistics (look for
11899 "channel_check_for_duplicates" lines) on the total number of
11900 connections to other relays. If the number of connections per
11901 relay is unexpectedly large, this log message is at notice level.
11902 Otherwise it is at info.
11904 o Major bugfixes (entry guards):
11905 - Don't block bootstrapping when a primary bridge is offline and we
11906 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11907 21969; bugfix on 0.3.0.3-alpha.
11909 o Major bugfixes (linux TPROXY support):
11910 - Fix a typo that had prevented TPROXY-based transparent proxying
11911 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11912 Patch from "d4fq0fQAgoJ".
11914 o Minor features (security, windows):
11915 - Enable a couple of pieces of Windows hardening: one
11916 (HeapEnableTerminationOnCorruption) that has been on-by-default
11917 since Windows 8, and unavailable before Windows 7; and one
11918 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11919 affect us, but shouldn't do any harm. Closes ticket 21953.
11921 o Minor features (config options):
11922 - Allow "%include" directives in torrc configuration files. These
11923 directives import the settings from other files, or from all the
11924 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
11925 - Make SAVECONF return an error when overwriting a torrc that has
11926 includes. Using SAVECONF with the FORCE option will allow it to
11927 overwrite torrc even if includes are used. Related to ticket 1922.
11928 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
11929 will work without the FORCE option. Related to ticket 1922.
11931 o Minor features (controller):
11932 - Warn the first time that a controller requests data in the long-
11933 deprecated 'GETINFO network-status' format. Closes ticket 21703.
11935 o Minor features (defaults):
11936 - The default value for UseCreateFast is now 0: clients which
11937 haven't yet received a consensus document will now use a proper
11938 ntor handshake to talk to their directory servers whenever they
11939 can. Closes ticket 21407.
11940 - Onion key rotation and expiry intervals are now defined as a
11941 network consensus parameter, per proposal 274. The default
11942 lifetime of an onion key is increased from 7 to 28 days. Old onion
11943 keys will expire after 7 days by default. This change will make
11944 consensus diffs much smaller, and save significant bandwidth.
11945 Closes ticket 21641.
11947 o Minor features (fallback directory list):
11948 - Update the fallback directory mirror whitelist and blacklist based
11949 on operator emails. Closes task 21121.
11950 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11951 December 2016 (of which ~126 were still functional) with a list of
11952 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11953 2017. Resolves ticket 21564.
11955 o Minor features (hidden services, logging):
11956 - Log a message when a hidden service descriptor has fewer
11957 introduction points than specified in
11958 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
11959 - Log a message when a hidden service reaches its introduction point
11960 circuit limit, and when that limit is reset. Follow up to ticket
11961 21594; closes ticket 21622.
11962 - Warn user if multiple entries in EntryNodes and at least one
11963 HiddenService are used together. Pinning EntryNodes along with a
11964 hidden service can be possibly harmful; for instance see ticket
11965 14917 or 21155. Closes ticket 21155.
11967 o Minor features (linux seccomp2 sandbox):
11968 - We now have a document storage backend compatible with the Linux
11969 seccomp2 sandbox. This backend is used for consensus documents and
11970 diffs between them; in the long term, we'd like to use it for
11971 unparseable directory material too. Closes ticket 21645
11972 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
11973 from 1MB to 16MB. This was necessary with the glibc allocator in
11974 order to allow worker threads to allocate more memory -- which in
11975 turn is necessary because of our new use of worker threads for
11976 compression. Closes ticket 22096.
11978 o Minor features (logging):
11979 - Log files are no longer created world-readable by default.
11980 (Previously, most distributors would store the logs in a non-
11981 world-readable location to prevent inappropriate access. This
11982 change is an extra precaution.) Closes ticket 21729; patch
11985 o Minor features (performance):
11986 - Our Keccak (SHA-3) implementation now accesses memory more
11987 efficiently, especially on little-endian systems. Closes
11989 - Add an O(1) implementation of channel_find_by_global_id(), to
11990 speed some controller functions.
11992 o Minor features (relay, configuration):
11993 - The MyFamily option may now be repeated as many times as desired,
11994 for relays that want to configure large families. Closes ticket
11995 4998; patch by Daniel Pinto.
11997 o Minor features (safety):
11998 - Add an explicit check to extrainfo_parse_entry_from_string() for
11999 NULL inputs. We don't believe this can actually happen, but it may
12000 help silence a warning from the Clang analyzer. Closes
12003 o Minor features (testing):
12004 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
12005 When Tor is compiled with this option, we disable a number of
12006 redundant memory-safety failsafes that are intended to stop bugs
12007 from becoming security issues. This makes it easier to hunt for
12008 bugs that would be security issues without the failsafes turned
12009 on. Closes ticket 21439.
12010 - Add a general event-tracing instrumentation support to Tor. This
12011 subsystem will enable developers and researchers to add fine-
12012 grained instrumentation to their Tor instances, for use when
12013 examining Tor network performance issues. There are no trace
12014 events yet, and event-tracing is off by default unless enabled at
12015 compile time. Implements ticket 13802.
12016 - Improve our version parsing tests: add tests for typical version
12017 components, add tests for invalid versions, including numeric
12018 range and non-numeric prefixes. Unit tests 21278, 21450, and
12019 21507. Partially implements 21470.
12021 o Minor bugfixes (bandwidth accounting):
12022 - Roll over monthly accounting at the configured hour and minute,
12023 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12024 Found by Andrey Karpov with PVS-Studio.
12026 o Minor bugfixes (code correctness):
12027 - Accurately identify client connections by their lack of peer
12028 authentication. This means that we bail out earlier if asked to
12029 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
12032 o Minor bugfixes (configuration):
12033 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12034 bug 22252; bugfix on 0.2.9.3-alpha.
12036 o Minor bugfixes (connection lifespan):
12037 - Allow more control over how long TLS connections are kept open:
12038 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
12039 single option called CircuitsAvailableTimeout. Also, allow the
12040 consensus to control the default values for both this preference
12041 and the lifespan of relay-to-relay connections. Fixes bug 17592;
12042 bugfix on 0.2.5.5-alpha.
12043 - Increase the initial circuit build timeout testing frequency, to
12044 help ensure that ReducedConnectionPadding clients finish learning
12045 a timeout before their orconn would expire. The initial testing
12046 rate was set back in the days of TAP and before the Tor Browser
12047 updater, when we had to be much more careful about new clients
12048 making lots of circuits. With this change, a circuit build timeout
12049 is learned in about 15-20 minutes, instead of 100-120 minutes.
12051 o Minor bugfixes (controller):
12052 - GETINFO onions/current and onions/detached no longer respond with
12053 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
12054 - Trigger HS descriptor events on the control port when the client
12055 fails to pick a hidden service directory for a hidden service.
12056 This can happen if all the hidden service directories are in
12057 ExcludeNodes, or they have all been queried within the last 15
12058 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
12060 o Minor bugfixes (directory authority):
12061 - When rejecting a router descriptor for running an obsolete version
12062 of Tor without ntor support, warn about the obsolete tor version,
12063 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12064 - Prevent the shared randomness subsystem from asserting when
12065 initialized by a bridge authority with an incomplete configuration
12066 file. Fixes bug 21586; bugfix on 0.2.9.8.
12068 o Minor bugfixes (exit-side DNS):
12069 - Fix an untriggerable assertion that checked the output of a
12070 libevent DNS error, so that the assertion actually behaves as
12071 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
12072 Karpov using PVS-Studio.
12074 o Minor bugfixes (fallback directories):
12075 - Make the usage example in updateFallbackDirs.py actually work, and
12076 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
12077 - Decrease the guard flag average required to be a fallback. This
12078 allows us to keep relays that have their guard flag removed when
12079 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12080 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
12081 bugfix on 0.2.8.1-alpha.
12082 - Make sure fallback directory mirrors have the same address, port,
12083 and relay identity key for at least 30 days before they are
12084 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12086 o Minor bugfixes (hidden services):
12087 - Stop printing a cryptic warning when a hidden service gets a
12088 request to connect to a virtual port that it hasn't configured.
12089 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
12090 - Simplify hidden service descriptor creation by using an existing
12091 flag to check if an introduction point is established. Fixes bug
12092 21599; bugfix on 0.2.7.2-alpha.
12094 o Minor bugfixes (memory leak):
12095 - Fix a small memory leak at exit from the backtrace handler code.
12096 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
12098 o Minor bugfixes (protocol, logging):
12099 - Downgrade a log statement about unexpected relay cells from "bug"
12100 to "protocol warning", because there is at least one use case
12101 where it can be triggered by a buggy tor implementation. Fixes bug
12102 21293; bugfix on 0.1.1.14-alpha.
12104 o Minor bugfixes (testing):
12105 - Use unbuffered I/O for utility functions around the
12106 process_handle_t type. This fixes unit test failures reported on
12107 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
12108 - Make display of captured unit test log messages consistent. Fixes
12109 bug 21510; bugfix on 0.2.9.3-alpha.
12110 - Make test-network.sh always call chutney's test-network.sh.
12111 Previously, this only worked on systems which had bash installed,
12112 due to some bash-specific code in the script. Fixes bug 19699;
12113 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
12115 o Minor bugfixes (voting consistency):
12116 - Reject version numbers with non-numeric prefixes (such as +, -, or
12117 whitespace). Disallowing whitespace prevents differential version
12118 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12119 and part of 21508; bugfix on 0.0.8pre1.
12121 o Minor bugfixes (windows, relay):
12122 - Resolve "Failure from drain_fd: No error" warnings on Windows
12123 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
12125 o Code simplification and refactoring:
12126 - Break up the 630-line function connection_dir_client_reached_eof()
12127 into a dozen smaller functions. This change should help
12128 maintainability and readability of the client directory code.
12129 - Isolate our use of the openssl headers so that they are only
12130 included from our crypto wrapper modules, and from tests that
12131 examine those modules' internals. Closes ticket 21841.
12132 - Simplify our API to launch directory requests, making it more
12133 extensible and less error-prone. Now it's easier to add extra
12134 headers to directory requests. Closes ticket 21646.
12135 - Our base64 decoding functions no longer overestimate the output
12136 space that they need when parsing unpadded inputs. Closes
12138 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
12139 Resolves ticket 22213.
12140 - The logic that directory caches use to spool request to clients,
12141 serving them one part at a time so as not to allocate too much
12142 memory, has been refactored for consistency. Previously there was
12143 a separate spooling implementation per type of spoolable data. Now
12144 there is one common spooling implementation, with extensible data
12145 types. Closes ticket 21651.
12146 - Tor's compression module now supports multiple backends. Part of
12147 the implementation for proposal 278; closes ticket 21663.
12150 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
12151 Closes ticket 21873.
12152 - Correct documentation about the default DataDirectory value.
12153 Closes ticket 21151.
12154 - Document the default behavior of NumEntryGuards and
12155 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
12157 - Document key=value pluggable transport arguments for Bridge lines
12158 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
12159 - Note that bandwidth-limiting options don't affect TCP headers or
12160 DNS. Closes ticket 17170.
12162 o Removed features (configuration options, all in ticket 22060):
12163 - These configuration options are now marked Obsolete, and no longer
12164 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
12165 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
12166 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
12167 in 0.2.9.2-alpha and have now been removed. The previous default
12168 behavior is now always chosen; the previous (less secure) non-
12169 default behavior is now unavailable.
12170 - CloseHSClientCircuitsImmediatelyOnTimeout and
12171 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
12172 0.2.9.2-alpha and now have been removed. HS circuits never close
12173 on circuit build timeout; they have a longer timeout period.
12174 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
12175 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
12176 (and others) to configure listen-only and advertise-only addresses.
12178 o Removed features (tools):
12179 - We've removed the tor-checkkey tool from src/tools. Long ago, we
12180 used it to help people detect RSA keys that were generated by
12181 versions of Debian affected by CVE-2008-0166. But those keys have
12182 been out of circulation for ages, and this tool is no longer
12183 required. Closes ticket 21842.
12186 Changes in version 0.3.0.7 - 2017-05-15
12187 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
12188 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
12189 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
12190 clients are not affected.
12192 o Major bugfixes (hidden service directory, security):
12193 - Fix an assertion failure in the hidden service directory code, which
12194 could be used by an attacker to remotely cause a Tor relay process to
12195 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
12196 should upgrade. This security issue is tracked as TROVE-2017-002.
12197 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
12200 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12203 o Minor features (future-proofing):
12204 - Tor no longer refuses to download microdescriptors or descriptors
12205 if they are listed as "published in the future". This change will
12206 eventually allow us to stop listing meaningful "published" dates
12207 in microdescriptor consensuses, and thereby allow us to reduce the
12208 resources required to download consensus diffs by over 50%.
12209 Implements part of ticket 21642; implements part of proposal 275.
12211 o Minor bugfixes (Linux seccomp2 sandbox):
12212 - The getpid() system call is now permitted under the Linux seccomp2
12213 sandbox, to avoid crashing with versions of OpenSSL (and other
12214 libraries) that attempt to learn the process's PID by using the
12215 syscall rather than the VDSO code. Fixes bug 21943; bugfix
12219 Changes in version 0.3.0.6 - 2017-04-26
12220 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
12222 With the 0.3.0 series, clients and relays now use Ed25519 keys to
12223 authenticate their link connections to relays, rather than the old
12224 RSA1024 keys that they used before. (Circuit crypto has been
12225 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
12226 the guard selection and replacement algorithm to behave more robustly
12227 in the presence of unreliable networks, and to resist guard-
12230 This series also includes numerous other small features and bugfixes,
12231 along with more groundwork for the upcoming hidden-services revamp.
12233 Per our stable release policy, we plan to support the Tor 0.3.0
12234 release series for at least the next nine months, or for three months
12235 after the first stable release of the 0.3.1 series: whichever is
12236 longer. If you need a release with long-term support, we recommend
12237 that you stay with the 0.2.9 series.
12239 Below are the changes since 0.3.0.5-rc. For a list of all changes
12240 since 0.2.9, see the ReleaseNotes file.
12242 o Minor features (geoip):
12243 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
12246 o Minor bugfixes (control port):
12247 - The GETINFO extra-info/digest/<digest> command was broken because
12248 of a wrong base16 decode return value check, introduced when
12249 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12251 o Minor bugfixes (crash prevention):
12252 - Fix a (currently untriggerable, but potentially dangerous) crash
12253 bug when base32-encoding inputs whose sizes are not a multiple of
12254 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
12257 Changes in version 0.3.0.5-rc - 2017-04-05
12258 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
12259 0.3.0 release series.
12261 This is the second release candidate in the Tor 0.3.0 series, and has
12262 much fewer changes than the first. If we find no new bugs or
12263 regressions here, the first stable 0.3.0 release will be nearly
12266 o Major bugfixes (crash, directory connections):
12267 - Fix a rare crash when sending a begin cell on a circuit whose
12268 linked directory connection had already been closed. Fixes bug
12269 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
12271 o Major bugfixes (guard selection):
12272 - Fix a guard selection bug where Tor would refuse to bootstrap in
12273 some cases if the user swapped a bridge for another bridge in
12274 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
12275 Reported by "torvlnt33r".
12277 o Minor features (geoip):
12278 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
12281 o Minor bugfix (compilation):
12282 - Fix a warning when compiling hs_service.c. Previously, it had no
12283 exported symbols when compiled for libor.a, resulting in a
12284 compilation warning from clang. Fixes bug 21825; bugfix
12287 o Minor bugfixes (hidden services):
12288 - Make hidden services check for failed intro point connections,
12289 even when they have exceeded their intro point creation limit.
12290 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
12291 - Make hidden services with 8 to 10 introduction points check for
12292 failed circuits immediately after startup. Previously, they would
12293 wait for 5 minutes before performing their first checks. Fixes bug
12294 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
12296 o Minor bugfixes (memory leaks):
12297 - Fix a memory leak when using GETCONF on a port option. Fixes bug
12298 21682; bugfix on 0.3.0.3-alpha.
12300 o Minor bugfixes (relay):
12301 - Avoid a double-marked-circuit warning that could happen when we
12302 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12305 o Minor bugfixes (tests):
12306 - Run the entry_guard_parse_from_state_full() test with the time set
12307 to a specific date. (The guard state that this test was parsing
12308 contained guards that had expired since the test was first
12309 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
12312 - Update the description of the directory server options in the
12313 manual page, to clarify that a relay no longer needs to set
12314 DirPort in order to be a directory cache. Closes ticket 21720.
12318 Changes in version 0.2.8.13 - 2017-03-03
12319 Tor 0.2.8.13 backports a security fix from later Tor
12320 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
12321 this release, if for some reason they cannot upgrade to a later
12322 release series, and if they build Tor with the --enable-expensive-hardening
12325 Note that support for Tor 0.2.8.x is ending next year: we will not issue
12326 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
12327 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12329 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12330 - Fix an integer underflow bug when comparing malformed Tor
12331 versions. This bug could crash Tor when built with
12332 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12333 0.2.9.8, which were built with -ftrapv by default. In other cases
12334 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12335 on 0.0.8pre1. Found by OSS-Fuzz.
12337 o Minor features (geoip):
12338 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12342 Changes in version 0.2.7.7 - 2017-03-03
12343 Tor 0.2.7.7 backports a number of security fixes from later Tor
12344 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
12345 this release, if for some reason they cannot upgrade to a later
12348 Note that support for Tor 0.2.7.x is ending this year: we will not issue
12349 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
12350 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12352 o Directory authority changes (backport from 0.2.8.5-rc):
12353 - Urras is no longer a directory authority. Closes ticket 19271.
12355 o Directory authority changes (backport from 0.2.9.2-alpha):
12356 - The "Tonga" bridge authority has been retired; the new bridge
12357 authority is "Bifroest". Closes tickets 19728 and 19690.
12359 o Directory authority key updates (backport from 0.2.8.1-alpha):
12360 - Update the V3 identity key for the dannenberg directory authority:
12361 it was changed on 18 November 2015. Closes task 17906. Patch
12364 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12365 - Fix a bug in parsing that could cause clients to read a single
12366 byte past the end of an allocated region. This bug could be used
12367 to cause hardened clients (built with --enable-expensive-hardening)
12368 to crash if they tried to visit a hostile hidden service. Non-
12369 hardened clients are only affected depending on the details of
12370 their platform's memory allocator. Fixes bug 21018; bugfix on
12371 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12372 2016-12-002 and as CVE-2016-1254.
12374 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12375 - Stop a crash that could occur when a client running with DNSPort
12376 received a query with multiple address types, and the first
12377 address type was not supported. Found and fixed by Scott Dial.
12378 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12379 - Prevent a class of security bugs caused by treating the contents
12380 of a buffer chunk as if they were a NUL-terminated string. At
12381 least one such bug seems to be present in all currently used
12382 versions of Tor, and would allow an attacker to remotely crash
12383 most Tor instances, especially those compiled with extra compiler
12384 hardening. With this defense in place, such bugs can't crash Tor,
12385 though we should still fix them as they occur. Closes ticket
12386 20384 (TROVE-2016-10-001).
12388 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12389 - Avoid a difficult-to-trigger heap corruption attack when extending
12390 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12391 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12392 Reported by Guido Vranken.
12394 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12395 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12396 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12398 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12399 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12400 pointer to the previous (uninitialized) key value. The impact here
12401 should be limited to a difficult-to-trigger crash, if OpenSSL is
12402 running an engine that makes key generation failures possible, or
12403 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12404 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12407 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12408 - Fix an integer underflow bug when comparing malformed Tor
12409 versions. This bug could crash Tor when built with
12410 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12411 0.2.9.8, which were built with -ftrapv by default. In other cases
12412 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12413 on 0.0.8pre1. Found by OSS-Fuzz.
12415 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12416 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12417 zero size. Check size argument to memwipe() for underflow. Fixes
12418 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12421 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12422 - Make Tor survive errors involving connections without a
12423 corresponding event object. Previously we'd fail with an
12424 assertion; now we produce a log message. Related to bug 16248.
12426 o Minor features (geoip):
12427 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12431 Changes in version 0.2.6.11 - 2017-03-03
12432 Tor 0.2.6.11 backports a number of security fixes from later Tor
12433 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
12434 this release, if for some reason they cannot upgrade to a later
12437 Note that support for Tor 0.2.6.x is ending this year: we will not issue
12438 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
12439 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12441 o Directory authority changes (backport from 0.2.8.5-rc):
12442 - Urras is no longer a directory authority. Closes ticket 19271.
12444 o Directory authority changes (backport from 0.2.9.2-alpha):
12445 - The "Tonga" bridge authority has been retired; the new bridge
12446 authority is "Bifroest". Closes tickets 19728 and 19690.
12448 o Directory authority key updates (backport from 0.2.8.1-alpha):
12449 - Update the V3 identity key for the dannenberg directory authority:
12450 it was changed on 18 November 2015. Closes task 17906. Patch
12453 o Major features (security fixes, backport from 0.2.9.4-alpha):
12454 - Prevent a class of security bugs caused by treating the contents
12455 of a buffer chunk as if they were a NUL-terminated string. At
12456 least one such bug seems to be present in all currently used
12457 versions of Tor, and would allow an attacker to remotely crash
12458 most Tor instances, especially those compiled with extra compiler
12459 hardening. With this defense in place, such bugs can't crash Tor,
12460 though we should still fix them as they occur. Closes ticket
12461 20384 (TROVE-2016-10-001).
12463 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12464 - Fix a bug in parsing that could cause clients to read a single
12465 byte past the end of an allocated region. This bug could be used
12466 to cause hardened clients (built with --enable-expensive-hardening)
12467 to crash if they tried to visit a hostile hidden service. Non-
12468 hardened clients are only affected depending on the details of
12469 their platform's memory allocator. Fixes bug 21018; bugfix on
12470 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12471 2016-12-002 and as CVE-2016-1254.
12473 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12474 - Stop a crash that could occur when a client running with DNSPort
12475 received a query with multiple address types, and the first
12476 address type was not supported. Found and fixed by Scott Dial.
12477 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12479 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12480 - Fix an error that could cause us to read 4 bytes before the
12481 beginning of an openssl string. This bug could be used to cause
12482 Tor to crash on systems with unusual malloc implementations, or
12483 systems with unusual hardening installed. Fixes bug 17404; bugfix
12486 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12487 - Avoid a difficult-to-trigger heap corruption attack when extending
12488 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12489 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12490 Reported by Guido Vranken.
12492 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12493 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12494 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12496 o Major bugfixes (guard selection, backport from 0.2.7.6):
12497 - Actually look at the Guard flag when selecting a new directory
12498 guard. When we implemented the directory guard design, we
12499 accidentally started treating all relays as if they have the Guard
12500 flag during guard selection, leading to weaker anonymity and worse
12501 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12504 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12505 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12506 pointer to the previous (uninitialized) key value. The impact here
12507 should be limited to a difficult-to-trigger crash, if OpenSSL is
12508 running an engine that makes key generation failures possible, or
12509 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12510 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12513 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12514 - Fix an integer underflow bug when comparing malformed Tor
12515 versions. This bug could crash Tor when built with
12516 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12517 0.2.9.8, which were built with -ftrapv by default. In other cases
12518 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12519 on 0.0.8pre1. Found by OSS-Fuzz.
12521 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12522 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12523 zero size. Check size argument to memwipe() for underflow. Fixes
12524 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12527 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12528 - Make Tor survive errors involving connections without a
12529 corresponding event object. Previously we'd fail with an
12530 assertion; now we produce a log message. Related to bug 16248.
12532 o Minor features (geoip):
12533 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12536 o Minor bugfixes (compilation, backport from 0.2.7.6):
12537 - Fix a compilation warning with Clang 3.6: Do not check the
12538 presence of an address which can never be NULL. Fixes bug 17781.
12541 Changes in version 0.2.5.13 - 2017-03-03
12542 Tor 0.2.5.13 backports a number of security fixes from later Tor
12543 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
12544 this release, if for some reason they cannot upgrade to a later
12547 Note that support for Tor 0.2.5.x is ending next year: we will not issue
12548 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
12549 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12551 o Directory authority changes (backport from 0.2.8.5-rc):
12552 - Urras is no longer a directory authority. Closes ticket 19271.
12554 o Directory authority changes (backport from 0.2.9.2-alpha):
12555 - The "Tonga" bridge authority has been retired; the new bridge
12556 authority is "Bifroest". Closes tickets 19728 and 19690.
12558 o Directory authority key updates (backport from 0.2.8.1-alpha):
12559 - Update the V3 identity key for the dannenberg directory authority:
12560 it was changed on 18 November 2015. Closes task 17906. Patch
12563 o Major features (security fixes, backport from 0.2.9.4-alpha):
12564 - Prevent a class of security bugs caused by treating the contents
12565 of a buffer chunk as if they were a NUL-terminated string. At
12566 least one such bug seems to be present in all currently used
12567 versions of Tor, and would allow an attacker to remotely crash
12568 most Tor instances, especially those compiled with extra compiler
12569 hardening. With this defense in place, such bugs can't crash Tor,
12570 though we should still fix them as they occur. Closes ticket
12571 20384 (TROVE-2016-10-001).
12573 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12574 - Fix a bug in parsing that could cause clients to read a single
12575 byte past the end of an allocated region. This bug could be used
12576 to cause hardened clients (built with --enable-expensive-hardening)
12577 to crash if they tried to visit a hostile hidden service. Non-
12578 hardened clients are only affected depending on the details of
12579 their platform's memory allocator. Fixes bug 21018; bugfix on
12580 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12581 2016-12-002 and as CVE-2016-1254.
12583 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12584 - Stop a crash that could occur when a client running with DNSPort
12585 received a query with multiple address types, and the first
12586 address type was not supported. Found and fixed by Scott Dial.
12587 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12589 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12590 - Fix an error that could cause us to read 4 bytes before the
12591 beginning of an openssl string. This bug could be used to cause
12592 Tor to crash on systems with unusual malloc implementations, or
12593 systems with unusual hardening installed. Fixes bug 17404; bugfix
12596 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12597 - Avoid a difficult-to-trigger heap corruption attack when extending
12598 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12599 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12600 Reported by Guido Vranken.
12602 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12603 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12604 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12606 o Major bugfixes (guard selection, backport from 0.2.7.6):
12607 - Actually look at the Guard flag when selecting a new directory
12608 guard. When we implemented the directory guard design, we
12609 accidentally started treating all relays as if they have the Guard
12610 flag during guard selection, leading to weaker anonymity and worse
12611 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12614 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12615 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12616 pointer to the previous (uninitialized) key value. The impact here
12617 should be limited to a difficult-to-trigger crash, if OpenSSL is
12618 running an engine that makes key generation failures possible, or
12619 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12620 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12623 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12624 - Fix an integer underflow bug when comparing malformed Tor
12625 versions. This bug could crash Tor when built with
12626 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12627 0.2.9.8, which were built with -ftrapv by default. In other cases
12628 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12629 on 0.0.8pre1. Found by OSS-Fuzz.
12631 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12632 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12633 zero size. Check size argument to memwipe() for underflow. Fixes
12634 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12637 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12638 - Make Tor survive errors involving connections without a
12639 corresponding event object. Previously we'd fail with an
12640 assertion; now we produce a log message. Related to bug 16248.
12642 o Minor features (geoip):
12643 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12646 o Minor bugfixes (compilation, backport from 0.2.7.6):
12647 - Fix a compilation warning with Clang 3.6: Do not check the
12648 presence of an address which can never be NULL. Fixes bug 17781.
12650 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
12651 - Check for failures from crypto_early_init, and refuse to continue.
12652 A previous typo meant that we could keep going with an
12653 uninitialized crypto library, and would have OpenSSL initialize
12654 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12655 when implementing ticket 4900. Patch by "teor".
12657 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12658 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12659 a client authorized hidden service. Fixes bug 15823; bugfix
12663 Changes in version 0.2.4.28 - 2017-03-03
12664 Tor 0.2.4.28 backports a number of security fixes from later Tor
12665 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
12666 this release, if for some reason they cannot upgrade to a later
12669 Note that support for Tor 0.2.4.x is ending soon: we will not issue
12670 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
12671 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
12673 o Directory authority changes (backport from 0.2.8.5-rc):
12674 - Urras is no longer a directory authority. Closes ticket 19271.
12676 o Directory authority changes (backport from 0.2.9.2-alpha):
12677 - The "Tonga" bridge authority has been retired; the new bridge
12678 authority is "Bifroest". Closes tickets 19728 and 19690.
12680 o Directory authority key updates (backport from 0.2.8.1-alpha):
12681 - Update the V3 identity key for the dannenberg directory authority:
12682 it was changed on 18 November 2015. Closes task 17906. Patch
12685 o Major features (security fixes, backport from 0.2.9.4-alpha):
12686 - Prevent a class of security bugs caused by treating the contents
12687 of a buffer chunk as if they were a NUL-terminated string. At
12688 least one such bug seems to be present in all currently used
12689 versions of Tor, and would allow an attacker to remotely crash
12690 most Tor instances, especially those compiled with extra compiler
12691 hardening. With this defense in place, such bugs can't crash Tor,
12692 though we should still fix them as they occur. Closes ticket
12693 20384 (TROVE-2016-10-001).
12695 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12696 - Fix a bug in parsing that could cause clients to read a single
12697 byte past the end of an allocated region. This bug could be used
12698 to cause hardened clients (built with --enable-expensive-hardening)
12699 to crash if they tried to visit a hostile hidden service. Non-
12700 hardened clients are only affected depending on the details of
12701 their platform's memory allocator. Fixes bug 21018; bugfix on
12702 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12703 2016-12-002 and as CVE-2016-1254.
12705 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12706 - Fix an error that could cause us to read 4 bytes before the
12707 beginning of an openssl string. This bug could be used to cause
12708 Tor to crash on systems with unusual malloc implementations, or
12709 systems with unusual hardening installed. Fixes bug 17404; bugfix
12712 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12713 - Avoid a difficult-to-trigger heap corruption attack when extending
12714 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12715 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12716 Reported by Guido Vranken.
12718 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12719 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12720 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12722 o Major bugfixes (guard selection, backport from 0.2.7.6):
12723 - Actually look at the Guard flag when selecting a new directory
12724 guard. When we implemented the directory guard design, we
12725 accidentally started treating all relays as if they have the Guard
12726 flag during guard selection, leading to weaker anonymity and worse
12727 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12730 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12731 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12732 pointer to the previous (uninitialized) key value. The impact here
12733 should be limited to a difficult-to-trigger crash, if OpenSSL is
12734 running an engine that makes key generation failures possible, or
12735 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12736 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12739 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12740 - Fix an integer underflow bug when comparing malformed Tor
12741 versions. This bug could crash Tor when built with
12742 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12743 0.2.9.8, which were built with -ftrapv by default. In other cases
12744 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12745 on 0.0.8pre1. Found by OSS-Fuzz.
12747 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12748 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12749 zero size. Check size argument to memwipe() for underflow. Fixes
12750 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12753 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12754 - Make Tor survive errors involving connections without a
12755 corresponding event object. Previously we'd fail with an
12756 assertion; now we produce a log message. Related to bug 16248.
12758 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
12759 - Make it harder for attackers to overload hidden services with
12760 introductions, by blocking multiple introduction requests on the
12761 same circuit. Resolves ticket 15515.
12763 o Minor features (geoip):
12764 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12767 o Minor bugfixes (compilation, backport from 0.2.7.6):
12768 - Fix a compilation warning with Clang 3.6: Do not check the
12769 presence of an address which can never be NULL. Fixes bug 17781.
12771 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12772 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12773 a client authorized hidden service. Fixes bug 15823; bugfix
12777 Changes in version 0.3.0.4-rc - 2017-03-01
12778 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
12779 0.3.0 release series, and introduces a few reliability features to
12780 keep them from coming back.
12782 This is the first release candidate in the Tor 0.3.0 series. If we
12783 find no new bugs or regressions here, the first stable 0.3.0 release
12784 will be nearly identical to it.
12786 o Major bugfixes (bridges):
12787 - When the same bridge is configured multiple times with the same
12788 identity, but at different address:port combinations, treat those
12789 bridge instances as separate guards. This fix restores the ability
12790 of clients to configure the same bridge with multiple pluggable
12791 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
12793 o Major bugfixes (hidden service directory v3):
12794 - Stop crashing on a failed v3 hidden service descriptor lookup
12795 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
12797 o Major bugfixes (parsing):
12798 - When parsing a malformed content-length field from an HTTP
12799 message, do not read off the end of the buffer. This bug was a
12800 potential remote denial-of-service attack against Tor clients and
12801 relays. A workaround was released in October 2016, to prevent this
12802 bug from crashing Tor. This is a fix for the underlying issue,
12803 which should no longer matter (if you applied the earlier patch).
12804 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
12805 using AFL (http://lcamtuf.coredump.cx/afl/).
12806 - Fix an integer underflow bug when comparing malformed Tor
12807 versions. This bug could crash Tor when built with
12808 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12809 0.2.9.8, which were built with -ftrapv by default. In other cases
12810 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12811 on 0.0.8pre1. Found by OSS-Fuzz.
12813 o Minor feature (protocol versioning):
12814 - Add new protocol version for proposal 224. HSIntro now advertises
12815 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
12817 o Minor features (directory authorities):
12818 - Directory authorities now reject descriptors that claim to be
12819 malformed versions of Tor. Helps prevent exploitation of
12821 - Reject version numbers with components that exceed INT32_MAX.
12822 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12823 Fixes bug 21450; bugfix on 0.0.8pre1.
12824 - Directory authorities now reject relays running versions
12825 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
12826 suffer from bug 20499 and don't keep their consensus cache
12827 up-to-date. Resolves ticket 20509.
12829 o Minor features (geoip):
12830 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12833 o Minor features (reliability, crash):
12834 - Try better to detect problems in buffers where they might grow (or
12835 think they have grown) over 2 GB in size. Diagnostic for
12838 o Minor features (testing):
12839 - During 'make test-network-all', if tor logs any warnings, ask
12840 chutney to output them. Requires a recent version of chutney with
12841 the 21572 patch. Implements 21570.
12843 o Minor bugfixes (certificate expiration time):
12844 - Avoid using link certificates that don't become valid till some
12845 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
12847 o Minor bugfixes (code correctness):
12848 - Repair a couple of (unreachable or harmless) cases of the risky
12849 comparison-by-subtraction pattern that caused bug 21278.
12850 - Remove a redundant check for the UseEntryGuards option from the
12851 options_transition_affects_guards() function. Fixes bug 21492;
12852 bugfix on 0.3.0.1-alpha.
12854 o Minor bugfixes (directory mirrors):
12855 - Allow relays to use directory mirrors without a DirPort: these
12856 relays need to be contacted over their ORPorts using a begindir
12857 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
12858 - Clarify the message logged when a remote relay is unexpectedly
12859 missing an ORPort or DirPort: users were confusing this with a
12860 local port. Fixes another case of bug 20711; bugfix
12863 o Minor bugfixes (guards):
12864 - Don't warn about a missing guard state on timeout-measurement
12865 circuits: they aren't supposed to be using guards. Fixes an
12866 instance of bug 21007; bugfix on 0.3.0.1-alpha.
12867 - Silence a BUG() warning when attempting to use a guard whose
12868 descriptor we don't know, and make this scenario less likely to
12869 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
12871 o Minor bugfixes (hidden service):
12872 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
12873 cells. Previously, we were using sizeof() on a pointer, instead of
12874 the real destination buffer. Fortunately, that value was only used
12875 to double-check that there was enough room--which was already
12876 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
12878 o Minor bugfixes (testing):
12879 - Fix Raspbian build issues related to missing socket errno in
12880 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
12882 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
12883 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
12884 - Use bash in src/test/test-network.sh. This ensures we reliably
12885 call chutney's newer tools/test-network.sh when available. Fixes
12886 bug 21562; bugfix on 0.2.9.1-alpha.
12889 - Small fixes to the fuzzing documentation. Closes ticket 21472.
12892 Changes in version 0.2.9.10 - 2017-03-01
12893 Tor 0.2.9.10 backports a security fix from later Tor release. It also
12894 includes fixes for some major issues affecting directory authorities,
12895 LibreSSL compatibility, and IPv6 correctness.
12897 The Tor 0.2.9.x release series is now marked as a long-term-support
12898 series. We intend to backport security fixes to 0.2.9.x until at
12899 least January of 2020.
12901 o Major bugfixes (directory authority, 0.3.0.3-alpha):
12902 - During voting, when marking a relay as a probable sybil, do not
12903 clear its BadExit flag: sybils can still be bad in other ways
12904 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12907 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
12908 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12909 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12910 exit policy rejects that port on more than an IPv6 /16 of
12911 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12912 which rejected a relay's own IPv6 address by default. Fixes bug
12913 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12915 o Major bugfixes (parsing, also in 0.3.0.4-rc):
12916 - Fix an integer underflow bug when comparing malformed Tor
12917 versions. This bug could crash Tor when built with
12918 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12919 0.2.9.8, which were built with -ftrapv by default. In other cases
12920 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12921 on 0.0.8pre1. Found by OSS-Fuzz.
12923 o Minor features (directory authorities, also in 0.3.0.4-rc):
12924 - Directory authorities now reject descriptors that claim to be
12925 malformed versions of Tor. Helps prevent exploitation of
12927 - Reject version numbers with components that exceed INT32_MAX.
12928 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12929 Fixes bug 21450; bugfix on 0.0.8pre1.
12931 o Minor features (geoip):
12932 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12935 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
12936 - Autoconf now checks to determine if OpenSSL structures are opaque,
12937 instead of explicitly checking for OpenSSL version numbers. Part
12939 - Support building with recent LibreSSL code that uses opaque
12940 structures. Closes ticket 21359.
12942 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
12943 - Repair a couple of (unreachable or harmless) cases of the risky
12944 comparison-by-subtraction pattern that caused bug 21278.
12946 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
12947 - The tor-resolve command line tool now rejects hostnames over 255
12948 characters in length. Previously, it would silently truncate them,
12949 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12950 Patch by "junglefowl".
12953 Changes in version 0.3.0.3-alpha - 2017-02-03
12954 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
12955 0.3.0.x development series, including some that could cause
12956 authorities to behave badly. There is also a fix for a longstanding
12957 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
12958 includes some smaller features and bugfixes.
12960 The Tor 0.3.0.x release series is now in patch-freeze: no additional
12961 features will be considered for inclusion in 0.3.0.x. We suspect that
12962 some bugs will probably remain, however, and we encourage people to
12965 o Major bugfixes (directory authority):
12966 - During voting, when marking a relay as a probable sybil, do not
12967 clear its BadExit flag: sybils can still be bad in other ways
12968 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12970 - When deciding whether we have just found a router to be reachable,
12971 do not penalize it for not having performed an Ed25519 link
12972 handshake if it does not claim to support an Ed25519 handshake.
12973 Previously, we would treat such relays as non-running. Fixes bug
12974 21107; bugfix on 0.3.0.1-alpha.
12976 o Major bugfixes (entry guards):
12977 - Stop trying to build circuits through entry guards for which we
12978 have no descriptor. Also, stop crashing in the case that we *do*
12979 accidentally try to build a circuit in such a state. Fixes bug
12980 21242; bugfix on 0.3.0.1-alpha.
12982 o Major bugfixes (IPv6 Exits):
12983 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12984 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12985 exit policy rejects that port on more than an IPv6 /16 of
12986 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12987 which rejected a relay's own IPv6 address by default. Fixes bug
12988 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12990 o Minor feature (client):
12991 - Enable IPv6 traffic on the SocksPort by default. To disable this,
12992 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
12994 o Minor feature (fallback scripts):
12995 - Add a check_existing mode to updateFallbackDirs.py, which checks
12996 if fallbacks in the hard-coded list are working. Closes ticket
12997 20174. Patch by haxxpop.
12999 o Minor features (ciphersuite selection):
13000 - Clients now advertise a list of ciphersuites closer to the ones
13001 preferred by Firefox. Closes part of ticket 15426.
13002 - Allow relays to accept a wider range of ciphersuites, including
13003 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
13005 o Minor features (controller, configuration):
13006 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
13007 and so on, now comes with a __*Port variant that will not be saved
13008 to the torrc file by the controller's SAVECONF command. This
13009 change allows TorBrowser to set up a single-use domain socket for
13010 each time it launches Tor. Closes ticket 20956.
13011 - The GETCONF command can now query options that may only be
13012 meaningful in context-sensitive lists. This allows the controller
13013 to query the mixed SocksPort/__SocksPort style options introduced
13014 in feature 20956. Implements ticket 21300.
13016 o Minor features (portability, compilation):
13017 - Autoconf now checks to determine if OpenSSL structures are opaque,
13018 instead of explicitly checking for OpenSSL version numbers. Part
13020 - Support building with recent LibreSSL code that uses opaque
13021 structures. Closes ticket 21359.
13023 o Minor features (relay):
13024 - We now allow separation of exit and relay traffic to different
13025 source IP addresses, using the OutboundBindAddressExit and
13026 OutboundBindAddressOR options respectively. Closes ticket 17975.
13027 Written by Michael Sonntag.
13029 o Minor bugfix (logging):
13030 - Don't recommend the use of Tor2web in non-anonymous mode.
13031 Recommending Tor2web is a bad idea because the client loses all
13032 anonymity. Tor2web should only be used in specific cases by users
13033 who *know* and understand the issues. Fixes bug 21294; bugfix
13036 o Minor bugfixes (client):
13037 - Always recover from failures in extend_info_from_node(), in an
13038 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
13039 bugfix on 0.2.3.1-alpha.
13041 o Minor bugfixes (client, entry guards):
13042 - Fix a bug warning (with backtrace) when we fail a channel that
13043 circuits to fallback directories on it. Fixes bug 21128; bugfix
13045 - Fix a spurious bug warning (with backtrace) when removing an
13046 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
13047 - Fix a bug of the new guard algorithm where tor could stall for up
13048 to 10 minutes before retrying a guard after a long period of no
13049 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
13050 - Do not try to build circuits until we have descriptors for our
13051 primary entry guards. Related to fix for bug 21242.
13053 o Minor bugfixes (configure, autoconf):
13054 - Rename the configure option --enable-expensive-hardening to
13055 --enable-fragile-hardening. Expensive hardening makes the tor
13056 daemon abort when some kinds of issues are detected. Thus, it
13057 makes tor more at risk of remote crashes but safer against RCE or
13058 heartbleed bug category. We now try to explain this issue in a
13059 message from the configure script. Fixes bug 21290; bugfix
13062 o Minor bugfixes (controller):
13063 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
13064 20824; bugfix on 0.3.0.1-alpha.
13066 o Minor bugfixes (hidden service):
13067 - Clean up the code for expiring intro points with no associated
13068 circuits. It was causing, rarely, a service with some expiring
13069 introduction points to not open enough additional introduction
13070 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
13071 - Stop setting the torrc option HiddenServiceStatistics to "0" just
13072 because we're not a bridge or relay. Instead, we preserve whatever
13073 value the user set (or didn't set). Fixes bug 21150; bugfix
13075 - Resolve two possible underflows which could lead to creating and
13076 closing a lot of introduction point circuits in a non-stop loop.
13077 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
13079 o Minor bugfixes (portability):
13080 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
13081 It is supported by OpenBSD itself, and also by most OpenBSD
13082 variants (such as Bitrig). Fixes bug 20980; bugfix
13084 - When mapping a file of length greater than SIZE_MAX, do not
13085 silently truncate its contents. This issue could occur on 32 bit
13086 systems with large file support and files which are larger than 4
13087 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
13089 o Minor bugfixes (tor-resolve):
13090 - The tor-resolve command line tool now rejects hostnames over 255
13091 characters in length. Previously, it would silently truncate them,
13092 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13093 Patch by "junglefowl".
13095 o Minor bugfixes (Windows services):
13096 - Be sure to initialize the monotonic time subsystem before using
13097 it, even when running as an NT service. Fixes bug 21356; bugfix
13101 Changes in version 0.3.0.2-alpha - 2017-01-23
13102 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
13103 cause relays and clients to crash, even if they were not built with
13104 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13105 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13106 version should upgrade.
13108 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
13109 time-to-live values, makes directory authorities enforce the 1-to-1
13110 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
13111 client-side onion service reachability bug, does better at selecting
13112 the set of fallback directories, and more.
13114 o Major bugfixes (security, also in 0.2.9.9):
13115 - Downgrade the "-ftrapv" option from "always on" to "only on when
13116 --enable-expensive-hardening is provided." This hardening option, like
13117 others, can turn survivable bugs into crashes--and having it on by
13118 default made a (relatively harmless) integer overflow bug into a
13119 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
13122 o Major features (security):
13123 - Change the algorithm used to decide DNS TTLs on client and server
13124 side, to better resist DNS-based correlation attacks like the
13125 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
13126 Feamster. Now relays only return one of two possible DNS TTL
13127 values, and clients are willing to believe DNS TTL values up to 3
13128 hours long. Closes ticket 19769.
13130 o Major features (directory authority, security):
13131 - The default for AuthDirPinKeys is now 1: directory authorities
13132 will reject relays where the RSA identity key matches a previously
13133 seen value, but the Ed25519 key has changed. Closes ticket 18319.
13135 o Major bugfixes (client, guard, crash):
13136 - In circuit_get_global_origin_list(), return the actual list of
13137 origin circuits. The previous version of this code returned the
13138 list of all the circuits, and could have caused strange bugs,
13139 including possible crashes. Fixes bug 21118; bugfix
13142 o Major bugfixes (client, onion service, also in 0.2.9.9):
13143 - Fix a client-side onion service reachability bug, where multiple
13144 socks requests to an onion service (or a single slow request)
13145 could cause us to mistakenly mark some of the service's
13146 introduction points as failed, and we cache that failure so
13147 eventually we run out and can't reach the service. Also resolves a
13148 mysterious "Remote server sent bogus reason code 65021" log
13149 warning. The bug was introduced in ticket 17218, where we tried to
13150 remember the circuit end reason as a uint16_t, which mangled
13151 negative values. Partially fixes bug 21056 and fixes bug 20307;
13152 bugfix on 0.2.8.1-alpha.
13154 o Major bugfixes (DNS):
13155 - Fix a bug that prevented exit nodes from caching DNS records for
13156 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
13158 o Minor features (controller):
13159 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
13160 shared-random values to the controller. Closes ticket 19925.
13162 o Minor features (entry guards):
13163 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
13164 break regression tests.
13165 - Require UseEntryGuards when UseBridges is set, in order to make
13166 sure bridges aren't bypassed. Resolves ticket 20502.
13168 o Minor features (fallback directories):
13169 - Select 200 fallback directories for each release. Closes
13171 - Allow 3 fallback relays per operator, which is safe now that we
13172 are choosing 200 fallback relays. Closes ticket 20912.
13173 - Exclude relays affected by bug 20499 from the fallback list.
13174 Exclude relays from the fallback list if they are running versions
13175 known to be affected by bug 20499, or if in our tests they deliver
13176 a stale consensus (i.e. one that expired more than 24 hours ago).
13177 Closes ticket 20539.
13178 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
13180 - Require fallback directories to have the same address and port for
13181 7 days (now that we have enough relays with this stability).
13182 Relays whose OnionOO stability timer is reset on restart by bug
13183 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
13184 this issue. Closes ticket 20880; maintains short-term fix
13186 - Require fallbacks to have flags for 90% of the time (weighted
13187 decaying average), rather than 95%. This allows at least 73% of
13188 clients to bootstrap in the first 5 seconds without contacting an
13189 authority. Part of ticket 18828.
13190 - Annotate updateFallbackDirs.py with the bandwidth and consensus
13191 weight for each candidate fallback. Closes ticket 20878.
13192 - Make it easier to change the output sort order of fallbacks.
13193 Closes ticket 20822.
13194 - Display the relay fingerprint when downloading consensuses from
13195 fallbacks. Closes ticket 20908.
13197 o Minor features (geoip, also in 0.2.9.9):
13198 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13201 o Minor features (next-gen onion service directories):
13202 - Remove the "EnableOnionServicesV3" consensus parameter that we
13203 introduced in 0.3.0.1-alpha: relays are now always willing to act
13204 as v3 onion service directories. Resolves ticket 19899.
13206 o Minor features (linting):
13207 - Enhance the changes file linter to warn on Tor versions that are
13208 prefixed with "tor-". Closes ticket 21096.
13210 o Minor features (logging):
13211 - In several places, describe unset ed25519 keys as "<unset>",
13212 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
13214 o Minor bugfix (control protocol):
13215 - The reply to a "GETINFO config/names" request via the control
13216 protocol now spells the type "Dependent" correctly. This is a
13217 breaking change in the control protocol. (The field seems to be
13218 ignored by the most common known controllers.) Fixes bug 18146;
13219 bugfix on 0.1.1.4-alpha.
13221 o Minor bugfixes (bug resilience):
13222 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
13223 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
13224 Hans Jerry Illikainen.
13226 o Minor bugfixes (build):
13227 - Replace obsolete Autoconf macros with their modern equivalent and
13228 prevent similar issues in the future. Fixes bug 20990; bugfix
13231 o Minor bugfixes (client, guards):
13232 - Fix bug where Tor would think that there are circuits waiting for
13233 better guards even though those circuits have been freed. Fixes
13234 bug 21142; bugfix on 0.3.0.1-alpha.
13236 o Minor bugfixes (config):
13237 - Don't assert on startup when trying to get the options list and
13238 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
13239 options so of course they aren't ready yet. Fixes bug 21062;
13240 bugfix on 0.2.9.3-alpha.
13242 o Minor bugfixes (controller):
13243 - Make the GETINFO interface for inquiring about entry guards
13244 support the new guards backend. Fixes bug 20823; bugfix
13247 o Minor bugfixes (dead code):
13248 - Remove a redundant check for PidFile changes at runtime in
13249 options_transition_allowed(): this check is already performed
13250 regardless of whether the sandbox is active. Fixes bug 21123;
13251 bugfix on 0.2.5.4-alpha.
13253 o Minor bugfixes (documentation):
13254 - Update the tor manual page to document every option that can not
13255 be changed while tor is running. Fixes bug 21122.
13257 o Minor bugfixes (fallback directories):
13258 - Stop failing when a relay has no uptime data in
13259 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
13260 - Avoid checking fallback candidates' DirPorts if they are down in
13261 OnionOO. When a relay operator has multiple relays, this
13262 prioritizes relays that are up over relays that are down. Fixes
13263 bug 20926; bugfix on 0.2.8.3-alpha.
13264 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
13265 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
13267 o Minor bugfixes (guards, bootstrapping):
13268 - When connecting to a directory guard during bootstrap, do not mark
13269 the guard as successful until we receive a good-looking directory
13270 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
13272 o Minor bugfixes (onion services):
13273 - Fix the config reload pruning of old vs new services so it
13274 actually works when both ephemeral and non-ephemeral services are
13275 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
13276 - Allow the number of introduction points to be as low as 0, rather
13277 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
13279 o Minor bugfixes (IPv6):
13280 - Make IPv6-using clients try harder to find an IPv6 directory
13281 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
13282 - When IPv6 addresses have not been downloaded yet (microdesc
13283 consensus documents don't list relay IPv6 addresses), use hard-
13284 coded addresses for authorities, fallbacks, and configured
13285 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
13286 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
13288 o Minor bugfixes (memory leaks):
13289 - Fix a memory leak when configuring hidden services. Fixes bug
13290 20987; bugfix on 0.3.0.1-alpha.
13292 o Minor bugfixes (portability, also in 0.2.9.9):
13293 - Avoid crashing when Tor is built using headers that contain
13294 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13295 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13297 - Fix Libevent detection on platforms without Libevent 1 headers
13298 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13300 o Minor bugfixes (relay):
13301 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
13302 initializing the keys would reset the DataDirectory to 0700
13303 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
13304 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
13306 o Minor bugfixes (testing):
13307 - Remove undefined behavior from the backtrace generator by removing
13308 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
13310 o Minor bugfixes (unit tests):
13311 - Allow the unit tests to pass even when DNS lookups of bogus
13312 addresses do not fail as expected. Fixes bug 20862 and 20863;
13313 bugfix on unit tests introduced in 0.2.8.1-alpha
13314 through 0.2.9.4-alpha.
13316 o Code simplification and refactoring:
13317 - Refactor code to manipulate global_origin_circuit_list into
13318 separate functions. Closes ticket 20921.
13320 o Documentation (formatting):
13321 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
13322 blocks were incorrectly appearing. Closes ticket 20885.
13324 o Documentation (man page):
13325 - Clarify many options in tor.1 and add some min/max values for
13326 HiddenService options. Closes ticket 21058.
13329 Changes in version 0.2.9.9 - 2017-01-23
13330 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
13331 cause relays and clients to crash, even if they were not built with
13332 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13333 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13334 version should upgrade.
13336 This release also resolves a client-side onion service reachability
13337 bug, and resolves a pair of small portability issues.
13339 o Major bugfixes (security):
13340 - Downgrade the "-ftrapv" option from "always on" to "only on when
13341 --enable-expensive-hardening is provided." This hardening option,
13342 like others, can turn survivable bugs into crashes -- and having
13343 it on by default made a (relatively harmless) integer overflow bug
13344 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13345 bugfix on 0.2.9.1-alpha.
13347 o Major bugfixes (client, onion service):
13348 - Fix a client-side onion service reachability bug, where multiple
13349 socks requests to an onion service (or a single slow request)
13350 could cause us to mistakenly mark some of the service's
13351 introduction points as failed, and we cache that failure so
13352 eventually we run out and can't reach the service. Also resolves a
13353 mysterious "Remote server sent bogus reason code 65021" log
13354 warning. The bug was introduced in ticket 17218, where we tried to
13355 remember the circuit end reason as a uint16_t, which mangled
13356 negative values. Partially fixes bug 21056 and fixes bug 20307;
13357 bugfix on 0.2.8.1-alpha.
13359 o Minor features (geoip):
13360 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13363 o Minor bugfixes (portability):
13364 - Avoid crashing when Tor is built using headers that contain
13365 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13366 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13368 - Fix Libevent detection on platforms without Libevent 1 headers
13369 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13372 Changes in version 0.3.0.1-alpha - 2016-12-19
13373 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
13374 series. It strengthens Tor's link and circuit handshakes by
13375 identifying relays by their Ed25519 keys, improves the algorithm that
13376 clients use to choose and maintain their list of guards, and includes
13377 additional backend support for the next-generation hidden service
13378 design. It also contains numerous other small features and
13379 improvements to security, correctness, and performance.
13381 Below are the changes since 0.2.9.8.
13383 o Major features (guard selection algorithm):
13384 - Tor's guard selection algorithm has been redesigned from the
13385 ground up, to better support unreliable networks and restrictive
13386 sets of entry nodes, and to better resist guard-capture attacks by
13387 hostile local networks. Implements proposal 271; closes
13390 o Major features (next-generation hidden services):
13391 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
13392 prop224 aka "Next Generation Hidden Services". Service and clients
13393 don't use this functionality yet. Closes ticket 19043. Based on
13394 initial code by Alec Heifetz.
13395 - Relays now support the HSDir version 3 protocol, so that they can
13396 can store and serve v3 descriptors. This is part of the next-
13397 generation onion service work detailed in proposal 224. Closes
13400 o Major features (protocol, ed25519 identity keys):
13401 - Relays now use Ed25519 to prove their Ed25519 identities and to
13402 one another, and to clients. This algorithm is faster and more
13403 secure than the RSA-based handshake we've been doing until now.
13404 Implements the second big part of proposal 220; Closes
13406 - Clients now support including Ed25519 identity keys in the EXTEND2
13407 cells they generate. By default, this is controlled by a consensus
13408 parameter, currently disabled. You can turn this feature on for
13409 testing by setting ExtendByEd25519ID in your configuration. This
13410 might make your traffic appear different than the traffic
13411 generated by other users, however. Implements part of ticket
13412 15056; part of proposal 220.
13413 - Relays now understand requests to extend to other relays by their
13414 Ed25519 identity keys. When an Ed25519 identity key is included in
13415 an EXTEND2 cell, the relay will only extend the circuit if the
13416 other relay can prove ownership of that identity. Implements part
13417 of ticket 15056; part of proposal 220.
13419 o Major bugfixes (scheduler):
13420 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
13421 caused the channel scheduler to behave more or less randomly,
13422 rather than preferring channels with higher-priority circuits.
13423 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
13425 o Minor features (controller):
13426 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
13427 rather than "unrecognized." Closes ticket 20389; patch from
13430 o Minor features (diagnostic, directory client):
13431 - Warn when we find an unexpected inconsistency in directory
13432 download status objects. Prevents some negative consequences of
13435 o Minor features (directory authority):
13436 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
13437 default) to control whether authorities should try to probe relays
13438 by their Ed25519 link keys. This option will go away in a few
13439 releases--unless we encounter major trouble in our ed25519 link
13440 protocol rollout, in which case it will serve as a safety option.
13442 o Minor features (directory cache):
13443 - Relays and bridges will now refuse to serve the consensus they
13444 have if they know it is too old for a client to use. Closes
13447 o Minor features (ed25519 link handshake):
13448 - Advertise support for the ed25519 link handshake using the
13449 subprotocol-versions mechanism, so that clients can tell which
13450 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
13452 o Minor features (fingerprinting resistance, authentication):
13453 - Extend the length of RSA keys used for TLS link authentication to
13454 2048 bits. (These weren't used for forward secrecy; for forward
13455 secrecy, we used P256.) Closes ticket 13752.
13457 o Minor features (infrastructure):
13458 - Implement smartlist_add_strdup() function. Replaces the use of
13459 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
13461 o Minor bugfixes (client):
13462 - When clients that use bridges start up with a cached consensus on
13463 disk, they were ignoring it and downloading a new one. Now they
13464 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
13466 o Minor bugfixes (configuration):
13467 - Accept non-space whitespace characters after the severity level in
13468 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
13469 - Support "TByte" and "TBytes" units in options given in bytes.
13470 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
13471 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
13473 o Minor bugfixes (consensus weight):
13474 - Add new consensus method that initializes bw weights to 1 instead
13475 of 0. This prevents a zero weight from making it all the way to
13476 the end (happens in small testing networks) and causing an error.
13477 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
13479 o Minor bugfixes (descriptors):
13480 - Correctly recognise downloaded full descriptors as valid, even
13481 when using microdescriptors as circuits. This affects clients with
13482 FetchUselessDescriptors set, and may affect directory authorities.
13483 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
13485 o Minor bugfixes (directory system):
13486 - Download all consensus flavors, descriptors, and authority
13487 certificates when FetchUselessDescriptors is set, regardless of
13488 whether tor is a directory cache or not. Fixes bug 20667; bugfix
13489 on all recent tor versions.
13490 - Bridges and relays now use microdescriptors (like clients do)
13491 rather than old-style router descriptors. Now bridges will blend
13492 in with clients in terms of the circuits they build. Fixes bug
13493 6769; bugfix on 0.2.3.2-alpha.
13495 o Minor bugfixes (ed25519 certificates):
13496 - Correctly interpret ed25519 certificates that would expire some
13497 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
13499 o Minor bugfixes (hidden services):
13500 - Stop ignoring misconfigured hidden services. Instead, refuse to
13501 start tor until the misconfigurations have been corrected. Fixes
13502 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
13505 o Minor bugfixes (memory leak at exit):
13506 - Fix a small harmless memory leak at exit of the previously unused
13507 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
13510 o Minor bugfixes (util):
13511 - When finishing writing a file to disk, if we were about to replace
13512 the file with the temporary file created before and we fail to
13513 replace it, remove the temporary file so it doesn't stay on disk.
13514 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
13516 o Minor bugfixes (Windows):
13517 - Check for getpagesize before using it to mmap files. This fixes
13518 compilation in some MinGW environments. Fixes bug 20530; bugfix on
13519 0.1.2.1-alpha. Reported by "ice".
13521 o Code simplification and refactoring:
13522 - Abolish all global guard context in entrynodes.c; replace with new
13523 guard_selection_t structure as preparation for proposal 271.
13524 Closes ticket 19858.
13525 - Introduce rend_service_is_ephemeral() that tells if given onion
13526 service is ephemeral. Replace unclear NULL-checkings for service
13527 directory with this function. Closes ticket 20526.
13528 - Extract magic numbers in circuituse.c into defined variables.
13529 - Refactor circuit_is_available_for_use to remove unnecessary check.
13530 - Refactor circuit_predict_and_launch_new for readability and
13531 testability. Closes ticket 18873.
13532 - Refactor large if statement in purpose_needs_anonymity to use
13533 switch statement instead. Closes part of ticket 20077.
13534 - Refactor the hashing API to return negative values for errors, as
13535 is done as throughout the codebase. Closes ticket 20717.
13536 - Remove data structures that were used to index or_connection
13537 objects by their RSA identity digests. These structures are fully
13538 redundant with the similar structures used in the
13539 channel abstraction.
13540 - Remove duplicate code in the channel_write_*cell() functions.
13541 Closes ticket 13827; patch from Pingl.
13542 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
13543 use only purpose_needs_anonymity. Closes part of ticket 20077.
13544 - The code to generate and parse EXTEND and EXTEND2 cells has been
13545 replaced with code automatically generated by the
13549 - Include the "TBits" unit in Tor's man page. Fixes part of bug
13550 20622; bugfix on 0.2.5.1-alpha.
13551 - Change '1' to 'weight_scale' in consensus bw weights calculation
13552 comments, as that is reality. Closes ticket 20273. Patch
13554 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
13555 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
13557 - Stop the man page from incorrectly stating that HiddenServiceDir
13558 must already exist. Fixes 20486.
13559 - Clarify that when ClientRejectInternalAddresses is enabled (which
13560 is the default), multicast DNS hostnames for machines on the local
13561 network (of the form *.local) are also rejected. Closes
13564 o Removed features:
13565 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
13566 limit for relays running on a single IP applies to authority IP
13567 addresses as well as to non-authority IP addresses. Closes
13569 - The UseDirectoryGuards torrc option no longer exists: all users
13570 that use entry guards will also use directory guards. Related to
13571 proposal 271; implements part of ticket 20831.
13574 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
13575 from "overcaffeinated".
13576 - Perform the coding style checks when running the tests and fail
13577 when coding style violations are found. Closes ticket 5500.
13578 - Add tests for networkstatus_compute_bw_weights_v10.
13579 - Add unit tests circuit_predict_and_launch_new.
13580 - Extract dummy_origin_circuit_new so it can be used by other
13584 Changes in version 0.2.8.12 - 2016-12-19
13585 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
13586 below) where Tor clients could crash when attempting to visit a
13587 hostile hidden service. Clients are recommended to upgrade as packages
13588 become available for their systems.
13590 It also includes an updated list of fallback directories, backported
13593 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
13594 backported to 0.2.8 in the future.
13596 o Major bugfixes (parsing, security, backported from 0.2.9.8):
13597 - Fix a bug in parsing that could cause clients to read a single
13598 byte past the end of an allocated region. This bug could be used
13599 to cause hardened clients (built with --enable-expensive-hardening)
13600 to crash if they tried to visit a hostile hidden service. Non-
13601 hardened clients are only affected depending on the details of
13602 their platform's memory allocator. Fixes bug 21018; bugfix on
13603 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13604 2016-12-002 and as CVE-2016-1254.
13606 o Minor features (fallback directory list, backported from 0.2.9.8):
13607 - Replace the 81 remaining fallbacks of the 100 originally
13608 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13609 fallbacks (123 new, 54 existing, 27 removed) generated in December
13610 2016. Resolves ticket 20170.
13612 o Minor features (geoip, backported from 0.2.9.7-rc):
13613 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13617 Changes in version 0.2.9.8 - 2016-12-19
13618 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
13620 The Tor 0.2.9 series makes mandatory a number of security features
13621 that were formerly optional. It includes support for a new shared-
13622 randomness protocol that will form the basis for next generation
13623 hidden services, includes a single-hop hidden service mode for
13624 optimizing .onion services that don't actually want to be hidden,
13625 tries harder not to overload the directory authorities with excessive
13626 downloads, and supports a better protocol versioning scheme for
13627 improved compatibility with other implementations of the Tor protocol.
13629 And of course, there are numerous other bugfixes and improvements.
13631 This release also includes a fix for a medium-severity issue (bug
13632 21018 below) where Tor clients could crash when attempting to visit a
13633 hostile hidden service. Clients are recommended to upgrade as packages
13634 become available for their systems.
13636 Below are the changes since 0.2.9.7-rc. For a list of all changes
13637 since 0.2.8, see the ReleaseNotes file.
13639 o Major bugfixes (parsing, security):
13640 - Fix a bug in parsing that could cause clients to read a single
13641 byte past the end of an allocated region. This bug could be used
13642 to cause hardened clients (built with --enable-expensive-hardening)
13643 to crash if they tried to visit a hostile hidden service. Non-
13644 hardened clients are only affected depending on the details of
13645 their platform's memory allocator. Fixes bug 21018; bugfix on
13646 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13647 2016-12-002 and as CVE-2016-1254.
13649 o Minor features (fallback directory list):
13650 - Replace the 81 remaining fallbacks of the 100 originally
13651 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13652 fallbacks (123 new, 54 existing, 27 removed) generated in December
13653 2016. Resolves ticket 20170.
13656 Changes in version 0.2.9.7-rc - 2016-12-12
13657 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
13658 including a few that had prevented tests from passing on
13661 o Minor features (geoip):
13662 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13665 o Minor bugfix (build):
13666 - The current Git revision when building from a local repository is
13667 now detected correctly when using git worktrees. Fixes bug 20492;
13668 bugfix on 0.2.3.9-alpha.
13670 o Minor bugfixes (directory authority):
13671 - When computing old Tor protocol line version in protover, we were
13672 looking at 0.2.7.5 twice instead of a specific case for
13673 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
13675 o Minor bugfixes (download scheduling):
13676 - Resolve a "bug" warning when considering a download schedule whose
13677 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
13679 o Minor bugfixes (logging):
13680 - Downgrade a harmless log message about the
13681 pending_entry_connections list from "warn" to "info". Mitigates
13684 o Minor bugfixes (memory leak):
13685 - Fix a small memory leak when receiving AF_UNIX connections on a
13686 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
13687 - When moving a signed descriptor object from a source to an
13688 existing destination, free the allocated memory inside that
13689 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
13691 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
13692 - Fix a memory leak and use-after-free error when removing entries
13693 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
13694 0.2.5.5-alpha. Patch from "cypherpunks".
13696 o Minor bugfixes (portability):
13697 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
13698 Fixes bug 20935; bugfix on 0.2.9.6-rc.
13700 o Minor bugfixes (unit tests):
13701 - Stop expecting NetBSD unit tests to report success for ipfw. Part
13702 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
13703 - Fix tolerances in unit tests for monotonic time comparisons
13704 between nanoseconds and microseconds. Previously, we accepted a 10
13705 us difference only, which is not realistic on every platform's
13706 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
13707 - Remove a double-free in the single onion service unit test. Stop
13708 ignoring a return value. Make future changes less error-prone.
13709 Fixes bug 20864; bugfix on 0.2.9.6-rc.
13712 Changes in version 0.2.8.11 - 2016-12-08
13713 Tor 0.2.8.11 backports fixes for additional portability issues that
13714 could prevent Tor from building correctly on OSX Sierra, or with
13715 OpenSSL 1.1. Affected users should upgrade; others can safely stay
13718 o Minor bugfixes (portability):
13719 - Avoid compilation errors when building on OSX Sierra. Sierra began
13720 to support the getentropy() and clock_gettime() APIs, but created
13721 a few problems in doing so. Tor 0.2.9 has a more thorough set of
13722 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
13723 monotonic time interfaces. Fixes bug 20865. Bugfix
13726 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13727 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13728 architectures. Closes ticket 20588.
13731 Changes in version 0.2.8.10 - 2016-12-02
13732 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
13733 unusable after they left standby mode. It also backports fixes for
13734 a few portability issues and a small but problematic memory leak.
13736 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
13737 - When Tor leaves standby because of a new application request, open
13738 circuits as needed to serve that request. Previously, we would
13739 potentially wait a very long time. Fixes part of bug 19969; bugfix
13742 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
13743 - Clients now respond to new application stream requests immediately
13744 when they arrive, rather than waiting up to one second before
13745 starting to handle them. Fixes part of bug 19969; bugfix
13748 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
13749 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13750 successfully targeting earlier versions of OSX. Resolves
13753 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13754 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13755 20551; bugfix on 0.2.1.1-alpha.
13757 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
13758 - Work around a memory leak in OpenSSL 1.1 when encoding public
13759 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13761 o Minor features (geoip):
13762 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13765 Changes in version 0.2.9.6-rc - 2016-12-02
13766 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
13767 version. We hope that it will be ready to become stable soon, and we
13768 encourage everyone to test this release. If no showstopper bugs are
13769 found here, the next 0.2.9 release will be stable.
13771 o Major bugfixes (relay, resolver, logging):
13772 - For relays that don't know their own address, avoid attempting a
13773 local hostname resolve for each descriptor we download. This
13774 will cut down on the number of "Success: chose address 'x.x.x.x'"
13775 log lines, and also avoid confusing clock jumps if the resolver
13776 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
13778 o Minor bugfixes (client, fascistfirewall):
13779 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
13780 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
13782 o Minor bugfixes (hidden services):
13783 - Stop ignoring the anonymity status of saved keys for hidden
13784 services and single onion services when first starting tor.
13785 Instead, refuse to start tor if any hidden service key has been
13786 used in a different hidden service anonymity mode. Fixes bug
13787 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
13789 o Minor bugfixes (portability):
13790 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13791 successfully targeting earlier versions of OSX. Resolves
13793 - Run correctly when built on Windows build environments that
13794 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
13796 o Minor bugfixes (single onion services, Tor2web):
13797 - Stop complaining about long-term one-hop circuits deliberately
13798 created by single onion services and Tor2web. These log messages
13799 are intended to diagnose issue 8387, which relates to circuits
13800 hanging around forever for no reason. Fixes bug 20613; bugfix on
13801 0.2.9.1-alpha. Reported by "pastly".
13803 o Minor bugfixes (unit tests):
13804 - Stop spurious failures in the local interface address discovery
13805 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
13809 - Correct the minimum bandwidth value in torrc.sample, and queue a
13810 corresponding change for torrc.minimal. Closes ticket 20085.
13813 Changes in version 0.2.9.5-alpha - 2016-11-08
13814 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
13815 version. We believe one or two probably remain, and we encourage
13816 everyone to test this release.
13818 o Major bugfixes (client performance):
13819 - Clients now respond to new application stream requests immediately
13820 when they arrive, rather than waiting up to one second before
13821 starting to handle them. Fixes part of bug 19969; bugfix
13824 o Major bugfixes (client reliability):
13825 - When Tor leaves standby because of a new application request, open
13826 circuits as needed to serve that request. Previously, we would
13827 potentially wait a very long time. Fixes part of bug 19969; bugfix
13830 o Major bugfixes (download scheduling):
13831 - When using an exponential backoff schedule, do not give up on
13832 downloading just because we have failed a bunch of times. Since
13833 each delay is longer than the last, retrying indefinitely won't
13834 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
13835 - If a consensus expires while we are waiting for certificates to
13836 download, stop waiting for certificates.
13837 - If we stop waiting for certificates less than a minute after we
13838 started downloading them, do not consider the certificate download
13839 failure a separate failure. Fixes bug 20533; bugfix
13841 - Remove the maximum delay on exponential-backoff scheduling. Since
13842 we now allow an infinite number of failures (see ticket 20536), we
13843 must now allow the time to grow longer on each failure. Fixes part
13844 of bug 20534; bugfix on 0.2.9.1-alpha.
13845 - Make our initial download delays closer to those from 0.2.8. Fixes
13846 another part of bug 20534; bugfix on 0.2.9.1-alpha.
13847 - When determining when to download a directory object, handle times
13848 after 2038 if the operating system supports them. (Someday this
13849 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
13850 - When using exponential backoff in test networks, use a lower
13851 exponent, so the delays do not vary as much. This helps test
13852 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
13854 o Minor features (geoip):
13855 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13858 o Minor bugfixes (client directory scheduling):
13859 - Treat "relay too busy to answer request" as a failed request and a
13860 reason to back off on our retry frequency. This is safe now that
13861 exponential backoffs retry indefinitely, and avoids a bug where we
13862 would reset our download schedule erroneously. Fixes bug 20593;
13863 bugfix on 0.2.9.1-alpha.
13865 o Minor bugfixes (client, logging):
13866 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
13867 assume all nodes support EXTEND2. Use ntor whenever a key is
13868 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
13869 - On DNSPort, stop logging a BUG warning on a failed hostname
13870 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
13872 o Minor bugfixes (hidden services):
13873 - When configuring hidden services, check every hidden service
13874 directory's permissions. Previously, we only checked the last
13875 hidden service. Fixes bug 20529; bugfix the work to fix 13942
13878 o Minor bugfixes (portability):
13879 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13880 architectures. Closes ticket 20588.
13881 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
13882 removed the ECDH ciphers which caused the tests to fail on
13883 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
13884 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13885 20551; bugfix on 0.2.1.1-alpha.
13887 o Minor bugfixes (relay bootstrap):
13888 - Ensure relays don't make multiple connections during bootstrap.
13889 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
13891 o Minor bugfixes (relay):
13892 - Work around a memory leak in OpenSSL 1.1 when encoding public
13893 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13894 - Avoid a small memory leak when informing worker threads about
13895 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
13896 - Do not try to parallelize workers more than 16x without the user
13897 explicitly configuring us to do so, even if we do detect more than
13898 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13900 o Minor bugfixes (single onion services):
13901 - Start correctly when creating a single onion service in a
13902 directory that did not previously exist. Fixes bug 20484; bugfix
13905 o Minor bugfixes (testing):
13906 - Avoid a unit test failure on systems with over 16 detectable CPU
13907 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13910 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
13911 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
13912 - Module-level documentation for several more modules. Closes
13913 tickets 19287 and 19290.
13916 Changes in version 0.2.8.9 - 2016-10-17
13917 Tor 0.2.8.9 backports a fix for a security hole in previous versions
13918 of Tor that would allow a remote attacker to crash a Tor client,
13919 hidden service, relay, or authority. All Tor users should upgrade to
13920 this version, or to 0.2.9.4-alpha. Patches will be released for older
13923 o Major features (security fixes, also in 0.2.9.4-alpha):
13924 - Prevent a class of security bugs caused by treating the contents
13925 of a buffer chunk as if they were a NUL-terminated string. At
13926 least one such bug seems to be present in all currently used
13927 versions of Tor, and would allow an attacker to remotely crash
13928 most Tor instances, especially those compiled with extra compiler
13929 hardening. With this defense in place, such bugs can't crash Tor,
13930 though we should still fix them as they occur. Closes ticket
13931 20384 (TROVE-2016-10-001).
13933 o Minor features (geoip):
13934 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
13938 Changes in version 0.2.9.4-alpha - 2016-10-17
13939 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
13940 that would allow a remote attacker to crash a Tor client, hidden
13941 service, relay, or authority. All Tor users should upgrade to this
13942 version, or to 0.2.8.9. Patches will be released for older versions
13945 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
13946 previous versions of Tor, including the implementation of a feature to
13947 future- proof the Tor ecosystem against protocol changes, some bug
13948 fixes necessary for Tor Browser to use unix domain sockets correctly,
13949 and several portability improvements. We anticipate that this will be
13950 the last alpha in the Tor 0.2.9 series, and that the next release will
13951 be a release candidate.
13953 o Major features (security fixes):
13954 - Prevent a class of security bugs caused by treating the contents
13955 of a buffer chunk as if they were a NUL-terminated string. At
13956 least one such bug seems to be present in all currently used
13957 versions of Tor, and would allow an attacker to remotely crash
13958 most Tor instances, especially those compiled with extra compiler
13959 hardening. With this defense in place, such bugs can't crash Tor,
13960 though we should still fix them as they occur. Closes ticket
13961 20384 (TROVE-2016-10-001).
13963 o Major features (subprotocol versions):
13964 - Tor directory authorities now vote on a set of recommended
13965 subprotocol versions, and on a set of required subprotocol
13966 versions. Clients and relays that lack support for a _required_
13967 subprotocol version will not start; those that lack support for a
13968 _recommended_ subprotocol version will warn the user to upgrade.
13969 Closes ticket 19958; implements part of proposal 264.
13970 - Tor now uses "subprotocol versions" to indicate compatibility.
13971 Previously, versions of Tor looked at the declared Tor version of
13972 a relay to tell whether they could use a given feature. Now, they
13973 should be able to rely on its declared subprotocol versions. This
13974 change allows compatible implementations of the Tor protocol(s) to
13975 exist without pretending to be 100% bug-compatible with particular
13976 releases of Tor itself. Closes ticket 19958; implements part of
13979 o Minor feature (fallback directories):
13980 - Remove broken fallbacks from the hard-coded fallback directory
13981 list. Closes ticket 20190; patch by teor.
13983 o Minor features (client, directory):
13984 - Since authorities now omit all routers that lack the Running and
13985 Valid flags, we assume that any relay listed in the consensus must
13986 have those flags. Closes ticket 20001; implements part of
13989 o Minor features (compilation, portability):
13990 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
13993 o Minor features (development tools, etags):
13994 - Teach the "make tags" Makefile target how to correctly find
13995 "MOCK_IMPL" function definitions. Patch from nherring; closes
13998 o Minor features (geoip):
13999 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
14002 o Minor features (unix domain sockets):
14003 - When configuring a unix domain socket for a SocksPort,
14004 ControlPort, or Hidden service, you can now wrap the address in
14005 quotes, using C-style escapes inside the quotes. This allows unix
14006 domain socket paths to contain spaces.
14008 o Minor features (virtual addresses):
14009 - Increase the maximum number of bits for the IPv6 virtual network
14010 prefix from 16 to 104. In this way, the condition for address
14011 allocation is less restrictive. Closes ticket 20151; feature
14014 o Minor bugfixes (address discovery):
14015 - Stop reordering IP addresses returned by the OS. This makes it
14016 more likely that Tor will guess the same relay IP address every
14017 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
14018 Reported by René Mayrhofer, patch by "cypherpunks".
14020 o Minor bugfixes (client, unix domain sockets):
14021 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
14022 the client address is meaningless. Fixes bug 20261; bugfix
14025 o Minor bugfixes (compilation, OpenBSD):
14026 - Detect Libevent2 functions correctly on systems that provide
14027 libevent2, but where libevent1 is linked with -levent. Fixes bug
14028 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
14030 o Minor bugfixes (configuration):
14031 - When parsing quoted configuration values from the torrc file,
14032 handle windows line endings correctly. Fixes bug 19167; bugfix on
14033 0.2.0.16-alpha. Patch from "Pingl".
14035 o Minor bugfixes (getpass):
14036 - Defensively fix a non-triggerable heap corruption at do_getpass()
14037 to protect ourselves from mistakes in the future. Fixes bug
14038 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
14041 o Minor bugfixes (hidden service):
14042 - Allow hidden services to run on IPv6 addresses even when the
14043 IPv6Exit option is not set. Fixes bug 18357; bugfix
14047 - Add module-level internal documentation for 36 C files that
14048 previously didn't have a high-level overview. Closes ticket #20385.
14050 o Required libraries:
14051 - When building with OpenSSL, Tor now requires version 1.0.1 or
14052 later. OpenSSL 1.0.0 and earlier are no longer supported by the
14053 OpenSSL team, and should not be used. Closes ticket 20303.
14056 Changes in version 0.2.9.3-alpha - 2016-09-23
14057 Tor 0.2.9.3-alpha adds improved support for entities that want to make
14058 high-performance services available through the Tor .onion mechanism
14059 without themselves receiving anonymity as they host those services. It
14060 also tries harder to ensure that all steps on a circuit are using the
14061 strongest crypto possible, strengthens some TLS properties, and
14062 resolves several bugs -- including a pair of crash bugs from the 0.2.8
14063 series. Anybody running an earlier version of 0.2.9.x should upgrade.
14065 o Major bugfixes (crash, also in 0.2.8.8):
14066 - Fix a complicated crash bug that could affect Tor clients
14067 configured to use bridges when replacing a networkstatus consensus
14068 in which one of their bridges was mentioned. OpenBSD users saw
14069 more crashes here, but all platforms were potentially affected.
14070 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14072 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
14073 - Fix a timing-dependent assertion failure that could occur when we
14074 tried to flush from a circuit after having freed its cells because
14075 of an out-of-memory condition. Fixes bug 20203; bugfix on
14076 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14079 o Major features (circuit building, security):
14080 - Authorities, relays and clients now require ntor keys in all
14081 descriptors, for all hops (except for rare hidden service protocol
14082 cases), for all circuits, and for all other roles. Part of
14084 - Tor authorities, relays, and clients only use ntor, except for
14085 rare cases in the hidden service protocol. Part of ticket 19163.
14087 o Major features (single-hop "hidden" services):
14088 - Add experimental HiddenServiceSingleHopMode and
14089 HiddenServiceNonAnonymousMode options. When both are set to 1,
14090 every hidden service on a Tor instance becomes a non-anonymous
14091 Single Onion Service. Single Onions make one-hop (direct)
14092 connections to their introduction and rendezvous points. One-hop
14093 circuits make Single Onion servers easily locatable, but clients
14094 remain location-anonymous. This is compatible with the existing
14095 hidden service implementation, and works on the current tor
14096 network without any changes to older relays or clients. Implements
14097 proposal 260, completes ticket 17178. Patch by teor and asn.
14099 o Major features (resource management):
14100 - Tor can now notice it is about to run out of sockets, and
14101 preemptively close connections of lower priority. (This feature is
14102 off by default for now, since the current prioritizing method is
14103 yet not mature enough. You can enable it by setting
14104 "DisableOOSCheck 0", but watch out: it might close some sockets
14105 you would rather have it keep.) Closes ticket 18640.
14107 o Major bugfixes (circuit building):
14108 - Hidden service client-to-intro-point and service-to-rendezvous-
14109 point circuits use the TAP key supplied by the protocol, to avoid
14110 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
14112 o Major bugfixes (compilation, OpenBSD):
14113 - Fix a Libevent-detection bug in our autoconf script that would
14114 prevent Tor from linking successfully on OpenBSD. Patch from
14115 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
14117 o Major bugfixes (hidden services):
14118 - Clients now require hidden services to include the TAP keys for
14119 their intro points in the hidden service descriptor. This prevents
14120 an inadvertent upgrade to ntor, which a malicious hidden service
14121 could use to distinguish clients by consensus version. Fixes bug
14122 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
14124 o Minor features (security, TLS):
14125 - Servers no longer support clients that without AES ciphersuites.
14126 (3DES is no longer considered an acceptable cipher.) We believe
14127 that no such Tor clients currently exist, since Tor has required
14128 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
14130 o Minor feature (fallback directories):
14131 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
14132 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
14133 2016. Closes ticket 20190; patch by teor.
14135 o Minor features (geoip, also in 0.2.8.8):
14136 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14139 o Minor feature (port flags):
14140 - Add new flags to the *Port options to finer control over which
14141 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
14142 and the synthetic flag OnionTrafficOnly, which is equivalent to
14143 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
14144 18693; patch by "teor".
14146 o Minor features (directory authority):
14147 - After voting, if the authorities decide that a relay is not
14148 "Valid", they no longer include it in the consensus at all. Closes
14149 ticket 20002; implements part of proposal 272.
14151 o Minor features (testing):
14152 - Disable memory protections on OpenBSD when performing our unit
14153 tests for memwipe(). The test deliberately invokes undefined
14154 behavior, and the OpenBSD protections interfere with this. Patch
14155 from "rubiate". Closes ticket 20066.
14157 o Minor features (testing, ipv6):
14158 - Add the single-onion and single-onion-ipv6 chutney targets to
14159 "make test-network-all". This requires a recent chutney version
14160 with the single onion network flavours (git c72a652 or later).
14161 Closes ticket 20072; patch by teor.
14162 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
14163 tests. Remove bridges+hs, as it's somewhat redundant. This
14164 requires a recent chutney version that supports IPv6 clients,
14165 relays, and authorities. Closes ticket 20069; patch by teor.
14167 o Minor features (Tor2web):
14168 - Make Tor2web clients respect ReachableAddresses. This feature was
14169 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
14170 0.2.8.7. Implements feature 20034. Patch by teor.
14172 o Minor features (unit tests):
14173 - We've done significant work to make the unit tests run faster.
14174 - Our link-handshake unit tests now check that when invalid
14175 handshakes fail, they fail with the error messages we expected.
14176 - Our unit testing code that captures log messages no longer
14177 prevents them from being written out if the user asked for them
14178 (by passing --debug or --info or or --notice --warn to the "test"
14179 binary). This change prevents us from missing unexpected log
14180 messages simply because we were looking for others. Related to
14182 - The unit tests now log all warning messages with the "BUG" flag.
14183 Previously, they only logged errors by default. This change will
14184 help us make our testing code more correct, and make sure that we
14185 only hit this code when we mean to. In the meantime, however,
14186 there will be more warnings in the unit test logs than before.
14187 This is preparatory work for ticket 19999.
14188 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
14189 assertion as a test failure.
14191 o Minor bug fixes (circuits):
14192 - Use the CircuitBuildTimeout option whenever
14193 LearnCircuitBuildTimeout is disabled. Previously, we would respect
14194 the option when a user disabled it, but not when it was disabled
14195 because some other option was set. Fixes bug 20073; bugfix on
14196 0.2.4.12-alpha. Patch by teor.
14198 o Minor bugfixes (allocation):
14199 - Change how we allocate memory for large chunks on buffers, to
14200 avoid a (currently impossible) integer overflow, and to waste less
14201 space when allocating unusually large chunks. Fixes bug 20081;
14202 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
14203 - Always include orconfig.h before including any other C headers.
14204 Sometimes, it includes macros that affect the behavior of the
14205 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
14206 first version to use AC_USE_SYSTEM_EXTENSIONS).
14207 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
14208 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
14209 Patch from Gisle Vanem.
14210 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
14211 They apparently require a set of annotations that we aren't
14212 currently using, and they create false positives in our pthreads
14213 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
14215 o Minor bugfixes (directory authority):
14216 - Die with a more useful error when the operator forgets to place
14217 the authority_signing_key file into the keys directory. This
14218 avoids an uninformative assert & traceback about having an invalid
14219 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
14220 - When allowing private addresses, mark Exits that only exit to
14221 private locations as such. Fixes bug 20064; bugfix
14224 o Minor bugfixes (documentation):
14225 - Document the default PathsNeededToBuildCircuits value that's used
14226 by clients when the directory authorities don't set
14227 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
14228 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
14229 - Fix manual for the User option: it takes a username, not a UID.
14230 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
14233 o Minor bugfixes (hidden services):
14234 - Stop logging intro point details to the client log on certain
14235 error conditions. Fixed as part of bug 20012; bugfix on
14236 0.2.4.8-alpha. Patch by teor.
14238 o Minor bugfixes (IPv6, testing):
14239 - Check for IPv6 correctly on Linux when running test networks.
14240 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
14242 o Minor bugfixes (Linux seccomp2 sandbox):
14243 - Add permission to run the sched_yield() and sigaltstack() system
14244 calls, in order to support versions of Tor compiled with asan or
14245 ubsan code that use these calls. Now "sandbox 1" and
14246 "--enable-expensive-hardening" should be compatible on more
14247 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
14249 o Minor bugfixes (logging):
14250 - When logging a message from the BUG() macro, be explicit about
14251 what we were asserting. Previously we were confusing what we were
14252 asserting with what the bug was. Fixes bug 20093; bugfix
14254 - When we are unable to remove the bw_accounting file, do not warn
14255 if the reason we couldn't remove it was that it didn't exist.
14256 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
14258 o Minor bugfixes (option parsing):
14259 - Count unix sockets when counting client listeners (SOCKS, Trans,
14260 NATD, and DNS). This has no user-visible behaviour changes: these
14261 options are set once, and never read. Required for correct
14262 behaviour in ticket 17178. Fixes bug 19677; bugfix on
14263 0.2.6.3-alpha. Patch by teor.
14265 o Minor bugfixes (options):
14266 - Check the consistency of UseEntryGuards and EntryNodes more
14267 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
14269 - Stop changing the configured value of UseEntryGuards on
14270 authorities and Tor2web clients. Fixes bug 20074; bugfix on
14271 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
14274 o Minor bugfixes (Tor2web):
14275 - Prevent Tor2web clients running hidden services, these services
14276 are not anonymous due to the one-hop client paths. Fixes bug
14277 19678. Patch by teor.
14279 o Minor bugfixes (unit tests):
14280 - Fix a shared-random unit test that was failing on big endian
14281 architectures due to internal representation of a integer copied
14282 to a buffer. The test is changed to take a full 32 bytes of data
14283 and use the output of a python script that make the COMMIT and
14284 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
14286 - The tor_tls_server_info_callback unit test no longer crashes when
14287 debug-level logging is turned on. Fixes bug 20041; bugfix
14291 Changes in version 0.2.8.8 - 2016-09-23
14292 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
14293 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
14294 who select public relays as their bridges.
14296 o Major bugfixes (crash):
14297 - Fix a complicated crash bug that could affect Tor clients
14298 configured to use bridges when replacing a networkstatus consensus
14299 in which one of their bridges was mentioned. OpenBSD users saw
14300 more crashes here, but all platforms were potentially affected.
14301 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14303 o Major bugfixes (relay, OOM handler):
14304 - Fix a timing-dependent assertion failure that could occur when we
14305 tried to flush from a circuit after having freed its cells because
14306 of an out-of-memory condition. Fixes bug 20203; bugfix on
14307 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14310 o Minor feature (fallback directories):
14311 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
14312 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
14313 2016. Closes ticket 20190; patch by teor.
14315 o Minor features (geoip):
14316 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14320 Changes in version 0.2.9.2-alpha - 2016-08-24
14321 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
14322 several new features and bugfixes. It also includes an important
14323 authority update and an important bugfix from 0.2.8.7. Everyone who
14324 sets the ReachableAddresses option, and all bridges, are strongly
14325 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
14327 o Directory authority changes (also in 0.2.8.7):
14328 - The "Tonga" bridge authority has been retired; the new bridge
14329 authority is "Bifroest". Closes tickets 19728 and 19690.
14331 o Major bugfixes (client, security, also in 0.2.8.7):
14332 - Only use the ReachableAddresses option to restrict the first hop
14333 in a path. In earlier versions of 0.2.8.x, it would apply to
14334 every hop in the path, with a possible degradation in anonymity
14335 for anyone using an uncommon ReachableAddress setting. Fixes bug
14336 19973; bugfix on 0.2.8.2-alpha.
14338 o Major features (user interface):
14339 - Tor now supports the ability to declare options deprecated, so
14340 that we can recommend that people stop using them. Previously,
14341 this was done in an ad-hoc way. Closes ticket 19820.
14343 o Major bugfixes (directory downloads):
14344 - Avoid resetting download status for consensuses hourly, since we
14345 already have another, smarter retry mechanism. Fixes bug 8625;
14346 bugfix on 0.2.0.9-alpha.
14348 o Minor features (config):
14349 - Warn users when descriptor and port addresses are inconsistent.
14350 Mitigates bug 13953; patch by teor.
14352 o Minor features (geoip):
14353 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14356 o Minor features (user interface):
14357 - There is a new --list-deprecated-options command-line option to
14358 list all of the deprecated options. Implemented as part of
14361 o Minor bugfixes (code style):
14362 - Fix an integer signedness conversion issue in the case conversion
14363 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
14365 o Minor bugfixes (compilation):
14366 - Build correctly on versions of libevent2 without support for
14367 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
14369 - Fix a compilation warning on GCC versions before 4.6. Our
14370 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
14371 when it is also required as an argument to the compiler pragma.
14372 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
14374 o Minor bugfixes (compilation, also in 0.2.8.7):
14375 - Remove an inappropriate "inline" in tortls.c that was causing
14376 warnings on older versions of GCC. Fixes bug 19903; bugfix
14379 o Minor bugfixes (fallback directories, also in 0.2.8.7):
14380 - Avoid logging a NULL string pointer when loading fallback
14381 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14382 and 0.2.8.1-alpha. Report and patch by "rubiate".
14384 o Minor bugfixes (logging):
14385 - Log a more accurate message when we fail to dump a microdescriptor.
14386 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
14388 o Minor bugfixes (memory leak):
14389 - Fix a series of slow memory leaks related to parsing torrc files
14390 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
14392 o Deprecated features:
14393 - A number of DNS-cache-related sub-options for client ports are now
14394 deprecated for security reasons, and may be removed in a future
14395 version of Tor. (We believe that client-side DNS caching is a bad
14396 idea for anonymity, and you should not turn it on.) The options
14397 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
14398 UseIPv4Cache, and UseIPv6Cache.
14399 - A number of options are deprecated for security reasons, and may
14400 be removed in a future version of Tor. The options are:
14401 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
14402 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
14403 CloseHSClientCircuitsImmediatelyOnTimeout,
14404 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
14405 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
14406 UseNTorHandshake, and WarnUnsafeSocks.
14407 - The *ListenAddress options are now deprecated as unnecessary: the
14408 corresponding *Port options should be used instead. These options
14409 may someday be removed. The affected options are:
14410 ControlListenAddress, DNSListenAddress, DirListenAddress,
14411 NATDListenAddress, ORListenAddress, SocksListenAddress,
14412 and TransListenAddress.
14415 - Correct the IPv6 syntax in our documentation for the
14416 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
14419 - We no longer include the (dead, deprecated) bufferevent code in
14420 Tor. Closes ticket 19450. Based on a patch from U+039b.
14423 Changes in version 0.2.8.7 - 2016-08-24
14424 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
14425 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
14426 who sets the ReachableAddresses option, and all bridges, are strongly
14427 encouraged to upgrade.
14429 o Directory authority changes:
14430 - The "Tonga" bridge authority has been retired; the new bridge
14431 authority is "Bifroest". Closes tickets 19728 and 19690.
14433 o Major bugfixes (client, security):
14434 - Only use the ReachableAddresses option to restrict the first hop
14435 in a path. In earlier versions of 0.2.8.x, it would apply to
14436 every hop in the path, with a possible degradation in anonymity
14437 for anyone using an uncommon ReachableAddress setting. Fixes bug
14438 19973; bugfix on 0.2.8.2-alpha.
14440 o Minor features (geoip):
14441 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14444 o Minor bugfixes (compilation):
14445 - Remove an inappropriate "inline" in tortls.c that was causing
14446 warnings on older versions of GCC. Fixes bug 19903; bugfix
14449 o Minor bugfixes (fallback directories):
14450 - Avoid logging a NULL string pointer when loading fallback
14451 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14452 and 0.2.8.1-alpha. Report and patch by "rubiate".
14455 Changes in version 0.2.9.1-alpha - 2016-08-08
14456 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
14457 series. It improves our support for hardened builds and compiler
14458 warnings, deploys some critical infrastructure for improvements to
14459 hidden services, includes a new timing backend that we hope to use for
14460 better support for traffic padding, makes it easier for programmers to
14461 log unexpected events, and contains other small improvements to
14462 security, correctness, and performance.
14464 Below are the changes since 0.2.8.6.
14466 o New system requirements:
14467 - Tor now requires Libevent version 2.0.10-stable or later. Older
14468 versions of Libevent have less efficient backends for several
14469 platforms, and lack the DNS code that we use for our server-side
14470 DNS support. This implements ticket 19554.
14471 - Tor now requires zlib version 1.2 or later, for security,
14472 efficiency, and (eventually) gzip support. (Back when we started,
14473 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
14474 released in 2003. We recommend the latest version.)
14476 o Major features (build, hardening):
14477 - Tor now builds with -ftrapv by default on compilers that support
14478 it. This option detects signed integer overflow (which C forbids),
14479 and turns it into a hard-failure. We do not apply this option to
14480 code that needs to run in constant time to avoid side-channels;
14481 instead, we use -fwrapv in that code. Closes ticket 17983.
14482 - When --enable-expensive-hardening is selected, stop applying the
14483 clang/gcc sanitizers to code that needs to run in constant time.
14484 Although we are aware of no introduced side-channels, we are not
14485 able to prove that there are none. Related to ticket 17983.
14487 o Major features (compilation):
14488 - Our big list of extra GCC warnings is now enabled by default when
14489 building with GCC (or with anything like Clang that claims to be
14490 GCC-compatible). To make all warnings into fatal compilation
14491 errors, pass --enable-fatal-warnings to configure. Closes
14493 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
14494 turn on C and POSIX extensions. (Previously, we attempted to do
14495 this on an ad hoc basis.) Closes ticket 19139.
14497 o Major features (directory authorities, hidden services):
14498 - Directory authorities can now perform the shared randomness
14499 protocol specified by proposal 250. Using this protocol, directory
14500 authorities generate a global fresh random value every day. In the
14501 future, this value will be used by hidden services to select
14502 HSDirs. This release implements the directory authority feature;
14503 the hidden service side will be implemented in the future as part
14504 of proposal 224. Resolves ticket 16943; implements proposal 250.
14506 o Major features (downloading, random exponential backoff):
14507 - When we fail to download an object from a directory service, wait
14508 for an (exponentially increasing) randomized amount of time before
14509 retrying, rather than a fixed interval as we did before. This
14510 prevents a group of Tor instances from becoming too synchronized,
14511 or a single Tor instance from becoming too predictable, in its
14512 download schedule. Closes ticket 15942.
14514 o Major bugfixes (exit policies):
14515 - Avoid disclosing exit outbound bind addresses, configured port
14516 bind addresses, and local interface addresses in relay descriptors
14517 by default under ExitPolicyRejectPrivate. Instead, only reject
14518 these (otherwise unlisted) addresses if
14519 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
14520 0.2.7.2-alpha. Patch by teor.
14522 o Major bugfixes (hidden service client):
14523 - Allow Tor clients with appropriate controllers to work with
14524 FetchHidServDescriptors set to 0. Previously, this option also
14525 disabled descriptor cache lookup, thus breaking hidden services
14526 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
14528 o Minor features (build, hardening):
14529 - Detect and work around a libclang_rt problem that would prevent
14530 clang from finding __mulodi4() on some 32-bit platforms, and thus
14531 keep -ftrapv from linking on those systems. Closes ticket 19079.
14532 - When building on a system without runtime support for the runtime
14533 hardening options, try to log a useful warning at configuration
14534 time, rather than an incomprehensible warning at link time. If
14535 expensive hardening was requested, this warning becomes an error.
14536 Closes ticket 18895.
14538 o Minor features (code safety):
14539 - In our integer-parsing functions, ensure that maxiumum value we
14540 give is no smaller than the minimum value. Closes ticket 19063;
14543 o Minor features (controller):
14544 - Implement new GETINFO queries for all downloads that use
14545 download_status_t to schedule retries. This allows controllers to
14546 examine the schedule for pending downloads. Closes ticket 19323.
14547 - Allow controllers to configure basic client authorization on
14548 hidden services when they create them with the ADD_ONION control
14549 command. Implements ticket 15588. Patch by "special".
14550 - Fire a STATUS_SERVER controller event whenever the hibernation
14551 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
14553 o Minor features (directory authority):
14554 - Directory authorities now only give the Guard flag to a relay if
14555 they are also giving it the Stable flag. This change allows us to
14556 simplify path selection for clients. It should have minimal effect
14557 in practice, since >99% of Guards already have the Stable flag.
14558 Implements ticket 18624.
14559 - Directory authorities now write their v3-status-votes file out to
14560 disk earlier in the consensus process, so we have a record of the
14561 votes even if we abort the consensus process. Resolves
14564 o Minor features (hidden service):
14565 - Stop being so strict about the payload length of "rendezvous1"
14566 cells. We used to be locked in to the "TAP" handshake length, and
14567 now we can handle better handshakes like "ntor". Resolves
14570 o Minor features (infrastructure, time):
14571 - Tor now uses the operating system's monotonic timers (where
14572 available) for internal fine-grained timing. Previously we would
14573 look at the system clock, and then attempt to compensate for the
14574 clock running backwards. Closes ticket 18908.
14575 - Tor now includes an improved timer backend, so that we can
14576 efficiently support tens or hundreds of thousands of concurrent
14577 timers, as will be needed for some of our planned anti-traffic-
14578 analysis work. This code is based on William Ahern's "timeout.c"
14579 project, which implements a "tickless hierarchical timing wheel".
14580 Closes ticket 18365.
14582 o Minor features (logging):
14583 - Provide a more useful warning message when configured with an
14584 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
14585 - When dumping unparseable router descriptors, optionally store them
14586 in separate files, named by digest, up to a configurable size
14587 limit. You can change the size limit by setting the
14588 MaxUnparseableDescSizeToLog option, and disable this feature by
14589 setting that option to 0. Closes ticket 18322.
14590 - Add a set of macros to check nonfatal assertions, for internal
14591 use. Migrating more of our checks to these should help us avoid
14592 needless crash bugs. Closes ticket 18613.
14594 o Minor features (performance):
14595 - Change the "optimistic data" extension from "off by default" to
14596 "on by default". The default was ordinarily overridden by a
14597 consensus option, but when clients were bootstrapping for the
14598 first time, they would not have a consensus to get the option
14599 from. Changing this default saves a round-trip during startup.
14600 Closes ticket 18815.
14602 o Minor features (relay, usability):
14603 - When the directory authorities refuse a bad relay's descriptor,
14604 encourage the relay operator to contact us. Many relay operators
14605 won't notice this line in their logs, but it's a win if even a few
14606 learn why we don't like what their relay was doing. Resolves
14609 o Minor features (testing):
14610 - Let backtrace tests work correctly under AddressSanitizer. Fixes
14611 part of bug 18934; bugfix on 0.2.5.2-alpha.
14612 - Move the test-network.sh script to chutney, and modify tor's test-
14613 network.sh to call the (newer) chutney version when available.
14614 Resolves ticket 19116. Patch by teor.
14615 - Use the lcov convention for marking lines as unreachable, so that
14616 we don't count them when we're generating test coverage data.
14617 Update our coverage tools to understand this convention. Closes
14620 o Minor bugfixes (bootstrap):
14621 - Remember the directory we fetched the consensus or previous
14622 certificates from, and use it to fetch future authority
14623 certificates. This change improves bootstrapping performance.
14624 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
14626 o Minor bugfixes (build):
14627 - The test-stem and test-network makefile targets now depend only on
14628 the tor binary that they are testing. Previously, they depended on
14629 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
14630 patch from "cypherpunks".
14632 o Minor bugfixes (circuits):
14633 - Make sure extend_info_from_router() is only called on servers.
14634 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
14636 o Minor bugfixes (compilation):
14637 - When building with Clang, use a full set of GCC warnings.
14638 (Previously, we included only a subset, because of the way we
14639 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
14641 o Minor bugfixes (directory authority):
14642 - Authorities now sort the "package" lines in their votes, for ease
14643 of debugging. (They are already sorted in consensus documents.)
14644 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
14645 - When parsing a detached signature, make sure we use the length of
14646 the digest algorithm instead of an hardcoded DIGEST256_LEN in
14647 order to avoid comparing bytes out-of-bounds with a smaller digest
14648 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
14650 o Minor bugfixes (documentation):
14651 - Document the --passphrase-fd option in the tor manpage. Fixes bug
14652 19504; bugfix on 0.2.7.3-rc.
14653 - Fix the description of the --passphrase-fd option in the
14654 tor-gencert manpage. The option is used to pass the number of a
14655 file descriptor to read the passphrase from, not to read the file
14656 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
14658 o Minor bugfixes (ephemeral hidden service):
14659 - When deleting an ephemeral hidden service, close its intro points
14660 even if they are not completely open. Fixes bug 18604; bugfix
14663 o Minor bugfixes (guard selection):
14664 - Use a single entry guard even if the NumEntryGuards consensus
14665 parameter is not provided. Fixes bug 17688; bugfix
14667 - Don't mark guards as unreachable if connection_connect() fails.
14668 That function fails for local reasons, so it shouldn't reveal
14669 anything about the status of the guard. Fixes bug 14334; bugfix
14672 o Minor bugfixes (hidden service client):
14673 - Increase the minimum number of internal circuits we preemptively
14674 build from 2 to 3, so a circuit is available when a client
14675 connects to another onion service. Fixes bug 13239; bugfix
14678 o Minor bugfixes (logging):
14679 - When logging a directory ownership mismatch, log the owning
14680 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
14682 o Minor bugfixes (memory leaks):
14683 - Fix a small, uncommon memory leak that could occur when reading a
14684 truncated ed25519 key file. Fixes bug 18956; bugfix
14687 o Minor bugfixes (testing):
14688 - Allow clients to retry HSDirs much faster in test networks. Fixes
14689 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
14690 - Disable ASAN's detection of segmentation faults while running
14691 test_bt.sh, so that we can make sure that our own backtrace
14692 generation code works. Fixes another aspect of bug 18934; bugfix
14693 on 0.2.5.2-alpha. Patch from "cypherpunks".
14694 - Fix the test-network-all target on out-of-tree builds by using the
14695 correct path to the test driver script. Fixes bug 19421; bugfix
14698 o Minor bugfixes (time):
14699 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
14700 bugfix on all released tor versions.
14701 - When computing the difference between two times in milliseconds,
14702 we now round to the nearest millisecond correctly. Previously, we
14703 could sometimes round in the wrong direction. Fixes bug 19428;
14704 bugfix on 0.2.2.2-alpha.
14706 o Minor bugfixes (user interface):
14707 - Display a more accurate number of suppressed messages in the log
14708 rate-limiter. Previously, there was a potential integer overflow
14709 in the counter. Now, if the number of messages hits a maximum, the
14710 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
14712 - Fix a typo in the passphrase prompt for the ed25519 identity key.
14713 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
14715 o Code simplification and refactoring:
14716 - Remove redundant declarations of the MIN macro. Closes
14718 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
14719 Closes ticket 18462; patch from "icanhasaccount".
14720 - Split the 600-line directory_handle_command_get function into
14721 separate functions for different URL types. Closes ticket 16698.
14724 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
14725 ticket 19153. Patch from "U+039b".
14727 o Removed features:
14728 - Remove support for "GET /tor/bytes.txt" DirPort request, and
14729 "GETINFO dir-usage" controller request, which were only available
14730 via a compile-time option in Tor anyway. Feature was added in
14731 0.2.2.1-alpha. Resolves ticket 19035.
14732 - There is no longer a compile-time option to disable support for
14733 TransPort. (If you don't want TransPort; just don't use it.) Patch
14734 from "U+039b". Closes ticket 19449.
14737 - Run more workqueue tests as part of "make check". These had
14738 previously been implemented, but you needed to know special
14739 command-line options to enable them.
14740 - We now have unit tests for our code to reject zlib "compression
14741 bombs". (Fortunately, the code works fine.)
14744 Changes in version 0.2.8.6 - 2016-08-02
14746 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
14748 The Tor 0.2.8 series improves client bootstrapping performance,
14749 completes the authority-side implementation of improved identity
14750 keys for relays, and includes numerous bugfixes and performance
14751 improvements throughout the program. This release continues to
14752 improve the coverage of Tor's test suite. For a full list of
14753 changes since Tor 0.2.7, see the ReleaseNotes file.
14755 Changes since 0.2.8.5-rc:
14757 o Minor features (geoip):
14758 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
14761 o Minor bugfixes (compilation):
14762 - Fix a compilation warning in the unit tests on systems where char
14763 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
14765 o Minor bugfixes (fallback directories):
14766 - Remove 1 fallback that was on the hardcoded list, then opted-out,
14767 leaving 89 of the 100 fallbacks originally introduced in Tor
14768 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
14770 o Minor bugfixes (Linux seccomp2 sandbox):
14771 - Allow more syscalls when running with "Sandbox 1" enabled:
14772 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
14773 some systems, these are required for Tor to start. Fixes bug
14774 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
14775 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
14776 so that get_interface_address6_via_udp_socket_hack() can work.
14777 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
14780 Changes in version 0.2.8.5-rc - 2016-07-07
14781 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
14782 series. If we find no new bugs or regressions here, the first stable
14783 0.2.8 release will be identical to it. It has a few small bugfixes
14784 against previous versions.
14786 o Directory authority changes:
14787 - Urras is no longer a directory authority. Closes ticket 19271.
14789 o Major bugfixes (heartbeat):
14790 - Fix a regression that would crash Tor when the periodic
14791 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
14792 0.2.8.1-alpha. Reported by "kubaku".
14794 o Minor features (build):
14795 - Tor now again builds with the recent OpenSSL 1.1 development
14796 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
14797 - When building manual pages, set the timezone to "UTC", so that the
14798 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
14799 Patch from intrigeri.
14801 o Minor bugfixes (fallback directory selection):
14802 - Avoid errors during fallback selection if there are no eligible
14803 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
14806 o Minor bugfixes (IPv6, microdescriptors):
14807 - Don't check node addresses when we only have a routerstatus. This
14808 allows IPv6-only clients to bootstrap by fetching microdescriptors
14809 from fallback directory mirrors. (The microdescriptor consensus
14810 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
14813 o Minor bugfixes (logging):
14814 - Reduce pointlessly verbose log messages when directory servers
14815 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
14816 0.2.8.1-alpha. Patch by teor.
14817 - When a fallback directory changes its fingerprint from the hard-
14818 coded fingerprint, log a less severe, more explanatory log
14819 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
14821 o Minor bugfixes (Linux seccomp2 sandboxing):
14822 - Allow statistics to be written to disk when "Sandbox 1" is
14823 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
14824 0.2.6.1-alpha respectively.
14826 o Minor bugfixes (user interface):
14827 - Remove a warning message "Service [scrubbed] not found after
14828 descriptor upload". This message appears when one uses HSPOST
14829 control command to upload a service descriptor. Since there is
14830 only a descriptor and no service, showing this message is
14831 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
14833 o Fallback directory list:
14834 - Add a comment to the generated fallback directory list that
14835 explains how to comment out unsuitable fallbacks in a way that's
14836 compatible with the stem fallback parser.
14837 - Update fallback whitelist and blacklist based on relay operator
14838 emails. Blacklist unsuitable (non-working, over-volatile)
14839 fallbacks. Resolves ticket 19071. Patch by teor.
14840 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
14841 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
14842 ticket 19071; patch by teor.
14845 Changes in version 0.2.8.4-rc - 2016-06-15
14846 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
14847 If we find no new bugs or regressions here, the first stable 0.2.8
14848 release will be identical to it. It has a few small bugfixes against
14851 o Major bugfixes (user interface):
14852 - Correctly give a warning in the cases where a relay is specified
14853 by nickname, and one such relay is found, but it is not officially
14854 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
14856 o Minor features (build):
14857 - Tor now builds once again with the recent OpenSSL 1.1 development
14858 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
14860 o Minor features (geoip):
14861 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
14864 o Minor bugfixes (compilation):
14865 - Cause the unit tests to compile correctly on mingw64 versions that
14866 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
14868 o Minor bugfixes (downloading):
14869 - Predict more correctly whether we'll be downloading over HTTP when
14870 we determine the maximum length of a URL. This should avoid a
14871 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
14875 Changes in version 0.2.8.3-alpha - 2016-05-26
14876 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
14877 the course of the 0.2.8 development cycle. It improves the behavior of
14878 directory clients, fixes several crash bugs, fixes a gap in compiler
14879 hardening, and allows the full integration test suite to run on
14882 o Major bugfixes (security, client, DNS proxy):
14883 - Stop a crash that could occur when a client running with DNSPort
14884 received a query with multiple address types, and the first
14885 address type was not supported. Found and fixed by Scott Dial.
14886 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14888 o Major bugfixes (security, compilation):
14889 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
14890 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
14891 cause a compiler warning, thereby making other checks fail, and
14892 needlessly disabling compiler-hardening support. Fixes one case of
14893 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
14895 o Major bugfixes (security, directory authorities):
14896 - Fix a crash and out-of-bounds write during authority voting, when
14897 the list of relays includes duplicate ed25519 identity keys. Fixes
14898 bug 19032; bugfix on 0.2.8.2-alpha.
14900 o Major bugfixes (client, bootstrapping):
14901 - Check if bootstrap consensus downloads are still needed when the
14902 linked connection attaches. This prevents tor making unnecessary
14903 begindir-style connections, which are the only directory
14904 connections tor clients make since the fix for 18483 was merged.
14905 - Fix some edge cases where consensus download connections may not
14906 have been closed, even though they were not needed. Related to fix
14908 - Make relays retry consensus downloads the correct number of times,
14909 rather than the more aggressive client retry count. Fixes part of
14911 - Stop downloading consensuses when we have a consensus, even if we
14912 don't have all the certificates for it yet. Fixes bug 18809;
14913 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
14915 o Major bugfixes (directory mirrors):
14916 - Decide whether to advertise begindir support in the the same way
14917 we decide whether to advertise our DirPort. Allowing these
14918 decisions to become out-of-sync led to surprising behavior like
14919 advertising begindir support when hibernation made us not
14920 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
14923 o Major bugfixes (IPv6 bridges, client):
14924 - Actually use IPv6 addresses when selecting directory addresses for
14925 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
14928 o Major bugfixes (key management):
14929 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14930 pointer to the previous (uninitialized) key value. The impact here
14931 should be limited to a difficult-to-trigger crash, if OpenSSL is
14932 running an engine that makes key generation failures possible, or
14933 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14934 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14937 o Major bugfixes (testing):
14938 - Fix a bug that would block 'make test-network-all' on systems where
14939 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
14940 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
14941 bugfix on 0.2.8.1-alpha.
14943 o Minor features (clients):
14944 - Make clients, onion services, and bridge relays always use an
14945 encrypted begindir connection for directory requests. Resolves
14946 ticket 18483. Patch by "teor".
14948 o Minor features (fallback directory mirrors):
14949 - Give each fallback the same weight for client selection; restrict
14950 fallbacks to one per operator; report fallback directory detail
14951 changes when rebuilding list; add new fallback directory mirrors
14952 to the whitelist; and many other minor simplifications and fixes.
14953 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
14954 0.2.8.1-alpha; patch by "teor".
14955 - Replace the 21 fallbacks generated in January 2016 and included in
14956 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
14957 2016. Closes task 17158; patch by "teor".
14959 o Minor features (geoip):
14960 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
14963 o Minor bugfixes (assert, portability):
14964 - Fix an assertion failure in memarea.c on systems where "long" is
14965 shorter than the size of a pointer. Fixes bug 18716; bugfix
14968 o Minor bugfixes (bootstrap):
14969 - Consistently use the consensus download schedule for authority
14970 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
14972 o Minor bugfixes (build):
14973 - Remove a pair of redundant AM_CONDITIONAL declarations from
14974 configure.ac. Fixes one final case of bug 17744; bugfix
14976 - Resolve warnings when building on systems that are concerned with
14977 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
14979 - When libscrypt.h is found, but no libscrypt library can be linked,
14980 treat libscrypt as absent. Fixes bug 19161; bugfix
14983 o Minor bugfixes (client):
14984 - Turn all TestingClientBootstrap* into non-testing torrc options.
14985 This changes simply renames them by removing "Testing" in front of
14986 them and they do not require TestingTorNetwork to be enabled
14987 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
14988 - Make directory node selection more reliable, mainly for IPv6-only
14989 clients and clients with few reachable addresses. Fixes bug 18929;
14990 bugfix on 0.2.8.1-alpha. Patch by "teor".
14992 o Minor bugfixes (controller, microdescriptors):
14993 - Make GETINFO dir/status-vote/current/consensus conform to the
14994 control specification by returning "551 Could not open cached
14995 consensus..." when not caching consensuses. Fixes bug 18920;
14996 bugfix on 0.2.2.6-alpha.
14998 o Minor bugfixes (crypto, portability):
14999 - The SHA3 and SHAKE routines now produce the correct output on Big
15000 Endian systems. No code calls either algorithm yet, so this is
15001 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
15002 - Tor now builds again with the recent OpenSSL 1.1 development
15003 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
15006 o Minor bugfixes (directories):
15007 - When fetching extrainfo documents, compare their SHA256 digests
15008 and Ed25519 signing key certificates with the routerinfo that led
15009 us to fetch them, rather than with the most recent routerinfo.
15010 Otherwise we generate many spurious warnings about mismatches.
15011 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
15013 o Minor bugfixes (logging):
15014 - When we can't generate a signing key because OfflineMasterKey is
15015 set, do not imply that we should have been able to load it. Fixes
15016 bug 18133; bugfix on 0.2.7.2-alpha.
15017 - Stop periodic_event_dispatch() from blasting twelve lines per
15018 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
15019 - When rejecting a misformed INTRODUCE2 cell, only log at
15020 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
15022 o Minor bugfixes (pluggable transports):
15023 - Avoid reporting a spurious error when we decide that we don't need
15024 to terminate a pluggable transport because it has already exited.
15025 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
15027 o Minor bugfixes (pointer arithmetic):
15028 - Fix a bug in memarea_alloc() that could have resulted in remote
15029 heap write access, if Tor had ever passed an unchecked size to
15030 memarea_alloc(). Fortunately, all the sizes we pass to
15031 memarea_alloc() are pre-checked to be less than 128 kilobytes.
15032 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
15035 o Minor bugfixes (relays):
15036 - Consider more config options when relays decide whether to
15037 regenerate their descriptor. Fixes more of bug 12538; bugfix
15039 - Resolve some edge cases where we might launch an ORPort
15040 reachability check even when DisableNetwork is set. Noticed while
15041 fixing bug 18616; bugfix on 0.2.3.9-alpha.
15043 o Minor bugfixes (statistics):
15044 - We now include consensus downloads via IPv6 in our directory-
15045 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
15047 o Minor bugfixes (testing):
15048 - Allow directories in small networks to bootstrap by skipping
15049 DirPort checks when the consensus has no exits. Fixes bug 19003;
15050 bugfix on 0.2.8.1-alpha. Patch by teor.
15051 - Fix a small memory leak that would occur when the
15052 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
15053 bugfix on 0.2.5.2-alpha.
15055 o Minor bugfixes (time handling):
15056 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
15057 field. Otherwise, our unit tests crash on Windows. Fixes bug
15058 18977; bugfix on 0.2.2.25-alpha.
15061 - Document the contents of the 'datadir/keys' subdirectory in the
15062 manual page. Closes ticket 17621.
15063 - Stop recommending use of nicknames to identify relays in our
15064 MapAddress documentation. Closes ticket 18312.
15067 Changes in version 0.2.8.2-alpha - 2016-03-28
15068 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
15069 bugs in earlier versions of Tor, including some that prevented
15070 authorities using Tor 0.2.7.x from running correctly. IPv6 and
15071 directory support should also be much improved.
15073 o New system requirements:
15074 - Tor no longer supports versions of OpenSSL with a broken
15075 implementation of counter mode. (This bug was present in OpenSSL
15076 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
15077 longer runs with, these versions.
15078 - Tor no longer attempts to support platforms where the "time_t"
15079 type is unsigned. (To the best of our knowledge, only OpenVMS does
15080 this, and Tor has never actually built on OpenVMS.) Closes
15082 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
15083 later (released in 2008 and 2009 respectively). If you are
15084 building Tor from the git repository instead of from the source
15085 distribution, and your tools are older than this, you will need to
15086 upgrade. Closes ticket 17732.
15088 o Major bugfixes (security, pointers):
15089 - Avoid a difficult-to-trigger heap corruption attack when extending
15090 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
15091 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
15092 Reported by Guido Vranken.
15094 o Major bugfixes (bridges, pluggable transports):
15095 - Modify the check for OR connections to private addresses. Allow
15096 bridges on private addresses, including pluggable transports that
15097 ignore the (potentially private) address in the bridge line. Fixes
15098 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
15100 o Major bugfixes (compilation):
15101 - Repair hardened builds under the clang compiler. Previously, our
15102 use of _FORTIFY_SOURCE would conflict with clang's address
15103 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
15105 o Major bugfixes (crash on shutdown):
15106 - Correctly handle detaching circuits from muxes when shutting down.
15107 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
15108 - Fix an assert-on-exit bug related to counting memory usage in
15109 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
15111 o Major bugfixes (crash on startup):
15112 - Fix a segfault during startup: If a Unix domain socket was
15113 configured as listener (such as a ControlSocket or a SocksPort
15114 "unix:" socket), and tor was started as root but not configured to
15115 switch to another user, tor would segfault while trying to string
15116 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
15119 o Major bugfixes (dns proxy mode, crash):
15120 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
15121 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
15123 o Major bugfixes (relays, bridge clients):
15124 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
15125 bridge clients use the address configured in the bridge line.
15126 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
15129 o Major bugfixes (voting):
15130 - Actually enable support for authorities to match routers by their
15131 Ed25519 identities. Previously, the code had been written, but
15132 some debugging code that had accidentally been left in the
15133 codebase made it stay turned off. Fixes bug 17702; bugfix
15135 - When collating votes by Ed25519 identities, authorities now
15136 include a "NoEdConsensus" flag if the ed25519 value (or lack
15137 thereof) for a server does not reflect the majority consensus.
15138 Related to bug 17668; bugfix on 0.2.7.2-alpha.
15139 - When generating a vote with keypinning disabled, never include two
15140 entries for the same ed25519 identity. This bug was causing
15141 authorities to generate votes that they could not parse when a
15142 router violated key pinning by changing its RSA identity but
15143 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
15144 18318. Bugfix on 0.2.7.2-alpha.
15146 o Minor features (security, win32):
15147 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
15148 attack. Fixes bug 18123; bugfix on all tor versions. Patch
15151 o Minor features (bug-resistance):
15152 - Make Tor survive errors involving connections without a
15153 corresponding event object. Previously we'd fail with an
15154 assertion; now we produce a log message. Related to bug 16248.
15156 o Minor features (build):
15157 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
15158 as having possible IPFW support. Closes ticket 18448. Patch from
15159 Steven Chamberlain.
15161 o Minor features (code hardening):
15162 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
15163 level code, to harden against accidental failures to NUL-
15164 terminate. Part of ticket 17852. Patch from jsturgix. Found
15167 o Minor features (crypto):
15168 - Validate the hard-coded Diffie-Hellman parameters and ensure that
15169 p is a safe prime, and g is a suitable generator. Closes
15172 o Minor features (geoip):
15173 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
15176 o Minor features (hidden service directory):
15177 - Streamline relay-side hsdir handling: when relays consider whether
15178 to accept an uploaded hidden service descriptor, they no longer
15179 check whether they are one of the relays in the network that is
15180 "supposed" to handle that descriptor. Implements ticket 18332.
15182 o Minor features (IPv6):
15183 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
15184 to 1, tor prefers IPv6 directory addresses.
15185 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
15186 avoids using IPv4 for client OR and directory connections.
15187 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
15188 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
15189 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
15191 o Minor features (linux seccomp2 sandbox):
15192 - Reject attempts to change our Address with "Sandbox 1" enabled.
15193 Changing Address with Sandbox turned on would never actually work,
15194 but previously it would fail in strange and confusing ways. Found
15195 while fixing 18548.
15197 o Minor features (robustness):
15198 - Exit immediately with an error message if the code attempts to use
15199 Libevent without having initialized it. This should resolve some
15200 frequently-made mistakes in our unit tests. Closes ticket 18241.
15202 o Minor features (unix domain sockets):
15203 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
15204 Unix domain sockets without checking the permissions on the parent
15205 directory. (Tor checks permissions by default because some
15206 operating systems only check permissions on the parent directory.
15207 However, some operating systems do look at permissions on the
15208 socket, and tor's default check is unneeded.) Closes ticket 18458.
15211 o Minor bugfixes (exit policies, security):
15212 - Refresh an exit relay's exit policy when interface addresses
15213 change. Previously, tor only refreshed the exit policy when the
15214 configured external address changed. Fixes bug 18208; bugfix on
15215 0.2.7.3-rc. Patch by teor.
15217 o Minor bugfixes (security, hidden services):
15218 - Prevent hidden services connecting to client-supplied rendezvous
15219 addresses that are reserved as internal or multicast. Fixes bug
15220 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
15222 o Minor bugfixes (build):
15223 - Do not link the unit tests against both the testing and non-
15224 testing versions of the static libraries. Fixes bug 18490; bugfix
15226 - Avoid spurious failures from configure files related to calling
15227 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
15228 0.2.0.1-alpha. Patch from "cypherpunks".
15229 - Silence spurious clang-scan warnings in the ed25519_donna code by
15230 explicitly initializing some objects. Fixes bug 18384; bugfix on
15231 0.2.7.2-alpha. Patch by teor.
15233 o Minor bugfixes (client, bootstrap):
15234 - Count receipt of new microdescriptors as progress towards
15235 bootstrapping. Previously, with EntryNodes set, Tor might not
15236 successfully repopulate the guard set on bootstrapping. Fixes bug
15237 16825; bugfix on 0.2.3.1-alpha.
15239 o Minor bugfixes (code correctness):
15240 - Update to the latest version of Trunnel, which tries harder to
15241 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
15242 by clang address sanitizer. Fixes bug 18373; bugfix
15245 o Minor bugfixes (configuration):
15246 - Fix a tiny memory leak when parsing a port configuration ending in
15247 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
15249 o Minor bugfixes (containers):
15250 - If we somehow attempt to construct a heap with more than
15251 1073741822 elements, avoid an integer overflow when maintaining
15252 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
15254 o Minor bugfixes (correctness):
15255 - Fix a bad memory handling bug that would occur if we had queued a
15256 cell on a channel's incoming queue. Fortunately, we can't actually
15257 queue a cell like that as our code is constructed today, but it's
15258 best to avoid this kind of error, even if there isn't any code
15259 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
15261 o Minor bugfixes (directory):
15262 - When generating a URL for a directory server on an IPv6 address,
15263 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
15264 on 0.2.3.9-alpha. Patch from Malek.
15266 o Minor bugfixes (fallback directory mirrors):
15267 - When requesting extrainfo descriptors from a trusted directory
15268 server, check whether it is an authority or a fallback directory
15269 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
15270 0.2.4.7-alpha. Reported by atagar, patch by teor.
15272 o Minor bugfixes (hidden service, client):
15273 - Handle the case where the user makes several fast consecutive
15274 requests to the same .onion address. Previously, the first six
15275 requests would each trigger a descriptor fetch, each picking a
15276 directory (there are 6 overall) and the seventh one would fail
15277 because no directories were left, thereby triggering a close on
15278 all current directory connections asking for the hidden service.
15279 The solution here is to not close the connections if we have
15280 pending directory fetches. Fixes bug 15937; bugfix
15283 o Minor bugfixes (hidden service, control port):
15284 - Add the onion address to the HS_DESC event for the UPLOADED action
15285 both on success or failure. It was previously hardcoded with
15286 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
15288 o Minor bugfixes (hidden service, directory):
15289 - Bridges now refuse "rendezvous2" (hidden service descriptor)
15290 publish attempts. Suggested by ticket 18332.
15292 o Minor bugfixes (linux seccomp2 sandbox):
15293 - Allow the setrlimit syscall, and the prlimit and prlimit64
15294 syscalls, which some libc implementations use under the hood.
15295 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
15296 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
15297 enabled and no DNS resolvers configured. This should help TAILS
15298 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
15299 - Fix the sandbox's interoperability with unix domain sockets under
15300 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
15302 o Minor bugfixes (logging):
15303 - When logging information about an unparsable networkstatus vote or
15304 consensus, do not say "vote" when we mean consensus. Fixes bug
15305 18368; bugfix on 0.2.0.8-alpha.
15306 - Scrub service name in "unrecognized service ID" log messages.
15307 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
15308 - Downgrade logs and backtraces about IP versions to info-level.
15309 Only log backtraces once each time tor runs. Assists in diagnosing
15310 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
15311 Christian, patch by teor.
15313 o Minor bugfixes (memory safety):
15314 - Avoid freeing an uninitialized pointer when opening a socket fails
15315 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
15316 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
15318 - Correctly duplicate addresses in get_interface_address6_list().
15319 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
15320 patch by "cypherpunks".
15321 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
15323 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
15324 18672; bugfix on 0.2.5.1-alpha.
15326 o Minor bugfixes (private directory):
15327 - Prevent a race condition when creating private directories. Fixes
15328 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
15329 Patch from jsturgix. Found with Flawfinder.
15331 o Minor bugfixes (test networks, IPv6):
15332 - Allow internal IPv6 addresses in descriptors in test networks.
15333 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
15336 o Minor bugfixes (testing):
15337 - We no longer disable assertions in the unit tests when coverage is
15338 enabled. Instead, we require you to say --disable-asserts-in-tests
15339 to the configure script if you need assertions disabled in the
15340 unit tests (for example, if you want to perform branch coverage).
15341 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
15343 o Minor bugfixes (time parsing):
15344 - Avoid overflow in tor_timegm when parsing dates in and after 2038
15345 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
15346 0.0.2pre14. Patch by teor.
15348 o Minor bugfixes (tor-gencert):
15349 - Correctly handle the case where an authority operator enters a
15350 passphrase but sends an EOF before sending a newline. Fixes bug
15351 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
15353 o Code simplification and refactoring:
15354 - Quote all the string interpolations in configure.ac -- even those
15355 which we are pretty sure can't contain spaces. Closes ticket
15356 17744. Patch from zerosion.
15357 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
15358 inplace, so there's no need to have a separate implementation for
15359 the non-inplace code. Closes ticket 18258. Patch from Malek.
15360 - Simplify return types for some crypto functions that can't
15361 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
15364 - Change build messages to refer to "Fedora" instead of "Fedora
15365 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
15366 Patches from "icanhasaccount" and "cypherpunks".
15368 o Removed features:
15369 - We no longer maintain an internal freelist in memarea.c.
15370 Allocators should be good enough to make this code unnecessary,
15371 and it's doubtful that it ever had any performance benefit.
15374 - Fix several warnings from clang's address sanitizer produced in
15376 - Treat backtrace test failures as expected on FreeBSD until we
15377 solve bug 17808. Closes ticket 18204.
15380 Changes in version 0.2.8.1-alpha - 2016-02-04
15381 Tor 0.2.8.1-alpha is the first alpha release in its series. It
15382 includes numerous small features and bugfixes against previous Tor
15383 versions, and numerous small infrastructure improvements. The most
15384 notable features are a set of improvements to the directory subsystem.
15386 o Major features (security, Linux):
15387 - When Tor starts as root on Linux and is told to switch user ID, it
15388 can now retain the capability to bind to low ports. By default,
15389 Tor will do this only when it's switching user ID and some low
15390 ports have been configured. You can change this behavior with the
15391 new option KeepBindCapabilities. Closes ticket 8195.
15393 o Major features (directory system):
15394 - When bootstrapping multiple consensus downloads at a time, use the
15395 first one that starts downloading, and close the rest. This
15396 reduces failures when authorities or fallback directories are slow
15397 or down. Together with the code for feature 15775, this feature
15398 should reduces failures due to fallback churn. Implements ticket
15399 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
15400 "mikeperry" and "teor".
15401 - Include a trial list of 21 default fallback directories, generated
15402 in January 2016, based on an opt-in survey of suitable relays.
15403 Doing this should make clients bootstrap more quickly and reliably,
15404 and reduce the load on the directory authorities. Closes ticket
15405 15775. Patch by "teor".
15406 Candidates identified using an OnionOO script by "weasel", "teor",
15407 "gsathya", and "karsten".
15408 - Previously only relays that explicitly opened a directory port
15409 (DirPort) accepted directory requests from clients. Now all
15410 relays, with and without a DirPort, accept and serve tunneled
15411 directory requests that they receive through their ORPort. You can
15412 disable this behavior using the new DirCache option. Closes
15415 o Major key updates:
15416 - Update the V3 identity key for the dannenberg directory authority:
15417 it was changed on 18 November 2015. Closes task 17906. Patch
15420 o Minor features (security, clock):
15421 - Warn when the system clock appears to move back in time (when the
15422 state file was last written in the future). Tor doesn't know that
15423 consensuses have expired if the clock is in the past. Patch by
15424 "teor". Implements ticket 17188.
15426 o Minor features (security, exit policies):
15427 - ExitPolicyRejectPrivate now rejects more private addresses by
15428 default. Specifically, it now rejects the relay's outbound bind
15429 addresses (if configured), and the relay's configured port
15430 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
15431 0.2.0.11-alpha. Patch by "teor".
15433 o Minor features (security, memory erasure):
15434 - Set the unused entries in a smartlist to NULL. This helped catch
15435 a (harmless) bug, and shouldn't affect performance too much.
15436 Implements ticket 17026.
15437 - Use SecureMemoryWipe() function to securely clean memory on
15438 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
15439 Implements feature 17986.
15440 - Use explicit_bzero or memset_s when present. Previously, we'd use
15441 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
15442 from <logan@hackers.mu> and <selven@hackers.mu>.
15443 - Make memwipe() do nothing when passed a NULL pointer or buffer of
15444 zero size. Check size argument to memwipe() for underflow. Fixes
15445 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
15448 o Minor features (security, RNG):
15449 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
15450 positively are not allowed to fail. Previously we depended on
15451 internal details of OpenSSL's behavior. Closes ticket 17686.
15452 - Never use the system entropy output directly for anything besides
15453 seeding the PRNG. When we want to generate important keys, instead
15454 of using system entropy directly, we now hash it with the PRNG
15455 stream. This may help resist certain attacks based on broken OS
15456 entropy implementations. Closes part of ticket 17694.
15457 - Use modern system calls (like getentropy() or getrandom()) to
15458 generate strong entropy on platforms that have them. Closes
15461 o Minor features (accounting):
15462 - Added two modes to the AccountingRule option: One for limiting
15463 only the number of bytes sent ("AccountingRule out"), and one for
15464 limiting only the number of bytes received ("AccountingRule in").
15465 Closes ticket 15989; patch from "unixninja92".
15467 o Minor features (build):
15468 - Since our build process now uses "make distcheck", we no longer
15469 force "make dist" to depend on "make check". Closes ticket 17893;
15470 patch from "cypherpunks."
15471 - Tor now builds successfully with the recent OpenSSL 1.1
15472 development branch, and with the latest LibreSSL. Closes tickets
15473 17549, 17921, and 17984.
15475 o Minor features (controller):
15476 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
15477 tickets 16774 and 17817. Patch by George Tankersley.
15478 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
15479 service descriptor from a service's local hidden service
15480 descriptor cache. Closes ticket 14846.
15481 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
15482 controllers can examine the the reject rules added by
15483 ExitPolicyRejectPrivate. This makes it easier for stem to display
15486 o Minor features (crypto):
15487 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
15489 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
15490 - When allocating a digest state object, allocate no more space than
15491 we actually need. Previously, we would allocate as much space as
15492 the state for the largest algorithm would need. This change saves
15493 up to 672 bytes per circuit. Closes ticket 17796.
15494 - Improve performance when hashing non-multiple of 8 sized buffers,
15495 based on Andrew Moon's public domain SipHash-2-4 implementation.
15496 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
15498 o Minor features (directory downloads):
15499 - Wait for busy authorities and fallback directories to become non-
15500 busy when bootstrapping. (A similar change was made in 6c443e987d
15501 for directory caches chosen from the consensus.) Closes ticket
15502 17864; patch by "teor".
15503 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
15504 directory mirrors. The default is 1; set it to 0 to disable
15505 fallbacks. Implements ticket 17576. Patch by "teor".
15507 o Minor features (geoip):
15508 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
15511 o Minor features (IPv6):
15512 - Add an argument 'ipv6=address:orport' to the DirAuthority and
15513 FallbackDir torrc options, to specify an IPv6 address for an
15514 authority or fallback directory. Add hard-coded ipv6 addresses for
15515 directory authorities that have them. Closes ticket 17327; patch
15516 from Nick Mathewson and "teor".
15517 - Add address policy assume_action support for IPv6 addresses.
15518 - Limit IPv6 mask bits to 128.
15519 - Warn when comparing against an AF_UNSPEC address in a policy, it's
15520 almost always a bug. Closes ticket 17863; patch by "teor".
15521 - Allow users to configure directory authorities and fallback
15522 directory servers with IPv6 addresses and ORPorts. Resolves
15524 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
15525 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
15526 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
15527 17638; bugfix on 0.0.2pre8. Patch by "teor".
15529 o Minor features (logging):
15530 - When logging to syslog, allow a tag to be added to the syslog
15531 identity (the string prepended to every log message). The tag can
15532 be configured with SyslogIdentityTag and defaults to none. Setting
15533 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
15536 o Minor features (portability):
15537 - Use timingsafe_memcmp() where available. Closes ticket 17944;
15538 patch from <logan@hackers.mu>.
15540 o Minor features (relay, address discovery):
15541 - Add a family argument to get_interface_addresses_raw() and
15542 subfunctions to make network interface address interogation more
15543 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
15544 types of interfaces from the operating system. Resolves
15546 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
15547 fails to enumerate interface addresses using the platform-specific
15548 API, have it rely on the UDP socket fallback technique to try and
15549 find out what IP addresses (both IPv4 and IPv6) our machine has.
15550 Resolves ticket 17951.
15552 o Minor features (replay cache):
15553 - The replay cache now uses SHA256 instead of SHA1. Implements
15554 feature 8961. Patch by "teor", issue reported by "rransom".
15556 o Minor features (unix file permissions):
15557 - Defer creation of Unix sockets until after setuid. This avoids
15558 needing CAP_CHOWN and CAP_FOWNER when using systemd's
15559 CapabilityBoundingSet, or chown and fowner when using SELinux.
15560 Implements part of ticket 17562. Patch from Jamie Nguyen.
15561 - If any directory created by Tor is marked as group readable, the
15562 filesystem group is allowed to be either the default GID or the
15563 root user. Allowing root to read the DataDirectory prevents the
15564 need for CAP_READ_SEARCH when using systemd's
15565 CapabilityBoundingSet, or dac_read_search when using SELinux.
15566 Implements part of ticket 17562. Patch from Jamie Nguyen.
15567 - Introduce a new DataDirectoryGroupReadable option. If it is set to
15568 1, the DataDirectory will be made readable by the default GID.
15569 Implements part of ticket 17562. Patch from Jamie Nguyen.
15571 o Minor bugfixes (accounting):
15572 - The max bandwidth when using 'AccountRule sum' is now correctly
15573 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
15574 from "unixninja92".
15576 o Minor bugfixes (code correctness):
15577 - When closing an entry connection, generate a warning if we should
15578 have sent an end cell for it but we haven't. Fixes bug 17876;
15579 bugfix on 0.2.3.2-alpha.
15580 - Assert that allocated memory held by the reputation code is freed
15581 according to its internal counters. Fixes bug 17753; bugfix
15583 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
15586 o Minor bugfixes (compilation):
15587 - Mark all object files that include micro-revision.i as depending
15588 on it, so as to make parallel builds more reliable. Fixes bug
15589 17826; bugfix on 0.2.5.1-alpha.
15590 - Don't try to use the pthread_condattr_setclock() function unless
15591 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
15592 17819; bugfix on 0.2.6.3-alpha.
15593 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
15595 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15596 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15597 - Fix search for libevent libraries on OpenBSD (and other systems
15598 that install libevent 1 and libevent 2 in parallel). Fixes bug
15599 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
15600 - Isolate environment variables meant for tests from the rest of the
15601 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
15602 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
15604 - Remove config.log only from make distclean, not from make clean.
15605 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
15607 o Minor bugfixes (crypto):
15608 - Check the return value of HMAC() and assert on failure. Fixes bug
15609 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
15611 o Minor bugfixes (fallback directories):
15612 - Mark fallbacks as "too busy" when they return a 503 response,
15613 rather than just marking authorities. Fixes bug 17572; bugfix on
15614 0.2.4.7-alpha. Patch by "teor".
15616 o Minor bugfixes (IPv6):
15617 - Update the limits in max_dl_per_request for IPv6 address length.
15618 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
15620 o Minor bugfixes (linux seccomp2 sandbox):
15621 - Fix a crash when using offline master ed25519 keys with the Linux
15622 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
15624 o Minor bugfixes (logging):
15625 - In log messages that include a function name, use __FUNCTION__
15626 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
15627 with clang __PRETTY_FUNCTION__ has extra information we don't
15628 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
15630 - Remove needless quotes from a log message about unparseable
15631 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
15633 o Minor bugfixes (portability):
15634 - Remove an #endif from configure.ac so that we correctly detect the
15635 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
15638 o Minor bugfixes (relays):
15639 - Check that both the ORPort and DirPort (if present) are reachable
15640 before publishing a relay descriptor. Otherwise, relays publish a
15641 descriptor with DirPort 0 when the DirPort reachability test takes
15642 longer than the ORPort reachability test. Fixes bug 18050; bugfix
15643 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
15645 o Minor bugfixes (relays, hidden services):
15646 - Refuse connection requests to private OR addresses unless
15647 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
15648 then refuse to send any cells to a private address. Fixes bugs
15649 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
15651 o Minor bugfixes (safe logging):
15652 - When logging a malformed hostname received through socks4, scrub
15653 it if SafeLogging says we should. Fixes bug 17419; bugfix
15656 o Minor bugfixes (statistics code):
15657 - Consistently check for overflow in round_*_to_next_multiple_of
15658 functions, and add unit tests with additional and maximal values.
15659 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
15660 - Handle edge cases in the laplace functions: avoid division by
15661 zero, avoid taking the log of zero, and silence clang type
15662 conversion warnings using round and trunc. Add unit tests for edge
15663 cases with maximal values. Fixes part of bug 13192; bugfix
15666 o Minor bugfixes (testing):
15667 - The test for log_heartbeat was incorrectly failing in timezones
15668 with non-integer offsets. Instead of comparing the end of the time
15669 string against a constant, compare it to the output of
15670 format_local_iso_time when given the correct input. Fixes bug
15671 18039; bugfix on 0.2.5.4-alpha.
15672 - Make unit tests pass on IPv6-only systems, and systems without
15673 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
15674 bugfix on 0.2.7.3-rc. Patch by "teor".
15675 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
15677 - Check the full results of SHA256 and SHA512 digests in the unit
15678 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
15680 o Code simplification and refactoring:
15681 - Move logging of redundant policy entries in
15682 policies_parse_exit_policy_internal into its own function. Closes
15683 ticket 17608; patch from "juce".
15684 - Extract the more complicated parts of circuit_mark_for_close()
15685 into a new function that we run periodically before circuits are
15686 freed. This change removes more than half of the functions
15687 currently in the "blob". Closes ticket 17218.
15688 - Clean up a little duplicated code in
15689 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
15691 - Decouple the list of streams waiting to be attached to circuits
15692 from the overall connection list. This change makes it possible to
15693 attach streams quickly while simplifying Tor's callgraph and
15694 avoiding O(N) scans of the entire connection list. Closes
15696 - When a direct directory request fails immediately on launch,
15697 instead of relaunching that request from inside the code that
15698 launches it, instead mark the connection for teardown. This change
15699 simplifies Tor's callback and prevents the directory-request
15700 launching code from invoking itself recursively. Closes
15702 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
15703 use them. Closes ticket 17926.
15706 - Add a description of the correct use of the '--keygen' command-
15707 line option. Closes ticket 17583; based on text by 's7r'.
15708 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
15709 - Explain actual minima for BandwidthRate. Closes ticket 16382.
15710 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
15711 - Mention torspec URL in the manpage and point the reader to it
15712 whenever we mention a document that belongs in torspce. Fixes
15715 o Removed features:
15716 - Remove client-side support for connecting to Tor relays running
15717 versions of Tor before 0.2.3.6-alpha. These relays didn't support
15718 the v3 TLS handshake protocol, and are no longer allowed on the
15719 Tor network. Implements the client side of ticket 11150. Based on
15720 patches by Tom van der Woerdt.
15723 - Add unit tests to check for common RNG failure modes, such as
15724 returning all zeroes, identical values, or incrementing values
15725 (OpenSSL's rand_predictable feature). Patch by "teor".
15726 - Log more information when the backtrace tests fail. Closes ticket
15727 17892. Patch from "cypherpunks."
15728 - Always test both ed25519 backends, so that we can be sure that our
15729 batch-open replacement code works. Part of ticket 16794.
15730 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
15731 portion of ticket 16831.
15732 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
15733 util_format.c, directory.c, and options_validate.c. Closes tickets
15734 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
15736 - Unit tests for directory_handle_command_get. Closes ticket 17004.
15737 Patch from Reinaldo de Souza Jr.
15740 Changes in version 0.2.7.6 - 2015-12-10
15741 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
15742 well as a minor bug in hidden service reliability.
15744 o Major bugfixes (guard selection):
15745 - Actually look at the Guard flag when selecting a new directory
15746 guard. When we implemented the directory guard design, we
15747 accidentally started treating all relays as if they have the Guard
15748 flag during guard selection, leading to weaker anonymity and worse
15749 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
15752 o Minor features (geoip):
15753 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
15756 o Minor bugfixes (compilation):
15757 - When checking for net/pfvar.h, include netinet/in.h if possible.
15758 This fixes transparent proxy detection on OpenBSD. Fixes bug
15759 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
15760 - Fix a compilation warning with Clang 3.6: Do not check the
15761 presence of an address which can never be NULL. Fixes bug 17781.
15763 o Minor bugfixes (correctness):
15764 - When displaying an IPv6 exit policy, include the mask bits
15765 correctly even when the number is greater than 31. Fixes bug
15766 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
15767 - The wrong list was used when looking up expired intro points in a
15768 rend service object, causing what we think could be reachability
15769 issues for hidden services, and triggering a BUG log. Fixes bug
15770 16702; bugfix on 0.2.7.2-alpha.
15771 - Fix undefined behavior in the tor_cert_checksig function. Fixes
15772 bug 17722; bugfix on 0.2.7.2-alpha.
15775 Changes in version 0.2.7.5 - 2015-11-20
15776 The Tor 0.2.7 release series is dedicated to the memory of Tor user
15777 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
15778 tirelessly to advocate human rights regardless of national borders,
15779 and oppose the encroachments of mass surveillance. He opposed national
15780 exceptionalism, he brought clarity to legal and policy debates, he
15781 understood and predicted the impact of mass surveillance on the world,
15782 and he laid the groundwork for resisting it. While serving on the Tor
15783 Project's board of directors, he brought us his uncompromising focus
15784 on technical excellence in the service of humankind. Caspar was an
15785 inimitable force for good and a wonderful friend. He was kind,
15786 humorous, generous, gallant, and believed we should protect one
15787 another without exception. We honor him here for his ideals, his
15788 efforts, and his accomplishments. Please honor his memory with works
15789 that would make him proud.
15791 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
15793 The 0.2.7 series adds a more secure identity key type for relays,
15794 improves cryptography performance, resolves several longstanding
15795 hidden-service performance issues, improves controller support for
15796 hidden services, and includes small bugfixes and performance
15797 improvements throughout the program. This release series also includes
15798 more tests than before, and significant simplifications to which parts
15799 of Tor invoke which others.
15801 (This release contains no code changes since 0.2.7.4-rc.)
15804 Changes in version 0.2.7.4-rc - 2015-10-21
15805 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
15806 fixes some important memory leaks, and a scary-looking (but mostly
15807 harmless in practice) invalid-read bug. It also has a few small
15808 bugfixes, notably fixes for compilation and portability on different
15809 platforms. If no further significant bounds are found, the next
15810 release will the the official stable release.
15812 o Major bugfixes (security, correctness):
15813 - Fix an error that could cause us to read 4 bytes before the
15814 beginning of an openssl string. This bug could be used to cause
15815 Tor to crash on systems with unusual malloc implementations, or
15816 systems with unusual hardening installed. Fixes bug 17404; bugfix
15819 o Major bugfixes (correctness):
15820 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
15821 bug 17401; bugfix on 0.2.7.3-rc.
15823 o Major bugfixes (memory leaks):
15824 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
15825 17398; bugfix on 0.2.6.1-alpha.
15826 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
15827 17402; bugfix on 0.2.7.3-rc.
15828 - Fix a memory leak when reading an expired signing key from disk.
15829 Fixes bug 17403; bugfix on 0.2.7.2-rc.
15831 o Minor features (geoIP):
15832 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
15835 o Minor bugfixes (compilation):
15836 - Repair compilation with the most recent (unreleased, alpha)
15837 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
15838 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
15839 17251; bugfix on 0.2.7.2-alpha.
15840 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15841 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15843 o Minor bugfixes (portability):
15844 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
15845 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
15848 o Minor bugfixes (sandbox):
15849 - Add the "hidserv-stats" filename to our sandbox filter for the
15850 HiddenServiceStatistics option to work properly. Fixes bug 17354;
15851 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
15853 o Minor bugfixes (testing):
15854 - Add unit tests for get_interface_address* failure cases. Fixes bug
15855 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
15856 - Fix breakage when running 'make check' with BSD make. Fixes bug
15857 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
15858 - Make the get_ifaddrs_* unit tests more tolerant of different
15859 network configurations. (Don't assume every test box has an IPv4
15860 address, and don't assume every test box has a non-localhost
15861 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
15862 - Skip backtrace tests when backtrace support is not compiled in.
15863 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
15867 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
15868 - Note that HiddenServicePorts can take a unix domain socket. Closes
15872 Changes in version 0.2.7.3-rc - 2015-09-25
15873 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
15874 contains numerous usability fixes for Ed25519 keys, safeguards against
15875 several misconfiguration problems, significant simplifications to
15876 Tor's callgraph, and numerous bugfixes and small features.
15878 This is the most tested release of Tor to date. The unit tests cover
15879 39.40% of the code, and the integration tests (accessible with "make
15880 test-full-online", requiring stem and chutney and a network
15881 connection) raise the coverage to 64.49%.
15883 o Major features (security, hidden services):
15884 - Hidden services, if using the EntryNodes option, are required to
15885 use more than one EntryNode, in order to avoid a guard discovery
15886 attack. (This would only affect people who had configured hidden
15887 services and manually specified the EntryNodes option with a
15888 single entry-node. The impact was that it would be easy to
15889 remotely identify the guard node used by such a hidden service.
15890 See ticket for more information.) Fixes ticket 14917.
15892 o Major features (Ed25519 keys, keypinning):
15893 - The key-pinning option on directory authorities is now advisory-
15894 only by default. In a future version, or when the AuthDirPinKeys
15895 option is set, pins are enforced again. Disabling key-pinning
15896 seemed like a good idea so that we can survive the fallout of any
15897 usability problems associated with Ed25519 keys. Closes
15900 o Major features (Ed25519 performance):
15901 - Improve the speed of Ed25519 operations and Curve25519 keypair
15902 generation when built targeting 32 bit x86 platforms with SSE2
15903 available. Implements ticket 16535.
15904 - Improve the runtime speed of Ed25519 signature verification by
15905 using Ed25519-donna's batch verification support. Implements
15908 o Major features (performance testing):
15909 - The test-network.sh script now supports performance testing.
15910 Requires corresponding chutney performance testing changes. Patch
15911 by "teor". Closes ticket 14175.
15913 o Major features (relay, Ed25519):
15914 - Significant usability improvements for Ed25519 key management. Log
15915 messages are better, and the code can recover from far more
15916 failure conditions. Thanks to "s7r" for reporting and diagnosing
15918 - Add a new OfflineMasterKey option to tell Tor never to try loading
15919 or generating a secret Ed25519 identity key. You can use this in
15920 combination with tor --keygen to manage offline and/or encrypted
15921 Ed25519 keys. Implements ticket 16944.
15922 - Add a --newpass option to allow changing or removing the
15923 passphrase of an encrypted key with tor --keygen. Implements part
15925 - On receiving a HUP signal, check to see whether the Ed25519
15926 signing key has changed, and reload it if so. Closes ticket 16790.
15928 o Major bugfixes (relay, Ed25519):
15929 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
15930 0.2.7.2-alpha. Reported by "s7r".
15931 - Improve handling of expired signing keys with offline master keys.
15932 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
15934 o Minor features (client-side privacy):
15935 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
15936 lifespan when IsolateSOCKSAuth and streams with SOCKS
15937 authentication are attached to the circuit. This allows
15938 applications like TorBrowser to manage circuit lifetime on their
15939 own. Implements feature 15482.
15940 - When logging malformed hostnames from SOCKS5 requests, respect
15941 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
15943 o Minor features (compilation):
15944 - Give a warning as early as possible when trying to build with an
15945 unsupported OpenSSL version. Closes ticket 16901.
15946 - Fail during configure if we're trying to build against an OpenSSL
15947 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
15948 which started requiring ECC.
15950 o Minor features (geoip):
15951 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
15954 o Minor features (hidden services):
15955 - Relays need to have the Fast flag to get the HSDir flag. As this
15956 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
15957 drop. This change should make some attacks against the hidden
15958 service directory system harder. Fixes ticket 15963.
15959 - Turn on hidden service statistics collection by setting the torrc
15960 option HiddenServiceStatistics to "1" by default. (This keeps
15961 track only of the fraction of traffic used by hidden services, and
15962 the total number of hidden services in existence.) Closes
15964 - Client now uses an introduction point failure cache to know when
15965 to fetch or keep a descriptor in their cache. Previously, failures
15966 were recorded implicitly, but not explicitly remembered. Closes
15969 o Minor features (testing, authorities, documentation):
15970 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
15971 explicitly manage consensus flags in testing networks. Patch by
15972 "robgjansen", modified by "teor". Implements part of ticket 14882.
15974 o Minor bugfixes (security, exit policies):
15975 - ExitPolicyRejectPrivate now also rejects the relay's published
15976 IPv6 address (if any), and any publicly routable IPv4 or IPv6
15977 addresses on any local interfaces. ticket 17027. Patch by "teor".
15978 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
15980 o Minor bug fixes (torrc exit policies):
15981 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
15982 produce IPv6 wildcard addresses. Previously they would produce
15983 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
15984 of bug 16069; bugfix on 0.2.4.7-alpha.
15985 - When parsing torrc ExitPolicies, we now warn for a number of cases
15986 where the user's intent is likely to differ from Tor's actual
15987 behavior. These include: using an IPv4 address with an accept6 or
15988 reject6 line; using "private" on an accept6 or reject6 line; and
15989 including any ExitPolicy lines after accept *:* or reject *:*.
15990 Related to ticket 16069.
15991 - When parsing torrc ExitPolicies, we now issue an info-level
15992 message when expanding an "accept/reject *" line to include both
15993 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
15994 - In each instance above, usage advice is provided to avoid the
15995 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
15996 16069; bugfix on 0.2.4.7-alpha.
15998 o Minor bugfixes (authority):
15999 - Don't assign "HSDir" to a router if it isn't Valid and Running.
16000 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
16001 - Downgrade log messages about Ed25519 key issues if they are in old
16002 cached router descriptors. Fixes part of bug 16286; bugfix
16004 - When we find an Ed25519 key issue in a cached descriptor, stop
16005 saying the descriptor was just "uploaded". Fixes another part of
16006 bug 16286; bugfix on 0.2.7.2-alpha.
16008 o Minor bugfixes (control port):
16009 - Repair a warning and a spurious result when getting the maximum
16010 number of file descriptors from the controller. Fixes bug 16697;
16011 bugfix on 0.2.7.2-alpha.
16013 o Minor bugfixes (correctness):
16014 - When calling channel_free_list(), avoid calling smartlist_remove()
16015 while inside a FOREACH loop. This partially reverts commit
16016 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
16017 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
16019 o Minor bugfixes (documentation):
16020 - Advise users on how to configure separate IPv4 and IPv6 exit
16021 policies in the manpage and sample torrcs. Related to ticket 16069.
16022 - Fix the usage message of tor-resolve(1) so that it no longer lists
16023 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
16024 - Fix an error in the manual page and comments for
16025 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
16026 required "ORPort connectivity". While this is true, it is in no
16027 way unique to the HSDir flag. Of all the flags, only HSDirs need a
16028 DirPort configured in order for the authorities to assign that
16029 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
16032 o Minor bugfixes (Ed25519):
16033 - Fix a memory leak when reading router descriptors with expired
16034 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
16036 o Minor bugfixes (linux seccomp2 sandbox):
16037 - Allow bridge authorities to run correctly under the seccomp2
16038 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
16039 - Allow routers with ed25519 keys to run correctly under the
16040 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
16042 o Minor bugfixes (open file limit):
16043 - Fix set_max_file_descriptors() to set by default the max open file
16044 limit to the current limit when setrlimit() fails. Fixes bug
16045 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
16047 o Minor bugfixes (portability):
16048 - Try harder to normalize the exit status of the Tor process to the
16049 standard-provided range. Fixes bug 16975; bugfix on every version
16051 - Check correctly for Windows socket errors in the workqueue
16052 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
16053 - Fix the behavior of crypto_rand_time_range() when told to consider
16054 times before 1970. (These times were possible when running in a
16055 simulated network environment where time()'s output starts at
16056 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
16057 - Restore correct operation of TLS client-cipher detection on
16058 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
16060 o Minor bugfixes (relay):
16061 - Ensure that worker threads actually exit when a fatal error or
16062 shutdown is indicated. This fix doesn't currently affect the
16063 behavior of Tor, because Tor workers never indicates fatal error
16064 or shutdown except in the unit tests. Fixes bug 16868; bugfix
16066 - Unblock threads before releasing the work queue mutex to ensure
16067 predictable scheduling behavior. Fixes bug 16644; bugfix
16070 o Code simplification and refactoring:
16071 - Change the function that's called when we need to retry all
16072 downloads so that it only reschedules the downloads to happen
16073 immediately, rather than launching them all at once itself. This
16074 further simplifies Tor's callgraph.
16075 - Move some format-parsing functions out of crypto.c and
16076 crypto_curve25519.c into crypto_format.c and/or util_format.c.
16077 - Move the client-only parts of init_keys() into a separate
16078 function. Closes ticket 16763.
16079 - Simplify the microdesc_free() implementation so that it no longer
16080 appears (to code analysis tools) to potentially invoke a huge
16081 suite of other microdesc functions.
16082 - Simply the control graph further by deferring the inner body of
16083 directory_all_unreachable() into a callback. Closes ticket 16762.
16084 - Treat the loss of an owning controller as equivalent to a SIGTERM
16085 signal. This removes a tiny amount of duplicated code, and
16086 simplifies our callgraph. Closes ticket 16788.
16087 - When generating an event to send to the controller, we no longer
16088 put the event over the network immediately. Instead, we queue
16089 these events, and use a Libevent callback to deliver them. This
16090 change simplifies Tor's callgraph by reducing the number of
16091 functions from which all other Tor functions are reachable. Closes
16093 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
16094 that try to scan or compile every file on Unix won't decide that
16096 - Remove the unused "nulterminate" argument from buf_pullup().
16099 - Recommend a 40 GB example AccountingMax in torrc.sample rather
16100 than a 4 GB max. Closes ticket 16742.
16101 - Include the TUNING document in our source tarball. It is referred
16102 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
16106 - The internal pure-C tor-fw-helper tool is now removed from the Tor
16107 distribution, in favor of the pure-Go clone available from
16108 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
16109 used by the C tor-fw-helper are not, in our opinion, very
16110 confidence- inspiring in their secure-programming techniques.
16111 Closes ticket 13338.
16112 - Remove the code that would try to aggressively flush controller
16113 connections while writing to them. This code was introduced in
16114 0.1.2.7-alpha, in order to keep output buffers from exceeding
16115 their limits. But there is no longer a maximum output buffer size,
16116 and flushing data in this way caused some undesirable recursions
16117 in our call graph. Closes ticket 16480.
16120 - Make "bridges+hs" the default test network. This tests almost all
16121 tor functionality during make test-network, while allowing tests
16122 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
16123 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
16124 (chutney). Patches by "teor".
16125 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
16126 by-side in the same parent directory. Closes ticket 16903. Patch
16128 - Use environment variables rather than autoconf substitutions to
16129 send variables from the build system to the test scripts. This
16130 change should be easier to maintain, and cause 'make distcheck' to
16131 work better than before. Fixes bug 17148.
16132 - Add a new set of callgraph analysis scripts that use clang to
16133 produce a list of which Tor functions are reachable from which
16134 other Tor functions. We're planning to use these to help simplify
16135 our code structure by identifying illogical dependencies.
16136 - Add new 'test-full' and 'test-full-online' targets to run all
16137 tests, including integration tests with stem and chutney.
16138 - Make the test-workqueue test work on Windows by initializing the
16139 network before we begin.
16140 - New make target (make test-network-all) to run multiple applicable
16141 chutney test cases. Patch from Teor; closes 16953.
16142 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
16143 functions in dns.c. Implements a portion of ticket 16831.
16144 - When building Tor with testing coverage enabled, run Chutney tests
16145 (if any) using the 'tor-cov' coverage binary.
16146 - When running test-network or test-stem, check for the absence of
16147 stem/chutney before doing any build operations.
16150 Changes in version 0.2.7.2-alpha - 2015-07-27
16151 This, the second alpha in the Tor 0.2.7 series, has a number of new
16152 features, including a way to manually pick the number of introduction
16153 points for hidden services, and the much stronger Ed25519 signing key
16154 algorithm for regular Tor relays (including support for encrypted
16155 offline identity keys in the new algorithm).
16157 Support for Ed25519 on relays is currently limited to signing router
16158 descriptors; later alphas in this series will extend Ed25519 key
16159 support to more parts of the Tor protocol.
16161 o Major features (Ed25519 identity keys, Proposal 220):
16162 - All relays now maintain a stronger identity key, using the Ed25519
16163 elliptic curve signature format. This master key is designed so
16164 that it can be kept offline. Relays also generate an online
16165 signing key, and a set of other Ed25519 keys and certificates.
16166 These are all automatically regenerated and rotated as needed.
16167 Implements part of ticket 12498.
16168 - Directory authorities now vote on Ed25519 identity keys along with
16169 RSA1024 keys. Implements part of ticket 12498.
16170 - Directory authorities track which Ed25519 identity keys have been
16171 used with which RSA1024 identity keys, and do not allow them to
16172 vary freely. Implements part of ticket 12498.
16173 - Microdescriptors now include Ed25519 identity keys. Implements
16174 part of ticket 12498.
16175 - Add support for offline encrypted Ed25519 master keys. To use this
16176 feature on your tor relay, run "tor --keygen" to make a new master
16177 key (or to make a new signing key if you already have a master
16178 key). Closes ticket 13642.
16180 o Major features (Hidden services):
16181 - Add the torrc option HiddenServiceNumIntroductionPoints, to
16182 specify a fixed number of introduction points. Its maximum value
16183 is 10 and default is 3. Using this option can increase a hidden
16184 service's reliability under load, at the cost of making it more
16185 visible that the hidden service is facing extra load. Closes
16187 - Remove the adaptive algorithm for choosing the number of
16188 introduction points, which used to change the number of
16189 introduction points (poorly) depending on the number of
16190 connections the HS sees. Closes ticket 4862.
16192 o Major features (onion key cross-certification):
16193 - Relay descriptors now include signatures of their own identity
16194 keys, made using the TAP and ntor onion keys. These signatures
16195 allow relays to prove ownership of their own onion keys. Because
16196 of this change, microdescriptors will no longer need to include
16197 RSA identity keys. Implements proposal 228; closes ticket 12499.
16199 o Major features (performance):
16200 - Improve the runtime speed of Ed25519 operations by using the
16201 public-domain Ed25519-donna by Andrew M. ("floodyberry").
16202 Implements ticket 16467.
16203 - Improve the runtime speed of the ntor handshake by using an
16204 optimized curve25519 basepoint scalarmult implementation from the
16205 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
16206 ideas by Adam Langley. Implements ticket 9663.
16208 o Major bugfixes (client-side privacy, also in 0.2.6.9):
16209 - Properly separate out each SOCKSPort when applying stream
16210 isolation. The error occurred because each port's session group
16211 was being overwritten by a default value when the listener
16212 connection was initialized. Fixes bug 16247; bugfix on
16213 0.2.6.3-alpha. Patch by "jojelino".
16215 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
16216 - Stop refusing to store updated hidden service descriptors on a
16217 client. This reverts commit 9407040c59218 (which indeed fixed bug
16218 14219, but introduced a major hidden service reachability
16219 regression detailed in bug 16381). This is a temporary fix since
16220 we can live with the minor issue in bug 14219 (it just results in
16221 some load on the network) but the regression of 16381 is too much
16222 of a setback. First-round fix for bug 16381; bugfix
16225 o Major bugfixes (hidden services):
16226 - When cannibalizing a circuit for an introduction point, always
16227 extend to the chosen exit node (creating a 4 hop circuit).
16228 Previously Tor would use the current circuit exit node, which
16229 changed the original choice of introduction point, and could cause
16230 the hidden service to skip excluded introduction points or
16231 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
16234 o Major bugfixes (open file limit):
16235 - The open file limit wasn't checked before calling
16236 tor_accept_socket_nonblocking(), which would make Tor exceed the
16237 limit. Now, before opening a new socket, Tor validates the open
16238 file limit just before, and if the max has been reached, return an
16239 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
16241 o Major bugfixes (stability, also in 0.2.6.10):
16242 - Stop crashing with an assertion failure when parsing certain kinds
16243 of malformed or truncated microdescriptors. Fixes bug 16400;
16244 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16245 by "cypherpunks_backup".
16246 - Stop random client-side assertion failures that could occur when
16247 connecting to a busy hidden service, or connecting to a hidden
16248 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16251 o Minor features (directory authorities, security, also in 0.2.6.9):
16252 - The HSDir flag given by authorities now requires the Stable flag.
16253 For the current network, this results in going from 2887 to 2806
16254 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16255 attack by raising the effort for a relay to become Stable to
16256 require at the very least 7 days, while maintaining the 96 hours
16257 uptime requirement for HSDir. Implements ticket 8243.
16259 o Minor features (client):
16260 - Relax the validation of hostnames in SOCKS5 requests, allowing the
16261 character '_' to appear, in order to cope with domains observed in
16262 the wild that are serving non-RFC compliant records. Resolves
16264 - Relax the validation done to hostnames in SOCKS5 requests, and
16265 allow a single trailing '.' to cope with clients that pass FQDNs
16266 using that syntax to explicitly indicate that the domain name is
16267 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
16268 - Add GroupWritable and WorldWritable options to unix-socket based
16269 SocksPort and ControlPort options. These options apply to a single
16270 socket, and override {Control,Socks}SocketsGroupWritable. Closes
16273 o Minor features (control protocol):
16274 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
16275 the control protocol. Resolves ticket 15358.
16277 o Minor features (directory authorities):
16278 - Directory authorities no longer vote against the "Fast", "Stable",
16279 and "HSDir" flags just because they were going to vote against
16280 "Running": if the consensus turns out to be that the router was
16281 running, then the authority's vote should count. Patch from Peter
16282 Retzlaff; closes issue 8712.
16284 o Minor features (geoip, also in 0.2.6.10):
16285 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16286 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16288 o Minor features (hidden services):
16289 - Add the new options "HiddenServiceMaxStreams" and
16290 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
16291 limit the maximum number of simultaneous streams per circuit, and
16292 optionally tear down the circuit when the limit is exceeded. Part
16295 o Minor features (portability):
16296 - Use C99 variadic macros when the compiler is not GCC. This avoids
16297 failing compilations on MSVC, and fixes a log-file-based race
16298 condition in our old workarounds. Original patch from Gisle Vanem.
16300 o Minor bugfixes (compilation, also in 0.2.6.9):
16301 - Build with --enable-systemd correctly when libsystemd is
16302 installed, but systemd is not. Fixes bug 16164; bugfix on
16303 0.2.6.3-alpha. Patch from Peter Palfrader.
16305 o Minor bugfixes (controller):
16306 - Add the descriptor ID in each HS_DESC control event. It was
16307 missing, but specified in control-spec.txt. Fixes bug 15881;
16308 bugfix on 0.2.5.2-alpha.
16310 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
16311 - Check for failures from crypto_early_init, and refuse to continue.
16312 A previous typo meant that we could keep going with an
16313 uninitialized crypto library, and would have OpenSSL initialize
16314 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16315 when implementing ticket 4900. Patch by "teor".
16317 o Minor bugfixes (hidden services):
16318 - Fix a crash when reloading configuration while at least one
16319 configured and one ephemeral hidden service exists. Fixes bug
16320 16060; bugfix on 0.2.7.1-alpha.
16321 - Avoid crashing with a double-free bug when we create an ephemeral
16322 hidden service but adding it fails for some reason. Fixes bug
16323 16228; bugfix on 0.2.7.1-alpha.
16325 o Minor bugfixes (Linux seccomp2 sandbox):
16326 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
16327 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
16329 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
16330 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16331 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16332 on 0.2.6.3-alpha. Patch from "teor".
16334 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
16335 - Fix sandboxing to work when running as a relay, by allowing the
16336 renaming of secret_id_key, and allowing the eventfd2 and futex
16337 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
16339 - Allow systemd connections to work with the Linux seccomp2 sandbox
16340 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16343 o Minor bugfixes (relay):
16344 - Fix a rarely-encountered memory leak when failing to initialize
16345 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
16346 from "cypherpunks".
16348 o Minor bugfixes (systemd):
16349 - Fix an accidental formatting error that broke the systemd
16350 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
16351 - Tor's systemd unit file no longer contains extraneous spaces.
16352 These spaces would sometimes confuse tools like deb-systemd-
16353 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
16355 o Minor bugfixes (tests):
16356 - Use the configured Python executable when running test-stem-full.
16357 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
16359 o Minor bugfixes (tests, also in 0.2.6.9):
16360 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16361 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16363 o Minor bugfixes (threads, comments):
16364 - Always initialize return value in compute_desc_id in rendcommon.c
16365 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16366 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
16367 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16368 - Remove undefined directive-in-macro in test_util_writepid clang
16369 3.7 complains that using a preprocessor directive inside a macro
16370 invocation in test_util_writepid in test_util.c is undefined.
16371 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16373 o Code simplification and refactoring:
16374 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
16375 to ensure they remain consistent and visible everywhere.
16376 - Remove some vestigial workarounds for the MSVC6 compiler. We
16377 haven't supported that in ages.
16378 - The link authentication code has been refactored for better
16379 testability and reliability. It now uses code generated with the
16380 "trunnel" binary encoding generator, to reduce the risk of bugs
16381 due to programmer error. Done as part of ticket 12498.
16384 - Include a specific and (hopefully) accurate documentation of the
16385 torrc file's meta-format in doc/torrc_format.txt. This is mainly
16386 of interest to people writing programs to parse or generate torrc
16387 files. This document is not a commitment to long-term
16388 compatibility; some aspects of the current format are a bit
16389 ridiculous. Closes ticket 2325.
16391 o Removed features:
16392 - Tor no longer supports copies of OpenSSL that are missing support
16393 for Elliptic Curve Cryptography. (We began using ECC when
16394 available in 0.2.4.8-alpha, for more safe and efficient key
16395 negotiation.) In particular, support for at least one of P256 or
16396 P224 is now required, with manual configuration needed if only
16397 P224 is available. Resolves ticket 16140.
16398 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
16399 on an operating system that has not upgraded to OpenSSL 1.0 or
16400 later, and you compile Tor from source, you will need to install a
16401 more recent OpenSSL to link Tor against.) These versions of
16402 OpenSSL are still supported by the OpenSSL, but the numerous
16403 cryptographic improvements in later OpenSSL releases makes them a
16404 clear choice. Resolves ticket 16034.
16405 - Remove the HidServDirectoryV2 option. Now all relays offer to
16406 store hidden service descriptors. Related to 16543.
16407 - Remove the VoteOnHidServDirectoriesV2 option, since all
16408 authorities have long set it to 1. Closes ticket 16543.
16411 - Document use of coverity, clang static analyzer, and clang dynamic
16412 undefined behavior and address sanitizers in doc/HACKING. Include
16413 detailed usage instructions in the blacklist. Patch by "teor".
16414 Closes ticket 15817.
16415 - The link authentication protocol code now has extensive tests.
16416 - The relay descriptor signature testing code now has
16418 - The test_workqueue program now runs faster, and is enabled by
16419 default as a part of "make check".
16420 - Now that OpenSSL has its own scrypt implementation, add an unit
16421 test that checks for interoperability between libscrypt_scrypt()
16422 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
16423 and rely on EVP_PBE_scrypt() whenever possible. Resolves
16427 Changes in version 0.2.6.10 - 2015-07-12
16428 Tor version 0.2.6.10 fixes some significant stability and hidden
16429 service client bugs, bulletproofs the cryptography init process, and
16430 fixes a bug when using the sandbox code with some older versions of
16431 Linux. Everyone running an older version, especially an older version
16432 of 0.2.6, should upgrade.
16434 o Major bugfixes (hidden service clients, stability):
16435 - Stop refusing to store updated hidden service descriptors on a
16436 client. This reverts commit 9407040c59218 (which indeed fixed bug
16437 14219, but introduced a major hidden service reachability
16438 regression detailed in bug 16381). This is a temporary fix since
16439 we can live with the minor issue in bug 14219 (it just results in
16440 some load on the network) but the regression of 16381 is too much
16441 of a setback. First-round fix for bug 16381; bugfix
16444 o Major bugfixes (stability):
16445 - Stop crashing with an assertion failure when parsing certain kinds
16446 of malformed or truncated microdescriptors. Fixes bug 16400;
16447 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16448 by "cypherpunks_backup".
16449 - Stop random client-side assertion failures that could occur when
16450 connecting to a busy hidden service, or connecting to a hidden
16451 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16454 o Minor features (geoip):
16455 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16456 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16458 o Minor bugfixes (crypto error-handling):
16459 - Check for failures from crypto_early_init, and refuse to continue.
16460 A previous typo meant that we could keep going with an
16461 uninitialized crypto library, and would have OpenSSL initialize
16462 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16463 when implementing ticket 4900. Patch by "teor".
16465 o Minor bugfixes (Linux seccomp2 sandbox):
16466 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16467 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16468 on 0.2.6.3-alpha. Patch from "teor".
16471 Changes in version 0.2.6.9 - 2015-06-11
16472 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
16473 requirements for receiving an HSDir flag, and addresses some other small
16474 bugs in the systemd and sandbox code. Clients using circuit isolation
16475 should upgrade; all directory authorities should upgrade.
16477 o Major bugfixes (client-side privacy):
16478 - Properly separate out each SOCKSPort when applying stream
16479 isolation. The error occurred because each port's session group was
16480 being overwritten by a default value when the listener connection
16481 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
16484 o Minor feature (directory authorities, security):
16485 - The HSDir flag given by authorities now requires the Stable flag.
16486 For the current network, this results in going from 2887 to 2806
16487 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16488 attack by raising the effort for a relay to become Stable which
16489 takes at the very least 7 days to do so and by keeping the 96
16490 hours uptime requirement for HSDir. Implements ticket 8243.
16492 o Minor bugfixes (compilation):
16493 - Build with --enable-systemd correctly when libsystemd is
16494 installed, but systemd is not. Fixes bug 16164; bugfix on
16495 0.2.6.3-alpha. Patch from Peter Palfrader.
16497 o Minor bugfixes (Linux seccomp2 sandbox):
16498 - Fix sandboxing to work when running as a relaymby renaming of
16499 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
16500 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
16501 - Allow systemd connections to work with the Linux seccomp2 sandbox
16502 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16505 o Minor bugfixes (tests):
16506 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16507 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16510 Changes in version 0.2.6.8 - 2015-05-21
16511 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
16512 fixes an authority-side bug in assigning the HSDir flag. All directory
16513 authorities should upgrade.
16515 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
16516 - Revert commit that made directory authorities assign the HSDir
16517 flag to relays without a DirPort; this was bad because such relays
16518 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16521 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
16522 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16523 a client authorized hidden service. Fixes bug 15823; bugfix
16526 o Minor features (geoip):
16527 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16528 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16532 Changes in version 0.2.7.1-alpha - 2015-05-12
16533 Tor 0.2.7.1-alpha is the first alpha release in its series. It
16534 includes numerous small features and bugfixes against previous Tor
16535 versions, and numerous small infrastructure improvements. The most
16536 notable features are several new ways for controllers to interact with
16537 the hidden services subsystem.
16539 o New system requirements:
16540 - Tor no longer includes workarounds to support Libevent versions
16541 before 1.3e. Libevent 2.0 or later is recommended. Closes
16544 o Major features (controller):
16545 - Add the ADD_ONION and DEL_ONION commands that allow the creation
16546 and management of hidden services via the controller. Closes
16548 - New "GETINFO onions/current" and "GETINFO onions/detached"
16549 commands to get information about hidden services created via the
16550 controller. Part of ticket 6411.
16551 - New HSFETCH command to launch a request for a hidden service
16552 descriptor. Closes ticket 14847.
16553 - New HSPOST command to upload a hidden service descriptor. Closes
16554 ticket 3523. Patch by "DonnchaC".
16556 o Major bugfixes (hidden services):
16557 - Revert commit that made directory authorities assign the HSDir
16558 flag to relays without a DirPort; this was bad because such relays
16559 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16562 o Minor features (clock-jump tolerance):
16563 - Recover better when our clock jumps back many hours, like might
16564 happen for Tails or Whonix users who start with a very wrong
16565 hardware clock, use Tor to discover a more accurate time, and then
16566 fix their clock. Resolves part of ticket 8766.
16568 o Minor features (command-line interface):
16569 - Make --hash-password imply --hush to prevent unnecessary noise.
16570 Closes ticket 15542. Patch from "cypherpunks".
16571 - Print a warning whenever we find a relative file path being used
16572 as torrc option. Resolves issue 14018.
16574 o Minor features (controller):
16575 - Add DirAuthority lines for default directory authorities to the
16576 output of the "GETINFO config/defaults" command if not already
16577 present. Implements ticket 14840.
16578 - Controllers can now use "GETINFO hs/client/desc/id/..." to
16579 retrieve items from the client's hidden service descriptor cache.
16580 Closes ticket 14845.
16581 - Implement a new controller command "GETINFO status/fresh-relay-
16582 descs" to fetch a descriptor/extrainfo pair that was generated on
16583 demand just for the controller's use. Implements ticket 14784.
16585 o Minor features (DoS-resistance):
16586 - Make it harder for attackers to overload hidden services with
16587 introductions, by blocking multiple introduction requests on the
16588 same circuit. Resolves ticket 15515.
16590 o Minor features (geoip):
16591 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16592 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16595 o Minor features (HS popularity countermeasure):
16596 - To avoid leaking HS popularity, don't cycle the introduction point
16597 when we've handled a fixed number of INTRODUCE2 cells but instead
16598 cycle it when a random number of introductions is reached, thus
16599 making it more difficult for an attacker to find out the amount of
16600 clients that have used the introduction point for a specific HS.
16601 Closes ticket 15745.
16603 o Minor features (logging):
16604 - Include the Tor version in all LD_BUG log messages, since people
16605 tend to cut and paste those into the bugtracker. Implements
16608 o Minor features (pluggable transports):
16609 - When launching managed pluggable transports on Linux systems,
16610 attempt to have the kernel deliver a SIGTERM on tor exit if the
16611 pluggable transport process is still running. Resolves
16613 - When launching managed pluggable transports, setup a valid open
16614 stdin in the child process that can be used to detect if tor has
16615 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
16616 can be used by implementations to detect this new behavior.
16617 Resolves ticket 15435.
16619 o Minor features (testing):
16620 - Add a test to verify that the compiler does not eliminate our
16621 memwipe() implementation. Closes ticket 15377.
16622 - Add make rule `check-changes` to verify the format of changes
16623 files. Closes ticket 15180.
16624 - Add unit tests for control_event_is_interesting(). Add a compile-
16625 time check that the number of events doesn't exceed the capacity
16626 of control_event_t.event_mask. Closes ticket 15431, checks for
16627 bugs similar to 13085. Patch by "teor".
16628 - Command-line argument tests moved to Stem. Resolves ticket 14806.
16629 - Integrate the ntor, backtrace, and zero-length keys tests into the
16630 automake test suite. Closes ticket 15344.
16631 - Remove assertions during builds to determine Tor's test coverage.
16632 We don't want to trigger these even in assertions, so including
16633 them artificially makes our branch coverage look worse than it is.
16634 This patch provides the new test-stem-full and coverage-html-full
16635 configure options. Implements ticket 15400.
16637 o Minor bugfixes (build):
16638 - Improve out-of-tree builds by making non-standard rules work and
16639 clean up additional files and directories. Fixes bug 15053; bugfix
16642 o Minor bugfixes (command-line interface):
16643 - When "--quiet" is provided along with "--validate-config", do not
16644 write anything to stdout on success. Fixes bug 14994; bugfix
16646 - When complaining about bad arguments to "--dump-config", use
16647 stderr, not stdout.
16649 o Minor bugfixes (configuration, unit tests):
16650 - Only add the default fallback directories when the DirAuthorities,
16651 AlternateDirAuthority, and FallbackDir directory config options
16652 are set to their defaults. The default fallback directory list is
16653 currently empty, this fix will only change tor's behavior when it
16654 has default fallback directories. Includes unit tests for
16655 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
16656 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
16658 o Minor bugfixes (correctness):
16659 - For correctness, avoid modifying a constant string in
16660 handle_control_postdescriptor. Fixes bug 15546; bugfix
16662 - Remove side-effects from tor_assert() calls. This was harmless,
16663 because we never disable assertions, but it is bad style and
16664 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
16667 o Minor bugfixes (hidden service):
16668 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16669 a client authorized hidden service. Fixes bug 15823; bugfix
16671 - Remove an extraneous newline character from the end of hidden
16672 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
16674 o Minor bugfixes (interface):
16675 - Print usage information for --dump-config when it is used without
16676 an argument. Also, fix the error message to use different wording
16677 and add newline at the end. Fixes bug 15541; bugfix
16680 o Minor bugfixes (logs):
16681 - When building Tor under Clang, do not include an extra set of
16682 parentheses in log messages that include function names. Fixes bug
16683 15269; bugfix on every released version of Tor when compiled with
16684 recent enough Clang.
16686 o Minor bugfixes (network):
16687 - When attempting to use fallback technique for network interface
16688 lookup, disregard loopback and multicast addresses since they are
16689 unsuitable for public communications.
16691 o Minor bugfixes (statistics):
16692 - Disregard the ConnDirectionStatistics torrc options when Tor is
16693 not a relay since in that mode of operation no sensible data is
16694 being collected and because Tor might run into measurement hiccups
16695 when running as a client for some time, then becoming a relay.
16696 Fixes bug 15604; bugfix on 0.2.2.35.
16698 o Minor bugfixes (test networks):
16699 - When self-testing reachability, use ExtendAllowPrivateAddresses to
16700 determine if local/private addresses imply reachability. The
16701 previous fix used TestingTorNetwork, which implies
16702 ExtendAllowPrivateAddresses, but this excluded rare configurations
16703 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
16704 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
16705 issue discovered by CJ Ess.
16707 o Minor bugfixes (testing):
16708 - Check for matching value in server response in ntor_ref.py. Fixes
16709 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
16711 - Set the severity correctly when testing
16712 get_interface_addresses_ifaddrs() and
16713 get_interface_addresses_win32(), so that the tests fail gracefully
16714 instead of triggering an assertion. Fixes bug 15759; bugfix on
16715 0.2.6.3-alpha. Reported by Nicolas Derive.
16717 o Code simplification and refactoring:
16718 - Move the hacky fallback code out of get_interface_address6() into
16719 separate function and get it covered with unit-tests. Resolves
16721 - Refactor hidden service client-side cache lookup to intelligently
16722 report its various failure cases, and disentangle failure cases
16723 involving a lack of introduction points. Closes ticket 14391.
16724 - Use our own Base64 encoder instead of OpenSSL's, to allow more
16725 control over the output. Part of ticket 15652.
16728 - Improve the descriptions of statistics-related torrc options in
16729 the manpage to describe rationale and possible uses cases. Fixes
16731 - Improve the layout and formatting of ./configure --help messages.
16732 Closes ticket 15024. Patch from "cypherpunks".
16733 - Standardize on the term "server descriptor" in the manual page.
16734 Previously, we had used "router descriptor", "server descriptor",
16735 and "relay descriptor" interchangeably. Part of ticket 14987.
16738 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
16739 and always use the internal Base64 decoder. The internal decoder
16740 has been part of tor since 0.2.0.10-alpha, and no one should
16741 be using the OpenSSL one. Part of ticket 15652.
16742 - Remove the 'tor_strclear()' function; use memwipe() instead.
16743 Closes ticket 14922.
16745 o Removed features:
16746 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
16747 fingerprinting we now recommend pluggable transports; for forward-
16748 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
16749 - Remove the undocumented "--digests" command-line option. It
16750 complicated our build process, caused subtle build issues on
16751 multiple platforms, and is now redundant since we started
16752 including git version identifiers. Closes ticket 14742.
16753 - Tor no longer contains checks for ancient directory cache versions
16754 that didn't know about microdescriptors.
16755 - Tor no longer contains workarounds for stat files generated by
16756 super-old versions of Tor that didn't choose guards sensibly.
16759 Changes in version 0.2.4.27 - 2015-04-06
16760 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
16761 could be used by an attacker to crash hidden services, or crash clients
16762 visiting hidden services. Hidden services should upgrade as soon as
16763 possible; clients should upgrade whenever packages become available.
16765 This release also backports a simple improvement to make hidden
16766 services a bit less vulnerable to denial-of-service attacks.
16768 o Major bugfixes (security, hidden service):
16769 - Fix an issue that would allow a malicious client to trigger an
16770 assertion failure and halt a hidden service. Fixes bug 15600;
16771 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16772 - Fix a bug that could cause a client to crash with an assertion
16773 failure when parsing a malformed hidden service descriptor. Fixes
16774 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16776 o Minor features (DoS-resistance, hidden service):
16777 - Introduction points no longer allow multiple INTRODUCE1 cells to
16778 arrive on the same circuit. This should make it more expensive for
16779 attackers to overwhelm hidden services with introductions.
16780 Resolves ticket 15515.
16783 Changes in version 0.2.5.12 - 2015-04-06
16784 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
16785 could be used by an attacker to crash hidden services, or crash clients
16786 visiting hidden services. Hidden services should upgrade as soon as
16787 possible; clients should upgrade whenever packages become available.
16789 This release also backports a simple improvement to make hidden
16790 services a bit less vulnerable to denial-of-service attacks.
16792 o Major bugfixes (security, hidden service):
16793 - Fix an issue that would allow a malicious client to trigger an
16794 assertion failure and halt a hidden service. Fixes bug 15600;
16795 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16796 - Fix a bug that could cause a client to crash with an assertion
16797 failure when parsing a malformed hidden service descriptor. Fixes
16798 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16800 o Minor features (DoS-resistance, hidden service):
16801 - Introduction points no longer allow multiple INTRODUCE1 cells to
16802 arrive on the same circuit. This should make it more expensive for
16803 attackers to overwhelm hidden services with introductions.
16804 Resolves ticket 15515.
16807 Changes in version 0.2.6.7 - 2015-04-06
16808 Tor 0.2.6.7 fixes two security issues that could be used by an
16809 attacker to crash hidden services, or crash clients visiting hidden
16810 services. Hidden services should upgrade as soon as possible; clients
16811 should upgrade whenever packages become available.
16813 This release also contains two simple improvements to make hidden
16814 services a bit less vulnerable to denial-of-service attacks.
16816 o Major bugfixes (security, hidden service):
16817 - Fix an issue that would allow a malicious client to trigger an
16818 assertion failure and halt a hidden service. Fixes bug 15600;
16819 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16820 - Fix a bug that could cause a client to crash with an assertion
16821 failure when parsing a malformed hidden service descriptor. Fixes
16822 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16824 o Minor features (DoS-resistance, hidden service):
16825 - Introduction points no longer allow multiple INTRODUCE1 cells to
16826 arrive on the same circuit. This should make it more expensive for
16827 attackers to overwhelm hidden services with introductions.
16828 Resolves ticket 15515.
16829 - Decrease the amount of reattempts that a hidden service performs
16830 when its rendezvous circuits fail. This reduces the computational
16831 cost for running a hidden service under heavy load. Resolves
16835 Changes in version 0.2.6.6 - 2015-03-24
16836 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
16838 It adds numerous safety, security, correctness, and performance
16839 improvements. Client programs can be configured to use more kinds of
16840 sockets, AutomapHosts works better, the multithreading backend is
16841 improved, cell transmission is refactored, test coverage is much
16842 higher, more denial-of-service attacks are handled, guard selection is
16843 improved to handle long-term guards better, pluggable transports
16844 should work a bit better, and some annoying hidden service performance
16845 bugs should be addressed.
16847 o Minor bugfixes (portability):
16848 - Use the correct datatype in the SipHash-2-4 function to prevent
16849 compilers from assuming any sort of alignment. Fixes bug 15436;
16850 bugfix on 0.2.5.3-alpha.
16852 Changes in version 0.2.6.5-rc - 2015-03-18
16853 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
16854 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
16856 o Major bugfixes (client):
16857 - Avoid crashing when making certain configuration option changes on
16858 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
16861 o Major bugfixes (pluggable transports):
16862 - Initialize the extended OR Port authentication cookie before
16863 launching pluggable transports. This prevents a race condition
16864 that occurred when server-side pluggable transports would cache the
16865 authentication cookie before it has been (re)generated. Fixes bug
16866 15240; bugfix on 0.2.5.1-alpha.
16868 o Major bugfixes (portability):
16869 - Do not crash on startup when running on Solaris. Fixes a bug
16870 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
16873 o Minor features (heartbeat):
16874 - On relays, report how many connections we negotiated using each
16875 version of the Tor link protocols. This information will let us
16876 know if removing support for very old versions of the Tor
16877 protocols is harming the network. Closes ticket 15212.
16879 o Code simplification and refactoring:
16880 - Refactor main loop to extract the 'loop' part. This makes it
16881 easier to run Tor under Shadow. Closes ticket 15176.
16884 Changes in version 0.2.5.11 - 2015-03-17
16885 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
16887 It backports several bugfixes from the 0.2.6 branch, including a
16888 couple of medium-level security fixes for relays and exit nodes.
16889 It also updates the list of directory authorities.
16891 o Directory authority changes:
16892 - Remove turtles as a directory authority.
16893 - Add longclaw as a new (v3) directory authority. This implements
16894 ticket 13296. This keeps the directory authority count at 9.
16895 - The directory authority Faravahar has a new IP address. This
16896 closes ticket 14487.
16898 o Major bugfixes (crash, OSX, security):
16899 - Fix a remote denial-of-service opportunity caused by a bug in
16900 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16903 o Major bugfixes (relay, stability, possible security):
16904 - Fix a bug that could lead to a relay crashing with an assertion
16905 failure if a buffer of exactly the wrong layout was passed to
16906 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16907 0.2.0.10-alpha. Patch from 'cypherpunks'.
16908 - Do not assert if the 'data' pointer on a buffer is advanced to the
16909 very end of the buffer; log a BUG message instead. Only assert if
16910 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16912 o Major bugfixes (exit node stability):
16913 - Fix an assertion failure that could occur under high DNS load.
16914 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16915 diagnosed and fixed by "cypherpunks".
16917 o Major bugfixes (Linux seccomp2 sandbox):
16918 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16919 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16920 0.2.5.1-alpha. Patch from "sanic".
16922 o Minor features (controller):
16923 - New "GETINFO bw-event-cache" to get information about recent
16924 bandwidth events. Closes ticket 14128. Useful for controllers to
16925 get recent bandwidth history after the fix for ticket 13988.
16927 o Minor features (geoip):
16928 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16929 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16932 o Minor bugfixes (client, automapping):
16933 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16934 no value follows the option. Fixes bug 14142; bugfix on
16935 0.2.4.7-alpha. Patch by "teor".
16936 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16937 14195; bugfix on 0.1.0.1-rc.
16939 o Minor bugfixes (compilation):
16940 - Build without warnings with the stock OpenSSL srtp.h header, which
16941 has a duplicate declaration of SSL_get_selected_srtp_profile().
16942 Fixes bug 14220; this is OpenSSL's bug, not ours.
16944 o Minor bugfixes (directory authority):
16945 - Allow directory authorities to fetch more data from one another if
16946 they find themselves missing lots of votes. Previously, they had
16947 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16948 bugfix on 0.1.2.5-alpha.
16949 - Enlarge the buffer to read bwauth generated files to avoid an
16950 issue when parsing the file in dirserv_read_measured_bandwidths().
16951 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16953 o Minor bugfixes (statistics):
16954 - Increase period over which bandwidth observations are aggregated
16955 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
16957 o Minor bugfixes (preventative security, C safety):
16958 - When reading a hexadecimal, base-32, or base-64 encoded value from
16959 a string, always overwrite the whole output buffer. This prevents
16960 some bugs where we would look at (but fortunately, not reveal)
16961 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
16965 Changes in version 0.2.4.26 - 2015-03-17
16966 Tor 0.2.4.26 includes an updated list of directory authorities. It
16967 also backports a couple of stability and security bugfixes from 0.2.5
16970 o Directory authority changes:
16971 - Remove turtles as a directory authority.
16972 - Add longclaw as a new (v3) directory authority. This implements
16973 ticket 13296. This keeps the directory authority count at 9.
16974 - The directory authority Faravahar has a new IP address. This
16975 closes ticket 14487.
16977 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
16978 - Fix an assertion failure that could occur under high DNS load.
16979 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16980 diagnosed and fixed by "cypherpunks".
16982 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
16983 - Fix a bug that could lead to a relay crashing with an assertion
16984 failure if a buffer of exactly the wrong layout was passed to
16985 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16986 0.2.0.10-alpha. Patch from 'cypherpunks'.
16987 - Do not assert if the 'data' pointer on a buffer is advanced to the
16988 very end of the buffer; log a BUG message instead. Only assert if
16989 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16991 o Minor features (geoip):
16992 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16993 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16996 Changes in version 0.2.6.4-rc - 2015-03-09
16997 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
16998 attacker might be able to use in order to crash certain Tor
16999 directories. It also resolves some minor issues left over from, or
17000 introduced in, Tor 0.2.6.3-alpha or earlier.
17002 o Major bugfixes (crash, OSX, security):
17003 - Fix a remote denial-of-service opportunity caused by a bug in
17004 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
17007 o Major bugfixes (relay, stability, possible security):
17008 - Fix a bug that could lead to a relay crashing with an assertion
17009 failure if a buffer of exactly the wrong layout is passed to
17010 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17011 0.2.0.10-alpha. Patch from "cypherpunks".
17012 - Do not assert if the 'data' pointer on a buffer is advanced to the
17013 very end of the buffer; log a BUG message instead. Only assert if
17014 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17016 o Major bugfixes (FreeBSD IPFW transparent proxy):
17017 - Fix address detection with FreeBSD transparent proxies, when
17018 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
17021 o Major bugfixes (Linux seccomp2 sandbox):
17022 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
17023 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
17025 - Allow AF_UNIX hidden services to be used with the seccomp2
17026 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
17027 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17028 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17029 0.2.5.1-alpha. Patch from "sanic".
17031 o Minor features (controller):
17032 - Messages about problems in the bootstrap process now include
17033 information about the server we were trying to connect to when we
17034 noticed the problem. Closes ticket 15006.
17036 o Minor features (geoip):
17037 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17038 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17041 o Minor features (logs):
17042 - Quiet some log messages in the heartbeat and at startup. Closes
17045 o Minor bugfixes (certificate handling):
17046 - If an authority operator accidentally makes a signing certificate
17047 with a future publication time, do not discard its real signing
17048 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
17049 - Remove any old authority certificates that have been superseded
17050 for at least two days. Previously, we would keep superseded
17051 certificates until they expired, if they were published close in
17052 time to the certificate that superseded them. Fixes bug 11454;
17053 bugfix on 0.2.1.8-alpha.
17055 o Minor bugfixes (compilation):
17056 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
17058 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
17061 o Minor bugfixes (testing):
17062 - Fix endianness issues in unit test for resolve_my_address() to
17063 have it pass on big endian systems. Fixes bug 14980; bugfix on
17065 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
17066 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
17067 - When running the new 'make test-stem' target, use the configured
17068 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
17069 from "cypherpunks".
17070 - When running the zero-length-keys tests, do not use the default
17071 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
17074 o Directory authority IP change:
17075 - The directory authority Faravahar has a new IP address. This
17076 closes ticket 14487.
17079 - Remove some lingering dead code that once supported mempools.
17080 Mempools were disabled by default in 0.2.5, and removed entirely
17081 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
17085 Changes in version 0.2.6.3-alpha - 2015-02-19
17086 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
17087 the 0.2.6.x series. It introduces support for more kinds of sockets,
17088 makes it harder to accidentally run an exit, improves our
17089 multithreading backend, incorporates several fixes for the
17090 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
17092 If no major regressions or security holes are found in this version,
17093 the next version will be a release candidate.
17095 o Deprecated versions:
17096 - Tor relays older than 0.2.4.18-rc are no longer allowed to
17097 advertise themselves on the network. Closes ticket 13555.
17099 o Major features (security, unix domain sockets):
17100 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
17101 applications can reach Tor without having to create AF_INET or
17102 AF_INET6 sockets, meaning they can completely disable their
17103 ability to make non-Tor network connections. To create a socket of
17104 this type, use "SocksPort unix:/path/to/socket". Implements
17106 - Support mapping hidden service virtual ports to AF_UNIX sockets.
17107 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
17108 Implements ticket 11485.
17110 o Major features (changed defaults):
17111 - Prevent relay operators from unintentionally running exits: When a
17112 relay is configured as an exit node, we now warn the user unless
17113 the "ExitRelay" option is set to 1. We warn even more loudly if
17114 the relay is configured with the default exit policy, since this
17115 can indicate accidental misconfiguration. Setting "ExitRelay 0"
17116 stops Tor from running as an exit relay. Closes ticket 10067.
17118 o Major features (directory system):
17119 - When downloading server- or microdescriptors from a directory
17120 server, we no longer launch multiple simultaneous requests to the
17121 same server. This reduces load on the directory servers,
17122 especially when directory guards are in use. Closes ticket 9969.
17123 - When downloading server- or microdescriptors over a tunneled
17124 connection, do not limit the length of our requests to what the
17125 Squid proxy is willing to handle. Part of ticket 9969.
17126 - Authorities can now vote on the correct digests and latest
17127 versions for different software packages. This allows packages
17128 that include Tor to use the Tor authority system as a way to get
17129 notified of updates and their correct digests. Implements proposal
17130 227. Closes ticket 10395.
17132 o Major features (guards):
17133 - Introduce the Guardfraction feature to improves load balancing on
17134 guard nodes. Specifically, it aims to reduce the traffic gap that
17135 guard nodes experience when they first get the Guard flag. This is
17136 a required step if we want to increase the guard lifetime to 9
17137 months or greater. Closes ticket 9321.
17139 o Major features (performance):
17140 - Make the CPU worker implementation more efficient by avoiding the
17141 kernel and lengthening pipelines. The original implementation used
17142 sockets to transfer data from the main thread to the workers, and
17143 didn't allow any thread to be assigned more than a single piece of
17144 work at once. The new implementation avoids communications
17145 overhead by making requests in shared memory, avoiding kernel IO
17146 where possible, and keeping more requests in flight at once.
17147 Implements ticket 9682.
17149 o Major features (relay):
17150 - Raise the minimum acceptable configured bandwidth rate for bridges
17151 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
17152 20 KiB/sec.) Closes ticket 13822.
17154 o Major bugfixes (exit node stability):
17155 - Fix an assertion failure that could occur under high DNS load.
17156 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17157 diagnosed and fixed by "cypherpunks".
17159 o Major bugfixes (mixed relay-client operation):
17160 - When running as a relay and client at the same time (not
17161 recommended), if we decide not to use a new guard because we want
17162 to retry older guards, only close the locally-originating circuits
17163 passing through that guard. Previously we would close all the
17164 circuits through that guard. Fixes bug 9819; bugfix on
17165 0.2.1.1-alpha. Reported by "skruffy".
17167 o Minor features (build):
17168 - New --disable-system-torrc compile-time option to prevent Tor from
17169 looking for the system-wide torrc or torrc-defaults files.
17170 Resolves ticket 13037.
17172 o Minor features (controller):
17173 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
17174 events so controllers can observe circuit isolation inputs. Closes
17176 - ControlPort now supports the unix:/path/to/socket syntax as an
17177 alternative to the ControlSocket option, for consistency with
17178 SocksPort and HiddenServicePort. Closes ticket 14451.
17179 - New "GETINFO bw-event-cache" to get information about recent
17180 bandwidth events. Closes ticket 14128. Useful for controllers to
17181 get recent bandwidth history after the fix for ticket 13988.
17183 o Minor features (Denial of service resistance):
17184 - Count the total number of bytes used storing hidden service
17185 descriptors against the value of MaxMemInQueues. If we're low on
17186 memory, and more than 20% of our memory is used holding hidden
17187 service descriptors, free them until no more than 10% of our
17188 memory holds hidden service descriptors. Free the least recently
17189 fetched descriptors first. Resolves ticket 13806.
17190 - When we have recently been under memory pressure (over 3/4 of
17191 MaxMemInQueues is allocated), then allocate smaller zlib objects
17192 for small requests. Closes ticket 11791.
17194 o Minor features (geoip):
17195 - Update geoip and geoip6 files to the January 7 2015 Maxmind
17196 GeoLite2 Country database.
17198 o Minor features (guard nodes):
17199 - Reduce the time delay before saving guard status to disk from 10
17200 minutes to 30 seconds (or from one hour to 10 minutes if
17201 AvoidDiskWrites is set). Closes ticket 12485.
17203 o Minor features (hidden service):
17204 - Make Sybil attacks against hidden services harder by changing the
17205 minimum time required to get the HSDir flag from 25 hours up to 96
17206 hours. Addresses ticket 14149.
17207 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
17208 services to disable the anti-scanning feature introduced in
17209 0.2.6.2-alpha. With this option not set, a connection to an
17210 unlisted port closes the circuit. With this option set, only a
17211 RELAY_DONE cell is sent. Closes ticket 14084.
17213 o Minor features (interface):
17214 - Implement "-f -" command-line option to read torrc configuration
17215 from standard input, if you don't want to store the torrc file in
17216 the file system. Implements feature 13865.
17218 o Minor features (logging):
17219 - Add a count of unique clients to the bridge heartbeat message.
17220 Resolves ticket 6852.
17221 - Suppress "router info incompatible with extra info" message when
17222 reading extrainfo documents from cache. (This message got loud
17223 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
17225 - Elevate hidden service authorized-client message from DEBUG to
17226 INFO. Closes ticket 14015.
17228 o Minor features (stability):
17229 - Add assertions in our hash-table iteration code to check for
17230 corrupted values that could cause infinite loops. Closes
17233 o Minor features (systemd):
17234 - Various improvements and modernizations in systemd hardening
17235 support. Closes ticket 13805. Patch from Craig Andrews.
17237 o Minor features (testing networks):
17238 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
17239 and the default on a testing network to 2 minutes. Drop the
17240 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
17241 keep the default on a testing network at 30 seconds. This reduces
17242 HS bootstrap time to around 25 seconds. Also, change the default
17243 time in test-network.sh to match. Closes ticket 13401. Patch
17245 - Create TestingDirAuthVoteHSDir to correspond to
17246 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
17247 HSDir flag for the listed relays regardless of uptime or ORPort
17248 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
17249 Partial implementation for ticket 14067. Patch by "teor".
17251 o Minor features (tor2web mode):
17252 - Introduce the config option Tor2webRendezvousPoints, which allows
17253 clients in Tor2webMode to select a specific Rendezvous Point to be
17254 used in HS circuits. This might allow better performance for
17255 Tor2Web nodes. Implements ticket 12844.
17257 o Minor bugfixes (client DNS):
17258 - Report the correct cached DNS expiration times on SOCKS port or in
17259 DNS replies. Previously, we would report everything as "never
17260 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
17261 - Avoid a small memory leak when we find a cached answer for a
17262 reverse DNS lookup in a client-side DNS cache. (Remember, client-
17263 side DNS caching is off by default, and is not recommended.) Fixes
17264 bug 14259; bugfix on 0.2.0.1-alpha.
17266 o Minor bugfixes (client, automapping):
17267 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17268 no value follows the option. Fixes bug 14142; bugfix on
17269 0.2.4.7-alpha. Patch by "teor".
17270 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17271 14195; bugfix on 0.1.0.1-rc.
17272 - Prevent changes to other options from removing the wildcard value
17273 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
17275 - Allow MapAddress and AutomapHostsOnResolve to work together when
17276 an address is mapped into another address type (like .onion) that
17277 must be automapped at resolve time. Fixes bug 7555; bugfix
17280 o Minor bugfixes (client, bridges):
17281 - When we are using bridges and we had a network connectivity
17282 problem, only retry connecting to our currently configured
17283 bridges, not all bridges we know about and remember using. Fixes
17284 bug 14216; bugfix on 0.2.2.17-alpha.
17286 o Minor bugfixes (client, IPv6):
17287 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
17288 flag is not set; and not because the NoIPv4Traffic flag was set.
17289 Previously we'd looked at the NoIPv4Traffic flag for both types of
17290 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
17292 o Minor bugfixes (compilation):
17293 - The address of an array in the middle of a structure will always
17294 be non-NULL. clang recognises this and complains. Disable the
17295 tautologous and redundant check to silence this warning. Fixes bug
17296 14001; bugfix on 0.2.1.2-alpha.
17297 - Avoid warnings when building with systemd 209 or later. Fixes bug
17298 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
17299 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
17300 Addresses ticket 14188.
17301 - Build without warnings with the stock OpenSSL srtp.h header, which
17302 has a duplicate declaration of SSL_get_selected_srtp_profile().
17303 Fixes bug 14220; this is OpenSSL's bug, not ours.
17304 - Do not compile any code related to Tor2Web mode when Tor2Web mode
17305 is not enabled at compile time. Previously, this code was included
17306 in a disabled state. See discussion on ticket 12844.
17307 - Remove the --disable-threads configure option again. It was
17308 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
17309 14819; bugfix on 0.2.6.2-alpha.
17311 o Minor bugfixes (controller):
17312 - Report "down" in response to the "GETINFO entry-guards" command
17313 when relays are down with an unreachable_since value. Previously,
17314 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
17315 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
17316 14116; bugfix on 0.2.2.9-alpha.
17317 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
17318 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
17320 o Minor bugfixes (directory authority):
17321 - Allow directory authorities to fetch more data from one another if
17322 they find themselves missing lots of votes. Previously, they had
17323 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17324 bugfix on 0.1.2.5-alpha.
17325 - Do not attempt to download extrainfo documents which we will be
17326 unable to validate with a matching server descriptor. Fixes bug
17327 13762; bugfix on 0.2.0.1-alpha.
17328 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
17329 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
17330 - Enlarge the buffer to read bwauth generated files to avoid an
17331 issue when parsing the file in dirserv_read_measured_bandwidths().
17332 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17334 o Minor bugfixes (file handling):
17335 - Stop failing when key files are zero-length. Instead, generate new
17336 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
17337 on all versions of Tor. Patch by "teor".
17338 - Stop generating a fresh .old RSA onion key file when the .old file
17339 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
17340 - Avoid overwriting .old key files with empty key files.
17341 - Skip loading zero-length extrainfo store, router store, stats,
17342 state, and key files.
17343 - Avoid crashing when trying to reload a torrc specified as a
17344 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
17347 o Minor bugfixes (hidden services):
17348 - Close the introduction circuit when we have no more usable intro
17349 points, instead of waiting for it to time out. This also ensures
17350 that no follow-up HS descriptor fetch is triggered when the
17351 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
17352 - When fetching a hidden service descriptor for a down service that
17353 was recently up, do not keep refetching until we try the same
17354 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
17355 - Successfully launch Tor with a nonexistent hidden service
17356 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
17357 14106; bugfix on 0.2.6.2-alpha.
17359 o Minor bugfixes (logging):
17360 - Avoid crashing when there are more log domains than entries in
17361 domain_list. Bugfix on 0.2.3.1-alpha.
17362 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
17364 - Don't log messages to stdout twice when starting up. Fixes bug
17365 13993; bugfix on 0.2.6.1-alpha.
17367 o Minor bugfixes (parsing):
17368 - Stop accepting milliseconds (or other junk) at the end of
17369 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
17370 - Support two-number and three-number version numbers correctly, in
17371 case we change the Tor versioning system in the future. Fixes bug
17372 13661; bugfix on 0.0.8pre1.
17374 o Minor bugfixes (path counting):
17375 - When deciding whether the consensus lists any exit nodes, count
17376 the number listed in the consensus, not the number we have
17377 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
17378 - When deciding whether we have any exit nodes, only examine
17379 ExitNodes when the ExitNodes option is actually set. Fixes part of
17380 bug 14918; bugfix on 0.2.6.2-alpha.
17381 - Get rid of redundant and possibly scary warnings that we are
17382 missing directory information while we bootstrap. Fixes part of
17383 bug 14918; bugfix on 0.2.6.2-alpha.
17385 o Minor bugfixes (portability):
17386 - Fix the ioctl()-based network interface lookup code so that it
17387 will work on systems that have variable-length struct ifreq, for
17389 - Fix scheduler compilation on targets where char is unsigned. Fixes
17390 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
17392 o Minor bugfixes (sandbox):
17393 - Allow glibc fatal errors to be sent to stderr before Tor exits.
17394 Previously, glibc would try to write them to /dev/tty, and the
17395 sandbox would trap the call and make Tor exit prematurely. Fixes
17396 bug 14759; bugfix on 0.2.5.1-alpha.
17398 o Minor bugfixes (shutdown):
17399 - When shutting down, always call event_del() on lingering read or
17400 write events before freeing them. Otherwise, we risk double-frees
17401 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
17404 o Minor bugfixes (small memory leaks):
17405 - Avoid leaking memory when using IPv6 virtual address mappings.
17406 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
17409 o Minor bugfixes (statistics):
17410 - Increase period over which bandwidth observations are aggregated
17411 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17413 o Minor bugfixes (systemd support):
17414 - Fix detection and operation of systemd watchdog. Fixes part of bug
17415 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
17416 - Run correctly under systemd with the RunAsDaemon option set. Fixes
17417 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
17418 - Inform the systemd supervisor about more changes in the Tor
17419 process status. Implements part of ticket 14141. Patch from
17421 - Cause the "--disable-systemd" option to actually disable systemd
17422 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
17425 o Minor bugfixes (TLS):
17426 - Check more thoroughly throughout the TLS code for possible
17427 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
17429 o Minor bugfixes (transparent proxy):
17430 - Use getsockname, not getsockopt, to retrieve the address for a
17431 TPROXY-redirected connection. Fixes bug 13796; bugfix
17434 o Code simplification and refactoring:
17435 - Move fields related to isolating and configuring client ports into
17436 a shared structure. Previously, they were duplicated across
17437 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
17438 to copy them correctly had been the cause of at least one bug in
17439 the past. Closes ticket 8546.
17440 - Refactor the get_interface_addresses_raw() doom-function into
17441 multiple smaller and simpler subfunctions. Cover the resulting
17442 subfunctions with unit-tests. Fixes a significant portion of
17444 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
17445 only for version <= 0.2.2.24 which is now deprecated. Closes
17447 - Remove a test for a long-defunct broken version-one
17451 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
17452 for writing the OpenBSD-specific tips. Resolves ticket 13702.
17453 - Make the tor-resolve documentation match its help string and its
17454 options. Resolves part of ticket 14325.
17455 - Log a more useful error message from tor-resolve when failing to
17456 look up a hidden service address. Resolves part of ticket 14325.
17458 o Downgraded warnings:
17459 - Don't warn when we've attempted to contact a relay using the wrong
17460 ntor onion key. Closes ticket 9635.
17462 o Removed features:
17463 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
17464 longer silently accepted as an alias for "ExitNodes".
17465 - The --enable-mempool and --enable-buf-freelists options, which
17466 were originally created to work around bad malloc implementations,
17467 no longer exist. They were off-by-default in 0.2.5. Closes
17471 - Make the checkdir/perms test complete successfully even if the
17472 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
17473 - Test that tor does not fail when key files are zero-length. Check
17474 that tor generates new keys, and overwrites the empty key files.
17475 - Test that tor generates new keys when keys are missing
17476 (existing behavior).
17477 - Test that tor does not overwrite key files that already contain
17478 data (existing behavior). Tests bug 13111. Patch by "teor".
17479 - New "make test-stem" target to run stem integration tests.
17480 Requires that the "STEM_SOURCE_DIR" environment variable be set.
17481 Closes ticket 14107.
17482 - Make the test_cmdline_args.py script work correctly on Windows.
17483 Patch from Gisle Vanem.
17484 - Move the slower unit tests into a new "./src/test/test-slow"
17485 binary that can be run independently of the other tests. Closes
17487 - Avoid undefined behavior when sampling huge values from the
17488 Laplace distribution. This made unittests fail on Raspberry Pi.
17489 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
17492 Changes in version 0.2.6.2-alpha - 2014-12-31
17493 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
17494 It introduces a major new backend for deciding when to send cells on
17495 channels, which should lead down the road to big performance
17496 increases. It contains security and statistics features for better
17497 work on hidden services, and numerous bugfixes.
17499 This release contains many new unit tests, along with major
17500 performance improvements for running testing networks using Chutney.
17501 Thanks to a series of patches contributed by "teor", testing networks
17502 should now bootstrap in seconds, rather than minutes.
17504 o Major features (relay, infrastructure):
17505 - Complete revision of the code that relays use to decide which cell
17506 to send next. Formerly, we selected the best circuit to write on
17507 each channel, but we didn't select among channels in any
17508 sophisticated way. Now, we choose the best circuits globally from
17509 among those whose channels are ready to deliver traffic.
17511 This patch implements a new inter-cmux comparison API, a global
17512 high/low watermark mechanism and a global scheduler loop for
17513 transmission prioritization across all channels as well as among
17514 circuits on one channel. This schedule is currently tuned to
17515 (tolerantly) avoid making changes in network performance, but it
17516 should form the basis for major circuit performance increases in
17517 the future. Code by Andrea; tuning by Rob Jansen; implements
17520 o Major features (hidden services):
17521 - Make HS port scanning more difficult by immediately closing the
17522 circuit when a user attempts to connect to a nonexistent port.
17523 Closes ticket 13667.
17524 - Add a HiddenServiceStatistics option that allows Tor relays to
17525 gather and publish statistics about the overall size and volume of
17526 hidden service usage. Specifically, when this option is turned on,
17527 an HSDir will publish an approximate number of hidden services
17528 that have published descriptors to it the past 24 hours. Also, if
17529 a relay has acted as a hidden service rendezvous point, it will
17530 publish the approximate amount of rendezvous cells it has relayed
17531 the past 24 hours. The statistics themselves are obfuscated so
17532 that the exact values cannot be derived. For more details see
17533 proposal 238, "Better hidden service stats from Tor relays". This
17534 feature is currently disabled by default. Implements feature 13192.
17536 o Major bugfixes (client, automap):
17537 - Repair automapping with IPv6 addresses. This automapping should
17538 have worked previously, but one piece of debugging code that we
17539 inserted to detect a regression actually caused the regression to
17540 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
17541 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
17544 o Major bugfixes (hidden services):
17545 - When closing an introduction circuit that was opened in parallel
17546 with others, don't mark the introduction point as unreachable.
17547 Previously, the first successful connection to an introduction
17548 point would make the other introduction points get marked as
17549 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
17551 o Directory authority changes:
17552 - Remove turtles as a directory authority.
17553 - Add longclaw as a new (v3) directory authority. This implements
17554 ticket 13296. This keeps the directory authority count at 9.
17556 o Major removed features:
17557 - Tor clients no longer support connecting to hidden services
17558 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
17559 option has been removed. (There shouldn't be any hidden services
17560 running these versions on the network.) Closes ticket 7803.
17562 o Minor features (client):
17563 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
17564 is enabled, reject requests with IP addresses as hostnames.
17565 Resolves ticket 13315.
17567 o Minor features (controller):
17568 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
17569 write an unscheduled heartbeat message to the log. Implements
17572 o Minor features (geoip):
17573 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
17576 o Minor features (hidden services):
17577 - When re-enabling the network, don't try to build introduction
17578 circuits until we have successfully built a circuit. This makes
17579 hidden services come up faster when the network is re-enabled.
17580 Patch from "akwizgran". Closes ticket 13447.
17581 - When we fail to retrieve a hidden service descriptor, send the
17582 controller an "HS_DESC FAILED" controller event. Implements
17584 - New HiddenServiceDirGroupReadable option to cause hidden service
17585 directories and hostname files to be created group-readable. Patch
17586 from "anon", David Stainton, and "meejah". Closes ticket 11291.
17588 o Minor features (systemd):
17589 - Where supported, when running with systemd, report successful
17590 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
17591 - When running with systemd, support systemd watchdog messages. Part
17592 of ticket 11016. Patch by Michael Scherer.
17594 o Minor features (transparent proxy):
17595 - Update the transparent proxy option checks to allow for both ipfw
17596 and pf on OS X. Closes ticket 14002.
17597 - Use the correct option when using IPv6 with transparent proxy
17598 support on Linux. Resolves 13808. Patch by Francisco Blas
17601 o Minor bugfixes (preventative security, C safety):
17602 - When reading a hexadecimal, base-32, or base-64 encoded value from
17603 a string, always overwrite the whole output buffer. This prevents
17604 some bugs where we would look at (but fortunately, not reveal)
17605 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17607 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
17608 just the part that's used. This makes it harder for data leak bugs
17609 to occur in the event of other programming failures. Resolves
17612 o Minor bugfixes (client, microdescriptors):
17613 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
17614 computing which microdescriptors to download. This keeps us from
17615 erroneous download behavior if two microdescriptor digests ever
17616 have the same first 160 bits. Fixes part of bug 13399; bugfix
17618 - Reset a router's status if its microdescriptor digest changes,
17619 even if the first 160 bits remain the same. Fixes part of bug
17620 13399; bugfix on 0.2.3.1-alpha.
17622 o Minor bugfixes (compilation):
17623 - Silence clang warnings under --enable-expensive-hardening,
17624 including implicit truncation of 64 bit values to 32 bit, const
17625 char assignment to self, tautological compare, and additional
17626 parentheses around equality tests. Fixes bug 13577; bugfix
17628 - Fix a clang warning about checking whether an address in the
17629 middle of a structure is NULL. Fixes bug 14001; bugfix
17632 o Minor bugfixes (hidden services):
17633 - Correctly send a controller event when we find that a rendezvous
17634 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
17635 - Pre-check directory permissions for new hidden-services to avoid
17636 at least one case of "Bug: Acting on config options left us in a
17637 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
17638 - When adding a new hidden service (for example, via SETCONF), Tor
17639 no longer congratulates the user for running a relay. Fixes bug
17640 13941; bugfix on 0.2.6.1-alpha.
17641 - When fetching hidden service descriptors, we now check not only
17642 for whether we got the hidden service we had in mind, but also
17643 whether we got the particular descriptors we wanted. This prevents
17644 a class of inefficient but annoying DoS attacks by hidden service
17645 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
17648 o Minor bugfixes (Linux seccomp2 sandbox):
17649 - Make transparent proxy support work along with the seccomp2
17650 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
17651 by Francisco Blas Izquierdo Riera.
17652 - Fix a memory leak in tor-resolve when running with the sandbox
17653 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
17655 o Minor bugfixes (logging):
17656 - Downgrade warnings about RSA signature failures to info log level.
17657 Emit a warning when an extra info document is found incompatible
17658 with a corresponding router descriptor. Fixes bug 9812; bugfix
17660 - Make connection_ap_handshake_attach_circuit() log the circuit ID
17661 correctly. Fixes bug 13701; bugfix on 0.0.6.
17663 o Minor bugfixes (misc):
17664 - Stop allowing invalid address patterns like "*/24" that contain
17665 both a wildcard address and a bit prefix length. This affects all
17666 our address-range parsing code. Fixes bug 7484; bugfix
17669 o Minor bugfixes (testing networks, fast startup):
17670 - Allow Tor to build circuits using a consensus with no exits. If
17671 the consensus has no exits (typical of a bootstrapping test
17672 network), allow Tor to build circuits once enough descriptors have
17673 been downloaded. This assists in bootstrapping a testing Tor
17674 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
17676 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
17677 header to directory servers. This allows us to obtain consensuses
17678 promptly when the consensus interval is very short. This assists
17679 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
17680 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
17681 - Stop assuming that private addresses are local when checking
17682 reachability in a TestingTorNetwork. Instead, when testing, assume
17683 all OR connections are remote. (This is necessary due to many test
17684 scenarios running all relays on localhost.) This assists in
17685 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
17686 0.1.0.1-rc. Patch by "teor".
17687 - Avoid building exit circuits from a consensus with no exits. Now
17688 thanks to our fix for 13718, we accept a no-exit network as not
17689 wholly lost, but we need to remember not to try to build exit
17690 circuits on it. Closes ticket 13814; patch by "teor".
17691 - Stop requiring exits to have non-zero bandwithcapacity in a
17692 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
17693 ignore exit bandwidthcapacity. This assists in bootstrapping a
17694 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
17695 on 0.2.0.3-alpha. Patch by "teor".
17696 - Add "internal" to some bootstrap statuses when no exits are
17697 available. If the consensus does not contain Exits, Tor will only
17698 build internal circuits. In this case, relevant statuses will
17699 contain the word "internal" as indicated in the Tor control-
17700 spec.txt. When bootstrap completes, Tor will be ready to build
17701 internal circuits. If a future consensus contains Exits, exit
17702 circuits may become available. Fixes part of bug 13718; bugfix on
17703 0.2.4.10-alpha. Patch by "teor".
17704 - Decrease minimum consensus interval to 10 seconds when
17705 TestingTorNetwork is set, or 5 seconds for the first consensus.
17706 Fix assumptions throughout the code that assume larger intervals.
17707 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
17709 - Avoid excluding guards from path building in minimal test
17710 networks, when we're in a test network and excluding guards would
17711 exclude all relays. This typically occurs in incredibly small tor
17712 networks, and those using "TestingAuthVoteGuard *". Fixes part of
17713 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
17715 o Code simplification and refactoring:
17716 - Stop using can_complete_circuits as a global variable; access it
17717 with a function instead.
17718 - Avoid using operators directly as macro arguments: this lets us
17719 apply coccinelle transformations to our codebase more directly.
17720 Closes ticket 13172.
17721 - Combine the functions used to parse ClientTransportPlugin and
17722 ServerTransportPlugin into a single function. Closes ticket 6456.
17723 - Add inline functions and convenience macros for inspecting channel
17724 state. Refactor the code to use convenience macros instead of
17725 checking channel state directly. Fixes issue 7356.
17726 - Document all members of was_router_added_t and rename
17727 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
17728 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
17729 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
17730 constant instead of hardcoded value. Fixes issue 13840.
17731 - Refactor our generic strmap and digestmap types into a single
17732 implementation, so that we can add a new digest256map
17736 - Document the bridge-authority-only 'networkstatus-bridges' file.
17737 Closes ticket 13713; patch from "tom".
17738 - Fix typo in PredictedPortsRelevanceTime option description in
17739 manpage. Resolves issue 13707.
17740 - Stop suggesting that users specify relays by nickname: it isn't a
17741 good idea. Also, properly cross-reference how to specify relays in
17742 all parts of manual documenting options that take a list of
17743 relays. Closes ticket 13381.
17744 - Clarify the HiddenServiceDir option description in manpage to make
17745 it clear that relative paths are taken with respect to the current
17746 working directory. Also clarify that this behavior is not
17747 guaranteed to remain indefinitely. Fixes issue 13913.
17750 - New tests for many parts of channel, relay, and circuitmux
17751 functionality. Code by Andrea; part of 9262.
17752 - New tests for parse_transport_line(). Part of ticket 6456.
17753 - In the unit tests, use chgrp() to change the group of the unit
17754 test temporary directory to the current user, so that the sticky
17755 bit doesn't interfere with tests that check directory groups.
17757 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
17761 Changes in version 0.2.6.1-alpha - 2014-10-30
17762 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
17763 includes numerous code cleanups and new tests, and fixes a large
17764 number of annoying bugs. Out-of-memory conditions are handled better
17765 than in 0.2.5, pluggable transports have improved proxy support, and
17766 clients now use optimistic data for contacting hidden services. Also,
17767 we are now more robust to changes in what we consider a parseable
17768 directory object, so that tightening restrictions does not have a risk
17769 of introducing infinite download loops.
17771 This is the first alpha release in a new series, so expect there to be
17772 bugs. Users who would rather test out a more stable branch should stay
17773 with 0.2.5.x for now.
17775 o New compiler and system requirements:
17776 - Tor 0.2.6.x requires that your compiler support more of the C99
17777 language standard than before. The 'configure' script now detects
17778 whether your compiler supports C99 mid-block declarations and
17779 designated initializers. If it does not, Tor will not compile.
17781 We may revisit this requirement if it turns out that a significant
17782 number of people need to build Tor with compilers that don't
17783 bother implementing a 15-year-old standard. Closes ticket 13233.
17784 - Tor no longer supports systems without threading support. When we
17785 began working on Tor, there were several systems that didn't have
17786 threads, or where the thread support wasn't able to run the
17787 threads of a single process on multiple CPUs. That no longer
17788 holds: every system where Tor needs to run well now has threading
17789 support. Resolves ticket 12439.
17791 o Removed platform support:
17792 - We no longer include special code to build on Windows CE; as far
17793 as we know, nobody has used Tor on Windows CE in a very long time.
17794 Closes ticket 11446.
17796 o Major features (bridges):
17797 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
17798 transports if they are configured via the "TOR_PT_PROXY"
17799 environment variable. Implements proposal 232. Resolves
17802 o Major features (client performance, hidden services):
17803 - Allow clients to use optimistic data when connecting to a hidden
17804 service, which should remove a round-trip from hidden service
17805 initialization. See proposal 181 for details. Implements
17808 o Major features (directory system):
17809 - Upon receiving an unparseable directory object, if its digest
17810 matches what we expected, then don't try to download it again.
17811 Previously, when we got a descriptor we didn't like, we would keep
17812 trying to download it over and over. Closes ticket 11243.
17814 o Major features (sample torrc):
17815 - Add a new, infrequently-changed "torrc.minimal". This file is
17816 similar to torrc.sample, but it will change as infrequently as
17817 possible, for the benefit of users whose systems prompt them for
17818 intervention whenever a default configuration file is changed.
17819 Making this change allows us to update torrc.sample to be a more
17820 generally useful "sample torrc".
17822 o Major bugfixes (directory authorities):
17823 - Do not assign the HSDir flag to relays if they are not Valid, or
17824 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
17826 o Major bugfixes (directory bandwidth performance):
17827 - Don't flush the zlib buffer aggressively when compressing
17828 directory information for clients. This should save about 7% of
17829 the bandwidth currently used for compressed descriptors and
17830 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
17832 o Minor features (security, memory wiping):
17833 - Ensure we securely wipe keys from memory after
17834 crypto_digest_get_digest and init_curve25519_keypair_from_file
17835 have finished using them. Resolves ticket 13477.
17837 o Minor features (security, out-of-memory handling):
17838 - When handling an out-of-memory condition, allocate less memory for
17839 temporary data structures. Fixes issue 10115.
17840 - When handling an out-of-memory condition, consider more types of
17841 buffers, including those on directory connections, and zlib
17842 buffers. Resolves ticket 11792.
17845 - When identity keypair is generated for first time, log a
17846 congratulatory message that links to the new relay lifecycle
17847 document. Implements feature 10427.
17849 o Minor features (client):
17850 - Clients are now willing to send optimistic data (before they
17851 receive a 'connected' cell) to relays of any version. (Relays
17852 without support for optimistic data are no longer supported on the
17853 Tor network.) Resolves ticket 13153.
17855 o Minor features (directory authorities):
17856 - Don't list relays with a bandwidth estimate of 0 in the consensus.
17857 Implements a feature proposed during discussion of bug 13000.
17858 - In tor-gencert, report an error if the user provides the same
17859 argument more than once.
17860 - If a directory authority can't find a best consensus method in the
17861 votes that it holds, it now falls back to its favorite consensus
17862 method. Previously, it fell back to method 1. Neither of these is
17863 likely to get enough signatures, but "fall back to favorite"
17864 doesn't require us to maintain support an obsolete consensus
17865 method. Implements part of proposal 215.
17867 o Minor features (logging):
17868 - On Unix-like systems, you can now use named pipes as the target of
17869 the Log option, and other options that try to append to files.
17870 Closes ticket 12061. Patch from "carlo von lynX".
17871 - When opening a log file at startup, send it every log message that
17872 we generated between startup and opening it. Previously, log
17873 messages that were generated before opening the log file were only
17874 logged to stdout. Closes ticket 6938.
17875 - Add a TruncateLogFile option to overwrite logs instead of
17876 appending to them. Closes ticket 5583.
17878 o Minor features (portability, Solaris):
17879 - Threads are no longer disabled by default on Solaris; we believe
17880 that the versions of Solaris with broken threading support are all
17881 obsolete by now. Resolves ticket 9495.
17883 o Minor features (relay):
17884 - Re-check our address after we detect a changed IP address from
17885 getsockname(). This ensures that the controller command "GETINFO
17886 address" will report the correct value. Resolves ticket 11582.
17888 - A new AccountingRule option lets Relays set whether they'd like
17889 AccountingMax to be applied separately to inbound and outbound
17890 traffic, or applied to the sum of inbound and outbound traffic.
17891 Resolves ticket 961. Patch by "chobe".
17893 o Minor features (testing networks):
17894 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
17895 the "Exit" flag regardless of their uptime, bandwidth, or exit
17896 policy. TestingTorNetwork must be set for this option to have any
17897 effect. Previously, authorities would take up to 35 minutes to
17898 give nodes the Exit flag in a test network. Partially implements
17901 o Minor features (validation):
17902 - Check all date/time values passed to tor_timegm and
17903 parse_rfc1123_time for validity, taking leap years into account.
17904 Improves HTTP header validation. Implemented with bug 13476.
17905 - In correct_tm(), limit the range of values returned by system
17906 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
17907 This means we don't have to deal with negative or too large dates,
17908 even if a clock is wrong. Otherwise we might fail to read a file
17909 written by us which includes such a date. Fixes bug 13476.
17911 o Minor bugfixes (bridge clients):
17912 - When configured to use a bridge without an identity digest (not
17913 recommended), avoid launching an extra channel to it when
17914 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
17916 o Minor bugfixes (bridges):
17917 - When DisableNetwork is set, do not launch pluggable transport
17918 plugins, and if any are running, terminate them. Fixes bug 13213;
17919 bugfix on 0.2.3.6-alpha.
17921 o Minor bugfixes (C correctness):
17922 - Fix several instances of possible integer overflow/underflow/NaN.
17923 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
17925 - In circuit_build_times_calculate_timeout() in circuitstats.c,
17926 avoid dividing by zero in the pareto calculations. This traps
17927 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
17929 - Fix an integer overflow in format_time_interval(). Fixes bug
17930 13393; bugfix on 0.2.0.10-alpha.
17931 - Set the correct day of year value when the system's localtime(_r)
17932 or gmtime(_r) functions fail to set struct tm. Not externally
17933 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
17934 - Avoid unlikely signed integer overflow in tor_timegm on systems
17935 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
17937 o Minor bugfixes (client):
17938 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
17939 BadExit flag are not considered worthy candidates. Fixes bug
17940 13066; bugfix on 0.1.2.3-alpha.
17941 - Use the consensus schedule for downloading consensuses, and not
17942 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
17943 - Handle unsupported or malformed SOCKS5 requests properly by
17944 responding with the appropriate error message before closing the
17945 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
17947 o Minor bugfixes (client, torrc):
17948 - Stop modifying the value of our DirReqStatistics torrc option just
17949 because we're not a bridge or relay. This bug was causing Tor
17950 Browser users to write "DirReqStatistics 0" in their torrc files
17951 as if they had chosen to change the config. Fixes bug 4244; bugfix
17953 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
17954 that our options have changed every time we SIGHUP. Fixes bug
17955 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
17957 o Minor bugfixes (controller):
17958 - Return an error when the second or later arguments of the
17959 "setevents" controller command are invalid events. Previously we
17960 would return success while silently skipping invalid events. Fixes
17961 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
17963 o Minor bugfixes (directory system):
17964 - Always believe that v3 directory authorities serve extra-info
17965 documents, whether they advertise "caches-extra-info" or not.
17966 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
17967 - When running as a v3 directory authority, advertise that you serve
17968 extra-info documents so that clients who want them can find them
17969 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
17970 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
17971 Previously, directories offering BRIDGE_DIRINFO and some other
17972 flag (i.e. microdescriptors or extrainfo) would be ignored when
17973 looking for bridges. Partially fixes bug 13163; bugfix
17976 o Minor bugfixes (networking):
17977 - Check for orconns and use connection_or_close_for_error() rather
17978 than connection_mark_for_close() directly in the getsockopt()
17979 failure case of connection_handle_write_impl(). Fixes bug 11302;
17980 bugfix on 0.2.4.4-alpha.
17982 o Minor bugfixes (relay):
17983 - When generating our family list, remove spaces from around the
17984 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
17985 - If our previous bandwidth estimate was 0 bytes, allow publishing a
17986 new relay descriptor immediately. Fixes bug 13000; bugfix
17989 o Minor bugfixes (testing networks):
17990 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
17991 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
17992 - Stop using the default authorities in networks which provide both
17993 AlternateDirAuthority and AlternateBridgeAuthority. Partially
17994 fixes bug 13163; bugfix on 0.2.0.13-alpha.
17996 o Minor bugfixes (testing):
17997 - Stop spawn test failures due to a race condition between the
17998 SIGCHLD handler updating the process status, and the test reading
17999 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
18001 o Minor bugfixes (testing, Windows):
18002 - Avoid passing an extra backslash when creating a temporary
18003 directory for running the unit tests on Windows. Fixes bug 12392;
18004 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
18006 o Minor bugfixes (windows):
18007 - Remove code to special-case handling of NTE_BAD_KEYSET when
18008 acquiring windows CryptoAPI context. This error can't actually
18009 occur for the parameters we're providing. Fixes bug 10816; bugfix
18012 o Minor bugfixes (zlib):
18013 - Avoid truncating a zlib stream when trying to finalize it with an
18014 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
18017 - Allow our configure script to build correctly with autoconf 2.62
18018 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
18019 - Improve the error message from ./configure to make it clear that
18020 when asciidoc has not been found, the user will have to either add
18021 --disable-asciidoc argument or install asciidoc. Resolves
18024 o Code simplification and refactoring:
18025 - Change the entry_is_live() function to take named bitfield
18026 elements instead of an unnamed list of booleans. Closes
18028 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
18029 Resolves ticket 12205.
18030 - Use calloc and reallocarray functions instead of multiply-
18031 then-malloc. This makes it less likely for us to fall victim to an
18032 integer overflow attack when allocating. Resolves ticket 12855.
18033 - Use the standard macro name SIZE_MAX, instead of our
18035 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
18036 functions which take them as arguments. Replace 0 with NO_DIRINFO
18037 in a function call for clarity. Seeks to prevent future issues
18039 - Avoid 4 null pointer errors under clang static analysis by using
18040 tor_assert() to prove that the pointers aren't null. Fixes
18042 - Rework the API of policies_parse_exit_policy() to use a bitmask to
18043 represent parsing options, instead of a confusing mess of
18044 booleans. Resolves ticket 8197.
18045 - Introduce a helper function to parse ExitPolicy in
18046 or_options_t structure.
18049 - Add a doc/TUNING document with tips for handling large numbers of
18050 TCP connections when running busy Tor relay. Update the warning
18051 message to point to this file when running out of sockets
18052 operating system is allowing to use simultaneously. Resolves
18055 o Removed features:
18056 - We no longer remind the user about configuration options that have
18057 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
18058 - Remove our old, non-weighted bandwidth-based node selection code.
18059 Previously, we used it as a fallback when we couldn't perform
18060 weighted bandwidth-based node selection. But that would only
18061 happen in the cases where we had no consensus, or when we had a
18062 consensus generated by buggy or ancient directory authorities. In
18063 either case, it's better to use the more modern, better maintained
18064 algorithm, with reasonable defaults for the weights. Closes
18066 - Remove the --disable-curve25519 configure option. Relays and
18067 clients now are required to support curve25519 and the
18069 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
18070 used to be deprecated synonyms for "StrictNodes", are now marked
18071 obsolete. Resolves ticket 12226.
18072 - Clients don't understand the BadDirectory flag in the consensus
18073 anymore, and ignore it.
18076 - Refactor the function that chooses guard nodes so that it can more
18077 easily be tested; write some tests for it.
18078 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
18079 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
18080 - Create unit tests for format_time_interval(). With bug 13393.
18081 - Add unit tests for tor_timegm signed overflow, tor_timegm and
18082 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
18083 tests (visible) fixes in bug 13476.
18084 - Add a "coverage-html" make target to generate HTML-visualized
18085 coverage results when building with --enable-coverage. (Requires
18086 lcov.) Patch from Kevin Murray.
18087 - Enable the backtrace handler (where supported) when running the
18089 - Revise all unit tests that used the legacy test_* macros to
18090 instead use the recommended tt_* macros. This patch was generated
18091 with coccinelle, to avoid manual errors. Closes ticket 13119.
18093 o Distribution (systemd):
18094 - systemd unit file: only allow tor to write to /var/lib/tor and
18095 /var/log/tor. The rest of the filesystem is accessible for reading
18096 only. Patch by intrigeri; resolves ticket 12751.
18097 - systemd unit file: ensure that the process and all its children
18098 can never gain new privileges. Patch by intrigeri; resolves
18100 - systemd unit file: set up /var/run/tor as writable for the Tor
18101 service. Patch by intrigeri; resolves ticket 13196.
18103 o Removed features (directory authorities):
18104 - Remove code that prevented authorities from listing Tor relays
18105 affected by CVE-2011-2769 as guards. These relays are already
18106 rejected altogether due to the minimum version requirement of
18107 0.2.3.16-alpha. Closes ticket 13152.
18108 - The "AuthDirRejectUnlisted" option no longer has any effect, as
18109 the fingerprints file (approved-routers) has been deprecated.
18110 - Directory authorities do not support being Naming dirauths anymore.
18111 The "NamingAuthoritativeDir" config option is now obsolete.
18112 - Directory authorities do not support giving out the BadDirectory
18114 - Directory authorities no longer advertise or support consensus
18115 methods 1 through 12 inclusive. These consensus methods were
18116 obsolete and/or insecure: maintaining the ability to support them
18117 served no good purpose. Implements part of proposal 215; closes
18120 o Testing (test-network.sh):
18121 - Stop using "echo -n", as some shells' built-in echo doesn't
18122 support "-n". Instead, use "/bin/echo -n". Partially fixes
18124 - Stop an apparent test-network hang when used with make -j2. Fixes
18126 - Add a --delay option to test-network.sh, which configures the
18127 delay before the chutney network tests for data transmission.
18128 Partially implements ticket 13161.
18131 Changes in version 0.2.5.10 - 2014-10-24
18132 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
18134 It adds several new security features, including improved
18135 denial-of-service resistance for relays, new compiler hardening
18136 options, and a system-call sandbox for hardened installations on Linux
18137 (requires seccomp2). The controller protocol has several new features,
18138 resolving IPv6 addresses should work better than before, and relays
18139 should be a little more CPU-efficient. We've added support for more
18140 OpenBSD and FreeBSD transparent proxy types. We've improved the build
18141 system and testing infrastructure to allow unit testing of more parts
18142 of the Tor codebase. Finally, we've addressed several nagging pluggable
18143 transport usability issues, and included numerous other small bugfixes
18144 and features mentioned below.
18146 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
18147 have accumulated many known flaws; everyone should upgrade.
18149 o Deprecated versions:
18150 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
18151 attention for some while.
18154 Changes in version 0.2.5.9-rc - 2014-10-20
18155 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
18156 series. It disables SSL3 in response to the recent "POODLE" attack
18157 (even though POODLE does not affect Tor). It also works around a crash
18158 bug caused by some operating systems' response to the "POODLE" attack
18159 (which does affect Tor). It also contains a few miscellaneous fixes.
18161 o Major security fixes:
18162 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18163 today support TLS 1.0 or later, so we can safely turn off support
18164 for this old (and insecure) protocol. Fixes bug 13426.
18166 o Major bugfixes (openssl bug workaround):
18167 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18168 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18169 13471. This is a workaround for an OpenSSL bug.
18172 - Disable the sandbox name resolver cache when running tor-resolve:
18173 tor-resolve doesn't use the sandbox code, and turning it on was
18174 breaking attempts to do tor-resolve on a non-default server on
18175 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
18177 o Compilation fixes:
18178 - Build and run correctly on systems like OpenBSD-current that have
18179 patched OpenSSL to remove get_cipher_by_char and/or its
18180 implementations. Fixes issue 13325.
18182 o Downgraded warnings:
18183 - Downgrade the severity of the 'unexpected sendme cell from client'
18184 from 'warn' to 'protocol warning'. Closes ticket 8093.
18187 Changes in version 0.2.4.25 - 2014-10-20
18188 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
18189 (even though POODLE does not affect Tor). It also works around a crash
18190 bug caused by some operating systems' response to the "POODLE" attack
18191 (which does affect Tor).
18193 o Major security fixes (also in 0.2.5.9-rc):
18194 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18195 today support TLS 1.0 or later, so we can safely turn off support
18196 for this old (and insecure) protocol. Fixes bug 13426.
18198 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
18199 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18200 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18201 13471. This is a workaround for an OpenSSL bug.
18204 Changes in version 0.2.5.8-rc - 2014-09-22
18205 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
18206 series. It fixes a bug that affects consistency and speed when
18207 connecting to hidden services, and it updates the location of one of
18208 the directory authorities.
18211 - Clients now send the correct address for their chosen rendezvous
18212 point when trying to access a hidden service. They used to send
18213 the wrong address, which would still work some of the time because
18214 they also sent the identity digest of the rendezvous point, and if
18215 the hidden service happened to try connecting to the rendezvous
18216 point from a relay that already had a connection open to it,
18217 the relay would reuse that connection. Now connections to hidden
18218 services should be more robust and faster. Also, this bug meant
18219 that clients were leaking to the hidden service whether they were
18220 on a little-endian (common) or big-endian (rare) system, which for
18221 some users might have reduced their anonymity. Fixes bug 13151;
18222 bugfix on 0.2.1.5-alpha.
18224 o Directory authority changes:
18225 - Change IP address for gabelmoo (v3 directory authority).
18228 Changes in version 0.2.4.24 - 2014-09-22
18229 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
18230 connecting to hidden services, and it updates the location of one of
18231 the directory authorities.
18234 - Clients now send the correct address for their chosen rendezvous
18235 point when trying to access a hidden service. They used to send
18236 the wrong address, which would still work some of the time because
18237 they also sent the identity digest of the rendezvous point, and if
18238 the hidden service happened to try connecting to the rendezvous
18239 point from a relay that already had a connection open to it,
18240 the relay would reuse that connection. Now connections to hidden
18241 services should be more robust and faster. Also, this bug meant
18242 that clients were leaking to the hidden service whether they were
18243 on a little-endian (common) or big-endian (rare) system, which for
18244 some users might have reduced their anonymity. Fixes bug 13151;
18245 bugfix on 0.2.1.5-alpha.
18247 o Directory authority changes:
18248 - Change IP address for gabelmoo (v3 directory authority).
18250 o Minor features (geoip):
18251 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18255 Changes in version 0.2.5.7-rc - 2014-09-11
18256 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
18257 release series, and some long-standing bugs related to ORPort reachability
18258 testing and failure to send CREATE cells. It is the first release
18259 candidate for the Tor 0.2.5.x series.
18261 o Major bugfixes (client, startup):
18262 - Start making circuits as soon as DisabledNetwork is turned off.
18263 When Tor started with DisabledNetwork set, it would correctly
18264 conclude that it shouldn't build circuits, but it would mistakenly
18265 cache this conclusion, and continue believing it even when
18266 DisableNetwork is set to 0. Fixes the bug introduced by the fix
18267 for bug 11200; bugfix on 0.2.5.4-alpha.
18268 - Resume expanding abbreviations for command-line options. The fix
18269 for bug 4647 accidentally removed our hack from bug 586 that
18270 rewrote HashedControlPassword to __HashedControlSessionPassword
18271 when it appears on the commandline (which allowed the user to set
18272 her own HashedControlPassword in the torrc file while the
18273 controller generates a fresh session password for each run). Fixes
18274 bug 12948; bugfix on 0.2.5.1-alpha.
18275 - Warn about attempts to run hidden services and relays in the same
18276 process: that's probably not a good idea. Closes ticket 12908.
18278 o Major bugfixes (relay):
18279 - Avoid queuing or sending destroy cells for circuit ID zero when we
18280 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
18281 Found and fixed by "cypherpunks".
18282 - Fix ORPort reachability detection on relays running behind a
18283 proxy, by correctly updating the "local" mark on the controlling
18284 channel when changing the address of an or_connection_t after the
18285 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
18287 o Minor features (bridge):
18288 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
18289 cookie file for the ExtORPort g+r by default.
18291 o Minor features (geoip):
18292 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18295 o Minor bugfixes (logging):
18296 - Reduce the log severity of the "Pluggable transport proxy does not
18297 provide any needed transports and will not be launched." message,
18298 since Tor Browser includes several ClientTransportPlugin lines in
18299 its torrc-defaults file, leading every Tor Browser user who looks
18300 at her logs to see these notices and wonder if they're dangerous.
18301 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
18302 - Downgrade "Unexpected onionskin length after decryption" warning
18303 to a protocol-warn, since there's nothing relay operators can do
18304 about a client that sends them a malformed create cell. Resolves
18305 bug 12996; bugfix on 0.0.6rc1.
18306 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
18307 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
18308 - When logging information about an EXTEND2 or EXTENDED2 cell, log
18309 their names correctly. Fixes part of bug 12700; bugfix
18311 - When logging information about a relay cell whose command we don't
18312 recognize, log its command as an integer. Fixes part of bug 12700;
18313 bugfix on 0.2.1.10-alpha.
18314 - Escape all strings from the directory connection before logging
18315 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
18317 o Minor bugfixes (controller):
18318 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
18319 bug 12864; bugfix on 0.2.5.1-alpha.
18320 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
18321 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
18324 o Minor bugfixes (compilation):
18325 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
18326 bugfix on 0.2.5.5-alpha.
18327 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
18328 0.2.5.1-alpha. Patch from "NewEraCracker".
18329 - In routerlist_assert_ok(), don't take the address of a
18330 routerinfo's cache_info member unless that routerinfo is non-NULL.
18331 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
18332 - Fix a large number of false positive warnings from the clang
18333 analyzer static analysis tool. This should make real warnings
18334 easier for clang analyzer to find. Patch from "teor". Closes
18337 o Distribution (systemd):
18338 - Verify configuration file via ExecStartPre in the systemd unit
18339 file. Patch from intrigeri; resolves ticket 12730.
18340 - Explicitly disable RunAsDaemon in the systemd unit file. Our
18341 current systemd unit uses "Type = simple", so systemd does not
18342 expect tor to fork. If the user has "RunAsDaemon 1" in their
18343 torrc, then things won't work as expected. This is e.g. the case
18344 on Debian (and derivatives), since there we pass "--defaults-torrc
18345 /usr/share/tor/tor-service-defaults-torrc" (that contains
18346 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
18350 - Adjust the URLs in the README to refer to the new locations of
18351 several documents on the website. Fixes bug 12830. Patch from
18353 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
18357 Changes in version 0.2.5.6-alpha - 2014-07-28
18358 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
18359 risk from guard rotation, and fixes a variety of other issues to get
18360 us closer to a release candidate.
18362 o Major features (also in 0.2.4.23):
18363 - Make the number of entry guards configurable via a new
18364 NumEntryGuards consensus parameter, and the number of directory
18365 guards configurable via a new NumDirectoryGuards consensus
18366 parameter. Implements ticket 12688.
18368 o Major bugfixes (also in 0.2.4.23):
18369 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18370 implementation that caused incorrect results on 32-bit
18371 implementations when certain malformed inputs were used along with
18372 a small class of private ntor keys. This bug does not currently
18373 appear to allow an attacker to learn private keys or impersonate a
18374 Tor server, but it could provide a means to distinguish 32-bit Tor
18375 implementations from 64-bit Tor implementations. Fixes bug 12694;
18376 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18380 - Perform circuit cleanup operations even when circuit
18381 construction operations are disabled (because the network is
18382 disabled, or because there isn't enough directory information).
18383 Previously, when we were not building predictive circuits, we
18384 were not closing expired circuits either. Fixes bug 8387; bugfix on
18385 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
18386 became more strict about when we have "enough directory information
18387 to build circuits".
18390 - Authorities now assign the Guard flag to the fastest 25% of the
18391 network (it used to be the fastest 50%). Also raise the consensus
18392 weight that guarantees the Guard flag from 250 to 2000. For the
18393 current network, this results in about 1100 guards, down from 2500.
18394 This step paves the way for moving the number of entry guards
18395 down to 1 (proposal 236) while still providing reasonable expected
18396 performance for most users. Implements ticket 12690.
18397 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18399 - Slightly enhance the diagnostic message for bug 12184.
18401 o Minor bugfixes (also in 0.2.4.23):
18402 - Warn and drop the circuit if we receive an inbound 'relay early'
18403 cell. Those used to be normal to receive on hidden service circuits
18404 due to bug 1038, but the buggy Tor versions are long gone from
18405 the network so we can afford to resume watching for them. Resolves
18406 the rest of bug 1038; bugfix on 0.2.1.19.
18407 - Correct a confusing error message when trying to extend a circuit
18408 via the control protocol but we don't know a descriptor or
18409 microdescriptor for one of the specified relays. Fixes bug 12718;
18410 bugfix on 0.2.3.1-alpha.
18413 - Fix compilation when building with bufferevents enabled. (This
18414 configuration is still not expected to work, however.)
18415 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
18416 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
18418 - Compile correctly with builds and forks of OpenSSL (such as
18419 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
18420 0.2.1.1-alpha. Patch from "dhill".
18423 Changes in version 0.2.4.23 - 2014-07-28
18424 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
18425 guard rotation, and also backports several important fixes from the
18426 Tor 0.2.5 alpha release series.
18429 - Clients now look at the "usecreatefast" consensus parameter to
18430 decide whether to use CREATE_FAST or CREATE cells for the first hop
18431 of their circuit. This approach can improve security on connections
18432 where Tor's circuit handshake is stronger than the available TLS
18433 connection security levels, but the tradeoff is more computational
18434 load on guard relays. Implements proposal 221. Resolves ticket 9386.
18435 - Make the number of entry guards configurable via a new
18436 NumEntryGuards consensus parameter, and the number of directory
18437 guards configurable via a new NumDirectoryGuards consensus
18438 parameter. Implements ticket 12688.
18441 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18442 implementation that caused incorrect results on 32-bit
18443 implementations when certain malformed inputs were used along with
18444 a small class of private ntor keys. This bug does not currently
18445 appear to allow an attacker to learn private keys or impersonate a
18446 Tor server, but it could provide a means to distinguish 32-bit Tor
18447 implementations from 64-bit Tor implementations. Fixes bug 12694;
18448 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18452 - Warn and drop the circuit if we receive an inbound 'relay early'
18453 cell. Those used to be normal to receive on hidden service circuits
18454 due to bug 1038, but the buggy Tor versions are long gone from
18455 the network so we can afford to resume watching for them. Resolves
18456 the rest of bug 1038; bugfix on 0.2.1.19.
18457 - Correct a confusing error message when trying to extend a circuit
18458 via the control protocol but we don't know a descriptor or
18459 microdescriptor for one of the specified relays. Fixes bug 12718;
18460 bugfix on 0.2.3.1-alpha.
18461 - Avoid an illegal read from stack when initializing the TLS
18462 module using a version of OpenSSL without all of the ciphers
18463 used by the v2 link handshake. Fixes bug 12227; bugfix on
18464 0.2.4.8-alpha. Found by "starlight".
18467 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18471 Changes in version 0.2.5.5-alpha - 2014-06-18
18472 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
18473 0.2.5.x release series, including a couple of DoS issues, some
18474 performance regressions, a large number of bugs affecting the Linux
18475 seccomp2 sandbox code, and various other bugfixes. It also adds
18476 diagnostic bugfixes for a few tricky issues that we're trying to
18479 o Major features (security, traffic analysis resistance):
18480 - Several major improvements to the algorithm used to decide when to
18481 close TLS connections. Previous versions of Tor closed connections
18482 at a fixed interval after the last time a non-padding cell was
18483 sent over the connection, regardless of the target of the
18484 connection. Now, we randomize the intervals by adding up to 50% of
18485 their base value, we measure the length of time since connection
18486 last had at least one circuit, and we allow connections to known
18487 ORs to remain open a little longer (15 minutes instead of 3
18488 minutes minimum). These changes should improve Tor's resistance
18489 against some kinds of traffic analysis, and lower some overhead
18490 from needlessly closed connections. Fixes ticket 6799.
18491 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
18493 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
18494 - Fix a memory leak that could occur if a microdescriptor parse
18495 fails during the tokenizing step. This bug could enable a memory
18496 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18499 o Major bugfixes (security, directory authorities):
18500 - Directory authorities now include a digest of each relay's
18501 identity key as a part of its microdescriptor.
18503 This is a workaround for bug 11743 (reported by "cypherpunks"),
18504 where Tor clients do not support receiving multiple
18505 microdescriptors with the same SHA256 digest in the same
18506 consensus. When clients receive a consensus like this, they only
18507 use one of the relays. Without this fix, a hostile relay could
18508 selectively disable some client use of target relays by
18509 constructing a router descriptor with a different identity and the
18510 same microdescriptor parameters and getting the authorities to
18511 list it in a microdescriptor consensus. This fix prevents an
18512 attacker from causing a microdescriptor collision, because the
18513 router's identity is not forgeable.
18515 o Major bugfixes (relay):
18516 - Use a direct dirport connection when uploading non-anonymous
18517 descriptors to the directory authorities. Previously, relays would
18518 incorrectly use tunnel connections under a fairly wide variety of
18519 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
18520 - When a circuit accidentally has the same circuit ID for its
18521 forward and reverse direction, correctly detect the direction of
18522 cells using that circuit. Previously, this bug made roughly one
18523 circuit in a million non-functional. Fixes bug 12195; this is a
18524 bugfix on every version of Tor.
18526 o Major bugfixes (client, pluggable transports):
18527 - When managing pluggable transports, use OS notification facilities
18528 to learn if they have crashed, and don't attempt to kill any
18529 process that has already exited. Fixes bug 8746; bugfix
18532 o Minor features (diagnostic):
18533 - When logging a warning because of bug 7164, additionally check the
18534 hash table for consistency (as proposed on ticket 11737). This may
18535 help diagnose bug 7164.
18536 - When we log a heartbeat, log how many one-hop circuits we have
18537 that are at least 30 minutes old, and log status information about
18538 a few of them. This is an attempt to track down bug 8387.
18539 - When encountering an unexpected CR while writing text to a file on
18540 Windows, log the name of the file. Should help diagnosing
18542 - Give more specific warnings when a client notices that an onion
18543 handshake has failed. Fixes ticket 9635.
18544 - Add significant new logging code to attempt to diagnose bug 12184,
18545 where relays seem to run out of available circuit IDs.
18546 - Improve the diagnostic log message for bug 8387 even further to
18547 try to improve our odds of figuring out why one-hop directory
18548 circuits sometimes do not get closed.
18550 o Minor features (security, memory management):
18551 - Memory allocation tricks (mempools and buffer freelists) are now
18552 disabled by default. You can turn them back on with
18553 --enable-mempools and --enable-buf-freelists respectively. We're
18554 disabling these features because malloc performance is good enough
18555 on most platforms, and a similar feature in OpenSSL exacerbated
18556 exploitation of the Heartbleed attack. Resolves ticket 11476.
18558 o Minor features (security):
18559 - Apply the secure SipHash-2-4 function to the hash table mapping
18560 circuit IDs and channels to circuits. We missed this one when we
18561 were converting all the other hash functions to use SipHash back
18562 in 0.2.5.3-alpha. Resolves ticket 11750.
18564 o Minor features (build):
18565 - The configure script has a --disable-seccomp option to turn off
18566 support for libseccomp on systems that have it, in case it (or
18567 Tor's use of it) is broken. Resolves ticket 11628.
18569 o Minor features (other):
18570 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
18573 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
18574 - When running a hidden service, do not allow TunneledDirConns 0;
18575 this will keep the hidden service from running, and also
18576 make it publish its descriptors directly over HTTP. Fixes bug 10849;
18577 bugfix on 0.2.1.1-alpha.
18579 o Minor bugfixes (performance):
18580 - Avoid a bug where every successful connection made us recompute
18581 the flag telling us whether we have sufficient information to
18582 build circuits. Previously, we would forget our cached value
18583 whenever we successfully opened a channel (or marked a router as
18584 running or not running for any other reason), regardless of
18585 whether we had previously believed the router to be running. This
18586 forced us to run an expensive update operation far too often.
18587 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
18588 - Avoid using tor_memeq() for checking relay cell integrity. This
18589 removes a possible performance bottleneck. Fixes part of bug
18590 12169; bugfix on 0.2.1.31.
18592 o Minor bugfixes (compilation):
18593 - Fix compilation of test_status.c when building with MVSC. Bugfix
18594 on 0.2.5.4-alpha. Patch from Gisle Vanem.
18595 - Resolve GCC complaints on OpenBSD about discarding constness in
18596 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
18597 on 0.1.1.23. Patch from Dana Koch.
18598 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
18599 treatment of long and time_t as comparable types. Fixes part of
18600 bug 11633. Patch from Dana Koch.
18601 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
18602 11623; bugfix on 0.2.5.3-alpha.
18603 - When deciding whether to build the 64-bit curve25519
18604 implementation, detect platforms where we can compile 128-bit
18605 arithmetic but cannot link it. Fixes bug 11729; bugfix on
18606 0.2.4.8-alpha. Patch from "conradev".
18607 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
18608 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
18609 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
18612 o Minor bugfixes (Directory server):
18613 - When sending a compressed set of descriptors or microdescriptors,
18614 make sure to finalize the zlib stream. Previously, we would write
18615 all the compressed data, but if the last descriptor we wanted to
18616 send was missing or too old, we would not mark the stream as
18617 finished. This caused problems for decompression tools. Fixes bug
18618 11648; bugfix on 0.1.1.23.
18620 o Minor bugfixes (Linux seccomp sandbox):
18621 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
18622 11622; bugfix on 0.2.5.1-alpha.
18623 - Avoid crashing when re-opening listener ports with the seccomp
18624 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
18625 - Avoid crashing with the seccomp sandbox enabled along with
18626 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
18627 - When we receive a SIGHUP with the sandbox enabled, correctly
18628 support rotating our log files. Fixes bug 12032; bugfix
18630 - Avoid crash when running with sandboxing enabled and
18631 DirReqStatistics not disabled. Fixes bug 12035; bugfix
18633 - Fix a "BUG" warning when trying to write bridge-stats files with
18634 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
18636 - Prevent the sandbox from crashing on startup when run with the
18637 --enable-expensive-hardening configuration option. Fixes bug
18638 11477; bugfix on 0.2.5.4-alpha.
18639 - When running with DirPortFrontPage and sandboxing both enabled,
18640 reload the DirPortFrontPage correctly when restarting. Fixes bug
18641 12028; bugfix on 0.2.5.1-alpha.
18642 - Don't try to enable the sandbox when using the Tor binary to check
18643 its configuration, hash a passphrase, or so on. Doing so was
18644 crashing on startup for some users. Fixes bug 11609; bugfix
18646 - Avoid warnings when running with sandboxing and node statistics
18647 enabled at the same time. Fixes part of 12064; bugfix on
18648 0.2.5.1-alpha. Patch from Michael Wolf.
18649 - Avoid warnings when running with sandboxing enabled at the same
18650 time as cookie authentication, hidden services, or directory
18651 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
18652 - Do not allow options that require calls to exec to be enabled
18653 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
18654 bug 12043; bugfix on 0.2.5.1-alpha.
18655 - Handle failures in getpwnam()/getpwuid() when running with the
18656 User option set and the Linux syscall sandbox enabled. Fixes bug
18657 11946; bugfix on 0.2.5.1-alpha.
18658 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
18659 to avoid calling getaddrinfo() after installing the sandbox
18660 filters. Previously, it preloaded a cache with the IPv4 address
18661 for our hostname, and nothing else. Now, it loads the cache with
18662 every address that it used to initialize the Tor process. Fixes
18663 bug 11970; bugfix on 0.2.5.1-alpha.
18665 o Minor bugfixes (pluggable transports):
18666 - Enable the ExtORPortCookieAuthFile option, to allow changing the
18667 default location of the authentication token for the extended OR
18668 Port as used by sever-side pluggable transports. We had
18669 implemented this option before, but the code to make it settable
18670 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
18671 - Avoid another 60-second delay when starting Tor in a pluggable-
18672 transport-using configuration when we already have cached
18673 descriptors for our bridges. Fixes bug 11965; bugfix
18676 o Minor bugfixes (client):
18677 - Avoid "Tried to open a socket with DisableNetwork set" warnings
18678 when starting a client with bridges configured and DisableNetwork
18679 set. (Tor launcher starts Tor with DisableNetwork set the first
18680 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
18682 o Minor bugfixes (testing):
18683 - The Python parts of the test scripts now work on Python 3 as well
18684 as Python 2, so systems where '/usr/bin/python' is Python 3 will
18685 no longer have the tests break. Fixes bug 11608; bugfix
18687 - When looking for versions of python that we could run the tests
18688 with, check for "python2.7" and "python3.3"; previously we were
18689 only looking for "python", "python2", and "python3". Patch from
18690 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
18691 - Fix all valgrind warnings produced by the unit tests. There were
18692 over a thousand memory leak warnings previously, mostly produced
18693 by forgetting to free things in the unit test code. Fixes bug
18694 11618, bugfixes on many versions of Tor.
18696 o Minor bugfixes (tor-fw-helper):
18697 - Give a correct log message when tor-fw-helper fails to launch.
18698 (Previously, we would say something like "tor-fw-helper sent us a
18699 string we could not parse".) Fixes bug 9781; bugfix
18702 o Minor bugfixes (relay, threading):
18703 - Check return code on spawn_func() in cpuworker code, so that we
18704 don't think we've spawned a nonworking cpuworker and write junk to
18705 it forever. Fix related to bug 4345; bugfix on all released Tor
18706 versions. Found by "skruffy".
18707 - Use a pthread_attr to make sure that spawn_func() cannot return an
18708 error while at the same time launching a thread. Fix related to
18709 bug 4345; bugfix on all released Tor versions. Reported
18712 o Minor bugfixes (relay, oom prevention):
18713 - Correctly detect the total available system memory. We tried to do
18714 this in 0.2.5.4-alpha, but the code was set up to always return an
18715 error value, even on success. Fixes bug 11805; bugfix
18718 o Minor bugfixes (relay, other):
18719 - We now drop CREATE cells for already-existent circuit IDs and for
18720 zero-valued circuit IDs, regardless of other factors that might
18721 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
18723 - Avoid an illegal read from stack when initializing the TLS module
18724 using a version of OpenSSL without all of the ciphers used by the
18725 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
18727 - When rejecting DATA cells for stream_id zero, still count them
18728 against the circuit's deliver window so that we don't fail to send
18729 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
18731 o Minor bugfixes (logging):
18732 - Fix a misformatted log message about delayed directory fetches.
18733 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
18734 - Squelch a spurious LD_BUG message "No origin circuit for
18735 successful SOCKS stream" in certain hidden service failure cases;
18739 - Include a tor.service file in contrib/dist for use with systemd.
18740 Some distributions will be able to use this file unmodified;
18741 others will need to tweak it, or write their own. Patch from Jamie
18742 Nguyen; resolves ticket 8368.
18745 - Clean up several option names in the manpage to match their real
18746 names, add the missing documentation for a couple of testing and
18747 directory authority options, remove the documentation for a
18748 V2-directory fetching option that no longer exists. Resolves
18750 - Correct the documentation so that it lists the correct directory
18751 for the stats files. (They are in a subdirectory called "stats",
18753 - In the manpage, move more authority-only options into the
18754 directory authority section so that operators of regular directory
18755 caches don't get confused.
18758 - The contrib directory has been sorted and tidied. Before, it was
18759 an unsorted dumping ground for useful and not-so-useful things.
18760 Now, it is divided based on functionality, and the items which
18761 seemed to be nonfunctional or useless have been removed. Resolves
18762 ticket 8966; based on patches from "rl1987".
18765 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
18766 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
18767 - The TunnelDirConns and PreferTunnelledDirConns options no longer
18768 exist; tunneled directory connections have been available since
18769 0.1.2.5-alpha, and turning them off is not a good idea. This is a
18770 brute-force fix for 10849, where "TunnelDirConns 0" would break
18774 Changes in version 0.2.4.22 - 2014-05-16
18775 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
18776 alpha release series. These include blocking all authority signing
18777 keys that may have been affected by the OpenSSL "heartbleed" bug,
18778 choosing a far more secure set of TLS ciphersuites by default, closing
18779 a couple of memory leaks that could be used to run a target relay out
18780 of RAM, and several others.
18782 o Major features (security, backport from 0.2.5.4-alpha):
18783 - Block authority signing keys that were used on authorities
18784 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18785 don't have any evidence that these keys _were_ compromised; we're
18786 doing this to be prudent.) Resolves ticket 11464.
18788 o Major bugfixes (security, OOM):
18789 - Fix a memory leak that could occur if a microdescriptor parse
18790 fails during the tokenizing step. This bug could enable a memory
18791 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18794 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
18795 - The relay ciphersuite list is now generated automatically based on
18796 uniform criteria, and includes all OpenSSL ciphersuites with
18797 acceptable strength and forward secrecy. Previously, we had left
18798 some perfectly fine ciphersuites unsupported due to omission or
18799 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18800 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18801 - Relays now trust themselves to have a better view than clients of
18802 which TLS ciphersuites are better than others. (Thanks to bug
18803 11513, the relay list is now well-considered, whereas the client
18804 list has been chosen mainly for anti-fingerprinting purposes.)
18805 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18806 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18807 AES128. Resolves ticket 11528.
18808 - Clients now try to advertise the same list of ciphersuites as
18809 Firefox 28. This change enables selection of (fast) GCM
18810 ciphersuites, disables some strange old ciphers, and stops
18811 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18812 Resolves ticket 11438.
18814 o Minor bugfixes (configuration, security):
18815 - When running a hidden service, do not allow TunneledDirConns 0:
18816 trying to set that option together with a hidden service would
18817 otherwise prevent the hidden service from running, and also make
18818 it publish its descriptors directly over HTTP. Fixes bug 10849;
18819 bugfix on 0.2.1.1-alpha.
18821 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
18822 - Avoid sending a garbage value to the controller when a circuit is
18823 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18825 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
18826 - Stop leaking memory when we successfully resolve a PTR record.
18827 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18829 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
18830 - Avoid 60-second delays in the bootstrapping process when Tor is
18831 launching for a second time while using bridges. Fixes bug 9229;
18832 bugfix on 0.2.0.3-alpha.
18834 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
18835 - Give the correct URL in the warning message when trying to run a
18836 relay on an ancient version of Windows. Fixes bug 9393.
18838 o Minor bugfixes (compilation):
18839 - Fix a compilation error when compiling with --disable-curve25519.
18840 Fixes bug 9700; bugfix on 0.2.4.17-rc.
18843 - Downgrade the warning severity for the the "md was still
18844 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
18845 for trying to diagnose this bug, and the current warning in
18846 earlier versions of tor achieves nothing useful. Addresses warning
18849 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
18850 - When we run out of usable circuit IDs on a channel, log only one
18851 warning for the whole channel, and describe how many circuits
18852 there were on the channel. Fixes part of ticket 11553.
18854 o Minor features (security, backport from 0.2.5.4-alpha):
18855 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
18856 leave the default at 8GBytes), to better support Raspberry Pi
18857 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
18859 o Documentation (backport from 0.2.5.4-alpha):
18860 - Correctly document that we search for a system torrc file before
18861 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18865 Changes in version 0.2.5.4-alpha - 2014-04-25
18866 Tor 0.2.5.4-alpha includes several security and performance
18867 improvements for clients and relays, including blacklisting authority
18868 signing keys that were used while susceptible to the OpenSSL
18869 "heartbleed" bug, fixing two expensive functions on busy relays,
18870 improved TLS ciphersuite preference lists, support for run-time
18871 hardening on compilers that support AddressSanitizer, and more work on
18872 the Linux sandbox code.
18874 There are also several usability fixes for clients (especially clients
18875 that use bridges), two new TransPort protocols supported (one on
18876 OpenBSD, one on FreeBSD), and various other bugfixes.
18878 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
18879 have accumulated many known flaws; everyone should upgrade.
18881 o Major features (security):
18882 - If you don't specify MaxMemInQueues yourself, Tor now tries to
18883 pick a good value based on your total system memory. Previously,
18884 the default was always 8 GB. You can still override the default by
18885 setting MaxMemInQueues yourself. Resolves ticket 11396.
18886 - Block authority signing keys that were used on authorities
18887 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18888 don't have any evidence that these keys _were_ compromised; we're
18889 doing this to be prudent.) Resolves ticket 11464.
18891 o Major features (relay performance):
18892 - Speed up server-side lookups of rendezvous and introduction point
18893 circuits by using hashtables instead of linear searches. These
18894 functions previously accounted between 3 and 7% of CPU usage on
18895 some busy relays. Resolves ticket 9841.
18896 - Avoid wasting CPU when extending a circuit over a channel that is
18897 nearly out of circuit IDs. Previously, we would do a linear scan
18898 over possible circuit IDs before finding one or deciding that we
18899 had exhausted our possibilities. Now, we try at most 64 random
18900 circuit IDs before deciding that we probably won't succeed. Fixes
18901 a possible root cause of ticket 11553.
18903 o Major features (seccomp2 sandbox, Linux only):
18904 - The seccomp2 sandbox can now run a test network for multiple hours
18905 without crashing. The sandbox is still experimental, and more bugs
18906 will probably turn up. To try it, enable "Sandbox 1" on a Linux
18907 host. Resolves ticket 11351.
18908 - Strengthen sandbox code: the sandbox can now test the arguments
18909 for rename(), and blocks _sysctl() entirely. Resolves another part
18911 - When the sandbox blocks a system call, it now tries to log a stack
18912 trace before exiting. Resolves ticket 11465.
18914 o Major bugfixes (TLS cipher selection):
18915 - The relay ciphersuite list is now generated automatically based on
18916 uniform criteria, and includes all OpenSSL ciphersuites with
18917 acceptable strength and forward secrecy. Previously, we had left
18918 some perfectly fine ciphersuites unsupported due to omission or
18919 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18920 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18921 - Relays now trust themselves to have a better view than clients of
18922 which TLS ciphersuites are better than others. (Thanks to bug
18923 11513, the relay list is now well-considered, whereas the client
18924 list has been chosen mainly for anti-fingerprinting purposes.)
18925 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18926 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18927 AES128. Resolves ticket 11528.
18928 - Clients now try to advertise the same list of ciphersuites as
18929 Firefox 28. This change enables selection of (fast) GCM
18930 ciphersuites, disables some strange old ciphers, and stops
18931 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18932 Resolves ticket 11438.
18934 o Major bugfixes (bridge client):
18935 - Avoid 60-second delays in the bootstrapping process when Tor is
18936 launching for a second time while using bridges. Fixes bug 9229;
18937 bugfix on 0.2.0.3-alpha.
18939 o Minor features (transparent proxy, *BSD):
18940 - Support FreeBSD's ipfw firewall interface for TransPort ports on
18941 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
18942 10267; patch from "yurivict".
18943 - Support OpenBSD's divert-to rules with the pf firewall for
18944 transparent proxy ports. To enable it, set "TransProxyType
18945 pf-divert". This allows Tor to run a TransPort transparent proxy
18946 port on OpenBSD 4.4 or later without root privileges. See the
18947 pf.conf(5) manual page for information on configuring pf to use
18948 divert-to rules. Closes ticket 10896; patch from Dana Koch.
18950 o Minor features (security):
18951 - New --enable-expensive-hardening option to enable security
18952 hardening options that consume nontrivial amounts of CPU and
18953 memory. Right now, this includes AddressSanitizer and UbSan, which
18954 are supported in newer versions of GCC and Clang. Closes ticket
18957 o Minor features (log verbosity):
18958 - Demote the message that we give when a flushing connection times
18959 out for too long from NOTICE to INFO. It was usually meaningless.
18960 Resolves ticket 5286.
18961 - Don't log so many notice-level bootstrapping messages at startup
18962 about downloading descriptors. Previously, we'd log a notice
18963 whenever we learned about more routers. Now, we only log a notice
18964 at every 5% of progress. Fixes bug 9963.
18965 - Warn less verbosely when receiving a malformed
18966 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
18967 - When we run out of usable circuit IDs on a channel, log only one
18968 warning for the whole channel, and describe how many circuits
18969 there were on the channel. Fixes part of ticket 11553.
18971 o Minor features (relay):
18972 - If a circuit timed out for at least 3 minutes, check if we have a
18973 new external IP address, and publish a new descriptor with the new
18974 IP address if it changed. Resolves ticket 2454.
18976 o Minor features (controller):
18977 - Make the entire exit policy available from the control port via
18978 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
18980 - Because of the fix for ticket 11396, the real limit for memory
18981 usage may no longer match the configured MaxMemInQueues value. The
18982 real limit is now exposed via GETINFO limits/max-mem-in-queues.
18984 o Minor features (bridge client):
18985 - Report a more useful failure message when we can't connect to a
18986 bridge because we don't have the right pluggable transport
18987 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
18989 o Minor features (diagnostic):
18990 - Add more log messages to diagnose bug 7164, which causes
18991 intermittent "microdesc_free() called but md was still referenced"
18992 warnings. We now include more information, to figure out why we
18993 might be cleaning a microdescriptor for being too old if it's
18994 still referenced by a live node_t object.
18996 o Minor bugfixes (client, DNSPort):
18997 - When using DNSPort, try to respond to AAAA requests with AAAA
18998 answers. Previously, we hadn't looked at the request type when
18999 deciding which answer type to prefer. Fixes bug 10468; bugfix on
19001 - When receiving a DNS query for an unsupported record type, reply
19002 with no answer rather than with a NOTIMPL error. This behavior
19003 isn't correct either, but it will break fewer client programs, we
19004 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
19007 o Minor bugfixes (exit relay):
19008 - Stop leaking memory when we successfully resolve a PTR record.
19009 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
19011 o Minor bugfixes (bridge client):
19012 - Stop accepting bridge lines containing hostnames. Doing so would
19013 cause clients to perform DNS requests on the hostnames, which was
19014 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
19015 - Avoid a 60-second delay in the bootstrapping process when a Tor
19016 client with pluggable transports re-reads its configuration at
19017 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
19019 o Minor bugfixes (client, logging during bootstrap):
19020 - Warn only once if we start logging in an unsafe way. Previously,
19021 we complain as many times as we had problems. Fixes bug 9870;
19022 bugfix on 0.2.5.1-alpha.
19023 - Only report the first fatal bootstrap error on a given OR
19024 connection. This stops us from telling the controller bogus error
19025 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
19026 - Be more helpful when trying to run sandboxed on Linux without
19027 libseccomp. Instead of saying "Sandbox is not implemented on this
19028 platform", we now explain that we need to be built with
19029 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
19030 - Avoid generating spurious warnings when starting with
19031 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
19034 o Minor bugfixes (closing OR connections):
19035 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
19036 check if it's an or_connection_t and correctly call
19037 connection_or_close_for_error() rather than
19038 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
19040 - When closing all connections on setting DisableNetwork to 1, use
19041 connection_or_close_normally() rather than closing OR connections
19042 out from under the channel layer. Fixes bug 11306; bugfix on
19045 o Minor bugfixes (controller):
19046 - Avoid sending a garbage value to the controller when a circuit is
19047 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
19049 o Minor bugfixes (tor-fw-helper):
19050 - Allow tor-fw-helper to build again by adding src/ext to its
19051 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
19053 o Minor bugfixes (bridges):
19054 - Avoid potential crashes or bad behavior when launching a
19055 server-side managed proxy with ORPort or ExtORPort temporarily
19056 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
19058 o Minor bugfixes (platform-specific):
19059 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
19060 bug 11426; bugfix on 0.2.5.3-alpha.
19061 - When dumping a malformed directory object to disk, save it in
19062 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
19064 - Don't report failures from make_socket_reuseable() on incoming
19065 sockets on OSX: this can happen when incoming connections close
19066 early. Fixes bug 10081.
19068 o Minor bugfixes (trivial memory leaks):
19069 - Fix a small memory leak when signing a directory object. Fixes bug
19070 11275; bugfix on 0.2.4.13-alpha.
19071 - Free placeholder entries in our circuit table at exit; fixes a
19072 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
19073 - Don't re-initialize a second set of OpenSSL mutexes when starting
19074 up. Previously, we'd make one set of mutexes, and then immediately
19075 replace them with another. Fixes bug 11726; bugfix on
19077 - Resolve some memory leaks found by coverity in the unit tests, on
19078 exit in tor-gencert, and on a failure to compute digests for our
19079 own keys when generating a v3 networkstatus vote. These leaks
19080 should never have affected anyone in practice.
19082 o Minor bugfixes (hidden service):
19083 - Only retry attempts to connect to a chosen rendezvous point 8
19084 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
19086 o Minor bugfixes (misc code correctness):
19087 - Fix various instances of undefined behavior in channeltls.c,
19088 tor_memmem(), and eventdns.c that would cause us to construct
19089 pointers to memory outside an allocated object. (These invalid
19090 pointers were not accessed, but C does not even allow them to
19091 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
19092 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
19093 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
19094 fix some miscellaneous errors in our tests and codebase. Fixes bug
19095 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
19096 - Always check return values for unlink, munmap, UnmapViewOfFile;
19097 check strftime return values more often. In some cases all we can
19098 do is report a warning, but this may help prevent deeper bugs from
19099 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
19101 - Fix numerous warnings from the clang "scan-build" static analyzer.
19102 Some of these are programming style issues; some of them are false
19103 positives that indicated awkward code; some are undefined behavior
19104 cases related to constructing (but not using) invalid pointers;
19105 some are assumptions about API behavior; some are (harmlessly)
19106 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
19107 correct; and one or two are genuine bugs that weren't reachable
19108 from the rest of the program. Fixes bug 8793; bugfixes on many,
19112 - Build the torify.1 manpage again. Previously, we were only trying
19113 to build it when also building tor-fw-helper. That's why we didn't
19114 notice that we'd broken the ability to build it. Fixes bug 11321;
19115 bugfix on 0.2.5.1-alpha.
19116 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
19117 11061; bugfix on 0.2.4.7-alpha.
19118 - Correctly document that we search for a system torrc file before
19119 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
19121 - Resolve warnings from Doxygen.
19123 o Code simplifications and refactoring:
19124 - Remove is_internal_IP() function. Resolves ticket 4645.
19125 - Remove unused function circuit_dump_by_chan from circuitlist.c.
19126 Closes issue 9107; patch from "marek".
19127 - Change our use of the ENUM_BF macro to avoid declarations that
19130 o Deprecated versions:
19131 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
19132 attention for some while. Directory authorities no longer accept
19133 descriptors from relays running any version of Tor prior to Tor
19134 0.2.3.16-alpha. Resolves ticket 11149.
19137 - New macros in test.h to simplify writing mock-functions for unit
19138 tests. Part of ticket 11507. Patch from Dana Koch.
19139 - Complete tests for the status.c module. Resolves ticket 11507.
19140 Patch from Dana Koch.
19143 - Remove all code for the long unused v1 directory protocol.
19144 Resolves ticket 11070.
19147 Changes in version 0.2.5.3-alpha - 2014-03-22
19148 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
19149 two new anti-DoS features for Tor relays, resolves a bug that kept
19150 SOCKS5 support for IPv6 from working, fixes several annoying usability
19151 issues for bridge users, and removes more old code for unused
19154 The Tor 0.2.5.x release series is now in patch-freeze: no feature
19155 patches not already written will be considered for inclusion in 0.2.5.x.
19157 o Major features (relay security, DoS-resistance):
19158 - When deciding whether we have run out of memory and we need to
19159 close circuits, also consider memory allocated in buffers for
19160 streams attached to each circuit.
19162 This change, which extends an anti-DoS feature introduced in
19163 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
19164 better resist more memory-based DoS attacks than before. Since the
19165 MaxMemInCellQueues option now applies to all queues, it is renamed
19166 to MaxMemInQueues. This feature fixes bug 10169.
19167 - Avoid hash-flooding denial-of-service attacks by using the secure
19168 SipHash-2-4 hash function for our hashtables. Without this
19169 feature, an attacker could degrade performance of a targeted
19170 client or server by flooding their data structures with a large
19171 number of entries to be stored at the same hash table position,
19172 thereby slowing down the Tor instance. With this feature, hash
19173 table positions are derived from a randomized cryptographic key,
19174 and an attacker cannot predict which entries will collide. Closes
19176 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
19177 the default at 8GBytes), to better support Raspberry Pi users. Fixes
19178 bug 9686; bugfix on 0.2.4.14-alpha.
19180 o Minor features (bridges, pluggable transports):
19181 - Bridges now write the SHA1 digest of their identity key
19182 fingerprint (that is, a hash of a hash of their public key) to
19183 notice-level logs, and to a new hashed-fingerprint file. This
19184 information will help bridge operators look up their bridge in
19185 Globe and similar tools. Resolves ticket 10884.
19186 - Improve the message that Tor displays when running as a bridge
19187 using pluggable transports without an Extended ORPort listener.
19188 Also, log the message in the log file too. Resolves ticket 11043.
19190 o Minor features (other):
19191 - Add a new option, PredictedPortsRelevanceTime, to control how long
19192 after having received a request to connect to a given port Tor
19193 will try to keep circuits ready in anticipation of future requests
19194 for that port. Patch from "unixninja92"; implements ticket 9176.
19195 - Generate a warning if any ports are listed in the SocksPolicy,
19196 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
19197 AuthDirBadExit options. (These options only support address
19198 ranges.) Fixes part of ticket 11108.
19199 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
19202 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
19203 - Build without warnings under clang 3.4. (We have some macros that
19204 define static functions only some of which will get used later in
19205 the module. Starting with clang 3.4, these give a warning unless the
19206 unused attribute is set on them.) Resolves ticket 10904.
19207 - Fix build warnings about missing "a2x" comment when building the
19208 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19209 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19211 o Minor bugfixes (client):
19212 - Improve the log message when we can't connect to a hidden service
19213 because all of the hidden service directory nodes hosting its
19214 descriptor are excluded. Improves on our fix for bug 10722, which
19215 was a bugfix on 0.2.0.10-alpha.
19216 - Raise a control port warning when we fail to connect to all of
19217 our bridges. Previously, we didn't inform the controller, and
19218 the bootstrap process would stall. Fixes bug 11069; bugfix on
19220 - Exit immediately when a process-owning controller exits.
19221 Previously, tor relays would wait for a little while after their
19222 controller exited, as if they had gotten an INT signal -- but this
19223 was problematic, since there was no feedback for the user. To do a
19224 clean shutdown, controllers should send an INT signal and give Tor
19225 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
19226 - Stop attempting to connect to bridges before our pluggable
19227 transports are configured (harmless but resulted in some erroneous
19228 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
19229 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
19230 generating incorrect SOCKS5 responses, and confusing client
19231 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
19233 o Minor bugfixes (relays and bridges):
19234 - Avoid crashing on a malformed resolv.conf file when running a
19235 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
19236 - Non-exit relays no longer launch mock DNS requests to check for
19237 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
19238 non-exit relays stopped servicing DNS requests. Fixes bug 965;
19239 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
19240 - Bridges now report complete directory request statistics. Related
19241 to bug 5824; bugfix on 0.2.2.1-alpha.
19242 - Bridges now never collect statistics that were designed for
19243 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
19244 - Stop giving annoying warning messages when we decide not to launch
19245 a pluggable transport proxy that we don't need (because there are
19246 no bridges configured to use it). Resolves ticket 5018; bugfix
19248 - Give the correct URL in the warning message when trying to run a
19249 relay on an ancient version of Windows. Fixes bug 9393.
19251 o Minor bugfixes (backtrace support):
19252 - Support automatic backtraces on more platforms by using the
19253 "-fasynchronous-unwind-tables" compiler option. This option is
19254 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
19255 is on by default and table generation is not. This doesn't yet
19256 add Windows support; only Linux, OSX, and some BSDs are affected.
19257 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
19258 - Avoid strange behavior if two threads hit failed assertions at the
19259 same time and both try to log backtraces at once. (Previously, if
19260 this had happened, both threads would have stored their intermediate
19261 results in the same buffer, and generated junk outputs.) Reported by
19262 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
19263 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
19264 0.2.5.2-alpha; patch from Nick Hopper.
19266 o Minor bugfixes (unit tests):
19267 - Fix a small bug in the unit tests that might have made the tests
19268 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
19269 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
19272 - Remove all remaining code related to version-0 hidden service
19273 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
19274 the rest of bug 10841.
19277 - Document in the manpage that "KBytes" may also be written as
19278 "kilobytes" or "KB", that "Kbits" may also be written as
19279 "kilobits", and so forth. Closes ticket 9222.
19280 - Document that the ClientOnly config option overrides ORPort.
19281 Our old explanation made ClientOnly sound as though it did
19282 nothing at all. Resolves bug 9059.
19283 - Explain that SocksPolicy, DirPolicy, and similar options don't
19284 take port arguments. Fixes the other part of ticket 11108.
19285 - Fix a comment about the rend_server_descriptor_t.protocols field
19286 to more accurately describe its range. Also, make that field
19287 unsigned, to more accurately reflect its usage. Fixes bug 9099;
19288 bugfix on 0.2.1.5-alpha.
19289 - Fix the manpage's description of HiddenServiceAuthorizeClient:
19290 the maximum client name length is 16, not 19. Fixes bug 11118;
19291 bugfix on 0.2.1.6-alpha.
19293 o Code simplifications and refactoring:
19294 - Get rid of router->address, since in all cases it was just the
19295 string representation of router->addr. Resolves ticket 5528.
19297 o Test infrastructure:
19298 - Update to the latest version of tinytest.
19299 - Improve the tinytest implementation of string operation tests so
19300 that comparisons with NULL strings no longer crash the tests; they
19301 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
19304 Changes in version 0.2.4.21 - 2014-02-28
19305 Tor 0.2.4.21 further improves security against potential adversaries who
19306 find breaking 1024-bit crypto doable, and backports several stability
19307 and robustness patches from the 0.2.5 branch.
19309 o Major features (client security):
19310 - When we choose a path for a 3-hop circuit, make sure it contains
19311 at least one relay that supports the NTor circuit extension
19312 handshake. Otherwise, there is a chance that we're building
19313 a circuit that's worth attacking by an adversary who finds
19314 breaking 1024-bit crypto doable, and that chance changes the game
19315 theory. Implements ticket 9777.
19318 - Do not treat streams that fail with reason
19319 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
19320 since it could also indicate an ENETUNREACH connection error. Fixes
19321 part of bug 10777; bugfix on 0.2.4.8-alpha.
19323 o Code simplification and refactoring:
19324 - Remove data structures which were introduced to implement the
19325 CellStatistics option: they are now redundant with the new timestamp
19326 field in the regular packed_cell_t data structure, which we did
19327 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
19330 - Always clear OpenSSL bignums before freeing them -- even bignums
19331 that don't contain secrets. Resolves ticket 10793. Patch by
19333 - Build without warnings under clang 3.4. (We have some macros that
19334 define static functions only some of which will get used later in
19335 the module. Starting with clang 3.4, these give a warning unless the
19336 unused attribute is set on them.) Resolves ticket 10904.
19337 - Update geoip and geoip6 files to the February 7 2014 Maxmind
19338 GeoLite2 Country database.
19341 - Set the listen() backlog limit to the largest actually supported
19342 on the system, not to the value in a header file. Fixes bug 9716;
19343 bugfix on every released Tor.
19344 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19345 exit node as a NOROUTE error, not an INTERNAL error, since they
19346 can apparently happen when trying to connect to the wrong sort
19347 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19348 - Fix build warnings about missing "a2x" comment when building the
19349 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19350 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19351 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19352 not entirely remove it from the connection lists. Fixes bug 9602;
19353 bugfix on 0.2.4.4-alpha.
19354 - Fix a segmentation fault in our benchmark code when running with
19355 Fedora's OpenSSL package, or any other OpenSSL that provides
19356 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19357 - Turn "circuit handshake stats since last time" log messages into a
19358 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19360 o Documentation fixes:
19361 - Document that all but one DirPort entry must have the NoAdvertise
19362 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19365 Changes in version 0.2.5.2-alpha - 2014-02-13
19366 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
19367 like the "poor random number generation" fix and the "building too many
19368 circuits" fix. It also further improves security against potential
19369 adversaries who find breaking 1024-bit crypto doable, and launches
19370 pluggable transports on demand (which gets us closer to integrating
19371 pluggable transport support by default -- not to be confused with Tor
19372 bundles enabling pluggable transports and bridges by default).
19374 o Major features (client security):
19375 - When we choose a path for a 3-hop circuit, make sure it contains
19376 at least one relay that supports the NTor circuit extension
19377 handshake. Otherwise, there is a chance that we're building
19378 a circuit that's worth attacking by an adversary who finds
19379 breaking 1024-bit crypto doable, and that chance changes the game
19380 theory. Implements ticket 9777.
19381 - Clients now look at the "usecreatefast" consensus parameter to
19382 decide whether to use CREATE_FAST or CREATE cells for the first hop
19383 of their circuit. This approach can improve security on connections
19384 where Tor's circuit handshake is stronger than the available TLS
19385 connection security levels, but the tradeoff is more computational
19386 load on guard relays. Implements proposal 221. Resolves ticket 9386.
19388 o Major features (bridges):
19389 - Don't launch pluggable transport proxies if we don't have any
19390 bridges configured that would use them. Now we can list many
19391 pluggable transports, and Tor will dynamically start one when it
19392 hears a bridge address that needs it. Resolves ticket 5018.
19393 - The bridge directory authority now assigns status flags (Stable,
19394 Guard, etc) to bridges based on thresholds calculated over all
19395 Running bridges. Now bridgedb can finally make use of its features
19396 to e.g. include at least one Stable bridge in its answers. Fixes
19399 o Major features (other):
19400 - Extend ORCONN controller event to include an "ID" parameter,
19401 and add four new controller event types CONN_BW, CIRC_BW,
19402 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
19403 The new events are emitted in private Tor networks only, with the
19404 goal of being able to better track performance and load during
19405 full-network simulations. Implements proposal 218 and ticket 7359.
19406 - On some platforms (currently: recent OSX versions, glibc-based
19407 platforms that support the ELF format, and a few other
19408 Unix-like operating systems), Tor can now dump stack traces
19409 when a crash occurs or an assertion fails. By default, traces
19410 are dumped to stderr (if possible) and to any logs that are
19411 reporting errors. Implements ticket 9299.
19414 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19415 not entirely remove it from the connection lists. Fixes bug 9602;
19416 bugfix on 0.2.4.4-alpha.
19417 - Do not treat streams that fail with reason
19418 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
19419 since it could also indicate an ENETUNREACH connection error. Fixes
19420 part of bug 10777; bugfix on 0.2.4.8-alpha.
19422 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
19423 - Do not allow OpenSSL engines to replace the PRNG, even when
19424 HardwareAccel is set. The only default builtin PRNG engine uses
19425 the Intel RDRAND instruction to replace the entire PRNG, and
19426 ignores all attempts to seed it with more entropy. That's
19427 cryptographically stupid: the right response to a new alleged
19428 entropy source is never to discard all previously used entropy
19429 sources. Fixes bug 10402; works around behavior introduced in
19430 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19432 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19433 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19434 - Avoid launching spurious extra circuits when a stream is pending.
19435 This fixes a bug where any circuit that _wasn't_ unusable for new
19436 streams would be treated as if it were, causing extra circuits to
19437 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19439 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19440 - No longer stop reading or writing on cpuworker connections when
19441 our rate limiting buckets go empty. Now we should handle circuit
19442 handshake requests more promptly. Resolves bug 9731.
19443 - Stop trying to bootstrap all our directory information from
19444 only our first guard. Discovered while fixing bug 9946; bugfix
19447 o Minor features (bridges, pluggable transports):
19448 - Add threshold cutoffs to the networkstatus document created by
19449 the Bridge Authority. Fixes bug 1117.
19450 - On Windows, spawn background processes using the CREATE_NO_WINDOW
19451 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
19452 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
19453 Vidalia set this option for us.) Implements ticket 10297.
19455 o Minor features (security):
19456 - Always clear OpenSSL bignums before freeing them -- even bignums
19457 that don't contain secrets. Resolves ticket 10793. Patch by
19460 o Minor features (config options and command line):
19461 - Add an --allow-missing-torrc commandline option that tells Tor to
19462 run even if the configuration file specified by -f is not available.
19463 Implements ticket 10060.
19464 - Add support for the TPROXY transparent proxying facility on Linux.
19465 See documentation for the new TransProxyType option for more
19466 details. Implementation by "thomo". Closes ticket 10582.
19468 o Minor features (controller):
19469 - Add a new "HS_DESC" controller event that reports activities
19470 related to hidden service descriptors. Resolves ticket 8510.
19471 - New "DROPGUARDS" controller command to forget all current entry
19472 guards. Not recommended for ordinary use, since replacing guards
19473 too frequently makes several attacks easier. Resolves ticket 9934;
19476 o Minor features (build):
19477 - Assume that a user using ./configure --host wants to cross-compile,
19478 and give an error if we cannot find a properly named
19479 tool-chain. Add a --disable-tool-name-check option to proceed
19480 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
19481 - If we run ./configure and the compiler recognizes -fstack-protector
19482 but the linker rejects it, warn the user about a potentially missing
19483 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
19485 o Minor features (testing):
19486 - If Python is installed, "make check" now runs extra tests beyond
19487 the unit test scripts.
19488 - When bootstrapping a test network, sometimes very few relays get
19489 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
19490 specify a set of relays which should be voted Guard regardless of
19491 their uptime or bandwidth. Addresses ticket 9206.
19493 o Minor features (log messages):
19494 - When ServerTransportPlugin is set on a bridge, Tor can write more
19495 useful statistics about bridge use in its extrainfo descriptors,
19496 but only if the Extended ORPort ("ExtORPort") is set too. Add a
19497 log message to inform the user in this case. Resolves ticket 9651.
19498 - When receiving a new controller connection, log the origin address.
19499 Resolves ticket 9698; patch from "sigpipe".
19500 - When logging OpenSSL engine status at startup, log the status of
19501 more engines. Fixes ticket 10043; patch from Joshua Datko.
19502 - Turn "circuit handshake stats since last time" log messages into a
19503 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19505 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19506 - Improve the circuit queue out-of-memory handler. Previously, when
19507 we ran low on memory, we'd close whichever circuits had the most
19508 queued cells. Now, we close those that have the *oldest* queued
19509 cells, on the theory that those are most responsible for us
19510 running low on memory. Based on analysis from a forthcoming paper
19511 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
19512 - Generate bootstrapping status update events correctly when fetching
19513 microdescriptors. Fixes bug 9927.
19514 - Update to the October 2 2013 Maxmind GeoLite Country database.
19516 o Minor bugfixes (clients):
19517 - When closing a channel that has already been open, do not close
19518 pending circuits that were waiting to connect to the same relay.
19519 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
19522 o Minor bugfixes (relays):
19523 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19524 exit node as a NOROUTE error, not an INTERNAL error, since they
19525 can apparently happen when trying to connect to the wrong sort
19526 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19528 o Minor bugfixes (bridges):
19529 - Fix a bug where the first connection works to a bridge that uses a
19530 pluggable transport with client-side parameters, but we don't send
19531 the client-side parameters on subsequent connections. (We don't
19532 use any pluggable transports with client-side parameters yet,
19533 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
19534 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
19536 o Minor bugfixes (node selection):
19537 - If ExcludeNodes is set, consider non-excluded hidden service
19538 directory servers before excluded ones. Do not consider excluded
19539 hidden service directory servers at all if StrictNodes is
19540 set. (Previously, we would sometimes decide to connect to those
19541 servers, and then realize before we initiated a connection that
19542 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
19543 Reported by "mr-4".
19544 - If we set the ExitNodes option but it doesn't include any nodes
19545 that have the Exit flag, we would choose not to bootstrap. Now we
19546 bootstrap so long as ExitNodes includes nodes which can exit to
19547 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
19549 o Minor bugfixes (controller and command-line):
19550 - If changing a config option via "setconf" fails in a recoverable
19551 way, we used to nonetheless write our new control ports to the
19552 file described by the "ControlPortWriteToFile" option. Now we only
19553 write out that file if we successfully switch to the new config
19554 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
19555 - When a command-line option such as --version or --help that
19556 ordinarily implies --hush appears on the command line along with
19557 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
19558 only if it appeared later on the command line. Fixes bug 9578;
19559 bugfix on 0.2.5.1-alpha.
19561 o Minor bugfixes (code correctness):
19562 - Previously we used two temporary files when writing descriptors to
19563 disk; now we only use one. Fixes bug 1376.
19564 - Remove an erroneous (but impossible and thus harmless) pointer
19565 comparison that would have allowed compilers to skip a bounds
19566 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
19567 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
19568 - Fix an always-true assertion in pluggable transports code so it
19569 actually checks what it was trying to check. Fixes bug 10046;
19570 bugfix on 0.2.3.9-alpha. Found by "dcb".
19572 o Minor bugfixes (protocol correctness):
19573 - When receiving a VERSIONS cell with an odd number of bytes, close
19574 the connection immediately since the cell is malformed. Fixes bug
19575 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
19578 o Minor bugfixes (build):
19579 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
19580 turned off (that is, without support for v2 link handshakes). Fixes
19581 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
19582 - Fix compilation warnings and startup issues when running with
19583 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
19585 - Fix compilation on Solaris 9, which didn't like us having an
19586 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
19588 o Minor bugfixes (testing):
19589 - Fix a segmentation fault in our benchmark code when running with
19590 Fedora's OpenSSL package, or any other OpenSSL that provides
19591 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19593 o Minor bugfixes (log messages):
19594 - Fix a bug where clients using bridges would report themselves
19595 as 50% bootstrapped even without a live consensus document.
19596 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
19597 - Suppress a warning where, if there's only one directory authority
19598 in the network, we would complain that votes and signatures cannot
19599 be uploaded to other directory authorities. Fixes bug 10842;
19600 bugfix on 0.2.2.26-beta.
19601 - Report bootstrapping progress correctly when we're downloading
19602 microdescriptors. We had updated our "do we have enough microdescs
19603 to begin building circuits?" logic most recently in 0.2.4.10-alpha
19604 (see bug 5956), but we left the bootstrap status event logic at
19605 "how far through getting 1/4 of them are we?" Fixes bug 9958;
19606 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
19608 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
19609 - Avoid a crash bug when starting with a corrupted microdescriptor
19610 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19611 - If we fail to dump a previously cached microdescriptor to disk, avoid
19612 freeing duplicate data later on. Fixes bug 10423; bugfix on
19613 0.2.4.13-alpha. Spotted by "bobnomnom".
19615 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19616 - Correctly log long IPv6 exit policies, instead of truncating them
19617 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
19618 - Our default TLS ecdhe groups were backwards: we meant to be using
19619 P224 for relays (for performance win) and P256 for bridges (since
19620 it is more common in the wild). Instead we had it backwards. After
19621 reconsideration, we decided that the default should be P256 on all
19622 hosts, since its security is probably better, and since P224 is
19623 reportedly used quite little in the wild. Found by "skruffy" on
19624 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
19625 - Free directory authority certificate download statuses on exit
19626 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
19628 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19629 - If the guard we choose first doesn't answer, we would try the
19630 second guard, but once we connected to the second guard we would
19631 abandon it and retry the first one, slowing down bootstrapping.
19632 The fix is to treat all our initially chosen guards as acceptable
19633 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19634 - Fix an assertion failure that would occur when disabling the
19635 ORPort setting on a running Tor process while accounting was
19636 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19637 - When examining the list of network interfaces to find our address,
19638 do not consider non-running or disabled network interfaces. Fixes
19639 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19640 - Avoid an off-by-one error when checking buffer boundaries when
19641 formatting the exit status of a pluggable transport helper.
19642 This is probably not an exploitable bug, but better safe than
19643 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19646 o Removed code and features:
19647 - Clients now reject any directory authority certificates lacking
19648 a dir-key-crosscert element. These have been included since
19649 0.2.1.9-alpha, so there's no real reason for them to be optional
19650 any longer. Completes proposal 157. Resolves ticket 10162.
19651 - Remove all code that existed to support the v2 directory system,
19652 since there are no longer any v2 directory authorities. Resolves
19654 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
19655 options, which were used for designating authorities as "Hidden
19656 service authorities". There has been no use of hidden service
19657 authorities since 0.2.2.1-alpha, when we stopped uploading or
19658 downloading v0 hidden service descriptors. Fixes bug 10881; also
19659 part of a fix for bug 10841.
19661 o Code simplification and refactoring:
19662 - Remove some old fallback code designed to keep Tor clients working
19663 in a network with only two working relays. Elsewhere in the code we
19664 have long since stopped supporting such networks, so there wasn't
19665 much point in keeping it around. Addresses ticket 9926.
19666 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
19667 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
19668 - Remove data structures which were introduced to implement the
19669 CellStatistics option: they are now redundant with the addition
19670 of a timestamp to the regular packed_cell_t data structure, which
19671 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
19674 o Documentation (man page) fixes:
19675 - Update manpage to describe some of the files you can expect to
19676 find in Tor's DataDirectory. Addresses ticket 9839.
19677 - Document that all but one DirPort entry must have the NoAdvertise
19678 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19680 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19681 - Clarify the usage and risks of setting the ContactInfo torrc line
19682 for your relay or bridge. Resolves ticket 9854.
19683 - Add anchors to the manpage so we can link to the html version of
19684 the documentation for specific options. Resolves ticket 9866.
19685 - Replace remaining references to DirServer in man page and
19686 log entries. Resolves ticket 10124.
19689 - Make the "tor-gencert" tool used by directory authority operators
19690 create 2048-bit signing keys by default (rather than 1024-bit, since
19691 1024-bit is uncomfortably small these days). Addresses ticket 10324.
19694 Changes in version 0.2.4.20 - 2013-12-22
19695 Tor 0.2.4.20 fixes potentially poor random number generation for users
19696 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
19697 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
19698 and 4) have no state file in their DataDirectory (as would happen on
19699 first start). Users who generated relay or hidden service identity
19700 keys in such a situation should discard them and generate new ones.
19702 This release also fixes a logic error that caused Tor clients to build
19703 many more preemptive circuits than they actually need.
19706 - Do not allow OpenSSL engines to replace the PRNG, even when
19707 HardwareAccel is set. The only default builtin PRNG engine uses
19708 the Intel RDRAND instruction to replace the entire PRNG, and
19709 ignores all attempts to seed it with more entropy. That's
19710 cryptographically stupid: the right response to a new alleged
19711 entropy source is never to discard all previously used entropy
19712 sources. Fixes bug 10402; works around behavior introduced in
19713 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19715 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19716 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19717 - Avoid launching spurious extra circuits when a stream is pending.
19718 This fixes a bug where any circuit that _wasn't_ unusable for new
19719 streams would be treated as if it were, causing extra circuits to
19720 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19723 - Avoid a crash bug when starting with a corrupted microdescriptor
19724 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19725 - If we fail to dump a previously cached microdescriptor to disk, avoid
19726 freeing duplicate data later on. Fixes bug 10423; bugfix on
19727 0.2.4.13-alpha. Spotted by "bobnomnom".
19730 Changes in version 0.2.4.19 - 2013-12-11
19731 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
19732 (1986-2013). Aaron worked on diverse projects including helping to guide
19733 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
19734 transparency to the U.S government's PACER documents, and contributing
19735 design and development for Tor and Tor2Web. Aaron was one of the latest
19736 martyrs in our collective fight for civil liberties and human rights,
19737 and his death is all the more painful because he was one of us.
19739 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
19740 a new circuit handshake and link encryption that use ECC to provide
19741 better security and efficiency; makes relays better manage circuit
19742 creation requests; uses "directory guards" to reduce client enumeration
19743 risks; makes bridges collect and report statistics about the pluggable
19744 transports they support; cleans up and improves our geoip database;
19745 gets much closer to IPv6 support for clients, bridges, and relays; makes
19746 directory authorities use measured bandwidths rather than advertised
19747 ones when computing flags and thresholds; disables client-side DNS
19748 caching to reduce tracking risks; and fixes a big bug in bridge
19749 reachability testing. This release introduces two new design
19750 abstractions in the code: a new "channel" abstraction between circuits
19751 and or_connections to allow for implementing alternate relay-to-relay
19752 transports, and a new "circuitmux" abstraction storing the queue of
19753 circuits for a channel. The release also includes many stability,
19754 security, and privacy fixes.
19757 Changes in version 0.2.4.18-rc - 2013-11-16
19758 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
19759 series. It takes a variety of fixes from the 0.2.5.x branch to improve
19760 stability, performance, and better handling of edge cases.
19763 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19764 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19765 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19766 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19767 them to solve bug 6033.)
19770 - No longer stop reading or writing on cpuworker connections when
19771 our rate limiting buckets go empty. Now we should handle circuit
19772 handshake requests more promptly. Resolves bug 9731.
19773 - If we are unable to save a microdescriptor to the journal, do not
19774 drop it from memory and then reattempt downloading it. Fixes bug
19775 9645; bugfix on 0.2.2.6-alpha.
19776 - Stop trying to bootstrap all our directory information from
19777 only our first guard. Discovered while fixing bug 9946; bugfix
19779 - The new channel code sometimes lost track of in-progress circuits,
19780 causing long-running clients to stop building new circuits. The
19781 fix is to always call circuit_n_chan_done(chan, 0) from
19782 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
19784 o Minor bugfixes (on 0.2.4.x):
19785 - Correctly log long IPv6 exit policies, instead of truncating them
19786 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
19787 - Our default TLS ecdhe groups were backwards: we meant to be using
19788 P224 for relays (for performance win) and P256 for bridges (since
19789 it is more common in the wild). Instead we had it backwards. After
19790 reconsideration, we decided that the default should be P256 on all
19791 hosts, since its security is probably better, and since P224 is
19792 reportedly used quite little in the wild. Found by "skruffy" on
19793 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
19794 - Free directory authority certificate download statuses on exit
19795 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
19797 o Minor bugfixes (on 0.2.3.x and earlier):
19798 - If the guard we choose first doesn't answer, we would try the
19799 second guard, but once we connected to the second guard we would
19800 abandon it and retry the first one, slowing down bootstrapping.
19801 The fix is to treat all our initially chosen guards as acceptable
19802 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19803 - Fix an assertion failure that would occur when disabling the
19804 ORPort setting on a running Tor process while accounting was
19805 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19806 - When examining the list of network interfaces to find our address,
19807 do not consider non-running or disabled network interfaces. Fixes
19808 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19809 - Avoid an off-by-one error when checking buffer boundaries when
19810 formatting the exit status of a pluggable transport helper.
19811 This is probably not an exploitable bug, but better safe than
19812 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19815 o Minor features (protecting client timestamps):
19816 - Clients no longer send timestamps in their NETINFO cells. These were
19817 not used for anything, and they provided one small way for clients
19818 to be distinguished from each other as they moved from network to
19819 network or behind NAT. Implements part of proposal 222.
19820 - Clients now round timestamps in INTRODUCE cells down to the nearest
19821 10 minutes. If a new Support022HiddenServices option is set to 0, or
19822 if it's set to "auto" and the feature is disabled in the consensus,
19823 the timestamp is sent as 0 instead. Implements part of proposal 222.
19824 - Stop sending timestamps in AUTHENTICATE cells. This is not such
19825 a big deal from a security point of view, but it achieves no actual
19826 good purpose, and isn't needed. Implements part of proposal 222.
19827 - Reduce down accuracy of timestamps in hidden service descriptors.
19828 Implements part of proposal 222.
19830 o Minor features (other):
19831 - Improve the circuit queue out-of-memory handler. Previously, when
19832 we ran low on memory, we'd close whichever circuits had the most
19833 queued cells. Now, we close those that have the *oldest* queued
19834 cells, on the theory that those are most responsible for us
19835 running low on memory. Based on analysis from a forthcoming paper
19836 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
19837 - Generate bootstrapping status update events correctly when fetching
19838 microdescriptors. Fixes bug 9927.
19839 - Update to the October 2 2013 Maxmind GeoLite Country database.
19841 o Documentation fixes:
19842 - Clarify the usage and risks of setting the ContactInfo torrc line
19843 for your relay or bridge. Resolves ticket 9854.
19844 - Add anchors to the manpage so we can link to the html version of
19845 the documentation for specific options. Resolves ticket 9866.
19846 - Replace remaining references to DirServer in man page and
19847 log entries. Resolves ticket 10124.
19850 Changes in version 0.2.5.1-alpha - 2013-10-02
19851 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
19852 on Linux, allows bridges that offer pluggable transports to report usage
19853 statistics, fixes many issues to make testing easier, and provides
19854 a pile of minor features and bugfixes that have been waiting for a
19855 release of the new branch.
19857 This is the first alpha release in a new series, so expect there to
19858 be bugs. Users who would rather test out a more stable branch should
19859 stay with 0.2.4.x for now.
19861 o Major features (security):
19862 - Use the seccomp2 syscall filtering facility on Linux to limit
19863 which system calls Tor can invoke. This is an experimental,
19864 Linux-only feature to provide defense-in-depth against unknown
19865 attacks. To try turning it on, set "Sandbox 1" in your torrc
19866 file. Please be ready to report bugs. We hope to add support
19867 for better sandboxing in the future, including more fine-grained
19868 filters, better division of responsibility, and support for more
19869 platforms. This work has been done by Cristian-Matei Toader for
19870 Google Summer of Code.
19871 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19872 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19873 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19874 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19875 them to solve bug 6033.)
19877 o Major features (other):
19878 - Add support for passing arguments to managed pluggable transport
19879 proxies. Implements ticket 3594.
19880 - Bridges now track GeoIP information and the number of their users
19881 even when pluggable transports are in use, and report usage
19882 statistics in their extra-info descriptors. Resolves tickets 4773
19884 - Make testing Tor networks bootstrap better: lower directory fetch
19885 retry schedules and maximum interval without directory requests,
19886 and raise maximum download tries. Implements ticket 6752.
19887 - Add make target 'test-network' to run tests on a Chutney network.
19888 Implements ticket 8530.
19889 - The ntor handshake is now on-by-default, no matter what the
19890 directory authorities recommend. Implements ticket 8561.
19893 - Instead of writing destroy cells directly to outgoing connection
19894 buffers, queue them and intersperse them with other outgoing cells.
19895 This can prevent a set of resource starvation conditions where too
19896 many pending destroy cells prevent data cells from actually getting
19897 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
19898 bugfix on 0.2.0.1-alpha.
19899 - If we are unable to save a microdescriptor to the journal, do not
19900 drop it from memory and then reattempt downloading it. Fixes bug
19901 9645; bugfix on 0.2.2.6-alpha.
19902 - The new channel code sometimes lost track of in-progress circuits,
19903 causing long-running clients to stop building new circuits. The
19904 fix is to always call circuit_n_chan_done(chan, 0) from
19905 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
19908 - Tor now builds each source file in two modes: a mode that avoids
19909 exposing identifiers needlessly, and another mode that exposes
19910 more identifiers for testing. This lets the compiler do better at
19911 optimizing the production code, while enabling us to take more
19912 radical measures to let the unit tests test things.
19913 - The production builds no longer include functions used only in
19914 the unit tests; all functions exposed from a module only for
19915 unit-testing are now static in production builds.
19916 - Add an --enable-coverage configuration option to make the unit
19917 tests (and a new src/or/tor-cov target) to build with gcov test
19921 - We now have rudimentary function mocking support that our unit
19922 tests can use to test functions in isolation. Function mocking
19923 lets the tests temporarily replace a function's dependencies with
19924 stub functions, so that the tests can check the function without
19925 invoking the other functions it calls.
19926 - Add more unit tests for the <circid,channel>->circuit map, and
19927 the destroy-cell-tracking code to fix bug 7912.
19928 - Unit tests for failing cases of the TAP onion handshake.
19929 - More unit tests for address-manipulation functions.
19931 o Minor features (protecting client timestamps):
19932 - Clients no longer send timestamps in their NETINFO cells. These were
19933 not used for anything, and they provided one small way for clients
19934 to be distinguished from each other as they moved from network to
19935 network or behind NAT. Implements part of proposal 222.
19936 - Clients now round timestamps in INTRODUCE cells down to the nearest
19937 10 minutes. If a new Support022HiddenServices option is set to 0, or
19938 if it's set to "auto" and the feature is disabled in the consensus,
19939 the timestamp is sent as 0 instead. Implements part of proposal 222.
19940 - Stop sending timestamps in AUTHENTICATE cells. This is not such
19941 a big deal from a security point of view, but it achieves no actual
19942 good purpose, and isn't needed. Implements part of proposal 222.
19943 - Reduce down accuracy of timestamps in hidden service descriptors.
19944 Implements part of proposal 222.
19946 o Minor features (config options):
19947 - Config (torrc) lines now handle fingerprints which are missing
19948 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
19949 - Support a --dump-config option to print some or all of the
19950 configured options. Mainly useful for debugging the command-line
19951 option parsing code. Helps resolve ticket 4647.
19952 - Raise awareness of safer logging: notify user of potentially
19953 unsafe config options, like logging more verbosely than severity
19954 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
19955 - Add a new configuration option TestingV3AuthVotingStartOffset
19956 that bootstraps a network faster by changing the timing for
19957 consensus votes. Addresses ticket 8532.
19958 - Add a new torrc option "ServerTransportOptions" that allows
19959 bridge operators to pass configuration parameters to their
19960 pluggable transports. Resolves ticket 8929.
19961 - The config (torrc) file now accepts bandwidth and space limits in
19962 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
19963 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
19966 o Minor features (build):
19967 - Add support for `--library-versions` flag. Implements ticket 6384.
19968 - Return the "unexpected sendme" warnings to a warn severity, but make
19969 them rate limited, to help diagnose ticket 8093.
19970 - Detect a missing asciidoc, and warn the user about it, during
19971 configure rather than at build time. Fixes issue 6506. Patch from
19974 o Minor features (other):
19975 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
19976 sockets in a single system call. Implements ticket 5129.
19977 - Log current accounting state (bytes sent and received + remaining
19978 time for the current accounting period) in the relay's heartbeat
19979 message. Implements ticket 5526; patch from Peter Retzlaff.
19980 - Implement the TRANSPORT_LAUNCHED control port event that
19981 notifies controllers about new launched pluggable
19982 transports. Resolves ticket 5609.
19983 - If we're using the pure-C 32-bit curve25519_donna implementation
19984 of curve25519, build it with the -fomit-frame-pointer option to
19985 make it go faster on register-starved hosts. This improves our
19986 handshake performance by about 6% on i386 hosts without nacl.
19987 Closes ticket 8109.
19988 - Update to the September 4 2013 Maxmind GeoLite Country database.
19991 - Set the listen() backlog limit to the largest actually supported
19992 on the system, not to the value in a header file. Fixes bug 9716;
19993 bugfix on every released Tor.
19994 - No longer accept malformed http headers when parsing urls from
19995 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
19996 bugfix on 0.0.6pre1.
19997 - In munge_extrainfo_into_routerinfo(), check the return value of
19998 memchr(). This would have been a serious issue if we ever passed
19999 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
20001 - On the chance that somebody manages to build Tor on a
20002 platform where time_t is unsigned, correct the way that
20003 microdesc_add_to_cache() handles negative time arguments.
20004 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
20005 - Reject relative control socket paths and emit a warning. Previously,
20006 single-component control socket paths would be rejected, but Tor
20007 would not log why it could not validate the config. Fixes bug 9258;
20008 bugfix on 0.2.3.16-alpha.
20010 o Minor bugfixes (command line):
20011 - Use a single command-line parser for parsing torrc options on the
20012 command line and for finding special command-line options to avoid
20013 inconsistent behavior for torrc option arguments that have the same
20014 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
20016 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
20017 9573; bugfix on 0.0.9pre5.
20019 o Minor fixes (build, auxiliary programs):
20020 - Stop preprocessing the "torify" script with autoconf, since
20021 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
20023 - The tor-fw-helper program now follows the standard convention and
20024 exits with status code "0" on success. Fixes bug 9030; bugfix on
20025 0.2.3.1-alpha. Patch by Arlo Breault.
20026 - Corrected ./configure advice for what openssl dev package you should
20027 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
20029 o Minor code improvements:
20030 - Remove constants and tests for PKCS1 padding; it's insecure and
20031 shouldn't be used for anything new. Fixes bug 8792; patch
20033 - Remove instances of strcpy() from the unit tests. They weren't
20034 hurting anything, since they were only in the unit tests, but it's
20035 embarrassing to have strcpy() in the code at all, and some analysis
20036 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
20037 0.2.3.8-alpha. Patch from Arlo Breault.
20039 o Removed features:
20040 - Remove migration code from when we renamed the "cached-routers"
20041 file to "cached-descriptors" back in 0.2.0.8-alpha. This
20042 incidentally resolves ticket 6502 by cleaning up the related code
20043 a bit. Patch from Akshay Hebbar.
20045 o Code simplification and refactoring:
20046 - Extract the common duplicated code for creating a subdirectory
20047 of the data directory and writing to a file in it. Fixes ticket
20048 4282; patch from Peter Retzlaff.
20049 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
20050 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
20051 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
20052 - Add a set of accessor functions for the circuit timeout data
20053 structure. Fixes ticket 6153; patch from "piet".
20054 - Clean up exit paths from connection_listener_new(). Closes ticket
20055 8789. Patch from Arlo Breault.
20056 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
20057 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
20058 - Use a doubly-linked list to implement the global circuit list.
20059 Resolves ticket 9108. Patch from Marek Majkowski.
20060 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
20063 Changes in version 0.2.4.17-rc - 2013-09-05
20064 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
20065 series. It adds an emergency step to help us tolerate the massive
20066 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
20067 circuit-level handshakes now effectively jump the queue compared to
20068 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
20069 big bug hindering bridge reachability tests.
20072 - Relays now process the new "NTor" circuit-level handshake requests
20073 with higher priority than the old "TAP" circuit-level handshake
20074 requests. We still process some TAP requests to not totally starve
20075 0.2.3 clients when NTor becomes popular. A new consensus parameter
20076 "NumNTorsPerTAP" lets us tune the balance later if we need to.
20077 Implements ticket 9574.
20080 - If the circuit build timeout logic is disabled (via the consensus,
20081 or because we are an authority), then don't build testing circuits.
20082 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
20083 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
20084 previously they did not, which prevented them from receiving
20085 successful connections from relays for self-test or bandwidth
20086 testing. Also, when a relay is extending a circuit to a bridge,
20087 it needs to send a NETINFO cell, even when the bridge hasn't sent
20088 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
20089 - If the time to download the next old-style networkstatus is in
20090 the future, do not decline to consider whether to download the
20091 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
20095 - Avoid double-closing the listener socket in our socketpair()
20096 replacement (used on Windows) in the case where the addresses on
20097 our opened sockets don't match what we expected. Fixes bug 9400;
20098 bugfix on 0.0.2pre7. Found by Coverity.
20100 o Minor fixes (config options):
20101 - Avoid overflows when the user sets MaxCircuitDirtiness to a
20102 ridiculously high value, by imposing a (ridiculously high) 30-day
20103 maximum on MaxCircuitDirtiness.
20104 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
20105 message is logged at notice, not at info.
20106 - Warn and fail if a server is configured not to advertise any
20107 ORPorts at all. (We need *something* to put in our descriptor,
20108 or we just won't work.)
20111 - Track how many "TAP" and "NTor" circuit handshake requests we get,
20112 and how many we complete, and log it every hour to help relay
20113 operators follow trends in network load. Addresses ticket 9658.
20114 - Update to the August 7 2013 Maxmind GeoLite Country database.
20117 Changes in version 0.2.4.16-rc - 2013-08-10
20118 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
20119 series. It fixes several crash bugs in the 0.2.4 branch.
20122 - Fix a bug in the voting algorithm that could yield incorrect results
20123 when a non-naming authority declared too many flags. Fixes bug 9200;
20124 bugfix on 0.2.0.3-alpha.
20125 - Fix an uninitialized read that could in some cases lead to a remote
20126 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
20127 Anybody running a hidden service on the experimental 0.2.4.x
20128 branch should upgrade. (This is, so far as we know, unrelated to
20130 - Avoid an assertion failure when processing DNS replies without the
20131 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
20132 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
20133 0.2.4.15-rc. Found by stem integration tests.
20136 - Fix an invalid memory read that occurred when a pluggable
20137 transport proxy failed its configuration protocol.
20138 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
20139 - When evaluating whether to use a connection that we haven't
20140 decided is canonical using a recent link protocol version,
20141 decide that it's canonical only if it used address _does_
20142 match the desired address. Fixes bug 9309; bugfix on
20143 0.2.4.4-alpha. Reported by skruffy.
20144 - Make the default behavior of NumDirectoryGuards be to track
20145 NumEntryGuards. Now a user who changes only NumEntryGuards will get
20146 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
20147 - Fix a spurious compilation warning with some older versions of
20148 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
20151 - Update to the July 3 2013 Maxmind GeoLite Country database.
20154 Changes in version 0.2.4.15-rc - 2013-07-01
20155 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
20156 series. It fixes a few smaller bugs, but generally appears stable.
20157 Please test it and let us know whether it is!
20160 - When receiving a new configuration file via the control port's
20161 LOADCONF command, do not treat the defaults file as absent.
20162 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
20165 - Issue a warning when running with the bufferevents backend enabled.
20166 It's still not stable, and people should know that they're likely
20167 to hit unexpected problems. Closes ticket 9147.
20170 Changes in version 0.2.4.14-alpha - 2013-06-18
20171 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
20172 present in 0.2.4.13-alpha.
20175 - When we have too much memory queued in circuits (according to a new
20176 MaxMemInCellQueues option), close the circuits consuming the most
20177 memory. This prevents us from running out of memory as a relay if
20178 circuits fill up faster than they can be drained. Fixes bug 9063;
20179 bugfix on the 54th commit of Tor. This bug is a further fix beyond
20180 bug 6252, whose fix was merged into 0.2.3.21-rc.
20182 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
20183 where we tried to solve this issue simply by imposing an upper limit
20184 on the number of queued cells for a single circuit. That approach
20185 proved to be problematic, since there are ways to provoke clients to
20186 send a number of cells in excess of any such reasonable limit. Fixes
20187 bug 9072; bugfix on 0.2.4.13-alpha.
20189 - Limit hidden service descriptors to at most ten introduction
20190 points, to slow one kind of guard enumeration. Fixes bug 9002;
20191 bugfix on 0.1.1.11-alpha.
20194 Changes in version 0.2.4.13-alpha - 2013-06-14
20195 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
20196 vulnerabilities, makes socks5 username/password circuit isolation
20197 actually actually work (this time for sure!), and cleans up a bunch
20198 of other issues in preparation for a release candidate.
20200 o Major bugfixes (robustness):
20201 - Close any circuit that has too many cells queued on it. Fixes
20202 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
20203 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
20204 - Prevent the get_freelists() function from running off the end of
20205 the list of freelists if it somehow gets an unrecognized
20206 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
20208 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
20209 when an exit connection with optimistic data succeeds immediately
20210 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
20212 - Fix a directory authority crash bug when building a consensus
20213 using an older consensus as its basis. Fixes bug 8833. Bugfix
20217 - Avoid a memory leak where we would leak a consensus body when we
20218 find that a consensus which we couldn't previously verify due to
20219 missing certificates is now verifiable. Fixes bug 8719; bugfix
20221 - We used to always request authority certificates by identity digest,
20222 meaning we'd get the newest one even when we wanted one with a
20223 different signing key. Then we would complain about being given
20224 a certificate we already had, and never get the one we really
20225 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
20226 resource to request the one we want. Fixes bug 5595; bugfix on
20228 - Follow the socks5 protocol when offering username/password
20229 authentication. The fix for bug 8117 exposed this bug, and it
20230 turns out real-world applications like Pidgin do care. Bugfix on
20231 0.2.3.2-alpha; fixes bug 8879.
20232 - Prevent failures on Windows Vista and later when rebuilding the
20233 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
20234 bugfix on 0.2.4.12-alpha.
20237 - Fix an impossible buffer overrun in the AES unit tests. Fixes
20238 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
20239 - If for some reason we fail to write a microdescriptor while
20240 rebuilding the cache, do not let the annotations from that
20241 microdescriptor linger in the cache file, and do not let the
20242 microdescriptor stay recorded as present in its old location.
20243 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
20244 - Fix a memory leak that would occur whenever a configuration
20245 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
20246 - Paste the description for PathBias parameters from the man
20247 page into or.h, so the code documents them too. Fixes bug 7982;
20248 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
20249 - Relays now treat a changed IPv6 ORPort as sufficient reason to
20250 publish an updated descriptor. Fixes bug 6026; bugfix on
20252 - When launching a resolve request on behalf of an AF_UNIX control
20253 socket, omit the address field of the new entry connection, used in
20254 subsequent controller events, rather than letting tor_dup_addr()
20255 set it to "<unknown address type>". Fixes bug 8639; bugfix on
20258 o Minor bugfixes (log messages):
20259 - Fix a scaling issue in the path bias accounting code that
20260 resulted in "Bug:" log messages from either
20261 pathbias_scale_close_rates() or pathbias_count_build_success().
20262 This represents a bugfix on a previous bugfix: the original fix
20263 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
20265 - Give a less useless error message when the user asks for an IPv4
20266 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
20270 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
20271 to tolerate bug 8093 for now.
20272 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
20273 in directory authority votes to describe whether they have enough
20274 measured bandwidths to ignore advertised (relay descriptor)
20275 bandwidth claims. Resolves ticket 8711.
20276 - Update to the June 5 2013 Maxmind GeoLite Country database.
20278 o Removed documentation:
20279 - Remove some of the older contents of doc/ as obsolete; move others
20280 to torspec.git. Fixes bug 8965.
20282 o Code simplification and refactoring:
20283 - Avoid using character buffers when constructing most directory
20284 objects: this approach was unwieldy and error-prone. Instead,
20285 build smartlists of strings, and concatenate them when done.
20288 Changes in version 0.2.4.12-alpha - 2013-04-18
20289 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
20290 process for lengthening the guard rotation period, makes directory
20291 authority opinions in the consensus a bit less gameable, makes socks5
20292 username/password circuit isolation actually work, and fixes a wide
20293 variety of other issues.
20296 - Raise the default time that a client keeps an entry guard from
20297 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
20298 2012 paper. (We would make it even longer, but we need better client
20299 load balancing first.) Also, make the guard lifetime controllable
20300 via a new GuardLifetime torrc option and a GuardLifetime consensus
20301 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
20302 - Directory authorities now prefer using measured bandwidths to
20303 advertised ones when computing flags and thresholds. Resolves
20305 - Directory authorities that have more than a threshold number
20306 of relays with measured bandwidths now treat relays with unmeasured
20307 bandwidths as having bandwidth 0. Resolves ticket 8435.
20309 o Major bugfixes (assert / resource use):
20310 - Avoid a bug where our response to TLS renegotiation under certain
20311 network conditions could lead to a busy-loop, with 100% CPU
20312 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
20313 - Avoid an assertion when we discover that we'd like to write a cell
20314 onto a closing connection: just discard the cell. Fixes another
20315 case of bug 7350; bugfix on 0.2.4.4-alpha.
20317 o Major bugfixes (client-side privacy):
20318 - When we mark a circuit as unusable for new circuits, have it
20319 continue to be unusable for new circuits even if MaxCircuitDirtiness
20320 is increased too much at the wrong time, or the system clock jumps
20321 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
20322 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
20323 which have resolved to internal addresses") is set, apply that
20324 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
20325 - When an exit relay rejects a stream with reason "exit policy", but
20326 we only know an exit policy summary (e.g. from the microdesc
20327 consensus) for it, do not mark the relay as useless for all exiting.
20328 Instead, mark just the circuit as unsuitable for that particular
20329 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
20330 - Allow applications to get proper stream isolation with
20331 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
20332 username/password authentication also offer "no authentication". Tor
20333 had previously preferred "no authentication", so the applications
20334 never actually sent Tor their auth details. Now Tor selects
20335 username/password authentication if it's offered. You can disable
20336 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
20337 bug 8117; bugfix on 0.2.3.3-alpha.
20339 o Major bugfixes (other):
20340 - When unable to find any working directory nodes to use as a
20341 directory guard, give up rather than adding the same non-working
20342 nodes to the directory guard list over and over. Fixes bug 8231;
20343 bugfix on 0.2.4.8-alpha.
20346 - Reject as invalid most directory objects containing a NUL.
20347 Belt-and-suspender fix for bug 8037.
20348 - In our testsuite, create temporary directories with a bit more
20349 entropy in their name to make name collisions less likely. Fixes
20351 - Add CACHED keyword to ADDRMAP events in the control protocol
20352 to indicate whether a DNS result will be cached or not. Resolves
20354 - Update to the April 3 2013 Maxmind GeoLite Country database.
20356 o Minor features (build):
20357 - Detect and reject attempts to build Tor with threading support
20358 when OpenSSL has been compiled without threading support.
20360 - Clarify that when autoconf is checking for nacl, it is checking
20361 specifically for nacl with a fast curve25519 implementation.
20363 - Warn if building on a platform with an unsigned time_t: there
20364 are too many places where Tor currently assumes that time_t can
20365 hold negative values. We'd like to fix them all, but probably
20368 o Minor bugfixes (build):
20369 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
20370 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
20371 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
20372 - Add the old src/or/micro-revision.i filename to CLEANFILES.
20373 On the off chance that somebody has one, it will go away as soon
20374 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
20375 - Build Tor correctly on 32-bit platforms where the compiler can build
20376 but not run code using the "uint128_t" construction. Fixes bug 8587;
20377 bugfix on 0.2.4.8-alpha.
20378 - Fix compilation warning with some versions of clang that would
20379 prefer the -Wswitch-enum compiler flag to warn about switch
20380 statements with missing enum values, even if those switch
20381 statements have a "default:" statement. Fixes bug 8598; bugfix
20384 o Minor bugfixes (protocol):
20385 - Fix the handling of a TRUNCATE cell when it arrives while the
20386 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
20387 - Fix a misframing issue when reading the version numbers in a
20388 VERSIONS cell. Previously we would recognize [00 01 00 02] as
20389 'version 1, version 2, and version 0x100', when it should have
20390 only included versions 1 and 2. Fixes bug 8059; bugfix on
20391 0.2.0.10-alpha. Reported pseudonymously.
20392 - Make the format and order of STREAM events for DNS lookups
20393 consistent among the various ways to launch DNS lookups. Fixes
20394 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
20395 - Correct our check for which versions of Tor support the EXTEND2
20396 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
20397 later, when support was really added in version 0.2.4.8-alpha.
20398 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
20400 o Minor bugfixes (other):
20401 - Correctly store microdescriptors and extrainfo descriptors with
20402 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
20403 Bug reported by "cypherpunks".
20404 - Increase the width of the field used to remember a connection's
20405 link protocol version to two bytes. Harmless for now, since the
20406 only currently recognized versions are one byte long. Reported
20407 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
20408 - If the state file's path bias counts are invalid (presumably from a
20409 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
20410 additional checks and log messages to the scaling of Path Bias
20411 counts, in case there still are remaining issues with scaling.
20412 Should help resolve bug 8235.
20413 - Eliminate several instances where we use "Nickname=ID" to refer to
20414 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
20415 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
20416 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
20418 o Minor bugfixes (syscalls):
20419 - Always check the return values of functions fcntl() and
20420 setsockopt(). We don't believe these are ever actually failing in
20421 practice, but better safe than sorry. Also, checking these return
20422 values should please analysis tools like Coverity. Patch from
20423 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
20424 - Use direct writes rather than stdio when building microdescriptor
20425 caches, in an attempt to mitigate bug 8031, or at least make it
20428 o Minor bugfixes (config):
20429 - When rejecting a configuration because we were unable to parse a
20430 quoted string, log an actual error message. Fixes bug 7950; bugfix
20432 - Behave correctly when the user disables LearnCircuitBuildTimeout
20433 but doesn't tell us what they would like the timeout to be. Fixes
20434 bug 6304; bugfix on 0.2.2.14-alpha.
20435 - When autodetecting the number of CPUs, use the number of available
20436 CPUs in preference to the number of configured CPUs. Inform the
20437 user if this reduces the number of available CPUs. Fixes bug 8002;
20438 bugfix on 0.2.3.1-alpha.
20439 - Make it an error when you set EntryNodes but disable UseGuardNodes,
20440 since it will (surprisingly to some users) ignore EntryNodes. Fixes
20441 bug 8180; bugfix on 0.2.3.11-alpha.
20442 - Allow TestingTorNetworks to override the 4096-byte minimum for
20443 the Fast threshold. Otherwise they can't bootstrap until they've
20444 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
20445 - Fix some logic errors when the user manually overrides the
20446 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
20449 o Minor bugfixes (log messages to help diagnose bugs):
20450 - If we fail to free a microdescriptor because of bug 7164, log
20451 the filename and line number from which we tried to free it.
20452 - Add another diagnostic to the heartbeat message: track and log
20453 overhead that TLS is adding to the data we write. If this is
20454 high, we are sending too little data to SSL_write at a time.
20455 Diagnostic for bug 7707.
20456 - Add more detail to a log message about relaxed timeouts, to help
20458 - Warn more aggressively when flushing microdescriptors to a
20459 microdescriptor cache fails, in an attempt to mitigate bug 8031,
20460 or at least make it more diagnosable.
20461 - Improve debugging output to help track down bug 8185 ("Bug:
20462 outgoing relay cell has n_chan==NULL. Dropping.")
20463 - Log the purpose of a path-bias testing circuit correctly.
20464 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
20466 o Minor bugfixes (0.2.4.x log messages that were too noisy):
20467 - Don't attempt to relax the timeout of already opened 1-hop circuits.
20468 They might never timeout. This should eliminate some/all cases of
20469 the relaxed timeout log message.
20470 - Use circuit creation time for network liveness evaluation. This
20471 should eliminate warning log messages about liveness caused
20472 by changes in timeout evaluation. Fixes bug 6572; bugfix on
20474 - Reduce a path bias length check from notice to info. The message
20475 is triggered when creating controller circuits. Fixes bug 8196;
20476 bugfix on 0.2.4.8-alpha.
20477 - Fix a path state issue that triggered a notice during relay startup.
20478 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
20479 - Reduce occurrences of warns about circuit purpose in
20480 connection_ap_expire_building(). Fixes bug 8477; bugfix on
20483 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
20484 - If we encounter a write failure on a SOCKS connection before we
20485 finish our SOCKS handshake, don't warn that we closed the
20486 connection before we could send a SOCKS reply. Fixes bug 8427;
20487 bugfix on 0.1.0.1-rc.
20488 - Correctly recognize that [::1] is a loopback address. Fixes
20489 bug 8377; bugfix on 0.2.1.3-alpha.
20490 - Fix a directory authority warn caused when we have a large amount
20491 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
20492 - Don't log inappropriate heartbeat messages when hibernating: a
20493 hibernating node is _expected_ to drop out of the consensus,
20494 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
20495 bugfix on 0.2.3.1-alpha.
20496 - Don't complain about bootstrapping problems while hibernating.
20497 These complaints reflect a general code problem, but not one
20498 with any problematic effects (no connections are actually
20499 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
20501 o Documentation fixes:
20502 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
20503 names match. Fixes bug 7768.
20504 - Make the torify manpage no longer refer to tsocks; torify hasn't
20505 supported tsocks since 0.2.3.14-alpha.
20506 - Make the tor manpage no longer reference tsocks.
20507 - Fix the GeoIPExcludeUnknown documentation to refer to
20508 ExcludeExitNodes rather than the currently nonexistent
20509 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
20512 - The tor-tsocks.conf is no longer distributed or installed. We
20513 recommend that tsocks users use torsocks instead. Resolves
20517 Changes in version 0.2.4.11-alpha - 2013-03-11
20518 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
20519 more robust, makes hidden service authentication work again, and
20520 resolves a DPI fingerprint for Tor's SSL transport.
20522 o Major features (directory authorities):
20523 - Directory authorities now support a new consensus method (17)
20524 where they cap the published bandwidth of servers for which
20525 insufficient bandwidth measurements exist. Fixes part of bug 2286.
20526 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
20527 serve any v2 directory information. Now we can test disabling the
20528 old deprecated v2 directory format, and see whether doing so has
20529 any effect on network load. Begins to fix bug 6783.
20530 - Directory authorities now include inside each vote a statement of
20531 the performance thresholds they used when assigning flags.
20532 Implements ticket 8151.
20534 o Major bugfixes (directory authorities):
20535 - Stop marking every relay as having been down for one hour every
20536 time we restart a directory authority. These artificial downtimes
20537 were messing with our Stable and Guard flag calculations. Fixes
20538 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
20540 o Major bugfixes (hidden services):
20541 - Allow hidden service authentication to succeed again. When we
20542 refactored the hidden service introduction code back
20543 in 0.2.4.1-alpha, we didn't update the code that checks
20544 whether authentication information is present, causing all
20545 authentication checks to return "false". Fix for bug 8207; bugfix
20546 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
20548 o Minor features (relays, bridges):
20549 - Make bridge relays check once a minute for whether their IP
20550 address has changed, rather than only every 15 minutes. Resolves
20551 bugs 1913 and 1992.
20552 - Refactor resolve_my_address() so it returns the method by which we
20553 decided our public IP address (explicitly configured, resolved from
20554 explicit hostname, guessed from interfaces, learned by gethostname).
20555 Now we can provide more helpful log messages when a relay guesses
20556 its IP address incorrectly (e.g. due to unexpected lines in
20557 /etc/hosts). Resolves ticket 2267.
20558 - Teach bridge-using clients to avoid 0.2.2 bridges when making
20559 microdescriptor-related dir requests, and only fall back to normal
20560 descriptors if none of their bridges can handle microdescriptors
20561 (as opposed to the fix in ticket 4013, which caused them to fall
20562 back to normal descriptors if *any* of their bridges preferred
20563 them). Resolves ticket 4994.
20564 - Randomize the lifetime of our SSL link certificate, so censors can't
20565 use the static value for filtering Tor flows. Resolves ticket 8443;
20566 related to ticket 4014 which was included in 0.2.2.33.
20567 - Support a new version of the link protocol that allows 4-byte circuit
20568 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
20569 a possible resource exhaustion issue. Closes ticket 7351; implements
20572 o Minor features (portability):
20573 - Tweak the curve25519-donna*.c implementations to tolerate systems
20574 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
20575 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
20576 the signs of types during autoconf. This is better than our old
20577 approach, which didn't work when cross-compiling.
20578 - Detect the sign of enum values, rather than assuming that MSC is the
20579 only compiler where enum types are all signed. Fixes bug 7727;
20580 bugfix on 0.2.4.10-alpha.
20582 o Minor features (other):
20583 - Say "KBytes" rather than "KB" in the man page (for various values
20584 of K), to further reduce confusion about whether Tor counts in
20585 units of memory or fractions of units of memory. Resolves ticket 7054.
20586 - Clear the high bit on curve25519 public keys before passing them to
20587 our backend, in case we ever wind up using a backend that doesn't do
20588 so itself. If we used such a backend, and *didn't* clear the high bit,
20589 we could wind up in a situation where users with such backends would
20590 be distinguishable from users without. Fixes bug 8121; bugfix on
20592 - Update to the March 6 2013 Maxmind GeoLite Country database.
20594 o Minor bugfixes (clients):
20595 - When we receive a RELAY_END cell with the reason DONE, or with no
20596 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
20597 status as "connection refused". Previously we reported these cases
20598 as success but then immediately closed the connection. Fixes bug
20599 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
20600 - Downgrade an assertion in connection_ap_expire_beginning to an
20601 LD_BUG message. The fix for bug 8024 should prevent this message
20602 from displaying, but just in case, a warn that we can diagnose
20603 is better than more assert crashes. Fixes bug 8065; bugfix on
20605 - Lower path use bias thresholds to .80 for notice and .60 for warn.
20606 Also make the rate limiting flags for the path use bias log messages
20607 independent from the original path bias flags. Fixes bug 8161;
20608 bugfix on 0.2.4.10-alpha.
20610 o Minor bugfixes (relays):
20611 - Stop trying to resolve our hostname so often (e.g. every time we
20612 think about doing a directory fetch). Now we reuse the cached
20613 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
20614 and 2410 (bugfix on 0.1.2.2-alpha).
20615 - Stop sending a stray "(null)" in some cases for the server status
20616 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
20618 - When choosing which stream on a formerly stalled circuit to wake
20619 first, make better use of the platform's weak RNG. Previously,
20620 we had been using the % ("modulo") operator to try to generate a
20621 1/N chance of picking each stream, but this behaves badly with
20622 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
20624 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
20625 Irix's random() only return 15 bits; Solaris's random() returns more
20626 bits but its RAND_MAX says it only returns 15, and so on. Motivated
20627 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
20629 o Minor bugfixes (directory authorities):
20630 - Directory authorities now use less space when formatting identical
20631 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
20634 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
20635 - Avoid leaking memory if we fail to compute a consensus signature
20636 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
20637 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
20639 - Fix a memory leak during safe-cookie controller authentication.
20640 Bugfix on 0.2.3.13-alpha.
20641 - Avoid memory leak of IPv6 policy content if we fail to format it into
20642 a router descriptor. Bugfix on 0.2.4.7-alpha.
20644 o Minor bugfixes (other code correctness issues):
20645 - Avoid a crash if we fail to generate an extrainfo descriptor.
20646 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
20647 this is CID 718634.
20648 - When detecting the largest possible file descriptor (in order to
20649 close all file descriptors when launching a new program), actually
20650 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
20651 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
20653 - Fix a copy-and-paste error when adding a missing A1 to a routerset
20654 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
20655 Bugfix on 0.2.4.10-alpha.
20656 - Fix an impossible-to-trigger integer overflow when estimating how
20657 long our onionskin queue would take. (This overflow would require us
20658 to accept 4 million onionskins before processing 100 of them.) Fixes
20659 bug 8210; bugfix on 0.2.4.10-alpha.
20661 o Code simplification and refactoring:
20662 - Add a wrapper function for the common "log a message with a
20666 Changes in version 0.2.4.10-alpha - 2013-02-04
20667 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
20668 certain attacks that flood the network with relays; changes the queue
20669 for circuit create requests from a sized-based limit to a time-based
20670 limit; resumes building with MSVC on Windows; and fixes a wide variety
20673 o Major bugfixes (directory authority):
20674 - When computing directory thresholds, ignore any rejected-as-sybil
20675 nodes during the computation so that they can't influence Fast,
20676 Guard, etc. (We should have done this for proposal 109.) Fixes
20678 - When marking a node as a likely sybil, reset its uptime metrics
20679 to zero, so that it cannot time towards getting marked as Guard,
20680 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
20684 - When a TLS write is partially successful but incomplete, remember
20685 that the flushed part has been flushed, and notice that bytes were
20686 actually written. Reported and fixed pseudonymously. Fixes bug
20687 7708; bugfix on Tor 0.1.0.5-rc.
20688 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
20689 ID: these could be used to create unexpected streams and circuits
20690 which would count as "present" to some parts of Tor but "absent"
20691 to others, leading to zombie circuits and streams or to a bandwidth
20692 denial-of-service. Fixes bug 7889; bugfix on every released version
20693 of Tor. Reported by "oftc_must_be_destroyed".
20694 - Rename all macros in our local copy of queue.h to begin with "TOR_".
20695 This change seems the only good way to permanently prevent conflicts
20696 with queue.h on various operating systems. Fixes bug 8107; bugfix
20699 o Major features (relay):
20700 - Instead of limiting the number of queued onionskins (aka circuit
20701 create requests) to a fixed, hard-to-configure number, we limit
20702 the size of the queue based on how many we expect to be able to
20703 process in a given amount of time. We estimate the time it will
20704 take to process an onionskin based on average processing time
20705 of previous onionskins. Closes ticket 7291. You'll never have to
20706 configure MaxOnionsPending again.
20708 o Major features (portability):
20709 - Resume building correctly with MSVC and Makefile.nmake. This patch
20710 resolves numerous bugs and fixes reported by ultramage, including
20711 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
20712 - Make the ntor and curve25519 code build correctly with MSVC.
20713 Fix on 0.2.4.8-alpha.
20716 - When directory authorities are computing thresholds for flags,
20717 never let the threshold for the Fast flag fall below 4096
20718 bytes. Also, do not consider nodes with extremely low bandwidths
20719 when deciding thresholds for various directory flags. This change
20720 should raise our threshold for Fast relays, possibly in turn
20721 improving overall network performance; see ticket 1854. Resolves
20723 - The Tor client now ignores sub-domain components of a .onion
20724 address. This change makes HTTP "virtual" hosting
20725 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
20726 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
20727 hosted on the same hidden service. Implements proposal 204.
20728 - We compute the overhead from passing onionskins back and forth to
20729 cpuworkers, and report it when dumping statistics in response to
20730 SIGUSR1. Supports ticket 7291.
20732 o Minor features (path selection):
20733 - When deciding whether we have enough descriptors to build circuits,
20734 instead of looking at raw relay counts, look at which fraction
20735 of (bandwidth-weighted) paths we're able to build. This approach
20736 keeps clients from building circuits if their paths are likely to
20737 stand out statistically. The default fraction of paths needed is
20738 taken from the consensus directory; you can override it with the
20739 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
20740 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
20741 and we have GeoIP information, also exclude all nodes with unknown
20742 countries "??" and "A1". This behavior is controlled by the
20743 new GeoIPExcludeUnknown option: you can make such nodes always
20744 excluded with "GeoIPExcludeUnknown 1", and disable the feature
20745 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
20746 gets you the default behavior. Implements feature 7706.
20747 - Path Use Bias: Perform separate accounting for successful circuit
20748 use. Keep separate statistics on stream attempt rates versus stream
20749 success rates for each guard. Provide configurable thresholds to
20750 determine when to emit log messages or disable use of guards that
20751 fail too many stream attempts. Resolves ticket 7802.
20753 o Minor features (log messages):
20754 - When learning a fingerprint for a bridge, log its corresponding
20755 transport type. Implements ticket 7896.
20756 - Improve the log message when "Bug/attack: unexpected sendme cell
20757 from client" occurs, to help us track bug 8093.
20760 - Remove a couple of extraneous semicolons that were upsetting the
20761 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
20762 bugfix on 0.2.2.1-alpha.
20763 - Remove a source of rounding error during path bias count scaling;
20764 don't count cannibalized circuits as used for path bias until we
20765 actually try to use them; and fix a circuit_package_relay_cell()
20766 warning message about n_chan==NULL. Fixes bug 7802.
20767 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
20768 actually link against nacl when we're configured to use it. Fixes
20769 bug 7972; bugfix on 0.2.4.8-alpha.
20770 - Compile correctly with the --disable-curve25519 option. Fixes
20771 bug 8153; bugfix on 0.2.4.8-alpha.
20773 o Build improvements:
20774 - Do not report status verbosely from autogen.sh unless the -v flag
20775 is specified. Fixes issue 4664. Patch from Onizuka.
20776 - Replace all calls to snprintf() outside of src/ext with
20777 tor_snprintf(). Also remove the #define to replace snprintf with
20778 _snprintf on Windows; they have different semantics, and all of
20779 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
20780 - Try to detect if we are ever building on a platform where
20781 memset(...,0,...) does not set the value of a double to 0.0. Such
20782 platforms are permitted by the C standard, though in practice
20783 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
20784 currently support them, but it's better to detect them and fail
20785 than to perform erroneously.
20787 o Removed features:
20788 - Stop exporting estimates of v2 and v3 directory traffic shares
20789 in extrainfo documents. They were unneeded and sometimes inaccurate.
20790 Also stop exporting any v2 directory request statistics. Resolves
20792 - Drop support for detecting and warning about versions of Libevent
20793 before 1.3e. Nothing reasonable ships with them any longer;
20794 warning the user about them shouldn't be needed. Resolves ticket
20797 o Code simplifications and refactoring:
20798 - Rename "isin" functions to "contains", for grammar. Resolves
20800 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
20801 with the natural logarithm function from the system libm. Resolves
20805 Changes in version 0.2.4.9-alpha - 2013-01-15
20806 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
20807 work more robustly.
20810 - Fix backward compatibility logic when receiving an embedded ntor
20811 handshake tunneled in a CREATE cell. This clears up the "Bug:
20812 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
20816 Changes in version 0.2.4.8-alpha - 2013-01-14
20817 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
20818 risks, adds a new stronger and faster circuit handshake, and offers
20819 stronger and faster link encryption when both sides support it.
20822 - Preliminary support for directory guards (proposal 207): when
20823 possible, clients now use their entry guards for non-anonymous
20824 directory requests. This can help prevent client enumeration. Note
20825 that this behavior only works when we have a usable consensus
20826 directory, and when options about what to download are more or less
20827 standard. In the future we should re-bootstrap from our guards,
20828 rather than re-bootstrapping from the preconfigured list of
20829 directory sources that ships with Tor. Resolves ticket 6526.
20830 - Tor relays and clients now support a better CREATE/EXTEND cell
20831 format, allowing the sender to specify multiple address, identity,
20832 and handshake types. Implements Robert Ransom's proposal 200;
20833 closes ticket 7199.
20835 o Major features (new circuit handshake):
20836 - Tor now supports a new circuit extension handshake designed by Ian
20837 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
20838 circuit extension handshake, later called "TAP", was a bit slow
20839 (especially on the relay side), had a fragile security proof, and
20840 used weaker keys than we'd now prefer. The new circuit handshake
20841 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
20842 function, making it significantly more secure than the older
20843 handshake, and significantly faster. Tor can use one of two built-in
20844 pure-C curve25519-donna implementations by Adam Langley, or it
20845 can link against the "nacl" library for a tuned version if present.
20847 The built-in version is very fast for 64-bit systems when building
20848 with GCC. The built-in 32-bit version is still faster than the
20849 old TAP protocol, but using libnacl is better on most such hosts.
20851 Clients don't currently use this protocol by default, since
20852 comparatively few clients support it so far. To try it, set
20853 UseNTorHandshake to 1.
20855 Implements proposal 216; closes ticket 7202.
20857 o Major features (better link encryption):
20858 - Relays can now enable the ECDHE TLS ciphersuites when available
20859 and appropriate. These ciphersuites let us negotiate forward-secure
20860 TLS secret keys more safely and more efficiently than with our
20861 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
20862 public relays prefer the (faster) P224 group, and bridges prefer
20863 the (more common) P256 group; you can override this with the
20866 Enabling these ciphers was a little tricky, since for a long time,
20867 clients had been claiming to support them without actually doing
20868 so, in order to foil fingerprinting. But with the client-side
20869 implementation of proposal 198 in 0.2.3.17-beta, clients can now
20870 match the ciphers from recent Firefox versions *and* list the
20871 ciphers they actually mean, so relays can believe such clients
20872 when they advertise ECDHE support in their TLS ClientHello messages.
20874 This feature requires clients running 0.2.3.17-beta or later,
20875 and requires both sides to be running OpenSSL 1.0.0 or later
20876 with ECC support. OpenSSL 1.0.1, with the compile-time option
20877 "enable-ec_nistp_64_gcc_128", is highly recommended.
20879 Implements the relay side of proposal 198; closes ticket 7200.
20882 - Avoid crashing when, as a relay without IPv6-exit support, a
20883 client insists on getting an IPv6 address or nothing. Fixes bug
20884 7814; bugfix on 0.2.4.7-alpha.
20887 - Improve circuit build timeout handling for hidden services.
20888 In particular: adjust build timeouts more accurately depending
20889 upon the number of hop-RTTs that a particular circuit type
20890 undergoes. Additionally, launch intro circuits in parallel
20891 if they timeout, and take the first one to reply as valid.
20892 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
20893 separate error codes; or at least, don't break for that reason.
20894 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
20895 - Update to the January 2 2013 Maxmind GeoLite Country database.
20897 o Minor features (testing):
20898 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
20899 (P-256) Diffie-Hellman handshakes to src/or/bench.
20900 - Add benchmark functions to test onion handshake performance.
20902 o Minor features (path bias detection):
20903 - Alter the Path Bias log messages to be more descriptive in terms
20904 of reporting timeouts and other statistics.
20905 - Create three levels of Path Bias log messages, as opposed to just
20906 two. These are configurable via consensus as well as via the torrc
20907 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
20908 The default values are 0.70, 0.50, and 0.30 respectively.
20909 - Separate the log message levels from the decision to drop guards,
20910 which also is available via torrc option PathBiasDropGuards.
20911 PathBiasDropGuards still defaults to 0 (off).
20912 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
20913 in combination with PathBiasExtremeRate.
20914 - Increase the default values for PathBiasScaleThreshold and
20915 PathBiasCircThreshold from (200, 20) to (300, 150).
20916 - Add in circuit usage accounting to path bias. If we try to use a
20917 built circuit but fail for any reason, it counts as path bias.
20918 Certain classes of circuits where the adversary gets to pick your
20919 destination node are exempt from this accounting. Usage accounting
20920 can be specifically disabled via consensus parameter or torrc.
20921 - Convert all internal path bias state to double-precision floating
20922 point, to avoid roundoff error and other issues.
20923 - Only record path bias information for circuits that have completed
20924 *two* hops. Assuming end-to-end tagging is the attack vector, this
20925 makes us more resilient to ambient circuit failure without any
20926 detection capability loss.
20928 o Minor bugfixes (log messages):
20929 - Rate-limit the "No circuits are opened. Relaxed timeout for a
20930 circuit with channel state open..." message to once per hour to
20931 keep it from filling the notice logs. Mitigates bug 7799 but does
20932 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
20933 - Avoid spurious warnings when configuring multiple client ports of
20934 which only some are nonlocal. Previously, we had claimed that some
20935 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
20938 o Code simplifications and refactoring:
20939 - Get rid of a couple of harmless clang warnings, where we compared
20940 enums to ints. These warnings are newly introduced in clang 3.2.
20941 - Split the onion.c file into separate modules for the onion queue
20942 and the different handshakes it supports.
20943 - Remove the marshalling/unmarshalling code for sending requests to
20944 cpuworkers over a socket, and instead just send structs. The
20945 recipient will always be the same Tor binary as the sender, so
20946 any encoding is overkill.
20949 Changes in version 0.2.4.7-alpha - 2012-12-24
20950 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
20951 directory mirrors for more robust bootstrapping; fixes more issues where
20952 clients with changing network conditions refuse to make any circuits;
20953 adds initial support for exiting to IPv6 addresses; resumes being able
20954 to update our GeoIP database, and includes the geoip6 file this time;
20955 turns off the client-side DNS cache by default due to privacy risks;
20956 and fixes a variety of other issues.
20958 o Major features (client resilience):
20959 - Add a new "FallbackDir" torrc option to use when we can't use
20960 a directory mirror from the consensus (either because we lack a
20961 consensus, or because they're all down). Currently, all authorities
20962 are fallbacks by default, and there are no other default fallbacks,
20963 but that will change. This option will allow us to give clients a
20964 longer list of servers to try to get a consensus from when first
20965 connecting to the Tor network, and thereby reduce load on the
20966 directory authorities. Implements proposal 206, "Preconfigured
20967 directory sources for bootstrapping". We also removed the old
20968 "FallbackNetworkstatus" option, since we never got it working well
20969 enough to use it. Closes bug 572.
20970 - If we have no circuits open, use a relaxed timeout (the
20971 95-percentile cutoff) until a circuit succeeds. This heuristic
20972 should allow Tor to succeed at building circuits even when the
20973 network connection drastically changes. Should help with bug 3443.
20975 o Major features (IPv6):
20976 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
20977 connectivity, then set the IPv6Exit flag to 1. Also make sure your
20978 exit policy reads as you would like: the address * applies to all
20979 address families, whereas *4 is IPv4 address only, and *6 is IPv6
20980 addresses only. On the client side, you'll need to wait until the
20981 authorities have upgraded, wait for enough exits to support IPv6,
20982 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
20983 ticket 5547, implements proposal 117 as revised in proposal 208.
20985 We DO NOT recommend that clients with actual anonymity needs start
20986 using IPv6 over Tor yet, since not enough exits support it yet.
20988 o Major features (geoip database):
20989 - Maxmind began labelling Tor relays as being in country "A1",
20990 which breaks by-country node selection inside Tor. Now we use a
20991 script to replace "A1" ("Anonymous Proxy") entries in our geoip
20992 file with real country codes. This script fixes about 90% of "A1"
20993 entries automatically and uses manual country code assignments to
20994 fix the remaining 10%. See src/config/README.geoip for details.
20995 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
20996 Country database, as modified above.
20998 o Major bugfixes (client-side DNS):
20999 - Turn off the client-side DNS cache by default. Updating and using
21000 the DNS cache is now configurable on a per-client-port
21001 level. SOCKSPort, DNSPort, etc lines may now contain
21002 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
21003 cache these types of DNS answers when we receive them from an
21004 exit node in response to an application request on this port, and
21005 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
21006 cached DNS answers of these types, we shouldn't use them. It's
21007 potentially risky to use cached DNS answers at the client, since
21008 doing so can indicate to one exit what answers we've gotten
21009 for DNS lookups in the past. With IPv6, this becomes especially
21010 problematic. Using cached DNS answers for requests on the same
21011 circuit would present less linkability risk, since all traffic
21012 on a circuit is already linkable, but it would also provide
21013 little performance benefit: the exit node caches DNS replies
21014 too. Implements a simplified version of Proposal 205. Implements
21017 o Major bugfixes (other):
21018 - Alter circuit build timeout measurement to start at the point
21019 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
21020 initialization). This should make our timeout measurements more
21021 uniform. Previously, we were sometimes including ORconn setup time
21022 in our circuit build time measurements. Should resolve bug 3443.
21023 - Fix an assertion that could trigger in hibernate_go_dormant() when
21024 closing an or_connection_t: call channel_mark_for_close() rather
21025 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
21027 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
21028 7655; bugfix on 0.2.4.6-alpha.
21031 - Add a new torrc option "ServerTransportListenAddr" to let bridge
21032 operators select the address where their pluggable transports will
21033 listen for connections. Resolves ticket 7013.
21034 - Allow an optional $ before the node identity digest in the
21035 controller command GETINFO ns/id/<identity>, for consistency with
21036 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
21037 - Log packaged cell fullness as part of the heartbeat message.
21038 Diagnosis to try to determine the extent of bug 7743.
21040 o Minor features (IPv6):
21041 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
21042 prefer to hand out virtual IPv6 addresses, since there are more of
21043 them and we can't run out. To override this behavior and make IPv4
21044 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
21045 or DNSPort you're using for resolving. Implements ticket 7571.
21046 - AutomapHostsOnResolve responses are now randomized, to avoid
21047 annoying situations where Tor is restarted and applications
21048 connect to the wrong addresses.
21049 - Never try more than 1000 times to pick a new virtual address when
21050 AutomapHostsOnResolve is set. That's good enough so long as we
21051 aren't close to handing out our entire virtual address space;
21052 if you're getting there, it's best to switch to IPv6 virtual
21056 - The ADDRMAP command can no longer generate an ill-formed error
21057 code on a failed MAPADDRESS. It now says "internal" rather than
21058 an English sentence fragment with spaces in the middle. Bugfix on
21059 Tor 0.2.0.19-alpha.
21060 - Fix log messages and comments to avoid saying "GMT" when we mean
21061 "UTC". Fixes bug 6113.
21062 - Compile on win64 using mingw64. Fixes bug 7260; patches from
21064 - Fix a crash when debugging unit tests on Windows: deallocate a
21065 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
21066 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
21069 - The DirServer option is now DirAuthority, for consistency with
21070 current naming patterns. You can still use the old DirServer form.
21072 o Code simplification and refactoring:
21073 - Move the client-side address-map/virtual-address/DNS-cache code
21074 out of connection_edge.c into a new addressmap.c module.
21075 - Remove unused code for parsing v1 directories and "running routers"
21076 documents. Fixes bug 6887.
21079 Changes in version 0.2.3.25 - 2012-11-19
21080 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
21081 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
21082 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
21083 programmer, and friend. Unstinting in his dedication to the cause of
21084 freedom, he inspired and helped many of us as we began our work on
21085 anonymity, and inspires us still. Please honor his memory by writing
21086 software to protect people's freedoms, and by helping others to do so.
21088 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
21089 significantly reduced directory overhead (via microdescriptors),
21090 enormous crypto performance improvements for fast relays on new
21091 enough hardware, a new v3 TLS handshake protocol that can better
21092 resist fingerprinting, support for protocol obfuscation plugins (aka
21093 pluggable transports), better scalability for hidden services, IPv6
21094 support for bridges, performance improvements like allowing clients
21095 to skip the first round-trip on the circuit ("optimistic data") and
21096 refilling token buckets more often, a new "stream isolation" design
21097 to isolate different applications on different circuits, and many
21098 stability, security, and privacy fixes.
21101 - Tor tries to wipe potentially sensitive data after using it, so
21102 that if some subsequent security failure exposes Tor's memory,
21103 the damage will be limited. But we had a bug where the compiler
21104 was eliminating these wipe operations when it decided that the
21105 memory was no longer visible to a (correctly running) program,
21106 hence defeating our attempt at defense in depth. We fix that
21107 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
21108 is unlikely to optimize away. Future versions of Tor may use
21109 a less ridiculously heavy approach for this. Fixes bug 7352.
21110 Reported in an article by Andrey Karpov.
21113 - Fix a harmless bug when opting against publishing a relay descriptor
21114 because DisableNetwork is set. Fixes bug 7464; bugfix on
21118 Changes in version 0.2.4.6-alpha - 2012-11-13
21119 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
21120 makes our defense-in-depth memory wiping more reliable, and begins to
21121 count IPv6 addresses in bridge statistics,
21124 - Fix an assertion failure that could occur when closing a connection
21125 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
21127 - Tor tries to wipe potentially sensitive data after using it, so
21128 that if some subsequent security failure exposes Tor's memory,
21129 the damage will be limited. But we had a bug where the compiler
21130 was eliminating these wipe operations when it decided that the
21131 memory was no longer visible to a (correctly running) program,
21132 hence defeating our attempt at defense in depth. We fix that
21133 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
21134 is unlikely to optimize away. Future versions of Tor may use
21135 a less ridiculously heavy approach for this. Fixes bug 7352.
21136 Reported in an article by Andrey Karpov.
21139 - Add GeoIP database for IPv6 addresses. The new config option
21141 - Bridge statistics now count bridge clients connecting over IPv6:
21142 bridge statistics files now list "bridge-ip-versions" and
21143 extra-info documents list "geoip6-db-digest". The control protocol
21144 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
21145 implementation by "shkoo", addressing ticket 5055.
21148 - Warn when we are binding low ports when hibernation is enabled;
21149 previously we had warned when we were _advertising_ low ports with
21150 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
21151 - Fix a harmless bug when opting against publishing a relay descriptor
21152 because DisableNetwork is set. Fixes bug 7464; bugfix on
21154 - Add warning message when a managed proxy dies during configuration.
21155 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
21156 - Fix a linking error when building tor-fw-helper without miniupnp.
21157 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
21158 - Check for closing an or_connection_t without going through correct
21159 channel functions; emit a warning and then call
21160 connection_or_close_for_error() so we don't assert as in bugs 7212
21162 - Compile correctly on compilers without C99 designated initializer
21163 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
21164 - Avoid a possible assert that can occur when channel_send_destroy() is
21165 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
21166 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
21167 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
21168 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
21169 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
21171 o Code simplification and refactoring:
21172 - Start using OpenBSD's implementation of queue.h, so that we don't
21173 need to hand-roll our own pointer and list structures whenever we
21174 need them. (We can't rely on a sys/queue.h, since some operating
21175 systems don't have them, and the ones that do have them don't all
21176 present the same extensions.)
21179 Changes in version 0.2.4.5-alpha - 2012-10-25
21180 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
21181 two important security vulnerabilities that could lead to remotely
21182 triggerable relay crashes, fix a major bug that was preventing clients
21183 from choosing suitable exit nodes, and refactor some of our code.
21185 o Major bugfixes (security, also in 0.2.3.24-rc):
21186 - Fix a group of remotely triggerable assertion failures related to
21187 incorrect link protocol negotiation. Found, diagnosed, and fixed
21188 by "some guy from France". Fix for CVE-2012-2250; bugfix on
21190 - Fix a denial of service attack by which any directory authority
21191 could crash all the others, or by which a single v2 directory
21192 authority could crash everybody downloading v2 directory
21193 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
21195 o Major bugfixes (also in 0.2.3.24-rc):
21196 - When parsing exit policy summaries from microdescriptors, we had
21197 previously been ignoring the last character in each one, so that
21198 "accept 80,443,8080" would be treated by clients as indicating
21199 a node that allows access to ports 80, 443, and 808. That would
21200 lead to clients attempting connections that could never work,
21201 and ignoring exit nodes that would support their connections. Now
21202 clients parse these exit policy summaries correctly. Fixes bug 7192;
21203 bugfix on 0.2.3.1-alpha.
21205 o Minor bugfixes (also in 0.2.3.24-rc):
21206 - Clients now consider the ClientRejectInternalAddresses config option
21207 when using a microdescriptor consensus stanza to decide whether
21208 an exit relay would allow exiting to an internal address. Fixes
21209 bug 7190; bugfix on 0.2.3.1-alpha.
21212 - Only disable TLS session ticket support when running as a TLS
21213 server. Now clients will blend better with regular Firefox
21214 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
21216 o Code simplification and refactoring:
21217 - Start using OpenBSD's implementation of queue.h (originally by
21219 - Move the entry node code from circuitbuild.c to its own file.
21220 - Move the circuit build timeout tracking code from circuitbuild.c
21224 Changes in version 0.2.3.24-rc - 2012-10-25
21225 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
21226 could lead to remotely triggerable relay crashes, and fixes
21227 a major bug that was preventing clients from choosing suitable exit
21230 o Major bugfixes (security):
21231 - Fix a group of remotely triggerable assertion failures related to
21232 incorrect link protocol negotiation. Found, diagnosed, and fixed
21233 by "some guy from France". Fix for CVE-2012-2250; bugfix on
21235 - Fix a denial of service attack by which any directory authority
21236 could crash all the others, or by which a single v2 directory
21237 authority could crash everybody downloading v2 directory
21238 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
21241 - When parsing exit policy summaries from microdescriptors, we had
21242 previously been ignoring the last character in each one, so that
21243 "accept 80,443,8080" would be treated by clients as indicating
21244 a node that allows access to ports 80, 443, and 808. That would
21245 lead to clients attempting connections that could never work,
21246 and ignoring exit nodes that would support their connections. Now
21247 clients parse these exit policy summaries correctly. Fixes bug 7192;
21248 bugfix on 0.2.3.1-alpha.
21251 - Clients now consider the ClientRejectInternalAddresses config option
21252 when using a microdescriptor consensus stanza to decide whether
21253 an exit relay would allow exiting to an internal address. Fixes
21254 bug 7190; bugfix on 0.2.3.1-alpha.
21257 Changes in version 0.2.4.4-alpha - 2012-10-20
21258 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
21259 vulnerability introduced by a change in OpenSSL, fixes a remotely
21260 triggerable assert, and adds new channel_t and circuitmux_t abstractions
21261 that will make it easier to test new connection transport and cell
21262 scheduling algorithms.
21264 o New directory authorities (also in 0.2.3.23-rc):
21265 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21266 authority. Closes ticket 5749.
21268 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
21269 - Disable TLS session tickets. OpenSSL's implementation was giving
21270 our TLS session keys the lifetime of our TLS context objects, when
21271 perfect forward secrecy would want us to discard anything that
21272 could decrypt a link connection as soon as the link connection
21273 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21274 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21275 - Discard extraneous renegotiation attempts once the V3 link
21276 protocol has been initiated. Failure to do so left us open to
21277 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21278 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21280 o Internal abstraction features:
21281 - Introduce new channel_t abstraction between circuits and
21282 or_connection_t to allow for implementing alternate OR-to-OR
21283 transports. A channel_t is an abstract object which can either be a
21284 cell-bearing channel, which is responsible for authenticating and
21285 handshaking with the remote OR and transmitting cells to and from
21286 it, or a listening channel, which spawns new cell-bearing channels
21287 at the request of remote ORs. Implements part of ticket 6465.
21288 - Also new is the channel_tls_t subclass of channel_t, adapting it
21289 to the existing or_connection_t code. The V2/V3 protocol handshaking
21290 code which formerly resided in command.c has been moved below the
21291 channel_t abstraction layer and may be found in channeltls.c now.
21292 Implements the rest of ticket 6465.
21293 - Introduce new circuitmux_t storing the queue of circuits for
21294 a channel; this encapsulates and abstracts the queue logic and
21295 circuit selection policy, and allows the latter to be overridden
21296 easily by switching out a policy object. The existing EWMA behavior
21297 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
21299 o Required libraries:
21300 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
21301 strongly recommended.
21304 - Warn users who run hidden services on a Tor client with
21305 UseEntryGuards disabled that their hidden services will be
21306 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
21307 attack which motivated Tor to support entry guards in the first
21308 place). Resolves ticket 6889.
21309 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
21310 dhill. Resolves ticket 6982.
21311 - Option OutboundBindAddress can be specified multiple times and
21312 accepts IPv6 addresses. Resolves ticket 6876.
21314 o Minor bugfixes (also in 0.2.3.23-rc):
21315 - Don't serve or accept v2 hidden service descriptors over a
21316 relay's DirPort. It's never correct to do so, and disabling it
21317 might make it more annoying to exploit any bugs that turn up in the
21318 descriptor-parsing code. Fixes bug 7149.
21319 - Fix two cases in src/or/transports.c where we were calling
21320 fmt_addr() twice in a parameter list. Bug found by David
21321 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21322 - Fix memory leaks whenever we logged any message about the "path
21323 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21324 - When relays refuse a "create" cell because their queue of pending
21325 create cells is too big (typically because their cpu can't keep up
21326 with the arrival rate), send back reason "resource limit" rather
21327 than reason "internal", so network measurement scripts can get a
21328 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
21331 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
21332 - Free some more still-in-use memory at exit, to make hunting for
21333 memory leaks easier. Resolves bug 7029.
21334 - When a Tor client gets a "truncated" relay cell, the first byte of
21335 its payload specifies why the circuit was truncated. We were
21336 ignoring this 'reason' byte when tearing down the circuit, resulting
21337 in the controller not being told why the circuit closed. Now we
21338 pass the reason from the truncated cell to the controller. Bugfix
21339 on 0.1.2.3-alpha; fixes bug 7039.
21340 - Downgrade "Failed to hand off onionskin" messages to "debug"
21341 severity, since they're typically redundant with the "Your computer
21342 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
21343 - Make clients running with IPv6 bridges connect over IPv6 again,
21344 even without setting new config options ClientUseIPv6 and
21345 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
21346 - Use square brackets around IPv6 addresses in numerous places
21347 that needed them, including log messages, HTTPS CONNECT proxy
21348 requests, TransportProxy statefile entries, and pluggable transport
21349 extra-info lines. Fixes bug 7011; patch by David Fifield.
21351 o Code refactoring and cleanup:
21352 - Source files taken from other packages now reside in src/ext;
21353 previously they were scattered around the rest of Tor.
21354 - Avoid use of reserved identifiers in our C code. The C standard
21355 doesn't like us declaring anything that starts with an
21356 underscore, so let's knock it off before we get in trouble. Fix
21357 for bug 1031; bugfix on the first Tor commit.
21360 Changes in version 0.2.3.23-rc - 2012-10-20
21361 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
21362 vulnerability introduced by a change in OpenSSL, and fixes a variety
21363 of smaller bugs in preparation for the release.
21365 o New directory authorities:
21366 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21367 authority. Closes ticket 5749.
21369 o Major bugfixes (security/privacy):
21370 - Disable TLS session tickets. OpenSSL's implementation was giving
21371 our TLS session keys the lifetime of our TLS context objects, when
21372 perfect forward secrecy would want us to discard anything that
21373 could decrypt a link connection as soon as the link connection
21374 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21375 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21376 - Discard extraneous renegotiation attempts once the V3 link
21377 protocol has been initiated. Failure to do so left us open to
21378 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21379 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21382 - Fix a possible crash bug when checking for deactivated circuits
21383 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21384 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21386 o Minor bugfixes (on 0.2.3.x):
21387 - Fix two cases in src/or/transports.c where we were calling
21388 fmt_addr() twice in a parameter list. Bug found by David
21389 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21390 - Convert an assert in the pathbias code to a log message. The assert
21391 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21392 bugfix on 0.2.3.17-beta.
21393 - Fix memory leaks whenever we logged any message about the "path
21394 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21396 o Minor bugfixes (on 0.2.2.x and earlier):
21397 - Don't serve or accept v2 hidden service descriptors over a relay's
21398 DirPort. It's never correct to do so, and disabling it might
21399 make it more annoying to exploit any bugs that turn up in the
21400 descriptor-parsing code. Fixes bug 7149.
21401 - When relays refuse a "create" cell because their queue of pending
21402 create cells is too big (typically because their cpu can't keep up
21403 with the arrival rate), send back reason "resource limit" rather
21404 than reason "internal", so network measurement scripts can get a
21405 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
21406 - Correct file sizes when reading binary files on Cygwin, to avoid
21407 a bug where Tor would fail to read its state file. Fixes bug 6844;
21408 bugfix on 0.1.2.7-alpha.
21409 - Avoid undefined behavior when parsing the list of supported
21410 rendezvous/introduction protocols in a hidden service descriptor.
21411 Previously, Tor would have confused (as-yet-unused) protocol version
21412 numbers greater than 32 with lower ones on many platforms. Fixes
21413 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
21415 o Documentation fixes:
21416 - Clarify that hidden services are TCP only. Fixes bug 6024.
21419 Changes in version 0.2.4.3-alpha - 2012-09-22
21420 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
21421 assertion, resumes letting relays test reachability of their DirPort,
21422 and cleans up a bunch of smaller bugs.
21425 - Fix an assertion failure in tor_timegm() that could be triggered
21426 by a badly formatted directory object. Bug found by fuzzing with
21427 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21430 - Fix a possible crash bug when checking for deactivated circuits
21431 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21432 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21433 - Allow routers to detect that their own DirPorts are running. When
21434 we removed support for versions_supports_begindir, we also
21435 accidentally removed the mechanism we used to self-test our
21436 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
21437 bugfix on 0.2.4.2-alpha.
21439 o Security features:
21440 - Switch to a completely time-invariant approach for picking nodes
21441 weighted by bandwidth. Our old approach would run through the
21442 part of the loop after it had made its choice slightly slower
21443 than it ran through the part of the loop before it had made its
21444 choice. Addresses ticket 6538.
21445 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
21446 by tor2web clients allows hidden services to identify tor2web
21447 clients through their repeated selection of the same rendezvous
21448 and introduction point circuit endpoints (their guards). Resolves
21452 - Enable Tor to read configuration, state, and key information from
21453 a FIFO. Previously Tor would only read from files with a positive
21454 stat.st_size. Code from meejah; fixes bug 6044.
21457 - Correct file sizes when reading binary files on Cygwin, to avoid
21458 a bug where Tor would fail to read its state file. Fixes bug 6844;
21459 bugfix on 0.1.2.7-alpha.
21460 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
21461 bugfix on 0.2.0.3-alpha.
21462 - When complaining about a client port on a public address, log
21463 which address we're complaining about. Fixes bug 4020; bugfix on
21464 0.2.3.3-alpha. Patch by Tom Fitzhenry.
21465 - Convert an assert in the pathbias code to a log message. The assert
21466 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21467 bugfix on 0.2.3.17-beta.
21468 - Our new buildsystem was overzealous about rebuilding manpages: it
21469 would rebuild them all whenever any one of them changed. Now our
21470 dependency checking should be correct. Fixes bug 6843; bugfix on
21472 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
21473 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
21474 - Correct log printout about which address family is preferred
21475 when connecting to a bridge with both an IPv4 and IPv6 OR port.
21476 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
21478 o Minor bugfixes (code cleanliness):
21479 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
21480 with large values. This situation was untriggered, but nevertheless
21481 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
21482 - Reject consensus votes with more than 64 known-flags. We aren't even
21483 close to that limit yet, and our code doesn't handle it correctly.
21484 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
21485 - Avoid undefined behavior when parsing the list of supported
21486 rendezvous/introduction protocols in a hidden service descriptor.
21487 Previously, Tor would have confused (as-yet-unused) protocol version
21488 numbers greater than 32 with lower ones on many platforms. Fixes
21489 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
21490 - Fix handling of rendezvous client authorization types over 8.
21491 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
21492 - Fix building with older versions of GCC (2.95, for one) that don't
21493 like preprocessor directives inside macro arguments. Found by
21494 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
21495 - Switch weighted node selection rule from using a list of doubles
21496 to using a list of int64_t. This change should make the process
21497 slightly easier to debug and maintain. Needed to finish ticket 6538.
21499 o Code simplification and refactoring:
21500 - Move the generic "config" code into a new file, and have "config.c"
21501 hold only torrc- and state-related code. Resolves ticket 6823.
21502 - Move the core of our "choose a weighted element at random" logic
21503 into its own function, and give it unit tests. Now the logic is
21504 testable, and a little less fragile too.
21505 - Removed the testing_since field of node_t, which hasn't been used
21506 for anything since 0.2.0.9-alpha.
21508 o Documentation fixes:
21509 - Clarify that hidden services are TCP only. Fixes bug 6024.
21510 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
21514 Changes in version 0.2.3.22-rc - 2012-09-11
21515 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
21519 - Fix an assertion failure in tor_timegm() that could be triggered
21520 by a badly formatted directory object. Bug found by fuzzing with
21521 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21524 - Avoid segfault when starting up having run with an extremely old
21525 version of Tor and parsing its state file. Fixes bug 6801; bugfix
21529 Changes in version 0.2.2.39 - 2012-09-11
21530 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
21534 - Fix an assertion failure in tor_timegm() that could be triggered
21535 by a badly formatted directory object. Bug found by fuzzing with
21536 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21537 - Do not crash when comparing an address with port value 0 to an
21538 address policy. This bug could have been used to cause a remote
21539 assertion failure by or against directory authorities, or to
21540 allow some applications to crash clients. Fixes bug 6690; bugfix
21544 Changes in version 0.2.4.2-alpha - 2012-09-10
21545 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
21546 raises the default rate limiting even more, and makes the bootstrapping
21547 log messages less noisy.
21550 - Automatically forward the TCP ports of pluggable transport
21551 proxies using tor-fw-helper if PortForwarding is enabled. Implements
21555 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
21556 to 1GB/1GB. The previous defaults were intended to be "basically
21557 infinite", but it turns out they're now limiting our 100mbit+
21558 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
21559 last time we raised it).
21562 - Detect when we're running with a version of OpenSSL other than the
21563 one we compiled with. This has occasionally given people hard-to-
21565 - Log fewer lines at level "notice" about our OpenSSL and Libevent
21566 versions and capabilities when everything is going right. Resolves
21567 part of ticket 6736.
21568 - Directory authorities no long accept descriptors for any version of
21569 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
21570 These versions are insecure, unsupported, or both. Implements
21574 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
21575 to start with a triple-underscore so the controller won't touch it.
21576 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
21577 - Avoid segfault when starting up having run with an extremely old
21578 version of Tor and parsing its state file. Fixes bug 6801; bugfix
21580 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
21581 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
21582 - Don't follow the NULL pointer if microdescriptor generation fails.
21583 (This does not appear to be triggerable, but it's best to be safe.)
21584 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
21585 - Fix mis-declared dependencies on src/common/crypto.c and
21586 src/or/tor_main.c that could break out-of-tree builds under some
21587 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
21588 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
21589 6778; bugfix on 0.2.4.1-alpha.
21590 - Fix a harmless (in this case) build warning for implicitly
21591 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
21593 o Removed features:
21594 - Now that all versions before 0.2.2.x are disallowed, we no longer
21595 need to work around their missing features. Thus we can remove a
21596 bunch of compatibility code.
21598 o Code refactoring:
21599 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
21600 TCP ports to forward. In the past it only accepted two ports:
21601 the ORPort and the DirPort.
21604 Changes in version 0.2.4.1-alpha - 2012-09-05
21605 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
21606 bridgedb; lets relays use IPv6 addresses and directory authorities
21607 advertise them; and switches to a cleaner build interface.
21609 This is the first alpha release in a new series, so expect there to
21610 be bugs. Users who would rather test out a more stable branch should
21611 stay with 0.2.3.x for now.
21613 o Major features (bridges):
21614 - Bridges now report the pluggable transports they support to the
21615 bridge authority, so it can pass the supported transports on to
21616 bridgedb and/or eventually do reachability testing. Implements
21619 o Major features (IPv6):
21620 - Bridge authorities now accept IPv6 bridge addresses and include
21621 them in network status documents. Implements ticket 5534.
21622 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
21623 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
21624 to happen. Implements ticket 5535.
21625 - All kind of relays, not just bridges, can now advertise an IPv6
21626 OR port. Implements ticket 6362.
21627 - Directory authorities vote on IPv6 OR ports using the new consensus
21628 method 14. Implements ticket 6363.
21630 o Major features (build):
21631 - Switch to a nonrecursive Makefile structure. Now instead of each
21632 Makefile.am invoking other Makefile.am's, there is a master
21633 Makefile.am that includes the others. This change makes our build
21634 process slightly more maintainable, and improves parallelism for
21635 building with make -j. Original patch by Stewart Smith; various
21636 fixes by Jim Meyering.
21637 - Where available, we now use automake's "silent" make rules by
21638 default, so that warnings are easier to spot. You can get the old
21639 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
21641 o Minor features (code security and spec conformance):
21642 - Clear keys and key-derived material left on the stack in
21643 rendservice.c and rendclient.c. Check return value of
21644 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
21645 These fixes should make us more forward-secure against cold-boot
21646 attacks and the like. Fixes bug 2385.
21647 - Reject EXTEND cells sent to nonexistent streams. According to the
21648 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
21649 we were only checking for stream IDs that were currently in use.
21650 Found while hunting for more instances of bug 6271. Bugfix on
21651 0.0.2pre8, which introduced incremental circuit construction.
21653 o Minor features (streamlining);
21654 - No longer include the "opt" prefix when generating routerinfos
21655 or v2 directories: it has been needless since Tor 0.1.2. Closes
21657 - Remove some now-needless code that tried to aggressively flush
21658 OR connections as data was added to them. Since 0.2.0.1-alpha, our
21659 cell queue logic has saved us from the failure mode that this code
21660 was supposed to prevent. Removing this code will limit the number
21661 of baroque control flow paths through Tor's network logic. Reported
21662 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
21664 o Minor features (controller):
21665 - Add a "GETINFO signal/names" control port command. Implements
21667 - Provide default values for all options via "GETINFO config/defaults".
21668 Implements ticket 4971.
21670 o Minor features (IPv6):
21671 - New config option "AuthDirHasIPv6Connectivity 1" that directory
21672 authorities should set if they have IPv6 connectivity and want to
21673 do reachability tests for IPv6 relays. Implements feature 5974.
21674 - A relay with an IPv6 OR port now sends that address in NETINFO
21675 cells (in addition to its other address). Implements ticket 6364.
21677 o Minor features (log messages):
21678 - Omit the first heartbeat log message, because it never has anything
21679 useful to say, and it clutters up the bootstrapping messages.
21680 Resolves ticket 6758.
21681 - Don't log about reloading the microdescriptor cache at startup. Our
21682 bootstrap warnings are supposed to tell the user when there's a
21683 problem, and our bootstrap notices say when there isn't. Resolves
21684 ticket 6759; bugfix on 0.2.2.6-alpha.
21685 - Don't log "I learned some more directory information" when we're
21686 reading cached directory information. Reserve it for when new
21687 directory information arrives in response to a fetch. Resolves
21689 - Prevent rounding error in path bias counts when scaling
21690 them down, and use the correct scale factor default. Also demote
21691 some path bias related log messages down a level and make others
21692 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
21693 - We no longer warn so much when generating manpages from their
21696 o Code simplifications and refactoring:
21697 - Enhance our internal sscanf replacement so that we can eliminate
21698 the last remaining uses of the system sscanf. (Though those uses
21699 of sscanf were safe, sscanf itself is generally error prone, so
21700 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
21702 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
21703 - Move last_reachable and testing_since from routerinfo_t to node_t.
21704 Implements ticket 5529.
21705 - Add replaycache_t structure, functions and unit tests, then refactor
21706 rend_service_introduce() to be more clear to read, improve, debug,
21707 and test. Resolves bug 6177.
21708 - Finally remove support for malloc_good_size and malloc_usable_size.
21709 We had hoped that these functions would let us eke a little more
21710 memory out of our malloc implementation. Unfortunately, the only
21711 implementations that provided these functions are also ones that
21712 are already efficient about not overallocation: they never got us
21713 more than 7 or so bytes per allocation. Removing them saves us a
21714 little code complexity and a nontrivial amount of build complexity.
21716 o New requirements:
21717 - Tor maintainers now require Automake version 1.9 or later to build
21718 Tor from the Git repository. (Automake is not required when building
21719 from a source distribution.)
21722 Changes in version 0.2.3.21-rc - 2012-09-05
21723 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
21724 series. It fixes a trio of potential security bugs, fixes a bug where
21725 we were leaving some of the fast relays out of the microdescriptor
21726 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
21727 and cleans up other smaller issues.
21729 o Major bugfixes (security):
21730 - Tear down the circuit if we get an unexpected SENDME cell. Clients
21731 could use this trick to make their circuits receive cells faster
21732 than our flow control would have allowed, or to gum up the network,
21733 or possibly to do targeted memory denial-of-service attacks on
21734 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
21735 from July 2002, before the release of Tor 0.0.0. We had committed
21736 this patch previously, but we had to revert it because of bug 6271.
21737 Now that 6271 is fixed, this patch appears to work.
21738 - Reject any attempt to extend to an internal address. Without
21739 this fix, a router could be used to probe addresses on an internal
21740 network to see whether they were accepting connections. Fixes bug
21741 6710; bugfix on 0.0.8pre1.
21742 - Do not crash when comparing an address with port value 0 to an
21743 address policy. This bug could have been used to cause a remote
21744 assertion failure by or against directory authorities, or to
21745 allow some applications to crash clients. Fixes bug 6690; bugfix
21749 - Remove the upper bound on microdescriptor length. We were hitting
21750 the limit for routers with complex exit policies or family
21751 declarations, causing clients to not use them. Fixes the first
21752 piece of bug 6404; fix on 0.2.2.6-alpha.
21753 - Detect "ORPort 0" as meaning, uniformly, that we're not running
21754 as a relay. Previously, some of our code would treat the presence
21755 of any ORPort line as meaning that we should act like a relay,
21756 even though our new listener code would correctly not open any
21757 ORPorts for ORPort 0. Similar bugs in other Port options are also
21758 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
21761 - Avoid a pair of double-free and use-after-mark bugs that can
21762 occur with certain timings in canceled and re-received DNS
21763 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
21764 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
21765 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
21766 - Allow one-hop directory fetching circuits the full "circuit build
21767 timeout" period, rather than just half of it, before failing them
21768 and marking the relay down. This fix should help reduce cases where
21769 clients declare relays (or worse, bridges) unreachable because
21770 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
21771 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
21773 - Authorities no longer include any router in their microdescriptor
21774 consensuses for which they couldn't generate or agree on a
21775 microdescriptor. Fixes the second piece of bug 6404; fix on
21777 - Detect and reject attempts to specify both "FooPort" and
21778 "FooPort 0" in the same configuration domain. (It's still okay
21779 to have a FooPort in your configuration file, and use "FooPort 0"
21780 on the command line to disable it.) Fixes the second half of bug
21781 6507; bugfix on 0.2.3.3-alpha.
21782 - Make wildcarded addresses (that is, ones beginning with "*.") work
21783 when provided via the controller's MapAddress command. Previously,
21784 they were accepted, but we never actually noticed that they were
21785 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
21786 - Avoid crashing on a malformed state file where EntryGuardPathBias
21787 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
21788 - Add a (probably redundant) memory clear between iterations of
21789 the router status voting loop, to prevent future coding errors
21790 where data might leak between iterations of the loop. Resolves
21793 o Minor bugfixes (log messages):
21794 - Downgrade "set buildtimeout to low value" messages to "info"
21795 severity; they were never an actual problem, there was never
21796 anything reasonable to do about them, and they tended to spam logs
21797 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
21798 - Downgrade path-bias warning messages to "info". We'll try to get
21799 them working better in 0.2.4. Add internal circuit construction
21800 state to protect against the noisy warn message "Unexpectedly high
21801 circuit_successes". Also add some additional rate-limited notice
21802 messages to help determine the root cause of the warn. Fixes bug
21803 6475. Bugfix against 0.2.3.17-beta.
21804 - Move log message when unable to find a microdesc in a routerstatus
21805 entry to parse time. Previously we'd spam this warning every time
21806 we tried to figure out which microdescriptors to download. Fixes
21807 the third piece of bug 6404; fix on 0.2.3.18-rc.
21810 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
21811 change when the authority is deciding whether to accept a newly
21812 uploaded descriptor. Implements ticket 6423.
21813 - Add missing documentation for consensus and microdesc files.
21814 Resolves ticket 6732.
21817 Changes in version 0.2.2.38 - 2012-08-12
21818 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
21819 attack that could in theory leak path information.
21822 - Avoid an uninitialized memory read when reading a vote or consensus
21823 document that has an unrecognized flavor name. This read could
21824 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21825 - Try to leak less information about what relays a client is
21826 choosing to a side-channel attacker. Previously, a Tor client would
21827 stop iterating through the list of available relays as soon as it
21828 had chosen one, thus finishing a little earlier when it picked
21829 a router earlier in the list. If an attacker can recover this
21830 timing information (nontrivial but not proven to be impossible),
21831 they could learn some coarse-grained information about which relays
21832 a client was picking (middle nodes in particular are likelier to
21833 be affected than exits). The timing attack might be mitigated by
21834 other factors (see bug 6537 for some discussion), but it's best
21835 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21838 Changes in version 0.2.3.20-rc - 2012-08-05
21839 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
21840 series. It fixes a pair of code security bugs and a potential anonymity
21841 issue, updates our RPM spec files, and cleans up other smaller issues.
21844 - Avoid read-from-freed-memory and double-free bugs that could occur
21845 when a DNS request fails while launching it. Fixes bug 6480;
21846 bugfix on 0.2.0.1-alpha.
21847 - Avoid an uninitialized memory read when reading a vote or consensus
21848 document that has an unrecognized flavor name. This read could
21849 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21850 - Try to leak less information about what relays a client is
21851 choosing to a side-channel attacker. Previously, a Tor client would
21852 stop iterating through the list of available relays as soon as it
21853 had chosen one, thus finishing a little earlier when it picked
21854 a router earlier in the list. If an attacker can recover this
21855 timing information (nontrivial but not proven to be impossible),
21856 they could learn some coarse-grained information about which relays
21857 a client was picking (middle nodes in particular are likelier to
21858 be affected than exits). The timing attack might be mitigated by
21859 other factors (see bug 6537 for some discussion), but it's best
21860 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21863 - Try to make the warning when giving an obsolete SOCKSListenAddress
21864 a little more useful.
21865 - Terminate active server managed proxies if Tor stops being a
21866 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
21867 - Provide a better error message about possible OSX Asciidoc failure
21868 reasons. Fixes bug 6436.
21869 - Warn when Tor is configured to use accounting in a way that can
21870 link a hidden service to some other hidden service or public
21871 address. Resolves ticket 6490.
21874 - Check return value of fputs() when writing authority certificate
21875 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
21876 - Ignore ServerTransportPlugin lines when Tor is not configured as
21877 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
21878 - When disabling guards for having too high a proportion of failed
21879 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
21883 - Update our default RPM spec files to work with mock and rpmbuild
21884 on RHEL/Fedora. They have an updated set of dependencies and
21885 conflicts, a fix for an ancient typo when creating the "_tor"
21886 user, and better instructions. Thanks to Ondrej Mikle for the
21887 patch series. Fixes bug 6043.
21890 - Make it possible to set the TestingTorNetwork configuration
21891 option using AlternateDirAuthority and AlternateBridgeAuthority
21892 as an alternative to setting DirServer. Addresses ticket 6377.
21895 - Clarify the documentation for the Alternate*Authority options.
21897 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
21899 o Code simplification and refactoring:
21900 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
21901 10 lines. Also, don't nest them. Doing so in the past has
21902 led to hard-to-debug code. The new style is to use the
21903 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
21906 Changes in version 0.2.3.19-rc - 2012-07-06
21907 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
21908 series. It fixes the compile on Windows, reverts to a GeoIP database
21909 that isn't as broken, and fixes a flow control bug that has been around
21910 since the beginning of Tor.
21913 - Fix a bug handling SENDME cells on nonexistent streams that could
21914 result in bizarre window values. Report and patch contributed
21915 pseudonymously. Fixes part of bug 6271. This bug was introduced
21916 before the first Tor release, in svn commit r152.
21917 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
21918 June 2012 database, Maxmind marked many Tor relays as country "A1",
21919 which will cause risky behavior for clients that set EntryNodes
21920 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
21921 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
21922 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
21925 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
21926 bugfix on 0.2.1.10-alpha.
21929 Changes in version 0.2.3.18-rc - 2012-06-28
21930 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
21931 series. It fixes a few smaller bugs, but generally appears stable.
21932 Please test it and let us know whether it is!
21935 - Allow wildcarded mapaddress targets to be specified on the
21936 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
21937 - Make our linker option detection code more robust against linkers
21938 such as on FreeBSD 8, where a bad combination of options completes
21939 successfully but makes an unrunnable binary. Fixes bug 6173;
21940 bugfix on 0.2.3.17-beta.
21942 o Minor bugfixes (on 0.2.2.x and earlier):
21943 - Avoid a false positive in the util/threads unit test by increasing
21944 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
21945 - Replace "Sending publish request" log messages with "Launching
21946 upload", so that they no longer confusingly imply that we're
21947 sending something to a directory we might not even be connected
21948 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
21949 - Make sure to set *socket_error in all error cases in
21950 connection_connect(), so it can't produce a warning about
21951 errno being zero from errno_to_orconn_end_reason(). Bugfix on
21952 0.2.1.1-alpha; resolves ticket 6028.
21953 - Downgrade "Got a certificate, but we already have it" log messages
21954 from warning to info, except when we're a dirauth. Fixes bug 5238;
21955 bugfix on 0.2.1.7-alpha.
21956 - When checking for requested signatures on the latest consensus
21957 before serving it to a client, make sure to check the right
21958 consensus flavor. Bugfix on 0.2.2.6-alpha.
21959 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
21960 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
21962 o Minor bugfixes (on 0.2.3.x):
21963 - Make format_helper_exit_status() avoid unnecessary space padding
21964 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
21966 - Downgrade a message about cleaning the microdescriptor cache to
21967 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
21968 - Log a BUG message at severity INFO if we have a networkstatus with
21969 a missing entry for some microdescriptor. Continues on a patch
21971 - Improve the log message when a managed proxy fails to launch. Fixes
21972 bug 5099; bugfix on 0.2.3.6-alpha.
21973 - Don't do DNS lookups when parsing corrupted managed proxy protocol
21974 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
21975 - When formatting wildcarded address mappings for the controller,
21976 be sure to include "*." as appropriate. Partially fixes bug 6244;
21977 bugfix on 0.2.3.9-alpha.
21978 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
21979 Bugfix on 0.2.3.13-alpha.
21980 - Stop logging messages about running with circuit timeout learning
21981 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
21982 - Disable a spurious warning about reading on a marked and flushing
21983 connection. We shouldn't be doing that, but apparently we
21984 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
21985 - Fix a bug that stopped AllowDotExit from working on addresses
21986 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
21989 o Code simplification, refactoring, unit tests:
21990 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
21991 Libevent's notion of cached time when possible.
21992 - Remove duplicate code for invoking getrlimit() from control.c.
21993 - Add a unit test for the environment_variable_names_equal function.
21996 - Document the --defaults-torrc option, and the new (in 0.2.3)
21997 semantics for overriding, extending, and clearing lists of
21998 options. Closes bug 4748.
22001 Changes in version 0.2.3.17-beta - 2012-06-15
22002 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
22003 gets our TLS handshake back on track for being able to blend in with
22004 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
22005 with Vidalia, and otherwise continues to get us closer to a release
22009 - Enable gcc and ld hardening by default. Resolves ticket 5210.
22010 - Update TLS cipher list to match Firefox 8 and later. Resolves
22012 - Implement the client side of proposal 198: remove support for
22013 clients falsely claiming to support standard ciphersuites that
22014 they can actually provide. As of modern OpenSSL versions, it's not
22015 necessary to fake any standard ciphersuite, and doing so prevents
22016 us from using better ciphersuites in the future, since servers
22017 can't know whether an advertised ciphersuite is really supported or
22018 not. Some hosts -- notably, ones with very old versions of OpenSSL
22019 or where OpenSSL has been built with ECC disabled -- will stand
22020 out because of this change; TBB users should not be affected.
22023 - Change the default value for DynamicDHGroups (introduced in
22024 0.2.3.9-alpha) to 0. This feature can make Tor relays less
22025 identifiable by their use of the mod_ssl DH group, but at
22026 the cost of some usability (#4721) and bridge tracing (#6087)
22027 regressions. Resolves ticket 5598.
22028 - Send a CRLF at the end of each STATUS_* control protocol event. This
22029 bug tickled a bug in Vidalia which would make it freeze. Fixes
22030 bug 6094; bugfix on 0.2.3.16-alpha.
22033 - Disable writing on marked-for-close connections when they are
22034 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
22035 bug 5263; bugfix on 0.0.2pre13, where we first added a special
22036 case for flushing marked connections.
22037 - Detect SSL handshake even when the initial attempt to write the
22038 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
22039 - Change the AllowDotExit rules so they should actually work.
22040 We now enforce AllowDotExit only immediately after receiving an
22041 address via SOCKS or DNSPort: other sources are free to provide
22042 .exit addresses after the resolution occurs. Fixes bug 3940;
22043 bugfix on 0.2.2.1-alpha.
22044 - Fix a (harmless) integer overflow in cell statistics reported by
22045 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
22046 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
22047 right places and never depends on the consensus parameters or
22048 computes adaptive timeouts when it is disabled. Fixes bug 5049;
22049 bugfix on 0.2.2.14-alpha.
22050 - When building Tor on Windows with -DUNICODE (not default), ensure
22051 that error messages, filenames, and DNS server names are always
22052 NUL-terminated when we convert them to a single-byte encoding.
22053 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
22054 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
22055 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
22056 - Fix an edge case where TestingTorNetwork is set but the authorities
22057 and relays all have an uptime of zero, where the private Tor network
22058 could briefly lack support for hidden services. Fixes bug 3886;
22059 bugfix on 0.2.2.18-alpha.
22060 - Correct the manpage's descriptions for the default values of
22061 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
22063 - Fix the documentation for the --hush and --quiet command line
22064 options, which changed their behavior back in 0.2.3.3-alpha.
22065 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
22069 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
22070 more information to it, so that we can track it down in case it
22071 returns again. Mitigates bug 5235.
22072 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
22073 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
22074 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
22075 - Warn the user when HTTPProxy, but no other proxy type, is
22076 configured. This can cause surprising behavior: it doesn't send
22077 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
22078 directory traffic only. Resolves ticket 4663.
22079 - Issue a notice if a guard completes less than 40% of your circuits.
22080 Threshold is configurable by torrc option PathBiasNoticeRate and
22081 consensus parameter pb_noticepct. There is additional, off-by-
22082 default code to disable guards which fail too many circuits.
22083 Addresses ticket 5458.
22084 - Update to the June 6 2012 Maxmind GeoLite Country database.
22086 o Code simplifications and refactoring:
22087 - Remove validate_pluggable_transports_config(): its warning
22088 message is now handled by connection_or_connect().
22091 Changes in version 0.2.2.37 - 2012-06-06
22092 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
22093 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
22097 - Work around a bug in OpenSSL that broke renegotiation with TLS
22098 1.1 and TLS 1.2. Without this workaround, all attempts to speak
22099 the v2 Tor connection protocol when both sides were using OpenSSL
22100 1.0.1 would fail. Resolves ticket 6033.
22101 - When waiting for a client to renegotiate, don't allow it to add
22102 any bytes to the input buffer. This fixes a potential DoS issue.
22103 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
22104 - Fix an edge case where if we fetch or publish a hidden service
22105 descriptor, we might build a 4-hop circuit and then use that circuit
22106 for exiting afterwards -- even if the new last hop doesn't obey our
22107 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
22110 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
22111 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
22114 - Tell GCC and Clang to check for any errors in format strings passed
22115 to the tor_v*(print|scan)f functions.
22118 Changes in version 0.2.3.16-alpha - 2012-06-05
22119 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
22120 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
22121 currently). It also fixes a variety of smaller bugs and other cleanups
22122 that get us closer to a release candidate.
22124 o Major bugfixes (general):
22125 - Work around a bug in OpenSSL that broke renegotiation with TLS
22126 1.1 and TLS 1.2. Without this workaround, all attempts to speak
22127 the v2 Tor connection protocol when both sides were using OpenSSL
22128 1.0.1 would fail. Resolves ticket 6033.
22129 - When waiting for a client to renegotiate, don't allow it to add
22130 any bytes to the input buffer. This fixes a potential DoS issue.
22131 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
22132 - Pass correct OR address to managed proxies (like obfsproxy),
22133 even when ORListenAddress is used. Fixes bug 4865; bugfix on
22135 - The advertised platform of a router now includes only its operating
22136 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
22137 service pack level (for Windows) or its CPU architecture (for Unix).
22138 We also no longer include the "git-XYZ" tag in the version. Resolves
22141 o Major bugfixes (clients):
22142 - If we are unable to find any exit that supports our predicted ports,
22143 stop calling them predicted, so that we don't loop and build
22144 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
22145 which introduced predicted ports.
22146 - Fix an edge case where if we fetch or publish a hidden service
22147 descriptor, we might build a 4-hop circuit and then use that circuit
22148 for exiting afterwards -- even if the new last hop doesn't obey our
22149 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
22150 - Check at each new consensus whether our entry guards were picked
22151 long enough ago that we should rotate them. Previously, we only
22152 did this check at startup, which could lead to us holding a guard
22153 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
22154 - When fetching a bridge descriptor from a bridge authority,
22155 always do so anonymously, whether we have been able to open
22156 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
22157 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
22158 but we'll need to wait for bug 6010 before it's actually usable.
22160 o Major bugfixes (directory authorities):
22161 - When computing weight parameters, behave more robustly in the
22162 presence of a bad bwweightscale value. Previously, the authorities
22163 would crash if they agreed on a sufficiently broken weight_scale
22164 value: now, they use a reasonable default and carry on. Partial
22165 fix for 5786; bugfix on 0.2.2.17-alpha.
22166 - Check more thoroughly to prevent a rogue authority from
22167 double-voting on any consensus directory parameter. Previously,
22168 authorities would crash in this case if the total number of
22169 votes for any parameter exceeded the number of active voters,
22170 but would let it pass otherwise. Partial fix for bug 5786; bugfix
22174 - Rate-limit log messages when asked to connect anonymously to
22175 a private address. When these hit, they tended to hit fast and
22176 often. Also, don't bother trying to connect to addresses that we
22177 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
22178 reply makes us think we have been lied to, even when the address the
22179 client tried to connect to was "localhost." Resolves ticket 2822.
22180 - Allow packagers to insert an extra string in server descriptor
22181 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
22182 Resolves the rest of ticket 2988.
22183 - Raise the threshold of server descriptors needed (75%) and exit
22184 server descriptors needed (50%) before we will declare ourselves
22185 bootstrapped. This will make clients start building circuits a
22186 little later, but makes the initially constructed circuits less
22187 skewed and less in conflict with further directory fetches. Fixes
22189 - Close any connection that sends unrecognized junk before the
22190 handshake. Solves an issue noted in bug 4369.
22191 - Improve log messages about managed transports. Resolves ticket 5070.
22192 - Tag a bridge's descriptor as "never to be sent unencrypted".
22193 This shouldn't matter, since bridges don't open non-anonymous
22194 connections to the bridge authority and don't allow unencrypted
22195 directory connections from clients, but we might as well make
22196 sure. Closes bug 5139.
22197 - Expose our view of whether we have gone dormant to the controller,
22198 via a new "GETINFO dormant" value. Torbutton and other controllers
22199 can use this to avoid doing periodic requests through Tor while
22200 it's dormant (bug 4718). Fixes bug 5954.
22201 - Tell GCC and Clang to check for any errors in format strings passed
22202 to the tor_v*(print|scan)f functions.
22203 - Update to the May 1 2012 Maxmind GeoLite Country database.
22205 o Minor bugfixes (already included in 0.2.2.36):
22206 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
22207 Fixes bug 5346; bugfix on 0.0.8pre3.
22208 - Correct parsing of certain date types in parse_http_time().
22209 Without this patch, If-Modified-Since would behave
22210 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
22211 Esteban Manchado Velázques.
22212 - Make our number-parsing functions always treat too-large values
22213 as an error, even when those values exceed the width of the
22214 underlying type. Previously, if the caller provided these
22215 functions with minima or maxima set to the extreme values of the
22216 underlying integer type, these functions would return those
22217 values on overflow rather than treating overflow as an error.
22218 Fixes part of bug 5786; bugfix on 0.0.9.
22219 - If we hit the error case where routerlist_insert() replaces an
22220 existing (old) server descriptor, make sure to remove that
22221 server descriptor from the old_routers list. Fix related to bug
22222 1776. Bugfix on 0.2.2.18-alpha.
22223 - Clarify the behavior of MaxCircuitDirtiness with hidden service
22224 circuits. Fixes issue 5259.
22226 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
22227 - Prevent a null-pointer dereference when receiving a data cell
22228 for a nonexistent stream when the circuit in question has an
22229 empty deliver window. We don't believe this is triggerable,
22230 since we don't currently allow deliver windows to become empty,
22231 but the logic is tricky enough that it's better to make the code
22232 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
22233 - Fix a memory leak when trying to launch a DNS request when the
22234 network is disabled or the nameservers are unconfigurable. Fixes
22235 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
22236 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
22237 - Don't hold a Windows file handle open for every file mapping;
22238 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
22240 - Avoid O(n^2) performance characteristics when parsing a large
22241 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
22242 - Format more doubles with %f, not %lf. Patch from grarpamp to make
22243 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
22245 - Make our replacement implementation of strtok_r() compatible with
22246 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
22247 bugfix on 0.2.2.1-alpha.
22248 - Fix a NULL-pointer dereference on a badly formed
22249 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
22250 bugfix on 0.2.2.9-alpha.
22251 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
22252 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
22253 - Defensively refactor rend_mid_rendezvous() so that protocol
22254 violations and length checks happen in the beginning. Fixes
22256 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
22257 that IPv6 stuff will compile on MSVC, and compilation issues
22258 will be easier to track down. Fixes bug 5861.
22260 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
22261 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
22262 resource exhaustion, so that clients can adjust their load to
22263 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
22264 started using END_STREAM_REASON_RESOURCELIMIT.
22265 - Don't check for whether the address we're using for outbound
22266 connections has changed until after the outbound connection has
22267 completed. On Windows, getsockname() doesn't succeed until the
22268 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
22269 - If the configuration tries to set MyFamily on a bridge, refuse to
22270 do so, and warn about the security implications. Fixes bug 4657;
22271 bugfix on 0.2.0.3-alpha.
22272 - If the client fails to set a reasonable set of ciphersuites
22273 during its v2 handshake renegotiation, allow the renegotiation to
22274 continue nevertheless (i.e. send all the required certificates).
22275 Fixes bug 4591; bugfix on 0.2.0.20-rc.
22276 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
22277 option is set to 0 (which Vidalia version 0.2.16 now does when
22278 a SAVECONF attempt fails), perform other actions that SIGHUP
22279 usually causes (like reopening the logs). Fixes bug 5095; bugfix
22281 - If we fail to write a microdescriptor to the disk cache, do not
22282 continue replacing the old microdescriptor file. Fixes bug 2954;
22283 bugfix on 0.2.2.6-alpha.
22284 - Exit nodes don't need to fetch certificates for authorities that
22285 they don't recognize; only directory authorities, bridges,
22286 and caches need to do that. Fixes part of bug 2297; bugfix on
22288 - Correctly handle checking the permissions on the parent
22289 directory of a control socket in the root directory. Bug found
22290 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
22292 - When told to add a bridge with the same digest as a preexisting
22293 bridge but a different addr:port, change the addr:port as
22294 requested. Previously we would not notice the change. Fixes half
22295 of bug 5603; fix on 0.2.2.26-beta.
22296 - End AUTHCHALLENGE error messages (in the control protocol) with
22297 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
22299 o Minor bugfixes (on 0.2.3.x):
22300 - Turn an assertion (that the number of handshakes received as a
22301 server is not < 1) into a warning. Fixes bug 4873; bugfix on
22303 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
22304 we had reversed them when the answer was cached.) Fixes bug
22305 5723; bugfix on 0.2.3.1-alpha.
22306 - Work correctly on Linux systems with accept4 support advertised in
22307 their headers, but without accept4 support in the kernel. Fix
22308 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
22309 - When told to add a bridge with the same addr:port as a preexisting
22310 bridge but a different transport, change the transport as
22311 requested. Previously we would not notice the change. Fixes half
22312 of bug 5603; fix on 0.2.3.2-alpha.
22313 - Avoid a "double-reply" warning when replying to a SOCKS request
22314 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
22315 bugfix on 0.2.3.4-alpha.
22316 - Fix a bug where a bridge authority crashes if it has seen no
22317 directory requests when it's time to write statistics to disk.
22318 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
22320 - Don't try to open non-control listeners when DisableNetwork is set.
22321 Previously, we'd open all listeners, then immediately close them.
22322 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
22323 - Don't abort the managed proxy protocol if the managed proxy
22324 sends us an unrecognized line; ignore it instead. Fixes bug
22325 5910; bugfix on 0.2.3.9-alpha.
22326 - Fix a compile warning in crypto.c when compiling with clang 3.1.
22327 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
22328 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
22329 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
22330 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
22331 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
22332 - Resolve numerous small warnings and build issues with MSVC. Resolves
22335 o Documentation fixes:
22336 - Improve the manual's documentation for the NT Service command-line
22337 options. Addresses ticket 3964.
22338 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
22339 - Document the changes to the ORPort and DirPort options, and the
22340 fact that {OR/Dir}ListenAddress is now unnecessary (and
22341 therefore deprecated). Resolves ticket 5597.
22344 - Remove the torrc.bridge file: we don't use it for anything, and
22345 it had become badly desynchronized from torrc.sample. Resolves
22349 Changes in version 0.2.2.36 - 2012-05-24
22350 Tor 0.2.2.36 updates the addresses for two of the eight directory
22351 authorities, fixes some potential anonymity and security issues,
22352 and fixes several crash bugs.
22354 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
22355 known flaws, and nobody should be using them. You should upgrade. If
22356 you're using a Linux or BSD and its packages are obsolete, stop using
22357 those packages and upgrade anyway.
22359 o Directory authority changes:
22360 - Change IP address for maatuska (v3 directory authority).
22361 - Change IP address for ides (v3 directory authority), and rename
22365 - When building or running with any version of OpenSSL earlier
22366 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22367 versions have a bug (CVE-2011-4576) in which their block cipher
22368 padding includes uninitialized data, potentially leaking sensitive
22369 information to any peer with whom they make a SSLv3 connection. Tor
22370 does not use SSL v3 by default, but a hostile client or server
22371 could force an SSLv3 connection in order to gain information that
22372 they shouldn't have been able to get. The best solution here is to
22373 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22374 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22375 to make sure that the bug can't happen.
22376 - Never use a bridge or a controller-supplied node as an exit, even
22377 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22378 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22379 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22380 - Only build circuits if we have a sufficient threshold of the total
22381 descriptors that are marked in the consensus with the "Exit"
22382 flag. This mitigates an attack proposed by wanoskarnet, in which
22383 all of a client's bridges collude to restrict the exit nodes that
22384 the client knows about. Fixes bug 5343.
22385 - Provide controllers with a safer way to implement the cookie
22386 authentication mechanism. With the old method, if another locally
22387 running program could convince a controller that it was the Tor
22388 process, then that program could trick the controller into telling
22389 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22390 authentication method uses a challenge-response approach to prevent
22391 this attack. Fixes bug 5185; implements proposal 193.
22394 - Avoid logging uninitialized data when unable to decode a hidden
22395 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22396 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22397 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22399 - Fix builds when the path to sed, openssl, or sha1sum contains
22400 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22402 - Correct our replacements for the timeradd() and timersub() functions
22403 on platforms that lack them (for example, Windows). The timersub()
22404 function is used when expiring circuits, while timeradd() is
22405 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
22406 bugfix on 0.2.2.24-alpha.
22407 - Fix the SOCKET_OK test that we use to tell when socket
22408 creation fails so that it works on Win64. Fixes part of bug 4533;
22409 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
22412 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
22413 Fixes bug 5346; bugfix on 0.0.8pre3.
22414 - Make our number-parsing functions always treat too-large values
22415 as an error, even when those values exceed the width of the
22416 underlying type. Previously, if the caller provided these
22417 functions with minima or maxima set to the extreme values of the
22418 underlying integer type, these functions would return those
22419 values on overflow rather than treating overflow as an error.
22420 Fixes part of bug 5786; bugfix on 0.0.9.
22421 - Older Linux kernels erroneously respond to strange nmap behavior
22422 by having accept() return successfully with a zero-length
22423 socket. When this happens, just close the connection. Previously,
22424 we would try harder to learn the remote address: but there was
22425 no such remote address to learn, and our method for trying to
22426 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
22427 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
22428 - Correct parsing of certain date types in parse_http_time().
22429 Without this patch, If-Modified-Since would behave
22430 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
22431 Esteban Manchado Velázques.
22432 - Change the BridgePassword feature (part of the "bridge community"
22433 design, which is not yet implemented) to use a time-independent
22434 comparison. The old behavior might have allowed an adversary
22435 to use timing to guess the BridgePassword value. Fixes bug 5543;
22436 bugfix on 0.2.0.14-alpha.
22437 - Detect and reject certain misformed escape sequences in
22438 configuration values. Previously, these values would cause us
22439 to crash if received in a torrc file or over an authenticated
22440 control port. Bug found by Esteban Manchado Velázquez, and
22441 independently by Robert Connolly from Matta Consulting who further
22442 noted that it allows a post-authentication heap overflow. Patch
22443 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
22444 bugfix on 0.2.0.16-alpha.
22445 - Fix a compile warning when using the --enable-openbsd-malloc
22446 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
22447 - During configure, detect when we're building with clang version
22448 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
22449 CFLAGS. clang doesn't support them yet.
22450 - When sending an HTTP/1.1 proxy request, include a Host header.
22451 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
22452 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
22453 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
22454 - If we hit the error case where routerlist_insert() replaces an
22455 existing (old) server descriptor, make sure to remove that
22456 server descriptor from the old_routers list. Fix related to bug
22457 1776. Bugfix on 0.2.2.18-alpha.
22459 o Minor bugfixes (documentation and log messages):
22460 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
22461 Fixes bug 4856; bugfix on Tor 0.0.6.
22462 - Update "ClientOnly" man page entry to explain that there isn't
22463 really any point to messing with it. Resolves ticket 5005.
22464 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
22465 directory authority option (introduced in Tor 0.2.2.34).
22466 - Downgrade the "We're missing a certificate" message from notice
22467 to info: people kept mistaking it for a real problem, whereas it
22468 is seldom the problem even when we are failing to bootstrap. Fixes
22469 bug 5067; bugfix on 0.2.0.10-alpha.
22470 - Correctly spell "connect" in a log message on failure to create a
22471 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
22472 - Clarify the behavior of MaxCircuitDirtiness with hidden service
22473 circuits. Fixes issue 5259.
22476 - Directory authorities now reject versions of Tor older than
22477 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
22478 inclusive. These versions accounted for only a small fraction of
22479 the Tor network, and have numerous known security issues. Resolves
22481 - Update to the May 1 2012 Maxmind GeoLite Country database.
22484 - When sending or relaying a RELAY_EARLY cell, we used to convert
22485 it to a RELAY cell if the connection was using the v1 link
22486 protocol. This was a workaround for older versions of Tor, which
22487 didn't handle RELAY_EARLY cells properly. Now that all supported
22488 versions can handle RELAY_EARLY cells, and now that we're enforcing
22489 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
22490 remove this workaround. Addresses bug 4786.
22493 Changes in version 0.2.3.15-alpha - 2012-04-30
22494 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
22495 the development branch build on Windows again.
22497 o Minor bugfixes (on 0.2.2.x and earlier):
22498 - Make sure that there are no unhandled pending TLS errors before
22499 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
22500 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
22501 Bugfix on 0.1.0.5-rc; fixes bug 4528.
22502 - Fix an assert that directory authorities could trigger on sighup
22503 during some configuration state transitions. We now don't treat
22504 it as a fatal error when the new descriptor we just generated in
22505 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
22506 - After we pick a directory mirror, we would refuse to use it if
22507 it's in our ExcludeExitNodes list, resulting in mysterious failures
22508 to bootstrap for people who just wanted to avoid exiting from
22509 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
22510 - When building with --enable-static-tor on OpenBSD, do not
22511 erroneously attempt to link -lrt. Fixes bug 5103.
22513 o Minor bugfixes (on 0.2.3.x):
22514 - When Tor is built with kernel headers from a recent (last few
22515 years) Linux kernel, do not fail to run on older (pre-2.6.28
22516 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
22517 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
22518 and 0.2.3.12-alpha.
22519 - Fix compilation with miniupnpc version 1.6; patch from
22520 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
22521 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
22522 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
22523 - Fix compilation on platforms without unistd.h, or where environ
22524 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
22527 - Directory authorities are now a little more lenient at accepting
22528 older router descriptors, or newer router descriptors that don't
22529 make big changes. This should help ameliorate past and future
22530 issues where routers think they have uploaded valid descriptors,
22531 but the authorities don't think so. Fix for ticket 2479.
22532 - Make the code that clients use to detect an address change be
22533 IPv6-aware, so that it won't fill clients' logs with error
22534 messages when trying to get the IPv4 address of an IPv6
22535 connection. Implements ticket 5537.
22537 o Removed features:
22538 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
22539 authorities needed to use it for a while to keep the network working
22540 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
22541 that was six months ago. As of now, it should no longer be needed
22545 Changes in version 0.2.3.14-alpha - 2012-04-23
22546 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
22547 candidate. It also dramatically speeds up AES: fast relays should
22548 consider switching to the newer OpenSSL library.
22550 o Directory authority changes:
22551 - Change IP address for ides (v3 directory authority), and rename
22555 - Avoid logging uninitialized data when unable to decode a hidden
22556 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22557 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22558 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22560 - If authorities are unable to get a v2 consensus document from other
22561 directory authorities, they no longer fall back to fetching
22562 them from regular directory caches. Fixes bug 5635; bugfix on
22563 0.2.2.26-beta, where routers stopped downloading v2 consensus
22564 documents entirely.
22565 - When we start a Tor client with a normal consensus already cached,
22566 be willing to download a microdescriptor consensus. Fixes bug 4011;
22567 fix on 0.2.3.1-alpha.
22569 o Major features (performance):
22570 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
22571 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
22572 vectorized AES implementations as appropriate. These can be much,
22573 much faster than other AES implementations.
22575 o Minor bugfixes (0.2.2.x and earlier):
22576 - Don't launch more than 10 service-side introduction-point circuits
22577 for a hidden service in five minutes. Previously, we would consider
22578 launching more introduction-point circuits if at least one second
22579 had passed without any introduction-point circuits failing. Fixes
22580 bug 4607; bugfix on 0.0.7pre1.
22581 - Change the BridgePassword feature (part of the "bridge community"
22582 design, which is not yet implemented) to use a time-independent
22583 comparison. The old behavior might have allowed an adversary
22584 to use timing to guess the BridgePassword value. Fixes bug 5543;
22585 bugfix on 0.2.0.14-alpha.
22586 - Enforce correct return behavior of tor_vsscanf() when the '%%'
22587 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
22588 - When sending an HTTP/1.1 proxy request, include a Host header.
22589 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
22590 - Don't log that we have "decided to publish new relay descriptor"
22591 unless we are actually publishing a descriptor. Fixes bug 3942;
22592 bugfix on 0.2.2.28-beta.
22594 o Minor bugfixes (0.2.3.x):
22595 - Fix a bug where a bridge authority crashes (on a failed assert)
22596 if it has seen no directory requests when it's time to write
22597 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
22598 - Fix bug stomping on ORPort option NoListen and ignoring option
22599 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
22600 - In the testsuite, provide a large enough buffer in the tor_sscanf
22601 unit test. Otherwise we'd overrun that buffer and crash during
22602 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
22604 - Make sure we create the keys directory if it doesn't exist and we're
22605 about to store the dynamic Diffie-Hellman parameters. Fixes bug
22606 5572; bugfix on 0.2.3.13-alpha.
22607 - Fix a small memory leak when trying to decode incorrect base16
22608 authenticator during SAFECOOKIE authentication. Found by
22609 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
22612 - Add more information to a log statement that might help track down
22613 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
22614 non-IP address" messages (or any Bug messages, for that matter!),
22615 please let us know about it.
22616 - Relays now understand an IPv6 address when they get one from a
22617 directory server. Resolves ticket 4875.
22618 - Resolve IPv6 addresses in bridge and entry statistics to country
22619 code "??" which means we at least count them. Resolves ticket 5053;
22620 improves on 0.2.3.9-alpha.
22621 - Update to the April 3 2012 Maxmind GeoLite Country database.
22622 - Begin a doc/state-contents.txt file to explain the contents of
22623 the Tor state file. Fixes bug 2987.
22625 o Default torrc changes:
22626 - Stop listing "socksport 9050" in torrc.sample. We open a socks
22627 port on 9050 by default anyway, so this should not change anything
22629 - Stop mentioning the deprecated *ListenAddress options in
22630 torrc.sample. Fixes bug 5438.
22631 - Document unit of bandwidth related options in sample torrc.
22634 o Removed features:
22635 - The "torify" script no longer supports the "tsocks" socksifier
22636 tool, since tsocks doesn't support DNS and UDP right for Tor.
22637 Everyone should be using torsocks instead. Fixes bugs 3530 and
22638 5180. Based on a patch by "ugh".
22640 o Code refactoring:
22641 - Change the symmetric cipher interface so that creating and
22642 initializing a stream cipher are no longer separate functions.
22643 - Remove all internal support for unpadded RSA. We never used it, and
22644 it would be a bad idea to start.
22647 Changes in version 0.2.3.13-alpha - 2012-03-26
22648 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
22649 in managed pluggable transports, as well as providing other cleanups
22650 that get us closer to a release candidate.
22652 o Directory authority changes:
22653 - Change IP address for maatuska (v3 directory authority).
22656 - Provide controllers with a safer way to implement the cookie
22657 authentication mechanism. With the old method, if another locally
22658 running program could convince a controller that it was the Tor
22659 process, then that program could trick the controller into telling
22660 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22661 authentication method uses a challenge-response approach to prevent
22662 this attack. Fixes bug 5185, implements proposal 193.
22663 - Never use a bridge or a controller-supplied node as an exit, even
22664 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22665 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22666 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22667 - Only build circuits if we have a sufficient threshold of the total
22668 descriptors that are marked in the consensus with the "Exit"
22669 flag. This mitigates an attack proposed by wanoskarnet, in which
22670 all of a client's bridges collude to restrict the exit nodes that
22671 the client knows about. Fixes bug 5343.
22673 o Major bugfixes (on Tor 0.2.3.x):
22674 - Avoid an assert when managed proxies like obfsproxy are configured,
22675 and we receive HUP signals or setconf attempts too rapidly. This
22676 situation happens most commonly when Vidalia tries to attach to
22677 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
22678 bugfix on 0.2.3.6-alpha.
22679 - Fix a relay-side pluggable transports bug where managed proxies were
22680 unreachable from the Internet, because Tor asked them to bind on
22681 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
22682 - Stop discarding command-line arguments when TestingTorNetwork
22683 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
22684 0.2.3.9-alpha, where task 4552 added support for two layers of
22686 - Resume allowing the unit tests to run in gdb. This was accidentally
22687 made impossible when the DisableDebuggerAttachment option was
22688 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
22689 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
22690 0.2.3.11-alpha. Reported by Anthony G. Basile.
22692 o Minor bugfixes (on 0.2.2.x and earlier):
22693 - Ensure we don't cannibalize circuits that are longer than three hops
22694 already, so we don't end up making circuits with 5 or more
22695 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
22696 0.1.0.1-rc which introduced cannibalization.
22697 - Detect and reject certain misformed escape sequences in
22698 configuration values. Previously, these values would cause us
22699 to crash if received in a torrc file or over an authenticated
22700 control port. Bug found by Esteban Manchado Velázquez, and
22701 independently by Robert Connolly from Matta Consulting who further
22702 noted that it allows a post-authentication heap overflow. Patch
22703 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
22704 bugfix on 0.2.0.16-alpha.
22705 - Fix a compile warning when using the --enable-openbsd-malloc
22706 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
22707 - Directory caches no longer refuse to clean out descriptors because
22708 of missing v2 networkstatus documents, unless they're configured
22709 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
22710 0.2.2.26-beta. Patch by Daniel Bryg.
22711 - Update to the latest version of the tinytest unit testing framework.
22712 This includes a couple of bugfixes that can be relevant for
22713 running forked unit tests on Windows, and removes all reserved
22716 o Minor bugfixes (on 0.2.3.x):
22717 - On a failed pipe() call, don't leak file descriptors. Fixes bug
22718 4296; bugfix on 0.2.3.1-alpha.
22719 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
22720 until after we have received a CERTS cell. Fixes bug 4361; bugfix
22721 on 0.2.3.6-alpha. Patch by "frosty".
22722 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
22723 option, so that the IP stack doesn't decide to use it for IPv4
22724 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
22725 - Ensure that variables set in Tor's environment cannot override
22726 environment variables that Tor passes to a managed
22727 pluggable-transport proxy. Previously, Tor would pass every
22728 variable in its environment to managed proxies along with the new
22729 ones, in such a way that on many operating systems, the inherited
22730 environment variables would override those which Tor tried to
22731 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
22732 bugfix on 0.2.3.9-alpha for Windows.
22735 - A wide variety of new unit tests by Esteban Manchado Velázquez.
22736 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
22737 - Update to the March 6 2012 Maxmind GeoLite Country database.
22740 Changes in version 0.2.3.12-alpha - 2012-02-13
22741 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
22742 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
22743 when Tor is configured to use a pluggable transport like obfsproxy.
22746 - Fix builds when the path to sed, openssl, or sha1sum contains
22747 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22749 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
22750 connections. This change should allow busy exit relays to stop
22751 running out of available sockets as quickly. Fixes bug 4950;
22752 bugfix on 0.2.2.26-beta.
22753 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
22754 would ask the bridge for microdescriptors, which are only supported
22755 in 0.2.3.x, and then fail to bootstrap when it didn't get the
22756 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
22757 - Properly set up obfsproxy's environment when in managed mode. The
22758 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
22759 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
22760 5076 and 5082; bugfix on 0.2.3.6-alpha.
22763 - Use the dead_strip option when building Tor on OS X. This reduces
22764 binary size by almost 19% when linking openssl and libevent
22765 statically, which we do for Tor Browser Bundle.
22766 - Fix broken URLs in the sample torrc file, and tell readers about
22767 the OutboundBindAddress, ExitPolicyRejectPrivate, and
22768 PublishServerDescriptor options. Addresses bug 4652.
22769 - Update to the February 7 2012 Maxmind GeoLite Country database.
22772 - Downgrade the "We're missing a certificate" message from notice
22773 to info: people kept mistaking it for a real problem, whereas it
22774 is seldom the problem even when we are failing to bootstrap. Fixes
22775 bug 5067; bugfix on 0.2.0.10-alpha.
22776 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
22777 managed pluggable transport server proxy's environment.
22778 Previously, we would put it there, even though Tor doesn't
22779 implement an 'extended server port' yet, and even though Tor
22780 almost certainly isn't listening at that address. For now, we set
22781 it to an empty string to avoid crashing older obfsproxies. Bugfix
22783 - Log the heartbeat message every HeartbeatPeriod seconds, not every
22784 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
22785 0.2.3.1-alpha. Bug reported by Scott Bennett.
22786 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
22787 bugfix on 0.2.3.11-alpha.
22788 - Update "ClientOnly" man page entry to explain that there isn't
22789 really any point to messing with it. Resolves ticket 5005.
22790 - Use the correct CVE number for CVE-2011-4576 in our comments and
22791 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
22794 o Code simplifications and refactoring:
22795 - Use the _WIN32 macro throughout our code to detect Windows.
22796 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
22800 Changes in version 0.2.3.11-alpha - 2012-01-22
22801 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
22802 the last step of the plan to limit maximum circuit length, includes
22803 a wide variety of hidden service performance and correctness fixes,
22804 works around an OpenSSL security flaw if your distro is too stubborn
22805 to upgrade, and fixes a bunch of smaller issues.
22808 - Now that Tor 0.2.0.x is completely deprecated, enable the final
22809 part of "Proposal 110: Avoiding infinite length circuits" by
22810 refusing all circuit-extend requests that do not use a relay_early
22811 cell. This change helps Tor resist a class of denial-of-service
22812 attacks by limiting the maximum circuit length.
22813 - Adjust the number of introduction points that a hidden service
22814 will try to maintain based on how long its introduction points
22815 remain in use and how many introductions they handle. Fixes
22817 - Try to use system facilities for enumerating local interface
22818 addresses, before falling back to our old approach (which was
22819 binding a UDP socket, and calling getsockname() on it). That
22820 approach was scaring OS X users whose draconian firewall
22821 software warned about binding to UDP sockets, regardless of
22822 whether packets were sent. Now we try to use getifaddrs(),
22823 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
22824 system supports. Resolves ticket 1827.
22826 o Major security workaround:
22827 - When building or running with any version of OpenSSL earlier
22828 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22829 versions have a bug (CVE-2011-4576) in which their block cipher
22830 padding includes uninitialized data, potentially leaking sensitive
22831 information to any peer with whom they make a SSLv3 connection. Tor
22832 does not use SSL v3 by default, but a hostile client or server
22833 could force an SSLv3 connection in order to gain information that
22834 they shouldn't have been able to get. The best solution here is to
22835 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22836 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22837 to make sure that the bug can't happen.
22840 - Fix the SOCKET_OK test that we use to tell when socket
22841 creation fails so that it works on Win64. Fixes part of bug 4533;
22842 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
22843 - Correct our replacements for the timeradd() and timersub() functions
22844 on platforms that lack them (for example, Windows). The timersub()
22845 function is used when expiring circuits, while timeradd() is
22846 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
22847 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
22848 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
22849 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
22850 bug at runtime, not compile time, because some distributions hack
22851 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
22852 on 0.2.3.9-alpha. Found by Pascal.
22854 o Minor features (controller):
22855 - Use absolute path names when reporting the torrc filename in the
22856 control protocol, so a controller can more easily find the torrc
22857 file. Resolves bug 1101.
22858 - Extend the control protocol to report flags that control a circuit's
22859 path selection in CIRC events and in replies to 'GETINFO
22860 circuit-status'. Implements part of ticket 2411.
22861 - Extend the control protocol to report the hidden service address
22862 and current state of a hidden-service-related circuit in CIRC
22863 events and in replies to 'GETINFO circuit-status'. Implements part
22865 - When reporting the path to the cookie file to the controller,
22866 give an absolute path. Resolves ticket 4881.
22867 - Allow controllers to request an event notification whenever a
22868 circuit is cannibalized or its purpose is changed. Implements
22869 part of ticket 3457.
22870 - Include the creation time of a circuit in CIRC and CIRC2
22871 control-port events and the list produced by the 'GETINFO
22872 circuit-status' control-port command.
22874 o Minor features (directory authorities):
22875 - Directory authorities now reject versions of Tor older than
22876 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
22877 inclusive. These versions accounted for only a small fraction of
22878 the Tor network, and have numerous known security issues. Resolves
22880 - Authority operators can now vote for all relays in a given
22881 set of countries to be BadDir/BadExit/Invalid/Rejected.
22882 - Provide two consensus parameters (FastFlagMinThreshold and
22883 FastFlagMaxThreshold) to control the range of allowable bandwidths
22884 for the Fast directory flag. These allow authorities to run
22885 experiments on appropriate requirements for being a "Fast" node.
22886 The AuthDirFastGuarantee config value still applies. Implements
22888 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
22889 directory authority option (introduced in Tor 0.2.2.34).
22891 o Minor features (other):
22892 - Don't disable the DirPort when we cannot exceed our AccountingMax
22893 limit during this interval because the effective bandwidthrate is
22894 low enough. This is useful in a situation where AccountMax is only
22895 used as an additional safeguard or to provide statistics.
22896 - Prepend an informative header to generated dynamic_dh_params files.
22897 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
22898 EntryNodes will have no effect. Resolves issue 2571.
22899 - Log more useful messages when we fail to disable debugger
22901 - Log which authority we're missing votes from when we go to fetch
22902 them from the other auths.
22903 - Log (at debug level) whenever a circuit's purpose is changed.
22904 - Add missing documentation for the MaxClientCircuitsPending,
22905 UseMicrodescriptors, UserspaceIOCPBuffers, and
22906 _UseFilteringSSLBufferevents options, all introduced during
22907 the 0.2.3.x series.
22908 - Update to the January 3 2012 Maxmind GeoLite Country database.
22910 o Minor bugfixes (hidden services):
22911 - Don't close hidden service client circuits which have almost
22912 finished connecting to their destination when they reach
22913 the normal circuit-build timeout. Previously, we would close
22914 introduction circuits which are waiting for an acknowledgement
22915 from the introduction point, and rendezvous circuits which have
22916 been specified in an INTRODUCE1 cell sent to a hidden service,
22917 after the normal CBT. Now, we mark them as 'timed out', and launch
22918 another rendezvous attempt in parallel. This behavior change can
22919 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
22920 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
22921 - Don't close hidden-service-side rendezvous circuits when they
22922 reach the normal circuit-build timeout. This behavior change can
22923 be disabled using the new
22924 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
22925 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
22926 - Make sure we never mark the wrong rendezvous circuit as having
22927 had its introduction cell acknowledged by the introduction-point
22928 relay. Previously, when we received an INTRODUCE_ACK cell on a
22929 client-side hidden-service introduction circuit, we might have
22930 marked a rendezvous circuit other than the one we specified in
22931 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
22932 a warning message and interfered with the hidden service
22933 connection-establishment process. Fixes bug 4759; bugfix on
22934 0.2.3.3-alpha, when we added the stream-isolation feature which
22935 might cause Tor to open multiple rendezvous circuits for the same
22937 - Don't trigger an assertion failure when we mark a new client-side
22938 hidden-service introduction circuit for close during the process
22939 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
22942 o Minor bugfixes (log messages):
22943 - Correctly spell "connect" in a log message on failure to create a
22944 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
22946 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
22947 Fixes bug 4856; bugfix on Tor 0.0.6.
22948 - Fix the log message describing how we work around discovering
22949 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
22950 4837; bugfix on 0.2.2.9-alpha.
22951 - When logging about a disallowed .exit name, do not also call it
22952 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
22954 o Minor bugfixes (build fixes):
22955 - During configure, detect when we're building with clang version
22956 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
22957 CFLAGS. clang doesn't support them yet.
22958 - During configure, search for library containing cos function as
22959 libm lives in libcore on some platforms (BeOS/Haiku). Linking
22960 against libm was hard-coded before. Fixes the first part of bug
22961 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
22963 - Detect attempts to build Tor on (as yet hypothetical) versions
22964 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
22965 fix for bug 4533. Bugfix on 0.2.2.28-beta.
22966 - Preprocessor directives should not be put inside the arguments
22967 of a macro. This would break compilation with GCC releases prior
22968 to version 3.3. We would never recommend such an old GCC version,
22969 but it is apparently required for binary compatibility on some
22970 platforms (namely, certain builds of Haiku). Fixes the other part
22971 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
22974 o Minor bugfixes (other):
22975 - Older Linux kernels erroneously respond to strange nmap behavior
22976 by having accept() return successfully with a zero-length
22977 socket. When this happens, just close the connection. Previously,
22978 we would try harder to learn the remote address: but there was
22979 no such remote address to learn, and our method for trying to
22980 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
22981 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
22982 - Fix null-pointer access that could occur if TLS allocation failed.
22983 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
22984 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
22985 accidentally been reverted.
22986 - Fix our implementation of crypto_random_hostname() so it can't
22987 overflow on ridiculously large inputs. (No Tor version has ever
22988 provided this kind of bad inputs, but let's be correct in depth.)
22989 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
22990 - Find more places in the code that should have been testing for
22991 invalid sockets using the SOCKET_OK macro. Required for a fix
22992 for bug 4533. Bugfix on 0.2.2.28-beta.
22993 - Fix an assertion failure when, while running with bufferevents, a
22994 connection finishes connecting after it is marked for close, but
22995 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
22996 - test_util_spawn_background_ok() hardcoded the expected value
22997 for ENOENT to 2. This isn't portable as error numbers are
22998 platform specific, and particularly the hurd has ENOENT at
22999 0x40000002. Construct expected string at runtime, using the correct
23000 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
23001 - Reject attempts to disable DisableDebuggerAttachment while Tor is
23002 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
23003 - Use an appropriate-width type for sockets in tor-fw-helper on
23004 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
23007 - When sending or relaying a RELAY_EARLY cell, we used to convert
23008 it to a RELAY cell if the connection was using the v1 link
23009 protocol. This was a workaround for older versions of Tor, which
23010 didn't handle RELAY_EARLY cells properly. Now that all supported
23011 versions can handle RELAY_EARLY cells, and now that we're enforcing
23012 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
23013 remove this workaround. Addresses bug 4786.
23015 o Code simplifications and refactoring:
23016 - Use OpenSSL's built-in SSL_state_string_long() instead of our
23017 own homebrewed ssl_state_to_string() replacement. Patch from
23018 Emile Snyder. Fixes bug 4653.
23019 - Use macros to indicate OpenSSL versions, so we don't need to worry
23020 about accidental hexadecimal bit shifts.
23021 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
23023 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
23024 - Use the smartlist_add_asprintf() alias more consistently.
23025 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
23026 invalid value, rather than just -1.
23027 - Rename a handful of old identifiers, mostly related to crypto
23028 structures and crypto functions. By convention, our "create an
23029 object" functions are called "type_new()", our "free an object"
23030 functions are called "type_free()", and our types indicate that
23031 they are types only with a final "_t". But a handful of older
23032 types and functions broke these rules, with function names like
23033 "type_create" or "subsystem_op_type", or with type names like
23037 Changes in version 0.2.3.10-alpha - 2011-12-16
23038 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
23039 Tor's buffers code. Absolutely everybody should upgrade.
23041 The bug relied on an incorrect calculation when making data continuous
23042 in one of our IO buffers, if the first chunk of the buffer was
23043 misaligned by just the wrong amount. The miscalculation would allow an
23044 attacker to overflow a piece of heap-allocated memory. To mount this
23045 attack, the attacker would need to either open a SOCKS connection to
23046 Tor's SocksPort (usually restricted to localhost), or target a Tor
23047 instance configured to make its connections through a SOCKS proxy
23048 (which Tor does not do by default).
23050 Good security practice requires that all heap-overflow bugs should be
23051 presumed to be exploitable until proven otherwise, so we are treating
23052 this as a potential code execution attack. Please upgrade immediately!
23053 This bug does not affect bufferevents-based builds of Tor. Special
23054 thanks to "Vektor" for reporting this issue to us!
23056 This release also contains a few minor bugfixes for issues discovered
23060 - Fix a heap overflow bug that could occur when trying to pull
23061 data into the first chunk of a buffer, when that chunk had
23062 already had some data drained from it. Fixes CVE-2011-2778;
23063 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23066 - If we can't attach streams to a rendezvous circuit when we
23067 finish connecting to a hidden service, clear the rendezvous
23068 circuit's stream-isolation state and try to attach streams
23069 again. Previously, we cleared rendezvous circuits' isolation
23070 state either too early (if they were freshly built) or not at all
23071 (if they had been built earlier and were cannibalized). Bugfix on
23072 0.2.3.3-alpha; fixes bug 4655.
23073 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
23074 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
23075 - Fix an assertion failure when a relay with accounting enabled
23076 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
23079 - Update to the December 6 2011 Maxmind GeoLite Country database.
23082 Changes in version 0.2.2.35 - 2011-12-16
23083 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
23084 buffers code. Absolutely everybody should upgrade.
23086 The bug relied on an incorrect calculation when making data continuous
23087 in one of our IO buffers, if the first chunk of the buffer was
23088 misaligned by just the wrong amount. The miscalculation would allow an
23089 attacker to overflow a piece of heap-allocated memory. To mount this
23090 attack, the attacker would need to either open a SOCKS connection to
23091 Tor's SocksPort (usually restricted to localhost), or target a Tor
23092 instance configured to make its connections through a SOCKS proxy
23093 (which Tor does not do by default).
23095 Good security practice requires that all heap-overflow bugs should be
23096 presumed to be exploitable until proven otherwise, so we are treating
23097 this as a potential code execution attack. Please upgrade immediately!
23098 This bug does not affect bufferevents-based builds of Tor. Special
23099 thanks to "Vektor" for reporting this issue to us!
23101 Tor 0.2.2.35 also fixes several bugs in previous versions, including
23102 crash bugs for unusual configurations, and a long-term bug that
23103 would prevent Tor from starting on Windows machines with draconian
23106 With this release, we remind everyone that 0.2.0.x has reached its
23107 formal end-of-life. Those Tor versions have many known flaws, and
23108 nobody should be using them. You should upgrade -- ideally to the
23109 0.2.2.x series. If you're using a Linux or BSD and its packages are
23110 obsolete, stop using those packages and upgrade anyway.
23112 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
23113 longer receive support after some time in early 2012.
23116 - Fix a heap overflow bug that could occur when trying to pull
23117 data into the first chunk of a buffer, when that chunk had
23118 already had some data drained from it. Fixes CVE-2011-2778;
23119 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23120 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
23121 that it doesn't attempt to allocate a socketpair. This could cause
23122 some problems on Windows systems with overzealous firewalls. Fix for
23123 bug 4457; workaround for Libevent versions 2.0.1-alpha through
23125 - If we mark an OR connection for close based on a cell we process,
23126 don't process any further cells on it. We already avoid further
23127 reads on marked-for-close connections, but now we also discard the
23128 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
23129 which was the first version where we might mark a connection for
23130 close based on processing a cell on it.
23131 - Correctly sanity-check that we don't underflow on a memory
23132 allocation (and then assert) for hidden service introduction
23133 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23134 bugfix on 0.2.1.5-alpha.
23135 - Fix a memory leak when we check whether a hidden service
23136 descriptor has any usable introduction points left. Fixes bug
23137 4424. Bugfix on 0.2.2.25-alpha.
23138 - Don't crash when we're running as a relay and don't have a GeoIP
23139 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
23140 we've had in the 0.2.3.x branch already.
23141 - When running as a client, do not print a misleading (and plain
23142 wrong) log message that we're collecting "directory request"
23143 statistics: clients don't collect statistics. Also don't create a
23144 useless (because empty) stats file in the stats/ directory. Fixes
23145 bug 4353; bugfix on 0.2.2.34.
23148 - Detect failure to initialize Libevent. This fix provides better
23149 detection for future instances of bug 4457.
23150 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
23151 function. This was eating up hideously large amounts of time on some
23152 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
23153 - Resolve an integer overflow bug in smartlist_ensure_capacity().
23154 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23156 - Don't warn about unused log_mutex in log.c when building with
23157 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
23158 0.1.0.6-rc which introduced --disable-threads.
23159 - When configuring, starting, or stopping an NT service, stop
23160 immediately after the service configuration attempt has succeeded
23161 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
23162 - When sending a NETINFO cell, include the original address
23163 received for the other side, not its canonical address. Found
23164 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
23165 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
23166 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
23167 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
23168 occurred when a client tried to fetch a descriptor for a bridge
23169 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
23170 - Backport fixes for a pair of compilation warnings on Windows.
23171 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
23172 - If we had ever tried to call tor_addr_to_str on an address of
23173 unknown type, we would have done a strdup on an uninitialized
23174 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23175 Reported by "troll_un".
23176 - Correctly detect and handle transient lookup failures from
23177 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23178 Reported by "troll_un".
23179 - Fix null-pointer access that could occur if TLS allocation failed.
23180 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23181 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23182 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23185 - Add two new config options for directory authorities:
23186 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
23187 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
23188 that is always sufficient to satisfy the bandwidth requirement for
23189 the Guard flag. Now it will be easier for researchers to simulate
23190 Tor networks with different values. Resolves ticket 4484.
23191 - When Tor ignores a hidden service specified in its configuration,
23192 include the hidden service's directory in the warning message.
23193 Previously, we would only tell the user that some hidden service
23194 was ignored. Bugfix on 0.0.6; fixes bug 4426.
23195 - Update to the December 6 2011 Maxmind GeoLite Country database.
23197 o Packaging changes:
23198 - Make it easier to automate expert package builds on Windows,
23199 by removing an absolute path from makensis.exe command.
23202 Changes in version 0.2.1.32 - 2011-12-16
23203 Tor 0.2.1.32 backports important security and privacy fixes for
23204 oldstable. This release is intended only for package maintainers and
23205 others who cannot use the 0.2.2 stable series. All others should be
23206 using Tor 0.2.2.x or newer.
23208 The Tor 0.2.1.x series will reach formal end-of-life some time in
23209 early 2012; we will stop releasing patches for it then.
23211 o Major bugfixes (also included in 0.2.2.x):
23212 - Correctly sanity-check that we don't underflow on a memory
23213 allocation (and then assert) for hidden service introduction
23214 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23215 bugfix on 0.2.1.5-alpha.
23216 - Fix a heap overflow bug that could occur when trying to pull
23217 data into the first chunk of a buffer, when that chunk had
23218 already had some data drained from it. Fixes CVE-2011-2778;
23219 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23222 - Update to the December 6 2011 Maxmind GeoLite Country database.
23225 Changes in version 0.2.3.9-alpha - 2011-12-08
23226 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
23227 a "DisableNetwork" security feature that bundles can use to avoid
23228 touching the network until bridges are configured, moves forward on
23229 the pluggable transport design, fixes a flaw in the hidden service
23230 design that unnecessarily prevented clients with wrong clocks from
23231 reaching hidden services, and fixes a wide variety of other issues.
23234 - Clients can now connect to private bridges over IPv6. Bridges
23235 still need at least one IPv4 address in order to connect to
23236 other relays. Note that we don't yet handle the case where the
23237 user has two bridge lines for the same bridge (one IPv4, one
23238 IPv6). Implements parts of proposal 186.
23239 - New "DisableNetwork" config option to prevent Tor from launching any
23240 connections or accepting any connections except on a control port.
23241 Bundles and controllers can set this option before letting Tor talk
23242 to the rest of the network, for example to prevent any connections
23243 to a non-bridge address. Packages like Orbot can also use this
23244 option to instruct Tor to save power when the network is off.
23245 - Clients and bridges can now be configured to use a separate
23246 "transport" proxy. This approach makes the censorship arms race
23247 easier by allowing bridges to use protocol obfuscation plugins. It
23248 implements the "managed proxy" part of proposal 180 (ticket 3472).
23249 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
23250 implementation. It makes AES_CTR about 7% faster than our old one
23251 (which was about 10% faster than the one OpenSSL used to provide).
23252 Resolves ticket 4526.
23253 - Add a "tor2web mode" for clients that want to connect to hidden
23254 services non-anonymously (and possibly more quickly). As a safety
23255 measure to try to keep users from turning this on without knowing
23256 what they are doing, tor2web mode must be explicitly enabled at
23257 compile time, and a copy of Tor compiled to run in tor2web mode
23258 cannot be used as a normal Tor client. Implements feature 2553.
23259 - Add experimental support for running on Windows with IOCP and no
23260 kernel-space socket buffers. This feature is controlled by a new
23261 "UserspaceIOCPBuffers" config option (off by default), which has
23262 no effect unless Tor has been built with support for bufferevents,
23263 is running on Windows, and has enabled IOCP. This may, in the long
23264 run, help solve or mitigate bug 98.
23265 - Use a more secure consensus parameter voting algorithm. Now at
23266 least three directory authorities or a majority of them must
23267 vote on a given parameter before it will be included in the
23268 consensus. Implements proposal 178.
23271 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
23272 They used to check that the timestamp was within 30 minutes
23273 of their system clock, so they could cap the size of their
23274 replay-detection cache, but that approach unnecessarily refused
23275 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
23276 the v3 intro-point protocol (the first one which sent a timestamp
23277 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
23278 - Only use the EVP interface when AES acceleration is enabled,
23279 to avoid a 5-7% performance regression. Resolves issue 4525;
23280 bugfix on 0.2.3.8-alpha.
23282 o Privacy/anonymity features (bridge detection):
23283 - Make bridge SSL certificates a bit more stealthy by using random
23284 serial numbers, in the same fashion as OpenSSL when generating
23285 self-signed certificates. Implements ticket 4584.
23286 - Introduce a new config option "DynamicDHGroups", enabled by
23287 default, which provides each bridge with a unique prime DH modulus
23288 to be used during SSL handshakes. This option attempts to help
23289 against censors who might use the Apache DH modulus as a static
23290 identifier for bridges. Addresses ticket 4548.
23292 o Minor features (new/different config options):
23293 - New configuration option "DisableDebuggerAttachment" (on by default)
23294 to prevent basic debugging attachment attempts by other processes.
23295 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
23296 - Allow MapAddress directives to specify matches against super-domains,
23297 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
23298 Implements issue 933.
23299 - Slightly change behavior of "list" options (that is, config
23300 options that can appear more than once) when they appear both in
23301 torrc and on the command line. Previously, the command-line options
23302 would be appended to the ones from torrc. Now, the command-line
23303 options override the torrc options entirely. This new behavior
23304 allows the user to override list options (like exit policies and
23305 ports to listen on) from the command line, rather than simply
23306 appending to the list.
23307 - You can get the old (appending) command-line behavior for "list"
23308 options by prefixing the option name with a "+".
23309 - You can remove all the values for a "list" option from the command
23310 line without adding any new ones by prefixing the option name
23312 - Add experimental support for a "defaults" torrc file to be parsed
23313 before the regular torrc. Torrc options override the defaults file's
23314 options in the same way that the command line overrides the torrc.
23315 The SAVECONF controller command saves only those options which
23316 differ between the current configuration and the defaults file. HUP
23317 reloads both files. (Note: This is an experimental feature; its
23318 behavior will probably be refined in future 0.2.3.x-alpha versions
23319 to better meet packagers' needs.) Implements task 4552.
23322 - Try to make the introductory warning message that Tor prints on
23323 startup more useful for actually finding help and information.
23324 Resolves ticket 2474.
23325 - Running "make version" now displays the version of Tor that
23326 we're about to build. Idea from katmagic; resolves issue 4400.
23327 - Expire old or over-used hidden service introduction points.
23328 Required by fix for bug 3460.
23329 - Move the replay-detection cache for the RSA-encrypted parts of
23330 INTRODUCE2 cells to the introduction point data structures.
23331 Previously, we would use one replay-detection cache per hidden
23332 service. Required by fix for bug 3460.
23333 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
23334 public key replay-detection cache from 60 minutes to 5 minutes. This
23335 replay-detection cache is now used only to detect multiple
23336 INTRODUCE2 cells specifying the same rendezvous point, so we can
23337 avoid launching multiple simultaneous attempts to connect to it.
23339 o Minor bugfixes (on Tor 0.2.2.x and earlier):
23340 - Resolve an integer overflow bug in smartlist_ensure_capacity().
23341 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23343 - Fix a minor formatting issue in one of tor-gencert's error messages.
23345 - Prevent a false positive from the check-spaces script, by disabling
23346 the "whitespace between function name and (" check for functions
23348 - Fix a log message suggesting that people contact a non-existent
23349 email address. Fixes bug 3448.
23350 - Fix null-pointer access that could occur if TLS allocation failed.
23351 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23352 - Report a real bootstrap problem to the controller on router
23353 identity mismatch. Previously we just said "foo", which probably
23354 made a lot of sense at the time. Fixes bug 4169; bugfix on
23356 - If we had ever tried to call tor_addr_to_str() on an address of
23357 unknown type, we would have done a strdup() on an uninitialized
23358 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23359 Reported by "troll_un".
23360 - Correctly detect and handle transient lookup failures from
23361 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23362 Reported by "troll_un".
23363 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23364 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23365 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
23366 bug 4532; found by "troll_un".
23368 o Minor bugfixes (on Tor 0.2.3.x):
23369 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
23371 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
23372 circuit for use as a hidden service client's rendezvous point.
23373 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
23374 with help from wanoskarnet.
23375 - Restore behavior of overriding SocksPort, ORPort, and similar
23376 options from the command line. Bugfix on 0.2.3.3-alpha.
23379 - Properly handle the case where the build-tree is not the same
23380 as the source tree when generating src/common/common_sha1.i,
23381 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
23382 bugfix on 0.2.0.1-alpha.
23384 o Code simplifications, cleanups, and refactorings:
23385 - Remove the pure attribute from all functions that used it
23386 previously. In many cases we assigned it incorrectly, because the
23387 functions might assert or call impure functions, and we don't have
23388 evidence that keeping the pure attribute is worthwhile. Implements
23389 changes suggested in ticket 4421.
23390 - Remove some dead code spotted by coverity. Fixes cid 432.
23391 Bugfix on 0.2.3.1-alpha, closes bug 4637.
23394 Changes in version 0.2.3.8-alpha - 2011-11-22
23395 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
23396 socketpair-related bug that has been bothering Windows users. It adds
23397 support to serve microdescriptors to controllers, so Vidalia's network
23398 map can resume listing relays (once Vidalia implements its side),
23399 and adds better support for hardware AES acceleration. Finally, it
23400 starts the process of adjusting the bandwidth cutoff for getting the
23401 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
23402 that tiny relays harm performance more than they help network capacity.
23405 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
23406 that it doesn't attempt to allocate a socketpair. This could cause
23407 some problems on Windows systems with overzealous firewalls. Fix for
23408 bug 4457; workaround for Libevent versions 2.0.1-alpha through
23410 - Correctly sanity-check that we don't underflow on a memory
23411 allocation (and then assert) for hidden service introduction
23412 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23413 bugfix on 0.2.1.5-alpha.
23414 - Remove the artificially low cutoff of 20KB to guarantee the Fast
23415 flag. In the past few years the average relay speed has picked
23416 up, and while the "top 7/8 of the network get the Fast flag" and
23417 "all relays with 20KB or more of capacity get the Fast flag" rules
23418 used to have the same result, now the top 7/8 of the network has
23419 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
23420 - Fix a rare assertion failure when checking whether a v0 hidden
23421 service descriptor has any usable introduction points left, and
23422 we don't have enough information to build a circuit to the first
23423 intro point named in the descriptor. The HS client code in
23424 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
23425 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
23426 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
23427 - Make bridge authorities not crash when they are asked for their own
23428 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
23429 - When running as a client, do not print a misleading (and plain
23430 wrong) log message that we're collecting "directory request"
23431 statistics: clients don't collect statistics. Also don't create a
23432 useless (because empty) stats file in the stats/ directory. Fixes
23433 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
23436 - Allow Tor controllers like Vidalia to obtain the microdescriptor
23437 for a relay by identity digest or nickname. Previously,
23438 microdescriptors were only available by their own digests, so a
23439 controller would have to ask for and parse the whole microdescriptor
23440 consensus in order to look up a single relay's microdesc. Fixes
23441 bug 3832; bugfix on 0.2.3.1-alpha.
23442 - Use OpenSSL's EVP interface for AES encryption, so that all AES
23443 operations can use hardware acceleration (if present). Resolves
23446 o Minor bugfixes (on 0.2.2.x and earlier):
23447 - Detect failure to initialize Libevent. This fix provides better
23448 detection for future instances of bug 4457.
23449 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
23450 function. This was eating up hideously large amounts of time on some
23451 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
23452 - Don't warn about unused log_mutex in log.c when building with
23453 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
23454 0.1.0.6-rc which introduced --disable-threads.
23455 - Allow manual 'authenticate' commands to the controller interface
23456 from netcat (nc) as well as telnet. We were rejecting them because
23457 they didn't come with the expected whitespace at the end of the
23458 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
23459 - Fix some (not actually triggerable) buffer size checks in usage of
23460 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
23462 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
23463 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
23464 - When configuring, starting, or stopping an NT service, stop
23465 immediately after the service configuration attempt has succeeded
23466 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
23467 - When sending a NETINFO cell, include the original address
23468 received for the other side, not its canonical address. Found
23469 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
23470 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
23471 can pick them up when the tests aren't disabled. Bugfix on
23472 0.2.2.4-alpha which introduced tinytest.
23473 - Fix a memory leak when we check whether a hidden service
23474 descriptor has any usable introduction points left. Fixes bug
23475 4424. Bugfix on 0.2.2.25-alpha.
23476 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
23477 occurred when a client tried to fetch a descriptor for a bridge
23478 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
23480 o Minor bugfixes (on 0.2.3.x):
23481 - Make util unit tests build correctly with MSVC. Bugfix on
23482 0.2.3.3-alpha. Patch by Gisle Vanem.
23483 - Successfully detect AUTH_CHALLENGE cells with no recognized
23484 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
23485 Found by frosty_un.
23486 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
23487 it should still send a NETINFO cell to allow the connection to
23488 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
23490 - Log less loudly when we get an invalid authentication certificate
23491 from a source other than a directory authority: it's not unusual
23492 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
23494 - Tolerate servers with more clock skew in their authentication
23495 certificates than previously. Fixes bug 4371; bugfix on
23497 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
23498 on 0.2.3.4-alpha and 0.2.3.6-alpha.
23501 - Add two new config options for directory authorities:
23502 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
23503 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
23504 that is always sufficient to satisfy the bandwidth requirement for
23505 the Guard flag. Now it will be easier for researchers to simulate
23506 Tor networks with different values. Resolves ticket 4484.
23507 - When Tor ignores a hidden service specified in its configuration,
23508 include the hidden service's directory in the warning message.
23509 Previously, we would only tell the user that some hidden service
23510 was ignored. Bugfix on 0.0.6; fixes bug 4426.
23511 - When we fail to initialize Libevent, retry with IOCP disabled so we
23512 don't need to turn on multi-threading support in Libevent, which in
23513 turn requires a working socketpair(). This is a workaround for bug
23514 4457, which affects Libevent versions from 2.0.1-alpha through
23516 - Detect when we try to build on a platform that doesn't define
23517 AF_UNSPEC to 0. We don't work there, so refuse to compile.
23518 - Update to the November 1 2011 Maxmind GeoLite Country database.
23520 o Packaging changes:
23521 - Make it easier to automate expert package builds on Windows,
23522 by removing an absolute path from makensis.exe command.
23524 o Code simplifications and refactoring:
23525 - Remove some redundant #include directives throughout the code.
23526 Patch from Andrea Gelmini.
23527 - Unconditionally use OpenSSL's AES implementation instead of our
23528 old built-in one. OpenSSL's AES has been better for a while, and
23529 relatively few servers should still be on any version of OpenSSL
23530 that doesn't have good optimized assembly AES.
23531 - Use the name "CERTS" consistently to refer to the new cell type;
23532 we were calling it CERT in some places and CERTS in others.
23535 - Numerous new unit tests for functions in util.c and address.c by
23537 - The long-disabled benchmark tests are now split into their own
23538 ./src/test/bench binary.
23539 - The benchmark tests can now use more accurate timers than
23540 gettimeofday() when such timers are available.
23543 Changes in version 0.2.3.7-alpha - 2011-10-30
23544 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
23545 the new v3 handshake. It also resolves yet another bridge address
23549 - If we mark an OR connection for close based on a cell we process,
23550 don't process any further cells on it. We already avoid further
23551 reads on marked-for-close connections, but now we also discard the
23552 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
23553 which was the first version where we might mark a connection for
23554 close based on processing a cell on it.
23555 - Fix a double-free bug that would occur when we received an invalid
23556 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
23557 bugfix on 0.2.3.6-alpha.
23558 - Bridges no longer include their address in NETINFO cells on outgoing
23559 OR connections, to allow them to blend in better with clients.
23560 Removes another avenue for enumerating bridges. Reported by
23561 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
23562 cells were introduced.
23565 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
23566 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
23569 Changes in version 0.2.3.6-alpha - 2011-10-26
23570 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
23571 anonymity vulnerability where an attacker can deanonymize Tor
23572 users. Everybody should upgrade.
23574 This release also features support for a new v3 connection handshake
23575 protocol, and fixes to make hidden service connections more robust.
23578 - Implement a new handshake protocol (v3) for authenticating Tors to
23579 each other over TLS. It should be more resistant to fingerprinting
23580 than previous protocols, and should require less TLS hacking for
23581 future Tor implementations. Implements proposal 176.
23582 - Allow variable-length padding cells to disguise the length of
23583 Tor's TLS records. Implements part of proposal 184.
23585 o Privacy/anonymity fixes (clients):
23586 - Clients and bridges no longer send TLS certificate chains on
23587 outgoing OR connections. Previously, each client or bridge would
23588 use the same cert chain for all outgoing OR connections until
23589 its IP address changes, which allowed any relay that the client
23590 or bridge contacted to determine which entry guards it is using.
23591 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23592 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23593 no longer considers that connection as suitable for satisfying a
23594 circuit EXTEND request. Now relays can protect clients from the
23595 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23596 - Directory authorities no longer assign the Guard flag to relays
23597 that haven't upgraded to the above "refuse EXTEND requests
23598 to client connections" fix. Now directory authorities can
23599 protect clients from the CVE-2011-2768 issue even if neither
23600 the clients nor the relays have upgraded yet. There's a new
23601 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
23602 to let us transition smoothly, else tomorrow there would be no
23605 o Major bugfixes (hidden services):
23606 - Improve hidden service robustness: when an attempt to connect to
23607 a hidden service ends, be willing to refetch its hidden service
23608 descriptors from each of the HSDir relays responsible for them
23609 immediately. Previously, we would not consider refetching the
23610 service's descriptors from each HSDir for 15 minutes after the last
23611 fetch, which was inconvenient if the hidden service was not running
23612 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
23613 - When one of a hidden service's introduction points appears to be
23614 unreachable, stop trying it. Previously, we would keep trying
23615 to build circuits to the introduction point until we lost the
23616 descriptor, usually because the user gave up and restarted Tor.
23617 Partly fixes bug 3825.
23618 - Don't launch a useless circuit after failing to use one of a
23619 hidden service's introduction points. Previously, we would
23620 launch a new introduction circuit, but not set the hidden service
23621 which that circuit was intended to connect to, so it would never
23622 actually be used. A different piece of code would then create a
23623 new introduction circuit correctly. Bug reported by katmagic and
23624 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
23626 o Major bugfixes (other):
23627 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23628 that they initiated. Relays could distinguish incoming bridge
23629 connections from client connections, creating another avenue for
23630 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23631 Found by "frosty_un".
23632 - Don't update the AccountingSoftLimitHitAt state file entry whenever
23633 tor gets started. This prevents a wrong average bandwidth
23634 estimate, which would cause relays to always start a new accounting
23635 interval at the earliest possible moment. Fixes bug 2003; bugfix
23636 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
23637 immensely in tracking this bug down.
23638 - Fix a crash bug when changing node restrictions while a DNS lookup
23639 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
23642 o Minor bugfixes (on 0.2.2.x and earlier):
23643 - When a hidden service turns an extra service-side introduction
23644 circuit into a general-purpose circuit, free the rend_data and
23645 intro_key fields first, so we won't leak memory if the circuit
23646 is cannibalized for use as another service-side introduction
23647 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
23648 - Rephrase the log message emitted if the TestSocks check is
23649 successful. Patch from Fabian Keil; fixes bug 4094.
23650 - Bridges now skip DNS self-tests, to act a little more stealthily.
23651 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
23652 bridges. Patch by "warms0x".
23653 - Remove a confusing dollar sign from the example fingerprint in the
23654 man page, and also make the example fingerprint a valid one. Fixes
23655 bug 4309; bugfix on 0.2.1.3-alpha.
23656 - Fix internal bug-checking logic that was supposed to catch
23657 failures in digest generation so that it will fail more robustly
23658 if we ask for a nonexistent algorithm. Found by Coverity Scan.
23659 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
23660 - Report any failure in init_keys() calls launched because our
23661 IP address has changed. Spotted by Coverity Scan. Bugfix on
23662 0.1.1.4-alpha; fixes CID 484.
23664 o Minor bugfixes (on 0.2.3.x):
23665 - Fix a bug in configure.in that kept it from building a configure
23666 script with autoconf versions earlier than 2.61. Fixes bug 2430;
23667 bugfix on 0.2.3.1-alpha.
23668 - Don't warn users that they are exposing a client port to the
23669 Internet if they have specified an RFC1918 address. Previously,
23670 we would warn if the user had specified any non-loopback
23671 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
23672 - Fix memory leaks in the failing cases of the new SocksPort and
23673 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
23674 fixes coverity CIDs 485, 486, and 487.
23677 - When a hidden service's introduction point times out, consider
23678 trying it again during the next attempt to connect to the
23679 HS. Previously, we would not try it again unless a newly fetched
23680 descriptor contained it. Required by fixes for bugs 1297 and 3825.
23681 - The next version of Windows will be called Windows 8, and it has
23682 a major version of 6, minor version of 2. Correctly identify that
23683 version instead of calling it "Very recent version". Resolves
23684 ticket 4153; reported by funkstar.
23685 - The Bridge Authority now writes statistics on how many bridge
23686 descriptors it gave out in total, and how many unique descriptors
23687 it gave out. It also lists how often the most and least commonly
23688 fetched descriptors were given out, as well as the median and
23689 25th/75th percentile. Implements tickets 4200 and 4294.
23690 - Update to the October 4 2011 Maxmind GeoLite Country database.
23692 o Code simplifications and refactoring:
23693 - Remove some old code to remember statistics about which descriptors
23694 we've served as a directory mirror. The feature wasn't used and
23695 is outdated now that microdescriptors are around.
23696 - Rename Tor functions that turn strings into addresses, so that
23697 "parse" indicates that no hostname resolution occurs, and
23698 "lookup" indicates that hostname resolution may occur. This
23699 should help prevent mistakes in the future. Fixes bug 3512.
23702 Changes in version 0.2.2.34 - 2011-10-26
23703 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
23704 can deanonymize Tor users. Everybody should upgrade.
23706 The attack relies on four components: 1) Clients reuse their TLS cert
23707 when talking to different relays, so relays can recognize a user by
23708 the identity key in her cert. 2) An attacker who knows the client's
23709 identity key can probe each guard relay to see if that identity key
23710 is connected to that guard relay right now. 3) A variety of active
23711 attacks in the literature (starting from "Low-Cost Traffic Analysis
23712 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
23713 discover the guard relays that a Tor user visiting the website is using.
23714 4) Clients typically pick three guards at random, so the set of guards
23715 for a given user could well be a unique fingerprint for her. This
23716 release fixes components #1 and #2, which is enough to block the attack;
23717 the other two remain as open research problems. Special thanks to
23718 "frosty_un" for reporting the issue to us!
23720 Clients should upgrade so they are no longer recognizable by the TLS
23721 certs they present. Relays should upgrade so they no longer allow a
23722 remote attacker to probe them to test whether unpatched clients are
23723 currently connected to them.
23725 This release also fixes several vulnerabilities that allow an attacker
23726 to enumerate bridge relays. Some bridge enumeration attacks still
23727 remain; see for example proposal 188.
23729 o Privacy/anonymity fixes (clients):
23730 - Clients and bridges no longer send TLS certificate chains on
23731 outgoing OR connections. Previously, each client or bridge would
23732 use the same cert chain for all outgoing OR connections until
23733 its IP address changes, which allowed any relay that the client
23734 or bridge contacted to determine which entry guards it is using.
23735 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23736 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23737 no longer considers that connection as suitable for satisfying a
23738 circuit EXTEND request. Now relays can protect clients from the
23739 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23740 - Directory authorities no longer assign the Guard flag to relays
23741 that haven't upgraded to the above "refuse EXTEND requests
23742 to client connections" fix. Now directory authorities can
23743 protect clients from the CVE-2011-2768 issue even if neither
23744 the clients nor the relays have upgraded yet. There's a new
23745 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
23746 to let us transition smoothly, else tomorrow there would be no
23749 o Privacy/anonymity fixes (bridge enumeration):
23750 - Bridge relays now do their directory fetches inside Tor TLS
23751 connections, like all the other clients do, rather than connecting
23752 directly to the DirPort like public relays do. Removes another
23753 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
23754 - Bridges relays now build circuits for themselves in a more similar
23755 way to how clients build them. Removes another avenue for
23756 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
23757 when bridges were introduced.
23758 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23759 that they initiated. Relays could distinguish incoming bridge
23760 connections from client connections, creating another avenue for
23761 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23762 Found by "frosty_un".
23765 - Fix a crash bug when changing node restrictions while a DNS lookup
23766 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
23768 - Don't launch a useless circuit after failing to use one of a
23769 hidden service's introduction points. Previously, we would
23770 launch a new introduction circuit, but not set the hidden service
23771 which that circuit was intended to connect to, so it would never
23772 actually be used. A different piece of code would then create a
23773 new introduction circuit correctly. Bug reported by katmagic and
23774 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
23777 - Change an integer overflow check in the OpenBSD_Malloc code so
23778 that GCC is less likely to eliminate it as impossible. Patch
23779 from Mansour Moufid. Fixes bug 4059.
23780 - When a hidden service turns an extra service-side introduction
23781 circuit into a general-purpose circuit, free the rend_data and
23782 intro_key fields first, so we won't leak memory if the circuit
23783 is cannibalized for use as another service-side introduction
23784 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
23785 - Bridges now skip DNS self-tests, to act a little more stealthily.
23786 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
23787 bridges. Patch by "warms0x".
23788 - Fix internal bug-checking logic that was supposed to catch
23789 failures in digest generation so that it will fail more robustly
23790 if we ask for a nonexistent algorithm. Found by Coverity Scan.
23791 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
23792 - Report any failure in init_keys() calls launched because our
23793 IP address has changed. Spotted by Coverity Scan. Bugfix on
23794 0.1.1.4-alpha; fixes CID 484.
23796 o Minor bugfixes (log messages and documentation):
23797 - Remove a confusing dollar sign from the example fingerprint in the
23798 man page, and also make the example fingerprint a valid one. Fixes
23799 bug 4309; bugfix on 0.2.1.3-alpha.
23800 - The next version of Windows will be called Windows 8, and it has
23801 a major version of 6, minor version of 2. Correctly identify that
23802 version instead of calling it "Very recent version". Resolves
23803 ticket 4153; reported by funkstar.
23804 - Downgrade log messages about circuit timeout calibration from
23805 "notice" to "info": they don't require or suggest any human
23806 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
23807 bugfix on 0.2.2.14-alpha.
23810 - Turn on directory request statistics by default and include them in
23811 extra-info descriptors. Don't break if we have no GeoIP database.
23812 Backported from 0.2.3.1-alpha; implements ticket 3951.
23813 - Update to the October 4 2011 Maxmind GeoLite Country database.
23816 Changes in version 0.2.1.31 - 2011-10-26
23817 Tor 0.2.1.31 backports important security and privacy fixes for
23818 oldstable. This release is intended only for package maintainers and
23819 others who cannot use the 0.2.2 stable series. All others should be
23820 using Tor 0.2.2.x or newer.
23822 o Security fixes (also included in 0.2.2.x):
23823 - Replace all potentially sensitive memory comparison operations
23824 with versions whose runtime does not depend on the data being
23825 compared. This will help resist a class of attacks where an
23826 adversary can use variations in timing information to learn
23827 sensitive data. Fix for one case of bug 3122. (Safe memcmp
23828 implementation by Robert Ransom based partially on code by DJB.)
23829 - Fix an assert in parsing router descriptors containing IPv6
23830 addresses. This one took down the directory authorities when
23831 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
23833 o Privacy/anonymity fixes (also included in 0.2.2.x):
23834 - Clients and bridges no longer send TLS certificate chains on
23835 outgoing OR connections. Previously, each client or bridge would
23836 use the same cert chain for all outgoing OR connections until
23837 its IP address changes, which allowed any relay that the client
23838 or bridge contacted to determine which entry guards it is using.
23839 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23840 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23841 no longer considers that connection as suitable for satisfying a
23842 circuit EXTEND request. Now relays can protect clients from the
23843 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23844 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23845 that they initiated. Relays could distinguish incoming bridge
23846 connections from client connections, creating another avenue for
23847 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23848 Found by "frosty_un".
23849 - When receiving a hidden service descriptor, check that it is for
23850 the hidden service we wanted. Previously, Tor would store any
23851 hidden service descriptors that a directory gave it, whether it
23852 wanted them or not. This wouldn't have let an attacker impersonate
23853 a hidden service, but it did let directories pre-seed a client
23854 with descriptors that it didn't want. Bugfix on 0.0.6.
23855 - Avoid linkability based on cached hidden service descriptors: forget
23856 all hidden service descriptors cached as a client when processing a
23857 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
23858 - Make the bridge directory authority refuse to answer directory
23859 requests for "all" descriptors. It used to include bridge
23860 descriptors in its answer, which was a major information leak.
23861 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
23862 - Don't attach new streams to old rendezvous circuits after SIGNAL
23863 NEWNYM. Previously, we would keep using an existing rendezvous
23864 circuit if it remained open (i.e. if it were kept open by a
23865 long-lived stream, or if a new stream were attached to it before
23866 Tor could notice that it was old and no longer in use). Bugfix on
23867 0.1.1.15-rc; fixes bug 3375.
23869 o Minor bugfixes (also included in 0.2.2.x):
23870 - When we restart our relay, we might get a successful connection
23871 from the outside before we've started our reachability tests,
23872 triggering a warning: "ORPort found reachable, but I have no
23873 routerinfo yet. Failing to inform controller of success." This
23874 bug was harmless unless Tor is running under a controller
23875 like Vidalia, in which case the controller would never get a
23876 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
23878 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23879 enabled. Fixes bug 1526.
23880 - Remove undocumented option "-F" from tor-resolve: it hasn't done
23881 anything since 0.2.1.16-rc.
23882 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
23883 None of the cases where we did this before were wrong, but by making
23884 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
23885 - Fix a rare crash bug that could occur when a client was configured
23886 with a large number of bridges. Fixes bug 2629; bugfix on
23887 0.2.1.2-alpha. Bugfix by trac user "shitlei".
23888 - Correct the warning displayed when a rendezvous descriptor exceeds
23889 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
23891 - Fix an uncommon assertion failure when running with DNSPort under
23892 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
23893 - When warning about missing zlib development packages during compile,
23894 give the correct package names. Bugfix on 0.2.0.1-alpha.
23895 - Require that introduction point keys and onion keys have public
23896 exponent 65537. Bugfix on 0.2.0.10-alpha.
23897 - Do not crash when our configuration file becomes unreadable, for
23898 example due to a permissions change, between when we start up
23899 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
23901 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
23903 - Always NUL-terminate the sun_path field of a sockaddr_un before
23904 passing it to the kernel. (Not a security issue: kernels are
23905 smart enough to reject bad sockaddr_uns.) Found by Coverity;
23906 CID #428. Bugfix on Tor 0.2.0.3-alpha.
23907 - Don't stack-allocate the list of supplementary GIDs when we're
23908 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
23909 could take up to 256K, which is way too much stack. Found by
23910 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
23912 o Minor bugfixes (only in 0.2.1.x):
23913 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
23914 rely on them. Bugfix on 0.2.1.30.
23915 - Use git revisions instead of svn revisions when generating our
23916 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
23918 o Minor features (also included in 0.2.2.x):
23919 - Adjust the expiration time on our SSL session certificates to
23920 better match SSL certs seen in the wild. Resolves ticket 4014.
23921 - Allow nameservers with IPv6 address. Resolves bug 2574.
23922 - Update to the October 4 2011 Maxmind GeoLite Country database.
23925 Changes in version 0.2.3.5-alpha - 2011-09-28
23926 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
23927 bridge relays; fixes an assertion error that many users started hitting
23928 today; and adds the ability to refill token buckets more often than
23929 once per second, allowing significant performance improvements.
23932 - Bridge relays now do their directory fetches inside Tor TLS
23933 connections, like all the other clients do, rather than connecting
23934 directly to the DirPort like public relays do. Removes another
23935 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
23936 - Bridges relays now build circuits for themselves in a more similar
23937 way to how clients build them. Removes another avenue for
23938 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
23939 when bridges were introduced.
23942 - Fix an "Assertion md->held_by_node == 1 failed" error that could
23943 occur when the same microdescriptor was referenced by two node_t
23944 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
23946 o Major features (networking):
23947 - Add a new TokenBucketRefillInterval option to refill token buckets
23948 more frequently than once per second. This should improve network
23949 performance, alleviate queueing problems, and make traffic less
23950 bursty. Implements proposal 183; closes ticket 3630. Design by
23951 Florian Tschorsch and Björn Scheuermann; implementation by
23955 - Change an integer overflow check in the OpenBSD_Malloc code so
23956 that GCC is less likely to eliminate it as impossible. Patch
23957 from Mansour Moufid. Fixes bug 4059.
23959 o Minor bugfixes (usability):
23960 - Downgrade log messages about circuit timeout calibration from
23961 "notice" to "info": they don't require or suggest any human
23962 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
23963 bugfix on 0.2.2.14-alpha.
23965 o Minor features (diagnostics):
23966 - When the system call to create a listener socket fails, log the
23967 error message explaining why. This may help diagnose bug 4027.
23970 Changes in version 0.2.3.4-alpha - 2011-09-13
23971 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
23972 tweak to Tor's TLS handshake that makes relays and bridges that run
23973 this new version reachable from Iran again. It also fixes a few new
23974 bugs in 0.2.3.x, and teaches relays to recognize when they're not
23975 listed in the network consensus and republish.
23977 o Major bugfixes (also part of 0.2.2.33):
23978 - Avoid an assertion failure when reloading a configuration with
23979 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
23980 3923; bugfix on 0.2.2.25-alpha.
23982 o Minor features (security, also part of 0.2.2.33):
23983 - Check for replays of the public-key encrypted portion of an
23984 INTRODUCE1 cell, in addition to the current check for replays of
23985 the g^x value. This prevents a possible class of active attacks
23986 by an attacker who controls both an introduction point and a
23987 rendezvous point, and who uses the malleability of AES-CTR to
23988 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
23989 that these attacks are infeasible (requiring the attacker to send
23990 on the order of zettabytes of altered cells in a short interval),
23991 but we'd rather block them off in case there are any classes of
23992 this attack that we missed. Reported by Willem Pinckaers.
23994 o Minor features (also part of 0.2.2.33):
23995 - Adjust the expiration time on our SSL session certificates to
23996 better match SSL certs seen in the wild. Resolves ticket 4014.
23997 - Change the default required uptime for a relay to be accepted as
23998 a HSDir (hidden service directory) from 24 hours to 25 hours.
23999 Improves on 0.2.0.10-alpha; resolves ticket 2649.
24000 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
24001 authorities to abstain from voting on assignment of the HSDir
24002 consensus flag. Related to bug 2649.
24003 - Update to the September 6 2011 Maxmind GeoLite Country database.
24005 o Minor bugfixes (also part of 0.2.2.33):
24006 - Demote the 'replay detected' log message emitted when a hidden
24007 service receives the same Diffie-Hellman public key in two different
24008 INTRODUCE2 cells to info level. A normal Tor client can cause that
24009 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
24010 fixes part of bug 2442.
24011 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
24012 level. There is nothing that a hidden service's operator can do
24013 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
24015 - Clarify a log message specifying the characters permitted in
24016 HiddenServiceAuthorizeClient client names. Previously, the log
24017 message said that "[A-Za-z0-9+-_]" were permitted; that could have
24018 given the impression that every ASCII character between "+" and "_"
24019 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
24021 o Build fixes (also part of 0.2.2.33):
24022 - Clean up some code issues that prevented Tor from building on older
24023 BSDs. Fixes bug 3894; reported by "grarpamp".
24024 - Search for a platform-specific version of "ar" when cross-compiling.
24025 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
24028 - Fix a bug where the SocksPort option (for example) would get
24029 ignored and replaced by the default if a SocksListenAddress
24030 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
24034 - Relays now try regenerating and uploading their descriptor more
24035 frequently if they are not listed in the consensus, or if the
24036 version of their descriptor listed in the consensus is too
24037 old. This fix should prevent situations where a server declines
24038 to re-publish itself because it has done so too recently, even
24039 though the authorities decided not to list its recent-enough
24040 descriptor. Fix for bug 3327.
24043 - Relays now include a reason for regenerating their descriptors
24044 in an HTTP header when uploading to the authorities. This will
24045 make it easier to debug descriptor-upload issues in the future.
24046 - When starting as root and then changing our UID via the User
24047 control option, and we have a ControlSocket configured, make sure
24048 that the ControlSocket is owned by the same account that Tor will
24049 run under. Implements ticket 3421; fix by Jérémy Bobbio.
24052 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
24053 utility function used in the control-port code). This shouldn't
24054 ever happen unless Tor is completely out of memory, but if it did
24055 happen and Tor somehow recovered from it, Tor could have sent a log
24056 message to a control port in the middle of a reply to a controller
24057 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
24058 - Make 'FetchUselessDescriptors' cause all descriptor types and
24059 all consensus types (including microdescriptors) to get fetched.
24060 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
24062 o Code refactoring:
24063 - Make a new "entry connection" struct as an internal subtype of "edge
24064 connection", to simplify the code and make exit connections smaller.
24067 Changes in version 0.2.2.33 - 2011-09-13
24068 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
24069 TLS handshake that makes relays and bridges that run this new version
24070 reachable from Iran again.
24073 - Avoid an assertion failure when reloading a configuration with
24074 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
24075 3923; bugfix on 0.2.2.25-alpha.
24077 o Minor features (security):
24078 - Check for replays of the public-key encrypted portion of an
24079 INTRODUCE1 cell, in addition to the current check for replays of
24080 the g^x value. This prevents a possible class of active attacks
24081 by an attacker who controls both an introduction point and a
24082 rendezvous point, and who uses the malleability of AES-CTR to
24083 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
24084 that these attacks are infeasible (requiring the attacker to send
24085 on the order of zettabytes of altered cells in a short interval),
24086 but we'd rather block them off in case there are any classes of
24087 this attack that we missed. Reported by Willem Pinckaers.
24090 - Adjust the expiration time on our SSL session certificates to
24091 better match SSL certs seen in the wild. Resolves ticket 4014.
24092 - Change the default required uptime for a relay to be accepted as
24093 a HSDir (hidden service directory) from 24 hours to 25 hours.
24094 Improves on 0.2.0.10-alpha; resolves ticket 2649.
24095 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
24096 authorities to abstain from voting on assignment of the HSDir
24097 consensus flag. Related to bug 2649.
24098 - Update to the September 6 2011 Maxmind GeoLite Country database.
24100 o Minor bugfixes (documentation and log messages):
24101 - Correct the man page to explain that HashedControlPassword and
24102 CookieAuthentication can both be set, in which case either method
24103 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
24104 when we decided to allow these config options to both be set. Issue
24105 raised by bug 3898.
24106 - Demote the 'replay detected' log message emitted when a hidden
24107 service receives the same Diffie-Hellman public key in two different
24108 INTRODUCE2 cells to info level. A normal Tor client can cause that
24109 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
24110 fixes part of bug 2442.
24111 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
24112 level. There is nothing that a hidden service's operator can do
24113 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
24115 - Clarify a log message specifying the characters permitted in
24116 HiddenServiceAuthorizeClient client names. Previously, the log
24117 message said that "[A-Za-z0-9+-_]" were permitted; that could have
24118 given the impression that every ASCII character between "+" and "_"
24119 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
24122 - Provide a substitute implementation of lround() for MSVC, which
24123 apparently lacks it. Patch from Gisle Vanem.
24124 - Clean up some code issues that prevented Tor from building on older
24125 BSDs. Fixes bug 3894; reported by "grarpamp".
24126 - Search for a platform-specific version of "ar" when cross-compiling.
24127 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
24130 Changes in version 0.2.3.3-alpha - 2011-09-01
24131 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
24132 security, and provides client-side support for the microdescriptor
24133 and optimistic data features introduced earlier in the 0.2.3.x
24134 series. It also includes numerous critical bugfixes in the (optional)
24135 bufferevent-based networking backend.
24137 o Major features (stream isolation):
24138 - You can now configure Tor so that streams from different
24139 applications are isolated on different circuits, to prevent an
24140 attacker who sees your streams as they leave an exit node from
24141 linking your sessions to one another. To do this, choose some way
24142 to distinguish the applications: have them connect to different
24143 SocksPorts, or have one of them use SOCKS4 while the other uses
24144 SOCKS5, or have them pass different authentication strings to the
24145 SOCKS proxy. Then, use the new SocksPort syntax to configure the
24146 degree of isolation you need. This implements Proposal 171.
24147 - There's a new syntax for specifying multiple client ports (such as
24148 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
24149 multiple *Port entries with full addr:port syntax on each.
24150 The old *ListenAddress format is still supported, but you can't
24151 mix it with the new *Port syntax.
24153 o Major features (other):
24154 - Enable microdescriptor fetching by default for clients. This allows
24155 clients to download a much smaller amount of directory information.
24156 To disable it (and go back to the old-style consensus and
24157 descriptors), set "UseMicrodescriptors 0" in your torrc file.
24158 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
24159 "PortForwarding" config option), now supports Windows.
24160 - When using an exit relay running 0.2.3.x, clients can now
24161 "optimistically" send data before the exit relay reports that
24162 the stream has opened. This saves a round trip when starting
24163 connections where the client speaks first (such as web browsing).
24164 This behavior is controlled by a consensus parameter (currently
24165 disabled). To turn it on or off manually, use the "OptimisticData"
24166 torrc option. Implements proposal 181; code by Ian Goldberg.
24168 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
24169 - When using IOCP on Windows, we need to enable Libevent windows
24171 - The IOCP backend now works even when the user has not specified
24172 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
24173 Fixes part of bug 3752.
24174 - Correctly record the bytes we've read and written when using
24175 bufferevents, so that we can include them in our bandwidth history
24176 and advertised bandwidth. Fixes bug 3803.
24177 - Apply rate-limiting only at the bottom of a chain of filtering
24178 bufferevents. This prevents us from filling up internal read
24179 buffers and violating rate-limits when filtering bufferevents
24180 are enabled. Fixes part of bug 3804.
24181 - Add high-watermarks to the output buffers for filtered
24182 bufferevents. This prevents us from filling up internal write
24183 buffers and wasting CPU cycles when filtering bufferevents are
24184 enabled. Fixes part of bug 3804.
24185 - Correctly notice when data has been written from a bufferevent
24186 without flushing it completely. Fixes bug 3805.
24187 - Fix a bug where server-side tunneled bufferevent-based directory
24188 streams would get closed prematurely. Fixes bug 3814.
24189 - Fix a use-after-free error with per-connection rate-limiting
24190 buckets. Fixes bug 3888.
24192 o Major bugfixes (also part of 0.2.2.31-rc):
24193 - If we're configured to write our ControlPorts to disk, only write
24194 them after switching UID and creating the data directory. This way,
24195 we don't fail when starting up with a nonexistent DataDirectory
24196 and a ControlPortWriteToFile setting based on that directory. Fixes
24197 bug 3747; bugfix on Tor 0.2.2.26-beta.
24200 - Added a new CONF_CHANGED event so that controllers can be notified
24201 of any configuration changes made by other controllers, or by the
24202 user. Implements ticket 1692.
24203 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
24204 leak when using bufferevents, and lets Libevent worry about how to
24205 best copy data out of a buffer.
24206 - Replace files in stats/ rather than appending to them. Now that we
24207 include statistics in extra-info descriptors, it makes no sense to
24208 keep old statistics forever. Implements ticket 2930.
24210 o Minor features (build compatibility):
24211 - Limited, experimental support for building with nmake and MSVC.
24212 - Provide a substitute implementation of lround() for MSVC, which
24213 apparently lacks it. Patch from Gisle Vanem.
24215 o Minor features (also part of 0.2.2.31-rc):
24216 - Update to the August 2 2011 Maxmind GeoLite Country database.
24218 o Minor bugfixes (on 0.2.3.x-alpha):
24219 - Fix a spurious warning when parsing SOCKS requests with
24220 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
24221 - Get rid of a harmless warning that could happen on relays running
24222 with bufferevents. The warning was caused by someone doing an http
24223 request to a relay's orport. Also don't warn for a few related
24224 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
24226 o Minor bugfixes (on 2.2.x and earlier):
24227 - Correct the man page to explain that HashedControlPassword and
24228 CookieAuthentication can both be set, in which case either method
24229 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
24230 when we decided to allow these config options to both be set. Issue
24231 raised by bug 3898.
24232 - The "--quiet" and "--hush" options now apply not only to Tor's
24233 behavior before logs are configured, but also to Tor's behavior in
24234 the absence of configured logs. Fixes bug 3550; bugfix on
24237 o Minor bugfixes (also part of 0.2.2.31-rc):
24238 - Write several files in text mode, on OSes that distinguish text
24239 mode from binary mode (namely, Windows). These files are:
24240 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
24241 that collect those statistics; 'client_keys' and 'hostname' for
24242 hidden services that use authentication; and (in the tor-gencert
24243 utility) newly generated identity and signing keys. Previously,
24244 we wouldn't specify text mode or binary mode, leading to an
24245 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
24246 the DirRecordUsageByCountry option which would have triggered
24247 the assertion failure was added), although this assertion failure
24248 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
24249 - Selectively disable deprecation warnings on OS X because Lion
24250 started deprecating the shipped copy of openssl. Fixes bug 3643.
24251 - Remove an extra pair of quotation marks around the error
24252 message in control-port STATUS_GENERAL BUG events. Bugfix on
24253 0.1.2.6-alpha; fixes bug 3732.
24254 - When unable to format an address as a string, report its value
24255 as "???" rather than reusing the last formatted address. Bugfix
24258 o Code simplifications and refactoring:
24259 - Rewrite the listener-selection logic so that parsing which ports
24260 we want to listen on is now separate from binding to the ports
24264 - Building Tor with bufferevent support now requires Libevent
24265 2.0.13-stable or later. Previous versions of Libevent had bugs in
24266 SSL-related bufferevents and related issues that would make Tor
24267 work badly with bufferevents. Requiring 2.0.13-stable also allows
24268 Tor with bufferevents to take advantage of Libevent APIs
24269 introduced after 2.0.8-rc.
24272 Changes in version 0.2.2.32 - 2011-08-27
24273 The Tor 0.2.2 release series is dedicated to the memory of Andreas
24274 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
24275 a founder of the PETS community, a leader in our field, a mentor,
24276 and a friend. He left us with these words: "I had the possibility
24277 to contribute to this world that is not as it should be. I hope I
24278 could help in some areas to make the world a better place, and that
24279 I could also encourage other people to be engaged in improving the
24280 world. Please, stay engaged. This world needs you, your love, your
24281 initiative -- now I cannot be part of that anymore."
24283 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
24284 ready. More than two years in the making, this release features improved
24285 client performance and hidden service reliability, better compatibility
24286 for Android, correct behavior for bridges that listen on more than
24287 one address, more extensible and flexible directory object handling,
24288 better reporting of network statistics, improved code security, and
24289 many many other features and bugfixes.
24292 Changes in version 0.2.2.31-rc - 2011-08-17
24293 Tor 0.2.2.31-rc is the second and hopefully final release candidate
24294 for the Tor 0.2.2.x series.
24297 - Remove an extra pair of quotation marks around the error
24298 message in control-port STATUS_GENERAL BUG events. Bugfix on
24299 0.1.2.6-alpha; fixes bug 3732.
24300 - If we're configured to write our ControlPorts to disk, only write
24301 them after switching UID and creating the data directory. This way,
24302 we don't fail when starting up with a nonexistent DataDirectory
24303 and a ControlPortWriteToFile setting based on that directory. Fixes
24304 bug 3747; bugfix on Tor 0.2.2.26-beta.
24307 - Update to the August 2 2011 Maxmind GeoLite Country database.
24310 - Allow GETINFO fingerprint to return a fingerprint even when
24311 we have not yet built a router descriptor. Fixes bug 3577;
24312 bugfix on 0.2.0.1-alpha.
24313 - Write several files in text mode, on OSes that distinguish text
24314 mode from binary mode (namely, Windows). These files are:
24315 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
24316 that collect those statistics; 'client_keys' and 'hostname' for
24317 hidden services that use authentication; and (in the tor-gencert
24318 utility) newly generated identity and signing keys. Previously,
24319 we wouldn't specify text mode or binary mode, leading to an
24320 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
24321 the DirRecordUsageByCountry option which would have triggered
24322 the assertion failure was added), although this assertion failure
24323 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
24324 - Selectively disable deprecation warnings on OS X because Lion
24325 started deprecating the shipped copy of openssl. Fixes bug 3643.
24326 - When unable to format an address as a string, report its value
24327 as "???" rather than reusing the last formatted address. Bugfix
24331 Changes in version 0.2.3.2-alpha - 2011-07-18
24332 Tor 0.2.3.2-alpha introduces two new experimental features:
24333 microdescriptors and pluggable transports. It also continues cleaning
24334 up a variety of recently introduced features.
24337 - Clients can now use microdescriptors instead of regular descriptors
24338 to build circuits. Microdescriptors are authority-generated
24339 summaries of regular descriptors' contents, designed to change
24340 very rarely (see proposal 158 for details). This feature is
24341 designed to save bandwidth, especially for clients on slow internet
24342 connections. It's off by default for now, since nearly no caches
24343 support it, but it will be on-by-default for clients in a future
24344 version. You can use the UseMicrodescriptors option to turn it on.
24345 - Tor clients using bridges can now be configured to use a separate
24346 'transport' proxy for each bridge. This approach helps to resist
24347 censorship by allowing bridges to use protocol obfuscation
24348 plugins. It implements part of proposal 180. Implements ticket 2841.
24349 - While we're trying to bootstrap, record how many TLS connections
24350 fail in each state, and report which states saw the most failures
24351 in response to any bootstrap failures. This feature may speed up
24352 diagnosis of censorship events. Implements ticket 3116.
24354 o Major bugfixes (on 0.2.3.1-alpha):
24355 - When configuring a large set of nodes in EntryNodes (as with
24356 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
24357 random subset to be guards, and choose them in random
24358 order. Fixes bug 2798.
24359 - Tor could crash when remembering a consensus in a non-used consensus
24360 flavor without having a current consensus set. Fixes bug 3361.
24361 - Comparing an unknown address to a microdescriptor's shortened exit
24362 policy would always give a "rejected" result. Fixes bug 3599.
24363 - Using microdescriptors as a client no longer prevents Tor from
24364 uploading and downloading hidden service descriptors. Fixes
24368 - Allow nameservers with IPv6 address. Resolves bug 2574.
24369 - Accept attempts to include a password authenticator in the
24370 handshake, as supported by SOCKS5. This handles SOCKS clients that
24371 don't know how to omit a password when authenticating. Resolves
24373 - When configuring a large set of nodes in EntryNodes, and there are
24374 enough of them listed as Guard so that we don't need to consider
24375 the non-guard entries, prefer the ones listed with the Guard flag.
24376 - Check for and recover from inconsistency in the microdescriptor
24377 cache. This will make it harder for us to accidentally free a
24378 microdescriptor without removing it from the appropriate data
24379 structures. Fixes issue 3135; issue noted by "wanoskarnet".
24380 - Log SSL state transitions at log level DEBUG, log domain
24381 HANDSHAKE. This can be useful for debugging censorship events.
24382 Implements ticket 3264.
24383 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
24384 implements ticket 3439.
24386 o Minor bugfixes (on 0.2.3.1-alpha):
24387 - Do not free all general-purpose regular descriptors just
24388 because microdescriptor use is enabled. Fixes bug 3113.
24389 - Correctly link libevent_openssl when --enable-static-libevent
24390 is passed to configure. Fixes bug 3118.
24391 - Bridges should not complain during their heartbeat log messages that
24392 they are unlisted in the consensus: that's more or less the point
24393 of being a bridge. Fixes bug 3183.
24394 - Report a SIGNAL event to controllers when acting on a delayed
24395 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
24396 event to the controller if we acted on a SIGNAL NEWNYM command
24397 immediately, and otherwise not report a SIGNAL event for the
24398 command at all. Fixes bug 3349.
24399 - Fix a crash when handling the SIGNAL controller command or
24400 reporting ERR-level status events with bufferevents enabled. Found
24401 by Robert Ransom. Fixes bug 3367.
24402 - Always ship the tor-fw-helper manpage in our release tarballs.
24403 Fixes bug 3389. Reported by Stephen Walker.
24404 - Fix a class of double-mark-for-close bugs when bufferevents
24405 are enabled. Fixes bug 3403.
24406 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
24407 - Add SIGNAL to the list returned by the 'GETINFO events/names'
24408 control-port command. Fixes part of bug 3465.
24409 - Prevent using negative indices during unit test runs when read_all()
24410 fails. Spotted by coverity.
24411 - Fix a rare memory leak when checking the nodelist without it being
24412 present. Found by coverity.
24413 - Only try to download a microdescriptor-flavored consensus from
24414 a directory cache that provides them.
24416 o Minor bugfixes (on 0.2.2.x and earlier):
24417 - Assert that hidden-service-related operations are not performed
24418 using single-hop circuits. Previously, Tor would assert that
24419 client-side streams are not attached to single-hop circuits,
24420 but not that other sensitive operations on the client and service
24421 side are not performed using single-hop circuits. Fixes bug 3332;
24423 - Don't publish a new relay descriptor when we reload our onion key,
24424 unless the onion key has actually changed. Fixes bug 3263 and
24425 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
24426 - Allow GETINFO fingerprint to return a fingerprint even when
24427 we have not yet built a router descriptor. Fixes bug 3577;
24428 bugfix on 0.2.0.1-alpha.
24429 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
24430 on 0.2.2.4-alpha; fixes bug 3427.
24432 o Code simplification and refactoring:
24433 - Use tor_sscanf() in place of scanf() in more places through the
24434 code. This makes us a little more locale-independent, and
24435 should help shut up code-analysis tools that can't tell
24436 a safe sscanf string from a dangerous one.
24437 - Use tt_assert(), not tor_assert(), for checking for test failures.
24438 This makes the unit tests more able to go on in the event that
24440 - Split connection_about_to_close() into separate functions for each
24444 - On Windows, we now define the _WIN32_WINNT macros only if they
24445 are not already defined. This lets the person building Tor decide,
24446 if they want, to require a later version of Windows.
24449 Changes in version 0.2.2.30-rc - 2011-07-07
24450 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
24451 series. It fixes a few smaller bugs, but generally appears stable.
24452 Please test it and let us know whether it is!
24455 - Send a SUCCEEDED stream event to the controller when a reverse
24456 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
24457 discovered by katmagic.
24458 - Always NUL-terminate the sun_path field of a sockaddr_un before
24459 passing it to the kernel. (Not a security issue: kernels are
24460 smart enough to reject bad sockaddr_uns.) Found by Coverity;
24461 CID #428. Bugfix on Tor 0.2.0.3-alpha.
24462 - Don't stack-allocate the list of supplementary GIDs when we're
24463 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
24464 could take up to 256K, which is way too much stack. Found by
24465 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
24466 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
24467 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
24468 fixes part of bug 3465.
24469 - Fix a memory leak when receiving a descriptor for a hidden
24470 service we didn't ask for. Found by Coverity; CID #30. Bugfix
24474 - Update to the July 1 2011 Maxmind GeoLite Country database.
24477 Changes in version 0.2.2.29-beta - 2011-06-20
24478 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
24479 have bridge lines in their torrc but don't want to use them; gets
24480 us closer to having the control socket feature working on Debian;
24481 and fixes a variety of smaller bugs.
24484 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
24485 When we changed the default behavior to "use bridges if any
24486 are listed in the torrc", we surprised users who had bridges
24487 in their torrc files but who didn't actually want to use them.
24488 Partial resolution for bug 3354.
24491 - Don't attach new streams to old rendezvous circuits after SIGNAL
24492 NEWNYM. Previously, we would keep using an existing rendezvous
24493 circuit if it remained open (i.e. if it were kept open by a
24494 long-lived stream, or if a new stream were attached to it before
24495 Tor could notice that it was old and no longer in use). Bugfix on
24496 0.1.1.15-rc; fixes bug 3375.
24499 - Fix a bug when using ControlSocketsGroupWritable with User. The
24500 directory's group would be checked against the current group, not
24501 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
24502 bugfix on 0.2.2.26-beta.
24503 - Make connection_printf_to_buf()'s behavior sane. Its callers
24504 expect it to emit a CRLF iff the format string ends with CRLF;
24505 it actually emitted a CRLF iff (a) the format string ended with
24506 CRLF or (b) the resulting string was over 1023 characters long or
24507 (c) the format string did not end with CRLF *and* the resulting
24508 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
24509 fixes part of bug 3407.
24510 - Make send_control_event_impl()'s behavior sane. Its callers
24511 expect it to always emit a CRLF at the end of the string; it
24512 might have emitted extra control characters as well. Bugfix on
24513 0.1.1.9-alpha; fixes another part of bug 3407.
24514 - Make crypto_rand_int() check the value of its input correctly.
24515 Previously, it accepted values up to UINT_MAX, but could return a
24516 negative number if given a value above INT_MAX+1. Found by George
24517 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
24518 - Avoid a segfault when reading a malformed circuit build state
24519 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
24521 - When asked about a DNS record type we don't support via a
24522 client DNSPort, reply with NOTIMPL rather than an empty
24523 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
24524 - Fix a rare memory leak during stats writing. Found by coverity.
24527 - Update to the June 1 2011 Maxmind GeoLite Country database.
24529 o Code simplifications and refactoring:
24530 - Remove some dead code as indicated by coverity.
24531 - Remove a few dead assignments during router parsing. Found by
24533 - Add some forgotten return value checks during unit tests. Found
24535 - Don't use 1-bit wide signed bit fields. Found by coverity.
24538 Changes in version 0.2.2.28-beta - 2011-06-04
24539 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
24540 fixed a big bug in whether relays stay in the consensus consistently,
24541 we moved closer to handling bridges and hidden services correctly,
24542 and we started the process of better handling the dreaded "my Vidalia
24543 died, and now my Tor demands a password when I try to reconnect to it"
24547 - Don't decide to make a new descriptor when receiving a HUP signal.
24548 This bug has caused a lot of 0.2.2.x relays to disappear from the
24549 consensus periodically. Fixes the most common case of triggering
24550 bug 1810; bugfix on 0.2.2.7-alpha.
24551 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
24552 - Don't try to build descriptors if "ORPort auto" is set and we
24553 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
24555 - Resolve a crash that occurred when setting BridgeRelay to 1 with
24556 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
24557 - Apply circuit timeouts to opened hidden-service-related circuits
24558 based on the correct start time. Previously, we would apply the
24559 circuit build timeout based on time since the circuit's creation;
24560 it was supposed to be applied based on time since the circuit
24561 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
24562 - Use the same circuit timeout for client-side introduction
24563 circuits as for other four-hop circuits, rather than the timeout
24564 for single-hop directory-fetch circuits; the shorter timeout may
24565 have been appropriate with the static circuit build timeout in
24566 0.2.1.x and earlier, but caused many hidden service access attempts
24567 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
24568 on 0.2.2.2-alpha; fixes another part of bug 1297.
24569 - In ticket 2511 we fixed a case where you could use an unconfigured
24570 bridge if you had configured it as a bridge the last time you ran
24571 Tor. Now fix another edge case: if you had configured it as a bridge
24572 but then switched to a different bridge via the controller, you
24573 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
24577 - Add an __OwningControllerProcess configuration option and a
24578 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
24579 that when it exits, Tor will shut down. Implements feature 3049.
24580 - If "UseBridges 1" is set and no bridges are configured, Tor will
24581 now refuse to build any circuits until some bridges are set.
24582 If "UseBridges auto" is set, Tor will use bridges if they are
24583 configured and we are not running as a server, but otherwise will
24584 make circuits as usual. The new default is "auto". Patch by anonym,
24585 so the Tails LiveCD can stop automatically revealing you as a Tor
24589 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
24590 - Remove a trailing asterisk from "exit-policy/default" in the
24591 output of the control port command "GETINFO info/names". Bugfix
24593 - Use a wide type to hold sockets when built for 64-bit Windows builds.
24595 - Warn when the user configures two HiddenServiceDir lines that point
24596 to the same directory. Bugfix on 0.0.6 (the version introducing
24597 HiddenServiceDir); fixes bug 3289.
24598 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
24599 part of bug 2748; bugfix on 0.2.0.10-alpha.
24600 - Log malformed requests for rendezvous descriptors as protocol
24601 warnings, not warnings. Also, use a more informative log message
24602 in case someone sees it at log level warning without prior
24603 info-level messages. Fixes the other part of bug 2748; bugfix
24605 - Clear the table recording the time of the last request for each
24606 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
24607 Previously, we would clear our HS descriptor cache on SIGNAL
24608 NEWNYM, but if we had previously retrieved a descriptor (or tried
24609 to) from every directory responsible for it, we would refuse to
24610 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
24612 - Fix a log message that said "bits" while displaying a value in
24613 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
24615 - When checking for 1024-bit keys, check for 1024 bits, not 128
24616 bytes. This allows Tor to correctly discard keys of length 1017
24617 through 1023. Bugfix on 0.0.9pre5.
24620 - Relays now log the reason for publishing a new relay descriptor,
24621 so we have a better chance of hunting down instances of bug 1810.
24622 Resolves ticket 3252.
24623 - Revise most log messages that refer to nodes by nickname to
24624 instead use the "$key=nickname at address" format. This should be
24625 more useful, especially since nicknames are less and less likely
24626 to be unique. Resolves ticket 3045.
24627 - Log (at info level) when purging pieces of hidden-service-client
24628 state because of SIGNAL NEWNYM.
24631 - Remove undocumented option "-F" from tor-resolve: it hasn't done
24632 anything since 0.2.1.16-rc.
24635 Changes in version 0.2.2.27-beta - 2011-05-18
24636 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
24637 release, and also adds a few more general bugfixes.
24640 - Fix a crash bug when changing bridges in a running Tor process.
24641 Fixes bug 3213; bugfix on 0.2.2.26-beta.
24642 - When the controller configures a new bridge, don't wait 10 to 60
24643 seconds before trying to fetch its descriptor. Bugfix on
24644 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
24647 - Require that onion keys have exponent 65537 in microdescriptors too.
24648 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
24649 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
24650 Changed the limit to 512 characters by removing base64 newlines.
24651 Fixes bug 2752. Fix by Michael Yakubovich.
24652 - When a client starts or stops using bridges, never use a circuit
24653 that was built before the configuration change. This behavior could
24654 put at risk a user who uses bridges to ensure that her traffic
24655 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
24659 Changes in version 0.2.2.26-beta - 2011-05-17
24660 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
24661 also introduces a new "socksport auto" approach that should make it
24662 easier to run multiple Tors on the same system, and does a lot of
24663 cleanup to get us closer to a release candidate.
24665 o Security/privacy fixes:
24666 - Replace all potentially sensitive memory comparison operations
24667 with versions whose runtime does not depend on the data being
24668 compared. This will help resist a class of attacks where an
24669 adversary can use variations in timing information to learn
24670 sensitive data. Fix for one case of bug 3122. (Safe memcmp
24671 implementation by Robert Ransom based partially on code by DJB.)
24672 - When receiving a hidden service descriptor, check that it is for
24673 the hidden service we wanted. Previously, Tor would store any
24674 hidden service descriptors that a directory gave it, whether it
24675 wanted them or not. This wouldn't have let an attacker impersonate
24676 a hidden service, but it did let directories pre-seed a client
24677 with descriptors that it didn't want. Bugfix on 0.0.6.
24678 - On SIGHUP, do not clear out all TrackHostExits mappings, client
24679 DNS cache entries, and virtual address mappings: that's what
24680 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
24683 - The options SocksPort, ControlPort, and so on now all accept a
24684 value "auto" that opens a socket on an OS-selected port. A
24685 new ControlPortWriteToFile option tells Tor to write its
24686 actual control port or ports to a chosen file. If the option
24687 ControlPortFileGroupReadable is set, the file is created as
24688 group-readable. Now users can run two Tor clients on the same
24689 system without needing to manually mess with parameters. Resolves
24690 part of ticket 3076.
24691 - Set SO_REUSEADDR on all sockets, not just listeners. This should
24692 help busy exit nodes avoid running out of useable ports just
24693 because all the ports have been used in the near past. Resolves
24697 - New "GETINFO net/listeners/(type)" controller command to return
24698 a list of addresses and ports that are bound for listeners for a
24699 given connection type. This is useful when the user has configured
24700 "SocksPort auto" and the controller needs to know which port got
24701 chosen. Resolves another part of ticket 3076.
24702 - Add a new ControlSocketsGroupWritable configuration option: when
24703 it is turned on, ControlSockets are group-writeable by the default
24704 group of the current user. Patch by Jérémy Bobbio; implements
24706 - Tor now refuses to create a ControlSocket in a directory that is
24707 world-readable (or group-readable if ControlSocketsGroupWritable
24708 is 0). This is necessary because some operating systems do not
24709 enforce permissions on an AF_UNIX sockets. Permissions on the
24710 directory holding the socket, however, seems to work everywhere.
24711 - Rate-limit a warning about failures to download v2 networkstatus
24712 documents. Resolves part of bug 1352.
24713 - Backport code from 0.2.3.x that allows directory authorities to
24714 clean their microdescriptor caches. Needed to resolve bug 2230.
24715 - When an HTTPS proxy reports "403 Forbidden", we now explain
24716 what it means rather than calling it an unexpected status code.
24717 Closes bug 2503. Patch from Michael Yakubovich.
24718 - Update to the May 1 2011 Maxmind GeoLite Country database.
24721 - Authorities now clean their microdesc cache periodically and when
24722 reading from disk initially, not only when adding new descriptors.
24723 This prevents a bug where we could lose microdescriptors. Bugfix
24724 on 0.2.2.6-alpha. Fixes bug 2230.
24725 - Do not crash when our configuration file becomes unreadable, for
24726 example due to a permissions change, between when we start up
24727 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
24729 - Avoid a bug that would keep us from replacing a microdescriptor
24730 cache on Windows. (We would try to replace the file while still
24731 holding it open. That's fine on Unix, but Windows doesn't let us
24732 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
24733 - Add missing explanations for the authority-related torrc options
24734 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
24735 man page. Resolves issue 2379.
24736 - As an authority, do not upload our own vote or signature set to
24737 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
24738 it would get flagged as a duplicate. Resolves bug 3026.
24739 - Accept hidden service descriptors if we think we might be a hidden
24740 service directory, regardless of what our consensus says. This
24741 helps robustness, since clients and hidden services can sometimes
24742 have a more up-to-date view of the network consensus than we do,
24743 and if they think that the directory authorities list us a HSDir,
24744 we might actually be one. Related to bug 2732; bugfix on
24746 - When a controller changes TrackHostExits, remove mappings for
24747 hosts that should no longer have their exits tracked. Bugfix on
24749 - When a controller changes VirtualAddrNetwork, remove any mappings
24750 for hosts that were automapped to the old network. Bugfix on
24752 - When a controller changes one of the AutomapHosts* options, remove
24753 any mappings for hosts that should no longer be automapped. Bugfix
24755 - Do not reset the bridge descriptor download status every time we
24756 re-parse our configuration or get a configuration change. Fixes
24757 bug 3019; bugfix on 0.2.0.3-alpha.
24759 o Minor bugfixes (code cleanup):
24760 - When loading the microdesc journal, remember its current size.
24761 In 0.2.2, this helps prevent the microdesc journal from growing
24762 without limit on authorities (who are the only ones to use it in
24763 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
24764 Fix posted by "cypherpunks."
24765 - The microdesc journal is supposed to get rebuilt only if it is
24766 at least _half_ the length of the store, not _twice_ the length
24767 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
24768 - Fix a potential null-pointer dereference while computing a
24769 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
24771 - Avoid a possible null-pointer dereference when rebuilding the mdesc
24772 cache without actually having any descriptors to cache. Bugfix on
24773 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
24774 - If we fail to compute the identity digest of a v3 legacy keypair,
24775 warn, and don't use a buffer-full of junk instead. Bugfix on
24776 0.2.1.1-alpha; fixes bug 3106.
24777 - Resolve an untriggerable issue in smartlist_string_num_isin(),
24778 where if the function had ever in the future been used to check
24779 for the presence of a too-large number, it would have given an
24780 incorrect result. (Fortunately, we only used it for 16-bit
24781 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
24782 - Require that introduction point keys and onion handshake keys
24783 have a public exponent of 65537. Starts to fix bug 3207; bugfix
24786 o Removed features:
24787 - Caches no longer download and serve v2 networkstatus documents
24788 unless FetchV2Networkstatus flag is set: these documents haven't
24789 haven't been used by clients or relays since 0.2.0.x. Resolves
24793 Changes in version 0.2.3.1-alpha - 2011-05-05
24794 Tor 0.2.3.1-alpha adds some new experimental features, including support
24795 for an improved network IO backend, IOCP networking on Windows,
24796 microdescriptor caching, "fast-start" support for streams, and automatic
24797 home router configuration. There are also numerous internal improvements
24798 to try to make the code easier for developers to work with.
24800 This is the first alpha release in a new series, so expect there to be
24801 bugs. Users who would rather test out a more stable branch should
24802 stay with 0.2.2.x for now.
24805 - Tor can now optionally build with the "bufferevents" buffered IO
24806 backend provided by Libevent 2. To use this feature, make sure you
24807 have the latest possible version of Libevent, and pass the
24808 --enable-bufferevents flag to configure when building Tor from
24809 source. This feature will make our networking code more flexible,
24810 let us stack layers on each other, and let us use more efficient
24811 zero-copy transports where available.
24812 - As an experimental feature, Tor can use IOCP for networking on Windows.
24813 Once this code is tuned and optimized, it promises much better
24814 performance than the select-based backend we've used in the past. To
24815 try this feature, you must build Tor with Libevent 2, configure Tor
24816 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
24817 your torrc. There are known bugs here: only try this if you can help
24818 debug it as it breaks.
24819 - The EntryNodes option can now include country codes like {de} or IP
24820 addresses or network masks. Previously we had disallowed these options
24821 because we didn't have an efficient way to keep the list up to
24822 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
24823 - Exit nodes now accept and queue data on not-yet-connected streams.
24824 Previously, the client wasn't allowed to send data until the stream was
24825 connected, which slowed down all connections. This change will enable
24826 clients to perform a "fast-start" on streams and send data without
24827 having to wait for a confirmation that the stream has opened. (Patch
24828 from Ian Goldberg; implements the server side of Proposal 174.)
24829 - Tor now has initial support for automatic port mapping on the many
24830 home routers that support NAT-PMP or UPnP. (Not yet supported on
24831 Windows). To build the support code, you'll need to have libnatpnp
24832 library and/or the libminiupnpc library, and you'll need to enable the
24833 feature specifically by passing "--enable-upnp" and/or
24834 "--enable-natpnp" to configure. To turn it on, use the new
24835 PortForwarding option.
24836 - Caches now download, cache, and serve multiple "flavors" of the
24837 consensus, including a flavor that describes microdescriptors.
24838 - Caches now download, cache, and serve microdescriptors -- small
24839 summaries of router descriptors that are authenticated by all of the
24840 directory authorities. Once enough caches are running this code,
24841 clients will be able to save significant amounts of directory bandwidth
24842 by downloading microdescriptors instead of router descriptors.
24845 - Make logging resolution configurable with a new LogTimeGranularity
24846 option, and change the default from 1 millisecond to 1 second.
24847 Implements enhancement 1668.
24848 - We log which torrc file we're using on startup. Implements ticket
24850 - Ordinarily, Tor does not count traffic from private addresses (like
24851 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
24852 There is now a new option, CountPrivateBandwidth, to disable this
24853 behavior. Patch from Daniel Cagara.
24854 - New --enable-static-tor configure option for building Tor as
24855 statically as possible. Idea, general hackery and thoughts from
24856 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
24858 - If you set the NumCPUs option to 0, Tor will now try to detect how
24859 many CPUs you have. This is the new default behavior.
24860 - Turn on directory request statistics by default and include them in
24861 extra-info descriptors. Don't break if we have no GeoIP database.
24862 - Relays that set "ConnDirectionStatistics 1" write statistics on the
24863 bidirectional use of connections to disk every 24 hours.
24864 - Add a GeoIP file digest to the extra-info descriptor. Implements
24866 - The NodeFamily option -- which let you declare that you want to
24867 consider nodes to be part of a family whether they list themselves
24868 that way or not -- now allows IP address ranges and country codes.
24869 - Add a new 'Heartbeat' log message type to periodically log a message
24870 describing Tor's status at level Notice. This feature is meant for
24871 operators who log at notice, and want to make sure that their Tor
24872 server is still working. Implementation by George Kadianakis.
24874 o Minor bugfixes (on 0.2.2.25-alpha):
24875 - When loading the microdesc journal, remember its current size.
24876 In 0.2.2, this helps prevent the microdesc journal from growing
24877 without limit on authorities (who are the only ones to use it in
24878 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
24879 Fix posted by "cypherpunks."
24880 - The microdesc journal is supposed to get rebuilt only if it is
24881 at least _half_ the length of the store, not _twice_ the length
24882 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
24883 - If as an authority we fail to compute the identity digest of a v3
24884 legacy keypair, warn, and don't use a buffer-full of junk instead.
24885 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
24886 - Authorities now clean their microdesc cache periodically and when
24887 reading from disk initially, not only when adding new descriptors.
24888 This prevents a bug where we could lose microdescriptors. Bugfix
24891 o Minor features (controller):
24892 - Add a new SIGNAL event to the controller interface so that
24893 controllers can be notified when Tor handles a signal. Resolves
24894 issue 1955. Patch by John Brooks.
24895 - Add a new GETINFO option to get total bytes read and written. Patch
24896 from pipe, revised by atagar. Resolves ticket 2345.
24897 - Implement some GETINFO controller fields to provide information about
24898 the Tor process's pid, euid, username, and resource limits.
24901 - Our build system requires automake 1.6 or later to create the
24902 Makefile.in files. Previously, you could have used 1.4.
24903 This only affects developers and people building Tor from git;
24904 people who build Tor from the source distribution without changing
24905 the Makefile.am files should be fine.
24906 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
24907 so on. This is more robust against some of the failure modes
24908 associated with running the autotools pieces on their own.
24910 o Minor packaging issues:
24911 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
24912 already created. Patch from Andreas Stieger. Fixes bug 2573.
24914 o Code simplifications and refactoring:
24915 - A major revision to our internal node-selecting and listing logic.
24916 Tor already had at least two major ways to look at the question of
24917 "which Tor servers do we know about": a list of router descriptors,
24918 and a list of entries in the current consensus. With
24919 microdescriptors, we're adding a third. Having so many systems
24920 without an abstraction layer over them was hurting the codebase.
24921 Now, we have a new "node_t" abstraction that presents a consistent
24922 interface to a client's view of a Tor node, and holds (nearly) all
24923 of the mutable state formerly in routerinfo_t and routerstatus_t.
24924 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
24925 no longer link against Libevent: they never used it, but
24926 our library structure used to force them to link it.
24928 o Removed features:
24929 - Remove some old code to work around even older versions of Tor that
24930 used forked processes to handle DNS requests. Such versions of Tor
24931 are no longer in use as servers.
24933 o Documentation fixes:
24934 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
24935 - Add missing documentation for the authority-related torrc options
24936 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
24940 Changes in version 0.2.2.25-alpha - 2011-04-29
24941 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
24942 robust, routers no longer overreport their bandwidth, Win7 should crash
24943 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
24944 now prevents hidden service-related activity from being linkable. It
24945 provides more information to Vidalia so you can see if your bridge is
24946 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
24947 StrictNodes configuration options to make them more reliable, more
24948 understandable, and more regularly applied. If you use those options,
24949 please see the revised documentation for them in the manual page.
24952 - Relays were publishing grossly inflated bandwidth values because
24953 they were writing their state files wrong--now they write the
24954 correct value. Also, resume reading bandwidth history from the
24955 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
24956 - Improve hidden service robustness: When we find that we have
24957 extended a hidden service's introduction circuit to a relay not
24958 listed as an introduction point in the HS descriptor we currently
24959 have, retry with an introduction point from the current
24960 descriptor. Previously we would just give up. Fixes bugs 1024 and
24961 1930; bugfix on 0.2.0.10-alpha.
24962 - Clients now stop trying to use an exit node associated with a given
24963 destination by TrackHostExits if they fail to reach that exit node.
24964 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
24965 - Fix crash bug on platforms where gmtime and localtime can return
24966 NULL. Windows 7 users were running into this one. Fixes part of bug
24967 2077. Bugfix on all versions of Tor. Found by boboper.
24969 o Security and stability fixes:
24970 - Don't double-free a parsable, but invalid, microdescriptor, even if
24971 it is followed in the blob we're parsing by an unparsable
24972 microdescriptor. Fixes an issue reported in a comment on bug 2954.
24973 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
24974 - If the Nickname configuration option isn't given, Tor would pick a
24975 nickname based on the local hostname as the nickname for a relay.
24976 Because nicknames are not very important in today's Tor and the
24977 "Unnamed" nickname has been implemented, this is now problematic
24978 behavior: It leaks information about the hostname without being
24979 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
24980 introduced the Unnamed nickname. Reported by tagnaq.
24981 - Fix an uncommon assertion failure when running with DNSPort under
24982 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
24983 - Avoid linkability based on cached hidden service descriptors: forget
24984 all hidden service descriptors cached as a client when processing a
24985 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
24988 - Export GeoIP information on bridge usage to controllers even if we
24989 have not yet been running for 24 hours. Now Vidalia bridge operators
24990 can get more accurate and immediate feedback about their
24991 contributions to the network.
24993 o Major features and bugfixes (node selection):
24994 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
24995 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
24996 options. Previously, we had been ambiguous in describing what
24997 counted as an "exit" node, and what operations exactly "StrictNodes
24998 0" would permit. This created confusion when people saw nodes built
24999 through unexpected circuits, and made it hard to tell real bugs from
25000 surprises. Now the intended behavior is:
25001 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
25002 a node that delivers user traffic outside the Tor network.
25003 . "Entry", in the context of EntryNodes, means a node used as the
25004 first hop of a multihop circuit. It doesn't include direct
25005 connections to directory servers.
25006 . "ExcludeNodes" applies to all nodes.
25007 . "StrictNodes" changes the behavior of ExcludeNodes only. When
25008 StrictNodes is set, Tor should avoid all nodes listed in
25009 ExcludeNodes, even when it will make user requests fail. When
25010 StrictNodes is *not* set, then Tor should follow ExcludeNodes
25011 whenever it can, except when it must use an excluded node to
25012 perform self-tests, connect to a hidden service, provide a
25013 hidden service, fulfill a .exit request, upload directory
25014 information, or fetch directory information.
25015 Collectively, the changes to implement the behavior fix bug 1090.
25016 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
25017 a node is listed in both, it's treated as excluded.
25018 - ExcludeNodes now applies to directory nodes -- as a preference if
25019 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
25020 Don't exclude all the directory authorities and set StrictNodes to 1
25021 unless you really want your Tor to break.
25022 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
25023 - ExcludeExitNodes now overrides .exit requests.
25024 - We don't use bridges listed in ExcludeNodes.
25025 - When StrictNodes is 1:
25026 . We now apply ExcludeNodes to hidden service introduction points
25027 and to rendezvous points selected by hidden service users. This
25028 can make your hidden service less reliable: use it with caution!
25029 . If we have used ExcludeNodes on ourself, do not try relay
25030 reachability self-tests.
25031 . If we have excluded all the directory authorities, we will not
25032 even try to upload our descriptor if we're a relay.
25033 . Do not honor .exit requests to an excluded node.
25034 - Remove a misfeature that caused us to ignore the Fast/Stable flags
25035 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
25036 - When the set of permitted nodes changes, we now remove any mappings
25037 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
25039 - We never cannibalize a circuit that had excluded nodes on it, even
25040 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
25041 - Revert a change where we would be laxer about attaching streams to
25042 circuits than when building the circuits. This was meant to prevent
25043 a set of bugs where streams were never attachable, but our improved
25044 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
25045 - Keep track of how many times we launch a new circuit to handle a
25046 given stream. Too many launches could indicate an inconsistency
25047 between our "launch a circuit to handle this stream" logic and our
25048 "attach this stream to one of the available circuits" logic.
25049 - Improve log messages related to excluded nodes.
25052 - Fix a spurious warning when moving from a short month to a long
25053 month on relays with month-based BandwidthAccounting. Bugfix on
25054 0.2.2.17-alpha; fixes bug 3020.
25055 - When a client finds that an origin circuit has run out of 16-bit
25056 stream IDs, we now mark it as unusable for new streams. Previously,
25057 we would try to close the entire circuit. Bugfix on 0.0.6.
25058 - Add a forgotten cast that caused a compile warning on OS X 10.6.
25059 Bugfix on 0.2.2.24-alpha.
25060 - Be more careful about reporting the correct error from a failed
25061 connect() system call. Under some circumstances, it was possible to
25062 look at an incorrect value for errno when sending the end reason.
25063 Bugfix on 0.1.0.1-rc.
25064 - Correctly handle an "impossible" overflow cases in connection byte
25065 counting, where we write or read more than 4GB on an edge connection
25066 in a single second. Bugfix on 0.1.2.8-beta.
25067 - Correct the warning displayed when a rendezvous descriptor exceeds
25068 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
25070 - Clients and hidden services now use HSDir-flagged relays for hidden
25071 service descriptor downloads and uploads even if the relays have no
25072 DirPort set and the client has disabled TunnelDirConns. This will
25073 eventually allow us to give the HSDir flag to relays with no
25074 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
25075 - Downgrade "no current certificates known for authority" message from
25076 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
25077 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
25078 2917. Bugfix on 0.1.1.1-alpha.
25079 - Only limit the lengths of single HS descriptors, even when multiple
25080 HS descriptors are published to an HSDir relay in a single POST
25081 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
25082 - Write the current time into the LastWritten line in our state file,
25083 rather than the time from the previous write attempt. Also, stop
25084 trying to use a time of -1 in our log statements. Fixes bug 3039;
25085 bugfix on 0.2.2.14-alpha.
25086 - Be more consistent in our treatment of file system paths. "~" should
25087 get expanded to the user's home directory in the Log config option.
25088 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
25089 feature for the -f and --DataDirectory options.
25092 - Make sure every relay writes a state file at least every 12 hours.
25093 Previously, a relay could go for weeks without writing its state
25094 file, and on a crash could lose its bandwidth history, capacity
25095 estimates, client country statistics, and so on. Addresses bug 3012.
25096 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
25097 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
25098 clients are already deprecated because of security bugs.
25099 - Don't allow v0 hidden service authorities to act as clients.
25100 Required by fix for bug 3000.
25101 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
25102 by fix for bug 3000.
25103 - Ensure that no empty [dirreq-](read|write)-history lines are added
25104 to an extrainfo document. Implements ticket 2497.
25106 o Code simplification and refactoring:
25107 - Remove workaround code to handle directory responses from servers
25108 that had bug 539 (they would send HTTP status 503 responses _and_
25109 send a body too). Since only server versions before
25110 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
25111 keep the workaround in place.
25112 - Remove the old 'fuzzy time' logic. It was supposed to be used for
25113 handling calculations where we have a known amount of clock skew and
25114 an allowed amount of unknown skew. But we only used it in three
25115 places, and we never adjusted the known/unknown skew values. This is
25116 still something we might want to do someday, but if we do, we'll
25117 want to do it differently.
25118 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
25119 None of the cases where we did this before were wrong, but by making
25120 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
25121 - Use GetTempDir to find the proper temporary directory location on
25122 Windows when generating temporary files for the unit tests. Patch by
25126 Changes in version 0.2.2.24-alpha - 2011-04-08
25127 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
25128 prevented Tor clients from effectively using "multihomed" bridges,
25129 that is, bridges that listen on multiple ports or IP addresses so users
25130 can continue to use some of their addresses even if others get blocked.
25133 - Fix a bug where bridge users who configure the non-canonical
25134 address of a bridge automatically switch to its canonical
25135 address. If a bridge listens at more than one address, it should be
25136 able to advertise those addresses independently and any non-blocked
25137 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
25139 - If you configured Tor to use bridge A, and then quit and
25140 configured Tor to use bridge B instead, it would happily continue
25141 to use bridge A if it's still reachable. While this behavior is
25142 a feature if your goal is connectivity, in some scenarios it's a
25143 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
25144 - Directory authorities now use data collected from their own
25145 uptime observations when choosing whether to assign the HSDir flag
25146 to relays, instead of trusting the uptime value the relay reports in
25147 its descriptor. This change helps prevent an attack where a small
25148 set of nodes with frequently-changing identity keys can blackhole
25149 a hidden service. (Only authorities need upgrade; others will be
25150 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
25153 - When we restart our relay, we might get a successful connection
25154 from the outside before we've started our reachability tests,
25155 triggering a warning: "ORPort found reachable, but I have no
25156 routerinfo yet. Failing to inform controller of success." This
25157 bug was harmless unless Tor is running under a controller
25158 like Vidalia, in which case the controller would never get a
25159 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
25161 - Make directory authorities more accurate at recording when
25162 relays that have failed several reachability tests became
25163 unreachable, so we can provide more accuracy at assigning Stable,
25164 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
25165 - Fix an issue that prevented static linking of libevent on
25166 some platforms (notably Linux). Fixes bug 2698; bugfix on
25167 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
25168 the --with-static-libevent configure option).
25169 - We now ask the other side of a stream (the client or the exit)
25170 for more data on that stream when the amount of queued data on
25171 that stream dips low enough. Previously, we wouldn't ask the
25172 other side for more data until either it sent us more data (which
25173 it wasn't supposed to do if it had exhausted its window!) or we
25174 had completely flushed all our queued data. This flow control fix
25175 should improve throughput. Fixes bug 2756; bugfix on the earliest
25176 released versions of Tor (svn commit r152).
25177 - Avoid a double-mark-for-free warning when failing to attach a
25178 transparent proxy connection. (We thought we had fixed this in
25179 0.2.2.23-alpha, but it turns out our fix was checking the wrong
25180 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
25181 bug) and 0.2.2.23-alpha (the incorrect fix).
25182 - When warning about missing zlib development packages during compile,
25183 give the correct package names. Bugfix on 0.2.0.1-alpha.
25186 - Directory authorities now log the source of a rejected POSTed v3
25187 networkstatus vote.
25188 - Make compilation with clang possible when using
25189 --enable-gcc-warnings by removing two warning options that clang
25190 hasn't implemented yet and by fixing a few warnings. Implements
25192 - When expiring circuits, use microsecond timers rather than
25193 one-second timers. This can avoid an unpleasant situation where a
25194 circuit is launched near the end of one second and expired right
25195 near the beginning of the next, and prevent fluctuations in circuit
25197 - Use computed circuit-build timeouts to decide when to launch
25198 parallel introduction circuits for hidden services. (Previously,
25199 we would retry after 15 seconds.)
25200 - Update to the April 1 2011 Maxmind GeoLite Country database.
25203 - Create the /var/run/tor directory on startup on OpenSUSE if it is
25204 not already created. Patch from Andreas Stieger. Fixes bug 2573.
25206 o Documentation changes:
25207 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
25208 - Resolve all doxygen warnings except those for missing documentation.
25210 - Add doxygen documentation for more functions, fields, and types.
25213 Changes in version 0.2.2.23-alpha - 2011-03-08
25214 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
25215 they restart they don't lose their bandwidth capacity estimate. This
25216 release also fixes a diverse set of user-facing bugs, ranging from
25217 relays overrunning their rate limiting to clients falsely warning about
25218 clock skew to bridge descriptor leaks by our bridge directory authority.
25221 - Stop sending a CLOCK_SKEW controller status event whenever
25222 we fetch directory information from a relay that has a wrong clock.
25223 Instead, only inform the controller when it's a trusted authority
25224 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25225 the rest of bug 1074.
25226 - Fix an assert in parsing router descriptors containing IPv6
25227 addresses. This one took down the directory authorities when
25228 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
25229 - Make the bridge directory authority refuse to answer directory
25230 requests for "all" descriptors. It used to include bridge
25231 descriptors in its answer, which was a major information leak.
25232 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
25233 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25234 Tor would ignore their RelayBandwidthBurst setting,
25235 potentially using more bandwidth than expected. Bugfix on
25236 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25237 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25238 hidserv" in her torrc. The 'hidserv' argument never controlled
25239 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25242 - Relays now save observed peak bandwidth throughput rates to their
25243 state file (along with total usage, which was already saved)
25244 so that they can determine their correct estimated bandwidth on
25245 restart. Resolves bug 1863, where Tor relays would reset their
25246 estimated bandwidth to 0 after restarting.
25247 - Directory authorities now take changes in router IP address and
25248 ORPort into account when determining router stability. Previously,
25249 if a router changed its IP or ORPort, the authorities would not
25250 treat it as having any downtime for the purposes of stability
25251 calculation, whereas clients would experience downtime since the
25252 change could take a while to propagate to them. Resolves issue 1035.
25253 - Enable Address Space Layout Randomization (ASLR) and Data Execution
25254 Prevention (DEP) by default on Windows to make it harder for
25255 attackers to exploit vulnerabilities. Patch from John Brooks.
25257 o Minor bugfixes (on 0.2.1.x and earlier):
25258 - Fix a rare crash bug that could occur when a client was configured
25259 with a large number of bridges. Fixes bug 2629; bugfix on
25260 0.2.1.2-alpha. Bugfix by trac user "shitlei".
25261 - Avoid a double mark-for-free warning when failing to attach a
25262 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
25264 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
25265 found by "cypherpunks". This bug was introduced before the first
25266 Tor release, in svn commit r110.
25267 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
25268 don't mention them in the manpage. Fixes bug 2450; issue
25269 spotted by keb and G-Lo.
25270 - Fix a bug in bandwidth history state parsing that could have been
25271 triggered if a future version of Tor ever changed the timing
25272 granularity at which bandwidth history is measured. Bugfix on
25273 Tor 0.1.1.11-alpha.
25274 - When a relay decides that its DNS is too broken for it to serve
25275 as an exit server, it advertised itself as a non-exit, but
25276 continued to act as an exit. This could create accidental
25277 partitioning opportunities for users. Instead, if a relay is
25278 going to advertise reject *:* as its exit policy, it should
25279 really act with exit policy "reject *:*". Fixes bug 2366.
25280 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
25281 - In the special case where you configure a public exit relay as your
25282 bridge, Tor would be willing to use that exit relay as the last
25283 hop in your circuit as well. Now we fail that circuit instead.
25284 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
25285 - Fix a bug with our locking implementation on Windows that couldn't
25286 correctly detect when a file was already locked. Fixes bug 2504,
25287 bugfix on 0.2.1.6-alpha.
25288 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
25289 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
25291 - Set target port in get_interface_address6() correctly. Bugfix
25292 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
25293 - Directory authorities are now more robust to hops back in time
25294 when calculating router stability. Previously, if a run of uptime
25295 or downtime appeared to be negative, the calculation could give
25296 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
25298 - Fix an assert that got triggered when using the TestingTorNetwork
25299 configuration option and then issuing a GETINFO config-text control
25300 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
25302 o Minor bugfixes (on 0.2.2.x):
25303 - Clients should not weight BadExit nodes as Exits in their node
25304 selection. Similarly, directory authorities should not count BadExit
25305 bandwidth as Exit bandwidth when computing bandwidth-weights.
25306 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
25307 - Correctly clear our dir_read/dir_write history when there is an
25308 error parsing any bw history value from the state file. Bugfix on
25309 Tor 0.2.2.15-alpha.
25310 - Resolve a bug in verifying signatures of directory objects
25311 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
25312 Fixes bug 2409. Found by "piebeer".
25313 - Bridge authorities no longer crash on SIGHUP when they try to
25314 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
25318 - Log less aggressively about circuit timeout changes, and improve
25319 some other circuit timeout messages. Resolves bug 2004.
25320 - Log a little more clearly about the times at which we're no longer
25321 accepting new connections. Resolves bug 2181.
25322 - Reject attempts at the client side to open connections to private
25323 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
25324 a randomly chosen exit node. Attempts to do so are always
25325 ill-defined, generally prevented by exit policies, and usually
25326 in error. This will also help to detect loops in transparent
25327 proxy configurations. You can disable this feature by setting
25328 "ClientRejectInternalAddresses 0" in your torrc.
25329 - Always treat failure to allocate an RSA key as an unrecoverable
25331 - Update to the March 1 2011 Maxmind GeoLite Country database.
25333 o Minor features (log subsystem):
25334 - Add documentation for configuring logging at different severities in
25335 different log domains. We've had this feature since 0.2.1.1-alpha,
25336 but for some reason it never made it into the manpage. Fixes
25338 - Make it simpler to specify "All log domains except for A and B".
25339 Previously you needed to say "[*,~A,~B]". Now you can just say
25341 - Add a "LogMessageDomains 1" option to include the domains of log
25342 messages along with the messages. Without this, there's no way
25343 to use log domains without reading the source or doing a lot
25346 o Packaging changes:
25347 - Stop shipping the Tor specs files and development proposal documents
25348 in the tarball. They are now in a separate git repository at
25349 git://git.torproject.org/torspec.git
25352 Changes in version 0.2.1.30 - 2011-02-23
25353 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
25354 change is a slight tweak to Tor's TLS handshake that makes relays
25355 and bridges that run this new version reachable from Iran again.
25356 We don't expect this tweak will win the arms race long-term, but it
25357 buys us time until we roll out a better solution.
25360 - Stop sending a CLOCK_SKEW controller status event whenever
25361 we fetch directory information from a relay that has a wrong clock.
25362 Instead, only inform the controller when it's a trusted authority
25363 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25364 the rest of bug 1074.
25365 - Fix a bounds-checking error that could allow an attacker to
25366 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25367 Found by "piebeer".
25368 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25369 Tor would ignore their RelayBandwidthBurst setting,
25370 potentially using more bandwidth than expected. Bugfix on
25371 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25372 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25373 hidserv" in her torrc. The 'hidserv' argument never controlled
25374 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25377 - Adjust our TLS Diffie-Hellman parameters to match those used by
25379 - Update to the February 1 2011 Maxmind GeoLite Country database.
25382 - Check for and reject overly long directory certificates and
25383 directory tokens before they have a chance to hit any assertions.
25384 Bugfix on 0.2.1.28. Found by "doorss".
25385 - Bring the logic that gathers routerinfos and assesses the
25386 acceptability of circuits into line. This prevents a Tor OP from
25387 getting locked in a cycle of choosing its local OR as an exit for a
25388 path (due to a .exit request) and then rejecting the circuit because
25389 its OR is not listed yet. It also prevents Tor clients from using an
25390 OR running in the same instance as an exit (due to a .exit request)
25391 if the OR does not meet the same requirements expected of an OR
25392 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25394 o Packaging changes:
25395 - Stop shipping the Tor specs files and development proposal documents
25396 in the tarball. They are now in a separate git repository at
25397 git://git.torproject.org/torspec.git
25398 - Do not include Git version tags as though they are SVN tags when
25399 generating a tarball from inside a repository that has switched
25400 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
25403 Changes in version 0.2.2.22-alpha - 2011-01-25
25404 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
25405 main other change is a slight tweak to Tor's TLS handshake that makes
25406 relays and bridges that run this new version reachable from Iran again.
25407 We don't expect this tweak will win the arms race long-term, but it
25408 will buy us a bit more time until we roll out a better solution.
25411 - Fix a bounds-checking error that could allow an attacker to
25412 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25413 Found by "piebeer".
25414 - Don't assert when changing from bridge to relay or vice versa
25415 via the controller. The assert happened because we didn't properly
25416 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
25417 bug 2433. Reported by bastik.
25420 - Adjust our TLS Diffie-Hellman parameters to match those used by
25422 - Provide a log message stating which geoip file we're parsing
25423 instead of just stating that we're parsing the geoip file.
25424 Implements ticket 2432.
25427 - Check for and reject overly long directory certificates and
25428 directory tokens before they have a chance to hit any assertions.
25429 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
25432 Changes in version 0.2.2.21-alpha - 2011-01-15
25433 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
25434 continues our recent code security audit work. The main fix resolves
25435 a remote heap overflow vulnerability that can allow remote code
25436 execution (CVE-2011-0427). Other fixes address a variety of assert
25437 and crash bugs, most of which we think are hard to exploit remotely.
25439 o Major bugfixes (security), also included in 0.2.1.29:
25440 - Fix a heap overflow bug where an adversary could cause heap
25441 corruption. This bug probably allows remote code execution
25442 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
25444 - Prevent a denial-of-service attack by disallowing any
25445 zlib-compressed data whose compression factor is implausibly
25446 high. Fixes part of bug 2324; reported by "doorss".
25447 - Zero out a few more keys in memory before freeing them. Fixes
25448 bug 2384 and part of bug 2385. These key instances found by
25449 "cypherpunks", based on Andrew Case's report about being able
25450 to find sensitive data in Tor's memory space if you have enough
25451 permissions. Bugfix on 0.0.2pre9.
25453 o Major bugfixes (crashes), also included in 0.2.1.29:
25454 - Prevent calls to Libevent from inside Libevent log handlers.
25455 This had potential to cause a nasty set of crashes, especially
25456 if running Libevent with debug logging enabled, and running
25457 Tor with a controller watching for low-severity log messages.
25458 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
25459 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
25460 underflow errors there too. Fixes the other part of bug 2324.
25461 - Fix a bug where we would assert if we ever had a
25462 cached-descriptors.new file (or another file read directly into
25463 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
25464 on 0.2.1.25. Found by doorss.
25465 - Fix some potential asserts and parsing issues with grossly
25466 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
25469 o Minor bugfixes (other), also included in 0.2.1.29:
25470 - Fix a bug with handling misformed replies to reverse DNS lookup
25471 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
25472 bug reported by doorss.
25473 - Fix compilation on mingw when a pthreads compatibility library
25474 has been installed. (We don't want to use it, so we shouldn't
25475 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
25476 - Fix a bug where we would declare that we had run out of virtual
25477 addresses when the address space was only half-exhausted. Bugfix
25479 - Correctly handle the case where AutomapHostsOnResolve is set but
25480 no virtual addresses are available. Fixes bug 2328; bugfix on
25481 0.1.2.1-alpha. Bug found by doorss.
25482 - Correctly handle wrapping around when we run out of virtual
25483 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
25485 o Minor features, also included in 0.2.1.29:
25486 - Update to the January 1 2011 Maxmind GeoLite Country database.
25487 - Introduce output size checks on all of our decryption functions.
25489 o Build changes, also included in 0.2.1.29:
25490 - Tor does not build packages correctly with Automake 1.6 and earlier;
25491 added a check to Makefile.am to make sure that we're building with
25492 Automake 1.7 or later.
25493 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
25494 because we built it with a too-old version of automake. Thus that
25495 release broke ./configure --enable-openbsd-malloc, which is popular
25496 among really fast exit relays on Linux.
25498 o Major bugfixes, new in 0.2.2.21-alpha:
25499 - Prevent crash/heap corruption when the cbtnummodes consensus
25500 parameter is set to 0 or large values. Fixes bug 2317; bugfix
25503 o Major features, new in 0.2.2.21-alpha:
25504 - Introduce minimum/maximum values that clients will believe
25505 from the consensus. Now we'll have a better chance to avoid crashes
25506 or worse when a consensus param has a weird value.
25508 o Minor features, new in 0.2.2.21-alpha:
25509 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
25510 used on bridges, and it makes bridge scanning somewhat easier.
25511 - If writing the state file to disk fails, wait up to an hour before
25512 retrying again, rather than trying again each second. Fixes bug
25513 2346; bugfix on Tor 0.1.1.3-alpha.
25514 - Make Libevent log messages get delivered to controllers later,
25515 and not from inside the Libevent log handler. This prevents unsafe
25516 reentrant Libevent calls while still letting the log messages
25518 - Detect platforms that brokenly use a signed size_t, and refuse to
25519 build there. Found and analyzed by doorss and rransom.
25520 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
25523 o Minor bugfixes, new in 0.2.2.21-alpha:
25524 - Handle SOCKS messages longer than 128 bytes long correctly, rather
25525 than waiting forever for them to finish. Fixes bug 2330; bugfix
25526 on 0.2.0.16-alpha. Found by doorss.
25527 - Add assertions to check for overflow in arguments to
25528 base32_encode() and base32_decode(); fix a signed-unsigned
25529 comparison there too. These bugs are not actually reachable in Tor,
25530 but it's good to prevent future errors too. Found by doorss.
25531 - Correctly detect failures to create DNS requests when using Libevent
25532 versions before v2. (Before Libevent 2, we used our own evdns
25533 implementation. Its return values for Libevent's evdns_resolve_*()
25534 functions are not consistent with those from Libevent.) Fixes bug
25535 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
25537 o Documentation, new in 0.2.2.21-alpha:
25538 - Document the default socks host and port (127.0.0.1:9050) for
25542 Changes in version 0.2.1.29 - 2011-01-15
25543 Tor 0.2.1.29 continues our recent code security audit work. The main
25544 fix resolves a remote heap overflow vulnerability that can allow remote
25545 code execution. Other fixes address a variety of assert and crash bugs,
25546 most of which we think are hard to exploit remotely.
25548 o Major bugfixes (security):
25549 - Fix a heap overflow bug where an adversary could cause heap
25550 corruption. This bug probably allows remote code execution
25551 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
25553 - Prevent a denial-of-service attack by disallowing any
25554 zlib-compressed data whose compression factor is implausibly
25555 high. Fixes part of bug 2324; reported by "doorss".
25556 - Zero out a few more keys in memory before freeing them. Fixes
25557 bug 2384 and part of bug 2385. These key instances found by
25558 "cypherpunks", based on Andrew Case's report about being able
25559 to find sensitive data in Tor's memory space if you have enough
25560 permissions. Bugfix on 0.0.2pre9.
25562 o Major bugfixes (crashes):
25563 - Prevent calls to Libevent from inside Libevent log handlers.
25564 This had potential to cause a nasty set of crashes, especially
25565 if running Libevent with debug logging enabled, and running
25566 Tor with a controller watching for low-severity log messages.
25567 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
25568 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
25569 underflow errors there too. Fixes the other part of bug 2324.
25570 - Fix a bug where we would assert if we ever had a
25571 cached-descriptors.new file (or another file read directly into
25572 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
25573 on 0.2.1.25. Found by doorss.
25574 - Fix some potential asserts and parsing issues with grossly
25575 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
25578 o Minor bugfixes (other):
25579 - Fix a bug with handling misformed replies to reverse DNS lookup
25580 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
25581 bug reported by doorss.
25582 - Fix compilation on mingw when a pthreads compatibility library
25583 has been installed. (We don't want to use it, so we shouldn't
25584 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
25585 - Fix a bug where we would declare that we had run out of virtual
25586 addresses when the address space was only half-exhausted. Bugfix
25588 - Correctly handle the case where AutomapHostsOnResolve is set but
25589 no virtual addresses are available. Fixes bug 2328; bugfix on
25590 0.1.2.1-alpha. Bug found by doorss.
25591 - Correctly handle wrapping around to when we run out of virtual
25592 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
25593 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
25594 because we built it with a too-old version of automake. Thus that
25595 release broke ./configure --enable-openbsd-malloc, which is popular
25596 among really fast exit relays on Linux.
25599 - Update to the January 1 2011 Maxmind GeoLite Country database.
25600 - Introduce output size checks on all of our decryption functions.
25603 - Tor does not build packages correctly with Automake 1.6 and earlier;
25604 added a check to Makefile.am to make sure that we're building with
25605 Automake 1.7 or later.
25608 Changes in version 0.2.2.20-alpha - 2010-12-17
25609 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
25610 exploitable bugs. We also fix a variety of other significant bugs,
25611 change the IP address for one of our directory authorities, and update
25612 the minimum version that Tor relays must run to join the network.
25615 - Fix a remotely exploitable bug that could be used to crash instances
25616 of Tor remotely by overflowing on the heap. Remote-code execution
25617 hasn't been confirmed, but can't be ruled out. Everyone should
25618 upgrade. Bugfix on the 0.1.1 series and later.
25619 - Fix a bug that could break accounting on 64-bit systems with large
25620 time_t values, making them hibernate for impossibly long intervals.
25621 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
25622 - Fix a logic error in directory_fetches_from_authorities() that
25623 would cause all _non_-exits refusing single-hop-like circuits
25624 to fetch from authorities, when we wanted to have _exits_ fetch
25625 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
25627 - Fix a stream fairness bug that would cause newer streams on a given
25628 circuit to get preference when reading bytes from the origin or
25629 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
25630 introduced before the first Tor release, in svn revision r152.
25632 o Directory authority changes:
25633 - Change IP address and ports for gabelmoo (v3 directory authority).
25636 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
25637 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
25638 - Fix an off-by-one error in calculating some controller command
25639 argument lengths. Fortunately, this mistake is harmless since
25640 the controller code does redundant NUL termination too. Found by
25641 boboper. Bugfix on 0.1.1.1-alpha.
25642 - Do not dereference NULL if a bridge fails to build its
25643 extra-info descriptor. Found by an anonymous commenter on
25644 Trac. Bugfix on 0.2.2.19-alpha.
25647 - Update to the December 1 2010 Maxmind GeoLite Country database.
25648 - Directory authorities now reject relays running any versions of
25649 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
25650 known bugs that keep RELAY_EARLY cells from working on rendezvous
25651 circuits. Followup to fix for bug 2081.
25652 - Directory authorities now reject relays running any version of Tor
25653 older than 0.2.0.26-rc. That version is the earliest that fetches
25654 current directory information correctly. Fixes bug 2156.
25655 - Report only the top 10 ports in exit-port stats in order not to
25656 exceed the maximum extra-info descriptor length of 50 KB. Implements
25660 Changes in version 0.2.1.28 - 2010-12-17
25661 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
25662 exploitable bugs. We also took this opportunity to change the IP address
25663 for one of our directory authorities, and to update the geoip database
25667 - Fix a remotely exploitable bug that could be used to crash instances
25668 of Tor remotely by overflowing on the heap. Remote-code execution
25669 hasn't been confirmed, but can't be ruled out. Everyone should
25670 upgrade. Bugfix on the 0.1.1 series and later.
25672 o Directory authority changes:
25673 - Change IP address and ports for gabelmoo (v3 directory authority).
25676 - Update to the December 1 2010 Maxmind GeoLite Country database.
25679 Changes in version 0.2.1.27 - 2010-11-23
25680 Yet another OpenSSL security patch broke its compatibility with Tor:
25681 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
25682 also took this opportunity to fix several crash bugs, integrate a new
25683 directory authority, and update the bundled GeoIP database.
25686 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
25687 No longer set the tlsext_host_name extension on server SSL objects;
25688 but continue to set it on client SSL objects. Our goal in setting
25689 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
25690 bugfix on 0.2.1.1-alpha.
25691 - Do not log messages to the controller while shrinking buffer
25692 freelists. Doing so would sometimes make the controller connection
25693 try to allocate a buffer chunk, which would mess up the internals
25694 of the freelist and cause an assertion failure. Fixes bug 1125;
25695 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
25696 - Learn our external IP address when we're a relay or bridge, even if
25697 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
25698 where we introduced bridge relays that don't need to publish to
25699 be useful. Fixes bug 2050.
25700 - Do even more to reject (and not just ignore) annotations on
25701 router descriptors received anywhere but from the cache. Previously
25702 we would ignore such annotations at first, but cache them to disk
25703 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
25704 - When you're using bridges and your network goes away and your
25705 bridges get marked as down, recover when you attempt a new socks
25706 connection (if the network is back), rather than waiting up to an
25707 hour to try fetching new descriptors for your bridges. Bugfix on
25708 0.2.0.3-alpha; fixes bug 1981.
25711 - Move to the November 2010 Maxmind GeoLite country db (rather
25712 than the June 2009 ip-to-country GeoIP db) for our statistics that
25713 count how many users relays are seeing from each country. Now we'll
25714 have more accurate data, especially for many African countries.
25716 o New directory authorities:
25717 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
25721 - Fix an assertion failure that could occur in directory caches or
25722 bridge users when using a very short voting interval on a testing
25723 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
25725 - Enforce multiplicity rules when parsing annotations. Bugfix on
25726 0.2.0.8-alpha. Found by piebeer.
25727 - Allow handshaking OR connections to take a full KeepalivePeriod
25728 seconds to handshake. Previously, we would close them after
25729 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
25730 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
25732 - When building with --enable-gcc-warnings on OpenBSD, disable
25733 warnings in system headers. This makes --enable-gcc-warnings
25734 pass on OpenBSD 4.8.
25737 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
25738 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
25739 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
25740 Servers can start sending this code when enough clients recognize
25741 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
25742 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
25743 Patch from mingw-san.
25746 - Remove the old debian/ directory from the main Tor distribution.
25747 The official Tor-for-debian git repository lives at the URL
25748 https://git.torproject.org/debian/tor.git
25749 - Stop shipping the old doc/website/ directory in the tarball. We
25750 changed the website format in late 2010, and what we shipped in
25751 0.2.1.26 really wasn't that useful anyway.
25754 Changes in version 0.2.2.19-alpha - 2010-11-22
25755 Yet another OpenSSL security patch broke its compatibility with Tor:
25756 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
25759 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
25760 No longer set the tlsext_host_name extension on server SSL objects;
25761 but continue to set it on client SSL objects. Our goal in setting
25762 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
25763 bugfix on 0.2.1.1-alpha.
25766 - Try harder not to exceed the maximum length of 50 KB when writing
25767 statistics to extra-info descriptors. This bug was triggered by very
25768 fast relays reporting exit-port, entry, and dirreq statistics.
25769 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
25770 - Publish a router descriptor even if generating an extra-info
25771 descriptor fails. Previously we would not publish a router
25772 descriptor without an extra-info descriptor; this can cause fast
25773 exit relays collecting exit-port statistics to drop from the
25774 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
25777 Changes in version 0.2.2.18-alpha - 2010-11-16
25778 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
25779 us lately, makes unpublished bridge relays able to detect their IP
25780 address, and fixes a wide variety of other bugs to get us much closer
25781 to a stable release.
25784 - Do even more to reject (and not just ignore) annotations on
25785 router descriptors received anywhere but from the cache. Previously
25786 we would ignore such annotations at first, but cache them to disk
25787 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
25788 - Do not log messages to the controller while shrinking buffer
25789 freelists. Doing so would sometimes make the controller connection
25790 try to allocate a buffer chunk, which would mess up the internals
25791 of the freelist and cause an assertion failure. Fixes bug 1125;
25792 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
25793 - Learn our external IP address when we're a relay or bridge, even if
25794 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
25795 where we introduced bridge relays that don't need to publish to
25796 be useful. Fixes bug 2050.
25797 - Maintain separate TLS contexts and certificates for incoming and
25798 outgoing connections in bridge relays. Previously we would use the
25799 same TLS contexts and certs for incoming and outgoing connections.
25800 Bugfix on 0.2.0.3-alpha; addresses bug 988.
25801 - Maintain separate identity keys for incoming and outgoing TLS
25802 contexts in bridge relays. Previously we would use the same
25803 identity keys for incoming and outgoing TLS contexts. Bugfix on
25804 0.2.0.3-alpha; addresses the other half of bug 988.
25805 - Avoid an assertion failure when we as an authority receive a
25806 duplicate upload of a router descriptor that we already have,
25807 but which we previously considered an obsolete descriptor.
25808 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
25809 - Avoid a crash bug triggered by looking at a dangling pointer while
25810 setting the network status consensus. Found by Robert Ransom.
25811 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
25812 - Fix a logic error where servers that _didn't_ act as exits would
25813 try to keep their server lists more aggressively up to date than
25814 exits, when it was supposed to be the other way around. Bugfix
25817 o Minor bugfixes (on Tor 0.2.1.x and earlier):
25818 - When we're trying to guess whether we know our IP address as
25819 a relay, we would log various ways that we failed to guess
25820 our address, but never log that we ended up guessing it
25821 successfully. Now add a log line to help confused and anxious
25822 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
25823 - Bring the logic that gathers routerinfos and assesses the
25824 acceptability of circuits into line. This prevents a Tor OP from
25825 getting locked in a cycle of choosing its local OR as an exit for a
25826 path (due to a .exit request) and then rejecting the circuit because
25827 its OR is not listed yet. It also prevents Tor clients from using an
25828 OR running in the same instance as an exit (due to a .exit request)
25829 if the OR does not meet the same requirements expected of an OR
25830 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25831 - Correctly describe errors that occur when generating a TLS object.
25832 Previously we would attribute them to a failure while generating a
25833 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
25835 - Enforce multiplicity rules when parsing annotations. Bugfix on
25836 0.2.0.8-alpha. Found by piebeer.
25837 - Fix warnings that newer versions of autoconf produced during
25838 ./autogen.sh. These warnings appear to be harmless in our case,
25839 but they were extremely verbose. Fixes bug 2020.
25841 o Minor bugfixes (on Tor 0.2.2.x):
25842 - Enable protection of small arrays whenever we build with gcc
25843 hardening features, not only when also building with warnings
25844 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
25847 - Make hidden services work better in private Tor networks by not
25848 requiring any uptime to join the hidden service descriptor
25849 DHT. Implements ticket 2088.
25850 - Rate-limit the "your application is giving Tor only an IP address"
25851 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
25852 - When AllowSingleHopExits is set, print a warning to explain to the
25853 relay operator why most clients are avoiding her relay.
25854 - Update to the November 1 2010 Maxmind GeoLite Country database.
25856 o Code simplifications and refactoring:
25857 - When we fixed bug 1038 we had to put in a restriction not to send
25858 RELAY_EARLY cells on rend circuits. This was necessary as long
25859 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
25860 active. Now remove this obsolete check. Resolves bug 2081.
25861 - Some options used different conventions for uppercasing of acronyms
25862 when comparing manpage and source. Fix those in favor of the
25863 manpage, as it makes sense to capitalize acronyms.
25864 - Remove the torrc.complete file. It hasn't been kept up to date
25865 and users will have better luck checking out the manpage.
25866 - Remove the obsolete "NoPublish" option; it has been flagged
25867 as obsolete and has produced a warning since 0.1.1.18-rc.
25868 - Remove everything related to building the expert bundle for OS X.
25869 It has confused many users, doesn't work right on OS X 10.6,
25870 and is hard to get rid of once installed. Resolves bug 1274.
25873 Changes in version 0.2.2.17-alpha - 2010-09-30
25874 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
25875 to use one-hop circuits (which can put the exit relays at higher risk,
25876 plus unbalance the network); fixes a big bug in bandwidth accounting
25877 for relays that want to limit their monthly bandwidth use; fixes a
25878 big pile of bugs in how clients tolerate temporary network failure;
25879 and makes our adaptive circuit build timeout feature (which improves
25880 client performance if your network is fast while not breaking things
25881 if your network is slow) better handle bad networks.
25884 - Exit relays now try harder to block exit attempts from unknown
25885 relays, to make it harder for people to use them as one-hop proxies
25886 a la tortunnel. Controlled by the refuseunknownexits consensus
25887 parameter (currently enabled), or you can override it on your
25888 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
25890 o Major bugfixes (0.2.1.x and earlier):
25891 - Fix a bug in bandwidth accounting that could make us use twice
25892 the intended bandwidth when our interval start changes due to
25893 daylight saving time. Now we tolerate skew in stored vs computed
25894 interval starts: if the start of the period changes by no more than
25895 50% of the period's duration, we remember bytes that we transferred
25896 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
25897 - Always search the Windows system directory for system DLLs, and
25898 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
25899 - When you're using bridges and your network goes away and your
25900 bridges get marked as down, recover when you attempt a new socks
25901 connection (if the network is back), rather than waiting up to an
25902 hour to try fetching new descriptors for your bridges. Bugfix on
25903 0.2.0.3-alpha; fixes bug 1981.
25905 o Major bugfixes (on 0.2.2.x):
25906 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
25908 - Fix a segfault that could happen when operating a bridge relay with
25909 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
25910 - The consensus bandwidth-weights (used by clients to choose fast
25911 relays) entered an unexpected edge case in September where
25912 Exits were much scarcer than Guards, resulting in bad weight
25913 recommendations. Now we compute them using new constraints that
25914 should succeed in all cases. Also alter directory authorities to
25915 not include the bandwidth-weights line if they fail to produce
25916 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
25917 - When weighting bridges during path selection, we used to trust
25918 the bandwidths they provided in their descriptor, only capping them
25919 at 10MB/s. This turned out to be problematic for two reasons:
25920 Bridges could claim to handle a lot more traffic then they
25921 actually would, thus making more clients pick them and have a
25922 pretty effective DoS attack. The other issue is that new bridges
25923 that might not have a good estimate for their bw capacity yet
25924 would not get used at all unless no other bridges are available
25925 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
25927 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
25928 - Ignore cannibalized circuits when recording circuit build times.
25929 This should provide for a minor performance improvement for hidden
25930 service users using 0.2.2.14-alpha, and should remove two spurious
25931 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
25932 - Simplify the logic that causes us to decide if the network is
25933 unavailable for purposes of recording circuit build times. If we
25934 receive no cells whatsoever for the entire duration of a circuit's
25935 full measured lifetime, the network is probably down. Also ignore
25936 one-hop directory fetching circuit timeouts when calculating our
25937 circuit build times. These changes should hopefully reduce the
25938 cases where we see ridiculous circuit build timeouts for people
25939 with spotty wireless connections. Fixes part of bug 1772; bugfix
25941 - Prevent the circuit build timeout from becoming larger than
25942 the maximum build time we have ever seen. Also, prevent the time
25943 period for measurement circuits from becoming larger than twice that
25944 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
25947 - When we run out of directory information such that we can't build
25948 circuits, but then get enough that we can build circuits, log when
25949 we actually construct a circuit, so the user has a better chance of
25950 knowing what's going on. Fixes bug 1362.
25951 - Be more generous with how much bandwidth we'd use up (with
25952 accounting enabled) before entering "soft hibernation". Previously,
25953 we'd refuse new connections and circuits once we'd used up 95% of
25954 our allotment. Now, we use up 95% of our allotment, AND make sure
25955 that we have no more than 500MB (or 3 hours of expected traffic,
25956 whichever is lower) remaining before we enter soft hibernation.
25957 - If we've configured EntryNodes and our network goes away and/or all
25958 our entrynodes get marked down, optimistically retry them all when
25959 a new socks application request appears. Fixes bug 1882.
25960 - Add some more defensive programming for architectures that can't
25961 handle unaligned integer accesses. We don't know of any actual bugs
25962 right now, but that's the best time to fix them. Fixes bug 1943.
25963 - Support line continuations in the torrc config file. If a line
25964 ends with a single backslash character, the newline is ignored, and
25965 the configuration value is treated as continuing on the next line.
25968 o Minor bugfixes (on 0.2.1.x and earlier):
25969 - For bandwidth accounting, calculate our expected bandwidth rate
25970 based on the time during which we were active and not in
25971 soft-hibernation during the last interval. Previously, we were
25972 also considering the time spent in soft-hibernation. If this
25973 was a long time, we would wind up underestimating our bandwidth
25974 by a lot, and skewing our wakeup time towards the start of the
25975 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
25977 o Minor bugfixes (on 0.2.2.x):
25978 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
25979 which were disabled by the circuit build timeout changes in
25980 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
25981 - Make sure we don't warn about missing bandwidth weights when
25982 choosing bridges or other relays not in the consensus. Bugfix on
25983 0.2.2.10-alpha; fixes bug 1805.
25984 - In our logs, do not double-report signatures from unrecognized
25985 authorities both as "from unknown authority" and "not
25986 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
25989 Changes in version 0.2.2.16-alpha - 2010-09-17
25990 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
25991 evident at exit relays), and also continues to resolve all the little
25992 bugs that have been filling up trac lately.
25994 o Major bugfixes (stream-level fairness):
25995 - When receiving a circuit-level SENDME for a blocked circuit, try
25996 to package cells fairly from all the streams that had previously
25997 been blocked on that circuit. Previously, we had started with the
25998 oldest stream, and allowed each stream to potentially exhaust
25999 the circuit's package window. This gave older streams on any
26000 given circuit priority over newer ones. Fixes bug 1937. Detected
26001 originally by Camilo Viecco. This bug was introduced before the
26002 first Tor release, in svn commit r152: it is the new winner of
26003 the longest-lived bug prize.
26004 - When the exit relay got a circuit-level sendme cell, it started
26005 reading on the exit streams, even if had 500 cells queued in the
26006 circuit queue already, so the circuit queue just grew and grew in
26007 some cases. We fix this by not re-enabling reading on receipt of a
26008 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
26009 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
26011 - Newly created streams were allowed to read cells onto circuits,
26012 even if the circuit's cell queue was blocked and waiting to drain.
26013 This created potential unfairness, as older streams would be
26014 blocked, but newer streams would gladly fill the queue completely.
26015 We add code to detect this situation and prevent any stream from
26016 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
26020 - Update to the September 1 2010 Maxmind GeoLite Country database.
26021 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
26022 not. This would lead to a cookie that is still not group readable.
26023 Closes bug 1843. Suggested by katmagic.
26024 - When logging a rate-limited warning, we now mention how many messages
26025 got suppressed since the last warning.
26026 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
26027 do individual connection-level rate limiting of clients. The torrc
26028 config options with the same names trump the consensus params, if
26029 both are present. Replaces the old "bwconnrate" and "bwconnburst"
26030 consensus params which were broken from 0.2.2.7-alpha through
26031 0.2.2.14-alpha. Closes bug 1947.
26032 - When a router changes IP address or port, authorities now launch
26033 a new reachability test for it. Implements ticket 1899.
26034 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
26035 2 no signature, 4 required" messages about consensus signatures
26036 easier to read, and make sure they get logged at the same severity
26037 as the messages explaining which keys are which. Fixes bug 1290.
26038 - Don't warn when we have a consensus that we can't verify because
26039 of missing certificates, unless those certificates are ones
26040 that we have been trying and failing to download. Fixes bug 1145.
26041 - If you configure your bridge with a known identity fingerprint,
26042 and the bridge authority is unreachable (as it is in at least
26043 one country now), fall back to directly requesting the descriptor
26044 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
26046 - When building with --enable-gcc-warnings on OpenBSD, disable
26047 warnings in system headers. This makes --enable-gcc-warnings
26048 pass on OpenBSD 4.8.
26050 o Minor bugfixes (on 0.2.1.x and earlier):
26051 - Authorities will now attempt to download consensuses if their
26052 own efforts to make a live consensus have failed. This change
26053 means authorities that restart will fetch a valid consensus, and
26054 it means authorities that didn't agree with the current consensus
26055 will still fetch and serve it if it has enough signatures. Bugfix
26056 on 0.2.0.9-alpha; fixes bug 1300.
26057 - Ensure DNS requests launched by "RESOLVE" commands from the
26058 controller respect the __LeaveStreamsUnattached setconf options. The
26059 same goes for requests launched via DNSPort or transparent
26060 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
26061 - Allow handshaking OR connections to take a full KeepalivePeriod
26062 seconds to handshake. Previously, we would close them after
26063 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
26064 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
26066 - Rate-limit "Failed to hand off onionskin" warnings.
26067 - Never relay a cell for a circuit we have already destroyed.
26068 Between marking a circuit as closeable and finally closing it,
26069 it may have been possible for a few queued cells to get relayed,
26070 even though they would have been immediately dropped by the next
26071 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
26072 - Never queue a cell for a circuit that's already been marked
26074 - Never vote for a server as "Running" if we have a descriptor for
26075 it claiming to be hibernating, and that descriptor was published
26076 more recently than our last contact with the server. Bugfix on
26077 0.2.0.3-alpha; fixes bug 911.
26078 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
26081 o Minor bugfixes (on 0.2.2.x):
26082 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
26083 down if a directory fetch fails and you've configured either
26084 bridges or EntryNodes. The intent was to mark the relay as down
26085 _unless_ you're using bridges or EntryNodes, since if you are
26086 then you could quickly run out of entry points.
26087 - Fix the Windows directory-listing code. A bug introduced in
26088 0.2.2.14-alpha could make Windows directory servers forget to load
26089 some of their cached v2 networkstatus files.
26090 - Really allow clients to use relays as bridges. Fixes bug 1776;
26091 bugfix on 0.2.2.15-alpha.
26092 - Demote a warn to info that happens when the CellStatistics option
26093 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
26094 Reported by Moritz Bartl.
26095 - On Windows, build correctly either with or without Unicode support.
26096 This is necessary so that Tor can support fringe platforms like
26097 Windows 98 (which has no Unicode), or Windows CE (which has no
26098 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
26101 - Add a unit test for cross-platform directory-listing code.
26104 Changes in version 0.2.2.15-alpha - 2010-08-18
26105 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
26106 fixes a variety of other bugs that were preventing performance
26107 experiments from moving forward, fixes several bothersome memory leaks,
26108 and generally closes a lot of smaller bugs that have been filling up
26112 - Stop assigning the HSDir flag to relays that disable their
26113 DirPort (and thus will refuse to answer directory requests). This
26114 fix should dramatically improve the reachability of hidden services:
26115 hidden services and hidden service clients pick six HSDir relays
26116 to store and retrieve the hidden service descriptor, and currently
26117 about half of the HSDir relays will refuse to work. Bugfix on
26118 0.2.0.10-alpha; fixes part of bug 1693.
26119 - The PerConnBWRate and Burst config options, along with the
26120 bwconnrate and bwconnburst consensus params, initialized each conn's
26121 token bucket values only when the connection is established. Now we
26122 update them if the config options change, and update them every time
26123 we get a new consensus. Otherwise we can encounter an ugly edge
26124 case where we initialize an OR conn to client-level bandwidth,
26125 but then later the relay joins the consensus and we leave it
26126 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
26127 - Fix a regression that caused Tor to rebind its ports if it receives
26128 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
26131 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
26132 should give us approximately 40-50% more Guard-flagged nodes,
26133 improving the anonymity the Tor network can provide and also
26134 decreasing the dropoff in throughput that relays experience when
26135 they first get the Guard flag.
26136 - Allow enabling or disabling the *Statistics config options while
26140 - Update to the August 1 2010 Maxmind GeoLite Country database.
26141 - Have the controller interface give a more useful message than
26142 "Internal Error" in response to failed GETINFO requests.
26143 - Warn when the same option is provided more than once in a torrc
26144 file, on the command line, or in a single SETCONF statement, and
26145 the option is one that only accepts a single line. Closes bug 1384.
26146 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
26147 Patch from mingw-san.
26148 - Add support for the country code "{??}" in torrc options like
26149 ExcludeNodes, to indicate all routers of unknown country. Closes
26151 - Relays report the number of bytes spent on answering directory
26152 requests in extra-info descriptors similar to {read,write}-history.
26153 Implements enhancement 1790.
26155 o Minor bugfixes (on 0.2.1.x and earlier):
26156 - Complain if PublishServerDescriptor is given multiple arguments that
26157 include 0 or 1. This configuration will be rejected in the future.
26158 Bugfix on 0.2.0.1-alpha; closes bug 1107.
26159 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
26160 Bugfix on 0.2.0.13-alpha; closes bug 928.
26161 - Change "Application request when we're believed to be offline."
26162 notice to "Application request when we haven't used client
26163 functionality lately.", to clarify that it's not an error. Bugfix
26164 on 0.0.9.3; fixes bug 1222.
26165 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
26166 would return "551 Internal error" rather than "552 Unrecognized key
26167 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
26168 - Users can't configure a regular relay to be their bridge. It didn't
26169 work because when Tor fetched the bridge descriptor, it found
26170 that it already had it, and didn't realize that the purpose of the
26171 descriptor had changed. Now we replace routers with a purpose other
26172 than bridge with bridge descriptors when fetching them. Bugfix on
26173 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
26174 refetch the descriptor with router purpose 'general', disabling
26176 - Fix a rare bug in rend_fn unit tests: we would fail a test when
26177 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
26178 on 0.2.0.10-alpha; fixes bug 1808.
26179 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
26180 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
26181 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
26182 Servers can start sending this code when enough clients recognize
26183 it. Also update the spec to reflect this new reason. Bugfix on
26184 0.1.0.1-rc; fixes part of bug 1793.
26185 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
26186 when we switch from being a public relay to a bridge. Otherwise
26187 there will still be clients that see the relay in their consensus,
26188 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
26190 - Instead of giving an assertion failure on an internal mismatch
26191 on estimated freelist size, just log a BUG warning and try later.
26192 Mitigates but does not fix bug 1125.
26193 - Fix an assertion failure that could occur in caches or bridge users
26194 when using a very short voting interval on a testing network.
26195 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
26197 o Minor bugfixes (on 0.2.2.x):
26198 - Alter directory authorities to always consider Exit-flagged nodes
26199 as potential Guard nodes in their votes. The actual decision to
26200 use Exits as Guards is done in the consensus bandwidth weights.
26201 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
26202 - When the controller is reporting the purpose of circuits that
26203 didn't finish building before the circuit build timeout, it was
26204 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
26205 - Our libevent version parsing code couldn't handle versions like
26206 1.4.14b-stable and incorrectly warned the user about using an
26207 old and broken version of libevent. Treat 1.4.14b-stable like
26208 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
26210 - Don't use substitution references like $(VAR:MOD) when
26211 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
26212 '$(:x)' to 'x' rather than the empty string. This bites us in
26213 doc/ when configured with --disable-asciidoc. Bugfix on
26214 0.2.2.9-alpha; fixes bug 1773.
26215 - Remove a spurious hidden service server-side log notice about
26216 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
26218 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
26220 - Correctly report written bytes on linked connections. Found while
26221 implementing 1790. Bugfix on 0.2.2.4-alpha.
26222 - Fix three memory leaks: one in circuit_build_times_parse_state(),
26223 one in dirvote_add_signatures_to_pending_consensus(), and one every
26224 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
26225 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
26227 o Code simplifications and refactoring:
26228 - Take a first step towards making or.h smaller by splitting out
26229 function definitions for all source files in src/or/. Leave
26230 structures and defines in or.h for now.
26231 - Remove a bunch of unused function declarations as well as a block of
26232 #if 0'd code from the unit tests. Closes bug 1824.
26233 - New unit tests for exit-port history statistics; refactored exit
26234 statistics code to be more easily tested.
26235 - Remove the old debian/ directory from the main Tor distribution.
26236 The official Tor-for-debian git repository lives at the URL
26237 https://git.torproject.org/debian/tor.git
26240 Changes in version 0.2.2.14-alpha - 2010-07-12
26241 Tor 0.2.2.14-alpha greatly improves client-side handling of
26242 circuit build timeouts, which are used to estimate speed and improve
26243 performance. We also move to a much better GeoIP database, port Tor to
26244 Windows CE, introduce new compile flags that improve code security,
26245 add an eighth v3 directory authority, and address a lot of more
26249 - Tor directory authorities no longer crash when started with a
26250 cached-microdesc-consensus file in their data directory. Bugfix
26251 on 0.2.2.6-alpha; fixes bug 1532.
26252 - Treat an unset $HOME like an empty $HOME rather than triggering an
26253 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
26254 - Ignore negative and large circuit build timeout values that can
26255 happen during a suspend or hibernate. These values caused various
26256 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
26257 - Alter calculation of Pareto distribution parameter 'Xm' for
26258 Circuit Build Timeout learning to use the weighted average of the
26259 top N=3 modes (because we have three entry guards). Considering
26260 multiple modes should improve the timeout calculation in some cases,
26261 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
26263 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
26264 right censored distribution model. This approach improves over the
26265 synthetic timeout generation approach that was producing insanely
26266 high timeout values. Now we calculate build timeouts using truncated
26267 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
26268 - Do not close circuits that are under construction when they reach
26269 the circuit build timeout. Instead, leave them building (but do not
26270 use them) for up until the time corresponding to the 95th percentile
26271 on the Pareto CDF or 60 seconds, whichever is greater. This is done
26272 to provide better data for the new Pareto model. This percentile
26273 can be controlled by the consensus.
26276 - Move to the June 2010 Maxmind GeoLite country db (rather than the
26277 June 2009 ip-to-country GeoIP db) for our statistics that count
26278 how many users relays are seeing from each country. Now we have
26279 more accurate data for many African countries.
26280 - Port Tor to build and run correctly on Windows CE systems, using
26281 the wcecompat library. Contributed by Valerio Lupi.
26282 - New "--enable-gcc-hardening" ./configure flag (off by default)
26283 to turn on gcc compile time hardening options. It ensures
26284 that signed ints have defined behavior (-fwrapv), enables
26285 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
26286 with canaries (-fstack-protector-all), turns on ASLR protection if
26287 supported by the kernel (-fPIE, -pie), and adds additional security
26288 related warnings. Verified to work on Mac OS X and Debian Lenny.
26289 - New "--enable-linker-hardening" ./configure flag (off by default)
26290 to turn on ELF specific hardening features (relro, now). This does
26291 not work with Mac OS X or any other non-ELF binary format.
26293 o New directory authorities:
26294 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
26298 - New config option "WarnUnsafeSocks 0" disables the warning that
26299 occurs whenever Tor receives a socks handshake using a version of
26300 the socks protocol that can only provide an IP address (rather
26301 than a hostname). Setups that do DNS locally over Tor are fine,
26302 and we shouldn't spam the logs in that case.
26303 - Convert the HACKING file to asciidoc, and add a few new sections
26304 to it, explaining how we use Git, how we make changelogs, and
26305 what should go in a patch.
26306 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
26307 event, to give information on the current rate of circuit timeouts
26308 over our stored history.
26309 - Add ability to disable circuit build time learning via consensus
26310 parameter and via a LearnCircuitBuildTimeout config option. Also
26311 automatically disable circuit build time calculation if we are
26312 either a AuthoritativeDirectory, or if we fail to write our state
26313 file. Fixes bug 1296.
26314 - More gracefully handle corrupt state files, removing asserts
26315 in favor of saving a backup and resetting state.
26316 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
26320 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
26322 - When a2x fails, mention that the user could disable manpages instead
26323 of trying to fix their asciidoc installation.
26324 - Where available, use Libevent 2.0's periodic timers so that our
26325 once-per-second cleanup code gets called even more closely to
26326 once per second than it would otherwise. Fixes bug 943.
26327 - If you run a bridge that listens on multiple IP addresses, and
26328 some user configures a bridge address that uses a different IP
26329 address than your bridge writes in its router descriptor, and the
26330 user doesn't specify an identity key, their Tor would discard the
26331 descriptor because "it isn't one of our configured bridges", and
26332 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
26333 Bugfix on 0.2.0.3-alpha.
26334 - If OpenSSL fails to make a duplicate of a private or public key, log
26335 an error message and try to exit cleanly. May help with debugging
26336 if bug 1209 ever remanifests.
26337 - Save a couple bytes in memory allocation every time we escape
26338 certain characters in a string. Patch from Florian Zumbiehl.
26339 - Make it explicit that we don't cannibalize one-hop circuits. This
26340 happens in the wild, but doesn't turn out to be a problem because
26341 we fortunately don't use those circuits. Many thanks to outofwords
26342 for the initial analysis and to swissknife who confirmed that
26343 two-hop circuits are actually created.
26344 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
26345 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
26346 - Eliminate a case where a circuit build time warning was displayed
26347 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
26350 Changes in version 0.2.1.26 - 2010-05-02
26351 Tor 0.2.1.26 addresses the recent connection and memory overload
26352 problems we've been seeing on relays, especially relays with their
26353 DirPort open. If your relay has been crashing, or you turned it off
26354 because it used too many resources, give this release a try.
26356 This release also fixes yet another instance of broken OpenSSL libraries
26357 that was causing some relays to drop out of the consensus.
26360 - Teach relays to defend themselves from connection overload. Relays
26361 now close idle circuits early if it looks like they were intended
26362 for directory fetches. Relays are also more aggressive about closing
26363 TLS connections that have no circuits on them. Such circuits are
26364 unlikely to be re-used, and tens of thousands of them were piling
26365 up at the fast relays, causing the relays to run out of sockets
26366 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26367 their directory fetches over TLS).
26368 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26369 that claim to be earlier than 0.9.8m, but which have in reality
26370 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26371 behavior. Possible fix for some cases of bug 1346.
26372 - Directory mirrors were fetching relay descriptors only from v2
26373 directory authorities, rather than v3 authorities like they should.
26374 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26375 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26378 - Finally get rid of the deprecated and now harmful notion of "clique
26379 mode", where directory authorities maintain TLS connections to
26383 - In the util/threads test, no longer free the test_mutex before all
26384 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26385 - The master thread could starve the worker threads quite badly on
26386 certain systems, causing them to run only partially in the allowed
26387 window. This resulted in test failures. Now the master thread sleeps
26388 occasionally for a few microseconds while the two worker-threads
26389 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26392 Changes in version 0.2.2.13-alpha - 2010-04-24
26393 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
26394 problems we've been seeing on relays, especially relays with their
26395 DirPort open. If your relay has been crashing, or you turned it off
26396 because it used too many resources, give this release a try.
26399 - Teach relays to defend themselves from connection overload. Relays
26400 now close idle circuits early if it looks like they were intended
26401 for directory fetches. Relays are also more aggressive about closing
26402 TLS connections that have no circuits on them. Such circuits are
26403 unlikely to be re-used, and tens of thousands of them were piling
26404 up at the fast relays, causing the relays to run out of sockets
26405 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26406 their directory fetches over TLS).
26409 - Finally get rid of the deprecated and now harmful notion of "clique
26410 mode", where directory authorities maintain TLS connections to
26412 - Directory authorities now do an immediate reachability check as soon
26413 as they hear about a new relay. This change should slightly reduce
26414 the time between setting up a relay and getting listed as running
26415 in the consensus. It should also improve the time between setting
26416 up a bridge and seeing use by bridge users.
26417 - Directory authorities no longer launch a TLS connection to every
26418 relay as they startup. Now that we have 2k+ descriptors cached,
26419 the resulting network hiccup is becoming a burden. Besides,
26420 authorities already avoid voting about Running for the first half
26421 hour of their uptime.
26424 Changes in version 0.2.2.12-alpha - 2010-04-20
26425 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
26426 handle and vote on descriptors. It was causing relays to drop out of
26430 - Many relays have been falling out of the consensus lately because
26431 not enough authorities know about their descriptor for them to get
26432 a majority of votes. When we deprecated the v2 directory protocol,
26433 we got rid of the only way that v3 authorities can hear from each
26434 other about other descriptors. Now authorities examine every v3
26435 vote for new descriptors, and fetch them from that authority. Bugfix
26437 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
26438 and a warning in or.h related to bandwidth_weight_rule_t that
26439 prevented clean compile on OS X. Fixes bug 1363; bugfix on
26441 - Fix a segfault on relays when DirReqStatistics is enabled
26442 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
26446 - Demote a confusing TLS warning that relay operators might get when
26447 someone tries to talk to their OrPort. It is neither the operator's
26448 fault nor can they do anything about it. Fixes bug 1364; bugfix
26452 Changes in version 0.2.2.11-alpha - 2010-04-15
26453 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
26454 libraries that was causing some relays to drop out of the consensus.
26457 - Directory mirrors were fetching relay descriptors only from v2
26458 directory authorities, rather than v3 authorities like they should.
26459 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26460 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26461 - Fix a parsing error that made every possible value of
26462 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
26463 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
26464 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
26465 about the option without breaking older ones.
26466 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26467 that claim to be earlier than 0.9.8m, but which have in reality
26468 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26469 behavior. Possible fix for some cases of bug 1346.
26472 - Experiment with a more aggressive approach to preventing clients
26473 from making one-hop exit streams. Exit relays who want to try it
26474 out can set "RefuseUnknownExits 1" in their torrc, and then look
26475 for "Attempt by %s to open a stream" log messages. Let us know
26477 - Add support for statically linking zlib by specifying
26478 --enable-static-zlib, to go with our support for statically linking
26479 openssl and libevent. Resolves bug 1358.
26482 - Fix a segfault that happens whenever a Tor client that is using
26483 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
26485 - When we cleaned up the contrib/tor-exit-notice.html file, we left
26486 out the first line. Fixes bug 1295.
26487 - When building the manpage from a tarball, we required asciidoc, but
26488 the asciidoc -> roff/html conversion was already done for the
26489 tarball. Make 'make' complain only when we need asciidoc (either
26490 because we're compiling directly from git, or because we altered
26491 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
26492 - When none of the directory authorities vote on any params, Tor
26493 segfaulted when trying to make the consensus from the votes. We
26494 didn't trigger the bug in practice, because authorities do include
26495 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
26498 - In the util/threads test, no longer free the test_mutex before all
26499 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26500 - The master thread could starve the worker threads quite badly on
26501 certain systems, causing them to run only partially in the allowed
26502 window. This resulted in test failures. Now the master thread sleeps
26503 occasionally for a few microseconds while the two worker-threads
26504 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26507 Changes in version 0.2.2.10-alpha - 2010-03-07
26508 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
26509 could prevent relays from guessing their IP address correctly. It also
26510 starts the groundwork for another client-side performance boost, since
26511 currently we're not making efficient use of relays that have both the
26512 Guard flag and the Exit flag.
26515 - Fix a regression from our patch for bug 1244 that caused relays
26516 to guess their IP address incorrectly if they didn't set Address
26517 in their torrc and/or their address fails to resolve. Bugfix on
26518 0.2.2.9-alpha; fixes bug 1269.
26520 o Major features (performance):
26521 - Directory authorities now compute consensus weightings that instruct
26522 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
26523 and no flag. Clients that use these weightings will distribute
26524 network load more evenly across these different relay types. The
26525 weightings are in the consensus so we can change them globally in
26526 the future. Extra thanks to "outofwords" for finding some nasty
26527 security bugs in the first implementation of this feature.
26529 o Minor features (performance):
26530 - Always perform router selections using weighted relay bandwidth,
26531 even if we don't need a high capacity circuit at the time. Non-fast
26532 circuits now only differ from fast ones in that they can use relays
26533 not marked with the Fast flag. This "feature" could turn out to
26534 be a horrible bug; we should investigate more before it goes into
26538 - Allow disabling building of the manpages. Skipping the manpage
26539 speeds up the build considerably.
26541 o Minor bugfixes (on 0.2.2.x):
26542 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
26543 Bugfix on 0.2.2.9-alpha.
26544 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
26545 config option. Bugfix on 0.2.2.7-alpha.
26546 - Ship the asciidoc-helper file in the tarball, so that people can
26547 build from source if they want to, and touching the .1.txt files
26548 doesn't break the build. Bugfix on 0.2.2.9-alpha.
26550 o Minor bugfixes (on 0.2.1.x or earlier):
26551 - Fix a dereference-then-NULL-check sequence when publishing
26552 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
26554 - Fix another dereference-then-NULL-check sequence. Bugfix on
26555 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
26556 - Make sure we treat potentially not NUL-terminated strings correctly.
26557 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
26559 o Code simplifications and refactoring:
26560 - Fix some urls in the exit notice file and make it XHTML1.1 strict
26561 compliant. Based on a patch from Christian Kujau.
26562 - Don't use sed in asciidoc-helper anymore.
26563 - Make the build process fail if asciidoc cannot be found and
26564 building with asciidoc isn't disabled.
26567 Changes in version 0.2.2.9-alpha - 2010-02-22
26568 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
26569 location of a directory authority, and cleans up a bunch of small bugs.
26571 o Directory authority changes:
26572 - Change IP address for dannenberg (v3 directory authority), and
26573 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
26574 service directory authority) from the list.
26577 - Make Tor work again on the latest OS X: when deciding whether to
26578 use strange flags to turn TLS renegotiation on, detect the OpenSSL
26579 version at run-time, not compile time. We need to do this because
26580 Apple doesn't update its dev-tools headers when it updates its
26581 libraries in a security patch.
26582 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
26583 that could happen on 32-bit platforms with 64-bit time_t. Also fix
26584 a memory leak when requesting a hidden service descriptor we've
26585 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
26587 - Authorities could be tricked into giving out the Exit flag to relays
26588 that didn't allow exiting to any ports. This bug could screw
26589 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
26590 1238. Bug discovered by Martin Kowalczyk.
26591 - When freeing a session key, zero it out completely. We only zeroed
26592 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
26593 patched by ekir. Fixes bug 1254.
26596 - Fix static compilation by listing the openssl libraries in the right
26597 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
26598 - Resume handling .exit hostnames in a special way: originally we
26599 stripped the .exit part and used the requested exit relay. In
26600 0.2.2.1-alpha we stopped treating them in any special way, meaning
26601 if you use a .exit address then Tor will pass it on to the exit
26602 relay. Now we reject the .exit stream outright, since that behavior
26603 might be more expected by the user. Found and diagnosed by Scott
26604 Bennett and Downie on or-talk.
26605 - Don't spam the controller with events when we have no file
26606 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
26607 for log messages was already solved from bug 748.)
26608 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
26610 - Make the DNSPort option work with libevent 2.x. Don't alter the
26611 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
26612 - Emit a GUARD DROPPED controller event for a case we missed.
26613 - Make more fields in the controller protocol case-insensitive, since
26614 control-spec.txt said they were.
26615 - Refactor resolve_my_address() to not use gethostbyname() anymore.
26616 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
26617 - Fix a spec conformance issue: the network-status-version token
26618 must be the first token in a v3 consensus or vote. Discovered by
26619 parakeep. Bugfix on 0.2.0.3-alpha.
26621 o Code simplifications and refactoring:
26622 - Generate our manpage and HTML documentation using Asciidoc. This
26623 change should make it easier to maintain the documentation, and
26624 produce nicer HTML.
26625 - Remove the --enable-iphone option. According to reports from Marco
26626 Bonetti, Tor builds fine without any special tweaking on recent
26627 iPhone SDK versions.
26628 - Removed some unnecessary files from the source distribution. The
26629 AUTHORS file has now been merged into the people page on the
26630 website. The roadmaps and design doc can now be found in the
26631 projects directory in svn.
26632 - Enabled various circuit build timeout constants to be controlled
26633 by consensus parameters. Also set better defaults for these
26634 parameters based on experimentation on broadband and simulated
26635 high latency links.
26638 - The 'EXTENDCIRCUIT' control port command can now be used with
26639 a circ id of 0 and no path. This feature will cause Tor to build
26640 a new 'fast' general purpose circuit using its own path selection
26642 - Added a BUILDTIMEOUT_SET controller event to describe changes
26643 to the circuit build timeout.
26644 - Future-proof the controller protocol a bit by ignoring keyword
26645 arguments we do not recognize.
26646 - Expand homedirs passed to tor-checkkey. This should silence a
26647 coverity complaint about passing a user-supplied string into
26648 open() without checking it.
26651 Changes in version 0.2.1.25 - 2010-03-16
26652 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
26653 prevent relays from guessing their IP address correctly. It also fixes
26654 several minor potential security bugs.
26657 - Fix a regression from our patch for bug 1244 that caused relays
26658 to guess their IP address incorrectly if they didn't set Address
26659 in their torrc and/or their address fails to resolve. Bugfix on
26660 0.2.1.23; fixes bug 1269.
26661 - When freeing a session key, zero it out completely. We only zeroed
26662 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
26663 patched by ekir. Fixes bug 1254.
26666 - Fix a dereference-then-NULL-check sequence when publishing
26667 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
26669 - Fix another dereference-then-NULL-check sequence. Bugfix on
26670 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
26671 - Make sure we treat potentially not NUL-terminated strings correctly.
26672 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
26676 Changes in version 0.2.1.24 - 2010-02-21
26677 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
26681 - Work correctly out-of-the-box with even more vendor-patched versions
26682 of OpenSSL. In particular, make it so Debian and OS X don't need
26683 customized patches to run/build.
26686 Changes in version 0.2.1.23 - 2010-02-13
26687 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
26688 again on the latest OS X, and updates the location of a directory
26691 o Major bugfixes (performance):
26692 - We were selecting our guards uniformly at random, and then weighting
26693 which of our guards we'd use uniformly at random. This imbalance
26694 meant that Tor clients were severely limited on throughput (and
26695 probably latency too) by the first hop in their circuit. Now we
26696 select guards weighted by currently advertised bandwidth. We also
26697 automatically discard guards picked using the old algorithm. Fixes
26698 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
26701 - Make Tor work again on the latest OS X: when deciding whether to
26702 use strange flags to turn TLS renegotiation on, detect the OpenSSL
26703 version at run-time, not compile time. We need to do this because
26704 Apple doesn't update its dev-tools headers when it updates its
26705 libraries in a security patch.
26706 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
26707 that could happen on 32-bit platforms with 64-bit time_t. Also fix
26708 a memory leak when requesting a hidden service descriptor we've
26709 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
26712 o Directory authority changes:
26713 - Change IP address for dannenberg (v3 directory authority), and
26714 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
26715 service directory authority) from the list.
26718 - Refactor resolve_my_address() to not use gethostbyname() anymore.
26719 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
26722 - Avoid a mad rush at the beginning of each month when each client
26723 rotates half of its guards. Instead we spread the rotation out
26724 throughout the month, but we still avoid leaving a precise timestamp
26725 in the state file about when we first picked the guard. Improves
26726 over the behavior introduced in 0.1.2.17.
26729 Changes in version 0.2.2.8-alpha - 2010-01-26
26730 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
26731 causing bridge relays to disappear. If you're running a bridge,
26735 - Fix a memory corruption bug on bridges that occurred during the
26736 inclusion of stats data in extra-info descriptors. Also fix the
26737 interface for geoip_get_bridge_stats* to prevent similar bugs in
26738 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
26739 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
26742 - Ignore OutboundBindAddress when connecting to localhost.
26743 Connections to localhost need to come _from_ localhost, or else
26744 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
26748 Changes in version 0.2.2.7-alpha - 2010-01-19
26749 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
26750 as laying the groundwork for further relay-side performance fixes. It
26751 also starts cleaning up client behavior with respect to the EntryNodes,
26752 ExitNodes, and StrictNodes config options.
26754 This release also rotates two directory authority keys, due to a
26755 security breach of some of the Torproject servers.
26757 o Directory authority changes:
26758 - Rotate keys (both v3 identity and relay identity) for moria1
26761 o Major features (performance):
26762 - We were selecting our guards uniformly at random, and then weighting
26763 which of our guards we'd use uniformly at random. This imbalance
26764 meant that Tor clients were severely limited on throughput (and
26765 probably latency too) by the first hop in their circuit. Now we
26766 select guards weighted by currently advertised bandwidth. We also
26767 automatically discard guards picked using the old algorithm. Fixes
26768 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
26769 - When choosing which cells to relay first, relays can now favor
26770 circuits that have been quiet recently, to provide lower latency
26771 for low-volume circuits. By default, relays enable or disable this
26772 feature based on a setting in the consensus. You can override
26773 this default by using the new "CircuitPriorityHalflife" config
26774 option. Design and code by Ian Goldberg, Can Tang, and Chris
26776 - Add separate per-conn write limiting to go with the per-conn read
26777 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
26778 but never per-conn write limits.
26779 - New consensus params "bwconnrate" and "bwconnburst" to let us
26780 rate-limit client connections as they enter the network. It's
26781 controlled in the consensus so we can turn it on and off for
26782 experiments. It's starting out off. Based on proposal 163.
26784 o Major features (relay selection options):
26785 - Switch to a StrictNodes config option, rather than the previous
26786 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
26787 "StrictExcludeNodes" option.
26788 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
26789 change during a config reload, mark and discard all our origin
26790 circuits. This fix should address edge cases where we change the
26791 config options and but then choose a circuit that we created before
26793 - If EntryNodes or ExitNodes are set, be more willing to use an
26794 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
26796 - Make EntryNodes config option much more aggressive even when
26797 StrictNodes is not set. Before it would prepend your requested
26798 entrynodes to your list of guard nodes, but feel free to use others
26799 after that. Now it chooses only from your EntryNodes if any of
26800 those are available, and only falls back to others if a) they're
26801 all down and b) StrictNodes is not set.
26802 - Now we refresh your entry guards from EntryNodes at each consensus
26803 fetch -- rather than just at startup and then they slowly rot as
26804 the network changes.
26807 - Stop bridge directory authorities from answering dbg-stability.txt
26808 directory queries, which would let people fetch a list of all
26809 bridge identities they track. Bugfix on 0.2.1.6-alpha.
26812 - Log a notice when we get a new control connection. Now it's easier
26813 for security-conscious users to recognize when a local application
26814 is knocking on their controller door. Suggested by bug 1196.
26815 - New config option "CircuitStreamTimeout" to override our internal
26816 timeout schedule for how many seconds until we detach a stream from
26817 a circuit and try a new circuit. If your network is particularly
26818 slow, you might want to set this to a number like 60.
26819 - New controller command "getinfo config-text". It returns the
26820 contents that Tor would write if you send it a SAVECONF command,
26821 so the controller can write the file to disk itself.
26822 - New options for SafeLogging to allow scrubbing only log messages
26823 generated while acting as a relay.
26824 - Ship the bridges spec file in the tarball too.
26825 - Avoid a mad rush at the beginning of each month when each client
26826 rotates half of its guards. Instead we spread the rotation out
26827 throughout the month, but we still avoid leaving a precise timestamp
26828 in the state file about when we first picked the guard. Improves
26829 over the behavior introduced in 0.1.2.17.
26831 o Minor bugfixes (compiling):
26832 - Fix compilation on OS X 10.3, which has a stub mlockall() but
26833 hides it. Bugfix on 0.2.2.6-alpha.
26834 - Fix compilation on Solaris by removing support for the
26835 DisableAllSwap config option. Solaris doesn't have an rlimit for
26836 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
26839 o Minor bugfixes (crashes):
26840 - Do not segfault when writing buffer stats when we haven't observed
26841 a single circuit to report about. Found by Fabian Lanze. Bugfix on
26843 - If we're in the pathological case where there's no exit bandwidth
26844 but there is non-exit bandwidth, or no guard bandwidth but there
26845 is non-guard bandwidth, don't crash during path selection. Bugfix
26847 - Fix an impossible-to-actually-trigger buffer overflow in relay
26848 descriptor generation. Bugfix on 0.1.0.15.
26850 o Minor bugfixes (privacy):
26851 - Fix an instance where a Tor directory mirror might accidentally
26852 log the IP address of a misbehaving Tor client. Bugfix on
26854 - Don't list Windows capabilities in relay descriptors. We never made
26855 use of them, and maybe it's a bad idea to publish them. Bugfix
26858 o Minor bugfixes (other):
26859 - Resolve an edge case in path weighting that could make us misweight
26860 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
26861 - Fix statistics on client numbers by country as seen by bridges that
26862 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
26863 intervals instead of variable 12-to-48-hour intervals.
26864 - After we free an internal connection structure, overwrite it
26865 with a different memory value than we use for overwriting a freed
26866 internal circuit structure. Should help with debugging. Suggested
26868 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
26871 o Removed features:
26872 - Remove the HSAuthorityRecordStats option that version 0 hidden
26873 service authorities could have used to track statistics of overall
26874 hidden service usage.
26877 Changes in version 0.2.1.22 - 2010-01-19
26878 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
26879 authorities -- it would tell you its whole history of bridge descriptors
26880 if you make the right directory request. This stable update also
26881 rotates two of the seven v3 directory authority keys and locations.
26883 o Directory authority changes:
26884 - Rotate keys (both v3 identity and relay identity) for moria1
26888 - Stop bridge directory authorities from answering dbg-stability.txt
26889 directory queries, which would let people fetch a list of all
26890 bridge identities they track. Bugfix on 0.2.1.6-alpha.
26893 Changes in version 0.2.1.21 - 2009-12-21
26894 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
26895 library. If you use Tor on Linux / Unix and you're getting SSL
26896 renegotiation errors, upgrading should help. We also recommend an
26897 upgrade if you're an exit relay.
26900 - Work around a security feature in OpenSSL 0.9.8l that prevents our
26901 handshake from working unless we explicitly tell OpenSSL that we
26902 are using SSL renegotiation safely. We are, of course, but OpenSSL
26903 0.9.8l won't work unless we say we are.
26904 - Avoid crashing if the client is trying to upload many bytes and the
26905 circuit gets torn down at the same time, or if the flip side
26906 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
26909 - Do not refuse to learn about authority certs and v2 networkstatus
26910 documents that are older than the latest consensus. This bug might
26911 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
26912 Spotted and fixed by xmux.
26913 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
26914 trigger platform-specific option misparsing case found by Coverity
26916 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
26917 trigger assert. Fixes bug 1173.
26920 Changes in version 0.2.2.6-alpha - 2009-11-19
26921 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
26922 support for the new lower-footprint "microdescriptor" directory design,
26923 future-proofing our consensus format against new hash functions or
26924 other changes, and an Android port. It also makes Tor compatible with
26925 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
26928 - Directory authorities can now create, vote on, and serve multiple
26929 parallel formats of directory data as part of their voting process.
26930 Partially implements Proposal 162: "Publish the consensus in
26932 - Directory authorities can now agree on and publish small summaries
26933 of router information that clients can use in place of regular
26934 server descriptors. This transition will eventually allow clients
26935 to use far less bandwidth for downloading information about the
26936 network. Begins the implementation of Proposal 158: "Clients
26937 download consensus + microdescriptors".
26938 - The directory voting system is now extensible to use multiple hash
26939 algorithms for signatures and resource selection. Newer formats
26940 are signed with SHA256, with a possibility for moving to a better
26941 hash algorithm in the future.
26942 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
26943 current and future memory pages via mlockall(). On supported
26944 platforms (modern Linux and probably BSD but not Windows or OS X),
26945 this should effectively disable any and all attempts to page out
26946 memory. This option requires that you start your Tor as root --
26947 if you use DisableAllSwap, please consider using the User option
26948 to properly reduce the privileges of your Tor.
26949 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
26950 to help Tor build correctly for Android phones.
26953 - Work around a security feature in OpenSSL 0.9.8l that prevents our
26954 handshake from working unless we explicitly tell OpenSSL that we
26955 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
26956 won't work unless we say we are.
26959 - Fix a crash bug when trying to initialize the evdns module in
26960 Libevent 2. Bugfix on 0.2.1.16-rc.
26961 - Stop logging at severity 'warn' when some other Tor client tries
26962 to establish a circuit with us using weak DH keys. It's a protocol
26963 violation, but that doesn't mean ordinary users need to hear about
26964 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
26965 - Do not refuse to learn about authority certs and v2 networkstatus
26966 documents that are older than the latest consensus. This bug might
26967 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
26968 Spotted and fixed by xmux.
26969 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
26970 - If all authorities restart at once right before a consensus vote,
26971 nobody will vote about "Running", and clients will get a consensus
26972 with no usable relays. Instead, authorities refuse to build a
26973 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
26974 - If your relay can't keep up with the number of incoming create
26975 cells, it would log one warning per failure into your logs. Limit
26976 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
26977 - Bridges now use "reject *:*" as their default exit policy. Bugfix
26978 on 0.2.0.3-alpha; fixes bug 1113.
26979 - Fix a memory leak on directory authorities during voting that was
26980 introduced in 0.2.2.1-alpha. Found via valgrind.
26983 Changes in version 0.2.1.20 - 2009-10-15
26984 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
26985 services at once, prepares for more performance improvements, and
26986 fixes a bunch of smaller bugs.
26988 The Windows and OS X bundles also include a more recent Vidalia,
26989 and switch from Privoxy to Polipo.
26991 The OS X installers are now drag and drop. It's best to un-install
26992 Tor/Vidalia and then install this new bundle, rather than upgrade. If
26993 you want to upgrade, you'll need to update the paths for Tor and Polipo
26994 in the Vidalia Settings window.
26997 - Send circuit or stream sendme cells when our window has decreased
26998 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
26999 by Karsten when testing the "reduce circuit window" performance
27000 patch. Bugfix on the 54th commit on Tor -- from July 2002,
27001 before the release of Tor 0.0.0. This is the new winner of the
27003 - Fix a remotely triggerable memory leak when a consensus document
27004 contains more than one signature from the same voter. Bugfix on
27006 - Avoid segfault in rare cases when finishing an introduction circuit
27007 as a client and finding out that we don't have an introduction key
27008 for it. Fixes bug 1073. Reported by Aaron Swartz.
27011 - Tor now reads the "circwindow" parameter out of the consensus,
27012 and uses that value for its circuit package window rather than the
27013 default of 1000 cells. Begins the implementation of proposal 168.
27015 o New directory authorities:
27016 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
27018 - Move moria1 and tonga to alternate IP addresses.
27021 - Fix a signed/unsigned compile warning in 0.2.1.19.
27022 - Fix possible segmentation fault on directory authorities. Bugfix on
27024 - Fix an extremely rare infinite recursion bug that could occur if
27025 we tried to log a message after shutting down the log subsystem.
27026 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
27027 - Fix an obscure bug where hidden services on 64-bit big-endian
27028 systems might mis-read the timestamp in v3 introduce cells, and
27029 refuse to connect back to the client. Discovered by "rotor".
27030 Bugfix on 0.2.1.6-alpha.
27031 - We were triggering a CLOCK_SKEW controller status event whenever
27032 we connect via the v2 connection protocol to any relay that has
27033 a wrong clock. Instead, we should only inform the controller when
27034 it's a trusted authority that claims our clock is wrong. Bugfix
27035 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
27036 - We were telling the controller about CHECKING_REACHABILITY and
27037 REACHABILITY_FAILED status events whenever we launch a testing
27038 circuit or notice that one has failed. Instead, only tell the
27039 controller when we want to inform the user of overall success or
27040 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
27042 - Don't warn when we're using a circuit that ends with a node
27043 excluded in ExcludeExitNodes, but the circuit is not used to access
27044 the outside world. This should help fix bug 1090. Bugfix on
27046 - Work around a small memory leak in some versions of OpenSSL that
27047 stopped the memory used by the hostname TLS extension from being
27051 - Add a "getinfo status/accepted-server-descriptor" controller
27052 command, which is the recommended way for controllers to learn
27053 whether our server descriptor has been successfully received by at
27054 least on directory authority. Un-recommend good-server-descriptor
27055 getinfo and status events until we have a better design for them.
27058 Changes in version 0.2.2.5-alpha - 2009-10-11
27059 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
27062 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
27064 o Directory authorities:
27065 - Temporarily (just for this release) move dizum to an alternate
27069 Changes in version 0.2.2.4-alpha - 2009-10-10
27070 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
27071 introduces a new unit test framework, shifts directry authority
27072 addresses around to reduce the impact from recent blocking events,
27073 and fixes a few smaller bugs.
27076 - Fix several more asserts in the circuit_build_times code, for
27077 example one that causes Tor to fail to start once we have
27078 accumulated 5000 build times in the state file. Bugfixes on
27079 0.2.2.2-alpha; fixes bug 1108.
27081 o New directory authorities:
27082 - Move moria1 and Tonga to alternate IP addresses.
27085 - Log SSL state transitions at debug level during handshake, and
27086 include SSL states in error messages. This may help debug future
27087 SSL handshake issues.
27088 - Add a new "Handshake" log domain for activities that happen
27089 during the TLS handshake.
27090 - Revert to the "June 3 2009" ip-to-country file. The September one
27091 seems to have removed most US IP addresses.
27092 - Directory authorities now reject Tor relays with versions less than
27093 0.1.2.14. This step cuts out four relays from the current network,
27094 none of which are very big.
27097 - Fix a couple of smaller issues with gathering statistics. Bugfixes
27099 - Fix two memory leaks in the error case of
27100 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
27101 - Don't count one-hop circuits when we're estimating how long it
27102 takes circuits to build on average. Otherwise we'll set our circuit
27103 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
27104 - Directory authorities no longer change their opinion of, or vote on,
27105 whether a router is Running, unless they have themselves been
27106 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
27109 o Code simplifications and refactoring:
27110 - Revise our unit tests to use the "tinytest" framework, so we
27111 can run tests in their own processes, have smarter setup/teardown
27112 code, and so on. The unit test code has moved to its own
27113 subdirectory, and has been split into multiple modules.
27116 Changes in version 0.2.2.3-alpha - 2009-09-23
27117 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
27120 - Fix an overzealous assert in our new circuit build timeout code.
27121 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
27124 - If the networkstatus consensus tells us that we should use a
27125 negative circuit package window, ignore it. Otherwise we'll
27126 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
27129 Changes in version 0.2.2.2-alpha - 2009-09-21
27130 Tor 0.2.2.2-alpha introduces our latest performance improvement for
27131 clients: Tor tracks the average time it takes to build a circuit, and
27132 avoids using circuits that take too long to build. For fast connections,
27133 this feature can cut your expected latency in half. For slow or flaky
27134 connections, it could ruin your Tor experience. Let us know if it does!
27137 - Tor now tracks how long it takes to build client-side circuits
27138 over time, and adapts its timeout to local network performance.
27139 Since a circuit that takes a long time to build will also provide
27140 bad performance, we get significant latency improvements by
27141 discarding the slowest 20% of circuits. Specifically, Tor creates
27142 circuits more aggressively than usual until it has enough data
27143 points for a good timeout estimate. Implements proposal 151.
27144 We are especially looking for reports (good and bad) from users with
27145 both EDGE and broadband connections that can move from broadband
27146 to EDGE and find out if the build-time data in the .tor/state gets
27147 reset without loss of Tor usability. You should also see a notice
27148 log message telling you that Tor has reset its timeout.
27149 - Directory authorities can now vote on arbitrary integer values as
27150 part of the consensus process. This is designed to help set
27151 network-wide parameters. Implements proposal 167.
27152 - Tor now reads the "circwindow" parameter out of the consensus,
27153 and uses that value for its circuit package window rather than the
27154 default of 1000 cells. Begins the implementation of proposal 168.
27157 - Fix a remotely triggerable memory leak when a consensus document
27158 contains more than one signature from the same voter. Bugfix on
27162 - Fix an extremely rare infinite recursion bug that could occur if
27163 we tried to log a message after shutting down the log subsystem.
27164 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
27165 - Fix parsing for memory or time units given without a space between
27166 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
27167 - A networkstatus vote must contain exactly one signature. Spec
27168 conformance issue. Bugfix on 0.2.0.3-alpha.
27169 - Fix an obscure bug where hidden services on 64-bit big-endian
27170 systems might mis-read the timestamp in v3 introduce cells, and
27171 refuse to connect back to the client. Discovered by "rotor".
27172 Bugfix on 0.2.1.6-alpha.
27173 - We were triggering a CLOCK_SKEW controller status event whenever
27174 we connect via the v2 connection protocol to any relay that has
27175 a wrong clock. Instead, we should only inform the controller when
27176 it's a trusted authority that claims our clock is wrong. Bugfix
27177 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
27178 - We were telling the controller about CHECKING_REACHABILITY and
27179 REACHABILITY_FAILED status events whenever we launch a testing
27180 circuit or notice that one has failed. Instead, only tell the
27181 controller when we want to inform the user of overall success or
27182 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
27184 - Don't warn when we're using a circuit that ends with a node
27185 excluded in ExcludeExitNodes, but the circuit is not used to access
27186 the outside world. This should help fix bug 1090, but more problems
27187 remain. Bugfix on 0.2.1.6-alpha.
27188 - Work around a small memory leak in some versions of OpenSSL that
27189 stopped the memory used by the hostname TLS extension from being
27191 - Make our 'torify' script more portable; if we have only one of
27192 'torsocks' or 'tsocks' installed, don't complain to the user;
27193 and explain our warning about tsocks better.
27196 - Add a "getinfo status/accepted-server-descriptor" controller
27197 command, which is the recommended way for controllers to learn
27198 whether our server descriptor has been successfully received by at
27199 least on directory authority. Un-recommend good-server-descriptor
27200 getinfo and status events until we have a better design for them.
27201 - Update to the "September 4 2009" ip-to-country file.
27204 Changes in version 0.2.2.1-alpha - 2009-08-26
27205 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
27206 Tor clients to bootstrap on networks where only port 80 is reachable,
27207 makes it more straightforward to support hardware crypto accelerators,
27208 and starts the groundwork for gathering stats safely at relays.
27211 - Start the process of disabling ".exit" address notation, since it
27212 can be used for a variety of esoteric application-level attacks
27213 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
27216 o New directory authorities:
27217 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
27221 - New AccelName and AccelDir options add support for dynamic OpenSSL
27222 hardware crypto acceleration engines.
27223 - Tor now supports tunneling all of its outgoing connections over
27224 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
27225 configuration options. Code by Christopher Davis.
27228 - Send circuit or stream sendme cells when our window has decreased
27229 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
27230 by Karsten when testing the "reduce circuit window" performance
27231 patch. Bugfix on the 54th commit on Tor -- from July 2002,
27232 before the release of Tor 0.0.0. This is the new winner of the
27235 o New options for gathering stats safely:
27236 - Directory mirrors that set "DirReqStatistics 1" write statistics
27237 about directory requests to disk every 24 hours. As compared to the
27238 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
27239 1) stats are written to disk exactly every 24 hours; 2) estimated
27240 shares of v2 and v3 requests are determined as mean values, not at
27241 the end of a measurement period; 3) unresolved requests are listed
27242 with country code '??'; 4) directories also measure download times.
27243 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
27244 number of exit streams and transferred bytes per port to disk every
27246 - Relays that set "CellStatistics 1" write statistics on how long
27247 cells spend in their circuit queues to disk every 24 hours.
27248 - Entry nodes that set "EntryStatistics 1" write statistics on the
27249 rough number and origins of connecting clients to disk every 24
27251 - Relays that write any of the above statistics to disk and set
27252 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
27253 their extra-info documents.
27256 - New --digests command-line switch to output the digests of the
27257 source files Tor was built with.
27258 - The "torify" script now uses torsocks where available.
27259 - The memarea code now uses a sentinel value at the end of each area
27260 to make sure nothing writes beyond the end of an area. This might
27261 help debug some conceivable causes of bug 930.
27262 - Time and memory units in the configuration file can now be set to
27263 fractional units. For example, "2.5 GB" is now a valid value for
27265 - Certain Tor clients (such as those behind check.torproject.org) may
27266 want to fetch the consensus in an extra early manner. To enable this
27267 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
27268 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
27269 as only certain clients who must have this information sooner should
27271 - Instead of adding the svn revision to the Tor version string, report
27272 the git commit (when we're building from a git checkout).
27275 - If any of the v3 certs we download are unparseable, we should
27276 actually notice the failure so we don't retry indefinitely. Bugfix
27277 on 0.2.0.x; reported by "rotator".
27278 - If the cached cert file is unparseable, warn but don't exit.
27279 - Fix possible segmentation fault on directory authorities. Bugfix on
27281 - When Tor fails to parse a descriptor of any kind, dump it to disk.
27282 Might help diagnosing bug 1051.
27284 o Deprecated and removed features:
27285 - The controller no longer accepts the old obsolete "addr-mappings/"
27286 or "unregistered-servers-" GETINFO values.
27287 - Hidden services no longer publish version 0 descriptors, and clients
27288 do not request or use version 0 descriptors. However, the old hidden
27289 service authorities still accept and serve version 0 descriptors
27290 when contacted by older hidden services/clients.
27291 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
27292 always on; using them is necessary for correct forward-compatible
27294 - Remove support for .noconnect style addresses. Nobody was using
27295 them, and they provided another avenue for detecting Tor users
27296 via application-level web tricks.
27298 o Packaging changes:
27299 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
27300 installer bundles. See
27301 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
27302 for details of what's new in Vidalia 0.2.3.
27303 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
27304 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
27305 configuration file, rather than the old Privoxy.
27306 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
27307 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
27308 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
27309 better compatibility with OS X 10.6, aka Snow Leopard.
27310 - OS X Vidalia Bundle: The multi-package installer is now replaced
27311 by a simple drag and drop to the /Applications folder. This change
27312 occurred with the upgrade to Vidalia 0.2.3.
27315 Changes in version 0.2.1.19 - 2009-07-28
27316 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
27317 services on Tor 0.2.1.3-alpha through 0.2.1.18.
27320 - Make accessing hidden services on 0.2.1.x work right again.
27321 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
27322 part of patch provided by "optimist".
27325 - When a relay/bridge is writing out its identity key fingerprint to
27326 the "fingerprint" file and to its logs, write it without spaces. Now
27327 it will look like the fingerprints in our bridges documentation,
27328 and confuse fewer users.
27331 - Relays no longer publish a new server descriptor if they change
27332 their MaxAdvertisedBandwidth config option but it doesn't end up
27333 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
27334 fixes bug 1026. Patch from Sebastian.
27335 - Avoid leaking memory every time we get a create cell but we have
27336 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
27337 fixes bug 1034. Reported by BarkerJr.
27340 Changes in version 0.2.1.18 - 2009-07-24
27341 Tor 0.2.1.18 lays the foundations for performance improvements,
27342 adds status events to help users diagnose bootstrap problems, adds
27343 optional authentication/authorization for hidden services, fixes a
27344 variety of potential anonymity problems, and includes a huge pile of
27345 other features and bug fixes.
27348 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
27351 Changes in version 0.2.1.17-rc - 2009-07-07
27352 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
27353 candidate for the 0.2.1.x series. It lays the groundwork for further
27354 client performance improvements, and also fixes a big bug with directory
27355 authorities that were causing them to assign Guard and Stable flags
27358 The Windows bundles also finally include the geoip database that we
27359 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
27360 should actually install Torbutton rather than giving you a cryptic
27361 failure message (oops).
27364 - Clients now use the bandwidth values in the consensus, rather than
27365 the bandwidth values in each relay descriptor. This approach opens
27366 the door to more accurate bandwidth estimates once the directory
27367 authorities start doing active measurements. Implements more of
27371 - When Tor clients restart after 1-5 days, they discard all their
27372 cached descriptors as too old, but they still use the cached
27373 consensus document. This approach is good for robustness, but
27374 bad for performance: since they don't know any bandwidths, they
27375 end up choosing at random rather than weighting their choice by
27376 speed. Fixed by the above feature of putting bandwidths in the
27377 consensus. Bugfix on 0.2.0.x.
27378 - Directory authorities were neglecting to mark relays down in their
27379 internal histories if the relays fall off the routerlist without
27380 ever being found unreachable. So there were relays in the histories
27381 that haven't been seen for eight months, and are listed as being
27382 up for eight months. This wreaked havoc on the "median wfu"
27383 and "median mtbf" calculations, in turn making Guard and Stable
27384 flags very wrong, hurting network performance. Fixes bugs 696 and
27385 969. Bugfix on 0.2.0.6-alpha.
27388 - Serve the DirPortFrontPage page even when we have been approaching
27389 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
27390 - The control port would close the connection before flushing long
27391 replies, such as the network consensus, if a QUIT command was issued
27392 before the reply had completed. Now, the control port flushes all
27393 pending replies before closing the connection. Also fixed a spurious
27394 warning when a QUIT command is issued after a malformed or rejected
27395 AUTHENTICATE command, but before the connection was closed. Patch
27396 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
27397 - When we can't find an intro key for a v2 hidden service descriptor,
27398 fall back to the v0 hidden service descriptor and log a bug message.
27399 Workaround for bug 1024.
27400 - Fix a log message that did not respect the SafeLogging option.
27404 - If we're a relay and we change our IP address, be more verbose
27405 about the reason that made us change. Should help track down
27406 further bugs for relays on dynamic IP addresses.
27409 Changes in version 0.2.0.35 - 2009-06-24
27411 - Avoid crashing in the presence of certain malformed descriptors.
27412 Found by lark, and by automated fuzzing.
27413 - Fix an edge case where a malicious exit relay could convince a
27414 controller that the client's DNS question resolves to an internal IP
27415 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
27418 - Finally fix the bug where dynamic-IP relays disappear when their
27419 IP address changes: directory mirrors were mistakenly telling
27420 them their old address if they asked via begin_dir, so they
27421 never got an accurate answer about their new address, so they
27422 just vanished after a day. For belt-and-suspenders, relays that
27423 don't set Address in their config now avoid using begin_dir for
27424 all direct connections. Should fix bugs 827, 883, and 900.
27425 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
27426 that would occur on some exit nodes when DNS failures and timeouts
27427 occurred in certain patterns. Fix for bug 957.
27430 - When starting with a cache over a few days old, do not leak
27431 memory for the obsolete router descriptors in it. Bugfix on
27432 0.2.0.33; fixes bug 672.
27433 - Hidden service clients didn't use a cached service descriptor that
27434 was older than 15 minutes, but wouldn't fetch a new one either,
27435 because there was already one in the cache. Now, fetch a v2
27436 descriptor unless the same descriptor was added to the cache within
27437 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
27440 Changes in version 0.2.1.16-rc - 2009-06-20
27441 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
27442 a bunch of minor bugs.
27445 - Fix an edge case where a malicious exit relay could convince a
27446 controller that the client's DNS question resolves to an internal IP
27447 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
27449 o Major performance improvements (on 0.2.0.x):
27450 - Disable and refactor some debugging checks that forced a linear scan
27451 over the whole server-side DNS cache. These accounted for over 50%
27452 of CPU time on a relatively busy exit node's gprof profile. Found
27454 - Disable some debugging checks that appeared in exit node profile
27458 - Update to the "June 3 2009" ip-to-country file.
27459 - Do not have tor-resolve automatically refuse all .onion addresses;
27460 if AutomapHostsOnResolve is set in your torrc, this will work fine.
27462 o Minor bugfixes (on 0.2.0.x):
27463 - Log correct error messages for DNS-related network errors on
27465 - Fix a race condition that could cause crashes or memory corruption
27466 when running as a server with a controller listening for log
27468 - Avoid crashing when we have a policy specified in a DirPolicy or
27469 SocksPolicy or ReachableAddresses option with ports set on it,
27470 and we re-load the policy. May fix bug 996.
27471 - Hidden service clients didn't use a cached service descriptor that
27472 was older than 15 minutes, but wouldn't fetch a new one either,
27473 because there was already one in the cache. Now, fetch a v2
27474 descriptor unless the same descriptor was added to the cache within
27475 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
27477 o Minor bugfixes (on 0.2.1.x):
27478 - Don't warn users about low port and hibernation mix when they
27479 provide a *ListenAddress directive to fix that. Bugfix on
27481 - When switching back and forth between bridge mode, do not start
27482 gathering GeoIP data until two hours have passed.
27483 - Do not complain that the user has requested an excluded node as
27484 an exit when the node is not really an exit. This could happen
27485 because the circuit was for testing, or an introduction point.
27489 Changes in version 0.2.1.15-rc - 2009-05-25
27490 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
27491 series. It fixes a major bug on fast exit relays, as well as a variety
27492 of more minor bugs.
27494 o Major bugfixes (on 0.2.0.x):
27495 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
27496 that would occur on some exit nodes when DNS failures and timeouts
27497 occurred in certain patterns. Fix for bug 957.
27499 o Minor bugfixes (on 0.2.0.x):
27500 - Actually return -1 in the error case for read_bandwidth_usage().
27501 Harmless bug, since we currently don't care about the return value
27502 anywhere. Bugfix on 0.2.0.9-alpha.
27503 - Provide a more useful log message if bug 977 (related to buffer
27504 freelists) ever reappears, and do not crash right away.
27505 - Fix an assertion failure on 64-bit platforms when we allocated
27506 memory right up to the end of a memarea, then realigned the memory
27507 one step beyond the end. Fixes a possible cause of bug 930.
27508 - Protect the count of open sockets with a mutex, so we can't
27509 corrupt it when two threads are closing or opening sockets at once.
27510 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
27511 - Don't allow a bridge to publish its router descriptor to a
27512 non-bridge directory authority. Fixes part of bug 932.
27513 - When we change to or from being a bridge, reset our counts of
27514 client usage by country. Fixes bug 932.
27515 - Fix a bug that made stream bandwidth get misreported to the
27517 - Stop using malloc_usable_size() to use more area than we had
27518 actually allocated: it was safe, but made valgrind really unhappy.
27519 - Fix a memory leak when v3 directory authorities load their keys
27520 and cert from disk. Bugfix on 0.2.0.1-alpha.
27522 o Minor bugfixes (on 0.2.1.x):
27523 - Fix use of freed memory when deciding to mark a non-addable
27524 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
27527 Changes in version 0.2.1.14-rc - 2009-04-12
27528 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
27529 series. It begins fixing some major performance problems, and also
27530 finally addresses the bug that was causing relays on dynamic IP
27531 addresses to fall out of the directory.
27534 - Clients replace entry guards that were chosen more than a few months
27535 ago. This change should significantly improve client performance,
27536 especially once more people upgrade, since relays that have been
27537 a guard for a long time are currently overloaded.
27539 o Major bugfixes (on 0.2.0):
27540 - Finally fix the bug where dynamic-IP relays disappear when their
27541 IP address changes: directory mirrors were mistakenly telling
27542 them their old address if they asked via begin_dir, so they
27543 never got an accurate answer about their new address, so they
27544 just vanished after a day. For belt-and-suspenders, relays that
27545 don't set Address in their config now avoid using begin_dir for
27546 all direct connections. Should fix bugs 827, 883, and 900.
27547 - Relays were falling out of the networkstatus consensus for
27548 part of a day if they changed their local config but the
27549 authorities discarded their new descriptor as "not sufficiently
27550 different". Now directory authorities accept a descriptor as changed
27551 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
27552 patch by Sebastian.
27553 - Avoid crashing in the presence of certain malformed descriptors.
27554 Found by lark, and by automated fuzzing.
27557 - When generating circuit events with verbose nicknames for
27558 controllers, try harder to look up nicknames for routers on a
27559 circuit. (Previously, we would look in the router descriptors we had
27560 for nicknames, but not in the consensus.) Partial fix for bug 941.
27561 - If the bridge config line doesn't specify a port, assume 443.
27562 This makes bridge lines a bit smaller and easier for users to
27564 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
27565 bytes (aka 20KB/s), to match our documentation. Also update
27566 directory authorities so they always assign the Fast flag to relays
27567 with 20KB/s of capacity. Now people running relays won't suddenly
27568 find themselves not seeing any use, if the network gets faster
27570 - Update to the "April 3 2009" ip-to-country file.
27573 - Avoid trying to print raw memory to the logs when we decide to
27574 give up on downloading a given relay descriptor. Bugfix on
27576 - In tor-resolve, when the Tor client to use is specified by
27577 <hostname>:<port>, actually use the specified port rather than
27578 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
27579 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
27580 - When starting with a cache over a few days old, do not leak
27581 memory for the obsolete router descriptors in it. Bugfix on
27583 - Avoid double-free on list of successfully uploaded hidden
27584 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
27585 - Change memarea_strndup() implementation to work even when
27586 duplicating a string at the end of a page. This bug was
27587 harmless for now, but could have meant crashes later. Fix by
27588 lark. Bugfix on 0.2.1.1-alpha.
27589 - Limit uploaded directory documents to be 16M rather than 500K.
27590 The directory authorities were refusing v3 consensus votes from
27591 other authorities, since the votes are now 504K. Fixes bug 959;
27592 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
27593 - Directory authorities should never send a 503 "busy" response to
27594 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
27598 Changes in version 0.2.1.13-alpha - 2009-03-09
27599 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
27600 cleanups. We're finally getting close to a release candidate.
27603 - Correctly update the list of which countries we exclude as
27604 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
27605 lark. Bugfix on 0.2.1.6-alpha.
27607 o Minor bugfixes (on 0.2.0.x and earlier):
27608 - Automatically detect MacOSX versions earlier than 10.4.0, and
27609 disable kqueue from inside Tor when running with these versions.
27610 We previously did this from the startup script, but that was no
27611 help to people who didn't use the startup script. Resolves bug 863.
27612 - When we had picked an exit node for a connection, but marked it as
27613 "optional", and it turned out we had no onion key for the exit,
27614 stop wanting that exit and try again. This situation may not
27615 be possible now, but will probably become feasible with proposal
27616 158. Spotted by rovv. Fixes another case of bug 752.
27617 - Clients no longer cache certificates for authorities they do not
27618 recognize. Bugfix on 0.2.0.9-alpha.
27619 - When we can't transmit a DNS request due to a network error, retry
27620 it after a while, and eventually transmit a failing response to
27621 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
27622 - If the controller claimed responsibility for a stream, but that
27623 stream never finished making its connection, it would live
27624 forever in circuit_wait state. Now we close it after SocksTimeout
27625 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
27626 - Drop begin cells to a hidden service if they come from the middle
27627 of a circuit. Patch from lark.
27628 - When we erroneously receive two EXTEND cells for the same circuit
27629 ID on the same connection, drop the second. Patch from lark.
27630 - Fix a crash that occurs on exit nodes when a nameserver request
27631 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
27632 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
27634 - Do not assume that a stack-allocated character array will be
27635 64-bit aligned on platforms that demand that uint64_t access is
27636 aligned. Possible fix for bug 604.
27637 - Parse dates and IPv4 addresses in a locale- and libc-independent
27638 manner, to avoid platform-dependent behavior on malformed input.
27639 - Build correctly when configured to build outside the main source
27640 path. Patch from Michael Gold.
27641 - We were already rejecting relay begin cells with destination port
27642 of 0. Now also reject extend cells with destination port or address
27643 of 0. Suggested by lark.
27645 o Minor bugfixes (on 0.2.1.x):
27646 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
27647 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
27648 - If we're an exit node, scrub the IP address to which we are exiting
27649 in the logs. Bugfix on 0.2.1.8-alpha.
27652 - On Linux, use the prctl call to re-enable core dumps when the user
27654 - New controller event NEWCONSENSUS that lists the networkstatus
27655 lines for every recommended relay. Now controllers like Torflow
27656 can keep up-to-date on which relays they should be using.
27657 - Update to the "February 26 2009" ip-to-country file.
27660 Changes in version 0.2.0.34 - 2009-02-08
27661 Tor 0.2.0.34 features several more security-related fixes. You should
27662 upgrade, especially if you run an exit relay (remote crash) or a
27663 directory authority (remote infinite loop), or you're on an older
27664 (pre-XP) or not-recently-patched Windows (remote exploit).
27666 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
27667 have many known flaws, and nobody should be using them. You should
27668 upgrade. If you're using a Linux or BSD and its packages are obsolete,
27669 stop using those packages and upgrade anyway.
27672 - Fix an infinite-loop bug on handling corrupt votes under certain
27673 circumstances. Bugfix on 0.2.0.8-alpha.
27674 - Fix a temporary DoS vulnerability that could be performed by
27675 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
27676 - Avoid a potential crash on exit nodes when processing malformed
27677 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
27678 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
27679 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
27682 - Fix compilation on systems where time_t is a 64-bit integer.
27683 Patch from Matthias Drochner.
27684 - Don't consider expiring already-closed client connections. Fixes
27685 bug 893. Bugfix on 0.0.2pre20.
27688 Changes in version 0.2.1.12-alpha - 2009-02-08
27689 Tor 0.2.1.12-alpha features several more security-related fixes. You
27690 should upgrade, especially if you run an exit relay (remote crash) or
27691 a directory authority (remote infinite loop), or you're on an older
27692 (pre-XP) or not-recently-patched Windows (remote exploit). It also
27693 includes a big pile of minor bugfixes and cleanups.
27696 - Fix an infinite-loop bug on handling corrupt votes under certain
27697 circumstances. Bugfix on 0.2.0.8-alpha.
27698 - Fix a temporary DoS vulnerability that could be performed by
27699 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
27700 - Avoid a potential crash on exit nodes when processing malformed
27701 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
27704 - Let controllers actually ask for the "clients_seen" event for
27705 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
27706 reported by Matt Edman.
27707 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
27709 - Fix a bug in address parsing that was preventing bridges or hidden
27710 service targets from being at IPv6 addresses.
27711 - Solve a bug that kept hardware crypto acceleration from getting
27712 enabled when accounting was turned on. Fixes bug 907. Bugfix on
27714 - Remove a bash-ism from configure.in to build properly on non-Linux
27715 platforms. Bugfix on 0.2.1.1-alpha.
27716 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
27717 headers. Bugfix on 0.2.0.10-alpha.
27718 - Don't consider expiring already-closed client connections. Fixes
27719 bug 893. Bugfix on 0.0.2pre20.
27720 - Fix another interesting corner-case of bug 891 spotted by rovv:
27721 Previously, if two hosts had different amounts of clock drift, and
27722 one of them created a new connection with just the wrong timing,
27723 the other might decide to deprecate the new connection erroneously.
27724 Bugfix on 0.1.1.13-alpha.
27725 - Resolve a very rare crash bug that could occur when the user forced
27726 a nameserver reconfiguration during the middle of a nameserver
27727 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
27728 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
27729 Bugfix on 0.2.1.7-alpha.
27730 - If we're using bridges and our network goes away, be more willing
27731 to forgive our bridges and try again when we get an application
27732 request. Bugfix on 0.2.0.x.
27735 - Support platforms where time_t is 64 bits long. (Congratulations,
27736 NetBSD!) Patch from Matthias Drochner.
27737 - Add a 'getinfo status/clients-seen' controller command, in case
27738 controllers want to hear clients_seen events but connect late.
27741 - Disable GCC's strict alias optimization by default, to avoid the
27742 likelihood of its introducing subtle bugs whenever our code violates
27743 the letter of C99's alias rules.
27746 Changes in version 0.2.0.33 - 2009-01-21
27747 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
27748 useful to users. It also finally fixes a bug where a relay or client
27749 that's been off for many days would take a long time to bootstrap.
27751 This update also fixes an important security-related bug reported by
27752 Ilja van Sprundel. You should upgrade. (We'll send out more details
27753 about the bug once people have had some time to upgrade.)
27756 - Fix a heap-corruption bug that may be remotely triggerable on
27757 some platforms. Reported by Ilja van Sprundel.
27760 - When a stream at an exit relay is in state "resolving" or
27761 "connecting" and it receives an "end" relay cell, the exit relay
27762 would silently ignore the end cell and not close the stream. If
27763 the client never closes the circuit, then the exit relay never
27764 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
27765 reported by "wood".
27766 - When sending CREATED cells back for a given circuit, use a 64-bit
27767 connection ID to find the right connection, rather than an addr:port
27768 combination. Now that we can have multiple OR connections between
27769 the same ORs, it is no longer possible to use addr:port to uniquely
27770 identify a connection.
27771 - Bridge relays that had DirPort set to 0 would stop fetching
27772 descriptors shortly after startup, and then briefly resume
27773 after a new bandwidth test and/or after publishing a new bridge
27774 descriptor. Bridge users that try to bootstrap from them would
27775 get a recent networkstatus but would get descriptors from up to
27776 18 hours earlier, meaning most of the descriptors were obsolete
27777 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
27778 - Prevent bridge relays from serving their 'extrainfo' document
27779 to anybody who asks, now that extrainfo docs include potentially
27780 sensitive aggregated client geoip summaries. Bugfix on
27782 - If the cached networkstatus consensus is more than five days old,
27783 discard it rather than trying to use it. In theory it could be
27784 useful because it lists alternate directory mirrors, but in practice
27785 it just means we spend many minutes trying directory mirrors that
27786 are long gone from the network. Also discard router descriptors as
27787 we load them if they are more than five days old, since the onion
27788 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
27791 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
27792 could make gcc generate non-functional binary search code. Bugfix
27794 - Build correctly on platforms without socklen_t.
27795 - Compile without warnings on solaris.
27796 - Avoid potential crash on internal error during signature collection.
27797 Fixes bug 864. Patch from rovv.
27798 - Correct handling of possible malformed authority signing key
27799 certificates with internal signature types. Fixes bug 880.
27800 Bugfix on 0.2.0.3-alpha.
27801 - Fix a hard-to-trigger resource leak when logging credential status.
27803 - When we can't initialize DNS because the network is down, do not
27804 automatically stop Tor from starting. Instead, we retry failed
27805 dns_init() every 10 minutes, and change the exit policy to reject
27806 *:* until one succeeds. Fixes bug 691.
27807 - Use 64 bits instead of 32 bits for connection identifiers used with
27808 the controller protocol, to greatly reduce risk of identifier reuse.
27809 - When we're choosing an exit node for a circuit, and we have
27810 no pending streams, choose a good general exit rather than one that
27811 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
27812 - Fix another case of assuming, when a specific exit is requested,
27813 that we know more than the user about what hosts it allows.
27814 Fixes one case of bug 752. Patch from rovv.
27815 - Clip the MaxCircuitDirtiness config option to a minimum of 10
27816 seconds. Warn the user if lower values are given in the
27817 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
27818 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
27819 user if lower values are given in the configuration. Bugfix on
27820 0.1.1.17-rc. Patch by Sebastian.
27821 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
27822 the cache because we already had a v0 descriptor with the same ID.
27823 Bugfix on 0.2.0.18-alpha.
27824 - Fix a race condition when freeing keys shared between main thread
27825 and CPU workers that could result in a memory leak. Bugfix on
27826 0.1.0.1-rc. Fixes bug 889.
27827 - Send a valid END cell back when a client tries to connect to a
27828 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
27829 840. Patch from rovv.
27830 - Check which hops rendezvous stream cells are associated with to
27831 prevent possible guess-the-streamid injection attacks from
27832 intermediate hops. Fixes another case of bug 446. Based on patch
27834 - If a broken client asks a non-exit router to connect somewhere,
27835 do not even do the DNS lookup before rejecting the connection.
27836 Fixes another case of bug 619. Patch from rovv.
27837 - When a relay gets a create cell it can't decrypt (e.g. because it's
27838 using the wrong onion key), we were dropping it and letting the
27839 client time out. Now actually answer with a destroy cell. Fixes
27840 bug 904. Bugfix on 0.0.2pre8.
27842 o Minor bugfixes (hidden services):
27843 - Do not throw away existing introduction points on SIGHUP. Bugfix on
27844 0.0.6pre1. Patch by Karsten. Fixes bug 874.
27847 - Report the case where all signatures in a detached set are rejected
27848 differently than the case where there is an error handling the
27850 - When we realize that another process has modified our cached
27851 descriptors, print out a more useful error message rather than
27852 triggering an assertion. Fixes bug 885. Patch from Karsten.
27853 - Implement the 0x20 hack to better resist DNS poisoning: set the
27854 case on outgoing DNS requests randomly, and reject responses that do
27855 not match the case correctly. This logic can be disabled with the
27856 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
27857 of servers that do not reliably preserve case in replies. See
27858 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
27860 - Check DNS replies for more matching fields to better resist DNS
27862 - Never use OpenSSL compression: it wastes RAM and CPU trying to
27863 compress cells, which are basically all encrypted, compressed, or
27867 Changes in version 0.2.1.11-alpha - 2009-01-20
27868 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
27869 week it will take a long time to bootstrap again" bug. It also fixes
27870 an important security-related bug reported by Ilja van Sprundel. You
27871 should upgrade. (We'll send out more details about the bug once people
27872 have had some time to upgrade.)
27875 - Fix a heap-corruption bug that may be remotely triggerable on
27876 some platforms. Reported by Ilja van Sprundel.
27879 - Discard router descriptors as we load them if they are more than
27880 five days old. Otherwise if Tor is off for a long time and then
27881 starts with cached descriptors, it will try to use the onion
27882 keys in those obsolete descriptors when building circuits. Bugfix
27883 on 0.2.0.x. Fixes bug 887.
27886 - Try to make sure that the version of Libevent we're running with
27887 is binary-compatible with the one we built with. May address bug
27889 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
27890 for bug 905. Bugfix on 0.2.1.7-alpha.
27891 - Add a new --enable-local-appdata configuration switch to change
27892 the default location of the datadir on win32 from APPDATA to
27893 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
27894 entirely. Patch from coderman.
27897 - Make outbound DNS packets respect the OutboundBindAddress setting.
27898 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
27899 - When our circuit fails at the first hop (e.g. we get a destroy
27900 cell back), avoid using that OR connection anymore, and also
27901 tell all the one-hop directory requests waiting for it that they
27902 should fail. Bugfix on 0.2.1.3-alpha.
27903 - In the torify(1) manpage, mention that tsocks will leak your
27907 Changes in version 0.2.1.10-alpha - 2009-01-06
27908 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
27909 would make the bridge relay not so useful if it had DirPort set to 0,
27910 and one that could let an attacker learn a little bit of information
27911 about the bridge's users), and a bug that would cause your Tor relay
27912 to ignore a circuit create request it can't decrypt (rather than reply
27913 with an error). It also fixes a wide variety of other bugs.
27916 - If the cached networkstatus consensus is more than five days old,
27917 discard it rather than trying to use it. In theory it could
27918 be useful because it lists alternate directory mirrors, but in
27919 practice it just means we spend many minutes trying directory
27920 mirrors that are long gone from the network. Helps bug 887 a bit;
27922 - Bridge relays that had DirPort set to 0 would stop fetching
27923 descriptors shortly after startup, and then briefly resume
27924 after a new bandwidth test and/or after publishing a new bridge
27925 descriptor. Bridge users that try to bootstrap from them would
27926 get a recent networkstatus but would get descriptors from up to
27927 18 hours earlier, meaning most of the descriptors were obsolete
27928 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
27929 - Prevent bridge relays from serving their 'extrainfo' document
27930 to anybody who asks, now that extrainfo docs include potentially
27931 sensitive aggregated client geoip summaries. Bugfix on
27935 - New controller event "clients_seen" to report a geoip-based summary
27936 of which countries we've seen clients from recently. Now controllers
27937 like Vidalia can show bridge operators that they're actually making
27939 - Build correctly against versions of OpenSSL 0.9.8 or later built
27940 without support for deprecated functions.
27941 - Update to the "December 19 2008" ip-to-country file.
27943 o Minor bugfixes (on 0.2.0.x):
27944 - Authorities now vote for the Stable flag for any router whose
27945 weighted MTBF is at least 5 days, regardless of the mean MTBF.
27946 - Do not remove routers as too old if we do not have any consensus
27947 document. Bugfix on 0.2.0.7-alpha.
27948 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
27949 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
27950 - When an exit relay resolves a stream address to a local IP address,
27951 do not just keep retrying that same exit relay over and
27952 over. Instead, just close the stream. Addresses bug 872. Bugfix
27953 on 0.2.0.32. Patch from rovv.
27954 - If a hidden service sends us an END cell, do not consider
27955 retrying the connection; just close it. Patch from rovv.
27956 - When we made bridge authorities stop serving bridge descriptors over
27957 unencrypted links, we also broke DirPort reachability testing for
27958 bridges. So bridges with a non-zero DirPort were printing spurious
27959 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
27960 - When a relay gets a create cell it can't decrypt (e.g. because it's
27961 using the wrong onion key), we were dropping it and letting the
27962 client time out. Now actually answer with a destroy cell. Fixes
27963 bug 904. Bugfix on 0.0.2pre8.
27964 - Squeeze 2-5% out of client performance (according to oprofile) by
27965 improving the implementation of some policy-manipulation functions.
27967 o Minor bugfixes (on 0.2.1.x):
27968 - Make get_interface_address() function work properly again; stop
27969 guessing the wrong parts of our address as our address.
27970 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
27971 send on that circuit. Otherwise we might violate the proposal-110
27972 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
27974 - When we're sending non-EXTEND cells to the first hop in a circuit,
27975 for example to use an encrypted directory connection, we don't need
27976 to use RELAY_EARLY cells: the first hop knows what kind of cell
27977 it is, and nobody else can even see the cell type. Conserving
27978 RELAY_EARLY cells makes it easier to cannibalize circuits like
27980 - Stop logging nameserver addresses in reverse order.
27981 - If we are retrying a directory download slowly over and over, do
27982 not automatically give up after the 254th failure. Bugfix on
27984 - Resume reporting accurate "stream end" reasons to the local control
27985 port. They were lost in the changes for Proposal 148. Bugfix on
27988 o Deprecated and removed features:
27989 - The old "tor --version --version" command, which would print out
27990 the subversion "Id" of most of the source files, is now removed. It
27991 turned out to be less useful than we'd expected, and harder to
27994 o Code simplifications and refactoring:
27995 - Change our header file guard macros to be less likely to conflict
27996 with system headers. Adam Langley noticed that we were conflicting
27997 with log.h on Android.
27998 - Tool-assisted documentation cleanup. Nearly every function or
27999 static variable in Tor should have its own documentation now.
28002 Changes in version 0.2.1.9-alpha - 2008-12-25
28003 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
28005 o New directory authorities:
28006 - gabelmoo (the authority run by Karsten Loesing) now has a new
28010 - Never use a connection with a mismatched address to extend a
28011 circuit, unless that connection is canonical. A canonical
28012 connection is one whose address is authenticated by the router's
28013 identity key, either in a NETINFO cell or in a router descriptor.
28014 - Avoid a possible memory corruption bug when receiving hidden service
28015 descriptors. Bugfix on 0.2.1.6-alpha.
28018 - Fix a logic error that would automatically reject all but the first
28019 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
28020 part of bug 813/868. Bug spotted by coderman.
28021 - When a stream at an exit relay is in state "resolving" or
28022 "connecting" and it receives an "end" relay cell, the exit relay
28023 would silently ignore the end cell and not close the stream. If
28024 the client never closes the circuit, then the exit relay never
28025 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
28026 reported by "wood".
28027 - When we can't initialize DNS because the network is down, do not
28028 automatically stop Tor from starting. Instead, retry failed
28029 dns_init() every 10 minutes, and change the exit policy to reject
28030 *:* until one succeeds. Fixes bug 691.
28033 - Give a better error message when an overzealous init script says
28034 "sudo -u username tor --user username". Makes Bug 882 easier for
28036 - When a directory authority gives us a new guess for our IP address,
28037 log which authority we used. Hopefully this will help us debug
28038 the recent complaints about bad IP address guesses.
28039 - Detect svn revision properly when we're using git-svn.
28040 - Try not to open more than one descriptor-downloading connection
28041 to an authority at once. This should reduce load on directory
28042 authorities. Fixes bug 366.
28043 - Add cross-certification to newly generated certificates, so that
28044 a signing key is enough information to look up a certificate.
28045 Partial implementation of proposal 157.
28046 - Start serving certificates by <identity digest, signing key digest>
28047 pairs. Partial implementation of proposal 157.
28048 - Clients now never report any stream end reason except 'MISC'.
28049 Implements proposal 148.
28050 - On platforms with a maximum syslog string length, truncate syslog
28051 messages to that length ourselves, rather than relying on the
28052 system to do it for us.
28053 - Optimize out calls to time(NULL) that occur for every IO operation,
28054 or for every cell. On systems where time() is a slow syscall,
28055 this fix will be slightly helpful.
28056 - Exit servers can now answer resolve requests for ip6.arpa addresses.
28057 - When we download a descriptor that we then immediately (as
28058 a directory authority) reject, do not retry downloading it right
28059 away. Should save some bandwidth on authorities. Fix for bug
28060 888. Patch by Sebastian Hahn.
28061 - When a download gets us zero good descriptors, do not notify
28062 Tor that new directory information has arrived.
28063 - Avoid some nasty corner cases in the logic for marking connections
28064 as too old or obsolete or noncanonical for circuits. Partial
28067 o Minor features (controller):
28068 - New CONSENSUS_ARRIVED event to note when a new consensus has
28069 been fetched and validated.
28070 - When we realize that another process has modified our cached
28071 descriptors file, print out a more useful error message rather
28072 than triggering an assertion. Fixes bug 885. Patch from Karsten.
28073 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
28074 controllers to prevent SIGHUP from reloading the
28075 configuration. Fixes bug 856.
28078 - Resume using the correct "REASON=" stream when telling the
28079 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
28080 - When a canonical connection appears later in our internal list
28081 than a noncanonical one for a given OR ID, always use the
28082 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
28084 - Clip the MaxCircuitDirtiness config option to a minimum of 10
28085 seconds. Warn the user if lower values are given in the
28086 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
28087 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
28088 user if lower values are given in the configuration. Bugfix on
28089 0.1.1.17-rc. Patch by Sebastian.
28090 - Fix a race condition when freeing keys shared between main thread
28091 and CPU workers that could result in a memory leak. Bugfix on
28092 0.1.0.1-rc. Fixes bug 889.
28094 o Minor bugfixes (hidden services):
28095 - Do not throw away existing introduction points on SIGHUP (bugfix on
28096 0.0.6pre1); also, do not stall hidden services because we're
28097 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
28098 by John Brooks. Patch by Karsten. Fixes bug 874.
28099 - Fix a memory leak when we decline to add a v2 rendezvous
28100 descriptor to the cache because we already had a v0 descriptor
28101 with the same ID. Bugfix on 0.2.0.18-alpha.
28103 o Deprecated and removed features:
28104 - RedirectExits has been removed. It was deprecated since
28106 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
28107 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
28108 - Cell pools are now always enabled; --disable-cell-pools is ignored.
28110 o Code simplifications and refactoring:
28111 - Rename the confusing or_is_obsolete field to the more appropriate
28112 is_bad_for_new_circs, and move it to or_connection_t where it
28114 - Move edge-only flags from connection_t to edge_connection_t: not
28115 only is this better coding, but on machines of plausible alignment,
28116 it should save 4-8 bytes per connection_t. "Every little bit helps."
28117 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
28118 for consistency; keep old option working for backward compatibility.
28119 - Simplify the code for finding connections to use for a circuit.
28122 Changes in version 0.2.1.8-alpha - 2008-12-08
28123 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
28124 builds better on unusual platforms like Solaris and old OS X, and
28125 fixes a variety of other issues.
28128 - New DirPortFrontPage option that takes an html file and publishes
28129 it as "/" on the DirPort. Now relay operators can provide a
28130 disclaimer without needing to set up a separate webserver. There's
28131 a sample disclaimer in contrib/tor-exit-notice.html.
28134 - When the client is choosing entry guards, now it selects at most
28135 one guard from a given relay family. Otherwise we could end up with
28136 all of our entry points into the network run by the same operator.
28137 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
28140 - Fix a DOS opportunity during the voting signature collection process
28141 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
28142 - Fix a possible segfault when establishing an exit connection. Bugfix
28146 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
28148 - Made Tor a little less aggressive about deleting expired
28149 certificates. Partial fix for bug 854.
28150 - Stop doing unaligned memory access that generated bus errors on
28151 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
28152 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
28153 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
28154 - Make USR2 log-level switch take effect immediately. Bugfix on
28156 - If one win32 nameserver fails to get added, continue adding the
28157 rest, and don't automatically fail.
28158 - Use fcntl() for locking when flock() is not available. Should fix
28159 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
28160 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
28161 could make gcc generate non-functional binary search code. Bugfix
28163 - Build correctly on platforms without socklen_t.
28164 - Avoid potential crash on internal error during signature collection.
28165 Fixes bug 864. Patch from rovv.
28166 - Do not use C's stdio library for writing to log files. This will
28167 improve logging performance by a minute amount, and will stop
28168 leaking fds when our disk is full. Fixes bug 861.
28169 - Stop erroneous use of O_APPEND in cases where we did not in fact
28170 want to re-seek to the end of a file before every last write().
28171 - Correct handling of possible malformed authority signing key
28172 certificates with internal signature types. Fixes bug 880. Bugfix
28174 - Fix a hard-to-trigger resource leak when logging credential status.
28178 - Directory mirrors no longer fetch the v1 directory or
28179 running-routers files. They are obsolete, and nobody asks for them
28180 anymore. This is the first step to making v1 authorities obsolete.
28182 o Minor features (controller):
28183 - Return circuit purposes in response to GETINFO circuit-status. Fixes
28187 Changes in version 0.2.0.32 - 2008-11-20
28188 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
28189 packages (and maybe other packages) noticed by Theo de Raadt, fixes
28190 a smaller security flaw that might allow an attacker to access local
28191 services, further improves hidden service performance, and fixes a
28192 variety of other issues.
28195 - The "User" and "Group" config options did not clear the
28196 supplementary group entries for the Tor process. The "User" option
28197 is now more robust, and we now set the groups to the specified
28198 user's primary group. The "Group" option is now ignored. For more
28199 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
28200 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
28201 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
28202 - The "ClientDNSRejectInternalAddresses" config option wasn't being
28203 consistently obeyed: if an exit relay refuses a stream because its
28204 exit policy doesn't allow it, we would remember what IP address
28205 the relay said the destination address resolves to, even if it's
28206 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
28209 - Fix a DOS opportunity during the voting signature collection process
28210 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
28212 o Major bugfixes (hidden services):
28213 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28214 we were failing the whole hidden service request when the v0
28215 descriptor fetch fails, even if the v2 fetch is still pending and
28216 might succeed. Similarly, if the last v2 fetch fails, we were
28217 failing the whole hidden service request even if a v0 fetch is
28218 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28219 - When extending a circuit to a hidden service directory to upload a
28220 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28221 requests failed, because the router descriptor has not been
28222 downloaded yet. In these cases, do not attempt to upload the
28223 rendezvous descriptor, but wait until the router descriptor is
28224 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
28225 descriptor from a hidden service directory for which the router
28226 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
28230 - Fix several infrequent memory leaks spotted by Coverity.
28231 - When testing for libevent functions, set the LDFLAGS variable
28232 correctly. Found by Riastradh.
28233 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
28234 bootstrapping with tunneled directory connections. Bugfix on
28235 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
28236 - When asked to connect to A.B.exit:80, if we don't know the IP for A
28237 and we know that server B rejects most-but-not all connections to
28238 port 80, we would previously reject the connection. Now, we assume
28239 the user knows what they were asking for. Fixes bug 752. Bugfix
28240 on 0.0.9rc5. Diagnosed by BarkerJr.
28241 - If we overrun our per-second write limits a little, count this as
28242 having used up our write allocation for the second, and choke
28243 outgoing directory writes. Previously, we had only counted this when
28244 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
28245 Bugfix on 0.2.0.x (??).
28246 - Remove the old v2 directory authority 'lefkada' from the default
28247 list. It has been gone for many months.
28248 - Stop doing unaligned memory access that generated bus errors on
28249 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
28250 - Make USR2 log-level switch take effect immediately. Bugfix on
28253 o Minor bugfixes (controller):
28254 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
28255 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
28258 Changes in version 0.2.1.7-alpha - 2008-11-08
28259 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
28260 packages (and maybe other packages) noticed by Theo de Raadt, fixes
28261 a smaller security flaw that might allow an attacker to access local
28262 services, adds better defense against DNS poisoning attacks on exit
28263 relays, further improves hidden service performance, and fixes a
28264 variety of other issues.
28267 - The "ClientDNSRejectInternalAddresses" config option wasn't being
28268 consistently obeyed: if an exit relay refuses a stream because its
28269 exit policy doesn't allow it, we would remember what IP address
28270 the relay said the destination address resolves to, even if it's
28271 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
28272 - The "User" and "Group" config options did not clear the
28273 supplementary group entries for the Tor process. The "User" option
28274 is now more robust, and we now set the groups to the specified
28275 user's primary group. The "Group" option is now ignored. For more
28276 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
28277 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
28278 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
28279 - Do not use or believe expired v3 authority certificates. Patch
28280 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
28283 - Now NodeFamily and MyFamily config options allow spaces in
28284 identity fingerprints, so it's easier to paste them in.
28285 Suggested by Lucky Green.
28286 - Implement the 0x20 hack to better resist DNS poisoning: set the
28287 case on outgoing DNS requests randomly, and reject responses that do
28288 not match the case correctly. This logic can be disabled with the
28289 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
28290 of servers that do not reliably preserve case in replies. See
28291 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
28293 - Preserve case in replies to DNSPort requests in order to support
28294 the 0x20 hack for resisting DNS poisoning attacks.
28296 o Hidden service performance improvements:
28297 - When the client launches an introduction circuit, retry with a
28298 new circuit after 30 seconds rather than 60 seconds.
28299 - Launch a second client-side introduction circuit in parallel
28300 after a delay of 15 seconds (based on work by Christian Wilms).
28301 - Hidden services start out building five intro circuits rather
28302 than three, and when the first three finish they publish a service
28303 descriptor using those. Now we publish our service descriptor much
28304 faster after restart.
28307 - Minor fix in the warning messages when you're having problems
28308 bootstrapping; also, be more forgiving of bootstrap problems when
28309 we're still making incremental progress on a given bootstrap phase.
28310 - When we're choosing an exit node for a circuit, and we have
28311 no pending streams, choose a good general exit rather than one that
28312 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
28313 - Send a valid END cell back when a client tries to connect to a
28314 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
28315 840. Patch from rovv.
28316 - If a broken client asks a non-exit router to connect somewhere,
28317 do not even do the DNS lookup before rejecting the connection.
28318 Fixes another case of bug 619. Patch from rovv.
28319 - Fix another case of assuming, when a specific exit is requested,
28320 that we know more than the user about what hosts it allows.
28321 Fixes another case of bug 752. Patch from rovv.
28322 - Check which hops rendezvous stream cells are associated with to
28323 prevent possible guess-the-streamid injection attacks from
28324 intermediate hops. Fixes another case of bug 446. Based on patch
28326 - Avoid using a negative right-shift when comparing 32-bit
28327 addresses. Possible fix for bug 845 and bug 811.
28328 - Make the assert_circuit_ok() function work correctly on circuits that
28329 have already been marked for close.
28330 - Fix read-off-the-end-of-string error in unit tests when decoding
28331 introduction points.
28332 - Fix uninitialized size field for memory area allocation: may improve
28333 memory performance during directory parsing.
28334 - Treat duplicate certificate fetches as failures, so that we do
28335 not try to re-fetch an expired certificate over and over and over.
28336 - Do not say we're fetching a certificate when we'll in fact skip it
28337 because of a pending download.
28340 Changes in version 0.2.1.6-alpha - 2008-09-30
28341 Tor 0.2.1.6-alpha further improves performance and robustness of
28342 hidden services, starts work on supporting per-country relay selection,
28343 and fixes a variety of smaller issues.
28346 - Implement proposal 121: make it possible to build hidden services
28347 that only certain clients are allowed to connect to. This is
28348 enforced at several points, so that unauthorized clients are unable
28349 to send INTRODUCE cells to the service, or even (depending on the
28350 type of authentication) to learn introduction points. This feature
28351 raises the bar for certain kinds of active attacks against hidden
28352 services. Code by Karsten Loesing.
28353 - Relays now store and serve v2 hidden service descriptors by default,
28354 i.e., the new default value for HidServDirectoryV2 is 1. This is
28355 the last step in proposal 114, which aims to make hidden service
28356 lookups more reliable.
28357 - Start work to allow node restrictions to include country codes. The
28358 syntax to exclude nodes in a country with country code XX is
28359 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
28360 refinement to decide what config options should take priority if
28361 you ask to both use a particular node and exclude it.
28362 - Allow ExitNodes list to include IP ranges and country codes, just
28363 like the Exclude*Nodes lists. Patch from Robert Hogan.
28366 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
28367 Tor to fail to start if you had it configured to use a bridge
28368 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
28369 - When extending a circuit to a hidden service directory to upload a
28370 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28371 requests failed, because the router descriptor had not been
28372 downloaded yet. In these cases, we now wait until the router
28373 descriptor is downloaded, and then retry. Likewise, clients
28374 now skip over a hidden service directory if they don't yet have
28375 its router descriptor, rather than futilely requesting it and
28376 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
28378 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28379 we were failing the whole hidden service request when the v0
28380 descriptor fetch fails, even if the v2 fetch is still pending and
28381 might succeed. Similarly, if the last v2 fetch fails, we were
28382 failing the whole hidden service request even if a v0 fetch is
28383 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28384 - DNS replies need to have names matching their requests, but
28385 these names should be in the questions section, not necessarily
28386 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
28389 - Update to the "September 1 2008" ip-to-country file.
28390 - Allow ports 465 and 587 in the default exit policy again. We had
28391 rejected them in 0.1.0.15, because back in 2005 they were commonly
28392 misconfigured and ended up as spam targets. We hear they are better
28393 locked down these days.
28394 - Use a lockfile to make sure that two Tor processes are not
28395 simultaneously running with the same datadir.
28396 - Serve the latest v3 networkstatus consensus via the control
28397 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
28398 - Better logging about stability/reliability calculations on directory
28400 - Drop the requirement to have an open dir port for storing and
28401 serving v2 hidden service descriptors.
28402 - Directory authorities now serve a /tor/dbg-stability.txt URL to
28403 help debug WFU and MTBF calculations.
28404 - Implement most of Proposal 152: allow specialized servers to permit
28405 single-hop circuits, and clients to use those servers to build
28406 single-hop circuits when using a specialized controller. Patch
28407 from Josh Albrecht. Resolves feature request 768.
28408 - Add a -p option to tor-resolve for specifying the SOCKS port: some
28409 people find host:port too confusing.
28410 - Make TrackHostExit mappings expire a while after their last use, not
28411 after their creation. Patch from Robert Hogan.
28412 - Provide circuit purposes along with circuit events to the controller.
28415 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
28417 - Fixed some memory leaks -- some quite frequent, some almost
28418 impossible to trigger -- based on results from Coverity.
28419 - When testing for libevent functions, set the LDFLAGS variable
28420 correctly. Found by Riastradh.
28421 - Fix an assertion bug in parsing policy-related options; possible fix
28423 - Catch and report a few more bootstrapping failure cases when Tor
28424 fails to establish a TCP connection. Cleanup on 0.2.1.x.
28425 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
28426 bootstrapping with tunneled directory connections. Bugfix on
28427 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
28428 - When asked to connect to A.B.exit:80, if we don't know the IP for A
28429 and we know that server B rejects most-but-not all connections to
28430 port 80, we would previously reject the connection. Now, we assume
28431 the user knows what they were asking for. Fixes bug 752. Bugfix
28432 on 0.0.9rc5. Diagnosed by BarkerJr.
28433 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
28434 service directories if they have no advertised dir port. Bugfix
28436 - If we overrun our per-second write limits a little, count this as
28437 having used up our write allocation for the second, and choke
28438 outgoing directory writes. Previously, we had only counted this when
28439 we had met our limits precisely. Fixes bug 824. Patch by rovv.
28440 Bugfix on 0.2.0.x (??).
28441 - Avoid a "0 divided by 0" calculation when calculating router uptime
28442 at directory authorities. Bugfix on 0.2.0.8-alpha.
28443 - Make DNS resolved controller events into "CLOSED", not
28444 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
28446 - Fix a bug where an unreachable relay would establish enough
28447 reachability testing circuits to do a bandwidth test -- if
28448 we already have a connection to the middle hop of the testing
28449 circuit, then it could establish the last hop by using the existing
28450 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
28451 circuits no longer use entry guards in 0.2.1.3-alpha.
28452 - If we have correct permissions on $datadir, we complain to stdout
28453 and fail to start. But dangerous permissions on
28454 $datadir/cached-status/ would cause us to open a log and complain
28455 there. Now complain to stdout and fail to start in both cases. Fixes
28456 bug 820, reported by seeess.
28457 - Remove the old v2 directory authority 'lefkada' from the default
28458 list. It has been gone for many months.
28460 o Code simplifications and refactoring:
28461 - Revise the connection_new functions so that a more typesafe variant
28462 exists. This will work better with Coverity, and let us find any
28463 actual mistakes we're making here.
28464 - Refactor unit testing logic so that dmalloc can be used sensibly
28465 with unit tests to check for memory leaks.
28466 - Move all hidden-service related fields from connection and circuit
28467 structure to substructures: this way they won't eat so much memory.
28470 Changes in version 0.2.0.31 - 2008-09-03
28471 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
28472 a big bug we're seeing where in rare cases traffic from one Tor stream
28473 gets mixed into another stream, and fixes a variety of smaller issues.
28476 - Make sure that two circuits can never exist on the same connection
28477 with the same circuit ID, even if one is marked for close. This
28478 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
28479 - Relays now reject risky extend cells: if the extend cell includes
28480 a digest of all zeroes, or asks to extend back to the relay that
28481 sent the extend cell, tear down the circuit. Ideas suggested
28483 - If not enough of our entry guards are available so we add a new
28484 one, we might use the new one even if it overlapped with the
28485 current circuit's exit relay (or its family). Anonymity bugfix
28486 pointed out by rovv.
28489 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
28490 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
28491 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28492 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
28493 - Pick size of default geoip filename string correctly on windows.
28494 Fixes bug 806. Bugfix on 0.2.0.30.
28495 - Make the autoconf script accept the obsolete --with-ssl-dir
28496 option as an alias for the actually-working --with-openssl-dir
28497 option. Fix the help documentation to recommend --with-openssl-dir.
28498 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
28499 - When using the TransPort option on OpenBSD, and using the User
28500 option to change UID and drop privileges, make sure to open
28501 /dev/pf before dropping privileges. Fixes bug 782. Patch from
28502 Christopher Davis. Bugfix on 0.1.2.1-alpha.
28503 - Try to attach connections immediately upon receiving a RENDEZVOUS2
28504 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
28505 on the client side when connecting to a hidden service. Bugfix
28506 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
28507 - When closing an application-side connection because its circuit is
28508 getting torn down, generate the stream event correctly. Bugfix on
28509 0.1.2.x. Anonymous patch.
28512 Changes in version 0.2.1.5-alpha - 2008-08-31
28513 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
28514 in a lot of the infrastructure for adding authorization to hidden
28515 services, lays the groundwork for having clients read their load
28516 balancing information out of the networkstatus consensus rather than
28517 the individual router descriptors, addresses two potential anonymity
28518 issues, and fixes a variety of smaller issues.
28521 - Convert many internal address representations to optionally hold
28523 - Generate and accept IPv6 addresses in many protocol elements.
28524 - Make resolver code handle nameservers located at ipv6 addresses.
28525 - Begin implementation of proposal 121 ("Client authorization for
28526 hidden services"): configure hidden services with client
28527 authorization, publish descriptors for them, and configure
28528 authorization data for hidden services at clients. The next
28529 step is to actually access hidden services that perform client
28531 - More progress toward proposal 141: Network status consensus
28532 documents and votes now contain bandwidth information for each
28533 router and a summary of that router's exit policy. Eventually this
28534 will be used by clients so that they do not have to download every
28535 known descriptor before building circuits.
28537 o Major bugfixes (on 0.2.0.x and before):
28538 - When sending CREATED cells back for a given circuit, use a 64-bit
28539 connection ID to find the right connection, rather than an addr:port
28540 combination. Now that we can have multiple OR connections between
28541 the same ORs, it is no longer possible to use addr:port to uniquely
28542 identify a connection.
28543 - Relays now reject risky extend cells: if the extend cell includes
28544 a digest of all zeroes, or asks to extend back to the relay that
28545 sent the extend cell, tear down the circuit. Ideas suggested
28547 - If not enough of our entry guards are available so we add a new
28548 one, we might use the new one even if it overlapped with the
28549 current circuit's exit relay (or its family). Anonymity bugfix
28550 pointed out by rovv.
28553 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
28554 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
28555 - When using the TransPort option on OpenBSD, and using the User
28556 option to change UID and drop privileges, make sure to open /dev/pf
28557 before dropping privileges. Fixes bug 782. Patch from Christopher
28558 Davis. Bugfix on 0.1.2.1-alpha.
28559 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28560 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
28561 - Add a missing safe_str() call for a debug log message.
28562 - Use 64 bits instead of 32 bits for connection identifiers used with
28563 the controller protocol, to greatly reduce risk of identifier reuse.
28564 - Make the autoconf script accept the obsolete --with-ssl-dir
28565 option as an alias for the actually-working --with-openssl-dir
28566 option. Fix the help documentation to recommend --with-openssl-dir.
28567 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
28570 - Rate-limit too-many-sockets messages: when they happen, they happen
28571 a lot. Resolves bug 748.
28572 - Resist DNS poisoning a little better by making sure that names in
28573 answer sections match.
28574 - Print the SOCKS5 error message string as well as the error code
28575 when a tor-resolve request fails. Patch from Jacob.
28578 Changes in version 0.2.1.4-alpha - 2008-08-04
28579 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
28582 - The address part of exit policies was not correctly written
28583 to router descriptors. This generated router descriptors that failed
28584 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
28586 - Tor triggered a false assert when extending a circuit to a relay
28587 but we already have a connection open to that relay. Noticed by
28588 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
28591 - Fix a hidden service logging bug: in some edge cases, the router
28592 descriptor of a previously picked introduction point becomes
28593 obsolete and we need to give up on it rather than continually
28594 complaining that it has become obsolete. Observed by xiando. Bugfix
28597 o Removed features:
28598 - Take out the TestVia config option, since it was a workaround for
28599 a bug that was fixed in Tor 0.1.1.21.
28602 Changes in version 0.2.1.3-alpha - 2008-08-03
28603 Tor 0.2.1.3-alpha implements most of the pieces to prevent
28604 infinite-length circuit attacks (see proposal 110); fixes a bug that
28605 might cause exit relays to corrupt streams they send back; allows
28606 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
28607 ExcludeExitNodes config options; and fixes a big pile of bugs.
28609 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
28610 - Send a bootstrap problem "warn" event on the first problem if the
28611 reason is NO_ROUTE (that is, our network is down).
28614 - Implement most of proposal 110: The first K cells to be sent
28615 along a circuit are marked as special "early" cells; only K "early"
28616 cells will be allowed. Once this code is universal, we can block
28617 certain kinds of DOS attack by requiring that EXTEND commands must
28618 be sent using an "early" cell.
28621 - Try to attach connections immediately upon receiving a RENDEZVOUS2
28622 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
28623 on the client side when connecting to a hidden service. Bugfix
28624 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
28625 - Ensure that two circuits can never exist on the same connection
28626 with the same circuit ID, even if one is marked for close. This
28627 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
28630 - When relays do their initial bandwidth measurement, don't limit
28631 to just our entry guards for the test circuits. Otherwise we tend
28632 to have multiple test circuits going through a single entry guard,
28633 which makes our bandwidth test less accurate. Fixes part of bug 654;
28634 patch contributed by Josh Albrecht.
28635 - Add an ExcludeExitNodes option so users can list a set of nodes
28636 that should be be excluded from the exit node position, but
28637 allowed elsewhere. Implements proposal 151.
28638 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
28639 ExcludeNodes and ExcludeExitNodes lists.
28640 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
28641 be more efficient. Formerly it was quadratic in the number of
28642 servers; now it should be linear. Fixes bug 509.
28643 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
28644 and n_conn_id_digest fields into a separate structure that's
28645 only needed when the circuit has not yet attached to an n_conn.
28648 - Change the contrib/tor.logrotate script so it makes the new
28649 logs as "_tor:_tor" rather than the default, which is generally
28650 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
28651 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
28652 warnings (occasionally), but it can also cause the compiler to
28653 eliminate error-checking code. Suggested by Peter Gutmann.
28654 - When a hidden service is giving up on an introduction point candidate
28655 that was not included in the last published rendezvous descriptor,
28656 don't reschedule publication of the next descriptor. Fixes bug 763.
28658 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
28659 HiddenServiceExcludeNodes as obsolete: they never worked properly,
28660 and nobody claims to be using them. Fixes bug 754. Bugfix on
28661 0.1.0.1-rc. Patch from Christian Wilms.
28662 - Fix a small alignment and memory-wasting bug on buffer chunks.
28665 o Minor bugfixes (controller):
28666 - When closing an application-side connection because its circuit
28667 is getting torn down, generate the stream event correctly.
28668 Bugfix on 0.1.2.x. Anonymous patch.
28670 o Removed features:
28671 - Remove all backward-compatibility code to support relays running
28672 versions of Tor so old that they no longer work at all on the
28676 Changes in version 0.2.0.30 - 2008-07-15
28678 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
28679 warnings (occasionally), but it can also cause the compiler to
28680 eliminate error-checking code. Suggested by Peter Gutmann.
28683 Changes in version 0.2.0.29-rc - 2008-07-08
28684 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
28685 hidden-service performance bugs, and fixes a bunch of smaller bugs.
28688 - If you have more than one bridge but don't know their keys,
28689 you would only launch a request for the descriptor of the first one
28690 on your list. (Tor considered launching requests for the others, but
28691 found that it already had a connection on the way for $0000...0000
28692 so it didn't open another.) Bugfix on 0.2.0.x.
28693 - If you have more than one bridge but don't know their keys, and the
28694 connection to one of the bridges failed, you would cancel all
28695 pending bridge connections. (After all, they all have the same
28696 digest.) Bugfix on 0.2.0.x.
28697 - When a hidden service was trying to establish an introduction point,
28698 and Tor had built circuits preemptively for such purposes, we
28699 were ignoring all the preemptive circuits and launching a new one
28700 instead. Bugfix on 0.2.0.14-alpha.
28701 - When a hidden service was trying to establish an introduction point,
28702 and Tor *did* manage to reuse one of the preemptively built
28703 circuits, it didn't correctly remember which one it used,
28704 so it asked for another one soon after, until there were no
28705 more preemptive circuits, at which point it launched one from
28706 scratch. Bugfix on 0.0.9.x.
28707 - Make directory servers include the X-Your-Address-Is: http header in
28708 their responses even for begin_dir conns. Now clients who only
28709 ever use begin_dir connections still have a way to learn their IP
28710 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
28713 - Fix a macro/CPP interaction that was confusing some compilers:
28714 some GCCs don't like #if/#endif pairs inside macro arguments.
28716 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
28717 Fixes bug 704; fix from Steven Murdoch.
28718 - When opening /dev/null in finish_daemonize(), do not pass the
28719 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
28720 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
28721 - Correctly detect transparent proxy support on Linux hosts that
28722 require in.h to be included before netfilter_ipv4.h. Patch
28724 - Disallow session resumption attempts during the renegotiation
28725 stage of the v2 handshake protocol. Clients should never be trying
28726 session resumption at this point, but apparently some did, in
28727 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
28728 found by Geoff Goodell.
28731 Changes in version 0.2.1.2-alpha - 2008-06-20
28732 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
28733 make it easier to set up your own private Tor network; fixes several
28734 big bugs with using more than one bridge relay; fixes a big bug with
28735 offering hidden services quickly after Tor starts; and uses a better
28736 API for reporting potential bootstrapping problems to the controller.
28739 - New TestingTorNetwork config option to allow adjustment of
28740 previously constant values that, while reasonable, could slow
28741 bootstrapping. Implements proposal 135. Patch from Karsten.
28744 - If you have more than one bridge but don't know their digests,
28745 you would only learn a request for the descriptor of the first one
28746 on your list. (Tor considered launching requests for the others, but
28747 found that it already had a connection on the way for $0000...0000
28748 so it didn't open another.) Bugfix on 0.2.0.x.
28749 - If you have more than one bridge but don't know their digests,
28750 and the connection to one of the bridges failed, you would cancel
28751 all pending bridge connections. (After all, they all have the
28752 same digest.) Bugfix on 0.2.0.x.
28753 - When establishing a hidden service, introduction points that
28754 originate from cannibalized circuits are completely ignored and not
28755 included in rendezvous service descriptors. This might be another
28756 reason for delay in making a hidden service available. Bugfix
28757 from long ago (0.0.9.x?)
28760 - Allow OpenSSL to use dynamic locks if it wants.
28761 - When building a consensus, do not include routers that are down.
28762 This will cut down 30% to 40% on consensus size. Implements
28764 - In directory authorities' approved-routers files, allow
28765 fingerprints with or without space.
28766 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
28767 controller can query our current bootstrap state in case it attaches
28768 partway through and wants to catch up.
28769 - Send an initial "Starting" bootstrap status event, so we have a
28770 state to start out in.
28773 - Asking for a conditional consensus at .../consensus/<fingerprints>
28774 would crash a dirserver if it did not already have a
28775 consensus. Bugfix on 0.2.1.1-alpha.
28776 - Clean up some macro/CPP interactions: some GCC versions don't like
28777 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
28780 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
28781 - Directory authorities shouldn't complain about bootstrapping
28782 problems just because they do a lot of reachability testing and
28783 some of the connection attempts fail.
28784 - Start sending "count" and "recommendation" key/value pairs in
28785 bootstrap problem status events, so the controller can hear about
28786 problems even before Tor decides they're worth reporting for sure.
28787 - If you're using bridges, generate "bootstrap problem" warnings
28788 as soon as you run out of working bridges, rather than waiting
28789 for ten failures -- which will never happen if you have less than
28791 - If we close our OR connection because there's been a circuit
28792 pending on it for too long, we were telling our bootstrap status
28793 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
28796 Changes in version 0.2.1.1-alpha - 2008-06-13
28797 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
28798 were making the Tor process bloat especially on Linux; makes our TLS
28799 handshake blend in better; sends "bootstrap phase" status events to
28800 the controller, so it can keep the user informed of progress (and
28801 problems) fetching directory information and establishing circuits;
28802 and adds a variety of smaller features.
28805 - More work on making our TLS handshake blend in: modify the list
28806 of ciphers advertised by OpenSSL in client mode to even more
28807 closely resemble a common web browser. We cheat a little so that
28808 we can advertise ciphers that the locally installed OpenSSL doesn't
28810 - Start sending "bootstrap phase" status events to the controller,
28811 so it can keep the user informed of progress fetching directory
28812 information and establishing circuits. Also inform the controller
28813 if we think we're stuck at a particular bootstrap phase. Implements
28815 - Resume using OpenSSL's RAND_poll() for better (and more portable)
28816 cross-platform entropy collection again. We used to use it, then
28817 stopped using it because of a bug that could crash systems that
28818 called RAND_poll when they had a lot of fds open. It looks like the
28819 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
28820 at startup, and to call RAND_poll() when we reseed later only if
28821 we have a non-buggy OpenSSL version.
28824 - When we choose to abandon a new entry guard because we think our
28825 older ones might be better, close any circuits pending on that
28826 new entry guard connection. This fix should make us recover much
28827 faster when our network is down and then comes back. Bugfix on
28828 0.1.2.8-beta; found by lodger.
28830 o Memory fixes and improvements:
28831 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
28832 to avoid unused RAM in buffer chunks and memory pools.
28833 - Speed up parsing and cut down on memory fragmentation by using
28834 stack-style allocations for parsing directory objects. Previously,
28835 this accounted for over 40% of allocations from within Tor's code
28836 on a typical directory cache.
28837 - Use a Bloom filter rather than a digest-based set to track which
28838 descriptors we need to keep around when we're cleaning out old
28839 router descriptors. This speeds up the computation significantly,
28840 and may reduce fragmentation.
28841 - Reduce the default smartlist size from 32 to 16; it turns out that
28842 most smartlists hold around 8-12 elements tops.
28843 - Make dumpstats() log the fullness and size of openssl-internal
28845 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
28846 patch to their OpenSSL, turn it on to save memory on servers. This
28847 patch will (with any luck) get included in a mainline distribution
28849 - Never use OpenSSL compression: it wastes RAM and CPU trying to
28850 compress cells, which are basically all encrypted, compressed,
28854 - Stop reloading the router list from disk for no reason when we
28855 run out of reachable directory mirrors. Once upon a time reloading
28856 it would set the 'is_running' flag back to 1 for them. It hasn't
28857 done that for a long time.
28858 - In very rare situations new hidden service descriptors were
28859 published earlier than 30 seconds after the last change to the
28860 service. (We currently think that a hidden service descriptor
28861 that's been stable for 30 seconds is worth publishing.)
28864 - Allow separate log levels to be configured for different logging
28865 domains. For example, this allows one to log all notices, warnings,
28866 or errors, plus all memory management messages of level debug or
28867 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
28868 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
28869 and stop using a warning that had become unfixably verbose under
28871 - New --hush command-line option similar to --quiet. While --quiet
28872 disables all logging to the console on startup, --hush limits the
28873 output to messages of warning and error severity.
28874 - Servers support a new URL scheme for consensus downloads that
28875 allows the client to specify which authorities are trusted.
28876 The server then only sends the consensus if the client will trust
28877 it. Otherwise a 404 error is sent back. Clients use this
28878 new scheme when the server supports it (meaning it's running
28879 0.2.1.1-alpha or later). Implements proposal 134.
28880 - New configure/torrc options (--enable-geoip-stats,
28881 DirRecordUsageByCountry) to record how many IPs we've served
28882 directory info to in each country code, how many status documents
28883 total we've sent to each country code, and what share of the total
28884 directory requests we should expect to see.
28885 - Use the TLS1 hostname extension to more closely resemble browser
28887 - Lots of new unit tests.
28888 - Add a macro to implement the common pattern of iterating through
28889 two parallel lists in lockstep.
28892 Changes in version 0.2.0.28-rc - 2008-06-13
28893 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
28894 performance bug, and fixes a bunch of smaller bugs.
28897 - Fix a bug where, when we were choosing the 'end stream reason' to
28898 put in our relay end cell that we send to the exit relay, Tor
28899 clients on Windows were sometimes sending the wrong 'reason'. The
28900 anonymity problem is that exit relays may be able to guess whether
28901 the client is running Windows, thus helping partition the anonymity
28902 set. Down the road we should stop sending reasons to exit relays,
28903 or otherwise prevent future versions of this bug.
28906 - While setting up a hidden service, some valid introduction circuits
28907 were overlooked and abandoned. This might be the reason for
28908 the long delay in making a hidden service available. Bugfix on
28912 - Update to the "June 9 2008" ip-to-country file.
28913 - Run 'make test' as part of 'make dist', so we stop releasing so
28914 many development snapshots that fail their unit tests.
28917 - When we're checking if we have enough dir info for each relay
28918 to begin establishing circuits, make sure that we actually have
28919 the descriptor listed in the consensus, not just any descriptor.
28921 - Bridge relays no longer print "xx=0" in their extrainfo document
28922 for every single country code in the geoip db. Bugfix on
28924 - Only warn when we fail to load the geoip file if we were planning to
28925 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
28926 - If we change our MaxAdvertisedBandwidth and then reload torrc,
28927 Tor won't realize it should publish a new relay descriptor. Fixes
28928 bug 688, reported by mfr. Bugfix on 0.1.2.x.
28929 - When we haven't had any application requests lately, don't bother
28930 logging that we have expired a bunch of descriptors. Bugfix
28932 - Make relay cells written on a connection count as non-padding when
28933 tracking how long a connection has been in use. Bugfix on
28934 0.2.0.1-alpha. Spotted by lodger.
28935 - Fix unit tests in 0.2.0.27-rc.
28936 - Fix compile on Windows.
28939 Changes in version 0.2.0.27-rc - 2008-06-03
28940 Tor 0.2.0.27-rc adds a few features we left out of the earlier
28941 release candidates. In particular, we now include an IP-to-country
28942 GeoIP database, so controllers can easily look up what country a
28943 given relay is in, and so bridge relays can give us some sanitized
28944 summaries about which countries are making use of bridges. (See proposal
28945 126-geoip-fetching.txt for details.)
28948 - Include an IP-to-country GeoIP file in the tarball, so bridge
28949 relays can report sanitized summaries of the usage they're seeing.
28952 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
28953 Robert Hogan. Fixes the first part of bug 681.
28954 - Make bridge authorities never serve extrainfo docs.
28955 - Add support to detect Libevent versions in the 1.4.x series
28957 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
28958 - Include a new contrib/tor-exit-notice.html file that exit relay
28959 operators can put on their website to help reduce abuse queries.
28962 - When tunneling an encrypted directory connection, and its first
28963 circuit fails, do not leave it unattached and ask the controller
28964 to deal. Fixes the second part of bug 681.
28965 - Make bridge authorities correctly expire old extrainfo documents
28969 Changes in version 0.2.0.26-rc - 2008-05-13
28970 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
28971 in Debian's OpenSSL packages. All users running any 0.2.0.x version
28972 should upgrade, whether they're running Debian or not.
28974 o Major security fixes:
28975 - Use new V3 directory authority keys on the tor26, gabelmoo, and
28976 moria1 V3 directory authorities. The old keys were generated with
28977 a vulnerable version of Debian's OpenSSL package, and must be
28978 considered compromised. Other authorities' keys were not generated
28979 with an affected version of OpenSSL.
28982 - List authority signatures as "unrecognized" based on DirServer
28983 lines, not on cert cache. Bugfix on 0.2.0.x.
28986 - Add a new V3AuthUseLegacyKey option to make it easier for
28987 authorities to change their identity keys if they have to.
28990 Changes in version 0.2.0.25-rc - 2008-04-23
28991 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
28994 - Remember to initialize threading before initializing logging.
28995 Otherwise, many BSD-family implementations will crash hard on
28996 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
28999 - Authorities correctly free policies on bad servers on
29000 exit. Fixes bug 672. Bugfix on 0.2.0.x.
29003 Changes in version 0.2.0.24-rc - 2008-04-22
29004 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
29005 v3 directory authority, makes relays with dynamic IP addresses and no
29006 DirPort notice more quickly when their IP address changes, fixes a few
29007 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
29009 o New directory authorities:
29010 - Take lefkada out of the list of v3 directory authorities, since
29011 it has been down for months.
29012 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
29016 - Detect address changes more quickly on non-directory mirror
29017 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
29019 o Minor features (security):
29020 - Reject requests for reverse-dns lookup of names that are in
29021 a private address space. Patch from lodger.
29022 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
29025 o Minor bugfixes (crashes):
29026 - Avoid a rare assert that can trigger when Tor doesn't have much
29027 directory information yet and it tries to fetch a v2 hidden
29028 service descriptor. Fixes bug 651, reported by nwf.
29029 - Initialize log mutex before initializing dmalloc. Otherwise,
29030 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
29031 - Use recursive pthread mutexes in order to avoid deadlock when
29032 logging debug-level messages to a controller. Bug spotted by nwf,
29033 bugfix on 0.2.0.16-alpha.
29035 o Minor bugfixes (resource management):
29036 - Keep address policies from leaking memory: start their refcount
29037 at 1, not 2. Bugfix on 0.2.0.16-alpha.
29038 - Free authority certificates on exit, so they don't look like memory
29039 leaks. Bugfix on 0.2.0.19-alpha.
29040 - Free static hashtables for policy maps and for TLS connections on
29041 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
29042 - Avoid allocating extra space when computing consensuses on 64-bit
29043 platforms. Bug spotted by aakova.
29045 o Minor bugfixes (misc):
29046 - Do not read the configuration file when we've only been told to
29047 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
29048 based on patch from Sebastian Hahn.
29049 - Exit relays that are used as a client can now reach themselves
29050 using the .exit notation, rather than just launching an infinite
29051 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
29052 - When attempting to open a logfile fails, tell us why.
29053 - Fix a dumb bug that was preventing us from knowing that we should
29054 preemptively build circuits to handle expected directory requests.
29055 Fixes bug 660. Bugfix on 0.1.2.x.
29056 - Warn less verbosely about clock skew from netinfo cells from
29057 untrusted sources. Fixes bug 663.
29058 - Make controller stream events for DNS requests more consistent,
29059 by adding "new stream" events for DNS requests, and removing
29060 spurious "stream closed" events" for cached reverse resolves.
29061 Patch from mwenge. Fixes bug 646.
29062 - Correctly notify one-hop connections when a circuit build has
29063 failed. Possible fix for bug 669. Found by lodger.
29066 Changes in version 0.2.0.23-rc - 2008-03-24
29067 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
29068 makes bootstrapping faster if the first directory mirror you contact
29069 is down. The bundles also include the new Vidalia 0.1.2 release.
29072 - When a tunneled directory request is made to a directory server
29073 that's down, notice after 30 seconds rather than 120 seconds. Also,
29074 fail any begindir streams that are pending on it, so they can
29075 retry elsewhere. This was causing multi-minute delays on bootstrap.
29078 Changes in version 0.2.0.22-rc - 2008-03-18
29079 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
29080 enables encrypted directory connections by default for non-relays, fixes
29081 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
29082 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
29085 - Enable encrypted directory connections by default for non-relays,
29086 so censor tools that block Tor directory connections based on their
29087 plaintext patterns will no longer work. This means Tor works in
29088 certain censored countries by default again.
29091 - Make sure servers always request certificates from clients during
29092 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
29093 - Do not enter a CPU-eating loop when a connection is closed in
29094 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
29095 diagnosed by lodger; bugfix on 0.2.0.20-rc.
29096 - Fix assertion failure that could occur when a blocked circuit
29097 became unblocked, and it had pending client DNS requests. Bugfix
29098 on 0.2.0.1-alpha. Fixes bug 632.
29100 o Minor bugfixes (on 0.1.2.x):
29101 - Generate "STATUS_SERVER" events rather than misspelled
29102 "STATUS_SEVER" events. Caught by mwenge.
29103 - When counting the number of bytes written on a TLS connection,
29104 look at the BIO actually used for writing to the network, not
29105 at the BIO used (sometimes) to buffer data for the network.
29106 Looking at different BIOs could result in write counts on the
29107 order of ULONG_MAX. Fixes bug 614.
29108 - On Windows, correctly detect errors when listing the contents of
29109 a directory. Fix from lodger.
29111 o Minor bugfixes (on 0.2.0.x):
29112 - Downgrade "sslv3 alert handshake failure" message to INFO.
29113 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
29114 left BandwidthRate and BandwidthBurst at the default, we would be
29115 silently limited by those defaults. Now raise them to match the
29116 RelayBandwidth* values.
29117 - Fix the SVK version detection logic to work correctly on a branch.
29118 - Make --enable-openbsd-malloc work correctly on Linux with alpha
29119 CPUs. Fixes bug 625.
29120 - Logging functions now check that the passed severity is sane.
29121 - Use proper log levels in the testsuite call of
29122 get_interface_address6().
29123 - When using a nonstandard malloc, do not use the platform values for
29124 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
29125 - Make the openbsd malloc code use 8k pages on alpha CPUs and
29127 - Detect mismatched page sizes when using --enable-openbsd-malloc.
29128 - Avoid double-marked-for-close warning when certain kinds of invalid
29129 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
29130 for bug 617. Bugfix on 0.2.0.1-alpha.
29131 - Make sure that the "NULL-means-reject *:*" convention is followed by
29132 all the policy manipulation functions, avoiding some possible crash
29133 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
29134 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
29135 actually works, and doesn't warn about every single reverse lookup.
29136 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
29139 - Only log guard node status when guard node status has changed.
29140 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
29141 make "INFO" 75% less verbose.
29144 Changes in version 0.2.0.21-rc - 2008-03-02
29145 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
29146 makes Tor work well with Vidalia again, fixes a rare assert bug,
29147 and fixes a pair of more minor bugs. The bundles also include Vidalia
29148 0.1.0 and Torbutton 1.1.16.
29151 - The control port should declare that it requires password auth
29152 when HashedControlSessionPassword is set too. Patch from Matt Edman;
29153 bugfix on 0.2.0.20-rc. Fixes bug 615.
29154 - Downgrade assert in connection_buckets_decrement() to a log message.
29155 This may help us solve bug 614, and in any case will make its
29156 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
29157 - We were sometimes miscounting the number of bytes read from the
29158 network, causing our rate limiting to not be followed exactly.
29159 Bugfix on 0.2.0.16-alpha. Reported by lodger.
29162 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
29163 OpenSSL versions should have been working fine. Diagnosis and patch
29164 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
29165 Bugfix on 0.2.0.20-rc.
29168 Changes in version 0.2.0.20-rc - 2008-02-24
29169 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
29170 makes more progress towards normalizing Tor's TLS handshake, makes
29171 hidden services work better again, helps relays bootstrap if they don't
29172 know their IP address, adds optional support for linking in openbsd's
29173 allocator or tcmalloc, allows really fast relays to scale past 15000
29174 sockets, and fixes a bunch of minor bugs reported by Veracode.
29177 - Enable the revised TLS handshake based on the one designed by
29178 Steven Murdoch in proposal 124, as revised in proposal 130. It
29179 includes version negotiation for OR connections as described in
29180 proposal 105. The new handshake is meant to be harder for censors
29181 to fingerprint, and it adds the ability to detect certain kinds of
29182 man-in-the-middle traffic analysis attacks. The version negotiation
29183 feature will allow us to improve Tor's link protocol more safely
29185 - Choose which bridge to use proportional to its advertised bandwidth,
29186 rather than uniformly at random. This should speed up Tor for
29187 bridge users. Also do this for people who set StrictEntryNodes.
29188 - When a TrackHostExits-chosen exit fails too many times in a row,
29189 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
29192 - Resolved problems with (re-)fetching hidden service descriptors.
29193 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
29194 and 0.2.0.19-alpha.
29195 - If we only ever used Tor for hidden service lookups or posts, we
29196 would stop building circuits and start refusing connections after
29197 24 hours, since we falsely believed that Tor was dormant. Reported
29198 by nwf; bugfix on 0.1.2.x.
29199 - Servers that don't know their own IP address should go to the
29200 authorities for their first directory fetch, even if their DirPort
29201 is off or if they don't know they're reachable yet. This will help
29202 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
29203 - When counting the number of open sockets, count not only the number
29204 of sockets we have received from the socket() call, but also
29205 the number we've gotten from accept() and socketpair(). This bug
29206 made us fail to count all sockets that we were using for incoming
29207 connections. Bugfix on 0.2.0.x.
29208 - Fix code used to find strings within buffers, when those strings
29209 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
29210 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
29211 - Add a new __HashedControlSessionPassword option for controllers
29212 to use for one-off session password hashes that shouldn't get
29213 saved to disk by SAVECONF --- Vidalia users were accumulating a
29214 pile of HashedControlPassword lines in their torrc files, one for
29215 each time they had restarted Tor and then clicked Save. Make Tor
29216 automatically convert "HashedControlPassword" to this new option but
29217 only when it's given on the command line. Partial fix for bug 586.
29219 o Minor features (performance):
29220 - Tune parameters for cell pool allocation to minimize amount of
29222 - Add OpenBSD malloc code from phk as an optional malloc
29223 replacement on Linux: some glibc libraries do very poorly
29224 with Tor's memory allocation patterns. Pass
29225 --enable-openbsd-malloc to get the replacement malloc code.
29226 - Add a --with-tcmalloc option to the configure script to link
29227 against tcmalloc (if present). Does not yet search for
29228 non-system include paths.
29229 - Stop imposing an arbitrary maximum on the number of file descriptors
29230 used for busy servers. Bug reported by Olaf Selke; patch from
29233 o Minor features (other):
29234 - When SafeLogging is disabled, log addresses along with all TLS
29236 - When building with --enable-gcc-warnings, check for whether Apple's
29237 warning "-Wshorten-64-to-32" is available.
29238 - Add a --passphrase-fd argument to the tor-gencert command for
29241 o Minor bugfixes (memory leaks and code problems):
29242 - We were leaking a file descriptor if Tor started with a zero-length
29243 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
29244 - Detect size overflow in zlib code. Reported by Justin Ferguson and
29246 - We were comparing the raw BridgePassword entry with a base64'ed
29247 version of it, when handling a "/tor/networkstatus-bridges"
29248 directory request. Now compare correctly. Noticed by Veracode.
29249 - Recover from bad tracked-since value in MTBF-history file.
29250 Should fix bug 537.
29251 - Alter the code that tries to recover from unhandled write
29252 errors, to not try to flush onto a socket that's given us
29253 unhandled errors. Bugfix on 0.1.2.x.
29254 - Make Unix controlsockets work correctly on OpenBSD. Patch from
29255 tup. Bugfix on 0.2.0.3-alpha.
29257 o Minor bugfixes (other):
29258 - If we have an extra-info document for our server, always make
29259 it available on the control port, even if we haven't gotten
29260 a copy of it from an authority yet. Patch from mwenge.
29261 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
29262 - Directory mirrors no longer include a guess at the client's IP
29263 address if the connection appears to be coming from the same /24
29264 network; it was producing too many wrong guesses.
29265 - Make the new hidden service code respect the SafeLogging setting.
29266 Bugfix on 0.2.0.x. Patch from Karsten.
29267 - When starting as an authority, do not overwrite all certificates
29268 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
29269 - If we're trying to flush the last bytes on a connection (for
29270 example, when answering a directory request), reset the
29271 time-to-give-up timeout every time we manage to write something
29272 on the socket. Bugfix on 0.1.2.x.
29273 - Change the behavior of "getinfo status/good-server-descriptor"
29274 so it doesn't return failure when any authority disappears.
29275 - Even though the man page said that "TrackHostExits ." should
29276 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
29277 - Report TLS "zero return" case as a "clean close" and "IO error"
29278 as a "close". Stop calling closes "unexpected closes": existing
29279 Tors don't use SSL_close(), so having a connection close without
29280 the TLS shutdown handshake is hardly unexpected.
29281 - Send NAMESERVER_STATUS messages for a single failed nameserver
29284 o Code simplifications and refactoring:
29285 - Remove the tor_strpartition function: its logic was confused,
29286 and it was only used for one thing that could be implemented far
29290 Changes in version 0.2.0.19-alpha - 2008-02-09
29291 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
29292 handshake, makes path selection for relays more secure and IP address
29293 guessing more robust, and generally fixes a lot of bugs in preparation
29294 for calling the 0.2.0 branch stable.
29297 - Do not include recognizeable strings in the commonname part of
29298 Tor's x509 certificates.
29301 - If we're a relay, avoid picking ourselves as an introduction point,
29302 a rendezvous point, or as the final hop for internal circuits. Bug
29303 reported by taranis and lodger. Bugfix on 0.1.2.x.
29304 - Patch from "Andrew S. Lists" to catch when we contact a directory
29305 mirror at IP address X and he says we look like we're coming from
29306 IP address X. Bugfix on 0.1.2.x.
29308 o Minor features (security):
29309 - Be more paranoid about overwriting sensitive memory on free(),
29310 as a defensive programming tactic to ensure forward secrecy.
29312 o Minor features (directory authority):
29313 - Actually validate the options passed to AuthDirReject,
29314 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
29315 - Reject router descriptors with out-of-range bandwidthcapacity or
29316 bandwidthburst values.
29318 o Minor features (controller):
29319 - Reject controller commands over 1MB in length. This keeps rogue
29320 processes from running us out of memory.
29322 o Minor features (misc):
29323 - Give more descriptive well-formedness errors for out-of-range
29324 hidden service descriptor/protocol versions.
29325 - Make memory debugging information describe more about history
29326 of cell allocation, so we can help reduce our memory use.
29328 o Deprecated features (controller):
29329 - The status/version/num-versioning and status/version/num-concurring
29330 GETINFO options are no longer useful in the v3 directory protocol:
29331 treat them as deprecated, and warn when they're used.
29334 - When our consensus networkstatus has been expired for a while, stop
29335 being willing to build circuits using it. Fixes bug 401. Bugfix
29337 - Directory caches now fetch certificates from all authorities
29338 listed in a networkstatus consensus, even when they do not
29339 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
29340 - When connecting to a bridge without specifying its key, insert
29341 the connection into the identity-to-connection map as soon as
29342 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
29343 - Detect versions of OS X where malloc_good_size() is present in the
29344 library but never actually declared. Resolves bug 587. Bugfix
29346 - Stop incorrectly truncating zlib responses to directory authority
29347 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
29348 - Stop recommending that every server operator send mail to tor-ops.
29349 Resolves bug 597. Bugfix on 0.1.2.x.
29350 - Don't trigger an assert if we start a directory authority with a
29351 private IP address (like 127.0.0.1).
29352 - Avoid possible failures when generating a directory with routers
29353 with over-long versions strings, or too many flags set. Bugfix
29355 - If an attempt to launch a DNS resolve request over the control
29356 port fails because we have overrun the limit on the number of
29357 connections, tell the controller that the request has failed.
29358 - Avoid using too little bandwidth when our clock skips a few
29359 seconds. Bugfix on 0.1.2.x.
29360 - Fix shell error when warning about missing packages in configure
29361 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
29362 - Do not become confused when receiving a spurious VERSIONS-like
29363 cell from a confused v1 client. Bugfix on 0.2.0.x.
29364 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
29365 introduction points for a hidden service have failed. Patch from
29366 Karsten Loesing. Bugfix on 0.2.0.x.
29368 o Code simplifications and refactoring:
29369 - Remove some needless generality from cpuworker code, for improved
29371 - Stop overloading the circuit_t.onionskin field for both "onionskin
29372 from a CREATE cell that we are waiting for a cpuworker to be
29373 assigned" and "onionskin from an EXTEND cell that we are going to
29374 send to an OR as soon as we are connected". Might help with bug 600.
29375 - Add an in-place version of aes_crypt() so that we can avoid doing a
29376 needless memcpy() call on each cell payload.
29379 Changes in version 0.2.0.18-alpha - 2008-01-25
29380 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
29381 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
29382 that can warn or reject connections to ports generally associated with
29383 vulnerable-plaintext protocols.
29385 o New directory authorities:
29386 - Set up dannenberg (run by CCC) as the sixth v3 directory
29390 - Fix a major memory leak when attempting to use the v2 TLS
29391 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
29392 - We accidentally enabled the under-development v2 TLS handshake
29393 code, which was causing log entries like "TLS error while
29394 renegotiating handshake". Disable it again. Resolves bug 590.
29395 - We were computing the wrong Content-Length: header for directory
29396 responses that need to be compressed on the fly, causing clients
29397 asking for those items to always fail. Bugfix on 0.2.0.x; partially
29401 - Avoid going directly to the directory authorities even if you're a
29402 relay, if you haven't found yourself reachable yet or if you've
29403 decided not to advertise your dirport yet. Addresses bug 556.
29404 - If we've gone 12 hours since our last bandwidth check, and we
29405 estimate we have less than 50KB bandwidth capacity but we could
29406 handle more, do another bandwidth test.
29407 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
29408 Tor can warn and/or refuse connections to ports commonly used with
29409 vulnerable-plaintext protocols. Currently we warn on ports 23,
29410 109, 110, and 143, but we don't reject any.
29413 - When we setconf ClientOnly to 1, close any current OR and Dir
29414 listeners. Reported by mwenge.
29415 - When we get a consensus that's been signed by more people than
29416 we expect, don't log about it; it's not a big deal. Reported
29420 - Don't answer "/tor/networkstatus-bridges" directory requests if
29421 the request isn't encrypted.
29422 - Make "ClientOnly 1" config option disable directory ports too.
29423 - Patches from Karsten Loesing to make v2 hidden services more
29424 robust: work even when there aren't enough HSDir relays available;
29425 retry when a v2 rend desc fetch fails; but don't retry if we
29426 already have a usable v0 rend desc.
29429 Changes in version 0.2.0.17-alpha - 2008-01-17
29430 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
29433 - Make the tor-gencert man page get included correctly in the tarball.
29436 Changes in version 0.2.0.16-alpha - 2008-01-17
29437 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
29438 Loesing, and generally cleans up a lot of features and minor bugs.
29440 o New directory authorities:
29441 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
29444 o Major performance improvements:
29445 - Switch our old ring buffer implementation for one more like that
29446 used by free Unix kernels. The wasted space in a buffer with 1mb
29447 of data will now be more like 8k than 1mb. The new implementation
29448 also avoids realloc();realloc(); patterns that can contribute to
29449 memory fragmentation.
29452 - Configuration files now accept C-style strings as values. This
29453 helps encode characters not allowed in the current configuration
29454 file format, such as newline or #. Addresses bug 557.
29455 - Although we fixed bug 539 (where servers would send HTTP status 503
29456 responses _and_ send a body too), there are still servers out
29457 there that haven't upgraded. Therefore, make clients parse such
29458 bodies when they receive them.
29459 - When we're not serving v2 directory information, there is no reason
29460 to actually keep any around. Remove the obsolete files and directory
29461 on startup if they are very old and we aren't going to serve them.
29463 o Minor performance improvements:
29464 - Reference-count and share copies of address policy entries; only 5%
29465 of them were actually distinct.
29466 - Never walk through the list of logs if we know that no log is
29467 interested in a given message.
29470 - When an authority has not signed a consensus, do not try to
29471 download a nonexistent "certificate with key 00000000". Bugfix
29472 on 0.2.0.x. Fixes bug 569.
29473 - Fix a rare assert error when we're closing one of our threads:
29474 use a mutex to protect the list of logs, so we never write to the
29475 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
29476 bug 575, which is kind of the revenge of bug 222.
29477 - Patch from Karsten Loesing to complain less at both the client
29478 and the relay when a relay used to have the HSDir flag but doesn't
29479 anymore, and we try to upload a hidden service descriptor.
29480 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
29482 - Do not try to download missing certificates until we have tried
29483 to check our fallback consensus. Fixes bug 583.
29484 - Make bridges round reported GeoIP stats info up to the nearest
29485 estimate, not down. Now we can distinguish between "0 people from
29486 this country" and "1 person from this country".
29487 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
29488 - Avoid possible segfault if key generation fails in
29489 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
29490 - Avoid segfault in the case where a badly behaved v2 versioning
29491 directory sends a signed networkstatus with missing client-versions.
29493 - Avoid segfaults on certain complex invocations of
29494 router_get_by_hexdigest(). Bugfix on 0.1.2.
29495 - Correct bad index on array access in parse_http_time(). Bugfix
29497 - Fix possible bug in vote generation when server versions are present
29498 but client versions are not.
29499 - Fix rare bug on REDIRECTSTREAM control command when called with no
29500 port set: it could erroneously report an error when none had
29502 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
29503 compressing large objects and find ourselves with more than 4k
29504 left over. Bugfix on 0.2.0.
29505 - Fix a small memory leak when setting up a hidden service.
29506 - Fix a few memory leaks that could in theory happen under bizarre
29508 - Fix an assert if we post a general-purpose descriptor via the
29509 control port but that descriptor isn't mentioned in our current
29510 network consensus. Bug reported by Jon McLachlan; bugfix on
29513 o Minor features (controller):
29514 - Get NS events working again. Patch from tup.
29515 - The GETCONF command now escapes and quotes configuration values
29516 that don't otherwise fit into the torrc file.
29517 - The SETCONF command now handles quoted values correctly.
29519 o Minor features (directory authorities):
29520 - New configuration options to override default maximum number of
29521 servers allowed on a single IP address. This is important for
29522 running a test network on a single host.
29523 - Actually implement the -s option to tor-gencert.
29524 - Add a manual page for tor-gencert.
29526 o Minor features (bridges):
29527 - Bridge authorities no longer serve bridge descriptors over
29528 unencrypted connections.
29530 o Minor features (other):
29531 - Add hidden services and DNSPorts to the list of things that make
29532 Tor accept that it has running ports. Change starting Tor with no
29533 ports from a fatal error to a warning; we might change it back if
29534 this turns out to confuse anybody. Fixes bug 579.
29537 Changes in version 0.1.2.19 - 2008-01-17
29538 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
29539 exit policy a little bit more conservative so it's safer to run an
29540 exit relay on a home system, and fixes a variety of smaller issues.
29543 - Exit policies now reject connections that are addressed to a
29544 relay's public (external) IP address too, unless
29545 ExitPolicyRejectPrivate is turned off. We do this because too
29546 many relays are running nearby to services that trust them based
29547 on network address.
29550 - When the clock jumps forward a lot, do not allow the bandwidth
29551 buckets to become negative. Fixes bug 544.
29552 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
29553 on every successful resolve. Reported by Mike Perry.
29554 - Purge old entries from the "rephist" database and the hidden
29555 service descriptor database even when DirPort is zero.
29556 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
29557 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
29558 crashing or mis-answering these requests.
29559 - When we decide to send a 503 response to a request for servers, do
29560 not then also send the server descriptors: this defeats the whole
29561 purpose. Fixes bug 539.
29564 - Changing the ExitPolicyRejectPrivate setting should cause us to
29565 rebuild our server descriptor.
29566 - Fix handling of hex nicknames when answering controller requests for
29567 networkstatus by name, or when deciding whether to warn about
29568 unknown routers in a config option. (Patch from mwenge.)
29569 - Fix a couple of hard-to-trigger autoconf problems that could result
29570 in really weird results on platforms whose sys/types.h files define
29571 nonstandard integer types.
29572 - Don't try to create the datadir when running --verify-config or
29573 --hash-password. Resolves bug 540.
29574 - If we were having problems getting a particular descriptor from the
29575 directory caches, and then we learned about a new descriptor for
29576 that router, we weren't resetting our failure count. Reported
29578 - Although we fixed bug 539 (where servers would send HTTP status 503
29579 responses _and_ send a body too), there are still servers out there
29580 that haven't upgraded. Therefore, make clients parse such bodies
29581 when they receive them.
29582 - Run correctly on systems where rlim_t is larger than unsigned long.
29583 This includes some 64-bit systems.
29584 - Run correctly on platforms (like some versions of OS X 10.5) where
29585 the real limit for number of open files is OPEN_FILES, not rlim_max
29586 from getrlimit(RLIMIT_NOFILES).
29587 - Avoid a spurious free on base64 failure.
29588 - Avoid segfaults on certain complex invocations of
29589 router_get_by_hexdigest().
29590 - Fix rare bug on REDIRECTSTREAM control command when called with no
29591 port set: it could erroneously report an error when none had
29595 Changes in version 0.2.0.15-alpha - 2007-12-25
29596 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
29597 features added in 0.2.0.13-alpha.
29600 - Fix several remotely triggerable asserts based on DirPort requests
29601 for a v2 or v3 networkstatus object before we were prepared. This
29602 was particularly bad for 0.2.0.13 and later bridge relays, who
29603 would never have a v2 networkstatus and would thus always crash
29604 when used. Bugfixes on 0.2.0.x.
29605 - Estimate the v3 networkstatus size more accurately, rather than
29606 estimating it at zero bytes and giving it artificially high priority
29607 compared to other directory requests. Bugfix on 0.2.0.x.
29610 - Fix configure.in logic for cross-compilation.
29611 - When we load a bridge descriptor from the cache, and it was
29612 previously unreachable, mark it as retriable so we won't just
29613 ignore it. Also, try fetching a new copy immediately. Bugfixes
29615 - The bridge GeoIP stats were counting other relays, for example
29616 self-reachability and authority-reachability tests.
29619 - Support compilation to target iPhone; patch from cjacker huang.
29620 To build for iPhone, pass the --enable-iphone option to configure.
29623 Changes in version 0.2.0.14-alpha - 2007-12-23
29625 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
29626 without a datadirectory from a previous Tor install. Reported
29628 - Fix a crash when we fetch a descriptor that turns out to be
29629 unexpected (it used to be in our networkstatus when we started
29630 fetching it, but it isn't in our current networkstatus), and we
29631 aren't using bridges. Bugfix on 0.2.0.x.
29632 - Fix a crash when accessing hidden services: it would work the first
29633 time you use a given introduction point for your service, but
29634 on subsequent requests we'd be using garbage memory. Fixed by
29635 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
29636 - Fix a crash when we load a bridge descriptor from disk but we don't
29637 currently have a Bridge line for it in our torrc. Bugfix on
29641 - If bridge authorities set BridgePassword, they will serve a
29642 snapshot of known bridge routerstatuses from their DirPort to
29643 anybody who knows that password. Unset by default.
29646 - Make the unit tests build again.
29647 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
29648 - Make PublishServerDescriptor default to 1, so the default doesn't
29649 have to change as we invent new directory protocol versions.
29650 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
29651 be included unless sys/time.h is already included. Fixes
29652 bug 553. Bugfix on 0.2.0.x.
29653 - If we receive a general-purpose descriptor and then receive an
29654 identical bridge-purpose descriptor soon after, don't discard
29655 the next one as a duplicate.
29658 - If BridgeRelay is set to 1, then the default for
29659 PublishServerDescriptor is now "bridge" rather than "v2,v3".
29660 - If the user sets RelayBandwidthRate but doesn't set
29661 RelayBandwidthBurst, then make them equal rather than erroring out.
29664 Changes in version 0.2.0.13-alpha - 2007-12-21
29665 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
29666 Goodell, fixes many more bugs, and adds a lot of infrastructure for
29669 o New directory authorities:
29670 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
29674 - Only update guard status (usable / not usable) once we have
29675 enough directory information. This was causing us to always pick
29676 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
29677 causing us to discard all our guards on startup if we hadn't been
29678 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
29679 - Purge old entries from the "rephist" database and the hidden
29680 service descriptor databases even when DirPort is zero. Bugfix
29682 - We were ignoring our RelayBandwidthRate for the first 30 seconds
29683 after opening a circuit -- even a relayed circuit. Bugfix on
29685 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
29686 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
29687 crashing or mis-answering these types of requests.
29688 - Relays were publishing their server descriptor to v1 and v2
29689 directory authorities, but they didn't try publishing to v3-only
29690 authorities. Fix this; and also stop publishing to v1 authorities.
29692 - When we were reading router descriptors from cache, we were ignoring
29693 the annotations -- so for example we were reading in bridge-purpose
29694 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
29695 - When we decided to send a 503 response to a request for servers, we
29696 were then also sending the server descriptors: this defeats the
29697 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
29700 - Bridge relays now behave like clients with respect to time
29701 intervals for downloading new consensus documents -- otherwise they
29702 stand out. Bridge users now wait until the end of the interval,
29703 so their bridge relay will be sure to have a new consensus document.
29704 - Three new config options (AlternateDirAuthority,
29705 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
29706 user selectively replace the default directory authorities by type,
29707 rather than the all-or-nothing replacement that DirServer offers.
29708 - Tor can now be configured to read a GeoIP file from disk in one
29709 of two formats. This can be used by controllers to map IP addresses
29710 to countries. Eventually, it may support exit-by-country.
29711 - When possible, bridge relays remember which countries users
29712 are coming from, and report aggregate information in their
29713 extra-info documents, so that the bridge authorities can learn
29714 where Tor is blocked.
29715 - Bridge directory authorities now do reachability testing on the
29716 bridges they know. They provide router status summaries to the
29717 controller via "getinfo ns/purpose/bridge", and also dump summaries
29718 to a file periodically.
29719 - Stop fetching directory info so aggressively if your DirPort is
29720 on but your ORPort is off; stop fetching v2 dir info entirely.
29721 You can override these choices with the new FetchDirInfoEarly
29725 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
29726 consensus documents when there are too many relays at a single
29727 IP address. Now clear it in v2 network status documents too, and
29728 also clear it in routerinfo_t when the relay is no longer listed
29729 in the relevant networkstatus document.
29730 - Don't crash if we get an unexpected value for the
29731 PublishServerDescriptor config option. Reported by Matt Edman;
29732 bugfix on 0.2.0.9-alpha.
29733 - Our new v2 hidden service descriptor format allows descriptors
29734 that have no introduction points. But Tor crashed when we tried
29735 to build a descriptor with no intro points (and it would have
29736 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
29737 by Karsten Loesing.
29738 - Fix building with dmalloc 5.5.2 with glibc.
29739 - Reject uploaded descriptors and extrainfo documents if they're
29740 huge. Otherwise we'll cache them all over the network and it'll
29741 clog everything up. Reported by Aljosha Judmayer.
29742 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
29743 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
29744 - When the DANGEROUS_VERSION controller status event told us we're
29745 running an obsolete version, it used the string "OLD" to describe
29746 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
29747 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
29748 - If we can't expand our list of entry guards (e.g. because we're
29749 using bridges or we have StrictEntryNodes set), don't mark relays
29750 down when they fail a directory request. Otherwise we're too quick
29751 to mark all our entry points down. Bugfix on 0.1.2.x.
29752 - Fix handling of hex nicknames when answering controller requests for
29753 networkstatus by name, or when deciding whether to warn about unknown
29754 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
29755 - Fix a couple of hard-to-trigger autoconf problems that could result
29756 in really weird results on platforms whose sys/types.h files define
29757 nonstandard integer types. Bugfix on 0.1.2.x.
29758 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
29759 - Don't crash on name lookup when we have no current consensus. Fixes
29760 bug 538; bugfix on 0.2.0.x.
29761 - Only Tors that want to mirror the v2 directory info should
29762 create the "cached-status" directory in their datadir. (All Tors
29763 used to create it.) Bugfix on 0.2.0.9-alpha.
29764 - Directory authorities should only automatically download Extra Info
29765 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
29768 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
29769 consumers. (We already do this on HUP.)
29770 - Authorities and caches fetch the v2 networkstatus documents
29771 less often, now that v3 is encouraged.
29772 - Add a new config option BridgeRelay that specifies you want to
29773 be a bridge relay. Right now the only difference is that it makes
29774 you answer begin_dir requests, and it makes you cache dir info,
29775 even if your DirPort isn't on.
29776 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
29777 ask about source, timestamp of arrival, purpose, etc. We need
29778 something like this to help Vidalia not do GeoIP lookups on bridge
29780 - Allow multiple HashedControlPassword config lines, to support
29781 multiple controller passwords.
29782 - Authorities now decide whether they're authoritative for a given
29783 router based on the router's purpose.
29784 - New config options AuthDirBadDir and AuthDirListBadDirs for
29785 authorities to mark certain relays as "bad directories" in the
29786 networkstatus documents. Also supports the "!baddir" directive in
29787 the approved-routers file.
29790 Changes in version 0.2.0.12-alpha - 2007-11-16
29791 This twelfth development snapshot fixes some more build problems as
29792 well as a few minor bugs.
29795 - Make it build on OpenBSD again. Patch from tup.
29796 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
29797 package-building for Red Hat, OS X, etc.
29799 o Minor bugfixes (on 0.1.2.x):
29800 - Changing the ExitPolicyRejectPrivate setting should cause us to
29801 rebuild our server descriptor.
29803 o Minor bugfixes (on 0.2.0.x):
29804 - When we're lacking a consensus, don't try to perform rendezvous
29805 operations. Reported by Karsten Loesing.
29806 - Fix a small memory leak whenever we decide against using a
29807 newly picked entry guard. Reported by Mike Perry.
29808 - When authorities detected more than two relays running on the same
29809 IP address, they were clearing all the status flags but forgetting
29810 to clear the "hsdir" flag. So clients were being told that a
29811 given relay was the right choice for a v2 hsdir lookup, yet they
29812 never had its descriptor because it was marked as 'not running'
29814 - If we're trying to fetch a bridge descriptor and there's no way
29815 the bridge authority could help us (for example, we don't know
29816 a digest, or there is no bridge authority), don't be so eager to
29817 fall back to asking the bridge authority.
29818 - If we're using bridges or have strictentrynodes set, and our
29819 chosen exit is in the same family as all our bridges/entry guards,
29820 then be flexible about families.
29823 - When we negotiate a v2 link-layer connection (not yet implemented),
29824 accept RELAY_EARLY cells and turn them into RELAY cells if we've
29825 negotiated a v1 connection for their next step. Initial code for
29829 Changes in version 0.2.0.11-alpha - 2007-11-12
29830 This eleventh development snapshot fixes some build problems with
29831 the previous snapshot. It also includes a more secure-by-default exit
29832 policy for relays, fixes an enormous memory leak for exit relays, and
29833 fixes another bug where servers were falling out of the directory list.
29836 - Exit policies now reject connections that are addressed to a
29837 relay's public (external) IP address too, unless
29838 ExitPolicyRejectPrivate is turned off. We do this because too
29839 many relays are running nearby to services that trust them based
29840 on network address. Bugfix on 0.1.2.x.
29843 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
29844 on every successful resolve. Reported by Mike Perry; bugfix
29846 - On authorities, never downgrade to old router descriptors simply
29847 because they're listed in the consensus. This created a catch-22
29848 where we wouldn't list a new descriptor because there was an
29849 old one in the consensus, and we couldn't get the new one in the
29850 consensus because we wouldn't list it. Possible fix for bug 548.
29851 Also, this might cause bug 543 to appear on authorities; if so,
29852 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
29854 o Packaging fixes on 0.2.0.10-alpha:
29855 - We were including instructions about what to do with the
29856 src/config/fallback-consensus file, but we weren't actually
29857 including it in the tarball. Disable all of that for now.
29860 - Allow people to say PreferTunnelledDirConns rather than
29861 PreferTunneledDirConns, for those alternate-spellers out there.
29864 - Don't reevaluate all the information from our consensus document
29865 just because we've downloaded a v2 networkstatus that we intend
29866 to cache. Fixes bug 545; bugfix on 0.2.0.x.
29869 Changes in version 0.2.0.10-alpha - 2007-11-10
29870 This tenth development snapshot adds a third v3 directory authority
29871 run by Mike Perry, adds most of Karsten Loesing's new hidden service
29872 descriptor format, fixes a bad crash bug and new bridge bugs introduced
29873 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
29874 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
29875 addresses many more minor issues.
29877 o New directory authorities:
29878 - Set up ides (run by Mike Perry) as the third v3 directory authority.
29881 - Allow tunnelled directory connections to ask for an encrypted
29882 "begin_dir" connection or an anonymized "uses a full Tor circuit"
29883 connection independently. Now we can make anonymized begin_dir
29884 connections for (e.g.) more secure hidden service posting and
29886 - More progress on proposal 114: code from Karsten Loesing to
29887 implement new hidden service descriptor format.
29888 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
29889 accommodate the growing number of servers that use the default
29890 and are reaching it.
29891 - Directory authorities use a new formula for selecting which nodes
29892 to advertise as Guards: they must be in the top 7/8 in terms of
29893 how long we have known about them, and above the median of those
29894 nodes in terms of weighted fractional uptime.
29895 - Make "not enough dir info yet" warnings describe *why* Tor feels
29896 it doesn't have enough directory info yet.
29899 - Stop servers from crashing if they set a Family option (or
29900 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
29902 - Make bridge users work again -- the move to v3 directories in
29903 0.2.0.9-alpha had introduced a number of bugs that made bridges
29904 no longer work for clients.
29905 - When the clock jumps forward a lot, do not allow the bandwidth
29906 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
29908 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
29909 - When the consensus lists a router descriptor that we previously were
29910 mirroring, but that we considered non-canonical, reload the
29911 descriptor as canonical. This fixes bug 543 where Tor servers
29912 would start complaining after a few days that they don't have
29913 enough directory information to build a circuit.
29914 - Consider replacing the current consensus when certificates arrive
29915 that make the pending consensus valid. Previously, we were only
29916 considering replacement when the new certs _didn't_ help.
29917 - Fix an assert error on startup if we didn't already have the
29918 consensus and certs cached in our datadirectory: we were caching
29919 the consensus in consensus_waiting_for_certs but then free'ing it
29921 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
29922 Request) if we need more v3 certs but we've already got pending
29923 requests for all of them.
29924 - Correctly back off from failing certificate downloads. Fixes
29926 - Authorities don't vote on the Running flag if they have been running
29927 for less than 30 minutes themselves. Fixes bug 547, where a newly
29928 started authority would vote that everyone was down.
29930 o New requirements:
29931 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
29932 it, it had no AES, and it hasn't seen any security patches since
29936 - Clients now hold circuitless TLS connections open for 1.5 times
29937 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
29938 rebuild a new circuit over them within that timeframe. Previously,
29939 they held them open only for KeepalivePeriod (5 minutes).
29940 - Use "If-Modified-Since" to avoid retrieving consensus
29941 networkstatuses that we already have.
29942 - When we have no consensus, check FallbackNetworkstatusFile (defaults
29943 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
29944 we start knowing some directory caches.
29945 - When we receive a consensus from the future, warn about skew.
29946 - Improve skew reporting: try to give the user a better log message
29947 about how skewed they are, and how much this matters.
29948 - When we have a certificate for an authority, believe that
29949 certificate's claims about the authority's IP address.
29950 - New --quiet command-line option to suppress the default console log.
29951 Good in combination with --hash-password.
29952 - Authorities send back an X-Descriptor-Not-New header in response to
29953 an accepted-but-discarded descriptor upload. Partially implements
29955 - Make the log message for "tls error. breaking." more useful.
29956 - Better log messages about certificate downloads, to attempt to
29957 track down the second incarnation of bug 546.
29959 o Minor features (bridges):
29960 - If bridge users set UpdateBridgesFromAuthority, but the digest
29961 they ask for is a 404 from the bridge authority, they now fall
29962 back to trying the bridge directly.
29963 - Bridges now use begin_dir to publish their server descriptor to
29964 the bridge authority, even when they haven't set TunnelDirConns.
29966 o Minor features (controller):
29967 - When reporting clock skew, and we know that the clock is _at least
29968 as skewed_ as some value, but we don't know the actual value,
29969 report the value as a "minimum skew."
29972 - Update linux-tor-prio.sh script to allow QoS based on the uid of
29973 the Tor process. Patch from Marco Bonetti with tweaks from Mike
29977 - Refuse to start if both ORPort and UseBridges are set. Bugfix
29978 on 0.2.0.x, suggested by Matt Edman.
29979 - Don't stop fetching descriptors when FetchUselessDescriptors is
29980 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
29981 reported by tup and ioerror.
29982 - Better log message on vote from unknown authority.
29983 - Don't log "Launching 0 request for 0 router" message.
29985 o Minor bugfixes (memory leaks):
29986 - Stop leaking memory every time we parse a v3 certificate. Bugfix
29988 - Stop leaking memory every time we load a v3 certificate. Bugfix
29989 on 0.2.0.1-alpha. Fixes bug 536.
29990 - Stop leaking a cached networkstatus on exit. Bugfix on
29992 - Stop leaking voter information every time we free a consensus.
29993 Bugfix on 0.2.0.3-alpha.
29994 - Stop leaking signed data every time we check a voter signature.
29995 Bugfix on 0.2.0.3-alpha.
29996 - Stop leaking a signature every time we fail to parse a consensus or
29997 a vote. Bugfix on 0.2.0.3-alpha.
29998 - Stop leaking v2_download_status_map on shutdown. Bugfix on
30000 - Stop leaking conn->nickname every time we make a connection to a
30001 Tor relay without knowing its expected identity digest (e.g. when
30002 using bridges). Bugfix on 0.2.0.3-alpha.
30004 - Minor bugfixes (portability):
30005 - Run correctly on platforms where rlim_t is larger than unsigned
30006 long, and/or where the real limit for number of open files is
30007 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
30008 particular, these may be needed for OS X 10.5.
30011 Changes in version 0.1.2.18 - 2007-10-28
30012 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
30013 hidden service introduction that were causing huge delays, and a big
30014 bug that was causing some servers to disappear from the network status
30015 lists for a few hours each day.
30017 o Major bugfixes (crashes):
30018 - If a connection is shut down abruptly because of something that
30019 happened inside connection_flushed_some(), do not call
30020 connection_finished_flushing(). Should fix bug 451:
30021 "connection_stop_writing: Assertion conn->write_event failed"
30022 Bugfix on 0.1.2.7-alpha.
30023 - Fix possible segfaults in functions called from
30024 rend_process_relay_cell().
30026 o Major bugfixes (hidden services):
30027 - Hidden services were choosing introduction points uniquely by
30028 hexdigest, but when constructing the hidden service descriptor
30029 they merely wrote the (potentially ambiguous) nickname.
30030 - Clients now use the v2 intro format for hidden service
30031 connections: they specify their chosen rendezvous point by identity
30032 digest rather than by (potentially ambiguous) nickname. These
30033 changes could speed up hidden service connections dramatically.
30035 o Major bugfixes (other):
30036 - Stop publishing a new server descriptor just because we get a
30037 HUP signal. This led (in a roundabout way) to some servers getting
30038 dropped from the networkstatus lists for a few hours each day.
30039 - When looking for a circuit to cannibalize, consider family as well
30040 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30041 circuit cannibalization).
30042 - When a router wasn't listed in a new networkstatus, we were leaving
30043 the flags for that router alone -- meaning it remained Named,
30044 Running, etc -- even though absence from the networkstatus means
30045 that it shouldn't be considered to exist at all anymore. Now we
30046 clear all the flags for routers that fall out of the networkstatus
30047 consensus. Fixes bug 529.
30050 - Don't try to access (or alter) the state file when running
30051 --list-fingerprint or --verify-config or --hash-password. Resolves
30053 - When generating information telling us how to extend to a given
30054 router, do not try to include the nickname if it is
30055 absent. Resolves bug 467.
30056 - Fix a user-triggerable segfault in expand_filename(). (There isn't
30057 a way to trigger this remotely.)
30058 - When sending a status event to the controller telling it that an
30059 OR address is reachable, set the port correctly. (Previously we
30060 were reporting the dir port.)
30061 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30062 command. Bugfix on 0.1.2.17.
30063 - When loading bandwidth history, do not believe any information in
30064 the future. Fixes bug 434.
30065 - When loading entry guard information, do not believe any information
30067 - When we have our clock set far in the future and generate an
30068 onion key, then re-set our clock to be correct, we should not stop
30069 the onion key from getting rotated.
30070 - On some platforms, accept() can return a broken address. Detect
30071 this more quietly, and deal accordingly. Fixes bug 483.
30072 - It's not actually an error to find a non-pending entry in the DNS
30073 cache when canceling a pending resolve. Don't log unless stuff
30074 is fishy. Resolves bug 463.
30075 - Don't reset trusted dir server list when we set a configuration
30076 option. Patch from Robert Hogan.
30077 - Don't try to create the datadir when running --verify-config or
30078 --hash-password. Resolves bug 540.
30081 Changes in version 0.2.0.9-alpha - 2007-10-24
30082 This ninth development snapshot switches clients to the new v3 directory
30083 system; allows servers to be listed in the network status even when they
30084 have the same nickname as a registered server; and fixes many other
30085 bugs including a big one that was causing some servers to disappear
30086 from the network status lists for a few hours each day.
30088 o Major features (directory system):
30089 - Clients now download v3 consensus networkstatus documents instead
30090 of v2 networkstatus documents. Clients and caches now base their
30091 opinions about routers on these consensus documents. Clients only
30092 download router descriptors listed in the consensus.
30093 - Authorities now list servers who have the same nickname as
30094 a different named server, but list them with a new flag,
30095 "Unnamed". Now we can list servers that happen to pick the same
30096 nickname as a server that registered two years ago and then
30097 disappeared. Partially implements proposal 122.
30098 - If the consensus lists a router as "Unnamed", the name is assigned
30099 to a different router: do not identify the router by that name.
30100 Partially implements proposal 122.
30101 - Authorities can now come to a consensus on which method to use to
30102 compute the consensus. This gives us forward compatibility.
30105 - Stop publishing a new server descriptor just because we HUP or
30106 when we find our DirPort to be reachable but won't actually publish
30107 it. New descriptors without any real changes are dropped by the
30108 authorities, and can screw up our "publish every 18 hours" schedule.
30110 - When a router wasn't listed in a new networkstatus, we were leaving
30111 the flags for that router alone -- meaning it remained Named,
30112 Running, etc -- even though absence from the networkstatus means
30113 that it shouldn't be considered to exist at all anymore. Now we
30114 clear all the flags for routers that fall out of the networkstatus
30115 consensus. Fixes bug 529; bugfix on 0.1.2.x.
30116 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
30117 extrainfo documents and then discard them immediately for not
30118 matching the latest router. Bugfix on 0.2.0.1-alpha.
30120 o Minor features (v3 directory protocol):
30121 - Allow tor-gencert to generate a new certificate without replacing
30123 - Allow certificates to include an address.
30124 - When we change our directory-cache settings, reschedule all voting
30125 and download operations.
30126 - Reattempt certificate downloads immediately on failure, as long as
30127 we haven't failed a threshold number of times yet.
30128 - Delay retrying consensus downloads while we're downloading
30129 certificates to verify the one we just got. Also, count getting a
30130 consensus that we already have (or one that isn't valid) as a failure,
30131 and count failing to get the certificates after 20 minutes as a
30133 - Build circuits and download descriptors even if our consensus is a
30134 little expired. (This feature will go away once authorities are
30137 o Minor features (router descriptor cache):
30138 - If we find a cached-routers file that's been sitting around for more
30139 than 28 days unmodified, then most likely it's a leftover from
30140 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
30142 - When we (as a cache) download a descriptor because it was listed
30143 in a consensus, remember when the consensus was supposed to expire,
30144 and don't expire the descriptor until then.
30146 o Minor features (performance):
30147 - Call routerlist_remove_old_routers() much less often. This should
30148 speed startup, especially on directory caches.
30149 - Don't try to launch new descriptor downloads quite so often when we
30150 already have enough directory information to build circuits.
30151 - Base64 decoding was actually showing up on our profile when parsing
30152 the initial descriptor file; switch to an in-process all-at-once
30153 implementation that's about 3.5x times faster than calling out to
30156 o Minor features (compilation):
30157 - Detect non-ASCII platforms (if any still exist) and refuse to
30158 build there: some of our code assumes that 'A' is 65 and so on.
30160 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
30161 - Make the "next period" votes into "current period" votes immediately
30162 after publishing the consensus; avoid a heisenbug that made them
30163 stick around indefinitely.
30164 - When we discard a vote as a duplicate, do not report this as
30166 - Treat missing v3 keys or certificates as an error when running as a
30167 v3 directory authority.
30168 - When we're configured to be a v3 authority, but we're only listed
30169 as a non-v3 authority in our DirServer line for ourself, correct
30171 - If an authority doesn't have a qualified hostname, just put
30172 its address in the vote. This fixes the problem where we referred to
30173 "moria on moria:9031."
30174 - Distinguish between detached signatures for the wrong period, and
30175 detached signatures for a divergent vote.
30176 - Fix a small memory leak when computing a consensus.
30177 - When there's no consensus, we were forming a vote every 30
30178 minutes, but writing the "valid-after" line in our vote based
30179 on our configured V3AuthVotingInterval: so unless the intervals
30180 matched up, we immediately rejected our own vote because it didn't
30181 start at the voting interval that caused us to construct a vote.
30183 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
30184 - Delete unverified-consensus when the real consensus is set.
30185 - Consider retrying a consensus networkstatus fetch immediately
30186 after one fails: don't wait 60 seconds to notice.
30187 - When fetching a consensus as a cache, wait until a newer consensus
30188 should exist before trying to replace the current one.
30189 - Use a more forgiving schedule for retrying failed consensus
30190 downloads than for other types.
30192 o Minor bugfixes (other directory issues):
30193 - Correct the implementation of "download votes by digest." Bugfix on
30195 - Authorities no longer send back "400 you're unreachable please fix
30196 it" errors to Tor servers that aren't online all the time. We're
30197 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
30199 o Minor bugfixes (controller):
30200 - Don't reset trusted dir server list when we set a configuration
30201 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
30202 - Respond to INT and TERM SIGNAL commands before we execute the
30203 signal, in case the signal shuts us down. We had a patch in
30204 0.1.2.1-alpha that tried to do this by queueing the response on
30205 the connection's buffer before shutting down, but that really
30206 isn't the same thing at all. Bug located by Matt Edman.
30208 o Minor bugfixes (misc):
30209 - Correctly check for bad options to the "PublishServerDescriptor"
30210 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
30211 - Stop leaking memory on failing case of base32_decode, and make
30212 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
30213 - Don't try to download extrainfo documents when we're trying to
30214 fetch enough directory info to build a circuit: having enough
30215 info should get priority. Bugfix on 0.2.0.x.
30216 - Don't complain that "your server has not managed to confirm that its
30217 ports are reachable" if we haven't been able to build any circuits
30218 yet. Bug found by spending four hours without a v3 consensus. Bugfix
30220 - Detect the reason for failing to mmap a descriptor file we just
30221 wrote, and give a more useful log message. Fixes bug 533. Bugfix
30224 o Code simplifications and refactoring:
30225 - Remove support for the old bw_accounting file: we've been storing
30226 bandwidth accounting information in the state file since
30227 0.1.2.5-alpha. This may result in bandwidth accounting errors
30228 if you try to upgrade from 0.1.1.x or earlier, or if you try to
30229 downgrade to 0.1.1.x or earlier.
30230 - New convenience code to locate a file within the DataDirectory.
30231 - Move non-authority functionality out of dirvote.c.
30232 - Refactor the arguments for router_pick_{directory_|trusteddir}server
30233 so that they all take the same named flags.
30236 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
30237 Unix users an easy way to script their Tor process (e.g. by
30238 adjusting bandwidth based on the time of the day).
30241 Changes in version 0.2.0.8-alpha - 2007-10-12
30242 This eighth development snapshot fixes a crash bug that's been bothering
30243 us since February 2007, lets bridge authorities store a list of bridge
30244 descriptors they've seen, gets v3 directory voting closer to working,
30245 starts caching v3 directory consensus documents on directory mirrors,
30246 and fixes a variety of smaller issues including some minor memory leaks.
30248 o Major features (router descriptor cache):
30249 - Store routers in a file called cached-descriptors instead of in
30250 cached-routers. Initialize cached-descriptors from cached-routers
30251 if the old format is around. The new format allows us to store
30252 annotations along with descriptors.
30253 - Use annotations to record the time we received each descriptor, its
30254 source, and its purpose.
30255 - Disable the SETROUTERPURPOSE controller command: it is now
30257 - Controllers should now specify cache=no or cache=yes when using
30258 the +POSTDESCRIPTOR command.
30259 - Bridge authorities now write bridge descriptors to disk, meaning
30260 we can export them to other programs and begin distributing them
30263 o Major features (directory authorities):
30264 - When a v3 authority is missing votes or signatures, it now tries
30266 - Directory authorities track weighted fractional uptime as well as
30267 weighted mean-time-between failures. WFU is suitable for deciding
30268 whether a node is "usually up", while MTBF is suitable for deciding
30269 whether a node is "likely to stay up." We need both, because
30270 "usually up" is a good requirement for guards, while "likely to
30271 stay up" is a good requirement for long-lived connections.
30273 o Major features (v3 directory system):
30274 - Caches now download v3 network status documents as needed,
30275 and download the descriptors listed in them.
30276 - All hosts now attempt to download and keep fresh v3 authority
30277 certificates, and re-attempt after failures.
30278 - More internal-consistency checks for vote parsing.
30280 o Major bugfixes (crashes):
30281 - If a connection is shut down abruptly because of something that
30282 happened inside connection_flushed_some(), do not call
30283 connection_finished_flushing(). Should fix bug 451. Bugfix on
30286 o Major bugfixes (performance):
30287 - Fix really bad O(n^2) performance when parsing a long list of
30288 routers: Instead of searching the entire list for an "extra-info "
30289 string which usually wasn't there, once for every routerinfo
30290 we read, just scan lines forward until we find one we like.
30292 - When we add data to a write buffer in response to the data on that
30293 write buffer getting low because of a flush, do not consider the
30294 newly added data as a candidate for immediate flushing, but rather
30295 make it wait until the next round of writing. Otherwise, we flush
30296 and refill recursively, and a single greedy TLS connection can
30297 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
30299 o Minor features (v3 authority system):
30300 - Add more ways for tools to download the votes that lead to the
30302 - Send a 503 when low on bandwidth and a vote, consensus, or
30303 certificate is requested.
30304 - If-modified-since is now implemented properly for all kinds of
30305 certificate requests.
30307 o Minor bugfixes (network statuses):
30308 - Tweak the implementation of proposal 109 slightly: allow at most
30309 two Tor servers on the same IP address, except if it's the location
30310 of a directory authority, in which case allow five. Bugfix on
30313 o Minor bugfixes (controller):
30314 - When sending a status event to the controller telling it that an
30315 OR address is reachable, set the port correctly. (Previously we
30316 were reporting the dir port.) Bugfix on 0.1.2.x.
30318 o Minor bugfixes (v3 directory system):
30319 - Fix logic to look up a cert by its signing key digest. Bugfix on
30321 - Only change the reply to a vote to "OK" if it's not already
30322 set. This gets rid of annoying "400 OK" log messages, which may
30323 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
30324 - When we get a valid consensus, recompute the voting schedule.
30325 - Base the valid-after time of a vote on the consensus voting
30326 schedule, not on our preferred schedule.
30327 - Make the return values and messages from signature uploads and
30328 downloads more sensible.
30329 - Fix a memory leak when serving votes and consensus documents, and
30330 another when serving certificates.
30332 o Minor bugfixes (performance):
30333 - Use a slightly simpler string hashing algorithm (copying Python's
30334 instead of Java's) and optimize our digest hashing algorithm to take
30335 advantage of 64-bit platforms and to remove some possibly-costly
30337 - Fix a minor memory leak whenever we parse guards from our state
30338 file. Bugfix on 0.2.0.7-alpha.
30339 - Fix a minor memory leak whenever we write out a file. Bugfix on
30341 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30342 command. Bugfix on 0.2.0.5-alpha.
30344 o Minor bugfixes (portability):
30345 - On some platforms, accept() can return a broken address. Detect
30346 this more quietly, and deal accordingly. Fixes bug 483.
30347 - Stop calling tor_strlower() on uninitialized memory in some cases.
30348 Bugfix in 0.2.0.7-alpha.
30350 o Minor bugfixes (usability):
30351 - Treat some 403 responses from directory servers as INFO rather than
30352 WARN-severity events.
30353 - It's not actually an error to find a non-pending entry in the DNS
30354 cache when canceling a pending resolve. Don't log unless stuff is
30355 fishy. Resolves bug 463.
30357 o Minor bugfixes (anonymity):
30358 - Never report that we've used more bandwidth than we're willing to
30359 relay: it leaks how much non-relay traffic we're using. Resolves
30361 - When looking for a circuit to cannibalize, consider family as well
30362 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30363 circuit cannibalization).
30365 o Code simplifications and refactoring:
30366 - Make a bunch of functions static. Remove some dead code.
30367 - Pull out about a third of the really big routerlist.c; put it in a
30368 new module, networkstatus.c.
30369 - Merge the extra fields in local_routerstatus_t back into
30370 routerstatus_t: we used to need one routerstatus_t for each
30371 authority's opinion, plus a local_routerstatus_t for the locally
30372 computed consensus opinion. To save space, we put the locally
30373 modified fields into local_routerstatus_t, and only the common
30374 stuff into routerstatus_t. But once v3 directories are in use,
30375 clients and caches will no longer need to hold authority opinions;
30376 thus, the rationale for keeping the types separate is now gone.
30377 - Make the code used to reschedule and reattempt downloads more
30379 - Turn all 'Are we a directory server/mirror?' logic into a call to
30381 - Remove the code to generate the oldest (v1) directory format.
30382 The code has been disabled since 0.2.0.5-alpha.
30385 Changes in version 0.2.0.7-alpha - 2007-09-21
30386 This seventh development snapshot makes bridges work again, makes bridge
30387 authorities work for the first time, fixes two huge performance flaws
30388 in hidden services, and fixes a variety of minor issues.
30390 o New directory authorities:
30391 - Set up moria1 and tor26 as the first v3 directory authorities. See
30392 doc/spec/dir-spec.txt for details on the new directory design.
30394 o Major bugfixes (crashes):
30395 - Fix possible segfaults in functions called from
30396 rend_process_relay_cell(). Bugfix on 0.1.2.x.
30398 o Major bugfixes (bridges):
30399 - Fix a bug that made servers send a "404 Not found" in response to
30400 attempts to fetch their server descriptor. This caused Tor servers
30401 to take many minutes to establish reachability for their DirPort,
30402 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
30403 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
30404 users configure that and specify a bridge with an identity
30405 fingerprint, now they will lookup the bridge descriptor at the
30406 default bridge authority via a one-hop tunnel, but once circuits
30407 are established they will switch to a three-hop tunnel for later
30408 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
30410 o Major bugfixes (hidden services):
30411 - Hidden services were choosing introduction points uniquely by
30412 hexdigest, but when constructing the hidden service descriptor
30413 they merely wrote the (potentially ambiguous) nickname.
30414 - Clients now use the v2 intro format for hidden service
30415 connections: they specify their chosen rendezvous point by identity
30416 digest rather than by (potentially ambiguous) nickname. Both
30417 are bugfixes on 0.1.2.x, and they could speed up hidden service
30418 connections dramatically. Thanks to Karsten Loesing.
30420 o Minor features (security):
30421 - As a client, do not believe any server that tells us that an
30422 address maps to an internal address space.
30423 - Make it possible to enable HashedControlPassword and
30424 CookieAuthentication at the same time.
30426 o Minor features (guard nodes):
30427 - Tag every guard node in our state file with the version that
30428 we believe added it, or with our own version if we add it. This way,
30429 if a user temporarily runs an old version of Tor and then switches
30430 back to a new one, she doesn't automatically lose her guards.
30432 o Minor features (speed):
30433 - When implementing AES counter mode, update only the portions of the
30434 counter buffer that need to change, and don't keep separate
30435 network-order and host-order counters when they are the same (i.e.,
30436 on big-endian hosts.)
30438 o Minor features (controller):
30439 - Accept LF instead of CRLF on controller, since some software has a
30440 hard time generating real Internet newlines.
30441 - Add GETINFO values for the server status events
30442 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
30445 o Removed features:
30446 - Routers no longer include bandwidth-history lines in their
30447 descriptors; this information is already available in extra-info
30448 documents, and including it in router descriptors took up 60%
30449 (!) of compressed router descriptor downloads. Completes
30450 implementation of proposal 104.
30451 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
30452 and TorControl.py, as they use the old v0 controller protocol,
30453 and are obsoleted by TorFlow anyway.
30454 - Drop support for v1 rendezvous descriptors, since we never used
30455 them anyway, and the code has probably rotted by now. Based on
30456 patch from Karsten Loesing.
30457 - On OSX, stop warning the user that kqueue support in libevent is
30458 "experimental", since it seems to have worked fine for ages.
30461 - When generating information telling us how to extend to a given
30462 router, do not try to include the nickname if it is absent. Fixes
30463 bug 467. Bugfix on 0.2.0.3-alpha.
30464 - Fix a user-triggerable (but not remotely-triggerable) segfault
30465 in expand_filename(). Bugfix on 0.1.2.x.
30466 - Fix a memory leak when freeing incomplete requests from DNSPort.
30467 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
30468 - Don't try to access (or alter) the state file when running
30469 --list-fingerprint or --verify-config or --hash-password. (Resolves
30470 bug 499.) Bugfix on 0.1.2.x.
30471 - Servers used to decline to publish their DirPort if their
30472 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
30473 were below a threshold. Now they only look at BandwidthRate and
30474 RelayBandwidthRate. Bugfix on 0.1.2.x.
30475 - Remove an optimization in the AES counter-mode code that assumed
30476 that the counter never exceeded 2^68. When the counter can be set
30477 arbitrarily as an IV (as it is by Karsten's new hidden services
30478 code), this assumption no longer holds. Bugfix on 0.1.2.x.
30479 - Resume listing "AUTHORITY" flag for authorities in network status.
30480 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
30482 o Code simplifications and refactoring:
30483 - Revamp file-writing logic so we don't need to have the entire
30484 contents of a file in memory at once before we write to disk. Tor,
30486 - Turn "descriptor store" into a full-fledged type.
30487 - Move all NT services code into a separate source file.
30488 - Unify all code that computes medians, percentile elements, etc.
30489 - Get rid of a needless malloc when parsing address policies.
30492 Changes in version 0.1.2.17 - 2007-08-30
30493 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
30494 X bundles. Vidalia 0.0.14 makes authentication required for the
30495 ControlPort in the default configuration, which addresses important
30496 security risks. Everybody who uses Vidalia (or another controller)
30499 In addition, this Tor update fixes major load balancing problems with
30500 path selection, which should speed things up a lot once many people
30503 o Major bugfixes (security):
30504 - We removed support for the old (v0) control protocol. It has been
30505 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
30506 become more of a headache than it's worth.
30508 o Major bugfixes (load balancing):
30509 - When choosing nodes for non-guard positions, weight guards
30510 proportionally less, since they already have enough load. Patch
30512 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
30513 will allow fast Tor servers to get more attention.
30514 - When we're upgrading from an old Tor version, forget our current
30515 guards and pick new ones according to the new weightings. These
30516 three load balancing patches could raise effective network capacity
30517 by a factor of four. Thanks to Mike Perry for measurements.
30519 o Major bugfixes (stream expiration):
30520 - Expire not-yet-successful application streams in all cases if
30521 they've been around longer than SocksTimeout. Right now there are
30522 some cases where the stream will live forever, demanding a new
30523 circuit every 15 seconds. Fixes bug 454; reported by lodger.
30525 o Minor features (controller):
30526 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
30527 is valid before any authentication has been received. It tells
30528 a controller what kind of authentication is expected, and what
30529 protocol is spoken. Implements proposal 119.
30531 o Minor bugfixes (performance):
30532 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
30533 greatly speeding up loading cached-routers from disk on startup.
30534 - Disable sentinel-based debugging for buffer code: we squashed all
30535 the bugs that this was supposed to detect a long time ago, and now
30536 its only effect is to change our buffer sizes from nice powers of
30537 two (which platform mallocs tend to like) to values slightly over
30538 powers of two (which make some platform mallocs sad).
30540 o Minor bugfixes (misc):
30541 - If exit bandwidth ever exceeds one third of total bandwidth, then
30542 use the correct formula to weight exit nodes when choosing paths.
30543 Based on patch from Mike Perry.
30544 - Choose perfectly fairly among routers when choosing by bandwidth and
30545 weighting by fraction of bandwidth provided by exits. Previously, we
30546 would choose with only approximate fairness, and correct ourselves
30547 if we ran off the end of the list.
30548 - If we require CookieAuthentication but we fail to write the
30549 cookie file, we would warn but not exit, and end up in a state
30550 where no controller could authenticate. Now we exit.
30551 - If we require CookieAuthentication, stop generating a new cookie
30552 every time we change any piece of our config.
30553 - Refuse to start with certain directory authority keys, and
30554 encourage people using them to stop.
30555 - Terminate multi-line control events properly. Original patch
30557 - Fix a minor memory leak when we fail to find enough suitable
30558 servers to choose a circuit.
30559 - Stop leaking part of the descriptor when we run into a particularly
30560 unparseable piece of it.
30563 Changes in version 0.2.0.6-alpha - 2007-08-26
30564 This sixth development snapshot features a new Vidalia version in the
30565 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
30566 the ControlPort in the default configuration, which addresses important
30569 In addition, this snapshot fixes major load balancing problems
30570 with path selection, which should speed things up a lot once many
30571 people have upgraded. The directory authorities also use a new
30572 mean-time-between-failure approach to tracking which servers are stable,
30573 rather than just looking at the most recent uptime.
30575 o New directory authorities:
30576 - Set up Tonga as the default bridge directory authority.
30579 - Directory authorities now track servers by weighted
30580 mean-times-between-failures. When we have 4 or more days of data,
30581 use measured MTBF rather than declared uptime to decide whether
30582 to call a router Stable. Implements proposal 108.
30584 o Major bugfixes (load balancing):
30585 - When choosing nodes for non-guard positions, weight guards
30586 proportionally less, since they already have enough load. Patch
30588 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
30589 will allow fast Tor servers to get more attention.
30590 - When we're upgrading from an old Tor version, forget our current
30591 guards and pick new ones according to the new weightings. These
30592 three load balancing patches could raise effective network capacity
30593 by a factor of four. Thanks to Mike Perry for measurements.
30595 o Major bugfixes (descriptor parsing):
30596 - Handle unexpected whitespace better in malformed descriptors. Bug
30597 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
30600 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
30601 GETINFO for Torstat to use until it can switch to using extrainfos.
30602 - Optionally (if built with -DEXPORTMALLINFO) export the output
30603 of mallinfo via http, as tor/mallinfo.txt. Only accessible
30607 - Do not intermix bridge routers with controller-added
30608 routers. (Bugfix on 0.2.0.x)
30609 - Do not fail with an assert when accept() returns an unexpected
30610 address family. Addresses but does not wholly fix bug 483. (Bugfix
30612 - Let directory authorities startup even when they can't generate
30613 a descriptor immediately, e.g. because they don't know their
30615 - Stop putting the authentication cookie in a file called "0"
30616 in your working directory if you don't specify anything for the
30617 new CookieAuthFile option. Reported by Matt Edman.
30618 - Make it possible to read the PROTOCOLINFO response in a way that
30619 conforms to our control-spec. Reported by Matt Edman.
30620 - Fix a minor memory leak when we fail to find enough suitable
30621 servers to choose a circuit. Bugfix on 0.1.2.x.
30622 - Stop leaking part of the descriptor when we run into a particularly
30623 unparseable piece of it. Bugfix on 0.1.2.x.
30624 - Unmap the extrainfo cache file on exit.
30627 Changes in version 0.2.0.5-alpha - 2007-08-19
30628 This fifth development snapshot fixes compilation on Windows again;
30629 fixes an obnoxious client-side bug that slowed things down and put
30630 extra load on the network; gets us closer to using the v3 directory
30631 voting scheme; makes it easier for Tor controllers to use cookie-based
30632 authentication; and fixes a variety of other bugs.
30634 o Removed features:
30635 - Version 1 directories are no longer generated in full. Instead,
30636 authorities generate and serve "stub" v1 directories that list
30637 no servers. This will stop Tor versions 0.1.0.x and earlier from
30638 working, but (for security reasons) nobody should be running those
30641 o Major bugfixes (compilation, 0.2.0.x):
30642 - Try to fix Win32 compilation again: improve checking for IPv6 types.
30643 - Try to fix MSVC compilation: build correctly on platforms that do
30644 not define s6_addr16 or s6_addr32.
30645 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
30648 o Major bugfixes (stream expiration):
30649 - Expire not-yet-successful application streams in all cases if
30650 they've been around longer than SocksTimeout. Right now there are
30651 some cases where the stream will live forever, demanding a new
30652 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
30653 reported by lodger.
30655 o Minor features (directory servers):
30656 - When somebody requests a list of statuses or servers, and we have
30657 none of those, return a 404 rather than an empty 200.
30659 o Minor features (directory voting):
30660 - Store v3 consensus status consensuses on disk, and reload them
30663 o Minor features (security):
30664 - Warn about unsafe ControlPort configurations.
30665 - Refuse to start with certain directory authority keys, and
30666 encourage people using them to stop.
30668 o Minor features (controller):
30669 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
30670 is valid before any authentication has been received. It tells
30671 a controller what kind of authentication is expected, and what
30672 protocol is spoken. Implements proposal 119.
30673 - New config option CookieAuthFile to choose a new location for the
30674 cookie authentication file, and config option
30675 CookieAuthFileGroupReadable to make it group-readable.
30677 o Minor features (unit testing):
30678 - Add command-line arguments to unit-test executable so that we can
30679 invoke any chosen test from the command line rather than having
30680 to run the whole test suite at once; and so that we can turn on
30681 logging for the unit tests.
30683 o Minor bugfixes (on 0.1.2.x):
30684 - If we require CookieAuthentication but we fail to write the
30685 cookie file, we would warn but not exit, and end up in a state
30686 where no controller could authenticate. Now we exit.
30687 - If we require CookieAuthentication, stop generating a new cookie
30688 every time we change any piece of our config.
30689 - When loading bandwidth history, do not believe any information in
30690 the future. Fixes bug 434.
30691 - When loading entry guard information, do not believe any information
30693 - When we have our clock set far in the future and generate an
30694 onion key, then re-set our clock to be correct, we should not stop
30695 the onion key from getting rotated.
30696 - Clean up torrc sample config file.
30697 - Do not automatically run configure from autogen.sh. This
30698 non-standard behavior tended to annoy people who have built other
30701 o Minor bugfixes (on 0.2.0.x):
30702 - Fix a bug with AutomapHostsOnResolve that would always cause
30703 the second request to fail. Bug reported by Kate. Bugfix on
30705 - Fix a bug in ADDRMAP controller replies that would sometimes
30706 try to print a NULL. Patch from tup.
30707 - Read v3 directory authority keys from the right location.
30708 - Numerous bugfixes to directory voting code.
30711 Changes in version 0.1.2.16 - 2007-08-01
30712 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
30713 remote attacker in certain situations to rewrite the user's torrc
30714 configuration file. This can completely compromise anonymity of users
30715 in most configurations, including those running the Vidalia bundles,
30716 TorK, etc. Or worse.
30718 o Major security fixes:
30719 - Close immediately after missing authentication on control port;
30720 do not allow multiple authentication attempts.
30723 Changes in version 0.2.0.4-alpha - 2007-08-01
30724 This fourth development snapshot fixes a critical security vulnerability
30725 for most users, specifically those running Vidalia, TorK, etc. Everybody
30726 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
30728 o Major security fixes:
30729 - Close immediately after missing authentication on control port;
30730 do not allow multiple authentication attempts.
30732 o Major bugfixes (compilation):
30733 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
30736 o Minor features (performance):
30737 - Be even more aggressive about releasing RAM from small
30738 empty buffers. Thanks to our free-list code, this shouldn't be too
30739 performance-intensive.
30740 - Disable sentinel-based debugging for buffer code: we squashed all
30741 the bugs that this was supposed to detect a long time ago, and
30742 now its only effect is to change our buffer sizes from nice
30743 powers of two (which platform mallocs tend to like) to values
30744 slightly over powers of two (which make some platform mallocs sad).
30745 - Log malloc statistics from mallinfo() on platforms where it
30749 Changes in version 0.2.0.3-alpha - 2007-07-29
30750 This third development snapshot introduces new experimental
30751 blocking-resistance features and a preliminary version of the v3
30752 directory voting design, and includes many other smaller features
30756 - The first pieces of our "bridge" design for blocking-resistance
30757 are implemented. People can run bridge directory authorities;
30758 people can run bridges; and people can configure their Tor clients
30759 with a set of bridges to use as the first hop into the Tor network.
30760 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
30762 - Create listener connections before we setuid to the configured
30763 User and Group. Now non-Windows users can choose port values
30764 under 1024, start Tor as root, and have Tor bind those ports
30765 before it changes to another UID. (Windows users could already
30767 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
30768 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
30769 on "vserver" accounts. (Patch from coderman.)
30770 - Be even more aggressive about separating local traffic from relayed
30771 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
30773 o Major features (experimental):
30774 - First cut of code for "v3 dir voting": directory authorities will
30775 vote on a common network status document rather than each publishing
30776 their own opinion. This code needs more testing and more corner-case
30777 handling before it's ready for use.
30780 - Directory authorities now call routers Fast if their bandwidth is
30781 at least 100KB/s, and consider their bandwidth adequate to be a
30782 Guard if it is at least 250KB/s, no matter the medians. This fix
30783 complements proposal 107. [Bugfix on 0.1.2.x]
30784 - Directory authorities now never mark more than 3 servers per IP as
30785 Valid and Running. (Implements proposal 109, by Kevin Bauer and
30787 - Minor change to organizationName and commonName generation
30788 procedures in TLS certificates during Tor handshakes, to invalidate
30789 some earlier censorware approaches. This is not a long-term
30790 solution, but applying it will give us a bit of time to look into
30791 the epidemiology of countermeasures as they spread.
30793 o Major bugfixes (directory):
30794 - Rewrite directory tokenization code to never run off the end of
30795 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
30797 o Minor features (controller):
30798 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
30799 match requests to applications. (Patch from Robert Hogan.)
30800 - Report address and port correctly on connections to DNSPort. (Patch
30801 from Robert Hogan.)
30802 - Add a RESOLVE command to launch hostname lookups. (Original patch
30803 from Robert Hogan.)
30804 - Add GETINFO status/enough-dir-info to let controllers tell whether
30805 Tor has downloaded sufficient directory information. (Patch
30807 - You can now use the ControlSocket option to tell Tor to listen for
30808 controller connections on Unix domain sockets on systems that
30809 support them. (Patch from Peter Palfrader.)
30810 - STREAM NEW events are generated for DNSPort requests and for
30811 tunneled directory connections. (Patch from Robert Hogan.)
30812 - New "GETINFO address-mappings/*" command to get address mappings
30813 with expiry information. "addr-mappings/*" is now deprecated.
30816 o Minor features (misc):
30817 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
30819 - The tor-gencert tool for v3 directory authorities now creates all
30820 files as readable to the file creator only, and write-protects
30821 the authority identity key.
30822 - When dumping memory usage, list bytes used in buffer memory
30824 - When running with dmalloc, dump more stats on hup and on exit.
30825 - Directory authorities now fail quickly and (relatively) harmlessly
30826 if they generate a network status document that is somehow
30829 o Traffic load balancing improvements:
30830 - If exit bandwidth ever exceeds one third of total bandwidth, then
30831 use the correct formula to weight exit nodes when choosing paths.
30832 (Based on patch from Mike Perry.)
30833 - Choose perfectly fairly among routers when choosing by bandwidth and
30834 weighting by fraction of bandwidth provided by exits. Previously, we
30835 would choose with only approximate fairness, and correct ourselves
30836 if we ran off the end of the list. [Bugfix on 0.1.2.x]
30838 o Performance improvements:
30839 - Be more aggressive with freeing buffer RAM or putting it on the
30841 - Use Critical Sections rather than Mutexes for synchronizing threads
30842 on win32; Mutexes are heavier-weight, and designed for synchronizing
30845 o Deprecated and removed features:
30846 - RedirectExits is now deprecated.
30847 - Stop allowing address masks that do not correspond to bit prefixes.
30848 We have warned about these for a really long time; now it's time
30849 to reject them. (Patch from croup.)
30851 o Minor bugfixes (directory):
30852 - Fix another crash bug related to extra-info caching. (Bug found by
30853 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
30854 - Directories no longer return a "304 not modified" when they don't
30855 have the networkstatus the client asked for. Also fix a memory
30856 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
30857 - We had accidentally labelled 0.1.2.x directory servers as not
30858 suitable for begin_dir requests, and had labelled no directory
30859 servers as suitable for uploading extra-info documents. [Bugfix
30862 o Minor bugfixes (dns):
30863 - Fix a crash when DNSPort is set more than once. (Patch from Robert
30864 Hogan.) [Bugfix on 0.2.0.2-alpha]
30865 - Add DNSPort connections to the global connection list, so that we
30866 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
30868 - Fix a dangling reference that could lead to a crash when DNSPort is
30869 changed or closed (Patch from Robert Hogan.) [Bugfix on
30872 o Minor bugfixes (controller):
30873 - Provide DNS expiry times in GMT, not in local time. For backward
30874 compatibility, ADDRMAP events only provide GMT expiry in an extended
30875 field. "GETINFO address-mappings" always does the right thing.
30876 - Use CRLF line endings properly in NS events.
30877 - Terminate multi-line control events properly. (Original patch
30878 from tup.) [Bugfix on 0.1.2.x-alpha]
30879 - Do not include spaces in SOURCE_ADDR fields in STREAM
30880 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
30883 Changes in version 0.1.2.15 - 2007-07-17
30884 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
30885 problems, fixes compilation on BSD, and fixes a variety of other
30886 bugs. Everybody should upgrade.
30888 o Major bugfixes (compilation):
30889 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
30891 o Major bugfixes (crashes):
30892 - Try even harder not to dereference the first character after
30893 an mmap(). Reported by lodger.
30894 - Fix a crash bug in directory authorities when we re-number the
30895 routerlist while inserting a new router.
30896 - When the cached-routers file is an even multiple of the page size,
30897 don't run off the end and crash. (Fixes bug 455; based on idea
30899 - Fix eventdns.c behavior on Solaris: It is critical to include
30900 orconfig.h _before_ sys/types.h, so that we can get the expected
30901 definition of _FILE_OFFSET_BITS.
30903 o Major bugfixes (security):
30904 - Fix a possible buffer overrun when using BSD natd support. Bug
30906 - When sending destroy cells from a circuit's origin, don't include
30907 the reason for tearing down the circuit. The spec says we didn't,
30908 and now we actually don't. Reported by lodger.
30909 - Keep streamids from different exits on a circuit separate. This
30910 bug may have allowed other routers on a given circuit to inject
30911 cells into streams. Reported by lodger; fixes bug 446.
30912 - If there's a never-before-connected-to guard node in our list,
30913 never choose any guards past it. This way we don't expand our
30914 guard list unless we need to.
30916 o Minor bugfixes (guard nodes):
30917 - Weight guard selection by bandwidth, so that low-bandwidth nodes
30918 don't get overused as guards.
30920 o Minor bugfixes (directory):
30921 - Correctly count the number of authorities that recommend each
30922 version. Previously, we were under-counting by 1.
30923 - Fix a potential crash bug when we load many server descriptors at
30924 once and some of them make others of them obsolete. Fixes bug 458.
30926 o Minor bugfixes (hidden services):
30927 - Stop tearing down the whole circuit when the user asks for a
30928 connection to a port that the hidden service didn't configure.
30931 o Minor bugfixes (misc):
30932 - On Windows, we were preventing other processes from reading
30933 cached-routers while Tor was running. Reported by janbar.
30934 - Fix a possible (but very unlikely) bug in picking routers by
30935 bandwidth. Add a log message to confirm that it is in fact
30936 unlikely. Patch from lodger.
30937 - Backport a couple of memory leak fixes.
30938 - Backport miscellaneous cosmetic bugfixes.
30941 Changes in version 0.2.0.2-alpha - 2007-06-02
30942 o Major bugfixes on 0.2.0.1-alpha:
30943 - Fix an assertion failure related to servers without extra-info digests.
30944 Resolves bugs 441 and 442.
30946 o Minor features (directory):
30947 - Support "If-Modified-Since" when answering HTTP requests for
30948 directories, running-routers documents, and network-status documents.
30949 (There's no need to support it for router descriptors, since those
30950 are downloaded by descriptor digest.)
30952 o Minor build issues:
30953 - Clear up some MIPSPro compiler warnings.
30954 - When building from a tarball on a machine that happens to have SVK
30955 installed, report the micro-revision as whatever version existed
30956 in the tarball, not as "x".
30959 Changes in version 0.2.0.1-alpha - 2007-06-01
30960 This early development snapshot provides new features for people running
30961 Tor as both a client and a server (check out the new RelayBandwidth
30962 config options); lets Tor run as a DNS proxy; and generally moves us
30963 forward on a lot of fronts.
30965 o Major features, server usability:
30966 - New config options RelayBandwidthRate and RelayBandwidthBurst:
30967 a separate set of token buckets for relayed traffic. Right now
30968 relayed traffic is defined as answers to directory requests, and
30969 OR connections that don't have any local circuits on them.
30971 o Major features, client usability:
30972 - A client-side DNS proxy feature to replace the need for
30973 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
30974 for DNS requests on port 9999, use the Tor network to resolve them
30975 anonymously, and send the reply back like a regular DNS server.
30976 The code still only implements a subset of DNS.
30977 - Make PreferTunneledDirConns and TunnelDirConns work even when
30978 we have no cached directory info. This means Tor clients can now
30979 do all of their connections protected by TLS.
30981 o Major features, performance and efficiency:
30982 - Directory authorities accept and serve "extra info" documents for
30983 routers. These documents contain fields from router descriptors
30984 that aren't usually needed, and that use a lot of excess
30985 bandwidth. Once these fields are removed from router descriptors,
30986 the bandwidth savings should be about 60%. [Partially implements
30988 - Servers upload extra-info documents to any authority that accepts
30989 them. Authorities (and caches that have been configured to download
30990 extra-info documents) download them as needed. [Partially implements
30992 - Change the way that Tor buffers data that it is waiting to write.
30993 Instead of queueing data cells in an enormous ring buffer for each
30994 client->OR or OR->OR connection, we now queue cells on a separate
30995 queue for each circuit. This lets us use less slack memory, and
30996 will eventually let us be smarter about prioritizing different kinds
30998 - Use memory pools to allocate cells with better speed and memory
30999 efficiency, especially on platforms where malloc() is inefficient.
31000 - Stop reading on edge connections when their corresponding circuit
31001 buffers are full; start again as the circuits empty out.
31003 o Major features, other:
31004 - Add an HSAuthorityRecordStats option that hidden service authorities
31005 can use to track statistics of overall hidden service usage without
31006 logging information that would be very useful to an attacker.
31007 - Start work implementing multi-level keys for directory authorities:
31008 Add a standalone tool to generate key certificates. (Proposal 103.)
31011 - Directory authorities now call routers Stable if they have an
31012 uptime of at least 30 days, even if that's not the median uptime
31013 in the network. Implements proposal 107, suggested by Kevin Bauer
31016 o Minor fixes (resource management):
31017 - Count the number of open sockets separately from the number
31018 of active connection_t objects. This will let us avoid underusing
31019 our allocated connection limit.
31020 - We no longer use socket pairs to link an edge connection to an
31021 anonymous directory connection or a DirPort test connection.
31022 Instead, we track the link internally and transfer the data
31023 in-process. This saves two sockets per "linked" connection (at the
31024 client and at the server), and avoids the nasty Windows socketpair()
31026 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
31027 for every single inactive connection_t. Free items from the
31028 4k/16k-buffer free lists when they haven't been used for a while.
31030 o Minor features (build):
31031 - Make autoconf search for libevent, openssl, and zlib consistently.
31032 - Update deprecated macros in configure.in.
31033 - When warning about missing headers, tell the user to let us
31034 know if the compile succeeds anyway, so we can downgrade the
31036 - Include the current subversion revision as part of the version
31037 string: either fetch it directly if we're in an SVN checkout, do
31038 some magic to guess it if we're in an SVK checkout, or use
31039 the last-detected version if we're building from a .tar.gz.
31040 Use this version consistently in log messages.
31042 o Minor features (logging):
31043 - Always prepend "Bug: " to any log message about a bug.
31044 - Put a platform string (e.g. "Linux i686") in the startup log
31045 message, so when people paste just their logs, we know if it's
31046 OpenBSD or Windows or what.
31047 - When logging memory usage, break down memory used in buffers by
31050 o Minor features (directory system):
31051 - New config option V2AuthoritativeDirectory that all directory
31052 authorities should set. This will let future authorities choose
31053 not to serve V2 directory information.
31054 - Directory authorities allow multiple router descriptors and/or extra
31055 info documents to be uploaded in a single go. This will make
31056 implementing proposal 104 simpler.
31058 o Minor features (controller):
31059 - Add a new config option __DisablePredictedCircuits designed for
31060 use by the controller, when we don't want Tor to build any circuits
31062 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
31063 so we can exit from the middle of the circuit.
31064 - Implement "getinfo status/circuit-established".
31065 - Implement "getinfo status/version/..." so a controller can tell
31066 whether the current version is recommended, and whether any versions
31067 are good, and how many authorities agree. (Patch from shibz.)
31069 o Minor features (hidden services):
31070 - Allow multiple HiddenServicePort directives with the same virtual
31071 port; when they occur, the user is sent round-robin to one
31072 of the target ports chosen at random. Partially fixes bug 393 by
31073 adding limited ad-hoc round-robining.
31075 o Minor features (other):
31077 - Add a new AutomapHostsOnResolve option: when it is enabled, any
31078 resolve request for hosts matching a given pattern causes Tor to
31079 generate an internal virtual address mapping for that host. This
31080 allows DNSPort to work sensibly with hidden service users. By
31081 default, .exit and .onion addresses are remapped; the list of
31082 patterns can be reconfigured with AutomapHostsSuffixes.
31083 - Add an "-F" option to tor-resolve to force a resolve for a .onion
31084 address. Thanks to the AutomapHostsOnResolve option, this is no
31085 longer a completely silly thing to do.
31086 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
31087 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
31088 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
31089 minus 1 byte: the actual maximum declared bandwidth.
31091 o Removed features:
31092 - Removed support for the old binary "version 0" controller protocol.
31093 This has been deprecated since 0.1.1, and warnings have been issued
31094 since 0.1.2. When we encounter a v0 control message, we now send
31095 back an error and close the connection.
31096 - Remove the old "dns worker" server DNS code: it hasn't been default
31097 since 0.1.2.2-alpha, and all the servers seem to be using the new
31100 o Minor bugfixes (portability):
31101 - Even though Windows is equally happy with / and \ as path separators,
31102 try to use \ consistently on Windows and / consistently on Unix: it
31103 makes the log messages nicer.
31104 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
31105 - Read resolv.conf files correctly on platforms where read() returns
31106 partial results on small file reads.
31108 o Minor bugfixes (directory):
31109 - Correctly enforce that elements of directory objects do not appear
31110 more often than they are allowed to appear.
31111 - When we are reporting the DirServer line we just parsed, we were
31112 logging the second stanza of the key fingerprint, not the first.
31114 o Minor bugfixes (logging):
31115 - When we hit an EOF on a log (probably because we're shutting down),
31116 don't try to remove the log from the list: just mark it as
31117 unusable. (Bulletproofs against bug 222.)
31119 o Minor bugfixes (other):
31120 - In the exitlist script, only consider the most recently published
31121 server descriptor for each server. Also, when the user requests
31122 a list of servers that _reject_ connections to a given address,
31123 explicitly exclude the IPs that also have servers that accept
31124 connections to that address. (Resolves bug 405.)
31125 - Stop allowing hibernating servers to be "stable" or "fast".
31126 - On Windows, we were preventing other processes from reading
31127 cached-routers while Tor was running. (Reported by janbar)
31128 - Make the NodeFamilies config option work. (Reported by
31129 lodger -- it has never actually worked, even though we added it
31131 - Check return values from pthread_mutex functions.
31132 - Don't save non-general-purpose router descriptors to the disk cache,
31133 because we have no way of remembering what their purpose was when
31135 - Add even more asserts to hunt down bug 417.
31136 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
31137 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
31138 Add a log message to confirm that it is in fact unlikely.
31140 o Minor bugfixes (controller):
31141 - Make 'getinfo fingerprint' return a 551 error if we're not a
31142 server, so we match what the control spec claims we do. Reported
31144 - Fix a typo in an error message when extendcircuit fails that
31145 caused us to not follow the \r\n-based delimiter protocol. Reported
31148 o Code simplifications and refactoring:
31149 - Stop passing around circuit_t and crypt_path_t pointers that are
31150 implicit in other procedure arguments.
31151 - Drop the old code to choke directory connections when the
31152 corresponding OR connections got full: thanks to the cell queue
31153 feature, OR conns don't get full any more.
31154 - Make dns_resolve() handle attaching connections to circuits
31155 properly, so the caller doesn't have to.
31156 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
31157 - Keep the connection array as a dynamic smartlist_t, rather than as
31158 a fixed-sized array. This is important, as the number of connections
31159 is becoming increasingly decoupled from the number of sockets.
31162 Changes in version 0.1.2.14 - 2007-05-25
31163 Tor 0.1.2.14 changes the addresses of two directory authorities (this
31164 change especially affects those who serve or use hidden services),
31165 and fixes several other crash- and security-related bugs.
31167 o Directory authority changes:
31168 - Two directory authorities (moria1 and moria2) just moved to new
31169 IP addresses. This change will particularly affect those who serve
31170 or use hidden services.
31172 o Major bugfixes (crashes):
31173 - If a directory server runs out of space in the connection table
31174 as it's processing a begin_dir request, it will free the exit stream
31175 but leave it attached to the circuit, leading to unpredictable
31176 behavior. (Reported by seeess, fixes bug 425.)
31177 - Fix a bug in dirserv_remove_invalid() that would cause authorities
31178 to corrupt memory under some really unlikely scenarios.
31179 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
31180 - Avoid segfaults when reading from mmaped descriptor file. (Reported
31183 o Major bugfixes (security):
31184 - When choosing an entry guard for a circuit, avoid using guards
31185 that are in the same family as the chosen exit -- not just guards
31186 that are exactly the chosen exit. (Reported by lodger.)
31188 o Major bugfixes (resource management):
31189 - If a directory authority is down, skip it when deciding where to get
31190 networkstatus objects or descriptors. Otherwise we keep asking
31191 every 10 seconds forever. Fixes bug 384.
31192 - Count it as a failure if we fetch a valid network-status but we
31193 don't want to keep it. Otherwise we'll keep fetching it and keep
31194 not wanting to keep it. Fixes part of bug 422.
31195 - If all of our dirservers have given us bad or no networkstatuses
31196 lately, then stop hammering them once per minute even when we
31197 think they're failed. Fixes another part of bug 422.
31200 - Actually set the purpose correctly for descriptors inserted with
31201 purpose=controller.
31202 - When we have k non-v2 authorities in our DirServer config,
31203 we ignored the last k authorities in the list when updating our
31205 - Correctly back-off from requesting router descriptors that we are
31206 having a hard time downloading.
31207 - Read resolv.conf files correctly on platforms where read() returns
31208 partial results on small file reads.
31209 - Don't rebuild the entire router store every time we get 32K of
31210 routers: rebuild it when the journal gets very large, or when
31211 the gaps in the store get very large.
31214 - When routers publish SVN revisions in their router descriptors,
31215 authorities now include those versions correctly in networkstatus
31217 - Warn when using a version of libevent before 1.3b to run a server on
31218 OSX or BSD: these versions interact badly with userspace threads.
31221 Changes in version 0.1.2.13 - 2007-04-24
31222 This release features some major anonymity fixes, such as safer path
31223 selection; better client performance; faster bootstrapping, better
31224 address detection, and better DNS support for servers; write limiting as
31225 well as read limiting to make servers easier to run; and a huge pile of
31226 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
31228 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
31229 of the Freenode IRC network, remembering his patience and vision for
31230 free speech on the Internet.
31233 - Fix a memory leak when we ask for "all" networkstatuses and we
31234 get one we don't recognize.
31235 - Add more asserts to hunt down bug 417.
31236 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
31239 Changes in version 0.1.2.12-rc - 2007-03-16
31241 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
31242 directory information requested inside Tor connections (i.e. via
31243 begin_dir cells). It only triggered when the same connection was
31244 serving other data at the same time. Reported by seeess.
31247 - When creating a circuit via the controller, send a 'launched'
31248 event when we're done, so we follow the spec better.
31251 Changes in version 0.1.2.11-rc - 2007-03-15
31252 o Minor bugfixes (controller), reported by daejees:
31253 - Correct the control spec to match how the code actually responds
31254 to 'getinfo addr-mappings/*'.
31255 - The control spec described a GUARDS event, but the code
31256 implemented a GUARD event. Standardize on GUARD, but let people
31257 ask for GUARDS too.
31260 Changes in version 0.1.2.10-rc - 2007-03-07
31261 o Major bugfixes (Windows):
31262 - Do not load the NT services library functions (which may not exist)
31263 just to detect if we're a service trying to shut down. Now we run
31264 on Win98 and friends again.
31266 o Minor bugfixes (other):
31267 - Clarify a couple of log messages.
31268 - Fix a misleading socks5 error number.
31271 Changes in version 0.1.2.9-rc - 2007-03-02
31272 o Major bugfixes (Windows):
31273 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
31274 of the usual GCC "%llu". This prevents a bug when saving 64-bit
31275 int configuration values: the high-order 32 bits would get
31276 truncated. In particular, we were being bitten by the default
31277 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
31278 and maybe also bug 397.)
31280 o Minor bugfixes (performance):
31281 - Use OpenSSL's AES implementation on platforms where it's faster.
31282 This could save us as much as 10% CPU usage.
31284 o Minor bugfixes (server):
31285 - Do not rotate onion key immediately after setting it for the first
31288 o Minor bugfixes (directory authorities):
31289 - Stop calling servers that have been hibernating for a long time
31290 "stable". Also, stop letting hibernating or obsolete servers affect
31291 uptime and bandwidth cutoffs.
31292 - Stop listing hibernating servers in the v1 directory.
31294 o Minor bugfixes (hidden services):
31295 - Upload hidden service descriptors slightly less often, to reduce
31296 load on authorities.
31298 o Minor bugfixes (other):
31299 - Fix an assert that could trigger if a controller quickly set then
31300 cleared EntryNodes. Bug found by Udo van den Heuvel.
31301 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
31303 - Fix a potential race condition in the rpm installer. Found by
31305 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
31306 of 2 as indicating that the server is completely bad; it sometimes
31307 means that the server is just bad for the request in question. (may fix
31308 the last of bug 326.)
31309 - Disable encrypted directory connections when we don't have a server
31310 descriptor for the destination. We'll get this working again in
31314 Changes in version 0.1.2.8-beta - 2007-02-26
31315 o Major bugfixes (crashes):
31316 - Stop crashing when the controller asks us to resetconf more than
31317 one config option at once. (Vidalia 0.0.11 does this.)
31318 - Fix a crash that happened on Win98 when we're given command-line
31319 arguments: don't try to load NT service functions from advapi32.dll
31320 except when we need them. (Bug introduced in 0.1.2.7-alpha;
31322 - Fix a longstanding obscure crash bug that could occur when
31323 we run out of DNS worker processes. (Resolves bug 390.)
31325 o Major bugfixes (hidden services):
31326 - Correctly detect whether hidden service descriptor downloads are
31327 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
31329 o Major bugfixes (accounting):
31330 - When we start during an accounting interval before it's time to wake
31331 up, remember to wake up at the correct time. (May fix bug 342.)
31333 o Minor bugfixes (controller):
31334 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
31335 clear the corresponding on_circuit variable, and remember later
31336 that we don't need to send a redundant CLOSED event. Resolves part
31338 - Report events where a resolve succeeded or where we got a socks
31339 protocol error correctly, rather than calling both of them
31341 - Change reported stream target addresses to IP consistently when
31342 we finally get the IP from an exit node.
31343 - Send log messages to the controller even if they happen to be very
31346 o Minor bugfixes (other):
31347 - Display correct results when reporting which versions are
31348 recommended, and how recommended they are. (Resolves bug 383.)
31349 - Improve our estimates for directory bandwidth to be less random:
31350 guess that an unrecognized directory will have the average bandwidth
31351 from all known directories, not that it will have the average
31352 bandwidth from those directories earlier than it on the list.
31353 - If we start a server with ClientOnly 1, then set ClientOnly to 0
31354 and hup, stop triggering an assert based on an empty onion_key.
31355 - On platforms with no working mmap() equivalent, don't warn the
31356 user when cached-routers doesn't exist.
31357 - Warn the user when mmap() [or its equivalent] fails for some reason
31358 other than file-not-found.
31359 - Don't warn the user when cached-routers.new doesn't exist: that's
31360 perfectly fine when starting up for the first time.
31361 - When EntryNodes are configured, rebuild the guard list to contain,
31362 in order: the EntryNodes that were guards before; the rest of the
31363 EntryNodes; the nodes that were guards before.
31364 - Mask out all signals in sub-threads; only the libevent signal
31365 handler should be processing them. This should prevent some crashes
31366 on some machines using pthreads. (Patch from coderman.)
31367 - Fix switched arguments on memset in the implementation of
31368 tor_munmap() for systems with no mmap() call.
31369 - When Tor receives a router descriptor that it asked for, but
31370 no longer wants (because it has received fresh networkstatuses
31371 in the meantime), do not warn the user. Cache the descriptor if
31372 we're a cache; drop it if we aren't.
31373 - Make earlier entry guards _really_ get retried when the network
31375 - On a malformed DNS reply, always give an error to the corresponding
31377 - Build with recent libevents on platforms that do not define the
31378 nonstandard types "u_int8_t" and friends.
31380 o Minor features (controller):
31381 - Warn the user when an application uses the obsolete binary v0
31382 control protocol. We're planning to remove support for it during
31383 the next development series, so it's good to give people some
31385 - Add STREAM_BW events to report per-entry-stream bandwidth
31386 use. (Patch from Robert Hogan.)
31387 - Rate-limit SIGNEWNYM signals in response to controllers that
31388 impolitely generate them for every single stream. (Patch from
31389 mwenge; closes bug 394.)
31390 - Make REMAP stream events have a SOURCE (cache or exit), and
31391 make them generated in every case where we get a successful
31392 connected or resolved cell.
31394 o Minor bugfixes (performance):
31395 - Call router_have_min_dir_info half as often. (This is showing up in
31396 some profiles, but not others.)
31397 - When using GCC, make log_debug never get called at all, and its
31398 arguments never get evaluated, when no debug logs are configured.
31399 (This is showing up in some profiles, but not others.)
31402 - Remove some never-implemented options. Mark PathlenCoinWeight as
31404 - Implement proposal 106: Stop requiring clients to have well-formed
31405 certificates; stop checking nicknames in certificates. (Clients
31406 have certificates so that they can look like Tor servers, but in
31407 the future we might want to allow them to look like regular TLS
31408 clients instead. Nicknames in certificates serve no purpose other
31409 than making our protocol easier to recognize on the wire.)
31410 - Revise messages on handshake failure again to be even more clear about
31411 which are incoming connections and which are outgoing.
31412 - Discard any v1 directory info that's over 1 month old (for
31413 directories) or over 1 week old (for running-routers lists).
31414 - Do not warn when individual nodes in the configuration's EntryNodes,
31415 ExitNodes, etc are down: warn only when all possible nodes
31416 are down. (Fixes bug 348.)
31417 - Always remove expired routers and networkstatus docs before checking
31418 whether we have enough information to build circuits. (Fixes
31420 - Put a lower-bound on MaxAdvertisedBandwidth.
31423 Changes in version 0.1.2.7-alpha - 2007-02-06
31424 o Major bugfixes (rate limiting):
31425 - Servers decline directory requests much more aggressively when
31426 they're low on bandwidth. Otherwise they end up queueing more and
31427 more directory responses, which can't be good for latency.
31428 - But never refuse directory requests from local addresses.
31429 - Fix a memory leak when sending a 503 response for a networkstatus
31431 - Be willing to read or write on local connections (e.g. controller
31432 connections) even when the global rate limiting buckets are empty.
31433 - If our system clock jumps back in time, don't publish a negative
31434 uptime in the descriptor. Also, don't let the global rate limiting
31435 buckets go absurdly negative.
31436 - Flush local controller connection buffers periodically as we're
31437 writing to them, so we avoid queueing 4+ megabytes of data before
31440 o Major bugfixes (NT services):
31441 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
31442 command-line flag so that admins can override the default by saying
31443 "tor --service install --user "SomeUser"". This will not affect
31444 existing installed services. Also, warn the user that the service
31445 will look for its configuration file in the service user's
31446 %appdata% directory. (We can't do the 'hardwire the user's appdata
31447 directory' trick any more, since we may not have read access to that
31450 o Major bugfixes (other):
31451 - Previously, we would cache up to 16 old networkstatus documents
31452 indefinitely, if they came from nontrusted authorities. Now we
31453 discard them if they are more than 10 days old.
31454 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
31456 - Detect and reject malformed DNS responses containing circular
31458 - If exits are rare enough that we're not marking exits as guards,
31459 ignore exit bandwidth when we're deciding the required bandwidth
31461 - When we're handling a directory connection tunneled over Tor,
31462 don't fill up internal memory buffers with all the data we want
31463 to tunnel; instead, only add it if the OR connection that will
31464 eventually receive it has some room for it. (This can lead to
31465 slowdowns in tunneled dir connections; a better solution will have
31466 to wait for 0.2.0.)
31468 o Minor bugfixes (dns):
31469 - Add some defensive programming to eventdns.c in an attempt to catch
31470 possible memory-stomping bugs.
31471 - Detect and reject DNS replies containing IPv4 or IPv6 records with
31472 an incorrect number of bytes. (Previously, we would ignore the
31474 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
31475 in the correct order, and doesn't crash.
31476 - Free memory held in recently-completed DNS lookup attempts on exit.
31477 This was not a memory leak, but may have been hiding memory leaks.
31478 - Handle TTL values correctly on reverse DNS lookups.
31479 - Treat failure to parse resolv.conf as an error.
31481 o Minor bugfixes (other):
31482 - Fix crash with "tor --list-fingerprint" (reported by seeess).
31483 - When computing clock skew from directory HTTP headers, consider what
31484 time it was when we finished asking for the directory, not what
31486 - Expire socks connections if they spend too long waiting for the
31487 handshake to finish. Previously we would let them sit around for
31488 days, if the connecting application didn't close them either.
31489 - And if the socks handshake hasn't started, don't send a
31490 "DNS resolve socks failed" handshake reply; just close it.
31491 - Stop using C functions that OpenBSD's linker doesn't like.
31492 - Don't launch requests for descriptors unless we have networkstatuses
31493 from at least half of the authorities. This delays the first
31494 download slightly under pathological circumstances, but can prevent
31495 us from downloading a bunch of descriptors we don't need.
31496 - Do not log IPs with TLS failures for incoming TLS
31497 connections. (Fixes bug 382.)
31498 - If the user asks to use invalid exit nodes, be willing to use
31500 - Stop using the reserved ac_cv namespace in our configure script.
31501 - Call stat() slightly less often; use fstat() when possible.
31502 - Refactor the way we handle pending circuits when an OR connection
31503 completes or fails, in an attempt to fix a rare crash bug.
31504 - Only rewrite a conn's address based on X-Forwarded-For: headers
31505 if it's a parseable public IP address; and stop adding extra quotes
31506 to the resulting address.
31509 - Weight directory requests by advertised bandwidth. Now we can
31510 let servers enable write limiting but still allow most clients to
31511 succeed at their directory requests. (We still ignore weights when
31512 choosing a directory authority; I hope this is a feature.)
31515 - Create a new file ReleaseNotes which was the old ChangeLog. The
31516 new ChangeLog file now includes the summaries for all development
31518 - Check for addresses with invalid characters at the exit as well
31519 as at the client, and warn less verbosely when they fail. You can
31520 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
31521 - Adapt a patch from goodell to let the contrib/exitlist script
31522 take arguments rather than require direct editing.
31523 - Inform the server operator when we decide not to advertise a
31524 DirPort due to AccountingMax enabled or a low BandwidthRate. It
31525 was confusing Zax, so now we're hopefully more helpful.
31526 - Bring us one step closer to being able to establish an encrypted
31527 directory tunnel without knowing a descriptor first. Still not
31528 ready yet. As part of the change, now assume we can use a
31529 create_fast cell if we don't know anything about a router.
31530 - Allow exit nodes to use nameservers running on ports other than 53.
31531 - Servers now cache reverse DNS replies.
31532 - Add an --ignore-missing-torrc command-line option so that we can
31533 get the "use sensible defaults if the configuration file doesn't
31534 exist" behavior even when specifying a torrc location on the command
31537 o Minor features (controller):
31538 - Track reasons for OR connection failure; make these reasons
31539 available via the controller interface. (Patch from Mike Perry.)
31540 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
31541 can learn when clients are sending malformed hostnames to Tor.
31542 - Clean up documentation for controller status events.
31543 - Add a REMAP status to stream events to note that a stream's
31544 address has changed because of a cached address or a MapAddress
31548 Changes in version 0.1.2.6-alpha - 2007-01-09
31550 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
31551 connection handles more than 4 gigs in either direction, we crash.
31552 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
31553 advertised exit node, somebody might try to exit from us when
31554 we're bootstrapping and before we've built our descriptor yet.
31555 Refuse the connection rather than crashing.
31558 - Warn if we (as a server) find that we've resolved an address that we
31559 weren't planning to resolve.
31560 - Warn that using select() on any libevent version before 1.1 will be
31561 unnecessarily slow (even for select()).
31562 - Flush ERR-level controller status events just like we currently
31563 flush ERR-level log events, so that a Tor shutdown doesn't prevent
31564 the controller from learning about current events.
31566 o Minor features (more controller status events):
31567 - Implement EXTERNAL_ADDRESS server status event so controllers can
31568 learn when our address changes.
31569 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
31570 can learn when directories reject our descriptor.
31571 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
31572 can learn when a client application is speaking a non-socks protocol
31574 - Implement DANGEROUS_SOCKS client status event so controllers
31575 can learn when a client application is leaking DNS addresses.
31576 - Implement BUG general status event so controllers can learn when
31577 Tor is unhappy about its internal invariants.
31578 - Implement CLOCK_SKEW general status event so controllers can learn
31579 when Tor thinks the system clock is set incorrectly.
31580 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
31581 server status events so controllers can learn when their descriptors
31582 are accepted by a directory.
31583 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
31584 server status events so controllers can learn about Tor's progress in
31585 deciding whether it's reachable from the outside.
31586 - Implement BAD_LIBEVENT general status event so controllers can learn
31587 when we have a version/method combination in libevent that needs to
31589 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
31590 and DNS_USELESS server status events so controllers can learn
31591 about changes to DNS server status.
31593 o Minor features (directory):
31594 - Authorities no longer recommend exits as guards if this would shift
31595 too much load to the exit nodes.
31598 Changes in version 0.1.2.5-alpha - 2007-01-06
31600 - Enable write limiting as well as read limiting. Now we sacrifice
31601 capacity if we're pushing out lots of directory traffic, rather
31602 than overrunning the user's intended bandwidth limits.
31603 - Include TLS overhead when counting bandwidth usage; previously, we
31604 would count only the bytes sent over TLS, but not the bytes used
31606 - Support running the Tor service with a torrc not in the same
31607 directory as tor.exe and default to using the torrc located in
31608 the %appdata%\Tor\ of the user who installed the service. Patch
31610 - Servers now check for the case when common DNS requests are going to
31611 wildcarded addresses (i.e. all getting the same answer), and change
31612 their exit policy to reject *:* if it's happening.
31613 - Implement BEGIN_DIR cells, so we can connect to the directory
31614 server via TLS to do encrypted directory requests rather than
31615 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
31616 config options if you like.
31618 o Minor features (config and docs):
31619 - Start using the state file to store bandwidth accounting data:
31620 the bw_accounting file is now obsolete. We'll keep generating it
31621 for a while for people who are still using 0.1.2.4-alpha.
31622 - Try to batch changes to the state file so that we do as few
31623 disk writes as possible while still storing important things in
31625 - The state file and the bw_accounting file get saved less often when
31626 the AvoidDiskWrites config option is set.
31627 - Make PIDFile work on Windows (untested).
31628 - Add internal descriptions for a bunch of configuration options:
31629 accessible via controller interface and in comments in saved
31631 - Reject *:563 (NNTPS) in the default exit policy. We already reject
31632 NNTP by default, so this seems like a sensible addition.
31633 - Clients now reject hostnames with invalid characters. This should
31634 avoid some inadvertent info leaks. Add an option
31635 AllowNonRFC953Hostnames to disable this behavior, in case somebody
31636 is running a private network with hosts called @, !, and #.
31637 - Add a maintainer script to tell us which options are missing
31638 documentation: "make check-docs".
31639 - Add a new address-spec.txt document to describe our special-case
31640 addresses: .exit, .onion, and .noconnnect.
31642 o Minor features (DNS):
31643 - Ongoing work on eventdns infrastructure: now it has dns server
31644 and ipv6 support. One day Tor will make use of it.
31645 - Add client-side caching for reverse DNS lookups.
31646 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
31647 - When we change nameservers or IP addresses, reset and re-launch
31648 our tests for DNS hijacking.
31650 o Minor features (directory):
31651 - Authorities now specify server versions in networkstatus. This adds
31652 about 2% to the size of compressed networkstatus docs, and allows
31653 clients to tell which servers support BEGIN_DIR and which don't.
31654 The implementation is forward-compatible with a proposed future
31655 protocol version scheme not tied to Tor versions.
31656 - DirServer configuration lines now have an orport= option so
31657 clients can open encrypted tunnels to the authorities without
31658 having downloaded their descriptors yet. Enabled for moria1,
31659 moria2, tor26, and lefkada now in the default configuration.
31660 - Directory servers are more willing to send a 503 "busy" if they
31661 are near their write limit, especially for v1 directory requests.
31662 Now they can use their limited bandwidth for actual Tor traffic.
31663 - Clients track responses with status 503 from dirservers. After a
31664 dirserver has given us a 503, we try not to use it until an hour has
31665 gone by, or until we have no dirservers that haven't given us a 503.
31666 - When we get a 503 from a directory, and we're not a server, we don't
31667 count the failure against the total number of failures allowed
31668 for the thing we're trying to download.
31669 - Report X-Your-Address-Is correctly from tunneled directory
31670 connections; don't report X-Your-Address-Is when it's an internal
31671 address; and never believe reported remote addresses when they're
31673 - Protect against an unlikely DoS attack on directory servers.
31674 - Add a BadDirectory flag to network status docs so that authorities
31675 can (eventually) tell clients about caches they believe to be
31678 o Minor features (controller):
31679 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
31680 - Reimplement GETINFO so that info/names stays in sync with the
31682 - Implement "GETINFO fingerprint".
31683 - Implement "SETEVENTS GUARD" so controllers can get updates on
31684 entry guard status as it changes.
31686 o Minor features (clean up obsolete pieces):
31687 - Remove some options that have been deprecated since at least
31688 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
31689 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
31690 to set log options.
31691 - We no longer look for identity and onion keys in "identity.key" and
31692 "onion.key" -- these were replaced by secret_id_key and
31693 secret_onion_key in 0.0.8pre1.
31694 - We no longer require unrecognized directory entries to be
31697 o Major bugfixes (security):
31698 - Stop sending the HttpProxyAuthenticator string to directory
31699 servers when directory connections are tunnelled through Tor.
31700 - Clients no longer store bandwidth history in the state file.
31701 - Do not log introduction points for hidden services if SafeLogging
31703 - When generating bandwidth history, round down to the nearest
31704 1k. When storing accounting data, round up to the nearest 1k.
31705 - When we're running as a server, remember when we last rotated onion
31706 keys, so that we will rotate keys once they're a week old even if
31707 we never stay up for a week ourselves.
31709 o Major bugfixes (other):
31710 - Fix a longstanding bug in eventdns that prevented the count of
31711 timed-out resolves from ever being reset. This bug caused us to
31712 give up on a nameserver the third time it timed out, and try it
31713 10 seconds later... and to give up on it every time it timed out
31715 - Take out the '5 second' timeout from the connection retry
31716 schedule. Now the first connect attempt will wait a full 10
31717 seconds before switching to a new circuit. Perhaps this will help
31718 a lot. Based on observations from Mike Perry.
31719 - Fix a bug on the Windows implementation of tor_mmap_file() that
31720 would prevent the cached-routers file from ever loading. Reported
31724 - Fix an assert failure when a directory authority sets
31725 AuthDirRejectUnlisted and then receives a descriptor from an
31726 unlisted router. Reported by seeess.
31727 - Avoid a double-free when parsing malformed DirServer lines.
31728 - Fix a bug when a BSD-style PF socket is first used. Patch from
31730 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
31731 to resolve an address at a given exit node even when they ask for
31733 - Servers no longer ever list themselves in their "family" line,
31734 even if configured to do so. This makes it easier to configure
31735 family lists conveniently.
31736 - When running as a server, don't fall back to 127.0.0.1 when no
31737 nameservers are configured in /etc/resolv.conf; instead, make the
31738 user fix resolv.conf or specify nameservers explicitly. (Resolves
31740 - Stop accepting certain malformed ports in configured exit policies.
31741 - Don't re-write the fingerprint file every restart, unless it has
31743 - Stop warning when a single nameserver fails: only warn when _all_ of
31744 our nameservers have failed. Also, when we only have one nameserver,
31745 raise the threshold for deciding that the nameserver is dead.
31746 - Directory authorities now only decide that routers are reachable
31747 if their identity keys are as expected.
31748 - When the user uses bad syntax in the Log config line, stop
31749 suggesting other bad syntax as a replacement.
31750 - Correctly detect ipv6 DNS capability on OpenBSD.
31752 o Minor bugfixes (controller):
31753 - Report the circuit number correctly in STREAM CLOSED events. Bug
31754 reported by Mike Perry.
31755 - Do not report bizarre values for results of accounting GETINFOs
31756 when the last second's write or read exceeds the allotted bandwidth.
31757 - Report "unrecognized key" rather than an empty string when the
31758 controller tries to fetch a networkstatus that doesn't exist.
31761 Changes in version 0.1.1.26 - 2006-12-14
31762 o Security bugfixes:
31763 - Stop sending the HttpProxyAuthenticator string to directory
31764 servers when directory connections are tunnelled through Tor.
31765 - Clients no longer store bandwidth history in the state file.
31766 - Do not log introduction points for hidden services if SafeLogging
31770 - Fix an assert failure when a directory authority sets
31771 AuthDirRejectUnlisted and then receives a descriptor from an
31772 unlisted router (reported by seeess).
31775 Changes in version 0.1.2.4-alpha - 2006-12-03
31777 - Add support for using natd; this allows FreeBSDs earlier than
31778 5.1.2 to have ipfw send connections through Tor without using
31779 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
31782 - Make all connections to addresses of the form ".noconnect"
31783 immediately get closed. This lets application/controller combos
31784 successfully test whether they're talking to the same Tor by
31785 watching for STREAM events.
31786 - Make cross.sh cross-compilation script work even when autogen.sh
31787 hasn't been run. (Patch from Michael Mohr.)
31788 - Statistics dumped by -USR2 now include a breakdown of public key
31789 operations, for profiling.
31792 - Fix a major leak when directory authorities parse their
31793 approved-routers list, a minor memory leak when we fail to pick
31794 an exit node, and a few rare leaks on errors.
31795 - Handle TransPort connections even when the server sends data before
31796 the client sends data. Previously, the connection would just hang
31797 until the client sent data. (Patch from tup based on patch from
31799 - Avoid assert failure when our cached-routers file is empty on
31803 - Don't log spurious warnings when we see a circuit close reason we
31804 don't recognize; it's probably just from a newer version of Tor.
31805 - Have directory authorities allow larger amounts of drift in uptime
31806 without replacing the server descriptor: previously, a server that
31807 restarted every 30 minutes could have 48 "interesting" descriptors
31809 - Start linking to the Tor specification and Tor reference manual
31810 correctly in the Windows installer.
31811 - Add Vidalia to the OS X uninstaller script, so when we uninstall
31812 Tor/Privoxy we also uninstall Vidalia.
31813 - Resume building on Irix64, and fix a lot of warnings from its
31814 MIPSpro C compiler.
31815 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
31816 when we're running as a client.
31819 Changes in version 0.1.1.25 - 2006-11-04
31821 - When a client asks us to resolve (rather than connect to)
31822 an address, and we have a cached answer, give them the cached
31823 answer. Previously, we would give them no answer at all.
31824 - We were building exactly the wrong circuits when we predict
31825 hidden service requirements, meaning Tor would have to build all
31826 its circuits on demand.
31827 - If none of our live entry guards have a high uptime, but we
31828 require a guard with a high uptime, try adding a new guard before
31829 we give up on the requirement. This patch should make long-lived
31830 connections more stable on average.
31831 - When testing reachability of our DirPort, don't launch new
31832 tests when there's already one in progress -- unreachable
31833 servers were stacking up dozens of testing streams.
31835 o Security bugfixes:
31836 - When the user sends a NEWNYM signal, clear the client-side DNS
31837 cache too. Otherwise we continue to act on previous information.
31840 - Avoid a memory corruption bug when creating a hash table for
31842 - Avoid possibility of controller-triggered crash when misusing
31843 certain commands from a v0 controller on platforms that do not
31844 handle printf("%s",NULL) gracefully.
31845 - Avoid infinite loop on unexpected controller input.
31846 - Don't log spurious warnings when we see a circuit close reason we
31847 don't recognize; it's probably just from a newer version of Tor.
31848 - Add Vidalia to the OS X uninstaller script, so when we uninstall
31849 Tor/Privoxy we also uninstall Vidalia.
31852 Changes in version 0.1.2.3-alpha - 2006-10-29
31854 - Prepare for servers to publish descriptors less often: never
31855 discard a descriptor simply for being too old until either it is
31856 recommended by no authorities, or until we get a better one for
31857 the same router. Make caches consider retaining old recommended
31858 routers for even longer.
31859 - If most authorities set a BadExit flag for a server, clients
31860 don't think of it as a general-purpose exit. Clients only consider
31861 authorities that advertise themselves as listing bad exits.
31862 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
31863 headers for content, so that we can work better in the presence of
31864 caching HTTP proxies.
31865 - Allow authorities to list nodes as bad exits by fingerprint or by
31868 o Minor features, controller:
31869 - Add a REASON field to CIRC events; for backward compatibility, this
31870 field is sent only to controllers that have enabled the extended
31871 event format. Also, add additional reason codes to explain why
31872 a given circuit has been destroyed or truncated. (Patches from
31874 - Add a REMOTE_REASON field to extended CIRC events to tell the
31875 controller about why a remote OR told us to close a circuit.
31876 - Stream events also now have REASON and REMOTE_REASON fields,
31877 working much like those for circuit events.
31878 - There's now a GETINFO ns/... field so that controllers can ask Tor
31879 about the current status of a router.
31880 - A new event type "NS" to inform a controller when our opinion of
31881 a router's status has changed.
31882 - Add a GETINFO events/names and GETINFO features/names so controllers
31883 can tell which events and features are supported.
31884 - A new CLEARDNSCACHE signal to allow controllers to clear the
31885 client-side DNS cache without expiring circuits.
31887 o Security bugfixes:
31888 - When the user sends a NEWNYM signal, clear the client-side DNS
31889 cache too. Otherwise we continue to act on previous information.
31892 - Avoid sending junk to controllers or segfaulting when a controller
31893 uses EVENT_NEW_DESC with verbose nicknames.
31894 - Stop triggering asserts if the controller tries to extend hidden
31895 service circuits (reported by mwenge).
31896 - Avoid infinite loop on unexpected controller input.
31897 - When the controller does a "GETINFO network-status", tell it
31898 about even those routers whose descriptors are very old, and use
31899 long nicknames where appropriate.
31900 - Change NT service functions to be loaded on demand. This lets us
31901 build with MinGW without breaking Tor for Windows 98 users.
31902 - Do DirPort reachability tests less often, since a single test
31903 chews through many circuits before giving up.
31904 - In the hidden service example in torrc.sample, stop recommending
31905 esoteric and discouraged hidden service options.
31906 - When stopping an NT service, wait up to 10 sec for it to actually
31907 stop. Patch from Matt Edman; resolves bug 295.
31908 - Fix handling of verbose nicknames with ORCONN controller events:
31909 make them show up exactly when requested, rather than exactly when
31911 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
31912 printing a duplicate "$" in the keys we send (reported by mwenge).
31913 - Correctly set maximum connection limit on Cygwin. (This time
31915 - Try to detect Windows correctly when cross-compiling.
31916 - Detect the size of the routers file correctly even if it is
31917 corrupted (on systems without mmap) or not page-aligned (on systems
31918 with mmap). This bug was harmless.
31919 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
31920 to open a stream fails; now we do in more cases. This should
31921 make clients able to find a good exit faster in some cases, since
31922 unhandleable requests will now get an error rather than timing out.
31923 - Resolve two memory leaks when rebuilding the on-disk router cache
31924 (reported by fookoowa).
31925 - Clean up minor code warnings suggested by the MIPSpro C compiler,
31926 and reported by some Centos users.
31927 - Controller signals now work on non-Unix platforms that don't define
31928 SIGUSR1 and SIGUSR2 the way we expect.
31929 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
31930 values before failing, and always enables eventdns.
31931 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
31932 Try to fix this in configure.in by checking for most functions
31933 before we check for libevent.
31936 Changes in version 0.1.2.2-alpha - 2006-10-07
31938 - Make our async eventdns library on-by-default for Tor servers,
31939 and plan to deprecate the separate dnsworker threads.
31940 - Add server-side support for "reverse" DNS lookups (using PTR
31941 records so clients can determine the canonical hostname for a given
31942 IPv4 address). Only supported by servers using eventdns; servers
31943 now announce in their descriptors whether they support eventdns.
31944 - Specify and implement client-side SOCKS5 interface for reverse DNS
31945 lookups (see doc/socks-extensions.txt).
31946 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
31947 connect to directory servers through Tor. Previously, clients needed
31948 to find Tor exits to make private connections to directory servers.
31949 - Avoid choosing Exit nodes for entry or middle hops when the
31950 total bandwidth available from non-Exit nodes is much higher than
31951 the total bandwidth available from Exit nodes.
31952 - Workaround for name servers (like Earthlink's) that hijack failing
31953 DNS requests and replace the no-such-server answer with a "helpful"
31954 redirect to an advertising-driven search portal. Also work around
31955 DNS hijackers who "helpfully" decline to hijack known-invalid
31956 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
31957 lets you turn it off.
31958 - Send out a burst of long-range padding cells once we've established
31959 that we're reachable. Spread them over 4 circuits, so hopefully
31960 a few will be fast. This exercises our bandwidth and bootstraps
31961 us into the directory more quickly.
31963 o New/improved config options:
31964 - Add new config option "ResolvConf" to let the server operator
31965 choose an alternate resolve.conf file when using eventdns.
31966 - Add an "EnforceDistinctSubnets" option to control our "exclude
31967 servers on the same /16" behavior. It's still on by default; this
31968 is mostly for people who want to operate private test networks with
31969 all the machines on the same subnet.
31970 - If one of our entry guards is on the ExcludeNodes list, or the
31971 directory authorities don't think it's a good guard, treat it as
31972 if it were unlisted: stop using it as a guard, and throw it off
31973 the guards list if it stays that way for a long time.
31974 - Allow directory authorities to be marked separately as authorities
31975 for the v1 directory protocol, the v2 directory protocol, and
31976 as hidden service directories, to make it easier to retire old
31977 authorities. V1 authorities should set "HSAuthoritativeDir 1"
31978 to continue being hidden service authorities too.
31979 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
31981 o Minor features, controller:
31982 - Fix CIRC controller events so that controllers can learn the
31983 identity digests of non-Named servers used in circuit paths.
31984 - Let controllers ask for more useful identifiers for servers. Instead
31985 of learning identity digests for un-Named servers and nicknames
31986 for Named servers, the new identifiers include digest, nickname,
31987 and indication of Named status. Off by default; see control-spec.txt
31988 for more information.
31989 - Add a "getinfo address" controller command so it can display Tor's
31990 best guess to the user.
31991 - New controller event to alert the controller when our server
31992 descriptor has changed.
31993 - Give more meaningful errors on controller authentication failure.
31995 o Minor features, other:
31996 - When asked to resolve a hostname, don't use non-exit servers unless
31997 requested to do so. This allows servers with broken DNS to be
31998 useful to the network.
31999 - Divide eventdns log messages into warn and info messages.
32000 - Reserve the nickname "Unnamed" for routers that can't pick
32001 a hostname: any router can call itself Unnamed; directory
32002 authorities will never allocate Unnamed to any particular router;
32003 clients won't believe that any router is the canonical Unnamed.
32004 - Only include function names in log messages for info/debug messages.
32005 For notice/warn/err, the content of the message should be clear on
32006 its own, and printing the function name only confuses users.
32007 - Avoid some false positives during reachability testing: don't try
32008 to test via a server that's on the same /24 as us.
32009 - If we fail to build a circuit to an intended enclave, and it's
32010 not mandatory that we use that enclave, stop wanting it.
32011 - When eventdns is enabled, allow multithreaded builds on NetBSD and
32012 OpenBSD. (We had previously disabled threads on these platforms
32013 because they didn't have working thread-safe resolver functions.)
32015 o Major bugfixes, anonymity/security:
32016 - If a client asked for a server by name, and there's a named server
32017 in our network-status but we don't have its descriptor yet, we
32018 could return an unnamed server instead.
32019 - Fix NetBSD bug that could allow someone to force uninitialized RAM
32020 to be sent to a server's DNS resolver. This only affects NetBSD
32021 and other platforms that do not bounds-check tolower().
32022 - Reject (most) attempts to use Tor circuits with length one. (If
32023 many people start using Tor as a one-hop proxy, exit nodes become
32024 a more attractive target for compromise.)
32025 - Just because your DirPort is open doesn't mean people should be
32026 able to remotely teach you about hidden service descriptors. Now
32027 only accept rendezvous posts if you've got HSAuthoritativeDir set.
32029 o Major bugfixes, other:
32030 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
32031 - When a client asks the server to resolve (not connect to)
32032 an address, and it has a cached answer, give them the cached answer.
32033 Previously, the server would give them no answer at all.
32034 - Allow really slow clients to not hang up five minutes into their
32035 directory downloads (suggested by Adam J. Richter).
32036 - We were building exactly the wrong circuits when we anticipated
32037 hidden service requirements, meaning Tor would have to build all
32038 its circuits on demand.
32039 - Avoid crashing when we mmap a router cache file of size 0.
32040 - When testing reachability of our DirPort, don't launch new
32041 tests when there's already one in progress -- unreachable
32042 servers were stacking up dozens of testing streams.
32044 o Minor bugfixes, correctness:
32045 - If we're a directory mirror and we ask for "all" network status
32046 documents, we would discard status documents from authorities
32047 we don't recognize.
32048 - Avoid a memory corruption bug when creating a hash table for
32050 - Avoid controller-triggered crash when misusing certain commands
32051 from a v0 controller on platforms that do not handle
32052 printf("%s",NULL) gracefully.
32053 - Don't crash when a controller sends a third argument to an
32054 "extendcircuit" request.
32055 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
32056 response; fix error code when "getinfo dir/status/" fails.
32057 - Avoid crash when telling controller stream-status and a stream
32059 - Patch from Adam Langley to fix assert() in eventdns.c.
32060 - Fix a debug log message in eventdns to say "X resolved to Y"
32061 instead of "X resolved to X".
32062 - Make eventdns give strings for DNS errors, not just error numbers.
32063 - Track unreachable entry guards correctly: don't conflate
32064 'unreachable by us right now' with 'listed as down by the directory
32065 authorities'. With the old code, if a guard was unreachable by
32066 us but listed as running, it would clog our guard list forever.
32067 - Behave correctly in case we ever have a network with more than
32068 2GB/s total advertised capacity.
32069 - Make TrackExitHosts case-insensitive, and fix the behavior of
32070 ".suffix" TrackExitHosts items to avoid matching in the middle of
32072 - Finally fix the openssl warnings from newer gccs that believe that
32073 ignoring a return value is okay, but casting a return value and
32074 then ignoring it is a sign of madness.
32075 - Prevent the contrib/exitlist script from printing the same
32076 result more than once.
32077 - Patch from Steve Hildrey: Generate network status correctly on
32078 non-versioning dirservers.
32079 - Don't listen to the X-Your-Address-Is hint if you did the lookup
32080 via Tor; otherwise you'll think you're the exit node's IP address.
32082 o Minor bugfixes, performance:
32083 - Two small performance improvements on parsing descriptors.
32084 - Major performance improvement on inserting descriptors: change
32085 algorithm from O(n^2) to O(n).
32086 - Make the common memory allocation path faster on machines where
32087 malloc(0) returns a pointer.
32088 - Start remembering X-Your-Address-Is directory hints even if you're
32089 a client, so you can become a server more smoothly.
32090 - Avoid duplicate entries on MyFamily line in server descriptor.
32092 o Packaging, features:
32093 - Remove architecture from OS X builds. The official builds are
32094 now universal binaries.
32095 - The Debian package now uses --verify-config when (re)starting,
32096 to distinguish configuration errors from other errors.
32097 - Update RPMs to require libevent 1.1b.
32099 o Packaging, bugfixes:
32100 - Patches so Tor builds with MinGW on Windows.
32101 - Patches so Tor might run on Cygwin again.
32102 - Resume building on non-gcc compilers and ancient gcc. Resume
32103 building with the -O0 compile flag. Resume building cleanly on
32105 - Run correctly on OS X platforms with case-sensitive filesystems.
32106 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
32107 - Add autoconf checks so Tor can build on Solaris x86 again.
32110 - Documented (and renamed) ServerDNSSearchDomains and
32111 ServerDNSResolvConfFile options.
32112 - Be clearer that the *ListenAddress directives can be repeated
32116 Changes in version 0.1.1.24 - 2006-09-29
32118 - Allow really slow clients to not hang up five minutes into their
32119 directory downloads (suggested by Adam J. Richter).
32120 - Fix major performance regression from 0.1.0.x: instead of checking
32121 whether we have enough directory information every time we want to
32122 do something, only check when the directory information has changed.
32123 This should improve client CPU usage by 25-50%.
32124 - Don't crash if, after a server has been running for a while,
32125 it can't resolve its hostname.
32128 - Allow Tor to start when RunAsDaemon is set but no logs are set.
32129 - Don't crash when the controller receives a third argument to an
32130 "extendcircuit" request.
32131 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
32132 response; fix error code when "getinfo dir/status/" fails.
32133 - Fix configure.in to not produce broken configure files with
32134 more recent versions of autoconf. Thanks to Clint for his auto*
32136 - Fix security bug on NetBSD that could allow someone to force
32137 uninitialized RAM to be sent to a server's DNS resolver. This
32138 only affects NetBSD and other platforms that do not bounds-check
32140 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
32141 methods: these are known to be buggy.
32142 - If we're a directory mirror and we ask for "all" network status
32143 documents, we would discard status documents from authorities
32144 we don't recognize.
32147 Changes in version 0.1.2.1-alpha - 2006-08-27
32149 - Add "eventdns" async dns library from Adam Langley, tweaked to
32150 build on OSX and Windows. Only enabled if you pass the
32151 --enable-eventdns argument to configure.
32152 - Allow servers with no hostname or IP address to learn their
32153 IP address by asking the directory authorities. This code only
32154 kicks in when you would normally have exited with a "no address"
32155 error. Nothing's authenticated, so use with care.
32156 - Rather than waiting a fixed amount of time between retrying
32157 application connections, we wait only 5 seconds for the first,
32158 10 seconds for the second, and 15 seconds for each retry after
32159 that. Hopefully this will improve the expected user experience.
32160 - Patch from Tup to add support for transparent AP connections:
32161 this basically bundles the functionality of trans-proxy-tor
32162 into the Tor mainline. Now hosts with compliant pf/netfilter
32163 implementations can redirect TCP connections straight to Tor
32164 without diverting through SOCKS. Needs docs.
32165 - Busy directory servers save lots of memory by spooling server
32166 descriptors, v1 directories, and v2 networkstatus docs to buffers
32167 as needed rather than en masse. Also mmap the cached-routers
32168 files, so we don't need to keep the whole thing in memory too.
32169 - Automatically avoid picking more than one node from the same
32170 /16 network when constructing a circuit.
32171 - Revise and clean up the torrc.sample that we ship with; add
32172 a section for BandwidthRate and BandwidthBurst.
32175 - Split circuit_t into origin_circuit_t and or_circuit_t, and
32176 split connection_t into edge, or, dir, control, and base structs.
32177 These will save quite a bit of memory on busy servers, and they'll
32178 also help us track down bugs in the code and bugs in the spec.
32179 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
32180 or later. Log when we are doing this, so we can diagnose it when
32181 it fails. (Also, recommend libevent 1.1b for kqueue and
32182 win32 methods; deprecate libevent 1.0b harder; make libevent
32183 recommendation system saner.)
32184 - Start being able to build universal binaries on OS X (thanks
32186 - Export the default exit policy via the control port, so controllers
32187 don't need to guess what it is / will be later.
32188 - Add a man page entry for ProtocolWarnings.
32189 - Add TestVia config option to the man page.
32190 - Remove even more protocol-related warnings from Tor server logs,
32191 such as bad TLS handshakes and malformed begin cells.
32192 - Stop fetching descriptors if you're not a dir mirror and you
32193 haven't tried to establish any circuits lately. [This currently
32194 causes some dangerous behavior, because when you start up again
32195 you'll use your ancient server descriptors.]
32196 - New DirPort behavior: if you have your dirport set, you download
32197 descriptors aggressively like a directory mirror, whether or not
32198 your ORPort is set.
32199 - Get rid of the router_retry_connections notion. Now routers
32200 no longer try to rebuild long-term connections to directory
32201 authorities, and directory authorities no longer try to rebuild
32202 long-term connections to all servers. We still don't hang up
32203 connections in these two cases though -- we need to look at it
32204 more carefully to avoid flapping, and we likely need to wait til
32205 0.1.1.x is obsolete.
32206 - Drop compatibility with obsolete Tors that permit create cells
32207 to have the wrong circ_id_type.
32208 - Re-enable per-connection rate limiting. Get rid of the "OP
32209 bandwidth" concept. Lay groundwork for "bandwidth classes" --
32210 separate global buckets that apply depending on what sort of conn
32212 - Start publishing one minute or so after we find our ORPort
32213 to be reachable. This will help reduce the number of descriptors
32214 we have for ourselves floating around, since it's quite likely
32215 other things (e.g. DirPort) will change during that minute too.
32216 - Fork the v1 directory protocol into its own spec document,
32217 and mark dir-spec.txt as the currently correct (v2) spec.
32220 - When we find our DirPort to be reachable, publish a new descriptor
32221 so we'll tell the world (reported by pnx).
32222 - Publish a new descriptor after we hup/reload. This is important
32223 if our config has changed such that we'll want to start advertising
32224 our DirPort now, etc.
32225 - Allow Tor to start when RunAsDaemon is set but no logs are set.
32226 - When we have a state file we cannot parse, tell the user and
32227 move it aside. Now we avoid situations where the user starts
32228 Tor in 1904, Tor writes a state file with that timestamp in it,
32229 the user fixes her clock, and Tor refuses to start.
32230 - Fix configure.in to not produce broken configure files with
32231 more recent versions of autoconf. Thanks to Clint for his auto*
32233 - "tor --verify-config" now exits with -1(255) or 0 depending on
32234 whether the config options are bad or good.
32235 - Resolve bug 321 when using dnsworkers: append a period to every
32236 address we resolve at the exit node, so that we do not accidentally
32237 pick up local addresses, and so that failing searches are retried
32238 in the resolver search domains. (This is already solved for
32239 eventdns.) (This breaks Blossom servers for now.)
32240 - If we are using an exit enclave and we can't connect, e.g. because
32241 its webserver is misconfigured to not listen on localhost, then
32242 back off and try connecting from somewhere else before we fail.
32245 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
32246 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
32247 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
32248 when the IP address is mapped through MapAddress to a hostname.
32249 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
32250 useless IPv6 DNS resolves.
32251 - Patch suggested by Karsten Loesing: respond to SIGNAL command
32252 before we execute the signal, in case the signal shuts us down.
32253 - Clean up AllowInvalidNodes man page entry.
32254 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
32255 - Add more asserts to track down an assert error on a windows Tor
32256 server with connection_add being called with socket == -1.
32257 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
32258 - Fix misleading log messages: an entry guard that is "unlisted",
32259 as well as not known to be "down" (because we've never heard
32260 of it), is not therefore "up".
32261 - Remove code to special-case "-cvs" ending, since it has not
32262 actually mattered since 0.0.9.
32263 - Make our socks5 handling more robust to broken socks clients:
32264 throw out everything waiting on the buffer in between socks
32265 handshake phases, since they can't possibly (so the theory
32266 goes) have predicted what we plan to respond to them.
32269 Changes in version 0.1.1.23 - 2006-07-30
32271 - Fast Tor servers, especially exit nodes, were triggering asserts
32272 due to a bug in handling the list of pending DNS resolves. Some
32273 bugs still remain here; we're hunting them.
32274 - Entry guards could crash clients by sending unexpected input.
32275 - More fixes on reachability testing: if you find yourself reachable,
32276 then don't ever make any client requests (so you stop predicting
32277 circuits), then hup or have your clock jump, then later your IP
32278 changes, you won't think circuits are working, so you won't try to
32279 test reachability, so you won't publish.
32282 - Avoid a crash if the controller does a resetconf firewallports
32283 and then a setconf fascistfirewall=1.
32284 - Avoid an integer underflow when the dir authority decides whether
32285 a router is stable: we might wrongly label it stable, and compute
32286 a slightly wrong median stability, when a descriptor is published
32288 - Fix a place where we might trigger an assert if we can't build our
32289 own server descriptor yet.
32292 Changes in version 0.1.1.22 - 2006-07-05
32294 - Fix a big bug that was causing servers to not find themselves
32295 reachable if they changed IP addresses. Since only 0.1.1.22+
32296 servers can do reachability testing correctly, now we automatically
32297 make sure to test via one of these.
32298 - Fix to allow clients and mirrors to learn directory info from
32299 descriptor downloads that get cut off partway through.
32300 - Directory authorities had a bug in deciding if a newly published
32301 descriptor was novel enough to make everybody want a copy -- a few
32302 servers seem to be publishing new descriptors many times a minute.
32304 - Fix a rare bug that was causing some servers to complain about
32305 "closing wedged cpuworkers" and skip some circuit create requests.
32306 - Make the Exit flag in directory status documents actually work.
32309 Changes in version 0.1.1.21 - 2006-06-10
32310 o Crash and assert fixes from 0.1.1.20:
32311 - Fix a rare crash on Tor servers that have enabled hibernation.
32312 - Fix a seg fault on startup for Tor networks that use only one
32313 directory authority.
32314 - Fix an assert from a race condition that occurs on Tor servers
32315 while exiting, where various threads are trying to log that they're
32316 exiting, and delete the logs, at the same time.
32317 - Make our unit tests pass again on certain obscure platforms.
32320 - Add support for building SUSE RPM packages.
32321 - Speed up initial bootstrapping for clients: if we are making our
32322 first ever connection to any entry guard, then don't mark it down
32324 - When only one Tor server in the network is labelled as a guard,
32325 and we've already picked him, we would cycle endlessly picking him
32326 again, being unhappy about it, etc. Now we specifically exclude
32327 current guards when picking a new guard.
32328 - Servers send create cells more reliably after the TLS connection
32329 is established: we were sometimes forgetting to send half of them
32330 when we had more than one pending.
32331 - If we get a create cell that asks us to extend somewhere, but the
32332 Tor server there doesn't match the expected digest, we now send
32333 a destroy cell back, rather than silently doing nothing.
32334 - Make options->RedirectExit work again.
32335 - Make cookie authentication for the controller work again.
32336 - Stop being picky about unusual characters in the arguments to
32337 mapaddress. It's none of our business.
32338 - Add a new config option "TestVia" that lets you specify preferred
32339 middle hops to use for test circuits. Perhaps this will let me
32340 debug the reachability problems better.
32342 o Log / documentation fixes:
32343 - If we're a server and some peer has a broken TLS certificate, don't
32344 log about it unless ProtocolWarnings is set, i.e., we want to hear
32345 about protocol violations by others.
32346 - Fix spelling of VirtualAddrNetwork in man page.
32347 - Add a better explanation at the top of the autogenerated torrc file
32348 about what happened to our old torrc.
32351 Changes in version 0.1.1.20 - 2006-05-23
32353 - Downgrade a log severity where servers complain that they're
32355 - Avoid a compile warning on FreeBSD.
32356 - Remove string size limit on NEWDESC messages; solve bug 291.
32357 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
32358 more thoroughly when we're running on windows.
32361 Changes in version 0.1.1.19-rc - 2006-05-03
32363 - Regenerate our local descriptor if it's dirty and we try to use
32364 it locally (e.g. if it changes during reachability detection).
32365 - If we setconf our ORPort to 0, we continued to listen on the
32366 old ORPort and receive connections.
32367 - Avoid a second warning about machine/limits.h on Debian
32369 - Be willing to add our own routerinfo into the routerlist.
32370 Now authorities will include themselves in their directories
32371 and network-statuses.
32372 - Stop trying to upload rendezvous descriptors to every
32373 directory authority: only try the v1 authorities.
32374 - Servers no longer complain when they think they're not
32375 registered with the directory authorities. There were too many
32377 - Backport dist-rpm changes so rpms can be built without errors.
32380 - Implement an option, VirtualAddrMask, to set which addresses
32381 get handed out in response to mapaddress requests. This works
32382 around a bug in tsocks where 127.0.0.0/8 is never socksified.
32385 Changes in version 0.1.1.18-rc - 2006-04-10
32387 - Work harder to download live network-statuses from all the
32388 directory authorities we know about. Improve the threshold
32389 decision logic so we're more robust to edge cases.
32390 - When fetching rendezvous descriptors, we were willing to ask
32391 v2 authorities too, which would always return 404.
32394 - Stop listing down or invalid nodes in the v1 directory. This will
32395 reduce its bulk by about 1/3, and reduce load on directory
32397 - When deciding whether a router is Fast or Guard-worthy, consider
32398 his advertised BandwidthRate and not just the BandwidthCapacity.
32399 - No longer ship INSTALL and README files -- they are useless now.
32400 - Force rpmbuild to behave and honor target_cpu.
32401 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
32402 - Start to include translated versions of the tor-doc-*.html
32403 files, along with the screenshots. Still needs more work.
32404 - Start sending back 512 and 451 errors if mapaddress fails,
32405 rather than not sending anything back at all.
32406 - When we fail to bind or listen on an incoming or outgoing
32407 socket, we should close it before failing. otherwise we just
32408 leak it. (thanks to weasel for finding.)
32409 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
32410 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
32411 - Make NoPublish (even though deprecated) work again.
32412 - Fix a minor security flaw where a versioning auth dirserver
32413 could list a recommended version many times in a row to make
32414 clients more convinced that it's recommended.
32415 - Fix crash bug if there are two unregistered servers running
32416 with the same nickname, one of them is down, and you ask for
32417 them by nickname in your EntryNodes or ExitNodes. Also, try
32418 to pick the one that's running rather than an arbitrary one.
32419 - Fix an infinite loop we could hit if we go offline for too long.
32420 - Complain when we hit WSAENOBUFS on recv() or write() too.
32421 Perhaps this will help us hunt the bug.
32422 - If you're not a versioning dirserver, don't put the string
32423 "client-versions \nserver-versions \n" in your network-status.
32424 - Lower the minimum required number of file descriptors to 1000,
32425 so we can have some overhead for Valgrind on Linux, where the
32426 default ulimit -n is 1024.
32429 - Add tor.dizum.com as the fifth authoritative directory server.
32430 - Add a new config option FetchUselessDescriptors, off by default,
32431 for when you plan to run "exitlist" on your client and you want
32432 to know about even the non-running descriptors.
32435 Changes in version 0.1.1.17-rc - 2006-03-28
32437 - Clients and servers since 0.1.1.10-alpha have been expiring
32438 connections whenever they are idle for 5 minutes and they *do*
32439 have circuits on them. Oops. With this new version, clients will
32440 discard their previous entry guard choices and avoid choosing
32441 entry guards running these flawed versions.
32442 - Fix memory leak when uncompressing concatenated zlib streams. This
32443 was causing substantial leaks over time on Tor servers.
32444 - The v1 directory was including servers as much as 48 hours old,
32445 because that's how the new routerlist->routers works. Now only
32446 include them if they're 20 hours old or less.
32449 - Resume building on irix64, netbsd 2.0, etc.
32450 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
32452 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
32453 and it is confusing some users.
32454 - Mirrors stop caching the v1 directory so often.
32455 - Make the max number of old descriptors that a cache will hold
32456 rise with the number of directory authorities, so we can scale.
32457 - Change our win32 uname() hack to be more forgiving about what
32458 win32 versions it thinks it's found.
32461 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
32463 - When the controller's *setconf commands fail, collect an error
32464 message in a string and hand it back to the controller.
32465 - Make the v2 dir's "Fast" flag based on relative capacity, just
32466 like "Stable" is based on median uptime. Name everything in the
32467 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
32468 - Log server fingerprint on startup, so new server operators don't
32469 have to go hunting around their filesystem for it.
32470 - Return a robots.txt on our dirport to discourage google indexing.
32471 - Let the controller ask for GETINFO dir/status/foo so it can ask
32472 directly rather than connecting to the dir port. Only works when
32473 dirport is set for now.
32475 o New config options rather than constants in the code:
32476 - SocksTimeout: How long do we let a socks connection wait
32477 unattached before we fail it?
32478 - CircuitBuildTimeout: Cull non-open circuits that were born
32479 at least this many seconds ago.
32480 - CircuitIdleTimeout: Cull open clean circuits that were born
32481 at least this many seconds ago.
32484 Changes in version 0.1.1.16-rc - 2006-03-18
32485 o Bugfixes on 0.1.1.15-rc:
32486 - Fix assert when the controller asks to attachstream a connect-wait
32487 or resolve-wait stream.
32488 - Now do address rewriting when the controller asks us to attach
32489 to a particular circuit too. This will let Blossom specify
32490 "moria2.exit" without having to learn what moria2's IP address is.
32491 - Make the "tor --verify-config" command-line work again, so people
32492 can automatically check if their torrc will parse.
32493 - Authoritative dirservers no longer require an open connection from
32494 a server to consider him "reachable". We need this change because
32495 when we add new auth dirservers, old servers won't know not to
32497 - Let Tor build on Sun CC again.
32498 - Fix an off-by-one buffer size in dirserv.c that magically never
32499 hit our three authorities but broke sjmurdoch's own tor network.
32500 - If we as a directory mirror don't know of any v1 directory
32501 authorities, then don't try to cache any v1 directories.
32502 - Stop warning about unknown servers in our family when they are
32503 given as hex digests.
32504 - Stop complaining as quickly to the server operator that he
32505 hasn't registered his nickname/key binding.
32506 - Various cleanups so we can add new V2 Auth Dirservers.
32507 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
32508 reflect the updated flags in our v2 dir protocol.
32509 - Resume allowing non-printable characters for exit streams (both
32510 for connecting and for resolving). Now we tolerate applications
32511 that don't follow the RFCs. But continue to block malformed names
32514 o Bugfixes on 0.1.0.x:
32515 - Fix assert bug in close_logs(): when we close and delete logs,
32516 remove them all from the global "logfiles" list.
32517 - Fix minor integer overflow in calculating when we expect to use up
32518 our bandwidth allocation before hibernating.
32519 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
32520 there are multiple SSLs installed with different versions.
32521 - When we try to be a server and Address is not explicitly set and
32522 our hostname resolves to a private IP address, try to use an
32523 interface address if it has a public address. Now Windows machines
32524 that think of themselves as localhost can work by default.
32527 - Let the controller ask for GETINFO dir/server/foo so it can ask
32528 directly rather than connecting to the dir port.
32529 - Let the controller tell us about certain router descriptors
32530 that it doesn't want Tor to use in circuits. Implement
32531 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
32532 - New config option SafeSocks to reject all application connections
32533 using unsafe socks protocols. Defaults to off.
32536 Changes in version 0.1.1.15-rc - 2006-03-11
32537 o Bugfixes and cleanups:
32538 - When we're printing strings from the network, don't try to print
32539 non-printable characters. This protects us against shell escape
32540 sequence exploits, and also against attacks to fool humans into
32541 misreading their logs.
32542 - Fix a bug where Tor would fail to establish any connections if you
32543 left it off for 24 hours and then started it: we were happy with
32544 the obsolete network statuses, but they all referred to router
32545 descriptors that were too old to fetch, so we ended up with no
32546 valid router descriptors.
32547 - Fix a seg fault in the controller's "getinfo orconn-status"
32548 command while listing status on incoming handshaking connections.
32549 Introduce a status name "NEW" for these connections.
32550 - If we get a linelist or linelist_s config option from the torrc
32551 (e.g. ExitPolicy) and it has no value, warn and skip rather than
32552 silently resetting it to its default.
32553 - Don't abandon entry guards until they've been down or gone for
32555 - Cleaner and quieter log messages.
32558 - New controller signal NEWNYM that makes new application requests
32559 use clean circuits.
32560 - Add a new circuit purpose 'controller' to let the controller ask
32561 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
32562 controller command to let you specify the purpose if you're
32563 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
32564 command to let you change a circuit's purpose after it's been
32566 - Accept "private:*" in routerdesc exit policies; not generated yet
32567 because older Tors do not understand it.
32568 - Add BSD-style contributed startup script "rc.subr" from Peter
32572 Changes in version 0.1.1.14-alpha - 2006-02-20
32573 o Bugfixes on 0.1.1.x:
32574 - Don't die if we ask for a stdout or stderr log (even implicitly)
32575 and we're set to RunAsDaemon -- just warn.
32576 - We still had a few bugs in the OR connection rotation code that
32577 caused directory servers to slowly aggregate connections to other
32578 fast Tor servers. This time for sure!
32579 - Make log entries on Win32 include the name of the function again.
32580 - We were treating a pair of exit policies if they were equal even
32581 if one said accept and the other said reject -- causing us to
32582 not always publish a new descriptor since we thought nothing
32584 - Retry pending server downloads as well as pending networkstatus
32585 downloads when we unexpectedly get a socks request.
32586 - We were ignoring the IS_FAST flag in the directory status,
32587 meaning we were willing to pick trivial-bandwidth nodes for "fast"
32589 - If the controller's SAVECONF command fails (e.g. due to file
32590 permissions), let the controller know that it failed.
32593 - If we're trying to be a Tor server and running Windows 95/98/ME
32594 as a server, explain that we'll likely crash.
32595 - When we're a server, a client asks for an old-style directory,
32596 and our write bucket is empty, don't give it to him. This way
32597 small servers can continue to serve the directory *sometimes*,
32598 without getting overloaded.
32599 - Compress exit policies even more -- look for duplicate lines
32601 - Clients now honor the "guard" flag in the router status when
32602 picking entry guards, rather than looking at is_fast or is_stable.
32603 - Retain unrecognized lines in $DATADIR/state file, so that we can
32604 be forward-compatible.
32605 - Generate 18.0.0.0/8 address policy format in descs when we can;
32606 warn when the mask is not reducible to a bit-prefix.
32607 - Let the user set ControlListenAddress in the torrc. This can be
32608 dangerous, but there are some cases (like a secured LAN) where it
32610 - Split ReachableAddresses into ReachableDirAddresses and
32611 ReachableORAddresses, so we can restrict Dir conns to port 80
32612 and OR conns to port 443.
32613 - Now we can target arch and OS in rpm builds (contributed by
32614 Phobos). Also make the resulting dist-rpm filename match the
32616 - New config options to help controllers: FetchServerDescriptors
32617 and FetchHidServDescriptors for whether to fetch server
32618 info and hidserv info or let the controller do it, and
32619 PublishServerDescriptor and PublishHidServDescriptors.
32620 - Also let the controller set the __AllDirActionsPrivate config
32621 option if you want all directory fetches/publishes to happen via
32622 Tor (it assumes your controller bootstraps your circuits).
32625 Changes in version 0.1.0.17 - 2006-02-17
32626 o Crash bugfixes on 0.1.0.x:
32627 - When servers with a non-zero DirPort came out of hibernation,
32628 sometimes they would trigger an assert.
32630 o Other important bugfixes:
32631 - On platforms that don't have getrlimit (like Windows), we were
32632 artificially constraining ourselves to a max of 1024
32633 connections. Now just assume that we can handle as many as 15000
32634 connections. Hopefully this won't cause other problems.
32636 o Backported features:
32637 - When we're a server, a client asks for an old-style directory,
32638 and our write bucket is empty, don't give it to him. This way
32639 small servers can continue to serve the directory *sometimes*,
32640 without getting overloaded.
32641 - Whenever you get a 503 in response to a directory fetch, try
32642 once more. This will become important once servers start sending
32643 503's whenever they feel busy.
32644 - Fetch a new directory every 120 minutes, not every 40 minutes.
32645 Now that we have hundreds of thousands of users running the old
32646 directory algorithm, it's starting to hurt a lot.
32647 - Bump up the period for forcing a hidden service descriptor upload
32648 from 20 minutes to 1 hour.
32651 Changes in version 0.1.1.13-alpha - 2006-02-09
32652 o Crashes in 0.1.1.x:
32653 - When you tried to setconf ORPort via the controller, Tor would
32654 crash. So people using TorCP to become a server were sad.
32655 - Solve (I hope) the stack-smashing bug that we were seeing on fast
32656 servers. The problem appears to be something do with OpenSSL's
32657 random number generation, or how we call it, or something. Let me
32658 know if the crashes continue.
32659 - Turn crypto hardware acceleration off by default, until we find
32660 somebody smart who can test it for us. (It appears to produce
32661 seg faults in at least some cases.)
32662 - Fix a rare assert error when we've tried all intro points for
32663 a hidden service and we try fetching the service descriptor again:
32664 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
32667 - Fix a major load balance bug: we were round-robining in 16 KB
32668 chunks, and servers with bandwidthrate of 20 KB, while downloading
32669 a 600 KB directory, would starve their other connections. Now we
32670 try to be a bit more fair.
32671 - Dir authorities and mirrors were never expiring the newest
32672 descriptor for each server, causing memory and directory bloat.
32673 - Fix memory-bloating and connection-bloating bug on servers: We
32674 were never closing any connection that had ever had a circuit on
32675 it, because we were checking conn->n_circuits == 0, yet we had a
32676 bug that let it go negative.
32677 - Make Tor work using squid as your http proxy again -- squid
32678 returns an error if you ask for a URL that's too long, and it uses
32679 a really generic error message. Plus, many people are behind a
32680 transparent squid so they don't even realize it.
32681 - On platforms that don't have getrlimit (like Windows), we were
32682 artificially constraining ourselves to a max of 1024
32683 connections. Now just assume that we can handle as many as 15000
32684 connections. Hopefully this won't cause other problems.
32685 - Add a new config option ExitPolicyRejectPrivate which defaults to
32686 1. This means all exit policies will begin with rejecting private
32687 addresses, unless the server operator explicitly turns it off.
32690 - Clients no longer download descriptors for non-running
32692 - Before we add new directory authorities, we should make it
32693 clear that only v1 authorities should receive/publish hidden
32694 service descriptors.
32697 - As soon as we've fetched some more directory info, immediately
32698 try to download more server descriptors. This way we don't have
32699 a 10 second pause during initial bootstrapping.
32700 - Remove even more loud log messages that the server operator can't
32702 - When we're running an obsolete or un-recommended version, make
32703 the log message more clear about what the problem is and what
32704 versions *are* still recommended.
32705 - Provide a more useful warn message when our onion queue gets full:
32706 the CPU is too slow or the exit policy is too liberal.
32707 - Don't warn when we receive a 503 from a dirserver/cache -- this
32708 will pave the way for them being able to refuse if they're busy.
32709 - When we fail to bind a listener, try to provide a more useful
32710 log message: e.g., "Is Tor already running?"
32711 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
32712 Goldberg can prove things about our handshake protocol more
32714 - MaxConn has been obsolete for a while now. Document the ConnLimit
32715 config option, which is a *minimum* number of file descriptors
32716 that must be available else Tor refuses to start.
32717 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
32718 if you log to syslog and want something other than LOG_DAEMON.
32719 - Make dirservers generate a separate "guard" flag to mean,
32720 "would make a good entry guard". Make clients parse it and vote
32721 on it. Not used by clients yet.
32722 - Implement --with-libevent-dir option to ./configure. Also, improve
32723 search techniques to find libevent, and use those for openssl too.
32724 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
32725 - Only start testing reachability once we've established a
32726 circuit. This will make startup on dirservers less noisy.
32727 - Don't try to upload hidden service descriptors until we have
32728 established a circuit.
32729 - Fix the controller's "attachstream 0" command to treat conn like
32730 it just connected, doing address remapping, handling .exit and
32731 .onion idioms, and so on. Now we're more uniform in making sure
32732 that the controller hears about new and closing connections.
32735 Changes in version 0.1.1.12-alpha - 2006-01-11
32736 o Bugfixes on 0.1.1.x:
32737 - The fix to close duplicate server connections was closing all
32738 Tor client connections if they didn't establish a circuit
32739 quickly enough. Oops.
32740 - Fix minor memory issue (double-free) that happened on exit.
32742 o Bugfixes on 0.1.0.x:
32743 - Tor didn't warn when it failed to open a log file.
32746 Changes in version 0.1.1.11-alpha - 2006-01-10
32747 o Crashes in 0.1.1.x:
32748 - Include all the assert/crash fixes from 0.1.0.16.
32749 - If you start Tor and then quit very quickly, there were some
32750 races that tried to free things that weren't allocated yet.
32751 - Fix a rare memory stomp if you're running hidden services.
32752 - Fix segfault when specifying DirServer in config without nickname.
32753 - Fix a seg fault when you finish connecting to a server but at
32754 that moment you dump his server descriptor.
32755 - Extendcircuit and Attachstream controller commands would
32756 assert/crash if you don't give them enough arguments.
32757 - Fix an assert error when we're out of space in the connection_list
32758 and we try to post a hidden service descriptor (reported by weasel).
32759 - If you specify a relative torrc path and you set RunAsDaemon in
32760 your torrc, then it chdir()'s to the new directory. If you HUP,
32761 it tries to load the new torrc location, fails, and exits.
32762 The fix: no longer allow a relative path to torrc using -f.
32765 - Implement "entry guards": automatically choose a handful of entry
32766 nodes and stick with them for all circuits. Only pick new guards
32767 when the ones you have are unsuitable, and if the old guards
32768 become suitable again, switch back. This will increase security
32769 dramatically against certain end-point attacks. The EntryNodes
32770 config option now provides some hints about which entry guards you
32771 want to use most; and StrictEntryNodes means to only use those.
32772 - New directory logic: download by descriptor digest, not by
32773 fingerprint. Caches try to download all listed digests from
32774 authorities; clients try to download "best" digests from caches.
32775 This avoids partitioning and isolating attacks better.
32776 - Make the "stable" router flag in network-status be the median of
32777 the uptimes of running valid servers, and make clients pay
32778 attention to the network-status flags. Thus the cutoff adapts
32779 to the stability of the network as a whole, making IRC, IM, etc
32780 connections more reliable.
32783 - Tor servers with dynamic IP addresses were needing to wait 18
32784 hours before they could start doing reachability testing using
32785 the new IP address and ports. This is because they were using
32786 the internal descriptor to learn what to test, yet they were only
32787 rebuilding the descriptor once they decided they were reachable.
32788 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
32789 to download certain server descriptors, throw them away, and then
32790 fetch them again after 30 minutes. Now mirrors throw away these
32791 server descriptors so clients can't get them.
32792 - We were leaving duplicate connections to other ORs open for a week,
32793 rather than closing them once we detect a duplicate. This only
32794 really affected authdirservers, but it affected them a lot.
32795 - Spread the authdirservers' reachability testing over the entire
32796 testing interval, so we don't try to do 500 TLS's at once every
32800 - If the network is down, and we try to connect to a conn because
32801 we have a circuit in mind, and we timeout (30 seconds) because the
32802 network never answers, we were expiring the circuit, but we weren't
32803 obsoleting the connection or telling the entry_guards functions.
32804 - Some Tor servers process billions of cells per day. These statistics
32805 need to be uint64_t's.
32806 - Check for integer overflows in more places, when adding elements
32807 to smartlists. This could possibly prevent a buffer overflow
32808 on malicious huge inputs. I don't see any, but I haven't looked
32810 - ReachableAddresses kept growing new "reject *:*" lines on every
32812 - When you "setconf log" via the controller, it should remove all
32813 logs. We were automatically adding back in a "log notice stdout".
32814 - Newly bootstrapped Tor networks couldn't establish hidden service
32815 circuits until they had nodes with high uptime. Be more tolerant.
32816 - We were marking servers down when they could not answer every piece
32817 of the directory request we sent them. This was far too harsh.
32818 - Fix the torify (tsocks) config file to not use Tor for localhost
32820 - Directory authorities now go to the proper authority when asking for
32821 a networkstatus, even when they want a compressed one.
32822 - Fix a harmless bug that was causing Tor servers to log
32823 "Got an end because of misc error, but we're not an AP. Closing."
32824 - Authorities were treating their own descriptor changes as cosmetic,
32825 meaning the descriptor available in the network-status and the
32826 descriptor that clients downloaded were different.
32827 - The OS X installer was adding a symlink for tor_resolve but
32828 the binary was called tor-resolve (reported by Thomas Hardly).
32829 - Workaround a problem with some http proxies where they refuse GET
32830 requests that specify "Content-Length: 0" (reported by Adrian).
32831 - Fix wrong log message when you add a "HiddenServiceNodes" config
32832 line without any HiddenServiceDir line (reported by Chris Thomas).
32835 - Write the TorVersion into the state file so we have a prayer of
32836 keeping forward and backward compatibility.
32837 - Revive the FascistFirewall config option rather than eliminating it:
32838 now it's a synonym for ReachableAddresses *:80,*:443.
32839 - Clients choose directory servers from the network status lists,
32840 not from their internal list of router descriptors. Now they can
32841 go to caches directly rather than needing to go to authorities
32843 - Directory authorities ignore router descriptors that have only
32844 cosmetic differences: do this for 0.1.0.x servers now too.
32845 - Add a new flag to network-status indicating whether the server
32846 can answer v2 directory requests too.
32847 - Authdirs now stop whining so loudly about bad descriptors that
32848 they fetch from other dirservers. So when there's a log complaint,
32849 it's for sure from a freshly uploaded descriptor.
32850 - Reduce memory requirements in our structs by changing the order
32852 - There used to be two ways to specify your listening ports in a
32853 server descriptor: on the "router" line and with a separate "ports"
32854 line. Remove support for the "ports" line.
32855 - New config option "AuthDirRejectUnlisted" for auth dirservers as
32856 a panic button: if we get flooded with unusable servers we can
32857 revert to only listing servers in the approved-routers file.
32858 - Auth dir servers can now mark a fingerprint as "!reject" or
32859 "!invalid" in the approved-routers file (as its nickname), to
32860 refuse descriptors outright or include them but marked as invalid.
32861 - Servers store bandwidth history across restarts/crashes.
32862 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
32863 get a better idea of why their circuits failed. Not used yet.
32864 - Directory mirrors now cache up to 16 unrecognized network-status
32865 docs. Now we can add new authdirservers and they'll be cached too.
32866 - When picking a random directory, prefer non-authorities if any
32868 - New controller option "getinfo desc/all-recent" to fetch the
32869 latest server descriptor for every router that Tor knows about.
32872 Changes in version 0.1.0.16 - 2006-01-02
32873 o Crash bugfixes on 0.1.0.x:
32874 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
32875 corrupting the heap, losing FDs, or crashing when we need to resize
32876 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
32877 - It turns out sparc64 platforms crash on unaligned memory access
32878 too -- so detect and avoid this.
32879 - Handle truncated compressed data correctly (by detecting it and
32881 - Fix possible-but-unlikely free(NULL) in control.c.
32882 - When we were closing connections, there was a rare case that
32883 stomped on memory, triggering seg faults and asserts.
32884 - Avoid potential infinite recursion when building a descriptor. (We
32885 don't know that it ever happened, but better to fix it anyway.)
32886 - We were neglecting to unlink marked circuits from soon-to-close OR
32887 connections, which caused some rare scribbling on freed memory.
32888 - Fix a memory stomping race bug when closing the joining point of two
32889 rendezvous circuits.
32890 - Fix an assert in time parsing found by Steven Murdoch.
32892 o Other bugfixes on 0.1.0.x:
32893 - When we're doing reachability testing, provide more useful log
32894 messages so the operator knows what to expect.
32895 - Do not check whether DirPort is reachable when we are suppressing
32896 advertising it because of hibernation.
32897 - When building with -static or on Solaris, we sometimes needed -ldl.
32898 - When we're deciding whether a stream has enough circuits around
32899 that can handle it, count the freshly dirty ones and not the ones
32900 that are so dirty they won't be able to handle it.
32901 - When we're expiring old circuits, we had a logic error that caused
32902 us to close new rendezvous circuits rather than old ones.
32903 - Give a more helpful log message when you try to change ORPort via
32904 the controller: you should upgrade Tor if you want that to work.
32905 - We were failing to parse Tor versions that start with "Tor ".
32906 - Tolerate faulty streams better: when a stream fails for reason
32907 exitpolicy, stop assuming that the router is lying about his exit
32908 policy. When a stream fails for reason misc, allow it to retry just
32909 as if it was resolvefailed. When a stream has failed three times,
32910 reset its failure count so we can try again and get all three tries.
32913 Changes in version 0.1.1.10-alpha - 2005-12-11
32914 o Correctness bugfixes on 0.1.0.x:
32915 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
32916 corrupting the heap, losing FDs, or crashing when we need to resize
32917 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
32918 - Stop doing the complex voodoo overkill checking for insecure
32919 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
32920 - When we were closing connections, there was a rare case that
32921 stomped on memory, triggering seg faults and asserts.
32922 - We were neglecting to unlink marked circuits from soon-to-close OR
32923 connections, which caused some rare scribbling on freed memory.
32924 - When we're deciding whether a stream has enough circuits around
32925 that can handle it, count the freshly dirty ones and not the ones
32926 that are so dirty they won't be able to handle it.
32927 - Recover better from TCP connections to Tor servers that are
32928 broken but don't tell you (it happens!); and rotate TLS
32929 connections once a week.
32930 - When we're expiring old circuits, we had a logic error that caused
32931 us to close new rendezvous circuits rather than old ones.
32932 - Fix a scary-looking but apparently harmless bug where circuits
32933 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
32934 servers, and never switch to state CIRCUIT_STATE_OPEN.
32935 - When building with -static or on Solaris, we sometimes needed to
32937 - Give a useful message when people run Tor as the wrong user,
32938 rather than telling them to start chowning random directories.
32939 - We were failing to inform the controller about new .onion streams.
32941 o Security bugfixes on 0.1.0.x:
32942 - Refuse server descriptors if the fingerprint line doesn't match
32943 the included identity key. Tor doesn't care, but other apps (and
32944 humans) might actually be trusting the fingerprint line.
32945 - We used to kill the circuit when we receive a relay command we
32946 don't recognize. Now we just drop it.
32947 - Start obeying our firewall options more rigorously:
32948 . If we can't get to a dirserver directly, try going via Tor.
32949 . Don't ever try to connect (as a client) to a place our
32950 firewall options forbid.
32951 . If we specify a proxy and also firewall options, obey the
32952 firewall options even when we're using the proxy: some proxies
32953 can only proxy to certain destinations.
32954 - Fix a bug found by Lasse Overlier: when we were making internal
32955 circuits (intended to be cannibalized later for rendezvous and
32956 introduction circuits), we were picking them so that they had
32957 useful exit nodes. There was no need for this, and it actually
32958 aids some statistical attacks.
32959 - Start treating internal circuits and exit circuits separately.
32960 It's important to keep them separate because internal circuits
32961 have their last hops picked like middle hops, rather than like
32962 exit hops. So exiting on them will break the user's expectations.
32964 o Bugfixes on 0.1.1.x:
32965 - Take out the mis-feature where we tried to detect IP address
32966 flapping for people with DynDNS, and chose not to upload a new
32967 server descriptor sometimes.
32968 - Try to be compatible with OpenSSL 0.9.6 again.
32969 - Log fix: when the controller is logging about .onion addresses,
32970 sometimes it didn't include the ".onion" part of the address.
32971 - Don't try to modify options->DirServers internally -- if the
32972 user didn't specify any, just add the default ones directly to
32973 the trusted dirserver list. This fixes a bug where people running
32974 controllers would use SETCONF on some totally unrelated config
32975 option, and Tor would start yelling at them about changing their
32977 - Let the controller's redirectstream command specify a port, in
32978 case the controller wants to change that too.
32979 - When we requested a pile of server descriptors, we sometimes
32980 accidentally launched a duplicate request for the first one.
32981 - Bugfix for trackhostexits: write down the fingerprint of the
32982 chosen exit, not its nickname, because the chosen exit might not
32984 - When parsing foo.exit, if foo is unknown, and we are leaving
32985 circuits unattached, set the chosen_exit field and leave the
32986 address empty. This matters because controllers got confused
32988 - Directory authorities no longer try to download server
32989 descriptors that they know they will reject.
32991 o Features and updates:
32992 - Replace balanced trees with hash tables: this should make stuff
32993 significantly faster.
32994 - Resume using the AES counter-mode implementation that we ship,
32995 rather than OpenSSL's. Ours is significantly faster.
32996 - Many other CPU and memory improvements.
32997 - Add a new config option FastFirstHopPK (on by default) so clients
32998 do a trivial crypto handshake for their first hop, since TLS has
32999 already taken care of confidentiality and authentication.
33000 - Add a new config option TestSocks so people can see if their
33001 applications are using socks4, socks4a, socks5-with-ip, or
33002 socks5-with-hostname. This way they don't have to keep mucking
33003 with tcpdump and wondering if something got cached somewhere.
33004 - Warn when listening on a public address for socks. I suspect a
33005 lot of people are setting themselves up as open socks proxies,
33006 and they have no idea that jerks on the Internet are using them,
33007 since they simply proxy the traffic into the Tor network.
33008 - Add "private:*" as an alias in configuration for policies. Now
33009 you can simplify your exit policy rather than needing to list
33010 every single internal or nonroutable network space.
33011 - Add a new controller event type that allows controllers to get
33012 all server descriptors that were uploaded to a router in its role
33013 as authoritative dirserver.
33014 - Start shipping socks-extensions.txt, tor-doc-unix.html,
33015 tor-doc-server.html, and stylesheet.css in the tarball.
33016 - Stop shipping tor-doc.html in the tarball.
33019 Changes in version 0.1.1.9-alpha - 2005-11-15
33020 o Usability improvements:
33021 - Start calling it FooListenAddress rather than FooBindAddress,
33022 since few of our users know what it means to bind an address
33024 - Reduce clutter in server logs. We're going to try to make
33025 them actually usable now. New config option ProtocolWarnings that
33026 lets you hear about how _other Tors_ are breaking the protocol. Off
33028 - Divide log messages into logging domains. Once we put some sort
33029 of interface on this, it will let people looking at more verbose
33030 log levels specify the topics they want to hear more about.
33031 - Make directory servers return better http 404 error messages
33032 instead of a generic "Servers unavailable".
33033 - Check for even more Windows version flags when writing the platform
33034 string in server descriptors, and note any we don't recognize.
33035 - Clean up more of the OpenSSL memory when exiting, so we can detect
33036 memory leaks better.
33037 - Make directory authorities be non-versioning, non-naming by
33038 default. Now we can add new directory servers without requiring
33039 their operators to pay close attention.
33040 - When logging via syslog, include the pid whenever we provide
33041 a log entry. Suggested by Todd Fries.
33043 o Performance improvements:
33044 - Directory servers now silently throw away new descriptors that
33045 haven't changed much if the timestamps are similar. We do this to
33046 tolerate older Tor servers that upload a new descriptor every 15
33047 minutes. (It seemed like a good idea at the time.)
33048 - Inline bottleneck smartlist functions; use fast versions by default.
33049 - Add a "Map from digest to void*" abstraction digestmap_t so we
33050 can do less hex encoding/decoding. Use it in router_get_by_digest()
33051 to resolve a performance bottleneck.
33052 - Allow tor_gzip_uncompress to extract as much as possible from
33053 truncated compressed data. Try to extract as many
33054 descriptors as possible from truncated http responses (when
33055 DIR_PURPOSE_FETCH_ROUTERDESC).
33056 - Make circ->onionskin a pointer, not a static array. moria2 was using
33057 125000 circuit_t's after it had been up for a few weeks, which
33058 translates to 20+ megs of wasted space.
33059 - The private half of our EDH handshake keys are now chosen out
33060 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
33062 o Security improvements:
33063 - Start making directory caches retain old routerinfos, so soon
33064 clients can start asking by digest of descriptor rather than by
33065 fingerprint of server.
33066 - Add half our entropy from RAND_poll in OpenSSL. This knows how
33067 to use egd (if present), openbsd weirdness (if present), vms/os2
33068 weirdness (if we ever port there), and more in the future.
33070 o Bugfixes on 0.1.0.x:
33071 - Do round-robin writes of at most 16 kB per write. This might be
33072 more fair on loaded Tor servers, and it might resolve our Windows
33073 crash bug. It might also slow things down.
33074 - Our TLS handshakes were generating a single public/private
33075 keypair for the TLS context, rather than making a new one for
33076 each new connections. Oops. (But we were still rotating them
33077 periodically, so it's not so bad.)
33078 - When we were cannibalizing a circuit with a particular exit
33079 node in mind, we weren't checking to see if that exit node was
33080 already present earlier in the circuit. Oops.
33081 - When a Tor server's IP changes (e.g. from a dyndns address),
33082 upload a new descriptor so clients will learn too.
33083 - Really busy servers were keeping enough circuits open on stable
33084 connections that they were wrapping around the circuit_id
33085 space. (It's only two bytes.) This exposed a bug where we would
33086 feel free to reuse a circuit_id even if it still exists but has
33087 been marked for close. Try to fix this bug. Some bug remains.
33088 - If we would close a stream early (e.g. it asks for a .exit that
33089 we know would refuse it) but the LeaveStreamsUnattached config
33090 option is set by the controller, then don't close it.
33092 o Bugfixes on 0.1.1.8-alpha:
33093 - Fix a big pile of memory leaks, some of them serious.
33094 - Do not try to download a routerdesc if we would immediately reject
33096 - Resume inserting a newline between all router descriptors when
33097 generating (old style) signed directories, since our spec says
33099 - When providing content-type application/octet-stream for
33100 server descriptors using .z, we were leaving out the
33101 content-encoding header. Oops. (Everything tolerated this just
33102 fine, but that doesn't mean we need to be part of the problem.)
33103 - Fix a potential seg fault in getconf and getinfo using version 1
33104 of the controller protocol.
33105 - Avoid crash: do not check whether DirPort is reachable when we
33106 are suppressing it because of hibernation.
33107 - Make --hash-password not crash on exit.
33110 Changes in version 0.1.1.8-alpha - 2005-10-07
33111 o New features (major):
33112 - Clients don't download or use the directory anymore. Now they
33113 download and use network-statuses from the trusted dirservers,
33114 and fetch individual server descriptors as needed from mirrors.
33115 See dir-spec.txt for all the gory details.
33116 - Be more conservative about whether to advertise our DirPort.
33117 The main change is to not advertise if we're running at capacity
33118 and either a) we could hibernate or b) our capacity is low and
33119 we're using a default DirPort.
33120 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
33122 o New features (minor):
33123 - Try to be smart about when to retry network-status and
33124 server-descriptor fetches. Still needs some tuning.
33125 - Stop parsing, storing, or using running-routers output (but
33126 mirrors still cache and serve it).
33127 - Consider a threshold of versioning dirservers (dirservers who have
33128 an opinion about which Tor versions are still recommended) before
33129 deciding whether to warn the user that he's obsolete.
33130 - Dirservers can now reject/invalidate by key and IP, with the
33131 config options "AuthDirInvalid" and "AuthDirReject". This is
33132 useful since currently we automatically list servers as running
33133 and usable even if we know they're jerks.
33134 - Provide dire warnings to any users who set DirServer; move it out
33135 of torrc.sample and into torrc.complete.
33136 - Add MyFamily to torrc.sample in the server section.
33137 - Add nicknames to the DirServer line, so we can refer to them
33138 without requiring all our users to memorize their IP addresses.
33139 - When we get an EOF or a timeout on a directory connection, note
33140 how many bytes of serverdesc we are dropping. This will help
33141 us determine whether it is smart to parse incomplete serverdesc
33143 - Add a new function to "change pseudonyms" -- that is, to stop
33144 using any currently-dirty circuits for new streams, so we don't
33145 link new actions to old actions. Currently it's only called on
33146 HUP (or SIGNAL RELOAD).
33147 - On sighup, if UseHelperNodes changed to 1, use new circuits.
33148 - Start using RAND_bytes rather than RAND_pseudo_bytes from
33149 OpenSSL. Also, reseed our entropy every hour, not just at
33150 startup. And entropy in 512-bit chunks, not 160-bit chunks.
33152 o Fixes on 0.1.1.7-alpha:
33153 - Nobody ever implemented EVENT_ADDRMAP for control protocol
33154 version 0, so don't let version 0 controllers ask for it.
33155 - If you requested something with too many newlines via the
33156 v1 controller protocol, you could crash tor.
33157 - Fix a number of memory leaks, including some pretty serious ones.
33158 - Re-enable DirPort testing again, so Tor servers will be willing
33159 to advertise their DirPort if it's reachable.
33160 - On TLS handshake, only check the other router's nickname against
33161 its expected nickname if is_named is set.
33163 o Fixes forward-ported from 0.1.0.15:
33164 - Don't crash when we don't have any spare file descriptors and we
33165 try to spawn a dns or cpu worker.
33166 - Make the numbers in read-history and write-history into uint64s,
33167 so they don't overflow and publish negatives in the descriptor.
33169 o Fixes on 0.1.0.x:
33170 - For the OS X package's modified privoxy config file, comment
33171 out the "logfile" line so we don't log everything passed
33173 - We were whining about using socks4 or socks5-with-local-lookup
33174 even when it's an IP in the "virtual" range we designed exactly
33176 - We were leaking some memory every time the client changes IPs.
33177 - Never call free() on tor_malloc()d memory. This will help us
33178 use dmalloc to detect memory leaks.
33179 - Check for named servers when looking them up by nickname;
33180 warn when we'recalling a non-named server by its nickname;
33181 don't warn twice about the same name.
33182 - Try to list MyFamily elements by key, not by nickname, and warn
33183 if we've not heard of the server.
33184 - Make windows platform detection (uname equivalent) smarter.
33185 - It turns out sparc64 doesn't like unaligned access either.
33188 Changes in version 0.1.0.15 - 2005-09-23
33189 o Bugfixes on 0.1.0.x:
33190 - Reject ports 465 and 587 (spam targets) in default exit policy.
33191 - Don't crash when we don't have any spare file descriptors and we
33192 try to spawn a dns or cpu worker.
33193 - Get rid of IgnoreVersion undocumented config option, and make us
33194 only warn, never exit, when we're running an obsolete version.
33195 - Don't try to print a null string when your server finds itself to
33196 be unreachable and the Address config option is empty.
33197 - Make the numbers in read-history and write-history into uint64s,
33198 so they don't overflow and publish negatives in the descriptor.
33199 - Fix a minor memory leak in smartlist_string_remove().
33200 - We were only allowing ourselves to upload a server descriptor at
33201 most every 20 minutes, even if it changed earlier than that.
33202 - Clean up log entries that pointed to old URLs.
33205 Changes in version 0.1.1.7-alpha - 2005-09-14
33206 o Fixes on 0.1.1.6-alpha:
33207 - Exit servers were crashing when people asked them to make a
33208 connection to an address not in their exit policy.
33209 - Looking up a non-existent stream for a v1 control connection would
33211 - Fix a seg fault if we ask a dirserver for a descriptor by
33212 fingerprint but he doesn't know about him.
33213 - SETCONF was appending items to linelists, not clearing them.
33214 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
33215 out and refuse the setconf if it would fail.
33216 - Downgrade the dirserver log messages when whining about
33220 - Add Peter Palfrader's check-tor script to tor/contrib/
33221 It lets you easily check whether a given server (referenced by
33222 nickname) is reachable by you.
33223 - Numerous changes to move towards client-side v2 directories. Not
33226 o Fixes on 0.1.0.x:
33227 - If the user gave tor an odd number of command-line arguments,
33228 we were silently ignoring the last one. Now we complain and fail.
33229 [This wins the oldest-bug prize -- this bug has been present since
33230 November 2002, as released in Tor 0.0.0.]
33231 - Do not use unaligned memory access on alpha, mips, or mipsel.
33232 It *works*, but is very slow, so we treat them as if it doesn't.
33233 - Retry directory requests if we fail to get an answer we like
33234 from a given dirserver (we were retrying before, but only if
33235 we fail to connect).
33236 - When writing the RecommendedVersions line, sort them first.
33237 - When the client asked for a rendezvous port that the hidden
33238 service didn't want to provide, we were sending an IP address
33239 back along with the end cell. Fortunately, it was zero. But stop
33241 - Correct "your server is reachable" log entries to indicate that
33242 it was self-testing that told us so.
33245 Changes in version 0.1.1.6-alpha - 2005-09-09
33246 o Fixes on 0.1.1.5-alpha:
33247 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
33248 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
33249 - Fix bug with tor_memmem finding a match at the end of the string.
33250 - Make unit tests run without segfaulting.
33251 - Resolve some solaris x86 compile warnings.
33252 - Handle duplicate lines in approved-routers files without warning.
33253 - Fix bug where as soon as a server refused any requests due to his
33254 exit policy (e.g. when we ask for localhost and he tells us that's
33255 127.0.0.1 and he won't do it), we decided he wasn't obeying his
33256 exit policy using him for any exits.
33257 - Only do openssl hardware accelerator stuff if openssl version is
33260 o New controller features/fixes:
33261 - Add a "RESETCONF" command so you can set config options like
33262 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
33263 a config option in the torrc with no value, then it clears it
33264 entirely (rather than setting it to its default).
33265 - Add a "GETINFO config-file" to tell us where torrc is.
33266 - Avoid sending blank lines when GETINFO replies should be empty.
33267 - Add a QUIT command for the controller (for using it manually).
33268 - Fix a bug in SAVECONF that was adding default dirservers and
33269 other redundant entries to the torrc file.
33271 o Start on the new directory design:
33272 - Generate, publish, cache, serve new network-status format.
33273 - Publish individual descriptors (by fingerprint, by "all", and by
33275 - Publish client and server recommended versions separately.
33276 - Allow tor_gzip_uncompress() to handle multiple concatenated
33277 compressed strings. Serve compressed groups of router
33278 descriptors. The compression logic here could be more
33280 - Distinguish v1 authorities (all currently trusted directories)
33281 from v2 authorities (all trusted directories).
33282 - Change DirServers config line to note which dirs are v1 authorities.
33283 - Add configuration option "V1AuthoritativeDirectory 1" which
33284 moria1, moria2, and tor26 should set.
33285 - Remove option when getting directory cache to see whether they
33286 support running-routers; they all do now. Replace it with one
33287 to see whether caches support v2 stuff.
33290 - Dirservers now do their own external reachability testing of each
33291 Tor server, and only list them as running if they've been found to
33292 be reachable. We also send back warnings to the server's logs if
33293 it uploads a descriptor that we already believe is unreachable.
33294 - Implement exit enclaves: if we know an IP address for the
33295 destination, and there's a running Tor server at that address
33296 which allows exit to the destination, then extend the circuit to
33297 that exit first. This provides end-to-end encryption and end-to-end
33298 authentication. Also, if the user wants a .exit address or enclave,
33299 use 4 hops rather than 3, and cannibalize a general circ for it
33301 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
33302 controller. Also, rotate dns and cpu workers if the controller
33303 changes options that will affect them; and initialize the dns
33304 worker cache tree whether or not we start out as a server.
33305 - Only upload a new server descriptor when options change, 18
33306 hours have passed, uptime is reset, or bandwidth changes a lot.
33307 - Check [X-]Forwarded-For headers in HTTP requests when generating
33308 log messages. This lets people run dirservers (and caches) behind
33309 Apache but still know which IP addresses are causing warnings.
33311 o Config option changes:
33312 - Replace (Fascist)Firewall* config options with a new
33313 ReachableAddresses option that understands address policies.
33314 For example, "ReachableAddresses *:80,*:443"
33315 - Get rid of IgnoreVersion undocumented config option, and make us
33316 only warn, never exit, when we're running an obsolete version.
33317 - Make MonthlyAccountingStart config option truly obsolete now.
33319 o Fixes on 0.1.0.x:
33320 - Reject ports 465 and 587 in the default exit policy, since
33321 people have started using them for spam too.
33322 - It turns out we couldn't bootstrap a network since we added
33323 reachability detection in 0.1.0.1-rc. Good thing the Tor network
33324 has never gone down. Add an AssumeReachable config option to let
33325 servers and dirservers bootstrap. When we're trying to build a
33326 high-uptime or high-bandwidth circuit but there aren't enough
33327 suitable servers, try being less picky rather than simply failing.
33328 - Our logic to decide if the OR we connected to was the right guy
33329 was brittle and maybe open to a mitm for unverified routers.
33330 - We weren't cannibalizing circuits correctly for
33331 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
33332 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
33333 build those from scratch. This should make hidden services faster.
33334 - Predict required circuits better, with an eye toward making hidden
33335 services faster on the service end.
33336 - Retry streams if the exit node sends back a 'misc' failure. This
33337 should result in fewer random failures. Also, after failing
33338 from resolve failed or misc, reset the num failures, so we give
33339 it a fair shake next time we try.
33340 - Clean up the rendezvous warn log msgs, and downgrade some to info.
33341 - Reduce severity on logs about dns worker spawning and culling.
33342 - When we're shutting down and we do something like try to post a
33343 server descriptor or rendezvous descriptor, don't complain that
33344 we seem to be unreachable. Of course we are, we're shutting down.
33345 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
33346 We don't use them yet, but maybe one day our DNS resolver will be
33347 able to discover them.
33348 - Make ContactInfo mandatory for authoritative directory servers.
33349 - Require server descriptors to list IPv4 addresses -- hostnames
33350 are no longer allowed. This also fixes some potential security
33351 problems with people providing hostnames as their address and then
33352 preferentially resolving them to partition users.
33353 - Change log line for unreachability to explicitly suggest /etc/hosts
33354 as the culprit. Also make it clearer what IP address and ports we're
33355 testing for reachability.
33356 - Put quotes around user-supplied strings when logging so users are
33357 more likely to realize if they add bad characters (like quotes)
33359 - Let auth dir servers start without specifying an Address config
33361 - Make unit tests (and other invocations that aren't the real Tor)
33362 run without launching listeners, creating subdirectories, and so on.
33365 Changes in version 0.1.1.5-alpha - 2005-08-08
33366 o Bugfixes included in 0.1.0.14.
33368 o Bugfixes on 0.1.0.x:
33369 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
33370 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
33371 it would silently using ignore the 6668.
33374 Changes in version 0.1.0.14 - 2005-08-08
33375 o Bugfixes on 0.1.0.x:
33376 - Fix the other half of the bug with crypto handshakes
33378 - Fix an assert trigger if you send a 'signal term' via the
33379 controller when it's listening for 'event info' messages.
33382 Changes in version 0.1.1.4-alpha - 2005-08-04
33383 o Bugfixes included in 0.1.0.13.
33386 - Improve tor_gettimeofday() granularity on windows.
33387 - Make clients regenerate their keys when their IP address changes.
33388 - Implement some more GETINFO goodness: expose helper nodes, config
33389 options, getinfo keys.
33392 Changes in version 0.1.0.13 - 2005-08-04
33393 o Bugfixes on 0.1.0.x:
33394 - Fix a critical bug in the security of our crypto handshakes.
33395 - Fix a size_t underflow in smartlist_join_strings2() that made
33396 it do bad things when you hand it an empty smartlist.
33397 - Fix Windows installer to ship Tor license (thanks to Aphex for
33398 pointing out this oversight) and put a link to the doc directory
33400 - Explicitly set no-unaligned-access for sparc: it turns out the
33401 new gcc's let you compile broken code, but that doesn't make it
33405 Changes in version 0.1.1.3-alpha - 2005-07-23
33406 o Bugfixes on 0.1.1.2-alpha:
33407 - Fix a bug in handling the controller's "post descriptor"
33409 - Fix several bugs in handling the controller's "extend circuit"
33411 - Fix a bug in handling the controller's "stream status" event.
33412 - Fix an assert failure if we have a controller listening for
33413 circuit events and we go offline.
33414 - Re-allow hidden service descriptors to publish 0 intro points.
33415 - Fix a crash when generating your hidden service descriptor if
33416 you don't have enough intro points already.
33418 o New features on 0.1.1.2-alpha:
33419 - New controller function "getinfo accounting", to ask how
33420 many bytes we've used in this time period.
33421 - Experimental support for helper nodes: a lot of the risk from
33422 a small static adversary comes because users pick new random
33423 nodes every time they rebuild a circuit. Now users will try to
33424 stick to the same small set of entry nodes if they can. Not
33425 enabled by default yet.
33427 o Bugfixes on 0.1.0.12:
33428 - If you're an auth dir server, always publish your dirport,
33429 even if you haven't yet found yourself to be reachable.
33430 - Fix a size_t underflow in smartlist_join_strings2() that made
33431 it do bad things when you hand it an empty smartlist.
33434 Changes in version 0.1.0.12 - 2005-07-18
33435 o New directory servers:
33436 - tor26 has changed IP address.
33438 o Bugfixes on 0.1.0.x:
33439 - Fix a possible double-free in tor_gzip_uncompress().
33440 - When --disable-threads is set, do not search for or link against
33441 pthreads libraries.
33442 - Don't trigger an assert if an authoritative directory server
33443 claims its dirport is 0.
33444 - Fix bug with removing Tor as an NT service: some people were
33445 getting "The service did not return an error." Thanks to Matt
33449 Changes in version 0.1.1.2-alpha - 2005-07-15
33450 o New directory servers:
33451 - tor26 has changed IP address.
33453 o Bugfixes on 0.1.0.x, crashes/leaks:
33454 - Port the servers-not-obeying-their-exit-policies fix from
33456 - Fix an fd leak in start_daemon().
33457 - On Windows, you can't always reopen a port right after you've
33458 closed it. So change retry_listeners() to only close and re-open
33459 ports that have changed.
33460 - Fix a possible double-free in tor_gzip_uncompress().
33462 o Bugfixes on 0.1.0.x, usability:
33463 - When tor_socketpair() fails in Windows, give a reasonable
33464 Windows-style errno back.
33465 - Let people type "tor --install" as well as "tor -install" when
33467 want to make it an NT service.
33468 - NT service patch from Matt Edman to improve error messages.
33469 - When the controller asks for a config option with an abbreviated
33470 name, give the full name in our response.
33471 - Correct the man page entry on TrackHostExitsExpire.
33472 - Looks like we were never delivering deflated (i.e. compressed)
33473 running-routers lists, even when asked. Oops.
33474 - When --disable-threads is set, do not search for or link against
33475 pthreads libraries.
33477 o Bugfixes on 0.1.1.x:
33478 - Fix a seg fault with autodetecting which controller version is
33482 - New hidden service descriptor format: put a version in it, and
33483 let people specify introduction/rendezvous points that aren't
33484 in "the directory" (which is subjective anyway).
33485 - Allow the DEBUG controller event to work again. Mark certain log
33486 entries as "don't tell this to controllers", so we avoid cycles.
33489 Changes in version 0.1.0.11 - 2005-06-30
33490 o Bugfixes on 0.1.0.x:
33491 - Fix major security bug: servers were disregarding their
33492 exit policies if clients behaved unexpectedly.
33493 - Make OS X init script check for missing argument, so we don't
33494 confuse users who invoke it incorrectly.
33495 - Fix a seg fault in "tor --hash-password foo".
33496 - The MAPADDRESS control command was broken.
33499 Changes in version 0.1.1.1-alpha - 2005-06-29
33501 - Make OS X init script check for missing argument, so we don't
33502 confuse users who invoke it incorrectly.
33503 - Fix a seg fault in "tor --hash-password foo".
33504 - Fix a possible way to DoS dirservers.
33505 - When we complain that your exit policy implicitly allows local or
33506 private address spaces, name them explicitly so operators can
33508 - Make the log message less scary when all the dirservers are
33509 temporarily unreachable.
33510 - We were printing the number of idle dns workers incorrectly when
33514 - Revised controller protocol (version 1) that uses ascii rather
33515 than binary. Add supporting libraries in python and java so you
33516 can use the controller from your applications without caring how
33517 our protocol works.
33518 - Spiffy new support for crypto hardware accelerators. Can somebody
33522 Changes in version 0.0.9.10 - 2005-06-16
33523 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
33524 - Refuse relay cells that claim to have a length larger than the
33525 maximum allowed. This prevents a potential attack that could read
33526 arbitrary memory (e.g. keys) from an exit server's process
33530 Changes in version 0.1.0.10 - 2005-06-14
33531 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
33532 libevent before 1.1a.
33535 Changes in version 0.1.0.9-rc - 2005-06-09
33537 - Reset buf->highwater every time buf_shrink() is called, not just on
33538 a successful shrink. This was causing significant memory bloat.
33539 - Fix buffer overflow when checking hashed passwords.
33540 - Security fix: if seeding the RNG on Win32 fails, quit.
33541 - Allow seeding the RNG on Win32 even when you're not running as
33543 - Disable threading on Solaris too. Something is wonky with it,
33544 cpuworkers, and reentrant libs.
33545 - Reenable the part of the code that tries to flush as soon as an
33546 OR outbuf has a full TLS record available. Perhaps this will make
33547 OR outbufs not grow as huge except in rare cases, thus saving lots
33548 of CPU time plus memory.
33549 - Reject malformed .onion addresses rather then passing them on as
33550 normal web requests.
33551 - Adapt patch from Adam Langley: fix possible memory leak in
33552 tor_lookup_hostname().
33553 - Initialize libevent later in the startup process, so the logs are
33554 already established by the time we start logging libevent warns.
33555 - Use correct errno on win32 if libevent fails.
33556 - Check and warn about known-bad/slow libevent versions.
33557 - Pay more attention to the ClientOnly config option.
33558 - Have torctl.in/tor.sh.in check for location of su binary (needed
33560 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
33561 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
33562 HttpProxyAuthenticator
33563 - Stop warning about sigpipes in the logs. We're going to
33564 pretend that getting these occasionally is normal and fine.
33565 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
33567 installer screens; and don't put stuff into StartupItems unless
33568 the user asks you to.
33569 - Require servers that use the default dirservers to have public IP
33570 addresses. We have too many servers that are configured with private
33571 IPs and their admins never notice the log entries complaining that
33572 their descriptors are being rejected.
33573 - Add OSX uninstall instructions. An actual uninstall script will
33577 Changes in version 0.1.0.8-rc - 2005-05-23
33579 - It turns out that kqueue on OS X 10.3.9 was causing kernel
33580 panics. Disable kqueue on all OS X Tors.
33581 - Fix RPM: remove duplicate line accidentally added to the rpm
33583 - Disable threads on openbsd too, since its gethostaddr is not
33585 - Tolerate libevent 0.8 since it still works, even though it's
33587 - Enable building on Red Hat 9.0 again.
33588 - Allow the middle hop of the testing circuit to be running any
33589 version, now that most of them have the bugfix to let them connect
33590 to unknown servers. This will allow reachability testing to work
33591 even when 0.0.9.7-0.0.9.9 become obsolete.
33592 - Handle relay cells with rh.length too large. This prevents
33593 a potential attack that could read arbitrary memory (maybe even
33594 keys) from the exit server's process.
33595 - We screwed up the dirport reachability testing when we don't yet
33596 have a cached version of the directory. Hopefully now fixed.
33597 - Clean up router_load_single_router() (used by the controller),
33598 so it doesn't seg fault on error.
33599 - Fix a minor memory leak when somebody establishes an introduction
33600 point at your Tor server.
33601 - If a socks connection ends because read fails, don't warn that
33602 you're not sending a socks reply back.
33605 - Add HttpProxyAuthenticator config option too, that works like
33606 the HttpsProxyAuthenticator config option.
33607 - Encode hashed controller passwords in hex instead of base64,
33608 to make it easier to write controllers.
33611 Changes in version 0.1.0.7-rc - 2005-05-17
33613 - Fix a bug in the OS X package installer that prevented it from
33614 installing on Tiger.
33615 - Fix a script bug in the OS X package installer that made it
33616 complain during installation.
33617 - Find libevent even if it's hiding in /usr/local/ and your
33618 CFLAGS and LDFLAGS don't tell you to look there.
33619 - Be able to link with libevent as a shared library (the default
33620 after 1.0d), even if it's hiding in /usr/local/lib and even
33621 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
33622 assuming you're running gcc. Otherwise fail and give a useful
33624 - Fix a bug in the RPM packager: set home directory for _tor to
33625 something more reasonable when first installing.
33626 - Free a minor amount of memory that is still reachable on exit.
33629 Changes in version 0.1.0.6-rc - 2005-05-14
33631 - Implement --disable-threads configure option. Disable threads on
33632 netbsd by default, because it appears to have no reentrant resolver
33634 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
33635 release (1.1) detects and disables kqueue if it's broken.
33636 - Append default exit policy before checking for implicit internal
33637 addresses. Now we don't log a bunch of complaints on startup
33638 when using the default exit policy.
33639 - Some people were putting "Address " in their torrc, and they had
33640 a buggy resolver that resolved " " to 0.0.0.0. Oops.
33641 - If DataDir is ~/.tor, and that expands to /.tor, then default to
33642 LOCALSTATEDIR/tor instead.
33643 - Fix fragmented-message bug in TorControl.py.
33644 - Resolve a minor bug which would prevent unreachable dirports
33645 from getting suppressed in the published descriptor.
33646 - When the controller gave us a new descriptor, we weren't resolving
33647 it immediately, so Tor would think its address was 0.0.0.0 until
33648 we fetched a new directory.
33649 - Fix an uppercase/lowercase case error in suppressing a bogus
33650 libevent warning on some Linuxes.
33653 - Begin scrubbing sensitive strings from logs by default. Turn off
33654 the config option SafeLogging if you need to do debugging.
33655 - Switch to a new buffer management algorithm, which tries to avoid
33656 reallocing and copying quite as much. In first tests it looks like
33657 it uses *more* memory on average, but less cpu.
33658 - First cut at support for "create-fast" cells. Clients can use
33659 these when extending to their first hop, since the TLS already
33660 provides forward secrecy and authentication. Not enabled on
33662 - When dirservers refuse a router descriptor, we now log its
33663 contactinfo, platform, and the poster's IP address.
33664 - Call tor_free_all instead of connections_free_all after forking, to
33665 save memory on systems that need to fork.
33666 - Whine at you if you're a server and you don't set your contactinfo.
33667 - Implement --verify-config command-line option to check if your torrc
33668 is valid without actually launching Tor.
33669 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
33670 rather than just rejecting it.
33673 Changes in version 0.1.0.5-rc - 2005-04-27
33675 - Stop trying to print a null pointer if an OR conn fails because
33676 we didn't like its cert.
33678 - Switch our internal buffers implementation to use a ring buffer,
33679 to hopefully improve performance for fast servers a lot.
33680 - Add HttpsProxyAuthenticator support (basic auth only), based
33681 on patch from Adam Langley.
33682 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
33683 the fast servers that have been joining lately.
33684 - Give hidden service accesses extra time on the first attempt,
33685 since 60 seconds is often only barely enough. This might improve
33687 - Improve performance for dirservers: stop re-parsing the whole
33688 directory every time you regenerate it.
33689 - Add more debugging info to help us find the weird dns freebsd
33690 pthreads bug; cleaner debug messages to help track future issues.
33693 Changes in version 0.0.9.9 - 2005-04-23
33694 o Bugfixes on 0.0.9.x:
33695 - If unofficial Tor clients connect and send weird TLS certs, our
33696 Tor server triggers an assert. This release contains a minimal
33697 backport from the broader fix that we put into 0.1.0.4-rc.
33700 Changes in version 0.1.0.4-rc - 2005-04-23
33702 - If unofficial Tor clients connect and send weird TLS certs, our
33703 Tor server triggers an assert. Stop asserting, and start handling
33704 TLS errors better in other situations too.
33705 - When the controller asks us to tell it about all the debug-level
33706 logs, it turns out we were generating debug-level logs while
33707 telling it about them, which turns into a bad loop. Now keep
33708 track of whether you're sending a debug log to the controller,
33709 and don't log when you are.
33710 - Fix the "postdescriptor" feature of the controller interface: on
33711 non-complete success, only say "done" once.
33713 - Clients are now willing to load balance over up to 2mB, not 1mB,
33714 of advertised bandwidth capacity.
33715 - Add a NoPublish config option, so you can be a server (e.g. for
33716 testing running Tor servers in other Tor networks) without
33717 publishing your descriptor to the primary dirservers.
33720 Changes in version 0.1.0.3-rc - 2005-04-08
33721 o Improvements on 0.1.0.2-rc:
33722 - Client now retries when streams end early for 'hibernating' or
33723 'resource limit' reasons, rather than failing them.
33724 - More automated handling for dirserver operators:
33725 - Automatically approve nodes running 0.1.0.2-rc or later,
33726 now that the the reachability detection stuff is working.
33727 - Now we allow two unverified servers with the same nickname
33728 but different keys. But if a nickname is verified, only that
33729 nickname+key are allowed.
33730 - If you're an authdirserver connecting to an address:port,
33731 and it's not the OR you were expecting, forget about that
33732 descriptor. If he *was* the one you were expecting, then forget
33733 about all other descriptors for that address:port.
33734 - Allow servers to publish descriptors from 12 hours in the future.
33735 Corollary: only whine about clock skew from the dirserver if
33736 he's a trusted dirserver (since now even verified servers could
33737 have quite wrong clocks).
33738 - Adjust maximum skew and age for rendezvous descriptors: let skew
33739 be 48 hours rather than 90 minutes.
33740 - Efficiency improvements:
33741 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
33742 it much faster to look up a circuit for each relay cell.
33743 - Remove most calls to assert_all_pending_dns_resolves_ok(),
33744 since they're eating our cpu on exit nodes.
33745 - Stop wasting time doing a case insensitive comparison for every
33746 dns name every time we do any lookup. Canonicalize the names to
33747 lowercase and be done with it.
33748 - Start sending 'truncated' cells back rather than destroy cells,
33749 if the circuit closes in front of you. This means we won't have
33750 to abandon partially built circuits.
33751 - Only warn once per nickname from add_nickname_list_to_smartlist
33752 per failure, so an entrynode or exitnode choice that's down won't
33754 - Put a note in the torrc about abuse potential with the default
33756 - Revise control spec and implementation to allow all log messages to
33757 be sent to controller with their severities intact (suggested by
33758 Matt Edman). Update TorControl to handle new log event types.
33759 - Provide better explanation messages when controller's POSTDESCRIPTOR
33761 - Stop putting nodename in the Platform string in server descriptors.
33762 It doesn't actually help, and it is confusing/upsetting some people.
33764 o Bugfixes on 0.1.0.2-rc:
33765 - We were printing the host mask wrong in exit policies in server
33766 descriptors. This isn't a critical bug though, since we were still
33767 obeying the exit policy internally.
33768 - Fix Tor when compiled with libevent but without pthreads: move
33769 connection_unregister() from _connection_free() to
33771 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
33772 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
33773 when we look through the connection array, we'll find any of the
33774 cpu/dnsworkers. This is no good.
33776 o Bugfixes on 0.0.9.8:
33777 - Fix possible bug on threading platforms (e.g. win32) which was
33778 leaking a file descriptor whenever a cpuworker or dnsworker died.
33779 - When using preferred entry or exit nodes, ignore whether the
33780 circuit wants uptime or capacity. They asked for the nodes, they
33782 - chdir() to your datadirectory at the *end* of the daemonize process,
33783 not the beginning. This was a problem because the first time you
33784 run tor, if your datadir isn't there, and you have runasdaemon set
33785 to 1, it will try to chdir to it before it tries to create it. Oops.
33786 - Handle changed router status correctly when dirserver reloads
33787 fingerprint file. We used to be dropping all unverified descriptors
33788 right then. The bug was hidden because we would immediately
33789 fetch a directory from another dirserver, which would include the
33790 descriptors we just dropped.
33791 - When we're connecting to an OR and he's got a different nickname/key
33792 than we were expecting, only complain loudly if we're an OP or a
33793 dirserver. Complaining loudly to the OR admins just confuses them.
33794 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
33795 artificially capped at 500kB.
33798 Changes in version 0.0.9.8 - 2005-04-07
33799 o Bugfixes on 0.0.9.x:
33800 - We have a bug that I haven't found yet. Sometimes, very rarely,
33801 cpuworkers get stuck in the 'busy' state, even though the cpuworker
33802 thinks of itself as idle. This meant that no new circuits ever got
33803 established. Here's a workaround to kill any cpuworker that's been
33804 busy for more than 100 seconds.
33807 Changes in version 0.1.0.2-rc - 2005-04-01
33808 o Bugfixes on 0.1.0.1-rc:
33809 - Fixes on reachability detection:
33810 - Don't check for reachability while hibernating.
33811 - If ORPort is reachable but DirPort isn't, still publish the
33812 descriptor, but zero out DirPort until it's found reachable.
33813 - When building testing circs for ORPort testing, use only
33814 high-bandwidth nodes, so fewer circuits fail.
33815 - Complain about unreachable ORPort separately from unreachable
33816 DirPort, so the user knows what's going on.
33817 - Make sure we only conclude ORPort reachability if we didn't
33818 initiate the conn. Otherwise we could falsely conclude that
33819 we're reachable just because we connected to the guy earlier
33820 and he used that same pipe to extend to us.
33821 - Authdirservers shouldn't do ORPort reachability detection,
33822 since they're in clique mode, so it will be rare to find a
33823 server not already connected to them.
33824 - When building testing circuits, always pick middle hops running
33825 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
33826 bug. (This is a kludge; it will go away when 0.0.9.x becomes
33828 - When we decide we're reachable, actually publish our descriptor
33830 - Fix bug in redirectstream in the controller.
33831 - Fix the state descriptor strings so logs don't claim edge streams
33832 are in a different state than they actually are.
33833 - Use recent libevent features when possible (this only really affects
33834 win32 and osx right now, because the new libevent with these
33835 features hasn't been released yet). Add code to suppress spurious
33837 - Prevent possible segfault in connection_close_unattached_ap().
33838 - Fix newlines on torrc in win32.
33839 - Improve error msgs when tor-resolve fails.
33841 o Improvements on 0.0.9.x:
33842 - New experimental script tor/contrib/ExerciseServer.py (needs more
33843 work) that uses the controller interface to build circuits and
33844 fetch pages over them. This will help us bootstrap servers that
33845 have lots of capacity but haven't noticed it yet.
33846 - New experimental script tor/contrib/PathDemo.py (needs more work)
33847 that uses the controller interface to let you choose whole paths
33849 "<hostname>.<path,separated by dots>.<length of path>.path"
33850 - When we've connected to an OR and handshaked but didn't like
33851 the result, we were closing the conn without sending destroy
33852 cells back for pending circuits. Now send those destroys.
33855 Changes in version 0.0.9.7 - 2005-04-01
33856 o Bugfixes on 0.0.9.x:
33857 - Fix another race crash bug (thanks to Glenn Fink for reporting).
33858 - Compare identity to identity, not to nickname, when extending to
33859 a router not already in the directory. This was preventing us from
33860 extending to unknown routers. Oops.
33861 - Make sure to create OS X Tor user in <500 range, so we aren't
33862 creating actual system users.
33863 - Note where connection-that-hasn't-sent-end was marked, and fix
33864 a few really loud instances of this harmless bug (it's fixed more
33868 Changes in version 0.1.0.1-rc - 2005-03-28
33870 - Add reachability testing. Your Tor server will automatically try
33871 to see if its ORPort and DirPort are reachable from the outside,
33872 and it won't upload its descriptor until it decides they are.
33873 - Handle unavailable hidden services better. Handle slow or busy
33874 hidden services better.
33875 - Add support for CONNECTing through https proxies, with "HttpsProxy"
33877 - New exit policy: accept most low-numbered ports, rather than
33878 rejecting most low-numbered ports.
33879 - More Tor controller support (still experimental). See
33880 http://tor.eff.org/doc/control-spec.txt for all the new features,
33881 including signals to emulate unix signals from any platform;
33882 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
33883 closestream; closecircuit; etc.
33884 - Make nt services work and start on startup on win32 (based on
33885 patch by Matt Edman).
33886 - Add a new AddressMap config directive to rewrite incoming socks
33887 addresses. This lets you, for example, declare an implicit
33888 required exit node for certain sites.
33889 - Add a new TrackHostExits config directive to trigger addressmaps
33890 for certain incoming socks addresses -- for sites that break when
33891 your exit keeps changing (based on patch by Mike Perry).
33892 - Redo the client-side dns cache so it's just an addressmap too.
33893 - Notice when our IP changes, and reset stats/uptime/reachability.
33894 - When an application is using socks5, give him the whole variety of
33895 potential socks5 responses (connect refused, host unreachable, etc),
33896 rather than just "success" or "failure".
33897 - A more sane version numbering system. See
33898 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
33899 - New contributed script "exitlist": a simple python script to
33900 parse directories and find Tor nodes that exit to listed
33902 - New contributed script "privoxy-tor-toggle" to toggle whether
33903 Privoxy uses Tor. Seems to be configured for Debian by default.
33904 - Report HTTP reasons to client when getting a response from directory
33905 servers -- so you can actually know what went wrong.
33906 - New config option MaxAdvertisedBandwidth which lets you advertise
33907 a low bandwidthrate (to not attract as many circuits) while still
33908 allowing a higher bandwidthrate in reality.
33910 o Robustness/stability fixes:
33911 - Make Tor use Niels Provos's libevent instead of its current
33912 poll-but-sometimes-select mess. This will let us use faster async
33913 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
33915 - pthread support now too. This was forced because when we forked,
33916 we ended up wasting a lot of duplicate ram over time. Also switch
33917 to foo_r versions of some library calls to allow reentry and
33919 - Better handling for heterogeneous / unreliable nodes:
33920 - Annotate circuits w/ whether they aim to contain high uptime nodes
33921 and/or high capacity nodes. When building circuits, choose
33923 - This means that every single node in an intro rend circuit,
33924 not just the last one, will have a minimum uptime.
33925 - New config option LongLivedPorts to indicate application streams
33926 that will want high uptime circuits.
33927 - Servers reset uptime when a dir fetch entirely fails. This
33928 hopefully reflects stability of the server's network connectivity.
33929 - If somebody starts his tor server in Jan 2004 and then fixes his
33930 clock, don't make his published uptime be a year.
33931 - Reset published uptime when you wake up from hibernation.
33932 - Introduce a notion of 'internal' circs, which are chosen without
33933 regard to the exit policy of the last hop. Intro and rendezvous
33934 circs must be internal circs, to avoid leaking information. Resolve
33935 and connect streams can use internal circs if they want.
33936 - New circuit pooling algorithm: make sure to have enough circs around
33937 to satisfy any predicted ports, and also make sure to have 2 internal
33938 circs around if we've required internal circs lately (and with high
33939 uptime if we've seen that lately too).
33940 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
33941 which describes how often we retry making new circuits if current
33942 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
33943 how long we're willing to make use of an already-dirty circuit.
33944 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
33945 circ as necessary, if there are any completed ones lying around
33946 when we try to launch one.
33947 - Make hidden services try to establish a rendezvous for 30 seconds,
33948 rather than for n (where n=3) attempts to build a circuit.
33949 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
33950 "ShutdownWaitLength".
33951 - Try to be more zealous about calling connection_edge_end when
33952 things go bad with edge conns in connection.c.
33953 - Revise tor-spec to add more/better stream end reasons.
33954 - Revise all calls to connection_edge_end to avoid sending "misc",
33955 and to take errno into account where possible.
33958 - Fix a race condition that can trigger an assert, when we have a
33959 pending create cell and an OR connection fails right then.
33960 - Fix several double-mark-for-close bugs, e.g. where we were finding
33961 a conn for a cell even if that conn is already marked for close.
33962 - Make sequence of log messages when starting on win32 with no config
33963 file more reasonable.
33964 - When choosing an exit node for a new non-internal circ, don't take
33965 into account whether it'll be useful for any pending x.onion
33966 addresses -- it won't.
33967 - Turn addr_policy_compare from a tristate to a quadstate; this should
33968 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
33969 for google.com" problem.
33970 - Make "platform" string in descriptor more accurate for Win32 servers,
33971 so it's not just "unknown platform".
33972 - Fix an edge case in parsing config options (thanks weasel).
33973 If they say "--" on the commandline, it's not an option.
33974 - Reject odd-looking addresses at the client (e.g. addresses that
33975 contain a colon), rather than having the server drop them because
33977 - tor-resolve requests were ignoring .exit if there was a working circuit
33978 they could use instead.
33979 - REUSEADDR on normal platforms means you can rebind to the port
33980 right after somebody else has let it go. But REUSEADDR on win32
33981 means to let you bind to the port _even when somebody else
33982 already has it bound_! So, don't do that on Win32.
33983 - Change version parsing logic: a version is "obsolete" if it is not
33984 recommended and (1) there is a newer recommended version in the
33985 same series, or (2) there are no recommended versions in the same
33986 series, but there are some recommended versions in a newer series.
33987 A version is "new" if it is newer than any recommended version in
33989 - Stop most cases of hanging up on a socks connection without sending
33993 - Require BandwidthRate to be at least 20kB/s for servers.
33994 - When a dirserver causes you to give a warn, mention which dirserver
33996 - New config option DirAllowPrivateAddresses for authdirservers.
33997 Now by default they refuse router descriptors that have non-IP or
33998 private-IP addresses.
33999 - Stop publishing socksport in the directory, since it's not
34000 actually meant to be public. For compatibility, publish a 0 there
34002 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
34003 smart" value, that is low for servers and high for clients.
34004 - If our clock jumps forward by 100 seconds or more, assume something
34005 has gone wrong with our network and abandon all not-yet-used circs.
34006 - Warn when exit policy implicitly allows local addresses.
34007 - If we get an incredibly skewed timestamp from a dirserver mirror
34008 that isn't a verified OR, don't warn -- it's probably him that's
34010 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
34011 cookies to disk and doesn't log each web request to disk. (Thanks
34012 to Brett Carrington for pointing this out.)
34013 - When a client asks us for a dir mirror and we don't have one,
34014 launch an attempt to get a fresh one.
34015 - If we're hibernating and we get a SIGINT, exit immediately.
34016 - Add --with-dmalloc ./configure option, to track memory leaks.
34017 - And try to free all memory on closing, so we can detect what
34019 - Cache local dns resolves correctly even when they're .exit
34021 - Give a better warning when some other server advertises an
34022 ORPort that is actually an apache running ssl.
34023 - Add "opt hibernating 1" to server descriptor to make it clearer
34024 whether the server is hibernating.
34027 Changes in version 0.0.9.6 - 2005-03-24
34028 o Bugfixes on 0.0.9.x (crashes and asserts):
34029 - Add new end stream reasons to maintenance branch. Fix bug where
34030 reason (8) could trigger an assert. Prevent bug from recurring.
34031 - Apparently win32 stat wants paths to not end with a slash.
34032 - Fix assert triggers in assert_cpath_layer_ok(), where we were
34033 blowing away the circuit that conn->cpath_layer points to, then
34034 checking to see if the circ is well-formed. Backport check to make
34035 sure we dont use the cpath on a closed connection.
34036 - Prevent circuit_resume_edge_reading_helper() from trying to package
34037 inbufs for marked-for-close streams.
34038 - Don't crash on hup if your options->address has become unresolvable.
34039 - Some systems (like OS X) sometimes accept() a connection and tell
34040 you the remote host is 0.0.0.0:0. If this happens, due to some
34041 other mis-features, we get confused; so refuse the conn for now.
34043 o Bugfixes on 0.0.9.x (other):
34044 - Fix harmless but scary "Unrecognized content encoding" warn message.
34045 - Add new stream error reason: TORPROTOCOL reason means "you are not
34046 speaking a version of Tor I understand; say bye-bye to your stream."
34047 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
34048 into the future, now that we are more tolerant of skew. This
34049 resolves a bug where a Tor server would refuse to cache a directory
34050 because all the directories it gets are too far in the future;
34051 yet the Tor server never logs any complaints about clock skew.
34052 - Mac packaging magic: make man pages useable, and do not overwrite
34053 existing torrc files.
34054 - Make OS X log happily to /var/log/tor/tor.log
34057 Changes in version 0.0.9.5 - 2005-02-22
34058 o Bugfixes on 0.0.9.x:
34059 - Fix an assert race at exit nodes when resolve requests fail.
34060 - Stop picking unverified dir mirrors--it only leads to misery.
34061 - Patch from Matt Edman to make NT services work better. Service
34062 support is still not compiled into the executable by default.
34063 - Patch from Dmitri Bely so the Tor service runs better under
34064 the win32 SYSTEM account.
34065 - Make tor-resolve actually work (?) on Win32.
34066 - Fix a sign bug when getrlimit claims to have 4+ billion
34067 file descriptors available.
34068 - Stop refusing to start when bandwidthburst == bandwidthrate.
34069 - When create cells have been on the onion queue more than five
34070 seconds, just send back a destroy and take them off the list.
34073 Changes in version 0.0.9.4 - 2005-02-03
34074 o Bugfixes on 0.0.9:
34075 - Fix an assert bug that took down most of our servers: when
34076 a server claims to have 1 GB of bandwidthburst, don't
34078 - Don't crash as badly if we have spawned the max allowed number
34079 of dnsworkers, or we're out of file descriptors.
34080 - Block more file-sharing ports in the default exit policy.
34081 - MaxConn is now automatically set to the hard limit of max
34082 file descriptors we're allowed (ulimit -n), minus a few for
34084 - Give a clearer message when servers need to raise their
34085 ulimit -n when they start running out of file descriptors.
34086 - SGI Compatibility patches from Jan Schaumann.
34087 - Tolerate a corrupt cached directory better.
34088 - When a dirserver hasn't approved your server, list which one.
34089 - Go into soft hibernation after 95% of the bandwidth is used,
34090 not 99%. This is especially important for daily hibernators who
34091 have a small accounting max. Hopefully it will result in fewer
34092 cut connections when the hard hibernation starts.
34093 - Load-balance better when using servers that claim more than
34094 800kB/s of capacity.
34095 - Make NT services work (experimental, only used if compiled in).
34098 Changes in version 0.0.9.3 - 2005-01-21
34099 o Bugfixes on 0.0.9:
34100 - Backport the cpu use fixes from main branch, so busy servers won't
34101 need as much processor time.
34102 - Work better when we go offline and then come back, or when we
34103 run Tor at boot before the network is up. We do this by
34104 optimistically trying to fetch a new directory whenever an
34105 application request comes in and we think we're offline -- the
34106 human is hopefully a good measure of when the network is back.
34107 - Backport some minimal hidserv bugfixes: keep rend circuits open as
34108 long as you keep using them; actually publish hidserv descriptors
34109 shortly after they change, rather than waiting 20-40 minutes.
34110 - Enable Mac startup script by default.
34111 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
34112 - When you update AllowUnverifiedNodes or FirewallPorts via the
34113 controller's setconf feature, we were always appending, never
34115 - When you update HiddenServiceDir via setconf, it was screwing up
34116 the order of reading the lines, making it fail.
34117 - Do not rewrite a cached directory back to the cache; otherwise we
34118 will think it is recent and not fetch a newer one on startup.
34119 - Workaround for webservers that lie about Content-Encoding: Tor
34120 now tries to autodetect compressed directories and compression
34121 itself. This lets us Proxypass dir fetches through apache.
34124 Changes in version 0.0.9.2 - 2005-01-04
34125 o Bugfixes on 0.0.9 (crashes and asserts):
34126 - Fix an assert on startup when the disk is full and you're logging
34128 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
34129 style address, then we'd crash.
34130 - Fix an assert trigger when the running-routers string we get from
34131 a dirserver is broken.
34132 - Make worker threads start and run on win32. Now win32 servers
34134 - Bandaid (not actually fix, but now it doesn't crash) an assert
34135 where the dns worker dies mysteriously and the main Tor process
34136 doesn't remember anything about the address it was resolving.
34138 o Bugfixes on 0.0.9 (Win32):
34139 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
34140 name out of the warning/assert messages.
34141 - Fix a superficial "unhandled error on read" bug on win32.
34142 - The win32 installer no longer requires a click-through for our
34143 license, since our Free Software license grants rights but does not
34145 - Win32: When connecting to a dirserver fails, try another one
34146 immediately. (This was already working for non-win32 Tors.)
34147 - Stop trying to parse $HOME on win32 when hunting for default
34149 - Make tor-resolve.c work on win32 by calling network_init().
34151 o Bugfixes on 0.0.9 (other):
34152 - Make 0.0.9.x build on Solaris again.
34153 - Due to a fencepost error, we were blowing away the \n when reporting
34154 confvalue items in the controller. So asking for multiple config
34155 values at once couldn't work.
34156 - When listing circuits that are pending on an opening OR connection,
34157 if we're an OR we were listing circuits that *end* at us as
34158 being pending on every listener, dns/cpu worker, etc. Stop that.
34159 - Dirservers were failing to create 'running-routers' or 'directory'
34160 strings if we had more than some threshold of routers. Fix them so
34161 they can handle any number of routers.
34162 - Fix a superficial "Duplicate mark for close" bug.
34163 - Stop checking for clock skew for OR connections, even for servers.
34164 - Fix a fencepost error that was chopping off the last letter of any
34165 nickname that is the maximum allowed nickname length.
34166 - Update URLs in log messages so they point to the new website.
34167 - Fix a potential problem in mangling server private keys while
34168 writing to disk (not triggered yet, as far as we know).
34169 - Include the licenses for other free software we include in Tor,
34170 now that we're shipping binary distributions more regularly.
34173 Changes in version 0.0.9.1 - 2004-12-15
34174 o Bugfixes on 0.0.9:
34175 - Make hibernation actually work.
34176 - Make HashedControlPassword config option work.
34177 - When we're reporting event circuit status to a controller,
34178 don't use the stream status code.
34181 Changes in version 0.0.9 - 2004-12-12
34183 - Clean up manpage and torrc.sample file.
34184 - Clean up severities and text of log warnings.
34186 - Make servers trigger an assert when they enter hibernation.
34189 Changes in version 0.0.9rc7 - 2004-12-08
34190 o Bugfixes on 0.0.9rc:
34191 - Fix a stack-trashing crash when an exit node begins hibernating.
34192 - Avoid looking at unallocated memory while considering which
34193 ports we need to build circuits to cover.
34194 - Stop a sigpipe: when an 'end' cell races with eof from the app,
34195 we shouldn't hold-open-until-flush if the eof arrived first.
34196 - Fix a bug with init_cookie_authentication() in the controller.
34197 - When recommending new-format log lines, if the upper bound is
34198 LOG_ERR, leave it implicit.
34200 o Bugfixes on 0.0.8.1:
34201 - Fix a whole slew of memory leaks.
34202 - Fix isspace() and friends so they still make Solaris happy
34203 but also so they don't trigger asserts on win32.
34204 - Fix parse_iso_time on platforms without strptime (eg win32).
34205 - win32: tolerate extra "readable" events better.
34206 - win32: when being multithreaded, leave parent fdarray open.
34207 - Make unit tests work on win32.
34210 Changes in version 0.0.9rc6 - 2004-12-06
34211 o Bugfixes on 0.0.9pre:
34212 - Clean up some more integer underflow opportunities (not exploitable
34214 - While hibernating, hup should not regrow our listeners.
34215 - Send an end to the streams we close when we hibernate, rather
34216 than just chopping them off.
34217 - React to eof immediately on non-open edge connections.
34219 o Bugfixes on 0.0.8.1:
34220 - Calculate timeout for waiting for a connected cell from the time
34221 we sent the begin cell, not from the time the stream started. If
34222 it took a long time to establish the circuit, we would time out
34223 right after sending the begin cell.
34224 - Fix router_compare_addr_to_addr_policy: it was not treating a port
34225 of * as always matching, so we were picking reject *:* nodes as
34226 exit nodes too. Oops.
34229 - New circuit building strategy: keep a list of ports that we've
34230 used in the past 6 hours, and always try to have 2 circuits open
34231 or on the way that will handle each such port. Seed us with port
34232 80 so web users won't complain that Tor is "slow to start up".
34233 - Make kill -USR1 dump more useful stats about circuits.
34234 - When warning about retrying or giving up, print the address, so
34235 the user knows which one it's talking about.
34236 - If you haven't used a clean circuit in an hour, throw it away,
34237 just to be on the safe side. (This means after 6 hours a totally
34238 unused Tor client will have no circuits open.)
34241 Changes in version 0.0.9rc5 - 2004-12-01
34242 o Bugfixes on 0.0.8.1:
34243 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
34244 - Let resolve conns retry/expire also, rather than sticking around
34246 - If we are using select, make sure we stay within FD_SETSIZE.
34248 o Bugfixes on 0.0.9pre:
34249 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
34250 but doesn't seem to be currently; thanks to Ilja van Sprundel for
34252 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
34253 instead. Impose minima and maxima for all *Period options; impose
34254 even tighter maxima for fetching if we are a caching dirserver.
34255 Clip rather than rejecting.
34256 - Fetch cached running-routers from servers that serve it (that is,
34257 authdirservers and servers running 0.0.9rc5-cvs or later.)
34260 - Accept *:706 (silc) in default exit policy.
34261 - Implement new versioning format for post 0.1.
34262 - Support "foo.nickname.exit" addresses, to let Alice request the
34263 address "foo" as viewed by exit node "nickname". Based on a patch
34265 - Make tor --version --version dump the cvs Id of every file.
34268 Changes in version 0.0.9rc4 - 2004-11-28
34269 o Bugfixes on 0.0.8.1:
34270 - Make windows sockets actually non-blocking (oops), and handle
34271 win32 socket errors better.
34273 o Bugfixes on 0.0.9rc1:
34274 - Actually catch the -USR2 signal.
34277 Changes in version 0.0.9rc3 - 2004-11-25
34278 o Bugfixes on 0.0.8.1:
34279 - Flush the log file descriptor after we print "Tor opening log file",
34280 so we don't see those messages days later.
34282 o Bugfixes on 0.0.9rc1:
34283 - Make tor-resolve work again.
34284 - Avoid infinite loop in tor-resolve if tor hangs up on it.
34285 - Fix an assert trigger for clients/servers handling resolves.
34288 Changes in version 0.0.9rc2 - 2004-11-24
34289 o Bugfixes on 0.0.9rc1:
34290 - I broke socks5 support while fixing the eof bug.
34291 - Allow unitless bandwidths and intervals; they default to bytes
34293 - New servers don't start out hibernating; they are active until
34294 they run out of bytes, so they have a better estimate of how
34295 long it takes, and so their operators can know they're working.
34298 Changes in version 0.0.9rc1 - 2004-11-23
34299 o Bugfixes on 0.0.8.1:
34300 - Finally fix a bug that's been plaguing us for a year:
34301 With high load, circuit package window was reaching 0. Whenever
34302 we got a circuit-level sendme, we were reading a lot on each
34303 socket, but only writing out a bit. So we would eventually reach
34304 eof. This would be noticed and acted on even when there were still
34305 bytes sitting in the inbuf.
34306 - When poll() is interrupted, we shouldn't believe the revents values.
34308 o Bugfixes on 0.0.9pre6:
34309 - Fix hibernate bug that caused pre6 to be broken.
34310 - Don't keep rephist info for routers that haven't had activity for
34311 24 hours. (This matters now that clients have keys, since we track
34313 - Never call close_temp_logs while validating log options.
34314 - Fix backslash-escaping on tor.sh.in and torctl.in.
34317 - Implement weekly/monthly/daily accounting: now you specify your
34318 hibernation properties by
34319 AccountingMax N bytes|KB|MB|GB|TB
34320 AccountingStart day|week|month [day] HH:MM
34321 Defaults to "month 1 0:00".
34322 - Let bandwidth and interval config options be specified as 5 bytes,
34323 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
34324 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
34325 get back to normal.)
34326 - If your requested entry or exit node has advertised bandwidth 0,
34328 - Be more greedy about filling up relay cells -- we try reading again
34329 once we've processed the stuff we read, in case enough has arrived
34330 to fill the last cell completely.
34331 - Apply NT service patch from Osamu Fujino. Still needs more work.
34334 Changes in version 0.0.9pre6 - 2004-11-15
34335 o Bugfixes on 0.0.8.1:
34336 - Fix assert failure on malformed socks4a requests.
34337 - Use identity comparison, not nickname comparison, to choose which
34338 half of circuit-ID-space each side gets to use. This is needed
34339 because sometimes we think of a router as a nickname, and sometimes
34340 as a hex ID, and we can't predict what the other side will do.
34341 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
34342 write() call will fail and we handle it there.
34343 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
34344 and smartlist_len, which are two major profiling offenders.
34346 o Bugfixes on 0.0.9pre5:
34347 - Fix a bug in read_all that was corrupting config files on windows.
34348 - When we're raising the max number of open file descriptors to
34349 'unlimited', don't log that we just raised it to '-1'.
34350 - Include event code with events, as required by control-spec.txt.
34351 - Don't give a fingerprint when clients do --list-fingerprint:
34352 it's misleading, because it will never be the same again.
34353 - Stop using strlcpy in tor_strndup, since it was slowing us
34355 - Remove warn on startup about missing cached-directory file.
34356 - Make kill -USR1 work again.
34357 - Hibernate if we start tor during the "wait for wakeup-time" phase
34358 of an accounting interval. Log our hibernation plans better.
34359 - Authoritative dirservers now also cache their directory, so they
34360 have it on start-up.
34363 - Fetch running-routers; cache running-routers; compress
34364 running-routers; serve compressed running-routers.z
34365 - Add NSI installer script contributed by J Doe.
34366 - Commit VC6 and VC7 workspace/project files.
34367 - Commit a tor.spec for making RPM files, with help from jbash.
34368 - Add contrib/torctl.in contributed by Glenn Fink.
34369 - Implement the control-spec's SAVECONF command, to write your
34370 configuration to torrc.
34371 - Get cookie authentication for the controller closer to working.
34372 - Include control-spec.txt in the tarball.
34373 - When set_conf changes our server descriptor, upload a new copy.
34374 But don't upload it too often if there are frequent changes.
34375 - Document authentication config in man page, and document signals
34377 - Clean up confusing parts of man page and torrc.sample.
34378 - Make expand_filename handle ~ and ~username.
34379 - Use autoconf to enable largefile support where necessary. Use
34380 ftello where available, since ftell can fail at 2GB.
34381 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
34382 log more informatively.
34383 - Give a slightly more useful output for "tor -h".
34384 - Refuse application socks connections to port 0.
34385 - Check clock skew for verified servers, but allow unverified
34386 servers and clients to have any clock skew.
34387 - Break DirFetchPostPeriod into:
34388 - DirFetchPeriod for fetching full directory,
34389 - StatusFetchPeriod for fetching running-routers,
34390 - DirPostPeriod for posting server descriptor,
34391 - RendPostPeriod for posting hidden service descriptors.
34392 - Make sure the hidden service descriptors are at a random offset
34393 from each other, to hinder linkability.
34396 Changes in version 0.0.9pre5 - 2004-11-09
34397 o Bugfixes on 0.0.9pre4:
34398 - Fix a seg fault in unit tests (doesn't affect main program).
34399 - Fix an assert bug where a hidden service provider would fail if
34400 the first hop of his rendezvous circuit was down.
34401 - Hidden service operators now correctly handle version 1 style
34402 INTRODUCE1 cells (nobody generates them still, so not a critical
34404 - If do_hup fails, actually notice.
34405 - Handle more errnos from accept() without closing the listener.
34406 Some OpenBSD machines were closing their listeners because
34407 they ran out of file descriptors.
34408 - Send resolve cells to exit routers that are running a new
34409 enough version of the resolve code to work right.
34410 - Better handling of winsock includes on non-MSV win32 compilers.
34411 - Some people had wrapped their tor client/server in a script
34412 that would restart it whenever it died. This did not play well
34413 with our "shut down if your version is obsolete" code. Now people
34414 don't fetch a new directory if their local cached version is
34416 - Make our autogen.sh work on ksh as well as bash.
34419 - Hibernation: New config option "AccountingMaxKB" lets you
34420 set how many KBytes per month you want to allow your server to
34421 consume. Rather than spreading those bytes out evenly over the
34422 month, we instead hibernate for some of the month and pop up
34423 at a deterministic time, work until the bytes are consumed, then
34424 hibernate again. Config option "MonthlyAccountingStart" lets you
34425 specify which day of the month your billing cycle starts on.
34426 - Control interface: a separate program can now talk to your
34427 client/server over a socket, and get/set config options, receive
34428 notifications of circuits and streams starting/finishing/dying,
34429 bandwidth used, etc. The next step is to get some GUIs working.
34430 Let us know if you want to help out. See doc/control-spec.txt .
34431 - Ship a contrib/tor-control.py as an example script to interact
34432 with the control port.
34433 - "tor --hash-password zzyxz" will output a salted password for
34434 use in authenticating to the control interface.
34435 - New log format in config:
34436 "Log minsev[-maxsev] stdout|stderr|syslog" or
34437 "Log minsev[-maxsev] file /var/foo"
34440 - DirPolicy config option, to let people reject incoming addresses
34441 from their dirserver.
34442 - "tor --list-fingerprint" will list your identity key fingerprint
34444 - Add "pass" target for RedirectExit, to make it easier to break
34445 out of a sequence of RedirectExit rules.
34446 - Clients now generate a TLS cert too, in preparation for having
34447 them act more like real nodes.
34448 - Ship src/win32/ in the tarball, so people can use it to build.
34449 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
34451 - New "router-status" line in directory, to better bind each verified
34452 nickname to its identity key.
34453 - Deprecate unofficial config option abbreviations, and abbreviations
34454 not on the command line.
34455 - Add a pure-C tor-resolve implementation.
34456 - Use getrlimit and friends to ensure we can reach MaxConn (currently
34457 1024) file descriptors.
34459 o Code security improvements, inspired by Ilja:
34460 - Replace sprintf with snprintf. (I think they were all safe, but
34462 - Replace strcpy/strncpy with strlcpy in more places.
34463 - Avoid strcat; use snprintf or strlcat instead.
34464 - snprintf wrapper with consistent (though not C99) overflow behavior.
34467 Changes in version 0.0.9pre4 - 2004-10-17
34468 o Bugfixes on 0.0.9pre3:
34469 - If the server doesn't specify an exit policy, use the real default
34470 exit policy, not reject *:*.
34471 - Ignore fascistfirewall when uploading/downloading hidden service
34472 descriptors, since we go through Tor for those; and when using
34473 an HttpProxy, since we assume it can reach them all.
34474 - When looking for an authoritative dirserver, use only the ones
34475 configured at boot. Don't bother looking in the directory.
34476 - The rest of the fix for get_default_conf_file() on older win32.
34477 - Make 'Routerfile' config option obsolete.
34480 - New 'MyFamily nick1,...' config option for a server to
34481 specify other servers that shouldn't be used in the same circuit
34482 with it. Only believed if nick1 also specifies us.
34483 - New 'NodeFamily nick1,nick2,...' config option for a client to
34484 specify nodes that it doesn't want to use in the same circuit.
34485 - New 'Redirectexit pattern address:port' config option for a
34486 server to redirect exit connections, e.g. to a local squid.
34489 Changes in version 0.0.9pre3 - 2004-10-13
34490 o Bugfixes on 0.0.8.1:
34491 - Better torrc example lines for dirbindaddress and orbindaddress.
34492 - Improved bounds checking on parsed ints (e.g. config options and
34493 the ones we find in directories.)
34494 - Better handling of size_t vs int, so we're more robust on 64
34496 - Fix the rest of the bug where a newly started OR would appear
34497 as unverified even after we've added his fingerprint and hupped
34499 - Fix a bug from 0.0.7: when read() failed on a stream, we would
34500 close it without sending back an end. So 'connection refused'
34501 would simply be ignored and the user would get no response.
34503 o Bugfixes on 0.0.9pre2:
34504 - Serving the cached-on-disk directory to people is bad. We now
34505 provide no directory until we've fetched a fresh one.
34506 - Workaround for bug on windows where cached-directories get crlf
34508 - Make get_default_conf_file() work on older windows too.
34509 - If we write a *:* exit policy line in the descriptor, don't write
34510 any more exit policy lines.
34513 - Use only 0.0.9pre1 and later servers for resolve cells.
34514 - Make the dirservers file obsolete.
34515 - Include a dir-signing-key token in directories to tell the
34516 parsing entity which key is being used to sign.
34517 - Remove the built-in bulky default dirservers string.
34518 - New config option "Dirserver %s:%d [fingerprint]", which can be
34519 repeated as many times as needed. If no dirservers specified,
34520 default to moria1,moria2,tor26.
34521 - Make moria2 advertise a dirport of 80, so people behind firewalls
34522 will be able to get a directory.
34523 - Http proxy support
34524 - Dirservers translate requests for http://%s:%d/x to /x
34525 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
34526 be routed through this host.
34527 - Clients ask for /tor/x rather than /x for new enough dirservers.
34528 This way we can one day coexist peacefully with apache.
34529 - Clients specify a "Host: %s%d" http header, to be compatible
34530 with more proxies, and so running squid on an exit node can work.
34533 Changes in version 0.0.8.1 - 2004-10-13
34535 - Fix a seg fault that can be triggered remotely for Tor
34536 clients/servers with an open dirport.
34537 - Fix a rare assert trigger, where routerinfos for entries in
34538 our cpath would expire while we're building the path.
34539 - Fix a bug in OutboundBindAddress so it (hopefully) works.
34540 - Fix a rare seg fault for people running hidden services on
34541 intermittent connections.
34542 - Fix a bug in parsing opt keywords with objects.
34543 - Fix a stale pointer assert bug when a stream detaches and
34545 - Fix a string format vulnerability (probably not exploitable)
34546 in reporting stats locally.
34547 - Fix an assert trigger: sometimes launching circuits can fail
34548 immediately, e.g. because too many circuits have failed recently.
34549 - Fix a compile warning on 64 bit platforms.
34552 Changes in version 0.0.9pre2 - 2004-10-03
34554 - Make fetching a cached directory work for 64-bit platforms too.
34555 - Make zlib.h a required header, not an optional header.
34558 Changes in version 0.0.9pre1 - 2004-10-01
34560 - Stop using separate defaults for no-config-file and
34561 empty-config-file. Now you have to explicitly turn off SocksPort,
34562 if you don't want it open.
34563 - Fix a bug in OutboundBindAddress so it (hopefully) works.
34564 - Improve man page to mention more of the 0.0.8 features.
34565 - Fix a rare seg fault for people running hidden services on
34566 intermittent connections.
34567 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
34569 - Fix more dns related bugs: send back resolve_failed and end cells
34570 more reliably when the resolve fails, rather than closing the
34571 circuit and then trying to send the cell. Also attach dummy resolve
34572 connections to a circuit *before* calling dns_resolve(), to fix
34573 a bug where cached answers would never be sent in RESOLVED cells.
34574 - When we run out of disk space, or other log writing error, don't
34575 crash. Just stop logging to that log and continue.
34576 - We were starting to daemonize before we opened our logs, so if
34577 there were any problems opening logs, we would complain to stderr,
34578 which wouldn't work, and then mysteriously exit.
34579 - Fix a rare bug where sometimes a verified OR would connect to us
34580 before he'd uploaded his descriptor, which would cause us to
34581 assign conn->nickname as though he's unverified. Now we look through
34582 the fingerprint list to see if he's there.
34583 - Fix a rare assert trigger, where routerinfos for entries in
34584 our cpath would expire while we're building the path.
34587 - Clients can ask dirservers for /dir.z to get a compressed version
34588 of the directory. Only works for servers running 0.0.9, of course.
34589 - Make clients cache directories and use them to seed their router
34590 lists at startup. This means clients have a datadir again.
34591 - Configuration infrastructure support for warning on obsolete
34593 - Respond to content-encoding headers by trying to uncompress as
34595 - Reply with a deflated directory when a client asks for "dir.z".
34596 We could use allow-encodings instead, but allow-encodings isn't
34597 specified in HTTP 1.0.
34598 - Raise the max dns workers from 50 to 100.
34599 - Discourage people from setting their dirfetchpostperiod more often
34600 than once per minute.
34601 - Protect dirservers from overzealous descriptor uploading -- wait
34602 10 seconds after directory gets dirty, before regenerating.
34605 Changes in version 0.0.8 - 2004-08-25
34606 o Port it to SunOS 5.9 / Athena
34609 Changes in version 0.0.8rc2 - 2004-08-20
34610 o Make it compile on cygwin again.
34611 o When picking unverified routers, skip those with low uptime and/or
34612 low bandwidth, depending on what properties you care about.
34615 Changes in version 0.0.8rc1 - 2004-08-18
34616 o Changes from 0.0.7.3:
34618 - Fix assert triggers: if the other side returns an address 0.0.0.0,
34619 don't put it into the client dns cache.
34620 - If a begin failed due to exit policy, but we believe the IP address
34621 should have been allowed, switch that router to exitpolicy reject *:*
34622 until we get our next directory.
34624 - Clients choose nodes proportional to advertised bandwidth.
34625 - Avoid using nodes with low uptime as introduction points.
34626 - Handle servers with dynamic IP addresses: don't replace
34627 options->Address with the resolved one at startup, and
34628 detect our address right before we make a routerinfo each time.
34629 - 'FascistFirewall' option to pick dirservers and ORs on specific
34630 ports; plus 'FirewallPorts' config option to tell FascistFirewall
34631 which ports are open. (Defaults to 80,443)
34632 - Be more aggressive about trying to make circuits when the network
34633 has changed (e.g. when you unsuspend your laptop).
34634 - Check for time skew on http headers; report date in response to
34636 - If the entrynode config line has only one node, don't pick it as
34638 - Add strict{entry|exit}nodes config options. If set to 1, then
34639 we refuse to build circuits that don't include the specified entry
34641 - OutboundBindAddress config option, to bind to a specific
34642 IP address for outgoing connect()s.
34643 - End truncated log entries (e.g. directories) with "[truncated]".
34645 o Patches to 0.0.8preX:
34647 - Patches to compile and run on win32 again (maybe)?
34648 - Fix crash when looking for ~/.torrc with no $HOME set.
34649 - Fix a race bug in the unit tests.
34650 - Handle verified/unverified name collisions better when new
34651 routerinfo's arrive in a directory.
34652 - Sometimes routers were getting entered into the stats before
34653 we'd assigned their identity_digest. Oops.
34654 - Only pick and establish intro points after we've gotten a
34657 - AllowUnverifiedNodes config option to let circuits choose no-name
34658 routers in entry,middle,exit,introduction,rendezvous positions.
34659 Allow middle and rendezvous positions by default.
34660 - Add a man page for tor-resolve.
34663 Changes in version 0.0.7.3 - 2004-08-12
34664 o Stop dnsworkers from triggering an assert failure when you
34665 ask them to resolve the host "".
34668 Changes in version 0.0.8pre3 - 2004-08-09
34669 o Changes from 0.0.7.2:
34670 - Allow multiple ORs with same nickname in routerlist -- now when
34671 people give us one identity key for a nickname, then later
34672 another, we don't constantly complain until the first expires.
34673 - Remember used bandwidth (both in and out), and publish 15-minute
34674 snapshots for the past day into our descriptor.
34675 - You can now fetch $DIRURL/running-routers to get just the
34676 running-routers line, not the whole descriptor list. (But
34677 clients don't use this yet.)
34678 - When people mistakenly use Tor as an http proxy, point them
34679 at the tor-doc.html rather than the INSTALL.
34680 - Remove our mostly unused -- and broken -- hex_encode()
34681 function. Use base16_encode() instead. (Thanks to Timo Lindfors
34682 for pointing out this bug.)
34683 - Rotate onion keys every 12 hours, not every 2 hours, so we have
34684 fewer problems with people using the wrong key.
34685 - Change the default exit policy to reject the default edonkey,
34686 kazaa, gnutella ports.
34687 - Add replace_file() to util.[ch] to handle win32's rename().
34689 o Changes from 0.0.8preX:
34690 - Fix two bugs in saving onion keys to disk when rotating, so
34691 hopefully we'll get fewer people using old onion keys.
34692 - Fix an assert error that was making SocksPolicy not work.
34693 - Be willing to expire routers that have an open dirport -- it's
34694 just the authoritative dirservers we want to not forget.
34695 - Reject tor-resolve requests for .onion addresses early, so we
34696 don't build a whole rendezvous circuit and then fail.
34697 - When you're warning a server that he's unverified, don't cry
34698 wolf unpredictably.
34699 - Fix a race condition: don't try to extend onto a connection
34700 that's still handshaking.
34701 - For servers in clique mode, require the conn to be open before
34702 you'll choose it for your path.
34703 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
34704 end relay cell, etc.
34705 - Measure bandwidth capacity over the last 24 hours, not just 12
34706 - Bugfix: authoritative dirservers were making and signing a new
34707 directory for each client, rather than reusing the cached one.
34710 Changes in version 0.0.8pre2 - 2004-08-04
34711 o Changes from 0.0.7.2:
34713 - Check directory signature _before_ you decide whether you're
34714 you're running an obsolete version and should exit.
34715 - Check directory signature _before_ you parse the running-routers
34716 list to decide who's running or verified.
34717 - Bugfixes and features:
34718 - Check return value of fclose while writing to disk, so we don't
34719 end up with broken files when servers run out of disk space.
34720 - Log a warning if the user uses an unsafe socks variant, so people
34721 are more likely to learn about privoxy or socat.
34722 - Dirservers now include RFC1123-style dates in the HTTP headers,
34723 which one day we will use to better detect clock skew.
34725 o Changes from 0.0.8pre1:
34726 - Make it compile without warnings again on win32.
34727 - Log a warning if you're running an unverified server, to let you
34728 know you might want to get it verified.
34729 - Only pick a default nickname if you plan to be a server.
34732 Changes in version 0.0.8pre1 - 2004-07-23
34734 - Made our unit tests compile again on OpenBSD 3.5, and tor
34735 itself compile again on OpenBSD on a sparc64.
34736 - We were neglecting milliseconds when logging on win32, so
34737 everything appeared to happen at the beginning of each second.
34739 o Protocol changes:
34740 - 'Extend' relay cell payloads now include the digest of the
34741 intended next hop's identity key. Now we can verify that we're
34742 extending to the right router, and also extend to routers we
34743 hadn't heard of before.
34746 - Tor nodes can now act as relays (with an advertised ORPort)
34747 without being manually verified by the dirserver operators.
34748 - Uploaded descriptors of unverified routers are now accepted
34749 by the dirservers, and included in the directory.
34750 - Verified routers are listed by nickname in the running-routers
34751 list; unverified routers are listed as "$<fingerprint>".
34752 - We now use hash-of-identity-key in most places rather than
34753 nickname or addr:port, for improved security/flexibility.
34754 - To avoid Sybil attacks, paths still use only verified servers.
34755 But now we have a chance to play around with hybrid approaches.
34756 - Nodes track bandwidth usage to estimate capacity (not used yet).
34757 - ClientOnly option for nodes that never want to become servers.
34758 - Directory caching.
34759 - "AuthoritativeDir 1" option for the official dirservers.
34760 - Now other nodes (clients and servers) will cache the latest
34761 directory they've pulled down.
34762 - They can enable their DirPort to serve it to others.
34763 - Clients will pull down a directory from any node with an open
34764 DirPort, and check the signature/timestamp correctly.
34765 - Authoritative dirservers now fetch directories from other
34766 authdirservers, to stay better synced.
34767 - Running-routers list tells who's down also, along with noting
34768 if they're verified (listed by nickname) or unverified (listed
34770 - Allow dirservers to serve running-router list separately.
34771 This isn't used yet.
34772 - ORs connect-on-demand to other ORs
34773 - If you get an extend cell to an OR you're not connected to,
34774 connect, handshake, and forward the create cell.
34775 - The authoritative dirservers stay connected to everybody,
34776 and everybody stays connected to 0.0.7 servers, but otherwise
34777 clients/servers expire unused connections after 5 minutes.
34778 - When servers get a sigint, they delay 30 seconds (refusing new
34779 connections) then exit. A second sigint causes immediate exit.
34780 - File and name management:
34781 - Look for .torrc if no CONFDIR "torrc" is found.
34782 - If no datadir is defined, then choose, make, and secure ~/.tor
34784 - If torrc not found, exitpolicy reject *:*.
34785 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
34786 - If no nickname is defined, derive default from hostname.
34787 - Rename secret key files, e.g. identity.key -> secret_id_key,
34788 to discourage people from mailing their identity key to tor-ops.
34789 - Refuse to build a circuit before the directory has arrived --
34790 it won't work anyway, since you won't know the right onion keys
34792 - Try other dirservers immediately if the one you try is down. This
34793 should tolerate down dirservers better now.
34794 - Parse tor version numbers so we can do an is-newer-than check
34795 rather than an is-in-the-list check.
34796 - New socks command 'resolve', to let us shim gethostbyname()
34798 - A 'tor_resolve' script to access the socks resolve functionality.
34799 - A new socks-extensions.txt doc file to describe our
34800 interpretation and extensions to the socks protocols.
34801 - Add a ContactInfo option, which gets published in descriptor.
34802 - Publish OR uptime in descriptor (and thus in directory) too.
34803 - Write tor version at the top of each log file
34804 - New docs in the tarball:
34806 - Document that you should proxy your SSL traffic too.
34809 Changes in version 0.0.7.2 - 2004-07-07
34810 o A better fix for the 0.0.0.0 problem, that will hopefully
34811 eliminate the remaining related assertion failures.
34814 Changes in version 0.0.7.1 - 2004-07-04
34815 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
34816 since internally we use 0.0.0.0 to signify "not yet resolved".
34819 Changes in version 0.0.7 - 2004-06-07
34820 o Updated the man page to reflect the new features.
34823 Changes in version 0.0.7rc2 - 2004-06-06
34824 o Changes from 0.0.7rc1:
34825 - Make it build on Win32 again.
34826 o Changes from 0.0.6.2:
34827 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
34831 Changes in version 0.0.7rc1 - 2004-06-02
34833 - On sighup, we were adding another log without removing the first
34834 one. So log messages would get duplicated n times for n sighups.
34835 - Several cases of using a connection after we'd freed it. The
34836 problem was that connections that are pending resolve are in both
34837 the pending_resolve tree, and also the circuit's resolving_streams
34838 list. When you want to remove one, you must remove it from both.
34839 - Fix a double-mark-for-close where an end cell arrived for a
34840 resolving stream, and then the resolve failed.
34841 - Check directory signatures based on name of signer, not on whom
34842 we got the directory from. This will let us cache directories more
34845 - Crank up some of our constants to handle more users.
34848 Changes in version 0.0.7pre1 - 2004-06-02
34849 o Fixes for crashes and other obnoxious bugs:
34850 - Fix an epipe bug: sometimes when directory connections failed
34851 to connect, we would give them a chance to flush before closing
34853 - When we detached from a circuit because of resolvefailed, we
34854 would immediately try the same circuit twice more, and then
34855 give up on the resolve thinking we'd tried three different
34857 - Limit the number of intro circuits we'll attempt to build for a
34858 hidden service per 15-minute period.
34859 - Check recommended-software string *early*, before actually parsing
34860 the directory. Thus we can detect an obsolete version and exit,
34861 even if the new directory format doesn't parse.
34862 o Fixes for security bugs:
34863 - Remember which nodes are dirservers when you startup, and if a
34864 random OR enables his dirport, don't automatically assume he's
34865 a trusted dirserver.
34867 - Directory connections were asking the wrong poll socket to
34868 start writing, and not asking themselves to start writing.
34869 - When we detached from a circuit because we sent a begin but
34870 didn't get a connected, we would use it again the first time;
34871 but after that we would correctly switch to a different one.
34872 - Stop warning when the first onion decrypt attempt fails; they
34873 will sometimes legitimately fail now that we rotate keys.
34874 - Override unaligned-access-ok check when $host_cpu is ia64 or
34875 arm. Apparently they allow it but the kernel whines.
34876 - Dirservers try to reconnect periodically too, in case connections
34878 - Fix some memory leaks in directory servers.
34879 - Allow backslash in Win32 filenames.
34880 - Made Tor build complain-free on FreeBSD, hopefully without
34881 breaking other BSD builds. We'll see.
34883 - Doxygen markup on all functions and global variables.
34884 - Make directory functions update routerlist, not replace it. So
34885 now directory disagreements are not so critical a problem.
34886 - Remove the upper limit on number of descriptors in a dirserver's
34887 directory (not that we were anywhere close).
34888 - Allow multiple logfiles at different severity ranges.
34889 - Allow *BindAddress to specify ":port" rather than setting *Port
34890 separately. Allow multiple instances of each BindAddress config
34891 option, so you can bind to multiple interfaces if you want.
34892 - Allow multiple exit policy lines, which are processed in order.
34893 Now we don't need that huge line with all the commas in it.
34894 - Enable accept/reject policies on SOCKS connections, so you can bind
34895 to 0.0.0.0 but still control who can use your OP.
34898 Changes in version 0.0.6.2 - 2004-05-16
34899 o Our integrity-checking digest was checking only the most recent cell,
34900 not the previous cells like we'd thought.
34901 Thanks to Stefan Mark for finding the flaw!
34904 Changes in version 0.0.6.1 - 2004-05-06
34905 o Fix two bugs in our AES counter-mode implementation (this affected
34906 onion-level stream encryption, but not TLS-level). It turns
34907 out we were doing something much more akin to a 16-character
34908 polyalphabetic cipher. Oops.
34909 Thanks to Stefan Mark for finding the flaw!
34910 o Retire moria3 as a directory server, and add tor26 as a directory
34914 Changes in version 0.0.6 - 2004-05-02
34915 [version bump only]
34918 Changes in version 0.0.6rc4 - 2004-05-01
34919 o Update the built-in dirservers list to use the new directory format
34920 o Fix a rare seg fault: if a node offering a hidden service attempts
34921 to build a circuit to Alice's rendezvous point and fails before it
34922 reaches the last hop, it retries with a different circuit, but
34924 o Handle windows socket errors correctly.
34927 Changes in version 0.0.6rc3 - 2004-04-28
34928 o Don't expire non-general excess circuits (if we had enough
34929 circuits open, we were expiring rendezvous circuits -- even
34930 when they had a stream attached. oops.)
34931 o Fetch randomness from /dev/urandom better (not via fopen/fread)
34932 o Better debugging for tls errors
34933 o Some versions of openssl have an SSL_pending function that erroneously
34934 returns bytes when there is a non-application record pending.
34935 o Set Content-Type on the directory and hidserv descriptor.
34936 o Remove IVs from cipher code, since AES-ctr has none.
34937 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
34938 o We were using an array of length zero in a few places.
34939 o win32's gethostbyname can't resolve an IP to an IP.
34940 o win32's close can't close a socket.
34943 Changes in version 0.0.6rc2 - 2004-04-26
34944 o Fix a bug where we were closing tls connections intermittently.
34945 It turns out openssl keeps its errors around -- so if an error
34946 happens, and you don't ask about it, and then another openssl
34947 operation happens and succeeds, and you ask if there was an error,
34948 it tells you about the first error. Fun fun.
34949 o Fix a bug that's been lurking since 27 may 03 (!)
34950 When passing back a destroy cell, we would use the wrong circ id.
34951 'Mostly harmless', but still worth fixing.
34952 o Since we don't support truncateds much, don't bother sending them;
34953 just close the circ.
34954 o check for <machine/limits.h> so we build on NetBSD again (I hope).
34955 o don't crash if a conn that sent a begin has suddenly lost its circuit
34956 (this was quite rare).
34959 Changes in version 0.0.6rc1 - 2004-04-25
34960 o We now rotate link (tls context) keys and onion keys.
34961 o CREATE cells now include oaep padding, so you can tell
34962 if you decrypted them correctly.
34963 o Add bandwidthburst to server descriptor.
34964 o Directories now say which dirserver signed them.
34965 o Use a tor_assert macro that logs failed assertions too.
34968 Changes in version 0.0.6pre5 - 2004-04-18
34969 o changes from 0.0.6pre4:
34970 - make tor build on broken freebsd 5.2 installs
34971 - fix a failed assert when you try an intro point, get a nack, and try
34972 a second one and it works.
34973 - when alice uses a port that the hidden service doesn't accept,
34974 it now sends back an end cell (denied by exit policy). otherwise
34975 alice would just have to wait to time out.
34976 - fix another rare bug: when we had tried all the intro
34977 points for a hidden service, we fetched the descriptor
34978 again, but we left our introcirc thinking it had already
34979 sent an intro, so it kept waiting for a response...
34980 - bugfix: when you sleep your hidden-service laptop, as soon
34981 as it wakes up it tries to upload a service descriptor, but
34982 socketpair fails for some reason (localhost not up yet?).
34983 now we simply give up on that upload, and we'll try again later.
34984 i'd still like to find the bug though.
34985 - if an intro circ waiting for an ack dies before getting one, then
34987 - we were reusing stale service descriptors and refetching usable
34991 Changes in version 0.0.6pre4 - 2004-04-14
34992 o changes from 0.0.6pre3:
34993 - when bob fails to connect to the rendezvous point, and his
34994 circ didn't fail because of the rendezvous point itself, then
34995 he retries a couple of times
34996 - we expire introduction and rendezvous circs more thoroughly
34997 (sometimes they were hanging around forever)
34998 - we expire unattached rendezvous streams that have been around
34999 too long (they were sticking around forever).
35000 - fix a measly fencepost error that was crashing everybody with
35004 Changes in version 0.0.6pre3 - 2004-04-14
35005 o changes from 0.0.6pre2:
35006 - make hup work again
35007 - fix some memory leaks for dirservers
35008 - allow more skew in rendezvous descriptor timestamps, to help
35009 handle people like blanu who don't know what time it is
35010 - normal circs are 3 hops, but some rend/intro circs are 4, if
35011 the initiator doesn't get to choose the last hop
35012 - send acks for introductions, so alice can know whether to try
35014 - bob publishes intro points more correctly
35015 o changes from 0.0.5:
35016 - fix an assert trigger that's been plaguing us since the days
35017 of 0.0.2prexx (thanks weasel!)
35018 - retry stream correctly when we fail to connect because of
35019 exit-policy-reject (should try another) or can't-resolve-address
35020 (also should try another, because dns on random internet servers
35022 - when we hup a dirserver and we've *removed* a server from the
35023 approved-routers list, now we remove that server from the
35024 in-memory directories too
35027 Changes in version 0.0.6pre2 - 2004-04-08
35028 o We fixed our base32 implementation. Now it works on all architectures.
35031 Changes in version 0.0.6pre1 - 2004-04-08
35033 - Hidden services and rendezvous points are implemented. Go to
35034 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
35035 hidden services. (This only works via a socks4a proxy such as
35036 Privoxy, and currently it's quite slow.)
35039 Changes in version 0.0.5 - 2004-03-30
35040 [version bump only]
35043 Changes in version 0.0.5rc3 - 2004-03-29
35044 o Install torrc as torrc.sample -- we no longer clobber your
35046 o Re-enable recommendedversion checking (we broke it in rc2, oops)
35047 o Add in a 'notice' log level for things the operator should hear
35048 but that aren't warnings
35051 Changes in version 0.0.5rc2 - 2004-03-29
35052 o Hold socks connection open until reply is flushed (if possible)
35053 o Make exit nodes resolve IPs to IPs immediately, rather than asking
35054 the dns farm to do it.
35055 o Fix c99 aliasing warnings in rephist.c
35056 o Don't include server descriptors that are older than 24 hours in the
35058 o Give socks 'reject' replies their whole 15s to attempt to flush,
35059 rather than seeing the 60s timeout and assuming the flush had failed.
35060 o Clean automake droppings from the cvs repository
35063 Changes in version 0.0.5rc1 - 2004-03-28
35064 o Fix mangled-state bug in directory fetching (was causing sigpipes).
35065 o Only build circuits after we've fetched the directory: clients were
35066 using only the directory servers before they'd fetched a directory.
35067 This also means longer startup time; so it goes.
35068 o Fix an assert trigger where an OP would fail to handshake, and we'd
35069 expect it to have a nickname.
35070 o Work around a tsocks bug: do a socks reject when AP connection dies
35071 early, else tsocks goes into an infinite loop.
35074 Changes in version 0.0.4 - 2004-03-26
35075 o When connecting to a dirserver or OR and the network is down,
35079 Changes in version 0.0.3 - 2004-03-26
35080 o Warn and fail if server chose a nickname with illegal characters
35081 o Port to Solaris and Sparc:
35082 - include missing header fcntl.h
35083 - have autoconf find -lsocket -lnsl automatically
35084 - deal with hardware word alignment
35085 - make uname() work (solaris has a different return convention)
35086 - switch from using signal() to sigaction()
35087 o Preliminary work on reputation system:
35088 - Keep statistics on success/fail of connect attempts; they're published
35089 by kill -USR1 currently.
35090 - Add a RunTesting option to try to learn link state by creating test
35091 circuits, even when SocksPort is off.
35092 - Remove unused open circuits when there are too many.
35095 Changes in version 0.0.2 - 2004-03-19
35096 - Include strlcpy and strlcat for safer string ops
35097 - define INADDR_NONE so we compile (but still not run) on solaris
35100 Changes in version 0.0.2pre27 - 2004-03-14
35102 - Allow internal tor networks (we were rejecting internal IPs,
35103 now we allow them if they're set explicitly).
35104 - And fix a few endian issues.
35107 Changes in version 0.0.2pre26 - 2004-03-14
35109 - If a stream times out after 15s without a connected cell, don't
35110 try that circuit again: try a new one.
35111 - Retry streams at most 4 times. Then give up.
35112 - When a dirserver gets a descriptor from an unknown router, it
35113 logs its fingerprint (so the dirserver operator can choose to
35114 accept it even without mail from the server operator).
35115 - Inform unapproved servers when we reject their descriptors.
35116 - Make tor build on Windows again. It works as a client, who knows
35118 - Clearer instructions in the torrc for how to set up a server.
35119 - Be more efficient about reading fd's when our global token bucket
35120 (used for rate limiting) becomes empty.
35122 - Stop asserting that computers always go forward in time. It's
35124 - When we sent a cell (e.g. destroy) and then marked an OR connection
35125 expired, we might close it before finishing a flush if the other
35126 side isn't reading right then.
35127 - Don't allow dirservers to start if they haven't defined
35128 RecommendedVersions
35129 - We were caching transient dns failures. Oops.
35130 - Prevent servers from publishing an internal IP as their address.
35131 - Address a strcat vulnerability in circuit.c
35134 Changes in version 0.0.2pre25 - 2004-03-04
35136 - Put the OR's IP in its router descriptor, not its fqdn. That way
35137 we'll stop being stalled by gethostbyname for nodes with flaky dns,
35140 - If the user typed in an address that didn't resolve, the server
35144 Changes in version 0.0.2pre24 - 2004-03-03
35146 - Fix an assertion failure in dns.c, where we were trying to dequeue
35147 a pending dns resolve even if it wasn't pending
35148 - Fix a spurious socks5 warning about still trying to write after the
35149 connection is finished.
35150 - Hold certain marked_for_close connections open until they're finished
35151 flushing, rather than losing bytes by closing them too early.
35152 - Correctly report the reason for ending a stream
35153 - Remove some duplicate calls to connection_mark_for_close
35154 - Put switch_id and start_daemon earlier in the boot sequence, so it
35155 will actually try to chdir() to options.DataDirectory
35156 - Make 'make test' exit(1) if a test fails; fix some unit tests
35157 - Make tor fail when you use a config option it doesn't know about,
35158 rather than warn and continue.
35159 - Make --version work
35160 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
35163 Changes in version 0.0.2pre23 - 2004-02-29
35165 - Print a statement when the first circ is finished, so the user
35166 knows it's working.
35167 - If a relay cell is unrecognized at the end of the circuit,
35168 send back a destroy. (So attacks to mutate cells are more
35170 - New config option 'excludenodes' to avoid certain nodes for circuits.
35171 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
35172 so you can collect coredumps there.
35174 - Fix a bug in tls flushing where sometimes data got wedged and
35175 didn't flush until more data got sent. Hopefully this bug was
35176 a big factor in the random delays we were seeing.
35177 - Make 'connected' cells include the resolved IP, so the client
35178 dns cache actually gets populated.
35179 - Disallow changing from ORPort=0 to ORPort>0 on hup.
35180 - When we time-out on a stream and detach from the circuit, send an
35181 end cell down it first.
35182 - Only warn about an unknown router (in exitnodes, entrynodes,
35183 excludenodes) after we've fetched a directory.
35186 Changes in version 0.0.2pre22 - 2004-02-26
35188 - Servers publish less revealing uname information in descriptors.
35189 - More memory tracking and assertions, to crash more usefully when
35191 - If the default torrc isn't there, just use some default defaults.
35192 Plus provide an internal dirservers file if they don't have one.
35193 - When the user tries to use Tor as an http proxy, give them an http
35194 501 failure explaining that we're a socks proxy.
35195 - Dump a new router.desc on hup, to help confused people who change
35196 their exit policies and then wonder why router.desc doesn't reflect
35198 - Clean up the generic tor.sh init script that we ship with.
35200 - If the exit stream is pending on the resolve, and a destroy arrives,
35201 then the stream wasn't getting removed from the pending list. I
35202 think this was the one causing recent server crashes.
35203 - Use a more robust poll on OSX 10.3, since their poll is flaky.
35204 - When it couldn't resolve any dirservers, it was useless from then on.
35205 Now it reloads the RouterFile (or default dirservers) if it has no
35207 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
35208 many users don't even *have* a /usr/local/sbin/.
35211 Changes in version 0.0.2pre21 - 2004-02-18
35213 - There's a ChangeLog file that actually reflects the changelog.
35214 - There's a 'torify' wrapper script, with an accompanying
35215 tor-tsocks.conf, that simplifies the process of using tsocks for
35216 tor. It even has a man page.
35217 - The tor binary gets installed to sbin rather than bin now.
35218 - Retry streams where the connected cell hasn't arrived in 15 seconds
35219 - Clean up exit policy handling -- get the default out of the torrc,
35220 so we can update it without forcing each server operator to fix
35222 - Allow imaps and pop3s in default exit policy
35224 - Prevent picking middleman nodes as the last node in the circuit
35227 Changes in version 0.0.2pre20 - 2004-01-30
35229 - We now have a deb package, and it's in debian unstable. Go to
35230 it, apt-getters. :)
35231 - I've split the TotalBandwidth option into BandwidthRate (how many
35232 bytes per second you want to allow, long-term) and
35233 BandwidthBurst (how many bytes you will allow at once before the cap
35234 kicks in). This better token bucket approach lets you, say, set
35235 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
35236 performance while not exceeding your monthly bandwidth quota.
35237 - Push out a tls record's worth of data once you've got it, rather
35238 than waiting until you've read everything waiting to be read. This
35239 may improve performance by pipelining better. We'll see.
35240 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
35241 from failed circuits (if they haven't been connected yet) and attach
35243 - Expire old streams that haven't managed to connect. Some day we'll
35244 have them reattach to new circuits instead.
35247 - Fix several memory leaks that were causing servers to become bloated
35249 - Fix a few very rare assert triggers. A few more remain.
35250 - Setuid to User _before_ complaining about running as root.
35253 Changes in version 0.0.2pre19 - 2004-01-07
35255 - Fix deadlock condition in dns farm. We were telling a child to die by
35256 closing the parent's file descriptor to him. But newer children were
35257 inheriting the open file descriptor from the parent, and since they
35258 weren't closing it, the socket never closed, so the child never read
35259 eof, so he never knew to exit. Similarly, dns workers were holding
35260 open other sockets, leading to all sorts of chaos.
35261 - New cleaner daemon() code for forking and backgrounding.
35262 - If you log to a file, it now prints an entry at the top of the
35263 logfile so you know it's working.
35264 - The onionskin challenge length was 30 bytes longer than necessary.
35265 - Started to patch up the spec so it's not quite so out of date.
35268 Changes in version 0.0.2pre18 - 2004-01-02
35270 - Fix endian issues with the 'integrity' field in the relay header.
35271 - Fix a potential bug where connections in state
35272 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
35275 Changes in version 0.0.2pre17 - 2003-12-30
35277 - Made --debuglogfile (or any second log file, actually) work.
35278 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
35279 adversary could force us into an infinite loop.
35282 - Each onionskin handshake now includes a hash of the computed key,
35283 to prove the server's identity and help perfect forward secrecy.
35284 - Changed cell size from 256 to 512 bytes (working toward compatibility
35286 - Changed cell length to 2 bytes, and moved it to the relay header.
35287 - Implemented end-to-end integrity checking for the payloads of
35289 - Separated streamid from 'recognized' (otherwise circuits will get
35290 messed up when we try to have streams exit from the middle). We
35291 use the integrity-checking to confirm that a cell is addressed to
35293 - Randomize the initial circid and streamid values, so an adversary who
35294 breaks into a node can't learn how many circuits or streams have
35298 Changes in version 0.0.2pre16 - 2003-12-14
35300 - Fixed a bug that made HUP trigger an assert
35301 - Fixed a bug where a circuit that immediately failed wasn't being
35302 counted as a failed circuit in counting retries.
35305 - Now we close the circuit when we get a truncated cell: otherwise we're
35306 open to an anonymity attack where a bad node in the path truncates
35307 the circuit and then we open streams at him.
35308 - Add port ranges to exit policies
35309 - Add a conservative default exit policy
35310 - Warn if you're running tor as root
35311 - on HUP, retry OR connections and close/rebind listeners
35312 - options.EntryNodes: try these nodes first when picking the first node
35313 - options.ExitNodes: if your best choices happen to include any of
35314 your preferred exit nodes, you choose among just those preferred
35316 - options.ExcludedNodes: nodes that are never picked in path building
35319 Changes in version 0.0.2pre15 - 2003-12-03
35320 o Robustness and bugfixes:
35321 - Sometimes clients would cache incorrect DNS resolves, which would
35322 really screw things up.
35323 - An OP that goes offline would slowly leak all its sockets and stop
35325 - A wide variety of bugfixes in exit node selection, exit policy
35326 handling, and processing pending streams when a new circuit is
35328 - Pick nodes for a path only from those the directory says are up
35329 - Choose randomly from all running dirservers, not always the first one
35330 - Increase allowed http header size for directory fetch.
35331 - Stop writing to stderr (if we're daemonized it will be closed).
35332 - Enable -g always, so cores will be more useful to me.
35333 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
35336 - Wrote a man page. It lists commonly used options.
35339 - Change default loglevel to warn.
35340 - Make PidFile default to null rather than littering in your CWD.
35341 - OnionRouter config option is now obsolete. Instead it just checks
35343 - Moved to a single unified torrc file for both clients and servers.
35346 Changes in version 0.0.2pre14 - 2003-11-29
35347 o Robustness and bugfixes:
35348 - Force the admin to make the DataDirectory himself
35349 - to get ownership/permissions right
35350 - so clients no longer make a DataDirectory and then never use it
35351 - fix bug where a client who was offline for 45 minutes would never
35352 pull down a directory again
35353 - fix (or at least hide really well) the dns assert bug that was
35354 causing server crashes
35355 - warnings and improved robustness wrt clockskew for certs
35356 - use the native daemon(3) to daemonize, when available
35357 - exit if bind() fails
35358 - exit if neither socksport nor orport is defined
35359 - include our own tor_timegm (Win32 doesn't have its own)
35360 - bugfix for win32 with lots of connections
35361 - fix minor bias in PRNG
35362 - make dirserver more robust to corrupt cached directory
35365 - Wrote the design document (woo)
35367 o Circuit building and exit policies:
35368 - Circuits no longer try to use nodes that the directory has told them
35370 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
35371 bitcounts (18.0.0.0/8).
35372 - Make AP connections standby for a circuit if no suitable circuit
35373 exists, rather than failing
35374 - Circuits choose exit node based on addr/port, exit policies, and
35375 which AP connections are standing by
35376 - Bump min pathlen from 2 to 3
35377 - Relay end cells have a payload to describe why the stream ended.
35378 - If the stream failed because of exit policy, try again with a new
35380 - Clients have a dns cache to remember resolved addresses.
35381 - Notice more quickly when we have no working circuits
35384 - APPort is now called SocksPort
35385 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
35387 - RecommendedVersions is now a config variable rather than
35388 hardcoded (for dirservers)
35389 - Reloads config on HUP
35390 - Usage info on -h or --help
35391 - If you set User and Group config vars, it'll setu/gid to them.
35394 Changes in version 0.0.2pre13 - 2003-10-19
35395 o General stability:
35396 - SSL_write no longer fails when it returns WANTWRITE and the number
35397 of bytes in the buf has changed by the next SSL_write call.
35398 - Fix segfault fetching directory when network is down
35399 - Fix a variety of minor memory leaks
35400 - Dirservers reload the fingerprints file on HUP, so I don't have
35401 to take down the network when I approve a new router
35402 - Default server config file has explicit Address line to specify fqdn
35405 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
35406 - Make listener connections not ever alloc bufs
35408 o Autoconf improvements:
35409 - don't clobber an external CFLAGS in ./configure
35410 - Make install now works
35411 - create var/lib/tor on make install
35412 - autocreate a tor.sh initscript to help distribs
35413 - autocreate the torrc and sample-server-torrc with correct paths
35415 o Log files and Daemonizing now work:
35416 - If --DebugLogFile is specified, log to it at -l debug
35417 - If --LogFile is specified, use it instead of commandline
35418 - If --RunAsDaemon is set, tor forks and backgrounds on startup