1 Changes in version 0.4.3.2-alpha - 2020-02-10
2 This is the second stable alpha release in the Tor 0.4.3.x series. It
3 fixes several bugs present in the previous alpha release. Anybody
4 running the previous alpha should upgrade, and look for bugs in this
7 o Major bugfixes (Onion service client, authorization):
8 - On a NEWNYM signal, purge the ephemeral client authorization
9 cache. The permanent ones are kept. Fixes bug 33139; bugfix
12 o Minor features (best practices tracker):
13 - Practracker now supports a --regen-overbroad option to regenerate
14 the exceptions file, but only to revise exceptions to be _less_
15 tolerant of best-practices violations. Closes ticket 32372.
17 o Minor features (continuous integration):
18 - Run Doxygen Makefile target on Travis. Closes ticket 32455.
19 - Stop allowing failures on the Travis CI stem tests job. It looks
20 like all the stem hangs we were seeing before are now fixed.
23 o Minor bugfixes (build system):
24 - Some configure options were either missing or incorrect in the
25 configure summary. Fixes bug 32230; bugfix on 0.4.3.1-alpha.
27 o Minor bugfixes (controller protocol):
28 - Fix a memory leak introduced by refactoring of control reply
29 formatting code. Fixes bug 33039; bugfix on 0.4.3.1-alpha.
30 - Fix a memory leak in GETINFO responses. Fixes bug 33103; bugfix
32 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
33 report them as SIGNAL events. Fixes bug 33104; bugfix
36 o Minor bugfixes (logging):
37 - If we encounter a bug when flushing a buffer to a TLS connection,
38 only log the bug once per invocation of the Tor process.
39 Previously we would log with every occurrence, which could cause
40 us to run out of disk space. Fixes bug 33093; bugfix
42 - When logging a bug, do not say "Future instances of this warning
43 will be silenced" unless we are actually going to do so.
44 Previously we would say this whenever a BUG() check failed in the
45 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
47 o Minor bugfixes (onion service v2):
48 - Move a series of warnings to protocol warning level because they
49 can all be triggered remotely by a malformed request. Fixes bug
50 32706; bugfix on 0.1.1.14-alpha.
52 o Minor bugfixes (onion service v3, client authorization):
53 - When removing client authorization credentials using the control
54 port, also remove the associated descriptor so they don't linger
55 and are still usable hence making the onion service behind client
56 authorization reachable. Fixes bug 33148; bugfix on 0.4.3.1-alpha.
58 o Minor bugfixes (pluggable transports):
59 - Lower the log level of standard error messages from a PT from
60 warning to info. Fixes bug 33005; bugfix on 0.4.0.1-alpha.
62 o Minor bugfixes (rust, build):
63 - Fix a syntax warning given by newer versions of Rust, and creating
64 problems for our continuous integration. Fixes bug 33212; bugfix
67 o Minor bugfixes (TLS bug handling):
68 - When encountering a bug in buf_read_freom_tls(), return a "MISC"
69 error code rather than "WANTWRITE". This change might help avoid
70 some CPU-wasting loops if the bug is ever triggered. Bug reported
71 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
73 o Code simplification and refactoring (mainloop):
74 - Simplify the ip_address_changed() function by removing redundant
75 checks. Closes ticket 33091.
77 o Documentation (manpage):
78 - Split Circuit Timeout options and Node Selection options into
79 their own sections of the tor manpage. Closes tickets 32928 and
80 32929. Work by Swati Thacker as part of Google Season of Docs.
83 Changes in version 0.4.2.6 - 2020-01-30
84 This is the second stable release in the 0.4.2.x series. It backports
85 several bugfixes from 0.4.3.1-alpha, including some that had affected
86 the Linux seccomp2 sandbox or Windows services. If you're running with
87 one of those configurations, you'll probably want to upgrade;
88 otherwise, you should be fine with 0.4.2.5.
90 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
91 - Correct how we use libseccomp. Particularly, stop assuming that
92 rules are applied in a particular order or that more rules are
93 processed after the first match. Neither is the case! In
94 libseccomp <2.4.0 this led to some rules having no effect.
95 libseccomp 2.4.0 changed how rules are generated, leading to a
96 different ordering, which in turn led to a fatal crash during
97 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
99 - Fix crash when reloading logging configuration while the
100 experimental sandbox is enabled. Fixes bug 32841; bugfix on
101 0.4.1.7. Patch by Peter Gerber.
103 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
104 - Use GCC/Clang's printf-checking feature to make sure that
105 tor_assertf() arguments are correctly typed. Fixes bug 32765;
106 bugfix on 0.4.1.1-alpha.
108 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
109 - Avoid a possible crash when trying to log a (fatal) assertion
110 failure about mismatched magic numbers in configuration objects.
111 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
113 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
114 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
115 test_practracker.sh script. Doing so caused a test failure. Fixes
116 bug 32705; bugfix on 0.4.2.1-alpha.
117 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
118 skipping practracker checks. Fixes bug 32705; bugfix
121 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
122 - Initialize the publish/subscribe system when running as a windows
123 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
125 o Testing (backport from 0.4.3.1-alpha):
126 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
127 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
128 fix the sandbox errors in 32722. Closes ticket 32240.
129 - Re-enable the Travis CI macOS Chutney build, but don't let it
130 prevent the Travis job from finishing. (The Travis macOS jobs are
131 slow, so we don't want to have it delay the whole CI process.)
134 o Testing (continuous integration, backport from 0.4.3.1-alpha):
135 - Use zstd in our Travis Linux builds. Closes ticket 32242.
138 Changes in version 0.4.1.8 - 2020-01-30
139 This release backports several bugfixes from later release series,
140 including some that had affected the Linux seccomp2 sandbox or Windows
141 services. If you're running with one of those configurations, you'll
142 probably want to upgrade; otherwise, you should be fine with your
143 current version of 0.4.1.x.
145 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
146 - Correct how we use libseccomp. Particularly, stop assuming that
147 rules are applied in a particular order or that more rules are
148 processed after the first match. Neither is the case! In
149 libseccomp <2.4.0 this led to some rules having no effect.
150 libseccomp 2.4.0 changed how rules are generated, leading to a
151 different ordering, which in turn led to a fatal crash during
152 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
154 - Fix crash when reloading logging configuration while the
155 experimental sandbox is enabled. Fixes bug 32841; bugfix on
156 0.4.1.7. Patch by Peter Gerber.
158 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
159 - When running Tor with an option like --verify-config or
160 --dump-config that does not start the event loop, avoid crashing
161 if we try to exit early because of an error. Fixes bug 32407;
162 bugfix on 0.3.3.1-alpha.
164 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
165 - Initialize the publish/subscribe system when running as a windows
166 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
168 o Testing (backport from 0.4.3.1-alpha):
169 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
170 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
171 fix the sandbox errors in 32722. Closes ticket 32240.
172 - Re-enable the Travis CI macOS Chutney build, but don't let it
173 prevent the Travis job from finishing. (The Travis macOS jobs are
174 slow, so we don't want to have it delay the whole CI process.)
177 o Testing (continuous integration, backport from 0.4.3.1-alpha):
178 - Use zstd in our Travis Linux builds. Closes ticket 32242.
181 Changes in version 0.4.3.1-alpha - 2020-01-22
182 This is the first alpha release in the 0.4.3.x series. It includes
183 improved support for application integration of onion services, support
184 for building in a client-only mode, and newly improved internal
185 documentation (online at https://src-ref.docs.torproject.org/tor/). It
186 also has numerous other small bugfixes and features, as well as
187 improvements to our code's internal organization that should help us
188 write better code in the future.
190 o New system requirements:
191 - When building Tor, you now need to have Python 3 in order to run
192 the integration tests. (Python 2 is officially unsupported
193 upstream, as of 1 Jan 2020.) Closes ticket 32608.
195 o Major features (build system):
196 - The relay code can now be disabled using the --disable-module-relay
197 configure option. When this option is set, we also disable the
198 dirauth module. Closes ticket 32123.
199 - When Tor is compiled --disable-module-relay, we also omit the code
200 used to act as a directory cache. Closes ticket 32487.
202 o Major features (directory authority, ed25519):
203 - Add support for banning a relay's ed25519 keys in the approved-
204 routers file. This will help us migrate away from RSA keys in the
205 future. Previously, only RSA keys could be banned in approved-
206 routers. Resolves ticket 22029. Patch by Neel Chauhan.
208 o Major features (onion service, controller):
209 - New control port commands to manage client-side onion service
210 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
211 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
212 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
214 o Major features (onion service, SOCKS5):
215 - Introduce a new SocksPort flag, ExtendedErrors, to support more
216 detailed error codes in information for applications that support
217 them. Closes ticket 30382; implements proposal 304.
219 o Major features (proxy):
220 - In addition to its current supported proxy types (HTTP CONNECT,
221 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
222 HAProxy server. A new torrc option was added to specify the
223 address/port of the server: TCPProxy <protocol> <host>:<port>.
224 Currently the only supported protocol for the option is haproxy.
225 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
227 o Major bugfixes (linux seccomp sandbox):
228 - Correct how we use libseccomp. Particularly, stop assuming that
229 rules are applied in a particular order or that more rules are
230 processed after the first match. Neither is the case! In
231 libseccomp <2.4.0 this led to some rules having no effect.
232 libseccomp 2.4.0 changed how rules are generated, leading to a
233 different ordering, which in turn led to a fatal crash during
234 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
236 - Fix crash when reloading logging configuration while the
237 experimental sandbox is enabled. Fixes bug 32841; bugfix on
238 0.4.1.7. Patch by Peter Gerber.
240 o Major bugfixes (networking):
241 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
242 and accept strings as well as binary addresses. Fixes bug 32315;
243 bugfix on 0.3.5.1-alpha.
245 o Major bugfixes (onion service):
246 - Report HS circuit failure back into the HS subsystem so we take
247 appropriate action with regards to the client introduction point
248 failure cache. This improves reachability of onion services, since
249 now clients notice failing introduction circuits properly. Fixes
250 bug 32020; bugfix on 0.3.2.1-alpha.
252 o Minor feature (configure, build system):
253 - Output a list of enabled/disabled features at the end of the
254 configure process in a pleasing way. Closes ticket 31373.
256 o Minor feature (heartbeat, onion service):
257 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
258 message. Closes ticket 31371.
260 o Minor features (configuration validation):
261 - Configuration validation can now be done by per-module callbacks,
262 rather than a global validation function. This will let us reduce
263 the size of config.c and some of its more cumbersome functions.
266 o Minor features (configuration):
267 - If a configured hardware crypto accelerator in AccelName is
268 prefixed with "!", Tor now exits when it cannot be found. Closes
270 - We now use flag-driven logic to warn about obsolete configuration
271 fields, so that we can include their names. In 0.4.2, we used a
272 special type, which prevented us from generating good warnings.
273 Implements ticket 32404.
275 o Minor features (controller):
276 - Add stream isolation data to STREAM event. Closes ticket 19859.
277 - Implement a new GETINFO command to fetch microdescriptor
278 consensus. Closes ticket 31684.
280 o Minor features (debugging, directory system):
281 - Don't crash when we find a non-guard with a guard-fraction value
282 set. Instead, log a bug warning, in an attempt to figure out how
283 this happened. Diagnostic for ticket 32868.
285 o Minor features (defense in depth):
286 - Add additional checks around tor_vasprintf() usage, in case the
287 function returns an error. Patch by Tobias Stoeckmann. Fixes
290 o Minor features (developer tooling):
291 - Remove the 0.2.9.x series branches from git scripts (git-merge-
292 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
295 o Minor features (developer tools):
296 - Add a check_cocci_parse.sh script that checks that new code is
297 parseable by Coccinelle. Add an exceptions file for unparseable
298 files, and run the script from travis CI. Closes ticket 31919.
299 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
300 target. Closes ticket 31919.
301 - Add a rename_c_identifiers.py tool to rename a bunch of C
302 identifiers at once, and generate a well-formed commit message
303 describing the change. This should help with refactoring. Closes
305 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
306 semantic patching tool with the correct flags. These flags are
307 fairly easy to forget, and these scripts should help us use
308 Coccinelle more effectively in the future. Closes ticket 31705.
310 o Minor features (Doxygen):
311 - Update Doxygen configuration file to a more recent template (from
312 1.8.15). Closes ticket 32110.
313 - "make doxygen" now works with out-of-tree builds. Closes
315 - Make sure that doxygen outputs documentation for all of our C
316 files. Previously, some were missing @file declarations, causing
317 them to be ignored. Closes ticket 32307.
318 - Our "make doxygen" target now respects --enable-fatal-warnings by
319 default, and does not warn about items that are missing
320 documentation. To warn about missing documentation, run configure
321 with the "--enable-missing-doc-warnings" flag: doing so suspends
322 fatal warnings for doxygen. Closes ticket 32385.
324 o Minor features (git scripts):
325 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
326 customisation. Closes ticket 32347.
327 - Add git-setup-dirs.sh, which sets up an upstream git repository
328 and worktrees for tor maintainers. Closes ticket 29603.
329 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
330 remote. Closes ticket 32347.
331 - Call the check_cocci_parse.sh script from the git commit and push
332 hooks. Closes ticket 31919.
333 - Make git-push-all.sh skip unchanged branches when pushing to
334 upstream. The script already skipped unchanged test branches.
336 - Make git-setup-dirs.sh create a master symlink in the worktree
337 directory. Closes ticket 32347.
338 - Skip unmodified source files when doing some existing git hook
339 checks. Related to ticket 31919.
341 o Minor features (IPv6, client):
342 - Make Tor clients tell dual-stack exits that they prefer IPv6
343 connections. This change is equivalent to setting the PreferIPv6
344 flag on SOCKSPorts (and most other listener ports). Tor Browser
345 has been setting this flag for some time, and we want to remove a
346 client distinguisher at exits. Closes ticket 32637.
348 o Minor features (portability, android):
349 - When building for Android, disable some tests that depend on $HOME
350 and/or pwdb, which Android doesn't have. Closes ticket 32825.
351 Patch from Hans-Christoph Steiner.
353 o Minor features (relay modularity):
354 - Split the relay and server pluggable transport config code into
355 separate files in the relay module. Disable this code when the
356 relay module is disabled. Closes part of ticket 32213.
357 - When the relay module is disabled, reject attempts to set the
358 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
359 ServerTransport* options, rather than ignoring the values of these
360 options. Closes part of ticket 32213.
362 o Minor features (relay):
363 - When the relay module is disabled, change the default config so
364 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
366 o Minor features (release tools):
367 - Port our ChangeLog formatting and sorting tools to Python 3.
370 o Minor features (testing):
371 - Detect some common failure cases for test_parseconf.sh in
372 src/test/conf_failures. Closes ticket 32451.
373 - Allow test_parseconf.sh to test expected log outputs for successful
374 configs, as well as failed configs. Closes ticket 32451.
375 - The test_parseconf.sh script now supports result variants for any
376 combination of the optional libraries lzma, nss, and zstd. Closes
379 o Minor features (tests, Android):
380 - When running the unit tests on Android, create temporary files in
381 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
382 patch from Hans-Christoph Steiner.
384 o Minor bugfixes (bridges):
385 - Lowercase the configured value of BridgeDistribution before adding
386 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
388 o Minor bugfixes (build system):
389 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
390 bugfix on 0.4.1.2-alpha.
392 o Minor bugfixes (configuration handling):
393 - Make control_event_conf_changed() take in a config_line_t instead
394 of a smartlist of alternating key/value entries. Fixes bug 31531;
395 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
397 o Minor bugfixes (configuration):
398 - Check for multiplication overflow when parsing memory units inside
399 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
400 - When dumping the configuration, stop adding a trailing space after
401 the option name when there is no option value. This issue only
402 affects options that accept an empty value or list. (Most options
403 reject empty values, or delete the entire line from the dumped
404 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
405 - Avoid changing the user's value of HardwareAccel as stored by
406 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
407 bug 32382; bugfix on 0.2.2.1-alpha.
408 - When creating a KeyDirectory with the same location as the
409 DataDirectory (not recommended), respect the DataDirectory's
410 group-readable setting if one has not been set for the
411 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
413 o Minor bugfixes (controller):
414 - In routerstatus_has_changed(), check all the fields that are
415 output over the control port. Fixes bug 20218; bugfix
418 o Minor bugfixes (correctness checks):
419 - Use GCC/Clang's printf-checking feature to make sure that
420 tor_assertf() arguments are correctly typed. Fixes bug 32765;
421 bugfix on 0.4.1.1-alpha.
423 o Minor bugfixes (developer tools):
424 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
425 31336; bugfix on 0.4.1.2-alpha.
427 o Minor bugfixes (dirauth module):
428 - Split the dirauth config code into a separate file in the dirauth
429 module. Disable this code when the dirauth module is disabled.
431 - When the dirauth module is disabled, reject attempts to set the
432 AuthoritativeDir option, rather than ignoring the value of the
433 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
435 o Minor bugfixes (embedded Tor):
436 - When starting Tor any time after the first time in a process,
437 register the thread in which it is running as the main thread.
438 Previously, we only did this on Windows, which could lead to bugs
439 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
442 o Minor bugfixes (git scripts):
443 - Avoid sleeping before the last push in git-push-all.sh. Closes
445 - Forward all unrecognised arguments in git-push-all.sh to git push.
448 o Minor bugfixes (hidden service v3):
449 - Do not rely on a "circuit established" flag for intro circuits but
450 instead always query the HS circuit map. This is to avoid sync
451 issue with that flag and the map. Fixes bug 32094; bugfix
454 o Minor bugfixes (logging, crash):
455 - Avoid a possible crash when trying to log a (fatal) assertion
456 failure about mismatched magic numbers in configuration objects.
457 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
459 o Minor bugfixes (onion service v2):
460 - When sending the INTRO cell for a v2 Onion Service, look at the
461 failure cache alongside timeout values to check if the intro point
462 is marked as failed. Previously, we only looked at the relay
463 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
466 o Minor bugfixes (onion services v3, client):
467 - Properly handle the client rendezvous circuit timeout. Previously
468 Tor would sometimes timeout a rendezvous circuit awaiting the
469 introduction ACK, and find itself unable to re-establish all
470 circuits because the rendezvous circuit timed out too early. Fixes
471 bug 32021; bugfix on 0.3.2.1-alpha.
473 o Minor bugfixes (onion services):
474 - In cancel_descriptor_fetches(), use
475 connection_list_by_type_purpose() instead of
476 connection_list_by_type_state(). Fixes bug 32639; bugfix on
477 0.3.2.1-alpha. Patch by Neel Chauhan.
479 o Minor bugfixes (scripts):
480 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
481 bugfix on 0.4.0.1-alpha.
483 o Minor bugfixes (test):
484 - Use the same code to find the tor binary in all of our test
485 scripts. This change makes sure we are always using the coverage
486 binary when coverage is enabled. Fixes bug 32368; bugfix
489 o Minor bugfixes (testing):
490 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
491 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
492 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
493 test_practracker.sh script. Doing so caused a test failure. Fixes
494 bug 32705; bugfix on 0.4.2.1-alpha.
495 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
496 skipping practracker checks. Fixes bug 32705; bugfix
499 o Minor bugfixes (tests):
500 - Our option-validation tests no longer depend on specially
501 configured non-default, non-passing sets of options. Previously,
502 the tests had been written to assume that options would _not_ be
503 set to their defaults, which led to needless complexity and
504 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
506 o Minor bugfixes (windows service):
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 Deprecated features:
511 - Deprecate the ClientAutoIPv6ORPort option. This option was not
512 true "Happy Eyeballs", and often failed on connections that
513 weren't reliably dual-stack. Closes ticket 32942. Patch by
517 - Provide a quickstart guide for a Circuit Padding Framework, and
518 documentation for researchers to implement and study circuit
519 padding machines. Closes ticket 28804.
520 - Add documentation in 'HelpfulTools.md' to describe how to build a
521 tag file. Closes ticket 32779.
522 - Create a high-level description of the long-term software
523 architecture goals. Closes ticket 32206.
524 - Describe the --dump-config command in the manual page. Closes
526 - Unite coding advice from this_not_that.md in torguts repo into our
527 coding standards document. Resolves ticket 31853.
530 - Our Doxygen configuration no longer generates LaTeX output. The
531 reference manual produced by doing this was over 4000 pages long,
532 and generally unusable. Closes ticket 32099.
533 - The option "TestingEstimatedDescriptorPropagationTime" is now
534 marked as obsolete. It has had no effect since 0.3.0.7, when
535 clients stopped rejecting consensuses "from the future". Closes
537 - We no longer support consensus methods before method 28; these
538 methods were only used by authorities running versions of Tor that
539 are now at end-of-life. In effect, this means that clients,
540 relays, and authorities now assume that authorities will be
541 running version 0.3.5.x or later. Closes ticket 32695.
544 - Add more test cases for tor's UTF-8 validation function. Also,
545 check the arguments passed to the function for consistency. Closes
547 - Improve test coverage for relay and dirauth config code, focusing
548 on option validation and normalization. Closes ticket 32213.
549 - Improve the consistency of test_parseconf.sh output, and run all
550 the tests, even if one fails. Closes ticket 32213.
551 - Re-enable the Travis CI macOS Chutney build, but don't let it
552 prevent the Travis job from finishing. (The Travis macOS jobs are
553 slow, so we don't want to have it delay the whole CI process.)
555 - Run the practracker unit tests in the pre-commit git hook. Closes
557 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
558 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
559 fix the sandbox errors in 32722. Closes ticket 32240.
561 o Code simplification and refactoring (channel):
562 - Channel layer had a variable length cell handler that was not used
563 and thus removed. Closes ticket 32892.
565 o Code simplification and refactoring (configuration):
566 - Immutability is now implemented as a flag on individual
567 configuration options rather than as part of the option-transition
568 checking code. Closes ticket 32344.
569 - Instead of keeping a list of configuration options to check for
570 relative paths, check all the options whose type is "FILENAME".
571 Solves part of ticket 32339.
572 - Our default log (which ordinarily sends NOTICE-level messages to
573 standard output) is now handled in a more logical manner.
574 Previously, we replaced the configured log options if they were
575 empty. Now, we interpret an empty set of log options as meaning
576 "use the default log". Closes ticket 31999.
577 - Remove some unused arguments from the options_validate() function,
578 to simplify our code and tests. Closes ticket 32187.
579 - Simplify the options_validate() code so that it looks at the
580 default options directly, rather than taking default options as an
581 argument. This change lets us simplify its interface. Closes
583 - Use our new configuration architecture to move most authority-
584 related options to the directory authority module. Closes
586 - When parsing the command line, handle options that determine our
587 "quiet level" and our mode of operation (e.g., --dump-config and
588 so on) all in one table. Closes ticket 32003.
590 o Code simplification and refactoring (controller):
591 - Create a new abstraction for formatting control protocol reply
592 lines based on key-value pairs. Refactor some existing control
593 protocol code to take advantage of this. Closes ticket 30984.
594 - Create a helper function that can fetch network status or
595 microdesc consensuses. Closes ticket 31684.
597 o Code simplification and refactoring (dirauth modularization):
598 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
600 - Replace some confusing identifiers in process_descs.c. Closes
602 - Simplify some relay and dirauth config code. Closes ticket 32213.
604 o Code simplification and refactoring (misc):
605 - Make all the structs we declare follow the same naming convention
606 of ending with "_t". Closes ticket 32415.
607 - Move and rename some configuration-related code for clarity.
609 - Our include.am files are now broken up by subdirectory.
610 Previously, src/core/include.am covered all of the subdirectories
611 in "core", "feature", and "app". Closes ticket 32137.
612 - Remove underused NS*() macros from test code: they make our tests
613 more confusing, especially for code-formatting tools. Closes
616 o Code simplification and refactoring (relay modularization):
617 - Disable relay_periodic when the relay module is disabled. Closes
619 - Disable relay_sys when the relay module is disabled. Closes
622 o Code simplification and refactoring (tool support):
623 - Add numerous missing dependencies to our include files, so that
624 they can be included in different reasonable orders and still
625 compile. Addresses part of ticket 32764.
626 - Fix some parts of our code that were difficult for Coccinelle to
627 parse. Related to ticket 31705.
628 - Fix some small issues in our code that prevented automatic
629 formatting tools from working. Addresses part of ticket 32764.
631 o Documentation (manpage):
632 - Alphabetize the Client Options section of the tor manpage. Closes
634 - Alphabetize the General Options section of the tor manpage. Closes
636 - In the tor(1) manpage, reword and improve formatting of the
637 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
638 32277. Based on work by Swati Thacker as part of Google Season
640 - In the tor(1) manpage, reword and improve formatting of the FILES,
641 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
642 Swati Thacker as part of Google Season of Docs.
644 o Testing (circuit, EWMA):
645 - Add unit tests for circuitmux and EWMA subsystems. Closes
648 o Testing (continuous integration):
649 - Use zstd in our Travis Linux builds. Closes ticket 32242.
652 Changes in version 0.4.2.5 - 2019-12-09
653 This is the first stable release in the 0.4.2.x series. This series
654 improves reliability and stability, and includes several stability and
655 correctness improvements for onion services. It also fixes many smaller
656 bugs present in previous series.
658 Per our support policy, we will support the 0.4.2.x series for nine
659 months, or until three months after the release of a stable 0.4.3.x:
660 whichever is longer. If you need longer-term support, please stick
661 with 0.3.5.x, which will we plan to support until Feb 2022.
663 Per our support policy, we will support the 0.4.2.x series for nine
664 months, or until three months after the release of a stable 0.4.3.x:
665 whichever is longer. If you need longer-term support, please stick
666 with 0.3.5.x, which will we plan to support until Feb 2022.
668 Below are the changes since 0.4.1.4-rc. For a complete list of changes
669 since 0.4.1.5, see the ReleaseNotes file.
671 o Minor features (geoip):
672 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
673 Country database. Closes ticket 32685.
676 - Require C99 standards-conforming code in Travis CI, but allow GNU
677 gcc extensions. Also activates clang's -Wtypedef-redefinition
678 warnings. Build some jobs with -std=gnu99, and some jobs without.
682 Changes in version 0.4.1.7 - 2019-12-09
683 This release backports several bugfixes to improve stability and
684 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
685 including all relays relying on AccountingMax, should upgrade.
687 o Major features (directory authorities, backport from 0.4.2.2-alpha):
688 - Directory authorities now reject relays running all currently
689 deprecated release series. The currently supported release series
690 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
692 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
693 - Avoid a possible crash when restarting Tor in embedded mode and
694 enabling a different set of publish/subscribe messages. Fixes bug
695 31898; bugfix on 0.4.1.1-alpha.
697 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
698 - Relays now respect their AccountingMax bandwidth again. When
699 relays entered "soft" hibernation (which typically starts when
700 we've hit 90% of our AccountingMax), we had stopped checking
701 whether we should enter hard hibernation. Soft hibernation refuses
702 new connections and new circuits, but the existing circuits can
703 continue, meaning that relays could have exceeded their configured
704 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
706 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
707 - Stop ignoring torrc options after an %include directive, when the
708 included directory ends with a file that does not contain any
709 config options (but does contain comments or whitespace). Fixes
710 bug 31408; bugfix on 0.3.1.1-alpha.
712 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
713 - Onion services now always use the exact number of intro points
714 configured with the HiddenServiceNumIntroductionPoints option (or
715 fewer if nodes are excluded). Before, a service could sometimes
716 pick more intro points than configured. Fixes bug 31548; bugfix
719 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
720 - When building on Appveyor and Travis, pass the "-k" flag to make,
721 so that we are informed of all compilation failures, not just the
722 first one or two. Closes ticket 31372.
724 o Minor features (geoip, backport from 0.4.2.5):
725 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
726 Country database. Closes ticket 32685.
728 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
729 - Avoid spurious errors when Appveyor CI fails before the install step.
730 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
732 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
733 - Fix a BUG() assertion that occurs within a very small race window
734 between when a client intro circuit opens and when its descriptor
735 gets cleaned up from the cache. The circuit is now closed early,
736 which will trigger a re-fetch of the descriptor and continue the
737 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
739 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
740 - Avoid trying to read data from closed connections, which can cause
741 needless loops in Libevent and infinite loops in Shadow. Fixes bug
742 30344; bugfix on 0.1.1.1-alpha.
744 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
745 - On abort, try harder to flush the output buffers of log messages.
746 On some platforms (macOS), log messages could be discarded when
747 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
748 - Report the tor version whenever an assertion fails. Previously, we
749 only reported the Tor version on some crashes, and some non-fatal
750 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
751 - When tor aborts due to an error, close log file descriptors before
752 aborting. Closing the logs makes some OSes flush log file buffers,
753 rather than deleting buffered log lines. Fixes bug 31594; bugfix
756 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
757 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
758 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
759 - Disable backtrace signal handlers when shutting down tor. Fixes
760 bug 31614; bugfix on 0.2.5.2-alpha.
761 - Rate-limit our the logging message about the obsolete .exit
762 notation. Previously, there was no limit on this warning, which
763 could potentially be triggered many times by a hostile website.
764 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
766 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
767 - Do not log a nonfatal assertion failure when receiving a VERSIONS
768 cell on a connection using the obsolete v1 link protocol. Log a
769 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
771 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
772 - Reset the periodic events' "enabled" flag when Tor is shut down
773 cleanly. Previously, this flag was left on, which caused periodic
774 events not to be re-enabled when Tor was relaunched in-process
775 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
778 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
779 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
780 31736; bugfix on 0.0.7.
782 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
783 - Remove overly strict assertions that triggered when a pluggable
784 transport failed to launch. Fixes bug 31091; bugfix
786 - Remove an assertion in the Unix process backend. This assertion
787 would trigger when we failed to find the executable for a child
788 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
790 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
791 - Avoid crashing when starting with a corrupt keys directory where
792 the old ntor key and the new ntor key are identical. Fixes bug
793 30916; bugfix on 0.2.4.8-alpha.
795 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
796 - When testing port rebinding, don't busy-wait for tor to log.
797 Instead, actually sleep for a short time before polling again.
798 Also improve the formatting of control commands and log messages.
799 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
801 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
802 - Avoid a map_anon_nofork test failure due to a signed/unsigned
803 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
805 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
806 - Log bugs about the TLS read buffer's length only once, rather than
807 filling the logs with similar warnings. Fixes bug 31939; bugfix
810 o Documentation (backport from 0.4.2.2-alpha):
811 - Explain why we can't destroy the backtrace buffer mutex. Explain
812 why we don't need to destroy the log mutex. Closes ticket 31736.
814 o Testing (continuous integration, backport from 0.4.2.3-alpha):
815 - Disable all but one Travis CI macOS build, to mitigate slow
816 scheduling of Travis macOS jobs. Closes ticket 32177.
817 - Run the chutney IPv6 networks as part of Travis CI. Closes
819 - Simplify the Travis CI build matrix, and optimise for build time.
821 - Use Windows Server 2019 instead of Windows Server 2016 in our
822 Appveyor builds. Closes ticket 32086.
824 o Testing (continuous integration, backport from 0.4.2.4-rc):
825 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
826 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
827 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
828 until we can fix some Bionic permissions issues (see ticket
829 32240). Related to ticket 31919.
830 - Install the mingw OpenSSL package in Appveyor. This makes sure
831 that the OpenSSL headers and libraries match in Tor's Appveyor
832 builds. (This bug was triggered by an Appveyor image update.)
833 Fixes bug 32449; bugfix on 0.3.5.6-rc.
835 o Testing (continuous integration, backport from 0.4.2.5):
836 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
837 extensions. Also activates clang's -Wtypedef-redefinition warnings.
838 Build some jobs with -std=gnu99, and some jobs without.
842 Changes in version 0.4.0.6 - 2019-12-09
843 This is the second stable release in the 0.4.0.x series. This release
844 backports several bugfixes to improve stability and correctness. Anyone
845 experiencing build problems or crashes with 0.4.0.5, including all relays
846 relying on AccountingMax, should upgrade.
848 Note that, per our support policy, support for the 0.4.0.x series will end
849 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
850 latest stable release, or downgrade to 0.3.5.x, which will get long-term
851 support until 1 Feb 2022.
853 o Directory authority changes (backport from 0.4.1.5):
854 - The directory authority "dizum" has a new IP address. Closes
857 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
858 - Consider our directory information to have changed when our list
859 of bridges changes. Previously, Tor would not re-compute the
860 status of its directory information when bridges changed, and
861 therefore would not realize that it was no longer able to build
862 circuits. Fixes part of bug 29875.
863 - Do not count previously configured working bridges towards our
864 total of working bridges. Previously, when Tor's list of bridges
865 changed, it would think that the old bridges were still usable,
866 and delay fetching router descriptors for the new ones. Fixes part
867 of bug 29875; bugfix on 0.3.0.1-alpha.
869 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
870 - When considering upgrading circuits from "waiting for guard" to
871 "open", always ignore circuits that are marked for close. Otherwise,
872 we can end up in the situation where a subsystem is notified that
873 a closing circuit has just opened, leading to undesirable
874 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
876 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
877 - Properly clean up the introduction point map when circuits change
878 purpose from onion service circuits to pathbias, measurement, or
879 other circuit types. This should fix some service-side instances
880 of introduction point failure. Fixes bug 29034; bugfix
883 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
884 - Fix an unreachable bug in which an introduction point could try to
885 send an INTRODUCE_ACK with a status code that Trunnel would refuse
886 to encode, leading the relay to assert(). We've consolidated the
887 ABI values into Trunnel now. Fixes bug 30454; bugfix
889 - Clients can now handle unknown status codes from INTRODUCE_ACK
890 cells. (The NACK behavior will stay the same.) This will allow us
891 to extend status codes in the future without breaking the normal
892 client behavior. Fixes another part of bug 30454; bugfix
895 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
896 - Relays now respect their AccountingMax bandwidth again. When
897 relays entered "soft" hibernation (which typically starts when
898 we've hit 90% of our AccountingMax), we had stopped checking
899 whether we should enter hard hibernation. Soft hibernation refuses
900 new connections and new circuits, but the existing circuits can
901 continue, meaning that relays could have exceeded their configured
902 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
904 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
905 - Stop ignoring torrc options after an %include directive, when the
906 included directory ends with a file that does not contain any
907 config options (but does contain comments or whitespace). Fixes
908 bug 31408; bugfix on 0.3.1.1-alpha.
910 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
911 - Onion services now always use the exact number of intro points
912 configured with the HiddenServiceNumIntroductionPoints option (or
913 fewer if nodes are excluded). Before, a service could sometimes
914 pick more intro points than configured. Fixes bug 31548; bugfix
917 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
918 - Add a "--list-modules" command to print a list of which compile-
919 time modules are enabled. Closes ticket 30452.
921 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
922 - Remove sudo configuration lines from .travis.yml as they are no
923 longer needed with current Travis build environment. Resolves
926 o Minor features (continuous integration, backport from 0.4.1.4-rc):
927 - Our Travis configuration now uses Chutney to run some network
928 integration tests automatically. Closes ticket 29280.
930 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
931 - When building on Appveyor and Travis, pass the "-k" flag to make,
932 so that we are informed of all compilation failures, not just the
933 first one or two. Closes ticket 31372.
935 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
936 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
937 in December 2018 (of which ~122 were still functional), with a
938 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
939 in June 2019. Closes ticket 28795.
941 o Minor features (geoip, backport from 0.4.2.5):
942 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
943 Country database. Closes ticket 32685.
945 o Minor features (stem tests, backport from 0.4.2.1-alpha):
946 - Change "make test-stem" so it only runs the stem tests that use
947 tor. This change makes test-stem faster and more reliable. Closes
950 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
951 - Avoid spurious errors when Appveyor CI fails before the install step.
952 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
954 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
955 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
956 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
958 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
959 - Fix a logic error that prevented the SessionGroup sub-option from
960 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
962 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
963 - On relays, properly check that a padding machine is absent before
964 logging a warning about it being absent. Fixes bug 30649; bugfix
967 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
968 - Fix a BUG() assertion that occurs within a very small race window
969 between when a client intro circuit opens and when its descriptor
970 gets cleaned up from the cache. The circuit is now closed early,
971 which will trigger a re-fetch of the descriptor and continue the
972 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
974 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
975 - Don't believe clock skew results from NETINFO cells that appear to
976 arrive before we sent the VERSIONS cells they are responding to.
977 Previously, we would accept them up to 3 minutes "in the past".
978 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
980 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
981 - Fix a compilation warning on Windows about casting a function
982 pointer for GetTickCount64(). Fixes bug 31374; bugfix
985 o Minor bugfixes (compilation, backport from 0.4.1.5):
986 - Avoid using labs() on time_t, which can cause compilation warnings
987 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
989 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
990 - Suppress spurious float-conversion warnings from GCC when calling
991 floating-point classifier functions on FreeBSD. Fixes part of bug
992 31687; bugfix on 0.3.1.5-alpha.
994 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
995 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
996 due to missing declarations of abort(), and prevent other such
997 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
999 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1000 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1001 want authentication along with configured (but unused!)
1002 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1004 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1005 - Avoid trying to read data from closed connections, which can cause
1006 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1007 30344; bugfix on 0.1.1.1-alpha.
1009 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1010 - Allow the test-stem job to fail in Travis, because it sometimes
1011 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1012 - Skip test_rebind on macOS in Travis, because it is unreliable on
1013 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1014 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1015 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1017 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1018 - Avoid a set of possible code paths that could try to use freed
1019 memory in routerlist_free() while Tor was exiting. Fixes bug
1020 31003; bugfix on 0.1.2.2-alpha.
1022 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1023 - Stop crashing after parsing an unknown descriptor purpose
1024 annotation. We think this bug can only be triggered by modifying a
1025 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1027 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1028 - Move the "bandwidth-file-headers" line in directory authority
1029 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1032 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1033 - On abort, try harder to flush the output buffers of log messages.
1034 On some platforms (macOS), log messages could be discarded when
1035 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1036 - Report the tor version whenever an assertion fails. Previously, we
1037 only reported the Tor version on some crashes, and some non-fatal
1038 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1040 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1041 - When extracting an IPv6 address from a PF-based proxy, verify that
1042 we are actually configured to receive an IPv6 address, and log an
1043 internal error if not. Fixes part of bug 31687; bugfix
1046 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1047 - When tor is missing descriptors for some primary entry guards,
1048 make the log message less alarming. It's normal for descriptors to
1049 expire, as long as tor fetches new ones soon after. Fixes bug
1050 31657; bugfix on 0.3.3.1-alpha.
1052 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1053 - Do not log a warning when running with an OpenSSL version other
1054 than the one Tor was compiled with, if the two versions should be
1055 compatible. Previously, we would warn whenever the version was
1056 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1058 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1059 - Change log level of message "Hash of session info was not as
1060 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1063 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1064 - Rate-limit our the logging message about the obsolete .exit
1065 notation. Previously, there was no limit on this warning, which
1066 could potentially be triggered many times by a hostile website.
1067 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1069 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1070 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1071 cell on a connection using the obsolete v1 link protocol. Log a
1072 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1074 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1075 - Reset the periodic events' "enabled" flag when Tor is shut down
1076 cleanly. Previously, this flag was left on, which caused periodic
1077 events not to be re-enabled when Tor was relaunched in-process
1078 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1081 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
1082 - Avoid a minor memory leak that could occur on relays when failing
1083 to create a "keys" directory. Fixes bug 30148; bugfix
1086 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
1087 - Fix a trivial memory leak when parsing an invalid value
1088 from a download schedule in the configuration. Fixes bug
1089 30894; bugfix on 0.3.4.1-alpha.
1091 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
1092 - Fix usage of minherit() on NetBSD and other platforms that define
1093 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
1094 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
1096 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
1097 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
1098 implemenation) when failing to load an onion service client
1099 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
1101 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
1102 - When purging the DNS cache because of an out-of-memory condition,
1103 try purging just the older entries at first. Previously, we would
1104 always purge the whole thing. Fixes bug 29617; bugfix
1107 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
1108 - Avoid crashing in our tor_vasprintf() implementation on systems
1109 that define neither vasprintf() nor _vscprintf(). (This bug has
1110 been here long enough that we question whether people are running
1111 Tor on such systems, but we're applying the fix out of caution.)
1112 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
1115 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1116 - Remove overly strict assertions that triggered when a pluggable
1117 transport failed to launch. Fixes bug 31091; bugfix
1119 - Remove an assertion in the Unix process backend. This assertion
1120 would trigger when we failed to find the executable for a child
1121 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1123 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1124 - Avoid crashing when starting with a corrupt keys directory where
1125 the old ntor key and the new ntor key are identical. Fixes bug
1126 30916; bugfix on 0.2.4.8-alpha.
1128 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1129 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1130 31463; bugfix on 0.3.5.4-alpha.
1132 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1133 - When testing port rebinding, don't busy-wait for tor to log.
1134 Instead, actually sleep for a short time before polling again.
1135 Also improve the formatting of control commands and log messages.
1136 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1138 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1139 - Log bugs about the TLS read buffer's length only once, rather than
1140 filling the logs with similar warnings. Fixes bug 31939; bugfix
1143 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
1144 - Always retry v2 single onion service intro and rend circuits with
1145 a 3-hop path. Previously, v2 single onion services used a 3-hop
1146 path when rendezvous circuits were retried after a remote or
1147 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1148 23818; bugfix on 0.2.9.3-alpha.
1149 - Make v3 single onion services fall back to a 3-hop intro, when all
1150 intro points are unreachable via a 1-hop path. Previously, v3
1151 single onion services failed when all intro nodes were unreachable
1152 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1154 o Documentation (backport from 0.4.2.1-alpha):
1155 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1156 notice.html so that operators no longer have to host it
1157 themselves. Closes ticket 31089.
1159 o Testing (backport from 0.4.1.2-alpha):
1160 - Specify torrc paths (with empty files) when launching tor in
1161 integration tests; refrain from reading user and system torrcs.
1162 Resolves issue 29702.
1164 o Testing (continuous integration, backport from 0.4.1.1-alpha):
1165 - In Travis, show stem's tor log after failure. Closes ticket 30234.
1167 o Testing (continuous integration, backport from 0.4.1.5):
1168 - In Travis, make stem log a controller trace to the console, and
1169 tail stem's tor log after failure. Closes ticket 30591.
1170 - In Travis, only run the stem tests that use a tor binary. Closes
1173 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1174 - Disable all but one Travis CI macOS build, to mitigate slow
1175 scheduling of Travis macOS jobs. Closes ticket 32177.
1176 - Run the chutney IPv6 networks as part of Travis CI. Closes
1178 - Simplify the Travis CI build matrix, and optimise for build time.
1179 Closes ticket 31859.
1180 - Use Windows Server 2019 instead of Windows Server 2016 in our
1181 Appveyor builds. Closes ticket 32086.
1183 o Testing (continuous integration, backport from 0.4.2.4-rc):
1184 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1185 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1186 until we can fix some Bionic permissions issues (see ticket
1187 32240). Related to ticket 31919.
1188 - Install the mingw OpenSSL package in Appveyor. This makes sure
1189 that the OpenSSL headers and libraries match in Tor's Appveyor
1190 builds. (This bug was triggered by an Appveyor image update.)
1191 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1192 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1194 o Testing (continuous integration, backport from 0.4.2.5):
1195 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1196 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1197 Build some jobs with -std=gnu99, and some jobs without.
1198 Closes ticket 32500.
1200 Changes in version 0.3.5.9 - 2019-12-09
1201 Tor 0.3.5.9 backports serveral fixes from later releases, including
1202 several that affect bridge users, relay stability, onion services,
1205 o Directory authority changes (backport from 0.4.1.5):
1206 - The directory authority "dizum" has a new IP address. Closes
1209 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
1210 - Consider our directory information to have changed when our list
1211 of bridges changes. Previously, Tor would not re-compute the
1212 status of its directory information when bridges changed, and
1213 therefore would not realize that it was no longer able to build
1214 circuits. Fixes part of bug 29875.
1215 - Do not count previously configured working bridges towards our
1216 total of working bridges. Previously, when Tor's list of bridges
1217 changed, it would think that the old bridges were still usable,
1218 and delay fetching router descriptors for the new ones. Fixes part
1219 of bug 29875; bugfix on 0.3.0.1-alpha.
1221 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
1222 - When considering upgrading circuits from "waiting for guard" to
1223 "open", always ignore circuits that are marked for close. Otherwise,
1224 we can end up in the situation where a subsystem is notified that
1225 a closing circuit has just opened, leading to undesirable
1226 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1228 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
1229 - When running with NSS, disable TLS 1.2 ciphersuites that use
1230 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
1231 these ciphersuites don't work -- which caused relays to fail to
1232 handshake with one another when these ciphersuites were enabled.
1233 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
1235 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
1236 - Properly clean up the introduction point map when circuits change
1237 purpose from onion service circuits to pathbias, measurement, or
1238 other circuit types. This should fix some service-side instances
1239 of introduction point failure. Fixes bug 29034; bugfix
1242 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
1243 - Fix an unreachable bug in which an introduction point could try to
1244 send an INTRODUCE_ACK with a status code that Trunnel would refuse
1245 to encode, leading the relay to assert(). We've consolidated the
1246 ABI values into Trunnel now. Fixes bug 30454; bugfix
1248 - Clients can now handle unknown status codes from INTRODUCE_ACK
1249 cells. (The NACK behavior will stay the same.) This will allow us
1250 to extend status codes in the future without breaking the normal
1251 client behavior. Fixes another part of bug 30454; bugfix
1254 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1255 - Stop ignoring torrc options after an %include directive, when the
1256 included directory ends with a file that does not contain any
1257 config options (but does contain comments or whitespace). Fixes
1258 bug 31408; bugfix on 0.3.1.1-alpha.
1260 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1261 - Onion services now always use the exact number of intro points
1262 configured with the HiddenServiceNumIntroductionPoints option (or
1263 fewer if nodes are excluded). Before, a service could sometimes
1264 pick more intro points than configured. Fixes bug 31548; bugfix
1267 o Minor features (address selection, backport from 0.4.0.3-alpha):
1268 - Treat the subnet 100.64.0.0/10 as public for some purposes;
1269 private for others. This subnet is the RFC 6598 (Carrier Grade
1270 NAT) IP range, and is deployed by many ISPs as an alternative to
1271 RFC 1918 that does not break existing internal networks. Tor now
1272 blocks SOCKS and control ports on these addresses and warns users
1273 if client ports or ExtORPorts are listening on a RFC 6598 address.
1274 Closes ticket 28525. Patch by Neel Chauhan.
1276 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
1277 - Make bandwidth authorities ignore relays that are reported in the
1278 bandwidth file with the flag "vote=0". This change allows us to
1279 report unmeasured relays for diagnostic reasons without including
1280 their bandwidth in the bandwidth authorities' vote. Closes
1283 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
1284 - Add a "--list-modules" command to print a list of which compile-
1285 time modules are enabled. Closes ticket 30452.
1287 o Minor features (continuous integration, backport from 0.4.0.4-rc):
1288 - On Travis Rust builds, cleanup Rust registry and refrain from
1289 caching the "target/" directory to speed up builds. Resolves
1292 o Minor features (continuous integration, backport from 0.4.0.5):
1293 - In Travis, tell timelimit to use stem's backtrace signals, and
1294 launch python directly from timelimit, so python receives the
1295 signals from timelimit, rather than make. Closes ticket 30117.
1297 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
1298 - Remove sudo configuration lines from .travis.yml as they are no
1299 longer needed with current Travis build environment. Resolves
1302 o Minor features (continuous integration, backport from 0.4.1.4-rc):
1303 - Our Travis configuration now uses Chutney to run some network
1304 integration tests automatically. Closes ticket 29280.
1306 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1307 - When building on Appveyor and Travis, pass the "-k" flag to make,
1308 so that we are informed of all compilation failures, not just the
1309 first one or two. Closes ticket 31372.
1311 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
1312 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1313 in December 2018 (of which ~122 were still functional), with a
1314 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1315 in June 2019. Closes ticket 28795.
1317 o Minor features (geoip, backport from 0.4.2.5):
1318 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1319 Country database. Closes ticket 32685.
1321 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
1322 - Try to log an error from NSS (if there is any) and a more useful
1323 description of our situation if we are using NSS and a call to
1324 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
1326 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1327 - Change "make test-stem" so it only runs the stem tests that use
1328 tor. This change makes test-stem faster and more reliable. Closes
1331 o Minor bugfixes (security, backport from 0.4.0.4-rc):
1332 - Verify in more places that we are not about to create a buffer
1333 with more than INT_MAX bytes, to avoid possible OOB access in the
1334 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
1335 fixed by Tobias Stoeckmann.
1336 - Fix a potential double free bug when reading huge bandwidth files.
1337 The issue is not exploitable in the current Tor network because
1338 the vulnerable code is only reached when directory authorities
1339 read bandwidth files, but bandwidth files come from a trusted
1340 source (usually the authorities themselves). Furthermore, the
1341 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
1342 which are not used by any of the current authorities. Fixes bug
1343 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
1346 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
1347 - Reset coverage state on disk after Travis CI has finished. This
1348 should prevent future coverage merge errors from causing the test
1349 suite for the "process" subsystem to fail. The process subsystem
1350 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
1352 - Terminate test-stem if it takes more than 9.5 minutes to run.
1353 (Travis terminates the job after 10 minutes of no output.)
1354 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
1356 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1357 - Avoid spurious errors when Appveyor CI fails before the install step.
1358 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1360 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1361 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1362 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1364 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
1365 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
1366 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
1369 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
1370 - Fix a logic error that prevented the SessionGroup sub-option from
1371 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1373 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1374 - Fix a BUG() assertion that occurs within a very small race window
1375 between when a client intro circuit opens and when its descriptor
1376 gets cleaned up from the cache. The circuit is now closed early,
1377 which will trigger a re-fetch of the descriptor and continue the
1378 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1380 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
1381 - Don't believe clock skew results from NETINFO cells that appear to
1382 arrive before we sent the VERSIONS cells they are responding to.
1383 Previously, we would accept them up to 3 minutes "in the past".
1384 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1386 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
1387 - Fix a compilation warning on Windows about casting a function
1388 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1391 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
1392 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1393 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1395 o Minor bugfixes (compilation, backport from 0.4.1.5):
1396 - Avoid using labs() on time_t, which can cause compilation warnings
1397 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1399 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1400 - Suppress spurious float-conversion warnings from GCC when calling
1401 floating-point classifier functions on FreeBSD. Fixes part of bug
1402 31687; bugfix on 0.3.1.5-alpha.
1404 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
1405 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
1406 due to missing declarations of abort(), and prevent other such
1407 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
1409 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1410 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1411 want authentication along with configured (but unused!)
1412 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1414 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1415 - Avoid trying to read data from closed connections, which can cause
1416 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1417 30344; bugfix on 0.1.1.1-alpha.
1419 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1420 - Allow the test-stem job to fail in Travis, because it sometimes
1421 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1422 - Skip test_rebind on macOS in Travis, because it is unreliable on
1423 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1424 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1425 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1427 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1428 - Avoid a set of possible code paths that could try to use freed
1429 memory in routerlist_free() while Tor was exiting. Fixes bug
1430 31003; bugfix on 0.1.2.2-alpha.
1432 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1433 - Stop crashing after parsing an unknown descriptor purpose
1434 annotation. We think this bug can only be triggered by modifying a
1435 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1437 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1438 - Move the "bandwidth-file-headers" line in directory authority
1439 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1442 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1443 - On abort, try harder to flush the output buffers of log messages.
1444 On some platforms (macOS), log messages could be discarded when
1445 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1446 - Report the tor version whenever an assertion fails. Previously, we
1447 only reported the Tor version on some crashes, and some non-fatal
1448 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1450 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1451 - When extracting an IPv6 address from a PF-based proxy, verify that
1452 we are actually configured to receive an IPv6 address, and log an
1453 internal error if not. Fixes part of bug 31687; bugfix
1456 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1457 - When tor is missing descriptors for some primary entry guards,
1458 make the log message less alarming. It's normal for descriptors to
1459 expire, as long as tor fetches new ones soon after. Fixes bug
1460 31657; bugfix on 0.3.3.1-alpha.
1462 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
1463 - Avoid logging that we are relaxing a circuit timeout when that
1464 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1466 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
1467 - Correct a misleading error message when IPv4Only or IPv6Only is
1468 used but the resolved address can not be interpreted as an address
1469 of the specified IP version. Fixes bug 13221; bugfix on
1470 0.2.3.9-alpha. Patch from Kris Katterjohn.
1471 - Log the correct port number for listening sockets when "auto" is
1472 used to let Tor pick the port number. Previously, port 0 was
1473 logged instead of the actual port number. Fixes bug 29144; bugfix
1474 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1475 - Stop logging a BUG() warning when Tor is waiting for exit
1476 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
1478 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1479 - Do not log a warning when running with an OpenSSL version other
1480 than the one Tor was compiled with, if the two versions should be
1481 compatible. Previously, we would warn whenever the version was
1482 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1484 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1485 - Change log level of message "Hash of session info was not as
1486 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1489 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1490 - Rate-limit our the logging message about the obsolete .exit
1491 notation. Previously, there was no limit on this warning, which
1492 could potentially be triggered many times by a hostile website.
1493 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1495 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1496 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1497 cell on a connection using the obsolete v1 link protocol. Log a
1498 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1500 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1501 - Reset the periodic events' "enabled" flag when Tor is shut down
1502 cleanly. Previously, this flag was left on, which caused periodic
1503 events not to be re-enabled when Tor was relaunched in-process
1504 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1507 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
1508 - Avoid a minor memory leak that could occur on relays when failing
1509 to create a "keys" directory. Fixes bug 30148; bugfix
1512 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
1513 - Fix a trivial memory leak when parsing an invalid value
1514 from a download schedule in the configuration. Fixes bug
1515 30894; bugfix on 0.3.4.1-alpha.
1517 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
1518 - Refactor the shared random state's memory management so that it
1519 actually takes ownership of the shared random value pointers.
1520 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
1522 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
1523 - Stop leaking parts of the shared random state in the shared-random
1524 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
1526 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
1527 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
1528 implemenation) when failing to load an onion service client
1529 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
1531 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
1532 - When purging the DNS cache because of an out-of-memory condition,
1533 try purging just the older entries at first. Previously, we would
1534 always purge the whole thing. Fixes bug 29617; bugfix
1537 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
1538 - Avoid crashing in our tor_vasprintf() implementation on systems
1539 that define neither vasprintf() nor _vscprintf(). (This bug has
1540 been here long enough that we question whether people are running
1541 Tor on such systems, but we're applying the fix out of caution.)
1542 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
1545 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1546 - Avoid crashing when starting with a corrupt keys directory where
1547 the old ntor key and the new ntor key are identical. Fixes bug
1548 30916; bugfix on 0.2.4.8-alpha.
1550 o Minor bugfixes (rust, backport from 0.4.0.5):
1551 - Abort on panic in all build profiles, instead of potentially
1552 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
1554 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1555 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1556 31463; bugfix on 0.3.5.4-alpha.
1558 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
1559 - Allow connections to single onion services to remain idle without
1560 being disconnected. Previously, relays acting as rendezvous points
1561 for single onion services were mistakenly closing idle rendezvous
1562 circuits after 60 seconds, thinking that they were unused
1563 directory-fetching circuits that had served their purpose. Fixes
1564 bug 29665; bugfix on 0.2.1.26.
1566 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
1567 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
1568 relay and bridge extra-info documents. Fixes bug 29017; bugfix
1571 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
1572 - Downgrade some LOG_ERR messages in the address/* tests to
1573 warnings. The LOG_ERR messages were occurring when we had no
1574 configured network. We were failing the unit tests, because we
1575 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
1576 29530; bugfix on 0.3.5.8.
1577 - Fix our gcov wrapper script to look for object files at the
1578 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
1580 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
1581 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
1582 recent test-network.sh to use new chutney features in CI. Fixes
1583 bug 29703; bugfix on 0.2.9.1-alpha.
1584 - Fix a test failure on Windows caused by an unexpected "BUG"
1585 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
1588 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1589 - When testing port rebinding, don't busy-wait for tor to log.
1590 Instead, actually sleep for a short time before polling again.
1591 Also improve the formatting of control commands and log messages.
1592 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1594 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
1595 - When classifying a client's selection of TLS ciphers, if the
1596 client ciphers are not yet available, do not cache the result.
1597 Previously, we had cached the unavailability of the cipher list
1598 and never looked again, which in turn led us to assume that the
1599 client only supported the ancient V1 link protocol. This, in turn,
1600 was causing Stem integration tests to stall in some cases. Fixes
1601 bug 30021; bugfix on 0.2.4.8-alpha.
1603 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1604 - Log bugs about the TLS read buffer's length only once, rather than
1605 filling the logs with similar warnings. Fixes bug 31939; bugfix
1608 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
1609 - Always retry v2 single onion service intro and rend circuits with
1610 a 3-hop path. Previously, v2 single onion services used a 3-hop
1611 path when rendezvous circuits were retried after a remote or
1612 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1613 23818; bugfix on 0.2.9.3-alpha.
1614 - Make v3 single onion services fall back to a 3-hop intro, when all
1615 intro points are unreachable via a 1-hop path. Previously, v3
1616 single onion services failed when all intro nodes were unreachable
1617 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1619 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
1620 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
1621 Windows Server 2012 R2 job. The remaining 2 jobs still provide
1622 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
1623 fast_finish, so failed jobs terminate the build immediately. Fixes
1624 bug 29601; bugfix on 0.3.5.4-alpha.
1626 o Documentation (backport from 0.4.2.1-alpha):
1627 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1628 notice.html so that operators no longer have to host it
1629 themselves. Closes ticket 31089.
1631 o Testing (backport from 0.4.1.2-alpha):
1632 - Specify torrc paths (with empty files) when launching tor in
1633 integration tests; refrain from reading user and system torrcs.
1634 Resolves issue 29702.
1636 o Testing (continuous integration, backport from 0.4.1.1-alpha):
1637 - In Travis, show stem's tor log after failure. Closes ticket 30234.
1639 o Testing (continuous integration, backport from 0.4.1.5):
1640 - In Travis, make stem log a controller trace to the console, and
1641 tail stem's tor log after failure. Closes ticket 30591.
1642 - In Travis, only run the stem tests that use a tor binary. Closes
1645 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1646 - Disable all but one Travis CI macOS build, to mitigate slow
1647 scheduling of Travis macOS jobs. Closes ticket 32177.
1648 - Run the chutney IPv6 networks as part of Travis CI. Closes
1650 - Simplify the Travis CI build matrix, and optimise for build time.
1651 Closes ticket 31859.
1652 - Use Windows Server 2019 instead of Windows Server 2016 in our
1653 Appveyor builds. Closes ticket 32086.
1655 o Testing (continuous integration, backport from 0.4.2.4-rc):
1656 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1657 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1658 until we can fix some Bionic permissions issues (see ticket
1659 32240). Related to ticket 31919.
1660 - Install the mingw OpenSSL package in Appveyor. This makes sure
1661 that the OpenSSL headers and libraries match in Tor's Appveyor
1662 builds. (This bug was triggered by an Appveyor image update.)
1663 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1664 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1666 o Testing (continuous integration, backport from 0.4.2.5):
1667 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1668 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1669 Build some jobs with -std=gnu99, and some jobs without.
1670 Closes ticket 32500.
1672 Changes in version 0.4.2.4-rc - 2019-11-15
1673 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
1674 several bugs from earlier versions, including a few that would result in
1675 stack traces or incorrect behavior.
1677 o Minor features (build system):
1678 - Make pkg-config use --prefix when cross-compiling, if
1679 PKG_CONFIG_PATH is not set. Closes ticket 32191.
1681 o Minor features (geoip):
1682 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
1683 Country database. Closes ticket 32440.
1685 o Minor bugfixes (client, onion service v3):
1686 - Fix a BUG() assertion that occurs within a very small race window
1687 between when a client intro circuit opens and when its descriptor
1688 gets cleaned up from the cache. The circuit is now closed early,
1689 which will trigger a re-fetch of the descriptor and continue the
1690 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1692 o Minor bugfixes (code quality):
1693 - Fix "make check-includes" so it runs correctly on out-of-tree
1694 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
1696 o Minor bugfixes (configuration):
1697 - Log the option name when skipping an obsolete option. Fixes bug
1698 32295; bugfix on 0.4.2.1-alpha.
1700 o Minor bugfixes (crash):
1701 - When running Tor with an option like --verify-config or
1702 --dump-config that does not start the event loop, avoid crashing
1703 if we try to exit early because of an error. Fixes bug 32407;
1704 bugfix on 0.3.3.1-alpha.
1706 o Minor bugfixes (directory):
1707 - When checking if a directory connection is anonymous, test if the
1708 circuit was marked for close before looking at its channel. This
1709 avoids a BUG() stacktrace if the circuit was previously closed.
1710 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
1712 o Minor bugfixes (shellcheck):
1713 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
1714 32402; bugfix on 0.4.2.1-alpha.
1715 - Start checking most scripts for shellcheck errors again. Fixes bug
1716 32402; bugfix on 0.4.2.1-alpha.
1718 o Testing (continuous integration):
1719 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1720 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1721 until we can fix some Bionic permissions issues (see ticket
1722 32240). Related to ticket 31919.
1723 - Install the mingw OpenSSL package in Appveyor. This makes sure
1724 that the OpenSSL headers and libraries match in Tor's Appveyor
1725 builds. (This bug was triggered by an Appveyor image update.)
1726 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1727 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1730 Changes in version 0.4.2.3-alpha - 2019-10-24
1731 This release fixes several bugs from the previous alpha release, and
1732 from earlier versions of Tor.
1734 o Major bugfixes (relay):
1735 - Relays now respect their AccountingMax bandwidth again. When
1736 relays entered "soft" hibernation (which typically starts when
1737 we've hit 90% of our AccountingMax), we had stopped checking
1738 whether we should enter hard hibernation. Soft hibernation refuses
1739 new connections and new circuits, but the existing circuits can
1740 continue, meaning that relays could have exceeded their configured
1741 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1743 o Major bugfixes (v3 onion services):
1744 - Onion services now always use the exact number of intro points
1745 configured with the HiddenServiceNumIntroductionPoints option (or
1746 fewer if nodes are excluded). Before, a service could sometimes
1747 pick more intro points than configured. Fixes bug 31548; bugfix
1750 o Minor feature (onion services, control port):
1751 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
1752 (v3) onion services. Previously it defaulted to RSA1024 (v2).
1753 Closes ticket 29669.
1755 o Minor features (testing):
1756 - When running tests that attempt to look up hostnames, replace the
1757 libc name lookup functions with ones that do not actually touch
1758 the network. This way, the tests complete more quickly in the
1759 presence of a slow or missing DNS resolver. Closes ticket 31841.
1761 o Minor features (testing, continuous integration):
1762 - Disable all but one Travis CI macOS build, to mitigate slow
1763 scheduling of Travis macOS jobs. Closes ticket 32177.
1764 - Run the chutney IPv6 networks as part of Travis CI. Closes
1766 - Simplify the Travis CI build matrix, and optimise for build time.
1767 Closes ticket 31859.
1768 - Use Windows Server 2019 instead of Windows Server 2016 in our
1769 Appveyor builds. Closes ticket 32086.
1771 o Minor bugfixes (build system):
1772 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
1773 32124; bugfix on 0.3.4.1-alpha.
1774 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
1776 - Stop failing when jemalloc is requested, but tcmalloc is not
1777 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
1778 - When pkg-config is not installed, or a library that depends on
1779 pkg-config is not found, tell the user what to do to fix the
1780 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
1782 o Minor bugfixes (connections):
1783 - Avoid trying to read data from closed connections, which can cause
1784 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1785 30344; bugfix on 0.1.1.1-alpha.
1787 o Minor bugfixes (error handling):
1788 - Always lock the backtrace buffer before it is used. Fixes bug
1789 31734; bugfix on 0.2.5.3-alpha.
1791 o Minor bugfixes (mainloop, periodic events, in-process API):
1792 - Reset the periodic events' "enabled" flag when Tor is shut down
1793 cleanly. Previously, this flag was left on, which caused periodic
1794 events not to be re-enabled when Tor was relaunched in-process
1795 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1798 o Minor bugfixes (process management):
1799 - Remove overly strict assertions that triggered when a pluggable
1800 transport failed to launch. Fixes bug 31091; bugfix
1802 - Remove an assertion in the Unix process backend. This assertion
1803 would trigger when we failed to find the executable for a child
1804 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1806 o Minor bugfixes (testing):
1807 - Avoid intermittent test failures due to a test that had relied on
1808 inconsistent timing sources. Fixes bug 31995; bugfix
1810 - When testing port rebinding, don't busy-wait for tor to log.
1811 Instead, actually sleep for a short time before polling again.
1812 Also improve the formatting of control commands and log messages.
1813 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1815 o Minor bugfixes (tls, logging):
1816 - Log bugs about the TLS read buffer's length only once, rather than
1817 filling the logs with similar warnings. Fixes bug 31939; bugfix
1820 o Minor bugfixes (v3 onion services):
1821 - Fix an implicit conversion from ssize_t to size_t discovered by
1822 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
1823 - Fix a memory leak in an unlikely error code path when encoding HS
1824 DoS establish intro extension cell. Fixes bug 32063; bugfix
1826 - When cleaning up intro circuits for a v3 onion service, don't
1827 remove circuits that have an established or pending circuit, even
1828 if they ran out of retries. This way, we don't remove a circuit on
1829 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
1832 - Correct the description of "GuardLifetime". Fixes bug 31189;
1833 bugfix on 0.3.0.1-alpha.
1834 - Make clear in the man page, in both the bandwidth section and the
1835 AccountingMax section, that Tor counts in powers of two, not
1836 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
1837 bytes. Resolves ticket 32106.
1840 Changes in version 0.4.2.2-alpha - 2019-10-07
1841 This release fixes several bugs from the previous alpha release, and
1842 from earlier versions. It also includes a change in authorities, so
1843 that they begin to reject the currently unsupported release series.
1845 o Major features (directory authorities):
1846 - Directory authorities now reject relays running all currently
1847 deprecated release series. The currently supported release series
1848 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1850 o Major bugfixes (embedded Tor):
1851 - Avoid a possible crash when restarting Tor in embedded mode and
1852 enabling a different set of publish/subscribe messages. Fixes bug
1853 31898; bugfix on 0.4.1.1-alpha.
1855 o Major bugfixes (torrc parsing):
1856 - Stop ignoring torrc options after an %include directive, when the
1857 included directory ends with a file that does not contain any
1858 config options (but does contain comments or whitespace). Fixes
1859 bug 31408; bugfix on 0.3.1.1-alpha.
1861 o Minor features (auto-formatting scripts):
1862 - When annotating C macros, never generate a line that our check-
1863 spaces script would reject. Closes ticket 31759.
1864 - When annotating C macros, try to remove cases of double-negation.
1865 Closes ticket 31779.
1867 o Minor features (continuous integration):
1868 - When building on Appveyor and Travis, pass the "-k" flag to make,
1869 so that we are informed of all compilation failures, not just the
1870 first one or two. Closes ticket 31372.
1872 o Minor features (geoip):
1873 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
1874 Country database. Closes ticket 31931.
1876 o Minor features (maintenance scripts):
1877 - Add a Coccinelle script to detect bugs caused by incrementing or
1878 decrementing a variable inside a call to log_debug(). Since
1879 log_debug() is a macro whose arguments are conditionally
1880 evaluated, it is usually an error to do this. One such bug was
1881 30628, in which SENDME cells were miscounted by a decrement
1882 operator inside a log_debug() call. Closes ticket 30743.
1884 o Minor features (onion services v3):
1885 - Assist users who try to setup v2 client authorization in v3 onion
1886 services by pointing them to the right documentation. Closes
1889 o Minor bugfixes (Appveyor continuous integration):
1890 - Avoid spurious errors when Appveyor CI fails before the install
1891 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1893 o Minor bugfixes (best practices tracker):
1894 - When listing overbroad exceptions, do not also list problems, and
1895 do not list insufficiently broad exceptions. Fixes bug 31338;
1896 bugfix on 0.4.2.1-alpha.
1898 o Minor bugfixes (controller protocol):
1899 - Fix the MAPADDRESS controller command to accept one or more
1900 arguments. Previously, it required two or more arguments, and
1901 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
1903 o Minor bugfixes (logging):
1904 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1905 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1906 - Disable backtrace signal handlers when shutting down tor. Fixes
1907 bug 31614; bugfix on 0.2.5.2-alpha.
1908 - Rate-limit our the logging message about the obsolete .exit
1909 notation. Previously, there was no limit on this warning, which
1910 could potentially be triggered many times by a hostile website.
1911 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1912 - When initialising log domain masks, only set known log domains.
1913 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
1915 o Minor bugfixes (logging, protocol violations):
1916 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1917 cell on a connection using the obsolete v1 link protocol. Log a
1918 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1920 o Minor bugfixes (modules):
1921 - Explain what the optional Directory Authority module is, and what
1922 happens when it is disabled. Fixes bug 31825; bugfix
1925 o Minor bugfixes (multithreading):
1926 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1927 31736; bugfix on 0.0.7.
1929 o Minor bugfixes (relay):
1930 - Avoid crashing when starting with a corrupt keys directory where
1931 the old ntor key and the new ntor key are identical. Fixes bug
1932 30916; bugfix on 0.2.4.8-alpha.
1934 o Minor bugfixes (tests, SunOS):
1935 - Avoid a map_anon_nofork test failure due to a signed/unsigned
1936 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
1938 o Code simplification and refactoring:
1939 - Refactor connection_control_process_inbuf() to reduce the size of
1940 a practracker exception. Closes ticket 31840.
1941 - Refactor the microdescs_parse_from_string() function into smaller
1942 pieces, for better comprehensibility. Closes ticket 31675.
1943 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
1944 tests and fuzzers, rather than using hard-coded values. Closes
1946 - Interface for function `decrypt_desc_layer` cleaned up. Closes
1950 - Document the signal-safe logging behaviour in the tor man page.
1951 Also add some comments to the relevant functions. Closes
1953 - Explain why we can't destroy the backtrace buffer mutex. Explain
1954 why we don't need to destroy the log mutex. Closes ticket 31736.
1955 - The Tor source code repository now includes a (somewhat dated)
1956 description of Tor's modular architecture, in doc/HACKING/design.
1957 This is based on the old "tor-guts.git" repository, which we are
1958 adopting and superseding. Closes ticket 31849.
1961 Changes in version 0.4.1.6 - 2019-09-19
1962 This release backports several bugfixes to improve stability and
1963 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
1964 or experiencing reliability issues with single onion services, should
1967 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
1968 - Tolerate systems (including some Android installations) where
1969 madvise and MADV_DONTDUMP are available at build-time, but not at
1970 run time. Previously, these systems would notice a failed syscall
1971 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
1972 - Tolerate systems (including some Linux installations) where
1973 madvise and/or MADV_DONTFORK are available at build-time, but not
1974 at run time. Previously, these systems would notice a failed
1975 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
1977 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1978 - Change "make test-stem" so it only runs the stem tests that use
1979 tor. This change makes test-stem faster and more reliable. Closes
1982 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1983 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1984 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1986 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1987 - Add more stub functions to fix compilation on Android with link-
1988 time optimization when --disable-module-dirauth is used.
1989 Previously, these compilation settings would make the compiler
1990 look for functions that didn't exist. Fixes bug 31552; bugfix
1992 - Suppress spurious float-conversion warnings from GCC when calling
1993 floating-point classifier functions on FreeBSD. Fixes part of bug
1994 31687; bugfix on 0.3.1.5-alpha.
1996 o Minor bugfixes (controller protocol):
1997 - Fix the MAPADDRESS controller command to accept one or more
1998 arguments. Previously, it required two or more arguments, and ignored
1999 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2001 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2002 - When extracting an IPv6 address from a PF-based proxy, verify that
2003 we are actually configured to receive an IPv6 address, and log an
2004 internal error if not. Fixes part of bug 31687; bugfix
2007 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2008 - When tor is missing descriptors for some primary entry guards,
2009 make the log message less alarming. It's normal for descriptors to
2010 expire, as long as tor fetches new ones soon after. Fixes bug
2011 31657; bugfix on 0.3.3.1-alpha.
2013 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2014 - Change log level of message "Hash of session info was not as
2015 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2018 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2019 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2020 31463; bugfix on 0.3.5.4-alpha.
2022 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2023 - Always retry v2 single onion service intro and rend circuits with
2024 a 3-hop path. Previously, v2 single onion services used a 3-hop
2025 path when rendezvous circuits were retried after a remote or
2026 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2027 23818; bugfix on 0.2.9.3-alpha.
2029 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
2030 - Always retry v3 single onion service intro and rend circuits with
2031 a 3-hop path. Previously, v3 single onion services used a 3-hop
2032 path when rend circuits were retried after a remote or delayed
2033 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2034 bugfix on 0.3.2.1-alpha.
2035 - Make v3 single onion services fall back to a 3-hop intro, when all
2036 intro points are unreachable via a 1-hop path. Previously, v3
2037 single onion services failed when all intro nodes were unreachable
2038 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2040 o Documentation (backport from 0.4.2.1-alpha):
2041 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2042 notice.html so that operators no longer have to host it
2043 themselves. Closes ticket 31089.
2046 Changes in version 0.4.2.1-alpha - 2019-09-17
2047 This is the first alpha release in the 0.4.2.x series. It adds new
2048 defenses for denial-of-service attacks against onion services. It also
2049 includes numerous kinds of bugfixes and refactoring to help improve
2050 Tor's stability and ease of development.
2052 o Major features (onion service v3, denial of service):
2053 - Add onion service introduction denial of service defenses. Intro
2054 points can now rate-limit client introduction requests, using
2055 parameters that can be sent by the service within the
2056 ESTABLISH_INTRO cell. If the cell extension for this is not used,
2057 the intro point will honor the consensus parameters. Closes
2060 o Major bugfixes (circuit build, guard):
2061 - When considering upgrading circuits from "waiting for guard" to
2062 "open", always ignore circuits that are marked for close.
2063 Previously we could end up in the situation where a subsystem is
2064 notified of a circuit opening, but the circuit is still marked for
2065 close, leading to undesirable behavior. Fixes bug 30871; bugfix
2068 o Major bugfixes (crash, Linux, Android):
2069 - Tolerate systems (including some Android installations) where
2070 madvise and MADV_DONTDUMP are available at build-time, but not at
2071 run time. Previously, these systems would notice a failed syscall
2072 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2073 - Tolerate systems (including some Linux installations) where
2074 madvise and/or MADV_DONTFORK are available at build-time, but not
2075 at run time. Previously, these systems would notice a failed
2076 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2078 o Minor features (best practices tracker):
2079 - Our best-practices tracker now integrates with our include-checker
2080 tool to keep track of how many layering violations we have not yet
2081 fixed. We hope to reduce this number over time to improve Tor's
2082 modularity. Closes ticket 31176.
2083 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
2084 practracker from the environment. We may want this for continuous
2085 integration. Closes ticket 31309.
2086 - Give a warning rather than an error when a practracker exception
2087 is violated by a small amount, add a --list-overbroad option to
2088 practracker that lists exceptions that are stricter than they need
2089 to be, and provide an environment variable for disabling
2090 practracker. Closes ticket 30752.
2091 - Our best-practices tracker now looks at headers as well as C
2092 files. Closes ticket 31175.
2094 o Minor features (build system):
2095 - Add --disable-manpage and --disable-html-manual options to
2096 configure script. This will enable shortening build times by not
2097 building documentation. Resolves issue 19381.
2099 o Minor features (compilation):
2100 - Log a more useful error message when we are compiling and one of
2101 the compile-time hardening options we have selected can be linked
2102 but not executed. Closes ticket 27530.
2104 o Minor features (configuration):
2105 - The configuration code has been extended to allow splitting
2106 configuration data across multiple objects. Previously, all
2107 configuration data needed to be kept in a single object, which
2108 tended to become bloated. Closes ticket 31240.
2110 o Minor features (continuous integration):
2111 - When running CI builds on Travis, put some random data in
2112 ~/.torrc, to make sure no tests are reading the Tor configuration
2113 file from its default location. Resolves issue 30102.
2115 o Minor features (debugging):
2116 - Log a nonfatal assertion failure if we encounter a configuration
2117 line whose command is "CLEAR" but which has a nonempty value. This
2118 should be impossible, according to the rules of our configuration
2119 line parsing. Closes ticket 31529.
2121 o Minor features (git hooks):
2122 - Our pre-commit git hook now checks for a special file before
2123 running practracker, so that practracker only runs on branches
2124 that are based on master. Since the pre-push hook calls the pre-
2125 commit hook, practracker will also only run before pushes of
2126 branches based on master. Closes ticket 30979.
2128 o Minor features (git scripts):
2129 - Add a "--" command-line argument, to separate git-push-all.sh
2130 script arguments from arguments that are passed through to git
2131 push. Closes ticket 31314.
2132 - Add a -r <remote-name> argument to git-push-all.sh, so the script
2133 can push test branches to a personal remote. Closes ticket 31314.
2134 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
2135 git-push-all.sh, which makes these scripts create, merge forward,
2136 and push test branches. Closes ticket 31314.
2137 - Add a -u argument to git-merge-forward.sh, so that the script can
2138 re-use existing test branches after a merge failure and fix.
2139 Closes ticket 31314.
2140 - Add a TOR_GIT_PUSH env var, which sets the default git push
2141 command and arguments for git-push-all.sh. Closes ticket 31314.
2142 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
2143 script push master and maint branches with a delay between each
2144 branch. These delays trigger the CI jobs in a set order, which
2145 should show the most likely failures first. Also make pushes
2146 atomic by default, and make the script pass any command-line
2147 arguments to git push. Closes ticket 29879.
2148 - Call the shellcheck script from the pre-commit hook. Closes
2150 - Skip pushing test branches that are the same as a remote
2151 maint/release/master branch in git-push-all.sh by default. Add a
2152 -s argument, so git-push-all.sh can push all test branches. Closes
2155 o Minor features (IPv6, logging):
2156 - Log IPv6 addresses as well as IPv4 addresses when describing
2157 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
2159 o Minor features (onion service v3):
2160 - Do not allow single hop clients to fetch or post an HS descriptor
2161 from an HSDir. Closes ticket 24964.
2163 o Minor features (onion service):
2164 - Disallow single-hop clients at the introduction point. We've
2165 removed Tor2web support a while back and single-hop rendezvous
2166 attempts are blocked at the relays. This change should remove load
2167 off the network from spammy clients. Close ticket 24963.
2169 o Minor features (stem tests):
2170 - Change "make test-stem" so it only runs the stem tests that use
2171 tor. This change makes test-stem faster and more reliable. Closes
2174 o Minor features (testing):
2175 - Add a script to invoke "tor --dump-config" and "tor
2176 --verify-config" with various configuration options, and see
2177 whether tor's resulting configuration or error messages are what
2178 we expect. Use it for integration testing of our +Option and
2179 /Option flags. Closes ticket 31637.
2180 - Improve test coverage for our existing configuration parsing and
2181 management API. Closes ticket 30893.
2182 - Add integration tests to make sure that practracker gives the
2183 outputs we expect. Closes ticket 31477.
2184 - The practracker self-tests are now run as part of the Tor test
2185 suite. Closes ticket 31304.
2187 o Minor features (token bucket):
2188 - Implement a generic token bucket that uses a single counter, for
2189 use in anti-DoS onion service work. Closes ticket 30687.
2191 o Minor bugfixes (best practices tracker):
2192 - Fix a few issues in the best-practices script, including tests,
2193 tab tolerance, error reporting, and directory-exclusion logic.
2194 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
2195 - When running check-best-practices, only consider files in the src
2196 subdirectory. Previously we had recursively considered all
2197 subdirectories, which made us get confused by the temporary
2198 directories made by "make distcheck". Fixes bug 31578; bugfix
2201 o Minor bugfixes (build system):
2202 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2203 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2205 o Minor bugfixes (chutney, makefiles, documentation):
2206 - "make test-network-all" now shows the warnings from each test-
2207 network.sh run on the console, so developers see new warnings
2208 early. We've also improved the documentation for this feature, and
2209 renamed a Makefile variable so the code is self-documenting. Fixes
2210 bug 30455; bugfix on 0.3.0.4-rc.
2212 o Minor bugfixes (compilation):
2213 - Add more stub functions to fix compilation on Android with link-
2214 time optimization when --disable-module-dirauth is used.
2215 Previously, these compilation settings would make the compiler
2216 look for functions that didn't exist. Fixes bug 31552; bugfix
2218 - Suppress spurious float-conversion warnings from GCC when calling
2219 floating-point classifier functions on FreeBSD. Fixes part of bug
2220 31687; bugfix on 0.3.1.5-alpha.
2222 o Minor bugfixes (configuration):
2223 - Invalid floating-point values in the configuration file are now
2224 treated as errors in the configuration. Previously, they were
2225 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
2227 o Minor bugfixes (coverity):
2228 - Add an assertion when parsing a BEGIN cell so that coverity can be
2229 sure that we are not about to dereference a NULL address. Fixes
2230 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
2231 - In our siphash implementation, when building for coverity, use
2232 memcpy in place of a switch statement, so that coverity can tell
2233 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
2234 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
2235 - Fix several coverity warnings from our unit tests. Fixes bug
2236 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
2238 o Minor bugfixes (developer tooling):
2239 - Only log git script changes in the post-merge script when the
2240 merge was to the master branch. Fixes bug 31040; bugfix
2243 o Minor bugfixes (directory authorities):
2244 - Return a distinct status when formatting annotations fails. Fixes
2245 bug 30780; bugfix on 0.2.0.8-alpha.
2247 o Minor bugfixes (error handling):
2248 - On abort, try harder to flush the output buffers of log messages.
2249 On some platforms (macOS), log messages could be discarded when
2250 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2251 - Report the tor version whenever an assertion fails. Previously, we
2252 only reported the Tor version on some crashes, and some non-fatal
2253 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2254 - When tor aborts due to an error, close log file descriptors before
2255 aborting. Closing the logs makes some OSes flush log file buffers,
2256 rather than deleting buffered log lines. Fixes bug 31594; bugfix
2259 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
2260 - When extracting an IPv6 address from a PF-based proxy, verify that
2261 we are actually configured to receive an IPv6 address, and log an
2262 internal error if not. Fixes part of bug 31687; bugfix
2265 o Minor bugfixes (git hooks):
2266 - Remove a duplicate call to practracker from the pre-push hook. The
2267 pre-push hook already calls the pre-commit hook, which calls
2268 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
2270 o Minor bugfixes (git scripts):
2271 - Stop hard-coding the bash path in the git scripts. Some OSes don't
2272 have bash in /usr/bin, others have an ancient bash at this path.
2273 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
2274 - Stop hard-coding the tor master branch name and worktree path in
2275 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
2276 - Allow git-push-all.sh to be run from any directory. Previously,
2277 the script only worked if run from an upstream worktree directory.
2278 Closes ticket 31678.
2280 o Minor bugfixes (guards):
2281 - When tor is missing descriptors for some primary entry guards,
2282 make the log message less alarming. It's normal for descriptors to
2283 expire, as long as tor fetches new ones soon after. Fixes bug
2284 31657; bugfix on 0.3.3.1-alpha.
2286 o Minor bugfixes (ipv6):
2287 - Check for private IPv6 addresses alongside their IPv4 equivalents
2288 when authorities check descriptors. Previously, we only checked
2289 for private IPv4 addresses. Fixes bug 31088; bugfix on
2290 0.2.3.21-rc. Patch by Neel Chauhan.
2291 - When parsing microdescriptors, we should check the IPv6 exit
2292 policy alongside IPv4. Previously, we checked both exit policies
2293 for only router info structures, while microdescriptors were
2294 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
2297 o Minor bugfixes (logging):
2298 - Change log level of message "Hash of session info was not as
2299 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2301 - Fix a code issue that would have broken our parsing of log domains
2302 as soon as we had 33 of them. Fortunately, we still only have 29.
2303 Fixes bug 31451; bugfix on 0.4.1.4-rc.
2305 o Minor bugfixes (memory management):
2306 - Stop leaking a small amount of memory in nt_service_install(), in
2307 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
2310 o Minor bugfixes (networking, IP addresses):
2311 - When parsing addresses via Tor's internal DNS lookup API, reject
2312 IPv4 addresses in square brackets, and accept IPv6 addresses in
2313 square brackets. This change completes the work started in 23082,
2314 making address parsing consistent between tor's internal DNS
2315 lookup and address parsing APIs. Fixes bug 30721; bugfix
2317 - When parsing addresses via Tor's internal address:port parsing and
2318 DNS lookup APIs, require IPv6 addresses with ports to have square
2319 brackets. But allow IPv6 addresses without ports, whether or not
2320 they have square brackets. Fixes bug 30721; bugfix
2323 o Minor bugfixes (onion service v3):
2324 - When purging the client descriptor cache, close any introduction
2325 point circuits associated with purged cache entries. This avoids
2326 picking those circuits later when connecting to the same
2327 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
2329 o Minor bugfixes (onion services):
2330 - In the hs_ident_circuit_t data structure, remove the unused field
2331 circuit_type and the respective argument in hs_ident_circuit_new().
2332 This field was set by clients (for introduction) and services (for
2333 introduction and rendezvous) but was never used afterwards. Fixes
2334 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
2336 o Minor bugfixes (operator tools):
2337 - Make tor-print-ed-signing-cert(1) print certificate expiration
2338 date in RFC 1123 and UNIX timestamp formats, to make output
2339 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
2341 o Minor bugfixes (rust):
2342 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2343 31463; bugfix on 0.3.5.4-alpha.
2344 - Raise the minimum rustc version to 1.31.0, as checked by configure
2345 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
2347 o Minor bugfixes (sendme, code structure):
2348 - Rename the trunnel SENDME file definition from sendme.trunnel to
2349 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
2350 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
2352 o Minor bugfixes (statistics):
2353 - Stop removing the ed25519 signature if the extra info file is too
2354 big. If the signature data was removed, but the keyword was kept,
2355 this could result in an unparseable extra info file. Fixes bug
2356 30958; bugfix on 0.2.7.2-alpha.
2358 o Minor bugfixes (subsystems):
2359 - Make the subsystem init order match the subsystem module
2360 dependencies. Call windows process security APIs as early as
2361 possible. Initialize logging before network and time, so that
2362 network and time can use logging. Fixes bug 31615; bugfix
2365 o Minor bugfixes (testing):
2366 - Teach the util/socketpair_ersatz test to work correctly when we
2367 have no network stack configured. Fixes bug 30804; bugfix
2370 o Minor bugfixes (v2 single onion services):
2371 - Always retry v2 single onion service intro and rend circuits with
2372 a 3-hop path. Previously, v2 single onion services used a 3-hop
2373 path when rendezvous circuits were retried after a remote or
2374 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2375 23818; bugfix on 0.2.9.3-alpha.
2377 o Minor bugfixes (v3 single onion services):
2378 - Always retry v3 single onion service intro and rend circuits with
2379 a 3-hop path. Previously, v3 single onion services used a 3-hop
2380 path when rend circuits were retried after a remote or delayed
2381 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2382 bugfix on 0.3.2.1-alpha.
2383 - Make v3 single onion services fall back to a 3-hop intro, when all
2384 intro points are unreachable via a 1-hop path. Previously, v3
2385 single onion services failed when all intro nodes were unreachable
2386 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2389 - Improve documentation in circuit padding subsystem. Patch by
2390 Tobias Pulls. Closes ticket 31113.
2391 - Include an example usage for IPv6 ORPort in our sample torrc.
2392 Closes ticket 31320; patch from Ali Raheem.
2393 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2394 notice.html so that operators no longer have to host it
2395 themselves. Closes ticket 31089.
2398 - No longer include recommended package digests in votes as detailed
2399 in proposal 301. The RecommendedPackages torrc option is
2400 deprecated and will no longer have any effect. "package" lines
2401 will still be considered when computing consensuses for consensus
2402 methods that include them. (This change has no effect on the list
2403 of recommended Tor versions, which is still in use.) Closes
2405 - Remove torctl.in from contrib/dist directory. Resolves
2409 - Run shellcheck for all non-third-party shell scripts that are
2410 shipped with Tor. Closes ticket 29533.
2411 - When checking shell scripts, ignore any user-created directories.
2412 Closes ticket 30967.
2414 o Code simplification and refactoring (config handling):
2415 - Extract our variable manipulation code from confparse.c to a new
2416 lower-level typedvar.h module. Closes ticket 30864.
2417 - Lower another layer of object management from confparse.c to a
2418 more general tool. Now typed structure members are accessible via
2419 an abstract type. Implements ticket 30914.
2420 - Move our backend logic for working with configuration and state
2421 files into a lower-level library, since it no longer depends on
2422 any tor-specific functionality. Closes ticket 31626.
2423 - Numerous simplifications in configuration-handling logic: remove
2424 duplicated macro definitions, replace magical names with flags,
2425 and refactor "TestingTorNetwork" to use the same default-option
2426 logic as the rest of Tor. Closes ticket 30935.
2427 - Replace our ad-hoc set of flags for configuration variables and
2428 configuration variable types with fine-grained orthogonal flags
2429 corresponding to the actual behavior we want. Closes ticket 31625.
2431 o Code simplification and refactoring (misc):
2432 - Eliminate some uses of lower-level control reply abstractions,
2433 primarily in the onion_helper functions. Closes ticket 30889.
2434 - Rework bootstrap tracking to use the new publish-subscribe
2435 subsystem. Closes ticket 29976.
2436 - Rewrite format_node_description() and router_get_verbose_nickname()
2437 to use strlcpy() and strlcat(). The previous implementation used
2438 memcpy() and pointer arithmetic, which was error-prone. Closes
2439 ticket 31545. This is CID 1452819.
2440 - Split extrainfo_dump_to_string() into smaller functions. Closes
2442 - Use the ptrdiff_t type consistently for expressing variable
2443 offsets and pointer differences. Previously we incorrectly (but
2444 harmlessly) used int and sometimes off_t for these cases. Closes
2446 - Use the subsystems mechanism to manage the main event loop code.
2447 Closes ticket 30806.
2448 - Various simplifications and minor improvements to the circuit
2449 padding machines. Patch by Tobias Pulls. Closes tickets 31112
2452 o Documentation (hard-coded directories):
2453 - Improve the documentation for the DirAuthority and FallbackDir
2454 torrc options. Closes ticket 30955.
2456 o Documentation (tor.1 man page):
2457 - Fix typo in tor.1 man page: the option is "--help", not "-help".
2458 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
2461 Changes in version 0.4.1.5 - 2019-08-20
2462 This is the first stable release in the 0.4.1.x series. This series
2463 adds experimental circuit-level padding, authenticated SENDME cells to
2464 defend against certain attacks, and several performance improvements
2465 to save on CPU consumption. It fixes bugs in bootstrapping and v3
2466 onion services. It also includes numerous smaller features and
2467 bugfixes on earlier versions.
2469 Per our support policy, we will support the 0.4.1.x series for nine
2470 months, or until three months after the release of a stable 0.4.2.x:
2471 whichever is longer. If you need longer-term support, please stick
2472 with 0.3.5.x, which will we plan to support until Feb 2022.
2474 Below are the changes since 0.4.1.4-rc. For a complete list of changes
2475 since 0.4.0.5, see the ReleaseNotes file.
2477 o Directory authority changes:
2478 - The directory authority "dizum" has a new IP address. Closes
2481 o Minor features (circuit padding logging):
2482 - Demote noisy client-side warn logs about circuit padding to
2483 protocol warnings. Add additional log messages and circuit ID
2484 fields to help with bug 30992 and any other future issues.
2486 o Minor bugfixes (circuit padding negotiation):
2487 - Bump the circuit padding protocol version to explicitly signify
2488 that the HS setup machine support is finalized in 0.4.1.x-stable.
2489 This also means that 0.4.1.x-alpha clients will not negotiate
2490 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
2491 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
2492 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
2494 o Minor bugfixes (circuit padding):
2495 - Ignore non-padding cells on padding circuits. This addresses
2496 various warning messages from subsystems that were not expecting
2497 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
2499 o Minor bugfixes (clock skew detection):
2500 - Don't believe clock skew results from NETINFO cells that appear to
2501 arrive before we sent the VERSIONS cells they are responding to.
2502 Previously, we would accept them up to 3 minutes "in the past".
2503 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2505 o Minor bugfixes (compatibility, standards compliance):
2506 - Fix a bug that would invoke undefined behavior on certain
2507 operating systems when trying to asprintf() a string exactly
2508 INT_MAX bytes long. We don't believe this is exploitable, but it's
2509 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
2510 Found and fixed by Tobias Stoeckmann.
2512 o Minor bugfixes (compilation warning):
2513 - Fix a compilation warning on Windows about casting a function
2514 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2517 o Minor bugfixes (compilation):
2518 - Avoid using labs() on time_t, which can cause compilation warnings
2519 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2521 o Minor bugfixes (distribution):
2522 - Do not ship any temporary files found in the
2523 scripts/maint/practracker directory. Fixes bug 31311; bugfix
2526 o Testing (continuous integration):
2527 - In Travis, make stem log a controller trace to the console, and
2528 tail stem's tor log after failure. Closes ticket 30591.
2529 - In Travis, only run the stem tests that use a tor binary. Closes
2533 Changes in version 0.4.1.4-rc - 2019-07-25
2534 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
2535 updates to a new list of fallback directories. If no new bugs are
2536 found, the next release in the 0.4.1.x serious should be stable.
2538 o Major bugfixes (circuit build, guard):
2539 - When considering upgrading circuits from "waiting for guard" to
2540 "open", always ignore circuits that are marked for close. Otherwise,
2541 we can end up in the situation where a subsystem is notified that
2542 a closing circuit has just opened, leading to undesirable
2543 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2545 o Minor features (continuous integration):
2546 - Our Travis configuration now uses Chutney to run some network
2547 integration tests automatically. Closes ticket 29280.
2549 o Minor features (fallback directory list):
2550 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2551 in December 2018 (of which ~122 were still functional), with a
2552 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2553 in June 2019. Closes ticket 28795.
2555 o Minor bugfixes (circuit padding):
2556 - On relays, properly check that a padding machine is absent before
2557 logging a warning about it being absent. Fixes bug 30649; bugfix
2559 - Add two NULL checks in unreachable places to silence Coverity (CID
2560 144729 and 1447291) and better future-proof ourselves. Fixes bug
2561 31024; bugfix on 0.4.1.1-alpha.
2563 o Minor bugfixes (crash on exit):
2564 - Avoid a set of possible code paths that could try to use freed
2565 memory in routerlist_free() while Tor was exiting. Fixes bug
2566 31003; bugfix on 0.1.2.2-alpha.
2568 o Minor bugfixes (logging):
2569 - Fix a conflict between the flag used for messaging-domain log
2570 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
2573 o Minor bugfixes (memory leaks):
2574 - Fix a trivial memory leak when parsing an invalid value from a
2575 download schedule in the configuration. Fixes bug 30894; bugfix
2578 o Code simplification and refactoring:
2579 - Remove some dead code from circpad_machine_remove_token() to fix
2580 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
2584 Changes in version 0.4.1.3-alpha - 2019-06-25
2585 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
2586 alpha, most of them from earlier release series.
2588 o Major bugfixes (Onion service reachability):
2589 - Properly clean up the introduction point map when circuits change
2590 purpose from onion service circuits to pathbias, measurement, or
2591 other circuit types. This should fix some service-side instances
2592 of introduction point failure. Fixes bug 29034; bugfix
2595 o Minor features (geoip):
2596 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
2597 Country database. Closes ticket 30852.
2599 o Minor features (logging):
2600 - Give a more useful assertion failure message if we think we have
2601 minherit() but we fail to make a region non-inheritable. Give a
2602 compile-time warning if our support for minherit() is incomplete.
2603 Closes ticket 30686.
2605 o Minor bugfixes (circuit isolation):
2606 - Fix a logic error that prevented the SessionGroup sub-option from
2607 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2609 o Minor bugfixes (continuous integration):
2610 - Allow the test-stem job to fail in Travis, because it sometimes
2611 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
2612 - Skip test_rebind on macOS in Travis, because it is unreliable on
2613 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2614 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
2615 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2617 o Minor bugfixes (directory authorities):
2618 - Stop crashing after parsing an unknown descriptor purpose
2619 annotation. We think this bug can only be triggered by modifying a
2620 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
2622 o Minor bugfixes (pluggable transports):
2623 - When running as a bridge with pluggable transports, always publish
2624 pluggable transport information in our extrainfo descriptor, even
2625 if ExtraInfoStatistics is 0. This information is needed by
2626 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
2629 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
2630 Closes ticket 30630.
2633 Changes in version 0.4.1.2-alpha - 2019-06-06
2634 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
2635 previous alpha, and some much older. It also contains minor testing
2636 improvements, and an improvement to the security of our authenticated
2637 SENDME implementation.
2639 o Major bugfixes (bridges):
2640 - Consider our directory information to have changed when our list
2641 of bridges changes. Previously, Tor would not re-compute the
2642 status of its directory information when bridges changed, and
2643 therefore would not realize that it was no longer able to build
2644 circuits. Fixes part of bug 29875.
2645 - Do not count previously configured working bridges towards our
2646 total of working bridges. Previously, when Tor's list of bridges
2647 changed, it would think that the old bridges were still usable,
2648 and delay fetching router descriptors for the new ones. Fixes part
2649 of bug 29875; bugfix on 0.3.0.1-alpha.
2651 o Major bugfixes (flow control, SENDME):
2652 - Decrement the stream-level package window after packaging a cell.
2653 Previously, it was done inside a log_debug() call, meaning that if
2654 debug logs were not enabled, the decrement would never happen, and
2655 thus the window would be out of sync with the other end point.
2656 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
2658 o Major bugfixes (onion service reachability):
2659 - Properly clean up the introduction point map and associated state
2660 when circuits change purpose from onion service circuits to
2661 pathbias, measurement, or other circuit types. This may fix some
2662 instances of introduction point failure. Fixes bug 29034; bugfix
2665 o Minor features (authenticated SENDME):
2666 - Ensure that there is enough randomness on every circuit to prevent
2667 an attacker from successfully predicting the hashes they will need
2668 to include in authenticated SENDME cells. At a random interval, if
2669 we have not sent randomness already, we now leave some extra space
2670 at the end of a cell that we can fill with random bytes. Closes
2673 o Minor features (continuous integration):
2674 - When running coverage builds on Travis, we now set
2675 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
2678 o Minor features (maintenance):
2679 - Add a new "make autostyle" target that developers can use to apply
2680 all automatic Tor style and consistency conversions to the
2681 codebase. Closes ticket 30539.
2683 o Minor features (testing):
2684 - The circuitpadding tests now use a reproducible RNG implementation,
2685 so that if a test fails, we can learn why. Part of ticket 28878.
2686 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
2687 to set the RNG seed for tests that use a reproducible RNG. Part of
2689 - When running tests in coverage mode, take additional care to make
2690 our coverage deterministic, so that we can accurately track
2691 changes in code coverage. Closes ticket 30519.
2693 o Minor bugfixes (configuration, proxies):
2694 - Fix a bug that prevented us from supporting SOCKS5 proxies that
2695 want authentication along with configured (but unused!)
2696 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
2698 o Minor bugfixes (controller):
2699 - POSTDESCRIPTOR requests should work again. Previously, they were
2700 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
2702 - Repair the HSFETCH command so that it works again. Previously, it
2703 expected a body when it shouldn't have. Fixes bug 30646; bugfix
2706 o Minor bugfixes (developer tooling):
2707 - Fix pre-push hook to allow fixup and squash commits when pushing
2708 to non-upstream git remote. Fixes bug 30286; bugfix
2711 o Minor bugfixes (directory authority):
2712 - Move the "bandwidth-file-headers" line in directory authority
2713 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
2716 o Minor bugfixes (NetBSD):
2717 - Fix usage of minherit() on NetBSD and other platforms that define
2718 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
2719 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
2721 o Minor bugfixes (out-of-memory handler):
2722 - When purging the DNS cache because of an out-of-memory condition,
2723 try purging just the older entries at first. Previously, we would
2724 always purge the whole thing. Fixes bug 29617; bugfix
2727 o Minor bugfixes (portability):
2728 - Avoid crashing in our tor_vasprintf() implementation on systems
2729 that define neither vasprintf() nor _vscprintf(). (This bug has
2730 been here long enough that we question whether people are running
2731 Tor on such systems, but we're applying the fix out of caution.)
2732 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2735 o Minor bugfixes (shutdown, libevent, memory safety):
2736 - Avoid use-after-free bugs when shutting down, by making sure that
2737 we shut down libevent only after shutting down all of its users.
2738 We believe these are harmless in practice, since they only occur
2739 on the shutdown path, and do not involve any attacker-controlled
2740 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
2742 o Minor bugfixes (static analysis):
2743 - Fix several spurious Coverity warnings about the unit tests, to
2744 lower our chances of missing real warnings in the future. Fixes
2745 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
2748 - Specify torrc paths (with empty files) when launching tor in
2749 integration tests; refrain from reading user and system torrcs.
2750 Resolves issue 29702.
2753 Changes in version 0.4.1.1-alpha - 2019-05-22
2754 This is the first alpha in the 0.4.1.x series. It introduces
2755 lightweight circuit padding to make some onion-service circuits harder
2756 to distinguish, includes a new "authenticated SENDME" feature to make
2757 certain denial-of-service attacks more difficult, and improves
2758 performance in several areas.
2760 o Major features (circuit padding):
2761 - Onion service clients now add padding cells at the start of their
2762 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
2763 look more like general purpose Exit traffic. The overhead for this
2764 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
2765 extra upstream cell and 10 downstream cells for INTRODUCE
2766 circuits. This feature is only enabled when also supported by the
2767 circuit's middle node. (Clients may specify fixed middle nodes
2768 with the MiddleNodes option, and may force-disable this feature
2769 with the CircuitPadding option.) Closes ticket 28634.
2771 o Major features (code organization):
2772 - Tor now includes a generic publish-subscribe message-passing
2773 subsystem that we can use to organize intermodule dependencies. We
2774 hope to use this to reduce dependencies between modules that don't
2775 need to be related, and to generally simplify our codebase. Closes
2778 o Major features (controller protocol):
2779 - Controller commands are now parsed using a generalized parsing
2780 subsystem. Previously, each controller command was responsible for
2781 parsing its own input, which led to strange inconsistencies.
2782 Closes ticket 30091.
2784 o Major features (flow control):
2785 - Implement authenticated SENDMEs as detailed in proposal 289. A
2786 SENDME cell now includes the digest of the traffic that it
2787 acknowledges, so that once an end point receives the SENDME, it
2788 can confirm the other side's knowledge of the previous cells that
2789 were sent, and prevent certain types of denial-of-service attacks.
2790 This behavior is controlled by two new consensus parameters: see
2791 the proposal for more details. Fixes ticket 26288.
2793 o Major features (performance):
2794 - Our node selection algorithm now excludes nodes in linear time.
2795 Previously, the algorithm was quadratic, which could slow down
2796 heavily used onion services. Closes ticket 30307.
2798 o Major features (performance, RNG):
2799 - Tor now constructs a fast secure pseudorandom number generator for
2800 each thread, to use when performance is critical. This PRNG is
2801 based on AES-CTR, using a buffering construction similar to
2802 libottery and the (newer) OpenBSD arc4random() code. It
2803 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
2804 small outputs. Although we believe it to be cryptographically
2805 strong, we are only using it when necessary for performance.
2806 Implements tickets 29023 and 29536.
2808 o Major bugfixes (onion service v3):
2809 - Fix an unreachable bug in which an introduction point could try to
2810 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2811 to encode, leading the relay to assert(). We've consolidated the
2812 ABI values into Trunnel now. Fixes bug 30454; bugfix
2814 - Clients can now handle unknown status codes from INTRODUCE_ACK
2815 cells. (The NACK behavior will stay the same.) This will allow us
2816 to extend status codes in the future without breaking the normal
2817 client behavior. Fixes another part of bug 30454; bugfix
2820 o Minor features (circuit padding):
2821 - We now use a fast PRNG when scheduling circuit padding. Part of
2823 - Allow the padding machine designer to pick the edges of their
2824 histogram instead of trying to compute them automatically using an
2825 exponential formula. Resolves some undefined behavior in the case
2826 of small histograms and allows greater flexibility on machine
2827 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
2828 - Allow circuit padding machines to hold a circuit open until they
2829 are done padding it. Closes ticket 28780.
2831 o Minor features (compile-time modules):
2832 - Add a "--list-modules" command to print a list of which compile-
2833 time modules are enabled. Closes ticket 30452.
2835 o Minor features (continuous integration):
2836 - Remove sudo configuration lines from .travis.yml as they are no
2837 longer needed with current Travis build environment. Resolves
2839 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2841 o Minor features (controller):
2842 - Add onion service version 3 support to the HSFETCH command.
2843 Previously, only version 2 onion services were supported. Closes
2844 ticket 25417. Patch by Neel Chauhan.
2846 o Minor features (debugging):
2847 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
2848 logging of additional information during assert failure. Now we
2849 can use format strings to include information for trouble
2850 shooting. Resolves ticket 29662.
2852 o Minor features (defense in depth):
2853 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
2854 case a bug causes them to be used later. Closes ticket 30176.
2855 Patch from Tobias Stoeckmann.
2856 - Tor now uses a cryptographically strong PRNG even for decisions
2857 that we do not believe are security-sensitive. Previously, for
2858 performance reasons, we had used a trivially predictable linear
2859 congruential generator algorithm for certain load-balancing and
2860 statistical sampling decisions. Now we use our fast RNG in those
2861 cases. Closes ticket 29542.
2863 o Minor features (developer tools):
2864 - Tor's "practracker" test script now checks for files and functions
2865 that seem too long and complicated. Existing overlong functions
2866 and files are accepted for now, but should eventually be
2867 refactored. Closes ticket 29221.
2868 - Add some scripts used for git maintenance to scripts/git. Closes
2870 - Call practracker from pre-push and pre-commit git hooks to let
2871 developers know if they made any code style violations. Closes
2873 - Add a script to check that each header has a well-formed and
2874 unique guard macro. Closes ticket 29756.
2876 o Minor features (geoip):
2877 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
2878 Country database. Closes ticket 30522.
2880 o Minor features (HTTP tunnel):
2881 - Return an informative web page when the HTTPTunnelPort is used as
2882 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
2884 o Minor features (IPv6, v3 onion services):
2885 - Make v3 onion services put IPv6 addresses in service descriptors.
2886 Before this change, service descriptors only contained IPv4
2887 addresses. Implements 26992.
2889 o Minor features (modularity):
2890 - The "--disable-module-dirauth" compile-time option now disables
2891 even more dirauth-only code. Closes ticket 30345.
2893 o Minor features (performance):
2894 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
2895 1.1.1 and later), since they tend to be faster than tiny-keccak.
2896 Closes ticket 28837.
2898 o Minor features (testing):
2899 - Tor's unit test code now contains helper functions to replace the
2900 PRNG with a deterministic or reproducible version for testing.
2901 Previously, various tests implemented this in various ways.
2902 Implements ticket 29732.
2903 - We now have a script, cov-test-determinism.sh, to identify places
2904 where our unit test coverage has become nondeterministic. Closes
2906 - Check that representative subsets of values of `int` and `unsigned
2907 int` can be represented by `void *`. Resolves issue 29537.
2909 o Minor bugfixes (bridge authority):
2910 - Bridge authorities now set bridges as running or non-running when
2911 about to dump their status to a file. Previously, they set bridges
2912 as running in response to a GETINFO command, but those shouldn't
2913 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
2914 Patch by Neel Chauhan.
2916 o Minor bugfixes (channel padding statistics):
2917 - Channel padding write totals and padding-enabled totals are now
2918 counted properly in relay extrainfo descriptors. Fixes bug 29231;
2919 bugfix on 0.3.1.1-alpha.
2921 o Minor bugfixes (circuit padding):
2922 - Add a "CircuitPadding" torrc option to disable circuit padding.
2923 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
2924 - Allow circuit padding machines to specify that they do not
2925 contribute much overhead, and provide consensus flags and torrc
2926 options to force clients to only use these low overhead machines.
2927 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
2928 - Provide a consensus parameter to fully disable circuit padding, to
2929 be used in emergency network overload situations. Fixes bug 30173;
2930 bugfix on 0.4.0.1-alpha.
2931 - The circuit padding subsystem will no longer schedule padding if
2932 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
2933 - Inspect a circuit-level cell queue before sending padding, to
2934 avoid sending padding while too much data is already queued. Fixes
2935 bug 29204; bugfix on 0.4.0.1-alpha.
2936 - Avoid calling monotime_absolute_usec() in circuit padding machines
2937 that do not use token removal or circuit RTT estimation. Fixes bug
2938 29085; bugfix on 0.4.0.1-alpha.
2940 o Minor bugfixes (compilation, unusual configurations):
2941 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
2942 due to missing declarations of abort(), and prevent other such
2943 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
2945 o Minor bugfixes (controller protocol):
2946 - Teach the controller parser to distinguish an object preceded by
2947 an argument list from one without. Previously, it couldn't
2948 distinguish an argument list from the first line of a multiline
2949 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
2951 o Minor bugfixes (directory authority, ipv6):
2952 - Directory authorities with IPv6 support now always mark themselves
2953 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
2954 Patch by Neel Chauhan.
2956 o Minor bugfixes (documentation):
2957 - Improve the documentation for using MapAddress with ".exit". Fixes
2958 bug 30109; bugfix on 0.1.0.1-rc.
2959 - Improve the monotonic time module and function documentation to
2960 explain what "monotonic" actually means, and document some results
2961 that have surprised people. Fixes bug 29640; bugfix
2963 - Use proper formatting when providing an example on quoting options
2964 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
2966 o Minor bugfixes (logging):
2967 - Do not log a warning when running with an OpenSSL version other
2968 than the one Tor was compiled with, if the two versions should be
2969 compatible. Previously, we would warn whenever the version was
2970 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
2971 - Warn operators when the MyFamily option is set but ContactInfo is
2972 missing, as the latter should be set too. Fixes bug 25110; bugfix
2975 o Minor bugfixes (memory leak):
2976 - Avoid a minor memory leak that could occur on relays when failing
2977 to create a "keys" directory. Fixes bug 30148; bugfix
2980 o Minor bugfixes (onion services):
2981 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2982 implemenation) when failing to load an onion service client
2983 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2984 - When refusing to launch a controller's HSFETCH request because of
2985 rate-limiting, respond to the controller with a new response,
2986 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
2987 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
2989 - When relaunching a circuit to a rendezvous service, mark the
2990 circuit as needing high-uptime routers as appropriate. Fixes bug
2991 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
2992 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
2993 (IPv6 support for v3 onion services is still incomplete: see
2994 ticket 23493 for details.) Fixes bug 23588; bugfix on
2995 0.3.2.1-alpha. Patch by Neel Chauhan.
2997 o Minor bugfixes (onion services, performance):
2998 - When building circuits to onion services, call tor_addr_parse()
2999 less often. Previously, we called tor_addr_parse() in
3000 circuit_is_acceptable() even if its output wasn't used. This
3001 change should improve performance when building circuits. Fixes
3002 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
3004 o Minor bugfixes (performance):
3005 - When checking whether a node is a bridge, use a fast check to make
3006 sure that its identity is set. Previously, we used a constant-time
3007 check, which is not necessary in this case. Fixes bug 30308;
3008 bugfix on 0.3.5.1-alpha.
3010 o Minor bugfixes (pluggable transports):
3011 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
3012 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
3014 o Minor bugfixes (probability distributions):
3015 - Refactor and improve parts of the probability distribution code
3016 that made Coverity complain. Fixes bug 29805; bugfix
3019 o Minor bugfixes (python):
3020 - Stop assuming that /usr/bin/python3 exists. For scripts that work
3021 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
3022 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
3024 o Minor bugfixes (relay):
3025 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
3026 is auto, act as if ExitRelay is 1. Previously, we would ignore
3027 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
3028 0.3.5.1-alpha. Patch by Neel Chauhan.
3030 o Minor bugfixes (stats):
3031 - When ExtraInfoStatistics is 0, stop including bandwidth usage
3032 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
3033 bridge statistics by country in extra-info documents. Fixes bug
3034 29018; bugfix on 0.2.4.1-alpha.
3036 o Minor bugfixes (testing):
3037 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
3038 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
3039 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
3040 - Fix some incorrect code in the v3 onion service unit tests. Fixes
3041 bug 29243; bugfix on 0.3.2.1-alpha.
3042 - In the "routerkeys/*" tests, check the return values of mkdir()
3043 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
3044 Found by Coverity as CID 1444254.
3045 - Split test_utils_general() into several smaller test functions.
3046 This makes it easier to perform resource deallocation on assert
3047 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
3048 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
3050 o Minor bugfixes (tor-resolve):
3051 - Fix a memory leak in tor-resolve that could happen if Tor gave it
3052 a malformed SOCKS response. (Memory leaks in tor-resolve don't
3053 actually matter, but it's good to fix them anyway.) Fixes bug
3054 30151; bugfix on 0.4.0.1-alpha.
3056 o Code simplification and refactoring:
3057 - Abstract out the low-level formatting of replies on the control
3058 port. Implements ticket 30007.
3059 - Add several assertions in an attempt to fix some Coverity
3060 warnings. Closes ticket 30149.
3061 - Introduce a connection_dir_buf_add() helper function that checks
3062 for compress_state of dir_connection_t and automatically writes a
3063 string to directory connection with or without compression.
3064 Resolves issue 28816.
3065 - Make the base32_decode() API return the number of bytes written,
3066 for consistency with base64_decode(). Closes ticket 28913.
3067 - Move most relay-only periodic events out of mainloop.c into the
3068 relay subsystem. Closes ticket 30414.
3069 - Refactor and encapsulate parts of the codebase that manipulate
3070 crypt_path_t objects. Resolves issue 30236.
3071 - Refactor several places in our code that Coverity incorrectly
3072 believed might have memory leaks. Closes ticket 30147.
3073 - Remove redundant return values in crypto_format, and the
3074 associated return value checks elsewhere in the code. Make the
3075 implementations in crypto_format consistent, and remove redundant
3076 code. Resolves ticket 29660.
3077 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
3078 it is not a constant-time function. Closes ticket 30309.
3079 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
3080 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
3081 bugfix on 0.3.2.1-alpha.
3082 - Simplify v3 onion service link specifier handling code. Fixes bug
3083 23576; bugfix on 0.3.2.1-alpha.
3084 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
3085 code. Resolves ticket 29108.
3086 - Split control.c into several submodules, in preparation for
3087 distributing its current responsibilities throughout the codebase.
3088 Closes ticket 29894.
3089 - Start to move responsibility for knowing about periodic events to
3090 the appropriate subsystems, so that the mainloop doesn't need to
3091 know all the periodic events in the rest of the codebase.
3092 Implements tickets 30293 and 30294.
3095 - Document how to find git commits and tags for bug fixes in
3096 CodingStandards.md. Update some file documentation. Closes
3100 - Remove the linux-tor-prio.sh script from contrib/operator-tools
3101 directory. Resolves issue 29434.
3102 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
3103 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
3106 o Code simplification and refactoring (shell scripts):
3107 - Clean up many of our shell scripts to fix shellcheck warnings.
3108 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
3109 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
3110 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
3111 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
3112 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
3113 nagios-check-tor-authority-cert (ticket 29071),
3114 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
3115 (ticket 29060), test_key_expiration.sh (ticket 30002),
3116 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
3119 o Testing (chutney):
3120 - In "make test-network-all", test IPv6-only v3 single onion
3121 services, using the chutney network single-onion-v23-ipv6-md.
3122 Closes ticket 27251.
3125 Changes in version 0.4.0.5 - 2019-05-02
3126 This is the first stable release in the 0.4.0.x series. It contains
3127 improvements for power management and bootstrap reporting, as well as
3128 preliminary backend support for circuit padding to prevent some kinds
3129 of traffic analysis. It also continues our work in refactoring Tor for
3130 long-term maintainability.
3132 Per our support policy, we will support the 0.4.0.x series for nine
3133 months, or until three months after the release of a stable 0.4.1.x:
3134 whichever is longer. If you need longer-term support, please stick
3135 with 0.3.5.x, which will we plan to support until Feb 2022.
3137 Below are the changes since 0.4.0.4-rc. For a complete list of changes
3138 since 0.3.5.7, see the ReleaseNotes file.
3140 o Minor features (continuous integration):
3141 - In Travis, tell timelimit to use stem's backtrace signals, and
3142 launch python directly from timelimit, so python receives the
3143 signals from timelimit, rather than make. Closes ticket 30117.
3145 o Minor features (diagnostic):
3146 - Add more diagnostic log messages in an attempt to solve the issue
3147 of NUL bytes appearing in a microdescriptor cache. Related to
3150 o Minor features (testing):
3151 - Use the approx_time() function when setting the "Expires" header
3152 in directory replies, to make them more testable. Needed for
3155 o Minor bugfixes (rust):
3156 - Abort on panic in all build profiles, instead of potentially
3157 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
3159 o Minor bugfixes (shellcheck):
3160 - Look for scripts in their correct locations during "make
3161 shellcheck". Previously we had looked in the wrong place during
3162 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
3164 o Minor bugfixes (testing):
3165 - Check the time in the "Expires" header using approx_time(). Fixes
3166 bug 30001; bugfix on 0.4.0.4-rc.
3168 o Minor bugfixes (UI):
3169 - Lower log level of unlink() errors during bootstrap. Fixes bug
3170 29930; bugfix on 0.4.0.1-alpha.
3173 Changes in version 0.4.0.4-rc - 2019-04-11
3174 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
3175 several bugs from earlier versions, including some that had affected
3176 stability, and one that prevented relays from working with NSS.
3178 o Major bugfixes (NSS, relay):
3179 - When running with NSS, disable TLS 1.2 ciphersuites that use
3180 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3181 these ciphersuites don't work -- which caused relays to fail to
3182 handshake with one another when these ciphersuites were enabled.
3183 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3185 o Minor features (bandwidth authority):
3186 - Make bandwidth authorities ignore relays that are reported in the
3187 bandwidth file with the flag "vote=0". This change allows us to
3188 report unmeasured relays for diagnostic reasons without including
3189 their bandwidth in the bandwidth authorities' vote. Closes
3191 - When a directory authority is using a bandwidth file to obtain the
3192 bandwidth values that will be included in the next vote, serve
3193 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
3196 o Minor features (circuit padding):
3197 - Stop warning about undefined behavior in the probability
3198 distribution tests. Float division by zero may technically be
3199 undefined behavior in C, but it's well defined in IEEE 754.
3200 Partial backport of 29298. Closes ticket 29527; bugfix
3203 o Minor features (continuous integration):
3204 - On Travis Rust builds, cleanup Rust registry and refrain from
3205 caching the "target/" directory to speed up builds. Resolves
3208 o Minor features (dormant mode):
3209 - Add a DormantCanceledByStartup option to tell Tor that it should
3210 treat a startup event as cancelling any previous dormant state.
3211 Integrators should use this option with caution: it should only be
3212 used if Tor is being started because of something that the user
3213 did, and not if Tor is being automatically started in the
3214 background. Closes ticket 29357.
3216 o Minor features (geoip):
3217 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
3218 Country database. Closes ticket 29992.
3220 o Minor features (NSS, diagnostic):
3221 - Try to log an error from NSS (if there is any) and a more useful
3222 description of our situation if we are using NSS and a call to
3223 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
3225 o Minor bugfixes (security):
3226 - Fix a potential double free bug when reading huge bandwidth files.
3227 The issue is not exploitable in the current Tor network because
3228 the vulnerable code is only reached when directory authorities
3229 read bandwidth files, but bandwidth files come from a trusted
3230 source (usually the authorities themselves). Furthermore, the
3231 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
3232 which are not used by any of the current authorities. Fixes bug
3233 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
3235 - Verify in more places that we are not about to create a buffer
3236 with more than INT_MAX bytes, to avoid possible OOB access in the
3237 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
3238 fixed by Tobias Stoeckmann.
3240 o Minor bugfix (continuous integration):
3241 - Reset coverage state on disk after Travis CI has finished. This
3242 should prevent future coverage merge errors from causing the test
3243 suite for the "process" subsystem to fail. The process subsystem
3244 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
3246 - Terminate test-stem if it takes more than 9.5 minutes to run.
3247 (Travis terminates the job after 10 minutes of no output.)
3248 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
3250 o Minor bugfixes (bootstrap reporting):
3251 - During bootstrap reporting, correctly distinguish pluggable
3252 transports from plain proxies. Fixes bug 28925; bugfix
3255 o Minor bugfixes (C correctness):
3256 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
3257 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
3260 o Minor bugfixes (circuitpadding testing):
3261 - Minor tweaks to avoid rare test failures related to timers and
3262 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
3264 o Minor bugfixes (directory authorities):
3265 - Actually include the bandwidth-file-digest line in directory
3266 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
3268 o Minor bugfixes (logging):
3269 - On Windows, when errors cause us to reload a consensus from disk,
3270 tell the user that we are retrying at log level "notice".
3271 Previously we only logged this information at "info", which was
3272 confusing because the errors themselves were logged at "warning".
3273 Improves previous fix for 28614. Fixes bug 30004; bugfix
3276 o Minor bugfixes (pluggable transports):
3277 - Restore old behavior when it comes to discovering the path of a
3278 given Pluggable Transport executable file. A change in
3279 0.4.0.1-alpha had broken this behavior on paths containing a
3280 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
3282 o Minor bugfixes (testing):
3283 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
3284 recent test-network.sh to use new chutney features in CI. Fixes
3285 bug 29703; bugfix on 0.2.9.1-alpha.
3286 - Fix a test failure on Windows caused by an unexpected "BUG"
3287 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
3290 o Minor bugfixes (TLS protocol):
3291 - When classifying a client's selection of TLS ciphers, if the
3292 client ciphers are not yet available, do not cache the result.
3293 Previously, we had cached the unavailability of the cipher list
3294 and never looked again, which in turn led us to assume that the
3295 client only supported the ancient V1 link protocol. This, in turn,
3296 was causing Stem integration tests to stall in some cases. Fixes
3297 bug 30021; bugfix on 0.2.4.8-alpha.
3299 o Code simplification and refactoring:
3300 - Introduce a connection_dir_buf_add() helper function that detects
3301 whether compression is in use, and adds a string accordingly.
3302 Resolves issue 28816.
3303 - Refactor handle_get_next_bandwidth() to use
3304 connection_dir_buf_add(). Implements ticket 29897.
3307 - Clarify that Tor performs stream isolation among *Port listeners
3308 by default. Resolves issue 29121.
3311 Changes in version 0.4.0.3-alpha - 2019-03-22
3312 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
3313 bugs from earlier versions.
3315 o Minor features (address selection):
3316 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3317 private for others. This subnet is the RFC 6598 (Carrier Grade
3318 NAT) IP range, and is deployed by many ISPs as an alternative to
3319 RFC 1918 that does not break existing internal networks. Tor now
3320 blocks SOCKS and control ports on these addresses and warns users
3321 if client ports or ExtORPorts are listening on a RFC 6598 address.
3322 Closes ticket 28525. Patch by Neel Chauhan.
3324 o Minor features (geoip):
3325 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
3326 Country database. Closes ticket 29666.
3328 o Minor bugfixes (circuitpadding):
3329 - Inspect the circuit-level cell queue before sending padding, to
3330 avoid sending padding when too much data is queued. Fixes bug
3331 29204; bugfix on 0.4.0.1-alpha.
3333 o Minor bugfixes (logging):
3334 - Correct a misleading error message when IPv4Only or IPv6Only is
3335 used but the resolved address can not be interpreted as an address
3336 of the specified IP version. Fixes bug 13221; bugfix on
3337 0.2.3.9-alpha. Patch from Kris Katterjohn.
3338 - Log the correct port number for listening sockets when "auto" is
3339 used to let Tor pick the port number. Previously, port 0 was
3340 logged instead of the actual port number. Fixes bug 29144; bugfix
3341 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3342 - Stop logging a BUG() warning when Tor is waiting for exit
3343 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3345 o Minor bugfixes (memory management):
3346 - Refactor the shared random state's memory management so that it
3347 actually takes ownership of the shared random value pointers.
3348 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
3350 o Minor bugfixes (memory management, testing):
3351 - Stop leaking parts of the shared random state in the shared-random
3352 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
3354 o Minor bugfixes (pluggable transports):
3355 - Fix an assertion failure crash bug when a pluggable transport is
3356 terminated during the bootstrap phase. Fixes bug 29562; bugfix
3359 o Minor bugfixes (Rust, protover):
3360 - Add a missing "Padding" value to the Rust implementation of
3361 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
3363 o Minor bugfixes (single onion services):
3364 - Allow connections to single onion services to remain idle without
3365 being disconnected. Previously, relays acting as rendezvous points
3366 for single onion services were mistakenly closing idle rendezvous
3367 circuits after 60 seconds, thinking that they were unused
3368 directory-fetching circuits that had served their purpose. Fixes
3369 bug 29665; bugfix on 0.2.1.26.
3371 o Minor bugfixes (stats):
3372 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
3373 relay and bridge extra-info documents. Fixes bug 29017; bugfix
3376 o Minor bugfixes (testing):
3377 - Downgrade some LOG_ERR messages in the address/* tests to
3378 warnings. The LOG_ERR messages were occurring when we had no
3379 configured network. We were failing the unit tests, because we
3380 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
3381 29530; bugfix on 0.3.5.8.
3382 - Fix our gcov wrapper script to look for object files at the
3383 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
3384 - Decrease the false positive rate of stochastic probability
3385 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
3387 o Minor bugfixes (Windows, CI):
3388 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
3389 Windows Server 2012 R2 job. The remaining 2 jobs still provide
3390 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
3391 fast_finish, so failed jobs terminate the build immediately. Fixes
3392 bug 29601; bugfix on 0.3.5.4-alpha.
3395 Changes in version 0.3.5.8 - 2019-02-21
3396 Tor 0.3.5.8 backports several fixes from later releases, including fixes
3397 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
3400 It also includes a fix for a medium-severity security bug affecting Tor
3401 0.3.2.1-alpha and later. All Tor instances running an affected release
3402 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3404 o Major bugfixes (cell scheduler, KIST, security):
3405 - Make KIST consider the outbuf length when computing what it can
3406 put in the outbuf. Previously, KIST acted as though the outbuf
3407 were empty, which could lead to the outbuf becoming too full. It
3408 is possible that an attacker could exploit this bug to cause a Tor
3409 client or relay to run out of memory and crash. Fixes bug 29168;
3410 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3411 TROVE-2019-001 and CVE-2019-8955.
3413 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
3414 - Gracefully handle empty username/password fields in SOCKS5
3415 username/password auth message and allow SOCKS5 handshake to
3416 continue. Previously, we had rejected these handshakes, breaking
3417 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3419 o Minor features (compilation, backport from 0.4.0.2-alpha):
3420 - Compile correctly when OpenSSL is built with engine support
3421 disabled, or with deprecated APIs disabled. Closes ticket 29026.
3422 Patches from "Mangix".
3424 o Minor features (geoip):
3425 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3426 Country database. Closes ticket 29478.
3428 o Minor features (testing, backport from 0.4.0.2-alpha):
3429 - Treat all unexpected ERR and BUG messages as test failures. Closes
3432 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
3433 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
3434 connection waiting for a descriptor that we actually have in the
3435 cache. It turns out that this can actually happen, though it is
3436 rare. Now, tor will recover and retry the descriptor. Fixes bug
3437 28669; bugfix on 0.3.2.4-alpha.
3439 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
3440 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
3441 IPv6 socket was bound using an address family of AF_INET instead
3442 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
3445 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3446 - Update Cargo.lock file to match the version made by the latest
3447 version of Rust, so that "make distcheck" will pass again. Fixes
3448 bug 29244; bugfix on 0.3.3.4-alpha.
3450 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
3451 - Select guards even if the consensus has expired, as long as the
3452 consensus is still reasonably live. Fixes bug 24661; bugfix
3455 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
3456 - Compile correctly on OpenBSD; previously, we were missing some
3457 headers required in order to detect it properly. Fixes bug 28938;
3458 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3460 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
3461 - Describe the contents of the v3 onion service client authorization
3462 files correctly: They hold public keys, not private keys. Fixes
3463 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3465 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
3466 - Rework rep_hist_log_link_protocol_counts() to iterate through all
3467 link protocol versions when logging incoming/outgoing connection
3468 counts. Tor no longer skips version 5, and we won't have to
3469 remember to update this function when new link protocol version is
3470 developed. Fixes bug 28920; bugfix on 0.2.6.10.
3472 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
3473 - Log more information at "warning" level when unable to read a
3474 private key; log more information at "info" level when unable to
3475 read a public key. We had warnings here before, but they were lost
3476 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
3478 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
3479 - The amount of total available physical memory is now determined
3480 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
3481 when it is defined and a 64-bit variant is not available. Fixes
3482 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
3484 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3485 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
3486 than one private key for a hidden service. Fixes bug 29040; bugfix
3488 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
3489 "debug" level. Tor used to log it as a warning, which caused very
3490 long log lines to appear for some users. Fixes bug 29135; bugfix
3492 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3493 as a warning. Instead, log it as a protocol warning, because there
3494 is nothing that relay operators can do to fix it. Fixes bug 29029;
3495 bugfix on 0.2.5.7-rc.
3497 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
3498 - Mark outdated dirservers when Tor only has a reasonably live
3499 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
3501 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
3502 - Detect and suppress "bug" warnings from the util/time test on
3503 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
3504 - Do not log an error-level message if we fail to find an IPv6
3505 network interface from the unit tests. Fixes bug 29160; bugfix
3508 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
3509 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
3510 Some users took this phrasing to mean that the mentioned guard was
3511 under their control or responsibility, which it is not. Fixes bug
3512 28895; bugfix on Tor 0.3.0.1-alpha.
3515 Changes in version 0.3.4.11 - 2019-02-21
3516 Tor 0.3.4.11 is the third stable release in its series. It includes
3517 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
3518 later. All Tor instances running an affected release should upgrade to
3519 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3521 o Major bugfixes (cell scheduler, KIST, security):
3522 - Make KIST consider the outbuf length when computing what it can
3523 put in the outbuf. Previously, KIST acted as though the outbuf
3524 were empty, which could lead to the outbuf becoming too full. It
3525 is possible that an attacker could exploit this bug to cause a Tor
3526 client or relay to run out of memory and crash. Fixes bug 29168;
3527 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3528 TROVE-2019-001 and CVE-2019-8955.
3530 o Minor features (geoip):
3531 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3532 Country database. Closes ticket 29478.
3534 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3535 - Update Cargo.lock file to match the version made by the latest
3536 version of Rust, so that "make distcheck" will pass again. Fixes
3537 bug 29244; bugfix on 0.3.3.4-alpha.
3539 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3540 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3541 as a warning. Instead, log it as a protocol warning, because there
3542 is nothing that relay operators can do to fix it. Fixes bug 29029;
3543 bugfix on 0.2.5.7-rc.
3546 Changes in version 0.3.3.12 - 2019-02-21
3547 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
3548 0.3.2.1-alpha and later. All Tor instances running an affected release
3549 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3551 This release marks the end of support for the Tor 0.3.3.x series. We
3552 recommend that users switch to either the Tor 0.3.4 series (supported
3553 until at least 10 June 2019), or the Tor 0.3.5 series, which will
3554 receive long-term support until at least 1 Feb 2022.
3556 o Major bugfixes (cell scheduler, KIST, security):
3557 - Make KIST consider the outbuf length when computing what it can
3558 put in the outbuf. Previously, KIST acted as though the outbuf
3559 were empty, which could lead to the outbuf becoming too full. It
3560 is possible that an attacker could exploit this bug to cause a Tor
3561 client or relay to run out of memory and crash. Fixes bug 29168;
3562 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3563 TROVE-2019-001 and CVE-2019-8955.
3565 o Minor features (geoip):
3566 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3567 Country database. Closes ticket 29478.
3569 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3570 - Update Cargo.lock file to match the version made by the latest
3571 version of Rust, so that "make distcheck" will pass again. Fixes
3572 bug 29244; bugfix on 0.3.3.4-alpha.
3574 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3575 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3576 as a warning. Instead, log it as a protocol warning, because there
3577 is nothing that relay operators can do to fix it. Fixes bug 29029;
3578 bugfix on 0.2.5.7-rc.
3581 Changes in version 0.4.0.2-alpha - 2019-02-21
3582 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
3583 bugs from earlier versions, including several that had broken
3584 backward compatibility.
3586 It also includes a fix for a medium-severity security bug affecting Tor
3587 0.3.2.1-alpha and later. All Tor instances running an affected release
3588 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3590 o Major bugfixes (cell scheduler, KIST, security):
3591 - Make KIST consider the outbuf length when computing what it can
3592 put in the outbuf. Previously, KIST acted as though the outbuf
3593 were empty, which could lead to the outbuf becoming too full. It
3594 is possible that an attacker could exploit this bug to cause a Tor
3595 client or relay to run out of memory and crash. Fixes bug 29168;
3596 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3597 TROVE-2019-001 and CVE-2019-8955.
3599 o Major bugfixes (networking):
3600 - Gracefully handle empty username/password fields in SOCKS5
3601 username/password auth messsage and allow SOCKS5 handshake to
3602 continue. Previously, we had rejected these handshakes, breaking
3603 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3605 o Major bugfixes (windows, startup):
3606 - When reading a consensus file from disk, detect whether it was
3607 written in text mode, and re-read it in text mode if so. Always
3608 write consensus files in binary mode so that we can map them into
3609 memory later. Previously, we had written in text mode, which
3610 confused us when we tried to map the file on windows. Fixes bug
3611 28614; bugfix on 0.4.0.1-alpha.
3613 o Minor features (compilation):
3614 - Compile correctly when OpenSSL is built with engine support
3615 disabled, or with deprecated APIs disabled. Closes ticket 29026.
3616 Patches from "Mangix".
3618 o Minor features (developer tooling):
3619 - Check that bugfix versions in changes files look like Tor versions
3620 from the versions spec. Warn when bugfixes claim to be on a future
3621 release. Closes ticket 27761.
3622 - Provide a git pre-commit hook that disallows committing if we have
3623 any failures in our code and changelog formatting checks. It is
3624 now available in scripts/maint/pre-commit.git-hook. Implements
3627 o Minor features (directory authority):
3628 - When a directory authority is using a bandwidth file to obtain
3629 bandwidth values, include the digest of that file in the vote.
3630 Closes ticket 26698.
3632 o Minor features (geoip):
3633 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3634 Country database. Closes ticket 29478.
3636 o Minor features (testing):
3637 - Treat all unexpected ERR and BUG messages as test failures. Closes
3640 o Minor bugfixes (build, compatibility, rust):
3641 - Update Cargo.lock file to match the version made by the latest
3642 version of Rust, so that "make distcheck" will pass again. Fixes
3643 bug 29244; bugfix on 0.3.3.4-alpha.
3645 o Minor bugfixes (compilation):
3646 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
3647 29169; bugfix on 0.4.0.1-alpha.
3648 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
3649 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3651 o Minor bugfixes (documentation):
3652 - Describe the contents of the v3 onion service client authorization
3653 files correctly: They hold public keys, not private keys. Fixes
3654 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3656 o Minor bugfixes (linux seccomp sandbox):
3657 - Fix startup crash when experimental sandbox support is enabled.
3658 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
3660 o Minor bugfixes (logging):
3661 - Avoid logging that we are relaxing a circuit timeout when that
3662 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
3663 - Log more information at "warning" level when unable to read a
3664 private key; log more information at "info" level when unable to
3665 read a public key. We had warnings here before, but they were lost
3666 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
3668 o Minor bugfixes (misc):
3669 - The amount of total available physical memory is now determined
3670 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
3671 when it is defined and a 64-bit variant is not available. Fixes
3672 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
3674 o Minor bugfixes (onion services):
3675 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
3676 than one private key for a hidden service. Fixes bug 29040; bugfix
3678 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
3679 "debug" level. Tor used to log it as a warning, which caused very
3680 long log lines to appear for some users. Fixes bug 29135; bugfix
3682 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3683 as a warning. Instead, log it as a protocol warning, because there
3684 is nothing that relay operators can do to fix it. Fixes bug 29029;
3685 bugfix on 0.2.5.7-rc.
3687 o Minor bugfixes (scheduler):
3688 - When re-adding channels to the pending list, check the correct
3689 channel's sched_heap_idx. This issue has had no effect in mainline
3690 Tor, but could have led to bugs down the road in improved versions
3691 of our circuit scheduling code. Fixes bug 29508; bugfix
3694 o Minor bugfixes (tests):
3695 - Fix intermittent failures on an adaptive padding test. Fixes one
3696 case of bug 29122; bugfix on 0.4.0.1-alpha.
3697 - Disable an unstable circuit-padding test that was failing
3698 intermittently because of an ill-defined small histogram. Such
3699 histograms will be allowed again after 29298 is implemented. Fixes
3700 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
3701 - Detect and suppress "bug" warnings from the util/time test on
3702 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
3703 - Do not log an error-level message if we fail to find an IPv6
3704 network interface from the unit tests. Fixes bug 29160; bugfix
3708 - In the manpage entry describing MapAddress torrc setting, use
3709 example IP addresses from ranges specified for use in documentation
3710 by RFC 5737. Resolves issue 28623.
3713 - Remove the old check-tor script. Resolves issue 29072.
3716 Changes in version 0.4.0.1-alpha - 2019-01-18
3717 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
3718 introduces improved features for power and bandwidth conservation,
3719 more accurate reporting of bootstrap progress for user interfaces, and
3720 an experimental backend for an exciting new adaptive padding feature.
3721 There is also the usual assortment of bugfixes and minor features, all
3724 o Major features (battery management, client, dormant mode):
3725 - When Tor is running as a client, and it is unused for a long time,
3726 it can now enter a "dormant" state. When Tor is dormant, it avoids
3727 network and CPU activity until it is reawoken either by a user
3728 request or by a controller command. For more information, see the
3729 configuration options starting with "Dormant". Implements tickets
3731 - The client's memory of whether it is "dormant", and how long it
3732 has spent idle, persists across invocations. Implements
3734 - There is a DormantOnFirstStartup option that integrators can use
3735 if they expect that in many cases, Tor will be installed but
3738 o Major features (bootstrap reporting):
3739 - When reporting bootstrap progress, report the first connection
3740 uniformly, regardless of whether it's a connection for building
3741 application circuits. This allows finer-grained reporting of early
3742 progress than previously possible, with the improvements of ticket
3743 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
3744 - When reporting bootstrap progress, treat connecting to a proxy or
3745 pluggable transport as separate from having successfully used that
3746 proxy or pluggable transport to connect to a relay. Closes tickets
3749 o Major features (circuit padding):
3750 - Implement preliminary support for the circuit padding portion of
3751 Proposal 254. The implementation supports Adaptive Padding (aka
3752 WTF-PAD) state machines for use between experimental clients and
3753 relays. Support is also provided for APE-style state machines that
3754 use probability distributions instead of histograms to specify
3755 inter-packet delay. At the moment, Tor does not provide any
3756 padding state machines that are used in normal operation: for now,
3757 this feature exists solely for experimentation. Closes
3760 o Major features (refactoring):
3761 - Tor now uses an explicit list of its own subsystems when
3762 initializing and shutting down. Previously, these systems were
3763 managed implicitly in various places throughout the codebase.
3764 (There may still be some subsystems using the old system.) Closes
3767 o Minor features (bootstrap reporting):
3768 - When reporting bootstrap progress, stop distinguishing between
3769 situations where only internal paths are available and situations
3770 where external paths are available. Previously, Tor would often
3771 erroneously report that it had only internal paths. Closes
3774 o Minor features (continuous integration):
3775 - Log Python version during each Travis CI job. Resolves
3778 o Minor features (controller):
3779 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
3780 Implements ticket 28843.
3782 o Minor features (developer tooling):
3783 - Provide a git hook script to prevent "fixup!" and "squash!"
3784 commits from ending up in the master branch, as scripts/main/pre-
3785 push.git-hook. Closes ticket 27993.
3787 o Minor features (directory authority):
3788 - Directory authorities support a new consensus algorithm, under
3789 which the family lines in microdescriptors are encoded in a
3790 canonical form. This change makes family lines more compressible
3791 in transit, and on the client. Closes ticket 28266; implements
3794 o Minor features (directory authority, relay):
3795 - Authorities now vote on a "StaleDesc" flag to indicate that a
3796 relay's descriptor is so old that the relay should upload again
3797 soon. Relays treat this flag as a signal to upload a new
3798 descriptor. This flag will eventually let us remove the
3799 'published' date from routerstatus entries, and make our consensus
3800 diffs much smaller. Closes ticket 26770; implements proposal 293.
3802 o Minor features (fallback directory mirrors):
3803 - Update the fallback whitelist based on operator opt-ins and opt-
3804 outs. Closes ticket 24805, patch by Phoul.
3806 o Minor features (FreeBSD):
3807 - On FreeBSD-based systems, warn relay operators if the
3808 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
3809 Closes ticket 28518.
3811 o Minor features (HTTP standards compliance):
3812 - Stop sending the header "Content-type: application/octet-stream"
3813 along with transparently compressed documents: this confused
3814 browsers. Closes ticket 28100.
3816 o Minor features (IPv6):
3817 - We add an option ClientAutoIPv6ORPort, to make clients randomly
3818 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
3819 every time a node is loaded from a new consensus or bridge config.
3820 We expect that this option will enable clients to bootstrap more
3821 quickly without having to determine whether they support IPv4,
3822 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
3823 - When using addrs_in_same_network_family(), avoid choosing circuit
3824 paths that pass through the same IPv6 subnet more than once.
3825 Previously, we only checked IPv4 subnets. Closes ticket 24393.
3826 Patch by Neel Chauhan.
3828 o Minor features (log messages):
3829 - Improve log message in v3 onion services that could print out
3830 negative revision counters. Closes ticket 27707. Patch
3833 o Minor features (memory usage):
3834 - Save memory by storing microdescriptor family lists with a more
3835 compact representation. Closes ticket 27359.
3836 - Tor clients now use mmap() to read consensus files from disk, so
3837 that they no longer need keep the full text of a consensus in
3838 memory when parsing it or applying a diff. Closes ticket 27244.
3840 o Minor features (parsing):
3841 - Directory authorities now validate that router descriptors and
3842 ExtraInfo documents are in a valid subset of UTF-8, and reject
3843 them if they are not. Closes ticket 27367.
3845 o Minor features (performance):
3846 - Cache the results of summarize_protocol_flags(), so that we don't
3847 have to parse the same protocol-versions string over and over.
3848 This should save us a huge number of malloc calls on startup, and
3849 may reduce memory fragmentation with some allocators. Closes
3851 - Remove a needless memset() call from get_token_arguments, thereby
3852 speeding up the tokenization of directory objects by about 20%.
3853 Closes ticket 28852.
3854 - Replace parse_short_policy() with a faster implementation, to
3855 improve microdescriptor parsing time. Closes ticket 28853.
3856 - Speed up directory parsing a little by avoiding use of the non-
3857 inlined strcmp_len() function. Closes ticket 28856.
3858 - Speed up microdescriptor parsing by about 30%, to help improve
3859 startup time. Closes ticket 28839.
3861 o Minor features (pluggable transports):
3862 - Add support for emitting STATUS updates to Tor's control port from
3863 a pluggable transport process. Closes ticket 28846.
3864 - Add support for logging to Tor's logging subsystem from a
3865 pluggable transport process. Closes ticket 28180.
3867 o Minor features (process management):
3868 - Add a new process API for handling child processes. This new API
3869 allows Tor to have bi-directional communication with child
3870 processes on both Unix and Windows. Closes ticket 28179.
3871 - Use the subsystem manager to initialize and shut down the process
3872 module. Closes ticket 28847.
3874 o Minor features (relay):
3875 - When listing relay families, list them in canonical form including
3876 the relay's own identity, and try to give a more useful set of
3877 warnings. Part of ticket 28266 and proposal 298.
3879 o Minor features (required protocols):
3880 - Before exiting because of a missing required protocol, Tor will
3881 now check the publication time of the consensus, and not exit
3882 unless the consensus is newer than the Tor program's own release
3883 date. Previously, Tor would not check the consensus publication
3884 time, and so might exit because of a missing protocol that might
3885 no longer be required in a current consensus. Implements proposal
3886 297; closes ticket 27735.
3888 o Minor features (testing):
3889 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
3890 networks. Closes ticket 28840. Patch by Rob Jansen.
3892 o Minor bugfixes (client, clock skew):
3893 - Bootstrap successfully even when Tor's clock is behind the clocks
3894 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
3895 - Select guards even if the consensus has expired, as long as the
3896 consensus is still reasonably live. Fixes bug 24661; bugfix
3899 o Minor bugfixes (compilation):
3900 - Compile correctly on OpenBSD; previously, we were missing some
3901 headers required in order to detect it properly. Fixes bug 28938;
3902 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3904 o Minor bugfixes (directory clients):
3905 - Mark outdated dirservers when Tor only has a reasonably live
3906 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
3908 o Minor bugfixes (directory mirrors):
3909 - Even when a directory mirror's clock is behind the clocks on the
3910 authorities, we now allow the mirror to serve "future"
3911 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
3913 o Minor bugfixes (DNS):
3914 - Gracefully handle an empty or absent resolve.conf file by falling
3915 back to using "localhost" as a DNS server (and hoping it works).
3916 Previously, we would just stop running as an exit. Fixes bug
3917 21900; bugfix on 0.2.1.10-alpha.
3919 o Minor bugfixes (guards):
3920 - In count_acceptable_nodes(), the minimum number is now one bridge
3921 or guard node, and two non-guard nodes for a circuit. Previously,
3922 we had added up the sum of all nodes with a descriptor, but that
3923 could cause us to build failing circuits when we had either too
3924 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
3925 0.2.3.1-alpha. Patch by Neel Chauhan.
3927 o Minor bugfixes (IPv6):
3928 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
3929 IPv6 socket was bound using an address family of AF_INET instead
3930 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
3933 o Minor bugfixes (logging):
3934 - Rework rep_hist_log_link_protocol_counts() to iterate through all
3935 link protocol versions when logging incoming/outgoing connection
3936 counts. Tor no longer skips version 5, and we won't have to
3937 remember to update this function when new link protocol version is
3938 developed. Fixes bug 28920; bugfix on 0.2.6.10.
3940 o Minor bugfixes (networking):
3941 - Introduce additional checks into tor_addr_parse() to reject
3942 certain incorrect inputs that previously were not detected. Fixes
3943 bug 23082; bugfix on 0.2.0.10-alpha.
3945 o Minor bugfixes (onion service v3, client):
3946 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
3947 connection waiting for a descriptor that we actually have in the
3948 cache. It turns out that this can actually happen, though it is
3949 rare. Now, tor will recover and retry the descriptor. Fixes bug
3950 28669; bugfix on 0.3.2.4-alpha.
3952 o Minor bugfixes (periodic events):
3953 - Refrain from calling routerlist_remove_old_routers() from
3954 check_descriptor_callback(). Instead, create a new hourly periodic
3955 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
3957 o Minor bugfixes (pluggable transports):
3958 - Make sure that data is continously read from standard output and
3959 standard error pipes of a pluggable transport child-process, to
3960 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
3961 bugfix on 0.2.3.6-alpha.
3963 o Minor bugfixes (unit tests):
3964 - Instead of relying on hs_free_all() to clean up all onion service
3965 objects in test_build_descriptors(), we now deallocate them one by
3966 one. This lets Coverity know that we are not leaking memory there
3967 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
3969 o Minor bugfixes (usability):
3970 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
3971 Some users took this phrasing to mean that the mentioned guard was
3972 under their control or responsibility, which it is not. Fixes bug
3973 28895; bugfix on Tor 0.3.0.1-alpha.
3975 o Code simplification and refactoring:
3976 - Reimplement NETINFO cell parsing and generation to rely on
3977 trunnel-generated wire format handling code. Closes ticket 27325.
3978 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
3980 - Rework SOCKS wire format handling to rely on trunnel-generated
3981 parsing/generation code. Resolves ticket 27620.
3982 - Split out bootstrap progress reporting from control.c into a
3983 separate file. Part of ticket 27402.
3984 - The .may_include files that we use to describe our directory-by-
3985 directory dependency structure now describe a noncircular
3986 dependency graph over the directories that they cover. Our
3987 checkIncludes.py tool now enforces this noncircularity. Closes
3991 - Mention that you cannot add a new onion service if Tor is already
3992 running with Sandbox enabled. Closes ticket 28560.
3993 - Improve ControlPort documentation. Mention that it accepts
3994 address:port pairs, and can be used multiple times. Closes
3996 - Document the exact output of "tor --version". Closes ticket 28889.
3999 - Stop responding to the 'GETINFO status/version/num-concurring' and
4000 'GETINFO status/version/num-versioning' control port commands, as
4001 those were deprecated back in 0.2.0.30. Also stop listing them in
4002 output of 'GETINFO info/names'. Resolves ticket 28757.
4003 - The scripts used to generate and maintain the list of fallback
4004 directories have been extracted into a new "fallback-scripts"
4005 repository. Closes ticket 27914.
4008 - Run shellcheck for scripts in the in scripts/ directory. Closes
4010 - Add unit tests for tokenize_string() and get_next_token()
4011 functions. Resolves ticket 27625.
4013 o Code simplification and refactoring (onion service v3):
4014 - Consolidate the authorized client descriptor cookie computation
4015 code from client and service into one function. Closes
4018 o Code simplification and refactoring (shell scripts):
4019 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
4021 - Fix issues that shellcheck found in chutney-git-bisect.sh.
4022 Resolves ticket 28006.
4023 - Fix issues that shellcheck found in updateRustDependencies.sh.
4024 Resolves ticket 28012.
4025 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
4026 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
4027 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
4028 - Fix shellcheck warnings in scripts/test/coverage. Resolves
4032 Changes in version 0.3.3.11 - 2019-01-07
4033 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
4034 numerous fixes, including an important fix for anyone using OpenSSL
4035 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
4036 to this version, or to a later series.
4038 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
4039 We anticipate that this will be the last release of Tor 0.3.3, unless
4040 some major bug is before then. Some time between now and then, users
4041 should switch to either the Tor 0.3.4 series (supported until at least
4042 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
4043 support until at least 1 Feb 2022.
4045 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4046 - Fix our usage of named groups when running as a TLS 1.3 client in
4047 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4048 running as a relay, which caused clients to fail to negotiate TLS
4049 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4052 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4053 - Fix a use-after-free error that could be caused by passing Tor an
4054 impossible set of options that would fail during options_act().
4055 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4057 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4058 - Only run one online rust build in Travis, to reduce network
4059 errors. Skip offline rust builds on Travis for Linux gcc, because
4060 they're redundant. Implements ticket 27252.
4061 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4062 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4063 Linux with default settings, because all the non-default builds
4064 use gcc on Linux. Implements ticket 27252.
4066 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4067 - Use the Travis Homebrew addon to install packages on macOS during
4068 Travis CI. The package list is the same, but the Homebrew addon
4069 does not do a `brew update` by default. Implements ticket 27738.
4071 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4072 - Replace the 150 fallbacks originally introduced in Tor
4073 0.3.3.1-alpha in January 2018 (of which ~115 were still
4074 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4075 removed) generated in December 2018. Closes ticket 24803.
4077 o Minor features (geoip):
4078 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4079 Country database. Closes ticket 29012.
4081 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4082 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4083 key export function from handling long labels. When this bug is
4084 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4085 version of OpenSSL without this bug when it becomes available.
4086 Closes ticket 28973.
4088 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4089 - Update relay descriptor on bandwidth changes only when the uptime
4090 is smaller than 24h, in order to reduce the efficiency of guard
4091 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4093 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
4094 - Avoid undefined behavior in an end-of-string check when parsing
4095 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4098 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4099 - Rewrite our assertion macros so that they no longer suppress the
4100 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4102 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4103 - Initialize a variable unconditionally in aes_new_cipher(), since
4104 some compilers cannot tell that we always initialize it before
4105 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4107 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
4108 - Log additional info when we get a relay that shares an ed25519 ID
4109 with a different relay, instead making a BUG() warning. Fixes bug
4110 27800; bugfix on 0.3.2.1-alpha.
4112 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4113 - When a user requests a group-readable DataDirectory, give it to
4114 them. Previously, when the DataDirectory and the CacheDirectory
4115 were the same, the default setting (0) for
4116 CacheDirectoryGroupReadable would override the setting for
4117 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4120 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4121 - When the onion service directory can't be created or has the wrong
4122 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4125 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4126 - Close all SOCKS request (for the same .onion) if the newly fetched
4127 descriptor is unusable. Before that, we would close only the first
4128 one leaving the other hanging and let to time out by themselves.
4129 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4131 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4132 - Don't warn so loudly when Tor is unable to decode an onion
4133 descriptor. This can now happen as a normal use case if a client
4134 gets a descriptor with client authorization but the client is not
4135 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4137 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4138 - When deleting an ephemeral onion service (DEL_ONION), do not close
4139 any rendezvous circuits in order to let the existing client
4140 connections finish by themselves or closed by the application. The
4141 HS v2 is doing that already so now we have the same behavior for
4142 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4144 o Minor bugfixes (HTTP tunnel):
4145 - Fix a bug warning when closing an HTTP tunnel connection due to
4146 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
4149 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4150 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4151 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4153 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4154 - Ensure circuitmux queues are empty before scheduling or sending
4155 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4157 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4158 - Reject protocol names containing bytes other than alphanumeric
4159 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4162 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4163 - Compute protover votes correctly in the rust version of the
4164 protover code. Previously, the protover rewrite in 24031 allowed
4165 repeated votes from the same voter for the same protocol version
4166 to be counted multiple times in protover_compute_vote(). Fixes bug
4167 27649; bugfix on 0.3.3.5-rc.
4168 - Reject protover names that contain invalid characters. Fixes bug
4169 27687; bugfix on 0.3.3.1-alpha.
4171 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4172 - protover_all_supported() would attempt to allocate up to 16GB on
4173 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4174 bugfix on 0.3.3.5-rc.
4176 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
4177 - Fix a potential null dereference in protover_all_supported(). Add
4178 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4179 - Return a string that can be safely freed by C code, not one
4180 created by the rust allocator, in protover_all_supported(). Fixes
4181 bug 27740; bugfix on 0.3.3.1-alpha.
4182 - Fix an API mismatch in the rust implementation of
4183 protover_compute_vote(). This bug could have caused crashes on any
4184 directory authorities running Tor with Rust (which we do not yet
4185 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4187 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4188 - If a unit test running in a subprocess exits abnormally or with a
4189 nonzero status code, treat the test as having failed, even if the
4190 test reported success. Without this fix, memory leaks don't cause
4191 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4192 bugfix on 0.2.2.4-alpha.
4194 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
4195 - Treat backtrace test failures as expected on BSD-derived systems
4196 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4197 (FreeBSD failures have been treated as expected since 18204 in
4198 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4200 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4201 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4202 bugfix on 0.3.0.1-alpha.
4205 Changes in version 0.3.4.10 - 2019-01-07
4206 Tor 0.3.4.9 is the second stable release in its series; it backports
4207 numerous fixes, including an important fix for relays, and for anyone
4208 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
4211 As a reminder, the Tor 0.3.4 series will be supported until 10 June
4212 2019. Some time between now and then, users should switch to the Tor
4213 0.3.5 series, which will receive long-term support until at least 1
4216 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4217 - Fix our usage of named groups when running as a TLS 1.3 client in
4218 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4219 running as a relay, which caused clients to fail to negotiate TLS
4220 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4223 o Major bugfixes (relay, directory, backport from 0.3.5.7):
4224 - Always reactivate linked connections in the main loop so long as
4225 any linked connection has been active. Previously, connections
4226 serving directory information wouldn't get reactivated after the
4227 first chunk of data was sent (usually 32KB), which would prevent
4228 clients from bootstrapping. Fixes bug 28912; bugfix on
4229 0.3.4.1-alpha. Patch by "cypherpunks3".
4231 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
4232 - Always show the configure and test logs, and upload them as build
4233 artifacts, when building for Windows using Appveyor CI.
4236 o Minor features (controller, backport from 0.3.5.1-alpha):
4237 - For purposes of CIRC_BW-based dropped cell detection, track half-
4238 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4239 bias check cells to arrive without counting it as dropped until
4240 either the END arrives, or the windows are empty. Closes
4243 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4244 - Replace the 150 fallbacks originally introduced in Tor
4245 0.3.3.1-alpha in January 2018 (of which ~115 were still
4246 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4247 removed) generated in December 2018. Closes ticket 24803.
4249 o Minor features (geoip):
4250 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4251 Country database. Closes ticket 28395.
4253 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4254 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4255 key export function from handling long labels. When this bug is
4256 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4257 version of OpenSSL without this bug when it becomes available.
4258 Closes ticket 28973.
4260 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4261 - Initialize a variable unconditionally in aes_new_cipher(), since
4262 some compilers cannot tell that we always initialize it before
4263 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4265 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
4266 - Avoid a logging a BUG() stacktrace when closing connection held
4267 open because the write side is rate limited but not the read side.
4268 Now, the connection read side is simply shut down until Tor is
4269 able to flush the connection and close it. Fixes bug 27750; bugfix
4272 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
4273 - Manually configure the zstd compiler options, when building using
4274 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4275 not come with a pkg-config file. Fixes bug 28454; bugfix
4277 - Stop using an external OpenSSL install, and stop installing MSYS2
4278 packages, when building using mingw on Appveyor Windows CI. Fixes
4279 bug 28399; bugfix on 0.3.4.1-alpha.
4281 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
4282 - Explicitly specify the path to the OpenSSL library and do not
4283 download OpenSSL from Pacman, but instead use the library that is
4284 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4286 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4287 - When a user requests a group-readable DataDirectory, give it to
4288 them. Previously, when the DataDirectory and the CacheDirectory
4289 were the same, the default setting (0) for
4290 CacheDirectoryGroupReadable would override the setting for
4291 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4294 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4295 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4296 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4298 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4299 - Don't warn so loudly when Tor is unable to decode an onion
4300 descriptor. This can now happen as a normal use case if a client
4301 gets a descriptor with client authorization but the client is not
4302 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4304 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4305 - When deleting an ephemeral onion service (DEL_ONION), do not close
4306 any rendezvous circuits in order to let the existing client
4307 connections finish by themselves or closed by the application. The
4308 HS v2 is doing that already so now we have the same behavior for
4309 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4311 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4312 - Update relay descriptor on bandwidth changes only when the uptime
4313 is smaller than 24h, in order to reduce the efficiency of guard
4314 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4316 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4317 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4318 bugfix on 0.3.0.1-alpha.
4321 Changes in version 0.3.5.7 - 2019-01-07
4322 Tor 0.3.5.7 is the first stable release in its series; it includes
4323 compilation and portability fixes, and a fix for a severe problem
4324 affecting directory caches.
4326 The Tor 0.3.5 series includes several new features and performance
4327 improvements, including client authorization for v3 onion services,
4328 cleanups to bootstrap reporting, support for improved bandwidth-
4329 measurement tools, experimental support for NSS in place of OpenSSL,
4330 and much more. It also begins a full reorganization of Tor's code
4331 layout, for improved modularity and maintainability in the future.
4332 Finally, there is the usual set of performance improvements and
4333 bugfixes that we try to do in every release series.
4335 There are a couple of changes in the 0.3.5 that may affect
4336 compatibility. First, the default version for newly created onion
4337 services is now v3. Use the HiddenServiceVersion option if you want to
4338 override this. Second, some log messages related to bootstrapping have
4339 changed; if you use stem, you may need to update to the latest version
4340 so it will recognize them.
4342 We have designated 0.3.5 as a "long-term support" (LTS) series: we
4343 will continue to patch major bugs in typical configurations of 0.3.5
4344 until at least 1 Feb 2022. (We do not plan to provide long-term
4345 support for embedding, Rust support, NSS support, running a directory
4346 authority, or unsupported platforms. For these, you will need to stick
4347 with the latest stable release.)
4349 Below are the changes since 0.3.5.6-rc. For a complete list of changes
4350 since 0.3.4.9, see the ReleaseNotes file.
4352 o Major bugfixes (relay, directory):
4353 - Always reactivate linked connections in the main loop so long as
4354 any linked connection has been active. Previously, connections
4355 serving directory information wouldn't get reactivated after the
4356 first chunk of data was sent (usually 32KB), which would prevent
4357 clients from bootstrapping. Fixes bug 28912; bugfix on
4358 0.3.4.1-alpha. Patch by "cypherpunks3".
4360 o Minor features (compilation):
4361 - When possible, place our warning flags in a separate file, to
4362 avoid flooding verbose build logs. Closes ticket 28924.
4364 o Minor features (geoip):
4365 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4366 Country database. Closes ticket 29012.
4368 o Minor features (OpenSSL bug workaround):
4369 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4370 key export function from handling long labels. When this bug is
4371 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4372 version of OpenSSL without this bug when it becomes available.
4373 Closes ticket 28973.
4375 o Minor features (performance):
4376 - Remove about 96% of the work from the function that we run at
4377 startup to test our curve25519_basepoint implementation. Since
4378 this function has yet to find an actual failure, we now only run
4379 it for 8 iterations instead of 200. Based on our profile
4380 information, this change should save around 8% of our startup time
4381 on typical desktops, and may have a similar effect on other
4382 platforms. Closes ticket 28838.
4383 - Stop re-validating our hardcoded Diffie-Hellman parameters on
4384 every startup. Doing this wasted time and cycles, especially on
4385 low-powered devices. Closes ticket 28851.
4387 o Minor bugfixes (compilation):
4388 - Fix compilation for Android by adding a missing header to
4389 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
4391 o Minor bugfixes (correctness):
4392 - Fix an unreached code path where we checked the value of
4393 "hostname" inside send_resolved_hostname_cell(). Previously, we
4394 used it before checking it; now we check it first. Fixes bug
4395 28879; bugfix on 0.1.2.7-alpha.
4397 o Minor bugfixes (testing):
4398 - Make sure that test_rebind.py actually obeys its timeout, even
4399 when it receives a large number of log messages. Fixes bug 28883;
4400 bugfix on 0.3.5.4-alpha.
4401 - Stop running stem's unit tests as part of "make test-stem", but
4402 continue to run stem's unit and online tests during "make test-
4403 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
4405 o Minor bugfixes (windows services):
4406 - Make Tor start correctly as an NT service again: previously it was
4407 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
4409 o Code simplification and refactoring:
4410 - When parsing a port configuration, make it more obvious to static
4411 analyzer tools that we always initialize the address. Closes
4415 Changes in version 0.3.5.6-rc - 2018-12-18
4416 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
4417 It is the first release candidate in the 0.3.5.x series; if no further
4418 huge bugs are found, our next release may be the stable 0.3.5.x.
4420 o Minor features (continuous integration, Windows):
4421 - Always show the configure and test logs, and upload them as build
4422 artifacts, when building for Windows using Appveyor CI.
4425 o Minor features (fallback directory list):
4426 - Replace the 150 fallbacks originally introduced in Tor
4427 0.3.3.1-alpha in January 2018 (of which ~115 were still
4428 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4429 removed) generated in December 2018. Closes ticket 24803.
4431 o Minor features (geoip):
4432 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
4433 Country database. Closes ticket 28744.
4435 o Minor bugfixes (compilation):
4436 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
4437 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
4439 o Minor bugfixes (continuous integration, Windows):
4440 - Explicitly specify the path to the OpenSSL library and do not
4441 download OpenSSL from Pacman, but instead use the library that is
4442 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4444 o Minor bugfixes (onion service v3):
4445 - When deleting an ephemeral onion service (DEL_ONION), do not close
4446 any rendezvous circuits in order to let the existing client
4447 connections finish by themselves or closed by the application. The
4448 HS v2 is doing that already so now we have the same behavior for
4449 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4451 o Minor bugfixes (restart-in-process, boostrap):
4452 - Add missing resets of bootstrap tracking state when shutting down
4453 (regression caused by ticket 27169). Fixes bug 28524; bugfix
4456 o Minor bugfixes (testing):
4457 - Use a separate DataDirectory for the test_rebind script.
4458 Previously, this script would run using the default DataDirectory,
4459 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
4460 Patch from Taylor R Campbell.
4461 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4462 bugfix on 0.3.0.1-alpha.
4464 o Minor bugfixes (Windows):
4465 - Correctly identify Windows 8.1, Windows 10, and Windows Server
4466 2008 and later from their NT versions. Fixes bug 28096; bugfix on
4467 0.2.2.34; reported by Keifer Bly.
4468 - On recent Windows versions, the GetVersionEx() function may report
4469 an earlier Windows version than the running OS. To avoid user
4470 confusion, add "[or later]" to Tor's version string on affected
4471 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
4473 - Remove Windows versions that were never supported by the
4474 GetVersionEx() function. Stop duplicating the latest Windows
4475 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
4476 reported by Keifer Bly.
4479 - Increase logging and tag all log entries with timestamps in
4480 test_rebind.py. Provides diagnostics for issue 28229.
4482 o Code simplification and refactoring (shared random, dirauth):
4483 - Change many tor_assert() to use BUG() instead. The idea is to not
4484 crash a dirauth but rather scream loudly with a stacktrace and let
4485 it continue run. The shared random subsystem is very resilient and
4486 if anything wrong happens with it, at worst a non coherent value
4487 will be put in the vote and discarded by the other authorities.
4488 Closes ticket 19566.
4490 o Documentation (onion services):
4491 - Document in the man page that changing ClientOnionAuthDir value or
4492 adding a new file in the directory will not work at runtime upon
4493 sending a HUP if Sandbox 1. Closes ticket 28128.
4494 - Note in the man page that the only real way to fully revoke an
4495 onion service v3 client authorization is by restarting the tor
4496 process. Closes ticket 28275.
4499 Changes in version 0.3.5.5-alpha - 2018-11-16
4500 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
4501 including several that we hope to backport to older release series in
4504 o Major bugfixes (OpenSSL, portability):
4505 - Fix our usage of named groups when running as a TLS 1.3 client in
4506 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4507 running as a relay, which caused clients to fail to negotiate TLS
4508 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4511 o Minor features (geoip):
4512 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4513 Country database. Closes ticket 28395.
4515 o Minor bugfixes (compilation):
4516 - Initialize a variable unconditionally in aes_new_cipher(), since
4517 some compilers cannot tell that we always initialize it before
4518 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4520 o Minor bugfixes (connection, relay):
4521 - Avoid a logging a BUG() stacktrace when closing connection held
4522 open because the write side is rate limited but not the read side.
4523 Now, the connection read side is simply shut down until Tor is
4524 able to flush the connection and close it. Fixes bug 27750; bugfix
4527 o Minor bugfixes (continuous integration, Windows):
4528 - Manually configure the zstd compiler options, when building using
4529 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4530 not come with a pkg-config file. Fixes bug 28454; bugfix
4532 - Stop using an external OpenSSL install, and stop installing MSYS2
4533 packages, when building using mingw on Appveyor Windows CI. Fixes
4534 bug 28399; bugfix on 0.3.4.1-alpha.
4536 o Minor bugfixes (documentation):
4537 - Make Doxygen work again after the code movement in the 0.3.5
4538 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
4540 o Minor bugfixes (Linux seccomp2 sandbox):
4541 - Permit the "shutdown()" system call, which is apparently used by
4542 OpenSSL under some circumstances. Fixes bug 28183; bugfix
4545 o Minor bugfixes (logging):
4546 - Stop talking about the Named flag in log messages. Clients have
4547 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
4550 o Minor bugfixes (memory leaks):
4551 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4552 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4554 o Minor bugfixes (onion services):
4555 - On an intro point for a version 3 onion service, stop closing
4556 introduction circuits on an NACK. This lets the client decide
4557 whether to reuse the circuit or discard it. Previously, we closed
4558 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
4559 0.3.2.1-alpha. Patch by Neel Chaunan.
4560 - When replacing a descriptor in the client cache, make sure to
4561 close all client introduction circuits for the old descriptor, so
4562 we don't end up with unusable leftover circuits. Fixes bug 27471;
4563 bugfix on 0.3.2.1-alpha.
4566 Changes in version 0.3.5.4-alpha - 2018-11-08
4567 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
4568 improves our continuous integration support. It continues our attempts
4569 to stabilize this alpha branch and build it into a foundation for an
4570 acceptable long-term-support release.
4572 o Major bugfixes (compilation, rust):
4573 - Rust tests can now build and run successfully with the
4574 --enable-fragile-hardening option enabled. Doing this currently
4575 requires the rust beta channel; it will be possible with stable
4576 rust once Rust version 1.31 is released. Patch from Alex Crichton.
4577 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
4579 o Major bugfixes (embedding, main loop):
4580 - When DisableNetwork becomes set, actually disable periodic events
4581 that are already enabled. (Previously, we would refrain from
4582 enabling new ones, but we would leave the old ones turned on.)
4583 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
4585 o Minor features (continuous integration):
4586 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
4588 - Add new CI job to Travis configuration to run stem-based
4589 integration tests. Closes ticket 27913.
4591 o Minor features (Windows, continuous integration):
4592 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
4593 Appveyor's CI. Closes ticket 28318.
4595 o Minor bugfixes (C correctness, also in 0.3.4.9):
4596 - Avoid undefined behavior in an end-of-string check when parsing
4597 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4600 o Minor bugfixes (compilation):
4601 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
4602 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4604 o Minor bugfixes (compilation, OpenSolaris):
4605 - Fix compilation on OpenSolaris and its descendants by adding a
4606 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
4609 o Minor bugfixes (configuration):
4610 - Refuse to start with relative file paths and RunAsDaemon set
4611 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
4614 o Minor bugfixes (directory authority, also in 0.3.4.9):
4615 - Log additional info when we get a relay that shares an ed25519 ID
4616 with a different relay, instead of a BUG() warning with a
4617 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
4619 o Minor bugfixes (onion service v3):
4620 - Build the service descriptor's signing key certificate before
4621 uploading, so we always have a fresh one: leaving no chances for
4622 it to expire service side. Fixes bug 27838; bugfix
4625 o Minor bugfixes (onion service v3, client authorization):
4626 - Fix an assert() when adding a client authorization for the first
4627 time and then sending a HUP signal to the service. Before that,
4628 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
4630 o Minor bugfixes (onion services):
4631 - Unless we have explicitly set HiddenServiceVersion, detect the
4632 onion service version and then look for invalid options.
4633 Previously, we did the reverse, but that broke existing configs
4634 which were pointed to a v2 service and had options like
4635 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
4636 0.3.5.1-alpha. Patch by Neel Chauhan.
4638 o Minor bugfixes (portability):
4639 - Make the OPE code (which is used for v3 onion services) run
4640 correctly on big-endian platforms. Fixes bug 28115; bugfix
4643 o Minor bugfixes (protover, rust):
4644 - Reject extra commas in version strings. Fixes bug 27197; bugfix
4647 o Minor bugfixes (relay shutdown, systemd):
4648 - Notify systemd of ShutdownWaitLength so it can be set to longer
4649 than systemd's TimeoutStopSec. In Tor's systemd service file, set
4650 TimeoutSec to 60 seconds to allow Tor some time to shut down.
4651 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
4653 o Minor bugfixes (rust, also in 0.3.4.9):
4654 - Fix a potential null dereference in protover_all_supported(). Add
4655 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4656 - Return a string that can be safely freed by C code, not one
4657 created by the rust allocator, in protover_all_supported(). Fixes
4658 bug 27740; bugfix on 0.3.3.1-alpha.
4660 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
4661 - Fix an API mismatch in the rust implementation of
4662 protover_compute_vote(). This bug could have caused crashes on any
4663 directory authorities running Tor with Rust (which we do not yet
4664 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4666 o Minor bugfixes (testing):
4667 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
4668 27968; bugfix on 0.3.5.1-alpha.
4670 o Minor bugfixes (testing, also in 0.3.4.9):
4671 - Treat backtrace test failures as expected on BSD-derived systems
4672 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4673 (FreeBSD failures have been treated as expected since 18204 in
4674 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4676 o Documentation (onion service manpage):
4677 - Improve HSv3 client authorization by making some options more
4678 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
4681 Changes in version 0.3.4.9 - 2018-11-02
4682 Tor 0.3.4.9 is the second stable release in its series; it backports
4683 numerous fixes, including a fix for a bandwidth management bug that
4684 was causing memory exhaustion on relays. Anyone running an earlier
4685 version of Tor 0.3.4.9 should upgrade.
4687 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
4688 - Fix compilation on ARM (and other less-used CPUs) when compiling
4689 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
4691 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
4692 - Make sure Tor bootstraps and works properly if only the
4693 ControlPort is set. Prior to this fix, Tor would only bootstrap
4694 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
4695 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
4697 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
4698 - When our write bandwidth limit is exhausted, stop writing on the
4699 connection. Previously, we had a typo in the code that would make
4700 us stop reading instead, leading to relay connections being stuck
4701 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
4704 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4705 - Fix a use-after-free error that could be caused by passing Tor an
4706 impossible set of options that would fail during options_act().
4707 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4709 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4710 - Don't do a distcheck with --disable-module-dirauth in Travis.
4711 Implements ticket 27252.
4712 - Only run one online rust build in Travis, to reduce network
4713 errors. Skip offline rust builds on Travis for Linux gcc, because
4714 they're redundant. Implements ticket 27252.
4715 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4716 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4717 Linux with default settings, because all the non-default builds
4718 use gcc on Linux. Implements ticket 27252.
4720 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4721 - Use the Travis Homebrew addon to install packages on macOS during
4722 Travis CI. The package list is the same, but the Homebrew addon
4723 does not do a `brew update` by default. Implements ticket 27738.
4725 o Minor features (geoip):
4726 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
4727 Country database. Closes ticket 27991.
4729 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
4730 - Fix an integer overflow bug in our optimized 32-bit millisecond-
4731 difference algorithm for 32-bit Apple platforms. Previously, it
4732 would overflow when calculating the difference between two times
4733 more than 47 days apart. Fixes part of bug 27139; bugfix
4735 - Improve the precision of our 32-bit millisecond difference
4736 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
4737 bugfix on 0.3.4.1-alpha.
4738 - Relax the tolerance on the mainloop/update_time_jumps test when
4739 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
4742 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
4743 - Avoid undefined behavior in an end-of-string check when parsing
4744 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4747 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
4748 - Only install the necessary mingw packages during our appveyor
4749 builds. This change makes the build a little faster, and prevents
4750 a conflict with a preinstalled mingw openssl that appveyor now
4751 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
4753 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4754 - Rewrite our assertion macros so that they no longer suppress the
4755 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4757 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
4758 - Stop reinstalling identical packages in our Windows CI. Fixes bug
4759 27464; bugfix on 0.3.4.1-alpha.
4761 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
4762 - Log additional info when we get a relay that shares an ed25519 ID
4763 with a different relay, instead making a BUG() warning. Fixes bug
4764 27800; bugfix on 0.3.2.1-alpha.
4766 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
4767 - Avoid a double-close when shutting down a stalled directory
4768 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
4770 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
4771 - Fix a bug warning when closing an HTTP tunnel connection due to an
4772 HTTP request we couldn't handle. Fixes bug 26470; bugfix
4775 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4776 - Ensure circuitmux queues are empty before scheduling or sending
4777 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4779 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4780 - When the onion service directory can't be created or has the wrong
4781 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4784 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4785 - Close all SOCKS request (for the same .onion) if the newly fetched
4786 descriptor is unusable. Before that, we would close only the first
4787 one leaving the other hanging and let to time out by themselves.
4788 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4790 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4791 - When selecting a v3 rendezvous point, don't only look at the
4792 protover, but also check whether the curve25519 onion key is
4793 present. This way we avoid picking a relay that supports the v3
4794 rendezvous but for which we don't have the microdescriptor. Fixes
4795 bug 27797; bugfix on 0.3.2.1-alpha.
4797 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4798 - Reject protocol names containing bytes other than alphanumeric
4799 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4802 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4803 - Compute protover votes correctly in the rust version of the
4804 protover code. Previously, the protover rewrite in 24031 allowed
4805 repeated votes from the same voter for the same protocol version
4806 to be counted multiple times in protover_compute_vote(). Fixes bug
4807 27649; bugfix on 0.3.3.5-rc.
4808 - Reject protover names that contain invalid characters. Fixes bug
4809 27687; bugfix on 0.3.3.1-alpha.
4811 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4812 - protover_all_supported() would attempt to allocate up to 16GB on
4813 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4814 bugfix on 0.3.3.5-rc.
4816 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
4817 - Fix an API mismatch in the rust implementation of
4818 protover_compute_vote(). This bug could have caused crashes on any
4819 directory authorities running Tor with Rust (which we do not yet
4820 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4822 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
4823 - Fix a potential null dereference in protover_all_supported(). Add
4824 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4825 - Return a string that can be safely freed by C code, not one
4826 created by the rust allocator, in protover_all_supported(). Fixes
4827 bug 27740; bugfix on 0.3.3.1-alpha.
4829 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4830 - If a unit test running in a subprocess exits abnormally or with a
4831 nonzero status code, treat the test as having failed, even if the
4832 test reported success. Without this fix, memory leaks don't cause
4833 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4834 bugfix on 0.2.2.4-alpha.
4836 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
4837 - Make the hs_service tests use the same time source when creating
4838 the introduction point and when testing it. Now tests work better
4839 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
4842 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
4843 - Treat backtrace test failures as expected on BSD-derived systems
4844 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4845 (FreeBSD failures have been treated as expected since 18204 in
4846 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4849 Changes in version 0.3.5.3-alpha - 2018-10-17
4850 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
4851 versions. One important fix for relays addresses a problem with rate-
4852 limiting code from back in 0.3.4.x: If the fix works out, we'll be
4853 backporting it soon. This release is still an alpha, but we hope it's
4854 getting closer and closer to stability.
4856 o Major features (onion services):
4857 - Version 3 onion services can now use the per-service
4858 HiddenServiceExportCircuitID option to differentiate client
4859 circuits. It communicates with the service by using the HAProxy
4860 protocol to assign virtual IP addresses to inbound client
4861 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
4863 o Major bugfixes (compilation):
4864 - Fix compilation on ARM (and other less-used CPUs) when compiling
4865 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
4867 o Major bugfixes (initialization, crash):
4868 - Fix an assertion crash that would stop Tor from starting up if it
4869 tried to activate a periodic event too early. Fixes bug 27861;
4870 bugfix on 0.3.5.1-alpha.
4872 o Major bugfixes (mainloop, bootstrap):
4873 - Make sure Tor bootstraps and works properly if only the
4874 ControlPort is set. Prior to this fix, Tor would only bootstrap
4875 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
4876 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
4878 o Major bugfixes (relay):
4879 - When our write bandwidth limit is exhausted, stop writing on the
4880 connection. Previously, we had a typo in the code that would make
4881 us stop reading instead, leading to relay connections being stuck
4882 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
4885 o Minor features (continuous integration):
4886 - Use the Travis Homebrew addon to install packages on macOS during
4887 Travis CI. The package list is the same, but the Homebrew addon
4888 does not do a `brew update` by default. Implements ticket 27738.
4889 - Report what program produced the mysterious core file that we
4890 occasionally see on Travis CI during make distcheck. Closes
4893 o Minor features (geoip):
4894 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
4895 Country database. Closes ticket 27991.
4897 o Minor bugfixes (code safety):
4898 - Rewrite our assertion macros so that they no longer suppress the
4899 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4902 o Minor bugfixes (compilation):
4903 - Compile the ed25519-donna code with a correct declaration of
4904 crypto_strongest_rand(). Previously, we built it with one type,
4905 but linked it against another in the unit tests, which caused
4906 compilation failures with LTO enabled. This could have caused
4907 other undefined behavior in the tests. Fixes bug 27728; bugfix
4910 o Minor bugfixes (compilation, netbsd):
4911 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
4914 o Minor bugfixes (continuous integration, appveyor):
4915 - Install only the necessary mingw packages during our appveyor
4916 builds. This change makes the build a little faster, and prevents
4917 a conflict with a preinstalled mingw openssl that appveyor now
4918 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
4920 o Minor bugfixes (directory permissions):
4921 - When a user requests a group-readable DataDirectory, give it to
4922 them. Previously, when the DataDirectory and the CacheDirectory
4923 were the same, the default setting (0) for
4924 CacheDirectoryGroupReadable would override the setting for
4925 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4928 o Minor bugfixes (memory leaks):
4929 - Fix a small memory leak when calling Tor with --dump-config. Fixes
4930 bug 27893; bugfix on 0.3.2.1-alpha.
4932 o Minor bugfixes (networking):
4933 - In retry_listeners_ports(), make sure that we're removing a member
4934 of old_conns smartlist at most once. Fixes bug 27808; bugfix
4936 - Refrain from attempting socket rebinding when old and new
4937 listeners are in different address families. Fixes bug 27928;
4938 bugfix on 0.3.5.1-alpha.
4940 o Minor bugfixes (onion service v3):
4941 - Stop dumping a stack trace when trying to connect to an intro
4942 point without having a descriptor for it. Fixes bug 27774; bugfix
4944 - Don't warn so loudly when Tor is unable to decode an onion
4945 descriptor. This can now happen as a normal use case if a client
4946 gets a descriptor with client authorization but the client is not
4947 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4948 - When selecting a v3 rendezvous point, don't only look at the
4949 protover, but also check whether the curve25519 onion key is
4950 present. This way we avoid picking a relay that supports the v3
4951 rendezvous but for which we don't have the microdescriptor. Fixes
4952 bug 27797; bugfix on 0.3.2.1-alpha.
4954 o Minor bugfixes (protover):
4955 - Reject protocol names containing bytes other than alphanumeric
4956 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4959 o Minor bugfixes (testing):
4960 - Make the hs_service tests use the same time source when creating
4961 the introduction point and when testing it. Now tests work better
4962 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
4964 - In test_rebind.py, check if the Python version is in the supported
4965 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
4967 o Code simplification and refactoring:
4968 - Divide more large Tor source files -- especially ones that span
4969 multiple areas of functionality -- into smaller parts, including
4970 onion.c and main.c. Closes ticket 26747.
4971 - Divide the "routerparse.c" module into separate modules for each
4972 group of parsed objects. Closes ticket 27924.
4973 - Move protover_rust.c to the same place protover.c was moved to.
4974 Closes ticket 27814.
4975 - Split directory.c into separate pieces for client, server, and
4976 common functionality. Closes ticket 26744.
4977 - Split the non-statistics-related parts from the rephist.c and
4978 geoip.c modules. Closes ticket 27892.
4979 - Split the router.c file into relay-only and shared components, to
4980 help with future modularization. Closes ticket 27864.
4983 - In the tor-resolve(1) manpage, fix the reference to socks-
4984 extensions.txt by adding a web URL. Resolves ticket 27853.
4985 - Mention that we require Python to be 2.7 or newer for some
4986 integration tests that we ship with Tor. Resolves ticket 27677.
4989 Changes in version 0.3.5.2-alpha - 2018-09-21
4990 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
4991 that made Tor think it had run out of sockets. Anybody running a relay
4992 or an onion service on 0.3.5.1-alpha should upgrade.
4994 o Major bugfixes (relay bandwidth statistics):
4995 - When we close relayed circuits, report the data in the circuit
4996 queues as being written in our relay bandwidth stats. This
4997 mitigates guard discovery and other attacks that close circuits
4998 for the explicit purpose of noticing this discrepancy in
4999 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
5001 o Major bugfixes (socket accounting):
5002 - In our socket accounting code, count a socket as closed even when
5003 it is closed indirectly by the TLS layer. Previously, we would
5004 count these sockets as still in use, and incorrectly believe that
5005 we had run out of sockets. Fixes bug 27795; bugfix
5008 o Minor bugfixes (32-bit OSX and iOS, timing):
5009 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5010 difference algorithm for 32-bit Apple platforms. Previously, it
5011 would overflow when calculating the difference between two times
5012 more than 47 days apart. Fixes part of bug 27139; bugfix
5014 - Improve the precision of our 32-bit millisecond difference
5015 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5016 bugfix on 0.3.4.1-alpha.
5017 - Relax the tolerance on the mainloop/update_time_jumps test when
5018 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5021 o Minor bugfixes (onion service v3):
5022 - Close all SOCKS request (for the same .onion) if the newly fetched
5023 descriptor is unusable. Before that, we would close only the first
5024 one leaving the other hanging and let to time out by themselves.
5025 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5027 o Minor bugfixes (memory leak):
5028 - Fix an unlikely memory leak when trying to read a private key from
5029 a ridiculously large file. Fixes bug 27764; bugfix on
5030 0.3.5.1-alpha. This is CID 1439488.
5032 o Minor bugfixes (NSS):
5033 - Correctly detect failure to open a dummy TCP socket when stealing
5034 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
5037 o Minor bugfixes (rust):
5038 - protover_all_supported() would attempt to allocate up to 16GB on
5039 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5040 bugfix on 0.3.3.5-rc.
5042 o Minor bugfixes (testing):
5043 - Revise the "conditionvar_timeout" test so that it succeeds even on
5044 heavily loaded systems where the test threads are not scheduled
5045 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
5047 o Code simplification and refactoring:
5048 - Divide the routerlist.c and dirserv.c modules into smaller parts.
5049 Closes ticket 27799.
5052 Changes in version 0.3.5.1-alpha - 2018-09-18
5053 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
5054 client authorization for modern (v3) onion services, improves
5055 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
5056 support for NSS in place of OpenSSL, and much more.
5058 o Major features (onion services, UI change):
5059 - For a newly created onion service, the default version is now 3.
5060 Tor still supports existing version 2 services, but the operator
5061 now needs to set "HiddenServiceVersion 2" in order to create a new
5062 version 2 service. For existing services, Tor now learns the
5063 version by reading the key file. Closes ticket 27215.
5065 o Major features (relay, UI change):
5066 - Relays no longer run as exits by default. If the "ExitRelay"
5067 option is auto (or unset), and no exit policy is specified with
5068 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
5069 Previously in this case, we allowed exit traffic and logged a
5070 warning message. Closes ticket 21530. Patch by Neel Chauhan.
5071 - Tor now validates that the ContactInfo config option is valid UTF-
5072 8 when parsing torrc. Closes ticket 27428.
5074 o Major features (bootstrap):
5075 - Don't report directory progress until after a connection to a
5076 relay or bridge has succeeded. Previously, we'd report 80%
5077 progress based on cached directory information when we couldn't
5078 even connect to the network. Closes ticket 27169.
5080 o Major features (new code layout):
5081 - Nearly all of Tor's source code has been moved around into more
5082 logical places. The "common" directory is now divided into a set
5083 of libraries in "lib", and files in the "or" directory have been
5084 split into "core" (logic absolutely needed for onion routing),
5085 "feature" (independent modules in Tor), and "app" (to configure
5086 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
5087 more information. Closes ticket 26481.
5089 This refactoring is not complete: although the libraries have been
5090 refactored to be acyclic, the main body of Tor is still too
5091 interconnected. We will attempt to improve this in the future.
5093 o Major features (onion services v3):
5094 - Implement onion service client authorization at the descriptor
5095 level: only authorized clients can decrypt a service's descriptor
5096 to find out how to contact it. A new torrc option was added to
5097 control this client side: ClientOnionAuthDir <path>. On the
5098 service side, if the "authorized_clients/" directory exists in the
5099 onion service directory path, client configurations are read from
5100 the files within. See the manpage for more details. Closes ticket
5101 27547. Patch done by Suphanat Chunhapanya (haxxpop).
5102 - Improve revision counter generation in next-gen onion services.
5103 Onion services can now scale by hosting multiple instances on
5104 different hosts without synchronization between them, which was
5105 previously impossible because descriptors would get rejected by
5106 HSDirs. Addresses ticket 25552.
5108 o Major features (portability, cryptography, experimental, TLS):
5109 - Tor now has the option to compile with the NSS library instead of
5110 OpenSSL. This feature is experimental, and we expect that bugs may
5111 remain. It is mainly intended for environments where Tor's
5112 performance is not CPU-bound, and where NSS is already known to be
5113 installed. To try it out, configure Tor with the --enable-nss
5114 flag. Closes tickets 26631, 26815, and 26816.
5116 If you are experimenting with this option and using an old cached
5117 consensus, Tor may fail to start. To solve this, delete your
5118 "cached-consensus" and "cached-microdesc-consensus" files,
5119 (if present), and restart Tor.
5121 o Major bugfixes (directory authority):
5122 - Actually check that the address we get from DirAuthority
5123 configuration line is valid IPv4. Explicitly disallow DirAuthority
5124 address to be a DNS hostname. Fixes bug 26488; bugfix
5127 o Major bugfixes (restart-in-process):
5128 - Fix a use-after-free error that could be caused by passing Tor an
5129 impossible set of options that would fail during options_act().
5130 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5132 o Minor features (admin tools):
5133 - Add a new --key-expiration option to print the expiration date of
5134 the signing cert in an ed25519_signing_cert file. Resolves
5137 o Minor features (build):
5138 - If you pass the "--enable-pic" option to configure, Tor will try
5139 to tell the compiler to build position-independent code suitable
5140 to link into a dynamic library. (The default remains -fPIE, for
5141 code suitable for a relocatable executable.) Closes ticket 23846.
5143 o Minor features (code correctness, testing):
5144 - Tor's build process now includes a "check-includes" make target to
5145 verify that no module of Tor relies on any headers from a higher-
5146 level module. We hope to use this feature over time to help
5147 refactor our codebase. Closes ticket 26447.
5149 o Minor features (code layout):
5150 - We have a new "lowest-level" error-handling API for use by code
5151 invoked from within the logging module. With this interface, the
5152 logging code is no longer at risk of calling into itself if a
5153 failure occurs while it is trying to log something. Closes
5156 o Minor features (compilation):
5157 - Tor's configure script now supports a --with-malloc= option to
5158 select your malloc implementation. Supported options are
5159 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
5160 default). Addresses part of ticket 20424. Based on a patch from
5163 o Minor features (config):
5164 - The "auto" keyword in torrc is now case-insensitive. Closes
5167 o Minor features (continuous integration):
5168 - Don't do a distcheck with --disable-module-dirauth in Travis.
5169 Implements ticket 27252.
5170 - Install libcap-dev and libseccomp2-dev so these optional
5171 dependencies get tested on Travis CI. Closes ticket 26560.
5172 - Only run one online rust build in Travis, to reduce network
5173 errors. Skip offline rust builds on Travis for Linux gcc, because
5174 they're redundant. Implements ticket 27252.
5175 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5176 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5177 Linux with default settings, because all the non-default builds
5178 use gcc on Linux. Implements ticket 27252.
5180 o Minor features (controller):
5181 - Emit CIRC_BW events as soon as we detect that we processed an
5182 invalid or otherwise dropped cell on a circuit. This allows
5183 vanguards and other controllers to react more quickly to dropped
5184 cells. Closes ticket 27678.
5185 - For purposes of CIRC_BW-based dropped cell detection, track half-
5186 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
5187 bias check cells to arrive without counting it as dropped until
5188 either the END arrives, or the windows are empty. Closes
5190 - Implement a 'GETINFO md/all' controller command to enable getting
5191 all known microdescriptors. Closes ticket 8323.
5192 - The GETINFO command now support an "uptime" argument, to return
5193 Tor's uptime in seconds. Closes ticket 25132.
5195 o Minor features (denial-of-service avoidance):
5196 - Make our OOM handler aware of the DNS cache so that it doesn't
5197 fill up the memory. This check is important for our DoS mitigation
5198 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
5200 o Minor features (development):
5201 - Tor's makefile now supports running the "clippy" Rust style tool
5202 on our Rust code. Closes ticket 22156.
5204 o Minor features (directory authority):
5205 - There is no longer an artificial upper limit on the length of
5206 bandwidth lines. Closes ticket 26223.
5207 - When a bandwidth file is used to obtain the bandwidth measurements,
5208 include this bandwidth file headers in the votes. Closes
5210 - Improved support for networks with only a single authority or a
5211 single fallback directory. Patch from Gabriel Somlo. Closes
5214 o Minor features (embedding API):
5215 - The Tor controller API now supports a function to launch Tor with
5216 a preconstructed owning controller FD, so that embedding
5217 applications don't need to manage controller ports and
5218 authentication. Closes ticket 24204.
5219 - The Tor controller API now has a function that returns the name
5220 and version of the backend implementing the API. Closes
5223 o Minor features (geoip):
5224 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
5225 Country database. Closes ticket 27631.
5227 o Minor features (memory management):
5228 - Get Libevent to use the same memory allocator as Tor, by calling
5229 event_set_mem_functions() during initialization. Resolves
5232 o Minor features (memory usage):
5233 - When not using them, store legacy TAP public onion keys in DER-
5234 encoded format, rather than as expanded public keys. This should
5235 save several megabytes on typical clients. Closes ticket 27246.
5237 o Minor features (OpenSSL):
5238 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
5239 than our own. Resolves ticket 19979.
5241 o Minor features (Rust, code quality):
5242 - Improve rust code quality in the rust protover implementation by
5243 making it more idiomatic. Includes changing an internal API to
5244 take &str instead of &String. Closes ticket 26492.
5246 o Minor features (testing):
5247 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
5248 chutney. Implements ticket 27211.
5250 o Minor features (tor-resolve):
5251 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
5252 Side-effect of the refactoring for ticket 26526.
5254 o Minor features (UI):
5255 - Log each included configuration file or directory as we read it,
5256 to provide more visibility about where Tor is reading from. Patch
5257 from Unto Sten; closes ticket 27186.
5258 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
5259 Closes ticket 26703.
5261 o Minor bugfixes (bootstrap):
5262 - Try harder to get descriptors in non-exit test networks, by using
5263 the mid weight for the third hop when there are no exits. Fixes
5264 bug 27237; bugfix on 0.2.6.2-alpha.
5266 o Minor bugfixes (C correctness):
5267 - Avoid casting smartlist index to int implicitly, as it may trigger
5268 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
5269 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
5270 - Use time_t for all values in
5271 predicted_ports_prediction_time_remaining(). Rework the code that
5272 computes difference between durations/timestamps. Fixes bug 27165;
5273 bugfix on 0.3.1.1-alpha.
5275 o Minor bugfixes (client, memory usage):
5276 - When not running as a directory cache, there is no need to store
5277 the text of the current consensus networkstatus in RAM.
5278 Previously, however, clients would store it anyway, at a cost of
5279 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
5282 o Minor bugfixes (client, reachableaddresses):
5283 - Instead of adding a "reject *:*" line to ReachableAddresses when
5284 loading the configuration, add one to the policy after parsing it
5285 in parse_reachable_addresses(). This prevents extra "reject *.*"
5286 lines from accumulating on reloads. Fixes bug 20874; bugfix on
5287 0.1.1.5-alpha. Patch by Neel Chauhan.
5289 o Minor bugfixes (code quality):
5290 - Rename sandbox_getaddrinfo() and other functions to no longer
5291 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
5292 bugfix on 0.2.7.1-alpha.
5294 o Minor bugfixes (configuration, Onion Services):
5295 - In rend_service_parse_port_config(), disallow any input to remain
5296 after address-port pair was parsed. This will catch address and
5297 port being whitespace-separated by mistake of the user. Fixes bug
5298 27044; bugfix on 0.2.9.10.
5300 o Minor bugfixes (continuous integration):
5301 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5302 27464; bugfix on 0.3.4.1-alpha.
5304 o Minor bugfixes (controller):
5305 - Consider all routerinfo errors other than "not a server" to be
5306 transient for the purpose of "GETINFO exit-policy/*" controller
5307 request. Print stacktrace in the unlikely case of failing to
5308 recompute routerinfo digest. Fixes bug 27034; bugfix
5311 o Minor bugfixes (directory connection shutdown):
5312 - Avoid a double-close when shutting down a stalled directory
5313 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5315 o Minor bugfixes (HTTP tunnel):
5316 - Fix a bug warning when closing an HTTP tunnel connection due to an
5317 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5320 o Minor bugfixes (ipv6):
5321 - In addrs_in_same_network_family(), we choose the subnet size based
5322 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
5323 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
5324 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
5326 o Minor bugfixes (logging):
5327 - As a precaution, do an early return from log_addr_has_changed() if
5328 Tor is running as client. Also, log a stack trace for debugging as
5329 this function should only be called when Tor runs as server. Fixes
5330 bug 26892; bugfix on 0.1.1.9-alpha.
5331 - Refrain from mentioning bug 21018 in the logs, as it is already
5332 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
5334 o Minor bugfixes (logging, documentation):
5335 - When SafeLogging is enabled, scrub IP address in
5336 channel_tls_process_netinfo_cell(). Also, add a note to manpage
5337 that scrubbing is not guaranteed on loglevels below Notice. Fixes
5338 bug 26882; bugfix on 0.2.4.10-alpha.
5340 o Minor bugfixes (netflow padding):
5341 - Ensure circuitmux queues are empty before scheduling or sending
5342 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5344 o Minor bugfixes (onion service v2):
5345 - Log at level "info", not "warning", in the case that we do not
5346 have a consensus when a .onion request comes in. This can happen
5347 normally while bootstrapping. Fixes bug 27040; bugfix
5350 o Minor bugfixes (onion service v3):
5351 - When the onion service directory can't be created or has the wrong
5352 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5355 o Minor bugfixes (OS compatibility):
5356 - Properly handle configuration changes that move a listener to/from
5357 wildcard IP address. If the first attempt to bind a socket fails,
5358 close the old listener and try binding the socket again. Fixes bug
5359 17873; bugfix on 0.0.8pre-1.
5361 o Minor bugfixes (performance)::
5362 - Rework node_is_a_configured_bridge() to no longer call
5363 node_get_all_orports(), which was performing too many memory
5364 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
5366 o Minor bugfixes (relay statistics):
5367 - Update relay descriptor on bandwidth changes only when the uptime
5368 is smaller than 24h, in order to reduce the efficiency of guard
5369 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5371 o Minor bugfixes (relays):
5372 - Consider the fact that we'll be making direct connections to our
5373 entry and guard nodes when computing the fraction of nodes that
5374 have their descriptors. Also, if we are using bridges and there is
5375 at least one bridge with a full descriptor, treat the fraction of
5376 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
5377 Patch by Neel Chauhan.
5378 - Update the message logged on relays when DirCache is disabled.
5379 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
5380 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
5382 o Minor bugfixes (rust, protover):
5383 - Compute protover votes correctly in the rust version of the
5384 protover code. Previously, the protover rewrite in 24031 allowed
5385 repeated votes from the same voter for the same protocol version
5386 to be counted multiple times in protover_compute_vote(). Fixes bug
5387 27649; bugfix on 0.3.3.5-rc.
5388 - Reject protover names that contain invalid characters. Fixes bug
5389 27687; bugfix on 0.3.3.1-alpha.
5391 o Minor bugfixes (testing):
5392 - Fix two unit tests to work when HOME environment variable is not
5393 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
5394 - If a unit test running in a subprocess exits abnormally or with a
5395 nonzero status code, treat the test as having failed, even if the
5396 test reported success. Without this fix, memory leaks don't cause
5397 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5398 bugfix on 0.2.2.4-alpha.
5399 - When logging a version mismatch in our openssl_version tests,
5400 report the actual offending version strings. Fixes bug 26152;
5401 bugfix on 0.2.9.1-alpha.
5402 - Fix forking tests on Windows when there is a space somewhere in
5403 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
5405 o Code simplification and refactoring:
5406 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
5407 longer needed. Closes ticket 26502.
5408 - Include paths to header files within Tor are now qualified by
5409 directory within the top-level src directory.
5410 - Many structures have been removed from the centralized "or.h"
5411 header, and moved into their own headers. This will allow us to
5412 reduce the number of places in the code that rely on each
5413 structure's contents and layout. Closes ticket 26383.
5414 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
5415 - Remove GetAdaptersAddresses_fn_t. The code that used it was
5416 removed as part of the 26481 refactor. Closes ticket 27467.
5417 - Rework Tor SOCKS server code to use Trunnel and benefit from
5418 autogenerated functions for parsing and generating SOCKS wire
5419 format. New implementation is cleaner, more maintainable and
5420 should be less prone to heartbleed-style vulnerabilities.
5421 Implements a significant fraction of ticket 3569.
5422 - Split sampled_guards_update_from_consensus() and
5423 select_entry_guard_for_circuit() into subfunctions. In
5424 entry_guards_update_primary() unite three smartlist enumerations
5425 into one and move smartlist comparison code out of the function.
5426 Closes ticket 21349.
5427 - Tor now assumes that you have standards-conformant stdint.h and
5428 inttypes.h headers when compiling. Closes ticket 26626.
5429 - Unify our bloom filter logic. Previously we had two copies of this
5430 code: one for routerlist filtering, and one for address set
5431 calculations. Closes ticket 26510.
5432 - Use the simpler strcmpstart() helper in
5433 rend_parse_v2_service_descriptor instead of strncmp(). Closes
5435 - Utility functions that can perform a DNS lookup are now wholly
5436 separated from those that can't, in separate headers and C
5437 modules. Closes ticket 26526.
5440 - Copy paragraph and URL to Tor's code of conduct document from
5441 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
5442 - Remove old instructions from INSTALL document. Closes ticket 26588.
5443 - Warn users that they should not include MyFamily line(s) in their
5444 torrc when running Tor bridge. Closes ticket 26908.
5447 - Tor no longer supports building with the dmalloc library. For
5448 debugging memory issues, we suggest using gperftools or msan
5449 instead. Closes ticket 26426.
5450 - Tor no longer attempts to run on Windows environments without the
5451 GetAdaptersAddresses() function. This function has existed since
5452 Windows XP, which is itself already older than we support.
5453 - Remove Tor2web functionality for version 2 onion services. The
5454 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
5455 (This feature was never shipped in vanilla Tor and it was only
5456 possible to use this feature by building the support at compile
5457 time. Tor2webMode is not implemented for version 3 onion services.)
5458 Closes ticket 26367.
5461 Changes in version 0.2.9.17 - 2018-09-10
5462 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
5464 o Minor features (compatibility, backport from 0.3.4.8):
5465 - Tell OpenSSL to maintain backward compatibility with previous
5466 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5467 ciphers are disabled by default. Closes ticket 27344.
5469 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5470 - Enable macOS builds in our Travis CI configuration. Closes
5472 - Install libcap-dev and libseccomp2-dev so these optional
5473 dependencies get tested on Travis CI. Closes ticket 26560.
5474 - Run asciidoc during Travis CI. Implements ticket 27087.
5475 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5477 o Minor features (geoip):
5478 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5479 Country database. Closes ticket 27089.
5481 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5482 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5483 tell the compiler not to include the system malloc implementation.
5484 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5486 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5487 - Silence a spurious compiler warning on the GetAdaptersAddresses
5488 function pointer cast. This issue is already fixed by 26481 in
5489 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5490 bugfix on 0.2.3.11-alpha.
5491 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5492 supported, and always fails. Some compilers warn about the
5493 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5496 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5497 - Don't link or search for pthreads when building for Windows, even
5498 if we are using build environment (like mingw) that provides a
5499 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5501 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5502 - Skip a pair of unreliable key generation tests on Windows, until
5503 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5504 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5506 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5507 - Pass the module flags to distcheck configure, and log the flags
5508 before running configure. (Backported to 0.2.9 and later as a
5509 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5511 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5512 - When a Travis build fails, and showing a log fails, keep trying to
5513 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5514 - When we use echo in Travis, don't pass a --flag as the first
5515 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5517 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5518 - When voting for recommended versions, make sure that all of the
5519 versions are well-formed and parsable. Fixes bug 26485; bugfix
5522 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5523 - Fix a bug in out sandboxing rules for the openat() syscall.
5524 Previously, no openat() call would be permitted, which would break
5525 filesystem operations on recent glibc versions. Fixes bug 25440;
5526 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5528 o Minor bugfixes (onion services, backport from 0.3.4.8):
5529 - Silence a spurious compiler warning in
5530 rend_client_send_introduction(). Fixes bug 27463; bugfix
5533 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5534 - Log a protocol warning when single onion services or Tor2web clients
5535 fail to authenticate direct connections to relays.
5536 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5538 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5539 - Disable core dumps in test_bt.sh, to avoid failures in "make
5540 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5542 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5543 - Before running make test-network-all, delete old logs and test
5544 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5547 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5548 - Our "tortls/cert_matches_key" unit test no longer relies on
5549 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5550 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5551 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5553 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5554 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5555 27185; bugfix on 0.2.2.2-alpha.
5558 Changes in version 0.3.2.12 - 2018-09-10
5559 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
5561 o Minor features (compatibility, backport from 0.3.4.8):
5562 - Tell OpenSSL to maintain backward compatibility with previous
5563 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5564 ciphers are disabled by default. Closes ticket 27344.
5566 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5567 - Enable macOS builds in our Travis CI configuration. Closes
5569 - Install libcap-dev and libseccomp2-dev so these optional
5570 dependencies get tested on Travis CI. Closes ticket 26560.
5571 - Run asciidoc during Travis CI. Implements ticket 27087.
5572 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5574 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5575 - Use cargo cache in our Travis CI configuration. Closes
5578 o Minor features (controller, backport from 0.3.4.6-rc):
5579 - The control port now exposes the list of HTTPTunnelPorts and
5580 ExtOrPorts via GETINFO net/listeners/httptunnel and
5581 net/listeners/extor respectively. Closes ticket 26647.
5583 o Minor features (directory authorities, backport from 0.3.4.7-rc):
5584 - Authorities no longer vote to make the subprotocol version
5585 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5586 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5588 o Minor features (geoip):
5589 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5590 Country database. Closes ticket 27089.
5592 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5593 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5594 tell the compiler not to include the system malloc implementation.
5595 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5596 - Don't try to use a pragma to temporarily disable the
5597 -Wunused-const-variable warning if the compiler doesn't support
5598 it. Fixes bug 26785; bugfix on 0.3.2.11.
5600 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5601 - Silence a spurious compiler warning on the GetAdaptersAddresses
5602 function pointer cast. This issue is already fixed by 26481 in
5603 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5604 bugfix on 0.2.3.11-alpha.
5605 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5606 supported, and always fails. Some compilers warn about the
5607 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5610 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5611 - Don't link or search for pthreads when building for Windows, even
5612 if we are using build environment (like mingw) that provides a
5613 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5615 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5616 - Skip a pair of unreliable key generation tests on Windows, until
5617 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5618 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5620 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5621 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5622 - Pass the module flags to distcheck configure, and log the flags
5623 before running configure. (Backported to 0.2.9 and later as a
5624 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5626 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5627 - When a Travis build fails, and showing a log fails, keep trying to
5628 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5629 - When we use echo in Travis, don't pass a --flag as the first
5630 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5632 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5633 - When voting for recommended versions, make sure that all of the
5634 versions are well-formed and parsable. Fixes bug 26485; bugfix
5637 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5638 - Fix a bug in out sandboxing rules for the openat() syscall.
5639 Previously, no openat() call would be permitted, which would break
5640 filesystem operations on recent glibc versions. Fixes bug 25440;
5641 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5643 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
5644 - Improve the log message when connection initiators fail to
5645 authenticate direct connections to relays. Fixes bug 26927; bugfix
5648 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
5649 - Fix bug that causes services to not ever rotate their descriptors
5650 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5653 o Minor bugfixes (onion services, backport from 0.3.4.8):
5654 - Silence a spurious compiler warning in
5655 rend_client_send_introduction(). Fixes bug 27463; bugfix
5658 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
5659 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5661 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5662 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5663 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5664 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5666 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5667 - Log a protocol warning when single onion services or Tor2web clients
5668 fail to authenticate direct connections to relays.
5669 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5671 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5672 - Disable core dumps in test_bt.sh, to avoid failures in "make
5673 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5675 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5676 - When running make test-network-all, use the mixed+hs-v2 network.
5677 (A previous fix to chutney removed v3 onion services from the
5678 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5679 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5680 - Before running make test-network-all, delete old logs and test
5681 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5684 o Minor bugfixes (testing, openssl compatibility):
5685 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
5686 internals. Previously, it relied on unsupported OpenSSL behavior in
5687 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
5688 bugfix on 0.2.5.1-alpha.
5690 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5691 - Our "tortls/cert_matches_key" unit test no longer relies on
5692 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5693 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5694 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5696 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5697 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5698 27185; bugfix on 0.2.2.2-alpha.
5701 Changes in version 0.3.3.10 - 2018-09-10
5702 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
5704 o Minor features (bug workaround, backport from 0.3.4.7-rc):
5705 - Compile correctly on systems that provide the C11 stdatomic.h
5706 header, but where C11 atomic functions don't actually compile.
5707 Closes ticket 26779; workaround for Debian issue 903709.
5709 o Minor features (compatibility, backport from 0.3.4.8):
5710 - Tell OpenSSL to maintain backward compatibility with previous
5711 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5712 ciphers are disabled by default. Closes ticket 27344.
5714 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5715 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
5716 - Enable macOS builds in our Travis CI configuration. Closes
5718 - Install libcap-dev and libseccomp2-dev so these optional
5719 dependencies get tested on Travis CI. Closes ticket 26560.
5720 - Run asciidoc during Travis CI. Implements ticket 27087.
5721 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5723 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5724 - Use cargo cache in our Travis CI configuration. Closes
5727 o Minor features (controller, backport from 0.3.4.6-rc):
5728 - The control port now exposes the list of HTTPTunnelPorts and
5729 ExtOrPorts via GETINFO net/listeners/httptunnel and
5730 net/listeners/extor respectively. Closes ticket 26647.
5732 o Minor features (directory authorities, backport from 0.3.4.7-rc):
5733 - Authorities no longer vote to make the subprotocol version
5734 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5735 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5737 o Minor features (geoip):
5738 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5739 Country database. Closes ticket 27089.
5741 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5742 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5743 tell the compiler not to include the system malloc implementation.
5744 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5745 - Don't try to use a pragma to temporarily disable the
5746 -Wunused-const-variable warning if the compiler doesn't support
5747 it. Fixes bug 26785; bugfix on 0.3.2.11.
5749 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5750 - Silence a spurious compiler warning on the GetAdaptersAddresses
5751 function pointer cast. This issue is already fixed by 26481 in
5752 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5753 bugfix on 0.2.3.11-alpha.
5754 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5755 supported, and always fails. Some compilers warn about the
5756 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5759 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5760 - Don't link or search for pthreads when building for Windows, even
5761 if we are using build environment (like mingw) that provides a
5762 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5764 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5765 - Skip a pair of unreliable key generation tests on Windows, until
5766 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5767 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5769 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5770 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5771 - Pass the module flags to distcheck configure, and log the flags
5772 before running configure. (Backported to 0.2.9 and later as a
5773 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5775 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5776 - When a Travis build fails, and showing a log fails, keep trying to
5777 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5778 - When we use echo in Travis, don't pass a --flag as the first
5779 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5781 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5782 - When voting for recommended versions, make sure that all of the
5783 versions are well-formed and parsable. Fixes bug 26485; bugfix
5786 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
5787 - Always call tor_free_all() when leaving tor_run_main(). When we
5788 did not, restarting tor in-process would cause an assertion
5789 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
5791 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5792 - Fix a bug in our sandboxing rules for the openat() syscall.
5793 Previously, no openat() call would be permitted, which would break
5794 filesystem operations on recent glibc versions. Fixes bug 25440;
5795 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5797 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
5798 - Improve the log message when connection initiators fail to
5799 authenticate direct connections to relays. Fixes bug 26927; bugfix
5802 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
5803 - Fix bug that causes services to not ever rotate their descriptors
5804 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5807 o Minor bugfixes (onion services, backport from 0.3.4.8):
5808 - Silence a spurious compiler warning in
5809 rend_client_send_introduction(). Fixes bug 27463; bugfix
5812 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
5813 - Work around two different bugs in the OS X 10.10 and later SDKs
5814 that would prevent us from successfully targeting earlier versions
5815 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
5817 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
5818 - Fix compilation of the unit tests on GNU/Hurd, which does not
5819 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
5822 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
5823 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5825 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5826 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5827 - Protover parsing was accepting the presence of whitespace in
5828 version strings, which the C implementation would choke on, e.g.
5829 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
5830 - Protover parsing was ignoring a 2nd hyphen and everything after
5831 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
5833 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5834 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5835 - cd to ${abs_top_builddir}/src/rust before running cargo in
5836 src/test/test_rust.sh. This makes the working directory consistent
5837 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
5839 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5840 - Log a protocol warning when single onion services or Tor2web clients
5841 fail to authenticate direct connections to relays.
5842 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5844 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5845 - Disable core dumps in test_bt.sh, to avoid failures in "make
5846 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5848 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5849 - When running make test-network-all, use the mixed+hs-v2 network.
5850 (A previous fix to chutney removed v3 onion services from the
5851 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5852 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5853 - Before running make test-network-all, delete old logs and test
5854 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5857 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5858 - Our "tortls/cert_matches_key" unit test no longer relies on
5859 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5860 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5861 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5863 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
5864 - Stop sending ed25519 link specifiers in v3 onion service introduce
5865 cells and descriptors, when the rendezvous or introduction point
5866 doesn't support ed25519 link authentication. Fixes bug 26627;
5867 bugfix on 0.3.2.4-alpha.
5869 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5870 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5871 27185; bugfix on 0.2.2.2-alpha.
5874 Changes in version 0.3.4.8 - 2018-09-10
5875 Tor 0.3.4.8 is the first stable release in its series; it includes
5876 compilation and portability fixes.
5878 The Tor 0.3.4 series includes improvements for running Tor in
5879 low-power and embedded environments, which should help performance in
5880 general. We've begun work on better modularity, and included preliminary
5881 changes on the directory authority side to accommodate a new bandwidth
5882 measurement system. We've also integrated more continuous-integration
5883 systems into our development process, and made corresponding changes to
5884 Tor's testing infrastructure. Finally, we've continued to refine
5885 our anti-denial-of-service code.
5887 Below are the changes since 0.3.4.7-rc. For a complete list of changes
5888 since 0.3.3.9, see the ReleaseNotes file.
5890 o Minor features (compatibility):
5891 - Tell OpenSSL to maintain backward compatibility with previous
5892 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5893 ciphers are disabled by default. Closes ticket 27344.
5895 o Minor features (continuous integration):
5896 - Log the compiler path and version during Appveyor builds.
5897 Implements ticket 27449.
5898 - Show config.log and test-suite.log after failed Appveyor builds.
5899 Also upload the zipped full logs as a build artifact. Implements
5902 o Minor bugfixes (compilation):
5903 - Silence a spurious compiler warning on the GetAdaptersAddresses
5904 function pointer cast. This issue is already fixed by 26481 in
5905 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5906 bugfix on 0.2.3.11-alpha.
5907 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5908 supported, and always fails. Some compilers warn about the
5909 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5912 o Minor bugfixes (continuous integration):
5913 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
5914 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
5915 Executables compiled for 64-bit Windows with this version of gcc
5916 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
5917 27460; bugfix on 0.3.4.1-alpha.
5918 - When a Travis build fails, and showing a log fails, keep trying to
5919 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5920 - When we use echo in Travis, don't pass a --flag as the first
5921 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5923 o Minor bugfixes (onion services):
5924 - Silence a spurious compiler warning in
5925 rend_client_send_introduction(). Fixes bug 27463; bugfix
5928 o Minor bugfixes (testing, chutney):
5929 - When running make test-network-all, use the mixed+hs-v2 network.
5930 (A previous fix to chutney removed v3 onion services from the
5931 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5932 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5933 - Before running make test-network-all, delete old logs and test
5934 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5937 Changes in version 0.3.4.7-rc - 2018-08-24
5938 Tor 0.3.4.7-rc fixes several small compilation, portability, and
5939 correctness issues in previous versions of Tor. This version is a
5940 release candidate: if no serious bugs are found, we expect that the
5941 stable 0.3.4 release will be (almost) the same as this release.
5943 o Minor features (bug workaround):
5944 - Compile correctly on systems that provide the C11 stdatomic.h
5945 header, but where C11 atomic functions don't actually compile.
5946 Closes ticket 26779; workaround for Debian issue 903709.
5948 o Minor features (continuous integration):
5949 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
5950 - Enable macOS builds in our Travis CI configuration. Closes
5952 - Install libcap-dev and libseccomp2-dev so these optional
5953 dependencies get tested on Travis CI. Closes ticket 26560.
5954 - Only post Appveyor IRC notifications when the build fails.
5955 Implements ticket 27275.
5956 - Run asciidoc during Travis CI. Implements ticket 27087.
5957 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5959 o Minor features (continuous integration, rust):
5960 - Use cargo cache in our Travis CI configuration. Closes
5963 o Minor features (directory authorities):
5964 - Authorities no longer vote to make the subprotocol version
5965 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5966 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5968 o Minor features (geoip):
5969 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5970 Country database. Closes ticket 27089.
5972 o Minor bugfixes (compilation, windows):
5973 - Don't link or search for pthreads when building for Windows, even
5974 if we are using build environment (like mingw) that provides a
5975 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5977 o Minor bugfixes (continuous integration):
5978 - Improve Appveyor CI IRC logging. Generate correct branches and
5979 URLs for pull requests and tags. Use unambiguous short commits.
5980 Fixes bug 26979; bugfix on master.
5981 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5982 - Pass the module flags to distcheck configure, and log the flags
5983 before running configure. (Backported to 0.2.9 and later as a
5984 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5986 o Minor bugfixes (in-process restart):
5987 - Always call tor_free_all() when leaving tor_run_main(). When we
5988 did not, restarting tor in-process would cause an assertion
5989 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
5991 o Minor bugfixes (linux seccomp2 sandbox):
5992 - Fix a bug in out sandboxing rules for the openat() syscall.
5993 Previously, no openat() call would be permitted, which would break
5994 filesystem operations on recent glibc versions. Fixes bug 25440;
5995 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5997 o Minor bugfixes (onion services):
5998 - Fix bug that causes services to not ever rotate their descriptors
5999 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6002 o Minor bugfixes (portability):
6003 - Fix compilation of the unit tests on GNU/Hurd, which does not
6004 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6007 o Minor bugfixes (rust):
6008 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6010 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6011 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6012 - Protover parsing was accepting the presence of whitespace in
6013 version strings, which the C implementation would choke on, e.g.
6014 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6015 - Protover parsing was ignoring a 2nd hyphen and everything after
6016 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6018 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6019 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6020 - cd to ${abs_top_builddir}/src/rust before running cargo in
6021 src/test/test_rust.sh. This makes the working directory consistent
6022 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6024 o Minor bugfixes (testing, bootstrap):
6025 - When calculating bootstrap progress, check exit policies and the
6026 exit flag. Previously, Tor would only check the exit flag, which
6027 caused race conditions in small and fast networks like chutney.
6028 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
6030 o Minor bugfixes (testing, openssl compatibility):
6031 - Our "tortls/cert_matches_key" unit test no longer relies on
6032 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6033 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6034 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6036 o Minor bugfixes (Windows, compilation):
6037 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6038 27185; bugfix on 0.2.2.2-alpha.
6041 Changes in version 0.3.4.6-rc - 2018-08-06
6042 Tor 0.3.4.6-rc fixes several small compilation, portability, and
6043 correctness issues in previous versions of Tor. This version is a
6044 release candidate: if no serious bugs are found, we expect that the
6045 stable 0.3.4 release will be (almost) the same as this release.
6047 o Major bugfixes (event scheduler):
6048 - When we enable a periodic event, schedule it in the event loop
6049 rather than running it immediately. Previously, we would re-run
6050 periodic events immediately in the middle of (for example)
6051 changing our options, with unpredictable effects. Fixes bug 27003;
6052 bugfix on 0.3.4.1-alpha.
6054 o Minor features (compilation):
6055 - When building Tor, prefer to use Python 3 over Python 2, and more
6056 recent (contemplated) versions over older ones. Closes
6058 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6059 tell the compiler not to include the system malloc implementation.
6060 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6061 - Don't try to use a pragma to temporarily disable the
6062 -Wunused-const-variable warning if the compiler doesn't support
6063 it. Fixes bug 26785; bugfix on 0.3.2.11.
6065 o Minor bugfixes (continuous integration):
6066 - Skip a pair of unreliable key generation tests on Windows, until
6067 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6068 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6070 o Minor features (controller):
6071 - The control port now exposes the list of HTTPTunnelPorts and
6072 ExtOrPorts via GETINFO net/listeners/httptunnel and
6073 net/listeners/extor respectively. Closes ticket 26647.
6075 o Minor bugfixes (directory authority):
6076 - When voting for recommended versions, make sure that all of the
6077 versions are well-formed and parsable. Fixes bug 26485; bugfix
6080 o Minor features (geoip):
6081 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6082 Country database. Closes ticket 26674.
6084 o Minor features (Rust, portability):
6085 - Rust cross-compilation is now supported. Closes ticket 25895.
6087 o Minor bugfixes (compilation):
6088 - Update build system so that tor builds again with --disable-unittests
6089 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
6090 - Fix a compilation warning on some versions of GCC when building
6091 code that calls routerinfo_get_my_routerinfo() twice, assuming
6092 that the second call will succeed if the first one did. Fixes bug
6093 26269; bugfix on 0.2.8.2-alpha.
6095 o Minor bugfixes (controller):
6096 - Report the port correctly when a port is configured to bind to
6097 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
6098 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
6099 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
6100 on 0.3.3.1-alpha. Patch by "akwizgran".
6102 o Minor bugfixes (correctness, flow control):
6103 - Upon receiving a stream-level SENDME cell, verify that our window
6104 has not grown too large. Fixes bug 26214; bugfix on svn
6107 o Minor bugfixes (memory, correctness):
6108 - Fix a number of small memory leaks identified by coverity. Fixes
6109 bug 26467; bugfix on numerous Tor versions.
6111 o Minor bugfixes (logging):
6112 - Improve the log message when connection initiators fail to
6113 authenticate direct connections to relays. Fixes bug 26927; bugfix
6116 o Minor bugfixes (portability):
6117 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
6118 26994; bugfix on 0.3.4.1-alpha.
6119 - Work around two different bugs in the OS X 10.10 and later SDKs
6120 that would prevent us from successfully targeting earlier versions
6121 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6123 o Minor bugfixes (single onion services, Tor2web):
6124 - Log a protocol warning when single onion services or Tor2web
6125 clients fail to authenticate direct connections to relays. Fixes
6126 bug 26924; bugfix on 0.2.9.1-alpha.
6128 o Minor bugfixes (testing):
6129 - Disable core dumps in test_bt.sh, to avoid failures in "make
6130 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6132 o Minor bugfixes (testing, compatibility):
6133 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
6134 only to pass strings (rather than "bytes" objects) to the Python
6135 subprocess module. Python 3 on Windows seems to require this.
6136 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
6137 0.3.1.1-alpha (for hs_ntor_ref.py).
6139 o Minor bugfixes (v3 onion services):
6140 - Stop sending ed25519 link specifiers in v3 onion service introduce
6141 cells and descriptors, when the rendezvous or introduction point
6142 doesn't support ed25519 link authentication. Fixes bug 26627;
6143 bugfix on 0.3.2.4-alpha.
6146 Changes in version 0.3.4.5-rc - 2018-07-13
6147 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
6148 bridge relays should upgrade.
6150 o Directory authority changes:
6151 - The "Bifroest" bridge authority has been retired; the new bridge
6152 authority is "Serge", and it is operated by George from the
6153 TorBSD project. Closes ticket 26771.
6156 Changes in version 0.3.3.9 - 2018-07-13
6157 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
6158 bridge relays should upgrade.
6160 o Directory authority changes:
6161 - The "Bifroest" bridge authority has been retired; the new bridge
6162 authority is "Serge", and it is operated by George from the
6163 TorBSD project. Closes ticket 26771.
6166 Changes in version 0.3.2.11 - 2018-07-13
6167 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
6168 bridge relays should upgrade. We also take this opportunity to backport
6171 o Directory authority changes:
6172 - The "Bifroest" bridge authority has been retired; the new bridge
6173 authority is "Serge", and it is operated by George from the
6174 TorBSD project. Closes ticket 26771.
6176 o Directory authority changes (backport from 0.3.3.7):
6177 - Add an IPv6 address for the "dannenberg" directory authority.
6178 Closes ticket 26343.
6180 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6181 - When directory authorities read a zero-byte bandwidth file, they
6182 would previously log a warning with the contents of an
6183 uninitialised buffer. They now log a warning about the empty file
6184 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6186 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6187 - Correctly detect when onion services get disabled after HUP. Fixes
6188 bug 25761; bugfix on 0.3.2.1.
6190 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6191 - Explicitly permit the poll() system call when the Linux
6192 seccomp2-based sandbox is enabled: apparently, some versions of
6193 libc use poll() when calling getpwnam(). Closes ticket 25313.
6195 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
6196 - Update the Travis CI configuration to use the stable Rust channel,
6197 now that we have decided to require that. Closes ticket 25714.
6199 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6200 - Our .travis.yml configuration now includes support for testing the
6201 results of "make distcheck". (It's not uncommon for "make check"
6202 to pass but "make distcheck" to fail.) Closes ticket 25814.
6203 - Our Travis CI configuration now integrates with the Coveralls
6204 coverage analysis tool. Closes ticket 25818.
6206 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6207 - Add several checks to detect whether Tor relays are uploading
6208 their descriptors without specifying why they regenerated them.
6209 Diagnostic for ticket 25686.
6211 o Minor features (compilation, backport from 0.3.4.4-rc):
6212 - When building Tor, prefer to use Python 3 over Python 2, and more
6213 recent (contemplated) versions over older ones. Closes
6216 o Minor features (geoip):
6217 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6218 Country database. Closes ticket 26674.
6220 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6221 - Upon receiving a malformed connected cell, stop processing the
6222 cell immediately. Previously we would mark the connection for
6223 close, but continue processing the cell as if the connection were
6224 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6226 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6227 - Allow the nanosleep() system call, which glibc uses to implement
6228 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6230 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6231 - When running the hs_ntor_ref.py test, make sure only to pass
6232 strings (rather than "bytes" objects) to the Python subprocess
6233 module. Python 3 on Windows seems to require this. Fixes bug
6234 26535; bugfix on 0.3.1.1-alpha.
6235 - When running the ntor_ref.py test, make sure only to pass strings
6236 (rather than "bytes" objects) to the Python subprocess module.
6237 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6240 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6241 - Work around a change in OpenSSL 1.1.1 where return values that
6242 would previously indicate "no password" now indicate an empty
6243 password. Without this workaround, Tor instances running with
6244 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6245 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6247 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
6248 - Document that the PerConnBW{Rate,Burst} options will fall back to
6249 their corresponding consensus parameters only if those parameters
6250 are set. Previously we had claimed that these values would always
6251 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
6253 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6254 - Fix a compilation warning on some versions of GCC when building
6255 code that calls routerinfo_get_my_routerinfo() twice, assuming
6256 that the second call will succeed if the first one did. Fixes bug
6257 26269; bugfix on 0.2.8.2-alpha.
6259 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6260 - Don't consider Tor running as a client if the ControlPort is open,
6261 but no actual client ports are open. Fixes bug 26062; bugfix
6264 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6265 - Prevent a possible out-of-bounds smartlist read in
6266 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6268 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6269 - Fix a very unlikely (impossible, we believe) null pointer
6270 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6271 Coverity; this is CID 1430932.
6273 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6274 - Fix a memory leak when a v3 onion service is configured and gets a
6275 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6276 - When parsing the descriptor signature, look for the token plus an
6277 extra white-space at the end. This is more correct but also will
6278 allow us to support new fields that might start with "signature".
6279 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6281 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6282 - Relays now correctly block attempts to re-extend to the previous
6283 relay by Ed25519 identity. Previously they would warn in this
6284 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6287 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6288 - Avoid a crash when running with DirPort set but ORPort turned off.
6289 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6291 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6292 - Silence unused-const-variable warnings in zstd.h with some GCC
6293 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6295 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
6296 - Avoid intermittent test failures due to a test that had relied on
6297 onion service introduction point creation finishing within 5
6298 seconds of real clock time. Fixes bug 25450; bugfix
6301 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
6302 - Fix a C99 compliance issue in our configuration script that caused
6303 compilation issues when compiling Tor with certain versions of
6304 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
6306 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6307 - Fix a number of small memory leaks identified by coverity. Fixes
6308 bug 26467; bugfix on numerous Tor versions.
6310 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6311 - Move the list of default directory authorities to its own file.
6312 Closes ticket 24854. Patch by "beastr0".
6315 Changes in version 0.2.9.16 - 2018-07-13
6316 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
6317 bridge relays should upgrade. We also take this opportunity to backport
6320 o Directory authority changes:
6321 - The "Bifroest" bridge authority has been retired; the new bridge
6322 authority is "Serge", and it is operated by George from the
6323 TorBSD project. Closes ticket 26771.
6325 o Directory authority changes (backport from 0.3.3.7):
6326 - Add an IPv6 address for the "dannenberg" directory authority.
6327 Closes ticket 26343.
6329 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6330 - When directory authorities read a zero-byte bandwidth file, they
6331 would previously log a warning with the contents of an
6332 uninitialised buffer. They now log a warning about the empty file
6333 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6335 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6336 - Explicitly permit the poll() system call when the Linux
6337 seccomp2-based sandbox is enabled: apparently, some versions of
6338 libc use poll() when calling getpwnam(). Closes ticket 25313.
6340 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6341 - Our .travis.yml configuration now includes support for testing the
6342 results of "make distcheck". (It's not uncommon for "make check"
6343 to pass but "make distcheck" to fail.) Closes ticket 25814.
6344 - Our Travis CI configuration now integrates with the Coveralls
6345 coverage analysis tool. Closes ticket 25818.
6347 o Minor features (compilation, backport from 0.3.4.4-rc):
6348 - When building Tor, prefer to use Python 3 over Python 2, and more
6349 recent (contemplated) versions over older ones. Closes
6352 o Minor features (geoip):
6353 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6354 Country database. Closes ticket 26674.
6356 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6357 - Upon receiving a malformed connected cell, stop processing the
6358 cell immediately. Previously we would mark the connection for
6359 close, but continue processing the cell as if the connection were
6360 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6362 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6363 - Allow the nanosleep() system call, which glibc uses to implement
6364 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6366 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6367 - When running the ntor_ref.py test, make sure only to pass strings
6368 (rather than "bytes" objects) to the Python subprocess module.
6369 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6372 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6373 - Work around a change in OpenSSL 1.1.1 where return values that
6374 would previously indicate "no password" now indicate an empty
6375 password. Without this workaround, Tor instances running with
6376 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6377 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6379 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6380 - Fix a compilation warning on some versions of GCC when building
6381 code that calls routerinfo_get_my_routerinfo() twice, assuming
6382 that the second call will succeed if the first one did. Fixes bug
6383 26269; bugfix on 0.2.8.2-alpha.
6385 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6386 - Don't consider Tor running as a client if the ControlPort is open,
6387 but no actual client ports are open. Fixes bug 26062; bugfix
6390 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6391 - Prevent a possible out-of-bounds smartlist read in
6392 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6394 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6395 - Fix a very unlikely (impossible, we believe) null pointer
6396 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6397 Coverity; this is CID 1430932.
6399 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6400 - Fix a number of small memory leaks identified by coverity. Fixes
6401 bug 26467; bugfix on numerous Tor versions.
6403 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6404 - Move the list of default directory authorities to its own file.
6405 Closes ticket 24854. Patch by "beastr0".
6408 Changes in version 0.3.4.4-rc - 2018-07-09
6409 Tor 0.3.4.4-rc fixes several small compilation, portability, and
6410 correctness issues in previous versions of Tor. This version is a
6411 release candidate: if no serious bugs are found, we expect that the
6412 stable 0.3.4 release will be (almost) the same as this release.
6414 o Minor features (compilation):
6415 - When building Tor, prefer to use Python 3 over Python 2, and more
6416 recent (contemplated) versions over older ones. Closes
6419 o Minor features (geoip):
6420 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6421 Country database. Closes ticket 26674.
6423 o Minor features (Rust, portability):
6424 - Rust cross-compilation is now supported. Closes ticket 25895.
6426 o Minor bugfixes (compilation):
6427 - Fix a compilation warning on some versions of GCC when building
6428 code that calls routerinfo_get_my_routerinfo() twice, assuming
6429 that the second call will succeed if the first one did. Fixes bug
6430 26269; bugfix on 0.2.8.2-alpha.
6432 o Minor bugfixes (control port):
6433 - Report the port correctly when a port is configured to bind to
6434 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
6435 - Handle the HSADDRESS= argument to the HSPOST command properly.
6436 (Previously, this argument was misparsed and thus ignored.) Fixes
6437 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6439 o Minor bugfixes (correctness, flow control):
6440 - Upon receiving a stream-level SENDME cell, verify that our window
6441 has not grown too large. Fixes bug 26214; bugfix on svn
6444 o Minor bugfixes (memory, correctness):
6445 - Fix a number of small memory leaks identified by coverity. Fixes
6446 bug 26467; bugfix on numerous Tor versions.
6448 o Minor bugfixes (testing, compatibility):
6449 - When running the hs_ntor_ref.py test, make sure only to pass
6450 strings (rather than "bytes" objects) to the Python subprocess
6451 module. Python 3 on Windows seems to require this. Fixes bug
6452 26535; bugfix on 0.3.1.1-alpha.
6453 - When running the ntor_ref.py test, make sure only to pass strings
6454 (rather than "bytes" objects) to the Python subprocess module.
6455 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6459 Changes in version 0.3.3.8 - 2018-07-09
6460 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
6461 fixes for a memory leak affecting directory authorities.
6463 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
6464 - Stop leaking memory on directory authorities when planning to
6465 vote. This bug was crashing authorities by exhausting their
6466 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6468 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
6469 - Make sure that failing tests in Rust will actually cause the build
6470 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6473 o Minor features (compilation, backport from 0.3.4.4-rc):
6474 - When building Tor, prefer to use Python 3 over Python 2, and more
6475 recent (contemplated) versions over older ones. Closes
6478 o Minor features (geoip):
6479 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6480 Country database. Closes ticket 26674.
6482 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6483 - Add several checks to detect whether Tor relays are uploading
6484 their descriptors without specifying why they regenerated them.
6485 Diagnostic for ticket 25686.
6487 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
6488 - Don't count path selection failures as circuit build failures.
6489 This change should eliminate cases where Tor blames its guard or
6490 the network for situations like insufficient microdescriptors
6491 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
6494 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6495 - Fix a compilation warning on some versions of GCC when building
6496 code that calls routerinfo_get_my_routerinfo() twice, assuming
6497 that the second call will succeed if the first one did. Fixes bug
6498 26269; bugfix on 0.2.8.2-alpha.
6500 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
6501 - Handle the HSADDRESS= argument to the HSPOST command properly.
6502 (Previously, this argument was misparsed and thus ignored.) Fixes
6503 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6505 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6506 - Fix a number of small memory leaks identified by coverity. Fixes
6507 bug 26467; bugfix on numerous Tor versions.
6509 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6510 - Relays now correctly block attempts to re-extend to the previous
6511 relay by Ed25519 identity. Previously they would warn in this
6512 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6515 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
6516 - When shutting down, Tor now clears all the flags in the control.c
6517 module. This should prevent a bug where authentication cookies are
6518 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
6520 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6521 - When running the hs_ntor_ref.py test, make sure only to pass
6522 strings (rather than "bytes" objects) to the Python subprocess
6523 module. Python 3 on Windows seems to require this. Fixes bug
6524 26535; bugfix on 0.3.1.1-alpha.
6525 - When running the ntor_ref.py test, make sure only to pass strings
6526 (rather than "bytes" objects) to the Python subprocess module.
6527 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6531 Changes in version 0.3.4.3-alpha - 2018-06-26
6532 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
6533 one that was causing stability issues on directory authorities.
6535 o Major bugfixes (directory authority):
6536 - Stop leaking memory on directory authorities when planning to
6537 vote. This bug was crashing authorities by exhausting their
6538 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6540 o Major bugfixes (rust, testing):
6541 - Make sure that failing tests in Rust will actually cause the build
6542 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6545 o Minor feature (directory authorities):
6546 - Stop warning about incomplete bw lines before the first complete
6547 bw line has been found, so that additional header lines can be
6548 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
6550 o Minor features (relay, diagnostic):
6551 - Add several checks to detect whether Tor relays are uploading
6552 their descriptors without specifying why they regenerated them.
6553 Diagnostic for ticket 25686.
6555 o Minor features (unit tests):
6556 - Test complete bandwidth measurements files, and test that
6557 incomplete bandwidth lines only give warnings when the end of the
6558 header has not been detected. Fixes bug 25947; bugfix
6561 o Minor bugfixes (compilation):
6562 - Refrain from compiling unit testing related object files when
6563 --disable-unittests is set to configure script. Fixes bug 24891;
6564 bugfix on 0.2.5.1-alpha.
6565 - When linking the libtor_testing.a library, only include the
6566 dirauth object files once. Previously, they were getting added
6567 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
6568 - The --enable-fatal-warnings flag now affects Rust code as well.
6569 Closes ticket 26245.
6571 o Minor bugfixes (onion services):
6572 - Recompute some consensus information after detecting a clock jump,
6573 or after transitioning from a non-live consensus to a live
6574 consensus. We do this to avoid having an outdated state, and
6575 miscalculating the index for next-generation onion services. Fixes
6576 bug 24977; bugfix on 0.3.2.1-alpha.
6578 o Minor bugfixes (relay):
6579 - Relays now correctly block attempts to re-extend to the previous
6580 relay by Ed25519 identity. Previously they would warn in this
6581 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6584 o Minor bugfixes (testing):
6585 - Fix compilation of the doctests in the Rust crypto crate. Fixes
6586 bug 26415; bugfix on 0.3.4.1-alpha.
6587 - Instead of trying to read the geoip configuration files from
6588 within the unit tests, instead create our own ersatz files with
6589 just enough geoip data in the format we expect. Trying to read
6590 from the source directory created problems on Windows with mingw,
6591 where the build system's paths are not the same as the platform's
6592 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
6593 - Refrain from trying to get an item from an empty smartlist in
6594 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
6595 to catch improper smartlist usage. Furthermore, enable
6596 DEBUG_SMARTLIST globally when build is configured with fragile
6597 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
6600 Changes in version 0.3.3.7 - 2018-06-12
6601 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
6602 fixes for bugs affecting compatibility and stability.
6604 o Directory authority changes:
6605 - Add an IPv6 address for the "dannenberg" directory authority.
6606 Closes ticket 26343.
6608 o Minor features (geoip):
6609 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
6610 Country database. Closes ticket 26351.
6612 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6613 - Work around a change in OpenSSL 1.1.1 where return values that
6614 would previously indicate "no password" now indicate an empty
6615 password. Without this workaround, Tor instances running with
6616 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6617 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6619 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6620 - Silence unused-const-variable warnings in zstd.h with some GCC
6621 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6623 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
6624 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
6625 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
6626 miscounting the total number of circuits for these field values.)
6627 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
6629 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6630 - Prevent a possible out-of-bounds smartlist read in
6631 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6633 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
6634 - Only select relays when they have the descriptors we prefer to use
6635 for them. This change fixes a bug where we could select a relay
6636 because it had _some_ descriptor, but reject it later with a
6637 nonfatal assertion error because it didn't have the exact one we
6638 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
6641 Changes in version 0.3.4.2-alpha - 2018-06-12
6642 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
6643 release, and forward-ports an authority-only security fix from 0.3.3.6.
6645 o Directory authority changes:
6646 - Add an IPv6 address for the "dannenberg" directory authority.
6647 Closes ticket 26343.
6649 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
6650 - Fix a bug that could have allowed an attacker to force a directory
6651 authority to use up all its RAM by passing it a maliciously
6652 crafted protocol versions string. Fixes bug 25517; bugfix on
6653 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
6655 o Minor features (continuous integration):
6656 - Add the necessary configuration files for continuous integration
6657 testing on Windows, via the Appveyor platform. Closes ticket
6658 25549. Patches from Marcin Cieślak and Isis Lovecruft.
6660 o Minor features (geoip):
6661 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
6662 Country database. Closes ticket 26351.
6664 o Minor bugfixes (compatibility, openssl):
6665 - Work around a change in OpenSSL 1.1.1 where return values that
6666 would previously indicate "no password" now indicate an empty
6667 password. Without this workaround, Tor instances running with
6668 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6669 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6671 o Minor bugfixes (compilation):
6672 - Silence unused-const-variable warnings in zstd.h with some GCC
6673 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6674 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
6675 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
6676 - Avoid a compiler warning when casting the return value of
6677 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
6678 26283; bugfix on 0.2.4.10-alpha.
6680 o Minor bugfixes (control port):
6681 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
6682 CIRC_BW events. Previously, such cells were counted entirely in
6683 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
6686 o Minor bugfixes (controller):
6687 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
6688 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
6689 miscounting the total number of circuits for these field values.)
6690 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
6692 o Minor bugfixes (hardening):
6693 - Prevent a possible out-of-bounds smartlist read in
6694 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6696 o Minor bugfixes (onion services):
6697 - Fix a bug that blocked the creation of ephemeral v3 onion
6698 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
6700 o Minor bugfixes (test coverage tools):
6701 - Update our "cov-diff" script to handle output from the latest
6702 version of gcov, and to remove extraneous timestamp information
6703 from its output. Fixes bugs 26101 and 26102; bugfix
6707 Changes in version 0.3.3.6 - 2018-05-22
6708 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
6709 backports several important fixes from the 0.3.4.1-alpha.
6711 The Tor 0.3.3 series includes controller support and other
6712 improvements for v3 onion services, official support for embedding Tor
6713 within other applications, and our first non-trivial module written in
6714 the Rust programming language. (Rust is still not enabled by default
6715 when building Tor.) And as usual, there are numerous other smaller
6716 bugfixes, features, and improvements.
6718 Below are the changes since 0.3.3.5-rc. For a list of all changes
6719 since 0.3.2.10, see the ReleaseNotes file.
6721 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
6722 - When directory authorities read a zero-byte bandwidth file, they
6723 would previously log a warning with the contents of an
6724 uninitialised buffer. They now log a warning about the empty file
6725 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6727 o Major bugfixes (security, directory authority, denial-of-service):
6728 - Fix a bug that could have allowed an attacker to force a directory
6729 authority to use up all its RAM by passing it a maliciously
6730 crafted protocol versions string. Fixes bug 25517; bugfix on
6731 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
6733 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
6734 - Avoid a rare assertion failure in the circuit build timeout code
6735 if we fail to allow any circuits to actually complete. Fixes bug
6736 25733; bugfix on 0.2.2.2-alpha.
6738 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6739 - Avoid a crash when testing router reachability on a router that
6740 could have an ed25519 ID, but which does not. Fixes bug 25415;
6741 bugfix on 0.3.3.2-alpha.
6743 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6744 - Correctly detect when onion services get disabled after HUP. Fixes
6745 bug 25761; bugfix on 0.3.2.1.
6747 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
6748 - Impose a limit on circuit cell queue size. The limit can be
6749 controlled by a consensus parameter. Fixes bug 25226; bugfix
6752 o Minor features (compatibility, backport from 0.3.4.1-alpha):
6753 - Avoid some compilation warnings with recent versions of LibreSSL.
6754 Closes ticket 26006.
6756 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6757 - Our .travis.yml configuration now includes support for testing the
6758 results of "make distcheck". (It's not uncommon for "make check"
6759 to pass but "make distcheck" to fail.) Closes ticket 25814.
6760 - Our Travis CI configuration now integrates with the Coveralls
6761 coverage analysis tool. Closes ticket 25818.
6763 o Minor features (geoip):
6764 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
6765 database. Closes ticket 26104.
6767 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6768 - Don't consider Tor running as a client if the ControlPort is open,
6769 but no actual client ports are open. Fixes bug 26062; bugfix
6772 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6773 - Upon receiving a malformed connected cell, stop processing the
6774 cell immediately. Previously we would mark the connection for
6775 close, but continue processing the cell as if the connection were
6776 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6778 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
6779 - Stop saying in the manual that clients cache ipv4 dns answers from
6780 exit relays. We haven't used them since 0.2.6.3-alpha, and in
6781 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
6782 we forgot to say so in the man page. Fixes bug 26052; bugfix
6785 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6786 - Allow the nanosleep() system call, which glibc uses to implement
6787 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6789 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6790 - Fix a memory leak when a v3 onion service is configured and gets a
6791 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6792 - When parsing the descriptor signature, look for the token plus an
6793 extra white-space at the end. This is more correct but also will
6794 allow us to support new fields that might start with "signature".
6795 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6797 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6798 - Avoid a crash when running with DirPort set but ORPort turned off.
6799 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6801 o Documentation (backport from 0.3.4.1-alpha):
6802 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
6803 ticket 25857. Patch from "CTassisF".
6806 Changes in version 0.3.4.1-alpha - 2018-05-17
6807 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
6808 includes refactoring to begin reducing Tor's binary size and idle CPU
6809 usage on mobile, along with prep work for new bandwidth scanners,
6810 improvements to the experimental "vanguards" feature, and numerous
6811 other small features and bugfixes.
6813 o New system requirements:
6814 - Tor no longer tries to support old operating systems without
6815 mmap() or some local equivalent. Apparently, compilation on such
6816 systems has been broken for some time, without anybody noticing or
6817 complaining. Closes ticket 25398.
6819 o Major feature (directory authority, modularization):
6820 - The directory authority subsystem has been modularized. The code
6821 is now located in src/or/dirauth/, and is compiled in by default.
6822 To disable the module, the configure option
6823 --disable-module-dirauth has been added. This module may be
6824 disabled by default in some future release. Closes ticket 25610.
6826 o Major features (main loop, CPU usage):
6827 - When Tor is disabled (via DisableNetwork or via hibernation), it
6828 no longer needs to run any per-second events. This change should
6829 make it easier for mobile applications to disable Tor while the
6830 device is sleeping, or Tor is not running. Closes ticket 26063.
6831 - Tor no longer enables all of its periodic events by default.
6832 Previously, Tor would enable all possible main loop events,
6833 regardless of whether it needed them. Furthermore, many of these
6834 events are now disabled with Tor is hibernating or DisableNetwork
6835 is set. This is a big step towards reducing client CPU usage by
6836 reducing the amount of wake-ups the daemon does. Closes ticket
6838 - The bandwidth-limitation logic has been refactored so that
6839 bandwidth calculations are performed on-demand, rather than every
6840 TokenBucketRefillInterval milliseconds. This change should improve
6841 the granularity of our bandwidth calculations, and limit the
6842 number of times that the Tor process needs to wake up when it is
6843 idle. Closes ticket 25373.
6844 - Move responsibility for many operations from a once-per-second
6845 callback to a callback that is only scheduled as needed. Moving
6846 this functionality has allowed us to disable the callback when
6847 Tor's network is disabled. Once enough items are removed from our
6848 once-per-second callback, we can eliminate it entirely to conserve
6849 CPU when idle. The functionality removed includes: closing
6850 connections, circuits, and channels (ticket 25932); consensus
6851 voting (25937); flushing log callbacks (25951); honoring delayed
6852 SIGNEWNYM requests (25949); rescanning the consensus cache
6853 (25931); saving the state file to disk (25948); warning relay
6854 operators about unreachable ports (25952); and keeping track of
6855 Tor's uptime (26009).
6857 o Major bugfixes (directory authorities, security):
6858 - When directory authorities read a zero-byte bandwidth file, they
6859 would previously log a warning with the contents of an
6860 uninitialised buffer. They now log a warning about the empty file
6861 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6863 o Major bugfixes (crash):
6864 - Avoid a rare assertion failure in the circuit build timeout code
6865 if we fail to allow any circuits to actually complete. Fixes bug
6866 25733; bugfix on 0.2.2.2-alpha.
6868 o Major bugfixes (directory authority):
6869 - Avoid a crash when testing router reachability on a router that
6870 could have an ed25519 ID, but which does not. Fixes bug 25415;
6871 bugfix on 0.3.3.2-alpha.
6873 o Major bugfixes (onion service):
6874 - Correctly detect when onion services get disabled after HUP. Fixes
6875 bug 25761; bugfix on 0.3.2.1.
6877 o Major bugfixes (protover, voting):
6878 - Revise Rust implementation of protover to use a more memory-
6879 efficient voting algorithm and corresponding data structures, thus
6880 avoiding a potential (but small impact) DoS attack where specially
6881 crafted protocol strings would expand to several potential
6882 megabytes in memory. In the process, several portions of code were
6883 revised to be methods on new, custom types, rather than functions
6884 taking interchangeable types, thus increasing type safety of the
6885 module. Custom error types and handling were added as well, in
6886 order to facilitate better error dismissal/handling in outside
6887 crates and avoid mistakenly passing an internal error string to C
6888 over the FFI boundary. Many tests were added, and some previous
6889 differences between the C and Rust implementations have been
6890 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
6892 o Major bugfixes (relay, denial of service):
6893 - Impose a limit on circuit cell queue size. The limit can be
6894 controlled by a consensus parameter. Fixes bug 25226; bugfix
6897 o Minor features (accounting):
6898 - When Tor becomes dormant, it now uses a scheduled event to wake up
6899 at the right time. Previously, we would use the per-second timer
6900 to check whether to wake up, but we no longer have any per-second
6901 timers enabled when the network is disabled. Closes ticket 26064.
6903 o Minor features (code quality):
6904 - Add optional spell-checking for the Tor codebase, using the
6905 "misspell" program. To use this feature, run "make check-typos".
6906 Closes ticket 25024.
6908 o Minor features (compatibility):
6909 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
6910 the no-deprecated option, and builds correctly with them. Closes
6911 tickets 19429, 19981, and 25353.
6912 - Avoid some compilation warnings with recent versions of LibreSSL.
6913 Closes ticket 26006.
6915 o Minor features (compression, zstd):
6916 - When running with zstd, Tor now considers using advanced functions
6917 that the zstd maintainers have labeled as potentially unstable. To
6918 prevent breakage, Tor will only use this functionality when the
6919 runtime version of the zstd library matches the version with which
6920 Tor was compiled. Closes ticket 25162.
6922 o Minor features (configuration):
6923 - The "DownloadSchedule" options have been renamed to end with
6924 "DownloadInitialDelay". The old names are still allowed, but will
6925 produce a warning. Comma-separated lists are still permitted for
6926 these options, but all values after the first are ignored (as they
6927 have been since 0.2.9). Closes ticket 23354.
6929 o Minor features (continuous integration):
6930 - Our .travis.yml configuration now includes support for testing the
6931 results of "make distcheck". (It's not uncommon for "make check"
6932 to pass but "make distcheck" to fail.) Closes ticket 25814.
6933 - Our Travis CI configuration now integrates with the Coveralls
6934 coverage analysis tool. Closes ticket 25818.
6936 o Minor features (control port):
6937 - Introduce GETINFO "current-time/{local,utc}" to return the local
6938 and UTC times respectively in ISO format. This helps a controller
6939 like Tor Browser detect a time-related error. Closes ticket 25511.
6940 Patch by Neel Chauhan.
6941 - Introduce new fields to the CIRC_BW event. There are two new
6942 fields in each of the read and written directions. The DELIVERED
6943 fields report the total valid data on the circuit, as measured by
6944 the payload sizes of verified and error-checked relay command
6945 cells. The OVERHEAD fields report the total unused bytes in each
6946 of these cells. Closes ticket 25903.
6948 o Minor features (directory authority):
6949 - Directory authorities now open their key-pinning files as O_SYNC,
6950 to limit their chances of accidentally writing partial lines.
6951 Closes ticket 23909.
6953 o Minor features (directory authority, forward compatibility):
6954 - Make the lines of the measured bandwidth file able to contain
6955 their entries in any order. Previously, the node_id entry needed
6956 to come first. Closes ticket 26004.
6958 o Minor features (entry guards):
6959 - Introduce a new torrc option NumPrimaryGuards for controlling the
6960 number of primary guards. Closes ticket 25843.
6962 o Minor features (geoip):
6963 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
6964 database. Closes ticket 26104.
6966 o Minor features (performance):
6967 - Avoid a needless call to malloc() when processing an incoming
6968 relay cell. Closes ticket 24914.
6969 - Make our timing-wheel code run a tiny bit faster on 32-bit
6970 platforms, by preferring 32-bit math to 64-bit. Closes
6972 - Avoid a needless malloc()/free() pair every time we handle an ntor
6973 handshake. Closes ticket 25150.
6975 o Minor features (testing):
6976 - Add a unit test for voting_schedule_get_start_of_next_interval().
6977 Closes ticket 26014, and helps make unit test coverage
6979 - A new unittests module specifically for testing the functions in
6980 the (new-ish) bridges.c module has been created with new
6981 unittests, raising the code coverage percentages. Closes 25425.
6982 - We now have improved testing for addressmap_get_virtual_address()
6983 function. This should improve our test coverage, and make our test
6984 coverage more deterministic. Closes ticket 25993.
6986 o Minor features (timekeeping, circuit scheduling):
6987 - When keeping track of how busy each circuit have been recently on
6988 a given connection, use coarse-grained monotonic timers rather
6989 than gettimeofday(). This change should marginally increase
6990 accuracy and performance. Implements part of ticket 25927.
6992 o Minor bugfixes (bandwidth management):
6993 - Consider ourselves "low on write bandwidth" if we have exhausted
6994 our write bandwidth some time in the last second. This was the
6995 documented behavior before, but the actual behavior was to change
6996 this value every TokenBucketRefillInterval. Fixes bug 25828;
6997 bugfix on 0.2.3.5-alpha.
6999 o Minor bugfixes (C correctness):
7000 - Add a missing lock acquisition in the shutdown code of the control
7001 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
7002 Coverity; this is CID 1433643.
7004 o Minor bugfixes (circuit path selection):
7005 - Don't count path selection failures as circuit build failures.
7006 This change should eliminate cases where Tor blames its guard or
7007 the network for situations like insufficient microdescriptors
7008 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
7011 o Minor bugfixes (client):
7012 - Don't consider Tor running as a client if the ControlPort is open,
7013 but no actual client ports are open. Fixes bug 26062; bugfix
7016 o Minor bugfixes (code style):
7017 - Fixed multiple includes of transports.h in src/or/connection.c
7018 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
7019 - Remove the unused variable n_possible from the function
7020 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
7022 o Minor bugfixes (control interface):
7023 - Respond with more human-readable error messages to GETINFO exit-
7024 policy/* requests. Also, let controller know if an error is
7025 transient (response code 551) or not (response code 552). Fixes
7026 bug 25852; bugfix on 0.2.8.1-alpha.
7028 o Minor bugfixes (controller):
7029 - Make CIRC_BW event reflect the total of all data sent on a
7030 circuit, including padding and dropped cells. Also fix a mis-
7031 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
7032 bugfix on 0.2.5.2-alpha.
7034 o Minor bugfixes (correctness, client):
7035 - Upon receiving a malformed connected cell, stop processing the cell
7036 immediately. Previously we would mark the connection for close, but
7037 continue processing the cell as if the connection were open. Fixes bug
7038 26072; bugfix on 0.2.4.7-alpha.
7040 o Minor bugfixes (directory client):
7041 - When unverified-consensus is verified, rename it to cached-
7042 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
7043 - Fixed launching a certificate fetch always during the scheduled
7044 periodic consensus fetch by fetching only in those cases when
7045 consensus are waiting for certs. Fixes bug 24740; bugfix
7048 o Minor bugfixes (documentation):
7049 - Stop saying in the manual that clients cache ipv4 dns answers from
7050 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7051 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7052 we forgot to say so in the man page. Fixes bug 26052; bugfix
7055 o Minor bugfixes (error reporting):
7056 - Improve tolerance for directory authorities with skewed clocks.
7057 Previously, an authority with a clock more than 60 seconds ahead
7058 could cause a client with a correct clock to warn that the
7059 client's clock was behind. Now the clocks of a majority of
7060 directory authorities have to be ahead of the client before this
7061 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
7063 o Minor bugfixes (Linux seccomp2 sandbox):
7064 - Allow the nanosleep() system call, which glibc uses to implement
7065 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7067 o Minor bugfixes (onion service):
7068 - Fix a memory leak when a v3 onion service is configured and gets a
7069 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7070 - When parsing the descriptor signature, look for the token plus an
7071 extra white-space at the end. This is more correct but also will
7072 allow us to support new fields that might start with "signature".
7073 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7075 o Minor bugfixes (path selection):
7076 - Only select relays when they have the descriptors we prefer to use
7077 for them. This change fixes a bug where we could select a relay
7078 because it had _some_ descriptor, but reject it later with a
7079 nonfatal assertion error because it didn't have the exact one we
7080 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
7082 o Minor bugfixes (portability):
7083 - Do not align mmap length, as it is not required by POSIX, and the
7084 getpagesize function is deprecated. Fixes bug 25399; bugfix
7087 o Minor bugfixes (portability, FreeBSD):
7088 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
7089 does not stringify on FreeBSD, so we switch to tor_asprintf().
7090 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
7092 o Minor bugfixes (relay statistics):
7093 - When a relay is collecting internal statistics about how many
7094 create cell requests it has seen of each type, accurately count
7095 the requests from relays that temporarily fall out of the
7096 consensus. (To be extra conservative, we were already ignoring
7097 requests from clients in our counts, and we continue ignoring them
7098 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
7100 o Minor bugfixes (relay, crash):
7101 - Avoid a crash when running with DirPort set but ORPort turned off.
7102 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7104 o Minor bugfixes (restart-in-process):
7105 - When shutting down, Tor now clears all the flags in the control.c
7106 module. This should prevent a bug where authentication cookies are
7107 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
7109 o Minor bugfixes (testing):
7110 - When testing workqueue event-cancellation, make sure that we
7111 actually cancel an event, and that cancel each event with equal
7112 probability. (It was previously possible, though extremely
7113 unlikely, for our event-canceling test not to cancel any events.)
7114 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
7115 - Repeat part of the test in test_client_pick_intro() a number of
7116 times, to give it consistent coverage. Fixes bug 25996; bugfix
7118 - Remove randomness from the hs_common/responsible_hsdirs test, so
7119 that it always takes the same path through the function it tests.
7120 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
7121 - Change the behavior of the "channel/outbound" test so that it
7122 never causes a 10-second rollover for the EWMA circuitmux code.
7123 Previously, this behavior would happen randomly, and result in
7124 fluctuating test coverage. Fixes bug 25994; bugfix
7126 - Use X509_new() to allocate certificates that will be freed later
7127 with X509_free(). Previously, some parts of the unit tests had
7128 used tor_malloc_zero(), which is incorrect, and which caused test
7129 failures on Windows when they were built with extra hardening.
7130 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
7132 - While running the circuit_timeout test, fix the PRNG to a
7133 deterministic AES stream, so that the test coverage from this test
7134 will itself be deterministic. Fixes bug 25995; bugfix
7137 o Minor bugfixes (vanguards):
7138 - Allow the last hop in a vanguard circuit to be the same as our
7139 first, to prevent the adversary from influencing guard node choice
7140 by choice of last hop. Also prevent the creation of A - B - A
7141 paths, or A - A paths, which are forbidden by relays. Fixes bug
7142 25870; bugfix on 0.3.3.1-alpha.
7144 o Code simplification and refactoring:
7145 - Remove duplicate code in parse_{c,s}method_line and bootstrap
7146 their functionalities into a single function. Fixes bug 6236;
7147 bugfix on 0.2.3.6-alpha.
7148 - We remove the PortForwarding and PortForwardingHelper options,
7149 related functions, and the port_forwarding tests. These options
7150 were used by the now-deprecated Vidalia to help ordinary users
7151 become Tor relays or bridges. Closes ticket 25409. Patch by
7153 - In order to make the OR and dir checking function in router.c less
7154 confusing we renamed some functions and
7155 consider_testing_reachability() has been split into
7156 router_should_check_reachability() and
7157 router_do_reachability_checks(). Also we improved the documentation
7158 in some functions. Closes ticket 18918.
7159 - Initial work to isolate Libevent usage to a handful of modules in
7160 our codebase, to simplify our call structure, and so that we can
7161 more easily change event loops in the future if needed. Closes
7163 - Introduce a function to call getsockname() and return tor_addr_t,
7164 to save a little complexity throughout the codebase. Closes
7166 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
7167 as hsdir_index is always present. Also, we move hsdir_index_t into
7168 or.h. Closes ticket 23094. Patch by Neel Chauhan.
7169 - Merge functions used for describing nodes and suppress the
7170 functions that do not allocate memory for the output buffer
7171 string. NODE_DESC_BUF_LEN constant and format_node_description()
7172 function cannot be used externally from router.c module anymore.
7173 Closes ticket 25432. Patch by valentecaio.
7174 - Our main loop has been simplified so that all important operations
7175 happen inside events. Previously, some operations had to happen
7176 outside the event loop, to prevent infinite sequences of event
7177 activations. Closes ticket 25374.
7178 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
7179 it in register_intro_circ() and service_intro_point_new(). This
7180 prevents the digest from being re-calculated each time. Closes
7181 ticket 23107. Patch by Neel Chauhan.
7182 - Refactor token-bucket implementations to use a common backend.
7183 Closes ticket 25766.
7184 - Remove extern declaration of stats_n_seconds_working variable from
7185 main, protecting its accesses with get_uptime() and reset_uptime()
7186 functions. Closes ticket 25081, patch by “valentecaio”.
7187 - Remove our previous logic for "cached gettimeofday()" -- our
7188 coarse monotonic timers are fast enough for this purpose, and far
7189 less error-prone. Implements part of ticket 25927.
7190 - Remove the return value for fascist_firewall_choose_address_base(),
7191 and sister functions such as fascist_firewall_choose_address_node()
7192 and fascist_firewall_choose_address_rs(). Also, while we're here,
7193 initialize the ap argument as leaving it uninitialized can pose a
7194 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
7195 - Rename two fields of connection_t struct. timestamp_lastwritten is
7196 renamed to timestamp_last_write_allowed and timestamp_lastread is
7197 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
7199 - Since Tor requires C99, remove our old workaround code for libc
7200 implementations where free(NULL) doesn't work. Closes ticket 24484.
7201 - Use our standard rate-limiting code to deal with excessive
7202 libevent failures, rather than the hand-rolled logic we had
7203 before. Closes ticket 26016.
7204 - We remove the return value of node_get_prim_orport() and
7205 node_get_prim_dirport(), and introduce node_get_prim_orport() in
7206 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
7207 check for a null address. Closes ticket 23873. Patch by
7209 - We switch to should_record_bridge_info() in
7210 geoip_note_client_seen() and options_need_geoip_info() instead of
7211 accessing the configuration values directly. Fixes bug 25290;
7212 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
7214 o Deprecated features:
7215 - As we are not recommending 0.2.5 anymore, we require relays that
7216 once had an ed25519 key associated with their RSA key to always
7217 have that key, instead of allowing them to drop back to a version
7218 that didn't support ed25519. This means they need to use a new RSA
7219 key if they want to downgrade to an older version of tor without
7220 ed25519. Closes ticket 20522.
7223 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7224 ticket 25857. Patch from "CTassisF".
7227 - Directory authorities will no longer support voting according to
7228 any consensus method before consensus method 25. This keeps
7229 authorities compatible with all authorities running 0.2.9.8 and
7230 later, and does not break any clients or relays. Implements ticket
7231 24378 and proposal 290.
7232 - The PortForwarding and PortForwardingHelper features have been
7233 removed. The reasoning is, given that implementations of NAT
7234 traversal protocols within common consumer grade routers are
7235 frequently buggy, and that the target audience for a NAT punching
7236 feature is a perhaps less-technically-inclined relay operator,
7237 when the helper fails to setup traversal the problems are usually
7238 deep, ugly, and very router specific, making them horrendously
7239 impossible for technical support to reliable assist with, and thus
7240 resulting in frustration all around. Unfortunately, relay
7241 operators who would like to run relays behind NATs will need to
7242 become more familiar with the port forwarding configurations on
7243 their local router. Closes 25409.
7244 - The TestingEnableTbEmptyEvent option has been removed. It was used
7245 in testing simulations to measure how often connection buckets
7246 were emptied, in order to improve our scheduling, but it has not
7247 been actively used in years. Closes ticket 25760.
7248 - The old "round-robin" circuit multiplexer (circuitmux)
7249 implementation has been removed, along with a fairly large set of
7250 code that existed to support it. It has not been the default
7251 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
7252 but it still required an unreasonable amount of memory and CPU.
7253 Closes ticket 25268.
7256 Changes in version 0.3.3.5-rc - 2018-04-15
7257 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
7258 including some that could affect reliability or correctness.
7260 This is the first release candidate in the 0.3.3 series. If we find no
7261 new bugs or regression here, then the first stable 0.3.3 release will
7262 be nearly identical to this one.
7264 o Major bugfixes (security, protover, voting):
7265 - Revise Rust implementation of protover to use a more memory-
7266 efficient voting algorithm and corresponding data structures, thus
7267 avoiding a potential memory-based DoS attack where specially
7268 crafted protocol strings would expand to fill available memory.
7269 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
7271 o Major bugfixes (performance, load balancing):
7272 - Directory authorities no longer vote in favor of the Guard flag
7273 for relays without directory support. Starting in Tor
7274 0.3.0.1-alpha, clients have been avoiding using such relays in the
7275 Guard position, leading to increasingly broken load balancing for
7276 the 5%-or-so of Guards that don't advertise directory support.
7277 Fixes bug 22310; bugfix on 0.3.0.6.
7279 o Minor feature (continuous integration):
7280 - Update the Travis CI configuration to use the stable Rust channel,
7281 now that we have decided to require that. Closes ticket 25714.
7283 o Minor features (config options):
7284 - Change the way the default value for MaxMemInQueues is calculated.
7285 We now use 40% of the hardware RAM if the system has 8 GB RAM or
7286 more. Otherwise we use the former value of 75%. Closes
7289 o Minor features (geoip):
7290 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
7291 Country database. Closes ticket 25718.
7293 o Minor bugfixes (client):
7294 - When using a listed relay as a bridge, and also using
7295 microdescriptors, and considering that relay as a non-bridge in a
7296 circuit, treat its microdescriptor as a valid source of
7297 information about that relay. This change should prevent a non-
7298 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
7300 o Minor bugfixes (controller):
7301 - Restore the correct operation of the RESOLVE command, which had
7302 been broken since we added the ability to enable/disable DNS on
7303 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
7305 o Minor bugfixes (distribution, compilation, rust):
7306 - Build correctly when the rust dependencies submodule is loaded,
7307 but the TOR_RUST_DEPENDENCIES environment variable is not set.
7308 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
7309 - Actually include all of our Rust source in our source
7310 distributions. (Previously, a few of the files were accidentally
7311 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
7313 o Minor bugfixes (documentation):
7314 - Document that the PerConnBW{Rate,Burst} options will fall back to
7315 their corresponding consensus parameters only if those parameters
7316 are set. Previously we had claimed that these values would always
7317 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7318 - Revert a misformatting issue in the ExitPolicy documentation.
7319 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
7321 o Minor bugfixes (exit relay DNS retries):
7322 - Re-attempt timed-out DNS queries 3 times before failure, since our
7323 timeout is 5 seconds for them, but clients wait 10-15. Also allow
7324 slightly more timeouts per resolver when an exit has multiple
7325 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
7327 o Minor bugfixes (onion services):
7328 - Re-instate counting the client HSDir fetch circuits against the
7329 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
7331 - Remove underscores from the _HSLayer{2,3}Nodes options. This
7332 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
7333 Fixes bug 25581; bugfix on 0.3.3.1-alpha
7335 o Code simplification and refactoring:
7336 - Move the list of default directory authorities to its own file.
7337 Closes ticket 24854. Patch by "beastr0".
7339 o Documentation (manpage, denial of service):
7340 - Provide more detail about the denial-of-service options, by
7341 listing each mitigation and explaining how they relate. Closes
7345 Changes in version 0.3.3.4-alpha - 2018-03-29
7346 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
7347 the alpha testing of earlier releases in its series. We are
7348 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
7350 o New system requirements:
7351 - When built with Rust, Tor now depends on version 0.2.39 of the
7352 libc crate. Closes tickets 25310 and 25664.
7354 o Major bugfixes (relay, connection):
7355 - If we have failed to connect to a relay and received a connection
7356 refused, timeout, or similar error (at the TCP level), do not try
7357 that same address/port again for 60 seconds after the failure has
7358 occurred. Fixes bug 24767; bugfix on 0.0.6.
7360 o Minor features (geoip):
7361 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
7362 Country database. Closes ticket 25469.
7364 o Minor features (log messages):
7365 - Improve log message in the out-of-memory handler to include
7366 information about memory usage from the different compression
7367 backends. Closes ticket 25372.
7369 o Minor features (sandbox):
7370 - Explicitly permit the poll() system call when the Linux
7371 seccomp2-based sandbox is enabled: apparently, some versions of
7372 libc use poll() when calling getpwnam(). Closes ticket 25313.
7374 o Minor bugfixes (C correctness):
7375 - Fix a very unlikely (impossible, we believe) null pointer
7376 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7377 Coverity; this is CID 1430932.
7379 o Minor bugfixes (channel, client):
7380 - Better identify client connection when reporting to the geoip
7381 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
7383 o Minor bugfixes (compilation):
7384 - Fix a C99 compliance issue in our configuration script that caused
7385 compilation issues when compiling Tor with certain versions of
7386 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7388 o Minor bugfixes (controller, reliability):
7389 - Avoid a (nonfatal) assertion failure when extending a one-hop
7390 circuit from the controller to become a multihop circuit. Fixes
7391 bug 24903; bugfix on 0.2.5.2-alpha.
7393 o Major bugfixes (networking):
7394 - Tor will no longer reject IPv6 address strings from Tor Browser
7395 when they are passed as hostnames in SOCKS5 requests. Fixes bug
7396 25036, bugfix on Tor 0.3.1.2.
7398 o Minor bugfixes (networking):
7399 - string_is_valid_hostname() will not consider IP strings to be
7400 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
7402 o Minor bugfixes (onion service v3):
7403 - Avoid an assertion failure when the next onion service
7404 descriptor rotation type is out of sync with the consensus's
7405 valid-after time. Instead, log a warning message with extra
7406 information, so we can better hunt down the cause of this
7407 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
7409 o Minor bugfixes (testing):
7410 - Avoid intermittent test failures due to a test that had relied on
7411 onion service introduction point creation finishing within 5
7412 seconds of real clock time. Fixes bug 25450; bugfix
7414 - Rust crates are now automatically detected and tested. Previously,
7415 some crates were not tested by `make test-rust` due to a static
7416 string in the `src/test/test_rust.sh` script specifying which
7417 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
7419 o Minor bugfixes (testing, benchmarks):
7420 - Fix a crash when running benchmark tests on win32 systems. The
7421 crash was due to a mutex that wasn't initialized before logging
7422 and options were initialized. Fixes bug 25479; bugfix
7425 o Minor bugfixes (warnings, ipv6):
7426 - Avoid a bug warning that could occur when trying to connect to a
7427 relay over IPv6. This warning would occur on a Tor instance that
7428 downloads router descriptors, but prefers to use microdescriptors.
7429 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
7431 o Code simplification and refactoring:
7432 - Remove the old (deterministic) directory retry logic entirely:
7433 We've used exponential backoff exclusively for some time. Closes
7437 - Improved the documentation of AccountingStart parameter. Closes
7439 - Update the documentation for "Log" to include the current list of
7440 logging domains. Closes ticket 25378.
7443 Changes in version 0.3.1.10 - 2018-03-03
7444 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
7447 It includes an important security fix for a remote crash attack
7448 against directory authorities, tracked as TROVE-2018-001.
7450 This release also backports our new system for improved resistance to
7451 denial-of-service attacks against relays.
7453 This release also fixes several minor bugs and annoyances from
7456 All directory authorities should upgrade to one of the versions
7457 released today. Relays running 0.3.1.x may wish to update to one of
7458 the versions released today, for the DoS mitigations.
7460 Please note: according to our release calendar, Tor 0.3.1 will no
7461 longer be supported after 1 July 2018. If you will be running Tor
7462 after that date, you should make sure to plan to upgrade to the latest
7463 stable version, or downgrade to 0.2.9 (which will receive long-term
7466 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7467 - Fix a protocol-list handling bug that could be used to remotely crash
7468 directory authorities with a null-pointer exception. Fixes bug 25074;
7469 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7472 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7473 - Give relays some defenses against the recent network overload. We
7474 start with three defenses (default parameters in parentheses).
7475 First: if a single client address makes too many concurrent
7476 connections (>100), hang up on further connections. Second: if a
7477 single client address makes circuits too quickly (more than 3 per
7478 second, with an allowed burst of 90) while also having too many
7479 connections open (3), refuse new create cells for the next while
7480 (1-2 hours). Third: if a client asks to establish a rendezvous
7481 point to you directly, ignore the request. These defenses can be
7482 manually controlled by new torrc options, but relays will also
7483 take guidance from consensus parameters, so there's no need to
7484 configure anything manually. Implements ticket 24902.
7486 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7487 - Update the sandbox rules so that they should now work correctly
7488 with Glibc 2.26. Closes ticket 24315.
7490 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7491 - Fix an "off by 2" error in counting rendezvous failures on the
7492 onion service side. While we thought we would stop the rendezvous
7493 attempt after one failed circuit, we were actually making three
7494 circuit attempts before giving up. Now switch to a default of 2,
7495 and allow the consensus parameter "hs_service_max_rdv_failures" to
7496 override. Fixes bug 24895; bugfix on 0.0.6.
7498 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7499 - Add Link protocol version 5 to the supported protocols list. Fixes
7500 bug 25070; bugfix on 0.3.1.1-alpha.
7502 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7503 - Fix a set of false positives where relays would consider
7504 connections to other relays as being client-only connections (and
7505 thus e.g. deserving different link padding schemes) if those
7506 relays fell out of the consensus briefly. Now we look only at the
7507 initial handshake and whether the connection authenticated as a
7508 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7510 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7511 - Make our OOM handler aware of the geoip client history cache so it
7512 doesn't fill up the memory. This check is important for IPv6 and
7513 our DoS mitigation subsystem. Closes ticket 25122.
7515 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
7516 - Change relay bandwidth reporting stats interval from 4 hours to 24
7517 hours in order to reduce the efficiency of guard discovery
7518 attacks. Fixes ticket 23856.
7520 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7521 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7522 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7523 since they neither disabled TLS 1.3 nor enabled any of the
7524 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7525 Closes ticket 24978.
7527 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
7528 - The fallback directory list has been re-generated based on the
7529 current status of the network. Tor uses fallback directories to
7530 bootstrap when it doesn't yet have up-to-date directory
7531 information. Closes ticket 24801.
7532 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7533 prefer to bootstrap from fallback directory mirrors. This is a
7534 follow-up to 24679, which removed weights from the default
7535 fallbacks. Implements ticket 24681.
7537 o Minor features (geoip):
7538 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7541 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7542 - Use the actual observed address of an incoming relay connection,
7543 not the canonical address of the relay from its descriptor, when
7544 making decisions about how to handle the incoming connection.
7545 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7547 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7548 - Directory authorities, when refusing a descriptor from a rejected
7549 relay, now explicitly tell the relay (in its logs) to set a valid
7550 ContactInfo address and contact the bad-relays@ mailing list.
7551 Fixes bug 25170; bugfix on 0.2.9.1.
7553 o Minor bugfixes (address selection, backport from 0.3.2.9):
7554 - When the fascist_firewall_choose_address_ functions don't find a
7555 reachable address, set the returned address to the null address
7556 and port. This is a precautionary measure, because some callers do
7557 not check the return value. Fixes bug 24736; bugfix
7560 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
7561 - Fetch descriptors aggressively whenever we lack enough to build
7562 circuits, regardless of how many descriptors we are missing.
7563 Previously, we would delay launching the fetch when we had fewer
7564 than 15 missing descriptors, even if some of those descriptors
7565 were blocking circuits from building. Fixes bug 23985; bugfix on
7566 0.1.1.11-alpha. The effects of this bug became worse in
7567 0.3.0.3-alpha, when we began treating missing descriptors from our
7568 primary guards as a reason to delay circuits.
7569 - Don't try fetching microdescriptors from relays that have failed
7570 to deliver them in the past. Fixes bug 23817; bugfix
7573 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
7574 - Fix a signed/unsigned comparison warning introduced by our fix to
7575 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7577 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7578 - Avoid a crash when attempting to use the seccomp2 sandbox together
7579 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
7582 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7583 - Fix a possible crash on malformed consensus. If a consensus had
7584 contained an unparseable protocol line, it could have made clients
7585 and relays crash with a null-pointer exception. To exploit this
7586 issue, however, an attacker would need to be able to subvert the
7587 directory authority system. Fixes bug 25251; bugfix on
7588 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7590 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
7591 - Recover better from empty or corrupt files in the consensus cache
7592 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
7593 - When a consensus diff calculation is only partially successful,
7594 only record the successful parts as having succeeded. Partial
7595 success can happen if (for example) one compression method fails
7596 but the others succeed. Previously we misrecorded all the
7597 calculations as having succeeded, which would later cause a
7598 nonfatal assertion failure. Fixes bug 24086; bugfix
7601 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
7602 - Tor now updates its guard state when it reads a consensus
7603 regardless of whether it's missing descriptors. That makes tor use
7604 its primary guards to fetch descriptors in some edge cases where
7605 it would previously have used fallback directories. Fixes bug
7606 23862; bugfix on 0.3.0.1-alpha.
7608 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
7609 - Don't treat inability to store a cached consensus object as a bug:
7610 it can happen normally when we are out of disk space. Fixes bug
7611 24859; bugfix on 0.3.1.1-alpha.
7613 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
7614 - When queuing DESTROY cells on a channel, only queue the circuit-id
7615 and reason fields: not the entire 514-byte cell. This fix should
7616 help mitigate any bugs or attacks that fill up these queues, and
7617 free more RAM for other uses. Fixes bug 24666; bugfix
7620 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
7621 - When closing a connection via close_connection_immediately(), we
7622 mark it as "not blocked on bandwidth", to prevent later calls from
7623 trying to unblock it, and give it permission to read. This fixes a
7624 backtrace warning that can happen on relays under various
7625 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
7627 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
7628 - When selecting relays by bandwidth, avoid a rounding error that
7629 could sometimes cause load to be imbalanced incorrectly.
7630 Previously, we would always round upwards; now, we round towards
7631 the nearest integer. This had the biggest effect when a relay's
7632 weight adjustments should have given it weight 0, but it got
7633 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7634 - When calculating the fraction of nodes that have descriptors, and
7635 all nodes in the network have zero bandwidths, count the number of
7636 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7637 - Actually log the total bandwidth in compute_weighted_bandwidths().
7638 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7640 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
7641 - Improve the performance of our consensus-diff application code
7642 when Tor is built with the --enable-fragile-hardening option set.
7643 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
7645 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
7646 - Don't exit the Tor process if setrlimit() fails to change the file
7647 limit (which can happen sometimes on some versions of OSX). Fixes
7648 bug 21074; bugfix on 0.0.9pre5.
7650 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
7651 - Fix a bug in the bit-counting parts of our timing-wheel code on
7652 MSVC. (Note that MSVC is still not a supported build platform, due
7653 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
7656 o Minor bugfixes (relay, partial backport):
7657 - Make the internal channel_is_client() function look at what sort
7658 of connection handshake the other side used, rather than whether
7659 the other side ever sent a create_fast cell to us. Backports part
7660 of the fixes from bugs 22805 and 24898.
7662 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7663 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7665 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7666 bugfix on 0.2.9.4-alpha.
7668 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
7669 - Update the "rust dependencies" submodule to be a project-level
7670 repository, rather than a user repository. Closes ticket 25323.
7673 Changes in version 0.2.9.15 - 2018-03-03
7674 Tor 0.2.9.15 backports important security and stability bugfixes from
7677 It includes an important security fix for a remote crash attack
7678 against directory authorities, tracked as TROVE-2018-001.
7680 This release also backports our new system for improved resistance to
7681 denial-of-service attacks against relays.
7683 This release also fixes several minor bugs and annoyances from
7686 All directory authorities should upgrade to one of the versions
7687 released today. Relays running 0.2.9.x may wish to update to one of
7688 the versions released today, for the DoS mitigations.
7690 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7691 - Fix a protocol-list handling bug that could be used to remotely crash
7692 directory authorities with a null-pointer exception. Fixes bug 25074;
7693 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7696 o Major features (denial-of-service mitigation):
7697 - Give relays some defenses against the recent network overload. We
7698 start with three defenses (default parameters in parentheses).
7699 First: if a single client address makes too many concurrent
7700 connections (>100), hang up on further connections. Second: if a
7701 single client address makes circuits too quickly (more than 3 per
7702 second, with an allowed burst of 90) while also having too many
7703 connections open (3), refuse new create cells for the next while
7704 (1-2 hours). Third: if a client asks to establish a rendezvous
7705 point to you directly, ignore the request. These defenses can be
7706 manually controlled by new torrc options, but relays will also
7707 take guidance from consensus parameters, so there's no need to
7708 configure anything manually. Implements ticket 24902.
7710 o Major bugfixes (bootstrapping):
7711 - Fetch descriptors aggressively whenever we lack enough to build
7712 circuits, regardless of how many descriptors we are missing.
7713 Previously, we would delay launching the fetch when we had fewer
7714 than 15 missing descriptors, even if some of those descriptors
7715 were blocking circuits from building. Fixes bug 23985; bugfix on
7716 0.1.1.11-alpha. The effects of this bug became worse in
7717 0.3.0.3-alpha, when we began treating missing descriptors from our
7718 primary guards as a reason to delay circuits.
7720 o Major bugfixes (onion services, retry behavior):
7721 - Fix an "off by 2" error in counting rendezvous failures on the
7722 onion service side. While we thought we would stop the rendezvous
7723 attempt after one failed circuit, we were actually making three
7724 circuit attempts before giving up. Now switch to a default of 2,
7725 and allow the consensus parameter "hs_service_max_rdv_failures" to
7726 override. Fixes bug 24895; bugfix on 0.0.6.
7728 o Minor feature (relay statistics):
7729 - Change relay bandwidth reporting stats interval from 4 hours to 24
7730 hours in order to reduce the efficiency of guard discovery
7731 attacks. Fixes ticket 23856.
7733 o Minor features (compatibility, OpenSSL):
7734 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7735 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7736 since they neither disabled TLS 1.3 nor enabled any of the
7737 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7738 Closes ticket 24978.
7740 o Minor features (denial-of-service avoidance):
7741 - Make our OOM handler aware of the geoip client history cache so it
7742 doesn't fill up the memory. This check is important for IPv6 and
7743 our DoS mitigation subsystem. Closes ticket 25122.
7745 o Minor features (fallback directory mirrors):
7746 - The fallback directory list has been re-generated based on the
7747 current status of the network. Tor uses fallback directories to
7748 bootstrap when it doesn't yet have up-to-date directory
7749 information. Closes ticket 24801.
7750 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7751 prefer to bootstrap from fallback directory mirrors. This is a
7752 follow-up to 24679, which removed weights from the default
7753 fallbacks. Implements ticket 24681.
7755 o Minor features (geoip):
7756 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7759 o Minor features (linux seccomp2 sandbox):
7760 - Update the sandbox rules so that they should now work correctly
7761 with Glibc 2.26. Closes ticket 24315.
7763 o Minor bugfix (channel connection):
7764 - Use the actual observed address of an incoming relay connection,
7765 not the canonical address of the relay from its descriptor, when
7766 making decisions about how to handle the incoming connection.
7767 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7769 o Minor bugfix (directory authority):
7770 - Directory authorities, when refusing a descriptor from a rejected
7771 relay, now explicitly tell the relay (in its logs) to set a valid
7772 ContactInfo address and contact the bad-relays@ mailing list.
7773 Fixes bug 25170; bugfix on 0.2.9.1.
7775 o Minor bugfixes (address selection):
7776 - When the fascist_firewall_choose_address_ functions don't find a
7777 reachable address, set the returned address to the null address
7778 and port. This is a precautionary measure, because some callers do
7779 not check the return value. Fixes bug 24736; bugfix
7782 o Minor bugfixes (compilation):
7783 - Fix a signed/unsigned comparison warning introduced by our fix to
7784 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7786 o Minor bugfixes (control port, linux seccomp2 sandbox):
7787 - Avoid a crash when attempting to use the seccomp2 sandbox together
7788 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
7791 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7792 - Fix a possible crash on malformed consensus. If a consensus had
7793 contained an unparseable protocol line, it could have made clients
7794 and relays crash with a null-pointer exception. To exploit this
7795 issue, however, an attacker would need to be able to subvert the
7796 directory authority system. Fixes bug 25251; bugfix on
7797 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7799 o Minor bugfixes (memory usage):
7800 - When queuing DESTROY cells on a channel, only queue the circuit-id
7801 and reason fields: not the entire 514-byte cell. This fix should
7802 help mitigate any bugs or attacks that fill up these queues, and
7803 free more RAM for other uses. Fixes bug 24666; bugfix
7806 o Minor bugfixes (network layer):
7807 - When closing a connection via close_connection_immediately(), we
7808 mark it as "not blocked on bandwidth", to prevent later calls from
7809 trying to unblock it, and give it permission to read. This fixes a
7810 backtrace warning that can happen on relays under various
7811 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
7813 o Minor bugfixes (OSX):
7814 - Don't exit the Tor process if setrlimit() fails to change the file
7815 limit (which can happen sometimes on some versions of OSX). Fixes
7816 bug 21074; bugfix on 0.0.9pre5.
7818 o Minor bugfixes (path selection):
7819 - When selecting relays by bandwidth, avoid a rounding error that
7820 could sometimes cause load to be imbalanced incorrectly.
7821 Previously, we would always round upwards; now, we round towards
7822 the nearest integer. This had the biggest effect when a relay's
7823 weight adjustments should have given it weight 0, but it got
7824 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7825 - When calculating the fraction of nodes that have descriptors, and
7826 all nodes in the network have zero bandwidths, count the number of
7827 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7828 - Actually log the total bandwidth in compute_weighted_bandwidths().
7829 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7831 o Minor bugfixes (portability, msvc):
7832 - Fix a bug in the bit-counting parts of our timing-wheel code on
7833 MSVC. (Note that MSVC is still not a supported build platform, due
7834 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
7837 o Minor bugfixes (relay):
7838 - Make the internal channel_is_client() function look at what sort
7839 of connection handshake the other side used, rather than whether
7840 the other side ever sent a create_fast cell to us. Backports part
7841 of the fixes from bugs 22805 and 24898.
7843 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7844 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7846 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7847 bugfix on 0.2.9.4-alpha.
7850 Changes in version 0.3.2.10 - 2018-03-03
7851 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
7852 backports a number of bugfixes, including important fixes for security
7855 It includes an important security fix for a remote crash attack
7856 against directory authorities, tracked as TROVE-2018-001.
7858 Additionally, it backports a fix for a bug whose severity we have
7859 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
7860 triggered in order to crash relays with a use-after-free pattern. As
7861 such, we are now tracking that bug as TROVE-2018-002 and
7862 CVE-2018-0491, and backporting it to earlier releases. This bug
7863 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
7866 This release also backports our new system for improved resistance to
7867 denial-of-service attacks against relays.
7869 This release also fixes several minor bugs and annoyances from
7872 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
7873 today, for the fix to TROVE-2018-002. Directory authorities should
7874 also upgrade. (Relays on earlier versions might want to update too for
7875 the DoS mitigations.)
7877 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7878 - Fix a protocol-list handling bug that could be used to remotely crash
7879 directory authorities with a null-pointer exception. Fixes bug 25074;
7880 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7883 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
7884 - Avoid adding the same channel twice in the KIST scheduler pending
7885 list, which could lead to remote denial-of-service use-after-free
7886 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
7888 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7889 - Give relays some defenses against the recent network overload. We
7890 start with three defenses (default parameters in parentheses).
7891 First: if a single client address makes too many concurrent
7892 connections (>100), hang up on further connections. Second: if a
7893 single client address makes circuits too quickly (more than 3 per
7894 second, with an allowed burst of 90) while also having too many
7895 connections open (3), refuse new create cells for the next while
7896 (1-2 hours). Third: if a client asks to establish a rendezvous
7897 point to you directly, ignore the request. These defenses can be
7898 manually controlled by new torrc options, but relays will also
7899 take guidance from consensus parameters, so there's no need to
7900 configure anything manually. Implements ticket 24902.
7902 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7903 - Fix an "off by 2" error in counting rendezvous failures on the
7904 onion service side. While we thought we would stop the rendezvous
7905 attempt after one failed circuit, we were actually making three
7906 circuit attempts before giving up. Now switch to a default of 2,
7907 and allow the consensus parameter "hs_service_max_rdv_failures" to
7908 override. Fixes bug 24895; bugfix on 0.0.6.
7909 - New-style (v3) onion services now obey the "max rendezvous circuit
7910 attempts" logic. Previously they would make as many rendezvous
7911 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
7912 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
7914 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7915 - Add Link protocol version 5 to the supported protocols list. Fixes
7916 bug 25070; bugfix on 0.3.1.1-alpha.
7918 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7919 - Fix a set of false positives where relays would consider
7920 connections to other relays as being client-only connections (and
7921 thus e.g. deserving different link padding schemes) if those
7922 relays fell out of the consensus briefly. Now we look only at the
7923 initial handshake and whether the connection authenticated as a
7924 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7926 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
7927 - The scheduler subsystem was failing to promptly notice changes in
7928 consensus parameters, making it harder to switch schedulers
7929 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
7931 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7932 - Make our OOM handler aware of the geoip client history cache so it
7933 doesn't fill up the memory. This check is important for IPv6 and
7934 our DoS mitigation subsystem. Closes ticket 25122.
7936 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7937 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7938 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7939 since they neither disabled TLS 1.3 nor enabled any of the
7940 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7941 Closes ticket 24978.
7943 o Minor features (geoip):
7944 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7947 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
7948 - When logging a failure to create an onion service's descriptor,
7949 also log what the problem with the descriptor was. Diagnostic
7952 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7953 - Use the actual observed address of an incoming relay connection,
7954 not the canonical address of the relay from its descriptor, when
7955 making decisions about how to handle the incoming connection.
7956 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7958 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7959 - Fix a possible crash on malformed consensus. If a consensus had
7960 contained an unparseable protocol line, it could have made clients
7961 and relays crash with a null-pointer exception. To exploit this
7962 issue, however, an attacker would need to be able to subvert the
7963 directory authority system. Fixes bug 25251; bugfix on
7964 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7966 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7967 - Directory authorities, when refusing a descriptor from a rejected
7968 relay, now explicitly tell the relay (in its logs) to set a valid
7969 ContactInfo address and contact the bad-relays@ mailing list.
7970 Fixes bug 25170; bugfix on 0.2.9.1.
7972 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
7973 - When building with Rust on OSX, link against libresolv, to work
7974 around the issue at https://github.com/rust-lang/rust/issues/46797.
7975 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
7977 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
7978 - Remove a BUG() statement when a client fetches an onion descriptor
7979 that has a lower revision counter than the one in its cache. This
7980 can happen in normal circumstances due to HSDir desync. Fixes bug
7981 24976; bugfix on 0.3.2.1-alpha.
7983 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
7984 - Don't treat inability to store a cached consensus object as a bug:
7985 it can happen normally when we are out of disk space. Fixes bug
7986 24859; bugfix on 0.3.1.1-alpha.
7988 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
7989 - Improve the performance of our consensus-diff application code
7990 when Tor is built with the --enable-fragile-hardening option set.
7991 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
7993 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
7994 - Don't exit the Tor process if setrlimit() fails to change the file
7995 limit (which can happen sometimes on some versions of OSX). Fixes
7996 bug 21074; bugfix on 0.0.9pre5.
7998 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7999 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8001 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8002 bugfix on 0.2.9.4-alpha.
8004 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
8005 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8006 25005; bugfix on 0.3.2.7-rc.
8008 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
8009 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8010 version, when deciding whether a consensus entry can support the
8011 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8012 bugfix on 0.3.2.1-alpha.
8014 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8015 - Update the "rust dependencies" submodule to be a project-level
8016 repository, rather than a user repository. Closes ticket 25323.
8018 o Documentation (backport from 0.3.3.1-alpha)
8019 - Document that operators who run more than one relay or bridge are
8020 expected to set MyFamily and ContactInfo correctly. Closes
8024 Changes in version 0.3.3.3-alpha - 2018-03-03
8025 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
8026 It includes an important security fix for a remote crash attack
8027 against directory authorities tracked as TROVE-2018-001.
8029 Additionally, with this release, we are upgrading the severity of a
8030 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
8031 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
8032 a use-after-free pattern. As such, we are now tracking that bug as
8033 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
8034 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
8036 This release also fixes several minor bugs and annoyances from
8039 Relays running 0.3.2.x should upgrade to one of the versions released
8040 today, for the fix to TROVE-2018-002. Directory authorities should
8041 also upgrade. (Relays on earlier versions might want to update too for
8042 the DoS mitigations.)
8044 o Major bugfixes (denial-of-service, directory authority):
8045 - Fix a protocol-list handling bug that could be used to remotely crash
8046 directory authorities with a null-pointer exception. Fixes bug 25074;
8047 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8050 o Minor features (compatibility, OpenSSL):
8051 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8052 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8053 since they neither disabled TLS 1.3 nor enabled any of the
8054 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8055 Closes ticket 24978.
8057 o Minor features (logging):
8058 - Clarify the log messages produced when getrandom() or a related
8059 entropy-generation mechanism gives an error. Closes ticket 25120.
8061 o Minor features (testing):
8062 - Add a "make test-rust" target to run the rust tests only. Closes
8065 o Minor bugfixes (denial-of-service):
8066 - Fix a possible crash on malformed consensus. If a consensus had
8067 contained an unparseable protocol line, it could have made clients
8068 and relays crash with a null-pointer exception. To exploit this
8069 issue, however, an attacker would need to be able to subvert the
8070 directory authority system. Fixes bug 25251; bugfix on
8071 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8073 o Minor bugfixes (DoS mitigation):
8074 - Add extra safety checks when refilling the circuit creation bucket
8075 to ensure we never set a value above the allowed maximum burst.
8076 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
8077 - When a new consensus arrives, don't update our DoS-mitigation
8078 parameters if we aren't a public relay. Fixes bug 25223; bugfix
8081 o Minor bugfixes (man page, SocksPort):
8082 - Remove dead code from the old "SocksSocket" option, and rename
8083 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
8084 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
8086 o Minor bugfixes (performance):
8087 - Reduce the number of circuits that will be opened at once during
8088 the circuit build timeout phase. This is done by increasing the
8089 idle timeout to 3 minutes, and lowering the maximum number of
8090 concurrent learning circuits to 10. Fixes bug 24769; bugfix
8093 o Minor bugfixes (spec conformance):
8094 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8096 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8097 bugfix on 0.2.9.4-alpha.
8099 o Minor bugfixes (spec conformance, rust):
8100 - Resolve a denial-of-service issue caused by an infinite loop in
8101 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
8102 Also tracked as TROVE-2018-003.
8104 o Code simplification and refactoring:
8105 - Update the "rust dependencies" submodule to be a project-level
8106 repository, rather than a user repository. Closes ticket 25323.
8109 Changes in version 0.3.3.2-alpha - 2018-02-10
8110 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
8111 introduces a mechanism to handle the high loads that many relay
8112 operators have been reporting recently. It also fixes several bugs in
8113 older releases. If this new code proves reliable, we plan to backport
8114 it to older supported release series.
8116 o Major features (denial-of-service mitigation):
8117 - Give relays some defenses against the recent network overload. We
8118 start with three defenses (default parameters in parentheses).
8119 First: if a single client address makes too many concurrent
8120 connections (>100), hang up on further connections. Second: if a
8121 single client address makes circuits too quickly (more than 3 per
8122 second, with an allowed burst of 90) while also having too many
8123 connections open (3), refuse new create cells for the next while
8124 (1-2 hours). Third: if a client asks to establish a rendezvous
8125 point to you directly, ignore the request. These defenses can be
8126 manually controlled by new torrc options, but relays will also
8127 take guidance from consensus parameters, so there's no need to
8128 configure anything manually. Implements ticket 24902.
8130 o Major bugfixes (netflow padding):
8131 - Stop adding unneeded channel padding right after we finish
8132 flushing to a connection that has been trying to flush for many
8133 seconds. Instead, treat all partial or complete flushes as
8134 activity on the channel, which will defer the time until we need
8135 to add padding. This fix should resolve confusing and scary log
8136 messages like "Channel padding timeout scheduled 221453ms in the
8137 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8139 o Major bugfixes (protocol versions):
8140 - Add Link protocol version 5 to the supported protocols list. Fixes
8141 bug 25070; bugfix on 0.3.1.1-alpha.
8143 o Major bugfixes (scheduler, consensus):
8144 - The scheduler subsystem was failing to promptly notice changes in
8145 consensus parameters, making it harder to switch schedulers
8146 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8148 o Minor features (denial-of-service avoidance):
8149 - Make our OOM handler aware of the geoip client history cache so it
8150 doesn't fill up the memory. This check is important for IPv6 and
8151 our DoS mitigation subsystem. Closes ticket 25122.
8153 o Minor features (directory authority):
8154 - When directory authorities are unable to add signatures to a
8155 pending consensus, log the reason why. Closes ticket 24849.
8157 o Minor features (geoip):
8158 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8161 o Minor features (logging, diagnostic):
8162 - When logging a failure to create an onion service's descriptor,
8163 also log what the problem with the descriptor was. Diagnostic for
8166 o Minor bugfix (channel connection):
8167 - Use the actual observed address of an incoming relay connection,
8168 not the canonical address of the relay from its descriptor, when
8169 making decisions about how to handle the incoming connection.
8170 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8172 o Minor bugfix (directory authority):
8173 - Directory authorities, when refusing a descriptor from a rejected
8174 relay, now explicitly tell the relay (in its logs) to set a valid
8175 ContactInfo address and contact the bad-relays@ mailing list.
8176 Fixes bug 25170; bugfix on 0.2.9.1.
8178 o Minor bugfixes (all versions of Tor):
8179 - Use the "misspell" tool to detect and fix typos throughout the
8180 source code. Fixes bug 23650; bugfix on various versions of Tor.
8181 Patch from Deepesh Pathak.
8183 o Minor bugfixes (circuit, cannibalization):
8184 - Don't cannibalize preemptively-built circuits if we no longer
8185 recognize their first hop. This situation can happen if our Guard
8186 relay went off the consensus after the circuit was created. Fixes
8187 bug 24469; bugfix on 0.0.6.
8189 o Minor bugfixes (correctness):
8190 - Remove a nonworking, unnecessary check to see whether a circuit
8191 hop's identity digest was set when the circuit failed. Fixes bug
8192 24927; bugfix on 0.2.4.4-alpha.
8194 o Minor bugfixes (logging):
8195 - Don't treat inability to store a cached consensus object as a bug:
8196 it can happen normally when we are out of disk space. Fixes bug
8197 24859; bugfix on 0.3.1.1-alpha.
8198 - Fix a (mostly harmless) race condition when invoking
8199 LOG_PROTOCOL_WARN message from a subthread while the torrc options
8200 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
8202 o Minor bugfixes (onion services):
8203 - Remove a BUG() statement when a client fetches an onion descriptor
8204 that has a lower revision counter than the one in its cache. This
8205 can happen in normal circumstances due to HSDir desync. Fixes bug
8206 24976; bugfix on 0.3.2.1-alpha.
8207 - If we are configured to offer a single onion service, don't log
8208 long-term established one hop rendezvous points in the heartbeat.
8209 Fixes bug 25116; bugfix on 0.2.9.6-rc.
8211 o Minor bugfixes (performance):
8212 - Avoid calling protocol_list_supports_protocol() from inside tight
8213 loops when running with cached routerinfo_t objects. Instead,
8214 summarize the relevant protocols as flags in the routerinfo_t, as
8215 we do for routerstatus_t objects. This change simplifies our code
8216 a little, and saves a large amount of short-term memory allocation
8217 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
8219 o Minor bugfixes (Rust FFI):
8220 - Fix a minor memory leak which would happen whenever the C code
8221 would call the Rust implementation of
8222 protover_get_supported_protocols(). This was due to the C version
8223 returning a static string, whereas the Rust version newly allocated
8224 a CString to pass across the FFI boundary. Consequently, the C
8225 code was not expecting to need to free() what it was given. Fixes
8226 bug 25127; bugfix on 0.3.2.1-alpha.
8228 o Minor bugfixes (scheduler, KIST):
8229 - Avoid adding the same channel twice in the KIST scheduler pending
8230 list, which would waste CPU cycles. Fixes bug 24700; bugfix
8233 o Minor bugfixes (unit test, monotonic time):
8234 - Increase a constant (1msec to 10msec) in the monotonic time test
8235 that makes sure the nsec/usec/msec times read are synchronized.
8236 This change was needed to accommodate slow systems like armel or
8237 when the clock_gettime() is not a VDSO on the running kernel.
8238 Fixes bug 25113; bugfix on 0.2.9.1.
8240 o Minor bugfixes (v3 onion services):
8241 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8242 version, when deciding whether a consensus entry can support the
8243 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8244 bugfix on 0.3.2.1-alpha.
8246 o Code simplification and refactoring:
8247 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
8249 - Remove a series of counters used to track circuit extend attempts
8250 and connection status but that in reality we aren't using for
8251 anything other than stats logged by a SIGUSR1 signal. Closes
8254 o Documentation (man page):
8255 - The HiddenServiceVersion torrc option accepts only one number:
8256 either version 2 or 3. Closes ticket 25026; bugfix
8260 Changes in version 0.3.3.1-alpha - 2018-01-25
8261 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
8262 several new features to Tor, including several improvements to
8263 bootstrapping, and support for an experimental "vanguards" feature to
8264 resist guard discovery attacks. This series also includes better
8265 support for applications that need to embed Tor or manage v3
8268 o Major features (embedding):
8269 - There is now a documented stable API for programs that need to
8270 embed Tor. See tor_api.h for full documentation and known bugs.
8271 Closes ticket 23684.
8272 - Tor now has support for restarting in the same process.
8273 Controllers that run Tor using the "tor_api.h" interface can now
8274 restart Tor after Tor has exited. This support is incomplete,
8275 however: we fixed crash bugs that prevented it from working at
8276 all, but many bugs probably remain, including a possibility of
8277 security issues. Implements ticket 24581.
8279 o Major features (IPv6, directory documents):
8280 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
8281 consensus. This information makes it easier for IPv6 clients to
8282 bootstrap and choose reachable entry guards. Implements ticket 23826.
8283 - Add consensus method 28, which removes IPv6 ORPorts from
8284 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
8285 are redundant in microdescs. This change will be used by Tor clients
8286 on 0.2.8.x and later. (That is to say, with all Tor clients that
8287 have IPv6 bootstrap and guard support.) Implements ticket 23828.
8288 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
8289 set by different numbers of authorities. Fixes 23870
8292 o Major features (onion service v3, control port):
8293 - The control port now supports commands and events for v3 onion
8294 services. It is now possible to create ephemeral v3 services using
8295 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
8296 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
8297 DEL_ONION) have been extended to support v3 onion services. Closes
8298 ticket 20699; implements proposal 284.
8300 o Major features (onion services):
8301 - Provide torrc options to pin the second and third hops of onion
8302 service circuits to a list of nodes. The option HSLayer2Guards
8303 pins the second hop, and the option HSLayer3Guards pins the third
8304 hop. These options are for use in conjunction with experiments
8305 with "vanguards" for preventing guard enumeration attacks. Closes
8308 o Major features (rust, portability, experimental):
8309 - Tor now ships with an optional implementation of one of its
8310 smaller modules (protover.c) in the Rust programming language. To
8311 try it out, install a Rust build environment, and configure Tor
8312 with "--enable-rust --enable-cargo-online-mode". This should not
8313 cause any user-visible changes, but should help us gain more
8314 experience with Rust, and plan future Rust integration work.
8315 Implementation by Chelsea Komlo. Closes ticket 22840.
8317 o Minor features (storage, configuration):
8318 - Users can store cached directory documents somewhere other than
8319 the DataDirectory by using the CacheDirectory option. Similarly,
8320 the storage location for relay's keys can be overridden with the
8321 KeyDirectory option. Closes ticket 22703.
8323 o Major features (v3 onion services, ipv6):
8324 - When v3 onion service clients send introduce cells, they now
8325 include the IPv6 address of the rendezvous point, if it has one.
8326 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
8327 in future Tor versions, IPv6-only v3 single onion services will be
8328 able to use IPv6 addresses to connect directly to the rendezvous
8329 point. Closes ticket 23577. Patch by Neel Chauhan.
8331 o Major bugfixes (onion services, retry behavior):
8332 - Fix an "off by 2" error in counting rendezvous failures on the
8333 onion service side. While we thought we would stop the rendezvous
8334 attempt after one failed circuit, we were actually making three
8335 circuit attempts before giving up. Now switch to a default of 2,
8336 and allow the consensus parameter "hs_service_max_rdv_failures" to
8337 override. Fixes bug 24895; bugfix on 0.0.6.
8338 - New-style (v3) onion services now obey the "max rendezvous circuit
8339 attempts" logic. Previously they would make as many rendezvous
8340 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8341 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8343 o Major bugfixes (relays):
8344 - Fix a set of false positives where relays would consider
8345 connections to other relays as being client-only connections (and
8346 thus e.g. deserving different link padding schemes) if those
8347 relays fell out of the consensus briefly. Now we look only at the
8348 initial handshake and whether the connection authenticated as a
8349 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8351 o Minor feature (IPv6):
8352 - Make IPv6-only clients wait for microdescs for relays, even if we
8353 were previously using descriptors (or were using them as a bridge)
8354 and have a cached descriptor for them. Implements ticket 23827.
8355 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
8356 them, rather than waiting to download microdescriptors.
8357 Implements ticket 23827.
8359 o Minor features (cleanup):
8360 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
8361 when it stops. Closes ticket 23271.
8363 o Minor features (defensive programming):
8364 - Most of the functions in Tor that free objects have been replaced
8365 with macros that free the objects and set the corresponding
8366 pointers to NULL. This change should help prevent a large class of
8367 dangling pointer bugs. Closes ticket 24337.
8368 - Where possible, the tor_free() macro now only evaluates its input
8369 once. Part of ticket 24337.
8370 - Check that microdesc ed25519 ids are non-zero in
8371 node_get_ed25519_id() before returning them. Implements ticket
8372 24001, patch by "aruna1234".
8374 o Minor features (embedding):
8375 - Tor can now start with a preauthenticated control connection
8376 created by the process that launched it. This feature is meant for
8377 use by programs that want to launch and manage a Tor process
8378 without allowing other programs to manage it as well. For more
8379 information, see the __OwningControllerFD option documented in
8380 control-spec.txt. Closes ticket 23900.
8381 - On most errors that would cause Tor to exit, it now tries to
8382 return from the tor_main() function, rather than calling the
8383 system exit() function. Most users won't notice a difference here,
8384 but it should be significant for programs that run Tor inside
8385 a separate thread: they should now be able to survive Tor's exit
8386 conditions rather than having Tor shut down the entire process.
8387 Closes ticket 23848.
8388 - Applications that want to embed Tor can now tell Tor not to
8389 register any of its own POSIX signal handlers, using the
8390 __DisableSignalHandlers option. Closes ticket 24588.
8392 o Minor features (fallback directory list):
8393 - Avoid selecting fallbacks that change their IP addresses too
8394 often. Select more fallbacks by ignoring the Guard flag, and
8395 allowing lower cutoffs for the Running and V2Dir flags. Also allow
8396 a lower bandwidth, and a higher number of fallbacks per operator
8397 (5% of the list). Implements ticket 24785.
8398 - Update the fallback whitelist and blacklist based on opt-ins and
8399 relay changes. Closes tickets 22321, 24678, 22527, 24135,
8402 o Minor features (fallback directory mirror configuration):
8403 - Add a nickname to each fallback in a C comment. This makes it
8404 easier for operators to find their relays, and allows stem to use
8405 nicknames to identify fallbacks. Implements ticket 24600.
8406 - Add a type and version header to the fallback directory mirror
8407 file. Also add a delimiter to the end of each fallback entry. This
8408 helps external parsers like stem and Relay Search. Implements
8410 - Add an extrainfo cache flag for each fallback in a C comment. This
8411 allows stem to use fallbacks to fetch extra-info documents, rather
8412 than using authorities. Implements ticket 22759.
8413 - Add the generateFallbackDirLine.py script for automatically
8414 generating fallback directory mirror lines from relay fingerprints.
8415 No more typos! Add the lookupFallbackDirContact.py script for
8416 automatically looking up operator contact info from relay
8417 fingerprints. Implements ticket 24706, patch by teor and atagar.
8418 - Reject any fallback directory mirror that serves an expired
8419 consensus. Implements ticket 20942, patch by "minik".
8420 - Remove commas and equals signs from external string inputs to the
8421 fallback list. This avoids format confusion attacks. Implements
8423 - Remove the "weight=10" line from fallback directory mirror
8424 entries. Ticket 24681 will maintain the current fallback weights
8425 by changing Tor's default fallback weight to 10. Implements
8427 - Stop logging excessive information about fallback netblocks.
8428 Implements ticket 24791.
8430 o Minor features (forward-compatibility):
8431 - If a relay supports some link authentication protocol that we do
8432 not recognize, then include that relay's ed25519 key when telling
8433 other relays to extend to it. Previously, we treated future
8434 versions as if they were too old to support ed25519 link
8435 authentication. Closes ticket 20895.
8437 o Minor features (heartbeat):
8438 - Add onion service information to our heartbeat logs, displaying
8439 stats about the activity of configured onion services. Closes
8442 o Minor features (instrumentation, development):
8443 - Add the MainloopStats option to allow developers to get
8444 instrumentation information from the main event loop via the
8445 heartbeat messages. We hope to use this to improve Tor's behavior
8446 when it's trying to sleep. Closes ticket 24605.
8448 o Minor features (log messages):
8449 - Improve a warning message that happens when we fail to re-parse an
8450 old router because of an expired certificate. Closes ticket 20020.
8451 - Make the log more quantitative when we hit MaxMemInQueues
8452 threshold exposing some values. Closes ticket 24501.
8454 o Minor features (logging, android):
8455 - Added support for the Android logging subsystem. Closes
8458 o Minor features (performance):
8459 - Support predictive circuit building for onion service circuits
8460 with multiple layers of guards. Closes ticket 23101.
8461 - Use stdatomic.h where available, rather than mutexes, to implement
8462 atomic_counter_t. Closes ticket 23953.
8464 o Minor features (performance, 32-bit):
8465 - Improve performance on 32-bit systems by avoiding 64-bit division
8466 when calculating the timestamp in milliseconds for channel padding
8467 computations. Implements ticket 24613.
8468 - Improve performance on 32-bit systems by avoiding 64-bit division
8469 when timestamping cells and buffer chunks for OOM calculations.
8470 Implements ticket 24374.
8472 o Minor features (performance, OSX, iOS):
8473 - Use the mach_approximate_time() function (when available) to
8474 implement coarse monotonic time. Having a coarse time function
8475 should avoid a large number of system calls, and improve
8476 performance slightly, especially under load. Closes ticket 24427.
8478 o Minor features (performance, windows):
8479 - Improve performance on Windows Vista and Windows 7 by adjusting
8480 TCP send window size according to the recommendation from
8481 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
8484 o Major features (relay):
8485 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
8486 operator to use a more reasonable ("reduced") exit policy, rather
8487 than the default one. If you want to run an exit node without
8488 thinking too hard about which ports to allow, this one is for you.
8489 Closes ticket 13605. Patch from Neel Chauhan.
8491 o Minor features (testing, debugging, embedding):
8492 - For development purposes, Tor now has a mode in which it runs for
8493 a few seconds, then stops, and starts again without exiting the
8494 process. This mode is meant to help us debug various issues with
8495 ticket 23847. To use this feature, compile with
8496 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
8497 environment variable. This is expected to crash a lot, and is
8498 really meant for developers only. It will likely be removed in a
8499 future release. Implements ticket 24583.
8501 o Minor bugfix (network IPv6 test):
8502 - Tor's test scripts now check if "ping -6 ::1" works when the user
8503 runs "make test-network-all". Fixes bug 24677; bugfix on
8504 0.2.9.3-alpha. Patch by "ffmancera".
8506 o Minor bugfixes (build, rust):
8507 - Fix output of autoconf checks to display success messages for Rust
8508 dependencies and a suitable rustc compiler version. Fixes bug
8509 24612; bugfix on 0.3.1.3-alpha.
8510 - When building with Rust on OSX, link against libresolv, to work
8511 around the issue at https://github.com/rust-lang/rust/issues/46797.
8512 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8513 - Don't pass the --quiet option to cargo: it seems to suppress some
8514 errors, which is not what we want to do when building. Fixes bug
8515 24518; bugfix on 0.3.1.7.
8516 - Build correctly when building from outside Tor's source tree with
8517 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
8520 o Minor bugfixes (directory authorities, IPv6):
8521 - When creating a routerstatus (vote) from a routerinfo (descriptor),
8522 set the IPv6 address to the unspecified IPv6 address, and
8523 explicitly initialize the port to zero. Fixes bug 24488; bugfix
8526 o Minor bugfixes (fallback directory mirrors):
8527 - Make updateFallbackDirs.py search harder for python. (Some OSs
8528 don't put it in /usr/bin.) Fixes bug 24708; bugfix
8531 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
8532 - When hibernating, close connections normally and allow them to
8533 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
8535 - Do not attempt to launch self-reachability tests when entering
8536 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8537 - Resolve several bugs related to descriptor fetching on bridge
8538 clients with bandwidth accounting enabled. (This combination is
8539 not recommended!) Fixes a case of bug 12062; bugfix
8541 - When hibernating, do not attempt to launch DNS checks. Fixes a
8542 case of bug 12062; bugfix on 0.1.2.2-alpha.
8543 - When hibernating, do not try to upload or download descriptors.
8544 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8546 o Minor bugfixes (IPv6, bridges):
8547 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
8548 bugfix on 0.2.8.2-alpha.
8549 - Tor now sets IPv6 address in the routerstatus as well as in the
8550 router descriptors when updating addresses for a bridge. Closes
8551 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
8553 o Minor bugfixes (linux seccomp2 sandbox):
8554 - When running with the sandbox enabled, reload configuration files
8555 correctly even when %include was used. Previously we would crash.
8556 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
8558 o Minor bugfixes (memory leaks):
8559 - Avoid possible at-exit memory leaks related to use of Libevent's
8560 event_base_once() function. (This function tends to leak memory if
8561 the event_base is closed before the event fires.) Fixes bug 24584;
8562 bugfix on 0.2.8.1-alpha.
8563 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
8566 o Minor bugfixes (OSX):
8567 - Don't exit the Tor process if setrlimit() fails to change the file
8568 limit (which can happen sometimes on some versions of OSX). Fixes
8569 bug 21074; bugfix on 0.0.9pre5.
8571 o Minor bugfixes (performance, fragile-hardening):
8572 - Improve the performance of our consensus-diff application code
8573 when Tor is built with the --enable-fragile-hardening option set.
8574 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8576 o Minor bugfixes (performance, timeouts):
8577 - Consider circuits for timeout as soon as they complete a hop. This
8578 is more accurate than applying the timeout in
8579 circuit_expire_building() because that function is only called
8580 once per second, which is now too slow for typical timeouts on the
8581 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
8582 - Use onion service circuits (and other circuits longer than 3 hops)
8583 to calculate a circuit build timeout. Previously, Tor only
8584 calculated its build timeout based on circuits that planned to be
8585 exactly 3 hops long. With this change, we include measurements
8586 from all circuits at the point where they complete their third
8587 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
8589 o Minor bugfixes (testing):
8590 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
8591 bugfix on 0.2.3.1-alpha.
8592 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8593 25005; bugfix on 0.3.2.7-rc.
8595 o Code simplification and refactoring:
8596 - Remove /usr/athena from search path in configure.ac. Closes
8598 - Remove duplicate code in node_has_curve25519_onion_key() and
8599 node_get_curve25519_onion_key(), and add a check for a zero
8600 microdesc curve25519 onion key. Closes ticket 23966, patch by
8601 "aruna1234" and teor.
8602 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
8603 memory allocations with large numbers of OR connections (e.g.
8604 relays). Closes ticket 24119.
8605 - Separate the function that deletes ephemeral files when Tor
8607 - Small changes to Tor's buf_t API to make it suitable for use as a
8608 general-purpose safe string constructor. Closes ticket 22342.
8609 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
8610 avoid source code identifier confusion. Closes ticket 24467.
8611 - The tor_git_revision[] constant no longer needs to be redeclared
8612 by everything that links against the rest of Tor. Done as part of
8613 ticket 23845, to simplify our external API.
8614 - We make extend_info_from_node() use node_get_curve25519_onion_key()
8615 introduced in ticket 23577 to access the curve25519 public keys
8616 rather than accessing it directly. Closes ticket 23760. Patch by
8618 - Add a function to log channels' scheduler state changes to aid
8619 debugging efforts. Closes ticket 24531.
8622 - Add documentation on how to build tor with Rust dependencies
8623 without having to be online. Closes ticket 22907; bugfix
8625 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
8626 traffic. Closes ticket 24318.
8627 - Document that OutboundBindAddress doesn't apply to DNS requests.
8628 Closes ticket 22145. Patch from Aruna Maurya.
8629 - Document that operators who run more than one relay or bridge are
8630 expected to set MyFamily and ContactInfo correctly. Closes
8633 o Code simplification and refactoring (channels):
8634 - Remove the incoming and outgoing channel queues. These were never
8635 used, but still took up a step in our fast path.
8636 - The majority of the channel unit tests have been rewritten and the
8637 code coverage has now been raised to 83.6% for channel.c. Closes
8639 - Remove other dead code from the channel subsystem: All together,
8640 this cleanup has removed more than 1500 lines of code overall and
8641 adding very little except for unit test.
8643 o Code simplification and refactoring (circuit rendezvous):
8644 - Split the client-side rendezvous circuit lookup into two
8645 functions: one that returns only established circuits and another
8646 that returns all kinds of circuits. Closes ticket 23459.
8648 o Code simplification and refactoring (controller):
8649 - Make most of the variables in networkstatus_getinfo_by_purpose()
8650 const. Implements ticket 24489.
8653 Changes in version 0.3.2.9 - 2018-01-09
8654 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
8656 The 0.3.2 series includes our long-anticipated new onion service
8657 design, with numerous security features. (For more information, see
8658 our blog post at https://blog.torproject.org/fall-harvest.) We also
8659 have a new circuit scheduler algorithm for improved performance on
8660 relays everywhere (see https://blog.torproject.org/kist-and-tell),
8661 along with many smaller features and bugfixes.
8663 Per our stable release policy, we plan to support each stable release
8664 series for at least the next nine months, or for three months after
8665 the first stable release of the next series: whichever is longer. If
8666 you need a release with long-term support, we recommend that you stay
8667 with the 0.2.9 series.
8669 Below is a list of the changes since 0.3.2.8-rc. For a list of all
8670 changes since 0.3.1, see the ReleaseNotes file.
8672 o Minor features (fallback directory mirrors):
8673 - The fallback directory list has been re-generated based on the
8674 current status of the network. Tor uses fallback directories to
8675 bootstrap when it doesn't yet have up-to-date directory
8676 information. Closes ticket 24801.
8677 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8678 prefer to bootstrap from fallback directory mirrors. This is a
8679 follow-up to 24679, which removed weights from the default
8680 fallbacks. Implements ticket 24681.
8682 o Minor features (geoip):
8683 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
8686 o Minor bugfixes (address selection):
8687 - When the fascist_firewall_choose_address_ functions don't find a
8688 reachable address, set the returned address to the null address
8689 and port. This is a precautionary measure, because some callers do
8690 not check the return value. Fixes bug 24736; bugfix
8693 o Minor bugfixes (compilation):
8694 - Resolve a few shadowed-variable warnings in the onion service
8695 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
8697 o Minor bugfixes (portability, msvc):
8698 - Fix a bug in the bit-counting parts of our timing-wheel code on
8699 MSVC. (Note that MSVC is still not a supported build platform, due
8700 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8704 Changes in version 0.3.2.8-rc - 2017-12-21
8705 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
8706 schedulers that had led servers under heavy load to overload their
8707 outgoing connections. All relay operators running earlier 0.3.2.x
8708 versions should upgrade. This version also includes a mitigation for
8709 over-full DESTROY queues leading to out-of-memory conditions: if it
8710 works, we will soon backport it to earlier release series.
8712 This is the second release candidate in the 0.3.2 series. If we find
8713 no new bugs or regression here, then the first stable 0.3.2 release
8714 will be nearly identical to this.
8716 o Major bugfixes (KIST, scheduler):
8717 - The KIST scheduler did not correctly account for data already
8718 enqueued in each connection's send socket buffer, particularly in
8719 cases when the TCP/IP congestion window was reduced between
8720 scheduler calls. This situation lead to excessive per-connection
8721 buffering in the kernel, and a potential memory DoS. Fixes bug
8722 24665; bugfix on 0.3.2.1-alpha.
8724 o Minor features (geoip):
8725 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
8728 o Minor bugfixes (hidden service v3):
8729 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
8730 the probability of reaching a service for a client missing
8731 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
8733 o Minor bugfixes (memory usage):
8734 - When queuing DESTROY cells on a channel, only queue the circuit-id
8735 and reason fields: not the entire 514-byte cell. This fix should
8736 help mitigate any bugs or attacks that fill up these queues, and
8737 free more RAM for other uses. Fixes bug 24666; bugfix
8740 o Minor bugfixes (scheduler, KIST):
8741 - Use a sane write limit for KISTLite when writing onto a connection
8742 buffer instead of using INT_MAX and shoving as much as it can.
8743 Because the OOM handler cleans up circuit queues, we are better
8744 off at keeping them in that queue instead of the connection's
8745 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
8748 Changes in version 0.3.2.7-rc - 2017-12-14
8749 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
8750 including some that could affect reliability or correctness.
8752 This is the first release candidate in the 0.3.2 series. If we find no
8753 new bugs or regression here, then the first stable 0.3.2. release will
8754 be nearly identical to this.
8756 o Major bugfixes (circuit prediction):
8757 - Fix circuit prediction logic so that a client doesn't treat a port
8758 as being "handled" by a circuit if that circuit already has
8759 isolation settings on it. This change should make Tor clients more
8760 responsive by improving their chances of having a pre-created
8761 circuit ready for use when a request arrives. Fixes bug 18859;
8762 bugfix on 0.2.3.3-alpha.
8764 o Minor features (logging):
8765 - Provide better warnings when the getrandom() syscall fails. Closes
8768 o Minor features (portability):
8769 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
8770 (It doesn't yet work with the sandbox enabled.) Closes
8773 o Minor bugfixes (bridge clients, bootstrap):
8774 - Retry directory downloads when we get our first bridge descriptor
8775 during bootstrap or while reconnecting to the network. Keep
8776 retrying every time we get a bridge descriptor, until we have a
8777 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
8778 - Stop delaying bridge descriptor fetches when we have cached bridge
8779 descriptors. Instead, only delay bridge descriptor fetches when we
8780 have at least one reachable bridge. Fixes part of bug 24367;
8781 bugfix on 0.2.0.3-alpha.
8782 - Stop delaying directory fetches when we have cached bridge
8783 descriptors. Instead, only delay bridge descriptor fetches when
8784 all our bridges are definitely unreachable. Fixes part of bug
8785 24367; bugfix on 0.2.0.3-alpha.
8787 o Minor bugfixes (compilation):
8788 - Fix a signed/unsigned comparison warning introduced by our fix to
8789 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8791 o Minor bugfixes (correctness):
8792 - Fix several places in our codebase where a C compiler would be
8793 likely to eliminate a check, based on assuming that undefined
8794 behavior had not happened elsewhere in the code. These cases are
8795 usually a sign of redundant checking or dubious arithmetic. Found
8796 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
8797 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
8800 o Minor bugfixes (onion service v3):
8801 - Fix a race where an onion service would launch a new intro circuit
8802 after closing an old one, but fail to register it before freeing
8803 the previously closed circuit. This bug was making the service
8804 unable to find the established intro circuit and thus not upload
8805 its descriptor, thus making a service unavailable for up to 24
8806 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
8808 o Minor bugfixes (scheduler, KIST):
8809 - Properly set the scheduler state of an unopened channel in the
8810 KIST scheduler main loop. This prevents a harmless but annoying
8811 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
8812 - Avoid a possible integer overflow when computing the available
8813 space on the TCP buffer of a channel. This had no security
8814 implications; but could make KIST allow too many cells on a
8815 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
8816 - Downgrade to "info" a harmless warning about the monotonic time
8817 moving backwards: This can happen on platform not supporting
8818 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
8821 Changes in version 0.3.2.6-alpha - 2017-12-01
8822 This version of Tor is the latest in the 0.3.2 alpha series. It
8823 includes fixes for several important security issues. All Tor users
8824 should upgrade to this release, or to one of the other releases coming
8827 o Major bugfixes (security):
8828 - Fix a denial of service bug where an attacker could use a
8829 malformed directory object to cause a Tor instance to pause while
8830 OpenSSL would try to read a passphrase from the terminal. (Tor
8831 instances run without a terminal, which is the case for most Tor
8832 packages, are not impacted.) Fixes bug 24246; bugfix on every
8833 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8834 Found by OSS-Fuzz as testcase 6360145429790720.
8835 - Fix a denial of service issue where an attacker could crash a
8836 directory authority using a malformed router descriptor. Fixes bug
8837 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8839 - When checking for replays in the INTRODUCE1 cell data for a
8840 (legacy) onion service, correctly detect replays in the RSA-
8841 encrypted part of the cell. We were previously checking for
8842 replays on the entire cell, but those can be circumvented due to
8843 the malleability of Tor's legacy hybrid encryption. This fix helps
8844 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8845 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8848 o Major bugfixes (security, onion service v2):
8849 - Fix a use-after-free error that could crash v2 Tor onion services
8850 when they failed to open circuits while expiring introduction
8851 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8852 also tracked as TROVE-2017-013 and CVE-2017-8823.
8854 o Major bugfixes (security, relay):
8855 - When running as a relay, make sure that we never build a path
8856 through ourselves, even in the case where we have somehow lost the
8857 version of our descriptor appearing in the consensus. Fixes part
8858 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8859 as TROVE-2017-012 and CVE-2017-8822.
8860 - When running as a relay, make sure that we never choose ourselves
8861 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8862 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8864 o Minor feature (relay statistics):
8865 - Change relay bandwidth reporting stats interval from 4 hours to 24
8866 hours in order to reduce the efficiency of guard discovery
8867 attacks. Fixes ticket 23856.
8869 o Minor features (directory authority):
8870 - Add an IPv6 address for the "bastet" directory authority. Closes
8873 o Minor bugfixes (client):
8874 - By default, do not enable storage of client-side DNS values. These
8875 values were unused by default previously, but they should not have
8876 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
8879 Changes in version 0.3.1.9 - 2017-12-01:
8880 Tor 0.3.1.9 backports important security and stability fixes from the
8881 0.3.2 development series. All Tor users should upgrade to this
8882 release, or to another of the releases coming out today.
8884 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8885 - Fix a denial of service bug where an attacker could use a
8886 malformed directory object to cause a Tor instance to pause while
8887 OpenSSL would try to read a passphrase from the terminal. (Tor
8888 instances run without a terminal, which is the case for most Tor
8889 packages, are not impacted.) Fixes bug 24246; bugfix on every
8890 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8891 Found by OSS-Fuzz as testcase 6360145429790720.
8892 - Fix a denial of service issue where an attacker could crash a
8893 directory authority using a malformed router descriptor. Fixes bug
8894 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8896 - When checking for replays in the INTRODUCE1 cell data for a
8897 (legacy) onion service, correctly detect replays in the RSA-
8898 encrypted part of the cell. We were previously checking for
8899 replays on the entire cell, but those can be circumvented due to
8900 the malleability of Tor's legacy hybrid encryption. This fix helps
8901 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8902 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8905 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8906 - Fix a use-after-free error that could crash v2 Tor onion services
8907 when they failed to open circuits while expiring introduction
8908 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8909 also tracked as TROVE-2017-013 and CVE-2017-8823.
8911 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8912 - When running as a relay, make sure that we never build a path
8913 through ourselves, even in the case where we have somehow lost the
8914 version of our descriptor appearing in the consensus. Fixes part
8915 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8916 as TROVE-2017-012 and CVE-2017-8822.
8917 - When running as a relay, make sure that we never choose ourselves
8918 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8919 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8921 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8922 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8923 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8924 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8925 identifying and finding a workaround to this bug and to Moritz,
8926 Arthur Edelstein, and Roger for helping to track it down and
8929 o Minor features (bridge):
8930 - Bridges now include notice in their descriptors that they are
8931 bridges, and notice of their distribution status, based on their
8932 publication settings. Implements ticket 18329. For more fine-
8933 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8936 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8937 - Add an IPv6 address for the "bastet" directory authority. Closes
8940 o Minor features (geoip):
8941 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8944 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
8945 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8946 relays, to prevent spurious address resolutions and descriptor
8947 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8948 bugfix on in 0.2.8.1-alpha.
8950 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
8951 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
8952 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8954 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
8955 - When a circuit is marked for close, do not attempt to package any
8956 cells for channels on that circuit. Previously, we would detect
8957 this condition lower in the call stack, when we noticed that the
8958 circuit had no attached channel, and log an annoying message.
8959 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8961 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
8962 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
8963 so it matches dir-spec.txt. Fixes bug 24262; bugfix
8966 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
8967 - Avoid a crash when transitioning from client mode to bridge mode.
8968 Previously, we would launch the worker threads whenever our
8969 "public server" mode changed, but not when our "server" mode
8970 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8973 Changes in version 0.3.0.13 - 2017-12-01
8974 Tor 0.3.0.13 backports important security and stability bugfixes from
8975 later Tor releases. All Tor users should upgrade to this release, or
8976 to another of the releases coming out today.
8978 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
8979 2018. If you need a release with long-term support, please stick with
8980 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8982 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8983 - Fix a denial of service bug where an attacker could use a
8984 malformed directory object to cause a Tor instance to pause while
8985 OpenSSL would try to read a passphrase from the terminal. (Tor
8986 instances run without a terminal, which is the case for most Tor
8987 packages, are not impacted.) Fixes bug 24246; bugfix on every
8988 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8989 Found by OSS-Fuzz as testcase 6360145429790720.
8990 - Fix a denial of service issue where an attacker could crash a
8991 directory authority using a malformed router descriptor. Fixes bug
8992 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8994 - When checking for replays in the INTRODUCE1 cell data for a
8995 (legacy) onion service, correctly detect replays in the RSA-
8996 encrypted part of the cell. We were previously checking for
8997 replays on the entire cell, but those can be circumvented due to
8998 the malleability of Tor's legacy hybrid encryption. This fix helps
8999 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9000 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9003 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9004 - Fix a use-after-free error that could crash v2 Tor onion services
9005 when they failed to open circuits while expiring introduction
9006 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9007 also tracked as TROVE-2017-013 and CVE-2017-8823.
9009 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9010 - When running as a relay, make sure that we never build a path
9011 through ourselves, even in the case where we have somehow lost the
9012 version of our descriptor appearing in the consensus. Fixes part
9013 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9014 as TROVE-2017-012 and CVE-2017-8822.
9015 - When running as a relay, make sure that we never choose ourselves
9016 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9017 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9019 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9020 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9021 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9022 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9023 identifying and finding a workaround to this bug and to Moritz,
9024 Arthur Edelstein, and Roger for helping to track it down and
9027 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9028 - Enable a couple of pieces of Windows hardening: one
9029 (HeapEnableTerminationOnCorruption) that has been on-by-default
9030 since Windows 8, and unavailable before Windows 7; and one
9031 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9032 affect us, but shouldn't do any harm. Closes ticket 21953.
9034 o Minor features (bridge, backport from 0.3.1.9):
9035 - Bridges now include notice in their descriptors that they are
9036 bridges, and notice of their distribution status, based on their
9037 publication settings. Implements ticket 18329. For more fine-
9038 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9041 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9042 - Add an IPv6 address for the "bastet" directory authority. Closes
9045 o Minor features (geoip):
9046 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9049 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9050 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9051 relays, to prevent spurious address resolutions and descriptor
9052 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9053 bugfix on in 0.2.8.1-alpha.
9055 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9056 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9057 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9059 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9060 - When a circuit is marked for close, do not attempt to package any
9061 cells for channels on that circuit. Previously, we would detect
9062 this condition lower in the call stack, when we noticed that the
9063 circuit had no attached channel, and log an annoying message.
9064 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9066 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9067 - Avoid a crash when transitioning from client mode to bridge mode.
9068 Previously, we would launch the worker threads whenever our
9069 "public server" mode changed, but not when our "server" mode
9070 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9072 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9073 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9074 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9077 Changes in version 0.2.9.14 - 2017-12-01
9078 Tor 0.3.0.13 backports important security and stability bugfixes from
9079 later Tor releases. All Tor users should upgrade to this release, or
9080 to another of the releases coming out today.
9082 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9083 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9084 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9085 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9086 identifying and finding a workaround to this bug and to Moritz,
9087 Arthur Edelstein, and Roger for helping to track it down and
9090 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9091 - Fix a denial of service bug where an attacker could use a
9092 malformed directory object to cause a Tor instance to pause while
9093 OpenSSL would try to read a passphrase from the terminal. (Tor
9094 instances run without a terminal, which is the case for most Tor
9095 packages, are not impacted.) Fixes bug 24246; bugfix on every
9096 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9097 Found by OSS-Fuzz as testcase 6360145429790720.
9098 - Fix a denial of service issue where an attacker could crash a
9099 directory authority using a malformed router descriptor. Fixes bug
9100 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9102 - When checking for replays in the INTRODUCE1 cell data for a
9103 (legacy) onion service, correctly detect replays in the RSA-
9104 encrypted part of the cell. We were previously checking for
9105 replays on the entire cell, but those can be circumvented due to
9106 the malleability of Tor's legacy hybrid encryption. This fix helps
9107 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9108 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9111 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9112 - Fix a use-after-free error that could crash v2 Tor onion services
9113 when they failed to open circuits while expiring introduction
9114 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9115 also tracked as TROVE-2017-013 and CVE-2017-8823.
9117 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9118 - When running as a relay, make sure that we never build a path
9119 through ourselves, even in the case where we have somehow lost the
9120 version of our descriptor appearing in the consensus. Fixes part
9121 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9122 as TROVE-2017-012 and CVE-2017-8822.
9124 o Minor features (bridge, backport from 0.3.1.9):
9125 - Bridges now include notice in their descriptors that they are
9126 bridges, and notice of their distribution status, based on their
9127 publication settings. Implements ticket 18329. For more fine-
9128 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9131 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9132 - Add an IPv6 address for the "bastet" directory authority. Closes
9135 o Minor features (geoip):
9136 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9139 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9140 - Enable a couple of pieces of Windows hardening: one
9141 (HeapEnableTerminationOnCorruption) that has been on-by-default
9142 since Windows 8, and unavailable before Windows 7; and one
9143 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9144 affect us, but shouldn't do any harm. Closes ticket 21953.
9146 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9147 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9148 relays, to prevent spurious address resolutions and descriptor
9149 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9150 bugfix on in 0.2.8.1-alpha.
9152 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9153 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9154 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9156 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9157 - When a circuit is marked for close, do not attempt to package any
9158 cells for channels on that circuit. Previously, we would detect
9159 this condition lower in the call stack, when we noticed that the
9160 circuit had no attached channel, and log an annoying message.
9161 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9163 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9164 - Avoid a crash when transitioning from client mode to bridge mode.
9165 Previously, we would launch the worker threads whenever our
9166 "public server" mode changed, but not when our "server" mode
9167 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9169 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9170 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9171 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9174 Changes in version 0.2.8.17 - 2017-12-01
9175 Tor 0.2.8.17 backports important security and stability bugfixes from
9176 later Tor releases. All Tor users should upgrade to this release, or
9177 to another of the releases coming out today.
9179 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9180 2018. If you need a release with long-term support, please upgrade with
9181 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9183 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9184 - Fix a denial of service bug where an attacker could use a
9185 malformed directory object to cause a Tor instance to pause while
9186 OpenSSL would try to read a passphrase from the terminal. (Tor
9187 instances run without a terminal, which is the case for most Tor
9188 packages, are not impacted.) Fixes bug 24246; bugfix on every
9189 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9190 Found by OSS-Fuzz as testcase 6360145429790720.
9191 - When checking for replays in the INTRODUCE1 cell data for a
9192 (legacy) onion service, correctly detect replays in the RSA-
9193 encrypted part of the cell. We were previously checking for
9194 replays on the entire cell, but those can be circumvented due to
9195 the malleability of Tor's legacy hybrid encryption. This fix helps
9196 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9197 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9200 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9201 - Fix a use-after-free error that could crash v2 Tor onion services
9202 when they failed to open circuits while expiring introduction
9203 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9204 also tracked as TROVE-2017-013 and CVE-2017-8823.
9206 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9207 - When running as a relay, make sure that we never build a path through
9208 ourselves, even in the case where we have somehow lost the version of
9209 our descriptor appearing in the consensus. Fixes part of bug 21534;
9210 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
9213 o Minor features (bridge, backport from 0.3.1.9):
9214 - Bridges now include notice in their descriptors that they are
9215 bridges, and notice of their distribution status, based on their
9216 publication settings. Implements ticket 18329. For more fine-
9217 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9220 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9221 - Add an IPv6 address for the "bastet" directory authority. Closes
9224 o Minor features (geoip):
9225 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9228 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9229 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9230 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9233 Changes in version 0.2.5.16 - 2017-12-01
9234 Tor 0.2.5.13 backports important security and stability bugfixes from
9235 later Tor releases. All Tor users should upgrade to this release, or
9236 to another of the releases coming out today.
9238 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9239 2018. If you need a release with long-term support, please upgrade to
9240 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9242 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9243 - Fix a denial of service bug where an attacker could use a
9244 malformed directory object to cause a Tor instance to pause while
9245 OpenSSL would try to read a passphrase from the terminal. (Tor
9246 instances run without a terminal, which is the case for most Tor
9247 packages, are not impacted.) Fixes bug 24246; bugfix on every
9248 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9249 Found by OSS-Fuzz as testcase 6360145429790720.
9250 - When checking for replays in the INTRODUCE1 cell data for a
9251 (legacy) onion service, correctly detect replays in the RSA-
9252 encrypted part of the cell. We were previously checking for
9253 replays on the entire cell, but those can be circumvented due to
9254 the malleability of Tor's legacy hybrid encryption. This fix helps
9255 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9256 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9259 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9260 - When running as a relay, make sure that we never build a path
9261 through ourselves, even in the case where we have somehow lost the
9262 version of our descriptor appearing in the consensus. Fixes part
9263 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9264 as TROVE-2017-012 and CVE-2017-8822.
9266 o Minor features (bridge, backport from 0.3.1.9):
9267 - Bridges now include notice in their descriptors that they are
9268 bridges, and notice of their distribution status, based on their
9269 publication settings. Implements ticket 18329. For more fine-
9270 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9273 o Minor features (geoip):
9274 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9278 Changes in version 0.3.2.5-alpha - 2017-11-22
9279 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
9280 fixes several stability and reliability bugs, including a fix for
9281 intermittent bootstrapping failures that some people have been seeing
9282 since the 0.3.0.x series.
9284 Please test this alpha out -- many of these fixes will soon be
9285 backported to stable Tor versions if no additional bugs are found
9288 o Major bugfixes (bootstrapping):
9289 - Fetch descriptors aggressively whenever we lack enough to build
9290 circuits, regardless of how many descriptors we are missing.
9291 Previously, we would delay launching the fetch when we had fewer
9292 than 15 missing descriptors, even if some of those descriptors
9293 were blocking circuits from building. Fixes bug 23985; bugfix on
9294 0.1.1.11-alpha. The effects of this bug became worse in
9295 0.3.0.3-alpha, when we began treating missing descriptors from our
9296 primary guards as a reason to delay circuits.
9297 - Don't try fetching microdescriptors from relays that have failed
9298 to deliver them in the past. Fixes bug 23817; bugfix
9301 o Minor features (directory authority):
9302 - Make the "Exit" flag assignment only depend on whether the exit
9303 policy allows connections to ports 80 and 443. Previously relays
9304 would get the Exit flag if they allowed connections to one of
9305 these ports and also port 6667. Resolves ticket 23637.
9307 o Minor features (geoip):
9308 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9311 o Minor features (linux seccomp2 sandbox):
9312 - Update the sandbox rules so that they should now work correctly
9313 with Glibc 2.26. Closes ticket 24315.
9315 o Minor features (logging):
9316 - Downgrade a pair of log messages that could occur when an exit's
9317 resolver gave us an unusual (but not forbidden) response. Closes
9319 - Improve the message we log when re-enabling circuit build timeouts
9320 after having received a consensus. Closes ticket 20963.
9322 o Minor bugfixes (compilation):
9323 - Fix a memory leak warning in one of the libevent-related
9324 configuration tests that could occur when manually specifying
9325 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
9326 Found and patched by Alex Xu.
9327 - When detecting OpenSSL on Windows from our configure script, make
9328 sure to try linking with the ws2_32 library. Fixes bug 23783;
9329 bugfix on 0.3.2.2-alpha.
9331 o Minor bugfixes (control port, linux seccomp2 sandbox):
9332 - Avoid a crash when attempting to use the seccomp2 sandbox together
9333 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9336 o Minor bugfixes (control port, onion services):
9337 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
9338 HS_DESC event when a service is not able to upload a descriptor.
9339 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
9341 o Minor bugfixes (directory cache):
9342 - Recover better from empty or corrupt files in the consensus cache
9343 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
9344 - When a consensus diff calculation is only partially successful,
9345 only record the successful parts as having succeeded. Partial
9346 success can happen if (for example) one compression method fails
9347 but the others succeed. Previously we misrecorded all the
9348 calculations as having succeeded, which would later cause a
9349 nonfatal assertion failure. Fixes bug 24086; bugfix
9352 o Minor bugfixes (logging):
9353 - Only log once if we notice that KIST support is gone. Fixes bug
9354 24158; bugfix on 0.3.2.1-alpha.
9355 - Suppress a log notice when relay descriptors arrive. We already
9356 have a bootstrap progress for this so no need to log notice
9357 everytime tor receives relay descriptors. Microdescriptors behave
9358 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
9360 o Minor bugfixes (network layer):
9361 - When closing a connection via close_connection_immediately(), we
9362 mark it as "not blocked on bandwidth", to prevent later calls from
9363 trying to unblock it, and give it permission to read. This fixes a
9364 backtrace warning that can happen on relays under various
9365 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9367 o Minor bugfixes (onion services):
9368 - The introduction circuit was being timed out too quickly while
9369 waiting for the rendezvous circuit to complete. Keep the intro
9370 circuit around longer instead of timing out and reopening new ones
9371 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
9372 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9373 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9375 - Silence a warning about failed v3 onion descriptor uploads that
9376 can happen naturally under certain edge cases. Fixes part of bug
9377 23662; bugfix on 0.3.2.1-alpha.
9379 o Minor bugfixes (tests):
9380 - Fix a memory leak in one of the bridge-distribution test cases.
9381 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
9382 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
9383 to correctly handle cases where a caller gives it an RSA key of
9384 under 160 bits. (This is not actually a bug in Tor itself, but
9385 rather in our fuzzing code.) Fixes bug 24247; bugfix on
9386 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
9389 - Add notes in man page regarding OS support for the various
9390 scheduler types. Attempt to use less jargon in the scheduler
9391 section. Closes ticket 24254.
9394 Changes in version 0.3.2.4-alpha - 2017-11-08
9395 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
9396 It fixes several stability and reliability bugs, especially including
9397 a major reliability issue that has been plaguing fast exit relays in
9400 o Major bugfixes (exit relays, DNS):
9401 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9402 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9403 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9404 identifying and finding a workaround to this bug and to Moritz,
9405 Arthur Edelstein, and Roger for helping to track it down and
9408 o Major bugfixes (scheduler, channel):
9409 - Stop processing scheduled channels if they closed while flushing
9410 cells. This can happen if the write on the connection fails
9411 leading to the channel being closed while in the scheduler loop.
9412 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
9414 o Minor features (logging, scheduler):
9415 - Introduce a SCHED_BUG() function to log extra information about
9416 the scheduler state if we ever catch a bug in the scheduler.
9417 Closes ticket 23753.
9419 o Minor features (removed deprecations):
9420 - The ClientDNSRejectInternalAddresses flag can once again be set in
9421 non-testing Tor networks, so long as they do not use the default
9422 directory authorities. This change also removes the deprecation of
9423 this flag from 0.2.9.2-alpha. Closes ticket 21031.
9425 o Minor features (testing):
9426 - Our fuzzing tests now test the encrypted portions of v3 onion
9427 service descriptors. Implements more of 21509.
9429 o Minor bugfixes (directory client):
9430 - On failure to download directory information, delay retry attempts
9431 by a random amount based on the "decorrelated jitter" algorithm.
9432 Our previous delay algorithm tended to produce extra-long delays
9433 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
9435 o Minor bugfixes (IPv6, v3 single onion services):
9436 - Remove buggy code for IPv6-only v3 single onion services, and
9437 reject attempts to configure them. This release supports IPv4,
9438 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
9439 stack v3 single onion services. Fixes bug 23820; bugfix
9442 o Minor bugfixes (logging, relay):
9443 - Give only a protocol warning when the ed25519 key is not
9444 consistent between the descriptor and microdescriptor of a relay.
9445 This can happen, for instance, if the relay has been flagged
9446 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
9448 o Minor bugfixes (manpage, onion service):
9449 - Document that the HiddenServiceNumIntroductionPoints option is
9450 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
9451 bugfix on 0.3.2.1-alpha.
9453 o Minor bugfixes (memory leaks):
9454 - Fix a minor memory leak at exit in the KIST scheduler. This bug
9455 should have no user-visible impact. Fixes bug 23774; bugfix
9457 - Fix a memory leak when decrypting a badly formatted v3 onion
9458 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
9459 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
9461 o Minor bugfixes (onion services):
9462 - Cache some needed onion service client information instead of
9463 constantly computing it over and over again. Fixes bug 23623;
9464 bugfix on 0.3.2.1-alpha.
9465 - Properly retry HSv3 descriptor fetches when missing required
9466 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
9468 o Minor bugfixes (path selection):
9469 - When selecting relays by bandwidth, avoid a rounding error that
9470 could sometimes cause load to be imbalanced incorrectly.
9471 Previously, we would always round upwards; now, we round towards
9472 the nearest integer. This had the biggest effect when a relay's
9473 weight adjustments should have given it weight 0, but it got
9474 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9475 - When calculating the fraction of nodes that have descriptors, and
9476 all nodes in the network have zero bandwidths, count the number of
9477 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9478 - Actually log the total bandwidth in compute_weighted_bandwidths().
9479 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9481 o Minor bugfixes (relay, crash):
9482 - Avoid a crash when transitioning from client mode to bridge mode.
9483 Previously, we would launch the worker threads whenever our
9484 "public server" mode changed, but not when our "server" mode
9485 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9487 o Minor bugfixes (testing):
9488 - Fix a spurious fuzzing-only use of an uninitialized value. Found
9489 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
9490 - Test that IPv6-only clients can use microdescriptors when running
9491 "make test-network-all". Requires chutney master 61c28b9 or later.
9492 Closes ticket 24109.
9495 Changes in version 0.3.2.3-alpha - 2017-10-27
9496 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
9497 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
9498 directory authority, Bastet.
9500 o Directory authority changes:
9501 - Add "Bastet" as a ninth directory authority to the default list.
9502 Closes ticket 23910.
9503 - The directory authority "Longclaw" has changed its IP address.
9504 Closes ticket 23592.
9506 o Minor features (bridge):
9507 - Bridge relays can now set the BridgeDistribution config option to
9508 add a "bridge-distribution-request" line to their bridge
9509 descriptor, which tells BridgeDB how they'd like their bridge
9510 address to be given out. (Note that as of Oct 2017, BridgeDB does
9511 not yet implement this feature.) As a side benefit, this feature
9512 provides a way to distinguish bridge descriptors from non-bridge
9513 descriptors. Implements tickets 18329.
9515 o Minor features (client, entry guards):
9516 - Improve log messages when missing descriptors for primary guards.
9517 Resolves ticket 23670.
9519 o Minor features (geoip):
9520 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9523 o Minor bugfixes (bridge):
9524 - Overwrite the bridge address earlier in the process of retrieving
9525 its descriptor, to make sure we reach it on the configured
9526 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
9528 o Minor bugfixes (documentation):
9529 - Document better how to read gcov, and what our gcov postprocessing
9530 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
9532 o Minor bugfixes (entry guards):
9533 - Tor now updates its guard state when it reads a consensus
9534 regardless of whether it's missing descriptors. That makes tor use
9535 its primary guards to fetch descriptors in some edge cases where
9536 it would previously have used fallback directories. Fixes bug
9537 23862; bugfix on 0.3.0.1-alpha.
9539 o Minor bugfixes (hidden service client):
9540 - When handling multiple SOCKS request for the same .onion address,
9541 only fetch the service descriptor once.
9542 - When a descriptor fetch fails with a non-recoverable error, close
9543 all pending SOCKS requests for that .onion. Fixes bug 23653;
9544 bugfix on 0.3.2.1-alpha.
9546 o Minor bugfixes (hidden service):
9547 - Always regenerate missing hidden service public key files. Prior
9548 to this, if the public key was deleted from disk, it wouldn't get
9549 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
9551 - Make sure that we have a usable ed25519 key when the intro point
9552 relay supports ed25519 link authentication. Fixes bug 24002;
9553 bugfix on 0.3.2.1-alpha.
9555 o Minor bugfixes (hidden service, v2):
9556 - When reloading configured hidden services, copy all information
9557 from the old service object. Previously, some data was omitted,
9558 causing delays in descriptor upload, and other bugs. Fixes bug
9559 23790; bugfix on 0.2.1.9-alpha.
9561 o Minor bugfixes (memory safety, defensive programming):
9562 - Clear the target address when node_get_prim_orport() returns
9563 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9565 o Minor bugfixes (relay):
9566 - Avoid a BUG warning when receiving a dubious CREATE cell while an
9567 option transition is in progress. Fixes bug 23952; bugfix
9570 o Minor bugfixes (testing):
9571 - Adjust the GitLab CI configuration to more closely match that of
9572 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
9573 - Prevent scripts/test/coverage from attempting to move gcov output
9574 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
9575 - When running unit tests as root, skip a test that would fail
9576 because it expects a permissions error. This affects some
9577 continuous integration setups. Fixes bug 23758; bugfix
9579 - Stop unconditionally mirroring the tor repository in GitLab CI.
9580 This prevented developers from enabling GitLab CI on master. Fixes
9581 bug 23755; bugfix on 0.3.2.2-alpha.
9582 - Fix the hidden service v3 descriptor decoding fuzzing to use the
9583 latest decoding API correctly. Fixes bug 21509; bugfix
9586 o Minor bugfixes (warnings):
9587 - When we get an HTTP request on a SOCKS port, tell the user about
9588 the new HTTPTunnelPort option. Previously, we would give a "Tor is
9589 not an HTTP Proxy" message, which stopped being true when
9590 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
9594 Changes in version 0.2.5.15 - 2017-10-25
9595 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
9596 series. It also adds a new directory authority, Bastet.
9598 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9599 2018. If you need a release with long-term support, please upgrade to
9600 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9602 o Directory authority changes:
9603 - Add "Bastet" as a ninth directory authority to the default list.
9604 Closes ticket 23910.
9605 - The directory authority "Longclaw" has changed its IP address.
9606 Closes ticket 23592.
9608 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9609 - Avoid an assertion failure bug affecting our implementation of
9610 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9611 handling of "0xx" differs from what we had expected. Fixes bug
9612 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9614 o Minor features (geoip):
9615 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9618 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9619 - Fix a memset() off the end of an array when packing cells. This
9620 bug should be harmless in practice, since the corrupted bytes are
9621 still in the same structure, and are always padding bytes,
9622 ignored, or immediately overwritten, depending on compiler
9623 behavior. Nevertheless, because the memset()'s purpose is to make
9624 sure that any other cell-handling bugs can't expose bytes to the
9625 network, we need to fix it. Fixes bug 22737; bugfix on
9626 0.2.4.11-alpha. Fixes CID 1401591.
9628 o Build features (backport from 0.3.1.5-alpha):
9629 - Tor's repository now includes a Travis Continuous Integration (CI)
9630 configuration file (.travis.yml). This is meant to help new
9631 developers and contributors who fork Tor to a Github repository be
9632 better able to test their changes, and understand what we expect
9633 to pass. To use this new build feature, you must fork Tor to your
9634 Github account, then go into the "Integrations" menu in the
9635 repository settings for your fork and enable Travis, then push
9636 your changes. Closes ticket 22636.
9639 Changes in version 0.2.8.16 - 2017-10-25
9640 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
9641 series, including a bugfix for a crash issue that had affected relays
9642 under memory pressure. It also adds a new directory authority, Bastet.
9644 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9645 2018. If you need a release with long-term support, please stick with
9646 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9648 o Directory authority changes:
9649 - Add "Bastet" as a ninth directory authority to the default list.
9650 Closes ticket 23910.
9651 - The directory authority "Longclaw" has changed its IP address.
9652 Closes ticket 23592.
9654 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9655 - Fix a timing-based assertion failure that could occur when the
9656 circuit out-of-memory handler freed a connection's output buffer.
9657 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9659 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9660 - Remove longclaw's IPv6 address, as it will soon change. Authority
9661 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9662 3/8 directory authorities with IPv6 addresses, but there are also
9663 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9665 o Minor features (geoip):
9666 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9670 Changes in version 0.2.9.13 - 2017-10-25
9671 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
9672 series, including a bugfix for a crash issue that had affected relays
9673 under memory pressure. It also adds a new directory authority, Bastet.
9675 o Directory authority changes:
9676 - Add "Bastet" as a ninth directory authority to the default list.
9677 Closes ticket 23910.
9678 - The directory authority "Longclaw" has changed its IP address.
9679 Closes ticket 23592.
9681 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9682 - Fix a timing-based assertion failure that could occur when the
9683 circuit out-of-memory handler freed a connection's output buffer.
9684 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9686 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9687 - Remove longclaw's IPv6 address, as it will soon change. Authority
9688 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9689 3/8 directory authorities with IPv6 addresses, but there are also
9690 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9692 o Minor features (geoip):
9693 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9696 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9697 - When a directory authority rejects a descriptor or extrainfo with
9698 a given digest, mark that digest as undownloadable, so that we do
9699 not attempt to download it again over and over. We previously
9700 tried to avoid downloading such descriptors by other means, but we
9701 didn't notice if we accidentally downloaded one anyway. This
9702 behavior became problematic in 0.2.7.2-alpha, when authorities
9703 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9706 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9707 - Clear the address when node_get_prim_orport() returns early.
9708 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9710 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9711 - When running as a Windows service, set the ID of the main thread
9712 correctly. Failure to do so made us fail to send log messages to
9713 the controller in 0.2.1.16-rc, slowed down controller event
9714 delivery in 0.2.7.3-rc and later, and crash with an assertion
9715 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9716 Patch and diagnosis from "Vort".
9719 Changes in version 0.3.0.12 - 2017-10-25
9720 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
9721 series, including a bugfix for a crash issue that had affected relays
9722 under memory pressure. It also adds a new directory authority, Bastet.
9724 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9725 2018. If you need a release with long-term support, please stick with
9726 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9728 o Directory authority changes:
9729 - Add "Bastet" as a ninth directory authority to the default list.
9730 Closes ticket 23910.
9731 - The directory authority "Longclaw" has changed its IP address.
9732 Closes ticket 23592.
9734 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9735 - Fix a timing-based assertion failure that could occur when the
9736 circuit out-of-memory handler freed a connection's output buffer.
9737 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9739 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9740 - Remove longclaw's IPv6 address, as it will soon change. Authority
9741 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9742 3/8 directory authorities with IPv6 addresses, but there are also
9743 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9745 o Minor features (geoip):
9746 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9749 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9750 - When a directory authority rejects a descriptor or extrainfo with
9751 a given digest, mark that digest as undownloadable, so that we do
9752 not attempt to download it again over and over. We previously
9753 tried to avoid downloading such descriptors by other means, but we
9754 didn't notice if we accidentally downloaded one anyway. This
9755 behavior became problematic in 0.2.7.2-alpha, when authorities
9756 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9759 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9760 - Avoid a possible double close of a circuit by the intro point on
9761 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9762 bugfix on 0.3.0.1-alpha.
9764 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9765 - Clear the address when node_get_prim_orport() returns early.
9766 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9768 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9769 - When running as a Windows service, set the ID of the main thread
9770 correctly. Failure to do so made us fail to send log messages to
9771 the controller in 0.2.1.16-rc, slowed down controller event
9772 delivery in 0.2.7.3-rc and later, and crash with an assertion
9773 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9774 Patch and diagnosis from "Vort".
9777 Changes in version 0.3.1.8 - 2017-10-25
9778 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
9779 It includes several bugfixes, including a bugfix for a crash issue
9780 that had affected relays under memory pressure. It also adds
9781 a new directory authority, Bastet.
9783 o Directory authority changes:
9784 - Add "Bastet" as a ninth directory authority to the default list.
9785 Closes ticket 23910.
9786 - The directory authority "Longclaw" has changed its IP address.
9787 Closes ticket 23592.
9789 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9790 - Fix a timing-based assertion failure that could occur when the
9791 circuit out-of-memory handler freed a connection's output buffer.
9792 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9794 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9795 - Remove longclaw's IPv6 address, as it will soon change. Authority
9796 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9797 3/8 directory authorities with IPv6 addresses, but there are also
9798 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9800 o Minor features (geoip):
9801 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9804 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
9805 - Fix a compilation warning when building with zstd support on
9806 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9807 and fixed by Andreas Stieger.
9809 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
9810 - Handle a pathological case when decompressing Zstandard data when
9811 the output buffer size is zero. Fixes bug 23551; bugfix
9814 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
9815 - Remove the length limit on HTTP status lines that authorities can
9816 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
9818 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9819 - Avoid a possible double close of a circuit by the intro point on
9820 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9821 bugfix on 0.3.0.1-alpha.
9823 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9824 - Clear the address when node_get_prim_orport() returns early.
9825 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9827 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
9828 - Fix additional channelpadding unit test failures by using mocked
9829 time instead of actual time for all tests. Fixes bug 23608; bugfix
9833 Changes in version 0.3.2.2-alpha - 2017-09-29
9834 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
9835 release fixes several minor bugs in the new scheduler and next-
9836 generation onion services; both features were newly added in the 0.3.2
9837 series. Other fixes in this alpha include several fixes for non-fatal
9838 tracebacks which would appear in logs.
9840 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
9841 alpha does not contain any substantial new features. Minor features
9842 include better testing and logging.
9844 The following comprises the complete list of changes included
9847 o Major bugfixes (relay, crash, assertion failure):
9848 - Fix a timing-based assertion failure that could occur when the
9849 circuit out-of-memory handler freed a connection's output buffer.
9850 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9852 o Major bugfixes (scheduler):
9853 - If a channel is put into the scheduler's pending list, then it
9854 starts closing, and then if the scheduler runs before it finishes
9855 closing, the scheduler will get stuck trying to flush its cells
9856 while the lower layers refuse to cooperate. Fix that race
9857 condition by giving the scheduler an escape method. Fixes bug
9858 23676; bugfix on 0.3.2.1-alpha.
9860 o Minor features (build, compilation):
9861 - The "check-changes" feature is now part of the "make check" tests;
9862 we'll use it to try to prevent misformed changes files from
9863 accumulating. Closes ticket 23564.
9864 - Tor builds should now fail if there are any mismatches between the
9865 C type representing a configuration variable and the C type the
9866 data-driven parser uses to store a value there. Previously, we
9867 needed to check these by hand, which sometimes led to mistakes.
9868 Closes ticket 23643.
9870 o Minor features (directory authorities):
9871 - Remove longclaw's IPv6 address, as it will soon change. Authority
9872 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9873 3/8 directory authorities with IPv6 addresses, but there are also
9874 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9876 o Minor features (hidden service, circuit, logging):
9877 - Improve logging of many callsite in the circuit subsystem to print
9878 the circuit identifier(s).
9879 - Log when we cleanup an intro point from a service so we know when
9880 and for what reason it happened. Closes ticket 23604.
9882 o Minor features (logging):
9883 - Log more circuit information whenever we are about to try to
9884 package a relay cell on a circuit with a nonexistent n_chan.
9885 Attempt to diagnose ticket 8185.
9886 - Improve info-level log identification of particular circuits, to
9887 help with debugging. Closes ticket 23645.
9889 o Minor features (relay):
9890 - When choosing which circuits can be expired as unused, consider
9891 circuits from clients even if those clients used regular CREATE
9892 cells to make them; and do not consider circuits from relays even
9893 if they were made with CREATE_FAST. Part of ticket 22805.
9895 o Minor features (robustness):
9896 - Change several fatal assertions when flushing buffers into non-
9897 fatal assertions, to prevent any recurrence of 23690.
9899 o Minor features (spec conformance, bridge, diagnostic):
9900 - When handling the USERADDR command on an ExtOrPort, warn when the
9901 transports provides a USERADDR with no port. In a future version,
9902 USERADDR commands of this format may be rejected. Detects problems
9903 related to ticket 23080.
9905 o Minor features (testing):
9906 - Add a unit test to make sure that our own generated platform
9907 string will be accepted by directory authorities. Closes
9910 o Minor bugfixes (bootstrapping):
9911 - When warning about state file clock skew, report the correct
9912 direction for the detected skew. Fixes bug 23606; bugfix
9914 - Avoid an assertion failure when logging a state file clock skew
9915 very early in bootstrapping. Fixes bug 23607; bugfix
9918 o Minor bugfixes (build, compilation):
9919 - Fix a compilation warning when building with zstd support on
9920 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9921 and fixed by Andreas Stieger.
9922 - When searching for OpenSSL, don't accept any OpenSSL library that
9923 lacks TLSv1_1_method(): Tor doesn't build with those versions.
9924 Additionally, look in /usr/local/opt/openssl, if it's present.
9925 These changes together repair the default build on OSX systems
9926 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
9928 o Minor bugfixes (compression):
9929 - Handle a pathological case when decompressing Zstandard data when
9930 the output buffer size is zero. Fixes bug 23551; bugfix
9933 o Minor bugfixes (documentation):
9934 - Fix manpage to not refer to the obsolete (and misspelled)
9935 UseEntryGuardsAsDirectoryGuards parameter in the description of
9936 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
9938 o Minor bugfixes (hidden service v3):
9939 - Don't log an assertion failure when we can't find the right
9940 information to extend to an introduction point. In rare cases,
9941 this could happen, causing a warning, even though tor would
9942 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
9943 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
9944 much bigger so the rendezvous point can't distinguish which hidden
9945 service protocol is being used. Fixes bug 23420; bugfix
9948 o Minor bugfixes (hidden service, relay):
9949 - Avoid a possible double close of a circuit by the intro point on
9950 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9951 bugfix on 0.3.0.1-alpha.
9953 o Minor bugfixes (logging, relay shutdown, annoyance):
9954 - When a circuit is marked for close, do not attempt to package any
9955 cells for channels on that circuit. Previously, we would detect
9956 this condition lower in the call stack, when we noticed that the
9957 circuit had no attached channel, and log an annoying message.
9958 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9960 o Minor bugfixes (scheduler):
9961 - When switching schedulers due to a consensus change, we didn't
9962 give the new scheduler a chance to react to the consensus. Fix
9963 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
9964 - Make the KISTSchedRunInterval option a non negative value. With
9965 this, the way to disable KIST through the consensus is to set it
9966 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
9967 - Only notice log the selected scheduler when we switch scheduler
9968 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
9969 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
9970 by a different tv_usec data type. Fixes bug 23575; bugfix
9972 - Make a hard exit if tor is unable to pick a scheduler which can
9973 happen if the user specifies a scheduler type that is not
9974 supported and not other types in Schedulers. Fixes bug 23581;
9975 bugfix on 0.3.2.1-alpha.
9976 - Properly initialize the scheduler last run time counter so it is
9977 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
9979 o Minor bugfixes (testing):
9980 - Capture and detect several "Result does not fit" warnings in unit
9981 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
9983 - Fix additional channelpadding unit test failures by using mocked
9984 time instead of actual time for all tests. Fixes bug 23608; bugfix
9986 - The removal of some old scheduler options caused some tests to
9987 fail on BSD systems. Assume current behavior is correct and make
9988 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
9990 o Code simplification and refactoring:
9991 - Remove various ways of testing circuits and connections for
9992 "clientness"; instead, favor channel_is_client(). Part of
9995 o Deprecated features:
9996 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
9997 now deprecated; they do not apply to relays, and they have had no
9998 effect on clients since 0.2.8.x. Closes ticket 19704.
10001 - HiddenServiceVersion man page entry wasn't mentioning the now
10002 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
10003 - Clarify that the Address option is entirely about setting an
10004 advertised IPv4 address. Closes ticket 18891.
10005 - Clarify the manpage's use of the term "address" to clarify what
10006 kind of address is intended. Closes ticket 21405.
10007 - Document that onion service subdomains are allowed, and ignored.
10008 Closes ticket 18736.
10011 Changes in version 0.3.2.1-alpha - 2017-09-18
10012 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
10013 includes support for our next-generation ("v3") onion service
10014 protocol, and adds a new circuit scheduler for more responsive
10015 forwarding decisions from relays. There are also numerous other small
10016 features and bugfixes here.
10018 Below are the changes since Tor 0.3.1.7.
10020 o Major feature (scheduler, channel):
10021 - Tor now uses new schedulers to decide which circuits should
10022 deliver cells first, in order to improve congestion at relays. The
10023 first type is called "KIST" ("Kernel Informed Socket Transport"),
10024 and is only available on Linux-like systems: it uses feedback from
10025 the kernel to prevent the kernel's TCP buffers from growing too
10026 full. The second new scheduler type is called "KISTLite": it
10027 behaves the same as KIST, but runs on systems without kernel
10028 support for inspecting TCP implementation details. The old
10029 scheduler is still available, under the name "Vanilla". To change
10030 the default scheduler preference order, use the new "Schedulers"
10031 option. (The default preference order is "KIST,KISTLite,Vanilla".)
10033 Matt Traudt implemented KIST, based on research by Rob Jansen,
10034 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
10035 more information, see the design paper at
10036 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
10037 followup implementation paper at https://arxiv.org/abs/1709.01044.
10038 Closes ticket 12541.
10040 o Major features (next-generation onion services):
10041 - Tor now supports the next-generation onion services protocol for
10042 clients and services! As part of this release, the core of
10043 proposal 224 has been implemented and is available for
10044 experimentation and testing by our users. This newer version of
10045 onion services ("v3") features many improvements over the legacy
10048 a) Better crypto (replaced SHA1/DH/RSA1024
10049 with SHA3/ed25519/curve25519)
10051 b) Improved directory protocol, leaking much less information to
10054 c) Improved directory protocol, with smaller surface for
10057 d) Better onion address security against impersonation.
10059 e) More extensible introduction/rendezvous protocol.
10061 f) A cleaner and more modular codebase.
10063 You can identify a next-generation onion address by its length:
10064 they are 56 characters long, as in
10065 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
10067 In the future, we will release more options and features for v3
10068 onion services, but we first need a testing period, so that the
10069 current codebase matures and becomes more robust. Planned features
10070 include: offline keys, advanced client authorization, improved
10071 guard algorithms, and statistics. For full details, see
10074 Legacy ("v2") onion services will still work for the foreseeable
10075 future, and will remain the default until this new codebase gets
10076 tested and hardened. Service operators who want to experiment with
10077 the new system can use the 'HiddenServiceVersion 3' torrc
10078 directive along with the regular onion service configuration
10079 options. We will publish a blog post about this new feature
10082 o Major bugfixes (usability, control port):
10083 - Report trusted clock skew indications as bootstrap errors, so
10084 controllers can more easily alert users when their clocks are
10085 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
10087 o Minor features (bug detection):
10088 - Log a warning message with a stack trace for any attempt to call
10089 get_options() during option validation. This pattern has caused
10090 subtle bugs in the past. Closes ticket 22281.
10092 o Minor features (client):
10093 - You can now use Tor as a tunneled HTTP proxy: use the new
10094 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
10095 requests. Closes ticket 22407.
10096 - Add an extra check to make sure that we always use the newer guard
10097 selection code for picking our guards. Closes ticket 22779.
10098 - When downloading (micro)descriptors, don't split the list into
10099 multiple requests unless we want at least 32 descriptors.
10100 Previously, we split at 4, not 32, which led to significant
10101 overhead in HTTP request size and degradation in compression
10102 performance. Closes ticket 23220.
10104 o Minor features (command line):
10105 - Add a new commandline option, --key-expiration, which prints when
10106 the current signing key is going to expire. Implements ticket
10107 17639; patch by Isis Lovecruft.
10109 o Minor features (control port):
10110 - If an application tries to use the control port as an HTTP proxy,
10111 respond with a meaningful "This is the Tor control port" message,
10112 and log the event. Closes ticket 1667. Patch from Ravi
10114 - Provide better error message for GETINFO desc/(id|name) when not
10115 fetching router descriptors. Closes ticket 5847. Patch by
10117 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
10118 whether Tor will try to download router descriptors and
10119 microdescriptors respectively. Closes ticket 22684.
10120 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
10121 so controllers can tell whether the geoip databases are loaded.
10122 Closes ticket 23237.
10123 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
10124 events. Closes ticket 19254. Patch by "DonnchaC".
10126 o Minor features (development support):
10127 - Developers can now generate a call-graph for Tor using the
10128 "calltool" python program, which post-processes object dumps. It
10129 should work okay on many Linux and OSX platforms, and might work
10130 elsewhere too. To run it, install calltool from
10131 https://gitweb.torproject.org/user/nickm/calltool.git and run
10132 "make callgraph". Closes ticket 19307.
10134 o Minor features (ed25519):
10135 - Add validation function to checks for torsion components in
10136 ed25519 public keys, used by prop224 client-side code. Closes
10137 ticket 22006. Math help by Ian Goldberg.
10139 o Minor features (exit relay, DNS):
10140 - Improve the clarity and safety of the log message from evdns when
10141 receiving an apparently spoofed DNS reply. Closes ticket 3056.
10143 o Minor features (integration, hardening):
10144 - Add a new NoExec option to prevent Tor from running other
10145 programs. When this option is set to 1, Tor will never try to run
10146 another program, regardless of the settings of
10147 PortForwardingHelper, ClientTransportPlugin, or
10148 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
10149 without restarting Tor. Closes ticket 22976.
10151 o Minor features (logging):
10152 - Improve the warning message for specifying a relay by nickname.
10153 The previous message implied that nickname registration was still
10154 part of the Tor network design, which it isn't. Closes
10156 - If the sandbox filter fails to load, suggest to the user that
10157 their kernel might not support seccomp2. Closes ticket 23090.
10159 o Minor features (portability):
10160 - Check at configure time whether uint8_t is the same type as
10161 unsigned char. Lots of existing code already makes this
10162 assumption, and there could be strict aliasing issues if the
10163 assumption is violated. Closes ticket 22410.
10165 o Minor features (relay, configuration):
10166 - Reject attempts to use relative file paths when RunAsDaemon is
10167 set. Previously, Tor would accept these, but the directory-
10168 changing step of RunAsDaemon would give strange and/or confusing
10169 results. Closes ticket 22731.
10171 o Minor features (startup, safety):
10172 - When configured to write a PID file, Tor now exits if it is unable
10173 to do so. Previously, it would warn and continue. Closes
10176 o Minor features (static analysis):
10177 - The BUG() macro has been changed slightly so that Coverity no
10178 longer complains about dead code if the bug is impossible. Closes
10181 o Minor features (testing):
10182 - The default chutney network tests now include tests for the v3
10183 hidden service design. Make sure you have the latest version of
10184 chutney if you want to run these. Closes ticket 22437.
10185 - Add a unit test to verify that we can parse a hardcoded v2 hidden
10186 service descriptor. Closes ticket 15554.
10188 o Minor bugfixes (certificate handling):
10189 - Fix a time handling bug in Tor certificates set to expire after
10190 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
10191 Coverity as CID 1415728.
10193 o Minor bugfixes (client, usability):
10194 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
10195 SOCKS4a requests that contain IP address strings, even when
10196 SafeSocks in enabled, as this prevents user from connecting to
10197 known IP addresses without relying on DNS for resolving. SafeSocks
10198 still rejects SOCKS connections that connect to IP addresses when
10199 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
10200 bugfix on Tor 0.2.6.2-alpha.
10202 o Minor bugfixes (code correctness):
10203 - Call htons() in extend_cell_format() for encoding a 16-bit value.
10204 Previously we used ntohs(), which happens to behave the same on
10205 all the platforms we support, but which isn't really correct.
10206 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
10207 - For defense-in-depth, make the controller's write_escaped_data()
10208 function robust to extremely long inputs. Fixes bug 19281; bugfix
10209 on 0.1.1.1-alpha. Reported by Guido Vranken.
10211 o Minor bugfixes (compilation):
10212 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
10213 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10215 o Minor bugfixes (consensus expiry):
10216 - Check for adequate directory information correctly. Previously, Tor
10217 would reconsider whether it had sufficient directory information
10218 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
10220 o Minor bugfixes (directory protocol):
10221 - Directory servers now include a "Date:" http header for response
10222 codes other than 200. Clients starting with a skewed clock and a
10223 recent consensus were getting "304 Not modified" responses from
10224 directory authorities, so without the Date header, the client
10225 would never hear about a wrong clock. Fixes bug 23499; bugfix
10227 - Make clients wait for 6 seconds before trying to download a
10228 consensus from an authority. Fixes bug 17750; bugfix
10231 o Minor bugfixes (DoS-resistance):
10232 - If future code asks if there are any running bridges, without
10233 checking if bridges are enabled, log a BUG warning rather than
10234 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
10236 o Minor bugfixes (format strictness):
10237 - Restrict several data formats to decimal. Previously, the
10238 BuildTimeHistogram entries in the state file, the "bw=" entries in
10239 the bandwidth authority file, and the process IDs passed to the
10240 __OwningControllerProcess option could all be specified in hex or
10241 octal as well as in decimal. This was not an intentional feature.
10242 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
10245 o Minor bugfixes (heartbeat):
10246 - If we fail to write a heartbeat message, schedule a retry for the
10247 minimum heartbeat interval number of seconds in the future. Fixes
10248 bug 19476; bugfix on 0.2.3.1-alpha.
10250 o Minor bugfixes (linux seccomp2 sandbox, logging):
10251 - Fix some messages on unexpected errors from the seccomp2 library.
10252 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
10254 o Minor bugfixes (logging):
10255 - Remove duplicate log messages regarding opening non-local
10256 SocksPorts upon parsing config and opening listeners at startup.
10257 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
10258 - Use a more comprehensible log message when telling the user
10259 they've excluded every running exit node. Fixes bug 7890; bugfix
10261 - When logging the number of descriptors we intend to download per
10262 directory request, do not log a number higher than then the number
10263 of descriptors we're fetching in total. Fixes bug 19648; bugfix
10265 - When warning about a directory owned by the wrong user, log the
10266 actual name of the user owning the directory. Previously, we'd log
10267 the name of the process owner twice. Fixes bug 23487; bugfix
10269 - The tor specification says hop counts are 1-based, so fix two log
10270 messages that mistakenly logged 0-based hop counts. Fixes bug
10271 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
10272 Credit to Xiaofan Li for reporting this issue.
10274 o Minor bugfixes (portability):
10275 - Stop using the PATH_MAX variable, which is not defined on GNU
10276 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
10278 o Minor bugfixes (relay):
10279 - When uploading our descriptor for the first time after startup,
10280 report the reason for uploading as "Tor just started" rather than
10281 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
10282 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10283 relays, to prevent spurious address resolutions and descriptor
10284 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10285 bugfix on in 0.2.8.1-alpha.
10287 o Minor bugfixes (tests):
10288 - Fix a broken unit test for the OutboundAddress option: the parsing
10289 function was never returning an error on failure. Fixes bug 23366;
10290 bugfix on 0.3.0.3-alpha.
10291 - Fix a signed-integer overflow in the unit tests for
10292 dir/download_status_random_backoff, which was untriggered until we
10293 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
10295 o Minor bugfixes (usability, control port):
10296 - Stop making an unnecessary routerlist check in NETINFO clock skew
10297 detection; this was preventing clients from reporting NETINFO clock
10298 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
10300 o Code simplification and refactoring:
10301 - Extract the code for handling newly-open channels into a separate
10302 function from the general code to handle channel state
10303 transitions. This change simplifies our callgraph, reducing the
10304 size of the largest strongly connected component by roughly a
10305 factor of two. Closes ticket 22608.
10306 - Remove dead code for largely unused statistics on the number of
10307 times we've attempted various public key operations. Fixes bug
10308 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
10309 - Remove several now-obsolete functions for asking about old
10310 variants directory authority status. Closes ticket 22311; patch
10312 - Remove some of the code that once supported "Named" and "Unnamed"
10313 routers. Authorities no longer vote for these flags. Closes
10315 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
10316 and old hidden services, to indicate that they aren't suitable for
10317 new protocols or formats. Closes ticket 23026.
10318 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
10319 22521. Patch from Neel Chauhan.
10320 - Split the enormous circuit_send_next_onion_skin() function into
10321 multiple subfunctions. Closes ticket 22804.
10322 - Split the portions of the buffer.c module that handle particular
10323 protocols into separate modules. Part of ticket 23149.
10324 - Use our test macros more consistently, to produce more useful
10325 error messages when our unit tests fail. Add coccinelle patches to
10326 allow us to re-check for test macro uses. Closes ticket 22497.
10328 o Deprecated features:
10329 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
10330 only applies to direct unencrypted HTTP connections to your
10331 directory server, which your Tor probably isn't using. Closes
10335 - Clarify in the manual that "Sandbox 1" is only supported on Linux
10336 kernels. Closes ticket 22677.
10337 - Document all values of PublishServerDescriptor in the manpage.
10338 Closes ticket 15645.
10339 - Improve the documentation for the directory port part of the
10340 DirAuthority line. Closes ticket 20152.
10341 - Restore documentation for the authorities' "approved-routers"
10342 file. Closes ticket 21148.
10344 o Removed features:
10345 - The AllowDotExit option has been removed as unsafe. It has been
10346 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
10347 - The ClientDNSRejectInternalAddresses flag can no longer be set on
10348 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
10349 Closes ticket 21031.
10350 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
10351 nobody was using it any longer. Closes ticket 22377.
10354 Changes in version 0.2.8.15 - 2017-09-18
10355 Tor 0.2.8.15 backports a collection of bugfixes from later
10358 Most significantly, it includes a fix for TROVE-2017-008, a
10359 security bug that affects hidden services running with the
10360 SafeLogging option disabled. For more information, see
10361 https://trac.torproject.org/projects/tor/ticket/23490
10363 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
10364 2018. We suggest that you upgrade to the latest stable release if
10365 possible. If you can't, we recommend that you upgrade at least to
10366 0.2.9, which will be supported until 2020.
10368 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10369 - Avoid an assertion failure bug affecting our implementation of
10370 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10371 handling of "0xx" differs from what we had expected. Fixes bug
10372 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10375 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10378 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10379 - Backport a fix for an "unused variable" warning that appeared
10380 in some versions of mingw. Fixes bug 22838; bugfix on
10383 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10384 - Fix a memset() off the end of an array when packing cells. This
10385 bug should be harmless in practice, since the corrupted bytes are
10386 still in the same structure, and are always padding bytes,
10387 ignored, or immediately overwritten, depending on compiler
10388 behavior. Nevertheless, because the memset()'s purpose is to make
10389 sure that any other cell-handling bugs can't expose bytes to the
10390 network, we need to fix it. Fixes bug 22737; bugfix on
10391 0.2.4.11-alpha. Fixes CID 1401591.
10393 o Build features (backport from 0.3.1.5-alpha):
10394 - Tor's repository now includes a Travis Continuous Integration (CI)
10395 configuration file (.travis.yml). This is meant to help new
10396 developers and contributors who fork Tor to a Github repository be
10397 better able to test their changes, and understand what we expect
10398 to pass. To use this new build feature, you must fork Tor to your
10399 Github account, then go into the "Integrations" menu in the
10400 repository settings for your fork and enable Travis, then push
10401 your changes. Closes ticket 22636.
10404 Changes in version 0.2.9.12 - 2017-09-18
10405 Tor 0.2.9.12 backports a collection of bugfixes from later
10408 Most significantly, it includes a fix for TROVE-2017-008, a
10409 security bug that affects hidden services running with the
10410 SafeLogging option disabled. For more information, see
10411 https://trac.torproject.org/projects/tor/ticket/23490
10413 o Major features (security, backport from 0.3.0.2-alpha):
10414 - Change the algorithm used to decide DNS TTLs on client and server
10415 side, to better resist DNS-based correlation attacks like the
10416 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10417 Feamster. Now relays only return one of two possible DNS TTL
10418 values, and clients are willing to believe DNS TTL values up to 3
10419 hours long. Closes ticket 19769.
10421 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
10422 - Fix a rare crash when sending a begin cell on a circuit whose
10423 linked directory connection had already been closed. Fixes bug
10424 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
10426 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
10427 - Fix a bug that prevented exit nodes from caching DNS records for
10428 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10430 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10431 - Fix a typo that had prevented TPROXY-based transparent proxying
10432 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10433 Patch from "d4fq0fQAgoJ".
10435 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10436 - Avoid an assertion failure bug affecting our implementation of
10437 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10438 handling of "0xx" differs from what we had expected. Fixes bug
10439 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10441 o Minor features (code style, backport from 0.3.1.3-alpha):
10442 - Add "Falls through" comments to our codebase, in order to silence
10443 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10444 Stieger. Closes ticket 22446.
10446 o Minor features (geoip):
10447 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10450 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
10451 - Roll over monthly accounting at the configured hour and minute,
10452 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10453 Found by Andrey Karpov with PVS-Studio.
10455 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
10456 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10457 bugfix on 0.2.8.1-alpha.
10458 - Fix warnings when building with libscrypt and openssl scrypt support
10459 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10460 - When building with certain versions the mingw C header files, avoid
10461 float-conversion warnings when calling the C functions isfinite(),
10462 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
10464 o Minor bugfixes (compilation, backport from 0.3.1.7):
10465 - Avoid compiler warnings in the unit tests for running tor_sscanf()
10466 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10468 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10469 - Backport a fix for an "unused variable" warning that appeared
10470 in some versions of mingw. Fixes bug 22838; bugfix on
10473 o Minor bugfixes (controller, backport from 0.3.1.7):
10474 - Do not crash when receiving a HSPOST command with an empty body.
10475 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10476 - Do not crash when receiving a POSTDESCRIPTOR command with an
10477 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10479 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10480 - Avoid Coverity build warnings related to our BUG() macro. By
10481 default, Coverity treats BUG() as the Linux kernel does: an
10482 instant abort(). We need to override that so our BUG() macro
10483 doesn't prevent Coverity from analyzing functions that use it.
10484 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10486 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10487 - Fix a memset() off the end of an array when packing cells. This
10488 bug should be harmless in practice, since the corrupted bytes are
10489 still in the same structure, and are always padding bytes,
10490 ignored, or immediately overwritten, depending on compiler
10491 behavior. Nevertheless, because the memset()'s purpose is to make
10492 sure that any other cell-handling bugs can't expose bytes to the
10493 network, we need to fix it. Fixes bug 22737; bugfix on
10494 0.2.4.11-alpha. Fixes CID 1401591.
10496 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10497 - When setting the maximum number of connections allowed by the OS,
10498 always allow some extra file descriptors for other files. Fixes
10499 bug 22797; bugfix on 0.2.0.10-alpha.
10501 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10502 - Avoid a sandbox failure when trying to re-bind to a socket and
10503 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10505 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10506 - Permit the fchmod system call, to avoid crashing on startup when
10507 starting with the seccomp2 sandbox and an unexpected set of
10508 permissions on the data directory or its contents. Fixes bug
10509 22516; bugfix on 0.2.5.4-alpha.
10511 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
10512 - Avoid a double-marked-circuit warning that could happen when we
10513 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
10516 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10517 - Reject version numbers with non-numeric prefixes (such as +, -, or
10518 whitespace). Disallowing whitespace prevents differential version
10519 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10520 and part of 21508; bugfix on 0.0.8pre1.
10522 o Build features (backport from 0.3.1.5-alpha):
10523 - Tor's repository now includes a Travis Continuous Integration (CI)
10524 configuration file (.travis.yml). This is meant to help new
10525 developers and contributors who fork Tor to a Github repository be
10526 better able to test their changes, and understand what we expect
10527 to pass. To use this new build feature, you must fork Tor to your
10528 Github account, then go into the "Integrations" menu in the
10529 repository settings for your fork and enable Travis, then push
10530 your changes. Closes ticket 22636.
10533 Changes in version 0.3.0.11 - 2017-09-18
10534 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
10537 Most significantly, it includes a fix for TROVE-2017-008, a
10538 security bug that affects hidden services running with the
10539 SafeLogging option disabled. For more information, see
10540 https://trac.torproject.org/projects/tor/ticket/23490
10542 o Minor features (code style, backport from 0.3.1.7):
10543 - Add "Falls through" comments to our codebase, in order to silence
10544 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10545 Stieger. Closes ticket 22446.
10548 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10551 o Minor bugfixes (compilation, backport from 0.3.1.7):
10552 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10553 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10555 o Minor bugfixes (controller, backport from 0.3.1.7):
10556 - Do not crash when receiving a HSPOST command with an empty body.
10557 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10558 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10559 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10561 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10562 - When setting the maximum number of connections allowed by the OS,
10563 always allow some extra file descriptors for other files. Fixes
10564 bug 22797; bugfix on 0.2.0.10-alpha.
10566 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
10567 - Remove a forgotten debugging message when an introduction point
10568 successfully establishes a hidden service prop224 circuit with
10570 - Change three other log_warn() for an introduction point to
10571 protocol warnings, because they can be failure from the network
10572 and are not relevant to the operator. Fixes bug 23078; bugfix on
10573 0.3.0.1-alpha and 0.3.0.2-alpha.
10576 Changes in version 0.3.1.7 - 2017-09-18
10577 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
10579 With the 0.3.1 series, Tor now serves and downloads directory
10580 information in more compact formats, to save on bandwidth overhead. It
10581 also contains a new padding system to resist netflow-based traffic
10582 analysis, and experimental support for building parts of Tor in Rust
10583 (though no parts of Tor are in Rust yet). There are also numerous
10584 small features, bugfixes on earlier release series, and groundwork for
10585 the hidden services revamp of 0.3.2.
10587 This release also includes a fix for TROVE-2017-008, a security bug
10588 that affects hidden services running with the SafeLogging option
10589 disabled. For more information, see
10590 https://trac.torproject.org/projects/tor/ticket/23490
10592 Per our stable release policy, we plan to support each stable release
10593 series for at least the next nine months, or for three months after
10594 the first stable release of the next series: whichever is longer. If
10595 you need a release with long-term support, we recommend that you stay
10596 with the 0.2.9 series.
10598 Below is a list of the changes since 0.3.1.6-rc. For a list of all
10599 changes since 0.3.0, see the ReleaseNotes file.
10601 o Major bugfixes (security, hidden services, loggging):
10602 - Fix a bug where we could log uninitialized stack when a certain
10603 hidden service error occurred while SafeLogging was disabled.
10604 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
10605 TROVE-2017-008 and CVE-2017-0380.
10607 o Minor features (defensive programming):
10608 - Create a pair of consensus parameters, nf_pad_tor2web and
10609 nf_pad_single_onion, to disable netflow padding in the consensus
10610 for non-anonymous connections in case the overhead is high. Closes
10613 o Minor features (diagnostic):
10614 - Add a stack trace to the bug warnings that can be logged when
10615 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
10616 attempt for bug 23105.
10618 o Minor features (geoip):
10619 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10622 o Minor bugfixes (compilation):
10623 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10624 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10626 o Minor bugfixes (controller):
10627 - Do not crash when receiving a HSPOST command with an empty body.
10628 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10629 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10630 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10632 o Minor bugfixes (relay):
10633 - Inform the geoip and rephist modules about all requests, even on
10634 relays that are only fetching microdescriptors. Fixes a bug
10635 related to 21585; bugfix on 0.3.0.1-alpha.
10637 o Minor bugfixes (unit tests):
10638 - Fix a channelpadding unit test failure on slow systems by using
10639 mocked time instead of actual time. Fixes bug 23077; bugfix
10643 Changes in version 0.3.1.6-rc - 2017-09-05
10644 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
10645 release series, including a bug that produced weird behavior on
10646 Windows directory caches.
10648 This is the first release candidate in the Tor 0.3.1 series. If we
10649 find no new bugs or regressions here, the first stable 0.3.1 release
10650 will be nearly identical to it.
10652 o Major bugfixes (windows, directory cache):
10653 - On Windows, do not try to delete cached consensus documents and
10654 diffs before they are unmapped from memory--Windows won't allow
10655 that. Instead, allow the consensus cache directory to grow larger,
10656 to hold files that might need to stay around longer. Fixes bug
10657 22752; bugfix on 0.3.1.1-alpha.
10659 o Minor features (directory authority):
10660 - Improve the message that authorities report to relays that present
10661 RSA/Ed25519 keypairs that conflict with previously pinned keys.
10662 Closes ticket 22348.
10664 o Minor features (geoip):
10665 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
10668 o Minor features (testing):
10669 - Add more tests for compression backend initialization. Closes
10672 o Minor bugfixes (directory cache):
10673 - Fix a memory leak when recovering space in the consensus cache.
10674 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
10676 o Minor bugfixes (hidden service):
10677 - Increase the number of circuits that a service is allowed to
10678 open over a specific period of time. The value was lower than it
10679 should be (8 vs 12) in the normal case of 3 introduction points.
10680 Fixes bug 22159; bugfix on 0.3.0.5-rc.
10681 - Fix a BUG warning during HSv3 descriptor decoding that could be
10682 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
10683 on 0.3.0.1-alpha. Bug found by "haxxpop".
10684 - Rate-limit the log messages if we exceed the maximum number of
10685 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
10687 o Minor bugfixes (logging, relay):
10688 - Remove a forgotten debugging message when an introduction point
10689 successfully establishes a hidden service prop224 circuit with
10691 - Change three other log_warn() for an introduction point to
10692 protocol warnings, because they can be failure from the network
10693 and are not relevant to the operator. Fixes bug 23078; bugfix on
10694 0.3.0.1-alpha and 0.3.0.2-alpha.
10696 o Minor bugfixes (relay):
10697 - When a relay is not running as a directory cache, it will no
10698 longer generate compressed consensuses and consensus diff
10699 information. Previously, this was a waste of disk and CPU. Fixes
10700 bug 23275; bugfix on 0.3.1.1-alpha.
10702 o Minor bugfixes (robustness, error handling):
10703 - Improve our handling of the cases where OpenSSL encounters a
10704 memory error while encoding keys and certificates. We haven't
10705 observed these errors in the wild, but if they do happen, we now
10706 detect and respond better. Fixes bug 19418; bugfix on all versions
10707 of Tor. Reported by Guido Vranken.
10709 o Minor bugfixes (stability):
10710 - Avoid crashing on a double-free when unable to load or process an
10711 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
10712 with the clang static analyzer.
10714 o Minor bugfixes (testing):
10715 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10716 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10717 - Port the hs_ntor handshake test to work correctly with recent
10718 versions of the pysha3 module. Fixes bug 23071; bugfix
10721 o Minor bugfixes (Windows service):
10722 - When running as a Windows service, set the ID of the main thread
10723 correctly. Failure to do so made us fail to send log messages to
10724 the controller in 0.2.1.16-rc, slowed down controller event
10725 delivery in 0.2.7.3-rc and later, and crash with an assertion
10726 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10727 Patch and diagnosis from "Vort".
10730 Changes in version 0.3.0.10 - 2017-08-02
10731 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
10732 from the current Tor alpha series. OpenBSD users and TPROXY users
10733 should upgrade; others are probably okay sticking with 0.3.0.9.
10735 o Major features (build system, continuous integration, 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.
10745 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10746 - Fix a typo that had prevented TPROXY-based transparent proxying
10747 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10748 Patch from "d4fq0fQAgoJ".
10750 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10751 - Avoid an assertion failure bug affecting our implementation of
10752 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10753 handling of "0xbar" differs from what we had expected. Fixes bug
10754 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10756 o Minor features (backport from 0.3.1.5-alpha):
10757 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
10760 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
10761 - Roll over monthly accounting at the configured hour and minute,
10762 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10763 Found by Andrey Karpov with PVS-Studio.
10765 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
10766 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10767 bugfix on 0.2.8.1-alpha.
10768 - Fix warnings when building with libscrypt and openssl scrypt
10769 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10770 - When building with certain versions of the mingw C header files,
10771 avoid float-conversion warnings when calling the C functions
10772 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10775 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10776 - Backport a fix for an "unused variable" warning that appeared
10777 in some versions of mingw. Fixes bug 22838; bugfix on
10780 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10781 - Avoid Coverity build warnings related to our BUG() macro. By
10782 default, Coverity treats BUG() as the Linux kernel does: an
10783 instant abort(). We need to override that so our BUG() macro
10784 doesn't prevent Coverity from analyzing functions that use it.
10785 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10787 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
10788 - When rejecting a router descriptor for running an obsolete version
10789 of Tor without ntor support, warn about the obsolete tor version,
10790 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
10792 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10793 - Avoid a sandbox failure when trying to re-bind to a socket and
10794 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10796 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
10797 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10798 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10801 Changes in version 0.3.1.5-alpha - 2017-08-01
10802 Tor 0.3.1.5-alpha improves the performance of consensus diff
10803 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
10804 several other bugs. If no serious bugs are found in this version, the
10805 next version will be a release candidate.
10807 This release also marks the end of support for the Tor 0.2.4.x,
10808 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
10809 further bug or security fixes. Anyone still running or distributing
10810 one of those versions should upgrade.
10812 o Major features (build system, continuous integration):
10813 - Tor's repository now includes a Travis Continuous Integration (CI)
10814 configuration file (.travis.yml). This is meant to help new
10815 developers and contributors who fork Tor to a Github repository be
10816 better able to test their changes, and understand what we expect
10817 to pass. To use this new build feature, you must fork Tor to your
10818 Github account, then go into the "Integrations" menu in the
10819 repository settings for your fork and enable Travis, then push
10820 your changes. Closes ticket 22636.
10822 o Major bugfixes (openbsd, denial-of-service):
10823 - Avoid an assertion failure bug affecting our implementation of
10824 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10825 handling of "0xbar" differs from what we had expected. Fixes bug
10826 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10828 o Major bugfixes (relay, performance):
10829 - Perform circuit handshake operations at a higher priority than we
10830 use for consensus diff creation and compression. This should
10831 prevent circuits from starving when a relay or bridge receives a
10832 new consensus, especially on lower-powered machines. Fixes bug
10833 22883; bugfix on 0.3.1.1-alpha.
10835 o Minor features (bridge authority):
10836 - Add "fingerprint" lines to the networkstatus-bridges file produced
10837 by bridge authorities. Closes ticket 22207.
10839 o Minor features (directory cache, consensus diff):
10840 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
10841 operators with low-resource environments to adjust the number of
10842 consensuses they'll store and generate diffs from. Most cache
10843 operators should leave it unchanged. Helps to work around
10846 o Minor features (geoip):
10847 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
10850 o Minor features (relay, performance):
10851 - Always start relays with at least two worker threads, to prevent
10852 priority inversion on slow tasks. Part of the fix for bug 22883.
10853 - Allow background work to be queued with different priorities, so
10854 that a big pile of slow low-priority jobs will not starve out
10855 higher priority jobs. This lays the groundwork for a fix for
10858 o Minor bugfixes (build system, rust):
10859 - Fix a problem where Rust toolchains were not being found when
10860 building without --enable-cargo-online-mode, due to setting the
10861 $HOME environment variable instead of $CARGO_HOME. Fixes bug
10862 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
10864 o Minor bugfixes (compatibility, zstd):
10865 - Write zstd epilogues correctly when the epilogue requires
10866 reallocation of the output buffer, even with zstd 1.3.0.
10867 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
10868 22927; bugfix on 0.3.1.1-alpha.
10870 o Minor bugfixes (compilation warnings):
10871 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
10872 22915; bugfix on 0.2.8.1-alpha.
10873 - Fix warnings when building with libscrypt and openssl scrypt
10874 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10875 - Compile correctly when both openssl 1.1.0 and libscrypt are
10876 detected. Previously this would cause an error. Fixes bug 22892;
10877 bugfix on 0.3.1.1-alpha.
10878 - When building with certain versions of the mingw C header files,
10879 avoid float-conversion warnings when calling the C functions
10880 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10883 o Minor bugfixes (coverity build support):
10884 - Avoid Coverity build warnings related to our BUG() macro. By
10885 default, Coverity treats BUG() as the Linux kernel does: an
10886 instant abort(). We need to override that so our BUG() macro
10887 doesn't prevent Coverity from analyzing functions that use it.
10888 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10890 o Minor bugfixes (directory authority):
10891 - When a directory authority rejects a descriptor or extrainfo with
10892 a given digest, mark that digest as undownloadable, so that we do
10893 not attempt to download it again over and over. We previously
10894 tried to avoid downloading such descriptors by other means, but we
10895 didn't notice if we accidentally downloaded one anyway. This
10896 behavior became problematic in 0.2.7.2-alpha, when authorities
10897 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10900 o Minor bugfixes (error reporting, windows):
10901 - When formatting Windows error messages, use the English format to
10902 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
10905 o Minor bugfixes (file limits, osx):
10906 - When setting the maximum number of connections allowed by the OS,
10907 always allow some extra file descriptors for other files. Fixes
10908 bug 22797; bugfix on 0.2.0.10-alpha.
10910 o Minor bugfixes (linux seccomp2 sandbox):
10911 - Avoid a sandbox failure when trying to re-bind to a socket and
10912 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10914 o Minor bugfixes (memory leaks):
10915 - Fix a small memory leak when validating a configuration that uses
10916 two or more AF_UNIX sockets for the same port type. Fixes bug
10917 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
10919 o Minor bugfixes (unit tests):
10920 - test_consdiff_base64cmp would fail on OS X because while OS X
10921 follows the standard of (less than zero/zero/greater than zero),
10922 it doesn't follow the convention of (-1/0/+1). Make the test
10923 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
10924 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10925 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10928 Changes in version 0.3.1.4-alpha - 2017-06-29
10929 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
10930 to use a guard that was in the same network family as a chosen exit
10931 relay. This is a security regression; all clients running earlier
10932 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
10935 This release also fixes several other bugs introduced in 0.3.0.x
10936 and 0.3.1.x, including others that can affect bandwidth usage
10939 o New dependencies:
10940 - To build with zstd and lzma support, Tor now requires the
10941 pkg-config tool at build time. (This requirement was new in
10942 0.3.1.1-alpha, but was not noted at the time. Noting it here to
10943 close ticket 22623.)
10945 o Major bugfixes (path selection, security):
10946 - When choosing which guard to use for a circuit, avoid the exit's
10947 family along with the exit itself. Previously, the new guard
10948 selection logic avoided the exit, but did not consider its family.
10949 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
10950 006 and CVE-2017-0377.
10952 o Major bugfixes (compression, zstd):
10953 - Correctly detect a full buffer when decompressing a large zstd-
10954 compressed input. Previously, we would sometimes treat a full
10955 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
10957 o Major bugfixes (directory protocol):
10958 - Ensure that we send "304 Not modified" as HTTP status code when a
10959 client is attempting to fetch a consensus or consensus diff, and
10960 the best one we can send them is one they already have. Fixes bug
10961 22702; bugfix on 0.3.1.1-alpha.
10963 o Major bugfixes (entry guards):
10964 - When starting with an old consensus, do not add new entry guards
10965 unless the consensus is "reasonably live" (under 1 day old). Fixes
10966 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
10968 o Minor features (bug mitigation, diagnostics, logging):
10969 - Avoid an assertion failure, and log a better error message, when
10970 unable to remove a file from the consensus cache on Windows.
10971 Attempts to mitigate and diagnose bug 22752.
10973 o Minor features (geoip):
10974 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
10977 o Minor bugfixes (compression):
10978 - When compressing or decompressing a buffer, check for a failure to
10979 create a compression object. Fixes bug 22626; bugfix
10981 - When decompressing a buffer, check for extra data after the end of
10982 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
10983 - When decompressing an object received over an anonymous directory
10984 connection, if we have already decompressed it using an acceptable
10985 compression method, do not reject it for looking like an
10986 unacceptable compression method. Fixes part of bug 22670; bugfix
10988 - When serving directory votes compressed with zlib, do not claim to
10989 have compressed them with zstd. Fixes bug 22669; bugfix
10991 - When spooling compressed data to an output buffer, don't try to
10992 spool more data when there is no more data to spool and we are not
10993 trying to flush the input. Previously, we would sometimes launch
10994 compression requests with nothing to do, which interferes with our
10995 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
10997 o Minor bugfixes (defensive programming):
10998 - Detect and break out of infinite loops in our compression code. We
10999 don't think that any such loops exist now, but it's best to be
11000 safe. Closes ticket 22672.
11001 - Fix a memset() off the end of an array when packing cells. This
11002 bug should be harmless in practice, since the corrupted bytes are
11003 still in the same structure, and are always padding bytes,
11004 ignored, or immediately overwritten, depending on compiler
11005 behavior. Nevertheless, because the memset()'s purpose is to make
11006 sure that any other cell-handling bugs can't expose bytes to the
11007 network, we need to fix it. Fixes bug 22737; bugfix on
11008 0.2.4.11-alpha. Fixes CID 1401591.
11010 o Minor bugfixes (linux seccomp2 sandbox):
11011 - Permit the fchmod system call, to avoid crashing on startup when
11012 starting with the seccomp2 sandbox and an unexpected set of
11013 permissions on the data directory or its contents. Fixes bug
11014 22516; bugfix on 0.2.5.4-alpha.
11015 - Fix a crash in the LZMA module, when the sandbox was enabled, and
11016 liblzma would allocate more than 16 MB of memory. We solve this by
11017 bumping the mprotect() limit in the sandbox module from 16 MB to
11018 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
11020 o Minor bugfixes (logging):
11021 - When decompressing, do not warn if we fail to decompress using a
11022 compression method that we merely guessed. Fixes part of bug
11023 22670; bugfix on 0.1.1.14-alpha.
11024 - When decompressing, treat mismatch between content-encoding and
11025 actual compression type as a protocol warning. Fixes part of bug
11026 22670; bugfix on 0.1.1.9-alpha.
11027 - Downgrade "assigned_to_cpuworker failed" message to info-level
11028 severity. In every case that can reach it, either a better warning
11029 has already been logged, or no warning is warranted. Fixes bug
11030 22356; bugfix on 0.2.6.3-alpha.
11031 - Demote a warn that was caused by libevent delays to info if
11032 netflow padding is less than 4.5 seconds late, or to notice
11033 if it is more (4.5 seconds is the amount of time that a netflow
11034 record might be emitted after, if we chose the maximum timeout).
11035 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
11037 o Minor bugfixes (process behavior):
11038 - When exiting because of an error, always exit with a nonzero exit
11039 status. Previously, we would fail to report an error in our exit
11040 status in cases related to __OwningControllerProcess failure,
11041 lockfile contention, and Ed25519 key initialization. Fixes bug
11042 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
11043 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
11047 - Add a manpage description for the key-pinning-journal file. Closes
11049 - Correctly note that bandwidth accounting values are stored in the
11050 state file, and the bw_accounting file is now obsolete. Closes
11052 - Document more of the files in the Tor data directory, including
11053 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
11054 approved-routers, sr-random, and diff-cache. Found while fixing
11058 Changes in version 0.3.0.9 - 2017-06-29
11059 Tor 0.3.0.9 fixes a path selection bug that would allow a client
11060 to use a guard that was in the same network family as a chosen exit
11061 relay. This is a security regression; all clients running earlier
11062 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
11065 This release also backports several other bugfixes from the 0.3.1.x
11068 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
11069 - When choosing which guard to use for a circuit, avoid the exit's
11070 family along with the exit itself. Previously, the new guard
11071 selection logic avoided the exit, but did not consider its family.
11072 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11073 006 and CVE-2017-0377.
11075 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
11076 - Don't block bootstrapping when a primary bridge is offline and we
11077 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11078 21969; bugfix on 0.3.0.3-alpha.
11080 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
11081 - When starting with an old consensus, do not add new entry guards
11082 unless the consensus is "reasonably live" (under 1 day old). Fixes
11083 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11085 o Minor features (geoip):
11086 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11089 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
11090 - Reject version numbers with non-numeric prefixes (such as +, -, or
11091 whitespace). Disallowing whitespace prevents differential version
11092 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11093 and part of 21508; bugfix on 0.0.8pre1.
11095 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
11096 - Permit the fchmod system call, to avoid crashing on startup when
11097 starting with the seccomp2 sandbox and an unexpected set of
11098 permissions on the data directory or its contents. Fixes bug
11099 22516; bugfix on 0.2.5.4-alpha.
11101 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
11102 - Fix a memset() off the end of an array when packing cells. This
11103 bug should be harmless in practice, since the corrupted bytes are
11104 still in the same structure, and are always padding bytes,
11105 ignored, or immediately overwritten, depending on compiler
11106 behavior. Nevertheless, because the memset()'s purpose is to make
11107 sure that any other cell-handling bugs can't expose bytes to the
11108 network, we need to fix it. Fixes bug 22737; bugfix on
11109 0.2.4.11-alpha. Fixes CID 1401591.
11112 Changes in version 0.3.1.3-alpha - 2017-06-08
11113 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
11114 remotely crash a hidden service with an assertion failure. Anyone
11115 running a hidden service should upgrade to this version, or to some
11116 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11118 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
11119 that sometimes made relays unreliable, as well as several other
11120 bugfixes described below.
11122 o Major bugfixes (hidden service, relay, security):
11123 - Fix a remotely triggerable assertion failure when a hidden service
11124 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11125 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11126 - Fix a remotely triggerable assertion failure caused by receiving a
11127 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11128 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11131 o Major bugfixes (relay, link handshake):
11132 - When performing the v3 link handshake on a TLS connection, report
11133 that we have the x509 certificate that we actually used on that
11134 connection, even if we have changed certificates since that
11135 connection was first opened. Previously, we would claim to have
11136 used our most recent x509 link certificate, which would sometimes
11137 make the link handshake fail. Fixes one case of bug 22460; bugfix
11140 o Major bugfixes (relays, key management):
11141 - Regenerate link and authentication certificates whenever the key
11142 that signs them changes; also, regenerate link certificates
11143 whenever the signed key changes. Previously, these processes were
11144 only weakly coupled, and we relays could (for minutes to hours)
11145 wind up with an inconsistent set of keys and certificates, which
11146 other relays would not accept. Fixes two cases of bug 22460;
11147 bugfix on 0.3.0.1-alpha.
11148 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11149 send the certificate that matches the x509 certificate that we
11150 used on the TLS connection. Previously, there was a race condition
11151 if the TLS context rotated after we began the TLS handshake but
11152 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11155 o Major bugfixes (torrc, crash):
11156 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
11157 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
11159 o Minor features (code style):
11160 - Add "Falls through" comments to our codebase, in order to silence
11161 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11162 Stieger. Closes ticket 22446.
11164 o Minor features (diagnostic):
11165 - Add logging messages to try to diagnose a rare bug that seems to
11166 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
11167 think this is happening because of incorrect system clocks, but
11168 we'd like to know for certain. Diagnostic for bug 22466.
11170 o Minor bugfixes (correctness):
11171 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11172 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11174 o Minor bugfixes (directory protocol):
11175 - Check for libzstd >= 1.1, because older versions lack the
11176 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
11178 o Minor bugfixes (link handshake):
11179 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11180 months, and regenerate it when it is within one month of expiring.
11181 Previously, we had generated this certificate at startup with a
11182 ten-year lifetime, but that could lead to weird behavior when Tor
11183 was started with a grossly inaccurate clock. Mitigates bug 22466;
11184 mitigation on 0.3.0.1-alpha.
11186 o Minor bugfixes (storage directories):
11187 - Always check for underflows in the cached storage directory usage.
11188 If the usage does underflow, re-calculate it. Also, avoid a
11189 separate underflow when the usage is not known. Fixes bug 22424;
11190 bugfix on 0.3.1.1-alpha.
11192 o Minor bugfixes (unit tests):
11193 - The unit tests now pass on systems where localhost is misconfigured
11194 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
11198 - Clarify the manpage for the (deprecated) torify script. Closes
11201 Changes in version 0.3.0.8 - 2017-06-08
11202 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
11203 remotely crash a hidden service with an assertion failure. Anyone
11204 running a hidden service should upgrade to this version, or to some
11205 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11207 Tor 0.3.0.8 also includes fixes for several key management bugs
11208 that sometimes made relays unreliable, as well as several other
11209 bugfixes described below.
11211 o Major bugfixes (hidden service, relay, security, backport
11212 from 0.3.1.3-alpha):
11213 - Fix a remotely triggerable assertion failure when a hidden service
11214 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11215 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11216 - Fix a remotely triggerable assertion failure caused by receiving a
11217 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11218 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11221 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11222 - When performing the v3 link handshake on a TLS connection, report
11223 that we have the x509 certificate that we actually used on that
11224 connection, even if we have changed certificates since that
11225 connection was first opened. Previously, we would claim to have
11226 used our most recent x509 link certificate, which would sometimes
11227 make the link handshake fail. Fixes one case of bug 22460; bugfix
11230 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
11231 - Regenerate link and authentication certificates whenever the key
11232 that signs them changes; also, regenerate link certificates
11233 whenever the signed key changes. Previously, these processes were
11234 only weakly coupled, and we relays could (for minutes to hours)
11235 wind up with an inconsistent set of keys and certificates, which
11236 other relays would not accept. Fixes two cases of bug 22460;
11237 bugfix on 0.3.0.1-alpha.
11238 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11239 send the certificate that matches the x509 certificate that we
11240 used on the TLS connection. Previously, there was a race condition
11241 if the TLS context rotated after we began the TLS handshake but
11242 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11245 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
11246 - Stop rejecting v3 hidden service descriptors because their size
11247 did not match an old padding rule. Fixes bug 22447; bugfix on
11250 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11251 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11252 December 2016 (of which ~126 were still functional) with a list of
11253 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11254 2017. Resolves ticket 21564.
11256 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
11257 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11258 bug 22252; bugfix on 0.2.9.3-alpha.
11260 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11261 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11262 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11264 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
11265 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11266 months, and regenerate it when it is within one month of expiring.
11267 Previously, we had generated this certificate at startup with a
11268 ten-year lifetime, but that could lead to weird behavior when Tor
11269 was started with a grossly inaccurate clock. Mitigates bug 22466;
11270 mitigation on 0.3.0.1-alpha.
11272 o Minor bugfixes (memory leak, directory authority, backport from
11274 - When directory authorities reject a router descriptor due to
11275 keypinning, free the router descriptor rather than leaking the
11276 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11279 Changes in version 0.2.9.11 - 2017-06-08
11280 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
11281 remotely crash a hidden service with an assertion failure. Anyone
11282 running a hidden service should upgrade to this version, or to some
11283 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11284 are not affected by TROVE-2017-004.)
11286 Tor 0.2.9.11 also backports fixes for several key management bugs
11287 that sometimes made relays unreliable, as well as several other
11288 bugfixes described below.
11290 o Major bugfixes (hidden service, relay, security, backport
11291 from 0.3.1.3-alpha):
11292 - Fix a remotely triggerable assertion failure caused by receiving a
11293 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11294 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11297 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11298 - When performing the v3 link handshake on a TLS connection, report
11299 that we have the x509 certificate that we actually used on that
11300 connection, even if we have changed certificates since that
11301 connection was first opened. Previously, we would claim to have
11302 used our most recent x509 link certificate, which would sometimes
11303 make the link handshake fail. Fixes one case of bug 22460; bugfix
11306 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11307 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11308 December 2016 (of which ~126 were still functional) with a list of
11309 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11310 2017. Resolves ticket 21564.
11312 o Minor features (future-proofing, backport from 0.3.0.7):
11313 - Tor no longer refuses to download microdescriptors or descriptors if
11314 they are listed as "published in the future". This change will
11315 eventually allow us to stop listing meaningful "published" dates
11316 in microdescriptor consensuses, and thereby allow us to reduce the
11317 resources required to download consensus diffs by over 50%.
11318 Implements part of ticket 21642; implements part of proposal 275.
11320 o Minor features (directory authorities, backport from 0.3.0.4-rc)
11321 - Directory authorities now reject relays running versions
11322 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
11323 suffer from bug 20499 and don't keep their consensus cache
11324 up-to-date. Resolves ticket 20509.
11326 o Minor features (geoip):
11327 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11330 o Minor bugfixes (control port, backport from 0.3.0.6):
11331 - The GETINFO extra-info/digest/<digest> command was broken because
11332 of a wrong base16 decode return value check, introduced when
11333 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11335 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11336 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11337 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11339 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
11340 - The getpid() system call is now permitted under the Linux seccomp2
11341 sandbox, to avoid crashing with versions of OpenSSL (and other
11342 libraries) that attempt to learn the process's PID by using the
11343 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11346 o Minor bugfixes (memory leak, directory authority, backport
11347 from 0.3.1.2-alpha):
11348 - When directory authorities reject a router descriptor due to
11349 keypinning, free the router descriptor rather than leaking the
11350 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11352 Changes in version 0.2.8.14 - 2017-06-08
11353 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11354 remotely crash a hidden service with an assertion failure. Anyone
11355 running a hidden service should upgrade to this version, or to some
11356 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11357 are not affected by TROVE-2017-004.)
11359 o Major bugfixes (hidden service, relay, security):
11360 - Fix a remotely triggerable assertion failure caused by receiving a
11361 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11362 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11365 o Minor features (geoip):
11366 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11369 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11370 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11371 December 2016 (of which ~126 were still functional) with a list of
11372 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11373 2017. Resolves ticket 21564.
11375 o Minor bugfixes (correctness):
11376 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11377 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11379 Changes in version 0.2.7.8 - 2017-06-08
11380 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11381 remotely crash a hidden service with an assertion failure. Anyone
11382 running a hidden service should upgrade to this version, or to some
11383 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11384 are not affected by TROVE-2017-004.)
11386 o Major bugfixes (hidden service, relay, security):
11387 - Fix a remotely triggerable assertion failure caused by receiving a
11388 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11389 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11392 o Minor features (geoip):
11393 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11396 o Minor bugfixes (correctness):
11397 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11398 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11401 Changes in version 0.2.6.12 - 2017-06-08
11402 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
11403 remotely crash a hidden service with an assertion failure. Anyone
11404 running a hidden service should upgrade to this version, or to some
11405 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11406 are not affected by TROVE-2017-004.)
11408 o Major bugfixes (hidden service, relay, security):
11409 - Fix a remotely triggerable assertion failure caused by receiving a
11410 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11411 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11414 o Minor features (geoip):
11415 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11418 o Minor bugfixes (correctness):
11419 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11420 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11422 Changes in version 0.2.5.14 - 2017-06-08
11423 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
11424 remotely crash a hidden service with an assertion failure. Anyone
11425 running a hidden service should upgrade to this version, or to some
11426 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11427 are not affected by TROVE-2017-004.)
11429 o Major bugfixes (hidden service, relay, security):
11430 - Fix a remotely triggerable assertion failure caused by receiving a
11431 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11432 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11435 o Minor features (geoip):
11436 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11439 o Minor bugfixes (correctness):
11440 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11441 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11443 Changes in version 0.2.4.29 - 2017-06-08
11444 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
11445 remotely crash a hidden service with an assertion failure. Anyone
11446 running a hidden service should upgrade to this version, or to some
11447 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11448 are not affected by TROVE-2017-004.)
11450 o Major bugfixes (hidden service, relay, security):
11451 - Fix a remotely triggerable assertion failure caused by receiving a
11452 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11453 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11456 o Minor features (geoip):
11457 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11460 o Minor bugfixes (correctness):
11461 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11462 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11465 Changes in version 0.3.1.2-alpha - 2017-05-26
11466 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
11467 fixes a few bugs found while testing 0.3.1.1-alpha, including a
11468 memory corruption bug that affected relay stability.
11470 o Major bugfixes (crash, relay):
11471 - Fix a memory-corruption bug in relays that set MyFamily.
11472 Previously, they would double-free MyFamily elements when making
11473 the next descriptor or when changing their configuration. Fixes
11474 bug 22368; bugfix on 0.3.1.1-alpha.
11476 o Minor bugfixes (logging):
11477 - Log a better message when a directory authority replies to an
11478 upload with an unexpected status code. Fixes bug 11121; bugfix
11481 o Minor bugfixes (memory leak, directory authority):
11482 - When directory authorities reject a router descriptor due to
11483 keypinning, free the router descriptor rather than leaking the
11484 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11487 Changes in version 0.3.1.1-alpha - 2017-05-22
11488 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
11489 reduces the bandwidth usage for Tor's directory protocol, adds some
11490 basic padding to resist netflow-based traffic analysis and to serve as
11491 the basis of other padding in the future, and adds rust support to the
11494 It also contains numerous other small features and improvements to
11495 security, correctness, and performance.
11497 Below are the changes since 0.3.0.7.
11499 o Major features (directory protocol):
11500 - Tor relays and authorities can now serve clients an abbreviated
11501 version of the consensus document, containing only the changes
11502 since an older consensus document that the client holds. Clients
11503 now request these documents when available. When both client and
11504 server use this new protocol, they will use far less bandwidth (up
11505 to 94% less) to keep the client's consensus up-to-date. Implements
11506 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
11507 - Tor can now compress directory traffic with lzma or with zstd
11508 compression algorithms, which can deliver better bandwidth
11509 performance. Because lzma is computationally expensive, it's only
11510 used for documents that can be compressed once and served many
11511 times. Support for these algorithms requires that tor is built
11512 with the libzstd and/or liblzma libraries available. Implements
11513 proposal 278; closes ticket 21662.
11514 - Relays now perform the more expensive compression operations, and
11515 consensus diff generation, in worker threads. This separation
11516 avoids delaying the main thread when a new consensus arrives.
11518 o Major features (experimental):
11519 - Tor can now build modules written in Rust. To turn this on, pass
11520 the "--enable-rust" flag to the configure script. It's not time to
11521 get excited yet: currently, there is no actual Rust functionality
11522 beyond some simple glue code, and a notice at startup to tell you
11523 that Rust is running. Still, we hope that programmers and
11524 packagers will try building Tor with Rust support, so that we can
11525 find issues and solve portability problems. Closes ticket 22106.
11527 o Major features (traffic analysis resistance):
11528 - Connections between clients and relays now send a padding cell in
11529 each direction every 1.5 to 9.5 seconds (tunable via consensus
11530 parameters). This padding will not resist specialized
11531 eavesdroppers, but it should be enough to make many ISPs' routine
11532 network flow logging less useful in traffic analysis against
11535 Padding is negotiated using Tor's link protocol, so both relays
11536 and clients must upgrade for this to take effect. Clients may
11537 still send padding despite the relay's version by setting
11538 ConnectionPadding 1 in torrc, and may disable padding by setting
11539 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
11540 users with the torrc option ReducedConnectionPadding. Implements
11541 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
11542 - Relays will publish 24 hour totals of padding and non-padding cell
11543 counts to their extra-info descriptors, unless PaddingStatistics 0
11544 is set in torrc. These 24 hour totals are also rounded to
11545 multiples of 10000.
11547 o Major bugfixes (connection usage):
11548 - We use NETINFO cells to try to determine if both relays involved
11549 in a connection will agree on the canonical status of that
11550 connection. We prefer the connections where this is the case for
11551 extend cells, and try to close connections where relays disagree
11552 on their canonical status early. Also, we now prefer the oldest
11553 valid connection for extend cells. These two changes should reduce
11554 the number of long-term connections that are kept open between
11555 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
11556 - Relays now log hourly statistics (look for
11557 "channel_check_for_duplicates" lines) on the total number of
11558 connections to other relays. If the number of connections per
11559 relay is unexpectedly large, this log message is at notice level.
11560 Otherwise it is at info.
11562 o Major bugfixes (entry guards):
11563 - Don't block bootstrapping when a primary bridge is offline and we
11564 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11565 21969; bugfix on 0.3.0.3-alpha.
11567 o Major bugfixes (linux TPROXY support):
11568 - Fix a typo that had prevented TPROXY-based transparent proxying
11569 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11570 Patch from "d4fq0fQAgoJ".
11572 o Minor features (security, windows):
11573 - Enable a couple of pieces of Windows hardening: one
11574 (HeapEnableTerminationOnCorruption) that has been on-by-default
11575 since Windows 8, and unavailable before Windows 7; and one
11576 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11577 affect us, but shouldn't do any harm. Closes ticket 21953.
11579 o Minor features (config options):
11580 - Allow "%include" directives in torrc configuration files. These
11581 directives import the settings from other files, or from all the
11582 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
11583 - Make SAVECONF return an error when overwriting a torrc that has
11584 includes. Using SAVECONF with the FORCE option will allow it to
11585 overwrite torrc even if includes are used. Related to ticket 1922.
11586 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
11587 will work without the FORCE option. Related to ticket 1922.
11589 o Minor features (controller):
11590 - Warn the first time that a controller requests data in the long-
11591 deprecated 'GETINFO network-status' format. Closes ticket 21703.
11593 o Minor features (defaults):
11594 - The default value for UseCreateFast is now 0: clients which
11595 haven't yet received a consensus document will now use a proper
11596 ntor handshake to talk to their directory servers whenever they
11597 can. Closes ticket 21407.
11598 - Onion key rotation and expiry intervals are now defined as a
11599 network consensus parameter, per proposal 274. The default
11600 lifetime of an onion key is increased from 7 to 28 days. Old onion
11601 keys will expire after 7 days by default. This change will make
11602 consensus diffs much smaller, and save significant bandwidth.
11603 Closes ticket 21641.
11605 o Minor features (fallback directory list):
11606 - Update the fallback directory mirror whitelist and blacklist based
11607 on operator emails. Closes task 21121.
11608 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11609 December 2016 (of which ~126 were still functional) with a list of
11610 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11611 2017. Resolves ticket 21564.
11613 o Minor features (hidden services, logging):
11614 - Log a message when a hidden service descriptor has fewer
11615 introduction points than specified in
11616 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
11617 - Log a message when a hidden service reaches its introduction point
11618 circuit limit, and when that limit is reset. Follow up to ticket
11619 21594; closes ticket 21622.
11620 - Warn user if multiple entries in EntryNodes and at least one
11621 HiddenService are used together. Pinning EntryNodes along with a
11622 hidden service can be possibly harmful; for instance see ticket
11623 14917 or 21155. Closes ticket 21155.
11625 o Minor features (linux seccomp2 sandbox):
11626 - We now have a document storage backend compatible with the Linux
11627 seccomp2 sandbox. This backend is used for consensus documents and
11628 diffs between them; in the long term, we'd like to use it for
11629 unparseable directory material too. Closes ticket 21645
11630 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
11631 from 1MB to 16MB. This was necessary with the glibc allocator in
11632 order to allow worker threads to allocate more memory -- which in
11633 turn is necessary because of our new use of worker threads for
11634 compression. Closes ticket 22096.
11636 o Minor features (logging):
11637 - Log files are no longer created world-readable by default.
11638 (Previously, most distributors would store the logs in a non-
11639 world-readable location to prevent inappropriate access. This
11640 change is an extra precaution.) Closes ticket 21729; patch
11643 o Minor features (performance):
11644 - Our Keccak (SHA-3) implementation now accesses memory more
11645 efficiently, especially on little-endian systems. Closes
11647 - Add an O(1) implementation of channel_find_by_global_id(), to
11648 speed some controller functions.
11650 o Minor features (relay, configuration):
11651 - The MyFamily option may now be repeated as many times as desired,
11652 for relays that want to configure large families. Closes ticket
11653 4998; patch by Daniel Pinto.
11655 o Minor features (safety):
11656 - Add an explicit check to extrainfo_parse_entry_from_string() for
11657 NULL inputs. We don't believe this can actually happen, but it may
11658 help silence a warning from the Clang analyzer. Closes
11661 o Minor features (testing):
11662 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
11663 When Tor is compiled with this option, we disable a number of
11664 redundant memory-safety failsafes that are intended to stop bugs
11665 from becoming security issues. This makes it easier to hunt for
11666 bugs that would be security issues without the failsafes turned
11667 on. Closes ticket 21439.
11668 - Add a general event-tracing instrumentation support to Tor. This
11669 subsystem will enable developers and researchers to add fine-
11670 grained instrumentation to their Tor instances, for use when
11671 examining Tor network performance issues. There are no trace
11672 events yet, and event-tracing is off by default unless enabled at
11673 compile time. Implements ticket 13802.
11674 - Improve our version parsing tests: add tests for typical version
11675 components, add tests for invalid versions, including numeric
11676 range and non-numeric prefixes. Unit tests 21278, 21450, and
11677 21507. Partially implements 21470.
11679 o Minor bugfixes (bandwidth accounting):
11680 - Roll over monthly accounting at the configured hour and minute,
11681 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11682 Found by Andrey Karpov with PVS-Studio.
11684 o Minor bugfixes (code correctness):
11685 - Accurately identify client connections by their lack of peer
11686 authentication. This means that we bail out earlier if asked to
11687 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
11690 o Minor bugfixes (configuration):
11691 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11692 bug 22252; bugfix on 0.2.9.3-alpha.
11694 o Minor bugfixes (connection lifespan):
11695 - Allow more control over how long TLS connections are kept open:
11696 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
11697 single option called CircuitsAvailableTimeout. Also, allow the
11698 consensus to control the default values for both this preference
11699 and the lifespan of relay-to-relay connections. Fixes bug 17592;
11700 bugfix on 0.2.5.5-alpha.
11701 - Increase the initial circuit build timeout testing frequency, to
11702 help ensure that ReducedConnectionPadding clients finish learning
11703 a timeout before their orconn would expire. The initial testing
11704 rate was set back in the days of TAP and before the Tor Browser
11705 updater, when we had to be much more careful about new clients
11706 making lots of circuits. With this change, a circuit build timeout
11707 is learned in about 15-20 minutes, instead of 100-120 minutes.
11709 o Minor bugfixes (controller):
11710 - GETINFO onions/current and onions/detached no longer respond with
11711 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
11712 - Trigger HS descriptor events on the control port when the client
11713 fails to pick a hidden service directory for a hidden service.
11714 This can happen if all the hidden service directories are in
11715 ExcludeNodes, or they have all been queried within the last 15
11716 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
11718 o Minor bugfixes (directory authority):
11719 - When rejecting a router descriptor for running an obsolete version
11720 of Tor without ntor support, warn about the obsolete tor version,
11721 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11722 - Prevent the shared randomness subsystem from asserting when
11723 initialized by a bridge authority with an incomplete configuration
11724 file. Fixes bug 21586; bugfix on 0.2.9.8.
11726 o Minor bugfixes (exit-side DNS):
11727 - Fix an untriggerable assertion that checked the output of a
11728 libevent DNS error, so that the assertion actually behaves as
11729 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
11730 Karpov using PVS-Studio.
11732 o Minor bugfixes (fallback directories):
11733 - Make the usage example in updateFallbackDirs.py actually work, and
11734 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
11735 - Decrease the guard flag average required to be a fallback. This
11736 allows us to keep relays that have their guard flag removed when
11737 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11738 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
11739 bugfix on 0.2.8.1-alpha.
11740 - Make sure fallback directory mirrors have the same address, port,
11741 and relay identity key for at least 30 days before they are
11742 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11744 o Minor bugfixes (hidden services):
11745 - Stop printing a cryptic warning when a hidden service gets a
11746 request to connect to a virtual port that it hasn't configured.
11747 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
11748 - Simplify hidden service descriptor creation by using an existing
11749 flag to check if an introduction point is established. Fixes bug
11750 21599; bugfix on 0.2.7.2-alpha.
11752 o Minor bugfixes (memory leak):
11753 - Fix a small memory leak at exit from the backtrace handler code.
11754 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
11756 o Minor bugfixes (protocol, logging):
11757 - Downgrade a log statement about unexpected relay cells from "bug"
11758 to "protocol warning", because there is at least one use case
11759 where it can be triggered by a buggy tor implementation. Fixes bug
11760 21293; bugfix on 0.1.1.14-alpha.
11762 o Minor bugfixes (testing):
11763 - Use unbuffered I/O for utility functions around the
11764 process_handle_t type. This fixes unit test failures reported on
11765 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
11766 - Make display of captured unit test log messages consistent. Fixes
11767 bug 21510; bugfix on 0.2.9.3-alpha.
11768 - Make test-network.sh always call chutney's test-network.sh.
11769 Previously, this only worked on systems which had bash installed,
11770 due to some bash-specific code in the script. Fixes bug 19699;
11771 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
11773 o Minor bugfixes (voting consistency):
11774 - Reject version numbers with non-numeric prefixes (such as +, -, or
11775 whitespace). Disallowing whitespace prevents differential version
11776 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11777 and part of 21508; bugfix on 0.0.8pre1.
11779 o Minor bugfixes (windows, relay):
11780 - Resolve "Failure from drain_fd: No error" warnings on Windows
11781 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
11783 o Code simplification and refactoring:
11784 - Break up the 630-line function connection_dir_client_reached_eof()
11785 into a dozen smaller functions. This change should help
11786 maintainability and readability of the client directory code.
11787 - Isolate our use of the openssl headers so that they are only
11788 included from our crypto wrapper modules, and from tests that
11789 examine those modules' internals. Closes ticket 21841.
11790 - Simplify our API to launch directory requests, making it more
11791 extensible and less error-prone. Now it's easier to add extra
11792 headers to directory requests. Closes ticket 21646.
11793 - Our base64 decoding functions no longer overestimate the output
11794 space that they need when parsing unpadded inputs. Closes
11796 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
11797 Resolves ticket 22213.
11798 - The logic that directory caches use to spool request to clients,
11799 serving them one part at a time so as not to allocate too much
11800 memory, has been refactored for consistency. Previously there was
11801 a separate spooling implementation per type of spoolable data. Now
11802 there is one common spooling implementation, with extensible data
11803 types. Closes ticket 21651.
11804 - Tor's compression module now supports multiple backends. Part of
11805 the implementation for proposal 278; closes ticket 21663.
11808 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
11809 Closes ticket 21873.
11810 - Correct documentation about the default DataDirectory value.
11811 Closes ticket 21151.
11812 - Document the default behavior of NumEntryGuards and
11813 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
11815 - Document key=value pluggable transport arguments for Bridge lines
11816 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
11817 - Note that bandwidth-limiting options don't affect TCP headers or
11818 DNS. Closes ticket 17170.
11820 o Removed features (configuration options, all in ticket 22060):
11821 - These configuration options are now marked Obsolete, and no longer
11822 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
11823 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
11824 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
11825 in 0.2.9.2-alpha and have now been removed. The previous default
11826 behavior is now always chosen; the previous (less secure) non-
11827 default behavior is now unavailable.
11828 - CloseHSClientCircuitsImmediatelyOnTimeout and
11829 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
11830 0.2.9.2-alpha and now have been removed. HS circuits never close
11831 on circuit build timeout; they have a longer timeout period.
11832 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
11833 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
11834 (and others) to configure listen-only and advertise-only addresses.
11836 o Removed features (tools):
11837 - We've removed the tor-checkkey tool from src/tools. Long ago, we
11838 used it to help people detect RSA keys that were generated by
11839 versions of Debian affected by CVE-2008-0166. But those keys have
11840 been out of circulation for ages, and this tool is no longer
11841 required. Closes ticket 21842.
11844 Changes in version 0.3.0.7 - 2017-05-15
11845 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
11846 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
11847 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
11848 clients are not affected.
11850 o Major bugfixes (hidden service directory, security):
11851 - Fix an assertion failure in the hidden service directory code, which
11852 could be used by an attacker to remotely cause a Tor relay process to
11853 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
11854 should upgrade. This security issue is tracked as TROVE-2017-002.
11855 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
11858 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11861 o Minor features (future-proofing):
11862 - Tor no longer refuses to download microdescriptors or descriptors
11863 if they are listed as "published in the future". This change will
11864 eventually allow us to stop listing meaningful "published" dates
11865 in microdescriptor consensuses, and thereby allow us to reduce the
11866 resources required to download consensus diffs by over 50%.
11867 Implements part of ticket 21642; implements part of proposal 275.
11869 o Minor bugfixes (Linux seccomp2 sandbox):
11870 - The getpid() system call is now permitted under the Linux seccomp2
11871 sandbox, to avoid crashing with versions of OpenSSL (and other
11872 libraries) that attempt to learn the process's PID by using the
11873 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11877 Changes in version 0.3.0.6 - 2017-04-26
11878 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
11880 With the 0.3.0 series, clients and relays now use Ed25519 keys to
11881 authenticate their link connections to relays, rather than the old
11882 RSA1024 keys that they used before. (Circuit crypto has been
11883 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
11884 the guard selection and replacement algorithm to behave more robustly
11885 in the presence of unreliable networks, and to resist guard-
11888 This series also includes numerous other small features and bugfixes,
11889 along with more groundwork for the upcoming hidden-services revamp.
11891 Per our stable release policy, we plan to support the Tor 0.3.0
11892 release series for at least the next nine months, or for three months
11893 after the first stable release of the 0.3.1 series: whichever is
11894 longer. If you need a release with long-term support, we recommend
11895 that you stay with the 0.2.9 series.
11897 Below are the changes since 0.3.0.5-rc. For a list of all changes
11898 since 0.2.9, see the ReleaseNotes file.
11900 o Minor features (geoip):
11901 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
11904 o Minor bugfixes (control port):
11905 - The GETINFO extra-info/digest/<digest> command was broken because
11906 of a wrong base16 decode return value check, introduced when
11907 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11909 o Minor bugfixes (crash prevention):
11910 - Fix a (currently untriggerable, but potentially dangerous) crash
11911 bug when base32-encoding inputs whose sizes are not a multiple of
11912 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
11915 Changes in version 0.3.0.5-rc - 2017-04-05
11916 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
11917 0.3.0 release series.
11919 This is the second release candidate in the Tor 0.3.0 series, and has
11920 much fewer changes than the first. If we find no new bugs or
11921 regressions here, the first stable 0.3.0 release will be nearly
11924 o Major bugfixes (crash, directory connections):
11925 - Fix a rare crash when sending a begin cell on a circuit whose
11926 linked directory connection had already been closed. Fixes bug
11927 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
11929 o Major bugfixes (guard selection):
11930 - Fix a guard selection bug where Tor would refuse to bootstrap in
11931 some cases if the user swapped a bridge for another bridge in
11932 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
11933 Reported by "torvlnt33r".
11935 o Minor features (geoip):
11936 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
11939 o Minor bugfix (compilation):
11940 - Fix a warning when compiling hs_service.c. Previously, it had no
11941 exported symbols when compiled for libor.a, resulting in a
11942 compilation warning from clang. Fixes bug 21825; bugfix
11945 o Minor bugfixes (hidden services):
11946 - Make hidden services check for failed intro point connections,
11947 even when they have exceeded their intro point creation limit.
11948 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
11949 - Make hidden services with 8 to 10 introduction points check for
11950 failed circuits immediately after startup. Previously, they would
11951 wait for 5 minutes before performing their first checks. Fixes bug
11952 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
11954 o Minor bugfixes (memory leaks):
11955 - Fix a memory leak when using GETCONF on a port option. Fixes bug
11956 21682; bugfix on 0.3.0.3-alpha.
11958 o Minor bugfixes (relay):
11959 - Avoid a double-marked-circuit warning that could happen when we
11960 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
11963 o Minor bugfixes (tests):
11964 - Run the entry_guard_parse_from_state_full() test with the time set
11965 to a specific date. (The guard state that this test was parsing
11966 contained guards that had expired since the test was first
11967 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
11970 - Update the description of the directory server options in the
11971 manual page, to clarify that a relay no longer needs to set
11972 DirPort in order to be a directory cache. Closes ticket 21720.
11976 Changes in version 0.2.8.13 - 2017-03-03
11977 Tor 0.2.8.13 backports a security fix from later Tor
11978 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
11979 this release, if for some reason they cannot upgrade to a later
11980 release series, and if they build Tor with the --enable-expensive-hardening
11983 Note that support for Tor 0.2.8.x is ending next year: we will not issue
11984 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
11985 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11987 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11988 - Fix an integer underflow bug when comparing malformed Tor
11989 versions. This bug could crash Tor when built with
11990 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11991 0.2.9.8, which were built with -ftrapv by default. In other cases
11992 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11993 on 0.0.8pre1. Found by OSS-Fuzz.
11995 o Minor features (geoip):
11996 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12000 Changes in version 0.2.7.7 - 2017-03-03
12001 Tor 0.2.7.7 backports a number of security fixes from later Tor
12002 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
12003 this release, if for some reason they cannot upgrade to a later
12006 Note that support for Tor 0.2.7.x is ending this year: we will not issue
12007 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
12008 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12010 o Directory authority changes (backport from 0.2.8.5-rc):
12011 - Urras is no longer a directory authority. Closes ticket 19271.
12013 o Directory authority changes (backport from 0.2.9.2-alpha):
12014 - The "Tonga" bridge authority has been retired; the new bridge
12015 authority is "Bifroest". Closes tickets 19728 and 19690.
12017 o Directory authority key updates (backport from 0.2.8.1-alpha):
12018 - Update the V3 identity key for the dannenberg directory authority:
12019 it was changed on 18 November 2015. Closes task 17906. Patch
12022 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12023 - Fix a bug in parsing that could cause clients to read a single
12024 byte past the end of an allocated region. This bug could be used
12025 to cause hardened clients (built with --enable-expensive-hardening)
12026 to crash if they tried to visit a hostile hidden service. Non-
12027 hardened clients are only affected depending on the details of
12028 their platform's memory allocator. Fixes bug 21018; bugfix on
12029 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12030 2016-12-002 and as CVE-2016-1254.
12032 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12033 - Stop a crash that could occur when a client running with DNSPort
12034 received a query with multiple address types, and the first
12035 address type was not supported. Found and fixed by Scott Dial.
12036 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12037 - Prevent a class of security bugs caused by treating the contents
12038 of a buffer chunk as if they were a NUL-terminated string. At
12039 least one such bug seems to be present in all currently used
12040 versions of Tor, and would allow an attacker to remotely crash
12041 most Tor instances, especially those compiled with extra compiler
12042 hardening. With this defense in place, such bugs can't crash Tor,
12043 though we should still fix them as they occur. Closes ticket
12044 20384 (TROVE-2016-10-001).
12046 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12047 - Avoid a difficult-to-trigger heap corruption attack when extending
12048 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12049 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12050 Reported by Guido Vranken.
12052 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12053 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12054 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12056 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12057 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12058 pointer to the previous (uninitialized) key value. The impact here
12059 should be limited to a difficult-to-trigger crash, if OpenSSL is
12060 running an engine that makes key generation failures possible, or
12061 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12062 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12065 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12066 - Fix an integer underflow bug when comparing malformed Tor
12067 versions. This bug could crash Tor when built with
12068 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12069 0.2.9.8, which were built with -ftrapv by default. In other cases
12070 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12071 on 0.0.8pre1. Found by OSS-Fuzz.
12073 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12074 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12075 zero size. Check size argument to memwipe() for underflow. Fixes
12076 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12079 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12080 - Make Tor survive errors involving connections without a
12081 corresponding event object. Previously we'd fail with an
12082 assertion; now we produce a log message. Related to bug 16248.
12084 o Minor features (geoip):
12085 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12089 Changes in version 0.2.6.11 - 2017-03-03
12090 Tor 0.2.6.11 backports a number of security fixes from later Tor
12091 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
12092 this release, if for some reason they cannot upgrade to a later
12095 Note that support for Tor 0.2.6.x is ending this year: we will not issue
12096 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
12097 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12099 o Directory authority changes (backport from 0.2.8.5-rc):
12100 - Urras is no longer a directory authority. Closes ticket 19271.
12102 o Directory authority changes (backport from 0.2.9.2-alpha):
12103 - The "Tonga" bridge authority has been retired; the new bridge
12104 authority is "Bifroest". Closes tickets 19728 and 19690.
12106 o Directory authority key updates (backport from 0.2.8.1-alpha):
12107 - Update the V3 identity key for the dannenberg directory authority:
12108 it was changed on 18 November 2015. Closes task 17906. Patch
12111 o Major features (security fixes, backport from 0.2.9.4-alpha):
12112 - Prevent a class of security bugs caused by treating the contents
12113 of a buffer chunk as if they were a NUL-terminated string. At
12114 least one such bug seems to be present in all currently used
12115 versions of Tor, and would allow an attacker to remotely crash
12116 most Tor instances, especially those compiled with extra compiler
12117 hardening. With this defense in place, such bugs can't crash Tor,
12118 though we should still fix them as they occur. Closes ticket
12119 20384 (TROVE-2016-10-001).
12121 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12122 - Fix a bug in parsing that could cause clients to read a single
12123 byte past the end of an allocated region. This bug could be used
12124 to cause hardened clients (built with --enable-expensive-hardening)
12125 to crash if they tried to visit a hostile hidden service. Non-
12126 hardened clients are only affected depending on the details of
12127 their platform's memory allocator. Fixes bug 21018; bugfix on
12128 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12129 2016-12-002 and as CVE-2016-1254.
12131 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12132 - Stop a crash that could occur when a client running with DNSPort
12133 received a query with multiple address types, and the first
12134 address type was not supported. Found and fixed by Scott Dial.
12135 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12137 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12138 - Fix an error that could cause us to read 4 bytes before the
12139 beginning of an openssl string. This bug could be used to cause
12140 Tor to crash on systems with unusual malloc implementations, or
12141 systems with unusual hardening installed. Fixes bug 17404; bugfix
12144 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12145 - Avoid a difficult-to-trigger heap corruption attack when extending
12146 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12147 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12148 Reported by Guido Vranken.
12150 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12151 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12152 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12154 o Major bugfixes (guard selection, backport from 0.2.7.6):
12155 - Actually look at the Guard flag when selecting a new directory
12156 guard. When we implemented the directory guard design, we
12157 accidentally started treating all relays as if they have the Guard
12158 flag during guard selection, leading to weaker anonymity and worse
12159 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12162 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12163 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12164 pointer to the previous (uninitialized) key value. The impact here
12165 should be limited to a difficult-to-trigger crash, if OpenSSL is
12166 running an engine that makes key generation failures possible, or
12167 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12168 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12171 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12172 - Fix an integer underflow bug when comparing malformed Tor
12173 versions. This bug could crash Tor when built with
12174 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12175 0.2.9.8, which were built with -ftrapv by default. In other cases
12176 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12177 on 0.0.8pre1. Found by OSS-Fuzz.
12179 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12180 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12181 zero size. Check size argument to memwipe() for underflow. Fixes
12182 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12185 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12186 - Make Tor survive errors involving connections without a
12187 corresponding event object. Previously we'd fail with an
12188 assertion; now we produce a log message. Related to bug 16248.
12190 o Minor features (geoip):
12191 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12194 o Minor bugfixes (compilation, backport from 0.2.7.6):
12195 - Fix a compilation warning with Clang 3.6: Do not check the
12196 presence of an address which can never be NULL. Fixes bug 17781.
12199 Changes in version 0.2.5.13 - 2017-03-03
12200 Tor 0.2.5.13 backports a number of security fixes from later Tor
12201 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
12202 this release, if for some reason they cannot upgrade to a later
12205 Note that support for Tor 0.2.5.x is ending next year: we will not issue
12206 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
12207 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12209 o Directory authority changes (backport from 0.2.8.5-rc):
12210 - Urras is no longer a directory authority. Closes ticket 19271.
12212 o Directory authority changes (backport from 0.2.9.2-alpha):
12213 - The "Tonga" bridge authority has been retired; the new bridge
12214 authority is "Bifroest". Closes tickets 19728 and 19690.
12216 o Directory authority key updates (backport from 0.2.8.1-alpha):
12217 - Update the V3 identity key for the dannenberg directory authority:
12218 it was changed on 18 November 2015. Closes task 17906. Patch
12221 o Major features (security fixes, backport from 0.2.9.4-alpha):
12222 - Prevent a class of security bugs caused by treating the contents
12223 of a buffer chunk as if they were a NUL-terminated string. At
12224 least one such bug seems to be present in all currently used
12225 versions of Tor, and would allow an attacker to remotely crash
12226 most Tor instances, especially those compiled with extra compiler
12227 hardening. With this defense in place, such bugs can't crash Tor,
12228 though we should still fix them as they occur. Closes ticket
12229 20384 (TROVE-2016-10-001).
12231 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12232 - Fix a bug in parsing that could cause clients to read a single
12233 byte past the end of an allocated region. This bug could be used
12234 to cause hardened clients (built with --enable-expensive-hardening)
12235 to crash if they tried to visit a hostile hidden service. Non-
12236 hardened clients are only affected depending on the details of
12237 their platform's memory allocator. Fixes bug 21018; bugfix on
12238 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12239 2016-12-002 and as CVE-2016-1254.
12241 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12242 - Stop a crash that could occur when a client running with DNSPort
12243 received a query with multiple address types, and the first
12244 address type was not supported. Found and fixed by Scott Dial.
12245 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12247 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12248 - Fix an error that could cause us to read 4 bytes before the
12249 beginning of an openssl string. This bug could be used to cause
12250 Tor to crash on systems with unusual malloc implementations, or
12251 systems with unusual hardening installed. Fixes bug 17404; bugfix
12254 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12255 - Avoid a difficult-to-trigger heap corruption attack when extending
12256 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12257 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12258 Reported by Guido Vranken.
12260 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12261 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12262 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12264 o Major bugfixes (guard selection, backport from 0.2.7.6):
12265 - Actually look at the Guard flag when selecting a new directory
12266 guard. When we implemented the directory guard design, we
12267 accidentally started treating all relays as if they have the Guard
12268 flag during guard selection, leading to weaker anonymity and worse
12269 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12272 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12273 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12274 pointer to the previous (uninitialized) key value. The impact here
12275 should be limited to a difficult-to-trigger crash, if OpenSSL is
12276 running an engine that makes key generation failures possible, or
12277 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12278 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12281 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12282 - Fix an integer underflow bug when comparing malformed Tor
12283 versions. This bug could crash Tor when built with
12284 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12285 0.2.9.8, which were built with -ftrapv by default. In other cases
12286 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12287 on 0.0.8pre1. Found by OSS-Fuzz.
12289 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12290 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12291 zero size. Check size argument to memwipe() for underflow. Fixes
12292 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12295 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12296 - Make Tor survive errors involving connections without a
12297 corresponding event object. Previously we'd fail with an
12298 assertion; now we produce a log message. Related to bug 16248.
12300 o Minor features (geoip):
12301 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12304 o Minor bugfixes (compilation, backport from 0.2.7.6):
12305 - Fix a compilation warning with Clang 3.6: Do not check the
12306 presence of an address which can never be NULL. Fixes bug 17781.
12308 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
12309 - Check for failures from crypto_early_init, and refuse to continue.
12310 A previous typo meant that we could keep going with an
12311 uninitialized crypto library, and would have OpenSSL initialize
12312 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12313 when implementing ticket 4900. Patch by "teor".
12315 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12316 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12317 a client authorized hidden service. Fixes bug 15823; bugfix
12321 Changes in version 0.2.4.28 - 2017-03-03
12322 Tor 0.2.4.28 backports a number of security fixes from later Tor
12323 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
12324 this release, if for some reason they cannot upgrade to a later
12327 Note that support for Tor 0.2.4.x is ending soon: we will not issue
12328 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
12329 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
12331 o Directory authority changes (backport from 0.2.8.5-rc):
12332 - Urras is no longer a directory authority. Closes ticket 19271.
12334 o Directory authority changes (backport from 0.2.9.2-alpha):
12335 - The "Tonga" bridge authority has been retired; the new bridge
12336 authority is "Bifroest". Closes tickets 19728 and 19690.
12338 o Directory authority key updates (backport from 0.2.8.1-alpha):
12339 - Update the V3 identity key for the dannenberg directory authority:
12340 it was changed on 18 November 2015. Closes task 17906. Patch
12343 o Major features (security fixes, backport from 0.2.9.4-alpha):
12344 - Prevent a class of security bugs caused by treating the contents
12345 of a buffer chunk as if they were a NUL-terminated string. At
12346 least one such bug seems to be present in all currently used
12347 versions of Tor, and would allow an attacker to remotely crash
12348 most Tor instances, especially those compiled with extra compiler
12349 hardening. With this defense in place, such bugs can't crash Tor,
12350 though we should still fix them as they occur. Closes ticket
12351 20384 (TROVE-2016-10-001).
12353 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12354 - Fix a bug in parsing that could cause clients to read a single
12355 byte past the end of an allocated region. This bug could be used
12356 to cause hardened clients (built with --enable-expensive-hardening)
12357 to crash if they tried to visit a hostile hidden service. Non-
12358 hardened clients are only affected depending on the details of
12359 their platform's memory allocator. Fixes bug 21018; bugfix on
12360 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12361 2016-12-002 and as CVE-2016-1254.
12363 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12364 - Fix an error that could cause us to read 4 bytes before the
12365 beginning of an openssl string. This bug could be used to cause
12366 Tor to crash on systems with unusual malloc implementations, or
12367 systems with unusual hardening installed. Fixes bug 17404; bugfix
12370 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12371 - Avoid a difficult-to-trigger heap corruption attack when extending
12372 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12373 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12374 Reported by Guido Vranken.
12376 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12377 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12378 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12380 o Major bugfixes (guard selection, backport from 0.2.7.6):
12381 - Actually look at the Guard flag when selecting a new directory
12382 guard. When we implemented the directory guard design, we
12383 accidentally started treating all relays as if they have the Guard
12384 flag during guard selection, leading to weaker anonymity and worse
12385 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12388 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12389 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12390 pointer to the previous (uninitialized) key value. The impact here
12391 should be limited to a difficult-to-trigger crash, if OpenSSL is
12392 running an engine that makes key generation failures possible, or
12393 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12394 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12397 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12398 - Fix an integer underflow bug when comparing malformed Tor
12399 versions. This bug could crash Tor when built with
12400 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12401 0.2.9.8, which were built with -ftrapv by default. In other cases
12402 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12403 on 0.0.8pre1. Found by OSS-Fuzz.
12405 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12406 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12407 zero size. Check size argument to memwipe() for underflow. Fixes
12408 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12411 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12412 - Make Tor survive errors involving connections without a
12413 corresponding event object. Previously we'd fail with an
12414 assertion; now we produce a log message. Related to bug 16248.
12416 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
12417 - Make it harder for attackers to overload hidden services with
12418 introductions, by blocking multiple introduction requests on the
12419 same circuit. Resolves ticket 15515.
12421 o Minor features (geoip):
12422 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12425 o Minor bugfixes (compilation, backport from 0.2.7.6):
12426 - Fix a compilation warning with Clang 3.6: Do not check the
12427 presence of an address which can never be NULL. Fixes bug 17781.
12429 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12430 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12431 a client authorized hidden service. Fixes bug 15823; bugfix
12435 Changes in version 0.3.0.4-rc - 2017-03-01
12436 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
12437 0.3.0 release series, and introduces a few reliability features to
12438 keep them from coming back.
12440 This is the first release candidate in the Tor 0.3.0 series. If we
12441 find no new bugs or regressions here, the first stable 0.3.0 release
12442 will be nearly identical to it.
12444 o Major bugfixes (bridges):
12445 - When the same bridge is configured multiple times with the same
12446 identity, but at different address:port combinations, treat those
12447 bridge instances as separate guards. This fix restores the ability
12448 of clients to configure the same bridge with multiple pluggable
12449 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
12451 o Major bugfixes (hidden service directory v3):
12452 - Stop crashing on a failed v3 hidden service descriptor lookup
12453 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
12455 o Major bugfixes (parsing):
12456 - When parsing a malformed content-length field from an HTTP
12457 message, do not read off the end of the buffer. This bug was a
12458 potential remote denial-of-service attack against Tor clients and
12459 relays. A workaround was released in October 2016, to prevent this
12460 bug from crashing Tor. This is a fix for the underlying issue,
12461 which should no longer matter (if you applied the earlier patch).
12462 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
12463 using AFL (http://lcamtuf.coredump.cx/afl/).
12464 - Fix an integer underflow bug when comparing malformed Tor
12465 versions. This bug could crash Tor when built with
12466 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12467 0.2.9.8, which were built with -ftrapv by default. In other cases
12468 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12469 on 0.0.8pre1. Found by OSS-Fuzz.
12471 o Minor feature (protocol versioning):
12472 - Add new protocol version for proposal 224. HSIntro now advertises
12473 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
12475 o Minor features (directory authorities):
12476 - Directory authorities now reject descriptors that claim to be
12477 malformed versions of Tor. Helps prevent exploitation of
12479 - Reject version numbers with components that exceed INT32_MAX.
12480 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12481 Fixes bug 21450; bugfix on 0.0.8pre1.
12482 - Directory authorities now reject relays running versions
12483 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
12484 suffer from bug 20499 and don't keep their consensus cache
12485 up-to-date. Resolves ticket 20509.
12487 o Minor features (geoip):
12488 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12491 o Minor features (reliability, crash):
12492 - Try better to detect problems in buffers where they might grow (or
12493 think they have grown) over 2 GB in size. Diagnostic for
12496 o Minor features (testing):
12497 - During 'make test-network-all', if tor logs any warnings, ask
12498 chutney to output them. Requires a recent version of chutney with
12499 the 21572 patch. Implements 21570.
12501 o Minor bugfixes (certificate expiration time):
12502 - Avoid using link certificates that don't become valid till some
12503 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
12505 o Minor bugfixes (code correctness):
12506 - Repair a couple of (unreachable or harmless) cases of the risky
12507 comparison-by-subtraction pattern that caused bug 21278.
12508 - Remove a redundant check for the UseEntryGuards option from the
12509 options_transition_affects_guards() function. Fixes bug 21492;
12510 bugfix on 0.3.0.1-alpha.
12512 o Minor bugfixes (directory mirrors):
12513 - Allow relays to use directory mirrors without a DirPort: these
12514 relays need to be contacted over their ORPorts using a begindir
12515 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
12516 - Clarify the message logged when a remote relay is unexpectedly
12517 missing an ORPort or DirPort: users were confusing this with a
12518 local port. Fixes another case of bug 20711; bugfix
12521 o Minor bugfixes (guards):
12522 - Don't warn about a missing guard state on timeout-measurement
12523 circuits: they aren't supposed to be using guards. Fixes an
12524 instance of bug 21007; bugfix on 0.3.0.1-alpha.
12525 - Silence a BUG() warning when attempting to use a guard whose
12526 descriptor we don't know, and make this scenario less likely to
12527 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
12529 o Minor bugfixes (hidden service):
12530 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
12531 cells. Previously, we were using sizeof() on a pointer, instead of
12532 the real destination buffer. Fortunately, that value was only used
12533 to double-check that there was enough room--which was already
12534 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
12536 o Minor bugfixes (testing):
12537 - Fix Raspbian build issues related to missing socket errno in
12538 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
12540 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
12541 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
12542 - Use bash in src/test/test-network.sh. This ensures we reliably
12543 call chutney's newer tools/test-network.sh when available. Fixes
12544 bug 21562; bugfix on 0.2.9.1-alpha.
12547 - Small fixes to the fuzzing documentation. Closes ticket 21472.
12550 Changes in version 0.2.9.10 - 2017-03-01
12551 Tor 0.2.9.10 backports a security fix from later Tor release. It also
12552 includes fixes for some major issues affecting directory authorities,
12553 LibreSSL compatibility, and IPv6 correctness.
12555 The Tor 0.2.9.x release series is now marked as a long-term-support
12556 series. We intend to backport security fixes to 0.2.9.x until at
12557 least January of 2020.
12559 o Major bugfixes (directory authority, 0.3.0.3-alpha):
12560 - During voting, when marking a relay as a probable sybil, do not
12561 clear its BadExit flag: sybils can still be bad in other ways
12562 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12565 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
12566 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12567 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12568 exit policy rejects that port on more than an IPv6 /16 of
12569 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12570 which rejected a relay's own IPv6 address by default. Fixes bug
12571 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12573 o Major bugfixes (parsing, also in 0.3.0.4-rc):
12574 - Fix an integer underflow bug when comparing malformed Tor
12575 versions. This bug could crash Tor when built with
12576 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12577 0.2.9.8, which were built with -ftrapv by default. In other cases
12578 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12579 on 0.0.8pre1. Found by OSS-Fuzz.
12581 o Minor features (directory authorities, also in 0.3.0.4-rc):
12582 - Directory authorities now reject descriptors that claim to be
12583 malformed versions of Tor. Helps prevent exploitation of
12585 - Reject version numbers with components that exceed INT32_MAX.
12586 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12587 Fixes bug 21450; bugfix on 0.0.8pre1.
12589 o Minor features (geoip):
12590 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12593 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
12594 - Autoconf now checks to determine if OpenSSL structures are opaque,
12595 instead of explicitly checking for OpenSSL version numbers. Part
12597 - Support building with recent LibreSSL code that uses opaque
12598 structures. Closes ticket 21359.
12600 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
12601 - Repair a couple of (unreachable or harmless) cases of the risky
12602 comparison-by-subtraction pattern that caused bug 21278.
12604 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
12605 - The tor-resolve command line tool now rejects hostnames over 255
12606 characters in length. Previously, it would silently truncate them,
12607 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12608 Patch by "junglefowl".
12611 Changes in version 0.3.0.3-alpha - 2017-02-03
12612 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
12613 0.3.0.x development series, including some that could cause
12614 authorities to behave badly. There is also a fix for a longstanding
12615 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
12616 includes some smaller features and bugfixes.
12618 The Tor 0.3.0.x release series is now in patch-freeze: no additional
12619 features will be considered for inclusion in 0.3.0.x. We suspect that
12620 some bugs will probably remain, however, and we encourage people to
12623 o Major bugfixes (directory authority):
12624 - During voting, when marking a relay as a probable sybil, do not
12625 clear its BadExit flag: sybils can still be bad in other ways
12626 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12628 - When deciding whether we have just found a router to be reachable,
12629 do not penalize it for not having performed an Ed25519 link
12630 handshake if it does not claim to support an Ed25519 handshake.
12631 Previously, we would treat such relays as non-running. Fixes bug
12632 21107; bugfix on 0.3.0.1-alpha.
12634 o Major bugfixes (entry guards):
12635 - Stop trying to build circuits through entry guards for which we
12636 have no descriptor. Also, stop crashing in the case that we *do*
12637 accidentally try to build a circuit in such a state. Fixes bug
12638 21242; bugfix on 0.3.0.1-alpha.
12640 o Major bugfixes (IPv6 Exits):
12641 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12642 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12643 exit policy rejects that port on more than an IPv6 /16 of
12644 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12645 which rejected a relay's own IPv6 address by default. Fixes bug
12646 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12648 o Minor feature (client):
12649 - Enable IPv6 traffic on the SocksPort by default. To disable this,
12650 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
12652 o Minor feature (fallback scripts):
12653 - Add a check_existing mode to updateFallbackDirs.py, which checks
12654 if fallbacks in the hard-coded list are working. Closes ticket
12655 20174. Patch by haxxpop.
12657 o Minor features (ciphersuite selection):
12658 - Clients now advertise a list of ciphersuites closer to the ones
12659 preferred by Firefox. Closes part of ticket 15426.
12660 - Allow relays to accept a wider range of ciphersuites, including
12661 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
12663 o Minor features (controller, configuration):
12664 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
12665 and so on, now comes with a __*Port variant that will not be saved
12666 to the torrc file by the controller's SAVECONF command. This
12667 change allows TorBrowser to set up a single-use domain socket for
12668 each time it launches Tor. Closes ticket 20956.
12669 - The GETCONF command can now query options that may only be
12670 meaningful in context-sensitive lists. This allows the controller
12671 to query the mixed SocksPort/__SocksPort style options introduced
12672 in feature 20956. Implements ticket 21300.
12674 o Minor features (portability, compilation):
12675 - Autoconf now checks to determine if OpenSSL structures are opaque,
12676 instead of explicitly checking for OpenSSL version numbers. Part
12678 - Support building with recent LibreSSL code that uses opaque
12679 structures. Closes ticket 21359.
12681 o Minor features (relay):
12682 - We now allow separation of exit and relay traffic to different
12683 source IP addresses, using the OutboundBindAddressExit and
12684 OutboundBindAddressOR options respectively. Closes ticket 17975.
12685 Written by Michael Sonntag.
12687 o Minor bugfix (logging):
12688 - Don't recommend the use of Tor2web in non-anonymous mode.
12689 Recommending Tor2web is a bad idea because the client loses all
12690 anonymity. Tor2web should only be used in specific cases by users
12691 who *know* and understand the issues. Fixes bug 21294; bugfix
12694 o Minor bugfixes (client):
12695 - Always recover from failures in extend_info_from_node(), in an
12696 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
12697 bugfix on 0.2.3.1-alpha.
12699 o Minor bugfixes (client, entry guards):
12700 - Fix a bug warning (with backtrace) when we fail a channel that
12701 circuits to fallback directories on it. Fixes bug 21128; bugfix
12703 - Fix a spurious bug warning (with backtrace) when removing an
12704 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
12705 - Fix a bug of the new guard algorithm where tor could stall for up
12706 to 10 minutes before retrying a guard after a long period of no
12707 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
12708 - Do not try to build circuits until we have descriptors for our
12709 primary entry guards. Related to fix for bug 21242.
12711 o Minor bugfixes (configure, autoconf):
12712 - Rename the configure option --enable-expensive-hardening to
12713 --enable-fragile-hardening. Expensive hardening makes the tor
12714 daemon abort when some kinds of issues are detected. Thus, it
12715 makes tor more at risk of remote crashes but safer against RCE or
12716 heartbleed bug category. We now try to explain this issue in a
12717 message from the configure script. Fixes bug 21290; bugfix
12720 o Minor bugfixes (controller):
12721 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
12722 20824; bugfix on 0.3.0.1-alpha.
12724 o Minor bugfixes (hidden service):
12725 - Clean up the code for expiring intro points with no associated
12726 circuits. It was causing, rarely, a service with some expiring
12727 introduction points to not open enough additional introduction
12728 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
12729 - Stop setting the torrc option HiddenServiceStatistics to "0" just
12730 because we're not a bridge or relay. Instead, we preserve whatever
12731 value the user set (or didn't set). Fixes bug 21150; bugfix
12733 - Resolve two possible underflows which could lead to creating and
12734 closing a lot of introduction point circuits in a non-stop loop.
12735 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
12737 o Minor bugfixes (portability):
12738 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
12739 It is supported by OpenBSD itself, and also by most OpenBSD
12740 variants (such as Bitrig). Fixes bug 20980; bugfix
12742 - When mapping a file of length greater than SIZE_MAX, do not
12743 silently truncate its contents. This issue could occur on 32 bit
12744 systems with large file support and files which are larger than 4
12745 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
12747 o Minor bugfixes (tor-resolve):
12748 - The tor-resolve command line tool now rejects hostnames over 255
12749 characters in length. Previously, it would silently truncate them,
12750 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12751 Patch by "junglefowl".
12753 o Minor bugfixes (Windows services):
12754 - Be sure to initialize the monotonic time subsystem before using
12755 it, even when running as an NT service. Fixes bug 21356; bugfix
12759 Changes in version 0.3.0.2-alpha - 2017-01-23
12760 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
12761 cause relays and clients to crash, even if they were not built with
12762 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
12763 versions, and also affects 0.3.0.1-alpha: all relays running an affected
12764 version should upgrade.
12766 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
12767 time-to-live values, makes directory authorities enforce the 1-to-1
12768 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
12769 client-side onion service reachability bug, does better at selecting
12770 the set of fallback directories, and more.
12772 o Major bugfixes (security, also in 0.2.9.9):
12773 - Downgrade the "-ftrapv" option from "always on" to "only on when
12774 --enable-expensive-hardening is provided." This hardening option, like
12775 others, can turn survivable bugs into crashes--and having it on by
12776 default made a (relatively harmless) integer overflow bug into a
12777 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
12780 o Major features (security):
12781 - Change the algorithm used to decide DNS TTLs on client and server
12782 side, to better resist DNS-based correlation attacks like the
12783 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
12784 Feamster. Now relays only return one of two possible DNS TTL
12785 values, and clients are willing to believe DNS TTL values up to 3
12786 hours long. Closes ticket 19769.
12788 o Major features (directory authority, security):
12789 - The default for AuthDirPinKeys is now 1: directory authorities
12790 will reject relays where the RSA identity key matches a previously
12791 seen value, but the Ed25519 key has changed. Closes ticket 18319.
12793 o Major bugfixes (client, guard, crash):
12794 - In circuit_get_global_origin_list(), return the actual list of
12795 origin circuits. The previous version of this code returned the
12796 list of all the circuits, and could have caused strange bugs,
12797 including possible crashes. Fixes bug 21118; bugfix
12800 o Major bugfixes (client, onion service, also in 0.2.9.9):
12801 - Fix a client-side onion service reachability bug, where multiple
12802 socks requests to an onion service (or a single slow request)
12803 could cause us to mistakenly mark some of the service's
12804 introduction points as failed, and we cache that failure so
12805 eventually we run out and can't reach the service. Also resolves a
12806 mysterious "Remote server sent bogus reason code 65021" log
12807 warning. The bug was introduced in ticket 17218, where we tried to
12808 remember the circuit end reason as a uint16_t, which mangled
12809 negative values. Partially fixes bug 21056 and fixes bug 20307;
12810 bugfix on 0.2.8.1-alpha.
12812 o Major bugfixes (DNS):
12813 - Fix a bug that prevented exit nodes from caching DNS records for
12814 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
12816 o Minor features (controller):
12817 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
12818 shared-random values to the controller. Closes ticket 19925.
12820 o Minor features (entry guards):
12821 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
12822 break regression tests.
12823 - Require UseEntryGuards when UseBridges is set, in order to make
12824 sure bridges aren't bypassed. Resolves ticket 20502.
12826 o Minor features (fallback directories):
12827 - Select 200 fallback directories for each release. Closes
12829 - Allow 3 fallback relays per operator, which is safe now that we
12830 are choosing 200 fallback relays. Closes ticket 20912.
12831 - Exclude relays affected by bug 20499 from the fallback list.
12832 Exclude relays from the fallback list if they are running versions
12833 known to be affected by bug 20499, or if in our tests they deliver
12834 a stale consensus (i.e. one that expired more than 24 hours ago).
12835 Closes ticket 20539.
12836 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
12838 - Require fallback directories to have the same address and port for
12839 7 days (now that we have enough relays with this stability).
12840 Relays whose OnionOO stability timer is reset on restart by bug
12841 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
12842 this issue. Closes ticket 20880; maintains short-term fix
12844 - Require fallbacks to have flags for 90% of the time (weighted
12845 decaying average), rather than 95%. This allows at least 73% of
12846 clients to bootstrap in the first 5 seconds without contacting an
12847 authority. Part of ticket 18828.
12848 - Annotate updateFallbackDirs.py with the bandwidth and consensus
12849 weight for each candidate fallback. Closes ticket 20878.
12850 - Make it easier to change the output sort order of fallbacks.
12851 Closes ticket 20822.
12852 - Display the relay fingerprint when downloading consensuses from
12853 fallbacks. Closes ticket 20908.
12855 o Minor features (geoip, also in 0.2.9.9):
12856 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
12859 o Minor features (next-gen onion service directories):
12860 - Remove the "EnableOnionServicesV3" consensus parameter that we
12861 introduced in 0.3.0.1-alpha: relays are now always willing to act
12862 as v3 onion service directories. Resolves ticket 19899.
12864 o Minor features (linting):
12865 - Enhance the changes file linter to warn on Tor versions that are
12866 prefixed with "tor-". Closes ticket 21096.
12868 o Minor features (logging):
12869 - In several places, describe unset ed25519 keys as "<unset>",
12870 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
12872 o Minor bugfix (control protocol):
12873 - The reply to a "GETINFO config/names" request via the control
12874 protocol now spells the type "Dependent" correctly. This is a
12875 breaking change in the control protocol. (The field seems to be
12876 ignored by the most common known controllers.) Fixes bug 18146;
12877 bugfix on 0.1.1.4-alpha.
12879 o Minor bugfixes (bug resilience):
12880 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
12881 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
12882 Hans Jerry Illikainen.
12884 o Minor bugfixes (build):
12885 - Replace obsolete Autoconf macros with their modern equivalent and
12886 prevent similar issues in the future. Fixes bug 20990; bugfix
12889 o Minor bugfixes (client, guards):
12890 - Fix bug where Tor would think that there are circuits waiting for
12891 better guards even though those circuits have been freed. Fixes
12892 bug 21142; bugfix on 0.3.0.1-alpha.
12894 o Minor bugfixes (config):
12895 - Don't assert on startup when trying to get the options list and
12896 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
12897 options so of course they aren't ready yet. Fixes bug 21062;
12898 bugfix on 0.2.9.3-alpha.
12900 o Minor bugfixes (controller):
12901 - Make the GETINFO interface for inquiring about entry guards
12902 support the new guards backend. Fixes bug 20823; bugfix
12905 o Minor bugfixes (dead code):
12906 - Remove a redundant check for PidFile changes at runtime in
12907 options_transition_allowed(): this check is already performed
12908 regardless of whether the sandbox is active. Fixes bug 21123;
12909 bugfix on 0.2.5.4-alpha.
12911 o Minor bugfixes (documentation):
12912 - Update the tor manual page to document every option that can not
12913 be changed while tor is running. Fixes bug 21122.
12915 o Minor bugfixes (fallback directories):
12916 - Stop failing when a relay has no uptime data in
12917 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
12918 - Avoid checking fallback candidates' DirPorts if they are down in
12919 OnionOO. When a relay operator has multiple relays, this
12920 prioritizes relays that are up over relays that are down. Fixes
12921 bug 20926; bugfix on 0.2.8.3-alpha.
12922 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
12923 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
12925 o Minor bugfixes (guards, bootstrapping):
12926 - When connecting to a directory guard during bootstrap, do not mark
12927 the guard as successful until we receive a good-looking directory
12928 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
12930 o Minor bugfixes (onion services):
12931 - Fix the config reload pruning of old vs new services so it
12932 actually works when both ephemeral and non-ephemeral services are
12933 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
12934 - Allow the number of introduction points to be as low as 0, rather
12935 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
12937 o Minor bugfixes (IPv6):
12938 - Make IPv6-using clients try harder to find an IPv6 directory
12939 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
12940 - When IPv6 addresses have not been downloaded yet (microdesc
12941 consensus documents don't list relay IPv6 addresses), use hard-
12942 coded addresses for authorities, fallbacks, and configured
12943 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
12944 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
12946 o Minor bugfixes (memory leaks):
12947 - Fix a memory leak when configuring hidden services. Fixes bug
12948 20987; bugfix on 0.3.0.1-alpha.
12950 o Minor bugfixes (portability, also in 0.2.9.9):
12951 - Avoid crashing when Tor is built using headers that contain
12952 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
12953 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
12955 - Fix Libevent detection on platforms without Libevent 1 headers
12956 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
12958 o Minor bugfixes (relay):
12959 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
12960 initializing the keys would reset the DataDirectory to 0700
12961 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
12962 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
12964 o Minor bugfixes (testing):
12965 - Remove undefined behavior from the backtrace generator by removing
12966 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
12968 o Minor bugfixes (unit tests):
12969 - Allow the unit tests to pass even when DNS lookups of bogus
12970 addresses do not fail as expected. Fixes bug 20862 and 20863;
12971 bugfix on unit tests introduced in 0.2.8.1-alpha
12972 through 0.2.9.4-alpha.
12974 o Code simplification and refactoring:
12975 - Refactor code to manipulate global_origin_circuit_list into
12976 separate functions. Closes ticket 20921.
12978 o Documentation (formatting):
12979 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
12980 blocks were incorrectly appearing. Closes ticket 20885.
12982 o Documentation (man page):
12983 - Clarify many options in tor.1 and add some min/max values for
12984 HiddenService options. Closes ticket 21058.
12987 Changes in version 0.2.9.9 - 2017-01-23
12988 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
12989 cause relays and clients to crash, even if they were not built with
12990 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
12991 versions, and also affects 0.3.0.1-alpha: all relays running an affected
12992 version should upgrade.
12994 This release also resolves a client-side onion service reachability
12995 bug, and resolves a pair of small portability issues.
12997 o Major bugfixes (security):
12998 - Downgrade the "-ftrapv" option from "always on" to "only on when
12999 --enable-expensive-hardening is provided." This hardening option,
13000 like others, can turn survivable bugs into crashes -- and having
13001 it on by default made a (relatively harmless) integer overflow bug
13002 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13003 bugfix on 0.2.9.1-alpha.
13005 o Major bugfixes (client, onion service):
13006 - Fix a client-side onion service reachability bug, where multiple
13007 socks requests to an onion service (or a single slow request)
13008 could cause us to mistakenly mark some of the service's
13009 introduction points as failed, and we cache that failure so
13010 eventually we run out and can't reach the service. Also resolves a
13011 mysterious "Remote server sent bogus reason code 65021" log
13012 warning. The bug was introduced in ticket 17218, where we tried to
13013 remember the circuit end reason as a uint16_t, which mangled
13014 negative values. Partially fixes bug 21056 and fixes bug 20307;
13015 bugfix on 0.2.8.1-alpha.
13017 o Minor features (geoip):
13018 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13021 o Minor bugfixes (portability):
13022 - Avoid crashing when Tor is built using headers that contain
13023 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13024 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13026 - Fix Libevent detection on platforms without Libevent 1 headers
13027 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13030 Changes in version 0.3.0.1-alpha - 2016-12-19
13031 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
13032 series. It strengthens Tor's link and circuit handshakes by
13033 identifying relays by their Ed25519 keys, improves the algorithm that
13034 clients use to choose and maintain their list of guards, and includes
13035 additional backend support for the next-generation hidden service
13036 design. It also contains numerous other small features and
13037 improvements to security, correctness, and performance.
13039 Below are the changes since 0.2.9.8.
13041 o Major features (guard selection algorithm):
13042 - Tor's guard selection algorithm has been redesigned from the
13043 ground up, to better support unreliable networks and restrictive
13044 sets of entry nodes, and to better resist guard-capture attacks by
13045 hostile local networks. Implements proposal 271; closes
13048 o Major features (next-generation hidden services):
13049 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
13050 prop224 aka "Next Generation Hidden Services". Service and clients
13051 don't use this functionality yet. Closes ticket 19043. Based on
13052 initial code by Alec Heifetz.
13053 - Relays now support the HSDir version 3 protocol, so that they can
13054 can store and serve v3 descriptors. This is part of the next-
13055 generation onion service work detailed in proposal 224. Closes
13058 o Major features (protocol, ed25519 identity keys):
13059 - Relays now use Ed25519 to prove their Ed25519 identities and to
13060 one another, and to clients. This algorithm is faster and more
13061 secure than the RSA-based handshake we've been doing until now.
13062 Implements the second big part of proposal 220; Closes
13064 - Clients now support including Ed25519 identity keys in the EXTEND2
13065 cells they generate. By default, this is controlled by a consensus
13066 parameter, currently disabled. You can turn this feature on for
13067 testing by setting ExtendByEd25519ID in your configuration. This
13068 might make your traffic appear different than the traffic
13069 generated by other users, however. Implements part of ticket
13070 15056; part of proposal 220.
13071 - Relays now understand requests to extend to other relays by their
13072 Ed25519 identity keys. When an Ed25519 identity key is included in
13073 an EXTEND2 cell, the relay will only extend the circuit if the
13074 other relay can prove ownership of that identity. Implements part
13075 of ticket 15056; part of proposal 220.
13077 o Major bugfixes (scheduler):
13078 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
13079 caused the channel scheduler to behave more or less randomly,
13080 rather than preferring channels with higher-priority circuits.
13081 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
13083 o Minor features (controller):
13084 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
13085 rather than "unrecognized." Closes ticket 20389; patch from
13088 o Minor features (diagnostic, directory client):
13089 - Warn when we find an unexpected inconsistency in directory
13090 download status objects. Prevents some negative consequences of
13093 o Minor features (directory authority):
13094 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
13095 default) to control whether authorities should try to probe relays
13096 by their Ed25519 link keys. This option will go away in a few
13097 releases--unless we encounter major trouble in our ed25519 link
13098 protocol rollout, in which case it will serve as a safety option.
13100 o Minor features (directory cache):
13101 - Relays and bridges will now refuse to serve the consensus they
13102 have if they know it is too old for a client to use. Closes
13105 o Minor features (ed25519 link handshake):
13106 - Advertise support for the ed25519 link handshake using the
13107 subprotocol-versions mechanism, so that clients can tell which
13108 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
13110 o Minor features (fingerprinting resistance, authentication):
13111 - Extend the length of RSA keys used for TLS link authentication to
13112 2048 bits. (These weren't used for forward secrecy; for forward
13113 secrecy, we used P256.) Closes ticket 13752.
13115 o Minor features (infrastructure):
13116 - Implement smartlist_add_strdup() function. Replaces the use of
13117 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
13119 o Minor bugfixes (client):
13120 - When clients that use bridges start up with a cached consensus on
13121 disk, they were ignoring it and downloading a new one. Now they
13122 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
13124 o Minor bugfixes (configuration):
13125 - Accept non-space whitespace characters after the severity level in
13126 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
13127 - Support "TByte" and "TBytes" units in options given in bytes.
13128 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
13129 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
13131 o Minor bugfixes (consensus weight):
13132 - Add new consensus method that initializes bw weights to 1 instead
13133 of 0. This prevents a zero weight from making it all the way to
13134 the end (happens in small testing networks) and causing an error.
13135 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
13137 o Minor bugfixes (descriptors):
13138 - Correctly recognise downloaded full descriptors as valid, even
13139 when using microdescriptors as circuits. This affects clients with
13140 FetchUselessDescriptors set, and may affect directory authorities.
13141 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
13143 o Minor bugfixes (directory system):
13144 - Download all consensus flavors, descriptors, and authority
13145 certificates when FetchUselessDescriptors is set, regardless of
13146 whether tor is a directory cache or not. Fixes bug 20667; bugfix
13147 on all recent tor versions.
13148 - Bridges and relays now use microdescriptors (like clients do)
13149 rather than old-style router descriptors. Now bridges will blend
13150 in with clients in terms of the circuits they build. Fixes bug
13151 6769; bugfix on 0.2.3.2-alpha.
13153 o Minor bugfixes (ed25519 certificates):
13154 - Correctly interpret ed25519 certificates that would expire some
13155 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
13157 o Minor bugfixes (hidden services):
13158 - Stop ignoring misconfigured hidden services. Instead, refuse to
13159 start tor until the misconfigurations have been corrected. Fixes
13160 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
13163 o Minor bugfixes (memory leak at exit):
13164 - Fix a small harmless memory leak at exit of the previously unused
13165 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
13168 o Minor bugfixes (util):
13169 - When finishing writing a file to disk, if we were about to replace
13170 the file with the temporary file created before and we fail to
13171 replace it, remove the temporary file so it doesn't stay on disk.
13172 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
13174 o Minor bugfixes (Windows):
13175 - Check for getpagesize before using it to mmap files. This fixes
13176 compilation in some MinGW environments. Fixes bug 20530; bugfix on
13177 0.1.2.1-alpha. Reported by "ice".
13179 o Code simplification and refactoring:
13180 - Abolish all global guard context in entrynodes.c; replace with new
13181 guard_selection_t structure as preparation for proposal 271.
13182 Closes ticket 19858.
13183 - Introduce rend_service_is_ephemeral() that tells if given onion
13184 service is ephemeral. Replace unclear NULL-checkings for service
13185 directory with this function. Closes ticket 20526.
13186 - Extract magic numbers in circuituse.c into defined variables.
13187 - Refactor circuit_is_available_for_use to remove unnecessary check.
13188 - Refactor circuit_predict_and_launch_new for readability and
13189 testability. Closes ticket 18873.
13190 - Refactor large if statement in purpose_needs_anonymity to use
13191 switch statement instead. Closes part of ticket 20077.
13192 - Refactor the hashing API to return negative values for errors, as
13193 is done as throughout the codebase. Closes ticket 20717.
13194 - Remove data structures that were used to index or_connection
13195 objects by their RSA identity digests. These structures are fully
13196 redundant with the similar structures used in the
13197 channel abstraction.
13198 - Remove duplicate code in the channel_write_*cell() functions.
13199 Closes ticket 13827; patch from Pingl.
13200 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
13201 use only purpose_needs_anonymity. Closes part of ticket 20077.
13202 - The code to generate and parse EXTEND and EXTEND2 cells has been
13203 replaced with code automatically generated by the
13207 - Include the "TBits" unit in Tor's man page. Fixes part of bug
13208 20622; bugfix on 0.2.5.1-alpha.
13209 - Change '1' to 'weight_scale' in consensus bw weights calculation
13210 comments, as that is reality. Closes ticket 20273. Patch
13212 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
13213 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
13215 - Stop the man page from incorrectly stating that HiddenServiceDir
13216 must already exist. Fixes 20486.
13217 - Clarify that when ClientRejectInternalAddresses is enabled (which
13218 is the default), multicast DNS hostnames for machines on the local
13219 network (of the form *.local) are also rejected. Closes
13222 o Removed features:
13223 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
13224 limit for relays running on a single IP applies to authority IP
13225 addresses as well as to non-authority IP addresses. Closes
13227 - The UseDirectoryGuards torrc option no longer exists: all users
13228 that use entry guards will also use directory guards. Related to
13229 proposal 271; implements part of ticket 20831.
13232 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
13233 from "overcaffeinated".
13234 - Perform the coding style checks when running the tests and fail
13235 when coding style violations are found. Closes ticket 5500.
13236 - Add tests for networkstatus_compute_bw_weights_v10.
13237 - Add unit tests circuit_predict_and_launch_new.
13238 - Extract dummy_origin_circuit_new so it can be used by other
13242 Changes in version 0.2.8.12 - 2016-12-19
13243 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
13244 below) where Tor clients could crash when attempting to visit a
13245 hostile hidden service. Clients are recommended to upgrade as packages
13246 become available for their systems.
13248 It also includes an updated list of fallback directories, backported
13251 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
13252 backported to 0.2.8 in the future.
13254 o Major bugfixes (parsing, security, backported from 0.2.9.8):
13255 - Fix a bug in parsing that could cause clients to read a single
13256 byte past the end of an allocated region. This bug could be used
13257 to cause hardened clients (built with --enable-expensive-hardening)
13258 to crash if they tried to visit a hostile hidden service. Non-
13259 hardened clients are only affected depending on the details of
13260 their platform's memory allocator. Fixes bug 21018; bugfix on
13261 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13262 2016-12-002 and as CVE-2016-1254.
13264 o Minor features (fallback directory list, backported from 0.2.9.8):
13265 - Replace the 81 remaining fallbacks of the 100 originally
13266 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13267 fallbacks (123 new, 54 existing, 27 removed) generated in December
13268 2016. Resolves ticket 20170.
13270 o Minor features (geoip, backported from 0.2.9.7-rc):
13271 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13275 Changes in version 0.2.9.8 - 2016-12-19
13276 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
13278 The Tor 0.2.9 series makes mandatory a number of security features
13279 that were formerly optional. It includes support for a new shared-
13280 randomness protocol that will form the basis for next generation
13281 hidden services, includes a single-hop hidden service mode for
13282 optimizing .onion services that don't actually want to be hidden,
13283 tries harder not to overload the directory authorities with excessive
13284 downloads, and supports a better protocol versioning scheme for
13285 improved compatibility with other implementations of the Tor protocol.
13287 And of course, there are numerous other bugfixes and improvements.
13289 This release also includes a fix for a medium-severity issue (bug
13290 21018 below) where Tor clients could crash when attempting to visit a
13291 hostile hidden service. Clients are recommended to upgrade as packages
13292 become available for their systems.
13294 Below are the changes since 0.2.9.7-rc. For a list of all changes
13295 since 0.2.8, see the ReleaseNotes file.
13297 o Major bugfixes (parsing, security):
13298 - Fix a bug in parsing that could cause clients to read a single
13299 byte past the end of an allocated region. This bug could be used
13300 to cause hardened clients (built with --enable-expensive-hardening)
13301 to crash if they tried to visit a hostile hidden service. Non-
13302 hardened clients are only affected depending on the details of
13303 their platform's memory allocator. Fixes bug 21018; bugfix on
13304 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13305 2016-12-002 and as CVE-2016-1254.
13307 o Minor features (fallback directory list):
13308 - Replace the 81 remaining fallbacks of the 100 originally
13309 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13310 fallbacks (123 new, 54 existing, 27 removed) generated in December
13311 2016. Resolves ticket 20170.
13314 Changes in version 0.2.9.7-rc - 2016-12-12
13315 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
13316 including a few that had prevented tests from passing on
13319 o Minor features (geoip):
13320 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13323 o Minor bugfix (build):
13324 - The current Git revision when building from a local repository is
13325 now detected correctly when using git worktrees. Fixes bug 20492;
13326 bugfix on 0.2.3.9-alpha.
13328 o Minor bugfixes (directory authority):
13329 - When computing old Tor protocol line version in protover, we were
13330 looking at 0.2.7.5 twice instead of a specific case for
13331 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
13333 o Minor bugfixes (download scheduling):
13334 - Resolve a "bug" warning when considering a download schedule whose
13335 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
13337 o Minor bugfixes (logging):
13338 - Downgrade a harmless log message about the
13339 pending_entry_connections list from "warn" to "info". Mitigates
13342 o Minor bugfixes (memory leak):
13343 - Fix a small memory leak when receiving AF_UNIX connections on a
13344 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
13345 - When moving a signed descriptor object from a source to an
13346 existing destination, free the allocated memory inside that
13347 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
13349 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
13350 - Fix a memory leak and use-after-free error when removing entries
13351 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
13352 0.2.5.5-alpha. Patch from "cypherpunks".
13354 o Minor bugfixes (portability):
13355 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
13356 Fixes bug 20935; bugfix on 0.2.9.6-rc.
13358 o Minor bugfixes (unit tests):
13359 - Stop expecting NetBSD unit tests to report success for ipfw. Part
13360 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
13361 - Fix tolerances in unit tests for monotonic time comparisons
13362 between nanoseconds and microseconds. Previously, we accepted a 10
13363 us difference only, which is not realistic on every platform's
13364 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
13365 - Remove a double-free in the single onion service unit test. Stop
13366 ignoring a return value. Make future changes less error-prone.
13367 Fixes bug 20864; bugfix on 0.2.9.6-rc.
13370 Changes in version 0.2.8.11 - 2016-12-08
13371 Tor 0.2.8.11 backports fixes for additional portability issues that
13372 could prevent Tor from building correctly on OSX Sierra, or with
13373 OpenSSL 1.1. Affected users should upgrade; others can safely stay
13376 o Minor bugfixes (portability):
13377 - Avoid compilation errors when building on OSX Sierra. Sierra began
13378 to support the getentropy() and clock_gettime() APIs, but created
13379 a few problems in doing so. Tor 0.2.9 has a more thorough set of
13380 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
13381 monotonic time interfaces. Fixes bug 20865. Bugfix
13384 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13385 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13386 architectures. Closes ticket 20588.
13389 Changes in version 0.2.8.10 - 2016-12-02
13390 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
13391 unusable after they left standby mode. It also backports fixes for
13392 a few portability issues and a small but problematic memory leak.
13394 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
13395 - When Tor leaves standby because of a new application request, open
13396 circuits as needed to serve that request. Previously, we would
13397 potentially wait a very long time. Fixes part of bug 19969; bugfix
13400 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
13401 - Clients now respond to new application stream requests immediately
13402 when they arrive, rather than waiting up to one second before
13403 starting to handle them. Fixes part of bug 19969; bugfix
13406 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
13407 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13408 successfully targeting earlier versions of OSX. Resolves
13411 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13412 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13413 20551; bugfix on 0.2.1.1-alpha.
13415 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
13416 - Work around a memory leak in OpenSSL 1.1 when encoding public
13417 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13419 o Minor features (geoip):
13420 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13423 Changes in version 0.2.9.6-rc - 2016-12-02
13424 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
13425 version. We hope that it will be ready to become stable soon, and we
13426 encourage everyone to test this release. If no showstopper bugs are
13427 found here, the next 0.2.9 release will be stable.
13429 o Major bugfixes (relay, resolver, logging):
13430 - For relays that don't know their own address, avoid attempting a
13431 local hostname resolve for each descriptor we download. This
13432 will cut down on the number of "Success: chose address 'x.x.x.x'"
13433 log lines, and also avoid confusing clock jumps if the resolver
13434 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
13436 o Minor bugfixes (client, fascistfirewall):
13437 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
13438 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
13440 o Minor bugfixes (hidden services):
13441 - Stop ignoring the anonymity status of saved keys for hidden
13442 services and single onion services when first starting tor.
13443 Instead, refuse to start tor if any hidden service key has been
13444 used in a different hidden service anonymity mode. Fixes bug
13445 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
13447 o Minor bugfixes (portability):
13448 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13449 successfully targeting earlier versions of OSX. Resolves
13451 - Run correctly when built on Windows build environments that
13452 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
13454 o Minor bugfixes (single onion services, Tor2web):
13455 - Stop complaining about long-term one-hop circuits deliberately
13456 created by single onion services and Tor2web. These log messages
13457 are intended to diagnose issue 8387, which relates to circuits
13458 hanging around forever for no reason. Fixes bug 20613; bugfix on
13459 0.2.9.1-alpha. Reported by "pastly".
13461 o Minor bugfixes (unit tests):
13462 - Stop spurious failures in the local interface address discovery
13463 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
13467 - Correct the minimum bandwidth value in torrc.sample, and queue a
13468 corresponding change for torrc.minimal. Closes ticket 20085.
13471 Changes in version 0.2.9.5-alpha - 2016-11-08
13472 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
13473 version. We believe one or two probably remain, and we encourage
13474 everyone to test this release.
13476 o Major bugfixes (client performance):
13477 - Clients now respond to new application stream requests immediately
13478 when they arrive, rather than waiting up to one second before
13479 starting to handle them. Fixes part of bug 19969; bugfix
13482 o Major bugfixes (client reliability):
13483 - When Tor leaves standby because of a new application request, open
13484 circuits as needed to serve that request. Previously, we would
13485 potentially wait a very long time. Fixes part of bug 19969; bugfix
13488 o Major bugfixes (download scheduling):
13489 - When using an exponential backoff schedule, do not give up on
13490 downloading just because we have failed a bunch of times. Since
13491 each delay is longer than the last, retrying indefinitely won't
13492 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
13493 - If a consensus expires while we are waiting for certificates to
13494 download, stop waiting for certificates.
13495 - If we stop waiting for certificates less than a minute after we
13496 started downloading them, do not consider the certificate download
13497 failure a separate failure. Fixes bug 20533; bugfix
13499 - Remove the maximum delay on exponential-backoff scheduling. Since
13500 we now allow an infinite number of failures (see ticket 20536), we
13501 must now allow the time to grow longer on each failure. Fixes part
13502 of bug 20534; bugfix on 0.2.9.1-alpha.
13503 - Make our initial download delays closer to those from 0.2.8. Fixes
13504 another part of bug 20534; bugfix on 0.2.9.1-alpha.
13505 - When determining when to download a directory object, handle times
13506 after 2038 if the operating system supports them. (Someday this
13507 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
13508 - When using exponential backoff in test networks, use a lower
13509 exponent, so the delays do not vary as much. This helps test
13510 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
13512 o Minor features (geoip):
13513 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13516 o Minor bugfixes (client directory scheduling):
13517 - Treat "relay too busy to answer request" as a failed request and a
13518 reason to back off on our retry frequency. This is safe now that
13519 exponential backoffs retry indefinitely, and avoids a bug where we
13520 would reset our download schedule erroneously. Fixes bug 20593;
13521 bugfix on 0.2.9.1-alpha.
13523 o Minor bugfixes (client, logging):
13524 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
13525 assume all nodes support EXTEND2. Use ntor whenever a key is
13526 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
13527 - On DNSPort, stop logging a BUG warning on a failed hostname
13528 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
13530 o Minor bugfixes (hidden services):
13531 - When configuring hidden services, check every hidden service
13532 directory's permissions. Previously, we only checked the last
13533 hidden service. Fixes bug 20529; bugfix the work to fix 13942
13536 o Minor bugfixes (portability):
13537 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13538 architectures. Closes ticket 20588.
13539 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
13540 removed the ECDH ciphers which caused the tests to fail on
13541 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
13542 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13543 20551; bugfix on 0.2.1.1-alpha.
13545 o Minor bugfixes (relay bootstrap):
13546 - Ensure relays don't make multiple connections during bootstrap.
13547 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
13549 o Minor bugfixes (relay):
13550 - Work around a memory leak in OpenSSL 1.1 when encoding public
13551 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13552 - Avoid a small memory leak when informing worker threads about
13553 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
13554 - Do not try to parallelize workers more than 16x without the user
13555 explicitly configuring us to do so, even if we do detect more than
13556 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13558 o Minor bugfixes (single onion services):
13559 - Start correctly when creating a single onion service in a
13560 directory that did not previously exist. Fixes bug 20484; bugfix
13563 o Minor bugfixes (testing):
13564 - Avoid a unit test failure on systems with over 16 detectable CPU
13565 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13568 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
13569 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
13570 - Module-level documentation for several more modules. Closes
13571 tickets 19287 and 19290.
13574 Changes in version 0.2.8.9 - 2016-10-17
13575 Tor 0.2.8.9 backports a fix for a security hole in previous versions
13576 of Tor that would allow a remote attacker to crash a Tor client,
13577 hidden service, relay, or authority. All Tor users should upgrade to
13578 this version, or to 0.2.9.4-alpha. Patches will be released for older
13581 o Major features (security fixes, also in 0.2.9.4-alpha):
13582 - Prevent a class of security bugs caused by treating the contents
13583 of a buffer chunk as if they were a NUL-terminated string. At
13584 least one such bug seems to be present in all currently used
13585 versions of Tor, and would allow an attacker to remotely crash
13586 most Tor instances, especially those compiled with extra compiler
13587 hardening. With this defense in place, such bugs can't crash Tor,
13588 though we should still fix them as they occur. Closes ticket
13589 20384 (TROVE-2016-10-001).
13591 o Minor features (geoip):
13592 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
13596 Changes in version 0.2.9.4-alpha - 2016-10-17
13597 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
13598 that would allow a remote attacker to crash a Tor client, hidden
13599 service, relay, or authority. All Tor users should upgrade to this
13600 version, or to 0.2.8.9. Patches will be released for older versions
13603 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
13604 previous versions of Tor, including the implementation of a feature to
13605 future- proof the Tor ecosystem against protocol changes, some bug
13606 fixes necessary for Tor Browser to use unix domain sockets correctly,
13607 and several portability improvements. We anticipate that this will be
13608 the last alpha in the Tor 0.2.9 series, and that the next release will
13609 be a release candidate.
13611 o Major features (security fixes):
13612 - Prevent a class of security bugs caused by treating the contents
13613 of a buffer chunk as if they were a NUL-terminated string. At
13614 least one such bug seems to be present in all currently used
13615 versions of Tor, and would allow an attacker to remotely crash
13616 most Tor instances, especially those compiled with extra compiler
13617 hardening. With this defense in place, such bugs can't crash Tor,
13618 though we should still fix them as they occur. Closes ticket
13619 20384 (TROVE-2016-10-001).
13621 o Major features (subprotocol versions):
13622 - Tor directory authorities now vote on a set of recommended
13623 subprotocol versions, and on a set of required subprotocol
13624 versions. Clients and relays that lack support for a _required_
13625 subprotocol version will not start; those that lack support for a
13626 _recommended_ subprotocol version will warn the user to upgrade.
13627 Closes ticket 19958; implements part of proposal 264.
13628 - Tor now uses "subprotocol versions" to indicate compatibility.
13629 Previously, versions of Tor looked at the declared Tor version of
13630 a relay to tell whether they could use a given feature. Now, they
13631 should be able to rely on its declared subprotocol versions. This
13632 change allows compatible implementations of the Tor protocol(s) to
13633 exist without pretending to be 100% bug-compatible with particular
13634 releases of Tor itself. Closes ticket 19958; implements part of
13637 o Minor feature (fallback directories):
13638 - Remove broken fallbacks from the hard-coded fallback directory
13639 list. Closes ticket 20190; patch by teor.
13641 o Minor features (client, directory):
13642 - Since authorities now omit all routers that lack the Running and
13643 Valid flags, we assume that any relay listed in the consensus must
13644 have those flags. Closes ticket 20001; implements part of
13647 o Minor features (compilation, portability):
13648 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
13651 o Minor features (development tools, etags):
13652 - Teach the "make tags" Makefile target how to correctly find
13653 "MOCK_IMPL" function definitions. Patch from nherring; closes
13656 o Minor features (geoip):
13657 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
13660 o Minor features (unix domain sockets):
13661 - When configuring a unix domain socket for a SocksPort,
13662 ControlPort, or Hidden service, you can now wrap the address in
13663 quotes, using C-style escapes inside the quotes. This allows unix
13664 domain socket paths to contain spaces.
13666 o Minor features (virtual addresses):
13667 - Increase the maximum number of bits for the IPv6 virtual network
13668 prefix from 16 to 104. In this way, the condition for address
13669 allocation is less restrictive. Closes ticket 20151; feature
13672 o Minor bugfixes (address discovery):
13673 - Stop reordering IP addresses returned by the OS. This makes it
13674 more likely that Tor will guess the same relay IP address every
13675 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
13676 Reported by René Mayrhofer, patch by "cypherpunks".
13678 o Minor bugfixes (client, unix domain sockets):
13679 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
13680 the client address is meaningless. Fixes bug 20261; bugfix
13683 o Minor bugfixes (compilation, OpenBSD):
13684 - Detect Libevent2 functions correctly on systems that provide
13685 libevent2, but where libevent1 is linked with -levent. Fixes bug
13686 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
13688 o Minor bugfixes (configuration):
13689 - When parsing quoted configuration values from the torrc file,
13690 handle windows line endings correctly. Fixes bug 19167; bugfix on
13691 0.2.0.16-alpha. Patch from "Pingl".
13693 o Minor bugfixes (getpass):
13694 - Defensively fix a non-triggerable heap corruption at do_getpass()
13695 to protect ourselves from mistakes in the future. Fixes bug
13696 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
13699 o Minor bugfixes (hidden service):
13700 - Allow hidden services to run on IPv6 addresses even when the
13701 IPv6Exit option is not set. Fixes bug 18357; bugfix
13705 - Add module-level internal documentation for 36 C files that
13706 previously didn't have a high-level overview. Closes ticket #20385.
13708 o Required libraries:
13709 - When building with OpenSSL, Tor now requires version 1.0.1 or
13710 later. OpenSSL 1.0.0 and earlier are no longer supported by the
13711 OpenSSL team, and should not be used. Closes ticket 20303.
13714 Changes in version 0.2.9.3-alpha - 2016-09-23
13715 Tor 0.2.9.3-alpha adds improved support for entities that want to make
13716 high-performance services available through the Tor .onion mechanism
13717 without themselves receiving anonymity as they host those services. It
13718 also tries harder to ensure that all steps on a circuit are using the
13719 strongest crypto possible, strengthens some TLS properties, and
13720 resolves several bugs -- including a pair of crash bugs from the 0.2.8
13721 series. Anybody running an earlier version of 0.2.9.x should upgrade.
13723 o Major bugfixes (crash, also in 0.2.8.8):
13724 - Fix a complicated crash bug that could affect Tor clients
13725 configured to use bridges when replacing a networkstatus consensus
13726 in which one of their bridges was mentioned. OpenBSD users saw
13727 more crashes here, but all platforms were potentially affected.
13728 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
13730 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
13731 - Fix a timing-dependent assertion failure that could occur when we
13732 tried to flush from a circuit after having freed its cells because
13733 of an out-of-memory condition. Fixes bug 20203; bugfix on
13734 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
13737 o Major features (circuit building, security):
13738 - Authorities, relays and clients now require ntor keys in all
13739 descriptors, for all hops (except for rare hidden service protocol
13740 cases), for all circuits, and for all other roles. Part of
13742 - Tor authorities, relays, and clients only use ntor, except for
13743 rare cases in the hidden service protocol. Part of ticket 19163.
13745 o Major features (single-hop "hidden" services):
13746 - Add experimental HiddenServiceSingleHopMode and
13747 HiddenServiceNonAnonymousMode options. When both are set to 1,
13748 every hidden service on a Tor instance becomes a non-anonymous
13749 Single Onion Service. Single Onions make one-hop (direct)
13750 connections to their introduction and rendezvous points. One-hop
13751 circuits make Single Onion servers easily locatable, but clients
13752 remain location-anonymous. This is compatible with the existing
13753 hidden service implementation, and works on the current tor
13754 network without any changes to older relays or clients. Implements
13755 proposal 260, completes ticket 17178. Patch by teor and asn.
13757 o Major features (resource management):
13758 - Tor can now notice it is about to run out of sockets, and
13759 preemptively close connections of lower priority. (This feature is
13760 off by default for now, since the current prioritizing method is
13761 yet not mature enough. You can enable it by setting
13762 "DisableOOSCheck 0", but watch out: it might close some sockets
13763 you would rather have it keep.) Closes ticket 18640.
13765 o Major bugfixes (circuit building):
13766 - Hidden service client-to-intro-point and service-to-rendezvous-
13767 point circuits use the TAP key supplied by the protocol, to avoid
13768 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
13770 o Major bugfixes (compilation, OpenBSD):
13771 - Fix a Libevent-detection bug in our autoconf script that would
13772 prevent Tor from linking successfully on OpenBSD. Patch from
13773 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
13775 o Major bugfixes (hidden services):
13776 - Clients now require hidden services to include the TAP keys for
13777 their intro points in the hidden service descriptor. This prevents
13778 an inadvertent upgrade to ntor, which a malicious hidden service
13779 could use to distinguish clients by consensus version. Fixes bug
13780 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
13782 o Minor features (security, TLS):
13783 - Servers no longer support clients that without AES ciphersuites.
13784 (3DES is no longer considered an acceptable cipher.) We believe
13785 that no such Tor clients currently exist, since Tor has required
13786 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
13788 o Minor feature (fallback directories):
13789 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
13790 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
13791 2016. Closes ticket 20190; patch by teor.
13793 o Minor features (geoip, also in 0.2.8.8):
13794 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
13797 o Minor feature (port flags):
13798 - Add new flags to the *Port options to finer control over which
13799 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
13800 and the synthetic flag OnionTrafficOnly, which is equivalent to
13801 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
13802 18693; patch by "teor".
13804 o Minor features (directory authority):
13805 - After voting, if the authorities decide that a relay is not
13806 "Valid", they no longer include it in the consensus at all. Closes
13807 ticket 20002; implements part of proposal 272.
13809 o Minor features (testing):
13810 - Disable memory protections on OpenBSD when performing our unit
13811 tests for memwipe(). The test deliberately invokes undefined
13812 behavior, and the OpenBSD protections interfere with this. Patch
13813 from "rubiate". Closes ticket 20066.
13815 o Minor features (testing, ipv6):
13816 - Add the single-onion and single-onion-ipv6 chutney targets to
13817 "make test-network-all". This requires a recent chutney version
13818 with the single onion network flavours (git c72a652 or later).
13819 Closes ticket 20072; patch by teor.
13820 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
13821 tests. Remove bridges+hs, as it's somewhat redundant. This
13822 requires a recent chutney version that supports IPv6 clients,
13823 relays, and authorities. Closes ticket 20069; patch by teor.
13825 o Minor features (Tor2web):
13826 - Make Tor2web clients respect ReachableAddresses. This feature was
13827 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
13828 0.2.8.7. Implements feature 20034. Patch by teor.
13830 o Minor features (unit tests):
13831 - We've done significant work to make the unit tests run faster.
13832 - Our link-handshake unit tests now check that when invalid
13833 handshakes fail, they fail with the error messages we expected.
13834 - Our unit testing code that captures log messages no longer
13835 prevents them from being written out if the user asked for them
13836 (by passing --debug or --info or or --notice --warn to the "test"
13837 binary). This change prevents us from missing unexpected log
13838 messages simply because we were looking for others. Related to
13840 - The unit tests now log all warning messages with the "BUG" flag.
13841 Previously, they only logged errors by default. This change will
13842 help us make our testing code more correct, and make sure that we
13843 only hit this code when we mean to. In the meantime, however,
13844 there will be more warnings in the unit test logs than before.
13845 This is preparatory work for ticket 19999.
13846 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
13847 assertion as a test failure.
13849 o Minor bug fixes (circuits):
13850 - Use the CircuitBuildTimeout option whenever
13851 LearnCircuitBuildTimeout is disabled. Previously, we would respect
13852 the option when a user disabled it, but not when it was disabled
13853 because some other option was set. Fixes bug 20073; bugfix on
13854 0.2.4.12-alpha. Patch by teor.
13856 o Minor bugfixes (allocation):
13857 - Change how we allocate memory for large chunks on buffers, to
13858 avoid a (currently impossible) integer overflow, and to waste less
13859 space when allocating unusually large chunks. Fixes bug 20081;
13860 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
13861 - Always include orconfig.h before including any other C headers.
13862 Sometimes, it includes macros that affect the behavior of the
13863 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
13864 first version to use AC_USE_SYSTEM_EXTENSIONS).
13865 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
13866 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
13867 Patch from Gisle Vanem.
13868 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
13869 They apparently require a set of annotations that we aren't
13870 currently using, and they create false positives in our pthreads
13871 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
13873 o Minor bugfixes (directory authority):
13874 - Die with a more useful error when the operator forgets to place
13875 the authority_signing_key file into the keys directory. This
13876 avoids an uninformative assert & traceback about having an invalid
13877 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
13878 - When allowing private addresses, mark Exits that only exit to
13879 private locations as such. Fixes bug 20064; bugfix
13882 o Minor bugfixes (documentation):
13883 - Document the default PathsNeededToBuildCircuits value that's used
13884 by clients when the directory authorities don't set
13885 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
13886 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
13887 - Fix manual for the User option: it takes a username, not a UID.
13888 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
13891 o Minor bugfixes (hidden services):
13892 - Stop logging intro point details to the client log on certain
13893 error conditions. Fixed as part of bug 20012; bugfix on
13894 0.2.4.8-alpha. Patch by teor.
13896 o Minor bugfixes (IPv6, testing):
13897 - Check for IPv6 correctly on Linux when running test networks.
13898 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
13900 o Minor bugfixes (Linux seccomp2 sandbox):
13901 - Add permission to run the sched_yield() and sigaltstack() system
13902 calls, in order to support versions of Tor compiled with asan or
13903 ubsan code that use these calls. Now "sandbox 1" and
13904 "--enable-expensive-hardening" should be compatible on more
13905 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
13907 o Minor bugfixes (logging):
13908 - When logging a message from the BUG() macro, be explicit about
13909 what we were asserting. Previously we were confusing what we were
13910 asserting with what the bug was. Fixes bug 20093; bugfix
13912 - When we are unable to remove the bw_accounting file, do not warn
13913 if the reason we couldn't remove it was that it didn't exist.
13914 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
13916 o Minor bugfixes (option parsing):
13917 - Count unix sockets when counting client listeners (SOCKS, Trans,
13918 NATD, and DNS). This has no user-visible behaviour changes: these
13919 options are set once, and never read. Required for correct
13920 behaviour in ticket 17178. Fixes bug 19677; bugfix on
13921 0.2.6.3-alpha. Patch by teor.
13923 o Minor bugfixes (options):
13924 - Check the consistency of UseEntryGuards and EntryNodes more
13925 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
13927 - Stop changing the configured value of UseEntryGuards on
13928 authorities and Tor2web clients. Fixes bug 20074; bugfix on
13929 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
13932 o Minor bugfixes (Tor2web):
13933 - Prevent Tor2web clients running hidden services, these services
13934 are not anonymous due to the one-hop client paths. Fixes bug
13935 19678. Patch by teor.
13937 o Minor bugfixes (unit tests):
13938 - Fix a shared-random unit test that was failing on big endian
13939 architectures due to internal representation of a integer copied
13940 to a buffer. The test is changed to take a full 32 bytes of data
13941 and use the output of a python script that make the COMMIT and
13942 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
13944 - The tor_tls_server_info_callback unit test no longer crashes when
13945 debug-level logging is turned on. Fixes bug 20041; bugfix
13949 Changes in version 0.2.8.8 - 2016-09-23
13950 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
13951 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
13952 who select public relays as their bridges.
13954 o Major bugfixes (crash):
13955 - Fix a complicated crash bug that could affect Tor clients
13956 configured to use bridges when replacing a networkstatus consensus
13957 in which one of their bridges was mentioned. OpenBSD users saw
13958 more crashes here, but all platforms were potentially affected.
13959 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
13961 o Major bugfixes (relay, OOM handler):
13962 - Fix a timing-dependent assertion failure that could occur when we
13963 tried to flush from a circuit after having freed its cells because
13964 of an out-of-memory condition. Fixes bug 20203; bugfix on
13965 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
13968 o Minor feature (fallback directories):
13969 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
13970 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
13971 2016. Closes ticket 20190; patch by teor.
13973 o Minor features (geoip):
13974 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
13978 Changes in version 0.2.9.2-alpha - 2016-08-24
13979 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
13980 several new features and bugfixes. It also includes an important
13981 authority update and an important bugfix from 0.2.8.7. Everyone who
13982 sets the ReachableAddresses option, and all bridges, are strongly
13983 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
13985 o Directory authority changes (also in 0.2.8.7):
13986 - The "Tonga" bridge authority has been retired; the new bridge
13987 authority is "Bifroest". Closes tickets 19728 and 19690.
13989 o Major bugfixes (client, security, also in 0.2.8.7):
13990 - Only use the ReachableAddresses option to restrict the first hop
13991 in a path. In earlier versions of 0.2.8.x, it would apply to
13992 every hop in the path, with a possible degradation in anonymity
13993 for anyone using an uncommon ReachableAddress setting. Fixes bug
13994 19973; bugfix on 0.2.8.2-alpha.
13996 o Major features (user interface):
13997 - Tor now supports the ability to declare options deprecated, so
13998 that we can recommend that people stop using them. Previously,
13999 this was done in an ad-hoc way. Closes ticket 19820.
14001 o Major bugfixes (directory downloads):
14002 - Avoid resetting download status for consensuses hourly, since we
14003 already have another, smarter retry mechanism. Fixes bug 8625;
14004 bugfix on 0.2.0.9-alpha.
14006 o Minor features (config):
14007 - Warn users when descriptor and port addresses are inconsistent.
14008 Mitigates bug 13953; patch by teor.
14010 o Minor features (geoip):
14011 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14014 o Minor features (user interface):
14015 - There is a new --list-deprecated-options command-line option to
14016 list all of the deprecated options. Implemented as part of
14019 o Minor bugfixes (code style):
14020 - Fix an integer signedness conversion issue in the case conversion
14021 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
14023 o Minor bugfixes (compilation):
14024 - Build correctly on versions of libevent2 without support for
14025 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
14027 - Fix a compilation warning on GCC versions before 4.6. Our
14028 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
14029 when it is also required as an argument to the compiler pragma.
14030 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
14032 o Minor bugfixes (compilation, also in 0.2.8.7):
14033 - Remove an inappropriate "inline" in tortls.c that was causing
14034 warnings on older versions of GCC. Fixes bug 19903; bugfix
14037 o Minor bugfixes (fallback directories, also in 0.2.8.7):
14038 - Avoid logging a NULL string pointer when loading fallback
14039 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14040 and 0.2.8.1-alpha. Report and patch by "rubiate".
14042 o Minor bugfixes (logging):
14043 - Log a more accurate message when we fail to dump a microdescriptor.
14044 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
14046 o Minor bugfixes (memory leak):
14047 - Fix a series of slow memory leaks related to parsing torrc files
14048 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
14050 o Deprecated features:
14051 - A number of DNS-cache-related sub-options for client ports are now
14052 deprecated for security reasons, and may be removed in a future
14053 version of Tor. (We believe that client-side DNS caching is a bad
14054 idea for anonymity, and you should not turn it on.) The options
14055 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
14056 UseIPv4Cache, and UseIPv6Cache.
14057 - A number of options are deprecated for security reasons, and may
14058 be removed in a future version of Tor. The options are:
14059 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
14060 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
14061 CloseHSClientCircuitsImmediatelyOnTimeout,
14062 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
14063 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
14064 UseNTorHandshake, and WarnUnsafeSocks.
14065 - The *ListenAddress options are now deprecated as unnecessary: the
14066 corresponding *Port options should be used instead. These options
14067 may someday be removed. The affected options are:
14068 ControlListenAddress, DNSListenAddress, DirListenAddress,
14069 NATDListenAddress, ORListenAddress, SocksListenAddress,
14070 and TransListenAddress.
14073 - Correct the IPv6 syntax in our documentation for the
14074 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
14077 - We no longer include the (dead, deprecated) bufferevent code in
14078 Tor. Closes ticket 19450. Based on a patch from U+039b.
14081 Changes in version 0.2.8.7 - 2016-08-24
14082 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
14083 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
14084 who sets the ReachableAddresses option, and all bridges, are strongly
14085 encouraged to upgrade.
14087 o Directory authority changes:
14088 - The "Tonga" bridge authority has been retired; the new bridge
14089 authority is "Bifroest". Closes tickets 19728 and 19690.
14091 o Major bugfixes (client, security):
14092 - Only use the ReachableAddresses option to restrict the first hop
14093 in a path. In earlier versions of 0.2.8.x, it would apply to
14094 every hop in the path, with a possible degradation in anonymity
14095 for anyone using an uncommon ReachableAddress setting. Fixes bug
14096 19973; bugfix on 0.2.8.2-alpha.
14098 o Minor features (geoip):
14099 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14102 o Minor bugfixes (compilation):
14103 - Remove an inappropriate "inline" in tortls.c that was causing
14104 warnings on older versions of GCC. Fixes bug 19903; bugfix
14107 o Minor bugfixes (fallback directories):
14108 - Avoid logging a NULL string pointer when loading fallback
14109 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14110 and 0.2.8.1-alpha. Report and patch by "rubiate".
14113 Changes in version 0.2.9.1-alpha - 2016-08-08
14114 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
14115 series. It improves our support for hardened builds and compiler
14116 warnings, deploys some critical infrastructure for improvements to
14117 hidden services, includes a new timing backend that we hope to use for
14118 better support for traffic padding, makes it easier for programmers to
14119 log unexpected events, and contains other small improvements to
14120 security, correctness, and performance.
14122 Below are the changes since 0.2.8.6.
14124 o New system requirements:
14125 - Tor now requires Libevent version 2.0.10-stable or later. Older
14126 versions of Libevent have less efficient backends for several
14127 platforms, and lack the DNS code that we use for our server-side
14128 DNS support. This implements ticket 19554.
14129 - Tor now requires zlib version 1.2 or later, for security,
14130 efficiency, and (eventually) gzip support. (Back when we started,
14131 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
14132 released in 2003. We recommend the latest version.)
14134 o Major features (build, hardening):
14135 - Tor now builds with -ftrapv by default on compilers that support
14136 it. This option detects signed integer overflow (which C forbids),
14137 and turns it into a hard-failure. We do not apply this option to
14138 code that needs to run in constant time to avoid side-channels;
14139 instead, we use -fwrapv in that code. Closes ticket 17983.
14140 - When --enable-expensive-hardening is selected, stop applying the
14141 clang/gcc sanitizers to code that needs to run in constant time.
14142 Although we are aware of no introduced side-channels, we are not
14143 able to prove that there are none. Related to ticket 17983.
14145 o Major features (compilation):
14146 - Our big list of extra GCC warnings is now enabled by default when
14147 building with GCC (or with anything like Clang that claims to be
14148 GCC-compatible). To make all warnings into fatal compilation
14149 errors, pass --enable-fatal-warnings to configure. Closes
14151 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
14152 turn on C and POSIX extensions. (Previously, we attempted to do
14153 this on an ad hoc basis.) Closes ticket 19139.
14155 o Major features (directory authorities, hidden services):
14156 - Directory authorities can now perform the shared randomness
14157 protocol specified by proposal 250. Using this protocol, directory
14158 authorities generate a global fresh random value every day. In the
14159 future, this value will be used by hidden services to select
14160 HSDirs. This release implements the directory authority feature;
14161 the hidden service side will be implemented in the future as part
14162 of proposal 224. Resolves ticket 16943; implements proposal 250.
14164 o Major features (downloading, random exponential backoff):
14165 - When we fail to download an object from a directory service, wait
14166 for an (exponentially increasing) randomized amount of time before
14167 retrying, rather than a fixed interval as we did before. This
14168 prevents a group of Tor instances from becoming too synchronized,
14169 or a single Tor instance from becoming too predictable, in its
14170 download schedule. Closes ticket 15942.
14172 o Major bugfixes (exit policies):
14173 - Avoid disclosing exit outbound bind addresses, configured port
14174 bind addresses, and local interface addresses in relay descriptors
14175 by default under ExitPolicyRejectPrivate. Instead, only reject
14176 these (otherwise unlisted) addresses if
14177 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
14178 0.2.7.2-alpha. Patch by teor.
14180 o Major bugfixes (hidden service client):
14181 - Allow Tor clients with appropriate controllers to work with
14182 FetchHidServDescriptors set to 0. Previously, this option also
14183 disabled descriptor cache lookup, thus breaking hidden services
14184 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
14186 o Minor features (build, hardening):
14187 - Detect and work around a libclang_rt problem that would prevent
14188 clang from finding __mulodi4() on some 32-bit platforms, and thus
14189 keep -ftrapv from linking on those systems. Closes ticket 19079.
14190 - When building on a system without runtime support for the runtime
14191 hardening options, try to log a useful warning at configuration
14192 time, rather than an incomprehensible warning at link time. If
14193 expensive hardening was requested, this warning becomes an error.
14194 Closes ticket 18895.
14196 o Minor features (code safety):
14197 - In our integer-parsing functions, ensure that maxiumum value we
14198 give is no smaller than the minimum value. Closes ticket 19063;
14201 o Minor features (controller):
14202 - Implement new GETINFO queries for all downloads that use
14203 download_status_t to schedule retries. This allows controllers to
14204 examine the schedule for pending downloads. Closes ticket 19323.
14205 - Allow controllers to configure basic client authorization on
14206 hidden services when they create them with the ADD_ONION control
14207 command. Implements ticket 15588. Patch by "special".
14208 - Fire a STATUS_SERVER controller event whenever the hibernation
14209 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
14211 o Minor features (directory authority):
14212 - Directory authorities now only give the Guard flag to a relay if
14213 they are also giving it the Stable flag. This change allows us to
14214 simplify path selection for clients. It should have minimal effect
14215 in practice, since >99% of Guards already have the Stable flag.
14216 Implements ticket 18624.
14217 - Directory authorities now write their v3-status-votes file out to
14218 disk earlier in the consensus process, so we have a record of the
14219 votes even if we abort the consensus process. Resolves
14222 o Minor features (hidden service):
14223 - Stop being so strict about the payload length of "rendezvous1"
14224 cells. We used to be locked in to the "TAP" handshake length, and
14225 now we can handle better handshakes like "ntor". Resolves
14228 o Minor features (infrastructure, time):
14229 - Tor now uses the operating system's monotonic timers (where
14230 available) for internal fine-grained timing. Previously we would
14231 look at the system clock, and then attempt to compensate for the
14232 clock running backwards. Closes ticket 18908.
14233 - Tor now includes an improved timer backend, so that we can
14234 efficiently support tens or hundreds of thousands of concurrent
14235 timers, as will be needed for some of our planned anti-traffic-
14236 analysis work. This code is based on William Ahern's "timeout.c"
14237 project, which implements a "tickless hierarchical timing wheel".
14238 Closes ticket 18365.
14240 o Minor features (logging):
14241 - Provide a more useful warning message when configured with an
14242 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
14243 - When dumping unparseable router descriptors, optionally store them
14244 in separate files, named by digest, up to a configurable size
14245 limit. You can change the size limit by setting the
14246 MaxUnparseableDescSizeToLog option, and disable this feature by
14247 setting that option to 0. Closes ticket 18322.
14248 - Add a set of macros to check nonfatal assertions, for internal
14249 use. Migrating more of our checks to these should help us avoid
14250 needless crash bugs. Closes ticket 18613.
14252 o Minor features (performance):
14253 - Change the "optimistic data" extension from "off by default" to
14254 "on by default". The default was ordinarily overridden by a
14255 consensus option, but when clients were bootstrapping for the
14256 first time, they would not have a consensus to get the option
14257 from. Changing this default saves a round-trip during startup.
14258 Closes ticket 18815.
14260 o Minor features (relay, usability):
14261 - When the directory authorities refuse a bad relay's descriptor,
14262 encourage the relay operator to contact us. Many relay operators
14263 won't notice this line in their logs, but it's a win if even a few
14264 learn why we don't like what their relay was doing. Resolves
14267 o Minor features (testing):
14268 - Let backtrace tests work correctly under AddressSanitizer. Fixes
14269 part of bug 18934; bugfix on 0.2.5.2-alpha.
14270 - Move the test-network.sh script to chutney, and modify tor's test-
14271 network.sh to call the (newer) chutney version when available.
14272 Resolves ticket 19116. Patch by teor.
14273 - Use the lcov convention for marking lines as unreachable, so that
14274 we don't count them when we're generating test coverage data.
14275 Update our coverage tools to understand this convention. Closes
14278 o Minor bugfixes (bootstrap):
14279 - Remember the directory we fetched the consensus or previous
14280 certificates from, and use it to fetch future authority
14281 certificates. This change improves bootstrapping performance.
14282 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
14284 o Minor bugfixes (build):
14285 - The test-stem and test-network makefile targets now depend only on
14286 the tor binary that they are testing. Previously, they depended on
14287 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
14288 patch from "cypherpunks".
14290 o Minor bugfixes (circuits):
14291 - Make sure extend_info_from_router() is only called on servers.
14292 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
14294 o Minor bugfixes (compilation):
14295 - When building with Clang, use a full set of GCC warnings.
14296 (Previously, we included only a subset, because of the way we
14297 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
14299 o Minor bugfixes (directory authority):
14300 - Authorities now sort the "package" lines in their votes, for ease
14301 of debugging. (They are already sorted in consensus documents.)
14302 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
14303 - When parsing a detached signature, make sure we use the length of
14304 the digest algorithm instead of an hardcoded DIGEST256_LEN in
14305 order to avoid comparing bytes out-of-bounds with a smaller digest
14306 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
14308 o Minor bugfixes (documentation):
14309 - Document the --passphrase-fd option in the tor manpage. Fixes bug
14310 19504; bugfix on 0.2.7.3-rc.
14311 - Fix the description of the --passphrase-fd option in the
14312 tor-gencert manpage. The option is used to pass the number of a
14313 file descriptor to read the passphrase from, not to read the file
14314 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
14316 o Minor bugfixes (ephemeral hidden service):
14317 - When deleting an ephemeral hidden service, close its intro points
14318 even if they are not completely open. Fixes bug 18604; bugfix
14321 o Minor bugfixes (guard selection):
14322 - Use a single entry guard even if the NumEntryGuards consensus
14323 parameter is not provided. Fixes bug 17688; bugfix
14325 - Don't mark guards as unreachable if connection_connect() fails.
14326 That function fails for local reasons, so it shouldn't reveal
14327 anything about the status of the guard. Fixes bug 14334; bugfix
14330 o Minor bugfixes (hidden service client):
14331 - Increase the minimum number of internal circuits we preemptively
14332 build from 2 to 3, so a circuit is available when a client
14333 connects to another onion service. Fixes bug 13239; bugfix
14336 o Minor bugfixes (logging):
14337 - When logging a directory ownership mismatch, log the owning
14338 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
14340 o Minor bugfixes (memory leaks):
14341 - Fix a small, uncommon memory leak that could occur when reading a
14342 truncated ed25519 key file. Fixes bug 18956; bugfix
14345 o Minor bugfixes (testing):
14346 - Allow clients to retry HSDirs much faster in test networks. Fixes
14347 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
14348 - Disable ASAN's detection of segmentation faults while running
14349 test_bt.sh, so that we can make sure that our own backtrace
14350 generation code works. Fixes another aspect of bug 18934; bugfix
14351 on 0.2.5.2-alpha. Patch from "cypherpunks".
14352 - Fix the test-network-all target on out-of-tree builds by using the
14353 correct path to the test driver script. Fixes bug 19421; bugfix
14356 o Minor bugfixes (time):
14357 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
14358 bugfix on all released tor versions.
14359 - When computing the difference between two times in milliseconds,
14360 we now round to the nearest millisecond correctly. Previously, we
14361 could sometimes round in the wrong direction. Fixes bug 19428;
14362 bugfix on 0.2.2.2-alpha.
14364 o Minor bugfixes (user interface):
14365 - Display a more accurate number of suppressed messages in the log
14366 rate-limiter. Previously, there was a potential integer overflow
14367 in the counter. Now, if the number of messages hits a maximum, the
14368 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
14370 - Fix a typo in the passphrase prompt for the ed25519 identity key.
14371 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
14373 o Code simplification and refactoring:
14374 - Remove redundant declarations of the MIN macro. Closes
14376 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
14377 Closes ticket 18462; patch from "icanhasaccount".
14378 - Split the 600-line directory_handle_command_get function into
14379 separate functions for different URL types. Closes ticket 16698.
14382 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
14383 ticket 19153. Patch from "U+039b".
14385 o Removed features:
14386 - Remove support for "GET /tor/bytes.txt" DirPort request, and
14387 "GETINFO dir-usage" controller request, which were only available
14388 via a compile-time option in Tor anyway. Feature was added in
14389 0.2.2.1-alpha. Resolves ticket 19035.
14390 - There is no longer a compile-time option to disable support for
14391 TransPort. (If you don't want TransPort; just don't use it.) Patch
14392 from "U+039b". Closes ticket 19449.
14395 - Run more workqueue tests as part of "make check". These had
14396 previously been implemented, but you needed to know special
14397 command-line options to enable them.
14398 - We now have unit tests for our code to reject zlib "compression
14399 bombs". (Fortunately, the code works fine.)
14402 Changes in version 0.2.8.6 - 2016-08-02
14404 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
14406 The Tor 0.2.8 series improves client bootstrapping performance,
14407 completes the authority-side implementation of improved identity
14408 keys for relays, and includes numerous bugfixes and performance
14409 improvements throughout the program. This release continues to
14410 improve the coverage of Tor's test suite. For a full list of
14411 changes since Tor 0.2.7, see the ReleaseNotes file.
14413 Changes since 0.2.8.5-rc:
14415 o Minor features (geoip):
14416 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
14419 o Minor bugfixes (compilation):
14420 - Fix a compilation warning in the unit tests on systems where char
14421 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
14423 o Minor bugfixes (fallback directories):
14424 - Remove 1 fallback that was on the hardcoded list, then opted-out,
14425 leaving 89 of the 100 fallbacks originally introduced in Tor
14426 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
14428 o Minor bugfixes (Linux seccomp2 sandbox):
14429 - Allow more syscalls when running with "Sandbox 1" enabled:
14430 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
14431 some systems, these are required for Tor to start. Fixes bug
14432 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
14433 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
14434 so that get_interface_address6_via_udp_socket_hack() can work.
14435 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
14438 Changes in version 0.2.8.5-rc - 2016-07-07
14439 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
14440 series. If we find no new bugs or regressions here, the first stable
14441 0.2.8 release will be identical to it. It has a few small bugfixes
14442 against previous versions.
14444 o Directory authority changes:
14445 - Urras is no longer a directory authority. Closes ticket 19271.
14447 o Major bugfixes (heartbeat):
14448 - Fix a regression that would crash Tor when the periodic
14449 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
14450 0.2.8.1-alpha. Reported by "kubaku".
14452 o Minor features (build):
14453 - Tor now again builds with the recent OpenSSL 1.1 development
14454 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
14455 - When building manual pages, set the timezone to "UTC", so that the
14456 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
14457 Patch from intrigeri.
14459 o Minor bugfixes (fallback directory selection):
14460 - Avoid errors during fallback selection if there are no eligible
14461 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
14464 o Minor bugfixes (IPv6, microdescriptors):
14465 - Don't check node addresses when we only have a routerstatus. This
14466 allows IPv6-only clients to bootstrap by fetching microdescriptors
14467 from fallback directory mirrors. (The microdescriptor consensus
14468 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
14471 o Minor bugfixes (logging):
14472 - Reduce pointlessly verbose log messages when directory servers
14473 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
14474 0.2.8.1-alpha. Patch by teor.
14475 - When a fallback directory changes its fingerprint from the hard-
14476 coded fingerprint, log a less severe, more explanatory log
14477 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
14479 o Minor bugfixes (Linux seccomp2 sandboxing):
14480 - Allow statistics to be written to disk when "Sandbox 1" is
14481 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
14482 0.2.6.1-alpha respectively.
14484 o Minor bugfixes (user interface):
14485 - Remove a warning message "Service [scrubbed] not found after
14486 descriptor upload". This message appears when one uses HSPOST
14487 control command to upload a service descriptor. Since there is
14488 only a descriptor and no service, showing this message is
14489 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
14491 o Fallback directory list:
14492 - Add a comment to the generated fallback directory list that
14493 explains how to comment out unsuitable fallbacks in a way that's
14494 compatible with the stem fallback parser.
14495 - Update fallback whitelist and blacklist based on relay operator
14496 emails. Blacklist unsuitable (non-working, over-volatile)
14497 fallbacks. Resolves ticket 19071. Patch by teor.
14498 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
14499 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
14500 ticket 19071; patch by teor.
14503 Changes in version 0.2.8.4-rc - 2016-06-15
14504 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
14505 If we find no new bugs or regressions here, the first stable 0.2.8
14506 release will be identical to it. It has a few small bugfixes against
14509 o Major bugfixes (user interface):
14510 - Correctly give a warning in the cases where a relay is specified
14511 by nickname, and one such relay is found, but it is not officially
14512 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
14514 o Minor features (build):
14515 - Tor now builds once again with the recent OpenSSL 1.1 development
14516 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
14518 o Minor features (geoip):
14519 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
14522 o Minor bugfixes (compilation):
14523 - Cause the unit tests to compile correctly on mingw64 versions that
14524 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
14526 o Minor bugfixes (downloading):
14527 - Predict more correctly whether we'll be downloading over HTTP when
14528 we determine the maximum length of a URL. This should avoid a
14529 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
14533 Changes in version 0.2.8.3-alpha - 2016-05-26
14534 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
14535 the course of the 0.2.8 development cycle. It improves the behavior of
14536 directory clients, fixes several crash bugs, fixes a gap in compiler
14537 hardening, and allows the full integration test suite to run on
14540 o Major bugfixes (security, client, DNS proxy):
14541 - Stop a crash that could occur when a client running with DNSPort
14542 received a query with multiple address types, and the first
14543 address type was not supported. Found and fixed by Scott Dial.
14544 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14546 o Major bugfixes (security, compilation):
14547 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
14548 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
14549 cause a compiler warning, thereby making other checks fail, and
14550 needlessly disabling compiler-hardening support. Fixes one case of
14551 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
14553 o Major bugfixes (security, directory authorities):
14554 - Fix a crash and out-of-bounds write during authority voting, when
14555 the list of relays includes duplicate ed25519 identity keys. Fixes
14556 bug 19032; bugfix on 0.2.8.2-alpha.
14558 o Major bugfixes (client, bootstrapping):
14559 - Check if bootstrap consensus downloads are still needed when the
14560 linked connection attaches. This prevents tor making unnecessary
14561 begindir-style connections, which are the only directory
14562 connections tor clients make since the fix for 18483 was merged.
14563 - Fix some edge cases where consensus download connections may not
14564 have been closed, even though they were not needed. Related to fix
14566 - Make relays retry consensus downloads the correct number of times,
14567 rather than the more aggressive client retry count. Fixes part of
14569 - Stop downloading consensuses when we have a consensus, even if we
14570 don't have all the certificates for it yet. Fixes bug 18809;
14571 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
14573 o Major bugfixes (directory mirrors):
14574 - Decide whether to advertise begindir support in the the same way
14575 we decide whether to advertise our DirPort. Allowing these
14576 decisions to become out-of-sync led to surprising behavior like
14577 advertising begindir support when hibernation made us not
14578 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
14581 o Major bugfixes (IPv6 bridges, client):
14582 - Actually use IPv6 addresses when selecting directory addresses for
14583 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
14586 o Major bugfixes (key management):
14587 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14588 pointer to the previous (uninitialized) key value. The impact here
14589 should be limited to a difficult-to-trigger crash, if OpenSSL is
14590 running an engine that makes key generation failures possible, or
14591 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14592 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14595 o Major bugfixes (testing):
14596 - Fix a bug that would block 'make test-network-all' on systems where
14597 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
14598 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
14599 bugfix on 0.2.8.1-alpha.
14601 o Minor features (clients):
14602 - Make clients, onion services, and bridge relays always use an
14603 encrypted begindir connection for directory requests. Resolves
14604 ticket 18483. Patch by "teor".
14606 o Minor features (fallback directory mirrors):
14607 - Give each fallback the same weight for client selection; restrict
14608 fallbacks to one per operator; report fallback directory detail
14609 changes when rebuilding list; add new fallback directory mirrors
14610 to the whitelist; and many other minor simplifications and fixes.
14611 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
14612 0.2.8.1-alpha; patch by "teor".
14613 - Replace the 21 fallbacks generated in January 2016 and included in
14614 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
14615 2016. Closes task 17158; patch by "teor".
14617 o Minor features (geoip):
14618 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
14621 o Minor bugfixes (assert, portability):
14622 - Fix an assertion failure in memarea.c on systems where "long" is
14623 shorter than the size of a pointer. Fixes bug 18716; bugfix
14626 o Minor bugfixes (bootstrap):
14627 - Consistently use the consensus download schedule for authority
14628 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
14630 o Minor bugfixes (build):
14631 - Remove a pair of redundant AM_CONDITIONAL declarations from
14632 configure.ac. Fixes one final case of bug 17744; bugfix
14634 - Resolve warnings when building on systems that are concerned with
14635 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
14637 - When libscrypt.h is found, but no libscrypt library can be linked,
14638 treat libscrypt as absent. Fixes bug 19161; bugfix
14641 o Minor bugfixes (client):
14642 - Turn all TestingClientBootstrap* into non-testing torrc options.
14643 This changes simply renames them by removing "Testing" in front of
14644 them and they do not require TestingTorNetwork to be enabled
14645 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
14646 - Make directory node selection more reliable, mainly for IPv6-only
14647 clients and clients with few reachable addresses. Fixes bug 18929;
14648 bugfix on 0.2.8.1-alpha. Patch by "teor".
14650 o Minor bugfixes (controller, microdescriptors):
14651 - Make GETINFO dir/status-vote/current/consensus conform to the
14652 control specification by returning "551 Could not open cached
14653 consensus..." when not caching consensuses. Fixes bug 18920;
14654 bugfix on 0.2.2.6-alpha.
14656 o Minor bugfixes (crypto, portability):
14657 - The SHA3 and SHAKE routines now produce the correct output on Big
14658 Endian systems. No code calls either algorithm yet, so this is
14659 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
14660 - Tor now builds again with the recent OpenSSL 1.1 development
14661 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
14664 o Minor bugfixes (directories):
14665 - When fetching extrainfo documents, compare their SHA256 digests
14666 and Ed25519 signing key certificates with the routerinfo that led
14667 us to fetch them, rather than with the most recent routerinfo.
14668 Otherwise we generate many spurious warnings about mismatches.
14669 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
14671 o Minor bugfixes (logging):
14672 - When we can't generate a signing key because OfflineMasterKey is
14673 set, do not imply that we should have been able to load it. Fixes
14674 bug 18133; bugfix on 0.2.7.2-alpha.
14675 - Stop periodic_event_dispatch() from blasting twelve lines per
14676 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
14677 - When rejecting a misformed INTRODUCE2 cell, only log at
14678 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
14680 o Minor bugfixes (pluggable transports):
14681 - Avoid reporting a spurious error when we decide that we don't need
14682 to terminate a pluggable transport because it has already exited.
14683 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
14685 o Minor bugfixes (pointer arithmetic):
14686 - Fix a bug in memarea_alloc() that could have resulted in remote
14687 heap write access, if Tor had ever passed an unchecked size to
14688 memarea_alloc(). Fortunately, all the sizes we pass to
14689 memarea_alloc() are pre-checked to be less than 128 kilobytes.
14690 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
14693 o Minor bugfixes (relays):
14694 - Consider more config options when relays decide whether to
14695 regenerate their descriptor. Fixes more of bug 12538; bugfix
14697 - Resolve some edge cases where we might launch an ORPort
14698 reachability check even when DisableNetwork is set. Noticed while
14699 fixing bug 18616; bugfix on 0.2.3.9-alpha.
14701 o Minor bugfixes (statistics):
14702 - We now include consensus downloads via IPv6 in our directory-
14703 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
14705 o Minor bugfixes (testing):
14706 - Allow directories in small networks to bootstrap by skipping
14707 DirPort checks when the consensus has no exits. Fixes bug 19003;
14708 bugfix on 0.2.8.1-alpha. Patch by teor.
14709 - Fix a small memory leak that would occur when the
14710 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
14711 bugfix on 0.2.5.2-alpha.
14713 o Minor bugfixes (time handling):
14714 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
14715 field. Otherwise, our unit tests crash on Windows. Fixes bug
14716 18977; bugfix on 0.2.2.25-alpha.
14719 - Document the contents of the 'datadir/keys' subdirectory in the
14720 manual page. Closes ticket 17621.
14721 - Stop recommending use of nicknames to identify relays in our
14722 MapAddress documentation. Closes ticket 18312.
14725 Changes in version 0.2.8.2-alpha - 2016-03-28
14726 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
14727 bugs in earlier versions of Tor, including some that prevented
14728 authorities using Tor 0.2.7.x from running correctly. IPv6 and
14729 directory support should also be much improved.
14731 o New system requirements:
14732 - Tor no longer supports versions of OpenSSL with a broken
14733 implementation of counter mode. (This bug was present in OpenSSL
14734 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
14735 longer runs with, these versions.
14736 - Tor no longer attempts to support platforms where the "time_t"
14737 type is unsigned. (To the best of our knowledge, only OpenVMS does
14738 this, and Tor has never actually built on OpenVMS.) Closes
14740 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
14741 later (released in 2008 and 2009 respectively). If you are
14742 building Tor from the git repository instead of from the source
14743 distribution, and your tools are older than this, you will need to
14744 upgrade. Closes ticket 17732.
14746 o Major bugfixes (security, pointers):
14747 - Avoid a difficult-to-trigger heap corruption attack when extending
14748 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14749 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14750 Reported by Guido Vranken.
14752 o Major bugfixes (bridges, pluggable transports):
14753 - Modify the check for OR connections to private addresses. Allow
14754 bridges on private addresses, including pluggable transports that
14755 ignore the (potentially private) address in the bridge line. Fixes
14756 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
14758 o Major bugfixes (compilation):
14759 - Repair hardened builds under the clang compiler. Previously, our
14760 use of _FORTIFY_SOURCE would conflict with clang's address
14761 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
14763 o Major bugfixes (crash on shutdown):
14764 - Correctly handle detaching circuits from muxes when shutting down.
14765 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
14766 - Fix an assert-on-exit bug related to counting memory usage in
14767 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
14769 o Major bugfixes (crash on startup):
14770 - Fix a segfault during startup: If a Unix domain socket was
14771 configured as listener (such as a ControlSocket or a SocksPort
14772 "unix:" socket), and tor was started as root but not configured to
14773 switch to another user, tor would segfault while trying to string
14774 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
14777 o Major bugfixes (dns proxy mode, crash):
14778 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14779 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14781 o Major bugfixes (relays, bridge clients):
14782 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
14783 bridge clients use the address configured in the bridge line.
14784 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
14787 o Major bugfixes (voting):
14788 - Actually enable support for authorities to match routers by their
14789 Ed25519 identities. Previously, the code had been written, but
14790 some debugging code that had accidentally been left in the
14791 codebase made it stay turned off. Fixes bug 17702; bugfix
14793 - When collating votes by Ed25519 identities, authorities now
14794 include a "NoEdConsensus" flag if the ed25519 value (or lack
14795 thereof) for a server does not reflect the majority consensus.
14796 Related to bug 17668; bugfix on 0.2.7.2-alpha.
14797 - When generating a vote with keypinning disabled, never include two
14798 entries for the same ed25519 identity. This bug was causing
14799 authorities to generate votes that they could not parse when a
14800 router violated key pinning by changing its RSA identity but
14801 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
14802 18318. Bugfix on 0.2.7.2-alpha.
14804 o Minor features (security, win32):
14805 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
14806 attack. Fixes bug 18123; bugfix on all tor versions. Patch
14809 o Minor features (bug-resistance):
14810 - Make Tor survive errors involving connections without a
14811 corresponding event object. Previously we'd fail with an
14812 assertion; now we produce a log message. Related to bug 16248.
14814 o Minor features (build):
14815 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
14816 as having possible IPFW support. Closes ticket 18448. Patch from
14817 Steven Chamberlain.
14819 o Minor features (code hardening):
14820 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
14821 level code, to harden against accidental failures to NUL-
14822 terminate. Part of ticket 17852. Patch from jsturgix. Found
14825 o Minor features (crypto):
14826 - Validate the hard-coded Diffie-Hellman parameters and ensure that
14827 p is a safe prime, and g is a suitable generator. Closes
14830 o Minor features (geoip):
14831 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
14834 o Minor features (hidden service directory):
14835 - Streamline relay-side hsdir handling: when relays consider whether
14836 to accept an uploaded hidden service descriptor, they no longer
14837 check whether they are one of the relays in the network that is
14838 "supposed" to handle that descriptor. Implements ticket 18332.
14840 o Minor features (IPv6):
14841 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
14842 to 1, tor prefers IPv6 directory addresses.
14843 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
14844 avoids using IPv4 for client OR and directory connections.
14845 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
14846 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
14847 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
14849 o Minor features (linux seccomp2 sandbox):
14850 - Reject attempts to change our Address with "Sandbox 1" enabled.
14851 Changing Address with Sandbox turned on would never actually work,
14852 but previously it would fail in strange and confusing ways. Found
14853 while fixing 18548.
14855 o Minor features (robustness):
14856 - Exit immediately with an error message if the code attempts to use
14857 Libevent without having initialized it. This should resolve some
14858 frequently-made mistakes in our unit tests. Closes ticket 18241.
14860 o Minor features (unix domain sockets):
14861 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
14862 Unix domain sockets without checking the permissions on the parent
14863 directory. (Tor checks permissions by default because some
14864 operating systems only check permissions on the parent directory.
14865 However, some operating systems do look at permissions on the
14866 socket, and tor's default check is unneeded.) Closes ticket 18458.
14869 o Minor bugfixes (exit policies, security):
14870 - Refresh an exit relay's exit policy when interface addresses
14871 change. Previously, tor only refreshed the exit policy when the
14872 configured external address changed. Fixes bug 18208; bugfix on
14873 0.2.7.3-rc. Patch by teor.
14875 o Minor bugfixes (security, hidden services):
14876 - Prevent hidden services connecting to client-supplied rendezvous
14877 addresses that are reserved as internal or multicast. Fixes bug
14878 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
14880 o Minor bugfixes (build):
14881 - Do not link the unit tests against both the testing and non-
14882 testing versions of the static libraries. Fixes bug 18490; bugfix
14884 - Avoid spurious failures from configure files related to calling
14885 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
14886 0.2.0.1-alpha. Patch from "cypherpunks".
14887 - Silence spurious clang-scan warnings in the ed25519_donna code by
14888 explicitly initializing some objects. Fixes bug 18384; bugfix on
14889 0.2.7.2-alpha. Patch by teor.
14891 o Minor bugfixes (client, bootstrap):
14892 - Count receipt of new microdescriptors as progress towards
14893 bootstrapping. Previously, with EntryNodes set, Tor might not
14894 successfully repopulate the guard set on bootstrapping. Fixes bug
14895 16825; bugfix on 0.2.3.1-alpha.
14897 o Minor bugfixes (code correctness):
14898 - Update to the latest version of Trunnel, which tries harder to
14899 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
14900 by clang address sanitizer. Fixes bug 18373; bugfix
14903 o Minor bugfixes (configuration):
14904 - Fix a tiny memory leak when parsing a port configuration ending in
14905 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
14907 o Minor bugfixes (containers):
14908 - If we somehow attempt to construct a heap with more than
14909 1073741822 elements, avoid an integer overflow when maintaining
14910 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
14912 o Minor bugfixes (correctness):
14913 - Fix a bad memory handling bug that would occur if we had queued a
14914 cell on a channel's incoming queue. Fortunately, we can't actually
14915 queue a cell like that as our code is constructed today, but it's
14916 best to avoid this kind of error, even if there isn't any code
14917 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
14919 o Minor bugfixes (directory):
14920 - When generating a URL for a directory server on an IPv6 address,
14921 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
14922 on 0.2.3.9-alpha. Patch from Malek.
14924 o Minor bugfixes (fallback directory mirrors):
14925 - When requesting extrainfo descriptors from a trusted directory
14926 server, check whether it is an authority or a fallback directory
14927 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
14928 0.2.4.7-alpha. Reported by atagar, patch by teor.
14930 o Minor bugfixes (hidden service, client):
14931 - Handle the case where the user makes several fast consecutive
14932 requests to the same .onion address. Previously, the first six
14933 requests would each trigger a descriptor fetch, each picking a
14934 directory (there are 6 overall) and the seventh one would fail
14935 because no directories were left, thereby triggering a close on
14936 all current directory connections asking for the hidden service.
14937 The solution here is to not close the connections if we have
14938 pending directory fetches. Fixes bug 15937; bugfix
14941 o Minor bugfixes (hidden service, control port):
14942 - Add the onion address to the HS_DESC event for the UPLOADED action
14943 both on success or failure. It was previously hardcoded with
14944 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
14946 o Minor bugfixes (hidden service, directory):
14947 - Bridges now refuse "rendezvous2" (hidden service descriptor)
14948 publish attempts. Suggested by ticket 18332.
14950 o Minor bugfixes (linux seccomp2 sandbox):
14951 - Allow the setrlimit syscall, and the prlimit and prlimit64
14952 syscalls, which some libc implementations use under the hood.
14953 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
14954 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
14955 enabled and no DNS resolvers configured. This should help TAILS
14956 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
14957 - Fix the sandbox's interoperability with unix domain sockets under
14958 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
14960 o Minor bugfixes (logging):
14961 - When logging information about an unparsable networkstatus vote or
14962 consensus, do not say "vote" when we mean consensus. Fixes bug
14963 18368; bugfix on 0.2.0.8-alpha.
14964 - Scrub service name in "unrecognized service ID" log messages.
14965 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
14966 - Downgrade logs and backtraces about IP versions to info-level.
14967 Only log backtraces once each time tor runs. Assists in diagnosing
14968 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
14969 Christian, patch by teor.
14971 o Minor bugfixes (memory safety):
14972 - Avoid freeing an uninitialized pointer when opening a socket fails
14973 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
14974 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
14976 - Correctly duplicate addresses in get_interface_address6_list().
14977 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
14978 patch by "cypherpunks".
14979 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
14981 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
14982 18672; bugfix on 0.2.5.1-alpha.
14984 o Minor bugfixes (private directory):
14985 - Prevent a race condition when creating private directories. Fixes
14986 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
14987 Patch from jsturgix. Found with Flawfinder.
14989 o Minor bugfixes (test networks, IPv6):
14990 - Allow internal IPv6 addresses in descriptors in test networks.
14991 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
14994 o Minor bugfixes (testing):
14995 - We no longer disable assertions in the unit tests when coverage is
14996 enabled. Instead, we require you to say --disable-asserts-in-tests
14997 to the configure script if you need assertions disabled in the
14998 unit tests (for example, if you want to perform branch coverage).
14999 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
15001 o Minor bugfixes (time parsing):
15002 - Avoid overflow in tor_timegm when parsing dates in and after 2038
15003 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
15004 0.0.2pre14. Patch by teor.
15006 o Minor bugfixes (tor-gencert):
15007 - Correctly handle the case where an authority operator enters a
15008 passphrase but sends an EOF before sending a newline. Fixes bug
15009 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
15011 o Code simplification and refactoring:
15012 - Quote all the string interpolations in configure.ac -- even those
15013 which we are pretty sure can't contain spaces. Closes ticket
15014 17744. Patch from zerosion.
15015 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
15016 inplace, so there's no need to have a separate implementation for
15017 the non-inplace code. Closes ticket 18258. Patch from Malek.
15018 - Simplify return types for some crypto functions that can't
15019 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
15022 - Change build messages to refer to "Fedora" instead of "Fedora
15023 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
15024 Patches from "icanhasaccount" and "cypherpunks".
15026 o Removed features:
15027 - We no longer maintain an internal freelist in memarea.c.
15028 Allocators should be good enough to make this code unnecessary,
15029 and it's doubtful that it ever had any performance benefit.
15032 - Fix several warnings from clang's address sanitizer produced in
15034 - Treat backtrace test failures as expected on FreeBSD until we
15035 solve bug 17808. Closes ticket 18204.
15038 Changes in version 0.2.8.1-alpha - 2016-02-04
15039 Tor 0.2.8.1-alpha is the first alpha release in its series. It
15040 includes numerous small features and bugfixes against previous Tor
15041 versions, and numerous small infrastructure improvements. The most
15042 notable features are a set of improvements to the directory subsystem.
15044 o Major features (security, Linux):
15045 - When Tor starts as root on Linux and is told to switch user ID, it
15046 can now retain the capability to bind to low ports. By default,
15047 Tor will do this only when it's switching user ID and some low
15048 ports have been configured. You can change this behavior with the
15049 new option KeepBindCapabilities. Closes ticket 8195.
15051 o Major features (directory system):
15052 - When bootstrapping multiple consensus downloads at a time, use the
15053 first one that starts downloading, and close the rest. This
15054 reduces failures when authorities or fallback directories are slow
15055 or down. Together with the code for feature 15775, this feature
15056 should reduces failures due to fallback churn. Implements ticket
15057 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
15058 "mikeperry" and "teor".
15059 - Include a trial list of 21 default fallback directories, generated
15060 in January 2016, based on an opt-in survey of suitable relays.
15061 Doing this should make clients bootstrap more quickly and reliably,
15062 and reduce the load on the directory authorities. Closes ticket
15063 15775. Patch by "teor".
15064 Candidates identified using an OnionOO script by "weasel", "teor",
15065 "gsathya", and "karsten".
15066 - Previously only relays that explicitly opened a directory port
15067 (DirPort) accepted directory requests from clients. Now all
15068 relays, with and without a DirPort, accept and serve tunneled
15069 directory requests that they receive through their ORPort. You can
15070 disable this behavior using the new DirCache option. Closes
15073 o Major key updates:
15074 - Update the V3 identity key for the dannenberg directory authority:
15075 it was changed on 18 November 2015. Closes task 17906. Patch
15078 o Minor features (security, clock):
15079 - Warn when the system clock appears to move back in time (when the
15080 state file was last written in the future). Tor doesn't know that
15081 consensuses have expired if the clock is in the past. Patch by
15082 "teor". Implements ticket 17188.
15084 o Minor features (security, exit policies):
15085 - ExitPolicyRejectPrivate now rejects more private addresses by
15086 default. Specifically, it now rejects the relay's outbound bind
15087 addresses (if configured), and the relay's configured port
15088 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
15089 0.2.0.11-alpha. Patch by "teor".
15091 o Minor features (security, memory erasure):
15092 - Set the unused entries in a smartlist to NULL. This helped catch
15093 a (harmless) bug, and shouldn't affect performance too much.
15094 Implements ticket 17026.
15095 - Use SecureMemoryWipe() function to securely clean memory on
15096 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
15097 Implements feature 17986.
15098 - Use explicit_bzero or memset_s when present. Previously, we'd use
15099 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
15100 from <logan@hackers.mu> and <selven@hackers.mu>.
15101 - Make memwipe() do nothing when passed a NULL pointer or buffer of
15102 zero size. Check size argument to memwipe() for underflow. Fixes
15103 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
15106 o Minor features (security, RNG):
15107 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
15108 positively are not allowed to fail. Previously we depended on
15109 internal details of OpenSSL's behavior. Closes ticket 17686.
15110 - Never use the system entropy output directly for anything besides
15111 seeding the PRNG. When we want to generate important keys, instead
15112 of using system entropy directly, we now hash it with the PRNG
15113 stream. This may help resist certain attacks based on broken OS
15114 entropy implementations. Closes part of ticket 17694.
15115 - Use modern system calls (like getentropy() or getrandom()) to
15116 generate strong entropy on platforms that have them. Closes
15119 o Minor features (accounting):
15120 - Added two modes to the AccountingRule option: One for limiting
15121 only the number of bytes sent ("AccountingRule out"), and one for
15122 limiting only the number of bytes received ("AccountingRule in").
15123 Closes ticket 15989; patch from "unixninja92".
15125 o Minor features (build):
15126 - Since our build process now uses "make distcheck", we no longer
15127 force "make dist" to depend on "make check". Closes ticket 17893;
15128 patch from "cypherpunks."
15129 - Tor now builds successfully with the recent OpenSSL 1.1
15130 development branch, and with the latest LibreSSL. Closes tickets
15131 17549, 17921, and 17984.
15133 o Minor features (controller):
15134 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
15135 tickets 16774 and 17817. Patch by George Tankersley.
15136 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
15137 service descriptor from a service's local hidden service
15138 descriptor cache. Closes ticket 14846.
15139 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
15140 controllers can examine the the reject rules added by
15141 ExitPolicyRejectPrivate. This makes it easier for stem to display
15144 o Minor features (crypto):
15145 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
15147 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
15148 - When allocating a digest state object, allocate no more space than
15149 we actually need. Previously, we would allocate as much space as
15150 the state for the largest algorithm would need. This change saves
15151 up to 672 bytes per circuit. Closes ticket 17796.
15152 - Improve performance when hashing non-multiple of 8 sized buffers,
15153 based on Andrew Moon's public domain SipHash-2-4 implementation.
15154 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
15156 o Minor features (directory downloads):
15157 - Wait for busy authorities and fallback directories to become non-
15158 busy when bootstrapping. (A similar change was made in 6c443e987d
15159 for directory caches chosen from the consensus.) Closes ticket
15160 17864; patch by "teor".
15161 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
15162 directory mirrors. The default is 1; set it to 0 to disable
15163 fallbacks. Implements ticket 17576. Patch by "teor".
15165 o Minor features (geoip):
15166 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
15169 o Minor features (IPv6):
15170 - Add an argument 'ipv6=address:orport' to the DirAuthority and
15171 FallbackDir torrc options, to specify an IPv6 address for an
15172 authority or fallback directory. Add hard-coded ipv6 addresses for
15173 directory authorities that have them. Closes ticket 17327; patch
15174 from Nick Mathewson and "teor".
15175 - Add address policy assume_action support for IPv6 addresses.
15176 - Limit IPv6 mask bits to 128.
15177 - Warn when comparing against an AF_UNSPEC address in a policy, it's
15178 almost always a bug. Closes ticket 17863; patch by "teor".
15179 - Allow users to configure directory authorities and fallback
15180 directory servers with IPv6 addresses and ORPorts. Resolves
15182 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
15183 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
15184 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
15185 17638; bugfix on 0.0.2pre8. Patch by "teor".
15187 o Minor features (logging):
15188 - When logging to syslog, allow a tag to be added to the syslog
15189 identity (the string prepended to every log message). The tag can
15190 be configured with SyslogIdentityTag and defaults to none. Setting
15191 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
15194 o Minor features (portability):
15195 - Use timingsafe_memcmp() where available. Closes ticket 17944;
15196 patch from <logan@hackers.mu>.
15198 o Minor features (relay, address discovery):
15199 - Add a family argument to get_interface_addresses_raw() and
15200 subfunctions to make network interface address interogation more
15201 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
15202 types of interfaces from the operating system. Resolves
15204 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
15205 fails to enumerate interface addresses using the platform-specific
15206 API, have it rely on the UDP socket fallback technique to try and
15207 find out what IP addresses (both IPv4 and IPv6) our machine has.
15208 Resolves ticket 17951.
15210 o Minor features (replay cache):
15211 - The replay cache now uses SHA256 instead of SHA1. Implements
15212 feature 8961. Patch by "teor", issue reported by "rransom".
15214 o Minor features (unix file permissions):
15215 - Defer creation of Unix sockets until after setuid. This avoids
15216 needing CAP_CHOWN and CAP_FOWNER when using systemd's
15217 CapabilityBoundingSet, or chown and fowner when using SELinux.
15218 Implements part of ticket 17562. Patch from Jamie Nguyen.
15219 - If any directory created by Tor is marked as group readable, the
15220 filesystem group is allowed to be either the default GID or the
15221 root user. Allowing root to read the DataDirectory prevents the
15222 need for CAP_READ_SEARCH when using systemd's
15223 CapabilityBoundingSet, or dac_read_search when using SELinux.
15224 Implements part of ticket 17562. Patch from Jamie Nguyen.
15225 - Introduce a new DataDirectoryGroupReadable option. If it is set to
15226 1, the DataDirectory will be made readable by the default GID.
15227 Implements part of ticket 17562. Patch from Jamie Nguyen.
15229 o Minor bugfixes (accounting):
15230 - The max bandwidth when using 'AccountRule sum' is now correctly
15231 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
15232 from "unixninja92".
15234 o Minor bugfixes (code correctness):
15235 - When closing an entry connection, generate a warning if we should
15236 have sent an end cell for it but we haven't. Fixes bug 17876;
15237 bugfix on 0.2.3.2-alpha.
15238 - Assert that allocated memory held by the reputation code is freed
15239 according to its internal counters. Fixes bug 17753; bugfix
15241 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
15244 o Minor bugfixes (compilation):
15245 - Mark all object files that include micro-revision.i as depending
15246 on it, so as to make parallel builds more reliable. Fixes bug
15247 17826; bugfix on 0.2.5.1-alpha.
15248 - Don't try to use the pthread_condattr_setclock() function unless
15249 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
15250 17819; bugfix on 0.2.6.3-alpha.
15251 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
15253 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15254 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15255 - Fix search for libevent libraries on OpenBSD (and other systems
15256 that install libevent 1 and libevent 2 in parallel). Fixes bug
15257 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
15258 - Isolate environment variables meant for tests from the rest of the
15259 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
15260 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
15262 - Remove config.log only from make distclean, not from make clean.
15263 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
15265 o Minor bugfixes (crypto):
15266 - Check the return value of HMAC() and assert on failure. Fixes bug
15267 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
15269 o Minor bugfixes (fallback directories):
15270 - Mark fallbacks as "too busy" when they return a 503 response,
15271 rather than just marking authorities. Fixes bug 17572; bugfix on
15272 0.2.4.7-alpha. Patch by "teor".
15274 o Minor bugfixes (IPv6):
15275 - Update the limits in max_dl_per_request for IPv6 address length.
15276 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
15278 o Minor bugfixes (linux seccomp2 sandbox):
15279 - Fix a crash when using offline master ed25519 keys with the Linux
15280 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
15282 o Minor bugfixes (logging):
15283 - In log messages that include a function name, use __FUNCTION__
15284 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
15285 with clang __PRETTY_FUNCTION__ has extra information we don't
15286 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
15288 - Remove needless quotes from a log message about unparseable
15289 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
15291 o Minor bugfixes (portability):
15292 - Remove an #endif from configure.ac so that we correctly detect the
15293 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
15296 o Minor bugfixes (relays):
15297 - Check that both the ORPort and DirPort (if present) are reachable
15298 before publishing a relay descriptor. Otherwise, relays publish a
15299 descriptor with DirPort 0 when the DirPort reachability test takes
15300 longer than the ORPort reachability test. Fixes bug 18050; bugfix
15301 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
15303 o Minor bugfixes (relays, hidden services):
15304 - Refuse connection requests to private OR addresses unless
15305 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
15306 then refuse to send any cells to a private address. Fixes bugs
15307 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
15309 o Minor bugfixes (safe logging):
15310 - When logging a malformed hostname received through socks4, scrub
15311 it if SafeLogging says we should. Fixes bug 17419; bugfix
15314 o Minor bugfixes (statistics code):
15315 - Consistently check for overflow in round_*_to_next_multiple_of
15316 functions, and add unit tests with additional and maximal values.
15317 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
15318 - Handle edge cases in the laplace functions: avoid division by
15319 zero, avoid taking the log of zero, and silence clang type
15320 conversion warnings using round and trunc. Add unit tests for edge
15321 cases with maximal values. Fixes part of bug 13192; bugfix
15324 o Minor bugfixes (testing):
15325 - The test for log_heartbeat was incorrectly failing in timezones
15326 with non-integer offsets. Instead of comparing the end of the time
15327 string against a constant, compare it to the output of
15328 format_local_iso_time when given the correct input. Fixes bug
15329 18039; bugfix on 0.2.5.4-alpha.
15330 - Make unit tests pass on IPv6-only systems, and systems without
15331 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
15332 bugfix on 0.2.7.3-rc. Patch by "teor".
15333 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
15335 - Check the full results of SHA256 and SHA512 digests in the unit
15336 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
15338 o Code simplification and refactoring:
15339 - Move logging of redundant policy entries in
15340 policies_parse_exit_policy_internal into its own function. Closes
15341 ticket 17608; patch from "juce".
15342 - Extract the more complicated parts of circuit_mark_for_close()
15343 into a new function that we run periodically before circuits are
15344 freed. This change removes more than half of the functions
15345 currently in the "blob". Closes ticket 17218.
15346 - Clean up a little duplicated code in
15347 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
15349 - Decouple the list of streams waiting to be attached to circuits
15350 from the overall connection list. This change makes it possible to
15351 attach streams quickly while simplifying Tor's callgraph and
15352 avoiding O(N) scans of the entire connection list. Closes
15354 - When a direct directory request fails immediately on launch,
15355 instead of relaunching that request from inside the code that
15356 launches it, instead mark the connection for teardown. This change
15357 simplifies Tor's callback and prevents the directory-request
15358 launching code from invoking itself recursively. Closes
15360 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
15361 use them. Closes ticket 17926.
15364 - Add a description of the correct use of the '--keygen' command-
15365 line option. Closes ticket 17583; based on text by 's7r'.
15366 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
15367 - Explain actual minima for BandwidthRate. Closes ticket 16382.
15368 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
15369 - Mention torspec URL in the manpage and point the reader to it
15370 whenever we mention a document that belongs in torspce. Fixes
15373 o Removed features:
15374 - Remove client-side support for connecting to Tor relays running
15375 versions of Tor before 0.2.3.6-alpha. These relays didn't support
15376 the v3 TLS handshake protocol, and are no longer allowed on the
15377 Tor network. Implements the client side of ticket 11150. Based on
15378 patches by Tom van der Woerdt.
15381 - Add unit tests to check for common RNG failure modes, such as
15382 returning all zeroes, identical values, or incrementing values
15383 (OpenSSL's rand_predictable feature). Patch by "teor".
15384 - Log more information when the backtrace tests fail. Closes ticket
15385 17892. Patch from "cypherpunks."
15386 - Always test both ed25519 backends, so that we can be sure that our
15387 batch-open replacement code works. Part of ticket 16794.
15388 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
15389 portion of ticket 16831.
15390 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
15391 util_format.c, directory.c, and options_validate.c. Closes tickets
15392 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
15394 - Unit tests for directory_handle_command_get. Closes ticket 17004.
15395 Patch from Reinaldo de Souza Jr.
15398 Changes in version 0.2.7.6 - 2015-12-10
15399 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
15400 well as a minor bug in hidden service reliability.
15402 o Major bugfixes (guard selection):
15403 - Actually look at the Guard flag when selecting a new directory
15404 guard. When we implemented the directory guard design, we
15405 accidentally started treating all relays as if they have the Guard
15406 flag during guard selection, leading to weaker anonymity and worse
15407 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
15410 o Minor features (geoip):
15411 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
15414 o Minor bugfixes (compilation):
15415 - When checking for net/pfvar.h, include netinet/in.h if possible.
15416 This fixes transparent proxy detection on OpenBSD. Fixes bug
15417 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
15418 - Fix a compilation warning with Clang 3.6: Do not check the
15419 presence of an address which can never be NULL. Fixes bug 17781.
15421 o Minor bugfixes (correctness):
15422 - When displaying an IPv6 exit policy, include the mask bits
15423 correctly even when the number is greater than 31. Fixes bug
15424 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
15425 - The wrong list was used when looking up expired intro points in a
15426 rend service object, causing what we think could be reachability
15427 issues for hidden services, and triggering a BUG log. Fixes bug
15428 16702; bugfix on 0.2.7.2-alpha.
15429 - Fix undefined behavior in the tor_cert_checksig function. Fixes
15430 bug 17722; bugfix on 0.2.7.2-alpha.
15433 Changes in version 0.2.7.5 - 2015-11-20
15434 The Tor 0.2.7 release series is dedicated to the memory of Tor user
15435 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
15436 tirelessly to advocate human rights regardless of national borders,
15437 and oppose the encroachments of mass surveillance. He opposed national
15438 exceptionalism, he brought clarity to legal and policy debates, he
15439 understood and predicted the impact of mass surveillance on the world,
15440 and he laid the groundwork for resisting it. While serving on the Tor
15441 Project's board of directors, he brought us his uncompromising focus
15442 on technical excellence in the service of humankind. Caspar was an
15443 inimitable force for good and a wonderful friend. He was kind,
15444 humorous, generous, gallant, and believed we should protect one
15445 another without exception. We honor him here for his ideals, his
15446 efforts, and his accomplishments. Please honor his memory with works
15447 that would make him proud.
15449 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
15451 The 0.2.7 series adds a more secure identity key type for relays,
15452 improves cryptography performance, resolves several longstanding
15453 hidden-service performance issues, improves controller support for
15454 hidden services, and includes small bugfixes and performance
15455 improvements throughout the program. This release series also includes
15456 more tests than before, and significant simplifications to which parts
15457 of Tor invoke which others.
15459 (This release contains no code changes since 0.2.7.4-rc.)
15462 Changes in version 0.2.7.4-rc - 2015-10-21
15463 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
15464 fixes some important memory leaks, and a scary-looking (but mostly
15465 harmless in practice) invalid-read bug. It also has a few small
15466 bugfixes, notably fixes for compilation and portability on different
15467 platforms. If no further significant bounds are found, the next
15468 release will the the official stable release.
15470 o Major bugfixes (security, correctness):
15471 - Fix an error that could cause us to read 4 bytes before the
15472 beginning of an openssl string. This bug could be used to cause
15473 Tor to crash on systems with unusual malloc implementations, or
15474 systems with unusual hardening installed. Fixes bug 17404; bugfix
15477 o Major bugfixes (correctness):
15478 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
15479 bug 17401; bugfix on 0.2.7.3-rc.
15481 o Major bugfixes (memory leaks):
15482 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
15483 17398; bugfix on 0.2.6.1-alpha.
15484 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
15485 17402; bugfix on 0.2.7.3-rc.
15486 - Fix a memory leak when reading an expired signing key from disk.
15487 Fixes bug 17403; bugfix on 0.2.7.2-rc.
15489 o Minor features (geoIP):
15490 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
15493 o Minor bugfixes (compilation):
15494 - Repair compilation with the most recent (unreleased, alpha)
15495 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
15496 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
15497 17251; bugfix on 0.2.7.2-alpha.
15498 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15499 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15501 o Minor bugfixes (portability):
15502 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
15503 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
15506 o Minor bugfixes (sandbox):
15507 - Add the "hidserv-stats" filename to our sandbox filter for the
15508 HiddenServiceStatistics option to work properly. Fixes bug 17354;
15509 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
15511 o Minor bugfixes (testing):
15512 - Add unit tests for get_interface_address* failure cases. Fixes bug
15513 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
15514 - Fix breakage when running 'make check' with BSD make. Fixes bug
15515 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
15516 - Make the get_ifaddrs_* unit tests more tolerant of different
15517 network configurations. (Don't assume every test box has an IPv4
15518 address, and don't assume every test box has a non-localhost
15519 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
15520 - Skip backtrace tests when backtrace support is not compiled in.
15521 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
15525 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
15526 - Note that HiddenServicePorts can take a unix domain socket. Closes
15530 Changes in version 0.2.7.3-rc - 2015-09-25
15531 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
15532 contains numerous usability fixes for Ed25519 keys, safeguards against
15533 several misconfiguration problems, significant simplifications to
15534 Tor's callgraph, and numerous bugfixes and small features.
15536 This is the most tested release of Tor to date. The unit tests cover
15537 39.40% of the code, and the integration tests (accessible with "make
15538 test-full-online", requiring stem and chutney and a network
15539 connection) raise the coverage to 64.49%.
15541 o Major features (security, hidden services):
15542 - Hidden services, if using the EntryNodes option, are required to
15543 use more than one EntryNode, in order to avoid a guard discovery
15544 attack. (This would only affect people who had configured hidden
15545 services and manually specified the EntryNodes option with a
15546 single entry-node. The impact was that it would be easy to
15547 remotely identify the guard node used by such a hidden service.
15548 See ticket for more information.) Fixes ticket 14917.
15550 o Major features (Ed25519 keys, keypinning):
15551 - The key-pinning option on directory authorities is now advisory-
15552 only by default. In a future version, or when the AuthDirPinKeys
15553 option is set, pins are enforced again. Disabling key-pinning
15554 seemed like a good idea so that we can survive the fallout of any
15555 usability problems associated with Ed25519 keys. Closes
15558 o Major features (Ed25519 performance):
15559 - Improve the speed of Ed25519 operations and Curve25519 keypair
15560 generation when built targeting 32 bit x86 platforms with SSE2
15561 available. Implements ticket 16535.
15562 - Improve the runtime speed of Ed25519 signature verification by
15563 using Ed25519-donna's batch verification support. Implements
15566 o Major features (performance testing):
15567 - The test-network.sh script now supports performance testing.
15568 Requires corresponding chutney performance testing changes. Patch
15569 by "teor". Closes ticket 14175.
15571 o Major features (relay, Ed25519):
15572 - Significant usability improvements for Ed25519 key management. Log
15573 messages are better, and the code can recover from far more
15574 failure conditions. Thanks to "s7r" for reporting and diagnosing
15576 - Add a new OfflineMasterKey option to tell Tor never to try loading
15577 or generating a secret Ed25519 identity key. You can use this in
15578 combination with tor --keygen to manage offline and/or encrypted
15579 Ed25519 keys. Implements ticket 16944.
15580 - Add a --newpass option to allow changing or removing the
15581 passphrase of an encrypted key with tor --keygen. Implements part
15583 - On receiving a HUP signal, check to see whether the Ed25519
15584 signing key has changed, and reload it if so. Closes ticket 16790.
15586 o Major bugfixes (relay, Ed25519):
15587 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
15588 0.2.7.2-alpha. Reported by "s7r".
15589 - Improve handling of expired signing keys with offline master keys.
15590 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
15592 o Minor features (client-side privacy):
15593 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
15594 lifespan when IsolateSOCKSAuth and streams with SOCKS
15595 authentication are attached to the circuit. This allows
15596 applications like TorBrowser to manage circuit lifetime on their
15597 own. Implements feature 15482.
15598 - When logging malformed hostnames from SOCKS5 requests, respect
15599 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
15601 o Minor features (compilation):
15602 - Give a warning as early as possible when trying to build with an
15603 unsupported OpenSSL version. Closes ticket 16901.
15604 - Fail during configure if we're trying to build against an OpenSSL
15605 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
15606 which started requiring ECC.
15608 o Minor features (geoip):
15609 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
15612 o Minor features (hidden services):
15613 - Relays need to have the Fast flag to get the HSDir flag. As this
15614 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
15615 drop. This change should make some attacks against the hidden
15616 service directory system harder. Fixes ticket 15963.
15617 - Turn on hidden service statistics collection by setting the torrc
15618 option HiddenServiceStatistics to "1" by default. (This keeps
15619 track only of the fraction of traffic used by hidden services, and
15620 the total number of hidden services in existence.) Closes
15622 - Client now uses an introduction point failure cache to know when
15623 to fetch or keep a descriptor in their cache. Previously, failures
15624 were recorded implicitly, but not explicitly remembered. Closes
15627 o Minor features (testing, authorities, documentation):
15628 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
15629 explicitly manage consensus flags in testing networks. Patch by
15630 "robgjansen", modified by "teor". Implements part of ticket 14882.
15632 o Minor bugfixes (security, exit policies):
15633 - ExitPolicyRejectPrivate now also rejects the relay's published
15634 IPv6 address (if any), and any publicly routable IPv4 or IPv6
15635 addresses on any local interfaces. ticket 17027. Patch by "teor".
15636 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
15638 o Minor bug fixes (torrc exit policies):
15639 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
15640 produce IPv6 wildcard addresses. Previously they would produce
15641 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
15642 of bug 16069; bugfix on 0.2.4.7-alpha.
15643 - When parsing torrc ExitPolicies, we now warn for a number of cases
15644 where the user's intent is likely to differ from Tor's actual
15645 behavior. These include: using an IPv4 address with an accept6 or
15646 reject6 line; using "private" on an accept6 or reject6 line; and
15647 including any ExitPolicy lines after accept *:* or reject *:*.
15648 Related to ticket 16069.
15649 - When parsing torrc ExitPolicies, we now issue an info-level
15650 message when expanding an "accept/reject *" line to include both
15651 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
15652 - In each instance above, usage advice is provided to avoid the
15653 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
15654 16069; bugfix on 0.2.4.7-alpha.
15656 o Minor bugfixes (authority):
15657 - Don't assign "HSDir" to a router if it isn't Valid and Running.
15658 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
15659 - Downgrade log messages about Ed25519 key issues if they are in old
15660 cached router descriptors. Fixes part of bug 16286; bugfix
15662 - When we find an Ed25519 key issue in a cached descriptor, stop
15663 saying the descriptor was just "uploaded". Fixes another part of
15664 bug 16286; bugfix on 0.2.7.2-alpha.
15666 o Minor bugfixes (control port):
15667 - Repair a warning and a spurious result when getting the maximum
15668 number of file descriptors from the controller. Fixes bug 16697;
15669 bugfix on 0.2.7.2-alpha.
15671 o Minor bugfixes (correctness):
15672 - When calling channel_free_list(), avoid calling smartlist_remove()
15673 while inside a FOREACH loop. This partially reverts commit
15674 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
15675 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
15677 o Minor bugfixes (documentation):
15678 - Advise users on how to configure separate IPv4 and IPv6 exit
15679 policies in the manpage and sample torrcs. Related to ticket 16069.
15680 - Fix the usage message of tor-resolve(1) so that it no longer lists
15681 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
15682 - Fix an error in the manual page and comments for
15683 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
15684 required "ORPort connectivity". While this is true, it is in no
15685 way unique to the HSDir flag. Of all the flags, only HSDirs need a
15686 DirPort configured in order for the authorities to assign that
15687 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
15690 o Minor bugfixes (Ed25519):
15691 - Fix a memory leak when reading router descriptors with expired
15692 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
15694 o Minor bugfixes (linux seccomp2 sandbox):
15695 - Allow bridge authorities to run correctly under the seccomp2
15696 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
15697 - Allow routers with ed25519 keys to run correctly under the
15698 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
15700 o Minor bugfixes (open file limit):
15701 - Fix set_max_file_descriptors() to set by default the max open file
15702 limit to the current limit when setrlimit() fails. Fixes bug
15703 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
15705 o Minor bugfixes (portability):
15706 - Try harder to normalize the exit status of the Tor process to the
15707 standard-provided range. Fixes bug 16975; bugfix on every version
15709 - Check correctly for Windows socket errors in the workqueue
15710 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
15711 - Fix the behavior of crypto_rand_time_range() when told to consider
15712 times before 1970. (These times were possible when running in a
15713 simulated network environment where time()'s output starts at
15714 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
15715 - Restore correct operation of TLS client-cipher detection on
15716 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
15718 o Minor bugfixes (relay):
15719 - Ensure that worker threads actually exit when a fatal error or
15720 shutdown is indicated. This fix doesn't currently affect the
15721 behavior of Tor, because Tor workers never indicates fatal error
15722 or shutdown except in the unit tests. Fixes bug 16868; bugfix
15724 - Unblock threads before releasing the work queue mutex to ensure
15725 predictable scheduling behavior. Fixes bug 16644; bugfix
15728 o Code simplification and refactoring:
15729 - Change the function that's called when we need to retry all
15730 downloads so that it only reschedules the downloads to happen
15731 immediately, rather than launching them all at once itself. This
15732 further simplifies Tor's callgraph.
15733 - Move some format-parsing functions out of crypto.c and
15734 crypto_curve25519.c into crypto_format.c and/or util_format.c.
15735 - Move the client-only parts of init_keys() into a separate
15736 function. Closes ticket 16763.
15737 - Simplify the microdesc_free() implementation so that it no longer
15738 appears (to code analysis tools) to potentially invoke a huge
15739 suite of other microdesc functions.
15740 - Simply the control graph further by deferring the inner body of
15741 directory_all_unreachable() into a callback. Closes ticket 16762.
15742 - Treat the loss of an owning controller as equivalent to a SIGTERM
15743 signal. This removes a tiny amount of duplicated code, and
15744 simplifies our callgraph. Closes ticket 16788.
15745 - When generating an event to send to the controller, we no longer
15746 put the event over the network immediately. Instead, we queue
15747 these events, and use a Libevent callback to deliver them. This
15748 change simplifies Tor's callgraph by reducing the number of
15749 functions from which all other Tor functions are reachable. Closes
15751 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
15752 that try to scan or compile every file on Unix won't decide that
15754 - Remove the unused "nulterminate" argument from buf_pullup().
15757 - Recommend a 40 GB example AccountingMax in torrc.sample rather
15758 than a 4 GB max. Closes ticket 16742.
15759 - Include the TUNING document in our source tarball. It is referred
15760 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
15764 - The internal pure-C tor-fw-helper tool is now removed from the Tor
15765 distribution, in favor of the pure-Go clone available from
15766 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
15767 used by the C tor-fw-helper are not, in our opinion, very
15768 confidence- inspiring in their secure-programming techniques.
15769 Closes ticket 13338.
15770 - Remove the code that would try to aggressively flush controller
15771 connections while writing to them. This code was introduced in
15772 0.1.2.7-alpha, in order to keep output buffers from exceeding
15773 their limits. But there is no longer a maximum output buffer size,
15774 and flushing data in this way caused some undesirable recursions
15775 in our call graph. Closes ticket 16480.
15778 - Make "bridges+hs" the default test network. This tests almost all
15779 tor functionality during make test-network, while allowing tests
15780 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
15781 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
15782 (chutney). Patches by "teor".
15783 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
15784 by-side in the same parent directory. Closes ticket 16903. Patch
15786 - Use environment variables rather than autoconf substitutions to
15787 send variables from the build system to the test scripts. This
15788 change should be easier to maintain, and cause 'make distcheck' to
15789 work better than before. Fixes bug 17148.
15790 - Add a new set of callgraph analysis scripts that use clang to
15791 produce a list of which Tor functions are reachable from which
15792 other Tor functions. We're planning to use these to help simplify
15793 our code structure by identifying illogical dependencies.
15794 - Add new 'test-full' and 'test-full-online' targets to run all
15795 tests, including integration tests with stem and chutney.
15796 - Make the test-workqueue test work on Windows by initializing the
15797 network before we begin.
15798 - New make target (make test-network-all) to run multiple applicable
15799 chutney test cases. Patch from Teor; closes 16953.
15800 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
15801 functions in dns.c. Implements a portion of ticket 16831.
15802 - When building Tor with testing coverage enabled, run Chutney tests
15803 (if any) using the 'tor-cov' coverage binary.
15804 - When running test-network or test-stem, check for the absence of
15805 stem/chutney before doing any build operations.
15808 Changes in version 0.2.7.2-alpha - 2015-07-27
15809 This, the second alpha in the Tor 0.2.7 series, has a number of new
15810 features, including a way to manually pick the number of introduction
15811 points for hidden services, and the much stronger Ed25519 signing key
15812 algorithm for regular Tor relays (including support for encrypted
15813 offline identity keys in the new algorithm).
15815 Support for Ed25519 on relays is currently limited to signing router
15816 descriptors; later alphas in this series will extend Ed25519 key
15817 support to more parts of the Tor protocol.
15819 o Major features (Ed25519 identity keys, Proposal 220):
15820 - All relays now maintain a stronger identity key, using the Ed25519
15821 elliptic curve signature format. This master key is designed so
15822 that it can be kept offline. Relays also generate an online
15823 signing key, and a set of other Ed25519 keys and certificates.
15824 These are all automatically regenerated and rotated as needed.
15825 Implements part of ticket 12498.
15826 - Directory authorities now vote on Ed25519 identity keys along with
15827 RSA1024 keys. Implements part of ticket 12498.
15828 - Directory authorities track which Ed25519 identity keys have been
15829 used with which RSA1024 identity keys, and do not allow them to
15830 vary freely. Implements part of ticket 12498.
15831 - Microdescriptors now include Ed25519 identity keys. Implements
15832 part of ticket 12498.
15833 - Add support for offline encrypted Ed25519 master keys. To use this
15834 feature on your tor relay, run "tor --keygen" to make a new master
15835 key (or to make a new signing key if you already have a master
15836 key). Closes ticket 13642.
15838 o Major features (Hidden services):
15839 - Add the torrc option HiddenServiceNumIntroductionPoints, to
15840 specify a fixed number of introduction points. Its maximum value
15841 is 10 and default is 3. Using this option can increase a hidden
15842 service's reliability under load, at the cost of making it more
15843 visible that the hidden service is facing extra load. Closes
15845 - Remove the adaptive algorithm for choosing the number of
15846 introduction points, which used to change the number of
15847 introduction points (poorly) depending on the number of
15848 connections the HS sees. Closes ticket 4862.
15850 o Major features (onion key cross-certification):
15851 - Relay descriptors now include signatures of their own identity
15852 keys, made using the TAP and ntor onion keys. These signatures
15853 allow relays to prove ownership of their own onion keys. Because
15854 of this change, microdescriptors will no longer need to include
15855 RSA identity keys. Implements proposal 228; closes ticket 12499.
15857 o Major features (performance):
15858 - Improve the runtime speed of Ed25519 operations by using the
15859 public-domain Ed25519-donna by Andrew M. ("floodyberry").
15860 Implements ticket 16467.
15861 - Improve the runtime speed of the ntor handshake by using an
15862 optimized curve25519 basepoint scalarmult implementation from the
15863 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
15864 ideas by Adam Langley. Implements ticket 9663.
15866 o Major bugfixes (client-side privacy, also in 0.2.6.9):
15867 - Properly separate out each SOCKSPort when applying stream
15868 isolation. The error occurred because each port's session group
15869 was being overwritten by a default value when the listener
15870 connection was initialized. Fixes bug 16247; bugfix on
15871 0.2.6.3-alpha. Patch by "jojelino".
15873 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
15874 - Stop refusing to store updated hidden service descriptors on a
15875 client. This reverts commit 9407040c59218 (which indeed fixed bug
15876 14219, but introduced a major hidden service reachability
15877 regression detailed in bug 16381). This is a temporary fix since
15878 we can live with the minor issue in bug 14219 (it just results in
15879 some load on the network) but the regression of 16381 is too much
15880 of a setback. First-round fix for bug 16381; bugfix
15883 o Major bugfixes (hidden services):
15884 - When cannibalizing a circuit for an introduction point, always
15885 extend to the chosen exit node (creating a 4 hop circuit).
15886 Previously Tor would use the current circuit exit node, which
15887 changed the original choice of introduction point, and could cause
15888 the hidden service to skip excluded introduction points or
15889 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
15892 o Major bugfixes (open file limit):
15893 - The open file limit wasn't checked before calling
15894 tor_accept_socket_nonblocking(), which would make Tor exceed the
15895 limit. Now, before opening a new socket, Tor validates the open
15896 file limit just before, and if the max has been reached, return an
15897 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
15899 o Major bugfixes (stability, also in 0.2.6.10):
15900 - Stop crashing with an assertion failure when parsing certain kinds
15901 of malformed or truncated microdescriptors. Fixes bug 16400;
15902 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
15903 by "cypherpunks_backup".
15904 - Stop random client-side assertion failures that could occur when
15905 connecting to a busy hidden service, or connecting to a hidden
15906 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
15909 o Minor features (directory authorities, security, also in 0.2.6.9):
15910 - The HSDir flag given by authorities now requires the Stable flag.
15911 For the current network, this results in going from 2887 to 2806
15912 HSDirs. Also, it makes it harder for an attacker to launch a sybil
15913 attack by raising the effort for a relay to become Stable to
15914 require at the very least 7 days, while maintaining the 96 hours
15915 uptime requirement for HSDir. Implements ticket 8243.
15917 o Minor features (client):
15918 - Relax the validation of hostnames in SOCKS5 requests, allowing the
15919 character '_' to appear, in order to cope with domains observed in
15920 the wild that are serving non-RFC compliant records. Resolves
15922 - Relax the validation done to hostnames in SOCKS5 requests, and
15923 allow a single trailing '.' to cope with clients that pass FQDNs
15924 using that syntax to explicitly indicate that the domain name is
15925 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
15926 - Add GroupWritable and WorldWritable options to unix-socket based
15927 SocksPort and ControlPort options. These options apply to a single
15928 socket, and override {Control,Socks}SocketsGroupWritable. Closes
15931 o Minor features (control protocol):
15932 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
15933 the control protocol. Resolves ticket 15358.
15935 o Minor features (directory authorities):
15936 - Directory authorities no longer vote against the "Fast", "Stable",
15937 and "HSDir" flags just because they were going to vote against
15938 "Running": if the consensus turns out to be that the router was
15939 running, then the authority's vote should count. Patch from Peter
15940 Retzlaff; closes issue 8712.
15942 o Minor features (geoip, also in 0.2.6.10):
15943 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
15944 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
15946 o Minor features (hidden services):
15947 - Add the new options "HiddenServiceMaxStreams" and
15948 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
15949 limit the maximum number of simultaneous streams per circuit, and
15950 optionally tear down the circuit when the limit is exceeded. Part
15953 o Minor features (portability):
15954 - Use C99 variadic macros when the compiler is not GCC. This avoids
15955 failing compilations on MSVC, and fixes a log-file-based race
15956 condition in our old workarounds. Original patch from Gisle Vanem.
15958 o Minor bugfixes (compilation, also in 0.2.6.9):
15959 - Build with --enable-systemd correctly when libsystemd is
15960 installed, but systemd is not. Fixes bug 16164; bugfix on
15961 0.2.6.3-alpha. Patch from Peter Palfrader.
15963 o Minor bugfixes (controller):
15964 - Add the descriptor ID in each HS_DESC control event. It was
15965 missing, but specified in control-spec.txt. Fixes bug 15881;
15966 bugfix on 0.2.5.2-alpha.
15968 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
15969 - Check for failures from crypto_early_init, and refuse to continue.
15970 A previous typo meant that we could keep going with an
15971 uninitialized crypto library, and would have OpenSSL initialize
15972 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15973 when implementing ticket 4900. Patch by "teor".
15975 o Minor bugfixes (hidden services):
15976 - Fix a crash when reloading configuration while at least one
15977 configured and one ephemeral hidden service exists. Fixes bug
15978 16060; bugfix on 0.2.7.1-alpha.
15979 - Avoid crashing with a double-free bug when we create an ephemeral
15980 hidden service but adding it fails for some reason. Fixes bug
15981 16228; bugfix on 0.2.7.1-alpha.
15983 o Minor bugfixes (Linux seccomp2 sandbox):
15984 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
15985 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
15987 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
15988 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15989 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15990 on 0.2.6.3-alpha. Patch from "teor".
15992 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
15993 - Fix sandboxing to work when running as a relay, by allowing the
15994 renaming of secret_id_key, and allowing the eventfd2 and futex
15995 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
15997 - Allow systemd connections to work with the Linux seccomp2 sandbox
15998 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16001 o Minor bugfixes (relay):
16002 - Fix a rarely-encountered memory leak when failing to initialize
16003 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
16004 from "cypherpunks".
16006 o Minor bugfixes (systemd):
16007 - Fix an accidental formatting error that broke the systemd
16008 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
16009 - Tor's systemd unit file no longer contains extraneous spaces.
16010 These spaces would sometimes confuse tools like deb-systemd-
16011 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
16013 o Minor bugfixes (tests):
16014 - Use the configured Python executable when running test-stem-full.
16015 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
16017 o Minor bugfixes (tests, also in 0.2.6.9):
16018 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16019 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16021 o Minor bugfixes (threads, comments):
16022 - Always initialize return value in compute_desc_id in rendcommon.c
16023 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16024 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
16025 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16026 - Remove undefined directive-in-macro in test_util_writepid clang
16027 3.7 complains that using a preprocessor directive inside a macro
16028 invocation in test_util_writepid in test_util.c is undefined.
16029 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16031 o Code simplification and refactoring:
16032 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
16033 to ensure they remain consistent and visible everywhere.
16034 - Remove some vestigial workarounds for the MSVC6 compiler. We
16035 haven't supported that in ages.
16036 - The link authentication code has been refactored for better
16037 testability and reliability. It now uses code generated with the
16038 "trunnel" binary encoding generator, to reduce the risk of bugs
16039 due to programmer error. Done as part of ticket 12498.
16042 - Include a specific and (hopefully) accurate documentation of the
16043 torrc file's meta-format in doc/torrc_format.txt. This is mainly
16044 of interest to people writing programs to parse or generate torrc
16045 files. This document is not a commitment to long-term
16046 compatibility; some aspects of the current format are a bit
16047 ridiculous. Closes ticket 2325.
16049 o Removed features:
16050 - Tor no longer supports copies of OpenSSL that are missing support
16051 for Elliptic Curve Cryptography. (We began using ECC when
16052 available in 0.2.4.8-alpha, for more safe and efficient key
16053 negotiation.) In particular, support for at least one of P256 or
16054 P224 is now required, with manual configuration needed if only
16055 P224 is available. Resolves ticket 16140.
16056 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
16057 on an operating system that has not upgraded to OpenSSL 1.0 or
16058 later, and you compile Tor from source, you will need to install a
16059 more recent OpenSSL to link Tor against.) These versions of
16060 OpenSSL are still supported by the OpenSSL, but the numerous
16061 cryptographic improvements in later OpenSSL releases makes them a
16062 clear choice. Resolves ticket 16034.
16063 - Remove the HidServDirectoryV2 option. Now all relays offer to
16064 store hidden service descriptors. Related to 16543.
16065 - Remove the VoteOnHidServDirectoriesV2 option, since all
16066 authorities have long set it to 1. Closes ticket 16543.
16069 - Document use of coverity, clang static analyzer, and clang dynamic
16070 undefined behavior and address sanitizers in doc/HACKING. Include
16071 detailed usage instructions in the blacklist. Patch by "teor".
16072 Closes ticket 15817.
16073 - The link authentication protocol code now has extensive tests.
16074 - The relay descriptor signature testing code now has
16076 - The test_workqueue program now runs faster, and is enabled by
16077 default as a part of "make check".
16078 - Now that OpenSSL has its own scrypt implementation, add an unit
16079 test that checks for interoperability between libscrypt_scrypt()
16080 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
16081 and rely on EVP_PBE_scrypt() whenever possible. Resolves
16085 Changes in version 0.2.6.10 - 2015-07-12
16086 Tor version 0.2.6.10 fixes some significant stability and hidden
16087 service client bugs, bulletproofs the cryptography init process, and
16088 fixes a bug when using the sandbox code with some older versions of
16089 Linux. Everyone running an older version, especially an older version
16090 of 0.2.6, should upgrade.
16092 o Major bugfixes (hidden service clients, stability):
16093 - Stop refusing to store updated hidden service descriptors on a
16094 client. This reverts commit 9407040c59218 (which indeed fixed bug
16095 14219, but introduced a major hidden service reachability
16096 regression detailed in bug 16381). This is a temporary fix since
16097 we can live with the minor issue in bug 14219 (it just results in
16098 some load on the network) but the regression of 16381 is too much
16099 of a setback. First-round fix for bug 16381; bugfix
16102 o Major bugfixes (stability):
16103 - Stop crashing with an assertion failure when parsing certain kinds
16104 of malformed or truncated microdescriptors. Fixes bug 16400;
16105 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16106 by "cypherpunks_backup".
16107 - Stop random client-side assertion failures that could occur when
16108 connecting to a busy hidden service, or connecting to a hidden
16109 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16112 o Minor features (geoip):
16113 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16114 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16116 o Minor bugfixes (crypto error-handling):
16117 - Check for failures from crypto_early_init, and refuse to continue.
16118 A previous typo meant that we could keep going with an
16119 uninitialized crypto library, and would have OpenSSL initialize
16120 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16121 when implementing ticket 4900. Patch by "teor".
16123 o Minor bugfixes (Linux seccomp2 sandbox):
16124 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16125 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16126 on 0.2.6.3-alpha. Patch from "teor".
16129 Changes in version 0.2.6.9 - 2015-06-11
16130 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
16131 requirements for receiving an HSDir flag, and addresses some other small
16132 bugs in the systemd and sandbox code. Clients using circuit isolation
16133 should upgrade; all directory authorities should upgrade.
16135 o Major bugfixes (client-side privacy):
16136 - Properly separate out each SOCKSPort when applying stream
16137 isolation. The error occurred because each port's session group was
16138 being overwritten by a default value when the listener connection
16139 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
16142 o Minor feature (directory authorities, security):
16143 - The HSDir flag given by authorities now requires the Stable flag.
16144 For the current network, this results in going from 2887 to 2806
16145 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16146 attack by raising the effort for a relay to become Stable which
16147 takes at the very least 7 days to do so and by keeping the 96
16148 hours uptime requirement for HSDir. Implements ticket 8243.
16150 o Minor bugfixes (compilation):
16151 - Build with --enable-systemd correctly when libsystemd is
16152 installed, but systemd is not. Fixes bug 16164; bugfix on
16153 0.2.6.3-alpha. Patch from Peter Palfrader.
16155 o Minor bugfixes (Linux seccomp2 sandbox):
16156 - Fix sandboxing to work when running as a relaymby renaming of
16157 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
16158 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
16159 - Allow systemd connections to work with the Linux seccomp2 sandbox
16160 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16163 o Minor bugfixes (tests):
16164 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16165 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16168 Changes in version 0.2.6.8 - 2015-05-21
16169 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
16170 fixes an authority-side bug in assigning the HSDir flag. All directory
16171 authorities should upgrade.
16173 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
16174 - Revert commit that made directory authorities assign the HSDir
16175 flag to relays without a DirPort; this was bad because such relays
16176 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16179 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
16180 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16181 a client authorized hidden service. Fixes bug 15823; bugfix
16184 o Minor features (geoip):
16185 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16186 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16190 Changes in version 0.2.7.1-alpha - 2015-05-12
16191 Tor 0.2.7.1-alpha is the first alpha release in its series. It
16192 includes numerous small features and bugfixes against previous Tor
16193 versions, and numerous small infrastructure improvements. The most
16194 notable features are several new ways for controllers to interact with
16195 the hidden services subsystem.
16197 o New system requirements:
16198 - Tor no longer includes workarounds to support Libevent versions
16199 before 1.3e. Libevent 2.0 or later is recommended. Closes
16202 o Major features (controller):
16203 - Add the ADD_ONION and DEL_ONION commands that allow the creation
16204 and management of hidden services via the controller. Closes
16206 - New "GETINFO onions/current" and "GETINFO onions/detached"
16207 commands to get information about hidden services created via the
16208 controller. Part of ticket 6411.
16209 - New HSFETCH command to launch a request for a hidden service
16210 descriptor. Closes ticket 14847.
16211 - New HSPOST command to upload a hidden service descriptor. Closes
16212 ticket 3523. Patch by "DonnchaC".
16214 o Major bugfixes (hidden services):
16215 - Revert commit that made directory authorities assign the HSDir
16216 flag to relays without a DirPort; this was bad because such relays
16217 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16220 o Minor features (clock-jump tolerance):
16221 - Recover better when our clock jumps back many hours, like might
16222 happen for Tails or Whonix users who start with a very wrong
16223 hardware clock, use Tor to discover a more accurate time, and then
16224 fix their clock. Resolves part of ticket 8766.
16226 o Minor features (command-line interface):
16227 - Make --hash-password imply --hush to prevent unnecessary noise.
16228 Closes ticket 15542. Patch from "cypherpunks".
16229 - Print a warning whenever we find a relative file path being used
16230 as torrc option. Resolves issue 14018.
16232 o Minor features (controller):
16233 - Add DirAuthority lines for default directory authorities to the
16234 output of the "GETINFO config/defaults" command if not already
16235 present. Implements ticket 14840.
16236 - Controllers can now use "GETINFO hs/client/desc/id/..." to
16237 retrieve items from the client's hidden service descriptor cache.
16238 Closes ticket 14845.
16239 - Implement a new controller command "GETINFO status/fresh-relay-
16240 descs" to fetch a descriptor/extrainfo pair that was generated on
16241 demand just for the controller's use. Implements ticket 14784.
16243 o Minor features (DoS-resistance):
16244 - Make it harder for attackers to overload hidden services with
16245 introductions, by blocking multiple introduction requests on the
16246 same circuit. Resolves ticket 15515.
16248 o Minor features (geoip):
16249 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16250 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16253 o Minor features (HS popularity countermeasure):
16254 - To avoid leaking HS popularity, don't cycle the introduction point
16255 when we've handled a fixed number of INTRODUCE2 cells but instead
16256 cycle it when a random number of introductions is reached, thus
16257 making it more difficult for an attacker to find out the amount of
16258 clients that have used the introduction point for a specific HS.
16259 Closes ticket 15745.
16261 o Minor features (logging):
16262 - Include the Tor version in all LD_BUG log messages, since people
16263 tend to cut and paste those into the bugtracker. Implements
16266 o Minor features (pluggable transports):
16267 - When launching managed pluggable transports on Linux systems,
16268 attempt to have the kernel deliver a SIGTERM on tor exit if the
16269 pluggable transport process is still running. Resolves
16271 - When launching managed pluggable transports, setup a valid open
16272 stdin in the child process that can be used to detect if tor has
16273 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
16274 can be used by implementations to detect this new behavior.
16275 Resolves ticket 15435.
16277 o Minor features (testing):
16278 - Add a test to verify that the compiler does not eliminate our
16279 memwipe() implementation. Closes ticket 15377.
16280 - Add make rule `check-changes` to verify the format of changes
16281 files. Closes ticket 15180.
16282 - Add unit tests for control_event_is_interesting(). Add a compile-
16283 time check that the number of events doesn't exceed the capacity
16284 of control_event_t.event_mask. Closes ticket 15431, checks for
16285 bugs similar to 13085. Patch by "teor".
16286 - Command-line argument tests moved to Stem. Resolves ticket 14806.
16287 - Integrate the ntor, backtrace, and zero-length keys tests into the
16288 automake test suite. Closes ticket 15344.
16289 - Remove assertions during builds to determine Tor's test coverage.
16290 We don't want to trigger these even in assertions, so including
16291 them artificially makes our branch coverage look worse than it is.
16292 This patch provides the new test-stem-full and coverage-html-full
16293 configure options. Implements ticket 15400.
16295 o Minor bugfixes (build):
16296 - Improve out-of-tree builds by making non-standard rules work and
16297 clean up additional files and directories. Fixes bug 15053; bugfix
16300 o Minor bugfixes (command-line interface):
16301 - When "--quiet" is provided along with "--validate-config", do not
16302 write anything to stdout on success. Fixes bug 14994; bugfix
16304 - When complaining about bad arguments to "--dump-config", use
16305 stderr, not stdout.
16307 o Minor bugfixes (configuration, unit tests):
16308 - Only add the default fallback directories when the DirAuthorities,
16309 AlternateDirAuthority, and FallbackDir directory config options
16310 are set to their defaults. The default fallback directory list is
16311 currently empty, this fix will only change tor's behavior when it
16312 has default fallback directories. Includes unit tests for
16313 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
16314 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
16316 o Minor bugfixes (correctness):
16317 - For correctness, avoid modifying a constant string in
16318 handle_control_postdescriptor. Fixes bug 15546; bugfix
16320 - Remove side-effects from tor_assert() calls. This was harmless,
16321 because we never disable assertions, but it is bad style and
16322 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
16325 o Minor bugfixes (hidden service):
16326 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16327 a client authorized hidden service. Fixes bug 15823; bugfix
16329 - Remove an extraneous newline character from the end of hidden
16330 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
16332 o Minor bugfixes (interface):
16333 - Print usage information for --dump-config when it is used without
16334 an argument. Also, fix the error message to use different wording
16335 and add newline at the end. Fixes bug 15541; bugfix
16338 o Minor bugfixes (logs):
16339 - When building Tor under Clang, do not include an extra set of
16340 parentheses in log messages that include function names. Fixes bug
16341 15269; bugfix on every released version of Tor when compiled with
16342 recent enough Clang.
16344 o Minor bugfixes (network):
16345 - When attempting to use fallback technique for network interface
16346 lookup, disregard loopback and multicast addresses since they are
16347 unsuitable for public communications.
16349 o Minor bugfixes (statistics):
16350 - Disregard the ConnDirectionStatistics torrc options when Tor is
16351 not a relay since in that mode of operation no sensible data is
16352 being collected and because Tor might run into measurement hiccups
16353 when running as a client for some time, then becoming a relay.
16354 Fixes bug 15604; bugfix on 0.2.2.35.
16356 o Minor bugfixes (test networks):
16357 - When self-testing reachability, use ExtendAllowPrivateAddresses to
16358 determine if local/private addresses imply reachability. The
16359 previous fix used TestingTorNetwork, which implies
16360 ExtendAllowPrivateAddresses, but this excluded rare configurations
16361 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
16362 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
16363 issue discovered by CJ Ess.
16365 o Minor bugfixes (testing):
16366 - Check for matching value in server response in ntor_ref.py. Fixes
16367 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
16369 - Set the severity correctly when testing
16370 get_interface_addresses_ifaddrs() and
16371 get_interface_addresses_win32(), so that the tests fail gracefully
16372 instead of triggering an assertion. Fixes bug 15759; bugfix on
16373 0.2.6.3-alpha. Reported by Nicolas Derive.
16375 o Code simplification and refactoring:
16376 - Move the hacky fallback code out of get_interface_address6() into
16377 separate function and get it covered with unit-tests. Resolves
16379 - Refactor hidden service client-side cache lookup to intelligently
16380 report its various failure cases, and disentangle failure cases
16381 involving a lack of introduction points. Closes ticket 14391.
16382 - Use our own Base64 encoder instead of OpenSSL's, to allow more
16383 control over the output. Part of ticket 15652.
16386 - Improve the descriptions of statistics-related torrc options in
16387 the manpage to describe rationale and possible uses cases. Fixes
16389 - Improve the layout and formatting of ./configure --help messages.
16390 Closes ticket 15024. Patch from "cypherpunks".
16391 - Standardize on the term "server descriptor" in the manual page.
16392 Previously, we had used "router descriptor", "server descriptor",
16393 and "relay descriptor" interchangeably. Part of ticket 14987.
16396 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
16397 and always use the internal Base64 decoder. The internal decoder
16398 has been part of tor since 0.2.0.10-alpha, and no one should
16399 be using the OpenSSL one. Part of ticket 15652.
16400 - Remove the 'tor_strclear()' function; use memwipe() instead.
16401 Closes ticket 14922.
16403 o Removed features:
16404 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
16405 fingerprinting we now recommend pluggable transports; for forward-
16406 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
16407 - Remove the undocumented "--digests" command-line option. It
16408 complicated our build process, caused subtle build issues on
16409 multiple platforms, and is now redundant since we started
16410 including git version identifiers. Closes ticket 14742.
16411 - Tor no longer contains checks for ancient directory cache versions
16412 that didn't know about microdescriptors.
16413 - Tor no longer contains workarounds for stat files generated by
16414 super-old versions of Tor that didn't choose guards sensibly.
16417 Changes in version 0.2.4.27 - 2015-04-06
16418 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
16419 could be used by an attacker to crash hidden services, or crash clients
16420 visiting hidden services. Hidden services should upgrade as soon as
16421 possible; clients should upgrade whenever packages become available.
16423 This release also backports a simple improvement to make hidden
16424 services a bit less vulnerable to denial-of-service attacks.
16426 o Major bugfixes (security, hidden service):
16427 - Fix an issue that would allow a malicious client to trigger an
16428 assertion failure and halt a hidden service. Fixes bug 15600;
16429 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16430 - Fix a bug that could cause a client to crash with an assertion
16431 failure when parsing a malformed hidden service descriptor. Fixes
16432 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16434 o Minor features (DoS-resistance, hidden service):
16435 - Introduction points no longer allow multiple INTRODUCE1 cells to
16436 arrive on the same circuit. This should make it more expensive for
16437 attackers to overwhelm hidden services with introductions.
16438 Resolves ticket 15515.
16441 Changes in version 0.2.5.12 - 2015-04-06
16442 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
16443 could be used by an attacker to crash hidden services, or crash clients
16444 visiting hidden services. Hidden services should upgrade as soon as
16445 possible; clients should upgrade whenever packages become available.
16447 This release also backports a simple improvement to make hidden
16448 services a bit less vulnerable to denial-of-service attacks.
16450 o Major bugfixes (security, hidden service):
16451 - Fix an issue that would allow a malicious client to trigger an
16452 assertion failure and halt a hidden service. Fixes bug 15600;
16453 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16454 - Fix a bug that could cause a client to crash with an assertion
16455 failure when parsing a malformed hidden service descriptor. Fixes
16456 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16458 o Minor features (DoS-resistance, hidden service):
16459 - Introduction points no longer allow multiple INTRODUCE1 cells to
16460 arrive on the same circuit. This should make it more expensive for
16461 attackers to overwhelm hidden services with introductions.
16462 Resolves ticket 15515.
16465 Changes in version 0.2.6.7 - 2015-04-06
16466 Tor 0.2.6.7 fixes two security issues that could be used by an
16467 attacker to crash hidden services, or crash clients visiting hidden
16468 services. Hidden services should upgrade as soon as possible; clients
16469 should upgrade whenever packages become available.
16471 This release also contains two simple improvements to make hidden
16472 services a bit less vulnerable to denial-of-service attacks.
16474 o Major bugfixes (security, hidden service):
16475 - Fix an issue that would allow a malicious client to trigger an
16476 assertion failure and halt a hidden service. Fixes bug 15600;
16477 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16478 - Fix a bug that could cause a client to crash with an assertion
16479 failure when parsing a malformed hidden service descriptor. Fixes
16480 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16482 o Minor features (DoS-resistance, hidden service):
16483 - Introduction points no longer allow multiple INTRODUCE1 cells to
16484 arrive on the same circuit. This should make it more expensive for
16485 attackers to overwhelm hidden services with introductions.
16486 Resolves ticket 15515.
16487 - Decrease the amount of reattempts that a hidden service performs
16488 when its rendezvous circuits fail. This reduces the computational
16489 cost for running a hidden service under heavy load. Resolves
16493 Changes in version 0.2.6.6 - 2015-03-24
16494 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
16496 It adds numerous safety, security, correctness, and performance
16497 improvements. Client programs can be configured to use more kinds of
16498 sockets, AutomapHosts works better, the multithreading backend is
16499 improved, cell transmission is refactored, test coverage is much
16500 higher, more denial-of-service attacks are handled, guard selection is
16501 improved to handle long-term guards better, pluggable transports
16502 should work a bit better, and some annoying hidden service performance
16503 bugs should be addressed.
16505 o Minor bugfixes (portability):
16506 - Use the correct datatype in the SipHash-2-4 function to prevent
16507 compilers from assuming any sort of alignment. Fixes bug 15436;
16508 bugfix on 0.2.5.3-alpha.
16510 Changes in version 0.2.6.5-rc - 2015-03-18
16511 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
16512 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
16514 o Major bugfixes (client):
16515 - Avoid crashing when making certain configuration option changes on
16516 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
16519 o Major bugfixes (pluggable transports):
16520 - Initialize the extended OR Port authentication cookie before
16521 launching pluggable transports. This prevents a race condition
16522 that occurred when server-side pluggable transports would cache the
16523 authentication cookie before it has been (re)generated. Fixes bug
16524 15240; bugfix on 0.2.5.1-alpha.
16526 o Major bugfixes (portability):
16527 - Do not crash on startup when running on Solaris. Fixes a bug
16528 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
16531 o Minor features (heartbeat):
16532 - On relays, report how many connections we negotiated using each
16533 version of the Tor link protocols. This information will let us
16534 know if removing support for very old versions of the Tor
16535 protocols is harming the network. Closes ticket 15212.
16537 o Code simplification and refactoring:
16538 - Refactor main loop to extract the 'loop' part. This makes it
16539 easier to run Tor under Shadow. Closes ticket 15176.
16542 Changes in version 0.2.5.11 - 2015-03-17
16543 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
16545 It backports several bugfixes from the 0.2.6 branch, including a
16546 couple of medium-level security fixes for relays and exit nodes.
16547 It also updates the list of directory authorities.
16549 o Directory authority changes:
16550 - Remove turtles as a directory authority.
16551 - Add longclaw as a new (v3) directory authority. This implements
16552 ticket 13296. This keeps the directory authority count at 9.
16553 - The directory authority Faravahar has a new IP address. This
16554 closes ticket 14487.
16556 o Major bugfixes (crash, OSX, security):
16557 - Fix a remote denial-of-service opportunity caused by a bug in
16558 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16561 o Major bugfixes (relay, stability, possible security):
16562 - Fix a bug that could lead to a relay crashing with an assertion
16563 failure if a buffer of exactly the wrong layout was passed to
16564 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16565 0.2.0.10-alpha. Patch from 'cypherpunks'.
16566 - Do not assert if the 'data' pointer on a buffer is advanced to the
16567 very end of the buffer; log a BUG message instead. Only assert if
16568 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16570 o Major bugfixes (exit node stability):
16571 - Fix an assertion failure that could occur under high DNS load.
16572 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16573 diagnosed and fixed by "cypherpunks".
16575 o Major bugfixes (Linux seccomp2 sandbox):
16576 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16577 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16578 0.2.5.1-alpha. Patch from "sanic".
16580 o Minor features (controller):
16581 - New "GETINFO bw-event-cache" to get information about recent
16582 bandwidth events. Closes ticket 14128. Useful for controllers to
16583 get recent bandwidth history after the fix for ticket 13988.
16585 o Minor features (geoip):
16586 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16587 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16590 o Minor bugfixes (client, automapping):
16591 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16592 no value follows the option. Fixes bug 14142; bugfix on
16593 0.2.4.7-alpha. Patch by "teor".
16594 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16595 14195; bugfix on 0.1.0.1-rc.
16597 o Minor bugfixes (compilation):
16598 - Build without warnings with the stock OpenSSL srtp.h header, which
16599 has a duplicate declaration of SSL_get_selected_srtp_profile().
16600 Fixes bug 14220; this is OpenSSL's bug, not ours.
16602 o Minor bugfixes (directory authority):
16603 - Allow directory authorities to fetch more data from one another if
16604 they find themselves missing lots of votes. Previously, they had
16605 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16606 bugfix on 0.1.2.5-alpha.
16607 - Enlarge the buffer to read bwauth generated files to avoid an
16608 issue when parsing the file in dirserv_read_measured_bandwidths().
16609 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16611 o Minor bugfixes (statistics):
16612 - Increase period over which bandwidth observations are aggregated
16613 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
16615 o Minor bugfixes (preventative security, C safety):
16616 - When reading a hexadecimal, base-32, or base-64 encoded value from
16617 a string, always overwrite the whole output buffer. This prevents
16618 some bugs where we would look at (but fortunately, not reveal)
16619 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
16623 Changes in version 0.2.4.26 - 2015-03-17
16624 Tor 0.2.4.26 includes an updated list of directory authorities. It
16625 also backports a couple of stability and security bugfixes from 0.2.5
16628 o Directory authority changes:
16629 - Remove turtles as a directory authority.
16630 - Add longclaw as a new (v3) directory authority. This implements
16631 ticket 13296. This keeps the directory authority count at 9.
16632 - The directory authority Faravahar has a new IP address. This
16633 closes ticket 14487.
16635 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
16636 - Fix an assertion failure that could occur under high DNS load.
16637 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16638 diagnosed and fixed by "cypherpunks".
16640 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
16641 - Fix a bug that could lead to a relay crashing with an assertion
16642 failure if a buffer of exactly the wrong layout was passed to
16643 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16644 0.2.0.10-alpha. Patch from 'cypherpunks'.
16645 - Do not assert if the 'data' pointer on a buffer is advanced to the
16646 very end of the buffer; log a BUG message instead. Only assert if
16647 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16649 o Minor features (geoip):
16650 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16651 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16654 Changes in version 0.2.6.4-rc - 2015-03-09
16655 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
16656 attacker might be able to use in order to crash certain Tor
16657 directories. It also resolves some minor issues left over from, or
16658 introduced in, Tor 0.2.6.3-alpha or earlier.
16660 o Major bugfixes (crash, OSX, security):
16661 - Fix a remote denial-of-service opportunity caused by a bug in
16662 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16665 o Major bugfixes (relay, stability, possible security):
16666 - Fix a bug that could lead to a relay crashing with an assertion
16667 failure if a buffer of exactly the wrong layout is passed to
16668 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16669 0.2.0.10-alpha. Patch from "cypherpunks".
16670 - Do not assert if the 'data' pointer on a buffer is advanced to the
16671 very end of the buffer; log a BUG message instead. Only assert if
16672 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16674 o Major bugfixes (FreeBSD IPFW transparent proxy):
16675 - Fix address detection with FreeBSD transparent proxies, when
16676 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
16679 o Major bugfixes (Linux seccomp2 sandbox):
16680 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
16681 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
16683 - Allow AF_UNIX hidden services to be used with the seccomp2
16684 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
16685 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16686 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16687 0.2.5.1-alpha. Patch from "sanic".
16689 o Minor features (controller):
16690 - Messages about problems in the bootstrap process now include
16691 information about the server we were trying to connect to when we
16692 noticed the problem. Closes ticket 15006.
16694 o Minor features (geoip):
16695 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16696 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16699 o Minor features (logs):
16700 - Quiet some log messages in the heartbeat and at startup. Closes
16703 o Minor bugfixes (certificate handling):
16704 - If an authority operator accidentally makes a signing certificate
16705 with a future publication time, do not discard its real signing
16706 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
16707 - Remove any old authority certificates that have been superseded
16708 for at least two days. Previously, we would keep superseded
16709 certificates until they expired, if they were published close in
16710 time to the certificate that superseded them. Fixes bug 11454;
16711 bugfix on 0.2.1.8-alpha.
16713 o Minor bugfixes (compilation):
16714 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
16716 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
16719 o Minor bugfixes (testing):
16720 - Fix endianness issues in unit test for resolve_my_address() to
16721 have it pass on big endian systems. Fixes bug 14980; bugfix on
16723 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
16724 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
16725 - When running the new 'make test-stem' target, use the configured
16726 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
16727 from "cypherpunks".
16728 - When running the zero-length-keys tests, do not use the default
16729 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
16732 o Directory authority IP change:
16733 - The directory authority Faravahar has a new IP address. This
16734 closes ticket 14487.
16737 - Remove some lingering dead code that once supported mempools.
16738 Mempools were disabled by default in 0.2.5, and removed entirely
16739 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
16743 Changes in version 0.2.6.3-alpha - 2015-02-19
16744 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
16745 the 0.2.6.x series. It introduces support for more kinds of sockets,
16746 makes it harder to accidentally run an exit, improves our
16747 multithreading backend, incorporates several fixes for the
16748 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
16750 If no major regressions or security holes are found in this version,
16751 the next version will be a release candidate.
16753 o Deprecated versions:
16754 - Tor relays older than 0.2.4.18-rc are no longer allowed to
16755 advertise themselves on the network. Closes ticket 13555.
16757 o Major features (security, unix domain sockets):
16758 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
16759 applications can reach Tor without having to create AF_INET or
16760 AF_INET6 sockets, meaning they can completely disable their
16761 ability to make non-Tor network connections. To create a socket of
16762 this type, use "SocksPort unix:/path/to/socket". Implements
16764 - Support mapping hidden service virtual ports to AF_UNIX sockets.
16765 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
16766 Implements ticket 11485.
16768 o Major features (changed defaults):
16769 - Prevent relay operators from unintentionally running exits: When a
16770 relay is configured as an exit node, we now warn the user unless
16771 the "ExitRelay" option is set to 1. We warn even more loudly if
16772 the relay is configured with the default exit policy, since this
16773 can indicate accidental misconfiguration. Setting "ExitRelay 0"
16774 stops Tor from running as an exit relay. Closes ticket 10067.
16776 o Major features (directory system):
16777 - When downloading server- or microdescriptors from a directory
16778 server, we no longer launch multiple simultaneous requests to the
16779 same server. This reduces load on the directory servers,
16780 especially when directory guards are in use. Closes ticket 9969.
16781 - When downloading server- or microdescriptors over a tunneled
16782 connection, do not limit the length of our requests to what the
16783 Squid proxy is willing to handle. Part of ticket 9969.
16784 - Authorities can now vote on the correct digests and latest
16785 versions for different software packages. This allows packages
16786 that include Tor to use the Tor authority system as a way to get
16787 notified of updates and their correct digests. Implements proposal
16788 227. Closes ticket 10395.
16790 o Major features (guards):
16791 - Introduce the Guardfraction feature to improves load balancing on
16792 guard nodes. Specifically, it aims to reduce the traffic gap that
16793 guard nodes experience when they first get the Guard flag. This is
16794 a required step if we want to increase the guard lifetime to 9
16795 months or greater. Closes ticket 9321.
16797 o Major features (performance):
16798 - Make the CPU worker implementation more efficient by avoiding the
16799 kernel and lengthening pipelines. The original implementation used
16800 sockets to transfer data from the main thread to the workers, and
16801 didn't allow any thread to be assigned more than a single piece of
16802 work at once. The new implementation avoids communications
16803 overhead by making requests in shared memory, avoiding kernel IO
16804 where possible, and keeping more requests in flight at once.
16805 Implements ticket 9682.
16807 o Major features (relay):
16808 - Raise the minimum acceptable configured bandwidth rate for bridges
16809 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
16810 20 KiB/sec.) Closes ticket 13822.
16812 o Major bugfixes (exit node stability):
16813 - Fix an assertion failure that could occur under high DNS load.
16814 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16815 diagnosed and fixed by "cypherpunks".
16817 o Major bugfixes (mixed relay-client operation):
16818 - When running as a relay and client at the same time (not
16819 recommended), if we decide not to use a new guard because we want
16820 to retry older guards, only close the locally-originating circuits
16821 passing through that guard. Previously we would close all the
16822 circuits through that guard. Fixes bug 9819; bugfix on
16823 0.2.1.1-alpha. Reported by "skruffy".
16825 o Minor features (build):
16826 - New --disable-system-torrc compile-time option to prevent Tor from
16827 looking for the system-wide torrc or torrc-defaults files.
16828 Resolves ticket 13037.
16830 o Minor features (controller):
16831 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
16832 events so controllers can observe circuit isolation inputs. Closes
16834 - ControlPort now supports the unix:/path/to/socket syntax as an
16835 alternative to the ControlSocket option, for consistency with
16836 SocksPort and HiddenServicePort. Closes ticket 14451.
16837 - New "GETINFO bw-event-cache" to get information about recent
16838 bandwidth events. Closes ticket 14128. Useful for controllers to
16839 get recent bandwidth history after the fix for ticket 13988.
16841 o Minor features (Denial of service resistance):
16842 - Count the total number of bytes used storing hidden service
16843 descriptors against the value of MaxMemInQueues. If we're low on
16844 memory, and more than 20% of our memory is used holding hidden
16845 service descriptors, free them until no more than 10% of our
16846 memory holds hidden service descriptors. Free the least recently
16847 fetched descriptors first. Resolves ticket 13806.
16848 - When we have recently been under memory pressure (over 3/4 of
16849 MaxMemInQueues is allocated), then allocate smaller zlib objects
16850 for small requests. Closes ticket 11791.
16852 o Minor features (geoip):
16853 - Update geoip and geoip6 files to the January 7 2015 Maxmind
16854 GeoLite2 Country database.
16856 o Minor features (guard nodes):
16857 - Reduce the time delay before saving guard status to disk from 10
16858 minutes to 30 seconds (or from one hour to 10 minutes if
16859 AvoidDiskWrites is set). Closes ticket 12485.
16861 o Minor features (hidden service):
16862 - Make Sybil attacks against hidden services harder by changing the
16863 minimum time required to get the HSDir flag from 25 hours up to 96
16864 hours. Addresses ticket 14149.
16865 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
16866 services to disable the anti-scanning feature introduced in
16867 0.2.6.2-alpha. With this option not set, a connection to an
16868 unlisted port closes the circuit. With this option set, only a
16869 RELAY_DONE cell is sent. Closes ticket 14084.
16871 o Minor features (interface):
16872 - Implement "-f -" command-line option to read torrc configuration
16873 from standard input, if you don't want to store the torrc file in
16874 the file system. Implements feature 13865.
16876 o Minor features (logging):
16877 - Add a count of unique clients to the bridge heartbeat message.
16878 Resolves ticket 6852.
16879 - Suppress "router info incompatible with extra info" message when
16880 reading extrainfo documents from cache. (This message got loud
16881 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
16883 - Elevate hidden service authorized-client message from DEBUG to
16884 INFO. Closes ticket 14015.
16886 o Minor features (stability):
16887 - Add assertions in our hash-table iteration code to check for
16888 corrupted values that could cause infinite loops. Closes
16891 o Minor features (systemd):
16892 - Various improvements and modernizations in systemd hardening
16893 support. Closes ticket 13805. Patch from Craig Andrews.
16895 o Minor features (testing networks):
16896 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
16897 and the default on a testing network to 2 minutes. Drop the
16898 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
16899 keep the default on a testing network at 30 seconds. This reduces
16900 HS bootstrap time to around 25 seconds. Also, change the default
16901 time in test-network.sh to match. Closes ticket 13401. Patch
16903 - Create TestingDirAuthVoteHSDir to correspond to
16904 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
16905 HSDir flag for the listed relays regardless of uptime or ORPort
16906 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
16907 Partial implementation for ticket 14067. Patch by "teor".
16909 o Minor features (tor2web mode):
16910 - Introduce the config option Tor2webRendezvousPoints, which allows
16911 clients in Tor2webMode to select a specific Rendezvous Point to be
16912 used in HS circuits. This might allow better performance for
16913 Tor2Web nodes. Implements ticket 12844.
16915 o Minor bugfixes (client DNS):
16916 - Report the correct cached DNS expiration times on SOCKS port or in
16917 DNS replies. Previously, we would report everything as "never
16918 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
16919 - Avoid a small memory leak when we find a cached answer for a
16920 reverse DNS lookup in a client-side DNS cache. (Remember, client-
16921 side DNS caching is off by default, and is not recommended.) Fixes
16922 bug 14259; bugfix on 0.2.0.1-alpha.
16924 o Minor bugfixes (client, automapping):
16925 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16926 no value follows the option. Fixes bug 14142; bugfix on
16927 0.2.4.7-alpha. Patch by "teor".
16928 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16929 14195; bugfix on 0.1.0.1-rc.
16930 - Prevent changes to other options from removing the wildcard value
16931 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
16933 - Allow MapAddress and AutomapHostsOnResolve to work together when
16934 an address is mapped into another address type (like .onion) that
16935 must be automapped at resolve time. Fixes bug 7555; bugfix
16938 o Minor bugfixes (client, bridges):
16939 - When we are using bridges and we had a network connectivity
16940 problem, only retry connecting to our currently configured
16941 bridges, not all bridges we know about and remember using. Fixes
16942 bug 14216; bugfix on 0.2.2.17-alpha.
16944 o Minor bugfixes (client, IPv6):
16945 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
16946 flag is not set; and not because the NoIPv4Traffic flag was set.
16947 Previously we'd looked at the NoIPv4Traffic flag for both types of
16948 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
16950 o Minor bugfixes (compilation):
16951 - The address of an array in the middle of a structure will always
16952 be non-NULL. clang recognises this and complains. Disable the
16953 tautologous and redundant check to silence this warning. Fixes bug
16954 14001; bugfix on 0.2.1.2-alpha.
16955 - Avoid warnings when building with systemd 209 or later. Fixes bug
16956 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
16957 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
16958 Addresses ticket 14188.
16959 - Build without warnings with the stock OpenSSL srtp.h header, which
16960 has a duplicate declaration of SSL_get_selected_srtp_profile().
16961 Fixes bug 14220; this is OpenSSL's bug, not ours.
16962 - Do not compile any code related to Tor2Web mode when Tor2Web mode
16963 is not enabled at compile time. Previously, this code was included
16964 in a disabled state. See discussion on ticket 12844.
16965 - Remove the --disable-threads configure option again. It was
16966 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
16967 14819; bugfix on 0.2.6.2-alpha.
16969 o Minor bugfixes (controller):
16970 - Report "down" in response to the "GETINFO entry-guards" command
16971 when relays are down with an unreachable_since value. Previously,
16972 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
16973 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
16974 14116; bugfix on 0.2.2.9-alpha.
16975 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
16976 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
16978 o Minor bugfixes (directory authority):
16979 - Allow directory authorities to fetch more data from one another if
16980 they find themselves missing lots of votes. Previously, they had
16981 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16982 bugfix on 0.1.2.5-alpha.
16983 - Do not attempt to download extrainfo documents which we will be
16984 unable to validate with a matching server descriptor. Fixes bug
16985 13762; bugfix on 0.2.0.1-alpha.
16986 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
16987 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
16988 - Enlarge the buffer to read bwauth generated files to avoid an
16989 issue when parsing the file in dirserv_read_measured_bandwidths().
16990 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16992 o Minor bugfixes (file handling):
16993 - Stop failing when key files are zero-length. Instead, generate new
16994 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
16995 on all versions of Tor. Patch by "teor".
16996 - Stop generating a fresh .old RSA onion key file when the .old file
16997 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
16998 - Avoid overwriting .old key files with empty key files.
16999 - Skip loading zero-length extrainfo store, router store, stats,
17000 state, and key files.
17001 - Avoid crashing when trying to reload a torrc specified as a
17002 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
17005 o Minor bugfixes (hidden services):
17006 - Close the introduction circuit when we have no more usable intro
17007 points, instead of waiting for it to time out. This also ensures
17008 that no follow-up HS descriptor fetch is triggered when the
17009 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
17010 - When fetching a hidden service descriptor for a down service that
17011 was recently up, do not keep refetching until we try the same
17012 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
17013 - Successfully launch Tor with a nonexistent hidden service
17014 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
17015 14106; bugfix on 0.2.6.2-alpha.
17017 o Minor bugfixes (logging):
17018 - Avoid crashing when there are more log domains than entries in
17019 domain_list. Bugfix on 0.2.3.1-alpha.
17020 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
17022 - Don't log messages to stdout twice when starting up. Fixes bug
17023 13993; bugfix on 0.2.6.1-alpha.
17025 o Minor bugfixes (parsing):
17026 - Stop accepting milliseconds (or other junk) at the end of
17027 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
17028 - Support two-number and three-number version numbers correctly, in
17029 case we change the Tor versioning system in the future. Fixes bug
17030 13661; bugfix on 0.0.8pre1.
17032 o Minor bugfixes (path counting):
17033 - When deciding whether the consensus lists any exit nodes, count
17034 the number listed in the consensus, not the number we have
17035 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
17036 - When deciding whether we have any exit nodes, only examine
17037 ExitNodes when the ExitNodes option is actually set. Fixes part of
17038 bug 14918; bugfix on 0.2.6.2-alpha.
17039 - Get rid of redundant and possibly scary warnings that we are
17040 missing directory information while we bootstrap. Fixes part of
17041 bug 14918; bugfix on 0.2.6.2-alpha.
17043 o Minor bugfixes (portability):
17044 - Fix the ioctl()-based network interface lookup code so that it
17045 will work on systems that have variable-length struct ifreq, for
17047 - Fix scheduler compilation on targets where char is unsigned. Fixes
17048 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
17050 o Minor bugfixes (sandbox):
17051 - Allow glibc fatal errors to be sent to stderr before Tor exits.
17052 Previously, glibc would try to write them to /dev/tty, and the
17053 sandbox would trap the call and make Tor exit prematurely. Fixes
17054 bug 14759; bugfix on 0.2.5.1-alpha.
17056 o Minor bugfixes (shutdown):
17057 - When shutting down, always call event_del() on lingering read or
17058 write events before freeing them. Otherwise, we risk double-frees
17059 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
17062 o Minor bugfixes (small memory leaks):
17063 - Avoid leaking memory when using IPv6 virtual address mappings.
17064 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
17067 o Minor bugfixes (statistics):
17068 - Increase period over which bandwidth observations are aggregated
17069 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17071 o Minor bugfixes (systemd support):
17072 - Fix detection and operation of systemd watchdog. Fixes part of bug
17073 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
17074 - Run correctly under systemd with the RunAsDaemon option set. Fixes
17075 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
17076 - Inform the systemd supervisor about more changes in the Tor
17077 process status. Implements part of ticket 14141. Patch from
17079 - Cause the "--disable-systemd" option to actually disable systemd
17080 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
17083 o Minor bugfixes (TLS):
17084 - Check more thoroughly throughout the TLS code for possible
17085 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
17087 o Minor bugfixes (transparent proxy):
17088 - Use getsockname, not getsockopt, to retrieve the address for a
17089 TPROXY-redirected connection. Fixes bug 13796; bugfix
17092 o Code simplification and refactoring:
17093 - Move fields related to isolating and configuring client ports into
17094 a shared structure. Previously, they were duplicated across
17095 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
17096 to copy them correctly had been the cause of at least one bug in
17097 the past. Closes ticket 8546.
17098 - Refactor the get_interface_addresses_raw() doom-function into
17099 multiple smaller and simpler subfunctions. Cover the resulting
17100 subfunctions with unit-tests. Fixes a significant portion of
17102 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
17103 only for version <= 0.2.2.24 which is now deprecated. Closes
17105 - Remove a test for a long-defunct broken version-one
17109 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
17110 for writing the OpenBSD-specific tips. Resolves ticket 13702.
17111 - Make the tor-resolve documentation match its help string and its
17112 options. Resolves part of ticket 14325.
17113 - Log a more useful error message from tor-resolve when failing to
17114 look up a hidden service address. Resolves part of ticket 14325.
17116 o Downgraded warnings:
17117 - Don't warn when we've attempted to contact a relay using the wrong
17118 ntor onion key. Closes ticket 9635.
17120 o Removed features:
17121 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
17122 longer silently accepted as an alias for "ExitNodes".
17123 - The --enable-mempool and --enable-buf-freelists options, which
17124 were originally created to work around bad malloc implementations,
17125 no longer exist. They were off-by-default in 0.2.5. Closes
17129 - Make the checkdir/perms test complete successfully even if the
17130 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
17131 - Test that tor does not fail when key files are zero-length. Check
17132 that tor generates new keys, and overwrites the empty key files.
17133 - Test that tor generates new keys when keys are missing
17134 (existing behavior).
17135 - Test that tor does not overwrite key files that already contain
17136 data (existing behavior). Tests bug 13111. Patch by "teor".
17137 - New "make test-stem" target to run stem integration tests.
17138 Requires that the "STEM_SOURCE_DIR" environment variable be set.
17139 Closes ticket 14107.
17140 - Make the test_cmdline_args.py script work correctly on Windows.
17141 Patch from Gisle Vanem.
17142 - Move the slower unit tests into a new "./src/test/test-slow"
17143 binary that can be run independently of the other tests. Closes
17145 - Avoid undefined behavior when sampling huge values from the
17146 Laplace distribution. This made unittests fail on Raspberry Pi.
17147 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
17150 Changes in version 0.2.6.2-alpha - 2014-12-31
17151 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
17152 It introduces a major new backend for deciding when to send cells on
17153 channels, which should lead down the road to big performance
17154 increases. It contains security and statistics features for better
17155 work on hidden services, and numerous bugfixes.
17157 This release contains many new unit tests, along with major
17158 performance improvements for running testing networks using Chutney.
17159 Thanks to a series of patches contributed by "teor", testing networks
17160 should now bootstrap in seconds, rather than minutes.
17162 o Major features (relay, infrastructure):
17163 - Complete revision of the code that relays use to decide which cell
17164 to send next. Formerly, we selected the best circuit to write on
17165 each channel, but we didn't select among channels in any
17166 sophisticated way. Now, we choose the best circuits globally from
17167 among those whose channels are ready to deliver traffic.
17169 This patch implements a new inter-cmux comparison API, a global
17170 high/low watermark mechanism and a global scheduler loop for
17171 transmission prioritization across all channels as well as among
17172 circuits on one channel. This schedule is currently tuned to
17173 (tolerantly) avoid making changes in network performance, but it
17174 should form the basis for major circuit performance increases in
17175 the future. Code by Andrea; tuning by Rob Jansen; implements
17178 o Major features (hidden services):
17179 - Make HS port scanning more difficult by immediately closing the
17180 circuit when a user attempts to connect to a nonexistent port.
17181 Closes ticket 13667.
17182 - Add a HiddenServiceStatistics option that allows Tor relays to
17183 gather and publish statistics about the overall size and volume of
17184 hidden service usage. Specifically, when this option is turned on,
17185 an HSDir will publish an approximate number of hidden services
17186 that have published descriptors to it the past 24 hours. Also, if
17187 a relay has acted as a hidden service rendezvous point, it will
17188 publish the approximate amount of rendezvous cells it has relayed
17189 the past 24 hours. The statistics themselves are obfuscated so
17190 that the exact values cannot be derived. For more details see
17191 proposal 238, "Better hidden service stats from Tor relays". This
17192 feature is currently disabled by default. Implements feature 13192.
17194 o Major bugfixes (client, automap):
17195 - Repair automapping with IPv6 addresses. This automapping should
17196 have worked previously, but one piece of debugging code that we
17197 inserted to detect a regression actually caused the regression to
17198 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
17199 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
17202 o Major bugfixes (hidden services):
17203 - When closing an introduction circuit that was opened in parallel
17204 with others, don't mark the introduction point as unreachable.
17205 Previously, the first successful connection to an introduction
17206 point would make the other introduction points get marked as
17207 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
17209 o Directory authority changes:
17210 - Remove turtles as a directory authority.
17211 - Add longclaw as a new (v3) directory authority. This implements
17212 ticket 13296. This keeps the directory authority count at 9.
17214 o Major removed features:
17215 - Tor clients no longer support connecting to hidden services
17216 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
17217 option has been removed. (There shouldn't be any hidden services
17218 running these versions on the network.) Closes ticket 7803.
17220 o Minor features (client):
17221 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
17222 is enabled, reject requests with IP addresses as hostnames.
17223 Resolves ticket 13315.
17225 o Minor features (controller):
17226 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
17227 write an unscheduled heartbeat message to the log. Implements
17230 o Minor features (geoip):
17231 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
17234 o Minor features (hidden services):
17235 - When re-enabling the network, don't try to build introduction
17236 circuits until we have successfully built a circuit. This makes
17237 hidden services come up faster when the network is re-enabled.
17238 Patch from "akwizgran". Closes ticket 13447.
17239 - When we fail to retrieve a hidden service descriptor, send the
17240 controller an "HS_DESC FAILED" controller event. Implements
17242 - New HiddenServiceDirGroupReadable option to cause hidden service
17243 directories and hostname files to be created group-readable. Patch
17244 from "anon", David Stainton, and "meejah". Closes ticket 11291.
17246 o Minor features (systemd):
17247 - Where supported, when running with systemd, report successful
17248 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
17249 - When running with systemd, support systemd watchdog messages. Part
17250 of ticket 11016. Patch by Michael Scherer.
17252 o Minor features (transparent proxy):
17253 - Update the transparent proxy option checks to allow for both ipfw
17254 and pf on OS X. Closes ticket 14002.
17255 - Use the correct option when using IPv6 with transparent proxy
17256 support on Linux. Resolves 13808. Patch by Francisco Blas
17259 o Minor bugfixes (preventative security, C safety):
17260 - When reading a hexadecimal, base-32, or base-64 encoded value from
17261 a string, always overwrite the whole output buffer. This prevents
17262 some bugs where we would look at (but fortunately, not reveal)
17263 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17265 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
17266 just the part that's used. This makes it harder for data leak bugs
17267 to occur in the event of other programming failures. Resolves
17270 o Minor bugfixes (client, microdescriptors):
17271 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
17272 computing which microdescriptors to download. This keeps us from
17273 erroneous download behavior if two microdescriptor digests ever
17274 have the same first 160 bits. Fixes part of bug 13399; bugfix
17276 - Reset a router's status if its microdescriptor digest changes,
17277 even if the first 160 bits remain the same. Fixes part of bug
17278 13399; bugfix on 0.2.3.1-alpha.
17280 o Minor bugfixes (compilation):
17281 - Silence clang warnings under --enable-expensive-hardening,
17282 including implicit truncation of 64 bit values to 32 bit, const
17283 char assignment to self, tautological compare, and additional
17284 parentheses around equality tests. Fixes bug 13577; bugfix
17286 - Fix a clang warning about checking whether an address in the
17287 middle of a structure is NULL. Fixes bug 14001; bugfix
17290 o Minor bugfixes (hidden services):
17291 - Correctly send a controller event when we find that a rendezvous
17292 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
17293 - Pre-check directory permissions for new hidden-services to avoid
17294 at least one case of "Bug: Acting on config options left us in a
17295 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
17296 - When adding a new hidden service (for example, via SETCONF), Tor
17297 no longer congratulates the user for running a relay. Fixes bug
17298 13941; bugfix on 0.2.6.1-alpha.
17299 - When fetching hidden service descriptors, we now check not only
17300 for whether we got the hidden service we had in mind, but also
17301 whether we got the particular descriptors we wanted. This prevents
17302 a class of inefficient but annoying DoS attacks by hidden service
17303 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
17306 o Minor bugfixes (Linux seccomp2 sandbox):
17307 - Make transparent proxy support work along with the seccomp2
17308 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
17309 by Francisco Blas Izquierdo Riera.
17310 - Fix a memory leak in tor-resolve when running with the sandbox
17311 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
17313 o Minor bugfixes (logging):
17314 - Downgrade warnings about RSA signature failures to info log level.
17315 Emit a warning when an extra info document is found incompatible
17316 with a corresponding router descriptor. Fixes bug 9812; bugfix
17318 - Make connection_ap_handshake_attach_circuit() log the circuit ID
17319 correctly. Fixes bug 13701; bugfix on 0.0.6.
17321 o Minor bugfixes (misc):
17322 - Stop allowing invalid address patterns like "*/24" that contain
17323 both a wildcard address and a bit prefix length. This affects all
17324 our address-range parsing code. Fixes bug 7484; bugfix
17327 o Minor bugfixes (testing networks, fast startup):
17328 - Allow Tor to build circuits using a consensus with no exits. If
17329 the consensus has no exits (typical of a bootstrapping test
17330 network), allow Tor to build circuits once enough descriptors have
17331 been downloaded. This assists in bootstrapping a testing Tor
17332 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
17334 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
17335 header to directory servers. This allows us to obtain consensuses
17336 promptly when the consensus interval is very short. This assists
17337 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
17338 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
17339 - Stop assuming that private addresses are local when checking
17340 reachability in a TestingTorNetwork. Instead, when testing, assume
17341 all OR connections are remote. (This is necessary due to many test
17342 scenarios running all relays on localhost.) This assists in
17343 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
17344 0.1.0.1-rc. Patch by "teor".
17345 - Avoid building exit circuits from a consensus with no exits. Now
17346 thanks to our fix for 13718, we accept a no-exit network as not
17347 wholly lost, but we need to remember not to try to build exit
17348 circuits on it. Closes ticket 13814; patch by "teor".
17349 - Stop requiring exits to have non-zero bandwithcapacity in a
17350 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
17351 ignore exit bandwidthcapacity. This assists in bootstrapping a
17352 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
17353 on 0.2.0.3-alpha. Patch by "teor".
17354 - Add "internal" to some bootstrap statuses when no exits are
17355 available. If the consensus does not contain Exits, Tor will only
17356 build internal circuits. In this case, relevant statuses will
17357 contain the word "internal" as indicated in the Tor control-
17358 spec.txt. When bootstrap completes, Tor will be ready to build
17359 internal circuits. If a future consensus contains Exits, exit
17360 circuits may become available. Fixes part of bug 13718; bugfix on
17361 0.2.4.10-alpha. Patch by "teor".
17362 - Decrease minimum consensus interval to 10 seconds when
17363 TestingTorNetwork is set, or 5 seconds for the first consensus.
17364 Fix assumptions throughout the code that assume larger intervals.
17365 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
17367 - Avoid excluding guards from path building in minimal test
17368 networks, when we're in a test network and excluding guards would
17369 exclude all relays. This typically occurs in incredibly small tor
17370 networks, and those using "TestingAuthVoteGuard *". Fixes part of
17371 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
17373 o Code simplification and refactoring:
17374 - Stop using can_complete_circuits as a global variable; access it
17375 with a function instead.
17376 - Avoid using operators directly as macro arguments: this lets us
17377 apply coccinelle transformations to our codebase more directly.
17378 Closes ticket 13172.
17379 - Combine the functions used to parse ClientTransportPlugin and
17380 ServerTransportPlugin into a single function. Closes ticket 6456.
17381 - Add inline functions and convenience macros for inspecting channel
17382 state. Refactor the code to use convenience macros instead of
17383 checking channel state directly. Fixes issue 7356.
17384 - Document all members of was_router_added_t and rename
17385 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
17386 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
17387 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
17388 constant instead of hardcoded value. Fixes issue 13840.
17389 - Refactor our generic strmap and digestmap types into a single
17390 implementation, so that we can add a new digest256map
17394 - Document the bridge-authority-only 'networkstatus-bridges' file.
17395 Closes ticket 13713; patch from "tom".
17396 - Fix typo in PredictedPortsRelevanceTime option description in
17397 manpage. Resolves issue 13707.
17398 - Stop suggesting that users specify relays by nickname: it isn't a
17399 good idea. Also, properly cross-reference how to specify relays in
17400 all parts of manual documenting options that take a list of
17401 relays. Closes ticket 13381.
17402 - Clarify the HiddenServiceDir option description in manpage to make
17403 it clear that relative paths are taken with respect to the current
17404 working directory. Also clarify that this behavior is not
17405 guaranteed to remain indefinitely. Fixes issue 13913.
17408 - New tests for many parts of channel, relay, and circuitmux
17409 functionality. Code by Andrea; part of 9262.
17410 - New tests for parse_transport_line(). Part of ticket 6456.
17411 - In the unit tests, use chgrp() to change the group of the unit
17412 test temporary directory to the current user, so that the sticky
17413 bit doesn't interfere with tests that check directory groups.
17415 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
17419 Changes in version 0.2.6.1-alpha - 2014-10-30
17420 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
17421 includes numerous code cleanups and new tests, and fixes a large
17422 number of annoying bugs. Out-of-memory conditions are handled better
17423 than in 0.2.5, pluggable transports have improved proxy support, and
17424 clients now use optimistic data for contacting hidden services. Also,
17425 we are now more robust to changes in what we consider a parseable
17426 directory object, so that tightening restrictions does not have a risk
17427 of introducing infinite download loops.
17429 This is the first alpha release in a new series, so expect there to be
17430 bugs. Users who would rather test out a more stable branch should stay
17431 with 0.2.5.x for now.
17433 o New compiler and system requirements:
17434 - Tor 0.2.6.x requires that your compiler support more of the C99
17435 language standard than before. The 'configure' script now detects
17436 whether your compiler supports C99 mid-block declarations and
17437 designated initializers. If it does not, Tor will not compile.
17439 We may revisit this requirement if it turns out that a significant
17440 number of people need to build Tor with compilers that don't
17441 bother implementing a 15-year-old standard. Closes ticket 13233.
17442 - Tor no longer supports systems without threading support. When we
17443 began working on Tor, there were several systems that didn't have
17444 threads, or where the thread support wasn't able to run the
17445 threads of a single process on multiple CPUs. That no longer
17446 holds: every system where Tor needs to run well now has threading
17447 support. Resolves ticket 12439.
17449 o Removed platform support:
17450 - We no longer include special code to build on Windows CE; as far
17451 as we know, nobody has used Tor on Windows CE in a very long time.
17452 Closes ticket 11446.
17454 o Major features (bridges):
17455 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
17456 transports if they are configured via the "TOR_PT_PROXY"
17457 environment variable. Implements proposal 232. Resolves
17460 o Major features (client performance, hidden services):
17461 - Allow clients to use optimistic data when connecting to a hidden
17462 service, which should remove a round-trip from hidden service
17463 initialization. See proposal 181 for details. Implements
17466 o Major features (directory system):
17467 - Upon receiving an unparseable directory object, if its digest
17468 matches what we expected, then don't try to download it again.
17469 Previously, when we got a descriptor we didn't like, we would keep
17470 trying to download it over and over. Closes ticket 11243.
17472 o Major features (sample torrc):
17473 - Add a new, infrequently-changed "torrc.minimal". This file is
17474 similar to torrc.sample, but it will change as infrequently as
17475 possible, for the benefit of users whose systems prompt them for
17476 intervention whenever a default configuration file is changed.
17477 Making this change allows us to update torrc.sample to be a more
17478 generally useful "sample torrc".
17480 o Major bugfixes (directory authorities):
17481 - Do not assign the HSDir flag to relays if they are not Valid, or
17482 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
17484 o Major bugfixes (directory bandwidth performance):
17485 - Don't flush the zlib buffer aggressively when compressing
17486 directory information for clients. This should save about 7% of
17487 the bandwidth currently used for compressed descriptors and
17488 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
17490 o Minor features (security, memory wiping):
17491 - Ensure we securely wipe keys from memory after
17492 crypto_digest_get_digest and init_curve25519_keypair_from_file
17493 have finished using them. Resolves ticket 13477.
17495 o Minor features (security, out-of-memory handling):
17496 - When handling an out-of-memory condition, allocate less memory for
17497 temporary data structures. Fixes issue 10115.
17498 - When handling an out-of-memory condition, consider more types of
17499 buffers, including those on directory connections, and zlib
17500 buffers. Resolves ticket 11792.
17503 - When identity keypair is generated for first time, log a
17504 congratulatory message that links to the new relay lifecycle
17505 document. Implements feature 10427.
17507 o Minor features (client):
17508 - Clients are now willing to send optimistic data (before they
17509 receive a 'connected' cell) to relays of any version. (Relays
17510 without support for optimistic data are no longer supported on the
17511 Tor network.) Resolves ticket 13153.
17513 o Minor features (directory authorities):
17514 - Don't list relays with a bandwidth estimate of 0 in the consensus.
17515 Implements a feature proposed during discussion of bug 13000.
17516 - In tor-gencert, report an error if the user provides the same
17517 argument more than once.
17518 - If a directory authority can't find a best consensus method in the
17519 votes that it holds, it now falls back to its favorite consensus
17520 method. Previously, it fell back to method 1. Neither of these is
17521 likely to get enough signatures, but "fall back to favorite"
17522 doesn't require us to maintain support an obsolete consensus
17523 method. Implements part of proposal 215.
17525 o Minor features (logging):
17526 - On Unix-like systems, you can now use named pipes as the target of
17527 the Log option, and other options that try to append to files.
17528 Closes ticket 12061. Patch from "carlo von lynX".
17529 - When opening a log file at startup, send it every log message that
17530 we generated between startup and opening it. Previously, log
17531 messages that were generated before opening the log file were only
17532 logged to stdout. Closes ticket 6938.
17533 - Add a TruncateLogFile option to overwrite logs instead of
17534 appending to them. Closes ticket 5583.
17536 o Minor features (portability, Solaris):
17537 - Threads are no longer disabled by default on Solaris; we believe
17538 that the versions of Solaris with broken threading support are all
17539 obsolete by now. Resolves ticket 9495.
17541 o Minor features (relay):
17542 - Re-check our address after we detect a changed IP address from
17543 getsockname(). This ensures that the controller command "GETINFO
17544 address" will report the correct value. Resolves ticket 11582.
17546 - A new AccountingRule option lets Relays set whether they'd like
17547 AccountingMax to be applied separately to inbound and outbound
17548 traffic, or applied to the sum of inbound and outbound traffic.
17549 Resolves ticket 961. Patch by "chobe".
17551 o Minor features (testing networks):
17552 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
17553 the "Exit" flag regardless of their uptime, bandwidth, or exit
17554 policy. TestingTorNetwork must be set for this option to have any
17555 effect. Previously, authorities would take up to 35 minutes to
17556 give nodes the Exit flag in a test network. Partially implements
17559 o Minor features (validation):
17560 - Check all date/time values passed to tor_timegm and
17561 parse_rfc1123_time for validity, taking leap years into account.
17562 Improves HTTP header validation. Implemented with bug 13476.
17563 - In correct_tm(), limit the range of values returned by system
17564 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
17565 This means we don't have to deal with negative or too large dates,
17566 even if a clock is wrong. Otherwise we might fail to read a file
17567 written by us which includes such a date. Fixes bug 13476.
17569 o Minor bugfixes (bridge clients):
17570 - When configured to use a bridge without an identity digest (not
17571 recommended), avoid launching an extra channel to it when
17572 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
17574 o Minor bugfixes (bridges):
17575 - When DisableNetwork is set, do not launch pluggable transport
17576 plugins, and if any are running, terminate them. Fixes bug 13213;
17577 bugfix on 0.2.3.6-alpha.
17579 o Minor bugfixes (C correctness):
17580 - Fix several instances of possible integer overflow/underflow/NaN.
17581 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
17583 - In circuit_build_times_calculate_timeout() in circuitstats.c,
17584 avoid dividing by zero in the pareto calculations. This traps
17585 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
17587 - Fix an integer overflow in format_time_interval(). Fixes bug
17588 13393; bugfix on 0.2.0.10-alpha.
17589 - Set the correct day of year value when the system's localtime(_r)
17590 or gmtime(_r) functions fail to set struct tm. Not externally
17591 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
17592 - Avoid unlikely signed integer overflow in tor_timegm on systems
17593 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
17595 o Minor bugfixes (client):
17596 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
17597 BadExit flag are not considered worthy candidates. Fixes bug
17598 13066; bugfix on 0.1.2.3-alpha.
17599 - Use the consensus schedule for downloading consensuses, and not
17600 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
17601 - Handle unsupported or malformed SOCKS5 requests properly by
17602 responding with the appropriate error message before closing the
17603 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
17605 o Minor bugfixes (client, torrc):
17606 - Stop modifying the value of our DirReqStatistics torrc option just
17607 because we're not a bridge or relay. This bug was causing Tor
17608 Browser users to write "DirReqStatistics 0" in their torrc files
17609 as if they had chosen to change the config. Fixes bug 4244; bugfix
17611 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
17612 that our options have changed every time we SIGHUP. Fixes bug
17613 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
17615 o Minor bugfixes (controller):
17616 - Return an error when the second or later arguments of the
17617 "setevents" controller command are invalid events. Previously we
17618 would return success while silently skipping invalid events. Fixes
17619 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
17621 o Minor bugfixes (directory system):
17622 - Always believe that v3 directory authorities serve extra-info
17623 documents, whether they advertise "caches-extra-info" or not.
17624 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
17625 - When running as a v3 directory authority, advertise that you serve
17626 extra-info documents so that clients who want them can find them
17627 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
17628 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
17629 Previously, directories offering BRIDGE_DIRINFO and some other
17630 flag (i.e. microdescriptors or extrainfo) would be ignored when
17631 looking for bridges. Partially fixes bug 13163; bugfix
17634 o Minor bugfixes (networking):
17635 - Check for orconns and use connection_or_close_for_error() rather
17636 than connection_mark_for_close() directly in the getsockopt()
17637 failure case of connection_handle_write_impl(). Fixes bug 11302;
17638 bugfix on 0.2.4.4-alpha.
17640 o Minor bugfixes (relay):
17641 - When generating our family list, remove spaces from around the
17642 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
17643 - If our previous bandwidth estimate was 0 bytes, allow publishing a
17644 new relay descriptor immediately. Fixes bug 13000; bugfix
17647 o Minor bugfixes (testing networks):
17648 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
17649 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
17650 - Stop using the default authorities in networks which provide both
17651 AlternateDirAuthority and AlternateBridgeAuthority. Partially
17652 fixes bug 13163; bugfix on 0.2.0.13-alpha.
17654 o Minor bugfixes (testing):
17655 - Stop spawn test failures due to a race condition between the
17656 SIGCHLD handler updating the process status, and the test reading
17657 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
17659 o Minor bugfixes (testing, Windows):
17660 - Avoid passing an extra backslash when creating a temporary
17661 directory for running the unit tests on Windows. Fixes bug 12392;
17662 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
17664 o Minor bugfixes (windows):
17665 - Remove code to special-case handling of NTE_BAD_KEYSET when
17666 acquiring windows CryptoAPI context. This error can't actually
17667 occur for the parameters we're providing. Fixes bug 10816; bugfix
17670 o Minor bugfixes (zlib):
17671 - Avoid truncating a zlib stream when trying to finalize it with an
17672 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
17675 - Allow our configure script to build correctly with autoconf 2.62
17676 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
17677 - Improve the error message from ./configure to make it clear that
17678 when asciidoc has not been found, the user will have to either add
17679 --disable-asciidoc argument or install asciidoc. Resolves
17682 o Code simplification and refactoring:
17683 - Change the entry_is_live() function to take named bitfield
17684 elements instead of an unnamed list of booleans. Closes
17686 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
17687 Resolves ticket 12205.
17688 - Use calloc and reallocarray functions instead of multiply-
17689 then-malloc. This makes it less likely for us to fall victim to an
17690 integer overflow attack when allocating. Resolves ticket 12855.
17691 - Use the standard macro name SIZE_MAX, instead of our
17693 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
17694 functions which take them as arguments. Replace 0 with NO_DIRINFO
17695 in a function call for clarity. Seeks to prevent future issues
17697 - Avoid 4 null pointer errors under clang static analysis by using
17698 tor_assert() to prove that the pointers aren't null. Fixes
17700 - Rework the API of policies_parse_exit_policy() to use a bitmask to
17701 represent parsing options, instead of a confusing mess of
17702 booleans. Resolves ticket 8197.
17703 - Introduce a helper function to parse ExitPolicy in
17704 or_options_t structure.
17707 - Add a doc/TUNING document with tips for handling large numbers of
17708 TCP connections when running busy Tor relay. Update the warning
17709 message to point to this file when running out of sockets
17710 operating system is allowing to use simultaneously. Resolves
17713 o Removed features:
17714 - We no longer remind the user about configuration options that have
17715 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
17716 - Remove our old, non-weighted bandwidth-based node selection code.
17717 Previously, we used it as a fallback when we couldn't perform
17718 weighted bandwidth-based node selection. But that would only
17719 happen in the cases where we had no consensus, or when we had a
17720 consensus generated by buggy or ancient directory authorities. In
17721 either case, it's better to use the more modern, better maintained
17722 algorithm, with reasonable defaults for the weights. Closes
17724 - Remove the --disable-curve25519 configure option. Relays and
17725 clients now are required to support curve25519 and the
17727 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
17728 used to be deprecated synonyms for "StrictNodes", are now marked
17729 obsolete. Resolves ticket 12226.
17730 - Clients don't understand the BadDirectory flag in the consensus
17731 anymore, and ignore it.
17734 - Refactor the function that chooses guard nodes so that it can more
17735 easily be tested; write some tests for it.
17736 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
17737 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
17738 - Create unit tests for format_time_interval(). With bug 13393.
17739 - Add unit tests for tor_timegm signed overflow, tor_timegm and
17740 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
17741 tests (visible) fixes in bug 13476.
17742 - Add a "coverage-html" make target to generate HTML-visualized
17743 coverage results when building with --enable-coverage. (Requires
17744 lcov.) Patch from Kevin Murray.
17745 - Enable the backtrace handler (where supported) when running the
17747 - Revise all unit tests that used the legacy test_* macros to
17748 instead use the recommended tt_* macros. This patch was generated
17749 with coccinelle, to avoid manual errors. Closes ticket 13119.
17751 o Distribution (systemd):
17752 - systemd unit file: only allow tor to write to /var/lib/tor and
17753 /var/log/tor. The rest of the filesystem is accessible for reading
17754 only. Patch by intrigeri; resolves ticket 12751.
17755 - systemd unit file: ensure that the process and all its children
17756 can never gain new privileges. Patch by intrigeri; resolves
17758 - systemd unit file: set up /var/run/tor as writable for the Tor
17759 service. Patch by intrigeri; resolves ticket 13196.
17761 o Removed features (directory authorities):
17762 - Remove code that prevented authorities from listing Tor relays
17763 affected by CVE-2011-2769 as guards. These relays are already
17764 rejected altogether due to the minimum version requirement of
17765 0.2.3.16-alpha. Closes ticket 13152.
17766 - The "AuthDirRejectUnlisted" option no longer has any effect, as
17767 the fingerprints file (approved-routers) has been deprecated.
17768 - Directory authorities do not support being Naming dirauths anymore.
17769 The "NamingAuthoritativeDir" config option is now obsolete.
17770 - Directory authorities do not support giving out the BadDirectory
17772 - Directory authorities no longer advertise or support consensus
17773 methods 1 through 12 inclusive. These consensus methods were
17774 obsolete and/or insecure: maintaining the ability to support them
17775 served no good purpose. Implements part of proposal 215; closes
17778 o Testing (test-network.sh):
17779 - Stop using "echo -n", as some shells' built-in echo doesn't
17780 support "-n". Instead, use "/bin/echo -n". Partially fixes
17782 - Stop an apparent test-network hang when used with make -j2. Fixes
17784 - Add a --delay option to test-network.sh, which configures the
17785 delay before the chutney network tests for data transmission.
17786 Partially implements ticket 13161.
17789 Changes in version 0.2.5.10 - 2014-10-24
17790 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
17792 It adds several new security features, including improved
17793 denial-of-service resistance for relays, new compiler hardening
17794 options, and a system-call sandbox for hardened installations on Linux
17795 (requires seccomp2). The controller protocol has several new features,
17796 resolving IPv6 addresses should work better than before, and relays
17797 should be a little more CPU-efficient. We've added support for more
17798 OpenBSD and FreeBSD transparent proxy types. We've improved the build
17799 system and testing infrastructure to allow unit testing of more parts
17800 of the Tor codebase. Finally, we've addressed several nagging pluggable
17801 transport usability issues, and included numerous other small bugfixes
17802 and features mentioned below.
17804 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
17805 have accumulated many known flaws; everyone should upgrade.
17807 o Deprecated versions:
17808 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
17809 attention for some while.
17812 Changes in version 0.2.5.9-rc - 2014-10-20
17813 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
17814 series. It disables SSL3 in response to the recent "POODLE" attack
17815 (even though POODLE does not affect Tor). It also works around a crash
17816 bug caused by some operating systems' response to the "POODLE" attack
17817 (which does affect Tor). It also contains a few miscellaneous fixes.
17819 o Major security fixes:
17820 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17821 today support TLS 1.0 or later, so we can safely turn off support
17822 for this old (and insecure) protocol. Fixes bug 13426.
17824 o Major bugfixes (openssl bug workaround):
17825 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
17826 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
17827 13471. This is a workaround for an OpenSSL bug.
17830 - Disable the sandbox name resolver cache when running tor-resolve:
17831 tor-resolve doesn't use the sandbox code, and turning it on was
17832 breaking attempts to do tor-resolve on a non-default server on
17833 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
17835 o Compilation fixes:
17836 - Build and run correctly on systems like OpenBSD-current that have
17837 patched OpenSSL to remove get_cipher_by_char and/or its
17838 implementations. Fixes issue 13325.
17840 o Downgraded warnings:
17841 - Downgrade the severity of the 'unexpected sendme cell from client'
17842 from 'warn' to 'protocol warning'. Closes ticket 8093.
17845 Changes in version 0.2.4.25 - 2014-10-20
17846 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
17847 (even though POODLE does not affect Tor). It also works around a crash
17848 bug caused by some operating systems' response to the "POODLE" attack
17849 (which does affect Tor).
17851 o Major security fixes (also in 0.2.5.9-rc):
17852 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17853 today support TLS 1.0 or later, so we can safely turn off support
17854 for this old (and insecure) protocol. Fixes bug 13426.
17856 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
17857 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
17858 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
17859 13471. This is a workaround for an OpenSSL bug.
17862 Changes in version 0.2.5.8-rc - 2014-09-22
17863 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
17864 series. It fixes a bug that affects consistency and speed when
17865 connecting to hidden services, and it updates the location of one of
17866 the directory authorities.
17869 - Clients now send the correct address for their chosen rendezvous
17870 point when trying to access a hidden service. They used to send
17871 the wrong address, which would still work some of the time because
17872 they also sent the identity digest of the rendezvous point, and if
17873 the hidden service happened to try connecting to the rendezvous
17874 point from a relay that already had a connection open to it,
17875 the relay would reuse that connection. Now connections to hidden
17876 services should be more robust and faster. Also, this bug meant
17877 that clients were leaking to the hidden service whether they were
17878 on a little-endian (common) or big-endian (rare) system, which for
17879 some users might have reduced their anonymity. Fixes bug 13151;
17880 bugfix on 0.2.1.5-alpha.
17882 o Directory authority changes:
17883 - Change IP address for gabelmoo (v3 directory authority).
17886 Changes in version 0.2.4.24 - 2014-09-22
17887 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
17888 connecting to hidden services, and it updates the location of one of
17889 the directory authorities.
17892 - Clients now send the correct address for their chosen rendezvous
17893 point when trying to access a hidden service. They used to send
17894 the wrong address, which would still work some of the time because
17895 they also sent the identity digest of the rendezvous point, and if
17896 the hidden service happened to try connecting to the rendezvous
17897 point from a relay that already had a connection open to it,
17898 the relay would reuse that connection. Now connections to hidden
17899 services should be more robust and faster. Also, this bug meant
17900 that clients were leaking to the hidden service whether they were
17901 on a little-endian (common) or big-endian (rare) system, which for
17902 some users might have reduced their anonymity. Fixes bug 13151;
17903 bugfix on 0.2.1.5-alpha.
17905 o Directory authority changes:
17906 - Change IP address for gabelmoo (v3 directory authority).
17908 o Minor features (geoip):
17909 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17913 Changes in version 0.2.5.7-rc - 2014-09-11
17914 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
17915 release series, and some long-standing bugs related to ORPort reachability
17916 testing and failure to send CREATE cells. It is the first release
17917 candidate for the Tor 0.2.5.x series.
17919 o Major bugfixes (client, startup):
17920 - Start making circuits as soon as DisabledNetwork is turned off.
17921 When Tor started with DisabledNetwork set, it would correctly
17922 conclude that it shouldn't build circuits, but it would mistakenly
17923 cache this conclusion, and continue believing it even when
17924 DisableNetwork is set to 0. Fixes the bug introduced by the fix
17925 for bug 11200; bugfix on 0.2.5.4-alpha.
17926 - Resume expanding abbreviations for command-line options. The fix
17927 for bug 4647 accidentally removed our hack from bug 586 that
17928 rewrote HashedControlPassword to __HashedControlSessionPassword
17929 when it appears on the commandline (which allowed the user to set
17930 her own HashedControlPassword in the torrc file while the
17931 controller generates a fresh session password for each run). Fixes
17932 bug 12948; bugfix on 0.2.5.1-alpha.
17933 - Warn about attempts to run hidden services and relays in the same
17934 process: that's probably not a good idea. Closes ticket 12908.
17936 o Major bugfixes (relay):
17937 - Avoid queuing or sending destroy cells for circuit ID zero when we
17938 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
17939 Found and fixed by "cypherpunks".
17940 - Fix ORPort reachability detection on relays running behind a
17941 proxy, by correctly updating the "local" mark on the controlling
17942 channel when changing the address of an or_connection_t after the
17943 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
17945 o Minor features (bridge):
17946 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
17947 cookie file for the ExtORPort g+r by default.
17949 o Minor features (geoip):
17950 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17953 o Minor bugfixes (logging):
17954 - Reduce the log severity of the "Pluggable transport proxy does not
17955 provide any needed transports and will not be launched." message,
17956 since Tor Browser includes several ClientTransportPlugin lines in
17957 its torrc-defaults file, leading every Tor Browser user who looks
17958 at her logs to see these notices and wonder if they're dangerous.
17959 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
17960 - Downgrade "Unexpected onionskin length after decryption" warning
17961 to a protocol-warn, since there's nothing relay operators can do
17962 about a client that sends them a malformed create cell. Resolves
17963 bug 12996; bugfix on 0.0.6rc1.
17964 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
17965 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
17966 - When logging information about an EXTEND2 or EXTENDED2 cell, log
17967 their names correctly. Fixes part of bug 12700; bugfix
17969 - When logging information about a relay cell whose command we don't
17970 recognize, log its command as an integer. Fixes part of bug 12700;
17971 bugfix on 0.2.1.10-alpha.
17972 - Escape all strings from the directory connection before logging
17973 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
17975 o Minor bugfixes (controller):
17976 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
17977 bug 12864; bugfix on 0.2.5.1-alpha.
17978 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
17979 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
17982 o Minor bugfixes (compilation):
17983 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
17984 bugfix on 0.2.5.5-alpha.
17985 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
17986 0.2.5.1-alpha. Patch from "NewEraCracker".
17987 - In routerlist_assert_ok(), don't take the address of a
17988 routerinfo's cache_info member unless that routerinfo is non-NULL.
17989 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
17990 - Fix a large number of false positive warnings from the clang
17991 analyzer static analysis tool. This should make real warnings
17992 easier for clang analyzer to find. Patch from "teor". Closes
17995 o Distribution (systemd):
17996 - Verify configuration file via ExecStartPre in the systemd unit
17997 file. Patch from intrigeri; resolves ticket 12730.
17998 - Explicitly disable RunAsDaemon in the systemd unit file. Our
17999 current systemd unit uses "Type = simple", so systemd does not
18000 expect tor to fork. If the user has "RunAsDaemon 1" in their
18001 torrc, then things won't work as expected. This is e.g. the case
18002 on Debian (and derivatives), since there we pass "--defaults-torrc
18003 /usr/share/tor/tor-service-defaults-torrc" (that contains
18004 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
18008 - Adjust the URLs in the README to refer to the new locations of
18009 several documents on the website. Fixes bug 12830. Patch from
18011 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
18015 Changes in version 0.2.5.6-alpha - 2014-07-28
18016 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
18017 risk from guard rotation, and fixes a variety of other issues to get
18018 us closer to a release candidate.
18020 o Major features (also in 0.2.4.23):
18021 - Make the number of entry guards configurable via a new
18022 NumEntryGuards consensus parameter, and the number of directory
18023 guards configurable via a new NumDirectoryGuards consensus
18024 parameter. Implements ticket 12688.
18026 o Major bugfixes (also in 0.2.4.23):
18027 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18028 implementation that caused incorrect results on 32-bit
18029 implementations when certain malformed inputs were used along with
18030 a small class of private ntor keys. This bug does not currently
18031 appear to allow an attacker to learn private keys or impersonate a
18032 Tor server, but it could provide a means to distinguish 32-bit Tor
18033 implementations from 64-bit Tor implementations. Fixes bug 12694;
18034 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18038 - Perform circuit cleanup operations even when circuit
18039 construction operations are disabled (because the network is
18040 disabled, or because there isn't enough directory information).
18041 Previously, when we were not building predictive circuits, we
18042 were not closing expired circuits either. Fixes bug 8387; bugfix on
18043 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
18044 became more strict about when we have "enough directory information
18045 to build circuits".
18048 - Authorities now assign the Guard flag to the fastest 25% of the
18049 network (it used to be the fastest 50%). Also raise the consensus
18050 weight that guarantees the Guard flag from 250 to 2000. For the
18051 current network, this results in about 1100 guards, down from 2500.
18052 This step paves the way for moving the number of entry guards
18053 down to 1 (proposal 236) while still providing reasonable expected
18054 performance for most users. Implements ticket 12690.
18055 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18057 - Slightly enhance the diagnostic message for bug 12184.
18059 o Minor bugfixes (also in 0.2.4.23):
18060 - Warn and drop the circuit if we receive an inbound 'relay early'
18061 cell. Those used to be normal to receive on hidden service circuits
18062 due to bug 1038, but the buggy Tor versions are long gone from
18063 the network so we can afford to resume watching for them. Resolves
18064 the rest of bug 1038; bugfix on 0.2.1.19.
18065 - Correct a confusing error message when trying to extend a circuit
18066 via the control protocol but we don't know a descriptor or
18067 microdescriptor for one of the specified relays. Fixes bug 12718;
18068 bugfix on 0.2.3.1-alpha.
18071 - Fix compilation when building with bufferevents enabled. (This
18072 configuration is still not expected to work, however.)
18073 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
18074 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
18076 - Compile correctly with builds and forks of OpenSSL (such as
18077 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
18078 0.2.1.1-alpha. Patch from "dhill".
18081 Changes in version 0.2.4.23 - 2014-07-28
18082 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
18083 guard rotation, and also backports several important fixes from the
18084 Tor 0.2.5 alpha release series.
18087 - Clients now look at the "usecreatefast" consensus parameter to
18088 decide whether to use CREATE_FAST or CREATE cells for the first hop
18089 of their circuit. This approach can improve security on connections
18090 where Tor's circuit handshake is stronger than the available TLS
18091 connection security levels, but the tradeoff is more computational
18092 load on guard relays. Implements proposal 221. Resolves ticket 9386.
18093 - Make the number of entry guards configurable via a new
18094 NumEntryGuards consensus parameter, and the number of directory
18095 guards configurable via a new NumDirectoryGuards consensus
18096 parameter. Implements ticket 12688.
18099 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18100 implementation that caused incorrect results on 32-bit
18101 implementations when certain malformed inputs were used along with
18102 a small class of private ntor keys. This bug does not currently
18103 appear to allow an attacker to learn private keys or impersonate a
18104 Tor server, but it could provide a means to distinguish 32-bit Tor
18105 implementations from 64-bit Tor implementations. Fixes bug 12694;
18106 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18110 - Warn and drop the circuit if we receive an inbound 'relay early'
18111 cell. Those used to be normal to receive on hidden service circuits
18112 due to bug 1038, but the buggy Tor versions are long gone from
18113 the network so we can afford to resume watching for them. Resolves
18114 the rest of bug 1038; bugfix on 0.2.1.19.
18115 - Correct a confusing error message when trying to extend a circuit
18116 via the control protocol but we don't know a descriptor or
18117 microdescriptor for one of the specified relays. Fixes bug 12718;
18118 bugfix on 0.2.3.1-alpha.
18119 - Avoid an illegal read from stack when initializing the TLS
18120 module using a version of OpenSSL without all of the ciphers
18121 used by the v2 link handshake. Fixes bug 12227; bugfix on
18122 0.2.4.8-alpha. Found by "starlight".
18125 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18129 Changes in version 0.2.5.5-alpha - 2014-06-18
18130 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
18131 0.2.5.x release series, including a couple of DoS issues, some
18132 performance regressions, a large number of bugs affecting the Linux
18133 seccomp2 sandbox code, and various other bugfixes. It also adds
18134 diagnostic bugfixes for a few tricky issues that we're trying to
18137 o Major features (security, traffic analysis resistance):
18138 - Several major improvements to the algorithm used to decide when to
18139 close TLS connections. Previous versions of Tor closed connections
18140 at a fixed interval after the last time a non-padding cell was
18141 sent over the connection, regardless of the target of the
18142 connection. Now, we randomize the intervals by adding up to 50% of
18143 their base value, we measure the length of time since connection
18144 last had at least one circuit, and we allow connections to known
18145 ORs to remain open a little longer (15 minutes instead of 3
18146 minutes minimum). These changes should improve Tor's resistance
18147 against some kinds of traffic analysis, and lower some overhead
18148 from needlessly closed connections. Fixes ticket 6799.
18149 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
18151 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
18152 - Fix a memory leak that could occur if a microdescriptor parse
18153 fails during the tokenizing step. This bug could enable a memory
18154 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18157 o Major bugfixes (security, directory authorities):
18158 - Directory authorities now include a digest of each relay's
18159 identity key as a part of its microdescriptor.
18161 This is a workaround for bug 11743 (reported by "cypherpunks"),
18162 where Tor clients do not support receiving multiple
18163 microdescriptors with the same SHA256 digest in the same
18164 consensus. When clients receive a consensus like this, they only
18165 use one of the relays. Without this fix, a hostile relay could
18166 selectively disable some client use of target relays by
18167 constructing a router descriptor with a different identity and the
18168 same microdescriptor parameters and getting the authorities to
18169 list it in a microdescriptor consensus. This fix prevents an
18170 attacker from causing a microdescriptor collision, because the
18171 router's identity is not forgeable.
18173 o Major bugfixes (relay):
18174 - Use a direct dirport connection when uploading non-anonymous
18175 descriptors to the directory authorities. Previously, relays would
18176 incorrectly use tunnel connections under a fairly wide variety of
18177 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
18178 - When a circuit accidentally has the same circuit ID for its
18179 forward and reverse direction, correctly detect the direction of
18180 cells using that circuit. Previously, this bug made roughly one
18181 circuit in a million non-functional. Fixes bug 12195; this is a
18182 bugfix on every version of Tor.
18184 o Major bugfixes (client, pluggable transports):
18185 - When managing pluggable transports, use OS notification facilities
18186 to learn if they have crashed, and don't attempt to kill any
18187 process that has already exited. Fixes bug 8746; bugfix
18190 o Minor features (diagnostic):
18191 - When logging a warning because of bug 7164, additionally check the
18192 hash table for consistency (as proposed on ticket 11737). This may
18193 help diagnose bug 7164.
18194 - When we log a heartbeat, log how many one-hop circuits we have
18195 that are at least 30 minutes old, and log status information about
18196 a few of them. This is an attempt to track down bug 8387.
18197 - When encountering an unexpected CR while writing text to a file on
18198 Windows, log the name of the file. Should help diagnosing
18200 - Give more specific warnings when a client notices that an onion
18201 handshake has failed. Fixes ticket 9635.
18202 - Add significant new logging code to attempt to diagnose bug 12184,
18203 where relays seem to run out of available circuit IDs.
18204 - Improve the diagnostic log message for bug 8387 even further to
18205 try to improve our odds of figuring out why one-hop directory
18206 circuits sometimes do not get closed.
18208 o Minor features (security, memory management):
18209 - Memory allocation tricks (mempools and buffer freelists) are now
18210 disabled by default. You can turn them back on with
18211 --enable-mempools and --enable-buf-freelists respectively. We're
18212 disabling these features because malloc performance is good enough
18213 on most platforms, and a similar feature in OpenSSL exacerbated
18214 exploitation of the Heartbleed attack. Resolves ticket 11476.
18216 o Minor features (security):
18217 - Apply the secure SipHash-2-4 function to the hash table mapping
18218 circuit IDs and channels to circuits. We missed this one when we
18219 were converting all the other hash functions to use SipHash back
18220 in 0.2.5.3-alpha. Resolves ticket 11750.
18222 o Minor features (build):
18223 - The configure script has a --disable-seccomp option to turn off
18224 support for libseccomp on systems that have it, in case it (or
18225 Tor's use of it) is broken. Resolves ticket 11628.
18227 o Minor features (other):
18228 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
18231 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
18232 - When running a hidden service, do not allow TunneledDirConns 0;
18233 this will keep the hidden service from running, and also
18234 make it publish its descriptors directly over HTTP. Fixes bug 10849;
18235 bugfix on 0.2.1.1-alpha.
18237 o Minor bugfixes (performance):
18238 - Avoid a bug where every successful connection made us recompute
18239 the flag telling us whether we have sufficient information to
18240 build circuits. Previously, we would forget our cached value
18241 whenever we successfully opened a channel (or marked a router as
18242 running or not running for any other reason), regardless of
18243 whether we had previously believed the router to be running. This
18244 forced us to run an expensive update operation far too often.
18245 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
18246 - Avoid using tor_memeq() for checking relay cell integrity. This
18247 removes a possible performance bottleneck. Fixes part of bug
18248 12169; bugfix on 0.2.1.31.
18250 o Minor bugfixes (compilation):
18251 - Fix compilation of test_status.c when building with MVSC. Bugfix
18252 on 0.2.5.4-alpha. Patch from Gisle Vanem.
18253 - Resolve GCC complaints on OpenBSD about discarding constness in
18254 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
18255 on 0.1.1.23. Patch from Dana Koch.
18256 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
18257 treatment of long and time_t as comparable types. Fixes part of
18258 bug 11633. Patch from Dana Koch.
18259 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
18260 11623; bugfix on 0.2.5.3-alpha.
18261 - When deciding whether to build the 64-bit curve25519
18262 implementation, detect platforms where we can compile 128-bit
18263 arithmetic but cannot link it. Fixes bug 11729; bugfix on
18264 0.2.4.8-alpha. Patch from "conradev".
18265 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
18266 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
18267 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
18270 o Minor bugfixes (Directory server):
18271 - When sending a compressed set of descriptors or microdescriptors,
18272 make sure to finalize the zlib stream. Previously, we would write
18273 all the compressed data, but if the last descriptor we wanted to
18274 send was missing or too old, we would not mark the stream as
18275 finished. This caused problems for decompression tools. Fixes bug
18276 11648; bugfix on 0.1.1.23.
18278 o Minor bugfixes (Linux seccomp sandbox):
18279 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
18280 11622; bugfix on 0.2.5.1-alpha.
18281 - Avoid crashing when re-opening listener ports with the seccomp
18282 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
18283 - Avoid crashing with the seccomp sandbox enabled along with
18284 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
18285 - When we receive a SIGHUP with the sandbox enabled, correctly
18286 support rotating our log files. Fixes bug 12032; bugfix
18288 - Avoid crash when running with sandboxing enabled and
18289 DirReqStatistics not disabled. Fixes bug 12035; bugfix
18291 - Fix a "BUG" warning when trying to write bridge-stats files with
18292 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
18294 - Prevent the sandbox from crashing on startup when run with the
18295 --enable-expensive-hardening configuration option. Fixes bug
18296 11477; bugfix on 0.2.5.4-alpha.
18297 - When running with DirPortFrontPage and sandboxing both enabled,
18298 reload the DirPortFrontPage correctly when restarting. Fixes bug
18299 12028; bugfix on 0.2.5.1-alpha.
18300 - Don't try to enable the sandbox when using the Tor binary to check
18301 its configuration, hash a passphrase, or so on. Doing so was
18302 crashing on startup for some users. Fixes bug 11609; bugfix
18304 - Avoid warnings when running with sandboxing and node statistics
18305 enabled at the same time. Fixes part of 12064; bugfix on
18306 0.2.5.1-alpha. Patch from Michael Wolf.
18307 - Avoid warnings when running with sandboxing enabled at the same
18308 time as cookie authentication, hidden services, or directory
18309 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
18310 - Do not allow options that require calls to exec to be enabled
18311 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
18312 bug 12043; bugfix on 0.2.5.1-alpha.
18313 - Handle failures in getpwnam()/getpwuid() when running with the
18314 User option set and the Linux syscall sandbox enabled. Fixes bug
18315 11946; bugfix on 0.2.5.1-alpha.
18316 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
18317 to avoid calling getaddrinfo() after installing the sandbox
18318 filters. Previously, it preloaded a cache with the IPv4 address
18319 for our hostname, and nothing else. Now, it loads the cache with
18320 every address that it used to initialize the Tor process. Fixes
18321 bug 11970; bugfix on 0.2.5.1-alpha.
18323 o Minor bugfixes (pluggable transports):
18324 - Enable the ExtORPortCookieAuthFile option, to allow changing the
18325 default location of the authentication token for the extended OR
18326 Port as used by sever-side pluggable transports. We had
18327 implemented this option before, but the code to make it settable
18328 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
18329 - Avoid another 60-second delay when starting Tor in a pluggable-
18330 transport-using configuration when we already have cached
18331 descriptors for our bridges. Fixes bug 11965; bugfix
18334 o Minor bugfixes (client):
18335 - Avoid "Tried to open a socket with DisableNetwork set" warnings
18336 when starting a client with bridges configured and DisableNetwork
18337 set. (Tor launcher starts Tor with DisableNetwork set the first
18338 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
18340 o Minor bugfixes (testing):
18341 - The Python parts of the test scripts now work on Python 3 as well
18342 as Python 2, so systems where '/usr/bin/python' is Python 3 will
18343 no longer have the tests break. Fixes bug 11608; bugfix
18345 - When looking for versions of python that we could run the tests
18346 with, check for "python2.7" and "python3.3"; previously we were
18347 only looking for "python", "python2", and "python3". Patch from
18348 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
18349 - Fix all valgrind warnings produced by the unit tests. There were
18350 over a thousand memory leak warnings previously, mostly produced
18351 by forgetting to free things in the unit test code. Fixes bug
18352 11618, bugfixes on many versions of Tor.
18354 o Minor bugfixes (tor-fw-helper):
18355 - Give a correct log message when tor-fw-helper fails to launch.
18356 (Previously, we would say something like "tor-fw-helper sent us a
18357 string we could not parse".) Fixes bug 9781; bugfix
18360 o Minor bugfixes (relay, threading):
18361 - Check return code on spawn_func() in cpuworker code, so that we
18362 don't think we've spawned a nonworking cpuworker and write junk to
18363 it forever. Fix related to bug 4345; bugfix on all released Tor
18364 versions. Found by "skruffy".
18365 - Use a pthread_attr to make sure that spawn_func() cannot return an
18366 error while at the same time launching a thread. Fix related to
18367 bug 4345; bugfix on all released Tor versions. Reported
18370 o Minor bugfixes (relay, oom prevention):
18371 - Correctly detect the total available system memory. We tried to do
18372 this in 0.2.5.4-alpha, but the code was set up to always return an
18373 error value, even on success. Fixes bug 11805; bugfix
18376 o Minor bugfixes (relay, other):
18377 - We now drop CREATE cells for already-existent circuit IDs and for
18378 zero-valued circuit IDs, regardless of other factors that might
18379 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
18381 - Avoid an illegal read from stack when initializing the TLS module
18382 using a version of OpenSSL without all of the ciphers used by the
18383 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
18385 - When rejecting DATA cells for stream_id zero, still count them
18386 against the circuit's deliver window so that we don't fail to send
18387 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
18389 o Minor bugfixes (logging):
18390 - Fix a misformatted log message about delayed directory fetches.
18391 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
18392 - Squelch a spurious LD_BUG message "No origin circuit for
18393 successful SOCKS stream" in certain hidden service failure cases;
18397 - Include a tor.service file in contrib/dist for use with systemd.
18398 Some distributions will be able to use this file unmodified;
18399 others will need to tweak it, or write their own. Patch from Jamie
18400 Nguyen; resolves ticket 8368.
18403 - Clean up several option names in the manpage to match their real
18404 names, add the missing documentation for a couple of testing and
18405 directory authority options, remove the documentation for a
18406 V2-directory fetching option that no longer exists. Resolves
18408 - Correct the documentation so that it lists the correct directory
18409 for the stats files. (They are in a subdirectory called "stats",
18411 - In the manpage, move more authority-only options into the
18412 directory authority section so that operators of regular directory
18413 caches don't get confused.
18416 - The contrib directory has been sorted and tidied. Before, it was
18417 an unsorted dumping ground for useful and not-so-useful things.
18418 Now, it is divided based on functionality, and the items which
18419 seemed to be nonfunctional or useless have been removed. Resolves
18420 ticket 8966; based on patches from "rl1987".
18423 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
18424 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
18425 - The TunnelDirConns and PreferTunnelledDirConns options no longer
18426 exist; tunneled directory connections have been available since
18427 0.1.2.5-alpha, and turning them off is not a good idea. This is a
18428 brute-force fix for 10849, where "TunnelDirConns 0" would break
18432 Changes in version 0.2.4.22 - 2014-05-16
18433 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
18434 alpha release series. These include blocking all authority signing
18435 keys that may have been affected by the OpenSSL "heartbleed" bug,
18436 choosing a far more secure set of TLS ciphersuites by default, closing
18437 a couple of memory leaks that could be used to run a target relay out
18438 of RAM, and several others.
18440 o Major features (security, backport from 0.2.5.4-alpha):
18441 - Block authority signing keys that were used on authorities
18442 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18443 don't have any evidence that these keys _were_ compromised; we're
18444 doing this to be prudent.) Resolves ticket 11464.
18446 o Major bugfixes (security, OOM):
18447 - Fix a memory leak that could occur if a microdescriptor parse
18448 fails during the tokenizing step. This bug could enable a memory
18449 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18452 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
18453 - The relay ciphersuite list is now generated automatically based on
18454 uniform criteria, and includes all OpenSSL ciphersuites with
18455 acceptable strength and forward secrecy. Previously, we had left
18456 some perfectly fine ciphersuites unsupported due to omission or
18457 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18458 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18459 - Relays now trust themselves to have a better view than clients of
18460 which TLS ciphersuites are better than others. (Thanks to bug
18461 11513, the relay list is now well-considered, whereas the client
18462 list has been chosen mainly for anti-fingerprinting purposes.)
18463 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18464 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18465 AES128. Resolves ticket 11528.
18466 - Clients now try to advertise the same list of ciphersuites as
18467 Firefox 28. This change enables selection of (fast) GCM
18468 ciphersuites, disables some strange old ciphers, and stops
18469 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18470 Resolves ticket 11438.
18472 o Minor bugfixes (configuration, security):
18473 - When running a hidden service, do not allow TunneledDirConns 0:
18474 trying to set that option together with a hidden service would
18475 otherwise prevent the hidden service from running, and also make
18476 it publish its descriptors directly over HTTP. Fixes bug 10849;
18477 bugfix on 0.2.1.1-alpha.
18479 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
18480 - Avoid sending a garbage value to the controller when a circuit is
18481 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18483 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
18484 - Stop leaking memory when we successfully resolve a PTR record.
18485 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18487 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
18488 - Avoid 60-second delays in the bootstrapping process when Tor is
18489 launching for a second time while using bridges. Fixes bug 9229;
18490 bugfix on 0.2.0.3-alpha.
18492 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
18493 - Give the correct URL in the warning message when trying to run a
18494 relay on an ancient version of Windows. Fixes bug 9393.
18496 o Minor bugfixes (compilation):
18497 - Fix a compilation error when compiling with --disable-curve25519.
18498 Fixes bug 9700; bugfix on 0.2.4.17-rc.
18501 - Downgrade the warning severity for the the "md was still
18502 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
18503 for trying to diagnose this bug, and the current warning in
18504 earlier versions of tor achieves nothing useful. Addresses warning
18507 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
18508 - When we run out of usable circuit IDs on a channel, log only one
18509 warning for the whole channel, and describe how many circuits
18510 there were on the channel. Fixes part of ticket 11553.
18512 o Minor features (security, backport from 0.2.5.4-alpha):
18513 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
18514 leave the default at 8GBytes), to better support Raspberry Pi
18515 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
18517 o Documentation (backport from 0.2.5.4-alpha):
18518 - Correctly document that we search for a system torrc file before
18519 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18523 Changes in version 0.2.5.4-alpha - 2014-04-25
18524 Tor 0.2.5.4-alpha includes several security and performance
18525 improvements for clients and relays, including blacklisting authority
18526 signing keys that were used while susceptible to the OpenSSL
18527 "heartbleed" bug, fixing two expensive functions on busy relays,
18528 improved TLS ciphersuite preference lists, support for run-time
18529 hardening on compilers that support AddressSanitizer, and more work on
18530 the Linux sandbox code.
18532 There are also several usability fixes for clients (especially clients
18533 that use bridges), two new TransPort protocols supported (one on
18534 OpenBSD, one on FreeBSD), and various other bugfixes.
18536 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
18537 have accumulated many known flaws; everyone should upgrade.
18539 o Major features (security):
18540 - If you don't specify MaxMemInQueues yourself, Tor now tries to
18541 pick a good value based on your total system memory. Previously,
18542 the default was always 8 GB. You can still override the default by
18543 setting MaxMemInQueues yourself. Resolves ticket 11396.
18544 - Block authority signing keys that were used on authorities
18545 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18546 don't have any evidence that these keys _were_ compromised; we're
18547 doing this to be prudent.) Resolves ticket 11464.
18549 o Major features (relay performance):
18550 - Speed up server-side lookups of rendezvous and introduction point
18551 circuits by using hashtables instead of linear searches. These
18552 functions previously accounted between 3 and 7% of CPU usage on
18553 some busy relays. Resolves ticket 9841.
18554 - Avoid wasting CPU when extending a circuit over a channel that is
18555 nearly out of circuit IDs. Previously, we would do a linear scan
18556 over possible circuit IDs before finding one or deciding that we
18557 had exhausted our possibilities. Now, we try at most 64 random
18558 circuit IDs before deciding that we probably won't succeed. Fixes
18559 a possible root cause of ticket 11553.
18561 o Major features (seccomp2 sandbox, Linux only):
18562 - The seccomp2 sandbox can now run a test network for multiple hours
18563 without crashing. The sandbox is still experimental, and more bugs
18564 will probably turn up. To try it, enable "Sandbox 1" on a Linux
18565 host. Resolves ticket 11351.
18566 - Strengthen sandbox code: the sandbox can now test the arguments
18567 for rename(), and blocks _sysctl() entirely. Resolves another part
18569 - When the sandbox blocks a system call, it now tries to log a stack
18570 trace before exiting. Resolves ticket 11465.
18572 o Major bugfixes (TLS cipher selection):
18573 - The relay ciphersuite list is now generated automatically based on
18574 uniform criteria, and includes all OpenSSL ciphersuites with
18575 acceptable strength and forward secrecy. Previously, we had left
18576 some perfectly fine ciphersuites unsupported due to omission or
18577 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18578 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18579 - Relays now trust themselves to have a better view than clients of
18580 which TLS ciphersuites are better than others. (Thanks to bug
18581 11513, the relay list is now well-considered, whereas the client
18582 list has been chosen mainly for anti-fingerprinting purposes.)
18583 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18584 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18585 AES128. Resolves ticket 11528.
18586 - Clients now try to advertise the same list of ciphersuites as
18587 Firefox 28. This change enables selection of (fast) GCM
18588 ciphersuites, disables some strange old ciphers, and stops
18589 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18590 Resolves ticket 11438.
18592 o Major bugfixes (bridge client):
18593 - Avoid 60-second delays in the bootstrapping process when Tor is
18594 launching for a second time while using bridges. Fixes bug 9229;
18595 bugfix on 0.2.0.3-alpha.
18597 o Minor features (transparent proxy, *BSD):
18598 - Support FreeBSD's ipfw firewall interface for TransPort ports on
18599 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
18600 10267; patch from "yurivict".
18601 - Support OpenBSD's divert-to rules with the pf firewall for
18602 transparent proxy ports. To enable it, set "TransProxyType
18603 pf-divert". This allows Tor to run a TransPort transparent proxy
18604 port on OpenBSD 4.4 or later without root privileges. See the
18605 pf.conf(5) manual page for information on configuring pf to use
18606 divert-to rules. Closes ticket 10896; patch from Dana Koch.
18608 o Minor features (security):
18609 - New --enable-expensive-hardening option to enable security
18610 hardening options that consume nontrivial amounts of CPU and
18611 memory. Right now, this includes AddressSanitizer and UbSan, which
18612 are supported in newer versions of GCC and Clang. Closes ticket
18615 o Minor features (log verbosity):
18616 - Demote the message that we give when a flushing connection times
18617 out for too long from NOTICE to INFO. It was usually meaningless.
18618 Resolves ticket 5286.
18619 - Don't log so many notice-level bootstrapping messages at startup
18620 about downloading descriptors. Previously, we'd log a notice
18621 whenever we learned about more routers. Now, we only log a notice
18622 at every 5% of progress. Fixes bug 9963.
18623 - Warn less verbosely when receiving a malformed
18624 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
18625 - When we run out of usable circuit IDs on a channel, log only one
18626 warning for the whole channel, and describe how many circuits
18627 there were on the channel. Fixes part of ticket 11553.
18629 o Minor features (relay):
18630 - If a circuit timed out for at least 3 minutes, check if we have a
18631 new external IP address, and publish a new descriptor with the new
18632 IP address if it changed. Resolves ticket 2454.
18634 o Minor features (controller):
18635 - Make the entire exit policy available from the control port via
18636 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
18638 - Because of the fix for ticket 11396, the real limit for memory
18639 usage may no longer match the configured MaxMemInQueues value. The
18640 real limit is now exposed via GETINFO limits/max-mem-in-queues.
18642 o Minor features (bridge client):
18643 - Report a more useful failure message when we can't connect to a
18644 bridge because we don't have the right pluggable transport
18645 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
18647 o Minor features (diagnostic):
18648 - Add more log messages to diagnose bug 7164, which causes
18649 intermittent "microdesc_free() called but md was still referenced"
18650 warnings. We now include more information, to figure out why we
18651 might be cleaning a microdescriptor for being too old if it's
18652 still referenced by a live node_t object.
18654 o Minor bugfixes (client, DNSPort):
18655 - When using DNSPort, try to respond to AAAA requests with AAAA
18656 answers. Previously, we hadn't looked at the request type when
18657 deciding which answer type to prefer. Fixes bug 10468; bugfix on
18659 - When receiving a DNS query for an unsupported record type, reply
18660 with no answer rather than with a NOTIMPL error. This behavior
18661 isn't correct either, but it will break fewer client programs, we
18662 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
18665 o Minor bugfixes (exit relay):
18666 - Stop leaking memory when we successfully resolve a PTR record.
18667 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18669 o Minor bugfixes (bridge client):
18670 - Stop accepting bridge lines containing hostnames. Doing so would
18671 cause clients to perform DNS requests on the hostnames, which was
18672 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
18673 - Avoid a 60-second delay in the bootstrapping process when a Tor
18674 client with pluggable transports re-reads its configuration at
18675 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
18677 o Minor bugfixes (client, logging during bootstrap):
18678 - Warn only once if we start logging in an unsafe way. Previously,
18679 we complain as many times as we had problems. Fixes bug 9870;
18680 bugfix on 0.2.5.1-alpha.
18681 - Only report the first fatal bootstrap error on a given OR
18682 connection. This stops us from telling the controller bogus error
18683 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
18684 - Be more helpful when trying to run sandboxed on Linux without
18685 libseccomp. Instead of saying "Sandbox is not implemented on this
18686 platform", we now explain that we need to be built with
18687 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
18688 - Avoid generating spurious warnings when starting with
18689 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
18692 o Minor bugfixes (closing OR connections):
18693 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
18694 check if it's an or_connection_t and correctly call
18695 connection_or_close_for_error() rather than
18696 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
18698 - When closing all connections on setting DisableNetwork to 1, use
18699 connection_or_close_normally() rather than closing OR connections
18700 out from under the channel layer. Fixes bug 11306; bugfix on
18703 o Minor bugfixes (controller):
18704 - Avoid sending a garbage value to the controller when a circuit is
18705 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18707 o Minor bugfixes (tor-fw-helper):
18708 - Allow tor-fw-helper to build again by adding src/ext to its
18709 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
18711 o Minor bugfixes (bridges):
18712 - Avoid potential crashes or bad behavior when launching a
18713 server-side managed proxy with ORPort or ExtORPort temporarily
18714 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
18716 o Minor bugfixes (platform-specific):
18717 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
18718 bug 11426; bugfix on 0.2.5.3-alpha.
18719 - When dumping a malformed directory object to disk, save it in
18720 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
18722 - Don't report failures from make_socket_reuseable() on incoming
18723 sockets on OSX: this can happen when incoming connections close
18724 early. Fixes bug 10081.
18726 o Minor bugfixes (trivial memory leaks):
18727 - Fix a small memory leak when signing a directory object. Fixes bug
18728 11275; bugfix on 0.2.4.13-alpha.
18729 - Free placeholder entries in our circuit table at exit; fixes a
18730 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
18731 - Don't re-initialize a second set of OpenSSL mutexes when starting
18732 up. Previously, we'd make one set of mutexes, and then immediately
18733 replace them with another. Fixes bug 11726; bugfix on
18735 - Resolve some memory leaks found by coverity in the unit tests, on
18736 exit in tor-gencert, and on a failure to compute digests for our
18737 own keys when generating a v3 networkstatus vote. These leaks
18738 should never have affected anyone in practice.
18740 o Minor bugfixes (hidden service):
18741 - Only retry attempts to connect to a chosen rendezvous point 8
18742 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
18744 o Minor bugfixes (misc code correctness):
18745 - Fix various instances of undefined behavior in channeltls.c,
18746 tor_memmem(), and eventdns.c that would cause us to construct
18747 pointers to memory outside an allocated object. (These invalid
18748 pointers were not accessed, but C does not even allow them to
18749 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
18750 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
18751 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
18752 fix some miscellaneous errors in our tests and codebase. Fixes bug
18753 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
18754 - Always check return values for unlink, munmap, UnmapViewOfFile;
18755 check strftime return values more often. In some cases all we can
18756 do is report a warning, but this may help prevent deeper bugs from
18757 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
18759 - Fix numerous warnings from the clang "scan-build" static analyzer.
18760 Some of these are programming style issues; some of them are false
18761 positives that indicated awkward code; some are undefined behavior
18762 cases related to constructing (but not using) invalid pointers;
18763 some are assumptions about API behavior; some are (harmlessly)
18764 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
18765 correct; and one or two are genuine bugs that weren't reachable
18766 from the rest of the program. Fixes bug 8793; bugfixes on many,
18770 - Build the torify.1 manpage again. Previously, we were only trying
18771 to build it when also building tor-fw-helper. That's why we didn't
18772 notice that we'd broken the ability to build it. Fixes bug 11321;
18773 bugfix on 0.2.5.1-alpha.
18774 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
18775 11061; bugfix on 0.2.4.7-alpha.
18776 - Correctly document that we search for a system torrc file before
18777 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18779 - Resolve warnings from Doxygen.
18781 o Code simplifications and refactoring:
18782 - Remove is_internal_IP() function. Resolves ticket 4645.
18783 - Remove unused function circuit_dump_by_chan from circuitlist.c.
18784 Closes issue 9107; patch from "marek".
18785 - Change our use of the ENUM_BF macro to avoid declarations that
18788 o Deprecated versions:
18789 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
18790 attention for some while. Directory authorities no longer accept
18791 descriptors from relays running any version of Tor prior to Tor
18792 0.2.3.16-alpha. Resolves ticket 11149.
18795 - New macros in test.h to simplify writing mock-functions for unit
18796 tests. Part of ticket 11507. Patch from Dana Koch.
18797 - Complete tests for the status.c module. Resolves ticket 11507.
18798 Patch from Dana Koch.
18801 - Remove all code for the long unused v1 directory protocol.
18802 Resolves ticket 11070.
18805 Changes in version 0.2.5.3-alpha - 2014-03-22
18806 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
18807 two new anti-DoS features for Tor relays, resolves a bug that kept
18808 SOCKS5 support for IPv6 from working, fixes several annoying usability
18809 issues for bridge users, and removes more old code for unused
18812 The Tor 0.2.5.x release series is now in patch-freeze: no feature
18813 patches not already written will be considered for inclusion in 0.2.5.x.
18815 o Major features (relay security, DoS-resistance):
18816 - When deciding whether we have run out of memory and we need to
18817 close circuits, also consider memory allocated in buffers for
18818 streams attached to each circuit.
18820 This change, which extends an anti-DoS feature introduced in
18821 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
18822 better resist more memory-based DoS attacks than before. Since the
18823 MaxMemInCellQueues option now applies to all queues, it is renamed
18824 to MaxMemInQueues. This feature fixes bug 10169.
18825 - Avoid hash-flooding denial-of-service attacks by using the secure
18826 SipHash-2-4 hash function for our hashtables. Without this
18827 feature, an attacker could degrade performance of a targeted
18828 client or server by flooding their data structures with a large
18829 number of entries to be stored at the same hash table position,
18830 thereby slowing down the Tor instance. With this feature, hash
18831 table positions are derived from a randomized cryptographic key,
18832 and an attacker cannot predict which entries will collide. Closes
18834 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
18835 the default at 8GBytes), to better support Raspberry Pi users. Fixes
18836 bug 9686; bugfix on 0.2.4.14-alpha.
18838 o Minor features (bridges, pluggable transports):
18839 - Bridges now write the SHA1 digest of their identity key
18840 fingerprint (that is, a hash of a hash of their public key) to
18841 notice-level logs, and to a new hashed-fingerprint file. This
18842 information will help bridge operators look up their bridge in
18843 Globe and similar tools. Resolves ticket 10884.
18844 - Improve the message that Tor displays when running as a bridge
18845 using pluggable transports without an Extended ORPort listener.
18846 Also, log the message in the log file too. Resolves ticket 11043.
18848 o Minor features (other):
18849 - Add a new option, PredictedPortsRelevanceTime, to control how long
18850 after having received a request to connect to a given port Tor
18851 will try to keep circuits ready in anticipation of future requests
18852 for that port. Patch from "unixninja92"; implements ticket 9176.
18853 - Generate a warning if any ports are listed in the SocksPolicy,
18854 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
18855 AuthDirBadExit options. (These options only support address
18856 ranges.) Fixes part of ticket 11108.
18857 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
18860 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
18861 - Build without warnings under clang 3.4. (We have some macros that
18862 define static functions only some of which will get used later in
18863 the module. Starting with clang 3.4, these give a warning unless the
18864 unused attribute is set on them.) Resolves ticket 10904.
18865 - Fix build warnings about missing "a2x" comment when building the
18866 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
18867 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
18869 o Minor bugfixes (client):
18870 - Improve the log message when we can't connect to a hidden service
18871 because all of the hidden service directory nodes hosting its
18872 descriptor are excluded. Improves on our fix for bug 10722, which
18873 was a bugfix on 0.2.0.10-alpha.
18874 - Raise a control port warning when we fail to connect to all of
18875 our bridges. Previously, we didn't inform the controller, and
18876 the bootstrap process would stall. Fixes bug 11069; bugfix on
18878 - Exit immediately when a process-owning controller exits.
18879 Previously, tor relays would wait for a little while after their
18880 controller exited, as if they had gotten an INT signal -- but this
18881 was problematic, since there was no feedback for the user. To do a
18882 clean shutdown, controllers should send an INT signal and give Tor
18883 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
18884 - Stop attempting to connect to bridges before our pluggable
18885 transports are configured (harmless but resulted in some erroneous
18886 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
18887 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
18888 generating incorrect SOCKS5 responses, and confusing client
18889 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
18891 o Minor bugfixes (relays and bridges):
18892 - Avoid crashing on a malformed resolv.conf file when running a
18893 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
18894 - Non-exit relays no longer launch mock DNS requests to check for
18895 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
18896 non-exit relays stopped servicing DNS requests. Fixes bug 965;
18897 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
18898 - Bridges now report complete directory request statistics. Related
18899 to bug 5824; bugfix on 0.2.2.1-alpha.
18900 - Bridges now never collect statistics that were designed for
18901 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
18902 - Stop giving annoying warning messages when we decide not to launch
18903 a pluggable transport proxy that we don't need (because there are
18904 no bridges configured to use it). Resolves ticket 5018; bugfix
18906 - Give the correct URL in the warning message when trying to run a
18907 relay on an ancient version of Windows. Fixes bug 9393.
18909 o Minor bugfixes (backtrace support):
18910 - Support automatic backtraces on more platforms by using the
18911 "-fasynchronous-unwind-tables" compiler option. This option is
18912 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
18913 is on by default and table generation is not. This doesn't yet
18914 add Windows support; only Linux, OSX, and some BSDs are affected.
18915 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
18916 - Avoid strange behavior if two threads hit failed assertions at the
18917 same time and both try to log backtraces at once. (Previously, if
18918 this had happened, both threads would have stored their intermediate
18919 results in the same buffer, and generated junk outputs.) Reported by
18920 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
18921 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
18922 0.2.5.2-alpha; patch from Nick Hopper.
18924 o Minor bugfixes (unit tests):
18925 - Fix a small bug in the unit tests that might have made the tests
18926 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
18927 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
18930 - Remove all remaining code related to version-0 hidden service
18931 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
18932 the rest of bug 10841.
18935 - Document in the manpage that "KBytes" may also be written as
18936 "kilobytes" or "KB", that "Kbits" may also be written as
18937 "kilobits", and so forth. Closes ticket 9222.
18938 - Document that the ClientOnly config option overrides ORPort.
18939 Our old explanation made ClientOnly sound as though it did
18940 nothing at all. Resolves bug 9059.
18941 - Explain that SocksPolicy, DirPolicy, and similar options don't
18942 take port arguments. Fixes the other part of ticket 11108.
18943 - Fix a comment about the rend_server_descriptor_t.protocols field
18944 to more accurately describe its range. Also, make that field
18945 unsigned, to more accurately reflect its usage. Fixes bug 9099;
18946 bugfix on 0.2.1.5-alpha.
18947 - Fix the manpage's description of HiddenServiceAuthorizeClient:
18948 the maximum client name length is 16, not 19. Fixes bug 11118;
18949 bugfix on 0.2.1.6-alpha.
18951 o Code simplifications and refactoring:
18952 - Get rid of router->address, since in all cases it was just the
18953 string representation of router->addr. Resolves ticket 5528.
18955 o Test infrastructure:
18956 - Update to the latest version of tinytest.
18957 - Improve the tinytest implementation of string operation tests so
18958 that comparisons with NULL strings no longer crash the tests; they
18959 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
18962 Changes in version 0.2.4.21 - 2014-02-28
18963 Tor 0.2.4.21 further improves security against potential adversaries who
18964 find breaking 1024-bit crypto doable, and backports several stability
18965 and robustness patches from the 0.2.5 branch.
18967 o Major features (client security):
18968 - When we choose a path for a 3-hop circuit, make sure it contains
18969 at least one relay that supports the NTor circuit extension
18970 handshake. Otherwise, there is a chance that we're building
18971 a circuit that's worth attacking by an adversary who finds
18972 breaking 1024-bit crypto doable, and that chance changes the game
18973 theory. Implements ticket 9777.
18976 - Do not treat streams that fail with reason
18977 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
18978 since it could also indicate an ENETUNREACH connection error. Fixes
18979 part of bug 10777; bugfix on 0.2.4.8-alpha.
18981 o Code simplification and refactoring:
18982 - Remove data structures which were introduced to implement the
18983 CellStatistics option: they are now redundant with the new timestamp
18984 field in the regular packed_cell_t data structure, which we did
18985 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
18988 - Always clear OpenSSL bignums before freeing them -- even bignums
18989 that don't contain secrets. Resolves ticket 10793. Patch by
18991 - Build without warnings under clang 3.4. (We have some macros that
18992 define static functions only some of which will get used later in
18993 the module. Starting with clang 3.4, these give a warning unless the
18994 unused attribute is set on them.) Resolves ticket 10904.
18995 - Update geoip and geoip6 files to the February 7 2014 Maxmind
18996 GeoLite2 Country database.
18999 - Set the listen() backlog limit to the largest actually supported
19000 on the system, not to the value in a header file. Fixes bug 9716;
19001 bugfix on every released Tor.
19002 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19003 exit node as a NOROUTE error, not an INTERNAL error, since they
19004 can apparently happen when trying to connect to the wrong sort
19005 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19006 - Fix build warnings about missing "a2x" comment when building the
19007 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19008 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19009 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19010 not entirely remove it from the connection lists. Fixes bug 9602;
19011 bugfix on 0.2.4.4-alpha.
19012 - Fix a segmentation fault in our benchmark code when running with
19013 Fedora's OpenSSL package, or any other OpenSSL that provides
19014 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19015 - Turn "circuit handshake stats since last time" log messages into a
19016 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19018 o Documentation fixes:
19019 - Document that all but one DirPort entry must have the NoAdvertise
19020 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19023 Changes in version 0.2.5.2-alpha - 2014-02-13
19024 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
19025 like the "poor random number generation" fix and the "building too many
19026 circuits" fix. It also further improves security against potential
19027 adversaries who find breaking 1024-bit crypto doable, and launches
19028 pluggable transports on demand (which gets us closer to integrating
19029 pluggable transport support by default -- not to be confused with Tor
19030 bundles enabling pluggable transports and bridges by default).
19032 o Major features (client security):
19033 - When we choose a path for a 3-hop circuit, make sure it contains
19034 at least one relay that supports the NTor circuit extension
19035 handshake. Otherwise, there is a chance that we're building
19036 a circuit that's worth attacking by an adversary who finds
19037 breaking 1024-bit crypto doable, and that chance changes the game
19038 theory. Implements ticket 9777.
19039 - Clients now look at the "usecreatefast" consensus parameter to
19040 decide whether to use CREATE_FAST or CREATE cells for the first hop
19041 of their circuit. This approach can improve security on connections
19042 where Tor's circuit handshake is stronger than the available TLS
19043 connection security levels, but the tradeoff is more computational
19044 load on guard relays. Implements proposal 221. Resolves ticket 9386.
19046 o Major features (bridges):
19047 - Don't launch pluggable transport proxies if we don't have any
19048 bridges configured that would use them. Now we can list many
19049 pluggable transports, and Tor will dynamically start one when it
19050 hears a bridge address that needs it. Resolves ticket 5018.
19051 - The bridge directory authority now assigns status flags (Stable,
19052 Guard, etc) to bridges based on thresholds calculated over all
19053 Running bridges. Now bridgedb can finally make use of its features
19054 to e.g. include at least one Stable bridge in its answers. Fixes
19057 o Major features (other):
19058 - Extend ORCONN controller event to include an "ID" parameter,
19059 and add four new controller event types CONN_BW, CIRC_BW,
19060 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
19061 The new events are emitted in private Tor networks only, with the
19062 goal of being able to better track performance and load during
19063 full-network simulations. Implements proposal 218 and ticket 7359.
19064 - On some platforms (currently: recent OSX versions, glibc-based
19065 platforms that support the ELF format, and a few other
19066 Unix-like operating systems), Tor can now dump stack traces
19067 when a crash occurs or an assertion fails. By default, traces
19068 are dumped to stderr (if possible) and to any logs that are
19069 reporting errors. Implements ticket 9299.
19072 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19073 not entirely remove it from the connection lists. Fixes bug 9602;
19074 bugfix on 0.2.4.4-alpha.
19075 - Do not treat streams that fail with reason
19076 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
19077 since it could also indicate an ENETUNREACH connection error. Fixes
19078 part of bug 10777; bugfix on 0.2.4.8-alpha.
19080 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
19081 - Do not allow OpenSSL engines to replace the PRNG, even when
19082 HardwareAccel is set. The only default builtin PRNG engine uses
19083 the Intel RDRAND instruction to replace the entire PRNG, and
19084 ignores all attempts to seed it with more entropy. That's
19085 cryptographically stupid: the right response to a new alleged
19086 entropy source is never to discard all previously used entropy
19087 sources. Fixes bug 10402; works around behavior introduced in
19088 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19090 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19091 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19092 - Avoid launching spurious extra circuits when a stream is pending.
19093 This fixes a bug where any circuit that _wasn't_ unusable for new
19094 streams would be treated as if it were, causing extra circuits to
19095 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19097 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19098 - No longer stop reading or writing on cpuworker connections when
19099 our rate limiting buckets go empty. Now we should handle circuit
19100 handshake requests more promptly. Resolves bug 9731.
19101 - Stop trying to bootstrap all our directory information from
19102 only our first guard. Discovered while fixing bug 9946; bugfix
19105 o Minor features (bridges, pluggable transports):
19106 - Add threshold cutoffs to the networkstatus document created by
19107 the Bridge Authority. Fixes bug 1117.
19108 - On Windows, spawn background processes using the CREATE_NO_WINDOW
19109 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
19110 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
19111 Vidalia set this option for us.) Implements ticket 10297.
19113 o Minor features (security):
19114 - Always clear OpenSSL bignums before freeing them -- even bignums
19115 that don't contain secrets. Resolves ticket 10793. Patch by
19118 o Minor features (config options and command line):
19119 - Add an --allow-missing-torrc commandline option that tells Tor to
19120 run even if the configuration file specified by -f is not available.
19121 Implements ticket 10060.
19122 - Add support for the TPROXY transparent proxying facility on Linux.
19123 See documentation for the new TransProxyType option for more
19124 details. Implementation by "thomo". Closes ticket 10582.
19126 o Minor features (controller):
19127 - Add a new "HS_DESC" controller event that reports activities
19128 related to hidden service descriptors. Resolves ticket 8510.
19129 - New "DROPGUARDS" controller command to forget all current entry
19130 guards. Not recommended for ordinary use, since replacing guards
19131 too frequently makes several attacks easier. Resolves ticket 9934;
19134 o Minor features (build):
19135 - Assume that a user using ./configure --host wants to cross-compile,
19136 and give an error if we cannot find a properly named
19137 tool-chain. Add a --disable-tool-name-check option to proceed
19138 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
19139 - If we run ./configure and the compiler recognizes -fstack-protector
19140 but the linker rejects it, warn the user about a potentially missing
19141 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
19143 o Minor features (testing):
19144 - If Python is installed, "make check" now runs extra tests beyond
19145 the unit test scripts.
19146 - When bootstrapping a test network, sometimes very few relays get
19147 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
19148 specify a set of relays which should be voted Guard regardless of
19149 their uptime or bandwidth. Addresses ticket 9206.
19151 o Minor features (log messages):
19152 - When ServerTransportPlugin is set on a bridge, Tor can write more
19153 useful statistics about bridge use in its extrainfo descriptors,
19154 but only if the Extended ORPort ("ExtORPort") is set too. Add a
19155 log message to inform the user in this case. Resolves ticket 9651.
19156 - When receiving a new controller connection, log the origin address.
19157 Resolves ticket 9698; patch from "sigpipe".
19158 - When logging OpenSSL engine status at startup, log the status of
19159 more engines. Fixes ticket 10043; patch from Joshua Datko.
19160 - Turn "circuit handshake stats since last time" log messages into a
19161 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19163 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19164 - Improve the circuit queue out-of-memory handler. Previously, when
19165 we ran low on memory, we'd close whichever circuits had the most
19166 queued cells. Now, we close those that have the *oldest* queued
19167 cells, on the theory that those are most responsible for us
19168 running low on memory. Based on analysis from a forthcoming paper
19169 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
19170 - Generate bootstrapping status update events correctly when fetching
19171 microdescriptors. Fixes bug 9927.
19172 - Update to the October 2 2013 Maxmind GeoLite Country database.
19174 o Minor bugfixes (clients):
19175 - When closing a channel that has already been open, do not close
19176 pending circuits that were waiting to connect to the same relay.
19177 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
19180 o Minor bugfixes (relays):
19181 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19182 exit node as a NOROUTE error, not an INTERNAL error, since they
19183 can apparently happen when trying to connect to the wrong sort
19184 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19186 o Minor bugfixes (bridges):
19187 - Fix a bug where the first connection works to a bridge that uses a
19188 pluggable transport with client-side parameters, but we don't send
19189 the client-side parameters on subsequent connections. (We don't
19190 use any pluggable transports with client-side parameters yet,
19191 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
19192 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
19194 o Minor bugfixes (node selection):
19195 - If ExcludeNodes is set, consider non-excluded hidden service
19196 directory servers before excluded ones. Do not consider excluded
19197 hidden service directory servers at all if StrictNodes is
19198 set. (Previously, we would sometimes decide to connect to those
19199 servers, and then realize before we initiated a connection that
19200 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
19201 Reported by "mr-4".
19202 - If we set the ExitNodes option but it doesn't include any nodes
19203 that have the Exit flag, we would choose not to bootstrap. Now we
19204 bootstrap so long as ExitNodes includes nodes which can exit to
19205 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
19207 o Minor bugfixes (controller and command-line):
19208 - If changing a config option via "setconf" fails in a recoverable
19209 way, we used to nonetheless write our new control ports to the
19210 file described by the "ControlPortWriteToFile" option. Now we only
19211 write out that file if we successfully switch to the new config
19212 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
19213 - When a command-line option such as --version or --help that
19214 ordinarily implies --hush appears on the command line along with
19215 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
19216 only if it appeared later on the command line. Fixes bug 9578;
19217 bugfix on 0.2.5.1-alpha.
19219 o Minor bugfixes (code correctness):
19220 - Previously we used two temporary files when writing descriptors to
19221 disk; now we only use one. Fixes bug 1376.
19222 - Remove an erroneous (but impossible and thus harmless) pointer
19223 comparison that would have allowed compilers to skip a bounds
19224 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
19225 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
19226 - Fix an always-true assertion in pluggable transports code so it
19227 actually checks what it was trying to check. Fixes bug 10046;
19228 bugfix on 0.2.3.9-alpha. Found by "dcb".
19230 o Minor bugfixes (protocol correctness):
19231 - When receiving a VERSIONS cell with an odd number of bytes, close
19232 the connection immediately since the cell is malformed. Fixes bug
19233 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
19236 o Minor bugfixes (build):
19237 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
19238 turned off (that is, without support for v2 link handshakes). Fixes
19239 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
19240 - Fix compilation warnings and startup issues when running with
19241 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
19243 - Fix compilation on Solaris 9, which didn't like us having an
19244 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
19246 o Minor bugfixes (testing):
19247 - Fix a segmentation fault in our benchmark code when running with
19248 Fedora's OpenSSL package, or any other OpenSSL that provides
19249 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19251 o Minor bugfixes (log messages):
19252 - Fix a bug where clients using bridges would report themselves
19253 as 50% bootstrapped even without a live consensus document.
19254 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
19255 - Suppress a warning where, if there's only one directory authority
19256 in the network, we would complain that votes and signatures cannot
19257 be uploaded to other directory authorities. Fixes bug 10842;
19258 bugfix on 0.2.2.26-beta.
19259 - Report bootstrapping progress correctly when we're downloading
19260 microdescriptors. We had updated our "do we have enough microdescs
19261 to begin building circuits?" logic most recently in 0.2.4.10-alpha
19262 (see bug 5956), but we left the bootstrap status event logic at
19263 "how far through getting 1/4 of them are we?" Fixes bug 9958;
19264 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
19266 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
19267 - Avoid a crash bug when starting with a corrupted microdescriptor
19268 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19269 - If we fail to dump a previously cached microdescriptor to disk, avoid
19270 freeing duplicate data later on. Fixes bug 10423; bugfix on
19271 0.2.4.13-alpha. Spotted by "bobnomnom".
19273 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19274 - Correctly log long IPv6 exit policies, instead of truncating them
19275 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
19276 - Our default TLS ecdhe groups were backwards: we meant to be using
19277 P224 for relays (for performance win) and P256 for bridges (since
19278 it is more common in the wild). Instead we had it backwards. After
19279 reconsideration, we decided that the default should be P256 on all
19280 hosts, since its security is probably better, and since P224 is
19281 reportedly used quite little in the wild. Found by "skruffy" on
19282 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
19283 - Free directory authority certificate download statuses on exit
19284 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
19286 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19287 - If the guard we choose first doesn't answer, we would try the
19288 second guard, but once we connected to the second guard we would
19289 abandon it and retry the first one, slowing down bootstrapping.
19290 The fix is to treat all our initially chosen guards as acceptable
19291 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19292 - Fix an assertion failure that would occur when disabling the
19293 ORPort setting on a running Tor process while accounting was
19294 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19295 - When examining the list of network interfaces to find our address,
19296 do not consider non-running or disabled network interfaces. Fixes
19297 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19298 - Avoid an off-by-one error when checking buffer boundaries when
19299 formatting the exit status of a pluggable transport helper.
19300 This is probably not an exploitable bug, but better safe than
19301 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19304 o Removed code and features:
19305 - Clients now reject any directory authority certificates lacking
19306 a dir-key-crosscert element. These have been included since
19307 0.2.1.9-alpha, so there's no real reason for them to be optional
19308 any longer. Completes proposal 157. Resolves ticket 10162.
19309 - Remove all code that existed to support the v2 directory system,
19310 since there are no longer any v2 directory authorities. Resolves
19312 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
19313 options, which were used for designating authorities as "Hidden
19314 service authorities". There has been no use of hidden service
19315 authorities since 0.2.2.1-alpha, when we stopped uploading or
19316 downloading v0 hidden service descriptors. Fixes bug 10881; also
19317 part of a fix for bug 10841.
19319 o Code simplification and refactoring:
19320 - Remove some old fallback code designed to keep Tor clients working
19321 in a network with only two working relays. Elsewhere in the code we
19322 have long since stopped supporting such networks, so there wasn't
19323 much point in keeping it around. Addresses ticket 9926.
19324 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
19325 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
19326 - Remove data structures which were introduced to implement the
19327 CellStatistics option: they are now redundant with the addition
19328 of a timestamp to the regular packed_cell_t data structure, which
19329 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
19332 o Documentation (man page) fixes:
19333 - Update manpage to describe some of the files you can expect to
19334 find in Tor's DataDirectory. Addresses ticket 9839.
19335 - Document that all but one DirPort entry must have the NoAdvertise
19336 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19338 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19339 - Clarify the usage and risks of setting the ContactInfo torrc line
19340 for your relay or bridge. Resolves ticket 9854.
19341 - Add anchors to the manpage so we can link to the html version of
19342 the documentation for specific options. Resolves ticket 9866.
19343 - Replace remaining references to DirServer in man page and
19344 log entries. Resolves ticket 10124.
19347 - Make the "tor-gencert" tool used by directory authority operators
19348 create 2048-bit signing keys by default (rather than 1024-bit, since
19349 1024-bit is uncomfortably small these days). Addresses ticket 10324.
19352 Changes in version 0.2.4.20 - 2013-12-22
19353 Tor 0.2.4.20 fixes potentially poor random number generation for users
19354 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
19355 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
19356 and 4) have no state file in their DataDirectory (as would happen on
19357 first start). Users who generated relay or hidden service identity
19358 keys in such a situation should discard them and generate new ones.
19360 This release also fixes a logic error that caused Tor clients to build
19361 many more preemptive circuits than they actually need.
19364 - Do not allow OpenSSL engines to replace the PRNG, even when
19365 HardwareAccel is set. The only default builtin PRNG engine uses
19366 the Intel RDRAND instruction to replace the entire PRNG, and
19367 ignores all attempts to seed it with more entropy. That's
19368 cryptographically stupid: the right response to a new alleged
19369 entropy source is never to discard all previously used entropy
19370 sources. Fixes bug 10402; works around behavior introduced in
19371 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19373 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19374 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19375 - Avoid launching spurious extra circuits when a stream is pending.
19376 This fixes a bug where any circuit that _wasn't_ unusable for new
19377 streams would be treated as if it were, causing extra circuits to
19378 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19381 - Avoid a crash bug when starting with a corrupted microdescriptor
19382 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19383 - If we fail to dump a previously cached microdescriptor to disk, avoid
19384 freeing duplicate data later on. Fixes bug 10423; bugfix on
19385 0.2.4.13-alpha. Spotted by "bobnomnom".
19388 Changes in version 0.2.4.19 - 2013-12-11
19389 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
19390 (1986-2013). Aaron worked on diverse projects including helping to guide
19391 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
19392 transparency to the U.S government's PACER documents, and contributing
19393 design and development for Tor and Tor2Web. Aaron was one of the latest
19394 martyrs in our collective fight for civil liberties and human rights,
19395 and his death is all the more painful because he was one of us.
19397 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
19398 a new circuit handshake and link encryption that use ECC to provide
19399 better security and efficiency; makes relays better manage circuit
19400 creation requests; uses "directory guards" to reduce client enumeration
19401 risks; makes bridges collect and report statistics about the pluggable
19402 transports they support; cleans up and improves our geoip database;
19403 gets much closer to IPv6 support for clients, bridges, and relays; makes
19404 directory authorities use measured bandwidths rather than advertised
19405 ones when computing flags and thresholds; disables client-side DNS
19406 caching to reduce tracking risks; and fixes a big bug in bridge
19407 reachability testing. This release introduces two new design
19408 abstractions in the code: a new "channel" abstraction between circuits
19409 and or_connections to allow for implementing alternate relay-to-relay
19410 transports, and a new "circuitmux" abstraction storing the queue of
19411 circuits for a channel. The release also includes many stability,
19412 security, and privacy fixes.
19415 Changes in version 0.2.4.18-rc - 2013-11-16
19416 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
19417 series. It takes a variety of fixes from the 0.2.5.x branch to improve
19418 stability, performance, and better handling of edge cases.
19421 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19422 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19423 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19424 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19425 them to solve bug 6033.)
19428 - No longer stop reading or writing on cpuworker connections when
19429 our rate limiting buckets go empty. Now we should handle circuit
19430 handshake requests more promptly. Resolves bug 9731.
19431 - If we are unable to save a microdescriptor to the journal, do not
19432 drop it from memory and then reattempt downloading it. Fixes bug
19433 9645; bugfix on 0.2.2.6-alpha.
19434 - Stop trying to bootstrap all our directory information from
19435 only our first guard. Discovered while fixing bug 9946; bugfix
19437 - The new channel code sometimes lost track of in-progress circuits,
19438 causing long-running clients to stop building new circuits. The
19439 fix is to always call circuit_n_chan_done(chan, 0) from
19440 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
19442 o Minor bugfixes (on 0.2.4.x):
19443 - Correctly log long IPv6 exit policies, instead of truncating them
19444 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
19445 - Our default TLS ecdhe groups were backwards: we meant to be using
19446 P224 for relays (for performance win) and P256 for bridges (since
19447 it is more common in the wild). Instead we had it backwards. After
19448 reconsideration, we decided that the default should be P256 on all
19449 hosts, since its security is probably better, and since P224 is
19450 reportedly used quite little in the wild. Found by "skruffy" on
19451 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
19452 - Free directory authority certificate download statuses on exit
19453 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
19455 o Minor bugfixes (on 0.2.3.x and earlier):
19456 - If the guard we choose first doesn't answer, we would try the
19457 second guard, but once we connected to the second guard we would
19458 abandon it and retry the first one, slowing down bootstrapping.
19459 The fix is to treat all our initially chosen guards as acceptable
19460 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19461 - Fix an assertion failure that would occur when disabling the
19462 ORPort setting on a running Tor process while accounting was
19463 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19464 - When examining the list of network interfaces to find our address,
19465 do not consider non-running or disabled network interfaces. Fixes
19466 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19467 - Avoid an off-by-one error when checking buffer boundaries when
19468 formatting the exit status of a pluggable transport helper.
19469 This is probably not an exploitable bug, but better safe than
19470 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19473 o Minor features (protecting client timestamps):
19474 - Clients no longer send timestamps in their NETINFO cells. These were
19475 not used for anything, and they provided one small way for clients
19476 to be distinguished from each other as they moved from network to
19477 network or behind NAT. Implements part of proposal 222.
19478 - Clients now round timestamps in INTRODUCE cells down to the nearest
19479 10 minutes. If a new Support022HiddenServices option is set to 0, or
19480 if it's set to "auto" and the feature is disabled in the consensus,
19481 the timestamp is sent as 0 instead. Implements part of proposal 222.
19482 - Stop sending timestamps in AUTHENTICATE cells. This is not such
19483 a big deal from a security point of view, but it achieves no actual
19484 good purpose, and isn't needed. Implements part of proposal 222.
19485 - Reduce down accuracy of timestamps in hidden service descriptors.
19486 Implements part of proposal 222.
19488 o Minor features (other):
19489 - Improve the circuit queue out-of-memory handler. Previously, when
19490 we ran low on memory, we'd close whichever circuits had the most
19491 queued cells. Now, we close those that have the *oldest* queued
19492 cells, on the theory that those are most responsible for us
19493 running low on memory. Based on analysis from a forthcoming paper
19494 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
19495 - Generate bootstrapping status update events correctly when fetching
19496 microdescriptors. Fixes bug 9927.
19497 - Update to the October 2 2013 Maxmind GeoLite Country database.
19499 o Documentation fixes:
19500 - Clarify the usage and risks of setting the ContactInfo torrc line
19501 for your relay or bridge. Resolves ticket 9854.
19502 - Add anchors to the manpage so we can link to the html version of
19503 the documentation for specific options. Resolves ticket 9866.
19504 - Replace remaining references to DirServer in man page and
19505 log entries. Resolves ticket 10124.
19508 Changes in version 0.2.5.1-alpha - 2013-10-02
19509 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
19510 on Linux, allows bridges that offer pluggable transports to report usage
19511 statistics, fixes many issues to make testing easier, and provides
19512 a pile of minor features and bugfixes that have been waiting for a
19513 release of the new branch.
19515 This is the first alpha release in a new series, so expect there to
19516 be bugs. Users who would rather test out a more stable branch should
19517 stay with 0.2.4.x for now.
19519 o Major features (security):
19520 - Use the seccomp2 syscall filtering facility on Linux to limit
19521 which system calls Tor can invoke. This is an experimental,
19522 Linux-only feature to provide defense-in-depth against unknown
19523 attacks. To try turning it on, set "Sandbox 1" in your torrc
19524 file. Please be ready to report bugs. We hope to add support
19525 for better sandboxing in the future, including more fine-grained
19526 filters, better division of responsibility, and support for more
19527 platforms. This work has been done by Cristian-Matei Toader for
19528 Google Summer of Code.
19529 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19530 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19531 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19532 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19533 them to solve bug 6033.)
19535 o Major features (other):
19536 - Add support for passing arguments to managed pluggable transport
19537 proxies. Implements ticket 3594.
19538 - Bridges now track GeoIP information and the number of their users
19539 even when pluggable transports are in use, and report usage
19540 statistics in their extra-info descriptors. Resolves tickets 4773
19542 - Make testing Tor networks bootstrap better: lower directory fetch
19543 retry schedules and maximum interval without directory requests,
19544 and raise maximum download tries. Implements ticket 6752.
19545 - Add make target 'test-network' to run tests on a Chutney network.
19546 Implements ticket 8530.
19547 - The ntor handshake is now on-by-default, no matter what the
19548 directory authorities recommend. Implements ticket 8561.
19551 - Instead of writing destroy cells directly to outgoing connection
19552 buffers, queue them and intersperse them with other outgoing cells.
19553 This can prevent a set of resource starvation conditions where too
19554 many pending destroy cells prevent data cells from actually getting
19555 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
19556 bugfix on 0.2.0.1-alpha.
19557 - If we are unable to save a microdescriptor to the journal, do not
19558 drop it from memory and then reattempt downloading it. Fixes bug
19559 9645; bugfix on 0.2.2.6-alpha.
19560 - The new channel code sometimes lost track of in-progress circuits,
19561 causing long-running clients to stop building new circuits. The
19562 fix is to always call circuit_n_chan_done(chan, 0) from
19563 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
19566 - Tor now builds each source file in two modes: a mode that avoids
19567 exposing identifiers needlessly, and another mode that exposes
19568 more identifiers for testing. This lets the compiler do better at
19569 optimizing the production code, while enabling us to take more
19570 radical measures to let the unit tests test things.
19571 - The production builds no longer include functions used only in
19572 the unit tests; all functions exposed from a module only for
19573 unit-testing are now static in production builds.
19574 - Add an --enable-coverage configuration option to make the unit
19575 tests (and a new src/or/tor-cov target) to build with gcov test
19579 - We now have rudimentary function mocking support that our unit
19580 tests can use to test functions in isolation. Function mocking
19581 lets the tests temporarily replace a function's dependencies with
19582 stub functions, so that the tests can check the function without
19583 invoking the other functions it calls.
19584 - Add more unit tests for the <circid,channel>->circuit map, and
19585 the destroy-cell-tracking code to fix bug 7912.
19586 - Unit tests for failing cases of the TAP onion handshake.
19587 - More unit tests for address-manipulation functions.
19589 o Minor features (protecting client timestamps):
19590 - Clients no longer send timestamps in their NETINFO cells. These were
19591 not used for anything, and they provided one small way for clients
19592 to be distinguished from each other as they moved from network to
19593 network or behind NAT. Implements part of proposal 222.
19594 - Clients now round timestamps in INTRODUCE cells down to the nearest
19595 10 minutes. If a new Support022HiddenServices option is set to 0, or
19596 if it's set to "auto" and the feature is disabled in the consensus,
19597 the timestamp is sent as 0 instead. Implements part of proposal 222.
19598 - Stop sending timestamps in AUTHENTICATE cells. This is not such
19599 a big deal from a security point of view, but it achieves no actual
19600 good purpose, and isn't needed. Implements part of proposal 222.
19601 - Reduce down accuracy of timestamps in hidden service descriptors.
19602 Implements part of proposal 222.
19604 o Minor features (config options):
19605 - Config (torrc) lines now handle fingerprints which are missing
19606 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
19607 - Support a --dump-config option to print some or all of the
19608 configured options. Mainly useful for debugging the command-line
19609 option parsing code. Helps resolve ticket 4647.
19610 - Raise awareness of safer logging: notify user of potentially
19611 unsafe config options, like logging more verbosely than severity
19612 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
19613 - Add a new configuration option TestingV3AuthVotingStartOffset
19614 that bootstraps a network faster by changing the timing for
19615 consensus votes. Addresses ticket 8532.
19616 - Add a new torrc option "ServerTransportOptions" that allows
19617 bridge operators to pass configuration parameters to their
19618 pluggable transports. Resolves ticket 8929.
19619 - The config (torrc) file now accepts bandwidth and space limits in
19620 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
19621 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
19624 o Minor features (build):
19625 - Add support for `--library-versions` flag. Implements ticket 6384.
19626 - Return the "unexpected sendme" warnings to a warn severity, but make
19627 them rate limited, to help diagnose ticket 8093.
19628 - Detect a missing asciidoc, and warn the user about it, during
19629 configure rather than at build time. Fixes issue 6506. Patch from
19632 o Minor features (other):
19633 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
19634 sockets in a single system call. Implements ticket 5129.
19635 - Log current accounting state (bytes sent and received + remaining
19636 time for the current accounting period) in the relay's heartbeat
19637 message. Implements ticket 5526; patch from Peter Retzlaff.
19638 - Implement the TRANSPORT_LAUNCHED control port event that
19639 notifies controllers about new launched pluggable
19640 transports. Resolves ticket 5609.
19641 - If we're using the pure-C 32-bit curve25519_donna implementation
19642 of curve25519, build it with the -fomit-frame-pointer option to
19643 make it go faster on register-starved hosts. This improves our
19644 handshake performance by about 6% on i386 hosts without nacl.
19645 Closes ticket 8109.
19646 - Update to the September 4 2013 Maxmind GeoLite Country database.
19649 - Set the listen() backlog limit to the largest actually supported
19650 on the system, not to the value in a header file. Fixes bug 9716;
19651 bugfix on every released Tor.
19652 - No longer accept malformed http headers when parsing urls from
19653 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
19654 bugfix on 0.0.6pre1.
19655 - In munge_extrainfo_into_routerinfo(), check the return value of
19656 memchr(). This would have been a serious issue if we ever passed
19657 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
19659 - On the chance that somebody manages to build Tor on a
19660 platform where time_t is unsigned, correct the way that
19661 microdesc_add_to_cache() handles negative time arguments.
19662 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
19663 - Reject relative control socket paths and emit a warning. Previously,
19664 single-component control socket paths would be rejected, but Tor
19665 would not log why it could not validate the config. Fixes bug 9258;
19666 bugfix on 0.2.3.16-alpha.
19668 o Minor bugfixes (command line):
19669 - Use a single command-line parser for parsing torrc options on the
19670 command line and for finding special command-line options to avoid
19671 inconsistent behavior for torrc option arguments that have the same
19672 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
19674 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
19675 9573; bugfix on 0.0.9pre5.
19677 o Minor fixes (build, auxiliary programs):
19678 - Stop preprocessing the "torify" script with autoconf, since
19679 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
19681 - The tor-fw-helper program now follows the standard convention and
19682 exits with status code "0" on success. Fixes bug 9030; bugfix on
19683 0.2.3.1-alpha. Patch by Arlo Breault.
19684 - Corrected ./configure advice for what openssl dev package you should
19685 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
19687 o Minor code improvements:
19688 - Remove constants and tests for PKCS1 padding; it's insecure and
19689 shouldn't be used for anything new. Fixes bug 8792; patch
19691 - Remove instances of strcpy() from the unit tests. They weren't
19692 hurting anything, since they were only in the unit tests, but it's
19693 embarrassing to have strcpy() in the code at all, and some analysis
19694 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
19695 0.2.3.8-alpha. Patch from Arlo Breault.
19697 o Removed features:
19698 - Remove migration code from when we renamed the "cached-routers"
19699 file to "cached-descriptors" back in 0.2.0.8-alpha. This
19700 incidentally resolves ticket 6502 by cleaning up the related code
19701 a bit. Patch from Akshay Hebbar.
19703 o Code simplification and refactoring:
19704 - Extract the common duplicated code for creating a subdirectory
19705 of the data directory and writing to a file in it. Fixes ticket
19706 4282; patch from Peter Retzlaff.
19707 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
19708 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
19709 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
19710 - Add a set of accessor functions for the circuit timeout data
19711 structure. Fixes ticket 6153; patch from "piet".
19712 - Clean up exit paths from connection_listener_new(). Closes ticket
19713 8789. Patch from Arlo Breault.
19714 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
19715 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
19716 - Use a doubly-linked list to implement the global circuit list.
19717 Resolves ticket 9108. Patch from Marek Majkowski.
19718 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
19721 Changes in version 0.2.4.17-rc - 2013-09-05
19722 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
19723 series. It adds an emergency step to help us tolerate the massive
19724 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
19725 circuit-level handshakes now effectively jump the queue compared to
19726 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
19727 big bug hindering bridge reachability tests.
19730 - Relays now process the new "NTor" circuit-level handshake requests
19731 with higher priority than the old "TAP" circuit-level handshake
19732 requests. We still process some TAP requests to not totally starve
19733 0.2.3 clients when NTor becomes popular. A new consensus parameter
19734 "NumNTorsPerTAP" lets us tune the balance later if we need to.
19735 Implements ticket 9574.
19738 - If the circuit build timeout logic is disabled (via the consensus,
19739 or because we are an authority), then don't build testing circuits.
19740 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
19741 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
19742 previously they did not, which prevented them from receiving
19743 successful connections from relays for self-test or bandwidth
19744 testing. Also, when a relay is extending a circuit to a bridge,
19745 it needs to send a NETINFO cell, even when the bridge hasn't sent
19746 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
19747 - If the time to download the next old-style networkstatus is in
19748 the future, do not decline to consider whether to download the
19749 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
19753 - Avoid double-closing the listener socket in our socketpair()
19754 replacement (used on Windows) in the case where the addresses on
19755 our opened sockets don't match what we expected. Fixes bug 9400;
19756 bugfix on 0.0.2pre7. Found by Coverity.
19758 o Minor fixes (config options):
19759 - Avoid overflows when the user sets MaxCircuitDirtiness to a
19760 ridiculously high value, by imposing a (ridiculously high) 30-day
19761 maximum on MaxCircuitDirtiness.
19762 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
19763 message is logged at notice, not at info.
19764 - Warn and fail if a server is configured not to advertise any
19765 ORPorts at all. (We need *something* to put in our descriptor,
19766 or we just won't work.)
19769 - Track how many "TAP" and "NTor" circuit handshake requests we get,
19770 and how many we complete, and log it every hour to help relay
19771 operators follow trends in network load. Addresses ticket 9658.
19772 - Update to the August 7 2013 Maxmind GeoLite Country database.
19775 Changes in version 0.2.4.16-rc - 2013-08-10
19776 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
19777 series. It fixes several crash bugs in the 0.2.4 branch.
19780 - Fix a bug in the voting algorithm that could yield incorrect results
19781 when a non-naming authority declared too many flags. Fixes bug 9200;
19782 bugfix on 0.2.0.3-alpha.
19783 - Fix an uninitialized read that could in some cases lead to a remote
19784 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
19785 Anybody running a hidden service on the experimental 0.2.4.x
19786 branch should upgrade. (This is, so far as we know, unrelated to
19788 - Avoid an assertion failure when processing DNS replies without the
19789 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
19790 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
19791 0.2.4.15-rc. Found by stem integration tests.
19794 - Fix an invalid memory read that occurred when a pluggable
19795 transport proxy failed its configuration protocol.
19796 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
19797 - When evaluating whether to use a connection that we haven't
19798 decided is canonical using a recent link protocol version,
19799 decide that it's canonical only if it used address _does_
19800 match the desired address. Fixes bug 9309; bugfix on
19801 0.2.4.4-alpha. Reported by skruffy.
19802 - Make the default behavior of NumDirectoryGuards be to track
19803 NumEntryGuards. Now a user who changes only NumEntryGuards will get
19804 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
19805 - Fix a spurious compilation warning with some older versions of
19806 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
19809 - Update to the July 3 2013 Maxmind GeoLite Country database.
19812 Changes in version 0.2.4.15-rc - 2013-07-01
19813 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
19814 series. It fixes a few smaller bugs, but generally appears stable.
19815 Please test it and let us know whether it is!
19818 - When receiving a new configuration file via the control port's
19819 LOADCONF command, do not treat the defaults file as absent.
19820 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
19823 - Issue a warning when running with the bufferevents backend enabled.
19824 It's still not stable, and people should know that they're likely
19825 to hit unexpected problems. Closes ticket 9147.
19828 Changes in version 0.2.4.14-alpha - 2013-06-18
19829 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
19830 present in 0.2.4.13-alpha.
19833 - When we have too much memory queued in circuits (according to a new
19834 MaxMemInCellQueues option), close the circuits consuming the most
19835 memory. This prevents us from running out of memory as a relay if
19836 circuits fill up faster than they can be drained. Fixes bug 9063;
19837 bugfix on the 54th commit of Tor. This bug is a further fix beyond
19838 bug 6252, whose fix was merged into 0.2.3.21-rc.
19840 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
19841 where we tried to solve this issue simply by imposing an upper limit
19842 on the number of queued cells for a single circuit. That approach
19843 proved to be problematic, since there are ways to provoke clients to
19844 send a number of cells in excess of any such reasonable limit. Fixes
19845 bug 9072; bugfix on 0.2.4.13-alpha.
19847 - Limit hidden service descriptors to at most ten introduction
19848 points, to slow one kind of guard enumeration. Fixes bug 9002;
19849 bugfix on 0.1.1.11-alpha.
19852 Changes in version 0.2.4.13-alpha - 2013-06-14
19853 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
19854 vulnerabilities, makes socks5 username/password circuit isolation
19855 actually actually work (this time for sure!), and cleans up a bunch
19856 of other issues in preparation for a release candidate.
19858 o Major bugfixes (robustness):
19859 - Close any circuit that has too many cells queued on it. Fixes
19860 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
19861 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
19862 - Prevent the get_freelists() function from running off the end of
19863 the list of freelists if it somehow gets an unrecognized
19864 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
19866 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
19867 when an exit connection with optimistic data succeeds immediately
19868 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
19870 - Fix a directory authority crash bug when building a consensus
19871 using an older consensus as its basis. Fixes bug 8833. Bugfix
19875 - Avoid a memory leak where we would leak a consensus body when we
19876 find that a consensus which we couldn't previously verify due to
19877 missing certificates is now verifiable. Fixes bug 8719; bugfix
19879 - We used to always request authority certificates by identity digest,
19880 meaning we'd get the newest one even when we wanted one with a
19881 different signing key. Then we would complain about being given
19882 a certificate we already had, and never get the one we really
19883 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
19884 resource to request the one we want. Fixes bug 5595; bugfix on
19886 - Follow the socks5 protocol when offering username/password
19887 authentication. The fix for bug 8117 exposed this bug, and it
19888 turns out real-world applications like Pidgin do care. Bugfix on
19889 0.2.3.2-alpha; fixes bug 8879.
19890 - Prevent failures on Windows Vista and later when rebuilding the
19891 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
19892 bugfix on 0.2.4.12-alpha.
19895 - Fix an impossible buffer overrun in the AES unit tests. Fixes
19896 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
19897 - If for some reason we fail to write a microdescriptor while
19898 rebuilding the cache, do not let the annotations from that
19899 microdescriptor linger in the cache file, and do not let the
19900 microdescriptor stay recorded as present in its old location.
19901 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
19902 - Fix a memory leak that would occur whenever a configuration
19903 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
19904 - Paste the description for PathBias parameters from the man
19905 page into or.h, so the code documents them too. Fixes bug 7982;
19906 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
19907 - Relays now treat a changed IPv6 ORPort as sufficient reason to
19908 publish an updated descriptor. Fixes bug 6026; bugfix on
19910 - When launching a resolve request on behalf of an AF_UNIX control
19911 socket, omit the address field of the new entry connection, used in
19912 subsequent controller events, rather than letting tor_dup_addr()
19913 set it to "<unknown address type>". Fixes bug 8639; bugfix on
19916 o Minor bugfixes (log messages):
19917 - Fix a scaling issue in the path bias accounting code that
19918 resulted in "Bug:" log messages from either
19919 pathbias_scale_close_rates() or pathbias_count_build_success().
19920 This represents a bugfix on a previous bugfix: the original fix
19921 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
19923 - Give a less useless error message when the user asks for an IPv4
19924 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
19928 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
19929 to tolerate bug 8093 for now.
19930 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
19931 in directory authority votes to describe whether they have enough
19932 measured bandwidths to ignore advertised (relay descriptor)
19933 bandwidth claims. Resolves ticket 8711.
19934 - Update to the June 5 2013 Maxmind GeoLite Country database.
19936 o Removed documentation:
19937 - Remove some of the older contents of doc/ as obsolete; move others
19938 to torspec.git. Fixes bug 8965.
19940 o Code simplification and refactoring:
19941 - Avoid using character buffers when constructing most directory
19942 objects: this approach was unwieldy and error-prone. Instead,
19943 build smartlists of strings, and concatenate them when done.
19946 Changes in version 0.2.4.12-alpha - 2013-04-18
19947 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
19948 process for lengthening the guard rotation period, makes directory
19949 authority opinions in the consensus a bit less gameable, makes socks5
19950 username/password circuit isolation actually work, and fixes a wide
19951 variety of other issues.
19954 - Raise the default time that a client keeps an entry guard from
19955 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
19956 2012 paper. (We would make it even longer, but we need better client
19957 load balancing first.) Also, make the guard lifetime controllable
19958 via a new GuardLifetime torrc option and a GuardLifetime consensus
19959 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
19960 - Directory authorities now prefer using measured bandwidths to
19961 advertised ones when computing flags and thresholds. Resolves
19963 - Directory authorities that have more than a threshold number
19964 of relays with measured bandwidths now treat relays with unmeasured
19965 bandwidths as having bandwidth 0. Resolves ticket 8435.
19967 o Major bugfixes (assert / resource use):
19968 - Avoid a bug where our response to TLS renegotiation under certain
19969 network conditions could lead to a busy-loop, with 100% CPU
19970 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
19971 - Avoid an assertion when we discover that we'd like to write a cell
19972 onto a closing connection: just discard the cell. Fixes another
19973 case of bug 7350; bugfix on 0.2.4.4-alpha.
19975 o Major bugfixes (client-side privacy):
19976 - When we mark a circuit as unusable for new circuits, have it
19977 continue to be unusable for new circuits even if MaxCircuitDirtiness
19978 is increased too much at the wrong time, or the system clock jumps
19979 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
19980 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
19981 which have resolved to internal addresses") is set, apply that
19982 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
19983 - When an exit relay rejects a stream with reason "exit policy", but
19984 we only know an exit policy summary (e.g. from the microdesc
19985 consensus) for it, do not mark the relay as useless for all exiting.
19986 Instead, mark just the circuit as unsuitable for that particular
19987 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
19988 - Allow applications to get proper stream isolation with
19989 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
19990 username/password authentication also offer "no authentication". Tor
19991 had previously preferred "no authentication", so the applications
19992 never actually sent Tor their auth details. Now Tor selects
19993 username/password authentication if it's offered. You can disable
19994 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
19995 bug 8117; bugfix on 0.2.3.3-alpha.
19997 o Major bugfixes (other):
19998 - When unable to find any working directory nodes to use as a
19999 directory guard, give up rather than adding the same non-working
20000 nodes to the directory guard list over and over. Fixes bug 8231;
20001 bugfix on 0.2.4.8-alpha.
20004 - Reject as invalid most directory objects containing a NUL.
20005 Belt-and-suspender fix for bug 8037.
20006 - In our testsuite, create temporary directories with a bit more
20007 entropy in their name to make name collisions less likely. Fixes
20009 - Add CACHED keyword to ADDRMAP events in the control protocol
20010 to indicate whether a DNS result will be cached or not. Resolves
20012 - Update to the April 3 2013 Maxmind GeoLite Country database.
20014 o Minor features (build):
20015 - Detect and reject attempts to build Tor with threading support
20016 when OpenSSL has been compiled without threading support.
20018 - Clarify that when autoconf is checking for nacl, it is checking
20019 specifically for nacl with a fast curve25519 implementation.
20021 - Warn if building on a platform with an unsigned time_t: there
20022 are too many places where Tor currently assumes that time_t can
20023 hold negative values. We'd like to fix them all, but probably
20026 o Minor bugfixes (build):
20027 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
20028 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
20029 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
20030 - Add the old src/or/micro-revision.i filename to CLEANFILES.
20031 On the off chance that somebody has one, it will go away as soon
20032 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
20033 - Build Tor correctly on 32-bit platforms where the compiler can build
20034 but not run code using the "uint128_t" construction. Fixes bug 8587;
20035 bugfix on 0.2.4.8-alpha.
20036 - Fix compilation warning with some versions of clang that would
20037 prefer the -Wswitch-enum compiler flag to warn about switch
20038 statements with missing enum values, even if those switch
20039 statements have a "default:" statement. Fixes bug 8598; bugfix
20042 o Minor bugfixes (protocol):
20043 - Fix the handling of a TRUNCATE cell when it arrives while the
20044 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
20045 - Fix a misframing issue when reading the version numbers in a
20046 VERSIONS cell. Previously we would recognize [00 01 00 02] as
20047 'version 1, version 2, and version 0x100', when it should have
20048 only included versions 1 and 2. Fixes bug 8059; bugfix on
20049 0.2.0.10-alpha. Reported pseudonymously.
20050 - Make the format and order of STREAM events for DNS lookups
20051 consistent among the various ways to launch DNS lookups. Fixes
20052 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
20053 - Correct our check for which versions of Tor support the EXTEND2
20054 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
20055 later, when support was really added in version 0.2.4.8-alpha.
20056 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
20058 o Minor bugfixes (other):
20059 - Correctly store microdescriptors and extrainfo descriptors with
20060 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
20061 Bug reported by "cypherpunks".
20062 - Increase the width of the field used to remember a connection's
20063 link protocol version to two bytes. Harmless for now, since the
20064 only currently recognized versions are one byte long. Reported
20065 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
20066 - If the state file's path bias counts are invalid (presumably from a
20067 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
20068 additional checks and log messages to the scaling of Path Bias
20069 counts, in case there still are remaining issues with scaling.
20070 Should help resolve bug 8235.
20071 - Eliminate several instances where we use "Nickname=ID" to refer to
20072 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
20073 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
20074 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
20076 o Minor bugfixes (syscalls):
20077 - Always check the return values of functions fcntl() and
20078 setsockopt(). We don't believe these are ever actually failing in
20079 practice, but better safe than sorry. Also, checking these return
20080 values should please analysis tools like Coverity. Patch from
20081 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
20082 - Use direct writes rather than stdio when building microdescriptor
20083 caches, in an attempt to mitigate bug 8031, or at least make it
20086 o Minor bugfixes (config):
20087 - When rejecting a configuration because we were unable to parse a
20088 quoted string, log an actual error message. Fixes bug 7950; bugfix
20090 - Behave correctly when the user disables LearnCircuitBuildTimeout
20091 but doesn't tell us what they would like the timeout to be. Fixes
20092 bug 6304; bugfix on 0.2.2.14-alpha.
20093 - When autodetecting the number of CPUs, use the number of available
20094 CPUs in preference to the number of configured CPUs. Inform the
20095 user if this reduces the number of available CPUs. Fixes bug 8002;
20096 bugfix on 0.2.3.1-alpha.
20097 - Make it an error when you set EntryNodes but disable UseGuardNodes,
20098 since it will (surprisingly to some users) ignore EntryNodes. Fixes
20099 bug 8180; bugfix on 0.2.3.11-alpha.
20100 - Allow TestingTorNetworks to override the 4096-byte minimum for
20101 the Fast threshold. Otherwise they can't bootstrap until they've
20102 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
20103 - Fix some logic errors when the user manually overrides the
20104 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
20107 o Minor bugfixes (log messages to help diagnose bugs):
20108 - If we fail to free a microdescriptor because of bug 7164, log
20109 the filename and line number from which we tried to free it.
20110 - Add another diagnostic to the heartbeat message: track and log
20111 overhead that TLS is adding to the data we write. If this is
20112 high, we are sending too little data to SSL_write at a time.
20113 Diagnostic for bug 7707.
20114 - Add more detail to a log message about relaxed timeouts, to help
20116 - Warn more aggressively when flushing microdescriptors to a
20117 microdescriptor cache fails, in an attempt to mitigate bug 8031,
20118 or at least make it more diagnosable.
20119 - Improve debugging output to help track down bug 8185 ("Bug:
20120 outgoing relay cell has n_chan==NULL. Dropping.")
20121 - Log the purpose of a path-bias testing circuit correctly.
20122 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
20124 o Minor bugfixes (0.2.4.x log messages that were too noisy):
20125 - Don't attempt to relax the timeout of already opened 1-hop circuits.
20126 They might never timeout. This should eliminate some/all cases of
20127 the relaxed timeout log message.
20128 - Use circuit creation time for network liveness evaluation. This
20129 should eliminate warning log messages about liveness caused
20130 by changes in timeout evaluation. Fixes bug 6572; bugfix on
20132 - Reduce a path bias length check from notice to info. The message
20133 is triggered when creating controller circuits. Fixes bug 8196;
20134 bugfix on 0.2.4.8-alpha.
20135 - Fix a path state issue that triggered a notice during relay startup.
20136 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
20137 - Reduce occurrences of warns about circuit purpose in
20138 connection_ap_expire_building(). Fixes bug 8477; bugfix on
20141 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
20142 - If we encounter a write failure on a SOCKS connection before we
20143 finish our SOCKS handshake, don't warn that we closed the
20144 connection before we could send a SOCKS reply. Fixes bug 8427;
20145 bugfix on 0.1.0.1-rc.
20146 - Correctly recognize that [::1] is a loopback address. Fixes
20147 bug 8377; bugfix on 0.2.1.3-alpha.
20148 - Fix a directory authority warn caused when we have a large amount
20149 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
20150 - Don't log inappropriate heartbeat messages when hibernating: a
20151 hibernating node is _expected_ to drop out of the consensus,
20152 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
20153 bugfix on 0.2.3.1-alpha.
20154 - Don't complain about bootstrapping problems while hibernating.
20155 These complaints reflect a general code problem, but not one
20156 with any problematic effects (no connections are actually
20157 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
20159 o Documentation fixes:
20160 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
20161 names match. Fixes bug 7768.
20162 - Make the torify manpage no longer refer to tsocks; torify hasn't
20163 supported tsocks since 0.2.3.14-alpha.
20164 - Make the tor manpage no longer reference tsocks.
20165 - Fix the GeoIPExcludeUnknown documentation to refer to
20166 ExcludeExitNodes rather than the currently nonexistent
20167 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
20170 - The tor-tsocks.conf is no longer distributed or installed. We
20171 recommend that tsocks users use torsocks instead. Resolves
20175 Changes in version 0.2.4.11-alpha - 2013-03-11
20176 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
20177 more robust, makes hidden service authentication work again, and
20178 resolves a DPI fingerprint for Tor's SSL transport.
20180 o Major features (directory authorities):
20181 - Directory authorities now support a new consensus method (17)
20182 where they cap the published bandwidth of servers for which
20183 insufficient bandwidth measurements exist. Fixes part of bug 2286.
20184 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
20185 serve any v2 directory information. Now we can test disabling the
20186 old deprecated v2 directory format, and see whether doing so has
20187 any effect on network load. Begins to fix bug 6783.
20188 - Directory authorities now include inside each vote a statement of
20189 the performance thresholds they used when assigning flags.
20190 Implements ticket 8151.
20192 o Major bugfixes (directory authorities):
20193 - Stop marking every relay as having been down for one hour every
20194 time we restart a directory authority. These artificial downtimes
20195 were messing with our Stable and Guard flag calculations. Fixes
20196 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
20198 o Major bugfixes (hidden services):
20199 - Allow hidden service authentication to succeed again. When we
20200 refactored the hidden service introduction code back
20201 in 0.2.4.1-alpha, we didn't update the code that checks
20202 whether authentication information is present, causing all
20203 authentication checks to return "false". Fix for bug 8207; bugfix
20204 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
20206 o Minor features (relays, bridges):
20207 - Make bridge relays check once a minute for whether their IP
20208 address has changed, rather than only every 15 minutes. Resolves
20209 bugs 1913 and 1992.
20210 - Refactor resolve_my_address() so it returns the method by which we
20211 decided our public IP address (explicitly configured, resolved from
20212 explicit hostname, guessed from interfaces, learned by gethostname).
20213 Now we can provide more helpful log messages when a relay guesses
20214 its IP address incorrectly (e.g. due to unexpected lines in
20215 /etc/hosts). Resolves ticket 2267.
20216 - Teach bridge-using clients to avoid 0.2.2 bridges when making
20217 microdescriptor-related dir requests, and only fall back to normal
20218 descriptors if none of their bridges can handle microdescriptors
20219 (as opposed to the fix in ticket 4013, which caused them to fall
20220 back to normal descriptors if *any* of their bridges preferred
20221 them). Resolves ticket 4994.
20222 - Randomize the lifetime of our SSL link certificate, so censors can't
20223 use the static value for filtering Tor flows. Resolves ticket 8443;
20224 related to ticket 4014 which was included in 0.2.2.33.
20225 - Support a new version of the link protocol that allows 4-byte circuit
20226 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
20227 a possible resource exhaustion issue. Closes ticket 7351; implements
20230 o Minor features (portability):
20231 - Tweak the curve25519-donna*.c implementations to tolerate systems
20232 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
20233 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
20234 the signs of types during autoconf. This is better than our old
20235 approach, which didn't work when cross-compiling.
20236 - Detect the sign of enum values, rather than assuming that MSC is the
20237 only compiler where enum types are all signed. Fixes bug 7727;
20238 bugfix on 0.2.4.10-alpha.
20240 o Minor features (other):
20241 - Say "KBytes" rather than "KB" in the man page (for various values
20242 of K), to further reduce confusion about whether Tor counts in
20243 units of memory or fractions of units of memory. Resolves ticket 7054.
20244 - Clear the high bit on curve25519 public keys before passing them to
20245 our backend, in case we ever wind up using a backend that doesn't do
20246 so itself. If we used such a backend, and *didn't* clear the high bit,
20247 we could wind up in a situation where users with such backends would
20248 be distinguishable from users without. Fixes bug 8121; bugfix on
20250 - Update to the March 6 2013 Maxmind GeoLite Country database.
20252 o Minor bugfixes (clients):
20253 - When we receive a RELAY_END cell with the reason DONE, or with no
20254 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
20255 status as "connection refused". Previously we reported these cases
20256 as success but then immediately closed the connection. Fixes bug
20257 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
20258 - Downgrade an assertion in connection_ap_expire_beginning to an
20259 LD_BUG message. The fix for bug 8024 should prevent this message
20260 from displaying, but just in case, a warn that we can diagnose
20261 is better than more assert crashes. Fixes bug 8065; bugfix on
20263 - Lower path use bias thresholds to .80 for notice and .60 for warn.
20264 Also make the rate limiting flags for the path use bias log messages
20265 independent from the original path bias flags. Fixes bug 8161;
20266 bugfix on 0.2.4.10-alpha.
20268 o Minor bugfixes (relays):
20269 - Stop trying to resolve our hostname so often (e.g. every time we
20270 think about doing a directory fetch). Now we reuse the cached
20271 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
20272 and 2410 (bugfix on 0.1.2.2-alpha).
20273 - Stop sending a stray "(null)" in some cases for the server status
20274 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
20276 - When choosing which stream on a formerly stalled circuit to wake
20277 first, make better use of the platform's weak RNG. Previously,
20278 we had been using the % ("modulo") operator to try to generate a
20279 1/N chance of picking each stream, but this behaves badly with
20280 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
20282 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
20283 Irix's random() only return 15 bits; Solaris's random() returns more
20284 bits but its RAND_MAX says it only returns 15, and so on. Motivated
20285 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
20287 o Minor bugfixes (directory authorities):
20288 - Directory authorities now use less space when formatting identical
20289 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
20292 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
20293 - Avoid leaking memory if we fail to compute a consensus signature
20294 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
20295 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
20297 - Fix a memory leak during safe-cookie controller authentication.
20298 Bugfix on 0.2.3.13-alpha.
20299 - Avoid memory leak of IPv6 policy content if we fail to format it into
20300 a router descriptor. Bugfix on 0.2.4.7-alpha.
20302 o Minor bugfixes (other code correctness issues):
20303 - Avoid a crash if we fail to generate an extrainfo descriptor.
20304 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
20305 this is CID 718634.
20306 - When detecting the largest possible file descriptor (in order to
20307 close all file descriptors when launching a new program), actually
20308 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
20309 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
20311 - Fix a copy-and-paste error when adding a missing A1 to a routerset
20312 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
20313 Bugfix on 0.2.4.10-alpha.
20314 - Fix an impossible-to-trigger integer overflow when estimating how
20315 long our onionskin queue would take. (This overflow would require us
20316 to accept 4 million onionskins before processing 100 of them.) Fixes
20317 bug 8210; bugfix on 0.2.4.10-alpha.
20319 o Code simplification and refactoring:
20320 - Add a wrapper function for the common "log a message with a
20324 Changes in version 0.2.4.10-alpha - 2013-02-04
20325 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
20326 certain attacks that flood the network with relays; changes the queue
20327 for circuit create requests from a sized-based limit to a time-based
20328 limit; resumes building with MSVC on Windows; and fixes a wide variety
20331 o Major bugfixes (directory authority):
20332 - When computing directory thresholds, ignore any rejected-as-sybil
20333 nodes during the computation so that they can't influence Fast,
20334 Guard, etc. (We should have done this for proposal 109.) Fixes
20336 - When marking a node as a likely sybil, reset its uptime metrics
20337 to zero, so that it cannot time towards getting marked as Guard,
20338 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
20342 - When a TLS write is partially successful but incomplete, remember
20343 that the flushed part has been flushed, and notice that bytes were
20344 actually written. Reported and fixed pseudonymously. Fixes bug
20345 7708; bugfix on Tor 0.1.0.5-rc.
20346 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
20347 ID: these could be used to create unexpected streams and circuits
20348 which would count as "present" to some parts of Tor but "absent"
20349 to others, leading to zombie circuits and streams or to a bandwidth
20350 denial-of-service. Fixes bug 7889; bugfix on every released version
20351 of Tor. Reported by "oftc_must_be_destroyed".
20352 - Rename all macros in our local copy of queue.h to begin with "TOR_".
20353 This change seems the only good way to permanently prevent conflicts
20354 with queue.h on various operating systems. Fixes bug 8107; bugfix
20357 o Major features (relay):
20358 - Instead of limiting the number of queued onionskins (aka circuit
20359 create requests) to a fixed, hard-to-configure number, we limit
20360 the size of the queue based on how many we expect to be able to
20361 process in a given amount of time. We estimate the time it will
20362 take to process an onionskin based on average processing time
20363 of previous onionskins. Closes ticket 7291. You'll never have to
20364 configure MaxOnionsPending again.
20366 o Major features (portability):
20367 - Resume building correctly with MSVC and Makefile.nmake. This patch
20368 resolves numerous bugs and fixes reported by ultramage, including
20369 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
20370 - Make the ntor and curve25519 code build correctly with MSVC.
20371 Fix on 0.2.4.8-alpha.
20374 - When directory authorities are computing thresholds for flags,
20375 never let the threshold for the Fast flag fall below 4096
20376 bytes. Also, do not consider nodes with extremely low bandwidths
20377 when deciding thresholds for various directory flags. This change
20378 should raise our threshold for Fast relays, possibly in turn
20379 improving overall network performance; see ticket 1854. Resolves
20381 - The Tor client now ignores sub-domain components of a .onion
20382 address. This change makes HTTP "virtual" hosting
20383 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
20384 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
20385 hosted on the same hidden service. Implements proposal 204.
20386 - We compute the overhead from passing onionskins back and forth to
20387 cpuworkers, and report it when dumping statistics in response to
20388 SIGUSR1. Supports ticket 7291.
20390 o Minor features (path selection):
20391 - When deciding whether we have enough descriptors to build circuits,
20392 instead of looking at raw relay counts, look at which fraction
20393 of (bandwidth-weighted) paths we're able to build. This approach
20394 keeps clients from building circuits if their paths are likely to
20395 stand out statistically. The default fraction of paths needed is
20396 taken from the consensus directory; you can override it with the
20397 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
20398 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
20399 and we have GeoIP information, also exclude all nodes with unknown
20400 countries "??" and "A1". This behavior is controlled by the
20401 new GeoIPExcludeUnknown option: you can make such nodes always
20402 excluded with "GeoIPExcludeUnknown 1", and disable the feature
20403 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
20404 gets you the default behavior. Implements feature 7706.
20405 - Path Use Bias: Perform separate accounting for successful circuit
20406 use. Keep separate statistics on stream attempt rates versus stream
20407 success rates for each guard. Provide configurable thresholds to
20408 determine when to emit log messages or disable use of guards that
20409 fail too many stream attempts. Resolves ticket 7802.
20411 o Minor features (log messages):
20412 - When learning a fingerprint for a bridge, log its corresponding
20413 transport type. Implements ticket 7896.
20414 - Improve the log message when "Bug/attack: unexpected sendme cell
20415 from client" occurs, to help us track bug 8093.
20418 - Remove a couple of extraneous semicolons that were upsetting the
20419 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
20420 bugfix on 0.2.2.1-alpha.
20421 - Remove a source of rounding error during path bias count scaling;
20422 don't count cannibalized circuits as used for path bias until we
20423 actually try to use them; and fix a circuit_package_relay_cell()
20424 warning message about n_chan==NULL. Fixes bug 7802.
20425 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
20426 actually link against nacl when we're configured to use it. Fixes
20427 bug 7972; bugfix on 0.2.4.8-alpha.
20428 - Compile correctly with the --disable-curve25519 option. Fixes
20429 bug 8153; bugfix on 0.2.4.8-alpha.
20431 o Build improvements:
20432 - Do not report status verbosely from autogen.sh unless the -v flag
20433 is specified. Fixes issue 4664. Patch from Onizuka.
20434 - Replace all calls to snprintf() outside of src/ext with
20435 tor_snprintf(). Also remove the #define to replace snprintf with
20436 _snprintf on Windows; they have different semantics, and all of
20437 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
20438 - Try to detect if we are ever building on a platform where
20439 memset(...,0,...) does not set the value of a double to 0.0. Such
20440 platforms are permitted by the C standard, though in practice
20441 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
20442 currently support them, but it's better to detect them and fail
20443 than to perform erroneously.
20445 o Removed features:
20446 - Stop exporting estimates of v2 and v3 directory traffic shares
20447 in extrainfo documents. They were unneeded and sometimes inaccurate.
20448 Also stop exporting any v2 directory request statistics. Resolves
20450 - Drop support for detecting and warning about versions of Libevent
20451 before 1.3e. Nothing reasonable ships with them any longer;
20452 warning the user about them shouldn't be needed. Resolves ticket
20455 o Code simplifications and refactoring:
20456 - Rename "isin" functions to "contains", for grammar. Resolves
20458 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
20459 with the natural logarithm function from the system libm. Resolves
20463 Changes in version 0.2.4.9-alpha - 2013-01-15
20464 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
20465 work more robustly.
20468 - Fix backward compatibility logic when receiving an embedded ntor
20469 handshake tunneled in a CREATE cell. This clears up the "Bug:
20470 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
20474 Changes in version 0.2.4.8-alpha - 2013-01-14
20475 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
20476 risks, adds a new stronger and faster circuit handshake, and offers
20477 stronger and faster link encryption when both sides support it.
20480 - Preliminary support for directory guards (proposal 207): when
20481 possible, clients now use their entry guards for non-anonymous
20482 directory requests. This can help prevent client enumeration. Note
20483 that this behavior only works when we have a usable consensus
20484 directory, and when options about what to download are more or less
20485 standard. In the future we should re-bootstrap from our guards,
20486 rather than re-bootstrapping from the preconfigured list of
20487 directory sources that ships with Tor. Resolves ticket 6526.
20488 - Tor relays and clients now support a better CREATE/EXTEND cell
20489 format, allowing the sender to specify multiple address, identity,
20490 and handshake types. Implements Robert Ransom's proposal 200;
20491 closes ticket 7199.
20493 o Major features (new circuit handshake):
20494 - Tor now supports a new circuit extension handshake designed by Ian
20495 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
20496 circuit extension handshake, later called "TAP", was a bit slow
20497 (especially on the relay side), had a fragile security proof, and
20498 used weaker keys than we'd now prefer. The new circuit handshake
20499 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
20500 function, making it significantly more secure than the older
20501 handshake, and significantly faster. Tor can use one of two built-in
20502 pure-C curve25519-donna implementations by Adam Langley, or it
20503 can link against the "nacl" library for a tuned version if present.
20505 The built-in version is very fast for 64-bit systems when building
20506 with GCC. The built-in 32-bit version is still faster than the
20507 old TAP protocol, but using libnacl is better on most such hosts.
20509 Clients don't currently use this protocol by default, since
20510 comparatively few clients support it so far. To try it, set
20511 UseNTorHandshake to 1.
20513 Implements proposal 216; closes ticket 7202.
20515 o Major features (better link encryption):
20516 - Relays can now enable the ECDHE TLS ciphersuites when available
20517 and appropriate. These ciphersuites let us negotiate forward-secure
20518 TLS secret keys more safely and more efficiently than with our
20519 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
20520 public relays prefer the (faster) P224 group, and bridges prefer
20521 the (more common) P256 group; you can override this with the
20524 Enabling these ciphers was a little tricky, since for a long time,
20525 clients had been claiming to support them without actually doing
20526 so, in order to foil fingerprinting. But with the client-side
20527 implementation of proposal 198 in 0.2.3.17-beta, clients can now
20528 match the ciphers from recent Firefox versions *and* list the
20529 ciphers they actually mean, so relays can believe such clients
20530 when they advertise ECDHE support in their TLS ClientHello messages.
20532 This feature requires clients running 0.2.3.17-beta or later,
20533 and requires both sides to be running OpenSSL 1.0.0 or later
20534 with ECC support. OpenSSL 1.0.1, with the compile-time option
20535 "enable-ec_nistp_64_gcc_128", is highly recommended.
20537 Implements the relay side of proposal 198; closes ticket 7200.
20540 - Avoid crashing when, as a relay without IPv6-exit support, a
20541 client insists on getting an IPv6 address or nothing. Fixes bug
20542 7814; bugfix on 0.2.4.7-alpha.
20545 - Improve circuit build timeout handling for hidden services.
20546 In particular: adjust build timeouts more accurately depending
20547 upon the number of hop-RTTs that a particular circuit type
20548 undergoes. Additionally, launch intro circuits in parallel
20549 if they timeout, and take the first one to reply as valid.
20550 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
20551 separate error codes; or at least, don't break for that reason.
20552 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
20553 - Update to the January 2 2013 Maxmind GeoLite Country database.
20555 o Minor features (testing):
20556 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
20557 (P-256) Diffie-Hellman handshakes to src/or/bench.
20558 - Add benchmark functions to test onion handshake performance.
20560 o Minor features (path bias detection):
20561 - Alter the Path Bias log messages to be more descriptive in terms
20562 of reporting timeouts and other statistics.
20563 - Create three levels of Path Bias log messages, as opposed to just
20564 two. These are configurable via consensus as well as via the torrc
20565 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
20566 The default values are 0.70, 0.50, and 0.30 respectively.
20567 - Separate the log message levels from the decision to drop guards,
20568 which also is available via torrc option PathBiasDropGuards.
20569 PathBiasDropGuards still defaults to 0 (off).
20570 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
20571 in combination with PathBiasExtremeRate.
20572 - Increase the default values for PathBiasScaleThreshold and
20573 PathBiasCircThreshold from (200, 20) to (300, 150).
20574 - Add in circuit usage accounting to path bias. If we try to use a
20575 built circuit but fail for any reason, it counts as path bias.
20576 Certain classes of circuits where the adversary gets to pick your
20577 destination node are exempt from this accounting. Usage accounting
20578 can be specifically disabled via consensus parameter or torrc.
20579 - Convert all internal path bias state to double-precision floating
20580 point, to avoid roundoff error and other issues.
20581 - Only record path bias information for circuits that have completed
20582 *two* hops. Assuming end-to-end tagging is the attack vector, this
20583 makes us more resilient to ambient circuit failure without any
20584 detection capability loss.
20586 o Minor bugfixes (log messages):
20587 - Rate-limit the "No circuits are opened. Relaxed timeout for a
20588 circuit with channel state open..." message to once per hour to
20589 keep it from filling the notice logs. Mitigates bug 7799 but does
20590 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
20591 - Avoid spurious warnings when configuring multiple client ports of
20592 which only some are nonlocal. Previously, we had claimed that some
20593 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
20596 o Code simplifications and refactoring:
20597 - Get rid of a couple of harmless clang warnings, where we compared
20598 enums to ints. These warnings are newly introduced in clang 3.2.
20599 - Split the onion.c file into separate modules for the onion queue
20600 and the different handshakes it supports.
20601 - Remove the marshalling/unmarshalling code for sending requests to
20602 cpuworkers over a socket, and instead just send structs. The
20603 recipient will always be the same Tor binary as the sender, so
20604 any encoding is overkill.
20607 Changes in version 0.2.4.7-alpha - 2012-12-24
20608 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
20609 directory mirrors for more robust bootstrapping; fixes more issues where
20610 clients with changing network conditions refuse to make any circuits;
20611 adds initial support for exiting to IPv6 addresses; resumes being able
20612 to update our GeoIP database, and includes the geoip6 file this time;
20613 turns off the client-side DNS cache by default due to privacy risks;
20614 and fixes a variety of other issues.
20616 o Major features (client resilience):
20617 - Add a new "FallbackDir" torrc option to use when we can't use
20618 a directory mirror from the consensus (either because we lack a
20619 consensus, or because they're all down). Currently, all authorities
20620 are fallbacks by default, and there are no other default fallbacks,
20621 but that will change. This option will allow us to give clients a
20622 longer list of servers to try to get a consensus from when first
20623 connecting to the Tor network, and thereby reduce load on the
20624 directory authorities. Implements proposal 206, "Preconfigured
20625 directory sources for bootstrapping". We also removed the old
20626 "FallbackNetworkstatus" option, since we never got it working well
20627 enough to use it. Closes bug 572.
20628 - If we have no circuits open, use a relaxed timeout (the
20629 95-percentile cutoff) until a circuit succeeds. This heuristic
20630 should allow Tor to succeed at building circuits even when the
20631 network connection drastically changes. Should help with bug 3443.
20633 o Major features (IPv6):
20634 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
20635 connectivity, then set the IPv6Exit flag to 1. Also make sure your
20636 exit policy reads as you would like: the address * applies to all
20637 address families, whereas *4 is IPv4 address only, and *6 is IPv6
20638 addresses only. On the client side, you'll need to wait until the
20639 authorities have upgraded, wait for enough exits to support IPv6,
20640 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
20641 ticket 5547, implements proposal 117 as revised in proposal 208.
20643 We DO NOT recommend that clients with actual anonymity needs start
20644 using IPv6 over Tor yet, since not enough exits support it yet.
20646 o Major features (geoip database):
20647 - Maxmind began labelling Tor relays as being in country "A1",
20648 which breaks by-country node selection inside Tor. Now we use a
20649 script to replace "A1" ("Anonymous Proxy") entries in our geoip
20650 file with real country codes. This script fixes about 90% of "A1"
20651 entries automatically and uses manual country code assignments to
20652 fix the remaining 10%. See src/config/README.geoip for details.
20653 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
20654 Country database, as modified above.
20656 o Major bugfixes (client-side DNS):
20657 - Turn off the client-side DNS cache by default. Updating and using
20658 the DNS cache is now configurable on a per-client-port
20659 level. SOCKSPort, DNSPort, etc lines may now contain
20660 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
20661 cache these types of DNS answers when we receive them from an
20662 exit node in response to an application request on this port, and
20663 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
20664 cached DNS answers of these types, we shouldn't use them. It's
20665 potentially risky to use cached DNS answers at the client, since
20666 doing so can indicate to one exit what answers we've gotten
20667 for DNS lookups in the past. With IPv6, this becomes especially
20668 problematic. Using cached DNS answers for requests on the same
20669 circuit would present less linkability risk, since all traffic
20670 on a circuit is already linkable, but it would also provide
20671 little performance benefit: the exit node caches DNS replies
20672 too. Implements a simplified version of Proposal 205. Implements
20675 o Major bugfixes (other):
20676 - Alter circuit build timeout measurement to start at the point
20677 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
20678 initialization). This should make our timeout measurements more
20679 uniform. Previously, we were sometimes including ORconn setup time
20680 in our circuit build time measurements. Should resolve bug 3443.
20681 - Fix an assertion that could trigger in hibernate_go_dormant() when
20682 closing an or_connection_t: call channel_mark_for_close() rather
20683 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
20685 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
20686 7655; bugfix on 0.2.4.6-alpha.
20689 - Add a new torrc option "ServerTransportListenAddr" to let bridge
20690 operators select the address where their pluggable transports will
20691 listen for connections. Resolves ticket 7013.
20692 - Allow an optional $ before the node identity digest in the
20693 controller command GETINFO ns/id/<identity>, for consistency with
20694 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
20695 - Log packaged cell fullness as part of the heartbeat message.
20696 Diagnosis to try to determine the extent of bug 7743.
20698 o Minor features (IPv6):
20699 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
20700 prefer to hand out virtual IPv6 addresses, since there are more of
20701 them and we can't run out. To override this behavior and make IPv4
20702 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
20703 or DNSPort you're using for resolving. Implements ticket 7571.
20704 - AutomapHostsOnResolve responses are now randomized, to avoid
20705 annoying situations where Tor is restarted and applications
20706 connect to the wrong addresses.
20707 - Never try more than 1000 times to pick a new virtual address when
20708 AutomapHostsOnResolve is set. That's good enough so long as we
20709 aren't close to handing out our entire virtual address space;
20710 if you're getting there, it's best to switch to IPv6 virtual
20714 - The ADDRMAP command can no longer generate an ill-formed error
20715 code on a failed MAPADDRESS. It now says "internal" rather than
20716 an English sentence fragment with spaces in the middle. Bugfix on
20717 Tor 0.2.0.19-alpha.
20718 - Fix log messages and comments to avoid saying "GMT" when we mean
20719 "UTC". Fixes bug 6113.
20720 - Compile on win64 using mingw64. Fixes bug 7260; patches from
20722 - Fix a crash when debugging unit tests on Windows: deallocate a
20723 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
20724 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
20727 - The DirServer option is now DirAuthority, for consistency with
20728 current naming patterns. You can still use the old DirServer form.
20730 o Code simplification and refactoring:
20731 - Move the client-side address-map/virtual-address/DNS-cache code
20732 out of connection_edge.c into a new addressmap.c module.
20733 - Remove unused code for parsing v1 directories and "running routers"
20734 documents. Fixes bug 6887.
20737 Changes in version 0.2.3.25 - 2012-11-19
20738 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
20739 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
20740 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
20741 programmer, and friend. Unstinting in his dedication to the cause of
20742 freedom, he inspired and helped many of us as we began our work on
20743 anonymity, and inspires us still. Please honor his memory by writing
20744 software to protect people's freedoms, and by helping others to do so.
20746 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
20747 significantly reduced directory overhead (via microdescriptors),
20748 enormous crypto performance improvements for fast relays on new
20749 enough hardware, a new v3 TLS handshake protocol that can better
20750 resist fingerprinting, support for protocol obfuscation plugins (aka
20751 pluggable transports), better scalability for hidden services, IPv6
20752 support for bridges, performance improvements like allowing clients
20753 to skip the first round-trip on the circuit ("optimistic data") and
20754 refilling token buckets more often, a new "stream isolation" design
20755 to isolate different applications on different circuits, and many
20756 stability, security, and privacy fixes.
20759 - Tor tries to wipe potentially sensitive data after using it, so
20760 that if some subsequent security failure exposes Tor's memory,
20761 the damage will be limited. But we had a bug where the compiler
20762 was eliminating these wipe operations when it decided that the
20763 memory was no longer visible to a (correctly running) program,
20764 hence defeating our attempt at defense in depth. We fix that
20765 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
20766 is unlikely to optimize away. Future versions of Tor may use
20767 a less ridiculously heavy approach for this. Fixes bug 7352.
20768 Reported in an article by Andrey Karpov.
20771 - Fix a harmless bug when opting against publishing a relay descriptor
20772 because DisableNetwork is set. Fixes bug 7464; bugfix on
20776 Changes in version 0.2.4.6-alpha - 2012-11-13
20777 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
20778 makes our defense-in-depth memory wiping more reliable, and begins to
20779 count IPv6 addresses in bridge statistics,
20782 - Fix an assertion failure that could occur when closing a connection
20783 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
20785 - Tor tries to wipe potentially sensitive data after using it, so
20786 that if some subsequent security failure exposes Tor's memory,
20787 the damage will be limited. But we had a bug where the compiler
20788 was eliminating these wipe operations when it decided that the
20789 memory was no longer visible to a (correctly running) program,
20790 hence defeating our attempt at defense in depth. We fix that
20791 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
20792 is unlikely to optimize away. Future versions of Tor may use
20793 a less ridiculously heavy approach for this. Fixes bug 7352.
20794 Reported in an article by Andrey Karpov.
20797 - Add GeoIP database for IPv6 addresses. The new config option
20799 - Bridge statistics now count bridge clients connecting over IPv6:
20800 bridge statistics files now list "bridge-ip-versions" and
20801 extra-info documents list "geoip6-db-digest". The control protocol
20802 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
20803 implementation by "shkoo", addressing ticket 5055.
20806 - Warn when we are binding low ports when hibernation is enabled;
20807 previously we had warned when we were _advertising_ low ports with
20808 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
20809 - Fix a harmless bug when opting against publishing a relay descriptor
20810 because DisableNetwork is set. Fixes bug 7464; bugfix on
20812 - Add warning message when a managed proxy dies during configuration.
20813 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
20814 - Fix a linking error when building tor-fw-helper without miniupnp.
20815 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
20816 - Check for closing an or_connection_t without going through correct
20817 channel functions; emit a warning and then call
20818 connection_or_close_for_error() so we don't assert as in bugs 7212
20820 - Compile correctly on compilers without C99 designated initializer
20821 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
20822 - Avoid a possible assert that can occur when channel_send_destroy() is
20823 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
20824 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
20825 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
20826 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
20827 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
20829 o Code simplification and refactoring:
20830 - Start using OpenBSD's implementation of queue.h, so that we don't
20831 need to hand-roll our own pointer and list structures whenever we
20832 need them. (We can't rely on a sys/queue.h, since some operating
20833 systems don't have them, and the ones that do have them don't all
20834 present the same extensions.)
20837 Changes in version 0.2.4.5-alpha - 2012-10-25
20838 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
20839 two important security vulnerabilities that could lead to remotely
20840 triggerable relay crashes, fix a major bug that was preventing clients
20841 from choosing suitable exit nodes, and refactor some of our code.
20843 o Major bugfixes (security, also in 0.2.3.24-rc):
20844 - Fix a group of remotely triggerable assertion failures related to
20845 incorrect link protocol negotiation. Found, diagnosed, and fixed
20846 by "some guy from France". Fix for CVE-2012-2250; bugfix on
20848 - Fix a denial of service attack by which any directory authority
20849 could crash all the others, or by which a single v2 directory
20850 authority could crash everybody downloading v2 directory
20851 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
20853 o Major bugfixes (also in 0.2.3.24-rc):
20854 - When parsing exit policy summaries from microdescriptors, we had
20855 previously been ignoring the last character in each one, so that
20856 "accept 80,443,8080" would be treated by clients as indicating
20857 a node that allows access to ports 80, 443, and 808. That would
20858 lead to clients attempting connections that could never work,
20859 and ignoring exit nodes that would support their connections. Now
20860 clients parse these exit policy summaries correctly. Fixes bug 7192;
20861 bugfix on 0.2.3.1-alpha.
20863 o Minor bugfixes (also in 0.2.3.24-rc):
20864 - Clients now consider the ClientRejectInternalAddresses config option
20865 when using a microdescriptor consensus stanza to decide whether
20866 an exit relay would allow exiting to an internal address. Fixes
20867 bug 7190; bugfix on 0.2.3.1-alpha.
20870 - Only disable TLS session ticket support when running as a TLS
20871 server. Now clients will blend better with regular Firefox
20872 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
20874 o Code simplification and refactoring:
20875 - Start using OpenBSD's implementation of queue.h (originally by
20877 - Move the entry node code from circuitbuild.c to its own file.
20878 - Move the circuit build timeout tracking code from circuitbuild.c
20882 Changes in version 0.2.3.24-rc - 2012-10-25
20883 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
20884 could lead to remotely triggerable relay crashes, and fixes
20885 a major bug that was preventing clients from choosing suitable exit
20888 o Major bugfixes (security):
20889 - Fix a group of remotely triggerable assertion failures related to
20890 incorrect link protocol negotiation. Found, diagnosed, and fixed
20891 by "some guy from France". Fix for CVE-2012-2250; bugfix on
20893 - Fix a denial of service attack by which any directory authority
20894 could crash all the others, or by which a single v2 directory
20895 authority could crash everybody downloading v2 directory
20896 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
20899 - When parsing exit policy summaries from microdescriptors, we had
20900 previously been ignoring the last character in each one, so that
20901 "accept 80,443,8080" would be treated by clients as indicating
20902 a node that allows access to ports 80, 443, and 808. That would
20903 lead to clients attempting connections that could never work,
20904 and ignoring exit nodes that would support their connections. Now
20905 clients parse these exit policy summaries correctly. Fixes bug 7192;
20906 bugfix on 0.2.3.1-alpha.
20909 - Clients now consider the ClientRejectInternalAddresses config option
20910 when using a microdescriptor consensus stanza to decide whether
20911 an exit relay would allow exiting to an internal address. Fixes
20912 bug 7190; bugfix on 0.2.3.1-alpha.
20915 Changes in version 0.2.4.4-alpha - 2012-10-20
20916 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
20917 vulnerability introduced by a change in OpenSSL, fixes a remotely
20918 triggerable assert, and adds new channel_t and circuitmux_t abstractions
20919 that will make it easier to test new connection transport and cell
20920 scheduling algorithms.
20922 o New directory authorities (also in 0.2.3.23-rc):
20923 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
20924 authority. Closes ticket 5749.
20926 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
20927 - Disable TLS session tickets. OpenSSL's implementation was giving
20928 our TLS session keys the lifetime of our TLS context objects, when
20929 perfect forward secrecy would want us to discard anything that
20930 could decrypt a link connection as soon as the link connection
20931 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
20932 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
20933 - Discard extraneous renegotiation attempts once the V3 link
20934 protocol has been initiated. Failure to do so left us open to
20935 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
20936 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
20938 o Internal abstraction features:
20939 - Introduce new channel_t abstraction between circuits and
20940 or_connection_t to allow for implementing alternate OR-to-OR
20941 transports. A channel_t is an abstract object which can either be a
20942 cell-bearing channel, which is responsible for authenticating and
20943 handshaking with the remote OR and transmitting cells to and from
20944 it, or a listening channel, which spawns new cell-bearing channels
20945 at the request of remote ORs. Implements part of ticket 6465.
20946 - Also new is the channel_tls_t subclass of channel_t, adapting it
20947 to the existing or_connection_t code. The V2/V3 protocol handshaking
20948 code which formerly resided in command.c has been moved below the
20949 channel_t abstraction layer and may be found in channeltls.c now.
20950 Implements the rest of ticket 6465.
20951 - Introduce new circuitmux_t storing the queue of circuits for
20952 a channel; this encapsulates and abstracts the queue logic and
20953 circuit selection policy, and allows the latter to be overridden
20954 easily by switching out a policy object. The existing EWMA behavior
20955 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
20957 o Required libraries:
20958 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
20959 strongly recommended.
20962 - Warn users who run hidden services on a Tor client with
20963 UseEntryGuards disabled that their hidden services will be
20964 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
20965 attack which motivated Tor to support entry guards in the first
20966 place). Resolves ticket 6889.
20967 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
20968 dhill. Resolves ticket 6982.
20969 - Option OutboundBindAddress can be specified multiple times and
20970 accepts IPv6 addresses. Resolves ticket 6876.
20972 o Minor bugfixes (also in 0.2.3.23-rc):
20973 - Don't serve or accept v2 hidden service descriptors over a
20974 relay's DirPort. It's never correct to do so, and disabling it
20975 might make it more annoying to exploit any bugs that turn up in the
20976 descriptor-parsing code. Fixes bug 7149.
20977 - Fix two cases in src/or/transports.c where we were calling
20978 fmt_addr() twice in a parameter list. Bug found by David
20979 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
20980 - Fix memory leaks whenever we logged any message about the "path
20981 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
20982 - When relays refuse a "create" cell because their queue of pending
20983 create cells is too big (typically because their cpu can't keep up
20984 with the arrival rate), send back reason "resource limit" rather
20985 than reason "internal", so network measurement scripts can get a
20986 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
20989 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
20990 - Free some more still-in-use memory at exit, to make hunting for
20991 memory leaks easier. Resolves bug 7029.
20992 - When a Tor client gets a "truncated" relay cell, the first byte of
20993 its payload specifies why the circuit was truncated. We were
20994 ignoring this 'reason' byte when tearing down the circuit, resulting
20995 in the controller not being told why the circuit closed. Now we
20996 pass the reason from the truncated cell to the controller. Bugfix
20997 on 0.1.2.3-alpha; fixes bug 7039.
20998 - Downgrade "Failed to hand off onionskin" messages to "debug"
20999 severity, since they're typically redundant with the "Your computer
21000 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
21001 - Make clients running with IPv6 bridges connect over IPv6 again,
21002 even without setting new config options ClientUseIPv6 and
21003 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
21004 - Use square brackets around IPv6 addresses in numerous places
21005 that needed them, including log messages, HTTPS CONNECT proxy
21006 requests, TransportProxy statefile entries, and pluggable transport
21007 extra-info lines. Fixes bug 7011; patch by David Fifield.
21009 o Code refactoring and cleanup:
21010 - Source files taken from other packages now reside in src/ext;
21011 previously they were scattered around the rest of Tor.
21012 - Avoid use of reserved identifiers in our C code. The C standard
21013 doesn't like us declaring anything that starts with an
21014 underscore, so let's knock it off before we get in trouble. Fix
21015 for bug 1031; bugfix on the first Tor commit.
21018 Changes in version 0.2.3.23-rc - 2012-10-20
21019 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
21020 vulnerability introduced by a change in OpenSSL, and fixes a variety
21021 of smaller bugs in preparation for the release.
21023 o New directory authorities:
21024 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21025 authority. Closes ticket 5749.
21027 o Major bugfixes (security/privacy):
21028 - Disable TLS session tickets. OpenSSL's implementation was giving
21029 our TLS session keys the lifetime of our TLS context objects, when
21030 perfect forward secrecy would want us to discard anything that
21031 could decrypt a link connection as soon as the link connection
21032 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21033 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21034 - Discard extraneous renegotiation attempts once the V3 link
21035 protocol has been initiated. Failure to do so left us open to
21036 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21037 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21040 - Fix a possible crash bug when checking for deactivated circuits
21041 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21042 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21044 o Minor bugfixes (on 0.2.3.x):
21045 - Fix two cases in src/or/transports.c where we were calling
21046 fmt_addr() twice in a parameter list. Bug found by David
21047 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21048 - Convert an assert in the pathbias code to a log message. The assert
21049 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21050 bugfix on 0.2.3.17-beta.
21051 - Fix memory leaks whenever we logged any message about the "path
21052 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21054 o Minor bugfixes (on 0.2.2.x and earlier):
21055 - Don't serve or accept v2 hidden service descriptors over a relay's
21056 DirPort. It's never correct to do so, and disabling it might
21057 make it more annoying to exploit any bugs that turn up in the
21058 descriptor-parsing code. Fixes bug 7149.
21059 - When relays refuse a "create" cell because their queue of pending
21060 create cells is too big (typically because their cpu can't keep up
21061 with the arrival rate), send back reason "resource limit" rather
21062 than reason "internal", so network measurement scripts can get a
21063 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
21064 - Correct file sizes when reading binary files on Cygwin, to avoid
21065 a bug where Tor would fail to read its state file. Fixes bug 6844;
21066 bugfix on 0.1.2.7-alpha.
21067 - Avoid undefined behavior when parsing the list of supported
21068 rendezvous/introduction protocols in a hidden service descriptor.
21069 Previously, Tor would have confused (as-yet-unused) protocol version
21070 numbers greater than 32 with lower ones on many platforms. Fixes
21071 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
21073 o Documentation fixes:
21074 - Clarify that hidden services are TCP only. Fixes bug 6024.
21077 Changes in version 0.2.4.3-alpha - 2012-09-22
21078 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
21079 assertion, resumes letting relays test reachability of their DirPort,
21080 and cleans up a bunch of smaller bugs.
21083 - Fix an assertion failure in tor_timegm() that could be triggered
21084 by a badly formatted directory object. Bug found by fuzzing with
21085 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21088 - Fix a possible crash bug when checking for deactivated circuits
21089 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21090 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21091 - Allow routers to detect that their own DirPorts are running. When
21092 we removed support for versions_supports_begindir, we also
21093 accidentally removed the mechanism we used to self-test our
21094 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
21095 bugfix on 0.2.4.2-alpha.
21097 o Security features:
21098 - Switch to a completely time-invariant approach for picking nodes
21099 weighted by bandwidth. Our old approach would run through the
21100 part of the loop after it had made its choice slightly slower
21101 than it ran through the part of the loop before it had made its
21102 choice. Addresses ticket 6538.
21103 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
21104 by tor2web clients allows hidden services to identify tor2web
21105 clients through their repeated selection of the same rendezvous
21106 and introduction point circuit endpoints (their guards). Resolves
21110 - Enable Tor to read configuration, state, and key information from
21111 a FIFO. Previously Tor would only read from files with a positive
21112 stat.st_size. Code from meejah; fixes bug 6044.
21115 - Correct file sizes when reading binary files on Cygwin, to avoid
21116 a bug where Tor would fail to read its state file. Fixes bug 6844;
21117 bugfix on 0.1.2.7-alpha.
21118 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
21119 bugfix on 0.2.0.3-alpha.
21120 - When complaining about a client port on a public address, log
21121 which address we're complaining about. Fixes bug 4020; bugfix on
21122 0.2.3.3-alpha. Patch by Tom Fitzhenry.
21123 - Convert an assert in the pathbias code to a log message. The assert
21124 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21125 bugfix on 0.2.3.17-beta.
21126 - Our new buildsystem was overzealous about rebuilding manpages: it
21127 would rebuild them all whenever any one of them changed. Now our
21128 dependency checking should be correct. Fixes bug 6843; bugfix on
21130 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
21131 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
21132 - Correct log printout about which address family is preferred
21133 when connecting to a bridge with both an IPv4 and IPv6 OR port.
21134 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
21136 o Minor bugfixes (code cleanliness):
21137 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
21138 with large values. This situation was untriggered, but nevertheless
21139 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
21140 - Reject consensus votes with more than 64 known-flags. We aren't even
21141 close to that limit yet, and our code doesn't handle it correctly.
21142 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
21143 - Avoid undefined behavior when parsing the list of supported
21144 rendezvous/introduction protocols in a hidden service descriptor.
21145 Previously, Tor would have confused (as-yet-unused) protocol version
21146 numbers greater than 32 with lower ones on many platforms. Fixes
21147 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
21148 - Fix handling of rendezvous client authorization types over 8.
21149 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
21150 - Fix building with older versions of GCC (2.95, for one) that don't
21151 like preprocessor directives inside macro arguments. Found by
21152 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
21153 - Switch weighted node selection rule from using a list of doubles
21154 to using a list of int64_t. This change should make the process
21155 slightly easier to debug and maintain. Needed to finish ticket 6538.
21157 o Code simplification and refactoring:
21158 - Move the generic "config" code into a new file, and have "config.c"
21159 hold only torrc- and state-related code. Resolves ticket 6823.
21160 - Move the core of our "choose a weighted element at random" logic
21161 into its own function, and give it unit tests. Now the logic is
21162 testable, and a little less fragile too.
21163 - Removed the testing_since field of node_t, which hasn't been used
21164 for anything since 0.2.0.9-alpha.
21166 o Documentation fixes:
21167 - Clarify that hidden services are TCP only. Fixes bug 6024.
21168 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
21172 Changes in version 0.2.3.22-rc - 2012-09-11
21173 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
21177 - Fix an assertion failure in tor_timegm() that could be triggered
21178 by a badly formatted directory object. Bug found by fuzzing with
21179 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21182 - Avoid segfault when starting up having run with an extremely old
21183 version of Tor and parsing its state file. Fixes bug 6801; bugfix
21187 Changes in version 0.2.2.39 - 2012-09-11
21188 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
21192 - Fix an assertion failure in tor_timegm() that could be triggered
21193 by a badly formatted directory object. Bug found by fuzzing with
21194 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21195 - Do not crash when comparing an address with port value 0 to an
21196 address policy. This bug could have been used to cause a remote
21197 assertion failure by or against directory authorities, or to
21198 allow some applications to crash clients. Fixes bug 6690; bugfix
21202 Changes in version 0.2.4.2-alpha - 2012-09-10
21203 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
21204 raises the default rate limiting even more, and makes the bootstrapping
21205 log messages less noisy.
21208 - Automatically forward the TCP ports of pluggable transport
21209 proxies using tor-fw-helper if PortForwarding is enabled. Implements
21213 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
21214 to 1GB/1GB. The previous defaults were intended to be "basically
21215 infinite", but it turns out they're now limiting our 100mbit+
21216 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
21217 last time we raised it).
21220 - Detect when we're running with a version of OpenSSL other than the
21221 one we compiled with. This has occasionally given people hard-to-
21223 - Log fewer lines at level "notice" about our OpenSSL and Libevent
21224 versions and capabilities when everything is going right. Resolves
21225 part of ticket 6736.
21226 - Directory authorities no long accept descriptors for any version of
21227 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
21228 These versions are insecure, unsupported, or both. Implements
21232 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
21233 to start with a triple-underscore so the controller won't touch it.
21234 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
21235 - Avoid segfault when starting up having run with an extremely old
21236 version of Tor and parsing its state file. Fixes bug 6801; bugfix
21238 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
21239 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
21240 - Don't follow the NULL pointer if microdescriptor generation fails.
21241 (This does not appear to be triggerable, but it's best to be safe.)
21242 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
21243 - Fix mis-declared dependencies on src/common/crypto.c and
21244 src/or/tor_main.c that could break out-of-tree builds under some
21245 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
21246 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
21247 6778; bugfix on 0.2.4.1-alpha.
21248 - Fix a harmless (in this case) build warning for implicitly
21249 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
21251 o Removed features:
21252 - Now that all versions before 0.2.2.x are disallowed, we no longer
21253 need to work around their missing features. Thus we can remove a
21254 bunch of compatibility code.
21256 o Code refactoring:
21257 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
21258 TCP ports to forward. In the past it only accepted two ports:
21259 the ORPort and the DirPort.
21262 Changes in version 0.2.4.1-alpha - 2012-09-05
21263 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
21264 bridgedb; lets relays use IPv6 addresses and directory authorities
21265 advertise them; and switches to a cleaner build interface.
21267 This is the first alpha release in a new series, so expect there to
21268 be bugs. Users who would rather test out a more stable branch should
21269 stay with 0.2.3.x for now.
21271 o Major features (bridges):
21272 - Bridges now report the pluggable transports they support to the
21273 bridge authority, so it can pass the supported transports on to
21274 bridgedb and/or eventually do reachability testing. Implements
21277 o Major features (IPv6):
21278 - Bridge authorities now accept IPv6 bridge addresses and include
21279 them in network status documents. Implements ticket 5534.
21280 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
21281 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
21282 to happen. Implements ticket 5535.
21283 - All kind of relays, not just bridges, can now advertise an IPv6
21284 OR port. Implements ticket 6362.
21285 - Directory authorities vote on IPv6 OR ports using the new consensus
21286 method 14. Implements ticket 6363.
21288 o Major features (build):
21289 - Switch to a nonrecursive Makefile structure. Now instead of each
21290 Makefile.am invoking other Makefile.am's, there is a master
21291 Makefile.am that includes the others. This change makes our build
21292 process slightly more maintainable, and improves parallelism for
21293 building with make -j. Original patch by Stewart Smith; various
21294 fixes by Jim Meyering.
21295 - Where available, we now use automake's "silent" make rules by
21296 default, so that warnings are easier to spot. You can get the old
21297 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
21299 o Minor features (code security and spec conformance):
21300 - Clear keys and key-derived material left on the stack in
21301 rendservice.c and rendclient.c. Check return value of
21302 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
21303 These fixes should make us more forward-secure against cold-boot
21304 attacks and the like. Fixes bug 2385.
21305 - Reject EXTEND cells sent to nonexistent streams. According to the
21306 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
21307 we were only checking for stream IDs that were currently in use.
21308 Found while hunting for more instances of bug 6271. Bugfix on
21309 0.0.2pre8, which introduced incremental circuit construction.
21311 o Minor features (streamlining);
21312 - No longer include the "opt" prefix when generating routerinfos
21313 or v2 directories: it has been needless since Tor 0.1.2. Closes
21315 - Remove some now-needless code that tried to aggressively flush
21316 OR connections as data was added to them. Since 0.2.0.1-alpha, our
21317 cell queue logic has saved us from the failure mode that this code
21318 was supposed to prevent. Removing this code will limit the number
21319 of baroque control flow paths through Tor's network logic. Reported
21320 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
21322 o Minor features (controller):
21323 - Add a "GETINFO signal/names" control port command. Implements
21325 - Provide default values for all options via "GETINFO config/defaults".
21326 Implements ticket 4971.
21328 o Minor features (IPv6):
21329 - New config option "AuthDirHasIPv6Connectivity 1" that directory
21330 authorities should set if they have IPv6 connectivity and want to
21331 do reachability tests for IPv6 relays. Implements feature 5974.
21332 - A relay with an IPv6 OR port now sends that address in NETINFO
21333 cells (in addition to its other address). Implements ticket 6364.
21335 o Minor features (log messages):
21336 - Omit the first heartbeat log message, because it never has anything
21337 useful to say, and it clutters up the bootstrapping messages.
21338 Resolves ticket 6758.
21339 - Don't log about reloading the microdescriptor cache at startup. Our
21340 bootstrap warnings are supposed to tell the user when there's a
21341 problem, and our bootstrap notices say when there isn't. Resolves
21342 ticket 6759; bugfix on 0.2.2.6-alpha.
21343 - Don't log "I learned some more directory information" when we're
21344 reading cached directory information. Reserve it for when new
21345 directory information arrives in response to a fetch. Resolves
21347 - Prevent rounding error in path bias counts when scaling
21348 them down, and use the correct scale factor default. Also demote
21349 some path bias related log messages down a level and make others
21350 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
21351 - We no longer warn so much when generating manpages from their
21354 o Code simplifications and refactoring:
21355 - Enhance our internal sscanf replacement so that we can eliminate
21356 the last remaining uses of the system sscanf. (Though those uses
21357 of sscanf were safe, sscanf itself is generally error prone, so
21358 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
21360 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
21361 - Move last_reachable and testing_since from routerinfo_t to node_t.
21362 Implements ticket 5529.
21363 - Add replaycache_t structure, functions and unit tests, then refactor
21364 rend_service_introduce() to be more clear to read, improve, debug,
21365 and test. Resolves bug 6177.
21366 - Finally remove support for malloc_good_size and malloc_usable_size.
21367 We had hoped that these functions would let us eke a little more
21368 memory out of our malloc implementation. Unfortunately, the only
21369 implementations that provided these functions are also ones that
21370 are already efficient about not overallocation: they never got us
21371 more than 7 or so bytes per allocation. Removing them saves us a
21372 little code complexity and a nontrivial amount of build complexity.
21374 o New requirements:
21375 - Tor maintainers now require Automake version 1.9 or later to build
21376 Tor from the Git repository. (Automake is not required when building
21377 from a source distribution.)
21380 Changes in version 0.2.3.21-rc - 2012-09-05
21381 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
21382 series. It fixes a trio of potential security bugs, fixes a bug where
21383 we were leaving some of the fast relays out of the microdescriptor
21384 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
21385 and cleans up other smaller issues.
21387 o Major bugfixes (security):
21388 - Tear down the circuit if we get an unexpected SENDME cell. Clients
21389 could use this trick to make their circuits receive cells faster
21390 than our flow control would have allowed, or to gum up the network,
21391 or possibly to do targeted memory denial-of-service attacks on
21392 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
21393 from July 2002, before the release of Tor 0.0.0. We had committed
21394 this patch previously, but we had to revert it because of bug 6271.
21395 Now that 6271 is fixed, this patch appears to work.
21396 - Reject any attempt to extend to an internal address. Without
21397 this fix, a router could be used to probe addresses on an internal
21398 network to see whether they were accepting connections. Fixes bug
21399 6710; bugfix on 0.0.8pre1.
21400 - Do not crash when comparing an address with port value 0 to an
21401 address policy. This bug could have been used to cause a remote
21402 assertion failure by or against directory authorities, or to
21403 allow some applications to crash clients. Fixes bug 6690; bugfix
21407 - Remove the upper bound on microdescriptor length. We were hitting
21408 the limit for routers with complex exit policies or family
21409 declarations, causing clients to not use them. Fixes the first
21410 piece of bug 6404; fix on 0.2.2.6-alpha.
21411 - Detect "ORPort 0" as meaning, uniformly, that we're not running
21412 as a relay. Previously, some of our code would treat the presence
21413 of any ORPort line as meaning that we should act like a relay,
21414 even though our new listener code would correctly not open any
21415 ORPorts for ORPort 0. Similar bugs in other Port options are also
21416 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
21419 - Avoid a pair of double-free and use-after-mark bugs that can
21420 occur with certain timings in canceled and re-received DNS
21421 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
21422 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
21423 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
21424 - Allow one-hop directory fetching circuits the full "circuit build
21425 timeout" period, rather than just half of it, before failing them
21426 and marking the relay down. This fix should help reduce cases where
21427 clients declare relays (or worse, bridges) unreachable because
21428 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
21429 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
21431 - Authorities no longer include any router in their microdescriptor
21432 consensuses for which they couldn't generate or agree on a
21433 microdescriptor. Fixes the second piece of bug 6404; fix on
21435 - Detect and reject attempts to specify both "FooPort" and
21436 "FooPort 0" in the same configuration domain. (It's still okay
21437 to have a FooPort in your configuration file, and use "FooPort 0"
21438 on the command line to disable it.) Fixes the second half of bug
21439 6507; bugfix on 0.2.3.3-alpha.
21440 - Make wildcarded addresses (that is, ones beginning with "*.") work
21441 when provided via the controller's MapAddress command. Previously,
21442 they were accepted, but we never actually noticed that they were
21443 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
21444 - Avoid crashing on a malformed state file where EntryGuardPathBias
21445 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
21446 - Add a (probably redundant) memory clear between iterations of
21447 the router status voting loop, to prevent future coding errors
21448 where data might leak between iterations of the loop. Resolves
21451 o Minor bugfixes (log messages):
21452 - Downgrade "set buildtimeout to low value" messages to "info"
21453 severity; they were never an actual problem, there was never
21454 anything reasonable to do about them, and they tended to spam logs
21455 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
21456 - Downgrade path-bias warning messages to "info". We'll try to get
21457 them working better in 0.2.4. Add internal circuit construction
21458 state to protect against the noisy warn message "Unexpectedly high
21459 circuit_successes". Also add some additional rate-limited notice
21460 messages to help determine the root cause of the warn. Fixes bug
21461 6475. Bugfix against 0.2.3.17-beta.
21462 - Move log message when unable to find a microdesc in a routerstatus
21463 entry to parse time. Previously we'd spam this warning every time
21464 we tried to figure out which microdescriptors to download. Fixes
21465 the third piece of bug 6404; fix on 0.2.3.18-rc.
21468 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
21469 change when the authority is deciding whether to accept a newly
21470 uploaded descriptor. Implements ticket 6423.
21471 - Add missing documentation for consensus and microdesc files.
21472 Resolves ticket 6732.
21475 Changes in version 0.2.2.38 - 2012-08-12
21476 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
21477 attack that could in theory leak path information.
21480 - Avoid an uninitialized memory read when reading a vote or consensus
21481 document that has an unrecognized flavor name. This read could
21482 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21483 - Try to leak less information about what relays a client is
21484 choosing to a side-channel attacker. Previously, a Tor client would
21485 stop iterating through the list of available relays as soon as it
21486 had chosen one, thus finishing a little earlier when it picked
21487 a router earlier in the list. If an attacker can recover this
21488 timing information (nontrivial but not proven to be impossible),
21489 they could learn some coarse-grained information about which relays
21490 a client was picking (middle nodes in particular are likelier to
21491 be affected than exits). The timing attack might be mitigated by
21492 other factors (see bug 6537 for some discussion), but it's best
21493 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21496 Changes in version 0.2.3.20-rc - 2012-08-05
21497 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
21498 series. It fixes a pair of code security bugs and a potential anonymity
21499 issue, updates our RPM spec files, and cleans up other smaller issues.
21502 - Avoid read-from-freed-memory and double-free bugs that could occur
21503 when a DNS request fails while launching it. Fixes bug 6480;
21504 bugfix on 0.2.0.1-alpha.
21505 - Avoid an uninitialized memory read when reading a vote or consensus
21506 document that has an unrecognized flavor name. This read could
21507 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21508 - Try to leak less information about what relays a client is
21509 choosing to a side-channel attacker. Previously, a Tor client would
21510 stop iterating through the list of available relays as soon as it
21511 had chosen one, thus finishing a little earlier when it picked
21512 a router earlier in the list. If an attacker can recover this
21513 timing information (nontrivial but not proven to be impossible),
21514 they could learn some coarse-grained information about which relays
21515 a client was picking (middle nodes in particular are likelier to
21516 be affected than exits). The timing attack might be mitigated by
21517 other factors (see bug 6537 for some discussion), but it's best
21518 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21521 - Try to make the warning when giving an obsolete SOCKSListenAddress
21522 a little more useful.
21523 - Terminate active server managed proxies if Tor stops being a
21524 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
21525 - Provide a better error message about possible OSX Asciidoc failure
21526 reasons. Fixes bug 6436.
21527 - Warn when Tor is configured to use accounting in a way that can
21528 link a hidden service to some other hidden service or public
21529 address. Resolves ticket 6490.
21532 - Check return value of fputs() when writing authority certificate
21533 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
21534 - Ignore ServerTransportPlugin lines when Tor is not configured as
21535 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
21536 - When disabling guards for having too high a proportion of failed
21537 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
21541 - Update our default RPM spec files to work with mock and rpmbuild
21542 on RHEL/Fedora. They have an updated set of dependencies and
21543 conflicts, a fix for an ancient typo when creating the "_tor"
21544 user, and better instructions. Thanks to Ondrej Mikle for the
21545 patch series. Fixes bug 6043.
21548 - Make it possible to set the TestingTorNetwork configuration
21549 option using AlternateDirAuthority and AlternateBridgeAuthority
21550 as an alternative to setting DirServer. Addresses ticket 6377.
21553 - Clarify the documentation for the Alternate*Authority options.
21555 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
21557 o Code simplification and refactoring:
21558 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
21559 10 lines. Also, don't nest them. Doing so in the past has
21560 led to hard-to-debug code. The new style is to use the
21561 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
21564 Changes in version 0.2.3.19-rc - 2012-07-06
21565 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
21566 series. It fixes the compile on Windows, reverts to a GeoIP database
21567 that isn't as broken, and fixes a flow control bug that has been around
21568 since the beginning of Tor.
21571 - Fix a bug handling SENDME cells on nonexistent streams that could
21572 result in bizarre window values. Report and patch contributed
21573 pseudonymously. Fixes part of bug 6271. This bug was introduced
21574 before the first Tor release, in svn commit r152.
21575 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
21576 June 2012 database, Maxmind marked many Tor relays as country "A1",
21577 which will cause risky behavior for clients that set EntryNodes
21578 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
21579 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
21580 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
21583 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
21584 bugfix on 0.2.1.10-alpha.
21587 Changes in version 0.2.3.18-rc - 2012-06-28
21588 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
21589 series. It fixes a few smaller bugs, but generally appears stable.
21590 Please test it and let us know whether it is!
21593 - Allow wildcarded mapaddress targets to be specified on the
21594 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
21595 - Make our linker option detection code more robust against linkers
21596 such as on FreeBSD 8, where a bad combination of options completes
21597 successfully but makes an unrunnable binary. Fixes bug 6173;
21598 bugfix on 0.2.3.17-beta.
21600 o Minor bugfixes (on 0.2.2.x and earlier):
21601 - Avoid a false positive in the util/threads unit test by increasing
21602 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
21603 - Replace "Sending publish request" log messages with "Launching
21604 upload", so that they no longer confusingly imply that we're
21605 sending something to a directory we might not even be connected
21606 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
21607 - Make sure to set *socket_error in all error cases in
21608 connection_connect(), so it can't produce a warning about
21609 errno being zero from errno_to_orconn_end_reason(). Bugfix on
21610 0.2.1.1-alpha; resolves ticket 6028.
21611 - Downgrade "Got a certificate, but we already have it" log messages
21612 from warning to info, except when we're a dirauth. Fixes bug 5238;
21613 bugfix on 0.2.1.7-alpha.
21614 - When checking for requested signatures on the latest consensus
21615 before serving it to a client, make sure to check the right
21616 consensus flavor. Bugfix on 0.2.2.6-alpha.
21617 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
21618 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
21620 o Minor bugfixes (on 0.2.3.x):
21621 - Make format_helper_exit_status() avoid unnecessary space padding
21622 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
21624 - Downgrade a message about cleaning the microdescriptor cache to
21625 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
21626 - Log a BUG message at severity INFO if we have a networkstatus with
21627 a missing entry for some microdescriptor. Continues on a patch
21629 - Improve the log message when a managed proxy fails to launch. Fixes
21630 bug 5099; bugfix on 0.2.3.6-alpha.
21631 - Don't do DNS lookups when parsing corrupted managed proxy protocol
21632 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
21633 - When formatting wildcarded address mappings for the controller,
21634 be sure to include "*." as appropriate. Partially fixes bug 6244;
21635 bugfix on 0.2.3.9-alpha.
21636 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
21637 Bugfix on 0.2.3.13-alpha.
21638 - Stop logging messages about running with circuit timeout learning
21639 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
21640 - Disable a spurious warning about reading on a marked and flushing
21641 connection. We shouldn't be doing that, but apparently we
21642 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
21643 - Fix a bug that stopped AllowDotExit from working on addresses
21644 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
21647 o Code simplification, refactoring, unit tests:
21648 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
21649 Libevent's notion of cached time when possible.
21650 - Remove duplicate code for invoking getrlimit() from control.c.
21651 - Add a unit test for the environment_variable_names_equal function.
21654 - Document the --defaults-torrc option, and the new (in 0.2.3)
21655 semantics for overriding, extending, and clearing lists of
21656 options. Closes bug 4748.
21659 Changes in version 0.2.3.17-beta - 2012-06-15
21660 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
21661 gets our TLS handshake back on track for being able to blend in with
21662 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
21663 with Vidalia, and otherwise continues to get us closer to a release
21667 - Enable gcc and ld hardening by default. Resolves ticket 5210.
21668 - Update TLS cipher list to match Firefox 8 and later. Resolves
21670 - Implement the client side of proposal 198: remove support for
21671 clients falsely claiming to support standard ciphersuites that
21672 they can actually provide. As of modern OpenSSL versions, it's not
21673 necessary to fake any standard ciphersuite, and doing so prevents
21674 us from using better ciphersuites in the future, since servers
21675 can't know whether an advertised ciphersuite is really supported or
21676 not. Some hosts -- notably, ones with very old versions of OpenSSL
21677 or where OpenSSL has been built with ECC disabled -- will stand
21678 out because of this change; TBB users should not be affected.
21681 - Change the default value for DynamicDHGroups (introduced in
21682 0.2.3.9-alpha) to 0. This feature can make Tor relays less
21683 identifiable by their use of the mod_ssl DH group, but at
21684 the cost of some usability (#4721) and bridge tracing (#6087)
21685 regressions. Resolves ticket 5598.
21686 - Send a CRLF at the end of each STATUS_* control protocol event. This
21687 bug tickled a bug in Vidalia which would make it freeze. Fixes
21688 bug 6094; bugfix on 0.2.3.16-alpha.
21691 - Disable writing on marked-for-close connections when they are
21692 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
21693 bug 5263; bugfix on 0.0.2pre13, where we first added a special
21694 case for flushing marked connections.
21695 - Detect SSL handshake even when the initial attempt to write the
21696 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
21697 - Change the AllowDotExit rules so they should actually work.
21698 We now enforce AllowDotExit only immediately after receiving an
21699 address via SOCKS or DNSPort: other sources are free to provide
21700 .exit addresses after the resolution occurs. Fixes bug 3940;
21701 bugfix on 0.2.2.1-alpha.
21702 - Fix a (harmless) integer overflow in cell statistics reported by
21703 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
21704 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
21705 right places and never depends on the consensus parameters or
21706 computes adaptive timeouts when it is disabled. Fixes bug 5049;
21707 bugfix on 0.2.2.14-alpha.
21708 - When building Tor on Windows with -DUNICODE (not default), ensure
21709 that error messages, filenames, and DNS server names are always
21710 NUL-terminated when we convert them to a single-byte encoding.
21711 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
21712 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
21713 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
21714 - Fix an edge case where TestingTorNetwork is set but the authorities
21715 and relays all have an uptime of zero, where the private Tor network
21716 could briefly lack support for hidden services. Fixes bug 3886;
21717 bugfix on 0.2.2.18-alpha.
21718 - Correct the manpage's descriptions for the default values of
21719 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
21721 - Fix the documentation for the --hush and --quiet command line
21722 options, which changed their behavior back in 0.2.3.3-alpha.
21723 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
21727 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
21728 more information to it, so that we can track it down in case it
21729 returns again. Mitigates bug 5235.
21730 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
21731 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
21732 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
21733 - Warn the user when HTTPProxy, but no other proxy type, is
21734 configured. This can cause surprising behavior: it doesn't send
21735 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
21736 directory traffic only. Resolves ticket 4663.
21737 - Issue a notice if a guard completes less than 40% of your circuits.
21738 Threshold is configurable by torrc option PathBiasNoticeRate and
21739 consensus parameter pb_noticepct. There is additional, off-by-
21740 default code to disable guards which fail too many circuits.
21741 Addresses ticket 5458.
21742 - Update to the June 6 2012 Maxmind GeoLite Country database.
21744 o Code simplifications and refactoring:
21745 - Remove validate_pluggable_transports_config(): its warning
21746 message is now handled by connection_or_connect().
21749 Changes in version 0.2.2.37 - 2012-06-06
21750 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
21751 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
21755 - Work around a bug in OpenSSL that broke renegotiation with TLS
21756 1.1 and TLS 1.2. Without this workaround, all attempts to speak
21757 the v2 Tor connection protocol when both sides were using OpenSSL
21758 1.0.1 would fail. Resolves ticket 6033.
21759 - When waiting for a client to renegotiate, don't allow it to add
21760 any bytes to the input buffer. This fixes a potential DoS issue.
21761 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
21762 - Fix an edge case where if we fetch or publish a hidden service
21763 descriptor, we might build a 4-hop circuit and then use that circuit
21764 for exiting afterwards -- even if the new last hop doesn't obey our
21765 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
21768 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
21769 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
21772 - Tell GCC and Clang to check for any errors in format strings passed
21773 to the tor_v*(print|scan)f functions.
21776 Changes in version 0.2.3.16-alpha - 2012-06-05
21777 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
21778 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
21779 currently). It also fixes a variety of smaller bugs and other cleanups
21780 that get us closer to a release candidate.
21782 o Major bugfixes (general):
21783 - Work around a bug in OpenSSL that broke renegotiation with TLS
21784 1.1 and TLS 1.2. Without this workaround, all attempts to speak
21785 the v2 Tor connection protocol when both sides were using OpenSSL
21786 1.0.1 would fail. Resolves ticket 6033.
21787 - When waiting for a client to renegotiate, don't allow it to add
21788 any bytes to the input buffer. This fixes a potential DoS issue.
21789 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
21790 - Pass correct OR address to managed proxies (like obfsproxy),
21791 even when ORListenAddress is used. Fixes bug 4865; bugfix on
21793 - The advertised platform of a router now includes only its operating
21794 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
21795 service pack level (for Windows) or its CPU architecture (for Unix).
21796 We also no longer include the "git-XYZ" tag in the version. Resolves
21799 o Major bugfixes (clients):
21800 - If we are unable to find any exit that supports our predicted ports,
21801 stop calling them predicted, so that we don't loop and build
21802 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
21803 which introduced predicted ports.
21804 - Fix an edge case where if we fetch or publish a hidden service
21805 descriptor, we might build a 4-hop circuit and then use that circuit
21806 for exiting afterwards -- even if the new last hop doesn't obey our
21807 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
21808 - Check at each new consensus whether our entry guards were picked
21809 long enough ago that we should rotate them. Previously, we only
21810 did this check at startup, which could lead to us holding a guard
21811 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
21812 - When fetching a bridge descriptor from a bridge authority,
21813 always do so anonymously, whether we have been able to open
21814 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
21815 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
21816 but we'll need to wait for bug 6010 before it's actually usable.
21818 o Major bugfixes (directory authorities):
21819 - When computing weight parameters, behave more robustly in the
21820 presence of a bad bwweightscale value. Previously, the authorities
21821 would crash if they agreed on a sufficiently broken weight_scale
21822 value: now, they use a reasonable default and carry on. Partial
21823 fix for 5786; bugfix on 0.2.2.17-alpha.
21824 - Check more thoroughly to prevent a rogue authority from
21825 double-voting on any consensus directory parameter. Previously,
21826 authorities would crash in this case if the total number of
21827 votes for any parameter exceeded the number of active voters,
21828 but would let it pass otherwise. Partial fix for bug 5786; bugfix
21832 - Rate-limit log messages when asked to connect anonymously to
21833 a private address. When these hit, they tended to hit fast and
21834 often. Also, don't bother trying to connect to addresses that we
21835 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
21836 reply makes us think we have been lied to, even when the address the
21837 client tried to connect to was "localhost." Resolves ticket 2822.
21838 - Allow packagers to insert an extra string in server descriptor
21839 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
21840 Resolves the rest of ticket 2988.
21841 - Raise the threshold of server descriptors needed (75%) and exit
21842 server descriptors needed (50%) before we will declare ourselves
21843 bootstrapped. This will make clients start building circuits a
21844 little later, but makes the initially constructed circuits less
21845 skewed and less in conflict with further directory fetches. Fixes
21847 - Close any connection that sends unrecognized junk before the
21848 handshake. Solves an issue noted in bug 4369.
21849 - Improve log messages about managed transports. Resolves ticket 5070.
21850 - Tag a bridge's descriptor as "never to be sent unencrypted".
21851 This shouldn't matter, since bridges don't open non-anonymous
21852 connections to the bridge authority and don't allow unencrypted
21853 directory connections from clients, but we might as well make
21854 sure. Closes bug 5139.
21855 - Expose our view of whether we have gone dormant to the controller,
21856 via a new "GETINFO dormant" value. Torbutton and other controllers
21857 can use this to avoid doing periodic requests through Tor while
21858 it's dormant (bug 4718). Fixes bug 5954.
21859 - Tell GCC and Clang to check for any errors in format strings passed
21860 to the tor_v*(print|scan)f functions.
21861 - Update to the May 1 2012 Maxmind GeoLite Country database.
21863 o Minor bugfixes (already included in 0.2.2.36):
21864 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
21865 Fixes bug 5346; bugfix on 0.0.8pre3.
21866 - Correct parsing of certain date types in parse_http_time().
21867 Without this patch, If-Modified-Since would behave
21868 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
21869 Esteban Manchado Velázques.
21870 - Make our number-parsing functions always treat too-large values
21871 as an error, even when those values exceed the width of the
21872 underlying type. Previously, if the caller provided these
21873 functions with minima or maxima set to the extreme values of the
21874 underlying integer type, these functions would return those
21875 values on overflow rather than treating overflow as an error.
21876 Fixes part of bug 5786; bugfix on 0.0.9.
21877 - If we hit the error case where routerlist_insert() replaces an
21878 existing (old) server descriptor, make sure to remove that
21879 server descriptor from the old_routers list. Fix related to bug
21880 1776. Bugfix on 0.2.2.18-alpha.
21881 - Clarify the behavior of MaxCircuitDirtiness with hidden service
21882 circuits. Fixes issue 5259.
21884 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
21885 - Prevent a null-pointer dereference when receiving a data cell
21886 for a nonexistent stream when the circuit in question has an
21887 empty deliver window. We don't believe this is triggerable,
21888 since we don't currently allow deliver windows to become empty,
21889 but the logic is tricky enough that it's better to make the code
21890 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
21891 - Fix a memory leak when trying to launch a DNS request when the
21892 network is disabled or the nameservers are unconfigurable. Fixes
21893 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
21894 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
21895 - Don't hold a Windows file handle open for every file mapping;
21896 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
21898 - Avoid O(n^2) performance characteristics when parsing a large
21899 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
21900 - Format more doubles with %f, not %lf. Patch from grarpamp to make
21901 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
21903 - Make our replacement implementation of strtok_r() compatible with
21904 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
21905 bugfix on 0.2.2.1-alpha.
21906 - Fix a NULL-pointer dereference on a badly formed
21907 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
21908 bugfix on 0.2.2.9-alpha.
21909 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
21910 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
21911 - Defensively refactor rend_mid_rendezvous() so that protocol
21912 violations and length checks happen in the beginning. Fixes
21914 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
21915 that IPv6 stuff will compile on MSVC, and compilation issues
21916 will be easier to track down. Fixes bug 5861.
21918 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
21919 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
21920 resource exhaustion, so that clients can adjust their load to
21921 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
21922 started using END_STREAM_REASON_RESOURCELIMIT.
21923 - Don't check for whether the address we're using for outbound
21924 connections has changed until after the outbound connection has
21925 completed. On Windows, getsockname() doesn't succeed until the
21926 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
21927 - If the configuration tries to set MyFamily on a bridge, refuse to
21928 do so, and warn about the security implications. Fixes bug 4657;
21929 bugfix on 0.2.0.3-alpha.
21930 - If the client fails to set a reasonable set of ciphersuites
21931 during its v2 handshake renegotiation, allow the renegotiation to
21932 continue nevertheless (i.e. send all the required certificates).
21933 Fixes bug 4591; bugfix on 0.2.0.20-rc.
21934 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
21935 option is set to 0 (which Vidalia version 0.2.16 now does when
21936 a SAVECONF attempt fails), perform other actions that SIGHUP
21937 usually causes (like reopening the logs). Fixes bug 5095; bugfix
21939 - If we fail to write a microdescriptor to the disk cache, do not
21940 continue replacing the old microdescriptor file. Fixes bug 2954;
21941 bugfix on 0.2.2.6-alpha.
21942 - Exit nodes don't need to fetch certificates for authorities that
21943 they don't recognize; only directory authorities, bridges,
21944 and caches need to do that. Fixes part of bug 2297; bugfix on
21946 - Correctly handle checking the permissions on the parent
21947 directory of a control socket in the root directory. Bug found
21948 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
21950 - When told to add a bridge with the same digest as a preexisting
21951 bridge but a different addr:port, change the addr:port as
21952 requested. Previously we would not notice the change. Fixes half
21953 of bug 5603; fix on 0.2.2.26-beta.
21954 - End AUTHCHALLENGE error messages (in the control protocol) with
21955 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
21957 o Minor bugfixes (on 0.2.3.x):
21958 - Turn an assertion (that the number of handshakes received as a
21959 server is not < 1) into a warning. Fixes bug 4873; bugfix on
21961 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
21962 we had reversed them when the answer was cached.) Fixes bug
21963 5723; bugfix on 0.2.3.1-alpha.
21964 - Work correctly on Linux systems with accept4 support advertised in
21965 their headers, but without accept4 support in the kernel. Fix
21966 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
21967 - When told to add a bridge with the same addr:port as a preexisting
21968 bridge but a different transport, change the transport as
21969 requested. Previously we would not notice the change. Fixes half
21970 of bug 5603; fix on 0.2.3.2-alpha.
21971 - Avoid a "double-reply" warning when replying to a SOCKS request
21972 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
21973 bugfix on 0.2.3.4-alpha.
21974 - Fix a bug where a bridge authority crashes if it has seen no
21975 directory requests when it's time to write statistics to disk.
21976 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
21978 - Don't try to open non-control listeners when DisableNetwork is set.
21979 Previously, we'd open all listeners, then immediately close them.
21980 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
21981 - Don't abort the managed proxy protocol if the managed proxy
21982 sends us an unrecognized line; ignore it instead. Fixes bug
21983 5910; bugfix on 0.2.3.9-alpha.
21984 - Fix a compile warning in crypto.c when compiling with clang 3.1.
21985 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
21986 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
21987 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
21988 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
21989 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
21990 - Resolve numerous small warnings and build issues with MSVC. Resolves
21993 o Documentation fixes:
21994 - Improve the manual's documentation for the NT Service command-line
21995 options. Addresses ticket 3964.
21996 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
21997 - Document the changes to the ORPort and DirPort options, and the
21998 fact that {OR/Dir}ListenAddress is now unnecessary (and
21999 therefore deprecated). Resolves ticket 5597.
22002 - Remove the torrc.bridge file: we don't use it for anything, and
22003 it had become badly desynchronized from torrc.sample. Resolves
22007 Changes in version 0.2.2.36 - 2012-05-24
22008 Tor 0.2.2.36 updates the addresses for two of the eight directory
22009 authorities, fixes some potential anonymity and security issues,
22010 and fixes several crash bugs.
22012 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
22013 known flaws, and nobody should be using them. You should upgrade. If
22014 you're using a Linux or BSD and its packages are obsolete, stop using
22015 those packages and upgrade anyway.
22017 o Directory authority changes:
22018 - Change IP address for maatuska (v3 directory authority).
22019 - Change IP address for ides (v3 directory authority), and rename
22023 - When building or running with any version of OpenSSL earlier
22024 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22025 versions have a bug (CVE-2011-4576) in which their block cipher
22026 padding includes uninitialized data, potentially leaking sensitive
22027 information to any peer with whom they make a SSLv3 connection. Tor
22028 does not use SSL v3 by default, but a hostile client or server
22029 could force an SSLv3 connection in order to gain information that
22030 they shouldn't have been able to get. The best solution here is to
22031 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22032 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22033 to make sure that the bug can't happen.
22034 - Never use a bridge or a controller-supplied node as an exit, even
22035 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22036 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22037 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22038 - Only build circuits if we have a sufficient threshold of the total
22039 descriptors that are marked in the consensus with the "Exit"
22040 flag. This mitigates an attack proposed by wanoskarnet, in which
22041 all of a client's bridges collude to restrict the exit nodes that
22042 the client knows about. Fixes bug 5343.
22043 - Provide controllers with a safer way to implement the cookie
22044 authentication mechanism. With the old method, if another locally
22045 running program could convince a controller that it was the Tor
22046 process, then that program could trick the controller into telling
22047 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22048 authentication method uses a challenge-response approach to prevent
22049 this attack. Fixes bug 5185; implements proposal 193.
22052 - Avoid logging uninitialized data when unable to decode a hidden
22053 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22054 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22055 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22057 - Fix builds when the path to sed, openssl, or sha1sum contains
22058 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22060 - Correct our replacements for the timeradd() and timersub() functions
22061 on platforms that lack them (for example, Windows). The timersub()
22062 function is used when expiring circuits, while timeradd() is
22063 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
22064 bugfix on 0.2.2.24-alpha.
22065 - Fix the SOCKET_OK test that we use to tell when socket
22066 creation fails so that it works on Win64. Fixes part of bug 4533;
22067 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
22070 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
22071 Fixes bug 5346; bugfix on 0.0.8pre3.
22072 - Make our number-parsing functions always treat too-large values
22073 as an error, even when those values exceed the width of the
22074 underlying type. Previously, if the caller provided these
22075 functions with minima or maxima set to the extreme values of the
22076 underlying integer type, these functions would return those
22077 values on overflow rather than treating overflow as an error.
22078 Fixes part of bug 5786; bugfix on 0.0.9.
22079 - Older Linux kernels erroneously respond to strange nmap behavior
22080 by having accept() return successfully with a zero-length
22081 socket. When this happens, just close the connection. Previously,
22082 we would try harder to learn the remote address: but there was
22083 no such remote address to learn, and our method for trying to
22084 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
22085 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
22086 - Correct parsing of certain date types in parse_http_time().
22087 Without this patch, If-Modified-Since would behave
22088 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
22089 Esteban Manchado Velázques.
22090 - Change the BridgePassword feature (part of the "bridge community"
22091 design, which is not yet implemented) to use a time-independent
22092 comparison. The old behavior might have allowed an adversary
22093 to use timing to guess the BridgePassword value. Fixes bug 5543;
22094 bugfix on 0.2.0.14-alpha.
22095 - Detect and reject certain misformed escape sequences in
22096 configuration values. Previously, these values would cause us
22097 to crash if received in a torrc file or over an authenticated
22098 control port. Bug found by Esteban Manchado Velázquez, and
22099 independently by Robert Connolly from Matta Consulting who further
22100 noted that it allows a post-authentication heap overflow. Patch
22101 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
22102 bugfix on 0.2.0.16-alpha.
22103 - Fix a compile warning when using the --enable-openbsd-malloc
22104 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
22105 - During configure, detect when we're building with clang version
22106 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
22107 CFLAGS. clang doesn't support them yet.
22108 - When sending an HTTP/1.1 proxy request, include a Host header.
22109 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
22110 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
22111 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
22112 - If we hit the error case where routerlist_insert() replaces an
22113 existing (old) server descriptor, make sure to remove that
22114 server descriptor from the old_routers list. Fix related to bug
22115 1776. Bugfix on 0.2.2.18-alpha.
22117 o Minor bugfixes (documentation and log messages):
22118 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
22119 Fixes bug 4856; bugfix on Tor 0.0.6.
22120 - Update "ClientOnly" man page entry to explain that there isn't
22121 really any point to messing with it. Resolves ticket 5005.
22122 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
22123 directory authority option (introduced in Tor 0.2.2.34).
22124 - Downgrade the "We're missing a certificate" message from notice
22125 to info: people kept mistaking it for a real problem, whereas it
22126 is seldom the problem even when we are failing to bootstrap. Fixes
22127 bug 5067; bugfix on 0.2.0.10-alpha.
22128 - Correctly spell "connect" in a log message on failure to create a
22129 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
22130 - Clarify the behavior of MaxCircuitDirtiness with hidden service
22131 circuits. Fixes issue 5259.
22134 - Directory authorities now reject versions of Tor older than
22135 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
22136 inclusive. These versions accounted for only a small fraction of
22137 the Tor network, and have numerous known security issues. Resolves
22139 - Update to the May 1 2012 Maxmind GeoLite Country database.
22142 - When sending or relaying a RELAY_EARLY cell, we used to convert
22143 it to a RELAY cell if the connection was using the v1 link
22144 protocol. This was a workaround for older versions of Tor, which
22145 didn't handle RELAY_EARLY cells properly. Now that all supported
22146 versions can handle RELAY_EARLY cells, and now that we're enforcing
22147 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
22148 remove this workaround. Addresses bug 4786.
22151 Changes in version 0.2.3.15-alpha - 2012-04-30
22152 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
22153 the development branch build on Windows again.
22155 o Minor bugfixes (on 0.2.2.x and earlier):
22156 - Make sure that there are no unhandled pending TLS errors before
22157 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
22158 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
22159 Bugfix on 0.1.0.5-rc; fixes bug 4528.
22160 - Fix an assert that directory authorities could trigger on sighup
22161 during some configuration state transitions. We now don't treat
22162 it as a fatal error when the new descriptor we just generated in
22163 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
22164 - After we pick a directory mirror, we would refuse to use it if
22165 it's in our ExcludeExitNodes list, resulting in mysterious failures
22166 to bootstrap for people who just wanted to avoid exiting from
22167 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
22168 - When building with --enable-static-tor on OpenBSD, do not
22169 erroneously attempt to link -lrt. Fixes bug 5103.
22171 o Minor bugfixes (on 0.2.3.x):
22172 - When Tor is built with kernel headers from a recent (last few
22173 years) Linux kernel, do not fail to run on older (pre-2.6.28
22174 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
22175 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
22176 and 0.2.3.12-alpha.
22177 - Fix compilation with miniupnpc version 1.6; patch from
22178 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
22179 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
22180 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
22181 - Fix compilation on platforms without unistd.h, or where environ
22182 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
22185 - Directory authorities are now a little more lenient at accepting
22186 older router descriptors, or newer router descriptors that don't
22187 make big changes. This should help ameliorate past and future
22188 issues where routers think they have uploaded valid descriptors,
22189 but the authorities don't think so. Fix for ticket 2479.
22190 - Make the code that clients use to detect an address change be
22191 IPv6-aware, so that it won't fill clients' logs with error
22192 messages when trying to get the IPv4 address of an IPv6
22193 connection. Implements ticket 5537.
22195 o Removed features:
22196 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
22197 authorities needed to use it for a while to keep the network working
22198 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
22199 that was six months ago. As of now, it should no longer be needed
22203 Changes in version 0.2.3.14-alpha - 2012-04-23
22204 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
22205 candidate. It also dramatically speeds up AES: fast relays should
22206 consider switching to the newer OpenSSL library.
22208 o Directory authority changes:
22209 - Change IP address for ides (v3 directory authority), and rename
22213 - Avoid logging uninitialized data when unable to decode a hidden
22214 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22215 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22216 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22218 - If authorities are unable to get a v2 consensus document from other
22219 directory authorities, they no longer fall back to fetching
22220 them from regular directory caches. Fixes bug 5635; bugfix on
22221 0.2.2.26-beta, where routers stopped downloading v2 consensus
22222 documents entirely.
22223 - When we start a Tor client with a normal consensus already cached,
22224 be willing to download a microdescriptor consensus. Fixes bug 4011;
22225 fix on 0.2.3.1-alpha.
22227 o Major features (performance):
22228 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
22229 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
22230 vectorized AES implementations as appropriate. These can be much,
22231 much faster than other AES implementations.
22233 o Minor bugfixes (0.2.2.x and earlier):
22234 - Don't launch more than 10 service-side introduction-point circuits
22235 for a hidden service in five minutes. Previously, we would consider
22236 launching more introduction-point circuits if at least one second
22237 had passed without any introduction-point circuits failing. Fixes
22238 bug 4607; bugfix on 0.0.7pre1.
22239 - Change the BridgePassword feature (part of the "bridge community"
22240 design, which is not yet implemented) to use a time-independent
22241 comparison. The old behavior might have allowed an adversary
22242 to use timing to guess the BridgePassword value. Fixes bug 5543;
22243 bugfix on 0.2.0.14-alpha.
22244 - Enforce correct return behavior of tor_vsscanf() when the '%%'
22245 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
22246 - When sending an HTTP/1.1 proxy request, include a Host header.
22247 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
22248 - Don't log that we have "decided to publish new relay descriptor"
22249 unless we are actually publishing a descriptor. Fixes bug 3942;
22250 bugfix on 0.2.2.28-beta.
22252 o Minor bugfixes (0.2.3.x):
22253 - Fix a bug where a bridge authority crashes (on a failed assert)
22254 if it has seen no directory requests when it's time to write
22255 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
22256 - Fix bug stomping on ORPort option NoListen and ignoring option
22257 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
22258 - In the testsuite, provide a large enough buffer in the tor_sscanf
22259 unit test. Otherwise we'd overrun that buffer and crash during
22260 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
22262 - Make sure we create the keys directory if it doesn't exist and we're
22263 about to store the dynamic Diffie-Hellman parameters. Fixes bug
22264 5572; bugfix on 0.2.3.13-alpha.
22265 - Fix a small memory leak when trying to decode incorrect base16
22266 authenticator during SAFECOOKIE authentication. Found by
22267 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
22270 - Add more information to a log statement that might help track down
22271 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
22272 non-IP address" messages (or any Bug messages, for that matter!),
22273 please let us know about it.
22274 - Relays now understand an IPv6 address when they get one from a
22275 directory server. Resolves ticket 4875.
22276 - Resolve IPv6 addresses in bridge and entry statistics to country
22277 code "??" which means we at least count them. Resolves ticket 5053;
22278 improves on 0.2.3.9-alpha.
22279 - Update to the April 3 2012 Maxmind GeoLite Country database.
22280 - Begin a doc/state-contents.txt file to explain the contents of
22281 the Tor state file. Fixes bug 2987.
22283 o Default torrc changes:
22284 - Stop listing "socksport 9050" in torrc.sample. We open a socks
22285 port on 9050 by default anyway, so this should not change anything
22287 - Stop mentioning the deprecated *ListenAddress options in
22288 torrc.sample. Fixes bug 5438.
22289 - Document unit of bandwidth related options in sample torrc.
22292 o Removed features:
22293 - The "torify" script no longer supports the "tsocks" socksifier
22294 tool, since tsocks doesn't support DNS and UDP right for Tor.
22295 Everyone should be using torsocks instead. Fixes bugs 3530 and
22296 5180. Based on a patch by "ugh".
22298 o Code refactoring:
22299 - Change the symmetric cipher interface so that creating and
22300 initializing a stream cipher are no longer separate functions.
22301 - Remove all internal support for unpadded RSA. We never used it, and
22302 it would be a bad idea to start.
22305 Changes in version 0.2.3.13-alpha - 2012-03-26
22306 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
22307 in managed pluggable transports, as well as providing other cleanups
22308 that get us closer to a release candidate.
22310 o Directory authority changes:
22311 - Change IP address for maatuska (v3 directory authority).
22314 - Provide controllers with a safer way to implement the cookie
22315 authentication mechanism. With the old method, if another locally
22316 running program could convince a controller that it was the Tor
22317 process, then that program could trick the controller into telling
22318 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22319 authentication method uses a challenge-response approach to prevent
22320 this attack. Fixes bug 5185, implements proposal 193.
22321 - Never use a bridge or a controller-supplied node as an exit, even
22322 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22323 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22324 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22325 - Only build circuits if we have a sufficient threshold of the total
22326 descriptors that are marked in the consensus with the "Exit"
22327 flag. This mitigates an attack proposed by wanoskarnet, in which
22328 all of a client's bridges collude to restrict the exit nodes that
22329 the client knows about. Fixes bug 5343.
22331 o Major bugfixes (on Tor 0.2.3.x):
22332 - Avoid an assert when managed proxies like obfsproxy are configured,
22333 and we receive HUP signals or setconf attempts too rapidly. This
22334 situation happens most commonly when Vidalia tries to attach to
22335 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
22336 bugfix on 0.2.3.6-alpha.
22337 - Fix a relay-side pluggable transports bug where managed proxies were
22338 unreachable from the Internet, because Tor asked them to bind on
22339 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
22340 - Stop discarding command-line arguments when TestingTorNetwork
22341 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
22342 0.2.3.9-alpha, where task 4552 added support for two layers of
22344 - Resume allowing the unit tests to run in gdb. This was accidentally
22345 made impossible when the DisableDebuggerAttachment option was
22346 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
22347 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
22348 0.2.3.11-alpha. Reported by Anthony G. Basile.
22350 o Minor bugfixes (on 0.2.2.x and earlier):
22351 - Ensure we don't cannibalize circuits that are longer than three hops
22352 already, so we don't end up making circuits with 5 or more
22353 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
22354 0.1.0.1-rc which introduced cannibalization.
22355 - Detect and reject certain misformed escape sequences in
22356 configuration values. Previously, these values would cause us
22357 to crash if received in a torrc file or over an authenticated
22358 control port. Bug found by Esteban Manchado Velázquez, and
22359 independently by Robert Connolly from Matta Consulting who further
22360 noted that it allows a post-authentication heap overflow. Patch
22361 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
22362 bugfix on 0.2.0.16-alpha.
22363 - Fix a compile warning when using the --enable-openbsd-malloc
22364 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
22365 - Directory caches no longer refuse to clean out descriptors because
22366 of missing v2 networkstatus documents, unless they're configured
22367 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
22368 0.2.2.26-beta. Patch by Daniel Bryg.
22369 - Update to the latest version of the tinytest unit testing framework.
22370 This includes a couple of bugfixes that can be relevant for
22371 running forked unit tests on Windows, and removes all reserved
22374 o Minor bugfixes (on 0.2.3.x):
22375 - On a failed pipe() call, don't leak file descriptors. Fixes bug
22376 4296; bugfix on 0.2.3.1-alpha.
22377 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
22378 until after we have received a CERTS cell. Fixes bug 4361; bugfix
22379 on 0.2.3.6-alpha. Patch by "frosty".
22380 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
22381 option, so that the IP stack doesn't decide to use it for IPv4
22382 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
22383 - Ensure that variables set in Tor's environment cannot override
22384 environment variables that Tor passes to a managed
22385 pluggable-transport proxy. Previously, Tor would pass every
22386 variable in its environment to managed proxies along with the new
22387 ones, in such a way that on many operating systems, the inherited
22388 environment variables would override those which Tor tried to
22389 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
22390 bugfix on 0.2.3.9-alpha for Windows.
22393 - A wide variety of new unit tests by Esteban Manchado Velázquez.
22394 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
22395 - Update to the March 6 2012 Maxmind GeoLite Country database.
22398 Changes in version 0.2.3.12-alpha - 2012-02-13
22399 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
22400 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
22401 when Tor is configured to use a pluggable transport like obfsproxy.
22404 - Fix builds when the path to sed, openssl, or sha1sum contains
22405 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22407 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
22408 connections. This change should allow busy exit relays to stop
22409 running out of available sockets as quickly. Fixes bug 4950;
22410 bugfix on 0.2.2.26-beta.
22411 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
22412 would ask the bridge for microdescriptors, which are only supported
22413 in 0.2.3.x, and then fail to bootstrap when it didn't get the
22414 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
22415 - Properly set up obfsproxy's environment when in managed mode. The
22416 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
22417 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
22418 5076 and 5082; bugfix on 0.2.3.6-alpha.
22421 - Use the dead_strip option when building Tor on OS X. This reduces
22422 binary size by almost 19% when linking openssl and libevent
22423 statically, which we do for Tor Browser Bundle.
22424 - Fix broken URLs in the sample torrc file, and tell readers about
22425 the OutboundBindAddress, ExitPolicyRejectPrivate, and
22426 PublishServerDescriptor options. Addresses bug 4652.
22427 - Update to the February 7 2012 Maxmind GeoLite Country database.
22430 - Downgrade the "We're missing a certificate" message from notice
22431 to info: people kept mistaking it for a real problem, whereas it
22432 is seldom the problem even when we are failing to bootstrap. Fixes
22433 bug 5067; bugfix on 0.2.0.10-alpha.
22434 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
22435 managed pluggable transport server proxy's environment.
22436 Previously, we would put it there, even though Tor doesn't
22437 implement an 'extended server port' yet, and even though Tor
22438 almost certainly isn't listening at that address. For now, we set
22439 it to an empty string to avoid crashing older obfsproxies. Bugfix
22441 - Log the heartbeat message every HeartbeatPeriod seconds, not every
22442 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
22443 0.2.3.1-alpha. Bug reported by Scott Bennett.
22444 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
22445 bugfix on 0.2.3.11-alpha.
22446 - Update "ClientOnly" man page entry to explain that there isn't
22447 really any point to messing with it. Resolves ticket 5005.
22448 - Use the correct CVE number for CVE-2011-4576 in our comments and
22449 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
22452 o Code simplifications and refactoring:
22453 - Use the _WIN32 macro throughout our code to detect Windows.
22454 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
22458 Changes in version 0.2.3.11-alpha - 2012-01-22
22459 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
22460 the last step of the plan to limit maximum circuit length, includes
22461 a wide variety of hidden service performance and correctness fixes,
22462 works around an OpenSSL security flaw if your distro is too stubborn
22463 to upgrade, and fixes a bunch of smaller issues.
22466 - Now that Tor 0.2.0.x is completely deprecated, enable the final
22467 part of "Proposal 110: Avoiding infinite length circuits" by
22468 refusing all circuit-extend requests that do not use a relay_early
22469 cell. This change helps Tor resist a class of denial-of-service
22470 attacks by limiting the maximum circuit length.
22471 - Adjust the number of introduction points that a hidden service
22472 will try to maintain based on how long its introduction points
22473 remain in use and how many introductions they handle. Fixes
22475 - Try to use system facilities for enumerating local interface
22476 addresses, before falling back to our old approach (which was
22477 binding a UDP socket, and calling getsockname() on it). That
22478 approach was scaring OS X users whose draconian firewall
22479 software warned about binding to UDP sockets, regardless of
22480 whether packets were sent. Now we try to use getifaddrs(),
22481 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
22482 system supports. Resolves ticket 1827.
22484 o Major security workaround:
22485 - When building or running with any version of OpenSSL earlier
22486 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22487 versions have a bug (CVE-2011-4576) in which their block cipher
22488 padding includes uninitialized data, potentially leaking sensitive
22489 information to any peer with whom they make a SSLv3 connection. Tor
22490 does not use SSL v3 by default, but a hostile client or server
22491 could force an SSLv3 connection in order to gain information that
22492 they shouldn't have been able to get. The best solution here is to
22493 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22494 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22495 to make sure that the bug can't happen.
22498 - Fix the SOCKET_OK test that we use to tell when socket
22499 creation fails so that it works on Win64. Fixes part of bug 4533;
22500 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
22501 - Correct our replacements for the timeradd() and timersub() functions
22502 on platforms that lack them (for example, Windows). The timersub()
22503 function is used when expiring circuits, while timeradd() is
22504 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
22505 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
22506 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
22507 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
22508 bug at runtime, not compile time, because some distributions hack
22509 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
22510 on 0.2.3.9-alpha. Found by Pascal.
22512 o Minor features (controller):
22513 - Use absolute path names when reporting the torrc filename in the
22514 control protocol, so a controller can more easily find the torrc
22515 file. Resolves bug 1101.
22516 - Extend the control protocol to report flags that control a circuit's
22517 path selection in CIRC events and in replies to 'GETINFO
22518 circuit-status'. Implements part of ticket 2411.
22519 - Extend the control protocol to report the hidden service address
22520 and current state of a hidden-service-related circuit in CIRC
22521 events and in replies to 'GETINFO circuit-status'. Implements part
22523 - When reporting the path to the cookie file to the controller,
22524 give an absolute path. Resolves ticket 4881.
22525 - Allow controllers to request an event notification whenever a
22526 circuit is cannibalized or its purpose is changed. Implements
22527 part of ticket 3457.
22528 - Include the creation time of a circuit in CIRC and CIRC2
22529 control-port events and the list produced by the 'GETINFO
22530 circuit-status' control-port command.
22532 o Minor features (directory authorities):
22533 - Directory authorities now reject versions of Tor older than
22534 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
22535 inclusive. These versions accounted for only a small fraction of
22536 the Tor network, and have numerous known security issues. Resolves
22538 - Authority operators can now vote for all relays in a given
22539 set of countries to be BadDir/BadExit/Invalid/Rejected.
22540 - Provide two consensus parameters (FastFlagMinThreshold and
22541 FastFlagMaxThreshold) to control the range of allowable bandwidths
22542 for the Fast directory flag. These allow authorities to run
22543 experiments on appropriate requirements for being a "Fast" node.
22544 The AuthDirFastGuarantee config value still applies. Implements
22546 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
22547 directory authority option (introduced in Tor 0.2.2.34).
22549 o Minor features (other):
22550 - Don't disable the DirPort when we cannot exceed our AccountingMax
22551 limit during this interval because the effective bandwidthrate is
22552 low enough. This is useful in a situation where AccountMax is only
22553 used as an additional safeguard or to provide statistics.
22554 - Prepend an informative header to generated dynamic_dh_params files.
22555 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
22556 EntryNodes will have no effect. Resolves issue 2571.
22557 - Log more useful messages when we fail to disable debugger
22559 - Log which authority we're missing votes from when we go to fetch
22560 them from the other auths.
22561 - Log (at debug level) whenever a circuit's purpose is changed.
22562 - Add missing documentation for the MaxClientCircuitsPending,
22563 UseMicrodescriptors, UserspaceIOCPBuffers, and
22564 _UseFilteringSSLBufferevents options, all introduced during
22565 the 0.2.3.x series.
22566 - Update to the January 3 2012 Maxmind GeoLite Country database.
22568 o Minor bugfixes (hidden services):
22569 - Don't close hidden service client circuits which have almost
22570 finished connecting to their destination when they reach
22571 the normal circuit-build timeout. Previously, we would close
22572 introduction circuits which are waiting for an acknowledgement
22573 from the introduction point, and rendezvous circuits which have
22574 been specified in an INTRODUCE1 cell sent to a hidden service,
22575 after the normal CBT. Now, we mark them as 'timed out', and launch
22576 another rendezvous attempt in parallel. This behavior change can
22577 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
22578 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
22579 - Don't close hidden-service-side rendezvous circuits when they
22580 reach the normal circuit-build timeout. This behavior change can
22581 be disabled using the new
22582 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
22583 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
22584 - Make sure we never mark the wrong rendezvous circuit as having
22585 had its introduction cell acknowledged by the introduction-point
22586 relay. Previously, when we received an INTRODUCE_ACK cell on a
22587 client-side hidden-service introduction circuit, we might have
22588 marked a rendezvous circuit other than the one we specified in
22589 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
22590 a warning message and interfered with the hidden service
22591 connection-establishment process. Fixes bug 4759; bugfix on
22592 0.2.3.3-alpha, when we added the stream-isolation feature which
22593 might cause Tor to open multiple rendezvous circuits for the same
22595 - Don't trigger an assertion failure when we mark a new client-side
22596 hidden-service introduction circuit for close during the process
22597 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
22600 o Minor bugfixes (log messages):
22601 - Correctly spell "connect" in a log message on failure to create a
22602 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
22604 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
22605 Fixes bug 4856; bugfix on Tor 0.0.6.
22606 - Fix the log message describing how we work around discovering
22607 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
22608 4837; bugfix on 0.2.2.9-alpha.
22609 - When logging about a disallowed .exit name, do not also call it
22610 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
22612 o Minor bugfixes (build fixes):
22613 - During configure, detect when we're building with clang version
22614 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
22615 CFLAGS. clang doesn't support them yet.
22616 - During configure, search for library containing cos function as
22617 libm lives in libcore on some platforms (BeOS/Haiku). Linking
22618 against libm was hard-coded before. Fixes the first part of bug
22619 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
22621 - Detect attempts to build Tor on (as yet hypothetical) versions
22622 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
22623 fix for bug 4533. Bugfix on 0.2.2.28-beta.
22624 - Preprocessor directives should not be put inside the arguments
22625 of a macro. This would break compilation with GCC releases prior
22626 to version 3.3. We would never recommend such an old GCC version,
22627 but it is apparently required for binary compatibility on some
22628 platforms (namely, certain builds of Haiku). Fixes the other part
22629 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
22632 o Minor bugfixes (other):
22633 - Older Linux kernels erroneously respond to strange nmap behavior
22634 by having accept() return successfully with a zero-length
22635 socket. When this happens, just close the connection. Previously,
22636 we would try harder to learn the remote address: but there was
22637 no such remote address to learn, and our method for trying to
22638 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
22639 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
22640 - Fix null-pointer access that could occur if TLS allocation failed.
22641 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
22642 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
22643 accidentally been reverted.
22644 - Fix our implementation of crypto_random_hostname() so it can't
22645 overflow on ridiculously large inputs. (No Tor version has ever
22646 provided this kind of bad inputs, but let's be correct in depth.)
22647 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
22648 - Find more places in the code that should have been testing for
22649 invalid sockets using the SOCKET_OK macro. Required for a fix
22650 for bug 4533. Bugfix on 0.2.2.28-beta.
22651 - Fix an assertion failure when, while running with bufferevents, a
22652 connection finishes connecting after it is marked for close, but
22653 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
22654 - test_util_spawn_background_ok() hardcoded the expected value
22655 for ENOENT to 2. This isn't portable as error numbers are
22656 platform specific, and particularly the hurd has ENOENT at
22657 0x40000002. Construct expected string at runtime, using the correct
22658 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
22659 - Reject attempts to disable DisableDebuggerAttachment while Tor is
22660 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
22661 - Use an appropriate-width type for sockets in tor-fw-helper on
22662 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
22665 - When sending or relaying a RELAY_EARLY cell, we used to convert
22666 it to a RELAY cell if the connection was using the v1 link
22667 protocol. This was a workaround for older versions of Tor, which
22668 didn't handle RELAY_EARLY cells properly. Now that all supported
22669 versions can handle RELAY_EARLY cells, and now that we're enforcing
22670 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
22671 remove this workaround. Addresses bug 4786.
22673 o Code simplifications and refactoring:
22674 - Use OpenSSL's built-in SSL_state_string_long() instead of our
22675 own homebrewed ssl_state_to_string() replacement. Patch from
22676 Emile Snyder. Fixes bug 4653.
22677 - Use macros to indicate OpenSSL versions, so we don't need to worry
22678 about accidental hexadecimal bit shifts.
22679 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
22681 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
22682 - Use the smartlist_add_asprintf() alias more consistently.
22683 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
22684 invalid value, rather than just -1.
22685 - Rename a handful of old identifiers, mostly related to crypto
22686 structures and crypto functions. By convention, our "create an
22687 object" functions are called "type_new()", our "free an object"
22688 functions are called "type_free()", and our types indicate that
22689 they are types only with a final "_t". But a handful of older
22690 types and functions broke these rules, with function names like
22691 "type_create" or "subsystem_op_type", or with type names like
22695 Changes in version 0.2.3.10-alpha - 2011-12-16
22696 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
22697 Tor's buffers code. Absolutely everybody should upgrade.
22699 The bug relied on an incorrect calculation when making data continuous
22700 in one of our IO buffers, if the first chunk of the buffer was
22701 misaligned by just the wrong amount. The miscalculation would allow an
22702 attacker to overflow a piece of heap-allocated memory. To mount this
22703 attack, the attacker would need to either open a SOCKS connection to
22704 Tor's SocksPort (usually restricted to localhost), or target a Tor
22705 instance configured to make its connections through a SOCKS proxy
22706 (which Tor does not do by default).
22708 Good security practice requires that all heap-overflow bugs should be
22709 presumed to be exploitable until proven otherwise, so we are treating
22710 this as a potential code execution attack. Please upgrade immediately!
22711 This bug does not affect bufferevents-based builds of Tor. Special
22712 thanks to "Vektor" for reporting this issue to us!
22714 This release also contains a few minor bugfixes for issues discovered
22718 - Fix a heap overflow bug that could occur when trying to pull
22719 data into the first chunk of a buffer, when that chunk had
22720 already had some data drained from it. Fixes CVE-2011-2778;
22721 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
22724 - If we can't attach streams to a rendezvous circuit when we
22725 finish connecting to a hidden service, clear the rendezvous
22726 circuit's stream-isolation state and try to attach streams
22727 again. Previously, we cleared rendezvous circuits' isolation
22728 state either too early (if they were freshly built) or not at all
22729 (if they had been built earlier and were cannibalized). Bugfix on
22730 0.2.3.3-alpha; fixes bug 4655.
22731 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
22732 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
22733 - Fix an assertion failure when a relay with accounting enabled
22734 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
22737 - Update to the December 6 2011 Maxmind GeoLite Country database.
22740 Changes in version 0.2.2.35 - 2011-12-16
22741 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
22742 buffers code. Absolutely everybody should upgrade.
22744 The bug relied on an incorrect calculation when making data continuous
22745 in one of our IO buffers, if the first chunk of the buffer was
22746 misaligned by just the wrong amount. The miscalculation would allow an
22747 attacker to overflow a piece of heap-allocated memory. To mount this
22748 attack, the attacker would need to either open a SOCKS connection to
22749 Tor's SocksPort (usually restricted to localhost), or target a Tor
22750 instance configured to make its connections through a SOCKS proxy
22751 (which Tor does not do by default).
22753 Good security practice requires that all heap-overflow bugs should be
22754 presumed to be exploitable until proven otherwise, so we are treating
22755 this as a potential code execution attack. Please upgrade immediately!
22756 This bug does not affect bufferevents-based builds of Tor. Special
22757 thanks to "Vektor" for reporting this issue to us!
22759 Tor 0.2.2.35 also fixes several bugs in previous versions, including
22760 crash bugs for unusual configurations, and a long-term bug that
22761 would prevent Tor from starting on Windows machines with draconian
22764 With this release, we remind everyone that 0.2.0.x has reached its
22765 formal end-of-life. Those Tor versions have many known flaws, and
22766 nobody should be using them. You should upgrade -- ideally to the
22767 0.2.2.x series. If you're using a Linux or BSD and its packages are
22768 obsolete, stop using those packages and upgrade anyway.
22770 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
22771 longer receive support after some time in early 2012.
22774 - Fix a heap overflow bug that could occur when trying to pull
22775 data into the first chunk of a buffer, when that chunk had
22776 already had some data drained from it. Fixes CVE-2011-2778;
22777 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
22778 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
22779 that it doesn't attempt to allocate a socketpair. This could cause
22780 some problems on Windows systems with overzealous firewalls. Fix for
22781 bug 4457; workaround for Libevent versions 2.0.1-alpha through
22783 - If we mark an OR connection for close based on a cell we process,
22784 don't process any further cells on it. We already avoid further
22785 reads on marked-for-close connections, but now we also discard the
22786 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
22787 which was the first version where we might mark a connection for
22788 close based on processing a cell on it.
22789 - Correctly sanity-check that we don't underflow on a memory
22790 allocation (and then assert) for hidden service introduction
22791 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
22792 bugfix on 0.2.1.5-alpha.
22793 - Fix a memory leak when we check whether a hidden service
22794 descriptor has any usable introduction points left. Fixes bug
22795 4424. Bugfix on 0.2.2.25-alpha.
22796 - Don't crash when we're running as a relay and don't have a GeoIP
22797 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
22798 we've had in the 0.2.3.x branch already.
22799 - When running as a client, do not print a misleading (and plain
22800 wrong) log message that we're collecting "directory request"
22801 statistics: clients don't collect statistics. Also don't create a
22802 useless (because empty) stats file in the stats/ directory. Fixes
22803 bug 4353; bugfix on 0.2.2.34.
22806 - Detect failure to initialize Libevent. This fix provides better
22807 detection for future instances of bug 4457.
22808 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
22809 function. This was eating up hideously large amounts of time on some
22810 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
22811 - Resolve an integer overflow bug in smartlist_ensure_capacity().
22812 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
22814 - Don't warn about unused log_mutex in log.c when building with
22815 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
22816 0.1.0.6-rc which introduced --disable-threads.
22817 - When configuring, starting, or stopping an NT service, stop
22818 immediately after the service configuration attempt has succeeded
22819 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
22820 - When sending a NETINFO cell, include the original address
22821 received for the other side, not its canonical address. Found
22822 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
22823 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
22824 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
22825 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
22826 occurred when a client tried to fetch a descriptor for a bridge
22827 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
22828 - Backport fixes for a pair of compilation warnings on Windows.
22829 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
22830 - If we had ever tried to call tor_addr_to_str on an address of
22831 unknown type, we would have done a strdup on an uninitialized
22832 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
22833 Reported by "troll_un".
22834 - Correctly detect and handle transient lookup failures from
22835 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
22836 Reported by "troll_un".
22837 - Fix null-pointer access that could occur if TLS allocation failed.
22838 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
22839 - Use tor_socket_t type for listener argument to accept(). Fixes bug
22840 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
22843 - Add two new config options for directory authorities:
22844 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
22845 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
22846 that is always sufficient to satisfy the bandwidth requirement for
22847 the Guard flag. Now it will be easier for researchers to simulate
22848 Tor networks with different values. Resolves ticket 4484.
22849 - When Tor ignores a hidden service specified in its configuration,
22850 include the hidden service's directory in the warning message.
22851 Previously, we would only tell the user that some hidden service
22852 was ignored. Bugfix on 0.0.6; fixes bug 4426.
22853 - Update to the December 6 2011 Maxmind GeoLite Country database.
22855 o Packaging changes:
22856 - Make it easier to automate expert package builds on Windows,
22857 by removing an absolute path from makensis.exe command.
22860 Changes in version 0.2.1.32 - 2011-12-16
22861 Tor 0.2.1.32 backports important security and privacy fixes for
22862 oldstable. This release is intended only for package maintainers and
22863 others who cannot use the 0.2.2 stable series. All others should be
22864 using Tor 0.2.2.x or newer.
22866 The Tor 0.2.1.x series will reach formal end-of-life some time in
22867 early 2012; we will stop releasing patches for it then.
22869 o Major bugfixes (also included in 0.2.2.x):
22870 - Correctly sanity-check that we don't underflow on a memory
22871 allocation (and then assert) for hidden service introduction
22872 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
22873 bugfix on 0.2.1.5-alpha.
22874 - Fix a heap overflow bug that could occur when trying to pull
22875 data into the first chunk of a buffer, when that chunk had
22876 already had some data drained from it. Fixes CVE-2011-2778;
22877 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
22880 - Update to the December 6 2011 Maxmind GeoLite Country database.
22883 Changes in version 0.2.3.9-alpha - 2011-12-08
22884 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
22885 a "DisableNetwork" security feature that bundles can use to avoid
22886 touching the network until bridges are configured, moves forward on
22887 the pluggable transport design, fixes a flaw in the hidden service
22888 design that unnecessarily prevented clients with wrong clocks from
22889 reaching hidden services, and fixes a wide variety of other issues.
22892 - Clients can now connect to private bridges over IPv6. Bridges
22893 still need at least one IPv4 address in order to connect to
22894 other relays. Note that we don't yet handle the case where the
22895 user has two bridge lines for the same bridge (one IPv4, one
22896 IPv6). Implements parts of proposal 186.
22897 - New "DisableNetwork" config option to prevent Tor from launching any
22898 connections or accepting any connections except on a control port.
22899 Bundles and controllers can set this option before letting Tor talk
22900 to the rest of the network, for example to prevent any connections
22901 to a non-bridge address. Packages like Orbot can also use this
22902 option to instruct Tor to save power when the network is off.
22903 - Clients and bridges can now be configured to use a separate
22904 "transport" proxy. This approach makes the censorship arms race
22905 easier by allowing bridges to use protocol obfuscation plugins. It
22906 implements the "managed proxy" part of proposal 180 (ticket 3472).
22907 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
22908 implementation. It makes AES_CTR about 7% faster than our old one
22909 (which was about 10% faster than the one OpenSSL used to provide).
22910 Resolves ticket 4526.
22911 - Add a "tor2web mode" for clients that want to connect to hidden
22912 services non-anonymously (and possibly more quickly). As a safety
22913 measure to try to keep users from turning this on without knowing
22914 what they are doing, tor2web mode must be explicitly enabled at
22915 compile time, and a copy of Tor compiled to run in tor2web mode
22916 cannot be used as a normal Tor client. Implements feature 2553.
22917 - Add experimental support for running on Windows with IOCP and no
22918 kernel-space socket buffers. This feature is controlled by a new
22919 "UserspaceIOCPBuffers" config option (off by default), which has
22920 no effect unless Tor has been built with support for bufferevents,
22921 is running on Windows, and has enabled IOCP. This may, in the long
22922 run, help solve or mitigate bug 98.
22923 - Use a more secure consensus parameter voting algorithm. Now at
22924 least three directory authorities or a majority of them must
22925 vote on a given parameter before it will be included in the
22926 consensus. Implements proposal 178.
22929 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
22930 They used to check that the timestamp was within 30 minutes
22931 of their system clock, so they could cap the size of their
22932 replay-detection cache, but that approach unnecessarily refused
22933 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
22934 the v3 intro-point protocol (the first one which sent a timestamp
22935 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
22936 - Only use the EVP interface when AES acceleration is enabled,
22937 to avoid a 5-7% performance regression. Resolves issue 4525;
22938 bugfix on 0.2.3.8-alpha.
22940 o Privacy/anonymity features (bridge detection):
22941 - Make bridge SSL certificates a bit more stealthy by using random
22942 serial numbers, in the same fashion as OpenSSL when generating
22943 self-signed certificates. Implements ticket 4584.
22944 - Introduce a new config option "DynamicDHGroups", enabled by
22945 default, which provides each bridge with a unique prime DH modulus
22946 to be used during SSL handshakes. This option attempts to help
22947 against censors who might use the Apache DH modulus as a static
22948 identifier for bridges. Addresses ticket 4548.
22950 o Minor features (new/different config options):
22951 - New configuration option "DisableDebuggerAttachment" (on by default)
22952 to prevent basic debugging attachment attempts by other processes.
22953 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
22954 - Allow MapAddress directives to specify matches against super-domains,
22955 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
22956 Implements issue 933.
22957 - Slightly change behavior of "list" options (that is, config
22958 options that can appear more than once) when they appear both in
22959 torrc and on the command line. Previously, the command-line options
22960 would be appended to the ones from torrc. Now, the command-line
22961 options override the torrc options entirely. This new behavior
22962 allows the user to override list options (like exit policies and
22963 ports to listen on) from the command line, rather than simply
22964 appending to the list.
22965 - You can get the old (appending) command-line behavior for "list"
22966 options by prefixing the option name with a "+".
22967 - You can remove all the values for a "list" option from the command
22968 line without adding any new ones by prefixing the option name
22970 - Add experimental support for a "defaults" torrc file to be parsed
22971 before the regular torrc. Torrc options override the defaults file's
22972 options in the same way that the command line overrides the torrc.
22973 The SAVECONF controller command saves only those options which
22974 differ between the current configuration and the defaults file. HUP
22975 reloads both files. (Note: This is an experimental feature; its
22976 behavior will probably be refined in future 0.2.3.x-alpha versions
22977 to better meet packagers' needs.) Implements task 4552.
22980 - Try to make the introductory warning message that Tor prints on
22981 startup more useful for actually finding help and information.
22982 Resolves ticket 2474.
22983 - Running "make version" now displays the version of Tor that
22984 we're about to build. Idea from katmagic; resolves issue 4400.
22985 - Expire old or over-used hidden service introduction points.
22986 Required by fix for bug 3460.
22987 - Move the replay-detection cache for the RSA-encrypted parts of
22988 INTRODUCE2 cells to the introduction point data structures.
22989 Previously, we would use one replay-detection cache per hidden
22990 service. Required by fix for bug 3460.
22991 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
22992 public key replay-detection cache from 60 minutes to 5 minutes. This
22993 replay-detection cache is now used only to detect multiple
22994 INTRODUCE2 cells specifying the same rendezvous point, so we can
22995 avoid launching multiple simultaneous attempts to connect to it.
22997 o Minor bugfixes (on Tor 0.2.2.x and earlier):
22998 - Resolve an integer overflow bug in smartlist_ensure_capacity().
22999 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23001 - Fix a minor formatting issue in one of tor-gencert's error messages.
23003 - Prevent a false positive from the check-spaces script, by disabling
23004 the "whitespace between function name and (" check for functions
23006 - Fix a log message suggesting that people contact a non-existent
23007 email address. Fixes bug 3448.
23008 - Fix null-pointer access that could occur if TLS allocation failed.
23009 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23010 - Report a real bootstrap problem to the controller on router
23011 identity mismatch. Previously we just said "foo", which probably
23012 made a lot of sense at the time. Fixes bug 4169; bugfix on
23014 - If we had ever tried to call tor_addr_to_str() on an address of
23015 unknown type, we would have done a strdup() on an uninitialized
23016 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23017 Reported by "troll_un".
23018 - Correctly detect and handle transient lookup failures from
23019 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23020 Reported by "troll_un".
23021 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23022 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23023 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
23024 bug 4532; found by "troll_un".
23026 o Minor bugfixes (on Tor 0.2.3.x):
23027 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
23029 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
23030 circuit for use as a hidden service client's rendezvous point.
23031 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
23032 with help from wanoskarnet.
23033 - Restore behavior of overriding SocksPort, ORPort, and similar
23034 options from the command line. Bugfix on 0.2.3.3-alpha.
23037 - Properly handle the case where the build-tree is not the same
23038 as the source tree when generating src/common/common_sha1.i,
23039 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
23040 bugfix on 0.2.0.1-alpha.
23042 o Code simplifications, cleanups, and refactorings:
23043 - Remove the pure attribute from all functions that used it
23044 previously. In many cases we assigned it incorrectly, because the
23045 functions might assert or call impure functions, and we don't have
23046 evidence that keeping the pure attribute is worthwhile. Implements
23047 changes suggested in ticket 4421.
23048 - Remove some dead code spotted by coverity. Fixes cid 432.
23049 Bugfix on 0.2.3.1-alpha, closes bug 4637.
23052 Changes in version 0.2.3.8-alpha - 2011-11-22
23053 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
23054 socketpair-related bug that has been bothering Windows users. It adds
23055 support to serve microdescriptors to controllers, so Vidalia's network
23056 map can resume listing relays (once Vidalia implements its side),
23057 and adds better support for hardware AES acceleration. Finally, it
23058 starts the process of adjusting the bandwidth cutoff for getting the
23059 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
23060 that tiny relays harm performance more than they help network capacity.
23063 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
23064 that it doesn't attempt to allocate a socketpair. This could cause
23065 some problems on Windows systems with overzealous firewalls. Fix for
23066 bug 4457; workaround for Libevent versions 2.0.1-alpha through
23068 - Correctly sanity-check that we don't underflow on a memory
23069 allocation (and then assert) for hidden service introduction
23070 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23071 bugfix on 0.2.1.5-alpha.
23072 - Remove the artificially low cutoff of 20KB to guarantee the Fast
23073 flag. In the past few years the average relay speed has picked
23074 up, and while the "top 7/8 of the network get the Fast flag" and
23075 "all relays with 20KB or more of capacity get the Fast flag" rules
23076 used to have the same result, now the top 7/8 of the network has
23077 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
23078 - Fix a rare assertion failure when checking whether a v0 hidden
23079 service descriptor has any usable introduction points left, and
23080 we don't have enough information to build a circuit to the first
23081 intro point named in the descriptor. The HS client code in
23082 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
23083 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
23084 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
23085 - Make bridge authorities not crash when they are asked for their own
23086 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
23087 - When running as a client, do not print a misleading (and plain
23088 wrong) log message that we're collecting "directory request"
23089 statistics: clients don't collect statistics. Also don't create a
23090 useless (because empty) stats file in the stats/ directory. Fixes
23091 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
23094 - Allow Tor controllers like Vidalia to obtain the microdescriptor
23095 for a relay by identity digest or nickname. Previously,
23096 microdescriptors were only available by their own digests, so a
23097 controller would have to ask for and parse the whole microdescriptor
23098 consensus in order to look up a single relay's microdesc. Fixes
23099 bug 3832; bugfix on 0.2.3.1-alpha.
23100 - Use OpenSSL's EVP interface for AES encryption, so that all AES
23101 operations can use hardware acceleration (if present). Resolves
23104 o Minor bugfixes (on 0.2.2.x and earlier):
23105 - Detect failure to initialize Libevent. This fix provides better
23106 detection for future instances of bug 4457.
23107 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
23108 function. This was eating up hideously large amounts of time on some
23109 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
23110 - Don't warn about unused log_mutex in log.c when building with
23111 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
23112 0.1.0.6-rc which introduced --disable-threads.
23113 - Allow manual 'authenticate' commands to the controller interface
23114 from netcat (nc) as well as telnet. We were rejecting them because
23115 they didn't come with the expected whitespace at the end of the
23116 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
23117 - Fix some (not actually triggerable) buffer size checks in usage of
23118 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
23120 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
23121 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
23122 - When configuring, starting, or stopping an NT service, stop
23123 immediately after the service configuration attempt has succeeded
23124 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
23125 - When sending a NETINFO cell, include the original address
23126 received for the other side, not its canonical address. Found
23127 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
23128 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
23129 can pick them up when the tests aren't disabled. Bugfix on
23130 0.2.2.4-alpha which introduced tinytest.
23131 - Fix a memory leak when we check whether a hidden service
23132 descriptor has any usable introduction points left. Fixes bug
23133 4424. Bugfix on 0.2.2.25-alpha.
23134 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
23135 occurred when a client tried to fetch a descriptor for a bridge
23136 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
23138 o Minor bugfixes (on 0.2.3.x):
23139 - Make util unit tests build correctly with MSVC. Bugfix on
23140 0.2.3.3-alpha. Patch by Gisle Vanem.
23141 - Successfully detect AUTH_CHALLENGE cells with no recognized
23142 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
23143 Found by frosty_un.
23144 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
23145 it should still send a NETINFO cell to allow the connection to
23146 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
23148 - Log less loudly when we get an invalid authentication certificate
23149 from a source other than a directory authority: it's not unusual
23150 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
23152 - Tolerate servers with more clock skew in their authentication
23153 certificates than previously. Fixes bug 4371; bugfix on
23155 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
23156 on 0.2.3.4-alpha and 0.2.3.6-alpha.
23159 - Add two new config options for directory authorities:
23160 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
23161 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
23162 that is always sufficient to satisfy the bandwidth requirement for
23163 the Guard flag. Now it will be easier for researchers to simulate
23164 Tor networks with different values. Resolves ticket 4484.
23165 - When Tor ignores a hidden service specified in its configuration,
23166 include the hidden service's directory in the warning message.
23167 Previously, we would only tell the user that some hidden service
23168 was ignored. Bugfix on 0.0.6; fixes bug 4426.
23169 - When we fail to initialize Libevent, retry with IOCP disabled so we
23170 don't need to turn on multi-threading support in Libevent, which in
23171 turn requires a working socketpair(). This is a workaround for bug
23172 4457, which affects Libevent versions from 2.0.1-alpha through
23174 - Detect when we try to build on a platform that doesn't define
23175 AF_UNSPEC to 0. We don't work there, so refuse to compile.
23176 - Update to the November 1 2011 Maxmind GeoLite Country database.
23178 o Packaging changes:
23179 - Make it easier to automate expert package builds on Windows,
23180 by removing an absolute path from makensis.exe command.
23182 o Code simplifications and refactoring:
23183 - Remove some redundant #include directives throughout the code.
23184 Patch from Andrea Gelmini.
23185 - Unconditionally use OpenSSL's AES implementation instead of our
23186 old built-in one. OpenSSL's AES has been better for a while, and
23187 relatively few servers should still be on any version of OpenSSL
23188 that doesn't have good optimized assembly AES.
23189 - Use the name "CERTS" consistently to refer to the new cell type;
23190 we were calling it CERT in some places and CERTS in others.
23193 - Numerous new unit tests for functions in util.c and address.c by
23195 - The long-disabled benchmark tests are now split into their own
23196 ./src/test/bench binary.
23197 - The benchmark tests can now use more accurate timers than
23198 gettimeofday() when such timers are available.
23201 Changes in version 0.2.3.7-alpha - 2011-10-30
23202 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
23203 the new v3 handshake. It also resolves yet another bridge address
23207 - If we mark an OR connection for close based on a cell we process,
23208 don't process any further cells on it. We already avoid further
23209 reads on marked-for-close connections, but now we also discard the
23210 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
23211 which was the first version where we might mark a connection for
23212 close based on processing a cell on it.
23213 - Fix a double-free bug that would occur when we received an invalid
23214 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
23215 bugfix on 0.2.3.6-alpha.
23216 - Bridges no longer include their address in NETINFO cells on outgoing
23217 OR connections, to allow them to blend in better with clients.
23218 Removes another avenue for enumerating bridges. Reported by
23219 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
23220 cells were introduced.
23223 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
23224 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
23227 Changes in version 0.2.3.6-alpha - 2011-10-26
23228 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
23229 anonymity vulnerability where an attacker can deanonymize Tor
23230 users. Everybody should upgrade.
23232 This release also features support for a new v3 connection handshake
23233 protocol, and fixes to make hidden service connections more robust.
23236 - Implement a new handshake protocol (v3) for authenticating Tors to
23237 each other over TLS. It should be more resistant to fingerprinting
23238 than previous protocols, and should require less TLS hacking for
23239 future Tor implementations. Implements proposal 176.
23240 - Allow variable-length padding cells to disguise the length of
23241 Tor's TLS records. Implements part of proposal 184.
23243 o Privacy/anonymity fixes (clients):
23244 - Clients and bridges no longer send TLS certificate chains on
23245 outgoing OR connections. Previously, each client or bridge would
23246 use the same cert chain for all outgoing OR connections until
23247 its IP address changes, which allowed any relay that the client
23248 or bridge contacted to determine which entry guards it is using.
23249 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23250 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23251 no longer considers that connection as suitable for satisfying a
23252 circuit EXTEND request. Now relays can protect clients from the
23253 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23254 - Directory authorities no longer assign the Guard flag to relays
23255 that haven't upgraded to the above "refuse EXTEND requests
23256 to client connections" fix. Now directory authorities can
23257 protect clients from the CVE-2011-2768 issue even if neither
23258 the clients nor the relays have upgraded yet. There's a new
23259 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
23260 to let us transition smoothly, else tomorrow there would be no
23263 o Major bugfixes (hidden services):
23264 - Improve hidden service robustness: when an attempt to connect to
23265 a hidden service ends, be willing to refetch its hidden service
23266 descriptors from each of the HSDir relays responsible for them
23267 immediately. Previously, we would not consider refetching the
23268 service's descriptors from each HSDir for 15 minutes after the last
23269 fetch, which was inconvenient if the hidden service was not running
23270 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
23271 - When one of a hidden service's introduction points appears to be
23272 unreachable, stop trying it. Previously, we would keep trying
23273 to build circuits to the introduction point until we lost the
23274 descriptor, usually because the user gave up and restarted Tor.
23275 Partly fixes bug 3825.
23276 - Don't launch a useless circuit after failing to use one of a
23277 hidden service's introduction points. Previously, we would
23278 launch a new introduction circuit, but not set the hidden service
23279 which that circuit was intended to connect to, so it would never
23280 actually be used. A different piece of code would then create a
23281 new introduction circuit correctly. Bug reported by katmagic and
23282 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
23284 o Major bugfixes (other):
23285 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23286 that they initiated. Relays could distinguish incoming bridge
23287 connections from client connections, creating another avenue for
23288 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23289 Found by "frosty_un".
23290 - Don't update the AccountingSoftLimitHitAt state file entry whenever
23291 tor gets started. This prevents a wrong average bandwidth
23292 estimate, which would cause relays to always start a new accounting
23293 interval at the earliest possible moment. Fixes bug 2003; bugfix
23294 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
23295 immensely in tracking this bug down.
23296 - Fix a crash bug when changing node restrictions while a DNS lookup
23297 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
23300 o Minor bugfixes (on 0.2.2.x and earlier):
23301 - When a hidden service turns an extra service-side introduction
23302 circuit into a general-purpose circuit, free the rend_data and
23303 intro_key fields first, so we won't leak memory if the circuit
23304 is cannibalized for use as another service-side introduction
23305 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
23306 - Rephrase the log message emitted if the TestSocks check is
23307 successful. Patch from Fabian Keil; fixes bug 4094.
23308 - Bridges now skip DNS self-tests, to act a little more stealthily.
23309 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
23310 bridges. Patch by "warms0x".
23311 - Remove a confusing dollar sign from the example fingerprint in the
23312 man page, and also make the example fingerprint a valid one. Fixes
23313 bug 4309; bugfix on 0.2.1.3-alpha.
23314 - Fix internal bug-checking logic that was supposed to catch
23315 failures in digest generation so that it will fail more robustly
23316 if we ask for a nonexistent algorithm. Found by Coverity Scan.
23317 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
23318 - Report any failure in init_keys() calls launched because our
23319 IP address has changed. Spotted by Coverity Scan. Bugfix on
23320 0.1.1.4-alpha; fixes CID 484.
23322 o Minor bugfixes (on 0.2.3.x):
23323 - Fix a bug in configure.in that kept it from building a configure
23324 script with autoconf versions earlier than 2.61. Fixes bug 2430;
23325 bugfix on 0.2.3.1-alpha.
23326 - Don't warn users that they are exposing a client port to the
23327 Internet if they have specified an RFC1918 address. Previously,
23328 we would warn if the user had specified any non-loopback
23329 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
23330 - Fix memory leaks in the failing cases of the new SocksPort and
23331 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
23332 fixes coverity CIDs 485, 486, and 487.
23335 - When a hidden service's introduction point times out, consider
23336 trying it again during the next attempt to connect to the
23337 HS. Previously, we would not try it again unless a newly fetched
23338 descriptor contained it. Required by fixes for bugs 1297 and 3825.
23339 - The next version of Windows will be called Windows 8, and it has
23340 a major version of 6, minor version of 2. Correctly identify that
23341 version instead of calling it "Very recent version". Resolves
23342 ticket 4153; reported by funkstar.
23343 - The Bridge Authority now writes statistics on how many bridge
23344 descriptors it gave out in total, and how many unique descriptors
23345 it gave out. It also lists how often the most and least commonly
23346 fetched descriptors were given out, as well as the median and
23347 25th/75th percentile. Implements tickets 4200 and 4294.
23348 - Update to the October 4 2011 Maxmind GeoLite Country database.
23350 o Code simplifications and refactoring:
23351 - Remove some old code to remember statistics about which descriptors
23352 we've served as a directory mirror. The feature wasn't used and
23353 is outdated now that microdescriptors are around.
23354 - Rename Tor functions that turn strings into addresses, so that
23355 "parse" indicates that no hostname resolution occurs, and
23356 "lookup" indicates that hostname resolution may occur. This
23357 should help prevent mistakes in the future. Fixes bug 3512.
23360 Changes in version 0.2.2.34 - 2011-10-26
23361 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
23362 can deanonymize Tor users. Everybody should upgrade.
23364 The attack relies on four components: 1) Clients reuse their TLS cert
23365 when talking to different relays, so relays can recognize a user by
23366 the identity key in her cert. 2) An attacker who knows the client's
23367 identity key can probe each guard relay to see if that identity key
23368 is connected to that guard relay right now. 3) A variety of active
23369 attacks in the literature (starting from "Low-Cost Traffic Analysis
23370 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
23371 discover the guard relays that a Tor user visiting the website is using.
23372 4) Clients typically pick three guards at random, so the set of guards
23373 for a given user could well be a unique fingerprint for her. This
23374 release fixes components #1 and #2, which is enough to block the attack;
23375 the other two remain as open research problems. Special thanks to
23376 "frosty_un" for reporting the issue to us!
23378 Clients should upgrade so they are no longer recognizable by the TLS
23379 certs they present. Relays should upgrade so they no longer allow a
23380 remote attacker to probe them to test whether unpatched clients are
23381 currently connected to them.
23383 This release also fixes several vulnerabilities that allow an attacker
23384 to enumerate bridge relays. Some bridge enumeration attacks still
23385 remain; see for example proposal 188.
23387 o Privacy/anonymity fixes (clients):
23388 - Clients and bridges no longer send TLS certificate chains on
23389 outgoing OR connections. Previously, each client or bridge would
23390 use the same cert chain for all outgoing OR connections until
23391 its IP address changes, which allowed any relay that the client
23392 or bridge contacted to determine which entry guards it is using.
23393 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23394 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23395 no longer considers that connection as suitable for satisfying a
23396 circuit EXTEND request. Now relays can protect clients from the
23397 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23398 - Directory authorities no longer assign the Guard flag to relays
23399 that haven't upgraded to the above "refuse EXTEND requests
23400 to client connections" fix. Now directory authorities can
23401 protect clients from the CVE-2011-2768 issue even if neither
23402 the clients nor the relays have upgraded yet. There's a new
23403 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
23404 to let us transition smoothly, else tomorrow there would be no
23407 o Privacy/anonymity fixes (bridge enumeration):
23408 - Bridge relays now do their directory fetches inside Tor TLS
23409 connections, like all the other clients do, rather than connecting
23410 directly to the DirPort like public relays do. Removes another
23411 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
23412 - Bridges relays now build circuits for themselves in a more similar
23413 way to how clients build them. Removes another avenue for
23414 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
23415 when bridges were introduced.
23416 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23417 that they initiated. Relays could distinguish incoming bridge
23418 connections from client connections, creating another avenue for
23419 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23420 Found by "frosty_un".
23423 - Fix a crash bug when changing node restrictions while a DNS lookup
23424 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
23426 - Don't launch a useless circuit after failing to use one of a
23427 hidden service's introduction points. Previously, we would
23428 launch a new introduction circuit, but not set the hidden service
23429 which that circuit was intended to connect to, so it would never
23430 actually be used. A different piece of code would then create a
23431 new introduction circuit correctly. Bug reported by katmagic and
23432 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
23435 - Change an integer overflow check in the OpenBSD_Malloc code so
23436 that GCC is less likely to eliminate it as impossible. Patch
23437 from Mansour Moufid. Fixes bug 4059.
23438 - When a hidden service turns an extra service-side introduction
23439 circuit into a general-purpose circuit, free the rend_data and
23440 intro_key fields first, so we won't leak memory if the circuit
23441 is cannibalized for use as another service-side introduction
23442 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
23443 - Bridges now skip DNS self-tests, to act a little more stealthily.
23444 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
23445 bridges. Patch by "warms0x".
23446 - Fix internal bug-checking logic that was supposed to catch
23447 failures in digest generation so that it will fail more robustly
23448 if we ask for a nonexistent algorithm. Found by Coverity Scan.
23449 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
23450 - Report any failure in init_keys() calls launched because our
23451 IP address has changed. Spotted by Coverity Scan. Bugfix on
23452 0.1.1.4-alpha; fixes CID 484.
23454 o Minor bugfixes (log messages and documentation):
23455 - Remove a confusing dollar sign from the example fingerprint in the
23456 man page, and also make the example fingerprint a valid one. Fixes
23457 bug 4309; bugfix on 0.2.1.3-alpha.
23458 - The next version of Windows will be called Windows 8, and it has
23459 a major version of 6, minor version of 2. Correctly identify that
23460 version instead of calling it "Very recent version". Resolves
23461 ticket 4153; reported by funkstar.
23462 - Downgrade log messages about circuit timeout calibration from
23463 "notice" to "info": they don't require or suggest any human
23464 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
23465 bugfix on 0.2.2.14-alpha.
23468 - Turn on directory request statistics by default and include them in
23469 extra-info descriptors. Don't break if we have no GeoIP database.
23470 Backported from 0.2.3.1-alpha; implements ticket 3951.
23471 - Update to the October 4 2011 Maxmind GeoLite Country database.
23474 Changes in version 0.2.1.31 - 2011-10-26
23475 Tor 0.2.1.31 backports important security and privacy fixes for
23476 oldstable. This release is intended only for package maintainers and
23477 others who cannot use the 0.2.2 stable series. All others should be
23478 using Tor 0.2.2.x or newer.
23480 o Security fixes (also included in 0.2.2.x):
23481 - Replace all potentially sensitive memory comparison operations
23482 with versions whose runtime does not depend on the data being
23483 compared. This will help resist a class of attacks where an
23484 adversary can use variations in timing information to learn
23485 sensitive data. Fix for one case of bug 3122. (Safe memcmp
23486 implementation by Robert Ransom based partially on code by DJB.)
23487 - Fix an assert in parsing router descriptors containing IPv6
23488 addresses. This one took down the directory authorities when
23489 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
23491 o Privacy/anonymity fixes (also included in 0.2.2.x):
23492 - Clients and bridges no longer send TLS certificate chains on
23493 outgoing OR connections. Previously, each client or bridge would
23494 use the same cert chain for all outgoing OR connections until
23495 its IP address changes, which allowed any relay that the client
23496 or bridge contacted to determine which entry guards it is using.
23497 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23498 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23499 no longer considers that connection as suitable for satisfying a
23500 circuit EXTEND request. Now relays can protect clients from the
23501 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23502 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23503 that they initiated. Relays could distinguish incoming bridge
23504 connections from client connections, creating another avenue for
23505 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23506 Found by "frosty_un".
23507 - When receiving a hidden service descriptor, check that it is for
23508 the hidden service we wanted. Previously, Tor would store any
23509 hidden service descriptors that a directory gave it, whether it
23510 wanted them or not. This wouldn't have let an attacker impersonate
23511 a hidden service, but it did let directories pre-seed a client
23512 with descriptors that it didn't want. Bugfix on 0.0.6.
23513 - Avoid linkability based on cached hidden service descriptors: forget
23514 all hidden service descriptors cached as a client when processing a
23515 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
23516 - Make the bridge directory authority refuse to answer directory
23517 requests for "all" descriptors. It used to include bridge
23518 descriptors in its answer, which was a major information leak.
23519 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
23520 - Don't attach new streams to old rendezvous circuits after SIGNAL
23521 NEWNYM. Previously, we would keep using an existing rendezvous
23522 circuit if it remained open (i.e. if it were kept open by a
23523 long-lived stream, or if a new stream were attached to it before
23524 Tor could notice that it was old and no longer in use). Bugfix on
23525 0.1.1.15-rc; fixes bug 3375.
23527 o Minor bugfixes (also included in 0.2.2.x):
23528 - When we restart our relay, we might get a successful connection
23529 from the outside before we've started our reachability tests,
23530 triggering a warning: "ORPort found reachable, but I have no
23531 routerinfo yet. Failing to inform controller of success." This
23532 bug was harmless unless Tor is running under a controller
23533 like Vidalia, in which case the controller would never get a
23534 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
23536 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23537 enabled. Fixes bug 1526.
23538 - Remove undocumented option "-F" from tor-resolve: it hasn't done
23539 anything since 0.2.1.16-rc.
23540 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
23541 None of the cases where we did this before were wrong, but by making
23542 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
23543 - Fix a rare crash bug that could occur when a client was configured
23544 with a large number of bridges. Fixes bug 2629; bugfix on
23545 0.2.1.2-alpha. Bugfix by trac user "shitlei".
23546 - Correct the warning displayed when a rendezvous descriptor exceeds
23547 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
23549 - Fix an uncommon assertion failure when running with DNSPort under
23550 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
23551 - When warning about missing zlib development packages during compile,
23552 give the correct package names. Bugfix on 0.2.0.1-alpha.
23553 - Require that introduction point keys and onion keys have public
23554 exponent 65537. Bugfix on 0.2.0.10-alpha.
23555 - Do not crash when our configuration file becomes unreadable, for
23556 example due to a permissions change, between when we start up
23557 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
23559 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
23561 - Always NUL-terminate the sun_path field of a sockaddr_un before
23562 passing it to the kernel. (Not a security issue: kernels are
23563 smart enough to reject bad sockaddr_uns.) Found by Coverity;
23564 CID #428. Bugfix on Tor 0.2.0.3-alpha.
23565 - Don't stack-allocate the list of supplementary GIDs when we're
23566 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
23567 could take up to 256K, which is way too much stack. Found by
23568 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
23570 o Minor bugfixes (only in 0.2.1.x):
23571 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
23572 rely on them. Bugfix on 0.2.1.30.
23573 - Use git revisions instead of svn revisions when generating our
23574 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
23576 o Minor features (also included in 0.2.2.x):
23577 - Adjust the expiration time on our SSL session certificates to
23578 better match SSL certs seen in the wild. Resolves ticket 4014.
23579 - Allow nameservers with IPv6 address. Resolves bug 2574.
23580 - Update to the October 4 2011 Maxmind GeoLite Country database.
23583 Changes in version 0.2.3.5-alpha - 2011-09-28
23584 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
23585 bridge relays; fixes an assertion error that many users started hitting
23586 today; and adds the ability to refill token buckets more often than
23587 once per second, allowing significant performance improvements.
23590 - Bridge relays now do their directory fetches inside Tor TLS
23591 connections, like all the other clients do, rather than connecting
23592 directly to the DirPort like public relays do. Removes another
23593 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
23594 - Bridges relays now build circuits for themselves in a more similar
23595 way to how clients build them. Removes another avenue for
23596 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
23597 when bridges were introduced.
23600 - Fix an "Assertion md->held_by_node == 1 failed" error that could
23601 occur when the same microdescriptor was referenced by two node_t
23602 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
23604 o Major features (networking):
23605 - Add a new TokenBucketRefillInterval option to refill token buckets
23606 more frequently than once per second. This should improve network
23607 performance, alleviate queueing problems, and make traffic less
23608 bursty. Implements proposal 183; closes ticket 3630. Design by
23609 Florian Tschorsch and Björn Scheuermann; implementation by
23613 - Change an integer overflow check in the OpenBSD_Malloc code so
23614 that GCC is less likely to eliminate it as impossible. Patch
23615 from Mansour Moufid. Fixes bug 4059.
23617 o Minor bugfixes (usability):
23618 - Downgrade log messages about circuit timeout calibration from
23619 "notice" to "info": they don't require or suggest any human
23620 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
23621 bugfix on 0.2.2.14-alpha.
23623 o Minor features (diagnostics):
23624 - When the system call to create a listener socket fails, log the
23625 error message explaining why. This may help diagnose bug 4027.
23628 Changes in version 0.2.3.4-alpha - 2011-09-13
23629 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
23630 tweak to Tor's TLS handshake that makes relays and bridges that run
23631 this new version reachable from Iran again. It also fixes a few new
23632 bugs in 0.2.3.x, and teaches relays to recognize when they're not
23633 listed in the network consensus and republish.
23635 o Major bugfixes (also part of 0.2.2.33):
23636 - Avoid an assertion failure when reloading a configuration with
23637 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
23638 3923; bugfix on 0.2.2.25-alpha.
23640 o Minor features (security, also part of 0.2.2.33):
23641 - Check for replays of the public-key encrypted portion of an
23642 INTRODUCE1 cell, in addition to the current check for replays of
23643 the g^x value. This prevents a possible class of active attacks
23644 by an attacker who controls both an introduction point and a
23645 rendezvous point, and who uses the malleability of AES-CTR to
23646 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
23647 that these attacks are infeasible (requiring the attacker to send
23648 on the order of zettabytes of altered cells in a short interval),
23649 but we'd rather block them off in case there are any classes of
23650 this attack that we missed. Reported by Willem Pinckaers.
23652 o Minor features (also part of 0.2.2.33):
23653 - Adjust the expiration time on our SSL session certificates to
23654 better match SSL certs seen in the wild. Resolves ticket 4014.
23655 - Change the default required uptime for a relay to be accepted as
23656 a HSDir (hidden service directory) from 24 hours to 25 hours.
23657 Improves on 0.2.0.10-alpha; resolves ticket 2649.
23658 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
23659 authorities to abstain from voting on assignment of the HSDir
23660 consensus flag. Related to bug 2649.
23661 - Update to the September 6 2011 Maxmind GeoLite Country database.
23663 o Minor bugfixes (also part of 0.2.2.33):
23664 - Demote the 'replay detected' log message emitted when a hidden
23665 service receives the same Diffie-Hellman public key in two different
23666 INTRODUCE2 cells to info level. A normal Tor client can cause that
23667 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
23668 fixes part of bug 2442.
23669 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
23670 level. There is nothing that a hidden service's operator can do
23671 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
23673 - Clarify a log message specifying the characters permitted in
23674 HiddenServiceAuthorizeClient client names. Previously, the log
23675 message said that "[A-Za-z0-9+-_]" were permitted; that could have
23676 given the impression that every ASCII character between "+" and "_"
23677 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
23679 o Build fixes (also part of 0.2.2.33):
23680 - Clean up some code issues that prevented Tor from building on older
23681 BSDs. Fixes bug 3894; reported by "grarpamp".
23682 - Search for a platform-specific version of "ar" when cross-compiling.
23683 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
23686 - Fix a bug where the SocksPort option (for example) would get
23687 ignored and replaced by the default if a SocksListenAddress
23688 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
23692 - Relays now try regenerating and uploading their descriptor more
23693 frequently if they are not listed in the consensus, or if the
23694 version of their descriptor listed in the consensus is too
23695 old. This fix should prevent situations where a server declines
23696 to re-publish itself because it has done so too recently, even
23697 though the authorities decided not to list its recent-enough
23698 descriptor. Fix for bug 3327.
23701 - Relays now include a reason for regenerating their descriptors
23702 in an HTTP header when uploading to the authorities. This will
23703 make it easier to debug descriptor-upload issues in the future.
23704 - When starting as root and then changing our UID via the User
23705 control option, and we have a ControlSocket configured, make sure
23706 that the ControlSocket is owned by the same account that Tor will
23707 run under. Implements ticket 3421; fix by Jérémy Bobbio.
23710 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
23711 utility function used in the control-port code). This shouldn't
23712 ever happen unless Tor is completely out of memory, but if it did
23713 happen and Tor somehow recovered from it, Tor could have sent a log
23714 message to a control port in the middle of a reply to a controller
23715 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
23716 - Make 'FetchUselessDescriptors' cause all descriptor types and
23717 all consensus types (including microdescriptors) to get fetched.
23718 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
23720 o Code refactoring:
23721 - Make a new "entry connection" struct as an internal subtype of "edge
23722 connection", to simplify the code and make exit connections smaller.
23725 Changes in version 0.2.2.33 - 2011-09-13
23726 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
23727 TLS handshake that makes relays and bridges that run this new version
23728 reachable from Iran again.
23731 - Avoid an assertion failure when reloading a configuration with
23732 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
23733 3923; bugfix on 0.2.2.25-alpha.
23735 o Minor features (security):
23736 - Check for replays of the public-key encrypted portion of an
23737 INTRODUCE1 cell, in addition to the current check for replays of
23738 the g^x value. This prevents a possible class of active attacks
23739 by an attacker who controls both an introduction point and a
23740 rendezvous point, and who uses the malleability of AES-CTR to
23741 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
23742 that these attacks are infeasible (requiring the attacker to send
23743 on the order of zettabytes of altered cells in a short interval),
23744 but we'd rather block them off in case there are any classes of
23745 this attack that we missed. Reported by Willem Pinckaers.
23748 - Adjust the expiration time on our SSL session certificates to
23749 better match SSL certs seen in the wild. Resolves ticket 4014.
23750 - Change the default required uptime for a relay to be accepted as
23751 a HSDir (hidden service directory) from 24 hours to 25 hours.
23752 Improves on 0.2.0.10-alpha; resolves ticket 2649.
23753 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
23754 authorities to abstain from voting on assignment of the HSDir
23755 consensus flag. Related to bug 2649.
23756 - Update to the September 6 2011 Maxmind GeoLite Country database.
23758 o Minor bugfixes (documentation and log messages):
23759 - Correct the man page to explain that HashedControlPassword and
23760 CookieAuthentication can both be set, in which case either method
23761 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
23762 when we decided to allow these config options to both be set. Issue
23763 raised by bug 3898.
23764 - Demote the 'replay detected' log message emitted when a hidden
23765 service receives the same Diffie-Hellman public key in two different
23766 INTRODUCE2 cells to info level. A normal Tor client can cause that
23767 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
23768 fixes part of bug 2442.
23769 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
23770 level. There is nothing that a hidden service's operator can do
23771 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
23773 - Clarify a log message specifying the characters permitted in
23774 HiddenServiceAuthorizeClient client names. Previously, the log
23775 message said that "[A-Za-z0-9+-_]" were permitted; that could have
23776 given the impression that every ASCII character between "+" and "_"
23777 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
23780 - Provide a substitute implementation of lround() for MSVC, which
23781 apparently lacks it. Patch from Gisle Vanem.
23782 - Clean up some code issues that prevented Tor from building on older
23783 BSDs. Fixes bug 3894; reported by "grarpamp".
23784 - Search for a platform-specific version of "ar" when cross-compiling.
23785 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
23788 Changes in version 0.2.3.3-alpha - 2011-09-01
23789 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
23790 security, and provides client-side support for the microdescriptor
23791 and optimistic data features introduced earlier in the 0.2.3.x
23792 series. It also includes numerous critical bugfixes in the (optional)
23793 bufferevent-based networking backend.
23795 o Major features (stream isolation):
23796 - You can now configure Tor so that streams from different
23797 applications are isolated on different circuits, to prevent an
23798 attacker who sees your streams as they leave an exit node from
23799 linking your sessions to one another. To do this, choose some way
23800 to distinguish the applications: have them connect to different
23801 SocksPorts, or have one of them use SOCKS4 while the other uses
23802 SOCKS5, or have them pass different authentication strings to the
23803 SOCKS proxy. Then, use the new SocksPort syntax to configure the
23804 degree of isolation you need. This implements Proposal 171.
23805 - There's a new syntax for specifying multiple client ports (such as
23806 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
23807 multiple *Port entries with full addr:port syntax on each.
23808 The old *ListenAddress format is still supported, but you can't
23809 mix it with the new *Port syntax.
23811 o Major features (other):
23812 - Enable microdescriptor fetching by default for clients. This allows
23813 clients to download a much smaller amount of directory information.
23814 To disable it (and go back to the old-style consensus and
23815 descriptors), set "UseMicrodescriptors 0" in your torrc file.
23816 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
23817 "PortForwarding" config option), now supports Windows.
23818 - When using an exit relay running 0.2.3.x, clients can now
23819 "optimistically" send data before the exit relay reports that
23820 the stream has opened. This saves a round trip when starting
23821 connections where the client speaks first (such as web browsing).
23822 This behavior is controlled by a consensus parameter (currently
23823 disabled). To turn it on or off manually, use the "OptimisticData"
23824 torrc option. Implements proposal 181; code by Ian Goldberg.
23826 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
23827 - When using IOCP on Windows, we need to enable Libevent windows
23829 - The IOCP backend now works even when the user has not specified
23830 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
23831 Fixes part of bug 3752.
23832 - Correctly record the bytes we've read and written when using
23833 bufferevents, so that we can include them in our bandwidth history
23834 and advertised bandwidth. Fixes bug 3803.
23835 - Apply rate-limiting only at the bottom of a chain of filtering
23836 bufferevents. This prevents us from filling up internal read
23837 buffers and violating rate-limits when filtering bufferevents
23838 are enabled. Fixes part of bug 3804.
23839 - Add high-watermarks to the output buffers for filtered
23840 bufferevents. This prevents us from filling up internal write
23841 buffers and wasting CPU cycles when filtering bufferevents are
23842 enabled. Fixes part of bug 3804.
23843 - Correctly notice when data has been written from a bufferevent
23844 without flushing it completely. Fixes bug 3805.
23845 - Fix a bug where server-side tunneled bufferevent-based directory
23846 streams would get closed prematurely. Fixes bug 3814.
23847 - Fix a use-after-free error with per-connection rate-limiting
23848 buckets. Fixes bug 3888.
23850 o Major bugfixes (also part of 0.2.2.31-rc):
23851 - If we're configured to write our ControlPorts to disk, only write
23852 them after switching UID and creating the data directory. This way,
23853 we don't fail when starting up with a nonexistent DataDirectory
23854 and a ControlPortWriteToFile setting based on that directory. Fixes
23855 bug 3747; bugfix on Tor 0.2.2.26-beta.
23858 - Added a new CONF_CHANGED event so that controllers can be notified
23859 of any configuration changes made by other controllers, or by the
23860 user. Implements ticket 1692.
23861 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
23862 leak when using bufferevents, and lets Libevent worry about how to
23863 best copy data out of a buffer.
23864 - Replace files in stats/ rather than appending to them. Now that we
23865 include statistics in extra-info descriptors, it makes no sense to
23866 keep old statistics forever. Implements ticket 2930.
23868 o Minor features (build compatibility):
23869 - Limited, experimental support for building with nmake and MSVC.
23870 - Provide a substitute implementation of lround() for MSVC, which
23871 apparently lacks it. Patch from Gisle Vanem.
23873 o Minor features (also part of 0.2.2.31-rc):
23874 - Update to the August 2 2011 Maxmind GeoLite Country database.
23876 o Minor bugfixes (on 0.2.3.x-alpha):
23877 - Fix a spurious warning when parsing SOCKS requests with
23878 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
23879 - Get rid of a harmless warning that could happen on relays running
23880 with bufferevents. The warning was caused by someone doing an http
23881 request to a relay's orport. Also don't warn for a few related
23882 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
23884 o Minor bugfixes (on 2.2.x and earlier):
23885 - Correct the man page to explain that HashedControlPassword and
23886 CookieAuthentication can both be set, in which case either method
23887 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
23888 when we decided to allow these config options to both be set. Issue
23889 raised by bug 3898.
23890 - The "--quiet" and "--hush" options now apply not only to Tor's
23891 behavior before logs are configured, but also to Tor's behavior in
23892 the absence of configured logs. Fixes bug 3550; bugfix on
23895 o Minor bugfixes (also part of 0.2.2.31-rc):
23896 - Write several files in text mode, on OSes that distinguish text
23897 mode from binary mode (namely, Windows). These files are:
23898 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
23899 that collect those statistics; 'client_keys' and 'hostname' for
23900 hidden services that use authentication; and (in the tor-gencert
23901 utility) newly generated identity and signing keys. Previously,
23902 we wouldn't specify text mode or binary mode, leading to an
23903 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
23904 the DirRecordUsageByCountry option which would have triggered
23905 the assertion failure was added), although this assertion failure
23906 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
23907 - Selectively disable deprecation warnings on OS X because Lion
23908 started deprecating the shipped copy of openssl. Fixes bug 3643.
23909 - Remove an extra pair of quotation marks around the error
23910 message in control-port STATUS_GENERAL BUG events. Bugfix on
23911 0.1.2.6-alpha; fixes bug 3732.
23912 - When unable to format an address as a string, report its value
23913 as "???" rather than reusing the last formatted address. Bugfix
23916 o Code simplifications and refactoring:
23917 - Rewrite the listener-selection logic so that parsing which ports
23918 we want to listen on is now separate from binding to the ports
23922 - Building Tor with bufferevent support now requires Libevent
23923 2.0.13-stable or later. Previous versions of Libevent had bugs in
23924 SSL-related bufferevents and related issues that would make Tor
23925 work badly with bufferevents. Requiring 2.0.13-stable also allows
23926 Tor with bufferevents to take advantage of Libevent APIs
23927 introduced after 2.0.8-rc.
23930 Changes in version 0.2.2.32 - 2011-08-27
23931 The Tor 0.2.2 release series is dedicated to the memory of Andreas
23932 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
23933 a founder of the PETS community, a leader in our field, a mentor,
23934 and a friend. He left us with these words: "I had the possibility
23935 to contribute to this world that is not as it should be. I hope I
23936 could help in some areas to make the world a better place, and that
23937 I could also encourage other people to be engaged in improving the
23938 world. Please, stay engaged. This world needs you, your love, your
23939 initiative -- now I cannot be part of that anymore."
23941 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
23942 ready. More than two years in the making, this release features improved
23943 client performance and hidden service reliability, better compatibility
23944 for Android, correct behavior for bridges that listen on more than
23945 one address, more extensible and flexible directory object handling,
23946 better reporting of network statistics, improved code security, and
23947 many many other features and bugfixes.
23950 Changes in version 0.2.2.31-rc - 2011-08-17
23951 Tor 0.2.2.31-rc is the second and hopefully final release candidate
23952 for the Tor 0.2.2.x series.
23955 - Remove an extra pair of quotation marks around the error
23956 message in control-port STATUS_GENERAL BUG events. Bugfix on
23957 0.1.2.6-alpha; fixes bug 3732.
23958 - If we're configured to write our ControlPorts to disk, only write
23959 them after switching UID and creating the data directory. This way,
23960 we don't fail when starting up with a nonexistent DataDirectory
23961 and a ControlPortWriteToFile setting based on that directory. Fixes
23962 bug 3747; bugfix on Tor 0.2.2.26-beta.
23965 - Update to the August 2 2011 Maxmind GeoLite Country database.
23968 - Allow GETINFO fingerprint to return a fingerprint even when
23969 we have not yet built a router descriptor. Fixes bug 3577;
23970 bugfix on 0.2.0.1-alpha.
23971 - Write several files in text mode, on OSes that distinguish text
23972 mode from binary mode (namely, Windows). These files are:
23973 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
23974 that collect those statistics; 'client_keys' and 'hostname' for
23975 hidden services that use authentication; and (in the tor-gencert
23976 utility) newly generated identity and signing keys. Previously,
23977 we wouldn't specify text mode or binary mode, leading to an
23978 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
23979 the DirRecordUsageByCountry option which would have triggered
23980 the assertion failure was added), although this assertion failure
23981 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
23982 - Selectively disable deprecation warnings on OS X because Lion
23983 started deprecating the shipped copy of openssl. Fixes bug 3643.
23984 - When unable to format an address as a string, report its value
23985 as "???" rather than reusing the last formatted address. Bugfix
23989 Changes in version 0.2.3.2-alpha - 2011-07-18
23990 Tor 0.2.3.2-alpha introduces two new experimental features:
23991 microdescriptors and pluggable transports. It also continues cleaning
23992 up a variety of recently introduced features.
23995 - Clients can now use microdescriptors instead of regular descriptors
23996 to build circuits. Microdescriptors are authority-generated
23997 summaries of regular descriptors' contents, designed to change
23998 very rarely (see proposal 158 for details). This feature is
23999 designed to save bandwidth, especially for clients on slow internet
24000 connections. It's off by default for now, since nearly no caches
24001 support it, but it will be on-by-default for clients in a future
24002 version. You can use the UseMicrodescriptors option to turn it on.
24003 - Tor clients using bridges can now be configured to use a separate
24004 'transport' proxy for each bridge. This approach helps to resist
24005 censorship by allowing bridges to use protocol obfuscation
24006 plugins. It implements part of proposal 180. Implements ticket 2841.
24007 - While we're trying to bootstrap, record how many TLS connections
24008 fail in each state, and report which states saw the most failures
24009 in response to any bootstrap failures. This feature may speed up
24010 diagnosis of censorship events. Implements ticket 3116.
24012 o Major bugfixes (on 0.2.3.1-alpha):
24013 - When configuring a large set of nodes in EntryNodes (as with
24014 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
24015 random subset to be guards, and choose them in random
24016 order. Fixes bug 2798.
24017 - Tor could crash when remembering a consensus in a non-used consensus
24018 flavor without having a current consensus set. Fixes bug 3361.
24019 - Comparing an unknown address to a microdescriptor's shortened exit
24020 policy would always give a "rejected" result. Fixes bug 3599.
24021 - Using microdescriptors as a client no longer prevents Tor from
24022 uploading and downloading hidden service descriptors. Fixes
24026 - Allow nameservers with IPv6 address. Resolves bug 2574.
24027 - Accept attempts to include a password authenticator in the
24028 handshake, as supported by SOCKS5. This handles SOCKS clients that
24029 don't know how to omit a password when authenticating. Resolves
24031 - When configuring a large set of nodes in EntryNodes, and there are
24032 enough of them listed as Guard so that we don't need to consider
24033 the non-guard entries, prefer the ones listed with the Guard flag.
24034 - Check for and recover from inconsistency in the microdescriptor
24035 cache. This will make it harder for us to accidentally free a
24036 microdescriptor without removing it from the appropriate data
24037 structures. Fixes issue 3135; issue noted by "wanoskarnet".
24038 - Log SSL state transitions at log level DEBUG, log domain
24039 HANDSHAKE. This can be useful for debugging censorship events.
24040 Implements ticket 3264.
24041 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
24042 implements ticket 3439.
24044 o Minor bugfixes (on 0.2.3.1-alpha):
24045 - Do not free all general-purpose regular descriptors just
24046 because microdescriptor use is enabled. Fixes bug 3113.
24047 - Correctly link libevent_openssl when --enable-static-libevent
24048 is passed to configure. Fixes bug 3118.
24049 - Bridges should not complain during their heartbeat log messages that
24050 they are unlisted in the consensus: that's more or less the point
24051 of being a bridge. Fixes bug 3183.
24052 - Report a SIGNAL event to controllers when acting on a delayed
24053 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
24054 event to the controller if we acted on a SIGNAL NEWNYM command
24055 immediately, and otherwise not report a SIGNAL event for the
24056 command at all. Fixes bug 3349.
24057 - Fix a crash when handling the SIGNAL controller command or
24058 reporting ERR-level status events with bufferevents enabled. Found
24059 by Robert Ransom. Fixes bug 3367.
24060 - Always ship the tor-fw-helper manpage in our release tarballs.
24061 Fixes bug 3389. Reported by Stephen Walker.
24062 - Fix a class of double-mark-for-close bugs when bufferevents
24063 are enabled. Fixes bug 3403.
24064 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
24065 - Add SIGNAL to the list returned by the 'GETINFO events/names'
24066 control-port command. Fixes part of bug 3465.
24067 - Prevent using negative indices during unit test runs when read_all()
24068 fails. Spotted by coverity.
24069 - Fix a rare memory leak when checking the nodelist without it being
24070 present. Found by coverity.
24071 - Only try to download a microdescriptor-flavored consensus from
24072 a directory cache that provides them.
24074 o Minor bugfixes (on 0.2.2.x and earlier):
24075 - Assert that hidden-service-related operations are not performed
24076 using single-hop circuits. Previously, Tor would assert that
24077 client-side streams are not attached to single-hop circuits,
24078 but not that other sensitive operations on the client and service
24079 side are not performed using single-hop circuits. Fixes bug 3332;
24081 - Don't publish a new relay descriptor when we reload our onion key,
24082 unless the onion key has actually changed. Fixes bug 3263 and
24083 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
24084 - Allow GETINFO fingerprint to return a fingerprint even when
24085 we have not yet built a router descriptor. Fixes bug 3577;
24086 bugfix on 0.2.0.1-alpha.
24087 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
24088 on 0.2.2.4-alpha; fixes bug 3427.
24090 o Code simplification and refactoring:
24091 - Use tor_sscanf() in place of scanf() in more places through the
24092 code. This makes us a little more locale-independent, and
24093 should help shut up code-analysis tools that can't tell
24094 a safe sscanf string from a dangerous one.
24095 - Use tt_assert(), not tor_assert(), for checking for test failures.
24096 This makes the unit tests more able to go on in the event that
24098 - Split connection_about_to_close() into separate functions for each
24102 - On Windows, we now define the _WIN32_WINNT macros only if they
24103 are not already defined. This lets the person building Tor decide,
24104 if they want, to require a later version of Windows.
24107 Changes in version 0.2.2.30-rc - 2011-07-07
24108 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
24109 series. It fixes a few smaller bugs, but generally appears stable.
24110 Please test it and let us know whether it is!
24113 - Send a SUCCEEDED stream event to the controller when a reverse
24114 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
24115 discovered by katmagic.
24116 - Always NUL-terminate the sun_path field of a sockaddr_un before
24117 passing it to the kernel. (Not a security issue: kernels are
24118 smart enough to reject bad sockaddr_uns.) Found by Coverity;
24119 CID #428. Bugfix on Tor 0.2.0.3-alpha.
24120 - Don't stack-allocate the list of supplementary GIDs when we're
24121 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
24122 could take up to 256K, which is way too much stack. Found by
24123 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
24124 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
24125 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
24126 fixes part of bug 3465.
24127 - Fix a memory leak when receiving a descriptor for a hidden
24128 service we didn't ask for. Found by Coverity; CID #30. Bugfix
24132 - Update to the July 1 2011 Maxmind GeoLite Country database.
24135 Changes in version 0.2.2.29-beta - 2011-06-20
24136 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
24137 have bridge lines in their torrc but don't want to use them; gets
24138 us closer to having the control socket feature working on Debian;
24139 and fixes a variety of smaller bugs.
24142 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
24143 When we changed the default behavior to "use bridges if any
24144 are listed in the torrc", we surprised users who had bridges
24145 in their torrc files but who didn't actually want to use them.
24146 Partial resolution for bug 3354.
24149 - Don't attach new streams to old rendezvous circuits after SIGNAL
24150 NEWNYM. Previously, we would keep using an existing rendezvous
24151 circuit if it remained open (i.e. if it were kept open by a
24152 long-lived stream, or if a new stream were attached to it before
24153 Tor could notice that it was old and no longer in use). Bugfix on
24154 0.1.1.15-rc; fixes bug 3375.
24157 - Fix a bug when using ControlSocketsGroupWritable with User. The
24158 directory's group would be checked against the current group, not
24159 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
24160 bugfix on 0.2.2.26-beta.
24161 - Make connection_printf_to_buf()'s behavior sane. Its callers
24162 expect it to emit a CRLF iff the format string ends with CRLF;
24163 it actually emitted a CRLF iff (a) the format string ended with
24164 CRLF or (b) the resulting string was over 1023 characters long or
24165 (c) the format string did not end with CRLF *and* the resulting
24166 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
24167 fixes part of bug 3407.
24168 - Make send_control_event_impl()'s behavior sane. Its callers
24169 expect it to always emit a CRLF at the end of the string; it
24170 might have emitted extra control characters as well. Bugfix on
24171 0.1.1.9-alpha; fixes another part of bug 3407.
24172 - Make crypto_rand_int() check the value of its input correctly.
24173 Previously, it accepted values up to UINT_MAX, but could return a
24174 negative number if given a value above INT_MAX+1. Found by George
24175 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
24176 - Avoid a segfault when reading a malformed circuit build state
24177 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
24179 - When asked about a DNS record type we don't support via a
24180 client DNSPort, reply with NOTIMPL rather than an empty
24181 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
24182 - Fix a rare memory leak during stats writing. Found by coverity.
24185 - Update to the June 1 2011 Maxmind GeoLite Country database.
24187 o Code simplifications and refactoring:
24188 - Remove some dead code as indicated by coverity.
24189 - Remove a few dead assignments during router parsing. Found by
24191 - Add some forgotten return value checks during unit tests. Found
24193 - Don't use 1-bit wide signed bit fields. Found by coverity.
24196 Changes in version 0.2.2.28-beta - 2011-06-04
24197 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
24198 fixed a big bug in whether relays stay in the consensus consistently,
24199 we moved closer to handling bridges and hidden services correctly,
24200 and we started the process of better handling the dreaded "my Vidalia
24201 died, and now my Tor demands a password when I try to reconnect to it"
24205 - Don't decide to make a new descriptor when receiving a HUP signal.
24206 This bug has caused a lot of 0.2.2.x relays to disappear from the
24207 consensus periodically. Fixes the most common case of triggering
24208 bug 1810; bugfix on 0.2.2.7-alpha.
24209 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
24210 - Don't try to build descriptors if "ORPort auto" is set and we
24211 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
24213 - Resolve a crash that occurred when setting BridgeRelay to 1 with
24214 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
24215 - Apply circuit timeouts to opened hidden-service-related circuits
24216 based on the correct start time. Previously, we would apply the
24217 circuit build timeout based on time since the circuit's creation;
24218 it was supposed to be applied based on time since the circuit
24219 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
24220 - Use the same circuit timeout for client-side introduction
24221 circuits as for other four-hop circuits, rather than the timeout
24222 for single-hop directory-fetch circuits; the shorter timeout may
24223 have been appropriate with the static circuit build timeout in
24224 0.2.1.x and earlier, but caused many hidden service access attempts
24225 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
24226 on 0.2.2.2-alpha; fixes another part of bug 1297.
24227 - In ticket 2511 we fixed a case where you could use an unconfigured
24228 bridge if you had configured it as a bridge the last time you ran
24229 Tor. Now fix another edge case: if you had configured it as a bridge
24230 but then switched to a different bridge via the controller, you
24231 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
24235 - Add an __OwningControllerProcess configuration option and a
24236 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
24237 that when it exits, Tor will shut down. Implements feature 3049.
24238 - If "UseBridges 1" is set and no bridges are configured, Tor will
24239 now refuse to build any circuits until some bridges are set.
24240 If "UseBridges auto" is set, Tor will use bridges if they are
24241 configured and we are not running as a server, but otherwise will
24242 make circuits as usual. The new default is "auto". Patch by anonym,
24243 so the Tails LiveCD can stop automatically revealing you as a Tor
24247 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
24248 - Remove a trailing asterisk from "exit-policy/default" in the
24249 output of the control port command "GETINFO info/names". Bugfix
24251 - Use a wide type to hold sockets when built for 64-bit Windows builds.
24253 - Warn when the user configures two HiddenServiceDir lines that point
24254 to the same directory. Bugfix on 0.0.6 (the version introducing
24255 HiddenServiceDir); fixes bug 3289.
24256 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
24257 part of bug 2748; bugfix on 0.2.0.10-alpha.
24258 - Log malformed requests for rendezvous descriptors as protocol
24259 warnings, not warnings. Also, use a more informative log message
24260 in case someone sees it at log level warning without prior
24261 info-level messages. Fixes the other part of bug 2748; bugfix
24263 - Clear the table recording the time of the last request for each
24264 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
24265 Previously, we would clear our HS descriptor cache on SIGNAL
24266 NEWNYM, but if we had previously retrieved a descriptor (or tried
24267 to) from every directory responsible for it, we would refuse to
24268 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
24270 - Fix a log message that said "bits" while displaying a value in
24271 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
24273 - When checking for 1024-bit keys, check for 1024 bits, not 128
24274 bytes. This allows Tor to correctly discard keys of length 1017
24275 through 1023. Bugfix on 0.0.9pre5.
24278 - Relays now log the reason for publishing a new relay descriptor,
24279 so we have a better chance of hunting down instances of bug 1810.
24280 Resolves ticket 3252.
24281 - Revise most log messages that refer to nodes by nickname to
24282 instead use the "$key=nickname at address" format. This should be
24283 more useful, especially since nicknames are less and less likely
24284 to be unique. Resolves ticket 3045.
24285 - Log (at info level) when purging pieces of hidden-service-client
24286 state because of SIGNAL NEWNYM.
24289 - Remove undocumented option "-F" from tor-resolve: it hasn't done
24290 anything since 0.2.1.16-rc.
24293 Changes in version 0.2.2.27-beta - 2011-05-18
24294 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
24295 release, and also adds a few more general bugfixes.
24298 - Fix a crash bug when changing bridges in a running Tor process.
24299 Fixes bug 3213; bugfix on 0.2.2.26-beta.
24300 - When the controller configures a new bridge, don't wait 10 to 60
24301 seconds before trying to fetch its descriptor. Bugfix on
24302 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
24305 - Require that onion keys have exponent 65537 in microdescriptors too.
24306 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
24307 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
24308 Changed the limit to 512 characters by removing base64 newlines.
24309 Fixes bug 2752. Fix by Michael Yakubovich.
24310 - When a client starts or stops using bridges, never use a circuit
24311 that was built before the configuration change. This behavior could
24312 put at risk a user who uses bridges to ensure that her traffic
24313 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
24317 Changes in version 0.2.2.26-beta - 2011-05-17
24318 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
24319 also introduces a new "socksport auto" approach that should make it
24320 easier to run multiple Tors on the same system, and does a lot of
24321 cleanup to get us closer to a release candidate.
24323 o Security/privacy fixes:
24324 - Replace all potentially sensitive memory comparison operations
24325 with versions whose runtime does not depend on the data being
24326 compared. This will help resist a class of attacks where an
24327 adversary can use variations in timing information to learn
24328 sensitive data. Fix for one case of bug 3122. (Safe memcmp
24329 implementation by Robert Ransom based partially on code by DJB.)
24330 - When receiving a hidden service descriptor, check that it is for
24331 the hidden service we wanted. Previously, Tor would store any
24332 hidden service descriptors that a directory gave it, whether it
24333 wanted them or not. This wouldn't have let an attacker impersonate
24334 a hidden service, but it did let directories pre-seed a client
24335 with descriptors that it didn't want. Bugfix on 0.0.6.
24336 - On SIGHUP, do not clear out all TrackHostExits mappings, client
24337 DNS cache entries, and virtual address mappings: that's what
24338 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
24341 - The options SocksPort, ControlPort, and so on now all accept a
24342 value "auto" that opens a socket on an OS-selected port. A
24343 new ControlPortWriteToFile option tells Tor to write its
24344 actual control port or ports to a chosen file. If the option
24345 ControlPortFileGroupReadable is set, the file is created as
24346 group-readable. Now users can run two Tor clients on the same
24347 system without needing to manually mess with parameters. Resolves
24348 part of ticket 3076.
24349 - Set SO_REUSEADDR on all sockets, not just listeners. This should
24350 help busy exit nodes avoid running out of useable ports just
24351 because all the ports have been used in the near past. Resolves
24355 - New "GETINFO net/listeners/(type)" controller command to return
24356 a list of addresses and ports that are bound for listeners for a
24357 given connection type. This is useful when the user has configured
24358 "SocksPort auto" and the controller needs to know which port got
24359 chosen. Resolves another part of ticket 3076.
24360 - Add a new ControlSocketsGroupWritable configuration option: when
24361 it is turned on, ControlSockets are group-writeable by the default
24362 group of the current user. Patch by Jérémy Bobbio; implements
24364 - Tor now refuses to create a ControlSocket in a directory that is
24365 world-readable (or group-readable if ControlSocketsGroupWritable
24366 is 0). This is necessary because some operating systems do not
24367 enforce permissions on an AF_UNIX sockets. Permissions on the
24368 directory holding the socket, however, seems to work everywhere.
24369 - Rate-limit a warning about failures to download v2 networkstatus
24370 documents. Resolves part of bug 1352.
24371 - Backport code from 0.2.3.x that allows directory authorities to
24372 clean their microdescriptor caches. Needed to resolve bug 2230.
24373 - When an HTTPS proxy reports "403 Forbidden", we now explain
24374 what it means rather than calling it an unexpected status code.
24375 Closes bug 2503. Patch from Michael Yakubovich.
24376 - Update to the May 1 2011 Maxmind GeoLite Country database.
24379 - Authorities now clean their microdesc cache periodically and when
24380 reading from disk initially, not only when adding new descriptors.
24381 This prevents a bug where we could lose microdescriptors. Bugfix
24382 on 0.2.2.6-alpha. Fixes bug 2230.
24383 - Do not crash when our configuration file becomes unreadable, for
24384 example due to a permissions change, between when we start up
24385 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
24387 - Avoid a bug that would keep us from replacing a microdescriptor
24388 cache on Windows. (We would try to replace the file while still
24389 holding it open. That's fine on Unix, but Windows doesn't let us
24390 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
24391 - Add missing explanations for the authority-related torrc options
24392 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
24393 man page. Resolves issue 2379.
24394 - As an authority, do not upload our own vote or signature set to
24395 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
24396 it would get flagged as a duplicate. Resolves bug 3026.
24397 - Accept hidden service descriptors if we think we might be a hidden
24398 service directory, regardless of what our consensus says. This
24399 helps robustness, since clients and hidden services can sometimes
24400 have a more up-to-date view of the network consensus than we do,
24401 and if they think that the directory authorities list us a HSDir,
24402 we might actually be one. Related to bug 2732; bugfix on
24404 - When a controller changes TrackHostExits, remove mappings for
24405 hosts that should no longer have their exits tracked. Bugfix on
24407 - When a controller changes VirtualAddrNetwork, remove any mappings
24408 for hosts that were automapped to the old network. Bugfix on
24410 - When a controller changes one of the AutomapHosts* options, remove
24411 any mappings for hosts that should no longer be automapped. Bugfix
24413 - Do not reset the bridge descriptor download status every time we
24414 re-parse our configuration or get a configuration change. Fixes
24415 bug 3019; bugfix on 0.2.0.3-alpha.
24417 o Minor bugfixes (code cleanup):
24418 - When loading the microdesc journal, remember its current size.
24419 In 0.2.2, this helps prevent the microdesc journal from growing
24420 without limit on authorities (who are the only ones to use it in
24421 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
24422 Fix posted by "cypherpunks."
24423 - The microdesc journal is supposed to get rebuilt only if it is
24424 at least _half_ the length of the store, not _twice_ the length
24425 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
24426 - Fix a potential null-pointer dereference while computing a
24427 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
24429 - Avoid a possible null-pointer dereference when rebuilding the mdesc
24430 cache without actually having any descriptors to cache. Bugfix on
24431 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
24432 - If we fail to compute the identity digest of a v3 legacy keypair,
24433 warn, and don't use a buffer-full of junk instead. Bugfix on
24434 0.2.1.1-alpha; fixes bug 3106.
24435 - Resolve an untriggerable issue in smartlist_string_num_isin(),
24436 where if the function had ever in the future been used to check
24437 for the presence of a too-large number, it would have given an
24438 incorrect result. (Fortunately, we only used it for 16-bit
24439 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
24440 - Require that introduction point keys and onion handshake keys
24441 have a public exponent of 65537. Starts to fix bug 3207; bugfix
24444 o Removed features:
24445 - Caches no longer download and serve v2 networkstatus documents
24446 unless FetchV2Networkstatus flag is set: these documents haven't
24447 haven't been used by clients or relays since 0.2.0.x. Resolves
24451 Changes in version 0.2.3.1-alpha - 2011-05-05
24452 Tor 0.2.3.1-alpha adds some new experimental features, including support
24453 for an improved network IO backend, IOCP networking on Windows,
24454 microdescriptor caching, "fast-start" support for streams, and automatic
24455 home router configuration. There are also numerous internal improvements
24456 to try to make the code easier for developers to work with.
24458 This is the first alpha release in a new series, so expect there to be
24459 bugs. Users who would rather test out a more stable branch should
24460 stay with 0.2.2.x for now.
24463 - Tor can now optionally build with the "bufferevents" buffered IO
24464 backend provided by Libevent 2. To use this feature, make sure you
24465 have the latest possible version of Libevent, and pass the
24466 --enable-bufferevents flag to configure when building Tor from
24467 source. This feature will make our networking code more flexible,
24468 let us stack layers on each other, and let us use more efficient
24469 zero-copy transports where available.
24470 - As an experimental feature, Tor can use IOCP for networking on Windows.
24471 Once this code is tuned and optimized, it promises much better
24472 performance than the select-based backend we've used in the past. To
24473 try this feature, you must build Tor with Libevent 2, configure Tor
24474 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
24475 your torrc. There are known bugs here: only try this if you can help
24476 debug it as it breaks.
24477 - The EntryNodes option can now include country codes like {de} or IP
24478 addresses or network masks. Previously we had disallowed these options
24479 because we didn't have an efficient way to keep the list up to
24480 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
24481 - Exit nodes now accept and queue data on not-yet-connected streams.
24482 Previously, the client wasn't allowed to send data until the stream was
24483 connected, which slowed down all connections. This change will enable
24484 clients to perform a "fast-start" on streams and send data without
24485 having to wait for a confirmation that the stream has opened. (Patch
24486 from Ian Goldberg; implements the server side of Proposal 174.)
24487 - Tor now has initial support for automatic port mapping on the many
24488 home routers that support NAT-PMP or UPnP. (Not yet supported on
24489 Windows). To build the support code, you'll need to have libnatpnp
24490 library and/or the libminiupnpc library, and you'll need to enable the
24491 feature specifically by passing "--enable-upnp" and/or
24492 "--enable-natpnp" to configure. To turn it on, use the new
24493 PortForwarding option.
24494 - Caches now download, cache, and serve multiple "flavors" of the
24495 consensus, including a flavor that describes microdescriptors.
24496 - Caches now download, cache, and serve microdescriptors -- small
24497 summaries of router descriptors that are authenticated by all of the
24498 directory authorities. Once enough caches are running this code,
24499 clients will be able to save significant amounts of directory bandwidth
24500 by downloading microdescriptors instead of router descriptors.
24503 - Make logging resolution configurable with a new LogTimeGranularity
24504 option, and change the default from 1 millisecond to 1 second.
24505 Implements enhancement 1668.
24506 - We log which torrc file we're using on startup. Implements ticket
24508 - Ordinarily, Tor does not count traffic from private addresses (like
24509 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
24510 There is now a new option, CountPrivateBandwidth, to disable this
24511 behavior. Patch from Daniel Cagara.
24512 - New --enable-static-tor configure option for building Tor as
24513 statically as possible. Idea, general hackery and thoughts from
24514 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
24516 - If you set the NumCPUs option to 0, Tor will now try to detect how
24517 many CPUs you have. This is the new default behavior.
24518 - Turn on directory request statistics by default and include them in
24519 extra-info descriptors. Don't break if we have no GeoIP database.
24520 - Relays that set "ConnDirectionStatistics 1" write statistics on the
24521 bidirectional use of connections to disk every 24 hours.
24522 - Add a GeoIP file digest to the extra-info descriptor. Implements
24524 - The NodeFamily option -- which let you declare that you want to
24525 consider nodes to be part of a family whether they list themselves
24526 that way or not -- now allows IP address ranges and country codes.
24527 - Add a new 'Heartbeat' log message type to periodically log a message
24528 describing Tor's status at level Notice. This feature is meant for
24529 operators who log at notice, and want to make sure that their Tor
24530 server is still working. Implementation by George Kadianakis.
24532 o Minor bugfixes (on 0.2.2.25-alpha):
24533 - When loading the microdesc journal, remember its current size.
24534 In 0.2.2, this helps prevent the microdesc journal from growing
24535 without limit on authorities (who are the only ones to use it in
24536 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
24537 Fix posted by "cypherpunks."
24538 - The microdesc journal is supposed to get rebuilt only if it is
24539 at least _half_ the length of the store, not _twice_ the length
24540 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
24541 - If as an authority we fail to compute the identity digest of a v3
24542 legacy keypair, warn, and don't use a buffer-full of junk instead.
24543 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
24544 - Authorities now clean their microdesc cache periodically and when
24545 reading from disk initially, not only when adding new descriptors.
24546 This prevents a bug where we could lose microdescriptors. Bugfix
24549 o Minor features (controller):
24550 - Add a new SIGNAL event to the controller interface so that
24551 controllers can be notified when Tor handles a signal. Resolves
24552 issue 1955. Patch by John Brooks.
24553 - Add a new GETINFO option to get total bytes read and written. Patch
24554 from pipe, revised by atagar. Resolves ticket 2345.
24555 - Implement some GETINFO controller fields to provide information about
24556 the Tor process's pid, euid, username, and resource limits.
24559 - Our build system requires automake 1.6 or later to create the
24560 Makefile.in files. Previously, you could have used 1.4.
24561 This only affects developers and people building Tor from git;
24562 people who build Tor from the source distribution without changing
24563 the Makefile.am files should be fine.
24564 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
24565 so on. This is more robust against some of the failure modes
24566 associated with running the autotools pieces on their own.
24568 o Minor packaging issues:
24569 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
24570 already created. Patch from Andreas Stieger. Fixes bug 2573.
24572 o Code simplifications and refactoring:
24573 - A major revision to our internal node-selecting and listing logic.
24574 Tor already had at least two major ways to look at the question of
24575 "which Tor servers do we know about": a list of router descriptors,
24576 and a list of entries in the current consensus. With
24577 microdescriptors, we're adding a third. Having so many systems
24578 without an abstraction layer over them was hurting the codebase.
24579 Now, we have a new "node_t" abstraction that presents a consistent
24580 interface to a client's view of a Tor node, and holds (nearly) all
24581 of the mutable state formerly in routerinfo_t and routerstatus_t.
24582 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
24583 no longer link against Libevent: they never used it, but
24584 our library structure used to force them to link it.
24586 o Removed features:
24587 - Remove some old code to work around even older versions of Tor that
24588 used forked processes to handle DNS requests. Such versions of Tor
24589 are no longer in use as servers.
24591 o Documentation fixes:
24592 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
24593 - Add missing documentation for the authority-related torrc options
24594 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
24598 Changes in version 0.2.2.25-alpha - 2011-04-29
24599 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
24600 robust, routers no longer overreport their bandwidth, Win7 should crash
24601 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
24602 now prevents hidden service-related activity from being linkable. It
24603 provides more information to Vidalia so you can see if your bridge is
24604 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
24605 StrictNodes configuration options to make them more reliable, more
24606 understandable, and more regularly applied. If you use those options,
24607 please see the revised documentation for them in the manual page.
24610 - Relays were publishing grossly inflated bandwidth values because
24611 they were writing their state files wrong--now they write the
24612 correct value. Also, resume reading bandwidth history from the
24613 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
24614 - Improve hidden service robustness: When we find that we have
24615 extended a hidden service's introduction circuit to a relay not
24616 listed as an introduction point in the HS descriptor we currently
24617 have, retry with an introduction point from the current
24618 descriptor. Previously we would just give up. Fixes bugs 1024 and
24619 1930; bugfix on 0.2.0.10-alpha.
24620 - Clients now stop trying to use an exit node associated with a given
24621 destination by TrackHostExits if they fail to reach that exit node.
24622 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
24623 - Fix crash bug on platforms where gmtime and localtime can return
24624 NULL. Windows 7 users were running into this one. Fixes part of bug
24625 2077. Bugfix on all versions of Tor. Found by boboper.
24627 o Security and stability fixes:
24628 - Don't double-free a parsable, but invalid, microdescriptor, even if
24629 it is followed in the blob we're parsing by an unparsable
24630 microdescriptor. Fixes an issue reported in a comment on bug 2954.
24631 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
24632 - If the Nickname configuration option isn't given, Tor would pick a
24633 nickname based on the local hostname as the nickname for a relay.
24634 Because nicknames are not very important in today's Tor and the
24635 "Unnamed" nickname has been implemented, this is now problematic
24636 behavior: It leaks information about the hostname without being
24637 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
24638 introduced the Unnamed nickname. Reported by tagnaq.
24639 - Fix an uncommon assertion failure when running with DNSPort under
24640 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
24641 - Avoid linkability based on cached hidden service descriptors: forget
24642 all hidden service descriptors cached as a client when processing a
24643 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
24646 - Export GeoIP information on bridge usage to controllers even if we
24647 have not yet been running for 24 hours. Now Vidalia bridge operators
24648 can get more accurate and immediate feedback about their
24649 contributions to the network.
24651 o Major features and bugfixes (node selection):
24652 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
24653 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
24654 options. Previously, we had been ambiguous in describing what
24655 counted as an "exit" node, and what operations exactly "StrictNodes
24656 0" would permit. This created confusion when people saw nodes built
24657 through unexpected circuits, and made it hard to tell real bugs from
24658 surprises. Now the intended behavior is:
24659 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
24660 a node that delivers user traffic outside the Tor network.
24661 . "Entry", in the context of EntryNodes, means a node used as the
24662 first hop of a multihop circuit. It doesn't include direct
24663 connections to directory servers.
24664 . "ExcludeNodes" applies to all nodes.
24665 . "StrictNodes" changes the behavior of ExcludeNodes only. When
24666 StrictNodes is set, Tor should avoid all nodes listed in
24667 ExcludeNodes, even when it will make user requests fail. When
24668 StrictNodes is *not* set, then Tor should follow ExcludeNodes
24669 whenever it can, except when it must use an excluded node to
24670 perform self-tests, connect to a hidden service, provide a
24671 hidden service, fulfill a .exit request, upload directory
24672 information, or fetch directory information.
24673 Collectively, the changes to implement the behavior fix bug 1090.
24674 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
24675 a node is listed in both, it's treated as excluded.
24676 - ExcludeNodes now applies to directory nodes -- as a preference if
24677 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
24678 Don't exclude all the directory authorities and set StrictNodes to 1
24679 unless you really want your Tor to break.
24680 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
24681 - ExcludeExitNodes now overrides .exit requests.
24682 - We don't use bridges listed in ExcludeNodes.
24683 - When StrictNodes is 1:
24684 . We now apply ExcludeNodes to hidden service introduction points
24685 and to rendezvous points selected by hidden service users. This
24686 can make your hidden service less reliable: use it with caution!
24687 . If we have used ExcludeNodes on ourself, do not try relay
24688 reachability self-tests.
24689 . If we have excluded all the directory authorities, we will not
24690 even try to upload our descriptor if we're a relay.
24691 . Do not honor .exit requests to an excluded node.
24692 - Remove a misfeature that caused us to ignore the Fast/Stable flags
24693 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
24694 - When the set of permitted nodes changes, we now remove any mappings
24695 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
24697 - We never cannibalize a circuit that had excluded nodes on it, even
24698 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
24699 - Revert a change where we would be laxer about attaching streams to
24700 circuits than when building the circuits. This was meant to prevent
24701 a set of bugs where streams were never attachable, but our improved
24702 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
24703 - Keep track of how many times we launch a new circuit to handle a
24704 given stream. Too many launches could indicate an inconsistency
24705 between our "launch a circuit to handle this stream" logic and our
24706 "attach this stream to one of the available circuits" logic.
24707 - Improve log messages related to excluded nodes.
24710 - Fix a spurious warning when moving from a short month to a long
24711 month on relays with month-based BandwidthAccounting. Bugfix on
24712 0.2.2.17-alpha; fixes bug 3020.
24713 - When a client finds that an origin circuit has run out of 16-bit
24714 stream IDs, we now mark it as unusable for new streams. Previously,
24715 we would try to close the entire circuit. Bugfix on 0.0.6.
24716 - Add a forgotten cast that caused a compile warning on OS X 10.6.
24717 Bugfix on 0.2.2.24-alpha.
24718 - Be more careful about reporting the correct error from a failed
24719 connect() system call. Under some circumstances, it was possible to
24720 look at an incorrect value for errno when sending the end reason.
24721 Bugfix on 0.1.0.1-rc.
24722 - Correctly handle an "impossible" overflow cases in connection byte
24723 counting, where we write or read more than 4GB on an edge connection
24724 in a single second. Bugfix on 0.1.2.8-beta.
24725 - Correct the warning displayed when a rendezvous descriptor exceeds
24726 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
24728 - Clients and hidden services now use HSDir-flagged relays for hidden
24729 service descriptor downloads and uploads even if the relays have no
24730 DirPort set and the client has disabled TunnelDirConns. This will
24731 eventually allow us to give the HSDir flag to relays with no
24732 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
24733 - Downgrade "no current certificates known for authority" message from
24734 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
24735 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
24736 2917. Bugfix on 0.1.1.1-alpha.
24737 - Only limit the lengths of single HS descriptors, even when multiple
24738 HS descriptors are published to an HSDir relay in a single POST
24739 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
24740 - Write the current time into the LastWritten line in our state file,
24741 rather than the time from the previous write attempt. Also, stop
24742 trying to use a time of -1 in our log statements. Fixes bug 3039;
24743 bugfix on 0.2.2.14-alpha.
24744 - Be more consistent in our treatment of file system paths. "~" should
24745 get expanded to the user's home directory in the Log config option.
24746 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
24747 feature for the -f and --DataDirectory options.
24750 - Make sure every relay writes a state file at least every 12 hours.
24751 Previously, a relay could go for weeks without writing its state
24752 file, and on a crash could lose its bandwidth history, capacity
24753 estimates, client country statistics, and so on. Addresses bug 3012.
24754 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
24755 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
24756 clients are already deprecated because of security bugs.
24757 - Don't allow v0 hidden service authorities to act as clients.
24758 Required by fix for bug 3000.
24759 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
24760 by fix for bug 3000.
24761 - Ensure that no empty [dirreq-](read|write)-history lines are added
24762 to an extrainfo document. Implements ticket 2497.
24764 o Code simplification and refactoring:
24765 - Remove workaround code to handle directory responses from servers
24766 that had bug 539 (they would send HTTP status 503 responses _and_
24767 send a body too). Since only server versions before
24768 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
24769 keep the workaround in place.
24770 - Remove the old 'fuzzy time' logic. It was supposed to be used for
24771 handling calculations where we have a known amount of clock skew and
24772 an allowed amount of unknown skew. But we only used it in three
24773 places, and we never adjusted the known/unknown skew values. This is
24774 still something we might want to do someday, but if we do, we'll
24775 want to do it differently.
24776 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
24777 None of the cases where we did this before were wrong, but by making
24778 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
24779 - Use GetTempDir to find the proper temporary directory location on
24780 Windows when generating temporary files for the unit tests. Patch by
24784 Changes in version 0.2.2.24-alpha - 2011-04-08
24785 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
24786 prevented Tor clients from effectively using "multihomed" bridges,
24787 that is, bridges that listen on multiple ports or IP addresses so users
24788 can continue to use some of their addresses even if others get blocked.
24791 - Fix a bug where bridge users who configure the non-canonical
24792 address of a bridge automatically switch to its canonical
24793 address. If a bridge listens at more than one address, it should be
24794 able to advertise those addresses independently and any non-blocked
24795 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
24797 - If you configured Tor to use bridge A, and then quit and
24798 configured Tor to use bridge B instead, it would happily continue
24799 to use bridge A if it's still reachable. While this behavior is
24800 a feature if your goal is connectivity, in some scenarios it's a
24801 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
24802 - Directory authorities now use data collected from their own
24803 uptime observations when choosing whether to assign the HSDir flag
24804 to relays, instead of trusting the uptime value the relay reports in
24805 its descriptor. This change helps prevent an attack where a small
24806 set of nodes with frequently-changing identity keys can blackhole
24807 a hidden service. (Only authorities need upgrade; others will be
24808 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
24811 - When we restart our relay, we might get a successful connection
24812 from the outside before we've started our reachability tests,
24813 triggering a warning: "ORPort found reachable, but I have no
24814 routerinfo yet. Failing to inform controller of success." This
24815 bug was harmless unless Tor is running under a controller
24816 like Vidalia, in which case the controller would never get a
24817 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
24819 - Make directory authorities more accurate at recording when
24820 relays that have failed several reachability tests became
24821 unreachable, so we can provide more accuracy at assigning Stable,
24822 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
24823 - Fix an issue that prevented static linking of libevent on
24824 some platforms (notably Linux). Fixes bug 2698; bugfix on
24825 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
24826 the --with-static-libevent configure option).
24827 - We now ask the other side of a stream (the client or the exit)
24828 for more data on that stream when the amount of queued data on
24829 that stream dips low enough. Previously, we wouldn't ask the
24830 other side for more data until either it sent us more data (which
24831 it wasn't supposed to do if it had exhausted its window!) or we
24832 had completely flushed all our queued data. This flow control fix
24833 should improve throughput. Fixes bug 2756; bugfix on the earliest
24834 released versions of Tor (svn commit r152).
24835 - Avoid a double-mark-for-free warning when failing to attach a
24836 transparent proxy connection. (We thought we had fixed this in
24837 0.2.2.23-alpha, but it turns out our fix was checking the wrong
24838 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
24839 bug) and 0.2.2.23-alpha (the incorrect fix).
24840 - When warning about missing zlib development packages during compile,
24841 give the correct package names. Bugfix on 0.2.0.1-alpha.
24844 - Directory authorities now log the source of a rejected POSTed v3
24845 networkstatus vote.
24846 - Make compilation with clang possible when using
24847 --enable-gcc-warnings by removing two warning options that clang
24848 hasn't implemented yet and by fixing a few warnings. Implements
24850 - When expiring circuits, use microsecond timers rather than
24851 one-second timers. This can avoid an unpleasant situation where a
24852 circuit is launched near the end of one second and expired right
24853 near the beginning of the next, and prevent fluctuations in circuit
24855 - Use computed circuit-build timeouts to decide when to launch
24856 parallel introduction circuits for hidden services. (Previously,
24857 we would retry after 15 seconds.)
24858 - Update to the April 1 2011 Maxmind GeoLite Country database.
24861 - Create the /var/run/tor directory on startup on OpenSUSE if it is
24862 not already created. Patch from Andreas Stieger. Fixes bug 2573.
24864 o Documentation changes:
24865 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
24866 - Resolve all doxygen warnings except those for missing documentation.
24868 - Add doxygen documentation for more functions, fields, and types.
24871 Changes in version 0.2.2.23-alpha - 2011-03-08
24872 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
24873 they restart they don't lose their bandwidth capacity estimate. This
24874 release also fixes a diverse set of user-facing bugs, ranging from
24875 relays overrunning their rate limiting to clients falsely warning about
24876 clock skew to bridge descriptor leaks by our bridge directory authority.
24879 - Stop sending a CLOCK_SKEW controller status event whenever
24880 we fetch directory information from a relay that has a wrong clock.
24881 Instead, only inform the controller when it's a trusted authority
24882 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
24883 the rest of bug 1074.
24884 - Fix an assert in parsing router descriptors containing IPv6
24885 addresses. This one took down the directory authorities when
24886 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
24887 - Make the bridge directory authority refuse to answer directory
24888 requests for "all" descriptors. It used to include bridge
24889 descriptors in its answer, which was a major information leak.
24890 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
24891 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
24892 Tor would ignore their RelayBandwidthBurst setting,
24893 potentially using more bandwidth than expected. Bugfix on
24894 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
24895 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
24896 hidserv" in her torrc. The 'hidserv' argument never controlled
24897 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
24900 - Relays now save observed peak bandwidth throughput rates to their
24901 state file (along with total usage, which was already saved)
24902 so that they can determine their correct estimated bandwidth on
24903 restart. Resolves bug 1863, where Tor relays would reset their
24904 estimated bandwidth to 0 after restarting.
24905 - Directory authorities now take changes in router IP address and
24906 ORPort into account when determining router stability. Previously,
24907 if a router changed its IP or ORPort, the authorities would not
24908 treat it as having any downtime for the purposes of stability
24909 calculation, whereas clients would experience downtime since the
24910 change could take a while to propagate to them. Resolves issue 1035.
24911 - Enable Address Space Layout Randomization (ASLR) and Data Execution
24912 Prevention (DEP) by default on Windows to make it harder for
24913 attackers to exploit vulnerabilities. Patch from John Brooks.
24915 o Minor bugfixes (on 0.2.1.x and earlier):
24916 - Fix a rare crash bug that could occur when a client was configured
24917 with a large number of bridges. Fixes bug 2629; bugfix on
24918 0.2.1.2-alpha. Bugfix by trac user "shitlei".
24919 - Avoid a double mark-for-free warning when failing to attach a
24920 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
24922 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
24923 found by "cypherpunks". This bug was introduced before the first
24924 Tor release, in svn commit r110.
24925 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
24926 don't mention them in the manpage. Fixes bug 2450; issue
24927 spotted by keb and G-Lo.
24928 - Fix a bug in bandwidth history state parsing that could have been
24929 triggered if a future version of Tor ever changed the timing
24930 granularity at which bandwidth history is measured. Bugfix on
24931 Tor 0.1.1.11-alpha.
24932 - When a relay decides that its DNS is too broken for it to serve
24933 as an exit server, it advertised itself as a non-exit, but
24934 continued to act as an exit. This could create accidental
24935 partitioning opportunities for users. Instead, if a relay is
24936 going to advertise reject *:* as its exit policy, it should
24937 really act with exit policy "reject *:*". Fixes bug 2366.
24938 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
24939 - In the special case where you configure a public exit relay as your
24940 bridge, Tor would be willing to use that exit relay as the last
24941 hop in your circuit as well. Now we fail that circuit instead.
24942 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
24943 - Fix a bug with our locking implementation on Windows that couldn't
24944 correctly detect when a file was already locked. Fixes bug 2504,
24945 bugfix on 0.2.1.6-alpha.
24946 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
24947 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
24949 - Set target port in get_interface_address6() correctly. Bugfix
24950 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
24951 - Directory authorities are now more robust to hops back in time
24952 when calculating router stability. Previously, if a run of uptime
24953 or downtime appeared to be negative, the calculation could give
24954 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
24956 - Fix an assert that got triggered when using the TestingTorNetwork
24957 configuration option and then issuing a GETINFO config-text control
24958 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
24960 o Minor bugfixes (on 0.2.2.x):
24961 - Clients should not weight BadExit nodes as Exits in their node
24962 selection. Similarly, directory authorities should not count BadExit
24963 bandwidth as Exit bandwidth when computing bandwidth-weights.
24964 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
24965 - Correctly clear our dir_read/dir_write history when there is an
24966 error parsing any bw history value from the state file. Bugfix on
24967 Tor 0.2.2.15-alpha.
24968 - Resolve a bug in verifying signatures of directory objects
24969 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
24970 Fixes bug 2409. Found by "piebeer".
24971 - Bridge authorities no longer crash on SIGHUP when they try to
24972 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
24976 - Log less aggressively about circuit timeout changes, and improve
24977 some other circuit timeout messages. Resolves bug 2004.
24978 - Log a little more clearly about the times at which we're no longer
24979 accepting new connections. Resolves bug 2181.
24980 - Reject attempts at the client side to open connections to private
24981 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
24982 a randomly chosen exit node. Attempts to do so are always
24983 ill-defined, generally prevented by exit policies, and usually
24984 in error. This will also help to detect loops in transparent
24985 proxy configurations. You can disable this feature by setting
24986 "ClientRejectInternalAddresses 0" in your torrc.
24987 - Always treat failure to allocate an RSA key as an unrecoverable
24989 - Update to the March 1 2011 Maxmind GeoLite Country database.
24991 o Minor features (log subsystem):
24992 - Add documentation for configuring logging at different severities in
24993 different log domains. We've had this feature since 0.2.1.1-alpha,
24994 but for some reason it never made it into the manpage. Fixes
24996 - Make it simpler to specify "All log domains except for A and B".
24997 Previously you needed to say "[*,~A,~B]". Now you can just say
24999 - Add a "LogMessageDomains 1" option to include the domains of log
25000 messages along with the messages. Without this, there's no way
25001 to use log domains without reading the source or doing a lot
25004 o Packaging changes:
25005 - Stop shipping the Tor specs files and development proposal documents
25006 in the tarball. They are now in a separate git repository at
25007 git://git.torproject.org/torspec.git
25010 Changes in version 0.2.1.30 - 2011-02-23
25011 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
25012 change is a slight tweak to Tor's TLS handshake that makes relays
25013 and bridges that run this new version reachable from Iran again.
25014 We don't expect this tweak will win the arms race long-term, but it
25015 buys us time until we roll out a better solution.
25018 - Stop sending a CLOCK_SKEW controller status event whenever
25019 we fetch directory information from a relay that has a wrong clock.
25020 Instead, only inform the controller when it's a trusted authority
25021 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25022 the rest of bug 1074.
25023 - Fix a bounds-checking error that could allow an attacker to
25024 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25025 Found by "piebeer".
25026 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25027 Tor would ignore their RelayBandwidthBurst setting,
25028 potentially using more bandwidth than expected. Bugfix on
25029 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25030 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25031 hidserv" in her torrc. The 'hidserv' argument never controlled
25032 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25035 - Adjust our TLS Diffie-Hellman parameters to match those used by
25037 - Update to the February 1 2011 Maxmind GeoLite Country database.
25040 - Check for and reject overly long directory certificates and
25041 directory tokens before they have a chance to hit any assertions.
25042 Bugfix on 0.2.1.28. Found by "doorss".
25043 - Bring the logic that gathers routerinfos and assesses the
25044 acceptability of circuits into line. This prevents a Tor OP from
25045 getting locked in a cycle of choosing its local OR as an exit for a
25046 path (due to a .exit request) and then rejecting the circuit because
25047 its OR is not listed yet. It also prevents Tor clients from using an
25048 OR running in the same instance as an exit (due to a .exit request)
25049 if the OR does not meet the same requirements expected of an OR
25050 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25052 o Packaging changes:
25053 - Stop shipping the Tor specs files and development proposal documents
25054 in the tarball. They are now in a separate git repository at
25055 git://git.torproject.org/torspec.git
25056 - Do not include Git version tags as though they are SVN tags when
25057 generating a tarball from inside a repository that has switched
25058 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
25061 Changes in version 0.2.2.22-alpha - 2011-01-25
25062 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
25063 main other change is a slight tweak to Tor's TLS handshake that makes
25064 relays and bridges that run this new version reachable from Iran again.
25065 We don't expect this tweak will win the arms race long-term, but it
25066 will buy us a bit more time until we roll out a better solution.
25069 - Fix a bounds-checking error that could allow an attacker to
25070 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25071 Found by "piebeer".
25072 - Don't assert when changing from bridge to relay or vice versa
25073 via the controller. The assert happened because we didn't properly
25074 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
25075 bug 2433. Reported by bastik.
25078 - Adjust our TLS Diffie-Hellman parameters to match those used by
25080 - Provide a log message stating which geoip file we're parsing
25081 instead of just stating that we're parsing the geoip file.
25082 Implements ticket 2432.
25085 - Check for and reject overly long directory certificates and
25086 directory tokens before they have a chance to hit any assertions.
25087 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
25090 Changes in version 0.2.2.21-alpha - 2011-01-15
25091 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
25092 continues our recent code security audit work. The main fix resolves
25093 a remote heap overflow vulnerability that can allow remote code
25094 execution (CVE-2011-0427). Other fixes address a variety of assert
25095 and crash bugs, most of which we think are hard to exploit remotely.
25097 o Major bugfixes (security), also included in 0.2.1.29:
25098 - Fix a heap overflow bug where an adversary could cause heap
25099 corruption. This bug probably allows remote code execution
25100 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
25102 - Prevent a denial-of-service attack by disallowing any
25103 zlib-compressed data whose compression factor is implausibly
25104 high. Fixes part of bug 2324; reported by "doorss".
25105 - Zero out a few more keys in memory before freeing them. Fixes
25106 bug 2384 and part of bug 2385. These key instances found by
25107 "cypherpunks", based on Andrew Case's report about being able
25108 to find sensitive data in Tor's memory space if you have enough
25109 permissions. Bugfix on 0.0.2pre9.
25111 o Major bugfixes (crashes), also included in 0.2.1.29:
25112 - Prevent calls to Libevent from inside Libevent log handlers.
25113 This had potential to cause a nasty set of crashes, especially
25114 if running Libevent with debug logging enabled, and running
25115 Tor with a controller watching for low-severity log messages.
25116 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
25117 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
25118 underflow errors there too. Fixes the other part of bug 2324.
25119 - Fix a bug where we would assert if we ever had a
25120 cached-descriptors.new file (or another file read directly into
25121 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
25122 on 0.2.1.25. Found by doorss.
25123 - Fix some potential asserts and parsing issues with grossly
25124 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
25127 o Minor bugfixes (other), also included in 0.2.1.29:
25128 - Fix a bug with handling misformed replies to reverse DNS lookup
25129 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
25130 bug reported by doorss.
25131 - Fix compilation on mingw when a pthreads compatibility library
25132 has been installed. (We don't want to use it, so we shouldn't
25133 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
25134 - Fix a bug where we would declare that we had run out of virtual
25135 addresses when the address space was only half-exhausted. Bugfix
25137 - Correctly handle the case where AutomapHostsOnResolve is set but
25138 no virtual addresses are available. Fixes bug 2328; bugfix on
25139 0.1.2.1-alpha. Bug found by doorss.
25140 - Correctly handle wrapping around when we run out of virtual
25141 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
25143 o Minor features, also included in 0.2.1.29:
25144 - Update to the January 1 2011 Maxmind GeoLite Country database.
25145 - Introduce output size checks on all of our decryption functions.
25147 o Build changes, also included in 0.2.1.29:
25148 - Tor does not build packages correctly with Automake 1.6 and earlier;
25149 added a check to Makefile.am to make sure that we're building with
25150 Automake 1.7 or later.
25151 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
25152 because we built it with a too-old version of automake. Thus that
25153 release broke ./configure --enable-openbsd-malloc, which is popular
25154 among really fast exit relays on Linux.
25156 o Major bugfixes, new in 0.2.2.21-alpha:
25157 - Prevent crash/heap corruption when the cbtnummodes consensus
25158 parameter is set to 0 or large values. Fixes bug 2317; bugfix
25161 o Major features, new in 0.2.2.21-alpha:
25162 - Introduce minimum/maximum values that clients will believe
25163 from the consensus. Now we'll have a better chance to avoid crashes
25164 or worse when a consensus param has a weird value.
25166 o Minor features, new in 0.2.2.21-alpha:
25167 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
25168 used on bridges, and it makes bridge scanning somewhat easier.
25169 - If writing the state file to disk fails, wait up to an hour before
25170 retrying again, rather than trying again each second. Fixes bug
25171 2346; bugfix on Tor 0.1.1.3-alpha.
25172 - Make Libevent log messages get delivered to controllers later,
25173 and not from inside the Libevent log handler. This prevents unsafe
25174 reentrant Libevent calls while still letting the log messages
25176 - Detect platforms that brokenly use a signed size_t, and refuse to
25177 build there. Found and analyzed by doorss and rransom.
25178 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
25181 o Minor bugfixes, new in 0.2.2.21-alpha:
25182 - Handle SOCKS messages longer than 128 bytes long correctly, rather
25183 than waiting forever for them to finish. Fixes bug 2330; bugfix
25184 on 0.2.0.16-alpha. Found by doorss.
25185 - Add assertions to check for overflow in arguments to
25186 base32_encode() and base32_decode(); fix a signed-unsigned
25187 comparison there too. These bugs are not actually reachable in Tor,
25188 but it's good to prevent future errors too. Found by doorss.
25189 - Correctly detect failures to create DNS requests when using Libevent
25190 versions before v2. (Before Libevent 2, we used our own evdns
25191 implementation. Its return values for Libevent's evdns_resolve_*()
25192 functions are not consistent with those from Libevent.) Fixes bug
25193 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
25195 o Documentation, new in 0.2.2.21-alpha:
25196 - Document the default socks host and port (127.0.0.1:9050) for
25200 Changes in version 0.2.1.29 - 2011-01-15
25201 Tor 0.2.1.29 continues our recent code security audit work. The main
25202 fix resolves a remote heap overflow vulnerability that can allow remote
25203 code execution. Other fixes address a variety of assert and crash bugs,
25204 most of which we think are hard to exploit remotely.
25206 o Major bugfixes (security):
25207 - Fix a heap overflow bug where an adversary could cause heap
25208 corruption. This bug probably allows remote code execution
25209 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
25211 - Prevent a denial-of-service attack by disallowing any
25212 zlib-compressed data whose compression factor is implausibly
25213 high. Fixes part of bug 2324; reported by "doorss".
25214 - Zero out a few more keys in memory before freeing them. Fixes
25215 bug 2384 and part of bug 2385. These key instances found by
25216 "cypherpunks", based on Andrew Case's report about being able
25217 to find sensitive data in Tor's memory space if you have enough
25218 permissions. Bugfix on 0.0.2pre9.
25220 o Major bugfixes (crashes):
25221 - Prevent calls to Libevent from inside Libevent log handlers.
25222 This had potential to cause a nasty set of crashes, especially
25223 if running Libevent with debug logging enabled, and running
25224 Tor with a controller watching for low-severity log messages.
25225 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
25226 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
25227 underflow errors there too. Fixes the other part of bug 2324.
25228 - Fix a bug where we would assert if we ever had a
25229 cached-descriptors.new file (or another file read directly into
25230 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
25231 on 0.2.1.25. Found by doorss.
25232 - Fix some potential asserts and parsing issues with grossly
25233 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
25236 o Minor bugfixes (other):
25237 - Fix a bug with handling misformed replies to reverse DNS lookup
25238 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
25239 bug reported by doorss.
25240 - Fix compilation on mingw when a pthreads compatibility library
25241 has been installed. (We don't want to use it, so we shouldn't
25242 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
25243 - Fix a bug where we would declare that we had run out of virtual
25244 addresses when the address space was only half-exhausted. Bugfix
25246 - Correctly handle the case where AutomapHostsOnResolve is set but
25247 no virtual addresses are available. Fixes bug 2328; bugfix on
25248 0.1.2.1-alpha. Bug found by doorss.
25249 - Correctly handle wrapping around to when we run out of virtual
25250 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
25251 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
25252 because we built it with a too-old version of automake. Thus that
25253 release broke ./configure --enable-openbsd-malloc, which is popular
25254 among really fast exit relays on Linux.
25257 - Update to the January 1 2011 Maxmind GeoLite Country database.
25258 - Introduce output size checks on all of our decryption functions.
25261 - Tor does not build packages correctly with Automake 1.6 and earlier;
25262 added a check to Makefile.am to make sure that we're building with
25263 Automake 1.7 or later.
25266 Changes in version 0.2.2.20-alpha - 2010-12-17
25267 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
25268 exploitable bugs. We also fix a variety of other significant bugs,
25269 change the IP address for one of our directory authorities, and update
25270 the minimum version that Tor relays must run to join the network.
25273 - Fix a remotely exploitable bug that could be used to crash instances
25274 of Tor remotely by overflowing on the heap. Remote-code execution
25275 hasn't been confirmed, but can't be ruled out. Everyone should
25276 upgrade. Bugfix on the 0.1.1 series and later.
25277 - Fix a bug that could break accounting on 64-bit systems with large
25278 time_t values, making them hibernate for impossibly long intervals.
25279 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
25280 - Fix a logic error in directory_fetches_from_authorities() that
25281 would cause all _non_-exits refusing single-hop-like circuits
25282 to fetch from authorities, when we wanted to have _exits_ fetch
25283 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
25285 - Fix a stream fairness bug that would cause newer streams on a given
25286 circuit to get preference when reading bytes from the origin or
25287 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
25288 introduced before the first Tor release, in svn revision r152.
25290 o Directory authority changes:
25291 - Change IP address and ports for gabelmoo (v3 directory authority).
25294 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
25295 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
25296 - Fix an off-by-one error in calculating some controller command
25297 argument lengths. Fortunately, this mistake is harmless since
25298 the controller code does redundant NUL termination too. Found by
25299 boboper. Bugfix on 0.1.1.1-alpha.
25300 - Do not dereference NULL if a bridge fails to build its
25301 extra-info descriptor. Found by an anonymous commenter on
25302 Trac. Bugfix on 0.2.2.19-alpha.
25305 - Update to the December 1 2010 Maxmind GeoLite Country database.
25306 - Directory authorities now reject relays running any versions of
25307 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
25308 known bugs that keep RELAY_EARLY cells from working on rendezvous
25309 circuits. Followup to fix for bug 2081.
25310 - Directory authorities now reject relays running any version of Tor
25311 older than 0.2.0.26-rc. That version is the earliest that fetches
25312 current directory information correctly. Fixes bug 2156.
25313 - Report only the top 10 ports in exit-port stats in order not to
25314 exceed the maximum extra-info descriptor length of 50 KB. Implements
25318 Changes in version 0.2.1.28 - 2010-12-17
25319 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
25320 exploitable bugs. We also took this opportunity to change the IP address
25321 for one of our directory authorities, and to update the geoip database
25325 - Fix a remotely exploitable bug that could be used to crash instances
25326 of Tor remotely by overflowing on the heap. Remote-code execution
25327 hasn't been confirmed, but can't be ruled out. Everyone should
25328 upgrade. Bugfix on the 0.1.1 series and later.
25330 o Directory authority changes:
25331 - Change IP address and ports for gabelmoo (v3 directory authority).
25334 - Update to the December 1 2010 Maxmind GeoLite Country database.
25337 Changes in version 0.2.1.27 - 2010-11-23
25338 Yet another OpenSSL security patch broke its compatibility with Tor:
25339 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
25340 also took this opportunity to fix several crash bugs, integrate a new
25341 directory authority, and update the bundled GeoIP database.
25344 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
25345 No longer set the tlsext_host_name extension on server SSL objects;
25346 but continue to set it on client SSL objects. Our goal in setting
25347 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
25348 bugfix on 0.2.1.1-alpha.
25349 - Do not log messages to the controller while shrinking buffer
25350 freelists. Doing so would sometimes make the controller connection
25351 try to allocate a buffer chunk, which would mess up the internals
25352 of the freelist and cause an assertion failure. Fixes bug 1125;
25353 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
25354 - Learn our external IP address when we're a relay or bridge, even if
25355 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
25356 where we introduced bridge relays that don't need to publish to
25357 be useful. Fixes bug 2050.
25358 - Do even more to reject (and not just ignore) annotations on
25359 router descriptors received anywhere but from the cache. Previously
25360 we would ignore such annotations at first, but cache them to disk
25361 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
25362 - When you're using bridges and your network goes away and your
25363 bridges get marked as down, recover when you attempt a new socks
25364 connection (if the network is back), rather than waiting up to an
25365 hour to try fetching new descriptors for your bridges. Bugfix on
25366 0.2.0.3-alpha; fixes bug 1981.
25369 - Move to the November 2010 Maxmind GeoLite country db (rather
25370 than the June 2009 ip-to-country GeoIP db) for our statistics that
25371 count how many users relays are seeing from each country. Now we'll
25372 have more accurate data, especially for many African countries.
25374 o New directory authorities:
25375 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
25379 - Fix an assertion failure that could occur in directory caches or
25380 bridge users when using a very short voting interval on a testing
25381 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
25383 - Enforce multiplicity rules when parsing annotations. Bugfix on
25384 0.2.0.8-alpha. Found by piebeer.
25385 - Allow handshaking OR connections to take a full KeepalivePeriod
25386 seconds to handshake. Previously, we would close them after
25387 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
25388 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
25390 - When building with --enable-gcc-warnings on OpenBSD, disable
25391 warnings in system headers. This makes --enable-gcc-warnings
25392 pass on OpenBSD 4.8.
25395 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
25396 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
25397 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
25398 Servers can start sending this code when enough clients recognize
25399 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
25400 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
25401 Patch from mingw-san.
25404 - Remove the old debian/ directory from the main Tor distribution.
25405 The official Tor-for-debian git repository lives at the URL
25406 https://git.torproject.org/debian/tor.git
25407 - Stop shipping the old doc/website/ directory in the tarball. We
25408 changed the website format in late 2010, and what we shipped in
25409 0.2.1.26 really wasn't that useful anyway.
25412 Changes in version 0.2.2.19-alpha - 2010-11-22
25413 Yet another OpenSSL security patch broke its compatibility with Tor:
25414 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
25417 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
25418 No longer set the tlsext_host_name extension on server SSL objects;
25419 but continue to set it on client SSL objects. Our goal in setting
25420 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
25421 bugfix on 0.2.1.1-alpha.
25424 - Try harder not to exceed the maximum length of 50 KB when writing
25425 statistics to extra-info descriptors. This bug was triggered by very
25426 fast relays reporting exit-port, entry, and dirreq statistics.
25427 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
25428 - Publish a router descriptor even if generating an extra-info
25429 descriptor fails. Previously we would not publish a router
25430 descriptor without an extra-info descriptor; this can cause fast
25431 exit relays collecting exit-port statistics to drop from the
25432 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
25435 Changes in version 0.2.2.18-alpha - 2010-11-16
25436 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
25437 us lately, makes unpublished bridge relays able to detect their IP
25438 address, and fixes a wide variety of other bugs to get us much closer
25439 to a stable release.
25442 - Do even more to reject (and not just ignore) annotations on
25443 router descriptors received anywhere but from the cache. Previously
25444 we would ignore such annotations at first, but cache them to disk
25445 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
25446 - Do not log messages to the controller while shrinking buffer
25447 freelists. Doing so would sometimes make the controller connection
25448 try to allocate a buffer chunk, which would mess up the internals
25449 of the freelist and cause an assertion failure. Fixes bug 1125;
25450 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
25451 - Learn our external IP address when we're a relay or bridge, even if
25452 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
25453 where we introduced bridge relays that don't need to publish to
25454 be useful. Fixes bug 2050.
25455 - Maintain separate TLS contexts and certificates for incoming and
25456 outgoing connections in bridge relays. Previously we would use the
25457 same TLS contexts and certs for incoming and outgoing connections.
25458 Bugfix on 0.2.0.3-alpha; addresses bug 988.
25459 - Maintain separate identity keys for incoming and outgoing TLS
25460 contexts in bridge relays. Previously we would use the same
25461 identity keys for incoming and outgoing TLS contexts. Bugfix on
25462 0.2.0.3-alpha; addresses the other half of bug 988.
25463 - Avoid an assertion failure when we as an authority receive a
25464 duplicate upload of a router descriptor that we already have,
25465 but which we previously considered an obsolete descriptor.
25466 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
25467 - Avoid a crash bug triggered by looking at a dangling pointer while
25468 setting the network status consensus. Found by Robert Ransom.
25469 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
25470 - Fix a logic error where servers that _didn't_ act as exits would
25471 try to keep their server lists more aggressively up to date than
25472 exits, when it was supposed to be the other way around. Bugfix
25475 o Minor bugfixes (on Tor 0.2.1.x and earlier):
25476 - When we're trying to guess whether we know our IP address as
25477 a relay, we would log various ways that we failed to guess
25478 our address, but never log that we ended up guessing it
25479 successfully. Now add a log line to help confused and anxious
25480 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
25481 - Bring the logic that gathers routerinfos and assesses the
25482 acceptability of circuits into line. This prevents a Tor OP from
25483 getting locked in a cycle of choosing its local OR as an exit for a
25484 path (due to a .exit request) and then rejecting the circuit because
25485 its OR is not listed yet. It also prevents Tor clients from using an
25486 OR running in the same instance as an exit (due to a .exit request)
25487 if the OR does not meet the same requirements expected of an OR
25488 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25489 - Correctly describe errors that occur when generating a TLS object.
25490 Previously we would attribute them to a failure while generating a
25491 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
25493 - Enforce multiplicity rules when parsing annotations. Bugfix on
25494 0.2.0.8-alpha. Found by piebeer.
25495 - Fix warnings that newer versions of autoconf produced during
25496 ./autogen.sh. These warnings appear to be harmless in our case,
25497 but they were extremely verbose. Fixes bug 2020.
25499 o Minor bugfixes (on Tor 0.2.2.x):
25500 - Enable protection of small arrays whenever we build with gcc
25501 hardening features, not only when also building with warnings
25502 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
25505 - Make hidden services work better in private Tor networks by not
25506 requiring any uptime to join the hidden service descriptor
25507 DHT. Implements ticket 2088.
25508 - Rate-limit the "your application is giving Tor only an IP address"
25509 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
25510 - When AllowSingleHopExits is set, print a warning to explain to the
25511 relay operator why most clients are avoiding her relay.
25512 - Update to the November 1 2010 Maxmind GeoLite Country database.
25514 o Code simplifications and refactoring:
25515 - When we fixed bug 1038 we had to put in a restriction not to send
25516 RELAY_EARLY cells on rend circuits. This was necessary as long
25517 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
25518 active. Now remove this obsolete check. Resolves bug 2081.
25519 - Some options used different conventions for uppercasing of acronyms
25520 when comparing manpage and source. Fix those in favor of the
25521 manpage, as it makes sense to capitalize acronyms.
25522 - Remove the torrc.complete file. It hasn't been kept up to date
25523 and users will have better luck checking out the manpage.
25524 - Remove the obsolete "NoPublish" option; it has been flagged
25525 as obsolete and has produced a warning since 0.1.1.18-rc.
25526 - Remove everything related to building the expert bundle for OS X.
25527 It has confused many users, doesn't work right on OS X 10.6,
25528 and is hard to get rid of once installed. Resolves bug 1274.
25531 Changes in version 0.2.2.17-alpha - 2010-09-30
25532 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
25533 to use one-hop circuits (which can put the exit relays at higher risk,
25534 plus unbalance the network); fixes a big bug in bandwidth accounting
25535 for relays that want to limit their monthly bandwidth use; fixes a
25536 big pile of bugs in how clients tolerate temporary network failure;
25537 and makes our adaptive circuit build timeout feature (which improves
25538 client performance if your network is fast while not breaking things
25539 if your network is slow) better handle bad networks.
25542 - Exit relays now try harder to block exit attempts from unknown
25543 relays, to make it harder for people to use them as one-hop proxies
25544 a la tortunnel. Controlled by the refuseunknownexits consensus
25545 parameter (currently enabled), or you can override it on your
25546 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
25548 o Major bugfixes (0.2.1.x and earlier):
25549 - Fix a bug in bandwidth accounting that could make us use twice
25550 the intended bandwidth when our interval start changes due to
25551 daylight saving time. Now we tolerate skew in stored vs computed
25552 interval starts: if the start of the period changes by no more than
25553 50% of the period's duration, we remember bytes that we transferred
25554 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
25555 - Always search the Windows system directory for system DLLs, and
25556 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
25557 - When you're using bridges and your network goes away and your
25558 bridges get marked as down, recover when you attempt a new socks
25559 connection (if the network is back), rather than waiting up to an
25560 hour to try fetching new descriptors for your bridges. Bugfix on
25561 0.2.0.3-alpha; fixes bug 1981.
25563 o Major bugfixes (on 0.2.2.x):
25564 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
25566 - Fix a segfault that could happen when operating a bridge relay with
25567 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
25568 - The consensus bandwidth-weights (used by clients to choose fast
25569 relays) entered an unexpected edge case in September where
25570 Exits were much scarcer than Guards, resulting in bad weight
25571 recommendations. Now we compute them using new constraints that
25572 should succeed in all cases. Also alter directory authorities to
25573 not include the bandwidth-weights line if they fail to produce
25574 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
25575 - When weighting bridges during path selection, we used to trust
25576 the bandwidths they provided in their descriptor, only capping them
25577 at 10MB/s. This turned out to be problematic for two reasons:
25578 Bridges could claim to handle a lot more traffic then they
25579 actually would, thus making more clients pick them and have a
25580 pretty effective DoS attack. The other issue is that new bridges
25581 that might not have a good estimate for their bw capacity yet
25582 would not get used at all unless no other bridges are available
25583 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
25585 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
25586 - Ignore cannibalized circuits when recording circuit build times.
25587 This should provide for a minor performance improvement for hidden
25588 service users using 0.2.2.14-alpha, and should remove two spurious
25589 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
25590 - Simplify the logic that causes us to decide if the network is
25591 unavailable for purposes of recording circuit build times. If we
25592 receive no cells whatsoever for the entire duration of a circuit's
25593 full measured lifetime, the network is probably down. Also ignore
25594 one-hop directory fetching circuit timeouts when calculating our
25595 circuit build times. These changes should hopefully reduce the
25596 cases where we see ridiculous circuit build timeouts for people
25597 with spotty wireless connections. Fixes part of bug 1772; bugfix
25599 - Prevent the circuit build timeout from becoming larger than
25600 the maximum build time we have ever seen. Also, prevent the time
25601 period for measurement circuits from becoming larger than twice that
25602 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
25605 - When we run out of directory information such that we can't build
25606 circuits, but then get enough that we can build circuits, log when
25607 we actually construct a circuit, so the user has a better chance of
25608 knowing what's going on. Fixes bug 1362.
25609 - Be more generous with how much bandwidth we'd use up (with
25610 accounting enabled) before entering "soft hibernation". Previously,
25611 we'd refuse new connections and circuits once we'd used up 95% of
25612 our allotment. Now, we use up 95% of our allotment, AND make sure
25613 that we have no more than 500MB (or 3 hours of expected traffic,
25614 whichever is lower) remaining before we enter soft hibernation.
25615 - If we've configured EntryNodes and our network goes away and/or all
25616 our entrynodes get marked down, optimistically retry them all when
25617 a new socks application request appears. Fixes bug 1882.
25618 - Add some more defensive programming for architectures that can't
25619 handle unaligned integer accesses. We don't know of any actual bugs
25620 right now, but that's the best time to fix them. Fixes bug 1943.
25621 - Support line continuations in the torrc config file. If a line
25622 ends with a single backslash character, the newline is ignored, and
25623 the configuration value is treated as continuing on the next line.
25626 o Minor bugfixes (on 0.2.1.x and earlier):
25627 - For bandwidth accounting, calculate our expected bandwidth rate
25628 based on the time during which we were active and not in
25629 soft-hibernation during the last interval. Previously, we were
25630 also considering the time spent in soft-hibernation. If this
25631 was a long time, we would wind up underestimating our bandwidth
25632 by a lot, and skewing our wakeup time towards the start of the
25633 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
25635 o Minor bugfixes (on 0.2.2.x):
25636 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
25637 which were disabled by the circuit build timeout changes in
25638 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
25639 - Make sure we don't warn about missing bandwidth weights when
25640 choosing bridges or other relays not in the consensus. Bugfix on
25641 0.2.2.10-alpha; fixes bug 1805.
25642 - In our logs, do not double-report signatures from unrecognized
25643 authorities both as "from unknown authority" and "not
25644 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
25647 Changes in version 0.2.2.16-alpha - 2010-09-17
25648 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
25649 evident at exit relays), and also continues to resolve all the little
25650 bugs that have been filling up trac lately.
25652 o Major bugfixes (stream-level fairness):
25653 - When receiving a circuit-level SENDME for a blocked circuit, try
25654 to package cells fairly from all the streams that had previously
25655 been blocked on that circuit. Previously, we had started with the
25656 oldest stream, and allowed each stream to potentially exhaust
25657 the circuit's package window. This gave older streams on any
25658 given circuit priority over newer ones. Fixes bug 1937. Detected
25659 originally by Camilo Viecco. This bug was introduced before the
25660 first Tor release, in svn commit r152: it is the new winner of
25661 the longest-lived bug prize.
25662 - When the exit relay got a circuit-level sendme cell, it started
25663 reading on the exit streams, even if had 500 cells queued in the
25664 circuit queue already, so the circuit queue just grew and grew in
25665 some cases. We fix this by not re-enabling reading on receipt of a
25666 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
25667 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
25669 - Newly created streams were allowed to read cells onto circuits,
25670 even if the circuit's cell queue was blocked and waiting to drain.
25671 This created potential unfairness, as older streams would be
25672 blocked, but newer streams would gladly fill the queue completely.
25673 We add code to detect this situation and prevent any stream from
25674 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
25678 - Update to the September 1 2010 Maxmind GeoLite Country database.
25679 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
25680 not. This would lead to a cookie that is still not group readable.
25681 Closes bug 1843. Suggested by katmagic.
25682 - When logging a rate-limited warning, we now mention how many messages
25683 got suppressed since the last warning.
25684 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
25685 do individual connection-level rate limiting of clients. The torrc
25686 config options with the same names trump the consensus params, if
25687 both are present. Replaces the old "bwconnrate" and "bwconnburst"
25688 consensus params which were broken from 0.2.2.7-alpha through
25689 0.2.2.14-alpha. Closes bug 1947.
25690 - When a router changes IP address or port, authorities now launch
25691 a new reachability test for it. Implements ticket 1899.
25692 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
25693 2 no signature, 4 required" messages about consensus signatures
25694 easier to read, and make sure they get logged at the same severity
25695 as the messages explaining which keys are which. Fixes bug 1290.
25696 - Don't warn when we have a consensus that we can't verify because
25697 of missing certificates, unless those certificates are ones
25698 that we have been trying and failing to download. Fixes bug 1145.
25699 - If you configure your bridge with a known identity fingerprint,
25700 and the bridge authority is unreachable (as it is in at least
25701 one country now), fall back to directly requesting the descriptor
25702 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
25704 - When building with --enable-gcc-warnings on OpenBSD, disable
25705 warnings in system headers. This makes --enable-gcc-warnings
25706 pass on OpenBSD 4.8.
25708 o Minor bugfixes (on 0.2.1.x and earlier):
25709 - Authorities will now attempt to download consensuses if their
25710 own efforts to make a live consensus have failed. This change
25711 means authorities that restart will fetch a valid consensus, and
25712 it means authorities that didn't agree with the current consensus
25713 will still fetch and serve it if it has enough signatures. Bugfix
25714 on 0.2.0.9-alpha; fixes bug 1300.
25715 - Ensure DNS requests launched by "RESOLVE" commands from the
25716 controller respect the __LeaveStreamsUnattached setconf options. The
25717 same goes for requests launched via DNSPort or transparent
25718 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
25719 - Allow handshaking OR connections to take a full KeepalivePeriod
25720 seconds to handshake. Previously, we would close them after
25721 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
25722 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
25724 - Rate-limit "Failed to hand off onionskin" warnings.
25725 - Never relay a cell for a circuit we have already destroyed.
25726 Between marking a circuit as closeable and finally closing it,
25727 it may have been possible for a few queued cells to get relayed,
25728 even though they would have been immediately dropped by the next
25729 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
25730 - Never queue a cell for a circuit that's already been marked
25732 - Never vote for a server as "Running" if we have a descriptor for
25733 it claiming to be hibernating, and that descriptor was published
25734 more recently than our last contact with the server. Bugfix on
25735 0.2.0.3-alpha; fixes bug 911.
25736 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
25739 o Minor bugfixes (on 0.2.2.x):
25740 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
25741 down if a directory fetch fails and you've configured either
25742 bridges or EntryNodes. The intent was to mark the relay as down
25743 _unless_ you're using bridges or EntryNodes, since if you are
25744 then you could quickly run out of entry points.
25745 - Fix the Windows directory-listing code. A bug introduced in
25746 0.2.2.14-alpha could make Windows directory servers forget to load
25747 some of their cached v2 networkstatus files.
25748 - Really allow clients to use relays as bridges. Fixes bug 1776;
25749 bugfix on 0.2.2.15-alpha.
25750 - Demote a warn to info that happens when the CellStatistics option
25751 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
25752 Reported by Moritz Bartl.
25753 - On Windows, build correctly either with or without Unicode support.
25754 This is necessary so that Tor can support fringe platforms like
25755 Windows 98 (which has no Unicode), or Windows CE (which has no
25756 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
25759 - Add a unit test for cross-platform directory-listing code.
25762 Changes in version 0.2.2.15-alpha - 2010-08-18
25763 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
25764 fixes a variety of other bugs that were preventing performance
25765 experiments from moving forward, fixes several bothersome memory leaks,
25766 and generally closes a lot of smaller bugs that have been filling up
25770 - Stop assigning the HSDir flag to relays that disable their
25771 DirPort (and thus will refuse to answer directory requests). This
25772 fix should dramatically improve the reachability of hidden services:
25773 hidden services and hidden service clients pick six HSDir relays
25774 to store and retrieve the hidden service descriptor, and currently
25775 about half of the HSDir relays will refuse to work. Bugfix on
25776 0.2.0.10-alpha; fixes part of bug 1693.
25777 - The PerConnBWRate and Burst config options, along with the
25778 bwconnrate and bwconnburst consensus params, initialized each conn's
25779 token bucket values only when the connection is established. Now we
25780 update them if the config options change, and update them every time
25781 we get a new consensus. Otherwise we can encounter an ugly edge
25782 case where we initialize an OR conn to client-level bandwidth,
25783 but then later the relay joins the consensus and we leave it
25784 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
25785 - Fix a regression that caused Tor to rebind its ports if it receives
25786 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
25789 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
25790 should give us approximately 40-50% more Guard-flagged nodes,
25791 improving the anonymity the Tor network can provide and also
25792 decreasing the dropoff in throughput that relays experience when
25793 they first get the Guard flag.
25794 - Allow enabling or disabling the *Statistics config options while
25798 - Update to the August 1 2010 Maxmind GeoLite Country database.
25799 - Have the controller interface give a more useful message than
25800 "Internal Error" in response to failed GETINFO requests.
25801 - Warn when the same option is provided more than once in a torrc
25802 file, on the command line, or in a single SETCONF statement, and
25803 the option is one that only accepts a single line. Closes bug 1384.
25804 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
25805 Patch from mingw-san.
25806 - Add support for the country code "{??}" in torrc options like
25807 ExcludeNodes, to indicate all routers of unknown country. Closes
25809 - Relays report the number of bytes spent on answering directory
25810 requests in extra-info descriptors similar to {read,write}-history.
25811 Implements enhancement 1790.
25813 o Minor bugfixes (on 0.2.1.x and earlier):
25814 - Complain if PublishServerDescriptor is given multiple arguments that
25815 include 0 or 1. This configuration will be rejected in the future.
25816 Bugfix on 0.2.0.1-alpha; closes bug 1107.
25817 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
25818 Bugfix on 0.2.0.13-alpha; closes bug 928.
25819 - Change "Application request when we're believed to be offline."
25820 notice to "Application request when we haven't used client
25821 functionality lately.", to clarify that it's not an error. Bugfix
25822 on 0.0.9.3; fixes bug 1222.
25823 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
25824 would return "551 Internal error" rather than "552 Unrecognized key
25825 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
25826 - Users can't configure a regular relay to be their bridge. It didn't
25827 work because when Tor fetched the bridge descriptor, it found
25828 that it already had it, and didn't realize that the purpose of the
25829 descriptor had changed. Now we replace routers with a purpose other
25830 than bridge with bridge descriptors when fetching them. Bugfix on
25831 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
25832 refetch the descriptor with router purpose 'general', disabling
25834 - Fix a rare bug in rend_fn unit tests: we would fail a test when
25835 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
25836 on 0.2.0.10-alpha; fixes bug 1808.
25837 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
25838 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
25839 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
25840 Servers can start sending this code when enough clients recognize
25841 it. Also update the spec to reflect this new reason. Bugfix on
25842 0.1.0.1-rc; fixes part of bug 1793.
25843 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
25844 when we switch from being a public relay to a bridge. Otherwise
25845 there will still be clients that see the relay in their consensus,
25846 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
25848 - Instead of giving an assertion failure on an internal mismatch
25849 on estimated freelist size, just log a BUG warning and try later.
25850 Mitigates but does not fix bug 1125.
25851 - Fix an assertion failure that could occur in caches or bridge users
25852 when using a very short voting interval on a testing network.
25853 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
25855 o Minor bugfixes (on 0.2.2.x):
25856 - Alter directory authorities to always consider Exit-flagged nodes
25857 as potential Guard nodes in their votes. The actual decision to
25858 use Exits as Guards is done in the consensus bandwidth weights.
25859 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
25860 - When the controller is reporting the purpose of circuits that
25861 didn't finish building before the circuit build timeout, it was
25862 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
25863 - Our libevent version parsing code couldn't handle versions like
25864 1.4.14b-stable and incorrectly warned the user about using an
25865 old and broken version of libevent. Treat 1.4.14b-stable like
25866 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
25868 - Don't use substitution references like $(VAR:MOD) when
25869 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
25870 '$(:x)' to 'x' rather than the empty string. This bites us in
25871 doc/ when configured with --disable-asciidoc. Bugfix on
25872 0.2.2.9-alpha; fixes bug 1773.
25873 - Remove a spurious hidden service server-side log notice about
25874 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
25876 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
25878 - Correctly report written bytes on linked connections. Found while
25879 implementing 1790. Bugfix on 0.2.2.4-alpha.
25880 - Fix three memory leaks: one in circuit_build_times_parse_state(),
25881 one in dirvote_add_signatures_to_pending_consensus(), and one every
25882 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
25883 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
25885 o Code simplifications and refactoring:
25886 - Take a first step towards making or.h smaller by splitting out
25887 function definitions for all source files in src/or/. Leave
25888 structures and defines in or.h for now.
25889 - Remove a bunch of unused function declarations as well as a block of
25890 #if 0'd code from the unit tests. Closes bug 1824.
25891 - New unit tests for exit-port history statistics; refactored exit
25892 statistics code to be more easily tested.
25893 - Remove the old debian/ directory from the main Tor distribution.
25894 The official Tor-for-debian git repository lives at the URL
25895 https://git.torproject.org/debian/tor.git
25898 Changes in version 0.2.2.14-alpha - 2010-07-12
25899 Tor 0.2.2.14-alpha greatly improves client-side handling of
25900 circuit build timeouts, which are used to estimate speed and improve
25901 performance. We also move to a much better GeoIP database, port Tor to
25902 Windows CE, introduce new compile flags that improve code security,
25903 add an eighth v3 directory authority, and address a lot of more
25907 - Tor directory authorities no longer crash when started with a
25908 cached-microdesc-consensus file in their data directory. Bugfix
25909 on 0.2.2.6-alpha; fixes bug 1532.
25910 - Treat an unset $HOME like an empty $HOME rather than triggering an
25911 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
25912 - Ignore negative and large circuit build timeout values that can
25913 happen during a suspend or hibernate. These values caused various
25914 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
25915 - Alter calculation of Pareto distribution parameter 'Xm' for
25916 Circuit Build Timeout learning to use the weighted average of the
25917 top N=3 modes (because we have three entry guards). Considering
25918 multiple modes should improve the timeout calculation in some cases,
25919 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
25921 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
25922 right censored distribution model. This approach improves over the
25923 synthetic timeout generation approach that was producing insanely
25924 high timeout values. Now we calculate build timeouts using truncated
25925 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
25926 - Do not close circuits that are under construction when they reach
25927 the circuit build timeout. Instead, leave them building (but do not
25928 use them) for up until the time corresponding to the 95th percentile
25929 on the Pareto CDF or 60 seconds, whichever is greater. This is done
25930 to provide better data for the new Pareto model. This percentile
25931 can be controlled by the consensus.
25934 - Move to the June 2010 Maxmind GeoLite country db (rather than the
25935 June 2009 ip-to-country GeoIP db) for our statistics that count
25936 how many users relays are seeing from each country. Now we have
25937 more accurate data for many African countries.
25938 - Port Tor to build and run correctly on Windows CE systems, using
25939 the wcecompat library. Contributed by Valerio Lupi.
25940 - New "--enable-gcc-hardening" ./configure flag (off by default)
25941 to turn on gcc compile time hardening options. It ensures
25942 that signed ints have defined behavior (-fwrapv), enables
25943 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
25944 with canaries (-fstack-protector-all), turns on ASLR protection if
25945 supported by the kernel (-fPIE, -pie), and adds additional security
25946 related warnings. Verified to work on Mac OS X and Debian Lenny.
25947 - New "--enable-linker-hardening" ./configure flag (off by default)
25948 to turn on ELF specific hardening features (relro, now). This does
25949 not work with Mac OS X or any other non-ELF binary format.
25951 o New directory authorities:
25952 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
25956 - New config option "WarnUnsafeSocks 0" disables the warning that
25957 occurs whenever Tor receives a socks handshake using a version of
25958 the socks protocol that can only provide an IP address (rather
25959 than a hostname). Setups that do DNS locally over Tor are fine,
25960 and we shouldn't spam the logs in that case.
25961 - Convert the HACKING file to asciidoc, and add a few new sections
25962 to it, explaining how we use Git, how we make changelogs, and
25963 what should go in a patch.
25964 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
25965 event, to give information on the current rate of circuit timeouts
25966 over our stored history.
25967 - Add ability to disable circuit build time learning via consensus
25968 parameter and via a LearnCircuitBuildTimeout config option. Also
25969 automatically disable circuit build time calculation if we are
25970 either a AuthoritativeDirectory, or if we fail to write our state
25971 file. Fixes bug 1296.
25972 - More gracefully handle corrupt state files, removing asserts
25973 in favor of saving a backup and resetting state.
25974 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
25978 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
25980 - When a2x fails, mention that the user could disable manpages instead
25981 of trying to fix their asciidoc installation.
25982 - Where available, use Libevent 2.0's periodic timers so that our
25983 once-per-second cleanup code gets called even more closely to
25984 once per second than it would otherwise. Fixes bug 943.
25985 - If you run a bridge that listens on multiple IP addresses, and
25986 some user configures a bridge address that uses a different IP
25987 address than your bridge writes in its router descriptor, and the
25988 user doesn't specify an identity key, their Tor would discard the
25989 descriptor because "it isn't one of our configured bridges", and
25990 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
25991 Bugfix on 0.2.0.3-alpha.
25992 - If OpenSSL fails to make a duplicate of a private or public key, log
25993 an error message and try to exit cleanly. May help with debugging
25994 if bug 1209 ever remanifests.
25995 - Save a couple bytes in memory allocation every time we escape
25996 certain characters in a string. Patch from Florian Zumbiehl.
25997 - Make it explicit that we don't cannibalize one-hop circuits. This
25998 happens in the wild, but doesn't turn out to be a problem because
25999 we fortunately don't use those circuits. Many thanks to outofwords
26000 for the initial analysis and to swissknife who confirmed that
26001 two-hop circuits are actually created.
26002 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
26003 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
26004 - Eliminate a case where a circuit build time warning was displayed
26005 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
26008 Changes in version 0.2.1.26 - 2010-05-02
26009 Tor 0.2.1.26 addresses the recent connection and memory overload
26010 problems we've been seeing on relays, especially relays with their
26011 DirPort open. If your relay has been crashing, or you turned it off
26012 because it used too many resources, give this release a try.
26014 This release also fixes yet another instance of broken OpenSSL libraries
26015 that was causing some relays to drop out of the consensus.
26018 - Teach relays to defend themselves from connection overload. Relays
26019 now close idle circuits early if it looks like they were intended
26020 for directory fetches. Relays are also more aggressive about closing
26021 TLS connections that have no circuits on them. Such circuits are
26022 unlikely to be re-used, and tens of thousands of them were piling
26023 up at the fast relays, causing the relays to run out of sockets
26024 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26025 their directory fetches over TLS).
26026 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26027 that claim to be earlier than 0.9.8m, but which have in reality
26028 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26029 behavior. Possible fix for some cases of bug 1346.
26030 - Directory mirrors were fetching relay descriptors only from v2
26031 directory authorities, rather than v3 authorities like they should.
26032 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26033 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26036 - Finally get rid of the deprecated and now harmful notion of "clique
26037 mode", where directory authorities maintain TLS connections to
26041 - In the util/threads test, no longer free the test_mutex before all
26042 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26043 - The master thread could starve the worker threads quite badly on
26044 certain systems, causing them to run only partially in the allowed
26045 window. This resulted in test failures. Now the master thread sleeps
26046 occasionally for a few microseconds while the two worker-threads
26047 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26050 Changes in version 0.2.2.13-alpha - 2010-04-24
26051 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
26052 problems we've been seeing on relays, especially relays with their
26053 DirPort open. If your relay has been crashing, or you turned it off
26054 because it used too many resources, give this release a try.
26057 - Teach relays to defend themselves from connection overload. Relays
26058 now close idle circuits early if it looks like they were intended
26059 for directory fetches. Relays are also more aggressive about closing
26060 TLS connections that have no circuits on them. Such circuits are
26061 unlikely to be re-used, and tens of thousands of them were piling
26062 up at the fast relays, causing the relays to run out of sockets
26063 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26064 their directory fetches over TLS).
26067 - Finally get rid of the deprecated and now harmful notion of "clique
26068 mode", where directory authorities maintain TLS connections to
26070 - Directory authorities now do an immediate reachability check as soon
26071 as they hear about a new relay. This change should slightly reduce
26072 the time between setting up a relay and getting listed as running
26073 in the consensus. It should also improve the time between setting
26074 up a bridge and seeing use by bridge users.
26075 - Directory authorities no longer launch a TLS connection to every
26076 relay as they startup. Now that we have 2k+ descriptors cached,
26077 the resulting network hiccup is becoming a burden. Besides,
26078 authorities already avoid voting about Running for the first half
26079 hour of their uptime.
26082 Changes in version 0.2.2.12-alpha - 2010-04-20
26083 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
26084 handle and vote on descriptors. It was causing relays to drop out of
26088 - Many relays have been falling out of the consensus lately because
26089 not enough authorities know about their descriptor for them to get
26090 a majority of votes. When we deprecated the v2 directory protocol,
26091 we got rid of the only way that v3 authorities can hear from each
26092 other about other descriptors. Now authorities examine every v3
26093 vote for new descriptors, and fetch them from that authority. Bugfix
26095 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
26096 and a warning in or.h related to bandwidth_weight_rule_t that
26097 prevented clean compile on OS X. Fixes bug 1363; bugfix on
26099 - Fix a segfault on relays when DirReqStatistics is enabled
26100 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
26104 - Demote a confusing TLS warning that relay operators might get when
26105 someone tries to talk to their OrPort. It is neither the operator's
26106 fault nor can they do anything about it. Fixes bug 1364; bugfix
26110 Changes in version 0.2.2.11-alpha - 2010-04-15
26111 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
26112 libraries that was causing some relays to drop out of the consensus.
26115 - Directory mirrors were fetching relay descriptors only from v2
26116 directory authorities, rather than v3 authorities like they should.
26117 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26118 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26119 - Fix a parsing error that made every possible value of
26120 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
26121 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
26122 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
26123 about the option without breaking older ones.
26124 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26125 that claim to be earlier than 0.9.8m, but which have in reality
26126 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26127 behavior. Possible fix for some cases of bug 1346.
26130 - Experiment with a more aggressive approach to preventing clients
26131 from making one-hop exit streams. Exit relays who want to try it
26132 out can set "RefuseUnknownExits 1" in their torrc, and then look
26133 for "Attempt by %s to open a stream" log messages. Let us know
26135 - Add support for statically linking zlib by specifying
26136 --enable-static-zlib, to go with our support for statically linking
26137 openssl and libevent. Resolves bug 1358.
26140 - Fix a segfault that happens whenever a Tor client that is using
26141 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
26143 - When we cleaned up the contrib/tor-exit-notice.html file, we left
26144 out the first line. Fixes bug 1295.
26145 - When building the manpage from a tarball, we required asciidoc, but
26146 the asciidoc -> roff/html conversion was already done for the
26147 tarball. Make 'make' complain only when we need asciidoc (either
26148 because we're compiling directly from git, or because we altered
26149 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
26150 - When none of the directory authorities vote on any params, Tor
26151 segfaulted when trying to make the consensus from the votes. We
26152 didn't trigger the bug in practice, because authorities do include
26153 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
26156 - In the util/threads test, no longer free the test_mutex before all
26157 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26158 - The master thread could starve the worker threads quite badly on
26159 certain systems, causing them to run only partially in the allowed
26160 window. This resulted in test failures. Now the master thread sleeps
26161 occasionally for a few microseconds while the two worker-threads
26162 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26165 Changes in version 0.2.2.10-alpha - 2010-03-07
26166 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
26167 could prevent relays from guessing their IP address correctly. It also
26168 starts the groundwork for another client-side performance boost, since
26169 currently we're not making efficient use of relays that have both the
26170 Guard flag and the Exit flag.
26173 - Fix a regression from our patch for bug 1244 that caused relays
26174 to guess their IP address incorrectly if they didn't set Address
26175 in their torrc and/or their address fails to resolve. Bugfix on
26176 0.2.2.9-alpha; fixes bug 1269.
26178 o Major features (performance):
26179 - Directory authorities now compute consensus weightings that instruct
26180 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
26181 and no flag. Clients that use these weightings will distribute
26182 network load more evenly across these different relay types. The
26183 weightings are in the consensus so we can change them globally in
26184 the future. Extra thanks to "outofwords" for finding some nasty
26185 security bugs in the first implementation of this feature.
26187 o Minor features (performance):
26188 - Always perform router selections using weighted relay bandwidth,
26189 even if we don't need a high capacity circuit at the time. Non-fast
26190 circuits now only differ from fast ones in that they can use relays
26191 not marked with the Fast flag. This "feature" could turn out to
26192 be a horrible bug; we should investigate more before it goes into
26196 - Allow disabling building of the manpages. Skipping the manpage
26197 speeds up the build considerably.
26199 o Minor bugfixes (on 0.2.2.x):
26200 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
26201 Bugfix on 0.2.2.9-alpha.
26202 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
26203 config option. Bugfix on 0.2.2.7-alpha.
26204 - Ship the asciidoc-helper file in the tarball, so that people can
26205 build from source if they want to, and touching the .1.txt files
26206 doesn't break the build. Bugfix on 0.2.2.9-alpha.
26208 o Minor bugfixes (on 0.2.1.x or earlier):
26209 - Fix a dereference-then-NULL-check sequence when publishing
26210 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
26212 - Fix another dereference-then-NULL-check sequence. Bugfix on
26213 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
26214 - Make sure we treat potentially not NUL-terminated strings correctly.
26215 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
26217 o Code simplifications and refactoring:
26218 - Fix some urls in the exit notice file and make it XHTML1.1 strict
26219 compliant. Based on a patch from Christian Kujau.
26220 - Don't use sed in asciidoc-helper anymore.
26221 - Make the build process fail if asciidoc cannot be found and
26222 building with asciidoc isn't disabled.
26225 Changes in version 0.2.2.9-alpha - 2010-02-22
26226 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
26227 location of a directory authority, and cleans up a bunch of small bugs.
26229 o Directory authority changes:
26230 - Change IP address for dannenberg (v3 directory authority), and
26231 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
26232 service directory authority) from the list.
26235 - Make Tor work again on the latest OS X: when deciding whether to
26236 use strange flags to turn TLS renegotiation on, detect the OpenSSL
26237 version at run-time, not compile time. We need to do this because
26238 Apple doesn't update its dev-tools headers when it updates its
26239 libraries in a security patch.
26240 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
26241 that could happen on 32-bit platforms with 64-bit time_t. Also fix
26242 a memory leak when requesting a hidden service descriptor we've
26243 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
26245 - Authorities could be tricked into giving out the Exit flag to relays
26246 that didn't allow exiting to any ports. This bug could screw
26247 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
26248 1238. Bug discovered by Martin Kowalczyk.
26249 - When freeing a session key, zero it out completely. We only zeroed
26250 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
26251 patched by ekir. Fixes bug 1254.
26254 - Fix static compilation by listing the openssl libraries in the right
26255 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
26256 - Resume handling .exit hostnames in a special way: originally we
26257 stripped the .exit part and used the requested exit relay. In
26258 0.2.2.1-alpha we stopped treating them in any special way, meaning
26259 if you use a .exit address then Tor will pass it on to the exit
26260 relay. Now we reject the .exit stream outright, since that behavior
26261 might be more expected by the user. Found and diagnosed by Scott
26262 Bennett and Downie on or-talk.
26263 - Don't spam the controller with events when we have no file
26264 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
26265 for log messages was already solved from bug 748.)
26266 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
26268 - Make the DNSPort option work with libevent 2.x. Don't alter the
26269 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
26270 - Emit a GUARD DROPPED controller event for a case we missed.
26271 - Make more fields in the controller protocol case-insensitive, since
26272 control-spec.txt said they were.
26273 - Refactor resolve_my_address() to not use gethostbyname() anymore.
26274 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
26275 - Fix a spec conformance issue: the network-status-version token
26276 must be the first token in a v3 consensus or vote. Discovered by
26277 parakeep. Bugfix on 0.2.0.3-alpha.
26279 o Code simplifications and refactoring:
26280 - Generate our manpage and HTML documentation using Asciidoc. This
26281 change should make it easier to maintain the documentation, and
26282 produce nicer HTML.
26283 - Remove the --enable-iphone option. According to reports from Marco
26284 Bonetti, Tor builds fine without any special tweaking on recent
26285 iPhone SDK versions.
26286 - Removed some unnecessary files from the source distribution. The
26287 AUTHORS file has now been merged into the people page on the
26288 website. The roadmaps and design doc can now be found in the
26289 projects directory in svn.
26290 - Enabled various circuit build timeout constants to be controlled
26291 by consensus parameters. Also set better defaults for these
26292 parameters based on experimentation on broadband and simulated
26293 high latency links.
26296 - The 'EXTENDCIRCUIT' control port command can now be used with
26297 a circ id of 0 and no path. This feature will cause Tor to build
26298 a new 'fast' general purpose circuit using its own path selection
26300 - Added a BUILDTIMEOUT_SET controller event to describe changes
26301 to the circuit build timeout.
26302 - Future-proof the controller protocol a bit by ignoring keyword
26303 arguments we do not recognize.
26304 - Expand homedirs passed to tor-checkkey. This should silence a
26305 coverity complaint about passing a user-supplied string into
26306 open() without checking it.
26309 Changes in version 0.2.1.25 - 2010-03-16
26310 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
26311 prevent relays from guessing their IP address correctly. It also fixes
26312 several minor potential security bugs.
26315 - Fix a regression from our patch for bug 1244 that caused relays
26316 to guess their IP address incorrectly if they didn't set Address
26317 in their torrc and/or their address fails to resolve. Bugfix on
26318 0.2.1.23; fixes bug 1269.
26319 - When freeing a session key, zero it out completely. We only zeroed
26320 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
26321 patched by ekir. Fixes bug 1254.
26324 - Fix a dereference-then-NULL-check sequence when publishing
26325 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
26327 - Fix another dereference-then-NULL-check sequence. Bugfix on
26328 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
26329 - Make sure we treat potentially not NUL-terminated strings correctly.
26330 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
26334 Changes in version 0.2.1.24 - 2010-02-21
26335 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
26339 - Work correctly out-of-the-box with even more vendor-patched versions
26340 of OpenSSL. In particular, make it so Debian and OS X don't need
26341 customized patches to run/build.
26344 Changes in version 0.2.1.23 - 2010-02-13
26345 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
26346 again on the latest OS X, and updates the location of a directory
26349 o Major bugfixes (performance):
26350 - We were selecting our guards uniformly at random, and then weighting
26351 which of our guards we'd use uniformly at random. This imbalance
26352 meant that Tor clients were severely limited on throughput (and
26353 probably latency too) by the first hop in their circuit. Now we
26354 select guards weighted by currently advertised bandwidth. We also
26355 automatically discard guards picked using the old algorithm. Fixes
26356 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
26359 - Make Tor work again on the latest OS X: when deciding whether to
26360 use strange flags to turn TLS renegotiation on, detect the OpenSSL
26361 version at run-time, not compile time. We need to do this because
26362 Apple doesn't update its dev-tools headers when it updates its
26363 libraries in a security patch.
26364 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
26365 that could happen on 32-bit platforms with 64-bit time_t. Also fix
26366 a memory leak when requesting a hidden service descriptor we've
26367 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
26370 o Directory authority changes:
26371 - Change IP address for dannenberg (v3 directory authority), and
26372 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
26373 service directory authority) from the list.
26376 - Refactor resolve_my_address() to not use gethostbyname() anymore.
26377 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
26380 - Avoid a mad rush at the beginning of each month when each client
26381 rotates half of its guards. Instead we spread the rotation out
26382 throughout the month, but we still avoid leaving a precise timestamp
26383 in the state file about when we first picked the guard. Improves
26384 over the behavior introduced in 0.1.2.17.
26387 Changes in version 0.2.2.8-alpha - 2010-01-26
26388 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
26389 causing bridge relays to disappear. If you're running a bridge,
26393 - Fix a memory corruption bug on bridges that occurred during the
26394 inclusion of stats data in extra-info descriptors. Also fix the
26395 interface for geoip_get_bridge_stats* to prevent similar bugs in
26396 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
26397 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
26400 - Ignore OutboundBindAddress when connecting to localhost.
26401 Connections to localhost need to come _from_ localhost, or else
26402 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
26406 Changes in version 0.2.2.7-alpha - 2010-01-19
26407 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
26408 as laying the groundwork for further relay-side performance fixes. It
26409 also starts cleaning up client behavior with respect to the EntryNodes,
26410 ExitNodes, and StrictNodes config options.
26412 This release also rotates two directory authority keys, due to a
26413 security breach of some of the Torproject servers.
26415 o Directory authority changes:
26416 - Rotate keys (both v3 identity and relay identity) for moria1
26419 o Major features (performance):
26420 - We were selecting our guards uniformly at random, and then weighting
26421 which of our guards we'd use uniformly at random. This imbalance
26422 meant that Tor clients were severely limited on throughput (and
26423 probably latency too) by the first hop in their circuit. Now we
26424 select guards weighted by currently advertised bandwidth. We also
26425 automatically discard guards picked using the old algorithm. Fixes
26426 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
26427 - When choosing which cells to relay first, relays can now favor
26428 circuits that have been quiet recently, to provide lower latency
26429 for low-volume circuits. By default, relays enable or disable this
26430 feature based on a setting in the consensus. You can override
26431 this default by using the new "CircuitPriorityHalflife" config
26432 option. Design and code by Ian Goldberg, Can Tang, and Chris
26434 - Add separate per-conn write limiting to go with the per-conn read
26435 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
26436 but never per-conn write limits.
26437 - New consensus params "bwconnrate" and "bwconnburst" to let us
26438 rate-limit client connections as they enter the network. It's
26439 controlled in the consensus so we can turn it on and off for
26440 experiments. It's starting out off. Based on proposal 163.
26442 o Major features (relay selection options):
26443 - Switch to a StrictNodes config option, rather than the previous
26444 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
26445 "StrictExcludeNodes" option.
26446 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
26447 change during a config reload, mark and discard all our origin
26448 circuits. This fix should address edge cases where we change the
26449 config options and but then choose a circuit that we created before
26451 - If EntryNodes or ExitNodes are set, be more willing to use an
26452 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
26454 - Make EntryNodes config option much more aggressive even when
26455 StrictNodes is not set. Before it would prepend your requested
26456 entrynodes to your list of guard nodes, but feel free to use others
26457 after that. Now it chooses only from your EntryNodes if any of
26458 those are available, and only falls back to others if a) they're
26459 all down and b) StrictNodes is not set.
26460 - Now we refresh your entry guards from EntryNodes at each consensus
26461 fetch -- rather than just at startup and then they slowly rot as
26462 the network changes.
26465 - Stop bridge directory authorities from answering dbg-stability.txt
26466 directory queries, which would let people fetch a list of all
26467 bridge identities they track. Bugfix on 0.2.1.6-alpha.
26470 - Log a notice when we get a new control connection. Now it's easier
26471 for security-conscious users to recognize when a local application
26472 is knocking on their controller door. Suggested by bug 1196.
26473 - New config option "CircuitStreamTimeout" to override our internal
26474 timeout schedule for how many seconds until we detach a stream from
26475 a circuit and try a new circuit. If your network is particularly
26476 slow, you might want to set this to a number like 60.
26477 - New controller command "getinfo config-text". It returns the
26478 contents that Tor would write if you send it a SAVECONF command,
26479 so the controller can write the file to disk itself.
26480 - New options for SafeLogging to allow scrubbing only log messages
26481 generated while acting as a relay.
26482 - Ship the bridges spec file in the tarball too.
26483 - Avoid a mad rush at the beginning of each month when each client
26484 rotates half of its guards. Instead we spread the rotation out
26485 throughout the month, but we still avoid leaving a precise timestamp
26486 in the state file about when we first picked the guard. Improves
26487 over the behavior introduced in 0.1.2.17.
26489 o Minor bugfixes (compiling):
26490 - Fix compilation on OS X 10.3, which has a stub mlockall() but
26491 hides it. Bugfix on 0.2.2.6-alpha.
26492 - Fix compilation on Solaris by removing support for the
26493 DisableAllSwap config option. Solaris doesn't have an rlimit for
26494 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
26497 o Minor bugfixes (crashes):
26498 - Do not segfault when writing buffer stats when we haven't observed
26499 a single circuit to report about. Found by Fabian Lanze. Bugfix on
26501 - If we're in the pathological case where there's no exit bandwidth
26502 but there is non-exit bandwidth, or no guard bandwidth but there
26503 is non-guard bandwidth, don't crash during path selection. Bugfix
26505 - Fix an impossible-to-actually-trigger buffer overflow in relay
26506 descriptor generation. Bugfix on 0.1.0.15.
26508 o Minor bugfixes (privacy):
26509 - Fix an instance where a Tor directory mirror might accidentally
26510 log the IP address of a misbehaving Tor client. Bugfix on
26512 - Don't list Windows capabilities in relay descriptors. We never made
26513 use of them, and maybe it's a bad idea to publish them. Bugfix
26516 o Minor bugfixes (other):
26517 - Resolve an edge case in path weighting that could make us misweight
26518 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
26519 - Fix statistics on client numbers by country as seen by bridges that
26520 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
26521 intervals instead of variable 12-to-48-hour intervals.
26522 - After we free an internal connection structure, overwrite it
26523 with a different memory value than we use for overwriting a freed
26524 internal circuit structure. Should help with debugging. Suggested
26526 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
26529 o Removed features:
26530 - Remove the HSAuthorityRecordStats option that version 0 hidden
26531 service authorities could have used to track statistics of overall
26532 hidden service usage.
26535 Changes in version 0.2.1.22 - 2010-01-19
26536 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
26537 authorities -- it would tell you its whole history of bridge descriptors
26538 if you make the right directory request. This stable update also
26539 rotates two of the seven v3 directory authority keys and locations.
26541 o Directory authority changes:
26542 - Rotate keys (both v3 identity and relay identity) for moria1
26546 - Stop bridge directory authorities from answering dbg-stability.txt
26547 directory queries, which would let people fetch a list of all
26548 bridge identities they track. Bugfix on 0.2.1.6-alpha.
26551 Changes in version 0.2.1.21 - 2009-12-21
26552 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
26553 library. If you use Tor on Linux / Unix and you're getting SSL
26554 renegotiation errors, upgrading should help. We also recommend an
26555 upgrade if you're an exit relay.
26558 - Work around a security feature in OpenSSL 0.9.8l that prevents our
26559 handshake from working unless we explicitly tell OpenSSL that we
26560 are using SSL renegotiation safely. We are, of course, but OpenSSL
26561 0.9.8l won't work unless we say we are.
26562 - Avoid crashing if the client is trying to upload many bytes and the
26563 circuit gets torn down at the same time, or if the flip side
26564 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
26567 - Do not refuse to learn about authority certs and v2 networkstatus
26568 documents that are older than the latest consensus. This bug might
26569 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
26570 Spotted and fixed by xmux.
26571 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
26572 trigger platform-specific option misparsing case found by Coverity
26574 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
26575 trigger assert. Fixes bug 1173.
26578 Changes in version 0.2.2.6-alpha - 2009-11-19
26579 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
26580 support for the new lower-footprint "microdescriptor" directory design,
26581 future-proofing our consensus format against new hash functions or
26582 other changes, and an Android port. It also makes Tor compatible with
26583 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
26586 - Directory authorities can now create, vote on, and serve multiple
26587 parallel formats of directory data as part of their voting process.
26588 Partially implements Proposal 162: "Publish the consensus in
26590 - Directory authorities can now agree on and publish small summaries
26591 of router information that clients can use in place of regular
26592 server descriptors. This transition will eventually allow clients
26593 to use far less bandwidth for downloading information about the
26594 network. Begins the implementation of Proposal 158: "Clients
26595 download consensus + microdescriptors".
26596 - The directory voting system is now extensible to use multiple hash
26597 algorithms for signatures and resource selection. Newer formats
26598 are signed with SHA256, with a possibility for moving to a better
26599 hash algorithm in the future.
26600 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
26601 current and future memory pages via mlockall(). On supported
26602 platforms (modern Linux and probably BSD but not Windows or OS X),
26603 this should effectively disable any and all attempts to page out
26604 memory. This option requires that you start your Tor as root --
26605 if you use DisableAllSwap, please consider using the User option
26606 to properly reduce the privileges of your Tor.
26607 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
26608 to help Tor build correctly for Android phones.
26611 - Work around a security feature in OpenSSL 0.9.8l that prevents our
26612 handshake from working unless we explicitly tell OpenSSL that we
26613 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
26614 won't work unless we say we are.
26617 - Fix a crash bug when trying to initialize the evdns module in
26618 Libevent 2. Bugfix on 0.2.1.16-rc.
26619 - Stop logging at severity 'warn' when some other Tor client tries
26620 to establish a circuit with us using weak DH keys. It's a protocol
26621 violation, but that doesn't mean ordinary users need to hear about
26622 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
26623 - Do not refuse to learn about authority certs and v2 networkstatus
26624 documents that are older than the latest consensus. This bug might
26625 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
26626 Spotted and fixed by xmux.
26627 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
26628 - If all authorities restart at once right before a consensus vote,
26629 nobody will vote about "Running", and clients will get a consensus
26630 with no usable relays. Instead, authorities refuse to build a
26631 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
26632 - If your relay can't keep up with the number of incoming create
26633 cells, it would log one warning per failure into your logs. Limit
26634 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
26635 - Bridges now use "reject *:*" as their default exit policy. Bugfix
26636 on 0.2.0.3-alpha; fixes bug 1113.
26637 - Fix a memory leak on directory authorities during voting that was
26638 introduced in 0.2.2.1-alpha. Found via valgrind.
26641 Changes in version 0.2.1.20 - 2009-10-15
26642 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
26643 services at once, prepares for more performance improvements, and
26644 fixes a bunch of smaller bugs.
26646 The Windows and OS X bundles also include a more recent Vidalia,
26647 and switch from Privoxy to Polipo.
26649 The OS X installers are now drag and drop. It's best to un-install
26650 Tor/Vidalia and then install this new bundle, rather than upgrade. If
26651 you want to upgrade, you'll need to update the paths for Tor and Polipo
26652 in the Vidalia Settings window.
26655 - Send circuit or stream sendme cells when our window has decreased
26656 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
26657 by Karsten when testing the "reduce circuit window" performance
26658 patch. Bugfix on the 54th commit on Tor -- from July 2002,
26659 before the release of Tor 0.0.0. This is the new winner of the
26661 - Fix a remotely triggerable memory leak when a consensus document
26662 contains more than one signature from the same voter. Bugfix on
26664 - Avoid segfault in rare cases when finishing an introduction circuit
26665 as a client and finding out that we don't have an introduction key
26666 for it. Fixes bug 1073. Reported by Aaron Swartz.
26669 - Tor now reads the "circwindow" parameter out of the consensus,
26670 and uses that value for its circuit package window rather than the
26671 default of 1000 cells. Begins the implementation of proposal 168.
26673 o New directory authorities:
26674 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
26676 - Move moria1 and tonga to alternate IP addresses.
26679 - Fix a signed/unsigned compile warning in 0.2.1.19.
26680 - Fix possible segmentation fault on directory authorities. Bugfix on
26682 - Fix an extremely rare infinite recursion bug that could occur if
26683 we tried to log a message after shutting down the log subsystem.
26684 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
26685 - Fix an obscure bug where hidden services on 64-bit big-endian
26686 systems might mis-read the timestamp in v3 introduce cells, and
26687 refuse to connect back to the client. Discovered by "rotor".
26688 Bugfix on 0.2.1.6-alpha.
26689 - We were triggering a CLOCK_SKEW controller status event whenever
26690 we connect via the v2 connection protocol to any relay that has
26691 a wrong clock. Instead, we should only inform the controller when
26692 it's a trusted authority that claims our clock is wrong. Bugfix
26693 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
26694 - We were telling the controller about CHECKING_REACHABILITY and
26695 REACHABILITY_FAILED status events whenever we launch a testing
26696 circuit or notice that one has failed. Instead, only tell the
26697 controller when we want to inform the user of overall success or
26698 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
26700 - Don't warn when we're using a circuit that ends with a node
26701 excluded in ExcludeExitNodes, but the circuit is not used to access
26702 the outside world. This should help fix bug 1090. Bugfix on
26704 - Work around a small memory leak in some versions of OpenSSL that
26705 stopped the memory used by the hostname TLS extension from being
26709 - Add a "getinfo status/accepted-server-descriptor" controller
26710 command, which is the recommended way for controllers to learn
26711 whether our server descriptor has been successfully received by at
26712 least on directory authority. Un-recommend good-server-descriptor
26713 getinfo and status events until we have a better design for them.
26716 Changes in version 0.2.2.5-alpha - 2009-10-11
26717 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
26720 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
26722 o Directory authorities:
26723 - Temporarily (just for this release) move dizum to an alternate
26727 Changes in version 0.2.2.4-alpha - 2009-10-10
26728 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
26729 introduces a new unit test framework, shifts directry authority
26730 addresses around to reduce the impact from recent blocking events,
26731 and fixes a few smaller bugs.
26734 - Fix several more asserts in the circuit_build_times code, for
26735 example one that causes Tor to fail to start once we have
26736 accumulated 5000 build times in the state file. Bugfixes on
26737 0.2.2.2-alpha; fixes bug 1108.
26739 o New directory authorities:
26740 - Move moria1 and Tonga to alternate IP addresses.
26743 - Log SSL state transitions at debug level during handshake, and
26744 include SSL states in error messages. This may help debug future
26745 SSL handshake issues.
26746 - Add a new "Handshake" log domain for activities that happen
26747 during the TLS handshake.
26748 - Revert to the "June 3 2009" ip-to-country file. The September one
26749 seems to have removed most US IP addresses.
26750 - Directory authorities now reject Tor relays with versions less than
26751 0.1.2.14. This step cuts out four relays from the current network,
26752 none of which are very big.
26755 - Fix a couple of smaller issues with gathering statistics. Bugfixes
26757 - Fix two memory leaks in the error case of
26758 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
26759 - Don't count one-hop circuits when we're estimating how long it
26760 takes circuits to build on average. Otherwise we'll set our circuit
26761 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
26762 - Directory authorities no longer change their opinion of, or vote on,
26763 whether a router is Running, unless they have themselves been
26764 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
26767 o Code simplifications and refactoring:
26768 - Revise our unit tests to use the "tinytest" framework, so we
26769 can run tests in their own processes, have smarter setup/teardown
26770 code, and so on. The unit test code has moved to its own
26771 subdirectory, and has been split into multiple modules.
26774 Changes in version 0.2.2.3-alpha - 2009-09-23
26775 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
26778 - Fix an overzealous assert in our new circuit build timeout code.
26779 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
26782 - If the networkstatus consensus tells us that we should use a
26783 negative circuit package window, ignore it. Otherwise we'll
26784 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
26787 Changes in version 0.2.2.2-alpha - 2009-09-21
26788 Tor 0.2.2.2-alpha introduces our latest performance improvement for
26789 clients: Tor tracks the average time it takes to build a circuit, and
26790 avoids using circuits that take too long to build. For fast connections,
26791 this feature can cut your expected latency in half. For slow or flaky
26792 connections, it could ruin your Tor experience. Let us know if it does!
26795 - Tor now tracks how long it takes to build client-side circuits
26796 over time, and adapts its timeout to local network performance.
26797 Since a circuit that takes a long time to build will also provide
26798 bad performance, we get significant latency improvements by
26799 discarding the slowest 20% of circuits. Specifically, Tor creates
26800 circuits more aggressively than usual until it has enough data
26801 points for a good timeout estimate. Implements proposal 151.
26802 We are especially looking for reports (good and bad) from users with
26803 both EDGE and broadband connections that can move from broadband
26804 to EDGE and find out if the build-time data in the .tor/state gets
26805 reset without loss of Tor usability. You should also see a notice
26806 log message telling you that Tor has reset its timeout.
26807 - Directory authorities can now vote on arbitrary integer values as
26808 part of the consensus process. This is designed to help set
26809 network-wide parameters. Implements proposal 167.
26810 - Tor now reads the "circwindow" parameter out of the consensus,
26811 and uses that value for its circuit package window rather than the
26812 default of 1000 cells. Begins the implementation of proposal 168.
26815 - Fix a remotely triggerable memory leak when a consensus document
26816 contains more than one signature from the same voter. Bugfix on
26820 - Fix an extremely rare infinite recursion bug that could occur if
26821 we tried to log a message after shutting down the log subsystem.
26822 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
26823 - Fix parsing for memory or time units given without a space between
26824 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
26825 - A networkstatus vote must contain exactly one signature. Spec
26826 conformance issue. Bugfix on 0.2.0.3-alpha.
26827 - Fix an obscure bug where hidden services on 64-bit big-endian
26828 systems might mis-read the timestamp in v3 introduce cells, and
26829 refuse to connect back to the client. Discovered by "rotor".
26830 Bugfix on 0.2.1.6-alpha.
26831 - We were triggering a CLOCK_SKEW controller status event whenever
26832 we connect via the v2 connection protocol to any relay that has
26833 a wrong clock. Instead, we should only inform the controller when
26834 it's a trusted authority that claims our clock is wrong. Bugfix
26835 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
26836 - We were telling the controller about CHECKING_REACHABILITY and
26837 REACHABILITY_FAILED status events whenever we launch a testing
26838 circuit or notice that one has failed. Instead, only tell the
26839 controller when we want to inform the user of overall success or
26840 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
26842 - Don't warn when we're using a circuit that ends with a node
26843 excluded in ExcludeExitNodes, but the circuit is not used to access
26844 the outside world. This should help fix bug 1090, but more problems
26845 remain. Bugfix on 0.2.1.6-alpha.
26846 - Work around a small memory leak in some versions of OpenSSL that
26847 stopped the memory used by the hostname TLS extension from being
26849 - Make our 'torify' script more portable; if we have only one of
26850 'torsocks' or 'tsocks' installed, don't complain to the user;
26851 and explain our warning about tsocks better.
26854 - Add a "getinfo status/accepted-server-descriptor" controller
26855 command, which is the recommended way for controllers to learn
26856 whether our server descriptor has been successfully received by at
26857 least on directory authority. Un-recommend good-server-descriptor
26858 getinfo and status events until we have a better design for them.
26859 - Update to the "September 4 2009" ip-to-country file.
26862 Changes in version 0.2.2.1-alpha - 2009-08-26
26863 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
26864 Tor clients to bootstrap on networks where only port 80 is reachable,
26865 makes it more straightforward to support hardware crypto accelerators,
26866 and starts the groundwork for gathering stats safely at relays.
26869 - Start the process of disabling ".exit" address notation, since it
26870 can be used for a variety of esoteric application-level attacks
26871 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
26874 o New directory authorities:
26875 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
26879 - New AccelName and AccelDir options add support for dynamic OpenSSL
26880 hardware crypto acceleration engines.
26881 - Tor now supports tunneling all of its outgoing connections over
26882 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
26883 configuration options. Code by Christopher Davis.
26886 - Send circuit or stream sendme cells when our window has decreased
26887 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
26888 by Karsten when testing the "reduce circuit window" performance
26889 patch. Bugfix on the 54th commit on Tor -- from July 2002,
26890 before the release of Tor 0.0.0. This is the new winner of the
26893 o New options for gathering stats safely:
26894 - Directory mirrors that set "DirReqStatistics 1" write statistics
26895 about directory requests to disk every 24 hours. As compared to the
26896 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
26897 1) stats are written to disk exactly every 24 hours; 2) estimated
26898 shares of v2 and v3 requests are determined as mean values, not at
26899 the end of a measurement period; 3) unresolved requests are listed
26900 with country code '??'; 4) directories also measure download times.
26901 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
26902 number of exit streams and transferred bytes per port to disk every
26904 - Relays that set "CellStatistics 1" write statistics on how long
26905 cells spend in their circuit queues to disk every 24 hours.
26906 - Entry nodes that set "EntryStatistics 1" write statistics on the
26907 rough number and origins of connecting clients to disk every 24
26909 - Relays that write any of the above statistics to disk and set
26910 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
26911 their extra-info documents.
26914 - New --digests command-line switch to output the digests of the
26915 source files Tor was built with.
26916 - The "torify" script now uses torsocks where available.
26917 - The memarea code now uses a sentinel value at the end of each area
26918 to make sure nothing writes beyond the end of an area. This might
26919 help debug some conceivable causes of bug 930.
26920 - Time and memory units in the configuration file can now be set to
26921 fractional units. For example, "2.5 GB" is now a valid value for
26923 - Certain Tor clients (such as those behind check.torproject.org) may
26924 want to fetch the consensus in an extra early manner. To enable this
26925 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
26926 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
26927 as only certain clients who must have this information sooner should
26929 - Instead of adding the svn revision to the Tor version string, report
26930 the git commit (when we're building from a git checkout).
26933 - If any of the v3 certs we download are unparseable, we should
26934 actually notice the failure so we don't retry indefinitely. Bugfix
26935 on 0.2.0.x; reported by "rotator".
26936 - If the cached cert file is unparseable, warn but don't exit.
26937 - Fix possible segmentation fault on directory authorities. Bugfix on
26939 - When Tor fails to parse a descriptor of any kind, dump it to disk.
26940 Might help diagnosing bug 1051.
26942 o Deprecated and removed features:
26943 - The controller no longer accepts the old obsolete "addr-mappings/"
26944 or "unregistered-servers-" GETINFO values.
26945 - Hidden services no longer publish version 0 descriptors, and clients
26946 do not request or use version 0 descriptors. However, the old hidden
26947 service authorities still accept and serve version 0 descriptors
26948 when contacted by older hidden services/clients.
26949 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
26950 always on; using them is necessary for correct forward-compatible
26952 - Remove support for .noconnect style addresses. Nobody was using
26953 them, and they provided another avenue for detecting Tor users
26954 via application-level web tricks.
26956 o Packaging changes:
26957 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
26958 installer bundles. See
26959 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
26960 for details of what's new in Vidalia 0.2.3.
26961 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
26962 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
26963 configuration file, rather than the old Privoxy.
26964 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
26965 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
26966 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
26967 better compatibility with OS X 10.6, aka Snow Leopard.
26968 - OS X Vidalia Bundle: The multi-package installer is now replaced
26969 by a simple drag and drop to the /Applications folder. This change
26970 occurred with the upgrade to Vidalia 0.2.3.
26973 Changes in version 0.2.1.19 - 2009-07-28
26974 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
26975 services on Tor 0.2.1.3-alpha through 0.2.1.18.
26978 - Make accessing hidden services on 0.2.1.x work right again.
26979 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
26980 part of patch provided by "optimist".
26983 - When a relay/bridge is writing out its identity key fingerprint to
26984 the "fingerprint" file and to its logs, write it without spaces. Now
26985 it will look like the fingerprints in our bridges documentation,
26986 and confuse fewer users.
26989 - Relays no longer publish a new server descriptor if they change
26990 their MaxAdvertisedBandwidth config option but it doesn't end up
26991 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
26992 fixes bug 1026. Patch from Sebastian.
26993 - Avoid leaking memory every time we get a create cell but we have
26994 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
26995 fixes bug 1034. Reported by BarkerJr.
26998 Changes in version 0.2.1.18 - 2009-07-24
26999 Tor 0.2.1.18 lays the foundations for performance improvements,
27000 adds status events to help users diagnose bootstrap problems, adds
27001 optional authentication/authorization for hidden services, fixes a
27002 variety of potential anonymity problems, and includes a huge pile of
27003 other features and bug fixes.
27006 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
27009 Changes in version 0.2.1.17-rc - 2009-07-07
27010 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
27011 candidate for the 0.2.1.x series. It lays the groundwork for further
27012 client performance improvements, and also fixes a big bug with directory
27013 authorities that were causing them to assign Guard and Stable flags
27016 The Windows bundles also finally include the geoip database that we
27017 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
27018 should actually install Torbutton rather than giving you a cryptic
27019 failure message (oops).
27022 - Clients now use the bandwidth values in the consensus, rather than
27023 the bandwidth values in each relay descriptor. This approach opens
27024 the door to more accurate bandwidth estimates once the directory
27025 authorities start doing active measurements. Implements more of
27029 - When Tor clients restart after 1-5 days, they discard all their
27030 cached descriptors as too old, but they still use the cached
27031 consensus document. This approach is good for robustness, but
27032 bad for performance: since they don't know any bandwidths, they
27033 end up choosing at random rather than weighting their choice by
27034 speed. Fixed by the above feature of putting bandwidths in the
27035 consensus. Bugfix on 0.2.0.x.
27036 - Directory authorities were neglecting to mark relays down in their
27037 internal histories if the relays fall off the routerlist without
27038 ever being found unreachable. So there were relays in the histories
27039 that haven't been seen for eight months, and are listed as being
27040 up for eight months. This wreaked havoc on the "median wfu"
27041 and "median mtbf" calculations, in turn making Guard and Stable
27042 flags very wrong, hurting network performance. Fixes bugs 696 and
27043 969. Bugfix on 0.2.0.6-alpha.
27046 - Serve the DirPortFrontPage page even when we have been approaching
27047 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
27048 - The control port would close the connection before flushing long
27049 replies, such as the network consensus, if a QUIT command was issued
27050 before the reply had completed. Now, the control port flushes all
27051 pending replies before closing the connection. Also fixed a spurious
27052 warning when a QUIT command is issued after a malformed or rejected
27053 AUTHENTICATE command, but before the connection was closed. Patch
27054 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
27055 - When we can't find an intro key for a v2 hidden service descriptor,
27056 fall back to the v0 hidden service descriptor and log a bug message.
27057 Workaround for bug 1024.
27058 - Fix a log message that did not respect the SafeLogging option.
27062 - If we're a relay and we change our IP address, be more verbose
27063 about the reason that made us change. Should help track down
27064 further bugs for relays on dynamic IP addresses.
27067 Changes in version 0.2.0.35 - 2009-06-24
27069 - Avoid crashing in the presence of certain malformed descriptors.
27070 Found by lark, and by automated fuzzing.
27071 - Fix an edge case where a malicious exit relay could convince a
27072 controller that the client's DNS question resolves to an internal IP
27073 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
27076 - Finally fix the bug where dynamic-IP relays disappear when their
27077 IP address changes: directory mirrors were mistakenly telling
27078 them their old address if they asked via begin_dir, so they
27079 never got an accurate answer about their new address, so they
27080 just vanished after a day. For belt-and-suspenders, relays that
27081 don't set Address in their config now avoid using begin_dir for
27082 all direct connections. Should fix bugs 827, 883, and 900.
27083 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
27084 that would occur on some exit nodes when DNS failures and timeouts
27085 occurred in certain patterns. Fix for bug 957.
27088 - When starting with a cache over a few days old, do not leak
27089 memory for the obsolete router descriptors in it. Bugfix on
27090 0.2.0.33; fixes bug 672.
27091 - Hidden service clients didn't use a cached service descriptor that
27092 was older than 15 minutes, but wouldn't fetch a new one either,
27093 because there was already one in the cache. Now, fetch a v2
27094 descriptor unless the same descriptor was added to the cache within
27095 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
27098 Changes in version 0.2.1.16-rc - 2009-06-20
27099 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
27100 a bunch of minor bugs.
27103 - Fix an edge case where a malicious exit relay could convince a
27104 controller that the client's DNS question resolves to an internal IP
27105 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
27107 o Major performance improvements (on 0.2.0.x):
27108 - Disable and refactor some debugging checks that forced a linear scan
27109 over the whole server-side DNS cache. These accounted for over 50%
27110 of CPU time on a relatively busy exit node's gprof profile. Found
27112 - Disable some debugging checks that appeared in exit node profile
27116 - Update to the "June 3 2009" ip-to-country file.
27117 - Do not have tor-resolve automatically refuse all .onion addresses;
27118 if AutomapHostsOnResolve is set in your torrc, this will work fine.
27120 o Minor bugfixes (on 0.2.0.x):
27121 - Log correct error messages for DNS-related network errors on
27123 - Fix a race condition that could cause crashes or memory corruption
27124 when running as a server with a controller listening for log
27126 - Avoid crashing when we have a policy specified in a DirPolicy or
27127 SocksPolicy or ReachableAddresses option with ports set on it,
27128 and we re-load the policy. May fix bug 996.
27129 - Hidden service clients didn't use a cached service descriptor that
27130 was older than 15 minutes, but wouldn't fetch a new one either,
27131 because there was already one in the cache. Now, fetch a v2
27132 descriptor unless the same descriptor was added to the cache within
27133 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
27135 o Minor bugfixes (on 0.2.1.x):
27136 - Don't warn users about low port and hibernation mix when they
27137 provide a *ListenAddress directive to fix that. Bugfix on
27139 - When switching back and forth between bridge mode, do not start
27140 gathering GeoIP data until two hours have passed.
27141 - Do not complain that the user has requested an excluded node as
27142 an exit when the node is not really an exit. This could happen
27143 because the circuit was for testing, or an introduction point.
27147 Changes in version 0.2.1.15-rc - 2009-05-25
27148 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
27149 series. It fixes a major bug on fast exit relays, as well as a variety
27150 of more minor bugs.
27152 o Major bugfixes (on 0.2.0.x):
27153 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
27154 that would occur on some exit nodes when DNS failures and timeouts
27155 occurred in certain patterns. Fix for bug 957.
27157 o Minor bugfixes (on 0.2.0.x):
27158 - Actually return -1 in the error case for read_bandwidth_usage().
27159 Harmless bug, since we currently don't care about the return value
27160 anywhere. Bugfix on 0.2.0.9-alpha.
27161 - Provide a more useful log message if bug 977 (related to buffer
27162 freelists) ever reappears, and do not crash right away.
27163 - Fix an assertion failure on 64-bit platforms when we allocated
27164 memory right up to the end of a memarea, then realigned the memory
27165 one step beyond the end. Fixes a possible cause of bug 930.
27166 - Protect the count of open sockets with a mutex, so we can't
27167 corrupt it when two threads are closing or opening sockets at once.
27168 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
27169 - Don't allow a bridge to publish its router descriptor to a
27170 non-bridge directory authority. Fixes part of bug 932.
27171 - When we change to or from being a bridge, reset our counts of
27172 client usage by country. Fixes bug 932.
27173 - Fix a bug that made stream bandwidth get misreported to the
27175 - Stop using malloc_usable_size() to use more area than we had
27176 actually allocated: it was safe, but made valgrind really unhappy.
27177 - Fix a memory leak when v3 directory authorities load their keys
27178 and cert from disk. Bugfix on 0.2.0.1-alpha.
27180 o Minor bugfixes (on 0.2.1.x):
27181 - Fix use of freed memory when deciding to mark a non-addable
27182 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
27185 Changes in version 0.2.1.14-rc - 2009-04-12
27186 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
27187 series. It begins fixing some major performance problems, and also
27188 finally addresses the bug that was causing relays on dynamic IP
27189 addresses to fall out of the directory.
27192 - Clients replace entry guards that were chosen more than a few months
27193 ago. This change should significantly improve client performance,
27194 especially once more people upgrade, since relays that have been
27195 a guard for a long time are currently overloaded.
27197 o Major bugfixes (on 0.2.0):
27198 - Finally fix the bug where dynamic-IP relays disappear when their
27199 IP address changes: directory mirrors were mistakenly telling
27200 them their old address if they asked via begin_dir, so they
27201 never got an accurate answer about their new address, so they
27202 just vanished after a day. For belt-and-suspenders, relays that
27203 don't set Address in their config now avoid using begin_dir for
27204 all direct connections. Should fix bugs 827, 883, and 900.
27205 - Relays were falling out of the networkstatus consensus for
27206 part of a day if they changed their local config but the
27207 authorities discarded their new descriptor as "not sufficiently
27208 different". Now directory authorities accept a descriptor as changed
27209 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
27210 patch by Sebastian.
27211 - Avoid crashing in the presence of certain malformed descriptors.
27212 Found by lark, and by automated fuzzing.
27215 - When generating circuit events with verbose nicknames for
27216 controllers, try harder to look up nicknames for routers on a
27217 circuit. (Previously, we would look in the router descriptors we had
27218 for nicknames, but not in the consensus.) Partial fix for bug 941.
27219 - If the bridge config line doesn't specify a port, assume 443.
27220 This makes bridge lines a bit smaller and easier for users to
27222 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
27223 bytes (aka 20KB/s), to match our documentation. Also update
27224 directory authorities so they always assign the Fast flag to relays
27225 with 20KB/s of capacity. Now people running relays won't suddenly
27226 find themselves not seeing any use, if the network gets faster
27228 - Update to the "April 3 2009" ip-to-country file.
27231 - Avoid trying to print raw memory to the logs when we decide to
27232 give up on downloading a given relay descriptor. Bugfix on
27234 - In tor-resolve, when the Tor client to use is specified by
27235 <hostname>:<port>, actually use the specified port rather than
27236 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
27237 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
27238 - When starting with a cache over a few days old, do not leak
27239 memory for the obsolete router descriptors in it. Bugfix on
27241 - Avoid double-free on list of successfully uploaded hidden
27242 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
27243 - Change memarea_strndup() implementation to work even when
27244 duplicating a string at the end of a page. This bug was
27245 harmless for now, but could have meant crashes later. Fix by
27246 lark. Bugfix on 0.2.1.1-alpha.
27247 - Limit uploaded directory documents to be 16M rather than 500K.
27248 The directory authorities were refusing v3 consensus votes from
27249 other authorities, since the votes are now 504K. Fixes bug 959;
27250 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
27251 - Directory authorities should never send a 503 "busy" response to
27252 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
27256 Changes in version 0.2.1.13-alpha - 2009-03-09
27257 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
27258 cleanups. We're finally getting close to a release candidate.
27261 - Correctly update the list of which countries we exclude as
27262 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
27263 lark. Bugfix on 0.2.1.6-alpha.
27265 o Minor bugfixes (on 0.2.0.x and earlier):
27266 - Automatically detect MacOSX versions earlier than 10.4.0, and
27267 disable kqueue from inside Tor when running with these versions.
27268 We previously did this from the startup script, but that was no
27269 help to people who didn't use the startup script. Resolves bug 863.
27270 - When we had picked an exit node for a connection, but marked it as
27271 "optional", and it turned out we had no onion key for the exit,
27272 stop wanting that exit and try again. This situation may not
27273 be possible now, but will probably become feasible with proposal
27274 158. Spotted by rovv. Fixes another case of bug 752.
27275 - Clients no longer cache certificates for authorities they do not
27276 recognize. Bugfix on 0.2.0.9-alpha.
27277 - When we can't transmit a DNS request due to a network error, retry
27278 it after a while, and eventually transmit a failing response to
27279 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
27280 - If the controller claimed responsibility for a stream, but that
27281 stream never finished making its connection, it would live
27282 forever in circuit_wait state. Now we close it after SocksTimeout
27283 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
27284 - Drop begin cells to a hidden service if they come from the middle
27285 of a circuit. Patch from lark.
27286 - When we erroneously receive two EXTEND cells for the same circuit
27287 ID on the same connection, drop the second. Patch from lark.
27288 - Fix a crash that occurs on exit nodes when a nameserver request
27289 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
27290 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
27292 - Do not assume that a stack-allocated character array will be
27293 64-bit aligned on platforms that demand that uint64_t access is
27294 aligned. Possible fix for bug 604.
27295 - Parse dates and IPv4 addresses in a locale- and libc-independent
27296 manner, to avoid platform-dependent behavior on malformed input.
27297 - Build correctly when configured to build outside the main source
27298 path. Patch from Michael Gold.
27299 - We were already rejecting relay begin cells with destination port
27300 of 0. Now also reject extend cells with destination port or address
27301 of 0. Suggested by lark.
27303 o Minor bugfixes (on 0.2.1.x):
27304 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
27305 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
27306 - If we're an exit node, scrub the IP address to which we are exiting
27307 in the logs. Bugfix on 0.2.1.8-alpha.
27310 - On Linux, use the prctl call to re-enable core dumps when the user
27312 - New controller event NEWCONSENSUS that lists the networkstatus
27313 lines for every recommended relay. Now controllers like Torflow
27314 can keep up-to-date on which relays they should be using.
27315 - Update to the "February 26 2009" ip-to-country file.
27318 Changes in version 0.2.0.34 - 2009-02-08
27319 Tor 0.2.0.34 features several more security-related fixes. You should
27320 upgrade, especially if you run an exit relay (remote crash) or a
27321 directory authority (remote infinite loop), or you're on an older
27322 (pre-XP) or not-recently-patched Windows (remote exploit).
27324 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
27325 have many known flaws, and nobody should be using them. You should
27326 upgrade. If you're using a Linux or BSD and its packages are obsolete,
27327 stop using those packages and upgrade anyway.
27330 - Fix an infinite-loop bug on handling corrupt votes under certain
27331 circumstances. Bugfix on 0.2.0.8-alpha.
27332 - Fix a temporary DoS vulnerability that could be performed by
27333 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
27334 - Avoid a potential crash on exit nodes when processing malformed
27335 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
27336 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
27337 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
27340 - Fix compilation on systems where time_t is a 64-bit integer.
27341 Patch from Matthias Drochner.
27342 - Don't consider expiring already-closed client connections. Fixes
27343 bug 893. Bugfix on 0.0.2pre20.
27346 Changes in version 0.2.1.12-alpha - 2009-02-08
27347 Tor 0.2.1.12-alpha features several more security-related fixes. You
27348 should upgrade, especially if you run an exit relay (remote crash) or
27349 a directory authority (remote infinite loop), or you're on an older
27350 (pre-XP) or not-recently-patched Windows (remote exploit). It also
27351 includes a big pile of minor bugfixes and cleanups.
27354 - Fix an infinite-loop bug on handling corrupt votes under certain
27355 circumstances. Bugfix on 0.2.0.8-alpha.
27356 - Fix a temporary DoS vulnerability that could be performed by
27357 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
27358 - Avoid a potential crash on exit nodes when processing malformed
27359 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
27362 - Let controllers actually ask for the "clients_seen" event for
27363 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
27364 reported by Matt Edman.
27365 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
27367 - Fix a bug in address parsing that was preventing bridges or hidden
27368 service targets from being at IPv6 addresses.
27369 - Solve a bug that kept hardware crypto acceleration from getting
27370 enabled when accounting was turned on. Fixes bug 907. Bugfix on
27372 - Remove a bash-ism from configure.in to build properly on non-Linux
27373 platforms. Bugfix on 0.2.1.1-alpha.
27374 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
27375 headers. Bugfix on 0.2.0.10-alpha.
27376 - Don't consider expiring already-closed client connections. Fixes
27377 bug 893. Bugfix on 0.0.2pre20.
27378 - Fix another interesting corner-case of bug 891 spotted by rovv:
27379 Previously, if two hosts had different amounts of clock drift, and
27380 one of them created a new connection with just the wrong timing,
27381 the other might decide to deprecate the new connection erroneously.
27382 Bugfix on 0.1.1.13-alpha.
27383 - Resolve a very rare crash bug that could occur when the user forced
27384 a nameserver reconfiguration during the middle of a nameserver
27385 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
27386 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
27387 Bugfix on 0.2.1.7-alpha.
27388 - If we're using bridges and our network goes away, be more willing
27389 to forgive our bridges and try again when we get an application
27390 request. Bugfix on 0.2.0.x.
27393 - Support platforms where time_t is 64 bits long. (Congratulations,
27394 NetBSD!) Patch from Matthias Drochner.
27395 - Add a 'getinfo status/clients-seen' controller command, in case
27396 controllers want to hear clients_seen events but connect late.
27399 - Disable GCC's strict alias optimization by default, to avoid the
27400 likelihood of its introducing subtle bugs whenever our code violates
27401 the letter of C99's alias rules.
27404 Changes in version 0.2.0.33 - 2009-01-21
27405 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
27406 useful to users. It also finally fixes a bug where a relay or client
27407 that's been off for many days would take a long time to bootstrap.
27409 This update also fixes an important security-related bug reported by
27410 Ilja van Sprundel. You should upgrade. (We'll send out more details
27411 about the bug once people have had some time to upgrade.)
27414 - Fix a heap-corruption bug that may be remotely triggerable on
27415 some platforms. Reported by Ilja van Sprundel.
27418 - When a stream at an exit relay is in state "resolving" or
27419 "connecting" and it receives an "end" relay cell, the exit relay
27420 would silently ignore the end cell and not close the stream. If
27421 the client never closes the circuit, then the exit relay never
27422 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
27423 reported by "wood".
27424 - When sending CREATED cells back for a given circuit, use a 64-bit
27425 connection ID to find the right connection, rather than an addr:port
27426 combination. Now that we can have multiple OR connections between
27427 the same ORs, it is no longer possible to use addr:port to uniquely
27428 identify a connection.
27429 - Bridge relays that had DirPort set to 0 would stop fetching
27430 descriptors shortly after startup, and then briefly resume
27431 after a new bandwidth test and/or after publishing a new bridge
27432 descriptor. Bridge users that try to bootstrap from them would
27433 get a recent networkstatus but would get descriptors from up to
27434 18 hours earlier, meaning most of the descriptors were obsolete
27435 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
27436 - Prevent bridge relays from serving their 'extrainfo' document
27437 to anybody who asks, now that extrainfo docs include potentially
27438 sensitive aggregated client geoip summaries. Bugfix on
27440 - If the cached networkstatus consensus is more than five days old,
27441 discard it rather than trying to use it. In theory it could be
27442 useful because it lists alternate directory mirrors, but in practice
27443 it just means we spend many minutes trying directory mirrors that
27444 are long gone from the network. Also discard router descriptors as
27445 we load them if they are more than five days old, since the onion
27446 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
27449 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
27450 could make gcc generate non-functional binary search code. Bugfix
27452 - Build correctly on platforms without socklen_t.
27453 - Compile without warnings on solaris.
27454 - Avoid potential crash on internal error during signature collection.
27455 Fixes bug 864. Patch from rovv.
27456 - Correct handling of possible malformed authority signing key
27457 certificates with internal signature types. Fixes bug 880.
27458 Bugfix on 0.2.0.3-alpha.
27459 - Fix a hard-to-trigger resource leak when logging credential status.
27461 - When we can't initialize DNS because the network is down, do not
27462 automatically stop Tor from starting. Instead, we retry failed
27463 dns_init() every 10 minutes, and change the exit policy to reject
27464 *:* until one succeeds. Fixes bug 691.
27465 - Use 64 bits instead of 32 bits for connection identifiers used with
27466 the controller protocol, to greatly reduce risk of identifier reuse.
27467 - When we're choosing an exit node for a circuit, and we have
27468 no pending streams, choose a good general exit rather than one that
27469 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
27470 - Fix another case of assuming, when a specific exit is requested,
27471 that we know more than the user about what hosts it allows.
27472 Fixes one case of bug 752. Patch from rovv.
27473 - Clip the MaxCircuitDirtiness config option to a minimum of 10
27474 seconds. Warn the user if lower values are given in the
27475 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
27476 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
27477 user if lower values are given in the configuration. Bugfix on
27478 0.1.1.17-rc. Patch by Sebastian.
27479 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
27480 the cache because we already had a v0 descriptor with the same ID.
27481 Bugfix on 0.2.0.18-alpha.
27482 - Fix a race condition when freeing keys shared between main thread
27483 and CPU workers that could result in a memory leak. Bugfix on
27484 0.1.0.1-rc. Fixes bug 889.
27485 - Send a valid END cell back when a client tries to connect to a
27486 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
27487 840. Patch from rovv.
27488 - Check which hops rendezvous stream cells are associated with to
27489 prevent possible guess-the-streamid injection attacks from
27490 intermediate hops. Fixes another case of bug 446. Based on patch
27492 - If a broken client asks a non-exit router to connect somewhere,
27493 do not even do the DNS lookup before rejecting the connection.
27494 Fixes another case of bug 619. Patch from rovv.
27495 - When a relay gets a create cell it can't decrypt (e.g. because it's
27496 using the wrong onion key), we were dropping it and letting the
27497 client time out. Now actually answer with a destroy cell. Fixes
27498 bug 904. Bugfix on 0.0.2pre8.
27500 o Minor bugfixes (hidden services):
27501 - Do not throw away existing introduction points on SIGHUP. Bugfix on
27502 0.0.6pre1. Patch by Karsten. Fixes bug 874.
27505 - Report the case where all signatures in a detached set are rejected
27506 differently than the case where there is an error handling the
27508 - When we realize that another process has modified our cached
27509 descriptors, print out a more useful error message rather than
27510 triggering an assertion. Fixes bug 885. Patch from Karsten.
27511 - Implement the 0x20 hack to better resist DNS poisoning: set the
27512 case on outgoing DNS requests randomly, and reject responses that do
27513 not match the case correctly. This logic can be disabled with the
27514 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
27515 of servers that do not reliably preserve case in replies. See
27516 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
27518 - Check DNS replies for more matching fields to better resist DNS
27520 - Never use OpenSSL compression: it wastes RAM and CPU trying to
27521 compress cells, which are basically all encrypted, compressed, or
27525 Changes in version 0.2.1.11-alpha - 2009-01-20
27526 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
27527 week it will take a long time to bootstrap again" bug. It also fixes
27528 an important security-related bug reported by Ilja van Sprundel. You
27529 should upgrade. (We'll send out more details about the bug once people
27530 have had some time to upgrade.)
27533 - Fix a heap-corruption bug that may be remotely triggerable on
27534 some platforms. Reported by Ilja van Sprundel.
27537 - Discard router descriptors as we load them if they are more than
27538 five days old. Otherwise if Tor is off for a long time and then
27539 starts with cached descriptors, it will try to use the onion
27540 keys in those obsolete descriptors when building circuits. Bugfix
27541 on 0.2.0.x. Fixes bug 887.
27544 - Try to make sure that the version of Libevent we're running with
27545 is binary-compatible with the one we built with. May address bug
27547 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
27548 for bug 905. Bugfix on 0.2.1.7-alpha.
27549 - Add a new --enable-local-appdata configuration switch to change
27550 the default location of the datadir on win32 from APPDATA to
27551 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
27552 entirely. Patch from coderman.
27555 - Make outbound DNS packets respect the OutboundBindAddress setting.
27556 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
27557 - When our circuit fails at the first hop (e.g. we get a destroy
27558 cell back), avoid using that OR connection anymore, and also
27559 tell all the one-hop directory requests waiting for it that they
27560 should fail. Bugfix on 0.2.1.3-alpha.
27561 - In the torify(1) manpage, mention that tsocks will leak your
27565 Changes in version 0.2.1.10-alpha - 2009-01-06
27566 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
27567 would make the bridge relay not so useful if it had DirPort set to 0,
27568 and one that could let an attacker learn a little bit of information
27569 about the bridge's users), and a bug that would cause your Tor relay
27570 to ignore a circuit create request it can't decrypt (rather than reply
27571 with an error). It also fixes a wide variety of other bugs.
27574 - If the cached networkstatus consensus is more than five days old,
27575 discard it rather than trying to use it. In theory it could
27576 be useful because it lists alternate directory mirrors, but in
27577 practice it just means we spend many minutes trying directory
27578 mirrors that are long gone from the network. Helps bug 887 a bit;
27580 - Bridge relays that had DirPort set to 0 would stop fetching
27581 descriptors shortly after startup, and then briefly resume
27582 after a new bandwidth test and/or after publishing a new bridge
27583 descriptor. Bridge users that try to bootstrap from them would
27584 get a recent networkstatus but would get descriptors from up to
27585 18 hours earlier, meaning most of the descriptors were obsolete
27586 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
27587 - Prevent bridge relays from serving their 'extrainfo' document
27588 to anybody who asks, now that extrainfo docs include potentially
27589 sensitive aggregated client geoip summaries. Bugfix on
27593 - New controller event "clients_seen" to report a geoip-based summary
27594 of which countries we've seen clients from recently. Now controllers
27595 like Vidalia can show bridge operators that they're actually making
27597 - Build correctly against versions of OpenSSL 0.9.8 or later built
27598 without support for deprecated functions.
27599 - Update to the "December 19 2008" ip-to-country file.
27601 o Minor bugfixes (on 0.2.0.x):
27602 - Authorities now vote for the Stable flag for any router whose
27603 weighted MTBF is at least 5 days, regardless of the mean MTBF.
27604 - Do not remove routers as too old if we do not have any consensus
27605 document. Bugfix on 0.2.0.7-alpha.
27606 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
27607 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
27608 - When an exit relay resolves a stream address to a local IP address,
27609 do not just keep retrying that same exit relay over and
27610 over. Instead, just close the stream. Addresses bug 872. Bugfix
27611 on 0.2.0.32. Patch from rovv.
27612 - If a hidden service sends us an END cell, do not consider
27613 retrying the connection; just close it. Patch from rovv.
27614 - When we made bridge authorities stop serving bridge descriptors over
27615 unencrypted links, we also broke DirPort reachability testing for
27616 bridges. So bridges with a non-zero DirPort were printing spurious
27617 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
27618 - When a relay gets a create cell it can't decrypt (e.g. because it's
27619 using the wrong onion key), we were dropping it and letting the
27620 client time out. Now actually answer with a destroy cell. Fixes
27621 bug 904. Bugfix on 0.0.2pre8.
27622 - Squeeze 2-5% out of client performance (according to oprofile) by
27623 improving the implementation of some policy-manipulation functions.
27625 o Minor bugfixes (on 0.2.1.x):
27626 - Make get_interface_address() function work properly again; stop
27627 guessing the wrong parts of our address as our address.
27628 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
27629 send on that circuit. Otherwise we might violate the proposal-110
27630 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
27632 - When we're sending non-EXTEND cells to the first hop in a circuit,
27633 for example to use an encrypted directory connection, we don't need
27634 to use RELAY_EARLY cells: the first hop knows what kind of cell
27635 it is, and nobody else can even see the cell type. Conserving
27636 RELAY_EARLY cells makes it easier to cannibalize circuits like
27638 - Stop logging nameserver addresses in reverse order.
27639 - If we are retrying a directory download slowly over and over, do
27640 not automatically give up after the 254th failure. Bugfix on
27642 - Resume reporting accurate "stream end" reasons to the local control
27643 port. They were lost in the changes for Proposal 148. Bugfix on
27646 o Deprecated and removed features:
27647 - The old "tor --version --version" command, which would print out
27648 the subversion "Id" of most of the source files, is now removed. It
27649 turned out to be less useful than we'd expected, and harder to
27652 o Code simplifications and refactoring:
27653 - Change our header file guard macros to be less likely to conflict
27654 with system headers. Adam Langley noticed that we were conflicting
27655 with log.h on Android.
27656 - Tool-assisted documentation cleanup. Nearly every function or
27657 static variable in Tor should have its own documentation now.
27660 Changes in version 0.2.1.9-alpha - 2008-12-25
27661 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
27663 o New directory authorities:
27664 - gabelmoo (the authority run by Karsten Loesing) now has a new
27668 - Never use a connection with a mismatched address to extend a
27669 circuit, unless that connection is canonical. A canonical
27670 connection is one whose address is authenticated by the router's
27671 identity key, either in a NETINFO cell or in a router descriptor.
27672 - Avoid a possible memory corruption bug when receiving hidden service
27673 descriptors. Bugfix on 0.2.1.6-alpha.
27676 - Fix a logic error that would automatically reject all but the first
27677 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
27678 part of bug 813/868. Bug spotted by coderman.
27679 - When a stream at an exit relay is in state "resolving" or
27680 "connecting" and it receives an "end" relay cell, the exit relay
27681 would silently ignore the end cell and not close the stream. If
27682 the client never closes the circuit, then the exit relay never
27683 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
27684 reported by "wood".
27685 - When we can't initialize DNS because the network is down, do not
27686 automatically stop Tor from starting. Instead, retry failed
27687 dns_init() every 10 minutes, and change the exit policy to reject
27688 *:* until one succeeds. Fixes bug 691.
27691 - Give a better error message when an overzealous init script says
27692 "sudo -u username tor --user username". Makes Bug 882 easier for
27694 - When a directory authority gives us a new guess for our IP address,
27695 log which authority we used. Hopefully this will help us debug
27696 the recent complaints about bad IP address guesses.
27697 - Detect svn revision properly when we're using git-svn.
27698 - Try not to open more than one descriptor-downloading connection
27699 to an authority at once. This should reduce load on directory
27700 authorities. Fixes bug 366.
27701 - Add cross-certification to newly generated certificates, so that
27702 a signing key is enough information to look up a certificate.
27703 Partial implementation of proposal 157.
27704 - Start serving certificates by <identity digest, signing key digest>
27705 pairs. Partial implementation of proposal 157.
27706 - Clients now never report any stream end reason except 'MISC'.
27707 Implements proposal 148.
27708 - On platforms with a maximum syslog string length, truncate syslog
27709 messages to that length ourselves, rather than relying on the
27710 system to do it for us.
27711 - Optimize out calls to time(NULL) that occur for every IO operation,
27712 or for every cell. On systems where time() is a slow syscall,
27713 this fix will be slightly helpful.
27714 - Exit servers can now answer resolve requests for ip6.arpa addresses.
27715 - When we download a descriptor that we then immediately (as
27716 a directory authority) reject, do not retry downloading it right
27717 away. Should save some bandwidth on authorities. Fix for bug
27718 888. Patch by Sebastian Hahn.
27719 - When a download gets us zero good descriptors, do not notify
27720 Tor that new directory information has arrived.
27721 - Avoid some nasty corner cases in the logic for marking connections
27722 as too old or obsolete or noncanonical for circuits. Partial
27725 o Minor features (controller):
27726 - New CONSENSUS_ARRIVED event to note when a new consensus has
27727 been fetched and validated.
27728 - When we realize that another process has modified our cached
27729 descriptors file, print out a more useful error message rather
27730 than triggering an assertion. Fixes bug 885. Patch from Karsten.
27731 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
27732 controllers to prevent SIGHUP from reloading the
27733 configuration. Fixes bug 856.
27736 - Resume using the correct "REASON=" stream when telling the
27737 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
27738 - When a canonical connection appears later in our internal list
27739 than a noncanonical one for a given OR ID, always use the
27740 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
27742 - Clip the MaxCircuitDirtiness config option to a minimum of 10
27743 seconds. Warn the user if lower values are given in the
27744 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
27745 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
27746 user if lower values are given in the configuration. Bugfix on
27747 0.1.1.17-rc. Patch by Sebastian.
27748 - Fix a race condition when freeing keys shared between main thread
27749 and CPU workers that could result in a memory leak. Bugfix on
27750 0.1.0.1-rc. Fixes bug 889.
27752 o Minor bugfixes (hidden services):
27753 - Do not throw away existing introduction points on SIGHUP (bugfix on
27754 0.0.6pre1); also, do not stall hidden services because we're
27755 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
27756 by John Brooks. Patch by Karsten. Fixes bug 874.
27757 - Fix a memory leak when we decline to add a v2 rendezvous
27758 descriptor to the cache because we already had a v0 descriptor
27759 with the same ID. Bugfix on 0.2.0.18-alpha.
27761 o Deprecated and removed features:
27762 - RedirectExits has been removed. It was deprecated since
27764 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
27765 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
27766 - Cell pools are now always enabled; --disable-cell-pools is ignored.
27768 o Code simplifications and refactoring:
27769 - Rename the confusing or_is_obsolete field to the more appropriate
27770 is_bad_for_new_circs, and move it to or_connection_t where it
27772 - Move edge-only flags from connection_t to edge_connection_t: not
27773 only is this better coding, but on machines of plausible alignment,
27774 it should save 4-8 bytes per connection_t. "Every little bit helps."
27775 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
27776 for consistency; keep old option working for backward compatibility.
27777 - Simplify the code for finding connections to use for a circuit.
27780 Changes in version 0.2.1.8-alpha - 2008-12-08
27781 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
27782 builds better on unusual platforms like Solaris and old OS X, and
27783 fixes a variety of other issues.
27786 - New DirPortFrontPage option that takes an html file and publishes
27787 it as "/" on the DirPort. Now relay operators can provide a
27788 disclaimer without needing to set up a separate webserver. There's
27789 a sample disclaimer in contrib/tor-exit-notice.html.
27792 - When the client is choosing entry guards, now it selects at most
27793 one guard from a given relay family. Otherwise we could end up with
27794 all of our entry points into the network run by the same operator.
27795 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
27798 - Fix a DOS opportunity during the voting signature collection process
27799 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
27800 - Fix a possible segfault when establishing an exit connection. Bugfix
27804 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
27806 - Made Tor a little less aggressive about deleting expired
27807 certificates. Partial fix for bug 854.
27808 - Stop doing unaligned memory access that generated bus errors on
27809 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
27810 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
27811 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
27812 - Make USR2 log-level switch take effect immediately. Bugfix on
27814 - If one win32 nameserver fails to get added, continue adding the
27815 rest, and don't automatically fail.
27816 - Use fcntl() for locking when flock() is not available. Should fix
27817 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
27818 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
27819 could make gcc generate non-functional binary search code. Bugfix
27821 - Build correctly on platforms without socklen_t.
27822 - Avoid potential crash on internal error during signature collection.
27823 Fixes bug 864. Patch from rovv.
27824 - Do not use C's stdio library for writing to log files. This will
27825 improve logging performance by a minute amount, and will stop
27826 leaking fds when our disk is full. Fixes bug 861.
27827 - Stop erroneous use of O_APPEND in cases where we did not in fact
27828 want to re-seek to the end of a file before every last write().
27829 - Correct handling of possible malformed authority signing key
27830 certificates with internal signature types. Fixes bug 880. Bugfix
27832 - Fix a hard-to-trigger resource leak when logging credential status.
27836 - Directory mirrors no longer fetch the v1 directory or
27837 running-routers files. They are obsolete, and nobody asks for them
27838 anymore. This is the first step to making v1 authorities obsolete.
27840 o Minor features (controller):
27841 - Return circuit purposes in response to GETINFO circuit-status. Fixes
27845 Changes in version 0.2.0.32 - 2008-11-20
27846 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
27847 packages (and maybe other packages) noticed by Theo de Raadt, fixes
27848 a smaller security flaw that might allow an attacker to access local
27849 services, further improves hidden service performance, and fixes a
27850 variety of other issues.
27853 - The "User" and "Group" config options did not clear the
27854 supplementary group entries for the Tor process. The "User" option
27855 is now more robust, and we now set the groups to the specified
27856 user's primary group. The "Group" option is now ignored. For more
27857 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
27858 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
27859 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
27860 - The "ClientDNSRejectInternalAddresses" config option wasn't being
27861 consistently obeyed: if an exit relay refuses a stream because its
27862 exit policy doesn't allow it, we would remember what IP address
27863 the relay said the destination address resolves to, even if it's
27864 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
27867 - Fix a DOS opportunity during the voting signature collection process
27868 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
27870 o Major bugfixes (hidden services):
27871 - When fetching v0 and v2 rendezvous service descriptors in parallel,
27872 we were failing the whole hidden service request when the v0
27873 descriptor fetch fails, even if the v2 fetch is still pending and
27874 might succeed. Similarly, if the last v2 fetch fails, we were
27875 failing the whole hidden service request even if a v0 fetch is
27876 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
27877 - When extending a circuit to a hidden service directory to upload a
27878 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
27879 requests failed, because the router descriptor has not been
27880 downloaded yet. In these cases, do not attempt to upload the
27881 rendezvous descriptor, but wait until the router descriptor is
27882 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
27883 descriptor from a hidden service directory for which the router
27884 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
27888 - Fix several infrequent memory leaks spotted by Coverity.
27889 - When testing for libevent functions, set the LDFLAGS variable
27890 correctly. Found by Riastradh.
27891 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
27892 bootstrapping with tunneled directory connections. Bugfix on
27893 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
27894 - When asked to connect to A.B.exit:80, if we don't know the IP for A
27895 and we know that server B rejects most-but-not all connections to
27896 port 80, we would previously reject the connection. Now, we assume
27897 the user knows what they were asking for. Fixes bug 752. Bugfix
27898 on 0.0.9rc5. Diagnosed by BarkerJr.
27899 - If we overrun our per-second write limits a little, count this as
27900 having used up our write allocation for the second, and choke
27901 outgoing directory writes. Previously, we had only counted this when
27902 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
27903 Bugfix on 0.2.0.x (??).
27904 - Remove the old v2 directory authority 'lefkada' from the default
27905 list. It has been gone for many months.
27906 - Stop doing unaligned memory access that generated bus errors on
27907 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
27908 - Make USR2 log-level switch take effect immediately. Bugfix on
27911 o Minor bugfixes (controller):
27912 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
27913 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
27916 Changes in version 0.2.1.7-alpha - 2008-11-08
27917 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
27918 packages (and maybe other packages) noticed by Theo de Raadt, fixes
27919 a smaller security flaw that might allow an attacker to access local
27920 services, adds better defense against DNS poisoning attacks on exit
27921 relays, further improves hidden service performance, and fixes a
27922 variety of other issues.
27925 - The "ClientDNSRejectInternalAddresses" config option wasn't being
27926 consistently obeyed: if an exit relay refuses a stream because its
27927 exit policy doesn't allow it, we would remember what IP address
27928 the relay said the destination address resolves to, even if it's
27929 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
27930 - The "User" and "Group" config options did not clear the
27931 supplementary group entries for the Tor process. The "User" option
27932 is now more robust, and we now set the groups to the specified
27933 user's primary group. The "Group" option is now ignored. For more
27934 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
27935 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
27936 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
27937 - Do not use or believe expired v3 authority certificates. Patch
27938 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
27941 - Now NodeFamily and MyFamily config options allow spaces in
27942 identity fingerprints, so it's easier to paste them in.
27943 Suggested by Lucky Green.
27944 - Implement the 0x20 hack to better resist DNS poisoning: set the
27945 case on outgoing DNS requests randomly, and reject responses that do
27946 not match the case correctly. This logic can be disabled with the
27947 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
27948 of servers that do not reliably preserve case in replies. See
27949 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
27951 - Preserve case in replies to DNSPort requests in order to support
27952 the 0x20 hack for resisting DNS poisoning attacks.
27954 o Hidden service performance improvements:
27955 - When the client launches an introduction circuit, retry with a
27956 new circuit after 30 seconds rather than 60 seconds.
27957 - Launch a second client-side introduction circuit in parallel
27958 after a delay of 15 seconds (based on work by Christian Wilms).
27959 - Hidden services start out building five intro circuits rather
27960 than three, and when the first three finish they publish a service
27961 descriptor using those. Now we publish our service descriptor much
27962 faster after restart.
27965 - Minor fix in the warning messages when you're having problems
27966 bootstrapping; also, be more forgiving of bootstrap problems when
27967 we're still making incremental progress on a given bootstrap phase.
27968 - When we're choosing an exit node for a circuit, and we have
27969 no pending streams, choose a good general exit rather than one that
27970 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
27971 - Send a valid END cell back when a client tries to connect to a
27972 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
27973 840. Patch from rovv.
27974 - If a broken client asks a non-exit router to connect somewhere,
27975 do not even do the DNS lookup before rejecting the connection.
27976 Fixes another case of bug 619. Patch from rovv.
27977 - Fix another case of assuming, when a specific exit is requested,
27978 that we know more than the user about what hosts it allows.
27979 Fixes another case of bug 752. Patch from rovv.
27980 - Check which hops rendezvous stream cells are associated with to
27981 prevent possible guess-the-streamid injection attacks from
27982 intermediate hops. Fixes another case of bug 446. Based on patch
27984 - Avoid using a negative right-shift when comparing 32-bit
27985 addresses. Possible fix for bug 845 and bug 811.
27986 - Make the assert_circuit_ok() function work correctly on circuits that
27987 have already been marked for close.
27988 - Fix read-off-the-end-of-string error in unit tests when decoding
27989 introduction points.
27990 - Fix uninitialized size field for memory area allocation: may improve
27991 memory performance during directory parsing.
27992 - Treat duplicate certificate fetches as failures, so that we do
27993 not try to re-fetch an expired certificate over and over and over.
27994 - Do not say we're fetching a certificate when we'll in fact skip it
27995 because of a pending download.
27998 Changes in version 0.2.1.6-alpha - 2008-09-30
27999 Tor 0.2.1.6-alpha further improves performance and robustness of
28000 hidden services, starts work on supporting per-country relay selection,
28001 and fixes a variety of smaller issues.
28004 - Implement proposal 121: make it possible to build hidden services
28005 that only certain clients are allowed to connect to. This is
28006 enforced at several points, so that unauthorized clients are unable
28007 to send INTRODUCE cells to the service, or even (depending on the
28008 type of authentication) to learn introduction points. This feature
28009 raises the bar for certain kinds of active attacks against hidden
28010 services. Code by Karsten Loesing.
28011 - Relays now store and serve v2 hidden service descriptors by default,
28012 i.e., the new default value for HidServDirectoryV2 is 1. This is
28013 the last step in proposal 114, which aims to make hidden service
28014 lookups more reliable.
28015 - Start work to allow node restrictions to include country codes. The
28016 syntax to exclude nodes in a country with country code XX is
28017 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
28018 refinement to decide what config options should take priority if
28019 you ask to both use a particular node and exclude it.
28020 - Allow ExitNodes list to include IP ranges and country codes, just
28021 like the Exclude*Nodes lists. Patch from Robert Hogan.
28024 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
28025 Tor to fail to start if you had it configured to use a bridge
28026 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
28027 - When extending a circuit to a hidden service directory to upload a
28028 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28029 requests failed, because the router descriptor had not been
28030 downloaded yet. In these cases, we now wait until the router
28031 descriptor is downloaded, and then retry. Likewise, clients
28032 now skip over a hidden service directory if they don't yet have
28033 its router descriptor, rather than futilely requesting it and
28034 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
28036 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28037 we were failing the whole hidden service request when the v0
28038 descriptor fetch fails, even if the v2 fetch is still pending and
28039 might succeed. Similarly, if the last v2 fetch fails, we were
28040 failing the whole hidden service request even if a v0 fetch is
28041 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28042 - DNS replies need to have names matching their requests, but
28043 these names should be in the questions section, not necessarily
28044 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
28047 - Update to the "September 1 2008" ip-to-country file.
28048 - Allow ports 465 and 587 in the default exit policy again. We had
28049 rejected them in 0.1.0.15, because back in 2005 they were commonly
28050 misconfigured and ended up as spam targets. We hear they are better
28051 locked down these days.
28052 - Use a lockfile to make sure that two Tor processes are not
28053 simultaneously running with the same datadir.
28054 - Serve the latest v3 networkstatus consensus via the control
28055 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
28056 - Better logging about stability/reliability calculations on directory
28058 - Drop the requirement to have an open dir port for storing and
28059 serving v2 hidden service descriptors.
28060 - Directory authorities now serve a /tor/dbg-stability.txt URL to
28061 help debug WFU and MTBF calculations.
28062 - Implement most of Proposal 152: allow specialized servers to permit
28063 single-hop circuits, and clients to use those servers to build
28064 single-hop circuits when using a specialized controller. Patch
28065 from Josh Albrecht. Resolves feature request 768.
28066 - Add a -p option to tor-resolve for specifying the SOCKS port: some
28067 people find host:port too confusing.
28068 - Make TrackHostExit mappings expire a while after their last use, not
28069 after their creation. Patch from Robert Hogan.
28070 - Provide circuit purposes along with circuit events to the controller.
28073 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
28075 - Fixed some memory leaks -- some quite frequent, some almost
28076 impossible to trigger -- based on results from Coverity.
28077 - When testing for libevent functions, set the LDFLAGS variable
28078 correctly. Found by Riastradh.
28079 - Fix an assertion bug in parsing policy-related options; possible fix
28081 - Catch and report a few more bootstrapping failure cases when Tor
28082 fails to establish a TCP connection. Cleanup on 0.2.1.x.
28083 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
28084 bootstrapping with tunneled directory connections. Bugfix on
28085 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
28086 - When asked to connect to A.B.exit:80, if we don't know the IP for A
28087 and we know that server B rejects most-but-not all connections to
28088 port 80, we would previously reject the connection. Now, we assume
28089 the user knows what they were asking for. Fixes bug 752. Bugfix
28090 on 0.0.9rc5. Diagnosed by BarkerJr.
28091 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
28092 service directories if they have no advertised dir port. Bugfix
28094 - If we overrun our per-second write limits a little, count this as
28095 having used up our write allocation for the second, and choke
28096 outgoing directory writes. Previously, we had only counted this when
28097 we had met our limits precisely. Fixes bug 824. Patch by rovv.
28098 Bugfix on 0.2.0.x (??).
28099 - Avoid a "0 divided by 0" calculation when calculating router uptime
28100 at directory authorities. Bugfix on 0.2.0.8-alpha.
28101 - Make DNS resolved controller events into "CLOSED", not
28102 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
28104 - Fix a bug where an unreachable relay would establish enough
28105 reachability testing circuits to do a bandwidth test -- if
28106 we already have a connection to the middle hop of the testing
28107 circuit, then it could establish the last hop by using the existing
28108 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
28109 circuits no longer use entry guards in 0.2.1.3-alpha.
28110 - If we have correct permissions on $datadir, we complain to stdout
28111 and fail to start. But dangerous permissions on
28112 $datadir/cached-status/ would cause us to open a log and complain
28113 there. Now complain to stdout and fail to start in both cases. Fixes
28114 bug 820, reported by seeess.
28115 - Remove the old v2 directory authority 'lefkada' from the default
28116 list. It has been gone for many months.
28118 o Code simplifications and refactoring:
28119 - Revise the connection_new functions so that a more typesafe variant
28120 exists. This will work better with Coverity, and let us find any
28121 actual mistakes we're making here.
28122 - Refactor unit testing logic so that dmalloc can be used sensibly
28123 with unit tests to check for memory leaks.
28124 - Move all hidden-service related fields from connection and circuit
28125 structure to substructures: this way they won't eat so much memory.
28128 Changes in version 0.2.0.31 - 2008-09-03
28129 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
28130 a big bug we're seeing where in rare cases traffic from one Tor stream
28131 gets mixed into another stream, and fixes a variety of smaller issues.
28134 - Make sure that two circuits can never exist on the same connection
28135 with the same circuit ID, even if one is marked for close. This
28136 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
28137 - Relays now reject risky extend cells: if the extend cell includes
28138 a digest of all zeroes, or asks to extend back to the relay that
28139 sent the extend cell, tear down the circuit. Ideas suggested
28141 - If not enough of our entry guards are available so we add a new
28142 one, we might use the new one even if it overlapped with the
28143 current circuit's exit relay (or its family). Anonymity bugfix
28144 pointed out by rovv.
28147 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
28148 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
28149 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28150 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
28151 - Pick size of default geoip filename string correctly on windows.
28152 Fixes bug 806. Bugfix on 0.2.0.30.
28153 - Make the autoconf script accept the obsolete --with-ssl-dir
28154 option as an alias for the actually-working --with-openssl-dir
28155 option. Fix the help documentation to recommend --with-openssl-dir.
28156 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
28157 - When using the TransPort option on OpenBSD, and using the User
28158 option to change UID and drop privileges, make sure to open
28159 /dev/pf before dropping privileges. Fixes bug 782. Patch from
28160 Christopher Davis. Bugfix on 0.1.2.1-alpha.
28161 - Try to attach connections immediately upon receiving a RENDEZVOUS2
28162 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
28163 on the client side when connecting to a hidden service. Bugfix
28164 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
28165 - When closing an application-side connection because its circuit is
28166 getting torn down, generate the stream event correctly. Bugfix on
28167 0.1.2.x. Anonymous patch.
28170 Changes in version 0.2.1.5-alpha - 2008-08-31
28171 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
28172 in a lot of the infrastructure for adding authorization to hidden
28173 services, lays the groundwork for having clients read their load
28174 balancing information out of the networkstatus consensus rather than
28175 the individual router descriptors, addresses two potential anonymity
28176 issues, and fixes a variety of smaller issues.
28179 - Convert many internal address representations to optionally hold
28181 - Generate and accept IPv6 addresses in many protocol elements.
28182 - Make resolver code handle nameservers located at ipv6 addresses.
28183 - Begin implementation of proposal 121 ("Client authorization for
28184 hidden services"): configure hidden services with client
28185 authorization, publish descriptors for them, and configure
28186 authorization data for hidden services at clients. The next
28187 step is to actually access hidden services that perform client
28189 - More progress toward proposal 141: Network status consensus
28190 documents and votes now contain bandwidth information for each
28191 router and a summary of that router's exit policy. Eventually this
28192 will be used by clients so that they do not have to download every
28193 known descriptor before building circuits.
28195 o Major bugfixes (on 0.2.0.x and before):
28196 - When sending CREATED cells back for a given circuit, use a 64-bit
28197 connection ID to find the right connection, rather than an addr:port
28198 combination. Now that we can have multiple OR connections between
28199 the same ORs, it is no longer possible to use addr:port to uniquely
28200 identify a connection.
28201 - Relays now reject risky extend cells: if the extend cell includes
28202 a digest of all zeroes, or asks to extend back to the relay that
28203 sent the extend cell, tear down the circuit. Ideas suggested
28205 - If not enough of our entry guards are available so we add a new
28206 one, we might use the new one even if it overlapped with the
28207 current circuit's exit relay (or its family). Anonymity bugfix
28208 pointed out by rovv.
28211 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
28212 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
28213 - When using the TransPort option on OpenBSD, and using the User
28214 option to change UID and drop privileges, make sure to open /dev/pf
28215 before dropping privileges. Fixes bug 782. Patch from Christopher
28216 Davis. Bugfix on 0.1.2.1-alpha.
28217 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28218 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
28219 - Add a missing safe_str() call for a debug log message.
28220 - Use 64 bits instead of 32 bits for connection identifiers used with
28221 the controller protocol, to greatly reduce risk of identifier reuse.
28222 - Make the autoconf script accept the obsolete --with-ssl-dir
28223 option as an alias for the actually-working --with-openssl-dir
28224 option. Fix the help documentation to recommend --with-openssl-dir.
28225 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
28228 - Rate-limit too-many-sockets messages: when they happen, they happen
28229 a lot. Resolves bug 748.
28230 - Resist DNS poisoning a little better by making sure that names in
28231 answer sections match.
28232 - Print the SOCKS5 error message string as well as the error code
28233 when a tor-resolve request fails. Patch from Jacob.
28236 Changes in version 0.2.1.4-alpha - 2008-08-04
28237 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
28240 - The address part of exit policies was not correctly written
28241 to router descriptors. This generated router descriptors that failed
28242 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
28244 - Tor triggered a false assert when extending a circuit to a relay
28245 but we already have a connection open to that relay. Noticed by
28246 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
28249 - Fix a hidden service logging bug: in some edge cases, the router
28250 descriptor of a previously picked introduction point becomes
28251 obsolete and we need to give up on it rather than continually
28252 complaining that it has become obsolete. Observed by xiando. Bugfix
28255 o Removed features:
28256 - Take out the TestVia config option, since it was a workaround for
28257 a bug that was fixed in Tor 0.1.1.21.
28260 Changes in version 0.2.1.3-alpha - 2008-08-03
28261 Tor 0.2.1.3-alpha implements most of the pieces to prevent
28262 infinite-length circuit attacks (see proposal 110); fixes a bug that
28263 might cause exit relays to corrupt streams they send back; allows
28264 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
28265 ExcludeExitNodes config options; and fixes a big pile of bugs.
28267 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
28268 - Send a bootstrap problem "warn" event on the first problem if the
28269 reason is NO_ROUTE (that is, our network is down).
28272 - Implement most of proposal 110: The first K cells to be sent
28273 along a circuit are marked as special "early" cells; only K "early"
28274 cells will be allowed. Once this code is universal, we can block
28275 certain kinds of DOS attack by requiring that EXTEND commands must
28276 be sent using an "early" cell.
28279 - Try to attach connections immediately upon receiving a RENDEZVOUS2
28280 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
28281 on the client side when connecting to a hidden service. Bugfix
28282 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
28283 - Ensure that two circuits can never exist on the same connection
28284 with the same circuit ID, even if one is marked for close. This
28285 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
28288 - When relays do their initial bandwidth measurement, don't limit
28289 to just our entry guards for the test circuits. Otherwise we tend
28290 to have multiple test circuits going through a single entry guard,
28291 which makes our bandwidth test less accurate. Fixes part of bug 654;
28292 patch contributed by Josh Albrecht.
28293 - Add an ExcludeExitNodes option so users can list a set of nodes
28294 that should be be excluded from the exit node position, but
28295 allowed elsewhere. Implements proposal 151.
28296 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
28297 ExcludeNodes and ExcludeExitNodes lists.
28298 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
28299 be more efficient. Formerly it was quadratic in the number of
28300 servers; now it should be linear. Fixes bug 509.
28301 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
28302 and n_conn_id_digest fields into a separate structure that's
28303 only needed when the circuit has not yet attached to an n_conn.
28306 - Change the contrib/tor.logrotate script so it makes the new
28307 logs as "_tor:_tor" rather than the default, which is generally
28308 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
28309 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
28310 warnings (occasionally), but it can also cause the compiler to
28311 eliminate error-checking code. Suggested by Peter Gutmann.
28312 - When a hidden service is giving up on an introduction point candidate
28313 that was not included in the last published rendezvous descriptor,
28314 don't reschedule publication of the next descriptor. Fixes bug 763.
28316 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
28317 HiddenServiceExcludeNodes as obsolete: they never worked properly,
28318 and nobody claims to be using them. Fixes bug 754. Bugfix on
28319 0.1.0.1-rc. Patch from Christian Wilms.
28320 - Fix a small alignment and memory-wasting bug on buffer chunks.
28323 o Minor bugfixes (controller):
28324 - When closing an application-side connection because its circuit
28325 is getting torn down, generate the stream event correctly.
28326 Bugfix on 0.1.2.x. Anonymous patch.
28328 o Removed features:
28329 - Remove all backward-compatibility code to support relays running
28330 versions of Tor so old that they no longer work at all on the
28334 Changes in version 0.2.0.30 - 2008-07-15
28336 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
28337 warnings (occasionally), but it can also cause the compiler to
28338 eliminate error-checking code. Suggested by Peter Gutmann.
28341 Changes in version 0.2.0.29-rc - 2008-07-08
28342 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
28343 hidden-service performance bugs, and fixes a bunch of smaller bugs.
28346 - If you have more than one bridge but don't know their keys,
28347 you would only launch a request for the descriptor of the first one
28348 on your list. (Tor considered launching requests for the others, but
28349 found that it already had a connection on the way for $0000...0000
28350 so it didn't open another.) Bugfix on 0.2.0.x.
28351 - If you have more than one bridge but don't know their keys, and the
28352 connection to one of the bridges failed, you would cancel all
28353 pending bridge connections. (After all, they all have the same
28354 digest.) Bugfix on 0.2.0.x.
28355 - When a hidden service was trying to establish an introduction point,
28356 and Tor had built circuits preemptively for such purposes, we
28357 were ignoring all the preemptive circuits and launching a new one
28358 instead. Bugfix on 0.2.0.14-alpha.
28359 - When a hidden service was trying to establish an introduction point,
28360 and Tor *did* manage to reuse one of the preemptively built
28361 circuits, it didn't correctly remember which one it used,
28362 so it asked for another one soon after, until there were no
28363 more preemptive circuits, at which point it launched one from
28364 scratch. Bugfix on 0.0.9.x.
28365 - Make directory servers include the X-Your-Address-Is: http header in
28366 their responses even for begin_dir conns. Now clients who only
28367 ever use begin_dir connections still have a way to learn their IP
28368 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
28371 - Fix a macro/CPP interaction that was confusing some compilers:
28372 some GCCs don't like #if/#endif pairs inside macro arguments.
28374 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
28375 Fixes bug 704; fix from Steven Murdoch.
28376 - When opening /dev/null in finish_daemonize(), do not pass the
28377 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
28378 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
28379 - Correctly detect transparent proxy support on Linux hosts that
28380 require in.h to be included before netfilter_ipv4.h. Patch
28382 - Disallow session resumption attempts during the renegotiation
28383 stage of the v2 handshake protocol. Clients should never be trying
28384 session resumption at this point, but apparently some did, in
28385 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
28386 found by Geoff Goodell.
28389 Changes in version 0.2.1.2-alpha - 2008-06-20
28390 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
28391 make it easier to set up your own private Tor network; fixes several
28392 big bugs with using more than one bridge relay; fixes a big bug with
28393 offering hidden services quickly after Tor starts; and uses a better
28394 API for reporting potential bootstrapping problems to the controller.
28397 - New TestingTorNetwork config option to allow adjustment of
28398 previously constant values that, while reasonable, could slow
28399 bootstrapping. Implements proposal 135. Patch from Karsten.
28402 - If you have more than one bridge but don't know their digests,
28403 you would only learn a request for the descriptor of the first one
28404 on your list. (Tor considered launching requests for the others, but
28405 found that it already had a connection on the way for $0000...0000
28406 so it didn't open another.) Bugfix on 0.2.0.x.
28407 - If you have more than one bridge but don't know their digests,
28408 and the connection to one of the bridges failed, you would cancel
28409 all pending bridge connections. (After all, they all have the
28410 same digest.) Bugfix on 0.2.0.x.
28411 - When establishing a hidden service, introduction points that
28412 originate from cannibalized circuits are completely ignored and not
28413 included in rendezvous service descriptors. This might be another
28414 reason for delay in making a hidden service available. Bugfix
28415 from long ago (0.0.9.x?)
28418 - Allow OpenSSL to use dynamic locks if it wants.
28419 - When building a consensus, do not include routers that are down.
28420 This will cut down 30% to 40% on consensus size. Implements
28422 - In directory authorities' approved-routers files, allow
28423 fingerprints with or without space.
28424 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
28425 controller can query our current bootstrap state in case it attaches
28426 partway through and wants to catch up.
28427 - Send an initial "Starting" bootstrap status event, so we have a
28428 state to start out in.
28431 - Asking for a conditional consensus at .../consensus/<fingerprints>
28432 would crash a dirserver if it did not already have a
28433 consensus. Bugfix on 0.2.1.1-alpha.
28434 - Clean up some macro/CPP interactions: some GCC versions don't like
28435 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
28438 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
28439 - Directory authorities shouldn't complain about bootstrapping
28440 problems just because they do a lot of reachability testing and
28441 some of the connection attempts fail.
28442 - Start sending "count" and "recommendation" key/value pairs in
28443 bootstrap problem status events, so the controller can hear about
28444 problems even before Tor decides they're worth reporting for sure.
28445 - If you're using bridges, generate "bootstrap problem" warnings
28446 as soon as you run out of working bridges, rather than waiting
28447 for ten failures -- which will never happen if you have less than
28449 - If we close our OR connection because there's been a circuit
28450 pending on it for too long, we were telling our bootstrap status
28451 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
28454 Changes in version 0.2.1.1-alpha - 2008-06-13
28455 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
28456 were making the Tor process bloat especially on Linux; makes our TLS
28457 handshake blend in better; sends "bootstrap phase" status events to
28458 the controller, so it can keep the user informed of progress (and
28459 problems) fetching directory information and establishing circuits;
28460 and adds a variety of smaller features.
28463 - More work on making our TLS handshake blend in: modify the list
28464 of ciphers advertised by OpenSSL in client mode to even more
28465 closely resemble a common web browser. We cheat a little so that
28466 we can advertise ciphers that the locally installed OpenSSL doesn't
28468 - Start sending "bootstrap phase" status events to the controller,
28469 so it can keep the user informed of progress fetching directory
28470 information and establishing circuits. Also inform the controller
28471 if we think we're stuck at a particular bootstrap phase. Implements
28473 - Resume using OpenSSL's RAND_poll() for better (and more portable)
28474 cross-platform entropy collection again. We used to use it, then
28475 stopped using it because of a bug that could crash systems that
28476 called RAND_poll when they had a lot of fds open. It looks like the
28477 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
28478 at startup, and to call RAND_poll() when we reseed later only if
28479 we have a non-buggy OpenSSL version.
28482 - When we choose to abandon a new entry guard because we think our
28483 older ones might be better, close any circuits pending on that
28484 new entry guard connection. This fix should make us recover much
28485 faster when our network is down and then comes back. Bugfix on
28486 0.1.2.8-beta; found by lodger.
28488 o Memory fixes and improvements:
28489 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
28490 to avoid unused RAM in buffer chunks and memory pools.
28491 - Speed up parsing and cut down on memory fragmentation by using
28492 stack-style allocations for parsing directory objects. Previously,
28493 this accounted for over 40% of allocations from within Tor's code
28494 on a typical directory cache.
28495 - Use a Bloom filter rather than a digest-based set to track which
28496 descriptors we need to keep around when we're cleaning out old
28497 router descriptors. This speeds up the computation significantly,
28498 and may reduce fragmentation.
28499 - Reduce the default smartlist size from 32 to 16; it turns out that
28500 most smartlists hold around 8-12 elements tops.
28501 - Make dumpstats() log the fullness and size of openssl-internal
28503 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
28504 patch to their OpenSSL, turn it on to save memory on servers. This
28505 patch will (with any luck) get included in a mainline distribution
28507 - Never use OpenSSL compression: it wastes RAM and CPU trying to
28508 compress cells, which are basically all encrypted, compressed,
28512 - Stop reloading the router list from disk for no reason when we
28513 run out of reachable directory mirrors. Once upon a time reloading
28514 it would set the 'is_running' flag back to 1 for them. It hasn't
28515 done that for a long time.
28516 - In very rare situations new hidden service descriptors were
28517 published earlier than 30 seconds after the last change to the
28518 service. (We currently think that a hidden service descriptor
28519 that's been stable for 30 seconds is worth publishing.)
28522 - Allow separate log levels to be configured for different logging
28523 domains. For example, this allows one to log all notices, warnings,
28524 or errors, plus all memory management messages of level debug or
28525 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
28526 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
28527 and stop using a warning that had become unfixably verbose under
28529 - New --hush command-line option similar to --quiet. While --quiet
28530 disables all logging to the console on startup, --hush limits the
28531 output to messages of warning and error severity.
28532 - Servers support a new URL scheme for consensus downloads that
28533 allows the client to specify which authorities are trusted.
28534 The server then only sends the consensus if the client will trust
28535 it. Otherwise a 404 error is sent back. Clients use this
28536 new scheme when the server supports it (meaning it's running
28537 0.2.1.1-alpha or later). Implements proposal 134.
28538 - New configure/torrc options (--enable-geoip-stats,
28539 DirRecordUsageByCountry) to record how many IPs we've served
28540 directory info to in each country code, how many status documents
28541 total we've sent to each country code, and what share of the total
28542 directory requests we should expect to see.
28543 - Use the TLS1 hostname extension to more closely resemble browser
28545 - Lots of new unit tests.
28546 - Add a macro to implement the common pattern of iterating through
28547 two parallel lists in lockstep.
28550 Changes in version 0.2.0.28-rc - 2008-06-13
28551 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
28552 performance bug, and fixes a bunch of smaller bugs.
28555 - Fix a bug where, when we were choosing the 'end stream reason' to
28556 put in our relay end cell that we send to the exit relay, Tor
28557 clients on Windows were sometimes sending the wrong 'reason'. The
28558 anonymity problem is that exit relays may be able to guess whether
28559 the client is running Windows, thus helping partition the anonymity
28560 set. Down the road we should stop sending reasons to exit relays,
28561 or otherwise prevent future versions of this bug.
28564 - While setting up a hidden service, some valid introduction circuits
28565 were overlooked and abandoned. This might be the reason for
28566 the long delay in making a hidden service available. Bugfix on
28570 - Update to the "June 9 2008" ip-to-country file.
28571 - Run 'make test' as part of 'make dist', so we stop releasing so
28572 many development snapshots that fail their unit tests.
28575 - When we're checking if we have enough dir info for each relay
28576 to begin establishing circuits, make sure that we actually have
28577 the descriptor listed in the consensus, not just any descriptor.
28579 - Bridge relays no longer print "xx=0" in their extrainfo document
28580 for every single country code in the geoip db. Bugfix on
28582 - Only warn when we fail to load the geoip file if we were planning to
28583 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
28584 - If we change our MaxAdvertisedBandwidth and then reload torrc,
28585 Tor won't realize it should publish a new relay descriptor. Fixes
28586 bug 688, reported by mfr. Bugfix on 0.1.2.x.
28587 - When we haven't had any application requests lately, don't bother
28588 logging that we have expired a bunch of descriptors. Bugfix
28590 - Make relay cells written on a connection count as non-padding when
28591 tracking how long a connection has been in use. Bugfix on
28592 0.2.0.1-alpha. Spotted by lodger.
28593 - Fix unit tests in 0.2.0.27-rc.
28594 - Fix compile on Windows.
28597 Changes in version 0.2.0.27-rc - 2008-06-03
28598 Tor 0.2.0.27-rc adds a few features we left out of the earlier
28599 release candidates. In particular, we now include an IP-to-country
28600 GeoIP database, so controllers can easily look up what country a
28601 given relay is in, and so bridge relays can give us some sanitized
28602 summaries about which countries are making use of bridges. (See proposal
28603 126-geoip-fetching.txt for details.)
28606 - Include an IP-to-country GeoIP file in the tarball, so bridge
28607 relays can report sanitized summaries of the usage they're seeing.
28610 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
28611 Robert Hogan. Fixes the first part of bug 681.
28612 - Make bridge authorities never serve extrainfo docs.
28613 - Add support to detect Libevent versions in the 1.4.x series
28615 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
28616 - Include a new contrib/tor-exit-notice.html file that exit relay
28617 operators can put on their website to help reduce abuse queries.
28620 - When tunneling an encrypted directory connection, and its first
28621 circuit fails, do not leave it unattached and ask the controller
28622 to deal. Fixes the second part of bug 681.
28623 - Make bridge authorities correctly expire old extrainfo documents
28627 Changes in version 0.2.0.26-rc - 2008-05-13
28628 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
28629 in Debian's OpenSSL packages. All users running any 0.2.0.x version
28630 should upgrade, whether they're running Debian or not.
28632 o Major security fixes:
28633 - Use new V3 directory authority keys on the tor26, gabelmoo, and
28634 moria1 V3 directory authorities. The old keys were generated with
28635 a vulnerable version of Debian's OpenSSL package, and must be
28636 considered compromised. Other authorities' keys were not generated
28637 with an affected version of OpenSSL.
28640 - List authority signatures as "unrecognized" based on DirServer
28641 lines, not on cert cache. Bugfix on 0.2.0.x.
28644 - Add a new V3AuthUseLegacyKey option to make it easier for
28645 authorities to change their identity keys if they have to.
28648 Changes in version 0.2.0.25-rc - 2008-04-23
28649 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
28652 - Remember to initialize threading before initializing logging.
28653 Otherwise, many BSD-family implementations will crash hard on
28654 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
28657 - Authorities correctly free policies on bad servers on
28658 exit. Fixes bug 672. Bugfix on 0.2.0.x.
28661 Changes in version 0.2.0.24-rc - 2008-04-22
28662 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
28663 v3 directory authority, makes relays with dynamic IP addresses and no
28664 DirPort notice more quickly when their IP address changes, fixes a few
28665 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
28667 o New directory authorities:
28668 - Take lefkada out of the list of v3 directory authorities, since
28669 it has been down for months.
28670 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
28674 - Detect address changes more quickly on non-directory mirror
28675 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
28677 o Minor features (security):
28678 - Reject requests for reverse-dns lookup of names that are in
28679 a private address space. Patch from lodger.
28680 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
28683 o Minor bugfixes (crashes):
28684 - Avoid a rare assert that can trigger when Tor doesn't have much
28685 directory information yet and it tries to fetch a v2 hidden
28686 service descriptor. Fixes bug 651, reported by nwf.
28687 - Initialize log mutex before initializing dmalloc. Otherwise,
28688 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
28689 - Use recursive pthread mutexes in order to avoid deadlock when
28690 logging debug-level messages to a controller. Bug spotted by nwf,
28691 bugfix on 0.2.0.16-alpha.
28693 o Minor bugfixes (resource management):
28694 - Keep address policies from leaking memory: start their refcount
28695 at 1, not 2. Bugfix on 0.2.0.16-alpha.
28696 - Free authority certificates on exit, so they don't look like memory
28697 leaks. Bugfix on 0.2.0.19-alpha.
28698 - Free static hashtables for policy maps and for TLS connections on
28699 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
28700 - Avoid allocating extra space when computing consensuses on 64-bit
28701 platforms. Bug spotted by aakova.
28703 o Minor bugfixes (misc):
28704 - Do not read the configuration file when we've only been told to
28705 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
28706 based on patch from Sebastian Hahn.
28707 - Exit relays that are used as a client can now reach themselves
28708 using the .exit notation, rather than just launching an infinite
28709 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
28710 - When attempting to open a logfile fails, tell us why.
28711 - Fix a dumb bug that was preventing us from knowing that we should
28712 preemptively build circuits to handle expected directory requests.
28713 Fixes bug 660. Bugfix on 0.1.2.x.
28714 - Warn less verbosely about clock skew from netinfo cells from
28715 untrusted sources. Fixes bug 663.
28716 - Make controller stream events for DNS requests more consistent,
28717 by adding "new stream" events for DNS requests, and removing
28718 spurious "stream closed" events" for cached reverse resolves.
28719 Patch from mwenge. Fixes bug 646.
28720 - Correctly notify one-hop connections when a circuit build has
28721 failed. Possible fix for bug 669. Found by lodger.
28724 Changes in version 0.2.0.23-rc - 2008-03-24
28725 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
28726 makes bootstrapping faster if the first directory mirror you contact
28727 is down. The bundles also include the new Vidalia 0.1.2 release.
28730 - When a tunneled directory request is made to a directory server
28731 that's down, notice after 30 seconds rather than 120 seconds. Also,
28732 fail any begindir streams that are pending on it, so they can
28733 retry elsewhere. This was causing multi-minute delays on bootstrap.
28736 Changes in version 0.2.0.22-rc - 2008-03-18
28737 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
28738 enables encrypted directory connections by default for non-relays, fixes
28739 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
28740 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
28743 - Enable encrypted directory connections by default for non-relays,
28744 so censor tools that block Tor directory connections based on their
28745 plaintext patterns will no longer work. This means Tor works in
28746 certain censored countries by default again.
28749 - Make sure servers always request certificates from clients during
28750 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
28751 - Do not enter a CPU-eating loop when a connection is closed in
28752 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
28753 diagnosed by lodger; bugfix on 0.2.0.20-rc.
28754 - Fix assertion failure that could occur when a blocked circuit
28755 became unblocked, and it had pending client DNS requests. Bugfix
28756 on 0.2.0.1-alpha. Fixes bug 632.
28758 o Minor bugfixes (on 0.1.2.x):
28759 - Generate "STATUS_SERVER" events rather than misspelled
28760 "STATUS_SEVER" events. Caught by mwenge.
28761 - When counting the number of bytes written on a TLS connection,
28762 look at the BIO actually used for writing to the network, not
28763 at the BIO used (sometimes) to buffer data for the network.
28764 Looking at different BIOs could result in write counts on the
28765 order of ULONG_MAX. Fixes bug 614.
28766 - On Windows, correctly detect errors when listing the contents of
28767 a directory. Fix from lodger.
28769 o Minor bugfixes (on 0.2.0.x):
28770 - Downgrade "sslv3 alert handshake failure" message to INFO.
28771 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
28772 left BandwidthRate and BandwidthBurst at the default, we would be
28773 silently limited by those defaults. Now raise them to match the
28774 RelayBandwidth* values.
28775 - Fix the SVK version detection logic to work correctly on a branch.
28776 - Make --enable-openbsd-malloc work correctly on Linux with alpha
28777 CPUs. Fixes bug 625.
28778 - Logging functions now check that the passed severity is sane.
28779 - Use proper log levels in the testsuite call of
28780 get_interface_address6().
28781 - When using a nonstandard malloc, do not use the platform values for
28782 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
28783 - Make the openbsd malloc code use 8k pages on alpha CPUs and
28785 - Detect mismatched page sizes when using --enable-openbsd-malloc.
28786 - Avoid double-marked-for-close warning when certain kinds of invalid
28787 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
28788 for bug 617. Bugfix on 0.2.0.1-alpha.
28789 - Make sure that the "NULL-means-reject *:*" convention is followed by
28790 all the policy manipulation functions, avoiding some possible crash
28791 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
28792 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
28793 actually works, and doesn't warn about every single reverse lookup.
28794 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
28797 - Only log guard node status when guard node status has changed.
28798 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
28799 make "INFO" 75% less verbose.
28802 Changes in version 0.2.0.21-rc - 2008-03-02
28803 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
28804 makes Tor work well with Vidalia again, fixes a rare assert bug,
28805 and fixes a pair of more minor bugs. The bundles also include Vidalia
28806 0.1.0 and Torbutton 1.1.16.
28809 - The control port should declare that it requires password auth
28810 when HashedControlSessionPassword is set too. Patch from Matt Edman;
28811 bugfix on 0.2.0.20-rc. Fixes bug 615.
28812 - Downgrade assert in connection_buckets_decrement() to a log message.
28813 This may help us solve bug 614, and in any case will make its
28814 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
28815 - We were sometimes miscounting the number of bytes read from the
28816 network, causing our rate limiting to not be followed exactly.
28817 Bugfix on 0.2.0.16-alpha. Reported by lodger.
28820 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
28821 OpenSSL versions should have been working fine. Diagnosis and patch
28822 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
28823 Bugfix on 0.2.0.20-rc.
28826 Changes in version 0.2.0.20-rc - 2008-02-24
28827 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
28828 makes more progress towards normalizing Tor's TLS handshake, makes
28829 hidden services work better again, helps relays bootstrap if they don't
28830 know their IP address, adds optional support for linking in openbsd's
28831 allocator or tcmalloc, allows really fast relays to scale past 15000
28832 sockets, and fixes a bunch of minor bugs reported by Veracode.
28835 - Enable the revised TLS handshake based on the one designed by
28836 Steven Murdoch in proposal 124, as revised in proposal 130. It
28837 includes version negotiation for OR connections as described in
28838 proposal 105. The new handshake is meant to be harder for censors
28839 to fingerprint, and it adds the ability to detect certain kinds of
28840 man-in-the-middle traffic analysis attacks. The version negotiation
28841 feature will allow us to improve Tor's link protocol more safely
28843 - Choose which bridge to use proportional to its advertised bandwidth,
28844 rather than uniformly at random. This should speed up Tor for
28845 bridge users. Also do this for people who set StrictEntryNodes.
28846 - When a TrackHostExits-chosen exit fails too many times in a row,
28847 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
28850 - Resolved problems with (re-)fetching hidden service descriptors.
28851 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
28852 and 0.2.0.19-alpha.
28853 - If we only ever used Tor for hidden service lookups or posts, we
28854 would stop building circuits and start refusing connections after
28855 24 hours, since we falsely believed that Tor was dormant. Reported
28856 by nwf; bugfix on 0.1.2.x.
28857 - Servers that don't know their own IP address should go to the
28858 authorities for their first directory fetch, even if their DirPort
28859 is off or if they don't know they're reachable yet. This will help
28860 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
28861 - When counting the number of open sockets, count not only the number
28862 of sockets we have received from the socket() call, but also
28863 the number we've gotten from accept() and socketpair(). This bug
28864 made us fail to count all sockets that we were using for incoming
28865 connections. Bugfix on 0.2.0.x.
28866 - Fix code used to find strings within buffers, when those strings
28867 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
28868 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
28869 - Add a new __HashedControlSessionPassword option for controllers
28870 to use for one-off session password hashes that shouldn't get
28871 saved to disk by SAVECONF --- Vidalia users were accumulating a
28872 pile of HashedControlPassword lines in their torrc files, one for
28873 each time they had restarted Tor and then clicked Save. Make Tor
28874 automatically convert "HashedControlPassword" to this new option but
28875 only when it's given on the command line. Partial fix for bug 586.
28877 o Minor features (performance):
28878 - Tune parameters for cell pool allocation to minimize amount of
28880 - Add OpenBSD malloc code from phk as an optional malloc
28881 replacement on Linux: some glibc libraries do very poorly
28882 with Tor's memory allocation patterns. Pass
28883 --enable-openbsd-malloc to get the replacement malloc code.
28884 - Add a --with-tcmalloc option to the configure script to link
28885 against tcmalloc (if present). Does not yet search for
28886 non-system include paths.
28887 - Stop imposing an arbitrary maximum on the number of file descriptors
28888 used for busy servers. Bug reported by Olaf Selke; patch from
28891 o Minor features (other):
28892 - When SafeLogging is disabled, log addresses along with all TLS
28894 - When building with --enable-gcc-warnings, check for whether Apple's
28895 warning "-Wshorten-64-to-32" is available.
28896 - Add a --passphrase-fd argument to the tor-gencert command for
28899 o Minor bugfixes (memory leaks and code problems):
28900 - We were leaking a file descriptor if Tor started with a zero-length
28901 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
28902 - Detect size overflow in zlib code. Reported by Justin Ferguson and
28904 - We were comparing the raw BridgePassword entry with a base64'ed
28905 version of it, when handling a "/tor/networkstatus-bridges"
28906 directory request. Now compare correctly. Noticed by Veracode.
28907 - Recover from bad tracked-since value in MTBF-history file.
28908 Should fix bug 537.
28909 - Alter the code that tries to recover from unhandled write
28910 errors, to not try to flush onto a socket that's given us
28911 unhandled errors. Bugfix on 0.1.2.x.
28912 - Make Unix controlsockets work correctly on OpenBSD. Patch from
28913 tup. Bugfix on 0.2.0.3-alpha.
28915 o Minor bugfixes (other):
28916 - If we have an extra-info document for our server, always make
28917 it available on the control port, even if we haven't gotten
28918 a copy of it from an authority yet. Patch from mwenge.
28919 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
28920 - Directory mirrors no longer include a guess at the client's IP
28921 address if the connection appears to be coming from the same /24
28922 network; it was producing too many wrong guesses.
28923 - Make the new hidden service code respect the SafeLogging setting.
28924 Bugfix on 0.2.0.x. Patch from Karsten.
28925 - When starting as an authority, do not overwrite all certificates
28926 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
28927 - If we're trying to flush the last bytes on a connection (for
28928 example, when answering a directory request), reset the
28929 time-to-give-up timeout every time we manage to write something
28930 on the socket. Bugfix on 0.1.2.x.
28931 - Change the behavior of "getinfo status/good-server-descriptor"
28932 so it doesn't return failure when any authority disappears.
28933 - Even though the man page said that "TrackHostExits ." should
28934 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
28935 - Report TLS "zero return" case as a "clean close" and "IO error"
28936 as a "close". Stop calling closes "unexpected closes": existing
28937 Tors don't use SSL_close(), so having a connection close without
28938 the TLS shutdown handshake is hardly unexpected.
28939 - Send NAMESERVER_STATUS messages for a single failed nameserver
28942 o Code simplifications and refactoring:
28943 - Remove the tor_strpartition function: its logic was confused,
28944 and it was only used for one thing that could be implemented far
28948 Changes in version 0.2.0.19-alpha - 2008-02-09
28949 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
28950 handshake, makes path selection for relays more secure and IP address
28951 guessing more robust, and generally fixes a lot of bugs in preparation
28952 for calling the 0.2.0 branch stable.
28955 - Do not include recognizeable strings in the commonname part of
28956 Tor's x509 certificates.
28959 - If we're a relay, avoid picking ourselves as an introduction point,
28960 a rendezvous point, or as the final hop for internal circuits. Bug
28961 reported by taranis and lodger. Bugfix on 0.1.2.x.
28962 - Patch from "Andrew S. Lists" to catch when we contact a directory
28963 mirror at IP address X and he says we look like we're coming from
28964 IP address X. Bugfix on 0.1.2.x.
28966 o Minor features (security):
28967 - Be more paranoid about overwriting sensitive memory on free(),
28968 as a defensive programming tactic to ensure forward secrecy.
28970 o Minor features (directory authority):
28971 - Actually validate the options passed to AuthDirReject,
28972 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
28973 - Reject router descriptors with out-of-range bandwidthcapacity or
28974 bandwidthburst values.
28976 o Minor features (controller):
28977 - Reject controller commands over 1MB in length. This keeps rogue
28978 processes from running us out of memory.
28980 o Minor features (misc):
28981 - Give more descriptive well-formedness errors for out-of-range
28982 hidden service descriptor/protocol versions.
28983 - Make memory debugging information describe more about history
28984 of cell allocation, so we can help reduce our memory use.
28986 o Deprecated features (controller):
28987 - The status/version/num-versioning and status/version/num-concurring
28988 GETINFO options are no longer useful in the v3 directory protocol:
28989 treat them as deprecated, and warn when they're used.
28992 - When our consensus networkstatus has been expired for a while, stop
28993 being willing to build circuits using it. Fixes bug 401. Bugfix
28995 - Directory caches now fetch certificates from all authorities
28996 listed in a networkstatus consensus, even when they do not
28997 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
28998 - When connecting to a bridge without specifying its key, insert
28999 the connection into the identity-to-connection map as soon as
29000 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
29001 - Detect versions of OS X where malloc_good_size() is present in the
29002 library but never actually declared. Resolves bug 587. Bugfix
29004 - Stop incorrectly truncating zlib responses to directory authority
29005 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
29006 - Stop recommending that every server operator send mail to tor-ops.
29007 Resolves bug 597. Bugfix on 0.1.2.x.
29008 - Don't trigger an assert if we start a directory authority with a
29009 private IP address (like 127.0.0.1).
29010 - Avoid possible failures when generating a directory with routers
29011 with over-long versions strings, or too many flags set. Bugfix
29013 - If an attempt to launch a DNS resolve request over the control
29014 port fails because we have overrun the limit on the number of
29015 connections, tell the controller that the request has failed.
29016 - Avoid using too little bandwidth when our clock skips a few
29017 seconds. Bugfix on 0.1.2.x.
29018 - Fix shell error when warning about missing packages in configure
29019 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
29020 - Do not become confused when receiving a spurious VERSIONS-like
29021 cell from a confused v1 client. Bugfix on 0.2.0.x.
29022 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
29023 introduction points for a hidden service have failed. Patch from
29024 Karsten Loesing. Bugfix on 0.2.0.x.
29026 o Code simplifications and refactoring:
29027 - Remove some needless generality from cpuworker code, for improved
29029 - Stop overloading the circuit_t.onionskin field for both "onionskin
29030 from a CREATE cell that we are waiting for a cpuworker to be
29031 assigned" and "onionskin from an EXTEND cell that we are going to
29032 send to an OR as soon as we are connected". Might help with bug 600.
29033 - Add an in-place version of aes_crypt() so that we can avoid doing a
29034 needless memcpy() call on each cell payload.
29037 Changes in version 0.2.0.18-alpha - 2008-01-25
29038 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
29039 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
29040 that can warn or reject connections to ports generally associated with
29041 vulnerable-plaintext protocols.
29043 o New directory authorities:
29044 - Set up dannenberg (run by CCC) as the sixth v3 directory
29048 - Fix a major memory leak when attempting to use the v2 TLS
29049 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
29050 - We accidentally enabled the under-development v2 TLS handshake
29051 code, which was causing log entries like "TLS error while
29052 renegotiating handshake". Disable it again. Resolves bug 590.
29053 - We were computing the wrong Content-Length: header for directory
29054 responses that need to be compressed on the fly, causing clients
29055 asking for those items to always fail. Bugfix on 0.2.0.x; partially
29059 - Avoid going directly to the directory authorities even if you're a
29060 relay, if you haven't found yourself reachable yet or if you've
29061 decided not to advertise your dirport yet. Addresses bug 556.
29062 - If we've gone 12 hours since our last bandwidth check, and we
29063 estimate we have less than 50KB bandwidth capacity but we could
29064 handle more, do another bandwidth test.
29065 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
29066 Tor can warn and/or refuse connections to ports commonly used with
29067 vulnerable-plaintext protocols. Currently we warn on ports 23,
29068 109, 110, and 143, but we don't reject any.
29071 - When we setconf ClientOnly to 1, close any current OR and Dir
29072 listeners. Reported by mwenge.
29073 - When we get a consensus that's been signed by more people than
29074 we expect, don't log about it; it's not a big deal. Reported
29078 - Don't answer "/tor/networkstatus-bridges" directory requests if
29079 the request isn't encrypted.
29080 - Make "ClientOnly 1" config option disable directory ports too.
29081 - Patches from Karsten Loesing to make v2 hidden services more
29082 robust: work even when there aren't enough HSDir relays available;
29083 retry when a v2 rend desc fetch fails; but don't retry if we
29084 already have a usable v0 rend desc.
29087 Changes in version 0.2.0.17-alpha - 2008-01-17
29088 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
29091 - Make the tor-gencert man page get included correctly in the tarball.
29094 Changes in version 0.2.0.16-alpha - 2008-01-17
29095 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
29096 Loesing, and generally cleans up a lot of features and minor bugs.
29098 o New directory authorities:
29099 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
29102 o Major performance improvements:
29103 - Switch our old ring buffer implementation for one more like that
29104 used by free Unix kernels. The wasted space in a buffer with 1mb
29105 of data will now be more like 8k than 1mb. The new implementation
29106 also avoids realloc();realloc(); patterns that can contribute to
29107 memory fragmentation.
29110 - Configuration files now accept C-style strings as values. This
29111 helps encode characters not allowed in the current configuration
29112 file format, such as newline or #. Addresses bug 557.
29113 - Although we fixed bug 539 (where servers would send HTTP status 503
29114 responses _and_ send a body too), there are still servers out
29115 there that haven't upgraded. Therefore, make clients parse such
29116 bodies when they receive them.
29117 - When we're not serving v2 directory information, there is no reason
29118 to actually keep any around. Remove the obsolete files and directory
29119 on startup if they are very old and we aren't going to serve them.
29121 o Minor performance improvements:
29122 - Reference-count and share copies of address policy entries; only 5%
29123 of them were actually distinct.
29124 - Never walk through the list of logs if we know that no log is
29125 interested in a given message.
29128 - When an authority has not signed a consensus, do not try to
29129 download a nonexistent "certificate with key 00000000". Bugfix
29130 on 0.2.0.x. Fixes bug 569.
29131 - Fix a rare assert error when we're closing one of our threads:
29132 use a mutex to protect the list of logs, so we never write to the
29133 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
29134 bug 575, which is kind of the revenge of bug 222.
29135 - Patch from Karsten Loesing to complain less at both the client
29136 and the relay when a relay used to have the HSDir flag but doesn't
29137 anymore, and we try to upload a hidden service descriptor.
29138 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
29140 - Do not try to download missing certificates until we have tried
29141 to check our fallback consensus. Fixes bug 583.
29142 - Make bridges round reported GeoIP stats info up to the nearest
29143 estimate, not down. Now we can distinguish between "0 people from
29144 this country" and "1 person from this country".
29145 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
29146 - Avoid possible segfault if key generation fails in
29147 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
29148 - Avoid segfault in the case where a badly behaved v2 versioning
29149 directory sends a signed networkstatus with missing client-versions.
29151 - Avoid segfaults on certain complex invocations of
29152 router_get_by_hexdigest(). Bugfix on 0.1.2.
29153 - Correct bad index on array access in parse_http_time(). Bugfix
29155 - Fix possible bug in vote generation when server versions are present
29156 but client versions are not.
29157 - Fix rare bug on REDIRECTSTREAM control command when called with no
29158 port set: it could erroneously report an error when none had
29160 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
29161 compressing large objects and find ourselves with more than 4k
29162 left over. Bugfix on 0.2.0.
29163 - Fix a small memory leak when setting up a hidden service.
29164 - Fix a few memory leaks that could in theory happen under bizarre
29166 - Fix an assert if we post a general-purpose descriptor via the
29167 control port but that descriptor isn't mentioned in our current
29168 network consensus. Bug reported by Jon McLachlan; bugfix on
29171 o Minor features (controller):
29172 - Get NS events working again. Patch from tup.
29173 - The GETCONF command now escapes and quotes configuration values
29174 that don't otherwise fit into the torrc file.
29175 - The SETCONF command now handles quoted values correctly.
29177 o Minor features (directory authorities):
29178 - New configuration options to override default maximum number of
29179 servers allowed on a single IP address. This is important for
29180 running a test network on a single host.
29181 - Actually implement the -s option to tor-gencert.
29182 - Add a manual page for tor-gencert.
29184 o Minor features (bridges):
29185 - Bridge authorities no longer serve bridge descriptors over
29186 unencrypted connections.
29188 o Minor features (other):
29189 - Add hidden services and DNSPorts to the list of things that make
29190 Tor accept that it has running ports. Change starting Tor with no
29191 ports from a fatal error to a warning; we might change it back if
29192 this turns out to confuse anybody. Fixes bug 579.
29195 Changes in version 0.1.2.19 - 2008-01-17
29196 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
29197 exit policy a little bit more conservative so it's safer to run an
29198 exit relay on a home system, and fixes a variety of smaller issues.
29201 - Exit policies now reject connections that are addressed to a
29202 relay's public (external) IP address too, unless
29203 ExitPolicyRejectPrivate is turned off. We do this because too
29204 many relays are running nearby to services that trust them based
29205 on network address.
29208 - When the clock jumps forward a lot, do not allow the bandwidth
29209 buckets to become negative. Fixes bug 544.
29210 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
29211 on every successful resolve. Reported by Mike Perry.
29212 - Purge old entries from the "rephist" database and the hidden
29213 service descriptor database even when DirPort is zero.
29214 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
29215 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
29216 crashing or mis-answering these requests.
29217 - When we decide to send a 503 response to a request for servers, do
29218 not then also send the server descriptors: this defeats the whole
29219 purpose. Fixes bug 539.
29222 - Changing the ExitPolicyRejectPrivate setting should cause us to
29223 rebuild our server descriptor.
29224 - Fix handling of hex nicknames when answering controller requests for
29225 networkstatus by name, or when deciding whether to warn about
29226 unknown routers in a config option. (Patch from mwenge.)
29227 - Fix a couple of hard-to-trigger autoconf problems that could result
29228 in really weird results on platforms whose sys/types.h files define
29229 nonstandard integer types.
29230 - Don't try to create the datadir when running --verify-config or
29231 --hash-password. Resolves bug 540.
29232 - If we were having problems getting a particular descriptor from the
29233 directory caches, and then we learned about a new descriptor for
29234 that router, we weren't resetting our failure count. Reported
29236 - Although we fixed bug 539 (where servers would send HTTP status 503
29237 responses _and_ send a body too), there are still servers out there
29238 that haven't upgraded. Therefore, make clients parse such bodies
29239 when they receive them.
29240 - Run correctly on systems where rlim_t is larger than unsigned long.
29241 This includes some 64-bit systems.
29242 - Run correctly on platforms (like some versions of OS X 10.5) where
29243 the real limit for number of open files is OPEN_FILES, not rlim_max
29244 from getrlimit(RLIMIT_NOFILES).
29245 - Avoid a spurious free on base64 failure.
29246 - Avoid segfaults on certain complex invocations of
29247 router_get_by_hexdigest().
29248 - Fix rare bug on REDIRECTSTREAM control command when called with no
29249 port set: it could erroneously report an error when none had
29253 Changes in version 0.2.0.15-alpha - 2007-12-25
29254 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
29255 features added in 0.2.0.13-alpha.
29258 - Fix several remotely triggerable asserts based on DirPort requests
29259 for a v2 or v3 networkstatus object before we were prepared. This
29260 was particularly bad for 0.2.0.13 and later bridge relays, who
29261 would never have a v2 networkstatus and would thus always crash
29262 when used. Bugfixes on 0.2.0.x.
29263 - Estimate the v3 networkstatus size more accurately, rather than
29264 estimating it at zero bytes and giving it artificially high priority
29265 compared to other directory requests. Bugfix on 0.2.0.x.
29268 - Fix configure.in logic for cross-compilation.
29269 - When we load a bridge descriptor from the cache, and it was
29270 previously unreachable, mark it as retriable so we won't just
29271 ignore it. Also, try fetching a new copy immediately. Bugfixes
29273 - The bridge GeoIP stats were counting other relays, for example
29274 self-reachability and authority-reachability tests.
29277 - Support compilation to target iPhone; patch from cjacker huang.
29278 To build for iPhone, pass the --enable-iphone option to configure.
29281 Changes in version 0.2.0.14-alpha - 2007-12-23
29283 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
29284 without a datadirectory from a previous Tor install. Reported
29286 - Fix a crash when we fetch a descriptor that turns out to be
29287 unexpected (it used to be in our networkstatus when we started
29288 fetching it, but it isn't in our current networkstatus), and we
29289 aren't using bridges. Bugfix on 0.2.0.x.
29290 - Fix a crash when accessing hidden services: it would work the first
29291 time you use a given introduction point for your service, but
29292 on subsequent requests we'd be using garbage memory. Fixed by
29293 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
29294 - Fix a crash when we load a bridge descriptor from disk but we don't
29295 currently have a Bridge line for it in our torrc. Bugfix on
29299 - If bridge authorities set BridgePassword, they will serve a
29300 snapshot of known bridge routerstatuses from their DirPort to
29301 anybody who knows that password. Unset by default.
29304 - Make the unit tests build again.
29305 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
29306 - Make PublishServerDescriptor default to 1, so the default doesn't
29307 have to change as we invent new directory protocol versions.
29308 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
29309 be included unless sys/time.h is already included. Fixes
29310 bug 553. Bugfix on 0.2.0.x.
29311 - If we receive a general-purpose descriptor and then receive an
29312 identical bridge-purpose descriptor soon after, don't discard
29313 the next one as a duplicate.
29316 - If BridgeRelay is set to 1, then the default for
29317 PublishServerDescriptor is now "bridge" rather than "v2,v3".
29318 - If the user sets RelayBandwidthRate but doesn't set
29319 RelayBandwidthBurst, then make them equal rather than erroring out.
29322 Changes in version 0.2.0.13-alpha - 2007-12-21
29323 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
29324 Goodell, fixes many more bugs, and adds a lot of infrastructure for
29327 o New directory authorities:
29328 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
29332 - Only update guard status (usable / not usable) once we have
29333 enough directory information. This was causing us to always pick
29334 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
29335 causing us to discard all our guards on startup if we hadn't been
29336 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
29337 - Purge old entries from the "rephist" database and the hidden
29338 service descriptor databases even when DirPort is zero. Bugfix
29340 - We were ignoring our RelayBandwidthRate for the first 30 seconds
29341 after opening a circuit -- even a relayed circuit. Bugfix on
29343 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
29344 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
29345 crashing or mis-answering these types of requests.
29346 - Relays were publishing their server descriptor to v1 and v2
29347 directory authorities, but they didn't try publishing to v3-only
29348 authorities. Fix this; and also stop publishing to v1 authorities.
29350 - When we were reading router descriptors from cache, we were ignoring
29351 the annotations -- so for example we were reading in bridge-purpose
29352 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
29353 - When we decided to send a 503 response to a request for servers, we
29354 were then also sending the server descriptors: this defeats the
29355 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
29358 - Bridge relays now behave like clients with respect to time
29359 intervals for downloading new consensus documents -- otherwise they
29360 stand out. Bridge users now wait until the end of the interval,
29361 so their bridge relay will be sure to have a new consensus document.
29362 - Three new config options (AlternateDirAuthority,
29363 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
29364 user selectively replace the default directory authorities by type,
29365 rather than the all-or-nothing replacement that DirServer offers.
29366 - Tor can now be configured to read a GeoIP file from disk in one
29367 of two formats. This can be used by controllers to map IP addresses
29368 to countries. Eventually, it may support exit-by-country.
29369 - When possible, bridge relays remember which countries users
29370 are coming from, and report aggregate information in their
29371 extra-info documents, so that the bridge authorities can learn
29372 where Tor is blocked.
29373 - Bridge directory authorities now do reachability testing on the
29374 bridges they know. They provide router status summaries to the
29375 controller via "getinfo ns/purpose/bridge", and also dump summaries
29376 to a file periodically.
29377 - Stop fetching directory info so aggressively if your DirPort is
29378 on but your ORPort is off; stop fetching v2 dir info entirely.
29379 You can override these choices with the new FetchDirInfoEarly
29383 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
29384 consensus documents when there are too many relays at a single
29385 IP address. Now clear it in v2 network status documents too, and
29386 also clear it in routerinfo_t when the relay is no longer listed
29387 in the relevant networkstatus document.
29388 - Don't crash if we get an unexpected value for the
29389 PublishServerDescriptor config option. Reported by Matt Edman;
29390 bugfix on 0.2.0.9-alpha.
29391 - Our new v2 hidden service descriptor format allows descriptors
29392 that have no introduction points. But Tor crashed when we tried
29393 to build a descriptor with no intro points (and it would have
29394 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
29395 by Karsten Loesing.
29396 - Fix building with dmalloc 5.5.2 with glibc.
29397 - Reject uploaded descriptors and extrainfo documents if they're
29398 huge. Otherwise we'll cache them all over the network and it'll
29399 clog everything up. Reported by Aljosha Judmayer.
29400 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
29401 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
29402 - When the DANGEROUS_VERSION controller status event told us we're
29403 running an obsolete version, it used the string "OLD" to describe
29404 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
29405 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
29406 - If we can't expand our list of entry guards (e.g. because we're
29407 using bridges or we have StrictEntryNodes set), don't mark relays
29408 down when they fail a directory request. Otherwise we're too quick
29409 to mark all our entry points down. Bugfix on 0.1.2.x.
29410 - Fix handling of hex nicknames when answering controller requests for
29411 networkstatus by name, or when deciding whether to warn about unknown
29412 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
29413 - Fix a couple of hard-to-trigger autoconf problems that could result
29414 in really weird results on platforms whose sys/types.h files define
29415 nonstandard integer types. Bugfix on 0.1.2.x.
29416 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
29417 - Don't crash on name lookup when we have no current consensus. Fixes
29418 bug 538; bugfix on 0.2.0.x.
29419 - Only Tors that want to mirror the v2 directory info should
29420 create the "cached-status" directory in their datadir. (All Tors
29421 used to create it.) Bugfix on 0.2.0.9-alpha.
29422 - Directory authorities should only automatically download Extra Info
29423 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
29426 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
29427 consumers. (We already do this on HUP.)
29428 - Authorities and caches fetch the v2 networkstatus documents
29429 less often, now that v3 is encouraged.
29430 - Add a new config option BridgeRelay that specifies you want to
29431 be a bridge relay. Right now the only difference is that it makes
29432 you answer begin_dir requests, and it makes you cache dir info,
29433 even if your DirPort isn't on.
29434 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
29435 ask about source, timestamp of arrival, purpose, etc. We need
29436 something like this to help Vidalia not do GeoIP lookups on bridge
29438 - Allow multiple HashedControlPassword config lines, to support
29439 multiple controller passwords.
29440 - Authorities now decide whether they're authoritative for a given
29441 router based on the router's purpose.
29442 - New config options AuthDirBadDir and AuthDirListBadDirs for
29443 authorities to mark certain relays as "bad directories" in the
29444 networkstatus documents. Also supports the "!baddir" directive in
29445 the approved-routers file.
29448 Changes in version 0.2.0.12-alpha - 2007-11-16
29449 This twelfth development snapshot fixes some more build problems as
29450 well as a few minor bugs.
29453 - Make it build on OpenBSD again. Patch from tup.
29454 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
29455 package-building for Red Hat, OS X, etc.
29457 o Minor bugfixes (on 0.1.2.x):
29458 - Changing the ExitPolicyRejectPrivate setting should cause us to
29459 rebuild our server descriptor.
29461 o Minor bugfixes (on 0.2.0.x):
29462 - When we're lacking a consensus, don't try to perform rendezvous
29463 operations. Reported by Karsten Loesing.
29464 - Fix a small memory leak whenever we decide against using a
29465 newly picked entry guard. Reported by Mike Perry.
29466 - When authorities detected more than two relays running on the same
29467 IP address, they were clearing all the status flags but forgetting
29468 to clear the "hsdir" flag. So clients were being told that a
29469 given relay was the right choice for a v2 hsdir lookup, yet they
29470 never had its descriptor because it was marked as 'not running'
29472 - If we're trying to fetch a bridge descriptor and there's no way
29473 the bridge authority could help us (for example, we don't know
29474 a digest, or there is no bridge authority), don't be so eager to
29475 fall back to asking the bridge authority.
29476 - If we're using bridges or have strictentrynodes set, and our
29477 chosen exit is in the same family as all our bridges/entry guards,
29478 then be flexible about families.
29481 - When we negotiate a v2 link-layer connection (not yet implemented),
29482 accept RELAY_EARLY cells and turn them into RELAY cells if we've
29483 negotiated a v1 connection for their next step. Initial code for
29487 Changes in version 0.2.0.11-alpha - 2007-11-12
29488 This eleventh development snapshot fixes some build problems with
29489 the previous snapshot. It also includes a more secure-by-default exit
29490 policy for relays, fixes an enormous memory leak for exit relays, and
29491 fixes another bug where servers were falling out of the directory list.
29494 - Exit policies now reject connections that are addressed to a
29495 relay's public (external) IP address too, unless
29496 ExitPolicyRejectPrivate is turned off. We do this because too
29497 many relays are running nearby to services that trust them based
29498 on network address. Bugfix on 0.1.2.x.
29501 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
29502 on every successful resolve. Reported by Mike Perry; bugfix
29504 - On authorities, never downgrade to old router descriptors simply
29505 because they're listed in the consensus. This created a catch-22
29506 where we wouldn't list a new descriptor because there was an
29507 old one in the consensus, and we couldn't get the new one in the
29508 consensus because we wouldn't list it. Possible fix for bug 548.
29509 Also, this might cause bug 543 to appear on authorities; if so,
29510 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
29512 o Packaging fixes on 0.2.0.10-alpha:
29513 - We were including instructions about what to do with the
29514 src/config/fallback-consensus file, but we weren't actually
29515 including it in the tarball. Disable all of that for now.
29518 - Allow people to say PreferTunnelledDirConns rather than
29519 PreferTunneledDirConns, for those alternate-spellers out there.
29522 - Don't reevaluate all the information from our consensus document
29523 just because we've downloaded a v2 networkstatus that we intend
29524 to cache. Fixes bug 545; bugfix on 0.2.0.x.
29527 Changes in version 0.2.0.10-alpha - 2007-11-10
29528 This tenth development snapshot adds a third v3 directory authority
29529 run by Mike Perry, adds most of Karsten Loesing's new hidden service
29530 descriptor format, fixes a bad crash bug and new bridge bugs introduced
29531 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
29532 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
29533 addresses many more minor issues.
29535 o New directory authorities:
29536 - Set up ides (run by Mike Perry) as the third v3 directory authority.
29539 - Allow tunnelled directory connections to ask for an encrypted
29540 "begin_dir" connection or an anonymized "uses a full Tor circuit"
29541 connection independently. Now we can make anonymized begin_dir
29542 connections for (e.g.) more secure hidden service posting and
29544 - More progress on proposal 114: code from Karsten Loesing to
29545 implement new hidden service descriptor format.
29546 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
29547 accommodate the growing number of servers that use the default
29548 and are reaching it.
29549 - Directory authorities use a new formula for selecting which nodes
29550 to advertise as Guards: they must be in the top 7/8 in terms of
29551 how long we have known about them, and above the median of those
29552 nodes in terms of weighted fractional uptime.
29553 - Make "not enough dir info yet" warnings describe *why* Tor feels
29554 it doesn't have enough directory info yet.
29557 - Stop servers from crashing if they set a Family option (or
29558 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
29560 - Make bridge users work again -- the move to v3 directories in
29561 0.2.0.9-alpha had introduced a number of bugs that made bridges
29562 no longer work for clients.
29563 - When the clock jumps forward a lot, do not allow the bandwidth
29564 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
29566 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
29567 - When the consensus lists a router descriptor that we previously were
29568 mirroring, but that we considered non-canonical, reload the
29569 descriptor as canonical. This fixes bug 543 where Tor servers
29570 would start complaining after a few days that they don't have
29571 enough directory information to build a circuit.
29572 - Consider replacing the current consensus when certificates arrive
29573 that make the pending consensus valid. Previously, we were only
29574 considering replacement when the new certs _didn't_ help.
29575 - Fix an assert error on startup if we didn't already have the
29576 consensus and certs cached in our datadirectory: we were caching
29577 the consensus in consensus_waiting_for_certs but then free'ing it
29579 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
29580 Request) if we need more v3 certs but we've already got pending
29581 requests for all of them.
29582 - Correctly back off from failing certificate downloads. Fixes
29584 - Authorities don't vote on the Running flag if they have been running
29585 for less than 30 minutes themselves. Fixes bug 547, where a newly
29586 started authority would vote that everyone was down.
29588 o New requirements:
29589 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
29590 it, it had no AES, and it hasn't seen any security patches since
29594 - Clients now hold circuitless TLS connections open for 1.5 times
29595 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
29596 rebuild a new circuit over them within that timeframe. Previously,
29597 they held them open only for KeepalivePeriod (5 minutes).
29598 - Use "If-Modified-Since" to avoid retrieving consensus
29599 networkstatuses that we already have.
29600 - When we have no consensus, check FallbackNetworkstatusFile (defaults
29601 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
29602 we start knowing some directory caches.
29603 - When we receive a consensus from the future, warn about skew.
29604 - Improve skew reporting: try to give the user a better log message
29605 about how skewed they are, and how much this matters.
29606 - When we have a certificate for an authority, believe that
29607 certificate's claims about the authority's IP address.
29608 - New --quiet command-line option to suppress the default console log.
29609 Good in combination with --hash-password.
29610 - Authorities send back an X-Descriptor-Not-New header in response to
29611 an accepted-but-discarded descriptor upload. Partially implements
29613 - Make the log message for "tls error. breaking." more useful.
29614 - Better log messages about certificate downloads, to attempt to
29615 track down the second incarnation of bug 546.
29617 o Minor features (bridges):
29618 - If bridge users set UpdateBridgesFromAuthority, but the digest
29619 they ask for is a 404 from the bridge authority, they now fall
29620 back to trying the bridge directly.
29621 - Bridges now use begin_dir to publish their server descriptor to
29622 the bridge authority, even when they haven't set TunnelDirConns.
29624 o Minor features (controller):
29625 - When reporting clock skew, and we know that the clock is _at least
29626 as skewed_ as some value, but we don't know the actual value,
29627 report the value as a "minimum skew."
29630 - Update linux-tor-prio.sh script to allow QoS based on the uid of
29631 the Tor process. Patch from Marco Bonetti with tweaks from Mike
29635 - Refuse to start if both ORPort and UseBridges are set. Bugfix
29636 on 0.2.0.x, suggested by Matt Edman.
29637 - Don't stop fetching descriptors when FetchUselessDescriptors is
29638 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
29639 reported by tup and ioerror.
29640 - Better log message on vote from unknown authority.
29641 - Don't log "Launching 0 request for 0 router" message.
29643 o Minor bugfixes (memory leaks):
29644 - Stop leaking memory every time we parse a v3 certificate. Bugfix
29646 - Stop leaking memory every time we load a v3 certificate. Bugfix
29647 on 0.2.0.1-alpha. Fixes bug 536.
29648 - Stop leaking a cached networkstatus on exit. Bugfix on
29650 - Stop leaking voter information every time we free a consensus.
29651 Bugfix on 0.2.0.3-alpha.
29652 - Stop leaking signed data every time we check a voter signature.
29653 Bugfix on 0.2.0.3-alpha.
29654 - Stop leaking a signature every time we fail to parse a consensus or
29655 a vote. Bugfix on 0.2.0.3-alpha.
29656 - Stop leaking v2_download_status_map on shutdown. Bugfix on
29658 - Stop leaking conn->nickname every time we make a connection to a
29659 Tor relay without knowing its expected identity digest (e.g. when
29660 using bridges). Bugfix on 0.2.0.3-alpha.
29662 - Minor bugfixes (portability):
29663 - Run correctly on platforms where rlim_t is larger than unsigned
29664 long, and/or where the real limit for number of open files is
29665 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
29666 particular, these may be needed for OS X 10.5.
29669 Changes in version 0.1.2.18 - 2007-10-28
29670 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
29671 hidden service introduction that were causing huge delays, and a big
29672 bug that was causing some servers to disappear from the network status
29673 lists for a few hours each day.
29675 o Major bugfixes (crashes):
29676 - If a connection is shut down abruptly because of something that
29677 happened inside connection_flushed_some(), do not call
29678 connection_finished_flushing(). Should fix bug 451:
29679 "connection_stop_writing: Assertion conn->write_event failed"
29680 Bugfix on 0.1.2.7-alpha.
29681 - Fix possible segfaults in functions called from
29682 rend_process_relay_cell().
29684 o Major bugfixes (hidden services):
29685 - Hidden services were choosing introduction points uniquely by
29686 hexdigest, but when constructing the hidden service descriptor
29687 they merely wrote the (potentially ambiguous) nickname.
29688 - Clients now use the v2 intro format for hidden service
29689 connections: they specify their chosen rendezvous point by identity
29690 digest rather than by (potentially ambiguous) nickname. These
29691 changes could speed up hidden service connections dramatically.
29693 o Major bugfixes (other):
29694 - Stop publishing a new server descriptor just because we get a
29695 HUP signal. This led (in a roundabout way) to some servers getting
29696 dropped from the networkstatus lists for a few hours each day.
29697 - When looking for a circuit to cannibalize, consider family as well
29698 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
29699 circuit cannibalization).
29700 - When a router wasn't listed in a new networkstatus, we were leaving
29701 the flags for that router alone -- meaning it remained Named,
29702 Running, etc -- even though absence from the networkstatus means
29703 that it shouldn't be considered to exist at all anymore. Now we
29704 clear all the flags for routers that fall out of the networkstatus
29705 consensus. Fixes bug 529.
29708 - Don't try to access (or alter) the state file when running
29709 --list-fingerprint or --verify-config or --hash-password. Resolves
29711 - When generating information telling us how to extend to a given
29712 router, do not try to include the nickname if it is
29713 absent. Resolves bug 467.
29714 - Fix a user-triggerable segfault in expand_filename(). (There isn't
29715 a way to trigger this remotely.)
29716 - When sending a status event to the controller telling it that an
29717 OR address is reachable, set the port correctly. (Previously we
29718 were reporting the dir port.)
29719 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
29720 command. Bugfix on 0.1.2.17.
29721 - When loading bandwidth history, do not believe any information in
29722 the future. Fixes bug 434.
29723 - When loading entry guard information, do not believe any information
29725 - When we have our clock set far in the future and generate an
29726 onion key, then re-set our clock to be correct, we should not stop
29727 the onion key from getting rotated.
29728 - On some platforms, accept() can return a broken address. Detect
29729 this more quietly, and deal accordingly. Fixes bug 483.
29730 - It's not actually an error to find a non-pending entry in the DNS
29731 cache when canceling a pending resolve. Don't log unless stuff
29732 is fishy. Resolves bug 463.
29733 - Don't reset trusted dir server list when we set a configuration
29734 option. Patch from Robert Hogan.
29735 - Don't try to create the datadir when running --verify-config or
29736 --hash-password. Resolves bug 540.
29739 Changes in version 0.2.0.9-alpha - 2007-10-24
29740 This ninth development snapshot switches clients to the new v3 directory
29741 system; allows servers to be listed in the network status even when they
29742 have the same nickname as a registered server; and fixes many other
29743 bugs including a big one that was causing some servers to disappear
29744 from the network status lists for a few hours each day.
29746 o Major features (directory system):
29747 - Clients now download v3 consensus networkstatus documents instead
29748 of v2 networkstatus documents. Clients and caches now base their
29749 opinions about routers on these consensus documents. Clients only
29750 download router descriptors listed in the consensus.
29751 - Authorities now list servers who have the same nickname as
29752 a different named server, but list them with a new flag,
29753 "Unnamed". Now we can list servers that happen to pick the same
29754 nickname as a server that registered two years ago and then
29755 disappeared. Partially implements proposal 122.
29756 - If the consensus lists a router as "Unnamed", the name is assigned
29757 to a different router: do not identify the router by that name.
29758 Partially implements proposal 122.
29759 - Authorities can now come to a consensus on which method to use to
29760 compute the consensus. This gives us forward compatibility.
29763 - Stop publishing a new server descriptor just because we HUP or
29764 when we find our DirPort to be reachable but won't actually publish
29765 it. New descriptors without any real changes are dropped by the
29766 authorities, and can screw up our "publish every 18 hours" schedule.
29768 - When a router wasn't listed in a new networkstatus, we were leaving
29769 the flags for that router alone -- meaning it remained Named,
29770 Running, etc -- even though absence from the networkstatus means
29771 that it shouldn't be considered to exist at all anymore. Now we
29772 clear all the flags for routers that fall out of the networkstatus
29773 consensus. Fixes bug 529; bugfix on 0.1.2.x.
29774 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
29775 extrainfo documents and then discard them immediately for not
29776 matching the latest router. Bugfix on 0.2.0.1-alpha.
29778 o Minor features (v3 directory protocol):
29779 - Allow tor-gencert to generate a new certificate without replacing
29781 - Allow certificates to include an address.
29782 - When we change our directory-cache settings, reschedule all voting
29783 and download operations.
29784 - Reattempt certificate downloads immediately on failure, as long as
29785 we haven't failed a threshold number of times yet.
29786 - Delay retrying consensus downloads while we're downloading
29787 certificates to verify the one we just got. Also, count getting a
29788 consensus that we already have (or one that isn't valid) as a failure,
29789 and count failing to get the certificates after 20 minutes as a
29791 - Build circuits and download descriptors even if our consensus is a
29792 little expired. (This feature will go away once authorities are
29795 o Minor features (router descriptor cache):
29796 - If we find a cached-routers file that's been sitting around for more
29797 than 28 days unmodified, then most likely it's a leftover from
29798 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
29800 - When we (as a cache) download a descriptor because it was listed
29801 in a consensus, remember when the consensus was supposed to expire,
29802 and don't expire the descriptor until then.
29804 o Minor features (performance):
29805 - Call routerlist_remove_old_routers() much less often. This should
29806 speed startup, especially on directory caches.
29807 - Don't try to launch new descriptor downloads quite so often when we
29808 already have enough directory information to build circuits.
29809 - Base64 decoding was actually showing up on our profile when parsing
29810 the initial descriptor file; switch to an in-process all-at-once
29811 implementation that's about 3.5x times faster than calling out to
29814 o Minor features (compilation):
29815 - Detect non-ASCII platforms (if any still exist) and refuse to
29816 build there: some of our code assumes that 'A' is 65 and so on.
29818 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
29819 - Make the "next period" votes into "current period" votes immediately
29820 after publishing the consensus; avoid a heisenbug that made them
29821 stick around indefinitely.
29822 - When we discard a vote as a duplicate, do not report this as
29824 - Treat missing v3 keys or certificates as an error when running as a
29825 v3 directory authority.
29826 - When we're configured to be a v3 authority, but we're only listed
29827 as a non-v3 authority in our DirServer line for ourself, correct
29829 - If an authority doesn't have a qualified hostname, just put
29830 its address in the vote. This fixes the problem where we referred to
29831 "moria on moria:9031."
29832 - Distinguish between detached signatures for the wrong period, and
29833 detached signatures for a divergent vote.
29834 - Fix a small memory leak when computing a consensus.
29835 - When there's no consensus, we were forming a vote every 30
29836 minutes, but writing the "valid-after" line in our vote based
29837 on our configured V3AuthVotingInterval: so unless the intervals
29838 matched up, we immediately rejected our own vote because it didn't
29839 start at the voting interval that caused us to construct a vote.
29841 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
29842 - Delete unverified-consensus when the real consensus is set.
29843 - Consider retrying a consensus networkstatus fetch immediately
29844 after one fails: don't wait 60 seconds to notice.
29845 - When fetching a consensus as a cache, wait until a newer consensus
29846 should exist before trying to replace the current one.
29847 - Use a more forgiving schedule for retrying failed consensus
29848 downloads than for other types.
29850 o Minor bugfixes (other directory issues):
29851 - Correct the implementation of "download votes by digest." Bugfix on
29853 - Authorities no longer send back "400 you're unreachable please fix
29854 it" errors to Tor servers that aren't online all the time. We're
29855 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
29857 o Minor bugfixes (controller):
29858 - Don't reset trusted dir server list when we set a configuration
29859 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
29860 - Respond to INT and TERM SIGNAL commands before we execute the
29861 signal, in case the signal shuts us down. We had a patch in
29862 0.1.2.1-alpha that tried to do this by queueing the response on
29863 the connection's buffer before shutting down, but that really
29864 isn't the same thing at all. Bug located by Matt Edman.
29866 o Minor bugfixes (misc):
29867 - Correctly check for bad options to the "PublishServerDescriptor"
29868 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
29869 - Stop leaking memory on failing case of base32_decode, and make
29870 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
29871 - Don't try to download extrainfo documents when we're trying to
29872 fetch enough directory info to build a circuit: having enough
29873 info should get priority. Bugfix on 0.2.0.x.
29874 - Don't complain that "your server has not managed to confirm that its
29875 ports are reachable" if we haven't been able to build any circuits
29876 yet. Bug found by spending four hours without a v3 consensus. Bugfix
29878 - Detect the reason for failing to mmap a descriptor file we just
29879 wrote, and give a more useful log message. Fixes bug 533. Bugfix
29882 o Code simplifications and refactoring:
29883 - Remove support for the old bw_accounting file: we've been storing
29884 bandwidth accounting information in the state file since
29885 0.1.2.5-alpha. This may result in bandwidth accounting errors
29886 if you try to upgrade from 0.1.1.x or earlier, or if you try to
29887 downgrade to 0.1.1.x or earlier.
29888 - New convenience code to locate a file within the DataDirectory.
29889 - Move non-authority functionality out of dirvote.c.
29890 - Refactor the arguments for router_pick_{directory_|trusteddir}server
29891 so that they all take the same named flags.
29894 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
29895 Unix users an easy way to script their Tor process (e.g. by
29896 adjusting bandwidth based on the time of the day).
29899 Changes in version 0.2.0.8-alpha - 2007-10-12
29900 This eighth development snapshot fixes a crash bug that's been bothering
29901 us since February 2007, lets bridge authorities store a list of bridge
29902 descriptors they've seen, gets v3 directory voting closer to working,
29903 starts caching v3 directory consensus documents on directory mirrors,
29904 and fixes a variety of smaller issues including some minor memory leaks.
29906 o Major features (router descriptor cache):
29907 - Store routers in a file called cached-descriptors instead of in
29908 cached-routers. Initialize cached-descriptors from cached-routers
29909 if the old format is around. The new format allows us to store
29910 annotations along with descriptors.
29911 - Use annotations to record the time we received each descriptor, its
29912 source, and its purpose.
29913 - Disable the SETROUTERPURPOSE controller command: it is now
29915 - Controllers should now specify cache=no or cache=yes when using
29916 the +POSTDESCRIPTOR command.
29917 - Bridge authorities now write bridge descriptors to disk, meaning
29918 we can export them to other programs and begin distributing them
29921 o Major features (directory authorities):
29922 - When a v3 authority is missing votes or signatures, it now tries
29924 - Directory authorities track weighted fractional uptime as well as
29925 weighted mean-time-between failures. WFU is suitable for deciding
29926 whether a node is "usually up", while MTBF is suitable for deciding
29927 whether a node is "likely to stay up." We need both, because
29928 "usually up" is a good requirement for guards, while "likely to
29929 stay up" is a good requirement for long-lived connections.
29931 o Major features (v3 directory system):
29932 - Caches now download v3 network status documents as needed,
29933 and download the descriptors listed in them.
29934 - All hosts now attempt to download and keep fresh v3 authority
29935 certificates, and re-attempt after failures.
29936 - More internal-consistency checks for vote parsing.
29938 o Major bugfixes (crashes):
29939 - If a connection is shut down abruptly because of something that
29940 happened inside connection_flushed_some(), do not call
29941 connection_finished_flushing(). Should fix bug 451. Bugfix on
29944 o Major bugfixes (performance):
29945 - Fix really bad O(n^2) performance when parsing a long list of
29946 routers: Instead of searching the entire list for an "extra-info "
29947 string which usually wasn't there, once for every routerinfo
29948 we read, just scan lines forward until we find one we like.
29950 - When we add data to a write buffer in response to the data on that
29951 write buffer getting low because of a flush, do not consider the
29952 newly added data as a candidate for immediate flushing, but rather
29953 make it wait until the next round of writing. Otherwise, we flush
29954 and refill recursively, and a single greedy TLS connection can
29955 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
29957 o Minor features (v3 authority system):
29958 - Add more ways for tools to download the votes that lead to the
29960 - Send a 503 when low on bandwidth and a vote, consensus, or
29961 certificate is requested.
29962 - If-modified-since is now implemented properly for all kinds of
29963 certificate requests.
29965 o Minor bugfixes (network statuses):
29966 - Tweak the implementation of proposal 109 slightly: allow at most
29967 two Tor servers on the same IP address, except if it's the location
29968 of a directory authority, in which case allow five. Bugfix on
29971 o Minor bugfixes (controller):
29972 - When sending a status event to the controller telling it that an
29973 OR address is reachable, set the port correctly. (Previously we
29974 were reporting the dir port.) Bugfix on 0.1.2.x.
29976 o Minor bugfixes (v3 directory system):
29977 - Fix logic to look up a cert by its signing key digest. Bugfix on
29979 - Only change the reply to a vote to "OK" if it's not already
29980 set. This gets rid of annoying "400 OK" log messages, which may
29981 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
29982 - When we get a valid consensus, recompute the voting schedule.
29983 - Base the valid-after time of a vote on the consensus voting
29984 schedule, not on our preferred schedule.
29985 - Make the return values and messages from signature uploads and
29986 downloads more sensible.
29987 - Fix a memory leak when serving votes and consensus documents, and
29988 another when serving certificates.
29990 o Minor bugfixes (performance):
29991 - Use a slightly simpler string hashing algorithm (copying Python's
29992 instead of Java's) and optimize our digest hashing algorithm to take
29993 advantage of 64-bit platforms and to remove some possibly-costly
29995 - Fix a minor memory leak whenever we parse guards from our state
29996 file. Bugfix on 0.2.0.7-alpha.
29997 - Fix a minor memory leak whenever we write out a file. Bugfix on
29999 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30000 command. Bugfix on 0.2.0.5-alpha.
30002 o Minor bugfixes (portability):
30003 - On some platforms, accept() can return a broken address. Detect
30004 this more quietly, and deal accordingly. Fixes bug 483.
30005 - Stop calling tor_strlower() on uninitialized memory in some cases.
30006 Bugfix in 0.2.0.7-alpha.
30008 o Minor bugfixes (usability):
30009 - Treat some 403 responses from directory servers as INFO rather than
30010 WARN-severity events.
30011 - It's not actually an error to find a non-pending entry in the DNS
30012 cache when canceling a pending resolve. Don't log unless stuff is
30013 fishy. Resolves bug 463.
30015 o Minor bugfixes (anonymity):
30016 - Never report that we've used more bandwidth than we're willing to
30017 relay: it leaks how much non-relay traffic we're using. Resolves
30019 - When looking for a circuit to cannibalize, consider family as well
30020 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30021 circuit cannibalization).
30023 o Code simplifications and refactoring:
30024 - Make a bunch of functions static. Remove some dead code.
30025 - Pull out about a third of the really big routerlist.c; put it in a
30026 new module, networkstatus.c.
30027 - Merge the extra fields in local_routerstatus_t back into
30028 routerstatus_t: we used to need one routerstatus_t for each
30029 authority's opinion, plus a local_routerstatus_t for the locally
30030 computed consensus opinion. To save space, we put the locally
30031 modified fields into local_routerstatus_t, and only the common
30032 stuff into routerstatus_t. But once v3 directories are in use,
30033 clients and caches will no longer need to hold authority opinions;
30034 thus, the rationale for keeping the types separate is now gone.
30035 - Make the code used to reschedule and reattempt downloads more
30037 - Turn all 'Are we a directory server/mirror?' logic into a call to
30039 - Remove the code to generate the oldest (v1) directory format.
30040 The code has been disabled since 0.2.0.5-alpha.
30043 Changes in version 0.2.0.7-alpha - 2007-09-21
30044 This seventh development snapshot makes bridges work again, makes bridge
30045 authorities work for the first time, fixes two huge performance flaws
30046 in hidden services, and fixes a variety of minor issues.
30048 o New directory authorities:
30049 - Set up moria1 and tor26 as the first v3 directory authorities. See
30050 doc/spec/dir-spec.txt for details on the new directory design.
30052 o Major bugfixes (crashes):
30053 - Fix possible segfaults in functions called from
30054 rend_process_relay_cell(). Bugfix on 0.1.2.x.
30056 o Major bugfixes (bridges):
30057 - Fix a bug that made servers send a "404 Not found" in response to
30058 attempts to fetch their server descriptor. This caused Tor servers
30059 to take many minutes to establish reachability for their DirPort,
30060 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
30061 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
30062 users configure that and specify a bridge with an identity
30063 fingerprint, now they will lookup the bridge descriptor at the
30064 default bridge authority via a one-hop tunnel, but once circuits
30065 are established they will switch to a three-hop tunnel for later
30066 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
30068 o Major bugfixes (hidden services):
30069 - Hidden services were choosing introduction points uniquely by
30070 hexdigest, but when constructing the hidden service descriptor
30071 they merely wrote the (potentially ambiguous) nickname.
30072 - Clients now use the v2 intro format for hidden service
30073 connections: they specify their chosen rendezvous point by identity
30074 digest rather than by (potentially ambiguous) nickname. Both
30075 are bugfixes on 0.1.2.x, and they could speed up hidden service
30076 connections dramatically. Thanks to Karsten Loesing.
30078 o Minor features (security):
30079 - As a client, do not believe any server that tells us that an
30080 address maps to an internal address space.
30081 - Make it possible to enable HashedControlPassword and
30082 CookieAuthentication at the same time.
30084 o Minor features (guard nodes):
30085 - Tag every guard node in our state file with the version that
30086 we believe added it, or with our own version if we add it. This way,
30087 if a user temporarily runs an old version of Tor and then switches
30088 back to a new one, she doesn't automatically lose her guards.
30090 o Minor features (speed):
30091 - When implementing AES counter mode, update only the portions of the
30092 counter buffer that need to change, and don't keep separate
30093 network-order and host-order counters when they are the same (i.e.,
30094 on big-endian hosts.)
30096 o Minor features (controller):
30097 - Accept LF instead of CRLF on controller, since some software has a
30098 hard time generating real Internet newlines.
30099 - Add GETINFO values for the server status events
30100 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
30103 o Removed features:
30104 - Routers no longer include bandwidth-history lines in their
30105 descriptors; this information is already available in extra-info
30106 documents, and including it in router descriptors took up 60%
30107 (!) of compressed router descriptor downloads. Completes
30108 implementation of proposal 104.
30109 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
30110 and TorControl.py, as they use the old v0 controller protocol,
30111 and are obsoleted by TorFlow anyway.
30112 - Drop support for v1 rendezvous descriptors, since we never used
30113 them anyway, and the code has probably rotted by now. Based on
30114 patch from Karsten Loesing.
30115 - On OSX, stop warning the user that kqueue support in libevent is
30116 "experimental", since it seems to have worked fine for ages.
30119 - When generating information telling us how to extend to a given
30120 router, do not try to include the nickname if it is absent. Fixes
30121 bug 467. Bugfix on 0.2.0.3-alpha.
30122 - Fix a user-triggerable (but not remotely-triggerable) segfault
30123 in expand_filename(). Bugfix on 0.1.2.x.
30124 - Fix a memory leak when freeing incomplete requests from DNSPort.
30125 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
30126 - Don't try to access (or alter) the state file when running
30127 --list-fingerprint or --verify-config or --hash-password. (Resolves
30128 bug 499.) Bugfix on 0.1.2.x.
30129 - Servers used to decline to publish their DirPort if their
30130 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
30131 were below a threshold. Now they only look at BandwidthRate and
30132 RelayBandwidthRate. Bugfix on 0.1.2.x.
30133 - Remove an optimization in the AES counter-mode code that assumed
30134 that the counter never exceeded 2^68. When the counter can be set
30135 arbitrarily as an IV (as it is by Karsten's new hidden services
30136 code), this assumption no longer holds. Bugfix on 0.1.2.x.
30137 - Resume listing "AUTHORITY" flag for authorities in network status.
30138 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
30140 o Code simplifications and refactoring:
30141 - Revamp file-writing logic so we don't need to have the entire
30142 contents of a file in memory at once before we write to disk. Tor,
30144 - Turn "descriptor store" into a full-fledged type.
30145 - Move all NT services code into a separate source file.
30146 - Unify all code that computes medians, percentile elements, etc.
30147 - Get rid of a needless malloc when parsing address policies.
30150 Changes in version 0.1.2.17 - 2007-08-30
30151 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
30152 X bundles. Vidalia 0.0.14 makes authentication required for the
30153 ControlPort in the default configuration, which addresses important
30154 security risks. Everybody who uses Vidalia (or another controller)
30157 In addition, this Tor update fixes major load balancing problems with
30158 path selection, which should speed things up a lot once many people
30161 o Major bugfixes (security):
30162 - We removed support for the old (v0) control protocol. It has been
30163 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
30164 become more of a headache than it's worth.
30166 o Major bugfixes (load balancing):
30167 - When choosing nodes for non-guard positions, weight guards
30168 proportionally less, since they already have enough load. Patch
30170 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
30171 will allow fast Tor servers to get more attention.
30172 - When we're upgrading from an old Tor version, forget our current
30173 guards and pick new ones according to the new weightings. These
30174 three load balancing patches could raise effective network capacity
30175 by a factor of four. Thanks to Mike Perry for measurements.
30177 o Major bugfixes (stream expiration):
30178 - Expire not-yet-successful application streams in all cases if
30179 they've been around longer than SocksTimeout. Right now there are
30180 some cases where the stream will live forever, demanding a new
30181 circuit every 15 seconds. Fixes bug 454; reported by lodger.
30183 o Minor features (controller):
30184 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
30185 is valid before any authentication has been received. It tells
30186 a controller what kind of authentication is expected, and what
30187 protocol is spoken. Implements proposal 119.
30189 o Minor bugfixes (performance):
30190 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
30191 greatly speeding up loading cached-routers from disk on startup.
30192 - Disable sentinel-based debugging for buffer code: we squashed all
30193 the bugs that this was supposed to detect a long time ago, and now
30194 its only effect is to change our buffer sizes from nice powers of
30195 two (which platform mallocs tend to like) to values slightly over
30196 powers of two (which make some platform mallocs sad).
30198 o Minor bugfixes (misc):
30199 - If exit bandwidth ever exceeds one third of total bandwidth, then
30200 use the correct formula to weight exit nodes when choosing paths.
30201 Based on patch from Mike Perry.
30202 - Choose perfectly fairly among routers when choosing by bandwidth and
30203 weighting by fraction of bandwidth provided by exits. Previously, we
30204 would choose with only approximate fairness, and correct ourselves
30205 if we ran off the end of the list.
30206 - If we require CookieAuthentication but we fail to write the
30207 cookie file, we would warn but not exit, and end up in a state
30208 where no controller could authenticate. Now we exit.
30209 - If we require CookieAuthentication, stop generating a new cookie
30210 every time we change any piece of our config.
30211 - Refuse to start with certain directory authority keys, and
30212 encourage people using them to stop.
30213 - Terminate multi-line control events properly. Original patch
30215 - Fix a minor memory leak when we fail to find enough suitable
30216 servers to choose a circuit.
30217 - Stop leaking part of the descriptor when we run into a particularly
30218 unparseable piece of it.
30221 Changes in version 0.2.0.6-alpha - 2007-08-26
30222 This sixth development snapshot features a new Vidalia version in the
30223 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
30224 the ControlPort in the default configuration, which addresses important
30227 In addition, this snapshot fixes major load balancing problems
30228 with path selection, which should speed things up a lot once many
30229 people have upgraded. The directory authorities also use a new
30230 mean-time-between-failure approach to tracking which servers are stable,
30231 rather than just looking at the most recent uptime.
30233 o New directory authorities:
30234 - Set up Tonga as the default bridge directory authority.
30237 - Directory authorities now track servers by weighted
30238 mean-times-between-failures. When we have 4 or more days of data,
30239 use measured MTBF rather than declared uptime to decide whether
30240 to call a router Stable. Implements proposal 108.
30242 o Major bugfixes (load balancing):
30243 - When choosing nodes for non-guard positions, weight guards
30244 proportionally less, since they already have enough load. Patch
30246 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
30247 will allow fast Tor servers to get more attention.
30248 - When we're upgrading from an old Tor version, forget our current
30249 guards and pick new ones according to the new weightings. These
30250 three load balancing patches could raise effective network capacity
30251 by a factor of four. Thanks to Mike Perry for measurements.
30253 o Major bugfixes (descriptor parsing):
30254 - Handle unexpected whitespace better in malformed descriptors. Bug
30255 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
30258 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
30259 GETINFO for Torstat to use until it can switch to using extrainfos.
30260 - Optionally (if built with -DEXPORTMALLINFO) export the output
30261 of mallinfo via http, as tor/mallinfo.txt. Only accessible
30265 - Do not intermix bridge routers with controller-added
30266 routers. (Bugfix on 0.2.0.x)
30267 - Do not fail with an assert when accept() returns an unexpected
30268 address family. Addresses but does not wholly fix bug 483. (Bugfix
30270 - Let directory authorities startup even when they can't generate
30271 a descriptor immediately, e.g. because they don't know their
30273 - Stop putting the authentication cookie in a file called "0"
30274 in your working directory if you don't specify anything for the
30275 new CookieAuthFile option. Reported by Matt Edman.
30276 - Make it possible to read the PROTOCOLINFO response in a way that
30277 conforms to our control-spec. Reported by Matt Edman.
30278 - Fix a minor memory leak when we fail to find enough suitable
30279 servers to choose a circuit. Bugfix on 0.1.2.x.
30280 - Stop leaking part of the descriptor when we run into a particularly
30281 unparseable piece of it. Bugfix on 0.1.2.x.
30282 - Unmap the extrainfo cache file on exit.
30285 Changes in version 0.2.0.5-alpha - 2007-08-19
30286 This fifth development snapshot fixes compilation on Windows again;
30287 fixes an obnoxious client-side bug that slowed things down and put
30288 extra load on the network; gets us closer to using the v3 directory
30289 voting scheme; makes it easier for Tor controllers to use cookie-based
30290 authentication; and fixes a variety of other bugs.
30292 o Removed features:
30293 - Version 1 directories are no longer generated in full. Instead,
30294 authorities generate and serve "stub" v1 directories that list
30295 no servers. This will stop Tor versions 0.1.0.x and earlier from
30296 working, but (for security reasons) nobody should be running those
30299 o Major bugfixes (compilation, 0.2.0.x):
30300 - Try to fix Win32 compilation again: improve checking for IPv6 types.
30301 - Try to fix MSVC compilation: build correctly on platforms that do
30302 not define s6_addr16 or s6_addr32.
30303 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
30306 o Major bugfixes (stream expiration):
30307 - Expire not-yet-successful application streams in all cases if
30308 they've been around longer than SocksTimeout. Right now there are
30309 some cases where the stream will live forever, demanding a new
30310 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
30311 reported by lodger.
30313 o Minor features (directory servers):
30314 - When somebody requests a list of statuses or servers, and we have
30315 none of those, return a 404 rather than an empty 200.
30317 o Minor features (directory voting):
30318 - Store v3 consensus status consensuses on disk, and reload them
30321 o Minor features (security):
30322 - Warn about unsafe ControlPort configurations.
30323 - Refuse to start with certain directory authority keys, and
30324 encourage people using them to stop.
30326 o Minor features (controller):
30327 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
30328 is valid before any authentication has been received. It tells
30329 a controller what kind of authentication is expected, and what
30330 protocol is spoken. Implements proposal 119.
30331 - New config option CookieAuthFile to choose a new location for the
30332 cookie authentication file, and config option
30333 CookieAuthFileGroupReadable to make it group-readable.
30335 o Minor features (unit testing):
30336 - Add command-line arguments to unit-test executable so that we can
30337 invoke any chosen test from the command line rather than having
30338 to run the whole test suite at once; and so that we can turn on
30339 logging for the unit tests.
30341 o Minor bugfixes (on 0.1.2.x):
30342 - If we require CookieAuthentication but we fail to write the
30343 cookie file, we would warn but not exit, and end up in a state
30344 where no controller could authenticate. Now we exit.
30345 - If we require CookieAuthentication, stop generating a new cookie
30346 every time we change any piece of our config.
30347 - When loading bandwidth history, do not believe any information in
30348 the future. Fixes bug 434.
30349 - When loading entry guard information, do not believe any information
30351 - When we have our clock set far in the future and generate an
30352 onion key, then re-set our clock to be correct, we should not stop
30353 the onion key from getting rotated.
30354 - Clean up torrc sample config file.
30355 - Do not automatically run configure from autogen.sh. This
30356 non-standard behavior tended to annoy people who have built other
30359 o Minor bugfixes (on 0.2.0.x):
30360 - Fix a bug with AutomapHostsOnResolve that would always cause
30361 the second request to fail. Bug reported by Kate. Bugfix on
30363 - Fix a bug in ADDRMAP controller replies that would sometimes
30364 try to print a NULL. Patch from tup.
30365 - Read v3 directory authority keys from the right location.
30366 - Numerous bugfixes to directory voting code.
30369 Changes in version 0.1.2.16 - 2007-08-01
30370 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
30371 remote attacker in certain situations to rewrite the user's torrc
30372 configuration file. This can completely compromise anonymity of users
30373 in most configurations, including those running the Vidalia bundles,
30374 TorK, etc. Or worse.
30376 o Major security fixes:
30377 - Close immediately after missing authentication on control port;
30378 do not allow multiple authentication attempts.
30381 Changes in version 0.2.0.4-alpha - 2007-08-01
30382 This fourth development snapshot fixes a critical security vulnerability
30383 for most users, specifically those running Vidalia, TorK, etc. Everybody
30384 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
30386 o Major security fixes:
30387 - Close immediately after missing authentication on control port;
30388 do not allow multiple authentication attempts.
30390 o Major bugfixes (compilation):
30391 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
30394 o Minor features (performance):
30395 - Be even more aggressive about releasing RAM from small
30396 empty buffers. Thanks to our free-list code, this shouldn't be too
30397 performance-intensive.
30398 - Disable sentinel-based debugging for buffer code: we squashed all
30399 the bugs that this was supposed to detect a long time ago, and
30400 now its only effect is to change our buffer sizes from nice
30401 powers of two (which platform mallocs tend to like) to values
30402 slightly over powers of two (which make some platform mallocs sad).
30403 - Log malloc statistics from mallinfo() on platforms where it
30407 Changes in version 0.2.0.3-alpha - 2007-07-29
30408 This third development snapshot introduces new experimental
30409 blocking-resistance features and a preliminary version of the v3
30410 directory voting design, and includes many other smaller features
30414 - The first pieces of our "bridge" design for blocking-resistance
30415 are implemented. People can run bridge directory authorities;
30416 people can run bridges; and people can configure their Tor clients
30417 with a set of bridges to use as the first hop into the Tor network.
30418 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
30420 - Create listener connections before we setuid to the configured
30421 User and Group. Now non-Windows users can choose port values
30422 under 1024, start Tor as root, and have Tor bind those ports
30423 before it changes to another UID. (Windows users could already
30425 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
30426 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
30427 on "vserver" accounts. (Patch from coderman.)
30428 - Be even more aggressive about separating local traffic from relayed
30429 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
30431 o Major features (experimental):
30432 - First cut of code for "v3 dir voting": directory authorities will
30433 vote on a common network status document rather than each publishing
30434 their own opinion. This code needs more testing and more corner-case
30435 handling before it's ready for use.
30438 - Directory authorities now call routers Fast if their bandwidth is
30439 at least 100KB/s, and consider their bandwidth adequate to be a
30440 Guard if it is at least 250KB/s, no matter the medians. This fix
30441 complements proposal 107. [Bugfix on 0.1.2.x]
30442 - Directory authorities now never mark more than 3 servers per IP as
30443 Valid and Running. (Implements proposal 109, by Kevin Bauer and
30445 - Minor change to organizationName and commonName generation
30446 procedures in TLS certificates during Tor handshakes, to invalidate
30447 some earlier censorware approaches. This is not a long-term
30448 solution, but applying it will give us a bit of time to look into
30449 the epidemiology of countermeasures as they spread.
30451 o Major bugfixes (directory):
30452 - Rewrite directory tokenization code to never run off the end of
30453 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
30455 o Minor features (controller):
30456 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
30457 match requests to applications. (Patch from Robert Hogan.)
30458 - Report address and port correctly on connections to DNSPort. (Patch
30459 from Robert Hogan.)
30460 - Add a RESOLVE command to launch hostname lookups. (Original patch
30461 from Robert Hogan.)
30462 - Add GETINFO status/enough-dir-info to let controllers tell whether
30463 Tor has downloaded sufficient directory information. (Patch
30465 - You can now use the ControlSocket option to tell Tor to listen for
30466 controller connections on Unix domain sockets on systems that
30467 support them. (Patch from Peter Palfrader.)
30468 - STREAM NEW events are generated for DNSPort requests and for
30469 tunneled directory connections. (Patch from Robert Hogan.)
30470 - New "GETINFO address-mappings/*" command to get address mappings
30471 with expiry information. "addr-mappings/*" is now deprecated.
30474 o Minor features (misc):
30475 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
30477 - The tor-gencert tool for v3 directory authorities now creates all
30478 files as readable to the file creator only, and write-protects
30479 the authority identity key.
30480 - When dumping memory usage, list bytes used in buffer memory
30482 - When running with dmalloc, dump more stats on hup and on exit.
30483 - Directory authorities now fail quickly and (relatively) harmlessly
30484 if they generate a network status document that is somehow
30487 o Traffic load balancing improvements:
30488 - If exit bandwidth ever exceeds one third of total bandwidth, then
30489 use the correct formula to weight exit nodes when choosing paths.
30490 (Based on patch from Mike Perry.)
30491 - Choose perfectly fairly among routers when choosing by bandwidth and
30492 weighting by fraction of bandwidth provided by exits. Previously, we
30493 would choose with only approximate fairness, and correct ourselves
30494 if we ran off the end of the list. [Bugfix on 0.1.2.x]
30496 o Performance improvements:
30497 - Be more aggressive with freeing buffer RAM or putting it on the
30499 - Use Critical Sections rather than Mutexes for synchronizing threads
30500 on win32; Mutexes are heavier-weight, and designed for synchronizing
30503 o Deprecated and removed features:
30504 - RedirectExits is now deprecated.
30505 - Stop allowing address masks that do not correspond to bit prefixes.
30506 We have warned about these for a really long time; now it's time
30507 to reject them. (Patch from croup.)
30509 o Minor bugfixes (directory):
30510 - Fix another crash bug related to extra-info caching. (Bug found by
30511 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
30512 - Directories no longer return a "304 not modified" when they don't
30513 have the networkstatus the client asked for. Also fix a memory
30514 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
30515 - We had accidentally labelled 0.1.2.x directory servers as not
30516 suitable for begin_dir requests, and had labelled no directory
30517 servers as suitable for uploading extra-info documents. [Bugfix
30520 o Minor bugfixes (dns):
30521 - Fix a crash when DNSPort is set more than once. (Patch from Robert
30522 Hogan.) [Bugfix on 0.2.0.2-alpha]
30523 - Add DNSPort connections to the global connection list, so that we
30524 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
30526 - Fix a dangling reference that could lead to a crash when DNSPort is
30527 changed or closed (Patch from Robert Hogan.) [Bugfix on
30530 o Minor bugfixes (controller):
30531 - Provide DNS expiry times in GMT, not in local time. For backward
30532 compatibility, ADDRMAP events only provide GMT expiry in an extended
30533 field. "GETINFO address-mappings" always does the right thing.
30534 - Use CRLF line endings properly in NS events.
30535 - Terminate multi-line control events properly. (Original patch
30536 from tup.) [Bugfix on 0.1.2.x-alpha]
30537 - Do not include spaces in SOURCE_ADDR fields in STREAM
30538 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
30541 Changes in version 0.1.2.15 - 2007-07-17
30542 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
30543 problems, fixes compilation on BSD, and fixes a variety of other
30544 bugs. Everybody should upgrade.
30546 o Major bugfixes (compilation):
30547 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
30549 o Major bugfixes (crashes):
30550 - Try even harder not to dereference the first character after
30551 an mmap(). Reported by lodger.
30552 - Fix a crash bug in directory authorities when we re-number the
30553 routerlist while inserting a new router.
30554 - When the cached-routers file is an even multiple of the page size,
30555 don't run off the end and crash. (Fixes bug 455; based on idea
30557 - Fix eventdns.c behavior on Solaris: It is critical to include
30558 orconfig.h _before_ sys/types.h, so that we can get the expected
30559 definition of _FILE_OFFSET_BITS.
30561 o Major bugfixes (security):
30562 - Fix a possible buffer overrun when using BSD natd support. Bug
30564 - When sending destroy cells from a circuit's origin, don't include
30565 the reason for tearing down the circuit. The spec says we didn't,
30566 and now we actually don't. Reported by lodger.
30567 - Keep streamids from different exits on a circuit separate. This
30568 bug may have allowed other routers on a given circuit to inject
30569 cells into streams. Reported by lodger; fixes bug 446.
30570 - If there's a never-before-connected-to guard node in our list,
30571 never choose any guards past it. This way we don't expand our
30572 guard list unless we need to.
30574 o Minor bugfixes (guard nodes):
30575 - Weight guard selection by bandwidth, so that low-bandwidth nodes
30576 don't get overused as guards.
30578 o Minor bugfixes (directory):
30579 - Correctly count the number of authorities that recommend each
30580 version. Previously, we were under-counting by 1.
30581 - Fix a potential crash bug when we load many server descriptors at
30582 once and some of them make others of them obsolete. Fixes bug 458.
30584 o Minor bugfixes (hidden services):
30585 - Stop tearing down the whole circuit when the user asks for a
30586 connection to a port that the hidden service didn't configure.
30589 o Minor bugfixes (misc):
30590 - On Windows, we were preventing other processes from reading
30591 cached-routers while Tor was running. Reported by janbar.
30592 - Fix a possible (but very unlikely) bug in picking routers by
30593 bandwidth. Add a log message to confirm that it is in fact
30594 unlikely. Patch from lodger.
30595 - Backport a couple of memory leak fixes.
30596 - Backport miscellaneous cosmetic bugfixes.
30599 Changes in version 0.2.0.2-alpha - 2007-06-02
30600 o Major bugfixes on 0.2.0.1-alpha:
30601 - Fix an assertion failure related to servers without extra-info digests.
30602 Resolves bugs 441 and 442.
30604 o Minor features (directory):
30605 - Support "If-Modified-Since" when answering HTTP requests for
30606 directories, running-routers documents, and network-status documents.
30607 (There's no need to support it for router descriptors, since those
30608 are downloaded by descriptor digest.)
30610 o Minor build issues:
30611 - Clear up some MIPSPro compiler warnings.
30612 - When building from a tarball on a machine that happens to have SVK
30613 installed, report the micro-revision as whatever version existed
30614 in the tarball, not as "x".
30617 Changes in version 0.2.0.1-alpha - 2007-06-01
30618 This early development snapshot provides new features for people running
30619 Tor as both a client and a server (check out the new RelayBandwidth
30620 config options); lets Tor run as a DNS proxy; and generally moves us
30621 forward on a lot of fronts.
30623 o Major features, server usability:
30624 - New config options RelayBandwidthRate and RelayBandwidthBurst:
30625 a separate set of token buckets for relayed traffic. Right now
30626 relayed traffic is defined as answers to directory requests, and
30627 OR connections that don't have any local circuits on them.
30629 o Major features, client usability:
30630 - A client-side DNS proxy feature to replace the need for
30631 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
30632 for DNS requests on port 9999, use the Tor network to resolve them
30633 anonymously, and send the reply back like a regular DNS server.
30634 The code still only implements a subset of DNS.
30635 - Make PreferTunneledDirConns and TunnelDirConns work even when
30636 we have no cached directory info. This means Tor clients can now
30637 do all of their connections protected by TLS.
30639 o Major features, performance and efficiency:
30640 - Directory authorities accept and serve "extra info" documents for
30641 routers. These documents contain fields from router descriptors
30642 that aren't usually needed, and that use a lot of excess
30643 bandwidth. Once these fields are removed from router descriptors,
30644 the bandwidth savings should be about 60%. [Partially implements
30646 - Servers upload extra-info documents to any authority that accepts
30647 them. Authorities (and caches that have been configured to download
30648 extra-info documents) download them as needed. [Partially implements
30650 - Change the way that Tor buffers data that it is waiting to write.
30651 Instead of queueing data cells in an enormous ring buffer for each
30652 client->OR or OR->OR connection, we now queue cells on a separate
30653 queue for each circuit. This lets us use less slack memory, and
30654 will eventually let us be smarter about prioritizing different kinds
30656 - Use memory pools to allocate cells with better speed and memory
30657 efficiency, especially on platforms where malloc() is inefficient.
30658 - Stop reading on edge connections when their corresponding circuit
30659 buffers are full; start again as the circuits empty out.
30661 o Major features, other:
30662 - Add an HSAuthorityRecordStats option that hidden service authorities
30663 can use to track statistics of overall hidden service usage without
30664 logging information that would be very useful to an attacker.
30665 - Start work implementing multi-level keys for directory authorities:
30666 Add a standalone tool to generate key certificates. (Proposal 103.)
30669 - Directory authorities now call routers Stable if they have an
30670 uptime of at least 30 days, even if that's not the median uptime
30671 in the network. Implements proposal 107, suggested by Kevin Bauer
30674 o Minor fixes (resource management):
30675 - Count the number of open sockets separately from the number
30676 of active connection_t objects. This will let us avoid underusing
30677 our allocated connection limit.
30678 - We no longer use socket pairs to link an edge connection to an
30679 anonymous directory connection or a DirPort test connection.
30680 Instead, we track the link internally and transfer the data
30681 in-process. This saves two sockets per "linked" connection (at the
30682 client and at the server), and avoids the nasty Windows socketpair()
30684 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
30685 for every single inactive connection_t. Free items from the
30686 4k/16k-buffer free lists when they haven't been used for a while.
30688 o Minor features (build):
30689 - Make autoconf search for libevent, openssl, and zlib consistently.
30690 - Update deprecated macros in configure.in.
30691 - When warning about missing headers, tell the user to let us
30692 know if the compile succeeds anyway, so we can downgrade the
30694 - Include the current subversion revision as part of the version
30695 string: either fetch it directly if we're in an SVN checkout, do
30696 some magic to guess it if we're in an SVK checkout, or use
30697 the last-detected version if we're building from a .tar.gz.
30698 Use this version consistently in log messages.
30700 o Minor features (logging):
30701 - Always prepend "Bug: " to any log message about a bug.
30702 - Put a platform string (e.g. "Linux i686") in the startup log
30703 message, so when people paste just their logs, we know if it's
30704 OpenBSD or Windows or what.
30705 - When logging memory usage, break down memory used in buffers by
30708 o Minor features (directory system):
30709 - New config option V2AuthoritativeDirectory that all directory
30710 authorities should set. This will let future authorities choose
30711 not to serve V2 directory information.
30712 - Directory authorities allow multiple router descriptors and/or extra
30713 info documents to be uploaded in a single go. This will make
30714 implementing proposal 104 simpler.
30716 o Minor features (controller):
30717 - Add a new config option __DisablePredictedCircuits designed for
30718 use by the controller, when we don't want Tor to build any circuits
30720 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
30721 so we can exit from the middle of the circuit.
30722 - Implement "getinfo status/circuit-established".
30723 - Implement "getinfo status/version/..." so a controller can tell
30724 whether the current version is recommended, and whether any versions
30725 are good, and how many authorities agree. (Patch from shibz.)
30727 o Minor features (hidden services):
30728 - Allow multiple HiddenServicePort directives with the same virtual
30729 port; when they occur, the user is sent round-robin to one
30730 of the target ports chosen at random. Partially fixes bug 393 by
30731 adding limited ad-hoc round-robining.
30733 o Minor features (other):
30735 - Add a new AutomapHostsOnResolve option: when it is enabled, any
30736 resolve request for hosts matching a given pattern causes Tor to
30737 generate an internal virtual address mapping for that host. This
30738 allows DNSPort to work sensibly with hidden service users. By
30739 default, .exit and .onion addresses are remapped; the list of
30740 patterns can be reconfigured with AutomapHostsSuffixes.
30741 - Add an "-F" option to tor-resolve to force a resolve for a .onion
30742 address. Thanks to the AutomapHostsOnResolve option, this is no
30743 longer a completely silly thing to do.
30744 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
30745 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
30746 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
30747 minus 1 byte: the actual maximum declared bandwidth.
30749 o Removed features:
30750 - Removed support for the old binary "version 0" controller protocol.
30751 This has been deprecated since 0.1.1, and warnings have been issued
30752 since 0.1.2. When we encounter a v0 control message, we now send
30753 back an error and close the connection.
30754 - Remove the old "dns worker" server DNS code: it hasn't been default
30755 since 0.1.2.2-alpha, and all the servers seem to be using the new
30758 o Minor bugfixes (portability):
30759 - Even though Windows is equally happy with / and \ as path separators,
30760 try to use \ consistently on Windows and / consistently on Unix: it
30761 makes the log messages nicer.
30762 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
30763 - Read resolv.conf files correctly on platforms where read() returns
30764 partial results on small file reads.
30766 o Minor bugfixes (directory):
30767 - Correctly enforce that elements of directory objects do not appear
30768 more often than they are allowed to appear.
30769 - When we are reporting the DirServer line we just parsed, we were
30770 logging the second stanza of the key fingerprint, not the first.
30772 o Minor bugfixes (logging):
30773 - When we hit an EOF on a log (probably because we're shutting down),
30774 don't try to remove the log from the list: just mark it as
30775 unusable. (Bulletproofs against bug 222.)
30777 o Minor bugfixes (other):
30778 - In the exitlist script, only consider the most recently published
30779 server descriptor for each server. Also, when the user requests
30780 a list of servers that _reject_ connections to a given address,
30781 explicitly exclude the IPs that also have servers that accept
30782 connections to that address. (Resolves bug 405.)
30783 - Stop allowing hibernating servers to be "stable" or "fast".
30784 - On Windows, we were preventing other processes from reading
30785 cached-routers while Tor was running. (Reported by janbar)
30786 - Make the NodeFamilies config option work. (Reported by
30787 lodger -- it has never actually worked, even though we added it
30789 - Check return values from pthread_mutex functions.
30790 - Don't save non-general-purpose router descriptors to the disk cache,
30791 because we have no way of remembering what their purpose was when
30793 - Add even more asserts to hunt down bug 417.
30794 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
30795 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
30796 Add a log message to confirm that it is in fact unlikely.
30798 o Minor bugfixes (controller):
30799 - Make 'getinfo fingerprint' return a 551 error if we're not a
30800 server, so we match what the control spec claims we do. Reported
30802 - Fix a typo in an error message when extendcircuit fails that
30803 caused us to not follow the \r\n-based delimiter protocol. Reported
30806 o Code simplifications and refactoring:
30807 - Stop passing around circuit_t and crypt_path_t pointers that are
30808 implicit in other procedure arguments.
30809 - Drop the old code to choke directory connections when the
30810 corresponding OR connections got full: thanks to the cell queue
30811 feature, OR conns don't get full any more.
30812 - Make dns_resolve() handle attaching connections to circuits
30813 properly, so the caller doesn't have to.
30814 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
30815 - Keep the connection array as a dynamic smartlist_t, rather than as
30816 a fixed-sized array. This is important, as the number of connections
30817 is becoming increasingly decoupled from the number of sockets.
30820 Changes in version 0.1.2.14 - 2007-05-25
30821 Tor 0.1.2.14 changes the addresses of two directory authorities (this
30822 change especially affects those who serve or use hidden services),
30823 and fixes several other crash- and security-related bugs.
30825 o Directory authority changes:
30826 - Two directory authorities (moria1 and moria2) just moved to new
30827 IP addresses. This change will particularly affect those who serve
30828 or use hidden services.
30830 o Major bugfixes (crashes):
30831 - If a directory server runs out of space in the connection table
30832 as it's processing a begin_dir request, it will free the exit stream
30833 but leave it attached to the circuit, leading to unpredictable
30834 behavior. (Reported by seeess, fixes bug 425.)
30835 - Fix a bug in dirserv_remove_invalid() that would cause authorities
30836 to corrupt memory under some really unlikely scenarios.
30837 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
30838 - Avoid segfaults when reading from mmaped descriptor file. (Reported
30841 o Major bugfixes (security):
30842 - When choosing an entry guard for a circuit, avoid using guards
30843 that are in the same family as the chosen exit -- not just guards
30844 that are exactly the chosen exit. (Reported by lodger.)
30846 o Major bugfixes (resource management):
30847 - If a directory authority is down, skip it when deciding where to get
30848 networkstatus objects or descriptors. Otherwise we keep asking
30849 every 10 seconds forever. Fixes bug 384.
30850 - Count it as a failure if we fetch a valid network-status but we
30851 don't want to keep it. Otherwise we'll keep fetching it and keep
30852 not wanting to keep it. Fixes part of bug 422.
30853 - If all of our dirservers have given us bad or no networkstatuses
30854 lately, then stop hammering them once per minute even when we
30855 think they're failed. Fixes another part of bug 422.
30858 - Actually set the purpose correctly for descriptors inserted with
30859 purpose=controller.
30860 - When we have k non-v2 authorities in our DirServer config,
30861 we ignored the last k authorities in the list when updating our
30863 - Correctly back-off from requesting router descriptors that we are
30864 having a hard time downloading.
30865 - Read resolv.conf files correctly on platforms where read() returns
30866 partial results on small file reads.
30867 - Don't rebuild the entire router store every time we get 32K of
30868 routers: rebuild it when the journal gets very large, or when
30869 the gaps in the store get very large.
30872 - When routers publish SVN revisions in their router descriptors,
30873 authorities now include those versions correctly in networkstatus
30875 - Warn when using a version of libevent before 1.3b to run a server on
30876 OSX or BSD: these versions interact badly with userspace threads.
30879 Changes in version 0.1.2.13 - 2007-04-24
30880 This release features some major anonymity fixes, such as safer path
30881 selection; better client performance; faster bootstrapping, better
30882 address detection, and better DNS support for servers; write limiting as
30883 well as read limiting to make servers easier to run; and a huge pile of
30884 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
30886 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
30887 of the Freenode IRC network, remembering his patience and vision for
30888 free speech on the Internet.
30891 - Fix a memory leak when we ask for "all" networkstatuses and we
30892 get one we don't recognize.
30893 - Add more asserts to hunt down bug 417.
30894 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
30897 Changes in version 0.1.2.12-rc - 2007-03-16
30899 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
30900 directory information requested inside Tor connections (i.e. via
30901 begin_dir cells). It only triggered when the same connection was
30902 serving other data at the same time. Reported by seeess.
30905 - When creating a circuit via the controller, send a 'launched'
30906 event when we're done, so we follow the spec better.
30909 Changes in version 0.1.2.11-rc - 2007-03-15
30910 o Minor bugfixes (controller), reported by daejees:
30911 - Correct the control spec to match how the code actually responds
30912 to 'getinfo addr-mappings/*'.
30913 - The control spec described a GUARDS event, but the code
30914 implemented a GUARD event. Standardize on GUARD, but let people
30915 ask for GUARDS too.
30918 Changes in version 0.1.2.10-rc - 2007-03-07
30919 o Major bugfixes (Windows):
30920 - Do not load the NT services library functions (which may not exist)
30921 just to detect if we're a service trying to shut down. Now we run
30922 on Win98 and friends again.
30924 o Minor bugfixes (other):
30925 - Clarify a couple of log messages.
30926 - Fix a misleading socks5 error number.
30929 Changes in version 0.1.2.9-rc - 2007-03-02
30930 o Major bugfixes (Windows):
30931 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
30932 of the usual GCC "%llu". This prevents a bug when saving 64-bit
30933 int configuration values: the high-order 32 bits would get
30934 truncated. In particular, we were being bitten by the default
30935 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
30936 and maybe also bug 397.)
30938 o Minor bugfixes (performance):
30939 - Use OpenSSL's AES implementation on platforms where it's faster.
30940 This could save us as much as 10% CPU usage.
30942 o Minor bugfixes (server):
30943 - Do not rotate onion key immediately after setting it for the first
30946 o Minor bugfixes (directory authorities):
30947 - Stop calling servers that have been hibernating for a long time
30948 "stable". Also, stop letting hibernating or obsolete servers affect
30949 uptime and bandwidth cutoffs.
30950 - Stop listing hibernating servers in the v1 directory.
30952 o Minor bugfixes (hidden services):
30953 - Upload hidden service descriptors slightly less often, to reduce
30954 load on authorities.
30956 o Minor bugfixes (other):
30957 - Fix an assert that could trigger if a controller quickly set then
30958 cleared EntryNodes. Bug found by Udo van den Heuvel.
30959 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
30961 - Fix a potential race condition in the rpm installer. Found by
30963 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
30964 of 2 as indicating that the server is completely bad; it sometimes
30965 means that the server is just bad for the request in question. (may fix
30966 the last of bug 326.)
30967 - Disable encrypted directory connections when we don't have a server
30968 descriptor for the destination. We'll get this working again in
30972 Changes in version 0.1.2.8-beta - 2007-02-26
30973 o Major bugfixes (crashes):
30974 - Stop crashing when the controller asks us to resetconf more than
30975 one config option at once. (Vidalia 0.0.11 does this.)
30976 - Fix a crash that happened on Win98 when we're given command-line
30977 arguments: don't try to load NT service functions from advapi32.dll
30978 except when we need them. (Bug introduced in 0.1.2.7-alpha;
30980 - Fix a longstanding obscure crash bug that could occur when
30981 we run out of DNS worker processes. (Resolves bug 390.)
30983 o Major bugfixes (hidden services):
30984 - Correctly detect whether hidden service descriptor downloads are
30985 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
30987 o Major bugfixes (accounting):
30988 - When we start during an accounting interval before it's time to wake
30989 up, remember to wake up at the correct time. (May fix bug 342.)
30991 o Minor bugfixes (controller):
30992 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
30993 clear the corresponding on_circuit variable, and remember later
30994 that we don't need to send a redundant CLOSED event. Resolves part
30996 - Report events where a resolve succeeded or where we got a socks
30997 protocol error correctly, rather than calling both of them
30999 - Change reported stream target addresses to IP consistently when
31000 we finally get the IP from an exit node.
31001 - Send log messages to the controller even if they happen to be very
31004 o Minor bugfixes (other):
31005 - Display correct results when reporting which versions are
31006 recommended, and how recommended they are. (Resolves bug 383.)
31007 - Improve our estimates for directory bandwidth to be less random:
31008 guess that an unrecognized directory will have the average bandwidth
31009 from all known directories, not that it will have the average
31010 bandwidth from those directories earlier than it on the list.
31011 - If we start a server with ClientOnly 1, then set ClientOnly to 0
31012 and hup, stop triggering an assert based on an empty onion_key.
31013 - On platforms with no working mmap() equivalent, don't warn the
31014 user when cached-routers doesn't exist.
31015 - Warn the user when mmap() [or its equivalent] fails for some reason
31016 other than file-not-found.
31017 - Don't warn the user when cached-routers.new doesn't exist: that's
31018 perfectly fine when starting up for the first time.
31019 - When EntryNodes are configured, rebuild the guard list to contain,
31020 in order: the EntryNodes that were guards before; the rest of the
31021 EntryNodes; the nodes that were guards before.
31022 - Mask out all signals in sub-threads; only the libevent signal
31023 handler should be processing them. This should prevent some crashes
31024 on some machines using pthreads. (Patch from coderman.)
31025 - Fix switched arguments on memset in the implementation of
31026 tor_munmap() for systems with no mmap() call.
31027 - When Tor receives a router descriptor that it asked for, but
31028 no longer wants (because it has received fresh networkstatuses
31029 in the meantime), do not warn the user. Cache the descriptor if
31030 we're a cache; drop it if we aren't.
31031 - Make earlier entry guards _really_ get retried when the network
31033 - On a malformed DNS reply, always give an error to the corresponding
31035 - Build with recent libevents on platforms that do not define the
31036 nonstandard types "u_int8_t" and friends.
31038 o Minor features (controller):
31039 - Warn the user when an application uses the obsolete binary v0
31040 control protocol. We're planning to remove support for it during
31041 the next development series, so it's good to give people some
31043 - Add STREAM_BW events to report per-entry-stream bandwidth
31044 use. (Patch from Robert Hogan.)
31045 - Rate-limit SIGNEWNYM signals in response to controllers that
31046 impolitely generate them for every single stream. (Patch from
31047 mwenge; closes bug 394.)
31048 - Make REMAP stream events have a SOURCE (cache or exit), and
31049 make them generated in every case where we get a successful
31050 connected or resolved cell.
31052 o Minor bugfixes (performance):
31053 - Call router_have_min_dir_info half as often. (This is showing up in
31054 some profiles, but not others.)
31055 - When using GCC, make log_debug never get called at all, and its
31056 arguments never get evaluated, when no debug logs are configured.
31057 (This is showing up in some profiles, but not others.)
31060 - Remove some never-implemented options. Mark PathlenCoinWeight as
31062 - Implement proposal 106: Stop requiring clients to have well-formed
31063 certificates; stop checking nicknames in certificates. (Clients
31064 have certificates so that they can look like Tor servers, but in
31065 the future we might want to allow them to look like regular TLS
31066 clients instead. Nicknames in certificates serve no purpose other
31067 than making our protocol easier to recognize on the wire.)
31068 - Revise messages on handshake failure again to be even more clear about
31069 which are incoming connections and which are outgoing.
31070 - Discard any v1 directory info that's over 1 month old (for
31071 directories) or over 1 week old (for running-routers lists).
31072 - Do not warn when individual nodes in the configuration's EntryNodes,
31073 ExitNodes, etc are down: warn only when all possible nodes
31074 are down. (Fixes bug 348.)
31075 - Always remove expired routers and networkstatus docs before checking
31076 whether we have enough information to build circuits. (Fixes
31078 - Put a lower-bound on MaxAdvertisedBandwidth.
31081 Changes in version 0.1.2.7-alpha - 2007-02-06
31082 o Major bugfixes (rate limiting):
31083 - Servers decline directory requests much more aggressively when
31084 they're low on bandwidth. Otherwise they end up queueing more and
31085 more directory responses, which can't be good for latency.
31086 - But never refuse directory requests from local addresses.
31087 - Fix a memory leak when sending a 503 response for a networkstatus
31089 - Be willing to read or write on local connections (e.g. controller
31090 connections) even when the global rate limiting buckets are empty.
31091 - If our system clock jumps back in time, don't publish a negative
31092 uptime in the descriptor. Also, don't let the global rate limiting
31093 buckets go absurdly negative.
31094 - Flush local controller connection buffers periodically as we're
31095 writing to them, so we avoid queueing 4+ megabytes of data before
31098 o Major bugfixes (NT services):
31099 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
31100 command-line flag so that admins can override the default by saying
31101 "tor --service install --user "SomeUser"". This will not affect
31102 existing installed services. Also, warn the user that the service
31103 will look for its configuration file in the service user's
31104 %appdata% directory. (We can't do the 'hardwire the user's appdata
31105 directory' trick any more, since we may not have read access to that
31108 o Major bugfixes (other):
31109 - Previously, we would cache up to 16 old networkstatus documents
31110 indefinitely, if they came from nontrusted authorities. Now we
31111 discard them if they are more than 10 days old.
31112 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
31114 - Detect and reject malformed DNS responses containing circular
31116 - If exits are rare enough that we're not marking exits as guards,
31117 ignore exit bandwidth when we're deciding the required bandwidth
31119 - When we're handling a directory connection tunneled over Tor,
31120 don't fill up internal memory buffers with all the data we want
31121 to tunnel; instead, only add it if the OR connection that will
31122 eventually receive it has some room for it. (This can lead to
31123 slowdowns in tunneled dir connections; a better solution will have
31124 to wait for 0.2.0.)
31126 o Minor bugfixes (dns):
31127 - Add some defensive programming to eventdns.c in an attempt to catch
31128 possible memory-stomping bugs.
31129 - Detect and reject DNS replies containing IPv4 or IPv6 records with
31130 an incorrect number of bytes. (Previously, we would ignore the
31132 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
31133 in the correct order, and doesn't crash.
31134 - Free memory held in recently-completed DNS lookup attempts on exit.
31135 This was not a memory leak, but may have been hiding memory leaks.
31136 - Handle TTL values correctly on reverse DNS lookups.
31137 - Treat failure to parse resolv.conf as an error.
31139 o Minor bugfixes (other):
31140 - Fix crash with "tor --list-fingerprint" (reported by seeess).
31141 - When computing clock skew from directory HTTP headers, consider what
31142 time it was when we finished asking for the directory, not what
31144 - Expire socks connections if they spend too long waiting for the
31145 handshake to finish. Previously we would let them sit around for
31146 days, if the connecting application didn't close them either.
31147 - And if the socks handshake hasn't started, don't send a
31148 "DNS resolve socks failed" handshake reply; just close it.
31149 - Stop using C functions that OpenBSD's linker doesn't like.
31150 - Don't launch requests for descriptors unless we have networkstatuses
31151 from at least half of the authorities. This delays the first
31152 download slightly under pathological circumstances, but can prevent
31153 us from downloading a bunch of descriptors we don't need.
31154 - Do not log IPs with TLS failures for incoming TLS
31155 connections. (Fixes bug 382.)
31156 - If the user asks to use invalid exit nodes, be willing to use
31158 - Stop using the reserved ac_cv namespace in our configure script.
31159 - Call stat() slightly less often; use fstat() when possible.
31160 - Refactor the way we handle pending circuits when an OR connection
31161 completes or fails, in an attempt to fix a rare crash bug.
31162 - Only rewrite a conn's address based on X-Forwarded-For: headers
31163 if it's a parseable public IP address; and stop adding extra quotes
31164 to the resulting address.
31167 - Weight directory requests by advertised bandwidth. Now we can
31168 let servers enable write limiting but still allow most clients to
31169 succeed at their directory requests. (We still ignore weights when
31170 choosing a directory authority; I hope this is a feature.)
31173 - Create a new file ReleaseNotes which was the old ChangeLog. The
31174 new ChangeLog file now includes the summaries for all development
31176 - Check for addresses with invalid characters at the exit as well
31177 as at the client, and warn less verbosely when they fail. You can
31178 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
31179 - Adapt a patch from goodell to let the contrib/exitlist script
31180 take arguments rather than require direct editing.
31181 - Inform the server operator when we decide not to advertise a
31182 DirPort due to AccountingMax enabled or a low BandwidthRate. It
31183 was confusing Zax, so now we're hopefully more helpful.
31184 - Bring us one step closer to being able to establish an encrypted
31185 directory tunnel without knowing a descriptor first. Still not
31186 ready yet. As part of the change, now assume we can use a
31187 create_fast cell if we don't know anything about a router.
31188 - Allow exit nodes to use nameservers running on ports other than 53.
31189 - Servers now cache reverse DNS replies.
31190 - Add an --ignore-missing-torrc command-line option so that we can
31191 get the "use sensible defaults if the configuration file doesn't
31192 exist" behavior even when specifying a torrc location on the command
31195 o Minor features (controller):
31196 - Track reasons for OR connection failure; make these reasons
31197 available via the controller interface. (Patch from Mike Perry.)
31198 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
31199 can learn when clients are sending malformed hostnames to Tor.
31200 - Clean up documentation for controller status events.
31201 - Add a REMAP status to stream events to note that a stream's
31202 address has changed because of a cached address or a MapAddress
31206 Changes in version 0.1.2.6-alpha - 2007-01-09
31208 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
31209 connection handles more than 4 gigs in either direction, we crash.
31210 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
31211 advertised exit node, somebody might try to exit from us when
31212 we're bootstrapping and before we've built our descriptor yet.
31213 Refuse the connection rather than crashing.
31216 - Warn if we (as a server) find that we've resolved an address that we
31217 weren't planning to resolve.
31218 - Warn that using select() on any libevent version before 1.1 will be
31219 unnecessarily slow (even for select()).
31220 - Flush ERR-level controller status events just like we currently
31221 flush ERR-level log events, so that a Tor shutdown doesn't prevent
31222 the controller from learning about current events.
31224 o Minor features (more controller status events):
31225 - Implement EXTERNAL_ADDRESS server status event so controllers can
31226 learn when our address changes.
31227 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
31228 can learn when directories reject our descriptor.
31229 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
31230 can learn when a client application is speaking a non-socks protocol
31232 - Implement DANGEROUS_SOCKS client status event so controllers
31233 can learn when a client application is leaking DNS addresses.
31234 - Implement BUG general status event so controllers can learn when
31235 Tor is unhappy about its internal invariants.
31236 - Implement CLOCK_SKEW general status event so controllers can learn
31237 when Tor thinks the system clock is set incorrectly.
31238 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
31239 server status events so controllers can learn when their descriptors
31240 are accepted by a directory.
31241 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
31242 server status events so controllers can learn about Tor's progress in
31243 deciding whether it's reachable from the outside.
31244 - Implement BAD_LIBEVENT general status event so controllers can learn
31245 when we have a version/method combination in libevent that needs to
31247 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
31248 and DNS_USELESS server status events so controllers can learn
31249 about changes to DNS server status.
31251 o Minor features (directory):
31252 - Authorities no longer recommend exits as guards if this would shift
31253 too much load to the exit nodes.
31256 Changes in version 0.1.2.5-alpha - 2007-01-06
31258 - Enable write limiting as well as read limiting. Now we sacrifice
31259 capacity if we're pushing out lots of directory traffic, rather
31260 than overrunning the user's intended bandwidth limits.
31261 - Include TLS overhead when counting bandwidth usage; previously, we
31262 would count only the bytes sent over TLS, but not the bytes used
31264 - Support running the Tor service with a torrc not in the same
31265 directory as tor.exe and default to using the torrc located in
31266 the %appdata%\Tor\ of the user who installed the service. Patch
31268 - Servers now check for the case when common DNS requests are going to
31269 wildcarded addresses (i.e. all getting the same answer), and change
31270 their exit policy to reject *:* if it's happening.
31271 - Implement BEGIN_DIR cells, so we can connect to the directory
31272 server via TLS to do encrypted directory requests rather than
31273 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
31274 config options if you like.
31276 o Minor features (config and docs):
31277 - Start using the state file to store bandwidth accounting data:
31278 the bw_accounting file is now obsolete. We'll keep generating it
31279 for a while for people who are still using 0.1.2.4-alpha.
31280 - Try to batch changes to the state file so that we do as few
31281 disk writes as possible while still storing important things in
31283 - The state file and the bw_accounting file get saved less often when
31284 the AvoidDiskWrites config option is set.
31285 - Make PIDFile work on Windows (untested).
31286 - Add internal descriptions for a bunch of configuration options:
31287 accessible via controller interface and in comments in saved
31289 - Reject *:563 (NNTPS) in the default exit policy. We already reject
31290 NNTP by default, so this seems like a sensible addition.
31291 - Clients now reject hostnames with invalid characters. This should
31292 avoid some inadvertent info leaks. Add an option
31293 AllowNonRFC953Hostnames to disable this behavior, in case somebody
31294 is running a private network with hosts called @, !, and #.
31295 - Add a maintainer script to tell us which options are missing
31296 documentation: "make check-docs".
31297 - Add a new address-spec.txt document to describe our special-case
31298 addresses: .exit, .onion, and .noconnnect.
31300 o Minor features (DNS):
31301 - Ongoing work on eventdns infrastructure: now it has dns server
31302 and ipv6 support. One day Tor will make use of it.
31303 - Add client-side caching for reverse DNS lookups.
31304 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
31305 - When we change nameservers or IP addresses, reset and re-launch
31306 our tests for DNS hijacking.
31308 o Minor features (directory):
31309 - Authorities now specify server versions in networkstatus. This adds
31310 about 2% to the size of compressed networkstatus docs, and allows
31311 clients to tell which servers support BEGIN_DIR and which don't.
31312 The implementation is forward-compatible with a proposed future
31313 protocol version scheme not tied to Tor versions.
31314 - DirServer configuration lines now have an orport= option so
31315 clients can open encrypted tunnels to the authorities without
31316 having downloaded their descriptors yet. Enabled for moria1,
31317 moria2, tor26, and lefkada now in the default configuration.
31318 - Directory servers are more willing to send a 503 "busy" if they
31319 are near their write limit, especially for v1 directory requests.
31320 Now they can use their limited bandwidth for actual Tor traffic.
31321 - Clients track responses with status 503 from dirservers. After a
31322 dirserver has given us a 503, we try not to use it until an hour has
31323 gone by, or until we have no dirservers that haven't given us a 503.
31324 - When we get a 503 from a directory, and we're not a server, we don't
31325 count the failure against the total number of failures allowed
31326 for the thing we're trying to download.
31327 - Report X-Your-Address-Is correctly from tunneled directory
31328 connections; don't report X-Your-Address-Is when it's an internal
31329 address; and never believe reported remote addresses when they're
31331 - Protect against an unlikely DoS attack on directory servers.
31332 - Add a BadDirectory flag to network status docs so that authorities
31333 can (eventually) tell clients about caches they believe to be
31336 o Minor features (controller):
31337 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
31338 - Reimplement GETINFO so that info/names stays in sync with the
31340 - Implement "GETINFO fingerprint".
31341 - Implement "SETEVENTS GUARD" so controllers can get updates on
31342 entry guard status as it changes.
31344 o Minor features (clean up obsolete pieces):
31345 - Remove some options that have been deprecated since at least
31346 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
31347 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
31348 to set log options.
31349 - We no longer look for identity and onion keys in "identity.key" and
31350 "onion.key" -- these were replaced by secret_id_key and
31351 secret_onion_key in 0.0.8pre1.
31352 - We no longer require unrecognized directory entries to be
31355 o Major bugfixes (security):
31356 - Stop sending the HttpProxyAuthenticator string to directory
31357 servers when directory connections are tunnelled through Tor.
31358 - Clients no longer store bandwidth history in the state file.
31359 - Do not log introduction points for hidden services if SafeLogging
31361 - When generating bandwidth history, round down to the nearest
31362 1k. When storing accounting data, round up to the nearest 1k.
31363 - When we're running as a server, remember when we last rotated onion
31364 keys, so that we will rotate keys once they're a week old even if
31365 we never stay up for a week ourselves.
31367 o Major bugfixes (other):
31368 - Fix a longstanding bug in eventdns that prevented the count of
31369 timed-out resolves from ever being reset. This bug caused us to
31370 give up on a nameserver the third time it timed out, and try it
31371 10 seconds later... and to give up on it every time it timed out
31373 - Take out the '5 second' timeout from the connection retry
31374 schedule. Now the first connect attempt will wait a full 10
31375 seconds before switching to a new circuit. Perhaps this will help
31376 a lot. Based on observations from Mike Perry.
31377 - Fix a bug on the Windows implementation of tor_mmap_file() that
31378 would prevent the cached-routers file from ever loading. Reported
31382 - Fix an assert failure when a directory authority sets
31383 AuthDirRejectUnlisted and then receives a descriptor from an
31384 unlisted router. Reported by seeess.
31385 - Avoid a double-free when parsing malformed DirServer lines.
31386 - Fix a bug when a BSD-style PF socket is first used. Patch from
31388 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
31389 to resolve an address at a given exit node even when they ask for
31391 - Servers no longer ever list themselves in their "family" line,
31392 even if configured to do so. This makes it easier to configure
31393 family lists conveniently.
31394 - When running as a server, don't fall back to 127.0.0.1 when no
31395 nameservers are configured in /etc/resolv.conf; instead, make the
31396 user fix resolv.conf or specify nameservers explicitly. (Resolves
31398 - Stop accepting certain malformed ports in configured exit policies.
31399 - Don't re-write the fingerprint file every restart, unless it has
31401 - Stop warning when a single nameserver fails: only warn when _all_ of
31402 our nameservers have failed. Also, when we only have one nameserver,
31403 raise the threshold for deciding that the nameserver is dead.
31404 - Directory authorities now only decide that routers are reachable
31405 if their identity keys are as expected.
31406 - When the user uses bad syntax in the Log config line, stop
31407 suggesting other bad syntax as a replacement.
31408 - Correctly detect ipv6 DNS capability on OpenBSD.
31410 o Minor bugfixes (controller):
31411 - Report the circuit number correctly in STREAM CLOSED events. Bug
31412 reported by Mike Perry.
31413 - Do not report bizarre values for results of accounting GETINFOs
31414 when the last second's write or read exceeds the allotted bandwidth.
31415 - Report "unrecognized key" rather than an empty string when the
31416 controller tries to fetch a networkstatus that doesn't exist.
31419 Changes in version 0.1.1.26 - 2006-12-14
31420 o Security bugfixes:
31421 - Stop sending the HttpProxyAuthenticator string to directory
31422 servers when directory connections are tunnelled through Tor.
31423 - Clients no longer store bandwidth history in the state file.
31424 - Do not log introduction points for hidden services if SafeLogging
31428 - Fix an assert failure when a directory authority sets
31429 AuthDirRejectUnlisted and then receives a descriptor from an
31430 unlisted router (reported by seeess).
31433 Changes in version 0.1.2.4-alpha - 2006-12-03
31435 - Add support for using natd; this allows FreeBSDs earlier than
31436 5.1.2 to have ipfw send connections through Tor without using
31437 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
31440 - Make all connections to addresses of the form ".noconnect"
31441 immediately get closed. This lets application/controller combos
31442 successfully test whether they're talking to the same Tor by
31443 watching for STREAM events.
31444 - Make cross.sh cross-compilation script work even when autogen.sh
31445 hasn't been run. (Patch from Michael Mohr.)
31446 - Statistics dumped by -USR2 now include a breakdown of public key
31447 operations, for profiling.
31450 - Fix a major leak when directory authorities parse their
31451 approved-routers list, a minor memory leak when we fail to pick
31452 an exit node, and a few rare leaks on errors.
31453 - Handle TransPort connections even when the server sends data before
31454 the client sends data. Previously, the connection would just hang
31455 until the client sent data. (Patch from tup based on patch from
31457 - Avoid assert failure when our cached-routers file is empty on
31461 - Don't log spurious warnings when we see a circuit close reason we
31462 don't recognize; it's probably just from a newer version of Tor.
31463 - Have directory authorities allow larger amounts of drift in uptime
31464 without replacing the server descriptor: previously, a server that
31465 restarted every 30 minutes could have 48 "interesting" descriptors
31467 - Start linking to the Tor specification and Tor reference manual
31468 correctly in the Windows installer.
31469 - Add Vidalia to the OS X uninstaller script, so when we uninstall
31470 Tor/Privoxy we also uninstall Vidalia.
31471 - Resume building on Irix64, and fix a lot of warnings from its
31472 MIPSpro C compiler.
31473 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
31474 when we're running as a client.
31477 Changes in version 0.1.1.25 - 2006-11-04
31479 - When a client asks us to resolve (rather than connect to)
31480 an address, and we have a cached answer, give them the cached
31481 answer. Previously, we would give them no answer at all.
31482 - We were building exactly the wrong circuits when we predict
31483 hidden service requirements, meaning Tor would have to build all
31484 its circuits on demand.
31485 - If none of our live entry guards have a high uptime, but we
31486 require a guard with a high uptime, try adding a new guard before
31487 we give up on the requirement. This patch should make long-lived
31488 connections more stable on average.
31489 - When testing reachability of our DirPort, don't launch new
31490 tests when there's already one in progress -- unreachable
31491 servers were stacking up dozens of testing streams.
31493 o Security bugfixes:
31494 - When the user sends a NEWNYM signal, clear the client-side DNS
31495 cache too. Otherwise we continue to act on previous information.
31498 - Avoid a memory corruption bug when creating a hash table for
31500 - Avoid possibility of controller-triggered crash when misusing
31501 certain commands from a v0 controller on platforms that do not
31502 handle printf("%s",NULL) gracefully.
31503 - Avoid infinite loop on unexpected controller input.
31504 - Don't log spurious warnings when we see a circuit close reason we
31505 don't recognize; it's probably just from a newer version of Tor.
31506 - Add Vidalia to the OS X uninstaller script, so when we uninstall
31507 Tor/Privoxy we also uninstall Vidalia.
31510 Changes in version 0.1.2.3-alpha - 2006-10-29
31512 - Prepare for servers to publish descriptors less often: never
31513 discard a descriptor simply for being too old until either it is
31514 recommended by no authorities, or until we get a better one for
31515 the same router. Make caches consider retaining old recommended
31516 routers for even longer.
31517 - If most authorities set a BadExit flag for a server, clients
31518 don't think of it as a general-purpose exit. Clients only consider
31519 authorities that advertise themselves as listing bad exits.
31520 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
31521 headers for content, so that we can work better in the presence of
31522 caching HTTP proxies.
31523 - Allow authorities to list nodes as bad exits by fingerprint or by
31526 o Minor features, controller:
31527 - Add a REASON field to CIRC events; for backward compatibility, this
31528 field is sent only to controllers that have enabled the extended
31529 event format. Also, add additional reason codes to explain why
31530 a given circuit has been destroyed or truncated. (Patches from
31532 - Add a REMOTE_REASON field to extended CIRC events to tell the
31533 controller about why a remote OR told us to close a circuit.
31534 - Stream events also now have REASON and REMOTE_REASON fields,
31535 working much like those for circuit events.
31536 - There's now a GETINFO ns/... field so that controllers can ask Tor
31537 about the current status of a router.
31538 - A new event type "NS" to inform a controller when our opinion of
31539 a router's status has changed.
31540 - Add a GETINFO events/names and GETINFO features/names so controllers
31541 can tell which events and features are supported.
31542 - A new CLEARDNSCACHE signal to allow controllers to clear the
31543 client-side DNS cache without expiring circuits.
31545 o Security bugfixes:
31546 - When the user sends a NEWNYM signal, clear the client-side DNS
31547 cache too. Otherwise we continue to act on previous information.
31550 - Avoid sending junk to controllers or segfaulting when a controller
31551 uses EVENT_NEW_DESC with verbose nicknames.
31552 - Stop triggering asserts if the controller tries to extend hidden
31553 service circuits (reported by mwenge).
31554 - Avoid infinite loop on unexpected controller input.
31555 - When the controller does a "GETINFO network-status", tell it
31556 about even those routers whose descriptors are very old, and use
31557 long nicknames where appropriate.
31558 - Change NT service functions to be loaded on demand. This lets us
31559 build with MinGW without breaking Tor for Windows 98 users.
31560 - Do DirPort reachability tests less often, since a single test
31561 chews through many circuits before giving up.
31562 - In the hidden service example in torrc.sample, stop recommending
31563 esoteric and discouraged hidden service options.
31564 - When stopping an NT service, wait up to 10 sec for it to actually
31565 stop. Patch from Matt Edman; resolves bug 295.
31566 - Fix handling of verbose nicknames with ORCONN controller events:
31567 make them show up exactly when requested, rather than exactly when
31569 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
31570 printing a duplicate "$" in the keys we send (reported by mwenge).
31571 - Correctly set maximum connection limit on Cygwin. (This time
31573 - Try to detect Windows correctly when cross-compiling.
31574 - Detect the size of the routers file correctly even if it is
31575 corrupted (on systems without mmap) or not page-aligned (on systems
31576 with mmap). This bug was harmless.
31577 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
31578 to open a stream fails; now we do in more cases. This should
31579 make clients able to find a good exit faster in some cases, since
31580 unhandleable requests will now get an error rather than timing out.
31581 - Resolve two memory leaks when rebuilding the on-disk router cache
31582 (reported by fookoowa).
31583 - Clean up minor code warnings suggested by the MIPSpro C compiler,
31584 and reported by some Centos users.
31585 - Controller signals now work on non-Unix platforms that don't define
31586 SIGUSR1 and SIGUSR2 the way we expect.
31587 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
31588 values before failing, and always enables eventdns.
31589 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
31590 Try to fix this in configure.in by checking for most functions
31591 before we check for libevent.
31594 Changes in version 0.1.2.2-alpha - 2006-10-07
31596 - Make our async eventdns library on-by-default for Tor servers,
31597 and plan to deprecate the separate dnsworker threads.
31598 - Add server-side support for "reverse" DNS lookups (using PTR
31599 records so clients can determine the canonical hostname for a given
31600 IPv4 address). Only supported by servers using eventdns; servers
31601 now announce in their descriptors whether they support eventdns.
31602 - Specify and implement client-side SOCKS5 interface for reverse DNS
31603 lookups (see doc/socks-extensions.txt).
31604 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
31605 connect to directory servers through Tor. Previously, clients needed
31606 to find Tor exits to make private connections to directory servers.
31607 - Avoid choosing Exit nodes for entry or middle hops when the
31608 total bandwidth available from non-Exit nodes is much higher than
31609 the total bandwidth available from Exit nodes.
31610 - Workaround for name servers (like Earthlink's) that hijack failing
31611 DNS requests and replace the no-such-server answer with a "helpful"
31612 redirect to an advertising-driven search portal. Also work around
31613 DNS hijackers who "helpfully" decline to hijack known-invalid
31614 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
31615 lets you turn it off.
31616 - Send out a burst of long-range padding cells once we've established
31617 that we're reachable. Spread them over 4 circuits, so hopefully
31618 a few will be fast. This exercises our bandwidth and bootstraps
31619 us into the directory more quickly.
31621 o New/improved config options:
31622 - Add new config option "ResolvConf" to let the server operator
31623 choose an alternate resolve.conf file when using eventdns.
31624 - Add an "EnforceDistinctSubnets" option to control our "exclude
31625 servers on the same /16" behavior. It's still on by default; this
31626 is mostly for people who want to operate private test networks with
31627 all the machines on the same subnet.
31628 - If one of our entry guards is on the ExcludeNodes list, or the
31629 directory authorities don't think it's a good guard, treat it as
31630 if it were unlisted: stop using it as a guard, and throw it off
31631 the guards list if it stays that way for a long time.
31632 - Allow directory authorities to be marked separately as authorities
31633 for the v1 directory protocol, the v2 directory protocol, and
31634 as hidden service directories, to make it easier to retire old
31635 authorities. V1 authorities should set "HSAuthoritativeDir 1"
31636 to continue being hidden service authorities too.
31637 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
31639 o Minor features, controller:
31640 - Fix CIRC controller events so that controllers can learn the
31641 identity digests of non-Named servers used in circuit paths.
31642 - Let controllers ask for more useful identifiers for servers. Instead
31643 of learning identity digests for un-Named servers and nicknames
31644 for Named servers, the new identifiers include digest, nickname,
31645 and indication of Named status. Off by default; see control-spec.txt
31646 for more information.
31647 - Add a "getinfo address" controller command so it can display Tor's
31648 best guess to the user.
31649 - New controller event to alert the controller when our server
31650 descriptor has changed.
31651 - Give more meaningful errors on controller authentication failure.
31653 o Minor features, other:
31654 - When asked to resolve a hostname, don't use non-exit servers unless
31655 requested to do so. This allows servers with broken DNS to be
31656 useful to the network.
31657 - Divide eventdns log messages into warn and info messages.
31658 - Reserve the nickname "Unnamed" for routers that can't pick
31659 a hostname: any router can call itself Unnamed; directory
31660 authorities will never allocate Unnamed to any particular router;
31661 clients won't believe that any router is the canonical Unnamed.
31662 - Only include function names in log messages for info/debug messages.
31663 For notice/warn/err, the content of the message should be clear on
31664 its own, and printing the function name only confuses users.
31665 - Avoid some false positives during reachability testing: don't try
31666 to test via a server that's on the same /24 as us.
31667 - If we fail to build a circuit to an intended enclave, and it's
31668 not mandatory that we use that enclave, stop wanting it.
31669 - When eventdns is enabled, allow multithreaded builds on NetBSD and
31670 OpenBSD. (We had previously disabled threads on these platforms
31671 because they didn't have working thread-safe resolver functions.)
31673 o Major bugfixes, anonymity/security:
31674 - If a client asked for a server by name, and there's a named server
31675 in our network-status but we don't have its descriptor yet, we
31676 could return an unnamed server instead.
31677 - Fix NetBSD bug that could allow someone to force uninitialized RAM
31678 to be sent to a server's DNS resolver. This only affects NetBSD
31679 and other platforms that do not bounds-check tolower().
31680 - Reject (most) attempts to use Tor circuits with length one. (If
31681 many people start using Tor as a one-hop proxy, exit nodes become
31682 a more attractive target for compromise.)
31683 - Just because your DirPort is open doesn't mean people should be
31684 able to remotely teach you about hidden service descriptors. Now
31685 only accept rendezvous posts if you've got HSAuthoritativeDir set.
31687 o Major bugfixes, other:
31688 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
31689 - When a client asks the server to resolve (not connect to)
31690 an address, and it has a cached answer, give them the cached answer.
31691 Previously, the server would give them no answer at all.
31692 - Allow really slow clients to not hang up five minutes into their
31693 directory downloads (suggested by Adam J. Richter).
31694 - We were building exactly the wrong circuits when we anticipated
31695 hidden service requirements, meaning Tor would have to build all
31696 its circuits on demand.
31697 - Avoid crashing when we mmap a router cache file of size 0.
31698 - When testing reachability of our DirPort, don't launch new
31699 tests when there's already one in progress -- unreachable
31700 servers were stacking up dozens of testing streams.
31702 o Minor bugfixes, correctness:
31703 - If we're a directory mirror and we ask for "all" network status
31704 documents, we would discard status documents from authorities
31705 we don't recognize.
31706 - Avoid a memory corruption bug when creating a hash table for
31708 - Avoid controller-triggered crash when misusing certain commands
31709 from a v0 controller on platforms that do not handle
31710 printf("%s",NULL) gracefully.
31711 - Don't crash when a controller sends a third argument to an
31712 "extendcircuit" request.
31713 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
31714 response; fix error code when "getinfo dir/status/" fails.
31715 - Avoid crash when telling controller stream-status and a stream
31717 - Patch from Adam Langley to fix assert() in eventdns.c.
31718 - Fix a debug log message in eventdns to say "X resolved to Y"
31719 instead of "X resolved to X".
31720 - Make eventdns give strings for DNS errors, not just error numbers.
31721 - Track unreachable entry guards correctly: don't conflate
31722 'unreachable by us right now' with 'listed as down by the directory
31723 authorities'. With the old code, if a guard was unreachable by
31724 us but listed as running, it would clog our guard list forever.
31725 - Behave correctly in case we ever have a network with more than
31726 2GB/s total advertised capacity.
31727 - Make TrackExitHosts case-insensitive, and fix the behavior of
31728 ".suffix" TrackExitHosts items to avoid matching in the middle of
31730 - Finally fix the openssl warnings from newer gccs that believe that
31731 ignoring a return value is okay, but casting a return value and
31732 then ignoring it is a sign of madness.
31733 - Prevent the contrib/exitlist script from printing the same
31734 result more than once.
31735 - Patch from Steve Hildrey: Generate network status correctly on
31736 non-versioning dirservers.
31737 - Don't listen to the X-Your-Address-Is hint if you did the lookup
31738 via Tor; otherwise you'll think you're the exit node's IP address.
31740 o Minor bugfixes, performance:
31741 - Two small performance improvements on parsing descriptors.
31742 - Major performance improvement on inserting descriptors: change
31743 algorithm from O(n^2) to O(n).
31744 - Make the common memory allocation path faster on machines where
31745 malloc(0) returns a pointer.
31746 - Start remembering X-Your-Address-Is directory hints even if you're
31747 a client, so you can become a server more smoothly.
31748 - Avoid duplicate entries on MyFamily line in server descriptor.
31750 o Packaging, features:
31751 - Remove architecture from OS X builds. The official builds are
31752 now universal binaries.
31753 - The Debian package now uses --verify-config when (re)starting,
31754 to distinguish configuration errors from other errors.
31755 - Update RPMs to require libevent 1.1b.
31757 o Packaging, bugfixes:
31758 - Patches so Tor builds with MinGW on Windows.
31759 - Patches so Tor might run on Cygwin again.
31760 - Resume building on non-gcc compilers and ancient gcc. Resume
31761 building with the -O0 compile flag. Resume building cleanly on
31763 - Run correctly on OS X platforms with case-sensitive filesystems.
31764 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
31765 - Add autoconf checks so Tor can build on Solaris x86 again.
31768 - Documented (and renamed) ServerDNSSearchDomains and
31769 ServerDNSResolvConfFile options.
31770 - Be clearer that the *ListenAddress directives can be repeated
31774 Changes in version 0.1.1.24 - 2006-09-29
31776 - Allow really slow clients to not hang up five minutes into their
31777 directory downloads (suggested by Adam J. Richter).
31778 - Fix major performance regression from 0.1.0.x: instead of checking
31779 whether we have enough directory information every time we want to
31780 do something, only check when the directory information has changed.
31781 This should improve client CPU usage by 25-50%.
31782 - Don't crash if, after a server has been running for a while,
31783 it can't resolve its hostname.
31786 - Allow Tor to start when RunAsDaemon is set but no logs are set.
31787 - Don't crash when the controller receives a third argument to an
31788 "extendcircuit" request.
31789 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
31790 response; fix error code when "getinfo dir/status/" fails.
31791 - Fix configure.in to not produce broken configure files with
31792 more recent versions of autoconf. Thanks to Clint for his auto*
31794 - Fix security bug on NetBSD that could allow someone to force
31795 uninitialized RAM to be sent to a server's DNS resolver. This
31796 only affects NetBSD and other platforms that do not bounds-check
31798 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
31799 methods: these are known to be buggy.
31800 - If we're a directory mirror and we ask for "all" network status
31801 documents, we would discard status documents from authorities
31802 we don't recognize.
31805 Changes in version 0.1.2.1-alpha - 2006-08-27
31807 - Add "eventdns" async dns library from Adam Langley, tweaked to
31808 build on OSX and Windows. Only enabled if you pass the
31809 --enable-eventdns argument to configure.
31810 - Allow servers with no hostname or IP address to learn their
31811 IP address by asking the directory authorities. This code only
31812 kicks in when you would normally have exited with a "no address"
31813 error. Nothing's authenticated, so use with care.
31814 - Rather than waiting a fixed amount of time between retrying
31815 application connections, we wait only 5 seconds for the first,
31816 10 seconds for the second, and 15 seconds for each retry after
31817 that. Hopefully this will improve the expected user experience.
31818 - Patch from Tup to add support for transparent AP connections:
31819 this basically bundles the functionality of trans-proxy-tor
31820 into the Tor mainline. Now hosts with compliant pf/netfilter
31821 implementations can redirect TCP connections straight to Tor
31822 without diverting through SOCKS. Needs docs.
31823 - Busy directory servers save lots of memory by spooling server
31824 descriptors, v1 directories, and v2 networkstatus docs to buffers
31825 as needed rather than en masse. Also mmap the cached-routers
31826 files, so we don't need to keep the whole thing in memory too.
31827 - Automatically avoid picking more than one node from the same
31828 /16 network when constructing a circuit.
31829 - Revise and clean up the torrc.sample that we ship with; add
31830 a section for BandwidthRate and BandwidthBurst.
31833 - Split circuit_t into origin_circuit_t and or_circuit_t, and
31834 split connection_t into edge, or, dir, control, and base structs.
31835 These will save quite a bit of memory on busy servers, and they'll
31836 also help us track down bugs in the code and bugs in the spec.
31837 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
31838 or later. Log when we are doing this, so we can diagnose it when
31839 it fails. (Also, recommend libevent 1.1b for kqueue and
31840 win32 methods; deprecate libevent 1.0b harder; make libevent
31841 recommendation system saner.)
31842 - Start being able to build universal binaries on OS X (thanks
31844 - Export the default exit policy via the control port, so controllers
31845 don't need to guess what it is / will be later.
31846 - Add a man page entry for ProtocolWarnings.
31847 - Add TestVia config option to the man page.
31848 - Remove even more protocol-related warnings from Tor server logs,
31849 such as bad TLS handshakes and malformed begin cells.
31850 - Stop fetching descriptors if you're not a dir mirror and you
31851 haven't tried to establish any circuits lately. [This currently
31852 causes some dangerous behavior, because when you start up again
31853 you'll use your ancient server descriptors.]
31854 - New DirPort behavior: if you have your dirport set, you download
31855 descriptors aggressively like a directory mirror, whether or not
31856 your ORPort is set.
31857 - Get rid of the router_retry_connections notion. Now routers
31858 no longer try to rebuild long-term connections to directory
31859 authorities, and directory authorities no longer try to rebuild
31860 long-term connections to all servers. We still don't hang up
31861 connections in these two cases though -- we need to look at it
31862 more carefully to avoid flapping, and we likely need to wait til
31863 0.1.1.x is obsolete.
31864 - Drop compatibility with obsolete Tors that permit create cells
31865 to have the wrong circ_id_type.
31866 - Re-enable per-connection rate limiting. Get rid of the "OP
31867 bandwidth" concept. Lay groundwork for "bandwidth classes" --
31868 separate global buckets that apply depending on what sort of conn
31870 - Start publishing one minute or so after we find our ORPort
31871 to be reachable. This will help reduce the number of descriptors
31872 we have for ourselves floating around, since it's quite likely
31873 other things (e.g. DirPort) will change during that minute too.
31874 - Fork the v1 directory protocol into its own spec document,
31875 and mark dir-spec.txt as the currently correct (v2) spec.
31878 - When we find our DirPort to be reachable, publish a new descriptor
31879 so we'll tell the world (reported by pnx).
31880 - Publish a new descriptor after we hup/reload. This is important
31881 if our config has changed such that we'll want to start advertising
31882 our DirPort now, etc.
31883 - Allow Tor to start when RunAsDaemon is set but no logs are set.
31884 - When we have a state file we cannot parse, tell the user and
31885 move it aside. Now we avoid situations where the user starts
31886 Tor in 1904, Tor writes a state file with that timestamp in it,
31887 the user fixes her clock, and Tor refuses to start.
31888 - Fix configure.in to not produce broken configure files with
31889 more recent versions of autoconf. Thanks to Clint for his auto*
31891 - "tor --verify-config" now exits with -1(255) or 0 depending on
31892 whether the config options are bad or good.
31893 - Resolve bug 321 when using dnsworkers: append a period to every
31894 address we resolve at the exit node, so that we do not accidentally
31895 pick up local addresses, and so that failing searches are retried
31896 in the resolver search domains. (This is already solved for
31897 eventdns.) (This breaks Blossom servers for now.)
31898 - If we are using an exit enclave and we can't connect, e.g. because
31899 its webserver is misconfigured to not listen on localhost, then
31900 back off and try connecting from somewhere else before we fail.
31903 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
31904 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
31905 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
31906 when the IP address is mapped through MapAddress to a hostname.
31907 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
31908 useless IPv6 DNS resolves.
31909 - Patch suggested by Karsten Loesing: respond to SIGNAL command
31910 before we execute the signal, in case the signal shuts us down.
31911 - Clean up AllowInvalidNodes man page entry.
31912 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
31913 - Add more asserts to track down an assert error on a windows Tor
31914 server with connection_add being called with socket == -1.
31915 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
31916 - Fix misleading log messages: an entry guard that is "unlisted",
31917 as well as not known to be "down" (because we've never heard
31918 of it), is not therefore "up".
31919 - Remove code to special-case "-cvs" ending, since it has not
31920 actually mattered since 0.0.9.
31921 - Make our socks5 handling more robust to broken socks clients:
31922 throw out everything waiting on the buffer in between socks
31923 handshake phases, since they can't possibly (so the theory
31924 goes) have predicted what we plan to respond to them.
31927 Changes in version 0.1.1.23 - 2006-07-30
31929 - Fast Tor servers, especially exit nodes, were triggering asserts
31930 due to a bug in handling the list of pending DNS resolves. Some
31931 bugs still remain here; we're hunting them.
31932 - Entry guards could crash clients by sending unexpected input.
31933 - More fixes on reachability testing: if you find yourself reachable,
31934 then don't ever make any client requests (so you stop predicting
31935 circuits), then hup or have your clock jump, then later your IP
31936 changes, you won't think circuits are working, so you won't try to
31937 test reachability, so you won't publish.
31940 - Avoid a crash if the controller does a resetconf firewallports
31941 and then a setconf fascistfirewall=1.
31942 - Avoid an integer underflow when the dir authority decides whether
31943 a router is stable: we might wrongly label it stable, and compute
31944 a slightly wrong median stability, when a descriptor is published
31946 - Fix a place where we might trigger an assert if we can't build our
31947 own server descriptor yet.
31950 Changes in version 0.1.1.22 - 2006-07-05
31952 - Fix a big bug that was causing servers to not find themselves
31953 reachable if they changed IP addresses. Since only 0.1.1.22+
31954 servers can do reachability testing correctly, now we automatically
31955 make sure to test via one of these.
31956 - Fix to allow clients and mirrors to learn directory info from
31957 descriptor downloads that get cut off partway through.
31958 - Directory authorities had a bug in deciding if a newly published
31959 descriptor was novel enough to make everybody want a copy -- a few
31960 servers seem to be publishing new descriptors many times a minute.
31962 - Fix a rare bug that was causing some servers to complain about
31963 "closing wedged cpuworkers" and skip some circuit create requests.
31964 - Make the Exit flag in directory status documents actually work.
31967 Changes in version 0.1.1.21 - 2006-06-10
31968 o Crash and assert fixes from 0.1.1.20:
31969 - Fix a rare crash on Tor servers that have enabled hibernation.
31970 - Fix a seg fault on startup for Tor networks that use only one
31971 directory authority.
31972 - Fix an assert from a race condition that occurs on Tor servers
31973 while exiting, where various threads are trying to log that they're
31974 exiting, and delete the logs, at the same time.
31975 - Make our unit tests pass again on certain obscure platforms.
31978 - Add support for building SUSE RPM packages.
31979 - Speed up initial bootstrapping for clients: if we are making our
31980 first ever connection to any entry guard, then don't mark it down
31982 - When only one Tor server in the network is labelled as a guard,
31983 and we've already picked him, we would cycle endlessly picking him
31984 again, being unhappy about it, etc. Now we specifically exclude
31985 current guards when picking a new guard.
31986 - Servers send create cells more reliably after the TLS connection
31987 is established: we were sometimes forgetting to send half of them
31988 when we had more than one pending.
31989 - If we get a create cell that asks us to extend somewhere, but the
31990 Tor server there doesn't match the expected digest, we now send
31991 a destroy cell back, rather than silently doing nothing.
31992 - Make options->RedirectExit work again.
31993 - Make cookie authentication for the controller work again.
31994 - Stop being picky about unusual characters in the arguments to
31995 mapaddress. It's none of our business.
31996 - Add a new config option "TestVia" that lets you specify preferred
31997 middle hops to use for test circuits. Perhaps this will let me
31998 debug the reachability problems better.
32000 o Log / documentation fixes:
32001 - If we're a server and some peer has a broken TLS certificate, don't
32002 log about it unless ProtocolWarnings is set, i.e., we want to hear
32003 about protocol violations by others.
32004 - Fix spelling of VirtualAddrNetwork in man page.
32005 - Add a better explanation at the top of the autogenerated torrc file
32006 about what happened to our old torrc.
32009 Changes in version 0.1.1.20 - 2006-05-23
32011 - Downgrade a log severity where servers complain that they're
32013 - Avoid a compile warning on FreeBSD.
32014 - Remove string size limit on NEWDESC messages; solve bug 291.
32015 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
32016 more thoroughly when we're running on windows.
32019 Changes in version 0.1.1.19-rc - 2006-05-03
32021 - Regenerate our local descriptor if it's dirty and we try to use
32022 it locally (e.g. if it changes during reachability detection).
32023 - If we setconf our ORPort to 0, we continued to listen on the
32024 old ORPort and receive connections.
32025 - Avoid a second warning about machine/limits.h on Debian
32027 - Be willing to add our own routerinfo into the routerlist.
32028 Now authorities will include themselves in their directories
32029 and network-statuses.
32030 - Stop trying to upload rendezvous descriptors to every
32031 directory authority: only try the v1 authorities.
32032 - Servers no longer complain when they think they're not
32033 registered with the directory authorities. There were too many
32035 - Backport dist-rpm changes so rpms can be built without errors.
32038 - Implement an option, VirtualAddrMask, to set which addresses
32039 get handed out in response to mapaddress requests. This works
32040 around a bug in tsocks where 127.0.0.0/8 is never socksified.
32043 Changes in version 0.1.1.18-rc - 2006-04-10
32045 - Work harder to download live network-statuses from all the
32046 directory authorities we know about. Improve the threshold
32047 decision logic so we're more robust to edge cases.
32048 - When fetching rendezvous descriptors, we were willing to ask
32049 v2 authorities too, which would always return 404.
32052 - Stop listing down or invalid nodes in the v1 directory. This will
32053 reduce its bulk by about 1/3, and reduce load on directory
32055 - When deciding whether a router is Fast or Guard-worthy, consider
32056 his advertised BandwidthRate and not just the BandwidthCapacity.
32057 - No longer ship INSTALL and README files -- they are useless now.
32058 - Force rpmbuild to behave and honor target_cpu.
32059 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
32060 - Start to include translated versions of the tor-doc-*.html
32061 files, along with the screenshots. Still needs more work.
32062 - Start sending back 512 and 451 errors if mapaddress fails,
32063 rather than not sending anything back at all.
32064 - When we fail to bind or listen on an incoming or outgoing
32065 socket, we should close it before failing. otherwise we just
32066 leak it. (thanks to weasel for finding.)
32067 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
32068 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
32069 - Make NoPublish (even though deprecated) work again.
32070 - Fix a minor security flaw where a versioning auth dirserver
32071 could list a recommended version many times in a row to make
32072 clients more convinced that it's recommended.
32073 - Fix crash bug if there are two unregistered servers running
32074 with the same nickname, one of them is down, and you ask for
32075 them by nickname in your EntryNodes or ExitNodes. Also, try
32076 to pick the one that's running rather than an arbitrary one.
32077 - Fix an infinite loop we could hit if we go offline for too long.
32078 - Complain when we hit WSAENOBUFS on recv() or write() too.
32079 Perhaps this will help us hunt the bug.
32080 - If you're not a versioning dirserver, don't put the string
32081 "client-versions \nserver-versions \n" in your network-status.
32082 - Lower the minimum required number of file descriptors to 1000,
32083 so we can have some overhead for Valgrind on Linux, where the
32084 default ulimit -n is 1024.
32087 - Add tor.dizum.com as the fifth authoritative directory server.
32088 - Add a new config option FetchUselessDescriptors, off by default,
32089 for when you plan to run "exitlist" on your client and you want
32090 to know about even the non-running descriptors.
32093 Changes in version 0.1.1.17-rc - 2006-03-28
32095 - Clients and servers since 0.1.1.10-alpha have been expiring
32096 connections whenever they are idle for 5 minutes and they *do*
32097 have circuits on them. Oops. With this new version, clients will
32098 discard their previous entry guard choices and avoid choosing
32099 entry guards running these flawed versions.
32100 - Fix memory leak when uncompressing concatenated zlib streams. This
32101 was causing substantial leaks over time on Tor servers.
32102 - The v1 directory was including servers as much as 48 hours old,
32103 because that's how the new routerlist->routers works. Now only
32104 include them if they're 20 hours old or less.
32107 - Resume building on irix64, netbsd 2.0, etc.
32108 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
32110 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
32111 and it is confusing some users.
32112 - Mirrors stop caching the v1 directory so often.
32113 - Make the max number of old descriptors that a cache will hold
32114 rise with the number of directory authorities, so we can scale.
32115 - Change our win32 uname() hack to be more forgiving about what
32116 win32 versions it thinks it's found.
32119 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
32121 - When the controller's *setconf commands fail, collect an error
32122 message in a string and hand it back to the controller.
32123 - Make the v2 dir's "Fast" flag based on relative capacity, just
32124 like "Stable" is based on median uptime. Name everything in the
32125 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
32126 - Log server fingerprint on startup, so new server operators don't
32127 have to go hunting around their filesystem for it.
32128 - Return a robots.txt on our dirport to discourage google indexing.
32129 - Let the controller ask for GETINFO dir/status/foo so it can ask
32130 directly rather than connecting to the dir port. Only works when
32131 dirport is set for now.
32133 o New config options rather than constants in the code:
32134 - SocksTimeout: How long do we let a socks connection wait
32135 unattached before we fail it?
32136 - CircuitBuildTimeout: Cull non-open circuits that were born
32137 at least this many seconds ago.
32138 - CircuitIdleTimeout: Cull open clean circuits that were born
32139 at least this many seconds ago.
32142 Changes in version 0.1.1.16-rc - 2006-03-18
32143 o Bugfixes on 0.1.1.15-rc:
32144 - Fix assert when the controller asks to attachstream a connect-wait
32145 or resolve-wait stream.
32146 - Now do address rewriting when the controller asks us to attach
32147 to a particular circuit too. This will let Blossom specify
32148 "moria2.exit" without having to learn what moria2's IP address is.
32149 - Make the "tor --verify-config" command-line work again, so people
32150 can automatically check if their torrc will parse.
32151 - Authoritative dirservers no longer require an open connection from
32152 a server to consider him "reachable". We need this change because
32153 when we add new auth dirservers, old servers won't know not to
32155 - Let Tor build on Sun CC again.
32156 - Fix an off-by-one buffer size in dirserv.c that magically never
32157 hit our three authorities but broke sjmurdoch's own tor network.
32158 - If we as a directory mirror don't know of any v1 directory
32159 authorities, then don't try to cache any v1 directories.
32160 - Stop warning about unknown servers in our family when they are
32161 given as hex digests.
32162 - Stop complaining as quickly to the server operator that he
32163 hasn't registered his nickname/key binding.
32164 - Various cleanups so we can add new V2 Auth Dirservers.
32165 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
32166 reflect the updated flags in our v2 dir protocol.
32167 - Resume allowing non-printable characters for exit streams (both
32168 for connecting and for resolving). Now we tolerate applications
32169 that don't follow the RFCs. But continue to block malformed names
32172 o Bugfixes on 0.1.0.x:
32173 - Fix assert bug in close_logs(): when we close and delete logs,
32174 remove them all from the global "logfiles" list.
32175 - Fix minor integer overflow in calculating when we expect to use up
32176 our bandwidth allocation before hibernating.
32177 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
32178 there are multiple SSLs installed with different versions.
32179 - When we try to be a server and Address is not explicitly set and
32180 our hostname resolves to a private IP address, try to use an
32181 interface address if it has a public address. Now Windows machines
32182 that think of themselves as localhost can work by default.
32185 - Let the controller ask for GETINFO dir/server/foo so it can ask
32186 directly rather than connecting to the dir port.
32187 - Let the controller tell us about certain router descriptors
32188 that it doesn't want Tor to use in circuits. Implement
32189 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
32190 - New config option SafeSocks to reject all application connections
32191 using unsafe socks protocols. Defaults to off.
32194 Changes in version 0.1.1.15-rc - 2006-03-11
32195 o Bugfixes and cleanups:
32196 - When we're printing strings from the network, don't try to print
32197 non-printable characters. This protects us against shell escape
32198 sequence exploits, and also against attacks to fool humans into
32199 misreading their logs.
32200 - Fix a bug where Tor would fail to establish any connections if you
32201 left it off for 24 hours and then started it: we were happy with
32202 the obsolete network statuses, but they all referred to router
32203 descriptors that were too old to fetch, so we ended up with no
32204 valid router descriptors.
32205 - Fix a seg fault in the controller's "getinfo orconn-status"
32206 command while listing status on incoming handshaking connections.
32207 Introduce a status name "NEW" for these connections.
32208 - If we get a linelist or linelist_s config option from the torrc
32209 (e.g. ExitPolicy) and it has no value, warn and skip rather than
32210 silently resetting it to its default.
32211 - Don't abandon entry guards until they've been down or gone for
32213 - Cleaner and quieter log messages.
32216 - New controller signal NEWNYM that makes new application requests
32217 use clean circuits.
32218 - Add a new circuit purpose 'controller' to let the controller ask
32219 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
32220 controller command to let you specify the purpose if you're
32221 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
32222 command to let you change a circuit's purpose after it's been
32224 - Accept "private:*" in routerdesc exit policies; not generated yet
32225 because older Tors do not understand it.
32226 - Add BSD-style contributed startup script "rc.subr" from Peter
32230 Changes in version 0.1.1.14-alpha - 2006-02-20
32231 o Bugfixes on 0.1.1.x:
32232 - Don't die if we ask for a stdout or stderr log (even implicitly)
32233 and we're set to RunAsDaemon -- just warn.
32234 - We still had a few bugs in the OR connection rotation code that
32235 caused directory servers to slowly aggregate connections to other
32236 fast Tor servers. This time for sure!
32237 - Make log entries on Win32 include the name of the function again.
32238 - We were treating a pair of exit policies if they were equal even
32239 if one said accept and the other said reject -- causing us to
32240 not always publish a new descriptor since we thought nothing
32242 - Retry pending server downloads as well as pending networkstatus
32243 downloads when we unexpectedly get a socks request.
32244 - We were ignoring the IS_FAST flag in the directory status,
32245 meaning we were willing to pick trivial-bandwidth nodes for "fast"
32247 - If the controller's SAVECONF command fails (e.g. due to file
32248 permissions), let the controller know that it failed.
32251 - If we're trying to be a Tor server and running Windows 95/98/ME
32252 as a server, explain that we'll likely crash.
32253 - When we're a server, a client asks for an old-style directory,
32254 and our write bucket is empty, don't give it to him. This way
32255 small servers can continue to serve the directory *sometimes*,
32256 without getting overloaded.
32257 - Compress exit policies even more -- look for duplicate lines
32259 - Clients now honor the "guard" flag in the router status when
32260 picking entry guards, rather than looking at is_fast or is_stable.
32261 - Retain unrecognized lines in $DATADIR/state file, so that we can
32262 be forward-compatible.
32263 - Generate 18.0.0.0/8 address policy format in descs when we can;
32264 warn when the mask is not reducible to a bit-prefix.
32265 - Let the user set ControlListenAddress in the torrc. This can be
32266 dangerous, but there are some cases (like a secured LAN) where it
32268 - Split ReachableAddresses into ReachableDirAddresses and
32269 ReachableORAddresses, so we can restrict Dir conns to port 80
32270 and OR conns to port 443.
32271 - Now we can target arch and OS in rpm builds (contributed by
32272 Phobos). Also make the resulting dist-rpm filename match the
32274 - New config options to help controllers: FetchServerDescriptors
32275 and FetchHidServDescriptors for whether to fetch server
32276 info and hidserv info or let the controller do it, and
32277 PublishServerDescriptor and PublishHidServDescriptors.
32278 - Also let the controller set the __AllDirActionsPrivate config
32279 option if you want all directory fetches/publishes to happen via
32280 Tor (it assumes your controller bootstraps your circuits).
32283 Changes in version 0.1.0.17 - 2006-02-17
32284 o Crash bugfixes on 0.1.0.x:
32285 - When servers with a non-zero DirPort came out of hibernation,
32286 sometimes they would trigger an assert.
32288 o Other important bugfixes:
32289 - On platforms that don't have getrlimit (like Windows), we were
32290 artificially constraining ourselves to a max of 1024
32291 connections. Now just assume that we can handle as many as 15000
32292 connections. Hopefully this won't cause other problems.
32294 o Backported features:
32295 - When we're a server, a client asks for an old-style directory,
32296 and our write bucket is empty, don't give it to him. This way
32297 small servers can continue to serve the directory *sometimes*,
32298 without getting overloaded.
32299 - Whenever you get a 503 in response to a directory fetch, try
32300 once more. This will become important once servers start sending
32301 503's whenever they feel busy.
32302 - Fetch a new directory every 120 minutes, not every 40 minutes.
32303 Now that we have hundreds of thousands of users running the old
32304 directory algorithm, it's starting to hurt a lot.
32305 - Bump up the period for forcing a hidden service descriptor upload
32306 from 20 minutes to 1 hour.
32309 Changes in version 0.1.1.13-alpha - 2006-02-09
32310 o Crashes in 0.1.1.x:
32311 - When you tried to setconf ORPort via the controller, Tor would
32312 crash. So people using TorCP to become a server were sad.
32313 - Solve (I hope) the stack-smashing bug that we were seeing on fast
32314 servers. The problem appears to be something do with OpenSSL's
32315 random number generation, or how we call it, or something. Let me
32316 know if the crashes continue.
32317 - Turn crypto hardware acceleration off by default, until we find
32318 somebody smart who can test it for us. (It appears to produce
32319 seg faults in at least some cases.)
32320 - Fix a rare assert error when we've tried all intro points for
32321 a hidden service and we try fetching the service descriptor again:
32322 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
32325 - Fix a major load balance bug: we were round-robining in 16 KB
32326 chunks, and servers with bandwidthrate of 20 KB, while downloading
32327 a 600 KB directory, would starve their other connections. Now we
32328 try to be a bit more fair.
32329 - Dir authorities and mirrors were never expiring the newest
32330 descriptor for each server, causing memory and directory bloat.
32331 - Fix memory-bloating and connection-bloating bug on servers: We
32332 were never closing any connection that had ever had a circuit on
32333 it, because we were checking conn->n_circuits == 0, yet we had a
32334 bug that let it go negative.
32335 - Make Tor work using squid as your http proxy again -- squid
32336 returns an error if you ask for a URL that's too long, and it uses
32337 a really generic error message. Plus, many people are behind a
32338 transparent squid so they don't even realize it.
32339 - On platforms that don't have getrlimit (like Windows), we were
32340 artificially constraining ourselves to a max of 1024
32341 connections. Now just assume that we can handle as many as 15000
32342 connections. Hopefully this won't cause other problems.
32343 - Add a new config option ExitPolicyRejectPrivate which defaults to
32344 1. This means all exit policies will begin with rejecting private
32345 addresses, unless the server operator explicitly turns it off.
32348 - Clients no longer download descriptors for non-running
32350 - Before we add new directory authorities, we should make it
32351 clear that only v1 authorities should receive/publish hidden
32352 service descriptors.
32355 - As soon as we've fetched some more directory info, immediately
32356 try to download more server descriptors. This way we don't have
32357 a 10 second pause during initial bootstrapping.
32358 - Remove even more loud log messages that the server operator can't
32360 - When we're running an obsolete or un-recommended version, make
32361 the log message more clear about what the problem is and what
32362 versions *are* still recommended.
32363 - Provide a more useful warn message when our onion queue gets full:
32364 the CPU is too slow or the exit policy is too liberal.
32365 - Don't warn when we receive a 503 from a dirserver/cache -- this
32366 will pave the way for them being able to refuse if they're busy.
32367 - When we fail to bind a listener, try to provide a more useful
32368 log message: e.g., "Is Tor already running?"
32369 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
32370 Goldberg can prove things about our handshake protocol more
32372 - MaxConn has been obsolete for a while now. Document the ConnLimit
32373 config option, which is a *minimum* number of file descriptors
32374 that must be available else Tor refuses to start.
32375 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
32376 if you log to syslog and want something other than LOG_DAEMON.
32377 - Make dirservers generate a separate "guard" flag to mean,
32378 "would make a good entry guard". Make clients parse it and vote
32379 on it. Not used by clients yet.
32380 - Implement --with-libevent-dir option to ./configure. Also, improve
32381 search techniques to find libevent, and use those for openssl too.
32382 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
32383 - Only start testing reachability once we've established a
32384 circuit. This will make startup on dirservers less noisy.
32385 - Don't try to upload hidden service descriptors until we have
32386 established a circuit.
32387 - Fix the controller's "attachstream 0" command to treat conn like
32388 it just connected, doing address remapping, handling .exit and
32389 .onion idioms, and so on. Now we're more uniform in making sure
32390 that the controller hears about new and closing connections.
32393 Changes in version 0.1.1.12-alpha - 2006-01-11
32394 o Bugfixes on 0.1.1.x:
32395 - The fix to close duplicate server connections was closing all
32396 Tor client connections if they didn't establish a circuit
32397 quickly enough. Oops.
32398 - Fix minor memory issue (double-free) that happened on exit.
32400 o Bugfixes on 0.1.0.x:
32401 - Tor didn't warn when it failed to open a log file.
32404 Changes in version 0.1.1.11-alpha - 2006-01-10
32405 o Crashes in 0.1.1.x:
32406 - Include all the assert/crash fixes from 0.1.0.16.
32407 - If you start Tor and then quit very quickly, there were some
32408 races that tried to free things that weren't allocated yet.
32409 - Fix a rare memory stomp if you're running hidden services.
32410 - Fix segfault when specifying DirServer in config without nickname.
32411 - Fix a seg fault when you finish connecting to a server but at
32412 that moment you dump his server descriptor.
32413 - Extendcircuit and Attachstream controller commands would
32414 assert/crash if you don't give them enough arguments.
32415 - Fix an assert error when we're out of space in the connection_list
32416 and we try to post a hidden service descriptor (reported by weasel).
32417 - If you specify a relative torrc path and you set RunAsDaemon in
32418 your torrc, then it chdir()'s to the new directory. If you HUP,
32419 it tries to load the new torrc location, fails, and exits.
32420 The fix: no longer allow a relative path to torrc using -f.
32423 - Implement "entry guards": automatically choose a handful of entry
32424 nodes and stick with them for all circuits. Only pick new guards
32425 when the ones you have are unsuitable, and if the old guards
32426 become suitable again, switch back. This will increase security
32427 dramatically against certain end-point attacks. The EntryNodes
32428 config option now provides some hints about which entry guards you
32429 want to use most; and StrictEntryNodes means to only use those.
32430 - New directory logic: download by descriptor digest, not by
32431 fingerprint. Caches try to download all listed digests from
32432 authorities; clients try to download "best" digests from caches.
32433 This avoids partitioning and isolating attacks better.
32434 - Make the "stable" router flag in network-status be the median of
32435 the uptimes of running valid servers, and make clients pay
32436 attention to the network-status flags. Thus the cutoff adapts
32437 to the stability of the network as a whole, making IRC, IM, etc
32438 connections more reliable.
32441 - Tor servers with dynamic IP addresses were needing to wait 18
32442 hours before they could start doing reachability testing using
32443 the new IP address and ports. This is because they were using
32444 the internal descriptor to learn what to test, yet they were only
32445 rebuilding the descriptor once they decided they were reachable.
32446 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
32447 to download certain server descriptors, throw them away, and then
32448 fetch them again after 30 minutes. Now mirrors throw away these
32449 server descriptors so clients can't get them.
32450 - We were leaving duplicate connections to other ORs open for a week,
32451 rather than closing them once we detect a duplicate. This only
32452 really affected authdirservers, but it affected them a lot.
32453 - Spread the authdirservers' reachability testing over the entire
32454 testing interval, so we don't try to do 500 TLS's at once every
32458 - If the network is down, and we try to connect to a conn because
32459 we have a circuit in mind, and we timeout (30 seconds) because the
32460 network never answers, we were expiring the circuit, but we weren't
32461 obsoleting the connection or telling the entry_guards functions.
32462 - Some Tor servers process billions of cells per day. These statistics
32463 need to be uint64_t's.
32464 - Check for integer overflows in more places, when adding elements
32465 to smartlists. This could possibly prevent a buffer overflow
32466 on malicious huge inputs. I don't see any, but I haven't looked
32468 - ReachableAddresses kept growing new "reject *:*" lines on every
32470 - When you "setconf log" via the controller, it should remove all
32471 logs. We were automatically adding back in a "log notice stdout".
32472 - Newly bootstrapped Tor networks couldn't establish hidden service
32473 circuits until they had nodes with high uptime. Be more tolerant.
32474 - We were marking servers down when they could not answer every piece
32475 of the directory request we sent them. This was far too harsh.
32476 - Fix the torify (tsocks) config file to not use Tor for localhost
32478 - Directory authorities now go to the proper authority when asking for
32479 a networkstatus, even when they want a compressed one.
32480 - Fix a harmless bug that was causing Tor servers to log
32481 "Got an end because of misc error, but we're not an AP. Closing."
32482 - Authorities were treating their own descriptor changes as cosmetic,
32483 meaning the descriptor available in the network-status and the
32484 descriptor that clients downloaded were different.
32485 - The OS X installer was adding a symlink for tor_resolve but
32486 the binary was called tor-resolve (reported by Thomas Hardly).
32487 - Workaround a problem with some http proxies where they refuse GET
32488 requests that specify "Content-Length: 0" (reported by Adrian).
32489 - Fix wrong log message when you add a "HiddenServiceNodes" config
32490 line without any HiddenServiceDir line (reported by Chris Thomas).
32493 - Write the TorVersion into the state file so we have a prayer of
32494 keeping forward and backward compatibility.
32495 - Revive the FascistFirewall config option rather than eliminating it:
32496 now it's a synonym for ReachableAddresses *:80,*:443.
32497 - Clients choose directory servers from the network status lists,
32498 not from their internal list of router descriptors. Now they can
32499 go to caches directly rather than needing to go to authorities
32501 - Directory authorities ignore router descriptors that have only
32502 cosmetic differences: do this for 0.1.0.x servers now too.
32503 - Add a new flag to network-status indicating whether the server
32504 can answer v2 directory requests too.
32505 - Authdirs now stop whining so loudly about bad descriptors that
32506 they fetch from other dirservers. So when there's a log complaint,
32507 it's for sure from a freshly uploaded descriptor.
32508 - Reduce memory requirements in our structs by changing the order
32510 - There used to be two ways to specify your listening ports in a
32511 server descriptor: on the "router" line and with a separate "ports"
32512 line. Remove support for the "ports" line.
32513 - New config option "AuthDirRejectUnlisted" for auth dirservers as
32514 a panic button: if we get flooded with unusable servers we can
32515 revert to only listing servers in the approved-routers file.
32516 - Auth dir servers can now mark a fingerprint as "!reject" or
32517 "!invalid" in the approved-routers file (as its nickname), to
32518 refuse descriptors outright or include them but marked as invalid.
32519 - Servers store bandwidth history across restarts/crashes.
32520 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
32521 get a better idea of why their circuits failed. Not used yet.
32522 - Directory mirrors now cache up to 16 unrecognized network-status
32523 docs. Now we can add new authdirservers and they'll be cached too.
32524 - When picking a random directory, prefer non-authorities if any
32526 - New controller option "getinfo desc/all-recent" to fetch the
32527 latest server descriptor for every router that Tor knows about.
32530 Changes in version 0.1.0.16 - 2006-01-02
32531 o Crash bugfixes on 0.1.0.x:
32532 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
32533 corrupting the heap, losing FDs, or crashing when we need to resize
32534 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
32535 - It turns out sparc64 platforms crash on unaligned memory access
32536 too -- so detect and avoid this.
32537 - Handle truncated compressed data correctly (by detecting it and
32539 - Fix possible-but-unlikely free(NULL) in control.c.
32540 - When we were closing connections, there was a rare case that
32541 stomped on memory, triggering seg faults and asserts.
32542 - Avoid potential infinite recursion when building a descriptor. (We
32543 don't know that it ever happened, but better to fix it anyway.)
32544 - We were neglecting to unlink marked circuits from soon-to-close OR
32545 connections, which caused some rare scribbling on freed memory.
32546 - Fix a memory stomping race bug when closing the joining point of two
32547 rendezvous circuits.
32548 - Fix an assert in time parsing found by Steven Murdoch.
32550 o Other bugfixes on 0.1.0.x:
32551 - When we're doing reachability testing, provide more useful log
32552 messages so the operator knows what to expect.
32553 - Do not check whether DirPort is reachable when we are suppressing
32554 advertising it because of hibernation.
32555 - When building with -static or on Solaris, we sometimes needed -ldl.
32556 - When we're deciding whether a stream has enough circuits around
32557 that can handle it, count the freshly dirty ones and not the ones
32558 that are so dirty they won't be able to handle it.
32559 - When we're expiring old circuits, we had a logic error that caused
32560 us to close new rendezvous circuits rather than old ones.
32561 - Give a more helpful log message when you try to change ORPort via
32562 the controller: you should upgrade Tor if you want that to work.
32563 - We were failing to parse Tor versions that start with "Tor ".
32564 - Tolerate faulty streams better: when a stream fails for reason
32565 exitpolicy, stop assuming that the router is lying about his exit
32566 policy. When a stream fails for reason misc, allow it to retry just
32567 as if it was resolvefailed. When a stream has failed three times,
32568 reset its failure count so we can try again and get all three tries.
32571 Changes in version 0.1.1.10-alpha - 2005-12-11
32572 o Correctness bugfixes on 0.1.0.x:
32573 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
32574 corrupting the heap, losing FDs, or crashing when we need to resize
32575 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
32576 - Stop doing the complex voodoo overkill checking for insecure
32577 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
32578 - When we were closing connections, there was a rare case that
32579 stomped on memory, triggering seg faults and asserts.
32580 - We were neglecting to unlink marked circuits from soon-to-close OR
32581 connections, which caused some rare scribbling on freed memory.
32582 - When we're deciding whether a stream has enough circuits around
32583 that can handle it, count the freshly dirty ones and not the ones
32584 that are so dirty they won't be able to handle it.
32585 - Recover better from TCP connections to Tor servers that are
32586 broken but don't tell you (it happens!); and rotate TLS
32587 connections once a week.
32588 - When we're expiring old circuits, we had a logic error that caused
32589 us to close new rendezvous circuits rather than old ones.
32590 - Fix a scary-looking but apparently harmless bug where circuits
32591 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
32592 servers, and never switch to state CIRCUIT_STATE_OPEN.
32593 - When building with -static or on Solaris, we sometimes needed to
32595 - Give a useful message when people run Tor as the wrong user,
32596 rather than telling them to start chowning random directories.
32597 - We were failing to inform the controller about new .onion streams.
32599 o Security bugfixes on 0.1.0.x:
32600 - Refuse server descriptors if the fingerprint line doesn't match
32601 the included identity key. Tor doesn't care, but other apps (and
32602 humans) might actually be trusting the fingerprint line.
32603 - We used to kill the circuit when we receive a relay command we
32604 don't recognize. Now we just drop it.
32605 - Start obeying our firewall options more rigorously:
32606 . If we can't get to a dirserver directly, try going via Tor.
32607 . Don't ever try to connect (as a client) to a place our
32608 firewall options forbid.
32609 . If we specify a proxy and also firewall options, obey the
32610 firewall options even when we're using the proxy: some proxies
32611 can only proxy to certain destinations.
32612 - Fix a bug found by Lasse Overlier: when we were making internal
32613 circuits (intended to be cannibalized later for rendezvous and
32614 introduction circuits), we were picking them so that they had
32615 useful exit nodes. There was no need for this, and it actually
32616 aids some statistical attacks.
32617 - Start treating internal circuits and exit circuits separately.
32618 It's important to keep them separate because internal circuits
32619 have their last hops picked like middle hops, rather than like
32620 exit hops. So exiting on them will break the user's expectations.
32622 o Bugfixes on 0.1.1.x:
32623 - Take out the mis-feature where we tried to detect IP address
32624 flapping for people with DynDNS, and chose not to upload a new
32625 server descriptor sometimes.
32626 - Try to be compatible with OpenSSL 0.9.6 again.
32627 - Log fix: when the controller is logging about .onion addresses,
32628 sometimes it didn't include the ".onion" part of the address.
32629 - Don't try to modify options->DirServers internally -- if the
32630 user didn't specify any, just add the default ones directly to
32631 the trusted dirserver list. This fixes a bug where people running
32632 controllers would use SETCONF on some totally unrelated config
32633 option, and Tor would start yelling at them about changing their
32635 - Let the controller's redirectstream command specify a port, in
32636 case the controller wants to change that too.
32637 - When we requested a pile of server descriptors, we sometimes
32638 accidentally launched a duplicate request for the first one.
32639 - Bugfix for trackhostexits: write down the fingerprint of the
32640 chosen exit, not its nickname, because the chosen exit might not
32642 - When parsing foo.exit, if foo is unknown, and we are leaving
32643 circuits unattached, set the chosen_exit field and leave the
32644 address empty. This matters because controllers got confused
32646 - Directory authorities no longer try to download server
32647 descriptors that they know they will reject.
32649 o Features and updates:
32650 - Replace balanced trees with hash tables: this should make stuff
32651 significantly faster.
32652 - Resume using the AES counter-mode implementation that we ship,
32653 rather than OpenSSL's. Ours is significantly faster.
32654 - Many other CPU and memory improvements.
32655 - Add a new config option FastFirstHopPK (on by default) so clients
32656 do a trivial crypto handshake for their first hop, since TLS has
32657 already taken care of confidentiality and authentication.
32658 - Add a new config option TestSocks so people can see if their
32659 applications are using socks4, socks4a, socks5-with-ip, or
32660 socks5-with-hostname. This way they don't have to keep mucking
32661 with tcpdump and wondering if something got cached somewhere.
32662 - Warn when listening on a public address for socks. I suspect a
32663 lot of people are setting themselves up as open socks proxies,
32664 and they have no idea that jerks on the Internet are using them,
32665 since they simply proxy the traffic into the Tor network.
32666 - Add "private:*" as an alias in configuration for policies. Now
32667 you can simplify your exit policy rather than needing to list
32668 every single internal or nonroutable network space.
32669 - Add a new controller event type that allows controllers to get
32670 all server descriptors that were uploaded to a router in its role
32671 as authoritative dirserver.
32672 - Start shipping socks-extensions.txt, tor-doc-unix.html,
32673 tor-doc-server.html, and stylesheet.css in the tarball.
32674 - Stop shipping tor-doc.html in the tarball.
32677 Changes in version 0.1.1.9-alpha - 2005-11-15
32678 o Usability improvements:
32679 - Start calling it FooListenAddress rather than FooBindAddress,
32680 since few of our users know what it means to bind an address
32682 - Reduce clutter in server logs. We're going to try to make
32683 them actually usable now. New config option ProtocolWarnings that
32684 lets you hear about how _other Tors_ are breaking the protocol. Off
32686 - Divide log messages into logging domains. Once we put some sort
32687 of interface on this, it will let people looking at more verbose
32688 log levels specify the topics they want to hear more about.
32689 - Make directory servers return better http 404 error messages
32690 instead of a generic "Servers unavailable".
32691 - Check for even more Windows version flags when writing the platform
32692 string in server descriptors, and note any we don't recognize.
32693 - Clean up more of the OpenSSL memory when exiting, so we can detect
32694 memory leaks better.
32695 - Make directory authorities be non-versioning, non-naming by
32696 default. Now we can add new directory servers without requiring
32697 their operators to pay close attention.
32698 - When logging via syslog, include the pid whenever we provide
32699 a log entry. Suggested by Todd Fries.
32701 o Performance improvements:
32702 - Directory servers now silently throw away new descriptors that
32703 haven't changed much if the timestamps are similar. We do this to
32704 tolerate older Tor servers that upload a new descriptor every 15
32705 minutes. (It seemed like a good idea at the time.)
32706 - Inline bottleneck smartlist functions; use fast versions by default.
32707 - Add a "Map from digest to void*" abstraction digestmap_t so we
32708 can do less hex encoding/decoding. Use it in router_get_by_digest()
32709 to resolve a performance bottleneck.
32710 - Allow tor_gzip_uncompress to extract as much as possible from
32711 truncated compressed data. Try to extract as many
32712 descriptors as possible from truncated http responses (when
32713 DIR_PURPOSE_FETCH_ROUTERDESC).
32714 - Make circ->onionskin a pointer, not a static array. moria2 was using
32715 125000 circuit_t's after it had been up for a few weeks, which
32716 translates to 20+ megs of wasted space.
32717 - The private half of our EDH handshake keys are now chosen out
32718 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
32720 o Security improvements:
32721 - Start making directory caches retain old routerinfos, so soon
32722 clients can start asking by digest of descriptor rather than by
32723 fingerprint of server.
32724 - Add half our entropy from RAND_poll in OpenSSL. This knows how
32725 to use egd (if present), openbsd weirdness (if present), vms/os2
32726 weirdness (if we ever port there), and more in the future.
32728 o Bugfixes on 0.1.0.x:
32729 - Do round-robin writes of at most 16 kB per write. This might be
32730 more fair on loaded Tor servers, and it might resolve our Windows
32731 crash bug. It might also slow things down.
32732 - Our TLS handshakes were generating a single public/private
32733 keypair for the TLS context, rather than making a new one for
32734 each new connections. Oops. (But we were still rotating them
32735 periodically, so it's not so bad.)
32736 - When we were cannibalizing a circuit with a particular exit
32737 node in mind, we weren't checking to see if that exit node was
32738 already present earlier in the circuit. Oops.
32739 - When a Tor server's IP changes (e.g. from a dyndns address),
32740 upload a new descriptor so clients will learn too.
32741 - Really busy servers were keeping enough circuits open on stable
32742 connections that they were wrapping around the circuit_id
32743 space. (It's only two bytes.) This exposed a bug where we would
32744 feel free to reuse a circuit_id even if it still exists but has
32745 been marked for close. Try to fix this bug. Some bug remains.
32746 - If we would close a stream early (e.g. it asks for a .exit that
32747 we know would refuse it) but the LeaveStreamsUnattached config
32748 option is set by the controller, then don't close it.
32750 o Bugfixes on 0.1.1.8-alpha:
32751 - Fix a big pile of memory leaks, some of them serious.
32752 - Do not try to download a routerdesc if we would immediately reject
32754 - Resume inserting a newline between all router descriptors when
32755 generating (old style) signed directories, since our spec says
32757 - When providing content-type application/octet-stream for
32758 server descriptors using .z, we were leaving out the
32759 content-encoding header. Oops. (Everything tolerated this just
32760 fine, but that doesn't mean we need to be part of the problem.)
32761 - Fix a potential seg fault in getconf and getinfo using version 1
32762 of the controller protocol.
32763 - Avoid crash: do not check whether DirPort is reachable when we
32764 are suppressing it because of hibernation.
32765 - Make --hash-password not crash on exit.
32768 Changes in version 0.1.1.8-alpha - 2005-10-07
32769 o New features (major):
32770 - Clients don't download or use the directory anymore. Now they
32771 download and use network-statuses from the trusted dirservers,
32772 and fetch individual server descriptors as needed from mirrors.
32773 See dir-spec.txt for all the gory details.
32774 - Be more conservative about whether to advertise our DirPort.
32775 The main change is to not advertise if we're running at capacity
32776 and either a) we could hibernate or b) our capacity is low and
32777 we're using a default DirPort.
32778 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
32780 o New features (minor):
32781 - Try to be smart about when to retry network-status and
32782 server-descriptor fetches. Still needs some tuning.
32783 - Stop parsing, storing, or using running-routers output (but
32784 mirrors still cache and serve it).
32785 - Consider a threshold of versioning dirservers (dirservers who have
32786 an opinion about which Tor versions are still recommended) before
32787 deciding whether to warn the user that he's obsolete.
32788 - Dirservers can now reject/invalidate by key and IP, with the
32789 config options "AuthDirInvalid" and "AuthDirReject". This is
32790 useful since currently we automatically list servers as running
32791 and usable even if we know they're jerks.
32792 - Provide dire warnings to any users who set DirServer; move it out
32793 of torrc.sample and into torrc.complete.
32794 - Add MyFamily to torrc.sample in the server section.
32795 - Add nicknames to the DirServer line, so we can refer to them
32796 without requiring all our users to memorize their IP addresses.
32797 - When we get an EOF or a timeout on a directory connection, note
32798 how many bytes of serverdesc we are dropping. This will help
32799 us determine whether it is smart to parse incomplete serverdesc
32801 - Add a new function to "change pseudonyms" -- that is, to stop
32802 using any currently-dirty circuits for new streams, so we don't
32803 link new actions to old actions. Currently it's only called on
32804 HUP (or SIGNAL RELOAD).
32805 - On sighup, if UseHelperNodes changed to 1, use new circuits.
32806 - Start using RAND_bytes rather than RAND_pseudo_bytes from
32807 OpenSSL. Also, reseed our entropy every hour, not just at
32808 startup. And entropy in 512-bit chunks, not 160-bit chunks.
32810 o Fixes on 0.1.1.7-alpha:
32811 - Nobody ever implemented EVENT_ADDRMAP for control protocol
32812 version 0, so don't let version 0 controllers ask for it.
32813 - If you requested something with too many newlines via the
32814 v1 controller protocol, you could crash tor.
32815 - Fix a number of memory leaks, including some pretty serious ones.
32816 - Re-enable DirPort testing again, so Tor servers will be willing
32817 to advertise their DirPort if it's reachable.
32818 - On TLS handshake, only check the other router's nickname against
32819 its expected nickname if is_named is set.
32821 o Fixes forward-ported from 0.1.0.15:
32822 - Don't crash when we don't have any spare file descriptors and we
32823 try to spawn a dns or cpu worker.
32824 - Make the numbers in read-history and write-history into uint64s,
32825 so they don't overflow and publish negatives in the descriptor.
32827 o Fixes on 0.1.0.x:
32828 - For the OS X package's modified privoxy config file, comment
32829 out the "logfile" line so we don't log everything passed
32831 - We were whining about using socks4 or socks5-with-local-lookup
32832 even when it's an IP in the "virtual" range we designed exactly
32834 - We were leaking some memory every time the client changes IPs.
32835 - Never call free() on tor_malloc()d memory. This will help us
32836 use dmalloc to detect memory leaks.
32837 - Check for named servers when looking them up by nickname;
32838 warn when we'recalling a non-named server by its nickname;
32839 don't warn twice about the same name.
32840 - Try to list MyFamily elements by key, not by nickname, and warn
32841 if we've not heard of the server.
32842 - Make windows platform detection (uname equivalent) smarter.
32843 - It turns out sparc64 doesn't like unaligned access either.
32846 Changes in version 0.1.0.15 - 2005-09-23
32847 o Bugfixes on 0.1.0.x:
32848 - Reject ports 465 and 587 (spam targets) in default exit policy.
32849 - Don't crash when we don't have any spare file descriptors and we
32850 try to spawn a dns or cpu worker.
32851 - Get rid of IgnoreVersion undocumented config option, and make us
32852 only warn, never exit, when we're running an obsolete version.
32853 - Don't try to print a null string when your server finds itself to
32854 be unreachable and the Address config option is empty.
32855 - Make the numbers in read-history and write-history into uint64s,
32856 so they don't overflow and publish negatives in the descriptor.
32857 - Fix a minor memory leak in smartlist_string_remove().
32858 - We were only allowing ourselves to upload a server descriptor at
32859 most every 20 minutes, even if it changed earlier than that.
32860 - Clean up log entries that pointed to old URLs.
32863 Changes in version 0.1.1.7-alpha - 2005-09-14
32864 o Fixes on 0.1.1.6-alpha:
32865 - Exit servers were crashing when people asked them to make a
32866 connection to an address not in their exit policy.
32867 - Looking up a non-existent stream for a v1 control connection would
32869 - Fix a seg fault if we ask a dirserver for a descriptor by
32870 fingerprint but he doesn't know about him.
32871 - SETCONF was appending items to linelists, not clearing them.
32872 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
32873 out and refuse the setconf if it would fail.
32874 - Downgrade the dirserver log messages when whining about
32878 - Add Peter Palfrader's check-tor script to tor/contrib/
32879 It lets you easily check whether a given server (referenced by
32880 nickname) is reachable by you.
32881 - Numerous changes to move towards client-side v2 directories. Not
32884 o Fixes on 0.1.0.x:
32885 - If the user gave tor an odd number of command-line arguments,
32886 we were silently ignoring the last one. Now we complain and fail.
32887 [This wins the oldest-bug prize -- this bug has been present since
32888 November 2002, as released in Tor 0.0.0.]
32889 - Do not use unaligned memory access on alpha, mips, or mipsel.
32890 It *works*, but is very slow, so we treat them as if it doesn't.
32891 - Retry directory requests if we fail to get an answer we like
32892 from a given dirserver (we were retrying before, but only if
32893 we fail to connect).
32894 - When writing the RecommendedVersions line, sort them first.
32895 - When the client asked for a rendezvous port that the hidden
32896 service didn't want to provide, we were sending an IP address
32897 back along with the end cell. Fortunately, it was zero. But stop
32899 - Correct "your server is reachable" log entries to indicate that
32900 it was self-testing that told us so.
32903 Changes in version 0.1.1.6-alpha - 2005-09-09
32904 o Fixes on 0.1.1.5-alpha:
32905 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
32906 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
32907 - Fix bug with tor_memmem finding a match at the end of the string.
32908 - Make unit tests run without segfaulting.
32909 - Resolve some solaris x86 compile warnings.
32910 - Handle duplicate lines in approved-routers files without warning.
32911 - Fix bug where as soon as a server refused any requests due to his
32912 exit policy (e.g. when we ask for localhost and he tells us that's
32913 127.0.0.1 and he won't do it), we decided he wasn't obeying his
32914 exit policy using him for any exits.
32915 - Only do openssl hardware accelerator stuff if openssl version is
32918 o New controller features/fixes:
32919 - Add a "RESETCONF" command so you can set config options like
32920 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
32921 a config option in the torrc with no value, then it clears it
32922 entirely (rather than setting it to its default).
32923 - Add a "GETINFO config-file" to tell us where torrc is.
32924 - Avoid sending blank lines when GETINFO replies should be empty.
32925 - Add a QUIT command for the controller (for using it manually).
32926 - Fix a bug in SAVECONF that was adding default dirservers and
32927 other redundant entries to the torrc file.
32929 o Start on the new directory design:
32930 - Generate, publish, cache, serve new network-status format.
32931 - Publish individual descriptors (by fingerprint, by "all", and by
32933 - Publish client and server recommended versions separately.
32934 - Allow tor_gzip_uncompress() to handle multiple concatenated
32935 compressed strings. Serve compressed groups of router
32936 descriptors. The compression logic here could be more
32938 - Distinguish v1 authorities (all currently trusted directories)
32939 from v2 authorities (all trusted directories).
32940 - Change DirServers config line to note which dirs are v1 authorities.
32941 - Add configuration option "V1AuthoritativeDirectory 1" which
32942 moria1, moria2, and tor26 should set.
32943 - Remove option when getting directory cache to see whether they
32944 support running-routers; they all do now. Replace it with one
32945 to see whether caches support v2 stuff.
32948 - Dirservers now do their own external reachability testing of each
32949 Tor server, and only list them as running if they've been found to
32950 be reachable. We also send back warnings to the server's logs if
32951 it uploads a descriptor that we already believe is unreachable.
32952 - Implement exit enclaves: if we know an IP address for the
32953 destination, and there's a running Tor server at that address
32954 which allows exit to the destination, then extend the circuit to
32955 that exit first. This provides end-to-end encryption and end-to-end
32956 authentication. Also, if the user wants a .exit address or enclave,
32957 use 4 hops rather than 3, and cannibalize a general circ for it
32959 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
32960 controller. Also, rotate dns and cpu workers if the controller
32961 changes options that will affect them; and initialize the dns
32962 worker cache tree whether or not we start out as a server.
32963 - Only upload a new server descriptor when options change, 18
32964 hours have passed, uptime is reset, or bandwidth changes a lot.
32965 - Check [X-]Forwarded-For headers in HTTP requests when generating
32966 log messages. This lets people run dirservers (and caches) behind
32967 Apache but still know which IP addresses are causing warnings.
32969 o Config option changes:
32970 - Replace (Fascist)Firewall* config options with a new
32971 ReachableAddresses option that understands address policies.
32972 For example, "ReachableAddresses *:80,*:443"
32973 - Get rid of IgnoreVersion undocumented config option, and make us
32974 only warn, never exit, when we're running an obsolete version.
32975 - Make MonthlyAccountingStart config option truly obsolete now.
32977 o Fixes on 0.1.0.x:
32978 - Reject ports 465 and 587 in the default exit policy, since
32979 people have started using them for spam too.
32980 - It turns out we couldn't bootstrap a network since we added
32981 reachability detection in 0.1.0.1-rc. Good thing the Tor network
32982 has never gone down. Add an AssumeReachable config option to let
32983 servers and dirservers bootstrap. When we're trying to build a
32984 high-uptime or high-bandwidth circuit but there aren't enough
32985 suitable servers, try being less picky rather than simply failing.
32986 - Our logic to decide if the OR we connected to was the right guy
32987 was brittle and maybe open to a mitm for unverified routers.
32988 - We weren't cannibalizing circuits correctly for
32989 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
32990 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
32991 build those from scratch. This should make hidden services faster.
32992 - Predict required circuits better, with an eye toward making hidden
32993 services faster on the service end.
32994 - Retry streams if the exit node sends back a 'misc' failure. This
32995 should result in fewer random failures. Also, after failing
32996 from resolve failed or misc, reset the num failures, so we give
32997 it a fair shake next time we try.
32998 - Clean up the rendezvous warn log msgs, and downgrade some to info.
32999 - Reduce severity on logs about dns worker spawning and culling.
33000 - When we're shutting down and we do something like try to post a
33001 server descriptor or rendezvous descriptor, don't complain that
33002 we seem to be unreachable. Of course we are, we're shutting down.
33003 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
33004 We don't use them yet, but maybe one day our DNS resolver will be
33005 able to discover them.
33006 - Make ContactInfo mandatory for authoritative directory servers.
33007 - Require server descriptors to list IPv4 addresses -- hostnames
33008 are no longer allowed. This also fixes some potential security
33009 problems with people providing hostnames as their address and then
33010 preferentially resolving them to partition users.
33011 - Change log line for unreachability to explicitly suggest /etc/hosts
33012 as the culprit. Also make it clearer what IP address and ports we're
33013 testing for reachability.
33014 - Put quotes around user-supplied strings when logging so users are
33015 more likely to realize if they add bad characters (like quotes)
33017 - Let auth dir servers start without specifying an Address config
33019 - Make unit tests (and other invocations that aren't the real Tor)
33020 run without launching listeners, creating subdirectories, and so on.
33023 Changes in version 0.1.1.5-alpha - 2005-08-08
33024 o Bugfixes included in 0.1.0.14.
33026 o Bugfixes on 0.1.0.x:
33027 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
33028 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
33029 it would silently using ignore the 6668.
33032 Changes in version 0.1.0.14 - 2005-08-08
33033 o Bugfixes on 0.1.0.x:
33034 - Fix the other half of the bug with crypto handshakes
33036 - Fix an assert trigger if you send a 'signal term' via the
33037 controller when it's listening for 'event info' messages.
33040 Changes in version 0.1.1.4-alpha - 2005-08-04
33041 o Bugfixes included in 0.1.0.13.
33044 - Improve tor_gettimeofday() granularity on windows.
33045 - Make clients regenerate their keys when their IP address changes.
33046 - Implement some more GETINFO goodness: expose helper nodes, config
33047 options, getinfo keys.
33050 Changes in version 0.1.0.13 - 2005-08-04
33051 o Bugfixes on 0.1.0.x:
33052 - Fix a critical bug in the security of our crypto handshakes.
33053 - Fix a size_t underflow in smartlist_join_strings2() that made
33054 it do bad things when you hand it an empty smartlist.
33055 - Fix Windows installer to ship Tor license (thanks to Aphex for
33056 pointing out this oversight) and put a link to the doc directory
33058 - Explicitly set no-unaligned-access for sparc: it turns out the
33059 new gcc's let you compile broken code, but that doesn't make it
33063 Changes in version 0.1.1.3-alpha - 2005-07-23
33064 o Bugfixes on 0.1.1.2-alpha:
33065 - Fix a bug in handling the controller's "post descriptor"
33067 - Fix several bugs in handling the controller's "extend circuit"
33069 - Fix a bug in handling the controller's "stream status" event.
33070 - Fix an assert failure if we have a controller listening for
33071 circuit events and we go offline.
33072 - Re-allow hidden service descriptors to publish 0 intro points.
33073 - Fix a crash when generating your hidden service descriptor if
33074 you don't have enough intro points already.
33076 o New features on 0.1.1.2-alpha:
33077 - New controller function "getinfo accounting", to ask how
33078 many bytes we've used in this time period.
33079 - Experimental support for helper nodes: a lot of the risk from
33080 a small static adversary comes because users pick new random
33081 nodes every time they rebuild a circuit. Now users will try to
33082 stick to the same small set of entry nodes if they can. Not
33083 enabled by default yet.
33085 o Bugfixes on 0.1.0.12:
33086 - If you're an auth dir server, always publish your dirport,
33087 even if you haven't yet found yourself to be reachable.
33088 - Fix a size_t underflow in smartlist_join_strings2() that made
33089 it do bad things when you hand it an empty smartlist.
33092 Changes in version 0.1.0.12 - 2005-07-18
33093 o New directory servers:
33094 - tor26 has changed IP address.
33096 o Bugfixes on 0.1.0.x:
33097 - Fix a possible double-free in tor_gzip_uncompress().
33098 - When --disable-threads is set, do not search for or link against
33099 pthreads libraries.
33100 - Don't trigger an assert if an authoritative directory server
33101 claims its dirport is 0.
33102 - Fix bug with removing Tor as an NT service: some people were
33103 getting "The service did not return an error." Thanks to Matt
33107 Changes in version 0.1.1.2-alpha - 2005-07-15
33108 o New directory servers:
33109 - tor26 has changed IP address.
33111 o Bugfixes on 0.1.0.x, crashes/leaks:
33112 - Port the servers-not-obeying-their-exit-policies fix from
33114 - Fix an fd leak in start_daemon().
33115 - On Windows, you can't always reopen a port right after you've
33116 closed it. So change retry_listeners() to only close and re-open
33117 ports that have changed.
33118 - Fix a possible double-free in tor_gzip_uncompress().
33120 o Bugfixes on 0.1.0.x, usability:
33121 - When tor_socketpair() fails in Windows, give a reasonable
33122 Windows-style errno back.
33123 - Let people type "tor --install" as well as "tor -install" when
33125 want to make it an NT service.
33126 - NT service patch from Matt Edman to improve error messages.
33127 - When the controller asks for a config option with an abbreviated
33128 name, give the full name in our response.
33129 - Correct the man page entry on TrackHostExitsExpire.
33130 - Looks like we were never delivering deflated (i.e. compressed)
33131 running-routers lists, even when asked. Oops.
33132 - When --disable-threads is set, do not search for or link against
33133 pthreads libraries.
33135 o Bugfixes on 0.1.1.x:
33136 - Fix a seg fault with autodetecting which controller version is
33140 - New hidden service descriptor format: put a version in it, and
33141 let people specify introduction/rendezvous points that aren't
33142 in "the directory" (which is subjective anyway).
33143 - Allow the DEBUG controller event to work again. Mark certain log
33144 entries as "don't tell this to controllers", so we avoid cycles.
33147 Changes in version 0.1.0.11 - 2005-06-30
33148 o Bugfixes on 0.1.0.x:
33149 - Fix major security bug: servers were disregarding their
33150 exit policies if clients behaved unexpectedly.
33151 - Make OS X init script check for missing argument, so we don't
33152 confuse users who invoke it incorrectly.
33153 - Fix a seg fault in "tor --hash-password foo".
33154 - The MAPADDRESS control command was broken.
33157 Changes in version 0.1.1.1-alpha - 2005-06-29
33159 - Make OS X init script check for missing argument, so we don't
33160 confuse users who invoke it incorrectly.
33161 - Fix a seg fault in "tor --hash-password foo".
33162 - Fix a possible way to DoS dirservers.
33163 - When we complain that your exit policy implicitly allows local or
33164 private address spaces, name them explicitly so operators can
33166 - Make the log message less scary when all the dirservers are
33167 temporarily unreachable.
33168 - We were printing the number of idle dns workers incorrectly when
33172 - Revised controller protocol (version 1) that uses ascii rather
33173 than binary. Add supporting libraries in python and java so you
33174 can use the controller from your applications without caring how
33175 our protocol works.
33176 - Spiffy new support for crypto hardware accelerators. Can somebody
33180 Changes in version 0.0.9.10 - 2005-06-16
33181 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
33182 - Refuse relay cells that claim to have a length larger than the
33183 maximum allowed. This prevents a potential attack that could read
33184 arbitrary memory (e.g. keys) from an exit server's process
33188 Changes in version 0.1.0.10 - 2005-06-14
33189 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
33190 libevent before 1.1a.
33193 Changes in version 0.1.0.9-rc - 2005-06-09
33195 - Reset buf->highwater every time buf_shrink() is called, not just on
33196 a successful shrink. This was causing significant memory bloat.
33197 - Fix buffer overflow when checking hashed passwords.
33198 - Security fix: if seeding the RNG on Win32 fails, quit.
33199 - Allow seeding the RNG on Win32 even when you're not running as
33201 - Disable threading on Solaris too. Something is wonky with it,
33202 cpuworkers, and reentrant libs.
33203 - Reenable the part of the code that tries to flush as soon as an
33204 OR outbuf has a full TLS record available. Perhaps this will make
33205 OR outbufs not grow as huge except in rare cases, thus saving lots
33206 of CPU time plus memory.
33207 - Reject malformed .onion addresses rather then passing them on as
33208 normal web requests.
33209 - Adapt patch from Adam Langley: fix possible memory leak in
33210 tor_lookup_hostname().
33211 - Initialize libevent later in the startup process, so the logs are
33212 already established by the time we start logging libevent warns.
33213 - Use correct errno on win32 if libevent fails.
33214 - Check and warn about known-bad/slow libevent versions.
33215 - Pay more attention to the ClientOnly config option.
33216 - Have torctl.in/tor.sh.in check for location of su binary (needed
33218 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
33219 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
33220 HttpProxyAuthenticator
33221 - Stop warning about sigpipes in the logs. We're going to
33222 pretend that getting these occasionally is normal and fine.
33223 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
33225 installer screens; and don't put stuff into StartupItems unless
33226 the user asks you to.
33227 - Require servers that use the default dirservers to have public IP
33228 addresses. We have too many servers that are configured with private
33229 IPs and their admins never notice the log entries complaining that
33230 their descriptors are being rejected.
33231 - Add OSX uninstall instructions. An actual uninstall script will
33235 Changes in version 0.1.0.8-rc - 2005-05-23
33237 - It turns out that kqueue on OS X 10.3.9 was causing kernel
33238 panics. Disable kqueue on all OS X Tors.
33239 - Fix RPM: remove duplicate line accidentally added to the rpm
33241 - Disable threads on openbsd too, since its gethostaddr is not
33243 - Tolerate libevent 0.8 since it still works, even though it's
33245 - Enable building on Red Hat 9.0 again.
33246 - Allow the middle hop of the testing circuit to be running any
33247 version, now that most of them have the bugfix to let them connect
33248 to unknown servers. This will allow reachability testing to work
33249 even when 0.0.9.7-0.0.9.9 become obsolete.
33250 - Handle relay cells with rh.length too large. This prevents
33251 a potential attack that could read arbitrary memory (maybe even
33252 keys) from the exit server's process.
33253 - We screwed up the dirport reachability testing when we don't yet
33254 have a cached version of the directory. Hopefully now fixed.
33255 - Clean up router_load_single_router() (used by the controller),
33256 so it doesn't seg fault on error.
33257 - Fix a minor memory leak when somebody establishes an introduction
33258 point at your Tor server.
33259 - If a socks connection ends because read fails, don't warn that
33260 you're not sending a socks reply back.
33263 - Add HttpProxyAuthenticator config option too, that works like
33264 the HttpsProxyAuthenticator config option.
33265 - Encode hashed controller passwords in hex instead of base64,
33266 to make it easier to write controllers.
33269 Changes in version 0.1.0.7-rc - 2005-05-17
33271 - Fix a bug in the OS X package installer that prevented it from
33272 installing on Tiger.
33273 - Fix a script bug in the OS X package installer that made it
33274 complain during installation.
33275 - Find libevent even if it's hiding in /usr/local/ and your
33276 CFLAGS and LDFLAGS don't tell you to look there.
33277 - Be able to link with libevent as a shared library (the default
33278 after 1.0d), even if it's hiding in /usr/local/lib and even
33279 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
33280 assuming you're running gcc. Otherwise fail and give a useful
33282 - Fix a bug in the RPM packager: set home directory for _tor to
33283 something more reasonable when first installing.
33284 - Free a minor amount of memory that is still reachable on exit.
33287 Changes in version 0.1.0.6-rc - 2005-05-14
33289 - Implement --disable-threads configure option. Disable threads on
33290 netbsd by default, because it appears to have no reentrant resolver
33292 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
33293 release (1.1) detects and disables kqueue if it's broken.
33294 - Append default exit policy before checking for implicit internal
33295 addresses. Now we don't log a bunch of complaints on startup
33296 when using the default exit policy.
33297 - Some people were putting "Address " in their torrc, and they had
33298 a buggy resolver that resolved " " to 0.0.0.0. Oops.
33299 - If DataDir is ~/.tor, and that expands to /.tor, then default to
33300 LOCALSTATEDIR/tor instead.
33301 - Fix fragmented-message bug in TorControl.py.
33302 - Resolve a minor bug which would prevent unreachable dirports
33303 from getting suppressed in the published descriptor.
33304 - When the controller gave us a new descriptor, we weren't resolving
33305 it immediately, so Tor would think its address was 0.0.0.0 until
33306 we fetched a new directory.
33307 - Fix an uppercase/lowercase case error in suppressing a bogus
33308 libevent warning on some Linuxes.
33311 - Begin scrubbing sensitive strings from logs by default. Turn off
33312 the config option SafeLogging if you need to do debugging.
33313 - Switch to a new buffer management algorithm, which tries to avoid
33314 reallocing and copying quite as much. In first tests it looks like
33315 it uses *more* memory on average, but less cpu.
33316 - First cut at support for "create-fast" cells. Clients can use
33317 these when extending to their first hop, since the TLS already
33318 provides forward secrecy and authentication. Not enabled on
33320 - When dirservers refuse a router descriptor, we now log its
33321 contactinfo, platform, and the poster's IP address.
33322 - Call tor_free_all instead of connections_free_all after forking, to
33323 save memory on systems that need to fork.
33324 - Whine at you if you're a server and you don't set your contactinfo.
33325 - Implement --verify-config command-line option to check if your torrc
33326 is valid without actually launching Tor.
33327 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
33328 rather than just rejecting it.
33331 Changes in version 0.1.0.5-rc - 2005-04-27
33333 - Stop trying to print a null pointer if an OR conn fails because
33334 we didn't like its cert.
33336 - Switch our internal buffers implementation to use a ring buffer,
33337 to hopefully improve performance for fast servers a lot.
33338 - Add HttpsProxyAuthenticator support (basic auth only), based
33339 on patch from Adam Langley.
33340 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
33341 the fast servers that have been joining lately.
33342 - Give hidden service accesses extra time on the first attempt,
33343 since 60 seconds is often only barely enough. This might improve
33345 - Improve performance for dirservers: stop re-parsing the whole
33346 directory every time you regenerate it.
33347 - Add more debugging info to help us find the weird dns freebsd
33348 pthreads bug; cleaner debug messages to help track future issues.
33351 Changes in version 0.0.9.9 - 2005-04-23
33352 o Bugfixes on 0.0.9.x:
33353 - If unofficial Tor clients connect and send weird TLS certs, our
33354 Tor server triggers an assert. This release contains a minimal
33355 backport from the broader fix that we put into 0.1.0.4-rc.
33358 Changes in version 0.1.0.4-rc - 2005-04-23
33360 - If unofficial Tor clients connect and send weird TLS certs, our
33361 Tor server triggers an assert. Stop asserting, and start handling
33362 TLS errors better in other situations too.
33363 - When the controller asks us to tell it about all the debug-level
33364 logs, it turns out we were generating debug-level logs while
33365 telling it about them, which turns into a bad loop. Now keep
33366 track of whether you're sending a debug log to the controller,
33367 and don't log when you are.
33368 - Fix the "postdescriptor" feature of the controller interface: on
33369 non-complete success, only say "done" once.
33371 - Clients are now willing to load balance over up to 2mB, not 1mB,
33372 of advertised bandwidth capacity.
33373 - Add a NoPublish config option, so you can be a server (e.g. for
33374 testing running Tor servers in other Tor networks) without
33375 publishing your descriptor to the primary dirservers.
33378 Changes in version 0.1.0.3-rc - 2005-04-08
33379 o Improvements on 0.1.0.2-rc:
33380 - Client now retries when streams end early for 'hibernating' or
33381 'resource limit' reasons, rather than failing them.
33382 - More automated handling for dirserver operators:
33383 - Automatically approve nodes running 0.1.0.2-rc or later,
33384 now that the the reachability detection stuff is working.
33385 - Now we allow two unverified servers with the same nickname
33386 but different keys. But if a nickname is verified, only that
33387 nickname+key are allowed.
33388 - If you're an authdirserver connecting to an address:port,
33389 and it's not the OR you were expecting, forget about that
33390 descriptor. If he *was* the one you were expecting, then forget
33391 about all other descriptors for that address:port.
33392 - Allow servers to publish descriptors from 12 hours in the future.
33393 Corollary: only whine about clock skew from the dirserver if
33394 he's a trusted dirserver (since now even verified servers could
33395 have quite wrong clocks).
33396 - Adjust maximum skew and age for rendezvous descriptors: let skew
33397 be 48 hours rather than 90 minutes.
33398 - Efficiency improvements:
33399 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
33400 it much faster to look up a circuit for each relay cell.
33401 - Remove most calls to assert_all_pending_dns_resolves_ok(),
33402 since they're eating our cpu on exit nodes.
33403 - Stop wasting time doing a case insensitive comparison for every
33404 dns name every time we do any lookup. Canonicalize the names to
33405 lowercase and be done with it.
33406 - Start sending 'truncated' cells back rather than destroy cells,
33407 if the circuit closes in front of you. This means we won't have
33408 to abandon partially built circuits.
33409 - Only warn once per nickname from add_nickname_list_to_smartlist
33410 per failure, so an entrynode or exitnode choice that's down won't
33412 - Put a note in the torrc about abuse potential with the default
33414 - Revise control spec and implementation to allow all log messages to
33415 be sent to controller with their severities intact (suggested by
33416 Matt Edman). Update TorControl to handle new log event types.
33417 - Provide better explanation messages when controller's POSTDESCRIPTOR
33419 - Stop putting nodename in the Platform string in server descriptors.
33420 It doesn't actually help, and it is confusing/upsetting some people.
33422 o Bugfixes on 0.1.0.2-rc:
33423 - We were printing the host mask wrong in exit policies in server
33424 descriptors. This isn't a critical bug though, since we were still
33425 obeying the exit policy internally.
33426 - Fix Tor when compiled with libevent but without pthreads: move
33427 connection_unregister() from _connection_free() to
33429 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
33430 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
33431 when we look through the connection array, we'll find any of the
33432 cpu/dnsworkers. This is no good.
33434 o Bugfixes on 0.0.9.8:
33435 - Fix possible bug on threading platforms (e.g. win32) which was
33436 leaking a file descriptor whenever a cpuworker or dnsworker died.
33437 - When using preferred entry or exit nodes, ignore whether the
33438 circuit wants uptime or capacity. They asked for the nodes, they
33440 - chdir() to your datadirectory at the *end* of the daemonize process,
33441 not the beginning. This was a problem because the first time you
33442 run tor, if your datadir isn't there, and you have runasdaemon set
33443 to 1, it will try to chdir to it before it tries to create it. Oops.
33444 - Handle changed router status correctly when dirserver reloads
33445 fingerprint file. We used to be dropping all unverified descriptors
33446 right then. The bug was hidden because we would immediately
33447 fetch a directory from another dirserver, which would include the
33448 descriptors we just dropped.
33449 - When we're connecting to an OR and he's got a different nickname/key
33450 than we were expecting, only complain loudly if we're an OP or a
33451 dirserver. Complaining loudly to the OR admins just confuses them.
33452 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
33453 artificially capped at 500kB.
33456 Changes in version 0.0.9.8 - 2005-04-07
33457 o Bugfixes on 0.0.9.x:
33458 - We have a bug that I haven't found yet. Sometimes, very rarely,
33459 cpuworkers get stuck in the 'busy' state, even though the cpuworker
33460 thinks of itself as idle. This meant that no new circuits ever got
33461 established. Here's a workaround to kill any cpuworker that's been
33462 busy for more than 100 seconds.
33465 Changes in version 0.1.0.2-rc - 2005-04-01
33466 o Bugfixes on 0.1.0.1-rc:
33467 - Fixes on reachability detection:
33468 - Don't check for reachability while hibernating.
33469 - If ORPort is reachable but DirPort isn't, still publish the
33470 descriptor, but zero out DirPort until it's found reachable.
33471 - When building testing circs for ORPort testing, use only
33472 high-bandwidth nodes, so fewer circuits fail.
33473 - Complain about unreachable ORPort separately from unreachable
33474 DirPort, so the user knows what's going on.
33475 - Make sure we only conclude ORPort reachability if we didn't
33476 initiate the conn. Otherwise we could falsely conclude that
33477 we're reachable just because we connected to the guy earlier
33478 and he used that same pipe to extend to us.
33479 - Authdirservers shouldn't do ORPort reachability detection,
33480 since they're in clique mode, so it will be rare to find a
33481 server not already connected to them.
33482 - When building testing circuits, always pick middle hops running
33483 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
33484 bug. (This is a kludge; it will go away when 0.0.9.x becomes
33486 - When we decide we're reachable, actually publish our descriptor
33488 - Fix bug in redirectstream in the controller.
33489 - Fix the state descriptor strings so logs don't claim edge streams
33490 are in a different state than they actually are.
33491 - Use recent libevent features when possible (this only really affects
33492 win32 and osx right now, because the new libevent with these
33493 features hasn't been released yet). Add code to suppress spurious
33495 - Prevent possible segfault in connection_close_unattached_ap().
33496 - Fix newlines on torrc in win32.
33497 - Improve error msgs when tor-resolve fails.
33499 o Improvements on 0.0.9.x:
33500 - New experimental script tor/contrib/ExerciseServer.py (needs more
33501 work) that uses the controller interface to build circuits and
33502 fetch pages over them. This will help us bootstrap servers that
33503 have lots of capacity but haven't noticed it yet.
33504 - New experimental script tor/contrib/PathDemo.py (needs more work)
33505 that uses the controller interface to let you choose whole paths
33507 "<hostname>.<path,separated by dots>.<length of path>.path"
33508 - When we've connected to an OR and handshaked but didn't like
33509 the result, we were closing the conn without sending destroy
33510 cells back for pending circuits. Now send those destroys.
33513 Changes in version 0.0.9.7 - 2005-04-01
33514 o Bugfixes on 0.0.9.x:
33515 - Fix another race crash bug (thanks to Glenn Fink for reporting).
33516 - Compare identity to identity, not to nickname, when extending to
33517 a router not already in the directory. This was preventing us from
33518 extending to unknown routers. Oops.
33519 - Make sure to create OS X Tor user in <500 range, so we aren't
33520 creating actual system users.
33521 - Note where connection-that-hasn't-sent-end was marked, and fix
33522 a few really loud instances of this harmless bug (it's fixed more
33526 Changes in version 0.1.0.1-rc - 2005-03-28
33528 - Add reachability testing. Your Tor server will automatically try
33529 to see if its ORPort and DirPort are reachable from the outside,
33530 and it won't upload its descriptor until it decides they are.
33531 - Handle unavailable hidden services better. Handle slow or busy
33532 hidden services better.
33533 - Add support for CONNECTing through https proxies, with "HttpsProxy"
33535 - New exit policy: accept most low-numbered ports, rather than
33536 rejecting most low-numbered ports.
33537 - More Tor controller support (still experimental). See
33538 http://tor.eff.org/doc/control-spec.txt for all the new features,
33539 including signals to emulate unix signals from any platform;
33540 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
33541 closestream; closecircuit; etc.
33542 - Make nt services work and start on startup on win32 (based on
33543 patch by Matt Edman).
33544 - Add a new AddressMap config directive to rewrite incoming socks
33545 addresses. This lets you, for example, declare an implicit
33546 required exit node for certain sites.
33547 - Add a new TrackHostExits config directive to trigger addressmaps
33548 for certain incoming socks addresses -- for sites that break when
33549 your exit keeps changing (based on patch by Mike Perry).
33550 - Redo the client-side dns cache so it's just an addressmap too.
33551 - Notice when our IP changes, and reset stats/uptime/reachability.
33552 - When an application is using socks5, give him the whole variety of
33553 potential socks5 responses (connect refused, host unreachable, etc),
33554 rather than just "success" or "failure".
33555 - A more sane version numbering system. See
33556 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
33557 - New contributed script "exitlist": a simple python script to
33558 parse directories and find Tor nodes that exit to listed
33560 - New contributed script "privoxy-tor-toggle" to toggle whether
33561 Privoxy uses Tor. Seems to be configured for Debian by default.
33562 - Report HTTP reasons to client when getting a response from directory
33563 servers -- so you can actually know what went wrong.
33564 - New config option MaxAdvertisedBandwidth which lets you advertise
33565 a low bandwidthrate (to not attract as many circuits) while still
33566 allowing a higher bandwidthrate in reality.
33568 o Robustness/stability fixes:
33569 - Make Tor use Niels Provos's libevent instead of its current
33570 poll-but-sometimes-select mess. This will let us use faster async
33571 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
33573 - pthread support now too. This was forced because when we forked,
33574 we ended up wasting a lot of duplicate ram over time. Also switch
33575 to foo_r versions of some library calls to allow reentry and
33577 - Better handling for heterogeneous / unreliable nodes:
33578 - Annotate circuits w/ whether they aim to contain high uptime nodes
33579 and/or high capacity nodes. When building circuits, choose
33581 - This means that every single node in an intro rend circuit,
33582 not just the last one, will have a minimum uptime.
33583 - New config option LongLivedPorts to indicate application streams
33584 that will want high uptime circuits.
33585 - Servers reset uptime when a dir fetch entirely fails. This
33586 hopefully reflects stability of the server's network connectivity.
33587 - If somebody starts his tor server in Jan 2004 and then fixes his
33588 clock, don't make his published uptime be a year.
33589 - Reset published uptime when you wake up from hibernation.
33590 - Introduce a notion of 'internal' circs, which are chosen without
33591 regard to the exit policy of the last hop. Intro and rendezvous
33592 circs must be internal circs, to avoid leaking information. Resolve
33593 and connect streams can use internal circs if they want.
33594 - New circuit pooling algorithm: make sure to have enough circs around
33595 to satisfy any predicted ports, and also make sure to have 2 internal
33596 circs around if we've required internal circs lately (and with high
33597 uptime if we've seen that lately too).
33598 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
33599 which describes how often we retry making new circuits if current
33600 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
33601 how long we're willing to make use of an already-dirty circuit.
33602 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
33603 circ as necessary, if there are any completed ones lying around
33604 when we try to launch one.
33605 - Make hidden services try to establish a rendezvous for 30 seconds,
33606 rather than for n (where n=3) attempts to build a circuit.
33607 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
33608 "ShutdownWaitLength".
33609 - Try to be more zealous about calling connection_edge_end when
33610 things go bad with edge conns in connection.c.
33611 - Revise tor-spec to add more/better stream end reasons.
33612 - Revise all calls to connection_edge_end to avoid sending "misc",
33613 and to take errno into account where possible.
33616 - Fix a race condition that can trigger an assert, when we have a
33617 pending create cell and an OR connection fails right then.
33618 - Fix several double-mark-for-close bugs, e.g. where we were finding
33619 a conn for a cell even if that conn is already marked for close.
33620 - Make sequence of log messages when starting on win32 with no config
33621 file more reasonable.
33622 - When choosing an exit node for a new non-internal circ, don't take
33623 into account whether it'll be useful for any pending x.onion
33624 addresses -- it won't.
33625 - Turn addr_policy_compare from a tristate to a quadstate; this should
33626 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
33627 for google.com" problem.
33628 - Make "platform" string in descriptor more accurate for Win32 servers,
33629 so it's not just "unknown platform".
33630 - Fix an edge case in parsing config options (thanks weasel).
33631 If they say "--" on the commandline, it's not an option.
33632 - Reject odd-looking addresses at the client (e.g. addresses that
33633 contain a colon), rather than having the server drop them because
33635 - tor-resolve requests were ignoring .exit if there was a working circuit
33636 they could use instead.
33637 - REUSEADDR on normal platforms means you can rebind to the port
33638 right after somebody else has let it go. But REUSEADDR on win32
33639 means to let you bind to the port _even when somebody else
33640 already has it bound_! So, don't do that on Win32.
33641 - Change version parsing logic: a version is "obsolete" if it is not
33642 recommended and (1) there is a newer recommended version in the
33643 same series, or (2) there are no recommended versions in the same
33644 series, but there are some recommended versions in a newer series.
33645 A version is "new" if it is newer than any recommended version in
33647 - Stop most cases of hanging up on a socks connection without sending
33651 - Require BandwidthRate to be at least 20kB/s for servers.
33652 - When a dirserver causes you to give a warn, mention which dirserver
33654 - New config option DirAllowPrivateAddresses for authdirservers.
33655 Now by default they refuse router descriptors that have non-IP or
33656 private-IP addresses.
33657 - Stop publishing socksport in the directory, since it's not
33658 actually meant to be public. For compatibility, publish a 0 there
33660 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
33661 smart" value, that is low for servers and high for clients.
33662 - If our clock jumps forward by 100 seconds or more, assume something
33663 has gone wrong with our network and abandon all not-yet-used circs.
33664 - Warn when exit policy implicitly allows local addresses.
33665 - If we get an incredibly skewed timestamp from a dirserver mirror
33666 that isn't a verified OR, don't warn -- it's probably him that's
33668 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
33669 cookies to disk and doesn't log each web request to disk. (Thanks
33670 to Brett Carrington for pointing this out.)
33671 - When a client asks us for a dir mirror and we don't have one,
33672 launch an attempt to get a fresh one.
33673 - If we're hibernating and we get a SIGINT, exit immediately.
33674 - Add --with-dmalloc ./configure option, to track memory leaks.
33675 - And try to free all memory on closing, so we can detect what
33677 - Cache local dns resolves correctly even when they're .exit
33679 - Give a better warning when some other server advertises an
33680 ORPort that is actually an apache running ssl.
33681 - Add "opt hibernating 1" to server descriptor to make it clearer
33682 whether the server is hibernating.
33685 Changes in version 0.0.9.6 - 2005-03-24
33686 o Bugfixes on 0.0.9.x (crashes and asserts):
33687 - Add new end stream reasons to maintenance branch. Fix bug where
33688 reason (8) could trigger an assert. Prevent bug from recurring.
33689 - Apparently win32 stat wants paths to not end with a slash.
33690 - Fix assert triggers in assert_cpath_layer_ok(), where we were
33691 blowing away the circuit that conn->cpath_layer points to, then
33692 checking to see if the circ is well-formed. Backport check to make
33693 sure we dont use the cpath on a closed connection.
33694 - Prevent circuit_resume_edge_reading_helper() from trying to package
33695 inbufs for marked-for-close streams.
33696 - Don't crash on hup if your options->address has become unresolvable.
33697 - Some systems (like OS X) sometimes accept() a connection and tell
33698 you the remote host is 0.0.0.0:0. If this happens, due to some
33699 other mis-features, we get confused; so refuse the conn for now.
33701 o Bugfixes on 0.0.9.x (other):
33702 - Fix harmless but scary "Unrecognized content encoding" warn message.
33703 - Add new stream error reason: TORPROTOCOL reason means "you are not
33704 speaking a version of Tor I understand; say bye-bye to your stream."
33705 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
33706 into the future, now that we are more tolerant of skew. This
33707 resolves a bug where a Tor server would refuse to cache a directory
33708 because all the directories it gets are too far in the future;
33709 yet the Tor server never logs any complaints about clock skew.
33710 - Mac packaging magic: make man pages useable, and do not overwrite
33711 existing torrc files.
33712 - Make OS X log happily to /var/log/tor/tor.log
33715 Changes in version 0.0.9.5 - 2005-02-22
33716 o Bugfixes on 0.0.9.x:
33717 - Fix an assert race at exit nodes when resolve requests fail.
33718 - Stop picking unverified dir mirrors--it only leads to misery.
33719 - Patch from Matt Edman to make NT services work better. Service
33720 support is still not compiled into the executable by default.
33721 - Patch from Dmitri Bely so the Tor service runs better under
33722 the win32 SYSTEM account.
33723 - Make tor-resolve actually work (?) on Win32.
33724 - Fix a sign bug when getrlimit claims to have 4+ billion
33725 file descriptors available.
33726 - Stop refusing to start when bandwidthburst == bandwidthrate.
33727 - When create cells have been on the onion queue more than five
33728 seconds, just send back a destroy and take them off the list.
33731 Changes in version 0.0.9.4 - 2005-02-03
33732 o Bugfixes on 0.0.9:
33733 - Fix an assert bug that took down most of our servers: when
33734 a server claims to have 1 GB of bandwidthburst, don't
33736 - Don't crash as badly if we have spawned the max allowed number
33737 of dnsworkers, or we're out of file descriptors.
33738 - Block more file-sharing ports in the default exit policy.
33739 - MaxConn is now automatically set to the hard limit of max
33740 file descriptors we're allowed (ulimit -n), minus a few for
33742 - Give a clearer message when servers need to raise their
33743 ulimit -n when they start running out of file descriptors.
33744 - SGI Compatibility patches from Jan Schaumann.
33745 - Tolerate a corrupt cached directory better.
33746 - When a dirserver hasn't approved your server, list which one.
33747 - Go into soft hibernation after 95% of the bandwidth is used,
33748 not 99%. This is especially important for daily hibernators who
33749 have a small accounting max. Hopefully it will result in fewer
33750 cut connections when the hard hibernation starts.
33751 - Load-balance better when using servers that claim more than
33752 800kB/s of capacity.
33753 - Make NT services work (experimental, only used if compiled in).
33756 Changes in version 0.0.9.3 - 2005-01-21
33757 o Bugfixes on 0.0.9:
33758 - Backport the cpu use fixes from main branch, so busy servers won't
33759 need as much processor time.
33760 - Work better when we go offline and then come back, or when we
33761 run Tor at boot before the network is up. We do this by
33762 optimistically trying to fetch a new directory whenever an
33763 application request comes in and we think we're offline -- the
33764 human is hopefully a good measure of when the network is back.
33765 - Backport some minimal hidserv bugfixes: keep rend circuits open as
33766 long as you keep using them; actually publish hidserv descriptors
33767 shortly after they change, rather than waiting 20-40 minutes.
33768 - Enable Mac startup script by default.
33769 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
33770 - When you update AllowUnverifiedNodes or FirewallPorts via the
33771 controller's setconf feature, we were always appending, never
33773 - When you update HiddenServiceDir via setconf, it was screwing up
33774 the order of reading the lines, making it fail.
33775 - Do not rewrite a cached directory back to the cache; otherwise we
33776 will think it is recent and not fetch a newer one on startup.
33777 - Workaround for webservers that lie about Content-Encoding: Tor
33778 now tries to autodetect compressed directories and compression
33779 itself. This lets us Proxypass dir fetches through apache.
33782 Changes in version 0.0.9.2 - 2005-01-04
33783 o Bugfixes on 0.0.9 (crashes and asserts):
33784 - Fix an assert on startup when the disk is full and you're logging
33786 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
33787 style address, then we'd crash.
33788 - Fix an assert trigger when the running-routers string we get from
33789 a dirserver is broken.
33790 - Make worker threads start and run on win32. Now win32 servers
33792 - Bandaid (not actually fix, but now it doesn't crash) an assert
33793 where the dns worker dies mysteriously and the main Tor process
33794 doesn't remember anything about the address it was resolving.
33796 o Bugfixes on 0.0.9 (Win32):
33797 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
33798 name out of the warning/assert messages.
33799 - Fix a superficial "unhandled error on read" bug on win32.
33800 - The win32 installer no longer requires a click-through for our
33801 license, since our Free Software license grants rights but does not
33803 - Win32: When connecting to a dirserver fails, try another one
33804 immediately. (This was already working for non-win32 Tors.)
33805 - Stop trying to parse $HOME on win32 when hunting for default
33807 - Make tor-resolve.c work on win32 by calling network_init().
33809 o Bugfixes on 0.0.9 (other):
33810 - Make 0.0.9.x build on Solaris again.
33811 - Due to a fencepost error, we were blowing away the \n when reporting
33812 confvalue items in the controller. So asking for multiple config
33813 values at once couldn't work.
33814 - When listing circuits that are pending on an opening OR connection,
33815 if we're an OR we were listing circuits that *end* at us as
33816 being pending on every listener, dns/cpu worker, etc. Stop that.
33817 - Dirservers were failing to create 'running-routers' or 'directory'
33818 strings if we had more than some threshold of routers. Fix them so
33819 they can handle any number of routers.
33820 - Fix a superficial "Duplicate mark for close" bug.
33821 - Stop checking for clock skew for OR connections, even for servers.
33822 - Fix a fencepost error that was chopping off the last letter of any
33823 nickname that is the maximum allowed nickname length.
33824 - Update URLs in log messages so they point to the new website.
33825 - Fix a potential problem in mangling server private keys while
33826 writing to disk (not triggered yet, as far as we know).
33827 - Include the licenses for other free software we include in Tor,
33828 now that we're shipping binary distributions more regularly.
33831 Changes in version 0.0.9.1 - 2004-12-15
33832 o Bugfixes on 0.0.9:
33833 - Make hibernation actually work.
33834 - Make HashedControlPassword config option work.
33835 - When we're reporting event circuit status to a controller,
33836 don't use the stream status code.
33839 Changes in version 0.0.9 - 2004-12-12
33841 - Clean up manpage and torrc.sample file.
33842 - Clean up severities and text of log warnings.
33844 - Make servers trigger an assert when they enter hibernation.
33847 Changes in version 0.0.9rc7 - 2004-12-08
33848 o Bugfixes on 0.0.9rc:
33849 - Fix a stack-trashing crash when an exit node begins hibernating.
33850 - Avoid looking at unallocated memory while considering which
33851 ports we need to build circuits to cover.
33852 - Stop a sigpipe: when an 'end' cell races with eof from the app,
33853 we shouldn't hold-open-until-flush if the eof arrived first.
33854 - Fix a bug with init_cookie_authentication() in the controller.
33855 - When recommending new-format log lines, if the upper bound is
33856 LOG_ERR, leave it implicit.
33858 o Bugfixes on 0.0.8.1:
33859 - Fix a whole slew of memory leaks.
33860 - Fix isspace() and friends so they still make Solaris happy
33861 but also so they don't trigger asserts on win32.
33862 - Fix parse_iso_time on platforms without strptime (eg win32).
33863 - win32: tolerate extra "readable" events better.
33864 - win32: when being multithreaded, leave parent fdarray open.
33865 - Make unit tests work on win32.
33868 Changes in version 0.0.9rc6 - 2004-12-06
33869 o Bugfixes on 0.0.9pre:
33870 - Clean up some more integer underflow opportunities (not exploitable
33872 - While hibernating, hup should not regrow our listeners.
33873 - Send an end to the streams we close when we hibernate, rather
33874 than just chopping them off.
33875 - React to eof immediately on non-open edge connections.
33877 o Bugfixes on 0.0.8.1:
33878 - Calculate timeout for waiting for a connected cell from the time
33879 we sent the begin cell, not from the time the stream started. If
33880 it took a long time to establish the circuit, we would time out
33881 right after sending the begin cell.
33882 - Fix router_compare_addr_to_addr_policy: it was not treating a port
33883 of * as always matching, so we were picking reject *:* nodes as
33884 exit nodes too. Oops.
33887 - New circuit building strategy: keep a list of ports that we've
33888 used in the past 6 hours, and always try to have 2 circuits open
33889 or on the way that will handle each such port. Seed us with port
33890 80 so web users won't complain that Tor is "slow to start up".
33891 - Make kill -USR1 dump more useful stats about circuits.
33892 - When warning about retrying or giving up, print the address, so
33893 the user knows which one it's talking about.
33894 - If you haven't used a clean circuit in an hour, throw it away,
33895 just to be on the safe side. (This means after 6 hours a totally
33896 unused Tor client will have no circuits open.)
33899 Changes in version 0.0.9rc5 - 2004-12-01
33900 o Bugfixes on 0.0.8.1:
33901 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
33902 - Let resolve conns retry/expire also, rather than sticking around
33904 - If we are using select, make sure we stay within FD_SETSIZE.
33906 o Bugfixes on 0.0.9pre:
33907 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
33908 but doesn't seem to be currently; thanks to Ilja van Sprundel for
33910 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
33911 instead. Impose minima and maxima for all *Period options; impose
33912 even tighter maxima for fetching if we are a caching dirserver.
33913 Clip rather than rejecting.
33914 - Fetch cached running-routers from servers that serve it (that is,
33915 authdirservers and servers running 0.0.9rc5-cvs or later.)
33918 - Accept *:706 (silc) in default exit policy.
33919 - Implement new versioning format for post 0.1.
33920 - Support "foo.nickname.exit" addresses, to let Alice request the
33921 address "foo" as viewed by exit node "nickname". Based on a patch
33923 - Make tor --version --version dump the cvs Id of every file.
33926 Changes in version 0.0.9rc4 - 2004-11-28
33927 o Bugfixes on 0.0.8.1:
33928 - Make windows sockets actually non-blocking (oops), and handle
33929 win32 socket errors better.
33931 o Bugfixes on 0.0.9rc1:
33932 - Actually catch the -USR2 signal.
33935 Changes in version 0.0.9rc3 - 2004-11-25
33936 o Bugfixes on 0.0.8.1:
33937 - Flush the log file descriptor after we print "Tor opening log file",
33938 so we don't see those messages days later.
33940 o Bugfixes on 0.0.9rc1:
33941 - Make tor-resolve work again.
33942 - Avoid infinite loop in tor-resolve if tor hangs up on it.
33943 - Fix an assert trigger for clients/servers handling resolves.
33946 Changes in version 0.0.9rc2 - 2004-11-24
33947 o Bugfixes on 0.0.9rc1:
33948 - I broke socks5 support while fixing the eof bug.
33949 - Allow unitless bandwidths and intervals; they default to bytes
33951 - New servers don't start out hibernating; they are active until
33952 they run out of bytes, so they have a better estimate of how
33953 long it takes, and so their operators can know they're working.
33956 Changes in version 0.0.9rc1 - 2004-11-23
33957 o Bugfixes on 0.0.8.1:
33958 - Finally fix a bug that's been plaguing us for a year:
33959 With high load, circuit package window was reaching 0. Whenever
33960 we got a circuit-level sendme, we were reading a lot on each
33961 socket, but only writing out a bit. So we would eventually reach
33962 eof. This would be noticed and acted on even when there were still
33963 bytes sitting in the inbuf.
33964 - When poll() is interrupted, we shouldn't believe the revents values.
33966 o Bugfixes on 0.0.9pre6:
33967 - Fix hibernate bug that caused pre6 to be broken.
33968 - Don't keep rephist info for routers that haven't had activity for
33969 24 hours. (This matters now that clients have keys, since we track
33971 - Never call close_temp_logs while validating log options.
33972 - Fix backslash-escaping on tor.sh.in and torctl.in.
33975 - Implement weekly/monthly/daily accounting: now you specify your
33976 hibernation properties by
33977 AccountingMax N bytes|KB|MB|GB|TB
33978 AccountingStart day|week|month [day] HH:MM
33979 Defaults to "month 1 0:00".
33980 - Let bandwidth and interval config options be specified as 5 bytes,
33981 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
33982 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
33983 get back to normal.)
33984 - If your requested entry or exit node has advertised bandwidth 0,
33986 - Be more greedy about filling up relay cells -- we try reading again
33987 once we've processed the stuff we read, in case enough has arrived
33988 to fill the last cell completely.
33989 - Apply NT service patch from Osamu Fujino. Still needs more work.
33992 Changes in version 0.0.9pre6 - 2004-11-15
33993 o Bugfixes on 0.0.8.1:
33994 - Fix assert failure on malformed socks4a requests.
33995 - Use identity comparison, not nickname comparison, to choose which
33996 half of circuit-ID-space each side gets to use. This is needed
33997 because sometimes we think of a router as a nickname, and sometimes
33998 as a hex ID, and we can't predict what the other side will do.
33999 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
34000 write() call will fail and we handle it there.
34001 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
34002 and smartlist_len, which are two major profiling offenders.
34004 o Bugfixes on 0.0.9pre5:
34005 - Fix a bug in read_all that was corrupting config files on windows.
34006 - When we're raising the max number of open file descriptors to
34007 'unlimited', don't log that we just raised it to '-1'.
34008 - Include event code with events, as required by control-spec.txt.
34009 - Don't give a fingerprint when clients do --list-fingerprint:
34010 it's misleading, because it will never be the same again.
34011 - Stop using strlcpy in tor_strndup, since it was slowing us
34013 - Remove warn on startup about missing cached-directory file.
34014 - Make kill -USR1 work again.
34015 - Hibernate if we start tor during the "wait for wakeup-time" phase
34016 of an accounting interval. Log our hibernation plans better.
34017 - Authoritative dirservers now also cache their directory, so they
34018 have it on start-up.
34021 - Fetch running-routers; cache running-routers; compress
34022 running-routers; serve compressed running-routers.z
34023 - Add NSI installer script contributed by J Doe.
34024 - Commit VC6 and VC7 workspace/project files.
34025 - Commit a tor.spec for making RPM files, with help from jbash.
34026 - Add contrib/torctl.in contributed by Glenn Fink.
34027 - Implement the control-spec's SAVECONF command, to write your
34028 configuration to torrc.
34029 - Get cookie authentication for the controller closer to working.
34030 - Include control-spec.txt in the tarball.
34031 - When set_conf changes our server descriptor, upload a new copy.
34032 But don't upload it too often if there are frequent changes.
34033 - Document authentication config in man page, and document signals
34035 - Clean up confusing parts of man page and torrc.sample.
34036 - Make expand_filename handle ~ and ~username.
34037 - Use autoconf to enable largefile support where necessary. Use
34038 ftello where available, since ftell can fail at 2GB.
34039 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
34040 log more informatively.
34041 - Give a slightly more useful output for "tor -h".
34042 - Refuse application socks connections to port 0.
34043 - Check clock skew for verified servers, but allow unverified
34044 servers and clients to have any clock skew.
34045 - Break DirFetchPostPeriod into:
34046 - DirFetchPeriod for fetching full directory,
34047 - StatusFetchPeriod for fetching running-routers,
34048 - DirPostPeriod for posting server descriptor,
34049 - RendPostPeriod for posting hidden service descriptors.
34050 - Make sure the hidden service descriptors are at a random offset
34051 from each other, to hinder linkability.
34054 Changes in version 0.0.9pre5 - 2004-11-09
34055 o Bugfixes on 0.0.9pre4:
34056 - Fix a seg fault in unit tests (doesn't affect main program).
34057 - Fix an assert bug where a hidden service provider would fail if
34058 the first hop of his rendezvous circuit was down.
34059 - Hidden service operators now correctly handle version 1 style
34060 INTRODUCE1 cells (nobody generates them still, so not a critical
34062 - If do_hup fails, actually notice.
34063 - Handle more errnos from accept() without closing the listener.
34064 Some OpenBSD machines were closing their listeners because
34065 they ran out of file descriptors.
34066 - Send resolve cells to exit routers that are running a new
34067 enough version of the resolve code to work right.
34068 - Better handling of winsock includes on non-MSV win32 compilers.
34069 - Some people had wrapped their tor client/server in a script
34070 that would restart it whenever it died. This did not play well
34071 with our "shut down if your version is obsolete" code. Now people
34072 don't fetch a new directory if their local cached version is
34074 - Make our autogen.sh work on ksh as well as bash.
34077 - Hibernation: New config option "AccountingMaxKB" lets you
34078 set how many KBytes per month you want to allow your server to
34079 consume. Rather than spreading those bytes out evenly over the
34080 month, we instead hibernate for some of the month and pop up
34081 at a deterministic time, work until the bytes are consumed, then
34082 hibernate again. Config option "MonthlyAccountingStart" lets you
34083 specify which day of the month your billing cycle starts on.
34084 - Control interface: a separate program can now talk to your
34085 client/server over a socket, and get/set config options, receive
34086 notifications of circuits and streams starting/finishing/dying,
34087 bandwidth used, etc. The next step is to get some GUIs working.
34088 Let us know if you want to help out. See doc/control-spec.txt .
34089 - Ship a contrib/tor-control.py as an example script to interact
34090 with the control port.
34091 - "tor --hash-password zzyxz" will output a salted password for
34092 use in authenticating to the control interface.
34093 - New log format in config:
34094 "Log minsev[-maxsev] stdout|stderr|syslog" or
34095 "Log minsev[-maxsev] file /var/foo"
34098 - DirPolicy config option, to let people reject incoming addresses
34099 from their dirserver.
34100 - "tor --list-fingerprint" will list your identity key fingerprint
34102 - Add "pass" target for RedirectExit, to make it easier to break
34103 out of a sequence of RedirectExit rules.
34104 - Clients now generate a TLS cert too, in preparation for having
34105 them act more like real nodes.
34106 - Ship src/win32/ in the tarball, so people can use it to build.
34107 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
34109 - New "router-status" line in directory, to better bind each verified
34110 nickname to its identity key.
34111 - Deprecate unofficial config option abbreviations, and abbreviations
34112 not on the command line.
34113 - Add a pure-C tor-resolve implementation.
34114 - Use getrlimit and friends to ensure we can reach MaxConn (currently
34115 1024) file descriptors.
34117 o Code security improvements, inspired by Ilja:
34118 - Replace sprintf with snprintf. (I think they were all safe, but
34120 - Replace strcpy/strncpy with strlcpy in more places.
34121 - Avoid strcat; use snprintf or strlcat instead.
34122 - snprintf wrapper with consistent (though not C99) overflow behavior.
34125 Changes in version 0.0.9pre4 - 2004-10-17
34126 o Bugfixes on 0.0.9pre3:
34127 - If the server doesn't specify an exit policy, use the real default
34128 exit policy, not reject *:*.
34129 - Ignore fascistfirewall when uploading/downloading hidden service
34130 descriptors, since we go through Tor for those; and when using
34131 an HttpProxy, since we assume it can reach them all.
34132 - When looking for an authoritative dirserver, use only the ones
34133 configured at boot. Don't bother looking in the directory.
34134 - The rest of the fix for get_default_conf_file() on older win32.
34135 - Make 'Routerfile' config option obsolete.
34138 - New 'MyFamily nick1,...' config option for a server to
34139 specify other servers that shouldn't be used in the same circuit
34140 with it. Only believed if nick1 also specifies us.
34141 - New 'NodeFamily nick1,nick2,...' config option for a client to
34142 specify nodes that it doesn't want to use in the same circuit.
34143 - New 'Redirectexit pattern address:port' config option for a
34144 server to redirect exit connections, e.g. to a local squid.
34147 Changes in version 0.0.9pre3 - 2004-10-13
34148 o Bugfixes on 0.0.8.1:
34149 - Better torrc example lines for dirbindaddress and orbindaddress.
34150 - Improved bounds checking on parsed ints (e.g. config options and
34151 the ones we find in directories.)
34152 - Better handling of size_t vs int, so we're more robust on 64
34154 - Fix the rest of the bug where a newly started OR would appear
34155 as unverified even after we've added his fingerprint and hupped
34157 - Fix a bug from 0.0.7: when read() failed on a stream, we would
34158 close it without sending back an end. So 'connection refused'
34159 would simply be ignored and the user would get no response.
34161 o Bugfixes on 0.0.9pre2:
34162 - Serving the cached-on-disk directory to people is bad. We now
34163 provide no directory until we've fetched a fresh one.
34164 - Workaround for bug on windows where cached-directories get crlf
34166 - Make get_default_conf_file() work on older windows too.
34167 - If we write a *:* exit policy line in the descriptor, don't write
34168 any more exit policy lines.
34171 - Use only 0.0.9pre1 and later servers for resolve cells.
34172 - Make the dirservers file obsolete.
34173 - Include a dir-signing-key token in directories to tell the
34174 parsing entity which key is being used to sign.
34175 - Remove the built-in bulky default dirservers string.
34176 - New config option "Dirserver %s:%d [fingerprint]", which can be
34177 repeated as many times as needed. If no dirservers specified,
34178 default to moria1,moria2,tor26.
34179 - Make moria2 advertise a dirport of 80, so people behind firewalls
34180 will be able to get a directory.
34181 - Http proxy support
34182 - Dirservers translate requests for http://%s:%d/x to /x
34183 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
34184 be routed through this host.
34185 - Clients ask for /tor/x rather than /x for new enough dirservers.
34186 This way we can one day coexist peacefully with apache.
34187 - Clients specify a "Host: %s%d" http header, to be compatible
34188 with more proxies, and so running squid on an exit node can work.
34191 Changes in version 0.0.8.1 - 2004-10-13
34193 - Fix a seg fault that can be triggered remotely for Tor
34194 clients/servers with an open dirport.
34195 - Fix a rare assert trigger, where routerinfos for entries in
34196 our cpath would expire while we're building the path.
34197 - Fix a bug in OutboundBindAddress so it (hopefully) works.
34198 - Fix a rare seg fault for people running hidden services on
34199 intermittent connections.
34200 - Fix a bug in parsing opt keywords with objects.
34201 - Fix a stale pointer assert bug when a stream detaches and
34203 - Fix a string format vulnerability (probably not exploitable)
34204 in reporting stats locally.
34205 - Fix an assert trigger: sometimes launching circuits can fail
34206 immediately, e.g. because too many circuits have failed recently.
34207 - Fix a compile warning on 64 bit platforms.
34210 Changes in version 0.0.9pre2 - 2004-10-03
34212 - Make fetching a cached directory work for 64-bit platforms too.
34213 - Make zlib.h a required header, not an optional header.
34216 Changes in version 0.0.9pre1 - 2004-10-01
34218 - Stop using separate defaults for no-config-file and
34219 empty-config-file. Now you have to explicitly turn off SocksPort,
34220 if you don't want it open.
34221 - Fix a bug in OutboundBindAddress so it (hopefully) works.
34222 - Improve man page to mention more of the 0.0.8 features.
34223 - Fix a rare seg fault for people running hidden services on
34224 intermittent connections.
34225 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
34227 - Fix more dns related bugs: send back resolve_failed and end cells
34228 more reliably when the resolve fails, rather than closing the
34229 circuit and then trying to send the cell. Also attach dummy resolve
34230 connections to a circuit *before* calling dns_resolve(), to fix
34231 a bug where cached answers would never be sent in RESOLVED cells.
34232 - When we run out of disk space, or other log writing error, don't
34233 crash. Just stop logging to that log and continue.
34234 - We were starting to daemonize before we opened our logs, so if
34235 there were any problems opening logs, we would complain to stderr,
34236 which wouldn't work, and then mysteriously exit.
34237 - Fix a rare bug where sometimes a verified OR would connect to us
34238 before he'd uploaded his descriptor, which would cause us to
34239 assign conn->nickname as though he's unverified. Now we look through
34240 the fingerprint list to see if he's there.
34241 - Fix a rare assert trigger, where routerinfos for entries in
34242 our cpath would expire while we're building the path.
34245 - Clients can ask dirservers for /dir.z to get a compressed version
34246 of the directory. Only works for servers running 0.0.9, of course.
34247 - Make clients cache directories and use them to seed their router
34248 lists at startup. This means clients have a datadir again.
34249 - Configuration infrastructure support for warning on obsolete
34251 - Respond to content-encoding headers by trying to uncompress as
34253 - Reply with a deflated directory when a client asks for "dir.z".
34254 We could use allow-encodings instead, but allow-encodings isn't
34255 specified in HTTP 1.0.
34256 - Raise the max dns workers from 50 to 100.
34257 - Discourage people from setting their dirfetchpostperiod more often
34258 than once per minute.
34259 - Protect dirservers from overzealous descriptor uploading -- wait
34260 10 seconds after directory gets dirty, before regenerating.
34263 Changes in version 0.0.8 - 2004-08-25
34264 o Port it to SunOS 5.9 / Athena
34267 Changes in version 0.0.8rc2 - 2004-08-20
34268 o Make it compile on cygwin again.
34269 o When picking unverified routers, skip those with low uptime and/or
34270 low bandwidth, depending on what properties you care about.
34273 Changes in version 0.0.8rc1 - 2004-08-18
34274 o Changes from 0.0.7.3:
34276 - Fix assert triggers: if the other side returns an address 0.0.0.0,
34277 don't put it into the client dns cache.
34278 - If a begin failed due to exit policy, but we believe the IP address
34279 should have been allowed, switch that router to exitpolicy reject *:*
34280 until we get our next directory.
34282 - Clients choose nodes proportional to advertised bandwidth.
34283 - Avoid using nodes with low uptime as introduction points.
34284 - Handle servers with dynamic IP addresses: don't replace
34285 options->Address with the resolved one at startup, and
34286 detect our address right before we make a routerinfo each time.
34287 - 'FascistFirewall' option to pick dirservers and ORs on specific
34288 ports; plus 'FirewallPorts' config option to tell FascistFirewall
34289 which ports are open. (Defaults to 80,443)
34290 - Be more aggressive about trying to make circuits when the network
34291 has changed (e.g. when you unsuspend your laptop).
34292 - Check for time skew on http headers; report date in response to
34294 - If the entrynode config line has only one node, don't pick it as
34296 - Add strict{entry|exit}nodes config options. If set to 1, then
34297 we refuse to build circuits that don't include the specified entry
34299 - OutboundBindAddress config option, to bind to a specific
34300 IP address for outgoing connect()s.
34301 - End truncated log entries (e.g. directories) with "[truncated]".
34303 o Patches to 0.0.8preX:
34305 - Patches to compile and run on win32 again (maybe)?
34306 - Fix crash when looking for ~/.torrc with no $HOME set.
34307 - Fix a race bug in the unit tests.
34308 - Handle verified/unverified name collisions better when new
34309 routerinfo's arrive in a directory.
34310 - Sometimes routers were getting entered into the stats before
34311 we'd assigned their identity_digest. Oops.
34312 - Only pick and establish intro points after we've gotten a
34315 - AllowUnverifiedNodes config option to let circuits choose no-name
34316 routers in entry,middle,exit,introduction,rendezvous positions.
34317 Allow middle and rendezvous positions by default.
34318 - Add a man page for tor-resolve.
34321 Changes in version 0.0.7.3 - 2004-08-12
34322 o Stop dnsworkers from triggering an assert failure when you
34323 ask them to resolve the host "".
34326 Changes in version 0.0.8pre3 - 2004-08-09
34327 o Changes from 0.0.7.2:
34328 - Allow multiple ORs with same nickname in routerlist -- now when
34329 people give us one identity key for a nickname, then later
34330 another, we don't constantly complain until the first expires.
34331 - Remember used bandwidth (both in and out), and publish 15-minute
34332 snapshots for the past day into our descriptor.
34333 - You can now fetch $DIRURL/running-routers to get just the
34334 running-routers line, not the whole descriptor list. (But
34335 clients don't use this yet.)
34336 - When people mistakenly use Tor as an http proxy, point them
34337 at the tor-doc.html rather than the INSTALL.
34338 - Remove our mostly unused -- and broken -- hex_encode()
34339 function. Use base16_encode() instead. (Thanks to Timo Lindfors
34340 for pointing out this bug.)
34341 - Rotate onion keys every 12 hours, not every 2 hours, so we have
34342 fewer problems with people using the wrong key.
34343 - Change the default exit policy to reject the default edonkey,
34344 kazaa, gnutella ports.
34345 - Add replace_file() to util.[ch] to handle win32's rename().
34347 o Changes from 0.0.8preX:
34348 - Fix two bugs in saving onion keys to disk when rotating, so
34349 hopefully we'll get fewer people using old onion keys.
34350 - Fix an assert error that was making SocksPolicy not work.
34351 - Be willing to expire routers that have an open dirport -- it's
34352 just the authoritative dirservers we want to not forget.
34353 - Reject tor-resolve requests for .onion addresses early, so we
34354 don't build a whole rendezvous circuit and then fail.
34355 - When you're warning a server that he's unverified, don't cry
34356 wolf unpredictably.
34357 - Fix a race condition: don't try to extend onto a connection
34358 that's still handshaking.
34359 - For servers in clique mode, require the conn to be open before
34360 you'll choose it for your path.
34361 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
34362 end relay cell, etc.
34363 - Measure bandwidth capacity over the last 24 hours, not just 12
34364 - Bugfix: authoritative dirservers were making and signing a new
34365 directory for each client, rather than reusing the cached one.
34368 Changes in version 0.0.8pre2 - 2004-08-04
34369 o Changes from 0.0.7.2:
34371 - Check directory signature _before_ you decide whether you're
34372 you're running an obsolete version and should exit.
34373 - Check directory signature _before_ you parse the running-routers
34374 list to decide who's running or verified.
34375 - Bugfixes and features:
34376 - Check return value of fclose while writing to disk, so we don't
34377 end up with broken files when servers run out of disk space.
34378 - Log a warning if the user uses an unsafe socks variant, so people
34379 are more likely to learn about privoxy or socat.
34380 - Dirservers now include RFC1123-style dates in the HTTP headers,
34381 which one day we will use to better detect clock skew.
34383 o Changes from 0.0.8pre1:
34384 - Make it compile without warnings again on win32.
34385 - Log a warning if you're running an unverified server, to let you
34386 know you might want to get it verified.
34387 - Only pick a default nickname if you plan to be a server.
34390 Changes in version 0.0.8pre1 - 2004-07-23
34392 - Made our unit tests compile again on OpenBSD 3.5, and tor
34393 itself compile again on OpenBSD on a sparc64.
34394 - We were neglecting milliseconds when logging on win32, so
34395 everything appeared to happen at the beginning of each second.
34397 o Protocol changes:
34398 - 'Extend' relay cell payloads now include the digest of the
34399 intended next hop's identity key. Now we can verify that we're
34400 extending to the right router, and also extend to routers we
34401 hadn't heard of before.
34404 - Tor nodes can now act as relays (with an advertised ORPort)
34405 without being manually verified by the dirserver operators.
34406 - Uploaded descriptors of unverified routers are now accepted
34407 by the dirservers, and included in the directory.
34408 - Verified routers are listed by nickname in the running-routers
34409 list; unverified routers are listed as "$<fingerprint>".
34410 - We now use hash-of-identity-key in most places rather than
34411 nickname or addr:port, for improved security/flexibility.
34412 - To avoid Sybil attacks, paths still use only verified servers.
34413 But now we have a chance to play around with hybrid approaches.
34414 - Nodes track bandwidth usage to estimate capacity (not used yet).
34415 - ClientOnly option for nodes that never want to become servers.
34416 - Directory caching.
34417 - "AuthoritativeDir 1" option for the official dirservers.
34418 - Now other nodes (clients and servers) will cache the latest
34419 directory they've pulled down.
34420 - They can enable their DirPort to serve it to others.
34421 - Clients will pull down a directory from any node with an open
34422 DirPort, and check the signature/timestamp correctly.
34423 - Authoritative dirservers now fetch directories from other
34424 authdirservers, to stay better synced.
34425 - Running-routers list tells who's down also, along with noting
34426 if they're verified (listed by nickname) or unverified (listed
34428 - Allow dirservers to serve running-router list separately.
34429 This isn't used yet.
34430 - ORs connect-on-demand to other ORs
34431 - If you get an extend cell to an OR you're not connected to,
34432 connect, handshake, and forward the create cell.
34433 - The authoritative dirservers stay connected to everybody,
34434 and everybody stays connected to 0.0.7 servers, but otherwise
34435 clients/servers expire unused connections after 5 minutes.
34436 - When servers get a sigint, they delay 30 seconds (refusing new
34437 connections) then exit. A second sigint causes immediate exit.
34438 - File and name management:
34439 - Look for .torrc if no CONFDIR "torrc" is found.
34440 - If no datadir is defined, then choose, make, and secure ~/.tor
34442 - If torrc not found, exitpolicy reject *:*.
34443 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
34444 - If no nickname is defined, derive default from hostname.
34445 - Rename secret key files, e.g. identity.key -> secret_id_key,
34446 to discourage people from mailing their identity key to tor-ops.
34447 - Refuse to build a circuit before the directory has arrived --
34448 it won't work anyway, since you won't know the right onion keys
34450 - Try other dirservers immediately if the one you try is down. This
34451 should tolerate down dirservers better now.
34452 - Parse tor version numbers so we can do an is-newer-than check
34453 rather than an is-in-the-list check.
34454 - New socks command 'resolve', to let us shim gethostbyname()
34456 - A 'tor_resolve' script to access the socks resolve functionality.
34457 - A new socks-extensions.txt doc file to describe our
34458 interpretation and extensions to the socks protocols.
34459 - Add a ContactInfo option, which gets published in descriptor.
34460 - Publish OR uptime in descriptor (and thus in directory) too.
34461 - Write tor version at the top of each log file
34462 - New docs in the tarball:
34464 - Document that you should proxy your SSL traffic too.
34467 Changes in version 0.0.7.2 - 2004-07-07
34468 o A better fix for the 0.0.0.0 problem, that will hopefully
34469 eliminate the remaining related assertion failures.
34472 Changes in version 0.0.7.1 - 2004-07-04
34473 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
34474 since internally we use 0.0.0.0 to signify "not yet resolved".
34477 Changes in version 0.0.7 - 2004-06-07
34478 o Updated the man page to reflect the new features.
34481 Changes in version 0.0.7rc2 - 2004-06-06
34482 o Changes from 0.0.7rc1:
34483 - Make it build on Win32 again.
34484 o Changes from 0.0.6.2:
34485 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
34489 Changes in version 0.0.7rc1 - 2004-06-02
34491 - On sighup, we were adding another log without removing the first
34492 one. So log messages would get duplicated n times for n sighups.
34493 - Several cases of using a connection after we'd freed it. The
34494 problem was that connections that are pending resolve are in both
34495 the pending_resolve tree, and also the circuit's resolving_streams
34496 list. When you want to remove one, you must remove it from both.
34497 - Fix a double-mark-for-close where an end cell arrived for a
34498 resolving stream, and then the resolve failed.
34499 - Check directory signatures based on name of signer, not on whom
34500 we got the directory from. This will let us cache directories more
34503 - Crank up some of our constants to handle more users.
34506 Changes in version 0.0.7pre1 - 2004-06-02
34507 o Fixes for crashes and other obnoxious bugs:
34508 - Fix an epipe bug: sometimes when directory connections failed
34509 to connect, we would give them a chance to flush before closing
34511 - When we detached from a circuit because of resolvefailed, we
34512 would immediately try the same circuit twice more, and then
34513 give up on the resolve thinking we'd tried three different
34515 - Limit the number of intro circuits we'll attempt to build for a
34516 hidden service per 15-minute period.
34517 - Check recommended-software string *early*, before actually parsing
34518 the directory. Thus we can detect an obsolete version and exit,
34519 even if the new directory format doesn't parse.
34520 o Fixes for security bugs:
34521 - Remember which nodes are dirservers when you startup, and if a
34522 random OR enables his dirport, don't automatically assume he's
34523 a trusted dirserver.
34525 - Directory connections were asking the wrong poll socket to
34526 start writing, and not asking themselves to start writing.
34527 - When we detached from a circuit because we sent a begin but
34528 didn't get a connected, we would use it again the first time;
34529 but after that we would correctly switch to a different one.
34530 - Stop warning when the first onion decrypt attempt fails; they
34531 will sometimes legitimately fail now that we rotate keys.
34532 - Override unaligned-access-ok check when $host_cpu is ia64 or
34533 arm. Apparently they allow it but the kernel whines.
34534 - Dirservers try to reconnect periodically too, in case connections
34536 - Fix some memory leaks in directory servers.
34537 - Allow backslash in Win32 filenames.
34538 - Made Tor build complain-free on FreeBSD, hopefully without
34539 breaking other BSD builds. We'll see.
34541 - Doxygen markup on all functions and global variables.
34542 - Make directory functions update routerlist, not replace it. So
34543 now directory disagreements are not so critical a problem.
34544 - Remove the upper limit on number of descriptors in a dirserver's
34545 directory (not that we were anywhere close).
34546 - Allow multiple logfiles at different severity ranges.
34547 - Allow *BindAddress to specify ":port" rather than setting *Port
34548 separately. Allow multiple instances of each BindAddress config
34549 option, so you can bind to multiple interfaces if you want.
34550 - Allow multiple exit policy lines, which are processed in order.
34551 Now we don't need that huge line with all the commas in it.
34552 - Enable accept/reject policies on SOCKS connections, so you can bind
34553 to 0.0.0.0 but still control who can use your OP.
34556 Changes in version 0.0.6.2 - 2004-05-16
34557 o Our integrity-checking digest was checking only the most recent cell,
34558 not the previous cells like we'd thought.
34559 Thanks to Stefan Mark for finding the flaw!
34562 Changes in version 0.0.6.1 - 2004-05-06
34563 o Fix two bugs in our AES counter-mode implementation (this affected
34564 onion-level stream encryption, but not TLS-level). It turns
34565 out we were doing something much more akin to a 16-character
34566 polyalphabetic cipher. Oops.
34567 Thanks to Stefan Mark for finding the flaw!
34568 o Retire moria3 as a directory server, and add tor26 as a directory
34572 Changes in version 0.0.6 - 2004-05-02
34573 [version bump only]
34576 Changes in version 0.0.6rc4 - 2004-05-01
34577 o Update the built-in dirservers list to use the new directory format
34578 o Fix a rare seg fault: if a node offering a hidden service attempts
34579 to build a circuit to Alice's rendezvous point and fails before it
34580 reaches the last hop, it retries with a different circuit, but
34582 o Handle windows socket errors correctly.
34585 Changes in version 0.0.6rc3 - 2004-04-28
34586 o Don't expire non-general excess circuits (if we had enough
34587 circuits open, we were expiring rendezvous circuits -- even
34588 when they had a stream attached. oops.)
34589 o Fetch randomness from /dev/urandom better (not via fopen/fread)
34590 o Better debugging for tls errors
34591 o Some versions of openssl have an SSL_pending function that erroneously
34592 returns bytes when there is a non-application record pending.
34593 o Set Content-Type on the directory and hidserv descriptor.
34594 o Remove IVs from cipher code, since AES-ctr has none.
34595 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
34596 o We were using an array of length zero in a few places.
34597 o win32's gethostbyname can't resolve an IP to an IP.
34598 o win32's close can't close a socket.
34601 Changes in version 0.0.6rc2 - 2004-04-26
34602 o Fix a bug where we were closing tls connections intermittently.
34603 It turns out openssl keeps its errors around -- so if an error
34604 happens, and you don't ask about it, and then another openssl
34605 operation happens and succeeds, and you ask if there was an error,
34606 it tells you about the first error. Fun fun.
34607 o Fix a bug that's been lurking since 27 may 03 (!)
34608 When passing back a destroy cell, we would use the wrong circ id.
34609 'Mostly harmless', but still worth fixing.
34610 o Since we don't support truncateds much, don't bother sending them;
34611 just close the circ.
34612 o check for <machine/limits.h> so we build on NetBSD again (I hope).
34613 o don't crash if a conn that sent a begin has suddenly lost its circuit
34614 (this was quite rare).
34617 Changes in version 0.0.6rc1 - 2004-04-25
34618 o We now rotate link (tls context) keys and onion keys.
34619 o CREATE cells now include oaep padding, so you can tell
34620 if you decrypted them correctly.
34621 o Add bandwidthburst to server descriptor.
34622 o Directories now say which dirserver signed them.
34623 o Use a tor_assert macro that logs failed assertions too.
34626 Changes in version 0.0.6pre5 - 2004-04-18
34627 o changes from 0.0.6pre4:
34628 - make tor build on broken freebsd 5.2 installs
34629 - fix a failed assert when you try an intro point, get a nack, and try
34630 a second one and it works.
34631 - when alice uses a port that the hidden service doesn't accept,
34632 it now sends back an end cell (denied by exit policy). otherwise
34633 alice would just have to wait to time out.
34634 - fix another rare bug: when we had tried all the intro
34635 points for a hidden service, we fetched the descriptor
34636 again, but we left our introcirc thinking it had already
34637 sent an intro, so it kept waiting for a response...
34638 - bugfix: when you sleep your hidden-service laptop, as soon
34639 as it wakes up it tries to upload a service descriptor, but
34640 socketpair fails for some reason (localhost not up yet?).
34641 now we simply give up on that upload, and we'll try again later.
34642 i'd still like to find the bug though.
34643 - if an intro circ waiting for an ack dies before getting one, then
34645 - we were reusing stale service descriptors and refetching usable
34649 Changes in version 0.0.6pre4 - 2004-04-14
34650 o changes from 0.0.6pre3:
34651 - when bob fails to connect to the rendezvous point, and his
34652 circ didn't fail because of the rendezvous point itself, then
34653 he retries a couple of times
34654 - we expire introduction and rendezvous circs more thoroughly
34655 (sometimes they were hanging around forever)
34656 - we expire unattached rendezvous streams that have been around
34657 too long (they were sticking around forever).
34658 - fix a measly fencepost error that was crashing everybody with
34662 Changes in version 0.0.6pre3 - 2004-04-14
34663 o changes from 0.0.6pre2:
34664 - make hup work again
34665 - fix some memory leaks for dirservers
34666 - allow more skew in rendezvous descriptor timestamps, to help
34667 handle people like blanu who don't know what time it is
34668 - normal circs are 3 hops, but some rend/intro circs are 4, if
34669 the initiator doesn't get to choose the last hop
34670 - send acks for introductions, so alice can know whether to try
34672 - bob publishes intro points more correctly
34673 o changes from 0.0.5:
34674 - fix an assert trigger that's been plaguing us since the days
34675 of 0.0.2prexx (thanks weasel!)
34676 - retry stream correctly when we fail to connect because of
34677 exit-policy-reject (should try another) or can't-resolve-address
34678 (also should try another, because dns on random internet servers
34680 - when we hup a dirserver and we've *removed* a server from the
34681 approved-routers list, now we remove that server from the
34682 in-memory directories too
34685 Changes in version 0.0.6pre2 - 2004-04-08
34686 o We fixed our base32 implementation. Now it works on all architectures.
34689 Changes in version 0.0.6pre1 - 2004-04-08
34691 - Hidden services and rendezvous points are implemented. Go to
34692 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
34693 hidden services. (This only works via a socks4a proxy such as
34694 Privoxy, and currently it's quite slow.)
34697 Changes in version 0.0.5 - 2004-03-30
34698 [version bump only]
34701 Changes in version 0.0.5rc3 - 2004-03-29
34702 o Install torrc as torrc.sample -- we no longer clobber your
34704 o Re-enable recommendedversion checking (we broke it in rc2, oops)
34705 o Add in a 'notice' log level for things the operator should hear
34706 but that aren't warnings
34709 Changes in version 0.0.5rc2 - 2004-03-29
34710 o Hold socks connection open until reply is flushed (if possible)
34711 o Make exit nodes resolve IPs to IPs immediately, rather than asking
34712 the dns farm to do it.
34713 o Fix c99 aliasing warnings in rephist.c
34714 o Don't include server descriptors that are older than 24 hours in the
34716 o Give socks 'reject' replies their whole 15s to attempt to flush,
34717 rather than seeing the 60s timeout and assuming the flush had failed.
34718 o Clean automake droppings from the cvs repository
34721 Changes in version 0.0.5rc1 - 2004-03-28
34722 o Fix mangled-state bug in directory fetching (was causing sigpipes).
34723 o Only build circuits after we've fetched the directory: clients were
34724 using only the directory servers before they'd fetched a directory.
34725 This also means longer startup time; so it goes.
34726 o Fix an assert trigger where an OP would fail to handshake, and we'd
34727 expect it to have a nickname.
34728 o Work around a tsocks bug: do a socks reject when AP connection dies
34729 early, else tsocks goes into an infinite loop.
34732 Changes in version 0.0.4 - 2004-03-26
34733 o When connecting to a dirserver or OR and the network is down,
34737 Changes in version 0.0.3 - 2004-03-26
34738 o Warn and fail if server chose a nickname with illegal characters
34739 o Port to Solaris and Sparc:
34740 - include missing header fcntl.h
34741 - have autoconf find -lsocket -lnsl automatically
34742 - deal with hardware word alignment
34743 - make uname() work (solaris has a different return convention)
34744 - switch from using signal() to sigaction()
34745 o Preliminary work on reputation system:
34746 - Keep statistics on success/fail of connect attempts; they're published
34747 by kill -USR1 currently.
34748 - Add a RunTesting option to try to learn link state by creating test
34749 circuits, even when SocksPort is off.
34750 - Remove unused open circuits when there are too many.
34753 Changes in version 0.0.2 - 2004-03-19
34754 - Include strlcpy and strlcat for safer string ops
34755 - define INADDR_NONE so we compile (but still not run) on solaris
34758 Changes in version 0.0.2pre27 - 2004-03-14
34760 - Allow internal tor networks (we were rejecting internal IPs,
34761 now we allow them if they're set explicitly).
34762 - And fix a few endian issues.
34765 Changes in version 0.0.2pre26 - 2004-03-14
34767 - If a stream times out after 15s without a connected cell, don't
34768 try that circuit again: try a new one.
34769 - Retry streams at most 4 times. Then give up.
34770 - When a dirserver gets a descriptor from an unknown router, it
34771 logs its fingerprint (so the dirserver operator can choose to
34772 accept it even without mail from the server operator).
34773 - Inform unapproved servers when we reject their descriptors.
34774 - Make tor build on Windows again. It works as a client, who knows
34776 - Clearer instructions in the torrc for how to set up a server.
34777 - Be more efficient about reading fd's when our global token bucket
34778 (used for rate limiting) becomes empty.
34780 - Stop asserting that computers always go forward in time. It's
34782 - When we sent a cell (e.g. destroy) and then marked an OR connection
34783 expired, we might close it before finishing a flush if the other
34784 side isn't reading right then.
34785 - Don't allow dirservers to start if they haven't defined
34786 RecommendedVersions
34787 - We were caching transient dns failures. Oops.
34788 - Prevent servers from publishing an internal IP as their address.
34789 - Address a strcat vulnerability in circuit.c
34792 Changes in version 0.0.2pre25 - 2004-03-04
34794 - Put the OR's IP in its router descriptor, not its fqdn. That way
34795 we'll stop being stalled by gethostbyname for nodes with flaky dns,
34798 - If the user typed in an address that didn't resolve, the server
34802 Changes in version 0.0.2pre24 - 2004-03-03
34804 - Fix an assertion failure in dns.c, where we were trying to dequeue
34805 a pending dns resolve even if it wasn't pending
34806 - Fix a spurious socks5 warning about still trying to write after the
34807 connection is finished.
34808 - Hold certain marked_for_close connections open until they're finished
34809 flushing, rather than losing bytes by closing them too early.
34810 - Correctly report the reason for ending a stream
34811 - Remove some duplicate calls to connection_mark_for_close
34812 - Put switch_id and start_daemon earlier in the boot sequence, so it
34813 will actually try to chdir() to options.DataDirectory
34814 - Make 'make test' exit(1) if a test fails; fix some unit tests
34815 - Make tor fail when you use a config option it doesn't know about,
34816 rather than warn and continue.
34817 - Make --version work
34818 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
34821 Changes in version 0.0.2pre23 - 2004-02-29
34823 - Print a statement when the first circ is finished, so the user
34824 knows it's working.
34825 - If a relay cell is unrecognized at the end of the circuit,
34826 send back a destroy. (So attacks to mutate cells are more
34828 - New config option 'excludenodes' to avoid certain nodes for circuits.
34829 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
34830 so you can collect coredumps there.
34832 - Fix a bug in tls flushing where sometimes data got wedged and
34833 didn't flush until more data got sent. Hopefully this bug was
34834 a big factor in the random delays we were seeing.
34835 - Make 'connected' cells include the resolved IP, so the client
34836 dns cache actually gets populated.
34837 - Disallow changing from ORPort=0 to ORPort>0 on hup.
34838 - When we time-out on a stream and detach from the circuit, send an
34839 end cell down it first.
34840 - Only warn about an unknown router (in exitnodes, entrynodes,
34841 excludenodes) after we've fetched a directory.
34844 Changes in version 0.0.2pre22 - 2004-02-26
34846 - Servers publish less revealing uname information in descriptors.
34847 - More memory tracking and assertions, to crash more usefully when
34849 - If the default torrc isn't there, just use some default defaults.
34850 Plus provide an internal dirservers file if they don't have one.
34851 - When the user tries to use Tor as an http proxy, give them an http
34852 501 failure explaining that we're a socks proxy.
34853 - Dump a new router.desc on hup, to help confused people who change
34854 their exit policies and then wonder why router.desc doesn't reflect
34856 - Clean up the generic tor.sh init script that we ship with.
34858 - If the exit stream is pending on the resolve, and a destroy arrives,
34859 then the stream wasn't getting removed from the pending list. I
34860 think this was the one causing recent server crashes.
34861 - Use a more robust poll on OSX 10.3, since their poll is flaky.
34862 - When it couldn't resolve any dirservers, it was useless from then on.
34863 Now it reloads the RouterFile (or default dirservers) if it has no
34865 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
34866 many users don't even *have* a /usr/local/sbin/.
34869 Changes in version 0.0.2pre21 - 2004-02-18
34871 - There's a ChangeLog file that actually reflects the changelog.
34872 - There's a 'torify' wrapper script, with an accompanying
34873 tor-tsocks.conf, that simplifies the process of using tsocks for
34874 tor. It even has a man page.
34875 - The tor binary gets installed to sbin rather than bin now.
34876 - Retry streams where the connected cell hasn't arrived in 15 seconds
34877 - Clean up exit policy handling -- get the default out of the torrc,
34878 so we can update it without forcing each server operator to fix
34880 - Allow imaps and pop3s in default exit policy
34882 - Prevent picking middleman nodes as the last node in the circuit
34885 Changes in version 0.0.2pre20 - 2004-01-30
34887 - We now have a deb package, and it's in debian unstable. Go to
34888 it, apt-getters. :)
34889 - I've split the TotalBandwidth option into BandwidthRate (how many
34890 bytes per second you want to allow, long-term) and
34891 BandwidthBurst (how many bytes you will allow at once before the cap
34892 kicks in). This better token bucket approach lets you, say, set
34893 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
34894 performance while not exceeding your monthly bandwidth quota.
34895 - Push out a tls record's worth of data once you've got it, rather
34896 than waiting until you've read everything waiting to be read. This
34897 may improve performance by pipelining better. We'll see.
34898 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
34899 from failed circuits (if they haven't been connected yet) and attach
34901 - Expire old streams that haven't managed to connect. Some day we'll
34902 have them reattach to new circuits instead.
34905 - Fix several memory leaks that were causing servers to become bloated
34907 - Fix a few very rare assert triggers. A few more remain.
34908 - Setuid to User _before_ complaining about running as root.
34911 Changes in version 0.0.2pre19 - 2004-01-07
34913 - Fix deadlock condition in dns farm. We were telling a child to die by
34914 closing the parent's file descriptor to him. But newer children were
34915 inheriting the open file descriptor from the parent, and since they
34916 weren't closing it, the socket never closed, so the child never read
34917 eof, so he never knew to exit. Similarly, dns workers were holding
34918 open other sockets, leading to all sorts of chaos.
34919 - New cleaner daemon() code for forking and backgrounding.
34920 - If you log to a file, it now prints an entry at the top of the
34921 logfile so you know it's working.
34922 - The onionskin challenge length was 30 bytes longer than necessary.
34923 - Started to patch up the spec so it's not quite so out of date.
34926 Changes in version 0.0.2pre18 - 2004-01-02
34928 - Fix endian issues with the 'integrity' field in the relay header.
34929 - Fix a potential bug where connections in state
34930 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
34933 Changes in version 0.0.2pre17 - 2003-12-30
34935 - Made --debuglogfile (or any second log file, actually) work.
34936 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
34937 adversary could force us into an infinite loop.
34940 - Each onionskin handshake now includes a hash of the computed key,
34941 to prove the server's identity and help perfect forward secrecy.
34942 - Changed cell size from 256 to 512 bytes (working toward compatibility
34944 - Changed cell length to 2 bytes, and moved it to the relay header.
34945 - Implemented end-to-end integrity checking for the payloads of
34947 - Separated streamid from 'recognized' (otherwise circuits will get
34948 messed up when we try to have streams exit from the middle). We
34949 use the integrity-checking to confirm that a cell is addressed to
34951 - Randomize the initial circid and streamid values, so an adversary who
34952 breaks into a node can't learn how many circuits or streams have
34956 Changes in version 0.0.2pre16 - 2003-12-14
34958 - Fixed a bug that made HUP trigger an assert
34959 - Fixed a bug where a circuit that immediately failed wasn't being
34960 counted as a failed circuit in counting retries.
34963 - Now we close the circuit when we get a truncated cell: otherwise we're
34964 open to an anonymity attack where a bad node in the path truncates
34965 the circuit and then we open streams at him.
34966 - Add port ranges to exit policies
34967 - Add a conservative default exit policy
34968 - Warn if you're running tor as root
34969 - on HUP, retry OR connections and close/rebind listeners
34970 - options.EntryNodes: try these nodes first when picking the first node
34971 - options.ExitNodes: if your best choices happen to include any of
34972 your preferred exit nodes, you choose among just those preferred
34974 - options.ExcludedNodes: nodes that are never picked in path building
34977 Changes in version 0.0.2pre15 - 2003-12-03
34978 o Robustness and bugfixes:
34979 - Sometimes clients would cache incorrect DNS resolves, which would
34980 really screw things up.
34981 - An OP that goes offline would slowly leak all its sockets and stop
34983 - A wide variety of bugfixes in exit node selection, exit policy
34984 handling, and processing pending streams when a new circuit is
34986 - Pick nodes for a path only from those the directory says are up
34987 - Choose randomly from all running dirservers, not always the first one
34988 - Increase allowed http header size for directory fetch.
34989 - Stop writing to stderr (if we're daemonized it will be closed).
34990 - Enable -g always, so cores will be more useful to me.
34991 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
34994 - Wrote a man page. It lists commonly used options.
34997 - Change default loglevel to warn.
34998 - Make PidFile default to null rather than littering in your CWD.
34999 - OnionRouter config option is now obsolete. Instead it just checks
35001 - Moved to a single unified torrc file for both clients and servers.
35004 Changes in version 0.0.2pre14 - 2003-11-29
35005 o Robustness and bugfixes:
35006 - Force the admin to make the DataDirectory himself
35007 - to get ownership/permissions right
35008 - so clients no longer make a DataDirectory and then never use it
35009 - fix bug where a client who was offline for 45 minutes would never
35010 pull down a directory again
35011 - fix (or at least hide really well) the dns assert bug that was
35012 causing server crashes
35013 - warnings and improved robustness wrt clockskew for certs
35014 - use the native daemon(3) to daemonize, when available
35015 - exit if bind() fails
35016 - exit if neither socksport nor orport is defined
35017 - include our own tor_timegm (Win32 doesn't have its own)
35018 - bugfix for win32 with lots of connections
35019 - fix minor bias in PRNG
35020 - make dirserver more robust to corrupt cached directory
35023 - Wrote the design document (woo)
35025 o Circuit building and exit policies:
35026 - Circuits no longer try to use nodes that the directory has told them
35028 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
35029 bitcounts (18.0.0.0/8).
35030 - Make AP connections standby for a circuit if no suitable circuit
35031 exists, rather than failing
35032 - Circuits choose exit node based on addr/port, exit policies, and
35033 which AP connections are standing by
35034 - Bump min pathlen from 2 to 3
35035 - Relay end cells have a payload to describe why the stream ended.
35036 - If the stream failed because of exit policy, try again with a new
35038 - Clients have a dns cache to remember resolved addresses.
35039 - Notice more quickly when we have no working circuits
35042 - APPort is now called SocksPort
35043 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
35045 - RecommendedVersions is now a config variable rather than
35046 hardcoded (for dirservers)
35047 - Reloads config on HUP
35048 - Usage info on -h or --help
35049 - If you set User and Group config vars, it'll setu/gid to them.
35052 Changes in version 0.0.2pre13 - 2003-10-19
35053 o General stability:
35054 - SSL_write no longer fails when it returns WANTWRITE and the number
35055 of bytes in the buf has changed by the next SSL_write call.
35056 - Fix segfault fetching directory when network is down
35057 - Fix a variety of minor memory leaks
35058 - Dirservers reload the fingerprints file on HUP, so I don't have
35059 to take down the network when I approve a new router
35060 - Default server config file has explicit Address line to specify fqdn
35063 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
35064 - Make listener connections not ever alloc bufs
35066 o Autoconf improvements:
35067 - don't clobber an external CFLAGS in ./configure
35068 - Make install now works
35069 - create var/lib/tor on make install
35070 - autocreate a tor.sh initscript to help distribs
35071 - autocreate the torrc and sample-server-torrc with correct paths
35073 o Log files and Daemonizing now work:
35074 - If --DebugLogFile is specified, log to it at -l debug
35075 - If --LogFile is specified, use it instead of commandline
35076 - If --RunAsDaemon is set, tor forks and backgrounds on startup