1 Changes in version 0.2.7.2-alpha - 2015-07-27
2 This, the second alpha in the Tor 0.2.7 series, has a number of new
3 features, including a way to manually pick the number of introduction
4 points for hidden services, and the much stronger Ed25519 signing key
5 algorithm for regular Tor relays (including support for encrypted
6 offline identity keys in the new algorithm).
8 Support for Ed25519 on relays is currently limited to signing router
9 descriptors; later alphas in this series will extend Ed25519 key
10 support to more parts of the Tor protocol.
12 o Major features (Ed25519 identity keys, Proposal 220):
13 - All relays now maintain a stronger identity key, using the Ed25519
14 elliptic curve signature format. This master key is designed so
15 that it can be kept offline. Relays also generate an online
16 signing key, and a set of other Ed25519 keys and certificates.
17 These are all automatically regenerated and rotated as needed.
18 Implements part of ticket 12498.
19 - Directory authorities now vote on Ed25519 identity keys along with
20 RSA1024 keys. Implements part of ticket 12498.
21 - Directory authorities track which Ed25519 identity keys have been
22 used with which RSA1024 identity keys, and do not allow them to
23 vary freely. Implements part of ticket 12498.
24 - Microdescriptors now include Ed25519 identity keys. Implements
26 - Add support for offline encrypted Ed25519 master keys. To use this
27 feature on your tor relay, run "tor --keygen" to make a new master
28 key (or to make a new signing key if you already have a master
29 key). Closes ticket 13642.
31 o Major features (Hidden services):
32 - Add the torrc option HiddenServiceNumIntroductionPoints, to
33 specify a fixed number of introduction points. Its maximum value
34 is 10 and default is 3. Using this option can increase a hidden
35 service's reliability under load, at the cost of making it more
36 visible that the hidden service is facing extra load. Closes
38 - Remove the adaptive algorithm for choosing the number of
39 introduction points, which used to change the number of
40 introduction points (poorly) depending on the number of
41 connections the HS sees. Closes ticket 4862.
43 o Major features (onion key cross-certification):
44 - Relay descriptors now include signatures of their own identity
45 keys, made using the TAP and ntor onion keys. These signatures
46 allow relays to prove ownership of their own onion keys. Because
47 of this change, microdescriptors will no longer need to include
48 RSA identity keys. Implements proposal 228; closes ticket 12499.
50 o Major features (performance):
51 - Improve the runtime speed of Ed25519 operations by using the
52 public-domain Ed25519-donna by Andrew M. ("floodyberry").
53 Implements ticket 16467.
54 - Improve the runtime speed of the ntor handshake by using an
55 optimized curve25519 basepoint scalarmult implementation from the
56 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
57 ideas by Adam Langley. Implements ticket 9663.
59 o Major bugfixes (client-side privacy, also in 0.2.6.9):
60 - Properly separate out each SOCKSPort when applying stream
61 isolation. The error occurred because each port's session group
62 was being overwritten by a default value when the listener
63 connection was initialized. Fixes bug 16247; bugfix on
64 0.2.6.3-alpha. Patch by "jojelino".
66 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
67 - Stop refusing to store updated hidden service descriptors on a
68 client. This reverts commit 9407040c59218 (which indeed fixed bug
69 14219, but introduced a major hidden service reachability
70 regression detailed in bug 16381). This is a temporary fix since
71 we can live with the minor issue in bug 14219 (it just results in
72 some load on the network) but the regression of 16381 is too much
73 of a setback. First-round fix for bug 16381; bugfix
76 o Major bugfixes (hidden services):
77 - When cannibalizing a circuit for an introduction point, always
78 extend to the chosen exit node (creating a 4 hop circuit).
79 Previously Tor would use the current circuit exit node, which
80 changed the original choice of introduction point, and could cause
81 the hidden service to skip excluded introduction points or
82 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
85 o Major bugfixes (open file limit):
86 - The open file limit wasn't checked before calling
87 tor_accept_socket_nonblocking(), which would make Tor exceed the
88 limit. Now, before opening a new socket, Tor validates the open
89 file limit just before, and if the max has been reached, return an
90 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
92 o Major bugfixes (stability, also in 0.2.6.10):
93 - Stop crashing with an assertion failure when parsing certain kinds
94 of malformed or truncated microdescriptors. Fixes bug 16400;
95 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
96 by "cypherpunks_backup".
97 - Stop random client-side assertion failures that could occur when
98 connecting to a busy hidden service, or connecting to a hidden
99 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
102 o Minor features (directory authorities, security, also in 0.2.6.9):
103 - The HSDir flag given by authorities now requires the Stable flag.
104 For the current network, this results in going from 2887 to 2806
105 HSDirs. Also, it makes it harder for an attacker to launch a sybil
106 attack by raising the effort for a relay to become Stable to
107 require at the very least 7 days, while maintaining the 96 hours
108 uptime requirement for HSDir. Implements ticket 8243.
110 o Minor features (client):
111 - Relax the validation of hostnames in SOCKS5 requests, allowing the
112 character '_' to appear, in order to cope with domains observed in
113 the wild that are serving non-RFC compliant records. Resolves
115 - Relax the validation done to hostnames in SOCKS5 requests, and
116 allow a single trailing '.' to cope with clients that pass FQDNs
117 using that syntax to explicitly indicate that the domain name is
118 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
119 - Add GroupWritable and WorldWritable options to unix-socket based
120 SocksPort and ControlPort options. These options apply to a single
121 socket, and override {Control,Socks}SocketsGroupWritable. Closes
124 o Minor features (control protocol):
125 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
126 the control protocol. Resolves ticket 15358.
128 o Minor features (directory authorities):
129 - Directory authorities no longer vote against the "Fast", "Stable",
130 and "HSDir" flags just because they were going to vote against
131 "Running": if the consensus turns out to be that the router was
132 running, then the authority's vote should count. Patch from Peter
133 Retzlaff; closes issue 8712.
135 o Minor features (geoip, also in 0.2.6.10):
136 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
137 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
139 o Minor features (hidden services):
140 - Add the new options "HiddenServiceMaxStreams" and
141 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
142 limit the maximum number of simultaneous streams per circuit, and
143 optionally tear down the circuit when the limit is exceeded. Part
146 o Minor features (portability):
147 - Use C99 variadic macros when the compiler is not GCC. This avoids
148 failing compilations on MSVC, and fixes a log-file-based race
149 condition in our old workarounds. Original patch from Gisle Vanem.
151 o Minor bugfixes (compilation, also in 0.2.6.9):
152 - Build with --enable-systemd correctly when libsystemd is
153 installed, but systemd is not. Fixes bug 16164; bugfix on
154 0.2.6.3-alpha. Patch from Peter Palfrader.
156 o Minor bugfixes (controller):
157 - Add the descriptor ID in each HS_DESC control event. It was
158 missing, but specified in control-spec.txt. Fixes bug 15881;
159 bugfix on 0.2.5.2-alpha.
161 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
162 - Check for failures from crypto_early_init, and refuse to continue.
163 A previous typo meant that we could keep going with an
164 uninitialized crypto library, and would have OpenSSL initialize
165 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
166 when implementing ticket 4900. Patch by "teor".
168 o Minor bugfixes (hidden services):
169 - Fix a crash when reloading configuration while at least one
170 configured and one ephemeral hidden service exists. Fixes bug
171 16060; bugfix on 0.2.7.1-alpha.
172 - Avoid crashing with a double-free bug when we create an ephemeral
173 hidden service but adding it fails for some reason. Fixes bug
174 16228; bugfix on 0.2.7.1-alpha.
176 o Minor bugfixes (Linux seccomp2 sandbox):
177 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
178 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
180 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
181 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
182 these when eventfd2() support is missing. Fixes bug 16363; bugfix
183 on 0.2.6.3-alpha. Patch from "teor".
185 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
186 - Fix sandboxing to work when running as a relay, by allowing the
187 renaming of secret_id_key, and allowing the eventfd2 and futex
188 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
190 - Allow systemd connections to work with the Linux seccomp2 sandbox
191 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
194 o Minor bugfixes (relay):
195 - Fix a rarely-encountered memory leak when failing to initialize
196 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
199 o Minor bugfixes (systemd):
200 - Fix an accidental formatting error that broke the systemd
201 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
202 - Tor's systemd unit file no longer contains extraneous spaces.
203 These spaces would sometimes confuse tools like deb-systemd-
204 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
206 o Minor bugfixes (tests):
207 - Use the configured Python executable when running test-stem-full.
208 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
210 o Minor bugfixes (tests, also in 0.2.6.9):
211 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
212 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
214 o Minor bugfixes (threads, comments):
215 - Always initialize return value in compute_desc_id in rendcommon.c
216 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
217 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
218 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
219 - Remove undefined directive-in-macro in test_util_writepid clang
220 3.7 complains that using a preprocessor directive inside a macro
221 invocation in test_util_writepid in test_util.c is undefined.
222 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
224 o Code simplification and refactoring:
225 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
226 to ensure they remain consistent and visible everywhere.
227 - Remove some vestigial workarounds for the MSVC6 compiler. We
228 haven't supported that in ages.
229 - The link authentication code has been refactored for better
230 testability and reliability. It now uses code generated with the
231 "trunnel" binary encoding generator, to reduce the risk of bugs
232 due to programmer error. Done as part of ticket 12498.
235 - Include a specific and (hopefully) accurate documentation of the
236 torrc file's meta-format in doc/torrc_format.txt. This is mainly
237 of interest to people writing programs to parse or generate torrc
238 files. This document is not a commitment to long-term
239 compatibility; some aspects of the current format are a bit
240 ridiculous. Closes ticket 2325.
243 - Tor no longer supports copies of OpenSSL that are missing support
244 for Elliptic Curve Cryptography. (We began using ECC when
245 available in 0.2.4.8-alpha, for more safe and efficient key
246 negotiation.) In particular, support for at least one of P256 or
247 P224 is now required, with manual configuration needed if only
248 P224 is available. Resolves ticket 16140.
249 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
250 on an operating system that has not upgraded to OpenSSL 1.0 or
251 later, and you compile Tor from source, you will need to install a
252 more recent OpenSSL to link Tor against.) These versions of
253 OpenSSL are still supported by the OpenSSL, but the numerous
254 cryptographic improvements in later OpenSSL releases makes them a
255 clear choice. Resolves ticket 16034.
256 - Remove the HidServDirectoryV2 option. Now all relays offer to
257 store hidden service descriptors. Related to 16543.
258 - Remove the VoteOnHidServDirectoriesV2 option, since all
259 authorities have long set it to 1. Closes ticket 16543.
262 - Document use of coverity, clang static analyzer, and clang dynamic
263 undefined behavior and address sanitizers in doc/HACKING. Include
264 detailed usage instructions in the blacklist. Patch by "teor".
266 - The link authentication protocol code now has extensive tests.
267 - The relay descriptor signature testing code now has
269 - The test_workqueue program now runs faster, and is enabled by
270 default as a part of "make check".
271 - Now that OpenSSL has its own scrypt implementation, add an unit
272 test that checks for interoperability between libscrypt_scrypt()
273 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
274 and rely on EVP_PBE_scrypt() whenever possible. Resolves
278 Changes in version 0.2.6.10 - 2015-07-12
279 Tor version 0.2.6.10 fixes some significant stability and hidden
280 service client bugs, bulletproofs the cryptography init process, and
281 fixes a bug when using the sandbox code with some older versions of
282 Linux. Everyone running an older version, especially an older version
283 of 0.2.6, should upgrade.
285 o Major bugfixes (hidden service clients, stability):
286 - Stop refusing to store updated hidden service descriptors on a
287 client. This reverts commit 9407040c59218 (which indeed fixed bug
288 14219, but introduced a major hidden service reachability
289 regression detailed in bug 16381). This is a temporary fix since
290 we can live with the minor issue in bug 14219 (it just results in
291 some load on the network) but the regression of 16381 is too much
292 of a setback. First-round fix for bug 16381; bugfix
295 o Major bugfixes (stability):
296 - Stop crashing with an assertion failure when parsing certain kinds
297 of malformed or truncated microdescriptors. Fixes bug 16400;
298 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
299 by "cypherpunks_backup".
300 - Stop random client-side assertion failures that could occur when
301 connecting to a busy hidden service, or connecting to a hidden
302 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
305 o Minor features (geoip):
306 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
307 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
309 o Minor bugfixes (crypto error-handling):
310 - Check for failures from crypto_early_init, and refuse to continue.
311 A previous typo meant that we could keep going with an
312 uninitialized crypto library, and would have OpenSSL initialize
313 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
314 when implementing ticket 4900. Patch by "teor".
316 o Minor bugfixes (Linux seccomp2 sandbox):
317 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
318 these when eventfd2() support is missing. Fixes bug 16363; bugfix
319 on 0.2.6.3-alpha. Patch from "teor".
322 Changes in version 0.2.6.9 - 2015-06-11
323 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
324 requirements for receiving an HSDir flag, and addresses some other small
325 bugs in the systemd and sandbox code. Clients using circuit isolation
326 should upgrade; all directory authorities should upgrade.
328 o Major bugfixes (client-side privacy):
329 - Properly separate out each SOCKSPort when applying stream
330 isolation. The error occurred because each port's session group was
331 being overwritten by a default value when the listener connection
332 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
335 o Minor feature (directory authorities, security):
336 - The HSDir flag given by authorities now requires the Stable flag.
337 For the current network, this results in going from 2887 to 2806
338 HSDirs. Also, it makes it harder for an attacker to launch a sybil
339 attack by raising the effort for a relay to become Stable which
340 takes at the very least 7 days to do so and by keeping the 96
341 hours uptime requirement for HSDir. Implements ticket 8243.
343 o Minor bugfixes (compilation):
344 - Build with --enable-systemd correctly when libsystemd is
345 installed, but systemd is not. Fixes bug 16164; bugfix on
346 0.2.6.3-alpha. Patch from Peter Palfrader.
348 o Minor bugfixes (Linux seccomp2 sandbox):
349 - Fix sandboxing to work when running as a relaymby renaming of
350 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
351 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
352 - Allow systemd connections to work with the Linux seccomp2 sandbox
353 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
356 o Minor bugfixes (tests):
357 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
358 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
361 Changes in version 0.2.6.8 - 2015-05-21
362 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
363 fixes an authority-side bug in assigning the HSDir flag. All directory
364 authorities should upgrade.
366 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
367 - Revert commit that made directory authorities assign the HSDir
368 flag to relay without a DirPort; this was bad because such relays
369 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
370 on tor-0.2.6.3-alpha.
372 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
373 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
374 a client authorized hidden service. Fixes bug 15823; bugfix
377 o Minor features (geoip):
378 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
379 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
383 Changes in version 0.2.7.1-alpha - 2015-05-12
384 Tor 0.2.7.1-alpha is the first alpha release in its series. It
385 includes numerous small features and bugfixes against previous Tor
386 versions, and numerous small infrastructure improvements. The most
387 notable features are several new ways for controllers to interact with
388 the hidden services subsystem.
390 o New system requirements:
391 - Tor no longer includes workarounds to support Libevent versions
392 before 1.3e. Libevent 2.0 or later is recommended. Closes
395 o Major features (controller):
396 - Add the ADD_ONION and DEL_ONION commands that allow the creation
397 and management of hidden services via the controller. Closes
399 - New "GETINFO onions/current" and "GETINFO onions/detached"
400 commands to get information about hidden services created via the
401 controller. Part of ticket 6411.
402 - New HSFETCH command to launch a request for a hidden service
403 descriptor. Closes ticket 14847.
404 - New HSPOST command to upload a hidden service descriptor. Closes
405 ticket 3523. Patch by "DonnchaC".
407 o Major bugfixes (hidden services):
408 - Revert commit that made directory authorities assign the HSDir
409 flag to relay without a DirPort; this was bad because such relays
410 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
411 on tor-0.2.6.3-alpha.
413 o Minor features (clock-jump tolerance):
414 - Recover better when our clock jumps back many hours, like might
415 happen for Tails or Whonix users who start with a very wrong
416 hardware clock, use Tor to discover a more accurate time, and then
417 fix their clock. Resolves part of ticket 8766.
419 o Minor features (command-line interface):
420 - Make --hash-password imply --hush to prevent unnecessary noise.
421 Closes ticket 15542. Patch from "cypherpunks".
422 - Print a warning whenever we find a relative file path being used
423 as torrc option. Resolves issue 14018.
425 o Minor features (controller):
426 - Add DirAuthority lines for default directory authorities to the
427 output of the "GETINFO config/defaults" command if not already
428 present. Implements ticket 14840.
429 - Controllers can now use "GETINFO hs/client/desc/id/..." to
430 retrieve items from the client's hidden service descriptor cache.
432 - Implement a new controller command "GETINFO status/fresh-relay-
433 descs" to fetch a descriptor/extrainfo pair that was generated on
434 demand just for the controller's use. Implements ticket 14784.
436 o Minor features (DoS-resistance):
437 - Make it harder for attackers to overload hidden services with
438 introductions, by blocking multiple introduction requests on the
439 same circuit. Resolves ticket 15515.
441 o Minor features (geoip):
442 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
443 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
446 o Minor features (HS popularity countermeasure):
447 - To avoid leaking HS popularity, don't cycle the introduction point
448 when we've handled a fixed number of INTRODUCE2 cells but instead
449 cycle it when a random number of introductions is reached, thus
450 making it more difficult for an attacker to find out the amount of
451 clients that have used the introduction point for a specific HS.
454 o Minor features (logging):
455 - Include the Tor version in all LD_BUG log messages, since people
456 tend to cut and paste those into the bugtracker. Implements
459 o Minor features (pluggable transports):
460 - When launching managed pluggable transports on Linux systems,
461 attempt to have the kernel deliver a SIGTERM on tor exit if the
462 pluggable transport process is still running. Resolves
464 - When launching managed pluggable transports, setup a valid open
465 stdin in the child process that can be used to detect if tor has
466 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
467 can be used by implementations to detect this new behavior.
468 Resolves ticket 15435.
470 o Minor features (testing):
471 - Add a test to verify that the compiler does not eliminate our
472 memwipe() implementation. Closes ticket 15377.
473 - Add make rule `check-changes` to verify the format of changes
474 files. Closes ticket 15180.
475 - Add unit tests for control_event_is_interesting(). Add a compile-
476 time check that the number of events doesn't exceed the capacity
477 of control_event_t.event_mask. Closes ticket 15431, checks for
478 bugs similar to 13085. Patch by "teor".
479 - Command-line argument tests moved to Stem. Resolves ticket 14806.
480 - Integrate the ntor, backtrace, and zero-length keys tests into the
481 automake test suite. Closes ticket 15344.
482 - Remove assertions during builds to determine Tor's test coverage.
483 We don't want to trigger these even in assertions, so including
484 them artificially makes our branch coverage look worse than it is.
485 This patch provides the new test-stem-full and coverage-html-full
486 configure options. Implements ticket 15400.
488 o Minor bugfixes (build):
489 - Improve out-of-tree builds by making non-standard rules work and
490 clean up additional files and directories. Fixes bug 15053; bugfix
493 o Minor bugfixes (command-line interface):
494 - When "--quiet" is provided along with "--validate-config", do not
495 write anything to stdout on success. Fixes bug 14994; bugfix
497 - When complaining about bad arguments to "--dump-config", use
500 o Minor bugfixes (configuration, unit tests):
501 - Only add the default fallback directories when the DirAuthorities,
502 AlternateDirAuthority, and FallbackDir directory config options
503 are set to their defaults. The default fallback directory list is
504 currently empty, this fix will only change tor's behavior when it
505 has default fallback directories. Includes unit tests for
506 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
507 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
509 o Minor bugfixes (correctness):
510 - For correctness, avoid modifying a constant string in
511 handle_control_postdescriptor. Fixes bug 15546; bugfix
513 - Remove side-effects from tor_assert() calls. This was harmless,
514 because we never disable assertions, but it is bad style and
515 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
518 o Minor bugfixes (hidden service):
519 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
520 a client authorized hidden service. Fixes bug 15823; bugfix
522 - Remove an extraneous newline character from the end of hidden
523 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
525 o Minor bugfixes (interface):
526 - Print usage information for --dump-config when it is used without
527 an argument. Also, fix the error message to use different wording
528 and add newline at the end. Fixes bug 15541; bugfix
531 o Minor bugfixes (logs):
532 - When building Tor under Clang, do not include an extra set of
533 parentheses in log messages that include function names. Fixes bug
534 15269; bugfix on every released version of Tor when compiled with
537 o Minor bugfixes (network):
538 - When attempting to use fallback technique for network interface
539 lookup, disregard loopback and multicast addresses since they are
540 unsuitable for public communications.
542 o Minor bugfixes (statistics):
543 - Disregard the ConnDirectionStatistics torrc options when Tor is
544 not a relay since in that mode of operation no sensible data is
545 being collected and because Tor might run into measurement hiccups
546 when running as a client for some time, then becoming a relay.
547 Fixes bug 15604; bugfix on 0.2.2.35.
549 o Minor bugfixes (test networks):
550 - When self-testing reachability, use ExtendAllowPrivateAddresses to
551 determine if local/private addresses imply reachability. The
552 previous fix used TestingTorNetwork, which implies
553 ExtendAllowPrivateAddresses, but this excluded rare configurations
554 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
555 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
556 issue discovered by CJ Ess.
558 o Minor bugfixes (testing):
559 - Check for matching value in server response in ntor_ref.py. Fixes
560 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
562 - Set the severity correctly when testing
563 get_interface_addresses_ifaddrs() and
564 get_interface_addresses_win32(), so that the tests fail gracefully
565 instead of triggering an assertion. Fixes bug 15759; bugfix on
566 0.2.6.3-alpha. Reported by Nicolas Derive.
568 o Code simplification and refactoring:
569 - Move the hacky fallback code out of get_interface_address6() into
570 separate function and get it covered with unit-tests. Resolves
572 - Refactor hidden service client-side cache lookup to intelligently
573 report its various failure cases, and disentangle failure cases
574 involving a lack of introduction points. Closes ticket 14391.
575 - Use our own Base64 encoder instead of OpenSSL's, to allow more
576 control over the output. Part of ticket 15652.
579 - Improve the descriptions of statistics-related torrc options in
580 the manpage to describe rationale and possible uses cases. Fixes
582 - Improve the layout and formatting of ./configure --help messages.
583 Closes ticket 15024. Patch from "cypherpunks".
584 - Standardize on the term "server descriptor" in the manual page.
585 Previously, we had used "router descriptor", "server descriptor",
586 and "relay descriptor" interchangeably. Part of ticket 14987.
589 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
590 and always use the internal Base64 decoder. The internal decoder
591 has been part of tor since tor-0.2.0.10-alpha, and no one should
592 be using the OpenSSL one. Part of ticket 15652.
593 - Remove the 'tor_strclear()' function; use memwipe() instead.
597 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
598 fingerprinting we now recommend pluggable transports; for forward-
599 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
600 - Remove the undocumented "--digests" command-line option. It
601 complicated our build process, caused subtle build issues on
602 multiple platforms, and is now redundant since we started
603 including git version identifiers. Closes ticket 14742.
604 - Tor no longer contains checks for ancient directory cache versions
605 that didn't know about microdescriptors.
606 - Tor no longer contains workarounds for stat files generated by
607 super-old versions of Tor that didn't choose guards sensibly.
610 Changes in version 0.2.4.27 - 2015-04-06
611 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
612 could be used by an attacker to crash hidden services, or crash clients
613 visiting hidden services. Hidden services should upgrade as soon as
614 possible; clients should upgrade whenever packages become available.
616 This release also backports a simple improvement to make hidden
617 services a bit less vulnerable to denial-of-service attacks.
619 o Major bugfixes (security, hidden service):
620 - Fix an issue that would allow a malicious client to trigger an
621 assertion failure and halt a hidden service. Fixes bug 15600;
622 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
623 - Fix a bug that could cause a client to crash with an assertion
624 failure when parsing a malformed hidden service descriptor. Fixes
625 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
627 o Minor features (DoS-resistance, hidden service):
628 - Introduction points no longer allow multiple INTRODUCE1 cells to
629 arrive on the same circuit. This should make it more expensive for
630 attackers to overwhelm hidden services with introductions.
631 Resolves ticket 15515.
634 Changes in version 0.2.6.7 - 2015-04-06
635 Tor 0.2.6.7 fixes two security issues that could be used by an
636 attacker to crash hidden services, or crash clients visiting hidden
637 services. Hidden services should upgrade as soon as possible; clients
638 should upgrade whenever packages become available.
640 This release also contains two simple improvements to make hidden
641 services a bit less vulnerable to denial-of-service attacks.
643 o Major bugfixes (security, hidden service):
644 - Fix an issue that would allow a malicious client to trigger an
645 assertion failure and halt a hidden service. Fixes bug 15600;
646 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
647 - Fix a bug that could cause a client to crash with an assertion
648 failure when parsing a malformed hidden service descriptor. Fixes
649 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
651 o Minor features (DoS-resistance, hidden service):
652 - Introduction points no longer allow multiple INTRODUCE1 cells to
653 arrive on the same circuit. This should make it more expensive for
654 attackers to overwhelm hidden services with introductions.
655 Resolves ticket 15515.
656 - Decrease the amount of reattempts that a hidden service performs
657 when its rendezvous circuits fail. This reduces the computational
658 cost for running a hidden service under heavy load. Resolves
662 Changes in version 0.2.6.6 - 2015-03-24
663 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
665 It adds numerous safety, security, correctness, and performance
666 improvements. Client programs can be configured to use more kinds of
667 sockets, AutomapHosts works better, the multithreading backend is
668 improved, cell transmission is refactored, test coverage is much
669 higher, more denial-of-service attacks are handled, guard selection is
670 improved to handle long-term guards better, pluggable transports
671 should work a bit better, and some annoying hidden service performance
672 bugs should be addressed.
674 o Minor bugfixes (portability):
675 - Use the correct datatype in the SipHash-2-4 function to prevent
676 compilers from assuming any sort of alignment. Fixes bug 15436;
677 bugfix on 0.2.5.3-alpha.
679 Changes in version 0.2.6.5-rc - 2015-03-18
680 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
681 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
683 o Major bugfixes (client):
684 - Avoid crashing when making certain configuration option changes on
685 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
688 o Major bugfixes (pluggable transports):
689 - Initialize the extended OR Port authentication cookie before
690 launching pluggable transports. This prevents a race condition
691 that occured when server-side pluggable transports would cache the
692 authentication cookie before it has been (re)generated. Fixes bug
693 15240; bugfix on 0.2.5.1-alpha.
695 o Major bugfixes (portability):
696 - Do not crash on startup when running on Solaris. Fixes a bug
697 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
700 o Minor features (heartbeat):
701 - On relays, report how many connections we negotiated using each
702 version of the Tor link protocols. This information will let us
703 know if removing support for very old versions of the Tor
704 protocols is harming the network. Closes ticket 15212.
706 o Code simplification and refactoring:
707 - Refactor main loop to extract the 'loop' part. This makes it
708 easier to run Tor under Shadow. Closes ticket 15176.
711 Changes in version 0.2.5.11 - 2015-03-17
712 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
714 It backports several bugfixes from the 0.2.6 branch, including a
715 couple of medium-level security fixes for relays and exit nodes.
716 It also updates the list of directory authorities.
718 o Directory authority changes:
719 - Remove turtles as a directory authority.
720 - Add longclaw as a new (v3) directory authority. This implements
721 ticket 13296. This keeps the directory authority count at 9.
722 - The directory authority Faravahar has a new IP address. This
725 o Major bugfixes (crash, OSX, security):
726 - Fix a remote denial-of-service opportunity caused by a bug in
727 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
730 o Major bugfixes (relay, stability, possible security):
731 - Fix a bug that could lead to a relay crashing with an assertion
732 failure if a buffer of exactly the wrong layout was passed to
733 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
734 0.2.0.10-alpha. Patch from 'cypherpunks'.
735 - Do not assert if the 'data' pointer on a buffer is advanced to the
736 very end of the buffer; log a BUG message instead. Only assert if
737 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
739 o Major bugfixes (exit node stability):
740 - Fix an assertion failure that could occur under high DNS load.
741 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
742 diagnosed and fixed by "cypherpunks".
744 o Major bugfixes (Linux seccomp2 sandbox):
745 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
746 crash during attempts to call wait4. Fixes bug 15088; bugfix on
747 0.2.5.1-alpha. Patch from "sanic".
749 o Minor features (controller):
750 - New "GETINFO bw-event-cache" to get information about recent
751 bandwidth events. Closes ticket 14128. Useful for controllers to
752 get recent bandwidth history after the fix for ticket 13988.
754 o Minor features (geoip):
755 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
756 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
759 o Minor bugfixes (client, automapping):
760 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
761 no value follows the option. Fixes bug 14142; bugfix on
762 0.2.4.7-alpha. Patch by "teor".
763 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
764 14195; bugfix on 0.1.0.1-rc.
766 o Minor bugfixes (compilation):
767 - Build without warnings with the stock OpenSSL srtp.h header, which
768 has a duplicate declaration of SSL_get_selected_srtp_profile().
769 Fixes bug 14220; this is OpenSSL's bug, not ours.
771 o Minor bugfixes (directory authority):
772 - Allow directory authorities to fetch more data from one another if
773 they find themselves missing lots of votes. Previously, they had
774 been bumping against the 10 MB queued data limit. Fixes bug 14261;
775 bugfix on 0.1.2.5-alpha.
776 - Enlarge the buffer to read bwauth generated files to avoid an
777 issue when parsing the file in dirserv_read_measured_bandwidths().
778 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
780 o Minor bugfixes (statistics):
781 - Increase period over which bandwidth observations are aggregated
782 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
784 o Minor bugfixes (preventative security, C safety):
785 - When reading a hexadecimal, base-32, or base-64 encoded value from
786 a string, always overwrite the whole output buffer. This prevents
787 some bugs where we would look at (but fortunately, not reveal)
788 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
792 Changes in version 0.2.4.26 - 2015-03-17
793 Tor 0.2.4.26 includes an updated list of directory authorities. It
794 also backports a couple of stability and security bugfixes from 0.2.5
797 o Directory authority changes:
798 - Remove turtles as a directory authority.
799 - Add longclaw as a new (v3) directory authority. This implements
800 ticket 13296. This keeps the directory authority count at 9.
801 - The directory authority Faravahar has a new IP address. This
804 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
805 - Fix an assertion failure that could occur under high DNS load.
806 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
807 diagnosed and fixed by "cypherpunks".
809 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
810 - Fix a bug that could lead to a relay crashing with an assertion
811 failure if a buffer of exactly the wrong layout was passed to
812 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
813 0.2.0.10-alpha. Patch from 'cypherpunks'.
814 - Do not assert if the 'data' pointer on a buffer is advanced to the
815 very end of the buffer; log a BUG message instead. Only assert if
816 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
818 o Minor features (geoip):
819 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
820 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
823 Changes in version 0.2.6.4-rc - 2015-03-09
824 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
825 attacker might be able to use in order to crash certain Tor
826 directories. It also resolves some minor issues left over from, or
827 introduced in, Tor 0.2.6.3-alpha or earlier.
829 o Major bugfixes (crash, OSX, security):
830 - Fix a remote denial-of-service opportunity caused by a bug in
831 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
834 o Major bugfixes (relay, stability, possible security):
835 - Fix a bug that could lead to a relay crashing with an assertion
836 failure if a buffer of exactly the wrong layout is passed to
837 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
838 0.2.0.10-alpha. Patch from "cypherpunks".
839 - Do not assert if the 'data' pointer on a buffer is advanced to the
840 very end of the buffer; log a BUG message instead. Only assert if
841 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
843 o Major bugfixes (FreeBSD IPFW transparent proxy):
844 - Fix address detection with FreeBSD transparent proxies, when
845 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
848 o Major bugfixes (Linux seccomp2 sandbox):
849 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
850 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
852 - Allow AF_UNIX hidden services to be used with the seccomp2
853 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
854 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
855 crash during attempts to call wait4. Fixes bug 15088; bugfix on
856 0.2.5.1-alpha. Patch from "sanic".
858 o Minor features (controller):
859 - Messages about problems in the bootstrap process now include
860 information about the server we were trying to connect to when we
861 noticed the problem. Closes ticket 15006.
863 o Minor features (geoip):
864 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
865 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
868 o Minor features (logs):
869 - Quiet some log messages in the heartbeat and at startup. Closes
872 o Minor bugfixes (certificate handling):
873 - If an authority operator accidentally makes a signing certificate
874 with a future publication time, do not discard its real signing
875 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
876 - Remove any old authority certificates that have been superseded
877 for at least two days. Previously, we would keep superseded
878 certificates until they expired, if they were published close in
879 time to the certificate that superseded them. Fixes bug 11454;
880 bugfix on 0.2.1.8-alpha.
882 o Minor bugfixes (compilation):
883 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
885 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
888 o Minor bugfixes (testing):
889 - Fix endianness issues in unit test for resolve_my_address() to
890 have it pass on big endian systems. Fixes bug 14980; bugfix on
892 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
893 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
894 - When running the new 'make test-stem' target, use the configured
895 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
897 - When running the zero-length-keys tests, do not use the default
898 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
901 o Directory authority IP change:
902 - The directory authority Faravahar has a new IP address. This
906 - Remove some lingering dead code that once supported mempools.
907 Mempools were disabled by default in 0.2.5, and removed entirely
908 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
912 Changes in version 0.2.6.3-alpha - 2015-02-19
913 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
914 the 0.2.6.x series. It introduces support for more kinds of sockets,
915 makes it harder to accidentally run an exit, improves our
916 multithreading backend, incorporates several fixes for the
917 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
919 If no major regressions or security holes are found in this version,
920 the next version will be a release candidate.
922 o Deprecated versions:
923 - Tor relays older than 0.2.4.18-rc are no longer allowed to
924 advertise themselves on the network. Closes ticket 13555.
926 o Major features (security, unix domain sockets):
927 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
928 applications can reach Tor without having to create AF_INET or
929 AF_INET6 sockets, meaning they can completely disable their
930 ability to make non-Tor network connections. To create a socket of
931 this type, use "SocksPort unix:/path/to/socket". Implements
933 - Support mapping hidden service virtual ports to AF_UNIX sockets.
934 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
935 Implements ticket 11485.
937 o Major features (changed defaults):
938 - Prevent relay operators from unintentionally running exits: When a
939 relay is configured as an exit node, we now warn the user unless
940 the "ExitRelay" option is set to 1. We warn even more loudly if
941 the relay is configured with the default exit policy, since this
942 can indicate accidental misconfiguration. Setting "ExitRelay 0"
943 stops Tor from running as an exit relay. Closes ticket 10067.
945 o Major features (directory system):
946 - When downloading server- or microdescriptors from a directory
947 server, we no longer launch multiple simultaneous requests to the
948 same server. This reduces load on the directory servers,
949 especially when directory guards are in use. Closes ticket 9969.
950 - When downloading server- or microdescriptors over a tunneled
951 connection, do not limit the length of our requests to what the
952 Squid proxy is willing to handle. Part of ticket 9969.
953 - Authorities can now vote on the correct digests and latest
954 versions for different software packages. This allows packages
955 that include Tor to use the Tor authority system as a way to get
956 notified of updates and their correct digests. Implements proposal
957 227. Closes ticket 10395.
959 o Major features (guards):
960 - Introduce the Guardfraction feature to improves load balancing on
961 guard nodes. Specifically, it aims to reduce the traffic gap that
962 guard nodes experience when they first get the Guard flag. This is
963 a required step if we want to increase the guard lifetime to 9
964 months or greater. Closes ticket 9321.
966 o Major features (performance):
967 - Make the CPU worker implementation more efficient by avoiding the
968 kernel and lengthening pipelines. The original implementation used
969 sockets to transfer data from the main thread to the workers, and
970 didn't allow any thread to be assigned more than a single piece of
971 work at once. The new implementation avoids communications
972 overhead by making requests in shared memory, avoiding kernel IO
973 where possible, and keeping more requests in flight at once.
974 Implements ticket 9682.
976 o Major features (relay):
977 - Raise the minimum acceptable configured bandwidth rate for bridges
978 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
979 20 KiB/sec.) Closes ticket 13822.
981 o Major bugfixes (exit node stability):
982 - Fix an assertion failure that could occur under high DNS load.
983 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
984 diagnosed and fixed by "cypherpunks".
986 o Major bugfixes (mixed relay-client operation):
987 - When running as a relay and client at the same time (not
988 recommended), if we decide not to use a new guard because we want
989 to retry older guards, only close the locally-originating circuits
990 passing through that guard. Previously we would close all the
991 circuits through that guard. Fixes bug 9819; bugfix on
992 0.2.1.1-alpha. Reported by "skruffy".
994 o Minor features (build):
995 - New --disable-system-torrc compile-time option to prevent Tor from
996 looking for the system-wide torrc or torrc-defaults files.
997 Resolves ticket 13037.
999 o Minor features (controller):
1000 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
1001 events so controllers can observe circuit isolation inputs. Closes
1003 - ControlPort now supports the unix:/path/to/socket syntax as an
1004 alternative to the ControlSocket option, for consistency with
1005 SocksPort and HiddenServicePort. Closes ticket 14451.
1006 - New "GETINFO bw-event-cache" to get information about recent
1007 bandwidth events. Closes ticket 14128. Useful for controllers to
1008 get recent bandwidth history after the fix for ticket 13988.
1010 o Minor features (Denial of service resistance):
1011 - Count the total number of bytes used storing hidden service
1012 descriptors against the value of MaxMemInQueues. If we're low on
1013 memory, and more than 20% of our memory is used holding hidden
1014 service descriptors, free them until no more than 10% of our
1015 memory holds hidden service descriptors. Free the least recently
1016 fetched descriptors first. Resolves ticket 13806.
1017 - When we have recently been under memory pressure (over 3/4 of
1018 MaxMemInQueues is allocated), then allocate smaller zlib objects
1019 for small requests. Closes ticket 11791.
1021 o Minor features (geoip):
1022 - Update geoip and geoip6 files to the January 7 2015 Maxmind
1023 GeoLite2 Country database.
1025 o Minor features (guard nodes):
1026 - Reduce the time delay before saving guard status to disk from 10
1027 minutes to 30 seconds (or from one hour to 10 minutes if
1028 AvoidDiskWrites is set). Closes ticket 12485.
1030 o Minor features (hidden service):
1031 - Make Sybil attacks against hidden services harder by changing the
1032 minimum time required to get the HSDir flag from 25 hours up to 96
1033 hours. Addresses ticket 14149.
1034 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
1035 services to disable the anti-scanning feature introduced in
1036 0.2.6.2-alpha. With this option not set, a connection to an
1037 unlisted port closes the circuit. With this option set, only a
1038 RELAY_DONE cell is sent. Closes ticket 14084.
1040 o Minor features (interface):
1041 - Implement "-f -" command-line option to read torrc configuration
1042 from standard input, if you don't want to store the torrc file in
1043 the file system. Implements feature 13865.
1045 o Minor features (logging):
1046 - Add a count of unique clients to the bridge heartbeat message.
1047 Resolves ticket 6852.
1048 - Suppress "router info incompatible with extra info" message when
1049 reading extrainfo documents from cache. (This message got loud
1050 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
1052 - Elevate hidden service authorized-client message from DEBUG to
1053 INFO. Closes ticket 14015.
1055 o Minor features (stability):
1056 - Add assertions in our hash-table iteration code to check for
1057 corrupted values that could cause infinite loops. Closes
1060 o Minor features (systemd):
1061 - Various improvements and modernizations in systemd hardening
1062 support. Closes ticket 13805. Patch from Craig Andrews.
1064 o Minor features (testing networks):
1065 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
1066 and the default on a testing network to 2 minutes. Drop the
1067 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
1068 keep the default on a testing network at 30 seconds. This reduces
1069 HS bootstrap time to around 25 seconds. Also, change the default
1070 time in test-network.sh to match. Closes ticket 13401. Patch
1072 - Create TestingDirAuthVoteHSDir to correspond to
1073 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
1074 HSDir flag for the listed relays regardless of uptime or ORPort
1075 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
1076 Partial implementation for ticket 14067. Patch by "teor".
1078 o Minor features (tor2web mode):
1079 - Introduce the config option Tor2webRendezvousPoints, which allows
1080 clients in Tor2webMode to select a specific Rendezvous Point to be
1081 used in HS circuits. This might allow better performance for
1082 Tor2Web nodes. Implements ticket 12844.
1084 o Minor bugfixes (client DNS):
1085 - Report the correct cached DNS expiration times on SOCKS port or in
1086 DNS replies. Previously, we would report everything as "never
1087 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
1088 - Avoid a small memory leak when we find a cached answer for a
1089 reverse DNS lookup in a client-side DNS cache. (Remember, client-
1090 side DNS caching is off by default, and is not recommended.) Fixes
1091 bug 14259; bugfix on 0.2.0.1-alpha.
1093 o Minor bugfixes (client, automapping):
1094 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1095 no value follows the option. Fixes bug 14142; bugfix on
1096 0.2.4.7-alpha. Patch by "teor".
1097 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1098 14195; bugfix on 0.1.0.1-rc.
1099 - Prevent changes to other options from removing the wildcard value
1100 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
1102 - Allow MapAddress and AutomapHostsOnResolve to work together when
1103 an address is mapped into another address type (like .onion) that
1104 must be automapped at resolve time. Fixes bug 7555; bugfix
1107 o Minor bugfixes (client, bridges):
1108 - When we are using bridges and we had a network connectivity
1109 problem, only retry connecting to our currently configured
1110 bridges, not all bridges we know about and remember using. Fixes
1111 bug 14216; bugfix on 0.2.2.17-alpha.
1113 o Minor bugfixes (client, IPv6):
1114 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
1115 flag is not set; and not because the NoIPv4Traffic flag was set.
1116 Previously we'd looked at the NoIPv4Traffic flag for both types of
1117 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
1119 o Minor bugfixes (compilation):
1120 - The address of an array in the middle of a structure will always
1121 be non-NULL. clang recognises this and complains. Disable the
1122 tautologous and redundant check to silence this warning. Fixes bug
1123 14001; bugfix on 0.2.1.2-alpha.
1124 - Avoid warnings when building with systemd 209 or later. Fixes bug
1125 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
1126 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
1127 Addresses ticket 14188.
1128 - Build without warnings with the stock OpenSSL srtp.h header, which
1129 has a duplicate declaration of SSL_get_selected_srtp_profile().
1130 Fixes bug 14220; this is OpenSSL's bug, not ours.
1131 - Do not compile any code related to Tor2Web mode when Tor2Web mode
1132 is not enabled at compile time. Previously, this code was included
1133 in a disabled state. See discussion on ticket 12844.
1134 - Remove the --disable-threads configure option again. It was
1135 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
1136 14819; bugfix on 0.2.6.2-alpha.
1138 o Minor bugfixes (controller):
1139 - Report "down" in response to the "GETINFO entry-guards" command
1140 when relays are down with an unreachable_since value. Previously,
1141 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
1142 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
1143 14116; bugfix on 0.2.2.9-alpha.
1144 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
1145 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
1147 o Minor bugfixes (directory authority):
1148 - Allow directory authorities to fetch more data from one another if
1149 they find themselves missing lots of votes. Previously, they had
1150 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1151 bugfix on 0.1.2.5-alpha.
1152 - Do not attempt to download extrainfo documents which we will be
1153 unable to validate with a matching server descriptor. Fixes bug
1154 13762; bugfix on 0.2.0.1-alpha.
1155 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
1156 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
1157 - Enlarge the buffer to read bwauth generated files to avoid an
1158 issue when parsing the file in dirserv_read_measured_bandwidths().
1159 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1161 o Minor bugfixes (file handling):
1162 - Stop failing when key files are zero-length. Instead, generate new
1163 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
1164 on all versions of Tor. Patch by "teor".
1165 - Stop generating a fresh .old RSA onion key file when the .old file
1166 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
1167 - Avoid overwriting .old key files with empty key files.
1168 - Skip loading zero-length extrainfo store, router store, stats,
1169 state, and key files.
1170 - Avoid crashing when trying to reload a torrc specified as a
1171 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
1174 o Minor bugfixes (hidden services):
1175 - Close the introduction circuit when we have no more usable intro
1176 points, instead of waiting for it to time out. This also ensures
1177 that no follow-up HS descriptor fetch is triggered when the
1178 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
1179 - When fetching a hidden service descriptor for a down service that
1180 was recently up, do not keep refetching until we try the same
1181 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
1182 - Successfully launch Tor with a nonexistent hidden service
1183 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
1184 14106; bugfix on 0.2.6.2-alpha.
1186 o Minor bugfixes (logging):
1187 - Avoid crashing when there are more log domains than entries in
1188 domain_list. Bugfix on 0.2.3.1-alpha.
1189 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
1191 - Don't log messages to stdout twice when starting up. Fixes bug
1192 13993; bugfix on 0.2.6.1-alpha.
1194 o Minor bugfixes (parsing):
1195 - Stop accepting milliseconds (or other junk) at the end of
1196 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
1197 - Support two-number and three-number version numbers correctly, in
1198 case we change the Tor versioning system in the future. Fixes bug
1199 13661; bugfix on 0.0.8pre1.
1201 o Minor bugfixes (path counting):
1202 - When deciding whether the consensus lists any exit nodes, count
1203 the number listed in the consensus, not the number we have
1204 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
1205 - When deciding whether we have any exit nodes, only examine
1206 ExitNodes when the ExitNodes option is actually set. Fixes part of
1207 bug 14918; bugfix on 0.2.6.2-alpha.
1208 - Get rid of redundant and possibly scary warnings that we are
1209 missing directory information while we bootstrap. Fixes part of
1210 bug 14918; bugfix on 0.2.6.2-alpha.
1212 o Minor bugfixes (portability):
1213 - Fix the ioctl()-based network interface lookup code so that it
1214 will work on systems that have variable-length struct ifreq, for
1216 - Fix scheduler compilation on targets where char is unsigned. Fixes
1217 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
1219 o Minor bugfixes (sandbox):
1220 - Allow glibc fatal errors to be sent to stderr before Tor exits.
1221 Previously, glibc would try to write them to /dev/tty, and the
1222 sandbox would trap the call and make Tor exit prematurely. Fixes
1223 bug 14759; bugfix on 0.2.5.1-alpha.
1225 o Minor bugfixes (shutdown):
1226 - When shutting down, always call event_del() on lingering read or
1227 write events before freeing them. Otherwise, we risk double-frees
1228 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
1231 o Minor bugfixes (small memory leaks):
1232 - Avoid leaking memory when using IPv6 virtual address mappings.
1233 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
1236 o Minor bugfixes (statistics):
1237 - Increase period over which bandwidth observations are aggregated
1238 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1240 o Minor bugfixes (systemd support):
1241 - Fix detection and operation of systemd watchdog. Fixes part of bug
1242 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
1243 - Run correctly under systemd with the RunAsDaemon option set. Fixes
1244 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
1245 - Inform the systemd supervisor about more changes in the Tor
1246 process status. Implements part of ticket 14141. Patch from
1248 - Cause the "--disable-systemd" option to actually disable systemd
1249 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
1252 o Minor bugfixes (TLS):
1253 - Check more thoroughly throughout the TLS code for possible
1254 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
1256 o Minor bugfixes (transparent proxy):
1257 - Use getsockname, not getsockopt, to retrieve the address for a
1258 TPROXY-redirected connection. Fixes bug 13796; bugfix
1261 o Code simplification and refactoring:
1262 - Move fields related to isolating and configuring client ports into
1263 a shared structure. Previously, they were duplicated across
1264 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
1265 to copy them correctly had been the cause of at least one bug in
1266 the past. Closes ticket 8546.
1267 - Refactor the get_interface_addresses_raw() doom-function into
1268 multiple smaller and simpler subfunctions. Cover the resulting
1269 subfunctions with unit-tests. Fixes a significant portion of
1271 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
1272 only for version <= 0.2.2.24 which is now deprecated. Closes
1274 - Remove a test for a long-defunct broken version-one
1278 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
1279 for writing the OpenBSD-specific tips. Resolves ticket 13702.
1280 - Make the tor-resolve documentation match its help string and its
1281 options. Resolves part of ticket 14325.
1282 - Log a more useful error message from tor-resolve when failing to
1283 look up a hidden service address. Resolves part of ticket 14325.
1285 o Downgraded warnings:
1286 - Don't warn when we've attempted to contact a relay using the wrong
1287 ntor onion key. Closes ticket 9635.
1290 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
1291 longer silently accepted as an alias for "ExitNodes".
1292 - The --enable-mempool and --enable-buf-freelists options, which
1293 were originally created to work around bad malloc implementations,
1294 no longer exist. They were off-by-default in 0.2.5. Closes
1298 - Make the checkdir/perms test complete successfully even if the
1299 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
1300 - Test that tor does not fail when key files are zero-length. Check
1301 that tor generates new keys, and overwrites the empty key files.
1302 - Test that tor generates new keys when keys are missing
1303 (existing behavior).
1304 - Test that tor does not overwrite key files that already contain
1305 data (existing behavior). Tests bug 13111. Patch by "teor".
1306 - New "make test-stem" target to run stem integration tests.
1307 Requires that the "STEM_SOURCE_DIR" environment variable be set.
1308 Closes ticket 14107.
1309 - Make the test_cmdline_args.py script work correctly on Windows.
1310 Patch from Gisle Vanem.
1311 - Move the slower unit tests into a new "./src/test/test-slow"
1312 binary that can be run independently of the other tests. Closes
1314 - Avoid undefined behavior when sampling huge values from the
1315 Laplace distribution. This made unittests fail on Raspberry Pi.
1316 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
1319 Changes in version 0.2.6.2-alpha - 2014-12-31
1320 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
1321 It introduces a major new backend for deciding when to send cells on
1322 channels, which should lead down the road to big performance
1323 increases. It contains security and statistics features for better
1324 work on hidden services, and numerous bugfixes.
1326 This release contains many new unit tests, along with major
1327 performance improvements for running testing networks using Chutney.
1328 Thanks to a series of patches contributed by "teor", testing networks
1329 should now bootstrap in seconds, rather than minutes.
1331 o Major features (relay, infrastructure):
1332 - Complete revision of the code that relays use to decide which cell
1333 to send next. Formerly, we selected the best circuit to write on
1334 each channel, but we didn't select among channels in any
1335 sophisticated way. Now, we choose the best circuits globally from
1336 among those whose channels are ready to deliver traffic.
1338 This patch implements a new inter-cmux comparison API, a global
1339 high/low watermark mechanism and a global scheduler loop for
1340 transmission prioritization across all channels as well as among
1341 circuits on one channel. This schedule is currently tuned to
1342 (tolerantly) avoid making changes in network performance, but it
1343 should form the basis for major circuit performance increases in
1344 the future. Code by Andrea; tuning by Rob Jansen; implements
1347 o Major features (hidden services):
1348 - Make HS port scanning more difficult by immediately closing the
1349 circuit when a user attempts to connect to a nonexistent port.
1350 Closes ticket 13667.
1351 - Add a HiddenServiceStatistics option that allows Tor relays to
1352 gather and publish statistics about the overall size and volume of
1353 hidden service usage. Specifically, when this option is turned on,
1354 an HSDir will publish an approximate number of hidden services
1355 that have published descriptors to it the past 24 hours. Also, if
1356 a relay has acted as a hidden service rendezvous point, it will
1357 publish the approximate amount of rendezvous cells it has relayed
1358 the past 24 hours. The statistics themselves are obfuscated so
1359 that the exact values cannot be derived. For more details see
1360 proposal 238, "Better hidden service stats from Tor relays". This
1361 feature is currently disabled by default. Implements feature 13192.
1363 o Major bugfixes (client, automap):
1364 - Repair automapping with IPv6 addresses. This automapping should
1365 have worked previously, but one piece of debugging code that we
1366 inserted to detect a regression actually caused the regression to
1367 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
1368 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
1371 o Major bugfixes (hidden services):
1372 - When closing an introduction circuit that was opened in parallel
1373 with others, don't mark the introduction point as unreachable.
1374 Previously, the first successful connection to an introduction
1375 point would make the other introduction points get marked as
1376 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
1378 o Directory authority changes:
1379 - Remove turtles as a directory authority.
1380 - Add longclaw as a new (v3) directory authority. This implements
1381 ticket 13296. This keeps the directory authority count at 9.
1383 o Major removed features:
1384 - Tor clients no longer support connecting to hidden services
1385 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
1386 option has been removed. (There shouldn't be any hidden services
1387 running these versions on the network.) Closes ticket 7803.
1389 o Minor features (client):
1390 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
1391 is enabled, reject requests with IP addresses as hostnames.
1392 Resolves ticket 13315.
1394 o Minor features (controller):
1395 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
1396 write an unscheduled heartbeat message to the log. Implements
1399 o Minor features (geoip):
1400 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
1403 o Minor features (hidden services):
1404 - When re-enabling the network, don't try to build introduction
1405 circuits until we have successfully built a circuit. This makes
1406 hidden services come up faster when the network is re-enabled.
1407 Patch from "akwizgran". Closes ticket 13447.
1408 - When we fail to retrieve a hidden service descriptor, send the
1409 controller an "HS_DESC FAILED" controller event. Implements
1411 - New HiddenServiceDirGroupReadable option to cause hidden service
1412 directories and hostname files to be created group-readable. Patch
1413 from "anon", David Stainton, and "meejah". Closes ticket 11291.
1415 o Minor features (systemd):
1416 - Where supported, when running with systemd, report successful
1417 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
1418 - When running with systemd, support systemd watchdog messages. Part
1419 of ticket 11016. Patch by Michael Scherer.
1421 o Minor features (transparent proxy):
1422 - Update the transparent proxy option checks to allow for both ipfw
1423 and pf on OS X. Closes ticket 14002.
1424 - Use the correct option when using IPv6 with transparent proxy
1425 support on Linux. Resolves 13808. Patch by Francisco Blas
1428 o Minor bugfixes (preventative security, C safety):
1429 - When reading a hexadecimal, base-32, or base-64 encoded value from
1430 a string, always overwrite the whole output buffer. This prevents
1431 some bugs where we would look at (but fortunately, not reveal)
1432 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1434 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
1435 just the part that's used. This makes it harder for data leak bugs
1436 to occur in the event of other programming failures. Resolves
1439 o Minor bugfixes (client, microdescriptors):
1440 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
1441 computing which microdescriptors to download. This keeps us from
1442 erroneous download behavior if two microdescriptor digests ever
1443 have the same first 160 bits. Fixes part of bug 13399; bugfix
1445 - Reset a router's status if its microdescriptor digest changes,
1446 even if the first 160 bits remain the same. Fixes part of bug
1447 13399; bugfix on 0.2.3.1-alpha.
1449 o Minor bugfixes (compilation):
1450 - Silence clang warnings under --enable-expensive-hardening,
1451 including implicit truncation of 64 bit values to 32 bit, const
1452 char assignment to self, tautological compare, and additional
1453 parentheses around equality tests. Fixes bug 13577; bugfix
1455 - Fix a clang warning about checking whether an address in the
1456 middle of a structure is NULL. Fixes bug 14001; bugfix
1459 o Minor bugfixes (hidden services):
1460 - Correctly send a controller event when we find that a rendezvous
1461 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
1462 - Pre-check directory permissions for new hidden-services to avoid
1463 at least one case of "Bug: Acting on config options left us in a
1464 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
1465 - When adding a new hidden service (for example, via SETCONF), Tor
1466 no longer congratulates the user for running a relay. Fixes bug
1467 13941; bugfix on 0.2.6.1-alpha.
1468 - When fetching hidden service descriptors, we now check not only
1469 for whether we got the hidden service we had in mind, but also
1470 whether we got the particular descriptors we wanted. This prevents
1471 a class of inefficient but annoying DoS attacks by hidden service
1472 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
1475 o Minor bugfixes (Linux seccomp2 sandbox):
1476 - Make transparent proxy support work along with the seccomp2
1477 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
1478 by Francisco Blas Izquierdo Riera.
1479 - Fix a memory leak in tor-resolve when running with the sandbox
1480 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
1482 o Minor bugfixes (logging):
1483 - Downgrade warnings about RSA signature failures to info log level.
1484 Emit a warning when an extra info document is found incompatible
1485 with a corresponding router descriptor. Fixes bug 9812; bugfix
1487 - Make connection_ap_handshake_attach_circuit() log the circuit ID
1488 correctly. Fixes bug 13701; bugfix on 0.0.6.
1490 o Minor bugfixes (misc):
1491 - Stop allowing invalid address patterns like "*/24" that contain
1492 both a wildcard address and a bit prefix length. This affects all
1493 our address-range parsing code. Fixes bug 7484; bugfix
1496 o Minor bugfixes (testing networks, fast startup):
1497 - Allow Tor to build circuits using a consensus with no exits. If
1498 the consensus has no exits (typical of a bootstrapping test
1499 network), allow Tor to build circuits once enough descriptors have
1500 been downloaded. This assists in bootstrapping a testing Tor
1501 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
1503 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
1504 header to directory servers. This allows us to obtain consensuses
1505 promptly when the consensus interval is very short. This assists
1506 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
1507 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
1508 - Stop assuming that private addresses are local when checking
1509 reachability in a TestingTorNetwork. Instead, when testing, assume
1510 all OR connections are remote. (This is necessary due to many test
1511 scenarios running all relays on localhost.) This assists in
1512 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
1513 0.1.0.1-rc. Patch by "teor".
1514 - Avoid building exit circuits from a consensus with no exits. Now
1515 thanks to our fix for 13718, we accept a no-exit network as not
1516 wholly lost, but we need to remember not to try to build exit
1517 circuits on it. Closes ticket 13814; patch by "teor".
1518 - Stop requiring exits to have non-zero bandwithcapacity in a
1519 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
1520 ignore exit bandwidthcapacity. This assists in bootstrapping a
1521 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
1522 on 0.2.0.3-alpha. Patch by "teor".
1523 - Add "internal" to some bootstrap statuses when no exits are
1524 available. If the consensus does not contain Exits, Tor will only
1525 build internal circuits. In this case, relevant statuses will
1526 contain the word "internal" as indicated in the Tor control-
1527 spec.txt. When bootstrap completes, Tor will be ready to build
1528 internal circuits. If a future consensus contains Exits, exit
1529 circuits may become available. Fixes part of bug 13718; bugfix on
1530 0.2.4.10-alpha. Patch by "teor".
1531 - Decrease minimum consensus interval to 10 seconds when
1532 TestingTorNetwork is set, or 5 seconds for the first consensus.
1533 Fix assumptions throughout the code that assume larger intervals.
1534 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
1536 - Avoid excluding guards from path building in minimal test
1537 networks, when we're in a test network and excluding guards would
1538 exclude all relays. This typically occurs in incredibly small tor
1539 networks, and those using "TestingAuthVoteGuard *". Fixes part of
1540 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
1542 o Code simplification and refactoring:
1543 - Stop using can_complete_circuits as a global variable; access it
1544 with a function instead.
1545 - Avoid using operators directly as macro arguments: this lets us
1546 apply coccinelle transformations to our codebase more directly.
1547 Closes ticket 13172.
1548 - Combine the functions used to parse ClientTransportPlugin and
1549 ServerTransportPlugin into a single function. Closes ticket 6456.
1550 - Add inline functions and convenience macros for inspecting channel
1551 state. Refactor the code to use convenience macros instead of
1552 checking channel state directly. Fixes issue 7356.
1553 - Document all members of was_router_added_t and rename
1554 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
1555 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
1556 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
1557 constant instead of hardcoded value. Fixes issue 13840.
1558 - Refactor our generic strmap and digestmap types into a single
1559 implementation, so that we can add a new digest256map
1563 - Document the bridge-authority-only 'networkstatus-bridges' file.
1564 Closes ticket 13713; patch from "tom".
1565 - Fix typo in PredictedPortsRelevanceTime option description in
1566 manpage. Resolves issue 13707.
1567 - Stop suggesting that users specify relays by nickname: it isn't a
1568 good idea. Also, properly cross-reference how to specify relays in
1569 all parts of manual documenting options that take a list of
1570 relays. Closes ticket 13381.
1571 - Clarify the HiddenServiceDir option description in manpage to make
1572 it clear that relative paths are taken with respect to the current
1573 working directory. Also clarify that this behavior is not
1574 guaranteed to remain indefinitely. Fixes issue 13913.
1577 - New tests for many parts of channel, relay, and circuitmux
1578 functionality. Code by Andrea; part of 9262.
1579 - New tests for parse_transport_line(). Part of ticket 6456.
1580 - In the unit tests, use chgrp() to change the group of the unit
1581 test temporary directory to the current user, so that the sticky
1582 bit doesn't interfere with tests that check directory groups.
1584 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1588 Changes in version 0.2.6.1-alpha - 2014-10-30
1589 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
1590 includes numerous code cleanups and new tests, and fixes a large
1591 number of annoying bugs. Out-of-memory conditions are handled better
1592 than in 0.2.5, pluggable transports have improved proxy support, and
1593 clients now use optimistic data for contacting hidden services. Also,
1594 we are now more robust to changes in what we consider a parseable
1595 directory object, so that tightening restrictions does not have a risk
1596 of introducing infinite download loops.
1598 This is the first alpha release in a new series, so expect there to be
1599 bugs. Users who would rather test out a more stable branch should stay
1600 with 0.2.5.x for now.
1602 o New compiler and system requirements:
1603 - Tor 0.2.6.x requires that your compiler support more of the C99
1604 language standard than before. The 'configure' script now detects
1605 whether your compiler supports C99 mid-block declarations and
1606 designated initializers. If it does not, Tor will not compile.
1608 We may revisit this requirement if it turns out that a significant
1609 number of people need to build Tor with compilers that don't
1610 bother implementing a 15-year-old standard. Closes ticket 13233.
1611 - Tor no longer supports systems without threading support. When we
1612 began working on Tor, there were several systems that didn't have
1613 threads, or where the thread support wasn't able to run the
1614 threads of a single process on multiple CPUs. That no longer
1615 holds: every system where Tor needs to run well now has threading
1616 support. Resolves ticket 12439.
1618 o Removed platform support:
1619 - We no longer include special code to build on Windows CE; as far
1620 as we know, nobody has used Tor on Windows CE in a very long time.
1621 Closes ticket 11446.
1623 o Major features (bridges):
1624 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
1625 transports if they are configured via the "TOR_PT_PROXY"
1626 environment variable. Implements proposal 232. Resolves
1629 o Major features (client performance, hidden services):
1630 - Allow clients to use optimistic data when connecting to a hidden
1631 service, which should remove a round-trip from hidden service
1632 initialization. See proposal 181 for details. Implements
1635 o Major features (directory system):
1636 - Upon receiving an unparseable directory object, if its digest
1637 matches what we expected, then don't try to download it again.
1638 Previously, when we got a descriptor we didn't like, we would keep
1639 trying to download it over and over. Closes ticket 11243.
1641 o Major features (sample torrc):
1642 - Add a new, infrequently-changed "torrc.minimal". This file is
1643 similar to torrc.sample, but it will change as infrequently as
1644 possible, for the benefit of users whose systems prompt them for
1645 intervention whenever a default configuration file is changed.
1646 Making this change allows us to update torrc.sample to be a more
1647 generally useful "sample torrc".
1649 o Major bugfixes (directory authorities):
1650 - Do not assign the HSDir flag to relays if they are not Valid, or
1651 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
1653 o Major bugfixes (directory bandwidth performance):
1654 - Don't flush the zlib buffer aggressively when compressing
1655 directory information for clients. This should save about 7% of
1656 the bandwidth currently used for compressed descriptors and
1657 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
1659 o Minor features (security, memory wiping):
1660 - Ensure we securely wipe keys from memory after
1661 crypto_digest_get_digest and init_curve25519_keypair_from_file
1662 have finished using them. Resolves ticket 13477.
1664 o Minor features (security, out-of-memory handling):
1665 - When handling an out-of-memory condition, allocate less memory for
1666 temporary data structures. Fixes issue 10115.
1667 - When handling an out-of-memory condition, consider more types of
1668 buffers, including those on directory connections, and zlib
1669 buffers. Resolves ticket 11792.
1672 - When identity keypair is generated for first time, log a
1673 congratulatory message that links to the new relay lifecycle
1674 document. Implements feature 10427.
1676 o Minor features (client):
1677 - Clients are now willing to send optimistic data (before they
1678 receive a 'connected' cell) to relays of any version. (Relays
1679 without support for optimistic data are no longer supported on the
1680 Tor network.) Resolves ticket 13153.
1682 o Minor features (directory authorities):
1683 - Don't list relays with a bandwidth estimate of 0 in the consensus.
1684 Implements a feature proposed during discussion of bug 13000.
1685 - In tor-gencert, report an error if the user provides the same
1686 argument more than once.
1687 - If a directory authority can't find a best consensus method in the
1688 votes that it holds, it now falls back to its favorite consensus
1689 method. Previously, it fell back to method 1. Neither of these is
1690 likely to get enough signatures, but "fall back to favorite"
1691 doesn't require us to maintain support an obsolete consensus
1692 method. Implements part of proposal 215.
1694 o Minor features (logging):
1695 - On Unix-like systems, you can now use named pipes as the target of
1696 the Log option, and other options that try to append to files.
1697 Closes ticket 12061. Patch from "carlo von lynX".
1698 - When opening a log file at startup, send it every log message that
1699 we generated between startup and opening it. Previously, log
1700 messages that were generated before opening the log file were only
1701 logged to stdout. Closes ticket 6938.
1702 - Add a TruncateLogFile option to overwrite logs instead of
1703 appending to them. Closes ticket 5583.
1705 o Minor features (portability, Solaris):
1706 - Threads are no longer disabled by default on Solaris; we believe
1707 that the versions of Solaris with broken threading support are all
1708 obsolete by now. Resolves ticket 9495.
1710 o Minor features (relay):
1711 - Re-check our address after we detect a changed IP address from
1712 getsockname(). This ensures that the controller command "GETINFO
1713 address" will report the correct value. Resolves ticket 11582.
1715 - A new AccountingRule option lets Relays set whether they'd like
1716 AccountingMax to be applied separately to inbound and outbound
1717 traffic, or applied to the sum of inbound and outbound traffic.
1718 Resolves ticket 961. Patch by "chobe".
1720 o Minor features (testing networks):
1721 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
1722 the "Exit" flag regardless of their uptime, bandwidth, or exit
1723 policy. TestingTorNetwork must be set for this option to have any
1724 effect. Previously, authorities would take up to 35 minutes to
1725 give nodes the Exit flag in a test network. Partially implements
1728 o Minor features (validation):
1729 - Check all date/time values passed to tor_timegm and
1730 parse_rfc1123_time for validity, taking leap years into account.
1731 Improves HTTP header validation. Implemented with bug 13476.
1732 - In correct_tm(), limit the range of values returned by system
1733 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
1734 This means we don't have to deal with negative or too large dates,
1735 even if a clock is wrong. Otherwise we might fail to read a file
1736 written by us which includes such a date. Fixes bug 13476.
1738 o Minor bugfixes (bridge clients):
1739 - When configured to use a bridge without an identity digest (not
1740 recommended), avoid launching an extra channel to it when
1741 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
1743 o Minor bugfixes (bridges):
1744 - When DisableNetwork is set, do not launch pluggable transport
1745 plugins, and if any are running, terminate them. Fixes bug 13213;
1746 bugfix on 0.2.3.6-alpha.
1748 o Minor bugfixes (C correctness):
1749 - Fix several instances of possible integer overflow/underflow/NaN.
1750 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
1752 - In circuit_build_times_calculate_timeout() in circuitstats.c,
1753 avoid dividing by zero in the pareto calculations. This traps
1754 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
1756 - Fix an integer overflow in format_time_interval(). Fixes bug
1757 13393; bugfix on 0.2.0.10-alpha.
1758 - Set the correct day of year value when the system's localtime(_r)
1759 or gmtime(_r) functions fail to set struct tm. Not externally
1760 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
1761 - Avoid unlikely signed integer overflow in tor_timegm on systems
1762 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
1764 o Minor bugfixes (client):
1765 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
1766 BadExit flag are not considered worthy candidates. Fixes bug
1767 13066; bugfix on 0.1.2.3-alpha.
1768 - Use the consensus schedule for downloading consensuses, and not
1769 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
1770 - Handle unsupported or malformed SOCKS5 requests properly by
1771 responding with the appropriate error message before closing the
1772 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
1774 o Minor bugfixes (client, torrc):
1775 - Stop modifying the value of our DirReqStatistics torrc option just
1776 because we're not a bridge or relay. This bug was causing Tor
1777 Browser users to write "DirReqStatistics 0" in their torrc files
1778 as if they had chosen to change the config. Fixes bug 4244; bugfix
1780 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
1781 that our options have changed every time we SIGHUP. Fixes bug
1782 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
1784 o Minor bugfixes (controller):
1785 - Return an error when the second or later arguments of the
1786 "setevents" controller command are invalid events. Previously we
1787 would return success while silently skipping invalid events. Fixes
1788 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
1790 o Minor bugfixes (directory system):
1791 - Always believe that v3 directory authorities serve extra-info
1792 documents, whether they advertise "caches-extra-info" or not.
1793 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1794 - When running as a v3 directory authority, advertise that you serve
1795 extra-info documents so that clients who want them can find them
1796 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1797 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
1798 Previously, directories offering BRIDGE_DIRINFO and some other
1799 flag (i.e. microdescriptors or extrainfo) would be ignored when
1800 looking for bridges. Partially fixes bug 13163; bugfix
1803 o Minor bugfixes (networking):
1804 - Check for orconns and use connection_or_close_for_error() rather
1805 than connection_mark_for_close() directly in the getsockopt()
1806 failure case of connection_handle_write_impl(). Fixes bug 11302;
1807 bugfix on 0.2.4.4-alpha.
1809 o Minor bugfixes (relay):
1810 - When generating our family list, remove spaces from around the
1811 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
1812 - If our previous bandwidth estimate was 0 bytes, allow publishing a
1813 new relay descriptor immediately. Fixes bug 13000; bugfix
1816 o Minor bugfixes (testing networks):
1817 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
1818 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
1819 - Stop using the default authorities in networks which provide both
1820 AlternateDirAuthority and AlternateBridgeAuthority. Partially
1821 fixes bug 13163; bugfix on 0.2.0.13-alpha.
1823 o Minor bugfixes (testing):
1824 - Stop spawn test failures due to a race condition between the
1825 SIGCHLD handler updating the process status, and the test reading
1826 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
1828 o Minor bugfixes (testing, Windows):
1829 - Avoid passing an extra backslash when creating a temporary
1830 directory for running the unit tests on Windows. Fixes bug 12392;
1831 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
1833 o Minor bugfixes (windows):
1834 - Remove code to special-case handling of NTE_BAD_KEYSET when
1835 acquiring windows CryptoAPI context. This error can't actually
1836 occur for the parameters we're providing. Fixes bug 10816; bugfix
1839 o Minor bugfixes (zlib):
1840 - Avoid truncating a zlib stream when trying to finalize it with an
1841 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
1844 - Allow our configure script to build correctly with autoconf 2.62
1845 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
1846 - Improve the error message from ./configure to make it clear that
1847 when asciidoc has not been found, the user will have to either add
1848 --disable-asciidoc argument or install asciidoc. Resolves
1851 o Code simplification and refactoring:
1852 - Change the entry_is_live() function to take named bitfield
1853 elements instead of an unnamed list of booleans. Closes
1855 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
1856 Resolves ticket 12205.
1857 - Use calloc and reallocarray functions instead of multiply-
1858 then-malloc. This makes it less likely for us to fall victim to an
1859 integer overflow attack when allocating. Resolves ticket 12855.
1860 - Use the standard macro name SIZE_MAX, instead of our
1862 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
1863 functions which take them as arguments. Replace 0 with NO_DIRINFO
1864 in a function call for clarity. Seeks to prevent future issues
1866 - Avoid 4 null pointer errors under clang static analysis by using
1867 tor_assert() to prove that the pointers aren't null. Fixes
1869 - Rework the API of policies_parse_exit_policy() to use a bitmask to
1870 represent parsing options, instead of a confusing mess of
1871 booleans. Resolves ticket 8197.
1872 - Introduce a helper function to parse ExitPolicy in
1873 or_options_t structure.
1876 - Add a doc/TUNING document with tips for handling large numbers of
1877 TCP connections when running busy Tor relay. Update the warning
1878 message to point to this file when running out of sockets
1879 operating system is allowing to use simultaneously. Resolves
1883 - We no longer remind the user about configuration options that have
1884 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
1885 - Remove our old, non-weighted bandwidth-based node selection code.
1886 Previously, we used it as a fallback when we couldn't perform
1887 weighted bandwidth-based node selection. But that would only
1888 happen in the cases where we had no consensus, or when we had a
1889 consensus generated by buggy or ancient directory authorities. In
1890 either case, it's better to use the more modern, better maintained
1891 algorithm, with reasonable defaults for the weights. Closes
1893 - Remove the --disable-curve25519 configure option. Relays and
1894 clients now are required to support curve25519 and the
1896 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
1897 used to be deprecated synonyms for "StrictNodes", are now marked
1898 obsolete. Resolves ticket 12226.
1899 - Clients don't understand the BadDirectory flag in the consensus
1900 anymore, and ignore it.
1903 - Refactor the function that chooses guard nodes so that it can more
1904 easily be tested; write some tests for it.
1905 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
1906 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1907 - Create unit tests for format_time_interval(). With bug 13393.
1908 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1909 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1910 tests (visible) fixes in bug 13476.
1911 - Add a "coverage-html" make target to generate HTML-visualized
1912 coverage results when building with --enable-coverage. (Requires
1913 lcov.) Patch from Kevin Murray.
1914 - Enable the backtrace handler (where supported) when running the
1916 - Revise all unit tests that used the legacy test_* macros to
1917 instead use the recommended tt_* macros. This patch was generated
1918 with coccinelle, to avoid manual errors. Closes ticket 13119.
1920 o Distribution (systemd):
1921 - systemd unit file: only allow tor to write to /var/lib/tor and
1922 /var/log/tor. The rest of the filesystem is accessible for reading
1923 only. Patch by intrigeri; resolves ticket 12751.
1924 - systemd unit file: ensure that the process and all its children
1925 can never gain new privileges. Patch by intrigeri; resolves
1927 - systemd unit file: set up /var/run/tor as writable for the Tor
1928 service. Patch by intrigeri; resolves ticket 13196.
1930 o Removed features (directory authorities):
1931 - Remove code that prevented authorities from listing Tor relays
1932 affected by CVE-2011-2769 as guards. These relays are already
1933 rejected altogether due to the minimum version requirement of
1934 0.2.3.16-alpha. Closes ticket 13152.
1935 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1936 the fingerprints file (approved-routers) has been deprecated.
1937 - Directory authorities do not support being Naming dirauths anymore.
1938 The "NamingAuthoritativeDir" config option is now obsolete.
1939 - Directory authorities do not support giving out the BadDirectory
1941 - Directory authorities no longer advertise or support consensus
1942 methods 1 through 12 inclusive. These consensus methods were
1943 obsolete and/or insecure: maintaining the ability to support them
1944 served no good purpose. Implements part of proposal 215; closes
1947 o Testing (test-network.sh):
1948 - Stop using "echo -n", as some shells' built-in echo doesn't
1949 support "-n". Instead, use "/bin/echo -n". Partially fixes
1951 - Stop an apparent test-network hang when used with make -j2. Fixes
1953 - Add a --delay option to test-network.sh, which configures the
1954 delay before the chutney network tests for data transmission.
1955 Partially implements ticket 13161.
1958 Changes in version 0.2.5.10 - 2014-10-24
1959 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1961 It adds several new security features, including improved
1962 denial-of-service resistance for relays, new compiler hardening
1963 options, and a system-call sandbox for hardened installations on Linux
1964 (requires seccomp2). The controller protocol has several new features,
1965 resolving IPv6 addresses should work better than before, and relays
1966 should be a little more CPU-efficient. We've added support for more
1967 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1968 system and testing infrastructure to allow unit testing of more parts
1969 of the Tor codebase. Finally, we've addressed several nagging pluggable
1970 transport usability issues, and included numerous other small bugfixes
1971 and features mentioned below.
1973 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1974 have accumulated many known flaws; everyone should upgrade.
1976 o Deprecated versions:
1977 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1978 attention for some while.
1981 Changes in version 0.2.5.9-rc - 2014-10-20
1982 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
1983 series. It disables SSL3 in response to the recent "POODLE" attack
1984 (even though POODLE does not affect Tor). It also works around a crash
1985 bug caused by some operating systems' response to the "POODLE" attack
1986 (which does affect Tor). It also contains a few miscellaneous fixes.
1988 o Major security fixes:
1989 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1990 today support TLS 1.0 or later, so we can safely turn off support
1991 for this old (and insecure) protocol. Fixes bug 13426.
1993 o Major bugfixes (openssl bug workaround):
1994 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1995 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1996 13471. This is a workaround for an OpenSSL bug.
1999 - Disable the sandbox name resolver cache when running tor-resolve:
2000 tor-resolve doesn't use the sandbox code, and turning it on was
2001 breaking attempts to do tor-resolve on a non-default server on
2002 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
2004 o Compilation fixes:
2005 - Build and run correctly on systems like OpenBSD-current that have
2006 patched OpenSSL to remove get_cipher_by_char and/or its
2007 implementations. Fixes issue 13325.
2009 o Downgraded warnings:
2010 - Downgrade the severity of the 'unexpected sendme cell from client'
2011 from 'warn' to 'protocol warning'. Closes ticket 8093.
2014 Changes in version 0.2.4.25 - 2014-10-20
2015 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2016 (even though POODLE does not affect Tor). It also works around a crash
2017 bug caused by some operating systems' response to the "POODLE" attack
2018 (which does affect Tor).
2020 o Major security fixes (also in 0.2.5.9-rc):
2021 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2022 today support TLS 1.0 or later, so we can safely turn off support
2023 for this old (and insecure) protocol. Fixes bug 13426.
2025 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2026 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2027 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2028 13471. This is a workaround for an OpenSSL bug.
2031 Changes in version 0.2.5.8-rc - 2014-09-22
2032 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
2033 series. It fixes a bug that affects consistency and speed when
2034 connecting to hidden services, and it updates the location of one of
2035 the directory authorities.
2038 - Clients now send the correct address for their chosen rendezvous
2039 point when trying to access a hidden service. They used to send
2040 the wrong address, which would still work some of the time because
2041 they also sent the identity digest of the rendezvous point, and if
2042 the hidden service happened to try connecting to the rendezvous
2043 point from a relay that already had a connection open to it,
2044 the relay would reuse that connection. Now connections to hidden
2045 services should be more robust and faster. Also, this bug meant
2046 that clients were leaking to the hidden service whether they were
2047 on a little-endian (common) or big-endian (rare) system, which for
2048 some users might have reduced their anonymity. Fixes bug 13151;
2049 bugfix on 0.2.1.5-alpha.
2051 o Directory authority changes:
2052 - Change IP address for gabelmoo (v3 directory authority).
2055 Changes in version 0.2.4.24 - 2014-09-22
2056 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2057 connecting to hidden services, and it updates the location of one of
2058 the directory authorities.
2061 - Clients now send the correct address for their chosen rendezvous
2062 point when trying to access a hidden service. They used to send
2063 the wrong address, which would still work some of the time because
2064 they also sent the identity digest of the rendezvous point, and if
2065 the hidden service happened to try connecting to the rendezvous
2066 point from a relay that already had a connection open to it,
2067 the relay would reuse that connection. Now connections to hidden
2068 services should be more robust and faster. Also, this bug meant
2069 that clients were leaking to the hidden service whether they were
2070 on a little-endian (common) or big-endian (rare) system, which for
2071 some users might have reduced their anonymity. Fixes bug 13151;
2072 bugfix on 0.2.1.5-alpha.
2074 o Directory authority changes:
2075 - Change IP address for gabelmoo (v3 directory authority).
2077 o Minor features (geoip):
2078 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2082 Changes in version 0.2.5.7-rc - 2014-09-11
2083 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
2084 release series, and some long-standing bugs related to ORPort reachability
2085 testing and failure to send CREATE cells. It is the first release
2086 candidate for the Tor 0.2.5.x series.
2088 o Major bugfixes (client, startup):
2089 - Start making circuits as soon as DisabledNetwork is turned off.
2090 When Tor started with DisabledNetwork set, it would correctly
2091 conclude that it shouldn't build circuits, but it would mistakenly
2092 cache this conclusion, and continue believing it even when
2093 DisableNetwork is set to 0. Fixes the bug introduced by the fix
2094 for bug 11200; bugfix on 0.2.5.4-alpha.
2095 - Resume expanding abbreviations for command-line options. The fix
2096 for bug 4647 accidentally removed our hack from bug 586 that
2097 rewrote HashedControlPassword to __HashedControlSessionPassword
2098 when it appears on the commandline (which allowed the user to set
2099 her own HashedControlPassword in the torrc file while the
2100 controller generates a fresh session password for each run). Fixes
2101 bug 12948; bugfix on 0.2.5.1-alpha.
2102 - Warn about attempts to run hidden services and relays in the same
2103 process: that's probably not a good idea. Closes ticket 12908.
2105 o Major bugfixes (relay):
2106 - Avoid queuing or sending destroy cells for circuit ID zero when we
2107 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
2108 Found and fixed by "cypherpunks".
2109 - Fix ORPort reachability detection on relays running behind a
2110 proxy, by correctly updating the "local" mark on the controlling
2111 channel when changing the address of an or_connection_t after the
2112 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
2114 o Minor features (bridge):
2115 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
2116 cookie file for the ExtORPort g+r by default.
2118 o Minor features (geoip):
2119 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2122 o Minor bugfixes (logging):
2123 - Reduce the log severity of the "Pluggable transport proxy does not
2124 provide any needed transports and will not be launched." message,
2125 since Tor Browser includes several ClientTransportPlugin lines in
2126 its torrc-defaults file, leading every Tor Browser user who looks
2127 at her logs to see these notices and wonder if they're dangerous.
2128 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
2129 - Downgrade "Unexpected onionskin length after decryption" warning
2130 to a protocol-warn, since there's nothing relay operators can do
2131 about a client that sends them a malformed create cell. Resolves
2132 bug 12996; bugfix on 0.0.6rc1.
2133 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
2134 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
2135 - When logging information about an EXTEND2 or EXTENDED2 cell, log
2136 their names correctly. Fixes part of bug 12700; bugfix
2138 - When logging information about a relay cell whose command we don't
2139 recognize, log its command as an integer. Fixes part of bug 12700;
2140 bugfix on 0.2.1.10-alpha.
2141 - Escape all strings from the directory connection before logging
2142 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
2144 o Minor bugfixes (controller):
2145 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
2146 bug 12864; bugfix on 0.2.5.1-alpha.
2147 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
2148 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
2151 o Minor bugfixes (compilation):
2152 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
2153 bugfix on 0.2.5.5-alpha.
2154 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
2155 0.2.5.1-alpha. Patch from "NewEraCracker".
2156 - In routerlist_assert_ok(), don't take the address of a
2157 routerinfo's cache_info member unless that routerinfo is non-NULL.
2158 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
2159 - Fix a large number of false positive warnings from the clang
2160 analyzer static analysis tool. This should make real warnings
2161 easier for clang analyzer to find. Patch from "teor". Closes
2164 o Distribution (systemd):
2165 - Verify configuration file via ExecStartPre in the systemd unit
2166 file. Patch from intrigeri; resolves ticket 12730.
2167 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2168 current systemd unit uses "Type = simple", so systemd does not
2169 expect tor to fork. If the user has "RunAsDaemon 1" in their
2170 torrc, then things won't work as expected. This is e.g. the case
2171 on Debian (and derivatives), since there we pass "--defaults-torrc
2172 /usr/share/tor/tor-service-defaults-torrc" (that contains
2173 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2177 - Adjust the URLs in the README to refer to the new locations of
2178 several documents on the website. Fixes bug 12830. Patch from
2180 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
2184 Changes in version 0.2.5.6-alpha - 2014-07-28
2185 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
2186 risk from guard rotation, and fixes a variety of other issues to get
2187 us closer to a release candidate.
2189 o Major features (also in 0.2.4.23):
2190 - Make the number of entry guards configurable via a new
2191 NumEntryGuards consensus parameter, and the number of directory
2192 guards configurable via a new NumDirectoryGuards consensus
2193 parameter. Implements ticket 12688.
2195 o Major bugfixes (also in 0.2.4.23):
2196 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2197 implementation that caused incorrect results on 32-bit
2198 implementations when certain malformed inputs were used along with
2199 a small class of private ntor keys. This bug does not currently
2200 appear to allow an attacker to learn private keys or impersonate a
2201 Tor server, but it could provide a means to distinguish 32-bit Tor
2202 implementations from 64-bit Tor implementations. Fixes bug 12694;
2203 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2207 - Perform circuit cleanup operations even when circuit
2208 construction operations are disabled (because the network is
2209 disabled, or because there isn't enough directory information).
2210 Previously, when we were not building predictive circuits, we
2211 were not closing expired circuits either. Fixes bug 8387; bugfix on
2212 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
2213 became more strict about when we have "enough directory information
2217 - Authorities now assign the Guard flag to the fastest 25% of the
2218 network (it used to be the fastest 50%). Also raise the consensus
2219 weight that guarantees the Guard flag from 250 to 2000. For the
2220 current network, this results in about 1100 guards, down from 2500.
2221 This step paves the way for moving the number of entry guards
2222 down to 1 (proposal 236) while still providing reasonable expected
2223 performance for most users. Implements ticket 12690.
2224 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2226 - Slightly enhance the diagnostic message for bug 12184.
2228 o Minor bugfixes (also in 0.2.4.23):
2229 - Warn and drop the circuit if we receive an inbound 'relay early'
2230 cell. Those used to be normal to receive on hidden service circuits
2231 due to bug 1038, but the buggy Tor versions are long gone from
2232 the network so we can afford to resume watching for them. Resolves
2233 the rest of bug 1038; bugfix on 0.2.1.19.
2234 - Correct a confusing error message when trying to extend a circuit
2235 via the control protocol but we don't know a descriptor or
2236 microdescriptor for one of the specified relays. Fixes bug 12718;
2237 bugfix on 0.2.3.1-alpha.
2240 - Fix compilation when building with bufferevents enabled. (This
2241 configuration is still not expected to work, however.)
2242 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
2243 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
2245 - Compile correctly with builds and forks of OpenSSL (such as
2246 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
2247 0.2.1.1-alpha. Patch from "dhill".
2250 Changes in version 0.2.4.23 - 2014-07-28
2251 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
2252 guard rotation, and also backports several important fixes from the
2253 Tor 0.2.5 alpha release series.
2256 - Clients now look at the "usecreatefast" consensus parameter to
2257 decide whether to use CREATE_FAST or CREATE cells for the first hop
2258 of their circuit. This approach can improve security on connections
2259 where Tor's circuit handshake is stronger than the available TLS
2260 connection security levels, but the tradeoff is more computational
2261 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2262 - Make the number of entry guards configurable via a new
2263 NumEntryGuards consensus parameter, and the number of directory
2264 guards configurable via a new NumDirectoryGuards consensus
2265 parameter. Implements ticket 12688.
2268 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2269 implementation that caused incorrect results on 32-bit
2270 implementations when certain malformed inputs were used along with
2271 a small class of private ntor keys. This bug does not currently
2272 appear to allow an attacker to learn private keys or impersonate a
2273 Tor server, but it could provide a means to distinguish 32-bit Tor
2274 implementations from 64-bit Tor implementations. Fixes bug 12694;
2275 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2279 - Warn and drop the circuit if we receive an inbound 'relay early'
2280 cell. Those used to be normal to receive on hidden service circuits
2281 due to bug 1038, but the buggy Tor versions are long gone from
2282 the network so we can afford to resume watching for them. Resolves
2283 the rest of bug 1038; bugfix on 0.2.1.19.
2284 - Correct a confusing error message when trying to extend a circuit
2285 via the control protocol but we don't know a descriptor or
2286 microdescriptor for one of the specified relays. Fixes bug 12718;
2287 bugfix on 0.2.3.1-alpha.
2288 - Avoid an illegal read from stack when initializing the TLS
2289 module using a version of OpenSSL without all of the ciphers
2290 used by the v2 link handshake. Fixes bug 12227; bugfix on
2291 0.2.4.8-alpha. Found by "starlight".
2294 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2298 Changes in version 0.2.5.5-alpha - 2014-06-18
2299 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
2300 0.2.5.x release series, including a couple of DoS issues, some
2301 performance regressions, a large number of bugs affecting the Linux
2302 seccomp2 sandbox code, and various other bugfixes. It also adds
2303 diagnostic bugfixes for a few tricky issues that we're trying to
2306 o Major features (security, traffic analysis resistance):
2307 - Several major improvements to the algorithm used to decide when to
2308 close TLS connections. Previous versions of Tor closed connections
2309 at a fixed interval after the last time a non-padding cell was
2310 sent over the connection, regardless of the target of the
2311 connection. Now, we randomize the intervals by adding up to 50% of
2312 their base value, we measure the length of time since connection
2313 last had at least one circuit, and we allow connections to known
2314 ORs to remain open a little longer (15 minutes instead of 3
2315 minutes minimum). These changes should improve Tor's resistance
2316 against some kinds of traffic analysis, and lower some overhead
2317 from needlessly closed connections. Fixes ticket 6799.
2318 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
2320 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
2321 - Fix a memory leak that could occur if a microdescriptor parse
2322 fails during the tokenizing step. This bug could enable a memory
2323 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2326 o Major bugfixes (security, directory authorities):
2327 - Directory authorities now include a digest of each relay's
2328 identity key as a part of its microdescriptor.
2330 This is a workaround for bug 11743 (reported by "cypherpunks"),
2331 where Tor clients do not support receiving multiple
2332 microdescriptors with the same SHA256 digest in the same
2333 consensus. When clients receive a consensus like this, they only
2334 use one of the relays. Without this fix, a hostile relay could
2335 selectively disable some client use of target relays by
2336 constructing a router descriptor with a different identity and the
2337 same microdescriptor parameters and getting the authorities to
2338 list it in a microdescriptor consensus. This fix prevents an
2339 attacker from causing a microdescriptor collision, because the
2340 router's identity is not forgeable.
2342 o Major bugfixes (relay):
2343 - Use a direct dirport connection when uploading non-anonymous
2344 descriptors to the directory authorities. Previously, relays would
2345 incorrectly use tunnel connections under a fairly wide variety of
2346 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
2347 - When a circuit accidentally has the same circuit ID for its
2348 forward and reverse direction, correctly detect the direction of
2349 cells using that circuit. Previously, this bug made roughly one
2350 circuit in a million non-functional. Fixes bug 12195; this is a
2351 bugfix on every version of Tor.
2353 o Major bugfixes (client, pluggable transports):
2354 - When managing pluggable transports, use OS notification facilities
2355 to learn if they have crashed, and don't attempt to kill any
2356 process that has already exited. Fixes bug 8746; bugfix
2359 o Minor features (diagnostic):
2360 - When logging a warning because of bug 7164, additionally check the
2361 hash table for consistency (as proposed on ticket 11737). This may
2362 help diagnose bug 7164.
2363 - When we log a heartbeat, log how many one-hop circuits we have
2364 that are at least 30 minutes old, and log status information about
2365 a few of them. This is an attempt to track down bug 8387.
2366 - When encountering an unexpected CR while writing text to a file on
2367 Windows, log the name of the file. Should help diagnosing
2369 - Give more specific warnings when a client notices that an onion
2370 handshake has failed. Fixes ticket 9635.
2371 - Add significant new logging code to attempt to diagnose bug 12184,
2372 where relays seem to run out of available circuit IDs.
2373 - Improve the diagnostic log message for bug 8387 even further to
2374 try to improve our odds of figuring out why one-hop directory
2375 circuits sometimes do not get closed.
2377 o Minor features (security, memory management):
2378 - Memory allocation tricks (mempools and buffer freelists) are now
2379 disabled by default. You can turn them back on with
2380 --enable-mempools and --enable-buf-freelists respectively. We're
2381 disabling these features because malloc performance is good enough
2382 on most platforms, and a similar feature in OpenSSL exacerbated
2383 exploitation of the Heartbleed attack. Resolves ticket 11476.
2385 o Minor features (security):
2386 - Apply the secure SipHash-2-4 function to the hash table mapping
2387 circuit IDs and channels to circuits. We missed this one when we
2388 were converting all the other hash functions to use SipHash back
2389 in 0.2.5.3-alpha. Resolves ticket 11750.
2391 o Minor features (build):
2392 - The configure script has a --disable-seccomp option to turn off
2393 support for libseccomp on systems that have it, in case it (or
2394 Tor's use of it) is broken. Resolves ticket 11628.
2396 o Minor features (other):
2397 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
2400 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
2401 - When running a hidden service, do not allow TunneledDirConns 0;
2402 this will keep the hidden service from running, and also
2403 make it publish its descriptors directly over HTTP. Fixes bug 10849;
2404 bugfix on 0.2.1.1-alpha.
2406 o Minor bugfixes (performance):
2407 - Avoid a bug where every successful connection made us recompute
2408 the flag telling us whether we have sufficient information to
2409 build circuits. Previously, we would forget our cached value
2410 whenever we successfully opened a channel (or marked a router as
2411 running or not running for any other reason), regardless of
2412 whether we had previously believed the router to be running. This
2413 forced us to run an expensive update operation far too often.
2414 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
2415 - Avoid using tor_memeq() for checking relay cell integrity. This
2416 removes a possible performance bottleneck. Fixes part of bug
2417 12169; bugfix on 0.2.1.31.
2419 o Minor bugfixes (compilation):
2420 - Fix compilation of test_status.c when building with MVSC. Bugfix
2421 on 0.2.5.4-alpha. Patch from Gisle Vanem.
2422 - Resolve GCC complaints on OpenBSD about discarding constness in
2423 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
2424 on 0.1.1.23. Patch from Dana Koch.
2425 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
2426 treatment of long and time_t as comparable types. Fixes part of
2427 bug 11633. Patch from Dana Koch.
2428 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
2429 11623; bugfix on 0.2.5.3-alpha.
2430 - When deciding whether to build the 64-bit curve25519
2431 implementation, detect platforms where we can compile 128-bit
2432 arithmetic but cannot link it. Fixes bug 11729; bugfix on
2433 0.2.4.8-alpha. Patch from "conradev".
2434 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
2435 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
2436 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
2439 o Minor bugfixes (Directory server):
2440 - When sending a compressed set of descriptors or microdescriptors,
2441 make sure to finalize the zlib stream. Previously, we would write
2442 all the compressed data, but if the last descriptor we wanted to
2443 send was missing or too old, we would not mark the stream as
2444 finished. This caused problems for decompression tools. Fixes bug
2445 11648; bugfix on 0.1.1.23.
2447 o Minor bugfixes (Linux seccomp sandbox):
2448 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
2449 11622; bugfix on 0.2.5.1-alpha.
2450 - Avoid crashing when re-opening listener ports with the seccomp
2451 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
2452 - Avoid crashing with the seccomp sandbox enabled along with
2453 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
2454 - When we receive a SIGHUP with the sandbox enabled, correctly
2455 support rotating our log files. Fixes bug 12032; bugfix
2457 - Avoid crash when running with sandboxing enabled and
2458 DirReqStatistics not disabled. Fixes bug 12035; bugfix
2460 - Fix a "BUG" warning when trying to write bridge-stats files with
2461 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
2463 - Prevent the sandbox from crashing on startup when run with the
2464 --enable-expensive-hardening configuration option. Fixes bug
2465 11477; bugfix on 0.2.5.4-alpha.
2466 - When running with DirPortFrontPage and sandboxing both enabled,
2467 reload the DirPortFrontPage correctly when restarting. Fixes bug
2468 12028; bugfix on 0.2.5.1-alpha.
2469 - Don't try to enable the sandbox when using the Tor binary to check
2470 its configuration, hash a passphrase, or so on. Doing so was
2471 crashing on startup for some users. Fixes bug 11609; bugfix
2473 - Avoid warnings when running with sandboxing and node statistics
2474 enabled at the same time. Fixes part of 12064; bugfix on
2475 0.2.5.1-alpha. Patch from Michael Wolf.
2476 - Avoid warnings when running with sandboxing enabled at the same
2477 time as cookie authentication, hidden services, or directory
2478 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
2479 - Do not allow options that require calls to exec to be enabled
2480 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
2481 bug 12043; bugfix on 0.2.5.1-alpha.
2482 - Handle failures in getpwnam()/getpwuid() when running with the
2483 User option set and the Linux syscall sandbox enabled. Fixes bug
2484 11946; bugfix on 0.2.5.1-alpha.
2485 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
2486 to avoid calling getaddrinfo() after installing the sandbox
2487 filters. Previously, it preloaded a cache with the IPv4 address
2488 for our hostname, and nothing else. Now, it loads the cache with
2489 every address that it used to initialize the Tor process. Fixes
2490 bug 11970; bugfix on 0.2.5.1-alpha.
2492 o Minor bugfixes (pluggable transports):
2493 - Enable the ExtORPortCookieAuthFile option, to allow changing the
2494 default location of the authentication token for the extended OR
2495 Port as used by sever-side pluggable transports. We had
2496 implemented this option before, but the code to make it settable
2497 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
2498 - Avoid another 60-second delay when starting Tor in a pluggable-
2499 transport-using configuration when we already have cached
2500 descriptors for our bridges. Fixes bug 11965; bugfix
2503 o Minor bugfixes (client):
2504 - Avoid "Tried to open a socket with DisableNetwork set" warnings
2505 when starting a client with bridges configured and DisableNetwork
2506 set. (Tor launcher starts Tor with DisableNetwork set the first
2507 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
2509 o Minor bugfixes (testing):
2510 - The Python parts of the test scripts now work on Python 3 as well
2511 as Python 2, so systems where '/usr/bin/python' is Python 3 will
2512 no longer have the tests break. Fixes bug 11608; bugfix
2514 - When looking for versions of python that we could run the tests
2515 with, check for "python2.7" and "python3.3"; previously we were
2516 only looking for "python", "python2", and "python3". Patch from
2517 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
2518 - Fix all valgrind warnings produced by the unit tests. There were
2519 over a thousand memory leak warnings previously, mostly produced
2520 by forgetting to free things in the unit test code. Fixes bug
2521 11618, bugfixes on many versions of Tor.
2523 o Minor bugfixes (tor-fw-helper):
2524 - Give a correct log message when tor-fw-helper fails to launch.
2525 (Previously, we would say something like "tor-fw-helper sent us a
2526 string we could not parse".) Fixes bug 9781; bugfix
2529 o Minor bugfixes (relay, threading):
2530 - Check return code on spawn_func() in cpuworker code, so that we
2531 don't think we've spawned a nonworking cpuworker and write junk to
2532 it forever. Fix related to bug 4345; bugfix on all released Tor
2533 versions. Found by "skruffy".
2534 - Use a pthread_attr to make sure that spawn_func() cannot return an
2535 error while at the same time launching a thread. Fix related to
2536 bug 4345; bugfix on all released Tor versions. Reported
2539 o Minor bugfixes (relay, oom prevention):
2540 - Correctly detect the total available system memory. We tried to do
2541 this in 0.2.5.4-alpha, but the code was set up to always return an
2542 error value, even on success. Fixes bug 11805; bugfix
2545 o Minor bugfixes (relay, other):
2546 - We now drop CREATE cells for already-existent circuit IDs and for
2547 zero-valued circuit IDs, regardless of other factors that might
2548 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
2550 - Avoid an illegal read from stack when initializing the TLS module
2551 using a version of OpenSSL without all of the ciphers used by the
2552 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
2554 - When rejecting DATA cells for stream_id zero, still count them
2555 against the circuit's deliver window so that we don't fail to send
2556 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
2558 o Minor bugfixes (logging):
2559 - Fix a misformatted log message about delayed directory fetches.
2560 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
2561 - Squelch a spurious LD_BUG message "No origin circuit for
2562 successful SOCKS stream" in certain hidden service failure cases;
2566 - Include a tor.service file in contrib/dist for use with systemd.
2567 Some distributions will be able to use this file unmodified;
2568 others will need to tweak it, or write their own. Patch from Jamie
2569 Nguyen; resolves ticket 8368.
2572 - Clean up several option names in the manpage to match their real
2573 names, add the missing documentation for a couple of testing and
2574 directory authority options, remove the documentation for a
2575 V2-directory fetching option that no longer exists. Resolves
2577 - Correct the documenation so that it lists the correct directory
2578 for the stats files. (They are in a subdirectory called "stats",
2580 - In the manpage, move more authority-only options into the
2581 directory authority section so that operators of regular directory
2582 caches don't get confused.
2585 - The contrib directory has been sorted and tidied. Before, it was
2586 an unsorted dumping ground for useful and not-so-useful things.
2587 Now, it is divided based on functionality, and the items which
2588 seemed to be nonfunctional or useless have been removed. Resolves
2589 ticket 8966; based on patches from "rl1987".
2592 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2593 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
2594 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2595 exist; tunneled directory connections have been available since
2596 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2597 brute-force fix for 10849, where "TunnelDirConns 0" would break
2601 Changes in version 0.2.4.22 - 2014-05-16
2602 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
2603 alpha release series. These include blocking all authority signing
2604 keys that may have been affected by the OpenSSL "heartbleed" bug,
2605 choosing a far more secure set of TLS ciphersuites by default, closing
2606 a couple of memory leaks that could be used to run a target relay out
2607 of RAM, and several others.
2609 o Major features (security, backport from 0.2.5.4-alpha):
2610 - Block authority signing keys that were used on authorities
2611 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2612 don't have any evidence that these keys _were_ compromised; we're
2613 doing this to be prudent.) Resolves ticket 11464.
2615 o Major bugfixes (security, OOM):
2616 - Fix a memory leak that could occur if a microdescriptor parse
2617 fails during the tokenizing step. This bug could enable a memory
2618 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2621 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
2622 - The relay ciphersuite list is now generated automatically based on
2623 uniform criteria, and includes all OpenSSL ciphersuites with
2624 acceptable strength and forward secrecy. Previously, we had left
2625 some perfectly fine ciphersuites unsupported due to omission or
2626 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2627 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2628 - Relays now trust themselves to have a better view than clients of
2629 which TLS ciphersuites are better than others. (Thanks to bug
2630 11513, the relay list is now well-considered, whereas the client
2631 list has been chosen mainly for anti-fingerprinting purposes.)
2632 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2633 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2634 AES128. Resolves ticket 11528.
2635 - Clients now try to advertise the same list of ciphersuites as
2636 Firefox 28. This change enables selection of (fast) GCM
2637 ciphersuites, disables some strange old ciphers, and stops
2638 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2639 Resolves ticket 11438.
2641 o Minor bugfixes (configuration, security):
2642 - When running a hidden service, do not allow TunneledDirConns 0:
2643 trying to set that option together with a hidden service would
2644 otherwise prevent the hidden service from running, and also make
2645 it publish its descriptors directly over HTTP. Fixes bug 10849;
2646 bugfix on 0.2.1.1-alpha.
2648 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
2649 - Avoid sending a garbage value to the controller when a circuit is
2650 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2652 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
2653 - Stop leaking memory when we successfully resolve a PTR record.
2654 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2656 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
2657 - Avoid 60-second delays in the bootstrapping process when Tor is
2658 launching for a second time while using bridges. Fixes bug 9229;
2659 bugfix on 0.2.0.3-alpha.
2661 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
2662 - Give the correct URL in the warning message when trying to run a
2663 relay on an ancient version of Windows. Fixes bug 9393.
2665 o Minor bugfixes (compilation):
2666 - Fix a compilation error when compiling with --disable-curve25519.
2667 Fixes bug 9700; bugfix on 0.2.4.17-rc.
2670 - Downgrade the warning severity for the the "md was still
2671 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
2672 for trying to diagnose this bug, and the current warning in
2673 earlier versions of tor achieves nothing useful. Addresses warning
2676 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
2677 - When we run out of usable circuit IDs on a channel, log only one
2678 warning for the whole channel, and describe how many circuits
2679 there were on the channel. Fixes part of ticket 11553.
2681 o Minor features (security, backport from 0.2.5.4-alpha):
2682 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
2683 leave the default at 8GBytes), to better support Raspberry Pi
2684 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
2686 o Documentation (backport from 0.2.5.4-alpha):
2687 - Correctly document that we search for a system torrc file before
2688 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2692 Changes in version 0.2.5.4-alpha - 2014-04-25
2693 Tor 0.2.5.4-alpha includes several security and performance
2694 improvements for clients and relays, including blacklisting authority
2695 signing keys that were used while susceptible to the OpenSSL
2696 "heartbleed" bug, fixing two expensive functions on busy relays,
2697 improved TLS ciphersuite preference lists, support for run-time
2698 hardening on compilers that support AddressSanitizer, and more work on
2699 the Linux sandbox code.
2701 There are also several usability fixes for clients (especially clients
2702 that use bridges), two new TransPort protocols supported (one on
2703 OpenBSD, one on FreeBSD), and various other bugfixes.
2705 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
2706 have accumulated many known flaws; everyone should upgrade.
2708 o Major features (security):
2709 - If you don't specify MaxMemInQueues yourself, Tor now tries to
2710 pick a good value based on your total system memory. Previously,
2711 the default was always 8 GB. You can still override the default by
2712 setting MaxMemInQueues yourself. Resolves ticket 11396.
2713 - Block authority signing keys that were used on authorities
2714 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2715 don't have any evidence that these keys _were_ compromised; we're
2716 doing this to be prudent.) Resolves ticket 11464.
2718 o Major features (relay performance):
2719 - Speed up server-side lookups of rendezvous and introduction point
2720 circuits by using hashtables instead of linear searches. These
2721 functions previously accounted between 3 and 7% of CPU usage on
2722 some busy relays. Resolves ticket 9841.
2723 - Avoid wasting CPU when extending a circuit over a channel that is
2724 nearly out of circuit IDs. Previously, we would do a linear scan
2725 over possible circuit IDs before finding one or deciding that we
2726 had exhausted our possibilities. Now, we try at most 64 random
2727 circuit IDs before deciding that we probably won't succeed. Fixes
2728 a possible root cause of ticket 11553.
2730 o Major features (seccomp2 sandbox, Linux only):
2731 - The seccomp2 sandbox can now run a test network for multiple hours
2732 without crashing. The sandbox is still experimental, and more bugs
2733 will probably turn up. To try it, enable "Sandbox 1" on a Linux
2734 host. Resolves ticket 11351.
2735 - Strengthen sandbox code: the sandbox can now test the arguments
2736 for rename(), and blocks _sysctl() entirely. Resolves another part
2738 - When the sandbox blocks a system call, it now tries to log a stack
2739 trace before exiting. Resolves ticket 11465.
2741 o Major bugfixes (TLS cipher selection):
2742 - The relay ciphersuite list is now generated automatically based on
2743 uniform criteria, and includes all OpenSSL ciphersuites with
2744 acceptable strength and forward secrecy. Previously, we had left
2745 some perfectly fine ciphersuites unsupported due to omission or
2746 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2747 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2748 - Relays now trust themselves to have a better view than clients of
2749 which TLS ciphersuites are better than others. (Thanks to bug
2750 11513, the relay list is now well-considered, whereas the client
2751 list has been chosen mainly for anti-fingerprinting purposes.)
2752 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2753 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2754 AES128. Resolves ticket 11528.
2755 - Clients now try to advertise the same list of ciphersuites as
2756 Firefox 28. This change enables selection of (fast) GCM
2757 ciphersuites, disables some strange old ciphers, and stops
2758 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2759 Resolves ticket 11438.
2761 o Major bugfixes (bridge client):
2762 - Avoid 60-second delays in the bootstrapping process when Tor is
2763 launching for a second time while using bridges. Fixes bug 9229;
2764 bugfix on 0.2.0.3-alpha.
2766 o Minor features (transparent proxy, *BSD):
2767 - Support FreeBSD's ipfw firewall interface for TransPort ports on
2768 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
2769 10267; patch from "yurivict".
2770 - Support OpenBSD's divert-to rules with the pf firewall for
2771 transparent proxy ports. To enable it, set "TransProxyType
2772 pf-divert". This allows Tor to run a TransPort transparent proxy
2773 port on OpenBSD 4.4 or later without root privileges. See the
2774 pf.conf(5) manual page for information on configuring pf to use
2775 divert-to rules. Closes ticket 10896; patch from Dana Koch.
2777 o Minor features (security):
2778 - New --enable-expensive-hardening option to enable security
2779 hardening options that consume nontrivial amounts of CPU and
2780 memory. Right now, this includes AddressSanitizer and UbSan, which
2781 are supported in newer versions of GCC and Clang. Closes ticket
2784 o Minor features (log verbosity):
2785 - Demote the message that we give when a flushing connection times
2786 out for too long from NOTICE to INFO. It was usually meaningless.
2787 Resolves ticket 5286.
2788 - Don't log so many notice-level bootstrapping messages at startup
2789 about downloading descriptors. Previously, we'd log a notice
2790 whenever we learned about more routers. Now, we only log a notice
2791 at every 5% of progress. Fixes bug 9963.
2792 - Warn less verbosely when receiving a malformed
2793 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
2794 - When we run out of usable circuit IDs on a channel, log only one
2795 warning for the whole channel, and describe how many circuits
2796 there were on the channel. Fixes part of ticket 11553.
2798 o Minor features (relay):
2799 - If a circuit timed out for at least 3 minutes, check if we have a
2800 new external IP address, and publish a new descriptor with the new
2801 IP address if it changed. Resolves ticket 2454.
2803 o Minor features (controller):
2804 - Make the entire exit policy available from the control port via
2805 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
2807 - Because of the fix for ticket 11396, the real limit for memory
2808 usage may no longer match the configured MaxMemInQueues value. The
2809 real limit is now exposed via GETINFO limits/max-mem-in-queues.
2811 o Minor features (bridge client):
2812 - Report a more useful failure message when we can't connect to a
2813 bridge because we don't have the right pluggable transport
2814 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
2816 o Minor features (diagnostic):
2817 - Add more log messages to diagnose bug 7164, which causes
2818 intermittent "microdesc_free() called but md was still referenced"
2819 warnings. We now include more information, to figure out why we
2820 might be cleaning a microdescriptor for being too old if it's
2821 still referenced by a live node_t object.
2823 o Minor bugfixes (client, DNSPort):
2824 - When using DNSPort, try to respond to AAAA requests with AAAA
2825 answers. Previously, we hadn't looked at the request type when
2826 deciding which answer type to prefer. Fixes bug 10468; bugfix on
2828 - When receiving a DNS query for an unsupported record type, reply
2829 with no answer rather than with a NOTIMPL error. This behavior
2830 isn't correct either, but it will break fewer client programs, we
2831 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
2834 o Minor bugfixes (exit relay):
2835 - Stop leaking memory when we successfully resolve a PTR record.
2836 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2838 o Minor bugfixes (bridge client):
2839 - Stop accepting bridge lines containing hostnames. Doing so would
2840 cause clients to perform DNS requests on the hostnames, which was
2841 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
2842 - Avoid a 60-second delay in the bootstrapping process when a Tor
2843 client with pluggable transports re-reads its configuration at
2844 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
2846 o Minor bugfixes (client, logging during bootstrap):
2847 - Warn only once if we start logging in an unsafe way. Previously,
2848 we complain as many times as we had problems. Fixes bug 9870;
2849 bugfix on 0.2.5.1-alpha.
2850 - Only report the first fatal bootstrap error on a given OR
2851 connection. This stops us from telling the controller bogus error
2852 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
2853 - Be more helpful when trying to run sandboxed on Linux without
2854 libseccomp. Instead of saying "Sandbox is not implemented on this
2855 platform", we now explain that we need to be built with
2856 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
2857 - Avoid generating spurious warnings when starting with
2858 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
2861 o Minor bugfixes (closing OR connections):
2862 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
2863 check if it's an or_connection_t and correctly call
2864 connection_or_close_for_error() rather than
2865 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
2867 - When closing all connections on setting DisableNetwork to 1, use
2868 connection_or_close_normally() rather than closing OR connections
2869 out from under the channel layer. Fixes bug 11306; bugfix on
2872 o Minor bugfixes (controller):
2873 - Avoid sending a garbage value to the controller when a circuit is
2874 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2876 o Minor bugfixes (tor-fw-helper):
2877 - Allow tor-fw-helper to build again by adding src/ext to its
2878 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
2880 o Minor bugfixes (bridges):
2881 - Avoid potential crashes or bad behavior when launching a
2882 server-side managed proxy with ORPort or ExtORPort temporarily
2883 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
2885 o Minor bugfixes (platform-specific):
2886 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
2887 bug 11426; bugfix on 0.2.5.3-alpha.
2888 - When dumping a malformed directory object to disk, save it in
2889 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
2891 - Don't report failures from make_socket_reuseable() on incoming
2892 sockets on OSX: this can happen when incoming connections close
2893 early. Fixes bug 10081.
2895 o Minor bugfixes (trivial memory leaks):
2896 - Fix a small memory leak when signing a directory object. Fixes bug
2897 11275; bugfix on 0.2.4.13-alpha.
2898 - Free placeholder entries in our circuit table at exit; fixes a
2899 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
2900 - Don't re-initialize a second set of OpenSSL mutexes when starting
2901 up. Previously, we'd make one set of mutexes, and then immediately
2902 replace them with another. Fixes bug 11726; bugfix on
2904 - Resolve some memory leaks found by coverity in the unit tests, on
2905 exit in tor-gencert, and on a failure to compute digests for our
2906 own keys when generating a v3 networkstatus vote. These leaks
2907 should never have affected anyone in practice.
2909 o Minor bugfixes (hidden service):
2910 - Only retry attempts to connect to a chosen rendezvous point 8
2911 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
2913 o Minor bugfixes (misc code correctness):
2914 - Fix various instances of undefined behavior in channeltls.c,
2915 tor_memmem(), and eventdns.c that would cause us to construct
2916 pointers to memory outside an allocated object. (These invalid
2917 pointers were not accessed, but C does not even allow them to
2918 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
2919 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
2920 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
2921 fix some miscellaneous errors in our tests and codebase. Fixes bug
2922 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
2923 - Always check return values for unlink, munmap, UnmapViewOfFile;
2924 check strftime return values more often. In some cases all we can
2925 do is report a warning, but this may help prevent deeper bugs from
2926 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
2928 - Fix numerous warnings from the clang "scan-build" static analyzer.
2929 Some of these are programming style issues; some of them are false
2930 positives that indicated awkward code; some are undefined behavior
2931 cases related to constructing (but not using) invalid pointers;
2932 some are assumptions about API behavior; some are (harmlessly)
2933 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
2934 correct; and one or two are genuine bugs that weren't reachable
2935 from the rest of the program. Fixes bug 8793; bugfixes on many,
2939 - Build the torify.1 manpage again. Previously, we were only trying
2940 to build it when also building tor-fw-helper. That's why we didn't
2941 notice that we'd broken the ability to build it. Fixes bug 11321;
2942 bugfix on 0.2.5.1-alpha.
2943 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
2944 11061; bugfix on 0.2.4.7-alpha.
2945 - Correctly document that we search for a system torrc file before
2946 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2948 - Resolve warnings from Doxygen.
2950 o Code simplifications and refactoring:
2951 - Remove is_internal_IP() function. Resolves ticket 4645.
2952 - Remove unused function circuit_dump_by_chan from circuitlist.c.
2953 Closes issue 9107; patch from "marek".
2954 - Change our use of the ENUM_BF macro to avoid declarations that
2957 o Deprecated versions:
2958 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
2959 attention for some while. Directory authorities no longer accept
2960 descriptors from relays running any version of Tor prior to Tor
2961 0.2.3.16-alpha. Resolves ticket 11149.
2964 - New macros in test.h to simplify writing mock-functions for unit
2965 tests. Part of ticket 11507. Patch from Dana Koch.
2966 - Complete tests for the status.c module. Resolves ticket 11507.
2967 Patch from Dana Koch.
2970 - Remove all code for the long unused v1 directory protocol.
2971 Resolves ticket 11070.
2974 Changes in version 0.2.5.3-alpha - 2014-03-22
2975 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
2976 two new anti-DoS features for Tor relays, resolves a bug that kept
2977 SOCKS5 support for IPv6 from working, fixes several annoying usability
2978 issues for bridge users, and removes more old code for unused
2981 The Tor 0.2.5.x release series is now in patch-freeze: no feature
2982 patches not already written will be considered for inclusion in 0.2.5.x.
2984 o Major features (relay security, DoS-resistance):
2985 - When deciding whether we have run out of memory and we need to
2986 close circuits, also consider memory allocated in buffers for
2987 streams attached to each circuit.
2989 This change, which extends an anti-DoS feature introduced in
2990 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2991 better resist more memory-based DoS attacks than before. Since the
2992 MaxMemInCellQueues option now applies to all queues, it is renamed
2993 to MaxMemInQueues. This feature fixes bug 10169.
2994 - Avoid hash-flooding denial-of-service attacks by using the secure
2995 SipHash-2-4 hash function for our hashtables. Without this
2996 feature, an attacker could degrade performance of a targeted
2997 client or server by flooding their data structures with a large
2998 number of entries to be stored at the same hash table position,
2999 thereby slowing down the Tor instance. With this feature, hash
3000 table positions are derived from a randomized cryptographic key,
3001 and an attacker cannot predict which entries will collide. Closes
3003 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
3004 the default at 8GBytes), to better support Raspberry Pi users. Fixes
3005 bug 9686; bugfix on 0.2.4.14-alpha.
3007 o Minor features (bridges, pluggable transports):
3008 - Bridges now write the SHA1 digest of their identity key
3009 fingerprint (that is, a hash of a hash of their public key) to
3010 notice-level logs, and to a new hashed-fingerprint file. This
3011 information will help bridge operators look up their bridge in
3012 Globe and similar tools. Resolves ticket 10884.
3013 - Improve the message that Tor displays when running as a bridge
3014 using pluggable transports without an Extended ORPort listener.
3015 Also, log the message in the log file too. Resolves ticket 11043.
3017 o Minor features (other):
3018 - Add a new option, PredictedPortsRelevanceTime, to control how long
3019 after having received a request to connect to a given port Tor
3020 will try to keep circuits ready in anticipation of future requests
3021 for that port. Patch from "unixninja92"; implements ticket 9176.
3022 - Generate a warning if any ports are listed in the SocksPolicy,
3023 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
3024 AuthDirBadExit options. (These options only support address
3025 ranges.) Fixes part of ticket 11108.
3026 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
3029 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
3030 - Build without warnings under clang 3.4. (We have some macros that
3031 define static functions only some of which will get used later in
3032 the module. Starting with clang 3.4, these give a warning unless the
3033 unused attribute is set on them.) Resolves ticket 10904.
3034 - Fix build warnings about missing "a2x" comment when building the
3035 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3036 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3038 o Minor bugfixes (client):
3039 - Improve the log message when we can't connect to a hidden service
3040 because all of the hidden service directory nodes hosting its
3041 descriptor are excluded. Improves on our fix for bug 10722, which
3042 was a bugfix on 0.2.0.10-alpha.
3043 - Raise a control port warning when we fail to connect to all of
3044 our bridges. Previously, we didn't inform the controller, and
3045 the bootstrap process would stall. Fixes bug 11069; bugfix on
3047 - Exit immediately when a process-owning controller exits.
3048 Previously, tor relays would wait for a little while after their
3049 controller exited, as if they had gotten an INT signal -- but this
3050 was problematic, since there was no feedback for the user. To do a
3051 clean shutdown, controllers should send an INT signal and give Tor
3052 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
3053 - Stop attempting to connect to bridges before our pluggable
3054 transports are configured (harmless but resulted in some erroneous
3055 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
3056 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
3057 generating incorrect SOCKS5 responses, and confusing client
3058 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
3060 o Minor bugfixes (relays and bridges):
3061 - Avoid crashing on a malformed resolv.conf file when running a
3062 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
3063 - Non-exit relays no longer launch mock DNS requests to check for
3064 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
3065 non-exit relays stopped servicing DNS requests. Fixes bug 965;
3066 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
3067 - Bridges now report complete directory request statistics. Related
3068 to bug 5824; bugfix on 0.2.2.1-alpha.
3069 - Bridges now never collect statistics that were designed for
3070 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
3071 - Stop giving annoying warning messages when we decide not to launch
3072 a pluggable transport proxy that we don't need (because there are
3073 no bridges configured to use it). Resolves ticket 5018; bugfix
3075 - Give the correct URL in the warning message when trying to run a
3076 relay on an ancient version of Windows. Fixes bug 9393.
3078 o Minor bugfixes (backtrace support):
3079 - Support automatic backtraces on more platforms by using the
3080 "-fasynchronous-unwind-tables" compiler option. This option is
3081 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
3082 is on by default and table generation is not. This doesn't yet
3083 add Windows support; only Linux, OSX, and some BSDs are affected.
3084 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
3085 - Avoid strange behavior if two threads hit failed assertions at the
3086 same time and both try to log backtraces at once. (Previously, if
3087 this had happened, both threads would have stored their intermediate
3088 results in the same buffer, and generated junk outputs.) Reported by
3089 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
3090 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
3091 0.2.5.2-alpha; patch from Nick Hopper.
3093 o Minor bugfixes (unit tests):
3094 - Fix a small bug in the unit tests that might have made the tests
3095 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
3096 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
3099 - Remove all remaining code related to version-0 hidden service
3100 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
3101 the rest of bug 10841.
3104 - Document in the manpage that "KBytes" may also be written as
3105 "kilobytes" or "KB", that "Kbits" may also be written as
3106 "kilobits", and so forth. Closes ticket 9222.
3107 - Document that the ClientOnly config option overrides ORPort.
3108 Our old explanation made ClientOnly sound as though it did
3109 nothing at all. Resolves bug 9059.
3110 - Explain that SocksPolicy, DirPolicy, and similar options don't
3111 take port arguments. Fixes the other part of ticket 11108.
3112 - Fix a comment about the rend_server_descriptor_t.protocols field
3113 to more accurately describe its range. Also, make that field
3114 unsigned, to more accurately reflect its usage. Fixes bug 9099;
3115 bugfix on 0.2.1.5-alpha.
3116 - Fix the manpage's description of HiddenServiceAuthorizeClient:
3117 the maximum client name length is 16, not 19. Fixes bug 11118;
3118 bugfix on 0.2.1.6-alpha.
3120 o Code simplifications and refactoring:
3121 - Get rid of router->address, since in all cases it was just the
3122 string representation of router->addr. Resolves ticket 5528.
3124 o Test infrastructure:
3125 - Update to the latest version of tinytest.
3126 - Improve the tinytest implementation of string operation tests so
3127 that comparisons with NULL strings no longer crash the tests; they
3128 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
3131 Changes in version 0.2.4.21 - 2014-02-28
3132 Tor 0.2.4.21 further improves security against potential adversaries who
3133 find breaking 1024-bit crypto doable, and backports several stability
3134 and robustness patches from the 0.2.5 branch.
3136 o Major features (client security):
3137 - When we choose a path for a 3-hop circuit, make sure it contains
3138 at least one relay that supports the NTor circuit extension
3139 handshake. Otherwise, there is a chance that we're building
3140 a circuit that's worth attacking by an adversary who finds
3141 breaking 1024-bit crypto doable, and that chance changes the game
3142 theory. Implements ticket 9777.
3145 - Do not treat streams that fail with reason
3146 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3147 since it could also indicate an ENETUNREACH connection error. Fixes
3148 part of bug 10777; bugfix on 0.2.4.8-alpha.
3150 o Code simplification and refactoring:
3151 - Remove data structures which were introduced to implement the
3152 CellStatistics option: they are now redundant with the new timestamp
3153 field in the regular packed_cell_t data structure, which we did
3154 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
3157 - Always clear OpenSSL bignums before freeing them -- even bignums
3158 that don't contain secrets. Resolves ticket 10793. Patch by
3160 - Build without warnings under clang 3.4. (We have some macros that
3161 define static functions only some of which will get used later in
3162 the module. Starting with clang 3.4, these give a warning unless the
3163 unused attribute is set on them.) Resolves ticket 10904.
3164 - Update geoip and geoip6 files to the February 7 2014 Maxmind
3165 GeoLite2 Country database.
3168 - Set the listen() backlog limit to the largest actually supported
3169 on the system, not to the value in a header file. Fixes bug 9716;
3170 bugfix on every released Tor.
3171 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3172 exit node as a NOROUTE error, not an INTERNAL error, since they
3173 can apparently happen when trying to connect to the wrong sort
3174 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3175 - Fix build warnings about missing "a2x" comment when building the
3176 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3177 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3178 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3179 not entirely remove it from the connection lists. Fixes bug 9602;
3180 bugfix on 0.2.4.4-alpha.
3181 - Fix a segmentation fault in our benchmark code when running with
3182 Fedora's OpenSSL package, or any other OpenSSL that provides
3183 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3184 - Turn "circuit handshake stats since last time" log messages into a
3185 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3187 o Documentation fixes:
3188 - Document that all but one DirPort entry must have the NoAdvertise
3189 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3192 Changes in version 0.2.5.2-alpha - 2014-02-13
3193 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
3194 like the "poor random number generation" fix and the "building too many
3195 circuits" fix. It also further improves security against potential
3196 adversaries who find breaking 1024-bit crypto doable, and launches
3197 pluggable transports on demand (which gets us closer to integrating
3198 pluggable transport support by default -- not to be confused with Tor
3199 bundles enabling pluggable transports and bridges by default).
3201 o Major features (client security):
3202 - When we choose a path for a 3-hop circuit, make sure it contains
3203 at least one relay that supports the NTor circuit extension
3204 handshake. Otherwise, there is a chance that we're building
3205 a circuit that's worth attacking by an adversary who finds
3206 breaking 1024-bit crypto doable, and that chance changes the game
3207 theory. Implements ticket 9777.
3208 - Clients now look at the "usecreatefast" consensus parameter to
3209 decide whether to use CREATE_FAST or CREATE cells for the first hop
3210 of their circuit. This approach can improve security on connections
3211 where Tor's circuit handshake is stronger than the available TLS
3212 connection security levels, but the tradeoff is more computational
3213 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3215 o Major features (bridges):
3216 - Don't launch pluggable transport proxies if we don't have any
3217 bridges configured that would use them. Now we can list many
3218 pluggable transports, and Tor will dynamically start one when it
3219 hears a bridge address that needs it. Resolves ticket 5018.
3220 - The bridge directory authority now assigns status flags (Stable,
3221 Guard, etc) to bridges based on thresholds calculated over all
3222 Running bridges. Now bridgedb can finally make use of its features
3223 to e.g. include at least one Stable bridge in its answers. Fixes
3226 o Major features (other):
3227 - Extend ORCONN controller event to include an "ID" parameter,
3228 and add four new controller event types CONN_BW, CIRC_BW,
3229 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
3230 The new events are emitted in private Tor networks only, with the
3231 goal of being able to better track performance and load during
3232 full-network simulations. Implements proposal 218 and ticket 7359.
3233 - On some platforms (currently: recent OSX versions, glibc-based
3234 platforms that support the ELF format, and a few other
3235 Unix-like operating systems), Tor can now dump stack traces
3236 when a crash occurs or an assertion fails. By default, traces
3237 are dumped to stderr (if possible) and to any logs that are
3238 reporting errors. Implements ticket 9299.
3241 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3242 not entirely remove it from the connection lists. Fixes bug 9602;
3243 bugfix on 0.2.4.4-alpha.
3244 - Do not treat streams that fail with reason
3245 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3246 since it could also indicate an ENETUNREACH connection error. Fixes
3247 part of bug 10777; bugfix on 0.2.4.8-alpha.
3249 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3250 - Do not allow OpenSSL engines to replace the PRNG, even when
3251 HardwareAccel is set. The only default builtin PRNG engine uses
3252 the Intel RDRAND instruction to replace the entire PRNG, and
3253 ignores all attempts to seed it with more entropy. That's
3254 cryptographically stupid: the right response to a new alleged
3255 entropy source is never to discard all previously used entropy
3256 sources. Fixes bug 10402; works around behavior introduced in
3257 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3259 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3260 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3261 - Avoid launching spurious extra circuits when a stream is pending.
3262 This fixes a bug where any circuit that _wasn't_ unusable for new
3263 streams would be treated as if it were, causing extra circuits to
3264 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3266 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3267 - No longer stop reading or writing on cpuworker connections when
3268 our rate limiting buckets go empty. Now we should handle circuit
3269 handshake requests more promptly. Resolves bug 9731.
3270 - Stop trying to bootstrap all our directory information from
3271 only our first guard. Discovered while fixing bug 9946; bugfix
3274 o Minor features (bridges, pluggable transports):
3275 - Add threshold cutoffs to the networkstatus document created by
3276 the Bridge Authority. Fixes bug 1117.
3277 - On Windows, spawn background processes using the CREATE_NO_WINDOW
3278 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
3279 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
3280 Vidalia set this option for us.) Implements ticket 10297.
3282 o Minor features (security):
3283 - Always clear OpenSSL bignums before freeing them -- even bignums
3284 that don't contain secrets. Resolves ticket 10793. Patch by
3287 o Minor features (config options and command line):
3288 - Add an --allow-missing-torrc commandline option that tells Tor to
3289 run even if the configuration file specified by -f is not available.
3290 Implements ticket 10060.
3291 - Add support for the TPROXY transparent proxying facility on Linux.
3292 See documentation for the new TransProxyType option for more
3293 details. Implementation by "thomo". Closes ticket 10582.
3295 o Minor features (controller):
3296 - Add a new "HS_DESC" controller event that reports activities
3297 related to hidden service descriptors. Resolves ticket 8510.
3298 - New "DROPGUARDS" controller command to forget all current entry
3299 guards. Not recommended for ordinary use, since replacing guards
3300 too frequently makes several attacks easier. Resolves ticket 9934;
3303 o Minor features (build):
3304 - Assume that a user using ./configure --host wants to cross-compile,
3305 and give an error if we cannot find a properly named
3306 tool-chain. Add a --disable-tool-name-check option to proceed
3307 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
3308 - If we run ./configure and the compiler recognizes -fstack-protector
3309 but the linker rejects it, warn the user about a potentially missing
3310 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
3312 o Minor features (testing):
3313 - If Python is installed, "make check" now runs extra tests beyond
3314 the unit test scripts.
3315 - When bootstrapping a test network, sometimes very few relays get
3316 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
3317 specify a set of relays which should be voted Guard regardless of
3318 their uptime or bandwidth. Addresses ticket 9206.
3320 o Minor features (log messages):
3321 - When ServerTransportPlugin is set on a bridge, Tor can write more
3322 useful statistics about bridge use in its extrainfo descriptors,
3323 but only if the Extended ORPort ("ExtORPort") is set too. Add a
3324 log message to inform the user in this case. Resolves ticket 9651.
3325 - When receiving a new controller connection, log the origin address.
3326 Resolves ticket 9698; patch from "sigpipe".
3327 - When logging OpenSSL engine status at startup, log the status of
3328 more engines. Fixes ticket 10043; patch from Joshua Datko.
3329 - Turn "circuit handshake stats since last time" log messages into a
3330 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3332 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3333 - Improve the circuit queue out-of-memory handler. Previously, when
3334 we ran low on memory, we'd close whichever circuits had the most
3335 queued cells. Now, we close those that have the *oldest* queued
3336 cells, on the theory that those are most responsible for us
3337 running low on memory. Based on analysis from a forthcoming paper
3338 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3339 - Generate bootstrapping status update events correctly when fetching
3340 microdescriptors. Fixes bug 9927.
3341 - Update to the October 2 2013 Maxmind GeoLite Country database.
3343 o Minor bugfixes (clients):
3344 - When closing a channel that has already been open, do not close
3345 pending circuits that were waiting to connect to the same relay.
3346 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
3349 o Minor bugfixes (relays):
3350 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3351 exit node as a NOROUTE error, not an INTERNAL error, since they
3352 can apparently happen when trying to connect to the wrong sort
3353 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3355 o Minor bugfixes (bridges):
3356 - Fix a bug where the first connection works to a bridge that uses a
3357 pluggable transport with client-side parameters, but we don't send
3358 the client-side parameters on subsequent connections. (We don't
3359 use any pluggable transports with client-side parameters yet,
3360 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
3361 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
3363 o Minor bugfixes (node selection):
3364 - If ExcludeNodes is set, consider non-excluded hidden service
3365 directory servers before excluded ones. Do not consider excluded
3366 hidden service directory servers at all if StrictNodes is
3367 set. (Previously, we would sometimes decide to connect to those
3368 servers, and then realize before we initiated a connection that
3369 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
3371 - If we set the ExitNodes option but it doesn't include any nodes
3372 that have the Exit flag, we would choose not to bootstrap. Now we
3373 bootstrap so long as ExitNodes includes nodes which can exit to
3374 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
3376 o Minor bugfixes (controller and command-line):
3377 - If changing a config option via "setconf" fails in a recoverable
3378 way, we used to nonetheless write our new control ports to the
3379 file described by the "ControlPortWriteToFile" option. Now we only
3380 write out that file if we successfully switch to the new config
3381 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
3382 - When a command-line option such as --version or --help that
3383 ordinarily implies --hush appears on the command line along with
3384 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
3385 only if it appeared later on the command line. Fixes bug 9578;
3386 bugfix on 0.2.5.1-alpha.
3388 o Minor bugfixes (code correctness):
3389 - Previously we used two temporary files when writing descriptors to
3390 disk; now we only use one. Fixes bug 1376.
3391 - Remove an erroneous (but impossible and thus harmless) pointer
3392 comparison that would have allowed compilers to skip a bounds
3393 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
3394 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
3395 - Fix an always-true assertion in pluggable transports code so it
3396 actually checks what it was trying to check. Fixes bug 10046;
3397 bugfix on 0.2.3.9-alpha. Found by "dcb".
3399 o Minor bugfixes (protocol correctness):
3400 - When receiving a VERSIONS cell with an odd number of bytes, close
3401 the connection immediately since the cell is malformed. Fixes bug
3402 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
3405 o Minor bugfixes (build):
3406 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
3407 turned off (that is, without support for v2 link handshakes). Fixes
3408 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
3409 - Fix compilation warnings and startup issues when running with
3410 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
3412 - Fix compilation on Solaris 9, which didn't like us having an
3413 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
3415 o Minor bugfixes (testing):
3416 - Fix a segmentation fault in our benchmark code when running with
3417 Fedora's OpenSSL package, or any other OpenSSL that provides
3418 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3420 o Minor bugfixes (log messages):
3421 - Fix a bug where clients using bridges would report themselves
3422 as 50% bootstrapped even without a live consensus document.
3423 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
3424 - Suppress a warning where, if there's only one directory authority
3425 in the network, we would complain that votes and signatures cannot
3426 be uploaded to other directory authorities. Fixes bug 10842;
3427 bugfix on 0.2.2.26-beta.
3428 - Report bootstrapping progress correctly when we're downloading
3429 microdescriptors. We had updated our "do we have enough microdescs
3430 to begin building circuits?" logic most recently in 0.2.4.10-alpha
3431 (see bug 5956), but we left the bootstrap status event logic at
3432 "how far through getting 1/4 of them are we?" Fixes bug 9958;
3433 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
3435 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3436 - Avoid a crash bug when starting with a corrupted microdescriptor
3437 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3438 - If we fail to dump a previously cached microdescriptor to disk, avoid
3439 freeing duplicate data later on. Fixes bug 10423; bugfix on
3440 0.2.4.13-alpha. Spotted by "bobnomnom".
3442 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3443 - Correctly log long IPv6 exit policies, instead of truncating them
3444 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3445 - Our default TLS ecdhe groups were backwards: we meant to be using
3446 P224 for relays (for performance win) and P256 for bridges (since
3447 it is more common in the wild). Instead we had it backwards. After
3448 reconsideration, we decided that the default should be P256 on all
3449 hosts, since its security is probably better, and since P224 is
3450 reportedly used quite little in the wild. Found by "skruffy" on
3451 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3452 - Free directory authority certificate download statuses on exit
3453 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3455 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3456 - If the guard we choose first doesn't answer, we would try the
3457 second guard, but once we connected to the second guard we would
3458 abandon it and retry the first one, slowing down bootstrapping.
3459 The fix is to treat all our initially chosen guards as acceptable
3460 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3461 - Fix an assertion failure that would occur when disabling the
3462 ORPort setting on a running Tor process while accounting was
3463 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3464 - When examining the list of network interfaces to find our address,
3465 do not consider non-running or disabled network interfaces. Fixes
3466 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3467 - Avoid an off-by-one error when checking buffer boundaries when
3468 formatting the exit status of a pluggable transport helper.
3469 This is probably not an exploitable bug, but better safe than
3470 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3473 o Removed code and features:
3474 - Clients now reject any directory authority certificates lacking
3475 a dir-key-crosscert element. These have been included since
3476 0.2.1.9-alpha, so there's no real reason for them to be optional
3477 any longer. Completes proposal 157. Resolves ticket 10162.
3478 - Remove all code that existed to support the v2 directory system,
3479 since there are no longer any v2 directory authorities. Resolves
3481 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
3482 options, which were used for designating authorities as "Hidden
3483 service authorities". There has been no use of hidden service
3484 authorities since 0.2.2.1-alpha, when we stopped uploading or
3485 downloading v0 hidden service descriptors. Fixes bug 10881; also
3486 part of a fix for bug 10841.
3488 o Code simplification and refactoring:
3489 - Remove some old fallback code designed to keep Tor clients working
3490 in a network with only two working relays. Elsewhere in the code we
3491 have long since stopped supporting such networks, so there wasn't
3492 much point in keeping it around. Addresses ticket 9926.
3493 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
3494 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
3495 - Remove data structures which were introduced to implement the
3496 CellStatistics option: they are now redundant with the addition
3497 of a timestamp to the regular packed_cell_t data structure, which
3498 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
3501 o Documentation (man page) fixes:
3502 - Update manpage to describe some of the files you can expect to
3503 find in Tor's DataDirectory. Addresses ticket 9839.
3504 - Document that all but one DirPort entry must have the NoAdvertise
3505 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3507 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3508 - Clarify the usage and risks of setting the ContactInfo torrc line
3509 for your relay or bridge. Resolves ticket 9854.
3510 - Add anchors to the manpage so we can link to the html version of
3511 the documentation for specific options. Resolves ticket 9866.
3512 - Replace remaining references to DirServer in man page and
3513 log entries. Resolves ticket 10124.
3516 - Make the "tor-gencert" tool used by directory authority operators
3517 create 2048-bit signing keys by default (rather than 1024-bit, since
3518 1024-bit is uncomfortably small these days). Addresses ticket 10324.
3521 Changes in version 0.2.4.20 - 2013-12-22
3522 Tor 0.2.4.20 fixes potentially poor random number generation for users
3523 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
3524 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
3525 and 4) have no state file in their DataDirectory (as would happen on
3526 first start). Users who generated relay or hidden service identity
3527 keys in such a situation should discard them and generate new ones.
3529 This release also fixes a logic error that caused Tor clients to build
3530 many more preemptive circuits than they actually need.
3533 - Do not allow OpenSSL engines to replace the PRNG, even when
3534 HardwareAccel is set. The only default builtin PRNG engine uses
3535 the Intel RDRAND instruction to replace the entire PRNG, and
3536 ignores all attempts to seed it with more entropy. That's
3537 cryptographically stupid: the right response to a new alleged
3538 entropy source is never to discard all previously used entropy
3539 sources. Fixes bug 10402; works around behavior introduced in
3540 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3542 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3543 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3544 - Avoid launching spurious extra circuits when a stream is pending.
3545 This fixes a bug where any circuit that _wasn't_ unusable for new
3546 streams would be treated as if it were, causing extra circuits to
3547 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3550 - Avoid a crash bug when starting with a corrupted microdescriptor
3551 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3552 - If we fail to dump a previously cached microdescriptor to disk, avoid
3553 freeing duplicate data later on. Fixes bug 10423; bugfix on
3554 0.2.4.13-alpha. Spotted by "bobnomnom".
3557 Changes in version 0.2.4.19 - 2013-12-11
3558 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
3559 (1986-2013). Aaron worked on diverse projects including helping to guide
3560 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
3561 transparency to the U.S government's PACER documents, and contributing
3562 design and development for Tor and Tor2Web. Aaron was one of the latest
3563 martyrs in our collective fight for civil liberties and human rights,
3564 and his death is all the more painful because he was one of us.
3566 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
3567 a new circuit handshake and link encryption that use ECC to provide
3568 better security and efficiency; makes relays better manage circuit
3569 creation requests; uses "directory guards" to reduce client enumeration
3570 risks; makes bridges collect and report statistics about the pluggable
3571 transports they support; cleans up and improves our geoip database;
3572 gets much closer to IPv6 support for clients, bridges, and relays; makes
3573 directory authorities use measured bandwidths rather than advertised
3574 ones when computing flags and thresholds; disables client-side DNS
3575 caching to reduce tracking risks; and fixes a big bug in bridge
3576 reachability testing. This release introduces two new design
3577 abstractions in the code: a new "channel" abstraction between circuits
3578 and or_connections to allow for implementing alternate relay-to-relay
3579 transports, and a new "circuitmux" abstraction storing the queue of
3580 circuits for a channel. The release also includes many stability,
3581 security, and privacy fixes.
3584 Changes in version 0.2.4.18-rc - 2013-11-16
3585 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
3586 series. It takes a variety of fixes from the 0.2.5.x branch to improve
3587 stability, performance, and better handling of edge cases.
3590 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3591 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3592 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3593 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3594 them to solve bug 6033.)
3597 - No longer stop reading or writing on cpuworker connections when
3598 our rate limiting buckets go empty. Now we should handle circuit
3599 handshake requests more promptly. Resolves bug 9731.
3600 - If we are unable to save a microdescriptor to the journal, do not
3601 drop it from memory and then reattempt downloading it. Fixes bug
3602 9645; bugfix on 0.2.2.6-alpha.
3603 - Stop trying to bootstrap all our directory information from
3604 only our first guard. Discovered while fixing bug 9946; bugfix
3606 - The new channel code sometimes lost track of in-progress circuits,
3607 causing long-running clients to stop building new circuits. The
3608 fix is to always call circuit_n_chan_done(chan, 0) from
3609 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3611 o Minor bugfixes (on 0.2.4.x):
3612 - Correctly log long IPv6 exit policies, instead of truncating them
3613 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3614 - Our default TLS ecdhe groups were backwards: we meant to be using
3615 P224 for relays (for performance win) and P256 for bridges (since
3616 it is more common in the wild). Instead we had it backwards. After
3617 reconsideration, we decided that the default should be P256 on all
3618 hosts, since its security is probably better, and since P224 is
3619 reportedly used quite little in the wild. Found by "skruffy" on
3620 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3621 - Free directory authority certificate download statuses on exit
3622 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3624 o Minor bugfixes (on 0.2.3.x and earlier):
3625 - If the guard we choose first doesn't answer, we would try the
3626 second guard, but once we connected to the second guard we would
3627 abandon it and retry the first one, slowing down bootstrapping.
3628 The fix is to treat all our initially chosen guards as acceptable
3629 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3630 - Fix an assertion failure that would occur when disabling the
3631 ORPort setting on a running Tor process while accounting was
3632 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3633 - When examining the list of network interfaces to find our address,
3634 do not consider non-running or disabled network interfaces. Fixes
3635 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3636 - Avoid an off-by-one error when checking buffer boundaries when
3637 formatting the exit status of a pluggable transport helper.
3638 This is probably not an exploitable bug, but better safe than
3639 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3642 o Minor features (protecting client timestamps):
3643 - Clients no longer send timestamps in their NETINFO cells. These were
3644 not used for anything, and they provided one small way for clients
3645 to be distinguished from each other as they moved from network to
3646 network or behind NAT. Implements part of proposal 222.
3647 - Clients now round timestamps in INTRODUCE cells down to the nearest
3648 10 minutes. If a new Support022HiddenServices option is set to 0, or
3649 if it's set to "auto" and the feature is disabled in the consensus,
3650 the timestamp is sent as 0 instead. Implements part of proposal 222.
3651 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3652 a big deal from a security point of view, but it achieves no actual
3653 good purpose, and isn't needed. Implements part of proposal 222.
3654 - Reduce down accuracy of timestamps in hidden service descriptors.
3655 Implements part of proposal 222.
3657 o Minor features (other):
3658 - Improve the circuit queue out-of-memory handler. Previously, when
3659 we ran low on memory, we'd close whichever circuits had the most
3660 queued cells. Now, we close those that have the *oldest* queued
3661 cells, on the theory that those are most responsible for us
3662 running low on memory. Based on analysis from a forthcoming paper
3663 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3664 - Generate bootstrapping status update events correctly when fetching
3665 microdescriptors. Fixes bug 9927.
3666 - Update to the October 2 2013 Maxmind GeoLite Country database.
3668 o Documentation fixes:
3669 - Clarify the usage and risks of setting the ContactInfo torrc line
3670 for your relay or bridge. Resolves ticket 9854.
3671 - Add anchors to the manpage so we can link to the html version of
3672 the documentation for specific options. Resolves ticket 9866.
3673 - Replace remaining references to DirServer in man page and
3674 log entries. Resolves ticket 10124.
3677 Changes in version 0.2.5.1-alpha - 2013-10-02
3678 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
3679 on Linux, allows bridges that offer pluggable transports to report usage
3680 statistics, fixes many issues to make testing easier, and provides
3681 a pile of minor features and bugfixes that have been waiting for a
3682 release of the new branch.
3684 This is the first alpha release in a new series, so expect there to
3685 be bugs. Users who would rather test out a more stable branch should
3686 stay with 0.2.4.x for now.
3688 o Major features (security):
3689 - Use the seccomp2 syscall filtering facility on Linux to limit
3690 which system calls Tor can invoke. This is an experimental,
3691 Linux-only feature to provide defense-in-depth against unknown
3692 attacks. To try turning it on, set "Sandbox 1" in your torrc
3693 file. Please be ready to report bugs. We hope to add support
3694 for better sandboxing in the future, including more fine-grained
3695 filters, better division of responsibility, and support for more
3696 platforms. This work has been done by Cristian-Matei Toader for
3697 Google Summer of Code.
3698 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3699 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3700 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3701 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3702 them to solve bug 6033.)
3704 o Major features (other):
3705 - Add support for passing arguments to managed pluggable transport
3706 proxies. Implements ticket 3594.
3707 - Bridges now track GeoIP information and the number of their users
3708 even when pluggable transports are in use, and report usage
3709 statistics in their extra-info descriptors. Resolves tickets 4773
3711 - Make testing Tor networks bootstrap better: lower directory fetch
3712 retry schedules and maximum interval without directory requests,
3713 and raise maximum download tries. Implements ticket 6752.
3714 - Add make target 'test-network' to run tests on a Chutney network.
3715 Implements ticket 8530.
3716 - The ntor handshake is now on-by-default, no matter what the
3717 directory authorities recommend. Implements ticket 8561.
3720 - Instead of writing destroy cells directly to outgoing connection
3721 buffers, queue them and intersperse them with other outgoing cells.
3722 This can prevent a set of resource starvation conditions where too
3723 many pending destroy cells prevent data cells from actually getting
3724 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
3725 bugfix on 0.2.0.1-alpha.
3726 - If we are unable to save a microdescriptor to the journal, do not
3727 drop it from memory and then reattempt downloading it. Fixes bug
3728 9645; bugfix on 0.2.2.6-alpha.
3729 - The new channel code sometimes lost track of in-progress circuits,
3730 causing long-running clients to stop building new circuits. The
3731 fix is to always call circuit_n_chan_done(chan, 0) from
3732 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3735 - Tor now builds each source file in two modes: a mode that avoids
3736 exposing identifiers needlessly, and another mode that exposes
3737 more identifiers for testing. This lets the compiler do better at
3738 optimizing the production code, while enabling us to take more
3739 radical measures to let the unit tests test things.
3740 - The production builds no longer include functions used only in
3741 the unit tests; all functions exposed from a module only for
3742 unit-testing are now static in production builds.
3743 - Add an --enable-coverage configuration option to make the unit
3744 tests (and a new src/or/tor-cov target) to build with gcov test
3748 - We now have rudimentary function mocking support that our unit
3749 tests can use to test functions in isolation. Function mocking
3750 lets the tests temporarily replace a function's dependencies with
3751 stub functions, so that the tests can check the function without
3752 invoking the other functions it calls.
3753 - Add more unit tests for the <circid,channel>->circuit map, and
3754 the destroy-cell-tracking code to fix bug 7912.
3755 - Unit tests for failing cases of the TAP onion handshake.
3756 - More unit tests for address-manipulation functions.
3758 o Minor features (protecting client timestamps):
3759 - Clients no longer send timestamps in their NETINFO cells. These were
3760 not used for anything, and they provided one small way for clients
3761 to be distinguished from each other as they moved from network to
3762 network or behind NAT. Implements part of proposal 222.
3763 - Clients now round timestamps in INTRODUCE cells down to the nearest
3764 10 minutes. If a new Support022HiddenServices option is set to 0, or
3765 if it's set to "auto" and the feature is disabled in the consensus,
3766 the timestamp is sent as 0 instead. Implements part of proposal 222.
3767 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3768 a big deal from a security point of view, but it achieves no actual
3769 good purpose, and isn't needed. Implements part of proposal 222.
3770 - Reduce down accuracy of timestamps in hidden service descriptors.
3771 Implements part of proposal 222.
3773 o Minor features (config options):
3774 - Config (torrc) lines now handle fingerprints which are missing
3775 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
3776 - Support a --dump-config option to print some or all of the
3777 configured options. Mainly useful for debugging the command-line
3778 option parsing code. Helps resolve ticket 4647.
3779 - Raise awareness of safer logging: notify user of potentially
3780 unsafe config options, like logging more verbosely than severity
3781 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
3782 - Add a new configuration option TestingV3AuthVotingStartOffset
3783 that bootstraps a network faster by changing the timing for
3784 consensus votes. Addresses ticket 8532.
3785 - Add a new torrc option "ServerTransportOptions" that allows
3786 bridge operators to pass configuration parameters to their
3787 pluggable transports. Resolves ticket 8929.
3788 - The config (torrc) file now accepts bandwidth and space limits in
3789 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
3790 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
3793 o Minor features (build):
3794 - Add support for `--library-versions` flag. Implements ticket 6384.
3795 - Return the "unexpected sendme" warnings to a warn severity, but make
3796 them rate limited, to help diagnose ticket 8093.
3797 - Detect a missing asciidoc, and warn the user about it, during
3798 configure rather than at build time. Fixes issue 6506. Patch from
3801 o Minor features (other):
3802 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
3803 sockets in a single system call. Implements ticket 5129.
3804 - Log current accounting state (bytes sent and received + remaining
3805 time for the current accounting period) in the relay's heartbeat
3806 message. Implements ticket 5526; patch from Peter Retzlaff.
3807 - Implement the TRANSPORT_LAUNCHED control port event that
3808 notifies controllers about new launched pluggable
3809 transports. Resolves ticket 5609.
3810 - If we're using the pure-C 32-bit curve25519_donna implementation
3811 of curve25519, build it with the -fomit-frame-pointer option to
3812 make it go faster on register-starved hosts. This improves our
3813 handshake performance by about 6% on i386 hosts without nacl.
3815 - Update to the September 4 2013 Maxmind GeoLite Country database.
3818 - Set the listen() backlog limit to the largest actually supported
3819 on the system, not to the value in a header file. Fixes bug 9716;
3820 bugfix on every released Tor.
3821 - No longer accept malformed http headers when parsing urls from
3822 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
3823 bugfix on 0.0.6pre1.
3824 - In munge_extrainfo_into_routerinfo(), check the return value of
3825 memchr(). This would have been a serious issue if we ever passed
3826 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
3828 - On the chance that somebody manages to build Tor on a
3829 platform where time_t is unsigned, correct the way that
3830 microdesc_add_to_cache() handles negative time arguments.
3831 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
3832 - Reject relative control socket paths and emit a warning. Previously,
3833 single-component control socket paths would be rejected, but Tor
3834 would not log why it could not validate the config. Fixes bug 9258;
3835 bugfix on 0.2.3.16-alpha.
3837 o Minor bugfixes (command line):
3838 - Use a single command-line parser for parsing torrc options on the
3839 command line and for finding special command-line options to avoid
3840 inconsistent behavior for torrc option arguments that have the same
3841 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
3843 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
3844 9573; bugfix on 0.0.9pre5.
3846 o Minor fixes (build, auxiliary programs):
3847 - Stop preprocessing the "torify" script with autoconf, since
3848 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
3850 - The tor-fw-helper program now follows the standard convention and
3851 exits with status code "0" on success. Fixes bug 9030; bugfix on
3852 0.2.3.1-alpha. Patch by Arlo Breault.
3853 - Corrected ./configure advice for what openssl dev package you should
3854 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
3856 o Minor code improvements:
3857 - Remove constants and tests for PKCS1 padding; it's insecure and
3858 shouldn't be used for anything new. Fixes bug 8792; patch
3860 - Remove instances of strcpy() from the unit tests. They weren't
3861 hurting anything, since they were only in the unit tests, but it's
3862 embarassing to have strcpy() in the code at all, and some analysis
3863 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
3864 0.2.3.8-alpha. Patch from Arlo Breault.
3867 - Remove migration code from when we renamed the "cached-routers"
3868 file to "cached-descriptors" back in 0.2.0.8-alpha. This
3869 incidentally resolves ticket 6502 by cleaning up the related code
3870 a bit. Patch from Akshay Hebbar.
3872 o Code simplification and refactoring:
3873 - Extract the common duplicated code for creating a subdirectory
3874 of the data directory and writing to a file in it. Fixes ticket
3875 4282; patch from Peter Retzlaff.
3876 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
3877 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
3878 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
3879 - Add a set of accessor functions for the circuit timeout data
3880 structure. Fixes ticket 6153; patch from "piet".
3881 - Clean up exit paths from connection_listener_new(). Closes ticket
3882 8789. Patch from Arlo Breault.
3883 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
3884 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
3885 - Use a doubly-linked list to implement the global circuit list.
3886 Resolves ticket 9108. Patch from Marek Majkowski.
3887 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
3890 Changes in version 0.2.4.17-rc - 2013-09-05
3891 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
3892 series. It adds an emergency step to help us tolerate the massive
3893 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
3894 circuit-level handshakes now effectively jump the queue compared to
3895 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
3896 big bug hindering bridge reachability tests.
3899 - Relays now process the new "NTor" circuit-level handshake requests
3900 with higher priority than the old "TAP" circuit-level handshake
3901 requests. We still process some TAP requests to not totally starve
3902 0.2.3 clients when NTor becomes popular. A new consensus parameter
3903 "NumNTorsPerTAP" lets us tune the balance later if we need to.
3904 Implements ticket 9574.
3907 - If the circuit build timeout logic is disabled (via the consensus,
3908 or because we are an authority), then don't build testing circuits.
3909 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
3910 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
3911 previously they did not, which prevented them from receiving
3912 successful connections from relays for self-test or bandwidth
3913 testing. Also, when a relay is extending a circuit to a bridge,
3914 it needs to send a NETINFO cell, even when the bridge hasn't sent
3915 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
3916 - If the time to download the next old-style networkstatus is in
3917 the future, do not decline to consider whether to download the
3918 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
3922 - Avoid double-closing the listener socket in our socketpair()
3923 replacement (used on Windows) in the case where the addresses on
3924 our opened sockets don't match what we expected. Fixes bug 9400;
3925 bugfix on 0.0.2pre7. Found by Coverity.
3927 o Minor fixes (config options):
3928 - Avoid overflows when the user sets MaxCircuitDirtiness to a
3929 ridiculously high value, by imposing a (ridiculously high) 30-day
3930 maximum on MaxCircuitDirtiness.
3931 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
3932 message is logged at notice, not at info.
3933 - Warn and fail if a server is configured not to advertise any
3934 ORPorts at all. (We need *something* to put in our descriptor,
3935 or we just won't work.)
3938 - Track how many "TAP" and "NTor" circuit handshake requests we get,
3939 and how many we complete, and log it every hour to help relay
3940 operators follow trends in network load. Addresses ticket 9658.
3941 - Update to the August 7 2013 Maxmind GeoLite Country database.
3944 Changes in version 0.2.4.16-rc - 2013-08-10
3945 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
3946 series. It fixes several crash bugs in the 0.2.4 branch.
3949 - Fix a bug in the voting algorithm that could yield incorrect results
3950 when a non-naming authority declared too many flags. Fixes bug 9200;
3951 bugfix on 0.2.0.3-alpha.
3952 - Fix an uninitialized read that could in some cases lead to a remote
3953 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
3954 Anybody running a hidden service on the experimental 0.2.4.x
3955 branch should upgrade. (This is, so far as we know, unrelated to
3957 - Avoid an assertion failure when processing DNS replies without the
3958 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
3959 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
3960 0.2.4.15-rc. Found by stem integration tests.
3963 - Fix an invalid memory read that occured when a pluggable
3964 transport proxy failed its configuration protocol.
3965 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
3966 - When evaluating whether to use a connection that we haven't
3967 decided is canonical using a recent link protocol version,
3968 decide that it's canonical only if it used address _does_
3969 match the desired address. Fixes bug 9309; bugfix on
3970 0.2.4.4-alpha. Reported by skruffy.
3971 - Make the default behavior of NumDirectoryGuards be to track
3972 NumEntryGuards. Now a user who changes only NumEntryGuards will get
3973 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
3974 - Fix a spurious compilation warning with some older versions of
3975 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
3978 - Update to the July 3 2013 Maxmind GeoLite Country database.
3981 Changes in version 0.2.4.15-rc - 2013-07-01
3982 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
3983 series. It fixes a few smaller bugs, but generally appears stable.
3984 Please test it and let us know whether it is!
3987 - When receiving a new configuration file via the control port's
3988 LOADCONF command, do not treat the defaults file as absent.
3989 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3992 - Issue a warning when running with the bufferevents backend enabled.
3993 It's still not stable, and people should know that they're likely
3994 to hit unexpected problems. Closes ticket 9147.
3997 Changes in version 0.2.4.14-alpha - 2013-06-18
3998 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3999 present in 0.2.4.13-alpha.
4002 - When we have too much memory queued in circuits (according to a new
4003 MaxMemInCellQueues option), close the circuits consuming the most
4004 memory. This prevents us from running out of memory as a relay if
4005 circuits fill up faster than they can be drained. Fixes bug 9063;
4006 bugfix on the 54th commit of Tor. This bug is a further fix beyond
4007 bug 6252, whose fix was merged into 0.2.3.21-rc.
4009 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
4010 where we tried to solve this issue simply by imposing an upper limit
4011 on the number of queued cells for a single circuit. That approach
4012 proved to be problematic, since there are ways to provoke clients to
4013 send a number of cells in excess of any such reasonable limit. Fixes
4014 bug 9072; bugfix on 0.2.4.13-alpha.
4016 - Limit hidden service descriptors to at most ten introduction
4017 points, to slow one kind of guard enumeration. Fixes bug 9002;
4018 bugfix on 0.1.1.11-alpha.
4021 Changes in version 0.2.4.13-alpha - 2013-06-14
4022 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
4023 vulnerabilities, makes socks5 username/password circuit isolation
4024 actually actually work (this time for sure!), and cleans up a bunch
4025 of other issues in preparation for a release candidate.
4027 o Major bugfixes (robustness):
4028 - Close any circuit that has too many cells queued on it. Fixes
4029 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
4030 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
4031 - Prevent the get_freelists() function from running off the end of
4032 the list of freelists if it somehow gets an unrecognized
4033 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
4035 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
4036 when an exit connection with optimistic data succeeds immediately
4037 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
4039 - Fix a directory authority crash bug when building a consensus
4040 using an older consensus as its basis. Fixes bug 8833. Bugfix
4044 - Avoid a memory leak where we would leak a consensus body when we
4045 find that a consensus which we couldn't previously verify due to
4046 missing certificates is now verifiable. Fixes bug 8719; bugfix
4048 - We used to always request authority certificates by identity digest,
4049 meaning we'd get the newest one even when we wanted one with a
4050 different signing key. Then we would complain about being given
4051 a certificate we already had, and never get the one we really
4052 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
4053 resource to request the one we want. Fixes bug 5595; bugfix on
4055 - Follow the socks5 protocol when offering username/password
4056 authentication. The fix for bug 8117 exposed this bug, and it
4057 turns out real-world applications like Pidgin do care. Bugfix on
4058 0.2.3.2-alpha; fixes bug 8879.
4059 - Prevent failures on Windows Vista and later when rebuilding the
4060 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
4061 bugfix on 0.2.4.12-alpha.
4064 - Fix an impossible buffer overrun in the AES unit tests. Fixes
4065 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
4066 - If for some reason we fail to write a microdescriptor while
4067 rebuilding the cache, do not let the annotations from that
4068 microdescriptor linger in the cache file, and do not let the
4069 microdescriptor stay recorded as present in its old location.
4070 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
4071 - Fix a memory leak that would occur whenever a configuration
4072 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
4073 - Paste the description for PathBias parameters from the man
4074 page into or.h, so the code documents them too. Fixes bug 7982;
4075 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
4076 - Relays now treat a changed IPv6 ORPort as sufficient reason to
4077 publish an updated descriptor. Fixes bug 6026; bugfix on
4079 - When launching a resolve request on behalf of an AF_UNIX control
4080 socket, omit the address field of the new entry connection, used in
4081 subsequent controller events, rather than letting tor_dup_addr()
4082 set it to "<unknown address type>". Fixes bug 8639; bugfix on
4085 o Minor bugfixes (log messages):
4086 - Fix a scaling issue in the path bias accounting code that
4087 resulted in "Bug:" log messages from either
4088 pathbias_scale_close_rates() or pathbias_count_build_success().
4089 This represents a bugfix on a previous bugfix: the original fix
4090 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
4092 - Give a less useless error message when the user asks for an IPv4
4093 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
4097 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
4098 to tolerate bug 8093 for now.
4099 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
4100 in directory authority votes to describe whether they have enough
4101 measured bandwidths to ignore advertised (relay descriptor)
4102 bandwidth claims. Resolves ticket 8711.
4103 - Update to the June 5 2013 Maxmind GeoLite Country database.
4105 o Removed documentation:
4106 - Remove some of the older contents of doc/ as obsolete; move others
4107 to torspec.git. Fixes bug 8965.
4109 o Code simplification and refactoring:
4110 - Avoid using character buffers when constructing most directory
4111 objects: this approach was unwieldy and error-prone. Instead,
4112 build smartlists of strings, and concatenate them when done.
4115 Changes in version 0.2.4.12-alpha - 2013-04-18
4116 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
4117 process for lengthening the guard rotation period, makes directory
4118 authority opinions in the consensus a bit less gameable, makes socks5
4119 username/password circuit isolation actually work, and fixes a wide
4120 variety of other issues.
4123 - Raise the default time that a client keeps an entry guard from
4124 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
4125 2012 paper. (We would make it even longer, but we need better client
4126 load balancing first.) Also, make the guard lifetime controllable
4127 via a new GuardLifetime torrc option and a GuardLifetime consensus
4128 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
4129 - Directory authorities now prefer using measured bandwidths to
4130 advertised ones when computing flags and thresholds. Resolves
4132 - Directory authorities that have more than a threshold number
4133 of relays with measured bandwidths now treat relays with unmeasured
4134 bandwidths as having bandwidth 0. Resolves ticket 8435.
4136 o Major bugfixes (assert / resource use):
4137 - Avoid a bug where our response to TLS renegotiation under certain
4138 network conditions could lead to a busy-loop, with 100% CPU
4139 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
4140 - Avoid an assertion when we discover that we'd like to write a cell
4141 onto a closing connection: just discard the cell. Fixes another
4142 case of bug 7350; bugfix on 0.2.4.4-alpha.
4144 o Major bugfixes (client-side privacy):
4145 - When we mark a circuit as unusable for new circuits, have it
4146 continue to be unusable for new circuits even if MaxCircuitDirtiness
4147 is increased too much at the wrong time, or the system clock jumps
4148 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
4149 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
4150 which have resolved to internal addresses") is set, apply that
4151 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
4152 - When an exit relay rejects a stream with reason "exit policy", but
4153 we only know an exit policy summary (e.g. from the microdesc
4154 consensus) for it, do not mark the relay as useless for all exiting.
4155 Instead, mark just the circuit as unsuitable for that particular
4156 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
4157 - Allow applications to get proper stream isolation with
4158 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
4159 username/password authentication also offer "no authentication". Tor
4160 had previously preferred "no authentication", so the applications
4161 never actually sent Tor their auth details. Now Tor selects
4162 username/password authentication if it's offered. You can disable
4163 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
4164 bug 8117; bugfix on 0.2.3.3-alpha.
4166 o Major bugfixes (other):
4167 - When unable to find any working directory nodes to use as a
4168 directory guard, give up rather than adding the same non-working
4169 nodes to the directory guard list over and over. Fixes bug 8231;
4170 bugfix on 0.2.4.8-alpha.
4173 - Reject as invalid most directory objects containing a NUL.
4174 Belt-and-suspender fix for bug 8037.
4175 - In our testsuite, create temporary directories with a bit more
4176 entropy in their name to make name collisions less likely. Fixes
4178 - Add CACHED keyword to ADDRMAP events in the control protocol
4179 to indicate whether a DNS result will be cached or not. Resolves
4181 - Update to the April 3 2013 Maxmind GeoLite Country database.
4183 o Minor features (build):
4184 - Detect and reject attempts to build Tor with threading support
4185 when OpenSSL has been compiled without threading support.
4187 - Clarify that when autoconf is checking for nacl, it is checking
4188 specifically for nacl with a fast curve25519 implementation.
4190 - Warn if building on a platform with an unsigned time_t: there
4191 are too many places where Tor currently assumes that time_t can
4192 hold negative values. We'd like to fix them all, but probably
4195 o Minor bugfixes (build):
4196 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
4197 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
4198 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
4199 - Add the old src/or/micro-revision.i filename to CLEANFILES.
4200 On the off chance that somebody has one, it will go away as soon
4201 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
4202 - Build Tor correctly on 32-bit platforms where the compiler can build
4203 but not run code using the "uint128_t" construction. Fixes bug 8587;
4204 bugfix on 0.2.4.8-alpha.
4205 - Fix compilation warning with some versions of clang that would
4206 prefer the -Wswitch-enum compiler flag to warn about switch
4207 statements with missing enum values, even if those switch
4208 statements have a "default:" statement. Fixes bug 8598; bugfix
4211 o Minor bugfixes (protocol):
4212 - Fix the handling of a TRUNCATE cell when it arrives while the
4213 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
4214 - Fix a misframing issue when reading the version numbers in a
4215 VERSIONS cell. Previously we would recognize [00 01 00 02] as
4216 'version 1, version 2, and version 0x100', when it should have
4217 only included versions 1 and 2. Fixes bug 8059; bugfix on
4218 0.2.0.10-alpha. Reported pseudonymously.
4219 - Make the format and order of STREAM events for DNS lookups
4220 consistent among the various ways to launch DNS lookups. Fixes
4221 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
4222 - Correct our check for which versions of Tor support the EXTEND2
4223 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
4224 later, when support was really added in version 0.2.4.8-alpha.
4225 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
4227 o Minor bugfixes (other):
4228 - Correctly store microdescriptors and extrainfo descriptors with
4229 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
4230 Bug reported by "cypherpunks".
4231 - Increase the width of the field used to remember a connection's
4232 link protocol version to two bytes. Harmless for now, since the
4233 only currently recognized versions are one byte long. Reported
4234 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
4235 - If the state file's path bias counts are invalid (presumably from a
4236 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
4237 additional checks and log messages to the scaling of Path Bias
4238 counts, in case there still are remaining issues with scaling.
4239 Should help resolve bug 8235.
4240 - Eliminate several instances where we use "Nickname=ID" to refer to
4241 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
4242 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
4243 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
4245 o Minor bugfixes (syscalls):
4246 - Always check the return values of functions fcntl() and
4247 setsockopt(). We don't believe these are ever actually failing in
4248 practice, but better safe than sorry. Also, checking these return
4249 values should please analysis tools like Coverity. Patch from
4250 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
4251 - Use direct writes rather than stdio when building microdescriptor
4252 caches, in an attempt to mitigate bug 8031, or at least make it
4255 o Minor bugfixes (config):
4256 - When rejecting a configuration because we were unable to parse a
4257 quoted string, log an actual error message. Fixes bug 7950; bugfix
4259 - Behave correctly when the user disables LearnCircuitBuildTimeout
4260 but doesn't tell us what they would like the timeout to be. Fixes
4261 bug 6304; bugfix on 0.2.2.14-alpha.
4262 - When autodetecting the number of CPUs, use the number of available
4263 CPUs in preference to the number of configured CPUs. Inform the
4264 user if this reduces the number of available CPUs. Fixes bug 8002;
4265 bugfix on 0.2.3.1-alpha.
4266 - Make it an error when you set EntryNodes but disable UseGuardNodes,
4267 since it will (surprisingly to some users) ignore EntryNodes. Fixes
4268 bug 8180; bugfix on 0.2.3.11-alpha.
4269 - Allow TestingTorNetworks to override the 4096-byte minimum for
4270 the Fast threshold. Otherwise they can't bootstrap until they've
4271 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
4272 - Fix some logic errors when the user manually overrides the
4273 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
4276 o Minor bugfixes (log messages to help diagnose bugs):
4277 - If we fail to free a microdescriptor because of bug 7164, log
4278 the filename and line number from which we tried to free it.
4279 - Add another diagnostic to the heartbeat message: track and log
4280 overhead that TLS is adding to the data we write. If this is
4281 high, we are sending too little data to SSL_write at a time.
4282 Diagnostic for bug 7707.
4283 - Add more detail to a log message about relaxed timeouts, to help
4285 - Warn more aggressively when flushing microdescriptors to a
4286 microdescriptor cache fails, in an attempt to mitigate bug 8031,
4287 or at least make it more diagnosable.
4288 - Improve debugging output to help track down bug 8185 ("Bug:
4289 outgoing relay cell has n_chan==NULL. Dropping.")
4290 - Log the purpose of a path-bias testing circuit correctly.
4291 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
4293 o Minor bugfixes (0.2.4.x log messages that were too noisy):
4294 - Don't attempt to relax the timeout of already opened 1-hop circuits.
4295 They might never timeout. This should eliminate some/all cases of
4296 the relaxed timeout log message.
4297 - Use circuit creation time for network liveness evaluation. This
4298 should eliminate warning log messages about liveness caused
4299 by changes in timeout evaluation. Fixes bug 6572; bugfix on
4301 - Reduce a path bias length check from notice to info. The message
4302 is triggered when creating controller circuits. Fixes bug 8196;
4303 bugfix on 0.2.4.8-alpha.
4304 - Fix a path state issue that triggered a notice during relay startup.
4305 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
4306 - Reduce occurrences of warns about circuit purpose in
4307 connection_ap_expire_building(). Fixes bug 8477; bugfix on
4310 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
4311 - If we encounter a write failure on a SOCKS connection before we
4312 finish our SOCKS handshake, don't warn that we closed the
4313 connection before we could send a SOCKS reply. Fixes bug 8427;
4314 bugfix on 0.1.0.1-rc.
4315 - Correctly recognize that [::1] is a loopback address. Fixes
4316 bug 8377; bugfix on 0.2.1.3-alpha.
4317 - Fix a directory authority warn caused when we have a large amount
4318 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
4319 - Don't log inappropriate heartbeat messages when hibernating: a
4320 hibernating node is _expected_ to drop out of the consensus,
4321 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
4322 bugfix on 0.2.3.1-alpha.
4323 - Don't complain about bootstrapping problems while hibernating.
4324 These complaints reflect a general code problem, but not one
4325 with any problematic effects (no connections are actually
4326 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
4328 o Documentation fixes:
4329 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
4330 names match. Fixes bug 7768.
4331 - Make the torify manpage no longer refer to tsocks; torify hasn't
4332 supported tsocks since 0.2.3.14-alpha.
4333 - Make the tor manpage no longer reference tsocks.
4334 - Fix the GeoIPExcludeUnknown documentation to refer to
4335 ExcludeExitNodes rather than the currently nonexistent
4336 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
4339 - The tor-tsocks.conf is no longer distributed or installed. We
4340 recommend that tsocks users use torsocks instead. Resolves
4344 Changes in version 0.2.4.11-alpha - 2013-03-11
4345 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
4346 more robust, makes hidden service authentication work again, and
4347 resolves a DPI fingerprint for Tor's SSL transport.
4349 o Major features (directory authorities):
4350 - Directory authorities now support a new consensus method (17)
4351 where they cap the published bandwidth of servers for which
4352 insufficient bandwidth measurements exist. Fixes part of bug 2286.
4353 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
4354 serve any v2 directory information. Now we can test disabling the
4355 old deprecated v2 directory format, and see whether doing so has
4356 any effect on network load. Begins to fix bug 6783.
4357 - Directory authorities now include inside each vote a statement of
4358 the performance thresholds they used when assigning flags.
4359 Implements ticket 8151.
4361 o Major bugfixes (directory authorities):
4362 - Stop marking every relay as having been down for one hour every
4363 time we restart a directory authority. These artificial downtimes
4364 were messing with our Stable and Guard flag calculations. Fixes
4365 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
4367 o Major bugfixes (hidden services):
4368 - Allow hidden service authentication to succeed again. When we
4369 refactored the hidden service introduction code back
4370 in 0.2.4.1-alpha, we didn't update the code that checks
4371 whether authentication information is present, causing all
4372 authentication checks to return "false". Fix for bug 8207; bugfix
4373 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
4375 o Minor features (relays, bridges):
4376 - Make bridge relays check once a minute for whether their IP
4377 address has changed, rather than only every 15 minutes. Resolves
4379 - Refactor resolve_my_address() so it returns the method by which we
4380 decided our public IP address (explicitly configured, resolved from
4381 explicit hostname, guessed from interfaces, learned by gethostname).
4382 Now we can provide more helpful log messages when a relay guesses
4383 its IP address incorrectly (e.g. due to unexpected lines in
4384 /etc/hosts). Resolves ticket 2267.
4385 - Teach bridge-using clients to avoid 0.2.2 bridges when making
4386 microdescriptor-related dir requests, and only fall back to normal
4387 descriptors if none of their bridges can handle microdescriptors
4388 (as opposed to the fix in ticket 4013, which caused them to fall
4389 back to normal descriptors if *any* of their bridges preferred
4390 them). Resolves ticket 4994.
4391 - Randomize the lifetime of our SSL link certificate, so censors can't
4392 use the static value for filtering Tor flows. Resolves ticket 8443;
4393 related to ticket 4014 which was included in 0.2.2.33.
4394 - Support a new version of the link protocol that allows 4-byte circuit
4395 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
4396 a possible resource exhaustion issue. Closes ticket 7351; implements
4399 o Minor features (portability):
4400 - Tweak the curve25519-donna*.c implementations to tolerate systems
4401 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
4402 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
4403 the signs of types during autoconf. This is better than our old
4404 approach, which didn't work when cross-compiling.
4405 - Detect the sign of enum values, rather than assuming that MSC is the
4406 only compiler where enum types are all signed. Fixes bug 7727;
4407 bugfix on 0.2.4.10-alpha.
4409 o Minor features (other):
4410 - Say "KBytes" rather than "KB" in the man page (for various values
4411 of K), to further reduce confusion about whether Tor counts in
4412 units of memory or fractions of units of memory. Resolves ticket 7054.
4413 - Clear the high bit on curve25519 public keys before passing them to
4414 our backend, in case we ever wind up using a backend that doesn't do
4415 so itself. If we used such a backend, and *didn't* clear the high bit,
4416 we could wind up in a situation where users with such backends would
4417 be distinguishable from users without. Fixes bug 8121; bugfix on
4419 - Update to the March 6 2013 Maxmind GeoLite Country database.
4421 o Minor bugfixes (clients):
4422 - When we receive a RELAY_END cell with the reason DONE, or with no
4423 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
4424 status as "connection refused". Previously we reported these cases
4425 as success but then immediately closed the connection. Fixes bug
4426 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
4427 - Downgrade an assertion in connection_ap_expire_beginning to an
4428 LD_BUG message. The fix for bug 8024 should prevent this message
4429 from displaying, but just in case, a warn that we can diagnose
4430 is better than more assert crashes. Fixes bug 8065; bugfix on
4432 - Lower path use bias thresholds to .80 for notice and .60 for warn.
4433 Also make the rate limiting flags for the path use bias log messages
4434 independent from the original path bias flags. Fixes bug 8161;
4435 bugfix on 0.2.4.10-alpha.
4437 o Minor bugfixes (relays):
4438 - Stop trying to resolve our hostname so often (e.g. every time we
4439 think about doing a directory fetch). Now we reuse the cached
4440 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
4441 and 2410 (bugfix on 0.1.2.2-alpha).
4442 - Stop sending a stray "(null)" in some cases for the server status
4443 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
4445 - When choosing which stream on a formerly stalled circuit to wake
4446 first, make better use of the platform's weak RNG. Previously,
4447 we had been using the % ("modulo") operator to try to generate a
4448 1/N chance of picking each stream, but this behaves badly with
4449 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
4451 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
4452 Irix's random() only return 15 bits; Solaris's random() returns more
4453 bits but its RAND_MAX says it only returns 15, and so on. Motivated
4454 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
4456 o Minor bugfixes (directory authorities):
4457 - Directory authorities now use less space when formatting identical
4458 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
4461 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
4462 - Avoid leaking memory if we fail to compute a consensus signature
4463 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
4464 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
4466 - Fix a memory leak during safe-cookie controller authentication.
4467 Bugfix on 0.2.3.13-alpha.
4468 - Avoid memory leak of IPv6 policy content if we fail to format it into
4469 a router descriptor. Bugfix on 0.2.4.7-alpha.
4471 o Minor bugfixes (other code correctness issues):
4472 - Avoid a crash if we fail to generate an extrainfo descriptor.
4473 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
4475 - When detecting the largest possible file descriptor (in order to
4476 close all file descriptors when launching a new program), actually
4477 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
4478 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
4480 - Fix a copy-and-paste error when adding a missing A1 to a routerset
4481 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
4482 Bugfix on 0.2.4.10-alpha.
4483 - Fix an impossible-to-trigger integer overflow when estimating how
4484 long our onionskin queue would take. (This overflow would require us
4485 to accept 4 million onionskins before processing 100 of them.) Fixes
4486 bug 8210; bugfix on 0.2.4.10-alpha.
4488 o Code simplification and refactoring:
4489 - Add a wrapper function for the common "log a message with a
4493 Changes in version 0.2.4.10-alpha - 2013-02-04
4494 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
4495 certain attacks that flood the network with relays; changes the queue
4496 for circuit create requests from a sized-based limit to a time-based
4497 limit; resumes building with MSVC on Windows; and fixes a wide variety
4500 o Major bugfixes (directory authority):
4501 - When computing directory thresholds, ignore any rejected-as-sybil
4502 nodes during the computation so that they can't influence Fast,
4503 Guard, etc. (We should have done this for proposal 109.) Fixes
4505 - When marking a node as a likely sybil, reset its uptime metrics
4506 to zero, so that it cannot time towards getting marked as Guard,
4507 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
4511 - When a TLS write is partially successful but incomplete, remember
4512 that the flushed part has been flushed, and notice that bytes were
4513 actually written. Reported and fixed pseudonymously. Fixes bug
4514 7708; bugfix on Tor 0.1.0.5-rc.
4515 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
4516 ID: these could be used to create unexpected streams and circuits
4517 which would count as "present" to some parts of Tor but "absent"
4518 to others, leading to zombie circuits and streams or to a bandwidth
4519 denial-of-service. Fixes bug 7889; bugfix on every released version
4520 of Tor. Reported by "oftc_must_be_destroyed".
4521 - Rename all macros in our local copy of queue.h to begin with "TOR_".
4522 This change seems the only good way to permanently prevent conflicts
4523 with queue.h on various operating systems. Fixes bug 8107; bugfix
4526 o Major features (relay):
4527 - Instead of limiting the number of queued onionskins (aka circuit
4528 create requests) to a fixed, hard-to-configure number, we limit
4529 the size of the queue based on how many we expect to be able to
4530 process in a given amount of time. We estimate the time it will
4531 take to process an onionskin based on average processing time
4532 of previous onionskins. Closes ticket 7291. You'll never have to
4533 configure MaxOnionsPending again.
4535 o Major features (portability):
4536 - Resume building correctly with MSVC and Makefile.nmake. This patch
4537 resolves numerous bugs and fixes reported by ultramage, including
4538 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
4539 - Make the ntor and curve25519 code build correctly with MSVC.
4540 Fix on 0.2.4.8-alpha.
4543 - When directory authorities are computing thresholds for flags,
4544 never let the threshold for the Fast flag fall below 4096
4545 bytes. Also, do not consider nodes with extremely low bandwidths
4546 when deciding thresholds for various directory flags. This change
4547 should raise our threshold for Fast relays, possibly in turn
4548 improving overall network performance; see ticket 1854. Resolves
4550 - The Tor client now ignores sub-domain components of a .onion
4551 address. This change makes HTTP "virtual" hosting
4552 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
4553 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
4554 hosted on the same hidden service. Implements proposal 204.
4555 - We compute the overhead from passing onionskins back and forth to
4556 cpuworkers, and report it when dumping statistics in response to
4557 SIGUSR1. Supports ticket 7291.
4559 o Minor features (path selection):
4560 - When deciding whether we have enough descriptors to build circuits,
4561 instead of looking at raw relay counts, look at which fraction
4562 of (bandwidth-weighted) paths we're able to build. This approach
4563 keeps clients from building circuits if their paths are likely to
4564 stand out statistically. The default fraction of paths needed is
4565 taken from the consensus directory; you can override it with the
4566 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
4567 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
4568 and we have GeoIP information, also exclude all nodes with unknown
4569 countries "??" and "A1". This behavior is controlled by the
4570 new GeoIPExcludeUnknown option: you can make such nodes always
4571 excluded with "GeoIPExcludeUnknown 1", and disable the feature
4572 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
4573 gets you the default behavior. Implements feature 7706.
4574 - Path Use Bias: Perform separate accounting for successful circuit
4575 use. Keep separate statistics on stream attempt rates versus stream
4576 success rates for each guard. Provide configurable thresholds to
4577 determine when to emit log messages or disable use of guards that
4578 fail too many stream attempts. Resolves ticket 7802.
4580 o Minor features (log messages):
4581 - When learning a fingerprint for a bridge, log its corresponding
4582 transport type. Implements ticket 7896.
4583 - Improve the log message when "Bug/attack: unexpected sendme cell
4584 from client" occurs, to help us track bug 8093.
4587 - Remove a couple of extraneous semicolons that were upsetting the
4588 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4589 bugfix on 0.2.2.1-alpha.
4590 - Remove a source of rounding error during path bias count scaling;
4591 don't count cannibalized circuits as used for path bias until we
4592 actually try to use them; and fix a circuit_package_relay_cell()
4593 warning message about n_chan==NULL. Fixes bug 7802.
4594 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
4595 actually link against nacl when we're configured to use it. Fixes
4596 bug 7972; bugfix on 0.2.4.8-alpha.
4597 - Compile correctly with the --disable-curve25519 option. Fixes
4598 bug 8153; bugfix on 0.2.4.8-alpha.
4600 o Build improvements:
4601 - Do not report status verbosely from autogen.sh unless the -v flag
4602 is specified. Fixes issue 4664. Patch from Onizuka.
4603 - Replace all calls to snprintf() outside of src/ext with
4604 tor_snprintf(). Also remove the #define to replace snprintf with
4605 _snprintf on Windows; they have different semantics, and all of
4606 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
4607 - Try to detect if we are ever building on a platform where
4608 memset(...,0,...) does not set the value of a double to 0.0. Such
4609 platforms are permitted by the C standard, though in practice
4610 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
4611 currently support them, but it's better to detect them and fail
4612 than to perform erroneously.
4615 - Stop exporting estimates of v2 and v3 directory traffic shares
4616 in extrainfo documents. They were unneeded and sometimes inaccurate.
4617 Also stop exporting any v2 directory request statistics. Resolves
4619 - Drop support for detecting and warning about versions of Libevent
4620 before 1.3e. Nothing reasonable ships with them any longer;
4621 warning the user about them shouldn't be needed. Resolves ticket
4624 o Code simplifications and refactoring:
4625 - Rename "isin" functions to "contains", for grammar. Resolves
4627 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
4628 with the natural logarithm function from the system libm. Resolves
4632 Changes in version 0.2.4.9-alpha - 2013-01-15
4633 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
4637 - Fix backward compatibility logic when receiving an embedded ntor
4638 handshake tunneled in a CREATE cell. This clears up the "Bug:
4639 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
4643 Changes in version 0.2.4.8-alpha - 2013-01-14
4644 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
4645 risks, adds a new stronger and faster circuit handshake, and offers
4646 stronger and faster link encryption when both sides support it.
4649 - Preliminary support for directory guards (proposal 207): when
4650 possible, clients now use their entry guards for non-anonymous
4651 directory requests. This can help prevent client enumeration. Note
4652 that this behavior only works when we have a usable consensus
4653 directory, and when options about what to download are more or less
4654 standard. In the future we should re-bootstrap from our guards,
4655 rather than re-bootstrapping from the preconfigured list of
4656 directory sources that ships with Tor. Resolves ticket 6526.
4657 - Tor relays and clients now support a better CREATE/EXTEND cell
4658 format, allowing the sender to specify multiple address, identity,
4659 and handshake types. Implements Robert Ransom's proposal 200;
4662 o Major features (new circuit handshake):
4663 - Tor now supports a new circuit extension handshake designed by Ian
4664 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
4665 circuit extension handshake, later called "TAP", was a bit slow
4666 (especially on the relay side), had a fragile security proof, and
4667 used weaker keys than we'd now prefer. The new circuit handshake
4668 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
4669 function, making it significantly more secure than the older
4670 handshake, and significantly faster. Tor can use one of two built-in
4671 pure-C curve25519-donna implementations by Adam Langley, or it
4672 can link against the "nacl" library for a tuned version if present.
4674 The built-in version is very fast for 64-bit systems when building
4675 with GCC. The built-in 32-bit version is still faster than the
4676 old TAP protocol, but using libnacl is better on most such hosts.
4678 Clients don't currently use this protocol by default, since
4679 comparatively few clients support it so far. To try it, set
4680 UseNTorHandshake to 1.
4682 Implements proposal 216; closes ticket 7202.
4684 o Major features (better link encryption):
4685 - Relays can now enable the ECDHE TLS ciphersuites when available
4686 and appropriate. These ciphersuites let us negotiate forward-secure
4687 TLS secret keys more safely and more efficiently than with our
4688 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
4689 public relays prefer the (faster) P224 group, and bridges prefer
4690 the (more common) P256 group; you can override this with the
4693 Enabling these ciphers was a little tricky, since for a long time,
4694 clients had been claiming to support them without actually doing
4695 so, in order to foil fingerprinting. But with the client-side
4696 implementation of proposal 198 in 0.2.3.17-beta, clients can now
4697 match the ciphers from recent Firefox versions *and* list the
4698 ciphers they actually mean, so relays can believe such clients
4699 when they advertise ECDHE support in their TLS ClientHello messages.
4701 This feature requires clients running 0.2.3.17-beta or later,
4702 and requires both sides to be running OpenSSL 1.0.0 or later
4703 with ECC support. OpenSSL 1.0.1, with the compile-time option
4704 "enable-ec_nistp_64_gcc_128", is highly recommended.
4706 Implements the relay side of proposal 198; closes ticket 7200.
4709 - Avoid crashing when, as a relay without IPv6-exit support, a
4710 client insists on getting an IPv6 address or nothing. Fixes bug
4711 7814; bugfix on 0.2.4.7-alpha.
4714 - Improve circuit build timeout handling for hidden services.
4715 In particular: adjust build timeouts more accurately depending
4716 upon the number of hop-RTTs that a particular circuit type
4717 undergoes. Additionally, launch intro circuits in parallel
4718 if they timeout, and take the first one to reply as valid.
4719 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
4720 separate error codes; or at least, don't break for that reason.
4721 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
4722 - Update to the January 2 2013 Maxmind GeoLite Country database.
4724 o Minor features (testing):
4725 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
4726 (P-256) Diffie-Hellman handshakes to src/or/bench.
4727 - Add benchmark functions to test onion handshake performance.
4729 o Minor features (path bias detection):
4730 - Alter the Path Bias log messages to be more descriptive in terms
4731 of reporting timeouts and other statistics.
4732 - Create three levels of Path Bias log messages, as opposed to just
4733 two. These are configurable via consensus as well as via the torrc
4734 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
4735 The default values are 0.70, 0.50, and 0.30 respectively.
4736 - Separate the log message levels from the decision to drop guards,
4737 which also is available via torrc option PathBiasDropGuards.
4738 PathBiasDropGuards still defaults to 0 (off).
4739 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
4740 in combination with PathBiasExtremeRate.
4741 - Increase the default values for PathBiasScaleThreshold and
4742 PathBiasCircThreshold from (200, 20) to (300, 150).
4743 - Add in circuit usage accounting to path bias. If we try to use a
4744 built circuit but fail for any reason, it counts as path bias.
4745 Certain classes of circuits where the adversary gets to pick your
4746 destination node are exempt from this accounting. Usage accounting
4747 can be specifically disabled via consensus parameter or torrc.
4748 - Convert all internal path bias state to double-precision floating
4749 point, to avoid roundoff error and other issues.
4750 - Only record path bias information for circuits that have completed
4751 *two* hops. Assuming end-to-end tagging is the attack vector, this
4752 makes us more resilient to ambient circuit failure without any
4753 detection capability loss.
4755 o Minor bugfixes (log messages):
4756 - Rate-limit the "No circuits are opened. Relaxed timeout for a
4757 circuit with channel state open..." message to once per hour to
4758 keep it from filling the notice logs. Mitigates bug 7799 but does
4759 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
4760 - Avoid spurious warnings when configuring multiple client ports of
4761 which only some are nonlocal. Previously, we had claimed that some
4762 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
4765 o Code simplifications and refactoring:
4766 - Get rid of a couple of harmless clang warnings, where we compared
4767 enums to ints. These warnings are newly introduced in clang 3.2.
4768 - Split the onion.c file into separate modules for the onion queue
4769 and the different handshakes it supports.
4770 - Remove the marshalling/unmarshalling code for sending requests to
4771 cpuworkers over a socket, and instead just send structs. The
4772 recipient will always be the same Tor binary as the sender, so
4773 any encoding is overkill.
4776 Changes in version 0.2.4.7-alpha - 2012-12-24
4777 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
4778 directory mirrors for more robust bootstrapping; fixes more issues where
4779 clients with changing network conditions refuse to make any circuits;
4780 adds initial support for exiting to IPv6 addresses; resumes being able
4781 to update our GeoIP database, and includes the geoip6 file this time;
4782 turns off the client-side DNS cache by default due to privacy risks;
4783 and fixes a variety of other issues.
4785 o Major features (client resilience):
4786 - Add a new "FallbackDir" torrc option to use when we can't use
4787 a directory mirror from the consensus (either because we lack a
4788 consensus, or because they're all down). Currently, all authorities
4789 are fallbacks by default, and there are no other default fallbacks,
4790 but that will change. This option will allow us to give clients a
4791 longer list of servers to try to get a consensus from when first
4792 connecting to the Tor network, and thereby reduce load on the
4793 directory authorities. Implements proposal 206, "Preconfigured
4794 directory sources for bootstrapping". We also removed the old
4795 "FallbackNetworkstatus" option, since we never got it working well
4796 enough to use it. Closes bug 572.
4797 - If we have no circuits open, use a relaxed timeout (the
4798 95-percentile cutoff) until a circuit succeeds. This heuristic
4799 should allow Tor to succeed at building circuits even when the
4800 network connection drastically changes. Should help with bug 3443.
4802 o Major features (IPv6):
4803 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
4804 connectivity, then set the IPv6Exit flag to 1. Also make sure your
4805 exit policy reads as you would like: the address * applies to all
4806 address families, whereas *4 is IPv4 address only, and *6 is IPv6
4807 addresses only. On the client side, you'll need to wait until the
4808 authorities have upgraded, wait for enough exits to support IPv6,
4809 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
4810 ticket 5547, implements proposal 117 as revised in proposal 208.
4812 We DO NOT recommend that clients with actual anonymity needs start
4813 using IPv6 over Tor yet, since not enough exits support it yet.
4815 o Major features (geoip database):
4816 - Maxmind began labelling Tor relays as being in country "A1",
4817 which breaks by-country node selection inside Tor. Now we use a
4818 script to replace "A1" ("Anonymous Proxy") entries in our geoip
4819 file with real country codes. This script fixes about 90% of "A1"
4820 entries automatically and uses manual country code assignments to
4821 fix the remaining 10%. See src/config/README.geoip for details.
4822 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
4823 Country database, as modified above.
4825 o Major bugfixes (client-side DNS):
4826 - Turn off the client-side DNS cache by default. Updating and using
4827 the DNS cache is now configurable on a per-client-port
4828 level. SOCKSPort, DNSPort, etc lines may now contain
4829 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
4830 cache these types of DNS answers when we receive them from an
4831 exit node in response to an application request on this port, and
4832 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
4833 cached DNS answers of these types, we shouldn't use them. It's
4834 potentially risky to use cached DNS answers at the client, since
4835 doing so can indicate to one exit what answers we've gotten
4836 for DNS lookups in the past. With IPv6, this becomes especially
4837 problematic. Using cached DNS answers for requests on the same
4838 circuit would present less linkability risk, since all traffic
4839 on a circuit is already linkable, but it would also provide
4840 little performance benefit: the exit node caches DNS replies
4841 too. Implements a simplified version of Proposal 205. Implements
4844 o Major bugfixes (other):
4845 - Alter circuit build timeout measurement to start at the point
4846 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
4847 initialization). This should make our timeout measurements more
4848 uniform. Previously, we were sometimes including ORconn setup time
4849 in our circuit build time measurements. Should resolve bug 3443.
4850 - Fix an assertion that could trigger in hibernate_go_dormant() when
4851 closing an or_connection_t: call channel_mark_for_close() rather
4852 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
4854 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
4855 7655; bugfix on 0.2.4.6-alpha.
4858 - Add a new torrc option "ServerTransportListenAddr" to let bridge
4859 operators select the address where their pluggable transports will
4860 listen for connections. Resolves ticket 7013.
4861 - Allow an optional $ before the node identity digest in the
4862 controller command GETINFO ns/id/<identity>, for consistency with
4863 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
4864 - Log packaged cell fullness as part of the heartbeat message.
4865 Diagnosis to try to determine the extent of bug 7743.
4867 o Minor features (IPv6):
4868 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
4869 prefer to hand out virtual IPv6 addresses, since there are more of
4870 them and we can't run out. To override this behavior and make IPv4
4871 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
4872 or DNSPort you're using for resolving. Implements ticket 7571.
4873 - AutomapHostsOnResolve responses are now randomized, to avoid
4874 annoying situations where Tor is restarted and applications
4875 connect to the wrong addresses.
4876 - Never try more than 1000 times to pick a new virtual address when
4877 AutomapHostsOnResolve is set. That's good enough so long as we
4878 aren't close to handing out our entire virtual address space;
4879 if you're getting there, it's best to switch to IPv6 virtual
4883 - The ADDRMAP command can no longer generate an ill-formed error
4884 code on a failed MAPADDRESS. It now says "internal" rather than
4885 an English sentence fragment with spaces in the middle. Bugfix on
4887 - Fix log messages and comments to avoid saying "GMT" when we mean
4888 "UTC". Fixes bug 6113.
4889 - Compile on win64 using mingw64. Fixes bug 7260; patches from
4891 - Fix a crash when debugging unit tests on Windows: deallocate a
4892 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
4893 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
4896 - The DirServer option is now DirAuthority, for consistency with
4897 current naming patterns. You can still use the old DirServer form.
4899 o Code simplification and refactoring:
4900 - Move the client-side address-map/virtual-address/DNS-cache code
4901 out of connection_edge.c into a new addressmap.c module.
4902 - Remove unused code for parsing v1 directories and "running routers"
4903 documents. Fixes bug 6887.
4906 Changes in version 0.2.3.25 - 2012-11-19
4907 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
4908 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4909 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
4910 programmer, and friend. Unstinting in his dedication to the cause of
4911 freedom, he inspired and helped many of us as we began our work on
4912 anonymity, and inspires us still. Please honor his memory by writing
4913 software to protect people's freedoms, and by helping others to do so.
4915 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
4916 significantly reduced directory overhead (via microdescriptors),
4917 enormous crypto performance improvements for fast relays on new
4918 enough hardware, a new v3 TLS handshake protocol that can better
4919 resist fingerprinting, support for protocol obfuscation plugins (aka
4920 pluggable transports), better scalability for hidden services, IPv6
4921 support for bridges, performance improvements like allowing clients
4922 to skip the first round-trip on the circuit ("optimistic data") and
4923 refilling token buckets more often, a new "stream isolation" design
4924 to isolate different applications on different circuits, and many
4925 stability, security, and privacy fixes.
4928 - Tor tries to wipe potentially sensitive data after using it, so
4929 that if some subsequent security failure exposes Tor's memory,
4930 the damage will be limited. But we had a bug where the compiler
4931 was eliminating these wipe operations when it decided that the
4932 memory was no longer visible to a (correctly running) program,
4933 hence defeating our attempt at defense in depth. We fix that
4934 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4935 is unlikely to optimize away. Future versions of Tor may use
4936 a less ridiculously heavy approach for this. Fixes bug 7352.
4937 Reported in an article by Andrey Karpov.
4940 - Fix a harmless bug when opting against publishing a relay descriptor
4941 because DisableNetwork is set. Fixes bug 7464; bugfix on
4945 Changes in version 0.2.4.6-alpha - 2012-11-13
4946 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
4947 makes our defense-in-depth memory wiping more reliable, and begins to
4948 count IPv6 addresses in bridge statistics,
4951 - Fix an assertion failure that could occur when closing a connection
4952 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
4954 - Tor tries to wipe potentially sensitive data after using it, so
4955 that if some subsequent security failure exposes Tor's memory,
4956 the damage will be limited. But we had a bug where the compiler
4957 was eliminating these wipe operations when it decided that the
4958 memory was no longer visible to a (correctly running) program,
4959 hence defeating our attempt at defense in depth. We fix that
4960 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4961 is unlikely to optimize away. Future versions of Tor may use
4962 a less ridiculously heavy approach for this. Fixes bug 7352.
4963 Reported in an article by Andrey Karpov.
4966 - Add GeoIP database for IPv6 addresses. The new config option
4968 - Bridge statistics now count bridge clients connecting over IPv6:
4969 bridge statistics files now list "bridge-ip-versions" and
4970 extra-info documents list "geoip6-db-digest". The control protocol
4971 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
4972 implementation by "shkoo", addressing ticket 5055.
4975 - Warn when we are binding low ports when hibernation is enabled;
4976 previously we had warned when we were _advertising_ low ports with
4977 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
4978 - Fix a harmless bug when opting against publishing a relay descriptor
4979 because DisableNetwork is set. Fixes bug 7464; bugfix on
4981 - Add warning message when a managed proxy dies during configuration.
4982 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
4983 - Fix a linking error when building tor-fw-helper without miniupnp.
4984 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
4985 - Check for closing an or_connection_t without going through correct
4986 channel functions; emit a warning and then call
4987 connection_or_close_for_error() so we don't assert as in bugs 7212
4989 - Compile correctly on compilers without C99 designated initializer
4990 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
4991 - Avoid a possible assert that can occur when channel_send_destroy() is
4992 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
4993 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
4994 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
4995 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
4996 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
4998 o Code simplification and refactoring:
4999 - Start using OpenBSD's implementation of queue.h, so that we don't
5000 need to hand-roll our own pointer and list structures whenever we
5001 need them. (We can't rely on a sys/queue.h, since some operating
5002 systems don't have them, and the ones that do have them don't all
5003 present the same extensions.)
5006 Changes in version 0.2.4.5-alpha - 2012-10-25
5007 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
5008 two important security vulnerabilities that could lead to remotely
5009 triggerable relay crashes, fix a major bug that was preventing clients
5010 from choosing suitable exit nodes, and refactor some of our code.
5012 o Major bugfixes (security, also in 0.2.3.24-rc):
5013 - Fix a group of remotely triggerable assertion failures related to
5014 incorrect link protocol negotiation. Found, diagnosed, and fixed
5015 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5017 - Fix a denial of service attack by which any directory authority
5018 could crash all the others, or by which a single v2 directory
5019 authority could crash everybody downloading v2 directory
5020 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5022 o Major bugfixes (also in 0.2.3.24-rc):
5023 - When parsing exit policy summaries from microdescriptors, we had
5024 previously been ignoring the last character in each one, so that
5025 "accept 80,443,8080" would be treated by clients as indicating
5026 a node that allows access to ports 80, 443, and 808. That would
5027 lead to clients attempting connections that could never work,
5028 and ignoring exit nodes that would support their connections. Now
5029 clients parse these exit policy summaries correctly. Fixes bug 7192;
5030 bugfix on 0.2.3.1-alpha.
5032 o Minor bugfixes (also in 0.2.3.24-rc):
5033 - Clients now consider the ClientRejectInternalAddresses config option
5034 when using a microdescriptor consensus stanza to decide whether
5035 an exit relay would allow exiting to an internal address. Fixes
5036 bug 7190; bugfix on 0.2.3.1-alpha.
5039 - Only disable TLS session ticket support when running as a TLS
5040 server. Now clients will blend better with regular Firefox
5041 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
5043 o Code simplification and refactoring:
5044 - Start using OpenBSD's implementation of queue.h (originally by
5046 - Move the entry node code from circuitbuild.c to its own file.
5047 - Move the circuit build timeout tracking code from circuitbuild.c
5051 Changes in version 0.2.3.24-rc - 2012-10-25
5052 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
5053 could lead to remotely triggerable relay crashes, and fixes
5054 a major bug that was preventing clients from choosing suitable exit
5057 o Major bugfixes (security):
5058 - Fix a group of remotely triggerable assertion failures related to
5059 incorrect link protocol negotiation. Found, diagnosed, and fixed
5060 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5062 - Fix a denial of service attack by which any directory authority
5063 could crash all the others, or by which a single v2 directory
5064 authority could crash everybody downloading v2 directory
5065 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5068 - When parsing exit policy summaries from microdescriptors, we had
5069 previously been ignoring the last character in each one, so that
5070 "accept 80,443,8080" would be treated by clients as indicating
5071 a node that allows access to ports 80, 443, and 808. That would
5072 lead to clients attempting connections that could never work,
5073 and ignoring exit nodes that would support their connections. Now
5074 clients parse these exit policy summaries correctly. Fixes bug 7192;
5075 bugfix on 0.2.3.1-alpha.
5078 - Clients now consider the ClientRejectInternalAddresses config option
5079 when using a microdescriptor consensus stanza to decide whether
5080 an exit relay would allow exiting to an internal address. Fixes
5081 bug 7190; bugfix on 0.2.3.1-alpha.
5084 Changes in version 0.2.4.4-alpha - 2012-10-20
5085 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
5086 vulnerability introduced by a change in OpenSSL, fixes a remotely
5087 triggerable assert, and adds new channel_t and circuitmux_t abstractions
5088 that will make it easier to test new connection transport and cell
5089 scheduling algorithms.
5091 o New directory authorities (also in 0.2.3.23-rc):
5092 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5093 authority. Closes ticket 5749.
5095 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
5096 - Disable TLS session tickets. OpenSSL's implementation was giving
5097 our TLS session keys the lifetime of our TLS context objects, when
5098 perfect forward secrecy would want us to discard anything that
5099 could decrypt a link connection as soon as the link connection
5100 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5101 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5102 - Discard extraneous renegotiation attempts once the V3 link
5103 protocol has been initiated. Failure to do so left us open to
5104 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5105 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5107 o Internal abstraction features:
5108 - Introduce new channel_t abstraction between circuits and
5109 or_connection_t to allow for implementing alternate OR-to-OR
5110 transports. A channel_t is an abstract object which can either be a
5111 cell-bearing channel, which is responsible for authenticating and
5112 handshaking with the remote OR and transmitting cells to and from
5113 it, or a listening channel, which spawns new cell-bearing channels
5114 at the request of remote ORs. Implements part of ticket 6465.
5115 - Also new is the channel_tls_t subclass of channel_t, adapting it
5116 to the existing or_connection_t code. The V2/V3 protocol handshaking
5117 code which formerly resided in command.c has been moved below the
5118 channel_t abstraction layer and may be found in channeltls.c now.
5119 Implements the rest of ticket 6465.
5120 - Introduce new circuitmux_t storing the queue of circuits for
5121 a channel; this encapsulates and abstracts the queue logic and
5122 circuit selection policy, and allows the latter to be overridden
5123 easily by switching out a policy object. The existing EWMA behavior
5124 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5126 o Required libraries:
5127 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5128 strongly recommended.
5131 - Warn users who run hidden services on a Tor client with
5132 UseEntryGuards disabled that their hidden services will be
5133 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5134 attack which motivated Tor to support entry guards in the first
5135 place). Resolves ticket 6889.
5136 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5137 dhill. Resolves ticket 6982.
5138 - Option OutboundBindAddress can be specified multiple times and
5139 accepts IPv6 addresses. Resolves ticket 6876.
5141 o Minor bugfixes (also in 0.2.3.23-rc):
5142 - Don't serve or accept v2 hidden service descriptors over a
5143 relay's DirPort. It's never correct to do so, and disabling it
5144 might make it more annoying to exploit any bugs that turn up in the
5145 descriptor-parsing code. Fixes bug 7149.
5146 - Fix two cases in src/or/transports.c where we were calling
5147 fmt_addr() twice in a parameter list. Bug found by David
5148 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5149 - Fix memory leaks whenever we logged any message about the "path
5150 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5151 - When relays refuse a "create" cell because their queue of pending
5152 create cells is too big (typically because their cpu can't keep up
5153 with the arrival rate), send back reason "resource limit" rather
5154 than reason "internal", so network measurement scripts can get a
5155 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
5158 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
5159 - Free some more still-in-use memory at exit, to make hunting for
5160 memory leaks easier. Resolves bug 7029.
5161 - When a Tor client gets a "truncated" relay cell, the first byte of
5162 its payload specifies why the circuit was truncated. We were
5163 ignoring this 'reason' byte when tearing down the circuit, resulting
5164 in the controller not being told why the circuit closed. Now we
5165 pass the reason from the truncated cell to the controller. Bugfix
5166 on 0.1.2.3-alpha; fixes bug 7039.
5167 - Downgrade "Failed to hand off onionskin" messages to "debug"
5168 severity, since they're typically redundant with the "Your computer
5169 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
5170 - Make clients running with IPv6 bridges connect over IPv6 again,
5171 even without setting new config options ClientUseIPv6 and
5172 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
5173 - Use square brackets around IPv6 addresses in numerous places
5174 that needed them, including log messages, HTTPS CONNECT proxy
5175 requests, TransportProxy statefile entries, and pluggable transport
5176 extra-info lines. Fixes bug 7011; patch by David Fifield.
5178 o Code refactoring and cleanup:
5179 - Source files taken from other packages now reside in src/ext;
5180 previously they were scattered around the rest of Tor.
5181 - Avoid use of reserved identifiers in our C code. The C standard
5182 doesn't like us declaring anything that starts with an
5183 underscore, so let's knock it off before we get in trouble. Fix
5184 for bug 1031; bugfix on the first Tor commit.
5187 Changes in version 0.2.3.23-rc - 2012-10-20
5188 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
5189 vulnerability introduced by a change in OpenSSL, and fixes a variety
5190 of smaller bugs in preparation for the release.
5192 o New directory authorities:
5193 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5194 authority. Closes ticket 5749.
5196 o Major bugfixes (security/privacy):
5197 - Disable TLS session tickets. OpenSSL's implementation was giving
5198 our TLS session keys the lifetime of our TLS context objects, when
5199 perfect forward secrecy would want us to discard anything that
5200 could decrypt a link connection as soon as the link connection
5201 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5202 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5203 - Discard extraneous renegotiation attempts once the V3 link
5204 protocol has been initiated. Failure to do so left us open to
5205 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5206 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5209 - Fix a possible crash bug when checking for deactivated circuits
5210 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5211 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5213 o Minor bugfixes (on 0.2.3.x):
5214 - Fix two cases in src/or/transports.c where we were calling
5215 fmt_addr() twice in a parameter list. Bug found by David
5216 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5217 - Convert an assert in the pathbias code to a log message. The assert
5218 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5219 bugfix on 0.2.3.17-beta.
5220 - Fix memory leaks whenever we logged any message about the "path
5221 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5223 o Minor bugfixes (on 0.2.2.x and earlier):
5224 - Don't serve or accept v2 hidden service descriptors over a relay's
5225 DirPort. It's never correct to do so, and disabling it might
5226 make it more annoying to exploit any bugs that turn up in the
5227 descriptor-parsing code. Fixes bug 7149.
5228 - When relays refuse a "create" cell because their queue of pending
5229 create cells is too big (typically because their cpu can't keep up
5230 with the arrival rate), send back reason "resource limit" rather
5231 than reason "internal", so network measurement scripts can get a
5232 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
5233 - Correct file sizes when reading binary files on Cygwin, to avoid
5234 a bug where Tor would fail to read its state file. Fixes bug 6844;
5235 bugfix on 0.1.2.7-alpha.
5236 - Avoid undefined behavior when parsing the list of supported
5237 rendezvous/introduction protocols in a hidden service descriptor.
5238 Previously, Tor would have confused (as-yet-unused) protocol version
5239 numbers greater than 32 with lower ones on many platforms. Fixes
5240 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5242 o Documentation fixes:
5243 - Clarify that hidden services are TCP only. Fixes bug 6024.
5246 Changes in version 0.2.4.3-alpha - 2012-09-22
5247 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
5248 assertion, resumes letting relays test reachability of their DirPort,
5249 and cleans up a bunch of smaller bugs.
5252 - Fix an assertion failure in tor_timegm() that could be triggered
5253 by a badly formatted directory object. Bug found by fuzzing with
5254 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5257 - Fix a possible crash bug when checking for deactivated circuits
5258 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5259 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5260 - Allow routers to detect that their own DirPorts are running. When
5261 we removed support for versions_supports_begindir, we also
5262 accidentally removed the mechanism we used to self-test our
5263 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
5264 bugfix on 0.2.4.2-alpha.
5266 o Security features:
5267 - Switch to a completely time-invariant approach for picking nodes
5268 weighted by bandwidth. Our old approach would run through the
5269 part of the loop after it had made its choice slightly slower
5270 than it ran through the part of the loop before it had made its
5271 choice. Addresses ticket 6538.
5272 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
5273 by tor2web clients allows hidden services to identify tor2web
5274 clients through their repeated selection of the same rendezvous
5275 and introduction point circuit endpoints (their guards). Resolves
5279 - Enable Tor to read configuration, state, and key information from
5280 a FIFO. Previously Tor would only read from files with a positive
5281 stat.st_size. Code from meejah; fixes bug 6044.
5284 - Correct file sizes when reading binary files on Cygwin, to avoid
5285 a bug where Tor would fail to read its state file. Fixes bug 6844;
5286 bugfix on 0.1.2.7-alpha.
5287 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
5288 bugfix on 0.2.0.3-alpha.
5289 - When complaining about a client port on a public address, log
5290 which address we're complaining about. Fixes bug 4020; bugfix on
5291 0.2.3.3-alpha. Patch by Tom Fitzhenry.
5292 - Convert an assert in the pathbias code to a log message. The assert
5293 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5294 bugfix on 0.2.3.17-beta.
5295 - Our new buildsystem was overzealous about rebuilding manpages: it
5296 would rebuild them all whenever any one of them changed. Now our
5297 dependency checking should be correct. Fixes bug 6843; bugfix on
5299 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
5300 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
5301 - Correct log printout about which address family is preferred
5302 when connecting to a bridge with both an IPv4 and IPv6 OR port.
5303 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
5305 o Minor bugfixes (code cleanliness):
5306 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
5307 with large values. This situation was untriggered, but nevertheless
5308 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
5309 - Reject consensus votes with more than 64 known-flags. We aren't even
5310 close to that limit yet, and our code doesn't handle it correctly.
5311 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
5312 - Avoid undefined behavior when parsing the list of supported
5313 rendezvous/introduction protocols in a hidden service descriptor.
5314 Previously, Tor would have confused (as-yet-unused) protocol version
5315 numbers greater than 32 with lower ones on many platforms. Fixes
5316 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5317 - Fix handling of rendezvous client authorization types over 8.
5318 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
5319 - Fix building with older versions of GCC (2.95, for one) that don't
5320 like preprocessor directives inside macro arguments. Found by
5321 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
5322 - Switch weighted node selection rule from using a list of doubles
5323 to using a list of int64_t. This change should make the process
5324 slightly easier to debug and maintain. Needed to finish ticket 6538.
5326 o Code simplification and refactoring:
5327 - Move the generic "config" code into a new file, and have "config.c"
5328 hold only torrc- and state-related code. Resolves ticket 6823.
5329 - Move the core of our "choose a weighted element at random" logic
5330 into its own function, and give it unit tests. Now the logic is
5331 testable, and a little less fragile too.
5332 - Removed the testing_since field of node_t, which hasn't been used
5333 for anything since 0.2.0.9-alpha.
5335 o Documentation fixes:
5336 - Clarify that hidden services are TCP only. Fixes bug 6024.
5337 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
5341 Changes in version 0.2.3.22-rc - 2012-09-11
5342 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
5346 - Fix an assertion failure in tor_timegm() that could be triggered
5347 by a badly formatted directory object. Bug found by fuzzing with
5348 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5351 - Avoid segfault when starting up having run with an extremely old
5352 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5356 Changes in version 0.2.2.39 - 2012-09-11
5357 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
5361 - Fix an assertion failure in tor_timegm() that could be triggered
5362 by a badly formatted directory object. Bug found by fuzzing with
5363 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5364 - Do not crash when comparing an address with port value 0 to an
5365 address policy. This bug could have been used to cause a remote
5366 assertion failure by or against directory authorities, or to
5367 allow some applications to crash clients. Fixes bug 6690; bugfix
5371 Changes in version 0.2.4.2-alpha - 2012-09-10
5372 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
5373 raises the default rate limiting even more, and makes the bootstrapping
5374 log messages less noisy.
5377 - Automatically forward the TCP ports of pluggable transport
5378 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5382 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5383 to 1GB/1GB. The previous defaults were intended to be "basically
5384 infinite", but it turns out they're now limiting our 100mbit+
5385 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5386 last time we raised it).
5389 - Detect when we're running with a version of OpenSSL other than the
5390 one we compiled with. This has occasionally given people hard-to-
5392 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5393 versions and capabilities when everything is going right. Resolves
5394 part of ticket 6736.
5395 - Directory authorities no long accept descriptors for any version of
5396 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5397 These versions are insecure, unsupported, or both. Implements
5401 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
5402 to start with a triple-underscore so the controller won't touch it.
5403 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
5404 - Avoid segfault when starting up having run with an extremely old
5405 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5407 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
5408 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
5409 - Don't follow the NULL pointer if microdescriptor generation fails.
5410 (This does not appear to be triggerable, but it's best to be safe.)
5411 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
5412 - Fix mis-declared dependencies on src/common/crypto.c and
5413 src/or/tor_main.c that could break out-of-tree builds under some
5414 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
5415 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
5416 6778; bugfix on 0.2.4.1-alpha.
5417 - Fix a harmless (in this case) build warning for implicitly
5418 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
5421 - Now that all versions before 0.2.2.x are disallowed, we no longer
5422 need to work around their missing features. Thus we can remove a
5423 bunch of compatibility code.
5426 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5427 TCP ports to forward. In the past it only accepted two ports:
5428 the ORPort and the DirPort.
5431 Changes in version 0.2.4.1-alpha - 2012-09-05
5432 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
5433 bridgedb; lets relays use IPv6 addresses and directory authorities
5434 advertise them; and switches to a cleaner build interface.
5436 This is the first alpha release in a new series, so expect there to
5437 be bugs. Users who would rather test out a more stable branch should
5438 stay with 0.2.3.x for now.
5440 o Major features (bridges):
5441 - Bridges now report the pluggable transports they support to the
5442 bridge authority, so it can pass the supported transports on to
5443 bridgedb and/or eventually do reachability testing. Implements
5446 o Major features (IPv6):
5447 - Bridge authorities now accept IPv6 bridge addresses and include
5448 them in network status documents. Implements ticket 5534.
5449 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5450 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5451 to happen. Implements ticket 5535.
5452 - All kind of relays, not just bridges, can now advertise an IPv6
5453 OR port. Implements ticket 6362.
5454 - Directory authorities vote on IPv6 OR ports using the new consensus
5455 method 14. Implements ticket 6363.
5457 o Major features (build):
5458 - Switch to a nonrecursive Makefile structure. Now instead of each
5459 Makefile.am invoking other Makefile.am's, there is a master
5460 Makefile.am that includes the others. This change makes our build
5461 process slightly more maintainable, and improves parallelism for
5462 building with make -j. Original patch by Stewart Smith; various
5463 fixes by Jim Meyering.
5464 - Where available, we now use automake's "silent" make rules by
5465 default, so that warnings are easier to spot. You can get the old
5466 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5468 o Minor features (code security and spec conformance):
5469 - Clear keys and key-derived material left on the stack in
5470 rendservice.c and rendclient.c. Check return value of
5471 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5472 These fixes should make us more forward-secure against cold-boot
5473 attacks and the like. Fixes bug 2385.
5474 - Reject EXTEND cells sent to nonexistent streams. According to the
5475 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5476 we were only checking for stream IDs that were currently in use.
5477 Found while hunting for more instances of bug 6271. Bugfix on
5478 0.0.2pre8, which introduced incremental circuit construction.
5480 o Minor features (streamlining);
5481 - No longer include the "opt" prefix when generating routerinfos
5482 or v2 directories: it has been needless since Tor 0.1.2. Closes
5484 - Remove some now-needless code that tried to aggressively flush
5485 OR connections as data was added to them. Since 0.2.0.1-alpha, our
5486 cell queue logic has saved us from the failure mode that this code
5487 was supposed to prevent. Removing this code will limit the number
5488 of baroque control flow paths through Tor's network logic. Reported
5489 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
5491 o Minor features (controller):
5492 - Add a "GETINFO signal/names" control port command. Implements
5494 - Provide default values for all options via "GETINFO config/defaults".
5495 Implements ticket 4971.
5497 o Minor features (IPv6):
5498 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5499 authorities should set if they have IPv6 connectivity and want to
5500 do reachability tests for IPv6 relays. Implements feature 5974.
5501 - A relay with an IPv6 OR port now sends that address in NETINFO
5502 cells (in addition to its other address). Implements ticket 6364.
5504 o Minor features (log messages):
5505 - Omit the first heartbeat log message, because it never has anything
5506 useful to say, and it clutters up the bootstrapping messages.
5507 Resolves ticket 6758.
5508 - Don't log about reloading the microdescriptor cache at startup. Our
5509 bootstrap warnings are supposed to tell the user when there's a
5510 problem, and our bootstrap notices say when there isn't. Resolves
5511 ticket 6759; bugfix on 0.2.2.6-alpha.
5512 - Don't log "I learned some more directory information" when we're
5513 reading cached directory information. Reserve it for when new
5514 directory information arrives in response to a fetch. Resolves
5516 - Prevent rounding error in path bias counts when scaling
5517 them down, and use the correct scale factor default. Also demote
5518 some path bias related log messages down a level and make others
5519 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
5520 - We no longer warn so much when generating manpages from their
5523 o Code simplifications and refactoring:
5524 - Enhance our internal sscanf replacement so that we can eliminate
5525 the last remaining uses of the system sscanf. (Though those uses
5526 of sscanf were safe, sscanf itself is generally error prone, so
5527 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
5529 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
5530 - Move last_reachable and testing_since from routerinfo_t to node_t.
5531 Implements ticket 5529.
5532 - Add replaycache_t structure, functions and unit tests, then refactor
5533 rend_service_introduce() to be more clear to read, improve, debug,
5534 and test. Resolves bug 6177.
5535 - Finally remove support for malloc_good_size and malloc_usable_size.
5536 We had hoped that these functions would let us eke a little more
5537 memory out of our malloc implementation. Unfortunately, the only
5538 implementations that provided these functions are also ones that
5539 are already efficient about not overallocation: they never got us
5540 more than 7 or so bytes per allocation. Removing them saves us a
5541 little code complexity and a nontrivial amount of build complexity.
5544 - Tor maintainers now require Automake version 1.9 or later to build
5545 Tor from the Git repository. (Automake is not required when building
5546 from a source distribution.)
5549 Changes in version 0.2.3.21-rc - 2012-09-05
5550 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
5551 series. It fixes a trio of potential security bugs, fixes a bug where
5552 we were leaving some of the fast relays out of the microdescriptor
5553 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
5554 and cleans up other smaller issues.
5556 o Major bugfixes (security):
5557 - Tear down the circuit if we get an unexpected SENDME cell. Clients
5558 could use this trick to make their circuits receive cells faster
5559 than our flow control would have allowed, or to gum up the network,
5560 or possibly to do targeted memory denial-of-service attacks on
5561 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
5562 from July 2002, before the release of Tor 0.0.0. We had committed
5563 this patch previously, but we had to revert it because of bug 6271.
5564 Now that 6271 is fixed, this patch appears to work.
5565 - Reject any attempt to extend to an internal address. Without
5566 this fix, a router could be used to probe addresses on an internal
5567 network to see whether they were accepting connections. Fixes bug
5568 6710; bugfix on 0.0.8pre1.
5569 - Do not crash when comparing an address with port value 0 to an
5570 address policy. This bug could have been used to cause a remote
5571 assertion failure by or against directory authorities, or to
5572 allow some applications to crash clients. Fixes bug 6690; bugfix
5576 - Remove the upper bound on microdescriptor length. We were hitting
5577 the limit for routers with complex exit policies or family
5578 declarations, causing clients to not use them. Fixes the first
5579 piece of bug 6404; fix on 0.2.2.6-alpha.
5580 - Detect "ORPort 0" as meaning, uniformly, that we're not running
5581 as a relay. Previously, some of our code would treat the presence
5582 of any ORPort line as meaning that we should act like a relay,
5583 even though our new listener code would correctly not open any
5584 ORPorts for ORPort 0. Similar bugs in other Port options are also
5585 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
5588 - Avoid a pair of double-free and use-after-mark bugs that can
5589 occur with certain timings in canceled and re-received DNS
5590 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
5591 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
5592 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
5593 - Allow one-hop directory fetching circuits the full "circuit build
5594 timeout" period, rather than just half of it, before failing them
5595 and marking the relay down. This fix should help reduce cases where
5596 clients declare relays (or worse, bridges) unreachable because
5597 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
5598 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
5600 - Authorities no longer include any router in their microdescriptor
5601 consensuses for which they couldn't generate or agree on a
5602 microdescriptor. Fixes the second piece of bug 6404; fix on
5604 - Detect and reject attempts to specify both "FooPort" and
5605 "FooPort 0" in the same configuration domain. (It's still okay
5606 to have a FooPort in your configuration file, and use "FooPort 0"
5607 on the command line to disable it.) Fixes the second half of bug
5608 6507; bugfix on 0.2.3.3-alpha.
5609 - Make wildcarded addresses (that is, ones beginning with "*.") work
5610 when provided via the controller's MapAddress command. Previously,
5611 they were accepted, but we never actually noticed that they were
5612 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
5613 - Avoid crashing on a malformed state file where EntryGuardPathBias
5614 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
5615 - Add a (probably redundant) memory clear between iterations of
5616 the router status voting loop, to prevent future coding errors
5617 where data might leak between iterations of the loop. Resolves
5620 o Minor bugfixes (log messages):
5621 - Downgrade "set buildtimeout to low value" messages to "info"
5622 severity; they were never an actual problem, there was never
5623 anything reasonable to do about them, and they tended to spam logs
5624 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
5625 - Downgrade path-bias warning messages to "info". We'll try to get
5626 them working better in 0.2.4. Add internal circuit construction
5627 state to protect against the noisy warn message "Unexpectedly high
5628 circuit_successes". Also add some additional rate-limited notice
5629 messages to help determine the root cause of the warn. Fixes bug
5630 6475. Bugfix against 0.2.3.17-beta.
5631 - Move log message when unable to find a microdesc in a routerstatus
5632 entry to parse time. Previously we'd spam this warning every time
5633 we tried to figure out which microdescriptors to download. Fixes
5634 the third piece of bug 6404; fix on 0.2.3.18-rc.
5637 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
5638 change when the authority is deciding whether to accept a newly
5639 uploaded descriptor. Implements ticket 6423.
5640 - Add missing documentation for consensus and microdesc files.
5641 Resolves ticket 6732.
5644 Changes in version 0.2.2.38 - 2012-08-12
5645 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
5646 attack that could in theory leak path information.
5649 - Avoid an uninitialized memory read when reading a vote or consensus
5650 document that has an unrecognized flavor name. This read could
5651 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5652 - Try to leak less information about what relays a client is
5653 choosing to a side-channel attacker. Previously, a Tor client would
5654 stop iterating through the list of available relays as soon as it
5655 had chosen one, thus finishing a little earlier when it picked
5656 a router earlier in the list. If an attacker can recover this
5657 timing information (nontrivial but not proven to be impossible),
5658 they could learn some coarse-grained information about which relays
5659 a client was picking (middle nodes in particular are likelier to
5660 be affected than exits). The timing attack might be mitigated by
5661 other factors (see bug 6537 for some discussion), but it's best
5662 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5665 Changes in version 0.2.3.20-rc - 2012-08-05
5666 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
5667 series. It fixes a pair of code security bugs and a potential anonymity
5668 issue, updates our RPM spec files, and cleans up other smaller issues.
5671 - Avoid read-from-freed-memory and double-free bugs that could occur
5672 when a DNS request fails while launching it. Fixes bug 6480;
5673 bugfix on 0.2.0.1-alpha.
5674 - Avoid an uninitialized memory read when reading a vote or consensus
5675 document that has an unrecognized flavor name. This read could
5676 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5677 - Try to leak less information about what relays a client is
5678 choosing to a side-channel attacker. Previously, a Tor client would
5679 stop iterating through the list of available relays as soon as it
5680 had chosen one, thus finishing a little earlier when it picked
5681 a router earlier in the list. If an attacker can recover this
5682 timing information (nontrivial but not proven to be impossible),
5683 they could learn some coarse-grained information about which relays
5684 a client was picking (middle nodes in particular are likelier to
5685 be affected than exits). The timing attack might be mitigated by
5686 other factors (see bug 6537 for some discussion), but it's best
5687 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5690 - Try to make the warning when giving an obsolete SOCKSListenAddress
5691 a little more useful.
5692 - Terminate active server managed proxies if Tor stops being a
5693 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
5694 - Provide a better error message about possible OSX Asciidoc failure
5695 reasons. Fixes bug 6436.
5696 - Warn when Tor is configured to use accounting in a way that can
5697 link a hidden service to some other hidden service or public
5698 address. Resolves ticket 6490.
5701 - Check return value of fputs() when writing authority certificate
5702 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
5703 - Ignore ServerTransportPlugin lines when Tor is not configured as
5704 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
5705 - When disabling guards for having too high a proportion of failed
5706 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
5710 - Update our default RPM spec files to work with mock and rpmbuild
5711 on RHEL/Fedora. They have an updated set of dependencies and
5712 conflicts, a fix for an ancient typo when creating the "_tor"
5713 user, and better instructions. Thanks to Ondrej Mikle for the
5714 patch series. Fixes bug 6043.
5717 - Make it possible to set the TestingTorNetwork configuration
5718 option using AlternateDirAuthority and AlternateBridgeAuthority
5719 as an alternative to setting DirServer. Addresses ticket 6377.
5722 - Clarify the documentation for the Alternate*Authority options.
5724 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
5726 o Code simplification and refactoring:
5727 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
5728 10 lines. Also, don't nest them. Doing so in the past has
5729 led to hard-to-debug code. The new style is to use the
5730 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
5733 Changes in version 0.2.3.19-rc - 2012-07-06
5734 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
5735 series. It fixes the compile on Windows, reverts to a GeoIP database
5736 that isn't as broken, and fixes a flow control bug that has been around
5737 since the beginning of Tor.
5740 - Fix a bug handling SENDME cells on nonexistent streams that could
5741 result in bizarre window values. Report and patch contributed
5742 pseudonymously. Fixes part of bug 6271. This bug was introduced
5743 before the first Tor release, in svn commit r152.
5744 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
5745 June 2012 database, Maxmind marked many Tor relays as country "A1",
5746 which will cause risky behavior for clients that set EntryNodes
5747 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
5748 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
5749 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
5752 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
5753 bugfix on 0.2.1.10-alpha.
5756 Changes in version 0.2.3.18-rc - 2012-06-28
5757 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
5758 series. It fixes a few smaller bugs, but generally appears stable.
5759 Please test it and let us know whether it is!
5762 - Allow wildcarded mapaddress targets to be specified on the
5763 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
5764 - Make our linker option detection code more robust against linkers
5765 such as on FreeBSD 8, where a bad combination of options completes
5766 successfully but makes an unrunnable binary. Fixes bug 6173;
5767 bugfix on 0.2.3.17-beta.
5769 o Minor bugfixes (on 0.2.2.x and earlier):
5770 - Avoid a false positive in the util/threads unit test by increasing
5771 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
5772 - Replace "Sending publish request" log messages with "Launching
5773 upload", so that they no longer confusingly imply that we're
5774 sending something to a directory we might not even be connected
5775 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
5776 - Make sure to set *socket_error in all error cases in
5777 connection_connect(), so it can't produce a warning about
5778 errno being zero from errno_to_orconn_end_reason(). Bugfix on
5779 0.2.1.1-alpha; resolves ticket 6028.
5780 - Downgrade "Got a certificate, but we already have it" log messages
5781 from warning to info, except when we're a dirauth. Fixes bug 5238;
5782 bugfix on 0.2.1.7-alpha.
5783 - When checking for requested signatures on the latest consensus
5784 before serving it to a client, make sure to check the right
5785 consensus flavor. Bugfix on 0.2.2.6-alpha.
5786 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
5787 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
5789 o Minor bugfixes (on 0.2.3.x):
5790 - Make format_helper_exit_status() avoid unnecessary space padding
5791 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
5793 - Downgrade a message about cleaning the microdescriptor cache to
5794 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
5795 - Log a BUG message at severity INFO if we have a networkstatus with
5796 a missing entry for some microdescriptor. Continues on a patch
5798 - Improve the log message when a managed proxy fails to launch. Fixes
5799 bug 5099; bugfix on 0.2.3.6-alpha.
5800 - Don't do DNS lookups when parsing corrupted managed proxy protocol
5801 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
5802 - When formatting wildcarded address mappings for the controller,
5803 be sure to include "*." as appropriate. Partially fixes bug 6244;
5804 bugfix on 0.2.3.9-alpha.
5805 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
5806 Bugfix on 0.2.3.13-alpha.
5807 - Stop logging messages about running with circuit timeout learning
5808 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
5809 - Disable a spurious warning about reading on a marked and flushing
5810 connection. We shouldn't be doing that, but apparently we
5811 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
5812 - Fix a bug that stopped AllowDotExit from working on addresses
5813 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
5816 o Code simplification, refactoring, unit tests:
5817 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
5818 Libevent's notion of cached time when possible.
5819 - Remove duplicate code for invoking getrlimit() from control.c.
5820 - Add a unit test for the environment_variable_names_equal function.
5823 - Document the --defaults-torrc option, and the new (in 0.2.3)
5824 semantics for overriding, extending, and clearing lists of
5825 options. Closes bug 4748.
5828 Changes in version 0.2.3.17-beta - 2012-06-15
5829 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
5830 gets our TLS handshake back on track for being able to blend in with
5831 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
5832 with Vidalia, and otherwise continues to get us closer to a release
5836 - Enable gcc and ld hardening by default. Resolves ticket 5210.
5837 - Update TLS cipher list to match Firefox 8 and later. Resolves
5839 - Implement the client side of proposal 198: remove support for
5840 clients falsely claiming to support standard ciphersuites that
5841 they can actually provide. As of modern OpenSSL versions, it's not
5842 necessary to fake any standard ciphersuite, and doing so prevents
5843 us from using better ciphersuites in the future, since servers
5844 can't know whether an advertised ciphersuite is really supported or
5845 not. Some hosts -- notably, ones with very old versions of OpenSSL
5846 or where OpenSSL has been built with ECC disabled -- will stand
5847 out because of this change; TBB users should not be affected.
5850 - Change the default value for DynamicDHGroups (introduced in
5851 0.2.3.9-alpha) to 0. This feature can make Tor relays less
5852 identifiable by their use of the mod_ssl DH group, but at
5853 the cost of some usability (#4721) and bridge tracing (#6087)
5854 regressions. Resolves ticket 5598.
5855 - Send a CRLF at the end of each STATUS_* control protocol event. This
5856 bug tickled a bug in Vidalia which would make it freeze. Fixes
5857 bug 6094; bugfix on 0.2.3.16-alpha.
5860 - Disable writing on marked-for-close connections when they are
5861 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
5862 bug 5263; bugfix on 0.0.2pre13, where we first added a special
5863 case for flushing marked connections.
5864 - Detect SSL handshake even when the initial attempt to write the
5865 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
5866 - Change the AllowDotExit rules so they should actually work.
5867 We now enforce AllowDotExit only immediately after receiving an
5868 address via SOCKS or DNSPort: other sources are free to provide
5869 .exit addresses after the resolution occurs. Fixes bug 3940;
5870 bugfix on 0.2.2.1-alpha.
5871 - Fix a (harmless) integer overflow in cell statistics reported by
5872 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
5873 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
5874 right places and never depends on the consensus parameters or
5875 computes adaptive timeouts when it is disabled. Fixes bug 5049;
5876 bugfix on 0.2.2.14-alpha.
5877 - When building Tor on Windows with -DUNICODE (not default), ensure
5878 that error messages, filenames, and DNS server names are always
5879 NUL-terminated when we convert them to a single-byte encoding.
5880 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
5881 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
5882 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
5883 - Fix an edge case where TestingTorNetwork is set but the authorities
5884 and relays all have an uptime of zero, where the private Tor network
5885 could briefly lack support for hidden services. Fixes bug 3886;
5886 bugfix on 0.2.2.18-alpha.
5887 - Correct the manpage's descriptions for the default values of
5888 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
5890 - Fix the documentation for the --hush and --quiet command line
5891 options, which changed their behavior back in 0.2.3.3-alpha.
5892 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
5896 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
5897 more information to it, so that we can track it down in case it
5898 returns again. Mitigates bug 5235.
5899 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
5900 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
5901 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
5902 - Warn the user when HTTPProxy, but no other proxy type, is
5903 configured. This can cause surprising behavior: it doesn't send
5904 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
5905 directory traffic only. Resolves ticket 4663.
5906 - Issue a notice if a guard completes less than 40% of your circuits.
5907 Threshold is configurable by torrc option PathBiasNoticeRate and
5908 consensus parameter pb_noticepct. There is additional, off-by-
5909 default code to disable guards which fail too many circuits.
5910 Addresses ticket 5458.
5911 - Update to the June 6 2012 Maxmind GeoLite Country database.
5913 o Code simplifications and refactoring:
5914 - Remove validate_pluggable_transports_config(): its warning
5915 message is now handled by connection_or_connect().
5918 Changes in version 0.2.2.37 - 2012-06-06
5919 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
5920 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5924 - Work around a bug in OpenSSL that broke renegotiation with TLS
5925 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5926 the v2 Tor connection protocol when both sides were using OpenSSL
5927 1.0.1 would fail. Resolves ticket 6033.
5928 - When waiting for a client to renegotiate, don't allow it to add
5929 any bytes to the input buffer. This fixes a potential DoS issue.
5930 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5931 - Fix an edge case where if we fetch or publish a hidden service
5932 descriptor, we might build a 4-hop circuit and then use that circuit
5933 for exiting afterwards -- even if the new last hop doesn't obey our
5934 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5937 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5938 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5941 - Tell GCC and Clang to check for any errors in format strings passed
5942 to the tor_v*(print|scan)f functions.
5945 Changes in version 0.2.3.16-alpha - 2012-06-05
5946 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
5947 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5948 currently). It also fixes a variety of smaller bugs and other cleanups
5949 that get us closer to a release candidate.
5951 o Major bugfixes (general):
5952 - Work around a bug in OpenSSL that broke renegotiation with TLS
5953 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5954 the v2 Tor connection protocol when both sides were using OpenSSL
5955 1.0.1 would fail. Resolves ticket 6033.
5956 - When waiting for a client to renegotiate, don't allow it to add
5957 any bytes to the input buffer. This fixes a potential DoS issue.
5958 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5959 - Pass correct OR address to managed proxies (like obfsproxy),
5960 even when ORListenAddress is used. Fixes bug 4865; bugfix on
5962 - The advertised platform of a router now includes only its operating
5963 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
5964 service pack level (for Windows) or its CPU architecture (for Unix).
5965 We also no longer include the "git-XYZ" tag in the version. Resolves
5968 o Major bugfixes (clients):
5969 - If we are unable to find any exit that supports our predicted ports,
5970 stop calling them predicted, so that we don't loop and build
5971 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
5972 which introduced predicted ports.
5973 - Fix an edge case where if we fetch or publish a hidden service
5974 descriptor, we might build a 4-hop circuit and then use that circuit
5975 for exiting afterwards -- even if the new last hop doesn't obey our
5976 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5977 - Check at each new consensus whether our entry guards were picked
5978 long enough ago that we should rotate them. Previously, we only
5979 did this check at startup, which could lead to us holding a guard
5980 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
5981 - When fetching a bridge descriptor from a bridge authority,
5982 always do so anonymously, whether we have been able to open
5983 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
5984 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
5985 but we'll need to wait for bug 6010 before it's actually usable.
5987 o Major bugfixes (directory authorities):
5988 - When computing weight parameters, behave more robustly in the
5989 presence of a bad bwweightscale value. Previously, the authorities
5990 would crash if they agreed on a sufficiently broken weight_scale
5991 value: now, they use a reasonable default and carry on. Partial
5992 fix for 5786; bugfix on 0.2.2.17-alpha.
5993 - Check more thoroughly to prevent a rogue authority from
5994 double-voting on any consensus directory parameter. Previously,
5995 authorities would crash in this case if the total number of
5996 votes for any parameter exceeded the number of active voters,
5997 but would let it pass otherwise. Partial fix for bug 5786; bugfix
6001 - Rate-limit log messages when asked to connect anonymously to
6002 a private address. When these hit, they tended to hit fast and
6003 often. Also, don't bother trying to connect to addresses that we
6004 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
6005 reply makes us think we have been lied to, even when the address the
6006 client tried to connect to was "localhost." Resolves ticket 2822.
6007 - Allow packagers to insert an extra string in server descriptor
6008 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
6009 Resolves the rest of ticket 2988.
6010 - Raise the threshold of server descriptors needed (75%) and exit
6011 server descriptors needed (50%) before we will declare ourselves
6012 bootstrapped. This will make clients start building circuits a
6013 little later, but makes the initially constructed circuits less
6014 skewed and less in conflict with further directory fetches. Fixes
6016 - Close any connection that sends unrecognized junk before the
6017 handshake. Solves an issue noted in bug 4369.
6018 - Improve log messages about managed transports. Resolves ticket 5070.
6019 - Tag a bridge's descriptor as "never to be sent unencrypted".
6020 This shouldn't matter, since bridges don't open non-anonymous
6021 connections to the bridge authority and don't allow unencrypted
6022 directory connections from clients, but we might as well make
6023 sure. Closes bug 5139.
6024 - Expose our view of whether we have gone dormant to the controller,
6025 via a new "GETINFO dormant" value. Torbutton and other controllers
6026 can use this to avoid doing periodic requests through Tor while
6027 it's dormant (bug 4718). Fixes bug 5954.
6028 - Tell GCC and Clang to check for any errors in format strings passed
6029 to the tor_v*(print|scan)f functions.
6030 - Update to the May 1 2012 Maxmind GeoLite Country database.
6032 o Minor bugfixes (already included in 0.2.2.36):
6033 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6034 Fixes bug 5346; bugfix on 0.0.8pre3.
6035 - Correct parsing of certain date types in parse_http_time().
6036 Without this patch, If-Modified-Since would behave
6037 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6038 Esteban Manchado Velázques.
6039 - Make our number-parsing functions always treat too-large values
6040 as an error, even when those values exceed the width of the
6041 underlying type. Previously, if the caller provided these
6042 functions with minima or maxima set to the extreme values of the
6043 underlying integer type, these functions would return those
6044 values on overflow rather than treating overflow as an error.
6045 Fixes part of bug 5786; bugfix on 0.0.9.
6046 - If we hit the error case where routerlist_insert() replaces an
6047 existing (old) server descriptor, make sure to remove that
6048 server descriptor from the old_routers list. Fix related to bug
6049 1776. Bugfix on 0.2.2.18-alpha.
6050 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6051 circuits. Fixes issue 5259.
6053 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
6054 - Prevent a null-pointer dereference when receiving a data cell
6055 for a nonexistent stream when the circuit in question has an
6056 empty deliver window. We don't believe this is triggerable,
6057 since we don't currently allow deliver windows to become empty,
6058 but the logic is tricky enough that it's better to make the code
6059 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6060 - Fix a memory leak when trying to launch a DNS request when the
6061 network is disabled or the nameservers are unconfigurable. Fixes
6062 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
6063 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
6064 - Don't hold a Windows file handle open for every file mapping;
6065 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
6067 - Avoid O(n^2) performance characteristics when parsing a large
6068 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6069 - Format more doubles with %f, not %lf. Patch from grarpamp to make
6070 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
6072 - Make our replacement implementation of strtok_r() compatible with
6073 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6074 bugfix on 0.2.2.1-alpha.
6075 - Fix a NULL-pointer dereference on a badly formed
6076 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
6077 bugfix on 0.2.2.9-alpha.
6078 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6079 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6080 - Defensively refactor rend_mid_rendezvous() so that protocol
6081 violations and length checks happen in the beginning. Fixes
6083 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
6084 that IPv6 stuff will compile on MSVC, and compilation issues
6085 will be easier to track down. Fixes bug 5861.
6087 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
6088 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
6089 resource exhaustion, so that clients can adjust their load to
6090 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
6091 started using END_STREAM_REASON_RESOURCELIMIT.
6092 - Don't check for whether the address we're using for outbound
6093 connections has changed until after the outbound connection has
6094 completed. On Windows, getsockname() doesn't succeed until the
6095 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
6096 - If the configuration tries to set MyFamily on a bridge, refuse to
6097 do so, and warn about the security implications. Fixes bug 4657;
6098 bugfix on 0.2.0.3-alpha.
6099 - If the client fails to set a reasonable set of ciphersuites
6100 during its v2 handshake renegotiation, allow the renegotiation to
6101 continue nevertheless (i.e. send all the required certificates).
6102 Fixes bug 4591; bugfix on 0.2.0.20-rc.
6103 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
6104 option is set to 0 (which Vidalia version 0.2.16 now does when
6105 a SAVECONF attempt fails), perform other actions that SIGHUP
6106 usually causes (like reopening the logs). Fixes bug 5095; bugfix
6108 - If we fail to write a microdescriptor to the disk cache, do not
6109 continue replacing the old microdescriptor file. Fixes bug 2954;
6110 bugfix on 0.2.2.6-alpha.
6111 - Exit nodes don't need to fetch certificates for authorities that
6112 they don't recognize; only directory authorities, bridges,
6113 and caches need to do that. Fixes part of bug 2297; bugfix on
6115 - Correctly handle checking the permissions on the parent
6116 directory of a control socket in the root directory. Bug found
6117 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
6119 - When told to add a bridge with the same digest as a preexisting
6120 bridge but a different addr:port, change the addr:port as
6121 requested. Previously we would not notice the change. Fixes half
6122 of bug 5603; fix on 0.2.2.26-beta.
6123 - End AUTHCHALLENGE error messages (in the control protocol) with
6124 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
6126 o Minor bugfixes (on 0.2.3.x):
6127 - Turn an assertion (that the number of handshakes received as a
6128 server is not < 1) into a warning. Fixes bug 4873; bugfix on
6130 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
6131 we had reversed them when the answer was cached.) Fixes bug
6132 5723; bugfix on 0.2.3.1-alpha.
6133 - Work correctly on Linux systems with accept4 support advertised in
6134 their headers, but without accept4 support in the kernel. Fix
6135 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
6136 - When told to add a bridge with the same addr:port as a preexisting
6137 bridge but a different transport, change the transport as
6138 requested. Previously we would not notice the change. Fixes half
6139 of bug 5603; fix on 0.2.3.2-alpha.
6140 - Avoid a "double-reply" warning when replying to a SOCKS request
6141 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
6142 bugfix on 0.2.3.4-alpha.
6143 - Fix a bug where a bridge authority crashes if it has seen no
6144 directory requests when it's time to write statistics to disk.
6145 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
6147 - Don't try to open non-control listeners when DisableNetwork is set.
6148 Previously, we'd open all listeners, then immediately close them.
6149 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
6150 - Don't abort the managed proxy protocol if the managed proxy
6151 sends us an unrecognized line; ignore it instead. Fixes bug
6152 5910; bugfix on 0.2.3.9-alpha.
6153 - Fix a compile warning in crypto.c when compiling with clang 3.1.
6154 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
6155 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
6156 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
6157 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
6158 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
6159 - Resolve numerous small warnings and build issues with MSVC. Resolves
6162 o Documentation fixes:
6163 - Improve the manual's documentation for the NT Service command-line
6164 options. Addresses ticket 3964.
6165 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
6166 - Document the changes to the ORPort and DirPort options, and the
6167 fact that {OR/Dir}ListenAddress is now unnecessary (and
6168 therefore deprecated). Resolves ticket 5597.
6171 - Remove the torrc.bridge file: we don't use it for anything, and
6172 it had become badly desynchronized from torrc.sample. Resolves
6176 Changes in version 0.2.2.36 - 2012-05-24
6177 Tor 0.2.2.36 updates the addresses for two of the eight directory
6178 authorities, fixes some potential anonymity and security issues,
6179 and fixes several crash bugs.
6181 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
6182 known flaws, and nobody should be using them. You should upgrade. If
6183 you're using a Linux or BSD and its packages are obsolete, stop using
6184 those packages and upgrade anyway.
6186 o Directory authority changes:
6187 - Change IP address for maatuska (v3 directory authority).
6188 - Change IP address for ides (v3 directory authority), and rename
6192 - When building or running with any version of OpenSSL earlier
6193 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6194 versions have a bug (CVE-2011-4576) in which their block cipher
6195 padding includes uninitialized data, potentially leaking sensitive
6196 information to any peer with whom they make a SSLv3 connection. Tor
6197 does not use SSL v3 by default, but a hostile client or server
6198 could force an SSLv3 connection in order to gain information that
6199 they shouldn't have been able to get. The best solution here is to
6200 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6201 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6202 to make sure that the bug can't happen.
6203 - Never use a bridge or a controller-supplied node as an exit, even
6204 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6205 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6206 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6207 - Only build circuits if we have a sufficient threshold of the total
6208 descriptors that are marked in the consensus with the "Exit"
6209 flag. This mitigates an attack proposed by wanoskarnet, in which
6210 all of a client's bridges collude to restrict the exit nodes that
6211 the client knows about. Fixes bug 5343.
6212 - Provide controllers with a safer way to implement the cookie
6213 authentication mechanism. With the old method, if another locally
6214 running program could convince a controller that it was the Tor
6215 process, then that program could trick the controller into telling
6216 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6217 authentication method uses a challenge-response approach to prevent
6218 this attack. Fixes bug 5185; implements proposal 193.
6221 - Avoid logging uninitialized data when unable to decode a hidden
6222 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6223 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6224 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6226 - Fix builds when the path to sed, openssl, or sha1sum contains
6227 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6229 - Correct our replacements for the timeradd() and timersub() functions
6230 on platforms that lack them (for example, Windows). The timersub()
6231 function is used when expiring circuits, while timeradd() is
6232 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6233 bugfix on 0.2.2.24-alpha.
6234 - Fix the SOCKET_OK test that we use to tell when socket
6235 creation fails so that it works on Win64. Fixes part of bug 4533;
6236 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6239 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6240 Fixes bug 5346; bugfix on 0.0.8pre3.
6241 - Make our number-parsing functions always treat too-large values
6242 as an error, even when those values exceed the width of the
6243 underlying type. Previously, if the caller provided these
6244 functions with minima or maxima set to the extreme values of the
6245 underlying integer type, these functions would return those
6246 values on overflow rather than treating overflow as an error.
6247 Fixes part of bug 5786; bugfix on 0.0.9.
6248 - Older Linux kernels erroneously respond to strange nmap behavior
6249 by having accept() return successfully with a zero-length
6250 socket. When this happens, just close the connection. Previously,
6251 we would try harder to learn the remote address: but there was
6252 no such remote address to learn, and our method for trying to
6253 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6254 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6255 - Correct parsing of certain date types in parse_http_time().
6256 Without this patch, If-Modified-Since would behave
6257 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6258 Esteban Manchado Velázques.
6259 - Change the BridgePassword feature (part of the "bridge community"
6260 design, which is not yet implemented) to use a time-independent
6261 comparison. The old behavior might have allowed an adversary
6262 to use timing to guess the BridgePassword value. Fixes bug 5543;
6263 bugfix on 0.2.0.14-alpha.
6264 - Detect and reject certain misformed escape sequences in
6265 configuration values. Previously, these values would cause us
6266 to crash if received in a torrc file or over an authenticated
6267 control port. Bug found by Esteban Manchado Velázquez, and
6268 independently by Robert Connolly from Matta Consulting who further
6269 noted that it allows a post-authentication heap overflow. Patch
6270 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6271 bugfix on 0.2.0.16-alpha.
6272 - Fix a compile warning when using the --enable-openbsd-malloc
6273 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6274 - During configure, detect when we're building with clang version
6275 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6276 CFLAGS. clang doesn't support them yet.
6277 - When sending an HTTP/1.1 proxy request, include a Host header.
6278 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6279 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
6280 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
6281 - If we hit the error case where routerlist_insert() replaces an
6282 existing (old) server descriptor, make sure to remove that
6283 server descriptor from the old_routers list. Fix related to bug
6284 1776. Bugfix on 0.2.2.18-alpha.
6286 o Minor bugfixes (documentation and log messages):
6287 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6288 Fixes bug 4856; bugfix on Tor 0.0.6.
6289 - Update "ClientOnly" man page entry to explain that there isn't
6290 really any point to messing with it. Resolves ticket 5005.
6291 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6292 directory authority option (introduced in Tor 0.2.2.34).
6293 - Downgrade the "We're missing a certificate" message from notice
6294 to info: people kept mistaking it for a real problem, whereas it
6295 is seldom the problem even when we are failing to bootstrap. Fixes
6296 bug 5067; bugfix on 0.2.0.10-alpha.
6297 - Correctly spell "connect" in a log message on failure to create a
6298 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
6299 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6300 circuits. Fixes issue 5259.
6303 - Directory authorities now reject versions of Tor older than
6304 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6305 inclusive. These versions accounted for only a small fraction of
6306 the Tor network, and have numerous known security issues. Resolves
6308 - Update to the May 1 2012 Maxmind GeoLite Country database.
6311 - When sending or relaying a RELAY_EARLY cell, we used to convert
6312 it to a RELAY cell if the connection was using the v1 link
6313 protocol. This was a workaround for older versions of Tor, which
6314 didn't handle RELAY_EARLY cells properly. Now that all supported
6315 versions can handle RELAY_EARLY cells, and now that we're enforcing
6316 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6317 remove this workaround. Addresses bug 4786.
6320 Changes in version 0.2.3.15-alpha - 2012-04-30
6321 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
6322 the development branch build on Windows again.
6324 o Minor bugfixes (on 0.2.2.x and earlier):
6325 - Make sure that there are no unhandled pending TLS errors before
6326 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
6327 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
6328 Bugfix on 0.1.0.5-rc; fixes bug 4528.
6329 - Fix an assert that directory authorities could trigger on sighup
6330 during some configuration state transitions. We now don't treat
6331 it as a fatal error when the new descriptor we just generated in
6332 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6333 - After we pick a directory mirror, we would refuse to use it if
6334 it's in our ExcludeExitNodes list, resulting in mysterious failures
6335 to bootstrap for people who just wanted to avoid exiting from
6336 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
6337 - When building with --enable-static-tor on OpenBSD, do not
6338 erroneously attempt to link -lrt. Fixes bug 5103.
6340 o Minor bugfixes (on 0.2.3.x):
6341 - When Tor is built with kernel headers from a recent (last few
6342 years) Linux kernel, do not fail to run on older (pre-2.6.28
6343 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
6344 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
6346 - Fix compilation with miniupnpc version 1.6; patch from
6347 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
6348 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
6349 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
6350 - Fix compilation on platforms without unistd.h, or where environ
6351 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
6354 - Directory authorities are now a little more lenient at accepting
6355 older router descriptors, or newer router descriptors that don't
6356 make big changes. This should help ameliorate past and future
6357 issues where routers think they have uploaded valid descriptors,
6358 but the authorities don't think so. Fix for ticket 2479.
6359 - Make the code that clients use to detect an address change be
6360 IPv6-aware, so that it won't fill clients' logs with error
6361 messages when trying to get the IPv4 address of an IPv6
6362 connection. Implements ticket 5537.
6365 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
6366 authorities needed to use it for a while to keep the network working
6367 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
6368 that was six months ago. As of now, it should no longer be needed
6372 Changes in version 0.2.3.14-alpha - 2012-04-23
6373 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
6374 candidate. It also dramatically speeds up AES: fast relays should
6375 consider switching to the newer OpenSSL library.
6377 o Directory authority changes:
6378 - Change IP address for ides (v3 directory authority), and rename
6382 - Avoid logging uninitialized data when unable to decode a hidden
6383 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6384 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6385 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6387 - If authorities are unable to get a v2 consensus document from other
6388 directory authorities, they no longer fall back to fetching
6389 them from regular directory caches. Fixes bug 5635; bugfix on
6390 0.2.2.26-beta, where routers stopped downloading v2 consensus
6392 - When we start a Tor client with a normal consensus already cached,
6393 be willing to download a microdescriptor consensus. Fixes bug 4011;
6394 fix on 0.2.3.1-alpha.
6396 o Major features (performance):
6397 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6398 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6399 vectorized AES implementations as appropriate. These can be much,
6400 much faster than other AES implementations.
6402 o Minor bugfixes (0.2.2.x and earlier):
6403 - Don't launch more than 10 service-side introduction-point circuits
6404 for a hidden service in five minutes. Previously, we would consider
6405 launching more introduction-point circuits if at least one second
6406 had passed without any introduction-point circuits failing. Fixes
6407 bug 4607; bugfix on 0.0.7pre1.
6408 - Change the BridgePassword feature (part of the "bridge community"
6409 design, which is not yet implemented) to use a time-independent
6410 comparison. The old behavior might have allowed an adversary
6411 to use timing to guess the BridgePassword value. Fixes bug 5543;
6412 bugfix on 0.2.0.14-alpha.
6413 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6414 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6415 - When sending an HTTP/1.1 proxy request, include a Host header.
6416 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6417 - Don't log that we have "decided to publish new relay descriptor"
6418 unless we are actually publishing a descriptor. Fixes bug 3942;
6419 bugfix on 0.2.2.28-beta.
6421 o Minor bugfixes (0.2.3.x):
6422 - Fix a bug where a bridge authority crashes (on a failed assert)
6423 if it has seen no directory requests when it's time to write
6424 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
6425 - Fix bug stomping on ORPort option NoListen and ignoring option
6426 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
6427 - In the testsuite, provide a large enough buffer in the tor_sscanf
6428 unit test. Otherwise we'd overrun that buffer and crash during
6429 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
6431 - Make sure we create the keys directory if it doesn't exist and we're
6432 about to store the dynamic Diffie-Hellman parameters. Fixes bug
6433 5572; bugfix on 0.2.3.13-alpha.
6434 - Fix a small memory leak when trying to decode incorrect base16
6435 authenticator during SAFECOOKIE authentication. Found by
6436 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
6439 - Add more information to a log statement that might help track down
6440 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6441 non-IP address" messages (or any Bug messages, for that matter!),
6442 please let us know about it.
6443 - Relays now understand an IPv6 address when they get one from a
6444 directory server. Resolves ticket 4875.
6445 - Resolve IPv6 addresses in bridge and entry statistics to country
6446 code "??" which means we at least count them. Resolves ticket 5053;
6447 improves on 0.2.3.9-alpha.
6448 - Update to the April 3 2012 Maxmind GeoLite Country database.
6449 - Begin a doc/state-contents.txt file to explain the contents of
6450 the Tor state file. Fixes bug 2987.
6452 o Default torrc changes:
6453 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6454 port on 9050 by default anyway, so this should not change anything
6456 - Stop mentioning the deprecated *ListenAddress options in
6457 torrc.sample. Fixes bug 5438.
6458 - Document unit of bandwidth related options in sample torrc.
6462 - The "torify" script no longer supports the "tsocks" socksifier
6463 tool, since tsocks doesn't support DNS and UDP right for Tor.
6464 Everyone should be using torsocks instead. Fixes bugs 3530 and
6465 5180. Based on a patch by "ugh".
6468 - Change the symmetric cipher interface so that creating and
6469 initializing a stream cipher are no longer separate functions.
6470 - Remove all internal support for unpadded RSA. We never used it, and
6471 it would be a bad idea to start.
6474 Changes in version 0.2.3.13-alpha - 2012-03-26
6475 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
6476 in managed pluggable transports, as well as providing other cleanups
6477 that get us closer to a release candidate.
6479 o Directory authority changes:
6480 - Change IP address for maatuska (v3 directory authority).
6483 - Provide controllers with a safer way to implement the cookie
6484 authentication mechanism. With the old method, if another locally
6485 running program could convince a controller that it was the Tor
6486 process, then that program could trick the controller into telling
6487 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6488 authentication method uses a challenge-response approach to prevent
6489 this attack. Fixes bug 5185, implements proposal 193.
6490 - Never use a bridge or a controller-supplied node as an exit, even
6491 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6492 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6493 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6494 - Only build circuits if we have a sufficient threshold of the total
6495 descriptors that are marked in the consensus with the "Exit"
6496 flag. This mitigates an attack proposed by wanoskarnet, in which
6497 all of a client's bridges collude to restrict the exit nodes that
6498 the client knows about. Fixes bug 5343.
6500 o Major bugfixes (on Tor 0.2.3.x):
6501 - Avoid an assert when managed proxies like obfsproxy are configured,
6502 and we receive HUP signals or setconf attempts too rapidly. This
6503 situation happens most commonly when Vidalia tries to attach to
6504 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
6505 bugfix on 0.2.3.6-alpha.
6506 - Fix a relay-side pluggable transports bug where managed proxies were
6507 unreachable from the Internet, because Tor asked them to bind on
6508 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
6509 - Stop discarding command-line arguments when TestingTorNetwork
6510 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
6511 0.2.3.9-alpha, where task 4552 added support for two layers of
6513 - Resume allowing the unit tests to run in gdb. This was accidentally
6514 made impossible when the DisableDebuggerAttachment option was
6515 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
6516 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
6517 0.2.3.11-alpha. Reported by Anthony G. Basile.
6519 o Minor bugfixes (on 0.2.2.x and earlier):
6520 - Ensure we don't cannibalize circuits that are longer than three hops
6521 already, so we don't end up making circuits with 5 or more
6522 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6523 0.1.0.1-rc which introduced cannibalization.
6524 - Detect and reject certain misformed escape sequences in
6525 configuration values. Previously, these values would cause us
6526 to crash if received in a torrc file or over an authenticated
6527 control port. Bug found by Esteban Manchado Velázquez, and
6528 independently by Robert Connolly from Matta Consulting who further
6529 noted that it allows a post-authentication heap overflow. Patch
6530 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6531 bugfix on 0.2.0.16-alpha.
6532 - Fix a compile warning when using the --enable-openbsd-malloc
6533 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6534 - Directory caches no longer refuse to clean out descriptors because
6535 of missing v2 networkstatus documents, unless they're configured
6536 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6537 0.2.2.26-beta. Patch by Daniel Bryg.
6538 - Update to the latest version of the tinytest unit testing framework.
6539 This includes a couple of bugfixes that can be relevant for
6540 running forked unit tests on Windows, and removes all reserved
6543 o Minor bugfixes (on 0.2.3.x):
6544 - On a failed pipe() call, don't leak file descriptors. Fixes bug
6545 4296; bugfix on 0.2.3.1-alpha.
6546 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
6547 until after we have received a CERTS cell. Fixes bug 4361; bugfix
6548 on 0.2.3.6-alpha. Patch by "frosty".
6549 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
6550 option, so that the IP stack doesn't decide to use it for IPv4
6551 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
6552 - Ensure that variables set in Tor's environment cannot override
6553 environment variables that Tor passes to a managed
6554 pluggable-transport proxy. Previously, Tor would pass every
6555 variable in its environment to managed proxies along with the new
6556 ones, in such a way that on many operating systems, the inherited
6557 environment variables would override those which Tor tried to
6558 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
6559 bugfix on 0.2.3.9-alpha for Windows.
6562 - A wide variety of new unit tests by Esteban Manchado Velázquez.
6563 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6564 - Update to the March 6 2012 Maxmind GeoLite Country database.
6567 Changes in version 0.2.3.12-alpha - 2012-02-13
6568 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
6569 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
6570 when Tor is configured to use a pluggable transport like obfsproxy.
6573 - Fix builds when the path to sed, openssl, or sha1sum contains
6574 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6576 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6577 connections. This change should allow busy exit relays to stop
6578 running out of available sockets as quickly. Fixes bug 4950;
6579 bugfix on 0.2.2.26-beta.
6580 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
6581 would ask the bridge for microdescriptors, which are only supported
6582 in 0.2.3.x, and then fail to bootstrap when it didn't get the
6583 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
6584 - Properly set up obfsproxy's environment when in managed mode. The
6585 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
6586 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
6587 5076 and 5082; bugfix on 0.2.3.6-alpha.
6590 - Use the dead_strip option when building Tor on OS X. This reduces
6591 binary size by almost 19% when linking openssl and libevent
6592 statically, which we do for Tor Browser Bundle.
6593 - Fix broken URLs in the sample torrc file, and tell readers about
6594 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6595 PublishServerDescriptor options. Addresses bug 4652.
6596 - Update to the February 7 2012 Maxmind GeoLite Country database.
6599 - Downgrade the "We're missing a certificate" message from notice
6600 to info: people kept mistaking it for a real problem, whereas it
6601 is seldom the problem even when we are failing to bootstrap. Fixes
6602 bug 5067; bugfix on 0.2.0.10-alpha.
6603 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
6604 managed pluggable transport server proxy's environment.
6605 Previously, we would put it there, even though Tor doesn't
6606 implement an 'extended server port' yet, and even though Tor
6607 almost certainly isn't listening at that address. For now, we set
6608 it to an empty string to avoid crashing older obfsproxies. Bugfix
6610 - Log the heartbeat message every HeartbeatPeriod seconds, not every
6611 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
6612 0.2.3.1-alpha. Bug reported by Scott Bennett.
6613 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
6614 bugfix on 0.2.3.11-alpha.
6615 - Update "ClientOnly" man page entry to explain that there isn't
6616 really any point to messing with it. Resolves ticket 5005.
6617 - Use the correct CVE number for CVE-2011-4576 in our comments and
6618 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
6621 o Code simplifications and refactoring:
6622 - Use the _WIN32 macro throughout our code to detect Windows.
6623 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
6627 Changes in version 0.2.3.11-alpha - 2012-01-22
6628 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
6629 the last step of the plan to limit maximum circuit length, includes
6630 a wide variety of hidden service performance and correctness fixes,
6631 works around an OpenSSL security flaw if your distro is too stubborn
6632 to upgrade, and fixes a bunch of smaller issues.
6635 - Now that Tor 0.2.0.x is completely deprecated, enable the final
6636 part of "Proposal 110: Avoiding infinite length circuits" by
6637 refusing all circuit-extend requests that do not use a relay_early
6638 cell. This change helps Tor resist a class of denial-of-service
6639 attacks by limiting the maximum circuit length.
6640 - Adjust the number of introduction points that a hidden service
6641 will try to maintain based on how long its introduction points
6642 remain in use and how many introductions they handle. Fixes
6644 - Try to use system facilities for enumerating local interface
6645 addresses, before falling back to our old approach (which was
6646 binding a UDP socket, and calling getsockname() on it). That
6647 approach was scaring OS X users whose draconian firewall
6648 software warned about binding to UDP sockets, regardless of
6649 whether packets were sent. Now we try to use getifaddrs(),
6650 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6651 system supports. Resolves ticket 1827.
6653 o Major security workaround:
6654 - When building or running with any version of OpenSSL earlier
6655 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6656 versions have a bug (CVE-2011-4576) in which their block cipher
6657 padding includes uninitialized data, potentially leaking sensitive
6658 information to any peer with whom they make a SSLv3 connection. Tor
6659 does not use SSL v3 by default, but a hostile client or server
6660 could force an SSLv3 connection in order to gain information that
6661 they shouldn't have been able to get. The best solution here is to
6662 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6663 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6664 to make sure that the bug can't happen.
6667 - Fix the SOCKET_OK test that we use to tell when socket
6668 creation fails so that it works on Win64. Fixes part of bug 4533;
6669 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6670 - Correct our replacements for the timeradd() and timersub() functions
6671 on platforms that lack them (for example, Windows). The timersub()
6672 function is used when expiring circuits, while timeradd() is
6673 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6674 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
6675 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
6676 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
6677 bug at runtime, not compile time, because some distributions hack
6678 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
6679 on 0.2.3.9-alpha. Found by Pascal.
6681 o Minor features (controller):
6682 - Use absolute path names when reporting the torrc filename in the
6683 control protocol, so a controller can more easily find the torrc
6684 file. Resolves bug 1101.
6685 - Extend the control protocol to report flags that control a circuit's
6686 path selection in CIRC events and in replies to 'GETINFO
6687 circuit-status'. Implements part of ticket 2411.
6688 - Extend the control protocol to report the hidden service address
6689 and current state of a hidden-service-related circuit in CIRC
6690 events and in replies to 'GETINFO circuit-status'. Implements part
6692 - When reporting the path to the cookie file to the controller,
6693 give an absolute path. Resolves ticket 4881.
6694 - Allow controllers to request an event notification whenever a
6695 circuit is cannibalized or its purpose is changed. Implements
6696 part of ticket 3457.
6697 - Include the creation time of a circuit in CIRC and CIRC2
6698 control-port events and the list produced by the 'GETINFO
6699 circuit-status' control-port command.
6701 o Minor features (directory authorities):
6702 - Directory authorities now reject versions of Tor older than
6703 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6704 inclusive. These versions accounted for only a small fraction of
6705 the Tor network, and have numerous known security issues. Resolves
6707 - Authority operators can now vote for all relays in a given
6708 set of countries to be BadDir/BadExit/Invalid/Rejected.
6709 - Provide two consensus parameters (FastFlagMinThreshold and
6710 FastFlagMaxThreshold) to control the range of allowable bandwidths
6711 for the Fast directory flag. These allow authorities to run
6712 experiments on appropriate requirements for being a "Fast" node.
6713 The AuthDirFastGuarantee config value still applies. Implements
6715 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6716 directory authority option (introduced in Tor 0.2.2.34).
6718 o Minor features (other):
6719 - Don't disable the DirPort when we cannot exceed our AccountingMax
6720 limit during this interval because the effective bandwidthrate is
6721 low enough. This is useful in a situation where AccountMax is only
6722 used as an additional safeguard or to provide statistics.
6723 - Prepend an informative header to generated dynamic_dh_params files.
6724 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6725 EntryNodes will have no effect. Resolves issue 2571.
6726 - Log more useful messages when we fail to disable debugger
6728 - Log which authority we're missing votes from when we go to fetch
6729 them from the other auths.
6730 - Log (at debug level) whenever a circuit's purpose is changed.
6731 - Add missing documentation for the MaxClientCircuitsPending,
6732 UseMicrodescriptors, UserspaceIOCPBuffers, and
6733 _UseFilteringSSLBufferevents options, all introduced during
6735 - Update to the January 3 2012 Maxmind GeoLite Country database.
6737 o Minor bugfixes (hidden services):
6738 - Don't close hidden service client circuits which have almost
6739 finished connecting to their destination when they reach
6740 the normal circuit-build timeout. Previously, we would close
6741 introduction circuits which are waiting for an acknowledgement
6742 from the introduction point, and rendezvous circuits which have
6743 been specified in an INTRODUCE1 cell sent to a hidden service,
6744 after the normal CBT. Now, we mark them as 'timed out', and launch
6745 another rendezvous attempt in parallel. This behavior change can
6746 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
6747 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
6748 - Don't close hidden-service-side rendezvous circuits when they
6749 reach the normal circuit-build timeout. This behavior change can
6750 be disabled using the new
6751 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
6752 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
6753 - Make sure we never mark the wrong rendezvous circuit as having
6754 had its introduction cell acknowleged by the introduction-point
6755 relay. Previously, when we received an INTRODUCE_ACK cell on a
6756 client-side hidden-service introduction circuit, we might have
6757 marked a rendezvous circuit other than the one we specified in
6758 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
6759 a warning message and interfered with the hidden service
6760 connection-establishment process. Fixes bug 4759; bugfix on
6761 0.2.3.3-alpha, when we added the stream-isolation feature which
6762 might cause Tor to open multiple rendezvous circuits for the same
6764 - Don't trigger an assertion failure when we mark a new client-side
6765 hidden-service introduction circuit for close during the process
6766 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
6769 o Minor bugfixes (log messages):
6770 - Correctly spell "connect" in a log message on failure to create a
6771 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
6773 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6774 Fixes bug 4856; bugfix on Tor 0.0.6.
6775 - Fix the log message describing how we work around discovering
6776 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
6777 4837; bugfix on 0.2.2.9-alpha.
6778 - When logging about a disallowed .exit name, do not also call it
6779 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
6781 o Minor bugfixes (build fixes):
6782 - During configure, detect when we're building with clang version
6783 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6784 CFLAGS. clang doesn't support them yet.
6785 - During configure, search for library containing cos function as
6786 libm lives in libcore on some platforms (BeOS/Haiku). Linking
6787 against libm was hard-coded before. Fixes the first part of bug
6788 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
6790 - Detect attempts to build Tor on (as yet hypothetical) versions
6791 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
6792 fix for bug 4533. Bugfix on 0.2.2.28-beta.
6793 - Preprocessor directives should not be put inside the arguments
6794 of a macro. This would break compilation with GCC releases prior
6795 to version 3.3. We would never recommend such an old GCC version,
6796 but it is apparently required for binary compatibility on some
6797 platforms (namely, certain builds of Haiku). Fixes the other part
6798 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
6801 o Minor bugfixes (other):
6802 - Older Linux kernels erroneously respond to strange nmap behavior
6803 by having accept() return successfully with a zero-length
6804 socket. When this happens, just close the connection. Previously,
6805 we would try harder to learn the remote address: but there was
6806 no such remote address to learn, and our method for trying to
6807 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6808 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6809 - Fix null-pointer access that could occur if TLS allocation failed.
6810 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
6811 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
6812 accidentally been reverted.
6813 - Fix our implementation of crypto_random_hostname() so it can't
6814 overflow on ridiculously large inputs. (No Tor version has ever
6815 provided this kind of bad inputs, but let's be correct in depth.)
6816 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
6817 - Find more places in the code that should have been testing for
6818 invalid sockets using the SOCKET_OK macro. Required for a fix
6819 for bug 4533. Bugfix on 0.2.2.28-beta.
6820 - Fix an assertion failure when, while running with bufferevents, a
6821 connection finishes connecting after it is marked for close, but
6822 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
6823 - test_util_spawn_background_ok() hardcoded the expected value
6824 for ENOENT to 2. This isn't portable as error numbers are
6825 platform specific, and particularly the hurd has ENOENT at
6826 0x40000002. Construct expected string at runtime, using the correct
6827 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
6828 - Reject attempts to disable DisableDebuggerAttachment while Tor is
6829 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
6830 - Use an appropriate-width type for sockets in tor-fw-helper on
6831 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
6834 - When sending or relaying a RELAY_EARLY cell, we used to convert
6835 it to a RELAY cell if the connection was using the v1 link
6836 protocol. This was a workaround for older versions of Tor, which
6837 didn't handle RELAY_EARLY cells properly. Now that all supported
6838 versions can handle RELAY_EARLY cells, and now that we're enforcing
6839 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6840 remove this workaround. Addresses bug 4786.
6842 o Code simplifications and refactoring:
6843 - Use OpenSSL's built-in SSL_state_string_long() instead of our
6844 own homebrewed ssl_state_to_string() replacement. Patch from
6845 Emile Snyder. Fixes bug 4653.
6846 - Use macros to indicate OpenSSL versions, so we don't need to worry
6847 about accidental hexadecimal bit shifts.
6848 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
6850 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
6851 - Use the smartlist_add_asprintf() alias more consistently.
6852 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
6853 invalid value, rather than just -1.
6854 - Rename a handful of old identifiers, mostly related to crypto
6855 structures and crypto functions. By convention, our "create an
6856 object" functions are called "type_new()", our "free an object"
6857 functions are called "type_free()", and our types indicate that
6858 they are types only with a final "_t". But a handful of older
6859 types and functions broke these rules, with function names like
6860 "type_create" or "subsystem_op_type", or with type names like
6864 Changes in version 0.2.3.10-alpha - 2011-12-16
6865 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
6866 Tor's buffers code. Absolutely everybody should upgrade.
6868 The bug relied on an incorrect calculation when making data continuous
6869 in one of our IO buffers, if the first chunk of the buffer was
6870 misaligned by just the wrong amount. The miscalculation would allow an
6871 attacker to overflow a piece of heap-allocated memory. To mount this
6872 attack, the attacker would need to either open a SOCKS connection to
6873 Tor's SocksPort (usually restricted to localhost), or target a Tor
6874 instance configured to make its connections through a SOCKS proxy
6875 (which Tor does not do by default).
6877 Good security practice requires that all heap-overflow bugs should be
6878 presumed to be exploitable until proven otherwise, so we are treating
6879 this as a potential code execution attack. Please upgrade immediately!
6880 This bug does not affect bufferevents-based builds of Tor. Special
6881 thanks to "Vektor" for reporting this issue to us!
6883 This release also contains a few minor bugfixes for issues discovered
6887 - Fix a heap overflow bug that could occur when trying to pull
6888 data into the first chunk of a buffer, when that chunk had
6889 already had some data drained from it. Fixes CVE-2011-2778;
6890 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6893 - If we can't attach streams to a rendezvous circuit when we
6894 finish connecting to a hidden service, clear the rendezvous
6895 circuit's stream-isolation state and try to attach streams
6896 again. Previously, we cleared rendezvous circuits' isolation
6897 state either too early (if they were freshly built) or not at all
6898 (if they had been built earlier and were cannibalized). Bugfix on
6899 0.2.3.3-alpha; fixes bug 4655.
6900 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
6901 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
6902 - Fix an assertion failure when a relay with accounting enabled
6903 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
6906 - Update to the December 6 2011 Maxmind GeoLite Country database.
6909 Changes in version 0.2.2.35 - 2011-12-16
6910 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
6911 buffers code. Absolutely everybody should upgrade.
6913 The bug relied on an incorrect calculation when making data continuous
6914 in one of our IO buffers, if the first chunk of the buffer was
6915 misaligned by just the wrong amount. The miscalculation would allow an
6916 attacker to overflow a piece of heap-allocated memory. To mount this
6917 attack, the attacker would need to either open a SOCKS connection to
6918 Tor's SocksPort (usually restricted to localhost), or target a Tor
6919 instance configured to make its connections through a SOCKS proxy
6920 (which Tor does not do by default).
6922 Good security practice requires that all heap-overflow bugs should be
6923 presumed to be exploitable until proven otherwise, so we are treating
6924 this as a potential code execution attack. Please upgrade immediately!
6925 This bug does not affect bufferevents-based builds of Tor. Special
6926 thanks to "Vektor" for reporting this issue to us!
6928 Tor 0.2.2.35 also fixes several bugs in previous versions, including
6929 crash bugs for unusual configurations, and a long-term bug that
6930 would prevent Tor from starting on Windows machines with draconian
6933 With this release, we remind everyone that 0.2.0.x has reached its
6934 formal end-of-life. Those Tor versions have many known flaws, and
6935 nobody should be using them. You should upgrade -- ideally to the
6936 0.2.2.x series. If you're using a Linux or BSD and its packages are
6937 obsolete, stop using those packages and upgrade anyway.
6939 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
6940 longer receive support after some time in early 2012.
6943 - Fix a heap overflow bug that could occur when trying to pull
6944 data into the first chunk of a buffer, when that chunk had
6945 already had some data drained from it. Fixes CVE-2011-2778;
6946 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6947 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6948 that it doesn't attempt to allocate a socketpair. This could cause
6949 some problems on Windows systems with overzealous firewalls. Fix for
6950 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6952 - If we mark an OR connection for close based on a cell we process,
6953 don't process any further cells on it. We already avoid further
6954 reads on marked-for-close connections, but now we also discard the
6955 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6956 which was the first version where we might mark a connection for
6957 close based on processing a cell on it.
6958 - Correctly sanity-check that we don't underflow on a memory
6959 allocation (and then assert) for hidden service introduction
6960 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6961 bugfix on 0.2.1.5-alpha.
6962 - Fix a memory leak when we check whether a hidden service
6963 descriptor has any usable introduction points left. Fixes bug
6964 4424. Bugfix on 0.2.2.25-alpha.
6965 - Don't crash when we're running as a relay and don't have a GeoIP
6966 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
6967 we've had in the 0.2.3.x branch already.
6968 - When running as a client, do not print a misleading (and plain
6969 wrong) log message that we're collecting "directory request"
6970 statistics: clients don't collect statistics. Also don't create a
6971 useless (because empty) stats file in the stats/ directory. Fixes
6972 bug 4353; bugfix on 0.2.2.34.
6975 - Detect failure to initialize Libevent. This fix provides better
6976 detection for future instances of bug 4457.
6977 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6978 function. This was eating up hideously large amounts of time on some
6979 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6980 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6981 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6983 - Don't warn about unused log_mutex in log.c when building with
6984 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6985 0.1.0.6-rc which introduced --disable-threads.
6986 - When configuring, starting, or stopping an NT service, stop
6987 immediately after the service configuration attempt has succeeded
6988 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6989 - When sending a NETINFO cell, include the original address
6990 received for the other side, not its canonical address. Found
6991 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6992 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
6993 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6994 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6995 occurred when a client tried to fetch a descriptor for a bridge
6996 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6997 - Backport fixes for a pair of compilation warnings on Windows.
6998 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
6999 - If we had ever tried to call tor_addr_to_str on an address of
7000 unknown type, we would have done a strdup on an uninitialized
7001 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7002 Reported by "troll_un".
7003 - Correctly detect and handle transient lookup failures from
7004 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7005 Reported by "troll_un".
7006 - Fix null-pointer access that could occur if TLS allocation failed.
7007 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7008 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7009 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7012 - Add two new config options for directory authorities:
7013 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7014 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7015 that is always sufficient to satisfy the bandwidth requirement for
7016 the Guard flag. Now it will be easier for researchers to simulate
7017 Tor networks with different values. Resolves ticket 4484.
7018 - When Tor ignores a hidden service specified in its configuration,
7019 include the hidden service's directory in the warning message.
7020 Previously, we would only tell the user that some hidden service
7021 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7022 - Update to the December 6 2011 Maxmind GeoLite Country database.
7024 o Packaging changes:
7025 - Make it easier to automate expert package builds on Windows,
7026 by removing an absolute path from makensis.exe command.
7029 Changes in version 0.2.1.32 - 2011-12-16
7030 Tor 0.2.1.32 backports important security and privacy fixes for
7031 oldstable. This release is intended only for package maintainers and
7032 others who cannot use the 0.2.2 stable series. All others should be
7033 using Tor 0.2.2.x or newer.
7035 The Tor 0.2.1.x series will reach formal end-of-life some time in
7036 early 2012; we will stop releasing patches for it then.
7038 o Major bugfixes (also included in 0.2.2.x):
7039 - Correctly sanity-check that we don't underflow on a memory
7040 allocation (and then assert) for hidden service introduction
7041 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7042 bugfix on 0.2.1.5-alpha.
7043 - Fix a heap overflow bug that could occur when trying to pull
7044 data into the first chunk of a buffer, when that chunk had
7045 already had some data drained from it. Fixes CVE-2011-2778;
7046 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7049 - Update to the December 6 2011 Maxmind GeoLite Country database.
7052 Changes in version 0.2.3.9-alpha - 2011-12-08
7053 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
7054 a "DisableNetwork" security feature that bundles can use to avoid
7055 touching the network until bridges are configured, moves forward on
7056 the pluggable transport design, fixes a flaw in the hidden service
7057 design that unnecessarily prevented clients with wrong clocks from
7058 reaching hidden services, and fixes a wide variety of other issues.
7061 - Clients can now connect to private bridges over IPv6. Bridges
7062 still need at least one IPv4 address in order to connect to
7063 other relays. Note that we don't yet handle the case where the
7064 user has two bridge lines for the same bridge (one IPv4, one
7065 IPv6). Implements parts of proposal 186.
7066 - New "DisableNetwork" config option to prevent Tor from launching any
7067 connections or accepting any connections except on a control port.
7068 Bundles and controllers can set this option before letting Tor talk
7069 to the rest of the network, for example to prevent any connections
7070 to a non-bridge address. Packages like Orbot can also use this
7071 option to instruct Tor to save power when the network is off.
7072 - Clients and bridges can now be configured to use a separate
7073 "transport" proxy. This approach makes the censorship arms race
7074 easier by allowing bridges to use protocol obfuscation plugins. It
7075 implements the "managed proxy" part of proposal 180 (ticket 3472).
7076 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
7077 implementation. It makes AES_CTR about 7% faster than our old one
7078 (which was about 10% faster than the one OpenSSL used to provide).
7079 Resolves ticket 4526.
7080 - Add a "tor2web mode" for clients that want to connect to hidden
7081 services non-anonymously (and possibly more quickly). As a safety
7082 measure to try to keep users from turning this on without knowing
7083 what they are doing, tor2web mode must be explicitly enabled at
7084 compile time, and a copy of Tor compiled to run in tor2web mode
7085 cannot be used as a normal Tor client. Implements feature 2553.
7086 - Add experimental support for running on Windows with IOCP and no
7087 kernel-space socket buffers. This feature is controlled by a new
7088 "UserspaceIOCPBuffers" config option (off by default), which has
7089 no effect unless Tor has been built with support for bufferevents,
7090 is running on Windows, and has enabled IOCP. This may, in the long
7091 run, help solve or mitigate bug 98.
7092 - Use a more secure consensus parameter voting algorithm. Now at
7093 least three directory authorities or a majority of them must
7094 vote on a given parameter before it will be included in the
7095 consensus. Implements proposal 178.
7098 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
7099 They used to check that the timestamp was within 30 minutes
7100 of their system clock, so they could cap the size of their
7101 replay-detection cache, but that approach unnecessarily refused
7102 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
7103 the v3 intro-point protocol (the first one which sent a timestamp
7104 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
7105 - Only use the EVP interface when AES acceleration is enabled,
7106 to avoid a 5-7% performance regression. Resolves issue 4525;
7107 bugfix on 0.2.3.8-alpha.
7109 o Privacy/anonymity features (bridge detection):
7110 - Make bridge SSL certificates a bit more stealthy by using random
7111 serial numbers, in the same fashion as OpenSSL when generating
7112 self-signed certificates. Implements ticket 4584.
7113 - Introduce a new config option "DynamicDHGroups", enabled by
7114 default, which provides each bridge with a unique prime DH modulus
7115 to be used during SSL handshakes. This option attempts to help
7116 against censors who might use the Apache DH modulus as a static
7117 identifier for bridges. Addresses ticket 4548.
7119 o Minor features (new/different config options):
7120 - New configuration option "DisableDebuggerAttachment" (on by default)
7121 to prevent basic debugging attachment attempts by other processes.
7122 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
7123 - Allow MapAddress directives to specify matches against super-domains,
7124 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
7125 Implements issue 933.
7126 - Slightly change behavior of "list" options (that is, config
7127 options that can appear more than once) when they appear both in
7128 torrc and on the command line. Previously, the command-line options
7129 would be appended to the ones from torrc. Now, the command-line
7130 options override the torrc options entirely. This new behavior
7131 allows the user to override list options (like exit policies and
7132 ports to listen on) from the command line, rather than simply
7133 appending to the list.
7134 - You can get the old (appending) command-line behavior for "list"
7135 options by prefixing the option name with a "+".
7136 - You can remove all the values for a "list" option from the command
7137 line without adding any new ones by prefixing the option name
7139 - Add experimental support for a "defaults" torrc file to be parsed
7140 before the regular torrc. Torrc options override the defaults file's
7141 options in the same way that the command line overrides the torrc.
7142 The SAVECONF controller command saves only those options which
7143 differ between the current configuration and the defaults file. HUP
7144 reloads both files. (Note: This is an experimental feature; its
7145 behavior will probably be refined in future 0.2.3.x-alpha versions
7146 to better meet packagers' needs.) Implements task 4552.
7149 - Try to make the introductory warning message that Tor prints on
7150 startup more useful for actually finding help and information.
7151 Resolves ticket 2474.
7152 - Running "make version" now displays the version of Tor that
7153 we're about to build. Idea from katmagic; resolves issue 4400.
7154 - Expire old or over-used hidden service introduction points.
7155 Required by fix for bug 3460.
7156 - Move the replay-detection cache for the RSA-encrypted parts of
7157 INTRODUCE2 cells to the introduction point data structures.
7158 Previously, we would use one replay-detection cache per hidden
7159 service. Required by fix for bug 3460.
7160 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
7161 public key replay-detection cache from 60 minutes to 5 minutes. This
7162 replay-detection cache is now used only to detect multiple
7163 INTRODUCE2 cells specifying the same rendezvous point, so we can
7164 avoid launching multiple simultaneous attempts to connect to it.
7166 o Minor bugfixes (on Tor 0.2.2.x and earlier):
7167 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7168 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7170 - Fix a minor formatting issue in one of tor-gencert's error messages.
7172 - Prevent a false positive from the check-spaces script, by disabling
7173 the "whitespace between function name and (" check for functions
7175 - Fix a log message suggesting that people contact a non-existent
7176 email address. Fixes bug 3448.
7177 - Fix null-pointer access that could occur if TLS allocation failed.
7178 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7179 - Report a real bootstrap problem to the controller on router
7180 identity mismatch. Previously we just said "foo", which probably
7181 made a lot of sense at the time. Fixes bug 4169; bugfix on
7183 - If we had ever tried to call tor_addr_to_str() on an address of
7184 unknown type, we would have done a strdup() on an uninitialized
7185 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7186 Reported by "troll_un".
7187 - Correctly detect and handle transient lookup failures from
7188 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7189 Reported by "troll_un".
7190 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7191 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7192 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
7193 bug 4532; found by "troll_un".
7195 o Minor bugfixes (on Tor 0.2.3.x):
7196 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
7198 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
7199 circuit for use as a hidden service client's rendezvous point.
7200 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
7201 with help from wanoskarnet.
7202 - Restore behavior of overriding SocksPort, ORPort, and similar
7203 options from the command line. Bugfix on 0.2.3.3-alpha.
7206 - Properly handle the case where the build-tree is not the same
7207 as the source tree when generating src/common/common_sha1.i,
7208 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7209 bugfix on 0.2.0.1-alpha.
7211 o Code simplifications, cleanups, and refactorings:
7212 - Remove the pure attribute from all functions that used it
7213 previously. In many cases we assigned it incorrectly, because the
7214 functions might assert or call impure functions, and we don't have
7215 evidence that keeping the pure attribute is worthwhile. Implements
7216 changes suggested in ticket 4421.
7217 - Remove some dead code spotted by coverity. Fixes cid 432.
7218 Bugfix on 0.2.3.1-alpha, closes bug 4637.
7221 Changes in version 0.2.3.8-alpha - 2011-11-22
7222 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
7223 socketpair-related bug that has been bothering Windows users. It adds
7224 support to serve microdescriptors to controllers, so Vidalia's network
7225 map can resume listing relays (once Vidalia implements its side),
7226 and adds better support for hardware AES acceleration. Finally, it
7227 starts the process of adjusting the bandwidth cutoff for getting the
7228 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
7229 that tiny relays harm performance more than they help network capacity.
7232 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7233 that it doesn't attempt to allocate a socketpair. This could cause
7234 some problems on Windows systems with overzealous firewalls. Fix for
7235 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7237 - Correctly sanity-check that we don't underflow on a memory
7238 allocation (and then assert) for hidden service introduction
7239 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7240 bugfix on 0.2.1.5-alpha.
7241 - Remove the artificially low cutoff of 20KB to guarantee the Fast
7242 flag. In the past few years the average relay speed has picked
7243 up, and while the "top 7/8 of the network get the Fast flag" and
7244 "all relays with 20KB or more of capacity get the Fast flag" rules
7245 used to have the same result, now the top 7/8 of the network has
7246 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
7247 - Fix a rare assertion failure when checking whether a v0 hidden
7248 service descriptor has any usable introduction points left, and
7249 we don't have enough information to build a circuit to the first
7250 intro point named in the descriptor. The HS client code in
7251 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
7252 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
7253 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
7254 - Make bridge authorities not crash when they are asked for their own
7255 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
7256 - When running as a client, do not print a misleading (and plain
7257 wrong) log message that we're collecting "directory request"
7258 statistics: clients don't collect statistics. Also don't create a
7259 useless (because empty) stats file in the stats/ directory. Fixes
7260 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
7263 - Allow Tor controllers like Vidalia to obtain the microdescriptor
7264 for a relay by identity digest or nickname. Previously,
7265 microdescriptors were only available by their own digests, so a
7266 controller would have to ask for and parse the whole microdescriptor
7267 consensus in order to look up a single relay's microdesc. Fixes
7268 bug 3832; bugfix on 0.2.3.1-alpha.
7269 - Use OpenSSL's EVP interface for AES encryption, so that all AES
7270 operations can use hardware acceleration (if present). Resolves
7273 o Minor bugfixes (on 0.2.2.x and earlier):
7274 - Detect failure to initialize Libevent. This fix provides better
7275 detection for future instances of bug 4457.
7276 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7277 function. This was eating up hideously large amounts of time on some
7278 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7279 - Don't warn about unused log_mutex in log.c when building with
7280 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7281 0.1.0.6-rc which introduced --disable-threads.
7282 - Allow manual 'authenticate' commands to the controller interface
7283 from netcat (nc) as well as telnet. We were rejecting them because
7284 they didn't come with the expected whitespace at the end of the
7285 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
7286 - Fix some (not actually triggerable) buffer size checks in usage of
7287 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
7289 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
7290 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
7291 - When configuring, starting, or stopping an NT service, stop
7292 immediately after the service configuration attempt has succeeded
7293 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7294 - When sending a NETINFO cell, include the original address
7295 received for the other side, not its canonical address. Found
7296 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7297 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
7298 can pick them up when the tests aren't disabled. Bugfix on
7299 0.2.2.4-alpha which introduced tinytest.
7300 - Fix a memory leak when we check whether a hidden service
7301 descriptor has any usable introduction points left. Fixes bug
7302 4424. Bugfix on 0.2.2.25-alpha.
7303 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7304 occurred when a client tried to fetch a descriptor for a bridge
7305 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7307 o Minor bugfixes (on 0.2.3.x):
7308 - Make util unit tests build correctly with MSVC. Bugfix on
7309 0.2.3.3-alpha. Patch by Gisle Vanem.
7310 - Successfully detect AUTH_CHALLENGE cells with no recognized
7311 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
7313 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
7314 it should still send a NETINFO cell to allow the connection to
7315 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
7317 - Log less loudly when we get an invalid authentication certificate
7318 from a source other than a directory authority: it's not unusual
7319 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
7321 - Tolerate servers with more clock skew in their authentication
7322 certificates than previously. Fixes bug 4371; bugfix on
7324 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
7325 on 0.2.3.4-alpha and 0.2.3.6-alpha.
7328 - Add two new config options for directory authorities:
7329 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7330 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7331 that is always sufficient to satisfy the bandwidth requirement for
7332 the Guard flag. Now it will be easier for researchers to simulate
7333 Tor networks with different values. Resolves ticket 4484.
7334 - When Tor ignores a hidden service specified in its configuration,
7335 include the hidden service's directory in the warning message.
7336 Previously, we would only tell the user that some hidden service
7337 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7338 - When we fail to initialize Libevent, retry with IOCP disabled so we
7339 don't need to turn on multi-threading support in Libevent, which in
7340 turn requires a working socketpair(). This is a workaround for bug
7341 4457, which affects Libevent versions from 2.0.1-alpha through
7343 - Detect when we try to build on a platform that doesn't define
7344 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7345 - Update to the November 1 2011 Maxmind GeoLite Country database.
7347 o Packaging changes:
7348 - Make it easier to automate expert package builds on Windows,
7349 by removing an absolute path from makensis.exe command.
7351 o Code simplifications and refactoring:
7352 - Remove some redundant #include directives throughout the code.
7353 Patch from Andrea Gelmini.
7354 - Unconditionally use OpenSSL's AES implementation instead of our
7355 old built-in one. OpenSSL's AES has been better for a while, and
7356 relatively few servers should still be on any version of OpenSSL
7357 that doesn't have good optimized assembly AES.
7358 - Use the name "CERTS" consistently to refer to the new cell type;
7359 we were calling it CERT in some places and CERTS in others.
7362 - Numerous new unit tests for functions in util.c and address.c by
7364 - The long-disabled benchmark tests are now split into their own
7365 ./src/test/bench binary.
7366 - The benchmark tests can now use more accurate timers than
7367 gettimeofday() when such timers are available.
7370 Changes in version 0.2.3.7-alpha - 2011-10-30
7371 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
7372 the new v3 handshake. It also resolves yet another bridge address
7376 - If we mark an OR connection for close based on a cell we process,
7377 don't process any further cells on it. We already avoid further
7378 reads on marked-for-close connections, but now we also discard the
7379 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7380 which was the first version where we might mark a connection for
7381 close based on processing a cell on it.
7382 - Fix a double-free bug that would occur when we received an invalid
7383 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
7384 bugfix on 0.2.3.6-alpha.
7385 - Bridges no longer include their address in NETINFO cells on outgoing
7386 OR connections, to allow them to blend in better with clients.
7387 Removes another avenue for enumerating bridges. Reported by
7388 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
7389 cells were introduced.
7392 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
7393 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7396 Changes in version 0.2.3.6-alpha - 2011-10-26
7397 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
7398 anonymity vulnerability where an attacker can deanonymize Tor
7399 users. Everybody should upgrade.
7401 This release also features support for a new v3 connection handshake
7402 protocol, and fixes to make hidden service connections more robust.
7405 - Implement a new handshake protocol (v3) for authenticating Tors to
7406 each other over TLS. It should be more resistant to fingerprinting
7407 than previous protocols, and should require less TLS hacking for
7408 future Tor implementations. Implements proposal 176.
7409 - Allow variable-length padding cells to disguise the length of
7410 Tor's TLS records. Implements part of proposal 184.
7412 o Privacy/anonymity fixes (clients):
7413 - Clients and bridges no longer send TLS certificate chains on
7414 outgoing OR connections. Previously, each client or bridge would
7415 use the same cert chain for all outgoing OR connections until
7416 its IP address changes, which allowed any relay that the client
7417 or bridge contacted to determine which entry guards it is using.
7418 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7419 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7420 no longer considers that connection as suitable for satisfying a
7421 circuit EXTEND request. Now relays can protect clients from the
7422 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7423 - Directory authorities no longer assign the Guard flag to relays
7424 that haven't upgraded to the above "refuse EXTEND requests
7425 to client connections" fix. Now directory authorities can
7426 protect clients from the CVE-2011-2768 issue even if neither
7427 the clients nor the relays have upgraded yet. There's a new
7428 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7429 to let us transition smoothly, else tomorrow there would be no
7432 o Major bugfixes (hidden services):
7433 - Improve hidden service robustness: when an attempt to connect to
7434 a hidden service ends, be willing to refetch its hidden service
7435 descriptors from each of the HSDir relays responsible for them
7436 immediately. Previously, we would not consider refetching the
7437 service's descriptors from each HSDir for 15 minutes after the last
7438 fetch, which was inconvenient if the hidden service was not running
7439 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
7440 - When one of a hidden service's introduction points appears to be
7441 unreachable, stop trying it. Previously, we would keep trying
7442 to build circuits to the introduction point until we lost the
7443 descriptor, usually because the user gave up and restarted Tor.
7444 Partly fixes bug 3825.
7445 - Don't launch a useless circuit after failing to use one of a
7446 hidden service's introduction points. Previously, we would
7447 launch a new introduction circuit, but not set the hidden service
7448 which that circuit was intended to connect to, so it would never
7449 actually be used. A different piece of code would then create a
7450 new introduction circuit correctly. Bug reported by katmagic and
7451 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7453 o Major bugfixes (other):
7454 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7455 that they initiated. Relays could distinguish incoming bridge
7456 connections from client connections, creating another avenue for
7457 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7458 Found by "frosty_un".
7459 - Don't update the AccountingSoftLimitHitAt state file entry whenever
7460 tor gets started. This prevents a wrong average bandwidth
7461 estimate, which would cause relays to always start a new accounting
7462 interval at the earliest possible moment. Fixes bug 2003; bugfix
7463 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
7464 immensely in tracking this bug down.
7465 - Fix a crash bug when changing node restrictions while a DNS lookup
7466 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7469 o Minor bugfixes (on 0.2.2.x and earlier):
7470 - When a hidden service turns an extra service-side introduction
7471 circuit into a general-purpose circuit, free the rend_data and
7472 intro_key fields first, so we won't leak memory if the circuit
7473 is cannibalized for use as another service-side introduction
7474 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7475 - Rephrase the log message emitted if the TestSocks check is
7476 successful. Patch from Fabian Keil; fixes bug 4094.
7477 - Bridges now skip DNS self-tests, to act a little more stealthily.
7478 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7479 bridges. Patch by "warms0x".
7480 - Remove a confusing dollar sign from the example fingerprint in the
7481 man page, and also make the example fingerprint a valid one. Fixes
7482 bug 4309; bugfix on 0.2.1.3-alpha.
7483 - Fix internal bug-checking logic that was supposed to catch
7484 failures in digest generation so that it will fail more robustly
7485 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7486 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7487 - Report any failure in init_keys() calls launched because our
7488 IP address has changed. Spotted by Coverity Scan. Bugfix on
7489 0.1.1.4-alpha; fixes CID 484.
7491 o Minor bugfixes (on 0.2.3.x):
7492 - Fix a bug in configure.in that kept it from building a configure
7493 script with autoconf versions earlier than 2.61. Fixes bug 2430;
7494 bugfix on 0.2.3.1-alpha.
7495 - Don't warn users that they are exposing a client port to the
7496 Internet if they have specified an RFC1918 address. Previously,
7497 we would warn if the user had specified any non-loopback
7498 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
7499 - Fix memory leaks in the failing cases of the new SocksPort and
7500 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
7501 fixes coverity CIDs 485, 486, and 487.
7504 - When a hidden service's introduction point times out, consider
7505 trying it again during the next attempt to connect to the
7506 HS. Previously, we would not try it again unless a newly fetched
7507 descriptor contained it. Required by fixes for bugs 1297 and 3825.
7508 - The next version of Windows will be called Windows 8, and it has
7509 a major version of 6, minor version of 2. Correctly identify that
7510 version instead of calling it "Very recent version". Resolves
7511 ticket 4153; reported by funkstar.
7512 - The Bridge Authority now writes statistics on how many bridge
7513 descriptors it gave out in total, and how many unique descriptors
7514 it gave out. It also lists how often the most and least commonly
7515 fetched descriptors were given out, as well as the median and
7516 25th/75th percentile. Implements tickets 4200 and 4294.
7517 - Update to the October 4 2011 Maxmind GeoLite Country database.
7519 o Code simplifications and refactoring:
7520 - Remove some old code to remember statistics about which descriptors
7521 we've served as a directory mirror. The feature wasn't used and
7522 is outdated now that microdescriptors are around.
7523 - Rename Tor functions that turn strings into addresses, so that
7524 "parse" indicates that no hostname resolution occurs, and
7525 "lookup" indicates that hostname resolution may occur. This
7526 should help prevent mistakes in the future. Fixes bug 3512.
7529 Changes in version 0.2.2.34 - 2011-10-26
7530 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7531 can deanonymize Tor users. Everybody should upgrade.
7533 The attack relies on four components: 1) Clients reuse their TLS cert
7534 when talking to different relays, so relays can recognize a user by
7535 the identity key in her cert. 2) An attacker who knows the client's
7536 identity key can probe each guard relay to see if that identity key
7537 is connected to that guard relay right now. 3) A variety of active
7538 attacks in the literature (starting from "Low-Cost Traffic Analysis
7539 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7540 discover the guard relays that a Tor user visiting the website is using.
7541 4) Clients typically pick three guards at random, so the set of guards
7542 for a given user could well be a unique fingerprint for her. This
7543 release fixes components #1 and #2, which is enough to block the attack;
7544 the other two remain as open research problems. Special thanks to
7545 "frosty_un" for reporting the issue to us!
7547 Clients should upgrade so they are no longer recognizable by the TLS
7548 certs they present. Relays should upgrade so they no longer allow a
7549 remote attacker to probe them to test whether unpatched clients are
7550 currently connected to them.
7552 This release also fixes several vulnerabilities that allow an attacker
7553 to enumerate bridge relays. Some bridge enumeration attacks still
7554 remain; see for example proposal 188.
7556 o Privacy/anonymity fixes (clients):
7557 - Clients and bridges no longer send TLS certificate chains on
7558 outgoing OR connections. Previously, each client or bridge would
7559 use the same cert chain for all outgoing OR connections until
7560 its IP address changes, which allowed any relay that the client
7561 or bridge contacted to determine which entry guards it is using.
7562 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7563 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7564 no longer considers that connection as suitable for satisfying a
7565 circuit EXTEND request. Now relays can protect clients from the
7566 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7567 - Directory authorities no longer assign the Guard flag to relays
7568 that haven't upgraded to the above "refuse EXTEND requests
7569 to client connections" fix. Now directory authorities can
7570 protect clients from the CVE-2011-2768 issue even if neither
7571 the clients nor the relays have upgraded yet. There's a new
7572 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7573 to let us transition smoothly, else tomorrow there would be no
7576 o Privacy/anonymity fixes (bridge enumeration):
7577 - Bridge relays now do their directory fetches inside Tor TLS
7578 connections, like all the other clients do, rather than connecting
7579 directly to the DirPort like public relays do. Removes another
7580 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7581 - Bridges relays now build circuits for themselves in a more similar
7582 way to how clients build them. Removes another avenue for
7583 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7584 when bridges were introduced.
7585 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7586 that they initiated. Relays could distinguish incoming bridge
7587 connections from client connections, creating another avenue for
7588 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7589 Found by "frosty_un".
7592 - Fix a crash bug when changing node restrictions while a DNS lookup
7593 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7595 - Don't launch a useless circuit after failing to use one of a
7596 hidden service's introduction points. Previously, we would
7597 launch a new introduction circuit, but not set the hidden service
7598 which that circuit was intended to connect to, so it would never
7599 actually be used. A different piece of code would then create a
7600 new introduction circuit correctly. Bug reported by katmagic and
7601 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7604 - Change an integer overflow check in the OpenBSD_Malloc code so
7605 that GCC is less likely to eliminate it as impossible. Patch
7606 from Mansour Moufid. Fixes bug 4059.
7607 - When a hidden service turns an extra service-side introduction
7608 circuit into a general-purpose circuit, free the rend_data and
7609 intro_key fields first, so we won't leak memory if the circuit
7610 is cannibalized for use as another service-side introduction
7611 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7612 - Bridges now skip DNS self-tests, to act a little more stealthily.
7613 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7614 bridges. Patch by "warms0x".
7615 - Fix internal bug-checking logic that was supposed to catch
7616 failures in digest generation so that it will fail more robustly
7617 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7618 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7619 - Report any failure in init_keys() calls launched because our
7620 IP address has changed. Spotted by Coverity Scan. Bugfix on
7621 0.1.1.4-alpha; fixes CID 484.
7623 o Minor bugfixes (log messages and documentation):
7624 - Remove a confusing dollar sign from the example fingerprint in the
7625 man page, and also make the example fingerprint a valid one. Fixes
7626 bug 4309; bugfix on 0.2.1.3-alpha.
7627 - The next version of Windows will be called Windows 8, and it has
7628 a major version of 6, minor version of 2. Correctly identify that
7629 version instead of calling it "Very recent version". Resolves
7630 ticket 4153; reported by funkstar.
7631 - Downgrade log messages about circuit timeout calibration from
7632 "notice" to "info": they don't require or suggest any human
7633 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7634 bugfix on 0.2.2.14-alpha.
7637 - Turn on directory request statistics by default and include them in
7638 extra-info descriptors. Don't break if we have no GeoIP database.
7639 Backported from 0.2.3.1-alpha; implements ticket 3951.
7640 - Update to the October 4 2011 Maxmind GeoLite Country database.
7643 Changes in version 0.2.1.31 - 2011-10-26
7644 Tor 0.2.1.31 backports important security and privacy fixes for
7645 oldstable. This release is intended only for package maintainers and
7646 others who cannot use the 0.2.2 stable series. All others should be
7647 using Tor 0.2.2.x or newer.
7649 o Security fixes (also included in 0.2.2.x):
7650 - Replace all potentially sensitive memory comparison operations
7651 with versions whose runtime does not depend on the data being
7652 compared. This will help resist a class of attacks where an
7653 adversary can use variations in timing information to learn
7654 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7655 implementation by Robert Ransom based partially on code by DJB.)
7656 - Fix an assert in parsing router descriptors containing IPv6
7657 addresses. This one took down the directory authorities when
7658 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7660 o Privacy/anonymity fixes (also included in 0.2.2.x):
7661 - Clients and bridges no longer send TLS certificate chains on
7662 outgoing OR connections. Previously, each client or bridge would
7663 use the same cert chain for all outgoing OR connections until
7664 its IP address changes, which allowed any relay that the client
7665 or bridge contacted to determine which entry guards it is using.
7666 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7667 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7668 no longer considers that connection as suitable for satisfying a
7669 circuit EXTEND request. Now relays can protect clients from the
7670 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7671 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7672 that they initiated. Relays could distinguish incoming bridge
7673 connections from client connections, creating another avenue for
7674 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7675 Found by "frosty_un".
7676 - When receiving a hidden service descriptor, check that it is for
7677 the hidden service we wanted. Previously, Tor would store any
7678 hidden service descriptors that a directory gave it, whether it
7679 wanted them or not. This wouldn't have let an attacker impersonate
7680 a hidden service, but it did let directories pre-seed a client
7681 with descriptors that it didn't want. Bugfix on 0.0.6.
7682 - Avoid linkability based on cached hidden service descriptors: forget
7683 all hidden service descriptors cached as a client when processing a
7684 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7685 - Make the bridge directory authority refuse to answer directory
7686 requests for "all" descriptors. It used to include bridge
7687 descriptors in its answer, which was a major information leak.
7688 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7689 - Don't attach new streams to old rendezvous circuits after SIGNAL
7690 NEWNYM. Previously, we would keep using an existing rendezvous
7691 circuit if it remained open (i.e. if it were kept open by a
7692 long-lived stream, or if a new stream were attached to it before
7693 Tor could notice that it was old and no longer in use). Bugfix on
7694 0.1.1.15-rc; fixes bug 3375.
7696 o Minor bugfixes (also included in 0.2.2.x):
7697 - When we restart our relay, we might get a successful connection
7698 from the outside before we've started our reachability tests,
7699 triggering a warning: "ORPort found reachable, but I have no
7700 routerinfo yet. Failing to inform controller of success." This
7701 bug was harmless unless Tor is running under a controller
7702 like Vidalia, in which case the controller would never get a
7703 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7705 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7706 enabled. Fixes bug 1526.
7707 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7708 anything since 0.2.1.16-rc.
7709 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7710 None of the cases where we did this before were wrong, but by making
7711 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7712 - Fix a rare crash bug that could occur when a client was configured
7713 with a large number of bridges. Fixes bug 2629; bugfix on
7714 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7715 - Correct the warning displayed when a rendezvous descriptor exceeds
7716 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7718 - Fix an uncommon assertion failure when running with DNSPort under
7719 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7720 - When warning about missing zlib development packages during compile,
7721 give the correct package names. Bugfix on 0.2.0.1-alpha.
7722 - Require that introduction point keys and onion keys have public
7723 exponent 65537. Bugfix on 0.2.0.10-alpha.
7724 - Do not crash when our configuration file becomes unreadable, for
7725 example due to a permissions change, between when we start up
7726 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7728 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7730 - Always NUL-terminate the sun_path field of a sockaddr_un before
7731 passing it to the kernel. (Not a security issue: kernels are
7732 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7733 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7734 - Don't stack-allocate the list of supplementary GIDs when we're
7735 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7736 could take up to 256K, which is way too much stack. Found by
7737 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7739 o Minor bugfixes (only in 0.2.1.x):
7740 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7741 rely on them. Bugfix on 0.2.1.30.
7742 - Use git revisions instead of svn revisions when generating our
7743 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7745 o Minor features (also included in 0.2.2.x):
7746 - Adjust the expiration time on our SSL session certificates to
7747 better match SSL certs seen in the wild. Resolves ticket 4014.
7748 - Allow nameservers with IPv6 address. Resolves bug 2574.
7749 - Update to the October 4 2011 Maxmind GeoLite Country database.
7752 Changes in version 0.2.3.5-alpha - 2011-09-28
7753 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
7754 bridge relays; fixes an assertion error that many users started hitting
7755 today; and adds the ability to refill token buckets more often than
7756 once per second, allowing significant performance improvements.
7759 - Bridge relays now do their directory fetches inside Tor TLS
7760 connections, like all the other clients do, rather than connecting
7761 directly to the DirPort like public relays do. Removes another
7762 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7763 - Bridges relays now build circuits for themselves in a more similar
7764 way to how clients build them. Removes another avenue for
7765 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7766 when bridges were introduced.
7769 - Fix an "Assertion md->held_by_node == 1 failed" error that could
7770 occur when the same microdescriptor was referenced by two node_t
7771 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
7773 o Major features (networking):
7774 - Add a new TokenBucketRefillInterval option to refill token buckets
7775 more frequently than once per second. This should improve network
7776 performance, alleviate queueing problems, and make traffic less
7777 bursty. Implements proposal 183; closes ticket 3630. Design by
7778 Florian Tschorsch and Björn Scheuermann; implementation by
7782 - Change an integer overflow check in the OpenBSD_Malloc code so
7783 that GCC is less likely to eliminate it as impossible. Patch
7784 from Mansour Moufid. Fixes bug 4059.
7786 o Minor bugfixes (usability):
7787 - Downgrade log messages about circuit timeout calibration from
7788 "notice" to "info": they don't require or suggest any human
7789 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7790 bugfix on 0.2.2.14-alpha.
7792 o Minor features (diagnostics):
7793 - When the system call to create a listener socket fails, log the
7794 error message explaining why. This may help diagnose bug 4027.
7797 Changes in version 0.2.3.4-alpha - 2011-09-13
7798 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
7799 tweak to Tor's TLS handshake that makes relays and bridges that run
7800 this new version reachable from Iran again. It also fixes a few new
7801 bugs in 0.2.3.x, and teaches relays to recognize when they're not
7802 listed in the network consensus and republish.
7804 o Major bugfixes (also part of 0.2.2.33):
7805 - Avoid an assertion failure when reloading a configuration with
7806 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7807 3923; bugfix on 0.2.2.25-alpha.
7809 o Minor features (security, also part of 0.2.2.33):
7810 - Check for replays of the public-key encrypted portion of an
7811 INTRODUCE1 cell, in addition to the current check for replays of
7812 the g^x value. This prevents a possible class of active attacks
7813 by an attacker who controls both an introduction point and a
7814 rendezvous point, and who uses the malleability of AES-CTR to
7815 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7816 that these attacks are infeasible (requiring the attacker to send
7817 on the order of zettabytes of altered cells in a short interval),
7818 but we'd rather block them off in case there are any classes of
7819 this attack that we missed. Reported by Willem Pinckaers.
7821 o Minor features (also part of 0.2.2.33):
7822 - Adjust the expiration time on our SSL session certificates to
7823 better match SSL certs seen in the wild. Resolves ticket 4014.
7824 - Change the default required uptime for a relay to be accepted as
7825 a HSDir (hidden service directory) from 24 hours to 25 hours.
7826 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7827 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7828 authorities to abstain from voting on assignment of the HSDir
7829 consensus flag. Related to bug 2649.
7830 - Update to the September 6 2011 Maxmind GeoLite Country database.
7832 o Minor bugfixes (also part of 0.2.2.33):
7833 - Demote the 'replay detected' log message emitted when a hidden
7834 service receives the same Diffie-Hellman public key in two different
7835 INTRODUCE2 cells to info level. A normal Tor client can cause that
7836 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7837 fixes part of bug 2442.
7838 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7839 level. There is nothing that a hidden service's operator can do
7840 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7842 - Clarify a log message specifying the characters permitted in
7843 HiddenServiceAuthorizeClient client names. Previously, the log
7844 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7845 given the impression that every ASCII character between "+" and "_"
7846 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7848 o Build fixes (also part of 0.2.2.33):
7849 - Clean up some code issues that prevented Tor from building on older
7850 BSDs. Fixes bug 3894; reported by "grarpamp".
7851 - Search for a platform-specific version of "ar" when cross-compiling.
7852 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7855 - Fix a bug where the SocksPort option (for example) would get
7856 ignored and replaced by the default if a SocksListenAddress
7857 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
7861 - Relays now try regenerating and uploading their descriptor more
7862 frequently if they are not listed in the consensus, or if the
7863 version of their descriptor listed in the consensus is too
7864 old. This fix should prevent situations where a server declines
7865 to re-publish itself because it has done so too recently, even
7866 though the authorities decided not to list its recent-enough
7867 descriptor. Fix for bug 3327.
7870 - Relays now include a reason for regenerating their descriptors
7871 in an HTTP header when uploading to the authorities. This will
7872 make it easier to debug descriptor-upload issues in the future.
7873 - When starting as root and then changing our UID via the User
7874 control option, and we have a ControlSocket configured, make sure
7875 that the ControlSocket is owned by the same account that Tor will
7876 run under. Implements ticket 3421; fix by Jérémy Bobbio.
7879 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
7880 utility function used in the control-port code). This shouldn't
7881 ever happen unless Tor is completely out of memory, but if it did
7882 happen and Tor somehow recovered from it, Tor could have sent a log
7883 message to a control port in the middle of a reply to a controller
7884 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
7885 - Make 'FetchUselessDescriptors' cause all descriptor types and
7886 all consensus types (including microdescriptors) to get fetched.
7887 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
7890 - Make a new "entry connection" struct as an internal subtype of "edge
7891 connection", to simplify the code and make exit connections smaller.
7894 Changes in version 0.2.2.33 - 2011-09-13
7895 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
7896 TLS handshake that makes relays and bridges that run this new version
7897 reachable from Iran again.
7900 - Avoid an assertion failure when reloading a configuration with
7901 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7902 3923; bugfix on 0.2.2.25-alpha.
7904 o Minor features (security):
7905 - Check for replays of the public-key encrypted portion of an
7906 INTRODUCE1 cell, in addition to the current check for replays of
7907 the g^x value. This prevents a possible class of active attacks
7908 by an attacker who controls both an introduction point and a
7909 rendezvous point, and who uses the malleability of AES-CTR to
7910 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7911 that these attacks are infeasible (requiring the attacker to send
7912 on the order of zettabytes of altered cells in a short interval),
7913 but we'd rather block them off in case there are any classes of
7914 this attack that we missed. Reported by Willem Pinckaers.
7917 - Adjust the expiration time on our SSL session certificates to
7918 better match SSL certs seen in the wild. Resolves ticket 4014.
7919 - Change the default required uptime for a relay to be accepted as
7920 a HSDir (hidden service directory) from 24 hours to 25 hours.
7921 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7922 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7923 authorities to abstain from voting on assignment of the HSDir
7924 consensus flag. Related to bug 2649.
7925 - Update to the September 6 2011 Maxmind GeoLite Country database.
7927 o Minor bugfixes (documentation and log messages):
7928 - Correct the man page to explain that HashedControlPassword and
7929 CookieAuthentication can both be set, in which case either method
7930 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7931 when we decided to allow these config options to both be set. Issue
7933 - Demote the 'replay detected' log message emitted when a hidden
7934 service receives the same Diffie-Hellman public key in two different
7935 INTRODUCE2 cells to info level. A normal Tor client can cause that
7936 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7937 fixes part of bug 2442.
7938 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7939 level. There is nothing that a hidden service's operator can do
7940 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7942 - Clarify a log message specifying the characters permitted in
7943 HiddenServiceAuthorizeClient client names. Previously, the log
7944 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7945 given the impression that every ASCII character between "+" and "_"
7946 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7949 - Provide a substitute implementation of lround() for MSVC, which
7950 apparently lacks it. Patch from Gisle Vanem.
7951 - Clean up some code issues that prevented Tor from building on older
7952 BSDs. Fixes bug 3894; reported by "grarpamp".
7953 - Search for a platform-specific version of "ar" when cross-compiling.
7954 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7957 Changes in version 0.2.3.3-alpha - 2011-09-01
7958 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
7959 security, and provides client-side support for the microdescriptor
7960 and optimistic data features introduced earlier in the 0.2.3.x
7961 series. It also includes numerous critical bugfixes in the (optional)
7962 bufferevent-based networking backend.
7964 o Major features (stream isolation):
7965 - You can now configure Tor so that streams from different
7966 applications are isolated on different circuits, to prevent an
7967 attacker who sees your streams as they leave an exit node from
7968 linking your sessions to one another. To do this, choose some way
7969 to distinguish the applications: have them connect to different
7970 SocksPorts, or have one of them use SOCKS4 while the other uses
7971 SOCKS5, or have them pass different authentication strings to the
7972 SOCKS proxy. Then, use the new SocksPort syntax to configure the
7973 degree of isolation you need. This implements Proposal 171.
7974 - There's a new syntax for specifying multiple client ports (such as
7975 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
7976 multiple *Port entries with full addr:port syntax on each.
7977 The old *ListenAddress format is still supported, but you can't
7978 mix it with the new *Port syntax.
7980 o Major features (other):
7981 - Enable microdescriptor fetching by default for clients. This allows
7982 clients to download a much smaller amount of directory information.
7983 To disable it (and go back to the old-style consensus and
7984 descriptors), set "UseMicrodescriptors 0" in your torrc file.
7985 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
7986 "PortForwarding" config option), now supports Windows.
7987 - When using an exit relay running 0.2.3.x, clients can now
7988 "optimistically" send data before the exit relay reports that
7989 the stream has opened. This saves a round trip when starting
7990 connections where the client speaks first (such as web browsing).
7991 This behavior is controlled by a consensus parameter (currently
7992 disabled). To turn it on or off manually, use the "OptimisticData"
7993 torrc option. Implements proposal 181; code by Ian Goldberg.
7995 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
7996 - When using IOCP on Windows, we need to enable Libevent windows
7998 - The IOCP backend now works even when the user has not specified
7999 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
8000 Fixes part of bug 3752.
8001 - Correctly record the bytes we've read and written when using
8002 bufferevents, so that we can include them in our bandwidth history
8003 and advertised bandwidth. Fixes bug 3803.
8004 - Apply rate-limiting only at the bottom of a chain of filtering
8005 bufferevents. This prevents us from filling up internal read
8006 buffers and violating rate-limits when filtering bufferevents
8007 are enabled. Fixes part of bug 3804.
8008 - Add high-watermarks to the output buffers for filtered
8009 bufferevents. This prevents us from filling up internal write
8010 buffers and wasting CPU cycles when filtering bufferevents are
8011 enabled. Fixes part of bug 3804.
8012 - Correctly notice when data has been written from a bufferevent
8013 without flushing it completely. Fixes bug 3805.
8014 - Fix a bug where server-side tunneled bufferevent-based directory
8015 streams would get closed prematurely. Fixes bug 3814.
8016 - Fix a use-after-free error with per-connection rate-limiting
8017 buckets. Fixes bug 3888.
8019 o Major bugfixes (also part of 0.2.2.31-rc):
8020 - If we're configured to write our ControlPorts to disk, only write
8021 them after switching UID and creating the data directory. This way,
8022 we don't fail when starting up with a nonexistent DataDirectory
8023 and a ControlPortWriteToFile setting based on that directory. Fixes
8024 bug 3747; bugfix on Tor 0.2.2.26-beta.
8027 - Added a new CONF_CHANGED event so that controllers can be notified
8028 of any configuration changes made by other controllers, or by the
8029 user. Implements ticket 1692.
8030 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
8031 leak when using bufferevents, and lets Libevent worry about how to
8032 best copy data out of a buffer.
8033 - Replace files in stats/ rather than appending to them. Now that we
8034 include statistics in extra-info descriptors, it makes no sense to
8035 keep old statistics forever. Implements ticket 2930.
8037 o Minor features (build compatibility):
8038 - Limited, experimental support for building with nmake and MSVC.
8039 - Provide a substitute implementation of lround() for MSVC, which
8040 apparently lacks it. Patch from Gisle Vanem.
8042 o Minor features (also part of 0.2.2.31-rc):
8043 - Update to the August 2 2011 Maxmind GeoLite Country database.
8045 o Minor bugfixes (on 0.2.3.x-alpha):
8046 - Fix a spurious warning when parsing SOCKS requests with
8047 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
8048 - Get rid of a harmless warning that could happen on relays running
8049 with bufferevents. The warning was caused by someone doing an http
8050 request to a relay's orport. Also don't warn for a few related
8051 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
8053 o Minor bugfixes (on 2.2.x and earlier):
8054 - Correct the man page to explain that HashedControlPassword and
8055 CookieAuthentication can both be set, in which case either method
8056 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8057 when we decided to allow these config options to both be set. Issue
8059 - The "--quiet" and "--hush" options now apply not only to Tor's
8060 behavior before logs are configured, but also to Tor's behavior in
8061 the absense of configured logs. Fixes bug 3550; bugfix on
8064 o Minor bugfixes (also part of 0.2.2.31-rc):
8065 - Write several files in text mode, on OSes that distinguish text
8066 mode from binary mode (namely, Windows). These files are:
8067 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8068 that collect those statistics; 'client_keys' and 'hostname' for
8069 hidden services that use authentication; and (in the tor-gencert
8070 utility) newly generated identity and signing keys. Previously,
8071 we wouldn't specify text mode or binary mode, leading to an
8072 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8073 the DirRecordUsageByCountry option which would have triggered
8074 the assertion failure was added), although this assertion failure
8075 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8076 - Selectively disable deprecation warnings on OS X because Lion
8077 started deprecating the shipped copy of openssl. Fixes bug 3643.
8078 - Remove an extra pair of quotation marks around the error
8079 message in control-port STATUS_GENERAL BUG events. Bugfix on
8080 0.1.2.6-alpha; fixes bug 3732.
8081 - When unable to format an address as a string, report its value
8082 as "???" rather than reusing the last formatted address. Bugfix
8085 o Code simplifications and refactoring:
8086 - Rewrite the listener-selection logic so that parsing which ports
8087 we want to listen on is now separate from binding to the ports
8091 - Building Tor with bufferevent support now requires Libevent
8092 2.0.13-stable or later. Previous versions of Libevent had bugs in
8093 SSL-related bufferevents and related issues that would make Tor
8094 work badly with bufferevents. Requiring 2.0.13-stable also allows
8095 Tor with bufferevents to take advantage of Libevent APIs
8096 introduced after 2.0.8-rc.
8099 Changes in version 0.2.2.32 - 2011-08-27
8100 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8101 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8102 a founder of the PETS community, a leader in our field, a mentor,
8103 and a friend. He left us with these words: "I had the possibility
8104 to contribute to this world that is not as it should be. I hope I
8105 could help in some areas to make the world a better place, and that
8106 I could also encourage other people to be engaged in improving the
8107 world. Please, stay engaged. This world needs you, your love, your
8108 initiative -- now I cannot be part of that anymore."
8110 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8111 ready. More than two years in the making, this release features improved
8112 client performance and hidden service reliability, better compatibility
8113 for Android, correct behavior for bridges that listen on more than
8114 one address, more extensible and flexible directory object handling,
8115 better reporting of network statistics, improved code security, and
8116 many many other features and bugfixes.
8119 Changes in version 0.2.2.31-rc - 2011-08-17
8120 Tor 0.2.2.31-rc is the second and hopefully final release candidate
8121 for the Tor 0.2.2.x series.
8124 - Remove an extra pair of quotation marks around the error
8125 message in control-port STATUS_GENERAL BUG events. Bugfix on
8126 0.1.2.6-alpha; fixes bug 3732.
8127 - If we're configured to write our ControlPorts to disk, only write
8128 them after switching UID and creating the data directory. This way,
8129 we don't fail when starting up with a nonexistent DataDirectory
8130 and a ControlPortWriteToFile setting based on that directory. Fixes
8131 bug 3747; bugfix on Tor 0.2.2.26-beta.
8134 - Update to the August 2 2011 Maxmind GeoLite Country database.
8137 - Allow GETINFO fingerprint to return a fingerprint even when
8138 we have not yet built a router descriptor. Fixes bug 3577;
8139 bugfix on 0.2.0.1-alpha.
8140 - Write several files in text mode, on OSes that distinguish text
8141 mode from binary mode (namely, Windows). These files are:
8142 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8143 that collect those statistics; 'client_keys' and 'hostname' for
8144 hidden services that use authentication; and (in the tor-gencert
8145 utility) newly generated identity and signing keys. Previously,
8146 we wouldn't specify text mode or binary mode, leading to an
8147 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8148 the DirRecordUsageByCountry option which would have triggered
8149 the assertion failure was added), although this assertion failure
8150 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8151 - Selectively disable deprecation warnings on OS X because Lion
8152 started deprecating the shipped copy of openssl. Fixes bug 3643.
8153 - When unable to format an address as a string, report its value
8154 as "???" rather than reusing the last formatted address. Bugfix
8158 Changes in version 0.2.3.2-alpha - 2011-07-18
8159 Tor 0.2.3.2-alpha introduces two new experimental features:
8160 microdescriptors and pluggable transports. It also continues cleaning
8161 up a variety of recently introduced features.
8164 - Clients can now use microdescriptors instead of regular descriptors
8165 to build circuits. Microdescriptors are authority-generated
8166 summaries of regular descriptors' contents, designed to change
8167 very rarely (see proposal 158 for details). This feature is
8168 designed to save bandwidth, especially for clients on slow internet
8169 connections. It's off by default for now, since nearly no caches
8170 support it, but it will be on-by-default for clients in a future
8171 version. You can use the UseMicrodescriptors option to turn it on.
8172 - Tor clients using bridges can now be configured to use a separate
8173 'transport' proxy for each bridge. This approach helps to resist
8174 censorship by allowing bridges to use protocol obfuscation
8175 plugins. It implements part of proposal 180. Implements ticket 2841.
8176 - While we're trying to bootstrap, record how many TLS connections
8177 fail in each state, and report which states saw the most failures
8178 in response to any bootstrap failures. This feature may speed up
8179 diagnosis of censorship events. Implements ticket 3116.
8181 o Major bugfixes (on 0.2.3.1-alpha):
8182 - When configuring a large set of nodes in EntryNodes (as with
8183 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
8184 random subset to be guards, and choose them in random
8185 order. Fixes bug 2798.
8186 - Tor could crash when remembering a consensus in a non-used consensus
8187 flavor without having a current consensus set. Fixes bug 3361.
8188 - Comparing an unknown address to a microdescriptor's shortened exit
8189 policy would always give a "rejected" result. Fixes bug 3599.
8190 - Using microdescriptors as a client no longer prevents Tor from
8191 uploading and downloading hidden service descriptors. Fixes
8195 - Allow nameservers with IPv6 address. Resolves bug 2574.
8196 - Accept attempts to include a password authenticator in the
8197 handshake, as supported by SOCKS5. This handles SOCKS clients that
8198 don't know how to omit a password when authenticating. Resolves
8200 - When configuring a large set of nodes in EntryNodes, and there are
8201 enough of them listed as Guard so that we don't need to consider
8202 the non-guard entries, prefer the ones listed with the Guard flag.
8203 - Check for and recover from inconsistency in the microdescriptor
8204 cache. This will make it harder for us to accidentally free a
8205 microdescriptor without removing it from the appropriate data
8206 structures. Fixes issue 3135; issue noted by "wanoskarnet".
8207 - Log SSL state transitions at log level DEBUG, log domain
8208 HANDSHAKE. This can be useful for debugging censorship events.
8209 Implements ticket 3264.
8210 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
8211 implements ticket 3439.
8213 o Minor bugfixes (on 0.2.3.1-alpha):
8214 - Do not free all general-purpose regular descriptors just
8215 because microdescriptor use is enabled. Fixes bug 3113.
8216 - Correctly link libevent_openssl when --enable-static-libevent
8217 is passed to configure. Fixes bug 3118.
8218 - Bridges should not complain during their heartbeat log messages that
8219 they are unlisted in the consensus: that's more or less the point
8220 of being a bridge. Fixes bug 3183.
8221 - Report a SIGNAL event to controllers when acting on a delayed
8222 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
8223 event to the controller if we acted on a SIGNAL NEWNYM command
8224 immediately, and otherwise not report a SIGNAL event for the
8225 command at all. Fixes bug 3349.
8226 - Fix a crash when handling the SIGNAL controller command or
8227 reporting ERR-level status events with bufferevents enabled. Found
8228 by Robert Ransom. Fixes bug 3367.
8229 - Always ship the tor-fw-helper manpage in our release tarballs.
8230 Fixes bug 3389. Reported by Stephen Walker.
8231 - Fix a class of double-mark-for-close bugs when bufferevents
8232 are enabled. Fixes bug 3403.
8233 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
8234 - Add SIGNAL to the list returned by the 'GETINFO events/names'
8235 control-port command. Fixes part of bug 3465.
8236 - Prevent using negative indices during unit test runs when read_all()
8237 fails. Spotted by coverity.
8238 - Fix a rare memory leak when checking the nodelist without it being
8239 present. Found by coverity.
8240 - Only try to download a microdescriptor-flavored consensus from
8241 a directory cache that provides them.
8243 o Minor bugfixes (on 0.2.2.x and earlier):
8244 - Assert that hidden-service-related operations are not performed
8245 using single-hop circuits. Previously, Tor would assert that
8246 client-side streams are not attached to single-hop circuits,
8247 but not that other sensitive operations on the client and service
8248 side are not performed using single-hop circuits. Fixes bug 3332;
8250 - Don't publish a new relay descriptor when we reload our onion key,
8251 unless the onion key has actually changed. Fixes bug 3263 and
8252 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
8253 - Allow GETINFO fingerprint to return a fingerprint even when
8254 we have not yet built a router descriptor. Fixes bug 3577;
8255 bugfix on 0.2.0.1-alpha.
8256 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
8257 on 0.2.2.4-alpha; fixes bug 3427.
8259 o Code simplification and refactoring:
8260 - Use tor_sscanf() in place of scanf() in more places through the
8261 code. This makes us a little more locale-independent, and
8262 should help shut up code-analysis tools that can't tell
8263 a safe sscanf string from a dangerous one.
8264 - Use tt_assert(), not tor_assert(), for checking for test failures.
8265 This makes the unit tests more able to go on in the event that
8267 - Split connection_about_to_close() into separate functions for each
8271 - On Windows, we now define the _WIN32_WINNT macros only if they
8272 are not already defined. This lets the person building Tor decide,
8273 if they want, to require a later version of Windows.
8276 Changes in version 0.2.2.30-rc - 2011-07-07
8277 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
8278 series. It fixes a few smaller bugs, but generally appears stable.
8279 Please test it and let us know whether it is!
8282 - Send a SUCCEEDED stream event to the controller when a reverse
8283 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
8284 discovered by katmagic.
8285 - Always NUL-terminate the sun_path field of a sockaddr_un before
8286 passing it to the kernel. (Not a security issue: kernels are
8287 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8288 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8289 - Don't stack-allocate the list of supplementary GIDs when we're
8290 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8291 could take up to 256K, which is way too much stack. Found by
8292 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8293 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
8294 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
8295 fixes part of bug 3465.
8296 - Fix a memory leak when receiving a descriptor for a hidden
8297 service we didn't ask for. Found by Coverity; CID #30. Bugfix
8301 - Update to the July 1 2011 Maxmind GeoLite Country database.
8304 Changes in version 0.2.2.29-beta - 2011-06-20
8305 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
8306 have bridge lines in their torrc but don't want to use them; gets
8307 us closer to having the control socket feature working on Debian;
8308 and fixes a variety of smaller bugs.
8311 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
8312 When we changed the default behavior to "use bridges if any
8313 are listed in the torrc", we surprised users who had bridges
8314 in their torrc files but who didn't actually want to use them.
8315 Partial resolution for bug 3354.
8318 - Don't attach new streams to old rendezvous circuits after SIGNAL
8319 NEWNYM. Previously, we would keep using an existing rendezvous
8320 circuit if it remained open (i.e. if it were kept open by a
8321 long-lived stream, or if a new stream were attached to it before
8322 Tor could notice that it was old and no longer in use). Bugfix on
8323 0.1.1.15-rc; fixes bug 3375.
8326 - Fix a bug when using ControlSocketsGroupWritable with User. The
8327 directory's group would be checked against the current group, not
8328 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
8329 bugfix on 0.2.2.26-beta.
8330 - Make connection_printf_to_buf()'s behavior sane. Its callers
8331 expect it to emit a CRLF iff the format string ends with CRLF;
8332 it actually emitted a CRLF iff (a) the format string ended with
8333 CRLF or (b) the resulting string was over 1023 characters long or
8334 (c) the format string did not end with CRLF *and* the resulting
8335 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
8336 fixes part of bug 3407.
8337 - Make send_control_event_impl()'s behavior sane. Its callers
8338 expect it to always emit a CRLF at the end of the string; it
8339 might have emitted extra control characters as well. Bugfix on
8340 0.1.1.9-alpha; fixes another part of bug 3407.
8341 - Make crypto_rand_int() check the value of its input correctly.
8342 Previously, it accepted values up to UINT_MAX, but could return a
8343 negative number if given a value above INT_MAX+1. Found by George
8344 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
8345 - Avoid a segfault when reading a malformed circuit build state
8346 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
8348 - When asked about a DNS record type we don't support via a
8349 client DNSPort, reply with NOTIMPL rather than an empty
8350 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8351 - Fix a rare memory leak during stats writing. Found by coverity.
8354 - Update to the June 1 2011 Maxmind GeoLite Country database.
8356 o Code simplifications and refactoring:
8357 - Remove some dead code as indicated by coverity.
8358 - Remove a few dead assignments during router parsing. Found by
8360 - Add some forgotten return value checks during unit tests. Found
8362 - Don't use 1-bit wide signed bit fields. Found by coverity.
8365 Changes in version 0.2.2.28-beta - 2011-06-04
8366 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
8367 fixed a big bug in whether relays stay in the consensus consistently,
8368 we moved closer to handling bridges and hidden services correctly,
8369 and we started the process of better handling the dreaded "my Vidalia
8370 died, and now my Tor demands a password when I try to reconnect to it"
8374 - Don't decide to make a new descriptor when receiving a HUP signal.
8375 This bug has caused a lot of 0.2.2.x relays to disappear from the
8376 consensus periodically. Fixes the most common case of triggering
8377 bug 1810; bugfix on 0.2.2.7-alpha.
8378 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
8379 - Don't try to build descriptors if "ORPort auto" is set and we
8380 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
8382 - Resolve a crash that occurred when setting BridgeRelay to 1 with
8383 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
8384 - Apply circuit timeouts to opened hidden-service-related circuits
8385 based on the correct start time. Previously, we would apply the
8386 circuit build timeout based on time since the circuit's creation;
8387 it was supposed to be applied based on time since the circuit
8388 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8389 - Use the same circuit timeout for client-side introduction
8390 circuits as for other four-hop circuits, rather than the timeout
8391 for single-hop directory-fetch circuits; the shorter timeout may
8392 have been appropriate with the static circuit build timeout in
8393 0.2.1.x and earlier, but caused many hidden service access attempts
8394 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
8395 on 0.2.2.2-alpha; fixes another part of bug 1297.
8396 - In ticket 2511 we fixed a case where you could use an unconfigured
8397 bridge if you had configured it as a bridge the last time you ran
8398 Tor. Now fix another edge case: if you had configured it as a bridge
8399 but then switched to a different bridge via the controller, you
8400 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
8404 - Add an __OwningControllerProcess configuration option and a
8405 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8406 that when it exits, Tor will shut down. Implements feature 3049.
8407 - If "UseBridges 1" is set and no bridges are configured, Tor will
8408 now refuse to build any circuits until some bridges are set.
8409 If "UseBridges auto" is set, Tor will use bridges if they are
8410 configured and we are not running as a server, but otherwise will
8411 make circuits as usual. The new default is "auto". Patch by anonym,
8412 so the Tails LiveCD can stop automatically revealing you as a Tor
8416 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8417 - Remove a trailing asterisk from "exit-policy/default" in the
8418 output of the control port command "GETINFO info/names". Bugfix
8420 - Use a wide type to hold sockets when built for 64-bit Windows builds.
8422 - Warn when the user configures two HiddenServiceDir lines that point
8423 to the same directory. Bugfix on 0.0.6 (the version introducing
8424 HiddenServiceDir); fixes bug 3289.
8425 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
8426 part of bug 2748; bugfix on 0.2.0.10-alpha.
8427 - Log malformed requests for rendezvous descriptors as protocol
8428 warnings, not warnings. Also, use a more informative log message
8429 in case someone sees it at log level warning without prior
8430 info-level messages. Fixes the other part of bug 2748; bugfix
8432 - Clear the table recording the time of the last request for each
8433 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
8434 Previously, we would clear our HS descriptor cache on SIGNAL
8435 NEWNYM, but if we had previously retrieved a descriptor (or tried
8436 to) from every directory responsible for it, we would refuse to
8437 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
8439 - Fix a log message that said "bits" while displaying a value in
8440 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8442 - When checking for 1024-bit keys, check for 1024 bits, not 128
8443 bytes. This allows Tor to correctly discard keys of length 1017
8444 through 1023. Bugfix on 0.0.9pre5.
8447 - Relays now log the reason for publishing a new relay descriptor,
8448 so we have a better chance of hunting down instances of bug 1810.
8449 Resolves ticket 3252.
8450 - Revise most log messages that refer to nodes by nickname to
8451 instead use the "$key=nickname at address" format. This should be
8452 more useful, especially since nicknames are less and less likely
8453 to be unique. Resolves ticket 3045.
8454 - Log (at info level) when purging pieces of hidden-service-client
8455 state because of SIGNAL NEWNYM.
8458 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8459 anything since 0.2.1.16-rc.
8462 Changes in version 0.2.2.27-beta - 2011-05-18
8463 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
8464 release, and also adds a few more general bugfixes.
8467 - Fix a crash bug when changing bridges in a running Tor process.
8468 Fixes bug 3213; bugfix on 0.2.2.26-beta.
8469 - When the controller configures a new bridge, don't wait 10 to 60
8470 seconds before trying to fetch its descriptor. Bugfix on
8471 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8474 - Require that onion keys have exponent 65537 in microdescriptors too.
8475 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
8476 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8477 Changed the limit to 512 characters by removing base64 newlines.
8478 Fixes bug 2752. Fix by Michael Yakubovich.
8479 - When a client starts or stops using bridges, never use a circuit
8480 that was built before the configuration change. This behavior could
8481 put at risk a user who uses bridges to ensure that her traffic
8482 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8486 Changes in version 0.2.2.26-beta - 2011-05-17
8487 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
8488 also introduces a new "socksport auto" approach that should make it
8489 easier to run multiple Tors on the same system, and does a lot of
8490 cleanup to get us closer to a release candidate.
8492 o Security/privacy fixes:
8493 - Replace all potentially sensitive memory comparison operations
8494 with versions whose runtime does not depend on the data being
8495 compared. This will help resist a class of attacks where an
8496 adversary can use variations in timing information to learn
8497 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8498 implementation by Robert Ransom based partially on code by DJB.)
8499 - When receiving a hidden service descriptor, check that it is for
8500 the hidden service we wanted. Previously, Tor would store any
8501 hidden service descriptors that a directory gave it, whether it
8502 wanted them or not. This wouldn't have let an attacker impersonate
8503 a hidden service, but it did let directories pre-seed a client
8504 with descriptors that it didn't want. Bugfix on 0.0.6.
8505 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8506 DNS cache entries, and virtual address mappings: that's what
8507 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8510 - The options SocksPort, ControlPort, and so on now all accept a
8511 value "auto" that opens a socket on an OS-selected port. A
8512 new ControlPortWriteToFile option tells Tor to write its
8513 actual control port or ports to a chosen file. If the option
8514 ControlPortFileGroupReadable is set, the file is created as
8515 group-readable. Now users can run two Tor clients on the same
8516 system without needing to manually mess with parameters. Resolves
8517 part of ticket 3076.
8518 - Set SO_REUSEADDR on all sockets, not just listeners. This should
8519 help busy exit nodes avoid running out of useable ports just
8520 because all the ports have been used in the near past. Resolves
8524 - New "GETINFO net/listeners/(type)" controller command to return
8525 a list of addresses and ports that are bound for listeners for a
8526 given connection type. This is useful when the user has configured
8527 "SocksPort auto" and the controller needs to know which port got
8528 chosen. Resolves another part of ticket 3076.
8529 - Add a new ControlSocketsGroupWritable configuration option: when
8530 it is turned on, ControlSockets are group-writeable by the default
8531 group of the current user. Patch by Jérémy Bobbio; implements
8533 - Tor now refuses to create a ControlSocket in a directory that is
8534 world-readable (or group-readable if ControlSocketsGroupWritable
8535 is 0). This is necessary because some operating systems do not
8536 enforce permissions on an AF_UNIX sockets. Permissions on the
8537 directory holding the socket, however, seems to work everywhere.
8538 - Rate-limit a warning about failures to download v2 networkstatus
8539 documents. Resolves part of bug 1352.
8540 - Backport code from 0.2.3.x that allows directory authorities to
8541 clean their microdescriptor caches. Needed to resolve bug 2230.
8542 - When an HTTPS proxy reports "403 Forbidden", we now explain
8543 what it means rather than calling it an unexpected status code.
8544 Closes bug 2503. Patch from Michael Yakubovich.
8545 - Update to the May 1 2011 Maxmind GeoLite Country database.
8548 - Authorities now clean their microdesc cache periodically and when
8549 reading from disk initially, not only when adding new descriptors.
8550 This prevents a bug where we could lose microdescriptors. Bugfix
8551 on 0.2.2.6-alpha. Fixes bug 2230.
8552 - Do not crash when our configuration file becomes unreadable, for
8553 example due to a permissions change, between when we start up
8554 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8556 - Avoid a bug that would keep us from replacing a microdescriptor
8557 cache on Windows. (We would try to replace the file while still
8558 holding it open. That's fine on Unix, but Windows doesn't let us
8559 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
8560 - Add missing explanations for the authority-related torrc options
8561 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
8562 man page. Resolves issue 2379.
8563 - As an authority, do not upload our own vote or signature set to
8564 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
8565 it would get flagged as a duplicate. Resolves bug 3026.
8566 - Accept hidden service descriptors if we think we might be a hidden
8567 service directory, regardless of what our consensus says. This
8568 helps robustness, since clients and hidden services can sometimes
8569 have a more up-to-date view of the network consensus than we do,
8570 and if they think that the directory authorities list us a HSDir,
8571 we might actually be one. Related to bug 2732; bugfix on
8573 - When a controller changes TrackHostExits, remove mappings for
8574 hosts that should no longer have their exits tracked. Bugfix on
8576 - When a controller changes VirtualAddrNetwork, remove any mappings
8577 for hosts that were automapped to the old network. Bugfix on
8579 - When a controller changes one of the AutomapHosts* options, remove
8580 any mappings for hosts that should no longer be automapped. Bugfix
8582 - Do not reset the bridge descriptor download status every time we
8583 re-parse our configuration or get a configuration change. Fixes
8584 bug 3019; bugfix on 0.2.0.3-alpha.
8586 o Minor bugfixes (code cleanup):
8587 - When loading the microdesc journal, remember its current size.
8588 In 0.2.2, this helps prevent the microdesc journal from growing
8589 without limit on authorities (who are the only ones to use it in
8590 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8591 Fix posted by "cypherpunks."
8592 - The microdesc journal is supposed to get rebuilt only if it is
8593 at least _half_ the length of the store, not _twice_ the length
8594 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8595 - Fix a potential null-pointer dereference while computing a
8596 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
8598 - Avoid a possible null-pointer dereference when rebuilding the mdesc
8599 cache without actually having any descriptors to cache. Bugfix on
8600 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
8601 - If we fail to compute the identity digest of a v3 legacy keypair,
8602 warn, and don't use a buffer-full of junk instead. Bugfix on
8603 0.2.1.1-alpha; fixes bug 3106.
8604 - Resolve an untriggerable issue in smartlist_string_num_isin(),
8605 where if the function had ever in the future been used to check
8606 for the presence of a too-large number, it would have given an
8607 incorrect result. (Fortunately, we only used it for 16-bit
8608 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
8609 - Require that introduction point keys and onion handshake keys
8610 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8614 - Caches no longer download and serve v2 networkstatus documents
8615 unless FetchV2Networkstatus flag is set: these documents haven't
8616 haven't been used by clients or relays since 0.2.0.x. Resolves
8620 Changes in version 0.2.3.1-alpha - 2011-05-05
8621 Tor 0.2.3.1-alpha adds some new experimental features, including support
8622 for an improved network IO backend, IOCP networking on Windows,
8623 microdescriptor caching, "fast-start" support for streams, and automatic
8624 home router configuration. There are also numerous internal improvements
8625 to try to make the code easier for developers to work with.
8627 This is the first alpha release in a new series, so expect there to be
8628 bugs. Users who would rather test out a more stable branch should
8629 stay with 0.2.2.x for now.
8632 - Tor can now optionally build with the "bufferevents" buffered IO
8633 backend provided by Libevent 2. To use this feature, make sure you
8634 have the latest possible version of Libevent, and pass the
8635 --enable-bufferevents flag to configure when building Tor from
8636 source. This feature will make our networking code more flexible,
8637 let us stack layers on each other, and let us use more efficient
8638 zero-copy transports where available.
8639 - As an experimental feature, Tor can use IOCP for networking on Windows.
8640 Once this code is tuned and optimized, it promises much better
8641 performance than the select-based backend we've used in the past. To
8642 try this feature, you must build Tor with Libevent 2, configure Tor
8643 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
8644 your torrc. There are known bugs here: only try this if you can help
8645 debug it as it breaks.
8646 - The EntryNodes option can now include country codes like {de} or IP
8647 addresses or network masks. Previously we had disallowed these options
8648 because we didn't have an efficient way to keep the list up to
8649 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
8650 - Exit nodes now accept and queue data on not-yet-connected streams.
8651 Previously, the client wasn't allowed to send data until the stream was
8652 connected, which slowed down all connections. This change will enable
8653 clients to perform a "fast-start" on streams and send data without
8654 having to wait for a confirmation that the stream has opened. (Patch
8655 from Ian Goldberg; implements the server side of Proposal 174.)
8656 - Tor now has initial support for automatic port mapping on the many
8657 home routers that support NAT-PMP or UPnP. (Not yet supported on
8658 Windows). To build the support code, you'll need to have libnatpnp
8659 library and/or the libminiupnpc library, and you'll need to enable the
8660 feature specifically by passing "--enable-upnp" and/or
8661 "--enable-natpnp" to configure. To turn it on, use the new
8662 PortForwarding option.
8663 - Caches now download, cache, and serve multiple "flavors" of the
8664 consensus, including a flavor that describes microdescriptors.
8665 - Caches now download, cache, and serve microdescriptors -- small
8666 summaries of router descriptors that are authenticated by all of the
8667 directory authorities. Once enough caches are running this code,
8668 clients will be able to save significant amounts of directory bandwidth
8669 by downloading microdescriptors instead of router descriptors.
8672 - Make logging resolution configurable with a new LogTimeGranularity
8673 option, and change the default from 1 millisecond to 1 second.
8674 Implements enhancement 1668.
8675 - We log which torrc file we're using on startup. Implements ticket
8677 - Ordinarily, Tor does not count traffic from private addresses (like
8678 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
8679 There is now a new option, CountPrivateBandwidth, to disable this
8680 behavior. Patch from Daniel Cagara.
8681 - New --enable-static-tor configure option for building Tor as
8682 statically as possible. Idea, general hackery and thoughts from
8683 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
8685 - If you set the NumCPUs option to 0, Tor will now try to detect how
8686 many CPUs you have. This is the new default behavior.
8687 - Turn on directory request statistics by default and include them in
8688 extra-info descriptors. Don't break if we have no GeoIP database.
8689 - Relays that set "ConnDirectionStatistics 1" write statistics on the
8690 bidirectional use of connections to disk every 24 hours.
8691 - Add a GeoIP file digest to the extra-info descriptor. Implements
8693 - The NodeFamily option -- which let you declare that you want to
8694 consider nodes to be part of a family whether they list themselves
8695 that way or not -- now allows IP address ranges and country codes.
8696 - Add a new 'Heartbeat' log message type to periodically log a message
8697 describing Tor's status at level Notice. This feature is meant for
8698 operators who log at notice, and want to make sure that their Tor
8699 server is still working. Implementation by George Kadianakis.
8701 o Minor bugfixes (on 0.2.2.25-alpha):
8702 - When loading the microdesc journal, remember its current size.
8703 In 0.2.2, this helps prevent the microdesc journal from growing
8704 without limit on authorities (who are the only ones to use it in
8705 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8706 Fix posted by "cypherpunks."
8707 - The microdesc journal is supposed to get rebuilt only if it is
8708 at least _half_ the length of the store, not _twice_ the length
8709 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8710 - If as an authority we fail to compute the identity digest of a v3
8711 legacy keypair, warn, and don't use a buffer-full of junk instead.
8712 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
8713 - Authorities now clean their microdesc cache periodically and when
8714 reading from disk initially, not only when adding new descriptors.
8715 This prevents a bug where we could lose microdescriptors. Bugfix
8718 o Minor features (controller):
8719 - Add a new SIGNAL event to the controller interface so that
8720 controllers can be notified when Tor handles a signal. Resolves
8721 issue 1955. Patch by John Brooks.
8722 - Add a new GETINFO option to get total bytes read and written. Patch
8723 from pipe, revised by atagar. Resolves ticket 2345.
8724 - Implement some GETINFO controller fields to provide information about
8725 the Tor process's pid, euid, username, and resource limits.
8728 - Our build system requires automake 1.6 or later to create the
8729 Makefile.in files. Previously, you could have used 1.4.
8730 This only affects developers and people building Tor from git;
8731 people who build Tor from the source distribution without changing
8732 the Makefile.am files should be fine.
8733 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
8734 so on. This is more robust against some of the failure modes
8735 associated with running the autotools pieces on their own.
8737 o Minor packaging issues:
8738 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
8739 already created. Patch from Andreas Stieger. Fixes bug 2573.
8741 o Code simplifications and refactoring:
8742 - A major revision to our internal node-selecting and listing logic.
8743 Tor already had at least two major ways to look at the question of
8744 "which Tor servers do we know about": a list of router descriptors,
8745 and a list of entries in the current consensus. With
8746 microdescriptors, we're adding a third. Having so many systems
8747 without an abstraction layer over them was hurting the codebase.
8748 Now, we have a new "node_t" abstraction that presents a consistent
8749 interface to a client's view of a Tor node, and holds (nearly) all
8750 of the mutable state formerly in routerinfo_t and routerstatus_t.
8751 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
8752 no longer link against Libevent: they never used it, but
8753 our library structure used to force them to link it.
8756 - Remove some old code to work around even older versions of Tor that
8757 used forked processes to handle DNS requests. Such versions of Tor
8758 are no longer in use as servers.
8760 o Documentation fixes:
8761 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
8762 - Add missing documentation for the authority-related torrc options
8763 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
8767 Changes in version 0.2.2.25-alpha - 2011-04-29
8768 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
8769 robust, routers no longer overreport their bandwidth, Win7 should crash
8770 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
8771 now prevents hidden service-related activity from being linkable. It
8772 provides more information to Vidalia so you can see if your bridge is
8773 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
8774 StrictNodes configuration options to make them more reliable, more
8775 understandable, and more regularly applied. If you use those options,
8776 please see the revised documentation for them in the manual page.
8779 - Relays were publishing grossly inflated bandwidth values because
8780 they were writing their state files wrong--now they write the
8781 correct value. Also, resume reading bandwidth history from the
8782 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
8783 - Improve hidden service robustness: When we find that we have
8784 extended a hidden service's introduction circuit to a relay not
8785 listed as an introduction point in the HS descriptor we currently
8786 have, retry with an introduction point from the current
8787 descriptor. Previously we would just give up. Fixes bugs 1024 and
8788 1930; bugfix on 0.2.0.10-alpha.
8789 - Clients now stop trying to use an exit node associated with a given
8790 destination by TrackHostExits if they fail to reach that exit node.
8791 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
8792 - Fix crash bug on platforms where gmtime and localtime can return
8793 NULL. Windows 7 users were running into this one. Fixes part of bug
8794 2077. Bugfix on all versions of Tor. Found by boboper.
8796 o Security and stability fixes:
8797 - Don't double-free a parsable, but invalid, microdescriptor, even if
8798 it is followed in the blob we're parsing by an unparsable
8799 microdescriptor. Fixes an issue reported in a comment on bug 2954.
8800 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
8801 - If the Nickname configuration option isn't given, Tor would pick a
8802 nickname based on the local hostname as the nickname for a relay.
8803 Because nicknames are not very important in today's Tor and the
8804 "Unnamed" nickname has been implemented, this is now problematic
8805 behavior: It leaks information about the hostname without being
8806 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
8807 introduced the Unnamed nickname. Reported by tagnaq.
8808 - Fix an uncommon assertion failure when running with DNSPort under
8809 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8810 - Avoid linkability based on cached hidden service descriptors: forget
8811 all hidden service descriptors cached as a client when processing a
8812 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8815 - Export GeoIP information on bridge usage to controllers even if we
8816 have not yet been running for 24 hours. Now Vidalia bridge operators
8817 can get more accurate and immediate feedback about their
8818 contributions to the network.
8820 o Major features and bugfixes (node selection):
8821 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
8822 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
8823 options. Previously, we had been ambiguous in describing what
8824 counted as an "exit" node, and what operations exactly "StrictNodes
8825 0" would permit. This created confusion when people saw nodes built
8826 through unexpected circuits, and made it hard to tell real bugs from
8827 surprises. Now the intended behavior is:
8828 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
8829 a node that delivers user traffic outside the Tor network.
8830 . "Entry", in the context of EntryNodes, means a node used as the
8831 first hop of a multihop circuit. It doesn't include direct
8832 connections to directory servers.
8833 . "ExcludeNodes" applies to all nodes.
8834 . "StrictNodes" changes the behavior of ExcludeNodes only. When
8835 StrictNodes is set, Tor should avoid all nodes listed in
8836 ExcludeNodes, even when it will make user requests fail. When
8837 StrictNodes is *not* set, then Tor should follow ExcludeNodes
8838 whenever it can, except when it must use an excluded node to
8839 perform self-tests, connect to a hidden service, provide a
8840 hidden service, fulfill a .exit request, upload directory
8841 information, or fetch directory information.
8842 Collectively, the changes to implement the behavior fix bug 1090.
8843 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
8844 a node is listed in both, it's treated as excluded.
8845 - ExcludeNodes now applies to directory nodes -- as a preference if
8846 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
8847 Don't exclude all the directory authorities and set StrictNodes to 1
8848 unless you really want your Tor to break.
8849 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
8850 - ExcludeExitNodes now overrides .exit requests.
8851 - We don't use bridges listed in ExcludeNodes.
8852 - When StrictNodes is 1:
8853 . We now apply ExcludeNodes to hidden service introduction points
8854 and to rendezvous points selected by hidden service users. This
8855 can make your hidden service less reliable: use it with caution!
8856 . If we have used ExcludeNodes on ourself, do not try relay
8857 reachability self-tests.
8858 . If we have excluded all the directory authorities, we will not
8859 even try to upload our descriptor if we're a relay.
8860 . Do not honor .exit requests to an excluded node.
8861 - Remove a misfeature that caused us to ignore the Fast/Stable flags
8862 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
8863 - When the set of permitted nodes changes, we now remove any mappings
8864 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
8866 - We never cannibalize a circuit that had excluded nodes on it, even
8867 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
8868 - Revert a change where we would be laxer about attaching streams to
8869 circuits than when building the circuits. This was meant to prevent
8870 a set of bugs where streams were never attachable, but our improved
8871 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
8872 - Keep track of how many times we launch a new circuit to handle a
8873 given stream. Too many launches could indicate an inconsistency
8874 between our "launch a circuit to handle this stream" logic and our
8875 "attach this stream to one of the available circuits" logic.
8876 - Improve log messages related to excluded nodes.
8879 - Fix a spurious warning when moving from a short month to a long
8880 month on relays with month-based BandwidthAccounting. Bugfix on
8881 0.2.2.17-alpha; fixes bug 3020.
8882 - When a client finds that an origin circuit has run out of 16-bit
8883 stream IDs, we now mark it as unusable for new streams. Previously,
8884 we would try to close the entire circuit. Bugfix on 0.0.6.
8885 - Add a forgotten cast that caused a compile warning on OS X 10.6.
8886 Bugfix on 0.2.2.24-alpha.
8887 - Be more careful about reporting the correct error from a failed
8888 connect() system call. Under some circumstances, it was possible to
8889 look at an incorrect value for errno when sending the end reason.
8890 Bugfix on 0.1.0.1-rc.
8891 - Correctly handle an "impossible" overflow cases in connection byte
8892 counting, where we write or read more than 4GB on an edge connection
8893 in a single second. Bugfix on 0.1.2.8-beta.
8894 - Correct the warning displayed when a rendezvous descriptor exceeds
8895 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8897 - Clients and hidden services now use HSDir-flagged relays for hidden
8898 service descriptor downloads and uploads even if the relays have no
8899 DirPort set and the client has disabled TunnelDirConns. This will
8900 eventually allow us to give the HSDir flag to relays with no
8901 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
8902 - Downgrade "no current certificates known for authority" message from
8903 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
8904 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
8905 2917. Bugfix on 0.1.1.1-alpha.
8906 - Only limit the lengths of single HS descriptors, even when multiple
8907 HS descriptors are published to an HSDir relay in a single POST
8908 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8909 - Write the current time into the LastWritten line in our state file,
8910 rather than the time from the previous write attempt. Also, stop
8911 trying to use a time of -1 in our log statements. Fixes bug 3039;
8912 bugfix on 0.2.2.14-alpha.
8913 - Be more consistent in our treatment of file system paths. "~" should
8914 get expanded to the user's home directory in the Log config option.
8915 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8916 feature for the -f and --DataDirectory options.
8919 - Make sure every relay writes a state file at least every 12 hours.
8920 Previously, a relay could go for weeks without writing its state
8921 file, and on a crash could lose its bandwidth history, capacity
8922 estimates, client country statistics, and so on. Addresses bug 3012.
8923 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8924 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8925 clients are already deprecated because of security bugs.
8926 - Don't allow v0 hidden service authorities to act as clients.
8927 Required by fix for bug 3000.
8928 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8929 by fix for bug 3000.
8930 - Ensure that no empty [dirreq-](read|write)-history lines are added
8931 to an extrainfo document. Implements ticket 2497.
8933 o Code simplification and refactoring:
8934 - Remove workaround code to handle directory responses from servers
8935 that had bug 539 (they would send HTTP status 503 responses _and_
8936 send a body too). Since only server versions before
8937 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
8938 keep the workaround in place.
8939 - Remove the old 'fuzzy time' logic. It was supposed to be used for
8940 handling calculations where we have a known amount of clock skew and
8941 an allowed amount of unknown skew. But we only used it in three
8942 places, and we never adjusted the known/unknown skew values. This is
8943 still something we might want to do someday, but if we do, we'll
8944 want to do it differently.
8945 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8946 None of the cases where we did this before were wrong, but by making
8947 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8948 - Use GetTempDir to find the proper temporary directory location on
8949 Windows when generating temporary files for the unit tests. Patch by
8953 Changes in version 0.2.2.24-alpha - 2011-04-08
8954 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
8955 prevented Tor clients from effectively using "multihomed" bridges,
8956 that is, bridges that listen on multiple ports or IP addresses so users
8957 can continue to use some of their addresses even if others get blocked.
8960 - Fix a bug where bridge users who configure the non-canonical
8961 address of a bridge automatically switch to its canonical
8962 address. If a bridge listens at more than one address, it should be
8963 able to advertise those addresses independently and any non-blocked
8964 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
8966 - If you configured Tor to use bridge A, and then quit and
8967 configured Tor to use bridge B instead, it would happily continue
8968 to use bridge A if it's still reachable. While this behavior is
8969 a feature if your goal is connectivity, in some scenarios it's a
8970 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8971 - Directory authorities now use data collected from their own
8972 uptime observations when choosing whether to assign the HSDir flag
8973 to relays, instead of trusting the uptime value the relay reports in
8974 its descriptor. This change helps prevent an attack where a small
8975 set of nodes with frequently-changing identity keys can blackhole
8976 a hidden service. (Only authorities need upgrade; others will be
8977 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8980 - When we restart our relay, we might get a successful connection
8981 from the outside before we've started our reachability tests,
8982 triggering a warning: "ORPort found reachable, but I have no
8983 routerinfo yet. Failing to inform controller of success." This
8984 bug was harmless unless Tor is running under a controller
8985 like Vidalia, in which case the controller would never get a
8986 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8988 - Make directory authorities more accurate at recording when
8989 relays that have failed several reachability tests became
8990 unreachable, so we can provide more accuracy at assigning Stable,
8991 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8992 - Fix an issue that prevented static linking of libevent on
8993 some platforms (notably Linux). Fixes bug 2698; bugfix on
8994 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
8995 the --with-static-libevent configure option).
8996 - We now ask the other side of a stream (the client or the exit)
8997 for more data on that stream when the amount of queued data on
8998 that stream dips low enough. Previously, we wouldn't ask the
8999 other side for more data until either it sent us more data (which
9000 it wasn't supposed to do if it had exhausted its window!) or we
9001 had completely flushed all our queued data. This flow control fix
9002 should improve throughput. Fixes bug 2756; bugfix on the earliest
9003 released versions of Tor (svn commit r152).
9004 - Avoid a double-mark-for-free warning when failing to attach a
9005 transparent proxy connection. (We thought we had fixed this in
9006 0.2.2.23-alpha, but it turns out our fix was checking the wrong
9007 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
9008 bug) and 0.2.2.23-alpha (the incorrect fix).
9009 - When warning about missing zlib development packages during compile,
9010 give the correct package names. Bugfix on 0.2.0.1-alpha.
9013 - Directory authorities now log the source of a rejected POSTed v3
9015 - Make compilation with clang possible when using
9016 --enable-gcc-warnings by removing two warning options that clang
9017 hasn't implemented yet and by fixing a few warnings. Implements
9019 - When expiring circuits, use microsecond timers rather than
9020 one-second timers. This can avoid an unpleasant situation where a
9021 circuit is launched near the end of one second and expired right
9022 near the beginning of the next, and prevent fluctuations in circuit
9024 - Use computed circuit-build timeouts to decide when to launch
9025 parallel introduction circuits for hidden services. (Previously,
9026 we would retry after 15 seconds.)
9027 - Update to the April 1 2011 Maxmind GeoLite Country database.
9030 - Create the /var/run/tor directory on startup on OpenSUSE if it is
9031 not already created. Patch from Andreas Stieger. Fixes bug 2573.
9033 o Documentation changes:
9034 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9035 - Resolve all doxygen warnings except those for missing documentation.
9037 - Add doxygen documentation for more functions, fields, and types.
9040 Changes in version 0.2.2.23-alpha - 2011-03-08
9041 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
9042 they restart they don't lose their bandwidth capacity estimate. This
9043 release also fixes a diverse set of user-facing bugs, ranging from
9044 relays overrunning their rate limiting to clients falsely warning about
9045 clock skew to bridge descriptor leaks by our bridge directory authority.
9048 - Stop sending a CLOCK_SKEW controller status event whenever
9049 we fetch directory information from a relay that has a wrong clock.
9050 Instead, only inform the controller when it's a trusted authority
9051 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9052 the rest of bug 1074.
9053 - Fix an assert in parsing router descriptors containing IPv6
9054 addresses. This one took down the directory authorities when
9055 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9056 - Make the bridge directory authority refuse to answer directory
9057 requests for "all" descriptors. It used to include bridge
9058 descriptors in its answer, which was a major information leak.
9059 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9060 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9061 Tor would ignore their RelayBandwidthBurst setting,
9062 potentially using more bandwidth than expected. Bugfix on
9063 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9064 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9065 hidserv" in her torrc. The 'hidserv' argument never controlled
9066 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9069 - Relays now save observed peak bandwidth throughput rates to their
9070 state file (along with total usage, which was already saved)
9071 so that they can determine their correct estimated bandwidth on
9072 restart. Resolves bug 1863, where Tor relays would reset their
9073 estimated bandwidth to 0 after restarting.
9074 - Directory authorities now take changes in router IP address and
9075 ORPort into account when determining router stability. Previously,
9076 if a router changed its IP or ORPort, the authorities would not
9077 treat it as having any downtime for the purposes of stability
9078 calculation, whereas clients would experience downtime since the
9079 change could take a while to propagate to them. Resolves issue 1035.
9080 - Enable Address Space Layout Randomization (ASLR) and Data Execution
9081 Prevention (DEP) by default on Windows to make it harder for
9082 attackers to exploit vulnerabilities. Patch from John Brooks.
9084 o Minor bugfixes (on 0.2.1.x and earlier):
9085 - Fix a rare crash bug that could occur when a client was configured
9086 with a large number of bridges. Fixes bug 2629; bugfix on
9087 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9088 - Avoid a double mark-for-free warning when failing to attach a
9089 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9091 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9092 found by "cypherpunks". This bug was introduced before the first
9093 Tor release, in svn commit r110.
9094 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
9095 don't mention them in the manpage. Fixes bug 2450; issue
9096 spotted by keb and G-Lo.
9097 - Fix a bug in bandwidth history state parsing that could have been
9098 triggered if a future version of Tor ever changed the timing
9099 granularity at which bandwidth history is measured. Bugfix on
9101 - When a relay decides that its DNS is too broken for it to serve
9102 as an exit server, it advertised itself as a non-exit, but
9103 continued to act as an exit. This could create accidental
9104 partitioning opportunities for users. Instead, if a relay is
9105 going to advertise reject *:* as its exit policy, it should
9106 really act with exit policy "reject *:*". Fixes bug 2366.
9107 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
9108 - In the special case where you configure a public exit relay as your
9109 bridge, Tor would be willing to use that exit relay as the last
9110 hop in your circuit as well. Now we fail that circuit instead.
9111 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
9112 - Fix a bug with our locking implementation on Windows that couldn't
9113 correctly detect when a file was already locked. Fixes bug 2504,
9114 bugfix on 0.2.1.6-alpha.
9115 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9116 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9118 - Set target port in get_interface_address6() correctly. Bugfix
9119 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9120 - Directory authorities are now more robust to hops back in time
9121 when calculating router stability. Previously, if a run of uptime
9122 or downtime appeared to be negative, the calculation could give
9123 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
9125 - Fix an assert that got triggered when using the TestingTorNetwork
9126 configuration option and then issuing a GETINFO config-text control
9127 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
9129 o Minor bugfixes (on 0.2.2.x):
9130 - Clients should not weight BadExit nodes as Exits in their node
9131 selection. Similarly, directory authorities should not count BadExit
9132 bandwidth as Exit bandwidth when computing bandwidth-weights.
9133 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
9134 - Correctly clear our dir_read/dir_write history when there is an
9135 error parsing any bw history value from the state file. Bugfix on
9137 - Resolve a bug in verifying signatures of directory objects
9138 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
9139 Fixes bug 2409. Found by "piebeer".
9140 - Bridge authorities no longer crash on SIGHUP when they try to
9141 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
9145 - Log less aggressively about circuit timeout changes, and improve
9146 some other circuit timeout messages. Resolves bug 2004.
9147 - Log a little more clearly about the times at which we're no longer
9148 accepting new connections. Resolves bug 2181.
9149 - Reject attempts at the client side to open connections to private
9150 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
9151 a randomly chosen exit node. Attempts to do so are always
9152 ill-defined, generally prevented by exit policies, and usually
9153 in error. This will also help to detect loops in transparent
9154 proxy configurations. You can disable this feature by setting
9155 "ClientRejectInternalAddresses 0" in your torrc.
9156 - Always treat failure to allocate an RSA key as an unrecoverable
9158 - Update to the March 1 2011 Maxmind GeoLite Country database.
9160 o Minor features (log subsystem):
9161 - Add documentation for configuring logging at different severities in
9162 different log domains. We've had this feature since 0.2.1.1-alpha,
9163 but for some reason it never made it into the manpage. Fixes
9165 - Make it simpler to specify "All log domains except for A and B".
9166 Previously you needed to say "[*,~A,~B]". Now you can just say
9168 - Add a "LogMessageDomains 1" option to include the domains of log
9169 messages along with the messages. Without this, there's no way
9170 to use log domains without reading the source or doing a lot
9173 o Packaging changes:
9174 - Stop shipping the Tor specs files and development proposal documents
9175 in the tarball. They are now in a separate git repository at
9176 git://git.torproject.org/torspec.git
9179 Changes in version 0.2.1.30 - 2011-02-23
9180 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9181 change is a slight tweak to Tor's TLS handshake that makes relays
9182 and bridges that run this new version reachable from Iran again.
9183 We don't expect this tweak will win the arms race long-term, but it
9184 buys us time until we roll out a better solution.
9187 - Stop sending a CLOCK_SKEW controller status event whenever
9188 we fetch directory information from a relay that has a wrong clock.
9189 Instead, only inform the controller when it's a trusted authority
9190 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9191 the rest of bug 1074.
9192 - Fix a bounds-checking error that could allow an attacker to
9193 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9195 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9196 Tor would ignore their RelayBandwidthBurst setting,
9197 potentially using more bandwidth than expected. Bugfix on
9198 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9199 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9200 hidserv" in her torrc. The 'hidserv' argument never controlled
9201 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9204 - Adjust our TLS Diffie-Hellman parameters to match those used by
9206 - Update to the February 1 2011 Maxmind GeoLite Country database.
9209 - Check for and reject overly long directory certificates and
9210 directory tokens before they have a chance to hit any assertions.
9211 Bugfix on 0.2.1.28. Found by "doorss".
9212 - Bring the logic that gathers routerinfos and assesses the
9213 acceptability of circuits into line. This prevents a Tor OP from
9214 getting locked in a cycle of choosing its local OR as an exit for a
9215 path (due to a .exit request) and then rejecting the circuit because
9216 its OR is not listed yet. It also prevents Tor clients from using an
9217 OR running in the same instance as an exit (due to a .exit request)
9218 if the OR does not meet the same requirements expected of an OR
9219 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9221 o Packaging changes:
9222 - Stop shipping the Tor specs files and development proposal documents
9223 in the tarball. They are now in a separate git repository at
9224 git://git.torproject.org/torspec.git
9225 - Do not include Git version tags as though they are SVN tags when
9226 generating a tarball from inside a repository that has switched
9227 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9230 Changes in version 0.2.2.22-alpha - 2011-01-25
9231 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
9232 main other change is a slight tweak to Tor's TLS handshake that makes
9233 relays and bridges that run this new version reachable from Iran again.
9234 We don't expect this tweak will win the arms race long-term, but it
9235 will buy us a bit more time until we roll out a better solution.
9238 - Fix a bounds-checking error that could allow an attacker to
9239 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9241 - Don't assert when changing from bridge to relay or vice versa
9242 via the controller. The assert happened because we didn't properly
9243 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
9244 bug 2433. Reported by bastik.
9247 - Adjust our TLS Diffie-Hellman parameters to match those used by
9249 - Provide a log message stating which geoip file we're parsing
9250 instead of just stating that we're parsing the geoip file.
9251 Implements ticket 2432.
9254 - Check for and reject overly long directory certificates and
9255 directory tokens before they have a chance to hit any assertions.
9256 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
9259 Changes in version 0.2.2.21-alpha - 2011-01-15
9260 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
9261 continues our recent code security audit work. The main fix resolves
9262 a remote heap overflow vulnerability that can allow remote code
9263 execution (CVE-2011-0427). Other fixes address a variety of assert
9264 and crash bugs, most of which we think are hard to exploit remotely.
9266 o Major bugfixes (security), also included in 0.2.1.29:
9267 - Fix a heap overflow bug where an adversary could cause heap
9268 corruption. This bug probably allows remote code execution
9269 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9271 - Prevent a denial-of-service attack by disallowing any
9272 zlib-compressed data whose compression factor is implausibly
9273 high. Fixes part of bug 2324; reported by "doorss".
9274 - Zero out a few more keys in memory before freeing them. Fixes
9275 bug 2384 and part of bug 2385. These key instances found by
9276 "cypherpunks", based on Andrew Case's report about being able
9277 to find sensitive data in Tor's memory space if you have enough
9278 permissions. Bugfix on 0.0.2pre9.
9280 o Major bugfixes (crashes), also included in 0.2.1.29:
9281 - Prevent calls to Libevent from inside Libevent log handlers.
9282 This had potential to cause a nasty set of crashes, especially
9283 if running Libevent with debug logging enabled, and running
9284 Tor with a controller watching for low-severity log messages.
9285 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9286 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9287 underflow errors there too. Fixes the other part of bug 2324.
9288 - Fix a bug where we would assert if we ever had a
9289 cached-descriptors.new file (or another file read directly into
9290 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9291 on 0.2.1.25. Found by doorss.
9292 - Fix some potential asserts and parsing issues with grossly
9293 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9296 o Minor bugfixes (other), also included in 0.2.1.29:
9297 - Fix a bug with handling misformed replies to reverse DNS lookup
9298 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9299 bug reported by doorss.
9300 - Fix compilation on mingw when a pthreads compatibility library
9301 has been installed. (We don't want to use it, so we shouldn't
9302 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9303 - Fix a bug where we would declare that we had run out of virtual
9304 addresses when the address space was only half-exhausted. Bugfix
9306 - Correctly handle the case where AutomapHostsOnResolve is set but
9307 no virtual addresses are available. Fixes bug 2328; bugfix on
9308 0.1.2.1-alpha. Bug found by doorss.
9309 - Correctly handle wrapping around when we run out of virtual
9310 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
9312 o Minor features, also included in 0.2.1.29:
9313 - Update to the January 1 2011 Maxmind GeoLite Country database.
9314 - Introduce output size checks on all of our decryption functions.
9316 o Build changes, also included in 0.2.1.29:
9317 - Tor does not build packages correctly with Automake 1.6 and earlier;
9318 added a check to Makefile.am to make sure that we're building with
9319 Automake 1.7 or later.
9320 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9321 because we built it with a too-old version of automake. Thus that
9322 release broke ./configure --enable-openbsd-malloc, which is popular
9323 among really fast exit relays on Linux.
9325 o Major bugfixes, new in 0.2.2.21-alpha:
9326 - Prevent crash/heap corruption when the cbtnummodes consensus
9327 parameter is set to 0 or large values. Fixes bug 2317; bugfix
9330 o Major features, new in 0.2.2.21-alpha:
9331 - Introduce minimum/maximum values that clients will believe
9332 from the consensus. Now we'll have a better chance to avoid crashes
9333 or worse when a consensus param has a weird value.
9335 o Minor features, new in 0.2.2.21-alpha:
9336 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
9337 used on bridges, and it makes bridge scanning somewhat easier.
9338 - If writing the state file to disk fails, wait up to an hour before
9339 retrying again, rather than trying again each second. Fixes bug
9340 2346; bugfix on Tor 0.1.1.3-alpha.
9341 - Make Libevent log messages get delivered to controllers later,
9342 and not from inside the Libevent log handler. This prevents unsafe
9343 reentrant Libevent calls while still letting the log messages
9345 - Detect platforms that brokenly use a signed size_t, and refuse to
9346 build there. Found and analyzed by doorss and rransom.
9347 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
9350 o Minor bugfixes, new in 0.2.2.21-alpha:
9351 - Handle SOCKS messages longer than 128 bytes long correctly, rather
9352 than waiting forever for them to finish. Fixes bug 2330; bugfix
9353 on 0.2.0.16-alpha. Found by doorss.
9354 - Add assertions to check for overflow in arguments to
9355 base32_encode() and base32_decode(); fix a signed-unsigned
9356 comparison there too. These bugs are not actually reachable in Tor,
9357 but it's good to prevent future errors too. Found by doorss.
9358 - Correctly detect failures to create DNS requests when using Libevent
9359 versions before v2. (Before Libevent 2, we used our own evdns
9360 implementation. Its return values for Libevent's evdns_resolve_*()
9361 functions are not consistent with those from Libevent.) Fixes bug
9362 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
9364 o Documentation, new in 0.2.2.21-alpha:
9365 - Document the default socks host and port (127.0.0.1:9050) for
9369 Changes in version 0.2.1.29 - 2011-01-15
9370 Tor 0.2.1.29 continues our recent code security audit work. The main
9371 fix resolves a remote heap overflow vulnerability that can allow remote
9372 code execution. Other fixes address a variety of assert and crash bugs,
9373 most of which we think are hard to exploit remotely.
9375 o Major bugfixes (security):
9376 - Fix a heap overflow bug where an adversary could cause heap
9377 corruption. This bug probably allows remote code execution
9378 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9380 - Prevent a denial-of-service attack by disallowing any
9381 zlib-compressed data whose compression factor is implausibly
9382 high. Fixes part of bug 2324; reported by "doorss".
9383 - Zero out a few more keys in memory before freeing them. Fixes
9384 bug 2384 and part of bug 2385. These key instances found by
9385 "cypherpunks", based on Andrew Case's report about being able
9386 to find sensitive data in Tor's memory space if you have enough
9387 permissions. Bugfix on 0.0.2pre9.
9389 o Major bugfixes (crashes):
9390 - Prevent calls to Libevent from inside Libevent log handlers.
9391 This had potential to cause a nasty set of crashes, especially
9392 if running Libevent with debug logging enabled, and running
9393 Tor with a controller watching for low-severity log messages.
9394 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9395 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9396 underflow errors there too. Fixes the other part of bug 2324.
9397 - Fix a bug where we would assert if we ever had a
9398 cached-descriptors.new file (or another file read directly into
9399 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9400 on 0.2.1.25. Found by doorss.
9401 - Fix some potential asserts and parsing issues with grossly
9402 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9405 o Minor bugfixes (other):
9406 - Fix a bug with handling misformed replies to reverse DNS lookup
9407 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9408 bug reported by doorss.
9409 - Fix compilation on mingw when a pthreads compatibility library
9410 has been installed. (We don't want to use it, so we shouldn't
9411 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9412 - Fix a bug where we would declare that we had run out of virtual
9413 addresses when the address space was only half-exhausted. Bugfix
9415 - Correctly handle the case where AutomapHostsOnResolve is set but
9416 no virtual addresses are available. Fixes bug 2328; bugfix on
9417 0.1.2.1-alpha. Bug found by doorss.
9418 - Correctly handle wrapping around to when we run out of virtual
9419 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
9420 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9421 because we built it with a too-old version of automake. Thus that
9422 release broke ./configure --enable-openbsd-malloc, which is popular
9423 among really fast exit relays on Linux.
9426 - Update to the January 1 2011 Maxmind GeoLite Country database.
9427 - Introduce output size checks on all of our decryption functions.
9430 - Tor does not build packages correctly with Automake 1.6 and earlier;
9431 added a check to Makefile.am to make sure that we're building with
9432 Automake 1.7 or later.
9435 Changes in version 0.2.2.20-alpha - 2010-12-17
9436 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
9437 exploitable bugs. We also fix a variety of other significant bugs,
9438 change the IP address for one of our directory authorities, and update
9439 the minimum version that Tor relays must run to join the network.
9442 - Fix a remotely exploitable bug that could be used to crash instances
9443 of Tor remotely by overflowing on the heap. Remote-code execution
9444 hasn't been confirmed, but can't be ruled out. Everyone should
9445 upgrade. Bugfix on the 0.1.1 series and later.
9446 - Fix a bug that could break accounting on 64-bit systems with large
9447 time_t values, making them hibernate for impossibly long intervals.
9448 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
9449 - Fix a logic error in directory_fetches_from_authorities() that
9450 would cause all _non_-exits refusing single-hop-like circuits
9451 to fetch from authorities, when we wanted to have _exits_ fetch
9452 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
9454 - Fix a stream fairness bug that would cause newer streams on a given
9455 circuit to get preference when reading bytes from the origin or
9456 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
9457 introduced before the first Tor release, in svn revision r152.
9459 o Directory authority changes:
9460 - Change IP address and ports for gabelmoo (v3 directory authority).
9463 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
9464 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
9465 - Fix an off-by-one error in calculating some controller command
9466 argument lengths. Fortunately, this mistake is harmless since
9467 the controller code does redundant NUL termination too. Found by
9468 boboper. Bugfix on 0.1.1.1-alpha.
9469 - Do not dereference NULL if a bridge fails to build its
9470 extra-info descriptor. Found by an anonymous commenter on
9471 Trac. Bugfix on 0.2.2.19-alpha.
9474 - Update to the December 1 2010 Maxmind GeoLite Country database.
9475 - Directory authorities now reject relays running any versions of
9476 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
9477 known bugs that keep RELAY_EARLY cells from working on rendezvous
9478 circuits. Followup to fix for bug 2081.
9479 - Directory authorities now reject relays running any version of Tor
9480 older than 0.2.0.26-rc. That version is the earliest that fetches
9481 current directory information correctly. Fixes bug 2156.
9482 - Report only the top 10 ports in exit-port stats in order not to
9483 exceed the maximum extra-info descriptor length of 50 KB. Implements
9487 Changes in version 0.2.1.28 - 2010-12-17
9488 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9489 exploitable bugs. We also took this opportunity to change the IP address
9490 for one of our directory authorities, and to update the geoip database
9494 - Fix a remotely exploitable bug that could be used to crash instances
9495 of Tor remotely by overflowing on the heap. Remote-code execution
9496 hasn't been confirmed, but can't be ruled out. Everyone should
9497 upgrade. Bugfix on the 0.1.1 series and later.
9499 o Directory authority changes:
9500 - Change IP address and ports for gabelmoo (v3 directory authority).
9503 - Update to the December 1 2010 Maxmind GeoLite Country database.
9506 Changes in version 0.2.1.27 - 2010-11-23
9507 Yet another OpenSSL security patch broke its compatibility with Tor:
9508 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9509 also took this opportunity to fix several crash bugs, integrate a new
9510 directory authority, and update the bundled GeoIP database.
9513 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9514 No longer set the tlsext_host_name extension on server SSL objects;
9515 but continue to set it on client SSL objects. Our goal in setting
9516 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9517 bugfix on 0.2.1.1-alpha.
9518 - Do not log messages to the controller while shrinking buffer
9519 freelists. Doing so would sometimes make the controller connection
9520 try to allocate a buffer chunk, which would mess up the internals
9521 of the freelist and cause an assertion failure. Fixes bug 1125;
9522 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9523 - Learn our external IP address when we're a relay or bridge, even if
9524 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9525 where we introduced bridge relays that don't need to publish to
9526 be useful. Fixes bug 2050.
9527 - Do even more to reject (and not just ignore) annotations on
9528 router descriptors received anywhere but from the cache. Previously
9529 we would ignore such annotations at first, but cache them to disk
9530 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9531 - When you're using bridges and your network goes away and your
9532 bridges get marked as down, recover when you attempt a new socks
9533 connection (if the network is back), rather than waiting up to an
9534 hour to try fetching new descriptors for your bridges. Bugfix on
9535 0.2.0.3-alpha; fixes bug 1981.
9538 - Move to the November 2010 Maxmind GeoLite country db (rather
9539 than the June 2009 ip-to-country GeoIP db) for our statistics that
9540 count how many users relays are seeing from each country. Now we'll
9541 have more accurate data, especially for many African countries.
9543 o New directory authorities:
9544 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9548 - Fix an assertion failure that could occur in directory caches or
9549 bridge users when using a very short voting interval on a testing
9550 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9552 - Enforce multiplicity rules when parsing annotations. Bugfix on
9553 0.2.0.8-alpha. Found by piebeer.
9554 - Allow handshaking OR connections to take a full KeepalivePeriod
9555 seconds to handshake. Previously, we would close them after
9556 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9557 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9559 - When building with --enable-gcc-warnings on OpenBSD, disable
9560 warnings in system headers. This makes --enable-gcc-warnings
9561 pass on OpenBSD 4.8.
9564 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9565 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9566 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9567 Servers can start sending this code when enough clients recognize
9568 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9569 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9570 Patch from mingw-san.
9573 - Remove the old debian/ directory from the main Tor distribution.
9574 The official Tor-for-debian git repository lives at the URL
9575 https://git.torproject.org/debian/tor.git
9576 - Stop shipping the old doc/website/ directory in the tarball. We
9577 changed the website format in late 2010, and what we shipped in
9578 0.2.1.26 really wasn't that useful anyway.
9581 Changes in version 0.2.2.19-alpha - 2010-11-22
9582 Yet another OpenSSL security patch broke its compatibility with Tor:
9583 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
9586 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9587 No longer set the tlsext_host_name extension on server SSL objects;
9588 but continue to set it on client SSL objects. Our goal in setting
9589 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9590 bugfix on 0.2.1.1-alpha.
9593 - Try harder not to exceed the maximum length of 50 KB when writing
9594 statistics to extra-info descriptors. This bug was triggered by very
9595 fast relays reporting exit-port, entry, and dirreq statistics.
9596 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
9597 - Publish a router descriptor even if generating an extra-info
9598 descriptor fails. Previously we would not publish a router
9599 descriptor without an extra-info descriptor; this can cause fast
9600 exit relays collecting exit-port statistics to drop from the
9601 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
9604 Changes in version 0.2.2.18-alpha - 2010-11-16
9605 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
9606 us lately, makes unpublished bridge relays able to detect their IP
9607 address, and fixes a wide variety of other bugs to get us much closer
9608 to a stable release.
9611 - Do even more to reject (and not just ignore) annotations on
9612 router descriptors received anywhere but from the cache. Previously
9613 we would ignore such annotations at first, but cache them to disk
9614 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9615 - Do not log messages to the controller while shrinking buffer
9616 freelists. Doing so would sometimes make the controller connection
9617 try to allocate a buffer chunk, which would mess up the internals
9618 of the freelist and cause an assertion failure. Fixes bug 1125;
9619 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9620 - Learn our external IP address when we're a relay or bridge, even if
9621 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9622 where we introduced bridge relays that don't need to publish to
9623 be useful. Fixes bug 2050.
9624 - Maintain separate TLS contexts and certificates for incoming and
9625 outgoing connections in bridge relays. Previously we would use the
9626 same TLS contexts and certs for incoming and outgoing connections.
9627 Bugfix on 0.2.0.3-alpha; addresses bug 988.
9628 - Maintain separate identity keys for incoming and outgoing TLS
9629 contexts in bridge relays. Previously we would use the same
9630 identity keys for incoming and outgoing TLS contexts. Bugfix on
9631 0.2.0.3-alpha; addresses the other half of bug 988.
9632 - Avoid an assertion failure when we as an authority receive a
9633 duplicate upload of a router descriptor that we already have,
9634 but which we previously considered an obsolete descriptor.
9635 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
9636 - Avoid a crash bug triggered by looking at a dangling pointer while
9637 setting the network status consensus. Found by Robert Ransom.
9638 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
9639 - Fix a logic error where servers that _didn't_ act as exits would
9640 try to keep their server lists more aggressively up to date than
9641 exits, when it was supposed to be the other way around. Bugfix
9644 o Minor bugfixes (on Tor 0.2.1.x and earlier):
9645 - When we're trying to guess whether we know our IP address as
9646 a relay, we would log various ways that we failed to guess
9647 our address, but never log that we ended up guessing it
9648 successfully. Now add a log line to help confused and anxious
9649 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
9650 - Bring the logic that gathers routerinfos and assesses the
9651 acceptability of circuits into line. This prevents a Tor OP from
9652 getting locked in a cycle of choosing its local OR as an exit for a
9653 path (due to a .exit request) and then rejecting the circuit because
9654 its OR is not listed yet. It also prevents Tor clients from using an
9655 OR running in the same instance as an exit (due to a .exit request)
9656 if the OR does not meet the same requirements expected of an OR
9657 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9658 - Correctly describe errors that occur when generating a TLS object.
9659 Previously we would attribute them to a failure while generating a
9660 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9662 - Enforce multiplicity rules when parsing annotations. Bugfix on
9663 0.2.0.8-alpha. Found by piebeer.
9664 - Fix warnings that newer versions of autoconf produced during
9665 ./autogen.sh. These warnings appear to be harmless in our case,
9666 but they were extremely verbose. Fixes bug 2020.
9668 o Minor bugfixes (on Tor 0.2.2.x):
9669 - Enable protection of small arrays whenever we build with gcc
9670 hardening features, not only when also building with warnings
9671 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
9674 - Make hidden services work better in private Tor networks by not
9675 requiring any uptime to join the hidden service descriptor
9676 DHT. Implements ticket 2088.
9677 - Rate-limit the "your application is giving Tor only an IP address"
9678 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
9679 - When AllowSingleHopExits is set, print a warning to explain to the
9680 relay operator why most clients are avoiding her relay.
9681 - Update to the November 1 2010 Maxmind GeoLite Country database.
9683 o Code simplifications and refactoring:
9684 - When we fixed bug 1038 we had to put in a restriction not to send
9685 RELAY_EARLY cells on rend circuits. This was necessary as long
9686 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9687 active. Now remove this obsolete check. Resolves bug 2081.
9688 - Some options used different conventions for uppercasing of acronyms
9689 when comparing manpage and source. Fix those in favor of the
9690 manpage, as it makes sense to capitalize acronyms.
9691 - Remove the torrc.complete file. It hasn't been kept up to date
9692 and users will have better luck checking out the manpage.
9693 - Remove the obsolete "NoPublish" option; it has been flagged
9694 as obsolete and has produced a warning since 0.1.1.18-rc.
9695 - Remove everything related to building the expert bundle for OS X.
9696 It has confused many users, doesn't work right on OS X 10.6,
9697 and is hard to get rid of once installed. Resolves bug 1274.
9700 Changes in version 0.2.2.17-alpha - 2010-09-30
9701 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
9702 to use one-hop circuits (which can put the exit relays at higher risk,
9703 plus unbalance the network); fixes a big bug in bandwidth accounting
9704 for relays that want to limit their monthly bandwidth use; fixes a
9705 big pile of bugs in how clients tolerate temporary network failure;
9706 and makes our adaptive circuit build timeout feature (which improves
9707 client performance if your network is fast while not breaking things
9708 if your network is slow) better handle bad networks.
9711 - Exit relays now try harder to block exit attempts from unknown
9712 relays, to make it harder for people to use them as one-hop proxies
9713 a la tortunnel. Controlled by the refuseunknownexits consensus
9714 parameter (currently enabled), or you can override it on your
9715 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
9717 o Major bugfixes (0.2.1.x and earlier):
9718 - Fix a bug in bandwidth accounting that could make us use twice
9719 the intended bandwidth when our interval start changes due to
9720 daylight saving time. Now we tolerate skew in stored vs computed
9721 interval starts: if the start of the period changes by no more than
9722 50% of the period's duration, we remember bytes that we transferred
9723 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
9724 - Always search the Windows system directory for system DLLs, and
9725 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
9726 - When you're using bridges and your network goes away and your
9727 bridges get marked as down, recover when you attempt a new socks
9728 connection (if the network is back), rather than waiting up to an
9729 hour to try fetching new descriptors for your bridges. Bugfix on
9730 0.2.0.3-alpha; fixes bug 1981.
9732 o Major bugfixes (on 0.2.2.x):
9733 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
9735 - Fix a segfault that could happen when operating a bridge relay with
9736 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
9737 - The consensus bandwidth-weights (used by clients to choose fast
9738 relays) entered an unexpected edge case in September where
9739 Exits were much scarcer than Guards, resulting in bad weight
9740 recommendations. Now we compute them using new constraints that
9741 should succeed in all cases. Also alter directory authorities to
9742 not include the bandwidth-weights line if they fail to produce
9743 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
9744 - When weighting bridges during path selection, we used to trust
9745 the bandwidths they provided in their descriptor, only capping them
9746 at 10MB/s. This turned out to be problematic for two reasons:
9747 Bridges could claim to handle a lot more traffic then they
9748 actually would, thus making more clients pick them and have a
9749 pretty effective DoS attack. The other issue is that new bridges
9750 that might not have a good estimate for their bw capacity yet
9751 would not get used at all unless no other bridges are available
9752 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
9754 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
9755 - Ignore cannibalized circuits when recording circuit build times.
9756 This should provide for a minor performance improvement for hidden
9757 service users using 0.2.2.14-alpha, and should remove two spurious
9758 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
9759 - Simplify the logic that causes us to decide if the network is
9760 unavailable for purposes of recording circuit build times. If we
9761 receive no cells whatsoever for the entire duration of a circuit's
9762 full measured lifetime, the network is probably down. Also ignore
9763 one-hop directory fetching circuit timeouts when calculating our
9764 circuit build times. These changes should hopefully reduce the
9765 cases where we see ridiculous circuit build timeouts for people
9766 with spotty wireless connections. Fixes part of bug 1772; bugfix
9768 - Prevent the circuit build timeout from becoming larger than
9769 the maximum build time we have ever seen. Also, prevent the time
9770 period for measurement circuits from becoming larger than twice that
9771 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
9774 - When we run out of directory information such that we can't build
9775 circuits, but then get enough that we can build circuits, log when
9776 we actually construct a circuit, so the user has a better chance of
9777 knowing what's going on. Fixes bug 1362.
9778 - Be more generous with how much bandwidth we'd use up (with
9779 accounting enabled) before entering "soft hibernation". Previously,
9780 we'd refuse new connections and circuits once we'd used up 95% of
9781 our allotment. Now, we use up 95% of our allotment, AND make sure
9782 that we have no more than 500MB (or 3 hours of expected traffic,
9783 whichever is lower) remaining before we enter soft hibernation.
9784 - If we've configured EntryNodes and our network goes away and/or all
9785 our entrynodes get marked down, optimistically retry them all when
9786 a new socks application request appears. Fixes bug 1882.
9787 - Add some more defensive programming for architectures that can't
9788 handle unaligned integer accesses. We don't know of any actual bugs
9789 right now, but that's the best time to fix them. Fixes bug 1943.
9790 - Support line continuations in the torrc config file. If a line
9791 ends with a single backslash character, the newline is ignored, and
9792 the configuration value is treated as continuing on the next line.
9795 o Minor bugfixes (on 0.2.1.x and earlier):
9796 - For bandwidth accounting, calculate our expected bandwidth rate
9797 based on the time during which we were active and not in
9798 soft-hibernation during the last interval. Previously, we were
9799 also considering the time spent in soft-hibernation. If this
9800 was a long time, we would wind up underestimating our bandwidth
9801 by a lot, and skewing our wakeup time towards the start of the
9802 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
9804 o Minor bugfixes (on 0.2.2.x):
9805 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
9806 which were disabled by the circuit build timeout changes in
9807 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
9808 - Make sure we don't warn about missing bandwidth weights when
9809 choosing bridges or other relays not in the consensus. Bugfix on
9810 0.2.2.10-alpha; fixes bug 1805.
9811 - In our logs, do not double-report signatures from unrecognized
9812 authorities both as "from unknown authority" and "not
9813 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
9816 Changes in version 0.2.2.16-alpha - 2010-09-17
9817 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
9818 evident at exit relays), and also continues to resolve all the little
9819 bugs that have been filling up trac lately.
9821 o Major bugfixes (stream-level fairness):
9822 - When receiving a circuit-level SENDME for a blocked circuit, try
9823 to package cells fairly from all the streams that had previously
9824 been blocked on that circuit. Previously, we had started with the
9825 oldest stream, and allowed each stream to potentially exhaust
9826 the circuit's package window. This gave older streams on any
9827 given circuit priority over newer ones. Fixes bug 1937. Detected
9828 originally by Camilo Viecco. This bug was introduced before the
9829 first Tor release, in svn commit r152: it is the new winner of
9830 the longest-lived bug prize.
9831 - When the exit relay got a circuit-level sendme cell, it started
9832 reading on the exit streams, even if had 500 cells queued in the
9833 circuit queue already, so the circuit queue just grew and grew in
9834 some cases. We fix this by not re-enabling reading on receipt of a
9835 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
9836 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
9838 - Newly created streams were allowed to read cells onto circuits,
9839 even if the circuit's cell queue was blocked and waiting to drain.
9840 This created potential unfairness, as older streams would be
9841 blocked, but newer streams would gladly fill the queue completely.
9842 We add code to detect this situation and prevent any stream from
9843 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
9847 - Update to the September 1 2010 Maxmind GeoLite Country database.
9848 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
9849 not. This would lead to a cookie that is still not group readable.
9850 Closes bug 1843. Suggested by katmagic.
9851 - When logging a rate-limited warning, we now mention how many messages
9852 got suppressed since the last warning.
9853 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
9854 do individual connection-level rate limiting of clients. The torrc
9855 config options with the same names trump the consensus params, if
9856 both are present. Replaces the old "bwconnrate" and "bwconnburst"
9857 consensus params which were broken from 0.2.2.7-alpha through
9858 0.2.2.14-alpha. Closes bug 1947.
9859 - When a router changes IP address or port, authorities now launch
9860 a new reachability test for it. Implements ticket 1899.
9861 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
9862 2 no signature, 4 required" messages about consensus signatures
9863 easier to read, and make sure they get logged at the same severity
9864 as the messages explaining which keys are which. Fixes bug 1290.
9865 - Don't warn when we have a consensus that we can't verify because
9866 of missing certificates, unless those certificates are ones
9867 that we have been trying and failing to download. Fixes bug 1145.
9868 - If you configure your bridge with a known identity fingerprint,
9869 and the bridge authority is unreachable (as it is in at least
9870 one country now), fall back to directly requesting the descriptor
9871 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
9873 - When building with --enable-gcc-warnings on OpenBSD, disable
9874 warnings in system headers. This makes --enable-gcc-warnings
9875 pass on OpenBSD 4.8.
9877 o Minor bugfixes (on 0.2.1.x and earlier):
9878 - Authorities will now attempt to download consensuses if their
9879 own efforts to make a live consensus have failed. This change
9880 means authorities that restart will fetch a valid consensus, and
9881 it means authorities that didn't agree with the current consensus
9882 will still fetch and serve it if it has enough signatures. Bugfix
9883 on 0.2.0.9-alpha; fixes bug 1300.
9884 - Ensure DNS requests launched by "RESOLVE" commands from the
9885 controller respect the __LeaveStreamsUnattached setconf options. The
9886 same goes for requests launched via DNSPort or transparent
9887 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
9888 - Allow handshaking OR connections to take a full KeepalivePeriod
9889 seconds to handshake. Previously, we would close them after
9890 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9891 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9893 - Rate-limit "Failed to hand off onionskin" warnings.
9894 - Never relay a cell for a circuit we have already destroyed.
9895 Between marking a circuit as closeable and finally closing it,
9896 it may have been possible for a few queued cells to get relayed,
9897 even though they would have been immediately dropped by the next
9898 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
9899 - Never queue a cell for a circuit that's already been marked
9901 - Never vote for a server as "Running" if we have a descriptor for
9902 it claiming to be hibernating, and that descriptor was published
9903 more recently than our last contact with the server. Bugfix on
9904 0.2.0.3-alpha; fixes bug 911.
9905 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9908 o Minor bugfixes (on 0.2.2.x):
9909 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
9910 down if a directory fetch fails and you've configured either
9911 bridges or EntryNodes. The intent was to mark the relay as down
9912 _unless_ you're using bridges or EntryNodes, since if you are
9913 then you could quickly run out of entry points.
9914 - Fix the Windows directory-listing code. A bug introduced in
9915 0.2.2.14-alpha could make Windows directory servers forget to load
9916 some of their cached v2 networkstatus files.
9917 - Really allow clients to use relays as bridges. Fixes bug 1776;
9918 bugfix on 0.2.2.15-alpha.
9919 - Demote a warn to info that happens when the CellStatistics option
9920 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
9921 Reported by Moritz Bartl.
9922 - On Windows, build correctly either with or without Unicode support.
9923 This is necessary so that Tor can support fringe platforms like
9924 Windows 98 (which has no Unicode), or Windows CE (which has no
9925 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
9928 - Add a unit test for cross-platform directory-listing code.
9931 Changes in version 0.2.2.15-alpha - 2010-08-18
9932 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
9933 fixes a variety of other bugs that were preventing performance
9934 experiments from moving forward, fixes several bothersome memory leaks,
9935 and generally closes a lot of smaller bugs that have been filling up
9939 - Stop assigning the HSDir flag to relays that disable their
9940 DirPort (and thus will refuse to answer directory requests). This
9941 fix should dramatically improve the reachability of hidden services:
9942 hidden services and hidden service clients pick six HSDir relays
9943 to store and retrieve the hidden service descriptor, and currently
9944 about half of the HSDir relays will refuse to work. Bugfix on
9945 0.2.0.10-alpha; fixes part of bug 1693.
9946 - The PerConnBWRate and Burst config options, along with the
9947 bwconnrate and bwconnburst consensus params, initialized each conn's
9948 token bucket values only when the connection is established. Now we
9949 update them if the config options change, and update them every time
9950 we get a new consensus. Otherwise we can encounter an ugly edge
9951 case where we initialize an OR conn to client-level bandwidth,
9952 but then later the relay joins the consensus and we leave it
9953 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
9954 - Fix a regression that caused Tor to rebind its ports if it receives
9955 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
9958 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
9959 should give us approximately 40-50% more Guard-flagged nodes,
9960 improving the anonymity the Tor network can provide and also
9961 decreasing the dropoff in throughput that relays experience when
9962 they first get the Guard flag.
9963 - Allow enabling or disabling the *Statistics config options while
9967 - Update to the August 1 2010 Maxmind GeoLite Country database.
9968 - Have the controller interface give a more useful message than
9969 "Internal Error" in response to failed GETINFO requests.
9970 - Warn when the same option is provided more than once in a torrc
9971 file, on the command line, or in a single SETCONF statement, and
9972 the option is one that only accepts a single line. Closes bug 1384.
9973 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9974 Patch from mingw-san.
9975 - Add support for the country code "{??}" in torrc options like
9976 ExcludeNodes, to indicate all routers of unknown country. Closes
9978 - Relays report the number of bytes spent on answering directory
9979 requests in extra-info descriptors similar to {read,write}-history.
9980 Implements enhancement 1790.
9982 o Minor bugfixes (on 0.2.1.x and earlier):
9983 - Complain if PublishServerDescriptor is given multiple arguments that
9984 include 0 or 1. This configuration will be rejected in the future.
9985 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9986 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9987 Bugfix on 0.2.0.13-alpha; closes bug 928.
9988 - Change "Application request when we're believed to be offline."
9989 notice to "Application request when we haven't used client
9990 functionality lately.", to clarify that it's not an error. Bugfix
9991 on 0.0.9.3; fixes bug 1222.
9992 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9993 would return "551 Internal error" rather than "552 Unrecognized key
9994 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9995 - Users can't configure a regular relay to be their bridge. It didn't
9996 work because when Tor fetched the bridge descriptor, it found
9997 that it already had it, and didn't realize that the purpose of the
9998 descriptor had changed. Now we replace routers with a purpose other
9999 than bridge with bridge descriptors when fetching them. Bugfix on
10000 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
10001 refetch the descriptor with router purpose 'general', disabling
10003 - Fix a rare bug in rend_fn unit tests: we would fail a test when
10004 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
10005 on 0.2.0.10-alpha; fixes bug 1808.
10006 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10007 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10008 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10009 Servers can start sending this code when enough clients recognize
10010 it. Also update the spec to reflect this new reason. Bugfix on
10011 0.1.0.1-rc; fixes part of bug 1793.
10012 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
10013 when we switch from being a public relay to a bridge. Otherwise
10014 there will still be clients that see the relay in their consensus,
10015 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
10017 - Instead of giving an assertion failure on an internal mismatch
10018 on estimated freelist size, just log a BUG warning and try later.
10019 Mitigates but does not fix bug 1125.
10020 - Fix an assertion failure that could occur in caches or bridge users
10021 when using a very short voting interval on a testing network.
10022 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
10024 o Minor bugfixes (on 0.2.2.x):
10025 - Alter directory authorities to always consider Exit-flagged nodes
10026 as potential Guard nodes in their votes. The actual decision to
10027 use Exits as Guards is done in the consensus bandwidth weights.
10028 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
10029 - When the controller is reporting the purpose of circuits that
10030 didn't finish building before the circuit build timeout, it was
10031 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
10032 - Our libevent version parsing code couldn't handle versions like
10033 1.4.14b-stable and incorrectly warned the user about using an
10034 old and broken version of libevent. Treat 1.4.14b-stable like
10035 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
10037 - Don't use substitution references like $(VAR:MOD) when
10038 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
10039 '$(:x)' to 'x' rather than the empty string. This bites us in
10040 doc/ when configured with --disable-asciidoc. Bugfix on
10041 0.2.2.9-alpha; fixes bug 1773.
10042 - Remove a spurious hidden service server-side log notice about
10043 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
10045 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
10047 - Correctly report written bytes on linked connections. Found while
10048 implementing 1790. Bugfix on 0.2.2.4-alpha.
10049 - Fix three memory leaks: one in circuit_build_times_parse_state(),
10050 one in dirvote_add_signatures_to_pending_consensus(), and one every
10051 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
10052 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
10054 o Code simplifications and refactoring:
10055 - Take a first step towards making or.h smaller by splitting out
10056 function definitions for all source files in src/or/. Leave
10057 structures and defines in or.h for now.
10058 - Remove a bunch of unused function declarations as well as a block of
10059 #if 0'd code from the unit tests. Closes bug 1824.
10060 - New unit tests for exit-port history statistics; refactored exit
10061 statistics code to be more easily tested.
10062 - Remove the old debian/ directory from the main Tor distribution.
10063 The official Tor-for-debian git repository lives at the URL
10064 https://git.torproject.org/debian/tor.git
10067 Changes in version 0.2.2.14-alpha - 2010-07-12
10068 Tor 0.2.2.14-alpha greatly improves client-side handling of
10069 circuit build timeouts, which are used to estimate speed and improve
10070 performance. We also move to a much better GeoIP database, port Tor to
10071 Windows CE, introduce new compile flags that improve code security,
10072 add an eighth v3 directory authority, and address a lot of more
10076 - Tor directory authorities no longer crash when started with a
10077 cached-microdesc-consensus file in their data directory. Bugfix
10078 on 0.2.2.6-alpha; fixes bug 1532.
10079 - Treat an unset $HOME like an empty $HOME rather than triggering an
10080 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
10081 - Ignore negative and large circuit build timeout values that can
10082 happen during a suspend or hibernate. These values caused various
10083 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
10084 - Alter calculation of Pareto distribution parameter 'Xm' for
10085 Circuit Build Timeout learning to use the weighted average of the
10086 top N=3 modes (because we have three entry guards). Considering
10087 multiple modes should improve the timeout calculation in some cases,
10088 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
10090 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
10091 right censored distribution model. This approach improves over the
10092 synthetic timeout generation approach that was producing insanely
10093 high timeout values. Now we calculate build timeouts using truncated
10094 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
10095 - Do not close circuits that are under construction when they reach
10096 the circuit build timeout. Instead, leave them building (but do not
10097 use them) for up until the time corresponding to the 95th percentile
10098 on the Pareto CDF or 60 seconds, whichever is greater. This is done
10099 to provide better data for the new Pareto model. This percentile
10100 can be controlled by the consensus.
10103 - Move to the June 2010 Maxmind GeoLite country db (rather than the
10104 June 2009 ip-to-country GeoIP db) for our statistics that count
10105 how many users relays are seeing from each country. Now we have
10106 more accurate data for many African countries.
10107 - Port Tor to build and run correctly on Windows CE systems, using
10108 the wcecompat library. Contributed by Valerio Lupi.
10109 - New "--enable-gcc-hardening" ./configure flag (off by default)
10110 to turn on gcc compile time hardening options. It ensures
10111 that signed ints have defined behavior (-fwrapv), enables
10112 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
10113 with canaries (-fstack-protector-all), turns on ASLR protection if
10114 supported by the kernel (-fPIE, -pie), and adds additional security
10115 related warnings. Verified to work on Mac OS X and Debian Lenny.
10116 - New "--enable-linker-hardening" ./configure flag (off by default)
10117 to turn on ELF specific hardening features (relro, now). This does
10118 not work with Mac OS X or any other non-ELF binary format.
10120 o New directory authorities:
10121 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10125 - New config option "WarnUnsafeSocks 0" disables the warning that
10126 occurs whenever Tor receives a socks handshake using a version of
10127 the socks protocol that can only provide an IP address (rather
10128 than a hostname). Setups that do DNS locally over Tor are fine,
10129 and we shouldn't spam the logs in that case.
10130 - Convert the HACKING file to asciidoc, and add a few new sections
10131 to it, explaining how we use Git, how we make changelogs, and
10132 what should go in a patch.
10133 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
10134 event, to give information on the current rate of circuit timeouts
10135 over our stored history.
10136 - Add ability to disable circuit build time learning via consensus
10137 parameter and via a LearnCircuitBuildTimeout config option. Also
10138 automatically disable circuit build time calculation if we are
10139 either a AuthoritativeDirectory, or if we fail to write our state
10140 file. Fixes bug 1296.
10141 - More gracefully handle corrupt state files, removing asserts
10142 in favor of saving a backup and resetting state.
10143 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
10147 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
10149 - When a2x fails, mention that the user could disable manpages instead
10150 of trying to fix their asciidoc installation.
10151 - Where available, use Libevent 2.0's periodic timers so that our
10152 once-per-second cleanup code gets called even more closely to
10153 once per second than it would otherwise. Fixes bug 943.
10154 - If you run a bridge that listens on multiple IP addresses, and
10155 some user configures a bridge address that uses a different IP
10156 address than your bridge writes in its router descriptor, and the
10157 user doesn't specify an identity key, their Tor would discard the
10158 descriptor because "it isn't one of our configured bridges", and
10159 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
10160 Bugfix on 0.2.0.3-alpha.
10161 - If OpenSSL fails to make a duplicate of a private or public key, log
10162 an error message and try to exit cleanly. May help with debugging
10163 if bug 1209 ever remanifests.
10164 - Save a couple bytes in memory allocation every time we escape
10165 certain characters in a string. Patch from Florian Zumbiehl.
10166 - Make it explicit that we don't cannibalize one-hop circuits. This
10167 happens in the wild, but doesn't turn out to be a problem because
10168 we fortunately don't use those circuits. Many thanks to outofwords
10169 for the initial analysis and to swissknife who confirmed that
10170 two-hop circuits are actually created.
10171 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
10172 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
10173 - Eliminate a case where a circuit build time warning was displayed
10174 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
10177 Changes in version 0.2.1.26 - 2010-05-02
10178 Tor 0.2.1.26 addresses the recent connection and memory overload
10179 problems we've been seeing on relays, especially relays with their
10180 DirPort open. If your relay has been crashing, or you turned it off
10181 because it used too many resources, give this release a try.
10183 This release also fixes yet another instance of broken OpenSSL libraries
10184 that was causing some relays to drop out of the consensus.
10187 - Teach relays to defend themselves from connection overload. Relays
10188 now close idle circuits early if it looks like they were intended
10189 for directory fetches. Relays are also more aggressive about closing
10190 TLS connections that have no circuits on them. Such circuits are
10191 unlikely to be re-used, and tens of thousands of them were piling
10192 up at the fast relays, causing the relays to run out of sockets
10193 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10194 their directory fetches over TLS).
10195 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10196 that claim to be earlier than 0.9.8m, but which have in reality
10197 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10198 behavior. Possible fix for some cases of bug 1346.
10199 - Directory mirrors were fetching relay descriptors only from v2
10200 directory authorities, rather than v3 authorities like they should.
10201 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10202 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10205 - Finally get rid of the deprecated and now harmful notion of "clique
10206 mode", where directory authorities maintain TLS connections to
10210 - In the util/threads test, no longer free the test_mutex before all
10211 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10212 - The master thread could starve the worker threads quite badly on
10213 certain systems, causing them to run only partially in the allowed
10214 window. This resulted in test failures. Now the master thread sleeps
10215 occasionally for a few microseconds while the two worker-threads
10216 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10219 Changes in version 0.2.2.13-alpha - 2010-04-24
10220 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
10221 problems we've been seeing on relays, especially relays with their
10222 DirPort open. If your relay has been crashing, or you turned it off
10223 because it used too many resources, give this release a try.
10226 - Teach relays to defend themselves from connection overload. Relays
10227 now close idle circuits early if it looks like they were intended
10228 for directory fetches. Relays are also more aggressive about closing
10229 TLS connections that have no circuits on them. Such circuits are
10230 unlikely to be re-used, and tens of thousands of them were piling
10231 up at the fast relays, causing the relays to run out of sockets
10232 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10233 their directory fetches over TLS).
10236 - Finally get rid of the deprecated and now harmful notion of "clique
10237 mode", where directory authorities maintain TLS connections to
10239 - Directory authorities now do an immediate reachability check as soon
10240 as they hear about a new relay. This change should slightly reduce
10241 the time between setting up a relay and getting listed as running
10242 in the consensus. It should also improve the time between setting
10243 up a bridge and seeing use by bridge users.
10244 - Directory authorities no longer launch a TLS connection to every
10245 relay as they startup. Now that we have 2k+ descriptors cached,
10246 the resulting network hiccup is becoming a burden. Besides,
10247 authorities already avoid voting about Running for the first half
10248 hour of their uptime.
10251 Changes in version 0.2.2.12-alpha - 2010-04-20
10252 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
10253 handle and vote on descriptors. It was causing relays to drop out of
10257 - Many relays have been falling out of the consensus lately because
10258 not enough authorities know about their descriptor for them to get
10259 a majority of votes. When we deprecated the v2 directory protocol,
10260 we got rid of the only way that v3 authorities can hear from each
10261 other about other descriptors. Now authorities examine every v3
10262 vote for new descriptors, and fetch them from that authority. Bugfix
10264 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
10265 and a warning in or.h related to bandwidth_weight_rule_t that
10266 prevented clean compile on OS X. Fixes bug 1363; bugfix on
10268 - Fix a segfault on relays when DirReqStatistics is enabled
10269 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
10273 - Demote a confusing TLS warning that relay operators might get when
10274 someone tries to talk to their OrPort. It is neither the operator's
10275 fault nor can they do anything about it. Fixes bug 1364; bugfix
10279 Changes in version 0.2.2.11-alpha - 2010-04-15
10280 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
10281 libraries that was causing some relays to drop out of the consensus.
10284 - Directory mirrors were fetching relay descriptors only from v2
10285 directory authorities, rather than v3 authorities like they should.
10286 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10287 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10288 - Fix a parsing error that made every possible value of
10289 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
10290 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
10291 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
10292 about the option without breaking older ones.
10293 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10294 that claim to be earlier than 0.9.8m, but which have in reality
10295 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10296 behavior. Possible fix for some cases of bug 1346.
10299 - Experiment with a more aggressive approach to preventing clients
10300 from making one-hop exit streams. Exit relays who want to try it
10301 out can set "RefuseUnknownExits 1" in their torrc, and then look
10302 for "Attempt by %s to open a stream" log messages. Let us know
10304 - Add support for statically linking zlib by specifying
10305 --enable-static-zlib, to go with our support for statically linking
10306 openssl and libevent. Resolves bug 1358.
10309 - Fix a segfault that happens whenever a Tor client that is using
10310 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
10312 - When we cleaned up the contrib/tor-exit-notice.html file, we left
10313 out the first line. Fixes bug 1295.
10314 - When building the manpage from a tarball, we required asciidoc, but
10315 the asciidoc -> roff/html conversion was already done for the
10316 tarball. Make 'make' complain only when we need asciidoc (either
10317 because we're compiling directly from git, or because we altered
10318 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
10319 - When none of the directory authorities vote on any params, Tor
10320 segfaulted when trying to make the consensus from the votes. We
10321 didn't trigger the bug in practice, because authorities do include
10322 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
10325 - In the util/threads test, no longer free the test_mutex before all
10326 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10327 - The master thread could starve the worker threads quite badly on
10328 certain systems, causing them to run only partially in the allowed
10329 window. This resulted in test failures. Now the master thread sleeps
10330 occasionally for a few microseconds while the two worker-threads
10331 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10334 Changes in version 0.2.2.10-alpha - 2010-03-07
10335 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
10336 could prevent relays from guessing their IP address correctly. It also
10337 starts the groundwork for another client-side performance boost, since
10338 currently we're not making efficient use of relays that have both the
10339 Guard flag and the Exit flag.
10342 - Fix a regression from our patch for bug 1244 that caused relays
10343 to guess their IP address incorrectly if they didn't set Address
10344 in their torrc and/or their address fails to resolve. Bugfix on
10345 0.2.2.9-alpha; fixes bug 1269.
10347 o Major features (performance):
10348 - Directory authorities now compute consensus weightings that instruct
10349 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
10350 and no flag. Clients that use these weightings will distribute
10351 network load more evenly across these different relay types. The
10352 weightings are in the consensus so we can change them globally in
10353 the future. Extra thanks to "outofwords" for finding some nasty
10354 security bugs in the first implementation of this feature.
10356 o Minor features (performance):
10357 - Always perform router selections using weighted relay bandwidth,
10358 even if we don't need a high capacity circuit at the time. Non-fast
10359 circuits now only differ from fast ones in that they can use relays
10360 not marked with the Fast flag. This "feature" could turn out to
10361 be a horrible bug; we should investigate more before it goes into
10365 - Allow disabling building of the manpages. Skipping the manpage
10366 speeds up the build considerably.
10368 o Minor bugfixes (on 0.2.2.x):
10369 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
10370 Bugfix on 0.2.2.9-alpha.
10371 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
10372 config option. Bugfix on 0.2.2.7-alpha.
10373 - Ship the asciidoc-helper file in the tarball, so that people can
10374 build from source if they want to, and touching the .1.txt files
10375 doesn't break the build. Bugfix on 0.2.2.9-alpha.
10377 o Minor bugfixes (on 0.2.1.x or earlier):
10378 - Fix a dereference-then-NULL-check sequence when publishing
10379 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10381 - Fix another dereference-then-NULL-check sequence. Bugfix on
10382 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10383 - Make sure we treat potentially not NUL-terminated strings correctly.
10384 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10386 o Code simplifications and refactoring:
10387 - Fix some urls in the exit notice file and make it XHTML1.1 strict
10388 compliant. Based on a patch from Christian Kujau.
10389 - Don't use sed in asciidoc-helper anymore.
10390 - Make the build process fail if asciidoc cannot be found and
10391 building with asciidoc isn't disabled.
10394 Changes in version 0.2.2.9-alpha - 2010-02-22
10395 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
10396 location of a directory authority, and cleans up a bunch of small bugs.
10398 o Directory authority changes:
10399 - Change IP address for dannenberg (v3 directory authority), and
10400 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10401 service directory authority) from the list.
10404 - Make Tor work again on the latest OS X: when deciding whether to
10405 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10406 version at run-time, not compile time. We need to do this because
10407 Apple doesn't update its dev-tools headers when it updates its
10408 libraries in a security patch.
10409 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10410 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10411 a memory leak when requesting a hidden service descriptor we've
10412 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10414 - Authorities could be tricked into giving out the Exit flag to relays
10415 that didn't allow exiting to any ports. This bug could screw
10416 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
10417 1238. Bug discovered by Martin Kowalczyk.
10418 - When freeing a session key, zero it out completely. We only zeroed
10419 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10420 patched by ekir. Fixes bug 1254.
10423 - Fix static compilation by listing the openssl libraries in the right
10424 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
10425 - Resume handling .exit hostnames in a special way: originally we
10426 stripped the .exit part and used the requested exit relay. In
10427 0.2.2.1-alpha we stopped treating them in any special way, meaning
10428 if you use a .exit address then Tor will pass it on to the exit
10429 relay. Now we reject the .exit stream outright, since that behavior
10430 might be more expected by the user. Found and diagnosed by Scott
10431 Bennett and Downie on or-talk.
10432 - Don't spam the controller with events when we have no file
10433 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
10434 for log messages was already solved from bug 748.)
10435 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
10437 - Make the DNSPort option work with libevent 2.x. Don't alter the
10438 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
10439 - Emit a GUARD DROPPED controller event for a case we missed.
10440 - Make more fields in the controller protocol case-insensitive, since
10441 control-spec.txt said they were.
10442 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10443 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10444 - Fix a spec conformance issue: the network-status-version token
10445 must be the first token in a v3 consensus or vote. Discovered by
10446 parakeep. Bugfix on 0.2.0.3-alpha.
10448 o Code simplifications and refactoring:
10449 - Generate our manpage and HTML documentation using Asciidoc. This
10450 change should make it easier to maintain the documentation, and
10451 produce nicer HTML.
10452 - Remove the --enable-iphone option. According to reports from Marco
10453 Bonetti, Tor builds fine without any special tweaking on recent
10454 iPhone SDK versions.
10455 - Removed some unnecessary files from the source distribution. The
10456 AUTHORS file has now been merged into the people page on the
10457 website. The roadmaps and design doc can now be found in the
10458 projects directory in svn.
10459 - Enabled various circuit build timeout constants to be controlled
10460 by consensus parameters. Also set better defaults for these
10461 parameters based on experimentation on broadband and simulated
10462 high latency links.
10465 - The 'EXTENDCIRCUIT' control port command can now be used with
10466 a circ id of 0 and no path. This feature will cause Tor to build
10467 a new 'fast' general purpose circuit using its own path selection
10469 - Added a BUILDTIMEOUT_SET controller event to describe changes
10470 to the circuit build timeout.
10471 - Future-proof the controller protocol a bit by ignoring keyword
10472 arguments we do not recognize.
10473 - Expand homedirs passed to tor-checkkey. This should silence a
10474 coverity complaint about passing a user-supplied string into
10475 open() without checking it.
10478 Changes in version 0.2.1.25 - 2010-03-16
10479 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
10480 prevent relays from guessing their IP address correctly. It also fixes
10481 several minor potential security bugs.
10484 - Fix a regression from our patch for bug 1244 that caused relays
10485 to guess their IP address incorrectly if they didn't set Address
10486 in their torrc and/or their address fails to resolve. Bugfix on
10487 0.2.1.23; fixes bug 1269.
10488 - When freeing a session key, zero it out completely. We only zeroed
10489 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10490 patched by ekir. Fixes bug 1254.
10493 - Fix a dereference-then-NULL-check sequence when publishing
10494 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10496 - Fix another dereference-then-NULL-check sequence. Bugfix on
10497 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10498 - Make sure we treat potentially not NUL-terminated strings correctly.
10499 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10503 Changes in version 0.2.1.24 - 2010-02-21
10504 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
10508 - Work correctly out-of-the-box with even more vendor-patched versions
10509 of OpenSSL. In particular, make it so Debian and OS X don't need
10510 customized patches to run/build.
10513 Changes in version 0.2.1.23 - 2010-02-13
10514 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
10515 again on the latest OS X, and updates the location of a directory
10518 o Major bugfixes (performance):
10519 - We were selecting our guards uniformly at random, and then weighting
10520 which of our guards we'd use uniformly at random. This imbalance
10521 meant that Tor clients were severely limited on throughput (and
10522 probably latency too) by the first hop in their circuit. Now we
10523 select guards weighted by currently advertised bandwidth. We also
10524 automatically discard guards picked using the old algorithm. Fixes
10525 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10528 - Make Tor work again on the latest OS X: when deciding whether to
10529 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10530 version at run-time, not compile time. We need to do this because
10531 Apple doesn't update its dev-tools headers when it updates its
10532 libraries in a security patch.
10533 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10534 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10535 a memory leak when requesting a hidden service descriptor we've
10536 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10539 o Directory authority changes:
10540 - Change IP address for dannenberg (v3 directory authority), and
10541 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10542 service directory authority) from the list.
10545 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10546 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10549 - Avoid a mad rush at the beginning of each month when each client
10550 rotates half of its guards. Instead we spread the rotation out
10551 throughout the month, but we still avoid leaving a precise timestamp
10552 in the state file about when we first picked the guard. Improves
10553 over the behavior introduced in 0.1.2.17.
10556 Changes in version 0.2.2.8-alpha - 2010-01-26
10557 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
10558 causing bridge relays to disappear. If you're running a bridge,
10562 - Fix a memory corruption bug on bridges that occured during the
10563 inclusion of stats data in extra-info descriptors. Also fix the
10564 interface for geoip_get_bridge_stats* to prevent similar bugs in
10565 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
10566 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
10569 - Ignore OutboundBindAddress when connecting to localhost.
10570 Connections to localhost need to come _from_ localhost, or else
10571 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10575 Changes in version 0.2.2.7-alpha - 2010-01-19
10576 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
10577 as laying the groundwork for further relay-side performance fixes. It
10578 also starts cleaning up client behavior with respect to the EntryNodes,
10579 ExitNodes, and StrictNodes config options.
10581 This release also rotates two directory authority keys, due to a
10582 security breach of some of the Torproject servers.
10584 o Directory authority changes:
10585 - Rotate keys (both v3 identity and relay identity) for moria1
10588 o Major features (performance):
10589 - We were selecting our guards uniformly at random, and then weighting
10590 which of our guards we'd use uniformly at random. This imbalance
10591 meant that Tor clients were severely limited on throughput (and
10592 probably latency too) by the first hop in their circuit. Now we
10593 select guards weighted by currently advertised bandwidth. We also
10594 automatically discard guards picked using the old algorithm. Fixes
10595 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10596 - When choosing which cells to relay first, relays can now favor
10597 circuits that have been quiet recently, to provide lower latency
10598 for low-volume circuits. By default, relays enable or disable this
10599 feature based on a setting in the consensus. You can override
10600 this default by using the new "CircuitPriorityHalflife" config
10601 option. Design and code by Ian Goldberg, Can Tang, and Chris
10603 - Add separate per-conn write limiting to go with the per-conn read
10604 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
10605 but never per-conn write limits.
10606 - New consensus params "bwconnrate" and "bwconnburst" to let us
10607 rate-limit client connections as they enter the network. It's
10608 controlled in the consensus so we can turn it on and off for
10609 experiments. It's starting out off. Based on proposal 163.
10611 o Major features (relay selection options):
10612 - Switch to a StrictNodes config option, rather than the previous
10613 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
10614 "StrictExcludeNodes" option.
10615 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
10616 change during a config reload, mark and discard all our origin
10617 circuits. This fix should address edge cases where we change the
10618 config options and but then choose a circuit that we created before
10620 - If EntryNodes or ExitNodes are set, be more willing to use an
10621 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
10623 - Make EntryNodes config option much more aggressive even when
10624 StrictNodes is not set. Before it would prepend your requested
10625 entrynodes to your list of guard nodes, but feel free to use others
10626 after that. Now it chooses only from your EntryNodes if any of
10627 those are available, and only falls back to others if a) they're
10628 all down and b) StrictNodes is not set.
10629 - Now we refresh your entry guards from EntryNodes at each consensus
10630 fetch -- rather than just at startup and then they slowly rot as
10631 the network changes.
10634 - Stop bridge directory authorities from answering dbg-stability.txt
10635 directory queries, which would let people fetch a list of all
10636 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10639 - Log a notice when we get a new control connection. Now it's easier
10640 for security-conscious users to recognize when a local application
10641 is knocking on their controller door. Suggested by bug 1196.
10642 - New config option "CircuitStreamTimeout" to override our internal
10643 timeout schedule for how many seconds until we detach a stream from
10644 a circuit and try a new circuit. If your network is particularly
10645 slow, you might want to set this to a number like 60.
10646 - New controller command "getinfo config-text". It returns the
10647 contents that Tor would write if you send it a SAVECONF command,
10648 so the controller can write the file to disk itself.
10649 - New options for SafeLogging to allow scrubbing only log messages
10650 generated while acting as a relay.
10651 - Ship the bridges spec file in the tarball too.
10652 - Avoid a mad rush at the beginning of each month when each client
10653 rotates half of its guards. Instead we spread the rotation out
10654 throughout the month, but we still avoid leaving a precise timestamp
10655 in the state file about when we first picked the guard. Improves
10656 over the behavior introduced in 0.1.2.17.
10658 o Minor bugfixes (compiling):
10659 - Fix compilation on OS X 10.3, which has a stub mlockall() but
10660 hides it. Bugfix on 0.2.2.6-alpha.
10661 - Fix compilation on Solaris by removing support for the
10662 DisableAllSwap config option. Solaris doesn't have an rlimit for
10663 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
10666 o Minor bugfixes (crashes):
10667 - Do not segfault when writing buffer stats when we haven't observed
10668 a single circuit to report about. Found by Fabian Lanze. Bugfix on
10670 - If we're in the pathological case where there's no exit bandwidth
10671 but there is non-exit bandwidth, or no guard bandwidth but there
10672 is non-guard bandwidth, don't crash during path selection. Bugfix
10674 - Fix an impossible-to-actually-trigger buffer overflow in relay
10675 descriptor generation. Bugfix on 0.1.0.15.
10677 o Minor bugfixes (privacy):
10678 - Fix an instance where a Tor directory mirror might accidentally
10679 log the IP address of a misbehaving Tor client. Bugfix on
10681 - Don't list Windows capabilities in relay descriptors. We never made
10682 use of them, and maybe it's a bad idea to publish them. Bugfix
10685 o Minor bugfixes (other):
10686 - Resolve an edge case in path weighting that could make us misweight
10687 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
10688 - Fix statistics on client numbers by country as seen by bridges that
10689 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
10690 intervals instead of variable 12-to-48-hour intervals.
10691 - After we free an internal connection structure, overwrite it
10692 with a different memory value than we use for overwriting a freed
10693 internal circuit structure. Should help with debugging. Suggested
10695 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
10698 o Removed features:
10699 - Remove the HSAuthorityRecordStats option that version 0 hidden
10700 service authorities could have used to track statistics of overall
10701 hidden service usage.
10704 Changes in version 0.2.1.22 - 2010-01-19
10705 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
10706 authorities -- it would tell you its whole history of bridge descriptors
10707 if you make the right directory request. This stable update also
10708 rotates two of the seven v3 directory authority keys and locations.
10710 o Directory authority changes:
10711 - Rotate keys (both v3 identity and relay identity) for moria1
10715 - Stop bridge directory authorities from answering dbg-stability.txt
10716 directory queries, which would let people fetch a list of all
10717 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10720 Changes in version 0.2.1.21 - 2009-12-21
10721 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
10722 library. If you use Tor on Linux / Unix and you're getting SSL
10723 renegotiation errors, upgrading should help. We also recommend an
10724 upgrade if you're an exit relay.
10727 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10728 handshake from working unless we explicitly tell OpenSSL that we
10729 are using SSL renegotiation safely. We are, of course, but OpenSSL
10730 0.9.8l won't work unless we say we are.
10731 - Avoid crashing if the client is trying to upload many bytes and the
10732 circuit gets torn down at the same time, or if the flip side
10733 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
10736 - Do not refuse to learn about authority certs and v2 networkstatus
10737 documents that are older than the latest consensus. This bug might
10738 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10739 Spotted and fixed by xmux.
10740 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
10741 trigger platform-specific option misparsing case found by Coverity
10743 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
10744 trigger assert. Fixes bug 1173.
10747 Changes in version 0.2.2.6-alpha - 2009-11-19
10748 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
10749 support for the new lower-footprint "microdescriptor" directory design,
10750 future-proofing our consensus format against new hash functions or
10751 other changes, and an Android port. It also makes Tor compatible with
10752 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
10755 - Directory authorities can now create, vote on, and serve multiple
10756 parallel formats of directory data as part of their voting process.
10757 Partially implements Proposal 162: "Publish the consensus in
10759 - Directory authorities can now agree on and publish small summaries
10760 of router information that clients can use in place of regular
10761 server descriptors. This transition will eventually allow clients
10762 to use far less bandwidth for downloading information about the
10763 network. Begins the implementation of Proposal 158: "Clients
10764 download consensus + microdescriptors".
10765 - The directory voting system is now extensible to use multiple hash
10766 algorithms for signatures and resource selection. Newer formats
10767 are signed with SHA256, with a possibility for moving to a better
10768 hash algorithm in the future.
10769 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
10770 current and future memory pages via mlockall(). On supported
10771 platforms (modern Linux and probably BSD but not Windows or OS X),
10772 this should effectively disable any and all attempts to page out
10773 memory. This option requires that you start your Tor as root --
10774 if you use DisableAllSwap, please consider using the User option
10775 to properly reduce the privileges of your Tor.
10776 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
10777 to help Tor build correctly for Android phones.
10780 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10781 handshake from working unless we explicitly tell OpenSSL that we
10782 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
10783 won't work unless we say we are.
10786 - Fix a crash bug when trying to initialize the evdns module in
10787 Libevent 2. Bugfix on 0.2.1.16-rc.
10788 - Stop logging at severity 'warn' when some other Tor client tries
10789 to establish a circuit with us using weak DH keys. It's a protocol
10790 violation, but that doesn't mean ordinary users need to hear about
10791 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
10792 - Do not refuse to learn about authority certs and v2 networkstatus
10793 documents that are older than the latest consensus. This bug might
10794 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10795 Spotted and fixed by xmux.
10796 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
10797 - If all authorities restart at once right before a consensus vote,
10798 nobody will vote about "Running", and clients will get a consensus
10799 with no usable relays. Instead, authorities refuse to build a
10800 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
10801 - If your relay can't keep up with the number of incoming create
10802 cells, it would log one warning per failure into your logs. Limit
10803 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
10804 - Bridges now use "reject *:*" as their default exit policy. Bugfix
10805 on 0.2.0.3-alpha; fixes bug 1113.
10806 - Fix a memory leak on directory authorities during voting that was
10807 introduced in 0.2.2.1-alpha. Found via valgrind.
10810 Changes in version 0.2.1.20 - 2009-10-15
10811 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
10812 services at once, prepares for more performance improvements, and
10813 fixes a bunch of smaller bugs.
10815 The Windows and OS X bundles also include a more recent Vidalia,
10816 and switch from Privoxy to Polipo.
10818 The OS X installers are now drag and drop. It's best to un-install
10819 Tor/Vidalia and then install this new bundle, rather than upgrade. If
10820 you want to upgrade, you'll need to update the paths for Tor and Polipo
10821 in the Vidalia Settings window.
10824 - Send circuit or stream sendme cells when our window has decreased
10825 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10826 by Karsten when testing the "reduce circuit window" performance
10827 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10828 before the release of Tor 0.0.0. This is the new winner of the
10830 - Fix a remotely triggerable memory leak when a consensus document
10831 contains more than one signature from the same voter. Bugfix on
10833 - Avoid segfault in rare cases when finishing an introduction circuit
10834 as a client and finding out that we don't have an introduction key
10835 for it. Fixes bug 1073. Reported by Aaron Swartz.
10838 - Tor now reads the "circwindow" parameter out of the consensus,
10839 and uses that value for its circuit package window rather than the
10840 default of 1000 cells. Begins the implementation of proposal 168.
10842 o New directory authorities:
10843 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10845 - Move moria1 and tonga to alternate IP addresses.
10848 - Fix a signed/unsigned compile warning in 0.2.1.19.
10849 - Fix possible segmentation fault on directory authorities. Bugfix on
10851 - Fix an extremely rare infinite recursion bug that could occur if
10852 we tried to log a message after shutting down the log subsystem.
10853 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10854 - Fix an obscure bug where hidden services on 64-bit big-endian
10855 systems might mis-read the timestamp in v3 introduce cells, and
10856 refuse to connect back to the client. Discovered by "rotor".
10857 Bugfix on 0.2.1.6-alpha.
10858 - We were triggering a CLOCK_SKEW controller status event whenever
10859 we connect via the v2 connection protocol to any relay that has
10860 a wrong clock. Instead, we should only inform the controller when
10861 it's a trusted authority that claims our clock is wrong. Bugfix
10862 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10863 - We were telling the controller about CHECKING_REACHABILITY and
10864 REACHABILITY_FAILED status events whenever we launch a testing
10865 circuit or notice that one has failed. Instead, only tell the
10866 controller when we want to inform the user of overall success or
10867 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10869 - Don't warn when we're using a circuit that ends with a node
10870 excluded in ExcludeExitNodes, but the circuit is not used to access
10871 the outside world. This should help fix bug 1090. Bugfix on
10873 - Work around a small memory leak in some versions of OpenSSL that
10874 stopped the memory used by the hostname TLS extension from being
10878 - Add a "getinfo status/accepted-server-descriptor" controller
10879 command, which is the recommended way for controllers to learn
10880 whether our server descriptor has been successfully received by at
10881 least on directory authority. Un-recommend good-server-descriptor
10882 getinfo and status events until we have a better design for them.
10885 Changes in version 0.2.2.5-alpha - 2009-10-11
10886 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
10889 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
10891 o Directory authorities:
10892 - Temporarily (just for this release) move dizum to an alternate
10896 Changes in version 0.2.2.4-alpha - 2009-10-10
10897 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
10898 introduces a new unit test framework, shifts directry authority
10899 addresses around to reduce the impact from recent blocking events,
10900 and fixes a few smaller bugs.
10903 - Fix several more asserts in the circuit_build_times code, for
10904 example one that causes Tor to fail to start once we have
10905 accumulated 5000 build times in the state file. Bugfixes on
10906 0.2.2.2-alpha; fixes bug 1108.
10908 o New directory authorities:
10909 - Move moria1 and Tonga to alternate IP addresses.
10912 - Log SSL state transitions at debug level during handshake, and
10913 include SSL states in error messages. This may help debug future
10914 SSL handshake issues.
10915 - Add a new "Handshake" log domain for activities that happen
10916 during the TLS handshake.
10917 - Revert to the "June 3 2009" ip-to-country file. The September one
10918 seems to have removed most US IP addresses.
10919 - Directory authorities now reject Tor relays with versions less than
10920 0.1.2.14. This step cuts out four relays from the current network,
10921 none of which are very big.
10924 - Fix a couple of smaller issues with gathering statistics. Bugfixes
10926 - Fix two memory leaks in the error case of
10927 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
10928 - Don't count one-hop circuits when we're estimating how long it
10929 takes circuits to build on average. Otherwise we'll set our circuit
10930 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
10931 - Directory authorities no longer change their opinion of, or vote on,
10932 whether a router is Running, unless they have themselves been
10933 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
10936 o Code simplifications and refactoring:
10937 - Revise our unit tests to use the "tinytest" framework, so we
10938 can run tests in their own processes, have smarter setup/teardown
10939 code, and so on. The unit test code has moved to its own
10940 subdirectory, and has been split into multiple modules.
10943 Changes in version 0.2.2.3-alpha - 2009-09-23
10944 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
10947 - Fix an overzealous assert in our new circuit build timeout code.
10948 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
10951 - If the networkstatus consensus tells us that we should use a
10952 negative circuit package window, ignore it. Otherwise we'll
10953 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
10956 Changes in version 0.2.2.2-alpha - 2009-09-21
10957 Tor 0.2.2.2-alpha introduces our latest performance improvement for
10958 clients: Tor tracks the average time it takes to build a circuit, and
10959 avoids using circuits that take too long to build. For fast connections,
10960 this feature can cut your expected latency in half. For slow or flaky
10961 connections, it could ruin your Tor experience. Let us know if it does!
10964 - Tor now tracks how long it takes to build client-side circuits
10965 over time, and adapts its timeout to local network performance.
10966 Since a circuit that takes a long time to build will also provide
10967 bad performance, we get significant latency improvements by
10968 discarding the slowest 20% of circuits. Specifically, Tor creates
10969 circuits more aggressively than usual until it has enough data
10970 points for a good timeout estimate. Implements proposal 151.
10971 We are especially looking for reports (good and bad) from users with
10972 both EDGE and broadband connections that can move from broadband
10973 to EDGE and find out if the build-time data in the .tor/state gets
10974 reset without loss of Tor usability. You should also see a notice
10975 log message telling you that Tor has reset its timeout.
10976 - Directory authorities can now vote on arbitary integer values as
10977 part of the consensus process. This is designed to help set
10978 network-wide parameters. Implements proposal 167.
10979 - Tor now reads the "circwindow" parameter out of the consensus,
10980 and uses that value for its circuit package window rather than the
10981 default of 1000 cells. Begins the implementation of proposal 168.
10984 - Fix a remotely triggerable memory leak when a consensus document
10985 contains more than one signature from the same voter. Bugfix on
10989 - Fix an extremely rare infinite recursion bug that could occur if
10990 we tried to log a message after shutting down the log subsystem.
10991 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10992 - Fix parsing for memory or time units given without a space between
10993 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
10994 - A networkstatus vote must contain exactly one signature. Spec
10995 conformance issue. Bugfix on 0.2.0.3-alpha.
10996 - Fix an obscure bug where hidden services on 64-bit big-endian
10997 systems might mis-read the timestamp in v3 introduce cells, and
10998 refuse to connect back to the client. Discovered by "rotor".
10999 Bugfix on 0.2.1.6-alpha.
11000 - We were triggering a CLOCK_SKEW controller status event whenever
11001 we connect via the v2 connection protocol to any relay that has
11002 a wrong clock. Instead, we should only inform the controller when
11003 it's a trusted authority that claims our clock is wrong. Bugfix
11004 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11005 - We were telling the controller about CHECKING_REACHABILITY and
11006 REACHABILITY_FAILED status events whenever we launch a testing
11007 circuit or notice that one has failed. Instead, only tell the
11008 controller when we want to inform the user of overall success or
11009 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11011 - Don't warn when we're using a circuit that ends with a node
11012 excluded in ExcludeExitNodes, but the circuit is not used to access
11013 the outside world. This should help fix bug 1090, but more problems
11014 remain. Bugfix on 0.2.1.6-alpha.
11015 - Work around a small memory leak in some versions of OpenSSL that
11016 stopped the memory used by the hostname TLS extension from being
11018 - Make our 'torify' script more portable; if we have only one of
11019 'torsocks' or 'tsocks' installed, don't complain to the user;
11020 and explain our warning about tsocks better.
11023 - Add a "getinfo status/accepted-server-descriptor" controller
11024 command, which is the recommended way for controllers to learn
11025 whether our server descriptor has been successfully received by at
11026 least on directory authority. Un-recommend good-server-descriptor
11027 getinfo and status events until we have a better design for them.
11028 - Update to the "September 4 2009" ip-to-country file.
11031 Changes in version 0.2.2.1-alpha - 2009-08-26
11032 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
11033 Tor clients to bootstrap on networks where only port 80 is reachable,
11034 makes it more straightforward to support hardware crypto accelerators,
11035 and starts the groundwork for gathering stats safely at relays.
11038 - Start the process of disabling ".exit" address notation, since it
11039 can be used for a variety of esoteric application-level attacks
11040 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
11043 o New directory authorities:
11044 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11048 - New AccelName and AccelDir options add support for dynamic OpenSSL
11049 hardware crypto acceleration engines.
11050 - Tor now supports tunneling all of its outgoing connections over
11051 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
11052 configuration options. Code by Christopher Davis.
11055 - Send circuit or stream sendme cells when our window has decreased
11056 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11057 by Karsten when testing the "reduce circuit window" performance
11058 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11059 before the release of Tor 0.0.0. This is the new winner of the
11062 o New options for gathering stats safely:
11063 - Directory mirrors that set "DirReqStatistics 1" write statistics
11064 about directory requests to disk every 24 hours. As compared to the
11065 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
11066 1) stats are written to disk exactly every 24 hours; 2) estimated
11067 shares of v2 and v3 requests are determined as mean values, not at
11068 the end of a measurement period; 3) unresolved requests are listed
11069 with country code '??'; 4) directories also measure download times.
11070 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
11071 number of exit streams and transferred bytes per port to disk every
11073 - Relays that set "CellStatistics 1" write statistics on how long
11074 cells spend in their circuit queues to disk every 24 hours.
11075 - Entry nodes that set "EntryStatistics 1" write statistics on the
11076 rough number and origins of connecting clients to disk every 24
11078 - Relays that write any of the above statistics to disk and set
11079 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
11080 their extra-info documents.
11083 - New --digests command-line switch to output the digests of the
11084 source files Tor was built with.
11085 - The "torify" script now uses torsocks where available.
11086 - The memarea code now uses a sentinel value at the end of each area
11087 to make sure nothing writes beyond the end of an area. This might
11088 help debug some conceivable causes of bug 930.
11089 - Time and memory units in the configuration file can now be set to
11090 fractional units. For example, "2.5 GB" is now a valid value for
11092 - Certain Tor clients (such as those behind check.torproject.org) may
11093 want to fetch the consensus in an extra early manner. To enable this
11094 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
11095 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
11096 as only certain clients who must have this information sooner should
11098 - Instead of adding the svn revision to the Tor version string, report
11099 the git commit (when we're building from a git checkout).
11102 - If any of the v3 certs we download are unparseable, we should
11103 actually notice the failure so we don't retry indefinitely. Bugfix
11104 on 0.2.0.x; reported by "rotator".
11105 - If the cached cert file is unparseable, warn but don't exit.
11106 - Fix possible segmentation fault on directory authorities. Bugfix on
11108 - When Tor fails to parse a descriptor of any kind, dump it to disk.
11109 Might help diagnosing bug 1051.
11111 o Deprecated and removed features:
11112 - The controller no longer accepts the old obsolete "addr-mappings/"
11113 or "unregistered-servers-" GETINFO values.
11114 - Hidden services no longer publish version 0 descriptors, and clients
11115 do not request or use version 0 descriptors. However, the old hidden
11116 service authorities still accept and serve version 0 descriptors
11117 when contacted by older hidden services/clients.
11118 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
11119 always on; using them is necessary for correct forward-compatible
11121 - Remove support for .noconnect style addresses. Nobody was using
11122 them, and they provided another avenue for detecting Tor users
11123 via application-level web tricks.
11125 o Packaging changes:
11126 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
11127 installer bundles. See
11128 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
11129 for details of what's new in Vidalia 0.2.3.
11130 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
11131 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
11132 configuration file, rather than the old Privoxy.
11133 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
11134 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
11135 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
11136 better compatibility with OS X 10.6, aka Snow Leopard.
11137 - OS X Vidalia Bundle: The multi-package installer is now replaced
11138 by a simple drag and drop to the /Applications folder. This change
11139 occurred with the upgrade to Vidalia 0.2.3.
11142 Changes in version 0.2.1.19 - 2009-07-28
11143 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
11144 services on Tor 0.2.1.3-alpha through 0.2.1.18.
11147 - Make accessing hidden services on 0.2.1.x work right again.
11148 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
11149 part of patch provided by "optimist".
11152 - When a relay/bridge is writing out its identity key fingerprint to
11153 the "fingerprint" file and to its logs, write it without spaces. Now
11154 it will look like the fingerprints in our bridges documentation,
11155 and confuse fewer users.
11158 - Relays no longer publish a new server descriptor if they change
11159 their MaxAdvertisedBandwidth config option but it doesn't end up
11160 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
11161 fixes bug 1026. Patch from Sebastian.
11162 - Avoid leaking memory every time we get a create cell but we have
11163 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
11164 fixes bug 1034. Reported by BarkerJr.
11167 Changes in version 0.2.1.18 - 2009-07-24
11168 Tor 0.2.1.18 lays the foundations for performance improvements,
11169 adds status events to help users diagnose bootstrap problems, adds
11170 optional authentication/authorization for hidden services, fixes a
11171 variety of potential anonymity problems, and includes a huge pile of
11172 other features and bug fixes.
11175 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
11178 Changes in version 0.2.1.17-rc - 2009-07-07
11179 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
11180 candidate for the 0.2.1.x series. It lays the groundwork for further
11181 client performance improvements, and also fixes a big bug with directory
11182 authorities that were causing them to assign Guard and Stable flags
11185 The Windows bundles also finally include the geoip database that we
11186 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
11187 should actually install Torbutton rather than giving you a cryptic
11188 failure message (oops).
11191 - Clients now use the bandwidth values in the consensus, rather than
11192 the bandwidth values in each relay descriptor. This approach opens
11193 the door to more accurate bandwidth estimates once the directory
11194 authorities start doing active measurements. Implements more of
11198 - When Tor clients restart after 1-5 days, they discard all their
11199 cached descriptors as too old, but they still use the cached
11200 consensus document. This approach is good for robustness, but
11201 bad for performance: since they don't know any bandwidths, they
11202 end up choosing at random rather than weighting their choice by
11203 speed. Fixed by the above feature of putting bandwidths in the
11204 consensus. Bugfix on 0.2.0.x.
11205 - Directory authorities were neglecting to mark relays down in their
11206 internal histories if the relays fall off the routerlist without
11207 ever being found unreachable. So there were relays in the histories
11208 that haven't been seen for eight months, and are listed as being
11209 up for eight months. This wreaked havoc on the "median wfu"
11210 and "median mtbf" calculations, in turn making Guard and Stable
11211 flags very wrong, hurting network performance. Fixes bugs 696 and
11212 969. Bugfix on 0.2.0.6-alpha.
11215 - Serve the DirPortFrontPage page even when we have been approaching
11216 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
11217 - The control port would close the connection before flushing long
11218 replies, such as the network consensus, if a QUIT command was issued
11219 before the reply had completed. Now, the control port flushes all
11220 pending replies before closing the connection. Also fixed a spurious
11221 warning when a QUIT command is issued after a malformed or rejected
11222 AUTHENTICATE command, but before the connection was closed. Patch
11223 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
11224 - When we can't find an intro key for a v2 hidden service descriptor,
11225 fall back to the v0 hidden service descriptor and log a bug message.
11226 Workaround for bug 1024.
11227 - Fix a log message that did not respect the SafeLogging option.
11231 - If we're a relay and we change our IP address, be more verbose
11232 about the reason that made us change. Should help track down
11233 further bugs for relays on dynamic IP addresses.
11236 Changes in version 0.2.0.35 - 2009-06-24
11238 - Avoid crashing in the presence of certain malformed descriptors.
11239 Found by lark, and by automated fuzzing.
11240 - Fix an edge case where a malicious exit relay could convince a
11241 controller that the client's DNS question resolves to an internal IP
11242 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11245 - Finally fix the bug where dynamic-IP relays disappear when their
11246 IP address changes: directory mirrors were mistakenly telling
11247 them their old address if they asked via begin_dir, so they
11248 never got an accurate answer about their new address, so they
11249 just vanished after a day. For belt-and-suspenders, relays that
11250 don't set Address in their config now avoid using begin_dir for
11251 all direct connections. Should fix bugs 827, 883, and 900.
11252 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11253 that would occur on some exit nodes when DNS failures and timeouts
11254 occurred in certain patterns. Fix for bug 957.
11257 - When starting with a cache over a few days old, do not leak
11258 memory for the obsolete router descriptors in it. Bugfix on
11259 0.2.0.33; fixes bug 672.
11260 - Hidden service clients didn't use a cached service descriptor that
11261 was older than 15 minutes, but wouldn't fetch a new one either,
11262 because there was already one in the cache. Now, fetch a v2
11263 descriptor unless the same descriptor was added to the cache within
11264 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11267 Changes in version 0.2.1.16-rc - 2009-06-20
11268 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
11269 a bunch of minor bugs.
11272 - Fix an edge case where a malicious exit relay could convince a
11273 controller that the client's DNS question resolves to an internal IP
11274 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11276 o Major performance improvements (on 0.2.0.x):
11277 - Disable and refactor some debugging checks that forced a linear scan
11278 over the whole server-side DNS cache. These accounted for over 50%
11279 of CPU time on a relatively busy exit node's gprof profile. Found
11281 - Disable some debugging checks that appeared in exit node profile
11285 - Update to the "June 3 2009" ip-to-country file.
11286 - Do not have tor-resolve automatically refuse all .onion addresses;
11287 if AutomapHostsOnResolve is set in your torrc, this will work fine.
11289 o Minor bugfixes (on 0.2.0.x):
11290 - Log correct error messages for DNS-related network errors on
11292 - Fix a race condition that could cause crashes or memory corruption
11293 when running as a server with a controller listening for log
11295 - Avoid crashing when we have a policy specified in a DirPolicy or
11296 SocksPolicy or ReachableAddresses option with ports set on it,
11297 and we re-load the policy. May fix bug 996.
11298 - Hidden service clients didn't use a cached service descriptor that
11299 was older than 15 minutes, but wouldn't fetch a new one either,
11300 because there was already one in the cache. Now, fetch a v2
11301 descriptor unless the same descriptor was added to the cache within
11302 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11304 o Minor bugfixes (on 0.2.1.x):
11305 - Don't warn users about low port and hibernation mix when they
11306 provide a *ListenAddress directive to fix that. Bugfix on
11308 - When switching back and forth between bridge mode, do not start
11309 gathering GeoIP data until two hours have passed.
11310 - Do not complain that the user has requested an excluded node as
11311 an exit when the node is not really an exit. This could happen
11312 because the circuit was for testing, or an introduction point.
11316 Changes in version 0.2.1.15-rc - 2009-05-25
11317 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
11318 series. It fixes a major bug on fast exit relays, as well as a variety
11319 of more minor bugs.
11321 o Major bugfixes (on 0.2.0.x):
11322 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11323 that would occur on some exit nodes when DNS failures and timeouts
11324 occurred in certain patterns. Fix for bug 957.
11326 o Minor bugfixes (on 0.2.0.x):
11327 - Actually return -1 in the error case for read_bandwidth_usage().
11328 Harmless bug, since we currently don't care about the return value
11329 anywhere. Bugfix on 0.2.0.9-alpha.
11330 - Provide a more useful log message if bug 977 (related to buffer
11331 freelists) ever reappears, and do not crash right away.
11332 - Fix an assertion failure on 64-bit platforms when we allocated
11333 memory right up to the end of a memarea, then realigned the memory
11334 one step beyond the end. Fixes a possible cause of bug 930.
11335 - Protect the count of open sockets with a mutex, so we can't
11336 corrupt it when two threads are closing or opening sockets at once.
11337 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
11338 - Don't allow a bridge to publish its router descriptor to a
11339 non-bridge directory authority. Fixes part of bug 932.
11340 - When we change to or from being a bridge, reset our counts of
11341 client usage by country. Fixes bug 932.
11342 - Fix a bug that made stream bandwidth get misreported to the
11344 - Stop using malloc_usable_size() to use more area than we had
11345 actually allocated: it was safe, but made valgrind really unhappy.
11346 - Fix a memory leak when v3 directory authorities load their keys
11347 and cert from disk. Bugfix on 0.2.0.1-alpha.
11349 o Minor bugfixes (on 0.2.1.x):
11350 - Fix use of freed memory when deciding to mark a non-addable
11351 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
11354 Changes in version 0.2.1.14-rc - 2009-04-12
11355 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
11356 series. It begins fixing some major performance problems, and also
11357 finally addresses the bug that was causing relays on dynamic IP
11358 addresses to fall out of the directory.
11361 - Clients replace entry guards that were chosen more than a few months
11362 ago. This change should significantly improve client performance,
11363 especially once more people upgrade, since relays that have been
11364 a guard for a long time are currently overloaded.
11366 o Major bugfixes (on 0.2.0):
11367 - Finally fix the bug where dynamic-IP relays disappear when their
11368 IP address changes: directory mirrors were mistakenly telling
11369 them their old address if they asked via begin_dir, so they
11370 never got an accurate answer about their new address, so they
11371 just vanished after a day. For belt-and-suspenders, relays that
11372 don't set Address in their config now avoid using begin_dir for
11373 all direct connections. Should fix bugs 827, 883, and 900.
11374 - Relays were falling out of the networkstatus consensus for
11375 part of a day if they changed their local config but the
11376 authorities discarded their new descriptor as "not sufficiently
11377 different". Now directory authorities accept a descriptor as changed
11378 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
11379 patch by Sebastian.
11380 - Avoid crashing in the presence of certain malformed descriptors.
11381 Found by lark, and by automated fuzzing.
11384 - When generating circuit events with verbose nicknames for
11385 controllers, try harder to look up nicknames for routers on a
11386 circuit. (Previously, we would look in the router descriptors we had
11387 for nicknames, but not in the consensus.) Partial fix for bug 941.
11388 - If the bridge config line doesn't specify a port, assume 443.
11389 This makes bridge lines a bit smaller and easier for users to
11391 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
11392 bytes (aka 20KB/s), to match our documentation. Also update
11393 directory authorities so they always assign the Fast flag to relays
11394 with 20KB/s of capacity. Now people running relays won't suddenly
11395 find themselves not seeing any use, if the network gets faster
11397 - Update to the "April 3 2009" ip-to-country file.
11400 - Avoid trying to print raw memory to the logs when we decide to
11401 give up on downloading a given relay descriptor. Bugfix on
11403 - In tor-resolve, when the Tor client to use is specified by
11404 <hostname>:<port>, actually use the specified port rather than
11405 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
11406 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
11407 - When starting with a cache over a few days old, do not leak
11408 memory for the obsolete router descriptors in it. Bugfix on
11410 - Avoid double-free on list of successfully uploaded hidden
11411 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
11412 - Change memarea_strndup() implementation to work even when
11413 duplicating a string at the end of a page. This bug was
11414 harmless for now, but could have meant crashes later. Fix by
11415 lark. Bugfix on 0.2.1.1-alpha.
11416 - Limit uploaded directory documents to be 16M rather than 500K.
11417 The directory authorities were refusing v3 consensus votes from
11418 other authorities, since the votes are now 504K. Fixes bug 959;
11419 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
11420 - Directory authorities should never send a 503 "busy" response to
11421 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
11425 Changes in version 0.2.1.13-alpha - 2009-03-09
11426 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
11427 cleanups. We're finally getting close to a release candidate.
11430 - Correctly update the list of which countries we exclude as
11431 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
11432 lark. Bugfix on 0.2.1.6-alpha.
11434 o Minor bugfixes (on 0.2.0.x and earlier):
11435 - Automatically detect MacOSX versions earlier than 10.4.0, and
11436 disable kqueue from inside Tor when running with these versions.
11437 We previously did this from the startup script, but that was no
11438 help to people who didn't use the startup script. Resolves bug 863.
11439 - When we had picked an exit node for a connection, but marked it as
11440 "optional", and it turned out we had no onion key for the exit,
11441 stop wanting that exit and try again. This situation may not
11442 be possible now, but will probably become feasible with proposal
11443 158. Spotted by rovv. Fixes another case of bug 752.
11444 - Clients no longer cache certificates for authorities they do not
11445 recognize. Bugfix on 0.2.0.9-alpha.
11446 - When we can't transmit a DNS request due to a network error, retry
11447 it after a while, and eventually transmit a failing response to
11448 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
11449 - If the controller claimed responsibility for a stream, but that
11450 stream never finished making its connection, it would live
11451 forever in circuit_wait state. Now we close it after SocksTimeout
11452 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
11453 - Drop begin cells to a hidden service if they come from the middle
11454 of a circuit. Patch from lark.
11455 - When we erroneously receive two EXTEND cells for the same circuit
11456 ID on the same connection, drop the second. Patch from lark.
11457 - Fix a crash that occurs on exit nodes when a nameserver request
11458 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
11459 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
11461 - Do not assume that a stack-allocated character array will be
11462 64-bit aligned on platforms that demand that uint64_t access is
11463 aligned. Possible fix for bug 604.
11464 - Parse dates and IPv4 addresses in a locale- and libc-independent
11465 manner, to avoid platform-dependent behavior on malformed input.
11466 - Build correctly when configured to build outside the main source
11467 path. Patch from Michael Gold.
11468 - We were already rejecting relay begin cells with destination port
11469 of 0. Now also reject extend cells with destination port or address
11470 of 0. Suggested by lark.
11472 o Minor bugfixes (on 0.2.1.x):
11473 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
11474 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
11475 - If we're an exit node, scrub the IP address to which we are exiting
11476 in the logs. Bugfix on 0.2.1.8-alpha.
11479 - On Linux, use the prctl call to re-enable core dumps when the user
11481 - New controller event NEWCONSENSUS that lists the networkstatus
11482 lines for every recommended relay. Now controllers like Torflow
11483 can keep up-to-date on which relays they should be using.
11484 - Update to the "February 26 2009" ip-to-country file.
11487 Changes in version 0.2.0.34 - 2009-02-08
11488 Tor 0.2.0.34 features several more security-related fixes. You should
11489 upgrade, especially if you run an exit relay (remote crash) or a
11490 directory authority (remote infinite loop), or you're on an older
11491 (pre-XP) or not-recently-patched Windows (remote exploit).
11493 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
11494 have many known flaws, and nobody should be using them. You should
11495 upgrade. If you're using a Linux or BSD and its packages are obsolete,
11496 stop using those packages and upgrade anyway.
11499 - Fix an infinite-loop bug on handling corrupt votes under certain
11500 circumstances. Bugfix on 0.2.0.8-alpha.
11501 - Fix a temporary DoS vulnerability that could be performed by
11502 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11503 - Avoid a potential crash on exit nodes when processing malformed
11504 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
11505 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11506 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11509 - Fix compilation on systems where time_t is a 64-bit integer.
11510 Patch from Matthias Drochner.
11511 - Don't consider expiring already-closed client connections. Fixes
11512 bug 893. Bugfix on 0.0.2pre20.
11515 Changes in version 0.2.1.12-alpha - 2009-02-08
11516 Tor 0.2.1.12-alpha features several more security-related fixes. You
11517 should upgrade, especially if you run an exit relay (remote crash) or
11518 a directory authority (remote infinite loop), or you're on an older
11519 (pre-XP) or not-recently-patched Windows (remote exploit). It also
11520 includes a big pile of minor bugfixes and cleanups.
11523 - Fix an infinite-loop bug on handling corrupt votes under certain
11524 circumstances. Bugfix on 0.2.0.8-alpha.
11525 - Fix a temporary DoS vulnerability that could be performed by
11526 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11527 - Avoid a potential crash on exit nodes when processing malformed
11528 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
11531 - Let controllers actually ask for the "clients_seen" event for
11532 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
11533 reported by Matt Edman.
11534 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
11536 - Fix a bug in address parsing that was preventing bridges or hidden
11537 service targets from being at IPv6 addresses.
11538 - Solve a bug that kept hardware crypto acceleration from getting
11539 enabled when accounting was turned on. Fixes bug 907. Bugfix on
11541 - Remove a bash-ism from configure.in to build properly on non-Linux
11542 platforms. Bugfix on 0.2.1.1-alpha.
11543 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
11544 headers. Bugfix on 0.2.0.10-alpha.
11545 - Don't consider expiring already-closed client connections. Fixes
11546 bug 893. Bugfix on 0.0.2pre20.
11547 - Fix another interesting corner-case of bug 891 spotted by rovv:
11548 Previously, if two hosts had different amounts of clock drift, and
11549 one of them created a new connection with just the wrong timing,
11550 the other might decide to deprecate the new connection erroneously.
11551 Bugfix on 0.1.1.13-alpha.
11552 - Resolve a very rare crash bug that could occur when the user forced
11553 a nameserver reconfiguration during the middle of a nameserver
11554 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
11555 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
11556 Bugfix on 0.2.1.7-alpha.
11557 - If we're using bridges and our network goes away, be more willing
11558 to forgive our bridges and try again when we get an application
11559 request. Bugfix on 0.2.0.x.
11562 - Support platforms where time_t is 64 bits long. (Congratulations,
11563 NetBSD!) Patch from Matthias Drochner.
11564 - Add a 'getinfo status/clients-seen' controller command, in case
11565 controllers want to hear clients_seen events but connect late.
11568 - Disable GCC's strict alias optimization by default, to avoid the
11569 likelihood of its introducing subtle bugs whenever our code violates
11570 the letter of C99's alias rules.
11573 Changes in version 0.2.0.33 - 2009-01-21
11574 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11575 useful to users. It also finally fixes a bug where a relay or client
11576 that's been off for many days would take a long time to bootstrap.
11578 This update also fixes an important security-related bug reported by
11579 Ilja van Sprundel. You should upgrade. (We'll send out more details
11580 about the bug once people have had some time to upgrade.)
11583 - Fix a heap-corruption bug that may be remotely triggerable on
11584 some platforms. Reported by Ilja van Sprundel.
11587 - When a stream at an exit relay is in state "resolving" or
11588 "connecting" and it receives an "end" relay cell, the exit relay
11589 would silently ignore the end cell and not close the stream. If
11590 the client never closes the circuit, then the exit relay never
11591 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
11592 reported by "wood".
11593 - When sending CREATED cells back for a given circuit, use a 64-bit
11594 connection ID to find the right connection, rather than an addr:port
11595 combination. Now that we can have multiple OR connections between
11596 the same ORs, it is no longer possible to use addr:port to uniquely
11597 identify a connection.
11598 - Bridge relays that had DirPort set to 0 would stop fetching
11599 descriptors shortly after startup, and then briefly resume
11600 after a new bandwidth test and/or after publishing a new bridge
11601 descriptor. Bridge users that try to bootstrap from them would
11602 get a recent networkstatus but would get descriptors from up to
11603 18 hours earlier, meaning most of the descriptors were obsolete
11604 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11605 - Prevent bridge relays from serving their 'extrainfo' document
11606 to anybody who asks, now that extrainfo docs include potentially
11607 sensitive aggregated client geoip summaries. Bugfix on
11609 - If the cached networkstatus consensus is more than five days old,
11610 discard it rather than trying to use it. In theory it could be
11611 useful because it lists alternate directory mirrors, but in practice
11612 it just means we spend many minutes trying directory mirrors that
11613 are long gone from the network. Also discard router descriptors as
11614 we load them if they are more than five days old, since the onion
11615 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
11618 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11619 could make gcc generate non-functional binary search code. Bugfix
11621 - Build correctly on platforms without socklen_t.
11622 - Compile without warnings on solaris.
11623 - Avoid potential crash on internal error during signature collection.
11624 Fixes bug 864. Patch from rovv.
11625 - Correct handling of possible malformed authority signing key
11626 certificates with internal signature types. Fixes bug 880.
11627 Bugfix on 0.2.0.3-alpha.
11628 - Fix a hard-to-trigger resource leak when logging credential status.
11630 - When we can't initialize DNS because the network is down, do not
11631 automatically stop Tor from starting. Instead, we retry failed
11632 dns_init() every 10 minutes, and change the exit policy to reject
11633 *:* until one succeeds. Fixes bug 691.
11634 - Use 64 bits instead of 32 bits for connection identifiers used with
11635 the controller protocol, to greatly reduce risk of identifier reuse.
11636 - When we're choosing an exit node for a circuit, and we have
11637 no pending streams, choose a good general exit rather than one that
11638 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11639 - Fix another case of assuming, when a specific exit is requested,
11640 that we know more than the user about what hosts it allows.
11641 Fixes one case of bug 752. Patch from rovv.
11642 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11643 seconds. Warn the user if lower values are given in the
11644 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11645 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11646 user if lower values are given in the configuration. Bugfix on
11647 0.1.1.17-rc. Patch by Sebastian.
11648 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
11649 the cache because we already had a v0 descriptor with the same ID.
11650 Bugfix on 0.2.0.18-alpha.
11651 - Fix a race condition when freeing keys shared between main thread
11652 and CPU workers that could result in a memory leak. Bugfix on
11653 0.1.0.1-rc. Fixes bug 889.
11654 - Send a valid END cell back when a client tries to connect to a
11655 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11656 840. Patch from rovv.
11657 - Check which hops rendezvous stream cells are associated with to
11658 prevent possible guess-the-streamid injection attacks from
11659 intermediate hops. Fixes another case of bug 446. Based on patch
11661 - If a broken client asks a non-exit router to connect somewhere,
11662 do not even do the DNS lookup before rejecting the connection.
11663 Fixes another case of bug 619. Patch from rovv.
11664 - When a relay gets a create cell it can't decrypt (e.g. because it's
11665 using the wrong onion key), we were dropping it and letting the
11666 client time out. Now actually answer with a destroy cell. Fixes
11667 bug 904. Bugfix on 0.0.2pre8.
11669 o Minor bugfixes (hidden services):
11670 - Do not throw away existing introduction points on SIGHUP. Bugfix on
11671 0.0.6pre1. Patch by Karsten. Fixes bug 874.
11674 - Report the case where all signatures in a detached set are rejected
11675 differently than the case where there is an error handling the
11677 - When we realize that another process has modified our cached
11678 descriptors, print out a more useful error message rather than
11679 triggering an assertion. Fixes bug 885. Patch from Karsten.
11680 - Implement the 0x20 hack to better resist DNS poisoning: set the
11681 case on outgoing DNS requests randomly, and reject responses that do
11682 not match the case correctly. This logic can be disabled with the
11683 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
11684 of servers that do not reliably preserve case in replies. See
11685 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11687 - Check DNS replies for more matching fields to better resist DNS
11689 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11690 compress cells, which are basically all encrypted, compressed, or
11694 Changes in version 0.2.1.11-alpha - 2009-01-20
11695 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
11696 week it will take a long time to bootstrap again" bug. It also fixes
11697 an important security-related bug reported by Ilja van Sprundel. You
11698 should upgrade. (We'll send out more details about the bug once people
11699 have had some time to upgrade.)
11702 - Fix a heap-corruption bug that may be remotely triggerable on
11703 some platforms. Reported by Ilja van Sprundel.
11706 - Discard router descriptors as we load them if they are more than
11707 five days old. Otherwise if Tor is off for a long time and then
11708 starts with cached descriptors, it will try to use the onion
11709 keys in those obsolete descriptors when building circuits. Bugfix
11710 on 0.2.0.x. Fixes bug 887.
11713 - Try to make sure that the version of Libevent we're running with
11714 is binary-compatible with the one we built with. May address bug
11716 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
11717 for bug 905. Bugfix on 0.2.1.7-alpha.
11718 - Add a new --enable-local-appdata configuration switch to change
11719 the default location of the datadir on win32 from APPDATA to
11720 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
11721 entirely. Patch from coderman.
11724 - Make outbound DNS packets respect the OutboundBindAddress setting.
11725 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
11726 - When our circuit fails at the first hop (e.g. we get a destroy
11727 cell back), avoid using that OR connection anymore, and also
11728 tell all the one-hop directory requests waiting for it that they
11729 should fail. Bugfix on 0.2.1.3-alpha.
11730 - In the torify(1) manpage, mention that tsocks will leak your
11734 Changes in version 0.2.1.10-alpha - 2009-01-06
11735 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
11736 would make the bridge relay not so useful if it had DirPort set to 0,
11737 and one that could let an attacker learn a little bit of information
11738 about the bridge's users), and a bug that would cause your Tor relay
11739 to ignore a circuit create request it can't decrypt (rather than reply
11740 with an error). It also fixes a wide variety of other bugs.
11743 - If the cached networkstatus consensus is more than five days old,
11744 discard it rather than trying to use it. In theory it could
11745 be useful because it lists alternate directory mirrors, but in
11746 practice it just means we spend many minutes trying directory
11747 mirrors that are long gone from the network. Helps bug 887 a bit;
11749 - Bridge relays that had DirPort set to 0 would stop fetching
11750 descriptors shortly after startup, and then briefly resume
11751 after a new bandwidth test and/or after publishing a new bridge
11752 descriptor. Bridge users that try to bootstrap from them would
11753 get a recent networkstatus but would get descriptors from up to
11754 18 hours earlier, meaning most of the descriptors were obsolete
11755 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11756 - Prevent bridge relays from serving their 'extrainfo' document
11757 to anybody who asks, now that extrainfo docs include potentially
11758 sensitive aggregated client geoip summaries. Bugfix on
11762 - New controller event "clients_seen" to report a geoip-based summary
11763 of which countries we've seen clients from recently. Now controllers
11764 like Vidalia can show bridge operators that they're actually making
11766 - Build correctly against versions of OpenSSL 0.9.8 or later built
11767 without support for deprecated functions.
11768 - Update to the "December 19 2008" ip-to-country file.
11770 o Minor bugfixes (on 0.2.0.x):
11771 - Authorities now vote for the Stable flag for any router whose
11772 weighted MTBF is at least 5 days, regardless of the mean MTBF.
11773 - Do not remove routers as too old if we do not have any consensus
11774 document. Bugfix on 0.2.0.7-alpha.
11775 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11776 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11777 - When an exit relay resolves a stream address to a local IP address,
11778 do not just keep retrying that same exit relay over and
11779 over. Instead, just close the stream. Addresses bug 872. Bugfix
11780 on 0.2.0.32. Patch from rovv.
11781 - If a hidden service sends us an END cell, do not consider
11782 retrying the connection; just close it. Patch from rovv.
11783 - When we made bridge authorities stop serving bridge descriptors over
11784 unencrypted links, we also broke DirPort reachability testing for
11785 bridges. So bridges with a non-zero DirPort were printing spurious
11786 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
11787 - When a relay gets a create cell it can't decrypt (e.g. because it's
11788 using the wrong onion key), we were dropping it and letting the
11789 client time out. Now actually answer with a destroy cell. Fixes
11790 bug 904. Bugfix on 0.0.2pre8.
11791 - Squeeze 2-5% out of client performance (according to oprofile) by
11792 improving the implementation of some policy-manipulation functions.
11794 o Minor bugfixes (on 0.2.1.x):
11795 - Make get_interface_address() function work properly again; stop
11796 guessing the wrong parts of our address as our address.
11797 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
11798 send on that circuit. Otherwise we might violate the proposal-110
11799 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
11801 - When we're sending non-EXTEND cells to the first hop in a circuit,
11802 for example to use an encrypted directory connection, we don't need
11803 to use RELAY_EARLY cells: the first hop knows what kind of cell
11804 it is, and nobody else can even see the cell type. Conserving
11805 RELAY_EARLY cells makes it easier to cannibalize circuits like
11807 - Stop logging nameserver addresses in reverse order.
11808 - If we are retrying a directory download slowly over and over, do
11809 not automatically give up after the 254th failure. Bugfix on
11811 - Resume reporting accurate "stream end" reasons to the local control
11812 port. They were lost in the changes for Proposal 148. Bugfix on
11815 o Deprecated and removed features:
11816 - The old "tor --version --version" command, which would print out
11817 the subversion "Id" of most of the source files, is now removed. It
11818 turned out to be less useful than we'd expected, and harder to
11821 o Code simplifications and refactoring:
11822 - Change our header file guard macros to be less likely to conflict
11823 with system headers. Adam Langley noticed that we were conflicting
11824 with log.h on Android.
11825 - Tool-assisted documentation cleanup. Nearly every function or
11826 static variable in Tor should have its own documentation now.
11829 Changes in version 0.2.1.9-alpha - 2008-12-25
11830 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
11832 o New directory authorities:
11833 - gabelmoo (the authority run by Karsten Loesing) now has a new
11837 - Never use a connection with a mismatched address to extend a
11838 circuit, unless that connection is canonical. A canonical
11839 connection is one whose address is authenticated by the router's
11840 identity key, either in a NETINFO cell or in a router descriptor.
11841 - Avoid a possible memory corruption bug when receiving hidden service
11842 descriptors. Bugfix on 0.2.1.6-alpha.
11845 - Fix a logic error that would automatically reject all but the first
11846 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
11847 part of bug 813/868. Bug spotted by coderman.
11848 - When a stream at an exit relay is in state "resolving" or
11849 "connecting" and it receives an "end" relay cell, the exit relay
11850 would silently ignore the end cell and not close the stream. If
11851 the client never closes the circuit, then the exit relay never
11852 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
11853 reported by "wood".
11854 - When we can't initialize DNS because the network is down, do not
11855 automatically stop Tor from starting. Instead, retry failed
11856 dns_init() every 10 minutes, and change the exit policy to reject
11857 *:* until one succeeds. Fixes bug 691.
11860 - Give a better error message when an overzealous init script says
11861 "sudo -u username tor --user username". Makes Bug 882 easier for
11863 - When a directory authority gives us a new guess for our IP address,
11864 log which authority we used. Hopefully this will help us debug
11865 the recent complaints about bad IP address guesses.
11866 - Detect svn revision properly when we're using git-svn.
11867 - Try not to open more than one descriptor-downloading connection
11868 to an authority at once. This should reduce load on directory
11869 authorities. Fixes bug 366.
11870 - Add cross-certification to newly generated certificates, so that
11871 a signing key is enough information to look up a certificate.
11872 Partial implementation of proposal 157.
11873 - Start serving certificates by <identity digest, signing key digest>
11874 pairs. Partial implementation of proposal 157.
11875 - Clients now never report any stream end reason except 'MISC'.
11876 Implements proposal 148.
11877 - On platforms with a maximum syslog string length, truncate syslog
11878 messages to that length ourselves, rather than relying on the
11879 system to do it for us.
11880 - Optimize out calls to time(NULL) that occur for every IO operation,
11881 or for every cell. On systems where time() is a slow syscall,
11882 this fix will be slightly helpful.
11883 - Exit servers can now answer resolve requests for ip6.arpa addresses.
11884 - When we download a descriptor that we then immediately (as
11885 a directory authority) reject, do not retry downloading it right
11886 away. Should save some bandwidth on authorities. Fix for bug
11887 888. Patch by Sebastian Hahn.
11888 - When a download gets us zero good descriptors, do not notify
11889 Tor that new directory information has arrived.
11890 - Avoid some nasty corner cases in the logic for marking connections
11891 as too old or obsolete or noncanonical for circuits. Partial
11894 o Minor features (controller):
11895 - New CONSENSUS_ARRIVED event to note when a new consensus has
11896 been fetched and validated.
11897 - When we realize that another process has modified our cached
11898 descriptors file, print out a more useful error message rather
11899 than triggering an assertion. Fixes bug 885. Patch from Karsten.
11900 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
11901 controllers to prevent SIGHUP from reloading the
11902 configuration. Fixes bug 856.
11905 - Resume using the correct "REASON=" stream when telling the
11906 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
11907 - When a canonical connection appears later in our internal list
11908 than a noncanonical one for a given OR ID, always use the
11909 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
11911 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11912 seconds. Warn the user if lower values are given in the
11913 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11914 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11915 user if lower values are given in the configuration. Bugfix on
11916 0.1.1.17-rc. Patch by Sebastian.
11917 - Fix a race condition when freeing keys shared between main thread
11918 and CPU workers that could result in a memory leak. Bugfix on
11919 0.1.0.1-rc. Fixes bug 889.
11921 o Minor bugfixes (hidden services):
11922 - Do not throw away existing introduction points on SIGHUP (bugfix on
11923 0.0.6pre1); also, do not stall hidden services because we're
11924 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
11925 by John Brooks. Patch by Karsten. Fixes bug 874.
11926 - Fix a memory leak when we decline to add a v2 rendezvous
11927 descriptor to the cache because we already had a v0 descriptor
11928 with the same ID. Bugfix on 0.2.0.18-alpha.
11930 o Deprecated and removed features:
11931 - RedirectExits has been removed. It was deprecated since
11933 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
11934 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
11935 - Cell pools are now always enabled; --disable-cell-pools is ignored.
11937 o Code simplifications and refactoring:
11938 - Rename the confusing or_is_obsolete field to the more appropriate
11939 is_bad_for_new_circs, and move it to or_connection_t where it
11941 - Move edge-only flags from connection_t to edge_connection_t: not
11942 only is this better coding, but on machines of plausible alignment,
11943 it should save 4-8 bytes per connection_t. "Every little bit helps."
11944 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
11945 for consistency; keep old option working for backward compatibility.
11946 - Simplify the code for finding connections to use for a circuit.
11949 Changes in version 0.2.1.8-alpha - 2008-12-08
11950 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
11951 builds better on unusual platforms like Solaris and old OS X, and
11952 fixes a variety of other issues.
11955 - New DirPortFrontPage option that takes an html file and publishes
11956 it as "/" on the DirPort. Now relay operators can provide a
11957 disclaimer without needing to set up a separate webserver. There's
11958 a sample disclaimer in contrib/tor-exit-notice.html.
11961 - When the client is choosing entry guards, now it selects at most
11962 one guard from a given relay family. Otherwise we could end up with
11963 all of our entry points into the network run by the same operator.
11964 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11967 - Fix a DOS opportunity during the voting signature collection process
11968 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11969 - Fix a possible segfault when establishing an exit connection. Bugfix
11973 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
11975 - Made Tor a little less aggressive about deleting expired
11976 certificates. Partial fix for bug 854.
11977 - Stop doing unaligned memory access that generated bus errors on
11978 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
11979 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
11980 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
11981 - Make USR2 log-level switch take effect immediately. Bugfix on
11983 - If one win32 nameserver fails to get added, continue adding the
11984 rest, and don't automatically fail.
11985 - Use fcntl() for locking when flock() is not available. Should fix
11986 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
11987 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11988 could make gcc generate non-functional binary search code. Bugfix
11990 - Build correctly on platforms without socklen_t.
11991 - Avoid potential crash on internal error during signature collection.
11992 Fixes bug 864. Patch from rovv.
11993 - Do not use C's stdio library for writing to log files. This will
11994 improve logging performance by a minute amount, and will stop
11995 leaking fds when our disk is full. Fixes bug 861.
11996 - Stop erroneous use of O_APPEND in cases where we did not in fact
11997 want to re-seek to the end of a file before every last write().
11998 - Correct handling of possible malformed authority signing key
11999 certificates with internal signature types. Fixes bug 880. Bugfix
12001 - Fix a hard-to-trigger resource leak when logging credential status.
12005 - Directory mirrors no longer fetch the v1 directory or
12006 running-routers files. They are obsolete, and nobody asks for them
12007 anymore. This is the first step to making v1 authorities obsolete.
12009 o Minor features (controller):
12010 - Return circuit purposes in response to GETINFO circuit-status. Fixes
12014 Changes in version 0.2.0.32 - 2008-11-20
12015 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
12016 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12017 a smaller security flaw that might allow an attacker to access local
12018 services, further improves hidden service performance, and fixes a
12019 variety of other issues.
12022 - The "User" and "Group" config options did not clear the
12023 supplementary group entries for the Tor process. The "User" option
12024 is now more robust, and we now set the groups to the specified
12025 user's primary group. The "Group" option is now ignored. For more
12026 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12027 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12028 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
12029 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12030 consistently obeyed: if an exit relay refuses a stream because its
12031 exit policy doesn't allow it, we would remember what IP address
12032 the relay said the destination address resolves to, even if it's
12033 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12036 - Fix a DOS opportunity during the voting signature collection process
12037 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12039 o Major bugfixes (hidden services):
12040 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12041 we were failing the whole hidden service request when the v0
12042 descriptor fetch fails, even if the v2 fetch is still pending and
12043 might succeed. Similarly, if the last v2 fetch fails, we were
12044 failing the whole hidden service request even if a v0 fetch is
12045 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12046 - When extending a circuit to a hidden service directory to upload a
12047 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12048 requests failed, because the router descriptor has not been
12049 downloaded yet. In these cases, do not attempt to upload the
12050 rendezvous descriptor, but wait until the router descriptor is
12051 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12052 descriptor from a hidden service directory for which the router
12053 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
12057 - Fix several infrequent memory leaks spotted by Coverity.
12058 - When testing for libevent functions, set the LDFLAGS variable
12059 correctly. Found by Riastradh.
12060 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12061 bootstrapping with tunneled directory connections. Bugfix on
12062 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12063 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12064 and we know that server B rejects most-but-not all connections to
12065 port 80, we would previously reject the connection. Now, we assume
12066 the user knows what they were asking for. Fixes bug 752. Bugfix
12067 on 0.0.9rc5. Diagnosed by BarkerJr.
12068 - If we overrun our per-second write limits a little, count this as
12069 having used up our write allocation for the second, and choke
12070 outgoing directory writes. Previously, we had only counted this when
12071 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
12072 Bugfix on 0.2.0.x (??).
12073 - Remove the old v2 directory authority 'lefkada' from the default
12074 list. It has been gone for many months.
12075 - Stop doing unaligned memory access that generated bus errors on
12076 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
12077 - Make USR2 log-level switch take effect immediately. Bugfix on
12080 o Minor bugfixes (controller):
12081 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
12082 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
12085 Changes in version 0.2.1.7-alpha - 2008-11-08
12086 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
12087 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12088 a smaller security flaw that might allow an attacker to access local
12089 services, adds better defense against DNS poisoning attacks on exit
12090 relays, further improves hidden service performance, and fixes a
12091 variety of other issues.
12094 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12095 consistently obeyed: if an exit relay refuses a stream because its
12096 exit policy doesn't allow it, we would remember what IP address
12097 the relay said the destination address resolves to, even if it's
12098 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12099 - The "User" and "Group" config options did not clear the
12100 supplementary group entries for the Tor process. The "User" option
12101 is now more robust, and we now set the groups to the specified
12102 user's primary group. The "Group" option is now ignored. For more
12103 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12104 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12105 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
12106 - Do not use or believe expired v3 authority certificates. Patch
12107 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
12110 - Now NodeFamily and MyFamily config options allow spaces in
12111 identity fingerprints, so it's easier to paste them in.
12112 Suggested by Lucky Green.
12113 - Implement the 0x20 hack to better resist DNS poisoning: set the
12114 case on outgoing DNS requests randomly, and reject responses that do
12115 not match the case correctly. This logic can be disabled with the
12116 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
12117 of servers that do not reliably preserve case in replies. See
12118 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12120 - Preserve case in replies to DNSPort requests in order to support
12121 the 0x20 hack for resisting DNS poisoning attacks.
12123 o Hidden service performance improvements:
12124 - When the client launches an introduction circuit, retry with a
12125 new circuit after 30 seconds rather than 60 seconds.
12126 - Launch a second client-side introduction circuit in parallel
12127 after a delay of 15 seconds (based on work by Christian Wilms).
12128 - Hidden services start out building five intro circuits rather
12129 than three, and when the first three finish they publish a service
12130 descriptor using those. Now we publish our service descriptor much
12131 faster after restart.
12134 - Minor fix in the warning messages when you're having problems
12135 bootstrapping; also, be more forgiving of bootstrap problems when
12136 we're still making incremental progress on a given bootstrap phase.
12137 - When we're choosing an exit node for a circuit, and we have
12138 no pending streams, choose a good general exit rather than one that
12139 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12140 - Send a valid END cell back when a client tries to connect to a
12141 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12142 840. Patch from rovv.
12143 - If a broken client asks a non-exit router to connect somewhere,
12144 do not even do the DNS lookup before rejecting the connection.
12145 Fixes another case of bug 619. Patch from rovv.
12146 - Fix another case of assuming, when a specific exit is requested,
12147 that we know more than the user about what hosts it allows.
12148 Fixes another case of bug 752. Patch from rovv.
12149 - Check which hops rendezvous stream cells are associated with to
12150 prevent possible guess-the-streamid injection attacks from
12151 intermediate hops. Fixes another case of bug 446. Based on patch
12153 - Avoid using a negative right-shift when comparing 32-bit
12154 addresses. Possible fix for bug 845 and bug 811.
12155 - Make the assert_circuit_ok() function work correctly on circuits that
12156 have already been marked for close.
12157 - Fix read-off-the-end-of-string error in unit tests when decoding
12158 introduction points.
12159 - Fix uninitialized size field for memory area allocation: may improve
12160 memory performance during directory parsing.
12161 - Treat duplicate certificate fetches as failures, so that we do
12162 not try to re-fetch an expired certificate over and over and over.
12163 - Do not say we're fetching a certificate when we'll in fact skip it
12164 because of a pending download.
12167 Changes in version 0.2.1.6-alpha - 2008-09-30
12168 Tor 0.2.1.6-alpha further improves performance and robustness of
12169 hidden services, starts work on supporting per-country relay selection,
12170 and fixes a variety of smaller issues.
12173 - Implement proposal 121: make it possible to build hidden services
12174 that only certain clients are allowed to connect to. This is
12175 enforced at several points, so that unauthorized clients are unable
12176 to send INTRODUCE cells to the service, or even (depending on the
12177 type of authentication) to learn introduction points. This feature
12178 raises the bar for certain kinds of active attacks against hidden
12179 services. Code by Karsten Loesing.
12180 - Relays now store and serve v2 hidden service descriptors by default,
12181 i.e., the new default value for HidServDirectoryV2 is 1. This is
12182 the last step in proposal 114, which aims to make hidden service
12183 lookups more reliable.
12184 - Start work to allow node restrictions to include country codes. The
12185 syntax to exclude nodes in a country with country code XX is
12186 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
12187 refinement to decide what config options should take priority if
12188 you ask to both use a particular node and exclude it.
12189 - Allow ExitNodes list to include IP ranges and country codes, just
12190 like the Exclude*Nodes lists. Patch from Robert Hogan.
12193 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
12194 Tor to fail to start if you had it configured to use a bridge
12195 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
12196 - When extending a circuit to a hidden service directory to upload a
12197 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12198 requests failed, because the router descriptor had not been
12199 downloaded yet. In these cases, we now wait until the router
12200 descriptor is downloaded, and then retry. Likewise, clients
12201 now skip over a hidden service directory if they don't yet have
12202 its router descriptor, rather than futilely requesting it and
12203 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
12205 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12206 we were failing the whole hidden service request when the v0
12207 descriptor fetch fails, even if the v2 fetch is still pending and
12208 might succeed. Similarly, if the last v2 fetch fails, we were
12209 failing the whole hidden service request even if a v0 fetch is
12210 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12211 - DNS replies need to have names matching their requests, but
12212 these names should be in the questions section, not necessarily
12213 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
12216 - Update to the "September 1 2008" ip-to-country file.
12217 - Allow ports 465 and 587 in the default exit policy again. We had
12218 rejected them in 0.1.0.15, because back in 2005 they were commonly
12219 misconfigured and ended up as spam targets. We hear they are better
12220 locked down these days.
12221 - Use a lockfile to make sure that two Tor processes are not
12222 simultaneously running with the same datadir.
12223 - Serve the latest v3 networkstatus consensus via the control
12224 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
12225 - Better logging about stability/reliability calculations on directory
12227 - Drop the requirement to have an open dir port for storing and
12228 serving v2 hidden service descriptors.
12229 - Directory authorities now serve a /tor/dbg-stability.txt URL to
12230 help debug WFU and MTBF calculations.
12231 - Implement most of Proposal 152: allow specialized servers to permit
12232 single-hop circuits, and clients to use those servers to build
12233 single-hop circuits when using a specialized controller. Patch
12234 from Josh Albrecht. Resolves feature request 768.
12235 - Add a -p option to tor-resolve for specifying the SOCKS port: some
12236 people find host:port too confusing.
12237 - Make TrackHostExit mappings expire a while after their last use, not
12238 after their creation. Patch from Robert Hogan.
12239 - Provide circuit purposes along with circuit events to the controller.
12242 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
12244 - Fixed some memory leaks -- some quite frequent, some almost
12245 impossible to trigger -- based on results from Coverity.
12246 - When testing for libevent functions, set the LDFLAGS variable
12247 correctly. Found by Riastradh.
12248 - Fix an assertion bug in parsing policy-related options; possible fix
12250 - Catch and report a few more bootstrapping failure cases when Tor
12251 fails to establish a TCP connection. Cleanup on 0.2.1.x.
12252 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12253 bootstrapping with tunneled directory connections. Bugfix on
12254 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12255 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12256 and we know that server B rejects most-but-not all connections to
12257 port 80, we would previously reject the connection. Now, we assume
12258 the user knows what they were asking for. Fixes bug 752. Bugfix
12259 on 0.0.9rc5. Diagnosed by BarkerJr.
12260 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
12261 service directories if they have no advertised dir port. Bugfix
12263 - If we overrun our per-second write limits a little, count this as
12264 having used up our write allocation for the second, and choke
12265 outgoing directory writes. Previously, we had only counted this when
12266 we had met our limits precisely. Fixes bug 824. Patch by rovv.
12267 Bugfix on 0.2.0.x (??).
12268 - Avoid a "0 divided by 0" calculation when calculating router uptime
12269 at directory authorities. Bugfix on 0.2.0.8-alpha.
12270 - Make DNS resolved controller events into "CLOSED", not
12271 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
12273 - Fix a bug where an unreachable relay would establish enough
12274 reachability testing circuits to do a bandwidth test -- if
12275 we already have a connection to the middle hop of the testing
12276 circuit, then it could establish the last hop by using the existing
12277 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
12278 circuits no longer use entry guards in 0.2.1.3-alpha.
12279 - If we have correct permissions on $datadir, we complain to stdout
12280 and fail to start. But dangerous permissions on
12281 $datadir/cached-status/ would cause us to open a log and complain
12282 there. Now complain to stdout and fail to start in both cases. Fixes
12283 bug 820, reported by seeess.
12284 - Remove the old v2 directory authority 'lefkada' from the default
12285 list. It has been gone for many months.
12287 o Code simplifications and refactoring:
12288 - Revise the connection_new functions so that a more typesafe variant
12289 exists. This will work better with Coverity, and let us find any
12290 actual mistakes we're making here.
12291 - Refactor unit testing logic so that dmalloc can be used sensibly
12292 with unit tests to check for memory leaks.
12293 - Move all hidden-service related fields from connection and circuit
12294 structure to substructures: this way they won't eat so much memory.
12297 Changes in version 0.2.0.31 - 2008-09-03
12298 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
12299 a big bug we're seeing where in rare cases traffic from one Tor stream
12300 gets mixed into another stream, and fixes a variety of smaller issues.
12303 - Make sure that two circuits can never exist on the same connection
12304 with the same circuit ID, even if one is marked for close. This
12305 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
12306 - Relays now reject risky extend cells: if the extend cell includes
12307 a digest of all zeroes, or asks to extend back to the relay that
12308 sent the extend cell, tear down the circuit. Ideas suggested
12310 - If not enough of our entry guards are available so we add a new
12311 one, we might use the new one even if it overlapped with the
12312 current circuit's exit relay (or its family). Anonymity bugfix
12313 pointed out by rovv.
12316 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12317 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12318 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12319 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12320 - Pick size of default geoip filename string correctly on windows.
12321 Fixes bug 806. Bugfix on 0.2.0.30.
12322 - Make the autoconf script accept the obsolete --with-ssl-dir
12323 option as an alias for the actually-working --with-openssl-dir
12324 option. Fix the help documentation to recommend --with-openssl-dir.
12325 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12326 - When using the TransPort option on OpenBSD, and using the User
12327 option to change UID and drop privileges, make sure to open
12328 /dev/pf before dropping privileges. Fixes bug 782. Patch from
12329 Christopher Davis. Bugfix on 0.1.2.1-alpha.
12330 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12331 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12332 on the client side when connecting to a hidden service. Bugfix
12333 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12334 - When closing an application-side connection because its circuit is
12335 getting torn down, generate the stream event correctly. Bugfix on
12336 0.1.2.x. Anonymous patch.
12339 Changes in version 0.2.1.5-alpha - 2008-08-31
12340 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
12341 in a lot of the infrastructure for adding authorization to hidden
12342 services, lays the groundwork for having clients read their load
12343 balancing information out of the networkstatus consensus rather than
12344 the individual router descriptors, addresses two potential anonymity
12345 issues, and fixes a variety of smaller issues.
12348 - Convert many internal address representations to optionally hold
12350 - Generate and accept IPv6 addresses in many protocol elements.
12351 - Make resolver code handle nameservers located at ipv6 addresses.
12352 - Begin implementation of proposal 121 ("Client authorization for
12353 hidden services"): configure hidden services with client
12354 authorization, publish descriptors for them, and configure
12355 authorization data for hidden services at clients. The next
12356 step is to actually access hidden services that perform client
12358 - More progress toward proposal 141: Network status consensus
12359 documents and votes now contain bandwidth information for each
12360 router and a summary of that router's exit policy. Eventually this
12361 will be used by clients so that they do not have to download every
12362 known descriptor before building circuits.
12364 o Major bugfixes (on 0.2.0.x and before):
12365 - When sending CREATED cells back for a given circuit, use a 64-bit
12366 connection ID to find the right connection, rather than an addr:port
12367 combination. Now that we can have multiple OR connections between
12368 the same ORs, it is no longer possible to use addr:port to uniquely
12369 identify a connection.
12370 - Relays now reject risky extend cells: if the extend cell includes
12371 a digest of all zeroes, or asks to extend back to the relay that
12372 sent the extend cell, tear down the circuit. Ideas suggested
12374 - If not enough of our entry guards are available so we add a new
12375 one, we might use the new one even if it overlapped with the
12376 current circuit's exit relay (or its family). Anonymity bugfix
12377 pointed out by rovv.
12380 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12381 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12382 - When using the TransPort option on OpenBSD, and using the User
12383 option to change UID and drop privileges, make sure to open /dev/pf
12384 before dropping privileges. Fixes bug 782. Patch from Christopher
12385 Davis. Bugfix on 0.1.2.1-alpha.
12386 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12387 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12388 - Add a missing safe_str() call for a debug log message.
12389 - Use 64 bits instead of 32 bits for connection identifiers used with
12390 the controller protocol, to greatly reduce risk of identifier reuse.
12391 - Make the autoconf script accept the obsolete --with-ssl-dir
12392 option as an alias for the actually-working --with-openssl-dir
12393 option. Fix the help documentation to recommend --with-openssl-dir.
12394 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12397 - Rate-limit too-many-sockets messages: when they happen, they happen
12398 a lot. Resolves bug 748.
12399 - Resist DNS poisoning a little better by making sure that names in
12400 answer sections match.
12401 - Print the SOCKS5 error message string as well as the error code
12402 when a tor-resolve request fails. Patch from Jacob.
12405 Changes in version 0.2.1.4-alpha - 2008-08-04
12406 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
12409 - The address part of exit policies was not correctly written
12410 to router descriptors. This generated router descriptors that failed
12411 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
12413 - Tor triggered a false assert when extending a circuit to a relay
12414 but we already have a connection open to that relay. Noticed by
12415 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
12418 - Fix a hidden service logging bug: in some edge cases, the router
12419 descriptor of a previously picked introduction point becomes
12420 obsolete and we need to give up on it rather than continually
12421 complaining that it has become obsolete. Observed by xiando. Bugfix
12424 o Removed features:
12425 - Take out the TestVia config option, since it was a workaround for
12426 a bug that was fixed in Tor 0.1.1.21.
12429 Changes in version 0.2.1.3-alpha - 2008-08-03
12430 Tor 0.2.1.3-alpha implements most of the pieces to prevent
12431 infinite-length circuit attacks (see proposal 110); fixes a bug that
12432 might cause exit relays to corrupt streams they send back; allows
12433 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
12434 ExcludeExitNodes config options; and fixes a big pile of bugs.
12436 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
12437 - Send a bootstrap problem "warn" event on the first problem if the
12438 reason is NO_ROUTE (that is, our network is down).
12441 - Implement most of proposal 110: The first K cells to be sent
12442 along a circuit are marked as special "early" cells; only K "early"
12443 cells will be allowed. Once this code is universal, we can block
12444 certain kinds of DOS attack by requiring that EXTEND commands must
12445 be sent using an "early" cell.
12448 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12449 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12450 on the client side when connecting to a hidden service. Bugfix
12451 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12452 - Ensure that two circuits can never exist on the same connection
12453 with the same circuit ID, even if one is marked for close. This
12454 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
12457 - When relays do their initial bandwidth measurement, don't limit
12458 to just our entry guards for the test circuits. Otherwise we tend
12459 to have multiple test circuits going through a single entry guard,
12460 which makes our bandwidth test less accurate. Fixes part of bug 654;
12461 patch contributed by Josh Albrecht.
12462 - Add an ExcludeExitNodes option so users can list a set of nodes
12463 that should be be excluded from the exit node position, but
12464 allowed elsewhere. Implements proposal 151.
12465 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
12466 ExcludeNodes and ExcludeExitNodes lists.
12467 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
12468 be more efficient. Formerly it was quadratic in the number of
12469 servers; now it should be linear. Fixes bug 509.
12470 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
12471 and n_conn_id_digest fields into a separate structure that's
12472 only needed when the circuit has not yet attached to an n_conn.
12475 - Change the contrib/tor.logrotate script so it makes the new
12476 logs as "_tor:_tor" rather than the default, which is generally
12477 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
12478 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12479 warnings (occasionally), but it can also cause the compiler to
12480 eliminate error-checking code. Suggested by Peter Gutmann.
12481 - When a hidden service is giving up on an introduction point candidate
12482 that was not included in the last published rendezvous descriptor,
12483 don't reschedule publication of the next descriptor. Fixes bug 763.
12485 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
12486 HiddenServiceExcludeNodes as obsolete: they never worked properly,
12487 and nobody claims to be using them. Fixes bug 754. Bugfix on
12488 0.1.0.1-rc. Patch from Christian Wilms.
12489 - Fix a small alignment and memory-wasting bug on buffer chunks.
12492 o Minor bugfixes (controller):
12493 - When closing an application-side connection because its circuit
12494 is getting torn down, generate the stream event correctly.
12495 Bugfix on 0.1.2.x. Anonymous patch.
12497 o Removed features:
12498 - Remove all backward-compatibility code to support relays running
12499 versions of Tor so old that they no longer work at all on the
12503 Changes in version 0.2.0.30 - 2008-07-15
12505 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12506 warnings (occasionally), but it can also cause the compiler to
12507 eliminate error-checking code. Suggested by Peter Gutmann.
12510 Changes in version 0.2.0.29-rc - 2008-07-08
12511 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
12512 hidden-service performance bugs, and fixes a bunch of smaller bugs.
12515 - If you have more than one bridge but don't know their keys,
12516 you would only launch a request for the descriptor of the first one
12517 on your list. (Tor considered launching requests for the others, but
12518 found that it already had a connection on the way for $0000...0000
12519 so it didn't open another.) Bugfix on 0.2.0.x.
12520 - If you have more than one bridge but don't know their keys, and the
12521 connection to one of the bridges failed, you would cancel all
12522 pending bridge connections. (After all, they all have the same
12523 digest.) Bugfix on 0.2.0.x.
12524 - When a hidden service was trying to establish an introduction point,
12525 and Tor had built circuits preemptively for such purposes, we
12526 were ignoring all the preemptive circuits and launching a new one
12527 instead. Bugfix on 0.2.0.14-alpha.
12528 - When a hidden service was trying to establish an introduction point,
12529 and Tor *did* manage to reuse one of the preemptively built
12530 circuits, it didn't correctly remember which one it used,
12531 so it asked for another one soon after, until there were no
12532 more preemptive circuits, at which point it launched one from
12533 scratch. Bugfix on 0.0.9.x.
12534 - Make directory servers include the X-Your-Address-Is: http header in
12535 their responses even for begin_dir conns. Now clients who only
12536 ever use begin_dir connections still have a way to learn their IP
12537 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
12540 - Fix a macro/CPP interaction that was confusing some compilers:
12541 some GCCs don't like #if/#endif pairs inside macro arguments.
12543 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
12544 Fixes bug 704; fix from Steven Murdoch.
12545 - When opening /dev/null in finish_daemonize(), do not pass the
12546 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
12547 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
12548 - Correctly detect transparent proxy support on Linux hosts that
12549 require in.h to be included before netfilter_ipv4.h. Patch
12551 - Disallow session resumption attempts during the renegotiation
12552 stage of the v2 handshake protocol. Clients should never be trying
12553 session resumption at this point, but apparently some did, in
12554 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
12555 found by Geoff Goodell.
12558 Changes in version 0.2.1.2-alpha - 2008-06-20
12559 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
12560 make it easier to set up your own private Tor network; fixes several
12561 big bugs with using more than one bridge relay; fixes a big bug with
12562 offering hidden services quickly after Tor starts; and uses a better
12563 API for reporting potential bootstrapping problems to the controller.
12566 - New TestingTorNetwork config option to allow adjustment of
12567 previously constant values that, while reasonable, could slow
12568 bootstrapping. Implements proposal 135. Patch from Karsten.
12571 - If you have more than one bridge but don't know their digests,
12572 you would only learn a request for the descriptor of the first one
12573 on your list. (Tor considered launching requests for the others, but
12574 found that it already had a connection on the way for $0000...0000
12575 so it didn't open another.) Bugfix on 0.2.0.x.
12576 - If you have more than one bridge but don't know their digests,
12577 and the connection to one of the bridges failed, you would cancel
12578 all pending bridge connections. (After all, they all have the
12579 same digest.) Bugfix on 0.2.0.x.
12580 - When establishing a hidden service, introduction points that
12581 originate from cannibalized circuits are completely ignored and not
12582 included in rendezvous service descriptors. This might be another
12583 reason for delay in making a hidden service available. Bugfix
12584 from long ago (0.0.9.x?)
12587 - Allow OpenSSL to use dynamic locks if it wants.
12588 - When building a consensus, do not include routers that are down.
12589 This will cut down 30% to 40% on consensus size. Implements
12591 - In directory authorities' approved-routers files, allow
12592 fingerprints with or without space.
12593 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
12594 controller can query our current bootstrap state in case it attaches
12595 partway through and wants to catch up.
12596 - Send an initial "Starting" bootstrap status event, so we have a
12597 state to start out in.
12600 - Asking for a conditional consensus at .../consensus/<fingerprints>
12601 would crash a dirserver if it did not already have a
12602 consensus. Bugfix on 0.2.1.1-alpha.
12603 - Clean up some macro/CPP interactions: some GCC versions don't like
12604 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
12607 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
12608 - Directory authorities shouldn't complain about bootstrapping
12609 problems just because they do a lot of reachability testing and
12610 some of the connection attempts fail.
12611 - Start sending "count" and "recommendation" key/value pairs in
12612 bootstrap problem status events, so the controller can hear about
12613 problems even before Tor decides they're worth reporting for sure.
12614 - If you're using bridges, generate "bootstrap problem" warnings
12615 as soon as you run out of working bridges, rather than waiting
12616 for ten failures -- which will never happen if you have less than
12618 - If we close our OR connection because there's been a circuit
12619 pending on it for too long, we were telling our bootstrap status
12620 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
12623 Changes in version 0.2.1.1-alpha - 2008-06-13
12624 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
12625 were making the Tor process bloat especially on Linux; makes our TLS
12626 handshake blend in better; sends "bootstrap phase" status events to
12627 the controller, so it can keep the user informed of progress (and
12628 problems) fetching directory information and establishing circuits;
12629 and adds a variety of smaller features.
12632 - More work on making our TLS handshake blend in: modify the list
12633 of ciphers advertised by OpenSSL in client mode to even more
12634 closely resemble a common web browser. We cheat a little so that
12635 we can advertise ciphers that the locally installed OpenSSL doesn't
12637 - Start sending "bootstrap phase" status events to the controller,
12638 so it can keep the user informed of progress fetching directory
12639 information and establishing circuits. Also inform the controller
12640 if we think we're stuck at a particular bootstrap phase. Implements
12642 - Resume using OpenSSL's RAND_poll() for better (and more portable)
12643 cross-platform entropy collection again. We used to use it, then
12644 stopped using it because of a bug that could crash systems that
12645 called RAND_poll when they had a lot of fds open. It looks like the
12646 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
12647 at startup, and to call RAND_poll() when we reseed later only if
12648 we have a non-buggy OpenSSL version.
12651 - When we choose to abandon a new entry guard because we think our
12652 older ones might be better, close any circuits pending on that
12653 new entry guard connection. This fix should make us recover much
12654 faster when our network is down and then comes back. Bugfix on
12655 0.1.2.8-beta; found by lodger.
12657 o Memory fixes and improvements:
12658 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
12659 to avoid unused RAM in buffer chunks and memory pools.
12660 - Speed up parsing and cut down on memory fragmentation by using
12661 stack-style allocations for parsing directory objects. Previously,
12662 this accounted for over 40% of allocations from within Tor's code
12663 on a typical directory cache.
12664 - Use a Bloom filter rather than a digest-based set to track which
12665 descriptors we need to keep around when we're cleaning out old
12666 router descriptors. This speeds up the computation significantly,
12667 and may reduce fragmentation.
12668 - Reduce the default smartlist size from 32 to 16; it turns out that
12669 most smartlists hold around 8-12 elements tops.
12670 - Make dumpstats() log the fullness and size of openssl-internal
12672 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
12673 patch to their OpenSSL, turn it on to save memory on servers. This
12674 patch will (with any luck) get included in a mainline distribution
12676 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12677 compress cells, which are basically all encrypted, compressed,
12681 - Stop reloading the router list from disk for no reason when we
12682 run out of reachable directory mirrors. Once upon a time reloading
12683 it would set the 'is_running' flag back to 1 for them. It hasn't
12684 done that for a long time.
12685 - In very rare situations new hidden service descriptors were
12686 published earlier than 30 seconds after the last change to the
12687 service. (We currently think that a hidden service descriptor
12688 that's been stable for 30 seconds is worth publishing.)
12691 - Allow separate log levels to be configured for different logging
12692 domains. For example, this allows one to log all notices, warnings,
12693 or errors, plus all memory management messages of level debug or
12694 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
12695 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
12696 and stop using a warning that had become unfixably verbose under
12698 - New --hush command-line option similar to --quiet. While --quiet
12699 disables all logging to the console on startup, --hush limits the
12700 output to messages of warning and error severity.
12701 - Servers support a new URL scheme for consensus downloads that
12702 allows the client to specify which authorities are trusted.
12703 The server then only sends the consensus if the client will trust
12704 it. Otherwise a 404 error is sent back. Clients use this
12705 new scheme when the server supports it (meaning it's running
12706 0.2.1.1-alpha or later). Implements proposal 134.
12707 - New configure/torrc options (--enable-geoip-stats,
12708 DirRecordUsageByCountry) to record how many IPs we've served
12709 directory info to in each country code, how many status documents
12710 total we've sent to each country code, and what share of the total
12711 directory requests we should expect to see.
12712 - Use the TLS1 hostname extension to more closely resemble browser
12714 - Lots of new unit tests.
12715 - Add a macro to implement the common pattern of iterating through
12716 two parallel lists in lockstep.
12719 Changes in version 0.2.0.28-rc - 2008-06-13
12720 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
12721 performance bug, and fixes a bunch of smaller bugs.
12724 - Fix a bug where, when we were choosing the 'end stream reason' to
12725 put in our relay end cell that we send to the exit relay, Tor
12726 clients on Windows were sometimes sending the wrong 'reason'. The
12727 anonymity problem is that exit relays may be able to guess whether
12728 the client is running Windows, thus helping partition the anonymity
12729 set. Down the road we should stop sending reasons to exit relays,
12730 or otherwise prevent future versions of this bug.
12733 - While setting up a hidden service, some valid introduction circuits
12734 were overlooked and abandoned. This might be the reason for
12735 the long delay in making a hidden service available. Bugfix on
12739 - Update to the "June 9 2008" ip-to-country file.
12740 - Run 'make test' as part of 'make dist', so we stop releasing so
12741 many development snapshots that fail their unit tests.
12744 - When we're checking if we have enough dir info for each relay
12745 to begin establishing circuits, make sure that we actually have
12746 the descriptor listed in the consensus, not just any descriptor.
12748 - Bridge relays no longer print "xx=0" in their extrainfo document
12749 for every single country code in the geoip db. Bugfix on
12751 - Only warn when we fail to load the geoip file if we were planning to
12752 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
12753 - If we change our MaxAdvertisedBandwidth and then reload torrc,
12754 Tor won't realize it should publish a new relay descriptor. Fixes
12755 bug 688, reported by mfr. Bugfix on 0.1.2.x.
12756 - When we haven't had any application requests lately, don't bother
12757 logging that we have expired a bunch of descriptors. Bugfix
12759 - Make relay cells written on a connection count as non-padding when
12760 tracking how long a connection has been in use. Bugfix on
12761 0.2.0.1-alpha. Spotted by lodger.
12762 - Fix unit tests in 0.2.0.27-rc.
12763 - Fix compile on Windows.
12766 Changes in version 0.2.0.27-rc - 2008-06-03
12767 Tor 0.2.0.27-rc adds a few features we left out of the earlier
12768 release candidates. In particular, we now include an IP-to-country
12769 GeoIP database, so controllers can easily look up what country a
12770 given relay is in, and so bridge relays can give us some sanitized
12771 summaries about which countries are making use of bridges. (See proposal
12772 126-geoip-fetching.txt for details.)
12775 - Include an IP-to-country GeoIP file in the tarball, so bridge
12776 relays can report sanitized summaries of the usage they're seeing.
12779 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
12780 Robert Hogan. Fixes the first part of bug 681.
12781 - Make bridge authorities never serve extrainfo docs.
12782 - Add support to detect Libevent versions in the 1.4.x series
12784 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
12785 - Include a new contrib/tor-exit-notice.html file that exit relay
12786 operators can put on their website to help reduce abuse queries.
12789 - When tunneling an encrypted directory connection, and its first
12790 circuit fails, do not leave it unattached and ask the controller
12791 to deal. Fixes the second part of bug 681.
12792 - Make bridge authorities correctly expire old extrainfo documents
12796 Changes in version 0.2.0.26-rc - 2008-05-13
12797 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
12798 in Debian's OpenSSL packages. All users running any 0.2.0.x version
12799 should upgrade, whether they're running Debian or not.
12801 o Major security fixes:
12802 - Use new V3 directory authority keys on the tor26, gabelmoo, and
12803 moria1 V3 directory authorities. The old keys were generated with
12804 a vulnerable version of Debian's OpenSSL package, and must be
12805 considered compromised. Other authorities' keys were not generated
12806 with an affected version of OpenSSL.
12809 - List authority signatures as "unrecognized" based on DirServer
12810 lines, not on cert cache. Bugfix on 0.2.0.x.
12813 - Add a new V3AuthUseLegacyKey option to make it easier for
12814 authorities to change their identity keys if they have to.
12817 Changes in version 0.2.0.25-rc - 2008-04-23
12818 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
12821 - Remember to initialize threading before initializing logging.
12822 Otherwise, many BSD-family implementations will crash hard on
12823 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
12826 - Authorities correctly free policies on bad servers on
12827 exit. Fixes bug 672. Bugfix on 0.2.0.x.
12830 Changes in version 0.2.0.24-rc - 2008-04-22
12831 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
12832 v3 directory authority, makes relays with dynamic IP addresses and no
12833 DirPort notice more quickly when their IP address changes, fixes a few
12834 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
12836 o New directory authorities:
12837 - Take lefkada out of the list of v3 directory authorities, since
12838 it has been down for months.
12839 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
12843 - Detect address changes more quickly on non-directory mirror
12844 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
12846 o Minor features (security):
12847 - Reject requests for reverse-dns lookup of names that are in
12848 a private address space. Patch from lodger.
12849 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
12852 o Minor bugfixes (crashes):
12853 - Avoid a rare assert that can trigger when Tor doesn't have much
12854 directory information yet and it tries to fetch a v2 hidden
12855 service descriptor. Fixes bug 651, reported by nwf.
12856 - Initialize log mutex before initializing dmalloc. Otherwise,
12857 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
12858 - Use recursive pthread mutexes in order to avoid deadlock when
12859 logging debug-level messages to a controller. Bug spotted by nwf,
12860 bugfix on 0.2.0.16-alpha.
12862 o Minor bugfixes (resource management):
12863 - Keep address policies from leaking memory: start their refcount
12864 at 1, not 2. Bugfix on 0.2.0.16-alpha.
12865 - Free authority certificates on exit, so they don't look like memory
12866 leaks. Bugfix on 0.2.0.19-alpha.
12867 - Free static hashtables for policy maps and for TLS connections on
12868 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
12869 - Avoid allocating extra space when computing consensuses on 64-bit
12870 platforms. Bug spotted by aakova.
12872 o Minor bugfixes (misc):
12873 - Do not read the configuration file when we've only been told to
12874 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
12875 based on patch from Sebastian Hahn.
12876 - Exit relays that are used as a client can now reach themselves
12877 using the .exit notation, rather than just launching an infinite
12878 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
12879 - When attempting to open a logfile fails, tell us why.
12880 - Fix a dumb bug that was preventing us from knowing that we should
12881 preemptively build circuits to handle expected directory requests.
12882 Fixes bug 660. Bugfix on 0.1.2.x.
12883 - Warn less verbosely about clock skew from netinfo cells from
12884 untrusted sources. Fixes bug 663.
12885 - Make controller stream events for DNS requests more consistent,
12886 by adding "new stream" events for DNS requests, and removing
12887 spurious "stream closed" events" for cached reverse resolves.
12888 Patch from mwenge. Fixes bug 646.
12889 - Correctly notify one-hop connections when a circuit build has
12890 failed. Possible fix for bug 669. Found by lodger.
12893 Changes in version 0.2.0.23-rc - 2008-03-24
12894 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
12895 makes bootstrapping faster if the first directory mirror you contact
12896 is down. The bundles also include the new Vidalia 0.1.2 release.
12899 - When a tunneled directory request is made to a directory server
12900 that's down, notice after 30 seconds rather than 120 seconds. Also,
12901 fail any begindir streams that are pending on it, so they can
12902 retry elsewhere. This was causing multi-minute delays on bootstrap.
12905 Changes in version 0.2.0.22-rc - 2008-03-18
12906 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
12907 enables encrypted directory connections by default for non-relays, fixes
12908 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
12909 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
12912 - Enable encrypted directory connections by default for non-relays,
12913 so censor tools that block Tor directory connections based on their
12914 plaintext patterns will no longer work. This means Tor works in
12915 certain censored countries by default again.
12918 - Make sure servers always request certificates from clients during
12919 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
12920 - Do not enter a CPU-eating loop when a connection is closed in
12921 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
12922 diagnosed by lodger; bugfix on 0.2.0.20-rc.
12923 - Fix assertion failure that could occur when a blocked circuit
12924 became unblocked, and it had pending client DNS requests. Bugfix
12925 on 0.2.0.1-alpha. Fixes bug 632.
12927 o Minor bugfixes (on 0.1.2.x):
12928 - Generate "STATUS_SERVER" events rather than misspelled
12929 "STATUS_SEVER" events. Caught by mwenge.
12930 - When counting the number of bytes written on a TLS connection,
12931 look at the BIO actually used for writing to the network, not
12932 at the BIO used (sometimes) to buffer data for the network.
12933 Looking at different BIOs could result in write counts on the
12934 order of ULONG_MAX. Fixes bug 614.
12935 - On Windows, correctly detect errors when listing the contents of
12936 a directory. Fix from lodger.
12938 o Minor bugfixes (on 0.2.0.x):
12939 - Downgrade "sslv3 alert handshake failure" message to INFO.
12940 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
12941 left BandwidthRate and BandwidthBurst at the default, we would be
12942 silently limited by those defaults. Now raise them to match the
12943 RelayBandwidth* values.
12944 - Fix the SVK version detection logic to work correctly on a branch.
12945 - Make --enable-openbsd-malloc work correctly on Linux with alpha
12946 CPUs. Fixes bug 625.
12947 - Logging functions now check that the passed severity is sane.
12948 - Use proper log levels in the testsuite call of
12949 get_interface_address6().
12950 - When using a nonstandard malloc, do not use the platform values for
12951 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
12952 - Make the openbsd malloc code use 8k pages on alpha CPUs and
12954 - Detect mismatched page sizes when using --enable-openbsd-malloc.
12955 - Avoid double-marked-for-close warning when certain kinds of invalid
12956 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
12957 for bug 617. Bugfix on 0.2.0.1-alpha.
12958 - Make sure that the "NULL-means-reject *:*" convention is followed by
12959 all the policy manipulation functions, avoiding some possible crash
12960 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
12961 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
12962 actually works, and doesn't warn about every single reverse lookup.
12963 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
12966 - Only log guard node status when guard node status has changed.
12967 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12968 make "INFO" 75% less verbose.
12971 Changes in version 0.2.0.21-rc - 2008-03-02
12972 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
12973 makes Tor work well with Vidalia again, fixes a rare assert bug,
12974 and fixes a pair of more minor bugs. The bundles also include Vidalia
12975 0.1.0 and Torbutton 1.1.16.
12978 - The control port should declare that it requires password auth
12979 when HashedControlSessionPassword is set too. Patch from Matt Edman;
12980 bugfix on 0.2.0.20-rc. Fixes bug 615.
12981 - Downgrade assert in connection_buckets_decrement() to a log message.
12982 This may help us solve bug 614, and in any case will make its
12983 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
12984 - We were sometimes miscounting the number of bytes read from the
12985 network, causing our rate limiting to not be followed exactly.
12986 Bugfix on 0.2.0.16-alpha. Reported by lodger.
12989 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
12990 OpenSSL versions should have been working fine. Diagnosis and patch
12991 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
12992 Bugfix on 0.2.0.20-rc.
12995 Changes in version 0.2.0.20-rc - 2008-02-24
12996 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
12997 makes more progress towards normalizing Tor's TLS handshake, makes
12998 hidden services work better again, helps relays bootstrap if they don't
12999 know their IP address, adds optional support for linking in openbsd's
13000 allocator or tcmalloc, allows really fast relays to scale past 15000
13001 sockets, and fixes a bunch of minor bugs reported by Veracode.
13004 - Enable the revised TLS handshake based on the one designed by
13005 Steven Murdoch in proposal 124, as revised in proposal 130. It
13006 includes version negotiation for OR connections as described in
13007 proposal 105. The new handshake is meant to be harder for censors
13008 to fingerprint, and it adds the ability to detect certain kinds of
13009 man-in-the-middle traffic analysis attacks. The version negotiation
13010 feature will allow us to improve Tor's link protocol more safely
13012 - Choose which bridge to use proportional to its advertised bandwidth,
13013 rather than uniformly at random. This should speed up Tor for
13014 bridge users. Also do this for people who set StrictEntryNodes.
13015 - When a TrackHostExits-chosen exit fails too many times in a row,
13016 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
13019 - Resolved problems with (re-)fetching hidden service descriptors.
13020 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
13021 and 0.2.0.19-alpha.
13022 - If we only ever used Tor for hidden service lookups or posts, we
13023 would stop building circuits and start refusing connections after
13024 24 hours, since we falsely believed that Tor was dormant. Reported
13025 by nwf; bugfix on 0.1.2.x.
13026 - Servers that don't know their own IP address should go to the
13027 authorities for their first directory fetch, even if their DirPort
13028 is off or if they don't know they're reachable yet. This will help
13029 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
13030 - When counting the number of open sockets, count not only the number
13031 of sockets we have received from the socket() call, but also
13032 the number we've gotten from accept() and socketpair(). This bug
13033 made us fail to count all sockets that we were using for incoming
13034 connections. Bugfix on 0.2.0.x.
13035 - Fix code used to find strings within buffers, when those strings
13036 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
13037 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
13038 - Add a new __HashedControlSessionPassword option for controllers
13039 to use for one-off session password hashes that shouldn't get
13040 saved to disk by SAVECONF --- Vidalia users were accumulating a
13041 pile of HashedControlPassword lines in their torrc files, one for
13042 each time they had restarted Tor and then clicked Save. Make Tor
13043 automatically convert "HashedControlPassword" to this new option but
13044 only when it's given on the command line. Partial fix for bug 586.
13046 o Minor features (performance):
13047 - Tune parameters for cell pool allocation to minimize amount of
13049 - Add OpenBSD malloc code from phk as an optional malloc
13050 replacement on Linux: some glibc libraries do very poorly
13051 with Tor's memory allocation patterns. Pass
13052 --enable-openbsd-malloc to get the replacement malloc code.
13053 - Add a --with-tcmalloc option to the configure script to link
13054 against tcmalloc (if present). Does not yet search for
13055 non-system include paths.
13056 - Stop imposing an arbitrary maximum on the number of file descriptors
13057 used for busy servers. Bug reported by Olaf Selke; patch from
13060 o Minor features (other):
13061 - When SafeLogging is disabled, log addresses along with all TLS
13063 - When building with --enable-gcc-warnings, check for whether Apple's
13064 warning "-Wshorten-64-to-32" is available.
13065 - Add a --passphrase-fd argument to the tor-gencert command for
13068 o Minor bugfixes (memory leaks and code problems):
13069 - We were leaking a file descriptor if Tor started with a zero-length
13070 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
13071 - Detect size overflow in zlib code. Reported by Justin Ferguson and
13073 - We were comparing the raw BridgePassword entry with a base64'ed
13074 version of it, when handling a "/tor/networkstatus-bridges"
13075 directory request. Now compare correctly. Noticed by Veracode.
13076 - Recover from bad tracked-since value in MTBF-history file.
13077 Should fix bug 537.
13078 - Alter the code that tries to recover from unhandled write
13079 errors, to not try to flush onto a socket that's given us
13080 unhandled errors. Bugfix on 0.1.2.x.
13081 - Make Unix controlsockets work correctly on OpenBSD. Patch from
13082 tup. Bugfix on 0.2.0.3-alpha.
13084 o Minor bugfixes (other):
13085 - If we have an extra-info document for our server, always make
13086 it available on the control port, even if we haven't gotten
13087 a copy of it from an authority yet. Patch from mwenge.
13088 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
13089 - Directory mirrors no longer include a guess at the client's IP
13090 address if the connection appears to be coming from the same /24
13091 network; it was producing too many wrong guesses.
13092 - Make the new hidden service code respect the SafeLogging setting.
13093 Bugfix on 0.2.0.x. Patch from Karsten.
13094 - When starting as an authority, do not overwrite all certificates
13095 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
13096 - If we're trying to flush the last bytes on a connection (for
13097 example, when answering a directory request), reset the
13098 time-to-give-up timeout every time we manage to write something
13099 on the socket. Bugfix on 0.1.2.x.
13100 - Change the behavior of "getinfo status/good-server-descriptor"
13101 so it doesn't return failure when any authority disappears.
13102 - Even though the man page said that "TrackHostExits ." should
13103 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
13104 - Report TLS "zero return" case as a "clean close" and "IO error"
13105 as a "close". Stop calling closes "unexpected closes": existing
13106 Tors don't use SSL_close(), so having a connection close without
13107 the TLS shutdown handshake is hardly unexpected.
13108 - Send NAMESERVER_STATUS messages for a single failed nameserver
13111 o Code simplifications and refactoring:
13112 - Remove the tor_strpartition function: its logic was confused,
13113 and it was only used for one thing that could be implemented far
13117 Changes in version 0.2.0.19-alpha - 2008-02-09
13118 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
13119 handshake, makes path selection for relays more secure and IP address
13120 guessing more robust, and generally fixes a lot of bugs in preparation
13121 for calling the 0.2.0 branch stable.
13124 - Do not include recognizeable strings in the commonname part of
13125 Tor's x509 certificates.
13128 - If we're a relay, avoid picking ourselves as an introduction point,
13129 a rendezvous point, or as the final hop for internal circuits. Bug
13130 reported by taranis and lodger. Bugfix on 0.1.2.x.
13131 - Patch from "Andrew S. Lists" to catch when we contact a directory
13132 mirror at IP address X and he says we look like we're coming from
13133 IP address X. Bugfix on 0.1.2.x.
13135 o Minor features (security):
13136 - Be more paranoid about overwriting sensitive memory on free(),
13137 as a defensive programming tactic to ensure forward secrecy.
13139 o Minor features (directory authority):
13140 - Actually validate the options passed to AuthDirReject,
13141 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
13142 - Reject router descriptors with out-of-range bandwidthcapacity or
13143 bandwidthburst values.
13145 o Minor features (controller):
13146 - Reject controller commands over 1MB in length. This keeps rogue
13147 processes from running us out of memory.
13149 o Minor features (misc):
13150 - Give more descriptive well-formedness errors for out-of-range
13151 hidden service descriptor/protocol versions.
13152 - Make memory debugging information describe more about history
13153 of cell allocation, so we can help reduce our memory use.
13155 o Deprecated features (controller):
13156 - The status/version/num-versioning and status/version/num-concurring
13157 GETINFO options are no longer useful in the v3 directory protocol:
13158 treat them as deprecated, and warn when they're used.
13161 - When our consensus networkstatus has been expired for a while, stop
13162 being willing to build circuits using it. Fixes bug 401. Bugfix
13164 - Directory caches now fetch certificates from all authorities
13165 listed in a networkstatus consensus, even when they do not
13166 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
13167 - When connecting to a bridge without specifying its key, insert
13168 the connection into the identity-to-connection map as soon as
13169 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
13170 - Detect versions of OS X where malloc_good_size() is present in the
13171 library but never actually declared. Resolves bug 587. Bugfix
13173 - Stop incorrectly truncating zlib responses to directory authority
13174 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
13175 - Stop recommending that every server operator send mail to tor-ops.
13176 Resolves bug 597. Bugfix on 0.1.2.x.
13177 - Don't trigger an assert if we start a directory authority with a
13178 private IP address (like 127.0.0.1).
13179 - Avoid possible failures when generating a directory with routers
13180 with over-long versions strings, or too many flags set. Bugfix
13182 - If an attempt to launch a DNS resolve request over the control
13183 port fails because we have overrun the limit on the number of
13184 connections, tell the controller that the request has failed.
13185 - Avoid using too little bandwidth when our clock skips a few
13186 seconds. Bugfix on 0.1.2.x.
13187 - Fix shell error when warning about missing packages in configure
13188 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
13189 - Do not become confused when receiving a spurious VERSIONS-like
13190 cell from a confused v1 client. Bugfix on 0.2.0.x.
13191 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
13192 introduction points for a hidden service have failed. Patch from
13193 Karsten Loesing. Bugfix on 0.2.0.x.
13195 o Code simplifications and refactoring:
13196 - Remove some needless generality from cpuworker code, for improved
13198 - Stop overloading the circuit_t.onionskin field for both "onionskin
13199 from a CREATE cell that we are waiting for a cpuworker to be
13200 assigned" and "onionskin from an EXTEND cell that we are going to
13201 send to an OR as soon as we are connected". Might help with bug 600.
13202 - Add an in-place version of aes_crypt() so that we can avoid doing a
13203 needless memcpy() call on each cell payload.
13206 Changes in version 0.2.0.18-alpha - 2008-01-25
13207 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
13208 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
13209 that can warn or reject connections to ports generally associated with
13210 vulnerable-plaintext protocols.
13212 o New directory authorities:
13213 - Set up dannenberg (run by CCC) as the sixth v3 directory
13217 - Fix a major memory leak when attempting to use the v2 TLS
13218 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
13219 - We accidentally enabled the under-development v2 TLS handshake
13220 code, which was causing log entries like "TLS error while
13221 renegotiating handshake". Disable it again. Resolves bug 590.
13222 - We were computing the wrong Content-Length: header for directory
13223 responses that need to be compressed on the fly, causing clients
13224 asking for those items to always fail. Bugfix on 0.2.0.x; partially
13228 - Avoid going directly to the directory authorities even if you're a
13229 relay, if you haven't found yourself reachable yet or if you've
13230 decided not to advertise your dirport yet. Addresses bug 556.
13231 - If we've gone 12 hours since our last bandwidth check, and we
13232 estimate we have less than 50KB bandwidth capacity but we could
13233 handle more, do another bandwidth test.
13234 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
13235 Tor can warn and/or refuse connections to ports commonly used with
13236 vulnerable-plaintext protocols. Currently we warn on ports 23,
13237 109, 110, and 143, but we don't reject any.
13240 - When we setconf ClientOnly to 1, close any current OR and Dir
13241 listeners. Reported by mwenge.
13242 - When we get a consensus that's been signed by more people than
13243 we expect, don't log about it; it's not a big deal. Reported
13247 - Don't answer "/tor/networkstatus-bridges" directory requests if
13248 the request isn't encrypted.
13249 - Make "ClientOnly 1" config option disable directory ports too.
13250 - Patches from Karsten Loesing to make v2 hidden services more
13251 robust: work even when there aren't enough HSDir relays available;
13252 retry when a v2 rend desc fetch fails; but don't retry if we
13253 already have a usable v0 rend desc.
13256 Changes in version 0.2.0.17-alpha - 2008-01-17
13257 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
13260 - Make the tor-gencert man page get included correctly in the tarball.
13263 Changes in version 0.2.0.16-alpha - 2008-01-17
13264 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
13265 Loesing, and generally cleans up a lot of features and minor bugs.
13267 o New directory authorities:
13268 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
13271 o Major performance improvements:
13272 - Switch our old ring buffer implementation for one more like that
13273 used by free Unix kernels. The wasted space in a buffer with 1mb
13274 of data will now be more like 8k than 1mb. The new implementation
13275 also avoids realloc();realloc(); patterns that can contribute to
13276 memory fragmentation.
13279 - Configuration files now accept C-style strings as values. This
13280 helps encode characters not allowed in the current configuration
13281 file format, such as newline or #. Addresses bug 557.
13282 - Although we fixed bug 539 (where servers would send HTTP status 503
13283 responses _and_ send a body too), there are still servers out
13284 there that haven't upgraded. Therefore, make clients parse such
13285 bodies when they receive them.
13286 - When we're not serving v2 directory information, there is no reason
13287 to actually keep any around. Remove the obsolete files and directory
13288 on startup if they are very old and we aren't going to serve them.
13290 o Minor performance improvements:
13291 - Reference-count and share copies of address policy entries; only 5%
13292 of them were actually distinct.
13293 - Never walk through the list of logs if we know that no log is
13294 interested in a given message.
13297 - When an authority has not signed a consensus, do not try to
13298 download a nonexistent "certificate with key 00000000". Bugfix
13299 on 0.2.0.x. Fixes bug 569.
13300 - Fix a rare assert error when we're closing one of our threads:
13301 use a mutex to protect the list of logs, so we never write to the
13302 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
13303 bug 575, which is kind of the revenge of bug 222.
13304 - Patch from Karsten Loesing to complain less at both the client
13305 and the relay when a relay used to have the HSDir flag but doesn't
13306 anymore, and we try to upload a hidden service descriptor.
13307 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
13309 - Do not try to download missing certificates until we have tried
13310 to check our fallback consensus. Fixes bug 583.
13311 - Make bridges round reported GeoIP stats info up to the nearest
13312 estimate, not down. Now we can distinguish between "0 people from
13313 this country" and "1 person from this country".
13314 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
13315 - Avoid possible segfault if key generation fails in
13316 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
13317 - Avoid segfault in the case where a badly behaved v2 versioning
13318 directory sends a signed networkstatus with missing client-versions.
13320 - Avoid segfaults on certain complex invocations of
13321 router_get_by_hexdigest(). Bugfix on 0.1.2.
13322 - Correct bad index on array access in parse_http_time(). Bugfix
13324 - Fix possible bug in vote generation when server versions are present
13325 but client versions are not.
13326 - Fix rare bug on REDIRECTSTREAM control command when called with no
13327 port set: it could erroneously report an error when none had
13329 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
13330 compressing large objects and find ourselves with more than 4k
13331 left over. Bugfix on 0.2.0.
13332 - Fix a small memory leak when setting up a hidden service.
13333 - Fix a few memory leaks that could in theory happen under bizarre
13335 - Fix an assert if we post a general-purpose descriptor via the
13336 control port but that descriptor isn't mentioned in our current
13337 network consensus. Bug reported by Jon McLachlan; bugfix on
13340 o Minor features (controller):
13341 - Get NS events working again. Patch from tup.
13342 - The GETCONF command now escapes and quotes configuration values
13343 that don't otherwise fit into the torrc file.
13344 - The SETCONF command now handles quoted values correctly.
13346 o Minor features (directory authorities):
13347 - New configuration options to override default maximum number of
13348 servers allowed on a single IP address. This is important for
13349 running a test network on a single host.
13350 - Actually implement the -s option to tor-gencert.
13351 - Add a manual page for tor-gencert.
13353 o Minor features (bridges):
13354 - Bridge authorities no longer serve bridge descriptors over
13355 unencrypted connections.
13357 o Minor features (other):
13358 - Add hidden services and DNSPorts to the list of things that make
13359 Tor accept that it has running ports. Change starting Tor with no
13360 ports from a fatal error to a warning; we might change it back if
13361 this turns out to confuse anybody. Fixes bug 579.
13364 Changes in version 0.1.2.19 - 2008-01-17
13365 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
13366 exit policy a little bit more conservative so it's safer to run an
13367 exit relay on a home system, and fixes a variety of smaller issues.
13370 - Exit policies now reject connections that are addressed to a
13371 relay's public (external) IP address too, unless
13372 ExitPolicyRejectPrivate is turned off. We do this because too
13373 many relays are running nearby to services that trust them based
13374 on network address.
13377 - When the clock jumps forward a lot, do not allow the bandwidth
13378 buckets to become negative. Fixes bug 544.
13379 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13380 on every successful resolve. Reported by Mike Perry.
13381 - Purge old entries from the "rephist" database and the hidden
13382 service descriptor database even when DirPort is zero.
13383 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13384 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13385 crashing or mis-answering these requests.
13386 - When we decide to send a 503 response to a request for servers, do
13387 not then also send the server descriptors: this defeats the whole
13388 purpose. Fixes bug 539.
13391 - Changing the ExitPolicyRejectPrivate setting should cause us to
13392 rebuild our server descriptor.
13393 - Fix handling of hex nicknames when answering controller requests for
13394 networkstatus by name, or when deciding whether to warn about
13395 unknown routers in a config option. (Patch from mwenge.)
13396 - Fix a couple of hard-to-trigger autoconf problems that could result
13397 in really weird results on platforms whose sys/types.h files define
13398 nonstandard integer types.
13399 - Don't try to create the datadir when running --verify-config or
13400 --hash-password. Resolves bug 540.
13401 - If we were having problems getting a particular descriptor from the
13402 directory caches, and then we learned about a new descriptor for
13403 that router, we weren't resetting our failure count. Reported
13405 - Although we fixed bug 539 (where servers would send HTTP status 503
13406 responses _and_ send a body too), there are still servers out there
13407 that haven't upgraded. Therefore, make clients parse such bodies
13408 when they receive them.
13409 - Run correctly on systems where rlim_t is larger than unsigned long.
13410 This includes some 64-bit systems.
13411 - Run correctly on platforms (like some versions of OS X 10.5) where
13412 the real limit for number of open files is OPEN_FILES, not rlim_max
13413 from getrlimit(RLIMIT_NOFILES).
13414 - Avoid a spurious free on base64 failure.
13415 - Avoid segfaults on certain complex invocations of
13416 router_get_by_hexdigest().
13417 - Fix rare bug on REDIRECTSTREAM control command when called with no
13418 port set: it could erroneously report an error when none had
13422 Changes in version 0.2.0.15-alpha - 2007-12-25
13423 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
13424 features added in 0.2.0.13-alpha.
13427 - Fix several remotely triggerable asserts based on DirPort requests
13428 for a v2 or v3 networkstatus object before we were prepared. This
13429 was particularly bad for 0.2.0.13 and later bridge relays, who
13430 would never have a v2 networkstatus and would thus always crash
13431 when used. Bugfixes on 0.2.0.x.
13432 - Estimate the v3 networkstatus size more accurately, rather than
13433 estimating it at zero bytes and giving it artificially high priority
13434 compared to other directory requests. Bugfix on 0.2.0.x.
13437 - Fix configure.in logic for cross-compilation.
13438 - When we load a bridge descriptor from the cache, and it was
13439 previously unreachable, mark it as retriable so we won't just
13440 ignore it. Also, try fetching a new copy immediately. Bugfixes
13442 - The bridge GeoIP stats were counting other relays, for example
13443 self-reachability and authority-reachability tests.
13446 - Support compilation to target iPhone; patch from cjacker huang.
13447 To build for iPhone, pass the --enable-iphone option to configure.
13450 Changes in version 0.2.0.14-alpha - 2007-12-23
13452 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
13453 without a datadirectory from a previous Tor install. Reported
13455 - Fix a crash when we fetch a descriptor that turns out to be
13456 unexpected (it used to be in our networkstatus when we started
13457 fetching it, but it isn't in our current networkstatus), and we
13458 aren't using bridges. Bugfix on 0.2.0.x.
13459 - Fix a crash when accessing hidden services: it would work the first
13460 time you use a given introduction point for your service, but
13461 on subsequent requests we'd be using garbage memory. Fixed by
13462 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
13463 - Fix a crash when we load a bridge descriptor from disk but we don't
13464 currently have a Bridge line for it in our torrc. Bugfix on
13468 - If bridge authorities set BridgePassword, they will serve a
13469 snapshot of known bridge routerstatuses from their DirPort to
13470 anybody who knows that password. Unset by default.
13473 - Make the unit tests build again.
13474 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
13475 - Make PublishServerDescriptor default to 1, so the default doesn't
13476 have to change as we invent new directory protocol versions.
13477 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
13478 be included unless sys/time.h is already included. Fixes
13479 bug 553. Bugfix on 0.2.0.x.
13480 - If we receive a general-purpose descriptor and then receive an
13481 identical bridge-purpose descriptor soon after, don't discard
13482 the next one as a duplicate.
13485 - If BridgeRelay is set to 1, then the default for
13486 PublishServerDescriptor is now "bridge" rather than "v2,v3".
13487 - If the user sets RelayBandwidthRate but doesn't set
13488 RelayBandwidthBurst, then make them equal rather than erroring out.
13491 Changes in version 0.2.0.13-alpha - 2007-12-21
13492 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
13493 Goodell, fixes many more bugs, and adds a lot of infrastructure for
13496 o New directory authorities:
13497 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
13501 - Only update guard status (usable / not usable) once we have
13502 enough directory information. This was causing us to always pick
13503 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
13504 causing us to discard all our guards on startup if we hadn't been
13505 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
13506 - Purge old entries from the "rephist" database and the hidden
13507 service descriptor databases even when DirPort is zero. Bugfix
13509 - We were ignoring our RelayBandwidthRate for the first 30 seconds
13510 after opening a circuit -- even a relayed circuit. Bugfix on
13512 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13513 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13514 crashing or mis-answering these types of requests.
13515 - Relays were publishing their server descriptor to v1 and v2
13516 directory authorities, but they didn't try publishing to v3-only
13517 authorities. Fix this; and also stop publishing to v1 authorities.
13519 - When we were reading router descriptors from cache, we were ignoring
13520 the annotations -- so for example we were reading in bridge-purpose
13521 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
13522 - When we decided to send a 503 response to a request for servers, we
13523 were then also sending the server descriptors: this defeats the
13524 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
13527 - Bridge relays now behave like clients with respect to time
13528 intervals for downloading new consensus documents -- otherwise they
13529 stand out. Bridge users now wait until the end of the interval,
13530 so their bridge relay will be sure to have a new consensus document.
13531 - Three new config options (AlternateDirAuthority,
13532 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
13533 user selectively replace the default directory authorities by type,
13534 rather than the all-or-nothing replacement that DirServer offers.
13535 - Tor can now be configured to read a GeoIP file from disk in one
13536 of two formats. This can be used by controllers to map IP addresses
13537 to countries. Eventually, it may support exit-by-country.
13538 - When possible, bridge relays remember which countries users
13539 are coming from, and report aggregate information in their
13540 extra-info documents, so that the bridge authorities can learn
13541 where Tor is blocked.
13542 - Bridge directory authorities now do reachability testing on the
13543 bridges they know. They provide router status summaries to the
13544 controller via "getinfo ns/purpose/bridge", and also dump summaries
13545 to a file periodically.
13546 - Stop fetching directory info so aggressively if your DirPort is
13547 on but your ORPort is off; stop fetching v2 dir info entirely.
13548 You can override these choices with the new FetchDirInfoEarly
13552 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
13553 consensus documents when there are too many relays at a single
13554 IP address. Now clear it in v2 network status documents too, and
13555 also clear it in routerinfo_t when the relay is no longer listed
13556 in the relevant networkstatus document.
13557 - Don't crash if we get an unexpected value for the
13558 PublishServerDescriptor config option. Reported by Matt Edman;
13559 bugfix on 0.2.0.9-alpha.
13560 - Our new v2 hidden service descriptor format allows descriptors
13561 that have no introduction points. But Tor crashed when we tried
13562 to build a descriptor with no intro points (and it would have
13563 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
13564 by Karsten Loesing.
13565 - Fix building with dmalloc 5.5.2 with glibc.
13566 - Reject uploaded descriptors and extrainfo documents if they're
13567 huge. Otherwise we'll cache them all over the network and it'll
13568 clog everything up. Reported by Aljosha Judmayer.
13569 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
13570 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
13571 - When the DANGEROUS_VERSION controller status event told us we're
13572 running an obsolete version, it used the string "OLD" to describe
13573 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
13574 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
13575 - If we can't expand our list of entry guards (e.g. because we're
13576 using bridges or we have StrictEntryNodes set), don't mark relays
13577 down when they fail a directory request. Otherwise we're too quick
13578 to mark all our entry points down. Bugfix on 0.1.2.x.
13579 - Fix handling of hex nicknames when answering controller requests for
13580 networkstatus by name, or when deciding whether to warn about unknown
13581 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
13582 - Fix a couple of hard-to-trigger autoconf problems that could result
13583 in really weird results on platforms whose sys/types.h files define
13584 nonstandard integer types. Bugfix on 0.1.2.x.
13585 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
13586 - Don't crash on name lookup when we have no current consensus. Fixes
13587 bug 538; bugfix on 0.2.0.x.
13588 - Only Tors that want to mirror the v2 directory info should
13589 create the "cached-status" directory in their datadir. (All Tors
13590 used to create it.) Bugfix on 0.2.0.9-alpha.
13591 - Directory authorities should only automatically download Extra Info
13592 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
13595 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
13596 consumers. (We already do this on HUP.)
13597 - Authorities and caches fetch the v2 networkstatus documents
13598 less often, now that v3 is encouraged.
13599 - Add a new config option BridgeRelay that specifies you want to
13600 be a bridge relay. Right now the only difference is that it makes
13601 you answer begin_dir requests, and it makes you cache dir info,
13602 even if your DirPort isn't on.
13603 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
13604 ask about source, timestamp of arrival, purpose, etc. We need
13605 something like this to help Vidalia not do GeoIP lookups on bridge
13607 - Allow multiple HashedControlPassword config lines, to support
13608 multiple controller passwords.
13609 - Authorities now decide whether they're authoritative for a given
13610 router based on the router's purpose.
13611 - New config options AuthDirBadDir and AuthDirListBadDirs for
13612 authorities to mark certain relays as "bad directories" in the
13613 networkstatus documents. Also supports the "!baddir" directive in
13614 the approved-routers file.
13617 Changes in version 0.2.0.12-alpha - 2007-11-16
13618 This twelfth development snapshot fixes some more build problems as
13619 well as a few minor bugs.
13622 - Make it build on OpenBSD again. Patch from tup.
13623 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
13624 package-building for Red Hat, OS X, etc.
13626 o Minor bugfixes (on 0.1.2.x):
13627 - Changing the ExitPolicyRejectPrivate setting should cause us to
13628 rebuild our server descriptor.
13630 o Minor bugfixes (on 0.2.0.x):
13631 - When we're lacking a consensus, don't try to perform rendezvous
13632 operations. Reported by Karsten Loesing.
13633 - Fix a small memory leak whenever we decide against using a
13634 newly picked entry guard. Reported by Mike Perry.
13635 - When authorities detected more than two relays running on the same
13636 IP address, they were clearing all the status flags but forgetting
13637 to clear the "hsdir" flag. So clients were being told that a
13638 given relay was the right choice for a v2 hsdir lookup, yet they
13639 never had its descriptor because it was marked as 'not running'
13641 - If we're trying to fetch a bridge descriptor and there's no way
13642 the bridge authority could help us (for example, we don't know
13643 a digest, or there is no bridge authority), don't be so eager to
13644 fall back to asking the bridge authority.
13645 - If we're using bridges or have strictentrynodes set, and our
13646 chosen exit is in the same family as all our bridges/entry guards,
13647 then be flexible about families.
13650 - When we negotiate a v2 link-layer connection (not yet implemented),
13651 accept RELAY_EARLY cells and turn them into RELAY cells if we've
13652 negotiated a v1 connection for their next step. Initial code for
13656 Changes in version 0.2.0.11-alpha - 2007-11-12
13657 This eleventh development snapshot fixes some build problems with
13658 the previous snapshot. It also includes a more secure-by-default exit
13659 policy for relays, fixes an enormous memory leak for exit relays, and
13660 fixes another bug where servers were falling out of the directory list.
13663 - Exit policies now reject connections that are addressed to a
13664 relay's public (external) IP address too, unless
13665 ExitPolicyRejectPrivate is turned off. We do this because too
13666 many relays are running nearby to services that trust them based
13667 on network address. Bugfix on 0.1.2.x.
13670 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13671 on every successful resolve. Reported by Mike Perry; bugfix
13673 - On authorities, never downgrade to old router descriptors simply
13674 because they're listed in the consensus. This created a catch-22
13675 where we wouldn't list a new descriptor because there was an
13676 old one in the consensus, and we couldn't get the new one in the
13677 consensus because we wouldn't list it. Possible fix for bug 548.
13678 Also, this might cause bug 543 to appear on authorities; if so,
13679 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
13681 o Packaging fixes on 0.2.0.10-alpha:
13682 - We were including instructions about what to do with the
13683 src/config/fallback-consensus file, but we weren't actually
13684 including it in the tarball. Disable all of that for now.
13687 - Allow people to say PreferTunnelledDirConns rather than
13688 PreferTunneledDirConns, for those alternate-spellers out there.
13691 - Don't reevaluate all the information from our consensus document
13692 just because we've downloaded a v2 networkstatus that we intend
13693 to cache. Fixes bug 545; bugfix on 0.2.0.x.
13696 Changes in version 0.2.0.10-alpha - 2007-11-10
13697 This tenth development snapshot adds a third v3 directory authority
13698 run by Mike Perry, adds most of Karsten Loesing's new hidden service
13699 descriptor format, fixes a bad crash bug and new bridge bugs introduced
13700 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
13701 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
13702 addresses many more minor issues.
13704 o New directory authorities:
13705 - Set up ides (run by Mike Perry) as the third v3 directory authority.
13708 - Allow tunnelled directory connections to ask for an encrypted
13709 "begin_dir" connection or an anonymized "uses a full Tor circuit"
13710 connection independently. Now we can make anonymized begin_dir
13711 connections for (e.g.) more secure hidden service posting and
13713 - More progress on proposal 114: code from Karsten Loesing to
13714 implement new hidden service descriptor format.
13715 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
13716 accommodate the growing number of servers that use the default
13717 and are reaching it.
13718 - Directory authorities use a new formula for selecting which nodes
13719 to advertise as Guards: they must be in the top 7/8 in terms of
13720 how long we have known about them, and above the median of those
13721 nodes in terms of weighted fractional uptime.
13722 - Make "not enough dir info yet" warnings describe *why* Tor feels
13723 it doesn't have enough directory info yet.
13726 - Stop servers from crashing if they set a Family option (or
13727 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
13729 - Make bridge users work again -- the move to v3 directories in
13730 0.2.0.9-alpha had introduced a number of bugs that made bridges
13731 no longer work for clients.
13732 - When the clock jumps forward a lot, do not allow the bandwidth
13733 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
13735 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
13736 - When the consensus lists a router descriptor that we previously were
13737 mirroring, but that we considered non-canonical, reload the
13738 descriptor as canonical. This fixes bug 543 where Tor servers
13739 would start complaining after a few days that they don't have
13740 enough directory information to build a circuit.
13741 - Consider replacing the current consensus when certificates arrive
13742 that make the pending consensus valid. Previously, we were only
13743 considering replacement when the new certs _didn't_ help.
13744 - Fix an assert error on startup if we didn't already have the
13745 consensus and certs cached in our datadirectory: we were caching
13746 the consensus in consensus_waiting_for_certs but then free'ing it
13748 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
13749 Request) if we need more v3 certs but we've already got pending
13750 requests for all of them.
13751 - Correctly back off from failing certificate downloads. Fixes
13753 - Authorities don't vote on the Running flag if they have been running
13754 for less than 30 minutes themselves. Fixes bug 547, where a newly
13755 started authority would vote that everyone was down.
13757 o New requirements:
13758 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
13759 it, it had no AES, and it hasn't seen any security patches since
13763 - Clients now hold circuitless TLS connections open for 1.5 times
13764 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
13765 rebuild a new circuit over them within that timeframe. Previously,
13766 they held them open only for KeepalivePeriod (5 minutes).
13767 - Use "If-Modified-Since" to avoid retrieving consensus
13768 networkstatuses that we already have.
13769 - When we have no consensus, check FallbackNetworkstatusFile (defaults
13770 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
13771 we start knowing some directory caches.
13772 - When we receive a consensus from the future, warn about skew.
13773 - Improve skew reporting: try to give the user a better log message
13774 about how skewed they are, and how much this matters.
13775 - When we have a certificate for an authority, believe that
13776 certificate's claims about the authority's IP address.
13777 - New --quiet command-line option to suppress the default console log.
13778 Good in combination with --hash-password.
13779 - Authorities send back an X-Descriptor-Not-New header in response to
13780 an accepted-but-discarded descriptor upload. Partially implements
13782 - Make the log message for "tls error. breaking." more useful.
13783 - Better log messages about certificate downloads, to attempt to
13784 track down the second incarnation of bug 546.
13786 o Minor features (bridges):
13787 - If bridge users set UpdateBridgesFromAuthority, but the digest
13788 they ask for is a 404 from the bridge authority, they now fall
13789 back to trying the bridge directly.
13790 - Bridges now use begin_dir to publish their server descriptor to
13791 the bridge authority, even when they haven't set TunnelDirConns.
13793 o Minor features (controller):
13794 - When reporting clock skew, and we know that the clock is _at least
13795 as skewed_ as some value, but we don't know the actual value,
13796 report the value as a "minimum skew."
13799 - Update linux-tor-prio.sh script to allow QoS based on the uid of
13800 the Tor process. Patch from Marco Bonetti with tweaks from Mike
13804 - Refuse to start if both ORPort and UseBridges are set. Bugfix
13805 on 0.2.0.x, suggested by Matt Edman.
13806 - Don't stop fetching descriptors when FetchUselessDescriptors is
13807 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
13808 reported by tup and ioerror.
13809 - Better log message on vote from unknown authority.
13810 - Don't log "Launching 0 request for 0 router" message.
13812 o Minor bugfixes (memory leaks):
13813 - Stop leaking memory every time we parse a v3 certificate. Bugfix
13815 - Stop leaking memory every time we load a v3 certificate. Bugfix
13816 on 0.2.0.1-alpha. Fixes bug 536.
13817 - Stop leaking a cached networkstatus on exit. Bugfix on
13819 - Stop leaking voter information every time we free a consensus.
13820 Bugfix on 0.2.0.3-alpha.
13821 - Stop leaking signed data every time we check a voter signature.
13822 Bugfix on 0.2.0.3-alpha.
13823 - Stop leaking a signature every time we fail to parse a consensus or
13824 a vote. Bugfix on 0.2.0.3-alpha.
13825 - Stop leaking v2_download_status_map on shutdown. Bugfix on
13827 - Stop leaking conn->nickname every time we make a connection to a
13828 Tor relay without knowing its expected identity digest (e.g. when
13829 using bridges). Bugfix on 0.2.0.3-alpha.
13831 - Minor bugfixes (portability):
13832 - Run correctly on platforms where rlim_t is larger than unsigned
13833 long, and/or where the real limit for number of open files is
13834 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
13835 particular, these may be needed for OS X 10.5.
13838 Changes in version 0.1.2.18 - 2007-10-28
13839 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
13840 hidden service introduction that were causing huge delays, and a big
13841 bug that was causing some servers to disappear from the network status
13842 lists for a few hours each day.
13844 o Major bugfixes (crashes):
13845 - If a connection is shut down abruptly because of something that
13846 happened inside connection_flushed_some(), do not call
13847 connection_finished_flushing(). Should fix bug 451:
13848 "connection_stop_writing: Assertion conn->write_event failed"
13849 Bugfix on 0.1.2.7-alpha.
13850 - Fix possible segfaults in functions called from
13851 rend_process_relay_cell().
13853 o Major bugfixes (hidden services):
13854 - Hidden services were choosing introduction points uniquely by
13855 hexdigest, but when constructing the hidden service descriptor
13856 they merely wrote the (potentially ambiguous) nickname.
13857 - Clients now use the v2 intro format for hidden service
13858 connections: they specify their chosen rendezvous point by identity
13859 digest rather than by (potentially ambiguous) nickname. These
13860 changes could speed up hidden service connections dramatically.
13862 o Major bugfixes (other):
13863 - Stop publishing a new server descriptor just because we get a
13864 HUP signal. This led (in a roundabout way) to some servers getting
13865 dropped from the networkstatus lists for a few hours each day.
13866 - When looking for a circuit to cannibalize, consider family as well
13867 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13868 circuit cannibalization).
13869 - When a router wasn't listed in a new networkstatus, we were leaving
13870 the flags for that router alone -- meaning it remained Named,
13871 Running, etc -- even though absence from the networkstatus means
13872 that it shouldn't be considered to exist at all anymore. Now we
13873 clear all the flags for routers that fall out of the networkstatus
13874 consensus. Fixes bug 529.
13877 - Don't try to access (or alter) the state file when running
13878 --list-fingerprint or --verify-config or --hash-password. Resolves
13880 - When generating information telling us how to extend to a given
13881 router, do not try to include the nickname if it is
13882 absent. Resolves bug 467.
13883 - Fix a user-triggerable segfault in expand_filename(). (There isn't
13884 a way to trigger this remotely.)
13885 - When sending a status event to the controller telling it that an
13886 OR address is reachable, set the port correctly. (Previously we
13887 were reporting the dir port.)
13888 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13889 command. Bugfix on 0.1.2.17.
13890 - When loading bandwidth history, do not believe any information in
13891 the future. Fixes bug 434.
13892 - When loading entry guard information, do not believe any information
13894 - When we have our clock set far in the future and generate an
13895 onion key, then re-set our clock to be correct, we should not stop
13896 the onion key from getting rotated.
13897 - On some platforms, accept() can return a broken address. Detect
13898 this more quietly, and deal accordingly. Fixes bug 483.
13899 - It's not actually an error to find a non-pending entry in the DNS
13900 cache when canceling a pending resolve. Don't log unless stuff
13901 is fishy. Resolves bug 463.
13902 - Don't reset trusted dir server list when we set a configuration
13903 option. Patch from Robert Hogan.
13904 - Don't try to create the datadir when running --verify-config or
13905 --hash-password. Resolves bug 540.
13908 Changes in version 0.2.0.9-alpha - 2007-10-24
13909 This ninth development snapshot switches clients to the new v3 directory
13910 system; allows servers to be listed in the network status even when they
13911 have the same nickname as a registered server; and fixes many other
13912 bugs including a big one that was causing some servers to disappear
13913 from the network status lists for a few hours each day.
13915 o Major features (directory system):
13916 - Clients now download v3 consensus networkstatus documents instead
13917 of v2 networkstatus documents. Clients and caches now base their
13918 opinions about routers on these consensus documents. Clients only
13919 download router descriptors listed in the consensus.
13920 - Authorities now list servers who have the same nickname as
13921 a different named server, but list them with a new flag,
13922 "Unnamed". Now we can list servers that happen to pick the same
13923 nickname as a server that registered two years ago and then
13924 disappeared. Partially implements proposal 122.
13925 - If the consensus lists a router as "Unnamed", the name is assigned
13926 to a different router: do not identify the router by that name.
13927 Partially implements proposal 122.
13928 - Authorities can now come to a consensus on which method to use to
13929 compute the consensus. This gives us forward compatibility.
13932 - Stop publishing a new server descriptor just because we HUP or
13933 when we find our DirPort to be reachable but won't actually publish
13934 it. New descriptors without any real changes are dropped by the
13935 authorities, and can screw up our "publish every 18 hours" schedule.
13937 - When a router wasn't listed in a new networkstatus, we were leaving
13938 the flags for that router alone -- meaning it remained Named,
13939 Running, etc -- even though absence from the networkstatus means
13940 that it shouldn't be considered to exist at all anymore. Now we
13941 clear all the flags for routers that fall out of the networkstatus
13942 consensus. Fixes bug 529; bugfix on 0.1.2.x.
13943 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
13944 extrainfo documents and then discard them immediately for not
13945 matching the latest router. Bugfix on 0.2.0.1-alpha.
13947 o Minor features (v3 directory protocol):
13948 - Allow tor-gencert to generate a new certificate without replacing
13950 - Allow certificates to include an address.
13951 - When we change our directory-cache settings, reschedule all voting
13952 and download operations.
13953 - Reattempt certificate downloads immediately on failure, as long as
13954 we haven't failed a threshold number of times yet.
13955 - Delay retrying consensus downloads while we're downloading
13956 certificates to verify the one we just got. Also, count getting a
13957 consensus that we already have (or one that isn't valid) as a failure,
13958 and count failing to get the certificates after 20 minutes as a
13960 - Build circuits and download descriptors even if our consensus is a
13961 little expired. (This feature will go away once authorities are
13964 o Minor features (router descriptor cache):
13965 - If we find a cached-routers file that's been sitting around for more
13966 than 28 days unmodified, then most likely it's a leftover from
13967 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
13969 - When we (as a cache) download a descriptor because it was listed
13970 in a consensus, remember when the consensus was supposed to expire,
13971 and don't expire the descriptor until then.
13973 o Minor features (performance):
13974 - Call routerlist_remove_old_routers() much less often. This should
13975 speed startup, especially on directory caches.
13976 - Don't try to launch new descriptor downloads quite so often when we
13977 already have enough directory information to build circuits.
13978 - Base64 decoding was actually showing up on our profile when parsing
13979 the initial descriptor file; switch to an in-process all-at-once
13980 implementation that's about 3.5x times faster than calling out to
13983 o Minor features (compilation):
13984 - Detect non-ASCII platforms (if any still exist) and refuse to
13985 build there: some of our code assumes that 'A' is 65 and so on.
13987 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
13988 - Make the "next period" votes into "current period" votes immediately
13989 after publishing the consensus; avoid a heisenbug that made them
13990 stick around indefinitely.
13991 - When we discard a vote as a duplicate, do not report this as
13993 - Treat missing v3 keys or certificates as an error when running as a
13994 v3 directory authority.
13995 - When we're configured to be a v3 authority, but we're only listed
13996 as a non-v3 authority in our DirServer line for ourself, correct
13998 - If an authority doesn't have a qualified hostname, just put
13999 its address in the vote. This fixes the problem where we referred to
14000 "moria on moria:9031."
14001 - Distinguish between detached signatures for the wrong period, and
14002 detached signatures for a divergent vote.
14003 - Fix a small memory leak when computing a consensus.
14004 - When there's no concensus, we were forming a vote every 30
14005 minutes, but writing the "valid-after" line in our vote based
14006 on our configured V3AuthVotingInterval: so unless the intervals
14007 matched up, we immediately rejected our own vote because it didn't
14008 start at the voting interval that caused us to construct a vote.
14010 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
14011 - Delete unverified-consensus when the real consensus is set.
14012 - Consider retrying a consensus networkstatus fetch immediately
14013 after one fails: don't wait 60 seconds to notice.
14014 - When fetching a consensus as a cache, wait until a newer consensus
14015 should exist before trying to replace the current one.
14016 - Use a more forgiving schedule for retrying failed consensus
14017 downloads than for other types.
14019 o Minor bugfixes (other directory issues):
14020 - Correct the implementation of "download votes by digest." Bugfix on
14022 - Authorities no longer send back "400 you're unreachable please fix
14023 it" errors to Tor servers that aren't online all the time. We're
14024 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
14026 o Minor bugfixes (controller):
14027 - Don't reset trusted dir server list when we set a configuration
14028 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
14029 - Respond to INT and TERM SIGNAL commands before we execute the
14030 signal, in case the signal shuts us down. We had a patch in
14031 0.1.2.1-alpha that tried to do this by queueing the response on
14032 the connection's buffer before shutting down, but that really
14033 isn't the same thing at all. Bug located by Matt Edman.
14035 o Minor bugfixes (misc):
14036 - Correctly check for bad options to the "PublishServerDescriptor"
14037 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
14038 - Stop leaking memory on failing case of base32_decode, and make
14039 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
14040 - Don't try to download extrainfo documents when we're trying to
14041 fetch enough directory info to build a circuit: having enough
14042 info should get priority. Bugfix on 0.2.0.x.
14043 - Don't complain that "your server has not managed to confirm that its
14044 ports are reachable" if we haven't been able to build any circuits
14045 yet. Bug found by spending four hours without a v3 consensus. Bugfix
14047 - Detect the reason for failing to mmap a descriptor file we just
14048 wrote, and give a more useful log message. Fixes bug 533. Bugfix
14051 o Code simplifications and refactoring:
14052 - Remove support for the old bw_accounting file: we've been storing
14053 bandwidth accounting information in the state file since
14054 0.1.2.5-alpha. This may result in bandwidth accounting errors
14055 if you try to upgrade from 0.1.1.x or earlier, or if you try to
14056 downgrade to 0.1.1.x or earlier.
14057 - New convenience code to locate a file within the DataDirectory.
14058 - Move non-authority functionality out of dirvote.c.
14059 - Refactor the arguments for router_pick_{directory_|trusteddir}server
14060 so that they all take the same named flags.
14063 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
14064 Unix users an easy way to script their Tor process (e.g. by
14065 adjusting bandwidth based on the time of the day).
14068 Changes in version 0.2.0.8-alpha - 2007-10-12
14069 This eighth development snapshot fixes a crash bug that's been bothering
14070 us since February 2007, lets bridge authorities store a list of bridge
14071 descriptors they've seen, gets v3 directory voting closer to working,
14072 starts caching v3 directory consensus documents on directory mirrors,
14073 and fixes a variety of smaller issues including some minor memory leaks.
14075 o Major features (router descriptor cache):
14076 - Store routers in a file called cached-descriptors instead of in
14077 cached-routers. Initialize cached-descriptors from cached-routers
14078 if the old format is around. The new format allows us to store
14079 annotations along with descriptors.
14080 - Use annotations to record the time we received each descriptor, its
14081 source, and its purpose.
14082 - Disable the SETROUTERPURPOSE controller command: it is now
14084 - Controllers should now specify cache=no or cache=yes when using
14085 the +POSTDESCRIPTOR command.
14086 - Bridge authorities now write bridge descriptors to disk, meaning
14087 we can export them to other programs and begin distributing them
14090 o Major features (directory authorities):
14091 - When a v3 authority is missing votes or signatures, it now tries
14093 - Directory authorities track weighted fractional uptime as well as
14094 weighted mean-time-between failures. WFU is suitable for deciding
14095 whether a node is "usually up", while MTBF is suitable for deciding
14096 whether a node is "likely to stay up." We need both, because
14097 "usually up" is a good requirement for guards, while "likely to
14098 stay up" is a good requirement for long-lived connections.
14100 o Major features (v3 directory system):
14101 - Caches now download v3 network status documents as needed,
14102 and download the descriptors listed in them.
14103 - All hosts now attempt to download and keep fresh v3 authority
14104 certificates, and re-attempt after failures.
14105 - More internal-consistency checks for vote parsing.
14107 o Major bugfixes (crashes):
14108 - If a connection is shut down abruptly because of something that
14109 happened inside connection_flushed_some(), do not call
14110 connection_finished_flushing(). Should fix bug 451. Bugfix on
14113 o Major bugfixes (performance):
14114 - Fix really bad O(n^2) performance when parsing a long list of
14115 routers: Instead of searching the entire list for an "extra-info "
14116 string which usually wasn't there, once for every routerinfo
14117 we read, just scan lines forward until we find one we like.
14119 - When we add data to a write buffer in response to the data on that
14120 write buffer getting low because of a flush, do not consider the
14121 newly added data as a candidate for immediate flushing, but rather
14122 make it wait until the next round of writing. Otherwise, we flush
14123 and refill recursively, and a single greedy TLS connection can
14124 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
14126 o Minor features (v3 authority system):
14127 - Add more ways for tools to download the votes that lead to the
14129 - Send a 503 when low on bandwidth and a vote, consensus, or
14130 certificate is requested.
14131 - If-modified-since is now implemented properly for all kinds of
14132 certificate requests.
14134 o Minor bugfixes (network statuses):
14135 - Tweak the implementation of proposal 109 slightly: allow at most
14136 two Tor servers on the same IP address, except if it's the location
14137 of a directory authority, in which case allow five. Bugfix on
14140 o Minor bugfixes (controller):
14141 - When sending a status event to the controller telling it that an
14142 OR address is reachable, set the port correctly. (Previously we
14143 were reporting the dir port.) Bugfix on 0.1.2.x.
14145 o Minor bugfixes (v3 directory system):
14146 - Fix logic to look up a cert by its signing key digest. Bugfix on
14148 - Only change the reply to a vote to "OK" if it's not already
14149 set. This gets rid of annoying "400 OK" log messages, which may
14150 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
14151 - When we get a valid consensus, recompute the voting schedule.
14152 - Base the valid-after time of a vote on the consensus voting
14153 schedule, not on our preferred schedule.
14154 - Make the return values and messages from signature uploads and
14155 downloads more sensible.
14156 - Fix a memory leak when serving votes and consensus documents, and
14157 another when serving certificates.
14159 o Minor bugfixes (performance):
14160 - Use a slightly simpler string hashing algorithm (copying Python's
14161 instead of Java's) and optimize our digest hashing algorithm to take
14162 advantage of 64-bit platforms and to remove some possibly-costly
14164 - Fix a minor memory leak whenever we parse guards from our state
14165 file. Bugfix on 0.2.0.7-alpha.
14166 - Fix a minor memory leak whenever we write out a file. Bugfix on
14168 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14169 command. Bugfix on 0.2.0.5-alpha.
14171 o Minor bugfixes (portability):
14172 - On some platforms, accept() can return a broken address. Detect
14173 this more quietly, and deal accordingly. Fixes bug 483.
14174 - Stop calling tor_strlower() on uninitialized memory in some cases.
14175 Bugfix in 0.2.0.7-alpha.
14177 o Minor bugfixes (usability):
14178 - Treat some 403 responses from directory servers as INFO rather than
14179 WARN-severity events.
14180 - It's not actually an error to find a non-pending entry in the DNS
14181 cache when canceling a pending resolve. Don't log unless stuff is
14182 fishy. Resolves bug 463.
14184 o Minor bugfixes (anonymity):
14185 - Never report that we've used more bandwidth than we're willing to
14186 relay: it leaks how much non-relay traffic we're using. Resolves
14188 - When looking for a circuit to cannibalize, consider family as well
14189 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14190 circuit cannibalization).
14192 o Code simplifications and refactoring:
14193 - Make a bunch of functions static. Remove some dead code.
14194 - Pull out about a third of the really big routerlist.c; put it in a
14195 new module, networkstatus.c.
14196 - Merge the extra fields in local_routerstatus_t back into
14197 routerstatus_t: we used to need one routerstatus_t for each
14198 authority's opinion, plus a local_routerstatus_t for the locally
14199 computed consensus opinion. To save space, we put the locally
14200 modified fields into local_routerstatus_t, and only the common
14201 stuff into routerstatus_t. But once v3 directories are in use,
14202 clients and caches will no longer need to hold authority opinions;
14203 thus, the rationale for keeping the types separate is now gone.
14204 - Make the code used to reschedule and reattempt downloads more
14206 - Turn all 'Are we a directory server/mirror?' logic into a call to
14208 - Remove the code to generate the oldest (v1) directory format.
14209 The code has been disabled since 0.2.0.5-alpha.
14212 Changes in version 0.2.0.7-alpha - 2007-09-21
14213 This seventh development snapshot makes bridges work again, makes bridge
14214 authorities work for the first time, fixes two huge performance flaws
14215 in hidden services, and fixes a variety of minor issues.
14217 o New directory authorities:
14218 - Set up moria1 and tor26 as the first v3 directory authorities. See
14219 doc/spec/dir-spec.txt for details on the new directory design.
14221 o Major bugfixes (crashes):
14222 - Fix possible segfaults in functions called from
14223 rend_process_relay_cell(). Bugfix on 0.1.2.x.
14225 o Major bugfixes (bridges):
14226 - Fix a bug that made servers send a "404 Not found" in response to
14227 attempts to fetch their server descriptor. This caused Tor servers
14228 to take many minutes to establish reachability for their DirPort,
14229 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
14230 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
14231 users configure that and specify a bridge with an identity
14232 fingerprint, now they will lookup the bridge descriptor at the
14233 default bridge authority via a one-hop tunnel, but once circuits
14234 are established they will switch to a three-hop tunnel for later
14235 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
14237 o Major bugfixes (hidden services):
14238 - Hidden services were choosing introduction points uniquely by
14239 hexdigest, but when constructing the hidden service descriptor
14240 they merely wrote the (potentially ambiguous) nickname.
14241 - Clients now use the v2 intro format for hidden service
14242 connections: they specify their chosen rendezvous point by identity
14243 digest rather than by (potentially ambiguous) nickname. Both
14244 are bugfixes on 0.1.2.x, and they could speed up hidden service
14245 connections dramatically. Thanks to Karsten Loesing.
14247 o Minor features (security):
14248 - As a client, do not believe any server that tells us that an
14249 address maps to an internal address space.
14250 - Make it possible to enable HashedControlPassword and
14251 CookieAuthentication at the same time.
14253 o Minor features (guard nodes):
14254 - Tag every guard node in our state file with the version that
14255 we believe added it, or with our own version if we add it. This way,
14256 if a user temporarily runs an old version of Tor and then switches
14257 back to a new one, she doesn't automatically lose her guards.
14259 o Minor features (speed):
14260 - When implementing AES counter mode, update only the portions of the
14261 counter buffer that need to change, and don't keep separate
14262 network-order and host-order counters when they are the same (i.e.,
14263 on big-endian hosts.)
14265 o Minor features (controller):
14266 - Accept LF instead of CRLF on controller, since some software has a
14267 hard time generating real Internet newlines.
14268 - Add GETINFO values for the server status events
14269 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
14272 o Removed features:
14273 - Routers no longer include bandwidth-history lines in their
14274 descriptors; this information is already available in extra-info
14275 documents, and including it in router descriptors took up 60%
14276 (!) of compressed router descriptor downloads. Completes
14277 implementation of proposal 104.
14278 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
14279 and TorControl.py, as they use the old v0 controller protocol,
14280 and are obsoleted by TorFlow anyway.
14281 - Drop support for v1 rendezvous descriptors, since we never used
14282 them anyway, and the code has probably rotted by now. Based on
14283 patch from Karsten Loesing.
14284 - On OSX, stop warning the user that kqueue support in libevent is
14285 "experimental", since it seems to have worked fine for ages.
14288 - When generating information telling us how to extend to a given
14289 router, do not try to include the nickname if it is absent. Fixes
14290 bug 467. Bugfix on 0.2.0.3-alpha.
14291 - Fix a user-triggerable (but not remotely-triggerable) segfault
14292 in expand_filename(). Bugfix on 0.1.2.x.
14293 - Fix a memory leak when freeing incomplete requests from DNSPort.
14294 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
14295 - Don't try to access (or alter) the state file when running
14296 --list-fingerprint or --verify-config or --hash-password. (Resolves
14297 bug 499.) Bugfix on 0.1.2.x.
14298 - Servers used to decline to publish their DirPort if their
14299 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
14300 were below a threshold. Now they only look at BandwidthRate and
14301 RelayBandwidthRate. Bugfix on 0.1.2.x.
14302 - Remove an optimization in the AES counter-mode code that assumed
14303 that the counter never exceeded 2^68. When the counter can be set
14304 arbitrarily as an IV (as it is by Karsten's new hidden services
14305 code), this assumption no longer holds. Bugfix on 0.1.2.x.
14306 - Resume listing "AUTHORITY" flag for authorities in network status.
14307 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
14309 o Code simplifications and refactoring:
14310 - Revamp file-writing logic so we don't need to have the entire
14311 contents of a file in memory at once before we write to disk. Tor,
14313 - Turn "descriptor store" into a full-fledged type.
14314 - Move all NT services code into a separate source file.
14315 - Unify all code that computes medians, percentile elements, etc.
14316 - Get rid of a needless malloc when parsing address policies.
14319 Changes in version 0.1.2.17 - 2007-08-30
14320 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
14321 X bundles. Vidalia 0.0.14 makes authentication required for the
14322 ControlPort in the default configuration, which addresses important
14323 security risks. Everybody who uses Vidalia (or another controller)
14326 In addition, this Tor update fixes major load balancing problems with
14327 path selection, which should speed things up a lot once many people
14330 o Major bugfixes (security):
14331 - We removed support for the old (v0) control protocol. It has been
14332 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
14333 become more of a headache than it's worth.
14335 o Major bugfixes (load balancing):
14336 - When choosing nodes for non-guard positions, weight guards
14337 proportionally less, since they already have enough load. Patch
14339 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14340 will allow fast Tor servers to get more attention.
14341 - When we're upgrading from an old Tor version, forget our current
14342 guards and pick new ones according to the new weightings. These
14343 three load balancing patches could raise effective network capacity
14344 by a factor of four. Thanks to Mike Perry for measurements.
14346 o Major bugfixes (stream expiration):
14347 - Expire not-yet-successful application streams in all cases if
14348 they've been around longer than SocksTimeout. Right now there are
14349 some cases where the stream will live forever, demanding a new
14350 circuit every 15 seconds. Fixes bug 454; reported by lodger.
14352 o Minor features (controller):
14353 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14354 is valid before any authentication has been received. It tells
14355 a controller what kind of authentication is expected, and what
14356 protocol is spoken. Implements proposal 119.
14358 o Minor bugfixes (performance):
14359 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
14360 greatly speeding up loading cached-routers from disk on startup.
14361 - Disable sentinel-based debugging for buffer code: we squashed all
14362 the bugs that this was supposed to detect a long time ago, and now
14363 its only effect is to change our buffer sizes from nice powers of
14364 two (which platform mallocs tend to like) to values slightly over
14365 powers of two (which make some platform mallocs sad).
14367 o Minor bugfixes (misc):
14368 - If exit bandwidth ever exceeds one third of total bandwidth, then
14369 use the correct formula to weight exit nodes when choosing paths.
14370 Based on patch from Mike Perry.
14371 - Choose perfectly fairly among routers when choosing by bandwidth and
14372 weighting by fraction of bandwidth provided by exits. Previously, we
14373 would choose with only approximate fairness, and correct ourselves
14374 if we ran off the end of the list.
14375 - If we require CookieAuthentication but we fail to write the
14376 cookie file, we would warn but not exit, and end up in a state
14377 where no controller could authenticate. Now we exit.
14378 - If we require CookieAuthentication, stop generating a new cookie
14379 every time we change any piece of our config.
14380 - Refuse to start with certain directory authority keys, and
14381 encourage people using them to stop.
14382 - Terminate multi-line control events properly. Original patch
14384 - Fix a minor memory leak when we fail to find enough suitable
14385 servers to choose a circuit.
14386 - Stop leaking part of the descriptor when we run into a particularly
14387 unparseable piece of it.
14390 Changes in version 0.2.0.6-alpha - 2007-08-26
14391 This sixth development snapshot features a new Vidalia version in the
14392 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
14393 the ControlPort in the default configuration, which addresses important
14396 In addition, this snapshot fixes major load balancing problems
14397 with path selection, which should speed things up a lot once many
14398 people have upgraded. The directory authorities also use a new
14399 mean-time-between-failure approach to tracking which servers are stable,
14400 rather than just looking at the most recent uptime.
14402 o New directory authorities:
14403 - Set up Tonga as the default bridge directory authority.
14406 - Directory authorities now track servers by weighted
14407 mean-times-between-failures. When we have 4 or more days of data,
14408 use measured MTBF rather than declared uptime to decide whether
14409 to call a router Stable. Implements proposal 108.
14411 o Major bugfixes (load balancing):
14412 - When choosing nodes for non-guard positions, weight guards
14413 proportionally less, since they already have enough load. Patch
14415 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14416 will allow fast Tor servers to get more attention.
14417 - When we're upgrading from an old Tor version, forget our current
14418 guards and pick new ones according to the new weightings. These
14419 three load balancing patches could raise effective network capacity
14420 by a factor of four. Thanks to Mike Perry for measurements.
14422 o Major bugfixes (descriptor parsing):
14423 - Handle unexpected whitespace better in malformed descriptors. Bug
14424 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
14427 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14428 GETINFO for Torstat to use until it can switch to using extrainfos.
14429 - Optionally (if built with -DEXPORTMALLINFO) export the output
14430 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14434 - Do not intermix bridge routers with controller-added
14435 routers. (Bugfix on 0.2.0.x)
14436 - Do not fail with an assert when accept() returns an unexpected
14437 address family. Addresses but does not wholly fix bug 483. (Bugfix
14439 - Let directory authorities startup even when they can't generate
14440 a descriptor immediately, e.g. because they don't know their
14442 - Stop putting the authentication cookie in a file called "0"
14443 in your working directory if you don't specify anything for the
14444 new CookieAuthFile option. Reported by Matt Edman.
14445 - Make it possible to read the PROTOCOLINFO response in a way that
14446 conforms to our control-spec. Reported by Matt Edman.
14447 - Fix a minor memory leak when we fail to find enough suitable
14448 servers to choose a circuit. Bugfix on 0.1.2.x.
14449 - Stop leaking part of the descriptor when we run into a particularly
14450 unparseable piece of it. Bugfix on 0.1.2.x.
14451 - Unmap the extrainfo cache file on exit.
14454 Changes in version 0.2.0.5-alpha - 2007-08-19
14455 This fifth development snapshot fixes compilation on Windows again;
14456 fixes an obnoxious client-side bug that slowed things down and put
14457 extra load on the network; gets us closer to using the v3 directory
14458 voting scheme; makes it easier for Tor controllers to use cookie-based
14459 authentication; and fixes a variety of other bugs.
14461 o Removed features:
14462 - Version 1 directories are no longer generated in full. Instead,
14463 authorities generate and serve "stub" v1 directories that list
14464 no servers. This will stop Tor versions 0.1.0.x and earlier from
14465 working, but (for security reasons) nobody should be running those
14468 o Major bugfixes (compilation, 0.2.0.x):
14469 - Try to fix Win32 compilation again: improve checking for IPv6 types.
14470 - Try to fix MSVC compilation: build correctly on platforms that do
14471 not define s6_addr16 or s6_addr32.
14472 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
14475 o Major bugfixes (stream expiration):
14476 - Expire not-yet-successful application streams in all cases if
14477 they've been around longer than SocksTimeout. Right now there are
14478 some cases where the stream will live forever, demanding a new
14479 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
14480 reported by lodger.
14482 o Minor features (directory servers):
14483 - When somebody requests a list of statuses or servers, and we have
14484 none of those, return a 404 rather than an empty 200.
14486 o Minor features (directory voting):
14487 - Store v3 consensus status consensuses on disk, and reload them
14490 o Minor features (security):
14491 - Warn about unsafe ControlPort configurations.
14492 - Refuse to start with certain directory authority keys, and
14493 encourage people using them to stop.
14495 o Minor features (controller):
14496 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14497 is valid before any authentication has been received. It tells
14498 a controller what kind of authentication is expected, and what
14499 protocol is spoken. Implements proposal 119.
14500 - New config option CookieAuthFile to choose a new location for the
14501 cookie authentication file, and config option
14502 CookieAuthFileGroupReadable to make it group-readable.
14504 o Minor features (unit testing):
14505 - Add command-line arguments to unit-test executable so that we can
14506 invoke any chosen test from the command line rather than having
14507 to run the whole test suite at once; and so that we can turn on
14508 logging for the unit tests.
14510 o Minor bugfixes (on 0.1.2.x):
14511 - If we require CookieAuthentication but we fail to write the
14512 cookie file, we would warn but not exit, and end up in a state
14513 where no controller could authenticate. Now we exit.
14514 - If we require CookieAuthentication, stop generating a new cookie
14515 every time we change any piece of our config.
14516 - When loading bandwidth history, do not believe any information in
14517 the future. Fixes bug 434.
14518 - When loading entry guard information, do not believe any information
14520 - When we have our clock set far in the future and generate an
14521 onion key, then re-set our clock to be correct, we should not stop
14522 the onion key from getting rotated.
14523 - Clean up torrc sample config file.
14524 - Do not automatically run configure from autogen.sh. This
14525 non-standard behavior tended to annoy people who have built other
14528 o Minor bugfixes (on 0.2.0.x):
14529 - Fix a bug with AutomapHostsOnResolve that would always cause
14530 the second request to fail. Bug reported by Kate. Bugfix on
14532 - Fix a bug in ADDRMAP controller replies that would sometimes
14533 try to print a NULL. Patch from tup.
14534 - Read v3 directory authority keys from the right location.
14535 - Numerous bugfixes to directory voting code.
14538 Changes in version 0.1.2.16 - 2007-08-01
14539 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
14540 remote attacker in certain situations to rewrite the user's torrc
14541 configuration file. This can completely compromise anonymity of users
14542 in most configurations, including those running the Vidalia bundles,
14543 TorK, etc. Or worse.
14545 o Major security fixes:
14546 - Close immediately after missing authentication on control port;
14547 do not allow multiple authentication attempts.
14550 Changes in version 0.2.0.4-alpha - 2007-08-01
14551 This fourth development snapshot fixes a critical security vulnerability
14552 for most users, specifically those running Vidalia, TorK, etc. Everybody
14553 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
14555 o Major security fixes:
14556 - Close immediately after missing authentication on control port;
14557 do not allow multiple authentication attempts.
14559 o Major bugfixes (compilation):
14560 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
14563 o Minor features (performance):
14564 - Be even more aggressive about releasing RAM from small
14565 empty buffers. Thanks to our free-list code, this shouldn't be too
14566 performance-intensive.
14567 - Disable sentinel-based debugging for buffer code: we squashed all
14568 the bugs that this was supposed to detect a long time ago, and
14569 now its only effect is to change our buffer sizes from nice
14570 powers of two (which platform mallocs tend to like) to values
14571 slightly over powers of two (which make some platform mallocs sad).
14572 - Log malloc statistics from mallinfo() on platforms where it
14576 Changes in version 0.2.0.3-alpha - 2007-07-29
14577 This third development snapshot introduces new experimental
14578 blocking-resistance features and a preliminary version of the v3
14579 directory voting design, and includes many other smaller features
14583 - The first pieces of our "bridge" design for blocking-resistance
14584 are implemented. People can run bridge directory authorities;
14585 people can run bridges; and people can configure their Tor clients
14586 with a set of bridges to use as the first hop into the Tor network.
14587 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
14589 - Create listener connections before we setuid to the configured
14590 User and Group. Now non-Windows users can choose port values
14591 under 1024, start Tor as root, and have Tor bind those ports
14592 before it changes to another UID. (Windows users could already
14594 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14595 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14596 on "vserver" accounts. (Patch from coderman.)
14597 - Be even more aggressive about separating local traffic from relayed
14598 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
14600 o Major features (experimental):
14601 - First cut of code for "v3 dir voting": directory authorities will
14602 vote on a common network status document rather than each publishing
14603 their own opinion. This code needs more testing and more corner-case
14604 handling before it's ready for use.
14607 - Directory authorities now call routers Fast if their bandwidth is
14608 at least 100KB/s, and consider their bandwidth adequate to be a
14609 Guard if it is at least 250KB/s, no matter the medians. This fix
14610 complements proposal 107. [Bugfix on 0.1.2.x]
14611 - Directory authorities now never mark more than 3 servers per IP as
14612 Valid and Running. (Implements proposal 109, by Kevin Bauer and
14614 - Minor change to organizationName and commonName generation
14615 procedures in TLS certificates during Tor handshakes, to invalidate
14616 some earlier censorware approaches. This is not a long-term
14617 solution, but applying it will give us a bit of time to look into
14618 the epidemiology of countermeasures as they spread.
14620 o Major bugfixes (directory):
14621 - Rewrite directory tokenization code to never run off the end of
14622 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
14624 o Minor features (controller):
14625 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
14626 match requests to applications. (Patch from Robert Hogan.)
14627 - Report address and port correctly on connections to DNSPort. (Patch
14628 from Robert Hogan.)
14629 - Add a RESOLVE command to launch hostname lookups. (Original patch
14630 from Robert Hogan.)
14631 - Add GETINFO status/enough-dir-info to let controllers tell whether
14632 Tor has downloaded sufficient directory information. (Patch
14634 - You can now use the ControlSocket option to tell Tor to listen for
14635 controller connections on Unix domain sockets on systems that
14636 support them. (Patch from Peter Palfrader.)
14637 - STREAM NEW events are generated for DNSPort requests and for
14638 tunneled directory connections. (Patch from Robert Hogan.)
14639 - New "GETINFO address-mappings/*" command to get address mappings
14640 with expiry information. "addr-mappings/*" is now deprecated.
14643 o Minor features (misc):
14644 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
14646 - The tor-gencert tool for v3 directory authorities now creates all
14647 files as readable to the file creator only, and write-protects
14648 the authority identity key.
14649 - When dumping memory usage, list bytes used in buffer memory
14651 - When running with dmalloc, dump more stats on hup and on exit.
14652 - Directory authorities now fail quickly and (relatively) harmlessly
14653 if they generate a network status document that is somehow
14656 o Traffic load balancing improvements:
14657 - If exit bandwidth ever exceeds one third of total bandwidth, then
14658 use the correct formula to weight exit nodes when choosing paths.
14659 (Based on patch from Mike Perry.)
14660 - Choose perfectly fairly among routers when choosing by bandwidth and
14661 weighting by fraction of bandwidth provided by exits. Previously, we
14662 would choose with only approximate fairness, and correct ourselves
14663 if we ran off the end of the list. [Bugfix on 0.1.2.x]
14665 o Performance improvements:
14666 - Be more aggressive with freeing buffer RAM or putting it on the
14668 - Use Critical Sections rather than Mutexes for synchronizing threads
14669 on win32; Mutexes are heavier-weight, and designed for synchronizing
14672 o Deprecated and removed features:
14673 - RedirectExits is now deprecated.
14674 - Stop allowing address masks that do not correspond to bit prefixes.
14675 We have warned about these for a really long time; now it's time
14676 to reject them. (Patch from croup.)
14678 o Minor bugfixes (directory):
14679 - Fix another crash bug related to extra-info caching. (Bug found by
14680 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
14681 - Directories no longer return a "304 not modified" when they don't
14682 have the networkstatus the client asked for. Also fix a memory
14683 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
14684 - We had accidentally labelled 0.1.2.x directory servers as not
14685 suitable for begin_dir requests, and had labelled no directory
14686 servers as suitable for uploading extra-info documents. [Bugfix
14689 o Minor bugfixes (dns):
14690 - Fix a crash when DNSPort is set more than once. (Patch from Robert
14691 Hogan.) [Bugfix on 0.2.0.2-alpha]
14692 - Add DNSPort connections to the global connection list, so that we
14693 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
14695 - Fix a dangling reference that could lead to a crash when DNSPort is
14696 changed or closed (Patch from Robert Hogan.) [Bugfix on
14699 o Minor bugfixes (controller):
14700 - Provide DNS expiry times in GMT, not in local time. For backward
14701 compatibility, ADDRMAP events only provide GMT expiry in an extended
14702 field. "GETINFO address-mappings" always does the right thing.
14703 - Use CRLF line endings properly in NS events.
14704 - Terminate multi-line control events properly. (Original patch
14705 from tup.) [Bugfix on 0.1.2.x-alpha]
14706 - Do not include spaces in SOURCE_ADDR fields in STREAM
14707 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
14710 Changes in version 0.1.2.15 - 2007-07-17
14711 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
14712 problems, fixes compilation on BSD, and fixes a variety of other
14713 bugs. Everybody should upgrade.
14715 o Major bugfixes (compilation):
14716 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
14718 o Major bugfixes (crashes):
14719 - Try even harder not to dereference the first character after
14720 an mmap(). Reported by lodger.
14721 - Fix a crash bug in directory authorities when we re-number the
14722 routerlist while inserting a new router.
14723 - When the cached-routers file is an even multiple of the page size,
14724 don't run off the end and crash. (Fixes bug 455; based on idea
14726 - Fix eventdns.c behavior on Solaris: It is critical to include
14727 orconfig.h _before_ sys/types.h, so that we can get the expected
14728 definition of _FILE_OFFSET_BITS.
14730 o Major bugfixes (security):
14731 - Fix a possible buffer overrun when using BSD natd support. Bug
14733 - When sending destroy cells from a circuit's origin, don't include
14734 the reason for tearing down the circuit. The spec says we didn't,
14735 and now we actually don't. Reported by lodger.
14736 - Keep streamids from different exits on a circuit separate. This
14737 bug may have allowed other routers on a given circuit to inject
14738 cells into streams. Reported by lodger; fixes bug 446.
14739 - If there's a never-before-connected-to guard node in our list,
14740 never choose any guards past it. This way we don't expand our
14741 guard list unless we need to.
14743 o Minor bugfixes (guard nodes):
14744 - Weight guard selection by bandwidth, so that low-bandwidth nodes
14745 don't get overused as guards.
14747 o Minor bugfixes (directory):
14748 - Correctly count the number of authorities that recommend each
14749 version. Previously, we were under-counting by 1.
14750 - Fix a potential crash bug when we load many server descriptors at
14751 once and some of them make others of them obsolete. Fixes bug 458.
14753 o Minor bugfixes (hidden services):
14754 - Stop tearing down the whole circuit when the user asks for a
14755 connection to a port that the hidden service didn't configure.
14758 o Minor bugfixes (misc):
14759 - On Windows, we were preventing other processes from reading
14760 cached-routers while Tor was running. Reported by janbar.
14761 - Fix a possible (but very unlikely) bug in picking routers by
14762 bandwidth. Add a log message to confirm that it is in fact
14763 unlikely. Patch from lodger.
14764 - Backport a couple of memory leak fixes.
14765 - Backport miscellaneous cosmetic bugfixes.
14768 Changes in version 0.2.0.2-alpha - 2007-06-02
14769 o Major bugfixes on 0.2.0.1-alpha:
14770 - Fix an assertion failure related to servers without extra-info digests.
14771 Resolves bugs 441 and 442.
14773 o Minor features (directory):
14774 - Support "If-Modified-Since" when answering HTTP requests for
14775 directories, running-routers documents, and network-status documents.
14776 (There's no need to support it for router descriptors, since those
14777 are downloaded by descriptor digest.)
14779 o Minor build issues:
14780 - Clear up some MIPSPro compiler warnings.
14781 - When building from a tarball on a machine that happens to have SVK
14782 installed, report the micro-revision as whatever version existed
14783 in the tarball, not as "x".
14786 Changes in version 0.2.0.1-alpha - 2007-06-01
14787 This early development snapshot provides new features for people running
14788 Tor as both a client and a server (check out the new RelayBandwidth
14789 config options); lets Tor run as a DNS proxy; and generally moves us
14790 forward on a lot of fronts.
14792 o Major features, server usability:
14793 - New config options RelayBandwidthRate and RelayBandwidthBurst:
14794 a separate set of token buckets for relayed traffic. Right now
14795 relayed traffic is defined as answers to directory requests, and
14796 OR connections that don't have any local circuits on them.
14798 o Major features, client usability:
14799 - A client-side DNS proxy feature to replace the need for
14800 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
14801 for DNS requests on port 9999, use the Tor network to resolve them
14802 anonymously, and send the reply back like a regular DNS server.
14803 The code still only implements a subset of DNS.
14804 - Make PreferTunneledDirConns and TunnelDirConns work even when
14805 we have no cached directory info. This means Tor clients can now
14806 do all of their connections protected by TLS.
14808 o Major features, performance and efficiency:
14809 - Directory authorities accept and serve "extra info" documents for
14810 routers. These documents contain fields from router descriptors
14811 that aren't usually needed, and that use a lot of excess
14812 bandwidth. Once these fields are removed from router descriptors,
14813 the bandwidth savings should be about 60%. [Partially implements
14815 - Servers upload extra-info documents to any authority that accepts
14816 them. Authorities (and caches that have been configured to download
14817 extra-info documents) download them as needed. [Partially implements
14819 - Change the way that Tor buffers data that it is waiting to write.
14820 Instead of queueing data cells in an enormous ring buffer for each
14821 client->OR or OR->OR connection, we now queue cells on a separate
14822 queue for each circuit. This lets us use less slack memory, and
14823 will eventually let us be smarter about prioritizing different kinds
14825 - Use memory pools to allocate cells with better speed and memory
14826 efficiency, especially on platforms where malloc() is inefficient.
14827 - Stop reading on edge connections when their corresponding circuit
14828 buffers are full; start again as the circuits empty out.
14830 o Major features, other:
14831 - Add an HSAuthorityRecordStats option that hidden service authorities
14832 can use to track statistics of overall hidden service usage without
14833 logging information that would be very useful to an attacker.
14834 - Start work implementing multi-level keys for directory authorities:
14835 Add a standalone tool to generate key certificates. (Proposal 103.)
14838 - Directory authorities now call routers Stable if they have an
14839 uptime of at least 30 days, even if that's not the median uptime
14840 in the network. Implements proposal 107, suggested by Kevin Bauer
14843 o Minor fixes (resource management):
14844 - Count the number of open sockets separately from the number
14845 of active connection_t objects. This will let us avoid underusing
14846 our allocated connection limit.
14847 - We no longer use socket pairs to link an edge connection to an
14848 anonymous directory connection or a DirPort test connection.
14849 Instead, we track the link internally and transfer the data
14850 in-process. This saves two sockets per "linked" connection (at the
14851 client and at the server), and avoids the nasty Windows socketpair()
14853 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14854 for every single inactive connection_t. Free items from the
14855 4k/16k-buffer free lists when they haven't been used for a while.
14857 o Minor features (build):
14858 - Make autoconf search for libevent, openssl, and zlib consistently.
14859 - Update deprecated macros in configure.in.
14860 - When warning about missing headers, tell the user to let us
14861 know if the compile succeeds anyway, so we can downgrade the
14863 - Include the current subversion revision as part of the version
14864 string: either fetch it directly if we're in an SVN checkout, do
14865 some magic to guess it if we're in an SVK checkout, or use
14866 the last-detected version if we're building from a .tar.gz.
14867 Use this version consistently in log messages.
14869 o Minor features (logging):
14870 - Always prepend "Bug: " to any log message about a bug.
14871 - Put a platform string (e.g. "Linux i686") in the startup log
14872 message, so when people paste just their logs, we know if it's
14873 OpenBSD or Windows or what.
14874 - When logging memory usage, break down memory used in buffers by
14877 o Minor features (directory system):
14878 - New config option V2AuthoritativeDirectory that all directory
14879 authorities should set. This will let future authorities choose
14880 not to serve V2 directory information.
14881 - Directory authorities allow multiple router descriptors and/or extra
14882 info documents to be uploaded in a single go. This will make
14883 implementing proposal 104 simpler.
14885 o Minor features (controller):
14886 - Add a new config option __DisablePredictedCircuits designed for
14887 use by the controller, when we don't want Tor to build any circuits
14889 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
14890 so we can exit from the middle of the circuit.
14891 - Implement "getinfo status/circuit-established".
14892 - Implement "getinfo status/version/..." so a controller can tell
14893 whether the current version is recommended, and whether any versions
14894 are good, and how many authorities agree. (Patch from shibz.)
14896 o Minor features (hidden services):
14897 - Allow multiple HiddenServicePort directives with the same virtual
14898 port; when they occur, the user is sent round-robin to one
14899 of the target ports chosen at random. Partially fixes bug 393 by
14900 adding limited ad-hoc round-robining.
14902 o Minor features (other):
14904 - Add a new AutomapHostsOnResolve option: when it is enabled, any
14905 resolve request for hosts matching a given pattern causes Tor to
14906 generate an internal virtual address mapping for that host. This
14907 allows DNSPort to work sensibly with hidden service users. By
14908 default, .exit and .onion addresses are remapped; the list of
14909 patterns can be reconfigured with AutomapHostsSuffixes.
14910 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14911 address. Thanks to the AutomapHostsOnResolve option, this is no
14912 longer a completely silly thing to do.
14913 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14914 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14915 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14916 minus 1 byte: the actual maximum declared bandwidth.
14918 o Removed features:
14919 - Removed support for the old binary "version 0" controller protocol.
14920 This has been deprecated since 0.1.1, and warnings have been issued
14921 since 0.1.2. When we encounter a v0 control message, we now send
14922 back an error and close the connection.
14923 - Remove the old "dns worker" server DNS code: it hasn't been default
14924 since 0.1.2.2-alpha, and all the servers seem to be using the new
14927 o Minor bugfixes (portability):
14928 - Even though Windows is equally happy with / and \ as path separators,
14929 try to use \ consistently on Windows and / consistently on Unix: it
14930 makes the log messages nicer.
14931 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
14932 - Read resolv.conf files correctly on platforms where read() returns
14933 partial results on small file reads.
14935 o Minor bugfixes (directory):
14936 - Correctly enforce that elements of directory objects do not appear
14937 more often than they are allowed to appear.
14938 - When we are reporting the DirServer line we just parsed, we were
14939 logging the second stanza of the key fingerprint, not the first.
14941 o Minor bugfixes (logging):
14942 - When we hit an EOF on a log (probably because we're shutting down),
14943 don't try to remove the log from the list: just mark it as
14944 unusable. (Bulletproofs against bug 222.)
14946 o Minor bugfixes (other):
14947 - In the exitlist script, only consider the most recently published
14948 server descriptor for each server. Also, when the user requests
14949 a list of servers that _reject_ connections to a given address,
14950 explicitly exclude the IPs that also have servers that accept
14951 connections to that address. (Resolves bug 405.)
14952 - Stop allowing hibernating servers to be "stable" or "fast".
14953 - On Windows, we were preventing other processes from reading
14954 cached-routers while Tor was running. (Reported by janbar)
14955 - Make the NodeFamilies config option work. (Reported by
14956 lodger -- it has never actually worked, even though we added it
14958 - Check return values from pthread_mutex functions.
14959 - Don't save non-general-purpose router descriptors to the disk cache,
14960 because we have no way of remembering what their purpose was when
14962 - Add even more asserts to hunt down bug 417.
14963 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
14964 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
14965 Add a log message to confirm that it is in fact unlikely.
14967 o Minor bugfixes (controller):
14968 - Make 'getinfo fingerprint' return a 551 error if we're not a
14969 server, so we match what the control spec claims we do. Reported
14971 - Fix a typo in an error message when extendcircuit fails that
14972 caused us to not follow the \r\n-based delimiter protocol. Reported
14975 o Code simplifications and refactoring:
14976 - Stop passing around circuit_t and crypt_path_t pointers that are
14977 implicit in other procedure arguments.
14978 - Drop the old code to choke directory connections when the
14979 corresponding OR connections got full: thanks to the cell queue
14980 feature, OR conns don't get full any more.
14981 - Make dns_resolve() handle attaching connections to circuits
14982 properly, so the caller doesn't have to.
14983 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
14984 - Keep the connection array as a dynamic smartlist_t, rather than as
14985 a fixed-sized array. This is important, as the number of connections
14986 is becoming increasingly decoupled from the number of sockets.
14989 Changes in version 0.1.2.14 - 2007-05-25
14990 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14991 change especially affects those who serve or use hidden services),
14992 and fixes several other crash- and security-related bugs.
14994 o Directory authority changes:
14995 - Two directory authorities (moria1 and moria2) just moved to new
14996 IP addresses. This change will particularly affect those who serve
14997 or use hidden services.
14999 o Major bugfixes (crashes):
15000 - If a directory server runs out of space in the connection table
15001 as it's processing a begin_dir request, it will free the exit stream
15002 but leave it attached to the circuit, leading to unpredictable
15003 behavior. (Reported by seeess, fixes bug 425.)
15004 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15005 to corrupt memory under some really unlikely scenarios.
15006 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15007 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15010 o Major bugfixes (security):
15011 - When choosing an entry guard for a circuit, avoid using guards
15012 that are in the same family as the chosen exit -- not just guards
15013 that are exactly the chosen exit. (Reported by lodger.)
15015 o Major bugfixes (resource management):
15016 - If a directory authority is down, skip it when deciding where to get
15017 networkstatus objects or descriptors. Otherwise we keep asking
15018 every 10 seconds forever. Fixes bug 384.
15019 - Count it as a failure if we fetch a valid network-status but we
15020 don't want to keep it. Otherwise we'll keep fetching it and keep
15021 not wanting to keep it. Fixes part of bug 422.
15022 - If all of our dirservers have given us bad or no networkstatuses
15023 lately, then stop hammering them once per minute even when we
15024 think they're failed. Fixes another part of bug 422.
15027 - Actually set the purpose correctly for descriptors inserted with
15028 purpose=controller.
15029 - When we have k non-v2 authorities in our DirServer config,
15030 we ignored the last k authorities in the list when updating our
15032 - Correctly back-off from requesting router descriptors that we are
15033 having a hard time downloading.
15034 - Read resolv.conf files correctly on platforms where read() returns
15035 partial results on small file reads.
15036 - Don't rebuild the entire router store every time we get 32K of
15037 routers: rebuild it when the journal gets very large, or when
15038 the gaps in the store get very large.
15041 - When routers publish SVN revisions in their router descriptors,
15042 authorities now include those versions correctly in networkstatus
15044 - Warn when using a version of libevent before 1.3b to run a server on
15045 OSX or BSD: these versions interact badly with userspace threads.
15048 Changes in version 0.1.2.13 - 2007-04-24
15049 This release features some major anonymity fixes, such as safer path
15050 selection; better client performance; faster bootstrapping, better
15051 address detection, and better DNS support for servers; write limiting as
15052 well as read limiting to make servers easier to run; and a huge pile of
15053 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15055 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15056 of the Freenode IRC network, remembering his patience and vision for
15057 free speech on the Internet.
15060 - Fix a memory leak when we ask for "all" networkstatuses and we
15061 get one we don't recognize.
15062 - Add more asserts to hunt down bug 417.
15063 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15066 Changes in version 0.1.2.12-rc - 2007-03-16
15068 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
15069 directory information requested inside Tor connections (i.e. via
15070 begin_dir cells). It only triggered when the same connection was
15071 serving other data at the same time. Reported by seeess.
15074 - When creating a circuit via the controller, send a 'launched'
15075 event when we're done, so we follow the spec better.
15078 Changes in version 0.1.2.11-rc - 2007-03-15
15079 o Minor bugfixes (controller), reported by daejees:
15080 - Correct the control spec to match how the code actually responds
15081 to 'getinfo addr-mappings/*'.
15082 - The control spec described a GUARDS event, but the code
15083 implemented a GUARD event. Standardize on GUARD, but let people
15084 ask for GUARDS too.
15087 Changes in version 0.1.2.10-rc - 2007-03-07
15088 o Major bugfixes (Windows):
15089 - Do not load the NT services library functions (which may not exist)
15090 just to detect if we're a service trying to shut down. Now we run
15091 on Win98 and friends again.
15093 o Minor bugfixes (other):
15094 - Clarify a couple of log messages.
15095 - Fix a misleading socks5 error number.
15098 Changes in version 0.1.2.9-rc - 2007-03-02
15099 o Major bugfixes (Windows):
15100 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
15101 of the usual GCC "%llu". This prevents a bug when saving 64-bit
15102 int configuration values: the high-order 32 bits would get
15103 truncated. In particular, we were being bitten by the default
15104 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
15105 and maybe also bug 397.)
15107 o Minor bugfixes (performance):
15108 - Use OpenSSL's AES implementation on platforms where it's faster.
15109 This could save us as much as 10% CPU usage.
15111 o Minor bugfixes (server):
15112 - Do not rotate onion key immediately after setting it for the first
15115 o Minor bugfixes (directory authorities):
15116 - Stop calling servers that have been hibernating for a long time
15117 "stable". Also, stop letting hibernating or obsolete servers affect
15118 uptime and bandwidth cutoffs.
15119 - Stop listing hibernating servers in the v1 directory.
15121 o Minor bugfixes (hidden services):
15122 - Upload hidden service descriptors slightly less often, to reduce
15123 load on authorities.
15125 o Minor bugfixes (other):
15126 - Fix an assert that could trigger if a controller quickly set then
15127 cleared EntryNodes. Bug found by Udo van den Heuvel.
15128 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
15130 - Fix a potential race condition in the rpm installer. Found by
15132 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
15133 of 2 as indicating that the server is completely bad; it sometimes
15134 means that the server is just bad for the request in question. (may fix
15135 the last of bug 326.)
15136 - Disable encrypted directory connections when we don't have a server
15137 descriptor for the destination. We'll get this working again in
15141 Changes in version 0.1.2.8-beta - 2007-02-26
15142 o Major bugfixes (crashes):
15143 - Stop crashing when the controller asks us to resetconf more than
15144 one config option at once. (Vidalia 0.0.11 does this.)
15145 - Fix a crash that happened on Win98 when we're given command-line
15146 arguments: don't try to load NT service functions from advapi32.dll
15147 except when we need them. (Bug introduced in 0.1.2.7-alpha;
15149 - Fix a longstanding obscure crash bug that could occur when
15150 we run out of DNS worker processes. (Resolves bug 390.)
15152 o Major bugfixes (hidden services):
15153 - Correctly detect whether hidden service descriptor downloads are
15154 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
15156 o Major bugfixes (accounting):
15157 - When we start during an accounting interval before it's time to wake
15158 up, remember to wake up at the correct time. (May fix bug 342.)
15160 o Minor bugfixes (controller):
15161 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15162 clear the corresponding on_circuit variable, and remember later
15163 that we don't need to send a redundant CLOSED event. Resolves part
15165 - Report events where a resolve succeeded or where we got a socks
15166 protocol error correctly, rather than calling both of them
15168 - Change reported stream target addresses to IP consistently when
15169 we finally get the IP from an exit node.
15170 - Send log messages to the controller even if they happen to be very
15173 o Minor bugfixes (other):
15174 - Display correct results when reporting which versions are
15175 recommended, and how recommended they are. (Resolves bug 383.)
15176 - Improve our estimates for directory bandwidth to be less random:
15177 guess that an unrecognized directory will have the average bandwidth
15178 from all known directories, not that it will have the average
15179 bandwidth from those directories earlier than it on the list.
15180 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15181 and hup, stop triggering an assert based on an empty onion_key.
15182 - On platforms with no working mmap() equivalent, don't warn the
15183 user when cached-routers doesn't exist.
15184 - Warn the user when mmap() [or its equivalent] fails for some reason
15185 other than file-not-found.
15186 - Don't warn the user when cached-routers.new doesn't exist: that's
15187 perfectly fine when starting up for the first time.
15188 - When EntryNodes are configured, rebuild the guard list to contain,
15189 in order: the EntryNodes that were guards before; the rest of the
15190 EntryNodes; the nodes that were guards before.
15191 - Mask out all signals in sub-threads; only the libevent signal
15192 handler should be processing them. This should prevent some crashes
15193 on some machines using pthreads. (Patch from coderman.)
15194 - Fix switched arguments on memset in the implementation of
15195 tor_munmap() for systems with no mmap() call.
15196 - When Tor receives a router descriptor that it asked for, but
15197 no longer wants (because it has received fresh networkstatuses
15198 in the meantime), do not warn the user. Cache the descriptor if
15199 we're a cache; drop it if we aren't.
15200 - Make earlier entry guards _really_ get retried when the network
15202 - On a malformed DNS reply, always give an error to the corresponding
15204 - Build with recent libevents on platforms that do not define the
15205 nonstandard types "u_int8_t" and friends.
15207 o Minor features (controller):
15208 - Warn the user when an application uses the obsolete binary v0
15209 control protocol. We're planning to remove support for it during
15210 the next development series, so it's good to give people some
15212 - Add STREAM_BW events to report per-entry-stream bandwidth
15213 use. (Patch from Robert Hogan.)
15214 - Rate-limit SIGNEWNYM signals in response to controllers that
15215 impolitely generate them for every single stream. (Patch from
15216 mwenge; closes bug 394.)
15217 - Make REMAP stream events have a SOURCE (cache or exit), and
15218 make them generated in every case where we get a successful
15219 connected or resolved cell.
15221 o Minor bugfixes (performance):
15222 - Call router_have_min_dir_info half as often. (This is showing up in
15223 some profiles, but not others.)
15224 - When using GCC, make log_debug never get called at all, and its
15225 arguments never get evaluated, when no debug logs are configured.
15226 (This is showing up in some profiles, but not others.)
15229 - Remove some never-implemented options. Mark PathlenCoinWeight as
15231 - Implement proposal 106: Stop requiring clients to have well-formed
15232 certificates; stop checking nicknames in certificates. (Clients
15233 have certificates so that they can look like Tor servers, but in
15234 the future we might want to allow them to look like regular TLS
15235 clients instead. Nicknames in certificates serve no purpose other
15236 than making our protocol easier to recognize on the wire.)
15237 - Revise messages on handshake failure again to be even more clear about
15238 which are incoming connections and which are outgoing.
15239 - Discard any v1 directory info that's over 1 month old (for
15240 directories) or over 1 week old (for running-routers lists).
15241 - Do not warn when individual nodes in the configuration's EntryNodes,
15242 ExitNodes, etc are down: warn only when all possible nodes
15243 are down. (Fixes bug 348.)
15244 - Always remove expired routers and networkstatus docs before checking
15245 whether we have enough information to build circuits. (Fixes
15247 - Put a lower-bound on MaxAdvertisedBandwidth.
15250 Changes in version 0.1.2.7-alpha - 2007-02-06
15251 o Major bugfixes (rate limiting):
15252 - Servers decline directory requests much more aggressively when
15253 they're low on bandwidth. Otherwise they end up queueing more and
15254 more directory responses, which can't be good for latency.
15255 - But never refuse directory requests from local addresses.
15256 - Fix a memory leak when sending a 503 response for a networkstatus
15258 - Be willing to read or write on local connections (e.g. controller
15259 connections) even when the global rate limiting buckets are empty.
15260 - If our system clock jumps back in time, don't publish a negative
15261 uptime in the descriptor. Also, don't let the global rate limiting
15262 buckets go absurdly negative.
15263 - Flush local controller connection buffers periodically as we're
15264 writing to them, so we avoid queueing 4+ megabytes of data before
15267 o Major bugfixes (NT services):
15268 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15269 command-line flag so that admins can override the default by saying
15270 "tor --service install --user "SomeUser"". This will not affect
15271 existing installed services. Also, warn the user that the service
15272 will look for its configuration file in the service user's
15273 %appdata% directory. (We can't do the 'hardwire the user's appdata
15274 directory' trick any more, since we may not have read access to that
15277 o Major bugfixes (other):
15278 - Previously, we would cache up to 16 old networkstatus documents
15279 indefinitely, if they came from nontrusted authorities. Now we
15280 discard them if they are more than 10 days old.
15281 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
15283 - Detect and reject malformed DNS responses containing circular
15285 - If exits are rare enough that we're not marking exits as guards,
15286 ignore exit bandwidth when we're deciding the required bandwidth
15288 - When we're handling a directory connection tunneled over Tor,
15289 don't fill up internal memory buffers with all the data we want
15290 to tunnel; instead, only add it if the OR connection that will
15291 eventually receive it has some room for it. (This can lead to
15292 slowdowns in tunneled dir connections; a better solution will have
15293 to wait for 0.2.0.)
15295 o Minor bugfixes (dns):
15296 - Add some defensive programming to eventdns.c in an attempt to catch
15297 possible memory-stomping bugs.
15298 - Detect and reject DNS replies containing IPv4 or IPv6 records with
15299 an incorrect number of bytes. (Previously, we would ignore the
15301 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
15302 in the correct order, and doesn't crash.
15303 - Free memory held in recently-completed DNS lookup attempts on exit.
15304 This was not a memory leak, but may have been hiding memory leaks.
15305 - Handle TTL values correctly on reverse DNS lookups.
15306 - Treat failure to parse resolv.conf as an error.
15308 o Minor bugfixes (other):
15309 - Fix crash with "tor --list-fingerprint" (reported by seeess).
15310 - When computing clock skew from directory HTTP headers, consider what
15311 time it was when we finished asking for the directory, not what
15313 - Expire socks connections if they spend too long waiting for the
15314 handshake to finish. Previously we would let them sit around for
15315 days, if the connecting application didn't close them either.
15316 - And if the socks handshake hasn't started, don't send a
15317 "DNS resolve socks failed" handshake reply; just close it.
15318 - Stop using C functions that OpenBSD's linker doesn't like.
15319 - Don't launch requests for descriptors unless we have networkstatuses
15320 from at least half of the authorities. This delays the first
15321 download slightly under pathological circumstances, but can prevent
15322 us from downloading a bunch of descriptors we don't need.
15323 - Do not log IPs with TLS failures for incoming TLS
15324 connections. (Fixes bug 382.)
15325 - If the user asks to use invalid exit nodes, be willing to use
15327 - Stop using the reserved ac_cv namespace in our configure script.
15328 - Call stat() slightly less often; use fstat() when possible.
15329 - Refactor the way we handle pending circuits when an OR connection
15330 completes or fails, in an attempt to fix a rare crash bug.
15331 - Only rewrite a conn's address based on X-Forwarded-For: headers
15332 if it's a parseable public IP address; and stop adding extra quotes
15333 to the resulting address.
15336 - Weight directory requests by advertised bandwidth. Now we can
15337 let servers enable write limiting but still allow most clients to
15338 succeed at their directory requests. (We still ignore weights when
15339 choosing a directory authority; I hope this is a feature.)
15342 - Create a new file ReleaseNotes which was the old ChangeLog. The
15343 new ChangeLog file now includes the summaries for all development
15345 - Check for addresses with invalid characters at the exit as well
15346 as at the client, and warn less verbosely when they fail. You can
15347 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
15348 - Adapt a patch from goodell to let the contrib/exitlist script
15349 take arguments rather than require direct editing.
15350 - Inform the server operator when we decide not to advertise a
15351 DirPort due to AccountingMax enabled or a low BandwidthRate. It
15352 was confusing Zax, so now we're hopefully more helpful.
15353 - Bring us one step closer to being able to establish an encrypted
15354 directory tunnel without knowing a descriptor first. Still not
15355 ready yet. As part of the change, now assume we can use a
15356 create_fast cell if we don't know anything about a router.
15357 - Allow exit nodes to use nameservers running on ports other than 53.
15358 - Servers now cache reverse DNS replies.
15359 - Add an --ignore-missing-torrc command-line option so that we can
15360 get the "use sensible defaults if the configuration file doesn't
15361 exist" behavior even when specifying a torrc location on the command
15364 o Minor features (controller):
15365 - Track reasons for OR connection failure; make these reasons
15366 available via the controller interface. (Patch from Mike Perry.)
15367 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15368 can learn when clients are sending malformed hostnames to Tor.
15369 - Clean up documentation for controller status events.
15370 - Add a REMAP status to stream events to note that a stream's
15371 address has changed because of a cached address or a MapAddress
15375 Changes in version 0.1.2.6-alpha - 2007-01-09
15377 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
15378 connection handles more than 4 gigs in either direction, we crash.
15379 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
15380 advertised exit node, somebody might try to exit from us when
15381 we're bootstrapping and before we've built our descriptor yet.
15382 Refuse the connection rather than crashing.
15385 - Warn if we (as a server) find that we've resolved an address that we
15386 weren't planning to resolve.
15387 - Warn that using select() on any libevent version before 1.1 will be
15388 unnecessarily slow (even for select()).
15389 - Flush ERR-level controller status events just like we currently
15390 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15391 the controller from learning about current events.
15393 o Minor features (more controller status events):
15394 - Implement EXTERNAL_ADDRESS server status event so controllers can
15395 learn when our address changes.
15396 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
15397 can learn when directories reject our descriptor.
15398 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
15399 can learn when a client application is speaking a non-socks protocol
15401 - Implement DANGEROUS_SOCKS client status event so controllers
15402 can learn when a client application is leaking DNS addresses.
15403 - Implement BUG general status event so controllers can learn when
15404 Tor is unhappy about its internal invariants.
15405 - Implement CLOCK_SKEW general status event so controllers can learn
15406 when Tor thinks the system clock is set incorrectly.
15407 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
15408 server status events so controllers can learn when their descriptors
15409 are accepted by a directory.
15410 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
15411 server status events so controllers can learn about Tor's progress in
15412 deciding whether it's reachable from the outside.
15413 - Implement BAD_LIBEVENT general status event so controllers can learn
15414 when we have a version/method combination in libevent that needs to
15416 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
15417 and DNS_USELESS server status events so controllers can learn
15418 about changes to DNS server status.
15420 o Minor features (directory):
15421 - Authorities no longer recommend exits as guards if this would shift
15422 too much load to the exit nodes.
15425 Changes in version 0.1.2.5-alpha - 2007-01-06
15427 - Enable write limiting as well as read limiting. Now we sacrifice
15428 capacity if we're pushing out lots of directory traffic, rather
15429 than overrunning the user's intended bandwidth limits.
15430 - Include TLS overhead when counting bandwidth usage; previously, we
15431 would count only the bytes sent over TLS, but not the bytes used
15433 - Support running the Tor service with a torrc not in the same
15434 directory as tor.exe and default to using the torrc located in
15435 the %appdata%\Tor\ of the user who installed the service. Patch
15437 - Servers now check for the case when common DNS requests are going to
15438 wildcarded addresses (i.e. all getting the same answer), and change
15439 their exit policy to reject *:* if it's happening.
15440 - Implement BEGIN_DIR cells, so we can connect to the directory
15441 server via TLS to do encrypted directory requests rather than
15442 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15443 config options if you like.
15445 o Minor features (config and docs):
15446 - Start using the state file to store bandwidth accounting data:
15447 the bw_accounting file is now obsolete. We'll keep generating it
15448 for a while for people who are still using 0.1.2.4-alpha.
15449 - Try to batch changes to the state file so that we do as few
15450 disk writes as possible while still storing important things in
15452 - The state file and the bw_accounting file get saved less often when
15453 the AvoidDiskWrites config option is set.
15454 - Make PIDFile work on Windows (untested).
15455 - Add internal descriptions for a bunch of configuration options:
15456 accessible via controller interface and in comments in saved
15458 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15459 NNTP by default, so this seems like a sensible addition.
15460 - Clients now reject hostnames with invalid characters. This should
15461 avoid some inadvertent info leaks. Add an option
15462 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15463 is running a private network with hosts called @, !, and #.
15464 - Add a maintainer script to tell us which options are missing
15465 documentation: "make check-docs".
15466 - Add a new address-spec.txt document to describe our special-case
15467 addresses: .exit, .onion, and .noconnnect.
15469 o Minor features (DNS):
15470 - Ongoing work on eventdns infrastructure: now it has dns server
15471 and ipv6 support. One day Tor will make use of it.
15472 - Add client-side caching for reverse DNS lookups.
15473 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15474 - When we change nameservers or IP addresses, reset and re-launch
15475 our tests for DNS hijacking.
15477 o Minor features (directory):
15478 - Authorities now specify server versions in networkstatus. This adds
15479 about 2% to the size of compressed networkstatus docs, and allows
15480 clients to tell which servers support BEGIN_DIR and which don't.
15481 The implementation is forward-compatible with a proposed future
15482 protocol version scheme not tied to Tor versions.
15483 - DirServer configuration lines now have an orport= option so
15484 clients can open encrypted tunnels to the authorities without
15485 having downloaded their descriptors yet. Enabled for moria1,
15486 moria2, tor26, and lefkada now in the default configuration.
15487 - Directory servers are more willing to send a 503 "busy" if they
15488 are near their write limit, especially for v1 directory requests.
15489 Now they can use their limited bandwidth for actual Tor traffic.
15490 - Clients track responses with status 503 from dirservers. After a
15491 dirserver has given us a 503, we try not to use it until an hour has
15492 gone by, or until we have no dirservers that haven't given us a 503.
15493 - When we get a 503 from a directory, and we're not a server, we don't
15494 count the failure against the total number of failures allowed
15495 for the thing we're trying to download.
15496 - Report X-Your-Address-Is correctly from tunneled directory
15497 connections; don't report X-Your-Address-Is when it's an internal
15498 address; and never believe reported remote addresses when they're
15500 - Protect against an unlikely DoS attack on directory servers.
15501 - Add a BadDirectory flag to network status docs so that authorities
15502 can (eventually) tell clients about caches they believe to be
15505 o Minor features (controller):
15506 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15507 - Reimplement GETINFO so that info/names stays in sync with the
15509 - Implement "GETINFO fingerprint".
15510 - Implement "SETEVENTS GUARD" so controllers can get updates on
15511 entry guard status as it changes.
15513 o Minor features (clean up obsolete pieces):
15514 - Remove some options that have been deprecated since at least
15515 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15516 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15517 to set log options.
15518 - We no longer look for identity and onion keys in "identity.key" and
15519 "onion.key" -- these were replaced by secret_id_key and
15520 secret_onion_key in 0.0.8pre1.
15521 - We no longer require unrecognized directory entries to be
15524 o Major bugfixes (security):
15525 - Stop sending the HttpProxyAuthenticator string to directory
15526 servers when directory connections are tunnelled through Tor.
15527 - Clients no longer store bandwidth history in the state file.
15528 - Do not log introduction points for hidden services if SafeLogging
15530 - When generating bandwidth history, round down to the nearest
15531 1k. When storing accounting data, round up to the nearest 1k.
15532 - When we're running as a server, remember when we last rotated onion
15533 keys, so that we will rotate keys once they're a week old even if
15534 we never stay up for a week ourselves.
15536 o Major bugfixes (other):
15537 - Fix a longstanding bug in eventdns that prevented the count of
15538 timed-out resolves from ever being reset. This bug caused us to
15539 give up on a nameserver the third time it timed out, and try it
15540 10 seconds later... and to give up on it every time it timed out
15542 - Take out the '5 second' timeout from the connection retry
15543 schedule. Now the first connect attempt will wait a full 10
15544 seconds before switching to a new circuit. Perhaps this will help
15545 a lot. Based on observations from Mike Perry.
15546 - Fix a bug on the Windows implementation of tor_mmap_file() that
15547 would prevent the cached-routers file from ever loading. Reported
15551 - Fix an assert failure when a directory authority sets
15552 AuthDirRejectUnlisted and then receives a descriptor from an
15553 unlisted router. Reported by seeess.
15554 - Avoid a double-free when parsing malformed DirServer lines.
15555 - Fix a bug when a BSD-style PF socket is first used. Patch from
15557 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
15558 to resolve an address at a given exit node even when they ask for
15560 - Servers no longer ever list themselves in their "family" line,
15561 even if configured to do so. This makes it easier to configure
15562 family lists conveniently.
15563 - When running as a server, don't fall back to 127.0.0.1 when no
15564 nameservers are configured in /etc/resolv.conf; instead, make the
15565 user fix resolv.conf or specify nameservers explicitly. (Resolves
15567 - Stop accepting certain malformed ports in configured exit policies.
15568 - Don't re-write the fingerprint file every restart, unless it has
15570 - Stop warning when a single nameserver fails: only warn when _all_ of
15571 our nameservers have failed. Also, when we only have one nameserver,
15572 raise the threshold for deciding that the nameserver is dead.
15573 - Directory authorities now only decide that routers are reachable
15574 if their identity keys are as expected.
15575 - When the user uses bad syntax in the Log config line, stop
15576 suggesting other bad syntax as a replacement.
15577 - Correctly detect ipv6 DNS capability on OpenBSD.
15579 o Minor bugfixes (controller):
15580 - Report the circuit number correctly in STREAM CLOSED events. Bug
15581 reported by Mike Perry.
15582 - Do not report bizarre values for results of accounting GETINFOs
15583 when the last second's write or read exceeds the allotted bandwidth.
15584 - Report "unrecognized key" rather than an empty string when the
15585 controller tries to fetch a networkstatus that doesn't exist.
15588 Changes in version 0.1.1.26 - 2006-12-14
15589 o Security bugfixes:
15590 - Stop sending the HttpProxyAuthenticator string to directory
15591 servers when directory connections are tunnelled through Tor.
15592 - Clients no longer store bandwidth history in the state file.
15593 - Do not log introduction points for hidden services if SafeLogging
15597 - Fix an assert failure when a directory authority sets
15598 AuthDirRejectUnlisted and then receives a descriptor from an
15599 unlisted router (reported by seeess).
15602 Changes in version 0.1.2.4-alpha - 2006-12-03
15604 - Add support for using natd; this allows FreeBSDs earlier than
15605 5.1.2 to have ipfw send connections through Tor without using
15606 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15609 - Make all connections to addresses of the form ".noconnect"
15610 immediately get closed. This lets application/controller combos
15611 successfully test whether they're talking to the same Tor by
15612 watching for STREAM events.
15613 - Make cross.sh cross-compilation script work even when autogen.sh
15614 hasn't been run. (Patch from Michael Mohr.)
15615 - Statistics dumped by -USR2 now include a breakdown of public key
15616 operations, for profiling.
15619 - Fix a major leak when directory authorities parse their
15620 approved-routers list, a minor memory leak when we fail to pick
15621 an exit node, and a few rare leaks on errors.
15622 - Handle TransPort connections even when the server sends data before
15623 the client sends data. Previously, the connection would just hang
15624 until the client sent data. (Patch from tup based on patch from
15626 - Avoid assert failure when our cached-routers file is empty on
15630 - Don't log spurious warnings when we see a circuit close reason we
15631 don't recognize; it's probably just from a newer version of Tor.
15632 - Have directory authorities allow larger amounts of drift in uptime
15633 without replacing the server descriptor: previously, a server that
15634 restarted every 30 minutes could have 48 "interesting" descriptors
15636 - Start linking to the Tor specification and Tor reference manual
15637 correctly in the Windows installer.
15638 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15639 Tor/Privoxy we also uninstall Vidalia.
15640 - Resume building on Irix64, and fix a lot of warnings from its
15641 MIPSpro C compiler.
15642 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
15643 when we're running as a client.
15646 Changes in version 0.1.1.25 - 2006-11-04
15648 - When a client asks us to resolve (rather than connect to)
15649 an address, and we have a cached answer, give them the cached
15650 answer. Previously, we would give them no answer at all.
15651 - We were building exactly the wrong circuits when we predict
15652 hidden service requirements, meaning Tor would have to build all
15653 its circuits on demand.
15654 - If none of our live entry guards have a high uptime, but we
15655 require a guard with a high uptime, try adding a new guard before
15656 we give up on the requirement. This patch should make long-lived
15657 connections more stable on average.
15658 - When testing reachability of our DirPort, don't launch new
15659 tests when there's already one in progress -- unreachable
15660 servers were stacking up dozens of testing streams.
15662 o Security bugfixes:
15663 - When the user sends a NEWNYM signal, clear the client-side DNS
15664 cache too. Otherwise we continue to act on previous information.
15667 - Avoid a memory corruption bug when creating a hash table for
15669 - Avoid possibility of controller-triggered crash when misusing
15670 certain commands from a v0 controller on platforms that do not
15671 handle printf("%s",NULL) gracefully.
15672 - Avoid infinite loop on unexpected controller input.
15673 - Don't log spurious warnings when we see a circuit close reason we
15674 don't recognize; it's probably just from a newer version of Tor.
15675 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15676 Tor/Privoxy we also uninstall Vidalia.
15679 Changes in version 0.1.2.3-alpha - 2006-10-29
15681 - Prepare for servers to publish descriptors less often: never
15682 discard a descriptor simply for being too old until either it is
15683 recommended by no authorities, or until we get a better one for
15684 the same router. Make caches consider retaining old recommended
15685 routers for even longer.
15686 - If most authorities set a BadExit flag for a server, clients
15687 don't think of it as a general-purpose exit. Clients only consider
15688 authorities that advertise themselves as listing bad exits.
15689 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15690 headers for content, so that we can work better in the presence of
15691 caching HTTP proxies.
15692 - Allow authorities to list nodes as bad exits by fingerprint or by
15695 o Minor features, controller:
15696 - Add a REASON field to CIRC events; for backward compatibility, this
15697 field is sent only to controllers that have enabled the extended
15698 event format. Also, add additional reason codes to explain why
15699 a given circuit has been destroyed or truncated. (Patches from
15701 - Add a REMOTE_REASON field to extended CIRC events to tell the
15702 controller about why a remote OR told us to close a circuit.
15703 - Stream events also now have REASON and REMOTE_REASON fields,
15704 working much like those for circuit events.
15705 - There's now a GETINFO ns/... field so that controllers can ask Tor
15706 about the current status of a router.
15707 - A new event type "NS" to inform a controller when our opinion of
15708 a router's status has changed.
15709 - Add a GETINFO events/names and GETINFO features/names so controllers
15710 can tell which events and features are supported.
15711 - A new CLEARDNSCACHE signal to allow controllers to clear the
15712 client-side DNS cache without expiring circuits.
15714 o Security bugfixes:
15715 - When the user sends a NEWNYM signal, clear the client-side DNS
15716 cache too. Otherwise we continue to act on previous information.
15719 - Avoid sending junk to controllers or segfaulting when a controller
15720 uses EVENT_NEW_DESC with verbose nicknames.
15721 - Stop triggering asserts if the controller tries to extend hidden
15722 service circuits (reported by mwenge).
15723 - Avoid infinite loop on unexpected controller input.
15724 - When the controller does a "GETINFO network-status", tell it
15725 about even those routers whose descriptors are very old, and use
15726 long nicknames where appropriate.
15727 - Change NT service functions to be loaded on demand. This lets us
15728 build with MinGW without breaking Tor for Windows 98 users.
15729 - Do DirPort reachability tests less often, since a single test
15730 chews through many circuits before giving up.
15731 - In the hidden service example in torrc.sample, stop recommending
15732 esoteric and discouraged hidden service options.
15733 - When stopping an NT service, wait up to 10 sec for it to actually
15734 stop. Patch from Matt Edman; resolves bug 295.
15735 - Fix handling of verbose nicknames with ORCONN controller events:
15736 make them show up exactly when requested, rather than exactly when
15738 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
15739 printing a duplicate "$" in the keys we send (reported by mwenge).
15740 - Correctly set maximum connection limit on Cygwin. (This time
15742 - Try to detect Windows correctly when cross-compiling.
15743 - Detect the size of the routers file correctly even if it is
15744 corrupted (on systems without mmap) or not page-aligned (on systems
15745 with mmap). This bug was harmless.
15746 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15747 to open a stream fails; now we do in more cases. This should
15748 make clients able to find a good exit faster in some cases, since
15749 unhandleable requests will now get an error rather than timing out.
15750 - Resolve two memory leaks when rebuilding the on-disk router cache
15751 (reported by fookoowa).
15752 - Clean up minor code warnings suggested by the MIPSpro C compiler,
15753 and reported by some Centos users.
15754 - Controller signals now work on non-Unix platforms that don't define
15755 SIGUSR1 and SIGUSR2 the way we expect.
15756 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
15757 values before failing, and always enables eventdns.
15758 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
15759 Try to fix this in configure.in by checking for most functions
15760 before we check for libevent.
15763 Changes in version 0.1.2.2-alpha - 2006-10-07
15765 - Make our async eventdns library on-by-default for Tor servers,
15766 and plan to deprecate the separate dnsworker threads.
15767 - Add server-side support for "reverse" DNS lookups (using PTR
15768 records so clients can determine the canonical hostname for a given
15769 IPv4 address). Only supported by servers using eventdns; servers
15770 now announce in their descriptors whether they support eventdns.
15771 - Specify and implement client-side SOCKS5 interface for reverse DNS
15772 lookups (see doc/socks-extensions.txt).
15773 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
15774 connect to directory servers through Tor. Previously, clients needed
15775 to find Tor exits to make private connections to directory servers.
15776 - Avoid choosing Exit nodes for entry or middle hops when the
15777 total bandwidth available from non-Exit nodes is much higher than
15778 the total bandwidth available from Exit nodes.
15779 - Workaround for name servers (like Earthlink's) that hijack failing
15780 DNS requests and replace the no-such-server answer with a "helpful"
15781 redirect to an advertising-driven search portal. Also work around
15782 DNS hijackers who "helpfully" decline to hijack known-invalid
15783 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15784 lets you turn it off.
15785 - Send out a burst of long-range padding cells once we've established
15786 that we're reachable. Spread them over 4 circuits, so hopefully
15787 a few will be fast. This exercises our bandwidth and bootstraps
15788 us into the directory more quickly.
15790 o New/improved config options:
15791 - Add new config option "ResolvConf" to let the server operator
15792 choose an alternate resolve.conf file when using eventdns.
15793 - Add an "EnforceDistinctSubnets" option to control our "exclude
15794 servers on the same /16" behavior. It's still on by default; this
15795 is mostly for people who want to operate private test networks with
15796 all the machines on the same subnet.
15797 - If one of our entry guards is on the ExcludeNodes list, or the
15798 directory authorities don't think it's a good guard, treat it as
15799 if it were unlisted: stop using it as a guard, and throw it off
15800 the guards list if it stays that way for a long time.
15801 - Allow directory authorities to be marked separately as authorities
15802 for the v1 directory protocol, the v2 directory protocol, and
15803 as hidden service directories, to make it easier to retire old
15804 authorities. V1 authorities should set "HSAuthoritativeDir 1"
15805 to continue being hidden service authorities too.
15806 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
15808 o Minor features, controller:
15809 - Fix CIRC controller events so that controllers can learn the
15810 identity digests of non-Named servers used in circuit paths.
15811 - Let controllers ask for more useful identifiers for servers. Instead
15812 of learning identity digests for un-Named servers and nicknames
15813 for Named servers, the new identifiers include digest, nickname,
15814 and indication of Named status. Off by default; see control-spec.txt
15815 for more information.
15816 - Add a "getinfo address" controller command so it can display Tor's
15817 best guess to the user.
15818 - New controller event to alert the controller when our server
15819 descriptor has changed.
15820 - Give more meaningful errors on controller authentication failure.
15822 o Minor features, other:
15823 - When asked to resolve a hostname, don't use non-exit servers unless
15824 requested to do so. This allows servers with broken DNS to be
15825 useful to the network.
15826 - Divide eventdns log messages into warn and info messages.
15827 - Reserve the nickname "Unnamed" for routers that can't pick
15828 a hostname: any router can call itself Unnamed; directory
15829 authorities will never allocate Unnamed to any particular router;
15830 clients won't believe that any router is the canonical Unnamed.
15831 - Only include function names in log messages for info/debug messages.
15832 For notice/warn/err, the content of the message should be clear on
15833 its own, and printing the function name only confuses users.
15834 - Avoid some false positives during reachability testing: don't try
15835 to test via a server that's on the same /24 as us.
15836 - If we fail to build a circuit to an intended enclave, and it's
15837 not mandatory that we use that enclave, stop wanting it.
15838 - When eventdns is enabled, allow multithreaded builds on NetBSD and
15839 OpenBSD. (We had previously disabled threads on these platforms
15840 because they didn't have working thread-safe resolver functions.)
15842 o Major bugfixes, anonymity/security:
15843 - If a client asked for a server by name, and there's a named server
15844 in our network-status but we don't have its descriptor yet, we
15845 could return an unnamed server instead.
15846 - Fix NetBSD bug that could allow someone to force uninitialized RAM
15847 to be sent to a server's DNS resolver. This only affects NetBSD
15848 and other platforms that do not bounds-check tolower().
15849 - Reject (most) attempts to use Tor circuits with length one. (If
15850 many people start using Tor as a one-hop proxy, exit nodes become
15851 a more attractive target for compromise.)
15852 - Just because your DirPort is open doesn't mean people should be
15853 able to remotely teach you about hidden service descriptors. Now
15854 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15856 o Major bugfixes, other:
15857 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
15858 - When a client asks the server to resolve (not connect to)
15859 an address, and it has a cached answer, give them the cached answer.
15860 Previously, the server would give them no answer at all.
15861 - Allow really slow clients to not hang up five minutes into their
15862 directory downloads (suggested by Adam J. Richter).
15863 - We were building exactly the wrong circuits when we anticipated
15864 hidden service requirements, meaning Tor would have to build all
15865 its circuits on demand.
15866 - Avoid crashing when we mmap a router cache file of size 0.
15867 - When testing reachability of our DirPort, don't launch new
15868 tests when there's already one in progress -- unreachable
15869 servers were stacking up dozens of testing streams.
15871 o Minor bugfixes, correctness:
15872 - If we're a directory mirror and we ask for "all" network status
15873 documents, we would discard status documents from authorities
15874 we don't recognize.
15875 - Avoid a memory corruption bug when creating a hash table for
15877 - Avoid controller-triggered crash when misusing certain commands
15878 from a v0 controller on platforms that do not handle
15879 printf("%s",NULL) gracefully.
15880 - Don't crash when a controller sends a third argument to an
15881 "extendcircuit" request.
15882 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15883 response; fix error code when "getinfo dir/status/" fails.
15884 - Avoid crash when telling controller stream-status and a stream
15886 - Patch from Adam Langley to fix assert() in eventdns.c.
15887 - Fix a debug log message in eventdns to say "X resolved to Y"
15888 instead of "X resolved to X".
15889 - Make eventdns give strings for DNS errors, not just error numbers.
15890 - Track unreachable entry guards correctly: don't conflate
15891 'unreachable by us right now' with 'listed as down by the directory
15892 authorities'. With the old code, if a guard was unreachable by
15893 us but listed as running, it would clog our guard list forever.
15894 - Behave correctly in case we ever have a network with more than
15895 2GB/s total advertised capacity.
15896 - Make TrackExitHosts case-insensitive, and fix the behavior of
15897 ".suffix" TrackExitHosts items to avoid matching in the middle of
15899 - Finally fix the openssl warnings from newer gccs that believe that
15900 ignoring a return value is okay, but casting a return value and
15901 then ignoring it is a sign of madness.
15902 - Prevent the contrib/exitlist script from printing the same
15903 result more than once.
15904 - Patch from Steve Hildrey: Generate network status correctly on
15905 non-versioning dirservers.
15906 - Don't listen to the X-Your-Address-Is hint if you did the lookup
15907 via Tor; otherwise you'll think you're the exit node's IP address.
15909 o Minor bugfixes, performance:
15910 - Two small performance improvements on parsing descriptors.
15911 - Major performance improvement on inserting descriptors: change
15912 algorithm from O(n^2) to O(n).
15913 - Make the common memory allocation path faster on machines where
15914 malloc(0) returns a pointer.
15915 - Start remembering X-Your-Address-Is directory hints even if you're
15916 a client, so you can become a server more smoothly.
15917 - Avoid duplicate entries on MyFamily line in server descriptor.
15919 o Packaging, features:
15920 - Remove architecture from OS X builds. The official builds are
15921 now universal binaries.
15922 - The Debian package now uses --verify-config when (re)starting,
15923 to distinguish configuration errors from other errors.
15924 - Update RPMs to require libevent 1.1b.
15926 o Packaging, bugfixes:
15927 - Patches so Tor builds with MinGW on Windows.
15928 - Patches so Tor might run on Cygwin again.
15929 - Resume building on non-gcc compilers and ancient gcc. Resume
15930 building with the -O0 compile flag. Resume building cleanly on
15932 - Run correctly on OS X platforms with case-sensitive filesystems.
15933 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
15934 - Add autoconf checks so Tor can build on Solaris x86 again.
15937 - Documented (and renamed) ServerDNSSearchDomains and
15938 ServerDNSResolvConfFile options.
15939 - Be clearer that the *ListenAddress directives can be repeated
15943 Changes in version 0.1.1.24 - 2006-09-29
15945 - Allow really slow clients to not hang up five minutes into their
15946 directory downloads (suggested by Adam J. Richter).
15947 - Fix major performance regression from 0.1.0.x: instead of checking
15948 whether we have enough directory information every time we want to
15949 do something, only check when the directory information has changed.
15950 This should improve client CPU usage by 25-50%.
15951 - Don't crash if, after a server has been running for a while,
15952 it can't resolve its hostname.
15955 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15956 - Don't crash when the controller receives a third argument to an
15957 "extendcircuit" request.
15958 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15959 response; fix error code when "getinfo dir/status/" fails.
15960 - Fix configure.in to not produce broken configure files with
15961 more recent versions of autoconf. Thanks to Clint for his auto*
15963 - Fix security bug on NetBSD that could allow someone to force
15964 uninitialized RAM to be sent to a server's DNS resolver. This
15965 only affects NetBSD and other platforms that do not bounds-check
15967 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15968 methods: these are known to be buggy.
15969 - If we're a directory mirror and we ask for "all" network status
15970 documents, we would discard status documents from authorities
15971 we don't recognize.
15974 Changes in version 0.1.2.1-alpha - 2006-08-27
15976 - Add "eventdns" async dns library from Adam Langley, tweaked to
15977 build on OSX and Windows. Only enabled if you pass the
15978 --enable-eventdns argument to configure.
15979 - Allow servers with no hostname or IP address to learn their
15980 IP address by asking the directory authorities. This code only
15981 kicks in when you would normally have exited with a "no address"
15982 error. Nothing's authenticated, so use with care.
15983 - Rather than waiting a fixed amount of time between retrying
15984 application connections, we wait only 5 seconds for the first,
15985 10 seconds for the second, and 15 seconds for each retry after
15986 that. Hopefully this will improve the expected user experience.
15987 - Patch from Tup to add support for transparent AP connections:
15988 this basically bundles the functionality of trans-proxy-tor
15989 into the Tor mainline. Now hosts with compliant pf/netfilter
15990 implementations can redirect TCP connections straight to Tor
15991 without diverting through SOCKS. Needs docs.
15992 - Busy directory servers save lots of memory by spooling server
15993 descriptors, v1 directories, and v2 networkstatus docs to buffers
15994 as needed rather than en masse. Also mmap the cached-routers
15995 files, so we don't need to keep the whole thing in memory too.
15996 - Automatically avoid picking more than one node from the same
15997 /16 network when constructing a circuit.
15998 - Revise and clean up the torrc.sample that we ship with; add
15999 a section for BandwidthRate and BandwidthBurst.
16002 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16003 split connection_t into edge, or, dir, control, and base structs.
16004 These will save quite a bit of memory on busy servers, and they'll
16005 also help us track down bugs in the code and bugs in the spec.
16006 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16007 or later. Log when we are doing this, so we can diagnose it when
16008 it fails. (Also, recommend libevent 1.1b for kqueue and
16009 win32 methods; deprecate libevent 1.0b harder; make libevent
16010 recommendation system saner.)
16011 - Start being able to build universal binaries on OS X (thanks
16013 - Export the default exit policy via the control port, so controllers
16014 don't need to guess what it is / will be later.
16015 - Add a man page entry for ProtocolWarnings.
16016 - Add TestVia config option to the man page.
16017 - Remove even more protocol-related warnings from Tor server logs,
16018 such as bad TLS handshakes and malformed begin cells.
16019 - Stop fetching descriptors if you're not a dir mirror and you
16020 haven't tried to establish any circuits lately. [This currently
16021 causes some dangerous behavior, because when you start up again
16022 you'll use your ancient server descriptors.]
16023 - New DirPort behavior: if you have your dirport set, you download
16024 descriptors aggressively like a directory mirror, whether or not
16025 your ORPort is set.
16026 - Get rid of the router_retry_connections notion. Now routers
16027 no longer try to rebuild long-term connections to directory
16028 authorities, and directory authorities no longer try to rebuild
16029 long-term connections to all servers. We still don't hang up
16030 connections in these two cases though -- we need to look at it
16031 more carefully to avoid flapping, and we likely need to wait til
16032 0.1.1.x is obsolete.
16033 - Drop compatibility with obsolete Tors that permit create cells
16034 to have the wrong circ_id_type.
16035 - Re-enable per-connection rate limiting. Get rid of the "OP
16036 bandwidth" concept. Lay groundwork for "bandwidth classes" --
16037 separate global buckets that apply depending on what sort of conn
16039 - Start publishing one minute or so after we find our ORPort
16040 to be reachable. This will help reduce the number of descriptors
16041 we have for ourselves floating around, since it's quite likely
16042 other things (e.g. DirPort) will change during that minute too.
16043 - Fork the v1 directory protocol into its own spec document,
16044 and mark dir-spec.txt as the currently correct (v2) spec.
16047 - When we find our DirPort to be reachable, publish a new descriptor
16048 so we'll tell the world (reported by pnx).
16049 - Publish a new descriptor after we hup/reload. This is important
16050 if our config has changed such that we'll want to start advertising
16051 our DirPort now, etc.
16052 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16053 - When we have a state file we cannot parse, tell the user and
16054 move it aside. Now we avoid situations where the user starts
16055 Tor in 1904, Tor writes a state file with that timestamp in it,
16056 the user fixes her clock, and Tor refuses to start.
16057 - Fix configure.in to not produce broken configure files with
16058 more recent versions of autoconf. Thanks to Clint for his auto*
16060 - "tor --verify-config" now exits with -1(255) or 0 depending on
16061 whether the config options are bad or good.
16062 - Resolve bug 321 when using dnsworkers: append a period to every
16063 address we resolve at the exit node, so that we do not accidentally
16064 pick up local addresses, and so that failing searches are retried
16065 in the resolver search domains. (This is already solved for
16066 eventdns.) (This breaks Blossom servers for now.)
16067 - If we are using an exit enclave and we can't connect, e.g. because
16068 its webserver is misconfigured to not listen on localhost, then
16069 back off and try connecting from somewhere else before we fail.
16072 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
16073 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16074 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16075 when the IP address is mapped through MapAddress to a hostname.
16076 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16077 useless IPv6 DNS resolves.
16078 - Patch suggested by Karsten Loesing: respond to SIGNAL command
16079 before we execute the signal, in case the signal shuts us down.
16080 - Clean up AllowInvalidNodes man page entry.
16081 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16082 - Add more asserts to track down an assert error on a windows Tor
16083 server with connection_add being called with socket == -1.
16084 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16085 - Fix misleading log messages: an entry guard that is "unlisted",
16086 as well as not known to be "down" (because we've never heard
16087 of it), is not therefore "up".
16088 - Remove code to special-case "-cvs" ending, since it has not
16089 actually mattered since 0.0.9.
16090 - Make our socks5 handling more robust to broken socks clients:
16091 throw out everything waiting on the buffer in between socks
16092 handshake phases, since they can't possibly (so the theory
16093 goes) have predicted what we plan to respond to them.
16096 Changes in version 0.1.1.23 - 2006-07-30
16098 - Fast Tor servers, especially exit nodes, were triggering asserts
16099 due to a bug in handling the list of pending DNS resolves. Some
16100 bugs still remain here; we're hunting them.
16101 - Entry guards could crash clients by sending unexpected input.
16102 - More fixes on reachability testing: if you find yourself reachable,
16103 then don't ever make any client requests (so you stop predicting
16104 circuits), then hup or have your clock jump, then later your IP
16105 changes, you won't think circuits are working, so you won't try to
16106 test reachability, so you won't publish.
16109 - Avoid a crash if the controller does a resetconf firewallports
16110 and then a setconf fascistfirewall=1.
16111 - Avoid an integer underflow when the dir authority decides whether
16112 a router is stable: we might wrongly label it stable, and compute
16113 a slightly wrong median stability, when a descriptor is published
16115 - Fix a place where we might trigger an assert if we can't build our
16116 own server descriptor yet.
16119 Changes in version 0.1.1.22 - 2006-07-05
16121 - Fix a big bug that was causing servers to not find themselves
16122 reachable if they changed IP addresses. Since only 0.1.1.22+
16123 servers can do reachability testing correctly, now we automatically
16124 make sure to test via one of these.
16125 - Fix to allow clients and mirrors to learn directory info from
16126 descriptor downloads that get cut off partway through.
16127 - Directory authorities had a bug in deciding if a newly published
16128 descriptor was novel enough to make everybody want a copy -- a few
16129 servers seem to be publishing new descriptors many times a minute.
16131 - Fix a rare bug that was causing some servers to complain about
16132 "closing wedged cpuworkers" and skip some circuit create requests.
16133 - Make the Exit flag in directory status documents actually work.
16136 Changes in version 0.1.1.21 - 2006-06-10
16137 o Crash and assert fixes from 0.1.1.20:
16138 - Fix a rare crash on Tor servers that have enabled hibernation.
16139 - Fix a seg fault on startup for Tor networks that use only one
16140 directory authority.
16141 - Fix an assert from a race condition that occurs on Tor servers
16142 while exiting, where various threads are trying to log that they're
16143 exiting, and delete the logs, at the same time.
16144 - Make our unit tests pass again on certain obscure platforms.
16147 - Add support for building SUSE RPM packages.
16148 - Speed up initial bootstrapping for clients: if we are making our
16149 first ever connection to any entry guard, then don't mark it down
16151 - When only one Tor server in the network is labelled as a guard,
16152 and we've already picked him, we would cycle endlessly picking him
16153 again, being unhappy about it, etc. Now we specifically exclude
16154 current guards when picking a new guard.
16155 - Servers send create cells more reliably after the TLS connection
16156 is established: we were sometimes forgetting to send half of them
16157 when we had more than one pending.
16158 - If we get a create cell that asks us to extend somewhere, but the
16159 Tor server there doesn't match the expected digest, we now send
16160 a destroy cell back, rather than silently doing nothing.
16161 - Make options->RedirectExit work again.
16162 - Make cookie authentication for the controller work again.
16163 - Stop being picky about unusual characters in the arguments to
16164 mapaddress. It's none of our business.
16165 - Add a new config option "TestVia" that lets you specify preferred
16166 middle hops to use for test circuits. Perhaps this will let me
16167 debug the reachability problems better.
16169 o Log / documentation fixes:
16170 - If we're a server and some peer has a broken TLS certificate, don't
16171 log about it unless ProtocolWarnings is set, i.e., we want to hear
16172 about protocol violations by others.
16173 - Fix spelling of VirtualAddrNetwork in man page.
16174 - Add a better explanation at the top of the autogenerated torrc file
16175 about what happened to our old torrc.
16178 Changes in version 0.1.1.20 - 2006-05-23
16180 - Downgrade a log severity where servers complain that they're
16182 - Avoid a compile warning on FreeBSD.
16183 - Remove string size limit on NEWDESC messages; solve bug 291.
16184 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
16185 more thoroughly when we're running on windows.
16188 Changes in version 0.1.1.19-rc - 2006-05-03
16190 - Regenerate our local descriptor if it's dirty and we try to use
16191 it locally (e.g. if it changes during reachability detection).
16192 - If we setconf our ORPort to 0, we continued to listen on the
16193 old ORPort and receive connections.
16194 - Avoid a second warning about machine/limits.h on Debian
16196 - Be willing to add our own routerinfo into the routerlist.
16197 Now authorities will include themselves in their directories
16198 and network-statuses.
16199 - Stop trying to upload rendezvous descriptors to every
16200 directory authority: only try the v1 authorities.
16201 - Servers no longer complain when they think they're not
16202 registered with the directory authorities. There were too many
16204 - Backport dist-rpm changes so rpms can be built without errors.
16207 - Implement an option, VirtualAddrMask, to set which addresses
16208 get handed out in response to mapaddress requests. This works
16209 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16212 Changes in version 0.1.1.18-rc - 2006-04-10
16214 - Work harder to download live network-statuses from all the
16215 directory authorities we know about. Improve the threshold
16216 decision logic so we're more robust to edge cases.
16217 - When fetching rendezvous descriptors, we were willing to ask
16218 v2 authorities too, which would always return 404.
16221 - Stop listing down or invalid nodes in the v1 directory. This will
16222 reduce its bulk by about 1/3, and reduce load on directory
16224 - When deciding whether a router is Fast or Guard-worthy, consider
16225 his advertised BandwidthRate and not just the BandwidthCapacity.
16226 - No longer ship INSTALL and README files -- they are useless now.
16227 - Force rpmbuild to behave and honor target_cpu.
16228 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16229 - Start to include translated versions of the tor-doc-*.html
16230 files, along with the screenshots. Still needs more work.
16231 - Start sending back 512 and 451 errors if mapaddress fails,
16232 rather than not sending anything back at all.
16233 - When we fail to bind or listen on an incoming or outgoing
16234 socket, we should close it before failing. otherwise we just
16235 leak it. (thanks to weasel for finding.)
16236 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
16237 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
16238 - Make NoPublish (even though deprecated) work again.
16239 - Fix a minor security flaw where a versioning auth dirserver
16240 could list a recommended version many times in a row to make
16241 clients more convinced that it's recommended.
16242 - Fix crash bug if there are two unregistered servers running
16243 with the same nickname, one of them is down, and you ask for
16244 them by nickname in your EntryNodes or ExitNodes. Also, try
16245 to pick the one that's running rather than an arbitrary one.
16246 - Fix an infinite loop we could hit if we go offline for too long.
16247 - Complain when we hit WSAENOBUFS on recv() or write() too.
16248 Perhaps this will help us hunt the bug.
16249 - If you're not a versioning dirserver, don't put the string
16250 "client-versions \nserver-versions \n" in your network-status.
16251 - Lower the minimum required number of file descriptors to 1000,
16252 so we can have some overhead for Valgrind on Linux, where the
16253 default ulimit -n is 1024.
16256 - Add tor.dizum.com as the fifth authoritative directory server.
16257 - Add a new config option FetchUselessDescriptors, off by default,
16258 for when you plan to run "exitlist" on your client and you want
16259 to know about even the non-running descriptors.
16262 Changes in version 0.1.1.17-rc - 2006-03-28
16264 - Clients and servers since 0.1.1.10-alpha have been expiring
16265 connections whenever they are idle for 5 minutes and they *do*
16266 have circuits on them. Oops. With this new version, clients will
16267 discard their previous entry guard choices and avoid choosing
16268 entry guards running these flawed versions.
16269 - Fix memory leak when uncompressing concatenated zlib streams. This
16270 was causing substantial leaks over time on Tor servers.
16271 - The v1 directory was including servers as much as 48 hours old,
16272 because that's how the new routerlist->routers works. Now only
16273 include them if they're 20 hours old or less.
16276 - Resume building on irix64, netbsd 2.0, etc.
16277 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
16279 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16280 and it is confusing some users.
16281 - Mirrors stop caching the v1 directory so often.
16282 - Make the max number of old descriptors that a cache will hold
16283 rise with the number of directory authorities, so we can scale.
16284 - Change our win32 uname() hack to be more forgiving about what
16285 win32 versions it thinks it's found.
16288 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
16290 - When the controller's *setconf commands fail, collect an error
16291 message in a string and hand it back to the controller.
16292 - Make the v2 dir's "Fast" flag based on relative capacity, just
16293 like "Stable" is based on median uptime. Name everything in the
16294 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
16295 - Log server fingerprint on startup, so new server operators don't
16296 have to go hunting around their filesystem for it.
16297 - Return a robots.txt on our dirport to discourage google indexing.
16298 - Let the controller ask for GETINFO dir/status/foo so it can ask
16299 directly rather than connecting to the dir port. Only works when
16300 dirport is set for now.
16302 o New config options rather than constants in the code:
16303 - SocksTimeout: How long do we let a socks connection wait
16304 unattached before we fail it?
16305 - CircuitBuildTimeout: Cull non-open circuits that were born
16306 at least this many seconds ago.
16307 - CircuitIdleTimeout: Cull open clean circuits that were born
16308 at least this many seconds ago.
16311 Changes in version 0.1.1.16-rc - 2006-03-18
16312 o Bugfixes on 0.1.1.15-rc:
16313 - Fix assert when the controller asks to attachstream a connect-wait
16314 or resolve-wait stream.
16315 - Now do address rewriting when the controller asks us to attach
16316 to a particular circuit too. This will let Blossom specify
16317 "moria2.exit" without having to learn what moria2's IP address is.
16318 - Make the "tor --verify-config" command-line work again, so people
16319 can automatically check if their torrc will parse.
16320 - Authoritative dirservers no longer require an open connection from
16321 a server to consider him "reachable". We need this change because
16322 when we add new auth dirservers, old servers won't know not to
16324 - Let Tor build on Sun CC again.
16325 - Fix an off-by-one buffer size in dirserv.c that magically never
16326 hit our three authorities but broke sjmurdoch's own tor network.
16327 - If we as a directory mirror don't know of any v1 directory
16328 authorities, then don't try to cache any v1 directories.
16329 - Stop warning about unknown servers in our family when they are
16330 given as hex digests.
16331 - Stop complaining as quickly to the server operator that he
16332 hasn't registered his nickname/key binding.
16333 - Various cleanups so we can add new V2 Auth Dirservers.
16334 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16335 reflect the updated flags in our v2 dir protocol.
16336 - Resume allowing non-printable characters for exit streams (both
16337 for connecting and for resolving). Now we tolerate applications
16338 that don't follow the RFCs. But continue to block malformed names
16341 o Bugfixes on 0.1.0.x:
16342 - Fix assert bug in close_logs(): when we close and delete logs,
16343 remove them all from the global "logfiles" list.
16344 - Fix minor integer overflow in calculating when we expect to use up
16345 our bandwidth allocation before hibernating.
16346 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
16347 there are multiple SSLs installed with different versions.
16348 - When we try to be a server and Address is not explicitly set and
16349 our hostname resolves to a private IP address, try to use an
16350 interface address if it has a public address. Now Windows machines
16351 that think of themselves as localhost can work by default.
16354 - Let the controller ask for GETINFO dir/server/foo so it can ask
16355 directly rather than connecting to the dir port.
16356 - Let the controller tell us about certain router descriptors
16357 that it doesn't want Tor to use in circuits. Implement
16358 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
16359 - New config option SafeSocks to reject all application connections
16360 using unsafe socks protocols. Defaults to off.
16363 Changes in version 0.1.1.15-rc - 2006-03-11
16364 o Bugfixes and cleanups:
16365 - When we're printing strings from the network, don't try to print
16366 non-printable characters. This protects us against shell escape
16367 sequence exploits, and also against attacks to fool humans into
16368 misreading their logs.
16369 - Fix a bug where Tor would fail to establish any connections if you
16370 left it off for 24 hours and then started it: we were happy with
16371 the obsolete network statuses, but they all referred to router
16372 descriptors that were too old to fetch, so we ended up with no
16373 valid router descriptors.
16374 - Fix a seg fault in the controller's "getinfo orconn-status"
16375 command while listing status on incoming handshaking connections.
16376 Introduce a status name "NEW" for these connections.
16377 - If we get a linelist or linelist_s config option from the torrc
16378 (e.g. ExitPolicy) and it has no value, warn and skip rather than
16379 silently resetting it to its default.
16380 - Don't abandon entry guards until they've been down or gone for
16382 - Cleaner and quieter log messages.
16385 - New controller signal NEWNYM that makes new application requests
16386 use clean circuits.
16387 - Add a new circuit purpose 'controller' to let the controller ask
16388 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
16389 controller command to let you specify the purpose if you're
16390 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
16391 command to let you change a circuit's purpose after it's been
16393 - Accept "private:*" in routerdesc exit policies; not generated yet
16394 because older Tors do not understand it.
16395 - Add BSD-style contributed startup script "rc.subr" from Peter
16399 Changes in version 0.1.1.14-alpha - 2006-02-20
16400 o Bugfixes on 0.1.1.x:
16401 - Don't die if we ask for a stdout or stderr log (even implicitly)
16402 and we're set to RunAsDaemon -- just warn.
16403 - We still had a few bugs in the OR connection rotation code that
16404 caused directory servers to slowly aggregate connections to other
16405 fast Tor servers. This time for sure!
16406 - Make log entries on Win32 include the name of the function again.
16407 - We were treating a pair of exit policies if they were equal even
16408 if one said accept and the other said reject -- causing us to
16409 not always publish a new descriptor since we thought nothing
16411 - Retry pending server downloads as well as pending networkstatus
16412 downloads when we unexpectedly get a socks request.
16413 - We were ignoring the IS_FAST flag in the directory status,
16414 meaning we were willing to pick trivial-bandwidth nodes for "fast"
16416 - If the controller's SAVECONF command fails (e.g. due to file
16417 permissions), let the controller know that it failed.
16420 - If we're trying to be a Tor server and running Windows 95/98/ME
16421 as a server, explain that we'll likely crash.
16422 - When we're a server, a client asks for an old-style directory,
16423 and our write bucket is empty, don't give it to him. This way
16424 small servers can continue to serve the directory *sometimes*,
16425 without getting overloaded.
16426 - Compress exit policies even more -- look for duplicate lines
16428 - Clients now honor the "guard" flag in the router status when
16429 picking entry guards, rather than looking at is_fast or is_stable.
16430 - Retain unrecognized lines in $DATADIR/state file, so that we can
16431 be forward-compatible.
16432 - Generate 18.0.0.0/8 address policy format in descs when we can;
16433 warn when the mask is not reducible to a bit-prefix.
16434 - Let the user set ControlListenAddress in the torrc. This can be
16435 dangerous, but there are some cases (like a secured LAN) where it
16437 - Split ReachableAddresses into ReachableDirAddresses and
16438 ReachableORAddresses, so we can restrict Dir conns to port 80
16439 and OR conns to port 443.
16440 - Now we can target arch and OS in rpm builds (contributed by
16441 Phobos). Also make the resulting dist-rpm filename match the
16443 - New config options to help controllers: FetchServerDescriptors
16444 and FetchHidServDescriptors for whether to fetch server
16445 info and hidserv info or let the controller do it, and
16446 PublishServerDescriptor and PublishHidServDescriptors.
16447 - Also let the controller set the __AllDirActionsPrivate config
16448 option if you want all directory fetches/publishes to happen via
16449 Tor (it assumes your controller bootstraps your circuits).
16452 Changes in version 0.1.0.17 - 2006-02-17
16453 o Crash bugfixes on 0.1.0.x:
16454 - When servers with a non-zero DirPort came out of hibernation,
16455 sometimes they would trigger an assert.
16457 o Other important bugfixes:
16458 - On platforms that don't have getrlimit (like Windows), we were
16459 artificially constraining ourselves to a max of 1024
16460 connections. Now just assume that we can handle as many as 15000
16461 connections. Hopefully this won't cause other problems.
16463 o Backported features:
16464 - When we're a server, a client asks for an old-style directory,
16465 and our write bucket is empty, don't give it to him. This way
16466 small servers can continue to serve the directory *sometimes*,
16467 without getting overloaded.
16468 - Whenever you get a 503 in response to a directory fetch, try
16469 once more. This will become important once servers start sending
16470 503's whenever they feel busy.
16471 - Fetch a new directory every 120 minutes, not every 40 minutes.
16472 Now that we have hundreds of thousands of users running the old
16473 directory algorithm, it's starting to hurt a lot.
16474 - Bump up the period for forcing a hidden service descriptor upload
16475 from 20 minutes to 1 hour.
16478 Changes in version 0.1.1.13-alpha - 2006-02-09
16479 o Crashes in 0.1.1.x:
16480 - When you tried to setconf ORPort via the controller, Tor would
16481 crash. So people using TorCP to become a server were sad.
16482 - Solve (I hope) the stack-smashing bug that we were seeing on fast
16483 servers. The problem appears to be something do with OpenSSL's
16484 random number generation, or how we call it, or something. Let me
16485 know if the crashes continue.
16486 - Turn crypto hardware acceleration off by default, until we find
16487 somebody smart who can test it for us. (It appears to produce
16488 seg faults in at least some cases.)
16489 - Fix a rare assert error when we've tried all intro points for
16490 a hidden service and we try fetching the service descriptor again:
16491 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
16494 - Fix a major load balance bug: we were round-robining in 16 KB
16495 chunks, and servers with bandwidthrate of 20 KB, while downloading
16496 a 600 KB directory, would starve their other connections. Now we
16497 try to be a bit more fair.
16498 - Dir authorities and mirrors were never expiring the newest
16499 descriptor for each server, causing memory and directory bloat.
16500 - Fix memory-bloating and connection-bloating bug on servers: We
16501 were never closing any connection that had ever had a circuit on
16502 it, because we were checking conn->n_circuits == 0, yet we had a
16503 bug that let it go negative.
16504 - Make Tor work using squid as your http proxy again -- squid
16505 returns an error if you ask for a URL that's too long, and it uses
16506 a really generic error message. Plus, many people are behind a
16507 transparent squid so they don't even realize it.
16508 - On platforms that don't have getrlimit (like Windows), we were
16509 artificially constraining ourselves to a max of 1024
16510 connections. Now just assume that we can handle as many as 15000
16511 connections. Hopefully this won't cause other problems.
16512 - Add a new config option ExitPolicyRejectPrivate which defaults to
16513 1. This means all exit policies will begin with rejecting private
16514 addresses, unless the server operator explicitly turns it off.
16517 - Clients no longer download descriptors for non-running
16519 - Before we add new directory authorities, we should make it
16520 clear that only v1 authorities should receive/publish hidden
16521 service descriptors.
16524 - As soon as we've fetched some more directory info, immediately
16525 try to download more server descriptors. This way we don't have
16526 a 10 second pause during initial bootstrapping.
16527 - Remove even more loud log messages that the server operator can't
16529 - When we're running an obsolete or un-recommended version, make
16530 the log message more clear about what the problem is and what
16531 versions *are* still recommended.
16532 - Provide a more useful warn message when our onion queue gets full:
16533 the CPU is too slow or the exit policy is too liberal.
16534 - Don't warn when we receive a 503 from a dirserver/cache -- this
16535 will pave the way for them being able to refuse if they're busy.
16536 - When we fail to bind a listener, try to provide a more useful
16537 log message: e.g., "Is Tor already running?"
16538 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
16539 Goldberg can prove things about our handshake protocol more
16541 - MaxConn has been obsolete for a while now. Document the ConnLimit
16542 config option, which is a *minimum* number of file descriptors
16543 that must be available else Tor refuses to start.
16544 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16545 if you log to syslog and want something other than LOG_DAEMON.
16546 - Make dirservers generate a separate "guard" flag to mean,
16547 "would make a good entry guard". Make clients parse it and vote
16548 on it. Not used by clients yet.
16549 - Implement --with-libevent-dir option to ./configure. Also, improve
16550 search techniques to find libevent, and use those for openssl too.
16551 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
16552 - Only start testing reachability once we've established a
16553 circuit. This will make startup on dirservers less noisy.
16554 - Don't try to upload hidden service descriptors until we have
16555 established a circuit.
16556 - Fix the controller's "attachstream 0" command to treat conn like
16557 it just connected, doing address remapping, handling .exit and
16558 .onion idioms, and so on. Now we're more uniform in making sure
16559 that the controller hears about new and closing connections.
16562 Changes in version 0.1.1.12-alpha - 2006-01-11
16563 o Bugfixes on 0.1.1.x:
16564 - The fix to close duplicate server connections was closing all
16565 Tor client connections if they didn't establish a circuit
16566 quickly enough. Oops.
16567 - Fix minor memory issue (double-free) that happened on exit.
16569 o Bugfixes on 0.1.0.x:
16570 - Tor didn't warn when it failed to open a log file.
16573 Changes in version 0.1.1.11-alpha - 2006-01-10
16574 o Crashes in 0.1.1.x:
16575 - Include all the assert/crash fixes from 0.1.0.16.
16576 - If you start Tor and then quit very quickly, there were some
16577 races that tried to free things that weren't allocated yet.
16578 - Fix a rare memory stomp if you're running hidden services.
16579 - Fix segfault when specifying DirServer in config without nickname.
16580 - Fix a seg fault when you finish connecting to a server but at
16581 that moment you dump his server descriptor.
16582 - Extendcircuit and Attachstream controller commands would
16583 assert/crash if you don't give them enough arguments.
16584 - Fix an assert error when we're out of space in the connection_list
16585 and we try to post a hidden service descriptor (reported by weasel).
16586 - If you specify a relative torrc path and you set RunAsDaemon in
16587 your torrc, then it chdir()'s to the new directory. If you HUP,
16588 it tries to load the new torrc location, fails, and exits.
16589 The fix: no longer allow a relative path to torrc using -f.
16592 - Implement "entry guards": automatically choose a handful of entry
16593 nodes and stick with them for all circuits. Only pick new guards
16594 when the ones you have are unsuitable, and if the old guards
16595 become suitable again, switch back. This will increase security
16596 dramatically against certain end-point attacks. The EntryNodes
16597 config option now provides some hints about which entry guards you
16598 want to use most; and StrictEntryNodes means to only use those.
16599 - New directory logic: download by descriptor digest, not by
16600 fingerprint. Caches try to download all listed digests from
16601 authorities; clients try to download "best" digests from caches.
16602 This avoids partitioning and isolating attacks better.
16603 - Make the "stable" router flag in network-status be the median of
16604 the uptimes of running valid servers, and make clients pay
16605 attention to the network-status flags. Thus the cutoff adapts
16606 to the stability of the network as a whole, making IRC, IM, etc
16607 connections more reliable.
16610 - Tor servers with dynamic IP addresses were needing to wait 18
16611 hours before they could start doing reachability testing using
16612 the new IP address and ports. This is because they were using
16613 the internal descriptor to learn what to test, yet they were only
16614 rebuilding the descriptor once they decided they were reachable.
16615 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
16616 to download certain server descriptors, throw them away, and then
16617 fetch them again after 30 minutes. Now mirrors throw away these
16618 server descriptors so clients can't get them.
16619 - We were leaving duplicate connections to other ORs open for a week,
16620 rather than closing them once we detect a duplicate. This only
16621 really affected authdirservers, but it affected them a lot.
16622 - Spread the authdirservers' reachability testing over the entire
16623 testing interval, so we don't try to do 500 TLS's at once every
16627 - If the network is down, and we try to connect to a conn because
16628 we have a circuit in mind, and we timeout (30 seconds) because the
16629 network never answers, we were expiring the circuit, but we weren't
16630 obsoleting the connection or telling the entry_guards functions.
16631 - Some Tor servers process billions of cells per day. These statistics
16632 need to be uint64_t's.
16633 - Check for integer overflows in more places, when adding elements
16634 to smartlists. This could possibly prevent a buffer overflow
16635 on malicious huge inputs. I don't see any, but I haven't looked
16637 - ReachableAddresses kept growing new "reject *:*" lines on every
16639 - When you "setconf log" via the controller, it should remove all
16640 logs. We were automatically adding back in a "log notice stdout".
16641 - Newly bootstrapped Tor networks couldn't establish hidden service
16642 circuits until they had nodes with high uptime. Be more tolerant.
16643 - We were marking servers down when they could not answer every piece
16644 of the directory request we sent them. This was far too harsh.
16645 - Fix the torify (tsocks) config file to not use Tor for localhost
16647 - Directory authorities now go to the proper authority when asking for
16648 a networkstatus, even when they want a compressed one.
16649 - Fix a harmless bug that was causing Tor servers to log
16650 "Got an end because of misc error, but we're not an AP. Closing."
16651 - Authorities were treating their own descriptor changes as cosmetic,
16652 meaning the descriptor available in the network-status and the
16653 descriptor that clients downloaded were different.
16654 - The OS X installer was adding a symlink for tor_resolve but
16655 the binary was called tor-resolve (reported by Thomas Hardly).
16656 - Workaround a problem with some http proxies where they refuse GET
16657 requests that specify "Content-Length: 0" (reported by Adrian).
16658 - Fix wrong log message when you add a "HiddenServiceNodes" config
16659 line without any HiddenServiceDir line (reported by Chris Thomas).
16662 - Write the TorVersion into the state file so we have a prayer of
16663 keeping forward and backward compatibility.
16664 - Revive the FascistFirewall config option rather than eliminating it:
16665 now it's a synonym for ReachableAddresses *:80,*:443.
16666 - Clients choose directory servers from the network status lists,
16667 not from their internal list of router descriptors. Now they can
16668 go to caches directly rather than needing to go to authorities
16670 - Directory authorities ignore router descriptors that have only
16671 cosmetic differences: do this for 0.1.0.x servers now too.
16672 - Add a new flag to network-status indicating whether the server
16673 can answer v2 directory requests too.
16674 - Authdirs now stop whining so loudly about bad descriptors that
16675 they fetch from other dirservers. So when there's a log complaint,
16676 it's for sure from a freshly uploaded descriptor.
16677 - Reduce memory requirements in our structs by changing the order
16679 - There used to be two ways to specify your listening ports in a
16680 server descriptor: on the "router" line and with a separate "ports"
16681 line. Remove support for the "ports" line.
16682 - New config option "AuthDirRejectUnlisted" for auth dirservers as
16683 a panic button: if we get flooded with unusable servers we can
16684 revert to only listing servers in the approved-routers file.
16685 - Auth dir servers can now mark a fingerprint as "!reject" or
16686 "!invalid" in the approved-routers file (as its nickname), to
16687 refuse descriptors outright or include them but marked as invalid.
16688 - Servers store bandwidth history across restarts/crashes.
16689 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16690 get a better idea of why their circuits failed. Not used yet.
16691 - Directory mirrors now cache up to 16 unrecognized network-status
16692 docs. Now we can add new authdirservers and they'll be cached too.
16693 - When picking a random directory, prefer non-authorities if any
16695 - New controller option "getinfo desc/all-recent" to fetch the
16696 latest server descriptor for every router that Tor knows about.
16699 Changes in version 0.1.0.16 - 2006-01-02
16700 o Crash bugfixes on 0.1.0.x:
16701 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16702 corrupting the heap, losing FDs, or crashing when we need to resize
16703 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16704 - It turns out sparc64 platforms crash on unaligned memory access
16705 too -- so detect and avoid this.
16706 - Handle truncated compressed data correctly (by detecting it and
16708 - Fix possible-but-unlikely free(NULL) in control.c.
16709 - When we were closing connections, there was a rare case that
16710 stomped on memory, triggering seg faults and asserts.
16711 - Avoid potential infinite recursion when building a descriptor. (We
16712 don't know that it ever happened, but better to fix it anyway.)
16713 - We were neglecting to unlink marked circuits from soon-to-close OR
16714 connections, which caused some rare scribbling on freed memory.
16715 - Fix a memory stomping race bug when closing the joining point of two
16716 rendezvous circuits.
16717 - Fix an assert in time parsing found by Steven Murdoch.
16719 o Other bugfixes on 0.1.0.x:
16720 - When we're doing reachability testing, provide more useful log
16721 messages so the operator knows what to expect.
16722 - Do not check whether DirPort is reachable when we are suppressing
16723 advertising it because of hibernation.
16724 - When building with -static or on Solaris, we sometimes needed -ldl.
16725 - When we're deciding whether a stream has enough circuits around
16726 that can handle it, count the freshly dirty ones and not the ones
16727 that are so dirty they won't be able to handle it.
16728 - When we're expiring old circuits, we had a logic error that caused
16729 us to close new rendezvous circuits rather than old ones.
16730 - Give a more helpful log message when you try to change ORPort via
16731 the controller: you should upgrade Tor if you want that to work.
16732 - We were failing to parse Tor versions that start with "Tor ".
16733 - Tolerate faulty streams better: when a stream fails for reason
16734 exitpolicy, stop assuming that the router is lying about his exit
16735 policy. When a stream fails for reason misc, allow it to retry just
16736 as if it was resolvefailed. When a stream has failed three times,
16737 reset its failure count so we can try again and get all three tries.
16740 Changes in version 0.1.1.10-alpha - 2005-12-11
16741 o Correctness bugfixes on 0.1.0.x:
16742 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16743 corrupting the heap, losing FDs, or crashing when we need to resize
16744 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16745 - Stop doing the complex voodoo overkill checking for insecure
16746 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16747 - When we were closing connections, there was a rare case that
16748 stomped on memory, triggering seg faults and asserts.
16749 - We were neglecting to unlink marked circuits from soon-to-close OR
16750 connections, which caused some rare scribbling on freed memory.
16751 - When we're deciding whether a stream has enough circuits around
16752 that can handle it, count the freshly dirty ones and not the ones
16753 that are so dirty they won't be able to handle it.
16754 - Recover better from TCP connections to Tor servers that are
16755 broken but don't tell you (it happens!); and rotate TLS
16756 connections once a week.
16757 - When we're expiring old circuits, we had a logic error that caused
16758 us to close new rendezvous circuits rather than old ones.
16759 - Fix a scary-looking but apparently harmless bug where circuits
16760 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16761 servers, and never switch to state CIRCUIT_STATE_OPEN.
16762 - When building with -static or on Solaris, we sometimes needed to
16764 - Give a useful message when people run Tor as the wrong user,
16765 rather than telling them to start chowning random directories.
16766 - We were failing to inform the controller about new .onion streams.
16768 o Security bugfixes on 0.1.0.x:
16769 - Refuse server descriptors if the fingerprint line doesn't match
16770 the included identity key. Tor doesn't care, but other apps (and
16771 humans) might actually be trusting the fingerprint line.
16772 - We used to kill the circuit when we receive a relay command we
16773 don't recognize. Now we just drop it.
16774 - Start obeying our firewall options more rigorously:
16775 . If we can't get to a dirserver directly, try going via Tor.
16776 . Don't ever try to connect (as a client) to a place our
16777 firewall options forbid.
16778 . If we specify a proxy and also firewall options, obey the
16779 firewall options even when we're using the proxy: some proxies
16780 can only proxy to certain destinations.
16781 - Fix a bug found by Lasse Overlier: when we were making internal
16782 circuits (intended to be cannibalized later for rendezvous and
16783 introduction circuits), we were picking them so that they had
16784 useful exit nodes. There was no need for this, and it actually
16785 aids some statistical attacks.
16786 - Start treating internal circuits and exit circuits separately.
16787 It's important to keep them separate because internal circuits
16788 have their last hops picked like middle hops, rather than like
16789 exit hops. So exiting on them will break the user's expectations.
16791 o Bugfixes on 0.1.1.x:
16792 - Take out the mis-feature where we tried to detect IP address
16793 flapping for people with DynDNS, and chose not to upload a new
16794 server descriptor sometimes.
16795 - Try to be compatible with OpenSSL 0.9.6 again.
16796 - Log fix: when the controller is logging about .onion addresses,
16797 sometimes it didn't include the ".onion" part of the address.
16798 - Don't try to modify options->DirServers internally -- if the
16799 user didn't specify any, just add the default ones directly to
16800 the trusted dirserver list. This fixes a bug where people running
16801 controllers would use SETCONF on some totally unrelated config
16802 option, and Tor would start yelling at them about changing their
16804 - Let the controller's redirectstream command specify a port, in
16805 case the controller wants to change that too.
16806 - When we requested a pile of server descriptors, we sometimes
16807 accidentally launched a duplicate request for the first one.
16808 - Bugfix for trackhostexits: write down the fingerprint of the
16809 chosen exit, not its nickname, because the chosen exit might not
16811 - When parsing foo.exit, if foo is unknown, and we are leaving
16812 circuits unattached, set the chosen_exit field and leave the
16813 address empty. This matters because controllers got confused
16815 - Directory authorities no longer try to download server
16816 descriptors that they know they will reject.
16818 o Features and updates:
16819 - Replace balanced trees with hash tables: this should make stuff
16820 significantly faster.
16821 - Resume using the AES counter-mode implementation that we ship,
16822 rather than OpenSSL's. Ours is significantly faster.
16823 - Many other CPU and memory improvements.
16824 - Add a new config option FastFirstHopPK (on by default) so clients
16825 do a trivial crypto handshake for their first hop, since TLS has
16826 already taken care of confidentiality and authentication.
16827 - Add a new config option TestSocks so people can see if their
16828 applications are using socks4, socks4a, socks5-with-ip, or
16829 socks5-with-hostname. This way they don't have to keep mucking
16830 with tcpdump and wondering if something got cached somewhere.
16831 - Warn when listening on a public address for socks. I suspect a
16832 lot of people are setting themselves up as open socks proxies,
16833 and they have no idea that jerks on the Internet are using them,
16834 since they simply proxy the traffic into the Tor network.
16835 - Add "private:*" as an alias in configuration for policies. Now
16836 you can simplify your exit policy rather than needing to list
16837 every single internal or nonroutable network space.
16838 - Add a new controller event type that allows controllers to get
16839 all server descriptors that were uploaded to a router in its role
16840 as authoritative dirserver.
16841 - Start shipping socks-extensions.txt, tor-doc-unix.html,
16842 tor-doc-server.html, and stylesheet.css in the tarball.
16843 - Stop shipping tor-doc.html in the tarball.
16846 Changes in version 0.1.1.9-alpha - 2005-11-15
16847 o Usability improvements:
16848 - Start calling it FooListenAddress rather than FooBindAddress,
16849 since few of our users know what it means to bind an address
16851 - Reduce clutter in server logs. We're going to try to make
16852 them actually usable now. New config option ProtocolWarnings that
16853 lets you hear about how _other Tors_ are breaking the protocol. Off
16855 - Divide log messages into logging domains. Once we put some sort
16856 of interface on this, it will let people looking at more verbose
16857 log levels specify the topics they want to hear more about.
16858 - Make directory servers return better http 404 error messages
16859 instead of a generic "Servers unavailable".
16860 - Check for even more Windows version flags when writing the platform
16861 string in server descriptors, and note any we don't recognize.
16862 - Clean up more of the OpenSSL memory when exiting, so we can detect
16863 memory leaks better.
16864 - Make directory authorities be non-versioning, non-naming by
16865 default. Now we can add new directory servers without requiring
16866 their operators to pay close attention.
16867 - When logging via syslog, include the pid whenever we provide
16868 a log entry. Suggested by Todd Fries.
16870 o Performance improvements:
16871 - Directory servers now silently throw away new descriptors that
16872 haven't changed much if the timestamps are similar. We do this to
16873 tolerate older Tor servers that upload a new descriptor every 15
16874 minutes. (It seemed like a good idea at the time.)
16875 - Inline bottleneck smartlist functions; use fast versions by default.
16876 - Add a "Map from digest to void*" abstraction digestmap_t so we
16877 can do less hex encoding/decoding. Use it in router_get_by_digest()
16878 to resolve a performance bottleneck.
16879 - Allow tor_gzip_uncompress to extract as much as possible from
16880 truncated compressed data. Try to extract as many
16881 descriptors as possible from truncated http responses (when
16882 DIR_PURPOSE_FETCH_ROUTERDESC).
16883 - Make circ->onionskin a pointer, not a static array. moria2 was using
16884 125000 circuit_t's after it had been up for a few weeks, which
16885 translates to 20+ megs of wasted space.
16886 - The private half of our EDH handshake keys are now chosen out
16887 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
16889 o Security improvements:
16890 - Start making directory caches retain old routerinfos, so soon
16891 clients can start asking by digest of descriptor rather than by
16892 fingerprint of server.
16893 - Add half our entropy from RAND_poll in OpenSSL. This knows how
16894 to use egd (if present), openbsd weirdness (if present), vms/os2
16895 weirdness (if we ever port there), and more in the future.
16897 o Bugfixes on 0.1.0.x:
16898 - Do round-robin writes of at most 16 kB per write. This might be
16899 more fair on loaded Tor servers, and it might resolve our Windows
16900 crash bug. It might also slow things down.
16901 - Our TLS handshakes were generating a single public/private
16902 keypair for the TLS context, rather than making a new one for
16903 each new connections. Oops. (But we were still rotating them
16904 periodically, so it's not so bad.)
16905 - When we were cannibalizing a circuit with a particular exit
16906 node in mind, we weren't checking to see if that exit node was
16907 already present earlier in the circuit. Oops.
16908 - When a Tor server's IP changes (e.g. from a dyndns address),
16909 upload a new descriptor so clients will learn too.
16910 - Really busy servers were keeping enough circuits open on stable
16911 connections that they were wrapping around the circuit_id
16912 space. (It's only two bytes.) This exposed a bug where we would
16913 feel free to reuse a circuit_id even if it still exists but has
16914 been marked for close. Try to fix this bug. Some bug remains.
16915 - If we would close a stream early (e.g. it asks for a .exit that
16916 we know would refuse it) but the LeaveStreamsUnattached config
16917 option is set by the controller, then don't close it.
16919 o Bugfixes on 0.1.1.8-alpha:
16920 - Fix a big pile of memory leaks, some of them serious.
16921 - Do not try to download a routerdesc if we would immediately reject
16923 - Resume inserting a newline between all router descriptors when
16924 generating (old style) signed directories, since our spec says
16926 - When providing content-type application/octet-stream for
16927 server descriptors using .z, we were leaving out the
16928 content-encoding header. Oops. (Everything tolerated this just
16929 fine, but that doesn't mean we need to be part of the problem.)
16930 - Fix a potential seg fault in getconf and getinfo using version 1
16931 of the controller protocol.
16932 - Avoid crash: do not check whether DirPort is reachable when we
16933 are suppressing it because of hibernation.
16934 - Make --hash-password not crash on exit.
16937 Changes in version 0.1.1.8-alpha - 2005-10-07
16938 o New features (major):
16939 - Clients don't download or use the directory anymore. Now they
16940 download and use network-statuses from the trusted dirservers,
16941 and fetch individual server descriptors as needed from mirrors.
16942 See dir-spec.txt for all the gory details.
16943 - Be more conservative about whether to advertise our DirPort.
16944 The main change is to not advertise if we're running at capacity
16945 and either a) we could hibernate or b) our capacity is low and
16946 we're using a default DirPort.
16947 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
16949 o New features (minor):
16950 - Try to be smart about when to retry network-status and
16951 server-descriptor fetches. Still needs some tuning.
16952 - Stop parsing, storing, or using running-routers output (but
16953 mirrors still cache and serve it).
16954 - Consider a threshold of versioning dirservers (dirservers who have
16955 an opinion about which Tor versions are still recommended) before
16956 deciding whether to warn the user that he's obsolete.
16957 - Dirservers can now reject/invalidate by key and IP, with the
16958 config options "AuthDirInvalid" and "AuthDirReject". This is
16959 useful since currently we automatically list servers as running
16960 and usable even if we know they're jerks.
16961 - Provide dire warnings to any users who set DirServer; move it out
16962 of torrc.sample and into torrc.complete.
16963 - Add MyFamily to torrc.sample in the server section.
16964 - Add nicknames to the DirServer line, so we can refer to them
16965 without requiring all our users to memorize their IP addresses.
16966 - When we get an EOF or a timeout on a directory connection, note
16967 how many bytes of serverdesc we are dropping. This will help
16968 us determine whether it is smart to parse incomplete serverdesc
16970 - Add a new function to "change pseudonyms" -- that is, to stop
16971 using any currently-dirty circuits for new streams, so we don't
16972 link new actions to old actions. Currently it's only called on
16973 HUP (or SIGNAL RELOAD).
16974 - On sighup, if UseHelperNodes changed to 1, use new circuits.
16975 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16976 OpenSSL. Also, reseed our entropy every hour, not just at
16977 startup. And entropy in 512-bit chunks, not 160-bit chunks.
16979 o Fixes on 0.1.1.7-alpha:
16980 - Nobody ever implemented EVENT_ADDRMAP for control protocol
16981 version 0, so don't let version 0 controllers ask for it.
16982 - If you requested something with too many newlines via the
16983 v1 controller protocol, you could crash tor.
16984 - Fix a number of memory leaks, including some pretty serious ones.
16985 - Re-enable DirPort testing again, so Tor servers will be willing
16986 to advertise their DirPort if it's reachable.
16987 - On TLS handshake, only check the other router's nickname against
16988 its expected nickname if is_named is set.
16990 o Fixes forward-ported from 0.1.0.15:
16991 - Don't crash when we don't have any spare file descriptors and we
16992 try to spawn a dns or cpu worker.
16993 - Make the numbers in read-history and write-history into uint64s,
16994 so they don't overflow and publish negatives in the descriptor.
16996 o Fixes on 0.1.0.x:
16997 - For the OS X package's modified privoxy config file, comment
16998 out the "logfile" line so we don't log everything passed
17000 - We were whining about using socks4 or socks5-with-local-lookup
17001 even when it's an IP in the "virtual" range we designed exactly
17003 - We were leaking some memory every time the client changes IPs.
17004 - Never call free() on tor_malloc()d memory. This will help us
17005 use dmalloc to detect memory leaks.
17006 - Check for named servers when looking them up by nickname;
17007 warn when we'recalling a non-named server by its nickname;
17008 don't warn twice about the same name.
17009 - Try to list MyFamily elements by key, not by nickname, and warn
17010 if we've not heard of the server.
17011 - Make windows platform detection (uname equivalent) smarter.
17012 - It turns out sparc64 doesn't like unaligned access either.
17015 Changes in version 0.1.0.15 - 2005-09-23
17016 o Bugfixes on 0.1.0.x:
17017 - Reject ports 465 and 587 (spam targets) in default exit policy.
17018 - Don't crash when we don't have any spare file descriptors and we
17019 try to spawn a dns or cpu worker.
17020 - Get rid of IgnoreVersion undocumented config option, and make us
17021 only warn, never exit, when we're running an obsolete version.
17022 - Don't try to print a null string when your server finds itself to
17023 be unreachable and the Address config option is empty.
17024 - Make the numbers in read-history and write-history into uint64s,
17025 so they don't overflow and publish negatives in the descriptor.
17026 - Fix a minor memory leak in smartlist_string_remove().
17027 - We were only allowing ourselves to upload a server descriptor at
17028 most every 20 minutes, even if it changed earlier than that.
17029 - Clean up log entries that pointed to old URLs.
17032 Changes in version 0.1.1.7-alpha - 2005-09-14
17033 o Fixes on 0.1.1.6-alpha:
17034 - Exit servers were crashing when people asked them to make a
17035 connection to an address not in their exit policy.
17036 - Looking up a non-existent stream for a v1 control connection would
17038 - Fix a seg fault if we ask a dirserver for a descriptor by
17039 fingerprint but he doesn't know about him.
17040 - SETCONF was appending items to linelists, not clearing them.
17041 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
17042 out and refuse the setconf if it would fail.
17043 - Downgrade the dirserver log messages when whining about
17047 - Add Peter Palfrader's check-tor script to tor/contrib/
17048 It lets you easily check whether a given server (referenced by
17049 nickname) is reachable by you.
17050 - Numerous changes to move towards client-side v2 directories. Not
17053 o Fixes on 0.1.0.x:
17054 - If the user gave tor an odd number of command-line arguments,
17055 we were silently ignoring the last one. Now we complain and fail.
17056 [This wins the oldest-bug prize -- this bug has been present since
17057 November 2002, as released in Tor 0.0.0.]
17058 - Do not use unaligned memory access on alpha, mips, or mipsel.
17059 It *works*, but is very slow, so we treat them as if it doesn't.
17060 - Retry directory requests if we fail to get an answer we like
17061 from a given dirserver (we were retrying before, but only if
17062 we fail to connect).
17063 - When writing the RecommendedVersions line, sort them first.
17064 - When the client asked for a rendezvous port that the hidden
17065 service didn't want to provide, we were sending an IP address
17066 back along with the end cell. Fortunately, it was zero. But stop
17068 - Correct "your server is reachable" log entries to indicate that
17069 it was self-testing that told us so.
17072 Changes in version 0.1.1.6-alpha - 2005-09-09
17073 o Fixes on 0.1.1.5-alpha:
17074 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
17075 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
17076 - Fix bug with tor_memmem finding a match at the end of the string.
17077 - Make unit tests run without segfaulting.
17078 - Resolve some solaris x86 compile warnings.
17079 - Handle duplicate lines in approved-routers files without warning.
17080 - Fix bug where as soon as a server refused any requests due to his
17081 exit policy (e.g. when we ask for localhost and he tells us that's
17082 127.0.0.1 and he won't do it), we decided he wasn't obeying his
17083 exit policy using him for any exits.
17084 - Only do openssl hardware accelerator stuff if openssl version is
17087 o New controller features/fixes:
17088 - Add a "RESETCONF" command so you can set config options like
17089 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17090 a config option in the torrc with no value, then it clears it
17091 entirely (rather than setting it to its default).
17092 - Add a "GETINFO config-file" to tell us where torrc is.
17093 - Avoid sending blank lines when GETINFO replies should be empty.
17094 - Add a QUIT command for the controller (for using it manually).
17095 - Fix a bug in SAVECONF that was adding default dirservers and
17096 other redundant entries to the torrc file.
17098 o Start on the new directory design:
17099 - Generate, publish, cache, serve new network-status format.
17100 - Publish individual descriptors (by fingerprint, by "all", and by
17102 - Publish client and server recommended versions separately.
17103 - Allow tor_gzip_uncompress() to handle multiple concatenated
17104 compressed strings. Serve compressed groups of router
17105 descriptors. The compression logic here could be more
17107 - Distinguish v1 authorities (all currently trusted directories)
17108 from v2 authorities (all trusted directories).
17109 - Change DirServers config line to note which dirs are v1 authorities.
17110 - Add configuration option "V1AuthoritativeDirectory 1" which
17111 moria1, moria2, and tor26 should set.
17112 - Remove option when getting directory cache to see whether they
17113 support running-routers; they all do now. Replace it with one
17114 to see whether caches support v2 stuff.
17117 - Dirservers now do their own external reachability testing of each
17118 Tor server, and only list them as running if they've been found to
17119 be reachable. We also send back warnings to the server's logs if
17120 it uploads a descriptor that we already believe is unreachable.
17121 - Implement exit enclaves: if we know an IP address for the
17122 destination, and there's a running Tor server at that address
17123 which allows exit to the destination, then extend the circuit to
17124 that exit first. This provides end-to-end encryption and end-to-end
17125 authentication. Also, if the user wants a .exit address or enclave,
17126 use 4 hops rather than 3, and cannibalize a general circ for it
17128 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
17129 controller. Also, rotate dns and cpu workers if the controller
17130 changes options that will affect them; and initialize the dns
17131 worker cache tree whether or not we start out as a server.
17132 - Only upload a new server descriptor when options change, 18
17133 hours have passed, uptime is reset, or bandwidth changes a lot.
17134 - Check [X-]Forwarded-For headers in HTTP requests when generating
17135 log messages. This lets people run dirservers (and caches) behind
17136 Apache but still know which IP addresses are causing warnings.
17138 o Config option changes:
17139 - Replace (Fascist)Firewall* config options with a new
17140 ReachableAddresses option that understands address policies.
17141 For example, "ReachableAddresses *:80,*:443"
17142 - Get rid of IgnoreVersion undocumented config option, and make us
17143 only warn, never exit, when we're running an obsolete version.
17144 - Make MonthlyAccountingStart config option truly obsolete now.
17146 o Fixes on 0.1.0.x:
17147 - Reject ports 465 and 587 in the default exit policy, since
17148 people have started using them for spam too.
17149 - It turns out we couldn't bootstrap a network since we added
17150 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17151 has never gone down. Add an AssumeReachable config option to let
17152 servers and dirservers bootstrap. When we're trying to build a
17153 high-uptime or high-bandwidth circuit but there aren't enough
17154 suitable servers, try being less picky rather than simply failing.
17155 - Our logic to decide if the OR we connected to was the right guy
17156 was brittle and maybe open to a mitm for unverified routers.
17157 - We weren't cannibalizing circuits correctly for
17158 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17159 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17160 build those from scratch. This should make hidden services faster.
17161 - Predict required circuits better, with an eye toward making hidden
17162 services faster on the service end.
17163 - Retry streams if the exit node sends back a 'misc' failure. This
17164 should result in fewer random failures. Also, after failing
17165 from resolve failed or misc, reset the num failures, so we give
17166 it a fair shake next time we try.
17167 - Clean up the rendezvous warn log msgs, and downgrade some to info.
17168 - Reduce severity on logs about dns worker spawning and culling.
17169 - When we're shutting down and we do something like try to post a
17170 server descriptor or rendezvous descriptor, don't complain that
17171 we seem to be unreachable. Of course we are, we're shutting down.
17172 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17173 We don't use them yet, but maybe one day our DNS resolver will be
17174 able to discover them.
17175 - Make ContactInfo mandatory for authoritative directory servers.
17176 - Require server descriptors to list IPv4 addresses -- hostnames
17177 are no longer allowed. This also fixes some potential security
17178 problems with people providing hostnames as their address and then
17179 preferentially resolving them to partition users.
17180 - Change log line for unreachability to explicitly suggest /etc/hosts
17181 as the culprit. Also make it clearer what IP address and ports we're
17182 testing for reachability.
17183 - Put quotes around user-supplied strings when logging so users are
17184 more likely to realize if they add bad characters (like quotes)
17186 - Let auth dir servers start without specifying an Address config
17188 - Make unit tests (and other invocations that aren't the real Tor)
17189 run without launching listeners, creating subdirectories, and so on.
17192 Changes in version 0.1.1.5-alpha - 2005-08-08
17193 o Bugfixes included in 0.1.0.14.
17195 o Bugfixes on 0.1.0.x:
17196 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17197 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17198 it would silently using ignore the 6668.
17201 Changes in version 0.1.0.14 - 2005-08-08
17202 o Bugfixes on 0.1.0.x:
17203 - Fix the other half of the bug with crypto handshakes
17205 - Fix an assert trigger if you send a 'signal term' via the
17206 controller when it's listening for 'event info' messages.
17209 Changes in version 0.1.1.4-alpha - 2005-08-04
17210 o Bugfixes included in 0.1.0.13.
17213 - Improve tor_gettimeofday() granularity on windows.
17214 - Make clients regenerate their keys when their IP address changes.
17215 - Implement some more GETINFO goodness: expose helper nodes, config
17216 options, getinfo keys.
17219 Changes in version 0.1.0.13 - 2005-08-04
17220 o Bugfixes on 0.1.0.x:
17221 - Fix a critical bug in the security of our crypto handshakes.
17222 - Fix a size_t underflow in smartlist_join_strings2() that made
17223 it do bad things when you hand it an empty smartlist.
17224 - Fix Windows installer to ship Tor license (thanks to Aphex for
17225 pointing out this oversight) and put a link to the doc directory
17227 - Explicitly set no-unaligned-access for sparc: it turns out the
17228 new gcc's let you compile broken code, but that doesn't make it
17232 Changes in version 0.1.1.3-alpha - 2005-07-23
17233 o Bugfixes on 0.1.1.2-alpha:
17234 - Fix a bug in handling the controller's "post descriptor"
17236 - Fix several bugs in handling the controller's "extend circuit"
17238 - Fix a bug in handling the controller's "stream status" event.
17239 - Fix an assert failure if we have a controller listening for
17240 circuit events and we go offline.
17241 - Re-allow hidden service descriptors to publish 0 intro points.
17242 - Fix a crash when generating your hidden service descriptor if
17243 you don't have enough intro points already.
17245 o New features on 0.1.1.2-alpha:
17246 - New controller function "getinfo accounting", to ask how
17247 many bytes we've used in this time period.
17248 - Experimental support for helper nodes: a lot of the risk from
17249 a small static adversary comes because users pick new random
17250 nodes every time they rebuild a circuit. Now users will try to
17251 stick to the same small set of entry nodes if they can. Not
17252 enabled by default yet.
17254 o Bugfixes on 0.1.0.12:
17255 - If you're an auth dir server, always publish your dirport,
17256 even if you haven't yet found yourself to be reachable.
17257 - Fix a size_t underflow in smartlist_join_strings2() that made
17258 it do bad things when you hand it an empty smartlist.
17261 Changes in version 0.1.0.12 - 2005-07-18
17262 o New directory servers:
17263 - tor26 has changed IP address.
17265 o Bugfixes on 0.1.0.x:
17266 - Fix a possible double-free in tor_gzip_uncompress().
17267 - When --disable-threads is set, do not search for or link against
17268 pthreads libraries.
17269 - Don't trigger an assert if an authoritative directory server
17270 claims its dirport is 0.
17271 - Fix bug with removing Tor as an NT service: some people were
17272 getting "The service did not return an error." Thanks to Matt
17276 Changes in version 0.1.1.2-alpha - 2005-07-15
17277 o New directory servers:
17278 - tor26 has changed IP address.
17280 o Bugfixes on 0.1.0.x, crashes/leaks:
17281 - Port the servers-not-obeying-their-exit-policies fix from
17283 - Fix an fd leak in start_daemon().
17284 - On Windows, you can't always reopen a port right after you've
17285 closed it. So change retry_listeners() to only close and re-open
17286 ports that have changed.
17287 - Fix a possible double-free in tor_gzip_uncompress().
17289 o Bugfixes on 0.1.0.x, usability:
17290 - When tor_socketpair() fails in Windows, give a reasonable
17291 Windows-style errno back.
17292 - Let people type "tor --install" as well as "tor -install" when
17294 want to make it an NT service.
17295 - NT service patch from Matt Edman to improve error messages.
17296 - When the controller asks for a config option with an abbreviated
17297 name, give the full name in our response.
17298 - Correct the man page entry on TrackHostExitsExpire.
17299 - Looks like we were never delivering deflated (i.e. compressed)
17300 running-routers lists, even when asked. Oops.
17301 - When --disable-threads is set, do not search for or link against
17302 pthreads libraries.
17304 o Bugfixes on 0.1.1.x:
17305 - Fix a seg fault with autodetecting which controller version is
17309 - New hidden service descriptor format: put a version in it, and
17310 let people specify introduction/rendezvous points that aren't
17311 in "the directory" (which is subjective anyway).
17312 - Allow the DEBUG controller event to work again. Mark certain log
17313 entries as "don't tell this to controllers", so we avoid cycles.
17316 Changes in version 0.1.0.11 - 2005-06-30
17317 o Bugfixes on 0.1.0.x:
17318 - Fix major security bug: servers were disregarding their
17319 exit policies if clients behaved unexpectedly.
17320 - Make OS X init script check for missing argument, so we don't
17321 confuse users who invoke it incorrectly.
17322 - Fix a seg fault in "tor --hash-password foo".
17323 - The MAPADDRESS control command was broken.
17326 Changes in version 0.1.1.1-alpha - 2005-06-29
17328 - Make OS X init script check for missing argument, so we don't
17329 confuse users who invoke it incorrectly.
17330 - Fix a seg fault in "tor --hash-password foo".
17331 - Fix a possible way to DoS dirservers.
17332 - When we complain that your exit policy implicitly allows local or
17333 private address spaces, name them explicitly so operators can
17335 - Make the log message less scary when all the dirservers are
17336 temporarily unreachable.
17337 - We were printing the number of idle dns workers incorrectly when
17341 - Revised controller protocol (version 1) that uses ascii rather
17342 than binary. Add supporting libraries in python and java so you
17343 can use the controller from your applications without caring how
17344 our protocol works.
17345 - Spiffy new support for crypto hardware accelerators. Can somebody
17349 Changes in version 0.0.9.10 - 2005-06-16
17350 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17351 - Refuse relay cells that claim to have a length larger than the
17352 maximum allowed. This prevents a potential attack that could read
17353 arbitrary memory (e.g. keys) from an exit server's process
17357 Changes in version 0.1.0.10 - 2005-06-14
17358 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
17359 libevent before 1.1a.
17362 Changes in version 0.1.0.9-rc - 2005-06-09
17364 - Reset buf->highwater every time buf_shrink() is called, not just on
17365 a successful shrink. This was causing significant memory bloat.
17366 - Fix buffer overflow when checking hashed passwords.
17367 - Security fix: if seeding the RNG on Win32 fails, quit.
17368 - Allow seeding the RNG on Win32 even when you're not running as
17370 - Disable threading on Solaris too. Something is wonky with it,
17371 cpuworkers, and reentrant libs.
17372 - Reenable the part of the code that tries to flush as soon as an
17373 OR outbuf has a full TLS record available. Perhaps this will make
17374 OR outbufs not grow as huge except in rare cases, thus saving lots
17375 of CPU time plus memory.
17376 - Reject malformed .onion addresses rather then passing them on as
17377 normal web requests.
17378 - Adapt patch from Adam Langley: fix possible memory leak in
17379 tor_lookup_hostname().
17380 - Initialize libevent later in the startup process, so the logs are
17381 already established by the time we start logging libevent warns.
17382 - Use correct errno on win32 if libevent fails.
17383 - Check and warn about known-bad/slow libevent versions.
17384 - Pay more attention to the ClientOnly config option.
17385 - Have torctl.in/tor.sh.in check for location of su binary (needed
17387 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
17388 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
17389 HttpProxyAuthenticator
17390 - Stop warning about sigpipes in the logs. We're going to
17391 pretend that getting these occassionally is normal and fine.
17392 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
17394 installer screens; and don't put stuff into StartupItems unless
17395 the user asks you to.
17396 - Require servers that use the default dirservers to have public IP
17397 addresses. We have too many servers that are configured with private
17398 IPs and their admins never notice the log entries complaining that
17399 their descriptors are being rejected.
17400 - Add OSX uninstall instructions. An actual uninstall script will
17404 Changes in version 0.1.0.8-rc - 2005-05-23
17406 - It turns out that kqueue on OS X 10.3.9 was causing kernel
17407 panics. Disable kqueue on all OS X Tors.
17408 - Fix RPM: remove duplicate line accidentally added to the rpm
17410 - Disable threads on openbsd too, since its gethostaddr is not
17412 - Tolerate libevent 0.8 since it still works, even though it's
17414 - Enable building on Red Hat 9.0 again.
17415 - Allow the middle hop of the testing circuit to be running any
17416 version, now that most of them have the bugfix to let them connect
17417 to unknown servers. This will allow reachability testing to work
17418 even when 0.0.9.7-0.0.9.9 become obsolete.
17419 - Handle relay cells with rh.length too large. This prevents
17420 a potential attack that could read arbitrary memory (maybe even
17421 keys) from the exit server's process.
17422 - We screwed up the dirport reachability testing when we don't yet
17423 have a cached version of the directory. Hopefully now fixed.
17424 - Clean up router_load_single_router() (used by the controller),
17425 so it doesn't seg fault on error.
17426 - Fix a minor memory leak when somebody establishes an introduction
17427 point at your Tor server.
17428 - If a socks connection ends because read fails, don't warn that
17429 you're not sending a socks reply back.
17432 - Add HttpProxyAuthenticator config option too, that works like
17433 the HttpsProxyAuthenticator config option.
17434 - Encode hashed controller passwords in hex instead of base64,
17435 to make it easier to write controllers.
17438 Changes in version 0.1.0.7-rc - 2005-05-17
17440 - Fix a bug in the OS X package installer that prevented it from
17441 installing on Tiger.
17442 - Fix a script bug in the OS X package installer that made it
17443 complain during installation.
17444 - Find libevent even if it's hiding in /usr/local/ and your
17445 CFLAGS and LDFLAGS don't tell you to look there.
17446 - Be able to link with libevent as a shared library (the default
17447 after 1.0d), even if it's hiding in /usr/local/lib and even
17448 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17449 assuming you're running gcc. Otherwise fail and give a useful
17451 - Fix a bug in the RPM packager: set home directory for _tor to
17452 something more reasonable when first installing.
17453 - Free a minor amount of memory that is still reachable on exit.
17456 Changes in version 0.1.0.6-rc - 2005-05-14
17458 - Implement --disable-threads configure option. Disable threads on
17459 netbsd by default, because it appears to have no reentrant resolver
17461 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
17462 release (1.1) detects and disables kqueue if it's broken.
17463 - Append default exit policy before checking for implicit internal
17464 addresses. Now we don't log a bunch of complaints on startup
17465 when using the default exit policy.
17466 - Some people were putting "Address " in their torrc, and they had
17467 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17468 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17469 LOCALSTATEDIR/tor instead.
17470 - Fix fragmented-message bug in TorControl.py.
17471 - Resolve a minor bug which would prevent unreachable dirports
17472 from getting suppressed in the published descriptor.
17473 - When the controller gave us a new descriptor, we weren't resolving
17474 it immediately, so Tor would think its address was 0.0.0.0 until
17475 we fetched a new directory.
17476 - Fix an uppercase/lowercase case error in suppressing a bogus
17477 libevent warning on some Linuxes.
17480 - Begin scrubbing sensitive strings from logs by default. Turn off
17481 the config option SafeLogging if you need to do debugging.
17482 - Switch to a new buffer management algorithm, which tries to avoid
17483 reallocing and copying quite as much. In first tests it looks like
17484 it uses *more* memory on average, but less cpu.
17485 - First cut at support for "create-fast" cells. Clients can use
17486 these when extending to their first hop, since the TLS already
17487 provides forward secrecy and authentication. Not enabled on
17489 - When dirservers refuse a router descriptor, we now log its
17490 contactinfo, platform, and the poster's IP address.
17491 - Call tor_free_all instead of connections_free_all after forking, to
17492 save memory on systems that need to fork.
17493 - Whine at you if you're a server and you don't set your contactinfo.
17494 - Implement --verify-config command-line option to check if your torrc
17495 is valid without actually launching Tor.
17496 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
17497 rather than just rejecting it.
17500 Changes in version 0.1.0.5-rc - 2005-04-27
17502 - Stop trying to print a null pointer if an OR conn fails because
17503 we didn't like its cert.
17505 - Switch our internal buffers implementation to use a ring buffer,
17506 to hopefully improve performance for fast servers a lot.
17507 - Add HttpsProxyAuthenticator support (basic auth only), based
17508 on patch from Adam Langley.
17509 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17510 the fast servers that have been joining lately.
17511 - Give hidden service accesses extra time on the first attempt,
17512 since 60 seconds is often only barely enough. This might improve
17514 - Improve performance for dirservers: stop re-parsing the whole
17515 directory every time you regenerate it.
17516 - Add more debugging info to help us find the weird dns freebsd
17517 pthreads bug; cleaner debug messages to help track future issues.
17520 Changes in version 0.0.9.9 - 2005-04-23
17521 o Bugfixes on 0.0.9.x:
17522 - If unofficial Tor clients connect and send weird TLS certs, our
17523 Tor server triggers an assert. This release contains a minimal
17524 backport from the broader fix that we put into 0.1.0.4-rc.
17527 Changes in version 0.1.0.4-rc - 2005-04-23
17529 - If unofficial Tor clients connect and send weird TLS certs, our
17530 Tor server triggers an assert. Stop asserting, and start handling
17531 TLS errors better in other situations too.
17532 - When the controller asks us to tell it about all the debug-level
17533 logs, it turns out we were generating debug-level logs while
17534 telling it about them, which turns into a bad loop. Now keep
17535 track of whether you're sending a debug log to the controller,
17536 and don't log when you are.
17537 - Fix the "postdescriptor" feature of the controller interface: on
17538 non-complete success, only say "done" once.
17540 - Clients are now willing to load balance over up to 2mB, not 1mB,
17541 of advertised bandwidth capacity.
17542 - Add a NoPublish config option, so you can be a server (e.g. for
17543 testing running Tor servers in other Tor networks) without
17544 publishing your descriptor to the primary dirservers.
17547 Changes in version 0.1.0.3-rc - 2005-04-08
17548 o Improvements on 0.1.0.2-rc:
17549 - Client now retries when streams end early for 'hibernating' or
17550 'resource limit' reasons, rather than failing them.
17551 - More automated handling for dirserver operators:
17552 - Automatically approve nodes running 0.1.0.2-rc or later,
17553 now that the the reachability detection stuff is working.
17554 - Now we allow two unverified servers with the same nickname
17555 but different keys. But if a nickname is verified, only that
17556 nickname+key are allowed.
17557 - If you're an authdirserver connecting to an address:port,
17558 and it's not the OR you were expecting, forget about that
17559 descriptor. If he *was* the one you were expecting, then forget
17560 about all other descriptors for that address:port.
17561 - Allow servers to publish descriptors from 12 hours in the future.
17562 Corollary: only whine about clock skew from the dirserver if
17563 he's a trusted dirserver (since now even verified servers could
17564 have quite wrong clocks).
17565 - Adjust maximum skew and age for rendezvous descriptors: let skew
17566 be 48 hours rather than 90 minutes.
17567 - Efficiency improvements:
17568 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17569 it much faster to look up a circuit for each relay cell.
17570 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17571 since they're eating our cpu on exit nodes.
17572 - Stop wasting time doing a case insensitive comparison for every
17573 dns name every time we do any lookup. Canonicalize the names to
17574 lowercase and be done with it.
17575 - Start sending 'truncated' cells back rather than destroy cells,
17576 if the circuit closes in front of you. This means we won't have
17577 to abandon partially built circuits.
17578 - Only warn once per nickname from add_nickname_list_to_smartlist
17579 per failure, so an entrynode or exitnode choice that's down won't
17581 - Put a note in the torrc about abuse potential with the default
17583 - Revise control spec and implementation to allow all log messages to
17584 be sent to controller with their severities intact (suggested by
17585 Matt Edman). Update TorControl to handle new log event types.
17586 - Provide better explanation messages when controller's POSTDESCRIPTOR
17588 - Stop putting nodename in the Platform string in server descriptors.
17589 It doesn't actually help, and it is confusing/upsetting some people.
17591 o Bugfixes on 0.1.0.2-rc:
17592 - We were printing the host mask wrong in exit policies in server
17593 descriptors. This isn't a critical bug though, since we were still
17594 obeying the exit policy internally.
17595 - Fix Tor when compiled with libevent but without pthreads: move
17596 connection_unregister() from _connection_free() to
17598 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
17599 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
17600 when we look through the connection array, we'll find any of the
17601 cpu/dnsworkers. This is no good.
17603 o Bugfixes on 0.0.9.8:
17604 - Fix possible bug on threading platforms (e.g. win32) which was
17605 leaking a file descriptor whenever a cpuworker or dnsworker died.
17606 - When using preferred entry or exit nodes, ignore whether the
17607 circuit wants uptime or capacity. They asked for the nodes, they
17609 - chdir() to your datadirectory at the *end* of the daemonize process,
17610 not the beginning. This was a problem because the first time you
17611 run tor, if your datadir isn't there, and you have runasdaemon set
17612 to 1, it will try to chdir to it before it tries to create it. Oops.
17613 - Handle changed router status correctly when dirserver reloads
17614 fingerprint file. We used to be dropping all unverified descriptors
17615 right then. The bug was hidden because we would immediately
17616 fetch a directory from another dirserver, which would include the
17617 descriptors we just dropped.
17618 - When we're connecting to an OR and he's got a different nickname/key
17619 than we were expecting, only complain loudly if we're an OP or a
17620 dirserver. Complaining loudly to the OR admins just confuses them.
17621 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17622 artificially capped at 500kB.
17625 Changes in version 0.0.9.8 - 2005-04-07
17626 o Bugfixes on 0.0.9.x:
17627 - We have a bug that I haven't found yet. Sometimes, very rarely,
17628 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17629 thinks of itself as idle. This meant that no new circuits ever got
17630 established. Here's a workaround to kill any cpuworker that's been
17631 busy for more than 100 seconds.
17634 Changes in version 0.1.0.2-rc - 2005-04-01
17635 o Bugfixes on 0.1.0.1-rc:
17636 - Fixes on reachability detection:
17637 - Don't check for reachability while hibernating.
17638 - If ORPort is reachable but DirPort isn't, still publish the
17639 descriptor, but zero out DirPort until it's found reachable.
17640 - When building testing circs for ORPort testing, use only
17641 high-bandwidth nodes, so fewer circuits fail.
17642 - Complain about unreachable ORPort separately from unreachable
17643 DirPort, so the user knows what's going on.
17644 - Make sure we only conclude ORPort reachability if we didn't
17645 initiate the conn. Otherwise we could falsely conclude that
17646 we're reachable just because we connected to the guy earlier
17647 and he used that same pipe to extend to us.
17648 - Authdirservers shouldn't do ORPort reachability detection,
17649 since they're in clique mode, so it will be rare to find a
17650 server not already connected to them.
17651 - When building testing circuits, always pick middle hops running
17652 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
17653 bug. (This is a kludge; it will go away when 0.0.9.x becomes
17655 - When we decide we're reachable, actually publish our descriptor
17657 - Fix bug in redirectstream in the controller.
17658 - Fix the state descriptor strings so logs don't claim edge streams
17659 are in a different state than they actually are.
17660 - Use recent libevent features when possible (this only really affects
17661 win32 and osx right now, because the new libevent with these
17662 features hasn't been released yet). Add code to suppress spurious
17664 - Prevent possible segfault in connection_close_unattached_ap().
17665 - Fix newlines on torrc in win32.
17666 - Improve error msgs when tor-resolve fails.
17668 o Improvements on 0.0.9.x:
17669 - New experimental script tor/contrib/ExerciseServer.py (needs more
17670 work) that uses the controller interface to build circuits and
17671 fetch pages over them. This will help us bootstrap servers that
17672 have lots of capacity but haven't noticed it yet.
17673 - New experimental script tor/contrib/PathDemo.py (needs more work)
17674 that uses the controller interface to let you choose whole paths
17676 "<hostname>.<path,separated by dots>.<length of path>.path"
17677 - When we've connected to an OR and handshaked but didn't like
17678 the result, we were closing the conn without sending destroy
17679 cells back for pending circuits. Now send those destroys.
17682 Changes in version 0.0.9.7 - 2005-04-01
17683 o Bugfixes on 0.0.9.x:
17684 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17685 - Compare identity to identity, not to nickname, when extending to
17686 a router not already in the directory. This was preventing us from
17687 extending to unknown routers. Oops.
17688 - Make sure to create OS X Tor user in <500 range, so we aren't
17689 creating actual system users.
17690 - Note where connection-that-hasn't-sent-end was marked, and fix
17691 a few really loud instances of this harmless bug (it's fixed more
17695 Changes in version 0.1.0.1-rc - 2005-03-28
17697 - Add reachability testing. Your Tor server will automatically try
17698 to see if its ORPort and DirPort are reachable from the outside,
17699 and it won't upload its descriptor until it decides they are.
17700 - Handle unavailable hidden services better. Handle slow or busy
17701 hidden services better.
17702 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17704 - New exit policy: accept most low-numbered ports, rather than
17705 rejecting most low-numbered ports.
17706 - More Tor controller support (still experimental). See
17707 http://tor.eff.org/doc/control-spec.txt for all the new features,
17708 including signals to emulate unix signals from any platform;
17709 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17710 closestream; closecircuit; etc.
17711 - Make nt services work and start on startup on win32 (based on
17712 patch by Matt Edman).
17713 - Add a new AddressMap config directive to rewrite incoming socks
17714 addresses. This lets you, for example, declare an implicit
17715 required exit node for certain sites.
17716 - Add a new TrackHostExits config directive to trigger addressmaps
17717 for certain incoming socks addresses -- for sites that break when
17718 your exit keeps changing (based on patch by Mike Perry).
17719 - Redo the client-side dns cache so it's just an addressmap too.
17720 - Notice when our IP changes, and reset stats/uptime/reachability.
17721 - When an application is using socks5, give him the whole variety of
17722 potential socks5 responses (connect refused, host unreachable, etc),
17723 rather than just "success" or "failure".
17724 - A more sane version numbering system. See
17725 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17726 - New contributed script "exitlist": a simple python script to
17727 parse directories and find Tor nodes that exit to listed
17729 - New contributed script "privoxy-tor-toggle" to toggle whether
17730 Privoxy uses Tor. Seems to be configured for Debian by default.
17731 - Report HTTP reasons to client when getting a response from directory
17732 servers -- so you can actually know what went wrong.
17733 - New config option MaxAdvertisedBandwidth which lets you advertise
17734 a low bandwidthrate (to not attract as many circuits) while still
17735 allowing a higher bandwidthrate in reality.
17737 o Robustness/stability fixes:
17738 - Make Tor use Niels Provos's libevent instead of its current
17739 poll-but-sometimes-select mess. This will let us use faster async
17740 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
17742 - pthread support now too. This was forced because when we forked,
17743 we ended up wasting a lot of duplicate ram over time. Also switch
17744 to foo_r versions of some library calls to allow reentry and
17746 - Better handling for heterogeneous / unreliable nodes:
17747 - Annotate circuits w/ whether they aim to contain high uptime nodes
17748 and/or high capacity nodes. When building circuits, choose
17750 - This means that every single node in an intro rend circuit,
17751 not just the last one, will have a minimum uptime.
17752 - New config option LongLivedPorts to indicate application streams
17753 that will want high uptime circuits.
17754 - Servers reset uptime when a dir fetch entirely fails. This
17755 hopefully reflects stability of the server's network connectivity.
17756 - If somebody starts his tor server in Jan 2004 and then fixes his
17757 clock, don't make his published uptime be a year.
17758 - Reset published uptime when you wake up from hibernation.
17759 - Introduce a notion of 'internal' circs, which are chosen without
17760 regard to the exit policy of the last hop. Intro and rendezvous
17761 circs must be internal circs, to avoid leaking information. Resolve
17762 and connect streams can use internal circs if they want.
17763 - New circuit pooling algorithm: make sure to have enough circs around
17764 to satisfy any predicted ports, and also make sure to have 2 internal
17765 circs around if we've required internal circs lately (and with high
17766 uptime if we've seen that lately too).
17767 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17768 which describes how often we retry making new circuits if current
17769 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17770 how long we're willing to make use of an already-dirty circuit.
17771 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17772 circ as necessary, if there are any completed ones lying around
17773 when we try to launch one.
17774 - Make hidden services try to establish a rendezvous for 30 seconds,
17775 rather than for n (where n=3) attempts to build a circuit.
17776 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
17777 "ShutdownWaitLength".
17778 - Try to be more zealous about calling connection_edge_end when
17779 things go bad with edge conns in connection.c.
17780 - Revise tor-spec to add more/better stream end reasons.
17781 - Revise all calls to connection_edge_end to avoid sending "misc",
17782 and to take errno into account where possible.
17785 - Fix a race condition that can trigger an assert, when we have a
17786 pending create cell and an OR connection fails right then.
17787 - Fix several double-mark-for-close bugs, e.g. where we were finding
17788 a conn for a cell even if that conn is already marked for close.
17789 - Make sequence of log messages when starting on win32 with no config
17790 file more reasonable.
17791 - When choosing an exit node for a new non-internal circ, don't take
17792 into account whether it'll be useful for any pending x.onion
17793 addresses -- it won't.
17794 - Turn addr_policy_compare from a tristate to a quadstate; this should
17795 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17796 for google.com" problem.
17797 - Make "platform" string in descriptor more accurate for Win32 servers,
17798 so it's not just "unknown platform".
17799 - Fix an edge case in parsing config options (thanks weasel).
17800 If they say "--" on the commandline, it's not an option.
17801 - Reject odd-looking addresses at the client (e.g. addresses that
17802 contain a colon), rather than having the server drop them because
17804 - tor-resolve requests were ignoring .exit if there was a working circuit
17805 they could use instead.
17806 - REUSEADDR on normal platforms means you can rebind to the port
17807 right after somebody else has let it go. But REUSEADDR on win32
17808 means to let you bind to the port _even when somebody else
17809 already has it bound_! So, don't do that on Win32.
17810 - Change version parsing logic: a version is "obsolete" if it is not
17811 recommended and (1) there is a newer recommended version in the
17812 same series, or (2) there are no recommended versions in the same
17813 series, but there are some recommended versions in a newer series.
17814 A version is "new" if it is newer than any recommended version in
17816 - Stop most cases of hanging up on a socks connection without sending
17820 - Require BandwidthRate to be at least 20kB/s for servers.
17821 - When a dirserver causes you to give a warn, mention which dirserver
17823 - New config option DirAllowPrivateAddresses for authdirservers.
17824 Now by default they refuse router descriptors that have non-IP or
17825 private-IP addresses.
17826 - Stop publishing socksport in the directory, since it's not
17827 actually meant to be public. For compatibility, publish a 0 there
17829 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17830 smart" value, that is low for servers and high for clients.
17831 - If our clock jumps forward by 100 seconds or more, assume something
17832 has gone wrong with our network and abandon all not-yet-used circs.
17833 - Warn when exit policy implicitly allows local addresses.
17834 - If we get an incredibly skewed timestamp from a dirserver mirror
17835 that isn't a verified OR, don't warn -- it's probably him that's
17837 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17838 cookies to disk and doesn't log each web request to disk. (Thanks
17839 to Brett Carrington for pointing this out.)
17840 - When a client asks us for a dir mirror and we don't have one,
17841 launch an attempt to get a fresh one.
17842 - If we're hibernating and we get a SIGINT, exit immediately.
17843 - Add --with-dmalloc ./configure option, to track memory leaks.
17844 - And try to free all memory on closing, so we can detect what
17846 - Cache local dns resolves correctly even when they're .exit
17848 - Give a better warning when some other server advertises an
17849 ORPort that is actually an apache running ssl.
17850 - Add "opt hibernating 1" to server descriptor to make it clearer
17851 whether the server is hibernating.
17854 Changes in version 0.0.9.6 - 2005-03-24
17855 o Bugfixes on 0.0.9.x (crashes and asserts):
17856 - Add new end stream reasons to maintainance branch. Fix bug where
17857 reason (8) could trigger an assert. Prevent bug from recurring.
17858 - Apparently win32 stat wants paths to not end with a slash.
17859 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17860 blowing away the circuit that conn->cpath_layer points to, then
17861 checking to see if the circ is well-formed. Backport check to make
17862 sure we dont use the cpath on a closed connection.
17863 - Prevent circuit_resume_edge_reading_helper() from trying to package
17864 inbufs for marked-for-close streams.
17865 - Don't crash on hup if your options->address has become unresolvable.
17866 - Some systems (like OS X) sometimes accept() a connection and tell
17867 you the remote host is 0.0.0.0:0. If this happens, due to some
17868 other mis-features, we get confused; so refuse the conn for now.
17870 o Bugfixes on 0.0.9.x (other):
17871 - Fix harmless but scary "Unrecognized content encoding" warn message.
17872 - Add new stream error reason: TORPROTOCOL reason means "you are not
17873 speaking a version of Tor I understand; say bye-bye to your stream."
17874 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17875 into the future, now that we are more tolerant of skew. This
17876 resolves a bug where a Tor server would refuse to cache a directory
17877 because all the directories it gets are too far in the future;
17878 yet the Tor server never logs any complaints about clock skew.
17879 - Mac packaging magic: make man pages useable, and do not overwrite
17880 existing torrc files.
17881 - Make OS X log happily to /var/log/tor/tor.log
17884 Changes in version 0.0.9.5 - 2005-02-22
17885 o Bugfixes on 0.0.9.x:
17886 - Fix an assert race at exit nodes when resolve requests fail.
17887 - Stop picking unverified dir mirrors--it only leads to misery.
17888 - Patch from Matt Edman to make NT services work better. Service
17889 support is still not compiled into the executable by default.
17890 - Patch from Dmitri Bely so the Tor service runs better under
17891 the win32 SYSTEM account.
17892 - Make tor-resolve actually work (?) on Win32.
17893 - Fix a sign bug when getrlimit claims to have 4+ billion
17894 file descriptors available.
17895 - Stop refusing to start when bandwidthburst == bandwidthrate.
17896 - When create cells have been on the onion queue more than five
17897 seconds, just send back a destroy and take them off the list.
17900 Changes in version 0.0.9.4 - 2005-02-03
17901 o Bugfixes on 0.0.9:
17902 - Fix an assert bug that took down most of our servers: when
17903 a server claims to have 1 GB of bandwidthburst, don't
17905 - Don't crash as badly if we have spawned the max allowed number
17906 of dnsworkers, or we're out of file descriptors.
17907 - Block more file-sharing ports in the default exit policy.
17908 - MaxConn is now automatically set to the hard limit of max
17909 file descriptors we're allowed (ulimit -n), minus a few for
17911 - Give a clearer message when servers need to raise their
17912 ulimit -n when they start running out of file descriptors.
17913 - SGI Compatibility patches from Jan Schaumann.
17914 - Tolerate a corrupt cached directory better.
17915 - When a dirserver hasn't approved your server, list which one.
17916 - Go into soft hibernation after 95% of the bandwidth is used,
17917 not 99%. This is especially important for daily hibernators who
17918 have a small accounting max. Hopefully it will result in fewer
17919 cut connections when the hard hibernation starts.
17920 - Load-balance better when using servers that claim more than
17921 800kB/s of capacity.
17922 - Make NT services work (experimental, only used if compiled in).
17925 Changes in version 0.0.9.3 - 2005-01-21
17926 o Bugfixes on 0.0.9:
17927 - Backport the cpu use fixes from main branch, so busy servers won't
17928 need as much processor time.
17929 - Work better when we go offline and then come back, or when we
17930 run Tor at boot before the network is up. We do this by
17931 optimistically trying to fetch a new directory whenever an
17932 application request comes in and we think we're offline -- the
17933 human is hopefully a good measure of when the network is back.
17934 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17935 long as you keep using them; actually publish hidserv descriptors
17936 shortly after they change, rather than waiting 20-40 minutes.
17937 - Enable Mac startup script by default.
17938 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17939 - When you update AllowUnverifiedNodes or FirewallPorts via the
17940 controller's setconf feature, we were always appending, never
17942 - When you update HiddenServiceDir via setconf, it was screwing up
17943 the order of reading the lines, making it fail.
17944 - Do not rewrite a cached directory back to the cache; otherwise we
17945 will think it is recent and not fetch a newer one on startup.
17946 - Workaround for webservers that lie about Content-Encoding: Tor
17947 now tries to autodetect compressed directories and compression
17948 itself. This lets us Proxypass dir fetches through apache.
17951 Changes in version 0.0.9.2 - 2005-01-04
17952 o Bugfixes on 0.0.9 (crashes and asserts):
17953 - Fix an assert on startup when the disk is full and you're logging
17955 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17956 style address, then we'd crash.
17957 - Fix an assert trigger when the running-routers string we get from
17958 a dirserver is broken.
17959 - Make worker threads start and run on win32. Now win32 servers
17961 - Bandaid (not actually fix, but now it doesn't crash) an assert
17962 where the dns worker dies mysteriously and the main Tor process
17963 doesn't remember anything about the address it was resolving.
17965 o Bugfixes on 0.0.9 (Win32):
17966 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17967 name out of the warning/assert messages.
17968 - Fix a superficial "unhandled error on read" bug on win32.
17969 - The win32 installer no longer requires a click-through for our
17970 license, since our Free Software license grants rights but does not
17972 - Win32: When connecting to a dirserver fails, try another one
17973 immediately. (This was already working for non-win32 Tors.)
17974 - Stop trying to parse $HOME on win32 when hunting for default
17976 - Make tor-resolve.c work on win32 by calling network_init().
17978 o Bugfixes on 0.0.9 (other):
17979 - Make 0.0.9.x build on Solaris again.
17980 - Due to a fencepost error, we were blowing away the \n when reporting
17981 confvalue items in the controller. So asking for multiple config
17982 values at once couldn't work.
17983 - When listing circuits that are pending on an opening OR connection,
17984 if we're an OR we were listing circuits that *end* at us as
17985 being pending on every listener, dns/cpu worker, etc. Stop that.
17986 - Dirservers were failing to create 'running-routers' or 'directory'
17987 strings if we had more than some threshold of routers. Fix them so
17988 they can handle any number of routers.
17989 - Fix a superficial "Duplicate mark for close" bug.
17990 - Stop checking for clock skew for OR connections, even for servers.
17991 - Fix a fencepost error that was chopping off the last letter of any
17992 nickname that is the maximum allowed nickname length.
17993 - Update URLs in log messages so they point to the new website.
17994 - Fix a potential problem in mangling server private keys while
17995 writing to disk (not triggered yet, as far as we know).
17996 - Include the licenses for other free software we include in Tor,
17997 now that we're shipping binary distributions more regularly.
18000 Changes in version 0.0.9.1 - 2004-12-15
18001 o Bugfixes on 0.0.9:
18002 - Make hibernation actually work.
18003 - Make HashedControlPassword config option work.
18004 - When we're reporting event circuit status to a controller,
18005 don't use the stream status code.
18008 Changes in version 0.0.9 - 2004-12-12
18010 - Clean up manpage and torrc.sample file.
18011 - Clean up severities and text of log warnings.
18013 - Make servers trigger an assert when they enter hibernation.
18016 Changes in version 0.0.9rc7 - 2004-12-08
18017 o Bugfixes on 0.0.9rc:
18018 - Fix a stack-trashing crash when an exit node begins hibernating.
18019 - Avoid looking at unallocated memory while considering which
18020 ports we need to build circuits to cover.
18021 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18022 we shouldn't hold-open-until-flush if the eof arrived first.
18023 - Fix a bug with init_cookie_authentication() in the controller.
18024 - When recommending new-format log lines, if the upper bound is
18025 LOG_ERR, leave it implicit.
18027 o Bugfixes on 0.0.8.1:
18028 - Fix a whole slew of memory leaks.
18029 - Fix isspace() and friends so they still make Solaris happy
18030 but also so they don't trigger asserts on win32.
18031 - Fix parse_iso_time on platforms without strptime (eg win32).
18032 - win32: tolerate extra "readable" events better.
18033 - win32: when being multithreaded, leave parent fdarray open.
18034 - Make unit tests work on win32.
18037 Changes in version 0.0.9rc6 - 2004-12-06
18038 o Bugfixes on 0.0.9pre:
18039 - Clean up some more integer underflow opportunities (not exploitable
18041 - While hibernating, hup should not regrow our listeners.
18042 - Send an end to the streams we close when we hibernate, rather
18043 than just chopping them off.
18044 - React to eof immediately on non-open edge connections.
18046 o Bugfixes on 0.0.8.1:
18047 - Calculate timeout for waiting for a connected cell from the time
18048 we sent the begin cell, not from the time the stream started. If
18049 it took a long time to establish the circuit, we would time out
18050 right after sending the begin cell.
18051 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18052 of * as always matching, so we were picking reject *:* nodes as
18053 exit nodes too. Oops.
18056 - New circuit building strategy: keep a list of ports that we've
18057 used in the past 6 hours, and always try to have 2 circuits open
18058 or on the way that will handle each such port. Seed us with port
18059 80 so web users won't complain that Tor is "slow to start up".
18060 - Make kill -USR1 dump more useful stats about circuits.
18061 - When warning about retrying or giving up, print the address, so
18062 the user knows which one it's talking about.
18063 - If you haven't used a clean circuit in an hour, throw it away,
18064 just to be on the safe side. (This means after 6 hours a totally
18065 unused Tor client will have no circuits open.)
18068 Changes in version 0.0.9rc5 - 2004-12-01
18069 o Bugfixes on 0.0.8.1:
18070 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18071 - Let resolve conns retry/expire also, rather than sticking around
18073 - If we are using select, make sure we stay within FD_SETSIZE.
18075 o Bugfixes on 0.0.9pre:
18076 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
18077 but doesn't seem to be currently; thanks to Ilja van Sprundel for
18079 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
18080 instead. Impose minima and maxima for all *Period options; impose
18081 even tighter maxima for fetching if we are a caching dirserver.
18082 Clip rather than rejecting.
18083 - Fetch cached running-routers from servers that serve it (that is,
18084 authdirservers and servers running 0.0.9rc5-cvs or later.)
18087 - Accept *:706 (silc) in default exit policy.
18088 - Implement new versioning format for post 0.1.
18089 - Support "foo.nickname.exit" addresses, to let Alice request the
18090 address "foo" as viewed by exit node "nickname". Based on a patch
18092 - Make tor --version --version dump the cvs Id of every file.
18095 Changes in version 0.0.9rc4 - 2004-11-28
18096 o Bugfixes on 0.0.8.1:
18097 - Make windows sockets actually non-blocking (oops), and handle
18098 win32 socket errors better.
18100 o Bugfixes on 0.0.9rc1:
18101 - Actually catch the -USR2 signal.
18104 Changes in version 0.0.9rc3 - 2004-11-25
18105 o Bugfixes on 0.0.8.1:
18106 - Flush the log file descriptor after we print "Tor opening log file",
18107 so we don't see those messages days later.
18109 o Bugfixes on 0.0.9rc1:
18110 - Make tor-resolve work again.
18111 - Avoid infinite loop in tor-resolve if tor hangs up on it.
18112 - Fix an assert trigger for clients/servers handling resolves.
18115 Changes in version 0.0.9rc2 - 2004-11-24
18116 o Bugfixes on 0.0.9rc1:
18117 - I broke socks5 support while fixing the eof bug.
18118 - Allow unitless bandwidths and intervals; they default to bytes
18120 - New servers don't start out hibernating; they are active until
18121 they run out of bytes, so they have a better estimate of how
18122 long it takes, and so their operators can know they're working.
18125 Changes in version 0.0.9rc1 - 2004-11-23
18126 o Bugfixes on 0.0.8.1:
18127 - Finally fix a bug that's been plaguing us for a year:
18128 With high load, circuit package window was reaching 0. Whenever
18129 we got a circuit-level sendme, we were reading a lot on each
18130 socket, but only writing out a bit. So we would eventually reach
18131 eof. This would be noticed and acted on even when there were still
18132 bytes sitting in the inbuf.
18133 - When poll() is interrupted, we shouldn't believe the revents values.
18135 o Bugfixes on 0.0.9pre6:
18136 - Fix hibernate bug that caused pre6 to be broken.
18137 - Don't keep rephist info for routers that haven't had activity for
18138 24 hours. (This matters now that clients have keys, since we track
18140 - Never call close_temp_logs while validating log options.
18141 - Fix backslash-escaping on tor.sh.in and torctl.in.
18144 - Implement weekly/monthly/daily accounting: now you specify your
18145 hibernation properties by
18146 AccountingMax N bytes|KB|MB|GB|TB
18147 AccountingStart day|week|month [day] HH:MM
18148 Defaults to "month 1 0:00".
18149 - Let bandwidth and interval config options be specified as 5 bytes,
18150 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18151 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18152 get back to normal.)
18153 - If your requested entry or exit node has advertised bandwidth 0,
18155 - Be more greedy about filling up relay cells -- we try reading again
18156 once we've processed the stuff we read, in case enough has arrived
18157 to fill the last cell completely.
18158 - Apply NT service patch from Osamu Fujino. Still needs more work.
18161 Changes in version 0.0.9pre6 - 2004-11-15
18162 o Bugfixes on 0.0.8.1:
18163 - Fix assert failure on malformed socks4a requests.
18164 - Use identity comparison, not nickname comparison, to choose which
18165 half of circuit-ID-space each side gets to use. This is needed
18166 because sometimes we think of a router as a nickname, and sometimes
18167 as a hex ID, and we can't predict what the other side will do.
18168 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18169 write() call will fail and we handle it there.
18170 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18171 and smartlist_len, which are two major profiling offenders.
18173 o Bugfixes on 0.0.9pre5:
18174 - Fix a bug in read_all that was corrupting config files on windows.
18175 - When we're raising the max number of open file descriptors to
18176 'unlimited', don't log that we just raised it to '-1'.
18177 - Include event code with events, as required by control-spec.txt.
18178 - Don't give a fingerprint when clients do --list-fingerprint:
18179 it's misleading, because it will never be the same again.
18180 - Stop using strlcpy in tor_strndup, since it was slowing us
18182 - Remove warn on startup about missing cached-directory file.
18183 - Make kill -USR1 work again.
18184 - Hibernate if we start tor during the "wait for wakeup-time" phase
18185 of an accounting interval. Log our hibernation plans better.
18186 - Authoritative dirservers now also cache their directory, so they
18187 have it on start-up.
18190 - Fetch running-routers; cache running-routers; compress
18191 running-routers; serve compressed running-routers.z
18192 - Add NSI installer script contributed by J Doe.
18193 - Commit VC6 and VC7 workspace/project files.
18194 - Commit a tor.spec for making RPM files, with help from jbash.
18195 - Add contrib/torctl.in contributed by Glenn Fink.
18196 - Implement the control-spec's SAVECONF command, to write your
18197 configuration to torrc.
18198 - Get cookie authentication for the controller closer to working.
18199 - Include control-spec.txt in the tarball.
18200 - When set_conf changes our server descriptor, upload a new copy.
18201 But don't upload it too often if there are frequent changes.
18202 - Document authentication config in man page, and document signals
18204 - Clean up confusing parts of man page and torrc.sample.
18205 - Make expand_filename handle ~ and ~username.
18206 - Use autoconf to enable largefile support where necessary. Use
18207 ftello where available, since ftell can fail at 2GB.
18208 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18209 log more informatively.
18210 - Give a slightly more useful output for "tor -h".
18211 - Refuse application socks connections to port 0.
18212 - Check clock skew for verified servers, but allow unverified
18213 servers and clients to have any clock skew.
18214 - Break DirFetchPostPeriod into:
18215 - DirFetchPeriod for fetching full directory,
18216 - StatusFetchPeriod for fetching running-routers,
18217 - DirPostPeriod for posting server descriptor,
18218 - RendPostPeriod for posting hidden service descriptors.
18219 - Make sure the hidden service descriptors are at a random offset
18220 from each other, to hinder linkability.
18223 Changes in version 0.0.9pre5 - 2004-11-09
18224 o Bugfixes on 0.0.9pre4:
18225 - Fix a seg fault in unit tests (doesn't affect main program).
18226 - Fix an assert bug where a hidden service provider would fail if
18227 the first hop of his rendezvous circuit was down.
18228 - Hidden service operators now correctly handle version 1 style
18229 INTRODUCE1 cells (nobody generates them still, so not a critical
18231 - If do_hup fails, actually notice.
18232 - Handle more errnos from accept() without closing the listener.
18233 Some OpenBSD machines were closing their listeners because
18234 they ran out of file descriptors.
18235 - Send resolve cells to exit routers that are running a new
18236 enough version of the resolve code to work right.
18237 - Better handling of winsock includes on non-MSV win32 compilers.
18238 - Some people had wrapped their tor client/server in a script
18239 that would restart it whenever it died. This did not play well
18240 with our "shut down if your version is obsolete" code. Now people
18241 don't fetch a new directory if their local cached version is
18243 - Make our autogen.sh work on ksh as well as bash.
18246 - Hibernation: New config option "AccountingMaxKB" lets you
18247 set how many KBytes per month you want to allow your server to
18248 consume. Rather than spreading those bytes out evenly over the
18249 month, we instead hibernate for some of the month and pop up
18250 at a deterministic time, work until the bytes are consumed, then
18251 hibernate again. Config option "MonthlyAccountingStart" lets you
18252 specify which day of the month your billing cycle starts on.
18253 - Control interface: a separate program can now talk to your
18254 client/server over a socket, and get/set config options, receive
18255 notifications of circuits and streams starting/finishing/dying,
18256 bandwidth used, etc. The next step is to get some GUIs working.
18257 Let us know if you want to help out. See doc/control-spec.txt .
18258 - Ship a contrib/tor-control.py as an example script to interact
18259 with the control port.
18260 - "tor --hash-password zzyxz" will output a salted password for
18261 use in authenticating to the control interface.
18262 - New log format in config:
18263 "Log minsev[-maxsev] stdout|stderr|syslog" or
18264 "Log minsev[-maxsev] file /var/foo"
18267 - DirPolicy config option, to let people reject incoming addresses
18268 from their dirserver.
18269 - "tor --list-fingerprint" will list your identity key fingerprint
18271 - Add "pass" target for RedirectExit, to make it easier to break
18272 out of a sequence of RedirectExit rules.
18273 - Clients now generate a TLS cert too, in preparation for having
18274 them act more like real nodes.
18275 - Ship src/win32/ in the tarball, so people can use it to build.
18276 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
18278 - New "router-status" line in directory, to better bind each verified
18279 nickname to its identity key.
18280 - Deprecate unofficial config option abbreviations, and abbreviations
18281 not on the command line.
18282 - Add a pure-C tor-resolve implementation.
18283 - Use getrlimit and friends to ensure we can reach MaxConn (currently
18284 1024) file descriptors.
18286 o Code security improvements, inspired by Ilja:
18287 - Replace sprintf with snprintf. (I think they were all safe, but
18289 - Replace strcpy/strncpy with strlcpy in more places.
18290 - Avoid strcat; use snprintf or strlcat instead.
18291 - snprintf wrapper with consistent (though not C99) overflow behavior.
18294 Changes in version 0.0.9pre4 - 2004-10-17
18295 o Bugfixes on 0.0.9pre3:
18296 - If the server doesn't specify an exit policy, use the real default
18297 exit policy, not reject *:*.
18298 - Ignore fascistfirewall when uploading/downloading hidden service
18299 descriptors, since we go through Tor for those; and when using
18300 an HttpProxy, since we assume it can reach them all.
18301 - When looking for an authoritative dirserver, use only the ones
18302 configured at boot. Don't bother looking in the directory.
18303 - The rest of the fix for get_default_conf_file() on older win32.
18304 - Make 'Routerfile' config option obsolete.
18307 - New 'MyFamily nick1,...' config option for a server to
18308 specify other servers that shouldn't be used in the same circuit
18309 with it. Only believed if nick1 also specifies us.
18310 - New 'NodeFamily nick1,nick2,...' config option for a client to
18311 specify nodes that it doesn't want to use in the same circuit.
18312 - New 'Redirectexit pattern address:port' config option for a
18313 server to redirect exit connections, e.g. to a local squid.
18316 Changes in version 0.0.9pre3 - 2004-10-13
18317 o Bugfixes on 0.0.8.1:
18318 - Better torrc example lines for dirbindaddress and orbindaddress.
18319 - Improved bounds checking on parsed ints (e.g. config options and
18320 the ones we find in directories.)
18321 - Better handling of size_t vs int, so we're more robust on 64
18323 - Fix the rest of the bug where a newly started OR would appear
18324 as unverified even after we've added his fingerprint and hupped
18326 - Fix a bug from 0.0.7: when read() failed on a stream, we would
18327 close it without sending back an end. So 'connection refused'
18328 would simply be ignored and the user would get no response.
18330 o Bugfixes on 0.0.9pre2:
18331 - Serving the cached-on-disk directory to people is bad. We now
18332 provide no directory until we've fetched a fresh one.
18333 - Workaround for bug on windows where cached-directories get crlf
18335 - Make get_default_conf_file() work on older windows too.
18336 - If we write a *:* exit policy line in the descriptor, don't write
18337 any more exit policy lines.
18340 - Use only 0.0.9pre1 and later servers for resolve cells.
18341 - Make the dirservers file obsolete.
18342 - Include a dir-signing-key token in directories to tell the
18343 parsing entity which key is being used to sign.
18344 - Remove the built-in bulky default dirservers string.
18345 - New config option "Dirserver %s:%d [fingerprint]", which can be
18346 repeated as many times as needed. If no dirservers specified,
18347 default to moria1,moria2,tor26.
18348 - Make moria2 advertise a dirport of 80, so people behind firewalls
18349 will be able to get a directory.
18350 - Http proxy support
18351 - Dirservers translate requests for http://%s:%d/x to /x
18352 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18353 be routed through this host.
18354 - Clients ask for /tor/x rather than /x for new enough dirservers.
18355 This way we can one day coexist peacefully with apache.
18356 - Clients specify a "Host: %s%d" http header, to be compatible
18357 with more proxies, and so running squid on an exit node can work.
18360 Changes in version 0.0.8.1 - 2004-10-13
18362 - Fix a seg fault that can be triggered remotely for Tor
18363 clients/servers with an open dirport.
18364 - Fix a rare assert trigger, where routerinfos for entries in
18365 our cpath would expire while we're building the path.
18366 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18367 - Fix a rare seg fault for people running hidden services on
18368 intermittent connections.
18369 - Fix a bug in parsing opt keywords with objects.
18370 - Fix a stale pointer assert bug when a stream detaches and
18372 - Fix a string format vulnerability (probably not exploitable)
18373 in reporting stats locally.
18374 - Fix an assert trigger: sometimes launching circuits can fail
18375 immediately, e.g. because too many circuits have failed recently.
18376 - Fix a compile warning on 64 bit platforms.
18379 Changes in version 0.0.9pre2 - 2004-10-03
18381 - Make fetching a cached directory work for 64-bit platforms too.
18382 - Make zlib.h a required header, not an optional header.
18385 Changes in version 0.0.9pre1 - 2004-10-01
18387 - Stop using separate defaults for no-config-file and
18388 empty-config-file. Now you have to explicitly turn off SocksPort,
18389 if you don't want it open.
18390 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18391 - Improve man page to mention more of the 0.0.8 features.
18392 - Fix a rare seg fault for people running hidden services on
18393 intermittent connections.
18394 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18396 - Fix more dns related bugs: send back resolve_failed and end cells
18397 more reliably when the resolve fails, rather than closing the
18398 circuit and then trying to send the cell. Also attach dummy resolve
18399 connections to a circuit *before* calling dns_resolve(), to fix
18400 a bug where cached answers would never be sent in RESOLVED cells.
18401 - When we run out of disk space, or other log writing error, don't
18402 crash. Just stop logging to that log and continue.
18403 - We were starting to daemonize before we opened our logs, so if
18404 there were any problems opening logs, we would complain to stderr,
18405 which wouldn't work, and then mysteriously exit.
18406 - Fix a rare bug where sometimes a verified OR would connect to us
18407 before he'd uploaded his descriptor, which would cause us to
18408 assign conn->nickname as though he's unverified. Now we look through
18409 the fingerprint list to see if he's there.
18410 - Fix a rare assert trigger, where routerinfos for entries in
18411 our cpath would expire while we're building the path.
18414 - Clients can ask dirservers for /dir.z to get a compressed version
18415 of the directory. Only works for servers running 0.0.9, of course.
18416 - Make clients cache directories and use them to seed their router
18417 lists at startup. This means clients have a datadir again.
18418 - Configuration infrastructure support for warning on obsolete
18420 - Respond to content-encoding headers by trying to uncompress as
18422 - Reply with a deflated directory when a client asks for "dir.z".
18423 We could use allow-encodings instead, but allow-encodings isn't
18424 specified in HTTP 1.0.
18425 - Raise the max dns workers from 50 to 100.
18426 - Discourage people from setting their dirfetchpostperiod more often
18427 than once per minute.
18428 - Protect dirservers from overzealous descriptor uploading -- wait
18429 10 seconds after directory gets dirty, before regenerating.
18432 Changes in version 0.0.8 - 2004-08-25
18433 o Port it to SunOS 5.9 / Athena
18436 Changes in version 0.0.8rc2 - 2004-08-20
18437 o Make it compile on cygwin again.
18438 o When picking unverified routers, skip those with low uptime and/or
18439 low bandwidth, depending on what properties you care about.
18442 Changes in version 0.0.8rc1 - 2004-08-18
18443 o Changes from 0.0.7.3:
18445 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18446 don't put it into the client dns cache.
18447 - If a begin failed due to exit policy, but we believe the IP address
18448 should have been allowed, switch that router to exitpolicy reject *:*
18449 until we get our next directory.
18451 - Clients choose nodes proportional to advertised bandwidth.
18452 - Avoid using nodes with low uptime as introduction points.
18453 - Handle servers with dynamic IP addresses: don't replace
18454 options->Address with the resolved one at startup, and
18455 detect our address right before we make a routerinfo each time.
18456 - 'FascistFirewall' option to pick dirservers and ORs on specific
18457 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18458 which ports are open. (Defaults to 80,443)
18459 - Be more aggressive about trying to make circuits when the network
18460 has changed (e.g. when you unsuspend your laptop).
18461 - Check for time skew on http headers; report date in response to
18463 - If the entrynode config line has only one node, don't pick it as
18465 - Add strict{entry|exit}nodes config options. If set to 1, then
18466 we refuse to build circuits that don't include the specified entry
18468 - OutboundBindAddress config option, to bind to a specific
18469 IP address for outgoing connect()s.
18470 - End truncated log entries (e.g. directories) with "[truncated]".
18472 o Patches to 0.0.8preX:
18474 - Patches to compile and run on win32 again (maybe)?
18475 - Fix crash when looking for ~/.torrc with no $HOME set.
18476 - Fix a race bug in the unit tests.
18477 - Handle verified/unverified name collisions better when new
18478 routerinfo's arrive in a directory.
18479 - Sometimes routers were getting entered into the stats before
18480 we'd assigned their identity_digest. Oops.
18481 - Only pick and establish intro points after we've gotten a
18484 - AllowUnverifiedNodes config option to let circuits choose no-name
18485 routers in entry,middle,exit,introduction,rendezvous positions.
18486 Allow middle and rendezvous positions by default.
18487 - Add a man page for tor-resolve.
18490 Changes in version 0.0.7.3 - 2004-08-12
18491 o Stop dnsworkers from triggering an assert failure when you
18492 ask them to resolve the host "".
18495 Changes in version 0.0.8pre3 - 2004-08-09
18496 o Changes from 0.0.7.2:
18497 - Allow multiple ORs with same nickname in routerlist -- now when
18498 people give us one identity key for a nickname, then later
18499 another, we don't constantly complain until the first expires.
18500 - Remember used bandwidth (both in and out), and publish 15-minute
18501 snapshots for the past day into our descriptor.
18502 - You can now fetch $DIRURL/running-routers to get just the
18503 running-routers line, not the whole descriptor list. (But
18504 clients don't use this yet.)
18505 - When people mistakenly use Tor as an http proxy, point them
18506 at the tor-doc.html rather than the INSTALL.
18507 - Remove our mostly unused -- and broken -- hex_encode()
18508 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18509 for pointing out this bug.)
18510 - Rotate onion keys every 12 hours, not every 2 hours, so we have
18511 fewer problems with people using the wrong key.
18512 - Change the default exit policy to reject the default edonkey,
18513 kazaa, gnutella ports.
18514 - Add replace_file() to util.[ch] to handle win32's rename().
18516 o Changes from 0.0.8preX:
18517 - Fix two bugs in saving onion keys to disk when rotating, so
18518 hopefully we'll get fewer people using old onion keys.
18519 - Fix an assert error that was making SocksPolicy not work.
18520 - Be willing to expire routers that have an open dirport -- it's
18521 just the authoritative dirservers we want to not forget.
18522 - Reject tor-resolve requests for .onion addresses early, so we
18523 don't build a whole rendezvous circuit and then fail.
18524 - When you're warning a server that he's unverified, don't cry
18525 wolf unpredictably.
18526 - Fix a race condition: don't try to extend onto a connection
18527 that's still handshaking.
18528 - For servers in clique mode, require the conn to be open before
18529 you'll choose it for your path.
18530 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
18531 end relay cell, etc.
18532 - Measure bandwidth capacity over the last 24 hours, not just 12
18533 - Bugfix: authoritative dirservers were making and signing a new
18534 directory for each client, rather than reusing the cached one.
18537 Changes in version 0.0.8pre2 - 2004-08-04
18538 o Changes from 0.0.7.2:
18540 - Check directory signature _before_ you decide whether you're
18541 you're running an obsolete version and should exit.
18542 - Check directory signature _before_ you parse the running-routers
18543 list to decide who's running or verified.
18544 - Bugfixes and features:
18545 - Check return value of fclose while writing to disk, so we don't
18546 end up with broken files when servers run out of disk space.
18547 - Log a warning if the user uses an unsafe socks variant, so people
18548 are more likely to learn about privoxy or socat.
18549 - Dirservers now include RFC1123-style dates in the HTTP headers,
18550 which one day we will use to better detect clock skew.
18552 o Changes from 0.0.8pre1:
18553 - Make it compile without warnings again on win32.
18554 - Log a warning if you're running an unverified server, to let you
18555 know you might want to get it verified.
18556 - Only pick a default nickname if you plan to be a server.
18559 Changes in version 0.0.8pre1 - 2004-07-23
18561 - Made our unit tests compile again on OpenBSD 3.5, and tor
18562 itself compile again on OpenBSD on a sparc64.
18563 - We were neglecting milliseconds when logging on win32, so
18564 everything appeared to happen at the beginning of each second.
18566 o Protocol changes:
18567 - 'Extend' relay cell payloads now include the digest of the
18568 intended next hop's identity key. Now we can verify that we're
18569 extending to the right router, and also extend to routers we
18570 hadn't heard of before.
18573 - Tor nodes can now act as relays (with an advertised ORPort)
18574 without being manually verified by the dirserver operators.
18575 - Uploaded descriptors of unverified routers are now accepted
18576 by the dirservers, and included in the directory.
18577 - Verified routers are listed by nickname in the running-routers
18578 list; unverified routers are listed as "$<fingerprint>".
18579 - We now use hash-of-identity-key in most places rather than
18580 nickname or addr:port, for improved security/flexibility.
18581 - To avoid Sybil attacks, paths still use only verified servers.
18582 But now we have a chance to play around with hybrid approaches.
18583 - Nodes track bandwidth usage to estimate capacity (not used yet).
18584 - ClientOnly option for nodes that never want to become servers.
18585 - Directory caching.
18586 - "AuthoritativeDir 1" option for the official dirservers.
18587 - Now other nodes (clients and servers) will cache the latest
18588 directory they've pulled down.
18589 - They can enable their DirPort to serve it to others.
18590 - Clients will pull down a directory from any node with an open
18591 DirPort, and check the signature/timestamp correctly.
18592 - Authoritative dirservers now fetch directories from other
18593 authdirservers, to stay better synced.
18594 - Running-routers list tells who's down also, along with noting
18595 if they're verified (listed by nickname) or unverified (listed
18597 - Allow dirservers to serve running-router list separately.
18598 This isn't used yet.
18599 - ORs connect-on-demand to other ORs
18600 - If you get an extend cell to an OR you're not connected to,
18601 connect, handshake, and forward the create cell.
18602 - The authoritative dirservers stay connected to everybody,
18603 and everybody stays connected to 0.0.7 servers, but otherwise
18604 clients/servers expire unused connections after 5 minutes.
18605 - When servers get a sigint, they delay 30 seconds (refusing new
18606 connections) then exit. A second sigint causes immediate exit.
18607 - File and name management:
18608 - Look for .torrc if no CONFDIR "torrc" is found.
18609 - If no datadir is defined, then choose, make, and secure ~/.tor
18611 - If torrc not found, exitpolicy reject *:*.
18612 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18613 - If no nickname is defined, derive default from hostname.
18614 - Rename secret key files, e.g. identity.key -> secret_id_key,
18615 to discourage people from mailing their identity key to tor-ops.
18616 - Refuse to build a circuit before the directory has arrived --
18617 it won't work anyway, since you won't know the right onion keys
18619 - Try other dirservers immediately if the one you try is down. This
18620 should tolerate down dirservers better now.
18621 - Parse tor version numbers so we can do an is-newer-than check
18622 rather than an is-in-the-list check.
18623 - New socks command 'resolve', to let us shim gethostbyname()
18625 - A 'tor_resolve' script to access the socks resolve functionality.
18626 - A new socks-extensions.txt doc file to describe our
18627 interpretation and extensions to the socks protocols.
18628 - Add a ContactInfo option, which gets published in descriptor.
18629 - Publish OR uptime in descriptor (and thus in directory) too.
18630 - Write tor version at the top of each log file
18631 - New docs in the tarball:
18633 - Document that you should proxy your SSL traffic too.
18636 Changes in version 0.0.7.2 - 2004-07-07
18637 o A better fix for the 0.0.0.0 problem, that will hopefully
18638 eliminate the remaining related assertion failures.
18641 Changes in version 0.0.7.1 - 2004-07-04
18642 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18643 since internally we use 0.0.0.0 to signify "not yet resolved".
18646 Changes in version 0.0.7 - 2004-06-07
18647 o Updated the man page to reflect the new features.
18650 Changes in version 0.0.7rc2 - 2004-06-06
18651 o Changes from 0.0.7rc1:
18652 - Make it build on Win32 again.
18653 o Changes from 0.0.6.2:
18654 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18658 Changes in version 0.0.7rc1 - 2004-06-02
18660 - On sighup, we were adding another log without removing the first
18661 one. So log messages would get duplicated n times for n sighups.
18662 - Several cases of using a connection after we'd freed it. The
18663 problem was that connections that are pending resolve are in both
18664 the pending_resolve tree, and also the circuit's resolving_streams
18665 list. When you want to remove one, you must remove it from both.
18666 - Fix a double-mark-for-close where an end cell arrived for a
18667 resolving stream, and then the resolve failed.
18668 - Check directory signatures based on name of signer, not on whom
18669 we got the directory from. This will let us cache directories more
18672 - Crank up some of our constants to handle more users.
18675 Changes in version 0.0.7pre1 - 2004-06-02
18676 o Fixes for crashes and other obnoxious bugs:
18677 - Fix an epipe bug: sometimes when directory connections failed
18678 to connect, we would give them a chance to flush before closing
18680 - When we detached from a circuit because of resolvefailed, we
18681 would immediately try the same circuit twice more, and then
18682 give up on the resolve thinking we'd tried three different
18684 - Limit the number of intro circuits we'll attempt to build for a
18685 hidden service per 15-minute period.
18686 - Check recommended-software string *early*, before actually parsing
18687 the directory. Thus we can detect an obsolete version and exit,
18688 even if the new directory format doesn't parse.
18689 o Fixes for security bugs:
18690 - Remember which nodes are dirservers when you startup, and if a
18691 random OR enables his dirport, don't automatically assume he's
18692 a trusted dirserver.
18694 - Directory connections were asking the wrong poll socket to
18695 start writing, and not asking themselves to start writing.
18696 - When we detached from a circuit because we sent a begin but
18697 didn't get a connected, we would use it again the first time;
18698 but after that we would correctly switch to a different one.
18699 - Stop warning when the first onion decrypt attempt fails; they
18700 will sometimes legitimately fail now that we rotate keys.
18701 - Override unaligned-access-ok check when $host_cpu is ia64 or
18702 arm. Apparently they allow it but the kernel whines.
18703 - Dirservers try to reconnect periodically too, in case connections
18705 - Fix some memory leaks in directory servers.
18706 - Allow backslash in Win32 filenames.
18707 - Made Tor build complain-free on FreeBSD, hopefully without
18708 breaking other BSD builds. We'll see.
18710 - Doxygen markup on all functions and global variables.
18711 - Make directory functions update routerlist, not replace it. So
18712 now directory disagreements are not so critical a problem.
18713 - Remove the upper limit on number of descriptors in a dirserver's
18714 directory (not that we were anywhere close).
18715 - Allow multiple logfiles at different severity ranges.
18716 - Allow *BindAddress to specify ":port" rather than setting *Port
18717 separately. Allow multiple instances of each BindAddress config
18718 option, so you can bind to multiple interfaces if you want.
18719 - Allow multiple exit policy lines, which are processed in order.
18720 Now we don't need that huge line with all the commas in it.
18721 - Enable accept/reject policies on SOCKS connections, so you can bind
18722 to 0.0.0.0 but still control who can use your OP.
18725 Changes in version 0.0.6.2 - 2004-05-16
18726 o Our integrity-checking digest was checking only the most recent cell,
18727 not the previous cells like we'd thought.
18728 Thanks to Stefan Mark for finding the flaw!
18731 Changes in version 0.0.6.1 - 2004-05-06
18732 o Fix two bugs in our AES counter-mode implementation (this affected
18733 onion-level stream encryption, but not TLS-level). It turns
18734 out we were doing something much more akin to a 16-character
18735 polyalphabetic cipher. Oops.
18736 Thanks to Stefan Mark for finding the flaw!
18737 o Retire moria3 as a directory server, and add tor26 as a directory
18741 Changes in version 0.0.6 - 2004-05-02
18742 [version bump only]
18745 Changes in version 0.0.6rc4 - 2004-05-01
18746 o Update the built-in dirservers list to use the new directory format
18747 o Fix a rare seg fault: if a node offering a hidden service attempts
18748 to build a circuit to Alice's rendezvous point and fails before it
18749 reaches the last hop, it retries with a different circuit, but
18751 o Handle windows socket errors correctly.
18754 Changes in version 0.0.6rc3 - 2004-04-28
18755 o Don't expire non-general excess circuits (if we had enough
18756 circuits open, we were expiring rendezvous circuits -- even
18757 when they had a stream attached. oops.)
18758 o Fetch randomness from /dev/urandom better (not via fopen/fread)
18759 o Better debugging for tls errors
18760 o Some versions of openssl have an SSL_pending function that erroneously
18761 returns bytes when there is a non-application record pending.
18762 o Set Content-Type on the directory and hidserv descriptor.
18763 o Remove IVs from cipher code, since AES-ctr has none.
18764 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18765 o We were using an array of length zero in a few places.
18766 o win32's gethostbyname can't resolve an IP to an IP.
18767 o win32's close can't close a socket.
18770 Changes in version 0.0.6rc2 - 2004-04-26
18771 o Fix a bug where we were closing tls connections intermittently.
18772 It turns out openssl keeps its errors around -- so if an error
18773 happens, and you don't ask about it, and then another openssl
18774 operation happens and succeeds, and you ask if there was an error,
18775 it tells you about the first error. Fun fun.
18776 o Fix a bug that's been lurking since 27 may 03 (!)
18777 When passing back a destroy cell, we would use the wrong circ id.
18778 'Mostly harmless', but still worth fixing.
18779 o Since we don't support truncateds much, don't bother sending them;
18780 just close the circ.
18781 o check for <machine/limits.h> so we build on NetBSD again (I hope).
18782 o don't crash if a conn that sent a begin has suddenly lost its circuit
18783 (this was quite rare).
18786 Changes in version 0.0.6rc1 - 2004-04-25
18787 o We now rotate link (tls context) keys and onion keys.
18788 o CREATE cells now include oaep padding, so you can tell
18789 if you decrypted them correctly.
18790 o Add bandwidthburst to server descriptor.
18791 o Directories now say which dirserver signed them.
18792 o Use a tor_assert macro that logs failed assertions too.
18795 Changes in version 0.0.6pre5 - 2004-04-18
18796 o changes from 0.0.6pre4:
18797 - make tor build on broken freebsd 5.2 installs
18798 - fix a failed assert when you try an intro point, get a nack, and try
18799 a second one and it works.
18800 - when alice uses a port that the hidden service doesn't accept,
18801 it now sends back an end cell (denied by exit policy). otherwise
18802 alice would just have to wait to time out.
18803 - fix another rare bug: when we had tried all the intro
18804 points for a hidden service, we fetched the descriptor
18805 again, but we left our introcirc thinking it had already
18806 sent an intro, so it kept waiting for a response...
18807 - bugfix: when you sleep your hidden-service laptop, as soon
18808 as it wakes up it tries to upload a service descriptor, but
18809 socketpair fails for some reason (localhost not up yet?).
18810 now we simply give up on that upload, and we'll try again later.
18811 i'd still like to find the bug though.
18812 - if an intro circ waiting for an ack dies before getting one, then
18814 - we were reusing stale service descriptors and refetching usable
18818 Changes in version 0.0.6pre4 - 2004-04-14
18819 o changes from 0.0.6pre3:
18820 - when bob fails to connect to the rendezvous point, and his
18821 circ didn't fail because of the rendezvous point itself, then
18822 he retries a couple of times
18823 - we expire introduction and rendezvous circs more thoroughly
18824 (sometimes they were hanging around forever)
18825 - we expire unattached rendezvous streams that have been around
18826 too long (they were sticking around forever).
18827 - fix a measly fencepost error that was crashing everybody with
18831 Changes in version 0.0.6pre3 - 2004-04-14
18832 o changes from 0.0.6pre2:
18833 - make hup work again
18834 - fix some memory leaks for dirservers
18835 - allow more skew in rendezvous descriptor timestamps, to help
18836 handle people like blanu who don't know what time it is
18837 - normal circs are 3 hops, but some rend/intro circs are 4, if
18838 the initiator doesn't get to choose the last hop
18839 - send acks for introductions, so alice can know whether to try
18841 - bob publishes intro points more correctly
18842 o changes from 0.0.5:
18843 - fix an assert trigger that's been plaguing us since the days
18844 of 0.0.2prexx (thanks weasel!)
18845 - retry stream correctly when we fail to connect because of
18846 exit-policy-reject (should try another) or can't-resolve-address
18847 (also should try another, because dns on random internet servers
18849 - when we hup a dirserver and we've *removed* a server from the
18850 approved-routers list, now we remove that server from the
18851 in-memory directories too
18854 Changes in version 0.0.6pre2 - 2004-04-08
18855 o We fixed our base32 implementation. Now it works on all architectures.
18858 Changes in version 0.0.6pre1 - 2004-04-08
18860 - Hidden services and rendezvous points are implemented. Go to
18861 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18862 hidden services. (This only works via a socks4a proxy such as
18863 Privoxy, and currently it's quite slow.)
18866 Changes in version 0.0.5 - 2004-03-30
18867 [version bump only]
18870 Changes in version 0.0.5rc3 - 2004-03-29
18871 o Install torrc as torrc.sample -- we no longer clobber your
18873 o Re-enable recommendedversion checking (we broke it in rc2, oops)
18874 o Add in a 'notice' log level for things the operator should hear
18875 but that aren't warnings
18878 Changes in version 0.0.5rc2 - 2004-03-29
18879 o Hold socks connection open until reply is flushed (if possible)
18880 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18881 the dns farm to do it.
18882 o Fix c99 aliasing warnings in rephist.c
18883 o Don't include server descriptors that are older than 24 hours in the
18885 o Give socks 'reject' replies their whole 15s to attempt to flush,
18886 rather than seeing the 60s timeout and assuming the flush had failed.
18887 o Clean automake droppings from the cvs repository
18890 Changes in version 0.0.5rc1 - 2004-03-28
18891 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18892 o Only build circuits after we've fetched the directory: clients were
18893 using only the directory servers before they'd fetched a directory.
18894 This also means longer startup time; so it goes.
18895 o Fix an assert trigger where an OP would fail to handshake, and we'd
18896 expect it to have a nickname.
18897 o Work around a tsocks bug: do a socks reject when AP connection dies
18898 early, else tsocks goes into an infinite loop.
18901 Changes in version 0.0.4 - 2004-03-26
18902 o When connecting to a dirserver or OR and the network is down,
18906 Changes in version 0.0.3 - 2004-03-26
18907 o Warn and fail if server chose a nickname with illegal characters
18908 o Port to Solaris and Sparc:
18909 - include missing header fcntl.h
18910 - have autoconf find -lsocket -lnsl automatically
18911 - deal with hardware word alignment
18912 - make uname() work (solaris has a different return convention)
18913 - switch from using signal() to sigaction()
18914 o Preliminary work on reputation system:
18915 - Keep statistics on success/fail of connect attempts; they're published
18916 by kill -USR1 currently.
18917 - Add a RunTesting option to try to learn link state by creating test
18918 circuits, even when SocksPort is off.
18919 - Remove unused open circuits when there are too many.
18922 Changes in version 0.0.2 - 2004-03-19
18923 - Include strlcpy and strlcat for safer string ops
18924 - define INADDR_NONE so we compile (but still not run) on solaris
18927 Changes in version 0.0.2pre27 - 2004-03-14
18929 - Allow internal tor networks (we were rejecting internal IPs,
18930 now we allow them if they're set explicitly).
18931 - And fix a few endian issues.
18934 Changes in version 0.0.2pre26 - 2004-03-14
18936 - If a stream times out after 15s without a connected cell, don't
18937 try that circuit again: try a new one.
18938 - Retry streams at most 4 times. Then give up.
18939 - When a dirserver gets a descriptor from an unknown router, it
18940 logs its fingerprint (so the dirserver operator can choose to
18941 accept it even without mail from the server operator).
18942 - Inform unapproved servers when we reject their descriptors.
18943 - Make tor build on Windows again. It works as a client, who knows
18945 - Clearer instructions in the torrc for how to set up a server.
18946 - Be more efficient about reading fd's when our global token bucket
18947 (used for rate limiting) becomes empty.
18949 - Stop asserting that computers always go forward in time. It's
18951 - When we sent a cell (e.g. destroy) and then marked an OR connection
18952 expired, we might close it before finishing a flush if the other
18953 side isn't reading right then.
18954 - Don't allow dirservers to start if they haven't defined
18955 RecommendedVersions
18956 - We were caching transient dns failures. Oops.
18957 - Prevent servers from publishing an internal IP as their address.
18958 - Address a strcat vulnerability in circuit.c
18961 Changes in version 0.0.2pre25 - 2004-03-04
18963 - Put the OR's IP in its router descriptor, not its fqdn. That way
18964 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18967 - If the user typed in an address that didn't resolve, the server
18971 Changes in version 0.0.2pre24 - 2004-03-03
18973 - Fix an assertion failure in dns.c, where we were trying to dequeue
18974 a pending dns resolve even if it wasn't pending
18975 - Fix a spurious socks5 warning about still trying to write after the
18976 connection is finished.
18977 - Hold certain marked_for_close connections open until they're finished
18978 flushing, rather than losing bytes by closing them too early.
18979 - Correctly report the reason for ending a stream
18980 - Remove some duplicate calls to connection_mark_for_close
18981 - Put switch_id and start_daemon earlier in the boot sequence, so it
18982 will actually try to chdir() to options.DataDirectory
18983 - Make 'make test' exit(1) if a test fails; fix some unit tests
18984 - Make tor fail when you use a config option it doesn't know about,
18985 rather than warn and continue.
18986 - Make --version work
18987 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18990 Changes in version 0.0.2pre23 - 2004-02-29
18992 - Print a statement when the first circ is finished, so the user
18993 knows it's working.
18994 - If a relay cell is unrecognized at the end of the circuit,
18995 send back a destroy. (So attacks to mutate cells are more
18997 - New config option 'excludenodes' to avoid certain nodes for circuits.
18998 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18999 so you can collect coredumps there.
19001 - Fix a bug in tls flushing where sometimes data got wedged and
19002 didn't flush until more data got sent. Hopefully this bug was
19003 a big factor in the random delays we were seeing.
19004 - Make 'connected' cells include the resolved IP, so the client
19005 dns cache actually gets populated.
19006 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19007 - When we time-out on a stream and detach from the circuit, send an
19008 end cell down it first.
19009 - Only warn about an unknown router (in exitnodes, entrynodes,
19010 excludenodes) after we've fetched a directory.
19013 Changes in version 0.0.2pre22 - 2004-02-26
19015 - Servers publish less revealing uname information in descriptors.
19016 - More memory tracking and assertions, to crash more usefully when
19018 - If the default torrc isn't there, just use some default defaults.
19019 Plus provide an internal dirservers file if they don't have one.
19020 - When the user tries to use Tor as an http proxy, give them an http
19021 501 failure explaining that we're a socks proxy.
19022 - Dump a new router.desc on hup, to help confused people who change
19023 their exit policies and then wonder why router.desc doesn't reflect
19025 - Clean up the generic tor.sh init script that we ship with.
19027 - If the exit stream is pending on the resolve, and a destroy arrives,
19028 then the stream wasn't getting removed from the pending list. I
19029 think this was the one causing recent server crashes.
19030 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19031 - When it couldn't resolve any dirservers, it was useless from then on.
19032 Now it reloads the RouterFile (or default dirservers) if it has no
19034 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19035 many users don't even *have* a /usr/local/sbin/.
19038 Changes in version 0.0.2pre21 - 2004-02-18
19040 - There's a ChangeLog file that actually reflects the changelog.
19041 - There's a 'torify' wrapper script, with an accompanying
19042 tor-tsocks.conf, that simplifies the process of using tsocks for
19043 tor. It even has a man page.
19044 - The tor binary gets installed to sbin rather than bin now.
19045 - Retry streams where the connected cell hasn't arrived in 15 seconds
19046 - Clean up exit policy handling -- get the default out of the torrc,
19047 so we can update it without forcing each server operator to fix
19049 - Allow imaps and pop3s in default exit policy
19051 - Prevent picking middleman nodes as the last node in the circuit
19054 Changes in version 0.0.2pre20 - 2004-01-30
19056 - We now have a deb package, and it's in debian unstable. Go to
19057 it, apt-getters. :)
19058 - I've split the TotalBandwidth option into BandwidthRate (how many
19059 bytes per second you want to allow, long-term) and
19060 BandwidthBurst (how many bytes you will allow at once before the cap
19061 kicks in). This better token bucket approach lets you, say, set
19062 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19063 performance while not exceeding your monthly bandwidth quota.
19064 - Push out a tls record's worth of data once you've got it, rather
19065 than waiting until you've read everything waiting to be read. This
19066 may improve performance by pipelining better. We'll see.
19067 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19068 from failed circuits (if they haven't been connected yet) and attach
19070 - Expire old streams that haven't managed to connect. Some day we'll
19071 have them reattach to new circuits instead.
19074 - Fix several memory leaks that were causing servers to become bloated
19076 - Fix a few very rare assert triggers. A few more remain.
19077 - Setuid to User _before_ complaining about running as root.
19080 Changes in version 0.0.2pre19 - 2004-01-07
19082 - Fix deadlock condition in dns farm. We were telling a child to die by
19083 closing the parent's file descriptor to him. But newer children were
19084 inheriting the open file descriptor from the parent, and since they
19085 weren't closing it, the socket never closed, so the child never read
19086 eof, so he never knew to exit. Similarly, dns workers were holding
19087 open other sockets, leading to all sorts of chaos.
19088 - New cleaner daemon() code for forking and backgrounding.
19089 - If you log to a file, it now prints an entry at the top of the
19090 logfile so you know it's working.
19091 - The onionskin challenge length was 30 bytes longer than necessary.
19092 - Started to patch up the spec so it's not quite so out of date.
19095 Changes in version 0.0.2pre18 - 2004-01-02
19097 - Fix endian issues with the 'integrity' field in the relay header.
19098 - Fix a potential bug where connections in state
19099 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19102 Changes in version 0.0.2pre17 - 2003-12-30
19104 - Made --debuglogfile (or any second log file, actually) work.
19105 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19106 adversary could force us into an infinite loop.
19109 - Each onionskin handshake now includes a hash of the computed key,
19110 to prove the server's identity and help perfect forward secrecy.
19111 - Changed cell size from 256 to 512 bytes (working toward compatibility
19113 - Changed cell length to 2 bytes, and moved it to the relay header.
19114 - Implemented end-to-end integrity checking for the payloads of
19116 - Separated streamid from 'recognized' (otherwise circuits will get
19117 messed up when we try to have streams exit from the middle). We
19118 use the integrity-checking to confirm that a cell is addressed to
19120 - Randomize the initial circid and streamid values, so an adversary who
19121 breaks into a node can't learn how many circuits or streams have
19125 Changes in version 0.0.2pre16 - 2003-12-14
19127 - Fixed a bug that made HUP trigger an assert
19128 - Fixed a bug where a circuit that immediately failed wasn't being
19129 counted as a failed circuit in counting retries.
19132 - Now we close the circuit when we get a truncated cell: otherwise we're
19133 open to an anonymity attack where a bad node in the path truncates
19134 the circuit and then we open streams at him.
19135 - Add port ranges to exit policies
19136 - Add a conservative default exit policy
19137 - Warn if you're running tor as root
19138 - on HUP, retry OR connections and close/rebind listeners
19139 - options.EntryNodes: try these nodes first when picking the first node
19140 - options.ExitNodes: if your best choices happen to include any of
19141 your preferred exit nodes, you choose among just those preferred
19143 - options.ExcludedNodes: nodes that are never picked in path building
19146 Changes in version 0.0.2pre15 - 2003-12-03
19147 o Robustness and bugfixes:
19148 - Sometimes clients would cache incorrect DNS resolves, which would
19149 really screw things up.
19150 - An OP that goes offline would slowly leak all its sockets and stop
19152 - A wide variety of bugfixes in exit node selection, exit policy
19153 handling, and processing pending streams when a new circuit is
19155 - Pick nodes for a path only from those the directory says are up
19156 - Choose randomly from all running dirservers, not always the first one
19157 - Increase allowed http header size for directory fetch.
19158 - Stop writing to stderr (if we're daemonized it will be closed).
19159 - Enable -g always, so cores will be more useful to me.
19160 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19163 - Wrote a man page. It lists commonly used options.
19166 - Change default loglevel to warn.
19167 - Make PidFile default to null rather than littering in your CWD.
19168 - OnionRouter config option is now obsolete. Instead it just checks
19170 - Moved to a single unified torrc file for both clients and servers.
19173 Changes in version 0.0.2pre14 - 2003-11-29
19174 o Robustness and bugfixes:
19175 - Force the admin to make the DataDirectory himself
19176 - to get ownership/permissions right
19177 - so clients no longer make a DataDirectory and then never use it
19178 - fix bug where a client who was offline for 45 minutes would never
19179 pull down a directory again
19180 - fix (or at least hide really well) the dns assert bug that was
19181 causing server crashes
19182 - warnings and improved robustness wrt clockskew for certs
19183 - use the native daemon(3) to daemonize, when available
19184 - exit if bind() fails
19185 - exit if neither socksport nor orport is defined
19186 - include our own tor_timegm (Win32 doesn't have its own)
19187 - bugfix for win32 with lots of connections
19188 - fix minor bias in PRNG
19189 - make dirserver more robust to corrupt cached directory
19192 - Wrote the design document (woo)
19194 o Circuit building and exit policies:
19195 - Circuits no longer try to use nodes that the directory has told them
19197 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19198 bitcounts (18.0.0.0/8).
19199 - Make AP connections standby for a circuit if no suitable circuit
19200 exists, rather than failing
19201 - Circuits choose exit node based on addr/port, exit policies, and
19202 which AP connections are standing by
19203 - Bump min pathlen from 2 to 3
19204 - Relay end cells have a payload to describe why the stream ended.
19205 - If the stream failed because of exit policy, try again with a new
19207 - Clients have a dns cache to remember resolved addresses.
19208 - Notice more quickly when we have no working circuits
19211 - APPort is now called SocksPort
19212 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19214 - RecommendedVersions is now a config variable rather than
19215 hardcoded (for dirservers)
19216 - Reloads config on HUP
19217 - Usage info on -h or --help
19218 - If you set User and Group config vars, it'll setu/gid to them.
19221 Changes in version 0.0.2pre13 - 2003-10-19
19222 o General stability:
19223 - SSL_write no longer fails when it returns WANTWRITE and the number
19224 of bytes in the buf has changed by the next SSL_write call.
19225 - Fix segfault fetching directory when network is down
19226 - Fix a variety of minor memory leaks
19227 - Dirservers reload the fingerprints file on HUP, so I don't have
19228 to take down the network when I approve a new router
19229 - Default server config file has explicit Address line to specify fqdn
19232 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19233 - Make listener connections not ever alloc bufs
19235 o Autoconf improvements:
19236 - don't clobber an external CFLAGS in ./configure
19237 - Make install now works
19238 - create var/lib/tor on make install
19239 - autocreate a tor.sh initscript to help distribs
19240 - autocreate the torrc and sample-server-torrc with correct paths
19242 o Log files and Daemonizing now work:
19243 - If --DebugLogFile is specified, log to it at -l debug
19244 - If --LogFile is specified, use it instead of commandline
19245 - If --RunAsDaemon is set, tor forks and backgrounds on startup