1 Changes in version 0.2.7.3-????? - 2015-09-1?
4 o Major features (security, hidden services):
5 - For an hidden service, it is now prohibited to use one single
6 EntryNodes to avoid a very easy guard discovery attack. For more
7 details, see the ticket description here:
8 https://trac.torproject.org/projects/tor/ticket/14917. Fixes
11 o Major features (relay, Ed25519):
12 - Significant improvements to the usability of relay-side Ed25519
13 key management. Log messages are better, and the code can recover
14 from far more failure conditions. Thanks to "s7r" for reporting
15 and diagnosing so many of these!
17 o Major bugfixes (relay, Ed25519):
18 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
19 0.2.7.2-alpha. Reported by "s7r".
20 - Improve handling of expired signing keys along with offline master
21 keys. Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
23 o Major enhancements (performance testing):
24 - Add chutney performance testing support to src/test/test-
25 network.sh The following arguments change how chutney verifies the
26 network: "--bytes n" sends n bytes per test connection;
27 "--connections n" makes n test connections per client; and
28 "--hs-multi-client 1" makes each client connect to each HS.
29 Requires the corresponding chutney performance testing changes.
30 Note: using --connections 7 or greater on a HS will trigger issue
31 15937. Patch by "teor". Closes ticket 14175.
34 - Try harder to normalize the exit status of the Tor process to the
35 standard-provided range. Fixes bug 16975; bugfix on every version
37 - Update geoip and geoip6 to the July 8 2015 Maxmind GeoLite2
40 o Minor features (client-side privacy):
41 - Indefinitely extend circuit lifespan by resetting dirtyness, if
42 IsolateSOCKSAuth is in use, the new `KeepAliveIsolateSOCKSAuth`
43 option is set, and streams with SOCKS authentication are attached
44 to the circuit. Implements feature 15482.
46 o Minor features (compilation):
47 - Give a warning as early as possible when trying to build with an
48 unsupported OpenSSL version. Closes ticket 16901.
50 o Minor features (Hidden service directory):
51 - Relays need to have the Fast flag to get the HSDir flag. As this
52 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
53 drop. Fixes ticket 15963.
55 o Minor features (hidden Service Statistics):
56 - Turn on hidden service statistics collection by setting the torrc
57 option HiddenServiceStatistics to "1" by default. Closes
60 o Minor features (hidden service):
61 - Client now uses an introduction point failure cache to know when
62 to fetch or keep a descriptor in their cache.
64 When fetching a descriptor, for every introduction points in it,
65 we look them up in the failure cache to know if we keep the
66 descriptor or not. For this to work, everytime an introduction
67 points is discarded (ex: receiving a NACK), we note it down in our
68 introduction cache. If all introduction points for an onion
69 service are in our failure cache, we discard the descriptor and
72 See rendcache.c for a detailed explanation of the cache's
73 behavior. Closes ticket 16389.
75 o Minor features (performance):
76 - Improve the runtime speed of Ed25519 operations and Curve25519
77 keypair generation when built targeting 32 bit x86 platforms with
78 SSE2 available. Implements ticket 16535.
79 - Improve the runtime speed of Ed25519 signature verification by
80 using Ed25519-donna's batch verification support when there are a
81 lot of signatures to verify at once. Implements ticket 16533.
83 o Minor features (testing):
84 - Autodetect CHUTNEY_PATH if the chutney and tor sources are side-
85 by-side in the same parent directory. Closes ticket 16903. Patch
88 o Minor features (testing, authorities):
89 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags. "A node
90 will never receive the corresponding flag unless that node is
91 specified in the TestingDirAuthVote{Exit,Guard,HSDir} list,
92 regardless of its uptime, bandwidth, exit policy, or DirPort".
93 Closes ticket 14882. Patch by "robgjansen", modified by "teor" as
94 VoteOnHidServDirectoriesV2 is now obsolete. Commit message and
95 changes file by "teor" & "robgjansen".
97 o Minor features (testing, authorities, documentation):
98 - Fix an error in the manual page and comments for
99 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
100 required "ORPort connectivity". While this is true, it is in no
101 way unique to the HSDir flag. Of all the flags, only HSDirs need a
102 DirPort configured in order for the authorities to assign that
103 particular flag. Fixed as part of 14882. Patch by "teor". Bugfix
104 on 0.2.6.3 (f9d57473e1ff on 10 January 2015).
106 o Minor features (testing, bridges, hidden services):
107 - Make "bridges+hs" the default test network. This tests almost all
108 tor functionality during make test-network, while allowing tests
109 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
110 test-network-bridges-hs. Closes tickets 16945 (tor), 16946
111 (chutney) . Patches by "teor".
114 - Check correctly for windows socket errors in the workqueue
115 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
116 - Ensure that worker threads actually exit when a fatal error or
117 shutdown is indicated. This doesn't currently affect the behaviour
118 of Tor, because Tor never indicates fatal error or shutdown except
119 in its unit tests. Fixes bug 16868; bugfix on 0.2.6.3-alpha.
120 - Fix an usage message of tor-resolve(1) so that it no longer lists
121 the removed -F option. Fixes bug 16913; bugfix on
123 - Fix the behavior of crypto_time_t when told to consider times
124 before 1970. (These times were possible when running in a
125 simulated network environment where time()'s output starts at
126 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
127 - When calling channel_free_list(), avoid calling smartlist_remove()
128 while inside a FOREACH loop. This partially reverts commit
129 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
130 removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
131 - When logging malformed hostnames in socks5 requests, respect
132 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
133 - include the TUNING document in our source tarball. It is referred
134 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
137 o Minor bugfix (open file limit):
138 - Fix set_max_file_descriptors() to set by default the max open file
139 limit to the current limit in case setrlimit() fails so we at
140 least have a usable value; Fixes bug 16274; bugfix on tor-
141 0.2.0.10-alpha. Patch by dgoulet.
143 o Minor bugfixes (authority):
144 - Don't assign "HSDir" to a router if it isn't Valid and Running.
145 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
146 - Downgrade log messages about Ed25519 key issues, if they are in
147 old cached router descriptors. Fixes part of bug 16286; bugfix
149 - When we find an Ed25519 key issue in a cached descriptor, stop
150 saying the descriptor was just "uploaded". Fixes another part of
151 bug 16286; bugfix on 0.2.7.2-alpha.
153 o Minor bugfixes (control port):
154 - Control port was using set_max_file_descriptors() with a limit set
155 to 0 to get the max value. A recent fix made this use case return
156 an error and introduced dead code in that function. This triggered
157 a warning that our limit (ConnLimit) was invalid but in reality it
160 Now, to the control port uses a specific getter function to query
161 the value and set_max_file_descriptors() should never be used
162 again for that purpose. Fixes bug 16697; bugfix on 0.2.7.2-alpha.
164 o Minor bugfixes (Ed25519):
165 - Fix a memory leak when reading router descriptors with expired
166 Ed25519 certificate. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
168 o Minor bugfixes (linux seccomp2 sandbox):
169 - Allow bridge authorities to run correctly under the seccomp2
170 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
171 - Allow routers with ed25519 keys to run correctly under the
172 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
174 o Minor bugfixes (relay):
175 - Unblock threads before releasing the mutex to ensure predictable
176 scheduling behavior. Fixes bug 16644; bugfix on 0.2.6.3-alpha.
178 o Code simplification and refactoring:
179 - Change the function that's called when we need to retry all
180 downloads so that it only reschedules the downloads to happen
181 immediately, rather than launching them all at once itself. This
182 further simplifies Tor's callgraph.
183 - Move some format-parsing functions out of crypto.c and
184 crypto_curve25519.c into crypto_format.c and/or util_format.c.
185 - Move the client-only parts of init_keys() into a separate
186 function. Closes ticket 16763.
187 - Simplify the microdesc_free() implementation so that it no longer
188 appears (to code analysis tools) to potentially invoke a huge
189 suite of other microdesc functions.
190 - Simply the control graph further by deferring the inner body of
191 directory_all_unreachable() into a callback. Closes ticket 16762.
192 - Treat the loss of an owning controller as equivalent to a SIGTERM
193 signal. This removes a tiny amount of duplicated code, and
194 simplifies our callgraph. Closes ticekt 16788.
195 - When generating an event to send to the controller, we no longer
196 put the event over the network immediately. Instead, we queue
197 these events, and use a Libevent callback to deliver them. This
198 change simplifies Tor's callgraph by reducing the number of
199 functions from which all other Tor functions are reachable. Closes
201 - Wrap windows-only C files inside '#ifdef _WIN32' so that tools
202 that try to scan or compile every file on Unix won't decide that
205 o Code simplifications and refactoring:
206 - Remove the unused "nulterminate" argument from buf_pullup().
209 - Recommend a 40 GB example AccountingMax in torrc.sample rather
210 than a 4 GB max. Closes ticket 16742.
213 - The internal pure-C tor-fw-helper tool is now removed from the Tor
214 distribution, in favor of the pure-Go clone available from
215 https://github.com/Yawning/tor-fw-helper . The libraries used by
216 the C tor-fw-helper are not, in our opinion, very confidence-
217 inspiring in their secure-proggramming techniques. Closes
221 - Remove the code that would try to aggressively flush controller
222 connections while writing to them. This code was introduced in
223 0.1.2.7-alpha, in order to keep output buffers from exceeding
224 their limits. But there is no longer a maximum output buffer size,
225 and flushing data in this way caused some undesirable recursions
226 in our call graph. Closes ticket 16480.
229 - Add a new set of callgraph analysis scripts that use clang to
230 produce a list of which Tor functions are reachable from which
231 other Tor functions. We're planning to use these to help simplify
232 our code structure by identifying illogical dependencies.
233 - Add new 'test-full' and 'test-full-online' targets to run all
234 tests, including integration tests with stem and chutney.
235 - Make the test-workqueue test work on windows by initializing the
236 network before we begin.
237 - New make target (make test-network-all) to run multiple applicable
238 chutney test cases. Patch from Teor; closes 16953.
239 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
240 functions in dns.c. Implements a portion of ticket 16831.
241 - When building Tor with testing coverage enabled, run Chutney tests
242 (if any) using the 'tor-cov' coverage binary.
243 - When running test-network or test-stem, check for the absence of
244 stem/chutney before doing any build operations.
247 Changes in version 0.2.7.2-alpha - 2015-07-27
248 This, the second alpha in the Tor 0.2.7 series, has a number of new
249 features, including a way to manually pick the number of introduction
250 points for hidden services, and the much stronger Ed25519 signing key
251 algorithm for regular Tor relays (including support for encrypted
252 offline identity keys in the new algorithm).
254 Support for Ed25519 on relays is currently limited to signing router
255 descriptors; later alphas in this series will extend Ed25519 key
256 support to more parts of the Tor protocol.
258 o Major features (Ed25519 identity keys, Proposal 220):
259 - All relays now maintain a stronger identity key, using the Ed25519
260 elliptic curve signature format. This master key is designed so
261 that it can be kept offline. Relays also generate an online
262 signing key, and a set of other Ed25519 keys and certificates.
263 These are all automatically regenerated and rotated as needed.
264 Implements part of ticket 12498.
265 - Directory authorities now vote on Ed25519 identity keys along with
266 RSA1024 keys. Implements part of ticket 12498.
267 - Directory authorities track which Ed25519 identity keys have been
268 used with which RSA1024 identity keys, and do not allow them to
269 vary freely. Implements part of ticket 12498.
270 - Microdescriptors now include Ed25519 identity keys. Implements
271 part of ticket 12498.
272 - Add support for offline encrypted Ed25519 master keys. To use this
273 feature on your tor relay, run "tor --keygen" to make a new master
274 key (or to make a new signing key if you already have a master
275 key). Closes ticket 13642.
277 o Major features (Hidden services):
278 - Add the torrc option HiddenServiceNumIntroductionPoints, to
279 specify a fixed number of introduction points. Its maximum value
280 is 10 and default is 3. Using this option can increase a hidden
281 service's reliability under load, at the cost of making it more
282 visible that the hidden service is facing extra load. Closes
284 - Remove the adaptive algorithm for choosing the number of
285 introduction points, which used to change the number of
286 introduction points (poorly) depending on the number of
287 connections the HS sees. Closes ticket 4862.
289 o Major features (onion key cross-certification):
290 - Relay descriptors now include signatures of their own identity
291 keys, made using the TAP and ntor onion keys. These signatures
292 allow relays to prove ownership of their own onion keys. Because
293 of this change, microdescriptors will no longer need to include
294 RSA identity keys. Implements proposal 228; closes ticket 12499.
296 o Major features (performance):
297 - Improve the runtime speed of Ed25519 operations by using the
298 public-domain Ed25519-donna by Andrew M. ("floodyberry").
299 Implements ticket 16467.
300 - Improve the runtime speed of the ntor handshake by using an
301 optimized curve25519 basepoint scalarmult implementation from the
302 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
303 ideas by Adam Langley. Implements ticket 9663.
305 o Major bugfixes (client-side privacy, also in 0.2.6.9):
306 - Properly separate out each SOCKSPort when applying stream
307 isolation. The error occurred because each port's session group
308 was being overwritten by a default value when the listener
309 connection was initialized. Fixes bug 16247; bugfix on
310 0.2.6.3-alpha. Patch by "jojelino".
312 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
313 - Stop refusing to store updated hidden service descriptors on a
314 client. This reverts commit 9407040c59218 (which indeed fixed bug
315 14219, but introduced a major hidden service reachability
316 regression detailed in bug 16381). This is a temporary fix since
317 we can live with the minor issue in bug 14219 (it just results in
318 some load on the network) but the regression of 16381 is too much
319 of a setback. First-round fix for bug 16381; bugfix
322 o Major bugfixes (hidden services):
323 - When cannibalizing a circuit for an introduction point, always
324 extend to the chosen exit node (creating a 4 hop circuit).
325 Previously Tor would use the current circuit exit node, which
326 changed the original choice of introduction point, and could cause
327 the hidden service to skip excluded introduction points or
328 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
331 o Major bugfixes (open file limit):
332 - The open file limit wasn't checked before calling
333 tor_accept_socket_nonblocking(), which would make Tor exceed the
334 limit. Now, before opening a new socket, Tor validates the open
335 file limit just before, and if the max has been reached, return an
336 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
338 o Major bugfixes (stability, also in 0.2.6.10):
339 - Stop crashing with an assertion failure when parsing certain kinds
340 of malformed or truncated microdescriptors. Fixes bug 16400;
341 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
342 by "cypherpunks_backup".
343 - Stop random client-side assertion failures that could occur when
344 connecting to a busy hidden service, or connecting to a hidden
345 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
348 o Minor features (directory authorities, security, also in 0.2.6.9):
349 - The HSDir flag given by authorities now requires the Stable flag.
350 For the current network, this results in going from 2887 to 2806
351 HSDirs. Also, it makes it harder for an attacker to launch a sybil
352 attack by raising the effort for a relay to become Stable to
353 require at the very least 7 days, while maintaining the 96 hours
354 uptime requirement for HSDir. Implements ticket 8243.
356 o Minor features (client):
357 - Relax the validation of hostnames in SOCKS5 requests, allowing the
358 character '_' to appear, in order to cope with domains observed in
359 the wild that are serving non-RFC compliant records. Resolves
361 - Relax the validation done to hostnames in SOCKS5 requests, and
362 allow a single trailing '.' to cope with clients that pass FQDNs
363 using that syntax to explicitly indicate that the domain name is
364 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
365 - Add GroupWritable and WorldWritable options to unix-socket based
366 SocksPort and ControlPort options. These options apply to a single
367 socket, and override {Control,Socks}SocketsGroupWritable. Closes
370 o Minor features (control protocol):
371 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
372 the control protocol. Resolves ticket 15358.
374 o Minor features (directory authorities):
375 - Directory authorities no longer vote against the "Fast", "Stable",
376 and "HSDir" flags just because they were going to vote against
377 "Running": if the consensus turns out to be that the router was
378 running, then the authority's vote should count. Patch from Peter
379 Retzlaff; closes issue 8712.
381 o Minor features (geoip, also in 0.2.6.10):
382 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
383 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
385 o Minor features (hidden services):
386 - Add the new options "HiddenServiceMaxStreams" and
387 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
388 limit the maximum number of simultaneous streams per circuit, and
389 optionally tear down the circuit when the limit is exceeded. Part
392 o Minor features (portability):
393 - Use C99 variadic macros when the compiler is not GCC. This avoids
394 failing compilations on MSVC, and fixes a log-file-based race
395 condition in our old workarounds. Original patch from Gisle Vanem.
397 o Minor bugfixes (compilation, also in 0.2.6.9):
398 - Build with --enable-systemd correctly when libsystemd is
399 installed, but systemd is not. Fixes bug 16164; bugfix on
400 0.2.6.3-alpha. Patch from Peter Palfrader.
402 o Minor bugfixes (controller):
403 - Add the descriptor ID in each HS_DESC control event. It was
404 missing, but specified in control-spec.txt. Fixes bug 15881;
405 bugfix on 0.2.5.2-alpha.
407 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
408 - Check for failures from crypto_early_init, and refuse to continue.
409 A previous typo meant that we could keep going with an
410 uninitialized crypto library, and would have OpenSSL initialize
411 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
412 when implementing ticket 4900. Patch by "teor".
414 o Minor bugfixes (hidden services):
415 - Fix a crash when reloading configuration while at least one
416 configured and one ephemeral hidden service exists. Fixes bug
417 16060; bugfix on 0.2.7.1-alpha.
418 - Avoid crashing with a double-free bug when we create an ephemeral
419 hidden service but adding it fails for some reason. Fixes bug
420 16228; bugfix on 0.2.7.1-alpha.
422 o Minor bugfixes (Linux seccomp2 sandbox):
423 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
424 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
426 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
427 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
428 these when eventfd2() support is missing. Fixes bug 16363; bugfix
429 on 0.2.6.3-alpha. Patch from "teor".
431 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
432 - Fix sandboxing to work when running as a relay, by allowing the
433 renaming of secret_id_key, and allowing the eventfd2 and futex
434 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
436 - Allow systemd connections to work with the Linux seccomp2 sandbox
437 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
440 o Minor bugfixes (relay):
441 - Fix a rarely-encountered memory leak when failing to initialize
442 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
445 o Minor bugfixes (systemd):
446 - Fix an accidental formatting error that broke the systemd
447 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
448 - Tor's systemd unit file no longer contains extraneous spaces.
449 These spaces would sometimes confuse tools like deb-systemd-
450 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
452 o Minor bugfixes (tests):
453 - Use the configured Python executable when running test-stem-full.
454 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
456 o Minor bugfixes (tests, also in 0.2.6.9):
457 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
458 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
460 o Minor bugfixes (threads, comments):
461 - Always initialize return value in compute_desc_id in rendcommon.c
462 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
463 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
464 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
465 - Remove undefined directive-in-macro in test_util_writepid clang
466 3.7 complains that using a preprocessor directive inside a macro
467 invocation in test_util_writepid in test_util.c is undefined.
468 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
470 o Code simplification and refactoring:
471 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
472 to ensure they remain consistent and visible everywhere.
473 - Remove some vestigial workarounds for the MSVC6 compiler. We
474 haven't supported that in ages.
475 - The link authentication code has been refactored for better
476 testability and reliability. It now uses code generated with the
477 "trunnel" binary encoding generator, to reduce the risk of bugs
478 due to programmer error. Done as part of ticket 12498.
481 - Include a specific and (hopefully) accurate documentation of the
482 torrc file's meta-format in doc/torrc_format.txt. This is mainly
483 of interest to people writing programs to parse or generate torrc
484 files. This document is not a commitment to long-term
485 compatibility; some aspects of the current format are a bit
486 ridiculous. Closes ticket 2325.
489 - Tor no longer supports copies of OpenSSL that are missing support
490 for Elliptic Curve Cryptography. (We began using ECC when
491 available in 0.2.4.8-alpha, for more safe and efficient key
492 negotiation.) In particular, support for at least one of P256 or
493 P224 is now required, with manual configuration needed if only
494 P224 is available. Resolves ticket 16140.
495 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
496 on an operating system that has not upgraded to OpenSSL 1.0 or
497 later, and you compile Tor from source, you will need to install a
498 more recent OpenSSL to link Tor against.) These versions of
499 OpenSSL are still supported by the OpenSSL, but the numerous
500 cryptographic improvements in later OpenSSL releases makes them a
501 clear choice. Resolves ticket 16034.
502 - Remove the HidServDirectoryV2 option. Now all relays offer to
503 store hidden service descriptors. Related to 16543.
504 - Remove the VoteOnHidServDirectoriesV2 option, since all
505 authorities have long set it to 1. Closes ticket 16543.
508 - Document use of coverity, clang static analyzer, and clang dynamic
509 undefined behavior and address sanitizers in doc/HACKING. Include
510 detailed usage instructions in the blacklist. Patch by "teor".
512 - The link authentication protocol code now has extensive tests.
513 - The relay descriptor signature testing code now has
515 - The test_workqueue program now runs faster, and is enabled by
516 default as a part of "make check".
517 - Now that OpenSSL has its own scrypt implementation, add an unit
518 test that checks for interoperability between libscrypt_scrypt()
519 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
520 and rely on EVP_PBE_scrypt() whenever possible. Resolves
524 Changes in version 0.2.6.10 - 2015-07-12
525 Tor version 0.2.6.10 fixes some significant stability and hidden
526 service client bugs, bulletproofs the cryptography init process, and
527 fixes a bug when using the sandbox code with some older versions of
528 Linux. Everyone running an older version, especially an older version
529 of 0.2.6, should upgrade.
531 o Major bugfixes (hidden service clients, stability):
532 - Stop refusing to store updated hidden service descriptors on a
533 client. This reverts commit 9407040c59218 (which indeed fixed bug
534 14219, but introduced a major hidden service reachability
535 regression detailed in bug 16381). This is a temporary fix since
536 we can live with the minor issue in bug 14219 (it just results in
537 some load on the network) but the regression of 16381 is too much
538 of a setback. First-round fix for bug 16381; bugfix
541 o Major bugfixes (stability):
542 - Stop crashing with an assertion failure when parsing certain kinds
543 of malformed or truncated microdescriptors. Fixes bug 16400;
544 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
545 by "cypherpunks_backup".
546 - Stop random client-side assertion failures that could occur when
547 connecting to a busy hidden service, or connecting to a hidden
548 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
551 o Minor features (geoip):
552 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
553 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
555 o Minor bugfixes (crypto error-handling):
556 - Check for failures from crypto_early_init, and refuse to continue.
557 A previous typo meant that we could keep going with an
558 uninitialized crypto library, and would have OpenSSL initialize
559 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
560 when implementing ticket 4900. Patch by "teor".
562 o Minor bugfixes (Linux seccomp2 sandbox):
563 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
564 these when eventfd2() support is missing. Fixes bug 16363; bugfix
565 on 0.2.6.3-alpha. Patch from "teor".
568 Changes in version 0.2.6.9 - 2015-06-11
569 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
570 requirements for receiving an HSDir flag, and addresses some other small
571 bugs in the systemd and sandbox code. Clients using circuit isolation
572 should upgrade; all directory authorities should upgrade.
574 o Major bugfixes (client-side privacy):
575 - Properly separate out each SOCKSPort when applying stream
576 isolation. The error occurred because each port's session group was
577 being overwritten by a default value when the listener connection
578 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
581 o Minor feature (directory authorities, security):
582 - The HSDir flag given by authorities now requires the Stable flag.
583 For the current network, this results in going from 2887 to 2806
584 HSDirs. Also, it makes it harder for an attacker to launch a sybil
585 attack by raising the effort for a relay to become Stable which
586 takes at the very least 7 days to do so and by keeping the 96
587 hours uptime requirement for HSDir. Implements ticket 8243.
589 o Minor bugfixes (compilation):
590 - Build with --enable-systemd correctly when libsystemd is
591 installed, but systemd is not. Fixes bug 16164; bugfix on
592 0.2.6.3-alpha. Patch from Peter Palfrader.
594 o Minor bugfixes (Linux seccomp2 sandbox):
595 - Fix sandboxing to work when running as a relaymby renaming of
596 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
597 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
598 - Allow systemd connections to work with the Linux seccomp2 sandbox
599 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
602 o Minor bugfixes (tests):
603 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
604 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
607 Changes in version 0.2.6.8 - 2015-05-21
608 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
609 fixes an authority-side bug in assigning the HSDir flag. All directory
610 authorities should upgrade.
612 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
613 - Revert commit that made directory authorities assign the HSDir
614 flag to relay without a DirPort; this was bad because such relays
615 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
616 on tor-0.2.6.3-alpha.
618 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
619 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
620 a client authorized hidden service. Fixes bug 15823; bugfix
623 o Minor features (geoip):
624 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
625 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
629 Changes in version 0.2.7.1-alpha - 2015-05-12
630 Tor 0.2.7.1-alpha is the first alpha release in its series. It
631 includes numerous small features and bugfixes against previous Tor
632 versions, and numerous small infrastructure improvements. The most
633 notable features are several new ways for controllers to interact with
634 the hidden services subsystem.
636 o New system requirements:
637 - Tor no longer includes workarounds to support Libevent versions
638 before 1.3e. Libevent 2.0 or later is recommended. Closes
641 o Major features (controller):
642 - Add the ADD_ONION and DEL_ONION commands that allow the creation
643 and management of hidden services via the controller. Closes
645 - New "GETINFO onions/current" and "GETINFO onions/detached"
646 commands to get information about hidden services created via the
647 controller. Part of ticket 6411.
648 - New HSFETCH command to launch a request for a hidden service
649 descriptor. Closes ticket 14847.
650 - New HSPOST command to upload a hidden service descriptor. Closes
651 ticket 3523. Patch by "DonnchaC".
653 o Major bugfixes (hidden services):
654 - Revert commit that made directory authorities assign the HSDir
655 flag to relay without a DirPort; this was bad because such relays
656 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
657 on tor-0.2.6.3-alpha.
659 o Minor features (clock-jump tolerance):
660 - Recover better when our clock jumps back many hours, like might
661 happen for Tails or Whonix users who start with a very wrong
662 hardware clock, use Tor to discover a more accurate time, and then
663 fix their clock. Resolves part of ticket 8766.
665 o Minor features (command-line interface):
666 - Make --hash-password imply --hush to prevent unnecessary noise.
667 Closes ticket 15542. Patch from "cypherpunks".
668 - Print a warning whenever we find a relative file path being used
669 as torrc option. Resolves issue 14018.
671 o Minor features (controller):
672 - Add DirAuthority lines for default directory authorities to the
673 output of the "GETINFO config/defaults" command if not already
674 present. Implements ticket 14840.
675 - Controllers can now use "GETINFO hs/client/desc/id/..." to
676 retrieve items from the client's hidden service descriptor cache.
678 - Implement a new controller command "GETINFO status/fresh-relay-
679 descs" to fetch a descriptor/extrainfo pair that was generated on
680 demand just for the controller's use. Implements ticket 14784.
682 o Minor features (DoS-resistance):
683 - Make it harder for attackers to overload hidden services with
684 introductions, by blocking multiple introduction requests on the
685 same circuit. Resolves ticket 15515.
687 o Minor features (geoip):
688 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
689 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
692 o Minor features (HS popularity countermeasure):
693 - To avoid leaking HS popularity, don't cycle the introduction point
694 when we've handled a fixed number of INTRODUCE2 cells but instead
695 cycle it when a random number of introductions is reached, thus
696 making it more difficult for an attacker to find out the amount of
697 clients that have used the introduction point for a specific HS.
700 o Minor features (logging):
701 - Include the Tor version in all LD_BUG log messages, since people
702 tend to cut and paste those into the bugtracker. Implements
705 o Minor features (pluggable transports):
706 - When launching managed pluggable transports on Linux systems,
707 attempt to have the kernel deliver a SIGTERM on tor exit if the
708 pluggable transport process is still running. Resolves
710 - When launching managed pluggable transports, setup a valid open
711 stdin in the child process that can be used to detect if tor has
712 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
713 can be used by implementations to detect this new behavior.
714 Resolves ticket 15435.
716 o Minor features (testing):
717 - Add a test to verify that the compiler does not eliminate our
718 memwipe() implementation. Closes ticket 15377.
719 - Add make rule `check-changes` to verify the format of changes
720 files. Closes ticket 15180.
721 - Add unit tests for control_event_is_interesting(). Add a compile-
722 time check that the number of events doesn't exceed the capacity
723 of control_event_t.event_mask. Closes ticket 15431, checks for
724 bugs similar to 13085. Patch by "teor".
725 - Command-line argument tests moved to Stem. Resolves ticket 14806.
726 - Integrate the ntor, backtrace, and zero-length keys tests into the
727 automake test suite. Closes ticket 15344.
728 - Remove assertions during builds to determine Tor's test coverage.
729 We don't want to trigger these even in assertions, so including
730 them artificially makes our branch coverage look worse than it is.
731 This patch provides the new test-stem-full and coverage-html-full
732 configure options. Implements ticket 15400.
734 o Minor bugfixes (build):
735 - Improve out-of-tree builds by making non-standard rules work and
736 clean up additional files and directories. Fixes bug 15053; bugfix
739 o Minor bugfixes (command-line interface):
740 - When "--quiet" is provided along with "--validate-config", do not
741 write anything to stdout on success. Fixes bug 14994; bugfix
743 - When complaining about bad arguments to "--dump-config", use
746 o Minor bugfixes (configuration, unit tests):
747 - Only add the default fallback directories when the DirAuthorities,
748 AlternateDirAuthority, and FallbackDir directory config options
749 are set to their defaults. The default fallback directory list is
750 currently empty, this fix will only change tor's behavior when it
751 has default fallback directories. Includes unit tests for
752 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
753 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
755 o Minor bugfixes (correctness):
756 - For correctness, avoid modifying a constant string in
757 handle_control_postdescriptor. Fixes bug 15546; bugfix
759 - Remove side-effects from tor_assert() calls. This was harmless,
760 because we never disable assertions, but it is bad style and
761 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
764 o Minor bugfixes (hidden service):
765 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
766 a client authorized hidden service. Fixes bug 15823; bugfix
768 - Remove an extraneous newline character from the end of hidden
769 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
771 o Minor bugfixes (interface):
772 - Print usage information for --dump-config when it is used without
773 an argument. Also, fix the error message to use different wording
774 and add newline at the end. Fixes bug 15541; bugfix
777 o Minor bugfixes (logs):
778 - When building Tor under Clang, do not include an extra set of
779 parentheses in log messages that include function names. Fixes bug
780 15269; bugfix on every released version of Tor when compiled with
783 o Minor bugfixes (network):
784 - When attempting to use fallback technique for network interface
785 lookup, disregard loopback and multicast addresses since they are
786 unsuitable for public communications.
788 o Minor bugfixes (statistics):
789 - Disregard the ConnDirectionStatistics torrc options when Tor is
790 not a relay since in that mode of operation no sensible data is
791 being collected and because Tor might run into measurement hiccups
792 when running as a client for some time, then becoming a relay.
793 Fixes bug 15604; bugfix on 0.2.2.35.
795 o Minor bugfixes (test networks):
796 - When self-testing reachability, use ExtendAllowPrivateAddresses to
797 determine if local/private addresses imply reachability. The
798 previous fix used TestingTorNetwork, which implies
799 ExtendAllowPrivateAddresses, but this excluded rare configurations
800 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
801 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
802 issue discovered by CJ Ess.
804 o Minor bugfixes (testing):
805 - Check for matching value in server response in ntor_ref.py. Fixes
806 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
808 - Set the severity correctly when testing
809 get_interface_addresses_ifaddrs() and
810 get_interface_addresses_win32(), so that the tests fail gracefully
811 instead of triggering an assertion. Fixes bug 15759; bugfix on
812 0.2.6.3-alpha. Reported by Nicolas Derive.
814 o Code simplification and refactoring:
815 - Move the hacky fallback code out of get_interface_address6() into
816 separate function and get it covered with unit-tests. Resolves
818 - Refactor hidden service client-side cache lookup to intelligently
819 report its various failure cases, and disentangle failure cases
820 involving a lack of introduction points. Closes ticket 14391.
821 - Use our own Base64 encoder instead of OpenSSL's, to allow more
822 control over the output. Part of ticket 15652.
825 - Improve the descriptions of statistics-related torrc options in
826 the manpage to describe rationale and possible uses cases. Fixes
828 - Improve the layout and formatting of ./configure --help messages.
829 Closes ticket 15024. Patch from "cypherpunks".
830 - Standardize on the term "server descriptor" in the manual page.
831 Previously, we had used "router descriptor", "server descriptor",
832 and "relay descriptor" interchangeably. Part of ticket 14987.
835 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
836 and always use the internal Base64 decoder. The internal decoder
837 has been part of tor since tor-0.2.0.10-alpha, and no one should
838 be using the OpenSSL one. Part of ticket 15652.
839 - Remove the 'tor_strclear()' function; use memwipe() instead.
843 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
844 fingerprinting we now recommend pluggable transports; for forward-
845 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
846 - Remove the undocumented "--digests" command-line option. It
847 complicated our build process, caused subtle build issues on
848 multiple platforms, and is now redundant since we started
849 including git version identifiers. Closes ticket 14742.
850 - Tor no longer contains checks for ancient directory cache versions
851 that didn't know about microdescriptors.
852 - Tor no longer contains workarounds for stat files generated by
853 super-old versions of Tor that didn't choose guards sensibly.
856 Changes in version 0.2.4.27 - 2015-04-06
857 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
858 could be used by an attacker to crash hidden services, or crash clients
859 visiting hidden services. Hidden services should upgrade as soon as
860 possible; clients should upgrade whenever packages become available.
862 This release also backports a simple improvement to make hidden
863 services a bit less vulnerable to denial-of-service attacks.
865 o Major bugfixes (security, hidden service):
866 - Fix an issue that would allow a malicious client to trigger an
867 assertion failure and halt a hidden service. Fixes bug 15600;
868 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
869 - Fix a bug that could cause a client to crash with an assertion
870 failure when parsing a malformed hidden service descriptor. Fixes
871 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
873 o Minor features (DoS-resistance, hidden service):
874 - Introduction points no longer allow multiple INTRODUCE1 cells to
875 arrive on the same circuit. This should make it more expensive for
876 attackers to overwhelm hidden services with introductions.
877 Resolves ticket 15515.
880 Changes in version 0.2.6.7 - 2015-04-06
881 Tor 0.2.6.7 fixes two security issues that could be used by an
882 attacker to crash hidden services, or crash clients visiting hidden
883 services. Hidden services should upgrade as soon as possible; clients
884 should upgrade whenever packages become available.
886 This release also contains two simple improvements to make hidden
887 services a bit less vulnerable to denial-of-service attacks.
889 o Major bugfixes (security, hidden service):
890 - Fix an issue that would allow a malicious client to trigger an
891 assertion failure and halt a hidden service. Fixes bug 15600;
892 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
893 - Fix a bug that could cause a client to crash with an assertion
894 failure when parsing a malformed hidden service descriptor. Fixes
895 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
897 o Minor features (DoS-resistance, hidden service):
898 - Introduction points no longer allow multiple INTRODUCE1 cells to
899 arrive on the same circuit. This should make it more expensive for
900 attackers to overwhelm hidden services with introductions.
901 Resolves ticket 15515.
902 - Decrease the amount of reattempts that a hidden service performs
903 when its rendezvous circuits fail. This reduces the computational
904 cost for running a hidden service under heavy load. Resolves
908 Changes in version 0.2.6.6 - 2015-03-24
909 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
911 It adds numerous safety, security, correctness, and performance
912 improvements. Client programs can be configured to use more kinds of
913 sockets, AutomapHosts works better, the multithreading backend is
914 improved, cell transmission is refactored, test coverage is much
915 higher, more denial-of-service attacks are handled, guard selection is
916 improved to handle long-term guards better, pluggable transports
917 should work a bit better, and some annoying hidden service performance
918 bugs should be addressed.
920 o Minor bugfixes (portability):
921 - Use the correct datatype in the SipHash-2-4 function to prevent
922 compilers from assuming any sort of alignment. Fixes bug 15436;
923 bugfix on 0.2.5.3-alpha.
925 Changes in version 0.2.6.5-rc - 2015-03-18
926 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
927 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
929 o Major bugfixes (client):
930 - Avoid crashing when making certain configuration option changes on
931 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
934 o Major bugfixes (pluggable transports):
935 - Initialize the extended OR Port authentication cookie before
936 launching pluggable transports. This prevents a race condition
937 that occured when server-side pluggable transports would cache the
938 authentication cookie before it has been (re)generated. Fixes bug
939 15240; bugfix on 0.2.5.1-alpha.
941 o Major bugfixes (portability):
942 - Do not crash on startup when running on Solaris. Fixes a bug
943 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
946 o Minor features (heartbeat):
947 - On relays, report how many connections we negotiated using each
948 version of the Tor link protocols. This information will let us
949 know if removing support for very old versions of the Tor
950 protocols is harming the network. Closes ticket 15212.
952 o Code simplification and refactoring:
953 - Refactor main loop to extract the 'loop' part. This makes it
954 easier to run Tor under Shadow. Closes ticket 15176.
957 Changes in version 0.2.5.11 - 2015-03-17
958 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
960 It backports several bugfixes from the 0.2.6 branch, including a
961 couple of medium-level security fixes for relays and exit nodes.
962 It also updates the list of directory authorities.
964 o Directory authority changes:
965 - Remove turtles as a directory authority.
966 - Add longclaw as a new (v3) directory authority. This implements
967 ticket 13296. This keeps the directory authority count at 9.
968 - The directory authority Faravahar has a new IP address. This
971 o Major bugfixes (crash, OSX, security):
972 - Fix a remote denial-of-service opportunity caused by a bug in
973 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
976 o Major bugfixes (relay, stability, possible security):
977 - Fix a bug that could lead to a relay crashing with an assertion
978 failure if a buffer of exactly the wrong layout was passed to
979 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
980 0.2.0.10-alpha. Patch from 'cypherpunks'.
981 - Do not assert if the 'data' pointer on a buffer is advanced to the
982 very end of the buffer; log a BUG message instead. Only assert if
983 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
985 o Major bugfixes (exit node stability):
986 - Fix an assertion failure that could occur under high DNS load.
987 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
988 diagnosed and fixed by "cypherpunks".
990 o Major bugfixes (Linux seccomp2 sandbox):
991 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
992 crash during attempts to call wait4. Fixes bug 15088; bugfix on
993 0.2.5.1-alpha. Patch from "sanic".
995 o Minor features (controller):
996 - New "GETINFO bw-event-cache" to get information about recent
997 bandwidth events. Closes ticket 14128. Useful for controllers to
998 get recent bandwidth history after the fix for ticket 13988.
1000 o Minor features (geoip):
1001 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1002 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1005 o Minor bugfixes (client, automapping):
1006 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1007 no value follows the option. Fixes bug 14142; bugfix on
1008 0.2.4.7-alpha. Patch by "teor".
1009 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1010 14195; bugfix on 0.1.0.1-rc.
1012 o Minor bugfixes (compilation):
1013 - Build without warnings with the stock OpenSSL srtp.h header, which
1014 has a duplicate declaration of SSL_get_selected_srtp_profile().
1015 Fixes bug 14220; this is OpenSSL's bug, not ours.
1017 o Minor bugfixes (directory authority):
1018 - Allow directory authorities to fetch more data from one another if
1019 they find themselves missing lots of votes. Previously, they had
1020 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1021 bugfix on 0.1.2.5-alpha.
1022 - Enlarge the buffer to read bwauth generated files to avoid an
1023 issue when parsing the file in dirserv_read_measured_bandwidths().
1024 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1026 o Minor bugfixes (statistics):
1027 - Increase period over which bandwidth observations are aggregated
1028 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1030 o Minor bugfixes (preventative security, C safety):
1031 - When reading a hexadecimal, base-32, or base-64 encoded value from
1032 a string, always overwrite the whole output buffer. This prevents
1033 some bugs where we would look at (but fortunately, not reveal)
1034 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1038 Changes in version 0.2.4.26 - 2015-03-17
1039 Tor 0.2.4.26 includes an updated list of directory authorities. It
1040 also backports a couple of stability and security bugfixes from 0.2.5
1043 o Directory authority changes:
1044 - Remove turtles as a directory authority.
1045 - Add longclaw as a new (v3) directory authority. This implements
1046 ticket 13296. This keeps the directory authority count at 9.
1047 - The directory authority Faravahar has a new IP address. This
1048 closes ticket 14487.
1050 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
1051 - Fix an assertion failure that could occur under high DNS load.
1052 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1053 diagnosed and fixed by "cypherpunks".
1055 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
1056 - Fix a bug that could lead to a relay crashing with an assertion
1057 failure if a buffer of exactly the wrong layout was passed to
1058 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1059 0.2.0.10-alpha. Patch from 'cypherpunks'.
1060 - Do not assert if the 'data' pointer on a buffer is advanced to the
1061 very end of the buffer; log a BUG message instead. Only assert if
1062 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1064 o Minor features (geoip):
1065 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1066 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1069 Changes in version 0.2.6.4-rc - 2015-03-09
1070 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
1071 attacker might be able to use in order to crash certain Tor
1072 directories. It also resolves some minor issues left over from, or
1073 introduced in, Tor 0.2.6.3-alpha or earlier.
1075 o Major bugfixes (crash, OSX, security):
1076 - Fix a remote denial-of-service opportunity caused by a bug in
1077 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1080 o Major bugfixes (relay, stability, possible security):
1081 - Fix a bug that could lead to a relay crashing with an assertion
1082 failure if a buffer of exactly the wrong layout is passed to
1083 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1084 0.2.0.10-alpha. Patch from "cypherpunks".
1085 - Do not assert if the 'data' pointer on a buffer is advanced to the
1086 very end of the buffer; log a BUG message instead. Only assert if
1087 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1089 o Major bugfixes (FreeBSD IPFW transparent proxy):
1090 - Fix address detection with FreeBSD transparent proxies, when
1091 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
1094 o Major bugfixes (Linux seccomp2 sandbox):
1095 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
1096 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
1098 - Allow AF_UNIX hidden services to be used with the seccomp2
1099 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
1100 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1101 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1102 0.2.5.1-alpha. Patch from "sanic".
1104 o Minor features (controller):
1105 - Messages about problems in the bootstrap process now include
1106 information about the server we were trying to connect to when we
1107 noticed the problem. Closes ticket 15006.
1109 o Minor features (geoip):
1110 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1111 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1114 o Minor features (logs):
1115 - Quiet some log messages in the heartbeat and at startup. Closes
1118 o Minor bugfixes (certificate handling):
1119 - If an authority operator accidentally makes a signing certificate
1120 with a future publication time, do not discard its real signing
1121 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
1122 - Remove any old authority certificates that have been superseded
1123 for at least two days. Previously, we would keep superseded
1124 certificates until they expired, if they were published close in
1125 time to the certificate that superseded them. Fixes bug 11454;
1126 bugfix on 0.2.1.8-alpha.
1128 o Minor bugfixes (compilation):
1129 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
1131 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
1134 o Minor bugfixes (testing):
1135 - Fix endianness issues in unit test for resolve_my_address() to
1136 have it pass on big endian systems. Fixes bug 14980; bugfix on
1138 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
1139 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
1140 - When running the new 'make test-stem' target, use the configured
1141 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
1143 - When running the zero-length-keys tests, do not use the default
1144 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
1147 o Directory authority IP change:
1148 - The directory authority Faravahar has a new IP address. This
1149 closes ticket 14487.
1152 - Remove some lingering dead code that once supported mempools.
1153 Mempools were disabled by default in 0.2.5, and removed entirely
1154 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
1158 Changes in version 0.2.6.3-alpha - 2015-02-19
1159 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
1160 the 0.2.6.x series. It introduces support for more kinds of sockets,
1161 makes it harder to accidentally run an exit, improves our
1162 multithreading backend, incorporates several fixes for the
1163 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
1165 If no major regressions or security holes are found in this version,
1166 the next version will be a release candidate.
1168 o Deprecated versions:
1169 - Tor relays older than 0.2.4.18-rc are no longer allowed to
1170 advertise themselves on the network. Closes ticket 13555.
1172 o Major features (security, unix domain sockets):
1173 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
1174 applications can reach Tor without having to create AF_INET or
1175 AF_INET6 sockets, meaning they can completely disable their
1176 ability to make non-Tor network connections. To create a socket of
1177 this type, use "SocksPort unix:/path/to/socket". Implements
1179 - Support mapping hidden service virtual ports to AF_UNIX sockets.
1180 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
1181 Implements ticket 11485.
1183 o Major features (changed defaults):
1184 - Prevent relay operators from unintentionally running exits: When a
1185 relay is configured as an exit node, we now warn the user unless
1186 the "ExitRelay" option is set to 1. We warn even more loudly if
1187 the relay is configured with the default exit policy, since this
1188 can indicate accidental misconfiguration. Setting "ExitRelay 0"
1189 stops Tor from running as an exit relay. Closes ticket 10067.
1191 o Major features (directory system):
1192 - When downloading server- or microdescriptors from a directory
1193 server, we no longer launch multiple simultaneous requests to the
1194 same server. This reduces load on the directory servers,
1195 especially when directory guards are in use. Closes ticket 9969.
1196 - When downloading server- or microdescriptors over a tunneled
1197 connection, do not limit the length of our requests to what the
1198 Squid proxy is willing to handle. Part of ticket 9969.
1199 - Authorities can now vote on the correct digests and latest
1200 versions for different software packages. This allows packages
1201 that include Tor to use the Tor authority system as a way to get
1202 notified of updates and their correct digests. Implements proposal
1203 227. Closes ticket 10395.
1205 o Major features (guards):
1206 - Introduce the Guardfraction feature to improves load balancing on
1207 guard nodes. Specifically, it aims to reduce the traffic gap that
1208 guard nodes experience when they first get the Guard flag. This is
1209 a required step if we want to increase the guard lifetime to 9
1210 months or greater. Closes ticket 9321.
1212 o Major features (performance):
1213 - Make the CPU worker implementation more efficient by avoiding the
1214 kernel and lengthening pipelines. The original implementation used
1215 sockets to transfer data from the main thread to the workers, and
1216 didn't allow any thread to be assigned more than a single piece of
1217 work at once. The new implementation avoids communications
1218 overhead by making requests in shared memory, avoiding kernel IO
1219 where possible, and keeping more requests in flight at once.
1220 Implements ticket 9682.
1222 o Major features (relay):
1223 - Raise the minimum acceptable configured bandwidth rate for bridges
1224 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
1225 20 KiB/sec.) Closes ticket 13822.
1227 o Major bugfixes (exit node stability):
1228 - Fix an assertion failure that could occur under high DNS load.
1229 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1230 diagnosed and fixed by "cypherpunks".
1232 o Major bugfixes (mixed relay-client operation):
1233 - When running as a relay and client at the same time (not
1234 recommended), if we decide not to use a new guard because we want
1235 to retry older guards, only close the locally-originating circuits
1236 passing through that guard. Previously we would close all the
1237 circuits through that guard. Fixes bug 9819; bugfix on
1238 0.2.1.1-alpha. Reported by "skruffy".
1240 o Minor features (build):
1241 - New --disable-system-torrc compile-time option to prevent Tor from
1242 looking for the system-wide torrc or torrc-defaults files.
1243 Resolves ticket 13037.
1245 o Minor features (controller):
1246 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
1247 events so controllers can observe circuit isolation inputs. Closes
1249 - ControlPort now supports the unix:/path/to/socket syntax as an
1250 alternative to the ControlSocket option, for consistency with
1251 SocksPort and HiddenServicePort. Closes ticket 14451.
1252 - New "GETINFO bw-event-cache" to get information about recent
1253 bandwidth events. Closes ticket 14128. Useful for controllers to
1254 get recent bandwidth history after the fix for ticket 13988.
1256 o Minor features (Denial of service resistance):
1257 - Count the total number of bytes used storing hidden service
1258 descriptors against the value of MaxMemInQueues. If we're low on
1259 memory, and more than 20% of our memory is used holding hidden
1260 service descriptors, free them until no more than 10% of our
1261 memory holds hidden service descriptors. Free the least recently
1262 fetched descriptors first. Resolves ticket 13806.
1263 - When we have recently been under memory pressure (over 3/4 of
1264 MaxMemInQueues is allocated), then allocate smaller zlib objects
1265 for small requests. Closes ticket 11791.
1267 o Minor features (geoip):
1268 - Update geoip and geoip6 files to the January 7 2015 Maxmind
1269 GeoLite2 Country database.
1271 o Minor features (guard nodes):
1272 - Reduce the time delay before saving guard status to disk from 10
1273 minutes to 30 seconds (or from one hour to 10 minutes if
1274 AvoidDiskWrites is set). Closes ticket 12485.
1276 o Minor features (hidden service):
1277 - Make Sybil attacks against hidden services harder by changing the
1278 minimum time required to get the HSDir flag from 25 hours up to 96
1279 hours. Addresses ticket 14149.
1280 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
1281 services to disable the anti-scanning feature introduced in
1282 0.2.6.2-alpha. With this option not set, a connection to an
1283 unlisted port closes the circuit. With this option set, only a
1284 RELAY_DONE cell is sent. Closes ticket 14084.
1286 o Minor features (interface):
1287 - Implement "-f -" command-line option to read torrc configuration
1288 from standard input, if you don't want to store the torrc file in
1289 the file system. Implements feature 13865.
1291 o Minor features (logging):
1292 - Add a count of unique clients to the bridge heartbeat message.
1293 Resolves ticket 6852.
1294 - Suppress "router info incompatible with extra info" message when
1295 reading extrainfo documents from cache. (This message got loud
1296 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
1298 - Elevate hidden service authorized-client message from DEBUG to
1299 INFO. Closes ticket 14015.
1301 o Minor features (stability):
1302 - Add assertions in our hash-table iteration code to check for
1303 corrupted values that could cause infinite loops. Closes
1306 o Minor features (systemd):
1307 - Various improvements and modernizations in systemd hardening
1308 support. Closes ticket 13805. Patch from Craig Andrews.
1310 o Minor features (testing networks):
1311 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
1312 and the default on a testing network to 2 minutes. Drop the
1313 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
1314 keep the default on a testing network at 30 seconds. This reduces
1315 HS bootstrap time to around 25 seconds. Also, change the default
1316 time in test-network.sh to match. Closes ticket 13401. Patch
1318 - Create TestingDirAuthVoteHSDir to correspond to
1319 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
1320 HSDir flag for the listed relays regardless of uptime or ORPort
1321 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
1322 Partial implementation for ticket 14067. Patch by "teor".
1324 o Minor features (tor2web mode):
1325 - Introduce the config option Tor2webRendezvousPoints, which allows
1326 clients in Tor2webMode to select a specific Rendezvous Point to be
1327 used in HS circuits. This might allow better performance for
1328 Tor2Web nodes. Implements ticket 12844.
1330 o Minor bugfixes (client DNS):
1331 - Report the correct cached DNS expiration times on SOCKS port or in
1332 DNS replies. Previously, we would report everything as "never
1333 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
1334 - Avoid a small memory leak when we find a cached answer for a
1335 reverse DNS lookup in a client-side DNS cache. (Remember, client-
1336 side DNS caching is off by default, and is not recommended.) Fixes
1337 bug 14259; bugfix on 0.2.0.1-alpha.
1339 o Minor bugfixes (client, automapping):
1340 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1341 no value follows the option. Fixes bug 14142; bugfix on
1342 0.2.4.7-alpha. Patch by "teor".
1343 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1344 14195; bugfix on 0.1.0.1-rc.
1345 - Prevent changes to other options from removing the wildcard value
1346 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
1348 - Allow MapAddress and AutomapHostsOnResolve to work together when
1349 an address is mapped into another address type (like .onion) that
1350 must be automapped at resolve time. Fixes bug 7555; bugfix
1353 o Minor bugfixes (client, bridges):
1354 - When we are using bridges and we had a network connectivity
1355 problem, only retry connecting to our currently configured
1356 bridges, not all bridges we know about and remember using. Fixes
1357 bug 14216; bugfix on 0.2.2.17-alpha.
1359 o Minor bugfixes (client, IPv6):
1360 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
1361 flag is not set; and not because the NoIPv4Traffic flag was set.
1362 Previously we'd looked at the NoIPv4Traffic flag for both types of
1363 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
1365 o Minor bugfixes (compilation):
1366 - The address of an array in the middle of a structure will always
1367 be non-NULL. clang recognises this and complains. Disable the
1368 tautologous and redundant check to silence this warning. Fixes bug
1369 14001; bugfix on 0.2.1.2-alpha.
1370 - Avoid warnings when building with systemd 209 or later. Fixes bug
1371 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
1372 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
1373 Addresses ticket 14188.
1374 - Build without warnings with the stock OpenSSL srtp.h header, which
1375 has a duplicate declaration of SSL_get_selected_srtp_profile().
1376 Fixes bug 14220; this is OpenSSL's bug, not ours.
1377 - Do not compile any code related to Tor2Web mode when Tor2Web mode
1378 is not enabled at compile time. Previously, this code was included
1379 in a disabled state. See discussion on ticket 12844.
1380 - Remove the --disable-threads configure option again. It was
1381 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
1382 14819; bugfix on 0.2.6.2-alpha.
1384 o Minor bugfixes (controller):
1385 - Report "down" in response to the "GETINFO entry-guards" command
1386 when relays are down with an unreachable_since value. Previously,
1387 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
1388 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
1389 14116; bugfix on 0.2.2.9-alpha.
1390 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
1391 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
1393 o Minor bugfixes (directory authority):
1394 - Allow directory authorities to fetch more data from one another if
1395 they find themselves missing lots of votes. Previously, they had
1396 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1397 bugfix on 0.1.2.5-alpha.
1398 - Do not attempt to download extrainfo documents which we will be
1399 unable to validate with a matching server descriptor. Fixes bug
1400 13762; bugfix on 0.2.0.1-alpha.
1401 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
1402 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
1403 - Enlarge the buffer to read bwauth generated files to avoid an
1404 issue when parsing the file in dirserv_read_measured_bandwidths().
1405 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1407 o Minor bugfixes (file handling):
1408 - Stop failing when key files are zero-length. Instead, generate new
1409 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
1410 on all versions of Tor. Patch by "teor".
1411 - Stop generating a fresh .old RSA onion key file when the .old file
1412 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
1413 - Avoid overwriting .old key files with empty key files.
1414 - Skip loading zero-length extrainfo store, router store, stats,
1415 state, and key files.
1416 - Avoid crashing when trying to reload a torrc specified as a
1417 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
1420 o Minor bugfixes (hidden services):
1421 - Close the introduction circuit when we have no more usable intro
1422 points, instead of waiting for it to time out. This also ensures
1423 that no follow-up HS descriptor fetch is triggered when the
1424 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
1425 - When fetching a hidden service descriptor for a down service that
1426 was recently up, do not keep refetching until we try the same
1427 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
1428 - Successfully launch Tor with a nonexistent hidden service
1429 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
1430 14106; bugfix on 0.2.6.2-alpha.
1432 o Minor bugfixes (logging):
1433 - Avoid crashing when there are more log domains than entries in
1434 domain_list. Bugfix on 0.2.3.1-alpha.
1435 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
1437 - Don't log messages to stdout twice when starting up. Fixes bug
1438 13993; bugfix on 0.2.6.1-alpha.
1440 o Minor bugfixes (parsing):
1441 - Stop accepting milliseconds (or other junk) at the end of
1442 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
1443 - Support two-number and three-number version numbers correctly, in
1444 case we change the Tor versioning system in the future. Fixes bug
1445 13661; bugfix on 0.0.8pre1.
1447 o Minor bugfixes (path counting):
1448 - When deciding whether the consensus lists any exit nodes, count
1449 the number listed in the consensus, not the number we have
1450 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
1451 - When deciding whether we have any exit nodes, only examine
1452 ExitNodes when the ExitNodes option is actually set. Fixes part of
1453 bug 14918; bugfix on 0.2.6.2-alpha.
1454 - Get rid of redundant and possibly scary warnings that we are
1455 missing directory information while we bootstrap. Fixes part of
1456 bug 14918; bugfix on 0.2.6.2-alpha.
1458 o Minor bugfixes (portability):
1459 - Fix the ioctl()-based network interface lookup code so that it
1460 will work on systems that have variable-length struct ifreq, for
1462 - Fix scheduler compilation on targets where char is unsigned. Fixes
1463 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
1465 o Minor bugfixes (sandbox):
1466 - Allow glibc fatal errors to be sent to stderr before Tor exits.
1467 Previously, glibc would try to write them to /dev/tty, and the
1468 sandbox would trap the call and make Tor exit prematurely. Fixes
1469 bug 14759; bugfix on 0.2.5.1-alpha.
1471 o Minor bugfixes (shutdown):
1472 - When shutting down, always call event_del() on lingering read or
1473 write events before freeing them. Otherwise, we risk double-frees
1474 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
1477 o Minor bugfixes (small memory leaks):
1478 - Avoid leaking memory when using IPv6 virtual address mappings.
1479 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
1482 o Minor bugfixes (statistics):
1483 - Increase period over which bandwidth observations are aggregated
1484 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1486 o Minor bugfixes (systemd support):
1487 - Fix detection and operation of systemd watchdog. Fixes part of bug
1488 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
1489 - Run correctly under systemd with the RunAsDaemon option set. Fixes
1490 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
1491 - Inform the systemd supervisor about more changes in the Tor
1492 process status. Implements part of ticket 14141. Patch from
1494 - Cause the "--disable-systemd" option to actually disable systemd
1495 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
1498 o Minor bugfixes (TLS):
1499 - Check more thoroughly throughout the TLS code for possible
1500 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
1502 o Minor bugfixes (transparent proxy):
1503 - Use getsockname, not getsockopt, to retrieve the address for a
1504 TPROXY-redirected connection. Fixes bug 13796; bugfix
1507 o Code simplification and refactoring:
1508 - Move fields related to isolating and configuring client ports into
1509 a shared structure. Previously, they were duplicated across
1510 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
1511 to copy them correctly had been the cause of at least one bug in
1512 the past. Closes ticket 8546.
1513 - Refactor the get_interface_addresses_raw() doom-function into
1514 multiple smaller and simpler subfunctions. Cover the resulting
1515 subfunctions with unit-tests. Fixes a significant portion of
1517 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
1518 only for version <= 0.2.2.24 which is now deprecated. Closes
1520 - Remove a test for a long-defunct broken version-one
1524 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
1525 for writing the OpenBSD-specific tips. Resolves ticket 13702.
1526 - Make the tor-resolve documentation match its help string and its
1527 options. Resolves part of ticket 14325.
1528 - Log a more useful error message from tor-resolve when failing to
1529 look up a hidden service address. Resolves part of ticket 14325.
1531 o Downgraded warnings:
1532 - Don't warn when we've attempted to contact a relay using the wrong
1533 ntor onion key. Closes ticket 9635.
1536 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
1537 longer silently accepted as an alias for "ExitNodes".
1538 - The --enable-mempool and --enable-buf-freelists options, which
1539 were originally created to work around bad malloc implementations,
1540 no longer exist. They were off-by-default in 0.2.5. Closes
1544 - Make the checkdir/perms test complete successfully even if the
1545 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
1546 - Test that tor does not fail when key files are zero-length. Check
1547 that tor generates new keys, and overwrites the empty key files.
1548 - Test that tor generates new keys when keys are missing
1549 (existing behavior).
1550 - Test that tor does not overwrite key files that already contain
1551 data (existing behavior). Tests bug 13111. Patch by "teor".
1552 - New "make test-stem" target to run stem integration tests.
1553 Requires that the "STEM_SOURCE_DIR" environment variable be set.
1554 Closes ticket 14107.
1555 - Make the test_cmdline_args.py script work correctly on Windows.
1556 Patch from Gisle Vanem.
1557 - Move the slower unit tests into a new "./src/test/test-slow"
1558 binary that can be run independently of the other tests. Closes
1560 - Avoid undefined behavior when sampling huge values from the
1561 Laplace distribution. This made unittests fail on Raspberry Pi.
1562 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
1565 Changes in version 0.2.6.2-alpha - 2014-12-31
1566 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
1567 It introduces a major new backend for deciding when to send cells on
1568 channels, which should lead down the road to big performance
1569 increases. It contains security and statistics features for better
1570 work on hidden services, and numerous bugfixes.
1572 This release contains many new unit tests, along with major
1573 performance improvements for running testing networks using Chutney.
1574 Thanks to a series of patches contributed by "teor", testing networks
1575 should now bootstrap in seconds, rather than minutes.
1577 o Major features (relay, infrastructure):
1578 - Complete revision of the code that relays use to decide which cell
1579 to send next. Formerly, we selected the best circuit to write on
1580 each channel, but we didn't select among channels in any
1581 sophisticated way. Now, we choose the best circuits globally from
1582 among those whose channels are ready to deliver traffic.
1584 This patch implements a new inter-cmux comparison API, a global
1585 high/low watermark mechanism and a global scheduler loop for
1586 transmission prioritization across all channels as well as among
1587 circuits on one channel. This schedule is currently tuned to
1588 (tolerantly) avoid making changes in network performance, but it
1589 should form the basis for major circuit performance increases in
1590 the future. Code by Andrea; tuning by Rob Jansen; implements
1593 o Major features (hidden services):
1594 - Make HS port scanning more difficult by immediately closing the
1595 circuit when a user attempts to connect to a nonexistent port.
1596 Closes ticket 13667.
1597 - Add a HiddenServiceStatistics option that allows Tor relays to
1598 gather and publish statistics about the overall size and volume of
1599 hidden service usage. Specifically, when this option is turned on,
1600 an HSDir will publish an approximate number of hidden services
1601 that have published descriptors to it the past 24 hours. Also, if
1602 a relay has acted as a hidden service rendezvous point, it will
1603 publish the approximate amount of rendezvous cells it has relayed
1604 the past 24 hours. The statistics themselves are obfuscated so
1605 that the exact values cannot be derived. For more details see
1606 proposal 238, "Better hidden service stats from Tor relays". This
1607 feature is currently disabled by default. Implements feature 13192.
1609 o Major bugfixes (client, automap):
1610 - Repair automapping with IPv6 addresses. This automapping should
1611 have worked previously, but one piece of debugging code that we
1612 inserted to detect a regression actually caused the regression to
1613 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
1614 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
1617 o Major bugfixes (hidden services):
1618 - When closing an introduction circuit that was opened in parallel
1619 with others, don't mark the introduction point as unreachable.
1620 Previously, the first successful connection to an introduction
1621 point would make the other introduction points get marked as
1622 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
1624 o Directory authority changes:
1625 - Remove turtles as a directory authority.
1626 - Add longclaw as a new (v3) directory authority. This implements
1627 ticket 13296. This keeps the directory authority count at 9.
1629 o Major removed features:
1630 - Tor clients no longer support connecting to hidden services
1631 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
1632 option has been removed. (There shouldn't be any hidden services
1633 running these versions on the network.) Closes ticket 7803.
1635 o Minor features (client):
1636 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
1637 is enabled, reject requests with IP addresses as hostnames.
1638 Resolves ticket 13315.
1640 o Minor features (controller):
1641 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
1642 write an unscheduled heartbeat message to the log. Implements
1645 o Minor features (geoip):
1646 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
1649 o Minor features (hidden services):
1650 - When re-enabling the network, don't try to build introduction
1651 circuits until we have successfully built a circuit. This makes
1652 hidden services come up faster when the network is re-enabled.
1653 Patch from "akwizgran". Closes ticket 13447.
1654 - When we fail to retrieve a hidden service descriptor, send the
1655 controller an "HS_DESC FAILED" controller event. Implements
1657 - New HiddenServiceDirGroupReadable option to cause hidden service
1658 directories and hostname files to be created group-readable. Patch
1659 from "anon", David Stainton, and "meejah". Closes ticket 11291.
1661 o Minor features (systemd):
1662 - Where supported, when running with systemd, report successful
1663 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
1664 - When running with systemd, support systemd watchdog messages. Part
1665 of ticket 11016. Patch by Michael Scherer.
1667 o Minor features (transparent proxy):
1668 - Update the transparent proxy option checks to allow for both ipfw
1669 and pf on OS X. Closes ticket 14002.
1670 - Use the correct option when using IPv6 with transparent proxy
1671 support on Linux. Resolves 13808. Patch by Francisco Blas
1674 o Minor bugfixes (preventative security, C safety):
1675 - When reading a hexadecimal, base-32, or base-64 encoded value from
1676 a string, always overwrite the whole output buffer. This prevents
1677 some bugs where we would look at (but fortunately, not reveal)
1678 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1680 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
1681 just the part that's used. This makes it harder for data leak bugs
1682 to occur in the event of other programming failures. Resolves
1685 o Minor bugfixes (client, microdescriptors):
1686 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
1687 computing which microdescriptors to download. This keeps us from
1688 erroneous download behavior if two microdescriptor digests ever
1689 have the same first 160 bits. Fixes part of bug 13399; bugfix
1691 - Reset a router's status if its microdescriptor digest changes,
1692 even if the first 160 bits remain the same. Fixes part of bug
1693 13399; bugfix on 0.2.3.1-alpha.
1695 o Minor bugfixes (compilation):
1696 - Silence clang warnings under --enable-expensive-hardening,
1697 including implicit truncation of 64 bit values to 32 bit, const
1698 char assignment to self, tautological compare, and additional
1699 parentheses around equality tests. Fixes bug 13577; bugfix
1701 - Fix a clang warning about checking whether an address in the
1702 middle of a structure is NULL. Fixes bug 14001; bugfix
1705 o Minor bugfixes (hidden services):
1706 - Correctly send a controller event when we find that a rendezvous
1707 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
1708 - Pre-check directory permissions for new hidden-services to avoid
1709 at least one case of "Bug: Acting on config options left us in a
1710 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
1711 - When adding a new hidden service (for example, via SETCONF), Tor
1712 no longer congratulates the user for running a relay. Fixes bug
1713 13941; bugfix on 0.2.6.1-alpha.
1714 - When fetching hidden service descriptors, we now check not only
1715 for whether we got the hidden service we had in mind, but also
1716 whether we got the particular descriptors we wanted. This prevents
1717 a class of inefficient but annoying DoS attacks by hidden service
1718 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
1721 o Minor bugfixes (Linux seccomp2 sandbox):
1722 - Make transparent proxy support work along with the seccomp2
1723 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
1724 by Francisco Blas Izquierdo Riera.
1725 - Fix a memory leak in tor-resolve when running with the sandbox
1726 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
1728 o Minor bugfixes (logging):
1729 - Downgrade warnings about RSA signature failures to info log level.
1730 Emit a warning when an extra info document is found incompatible
1731 with a corresponding router descriptor. Fixes bug 9812; bugfix
1733 - Make connection_ap_handshake_attach_circuit() log the circuit ID
1734 correctly. Fixes bug 13701; bugfix on 0.0.6.
1736 o Minor bugfixes (misc):
1737 - Stop allowing invalid address patterns like "*/24" that contain
1738 both a wildcard address and a bit prefix length. This affects all
1739 our address-range parsing code. Fixes bug 7484; bugfix
1742 o Minor bugfixes (testing networks, fast startup):
1743 - Allow Tor to build circuits using a consensus with no exits. If
1744 the consensus has no exits (typical of a bootstrapping test
1745 network), allow Tor to build circuits once enough descriptors have
1746 been downloaded. This assists in bootstrapping a testing Tor
1747 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
1749 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
1750 header to directory servers. This allows us to obtain consensuses
1751 promptly when the consensus interval is very short. This assists
1752 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
1753 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
1754 - Stop assuming that private addresses are local when checking
1755 reachability in a TestingTorNetwork. Instead, when testing, assume
1756 all OR connections are remote. (This is necessary due to many test
1757 scenarios running all relays on localhost.) This assists in
1758 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
1759 0.1.0.1-rc. Patch by "teor".
1760 - Avoid building exit circuits from a consensus with no exits. Now
1761 thanks to our fix for 13718, we accept a no-exit network as not
1762 wholly lost, but we need to remember not to try to build exit
1763 circuits on it. Closes ticket 13814; patch by "teor".
1764 - Stop requiring exits to have non-zero bandwithcapacity in a
1765 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
1766 ignore exit bandwidthcapacity. This assists in bootstrapping a
1767 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
1768 on 0.2.0.3-alpha. Patch by "teor".
1769 - Add "internal" to some bootstrap statuses when no exits are
1770 available. If the consensus does not contain Exits, Tor will only
1771 build internal circuits. In this case, relevant statuses will
1772 contain the word "internal" as indicated in the Tor control-
1773 spec.txt. When bootstrap completes, Tor will be ready to build
1774 internal circuits. If a future consensus contains Exits, exit
1775 circuits may become available. Fixes part of bug 13718; bugfix on
1776 0.2.4.10-alpha. Patch by "teor".
1777 - Decrease minimum consensus interval to 10 seconds when
1778 TestingTorNetwork is set, or 5 seconds for the first consensus.
1779 Fix assumptions throughout the code that assume larger intervals.
1780 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
1782 - Avoid excluding guards from path building in minimal test
1783 networks, when we're in a test network and excluding guards would
1784 exclude all relays. This typically occurs in incredibly small tor
1785 networks, and those using "TestingAuthVoteGuard *". Fixes part of
1786 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
1788 o Code simplification and refactoring:
1789 - Stop using can_complete_circuits as a global variable; access it
1790 with a function instead.
1791 - Avoid using operators directly as macro arguments: this lets us
1792 apply coccinelle transformations to our codebase more directly.
1793 Closes ticket 13172.
1794 - Combine the functions used to parse ClientTransportPlugin and
1795 ServerTransportPlugin into a single function. Closes ticket 6456.
1796 - Add inline functions and convenience macros for inspecting channel
1797 state. Refactor the code to use convenience macros instead of
1798 checking channel state directly. Fixes issue 7356.
1799 - Document all members of was_router_added_t and rename
1800 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
1801 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
1802 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
1803 constant instead of hardcoded value. Fixes issue 13840.
1804 - Refactor our generic strmap and digestmap types into a single
1805 implementation, so that we can add a new digest256map
1809 - Document the bridge-authority-only 'networkstatus-bridges' file.
1810 Closes ticket 13713; patch from "tom".
1811 - Fix typo in PredictedPortsRelevanceTime option description in
1812 manpage. Resolves issue 13707.
1813 - Stop suggesting that users specify relays by nickname: it isn't a
1814 good idea. Also, properly cross-reference how to specify relays in
1815 all parts of manual documenting options that take a list of
1816 relays. Closes ticket 13381.
1817 - Clarify the HiddenServiceDir option description in manpage to make
1818 it clear that relative paths are taken with respect to the current
1819 working directory. Also clarify that this behavior is not
1820 guaranteed to remain indefinitely. Fixes issue 13913.
1823 - New tests for many parts of channel, relay, and circuitmux
1824 functionality. Code by Andrea; part of 9262.
1825 - New tests for parse_transport_line(). Part of ticket 6456.
1826 - In the unit tests, use chgrp() to change the group of the unit
1827 test temporary directory to the current user, so that the sticky
1828 bit doesn't interfere with tests that check directory groups.
1830 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1834 Changes in version 0.2.6.1-alpha - 2014-10-30
1835 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
1836 includes numerous code cleanups and new tests, and fixes a large
1837 number of annoying bugs. Out-of-memory conditions are handled better
1838 than in 0.2.5, pluggable transports have improved proxy support, and
1839 clients now use optimistic data for contacting hidden services. Also,
1840 we are now more robust to changes in what we consider a parseable
1841 directory object, so that tightening restrictions does not have a risk
1842 of introducing infinite download loops.
1844 This is the first alpha release in a new series, so expect there to be
1845 bugs. Users who would rather test out a more stable branch should stay
1846 with 0.2.5.x for now.
1848 o New compiler and system requirements:
1849 - Tor 0.2.6.x requires that your compiler support more of the C99
1850 language standard than before. The 'configure' script now detects
1851 whether your compiler supports C99 mid-block declarations and
1852 designated initializers. If it does not, Tor will not compile.
1854 We may revisit this requirement if it turns out that a significant
1855 number of people need to build Tor with compilers that don't
1856 bother implementing a 15-year-old standard. Closes ticket 13233.
1857 - Tor no longer supports systems without threading support. When we
1858 began working on Tor, there were several systems that didn't have
1859 threads, or where the thread support wasn't able to run the
1860 threads of a single process on multiple CPUs. That no longer
1861 holds: every system where Tor needs to run well now has threading
1862 support. Resolves ticket 12439.
1864 o Removed platform support:
1865 - We no longer include special code to build on Windows CE; as far
1866 as we know, nobody has used Tor on Windows CE in a very long time.
1867 Closes ticket 11446.
1869 o Major features (bridges):
1870 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
1871 transports if they are configured via the "TOR_PT_PROXY"
1872 environment variable. Implements proposal 232. Resolves
1875 o Major features (client performance, hidden services):
1876 - Allow clients to use optimistic data when connecting to a hidden
1877 service, which should remove a round-trip from hidden service
1878 initialization. See proposal 181 for details. Implements
1881 o Major features (directory system):
1882 - Upon receiving an unparseable directory object, if its digest
1883 matches what we expected, then don't try to download it again.
1884 Previously, when we got a descriptor we didn't like, we would keep
1885 trying to download it over and over. Closes ticket 11243.
1887 o Major features (sample torrc):
1888 - Add a new, infrequently-changed "torrc.minimal". This file is
1889 similar to torrc.sample, but it will change as infrequently as
1890 possible, for the benefit of users whose systems prompt them for
1891 intervention whenever a default configuration file is changed.
1892 Making this change allows us to update torrc.sample to be a more
1893 generally useful "sample torrc".
1895 o Major bugfixes (directory authorities):
1896 - Do not assign the HSDir flag to relays if they are not Valid, or
1897 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
1899 o Major bugfixes (directory bandwidth performance):
1900 - Don't flush the zlib buffer aggressively when compressing
1901 directory information for clients. This should save about 7% of
1902 the bandwidth currently used for compressed descriptors and
1903 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
1905 o Minor features (security, memory wiping):
1906 - Ensure we securely wipe keys from memory after
1907 crypto_digest_get_digest and init_curve25519_keypair_from_file
1908 have finished using them. Resolves ticket 13477.
1910 o Minor features (security, out-of-memory handling):
1911 - When handling an out-of-memory condition, allocate less memory for
1912 temporary data structures. Fixes issue 10115.
1913 - When handling an out-of-memory condition, consider more types of
1914 buffers, including those on directory connections, and zlib
1915 buffers. Resolves ticket 11792.
1918 - When identity keypair is generated for first time, log a
1919 congratulatory message that links to the new relay lifecycle
1920 document. Implements feature 10427.
1922 o Minor features (client):
1923 - Clients are now willing to send optimistic data (before they
1924 receive a 'connected' cell) to relays of any version. (Relays
1925 without support for optimistic data are no longer supported on the
1926 Tor network.) Resolves ticket 13153.
1928 o Minor features (directory authorities):
1929 - Don't list relays with a bandwidth estimate of 0 in the consensus.
1930 Implements a feature proposed during discussion of bug 13000.
1931 - In tor-gencert, report an error if the user provides the same
1932 argument more than once.
1933 - If a directory authority can't find a best consensus method in the
1934 votes that it holds, it now falls back to its favorite consensus
1935 method. Previously, it fell back to method 1. Neither of these is
1936 likely to get enough signatures, but "fall back to favorite"
1937 doesn't require us to maintain support an obsolete consensus
1938 method. Implements part of proposal 215.
1940 o Minor features (logging):
1941 - On Unix-like systems, you can now use named pipes as the target of
1942 the Log option, and other options that try to append to files.
1943 Closes ticket 12061. Patch from "carlo von lynX".
1944 - When opening a log file at startup, send it every log message that
1945 we generated between startup and opening it. Previously, log
1946 messages that were generated before opening the log file were only
1947 logged to stdout. Closes ticket 6938.
1948 - Add a TruncateLogFile option to overwrite logs instead of
1949 appending to them. Closes ticket 5583.
1951 o Minor features (portability, Solaris):
1952 - Threads are no longer disabled by default on Solaris; we believe
1953 that the versions of Solaris with broken threading support are all
1954 obsolete by now. Resolves ticket 9495.
1956 o Minor features (relay):
1957 - Re-check our address after we detect a changed IP address from
1958 getsockname(). This ensures that the controller command "GETINFO
1959 address" will report the correct value. Resolves ticket 11582.
1961 - A new AccountingRule option lets Relays set whether they'd like
1962 AccountingMax to be applied separately to inbound and outbound
1963 traffic, or applied to the sum of inbound and outbound traffic.
1964 Resolves ticket 961. Patch by "chobe".
1966 o Minor features (testing networks):
1967 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
1968 the "Exit" flag regardless of their uptime, bandwidth, or exit
1969 policy. TestingTorNetwork must be set for this option to have any
1970 effect. Previously, authorities would take up to 35 minutes to
1971 give nodes the Exit flag in a test network. Partially implements
1974 o Minor features (validation):
1975 - Check all date/time values passed to tor_timegm and
1976 parse_rfc1123_time for validity, taking leap years into account.
1977 Improves HTTP header validation. Implemented with bug 13476.
1978 - In correct_tm(), limit the range of values returned by system
1979 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
1980 This means we don't have to deal with negative or too large dates,
1981 even if a clock is wrong. Otherwise we might fail to read a file
1982 written by us which includes such a date. Fixes bug 13476.
1984 o Minor bugfixes (bridge clients):
1985 - When configured to use a bridge without an identity digest (not
1986 recommended), avoid launching an extra channel to it when
1987 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
1989 o Minor bugfixes (bridges):
1990 - When DisableNetwork is set, do not launch pluggable transport
1991 plugins, and if any are running, terminate them. Fixes bug 13213;
1992 bugfix on 0.2.3.6-alpha.
1994 o Minor bugfixes (C correctness):
1995 - Fix several instances of possible integer overflow/underflow/NaN.
1996 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
1998 - In circuit_build_times_calculate_timeout() in circuitstats.c,
1999 avoid dividing by zero in the pareto calculations. This traps
2000 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
2002 - Fix an integer overflow in format_time_interval(). Fixes bug
2003 13393; bugfix on 0.2.0.10-alpha.
2004 - Set the correct day of year value when the system's localtime(_r)
2005 or gmtime(_r) functions fail to set struct tm. Not externally
2006 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
2007 - Avoid unlikely signed integer overflow in tor_timegm on systems
2008 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
2010 o Minor bugfixes (client):
2011 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
2012 BadExit flag are not considered worthy candidates. Fixes bug
2013 13066; bugfix on 0.1.2.3-alpha.
2014 - Use the consensus schedule for downloading consensuses, and not
2015 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
2016 - Handle unsupported or malformed SOCKS5 requests properly by
2017 responding with the appropriate error message before closing the
2018 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
2020 o Minor bugfixes (client, torrc):
2021 - Stop modifying the value of our DirReqStatistics torrc option just
2022 because we're not a bridge or relay. This bug was causing Tor
2023 Browser users to write "DirReqStatistics 0" in their torrc files
2024 as if they had chosen to change the config. Fixes bug 4244; bugfix
2026 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
2027 that our options have changed every time we SIGHUP. Fixes bug
2028 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
2030 o Minor bugfixes (controller):
2031 - Return an error when the second or later arguments of the
2032 "setevents" controller command are invalid events. Previously we
2033 would return success while silently skipping invalid events. Fixes
2034 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
2036 o Minor bugfixes (directory system):
2037 - Always believe that v3 directory authorities serve extra-info
2038 documents, whether they advertise "caches-extra-info" or not.
2039 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2040 - When running as a v3 directory authority, advertise that you serve
2041 extra-info documents so that clients who want them can find them
2042 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2043 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
2044 Previously, directories offering BRIDGE_DIRINFO and some other
2045 flag (i.e. microdescriptors or extrainfo) would be ignored when
2046 looking for bridges. Partially fixes bug 13163; bugfix
2049 o Minor bugfixes (networking):
2050 - Check for orconns and use connection_or_close_for_error() rather
2051 than connection_mark_for_close() directly in the getsockopt()
2052 failure case of connection_handle_write_impl(). Fixes bug 11302;
2053 bugfix on 0.2.4.4-alpha.
2055 o Minor bugfixes (relay):
2056 - When generating our family list, remove spaces from around the
2057 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
2058 - If our previous bandwidth estimate was 0 bytes, allow publishing a
2059 new relay descriptor immediately. Fixes bug 13000; bugfix
2062 o Minor bugfixes (testing networks):
2063 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
2064 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
2065 - Stop using the default authorities in networks which provide both
2066 AlternateDirAuthority and AlternateBridgeAuthority. Partially
2067 fixes bug 13163; bugfix on 0.2.0.13-alpha.
2069 o Minor bugfixes (testing):
2070 - Stop spawn test failures due to a race condition between the
2071 SIGCHLD handler updating the process status, and the test reading
2072 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
2074 o Minor bugfixes (testing, Windows):
2075 - Avoid passing an extra backslash when creating a temporary
2076 directory for running the unit tests on Windows. Fixes bug 12392;
2077 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
2079 o Minor bugfixes (windows):
2080 - Remove code to special-case handling of NTE_BAD_KEYSET when
2081 acquiring windows CryptoAPI context. This error can't actually
2082 occur for the parameters we're providing. Fixes bug 10816; bugfix
2085 o Minor bugfixes (zlib):
2086 - Avoid truncating a zlib stream when trying to finalize it with an
2087 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
2090 - Allow our configure script to build correctly with autoconf 2.62
2091 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
2092 - Improve the error message from ./configure to make it clear that
2093 when asciidoc has not been found, the user will have to either add
2094 --disable-asciidoc argument or install asciidoc. Resolves
2097 o Code simplification and refactoring:
2098 - Change the entry_is_live() function to take named bitfield
2099 elements instead of an unnamed list of booleans. Closes
2101 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
2102 Resolves ticket 12205.
2103 - Use calloc and reallocarray functions instead of multiply-
2104 then-malloc. This makes it less likely for us to fall victim to an
2105 integer overflow attack when allocating. Resolves ticket 12855.
2106 - Use the standard macro name SIZE_MAX, instead of our
2108 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
2109 functions which take them as arguments. Replace 0 with NO_DIRINFO
2110 in a function call for clarity. Seeks to prevent future issues
2112 - Avoid 4 null pointer errors under clang static analysis by using
2113 tor_assert() to prove that the pointers aren't null. Fixes
2115 - Rework the API of policies_parse_exit_policy() to use a bitmask to
2116 represent parsing options, instead of a confusing mess of
2117 booleans. Resolves ticket 8197.
2118 - Introduce a helper function to parse ExitPolicy in
2119 or_options_t structure.
2122 - Add a doc/TUNING document with tips for handling large numbers of
2123 TCP connections when running busy Tor relay. Update the warning
2124 message to point to this file when running out of sockets
2125 operating system is allowing to use simultaneously. Resolves
2129 - We no longer remind the user about configuration options that have
2130 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
2131 - Remove our old, non-weighted bandwidth-based node selection code.
2132 Previously, we used it as a fallback when we couldn't perform
2133 weighted bandwidth-based node selection. But that would only
2134 happen in the cases where we had no consensus, or when we had a
2135 consensus generated by buggy or ancient directory authorities. In
2136 either case, it's better to use the more modern, better maintained
2137 algorithm, with reasonable defaults for the weights. Closes
2139 - Remove the --disable-curve25519 configure option. Relays and
2140 clients now are required to support curve25519 and the
2142 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
2143 used to be deprecated synonyms for "StrictNodes", are now marked
2144 obsolete. Resolves ticket 12226.
2145 - Clients don't understand the BadDirectory flag in the consensus
2146 anymore, and ignore it.
2149 - Refactor the function that chooses guard nodes so that it can more
2150 easily be tested; write some tests for it.
2151 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
2152 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
2153 - Create unit tests for format_time_interval(). With bug 13393.
2154 - Add unit tests for tor_timegm signed overflow, tor_timegm and
2155 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
2156 tests (visible) fixes in bug 13476.
2157 - Add a "coverage-html" make target to generate HTML-visualized
2158 coverage results when building with --enable-coverage. (Requires
2159 lcov.) Patch from Kevin Murray.
2160 - Enable the backtrace handler (where supported) when running the
2162 - Revise all unit tests that used the legacy test_* macros to
2163 instead use the recommended tt_* macros. This patch was generated
2164 with coccinelle, to avoid manual errors. Closes ticket 13119.
2166 o Distribution (systemd):
2167 - systemd unit file: only allow tor to write to /var/lib/tor and
2168 /var/log/tor. The rest of the filesystem is accessible for reading
2169 only. Patch by intrigeri; resolves ticket 12751.
2170 - systemd unit file: ensure that the process and all its children
2171 can never gain new privileges. Patch by intrigeri; resolves
2173 - systemd unit file: set up /var/run/tor as writable for the Tor
2174 service. Patch by intrigeri; resolves ticket 13196.
2176 o Removed features (directory authorities):
2177 - Remove code that prevented authorities from listing Tor relays
2178 affected by CVE-2011-2769 as guards. These relays are already
2179 rejected altogether due to the minimum version requirement of
2180 0.2.3.16-alpha. Closes ticket 13152.
2181 - The "AuthDirRejectUnlisted" option no longer has any effect, as
2182 the fingerprints file (approved-routers) has been deprecated.
2183 - Directory authorities do not support being Naming dirauths anymore.
2184 The "NamingAuthoritativeDir" config option is now obsolete.
2185 - Directory authorities do not support giving out the BadDirectory
2187 - Directory authorities no longer advertise or support consensus
2188 methods 1 through 12 inclusive. These consensus methods were
2189 obsolete and/or insecure: maintaining the ability to support them
2190 served no good purpose. Implements part of proposal 215; closes
2193 o Testing (test-network.sh):
2194 - Stop using "echo -n", as some shells' built-in echo doesn't
2195 support "-n". Instead, use "/bin/echo -n". Partially fixes
2197 - Stop an apparent test-network hang when used with make -j2. Fixes
2199 - Add a --delay option to test-network.sh, which configures the
2200 delay before the chutney network tests for data transmission.
2201 Partially implements ticket 13161.
2204 Changes in version 0.2.5.10 - 2014-10-24
2205 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
2207 It adds several new security features, including improved
2208 denial-of-service resistance for relays, new compiler hardening
2209 options, and a system-call sandbox for hardened installations on Linux
2210 (requires seccomp2). The controller protocol has several new features,
2211 resolving IPv6 addresses should work better than before, and relays
2212 should be a little more CPU-efficient. We've added support for more
2213 OpenBSD and FreeBSD transparent proxy types. We've improved the build
2214 system and testing infrastructure to allow unit testing of more parts
2215 of the Tor codebase. Finally, we've addressed several nagging pluggable
2216 transport usability issues, and included numerous other small bugfixes
2217 and features mentioned below.
2219 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
2220 have accumulated many known flaws; everyone should upgrade.
2222 o Deprecated versions:
2223 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
2224 attention for some while.
2227 Changes in version 0.2.5.9-rc - 2014-10-20
2228 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
2229 series. It disables SSL3 in response to the recent "POODLE" attack
2230 (even though POODLE does not affect Tor). It also works around a crash
2231 bug caused by some operating systems' response to the "POODLE" attack
2232 (which does affect Tor). It also contains a few miscellaneous fixes.
2234 o Major security fixes:
2235 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2236 today support TLS 1.0 or later, so we can safely turn off support
2237 for this old (and insecure) protocol. Fixes bug 13426.
2239 o Major bugfixes (openssl bug workaround):
2240 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2241 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2242 13471. This is a workaround for an OpenSSL bug.
2245 - Disable the sandbox name resolver cache when running tor-resolve:
2246 tor-resolve doesn't use the sandbox code, and turning it on was
2247 breaking attempts to do tor-resolve on a non-default server on
2248 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
2250 o Compilation fixes:
2251 - Build and run correctly on systems like OpenBSD-current that have
2252 patched OpenSSL to remove get_cipher_by_char and/or its
2253 implementations. Fixes issue 13325.
2255 o Downgraded warnings:
2256 - Downgrade the severity of the 'unexpected sendme cell from client'
2257 from 'warn' to 'protocol warning'. Closes ticket 8093.
2260 Changes in version 0.2.4.25 - 2014-10-20
2261 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2262 (even though POODLE does not affect Tor). It also works around a crash
2263 bug caused by some operating systems' response to the "POODLE" attack
2264 (which does affect Tor).
2266 o Major security fixes (also in 0.2.5.9-rc):
2267 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2268 today support TLS 1.0 or later, so we can safely turn off support
2269 for this old (and insecure) protocol. Fixes bug 13426.
2271 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2272 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2273 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2274 13471. This is a workaround for an OpenSSL bug.
2277 Changes in version 0.2.5.8-rc - 2014-09-22
2278 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
2279 series. It fixes a bug that affects consistency and speed when
2280 connecting to hidden services, and it updates the location of one of
2281 the directory authorities.
2284 - Clients now send the correct address for their chosen rendezvous
2285 point when trying to access a hidden service. They used to send
2286 the wrong address, which would still work some of the time because
2287 they also sent the identity digest of the rendezvous point, and if
2288 the hidden service happened to try connecting to the rendezvous
2289 point from a relay that already had a connection open to it,
2290 the relay would reuse that connection. Now connections to hidden
2291 services should be more robust and faster. Also, this bug meant
2292 that clients were leaking to the hidden service whether they were
2293 on a little-endian (common) or big-endian (rare) system, which for
2294 some users might have reduced their anonymity. Fixes bug 13151;
2295 bugfix on 0.2.1.5-alpha.
2297 o Directory authority changes:
2298 - Change IP address for gabelmoo (v3 directory authority).
2301 Changes in version 0.2.4.24 - 2014-09-22
2302 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2303 connecting to hidden services, and it updates the location of one of
2304 the directory authorities.
2307 - Clients now send the correct address for their chosen rendezvous
2308 point when trying to access a hidden service. They used to send
2309 the wrong address, which would still work some of the time because
2310 they also sent the identity digest of the rendezvous point, and if
2311 the hidden service happened to try connecting to the rendezvous
2312 point from a relay that already had a connection open to it,
2313 the relay would reuse that connection. Now connections to hidden
2314 services should be more robust and faster. Also, this bug meant
2315 that clients were leaking to the hidden service whether they were
2316 on a little-endian (common) or big-endian (rare) system, which for
2317 some users might have reduced their anonymity. Fixes bug 13151;
2318 bugfix on 0.2.1.5-alpha.
2320 o Directory authority changes:
2321 - Change IP address for gabelmoo (v3 directory authority).
2323 o Minor features (geoip):
2324 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2328 Changes in version 0.2.5.7-rc - 2014-09-11
2329 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
2330 release series, and some long-standing bugs related to ORPort reachability
2331 testing and failure to send CREATE cells. It is the first release
2332 candidate for the Tor 0.2.5.x series.
2334 o Major bugfixes (client, startup):
2335 - Start making circuits as soon as DisabledNetwork is turned off.
2336 When Tor started with DisabledNetwork set, it would correctly
2337 conclude that it shouldn't build circuits, but it would mistakenly
2338 cache this conclusion, and continue believing it even when
2339 DisableNetwork is set to 0. Fixes the bug introduced by the fix
2340 for bug 11200; bugfix on 0.2.5.4-alpha.
2341 - Resume expanding abbreviations for command-line options. The fix
2342 for bug 4647 accidentally removed our hack from bug 586 that
2343 rewrote HashedControlPassword to __HashedControlSessionPassword
2344 when it appears on the commandline (which allowed the user to set
2345 her own HashedControlPassword in the torrc file while the
2346 controller generates a fresh session password for each run). Fixes
2347 bug 12948; bugfix on 0.2.5.1-alpha.
2348 - Warn about attempts to run hidden services and relays in the same
2349 process: that's probably not a good idea. Closes ticket 12908.
2351 o Major bugfixes (relay):
2352 - Avoid queuing or sending destroy cells for circuit ID zero when we
2353 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
2354 Found and fixed by "cypherpunks".
2355 - Fix ORPort reachability detection on relays running behind a
2356 proxy, by correctly updating the "local" mark on the controlling
2357 channel when changing the address of an or_connection_t after the
2358 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
2360 o Minor features (bridge):
2361 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
2362 cookie file for the ExtORPort g+r by default.
2364 o Minor features (geoip):
2365 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2368 o Minor bugfixes (logging):
2369 - Reduce the log severity of the "Pluggable transport proxy does not
2370 provide any needed transports and will not be launched." message,
2371 since Tor Browser includes several ClientTransportPlugin lines in
2372 its torrc-defaults file, leading every Tor Browser user who looks
2373 at her logs to see these notices and wonder if they're dangerous.
2374 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
2375 - Downgrade "Unexpected onionskin length after decryption" warning
2376 to a protocol-warn, since there's nothing relay operators can do
2377 about a client that sends them a malformed create cell. Resolves
2378 bug 12996; bugfix on 0.0.6rc1.
2379 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
2380 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
2381 - When logging information about an EXTEND2 or EXTENDED2 cell, log
2382 their names correctly. Fixes part of bug 12700; bugfix
2384 - When logging information about a relay cell whose command we don't
2385 recognize, log its command as an integer. Fixes part of bug 12700;
2386 bugfix on 0.2.1.10-alpha.
2387 - Escape all strings from the directory connection before logging
2388 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
2390 o Minor bugfixes (controller):
2391 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
2392 bug 12864; bugfix on 0.2.5.1-alpha.
2393 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
2394 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
2397 o Minor bugfixes (compilation):
2398 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
2399 bugfix on 0.2.5.5-alpha.
2400 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
2401 0.2.5.1-alpha. Patch from "NewEraCracker".
2402 - In routerlist_assert_ok(), don't take the address of a
2403 routerinfo's cache_info member unless that routerinfo is non-NULL.
2404 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
2405 - Fix a large number of false positive warnings from the clang
2406 analyzer static analysis tool. This should make real warnings
2407 easier for clang analyzer to find. Patch from "teor". Closes
2410 o Distribution (systemd):
2411 - Verify configuration file via ExecStartPre in the systemd unit
2412 file. Patch from intrigeri; resolves ticket 12730.
2413 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2414 current systemd unit uses "Type = simple", so systemd does not
2415 expect tor to fork. If the user has "RunAsDaemon 1" in their
2416 torrc, then things won't work as expected. This is e.g. the case
2417 on Debian (and derivatives), since there we pass "--defaults-torrc
2418 /usr/share/tor/tor-service-defaults-torrc" (that contains
2419 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2423 - Adjust the URLs in the README to refer to the new locations of
2424 several documents on the website. Fixes bug 12830. Patch from
2426 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
2430 Changes in version 0.2.5.6-alpha - 2014-07-28
2431 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
2432 risk from guard rotation, and fixes a variety of other issues to get
2433 us closer to a release candidate.
2435 o Major features (also in 0.2.4.23):
2436 - Make the number of entry guards configurable via a new
2437 NumEntryGuards consensus parameter, and the number of directory
2438 guards configurable via a new NumDirectoryGuards consensus
2439 parameter. Implements ticket 12688.
2441 o Major bugfixes (also in 0.2.4.23):
2442 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2443 implementation that caused incorrect results on 32-bit
2444 implementations when certain malformed inputs were used along with
2445 a small class of private ntor keys. This bug does not currently
2446 appear to allow an attacker to learn private keys or impersonate a
2447 Tor server, but it could provide a means to distinguish 32-bit Tor
2448 implementations from 64-bit Tor implementations. Fixes bug 12694;
2449 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2453 - Perform circuit cleanup operations even when circuit
2454 construction operations are disabled (because the network is
2455 disabled, or because there isn't enough directory information).
2456 Previously, when we were not building predictive circuits, we
2457 were not closing expired circuits either. Fixes bug 8387; bugfix on
2458 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
2459 became more strict about when we have "enough directory information
2463 - Authorities now assign the Guard flag to the fastest 25% of the
2464 network (it used to be the fastest 50%). Also raise the consensus
2465 weight that guarantees the Guard flag from 250 to 2000. For the
2466 current network, this results in about 1100 guards, down from 2500.
2467 This step paves the way for moving the number of entry guards
2468 down to 1 (proposal 236) while still providing reasonable expected
2469 performance for most users. Implements ticket 12690.
2470 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2472 - Slightly enhance the diagnostic message for bug 12184.
2474 o Minor bugfixes (also in 0.2.4.23):
2475 - Warn and drop the circuit if we receive an inbound 'relay early'
2476 cell. Those used to be normal to receive on hidden service circuits
2477 due to bug 1038, but the buggy Tor versions are long gone from
2478 the network so we can afford to resume watching for them. Resolves
2479 the rest of bug 1038; bugfix on 0.2.1.19.
2480 - Correct a confusing error message when trying to extend a circuit
2481 via the control protocol but we don't know a descriptor or
2482 microdescriptor for one of the specified relays. Fixes bug 12718;
2483 bugfix on 0.2.3.1-alpha.
2486 - Fix compilation when building with bufferevents enabled. (This
2487 configuration is still not expected to work, however.)
2488 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
2489 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
2491 - Compile correctly with builds and forks of OpenSSL (such as
2492 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
2493 0.2.1.1-alpha. Patch from "dhill".
2496 Changes in version 0.2.4.23 - 2014-07-28
2497 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
2498 guard rotation, and also backports several important fixes from the
2499 Tor 0.2.5 alpha release series.
2502 - Clients now look at the "usecreatefast" consensus parameter to
2503 decide whether to use CREATE_FAST or CREATE cells for the first hop
2504 of their circuit. This approach can improve security on connections
2505 where Tor's circuit handshake is stronger than the available TLS
2506 connection security levels, but the tradeoff is more computational
2507 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2508 - Make the number of entry guards configurable via a new
2509 NumEntryGuards consensus parameter, and the number of directory
2510 guards configurable via a new NumDirectoryGuards consensus
2511 parameter. Implements ticket 12688.
2514 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2515 implementation that caused incorrect results on 32-bit
2516 implementations when certain malformed inputs were used along with
2517 a small class of private ntor keys. This bug does not currently
2518 appear to allow an attacker to learn private keys or impersonate a
2519 Tor server, but it could provide a means to distinguish 32-bit Tor
2520 implementations from 64-bit Tor implementations. Fixes bug 12694;
2521 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2525 - Warn and drop the circuit if we receive an inbound 'relay early'
2526 cell. Those used to be normal to receive on hidden service circuits
2527 due to bug 1038, but the buggy Tor versions are long gone from
2528 the network so we can afford to resume watching for them. Resolves
2529 the rest of bug 1038; bugfix on 0.2.1.19.
2530 - Correct a confusing error message when trying to extend a circuit
2531 via the control protocol but we don't know a descriptor or
2532 microdescriptor for one of the specified relays. Fixes bug 12718;
2533 bugfix on 0.2.3.1-alpha.
2534 - Avoid an illegal read from stack when initializing the TLS
2535 module using a version of OpenSSL without all of the ciphers
2536 used by the v2 link handshake. Fixes bug 12227; bugfix on
2537 0.2.4.8-alpha. Found by "starlight".
2540 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2544 Changes in version 0.2.5.5-alpha - 2014-06-18
2545 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
2546 0.2.5.x release series, including a couple of DoS issues, some
2547 performance regressions, a large number of bugs affecting the Linux
2548 seccomp2 sandbox code, and various other bugfixes. It also adds
2549 diagnostic bugfixes for a few tricky issues that we're trying to
2552 o Major features (security, traffic analysis resistance):
2553 - Several major improvements to the algorithm used to decide when to
2554 close TLS connections. Previous versions of Tor closed connections
2555 at a fixed interval after the last time a non-padding cell was
2556 sent over the connection, regardless of the target of the
2557 connection. Now, we randomize the intervals by adding up to 50% of
2558 their base value, we measure the length of time since connection
2559 last had at least one circuit, and we allow connections to known
2560 ORs to remain open a little longer (15 minutes instead of 3
2561 minutes minimum). These changes should improve Tor's resistance
2562 against some kinds of traffic analysis, and lower some overhead
2563 from needlessly closed connections. Fixes ticket 6799.
2564 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
2566 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
2567 - Fix a memory leak that could occur if a microdescriptor parse
2568 fails during the tokenizing step. This bug could enable a memory
2569 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2572 o Major bugfixes (security, directory authorities):
2573 - Directory authorities now include a digest of each relay's
2574 identity key as a part of its microdescriptor.
2576 This is a workaround for bug 11743 (reported by "cypherpunks"),
2577 where Tor clients do not support receiving multiple
2578 microdescriptors with the same SHA256 digest in the same
2579 consensus. When clients receive a consensus like this, they only
2580 use one of the relays. Without this fix, a hostile relay could
2581 selectively disable some client use of target relays by
2582 constructing a router descriptor with a different identity and the
2583 same microdescriptor parameters and getting the authorities to
2584 list it in a microdescriptor consensus. This fix prevents an
2585 attacker from causing a microdescriptor collision, because the
2586 router's identity is not forgeable.
2588 o Major bugfixes (relay):
2589 - Use a direct dirport connection when uploading non-anonymous
2590 descriptors to the directory authorities. Previously, relays would
2591 incorrectly use tunnel connections under a fairly wide variety of
2592 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
2593 - When a circuit accidentally has the same circuit ID for its
2594 forward and reverse direction, correctly detect the direction of
2595 cells using that circuit. Previously, this bug made roughly one
2596 circuit in a million non-functional. Fixes bug 12195; this is a
2597 bugfix on every version of Tor.
2599 o Major bugfixes (client, pluggable transports):
2600 - When managing pluggable transports, use OS notification facilities
2601 to learn if they have crashed, and don't attempt to kill any
2602 process that has already exited. Fixes bug 8746; bugfix
2605 o Minor features (diagnostic):
2606 - When logging a warning because of bug 7164, additionally check the
2607 hash table for consistency (as proposed on ticket 11737). This may
2608 help diagnose bug 7164.
2609 - When we log a heartbeat, log how many one-hop circuits we have
2610 that are at least 30 minutes old, and log status information about
2611 a few of them. This is an attempt to track down bug 8387.
2612 - When encountering an unexpected CR while writing text to a file on
2613 Windows, log the name of the file. Should help diagnosing
2615 - Give more specific warnings when a client notices that an onion
2616 handshake has failed. Fixes ticket 9635.
2617 - Add significant new logging code to attempt to diagnose bug 12184,
2618 where relays seem to run out of available circuit IDs.
2619 - Improve the diagnostic log message for bug 8387 even further to
2620 try to improve our odds of figuring out why one-hop directory
2621 circuits sometimes do not get closed.
2623 o Minor features (security, memory management):
2624 - Memory allocation tricks (mempools and buffer freelists) are now
2625 disabled by default. You can turn them back on with
2626 --enable-mempools and --enable-buf-freelists respectively. We're
2627 disabling these features because malloc performance is good enough
2628 on most platforms, and a similar feature in OpenSSL exacerbated
2629 exploitation of the Heartbleed attack. Resolves ticket 11476.
2631 o Minor features (security):
2632 - Apply the secure SipHash-2-4 function to the hash table mapping
2633 circuit IDs and channels to circuits. We missed this one when we
2634 were converting all the other hash functions to use SipHash back
2635 in 0.2.5.3-alpha. Resolves ticket 11750.
2637 o Minor features (build):
2638 - The configure script has a --disable-seccomp option to turn off
2639 support for libseccomp on systems that have it, in case it (or
2640 Tor's use of it) is broken. Resolves ticket 11628.
2642 o Minor features (other):
2643 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
2646 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
2647 - When running a hidden service, do not allow TunneledDirConns 0;
2648 this will keep the hidden service from running, and also
2649 make it publish its descriptors directly over HTTP. Fixes bug 10849;
2650 bugfix on 0.2.1.1-alpha.
2652 o Minor bugfixes (performance):
2653 - Avoid a bug where every successful connection made us recompute
2654 the flag telling us whether we have sufficient information to
2655 build circuits. Previously, we would forget our cached value
2656 whenever we successfully opened a channel (or marked a router as
2657 running or not running for any other reason), regardless of
2658 whether we had previously believed the router to be running. This
2659 forced us to run an expensive update operation far too often.
2660 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
2661 - Avoid using tor_memeq() for checking relay cell integrity. This
2662 removes a possible performance bottleneck. Fixes part of bug
2663 12169; bugfix on 0.2.1.31.
2665 o Minor bugfixes (compilation):
2666 - Fix compilation of test_status.c when building with MVSC. Bugfix
2667 on 0.2.5.4-alpha. Patch from Gisle Vanem.
2668 - Resolve GCC complaints on OpenBSD about discarding constness in
2669 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
2670 on 0.1.1.23. Patch from Dana Koch.
2671 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
2672 treatment of long and time_t as comparable types. Fixes part of
2673 bug 11633. Patch from Dana Koch.
2674 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
2675 11623; bugfix on 0.2.5.3-alpha.
2676 - When deciding whether to build the 64-bit curve25519
2677 implementation, detect platforms where we can compile 128-bit
2678 arithmetic but cannot link it. Fixes bug 11729; bugfix on
2679 0.2.4.8-alpha. Patch from "conradev".
2680 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
2681 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
2682 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
2685 o Minor bugfixes (Directory server):
2686 - When sending a compressed set of descriptors or microdescriptors,
2687 make sure to finalize the zlib stream. Previously, we would write
2688 all the compressed data, but if the last descriptor we wanted to
2689 send was missing or too old, we would not mark the stream as
2690 finished. This caused problems for decompression tools. Fixes bug
2691 11648; bugfix on 0.1.1.23.
2693 o Minor bugfixes (Linux seccomp sandbox):
2694 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
2695 11622; bugfix on 0.2.5.1-alpha.
2696 - Avoid crashing when re-opening listener ports with the seccomp
2697 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
2698 - Avoid crashing with the seccomp sandbox enabled along with
2699 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
2700 - When we receive a SIGHUP with the sandbox enabled, correctly
2701 support rotating our log files. Fixes bug 12032; bugfix
2703 - Avoid crash when running with sandboxing enabled and
2704 DirReqStatistics not disabled. Fixes bug 12035; bugfix
2706 - Fix a "BUG" warning when trying to write bridge-stats files with
2707 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
2709 - Prevent the sandbox from crashing on startup when run with the
2710 --enable-expensive-hardening configuration option. Fixes bug
2711 11477; bugfix on 0.2.5.4-alpha.
2712 - When running with DirPortFrontPage and sandboxing both enabled,
2713 reload the DirPortFrontPage correctly when restarting. Fixes bug
2714 12028; bugfix on 0.2.5.1-alpha.
2715 - Don't try to enable the sandbox when using the Tor binary to check
2716 its configuration, hash a passphrase, or so on. Doing so was
2717 crashing on startup for some users. Fixes bug 11609; bugfix
2719 - Avoid warnings when running with sandboxing and node statistics
2720 enabled at the same time. Fixes part of 12064; bugfix on
2721 0.2.5.1-alpha. Patch from Michael Wolf.
2722 - Avoid warnings when running with sandboxing enabled at the same
2723 time as cookie authentication, hidden services, or directory
2724 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
2725 - Do not allow options that require calls to exec to be enabled
2726 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
2727 bug 12043; bugfix on 0.2.5.1-alpha.
2728 - Handle failures in getpwnam()/getpwuid() when running with the
2729 User option set and the Linux syscall sandbox enabled. Fixes bug
2730 11946; bugfix on 0.2.5.1-alpha.
2731 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
2732 to avoid calling getaddrinfo() after installing the sandbox
2733 filters. Previously, it preloaded a cache with the IPv4 address
2734 for our hostname, and nothing else. Now, it loads the cache with
2735 every address that it used to initialize the Tor process. Fixes
2736 bug 11970; bugfix on 0.2.5.1-alpha.
2738 o Minor bugfixes (pluggable transports):
2739 - Enable the ExtORPortCookieAuthFile option, to allow changing the
2740 default location of the authentication token for the extended OR
2741 Port as used by sever-side pluggable transports. We had
2742 implemented this option before, but the code to make it settable
2743 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
2744 - Avoid another 60-second delay when starting Tor in a pluggable-
2745 transport-using configuration when we already have cached
2746 descriptors for our bridges. Fixes bug 11965; bugfix
2749 o Minor bugfixes (client):
2750 - Avoid "Tried to open a socket with DisableNetwork set" warnings
2751 when starting a client with bridges configured and DisableNetwork
2752 set. (Tor launcher starts Tor with DisableNetwork set the first
2753 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
2755 o Minor bugfixes (testing):
2756 - The Python parts of the test scripts now work on Python 3 as well
2757 as Python 2, so systems where '/usr/bin/python' is Python 3 will
2758 no longer have the tests break. Fixes bug 11608; bugfix
2760 - When looking for versions of python that we could run the tests
2761 with, check for "python2.7" and "python3.3"; previously we were
2762 only looking for "python", "python2", and "python3". Patch from
2763 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
2764 - Fix all valgrind warnings produced by the unit tests. There were
2765 over a thousand memory leak warnings previously, mostly produced
2766 by forgetting to free things in the unit test code. Fixes bug
2767 11618, bugfixes on many versions of Tor.
2769 o Minor bugfixes (tor-fw-helper):
2770 - Give a correct log message when tor-fw-helper fails to launch.
2771 (Previously, we would say something like "tor-fw-helper sent us a
2772 string we could not parse".) Fixes bug 9781; bugfix
2775 o Minor bugfixes (relay, threading):
2776 - Check return code on spawn_func() in cpuworker code, so that we
2777 don't think we've spawned a nonworking cpuworker and write junk to
2778 it forever. Fix related to bug 4345; bugfix on all released Tor
2779 versions. Found by "skruffy".
2780 - Use a pthread_attr to make sure that spawn_func() cannot return an
2781 error while at the same time launching a thread. Fix related to
2782 bug 4345; bugfix on all released Tor versions. Reported
2785 o Minor bugfixes (relay, oom prevention):
2786 - Correctly detect the total available system memory. We tried to do
2787 this in 0.2.5.4-alpha, but the code was set up to always return an
2788 error value, even on success. Fixes bug 11805; bugfix
2791 o Minor bugfixes (relay, other):
2792 - We now drop CREATE cells for already-existent circuit IDs and for
2793 zero-valued circuit IDs, regardless of other factors that might
2794 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
2796 - Avoid an illegal read from stack when initializing the TLS module
2797 using a version of OpenSSL without all of the ciphers used by the
2798 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
2800 - When rejecting DATA cells for stream_id zero, still count them
2801 against the circuit's deliver window so that we don't fail to send
2802 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
2804 o Minor bugfixes (logging):
2805 - Fix a misformatted log message about delayed directory fetches.
2806 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
2807 - Squelch a spurious LD_BUG message "No origin circuit for
2808 successful SOCKS stream" in certain hidden service failure cases;
2812 - Include a tor.service file in contrib/dist for use with systemd.
2813 Some distributions will be able to use this file unmodified;
2814 others will need to tweak it, or write their own. Patch from Jamie
2815 Nguyen; resolves ticket 8368.
2818 - Clean up several option names in the manpage to match their real
2819 names, add the missing documentation for a couple of testing and
2820 directory authority options, remove the documentation for a
2821 V2-directory fetching option that no longer exists. Resolves
2823 - Correct the documenation so that it lists the correct directory
2824 for the stats files. (They are in a subdirectory called "stats",
2826 - In the manpage, move more authority-only options into the
2827 directory authority section so that operators of regular directory
2828 caches don't get confused.
2831 - The contrib directory has been sorted and tidied. Before, it was
2832 an unsorted dumping ground for useful and not-so-useful things.
2833 Now, it is divided based on functionality, and the items which
2834 seemed to be nonfunctional or useless have been removed. Resolves
2835 ticket 8966; based on patches from "rl1987".
2838 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2839 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
2840 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2841 exist; tunneled directory connections have been available since
2842 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2843 brute-force fix for 10849, where "TunnelDirConns 0" would break
2847 Changes in version 0.2.4.22 - 2014-05-16
2848 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
2849 alpha release series. These include blocking all authority signing
2850 keys that may have been affected by the OpenSSL "heartbleed" bug,
2851 choosing a far more secure set of TLS ciphersuites by default, closing
2852 a couple of memory leaks that could be used to run a target relay out
2853 of RAM, and several others.
2855 o Major features (security, backport from 0.2.5.4-alpha):
2856 - Block authority signing keys that were used on authorities
2857 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2858 don't have any evidence that these keys _were_ compromised; we're
2859 doing this to be prudent.) Resolves ticket 11464.
2861 o Major bugfixes (security, OOM):
2862 - Fix a memory leak that could occur if a microdescriptor parse
2863 fails during the tokenizing step. This bug could enable a memory
2864 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2867 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
2868 - The relay ciphersuite list is now generated automatically based on
2869 uniform criteria, and includes all OpenSSL ciphersuites with
2870 acceptable strength and forward secrecy. Previously, we had left
2871 some perfectly fine ciphersuites unsupported due to omission or
2872 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2873 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2874 - Relays now trust themselves to have a better view than clients of
2875 which TLS ciphersuites are better than others. (Thanks to bug
2876 11513, the relay list is now well-considered, whereas the client
2877 list has been chosen mainly for anti-fingerprinting purposes.)
2878 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2879 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2880 AES128. Resolves ticket 11528.
2881 - Clients now try to advertise the same list of ciphersuites as
2882 Firefox 28. This change enables selection of (fast) GCM
2883 ciphersuites, disables some strange old ciphers, and stops
2884 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2885 Resolves ticket 11438.
2887 o Minor bugfixes (configuration, security):
2888 - When running a hidden service, do not allow TunneledDirConns 0:
2889 trying to set that option together with a hidden service would
2890 otherwise prevent the hidden service from running, and also make
2891 it publish its descriptors directly over HTTP. Fixes bug 10849;
2892 bugfix on 0.2.1.1-alpha.
2894 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
2895 - Avoid sending a garbage value to the controller when a circuit is
2896 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2898 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
2899 - Stop leaking memory when we successfully resolve a PTR record.
2900 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2902 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
2903 - Avoid 60-second delays in the bootstrapping process when Tor is
2904 launching for a second time while using bridges. Fixes bug 9229;
2905 bugfix on 0.2.0.3-alpha.
2907 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
2908 - Give the correct URL in the warning message when trying to run a
2909 relay on an ancient version of Windows. Fixes bug 9393.
2911 o Minor bugfixes (compilation):
2912 - Fix a compilation error when compiling with --disable-curve25519.
2913 Fixes bug 9700; bugfix on 0.2.4.17-rc.
2916 - Downgrade the warning severity for the the "md was still
2917 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
2918 for trying to diagnose this bug, and the current warning in
2919 earlier versions of tor achieves nothing useful. Addresses warning
2922 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
2923 - When we run out of usable circuit IDs on a channel, log only one
2924 warning for the whole channel, and describe how many circuits
2925 there were on the channel. Fixes part of ticket 11553.
2927 o Minor features (security, backport from 0.2.5.4-alpha):
2928 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
2929 leave the default at 8GBytes), to better support Raspberry Pi
2930 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
2932 o Documentation (backport from 0.2.5.4-alpha):
2933 - Correctly document that we search for a system torrc file before
2934 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2938 Changes in version 0.2.5.4-alpha - 2014-04-25
2939 Tor 0.2.5.4-alpha includes several security and performance
2940 improvements for clients and relays, including blacklisting authority
2941 signing keys that were used while susceptible to the OpenSSL
2942 "heartbleed" bug, fixing two expensive functions on busy relays,
2943 improved TLS ciphersuite preference lists, support for run-time
2944 hardening on compilers that support AddressSanitizer, and more work on
2945 the Linux sandbox code.
2947 There are also several usability fixes for clients (especially clients
2948 that use bridges), two new TransPort protocols supported (one on
2949 OpenBSD, one on FreeBSD), and various other bugfixes.
2951 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
2952 have accumulated many known flaws; everyone should upgrade.
2954 o Major features (security):
2955 - If you don't specify MaxMemInQueues yourself, Tor now tries to
2956 pick a good value based on your total system memory. Previously,
2957 the default was always 8 GB. You can still override the default by
2958 setting MaxMemInQueues yourself. Resolves ticket 11396.
2959 - Block authority signing keys that were used on authorities
2960 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2961 don't have any evidence that these keys _were_ compromised; we're
2962 doing this to be prudent.) Resolves ticket 11464.
2964 o Major features (relay performance):
2965 - Speed up server-side lookups of rendezvous and introduction point
2966 circuits by using hashtables instead of linear searches. These
2967 functions previously accounted between 3 and 7% of CPU usage on
2968 some busy relays. Resolves ticket 9841.
2969 - Avoid wasting CPU when extending a circuit over a channel that is
2970 nearly out of circuit IDs. Previously, we would do a linear scan
2971 over possible circuit IDs before finding one or deciding that we
2972 had exhausted our possibilities. Now, we try at most 64 random
2973 circuit IDs before deciding that we probably won't succeed. Fixes
2974 a possible root cause of ticket 11553.
2976 o Major features (seccomp2 sandbox, Linux only):
2977 - The seccomp2 sandbox can now run a test network for multiple hours
2978 without crashing. The sandbox is still experimental, and more bugs
2979 will probably turn up. To try it, enable "Sandbox 1" on a Linux
2980 host. Resolves ticket 11351.
2981 - Strengthen sandbox code: the sandbox can now test the arguments
2982 for rename(), and blocks _sysctl() entirely. Resolves another part
2984 - When the sandbox blocks a system call, it now tries to log a stack
2985 trace before exiting. Resolves ticket 11465.
2987 o Major bugfixes (TLS cipher selection):
2988 - The relay ciphersuite list is now generated automatically based on
2989 uniform criteria, and includes all OpenSSL ciphersuites with
2990 acceptable strength and forward secrecy. Previously, we had left
2991 some perfectly fine ciphersuites unsupported due to omission or
2992 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2993 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2994 - Relays now trust themselves to have a better view than clients of
2995 which TLS ciphersuites are better than others. (Thanks to bug
2996 11513, the relay list is now well-considered, whereas the client
2997 list has been chosen mainly for anti-fingerprinting purposes.)
2998 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2999 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3000 AES128. Resolves ticket 11528.
3001 - Clients now try to advertise the same list of ciphersuites as
3002 Firefox 28. This change enables selection of (fast) GCM
3003 ciphersuites, disables some strange old ciphers, and stops
3004 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3005 Resolves ticket 11438.
3007 o Major bugfixes (bridge client):
3008 - Avoid 60-second delays in the bootstrapping process when Tor is
3009 launching for a second time while using bridges. Fixes bug 9229;
3010 bugfix on 0.2.0.3-alpha.
3012 o Minor features (transparent proxy, *BSD):
3013 - Support FreeBSD's ipfw firewall interface for TransPort ports on
3014 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
3015 10267; patch from "yurivict".
3016 - Support OpenBSD's divert-to rules with the pf firewall for
3017 transparent proxy ports. To enable it, set "TransProxyType
3018 pf-divert". This allows Tor to run a TransPort transparent proxy
3019 port on OpenBSD 4.4 or later without root privileges. See the
3020 pf.conf(5) manual page for information on configuring pf to use
3021 divert-to rules. Closes ticket 10896; patch from Dana Koch.
3023 o Minor features (security):
3024 - New --enable-expensive-hardening option to enable security
3025 hardening options that consume nontrivial amounts of CPU and
3026 memory. Right now, this includes AddressSanitizer and UbSan, which
3027 are supported in newer versions of GCC and Clang. Closes ticket
3030 o Minor features (log verbosity):
3031 - Demote the message that we give when a flushing connection times
3032 out for too long from NOTICE to INFO. It was usually meaningless.
3033 Resolves ticket 5286.
3034 - Don't log so many notice-level bootstrapping messages at startup
3035 about downloading descriptors. Previously, we'd log a notice
3036 whenever we learned about more routers. Now, we only log a notice
3037 at every 5% of progress. Fixes bug 9963.
3038 - Warn less verbosely when receiving a malformed
3039 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
3040 - When we run out of usable circuit IDs on a channel, log only one
3041 warning for the whole channel, and describe how many circuits
3042 there were on the channel. Fixes part of ticket 11553.
3044 o Minor features (relay):
3045 - If a circuit timed out for at least 3 minutes, check if we have a
3046 new external IP address, and publish a new descriptor with the new
3047 IP address if it changed. Resolves ticket 2454.
3049 o Minor features (controller):
3050 - Make the entire exit policy available from the control port via
3051 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
3053 - Because of the fix for ticket 11396, the real limit for memory
3054 usage may no longer match the configured MaxMemInQueues value. The
3055 real limit is now exposed via GETINFO limits/max-mem-in-queues.
3057 o Minor features (bridge client):
3058 - Report a more useful failure message when we can't connect to a
3059 bridge because we don't have the right pluggable transport
3060 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
3062 o Minor features (diagnostic):
3063 - Add more log messages to diagnose bug 7164, which causes
3064 intermittent "microdesc_free() called but md was still referenced"
3065 warnings. We now include more information, to figure out why we
3066 might be cleaning a microdescriptor for being too old if it's
3067 still referenced by a live node_t object.
3069 o Minor bugfixes (client, DNSPort):
3070 - When using DNSPort, try to respond to AAAA requests with AAAA
3071 answers. Previously, we hadn't looked at the request type when
3072 deciding which answer type to prefer. Fixes bug 10468; bugfix on
3074 - When receiving a DNS query for an unsupported record type, reply
3075 with no answer rather than with a NOTIMPL error. This behavior
3076 isn't correct either, but it will break fewer client programs, we
3077 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
3080 o Minor bugfixes (exit relay):
3081 - Stop leaking memory when we successfully resolve a PTR record.
3082 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3084 o Minor bugfixes (bridge client):
3085 - Stop accepting bridge lines containing hostnames. Doing so would
3086 cause clients to perform DNS requests on the hostnames, which was
3087 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
3088 - Avoid a 60-second delay in the bootstrapping process when a Tor
3089 client with pluggable transports re-reads its configuration at
3090 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
3092 o Minor bugfixes (client, logging during bootstrap):
3093 - Warn only once if we start logging in an unsafe way. Previously,
3094 we complain as many times as we had problems. Fixes bug 9870;
3095 bugfix on 0.2.5.1-alpha.
3096 - Only report the first fatal bootstrap error on a given OR
3097 connection. This stops us from telling the controller bogus error
3098 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
3099 - Be more helpful when trying to run sandboxed on Linux without
3100 libseccomp. Instead of saying "Sandbox is not implemented on this
3101 platform", we now explain that we need to be built with
3102 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
3103 - Avoid generating spurious warnings when starting with
3104 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
3107 o Minor bugfixes (closing OR connections):
3108 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
3109 check if it's an or_connection_t and correctly call
3110 connection_or_close_for_error() rather than
3111 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
3113 - When closing all connections on setting DisableNetwork to 1, use
3114 connection_or_close_normally() rather than closing OR connections
3115 out from under the channel layer. Fixes bug 11306; bugfix on
3118 o Minor bugfixes (controller):
3119 - Avoid sending a garbage value to the controller when a circuit is
3120 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3122 o Minor bugfixes (tor-fw-helper):
3123 - Allow tor-fw-helper to build again by adding src/ext to its
3124 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
3126 o Minor bugfixes (bridges):
3127 - Avoid potential crashes or bad behavior when launching a
3128 server-side managed proxy with ORPort or ExtORPort temporarily
3129 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
3131 o Minor bugfixes (platform-specific):
3132 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
3133 bug 11426; bugfix on 0.2.5.3-alpha.
3134 - When dumping a malformed directory object to disk, save it in
3135 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
3137 - Don't report failures from make_socket_reuseable() on incoming
3138 sockets on OSX: this can happen when incoming connections close
3139 early. Fixes bug 10081.
3141 o Minor bugfixes (trivial memory leaks):
3142 - Fix a small memory leak when signing a directory object. Fixes bug
3143 11275; bugfix on 0.2.4.13-alpha.
3144 - Free placeholder entries in our circuit table at exit; fixes a
3145 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
3146 - Don't re-initialize a second set of OpenSSL mutexes when starting
3147 up. Previously, we'd make one set of mutexes, and then immediately
3148 replace them with another. Fixes bug 11726; bugfix on
3150 - Resolve some memory leaks found by coverity in the unit tests, on
3151 exit in tor-gencert, and on a failure to compute digests for our
3152 own keys when generating a v3 networkstatus vote. These leaks
3153 should never have affected anyone in practice.
3155 o Minor bugfixes (hidden service):
3156 - Only retry attempts to connect to a chosen rendezvous point 8
3157 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
3159 o Minor bugfixes (misc code correctness):
3160 - Fix various instances of undefined behavior in channeltls.c,
3161 tor_memmem(), and eventdns.c that would cause us to construct
3162 pointers to memory outside an allocated object. (These invalid
3163 pointers were not accessed, but C does not even allow them to
3164 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
3165 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
3166 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
3167 fix some miscellaneous errors in our tests and codebase. Fixes bug
3168 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
3169 - Always check return values for unlink, munmap, UnmapViewOfFile;
3170 check strftime return values more often. In some cases all we can
3171 do is report a warning, but this may help prevent deeper bugs from
3172 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
3174 - Fix numerous warnings from the clang "scan-build" static analyzer.
3175 Some of these are programming style issues; some of them are false
3176 positives that indicated awkward code; some are undefined behavior
3177 cases related to constructing (but not using) invalid pointers;
3178 some are assumptions about API behavior; some are (harmlessly)
3179 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
3180 correct; and one or two are genuine bugs that weren't reachable
3181 from the rest of the program. Fixes bug 8793; bugfixes on many,
3185 - Build the torify.1 manpage again. Previously, we were only trying
3186 to build it when also building tor-fw-helper. That's why we didn't
3187 notice that we'd broken the ability to build it. Fixes bug 11321;
3188 bugfix on 0.2.5.1-alpha.
3189 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
3190 11061; bugfix on 0.2.4.7-alpha.
3191 - Correctly document that we search for a system torrc file before
3192 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3194 - Resolve warnings from Doxygen.
3196 o Code simplifications and refactoring:
3197 - Remove is_internal_IP() function. Resolves ticket 4645.
3198 - Remove unused function circuit_dump_by_chan from circuitlist.c.
3199 Closes issue 9107; patch from "marek".
3200 - Change our use of the ENUM_BF macro to avoid declarations that
3203 o Deprecated versions:
3204 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
3205 attention for some while. Directory authorities no longer accept
3206 descriptors from relays running any version of Tor prior to Tor
3207 0.2.3.16-alpha. Resolves ticket 11149.
3210 - New macros in test.h to simplify writing mock-functions for unit
3211 tests. Part of ticket 11507. Patch from Dana Koch.
3212 - Complete tests for the status.c module. Resolves ticket 11507.
3213 Patch from Dana Koch.
3216 - Remove all code for the long unused v1 directory protocol.
3217 Resolves ticket 11070.
3220 Changes in version 0.2.5.3-alpha - 2014-03-22
3221 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
3222 two new anti-DoS features for Tor relays, resolves a bug that kept
3223 SOCKS5 support for IPv6 from working, fixes several annoying usability
3224 issues for bridge users, and removes more old code for unused
3227 The Tor 0.2.5.x release series is now in patch-freeze: no feature
3228 patches not already written will be considered for inclusion in 0.2.5.x.
3230 o Major features (relay security, DoS-resistance):
3231 - When deciding whether we have run out of memory and we need to
3232 close circuits, also consider memory allocated in buffers for
3233 streams attached to each circuit.
3235 This change, which extends an anti-DoS feature introduced in
3236 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
3237 better resist more memory-based DoS attacks than before. Since the
3238 MaxMemInCellQueues option now applies to all queues, it is renamed
3239 to MaxMemInQueues. This feature fixes bug 10169.
3240 - Avoid hash-flooding denial-of-service attacks by using the secure
3241 SipHash-2-4 hash function for our hashtables. Without this
3242 feature, an attacker could degrade performance of a targeted
3243 client or server by flooding their data structures with a large
3244 number of entries to be stored at the same hash table position,
3245 thereby slowing down the Tor instance. With this feature, hash
3246 table positions are derived from a randomized cryptographic key,
3247 and an attacker cannot predict which entries will collide. Closes
3249 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
3250 the default at 8GBytes), to better support Raspberry Pi users. Fixes
3251 bug 9686; bugfix on 0.2.4.14-alpha.
3253 o Minor features (bridges, pluggable transports):
3254 - Bridges now write the SHA1 digest of their identity key
3255 fingerprint (that is, a hash of a hash of their public key) to
3256 notice-level logs, and to a new hashed-fingerprint file. This
3257 information will help bridge operators look up their bridge in
3258 Globe and similar tools. Resolves ticket 10884.
3259 - Improve the message that Tor displays when running as a bridge
3260 using pluggable transports without an Extended ORPort listener.
3261 Also, log the message in the log file too. Resolves ticket 11043.
3263 o Minor features (other):
3264 - Add a new option, PredictedPortsRelevanceTime, to control how long
3265 after having received a request to connect to a given port Tor
3266 will try to keep circuits ready in anticipation of future requests
3267 for that port. Patch from "unixninja92"; implements ticket 9176.
3268 - Generate a warning if any ports are listed in the SocksPolicy,
3269 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
3270 AuthDirBadExit options. (These options only support address
3271 ranges.) Fixes part of ticket 11108.
3272 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
3275 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
3276 - Build without warnings under clang 3.4. (We have some macros that
3277 define static functions only some of which will get used later in
3278 the module. Starting with clang 3.4, these give a warning unless the
3279 unused attribute is set on them.) Resolves ticket 10904.
3280 - Fix build warnings about missing "a2x" comment when building the
3281 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3282 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3284 o Minor bugfixes (client):
3285 - Improve the log message when we can't connect to a hidden service
3286 because all of the hidden service directory nodes hosting its
3287 descriptor are excluded. Improves on our fix for bug 10722, which
3288 was a bugfix on 0.2.0.10-alpha.
3289 - Raise a control port warning when we fail to connect to all of
3290 our bridges. Previously, we didn't inform the controller, and
3291 the bootstrap process would stall. Fixes bug 11069; bugfix on
3293 - Exit immediately when a process-owning controller exits.
3294 Previously, tor relays would wait for a little while after their
3295 controller exited, as if they had gotten an INT signal -- but this
3296 was problematic, since there was no feedback for the user. To do a
3297 clean shutdown, controllers should send an INT signal and give Tor
3298 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
3299 - Stop attempting to connect to bridges before our pluggable
3300 transports are configured (harmless but resulted in some erroneous
3301 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
3302 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
3303 generating incorrect SOCKS5 responses, and confusing client
3304 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
3306 o Minor bugfixes (relays and bridges):
3307 - Avoid crashing on a malformed resolv.conf file when running a
3308 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
3309 - Non-exit relays no longer launch mock DNS requests to check for
3310 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
3311 non-exit relays stopped servicing DNS requests. Fixes bug 965;
3312 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
3313 - Bridges now report complete directory request statistics. Related
3314 to bug 5824; bugfix on 0.2.2.1-alpha.
3315 - Bridges now never collect statistics that were designed for
3316 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
3317 - Stop giving annoying warning messages when we decide not to launch
3318 a pluggable transport proxy that we don't need (because there are
3319 no bridges configured to use it). Resolves ticket 5018; bugfix
3321 - Give the correct URL in the warning message when trying to run a
3322 relay on an ancient version of Windows. Fixes bug 9393.
3324 o Minor bugfixes (backtrace support):
3325 - Support automatic backtraces on more platforms by using the
3326 "-fasynchronous-unwind-tables" compiler option. This option is
3327 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
3328 is on by default and table generation is not. This doesn't yet
3329 add Windows support; only Linux, OSX, and some BSDs are affected.
3330 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
3331 - Avoid strange behavior if two threads hit failed assertions at the
3332 same time and both try to log backtraces at once. (Previously, if
3333 this had happened, both threads would have stored their intermediate
3334 results in the same buffer, and generated junk outputs.) Reported by
3335 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
3336 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
3337 0.2.5.2-alpha; patch from Nick Hopper.
3339 o Minor bugfixes (unit tests):
3340 - Fix a small bug in the unit tests that might have made the tests
3341 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
3342 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
3345 - Remove all remaining code related to version-0 hidden service
3346 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
3347 the rest of bug 10841.
3350 - Document in the manpage that "KBytes" may also be written as
3351 "kilobytes" or "KB", that "Kbits" may also be written as
3352 "kilobits", and so forth. Closes ticket 9222.
3353 - Document that the ClientOnly config option overrides ORPort.
3354 Our old explanation made ClientOnly sound as though it did
3355 nothing at all. Resolves bug 9059.
3356 - Explain that SocksPolicy, DirPolicy, and similar options don't
3357 take port arguments. Fixes the other part of ticket 11108.
3358 - Fix a comment about the rend_server_descriptor_t.protocols field
3359 to more accurately describe its range. Also, make that field
3360 unsigned, to more accurately reflect its usage. Fixes bug 9099;
3361 bugfix on 0.2.1.5-alpha.
3362 - Fix the manpage's description of HiddenServiceAuthorizeClient:
3363 the maximum client name length is 16, not 19. Fixes bug 11118;
3364 bugfix on 0.2.1.6-alpha.
3366 o Code simplifications and refactoring:
3367 - Get rid of router->address, since in all cases it was just the
3368 string representation of router->addr. Resolves ticket 5528.
3370 o Test infrastructure:
3371 - Update to the latest version of tinytest.
3372 - Improve the tinytest implementation of string operation tests so
3373 that comparisons with NULL strings no longer crash the tests; they
3374 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
3377 Changes in version 0.2.4.21 - 2014-02-28
3378 Tor 0.2.4.21 further improves security against potential adversaries who
3379 find breaking 1024-bit crypto doable, and backports several stability
3380 and robustness patches from the 0.2.5 branch.
3382 o Major features (client security):
3383 - When we choose a path for a 3-hop circuit, make sure it contains
3384 at least one relay that supports the NTor circuit extension
3385 handshake. Otherwise, there is a chance that we're building
3386 a circuit that's worth attacking by an adversary who finds
3387 breaking 1024-bit crypto doable, and that chance changes the game
3388 theory. Implements ticket 9777.
3391 - Do not treat streams that fail with reason
3392 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3393 since it could also indicate an ENETUNREACH connection error. Fixes
3394 part of bug 10777; bugfix on 0.2.4.8-alpha.
3396 o Code simplification and refactoring:
3397 - Remove data structures which were introduced to implement the
3398 CellStatistics option: they are now redundant with the new timestamp
3399 field in the regular packed_cell_t data structure, which we did
3400 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
3403 - Always clear OpenSSL bignums before freeing them -- even bignums
3404 that don't contain secrets. Resolves ticket 10793. Patch by
3406 - Build without warnings under clang 3.4. (We have some macros that
3407 define static functions only some of which will get used later in
3408 the module. Starting with clang 3.4, these give a warning unless the
3409 unused attribute is set on them.) Resolves ticket 10904.
3410 - Update geoip and geoip6 files to the February 7 2014 Maxmind
3411 GeoLite2 Country database.
3414 - Set the listen() backlog limit to the largest actually supported
3415 on the system, not to the value in a header file. Fixes bug 9716;
3416 bugfix on every released Tor.
3417 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3418 exit node as a NOROUTE error, not an INTERNAL error, since they
3419 can apparently happen when trying to connect to the wrong sort
3420 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3421 - Fix build warnings about missing "a2x" comment when building the
3422 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3423 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3424 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3425 not entirely remove it from the connection lists. Fixes bug 9602;
3426 bugfix on 0.2.4.4-alpha.
3427 - Fix a segmentation fault in our benchmark code when running with
3428 Fedora's OpenSSL package, or any other OpenSSL that provides
3429 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3430 - Turn "circuit handshake stats since last time" log messages into a
3431 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3433 o Documentation fixes:
3434 - Document that all but one DirPort entry must have the NoAdvertise
3435 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3438 Changes in version 0.2.5.2-alpha - 2014-02-13
3439 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
3440 like the "poor random number generation" fix and the "building too many
3441 circuits" fix. It also further improves security against potential
3442 adversaries who find breaking 1024-bit crypto doable, and launches
3443 pluggable transports on demand (which gets us closer to integrating
3444 pluggable transport support by default -- not to be confused with Tor
3445 bundles enabling pluggable transports and bridges by default).
3447 o Major features (client security):
3448 - When we choose a path for a 3-hop circuit, make sure it contains
3449 at least one relay that supports the NTor circuit extension
3450 handshake. Otherwise, there is a chance that we're building
3451 a circuit that's worth attacking by an adversary who finds
3452 breaking 1024-bit crypto doable, and that chance changes the game
3453 theory. Implements ticket 9777.
3454 - Clients now look at the "usecreatefast" consensus parameter to
3455 decide whether to use CREATE_FAST or CREATE cells for the first hop
3456 of their circuit. This approach can improve security on connections
3457 where Tor's circuit handshake is stronger than the available TLS
3458 connection security levels, but the tradeoff is more computational
3459 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3461 o Major features (bridges):
3462 - Don't launch pluggable transport proxies if we don't have any
3463 bridges configured that would use them. Now we can list many
3464 pluggable transports, and Tor will dynamically start one when it
3465 hears a bridge address that needs it. Resolves ticket 5018.
3466 - The bridge directory authority now assigns status flags (Stable,
3467 Guard, etc) to bridges based on thresholds calculated over all
3468 Running bridges. Now bridgedb can finally make use of its features
3469 to e.g. include at least one Stable bridge in its answers. Fixes
3472 o Major features (other):
3473 - Extend ORCONN controller event to include an "ID" parameter,
3474 and add four new controller event types CONN_BW, CIRC_BW,
3475 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
3476 The new events are emitted in private Tor networks only, with the
3477 goal of being able to better track performance and load during
3478 full-network simulations. Implements proposal 218 and ticket 7359.
3479 - On some platforms (currently: recent OSX versions, glibc-based
3480 platforms that support the ELF format, and a few other
3481 Unix-like operating systems), Tor can now dump stack traces
3482 when a crash occurs or an assertion fails. By default, traces
3483 are dumped to stderr (if possible) and to any logs that are
3484 reporting errors. Implements ticket 9299.
3487 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3488 not entirely remove it from the connection lists. Fixes bug 9602;
3489 bugfix on 0.2.4.4-alpha.
3490 - Do not treat streams that fail with reason
3491 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3492 since it could also indicate an ENETUNREACH connection error. Fixes
3493 part of bug 10777; bugfix on 0.2.4.8-alpha.
3495 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3496 - Do not allow OpenSSL engines to replace the PRNG, even when
3497 HardwareAccel is set. The only default builtin PRNG engine uses
3498 the Intel RDRAND instruction to replace the entire PRNG, and
3499 ignores all attempts to seed it with more entropy. That's
3500 cryptographically stupid: the right response to a new alleged
3501 entropy source is never to discard all previously used entropy
3502 sources. Fixes bug 10402; works around behavior introduced in
3503 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3505 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3506 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3507 - Avoid launching spurious extra circuits when a stream is pending.
3508 This fixes a bug where any circuit that _wasn't_ unusable for new
3509 streams would be treated as if it were, causing extra circuits to
3510 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3512 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3513 - No longer stop reading or writing on cpuworker connections when
3514 our rate limiting buckets go empty. Now we should handle circuit
3515 handshake requests more promptly. Resolves bug 9731.
3516 - Stop trying to bootstrap all our directory information from
3517 only our first guard. Discovered while fixing bug 9946; bugfix
3520 o Minor features (bridges, pluggable transports):
3521 - Add threshold cutoffs to the networkstatus document created by
3522 the Bridge Authority. Fixes bug 1117.
3523 - On Windows, spawn background processes using the CREATE_NO_WINDOW
3524 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
3525 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
3526 Vidalia set this option for us.) Implements ticket 10297.
3528 o Minor features (security):
3529 - Always clear OpenSSL bignums before freeing them -- even bignums
3530 that don't contain secrets. Resolves ticket 10793. Patch by
3533 o Minor features (config options and command line):
3534 - Add an --allow-missing-torrc commandline option that tells Tor to
3535 run even if the configuration file specified by -f is not available.
3536 Implements ticket 10060.
3537 - Add support for the TPROXY transparent proxying facility on Linux.
3538 See documentation for the new TransProxyType option for more
3539 details. Implementation by "thomo". Closes ticket 10582.
3541 o Minor features (controller):
3542 - Add a new "HS_DESC" controller event that reports activities
3543 related to hidden service descriptors. Resolves ticket 8510.
3544 - New "DROPGUARDS" controller command to forget all current entry
3545 guards. Not recommended for ordinary use, since replacing guards
3546 too frequently makes several attacks easier. Resolves ticket 9934;
3549 o Minor features (build):
3550 - Assume that a user using ./configure --host wants to cross-compile,
3551 and give an error if we cannot find a properly named
3552 tool-chain. Add a --disable-tool-name-check option to proceed
3553 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
3554 - If we run ./configure and the compiler recognizes -fstack-protector
3555 but the linker rejects it, warn the user about a potentially missing
3556 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
3558 o Minor features (testing):
3559 - If Python is installed, "make check" now runs extra tests beyond
3560 the unit test scripts.
3561 - When bootstrapping a test network, sometimes very few relays get
3562 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
3563 specify a set of relays which should be voted Guard regardless of
3564 their uptime or bandwidth. Addresses ticket 9206.
3566 o Minor features (log messages):
3567 - When ServerTransportPlugin is set on a bridge, Tor can write more
3568 useful statistics about bridge use in its extrainfo descriptors,
3569 but only if the Extended ORPort ("ExtORPort") is set too. Add a
3570 log message to inform the user in this case. Resolves ticket 9651.
3571 - When receiving a new controller connection, log the origin address.
3572 Resolves ticket 9698; patch from "sigpipe".
3573 - When logging OpenSSL engine status at startup, log the status of
3574 more engines. Fixes ticket 10043; patch from Joshua Datko.
3575 - Turn "circuit handshake stats since last time" log messages into a
3576 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3578 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3579 - Improve the circuit queue out-of-memory handler. Previously, when
3580 we ran low on memory, we'd close whichever circuits had the most
3581 queued cells. Now, we close those that have the *oldest* queued
3582 cells, on the theory that those are most responsible for us
3583 running low on memory. Based on analysis from a forthcoming paper
3584 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3585 - Generate bootstrapping status update events correctly when fetching
3586 microdescriptors. Fixes bug 9927.
3587 - Update to the October 2 2013 Maxmind GeoLite Country database.
3589 o Minor bugfixes (clients):
3590 - When closing a channel that has already been open, do not close
3591 pending circuits that were waiting to connect to the same relay.
3592 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
3595 o Minor bugfixes (relays):
3596 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3597 exit node as a NOROUTE error, not an INTERNAL error, since they
3598 can apparently happen when trying to connect to the wrong sort
3599 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3601 o Minor bugfixes (bridges):
3602 - Fix a bug where the first connection works to a bridge that uses a
3603 pluggable transport with client-side parameters, but we don't send
3604 the client-side parameters on subsequent connections. (We don't
3605 use any pluggable transports with client-side parameters yet,
3606 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
3607 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
3609 o Minor bugfixes (node selection):
3610 - If ExcludeNodes is set, consider non-excluded hidden service
3611 directory servers before excluded ones. Do not consider excluded
3612 hidden service directory servers at all if StrictNodes is
3613 set. (Previously, we would sometimes decide to connect to those
3614 servers, and then realize before we initiated a connection that
3615 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
3617 - If we set the ExitNodes option but it doesn't include any nodes
3618 that have the Exit flag, we would choose not to bootstrap. Now we
3619 bootstrap so long as ExitNodes includes nodes which can exit to
3620 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
3622 o Minor bugfixes (controller and command-line):
3623 - If changing a config option via "setconf" fails in a recoverable
3624 way, we used to nonetheless write our new control ports to the
3625 file described by the "ControlPortWriteToFile" option. Now we only
3626 write out that file if we successfully switch to the new config
3627 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
3628 - When a command-line option such as --version or --help that
3629 ordinarily implies --hush appears on the command line along with
3630 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
3631 only if it appeared later on the command line. Fixes bug 9578;
3632 bugfix on 0.2.5.1-alpha.
3634 o Minor bugfixes (code correctness):
3635 - Previously we used two temporary files when writing descriptors to
3636 disk; now we only use one. Fixes bug 1376.
3637 - Remove an erroneous (but impossible and thus harmless) pointer
3638 comparison that would have allowed compilers to skip a bounds
3639 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
3640 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
3641 - Fix an always-true assertion in pluggable transports code so it
3642 actually checks what it was trying to check. Fixes bug 10046;
3643 bugfix on 0.2.3.9-alpha. Found by "dcb".
3645 o Minor bugfixes (protocol correctness):
3646 - When receiving a VERSIONS cell with an odd number of bytes, close
3647 the connection immediately since the cell is malformed. Fixes bug
3648 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
3651 o Minor bugfixes (build):
3652 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
3653 turned off (that is, without support for v2 link handshakes). Fixes
3654 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
3655 - Fix compilation warnings and startup issues when running with
3656 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
3658 - Fix compilation on Solaris 9, which didn't like us having an
3659 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
3661 o Minor bugfixes (testing):
3662 - Fix a segmentation fault in our benchmark code when running with
3663 Fedora's OpenSSL package, or any other OpenSSL that provides
3664 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3666 o Minor bugfixes (log messages):
3667 - Fix a bug where clients using bridges would report themselves
3668 as 50% bootstrapped even without a live consensus document.
3669 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
3670 - Suppress a warning where, if there's only one directory authority
3671 in the network, we would complain that votes and signatures cannot
3672 be uploaded to other directory authorities. Fixes bug 10842;
3673 bugfix on 0.2.2.26-beta.
3674 - Report bootstrapping progress correctly when we're downloading
3675 microdescriptors. We had updated our "do we have enough microdescs
3676 to begin building circuits?" logic most recently in 0.2.4.10-alpha
3677 (see bug 5956), but we left the bootstrap status event logic at
3678 "how far through getting 1/4 of them are we?" Fixes bug 9958;
3679 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
3681 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3682 - Avoid a crash bug when starting with a corrupted microdescriptor
3683 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3684 - If we fail to dump a previously cached microdescriptor to disk, avoid
3685 freeing duplicate data later on. Fixes bug 10423; bugfix on
3686 0.2.4.13-alpha. Spotted by "bobnomnom".
3688 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3689 - Correctly log long IPv6 exit policies, instead of truncating them
3690 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3691 - Our default TLS ecdhe groups were backwards: we meant to be using
3692 P224 for relays (for performance win) and P256 for bridges (since
3693 it is more common in the wild). Instead we had it backwards. After
3694 reconsideration, we decided that the default should be P256 on all
3695 hosts, since its security is probably better, and since P224 is
3696 reportedly used quite little in the wild. Found by "skruffy" on
3697 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3698 - Free directory authority certificate download statuses on exit
3699 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3701 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3702 - If the guard we choose first doesn't answer, we would try the
3703 second guard, but once we connected to the second guard we would
3704 abandon it and retry the first one, slowing down bootstrapping.
3705 The fix is to treat all our initially chosen guards as acceptable
3706 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3707 - Fix an assertion failure that would occur when disabling the
3708 ORPort setting on a running Tor process while accounting was
3709 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3710 - When examining the list of network interfaces to find our address,
3711 do not consider non-running or disabled network interfaces. Fixes
3712 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3713 - Avoid an off-by-one error when checking buffer boundaries when
3714 formatting the exit status of a pluggable transport helper.
3715 This is probably not an exploitable bug, but better safe than
3716 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3719 o Removed code and features:
3720 - Clients now reject any directory authority certificates lacking
3721 a dir-key-crosscert element. These have been included since
3722 0.2.1.9-alpha, so there's no real reason for them to be optional
3723 any longer. Completes proposal 157. Resolves ticket 10162.
3724 - Remove all code that existed to support the v2 directory system,
3725 since there are no longer any v2 directory authorities. Resolves
3727 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
3728 options, which were used for designating authorities as "Hidden
3729 service authorities". There has been no use of hidden service
3730 authorities since 0.2.2.1-alpha, when we stopped uploading or
3731 downloading v0 hidden service descriptors. Fixes bug 10881; also
3732 part of a fix for bug 10841.
3734 o Code simplification and refactoring:
3735 - Remove some old fallback code designed to keep Tor clients working
3736 in a network with only two working relays. Elsewhere in the code we
3737 have long since stopped supporting such networks, so there wasn't
3738 much point in keeping it around. Addresses ticket 9926.
3739 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
3740 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
3741 - Remove data structures which were introduced to implement the
3742 CellStatistics option: they are now redundant with the addition
3743 of a timestamp to the regular packed_cell_t data structure, which
3744 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
3747 o Documentation (man page) fixes:
3748 - Update manpage to describe some of the files you can expect to
3749 find in Tor's DataDirectory. Addresses ticket 9839.
3750 - Document that all but one DirPort entry must have the NoAdvertise
3751 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3753 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3754 - Clarify the usage and risks of setting the ContactInfo torrc line
3755 for your relay or bridge. Resolves ticket 9854.
3756 - Add anchors to the manpage so we can link to the html version of
3757 the documentation for specific options. Resolves ticket 9866.
3758 - Replace remaining references to DirServer in man page and
3759 log entries. Resolves ticket 10124.
3762 - Make the "tor-gencert" tool used by directory authority operators
3763 create 2048-bit signing keys by default (rather than 1024-bit, since
3764 1024-bit is uncomfortably small these days). Addresses ticket 10324.
3767 Changes in version 0.2.4.20 - 2013-12-22
3768 Tor 0.2.4.20 fixes potentially poor random number generation for users
3769 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
3770 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
3771 and 4) have no state file in their DataDirectory (as would happen on
3772 first start). Users who generated relay or hidden service identity
3773 keys in such a situation should discard them and generate new ones.
3775 This release also fixes a logic error that caused Tor clients to build
3776 many more preemptive circuits than they actually need.
3779 - Do not allow OpenSSL engines to replace the PRNG, even when
3780 HardwareAccel is set. The only default builtin PRNG engine uses
3781 the Intel RDRAND instruction to replace the entire PRNG, and
3782 ignores all attempts to seed it with more entropy. That's
3783 cryptographically stupid: the right response to a new alleged
3784 entropy source is never to discard all previously used entropy
3785 sources. Fixes bug 10402; works around behavior introduced in
3786 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3788 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3789 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3790 - Avoid launching spurious extra circuits when a stream is pending.
3791 This fixes a bug where any circuit that _wasn't_ unusable for new
3792 streams would be treated as if it were, causing extra circuits to
3793 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3796 - Avoid a crash bug when starting with a corrupted microdescriptor
3797 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3798 - If we fail to dump a previously cached microdescriptor to disk, avoid
3799 freeing duplicate data later on. Fixes bug 10423; bugfix on
3800 0.2.4.13-alpha. Spotted by "bobnomnom".
3803 Changes in version 0.2.4.19 - 2013-12-11
3804 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
3805 (1986-2013). Aaron worked on diverse projects including helping to guide
3806 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
3807 transparency to the U.S government's PACER documents, and contributing
3808 design and development for Tor and Tor2Web. Aaron was one of the latest
3809 martyrs in our collective fight for civil liberties and human rights,
3810 and his death is all the more painful because he was one of us.
3812 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
3813 a new circuit handshake and link encryption that use ECC to provide
3814 better security and efficiency; makes relays better manage circuit
3815 creation requests; uses "directory guards" to reduce client enumeration
3816 risks; makes bridges collect and report statistics about the pluggable
3817 transports they support; cleans up and improves our geoip database;
3818 gets much closer to IPv6 support for clients, bridges, and relays; makes
3819 directory authorities use measured bandwidths rather than advertised
3820 ones when computing flags and thresholds; disables client-side DNS
3821 caching to reduce tracking risks; and fixes a big bug in bridge
3822 reachability testing. This release introduces two new design
3823 abstractions in the code: a new "channel" abstraction between circuits
3824 and or_connections to allow for implementing alternate relay-to-relay
3825 transports, and a new "circuitmux" abstraction storing the queue of
3826 circuits for a channel. The release also includes many stability,
3827 security, and privacy fixes.
3830 Changes in version 0.2.4.18-rc - 2013-11-16
3831 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
3832 series. It takes a variety of fixes from the 0.2.5.x branch to improve
3833 stability, performance, and better handling of edge cases.
3836 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3837 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3838 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3839 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3840 them to solve bug 6033.)
3843 - No longer stop reading or writing on cpuworker connections when
3844 our rate limiting buckets go empty. Now we should handle circuit
3845 handshake requests more promptly. Resolves bug 9731.
3846 - If we are unable to save a microdescriptor to the journal, do not
3847 drop it from memory and then reattempt downloading it. Fixes bug
3848 9645; bugfix on 0.2.2.6-alpha.
3849 - Stop trying to bootstrap all our directory information from
3850 only our first guard. Discovered while fixing bug 9946; bugfix
3852 - The new channel code sometimes lost track of in-progress circuits,
3853 causing long-running clients to stop building new circuits. The
3854 fix is to always call circuit_n_chan_done(chan, 0) from
3855 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3857 o Minor bugfixes (on 0.2.4.x):
3858 - Correctly log long IPv6 exit policies, instead of truncating them
3859 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3860 - Our default TLS ecdhe groups were backwards: we meant to be using
3861 P224 for relays (for performance win) and P256 for bridges (since
3862 it is more common in the wild). Instead we had it backwards. After
3863 reconsideration, we decided that the default should be P256 on all
3864 hosts, since its security is probably better, and since P224 is
3865 reportedly used quite little in the wild. Found by "skruffy" on
3866 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3867 - Free directory authority certificate download statuses on exit
3868 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3870 o Minor bugfixes (on 0.2.3.x and earlier):
3871 - If the guard we choose first doesn't answer, we would try the
3872 second guard, but once we connected to the second guard we would
3873 abandon it and retry the first one, slowing down bootstrapping.
3874 The fix is to treat all our initially chosen guards as acceptable
3875 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3876 - Fix an assertion failure that would occur when disabling the
3877 ORPort setting on a running Tor process while accounting was
3878 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3879 - When examining the list of network interfaces to find our address,
3880 do not consider non-running or disabled network interfaces. Fixes
3881 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3882 - Avoid an off-by-one error when checking buffer boundaries when
3883 formatting the exit status of a pluggable transport helper.
3884 This is probably not an exploitable bug, but better safe than
3885 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3888 o Minor features (protecting client timestamps):
3889 - Clients no longer send timestamps in their NETINFO cells. These were
3890 not used for anything, and they provided one small way for clients
3891 to be distinguished from each other as they moved from network to
3892 network or behind NAT. Implements part of proposal 222.
3893 - Clients now round timestamps in INTRODUCE cells down to the nearest
3894 10 minutes. If a new Support022HiddenServices option is set to 0, or
3895 if it's set to "auto" and the feature is disabled in the consensus,
3896 the timestamp is sent as 0 instead. Implements part of proposal 222.
3897 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3898 a big deal from a security point of view, but it achieves no actual
3899 good purpose, and isn't needed. Implements part of proposal 222.
3900 - Reduce down accuracy of timestamps in hidden service descriptors.
3901 Implements part of proposal 222.
3903 o Minor features (other):
3904 - Improve the circuit queue out-of-memory handler. Previously, when
3905 we ran low on memory, we'd close whichever circuits had the most
3906 queued cells. Now, we close those that have the *oldest* queued
3907 cells, on the theory that those are most responsible for us
3908 running low on memory. Based on analysis from a forthcoming paper
3909 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3910 - Generate bootstrapping status update events correctly when fetching
3911 microdescriptors. Fixes bug 9927.
3912 - Update to the October 2 2013 Maxmind GeoLite Country database.
3914 o Documentation fixes:
3915 - Clarify the usage and risks of setting the ContactInfo torrc line
3916 for your relay or bridge. Resolves ticket 9854.
3917 - Add anchors to the manpage so we can link to the html version of
3918 the documentation for specific options. Resolves ticket 9866.
3919 - Replace remaining references to DirServer in man page and
3920 log entries. Resolves ticket 10124.
3923 Changes in version 0.2.5.1-alpha - 2013-10-02
3924 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
3925 on Linux, allows bridges that offer pluggable transports to report usage
3926 statistics, fixes many issues to make testing easier, and provides
3927 a pile of minor features and bugfixes that have been waiting for a
3928 release of the new branch.
3930 This is the first alpha release in a new series, so expect there to
3931 be bugs. Users who would rather test out a more stable branch should
3932 stay with 0.2.4.x for now.
3934 o Major features (security):
3935 - Use the seccomp2 syscall filtering facility on Linux to limit
3936 which system calls Tor can invoke. This is an experimental,
3937 Linux-only feature to provide defense-in-depth against unknown
3938 attacks. To try turning it on, set "Sandbox 1" in your torrc
3939 file. Please be ready to report bugs. We hope to add support
3940 for better sandboxing in the future, including more fine-grained
3941 filters, better division of responsibility, and support for more
3942 platforms. This work has been done by Cristian-Matei Toader for
3943 Google Summer of Code.
3944 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3945 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3946 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3947 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3948 them to solve bug 6033.)
3950 o Major features (other):
3951 - Add support for passing arguments to managed pluggable transport
3952 proxies. Implements ticket 3594.
3953 - Bridges now track GeoIP information and the number of their users
3954 even when pluggable transports are in use, and report usage
3955 statistics in their extra-info descriptors. Resolves tickets 4773
3957 - Make testing Tor networks bootstrap better: lower directory fetch
3958 retry schedules and maximum interval without directory requests,
3959 and raise maximum download tries. Implements ticket 6752.
3960 - Add make target 'test-network' to run tests on a Chutney network.
3961 Implements ticket 8530.
3962 - The ntor handshake is now on-by-default, no matter what the
3963 directory authorities recommend. Implements ticket 8561.
3966 - Instead of writing destroy cells directly to outgoing connection
3967 buffers, queue them and intersperse them with other outgoing cells.
3968 This can prevent a set of resource starvation conditions where too
3969 many pending destroy cells prevent data cells from actually getting
3970 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
3971 bugfix on 0.2.0.1-alpha.
3972 - If we are unable to save a microdescriptor to the journal, do not
3973 drop it from memory and then reattempt downloading it. Fixes bug
3974 9645; bugfix on 0.2.2.6-alpha.
3975 - The new channel code sometimes lost track of in-progress circuits,
3976 causing long-running clients to stop building new circuits. The
3977 fix is to always call circuit_n_chan_done(chan, 0) from
3978 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3981 - Tor now builds each source file in two modes: a mode that avoids
3982 exposing identifiers needlessly, and another mode that exposes
3983 more identifiers for testing. This lets the compiler do better at
3984 optimizing the production code, while enabling us to take more
3985 radical measures to let the unit tests test things.
3986 - The production builds no longer include functions used only in
3987 the unit tests; all functions exposed from a module only for
3988 unit-testing are now static in production builds.
3989 - Add an --enable-coverage configuration option to make the unit
3990 tests (and a new src/or/tor-cov target) to build with gcov test
3994 - We now have rudimentary function mocking support that our unit
3995 tests can use to test functions in isolation. Function mocking
3996 lets the tests temporarily replace a function's dependencies with
3997 stub functions, so that the tests can check the function without
3998 invoking the other functions it calls.
3999 - Add more unit tests for the <circid,channel>->circuit map, and
4000 the destroy-cell-tracking code to fix bug 7912.
4001 - Unit tests for failing cases of the TAP onion handshake.
4002 - More unit tests for address-manipulation functions.
4004 o Minor features (protecting client timestamps):
4005 - Clients no longer send timestamps in their NETINFO cells. These were
4006 not used for anything, and they provided one small way for clients
4007 to be distinguished from each other as they moved from network to
4008 network or behind NAT. Implements part of proposal 222.
4009 - Clients now round timestamps in INTRODUCE cells down to the nearest
4010 10 minutes. If a new Support022HiddenServices option is set to 0, or
4011 if it's set to "auto" and the feature is disabled in the consensus,
4012 the timestamp is sent as 0 instead. Implements part of proposal 222.
4013 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4014 a big deal from a security point of view, but it achieves no actual
4015 good purpose, and isn't needed. Implements part of proposal 222.
4016 - Reduce down accuracy of timestamps in hidden service descriptors.
4017 Implements part of proposal 222.
4019 o Minor features (config options):
4020 - Config (torrc) lines now handle fingerprints which are missing
4021 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4022 - Support a --dump-config option to print some or all of the
4023 configured options. Mainly useful for debugging the command-line
4024 option parsing code. Helps resolve ticket 4647.
4025 - Raise awareness of safer logging: notify user of potentially
4026 unsafe config options, like logging more verbosely than severity
4027 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4028 - Add a new configuration option TestingV3AuthVotingStartOffset
4029 that bootstraps a network faster by changing the timing for
4030 consensus votes. Addresses ticket 8532.
4031 - Add a new torrc option "ServerTransportOptions" that allows
4032 bridge operators to pass configuration parameters to their
4033 pluggable transports. Resolves ticket 8929.
4034 - The config (torrc) file now accepts bandwidth and space limits in
4035 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4036 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4039 o Minor features (build):
4040 - Add support for `--library-versions` flag. Implements ticket 6384.
4041 - Return the "unexpected sendme" warnings to a warn severity, but make
4042 them rate limited, to help diagnose ticket 8093.
4043 - Detect a missing asciidoc, and warn the user about it, during
4044 configure rather than at build time. Fixes issue 6506. Patch from
4047 o Minor features (other):
4048 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4049 sockets in a single system call. Implements ticket 5129.
4050 - Log current accounting state (bytes sent and received + remaining
4051 time for the current accounting period) in the relay's heartbeat
4052 message. Implements ticket 5526; patch from Peter Retzlaff.
4053 - Implement the TRANSPORT_LAUNCHED control port event that
4054 notifies controllers about new launched pluggable
4055 transports. Resolves ticket 5609.
4056 - If we're using the pure-C 32-bit curve25519_donna implementation
4057 of curve25519, build it with the -fomit-frame-pointer option to
4058 make it go faster on register-starved hosts. This improves our
4059 handshake performance by about 6% on i386 hosts without nacl.
4061 - Update to the September 4 2013 Maxmind GeoLite Country database.
4064 - Set the listen() backlog limit to the largest actually supported
4065 on the system, not to the value in a header file. Fixes bug 9716;
4066 bugfix on every released Tor.
4067 - No longer accept malformed http headers when parsing urls from
4068 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4069 bugfix on 0.0.6pre1.
4070 - In munge_extrainfo_into_routerinfo(), check the return value of
4071 memchr(). This would have been a serious issue if we ever passed
4072 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4074 - On the chance that somebody manages to build Tor on a
4075 platform where time_t is unsigned, correct the way that
4076 microdesc_add_to_cache() handles negative time arguments.
4077 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4078 - Reject relative control socket paths and emit a warning. Previously,
4079 single-component control socket paths would be rejected, but Tor
4080 would not log why it could not validate the config. Fixes bug 9258;
4081 bugfix on 0.2.3.16-alpha.
4083 o Minor bugfixes (command line):
4084 - Use a single command-line parser for parsing torrc options on the
4085 command line and for finding special command-line options to avoid
4086 inconsistent behavior for torrc option arguments that have the same
4087 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4089 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4090 9573; bugfix on 0.0.9pre5.
4092 o Minor fixes (build, auxiliary programs):
4093 - Stop preprocessing the "torify" script with autoconf, since
4094 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4096 - The tor-fw-helper program now follows the standard convention and
4097 exits with status code "0" on success. Fixes bug 9030; bugfix on
4098 0.2.3.1-alpha. Patch by Arlo Breault.
4099 - Corrected ./configure advice for what openssl dev package you should
4100 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4102 o Minor code improvements:
4103 - Remove constants and tests for PKCS1 padding; it's insecure and
4104 shouldn't be used for anything new. Fixes bug 8792; patch
4106 - Remove instances of strcpy() from the unit tests. They weren't
4107 hurting anything, since they were only in the unit tests, but it's
4108 embarassing to have strcpy() in the code at all, and some analysis
4109 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4110 0.2.3.8-alpha. Patch from Arlo Breault.
4113 - Remove migration code from when we renamed the "cached-routers"
4114 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4115 incidentally resolves ticket 6502 by cleaning up the related code
4116 a bit. Patch from Akshay Hebbar.
4118 o Code simplification and refactoring:
4119 - Extract the common duplicated code for creating a subdirectory
4120 of the data directory and writing to a file in it. Fixes ticket
4121 4282; patch from Peter Retzlaff.
4122 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4123 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4124 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4125 - Add a set of accessor functions for the circuit timeout data
4126 structure. Fixes ticket 6153; patch from "piet".
4127 - Clean up exit paths from connection_listener_new(). Closes ticket
4128 8789. Patch from Arlo Breault.
4129 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4130 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4131 - Use a doubly-linked list to implement the global circuit list.
4132 Resolves ticket 9108. Patch from Marek Majkowski.
4133 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4136 Changes in version 0.2.4.17-rc - 2013-09-05
4137 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
4138 series. It adds an emergency step to help us tolerate the massive
4139 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
4140 circuit-level handshakes now effectively jump the queue compared to
4141 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
4142 big bug hindering bridge reachability tests.
4145 - Relays now process the new "NTor" circuit-level handshake requests
4146 with higher priority than the old "TAP" circuit-level handshake
4147 requests. We still process some TAP requests to not totally starve
4148 0.2.3 clients when NTor becomes popular. A new consensus parameter
4149 "NumNTorsPerTAP" lets us tune the balance later if we need to.
4150 Implements ticket 9574.
4153 - If the circuit build timeout logic is disabled (via the consensus,
4154 or because we are an authority), then don't build testing circuits.
4155 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
4156 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
4157 previously they did not, which prevented them from receiving
4158 successful connections from relays for self-test or bandwidth
4159 testing. Also, when a relay is extending a circuit to a bridge,
4160 it needs to send a NETINFO cell, even when the bridge hasn't sent
4161 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
4162 - If the time to download the next old-style networkstatus is in
4163 the future, do not decline to consider whether to download the
4164 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
4168 - Avoid double-closing the listener socket in our socketpair()
4169 replacement (used on Windows) in the case where the addresses on
4170 our opened sockets don't match what we expected. Fixes bug 9400;
4171 bugfix on 0.0.2pre7. Found by Coverity.
4173 o Minor fixes (config options):
4174 - Avoid overflows when the user sets MaxCircuitDirtiness to a
4175 ridiculously high value, by imposing a (ridiculously high) 30-day
4176 maximum on MaxCircuitDirtiness.
4177 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
4178 message is logged at notice, not at info.
4179 - Warn and fail if a server is configured not to advertise any
4180 ORPorts at all. (We need *something* to put in our descriptor,
4181 or we just won't work.)
4184 - Track how many "TAP" and "NTor" circuit handshake requests we get,
4185 and how many we complete, and log it every hour to help relay
4186 operators follow trends in network load. Addresses ticket 9658.
4187 - Update to the August 7 2013 Maxmind GeoLite Country database.
4190 Changes in version 0.2.4.16-rc - 2013-08-10
4191 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
4192 series. It fixes several crash bugs in the 0.2.4 branch.
4195 - Fix a bug in the voting algorithm that could yield incorrect results
4196 when a non-naming authority declared too many flags. Fixes bug 9200;
4197 bugfix on 0.2.0.3-alpha.
4198 - Fix an uninitialized read that could in some cases lead to a remote
4199 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
4200 Anybody running a hidden service on the experimental 0.2.4.x
4201 branch should upgrade. (This is, so far as we know, unrelated to
4203 - Avoid an assertion failure when processing DNS replies without the
4204 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
4205 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
4206 0.2.4.15-rc. Found by stem integration tests.
4209 - Fix an invalid memory read that occured when a pluggable
4210 transport proxy failed its configuration protocol.
4211 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
4212 - When evaluating whether to use a connection that we haven't
4213 decided is canonical using a recent link protocol version,
4214 decide that it's canonical only if it used address _does_
4215 match the desired address. Fixes bug 9309; bugfix on
4216 0.2.4.4-alpha. Reported by skruffy.
4217 - Make the default behavior of NumDirectoryGuards be to track
4218 NumEntryGuards. Now a user who changes only NumEntryGuards will get
4219 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
4220 - Fix a spurious compilation warning with some older versions of
4221 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
4224 - Update to the July 3 2013 Maxmind GeoLite Country database.
4227 Changes in version 0.2.4.15-rc - 2013-07-01
4228 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
4229 series. It fixes a few smaller bugs, but generally appears stable.
4230 Please test it and let us know whether it is!
4233 - When receiving a new configuration file via the control port's
4234 LOADCONF command, do not treat the defaults file as absent.
4235 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
4238 - Issue a warning when running with the bufferevents backend enabled.
4239 It's still not stable, and people should know that they're likely
4240 to hit unexpected problems. Closes ticket 9147.
4243 Changes in version 0.2.4.14-alpha - 2013-06-18
4244 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
4245 present in 0.2.4.13-alpha.
4248 - When we have too much memory queued in circuits (according to a new
4249 MaxMemInCellQueues option), close the circuits consuming the most
4250 memory. This prevents us from running out of memory as a relay if
4251 circuits fill up faster than they can be drained. Fixes bug 9063;
4252 bugfix on the 54th commit of Tor. This bug is a further fix beyond
4253 bug 6252, whose fix was merged into 0.2.3.21-rc.
4255 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
4256 where we tried to solve this issue simply by imposing an upper limit
4257 on the number of queued cells for a single circuit. That approach
4258 proved to be problematic, since there are ways to provoke clients to
4259 send a number of cells in excess of any such reasonable limit. Fixes
4260 bug 9072; bugfix on 0.2.4.13-alpha.
4262 - Limit hidden service descriptors to at most ten introduction
4263 points, to slow one kind of guard enumeration. Fixes bug 9002;
4264 bugfix on 0.1.1.11-alpha.
4267 Changes in version 0.2.4.13-alpha - 2013-06-14
4268 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
4269 vulnerabilities, makes socks5 username/password circuit isolation
4270 actually actually work (this time for sure!), and cleans up a bunch
4271 of other issues in preparation for a release candidate.
4273 o Major bugfixes (robustness):
4274 - Close any circuit that has too many cells queued on it. Fixes
4275 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
4276 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
4277 - Prevent the get_freelists() function from running off the end of
4278 the list of freelists if it somehow gets an unrecognized
4279 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
4281 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
4282 when an exit connection with optimistic data succeeds immediately
4283 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
4285 - Fix a directory authority crash bug when building a consensus
4286 using an older consensus as its basis. Fixes bug 8833. Bugfix
4290 - Avoid a memory leak where we would leak a consensus body when we
4291 find that a consensus which we couldn't previously verify due to
4292 missing certificates is now verifiable. Fixes bug 8719; bugfix
4294 - We used to always request authority certificates by identity digest,
4295 meaning we'd get the newest one even when we wanted one with a
4296 different signing key. Then we would complain about being given
4297 a certificate we already had, and never get the one we really
4298 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
4299 resource to request the one we want. Fixes bug 5595; bugfix on
4301 - Follow the socks5 protocol when offering username/password
4302 authentication. The fix for bug 8117 exposed this bug, and it
4303 turns out real-world applications like Pidgin do care. Bugfix on
4304 0.2.3.2-alpha; fixes bug 8879.
4305 - Prevent failures on Windows Vista and later when rebuilding the
4306 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
4307 bugfix on 0.2.4.12-alpha.
4310 - Fix an impossible buffer overrun in the AES unit tests. Fixes
4311 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
4312 - If for some reason we fail to write a microdescriptor while
4313 rebuilding the cache, do not let the annotations from that
4314 microdescriptor linger in the cache file, and do not let the
4315 microdescriptor stay recorded as present in its old location.
4316 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
4317 - Fix a memory leak that would occur whenever a configuration
4318 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
4319 - Paste the description for PathBias parameters from the man
4320 page into or.h, so the code documents them too. Fixes bug 7982;
4321 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
4322 - Relays now treat a changed IPv6 ORPort as sufficient reason to
4323 publish an updated descriptor. Fixes bug 6026; bugfix on
4325 - When launching a resolve request on behalf of an AF_UNIX control
4326 socket, omit the address field of the new entry connection, used in
4327 subsequent controller events, rather than letting tor_dup_addr()
4328 set it to "<unknown address type>". Fixes bug 8639; bugfix on
4331 o Minor bugfixes (log messages):
4332 - Fix a scaling issue in the path bias accounting code that
4333 resulted in "Bug:" log messages from either
4334 pathbias_scale_close_rates() or pathbias_count_build_success().
4335 This represents a bugfix on a previous bugfix: the original fix
4336 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
4338 - Give a less useless error message when the user asks for an IPv4
4339 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
4343 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
4344 to tolerate bug 8093 for now.
4345 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
4346 in directory authority votes to describe whether they have enough
4347 measured bandwidths to ignore advertised (relay descriptor)
4348 bandwidth claims. Resolves ticket 8711.
4349 - Update to the June 5 2013 Maxmind GeoLite Country database.
4351 o Removed documentation:
4352 - Remove some of the older contents of doc/ as obsolete; move others
4353 to torspec.git. Fixes bug 8965.
4355 o Code simplification and refactoring:
4356 - Avoid using character buffers when constructing most directory
4357 objects: this approach was unwieldy and error-prone. Instead,
4358 build smartlists of strings, and concatenate them when done.
4361 Changes in version 0.2.4.12-alpha - 2013-04-18
4362 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
4363 process for lengthening the guard rotation period, makes directory
4364 authority opinions in the consensus a bit less gameable, makes socks5
4365 username/password circuit isolation actually work, and fixes a wide
4366 variety of other issues.
4369 - Raise the default time that a client keeps an entry guard from
4370 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
4371 2012 paper. (We would make it even longer, but we need better client
4372 load balancing first.) Also, make the guard lifetime controllable
4373 via a new GuardLifetime torrc option and a GuardLifetime consensus
4374 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
4375 - Directory authorities now prefer using measured bandwidths to
4376 advertised ones when computing flags and thresholds. Resolves
4378 - Directory authorities that have more than a threshold number
4379 of relays with measured bandwidths now treat relays with unmeasured
4380 bandwidths as having bandwidth 0. Resolves ticket 8435.
4382 o Major bugfixes (assert / resource use):
4383 - Avoid a bug where our response to TLS renegotiation under certain
4384 network conditions could lead to a busy-loop, with 100% CPU
4385 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
4386 - Avoid an assertion when we discover that we'd like to write a cell
4387 onto a closing connection: just discard the cell. Fixes another
4388 case of bug 7350; bugfix on 0.2.4.4-alpha.
4390 o Major bugfixes (client-side privacy):
4391 - When we mark a circuit as unusable for new circuits, have it
4392 continue to be unusable for new circuits even if MaxCircuitDirtiness
4393 is increased too much at the wrong time, or the system clock jumps
4394 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
4395 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
4396 which have resolved to internal addresses") is set, apply that
4397 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
4398 - When an exit relay rejects a stream with reason "exit policy", but
4399 we only know an exit policy summary (e.g. from the microdesc
4400 consensus) for it, do not mark the relay as useless for all exiting.
4401 Instead, mark just the circuit as unsuitable for that particular
4402 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
4403 - Allow applications to get proper stream isolation with
4404 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
4405 username/password authentication also offer "no authentication". Tor
4406 had previously preferred "no authentication", so the applications
4407 never actually sent Tor their auth details. Now Tor selects
4408 username/password authentication if it's offered. You can disable
4409 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
4410 bug 8117; bugfix on 0.2.3.3-alpha.
4412 o Major bugfixes (other):
4413 - When unable to find any working directory nodes to use as a
4414 directory guard, give up rather than adding the same non-working
4415 nodes to the directory guard list over and over. Fixes bug 8231;
4416 bugfix on 0.2.4.8-alpha.
4419 - Reject as invalid most directory objects containing a NUL.
4420 Belt-and-suspender fix for bug 8037.
4421 - In our testsuite, create temporary directories with a bit more
4422 entropy in their name to make name collisions less likely. Fixes
4424 - Add CACHED keyword to ADDRMAP events in the control protocol
4425 to indicate whether a DNS result will be cached or not. Resolves
4427 - Update to the April 3 2013 Maxmind GeoLite Country database.
4429 o Minor features (build):
4430 - Detect and reject attempts to build Tor with threading support
4431 when OpenSSL has been compiled without threading support.
4433 - Clarify that when autoconf is checking for nacl, it is checking
4434 specifically for nacl with a fast curve25519 implementation.
4436 - Warn if building on a platform with an unsigned time_t: there
4437 are too many places where Tor currently assumes that time_t can
4438 hold negative values. We'd like to fix them all, but probably
4441 o Minor bugfixes (build):
4442 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
4443 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
4444 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
4445 - Add the old src/or/micro-revision.i filename to CLEANFILES.
4446 On the off chance that somebody has one, it will go away as soon
4447 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
4448 - Build Tor correctly on 32-bit platforms where the compiler can build
4449 but not run code using the "uint128_t" construction. Fixes bug 8587;
4450 bugfix on 0.2.4.8-alpha.
4451 - Fix compilation warning with some versions of clang that would
4452 prefer the -Wswitch-enum compiler flag to warn about switch
4453 statements with missing enum values, even if those switch
4454 statements have a "default:" statement. Fixes bug 8598; bugfix
4457 o Minor bugfixes (protocol):
4458 - Fix the handling of a TRUNCATE cell when it arrives while the
4459 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
4460 - Fix a misframing issue when reading the version numbers in a
4461 VERSIONS cell. Previously we would recognize [00 01 00 02] as
4462 'version 1, version 2, and version 0x100', when it should have
4463 only included versions 1 and 2. Fixes bug 8059; bugfix on
4464 0.2.0.10-alpha. Reported pseudonymously.
4465 - Make the format and order of STREAM events for DNS lookups
4466 consistent among the various ways to launch DNS lookups. Fixes
4467 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
4468 - Correct our check for which versions of Tor support the EXTEND2
4469 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
4470 later, when support was really added in version 0.2.4.8-alpha.
4471 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
4473 o Minor bugfixes (other):
4474 - Correctly store microdescriptors and extrainfo descriptors with
4475 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
4476 Bug reported by "cypherpunks".
4477 - Increase the width of the field used to remember a connection's
4478 link protocol version to two bytes. Harmless for now, since the
4479 only currently recognized versions are one byte long. Reported
4480 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
4481 - If the state file's path bias counts are invalid (presumably from a
4482 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
4483 additional checks and log messages to the scaling of Path Bias
4484 counts, in case there still are remaining issues with scaling.
4485 Should help resolve bug 8235.
4486 - Eliminate several instances where we use "Nickname=ID" to refer to
4487 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
4488 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
4489 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
4491 o Minor bugfixes (syscalls):
4492 - Always check the return values of functions fcntl() and
4493 setsockopt(). We don't believe these are ever actually failing in
4494 practice, but better safe than sorry. Also, checking these return
4495 values should please analysis tools like Coverity. Patch from
4496 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
4497 - Use direct writes rather than stdio when building microdescriptor
4498 caches, in an attempt to mitigate bug 8031, or at least make it
4501 o Minor bugfixes (config):
4502 - When rejecting a configuration because we were unable to parse a
4503 quoted string, log an actual error message. Fixes bug 7950; bugfix
4505 - Behave correctly when the user disables LearnCircuitBuildTimeout
4506 but doesn't tell us what they would like the timeout to be. Fixes
4507 bug 6304; bugfix on 0.2.2.14-alpha.
4508 - When autodetecting the number of CPUs, use the number of available
4509 CPUs in preference to the number of configured CPUs. Inform the
4510 user if this reduces the number of available CPUs. Fixes bug 8002;
4511 bugfix on 0.2.3.1-alpha.
4512 - Make it an error when you set EntryNodes but disable UseGuardNodes,
4513 since it will (surprisingly to some users) ignore EntryNodes. Fixes
4514 bug 8180; bugfix on 0.2.3.11-alpha.
4515 - Allow TestingTorNetworks to override the 4096-byte minimum for
4516 the Fast threshold. Otherwise they can't bootstrap until they've
4517 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
4518 - Fix some logic errors when the user manually overrides the
4519 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
4522 o Minor bugfixes (log messages to help diagnose bugs):
4523 - If we fail to free a microdescriptor because of bug 7164, log
4524 the filename and line number from which we tried to free it.
4525 - Add another diagnostic to the heartbeat message: track and log
4526 overhead that TLS is adding to the data we write. If this is
4527 high, we are sending too little data to SSL_write at a time.
4528 Diagnostic for bug 7707.
4529 - Add more detail to a log message about relaxed timeouts, to help
4531 - Warn more aggressively when flushing microdescriptors to a
4532 microdescriptor cache fails, in an attempt to mitigate bug 8031,
4533 or at least make it more diagnosable.
4534 - Improve debugging output to help track down bug 8185 ("Bug:
4535 outgoing relay cell has n_chan==NULL. Dropping.")
4536 - Log the purpose of a path-bias testing circuit correctly.
4537 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
4539 o Minor bugfixes (0.2.4.x log messages that were too noisy):
4540 - Don't attempt to relax the timeout of already opened 1-hop circuits.
4541 They might never timeout. This should eliminate some/all cases of
4542 the relaxed timeout log message.
4543 - Use circuit creation time for network liveness evaluation. This
4544 should eliminate warning log messages about liveness caused
4545 by changes in timeout evaluation. Fixes bug 6572; bugfix on
4547 - Reduce a path bias length check from notice to info. The message
4548 is triggered when creating controller circuits. Fixes bug 8196;
4549 bugfix on 0.2.4.8-alpha.
4550 - Fix a path state issue that triggered a notice during relay startup.
4551 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
4552 - Reduce occurrences of warns about circuit purpose in
4553 connection_ap_expire_building(). Fixes bug 8477; bugfix on
4556 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
4557 - If we encounter a write failure on a SOCKS connection before we
4558 finish our SOCKS handshake, don't warn that we closed the
4559 connection before we could send a SOCKS reply. Fixes bug 8427;
4560 bugfix on 0.1.0.1-rc.
4561 - Correctly recognize that [::1] is a loopback address. Fixes
4562 bug 8377; bugfix on 0.2.1.3-alpha.
4563 - Fix a directory authority warn caused when we have a large amount
4564 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
4565 - Don't log inappropriate heartbeat messages when hibernating: a
4566 hibernating node is _expected_ to drop out of the consensus,
4567 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
4568 bugfix on 0.2.3.1-alpha.
4569 - Don't complain about bootstrapping problems while hibernating.
4570 These complaints reflect a general code problem, but not one
4571 with any problematic effects (no connections are actually
4572 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
4574 o Documentation fixes:
4575 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
4576 names match. Fixes bug 7768.
4577 - Make the torify manpage no longer refer to tsocks; torify hasn't
4578 supported tsocks since 0.2.3.14-alpha.
4579 - Make the tor manpage no longer reference tsocks.
4580 - Fix the GeoIPExcludeUnknown documentation to refer to
4581 ExcludeExitNodes rather than the currently nonexistent
4582 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
4585 - The tor-tsocks.conf is no longer distributed or installed. We
4586 recommend that tsocks users use torsocks instead. Resolves
4590 Changes in version 0.2.4.11-alpha - 2013-03-11
4591 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
4592 more robust, makes hidden service authentication work again, and
4593 resolves a DPI fingerprint for Tor's SSL transport.
4595 o Major features (directory authorities):
4596 - Directory authorities now support a new consensus method (17)
4597 where they cap the published bandwidth of servers for which
4598 insufficient bandwidth measurements exist. Fixes part of bug 2286.
4599 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
4600 serve any v2 directory information. Now we can test disabling the
4601 old deprecated v2 directory format, and see whether doing so has
4602 any effect on network load. Begins to fix bug 6783.
4603 - Directory authorities now include inside each vote a statement of
4604 the performance thresholds they used when assigning flags.
4605 Implements ticket 8151.
4607 o Major bugfixes (directory authorities):
4608 - Stop marking every relay as having been down for one hour every
4609 time we restart a directory authority. These artificial downtimes
4610 were messing with our Stable and Guard flag calculations. Fixes
4611 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
4613 o Major bugfixes (hidden services):
4614 - Allow hidden service authentication to succeed again. When we
4615 refactored the hidden service introduction code back
4616 in 0.2.4.1-alpha, we didn't update the code that checks
4617 whether authentication information is present, causing all
4618 authentication checks to return "false". Fix for bug 8207; bugfix
4619 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
4621 o Minor features (relays, bridges):
4622 - Make bridge relays check once a minute for whether their IP
4623 address has changed, rather than only every 15 minutes. Resolves
4625 - Refactor resolve_my_address() so it returns the method by which we
4626 decided our public IP address (explicitly configured, resolved from
4627 explicit hostname, guessed from interfaces, learned by gethostname).
4628 Now we can provide more helpful log messages when a relay guesses
4629 its IP address incorrectly (e.g. due to unexpected lines in
4630 /etc/hosts). Resolves ticket 2267.
4631 - Teach bridge-using clients to avoid 0.2.2 bridges when making
4632 microdescriptor-related dir requests, and only fall back to normal
4633 descriptors if none of their bridges can handle microdescriptors
4634 (as opposed to the fix in ticket 4013, which caused them to fall
4635 back to normal descriptors if *any* of their bridges preferred
4636 them). Resolves ticket 4994.
4637 - Randomize the lifetime of our SSL link certificate, so censors can't
4638 use the static value for filtering Tor flows. Resolves ticket 8443;
4639 related to ticket 4014 which was included in 0.2.2.33.
4640 - Support a new version of the link protocol that allows 4-byte circuit
4641 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
4642 a possible resource exhaustion issue. Closes ticket 7351; implements
4645 o Minor features (portability):
4646 - Tweak the curve25519-donna*.c implementations to tolerate systems
4647 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
4648 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
4649 the signs of types during autoconf. This is better than our old
4650 approach, which didn't work when cross-compiling.
4651 - Detect the sign of enum values, rather than assuming that MSC is the
4652 only compiler where enum types are all signed. Fixes bug 7727;
4653 bugfix on 0.2.4.10-alpha.
4655 o Minor features (other):
4656 - Say "KBytes" rather than "KB" in the man page (for various values
4657 of K), to further reduce confusion about whether Tor counts in
4658 units of memory or fractions of units of memory. Resolves ticket 7054.
4659 - Clear the high bit on curve25519 public keys before passing them to
4660 our backend, in case we ever wind up using a backend that doesn't do
4661 so itself. If we used such a backend, and *didn't* clear the high bit,
4662 we could wind up in a situation where users with such backends would
4663 be distinguishable from users without. Fixes bug 8121; bugfix on
4665 - Update to the March 6 2013 Maxmind GeoLite Country database.
4667 o Minor bugfixes (clients):
4668 - When we receive a RELAY_END cell with the reason DONE, or with no
4669 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
4670 status as "connection refused". Previously we reported these cases
4671 as success but then immediately closed the connection. Fixes bug
4672 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
4673 - Downgrade an assertion in connection_ap_expire_beginning to an
4674 LD_BUG message. The fix for bug 8024 should prevent this message
4675 from displaying, but just in case, a warn that we can diagnose
4676 is better than more assert crashes. Fixes bug 8065; bugfix on
4678 - Lower path use bias thresholds to .80 for notice and .60 for warn.
4679 Also make the rate limiting flags for the path use bias log messages
4680 independent from the original path bias flags. Fixes bug 8161;
4681 bugfix on 0.2.4.10-alpha.
4683 o Minor bugfixes (relays):
4684 - Stop trying to resolve our hostname so often (e.g. every time we
4685 think about doing a directory fetch). Now we reuse the cached
4686 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
4687 and 2410 (bugfix on 0.1.2.2-alpha).
4688 - Stop sending a stray "(null)" in some cases for the server status
4689 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
4691 - When choosing which stream on a formerly stalled circuit to wake
4692 first, make better use of the platform's weak RNG. Previously,
4693 we had been using the % ("modulo") operator to try to generate a
4694 1/N chance of picking each stream, but this behaves badly with
4695 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
4697 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
4698 Irix's random() only return 15 bits; Solaris's random() returns more
4699 bits but its RAND_MAX says it only returns 15, and so on. Motivated
4700 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
4702 o Minor bugfixes (directory authorities):
4703 - Directory authorities now use less space when formatting identical
4704 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
4707 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
4708 - Avoid leaking memory if we fail to compute a consensus signature
4709 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
4710 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
4712 - Fix a memory leak during safe-cookie controller authentication.
4713 Bugfix on 0.2.3.13-alpha.
4714 - Avoid memory leak of IPv6 policy content if we fail to format it into
4715 a router descriptor. Bugfix on 0.2.4.7-alpha.
4717 o Minor bugfixes (other code correctness issues):
4718 - Avoid a crash if we fail to generate an extrainfo descriptor.
4719 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
4721 - When detecting the largest possible file descriptor (in order to
4722 close all file descriptors when launching a new program), actually
4723 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
4724 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
4726 - Fix a copy-and-paste error when adding a missing A1 to a routerset
4727 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
4728 Bugfix on 0.2.4.10-alpha.
4729 - Fix an impossible-to-trigger integer overflow when estimating how
4730 long our onionskin queue would take. (This overflow would require us
4731 to accept 4 million onionskins before processing 100 of them.) Fixes
4732 bug 8210; bugfix on 0.2.4.10-alpha.
4734 o Code simplification and refactoring:
4735 - Add a wrapper function for the common "log a message with a
4739 Changes in version 0.2.4.10-alpha - 2013-02-04
4740 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
4741 certain attacks that flood the network with relays; changes the queue
4742 for circuit create requests from a sized-based limit to a time-based
4743 limit; resumes building with MSVC on Windows; and fixes a wide variety
4746 o Major bugfixes (directory authority):
4747 - When computing directory thresholds, ignore any rejected-as-sybil
4748 nodes during the computation so that they can't influence Fast,
4749 Guard, etc. (We should have done this for proposal 109.) Fixes
4751 - When marking a node as a likely sybil, reset its uptime metrics
4752 to zero, so that it cannot time towards getting marked as Guard,
4753 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
4757 - When a TLS write is partially successful but incomplete, remember
4758 that the flushed part has been flushed, and notice that bytes were
4759 actually written. Reported and fixed pseudonymously. Fixes bug
4760 7708; bugfix on Tor 0.1.0.5-rc.
4761 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
4762 ID: these could be used to create unexpected streams and circuits
4763 which would count as "present" to some parts of Tor but "absent"
4764 to others, leading to zombie circuits and streams or to a bandwidth
4765 denial-of-service. Fixes bug 7889; bugfix on every released version
4766 of Tor. Reported by "oftc_must_be_destroyed".
4767 - Rename all macros in our local copy of queue.h to begin with "TOR_".
4768 This change seems the only good way to permanently prevent conflicts
4769 with queue.h on various operating systems. Fixes bug 8107; bugfix
4772 o Major features (relay):
4773 - Instead of limiting the number of queued onionskins (aka circuit
4774 create requests) to a fixed, hard-to-configure number, we limit
4775 the size of the queue based on how many we expect to be able to
4776 process in a given amount of time. We estimate the time it will
4777 take to process an onionskin based on average processing time
4778 of previous onionskins. Closes ticket 7291. You'll never have to
4779 configure MaxOnionsPending again.
4781 o Major features (portability):
4782 - Resume building correctly with MSVC and Makefile.nmake. This patch
4783 resolves numerous bugs and fixes reported by ultramage, including
4784 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
4785 - Make the ntor and curve25519 code build correctly with MSVC.
4786 Fix on 0.2.4.8-alpha.
4789 - When directory authorities are computing thresholds for flags,
4790 never let the threshold for the Fast flag fall below 4096
4791 bytes. Also, do not consider nodes with extremely low bandwidths
4792 when deciding thresholds for various directory flags. This change
4793 should raise our threshold for Fast relays, possibly in turn
4794 improving overall network performance; see ticket 1854. Resolves
4796 - The Tor client now ignores sub-domain components of a .onion
4797 address. This change makes HTTP "virtual" hosting
4798 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
4799 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
4800 hosted on the same hidden service. Implements proposal 204.
4801 - We compute the overhead from passing onionskins back and forth to
4802 cpuworkers, and report it when dumping statistics in response to
4803 SIGUSR1. Supports ticket 7291.
4805 o Minor features (path selection):
4806 - When deciding whether we have enough descriptors to build circuits,
4807 instead of looking at raw relay counts, look at which fraction
4808 of (bandwidth-weighted) paths we're able to build. This approach
4809 keeps clients from building circuits if their paths are likely to
4810 stand out statistically. The default fraction of paths needed is
4811 taken from the consensus directory; you can override it with the
4812 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
4813 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
4814 and we have GeoIP information, also exclude all nodes with unknown
4815 countries "??" and "A1". This behavior is controlled by the
4816 new GeoIPExcludeUnknown option: you can make such nodes always
4817 excluded with "GeoIPExcludeUnknown 1", and disable the feature
4818 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
4819 gets you the default behavior. Implements feature 7706.
4820 - Path Use Bias: Perform separate accounting for successful circuit
4821 use. Keep separate statistics on stream attempt rates versus stream
4822 success rates for each guard. Provide configurable thresholds to
4823 determine when to emit log messages or disable use of guards that
4824 fail too many stream attempts. Resolves ticket 7802.
4826 o Minor features (log messages):
4827 - When learning a fingerprint for a bridge, log its corresponding
4828 transport type. Implements ticket 7896.
4829 - Improve the log message when "Bug/attack: unexpected sendme cell
4830 from client" occurs, to help us track bug 8093.
4833 - Remove a couple of extraneous semicolons that were upsetting the
4834 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4835 bugfix on 0.2.2.1-alpha.
4836 - Remove a source of rounding error during path bias count scaling;
4837 don't count cannibalized circuits as used for path bias until we
4838 actually try to use them; and fix a circuit_package_relay_cell()
4839 warning message about n_chan==NULL. Fixes bug 7802.
4840 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
4841 actually link against nacl when we're configured to use it. Fixes
4842 bug 7972; bugfix on 0.2.4.8-alpha.
4843 - Compile correctly with the --disable-curve25519 option. Fixes
4844 bug 8153; bugfix on 0.2.4.8-alpha.
4846 o Build improvements:
4847 - Do not report status verbosely from autogen.sh unless the -v flag
4848 is specified. Fixes issue 4664. Patch from Onizuka.
4849 - Replace all calls to snprintf() outside of src/ext with
4850 tor_snprintf(). Also remove the #define to replace snprintf with
4851 _snprintf on Windows; they have different semantics, and all of
4852 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
4853 - Try to detect if we are ever building on a platform where
4854 memset(...,0,...) does not set the value of a double to 0.0. Such
4855 platforms are permitted by the C standard, though in practice
4856 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
4857 currently support them, but it's better to detect them and fail
4858 than to perform erroneously.
4861 - Stop exporting estimates of v2 and v3 directory traffic shares
4862 in extrainfo documents. They were unneeded and sometimes inaccurate.
4863 Also stop exporting any v2 directory request statistics. Resolves
4865 - Drop support for detecting and warning about versions of Libevent
4866 before 1.3e. Nothing reasonable ships with them any longer;
4867 warning the user about them shouldn't be needed. Resolves ticket
4870 o Code simplifications and refactoring:
4871 - Rename "isin" functions to "contains", for grammar. Resolves
4873 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
4874 with the natural logarithm function from the system libm. Resolves
4878 Changes in version 0.2.4.9-alpha - 2013-01-15
4879 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
4883 - Fix backward compatibility logic when receiving an embedded ntor
4884 handshake tunneled in a CREATE cell. This clears up the "Bug:
4885 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
4889 Changes in version 0.2.4.8-alpha - 2013-01-14
4890 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
4891 risks, adds a new stronger and faster circuit handshake, and offers
4892 stronger and faster link encryption when both sides support it.
4895 - Preliminary support for directory guards (proposal 207): when
4896 possible, clients now use their entry guards for non-anonymous
4897 directory requests. This can help prevent client enumeration. Note
4898 that this behavior only works when we have a usable consensus
4899 directory, and when options about what to download are more or less
4900 standard. In the future we should re-bootstrap from our guards,
4901 rather than re-bootstrapping from the preconfigured list of
4902 directory sources that ships with Tor. Resolves ticket 6526.
4903 - Tor relays and clients now support a better CREATE/EXTEND cell
4904 format, allowing the sender to specify multiple address, identity,
4905 and handshake types. Implements Robert Ransom's proposal 200;
4908 o Major features (new circuit handshake):
4909 - Tor now supports a new circuit extension handshake designed by Ian
4910 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
4911 circuit extension handshake, later called "TAP", was a bit slow
4912 (especially on the relay side), had a fragile security proof, and
4913 used weaker keys than we'd now prefer. The new circuit handshake
4914 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
4915 function, making it significantly more secure than the older
4916 handshake, and significantly faster. Tor can use one of two built-in
4917 pure-C curve25519-donna implementations by Adam Langley, or it
4918 can link against the "nacl" library for a tuned version if present.
4920 The built-in version is very fast for 64-bit systems when building
4921 with GCC. The built-in 32-bit version is still faster than the
4922 old TAP protocol, but using libnacl is better on most such hosts.
4924 Clients don't currently use this protocol by default, since
4925 comparatively few clients support it so far. To try it, set
4926 UseNTorHandshake to 1.
4928 Implements proposal 216; closes ticket 7202.
4930 o Major features (better link encryption):
4931 - Relays can now enable the ECDHE TLS ciphersuites when available
4932 and appropriate. These ciphersuites let us negotiate forward-secure
4933 TLS secret keys more safely and more efficiently than with our
4934 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
4935 public relays prefer the (faster) P224 group, and bridges prefer
4936 the (more common) P256 group; you can override this with the
4939 Enabling these ciphers was a little tricky, since for a long time,
4940 clients had been claiming to support them without actually doing
4941 so, in order to foil fingerprinting. But with the client-side
4942 implementation of proposal 198 in 0.2.3.17-beta, clients can now
4943 match the ciphers from recent Firefox versions *and* list the
4944 ciphers they actually mean, so relays can believe such clients
4945 when they advertise ECDHE support in their TLS ClientHello messages.
4947 This feature requires clients running 0.2.3.17-beta or later,
4948 and requires both sides to be running OpenSSL 1.0.0 or later
4949 with ECC support. OpenSSL 1.0.1, with the compile-time option
4950 "enable-ec_nistp_64_gcc_128", is highly recommended.
4952 Implements the relay side of proposal 198; closes ticket 7200.
4955 - Avoid crashing when, as a relay without IPv6-exit support, a
4956 client insists on getting an IPv6 address or nothing. Fixes bug
4957 7814; bugfix on 0.2.4.7-alpha.
4960 - Improve circuit build timeout handling for hidden services.
4961 In particular: adjust build timeouts more accurately depending
4962 upon the number of hop-RTTs that a particular circuit type
4963 undergoes. Additionally, launch intro circuits in parallel
4964 if they timeout, and take the first one to reply as valid.
4965 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
4966 separate error codes; or at least, don't break for that reason.
4967 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
4968 - Update to the January 2 2013 Maxmind GeoLite Country database.
4970 o Minor features (testing):
4971 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
4972 (P-256) Diffie-Hellman handshakes to src/or/bench.
4973 - Add benchmark functions to test onion handshake performance.
4975 o Minor features (path bias detection):
4976 - Alter the Path Bias log messages to be more descriptive in terms
4977 of reporting timeouts and other statistics.
4978 - Create three levels of Path Bias log messages, as opposed to just
4979 two. These are configurable via consensus as well as via the torrc
4980 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
4981 The default values are 0.70, 0.50, and 0.30 respectively.
4982 - Separate the log message levels from the decision to drop guards,
4983 which also is available via torrc option PathBiasDropGuards.
4984 PathBiasDropGuards still defaults to 0 (off).
4985 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
4986 in combination with PathBiasExtremeRate.
4987 - Increase the default values for PathBiasScaleThreshold and
4988 PathBiasCircThreshold from (200, 20) to (300, 150).
4989 - Add in circuit usage accounting to path bias. If we try to use a
4990 built circuit but fail for any reason, it counts as path bias.
4991 Certain classes of circuits where the adversary gets to pick your
4992 destination node are exempt from this accounting. Usage accounting
4993 can be specifically disabled via consensus parameter or torrc.
4994 - Convert all internal path bias state to double-precision floating
4995 point, to avoid roundoff error and other issues.
4996 - Only record path bias information for circuits that have completed
4997 *two* hops. Assuming end-to-end tagging is the attack vector, this
4998 makes us more resilient to ambient circuit failure without any
4999 detection capability loss.
5001 o Minor bugfixes (log messages):
5002 - Rate-limit the "No circuits are opened. Relaxed timeout for a
5003 circuit with channel state open..." message to once per hour to
5004 keep it from filling the notice logs. Mitigates bug 7799 but does
5005 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
5006 - Avoid spurious warnings when configuring multiple client ports of
5007 which only some are nonlocal. Previously, we had claimed that some
5008 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
5011 o Code simplifications and refactoring:
5012 - Get rid of a couple of harmless clang warnings, where we compared
5013 enums to ints. These warnings are newly introduced in clang 3.2.
5014 - Split the onion.c file into separate modules for the onion queue
5015 and the different handshakes it supports.
5016 - Remove the marshalling/unmarshalling code for sending requests to
5017 cpuworkers over a socket, and instead just send structs. The
5018 recipient will always be the same Tor binary as the sender, so
5019 any encoding is overkill.
5022 Changes in version 0.2.4.7-alpha - 2012-12-24
5023 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
5024 directory mirrors for more robust bootstrapping; fixes more issues where
5025 clients with changing network conditions refuse to make any circuits;
5026 adds initial support for exiting to IPv6 addresses; resumes being able
5027 to update our GeoIP database, and includes the geoip6 file this time;
5028 turns off the client-side DNS cache by default due to privacy risks;
5029 and fixes a variety of other issues.
5031 o Major features (client resilience):
5032 - Add a new "FallbackDir" torrc option to use when we can't use
5033 a directory mirror from the consensus (either because we lack a
5034 consensus, or because they're all down). Currently, all authorities
5035 are fallbacks by default, and there are no other default fallbacks,
5036 but that will change. This option will allow us to give clients a
5037 longer list of servers to try to get a consensus from when first
5038 connecting to the Tor network, and thereby reduce load on the
5039 directory authorities. Implements proposal 206, "Preconfigured
5040 directory sources for bootstrapping". We also removed the old
5041 "FallbackNetworkstatus" option, since we never got it working well
5042 enough to use it. Closes bug 572.
5043 - If we have no circuits open, use a relaxed timeout (the
5044 95-percentile cutoff) until a circuit succeeds. This heuristic
5045 should allow Tor to succeed at building circuits even when the
5046 network connection drastically changes. Should help with bug 3443.
5048 o Major features (IPv6):
5049 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5050 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5051 exit policy reads as you would like: the address * applies to all
5052 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5053 addresses only. On the client side, you'll need to wait until the
5054 authorities have upgraded, wait for enough exits to support IPv6,
5055 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
5056 ticket 5547, implements proposal 117 as revised in proposal 208.
5058 We DO NOT recommend that clients with actual anonymity needs start
5059 using IPv6 over Tor yet, since not enough exits support it yet.
5061 o Major features (geoip database):
5062 - Maxmind began labelling Tor relays as being in country "A1",
5063 which breaks by-country node selection inside Tor. Now we use a
5064 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5065 file with real country codes. This script fixes about 90% of "A1"
5066 entries automatically and uses manual country code assignments to
5067 fix the remaining 10%. See src/config/README.geoip for details.
5068 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
5069 Country database, as modified above.
5071 o Major bugfixes (client-side DNS):
5072 - Turn off the client-side DNS cache by default. Updating and using
5073 the DNS cache is now configurable on a per-client-port
5074 level. SOCKSPort, DNSPort, etc lines may now contain
5075 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5076 cache these types of DNS answers when we receive them from an
5077 exit node in response to an application request on this port, and
5078 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5079 cached DNS answers of these types, we shouldn't use them. It's
5080 potentially risky to use cached DNS answers at the client, since
5081 doing so can indicate to one exit what answers we've gotten
5082 for DNS lookups in the past. With IPv6, this becomes especially
5083 problematic. Using cached DNS answers for requests on the same
5084 circuit would present less linkability risk, since all traffic
5085 on a circuit is already linkable, but it would also provide
5086 little performance benefit: the exit node caches DNS replies
5087 too. Implements a simplified version of Proposal 205. Implements
5090 o Major bugfixes (other):
5091 - Alter circuit build timeout measurement to start at the point
5092 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5093 initialization). This should make our timeout measurements more
5094 uniform. Previously, we were sometimes including ORconn setup time
5095 in our circuit build time measurements. Should resolve bug 3443.
5096 - Fix an assertion that could trigger in hibernate_go_dormant() when
5097 closing an or_connection_t: call channel_mark_for_close() rather
5098 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
5100 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
5101 7655; bugfix on 0.2.4.6-alpha.
5104 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5105 operators select the address where their pluggable transports will
5106 listen for connections. Resolves ticket 7013.
5107 - Allow an optional $ before the node identity digest in the
5108 controller command GETINFO ns/id/<identity>, for consistency with
5109 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5110 - Log packaged cell fullness as part of the heartbeat message.
5111 Diagnosis to try to determine the extent of bug 7743.
5113 o Minor features (IPv6):
5114 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5115 prefer to hand out virtual IPv6 addresses, since there are more of
5116 them and we can't run out. To override this behavior and make IPv4
5117 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5118 or DNSPort you're using for resolving. Implements ticket 7571.
5119 - AutomapHostsOnResolve responses are now randomized, to avoid
5120 annoying situations where Tor is restarted and applications
5121 connect to the wrong addresses.
5122 - Never try more than 1000 times to pick a new virtual address when
5123 AutomapHostsOnResolve is set. That's good enough so long as we
5124 aren't close to handing out our entire virtual address space;
5125 if you're getting there, it's best to switch to IPv6 virtual
5129 - The ADDRMAP command can no longer generate an ill-formed error
5130 code on a failed MAPADDRESS. It now says "internal" rather than
5131 an English sentence fragment with spaces in the middle. Bugfix on
5133 - Fix log messages and comments to avoid saying "GMT" when we mean
5134 "UTC". Fixes bug 6113.
5135 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5137 - Fix a crash when debugging unit tests on Windows: deallocate a
5138 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
5139 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
5142 - The DirServer option is now DirAuthority, for consistency with
5143 current naming patterns. You can still use the old DirServer form.
5145 o Code simplification and refactoring:
5146 - Move the client-side address-map/virtual-address/DNS-cache code
5147 out of connection_edge.c into a new addressmap.c module.
5148 - Remove unused code for parsing v1 directories and "running routers"
5149 documents. Fixes bug 6887.
5152 Changes in version 0.2.3.25 - 2012-11-19
5153 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
5154 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
5155 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
5156 programmer, and friend. Unstinting in his dedication to the cause of
5157 freedom, he inspired and helped many of us as we began our work on
5158 anonymity, and inspires us still. Please honor his memory by writing
5159 software to protect people's freedoms, and by helping others to do so.
5161 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
5162 significantly reduced directory overhead (via microdescriptors),
5163 enormous crypto performance improvements for fast relays on new
5164 enough hardware, a new v3 TLS handshake protocol that can better
5165 resist fingerprinting, support for protocol obfuscation plugins (aka
5166 pluggable transports), better scalability for hidden services, IPv6
5167 support for bridges, performance improvements like allowing clients
5168 to skip the first round-trip on the circuit ("optimistic data") and
5169 refilling token buckets more often, a new "stream isolation" design
5170 to isolate different applications on different circuits, and many
5171 stability, security, and privacy fixes.
5174 - Tor tries to wipe potentially sensitive data after using it, so
5175 that if some subsequent security failure exposes Tor's memory,
5176 the damage will be limited. But we had a bug where the compiler
5177 was eliminating these wipe operations when it decided that the
5178 memory was no longer visible to a (correctly running) program,
5179 hence defeating our attempt at defense in depth. We fix that
5180 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5181 is unlikely to optimize away. Future versions of Tor may use
5182 a less ridiculously heavy approach for this. Fixes bug 7352.
5183 Reported in an article by Andrey Karpov.
5186 - Fix a harmless bug when opting against publishing a relay descriptor
5187 because DisableNetwork is set. Fixes bug 7464; bugfix on
5191 Changes in version 0.2.4.6-alpha - 2012-11-13
5192 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
5193 makes our defense-in-depth memory wiping more reliable, and begins to
5194 count IPv6 addresses in bridge statistics,
5197 - Fix an assertion failure that could occur when closing a connection
5198 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
5200 - Tor tries to wipe potentially sensitive data after using it, so
5201 that if some subsequent security failure exposes Tor's memory,
5202 the damage will be limited. But we had a bug where the compiler
5203 was eliminating these wipe operations when it decided that the
5204 memory was no longer visible to a (correctly running) program,
5205 hence defeating our attempt at defense in depth. We fix that
5206 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5207 is unlikely to optimize away. Future versions of Tor may use
5208 a less ridiculously heavy approach for this. Fixes bug 7352.
5209 Reported in an article by Andrey Karpov.
5212 - Add GeoIP database for IPv6 addresses. The new config option
5214 - Bridge statistics now count bridge clients connecting over IPv6:
5215 bridge statistics files now list "bridge-ip-versions" and
5216 extra-info documents list "geoip6-db-digest". The control protocol
5217 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
5218 implementation by "shkoo", addressing ticket 5055.
5221 - Warn when we are binding low ports when hibernation is enabled;
5222 previously we had warned when we were _advertising_ low ports with
5223 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
5224 - Fix a harmless bug when opting against publishing a relay descriptor
5225 because DisableNetwork is set. Fixes bug 7464; bugfix on
5227 - Add warning message when a managed proxy dies during configuration.
5228 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
5229 - Fix a linking error when building tor-fw-helper without miniupnp.
5230 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
5231 - Check for closing an or_connection_t without going through correct
5232 channel functions; emit a warning and then call
5233 connection_or_close_for_error() so we don't assert as in bugs 7212
5235 - Compile correctly on compilers without C99 designated initializer
5236 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
5237 - Avoid a possible assert that can occur when channel_send_destroy() is
5238 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
5239 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
5240 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
5241 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
5242 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
5244 o Code simplification and refactoring:
5245 - Start using OpenBSD's implementation of queue.h, so that we don't
5246 need to hand-roll our own pointer and list structures whenever we
5247 need them. (We can't rely on a sys/queue.h, since some operating
5248 systems don't have them, and the ones that do have them don't all
5249 present the same extensions.)
5252 Changes in version 0.2.4.5-alpha - 2012-10-25
5253 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
5254 two important security vulnerabilities that could lead to remotely
5255 triggerable relay crashes, fix a major bug that was preventing clients
5256 from choosing suitable exit nodes, and refactor some of our code.
5258 o Major bugfixes (security, also in 0.2.3.24-rc):
5259 - Fix a group of remotely triggerable assertion failures related to
5260 incorrect link protocol negotiation. Found, diagnosed, and fixed
5261 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5263 - Fix a denial of service attack by which any directory authority
5264 could crash all the others, or by which a single v2 directory
5265 authority could crash everybody downloading v2 directory
5266 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5268 o Major bugfixes (also in 0.2.3.24-rc):
5269 - When parsing exit policy summaries from microdescriptors, we had
5270 previously been ignoring the last character in each one, so that
5271 "accept 80,443,8080" would be treated by clients as indicating
5272 a node that allows access to ports 80, 443, and 808. That would
5273 lead to clients attempting connections that could never work,
5274 and ignoring exit nodes that would support their connections. Now
5275 clients parse these exit policy summaries correctly. Fixes bug 7192;
5276 bugfix on 0.2.3.1-alpha.
5278 o Minor bugfixes (also in 0.2.3.24-rc):
5279 - Clients now consider the ClientRejectInternalAddresses config option
5280 when using a microdescriptor consensus stanza to decide whether
5281 an exit relay would allow exiting to an internal address. Fixes
5282 bug 7190; bugfix on 0.2.3.1-alpha.
5285 - Only disable TLS session ticket support when running as a TLS
5286 server. Now clients will blend better with regular Firefox
5287 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
5289 o Code simplification and refactoring:
5290 - Start using OpenBSD's implementation of queue.h (originally by
5292 - Move the entry node code from circuitbuild.c to its own file.
5293 - Move the circuit build timeout tracking code from circuitbuild.c
5297 Changes in version 0.2.3.24-rc - 2012-10-25
5298 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
5299 could lead to remotely triggerable relay crashes, and fixes
5300 a major bug that was preventing clients from choosing suitable exit
5303 o Major bugfixes (security):
5304 - Fix a group of remotely triggerable assertion failures related to
5305 incorrect link protocol negotiation. Found, diagnosed, and fixed
5306 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5308 - Fix a denial of service attack by which any directory authority
5309 could crash all the others, or by which a single v2 directory
5310 authority could crash everybody downloading v2 directory
5311 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5314 - When parsing exit policy summaries from microdescriptors, we had
5315 previously been ignoring the last character in each one, so that
5316 "accept 80,443,8080" would be treated by clients as indicating
5317 a node that allows access to ports 80, 443, and 808. That would
5318 lead to clients attempting connections that could never work,
5319 and ignoring exit nodes that would support their connections. Now
5320 clients parse these exit policy summaries correctly. Fixes bug 7192;
5321 bugfix on 0.2.3.1-alpha.
5324 - Clients now consider the ClientRejectInternalAddresses config option
5325 when using a microdescriptor consensus stanza to decide whether
5326 an exit relay would allow exiting to an internal address. Fixes
5327 bug 7190; bugfix on 0.2.3.1-alpha.
5330 Changes in version 0.2.4.4-alpha - 2012-10-20
5331 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
5332 vulnerability introduced by a change in OpenSSL, fixes a remotely
5333 triggerable assert, and adds new channel_t and circuitmux_t abstractions
5334 that will make it easier to test new connection transport and cell
5335 scheduling algorithms.
5337 o New directory authorities (also in 0.2.3.23-rc):
5338 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5339 authority. Closes ticket 5749.
5341 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
5342 - Disable TLS session tickets. OpenSSL's implementation was giving
5343 our TLS session keys the lifetime of our TLS context objects, when
5344 perfect forward secrecy would want us to discard anything that
5345 could decrypt a link connection as soon as the link connection
5346 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5347 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5348 - Discard extraneous renegotiation attempts once the V3 link
5349 protocol has been initiated. Failure to do so left us open to
5350 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5351 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5353 o Internal abstraction features:
5354 - Introduce new channel_t abstraction between circuits and
5355 or_connection_t to allow for implementing alternate OR-to-OR
5356 transports. A channel_t is an abstract object which can either be a
5357 cell-bearing channel, which is responsible for authenticating and
5358 handshaking with the remote OR and transmitting cells to and from
5359 it, or a listening channel, which spawns new cell-bearing channels
5360 at the request of remote ORs. Implements part of ticket 6465.
5361 - Also new is the channel_tls_t subclass of channel_t, adapting it
5362 to the existing or_connection_t code. The V2/V3 protocol handshaking
5363 code which formerly resided in command.c has been moved below the
5364 channel_t abstraction layer and may be found in channeltls.c now.
5365 Implements the rest of ticket 6465.
5366 - Introduce new circuitmux_t storing the queue of circuits for
5367 a channel; this encapsulates and abstracts the queue logic and
5368 circuit selection policy, and allows the latter to be overridden
5369 easily by switching out a policy object. The existing EWMA behavior
5370 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5372 o Required libraries:
5373 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5374 strongly recommended.
5377 - Warn users who run hidden services on a Tor client with
5378 UseEntryGuards disabled that their hidden services will be
5379 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5380 attack which motivated Tor to support entry guards in the first
5381 place). Resolves ticket 6889.
5382 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5383 dhill. Resolves ticket 6982.
5384 - Option OutboundBindAddress can be specified multiple times and
5385 accepts IPv6 addresses. Resolves ticket 6876.
5387 o Minor bugfixes (also in 0.2.3.23-rc):
5388 - Don't serve or accept v2 hidden service descriptors over a
5389 relay's DirPort. It's never correct to do so, and disabling it
5390 might make it more annoying to exploit any bugs that turn up in the
5391 descriptor-parsing code. Fixes bug 7149.
5392 - Fix two cases in src/or/transports.c where we were calling
5393 fmt_addr() twice in a parameter list. Bug found by David
5394 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5395 - Fix memory leaks whenever we logged any message about the "path
5396 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5397 - When relays refuse a "create" cell because their queue of pending
5398 create cells is too big (typically because their cpu can't keep up
5399 with the arrival rate), send back reason "resource limit" rather
5400 than reason "internal", so network measurement scripts can get a
5401 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
5404 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
5405 - Free some more still-in-use memory at exit, to make hunting for
5406 memory leaks easier. Resolves bug 7029.
5407 - When a Tor client gets a "truncated" relay cell, the first byte of
5408 its payload specifies why the circuit was truncated. We were
5409 ignoring this 'reason' byte when tearing down the circuit, resulting
5410 in the controller not being told why the circuit closed. Now we
5411 pass the reason from the truncated cell to the controller. Bugfix
5412 on 0.1.2.3-alpha; fixes bug 7039.
5413 - Downgrade "Failed to hand off onionskin" messages to "debug"
5414 severity, since they're typically redundant with the "Your computer
5415 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
5416 - Make clients running with IPv6 bridges connect over IPv6 again,
5417 even without setting new config options ClientUseIPv6 and
5418 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
5419 - Use square brackets around IPv6 addresses in numerous places
5420 that needed them, including log messages, HTTPS CONNECT proxy
5421 requests, TransportProxy statefile entries, and pluggable transport
5422 extra-info lines. Fixes bug 7011; patch by David Fifield.
5424 o Code refactoring and cleanup:
5425 - Source files taken from other packages now reside in src/ext;
5426 previously they were scattered around the rest of Tor.
5427 - Avoid use of reserved identifiers in our C code. The C standard
5428 doesn't like us declaring anything that starts with an
5429 underscore, so let's knock it off before we get in trouble. Fix
5430 for bug 1031; bugfix on the first Tor commit.
5433 Changes in version 0.2.3.23-rc - 2012-10-20
5434 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
5435 vulnerability introduced by a change in OpenSSL, and fixes a variety
5436 of smaller bugs in preparation for the release.
5438 o New directory authorities:
5439 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5440 authority. Closes ticket 5749.
5442 o Major bugfixes (security/privacy):
5443 - Disable TLS session tickets. OpenSSL's implementation was giving
5444 our TLS session keys the lifetime of our TLS context objects, when
5445 perfect forward secrecy would want us to discard anything that
5446 could decrypt a link connection as soon as the link connection
5447 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5448 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5449 - Discard extraneous renegotiation attempts once the V3 link
5450 protocol has been initiated. Failure to do so left us open to
5451 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5452 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5455 - Fix a possible crash bug when checking for deactivated circuits
5456 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5457 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5459 o Minor bugfixes (on 0.2.3.x):
5460 - Fix two cases in src/or/transports.c where we were calling
5461 fmt_addr() twice in a parameter list. Bug found by David
5462 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5463 - Convert an assert in the pathbias code to a log message. The assert
5464 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5465 bugfix on 0.2.3.17-beta.
5466 - Fix memory leaks whenever we logged any message about the "path
5467 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5469 o Minor bugfixes (on 0.2.2.x and earlier):
5470 - Don't serve or accept v2 hidden service descriptors over a relay's
5471 DirPort. It's never correct to do so, and disabling it might
5472 make it more annoying to exploit any bugs that turn up in the
5473 descriptor-parsing code. Fixes bug 7149.
5474 - When relays refuse a "create" cell because their queue of pending
5475 create cells is too big (typically because their cpu can't keep up
5476 with the arrival rate), send back reason "resource limit" rather
5477 than reason "internal", so network measurement scripts can get a
5478 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
5479 - Correct file sizes when reading binary files on Cygwin, to avoid
5480 a bug where Tor would fail to read its state file. Fixes bug 6844;
5481 bugfix on 0.1.2.7-alpha.
5482 - Avoid undefined behavior when parsing the list of supported
5483 rendezvous/introduction protocols in a hidden service descriptor.
5484 Previously, Tor would have confused (as-yet-unused) protocol version
5485 numbers greater than 32 with lower ones on many platforms. Fixes
5486 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5488 o Documentation fixes:
5489 - Clarify that hidden services are TCP only. Fixes bug 6024.
5492 Changes in version 0.2.4.3-alpha - 2012-09-22
5493 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
5494 assertion, resumes letting relays test reachability of their DirPort,
5495 and cleans up a bunch of smaller bugs.
5498 - Fix an assertion failure in tor_timegm() that could be triggered
5499 by a badly formatted directory object. Bug found by fuzzing with
5500 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5503 - Fix a possible crash bug when checking for deactivated circuits
5504 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5505 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5506 - Allow routers to detect that their own DirPorts are running. When
5507 we removed support for versions_supports_begindir, we also
5508 accidentally removed the mechanism we used to self-test our
5509 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
5510 bugfix on 0.2.4.2-alpha.
5512 o Security features:
5513 - Switch to a completely time-invariant approach for picking nodes
5514 weighted by bandwidth. Our old approach would run through the
5515 part of the loop after it had made its choice slightly slower
5516 than it ran through the part of the loop before it had made its
5517 choice. Addresses ticket 6538.
5518 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
5519 by tor2web clients allows hidden services to identify tor2web
5520 clients through their repeated selection of the same rendezvous
5521 and introduction point circuit endpoints (their guards). Resolves
5525 - Enable Tor to read configuration, state, and key information from
5526 a FIFO. Previously Tor would only read from files with a positive
5527 stat.st_size. Code from meejah; fixes bug 6044.
5530 - Correct file sizes when reading binary files on Cygwin, to avoid
5531 a bug where Tor would fail to read its state file. Fixes bug 6844;
5532 bugfix on 0.1.2.7-alpha.
5533 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
5534 bugfix on 0.2.0.3-alpha.
5535 - When complaining about a client port on a public address, log
5536 which address we're complaining about. Fixes bug 4020; bugfix on
5537 0.2.3.3-alpha. Patch by Tom Fitzhenry.
5538 - Convert an assert in the pathbias code to a log message. The assert
5539 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5540 bugfix on 0.2.3.17-beta.
5541 - Our new buildsystem was overzealous about rebuilding manpages: it
5542 would rebuild them all whenever any one of them changed. Now our
5543 dependency checking should be correct. Fixes bug 6843; bugfix on
5545 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
5546 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
5547 - Correct log printout about which address family is preferred
5548 when connecting to a bridge with both an IPv4 and IPv6 OR port.
5549 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
5551 o Minor bugfixes (code cleanliness):
5552 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
5553 with large values. This situation was untriggered, but nevertheless
5554 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
5555 - Reject consensus votes with more than 64 known-flags. We aren't even
5556 close to that limit yet, and our code doesn't handle it correctly.
5557 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
5558 - Avoid undefined behavior when parsing the list of supported
5559 rendezvous/introduction protocols in a hidden service descriptor.
5560 Previously, Tor would have confused (as-yet-unused) protocol version
5561 numbers greater than 32 with lower ones on many platforms. Fixes
5562 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5563 - Fix handling of rendezvous client authorization types over 8.
5564 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
5565 - Fix building with older versions of GCC (2.95, for one) that don't
5566 like preprocessor directives inside macro arguments. Found by
5567 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
5568 - Switch weighted node selection rule from using a list of doubles
5569 to using a list of int64_t. This change should make the process
5570 slightly easier to debug and maintain. Needed to finish ticket 6538.
5572 o Code simplification and refactoring:
5573 - Move the generic "config" code into a new file, and have "config.c"
5574 hold only torrc- and state-related code. Resolves ticket 6823.
5575 - Move the core of our "choose a weighted element at random" logic
5576 into its own function, and give it unit tests. Now the logic is
5577 testable, and a little less fragile too.
5578 - Removed the testing_since field of node_t, which hasn't been used
5579 for anything since 0.2.0.9-alpha.
5581 o Documentation fixes:
5582 - Clarify that hidden services are TCP only. Fixes bug 6024.
5583 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
5587 Changes in version 0.2.3.22-rc - 2012-09-11
5588 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
5592 - Fix an assertion failure in tor_timegm() that could be triggered
5593 by a badly formatted directory object. Bug found by fuzzing with
5594 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5597 - Avoid segfault when starting up having run with an extremely old
5598 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5602 Changes in version 0.2.2.39 - 2012-09-11
5603 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
5607 - Fix an assertion failure in tor_timegm() that could be triggered
5608 by a badly formatted directory object. Bug found by fuzzing with
5609 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5610 - Do not crash when comparing an address with port value 0 to an
5611 address policy. This bug could have been used to cause a remote
5612 assertion failure by or against directory authorities, or to
5613 allow some applications to crash clients. Fixes bug 6690; bugfix
5617 Changes in version 0.2.4.2-alpha - 2012-09-10
5618 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
5619 raises the default rate limiting even more, and makes the bootstrapping
5620 log messages less noisy.
5623 - Automatically forward the TCP ports of pluggable transport
5624 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5628 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5629 to 1GB/1GB. The previous defaults were intended to be "basically
5630 infinite", but it turns out they're now limiting our 100mbit+
5631 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5632 last time we raised it).
5635 - Detect when we're running with a version of OpenSSL other than the
5636 one we compiled with. This has occasionally given people hard-to-
5638 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5639 versions and capabilities when everything is going right. Resolves
5640 part of ticket 6736.
5641 - Directory authorities no long accept descriptors for any version of
5642 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5643 These versions are insecure, unsupported, or both. Implements
5647 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
5648 to start with a triple-underscore so the controller won't touch it.
5649 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
5650 - Avoid segfault when starting up having run with an extremely old
5651 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5653 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
5654 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
5655 - Don't follow the NULL pointer if microdescriptor generation fails.
5656 (This does not appear to be triggerable, but it's best to be safe.)
5657 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
5658 - Fix mis-declared dependencies on src/common/crypto.c and
5659 src/or/tor_main.c that could break out-of-tree builds under some
5660 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
5661 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
5662 6778; bugfix on 0.2.4.1-alpha.
5663 - Fix a harmless (in this case) build warning for implicitly
5664 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
5667 - Now that all versions before 0.2.2.x are disallowed, we no longer
5668 need to work around their missing features. Thus we can remove a
5669 bunch of compatibility code.
5672 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5673 TCP ports to forward. In the past it only accepted two ports:
5674 the ORPort and the DirPort.
5677 Changes in version 0.2.4.1-alpha - 2012-09-05
5678 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
5679 bridgedb; lets relays use IPv6 addresses and directory authorities
5680 advertise them; and switches to a cleaner build interface.
5682 This is the first alpha release in a new series, so expect there to
5683 be bugs. Users who would rather test out a more stable branch should
5684 stay with 0.2.3.x for now.
5686 o Major features (bridges):
5687 - Bridges now report the pluggable transports they support to the
5688 bridge authority, so it can pass the supported transports on to
5689 bridgedb and/or eventually do reachability testing. Implements
5692 o Major features (IPv6):
5693 - Bridge authorities now accept IPv6 bridge addresses and include
5694 them in network status documents. Implements ticket 5534.
5695 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5696 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5697 to happen. Implements ticket 5535.
5698 - All kind of relays, not just bridges, can now advertise an IPv6
5699 OR port. Implements ticket 6362.
5700 - Directory authorities vote on IPv6 OR ports using the new consensus
5701 method 14. Implements ticket 6363.
5703 o Major features (build):
5704 - Switch to a nonrecursive Makefile structure. Now instead of each
5705 Makefile.am invoking other Makefile.am's, there is a master
5706 Makefile.am that includes the others. This change makes our build
5707 process slightly more maintainable, and improves parallelism for
5708 building with make -j. Original patch by Stewart Smith; various
5709 fixes by Jim Meyering.
5710 - Where available, we now use automake's "silent" make rules by
5711 default, so that warnings are easier to spot. You can get the old
5712 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5714 o Minor features (code security and spec conformance):
5715 - Clear keys and key-derived material left on the stack in
5716 rendservice.c and rendclient.c. Check return value of
5717 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5718 These fixes should make us more forward-secure against cold-boot
5719 attacks and the like. Fixes bug 2385.
5720 - Reject EXTEND cells sent to nonexistent streams. According to the
5721 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5722 we were only checking for stream IDs that were currently in use.
5723 Found while hunting for more instances of bug 6271. Bugfix on
5724 0.0.2pre8, which introduced incremental circuit construction.
5726 o Minor features (streamlining);
5727 - No longer include the "opt" prefix when generating routerinfos
5728 or v2 directories: it has been needless since Tor 0.1.2. Closes
5730 - Remove some now-needless code that tried to aggressively flush
5731 OR connections as data was added to them. Since 0.2.0.1-alpha, our
5732 cell queue logic has saved us from the failure mode that this code
5733 was supposed to prevent. Removing this code will limit the number
5734 of baroque control flow paths through Tor's network logic. Reported
5735 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
5737 o Minor features (controller):
5738 - Add a "GETINFO signal/names" control port command. Implements
5740 - Provide default values for all options via "GETINFO config/defaults".
5741 Implements ticket 4971.
5743 o Minor features (IPv6):
5744 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5745 authorities should set if they have IPv6 connectivity and want to
5746 do reachability tests for IPv6 relays. Implements feature 5974.
5747 - A relay with an IPv6 OR port now sends that address in NETINFO
5748 cells (in addition to its other address). Implements ticket 6364.
5750 o Minor features (log messages):
5751 - Omit the first heartbeat log message, because it never has anything
5752 useful to say, and it clutters up the bootstrapping messages.
5753 Resolves ticket 6758.
5754 - Don't log about reloading the microdescriptor cache at startup. Our
5755 bootstrap warnings are supposed to tell the user when there's a
5756 problem, and our bootstrap notices say when there isn't. Resolves
5757 ticket 6759; bugfix on 0.2.2.6-alpha.
5758 - Don't log "I learned some more directory information" when we're
5759 reading cached directory information. Reserve it for when new
5760 directory information arrives in response to a fetch. Resolves
5762 - Prevent rounding error in path bias counts when scaling
5763 them down, and use the correct scale factor default. Also demote
5764 some path bias related log messages down a level and make others
5765 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
5766 - We no longer warn so much when generating manpages from their
5769 o Code simplifications and refactoring:
5770 - Enhance our internal sscanf replacement so that we can eliminate
5771 the last remaining uses of the system sscanf. (Though those uses
5772 of sscanf were safe, sscanf itself is generally error prone, so
5773 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
5775 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
5776 - Move last_reachable and testing_since from routerinfo_t to node_t.
5777 Implements ticket 5529.
5778 - Add replaycache_t structure, functions and unit tests, then refactor
5779 rend_service_introduce() to be more clear to read, improve, debug,
5780 and test. Resolves bug 6177.
5781 - Finally remove support for malloc_good_size and malloc_usable_size.
5782 We had hoped that these functions would let us eke a little more
5783 memory out of our malloc implementation. Unfortunately, the only
5784 implementations that provided these functions are also ones that
5785 are already efficient about not overallocation: they never got us
5786 more than 7 or so bytes per allocation. Removing them saves us a
5787 little code complexity and a nontrivial amount of build complexity.
5790 - Tor maintainers now require Automake version 1.9 or later to build
5791 Tor from the Git repository. (Automake is not required when building
5792 from a source distribution.)
5795 Changes in version 0.2.3.21-rc - 2012-09-05
5796 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
5797 series. It fixes a trio of potential security bugs, fixes a bug where
5798 we were leaving some of the fast relays out of the microdescriptor
5799 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
5800 and cleans up other smaller issues.
5802 o Major bugfixes (security):
5803 - Tear down the circuit if we get an unexpected SENDME cell. Clients
5804 could use this trick to make their circuits receive cells faster
5805 than our flow control would have allowed, or to gum up the network,
5806 or possibly to do targeted memory denial-of-service attacks on
5807 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
5808 from July 2002, before the release of Tor 0.0.0. We had committed
5809 this patch previously, but we had to revert it because of bug 6271.
5810 Now that 6271 is fixed, this patch appears to work.
5811 - Reject any attempt to extend to an internal address. Without
5812 this fix, a router could be used to probe addresses on an internal
5813 network to see whether they were accepting connections. Fixes bug
5814 6710; bugfix on 0.0.8pre1.
5815 - Do not crash when comparing an address with port value 0 to an
5816 address policy. This bug could have been used to cause a remote
5817 assertion failure by or against directory authorities, or to
5818 allow some applications to crash clients. Fixes bug 6690; bugfix
5822 - Remove the upper bound on microdescriptor length. We were hitting
5823 the limit for routers with complex exit policies or family
5824 declarations, causing clients to not use them. Fixes the first
5825 piece of bug 6404; fix on 0.2.2.6-alpha.
5826 - Detect "ORPort 0" as meaning, uniformly, that we're not running
5827 as a relay. Previously, some of our code would treat the presence
5828 of any ORPort line as meaning that we should act like a relay,
5829 even though our new listener code would correctly not open any
5830 ORPorts for ORPort 0. Similar bugs in other Port options are also
5831 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
5834 - Avoid a pair of double-free and use-after-mark bugs that can
5835 occur with certain timings in canceled and re-received DNS
5836 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
5837 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
5838 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
5839 - Allow one-hop directory fetching circuits the full "circuit build
5840 timeout" period, rather than just half of it, before failing them
5841 and marking the relay down. This fix should help reduce cases where
5842 clients declare relays (or worse, bridges) unreachable because
5843 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
5844 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
5846 - Authorities no longer include any router in their microdescriptor
5847 consensuses for which they couldn't generate or agree on a
5848 microdescriptor. Fixes the second piece of bug 6404; fix on
5850 - Detect and reject attempts to specify both "FooPort" and
5851 "FooPort 0" in the same configuration domain. (It's still okay
5852 to have a FooPort in your configuration file, and use "FooPort 0"
5853 on the command line to disable it.) Fixes the second half of bug
5854 6507; bugfix on 0.2.3.3-alpha.
5855 - Make wildcarded addresses (that is, ones beginning with "*.") work
5856 when provided via the controller's MapAddress command. Previously,
5857 they were accepted, but we never actually noticed that they were
5858 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
5859 - Avoid crashing on a malformed state file where EntryGuardPathBias
5860 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
5861 - Add a (probably redundant) memory clear between iterations of
5862 the router status voting loop, to prevent future coding errors
5863 where data might leak between iterations of the loop. Resolves
5866 o Minor bugfixes (log messages):
5867 - Downgrade "set buildtimeout to low value" messages to "info"
5868 severity; they were never an actual problem, there was never
5869 anything reasonable to do about them, and they tended to spam logs
5870 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
5871 - Downgrade path-bias warning messages to "info". We'll try to get
5872 them working better in 0.2.4. Add internal circuit construction
5873 state to protect against the noisy warn message "Unexpectedly high
5874 circuit_successes". Also add some additional rate-limited notice
5875 messages to help determine the root cause of the warn. Fixes bug
5876 6475. Bugfix against 0.2.3.17-beta.
5877 - Move log message when unable to find a microdesc in a routerstatus
5878 entry to parse time. Previously we'd spam this warning every time
5879 we tried to figure out which microdescriptors to download. Fixes
5880 the third piece of bug 6404; fix on 0.2.3.18-rc.
5883 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
5884 change when the authority is deciding whether to accept a newly
5885 uploaded descriptor. Implements ticket 6423.
5886 - Add missing documentation for consensus and microdesc files.
5887 Resolves ticket 6732.
5890 Changes in version 0.2.2.38 - 2012-08-12
5891 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
5892 attack that could in theory leak path information.
5895 - Avoid an uninitialized memory read when reading a vote or consensus
5896 document that has an unrecognized flavor name. This read could
5897 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5898 - Try to leak less information about what relays a client is
5899 choosing to a side-channel attacker. Previously, a Tor client would
5900 stop iterating through the list of available relays as soon as it
5901 had chosen one, thus finishing a little earlier when it picked
5902 a router earlier in the list. If an attacker can recover this
5903 timing information (nontrivial but not proven to be impossible),
5904 they could learn some coarse-grained information about which relays
5905 a client was picking (middle nodes in particular are likelier to
5906 be affected than exits). The timing attack might be mitigated by
5907 other factors (see bug 6537 for some discussion), but it's best
5908 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5911 Changes in version 0.2.3.20-rc - 2012-08-05
5912 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
5913 series. It fixes a pair of code security bugs and a potential anonymity
5914 issue, updates our RPM spec files, and cleans up other smaller issues.
5917 - Avoid read-from-freed-memory and double-free bugs that could occur
5918 when a DNS request fails while launching it. Fixes bug 6480;
5919 bugfix on 0.2.0.1-alpha.
5920 - Avoid an uninitialized memory read when reading a vote or consensus
5921 document that has an unrecognized flavor name. This read could
5922 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5923 - Try to leak less information about what relays a client is
5924 choosing to a side-channel attacker. Previously, a Tor client would
5925 stop iterating through the list of available relays as soon as it
5926 had chosen one, thus finishing a little earlier when it picked
5927 a router earlier in the list. If an attacker can recover this
5928 timing information (nontrivial but not proven to be impossible),
5929 they could learn some coarse-grained information about which relays
5930 a client was picking (middle nodes in particular are likelier to
5931 be affected than exits). The timing attack might be mitigated by
5932 other factors (see bug 6537 for some discussion), but it's best
5933 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5936 - Try to make the warning when giving an obsolete SOCKSListenAddress
5937 a little more useful.
5938 - Terminate active server managed proxies if Tor stops being a
5939 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
5940 - Provide a better error message about possible OSX Asciidoc failure
5941 reasons. Fixes bug 6436.
5942 - Warn when Tor is configured to use accounting in a way that can
5943 link a hidden service to some other hidden service or public
5944 address. Resolves ticket 6490.
5947 - Check return value of fputs() when writing authority certificate
5948 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
5949 - Ignore ServerTransportPlugin lines when Tor is not configured as
5950 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
5951 - When disabling guards for having too high a proportion of failed
5952 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
5956 - Update our default RPM spec files to work with mock and rpmbuild
5957 on RHEL/Fedora. They have an updated set of dependencies and
5958 conflicts, a fix for an ancient typo when creating the "_tor"
5959 user, and better instructions. Thanks to Ondrej Mikle for the
5960 patch series. Fixes bug 6043.
5963 - Make it possible to set the TestingTorNetwork configuration
5964 option using AlternateDirAuthority and AlternateBridgeAuthority
5965 as an alternative to setting DirServer. Addresses ticket 6377.
5968 - Clarify the documentation for the Alternate*Authority options.
5970 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
5972 o Code simplification and refactoring:
5973 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
5974 10 lines. Also, don't nest them. Doing so in the past has
5975 led to hard-to-debug code. The new style is to use the
5976 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
5979 Changes in version 0.2.3.19-rc - 2012-07-06
5980 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
5981 series. It fixes the compile on Windows, reverts to a GeoIP database
5982 that isn't as broken, and fixes a flow control bug that has been around
5983 since the beginning of Tor.
5986 - Fix a bug handling SENDME cells on nonexistent streams that could
5987 result in bizarre window values. Report and patch contributed
5988 pseudonymously. Fixes part of bug 6271. This bug was introduced
5989 before the first Tor release, in svn commit r152.
5990 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
5991 June 2012 database, Maxmind marked many Tor relays as country "A1",
5992 which will cause risky behavior for clients that set EntryNodes
5993 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
5994 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
5995 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
5998 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
5999 bugfix on 0.2.1.10-alpha.
6002 Changes in version 0.2.3.18-rc - 2012-06-28
6003 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
6004 series. It fixes a few smaller bugs, but generally appears stable.
6005 Please test it and let us know whether it is!
6008 - Allow wildcarded mapaddress targets to be specified on the
6009 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
6010 - Make our linker option detection code more robust against linkers
6011 such as on FreeBSD 8, where a bad combination of options completes
6012 successfully but makes an unrunnable binary. Fixes bug 6173;
6013 bugfix on 0.2.3.17-beta.
6015 o Minor bugfixes (on 0.2.2.x and earlier):
6016 - Avoid a false positive in the util/threads unit test by increasing
6017 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
6018 - Replace "Sending publish request" log messages with "Launching
6019 upload", so that they no longer confusingly imply that we're
6020 sending something to a directory we might not even be connected
6021 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
6022 - Make sure to set *socket_error in all error cases in
6023 connection_connect(), so it can't produce a warning about
6024 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6025 0.2.1.1-alpha; resolves ticket 6028.
6026 - Downgrade "Got a certificate, but we already have it" log messages
6027 from warning to info, except when we're a dirauth. Fixes bug 5238;
6028 bugfix on 0.2.1.7-alpha.
6029 - When checking for requested signatures on the latest consensus
6030 before serving it to a client, make sure to check the right
6031 consensus flavor. Bugfix on 0.2.2.6-alpha.
6032 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
6033 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
6035 o Minor bugfixes (on 0.2.3.x):
6036 - Make format_helper_exit_status() avoid unnecessary space padding
6037 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
6039 - Downgrade a message about cleaning the microdescriptor cache to
6040 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
6041 - Log a BUG message at severity INFO if we have a networkstatus with
6042 a missing entry for some microdescriptor. Continues on a patch
6044 - Improve the log message when a managed proxy fails to launch. Fixes
6045 bug 5099; bugfix on 0.2.3.6-alpha.
6046 - Don't do DNS lookups when parsing corrupted managed proxy protocol
6047 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
6048 - When formatting wildcarded address mappings for the controller,
6049 be sure to include "*." as appropriate. Partially fixes bug 6244;
6050 bugfix on 0.2.3.9-alpha.
6051 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
6052 Bugfix on 0.2.3.13-alpha.
6053 - Stop logging messages about running with circuit timeout learning
6054 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
6055 - Disable a spurious warning about reading on a marked and flushing
6056 connection. We shouldn't be doing that, but apparently we
6057 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
6058 - Fix a bug that stopped AllowDotExit from working on addresses
6059 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
6062 o Code simplification, refactoring, unit tests:
6063 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
6064 Libevent's notion of cached time when possible.
6065 - Remove duplicate code for invoking getrlimit() from control.c.
6066 - Add a unit test for the environment_variable_names_equal function.
6069 - Document the --defaults-torrc option, and the new (in 0.2.3)
6070 semantics for overriding, extending, and clearing lists of
6071 options. Closes bug 4748.
6074 Changes in version 0.2.3.17-beta - 2012-06-15
6075 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
6076 gets our TLS handshake back on track for being able to blend in with
6077 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
6078 with Vidalia, and otherwise continues to get us closer to a release
6082 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6083 - Update TLS cipher list to match Firefox 8 and later. Resolves
6085 - Implement the client side of proposal 198: remove support for
6086 clients falsely claiming to support standard ciphersuites that
6087 they can actually provide. As of modern OpenSSL versions, it's not
6088 necessary to fake any standard ciphersuite, and doing so prevents
6089 us from using better ciphersuites in the future, since servers
6090 can't know whether an advertised ciphersuite is really supported or
6091 not. Some hosts -- notably, ones with very old versions of OpenSSL
6092 or where OpenSSL has been built with ECC disabled -- will stand
6093 out because of this change; TBB users should not be affected.
6096 - Change the default value for DynamicDHGroups (introduced in
6097 0.2.3.9-alpha) to 0. This feature can make Tor relays less
6098 identifiable by their use of the mod_ssl DH group, but at
6099 the cost of some usability (#4721) and bridge tracing (#6087)
6100 regressions. Resolves ticket 5598.
6101 - Send a CRLF at the end of each STATUS_* control protocol event. This
6102 bug tickled a bug in Vidalia which would make it freeze. Fixes
6103 bug 6094; bugfix on 0.2.3.16-alpha.
6106 - Disable writing on marked-for-close connections when they are
6107 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
6108 bug 5263; bugfix on 0.0.2pre13, where we first added a special
6109 case for flushing marked connections.
6110 - Detect SSL handshake even when the initial attempt to write the
6111 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
6112 - Change the AllowDotExit rules so they should actually work.
6113 We now enforce AllowDotExit only immediately after receiving an
6114 address via SOCKS or DNSPort: other sources are free to provide
6115 .exit addresses after the resolution occurs. Fixes bug 3940;
6116 bugfix on 0.2.2.1-alpha.
6117 - Fix a (harmless) integer overflow in cell statistics reported by
6118 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6119 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
6120 right places and never depends on the consensus parameters or
6121 computes adaptive timeouts when it is disabled. Fixes bug 5049;
6122 bugfix on 0.2.2.14-alpha.
6123 - When building Tor on Windows with -DUNICODE (not default), ensure
6124 that error messages, filenames, and DNS server names are always
6125 NUL-terminated when we convert them to a single-byte encoding.
6126 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6127 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
6128 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
6129 - Fix an edge case where TestingTorNetwork is set but the authorities
6130 and relays all have an uptime of zero, where the private Tor network
6131 could briefly lack support for hidden services. Fixes bug 3886;
6132 bugfix on 0.2.2.18-alpha.
6133 - Correct the manpage's descriptions for the default values of
6134 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
6136 - Fix the documentation for the --hush and --quiet command line
6137 options, which changed their behavior back in 0.2.3.3-alpha.
6138 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
6142 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
6143 more information to it, so that we can track it down in case it
6144 returns again. Mitigates bug 5235.
6145 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
6146 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
6147 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
6148 - Warn the user when HTTPProxy, but no other proxy type, is
6149 configured. This can cause surprising behavior: it doesn't send
6150 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
6151 directory traffic only. Resolves ticket 4663.
6152 - Issue a notice if a guard completes less than 40% of your circuits.
6153 Threshold is configurable by torrc option PathBiasNoticeRate and
6154 consensus parameter pb_noticepct. There is additional, off-by-
6155 default code to disable guards which fail too many circuits.
6156 Addresses ticket 5458.
6157 - Update to the June 6 2012 Maxmind GeoLite Country database.
6159 o Code simplifications and refactoring:
6160 - Remove validate_pluggable_transports_config(): its warning
6161 message is now handled by connection_or_connect().
6164 Changes in version 0.2.2.37 - 2012-06-06
6165 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
6166 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6170 - Work around a bug in OpenSSL that broke renegotiation with TLS
6171 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6172 the v2 Tor connection protocol when both sides were using OpenSSL
6173 1.0.1 would fail. Resolves ticket 6033.
6174 - When waiting for a client to renegotiate, don't allow it to add
6175 any bytes to the input buffer. This fixes a potential DoS issue.
6176 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6177 - Fix an edge case where if we fetch or publish a hidden service
6178 descriptor, we might build a 4-hop circuit and then use that circuit
6179 for exiting afterwards -- even if the new last hop doesn't obey our
6180 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6183 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6184 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6187 - Tell GCC and Clang to check for any errors in format strings passed
6188 to the tor_v*(print|scan)f functions.
6191 Changes in version 0.2.3.16-alpha - 2012-06-05
6192 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
6193 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6194 currently). It also fixes a variety of smaller bugs and other cleanups
6195 that get us closer to a release candidate.
6197 o Major bugfixes (general):
6198 - Work around a bug in OpenSSL that broke renegotiation with TLS
6199 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6200 the v2 Tor connection protocol when both sides were using OpenSSL
6201 1.0.1 would fail. Resolves ticket 6033.
6202 - When waiting for a client to renegotiate, don't allow it to add
6203 any bytes to the input buffer. This fixes a potential DoS issue.
6204 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6205 - Pass correct OR address to managed proxies (like obfsproxy),
6206 even when ORListenAddress is used. Fixes bug 4865; bugfix on
6208 - The advertised platform of a router now includes only its operating
6209 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
6210 service pack level (for Windows) or its CPU architecture (for Unix).
6211 We also no longer include the "git-XYZ" tag in the version. Resolves
6214 o Major bugfixes (clients):
6215 - If we are unable to find any exit that supports our predicted ports,
6216 stop calling them predicted, so that we don't loop and build
6217 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
6218 which introduced predicted ports.
6219 - Fix an edge case where if we fetch or publish a hidden service
6220 descriptor, we might build a 4-hop circuit and then use that circuit
6221 for exiting afterwards -- even if the new last hop doesn't obey our
6222 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6223 - Check at each new consensus whether our entry guards were picked
6224 long enough ago that we should rotate them. Previously, we only
6225 did this check at startup, which could lead to us holding a guard
6226 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
6227 - When fetching a bridge descriptor from a bridge authority,
6228 always do so anonymously, whether we have been able to open
6229 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
6230 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
6231 but we'll need to wait for bug 6010 before it's actually usable.
6233 o Major bugfixes (directory authorities):
6234 - When computing weight parameters, behave more robustly in the
6235 presence of a bad bwweightscale value. Previously, the authorities
6236 would crash if they agreed on a sufficiently broken weight_scale
6237 value: now, they use a reasonable default and carry on. Partial
6238 fix for 5786; bugfix on 0.2.2.17-alpha.
6239 - Check more thoroughly to prevent a rogue authority from
6240 double-voting on any consensus directory parameter. Previously,
6241 authorities would crash in this case if the total number of
6242 votes for any parameter exceeded the number of active voters,
6243 but would let it pass otherwise. Partial fix for bug 5786; bugfix
6247 - Rate-limit log messages when asked to connect anonymously to
6248 a private address. When these hit, they tended to hit fast and
6249 often. Also, don't bother trying to connect to addresses that we
6250 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
6251 reply makes us think we have been lied to, even when the address the
6252 client tried to connect to was "localhost." Resolves ticket 2822.
6253 - Allow packagers to insert an extra string in server descriptor
6254 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
6255 Resolves the rest of ticket 2988.
6256 - Raise the threshold of server descriptors needed (75%) and exit
6257 server descriptors needed (50%) before we will declare ourselves
6258 bootstrapped. This will make clients start building circuits a
6259 little later, but makes the initially constructed circuits less
6260 skewed and less in conflict with further directory fetches. Fixes
6262 - Close any connection that sends unrecognized junk before the
6263 handshake. Solves an issue noted in bug 4369.
6264 - Improve log messages about managed transports. Resolves ticket 5070.
6265 - Tag a bridge's descriptor as "never to be sent unencrypted".
6266 This shouldn't matter, since bridges don't open non-anonymous
6267 connections to the bridge authority and don't allow unencrypted
6268 directory connections from clients, but we might as well make
6269 sure. Closes bug 5139.
6270 - Expose our view of whether we have gone dormant to the controller,
6271 via a new "GETINFO dormant" value. Torbutton and other controllers
6272 can use this to avoid doing periodic requests through Tor while
6273 it's dormant (bug 4718). Fixes bug 5954.
6274 - Tell GCC and Clang to check for any errors in format strings passed
6275 to the tor_v*(print|scan)f functions.
6276 - Update to the May 1 2012 Maxmind GeoLite Country database.
6278 o Minor bugfixes (already included in 0.2.2.36):
6279 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6280 Fixes bug 5346; bugfix on 0.0.8pre3.
6281 - Correct parsing of certain date types in parse_http_time().
6282 Without this patch, If-Modified-Since would behave
6283 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6284 Esteban Manchado Velázques.
6285 - Make our number-parsing functions always treat too-large values
6286 as an error, even when those values exceed the width of the
6287 underlying type. Previously, if the caller provided these
6288 functions with minima or maxima set to the extreme values of the
6289 underlying integer type, these functions would return those
6290 values on overflow rather than treating overflow as an error.
6291 Fixes part of bug 5786; bugfix on 0.0.9.
6292 - If we hit the error case where routerlist_insert() replaces an
6293 existing (old) server descriptor, make sure to remove that
6294 server descriptor from the old_routers list. Fix related to bug
6295 1776. Bugfix on 0.2.2.18-alpha.
6296 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6297 circuits. Fixes issue 5259.
6299 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
6300 - Prevent a null-pointer dereference when receiving a data cell
6301 for a nonexistent stream when the circuit in question has an
6302 empty deliver window. We don't believe this is triggerable,
6303 since we don't currently allow deliver windows to become empty,
6304 but the logic is tricky enough that it's better to make the code
6305 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6306 - Fix a memory leak when trying to launch a DNS request when the
6307 network is disabled or the nameservers are unconfigurable. Fixes
6308 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
6309 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
6310 - Don't hold a Windows file handle open for every file mapping;
6311 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
6313 - Avoid O(n^2) performance characteristics when parsing a large
6314 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6315 - Format more doubles with %f, not %lf. Patch from grarpamp to make
6316 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
6318 - Make our replacement implementation of strtok_r() compatible with
6319 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6320 bugfix on 0.2.2.1-alpha.
6321 - Fix a NULL-pointer dereference on a badly formed
6322 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
6323 bugfix on 0.2.2.9-alpha.
6324 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6325 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6326 - Defensively refactor rend_mid_rendezvous() so that protocol
6327 violations and length checks happen in the beginning. Fixes
6329 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
6330 that IPv6 stuff will compile on MSVC, and compilation issues
6331 will be easier to track down. Fixes bug 5861.
6333 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
6334 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
6335 resource exhaustion, so that clients can adjust their load to
6336 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
6337 started using END_STREAM_REASON_RESOURCELIMIT.
6338 - Don't check for whether the address we're using for outbound
6339 connections has changed until after the outbound connection has
6340 completed. On Windows, getsockname() doesn't succeed until the
6341 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
6342 - If the configuration tries to set MyFamily on a bridge, refuse to
6343 do so, and warn about the security implications. Fixes bug 4657;
6344 bugfix on 0.2.0.3-alpha.
6345 - If the client fails to set a reasonable set of ciphersuites
6346 during its v2 handshake renegotiation, allow the renegotiation to
6347 continue nevertheless (i.e. send all the required certificates).
6348 Fixes bug 4591; bugfix on 0.2.0.20-rc.
6349 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
6350 option is set to 0 (which Vidalia version 0.2.16 now does when
6351 a SAVECONF attempt fails), perform other actions that SIGHUP
6352 usually causes (like reopening the logs). Fixes bug 5095; bugfix
6354 - If we fail to write a microdescriptor to the disk cache, do not
6355 continue replacing the old microdescriptor file. Fixes bug 2954;
6356 bugfix on 0.2.2.6-alpha.
6357 - Exit nodes don't need to fetch certificates for authorities that
6358 they don't recognize; only directory authorities, bridges,
6359 and caches need to do that. Fixes part of bug 2297; bugfix on
6361 - Correctly handle checking the permissions on the parent
6362 directory of a control socket in the root directory. Bug found
6363 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
6365 - When told to add a bridge with the same digest as a preexisting
6366 bridge but a different addr:port, change the addr:port as
6367 requested. Previously we would not notice the change. Fixes half
6368 of bug 5603; fix on 0.2.2.26-beta.
6369 - End AUTHCHALLENGE error messages (in the control protocol) with
6370 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
6372 o Minor bugfixes (on 0.2.3.x):
6373 - Turn an assertion (that the number of handshakes received as a
6374 server is not < 1) into a warning. Fixes bug 4873; bugfix on
6376 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
6377 we had reversed them when the answer was cached.) Fixes bug
6378 5723; bugfix on 0.2.3.1-alpha.
6379 - Work correctly on Linux systems with accept4 support advertised in
6380 their headers, but without accept4 support in the kernel. Fix
6381 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
6382 - When told to add a bridge with the same addr:port as a preexisting
6383 bridge but a different transport, change the transport as
6384 requested. Previously we would not notice the change. Fixes half
6385 of bug 5603; fix on 0.2.3.2-alpha.
6386 - Avoid a "double-reply" warning when replying to a SOCKS request
6387 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
6388 bugfix on 0.2.3.4-alpha.
6389 - Fix a bug where a bridge authority crashes if it has seen no
6390 directory requests when it's time to write statistics to disk.
6391 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
6393 - Don't try to open non-control listeners when DisableNetwork is set.
6394 Previously, we'd open all listeners, then immediately close them.
6395 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
6396 - Don't abort the managed proxy protocol if the managed proxy
6397 sends us an unrecognized line; ignore it instead. Fixes bug
6398 5910; bugfix on 0.2.3.9-alpha.
6399 - Fix a compile warning in crypto.c when compiling with clang 3.1.
6400 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
6401 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
6402 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
6403 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
6404 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
6405 - Resolve numerous small warnings and build issues with MSVC. Resolves
6408 o Documentation fixes:
6409 - Improve the manual's documentation for the NT Service command-line
6410 options. Addresses ticket 3964.
6411 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
6412 - Document the changes to the ORPort and DirPort options, and the
6413 fact that {OR/Dir}ListenAddress is now unnecessary (and
6414 therefore deprecated). Resolves ticket 5597.
6417 - Remove the torrc.bridge file: we don't use it for anything, and
6418 it had become badly desynchronized from torrc.sample. Resolves
6422 Changes in version 0.2.2.36 - 2012-05-24
6423 Tor 0.2.2.36 updates the addresses for two of the eight directory
6424 authorities, fixes some potential anonymity and security issues,
6425 and fixes several crash bugs.
6427 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
6428 known flaws, and nobody should be using them. You should upgrade. If
6429 you're using a Linux or BSD and its packages are obsolete, stop using
6430 those packages and upgrade anyway.
6432 o Directory authority changes:
6433 - Change IP address for maatuska (v3 directory authority).
6434 - Change IP address for ides (v3 directory authority), and rename
6438 - When building or running with any version of OpenSSL earlier
6439 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6440 versions have a bug (CVE-2011-4576) in which their block cipher
6441 padding includes uninitialized data, potentially leaking sensitive
6442 information to any peer with whom they make a SSLv3 connection. Tor
6443 does not use SSL v3 by default, but a hostile client or server
6444 could force an SSLv3 connection in order to gain information that
6445 they shouldn't have been able to get. The best solution here is to
6446 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6447 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6448 to make sure that the bug can't happen.
6449 - Never use a bridge or a controller-supplied node as an exit, even
6450 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6451 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6452 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6453 - Only build circuits if we have a sufficient threshold of the total
6454 descriptors that are marked in the consensus with the "Exit"
6455 flag. This mitigates an attack proposed by wanoskarnet, in which
6456 all of a client's bridges collude to restrict the exit nodes that
6457 the client knows about. Fixes bug 5343.
6458 - Provide controllers with a safer way to implement the cookie
6459 authentication mechanism. With the old method, if another locally
6460 running program could convince a controller that it was the Tor
6461 process, then that program could trick the controller into telling
6462 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6463 authentication method uses a challenge-response approach to prevent
6464 this attack. Fixes bug 5185; implements proposal 193.
6467 - Avoid logging uninitialized data when unable to decode a hidden
6468 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6469 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6470 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6472 - Fix builds when the path to sed, openssl, or sha1sum contains
6473 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6475 - Correct our replacements for the timeradd() and timersub() functions
6476 on platforms that lack them (for example, Windows). The timersub()
6477 function is used when expiring circuits, while timeradd() is
6478 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6479 bugfix on 0.2.2.24-alpha.
6480 - Fix the SOCKET_OK test that we use to tell when socket
6481 creation fails so that it works on Win64. Fixes part of bug 4533;
6482 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6485 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6486 Fixes bug 5346; bugfix on 0.0.8pre3.
6487 - Make our number-parsing functions always treat too-large values
6488 as an error, even when those values exceed the width of the
6489 underlying type. Previously, if the caller provided these
6490 functions with minima or maxima set to the extreme values of the
6491 underlying integer type, these functions would return those
6492 values on overflow rather than treating overflow as an error.
6493 Fixes part of bug 5786; bugfix on 0.0.9.
6494 - Older Linux kernels erroneously respond to strange nmap behavior
6495 by having accept() return successfully with a zero-length
6496 socket. When this happens, just close the connection. Previously,
6497 we would try harder to learn the remote address: but there was
6498 no such remote address to learn, and our method for trying to
6499 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6500 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6501 - Correct parsing of certain date types in parse_http_time().
6502 Without this patch, If-Modified-Since would behave
6503 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6504 Esteban Manchado Velázques.
6505 - Change the BridgePassword feature (part of the "bridge community"
6506 design, which is not yet implemented) to use a time-independent
6507 comparison. The old behavior might have allowed an adversary
6508 to use timing to guess the BridgePassword value. Fixes bug 5543;
6509 bugfix on 0.2.0.14-alpha.
6510 - Detect and reject certain misformed escape sequences in
6511 configuration values. Previously, these values would cause us
6512 to crash if received in a torrc file or over an authenticated
6513 control port. Bug found by Esteban Manchado Velázquez, and
6514 independently by Robert Connolly from Matta Consulting who further
6515 noted that it allows a post-authentication heap overflow. Patch
6516 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6517 bugfix on 0.2.0.16-alpha.
6518 - Fix a compile warning when using the --enable-openbsd-malloc
6519 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6520 - During configure, detect when we're building with clang version
6521 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6522 CFLAGS. clang doesn't support them yet.
6523 - When sending an HTTP/1.1 proxy request, include a Host header.
6524 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6525 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
6526 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
6527 - If we hit the error case where routerlist_insert() replaces an
6528 existing (old) server descriptor, make sure to remove that
6529 server descriptor from the old_routers list. Fix related to bug
6530 1776. Bugfix on 0.2.2.18-alpha.
6532 o Minor bugfixes (documentation and log messages):
6533 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6534 Fixes bug 4856; bugfix on Tor 0.0.6.
6535 - Update "ClientOnly" man page entry to explain that there isn't
6536 really any point to messing with it. Resolves ticket 5005.
6537 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6538 directory authority option (introduced in Tor 0.2.2.34).
6539 - Downgrade the "We're missing a certificate" message from notice
6540 to info: people kept mistaking it for a real problem, whereas it
6541 is seldom the problem even when we are failing to bootstrap. Fixes
6542 bug 5067; bugfix on 0.2.0.10-alpha.
6543 - Correctly spell "connect" in a log message on failure to create a
6544 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
6545 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6546 circuits. Fixes issue 5259.
6549 - Directory authorities now reject versions of Tor older than
6550 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6551 inclusive. These versions accounted for only a small fraction of
6552 the Tor network, and have numerous known security issues. Resolves
6554 - Update to the May 1 2012 Maxmind GeoLite Country database.
6557 - When sending or relaying a RELAY_EARLY cell, we used to convert
6558 it to a RELAY cell if the connection was using the v1 link
6559 protocol. This was a workaround for older versions of Tor, which
6560 didn't handle RELAY_EARLY cells properly. Now that all supported
6561 versions can handle RELAY_EARLY cells, and now that we're enforcing
6562 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6563 remove this workaround. Addresses bug 4786.
6566 Changes in version 0.2.3.15-alpha - 2012-04-30
6567 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
6568 the development branch build on Windows again.
6570 o Minor bugfixes (on 0.2.2.x and earlier):
6571 - Make sure that there are no unhandled pending TLS errors before
6572 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
6573 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
6574 Bugfix on 0.1.0.5-rc; fixes bug 4528.
6575 - Fix an assert that directory authorities could trigger on sighup
6576 during some configuration state transitions. We now don't treat
6577 it as a fatal error when the new descriptor we just generated in
6578 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6579 - After we pick a directory mirror, we would refuse to use it if
6580 it's in our ExcludeExitNodes list, resulting in mysterious failures
6581 to bootstrap for people who just wanted to avoid exiting from
6582 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
6583 - When building with --enable-static-tor on OpenBSD, do not
6584 erroneously attempt to link -lrt. Fixes bug 5103.
6586 o Minor bugfixes (on 0.2.3.x):
6587 - When Tor is built with kernel headers from a recent (last few
6588 years) Linux kernel, do not fail to run on older (pre-2.6.28
6589 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
6590 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
6592 - Fix compilation with miniupnpc version 1.6; patch from
6593 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
6594 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
6595 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
6596 - Fix compilation on platforms without unistd.h, or where environ
6597 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
6600 - Directory authorities are now a little more lenient at accepting
6601 older router descriptors, or newer router descriptors that don't
6602 make big changes. This should help ameliorate past and future
6603 issues where routers think they have uploaded valid descriptors,
6604 but the authorities don't think so. Fix for ticket 2479.
6605 - Make the code that clients use to detect an address change be
6606 IPv6-aware, so that it won't fill clients' logs with error
6607 messages when trying to get the IPv4 address of an IPv6
6608 connection. Implements ticket 5537.
6611 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
6612 authorities needed to use it for a while to keep the network working
6613 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
6614 that was six months ago. As of now, it should no longer be needed
6618 Changes in version 0.2.3.14-alpha - 2012-04-23
6619 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
6620 candidate. It also dramatically speeds up AES: fast relays should
6621 consider switching to the newer OpenSSL library.
6623 o Directory authority changes:
6624 - Change IP address for ides (v3 directory authority), and rename
6628 - Avoid logging uninitialized data when unable to decode a hidden
6629 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6630 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6631 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6633 - If authorities are unable to get a v2 consensus document from other
6634 directory authorities, they no longer fall back to fetching
6635 them from regular directory caches. Fixes bug 5635; bugfix on
6636 0.2.2.26-beta, where routers stopped downloading v2 consensus
6638 - When we start a Tor client with a normal consensus already cached,
6639 be willing to download a microdescriptor consensus. Fixes bug 4011;
6640 fix on 0.2.3.1-alpha.
6642 o Major features (performance):
6643 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6644 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6645 vectorized AES implementations as appropriate. These can be much,
6646 much faster than other AES implementations.
6648 o Minor bugfixes (0.2.2.x and earlier):
6649 - Don't launch more than 10 service-side introduction-point circuits
6650 for a hidden service in five minutes. Previously, we would consider
6651 launching more introduction-point circuits if at least one second
6652 had passed without any introduction-point circuits failing. Fixes
6653 bug 4607; bugfix on 0.0.7pre1.
6654 - Change the BridgePassword feature (part of the "bridge community"
6655 design, which is not yet implemented) to use a time-independent
6656 comparison. The old behavior might have allowed an adversary
6657 to use timing to guess the BridgePassword value. Fixes bug 5543;
6658 bugfix on 0.2.0.14-alpha.
6659 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6660 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6661 - When sending an HTTP/1.1 proxy request, include a Host header.
6662 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6663 - Don't log that we have "decided to publish new relay descriptor"
6664 unless we are actually publishing a descriptor. Fixes bug 3942;
6665 bugfix on 0.2.2.28-beta.
6667 o Minor bugfixes (0.2.3.x):
6668 - Fix a bug where a bridge authority crashes (on a failed assert)
6669 if it has seen no directory requests when it's time to write
6670 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
6671 - Fix bug stomping on ORPort option NoListen and ignoring option
6672 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
6673 - In the testsuite, provide a large enough buffer in the tor_sscanf
6674 unit test. Otherwise we'd overrun that buffer and crash during
6675 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
6677 - Make sure we create the keys directory if it doesn't exist and we're
6678 about to store the dynamic Diffie-Hellman parameters. Fixes bug
6679 5572; bugfix on 0.2.3.13-alpha.
6680 - Fix a small memory leak when trying to decode incorrect base16
6681 authenticator during SAFECOOKIE authentication. Found by
6682 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
6685 - Add more information to a log statement that might help track down
6686 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6687 non-IP address" messages (or any Bug messages, for that matter!),
6688 please let us know about it.
6689 - Relays now understand an IPv6 address when they get one from a
6690 directory server. Resolves ticket 4875.
6691 - Resolve IPv6 addresses in bridge and entry statistics to country
6692 code "??" which means we at least count them. Resolves ticket 5053;
6693 improves on 0.2.3.9-alpha.
6694 - Update to the April 3 2012 Maxmind GeoLite Country database.
6695 - Begin a doc/state-contents.txt file to explain the contents of
6696 the Tor state file. Fixes bug 2987.
6698 o Default torrc changes:
6699 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6700 port on 9050 by default anyway, so this should not change anything
6702 - Stop mentioning the deprecated *ListenAddress options in
6703 torrc.sample. Fixes bug 5438.
6704 - Document unit of bandwidth related options in sample torrc.
6708 - The "torify" script no longer supports the "tsocks" socksifier
6709 tool, since tsocks doesn't support DNS and UDP right for Tor.
6710 Everyone should be using torsocks instead. Fixes bugs 3530 and
6711 5180. Based on a patch by "ugh".
6714 - Change the symmetric cipher interface so that creating and
6715 initializing a stream cipher are no longer separate functions.
6716 - Remove all internal support for unpadded RSA. We never used it, and
6717 it would be a bad idea to start.
6720 Changes in version 0.2.3.13-alpha - 2012-03-26
6721 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
6722 in managed pluggable transports, as well as providing other cleanups
6723 that get us closer to a release candidate.
6725 o Directory authority changes:
6726 - Change IP address for maatuska (v3 directory authority).
6729 - Provide controllers with a safer way to implement the cookie
6730 authentication mechanism. With the old method, if another locally
6731 running program could convince a controller that it was the Tor
6732 process, then that program could trick the controller into telling
6733 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6734 authentication method uses a challenge-response approach to prevent
6735 this attack. Fixes bug 5185, implements proposal 193.
6736 - Never use a bridge or a controller-supplied node as an exit, even
6737 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6738 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6739 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6740 - Only build circuits if we have a sufficient threshold of the total
6741 descriptors that are marked in the consensus with the "Exit"
6742 flag. This mitigates an attack proposed by wanoskarnet, in which
6743 all of a client's bridges collude to restrict the exit nodes that
6744 the client knows about. Fixes bug 5343.
6746 o Major bugfixes (on Tor 0.2.3.x):
6747 - Avoid an assert when managed proxies like obfsproxy are configured,
6748 and we receive HUP signals or setconf attempts too rapidly. This
6749 situation happens most commonly when Vidalia tries to attach to
6750 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
6751 bugfix on 0.2.3.6-alpha.
6752 - Fix a relay-side pluggable transports bug where managed proxies were
6753 unreachable from the Internet, because Tor asked them to bind on
6754 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
6755 - Stop discarding command-line arguments when TestingTorNetwork
6756 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
6757 0.2.3.9-alpha, where task 4552 added support for two layers of
6759 - Resume allowing the unit tests to run in gdb. This was accidentally
6760 made impossible when the DisableDebuggerAttachment option was
6761 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
6762 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
6763 0.2.3.11-alpha. Reported by Anthony G. Basile.
6765 o Minor bugfixes (on 0.2.2.x and earlier):
6766 - Ensure we don't cannibalize circuits that are longer than three hops
6767 already, so we don't end up making circuits with 5 or more
6768 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6769 0.1.0.1-rc which introduced cannibalization.
6770 - Detect and reject certain misformed escape sequences in
6771 configuration values. Previously, these values would cause us
6772 to crash if received in a torrc file or over an authenticated
6773 control port. Bug found by Esteban Manchado Velázquez, and
6774 independently by Robert Connolly from Matta Consulting who further
6775 noted that it allows a post-authentication heap overflow. Patch
6776 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6777 bugfix on 0.2.0.16-alpha.
6778 - Fix a compile warning when using the --enable-openbsd-malloc
6779 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6780 - Directory caches no longer refuse to clean out descriptors because
6781 of missing v2 networkstatus documents, unless they're configured
6782 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6783 0.2.2.26-beta. Patch by Daniel Bryg.
6784 - Update to the latest version of the tinytest unit testing framework.
6785 This includes a couple of bugfixes that can be relevant for
6786 running forked unit tests on Windows, and removes all reserved
6789 o Minor bugfixes (on 0.2.3.x):
6790 - On a failed pipe() call, don't leak file descriptors. Fixes bug
6791 4296; bugfix on 0.2.3.1-alpha.
6792 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
6793 until after we have received a CERTS cell. Fixes bug 4361; bugfix
6794 on 0.2.3.6-alpha. Patch by "frosty".
6795 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
6796 option, so that the IP stack doesn't decide to use it for IPv4
6797 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
6798 - Ensure that variables set in Tor's environment cannot override
6799 environment variables that Tor passes to a managed
6800 pluggable-transport proxy. Previously, Tor would pass every
6801 variable in its environment to managed proxies along with the new
6802 ones, in such a way that on many operating systems, the inherited
6803 environment variables would override those which Tor tried to
6804 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
6805 bugfix on 0.2.3.9-alpha for Windows.
6808 - A wide variety of new unit tests by Esteban Manchado Velázquez.
6809 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6810 - Update to the March 6 2012 Maxmind GeoLite Country database.
6813 Changes in version 0.2.3.12-alpha - 2012-02-13
6814 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
6815 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
6816 when Tor is configured to use a pluggable transport like obfsproxy.
6819 - Fix builds when the path to sed, openssl, or sha1sum contains
6820 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6822 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6823 connections. This change should allow busy exit relays to stop
6824 running out of available sockets as quickly. Fixes bug 4950;
6825 bugfix on 0.2.2.26-beta.
6826 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
6827 would ask the bridge for microdescriptors, which are only supported
6828 in 0.2.3.x, and then fail to bootstrap when it didn't get the
6829 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
6830 - Properly set up obfsproxy's environment when in managed mode. The
6831 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
6832 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
6833 5076 and 5082; bugfix on 0.2.3.6-alpha.
6836 - Use the dead_strip option when building Tor on OS X. This reduces
6837 binary size by almost 19% when linking openssl and libevent
6838 statically, which we do for Tor Browser Bundle.
6839 - Fix broken URLs in the sample torrc file, and tell readers about
6840 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6841 PublishServerDescriptor options. Addresses bug 4652.
6842 - Update to the February 7 2012 Maxmind GeoLite Country database.
6845 - Downgrade the "We're missing a certificate" message from notice
6846 to info: people kept mistaking it for a real problem, whereas it
6847 is seldom the problem even when we are failing to bootstrap. Fixes
6848 bug 5067; bugfix on 0.2.0.10-alpha.
6849 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
6850 managed pluggable transport server proxy's environment.
6851 Previously, we would put it there, even though Tor doesn't
6852 implement an 'extended server port' yet, and even though Tor
6853 almost certainly isn't listening at that address. For now, we set
6854 it to an empty string to avoid crashing older obfsproxies. Bugfix
6856 - Log the heartbeat message every HeartbeatPeriod seconds, not every
6857 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
6858 0.2.3.1-alpha. Bug reported by Scott Bennett.
6859 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
6860 bugfix on 0.2.3.11-alpha.
6861 - Update "ClientOnly" man page entry to explain that there isn't
6862 really any point to messing with it. Resolves ticket 5005.
6863 - Use the correct CVE number for CVE-2011-4576 in our comments and
6864 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
6867 o Code simplifications and refactoring:
6868 - Use the _WIN32 macro throughout our code to detect Windows.
6869 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
6873 Changes in version 0.2.3.11-alpha - 2012-01-22
6874 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
6875 the last step of the plan to limit maximum circuit length, includes
6876 a wide variety of hidden service performance and correctness fixes,
6877 works around an OpenSSL security flaw if your distro is too stubborn
6878 to upgrade, and fixes a bunch of smaller issues.
6881 - Now that Tor 0.2.0.x is completely deprecated, enable the final
6882 part of "Proposal 110: Avoiding infinite length circuits" by
6883 refusing all circuit-extend requests that do not use a relay_early
6884 cell. This change helps Tor resist a class of denial-of-service
6885 attacks by limiting the maximum circuit length.
6886 - Adjust the number of introduction points that a hidden service
6887 will try to maintain based on how long its introduction points
6888 remain in use and how many introductions they handle. Fixes
6890 - Try to use system facilities for enumerating local interface
6891 addresses, before falling back to our old approach (which was
6892 binding a UDP socket, and calling getsockname() on it). That
6893 approach was scaring OS X users whose draconian firewall
6894 software warned about binding to UDP sockets, regardless of
6895 whether packets were sent. Now we try to use getifaddrs(),
6896 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6897 system supports. Resolves ticket 1827.
6899 o Major security workaround:
6900 - When building or running with any version of OpenSSL earlier
6901 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6902 versions have a bug (CVE-2011-4576) in which their block cipher
6903 padding includes uninitialized data, potentially leaking sensitive
6904 information to any peer with whom they make a SSLv3 connection. Tor
6905 does not use SSL v3 by default, but a hostile client or server
6906 could force an SSLv3 connection in order to gain information that
6907 they shouldn't have been able to get. The best solution here is to
6908 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6909 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6910 to make sure that the bug can't happen.
6913 - Fix the SOCKET_OK test that we use to tell when socket
6914 creation fails so that it works on Win64. Fixes part of bug 4533;
6915 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6916 - Correct our replacements for the timeradd() and timersub() functions
6917 on platforms that lack them (for example, Windows). The timersub()
6918 function is used when expiring circuits, while timeradd() is
6919 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6920 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
6921 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
6922 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
6923 bug at runtime, not compile time, because some distributions hack
6924 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
6925 on 0.2.3.9-alpha. Found by Pascal.
6927 o Minor features (controller):
6928 - Use absolute path names when reporting the torrc filename in the
6929 control protocol, so a controller can more easily find the torrc
6930 file. Resolves bug 1101.
6931 - Extend the control protocol to report flags that control a circuit's
6932 path selection in CIRC events and in replies to 'GETINFO
6933 circuit-status'. Implements part of ticket 2411.
6934 - Extend the control protocol to report the hidden service address
6935 and current state of a hidden-service-related circuit in CIRC
6936 events and in replies to 'GETINFO circuit-status'. Implements part
6938 - When reporting the path to the cookie file to the controller,
6939 give an absolute path. Resolves ticket 4881.
6940 - Allow controllers to request an event notification whenever a
6941 circuit is cannibalized or its purpose is changed. Implements
6942 part of ticket 3457.
6943 - Include the creation time of a circuit in CIRC and CIRC2
6944 control-port events and the list produced by the 'GETINFO
6945 circuit-status' control-port command.
6947 o Minor features (directory authorities):
6948 - Directory authorities now reject versions of Tor older than
6949 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6950 inclusive. These versions accounted for only a small fraction of
6951 the Tor network, and have numerous known security issues. Resolves
6953 - Authority operators can now vote for all relays in a given
6954 set of countries to be BadDir/BadExit/Invalid/Rejected.
6955 - Provide two consensus parameters (FastFlagMinThreshold and
6956 FastFlagMaxThreshold) to control the range of allowable bandwidths
6957 for the Fast directory flag. These allow authorities to run
6958 experiments on appropriate requirements for being a "Fast" node.
6959 The AuthDirFastGuarantee config value still applies. Implements
6961 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6962 directory authority option (introduced in Tor 0.2.2.34).
6964 o Minor features (other):
6965 - Don't disable the DirPort when we cannot exceed our AccountingMax
6966 limit during this interval because the effective bandwidthrate is
6967 low enough. This is useful in a situation where AccountMax is only
6968 used as an additional safeguard or to provide statistics.
6969 - Prepend an informative header to generated dynamic_dh_params files.
6970 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6971 EntryNodes will have no effect. Resolves issue 2571.
6972 - Log more useful messages when we fail to disable debugger
6974 - Log which authority we're missing votes from when we go to fetch
6975 them from the other auths.
6976 - Log (at debug level) whenever a circuit's purpose is changed.
6977 - Add missing documentation for the MaxClientCircuitsPending,
6978 UseMicrodescriptors, UserspaceIOCPBuffers, and
6979 _UseFilteringSSLBufferevents options, all introduced during
6981 - Update to the January 3 2012 Maxmind GeoLite Country database.
6983 o Minor bugfixes (hidden services):
6984 - Don't close hidden service client circuits which have almost
6985 finished connecting to their destination when they reach
6986 the normal circuit-build timeout. Previously, we would close
6987 introduction circuits which are waiting for an acknowledgement
6988 from the introduction point, and rendezvous circuits which have
6989 been specified in an INTRODUCE1 cell sent to a hidden service,
6990 after the normal CBT. Now, we mark them as 'timed out', and launch
6991 another rendezvous attempt in parallel. This behavior change can
6992 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
6993 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
6994 - Don't close hidden-service-side rendezvous circuits when they
6995 reach the normal circuit-build timeout. This behavior change can
6996 be disabled using the new
6997 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
6998 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
6999 - Make sure we never mark the wrong rendezvous circuit as having
7000 had its introduction cell acknowleged by the introduction-point
7001 relay. Previously, when we received an INTRODUCE_ACK cell on a
7002 client-side hidden-service introduction circuit, we might have
7003 marked a rendezvous circuit other than the one we specified in
7004 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
7005 a warning message and interfered with the hidden service
7006 connection-establishment process. Fixes bug 4759; bugfix on
7007 0.2.3.3-alpha, when we added the stream-isolation feature which
7008 might cause Tor to open multiple rendezvous circuits for the same
7010 - Don't trigger an assertion failure when we mark a new client-side
7011 hidden-service introduction circuit for close during the process
7012 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
7015 o Minor bugfixes (log messages):
7016 - Correctly spell "connect" in a log message on failure to create a
7017 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
7019 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7020 Fixes bug 4856; bugfix on Tor 0.0.6.
7021 - Fix the log message describing how we work around discovering
7022 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7023 4837; bugfix on 0.2.2.9-alpha.
7024 - When logging about a disallowed .exit name, do not also call it
7025 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7027 o Minor bugfixes (build fixes):
7028 - During configure, detect when we're building with clang version
7029 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7030 CFLAGS. clang doesn't support them yet.
7031 - During configure, search for library containing cos function as
7032 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7033 against libm was hard-coded before. Fixes the first part of bug
7034 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7036 - Detect attempts to build Tor on (as yet hypothetical) versions
7037 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7038 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7039 - Preprocessor directives should not be put inside the arguments
7040 of a macro. This would break compilation with GCC releases prior
7041 to version 3.3. We would never recommend such an old GCC version,
7042 but it is apparently required for binary compatibility on some
7043 platforms (namely, certain builds of Haiku). Fixes the other part
7044 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
7047 o Minor bugfixes (other):
7048 - Older Linux kernels erroneously respond to strange nmap behavior
7049 by having accept() return successfully with a zero-length
7050 socket. When this happens, just close the connection. Previously,
7051 we would try harder to learn the remote address: but there was
7052 no such remote address to learn, and our method for trying to
7053 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7054 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7055 - Fix null-pointer access that could occur if TLS allocation failed.
7056 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
7057 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
7058 accidentally been reverted.
7059 - Fix our implementation of crypto_random_hostname() so it can't
7060 overflow on ridiculously large inputs. (No Tor version has ever
7061 provided this kind of bad inputs, but let's be correct in depth.)
7062 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
7063 - Find more places in the code that should have been testing for
7064 invalid sockets using the SOCKET_OK macro. Required for a fix
7065 for bug 4533. Bugfix on 0.2.2.28-beta.
7066 - Fix an assertion failure when, while running with bufferevents, a
7067 connection finishes connecting after it is marked for close, but
7068 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
7069 - test_util_spawn_background_ok() hardcoded the expected value
7070 for ENOENT to 2. This isn't portable as error numbers are
7071 platform specific, and particularly the hurd has ENOENT at
7072 0x40000002. Construct expected string at runtime, using the correct
7073 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
7074 - Reject attempts to disable DisableDebuggerAttachment while Tor is
7075 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
7076 - Use an appropriate-width type for sockets in tor-fw-helper on
7077 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
7080 - When sending or relaying a RELAY_EARLY cell, we used to convert
7081 it to a RELAY cell if the connection was using the v1 link
7082 protocol. This was a workaround for older versions of Tor, which
7083 didn't handle RELAY_EARLY cells properly. Now that all supported
7084 versions can handle RELAY_EARLY cells, and now that we're enforcing
7085 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7086 remove this workaround. Addresses bug 4786.
7088 o Code simplifications and refactoring:
7089 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7090 own homebrewed ssl_state_to_string() replacement. Patch from
7091 Emile Snyder. Fixes bug 4653.
7092 - Use macros to indicate OpenSSL versions, so we don't need to worry
7093 about accidental hexadecimal bit shifts.
7094 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7096 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7097 - Use the smartlist_add_asprintf() alias more consistently.
7098 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7099 invalid value, rather than just -1.
7100 - Rename a handful of old identifiers, mostly related to crypto
7101 structures and crypto functions. By convention, our "create an
7102 object" functions are called "type_new()", our "free an object"
7103 functions are called "type_free()", and our types indicate that
7104 they are types only with a final "_t". But a handful of older
7105 types and functions broke these rules, with function names like
7106 "type_create" or "subsystem_op_type", or with type names like
7110 Changes in version 0.2.3.10-alpha - 2011-12-16
7111 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
7112 Tor's buffers code. Absolutely everybody should upgrade.
7114 The bug relied on an incorrect calculation when making data continuous
7115 in one of our IO buffers, if the first chunk of the buffer was
7116 misaligned by just the wrong amount. The miscalculation would allow an
7117 attacker to overflow a piece of heap-allocated memory. To mount this
7118 attack, the attacker would need to either open a SOCKS connection to
7119 Tor's SocksPort (usually restricted to localhost), or target a Tor
7120 instance configured to make its connections through a SOCKS proxy
7121 (which Tor does not do by default).
7123 Good security practice requires that all heap-overflow bugs should be
7124 presumed to be exploitable until proven otherwise, so we are treating
7125 this as a potential code execution attack. Please upgrade immediately!
7126 This bug does not affect bufferevents-based builds of Tor. Special
7127 thanks to "Vektor" for reporting this issue to us!
7129 This release also contains a few minor bugfixes for issues discovered
7133 - Fix a heap overflow bug that could occur when trying to pull
7134 data into the first chunk of a buffer, when that chunk had
7135 already had some data drained from it. Fixes CVE-2011-2778;
7136 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7139 - If we can't attach streams to a rendezvous circuit when we
7140 finish connecting to a hidden service, clear the rendezvous
7141 circuit's stream-isolation state and try to attach streams
7142 again. Previously, we cleared rendezvous circuits' isolation
7143 state either too early (if they were freshly built) or not at all
7144 (if they had been built earlier and were cannibalized). Bugfix on
7145 0.2.3.3-alpha; fixes bug 4655.
7146 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
7147 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
7148 - Fix an assertion failure when a relay with accounting enabled
7149 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
7152 - Update to the December 6 2011 Maxmind GeoLite Country database.
7155 Changes in version 0.2.2.35 - 2011-12-16
7156 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
7157 buffers code. Absolutely everybody should upgrade.
7159 The bug relied on an incorrect calculation when making data continuous
7160 in one of our IO buffers, if the first chunk of the buffer was
7161 misaligned by just the wrong amount. The miscalculation would allow an
7162 attacker to overflow a piece of heap-allocated memory. To mount this
7163 attack, the attacker would need to either open a SOCKS connection to
7164 Tor's SocksPort (usually restricted to localhost), or target a Tor
7165 instance configured to make its connections through a SOCKS proxy
7166 (which Tor does not do by default).
7168 Good security practice requires that all heap-overflow bugs should be
7169 presumed to be exploitable until proven otherwise, so we are treating
7170 this as a potential code execution attack. Please upgrade immediately!
7171 This bug does not affect bufferevents-based builds of Tor. Special
7172 thanks to "Vektor" for reporting this issue to us!
7174 Tor 0.2.2.35 also fixes several bugs in previous versions, including
7175 crash bugs for unusual configurations, and a long-term bug that
7176 would prevent Tor from starting on Windows machines with draconian
7179 With this release, we remind everyone that 0.2.0.x has reached its
7180 formal end-of-life. Those Tor versions have many known flaws, and
7181 nobody should be using them. You should upgrade -- ideally to the
7182 0.2.2.x series. If you're using a Linux or BSD and its packages are
7183 obsolete, stop using those packages and upgrade anyway.
7185 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
7186 longer receive support after some time in early 2012.
7189 - Fix a heap overflow bug that could occur when trying to pull
7190 data into the first chunk of a buffer, when that chunk had
7191 already had some data drained from it. Fixes CVE-2011-2778;
7192 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7193 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7194 that it doesn't attempt to allocate a socketpair. This could cause
7195 some problems on Windows systems with overzealous firewalls. Fix for
7196 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7198 - If we mark an OR connection for close based on a cell we process,
7199 don't process any further cells on it. We already avoid further
7200 reads on marked-for-close connections, but now we also discard the
7201 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7202 which was the first version where we might mark a connection for
7203 close based on processing a cell on it.
7204 - Correctly sanity-check that we don't underflow on a memory
7205 allocation (and then assert) for hidden service introduction
7206 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7207 bugfix on 0.2.1.5-alpha.
7208 - Fix a memory leak when we check whether a hidden service
7209 descriptor has any usable introduction points left. Fixes bug
7210 4424. Bugfix on 0.2.2.25-alpha.
7211 - Don't crash when we're running as a relay and don't have a GeoIP
7212 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
7213 we've had in the 0.2.3.x branch already.
7214 - When running as a client, do not print a misleading (and plain
7215 wrong) log message that we're collecting "directory request"
7216 statistics: clients don't collect statistics. Also don't create a
7217 useless (because empty) stats file in the stats/ directory. Fixes
7218 bug 4353; bugfix on 0.2.2.34.
7221 - Detect failure to initialize Libevent. This fix provides better
7222 detection for future instances of bug 4457.
7223 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7224 function. This was eating up hideously large amounts of time on some
7225 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7226 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7227 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7229 - Don't warn about unused log_mutex in log.c when building with
7230 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7231 0.1.0.6-rc which introduced --disable-threads.
7232 - When configuring, starting, or stopping an NT service, stop
7233 immediately after the service configuration attempt has succeeded
7234 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7235 - When sending a NETINFO cell, include the original address
7236 received for the other side, not its canonical address. Found
7237 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7238 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
7239 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7240 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7241 occurred when a client tried to fetch a descriptor for a bridge
7242 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7243 - Backport fixes for a pair of compilation warnings on Windows.
7244 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
7245 - If we had ever tried to call tor_addr_to_str on an address of
7246 unknown type, we would have done a strdup on an uninitialized
7247 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7248 Reported by "troll_un".
7249 - Correctly detect and handle transient lookup failures from
7250 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7251 Reported by "troll_un".
7252 - Fix null-pointer access that could occur if TLS allocation failed.
7253 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7254 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7255 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7258 - Add two new config options for directory authorities:
7259 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7260 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7261 that is always sufficient to satisfy the bandwidth requirement for
7262 the Guard flag. Now it will be easier for researchers to simulate
7263 Tor networks with different values. Resolves ticket 4484.
7264 - When Tor ignores a hidden service specified in its configuration,
7265 include the hidden service's directory in the warning message.
7266 Previously, we would only tell the user that some hidden service
7267 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7268 - Update to the December 6 2011 Maxmind GeoLite Country database.
7270 o Packaging changes:
7271 - Make it easier to automate expert package builds on Windows,
7272 by removing an absolute path from makensis.exe command.
7275 Changes in version 0.2.1.32 - 2011-12-16
7276 Tor 0.2.1.32 backports important security and privacy fixes for
7277 oldstable. This release is intended only for package maintainers and
7278 others who cannot use the 0.2.2 stable series. All others should be
7279 using Tor 0.2.2.x or newer.
7281 The Tor 0.2.1.x series will reach formal end-of-life some time in
7282 early 2012; we will stop releasing patches for it then.
7284 o Major bugfixes (also included in 0.2.2.x):
7285 - Correctly sanity-check that we don't underflow on a memory
7286 allocation (and then assert) for hidden service introduction
7287 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7288 bugfix on 0.2.1.5-alpha.
7289 - Fix a heap overflow bug that could occur when trying to pull
7290 data into the first chunk of a buffer, when that chunk had
7291 already had some data drained from it. Fixes CVE-2011-2778;
7292 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7295 - Update to the December 6 2011 Maxmind GeoLite Country database.
7298 Changes in version 0.2.3.9-alpha - 2011-12-08
7299 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
7300 a "DisableNetwork" security feature that bundles can use to avoid
7301 touching the network until bridges are configured, moves forward on
7302 the pluggable transport design, fixes a flaw in the hidden service
7303 design that unnecessarily prevented clients with wrong clocks from
7304 reaching hidden services, and fixes a wide variety of other issues.
7307 - Clients can now connect to private bridges over IPv6. Bridges
7308 still need at least one IPv4 address in order to connect to
7309 other relays. Note that we don't yet handle the case where the
7310 user has two bridge lines for the same bridge (one IPv4, one
7311 IPv6). Implements parts of proposal 186.
7312 - New "DisableNetwork" config option to prevent Tor from launching any
7313 connections or accepting any connections except on a control port.
7314 Bundles and controllers can set this option before letting Tor talk
7315 to the rest of the network, for example to prevent any connections
7316 to a non-bridge address. Packages like Orbot can also use this
7317 option to instruct Tor to save power when the network is off.
7318 - Clients and bridges can now be configured to use a separate
7319 "transport" proxy. This approach makes the censorship arms race
7320 easier by allowing bridges to use protocol obfuscation plugins. It
7321 implements the "managed proxy" part of proposal 180 (ticket 3472).
7322 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
7323 implementation. It makes AES_CTR about 7% faster than our old one
7324 (which was about 10% faster than the one OpenSSL used to provide).
7325 Resolves ticket 4526.
7326 - Add a "tor2web mode" for clients that want to connect to hidden
7327 services non-anonymously (and possibly more quickly). As a safety
7328 measure to try to keep users from turning this on without knowing
7329 what they are doing, tor2web mode must be explicitly enabled at
7330 compile time, and a copy of Tor compiled to run in tor2web mode
7331 cannot be used as a normal Tor client. Implements feature 2553.
7332 - Add experimental support for running on Windows with IOCP and no
7333 kernel-space socket buffers. This feature is controlled by a new
7334 "UserspaceIOCPBuffers" config option (off by default), which has
7335 no effect unless Tor has been built with support for bufferevents,
7336 is running on Windows, and has enabled IOCP. This may, in the long
7337 run, help solve or mitigate bug 98.
7338 - Use a more secure consensus parameter voting algorithm. Now at
7339 least three directory authorities or a majority of them must
7340 vote on a given parameter before it will be included in the
7341 consensus. Implements proposal 178.
7344 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
7345 They used to check that the timestamp was within 30 minutes
7346 of their system clock, so they could cap the size of their
7347 replay-detection cache, but that approach unnecessarily refused
7348 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
7349 the v3 intro-point protocol (the first one which sent a timestamp
7350 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
7351 - Only use the EVP interface when AES acceleration is enabled,
7352 to avoid a 5-7% performance regression. Resolves issue 4525;
7353 bugfix on 0.2.3.8-alpha.
7355 o Privacy/anonymity features (bridge detection):
7356 - Make bridge SSL certificates a bit more stealthy by using random
7357 serial numbers, in the same fashion as OpenSSL when generating
7358 self-signed certificates. Implements ticket 4584.
7359 - Introduce a new config option "DynamicDHGroups", enabled by
7360 default, which provides each bridge with a unique prime DH modulus
7361 to be used during SSL handshakes. This option attempts to help
7362 against censors who might use the Apache DH modulus as a static
7363 identifier for bridges. Addresses ticket 4548.
7365 o Minor features (new/different config options):
7366 - New configuration option "DisableDebuggerAttachment" (on by default)
7367 to prevent basic debugging attachment attempts by other processes.
7368 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
7369 - Allow MapAddress directives to specify matches against super-domains,
7370 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
7371 Implements issue 933.
7372 - Slightly change behavior of "list" options (that is, config
7373 options that can appear more than once) when they appear both in
7374 torrc and on the command line. Previously, the command-line options
7375 would be appended to the ones from torrc. Now, the command-line
7376 options override the torrc options entirely. This new behavior
7377 allows the user to override list options (like exit policies and
7378 ports to listen on) from the command line, rather than simply
7379 appending to the list.
7380 - You can get the old (appending) command-line behavior for "list"
7381 options by prefixing the option name with a "+".
7382 - You can remove all the values for a "list" option from the command
7383 line without adding any new ones by prefixing the option name
7385 - Add experimental support for a "defaults" torrc file to be parsed
7386 before the regular torrc. Torrc options override the defaults file's
7387 options in the same way that the command line overrides the torrc.
7388 The SAVECONF controller command saves only those options which
7389 differ between the current configuration and the defaults file. HUP
7390 reloads both files. (Note: This is an experimental feature; its
7391 behavior will probably be refined in future 0.2.3.x-alpha versions
7392 to better meet packagers' needs.) Implements task 4552.
7395 - Try to make the introductory warning message that Tor prints on
7396 startup more useful for actually finding help and information.
7397 Resolves ticket 2474.
7398 - Running "make version" now displays the version of Tor that
7399 we're about to build. Idea from katmagic; resolves issue 4400.
7400 - Expire old or over-used hidden service introduction points.
7401 Required by fix for bug 3460.
7402 - Move the replay-detection cache for the RSA-encrypted parts of
7403 INTRODUCE2 cells to the introduction point data structures.
7404 Previously, we would use one replay-detection cache per hidden
7405 service. Required by fix for bug 3460.
7406 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
7407 public key replay-detection cache from 60 minutes to 5 minutes. This
7408 replay-detection cache is now used only to detect multiple
7409 INTRODUCE2 cells specifying the same rendezvous point, so we can
7410 avoid launching multiple simultaneous attempts to connect to it.
7412 o Minor bugfixes (on Tor 0.2.2.x and earlier):
7413 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7414 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7416 - Fix a minor formatting issue in one of tor-gencert's error messages.
7418 - Prevent a false positive from the check-spaces script, by disabling
7419 the "whitespace between function name and (" check for functions
7421 - Fix a log message suggesting that people contact a non-existent
7422 email address. Fixes bug 3448.
7423 - Fix null-pointer access that could occur if TLS allocation failed.
7424 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7425 - Report a real bootstrap problem to the controller on router
7426 identity mismatch. Previously we just said "foo", which probably
7427 made a lot of sense at the time. Fixes bug 4169; bugfix on
7429 - If we had ever tried to call tor_addr_to_str() on an address of
7430 unknown type, we would have done a strdup() on an uninitialized
7431 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7432 Reported by "troll_un".
7433 - Correctly detect and handle transient lookup failures from
7434 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7435 Reported by "troll_un".
7436 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7437 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7438 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
7439 bug 4532; found by "troll_un".
7441 o Minor bugfixes (on Tor 0.2.3.x):
7442 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
7444 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
7445 circuit for use as a hidden service client's rendezvous point.
7446 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
7447 with help from wanoskarnet.
7448 - Restore behavior of overriding SocksPort, ORPort, and similar
7449 options from the command line. Bugfix on 0.2.3.3-alpha.
7452 - Properly handle the case where the build-tree is not the same
7453 as the source tree when generating src/common/common_sha1.i,
7454 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7455 bugfix on 0.2.0.1-alpha.
7457 o Code simplifications, cleanups, and refactorings:
7458 - Remove the pure attribute from all functions that used it
7459 previously. In many cases we assigned it incorrectly, because the
7460 functions might assert or call impure functions, and we don't have
7461 evidence that keeping the pure attribute is worthwhile. Implements
7462 changes suggested in ticket 4421.
7463 - Remove some dead code spotted by coverity. Fixes cid 432.
7464 Bugfix on 0.2.3.1-alpha, closes bug 4637.
7467 Changes in version 0.2.3.8-alpha - 2011-11-22
7468 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
7469 socketpair-related bug that has been bothering Windows users. It adds
7470 support to serve microdescriptors to controllers, so Vidalia's network
7471 map can resume listing relays (once Vidalia implements its side),
7472 and adds better support for hardware AES acceleration. Finally, it
7473 starts the process of adjusting the bandwidth cutoff for getting the
7474 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
7475 that tiny relays harm performance more than they help network capacity.
7478 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7479 that it doesn't attempt to allocate a socketpair. This could cause
7480 some problems on Windows systems with overzealous firewalls. Fix for
7481 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7483 - Correctly sanity-check that we don't underflow on a memory
7484 allocation (and then assert) for hidden service introduction
7485 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7486 bugfix on 0.2.1.5-alpha.
7487 - Remove the artificially low cutoff of 20KB to guarantee the Fast
7488 flag. In the past few years the average relay speed has picked
7489 up, and while the "top 7/8 of the network get the Fast flag" and
7490 "all relays with 20KB or more of capacity get the Fast flag" rules
7491 used to have the same result, now the top 7/8 of the network has
7492 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
7493 - Fix a rare assertion failure when checking whether a v0 hidden
7494 service descriptor has any usable introduction points left, and
7495 we don't have enough information to build a circuit to the first
7496 intro point named in the descriptor. The HS client code in
7497 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
7498 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
7499 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
7500 - Make bridge authorities not crash when they are asked for their own
7501 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
7502 - When running as a client, do not print a misleading (and plain
7503 wrong) log message that we're collecting "directory request"
7504 statistics: clients don't collect statistics. Also don't create a
7505 useless (because empty) stats file in the stats/ directory. Fixes
7506 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
7509 - Allow Tor controllers like Vidalia to obtain the microdescriptor
7510 for a relay by identity digest or nickname. Previously,
7511 microdescriptors were only available by their own digests, so a
7512 controller would have to ask for and parse the whole microdescriptor
7513 consensus in order to look up a single relay's microdesc. Fixes
7514 bug 3832; bugfix on 0.2.3.1-alpha.
7515 - Use OpenSSL's EVP interface for AES encryption, so that all AES
7516 operations can use hardware acceleration (if present). Resolves
7519 o Minor bugfixes (on 0.2.2.x and earlier):
7520 - Detect failure to initialize Libevent. This fix provides better
7521 detection for future instances of bug 4457.
7522 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7523 function. This was eating up hideously large amounts of time on some
7524 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7525 - Don't warn about unused log_mutex in log.c when building with
7526 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7527 0.1.0.6-rc which introduced --disable-threads.
7528 - Allow manual 'authenticate' commands to the controller interface
7529 from netcat (nc) as well as telnet. We were rejecting them because
7530 they didn't come with the expected whitespace at the end of the
7531 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
7532 - Fix some (not actually triggerable) buffer size checks in usage of
7533 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
7535 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
7536 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
7537 - When configuring, starting, or stopping an NT service, stop
7538 immediately after the service configuration attempt has succeeded
7539 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7540 - When sending a NETINFO cell, include the original address
7541 received for the other side, not its canonical address. Found
7542 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7543 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
7544 can pick them up when the tests aren't disabled. Bugfix on
7545 0.2.2.4-alpha which introduced tinytest.
7546 - Fix a memory leak when we check whether a hidden service
7547 descriptor has any usable introduction points left. Fixes bug
7548 4424. Bugfix on 0.2.2.25-alpha.
7549 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7550 occurred when a client tried to fetch a descriptor for a bridge
7551 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7553 o Minor bugfixes (on 0.2.3.x):
7554 - Make util unit tests build correctly with MSVC. Bugfix on
7555 0.2.3.3-alpha. Patch by Gisle Vanem.
7556 - Successfully detect AUTH_CHALLENGE cells with no recognized
7557 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
7559 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
7560 it should still send a NETINFO cell to allow the connection to
7561 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
7563 - Log less loudly when we get an invalid authentication certificate
7564 from a source other than a directory authority: it's not unusual
7565 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
7567 - Tolerate servers with more clock skew in their authentication
7568 certificates than previously. Fixes bug 4371; bugfix on
7570 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
7571 on 0.2.3.4-alpha and 0.2.3.6-alpha.
7574 - Add two new config options for directory authorities:
7575 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7576 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7577 that is always sufficient to satisfy the bandwidth requirement for
7578 the Guard flag. Now it will be easier for researchers to simulate
7579 Tor networks with different values. Resolves ticket 4484.
7580 - When Tor ignores a hidden service specified in its configuration,
7581 include the hidden service's directory in the warning message.
7582 Previously, we would only tell the user that some hidden service
7583 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7584 - When we fail to initialize Libevent, retry with IOCP disabled so we
7585 don't need to turn on multi-threading support in Libevent, which in
7586 turn requires a working socketpair(). This is a workaround for bug
7587 4457, which affects Libevent versions from 2.0.1-alpha through
7589 - Detect when we try to build on a platform that doesn't define
7590 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7591 - Update to the November 1 2011 Maxmind GeoLite Country database.
7593 o Packaging changes:
7594 - Make it easier to automate expert package builds on Windows,
7595 by removing an absolute path from makensis.exe command.
7597 o Code simplifications and refactoring:
7598 - Remove some redundant #include directives throughout the code.
7599 Patch from Andrea Gelmini.
7600 - Unconditionally use OpenSSL's AES implementation instead of our
7601 old built-in one. OpenSSL's AES has been better for a while, and
7602 relatively few servers should still be on any version of OpenSSL
7603 that doesn't have good optimized assembly AES.
7604 - Use the name "CERTS" consistently to refer to the new cell type;
7605 we were calling it CERT in some places and CERTS in others.
7608 - Numerous new unit tests for functions in util.c and address.c by
7610 - The long-disabled benchmark tests are now split into their own
7611 ./src/test/bench binary.
7612 - The benchmark tests can now use more accurate timers than
7613 gettimeofday() when such timers are available.
7616 Changes in version 0.2.3.7-alpha - 2011-10-30
7617 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
7618 the new v3 handshake. It also resolves yet another bridge address
7622 - If we mark an OR connection for close based on a cell we process,
7623 don't process any further cells on it. We already avoid further
7624 reads on marked-for-close connections, but now we also discard the
7625 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7626 which was the first version where we might mark a connection for
7627 close based on processing a cell on it.
7628 - Fix a double-free bug that would occur when we received an invalid
7629 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
7630 bugfix on 0.2.3.6-alpha.
7631 - Bridges no longer include their address in NETINFO cells on outgoing
7632 OR connections, to allow them to blend in better with clients.
7633 Removes another avenue for enumerating bridges. Reported by
7634 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
7635 cells were introduced.
7638 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
7639 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7642 Changes in version 0.2.3.6-alpha - 2011-10-26
7643 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
7644 anonymity vulnerability where an attacker can deanonymize Tor
7645 users. Everybody should upgrade.
7647 This release also features support for a new v3 connection handshake
7648 protocol, and fixes to make hidden service connections more robust.
7651 - Implement a new handshake protocol (v3) for authenticating Tors to
7652 each other over TLS. It should be more resistant to fingerprinting
7653 than previous protocols, and should require less TLS hacking for
7654 future Tor implementations. Implements proposal 176.
7655 - Allow variable-length padding cells to disguise the length of
7656 Tor's TLS records. Implements part of proposal 184.
7658 o Privacy/anonymity fixes (clients):
7659 - Clients and bridges no longer send TLS certificate chains on
7660 outgoing OR connections. Previously, each client or bridge would
7661 use the same cert chain for all outgoing OR connections until
7662 its IP address changes, which allowed any relay that the client
7663 or bridge contacted to determine which entry guards it is using.
7664 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7665 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7666 no longer considers that connection as suitable for satisfying a
7667 circuit EXTEND request. Now relays can protect clients from the
7668 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7669 - Directory authorities no longer assign the Guard flag to relays
7670 that haven't upgraded to the above "refuse EXTEND requests
7671 to client connections" fix. Now directory authorities can
7672 protect clients from the CVE-2011-2768 issue even if neither
7673 the clients nor the relays have upgraded yet. There's a new
7674 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7675 to let us transition smoothly, else tomorrow there would be no
7678 o Major bugfixes (hidden services):
7679 - Improve hidden service robustness: when an attempt to connect to
7680 a hidden service ends, be willing to refetch its hidden service
7681 descriptors from each of the HSDir relays responsible for them
7682 immediately. Previously, we would not consider refetching the
7683 service's descriptors from each HSDir for 15 minutes after the last
7684 fetch, which was inconvenient if the hidden service was not running
7685 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
7686 - When one of a hidden service's introduction points appears to be
7687 unreachable, stop trying it. Previously, we would keep trying
7688 to build circuits to the introduction point until we lost the
7689 descriptor, usually because the user gave up and restarted Tor.
7690 Partly fixes bug 3825.
7691 - Don't launch a useless circuit after failing to use one of a
7692 hidden service's introduction points. Previously, we would
7693 launch a new introduction circuit, but not set the hidden service
7694 which that circuit was intended to connect to, so it would never
7695 actually be used. A different piece of code would then create a
7696 new introduction circuit correctly. Bug reported by katmagic and
7697 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7699 o Major bugfixes (other):
7700 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7701 that they initiated. Relays could distinguish incoming bridge
7702 connections from client connections, creating another avenue for
7703 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7704 Found by "frosty_un".
7705 - Don't update the AccountingSoftLimitHitAt state file entry whenever
7706 tor gets started. This prevents a wrong average bandwidth
7707 estimate, which would cause relays to always start a new accounting
7708 interval at the earliest possible moment. Fixes bug 2003; bugfix
7709 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
7710 immensely in tracking this bug down.
7711 - Fix a crash bug when changing node restrictions while a DNS lookup
7712 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7715 o Minor bugfixes (on 0.2.2.x and earlier):
7716 - When a hidden service turns an extra service-side introduction
7717 circuit into a general-purpose circuit, free the rend_data and
7718 intro_key fields first, so we won't leak memory if the circuit
7719 is cannibalized for use as another service-side introduction
7720 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7721 - Rephrase the log message emitted if the TestSocks check is
7722 successful. Patch from Fabian Keil; fixes bug 4094.
7723 - Bridges now skip DNS self-tests, to act a little more stealthily.
7724 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7725 bridges. Patch by "warms0x".
7726 - Remove a confusing dollar sign from the example fingerprint in the
7727 man page, and also make the example fingerprint a valid one. Fixes
7728 bug 4309; bugfix on 0.2.1.3-alpha.
7729 - Fix internal bug-checking logic that was supposed to catch
7730 failures in digest generation so that it will fail more robustly
7731 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7732 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7733 - Report any failure in init_keys() calls launched because our
7734 IP address has changed. Spotted by Coverity Scan. Bugfix on
7735 0.1.1.4-alpha; fixes CID 484.
7737 o Minor bugfixes (on 0.2.3.x):
7738 - Fix a bug in configure.in that kept it from building a configure
7739 script with autoconf versions earlier than 2.61. Fixes bug 2430;
7740 bugfix on 0.2.3.1-alpha.
7741 - Don't warn users that they are exposing a client port to the
7742 Internet if they have specified an RFC1918 address. Previously,
7743 we would warn if the user had specified any non-loopback
7744 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
7745 - Fix memory leaks in the failing cases of the new SocksPort and
7746 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
7747 fixes coverity CIDs 485, 486, and 487.
7750 - When a hidden service's introduction point times out, consider
7751 trying it again during the next attempt to connect to the
7752 HS. Previously, we would not try it again unless a newly fetched
7753 descriptor contained it. Required by fixes for bugs 1297 and 3825.
7754 - The next version of Windows will be called Windows 8, and it has
7755 a major version of 6, minor version of 2. Correctly identify that
7756 version instead of calling it "Very recent version". Resolves
7757 ticket 4153; reported by funkstar.
7758 - The Bridge Authority now writes statistics on how many bridge
7759 descriptors it gave out in total, and how many unique descriptors
7760 it gave out. It also lists how often the most and least commonly
7761 fetched descriptors were given out, as well as the median and
7762 25th/75th percentile. Implements tickets 4200 and 4294.
7763 - Update to the October 4 2011 Maxmind GeoLite Country database.
7765 o Code simplifications and refactoring:
7766 - Remove some old code to remember statistics about which descriptors
7767 we've served as a directory mirror. The feature wasn't used and
7768 is outdated now that microdescriptors are around.
7769 - Rename Tor functions that turn strings into addresses, so that
7770 "parse" indicates that no hostname resolution occurs, and
7771 "lookup" indicates that hostname resolution may occur. This
7772 should help prevent mistakes in the future. Fixes bug 3512.
7775 Changes in version 0.2.2.34 - 2011-10-26
7776 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7777 can deanonymize Tor users. Everybody should upgrade.
7779 The attack relies on four components: 1) Clients reuse their TLS cert
7780 when talking to different relays, so relays can recognize a user by
7781 the identity key in her cert. 2) An attacker who knows the client's
7782 identity key can probe each guard relay to see if that identity key
7783 is connected to that guard relay right now. 3) A variety of active
7784 attacks in the literature (starting from "Low-Cost Traffic Analysis
7785 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7786 discover the guard relays that a Tor user visiting the website is using.
7787 4) Clients typically pick three guards at random, so the set of guards
7788 for a given user could well be a unique fingerprint for her. This
7789 release fixes components #1 and #2, which is enough to block the attack;
7790 the other two remain as open research problems. Special thanks to
7791 "frosty_un" for reporting the issue to us!
7793 Clients should upgrade so they are no longer recognizable by the TLS
7794 certs they present. Relays should upgrade so they no longer allow a
7795 remote attacker to probe them to test whether unpatched clients are
7796 currently connected to them.
7798 This release also fixes several vulnerabilities that allow an attacker
7799 to enumerate bridge relays. Some bridge enumeration attacks still
7800 remain; see for example proposal 188.
7802 o Privacy/anonymity fixes (clients):
7803 - Clients and bridges no longer send TLS certificate chains on
7804 outgoing OR connections. Previously, each client or bridge would
7805 use the same cert chain for all outgoing OR connections until
7806 its IP address changes, which allowed any relay that the client
7807 or bridge contacted to determine which entry guards it is using.
7808 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7809 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7810 no longer considers that connection as suitable for satisfying a
7811 circuit EXTEND request. Now relays can protect clients from the
7812 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7813 - Directory authorities no longer assign the Guard flag to relays
7814 that haven't upgraded to the above "refuse EXTEND requests
7815 to client connections" fix. Now directory authorities can
7816 protect clients from the CVE-2011-2768 issue even if neither
7817 the clients nor the relays have upgraded yet. There's a new
7818 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7819 to let us transition smoothly, else tomorrow there would be no
7822 o Privacy/anonymity fixes (bridge enumeration):
7823 - Bridge relays now do their directory fetches inside Tor TLS
7824 connections, like all the other clients do, rather than connecting
7825 directly to the DirPort like public relays do. Removes another
7826 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7827 - Bridges relays now build circuits for themselves in a more similar
7828 way to how clients build them. Removes another avenue for
7829 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7830 when bridges were introduced.
7831 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7832 that they initiated. Relays could distinguish incoming bridge
7833 connections from client connections, creating another avenue for
7834 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7835 Found by "frosty_un".
7838 - Fix a crash bug when changing node restrictions while a DNS lookup
7839 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7841 - Don't launch a useless circuit after failing to use one of a
7842 hidden service's introduction points. Previously, we would
7843 launch a new introduction circuit, but not set the hidden service
7844 which that circuit was intended to connect to, so it would never
7845 actually be used. A different piece of code would then create a
7846 new introduction circuit correctly. Bug reported by katmagic and
7847 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7850 - Change an integer overflow check in the OpenBSD_Malloc code so
7851 that GCC is less likely to eliminate it as impossible. Patch
7852 from Mansour Moufid. Fixes bug 4059.
7853 - When a hidden service turns an extra service-side introduction
7854 circuit into a general-purpose circuit, free the rend_data and
7855 intro_key fields first, so we won't leak memory if the circuit
7856 is cannibalized for use as another service-side introduction
7857 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7858 - Bridges now skip DNS self-tests, to act a little more stealthily.
7859 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7860 bridges. Patch by "warms0x".
7861 - Fix internal bug-checking logic that was supposed to catch
7862 failures in digest generation so that it will fail more robustly
7863 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7864 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7865 - Report any failure in init_keys() calls launched because our
7866 IP address has changed. Spotted by Coverity Scan. Bugfix on
7867 0.1.1.4-alpha; fixes CID 484.
7869 o Minor bugfixes (log messages and documentation):
7870 - Remove a confusing dollar sign from the example fingerprint in the
7871 man page, and also make the example fingerprint a valid one. Fixes
7872 bug 4309; bugfix on 0.2.1.3-alpha.
7873 - The next version of Windows will be called Windows 8, and it has
7874 a major version of 6, minor version of 2. Correctly identify that
7875 version instead of calling it "Very recent version". Resolves
7876 ticket 4153; reported by funkstar.
7877 - Downgrade log messages about circuit timeout calibration from
7878 "notice" to "info": they don't require or suggest any human
7879 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7880 bugfix on 0.2.2.14-alpha.
7883 - Turn on directory request statistics by default and include them in
7884 extra-info descriptors. Don't break if we have no GeoIP database.
7885 Backported from 0.2.3.1-alpha; implements ticket 3951.
7886 - Update to the October 4 2011 Maxmind GeoLite Country database.
7889 Changes in version 0.2.1.31 - 2011-10-26
7890 Tor 0.2.1.31 backports important security and privacy fixes for
7891 oldstable. This release is intended only for package maintainers and
7892 others who cannot use the 0.2.2 stable series. All others should be
7893 using Tor 0.2.2.x or newer.
7895 o Security fixes (also included in 0.2.2.x):
7896 - Replace all potentially sensitive memory comparison operations
7897 with versions whose runtime does not depend on the data being
7898 compared. This will help resist a class of attacks where an
7899 adversary can use variations in timing information to learn
7900 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7901 implementation by Robert Ransom based partially on code by DJB.)
7902 - Fix an assert in parsing router descriptors containing IPv6
7903 addresses. This one took down the directory authorities when
7904 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7906 o Privacy/anonymity fixes (also included in 0.2.2.x):
7907 - Clients and bridges no longer send TLS certificate chains on
7908 outgoing OR connections. Previously, each client or bridge would
7909 use the same cert chain for all outgoing OR connections until
7910 its IP address changes, which allowed any relay that the client
7911 or bridge contacted to determine which entry guards it is using.
7912 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7913 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7914 no longer considers that connection as suitable for satisfying a
7915 circuit EXTEND request. Now relays can protect clients from the
7916 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7917 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7918 that they initiated. Relays could distinguish incoming bridge
7919 connections from client connections, creating another avenue for
7920 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7921 Found by "frosty_un".
7922 - When receiving a hidden service descriptor, check that it is for
7923 the hidden service we wanted. Previously, Tor would store any
7924 hidden service descriptors that a directory gave it, whether it
7925 wanted them or not. This wouldn't have let an attacker impersonate
7926 a hidden service, but it did let directories pre-seed a client
7927 with descriptors that it didn't want. Bugfix on 0.0.6.
7928 - Avoid linkability based on cached hidden service descriptors: forget
7929 all hidden service descriptors cached as a client when processing a
7930 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7931 - Make the bridge directory authority refuse to answer directory
7932 requests for "all" descriptors. It used to include bridge
7933 descriptors in its answer, which was a major information leak.
7934 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7935 - Don't attach new streams to old rendezvous circuits after SIGNAL
7936 NEWNYM. Previously, we would keep using an existing rendezvous
7937 circuit if it remained open (i.e. if it were kept open by a
7938 long-lived stream, or if a new stream were attached to it before
7939 Tor could notice that it was old and no longer in use). Bugfix on
7940 0.1.1.15-rc; fixes bug 3375.
7942 o Minor bugfixes (also included in 0.2.2.x):
7943 - When we restart our relay, we might get a successful connection
7944 from the outside before we've started our reachability tests,
7945 triggering a warning: "ORPort found reachable, but I have no
7946 routerinfo yet. Failing to inform controller of success." This
7947 bug was harmless unless Tor is running under a controller
7948 like Vidalia, in which case the controller would never get a
7949 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7951 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7952 enabled. Fixes bug 1526.
7953 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7954 anything since 0.2.1.16-rc.
7955 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7956 None of the cases where we did this before were wrong, but by making
7957 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7958 - Fix a rare crash bug that could occur when a client was configured
7959 with a large number of bridges. Fixes bug 2629; bugfix on
7960 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7961 - Correct the warning displayed when a rendezvous descriptor exceeds
7962 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7964 - Fix an uncommon assertion failure when running with DNSPort under
7965 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7966 - When warning about missing zlib development packages during compile,
7967 give the correct package names. Bugfix on 0.2.0.1-alpha.
7968 - Require that introduction point keys and onion keys have public
7969 exponent 65537. Bugfix on 0.2.0.10-alpha.
7970 - Do not crash when our configuration file becomes unreadable, for
7971 example due to a permissions change, between when we start up
7972 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7974 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7976 - Always NUL-terminate the sun_path field of a sockaddr_un before
7977 passing it to the kernel. (Not a security issue: kernels are
7978 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7979 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7980 - Don't stack-allocate the list of supplementary GIDs when we're
7981 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7982 could take up to 256K, which is way too much stack. Found by
7983 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7985 o Minor bugfixes (only in 0.2.1.x):
7986 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7987 rely on them. Bugfix on 0.2.1.30.
7988 - Use git revisions instead of svn revisions when generating our
7989 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7991 o Minor features (also included in 0.2.2.x):
7992 - Adjust the expiration time on our SSL session certificates to
7993 better match SSL certs seen in the wild. Resolves ticket 4014.
7994 - Allow nameservers with IPv6 address. Resolves bug 2574.
7995 - Update to the October 4 2011 Maxmind GeoLite Country database.
7998 Changes in version 0.2.3.5-alpha - 2011-09-28
7999 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
8000 bridge relays; fixes an assertion error that many users started hitting
8001 today; and adds the ability to refill token buckets more often than
8002 once per second, allowing significant performance improvements.
8005 - Bridge relays now do their directory fetches inside Tor TLS
8006 connections, like all the other clients do, rather than connecting
8007 directly to the DirPort like public relays do. Removes another
8008 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8009 - Bridges relays now build circuits for themselves in a more similar
8010 way to how clients build them. Removes another avenue for
8011 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8012 when bridges were introduced.
8015 - Fix an "Assertion md->held_by_node == 1 failed" error that could
8016 occur when the same microdescriptor was referenced by two node_t
8017 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
8019 o Major features (networking):
8020 - Add a new TokenBucketRefillInterval option to refill token buckets
8021 more frequently than once per second. This should improve network
8022 performance, alleviate queueing problems, and make traffic less
8023 bursty. Implements proposal 183; closes ticket 3630. Design by
8024 Florian Tschorsch and Björn Scheuermann; implementation by
8028 - Change an integer overflow check in the OpenBSD_Malloc code so
8029 that GCC is less likely to eliminate it as impossible. Patch
8030 from Mansour Moufid. Fixes bug 4059.
8032 o Minor bugfixes (usability):
8033 - Downgrade log messages about circuit timeout calibration from
8034 "notice" to "info": they don't require or suggest any human
8035 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8036 bugfix on 0.2.2.14-alpha.
8038 o Minor features (diagnostics):
8039 - When the system call to create a listener socket fails, log the
8040 error message explaining why. This may help diagnose bug 4027.
8043 Changes in version 0.2.3.4-alpha - 2011-09-13
8044 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
8045 tweak to Tor's TLS handshake that makes relays and bridges that run
8046 this new version reachable from Iran again. It also fixes a few new
8047 bugs in 0.2.3.x, and teaches relays to recognize when they're not
8048 listed in the network consensus and republish.
8050 o Major bugfixes (also part of 0.2.2.33):
8051 - Avoid an assertion failure when reloading a configuration with
8052 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8053 3923; bugfix on 0.2.2.25-alpha.
8055 o Minor features (security, also part of 0.2.2.33):
8056 - Check for replays of the public-key encrypted portion of an
8057 INTRODUCE1 cell, in addition to the current check for replays of
8058 the g^x value. This prevents a possible class of active attacks
8059 by an attacker who controls both an introduction point and a
8060 rendezvous point, and who uses the malleability of AES-CTR to
8061 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8062 that these attacks are infeasible (requiring the attacker to send
8063 on the order of zettabytes of altered cells in a short interval),
8064 but we'd rather block them off in case there are any classes of
8065 this attack that we missed. Reported by Willem Pinckaers.
8067 o Minor features (also part of 0.2.2.33):
8068 - Adjust the expiration time on our SSL session certificates to
8069 better match SSL certs seen in the wild. Resolves ticket 4014.
8070 - Change the default required uptime for a relay to be accepted as
8071 a HSDir (hidden service directory) from 24 hours to 25 hours.
8072 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8073 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8074 authorities to abstain from voting on assignment of the HSDir
8075 consensus flag. Related to bug 2649.
8076 - Update to the September 6 2011 Maxmind GeoLite Country database.
8078 o Minor bugfixes (also part of 0.2.2.33):
8079 - Demote the 'replay detected' log message emitted when a hidden
8080 service receives the same Diffie-Hellman public key in two different
8081 INTRODUCE2 cells to info level. A normal Tor client can cause that
8082 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8083 fixes part of bug 2442.
8084 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8085 level. There is nothing that a hidden service's operator can do
8086 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8088 - Clarify a log message specifying the characters permitted in
8089 HiddenServiceAuthorizeClient client names. Previously, the log
8090 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8091 given the impression that every ASCII character between "+" and "_"
8092 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8094 o Build fixes (also part of 0.2.2.33):
8095 - Clean up some code issues that prevented Tor from building on older
8096 BSDs. Fixes bug 3894; reported by "grarpamp".
8097 - Search for a platform-specific version of "ar" when cross-compiling.
8098 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8101 - Fix a bug where the SocksPort option (for example) would get
8102 ignored and replaced by the default if a SocksListenAddress
8103 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
8107 - Relays now try regenerating and uploading their descriptor more
8108 frequently if they are not listed in the consensus, or if the
8109 version of their descriptor listed in the consensus is too
8110 old. This fix should prevent situations where a server declines
8111 to re-publish itself because it has done so too recently, even
8112 though the authorities decided not to list its recent-enough
8113 descriptor. Fix for bug 3327.
8116 - Relays now include a reason for regenerating their descriptors
8117 in an HTTP header when uploading to the authorities. This will
8118 make it easier to debug descriptor-upload issues in the future.
8119 - When starting as root and then changing our UID via the User
8120 control option, and we have a ControlSocket configured, make sure
8121 that the ControlSocket is owned by the same account that Tor will
8122 run under. Implements ticket 3421; fix by Jérémy Bobbio.
8125 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
8126 utility function used in the control-port code). This shouldn't
8127 ever happen unless Tor is completely out of memory, but if it did
8128 happen and Tor somehow recovered from it, Tor could have sent a log
8129 message to a control port in the middle of a reply to a controller
8130 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
8131 - Make 'FetchUselessDescriptors' cause all descriptor types and
8132 all consensus types (including microdescriptors) to get fetched.
8133 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
8136 - Make a new "entry connection" struct as an internal subtype of "edge
8137 connection", to simplify the code and make exit connections smaller.
8140 Changes in version 0.2.2.33 - 2011-09-13
8141 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
8142 TLS handshake that makes relays and bridges that run this new version
8143 reachable from Iran again.
8146 - Avoid an assertion failure when reloading a configuration with
8147 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8148 3923; bugfix on 0.2.2.25-alpha.
8150 o Minor features (security):
8151 - Check for replays of the public-key encrypted portion of an
8152 INTRODUCE1 cell, in addition to the current check for replays of
8153 the g^x value. This prevents a possible class of active attacks
8154 by an attacker who controls both an introduction point and a
8155 rendezvous point, and who uses the malleability of AES-CTR to
8156 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8157 that these attacks are infeasible (requiring the attacker to send
8158 on the order of zettabytes of altered cells in a short interval),
8159 but we'd rather block them off in case there are any classes of
8160 this attack that we missed. Reported by Willem Pinckaers.
8163 - Adjust the expiration time on our SSL session certificates to
8164 better match SSL certs seen in the wild. Resolves ticket 4014.
8165 - Change the default required uptime for a relay to be accepted as
8166 a HSDir (hidden service directory) from 24 hours to 25 hours.
8167 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8168 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8169 authorities to abstain from voting on assignment of the HSDir
8170 consensus flag. Related to bug 2649.
8171 - Update to the September 6 2011 Maxmind GeoLite Country database.
8173 o Minor bugfixes (documentation and log messages):
8174 - Correct the man page to explain that HashedControlPassword and
8175 CookieAuthentication can both be set, in which case either method
8176 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8177 when we decided to allow these config options to both be set. Issue
8179 - Demote the 'replay detected' log message emitted when a hidden
8180 service receives the same Diffie-Hellman public key in two different
8181 INTRODUCE2 cells to info level. A normal Tor client can cause that
8182 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8183 fixes part of bug 2442.
8184 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8185 level. There is nothing that a hidden service's operator can do
8186 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8188 - Clarify a log message specifying the characters permitted in
8189 HiddenServiceAuthorizeClient client names. Previously, the log
8190 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8191 given the impression that every ASCII character between "+" and "_"
8192 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8195 - Provide a substitute implementation of lround() for MSVC, which
8196 apparently lacks it. Patch from Gisle Vanem.
8197 - Clean up some code issues that prevented Tor from building on older
8198 BSDs. Fixes bug 3894; reported by "grarpamp".
8199 - Search for a platform-specific version of "ar" when cross-compiling.
8200 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8203 Changes in version 0.2.3.3-alpha - 2011-09-01
8204 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
8205 security, and provides client-side support for the microdescriptor
8206 and optimistic data features introduced earlier in the 0.2.3.x
8207 series. It also includes numerous critical bugfixes in the (optional)
8208 bufferevent-based networking backend.
8210 o Major features (stream isolation):
8211 - You can now configure Tor so that streams from different
8212 applications are isolated on different circuits, to prevent an
8213 attacker who sees your streams as they leave an exit node from
8214 linking your sessions to one another. To do this, choose some way
8215 to distinguish the applications: have them connect to different
8216 SocksPorts, or have one of them use SOCKS4 while the other uses
8217 SOCKS5, or have them pass different authentication strings to the
8218 SOCKS proxy. Then, use the new SocksPort syntax to configure the
8219 degree of isolation you need. This implements Proposal 171.
8220 - There's a new syntax for specifying multiple client ports (such as
8221 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
8222 multiple *Port entries with full addr:port syntax on each.
8223 The old *ListenAddress format is still supported, but you can't
8224 mix it with the new *Port syntax.
8226 o Major features (other):
8227 - Enable microdescriptor fetching by default for clients. This allows
8228 clients to download a much smaller amount of directory information.
8229 To disable it (and go back to the old-style consensus and
8230 descriptors), set "UseMicrodescriptors 0" in your torrc file.
8231 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
8232 "PortForwarding" config option), now supports Windows.
8233 - When using an exit relay running 0.2.3.x, clients can now
8234 "optimistically" send data before the exit relay reports that
8235 the stream has opened. This saves a round trip when starting
8236 connections where the client speaks first (such as web browsing).
8237 This behavior is controlled by a consensus parameter (currently
8238 disabled). To turn it on or off manually, use the "OptimisticData"
8239 torrc option. Implements proposal 181; code by Ian Goldberg.
8241 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
8242 - When using IOCP on Windows, we need to enable Libevent windows
8244 - The IOCP backend now works even when the user has not specified
8245 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
8246 Fixes part of bug 3752.
8247 - Correctly record the bytes we've read and written when using
8248 bufferevents, so that we can include them in our bandwidth history
8249 and advertised bandwidth. Fixes bug 3803.
8250 - Apply rate-limiting only at the bottom of a chain of filtering
8251 bufferevents. This prevents us from filling up internal read
8252 buffers and violating rate-limits when filtering bufferevents
8253 are enabled. Fixes part of bug 3804.
8254 - Add high-watermarks to the output buffers for filtered
8255 bufferevents. This prevents us from filling up internal write
8256 buffers and wasting CPU cycles when filtering bufferevents are
8257 enabled. Fixes part of bug 3804.
8258 - Correctly notice when data has been written from a bufferevent
8259 without flushing it completely. Fixes bug 3805.
8260 - Fix a bug where server-side tunneled bufferevent-based directory
8261 streams would get closed prematurely. Fixes bug 3814.
8262 - Fix a use-after-free error with per-connection rate-limiting
8263 buckets. Fixes bug 3888.
8265 o Major bugfixes (also part of 0.2.2.31-rc):
8266 - If we're configured to write our ControlPorts to disk, only write
8267 them after switching UID and creating the data directory. This way,
8268 we don't fail when starting up with a nonexistent DataDirectory
8269 and a ControlPortWriteToFile setting based on that directory. Fixes
8270 bug 3747; bugfix on Tor 0.2.2.26-beta.
8273 - Added a new CONF_CHANGED event so that controllers can be notified
8274 of any configuration changes made by other controllers, or by the
8275 user. Implements ticket 1692.
8276 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
8277 leak when using bufferevents, and lets Libevent worry about how to
8278 best copy data out of a buffer.
8279 - Replace files in stats/ rather than appending to them. Now that we
8280 include statistics in extra-info descriptors, it makes no sense to
8281 keep old statistics forever. Implements ticket 2930.
8283 o Minor features (build compatibility):
8284 - Limited, experimental support for building with nmake and MSVC.
8285 - Provide a substitute implementation of lround() for MSVC, which
8286 apparently lacks it. Patch from Gisle Vanem.
8288 o Minor features (also part of 0.2.2.31-rc):
8289 - Update to the August 2 2011 Maxmind GeoLite Country database.
8291 o Minor bugfixes (on 0.2.3.x-alpha):
8292 - Fix a spurious warning when parsing SOCKS requests with
8293 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
8294 - Get rid of a harmless warning that could happen on relays running
8295 with bufferevents. The warning was caused by someone doing an http
8296 request to a relay's orport. Also don't warn for a few related
8297 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
8299 o Minor bugfixes (on 2.2.x and earlier):
8300 - Correct the man page to explain that HashedControlPassword and
8301 CookieAuthentication can both be set, in which case either method
8302 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8303 when we decided to allow these config options to both be set. Issue
8305 - The "--quiet" and "--hush" options now apply not only to Tor's
8306 behavior before logs are configured, but also to Tor's behavior in
8307 the absense of configured logs. Fixes bug 3550; bugfix on
8310 o Minor bugfixes (also part of 0.2.2.31-rc):
8311 - Write several files in text mode, on OSes that distinguish text
8312 mode from binary mode (namely, Windows). These files are:
8313 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8314 that collect those statistics; 'client_keys' and 'hostname' for
8315 hidden services that use authentication; and (in the tor-gencert
8316 utility) newly generated identity and signing keys. Previously,
8317 we wouldn't specify text mode or binary mode, leading to an
8318 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8319 the DirRecordUsageByCountry option which would have triggered
8320 the assertion failure was added), although this assertion failure
8321 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8322 - Selectively disable deprecation warnings on OS X because Lion
8323 started deprecating the shipped copy of openssl. Fixes bug 3643.
8324 - Remove an extra pair of quotation marks around the error
8325 message in control-port STATUS_GENERAL BUG events. Bugfix on
8326 0.1.2.6-alpha; fixes bug 3732.
8327 - When unable to format an address as a string, report its value
8328 as "???" rather than reusing the last formatted address. Bugfix
8331 o Code simplifications and refactoring:
8332 - Rewrite the listener-selection logic so that parsing which ports
8333 we want to listen on is now separate from binding to the ports
8337 - Building Tor with bufferevent support now requires Libevent
8338 2.0.13-stable or later. Previous versions of Libevent had bugs in
8339 SSL-related bufferevents and related issues that would make Tor
8340 work badly with bufferevents. Requiring 2.0.13-stable also allows
8341 Tor with bufferevents to take advantage of Libevent APIs
8342 introduced after 2.0.8-rc.
8345 Changes in version 0.2.2.32 - 2011-08-27
8346 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8347 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8348 a founder of the PETS community, a leader in our field, a mentor,
8349 and a friend. He left us with these words: "I had the possibility
8350 to contribute to this world that is not as it should be. I hope I
8351 could help in some areas to make the world a better place, and that
8352 I could also encourage other people to be engaged in improving the
8353 world. Please, stay engaged. This world needs you, your love, your
8354 initiative -- now I cannot be part of that anymore."
8356 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8357 ready. More than two years in the making, this release features improved
8358 client performance and hidden service reliability, better compatibility
8359 for Android, correct behavior for bridges that listen on more than
8360 one address, more extensible and flexible directory object handling,
8361 better reporting of network statistics, improved code security, and
8362 many many other features and bugfixes.
8365 Changes in version 0.2.2.31-rc - 2011-08-17
8366 Tor 0.2.2.31-rc is the second and hopefully final release candidate
8367 for the Tor 0.2.2.x series.
8370 - Remove an extra pair of quotation marks around the error
8371 message in control-port STATUS_GENERAL BUG events. Bugfix on
8372 0.1.2.6-alpha; fixes bug 3732.
8373 - If we're configured to write our ControlPorts to disk, only write
8374 them after switching UID and creating the data directory. This way,
8375 we don't fail when starting up with a nonexistent DataDirectory
8376 and a ControlPortWriteToFile setting based on that directory. Fixes
8377 bug 3747; bugfix on Tor 0.2.2.26-beta.
8380 - Update to the August 2 2011 Maxmind GeoLite Country database.
8383 - Allow GETINFO fingerprint to return a fingerprint even when
8384 we have not yet built a router descriptor. Fixes bug 3577;
8385 bugfix on 0.2.0.1-alpha.
8386 - Write several files in text mode, on OSes that distinguish text
8387 mode from binary mode (namely, Windows). These files are:
8388 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8389 that collect those statistics; 'client_keys' and 'hostname' for
8390 hidden services that use authentication; and (in the tor-gencert
8391 utility) newly generated identity and signing keys. Previously,
8392 we wouldn't specify text mode or binary mode, leading to an
8393 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8394 the DirRecordUsageByCountry option which would have triggered
8395 the assertion failure was added), although this assertion failure
8396 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8397 - Selectively disable deprecation warnings on OS X because Lion
8398 started deprecating the shipped copy of openssl. Fixes bug 3643.
8399 - When unable to format an address as a string, report its value
8400 as "???" rather than reusing the last formatted address. Bugfix
8404 Changes in version 0.2.3.2-alpha - 2011-07-18
8405 Tor 0.2.3.2-alpha introduces two new experimental features:
8406 microdescriptors and pluggable transports. It also continues cleaning
8407 up a variety of recently introduced features.
8410 - Clients can now use microdescriptors instead of regular descriptors
8411 to build circuits. Microdescriptors are authority-generated
8412 summaries of regular descriptors' contents, designed to change
8413 very rarely (see proposal 158 for details). This feature is
8414 designed to save bandwidth, especially for clients on slow internet
8415 connections. It's off by default for now, since nearly no caches
8416 support it, but it will be on-by-default for clients in a future
8417 version. You can use the UseMicrodescriptors option to turn it on.
8418 - Tor clients using bridges can now be configured to use a separate
8419 'transport' proxy for each bridge. This approach helps to resist
8420 censorship by allowing bridges to use protocol obfuscation
8421 plugins. It implements part of proposal 180. Implements ticket 2841.
8422 - While we're trying to bootstrap, record how many TLS connections
8423 fail in each state, and report which states saw the most failures
8424 in response to any bootstrap failures. This feature may speed up
8425 diagnosis of censorship events. Implements ticket 3116.
8427 o Major bugfixes (on 0.2.3.1-alpha):
8428 - When configuring a large set of nodes in EntryNodes (as with
8429 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
8430 random subset to be guards, and choose them in random
8431 order. Fixes bug 2798.
8432 - Tor could crash when remembering a consensus in a non-used consensus
8433 flavor without having a current consensus set. Fixes bug 3361.
8434 - Comparing an unknown address to a microdescriptor's shortened exit
8435 policy would always give a "rejected" result. Fixes bug 3599.
8436 - Using microdescriptors as a client no longer prevents Tor from
8437 uploading and downloading hidden service descriptors. Fixes
8441 - Allow nameservers with IPv6 address. Resolves bug 2574.
8442 - Accept attempts to include a password authenticator in the
8443 handshake, as supported by SOCKS5. This handles SOCKS clients that
8444 don't know how to omit a password when authenticating. Resolves
8446 - When configuring a large set of nodes in EntryNodes, and there are
8447 enough of them listed as Guard so that we don't need to consider
8448 the non-guard entries, prefer the ones listed with the Guard flag.
8449 - Check for and recover from inconsistency in the microdescriptor
8450 cache. This will make it harder for us to accidentally free a
8451 microdescriptor without removing it from the appropriate data
8452 structures. Fixes issue 3135; issue noted by "wanoskarnet".
8453 - Log SSL state transitions at log level DEBUG, log domain
8454 HANDSHAKE. This can be useful for debugging censorship events.
8455 Implements ticket 3264.
8456 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
8457 implements ticket 3439.
8459 o Minor bugfixes (on 0.2.3.1-alpha):
8460 - Do not free all general-purpose regular descriptors just
8461 because microdescriptor use is enabled. Fixes bug 3113.
8462 - Correctly link libevent_openssl when --enable-static-libevent
8463 is passed to configure. Fixes bug 3118.
8464 - Bridges should not complain during their heartbeat log messages that
8465 they are unlisted in the consensus: that's more or less the point
8466 of being a bridge. Fixes bug 3183.
8467 - Report a SIGNAL event to controllers when acting on a delayed
8468 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
8469 event to the controller if we acted on a SIGNAL NEWNYM command
8470 immediately, and otherwise not report a SIGNAL event for the
8471 command at all. Fixes bug 3349.
8472 - Fix a crash when handling the SIGNAL controller command or
8473 reporting ERR-level status events with bufferevents enabled. Found
8474 by Robert Ransom. Fixes bug 3367.
8475 - Always ship the tor-fw-helper manpage in our release tarballs.
8476 Fixes bug 3389. Reported by Stephen Walker.
8477 - Fix a class of double-mark-for-close bugs when bufferevents
8478 are enabled. Fixes bug 3403.
8479 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
8480 - Add SIGNAL to the list returned by the 'GETINFO events/names'
8481 control-port command. Fixes part of bug 3465.
8482 - Prevent using negative indices during unit test runs when read_all()
8483 fails. Spotted by coverity.
8484 - Fix a rare memory leak when checking the nodelist without it being
8485 present. Found by coverity.
8486 - Only try to download a microdescriptor-flavored consensus from
8487 a directory cache that provides them.
8489 o Minor bugfixes (on 0.2.2.x and earlier):
8490 - Assert that hidden-service-related operations are not performed
8491 using single-hop circuits. Previously, Tor would assert that
8492 client-side streams are not attached to single-hop circuits,
8493 but not that other sensitive operations on the client and service
8494 side are not performed using single-hop circuits. Fixes bug 3332;
8496 - Don't publish a new relay descriptor when we reload our onion key,
8497 unless the onion key has actually changed. Fixes bug 3263 and
8498 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
8499 - Allow GETINFO fingerprint to return a fingerprint even when
8500 we have not yet built a router descriptor. Fixes bug 3577;
8501 bugfix on 0.2.0.1-alpha.
8502 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
8503 on 0.2.2.4-alpha; fixes bug 3427.
8505 o Code simplification and refactoring:
8506 - Use tor_sscanf() in place of scanf() in more places through the
8507 code. This makes us a little more locale-independent, and
8508 should help shut up code-analysis tools that can't tell
8509 a safe sscanf string from a dangerous one.
8510 - Use tt_assert(), not tor_assert(), for checking for test failures.
8511 This makes the unit tests more able to go on in the event that
8513 - Split connection_about_to_close() into separate functions for each
8517 - On Windows, we now define the _WIN32_WINNT macros only if they
8518 are not already defined. This lets the person building Tor decide,
8519 if they want, to require a later version of Windows.
8522 Changes in version 0.2.2.30-rc - 2011-07-07
8523 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
8524 series. It fixes a few smaller bugs, but generally appears stable.
8525 Please test it and let us know whether it is!
8528 - Send a SUCCEEDED stream event to the controller when a reverse
8529 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
8530 discovered by katmagic.
8531 - Always NUL-terminate the sun_path field of a sockaddr_un before
8532 passing it to the kernel. (Not a security issue: kernels are
8533 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8534 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8535 - Don't stack-allocate the list of supplementary GIDs when we're
8536 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8537 could take up to 256K, which is way too much stack. Found by
8538 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8539 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
8540 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
8541 fixes part of bug 3465.
8542 - Fix a memory leak when receiving a descriptor for a hidden
8543 service we didn't ask for. Found by Coverity; CID #30. Bugfix
8547 - Update to the July 1 2011 Maxmind GeoLite Country database.
8550 Changes in version 0.2.2.29-beta - 2011-06-20
8551 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
8552 have bridge lines in their torrc but don't want to use them; gets
8553 us closer to having the control socket feature working on Debian;
8554 and fixes a variety of smaller bugs.
8557 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
8558 When we changed the default behavior to "use bridges if any
8559 are listed in the torrc", we surprised users who had bridges
8560 in their torrc files but who didn't actually want to use them.
8561 Partial resolution for bug 3354.
8564 - Don't attach new streams to old rendezvous circuits after SIGNAL
8565 NEWNYM. Previously, we would keep using an existing rendezvous
8566 circuit if it remained open (i.e. if it were kept open by a
8567 long-lived stream, or if a new stream were attached to it before
8568 Tor could notice that it was old and no longer in use). Bugfix on
8569 0.1.1.15-rc; fixes bug 3375.
8572 - Fix a bug when using ControlSocketsGroupWritable with User. The
8573 directory's group would be checked against the current group, not
8574 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
8575 bugfix on 0.2.2.26-beta.
8576 - Make connection_printf_to_buf()'s behavior sane. Its callers
8577 expect it to emit a CRLF iff the format string ends with CRLF;
8578 it actually emitted a CRLF iff (a) the format string ended with
8579 CRLF or (b) the resulting string was over 1023 characters long or
8580 (c) the format string did not end with CRLF *and* the resulting
8581 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
8582 fixes part of bug 3407.
8583 - Make send_control_event_impl()'s behavior sane. Its callers
8584 expect it to always emit a CRLF at the end of the string; it
8585 might have emitted extra control characters as well. Bugfix on
8586 0.1.1.9-alpha; fixes another part of bug 3407.
8587 - Make crypto_rand_int() check the value of its input correctly.
8588 Previously, it accepted values up to UINT_MAX, but could return a
8589 negative number if given a value above INT_MAX+1. Found by George
8590 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
8591 - Avoid a segfault when reading a malformed circuit build state
8592 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
8594 - When asked about a DNS record type we don't support via a
8595 client DNSPort, reply with NOTIMPL rather than an empty
8596 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8597 - Fix a rare memory leak during stats writing. Found by coverity.
8600 - Update to the June 1 2011 Maxmind GeoLite Country database.
8602 o Code simplifications and refactoring:
8603 - Remove some dead code as indicated by coverity.
8604 - Remove a few dead assignments during router parsing. Found by
8606 - Add some forgotten return value checks during unit tests. Found
8608 - Don't use 1-bit wide signed bit fields. Found by coverity.
8611 Changes in version 0.2.2.28-beta - 2011-06-04
8612 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
8613 fixed a big bug in whether relays stay in the consensus consistently,
8614 we moved closer to handling bridges and hidden services correctly,
8615 and we started the process of better handling the dreaded "my Vidalia
8616 died, and now my Tor demands a password when I try to reconnect to it"
8620 - Don't decide to make a new descriptor when receiving a HUP signal.
8621 This bug has caused a lot of 0.2.2.x relays to disappear from the
8622 consensus periodically. Fixes the most common case of triggering
8623 bug 1810; bugfix on 0.2.2.7-alpha.
8624 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
8625 - Don't try to build descriptors if "ORPort auto" is set and we
8626 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
8628 - Resolve a crash that occurred when setting BridgeRelay to 1 with
8629 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
8630 - Apply circuit timeouts to opened hidden-service-related circuits
8631 based on the correct start time. Previously, we would apply the
8632 circuit build timeout based on time since the circuit's creation;
8633 it was supposed to be applied based on time since the circuit
8634 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8635 - Use the same circuit timeout for client-side introduction
8636 circuits as for other four-hop circuits, rather than the timeout
8637 for single-hop directory-fetch circuits; the shorter timeout may
8638 have been appropriate with the static circuit build timeout in
8639 0.2.1.x and earlier, but caused many hidden service access attempts
8640 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
8641 on 0.2.2.2-alpha; fixes another part of bug 1297.
8642 - In ticket 2511 we fixed a case where you could use an unconfigured
8643 bridge if you had configured it as a bridge the last time you ran
8644 Tor. Now fix another edge case: if you had configured it as a bridge
8645 but then switched to a different bridge via the controller, you
8646 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
8650 - Add an __OwningControllerProcess configuration option and a
8651 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8652 that when it exits, Tor will shut down. Implements feature 3049.
8653 - If "UseBridges 1" is set and no bridges are configured, Tor will
8654 now refuse to build any circuits until some bridges are set.
8655 If "UseBridges auto" is set, Tor will use bridges if they are
8656 configured and we are not running as a server, but otherwise will
8657 make circuits as usual. The new default is "auto". Patch by anonym,
8658 so the Tails LiveCD can stop automatically revealing you as a Tor
8662 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8663 - Remove a trailing asterisk from "exit-policy/default" in the
8664 output of the control port command "GETINFO info/names". Bugfix
8666 - Use a wide type to hold sockets when built for 64-bit Windows builds.
8668 - Warn when the user configures two HiddenServiceDir lines that point
8669 to the same directory. Bugfix on 0.0.6 (the version introducing
8670 HiddenServiceDir); fixes bug 3289.
8671 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
8672 part of bug 2748; bugfix on 0.2.0.10-alpha.
8673 - Log malformed requests for rendezvous descriptors as protocol
8674 warnings, not warnings. Also, use a more informative log message
8675 in case someone sees it at log level warning without prior
8676 info-level messages. Fixes the other part of bug 2748; bugfix
8678 - Clear the table recording the time of the last request for each
8679 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
8680 Previously, we would clear our HS descriptor cache on SIGNAL
8681 NEWNYM, but if we had previously retrieved a descriptor (or tried
8682 to) from every directory responsible for it, we would refuse to
8683 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
8685 - Fix a log message that said "bits" while displaying a value in
8686 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8688 - When checking for 1024-bit keys, check for 1024 bits, not 128
8689 bytes. This allows Tor to correctly discard keys of length 1017
8690 through 1023. Bugfix on 0.0.9pre5.
8693 - Relays now log the reason for publishing a new relay descriptor,
8694 so we have a better chance of hunting down instances of bug 1810.
8695 Resolves ticket 3252.
8696 - Revise most log messages that refer to nodes by nickname to
8697 instead use the "$key=nickname at address" format. This should be
8698 more useful, especially since nicknames are less and less likely
8699 to be unique. Resolves ticket 3045.
8700 - Log (at info level) when purging pieces of hidden-service-client
8701 state because of SIGNAL NEWNYM.
8704 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8705 anything since 0.2.1.16-rc.
8708 Changes in version 0.2.2.27-beta - 2011-05-18
8709 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
8710 release, and also adds a few more general bugfixes.
8713 - Fix a crash bug when changing bridges in a running Tor process.
8714 Fixes bug 3213; bugfix on 0.2.2.26-beta.
8715 - When the controller configures a new bridge, don't wait 10 to 60
8716 seconds before trying to fetch its descriptor. Bugfix on
8717 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8720 - Require that onion keys have exponent 65537 in microdescriptors too.
8721 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
8722 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8723 Changed the limit to 512 characters by removing base64 newlines.
8724 Fixes bug 2752. Fix by Michael Yakubovich.
8725 - When a client starts or stops using bridges, never use a circuit
8726 that was built before the configuration change. This behavior could
8727 put at risk a user who uses bridges to ensure that her traffic
8728 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8732 Changes in version 0.2.2.26-beta - 2011-05-17
8733 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
8734 also introduces a new "socksport auto" approach that should make it
8735 easier to run multiple Tors on the same system, and does a lot of
8736 cleanup to get us closer to a release candidate.
8738 o Security/privacy fixes:
8739 - Replace all potentially sensitive memory comparison operations
8740 with versions whose runtime does not depend on the data being
8741 compared. This will help resist a class of attacks where an
8742 adversary can use variations in timing information to learn
8743 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8744 implementation by Robert Ransom based partially on code by DJB.)
8745 - When receiving a hidden service descriptor, check that it is for
8746 the hidden service we wanted. Previously, Tor would store any
8747 hidden service descriptors that a directory gave it, whether it
8748 wanted them or not. This wouldn't have let an attacker impersonate
8749 a hidden service, but it did let directories pre-seed a client
8750 with descriptors that it didn't want. Bugfix on 0.0.6.
8751 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8752 DNS cache entries, and virtual address mappings: that's what
8753 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8756 - The options SocksPort, ControlPort, and so on now all accept a
8757 value "auto" that opens a socket on an OS-selected port. A
8758 new ControlPortWriteToFile option tells Tor to write its
8759 actual control port or ports to a chosen file. If the option
8760 ControlPortFileGroupReadable is set, the file is created as
8761 group-readable. Now users can run two Tor clients on the same
8762 system without needing to manually mess with parameters. Resolves
8763 part of ticket 3076.
8764 - Set SO_REUSEADDR on all sockets, not just listeners. This should
8765 help busy exit nodes avoid running out of useable ports just
8766 because all the ports have been used in the near past. Resolves
8770 - New "GETINFO net/listeners/(type)" controller command to return
8771 a list of addresses and ports that are bound for listeners for a
8772 given connection type. This is useful when the user has configured
8773 "SocksPort auto" and the controller needs to know which port got
8774 chosen. Resolves another part of ticket 3076.
8775 - Add a new ControlSocketsGroupWritable configuration option: when
8776 it is turned on, ControlSockets are group-writeable by the default
8777 group of the current user. Patch by Jérémy Bobbio; implements
8779 - Tor now refuses to create a ControlSocket in a directory that is
8780 world-readable (or group-readable if ControlSocketsGroupWritable
8781 is 0). This is necessary because some operating systems do not
8782 enforce permissions on an AF_UNIX sockets. Permissions on the
8783 directory holding the socket, however, seems to work everywhere.
8784 - Rate-limit a warning about failures to download v2 networkstatus
8785 documents. Resolves part of bug 1352.
8786 - Backport code from 0.2.3.x that allows directory authorities to
8787 clean their microdescriptor caches. Needed to resolve bug 2230.
8788 - When an HTTPS proxy reports "403 Forbidden", we now explain
8789 what it means rather than calling it an unexpected status code.
8790 Closes bug 2503. Patch from Michael Yakubovich.
8791 - Update to the May 1 2011 Maxmind GeoLite Country database.
8794 - Authorities now clean their microdesc cache periodically and when
8795 reading from disk initially, not only when adding new descriptors.
8796 This prevents a bug where we could lose microdescriptors. Bugfix
8797 on 0.2.2.6-alpha. Fixes bug 2230.
8798 - Do not crash when our configuration file becomes unreadable, for
8799 example due to a permissions change, between when we start up
8800 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8802 - Avoid a bug that would keep us from replacing a microdescriptor
8803 cache on Windows. (We would try to replace the file while still
8804 holding it open. That's fine on Unix, but Windows doesn't let us
8805 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
8806 - Add missing explanations for the authority-related torrc options
8807 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
8808 man page. Resolves issue 2379.
8809 - As an authority, do not upload our own vote or signature set to
8810 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
8811 it would get flagged as a duplicate. Resolves bug 3026.
8812 - Accept hidden service descriptors if we think we might be a hidden
8813 service directory, regardless of what our consensus says. This
8814 helps robustness, since clients and hidden services can sometimes
8815 have a more up-to-date view of the network consensus than we do,
8816 and if they think that the directory authorities list us a HSDir,
8817 we might actually be one. Related to bug 2732; bugfix on
8819 - When a controller changes TrackHostExits, remove mappings for
8820 hosts that should no longer have their exits tracked. Bugfix on
8822 - When a controller changes VirtualAddrNetwork, remove any mappings
8823 for hosts that were automapped to the old network. Bugfix on
8825 - When a controller changes one of the AutomapHosts* options, remove
8826 any mappings for hosts that should no longer be automapped. Bugfix
8828 - Do not reset the bridge descriptor download status every time we
8829 re-parse our configuration or get a configuration change. Fixes
8830 bug 3019; bugfix on 0.2.0.3-alpha.
8832 o Minor bugfixes (code cleanup):
8833 - When loading the microdesc journal, remember its current size.
8834 In 0.2.2, this helps prevent the microdesc journal from growing
8835 without limit on authorities (who are the only ones to use it in
8836 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8837 Fix posted by "cypherpunks."
8838 - The microdesc journal is supposed to get rebuilt only if it is
8839 at least _half_ the length of the store, not _twice_ the length
8840 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8841 - Fix a potential null-pointer dereference while computing a
8842 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
8844 - Avoid a possible null-pointer dereference when rebuilding the mdesc
8845 cache without actually having any descriptors to cache. Bugfix on
8846 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
8847 - If we fail to compute the identity digest of a v3 legacy keypair,
8848 warn, and don't use a buffer-full of junk instead. Bugfix on
8849 0.2.1.1-alpha; fixes bug 3106.
8850 - Resolve an untriggerable issue in smartlist_string_num_isin(),
8851 where if the function had ever in the future been used to check
8852 for the presence of a too-large number, it would have given an
8853 incorrect result. (Fortunately, we only used it for 16-bit
8854 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
8855 - Require that introduction point keys and onion handshake keys
8856 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8860 - Caches no longer download and serve v2 networkstatus documents
8861 unless FetchV2Networkstatus flag is set: these documents haven't
8862 haven't been used by clients or relays since 0.2.0.x. Resolves
8866 Changes in version 0.2.3.1-alpha - 2011-05-05
8867 Tor 0.2.3.1-alpha adds some new experimental features, including support
8868 for an improved network IO backend, IOCP networking on Windows,
8869 microdescriptor caching, "fast-start" support for streams, and automatic
8870 home router configuration. There are also numerous internal improvements
8871 to try to make the code easier for developers to work with.
8873 This is the first alpha release in a new series, so expect there to be
8874 bugs. Users who would rather test out a more stable branch should
8875 stay with 0.2.2.x for now.
8878 - Tor can now optionally build with the "bufferevents" buffered IO
8879 backend provided by Libevent 2. To use this feature, make sure you
8880 have the latest possible version of Libevent, and pass the
8881 --enable-bufferevents flag to configure when building Tor from
8882 source. This feature will make our networking code more flexible,
8883 let us stack layers on each other, and let us use more efficient
8884 zero-copy transports where available.
8885 - As an experimental feature, Tor can use IOCP for networking on Windows.
8886 Once this code is tuned and optimized, it promises much better
8887 performance than the select-based backend we've used in the past. To
8888 try this feature, you must build Tor with Libevent 2, configure Tor
8889 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
8890 your torrc. There are known bugs here: only try this if you can help
8891 debug it as it breaks.
8892 - The EntryNodes option can now include country codes like {de} or IP
8893 addresses or network masks. Previously we had disallowed these options
8894 because we didn't have an efficient way to keep the list up to
8895 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
8896 - Exit nodes now accept and queue data on not-yet-connected streams.
8897 Previously, the client wasn't allowed to send data until the stream was
8898 connected, which slowed down all connections. This change will enable
8899 clients to perform a "fast-start" on streams and send data without
8900 having to wait for a confirmation that the stream has opened. (Patch
8901 from Ian Goldberg; implements the server side of Proposal 174.)
8902 - Tor now has initial support for automatic port mapping on the many
8903 home routers that support NAT-PMP or UPnP. (Not yet supported on
8904 Windows). To build the support code, you'll need to have libnatpnp
8905 library and/or the libminiupnpc library, and you'll need to enable the
8906 feature specifically by passing "--enable-upnp" and/or
8907 "--enable-natpnp" to configure. To turn it on, use the new
8908 PortForwarding option.
8909 - Caches now download, cache, and serve multiple "flavors" of the
8910 consensus, including a flavor that describes microdescriptors.
8911 - Caches now download, cache, and serve microdescriptors -- small
8912 summaries of router descriptors that are authenticated by all of the
8913 directory authorities. Once enough caches are running this code,
8914 clients will be able to save significant amounts of directory bandwidth
8915 by downloading microdescriptors instead of router descriptors.
8918 - Make logging resolution configurable with a new LogTimeGranularity
8919 option, and change the default from 1 millisecond to 1 second.
8920 Implements enhancement 1668.
8921 - We log which torrc file we're using on startup. Implements ticket
8923 - Ordinarily, Tor does not count traffic from private addresses (like
8924 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
8925 There is now a new option, CountPrivateBandwidth, to disable this
8926 behavior. Patch from Daniel Cagara.
8927 - New --enable-static-tor configure option for building Tor as
8928 statically as possible. Idea, general hackery and thoughts from
8929 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
8931 - If you set the NumCPUs option to 0, Tor will now try to detect how
8932 many CPUs you have. This is the new default behavior.
8933 - Turn on directory request statistics by default and include them in
8934 extra-info descriptors. Don't break if we have no GeoIP database.
8935 - Relays that set "ConnDirectionStatistics 1" write statistics on the
8936 bidirectional use of connections to disk every 24 hours.
8937 - Add a GeoIP file digest to the extra-info descriptor. Implements
8939 - The NodeFamily option -- which let you declare that you want to
8940 consider nodes to be part of a family whether they list themselves
8941 that way or not -- now allows IP address ranges and country codes.
8942 - Add a new 'Heartbeat' log message type to periodically log a message
8943 describing Tor's status at level Notice. This feature is meant for
8944 operators who log at notice, and want to make sure that their Tor
8945 server is still working. Implementation by George Kadianakis.
8947 o Minor bugfixes (on 0.2.2.25-alpha):
8948 - When loading the microdesc journal, remember its current size.
8949 In 0.2.2, this helps prevent the microdesc journal from growing
8950 without limit on authorities (who are the only ones to use it in
8951 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8952 Fix posted by "cypherpunks."
8953 - The microdesc journal is supposed to get rebuilt only if it is
8954 at least _half_ the length of the store, not _twice_ the length
8955 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8956 - If as an authority we fail to compute the identity digest of a v3
8957 legacy keypair, warn, and don't use a buffer-full of junk instead.
8958 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
8959 - Authorities now clean their microdesc cache periodically and when
8960 reading from disk initially, not only when adding new descriptors.
8961 This prevents a bug where we could lose microdescriptors. Bugfix
8964 o Minor features (controller):
8965 - Add a new SIGNAL event to the controller interface so that
8966 controllers can be notified when Tor handles a signal. Resolves
8967 issue 1955. Patch by John Brooks.
8968 - Add a new GETINFO option to get total bytes read and written. Patch
8969 from pipe, revised by atagar. Resolves ticket 2345.
8970 - Implement some GETINFO controller fields to provide information about
8971 the Tor process's pid, euid, username, and resource limits.
8974 - Our build system requires automake 1.6 or later to create the
8975 Makefile.in files. Previously, you could have used 1.4.
8976 This only affects developers and people building Tor from git;
8977 people who build Tor from the source distribution without changing
8978 the Makefile.am files should be fine.
8979 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
8980 so on. This is more robust against some of the failure modes
8981 associated with running the autotools pieces on their own.
8983 o Minor packaging issues:
8984 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
8985 already created. Patch from Andreas Stieger. Fixes bug 2573.
8987 o Code simplifications and refactoring:
8988 - A major revision to our internal node-selecting and listing logic.
8989 Tor already had at least two major ways to look at the question of
8990 "which Tor servers do we know about": a list of router descriptors,
8991 and a list of entries in the current consensus. With
8992 microdescriptors, we're adding a third. Having so many systems
8993 without an abstraction layer over them was hurting the codebase.
8994 Now, we have a new "node_t" abstraction that presents a consistent
8995 interface to a client's view of a Tor node, and holds (nearly) all
8996 of the mutable state formerly in routerinfo_t and routerstatus_t.
8997 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
8998 no longer link against Libevent: they never used it, but
8999 our library structure used to force them to link it.
9002 - Remove some old code to work around even older versions of Tor that
9003 used forked processes to handle DNS requests. Such versions of Tor
9004 are no longer in use as servers.
9006 o Documentation fixes:
9007 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
9008 - Add missing documentation for the authority-related torrc options
9009 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
9013 Changes in version 0.2.2.25-alpha - 2011-04-29
9014 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
9015 robust, routers no longer overreport their bandwidth, Win7 should crash
9016 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
9017 now prevents hidden service-related activity from being linkable. It
9018 provides more information to Vidalia so you can see if your bridge is
9019 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
9020 StrictNodes configuration options to make them more reliable, more
9021 understandable, and more regularly applied. If you use those options,
9022 please see the revised documentation for them in the manual page.
9025 - Relays were publishing grossly inflated bandwidth values because
9026 they were writing their state files wrong--now they write the
9027 correct value. Also, resume reading bandwidth history from the
9028 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
9029 - Improve hidden service robustness: When we find that we have
9030 extended a hidden service's introduction circuit to a relay not
9031 listed as an introduction point in the HS descriptor we currently
9032 have, retry with an introduction point from the current
9033 descriptor. Previously we would just give up. Fixes bugs 1024 and
9034 1930; bugfix on 0.2.0.10-alpha.
9035 - Clients now stop trying to use an exit node associated with a given
9036 destination by TrackHostExits if they fail to reach that exit node.
9037 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
9038 - Fix crash bug on platforms where gmtime and localtime can return
9039 NULL. Windows 7 users were running into this one. Fixes part of bug
9040 2077. Bugfix on all versions of Tor. Found by boboper.
9042 o Security and stability fixes:
9043 - Don't double-free a parsable, but invalid, microdescriptor, even if
9044 it is followed in the blob we're parsing by an unparsable
9045 microdescriptor. Fixes an issue reported in a comment on bug 2954.
9046 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
9047 - If the Nickname configuration option isn't given, Tor would pick a
9048 nickname based on the local hostname as the nickname for a relay.
9049 Because nicknames are not very important in today's Tor and the
9050 "Unnamed" nickname has been implemented, this is now problematic
9051 behavior: It leaks information about the hostname without being
9052 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
9053 introduced the Unnamed nickname. Reported by tagnaq.
9054 - Fix an uncommon assertion failure when running with DNSPort under
9055 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9056 - Avoid linkability based on cached hidden service descriptors: forget
9057 all hidden service descriptors cached as a client when processing a
9058 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9061 - Export GeoIP information on bridge usage to controllers even if we
9062 have not yet been running for 24 hours. Now Vidalia bridge operators
9063 can get more accurate and immediate feedback about their
9064 contributions to the network.
9066 o Major features and bugfixes (node selection):
9067 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
9068 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
9069 options. Previously, we had been ambiguous in describing what
9070 counted as an "exit" node, and what operations exactly "StrictNodes
9071 0" would permit. This created confusion when people saw nodes built
9072 through unexpected circuits, and made it hard to tell real bugs from
9073 surprises. Now the intended behavior is:
9074 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
9075 a node that delivers user traffic outside the Tor network.
9076 . "Entry", in the context of EntryNodes, means a node used as the
9077 first hop of a multihop circuit. It doesn't include direct
9078 connections to directory servers.
9079 . "ExcludeNodes" applies to all nodes.
9080 . "StrictNodes" changes the behavior of ExcludeNodes only. When
9081 StrictNodes is set, Tor should avoid all nodes listed in
9082 ExcludeNodes, even when it will make user requests fail. When
9083 StrictNodes is *not* set, then Tor should follow ExcludeNodes
9084 whenever it can, except when it must use an excluded node to
9085 perform self-tests, connect to a hidden service, provide a
9086 hidden service, fulfill a .exit request, upload directory
9087 information, or fetch directory information.
9088 Collectively, the changes to implement the behavior fix bug 1090.
9089 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
9090 a node is listed in both, it's treated as excluded.
9091 - ExcludeNodes now applies to directory nodes -- as a preference if
9092 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
9093 Don't exclude all the directory authorities and set StrictNodes to 1
9094 unless you really want your Tor to break.
9095 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
9096 - ExcludeExitNodes now overrides .exit requests.
9097 - We don't use bridges listed in ExcludeNodes.
9098 - When StrictNodes is 1:
9099 . We now apply ExcludeNodes to hidden service introduction points
9100 and to rendezvous points selected by hidden service users. This
9101 can make your hidden service less reliable: use it with caution!
9102 . If we have used ExcludeNodes on ourself, do not try relay
9103 reachability self-tests.
9104 . If we have excluded all the directory authorities, we will not
9105 even try to upload our descriptor if we're a relay.
9106 . Do not honor .exit requests to an excluded node.
9107 - Remove a misfeature that caused us to ignore the Fast/Stable flags
9108 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
9109 - When the set of permitted nodes changes, we now remove any mappings
9110 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
9112 - We never cannibalize a circuit that had excluded nodes on it, even
9113 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
9114 - Revert a change where we would be laxer about attaching streams to
9115 circuits than when building the circuits. This was meant to prevent
9116 a set of bugs where streams were never attachable, but our improved
9117 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
9118 - Keep track of how many times we launch a new circuit to handle a
9119 given stream. Too many launches could indicate an inconsistency
9120 between our "launch a circuit to handle this stream" logic and our
9121 "attach this stream to one of the available circuits" logic.
9122 - Improve log messages related to excluded nodes.
9125 - Fix a spurious warning when moving from a short month to a long
9126 month on relays with month-based BandwidthAccounting. Bugfix on
9127 0.2.2.17-alpha; fixes bug 3020.
9128 - When a client finds that an origin circuit has run out of 16-bit
9129 stream IDs, we now mark it as unusable for new streams. Previously,
9130 we would try to close the entire circuit. Bugfix on 0.0.6.
9131 - Add a forgotten cast that caused a compile warning on OS X 10.6.
9132 Bugfix on 0.2.2.24-alpha.
9133 - Be more careful about reporting the correct error from a failed
9134 connect() system call. Under some circumstances, it was possible to
9135 look at an incorrect value for errno when sending the end reason.
9136 Bugfix on 0.1.0.1-rc.
9137 - Correctly handle an "impossible" overflow cases in connection byte
9138 counting, where we write or read more than 4GB on an edge connection
9139 in a single second. Bugfix on 0.1.2.8-beta.
9140 - Correct the warning displayed when a rendezvous descriptor exceeds
9141 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9143 - Clients and hidden services now use HSDir-flagged relays for hidden
9144 service descriptor downloads and uploads even if the relays have no
9145 DirPort set and the client has disabled TunnelDirConns. This will
9146 eventually allow us to give the HSDir flag to relays with no
9147 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
9148 - Downgrade "no current certificates known for authority" message from
9149 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
9150 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
9151 2917. Bugfix on 0.1.1.1-alpha.
9152 - Only limit the lengths of single HS descriptors, even when multiple
9153 HS descriptors are published to an HSDir relay in a single POST
9154 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
9155 - Write the current time into the LastWritten line in our state file,
9156 rather than the time from the previous write attempt. Also, stop
9157 trying to use a time of -1 in our log statements. Fixes bug 3039;
9158 bugfix on 0.2.2.14-alpha.
9159 - Be more consistent in our treatment of file system paths. "~" should
9160 get expanded to the user's home directory in the Log config option.
9161 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
9162 feature for the -f and --DataDirectory options.
9165 - Make sure every relay writes a state file at least every 12 hours.
9166 Previously, a relay could go for weeks without writing its state
9167 file, and on a crash could lose its bandwidth history, capacity
9168 estimates, client country statistics, and so on. Addresses bug 3012.
9169 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
9170 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
9171 clients are already deprecated because of security bugs.
9172 - Don't allow v0 hidden service authorities to act as clients.
9173 Required by fix for bug 3000.
9174 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
9175 by fix for bug 3000.
9176 - Ensure that no empty [dirreq-](read|write)-history lines are added
9177 to an extrainfo document. Implements ticket 2497.
9179 o Code simplification and refactoring:
9180 - Remove workaround code to handle directory responses from servers
9181 that had bug 539 (they would send HTTP status 503 responses _and_
9182 send a body too). Since only server versions before
9183 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
9184 keep the workaround in place.
9185 - Remove the old 'fuzzy time' logic. It was supposed to be used for
9186 handling calculations where we have a known amount of clock skew and
9187 an allowed amount of unknown skew. But we only used it in three
9188 places, and we never adjusted the known/unknown skew values. This is
9189 still something we might want to do someday, but if we do, we'll
9190 want to do it differently.
9191 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9192 None of the cases where we did this before were wrong, but by making
9193 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9194 - Use GetTempDir to find the proper temporary directory location on
9195 Windows when generating temporary files for the unit tests. Patch by
9199 Changes in version 0.2.2.24-alpha - 2011-04-08
9200 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
9201 prevented Tor clients from effectively using "multihomed" bridges,
9202 that is, bridges that listen on multiple ports or IP addresses so users
9203 can continue to use some of their addresses even if others get blocked.
9206 - Fix a bug where bridge users who configure the non-canonical
9207 address of a bridge automatically switch to its canonical
9208 address. If a bridge listens at more than one address, it should be
9209 able to advertise those addresses independently and any non-blocked
9210 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
9212 - If you configured Tor to use bridge A, and then quit and
9213 configured Tor to use bridge B instead, it would happily continue
9214 to use bridge A if it's still reachable. While this behavior is
9215 a feature if your goal is connectivity, in some scenarios it's a
9216 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
9217 - Directory authorities now use data collected from their own
9218 uptime observations when choosing whether to assign the HSDir flag
9219 to relays, instead of trusting the uptime value the relay reports in
9220 its descriptor. This change helps prevent an attack where a small
9221 set of nodes with frequently-changing identity keys can blackhole
9222 a hidden service. (Only authorities need upgrade; others will be
9223 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
9226 - When we restart our relay, we might get a successful connection
9227 from the outside before we've started our reachability tests,
9228 triggering a warning: "ORPort found reachable, but I have no
9229 routerinfo yet. Failing to inform controller of success." This
9230 bug was harmless unless Tor is running under a controller
9231 like Vidalia, in which case the controller would never get a
9232 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9234 - Make directory authorities more accurate at recording when
9235 relays that have failed several reachability tests became
9236 unreachable, so we can provide more accuracy at assigning Stable,
9237 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
9238 - Fix an issue that prevented static linking of libevent on
9239 some platforms (notably Linux). Fixes bug 2698; bugfix on
9240 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
9241 the --with-static-libevent configure option).
9242 - We now ask the other side of a stream (the client or the exit)
9243 for more data on that stream when the amount of queued data on
9244 that stream dips low enough. Previously, we wouldn't ask the
9245 other side for more data until either it sent us more data (which
9246 it wasn't supposed to do if it had exhausted its window!) or we
9247 had completely flushed all our queued data. This flow control fix
9248 should improve throughput. Fixes bug 2756; bugfix on the earliest
9249 released versions of Tor (svn commit r152).
9250 - Avoid a double-mark-for-free warning when failing to attach a
9251 transparent proxy connection. (We thought we had fixed this in
9252 0.2.2.23-alpha, but it turns out our fix was checking the wrong
9253 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
9254 bug) and 0.2.2.23-alpha (the incorrect fix).
9255 - When warning about missing zlib development packages during compile,
9256 give the correct package names. Bugfix on 0.2.0.1-alpha.
9259 - Directory authorities now log the source of a rejected POSTed v3
9261 - Make compilation with clang possible when using
9262 --enable-gcc-warnings by removing two warning options that clang
9263 hasn't implemented yet and by fixing a few warnings. Implements
9265 - When expiring circuits, use microsecond timers rather than
9266 one-second timers. This can avoid an unpleasant situation where a
9267 circuit is launched near the end of one second and expired right
9268 near the beginning of the next, and prevent fluctuations in circuit
9270 - Use computed circuit-build timeouts to decide when to launch
9271 parallel introduction circuits for hidden services. (Previously,
9272 we would retry after 15 seconds.)
9273 - Update to the April 1 2011 Maxmind GeoLite Country database.
9276 - Create the /var/run/tor directory on startup on OpenSUSE if it is
9277 not already created. Patch from Andreas Stieger. Fixes bug 2573.
9279 o Documentation changes:
9280 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9281 - Resolve all doxygen warnings except those for missing documentation.
9283 - Add doxygen documentation for more functions, fields, and types.
9286 Changes in version 0.2.2.23-alpha - 2011-03-08
9287 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
9288 they restart they don't lose their bandwidth capacity estimate. This
9289 release also fixes a diverse set of user-facing bugs, ranging from
9290 relays overrunning their rate limiting to clients falsely warning about
9291 clock skew to bridge descriptor leaks by our bridge directory authority.
9294 - Stop sending a CLOCK_SKEW controller status event whenever
9295 we fetch directory information from a relay that has a wrong clock.
9296 Instead, only inform the controller when it's a trusted authority
9297 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9298 the rest of bug 1074.
9299 - Fix an assert in parsing router descriptors containing IPv6
9300 addresses. This one took down the directory authorities when
9301 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9302 - Make the bridge directory authority refuse to answer directory
9303 requests for "all" descriptors. It used to include bridge
9304 descriptors in its answer, which was a major information leak.
9305 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9306 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9307 Tor would ignore their RelayBandwidthBurst setting,
9308 potentially using more bandwidth than expected. Bugfix on
9309 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9310 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9311 hidserv" in her torrc. The 'hidserv' argument never controlled
9312 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9315 - Relays now save observed peak bandwidth throughput rates to their
9316 state file (along with total usage, which was already saved)
9317 so that they can determine their correct estimated bandwidth on
9318 restart. Resolves bug 1863, where Tor relays would reset their
9319 estimated bandwidth to 0 after restarting.
9320 - Directory authorities now take changes in router IP address and
9321 ORPort into account when determining router stability. Previously,
9322 if a router changed its IP or ORPort, the authorities would not
9323 treat it as having any downtime for the purposes of stability
9324 calculation, whereas clients would experience downtime since the
9325 change could take a while to propagate to them. Resolves issue 1035.
9326 - Enable Address Space Layout Randomization (ASLR) and Data Execution
9327 Prevention (DEP) by default on Windows to make it harder for
9328 attackers to exploit vulnerabilities. Patch from John Brooks.
9330 o Minor bugfixes (on 0.2.1.x and earlier):
9331 - Fix a rare crash bug that could occur when a client was configured
9332 with a large number of bridges. Fixes bug 2629; bugfix on
9333 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9334 - Avoid a double mark-for-free warning when failing to attach a
9335 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9337 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9338 found by "cypherpunks". This bug was introduced before the first
9339 Tor release, in svn commit r110.
9340 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
9341 don't mention them in the manpage. Fixes bug 2450; issue
9342 spotted by keb and G-Lo.
9343 - Fix a bug in bandwidth history state parsing that could have been
9344 triggered if a future version of Tor ever changed the timing
9345 granularity at which bandwidth history is measured. Bugfix on
9347 - When a relay decides that its DNS is too broken for it to serve
9348 as an exit server, it advertised itself as a non-exit, but
9349 continued to act as an exit. This could create accidental
9350 partitioning opportunities for users. Instead, if a relay is
9351 going to advertise reject *:* as its exit policy, it should
9352 really act with exit policy "reject *:*". Fixes bug 2366.
9353 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
9354 - In the special case where you configure a public exit relay as your
9355 bridge, Tor would be willing to use that exit relay as the last
9356 hop in your circuit as well. Now we fail that circuit instead.
9357 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
9358 - Fix a bug with our locking implementation on Windows that couldn't
9359 correctly detect when a file was already locked. Fixes bug 2504,
9360 bugfix on 0.2.1.6-alpha.
9361 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9362 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9364 - Set target port in get_interface_address6() correctly. Bugfix
9365 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9366 - Directory authorities are now more robust to hops back in time
9367 when calculating router stability. Previously, if a run of uptime
9368 or downtime appeared to be negative, the calculation could give
9369 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
9371 - Fix an assert that got triggered when using the TestingTorNetwork
9372 configuration option and then issuing a GETINFO config-text control
9373 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
9375 o Minor bugfixes (on 0.2.2.x):
9376 - Clients should not weight BadExit nodes as Exits in their node
9377 selection. Similarly, directory authorities should not count BadExit
9378 bandwidth as Exit bandwidth when computing bandwidth-weights.
9379 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
9380 - Correctly clear our dir_read/dir_write history when there is an
9381 error parsing any bw history value from the state file. Bugfix on
9383 - Resolve a bug in verifying signatures of directory objects
9384 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
9385 Fixes bug 2409. Found by "piebeer".
9386 - Bridge authorities no longer crash on SIGHUP when they try to
9387 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
9391 - Log less aggressively about circuit timeout changes, and improve
9392 some other circuit timeout messages. Resolves bug 2004.
9393 - Log a little more clearly about the times at which we're no longer
9394 accepting new connections. Resolves bug 2181.
9395 - Reject attempts at the client side to open connections to private
9396 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
9397 a randomly chosen exit node. Attempts to do so are always
9398 ill-defined, generally prevented by exit policies, and usually
9399 in error. This will also help to detect loops in transparent
9400 proxy configurations. You can disable this feature by setting
9401 "ClientRejectInternalAddresses 0" in your torrc.
9402 - Always treat failure to allocate an RSA key as an unrecoverable
9404 - Update to the March 1 2011 Maxmind GeoLite Country database.
9406 o Minor features (log subsystem):
9407 - Add documentation for configuring logging at different severities in
9408 different log domains. We've had this feature since 0.2.1.1-alpha,
9409 but for some reason it never made it into the manpage. Fixes
9411 - Make it simpler to specify "All log domains except for A and B".
9412 Previously you needed to say "[*,~A,~B]". Now you can just say
9414 - Add a "LogMessageDomains 1" option to include the domains of log
9415 messages along with the messages. Without this, there's no way
9416 to use log domains without reading the source or doing a lot
9419 o Packaging changes:
9420 - Stop shipping the Tor specs files and development proposal documents
9421 in the tarball. They are now in a separate git repository at
9422 git://git.torproject.org/torspec.git
9425 Changes in version 0.2.1.30 - 2011-02-23
9426 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9427 change is a slight tweak to Tor's TLS handshake that makes relays
9428 and bridges that run this new version reachable from Iran again.
9429 We don't expect this tweak will win the arms race long-term, but it
9430 buys us time until we roll out a better solution.
9433 - Stop sending a CLOCK_SKEW controller status event whenever
9434 we fetch directory information from a relay that has a wrong clock.
9435 Instead, only inform the controller when it's a trusted authority
9436 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9437 the rest of bug 1074.
9438 - Fix a bounds-checking error that could allow an attacker to
9439 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9441 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9442 Tor would ignore their RelayBandwidthBurst setting,
9443 potentially using more bandwidth than expected. Bugfix on
9444 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9445 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9446 hidserv" in her torrc. The 'hidserv' argument never controlled
9447 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9450 - Adjust our TLS Diffie-Hellman parameters to match those used by
9452 - Update to the February 1 2011 Maxmind GeoLite Country database.
9455 - Check for and reject overly long directory certificates and
9456 directory tokens before they have a chance to hit any assertions.
9457 Bugfix on 0.2.1.28. Found by "doorss".
9458 - Bring the logic that gathers routerinfos and assesses the
9459 acceptability of circuits into line. This prevents a Tor OP from
9460 getting locked in a cycle of choosing its local OR as an exit for a
9461 path (due to a .exit request) and then rejecting the circuit because
9462 its OR is not listed yet. It also prevents Tor clients from using an
9463 OR running in the same instance as an exit (due to a .exit request)
9464 if the OR does not meet the same requirements expected of an OR
9465 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9467 o Packaging changes:
9468 - Stop shipping the Tor specs files and development proposal documents
9469 in the tarball. They are now in a separate git repository at
9470 git://git.torproject.org/torspec.git
9471 - Do not include Git version tags as though they are SVN tags when
9472 generating a tarball from inside a repository that has switched
9473 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9476 Changes in version 0.2.2.22-alpha - 2011-01-25
9477 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
9478 main other change is a slight tweak to Tor's TLS handshake that makes
9479 relays and bridges that run this new version reachable from Iran again.
9480 We don't expect this tweak will win the arms race long-term, but it
9481 will buy us a bit more time until we roll out a better solution.
9484 - Fix a bounds-checking error that could allow an attacker to
9485 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9487 - Don't assert when changing from bridge to relay or vice versa
9488 via the controller. The assert happened because we didn't properly
9489 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
9490 bug 2433. Reported by bastik.
9493 - Adjust our TLS Diffie-Hellman parameters to match those used by
9495 - Provide a log message stating which geoip file we're parsing
9496 instead of just stating that we're parsing the geoip file.
9497 Implements ticket 2432.
9500 - Check for and reject overly long directory certificates and
9501 directory tokens before they have a chance to hit any assertions.
9502 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
9505 Changes in version 0.2.2.21-alpha - 2011-01-15
9506 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
9507 continues our recent code security audit work. The main fix resolves
9508 a remote heap overflow vulnerability that can allow remote code
9509 execution (CVE-2011-0427). Other fixes address a variety of assert
9510 and crash bugs, most of which we think are hard to exploit remotely.
9512 o Major bugfixes (security), also included in 0.2.1.29:
9513 - Fix a heap overflow bug where an adversary could cause heap
9514 corruption. This bug probably allows remote code execution
9515 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9517 - Prevent a denial-of-service attack by disallowing any
9518 zlib-compressed data whose compression factor is implausibly
9519 high. Fixes part of bug 2324; reported by "doorss".
9520 - Zero out a few more keys in memory before freeing them. Fixes
9521 bug 2384 and part of bug 2385. These key instances found by
9522 "cypherpunks", based on Andrew Case's report about being able
9523 to find sensitive data in Tor's memory space if you have enough
9524 permissions. Bugfix on 0.0.2pre9.
9526 o Major bugfixes (crashes), also included in 0.2.1.29:
9527 - Prevent calls to Libevent from inside Libevent log handlers.
9528 This had potential to cause a nasty set of crashes, especially
9529 if running Libevent with debug logging enabled, and running
9530 Tor with a controller watching for low-severity log messages.
9531 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9532 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9533 underflow errors there too. Fixes the other part of bug 2324.
9534 - Fix a bug where we would assert if we ever had a
9535 cached-descriptors.new file (or another file read directly into
9536 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9537 on 0.2.1.25. Found by doorss.
9538 - Fix some potential asserts and parsing issues with grossly
9539 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9542 o Minor bugfixes (other), also included in 0.2.1.29:
9543 - Fix a bug with handling misformed replies to reverse DNS lookup
9544 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9545 bug reported by doorss.
9546 - Fix compilation on mingw when a pthreads compatibility library
9547 has been installed. (We don't want to use it, so we shouldn't
9548 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9549 - Fix a bug where we would declare that we had run out of virtual
9550 addresses when the address space was only half-exhausted. Bugfix
9552 - Correctly handle the case where AutomapHostsOnResolve is set but
9553 no virtual addresses are available. Fixes bug 2328; bugfix on
9554 0.1.2.1-alpha. Bug found by doorss.
9555 - Correctly handle wrapping around when we run out of virtual
9556 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
9558 o Minor features, also included in 0.2.1.29:
9559 - Update to the January 1 2011 Maxmind GeoLite Country database.
9560 - Introduce output size checks on all of our decryption functions.
9562 o Build changes, also included in 0.2.1.29:
9563 - Tor does not build packages correctly with Automake 1.6 and earlier;
9564 added a check to Makefile.am to make sure that we're building with
9565 Automake 1.7 or later.
9566 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9567 because we built it with a too-old version of automake. Thus that
9568 release broke ./configure --enable-openbsd-malloc, which is popular
9569 among really fast exit relays on Linux.
9571 o Major bugfixes, new in 0.2.2.21-alpha:
9572 - Prevent crash/heap corruption when the cbtnummodes consensus
9573 parameter is set to 0 or large values. Fixes bug 2317; bugfix
9576 o Major features, new in 0.2.2.21-alpha:
9577 - Introduce minimum/maximum values that clients will believe
9578 from the consensus. Now we'll have a better chance to avoid crashes
9579 or worse when a consensus param has a weird value.
9581 o Minor features, new in 0.2.2.21-alpha:
9582 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
9583 used on bridges, and it makes bridge scanning somewhat easier.
9584 - If writing the state file to disk fails, wait up to an hour before
9585 retrying again, rather than trying again each second. Fixes bug
9586 2346; bugfix on Tor 0.1.1.3-alpha.
9587 - Make Libevent log messages get delivered to controllers later,
9588 and not from inside the Libevent log handler. This prevents unsafe
9589 reentrant Libevent calls while still letting the log messages
9591 - Detect platforms that brokenly use a signed size_t, and refuse to
9592 build there. Found and analyzed by doorss and rransom.
9593 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
9596 o Minor bugfixes, new in 0.2.2.21-alpha:
9597 - Handle SOCKS messages longer than 128 bytes long correctly, rather
9598 than waiting forever for them to finish. Fixes bug 2330; bugfix
9599 on 0.2.0.16-alpha. Found by doorss.
9600 - Add assertions to check for overflow in arguments to
9601 base32_encode() and base32_decode(); fix a signed-unsigned
9602 comparison there too. These bugs are not actually reachable in Tor,
9603 but it's good to prevent future errors too. Found by doorss.
9604 - Correctly detect failures to create DNS requests when using Libevent
9605 versions before v2. (Before Libevent 2, we used our own evdns
9606 implementation. Its return values for Libevent's evdns_resolve_*()
9607 functions are not consistent with those from Libevent.) Fixes bug
9608 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
9610 o Documentation, new in 0.2.2.21-alpha:
9611 - Document the default socks host and port (127.0.0.1:9050) for
9615 Changes in version 0.2.1.29 - 2011-01-15
9616 Tor 0.2.1.29 continues our recent code security audit work. The main
9617 fix resolves a remote heap overflow vulnerability that can allow remote
9618 code execution. Other fixes address a variety of assert and crash bugs,
9619 most of which we think are hard to exploit remotely.
9621 o Major bugfixes (security):
9622 - Fix a heap overflow bug where an adversary could cause heap
9623 corruption. This bug probably allows remote code execution
9624 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9626 - Prevent a denial-of-service attack by disallowing any
9627 zlib-compressed data whose compression factor is implausibly
9628 high. Fixes part of bug 2324; reported by "doorss".
9629 - Zero out a few more keys in memory before freeing them. Fixes
9630 bug 2384 and part of bug 2385. These key instances found by
9631 "cypherpunks", based on Andrew Case's report about being able
9632 to find sensitive data in Tor's memory space if you have enough
9633 permissions. Bugfix on 0.0.2pre9.
9635 o Major bugfixes (crashes):
9636 - Prevent calls to Libevent from inside Libevent log handlers.
9637 This had potential to cause a nasty set of crashes, especially
9638 if running Libevent with debug logging enabled, and running
9639 Tor with a controller watching for low-severity log messages.
9640 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9641 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9642 underflow errors there too. Fixes the other part of bug 2324.
9643 - Fix a bug where we would assert if we ever had a
9644 cached-descriptors.new file (or another file read directly into
9645 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9646 on 0.2.1.25. Found by doorss.
9647 - Fix some potential asserts and parsing issues with grossly
9648 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9651 o Minor bugfixes (other):
9652 - Fix a bug with handling misformed replies to reverse DNS lookup
9653 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9654 bug reported by doorss.
9655 - Fix compilation on mingw when a pthreads compatibility library
9656 has been installed. (We don't want to use it, so we shouldn't
9657 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9658 - Fix a bug where we would declare that we had run out of virtual
9659 addresses when the address space was only half-exhausted. Bugfix
9661 - Correctly handle the case where AutomapHostsOnResolve is set but
9662 no virtual addresses are available. Fixes bug 2328; bugfix on
9663 0.1.2.1-alpha. Bug found by doorss.
9664 - Correctly handle wrapping around to when we run out of virtual
9665 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
9666 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9667 because we built it with a too-old version of automake. Thus that
9668 release broke ./configure --enable-openbsd-malloc, which is popular
9669 among really fast exit relays on Linux.
9672 - Update to the January 1 2011 Maxmind GeoLite Country database.
9673 - Introduce output size checks on all of our decryption functions.
9676 - Tor does not build packages correctly with Automake 1.6 and earlier;
9677 added a check to Makefile.am to make sure that we're building with
9678 Automake 1.7 or later.
9681 Changes in version 0.2.2.20-alpha - 2010-12-17
9682 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
9683 exploitable bugs. We also fix a variety of other significant bugs,
9684 change the IP address for one of our directory authorities, and update
9685 the minimum version that Tor relays must run to join the network.
9688 - Fix a remotely exploitable bug that could be used to crash instances
9689 of Tor remotely by overflowing on the heap. Remote-code execution
9690 hasn't been confirmed, but can't be ruled out. Everyone should
9691 upgrade. Bugfix on the 0.1.1 series and later.
9692 - Fix a bug that could break accounting on 64-bit systems with large
9693 time_t values, making them hibernate for impossibly long intervals.
9694 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
9695 - Fix a logic error in directory_fetches_from_authorities() that
9696 would cause all _non_-exits refusing single-hop-like circuits
9697 to fetch from authorities, when we wanted to have _exits_ fetch
9698 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
9700 - Fix a stream fairness bug that would cause newer streams on a given
9701 circuit to get preference when reading bytes from the origin or
9702 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
9703 introduced before the first Tor release, in svn revision r152.
9705 o Directory authority changes:
9706 - Change IP address and ports for gabelmoo (v3 directory authority).
9709 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
9710 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
9711 - Fix an off-by-one error in calculating some controller command
9712 argument lengths. Fortunately, this mistake is harmless since
9713 the controller code does redundant NUL termination too. Found by
9714 boboper. Bugfix on 0.1.1.1-alpha.
9715 - Do not dereference NULL if a bridge fails to build its
9716 extra-info descriptor. Found by an anonymous commenter on
9717 Trac. Bugfix on 0.2.2.19-alpha.
9720 - Update to the December 1 2010 Maxmind GeoLite Country database.
9721 - Directory authorities now reject relays running any versions of
9722 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
9723 known bugs that keep RELAY_EARLY cells from working on rendezvous
9724 circuits. Followup to fix for bug 2081.
9725 - Directory authorities now reject relays running any version of Tor
9726 older than 0.2.0.26-rc. That version is the earliest that fetches
9727 current directory information correctly. Fixes bug 2156.
9728 - Report only the top 10 ports in exit-port stats in order not to
9729 exceed the maximum extra-info descriptor length of 50 KB. Implements
9733 Changes in version 0.2.1.28 - 2010-12-17
9734 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9735 exploitable bugs. We also took this opportunity to change the IP address
9736 for one of our directory authorities, and to update the geoip database
9740 - Fix a remotely exploitable bug that could be used to crash instances
9741 of Tor remotely by overflowing on the heap. Remote-code execution
9742 hasn't been confirmed, but can't be ruled out. Everyone should
9743 upgrade. Bugfix on the 0.1.1 series and later.
9745 o Directory authority changes:
9746 - Change IP address and ports for gabelmoo (v3 directory authority).
9749 - Update to the December 1 2010 Maxmind GeoLite Country database.
9752 Changes in version 0.2.1.27 - 2010-11-23
9753 Yet another OpenSSL security patch broke its compatibility with Tor:
9754 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9755 also took this opportunity to fix several crash bugs, integrate a new
9756 directory authority, and update the bundled GeoIP database.
9759 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9760 No longer set the tlsext_host_name extension on server SSL objects;
9761 but continue to set it on client SSL objects. Our goal in setting
9762 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9763 bugfix on 0.2.1.1-alpha.
9764 - Do not log messages to the controller while shrinking buffer
9765 freelists. Doing so would sometimes make the controller connection
9766 try to allocate a buffer chunk, which would mess up the internals
9767 of the freelist and cause an assertion failure. Fixes bug 1125;
9768 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9769 - Learn our external IP address when we're a relay or bridge, even if
9770 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9771 where we introduced bridge relays that don't need to publish to
9772 be useful. Fixes bug 2050.
9773 - Do even more to reject (and not just ignore) annotations on
9774 router descriptors received anywhere but from the cache. Previously
9775 we would ignore such annotations at first, but cache them to disk
9776 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9777 - When you're using bridges and your network goes away and your
9778 bridges get marked as down, recover when you attempt a new socks
9779 connection (if the network is back), rather than waiting up to an
9780 hour to try fetching new descriptors for your bridges. Bugfix on
9781 0.2.0.3-alpha; fixes bug 1981.
9784 - Move to the November 2010 Maxmind GeoLite country db (rather
9785 than the June 2009 ip-to-country GeoIP db) for our statistics that
9786 count how many users relays are seeing from each country. Now we'll
9787 have more accurate data, especially for many African countries.
9789 o New directory authorities:
9790 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9794 - Fix an assertion failure that could occur in directory caches or
9795 bridge users when using a very short voting interval on a testing
9796 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9798 - Enforce multiplicity rules when parsing annotations. Bugfix on
9799 0.2.0.8-alpha. Found by piebeer.
9800 - Allow handshaking OR connections to take a full KeepalivePeriod
9801 seconds to handshake. Previously, we would close them after
9802 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9803 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9805 - When building with --enable-gcc-warnings on OpenBSD, disable
9806 warnings in system headers. This makes --enable-gcc-warnings
9807 pass on OpenBSD 4.8.
9810 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9811 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9812 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9813 Servers can start sending this code when enough clients recognize
9814 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9815 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9816 Patch from mingw-san.
9819 - Remove the old debian/ directory from the main Tor distribution.
9820 The official Tor-for-debian git repository lives at the URL
9821 https://git.torproject.org/debian/tor.git
9822 - Stop shipping the old doc/website/ directory in the tarball. We
9823 changed the website format in late 2010, and what we shipped in
9824 0.2.1.26 really wasn't that useful anyway.
9827 Changes in version 0.2.2.19-alpha - 2010-11-22
9828 Yet another OpenSSL security patch broke its compatibility with Tor:
9829 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
9832 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9833 No longer set the tlsext_host_name extension on server SSL objects;
9834 but continue to set it on client SSL objects. Our goal in setting
9835 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9836 bugfix on 0.2.1.1-alpha.
9839 - Try harder not to exceed the maximum length of 50 KB when writing
9840 statistics to extra-info descriptors. This bug was triggered by very
9841 fast relays reporting exit-port, entry, and dirreq statistics.
9842 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
9843 - Publish a router descriptor even if generating an extra-info
9844 descriptor fails. Previously we would not publish a router
9845 descriptor without an extra-info descriptor; this can cause fast
9846 exit relays collecting exit-port statistics to drop from the
9847 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
9850 Changes in version 0.2.2.18-alpha - 2010-11-16
9851 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
9852 us lately, makes unpublished bridge relays able to detect their IP
9853 address, and fixes a wide variety of other bugs to get us much closer
9854 to a stable release.
9857 - Do even more to reject (and not just ignore) annotations on
9858 router descriptors received anywhere but from the cache. Previously
9859 we would ignore such annotations at first, but cache them to disk
9860 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9861 - Do not log messages to the controller while shrinking buffer
9862 freelists. Doing so would sometimes make the controller connection
9863 try to allocate a buffer chunk, which would mess up the internals
9864 of the freelist and cause an assertion failure. Fixes bug 1125;
9865 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9866 - Learn our external IP address when we're a relay or bridge, even if
9867 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9868 where we introduced bridge relays that don't need to publish to
9869 be useful. Fixes bug 2050.
9870 - Maintain separate TLS contexts and certificates for incoming and
9871 outgoing connections in bridge relays. Previously we would use the
9872 same TLS contexts and certs for incoming and outgoing connections.
9873 Bugfix on 0.2.0.3-alpha; addresses bug 988.
9874 - Maintain separate identity keys for incoming and outgoing TLS
9875 contexts in bridge relays. Previously we would use the same
9876 identity keys for incoming and outgoing TLS contexts. Bugfix on
9877 0.2.0.3-alpha; addresses the other half of bug 988.
9878 - Avoid an assertion failure when we as an authority receive a
9879 duplicate upload of a router descriptor that we already have,
9880 but which we previously considered an obsolete descriptor.
9881 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
9882 - Avoid a crash bug triggered by looking at a dangling pointer while
9883 setting the network status consensus. Found by Robert Ransom.
9884 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
9885 - Fix a logic error where servers that _didn't_ act as exits would
9886 try to keep their server lists more aggressively up to date than
9887 exits, when it was supposed to be the other way around. Bugfix
9890 o Minor bugfixes (on Tor 0.2.1.x and earlier):
9891 - When we're trying to guess whether we know our IP address as
9892 a relay, we would log various ways that we failed to guess
9893 our address, but never log that we ended up guessing it
9894 successfully. Now add a log line to help confused and anxious
9895 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
9896 - Bring the logic that gathers routerinfos and assesses the
9897 acceptability of circuits into line. This prevents a Tor OP from
9898 getting locked in a cycle of choosing its local OR as an exit for a
9899 path (due to a .exit request) and then rejecting the circuit because
9900 its OR is not listed yet. It also prevents Tor clients from using an
9901 OR running in the same instance as an exit (due to a .exit request)
9902 if the OR does not meet the same requirements expected of an OR
9903 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9904 - Correctly describe errors that occur when generating a TLS object.
9905 Previously we would attribute them to a failure while generating a
9906 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9908 - Enforce multiplicity rules when parsing annotations. Bugfix on
9909 0.2.0.8-alpha. Found by piebeer.
9910 - Fix warnings that newer versions of autoconf produced during
9911 ./autogen.sh. These warnings appear to be harmless in our case,
9912 but they were extremely verbose. Fixes bug 2020.
9914 o Minor bugfixes (on Tor 0.2.2.x):
9915 - Enable protection of small arrays whenever we build with gcc
9916 hardening features, not only when also building with warnings
9917 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
9920 - Make hidden services work better in private Tor networks by not
9921 requiring any uptime to join the hidden service descriptor
9922 DHT. Implements ticket 2088.
9923 - Rate-limit the "your application is giving Tor only an IP address"
9924 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
9925 - When AllowSingleHopExits is set, print a warning to explain to the
9926 relay operator why most clients are avoiding her relay.
9927 - Update to the November 1 2010 Maxmind GeoLite Country database.
9929 o Code simplifications and refactoring:
9930 - When we fixed bug 1038 we had to put in a restriction not to send
9931 RELAY_EARLY cells on rend circuits. This was necessary as long
9932 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9933 active. Now remove this obsolete check. Resolves bug 2081.
9934 - Some options used different conventions for uppercasing of acronyms
9935 when comparing manpage and source. Fix those in favor of the
9936 manpage, as it makes sense to capitalize acronyms.
9937 - Remove the torrc.complete file. It hasn't been kept up to date
9938 and users will have better luck checking out the manpage.
9939 - Remove the obsolete "NoPublish" option; it has been flagged
9940 as obsolete and has produced a warning since 0.1.1.18-rc.
9941 - Remove everything related to building the expert bundle for OS X.
9942 It has confused many users, doesn't work right on OS X 10.6,
9943 and is hard to get rid of once installed. Resolves bug 1274.
9946 Changes in version 0.2.2.17-alpha - 2010-09-30
9947 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
9948 to use one-hop circuits (which can put the exit relays at higher risk,
9949 plus unbalance the network); fixes a big bug in bandwidth accounting
9950 for relays that want to limit their monthly bandwidth use; fixes a
9951 big pile of bugs in how clients tolerate temporary network failure;
9952 and makes our adaptive circuit build timeout feature (which improves
9953 client performance if your network is fast while not breaking things
9954 if your network is slow) better handle bad networks.
9957 - Exit relays now try harder to block exit attempts from unknown
9958 relays, to make it harder for people to use them as one-hop proxies
9959 a la tortunnel. Controlled by the refuseunknownexits consensus
9960 parameter (currently enabled), or you can override it on your
9961 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
9963 o Major bugfixes (0.2.1.x and earlier):
9964 - Fix a bug in bandwidth accounting that could make us use twice
9965 the intended bandwidth when our interval start changes due to
9966 daylight saving time. Now we tolerate skew in stored vs computed
9967 interval starts: if the start of the period changes by no more than
9968 50% of the period's duration, we remember bytes that we transferred
9969 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
9970 - Always search the Windows system directory for system DLLs, and
9971 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
9972 - When you're using bridges and your network goes away and your
9973 bridges get marked as down, recover when you attempt a new socks
9974 connection (if the network is back), rather than waiting up to an
9975 hour to try fetching new descriptors for your bridges. Bugfix on
9976 0.2.0.3-alpha; fixes bug 1981.
9978 o Major bugfixes (on 0.2.2.x):
9979 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
9981 - Fix a segfault that could happen when operating a bridge relay with
9982 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
9983 - The consensus bandwidth-weights (used by clients to choose fast
9984 relays) entered an unexpected edge case in September where
9985 Exits were much scarcer than Guards, resulting in bad weight
9986 recommendations. Now we compute them using new constraints that
9987 should succeed in all cases. Also alter directory authorities to
9988 not include the bandwidth-weights line if they fail to produce
9989 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
9990 - When weighting bridges during path selection, we used to trust
9991 the bandwidths they provided in their descriptor, only capping them
9992 at 10MB/s. This turned out to be problematic for two reasons:
9993 Bridges could claim to handle a lot more traffic then they
9994 actually would, thus making more clients pick them and have a
9995 pretty effective DoS attack. The other issue is that new bridges
9996 that might not have a good estimate for their bw capacity yet
9997 would not get used at all unless no other bridges are available
9998 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
10000 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
10001 - Ignore cannibalized circuits when recording circuit build times.
10002 This should provide for a minor performance improvement for hidden
10003 service users using 0.2.2.14-alpha, and should remove two spurious
10004 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
10005 - Simplify the logic that causes us to decide if the network is
10006 unavailable for purposes of recording circuit build times. If we
10007 receive no cells whatsoever for the entire duration of a circuit's
10008 full measured lifetime, the network is probably down. Also ignore
10009 one-hop directory fetching circuit timeouts when calculating our
10010 circuit build times. These changes should hopefully reduce the
10011 cases where we see ridiculous circuit build timeouts for people
10012 with spotty wireless connections. Fixes part of bug 1772; bugfix
10014 - Prevent the circuit build timeout from becoming larger than
10015 the maximum build time we have ever seen. Also, prevent the time
10016 period for measurement circuits from becoming larger than twice that
10017 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
10020 - When we run out of directory information such that we can't build
10021 circuits, but then get enough that we can build circuits, log when
10022 we actually construct a circuit, so the user has a better chance of
10023 knowing what's going on. Fixes bug 1362.
10024 - Be more generous with how much bandwidth we'd use up (with
10025 accounting enabled) before entering "soft hibernation". Previously,
10026 we'd refuse new connections and circuits once we'd used up 95% of
10027 our allotment. Now, we use up 95% of our allotment, AND make sure
10028 that we have no more than 500MB (or 3 hours of expected traffic,
10029 whichever is lower) remaining before we enter soft hibernation.
10030 - If we've configured EntryNodes and our network goes away and/or all
10031 our entrynodes get marked down, optimistically retry them all when
10032 a new socks application request appears. Fixes bug 1882.
10033 - Add some more defensive programming for architectures that can't
10034 handle unaligned integer accesses. We don't know of any actual bugs
10035 right now, but that's the best time to fix them. Fixes bug 1943.
10036 - Support line continuations in the torrc config file. If a line
10037 ends with a single backslash character, the newline is ignored, and
10038 the configuration value is treated as continuing on the next line.
10041 o Minor bugfixes (on 0.2.1.x and earlier):
10042 - For bandwidth accounting, calculate our expected bandwidth rate
10043 based on the time during which we were active and not in
10044 soft-hibernation during the last interval. Previously, we were
10045 also considering the time spent in soft-hibernation. If this
10046 was a long time, we would wind up underestimating our bandwidth
10047 by a lot, and skewing our wakeup time towards the start of the
10048 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
10050 o Minor bugfixes (on 0.2.2.x):
10051 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
10052 which were disabled by the circuit build timeout changes in
10053 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
10054 - Make sure we don't warn about missing bandwidth weights when
10055 choosing bridges or other relays not in the consensus. Bugfix on
10056 0.2.2.10-alpha; fixes bug 1805.
10057 - In our logs, do not double-report signatures from unrecognized
10058 authorities both as "from unknown authority" and "not
10059 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
10062 Changes in version 0.2.2.16-alpha - 2010-09-17
10063 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
10064 evident at exit relays), and also continues to resolve all the little
10065 bugs that have been filling up trac lately.
10067 o Major bugfixes (stream-level fairness):
10068 - When receiving a circuit-level SENDME for a blocked circuit, try
10069 to package cells fairly from all the streams that had previously
10070 been blocked on that circuit. Previously, we had started with the
10071 oldest stream, and allowed each stream to potentially exhaust
10072 the circuit's package window. This gave older streams on any
10073 given circuit priority over newer ones. Fixes bug 1937. Detected
10074 originally by Camilo Viecco. This bug was introduced before the
10075 first Tor release, in svn commit r152: it is the new winner of
10076 the longest-lived bug prize.
10077 - When the exit relay got a circuit-level sendme cell, it started
10078 reading on the exit streams, even if had 500 cells queued in the
10079 circuit queue already, so the circuit queue just grew and grew in
10080 some cases. We fix this by not re-enabling reading on receipt of a
10081 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
10082 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
10084 - Newly created streams were allowed to read cells onto circuits,
10085 even if the circuit's cell queue was blocked and waiting to drain.
10086 This created potential unfairness, as older streams would be
10087 blocked, but newer streams would gladly fill the queue completely.
10088 We add code to detect this situation and prevent any stream from
10089 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
10093 - Update to the September 1 2010 Maxmind GeoLite Country database.
10094 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
10095 not. This would lead to a cookie that is still not group readable.
10096 Closes bug 1843. Suggested by katmagic.
10097 - When logging a rate-limited warning, we now mention how many messages
10098 got suppressed since the last warning.
10099 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
10100 do individual connection-level rate limiting of clients. The torrc
10101 config options with the same names trump the consensus params, if
10102 both are present. Replaces the old "bwconnrate" and "bwconnburst"
10103 consensus params which were broken from 0.2.2.7-alpha through
10104 0.2.2.14-alpha. Closes bug 1947.
10105 - When a router changes IP address or port, authorities now launch
10106 a new reachability test for it. Implements ticket 1899.
10107 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
10108 2 no signature, 4 required" messages about consensus signatures
10109 easier to read, and make sure they get logged at the same severity
10110 as the messages explaining which keys are which. Fixes bug 1290.
10111 - Don't warn when we have a consensus that we can't verify because
10112 of missing certificates, unless those certificates are ones
10113 that we have been trying and failing to download. Fixes bug 1145.
10114 - If you configure your bridge with a known identity fingerprint,
10115 and the bridge authority is unreachable (as it is in at least
10116 one country now), fall back to directly requesting the descriptor
10117 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
10119 - When building with --enable-gcc-warnings on OpenBSD, disable
10120 warnings in system headers. This makes --enable-gcc-warnings
10121 pass on OpenBSD 4.8.
10123 o Minor bugfixes (on 0.2.1.x and earlier):
10124 - Authorities will now attempt to download consensuses if their
10125 own efforts to make a live consensus have failed. This change
10126 means authorities that restart will fetch a valid consensus, and
10127 it means authorities that didn't agree with the current consensus
10128 will still fetch and serve it if it has enough signatures. Bugfix
10129 on 0.2.0.9-alpha; fixes bug 1300.
10130 - Ensure DNS requests launched by "RESOLVE" commands from the
10131 controller respect the __LeaveStreamsUnattached setconf options. The
10132 same goes for requests launched via DNSPort or transparent
10133 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
10134 - Allow handshaking OR connections to take a full KeepalivePeriod
10135 seconds to handshake. Previously, we would close them after
10136 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10137 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10139 - Rate-limit "Failed to hand off onionskin" warnings.
10140 - Never relay a cell for a circuit we have already destroyed.
10141 Between marking a circuit as closeable and finally closing it,
10142 it may have been possible for a few queued cells to get relayed,
10143 even though they would have been immediately dropped by the next
10144 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
10145 - Never queue a cell for a circuit that's already been marked
10147 - Never vote for a server as "Running" if we have a descriptor for
10148 it claiming to be hibernating, and that descriptor was published
10149 more recently than our last contact with the server. Bugfix on
10150 0.2.0.3-alpha; fixes bug 911.
10151 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
10154 o Minor bugfixes (on 0.2.2.x):
10155 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
10156 down if a directory fetch fails and you've configured either
10157 bridges or EntryNodes. The intent was to mark the relay as down
10158 _unless_ you're using bridges or EntryNodes, since if you are
10159 then you could quickly run out of entry points.
10160 - Fix the Windows directory-listing code. A bug introduced in
10161 0.2.2.14-alpha could make Windows directory servers forget to load
10162 some of their cached v2 networkstatus files.
10163 - Really allow clients to use relays as bridges. Fixes bug 1776;
10164 bugfix on 0.2.2.15-alpha.
10165 - Demote a warn to info that happens when the CellStatistics option
10166 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
10167 Reported by Moritz Bartl.
10168 - On Windows, build correctly either with or without Unicode support.
10169 This is necessary so that Tor can support fringe platforms like
10170 Windows 98 (which has no Unicode), or Windows CE (which has no
10171 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
10174 - Add a unit test for cross-platform directory-listing code.
10177 Changes in version 0.2.2.15-alpha - 2010-08-18
10178 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
10179 fixes a variety of other bugs that were preventing performance
10180 experiments from moving forward, fixes several bothersome memory leaks,
10181 and generally closes a lot of smaller bugs that have been filling up
10185 - Stop assigning the HSDir flag to relays that disable their
10186 DirPort (and thus will refuse to answer directory requests). This
10187 fix should dramatically improve the reachability of hidden services:
10188 hidden services and hidden service clients pick six HSDir relays
10189 to store and retrieve the hidden service descriptor, and currently
10190 about half of the HSDir relays will refuse to work. Bugfix on
10191 0.2.0.10-alpha; fixes part of bug 1693.
10192 - The PerConnBWRate and Burst config options, along with the
10193 bwconnrate and bwconnburst consensus params, initialized each conn's
10194 token bucket values only when the connection is established. Now we
10195 update them if the config options change, and update them every time
10196 we get a new consensus. Otherwise we can encounter an ugly edge
10197 case where we initialize an OR conn to client-level bandwidth,
10198 but then later the relay joins the consensus and we leave it
10199 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
10200 - Fix a regression that caused Tor to rebind its ports if it receives
10201 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
10204 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
10205 should give us approximately 40-50% more Guard-flagged nodes,
10206 improving the anonymity the Tor network can provide and also
10207 decreasing the dropoff in throughput that relays experience when
10208 they first get the Guard flag.
10209 - Allow enabling or disabling the *Statistics config options while
10213 - Update to the August 1 2010 Maxmind GeoLite Country database.
10214 - Have the controller interface give a more useful message than
10215 "Internal Error" in response to failed GETINFO requests.
10216 - Warn when the same option is provided more than once in a torrc
10217 file, on the command line, or in a single SETCONF statement, and
10218 the option is one that only accepts a single line. Closes bug 1384.
10219 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10220 Patch from mingw-san.
10221 - Add support for the country code "{??}" in torrc options like
10222 ExcludeNodes, to indicate all routers of unknown country. Closes
10224 - Relays report the number of bytes spent on answering directory
10225 requests in extra-info descriptors similar to {read,write}-history.
10226 Implements enhancement 1790.
10228 o Minor bugfixes (on 0.2.1.x and earlier):
10229 - Complain if PublishServerDescriptor is given multiple arguments that
10230 include 0 or 1. This configuration will be rejected in the future.
10231 Bugfix on 0.2.0.1-alpha; closes bug 1107.
10232 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
10233 Bugfix on 0.2.0.13-alpha; closes bug 928.
10234 - Change "Application request when we're believed to be offline."
10235 notice to "Application request when we haven't used client
10236 functionality lately.", to clarify that it's not an error. Bugfix
10237 on 0.0.9.3; fixes bug 1222.
10238 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
10239 would return "551 Internal error" rather than "552 Unrecognized key
10240 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
10241 - Users can't configure a regular relay to be their bridge. It didn't
10242 work because when Tor fetched the bridge descriptor, it found
10243 that it already had it, and didn't realize that the purpose of the
10244 descriptor had changed. Now we replace routers with a purpose other
10245 than bridge with bridge descriptors when fetching them. Bugfix on
10246 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
10247 refetch the descriptor with router purpose 'general', disabling
10249 - Fix a rare bug in rend_fn unit tests: we would fail a test when
10250 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
10251 on 0.2.0.10-alpha; fixes bug 1808.
10252 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10253 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10254 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10255 Servers can start sending this code when enough clients recognize
10256 it. Also update the spec to reflect this new reason. Bugfix on
10257 0.1.0.1-rc; fixes part of bug 1793.
10258 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
10259 when we switch from being a public relay to a bridge. Otherwise
10260 there will still be clients that see the relay in their consensus,
10261 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
10263 - Instead of giving an assertion failure on an internal mismatch
10264 on estimated freelist size, just log a BUG warning and try later.
10265 Mitigates but does not fix bug 1125.
10266 - Fix an assertion failure that could occur in caches or bridge users
10267 when using a very short voting interval on a testing network.
10268 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
10270 o Minor bugfixes (on 0.2.2.x):
10271 - Alter directory authorities to always consider Exit-flagged nodes
10272 as potential Guard nodes in their votes. The actual decision to
10273 use Exits as Guards is done in the consensus bandwidth weights.
10274 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
10275 - When the controller is reporting the purpose of circuits that
10276 didn't finish building before the circuit build timeout, it was
10277 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
10278 - Our libevent version parsing code couldn't handle versions like
10279 1.4.14b-stable and incorrectly warned the user about using an
10280 old and broken version of libevent. Treat 1.4.14b-stable like
10281 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
10283 - Don't use substitution references like $(VAR:MOD) when
10284 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
10285 '$(:x)' to 'x' rather than the empty string. This bites us in
10286 doc/ when configured with --disable-asciidoc. Bugfix on
10287 0.2.2.9-alpha; fixes bug 1773.
10288 - Remove a spurious hidden service server-side log notice about
10289 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
10291 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
10293 - Correctly report written bytes on linked connections. Found while
10294 implementing 1790. Bugfix on 0.2.2.4-alpha.
10295 - Fix three memory leaks: one in circuit_build_times_parse_state(),
10296 one in dirvote_add_signatures_to_pending_consensus(), and one every
10297 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
10298 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
10300 o Code simplifications and refactoring:
10301 - Take a first step towards making or.h smaller by splitting out
10302 function definitions for all source files in src/or/. Leave
10303 structures and defines in or.h for now.
10304 - Remove a bunch of unused function declarations as well as a block of
10305 #if 0'd code from the unit tests. Closes bug 1824.
10306 - New unit tests for exit-port history statistics; refactored exit
10307 statistics code to be more easily tested.
10308 - Remove the old debian/ directory from the main Tor distribution.
10309 The official Tor-for-debian git repository lives at the URL
10310 https://git.torproject.org/debian/tor.git
10313 Changes in version 0.2.2.14-alpha - 2010-07-12
10314 Tor 0.2.2.14-alpha greatly improves client-side handling of
10315 circuit build timeouts, which are used to estimate speed and improve
10316 performance. We also move to a much better GeoIP database, port Tor to
10317 Windows CE, introduce new compile flags that improve code security,
10318 add an eighth v3 directory authority, and address a lot of more
10322 - Tor directory authorities no longer crash when started with a
10323 cached-microdesc-consensus file in their data directory. Bugfix
10324 on 0.2.2.6-alpha; fixes bug 1532.
10325 - Treat an unset $HOME like an empty $HOME rather than triggering an
10326 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
10327 - Ignore negative and large circuit build timeout values that can
10328 happen during a suspend or hibernate. These values caused various
10329 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
10330 - Alter calculation of Pareto distribution parameter 'Xm' for
10331 Circuit Build Timeout learning to use the weighted average of the
10332 top N=3 modes (because we have three entry guards). Considering
10333 multiple modes should improve the timeout calculation in some cases,
10334 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
10336 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
10337 right censored distribution model. This approach improves over the
10338 synthetic timeout generation approach that was producing insanely
10339 high timeout values. Now we calculate build timeouts using truncated
10340 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
10341 - Do not close circuits that are under construction when they reach
10342 the circuit build timeout. Instead, leave them building (but do not
10343 use them) for up until the time corresponding to the 95th percentile
10344 on the Pareto CDF or 60 seconds, whichever is greater. This is done
10345 to provide better data for the new Pareto model. This percentile
10346 can be controlled by the consensus.
10349 - Move to the June 2010 Maxmind GeoLite country db (rather than the
10350 June 2009 ip-to-country GeoIP db) for our statistics that count
10351 how many users relays are seeing from each country. Now we have
10352 more accurate data for many African countries.
10353 - Port Tor to build and run correctly on Windows CE systems, using
10354 the wcecompat library. Contributed by Valerio Lupi.
10355 - New "--enable-gcc-hardening" ./configure flag (off by default)
10356 to turn on gcc compile time hardening options. It ensures
10357 that signed ints have defined behavior (-fwrapv), enables
10358 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
10359 with canaries (-fstack-protector-all), turns on ASLR protection if
10360 supported by the kernel (-fPIE, -pie), and adds additional security
10361 related warnings. Verified to work on Mac OS X and Debian Lenny.
10362 - New "--enable-linker-hardening" ./configure flag (off by default)
10363 to turn on ELF specific hardening features (relro, now). This does
10364 not work with Mac OS X or any other non-ELF binary format.
10366 o New directory authorities:
10367 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10371 - New config option "WarnUnsafeSocks 0" disables the warning that
10372 occurs whenever Tor receives a socks handshake using a version of
10373 the socks protocol that can only provide an IP address (rather
10374 than a hostname). Setups that do DNS locally over Tor are fine,
10375 and we shouldn't spam the logs in that case.
10376 - Convert the HACKING file to asciidoc, and add a few new sections
10377 to it, explaining how we use Git, how we make changelogs, and
10378 what should go in a patch.
10379 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
10380 event, to give information on the current rate of circuit timeouts
10381 over our stored history.
10382 - Add ability to disable circuit build time learning via consensus
10383 parameter and via a LearnCircuitBuildTimeout config option. Also
10384 automatically disable circuit build time calculation if we are
10385 either a AuthoritativeDirectory, or if we fail to write our state
10386 file. Fixes bug 1296.
10387 - More gracefully handle corrupt state files, removing asserts
10388 in favor of saving a backup and resetting state.
10389 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
10393 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
10395 - When a2x fails, mention that the user could disable manpages instead
10396 of trying to fix their asciidoc installation.
10397 - Where available, use Libevent 2.0's periodic timers so that our
10398 once-per-second cleanup code gets called even more closely to
10399 once per second than it would otherwise. Fixes bug 943.
10400 - If you run a bridge that listens on multiple IP addresses, and
10401 some user configures a bridge address that uses a different IP
10402 address than your bridge writes in its router descriptor, and the
10403 user doesn't specify an identity key, their Tor would discard the
10404 descriptor because "it isn't one of our configured bridges", and
10405 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
10406 Bugfix on 0.2.0.3-alpha.
10407 - If OpenSSL fails to make a duplicate of a private or public key, log
10408 an error message and try to exit cleanly. May help with debugging
10409 if bug 1209 ever remanifests.
10410 - Save a couple bytes in memory allocation every time we escape
10411 certain characters in a string. Patch from Florian Zumbiehl.
10412 - Make it explicit that we don't cannibalize one-hop circuits. This
10413 happens in the wild, but doesn't turn out to be a problem because
10414 we fortunately don't use those circuits. Many thanks to outofwords
10415 for the initial analysis and to swissknife who confirmed that
10416 two-hop circuits are actually created.
10417 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
10418 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
10419 - Eliminate a case where a circuit build time warning was displayed
10420 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
10423 Changes in version 0.2.1.26 - 2010-05-02
10424 Tor 0.2.1.26 addresses the recent connection and memory overload
10425 problems we've been seeing on relays, especially relays with their
10426 DirPort open. If your relay has been crashing, or you turned it off
10427 because it used too many resources, give this release a try.
10429 This release also fixes yet another instance of broken OpenSSL libraries
10430 that was causing some relays to drop out of the consensus.
10433 - Teach relays to defend themselves from connection overload. Relays
10434 now close idle circuits early if it looks like they were intended
10435 for directory fetches. Relays are also more aggressive about closing
10436 TLS connections that have no circuits on them. Such circuits are
10437 unlikely to be re-used, and tens of thousands of them were piling
10438 up at the fast relays, causing the relays to run out of sockets
10439 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10440 their directory fetches over TLS).
10441 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10442 that claim to be earlier than 0.9.8m, but which have in reality
10443 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10444 behavior. Possible fix for some cases of bug 1346.
10445 - Directory mirrors were fetching relay descriptors only from v2
10446 directory authorities, rather than v3 authorities like they should.
10447 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10448 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10451 - Finally get rid of the deprecated and now harmful notion of "clique
10452 mode", where directory authorities maintain TLS connections to
10456 - In the util/threads test, no longer free the test_mutex before all
10457 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10458 - The master thread could starve the worker threads quite badly on
10459 certain systems, causing them to run only partially in the allowed
10460 window. This resulted in test failures. Now the master thread sleeps
10461 occasionally for a few microseconds while the two worker-threads
10462 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10465 Changes in version 0.2.2.13-alpha - 2010-04-24
10466 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
10467 problems we've been seeing on relays, especially relays with their
10468 DirPort open. If your relay has been crashing, or you turned it off
10469 because it used too many resources, give this release a try.
10472 - Teach relays to defend themselves from connection overload. Relays
10473 now close idle circuits early if it looks like they were intended
10474 for directory fetches. Relays are also more aggressive about closing
10475 TLS connections that have no circuits on them. Such circuits are
10476 unlikely to be re-used, and tens of thousands of them were piling
10477 up at the fast relays, causing the relays to run out of sockets
10478 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10479 their directory fetches over TLS).
10482 - Finally get rid of the deprecated and now harmful notion of "clique
10483 mode", where directory authorities maintain TLS connections to
10485 - Directory authorities now do an immediate reachability check as soon
10486 as they hear about a new relay. This change should slightly reduce
10487 the time between setting up a relay and getting listed as running
10488 in the consensus. It should also improve the time between setting
10489 up a bridge and seeing use by bridge users.
10490 - Directory authorities no longer launch a TLS connection to every
10491 relay as they startup. Now that we have 2k+ descriptors cached,
10492 the resulting network hiccup is becoming a burden. Besides,
10493 authorities already avoid voting about Running for the first half
10494 hour of their uptime.
10497 Changes in version 0.2.2.12-alpha - 2010-04-20
10498 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
10499 handle and vote on descriptors. It was causing relays to drop out of
10503 - Many relays have been falling out of the consensus lately because
10504 not enough authorities know about their descriptor for them to get
10505 a majority of votes. When we deprecated the v2 directory protocol,
10506 we got rid of the only way that v3 authorities can hear from each
10507 other about other descriptors. Now authorities examine every v3
10508 vote for new descriptors, and fetch them from that authority. Bugfix
10510 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
10511 and a warning in or.h related to bandwidth_weight_rule_t that
10512 prevented clean compile on OS X. Fixes bug 1363; bugfix on
10514 - Fix a segfault on relays when DirReqStatistics is enabled
10515 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
10519 - Demote a confusing TLS warning that relay operators might get when
10520 someone tries to talk to their OrPort. It is neither the operator's
10521 fault nor can they do anything about it. Fixes bug 1364; bugfix
10525 Changes in version 0.2.2.11-alpha - 2010-04-15
10526 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
10527 libraries that was causing some relays to drop out of the consensus.
10530 - Directory mirrors were fetching relay descriptors only from v2
10531 directory authorities, rather than v3 authorities like they should.
10532 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10533 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10534 - Fix a parsing error that made every possible value of
10535 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
10536 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
10537 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
10538 about the option without breaking older ones.
10539 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10540 that claim to be earlier than 0.9.8m, but which have in reality
10541 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10542 behavior. Possible fix for some cases of bug 1346.
10545 - Experiment with a more aggressive approach to preventing clients
10546 from making one-hop exit streams. Exit relays who want to try it
10547 out can set "RefuseUnknownExits 1" in their torrc, and then look
10548 for "Attempt by %s to open a stream" log messages. Let us know
10550 - Add support for statically linking zlib by specifying
10551 --enable-static-zlib, to go with our support for statically linking
10552 openssl and libevent. Resolves bug 1358.
10555 - Fix a segfault that happens whenever a Tor client that is using
10556 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
10558 - When we cleaned up the contrib/tor-exit-notice.html file, we left
10559 out the first line. Fixes bug 1295.
10560 - When building the manpage from a tarball, we required asciidoc, but
10561 the asciidoc -> roff/html conversion was already done for the
10562 tarball. Make 'make' complain only when we need asciidoc (either
10563 because we're compiling directly from git, or because we altered
10564 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
10565 - When none of the directory authorities vote on any params, Tor
10566 segfaulted when trying to make the consensus from the votes. We
10567 didn't trigger the bug in practice, because authorities do include
10568 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
10571 - In the util/threads test, no longer free the test_mutex before all
10572 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10573 - The master thread could starve the worker threads quite badly on
10574 certain systems, causing them to run only partially in the allowed
10575 window. This resulted in test failures. Now the master thread sleeps
10576 occasionally for a few microseconds while the two worker-threads
10577 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10580 Changes in version 0.2.2.10-alpha - 2010-03-07
10581 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
10582 could prevent relays from guessing their IP address correctly. It also
10583 starts the groundwork for another client-side performance boost, since
10584 currently we're not making efficient use of relays that have both the
10585 Guard flag and the Exit flag.
10588 - Fix a regression from our patch for bug 1244 that caused relays
10589 to guess their IP address incorrectly if they didn't set Address
10590 in their torrc and/or their address fails to resolve. Bugfix on
10591 0.2.2.9-alpha; fixes bug 1269.
10593 o Major features (performance):
10594 - Directory authorities now compute consensus weightings that instruct
10595 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
10596 and no flag. Clients that use these weightings will distribute
10597 network load more evenly across these different relay types. The
10598 weightings are in the consensus so we can change them globally in
10599 the future. Extra thanks to "outofwords" for finding some nasty
10600 security bugs in the first implementation of this feature.
10602 o Minor features (performance):
10603 - Always perform router selections using weighted relay bandwidth,
10604 even if we don't need a high capacity circuit at the time. Non-fast
10605 circuits now only differ from fast ones in that they can use relays
10606 not marked with the Fast flag. This "feature" could turn out to
10607 be a horrible bug; we should investigate more before it goes into
10611 - Allow disabling building of the manpages. Skipping the manpage
10612 speeds up the build considerably.
10614 o Minor bugfixes (on 0.2.2.x):
10615 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
10616 Bugfix on 0.2.2.9-alpha.
10617 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
10618 config option. Bugfix on 0.2.2.7-alpha.
10619 - Ship the asciidoc-helper file in the tarball, so that people can
10620 build from source if they want to, and touching the .1.txt files
10621 doesn't break the build. Bugfix on 0.2.2.9-alpha.
10623 o Minor bugfixes (on 0.2.1.x or earlier):
10624 - Fix a dereference-then-NULL-check sequence when publishing
10625 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10627 - Fix another dereference-then-NULL-check sequence. Bugfix on
10628 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10629 - Make sure we treat potentially not NUL-terminated strings correctly.
10630 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10632 o Code simplifications and refactoring:
10633 - Fix some urls in the exit notice file and make it XHTML1.1 strict
10634 compliant. Based on a patch from Christian Kujau.
10635 - Don't use sed in asciidoc-helper anymore.
10636 - Make the build process fail if asciidoc cannot be found and
10637 building with asciidoc isn't disabled.
10640 Changes in version 0.2.2.9-alpha - 2010-02-22
10641 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
10642 location of a directory authority, and cleans up a bunch of small bugs.
10644 o Directory authority changes:
10645 - Change IP address for dannenberg (v3 directory authority), and
10646 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10647 service directory authority) from the list.
10650 - Make Tor work again on the latest OS X: when deciding whether to
10651 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10652 version at run-time, not compile time. We need to do this because
10653 Apple doesn't update its dev-tools headers when it updates its
10654 libraries in a security patch.
10655 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10656 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10657 a memory leak when requesting a hidden service descriptor we've
10658 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10660 - Authorities could be tricked into giving out the Exit flag to relays
10661 that didn't allow exiting to any ports. This bug could screw
10662 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
10663 1238. Bug discovered by Martin Kowalczyk.
10664 - When freeing a session key, zero it out completely. We only zeroed
10665 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10666 patched by ekir. Fixes bug 1254.
10669 - Fix static compilation by listing the openssl libraries in the right
10670 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
10671 - Resume handling .exit hostnames in a special way: originally we
10672 stripped the .exit part and used the requested exit relay. In
10673 0.2.2.1-alpha we stopped treating them in any special way, meaning
10674 if you use a .exit address then Tor will pass it on to the exit
10675 relay. Now we reject the .exit stream outright, since that behavior
10676 might be more expected by the user. Found and diagnosed by Scott
10677 Bennett and Downie on or-talk.
10678 - Don't spam the controller with events when we have no file
10679 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
10680 for log messages was already solved from bug 748.)
10681 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
10683 - Make the DNSPort option work with libevent 2.x. Don't alter the
10684 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
10685 - Emit a GUARD DROPPED controller event for a case we missed.
10686 - Make more fields in the controller protocol case-insensitive, since
10687 control-spec.txt said they were.
10688 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10689 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10690 - Fix a spec conformance issue: the network-status-version token
10691 must be the first token in a v3 consensus or vote. Discovered by
10692 parakeep. Bugfix on 0.2.0.3-alpha.
10694 o Code simplifications and refactoring:
10695 - Generate our manpage and HTML documentation using Asciidoc. This
10696 change should make it easier to maintain the documentation, and
10697 produce nicer HTML.
10698 - Remove the --enable-iphone option. According to reports from Marco
10699 Bonetti, Tor builds fine without any special tweaking on recent
10700 iPhone SDK versions.
10701 - Removed some unnecessary files from the source distribution. The
10702 AUTHORS file has now been merged into the people page on the
10703 website. The roadmaps and design doc can now be found in the
10704 projects directory in svn.
10705 - Enabled various circuit build timeout constants to be controlled
10706 by consensus parameters. Also set better defaults for these
10707 parameters based on experimentation on broadband and simulated
10708 high latency links.
10711 - The 'EXTENDCIRCUIT' control port command can now be used with
10712 a circ id of 0 and no path. This feature will cause Tor to build
10713 a new 'fast' general purpose circuit using its own path selection
10715 - Added a BUILDTIMEOUT_SET controller event to describe changes
10716 to the circuit build timeout.
10717 - Future-proof the controller protocol a bit by ignoring keyword
10718 arguments we do not recognize.
10719 - Expand homedirs passed to tor-checkkey. This should silence a
10720 coverity complaint about passing a user-supplied string into
10721 open() without checking it.
10724 Changes in version 0.2.1.25 - 2010-03-16
10725 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
10726 prevent relays from guessing their IP address correctly. It also fixes
10727 several minor potential security bugs.
10730 - Fix a regression from our patch for bug 1244 that caused relays
10731 to guess their IP address incorrectly if they didn't set Address
10732 in their torrc and/or their address fails to resolve. Bugfix on
10733 0.2.1.23; fixes bug 1269.
10734 - When freeing a session key, zero it out completely. We only zeroed
10735 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10736 patched by ekir. Fixes bug 1254.
10739 - Fix a dereference-then-NULL-check sequence when publishing
10740 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10742 - Fix another dereference-then-NULL-check sequence. Bugfix on
10743 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10744 - Make sure we treat potentially not NUL-terminated strings correctly.
10745 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10749 Changes in version 0.2.1.24 - 2010-02-21
10750 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
10754 - Work correctly out-of-the-box with even more vendor-patched versions
10755 of OpenSSL. In particular, make it so Debian and OS X don't need
10756 customized patches to run/build.
10759 Changes in version 0.2.1.23 - 2010-02-13
10760 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
10761 again on the latest OS X, and updates the location of a directory
10764 o Major bugfixes (performance):
10765 - We were selecting our guards uniformly at random, and then weighting
10766 which of our guards we'd use uniformly at random. This imbalance
10767 meant that Tor clients were severely limited on throughput (and
10768 probably latency too) by the first hop in their circuit. Now we
10769 select guards weighted by currently advertised bandwidth. We also
10770 automatically discard guards picked using the old algorithm. Fixes
10771 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10774 - Make Tor work again on the latest OS X: when deciding whether to
10775 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10776 version at run-time, not compile time. We need to do this because
10777 Apple doesn't update its dev-tools headers when it updates its
10778 libraries in a security patch.
10779 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10780 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10781 a memory leak when requesting a hidden service descriptor we've
10782 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10785 o Directory authority changes:
10786 - Change IP address for dannenberg (v3 directory authority), and
10787 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10788 service directory authority) from the list.
10791 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10792 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10795 - Avoid a mad rush at the beginning of each month when each client
10796 rotates half of its guards. Instead we spread the rotation out
10797 throughout the month, but we still avoid leaving a precise timestamp
10798 in the state file about when we first picked the guard. Improves
10799 over the behavior introduced in 0.1.2.17.
10802 Changes in version 0.2.2.8-alpha - 2010-01-26
10803 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
10804 causing bridge relays to disappear. If you're running a bridge,
10808 - Fix a memory corruption bug on bridges that occured during the
10809 inclusion of stats data in extra-info descriptors. Also fix the
10810 interface for geoip_get_bridge_stats* to prevent similar bugs in
10811 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
10812 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
10815 - Ignore OutboundBindAddress when connecting to localhost.
10816 Connections to localhost need to come _from_ localhost, or else
10817 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10821 Changes in version 0.2.2.7-alpha - 2010-01-19
10822 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
10823 as laying the groundwork for further relay-side performance fixes. It
10824 also starts cleaning up client behavior with respect to the EntryNodes,
10825 ExitNodes, and StrictNodes config options.
10827 This release also rotates two directory authority keys, due to a
10828 security breach of some of the Torproject servers.
10830 o Directory authority changes:
10831 - Rotate keys (both v3 identity and relay identity) for moria1
10834 o Major features (performance):
10835 - We were selecting our guards uniformly at random, and then weighting
10836 which of our guards we'd use uniformly at random. This imbalance
10837 meant that Tor clients were severely limited on throughput (and
10838 probably latency too) by the first hop in their circuit. Now we
10839 select guards weighted by currently advertised bandwidth. We also
10840 automatically discard guards picked using the old algorithm. Fixes
10841 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10842 - When choosing which cells to relay first, relays can now favor
10843 circuits that have been quiet recently, to provide lower latency
10844 for low-volume circuits. By default, relays enable or disable this
10845 feature based on a setting in the consensus. You can override
10846 this default by using the new "CircuitPriorityHalflife" config
10847 option. Design and code by Ian Goldberg, Can Tang, and Chris
10849 - Add separate per-conn write limiting to go with the per-conn read
10850 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
10851 but never per-conn write limits.
10852 - New consensus params "bwconnrate" and "bwconnburst" to let us
10853 rate-limit client connections as they enter the network. It's
10854 controlled in the consensus so we can turn it on and off for
10855 experiments. It's starting out off. Based on proposal 163.
10857 o Major features (relay selection options):
10858 - Switch to a StrictNodes config option, rather than the previous
10859 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
10860 "StrictExcludeNodes" option.
10861 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
10862 change during a config reload, mark and discard all our origin
10863 circuits. This fix should address edge cases where we change the
10864 config options and but then choose a circuit that we created before
10866 - If EntryNodes or ExitNodes are set, be more willing to use an
10867 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
10869 - Make EntryNodes config option much more aggressive even when
10870 StrictNodes is not set. Before it would prepend your requested
10871 entrynodes to your list of guard nodes, but feel free to use others
10872 after that. Now it chooses only from your EntryNodes if any of
10873 those are available, and only falls back to others if a) they're
10874 all down and b) StrictNodes is not set.
10875 - Now we refresh your entry guards from EntryNodes at each consensus
10876 fetch -- rather than just at startup and then they slowly rot as
10877 the network changes.
10880 - Stop bridge directory authorities from answering dbg-stability.txt
10881 directory queries, which would let people fetch a list of all
10882 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10885 - Log a notice when we get a new control connection. Now it's easier
10886 for security-conscious users to recognize when a local application
10887 is knocking on their controller door. Suggested by bug 1196.
10888 - New config option "CircuitStreamTimeout" to override our internal
10889 timeout schedule for how many seconds until we detach a stream from
10890 a circuit and try a new circuit. If your network is particularly
10891 slow, you might want to set this to a number like 60.
10892 - New controller command "getinfo config-text". It returns the
10893 contents that Tor would write if you send it a SAVECONF command,
10894 so the controller can write the file to disk itself.
10895 - New options for SafeLogging to allow scrubbing only log messages
10896 generated while acting as a relay.
10897 - Ship the bridges spec file in the tarball too.
10898 - Avoid a mad rush at the beginning of each month when each client
10899 rotates half of its guards. Instead we spread the rotation out
10900 throughout the month, but we still avoid leaving a precise timestamp
10901 in the state file about when we first picked the guard. Improves
10902 over the behavior introduced in 0.1.2.17.
10904 o Minor bugfixes (compiling):
10905 - Fix compilation on OS X 10.3, which has a stub mlockall() but
10906 hides it. Bugfix on 0.2.2.6-alpha.
10907 - Fix compilation on Solaris by removing support for the
10908 DisableAllSwap config option. Solaris doesn't have an rlimit for
10909 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
10912 o Minor bugfixes (crashes):
10913 - Do not segfault when writing buffer stats when we haven't observed
10914 a single circuit to report about. Found by Fabian Lanze. Bugfix on
10916 - If we're in the pathological case where there's no exit bandwidth
10917 but there is non-exit bandwidth, or no guard bandwidth but there
10918 is non-guard bandwidth, don't crash during path selection. Bugfix
10920 - Fix an impossible-to-actually-trigger buffer overflow in relay
10921 descriptor generation. Bugfix on 0.1.0.15.
10923 o Minor bugfixes (privacy):
10924 - Fix an instance where a Tor directory mirror might accidentally
10925 log the IP address of a misbehaving Tor client. Bugfix on
10927 - Don't list Windows capabilities in relay descriptors. We never made
10928 use of them, and maybe it's a bad idea to publish them. Bugfix
10931 o Minor bugfixes (other):
10932 - Resolve an edge case in path weighting that could make us misweight
10933 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
10934 - Fix statistics on client numbers by country as seen by bridges that
10935 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
10936 intervals instead of variable 12-to-48-hour intervals.
10937 - After we free an internal connection structure, overwrite it
10938 with a different memory value than we use for overwriting a freed
10939 internal circuit structure. Should help with debugging. Suggested
10941 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
10944 o Removed features:
10945 - Remove the HSAuthorityRecordStats option that version 0 hidden
10946 service authorities could have used to track statistics of overall
10947 hidden service usage.
10950 Changes in version 0.2.1.22 - 2010-01-19
10951 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
10952 authorities -- it would tell you its whole history of bridge descriptors
10953 if you make the right directory request. This stable update also
10954 rotates two of the seven v3 directory authority keys and locations.
10956 o Directory authority changes:
10957 - Rotate keys (both v3 identity and relay identity) for moria1
10961 - Stop bridge directory authorities from answering dbg-stability.txt
10962 directory queries, which would let people fetch a list of all
10963 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10966 Changes in version 0.2.1.21 - 2009-12-21
10967 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
10968 library. If you use Tor on Linux / Unix and you're getting SSL
10969 renegotiation errors, upgrading should help. We also recommend an
10970 upgrade if you're an exit relay.
10973 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10974 handshake from working unless we explicitly tell OpenSSL that we
10975 are using SSL renegotiation safely. We are, of course, but OpenSSL
10976 0.9.8l won't work unless we say we are.
10977 - Avoid crashing if the client is trying to upload many bytes and the
10978 circuit gets torn down at the same time, or if the flip side
10979 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
10982 - Do not refuse to learn about authority certs and v2 networkstatus
10983 documents that are older than the latest consensus. This bug might
10984 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10985 Spotted and fixed by xmux.
10986 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
10987 trigger platform-specific option misparsing case found by Coverity
10989 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
10990 trigger assert. Fixes bug 1173.
10993 Changes in version 0.2.2.6-alpha - 2009-11-19
10994 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
10995 support for the new lower-footprint "microdescriptor" directory design,
10996 future-proofing our consensus format against new hash functions or
10997 other changes, and an Android port. It also makes Tor compatible with
10998 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
11001 - Directory authorities can now create, vote on, and serve multiple
11002 parallel formats of directory data as part of their voting process.
11003 Partially implements Proposal 162: "Publish the consensus in
11005 - Directory authorities can now agree on and publish small summaries
11006 of router information that clients can use in place of regular
11007 server descriptors. This transition will eventually allow clients
11008 to use far less bandwidth for downloading information about the
11009 network. Begins the implementation of Proposal 158: "Clients
11010 download consensus + microdescriptors".
11011 - The directory voting system is now extensible to use multiple hash
11012 algorithms for signatures and resource selection. Newer formats
11013 are signed with SHA256, with a possibility for moving to a better
11014 hash algorithm in the future.
11015 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
11016 current and future memory pages via mlockall(). On supported
11017 platforms (modern Linux and probably BSD but not Windows or OS X),
11018 this should effectively disable any and all attempts to page out
11019 memory. This option requires that you start your Tor as root --
11020 if you use DisableAllSwap, please consider using the User option
11021 to properly reduce the privileges of your Tor.
11022 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
11023 to help Tor build correctly for Android phones.
11026 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11027 handshake from working unless we explicitly tell OpenSSL that we
11028 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
11029 won't work unless we say we are.
11032 - Fix a crash bug when trying to initialize the evdns module in
11033 Libevent 2. Bugfix on 0.2.1.16-rc.
11034 - Stop logging at severity 'warn' when some other Tor client tries
11035 to establish a circuit with us using weak DH keys. It's a protocol
11036 violation, but that doesn't mean ordinary users need to hear about
11037 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
11038 - Do not refuse to learn about authority certs and v2 networkstatus
11039 documents that are older than the latest consensus. This bug might
11040 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11041 Spotted and fixed by xmux.
11042 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
11043 - If all authorities restart at once right before a consensus vote,
11044 nobody will vote about "Running", and clients will get a consensus
11045 with no usable relays. Instead, authorities refuse to build a
11046 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
11047 - If your relay can't keep up with the number of incoming create
11048 cells, it would log one warning per failure into your logs. Limit
11049 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
11050 - Bridges now use "reject *:*" as their default exit policy. Bugfix
11051 on 0.2.0.3-alpha; fixes bug 1113.
11052 - Fix a memory leak on directory authorities during voting that was
11053 introduced in 0.2.2.1-alpha. Found via valgrind.
11056 Changes in version 0.2.1.20 - 2009-10-15
11057 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
11058 services at once, prepares for more performance improvements, and
11059 fixes a bunch of smaller bugs.
11061 The Windows and OS X bundles also include a more recent Vidalia,
11062 and switch from Privoxy to Polipo.
11064 The OS X installers are now drag and drop. It's best to un-install
11065 Tor/Vidalia and then install this new bundle, rather than upgrade. If
11066 you want to upgrade, you'll need to update the paths for Tor and Polipo
11067 in the Vidalia Settings window.
11070 - Send circuit or stream sendme cells when our window has decreased
11071 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11072 by Karsten when testing the "reduce circuit window" performance
11073 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11074 before the release of Tor 0.0.0. This is the new winner of the
11076 - Fix a remotely triggerable memory leak when a consensus document
11077 contains more than one signature from the same voter. Bugfix on
11079 - Avoid segfault in rare cases when finishing an introduction circuit
11080 as a client and finding out that we don't have an introduction key
11081 for it. Fixes bug 1073. Reported by Aaron Swartz.
11084 - Tor now reads the "circwindow" parameter out of the consensus,
11085 and uses that value for its circuit package window rather than the
11086 default of 1000 cells. Begins the implementation of proposal 168.
11088 o New directory authorities:
11089 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11091 - Move moria1 and tonga to alternate IP addresses.
11094 - Fix a signed/unsigned compile warning in 0.2.1.19.
11095 - Fix possible segmentation fault on directory authorities. Bugfix on
11097 - Fix an extremely rare infinite recursion bug that could occur if
11098 we tried to log a message after shutting down the log subsystem.
11099 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11100 - Fix an obscure bug where hidden services on 64-bit big-endian
11101 systems might mis-read the timestamp in v3 introduce cells, and
11102 refuse to connect back to the client. Discovered by "rotor".
11103 Bugfix on 0.2.1.6-alpha.
11104 - We were triggering a CLOCK_SKEW controller status event whenever
11105 we connect via the v2 connection protocol to any relay that has
11106 a wrong clock. Instead, we should only inform the controller when
11107 it's a trusted authority that claims our clock is wrong. Bugfix
11108 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11109 - We were telling the controller about CHECKING_REACHABILITY and
11110 REACHABILITY_FAILED status events whenever we launch a testing
11111 circuit or notice that one has failed. Instead, only tell the
11112 controller when we want to inform the user of overall success or
11113 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11115 - Don't warn when we're using a circuit that ends with a node
11116 excluded in ExcludeExitNodes, but the circuit is not used to access
11117 the outside world. This should help fix bug 1090. Bugfix on
11119 - Work around a small memory leak in some versions of OpenSSL that
11120 stopped the memory used by the hostname TLS extension from being
11124 - Add a "getinfo status/accepted-server-descriptor" controller
11125 command, which is the recommended way for controllers to learn
11126 whether our server descriptor has been successfully received by at
11127 least on directory authority. Un-recommend good-server-descriptor
11128 getinfo and status events until we have a better design for them.
11131 Changes in version 0.2.2.5-alpha - 2009-10-11
11132 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
11135 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
11137 o Directory authorities:
11138 - Temporarily (just for this release) move dizum to an alternate
11142 Changes in version 0.2.2.4-alpha - 2009-10-10
11143 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
11144 introduces a new unit test framework, shifts directry authority
11145 addresses around to reduce the impact from recent blocking events,
11146 and fixes a few smaller bugs.
11149 - Fix several more asserts in the circuit_build_times code, for
11150 example one that causes Tor to fail to start once we have
11151 accumulated 5000 build times in the state file. Bugfixes on
11152 0.2.2.2-alpha; fixes bug 1108.
11154 o New directory authorities:
11155 - Move moria1 and Tonga to alternate IP addresses.
11158 - Log SSL state transitions at debug level during handshake, and
11159 include SSL states in error messages. This may help debug future
11160 SSL handshake issues.
11161 - Add a new "Handshake" log domain for activities that happen
11162 during the TLS handshake.
11163 - Revert to the "June 3 2009" ip-to-country file. The September one
11164 seems to have removed most US IP addresses.
11165 - Directory authorities now reject Tor relays with versions less than
11166 0.1.2.14. This step cuts out four relays from the current network,
11167 none of which are very big.
11170 - Fix a couple of smaller issues with gathering statistics. Bugfixes
11172 - Fix two memory leaks in the error case of
11173 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
11174 - Don't count one-hop circuits when we're estimating how long it
11175 takes circuits to build on average. Otherwise we'll set our circuit
11176 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
11177 - Directory authorities no longer change their opinion of, or vote on,
11178 whether a router is Running, unless they have themselves been
11179 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
11182 o Code simplifications and refactoring:
11183 - Revise our unit tests to use the "tinytest" framework, so we
11184 can run tests in their own processes, have smarter setup/teardown
11185 code, and so on. The unit test code has moved to its own
11186 subdirectory, and has been split into multiple modules.
11189 Changes in version 0.2.2.3-alpha - 2009-09-23
11190 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
11193 - Fix an overzealous assert in our new circuit build timeout code.
11194 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
11197 - If the networkstatus consensus tells us that we should use a
11198 negative circuit package window, ignore it. Otherwise we'll
11199 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
11202 Changes in version 0.2.2.2-alpha - 2009-09-21
11203 Tor 0.2.2.2-alpha introduces our latest performance improvement for
11204 clients: Tor tracks the average time it takes to build a circuit, and
11205 avoids using circuits that take too long to build. For fast connections,
11206 this feature can cut your expected latency in half. For slow or flaky
11207 connections, it could ruin your Tor experience. Let us know if it does!
11210 - Tor now tracks how long it takes to build client-side circuits
11211 over time, and adapts its timeout to local network performance.
11212 Since a circuit that takes a long time to build will also provide
11213 bad performance, we get significant latency improvements by
11214 discarding the slowest 20% of circuits. Specifically, Tor creates
11215 circuits more aggressively than usual until it has enough data
11216 points for a good timeout estimate. Implements proposal 151.
11217 We are especially looking for reports (good and bad) from users with
11218 both EDGE and broadband connections that can move from broadband
11219 to EDGE and find out if the build-time data in the .tor/state gets
11220 reset without loss of Tor usability. You should also see a notice
11221 log message telling you that Tor has reset its timeout.
11222 - Directory authorities can now vote on arbitary integer values as
11223 part of the consensus process. This is designed to help set
11224 network-wide parameters. Implements proposal 167.
11225 - Tor now reads the "circwindow" parameter out of the consensus,
11226 and uses that value for its circuit package window rather than the
11227 default of 1000 cells. Begins the implementation of proposal 168.
11230 - Fix a remotely triggerable memory leak when a consensus document
11231 contains more than one signature from the same voter. Bugfix on
11235 - Fix an extremely rare infinite recursion bug that could occur if
11236 we tried to log a message after shutting down the log subsystem.
11237 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11238 - Fix parsing for memory or time units given without a space between
11239 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
11240 - A networkstatus vote must contain exactly one signature. Spec
11241 conformance issue. Bugfix on 0.2.0.3-alpha.
11242 - Fix an obscure bug where hidden services on 64-bit big-endian
11243 systems might mis-read the timestamp in v3 introduce cells, and
11244 refuse to connect back to the client. Discovered by "rotor".
11245 Bugfix on 0.2.1.6-alpha.
11246 - We were triggering a CLOCK_SKEW controller status event whenever
11247 we connect via the v2 connection protocol to any relay that has
11248 a wrong clock. Instead, we should only inform the controller when
11249 it's a trusted authority that claims our clock is wrong. Bugfix
11250 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11251 - We were telling the controller about CHECKING_REACHABILITY and
11252 REACHABILITY_FAILED status events whenever we launch a testing
11253 circuit or notice that one has failed. Instead, only tell the
11254 controller when we want to inform the user of overall success or
11255 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11257 - Don't warn when we're using a circuit that ends with a node
11258 excluded in ExcludeExitNodes, but the circuit is not used to access
11259 the outside world. This should help fix bug 1090, but more problems
11260 remain. Bugfix on 0.2.1.6-alpha.
11261 - Work around a small memory leak in some versions of OpenSSL that
11262 stopped the memory used by the hostname TLS extension from being
11264 - Make our 'torify' script more portable; if we have only one of
11265 'torsocks' or 'tsocks' installed, don't complain to the user;
11266 and explain our warning about tsocks better.
11269 - Add a "getinfo status/accepted-server-descriptor" controller
11270 command, which is the recommended way for controllers to learn
11271 whether our server descriptor has been successfully received by at
11272 least on directory authority. Un-recommend good-server-descriptor
11273 getinfo and status events until we have a better design for them.
11274 - Update to the "September 4 2009" ip-to-country file.
11277 Changes in version 0.2.2.1-alpha - 2009-08-26
11278 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
11279 Tor clients to bootstrap on networks where only port 80 is reachable,
11280 makes it more straightforward to support hardware crypto accelerators,
11281 and starts the groundwork for gathering stats safely at relays.
11284 - Start the process of disabling ".exit" address notation, since it
11285 can be used for a variety of esoteric application-level attacks
11286 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
11289 o New directory authorities:
11290 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11294 - New AccelName and AccelDir options add support for dynamic OpenSSL
11295 hardware crypto acceleration engines.
11296 - Tor now supports tunneling all of its outgoing connections over
11297 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
11298 configuration options. Code by Christopher Davis.
11301 - Send circuit or stream sendme cells when our window has decreased
11302 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11303 by Karsten when testing the "reduce circuit window" performance
11304 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11305 before the release of Tor 0.0.0. This is the new winner of the
11308 o New options for gathering stats safely:
11309 - Directory mirrors that set "DirReqStatistics 1" write statistics
11310 about directory requests to disk every 24 hours. As compared to the
11311 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
11312 1) stats are written to disk exactly every 24 hours; 2) estimated
11313 shares of v2 and v3 requests are determined as mean values, not at
11314 the end of a measurement period; 3) unresolved requests are listed
11315 with country code '??'; 4) directories also measure download times.
11316 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
11317 number of exit streams and transferred bytes per port to disk every
11319 - Relays that set "CellStatistics 1" write statistics on how long
11320 cells spend in their circuit queues to disk every 24 hours.
11321 - Entry nodes that set "EntryStatistics 1" write statistics on the
11322 rough number and origins of connecting clients to disk every 24
11324 - Relays that write any of the above statistics to disk and set
11325 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
11326 their extra-info documents.
11329 - New --digests command-line switch to output the digests of the
11330 source files Tor was built with.
11331 - The "torify" script now uses torsocks where available.
11332 - The memarea code now uses a sentinel value at the end of each area
11333 to make sure nothing writes beyond the end of an area. This might
11334 help debug some conceivable causes of bug 930.
11335 - Time and memory units in the configuration file can now be set to
11336 fractional units. For example, "2.5 GB" is now a valid value for
11338 - Certain Tor clients (such as those behind check.torproject.org) may
11339 want to fetch the consensus in an extra early manner. To enable this
11340 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
11341 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
11342 as only certain clients who must have this information sooner should
11344 - Instead of adding the svn revision to the Tor version string, report
11345 the git commit (when we're building from a git checkout).
11348 - If any of the v3 certs we download are unparseable, we should
11349 actually notice the failure so we don't retry indefinitely. Bugfix
11350 on 0.2.0.x; reported by "rotator".
11351 - If the cached cert file is unparseable, warn but don't exit.
11352 - Fix possible segmentation fault on directory authorities. Bugfix on
11354 - When Tor fails to parse a descriptor of any kind, dump it to disk.
11355 Might help diagnosing bug 1051.
11357 o Deprecated and removed features:
11358 - The controller no longer accepts the old obsolete "addr-mappings/"
11359 or "unregistered-servers-" GETINFO values.
11360 - Hidden services no longer publish version 0 descriptors, and clients
11361 do not request or use version 0 descriptors. However, the old hidden
11362 service authorities still accept and serve version 0 descriptors
11363 when contacted by older hidden services/clients.
11364 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
11365 always on; using them is necessary for correct forward-compatible
11367 - Remove support for .noconnect style addresses. Nobody was using
11368 them, and they provided another avenue for detecting Tor users
11369 via application-level web tricks.
11371 o Packaging changes:
11372 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
11373 installer bundles. See
11374 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
11375 for details of what's new in Vidalia 0.2.3.
11376 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
11377 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
11378 configuration file, rather than the old Privoxy.
11379 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
11380 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
11381 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
11382 better compatibility with OS X 10.6, aka Snow Leopard.
11383 - OS X Vidalia Bundle: The multi-package installer is now replaced
11384 by a simple drag and drop to the /Applications folder. This change
11385 occurred with the upgrade to Vidalia 0.2.3.
11388 Changes in version 0.2.1.19 - 2009-07-28
11389 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
11390 services on Tor 0.2.1.3-alpha through 0.2.1.18.
11393 - Make accessing hidden services on 0.2.1.x work right again.
11394 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
11395 part of patch provided by "optimist".
11398 - When a relay/bridge is writing out its identity key fingerprint to
11399 the "fingerprint" file and to its logs, write it without spaces. Now
11400 it will look like the fingerprints in our bridges documentation,
11401 and confuse fewer users.
11404 - Relays no longer publish a new server descriptor if they change
11405 their MaxAdvertisedBandwidth config option but it doesn't end up
11406 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
11407 fixes bug 1026. Patch from Sebastian.
11408 - Avoid leaking memory every time we get a create cell but we have
11409 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
11410 fixes bug 1034. Reported by BarkerJr.
11413 Changes in version 0.2.1.18 - 2009-07-24
11414 Tor 0.2.1.18 lays the foundations for performance improvements,
11415 adds status events to help users diagnose bootstrap problems, adds
11416 optional authentication/authorization for hidden services, fixes a
11417 variety of potential anonymity problems, and includes a huge pile of
11418 other features and bug fixes.
11421 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
11424 Changes in version 0.2.1.17-rc - 2009-07-07
11425 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
11426 candidate for the 0.2.1.x series. It lays the groundwork for further
11427 client performance improvements, and also fixes a big bug with directory
11428 authorities that were causing them to assign Guard and Stable flags
11431 The Windows bundles also finally include the geoip database that we
11432 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
11433 should actually install Torbutton rather than giving you a cryptic
11434 failure message (oops).
11437 - Clients now use the bandwidth values in the consensus, rather than
11438 the bandwidth values in each relay descriptor. This approach opens
11439 the door to more accurate bandwidth estimates once the directory
11440 authorities start doing active measurements. Implements more of
11444 - When Tor clients restart after 1-5 days, they discard all their
11445 cached descriptors as too old, but they still use the cached
11446 consensus document. This approach is good for robustness, but
11447 bad for performance: since they don't know any bandwidths, they
11448 end up choosing at random rather than weighting their choice by
11449 speed. Fixed by the above feature of putting bandwidths in the
11450 consensus. Bugfix on 0.2.0.x.
11451 - Directory authorities were neglecting to mark relays down in their
11452 internal histories if the relays fall off the routerlist without
11453 ever being found unreachable. So there were relays in the histories
11454 that haven't been seen for eight months, and are listed as being
11455 up for eight months. This wreaked havoc on the "median wfu"
11456 and "median mtbf" calculations, in turn making Guard and Stable
11457 flags very wrong, hurting network performance. Fixes bugs 696 and
11458 969. Bugfix on 0.2.0.6-alpha.
11461 - Serve the DirPortFrontPage page even when we have been approaching
11462 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
11463 - The control port would close the connection before flushing long
11464 replies, such as the network consensus, if a QUIT command was issued
11465 before the reply had completed. Now, the control port flushes all
11466 pending replies before closing the connection. Also fixed a spurious
11467 warning when a QUIT command is issued after a malformed or rejected
11468 AUTHENTICATE command, but before the connection was closed. Patch
11469 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
11470 - When we can't find an intro key for a v2 hidden service descriptor,
11471 fall back to the v0 hidden service descriptor and log a bug message.
11472 Workaround for bug 1024.
11473 - Fix a log message that did not respect the SafeLogging option.
11477 - If we're a relay and we change our IP address, be more verbose
11478 about the reason that made us change. Should help track down
11479 further bugs for relays on dynamic IP addresses.
11482 Changes in version 0.2.0.35 - 2009-06-24
11484 - Avoid crashing in the presence of certain malformed descriptors.
11485 Found by lark, and by automated fuzzing.
11486 - Fix an edge case where a malicious exit relay could convince a
11487 controller that the client's DNS question resolves to an internal IP
11488 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11491 - Finally fix the bug where dynamic-IP relays disappear when their
11492 IP address changes: directory mirrors were mistakenly telling
11493 them their old address if they asked via begin_dir, so they
11494 never got an accurate answer about their new address, so they
11495 just vanished after a day. For belt-and-suspenders, relays that
11496 don't set Address in their config now avoid using begin_dir for
11497 all direct connections. Should fix bugs 827, 883, and 900.
11498 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11499 that would occur on some exit nodes when DNS failures and timeouts
11500 occurred in certain patterns. Fix for bug 957.
11503 - When starting with a cache over a few days old, do not leak
11504 memory for the obsolete router descriptors in it. Bugfix on
11505 0.2.0.33; fixes bug 672.
11506 - Hidden service clients didn't use a cached service descriptor that
11507 was older than 15 minutes, but wouldn't fetch a new one either,
11508 because there was already one in the cache. Now, fetch a v2
11509 descriptor unless the same descriptor was added to the cache within
11510 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11513 Changes in version 0.2.1.16-rc - 2009-06-20
11514 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
11515 a bunch of minor bugs.
11518 - Fix an edge case where a malicious exit relay could convince a
11519 controller that the client's DNS question resolves to an internal IP
11520 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11522 o Major performance improvements (on 0.2.0.x):
11523 - Disable and refactor some debugging checks that forced a linear scan
11524 over the whole server-side DNS cache. These accounted for over 50%
11525 of CPU time on a relatively busy exit node's gprof profile. Found
11527 - Disable some debugging checks that appeared in exit node profile
11531 - Update to the "June 3 2009" ip-to-country file.
11532 - Do not have tor-resolve automatically refuse all .onion addresses;
11533 if AutomapHostsOnResolve is set in your torrc, this will work fine.
11535 o Minor bugfixes (on 0.2.0.x):
11536 - Log correct error messages for DNS-related network errors on
11538 - Fix a race condition that could cause crashes or memory corruption
11539 when running as a server with a controller listening for log
11541 - Avoid crashing when we have a policy specified in a DirPolicy or
11542 SocksPolicy or ReachableAddresses option with ports set on it,
11543 and we re-load the policy. May fix bug 996.
11544 - Hidden service clients didn't use a cached service descriptor that
11545 was older than 15 minutes, but wouldn't fetch a new one either,
11546 because there was already one in the cache. Now, fetch a v2
11547 descriptor unless the same descriptor was added to the cache within
11548 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11550 o Minor bugfixes (on 0.2.1.x):
11551 - Don't warn users about low port and hibernation mix when they
11552 provide a *ListenAddress directive to fix that. Bugfix on
11554 - When switching back and forth between bridge mode, do not start
11555 gathering GeoIP data until two hours have passed.
11556 - Do not complain that the user has requested an excluded node as
11557 an exit when the node is not really an exit. This could happen
11558 because the circuit was for testing, or an introduction point.
11562 Changes in version 0.2.1.15-rc - 2009-05-25
11563 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
11564 series. It fixes a major bug on fast exit relays, as well as a variety
11565 of more minor bugs.
11567 o Major bugfixes (on 0.2.0.x):
11568 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11569 that would occur on some exit nodes when DNS failures and timeouts
11570 occurred in certain patterns. Fix for bug 957.
11572 o Minor bugfixes (on 0.2.0.x):
11573 - Actually return -1 in the error case for read_bandwidth_usage().
11574 Harmless bug, since we currently don't care about the return value
11575 anywhere. Bugfix on 0.2.0.9-alpha.
11576 - Provide a more useful log message if bug 977 (related to buffer
11577 freelists) ever reappears, and do not crash right away.
11578 - Fix an assertion failure on 64-bit platforms when we allocated
11579 memory right up to the end of a memarea, then realigned the memory
11580 one step beyond the end. Fixes a possible cause of bug 930.
11581 - Protect the count of open sockets with a mutex, so we can't
11582 corrupt it when two threads are closing or opening sockets at once.
11583 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
11584 - Don't allow a bridge to publish its router descriptor to a
11585 non-bridge directory authority. Fixes part of bug 932.
11586 - When we change to or from being a bridge, reset our counts of
11587 client usage by country. Fixes bug 932.
11588 - Fix a bug that made stream bandwidth get misreported to the
11590 - Stop using malloc_usable_size() to use more area than we had
11591 actually allocated: it was safe, but made valgrind really unhappy.
11592 - Fix a memory leak when v3 directory authorities load their keys
11593 and cert from disk. Bugfix on 0.2.0.1-alpha.
11595 o Minor bugfixes (on 0.2.1.x):
11596 - Fix use of freed memory when deciding to mark a non-addable
11597 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
11600 Changes in version 0.2.1.14-rc - 2009-04-12
11601 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
11602 series. It begins fixing some major performance problems, and also
11603 finally addresses the bug that was causing relays on dynamic IP
11604 addresses to fall out of the directory.
11607 - Clients replace entry guards that were chosen more than a few months
11608 ago. This change should significantly improve client performance,
11609 especially once more people upgrade, since relays that have been
11610 a guard for a long time are currently overloaded.
11612 o Major bugfixes (on 0.2.0):
11613 - Finally fix the bug where dynamic-IP relays disappear when their
11614 IP address changes: directory mirrors were mistakenly telling
11615 them their old address if they asked via begin_dir, so they
11616 never got an accurate answer about their new address, so they
11617 just vanished after a day. For belt-and-suspenders, relays that
11618 don't set Address in their config now avoid using begin_dir for
11619 all direct connections. Should fix bugs 827, 883, and 900.
11620 - Relays were falling out of the networkstatus consensus for
11621 part of a day if they changed their local config but the
11622 authorities discarded their new descriptor as "not sufficiently
11623 different". Now directory authorities accept a descriptor as changed
11624 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
11625 patch by Sebastian.
11626 - Avoid crashing in the presence of certain malformed descriptors.
11627 Found by lark, and by automated fuzzing.
11630 - When generating circuit events with verbose nicknames for
11631 controllers, try harder to look up nicknames for routers on a
11632 circuit. (Previously, we would look in the router descriptors we had
11633 for nicknames, but not in the consensus.) Partial fix for bug 941.
11634 - If the bridge config line doesn't specify a port, assume 443.
11635 This makes bridge lines a bit smaller and easier for users to
11637 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
11638 bytes (aka 20KB/s), to match our documentation. Also update
11639 directory authorities so they always assign the Fast flag to relays
11640 with 20KB/s of capacity. Now people running relays won't suddenly
11641 find themselves not seeing any use, if the network gets faster
11643 - Update to the "April 3 2009" ip-to-country file.
11646 - Avoid trying to print raw memory to the logs when we decide to
11647 give up on downloading a given relay descriptor. Bugfix on
11649 - In tor-resolve, when the Tor client to use is specified by
11650 <hostname>:<port>, actually use the specified port rather than
11651 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
11652 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
11653 - When starting with a cache over a few days old, do not leak
11654 memory for the obsolete router descriptors in it. Bugfix on
11656 - Avoid double-free on list of successfully uploaded hidden
11657 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
11658 - Change memarea_strndup() implementation to work even when
11659 duplicating a string at the end of a page. This bug was
11660 harmless for now, but could have meant crashes later. Fix by
11661 lark. Bugfix on 0.2.1.1-alpha.
11662 - Limit uploaded directory documents to be 16M rather than 500K.
11663 The directory authorities were refusing v3 consensus votes from
11664 other authorities, since the votes are now 504K. Fixes bug 959;
11665 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
11666 - Directory authorities should never send a 503 "busy" response to
11667 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
11671 Changes in version 0.2.1.13-alpha - 2009-03-09
11672 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
11673 cleanups. We're finally getting close to a release candidate.
11676 - Correctly update the list of which countries we exclude as
11677 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
11678 lark. Bugfix on 0.2.1.6-alpha.
11680 o Minor bugfixes (on 0.2.0.x and earlier):
11681 - Automatically detect MacOSX versions earlier than 10.4.0, and
11682 disable kqueue from inside Tor when running with these versions.
11683 We previously did this from the startup script, but that was no
11684 help to people who didn't use the startup script. Resolves bug 863.
11685 - When we had picked an exit node for a connection, but marked it as
11686 "optional", and it turned out we had no onion key for the exit,
11687 stop wanting that exit and try again. This situation may not
11688 be possible now, but will probably become feasible with proposal
11689 158. Spotted by rovv. Fixes another case of bug 752.
11690 - Clients no longer cache certificates for authorities they do not
11691 recognize. Bugfix on 0.2.0.9-alpha.
11692 - When we can't transmit a DNS request due to a network error, retry
11693 it after a while, and eventually transmit a failing response to
11694 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
11695 - If the controller claimed responsibility for a stream, but that
11696 stream never finished making its connection, it would live
11697 forever in circuit_wait state. Now we close it after SocksTimeout
11698 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
11699 - Drop begin cells to a hidden service if they come from the middle
11700 of a circuit. Patch from lark.
11701 - When we erroneously receive two EXTEND cells for the same circuit
11702 ID on the same connection, drop the second. Patch from lark.
11703 - Fix a crash that occurs on exit nodes when a nameserver request
11704 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
11705 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
11707 - Do not assume that a stack-allocated character array will be
11708 64-bit aligned on platforms that demand that uint64_t access is
11709 aligned. Possible fix for bug 604.
11710 - Parse dates and IPv4 addresses in a locale- and libc-independent
11711 manner, to avoid platform-dependent behavior on malformed input.
11712 - Build correctly when configured to build outside the main source
11713 path. Patch from Michael Gold.
11714 - We were already rejecting relay begin cells with destination port
11715 of 0. Now also reject extend cells with destination port or address
11716 of 0. Suggested by lark.
11718 o Minor bugfixes (on 0.2.1.x):
11719 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
11720 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
11721 - If we're an exit node, scrub the IP address to which we are exiting
11722 in the logs. Bugfix on 0.2.1.8-alpha.
11725 - On Linux, use the prctl call to re-enable core dumps when the user
11727 - New controller event NEWCONSENSUS that lists the networkstatus
11728 lines for every recommended relay. Now controllers like Torflow
11729 can keep up-to-date on which relays they should be using.
11730 - Update to the "February 26 2009" ip-to-country file.
11733 Changes in version 0.2.0.34 - 2009-02-08
11734 Tor 0.2.0.34 features several more security-related fixes. You should
11735 upgrade, especially if you run an exit relay (remote crash) or a
11736 directory authority (remote infinite loop), or you're on an older
11737 (pre-XP) or not-recently-patched Windows (remote exploit).
11739 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
11740 have many known flaws, and nobody should be using them. You should
11741 upgrade. If you're using a Linux or BSD and its packages are obsolete,
11742 stop using those packages and upgrade anyway.
11745 - Fix an infinite-loop bug on handling corrupt votes under certain
11746 circumstances. Bugfix on 0.2.0.8-alpha.
11747 - Fix a temporary DoS vulnerability that could be performed by
11748 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11749 - Avoid a potential crash on exit nodes when processing malformed
11750 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
11751 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11752 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11755 - Fix compilation on systems where time_t is a 64-bit integer.
11756 Patch from Matthias Drochner.
11757 - Don't consider expiring already-closed client connections. Fixes
11758 bug 893. Bugfix on 0.0.2pre20.
11761 Changes in version 0.2.1.12-alpha - 2009-02-08
11762 Tor 0.2.1.12-alpha features several more security-related fixes. You
11763 should upgrade, especially if you run an exit relay (remote crash) or
11764 a directory authority (remote infinite loop), or you're on an older
11765 (pre-XP) or not-recently-patched Windows (remote exploit). It also
11766 includes a big pile of minor bugfixes and cleanups.
11769 - Fix an infinite-loop bug on handling corrupt votes under certain
11770 circumstances. Bugfix on 0.2.0.8-alpha.
11771 - Fix a temporary DoS vulnerability that could be performed by
11772 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11773 - Avoid a potential crash on exit nodes when processing malformed
11774 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
11777 - Let controllers actually ask for the "clients_seen" event for
11778 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
11779 reported by Matt Edman.
11780 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
11782 - Fix a bug in address parsing that was preventing bridges or hidden
11783 service targets from being at IPv6 addresses.
11784 - Solve a bug that kept hardware crypto acceleration from getting
11785 enabled when accounting was turned on. Fixes bug 907. Bugfix on
11787 - Remove a bash-ism from configure.in to build properly on non-Linux
11788 platforms. Bugfix on 0.2.1.1-alpha.
11789 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
11790 headers. Bugfix on 0.2.0.10-alpha.
11791 - Don't consider expiring already-closed client connections. Fixes
11792 bug 893. Bugfix on 0.0.2pre20.
11793 - Fix another interesting corner-case of bug 891 spotted by rovv:
11794 Previously, if two hosts had different amounts of clock drift, and
11795 one of them created a new connection with just the wrong timing,
11796 the other might decide to deprecate the new connection erroneously.
11797 Bugfix on 0.1.1.13-alpha.
11798 - Resolve a very rare crash bug that could occur when the user forced
11799 a nameserver reconfiguration during the middle of a nameserver
11800 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
11801 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
11802 Bugfix on 0.2.1.7-alpha.
11803 - If we're using bridges and our network goes away, be more willing
11804 to forgive our bridges and try again when we get an application
11805 request. Bugfix on 0.2.0.x.
11808 - Support platforms where time_t is 64 bits long. (Congratulations,
11809 NetBSD!) Patch from Matthias Drochner.
11810 - Add a 'getinfo status/clients-seen' controller command, in case
11811 controllers want to hear clients_seen events but connect late.
11814 - Disable GCC's strict alias optimization by default, to avoid the
11815 likelihood of its introducing subtle bugs whenever our code violates
11816 the letter of C99's alias rules.
11819 Changes in version 0.2.0.33 - 2009-01-21
11820 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11821 useful to users. It also finally fixes a bug where a relay or client
11822 that's been off for many days would take a long time to bootstrap.
11824 This update also fixes an important security-related bug reported by
11825 Ilja van Sprundel. You should upgrade. (We'll send out more details
11826 about the bug once people have had some time to upgrade.)
11829 - Fix a heap-corruption bug that may be remotely triggerable on
11830 some platforms. Reported by Ilja van Sprundel.
11833 - When a stream at an exit relay is in state "resolving" or
11834 "connecting" and it receives an "end" relay cell, the exit relay
11835 would silently ignore the end cell and not close the stream. If
11836 the client never closes the circuit, then the exit relay never
11837 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
11838 reported by "wood".
11839 - When sending CREATED cells back for a given circuit, use a 64-bit
11840 connection ID to find the right connection, rather than an addr:port
11841 combination. Now that we can have multiple OR connections between
11842 the same ORs, it is no longer possible to use addr:port to uniquely
11843 identify a connection.
11844 - Bridge relays that had DirPort set to 0 would stop fetching
11845 descriptors shortly after startup, and then briefly resume
11846 after a new bandwidth test and/or after publishing a new bridge
11847 descriptor. Bridge users that try to bootstrap from them would
11848 get a recent networkstatus but would get descriptors from up to
11849 18 hours earlier, meaning most of the descriptors were obsolete
11850 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11851 - Prevent bridge relays from serving their 'extrainfo' document
11852 to anybody who asks, now that extrainfo docs include potentially
11853 sensitive aggregated client geoip summaries. Bugfix on
11855 - If the cached networkstatus consensus is more than five days old,
11856 discard it rather than trying to use it. In theory it could be
11857 useful because it lists alternate directory mirrors, but in practice
11858 it just means we spend many minutes trying directory mirrors that
11859 are long gone from the network. Also discard router descriptors as
11860 we load them if they are more than five days old, since the onion
11861 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
11864 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11865 could make gcc generate non-functional binary search code. Bugfix
11867 - Build correctly on platforms without socklen_t.
11868 - Compile without warnings on solaris.
11869 - Avoid potential crash on internal error during signature collection.
11870 Fixes bug 864. Patch from rovv.
11871 - Correct handling of possible malformed authority signing key
11872 certificates with internal signature types. Fixes bug 880.
11873 Bugfix on 0.2.0.3-alpha.
11874 - Fix a hard-to-trigger resource leak when logging credential status.
11876 - When we can't initialize DNS because the network is down, do not
11877 automatically stop Tor from starting. Instead, we retry failed
11878 dns_init() every 10 minutes, and change the exit policy to reject
11879 *:* until one succeeds. Fixes bug 691.
11880 - Use 64 bits instead of 32 bits for connection identifiers used with
11881 the controller protocol, to greatly reduce risk of identifier reuse.
11882 - When we're choosing an exit node for a circuit, and we have
11883 no pending streams, choose a good general exit rather than one that
11884 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11885 - Fix another case of assuming, when a specific exit is requested,
11886 that we know more than the user about what hosts it allows.
11887 Fixes one case of bug 752. Patch from rovv.
11888 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11889 seconds. Warn the user if lower values are given in the
11890 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11891 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11892 user if lower values are given in the configuration. Bugfix on
11893 0.1.1.17-rc. Patch by Sebastian.
11894 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
11895 the cache because we already had a v0 descriptor with the same ID.
11896 Bugfix on 0.2.0.18-alpha.
11897 - Fix a race condition when freeing keys shared between main thread
11898 and CPU workers that could result in a memory leak. Bugfix on
11899 0.1.0.1-rc. Fixes bug 889.
11900 - Send a valid END cell back when a client tries to connect to a
11901 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11902 840. Patch from rovv.
11903 - Check which hops rendezvous stream cells are associated with to
11904 prevent possible guess-the-streamid injection attacks from
11905 intermediate hops. Fixes another case of bug 446. Based on patch
11907 - If a broken client asks a non-exit router to connect somewhere,
11908 do not even do the DNS lookup before rejecting the connection.
11909 Fixes another case of bug 619. Patch from rovv.
11910 - When a relay gets a create cell it can't decrypt (e.g. because it's
11911 using the wrong onion key), we were dropping it and letting the
11912 client time out. Now actually answer with a destroy cell. Fixes
11913 bug 904. Bugfix on 0.0.2pre8.
11915 o Minor bugfixes (hidden services):
11916 - Do not throw away existing introduction points on SIGHUP. Bugfix on
11917 0.0.6pre1. Patch by Karsten. Fixes bug 874.
11920 - Report the case where all signatures in a detached set are rejected
11921 differently than the case where there is an error handling the
11923 - When we realize that another process has modified our cached
11924 descriptors, print out a more useful error message rather than
11925 triggering an assertion. Fixes bug 885. Patch from Karsten.
11926 - Implement the 0x20 hack to better resist DNS poisoning: set the
11927 case on outgoing DNS requests randomly, and reject responses that do
11928 not match the case correctly. This logic can be disabled with the
11929 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
11930 of servers that do not reliably preserve case in replies. See
11931 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11933 - Check DNS replies for more matching fields to better resist DNS
11935 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11936 compress cells, which are basically all encrypted, compressed, or
11940 Changes in version 0.2.1.11-alpha - 2009-01-20
11941 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
11942 week it will take a long time to bootstrap again" bug. It also fixes
11943 an important security-related bug reported by Ilja van Sprundel. You
11944 should upgrade. (We'll send out more details about the bug once people
11945 have had some time to upgrade.)
11948 - Fix a heap-corruption bug that may be remotely triggerable on
11949 some platforms. Reported by Ilja van Sprundel.
11952 - Discard router descriptors as we load them if they are more than
11953 five days old. Otherwise if Tor is off for a long time and then
11954 starts with cached descriptors, it will try to use the onion
11955 keys in those obsolete descriptors when building circuits. Bugfix
11956 on 0.2.0.x. Fixes bug 887.
11959 - Try to make sure that the version of Libevent we're running with
11960 is binary-compatible with the one we built with. May address bug
11962 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
11963 for bug 905. Bugfix on 0.2.1.7-alpha.
11964 - Add a new --enable-local-appdata configuration switch to change
11965 the default location of the datadir on win32 from APPDATA to
11966 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
11967 entirely. Patch from coderman.
11970 - Make outbound DNS packets respect the OutboundBindAddress setting.
11971 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
11972 - When our circuit fails at the first hop (e.g. we get a destroy
11973 cell back), avoid using that OR connection anymore, and also
11974 tell all the one-hop directory requests waiting for it that they
11975 should fail. Bugfix on 0.2.1.3-alpha.
11976 - In the torify(1) manpage, mention that tsocks will leak your
11980 Changes in version 0.2.1.10-alpha - 2009-01-06
11981 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
11982 would make the bridge relay not so useful if it had DirPort set to 0,
11983 and one that could let an attacker learn a little bit of information
11984 about the bridge's users), and a bug that would cause your Tor relay
11985 to ignore a circuit create request it can't decrypt (rather than reply
11986 with an error). It also fixes a wide variety of other bugs.
11989 - If the cached networkstatus consensus is more than five days old,
11990 discard it rather than trying to use it. In theory it could
11991 be useful because it lists alternate directory mirrors, but in
11992 practice it just means we spend many minutes trying directory
11993 mirrors that are long gone from the network. Helps bug 887 a bit;
11995 - Bridge relays that had DirPort set to 0 would stop fetching
11996 descriptors shortly after startup, and then briefly resume
11997 after a new bandwidth test and/or after publishing a new bridge
11998 descriptor. Bridge users that try to bootstrap from them would
11999 get a recent networkstatus but would get descriptors from up to
12000 18 hours earlier, meaning most of the descriptors were obsolete
12001 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12002 - Prevent bridge relays from serving their 'extrainfo' document
12003 to anybody who asks, now that extrainfo docs include potentially
12004 sensitive aggregated client geoip summaries. Bugfix on
12008 - New controller event "clients_seen" to report a geoip-based summary
12009 of which countries we've seen clients from recently. Now controllers
12010 like Vidalia can show bridge operators that they're actually making
12012 - Build correctly against versions of OpenSSL 0.9.8 or later built
12013 without support for deprecated functions.
12014 - Update to the "December 19 2008" ip-to-country file.
12016 o Minor bugfixes (on 0.2.0.x):
12017 - Authorities now vote for the Stable flag for any router whose
12018 weighted MTBF is at least 5 days, regardless of the mean MTBF.
12019 - Do not remove routers as too old if we do not have any consensus
12020 document. Bugfix on 0.2.0.7-alpha.
12021 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12022 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12023 - When an exit relay resolves a stream address to a local IP address,
12024 do not just keep retrying that same exit relay over and
12025 over. Instead, just close the stream. Addresses bug 872. Bugfix
12026 on 0.2.0.32. Patch from rovv.
12027 - If a hidden service sends us an END cell, do not consider
12028 retrying the connection; just close it. Patch from rovv.
12029 - When we made bridge authorities stop serving bridge descriptors over
12030 unencrypted links, we also broke DirPort reachability testing for
12031 bridges. So bridges with a non-zero DirPort were printing spurious
12032 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
12033 - When a relay gets a create cell it can't decrypt (e.g. because it's
12034 using the wrong onion key), we were dropping it and letting the
12035 client time out. Now actually answer with a destroy cell. Fixes
12036 bug 904. Bugfix on 0.0.2pre8.
12037 - Squeeze 2-5% out of client performance (according to oprofile) by
12038 improving the implementation of some policy-manipulation functions.
12040 o Minor bugfixes (on 0.2.1.x):
12041 - Make get_interface_address() function work properly again; stop
12042 guessing the wrong parts of our address as our address.
12043 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
12044 send on that circuit. Otherwise we might violate the proposal-110
12045 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
12047 - When we're sending non-EXTEND cells to the first hop in a circuit,
12048 for example to use an encrypted directory connection, we don't need
12049 to use RELAY_EARLY cells: the first hop knows what kind of cell
12050 it is, and nobody else can even see the cell type. Conserving
12051 RELAY_EARLY cells makes it easier to cannibalize circuits like
12053 - Stop logging nameserver addresses in reverse order.
12054 - If we are retrying a directory download slowly over and over, do
12055 not automatically give up after the 254th failure. Bugfix on
12057 - Resume reporting accurate "stream end" reasons to the local control
12058 port. They were lost in the changes for Proposal 148. Bugfix on
12061 o Deprecated and removed features:
12062 - The old "tor --version --version" command, which would print out
12063 the subversion "Id" of most of the source files, is now removed. It
12064 turned out to be less useful than we'd expected, and harder to
12067 o Code simplifications and refactoring:
12068 - Change our header file guard macros to be less likely to conflict
12069 with system headers. Adam Langley noticed that we were conflicting
12070 with log.h on Android.
12071 - Tool-assisted documentation cleanup. Nearly every function or
12072 static variable in Tor should have its own documentation now.
12075 Changes in version 0.2.1.9-alpha - 2008-12-25
12076 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
12078 o New directory authorities:
12079 - gabelmoo (the authority run by Karsten Loesing) now has a new
12083 - Never use a connection with a mismatched address to extend a
12084 circuit, unless that connection is canonical. A canonical
12085 connection is one whose address is authenticated by the router's
12086 identity key, either in a NETINFO cell or in a router descriptor.
12087 - Avoid a possible memory corruption bug when receiving hidden service
12088 descriptors. Bugfix on 0.2.1.6-alpha.
12091 - Fix a logic error that would automatically reject all but the first
12092 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
12093 part of bug 813/868. Bug spotted by coderman.
12094 - When a stream at an exit relay is in state "resolving" or
12095 "connecting" and it receives an "end" relay cell, the exit relay
12096 would silently ignore the end cell and not close the stream. If
12097 the client never closes the circuit, then the exit relay never
12098 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
12099 reported by "wood".
12100 - When we can't initialize DNS because the network is down, do not
12101 automatically stop Tor from starting. Instead, retry failed
12102 dns_init() every 10 minutes, and change the exit policy to reject
12103 *:* until one succeeds. Fixes bug 691.
12106 - Give a better error message when an overzealous init script says
12107 "sudo -u username tor --user username". Makes Bug 882 easier for
12109 - When a directory authority gives us a new guess for our IP address,
12110 log which authority we used. Hopefully this will help us debug
12111 the recent complaints about bad IP address guesses.
12112 - Detect svn revision properly when we're using git-svn.
12113 - Try not to open more than one descriptor-downloading connection
12114 to an authority at once. This should reduce load on directory
12115 authorities. Fixes bug 366.
12116 - Add cross-certification to newly generated certificates, so that
12117 a signing key is enough information to look up a certificate.
12118 Partial implementation of proposal 157.
12119 - Start serving certificates by <identity digest, signing key digest>
12120 pairs. Partial implementation of proposal 157.
12121 - Clients now never report any stream end reason except 'MISC'.
12122 Implements proposal 148.
12123 - On platforms with a maximum syslog string length, truncate syslog
12124 messages to that length ourselves, rather than relying on the
12125 system to do it for us.
12126 - Optimize out calls to time(NULL) that occur for every IO operation,
12127 or for every cell. On systems where time() is a slow syscall,
12128 this fix will be slightly helpful.
12129 - Exit servers can now answer resolve requests for ip6.arpa addresses.
12130 - When we download a descriptor that we then immediately (as
12131 a directory authority) reject, do not retry downloading it right
12132 away. Should save some bandwidth on authorities. Fix for bug
12133 888. Patch by Sebastian Hahn.
12134 - When a download gets us zero good descriptors, do not notify
12135 Tor that new directory information has arrived.
12136 - Avoid some nasty corner cases in the logic for marking connections
12137 as too old or obsolete or noncanonical for circuits. Partial
12140 o Minor features (controller):
12141 - New CONSENSUS_ARRIVED event to note when a new consensus has
12142 been fetched and validated.
12143 - When we realize that another process has modified our cached
12144 descriptors file, print out a more useful error message rather
12145 than triggering an assertion. Fixes bug 885. Patch from Karsten.
12146 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
12147 controllers to prevent SIGHUP from reloading the
12148 configuration. Fixes bug 856.
12151 - Resume using the correct "REASON=" stream when telling the
12152 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
12153 - When a canonical connection appears later in our internal list
12154 than a noncanonical one for a given OR ID, always use the
12155 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
12157 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12158 seconds. Warn the user if lower values are given in the
12159 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12160 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12161 user if lower values are given in the configuration. Bugfix on
12162 0.1.1.17-rc. Patch by Sebastian.
12163 - Fix a race condition when freeing keys shared between main thread
12164 and CPU workers that could result in a memory leak. Bugfix on
12165 0.1.0.1-rc. Fixes bug 889.
12167 o Minor bugfixes (hidden services):
12168 - Do not throw away existing introduction points on SIGHUP (bugfix on
12169 0.0.6pre1); also, do not stall hidden services because we're
12170 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
12171 by John Brooks. Patch by Karsten. Fixes bug 874.
12172 - Fix a memory leak when we decline to add a v2 rendezvous
12173 descriptor to the cache because we already had a v0 descriptor
12174 with the same ID. Bugfix on 0.2.0.18-alpha.
12176 o Deprecated and removed features:
12177 - RedirectExits has been removed. It was deprecated since
12179 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
12180 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
12181 - Cell pools are now always enabled; --disable-cell-pools is ignored.
12183 o Code simplifications and refactoring:
12184 - Rename the confusing or_is_obsolete field to the more appropriate
12185 is_bad_for_new_circs, and move it to or_connection_t where it
12187 - Move edge-only flags from connection_t to edge_connection_t: not
12188 only is this better coding, but on machines of plausible alignment,
12189 it should save 4-8 bytes per connection_t. "Every little bit helps."
12190 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
12191 for consistency; keep old option working for backward compatibility.
12192 - Simplify the code for finding connections to use for a circuit.
12195 Changes in version 0.2.1.8-alpha - 2008-12-08
12196 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
12197 builds better on unusual platforms like Solaris and old OS X, and
12198 fixes a variety of other issues.
12201 - New DirPortFrontPage option that takes an html file and publishes
12202 it as "/" on the DirPort. Now relay operators can provide a
12203 disclaimer without needing to set up a separate webserver. There's
12204 a sample disclaimer in contrib/tor-exit-notice.html.
12207 - When the client is choosing entry guards, now it selects at most
12208 one guard from a given relay family. Otherwise we could end up with
12209 all of our entry points into the network run by the same operator.
12210 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
12213 - Fix a DOS opportunity during the voting signature collection process
12214 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12215 - Fix a possible segfault when establishing an exit connection. Bugfix
12219 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
12221 - Made Tor a little less aggressive about deleting expired
12222 certificates. Partial fix for bug 854.
12223 - Stop doing unaligned memory access that generated bus errors on
12224 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
12225 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
12226 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
12227 - Make USR2 log-level switch take effect immediately. Bugfix on
12229 - If one win32 nameserver fails to get added, continue adding the
12230 rest, and don't automatically fail.
12231 - Use fcntl() for locking when flock() is not available. Should fix
12232 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
12233 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12234 could make gcc generate non-functional binary search code. Bugfix
12236 - Build correctly on platforms without socklen_t.
12237 - Avoid potential crash on internal error during signature collection.
12238 Fixes bug 864. Patch from rovv.
12239 - Do not use C's stdio library for writing to log files. This will
12240 improve logging performance by a minute amount, and will stop
12241 leaking fds when our disk is full. Fixes bug 861.
12242 - Stop erroneous use of O_APPEND in cases where we did not in fact
12243 want to re-seek to the end of a file before every last write().
12244 - Correct handling of possible malformed authority signing key
12245 certificates with internal signature types. Fixes bug 880. Bugfix
12247 - Fix a hard-to-trigger resource leak when logging credential status.
12251 - Directory mirrors no longer fetch the v1 directory or
12252 running-routers files. They are obsolete, and nobody asks for them
12253 anymore. This is the first step to making v1 authorities obsolete.
12255 o Minor features (controller):
12256 - Return circuit purposes in response to GETINFO circuit-status. Fixes
12260 Changes in version 0.2.0.32 - 2008-11-20
12261 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
12262 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12263 a smaller security flaw that might allow an attacker to access local
12264 services, further improves hidden service performance, and fixes a
12265 variety of other issues.
12268 - The "User" and "Group" config options did not clear the
12269 supplementary group entries for the Tor process. The "User" option
12270 is now more robust, and we now set the groups to the specified
12271 user's primary group. The "Group" option is now ignored. For more
12272 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12273 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12274 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
12275 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12276 consistently obeyed: if an exit relay refuses a stream because its
12277 exit policy doesn't allow it, we would remember what IP address
12278 the relay said the destination address resolves to, even if it's
12279 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12282 - Fix a DOS opportunity during the voting signature collection process
12283 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12285 o Major bugfixes (hidden services):
12286 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12287 we were failing the whole hidden service request when the v0
12288 descriptor fetch fails, even if the v2 fetch is still pending and
12289 might succeed. Similarly, if the last v2 fetch fails, we were
12290 failing the whole hidden service request even if a v0 fetch is
12291 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12292 - When extending a circuit to a hidden service directory to upload a
12293 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12294 requests failed, because the router descriptor has not been
12295 downloaded yet. In these cases, do not attempt to upload the
12296 rendezvous descriptor, but wait until the router descriptor is
12297 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12298 descriptor from a hidden service directory for which the router
12299 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
12303 - Fix several infrequent memory leaks spotted by Coverity.
12304 - When testing for libevent functions, set the LDFLAGS variable
12305 correctly. Found by Riastradh.
12306 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12307 bootstrapping with tunneled directory connections. Bugfix on
12308 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12309 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12310 and we know that server B rejects most-but-not all connections to
12311 port 80, we would previously reject the connection. Now, we assume
12312 the user knows what they were asking for. Fixes bug 752. Bugfix
12313 on 0.0.9rc5. Diagnosed by BarkerJr.
12314 - If we overrun our per-second write limits a little, count this as
12315 having used up our write allocation for the second, and choke
12316 outgoing directory writes. Previously, we had only counted this when
12317 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
12318 Bugfix on 0.2.0.x (??).
12319 - Remove the old v2 directory authority 'lefkada' from the default
12320 list. It has been gone for many months.
12321 - Stop doing unaligned memory access that generated bus errors on
12322 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
12323 - Make USR2 log-level switch take effect immediately. Bugfix on
12326 o Minor bugfixes (controller):
12327 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
12328 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
12331 Changes in version 0.2.1.7-alpha - 2008-11-08
12332 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
12333 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12334 a smaller security flaw that might allow an attacker to access local
12335 services, adds better defense against DNS poisoning attacks on exit
12336 relays, further improves hidden service performance, and fixes a
12337 variety of other issues.
12340 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12341 consistently obeyed: if an exit relay refuses a stream because its
12342 exit policy doesn't allow it, we would remember what IP address
12343 the relay said the destination address resolves to, even if it's
12344 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12345 - The "User" and "Group" config options did not clear the
12346 supplementary group entries for the Tor process. The "User" option
12347 is now more robust, and we now set the groups to the specified
12348 user's primary group. The "Group" option is now ignored. For more
12349 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12350 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12351 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
12352 - Do not use or believe expired v3 authority certificates. Patch
12353 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
12356 - Now NodeFamily and MyFamily config options allow spaces in
12357 identity fingerprints, so it's easier to paste them in.
12358 Suggested by Lucky Green.
12359 - Implement the 0x20 hack to better resist DNS poisoning: set the
12360 case on outgoing DNS requests randomly, and reject responses that do
12361 not match the case correctly. This logic can be disabled with the
12362 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
12363 of servers that do not reliably preserve case in replies. See
12364 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12366 - Preserve case in replies to DNSPort requests in order to support
12367 the 0x20 hack for resisting DNS poisoning attacks.
12369 o Hidden service performance improvements:
12370 - When the client launches an introduction circuit, retry with a
12371 new circuit after 30 seconds rather than 60 seconds.
12372 - Launch a second client-side introduction circuit in parallel
12373 after a delay of 15 seconds (based on work by Christian Wilms).
12374 - Hidden services start out building five intro circuits rather
12375 than three, and when the first three finish they publish a service
12376 descriptor using those. Now we publish our service descriptor much
12377 faster after restart.
12380 - Minor fix in the warning messages when you're having problems
12381 bootstrapping; also, be more forgiving of bootstrap problems when
12382 we're still making incremental progress on a given bootstrap phase.
12383 - When we're choosing an exit node for a circuit, and we have
12384 no pending streams, choose a good general exit rather than one that
12385 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12386 - Send a valid END cell back when a client tries to connect to a
12387 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12388 840. Patch from rovv.
12389 - If a broken client asks a non-exit router to connect somewhere,
12390 do not even do the DNS lookup before rejecting the connection.
12391 Fixes another case of bug 619. Patch from rovv.
12392 - Fix another case of assuming, when a specific exit is requested,
12393 that we know more than the user about what hosts it allows.
12394 Fixes another case of bug 752. Patch from rovv.
12395 - Check which hops rendezvous stream cells are associated with to
12396 prevent possible guess-the-streamid injection attacks from
12397 intermediate hops. Fixes another case of bug 446. Based on patch
12399 - Avoid using a negative right-shift when comparing 32-bit
12400 addresses. Possible fix for bug 845 and bug 811.
12401 - Make the assert_circuit_ok() function work correctly on circuits that
12402 have already been marked for close.
12403 - Fix read-off-the-end-of-string error in unit tests when decoding
12404 introduction points.
12405 - Fix uninitialized size field for memory area allocation: may improve
12406 memory performance during directory parsing.
12407 - Treat duplicate certificate fetches as failures, so that we do
12408 not try to re-fetch an expired certificate over and over and over.
12409 - Do not say we're fetching a certificate when we'll in fact skip it
12410 because of a pending download.
12413 Changes in version 0.2.1.6-alpha - 2008-09-30
12414 Tor 0.2.1.6-alpha further improves performance and robustness of
12415 hidden services, starts work on supporting per-country relay selection,
12416 and fixes a variety of smaller issues.
12419 - Implement proposal 121: make it possible to build hidden services
12420 that only certain clients are allowed to connect to. This is
12421 enforced at several points, so that unauthorized clients are unable
12422 to send INTRODUCE cells to the service, or even (depending on the
12423 type of authentication) to learn introduction points. This feature
12424 raises the bar for certain kinds of active attacks against hidden
12425 services. Code by Karsten Loesing.
12426 - Relays now store and serve v2 hidden service descriptors by default,
12427 i.e., the new default value for HidServDirectoryV2 is 1. This is
12428 the last step in proposal 114, which aims to make hidden service
12429 lookups more reliable.
12430 - Start work to allow node restrictions to include country codes. The
12431 syntax to exclude nodes in a country with country code XX is
12432 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
12433 refinement to decide what config options should take priority if
12434 you ask to both use a particular node and exclude it.
12435 - Allow ExitNodes list to include IP ranges and country codes, just
12436 like the Exclude*Nodes lists. Patch from Robert Hogan.
12439 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
12440 Tor to fail to start if you had it configured to use a bridge
12441 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
12442 - When extending a circuit to a hidden service directory to upload a
12443 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12444 requests failed, because the router descriptor had not been
12445 downloaded yet. In these cases, we now wait until the router
12446 descriptor is downloaded, and then retry. Likewise, clients
12447 now skip over a hidden service directory if they don't yet have
12448 its router descriptor, rather than futilely requesting it and
12449 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
12451 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12452 we were failing the whole hidden service request when the v0
12453 descriptor fetch fails, even if the v2 fetch is still pending and
12454 might succeed. Similarly, if the last v2 fetch fails, we were
12455 failing the whole hidden service request even if a v0 fetch is
12456 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12457 - DNS replies need to have names matching their requests, but
12458 these names should be in the questions section, not necessarily
12459 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
12462 - Update to the "September 1 2008" ip-to-country file.
12463 - Allow ports 465 and 587 in the default exit policy again. We had
12464 rejected them in 0.1.0.15, because back in 2005 they were commonly
12465 misconfigured and ended up as spam targets. We hear they are better
12466 locked down these days.
12467 - Use a lockfile to make sure that two Tor processes are not
12468 simultaneously running with the same datadir.
12469 - Serve the latest v3 networkstatus consensus via the control
12470 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
12471 - Better logging about stability/reliability calculations on directory
12473 - Drop the requirement to have an open dir port for storing and
12474 serving v2 hidden service descriptors.
12475 - Directory authorities now serve a /tor/dbg-stability.txt URL to
12476 help debug WFU and MTBF calculations.
12477 - Implement most of Proposal 152: allow specialized servers to permit
12478 single-hop circuits, and clients to use those servers to build
12479 single-hop circuits when using a specialized controller. Patch
12480 from Josh Albrecht. Resolves feature request 768.
12481 - Add a -p option to tor-resolve for specifying the SOCKS port: some
12482 people find host:port too confusing.
12483 - Make TrackHostExit mappings expire a while after their last use, not
12484 after their creation. Patch from Robert Hogan.
12485 - Provide circuit purposes along with circuit events to the controller.
12488 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
12490 - Fixed some memory leaks -- some quite frequent, some almost
12491 impossible to trigger -- based on results from Coverity.
12492 - When testing for libevent functions, set the LDFLAGS variable
12493 correctly. Found by Riastradh.
12494 - Fix an assertion bug in parsing policy-related options; possible fix
12496 - Catch and report a few more bootstrapping failure cases when Tor
12497 fails to establish a TCP connection. Cleanup on 0.2.1.x.
12498 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12499 bootstrapping with tunneled directory connections. Bugfix on
12500 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12501 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12502 and we know that server B rejects most-but-not all connections to
12503 port 80, we would previously reject the connection. Now, we assume
12504 the user knows what they were asking for. Fixes bug 752. Bugfix
12505 on 0.0.9rc5. Diagnosed by BarkerJr.
12506 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
12507 service directories if they have no advertised dir port. Bugfix
12509 - If we overrun our per-second write limits a little, count this as
12510 having used up our write allocation for the second, and choke
12511 outgoing directory writes. Previously, we had only counted this when
12512 we had met our limits precisely. Fixes bug 824. Patch by rovv.
12513 Bugfix on 0.2.0.x (??).
12514 - Avoid a "0 divided by 0" calculation when calculating router uptime
12515 at directory authorities. Bugfix on 0.2.0.8-alpha.
12516 - Make DNS resolved controller events into "CLOSED", not
12517 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
12519 - Fix a bug where an unreachable relay would establish enough
12520 reachability testing circuits to do a bandwidth test -- if
12521 we already have a connection to the middle hop of the testing
12522 circuit, then it could establish the last hop by using the existing
12523 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
12524 circuits no longer use entry guards in 0.2.1.3-alpha.
12525 - If we have correct permissions on $datadir, we complain to stdout
12526 and fail to start. But dangerous permissions on
12527 $datadir/cached-status/ would cause us to open a log and complain
12528 there. Now complain to stdout and fail to start in both cases. Fixes
12529 bug 820, reported by seeess.
12530 - Remove the old v2 directory authority 'lefkada' from the default
12531 list. It has been gone for many months.
12533 o Code simplifications and refactoring:
12534 - Revise the connection_new functions so that a more typesafe variant
12535 exists. This will work better with Coverity, and let us find any
12536 actual mistakes we're making here.
12537 - Refactor unit testing logic so that dmalloc can be used sensibly
12538 with unit tests to check for memory leaks.
12539 - Move all hidden-service related fields from connection and circuit
12540 structure to substructures: this way they won't eat so much memory.
12543 Changes in version 0.2.0.31 - 2008-09-03
12544 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
12545 a big bug we're seeing where in rare cases traffic from one Tor stream
12546 gets mixed into another stream, and fixes a variety of smaller issues.
12549 - Make sure that two circuits can never exist on the same connection
12550 with the same circuit ID, even if one is marked for close. This
12551 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
12552 - Relays now reject risky extend cells: if the extend cell includes
12553 a digest of all zeroes, or asks to extend back to the relay that
12554 sent the extend cell, tear down the circuit. Ideas suggested
12556 - If not enough of our entry guards are available so we add a new
12557 one, we might use the new one even if it overlapped with the
12558 current circuit's exit relay (or its family). Anonymity bugfix
12559 pointed out by rovv.
12562 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12563 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12564 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12565 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12566 - Pick size of default geoip filename string correctly on windows.
12567 Fixes bug 806. Bugfix on 0.2.0.30.
12568 - Make the autoconf script accept the obsolete --with-ssl-dir
12569 option as an alias for the actually-working --with-openssl-dir
12570 option. Fix the help documentation to recommend --with-openssl-dir.
12571 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12572 - When using the TransPort option on OpenBSD, and using the User
12573 option to change UID and drop privileges, make sure to open
12574 /dev/pf before dropping privileges. Fixes bug 782. Patch from
12575 Christopher Davis. Bugfix on 0.1.2.1-alpha.
12576 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12577 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12578 on the client side when connecting to a hidden service. Bugfix
12579 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12580 - When closing an application-side connection because its circuit is
12581 getting torn down, generate the stream event correctly. Bugfix on
12582 0.1.2.x. Anonymous patch.
12585 Changes in version 0.2.1.5-alpha - 2008-08-31
12586 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
12587 in a lot of the infrastructure for adding authorization to hidden
12588 services, lays the groundwork for having clients read their load
12589 balancing information out of the networkstatus consensus rather than
12590 the individual router descriptors, addresses two potential anonymity
12591 issues, and fixes a variety of smaller issues.
12594 - Convert many internal address representations to optionally hold
12596 - Generate and accept IPv6 addresses in many protocol elements.
12597 - Make resolver code handle nameservers located at ipv6 addresses.
12598 - Begin implementation of proposal 121 ("Client authorization for
12599 hidden services"): configure hidden services with client
12600 authorization, publish descriptors for them, and configure
12601 authorization data for hidden services at clients. The next
12602 step is to actually access hidden services that perform client
12604 - More progress toward proposal 141: Network status consensus
12605 documents and votes now contain bandwidth information for each
12606 router and a summary of that router's exit policy. Eventually this
12607 will be used by clients so that they do not have to download every
12608 known descriptor before building circuits.
12610 o Major bugfixes (on 0.2.0.x and before):
12611 - When sending CREATED cells back for a given circuit, use a 64-bit
12612 connection ID to find the right connection, rather than an addr:port
12613 combination. Now that we can have multiple OR connections between
12614 the same ORs, it is no longer possible to use addr:port to uniquely
12615 identify a connection.
12616 - Relays now reject risky extend cells: if the extend cell includes
12617 a digest of all zeroes, or asks to extend back to the relay that
12618 sent the extend cell, tear down the circuit. Ideas suggested
12620 - If not enough of our entry guards are available so we add a new
12621 one, we might use the new one even if it overlapped with the
12622 current circuit's exit relay (or its family). Anonymity bugfix
12623 pointed out by rovv.
12626 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12627 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12628 - When using the TransPort option on OpenBSD, and using the User
12629 option to change UID and drop privileges, make sure to open /dev/pf
12630 before dropping privileges. Fixes bug 782. Patch from Christopher
12631 Davis. Bugfix on 0.1.2.1-alpha.
12632 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12633 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12634 - Add a missing safe_str() call for a debug log message.
12635 - Use 64 bits instead of 32 bits for connection identifiers used with
12636 the controller protocol, to greatly reduce risk of identifier reuse.
12637 - Make the autoconf script accept the obsolete --with-ssl-dir
12638 option as an alias for the actually-working --with-openssl-dir
12639 option. Fix the help documentation to recommend --with-openssl-dir.
12640 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12643 - Rate-limit too-many-sockets messages: when they happen, they happen
12644 a lot. Resolves bug 748.
12645 - Resist DNS poisoning a little better by making sure that names in
12646 answer sections match.
12647 - Print the SOCKS5 error message string as well as the error code
12648 when a tor-resolve request fails. Patch from Jacob.
12651 Changes in version 0.2.1.4-alpha - 2008-08-04
12652 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
12655 - The address part of exit policies was not correctly written
12656 to router descriptors. This generated router descriptors that failed
12657 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
12659 - Tor triggered a false assert when extending a circuit to a relay
12660 but we already have a connection open to that relay. Noticed by
12661 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
12664 - Fix a hidden service logging bug: in some edge cases, the router
12665 descriptor of a previously picked introduction point becomes
12666 obsolete and we need to give up on it rather than continually
12667 complaining that it has become obsolete. Observed by xiando. Bugfix
12670 o Removed features:
12671 - Take out the TestVia config option, since it was a workaround for
12672 a bug that was fixed in Tor 0.1.1.21.
12675 Changes in version 0.2.1.3-alpha - 2008-08-03
12676 Tor 0.2.1.3-alpha implements most of the pieces to prevent
12677 infinite-length circuit attacks (see proposal 110); fixes a bug that
12678 might cause exit relays to corrupt streams they send back; allows
12679 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
12680 ExcludeExitNodes config options; and fixes a big pile of bugs.
12682 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
12683 - Send a bootstrap problem "warn" event on the first problem if the
12684 reason is NO_ROUTE (that is, our network is down).
12687 - Implement most of proposal 110: The first K cells to be sent
12688 along a circuit are marked as special "early" cells; only K "early"
12689 cells will be allowed. Once this code is universal, we can block
12690 certain kinds of DOS attack by requiring that EXTEND commands must
12691 be sent using an "early" cell.
12694 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12695 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12696 on the client side when connecting to a hidden service. Bugfix
12697 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12698 - Ensure that two circuits can never exist on the same connection
12699 with the same circuit ID, even if one is marked for close. This
12700 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
12703 - When relays do their initial bandwidth measurement, don't limit
12704 to just our entry guards for the test circuits. Otherwise we tend
12705 to have multiple test circuits going through a single entry guard,
12706 which makes our bandwidth test less accurate. Fixes part of bug 654;
12707 patch contributed by Josh Albrecht.
12708 - Add an ExcludeExitNodes option so users can list a set of nodes
12709 that should be be excluded from the exit node position, but
12710 allowed elsewhere. Implements proposal 151.
12711 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
12712 ExcludeNodes and ExcludeExitNodes lists.
12713 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
12714 be more efficient. Formerly it was quadratic in the number of
12715 servers; now it should be linear. Fixes bug 509.
12716 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
12717 and n_conn_id_digest fields into a separate structure that's
12718 only needed when the circuit has not yet attached to an n_conn.
12721 - Change the contrib/tor.logrotate script so it makes the new
12722 logs as "_tor:_tor" rather than the default, which is generally
12723 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
12724 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12725 warnings (occasionally), but it can also cause the compiler to
12726 eliminate error-checking code. Suggested by Peter Gutmann.
12727 - When a hidden service is giving up on an introduction point candidate
12728 that was not included in the last published rendezvous descriptor,
12729 don't reschedule publication of the next descriptor. Fixes bug 763.
12731 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
12732 HiddenServiceExcludeNodes as obsolete: they never worked properly,
12733 and nobody claims to be using them. Fixes bug 754. Bugfix on
12734 0.1.0.1-rc. Patch from Christian Wilms.
12735 - Fix a small alignment and memory-wasting bug on buffer chunks.
12738 o Minor bugfixes (controller):
12739 - When closing an application-side connection because its circuit
12740 is getting torn down, generate the stream event correctly.
12741 Bugfix on 0.1.2.x. Anonymous patch.
12743 o Removed features:
12744 - Remove all backward-compatibility code to support relays running
12745 versions of Tor so old that they no longer work at all on the
12749 Changes in version 0.2.0.30 - 2008-07-15
12751 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12752 warnings (occasionally), but it can also cause the compiler to
12753 eliminate error-checking code. Suggested by Peter Gutmann.
12756 Changes in version 0.2.0.29-rc - 2008-07-08
12757 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
12758 hidden-service performance bugs, and fixes a bunch of smaller bugs.
12761 - If you have more than one bridge but don't know their keys,
12762 you would only launch a request for the descriptor of the first one
12763 on your list. (Tor considered launching requests for the others, but
12764 found that it already had a connection on the way for $0000...0000
12765 so it didn't open another.) Bugfix on 0.2.0.x.
12766 - If you have more than one bridge but don't know their keys, and the
12767 connection to one of the bridges failed, you would cancel all
12768 pending bridge connections. (After all, they all have the same
12769 digest.) Bugfix on 0.2.0.x.
12770 - When a hidden service was trying to establish an introduction point,
12771 and Tor had built circuits preemptively for such purposes, we
12772 were ignoring all the preemptive circuits and launching a new one
12773 instead. Bugfix on 0.2.0.14-alpha.
12774 - When a hidden service was trying to establish an introduction point,
12775 and Tor *did* manage to reuse one of the preemptively built
12776 circuits, it didn't correctly remember which one it used,
12777 so it asked for another one soon after, until there were no
12778 more preemptive circuits, at which point it launched one from
12779 scratch. Bugfix on 0.0.9.x.
12780 - Make directory servers include the X-Your-Address-Is: http header in
12781 their responses even for begin_dir conns. Now clients who only
12782 ever use begin_dir connections still have a way to learn their IP
12783 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
12786 - Fix a macro/CPP interaction that was confusing some compilers:
12787 some GCCs don't like #if/#endif pairs inside macro arguments.
12789 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
12790 Fixes bug 704; fix from Steven Murdoch.
12791 - When opening /dev/null in finish_daemonize(), do not pass the
12792 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
12793 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
12794 - Correctly detect transparent proxy support on Linux hosts that
12795 require in.h to be included before netfilter_ipv4.h. Patch
12797 - Disallow session resumption attempts during the renegotiation
12798 stage of the v2 handshake protocol. Clients should never be trying
12799 session resumption at this point, but apparently some did, in
12800 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
12801 found by Geoff Goodell.
12804 Changes in version 0.2.1.2-alpha - 2008-06-20
12805 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
12806 make it easier to set up your own private Tor network; fixes several
12807 big bugs with using more than one bridge relay; fixes a big bug with
12808 offering hidden services quickly after Tor starts; and uses a better
12809 API for reporting potential bootstrapping problems to the controller.
12812 - New TestingTorNetwork config option to allow adjustment of
12813 previously constant values that, while reasonable, could slow
12814 bootstrapping. Implements proposal 135. Patch from Karsten.
12817 - If you have more than one bridge but don't know their digests,
12818 you would only learn a request for the descriptor of the first one
12819 on your list. (Tor considered launching requests for the others, but
12820 found that it already had a connection on the way for $0000...0000
12821 so it didn't open another.) Bugfix on 0.2.0.x.
12822 - If you have more than one bridge but don't know their digests,
12823 and the connection to one of the bridges failed, you would cancel
12824 all pending bridge connections. (After all, they all have the
12825 same digest.) Bugfix on 0.2.0.x.
12826 - When establishing a hidden service, introduction points that
12827 originate from cannibalized circuits are completely ignored and not
12828 included in rendezvous service descriptors. This might be another
12829 reason for delay in making a hidden service available. Bugfix
12830 from long ago (0.0.9.x?)
12833 - Allow OpenSSL to use dynamic locks if it wants.
12834 - When building a consensus, do not include routers that are down.
12835 This will cut down 30% to 40% on consensus size. Implements
12837 - In directory authorities' approved-routers files, allow
12838 fingerprints with or without space.
12839 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
12840 controller can query our current bootstrap state in case it attaches
12841 partway through and wants to catch up.
12842 - Send an initial "Starting" bootstrap status event, so we have a
12843 state to start out in.
12846 - Asking for a conditional consensus at .../consensus/<fingerprints>
12847 would crash a dirserver if it did not already have a
12848 consensus. Bugfix on 0.2.1.1-alpha.
12849 - Clean up some macro/CPP interactions: some GCC versions don't like
12850 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
12853 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
12854 - Directory authorities shouldn't complain about bootstrapping
12855 problems just because they do a lot of reachability testing and
12856 some of the connection attempts fail.
12857 - Start sending "count" and "recommendation" key/value pairs in
12858 bootstrap problem status events, so the controller can hear about
12859 problems even before Tor decides they're worth reporting for sure.
12860 - If you're using bridges, generate "bootstrap problem" warnings
12861 as soon as you run out of working bridges, rather than waiting
12862 for ten failures -- which will never happen if you have less than
12864 - If we close our OR connection because there's been a circuit
12865 pending on it for too long, we were telling our bootstrap status
12866 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
12869 Changes in version 0.2.1.1-alpha - 2008-06-13
12870 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
12871 were making the Tor process bloat especially on Linux; makes our TLS
12872 handshake blend in better; sends "bootstrap phase" status events to
12873 the controller, so it can keep the user informed of progress (and
12874 problems) fetching directory information and establishing circuits;
12875 and adds a variety of smaller features.
12878 - More work on making our TLS handshake blend in: modify the list
12879 of ciphers advertised by OpenSSL in client mode to even more
12880 closely resemble a common web browser. We cheat a little so that
12881 we can advertise ciphers that the locally installed OpenSSL doesn't
12883 - Start sending "bootstrap phase" status events to the controller,
12884 so it can keep the user informed of progress fetching directory
12885 information and establishing circuits. Also inform the controller
12886 if we think we're stuck at a particular bootstrap phase. Implements
12888 - Resume using OpenSSL's RAND_poll() for better (and more portable)
12889 cross-platform entropy collection again. We used to use it, then
12890 stopped using it because of a bug that could crash systems that
12891 called RAND_poll when they had a lot of fds open. It looks like the
12892 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
12893 at startup, and to call RAND_poll() when we reseed later only if
12894 we have a non-buggy OpenSSL version.
12897 - When we choose to abandon a new entry guard because we think our
12898 older ones might be better, close any circuits pending on that
12899 new entry guard connection. This fix should make us recover much
12900 faster when our network is down and then comes back. Bugfix on
12901 0.1.2.8-beta; found by lodger.
12903 o Memory fixes and improvements:
12904 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
12905 to avoid unused RAM in buffer chunks and memory pools.
12906 - Speed up parsing and cut down on memory fragmentation by using
12907 stack-style allocations for parsing directory objects. Previously,
12908 this accounted for over 40% of allocations from within Tor's code
12909 on a typical directory cache.
12910 - Use a Bloom filter rather than a digest-based set to track which
12911 descriptors we need to keep around when we're cleaning out old
12912 router descriptors. This speeds up the computation significantly,
12913 and may reduce fragmentation.
12914 - Reduce the default smartlist size from 32 to 16; it turns out that
12915 most smartlists hold around 8-12 elements tops.
12916 - Make dumpstats() log the fullness and size of openssl-internal
12918 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
12919 patch to their OpenSSL, turn it on to save memory on servers. This
12920 patch will (with any luck) get included in a mainline distribution
12922 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12923 compress cells, which are basically all encrypted, compressed,
12927 - Stop reloading the router list from disk for no reason when we
12928 run out of reachable directory mirrors. Once upon a time reloading
12929 it would set the 'is_running' flag back to 1 for them. It hasn't
12930 done that for a long time.
12931 - In very rare situations new hidden service descriptors were
12932 published earlier than 30 seconds after the last change to the
12933 service. (We currently think that a hidden service descriptor
12934 that's been stable for 30 seconds is worth publishing.)
12937 - Allow separate log levels to be configured for different logging
12938 domains. For example, this allows one to log all notices, warnings,
12939 or errors, plus all memory management messages of level debug or
12940 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
12941 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
12942 and stop using a warning that had become unfixably verbose under
12944 - New --hush command-line option similar to --quiet. While --quiet
12945 disables all logging to the console on startup, --hush limits the
12946 output to messages of warning and error severity.
12947 - Servers support a new URL scheme for consensus downloads that
12948 allows the client to specify which authorities are trusted.
12949 The server then only sends the consensus if the client will trust
12950 it. Otherwise a 404 error is sent back. Clients use this
12951 new scheme when the server supports it (meaning it's running
12952 0.2.1.1-alpha or later). Implements proposal 134.
12953 - New configure/torrc options (--enable-geoip-stats,
12954 DirRecordUsageByCountry) to record how many IPs we've served
12955 directory info to in each country code, how many status documents
12956 total we've sent to each country code, and what share of the total
12957 directory requests we should expect to see.
12958 - Use the TLS1 hostname extension to more closely resemble browser
12960 - Lots of new unit tests.
12961 - Add a macro to implement the common pattern of iterating through
12962 two parallel lists in lockstep.
12965 Changes in version 0.2.0.28-rc - 2008-06-13
12966 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
12967 performance bug, and fixes a bunch of smaller bugs.
12970 - Fix a bug where, when we were choosing the 'end stream reason' to
12971 put in our relay end cell that we send to the exit relay, Tor
12972 clients on Windows were sometimes sending the wrong 'reason'. The
12973 anonymity problem is that exit relays may be able to guess whether
12974 the client is running Windows, thus helping partition the anonymity
12975 set. Down the road we should stop sending reasons to exit relays,
12976 or otherwise prevent future versions of this bug.
12979 - While setting up a hidden service, some valid introduction circuits
12980 were overlooked and abandoned. This might be the reason for
12981 the long delay in making a hidden service available. Bugfix on
12985 - Update to the "June 9 2008" ip-to-country file.
12986 - Run 'make test' as part of 'make dist', so we stop releasing so
12987 many development snapshots that fail their unit tests.
12990 - When we're checking if we have enough dir info for each relay
12991 to begin establishing circuits, make sure that we actually have
12992 the descriptor listed in the consensus, not just any descriptor.
12994 - Bridge relays no longer print "xx=0" in their extrainfo document
12995 for every single country code in the geoip db. Bugfix on
12997 - Only warn when we fail to load the geoip file if we were planning to
12998 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
12999 - If we change our MaxAdvertisedBandwidth and then reload torrc,
13000 Tor won't realize it should publish a new relay descriptor. Fixes
13001 bug 688, reported by mfr. Bugfix on 0.1.2.x.
13002 - When we haven't had any application requests lately, don't bother
13003 logging that we have expired a bunch of descriptors. Bugfix
13005 - Make relay cells written on a connection count as non-padding when
13006 tracking how long a connection has been in use. Bugfix on
13007 0.2.0.1-alpha. Spotted by lodger.
13008 - Fix unit tests in 0.2.0.27-rc.
13009 - Fix compile on Windows.
13012 Changes in version 0.2.0.27-rc - 2008-06-03
13013 Tor 0.2.0.27-rc adds a few features we left out of the earlier
13014 release candidates. In particular, we now include an IP-to-country
13015 GeoIP database, so controllers can easily look up what country a
13016 given relay is in, and so bridge relays can give us some sanitized
13017 summaries about which countries are making use of bridges. (See proposal
13018 126-geoip-fetching.txt for details.)
13021 - Include an IP-to-country GeoIP file in the tarball, so bridge
13022 relays can report sanitized summaries of the usage they're seeing.
13025 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
13026 Robert Hogan. Fixes the first part of bug 681.
13027 - Make bridge authorities never serve extrainfo docs.
13028 - Add support to detect Libevent versions in the 1.4.x series
13030 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
13031 - Include a new contrib/tor-exit-notice.html file that exit relay
13032 operators can put on their website to help reduce abuse queries.
13035 - When tunneling an encrypted directory connection, and its first
13036 circuit fails, do not leave it unattached and ask the controller
13037 to deal. Fixes the second part of bug 681.
13038 - Make bridge authorities correctly expire old extrainfo documents
13042 Changes in version 0.2.0.26-rc - 2008-05-13
13043 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
13044 in Debian's OpenSSL packages. All users running any 0.2.0.x version
13045 should upgrade, whether they're running Debian or not.
13047 o Major security fixes:
13048 - Use new V3 directory authority keys on the tor26, gabelmoo, and
13049 moria1 V3 directory authorities. The old keys were generated with
13050 a vulnerable version of Debian's OpenSSL package, and must be
13051 considered compromised. Other authorities' keys were not generated
13052 with an affected version of OpenSSL.
13055 - List authority signatures as "unrecognized" based on DirServer
13056 lines, not on cert cache. Bugfix on 0.2.0.x.
13059 - Add a new V3AuthUseLegacyKey option to make it easier for
13060 authorities to change their identity keys if they have to.
13063 Changes in version 0.2.0.25-rc - 2008-04-23
13064 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
13067 - Remember to initialize threading before initializing logging.
13068 Otherwise, many BSD-family implementations will crash hard on
13069 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
13072 - Authorities correctly free policies on bad servers on
13073 exit. Fixes bug 672. Bugfix on 0.2.0.x.
13076 Changes in version 0.2.0.24-rc - 2008-04-22
13077 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
13078 v3 directory authority, makes relays with dynamic IP addresses and no
13079 DirPort notice more quickly when their IP address changes, fixes a few
13080 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
13082 o New directory authorities:
13083 - Take lefkada out of the list of v3 directory authorities, since
13084 it has been down for months.
13085 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
13089 - Detect address changes more quickly on non-directory mirror
13090 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
13092 o Minor features (security):
13093 - Reject requests for reverse-dns lookup of names that are in
13094 a private address space. Patch from lodger.
13095 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
13098 o Minor bugfixes (crashes):
13099 - Avoid a rare assert that can trigger when Tor doesn't have much
13100 directory information yet and it tries to fetch a v2 hidden
13101 service descriptor. Fixes bug 651, reported by nwf.
13102 - Initialize log mutex before initializing dmalloc. Otherwise,
13103 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
13104 - Use recursive pthread mutexes in order to avoid deadlock when
13105 logging debug-level messages to a controller. Bug spotted by nwf,
13106 bugfix on 0.2.0.16-alpha.
13108 o Minor bugfixes (resource management):
13109 - Keep address policies from leaking memory: start their refcount
13110 at 1, not 2. Bugfix on 0.2.0.16-alpha.
13111 - Free authority certificates on exit, so they don't look like memory
13112 leaks. Bugfix on 0.2.0.19-alpha.
13113 - Free static hashtables for policy maps and for TLS connections on
13114 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
13115 - Avoid allocating extra space when computing consensuses on 64-bit
13116 platforms. Bug spotted by aakova.
13118 o Minor bugfixes (misc):
13119 - Do not read the configuration file when we've only been told to
13120 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
13121 based on patch from Sebastian Hahn.
13122 - Exit relays that are used as a client can now reach themselves
13123 using the .exit notation, rather than just launching an infinite
13124 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
13125 - When attempting to open a logfile fails, tell us why.
13126 - Fix a dumb bug that was preventing us from knowing that we should
13127 preemptively build circuits to handle expected directory requests.
13128 Fixes bug 660. Bugfix on 0.1.2.x.
13129 - Warn less verbosely about clock skew from netinfo cells from
13130 untrusted sources. Fixes bug 663.
13131 - Make controller stream events for DNS requests more consistent,
13132 by adding "new stream" events for DNS requests, and removing
13133 spurious "stream closed" events" for cached reverse resolves.
13134 Patch from mwenge. Fixes bug 646.
13135 - Correctly notify one-hop connections when a circuit build has
13136 failed. Possible fix for bug 669. Found by lodger.
13139 Changes in version 0.2.0.23-rc - 2008-03-24
13140 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
13141 makes bootstrapping faster if the first directory mirror you contact
13142 is down. The bundles also include the new Vidalia 0.1.2 release.
13145 - When a tunneled directory request is made to a directory server
13146 that's down, notice after 30 seconds rather than 120 seconds. Also,
13147 fail any begindir streams that are pending on it, so they can
13148 retry elsewhere. This was causing multi-minute delays on bootstrap.
13151 Changes in version 0.2.0.22-rc - 2008-03-18
13152 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
13153 enables encrypted directory connections by default for non-relays, fixes
13154 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
13155 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
13158 - Enable encrypted directory connections by default for non-relays,
13159 so censor tools that block Tor directory connections based on their
13160 plaintext patterns will no longer work. This means Tor works in
13161 certain censored countries by default again.
13164 - Make sure servers always request certificates from clients during
13165 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
13166 - Do not enter a CPU-eating loop when a connection is closed in
13167 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
13168 diagnosed by lodger; bugfix on 0.2.0.20-rc.
13169 - Fix assertion failure that could occur when a blocked circuit
13170 became unblocked, and it had pending client DNS requests. Bugfix
13171 on 0.2.0.1-alpha. Fixes bug 632.
13173 o Minor bugfixes (on 0.1.2.x):
13174 - Generate "STATUS_SERVER" events rather than misspelled
13175 "STATUS_SEVER" events. Caught by mwenge.
13176 - When counting the number of bytes written on a TLS connection,
13177 look at the BIO actually used for writing to the network, not
13178 at the BIO used (sometimes) to buffer data for the network.
13179 Looking at different BIOs could result in write counts on the
13180 order of ULONG_MAX. Fixes bug 614.
13181 - On Windows, correctly detect errors when listing the contents of
13182 a directory. Fix from lodger.
13184 o Minor bugfixes (on 0.2.0.x):
13185 - Downgrade "sslv3 alert handshake failure" message to INFO.
13186 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
13187 left BandwidthRate and BandwidthBurst at the default, we would be
13188 silently limited by those defaults. Now raise them to match the
13189 RelayBandwidth* values.
13190 - Fix the SVK version detection logic to work correctly on a branch.
13191 - Make --enable-openbsd-malloc work correctly on Linux with alpha
13192 CPUs. Fixes bug 625.
13193 - Logging functions now check that the passed severity is sane.
13194 - Use proper log levels in the testsuite call of
13195 get_interface_address6().
13196 - When using a nonstandard malloc, do not use the platform values for
13197 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
13198 - Make the openbsd malloc code use 8k pages on alpha CPUs and
13200 - Detect mismatched page sizes when using --enable-openbsd-malloc.
13201 - Avoid double-marked-for-close warning when certain kinds of invalid
13202 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
13203 for bug 617. Bugfix on 0.2.0.1-alpha.
13204 - Make sure that the "NULL-means-reject *:*" convention is followed by
13205 all the policy manipulation functions, avoiding some possible crash
13206 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
13207 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
13208 actually works, and doesn't warn about every single reverse lookup.
13209 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
13212 - Only log guard node status when guard node status has changed.
13213 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
13214 make "INFO" 75% less verbose.
13217 Changes in version 0.2.0.21-rc - 2008-03-02
13218 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
13219 makes Tor work well with Vidalia again, fixes a rare assert bug,
13220 and fixes a pair of more minor bugs. The bundles also include Vidalia
13221 0.1.0 and Torbutton 1.1.16.
13224 - The control port should declare that it requires password auth
13225 when HashedControlSessionPassword is set too. Patch from Matt Edman;
13226 bugfix on 0.2.0.20-rc. Fixes bug 615.
13227 - Downgrade assert in connection_buckets_decrement() to a log message.
13228 This may help us solve bug 614, and in any case will make its
13229 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
13230 - We were sometimes miscounting the number of bytes read from the
13231 network, causing our rate limiting to not be followed exactly.
13232 Bugfix on 0.2.0.16-alpha. Reported by lodger.
13235 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
13236 OpenSSL versions should have been working fine. Diagnosis and patch
13237 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
13238 Bugfix on 0.2.0.20-rc.
13241 Changes in version 0.2.0.20-rc - 2008-02-24
13242 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
13243 makes more progress towards normalizing Tor's TLS handshake, makes
13244 hidden services work better again, helps relays bootstrap if they don't
13245 know their IP address, adds optional support for linking in openbsd's
13246 allocator or tcmalloc, allows really fast relays to scale past 15000
13247 sockets, and fixes a bunch of minor bugs reported by Veracode.
13250 - Enable the revised TLS handshake based on the one designed by
13251 Steven Murdoch in proposal 124, as revised in proposal 130. It
13252 includes version negotiation for OR connections as described in
13253 proposal 105. The new handshake is meant to be harder for censors
13254 to fingerprint, and it adds the ability to detect certain kinds of
13255 man-in-the-middle traffic analysis attacks. The version negotiation
13256 feature will allow us to improve Tor's link protocol more safely
13258 - Choose which bridge to use proportional to its advertised bandwidth,
13259 rather than uniformly at random. This should speed up Tor for
13260 bridge users. Also do this for people who set StrictEntryNodes.
13261 - When a TrackHostExits-chosen exit fails too many times in a row,
13262 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
13265 - Resolved problems with (re-)fetching hidden service descriptors.
13266 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
13267 and 0.2.0.19-alpha.
13268 - If we only ever used Tor for hidden service lookups or posts, we
13269 would stop building circuits and start refusing connections after
13270 24 hours, since we falsely believed that Tor was dormant. Reported
13271 by nwf; bugfix on 0.1.2.x.
13272 - Servers that don't know their own IP address should go to the
13273 authorities for their first directory fetch, even if their DirPort
13274 is off or if they don't know they're reachable yet. This will help
13275 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
13276 - When counting the number of open sockets, count not only the number
13277 of sockets we have received from the socket() call, but also
13278 the number we've gotten from accept() and socketpair(). This bug
13279 made us fail to count all sockets that we were using for incoming
13280 connections. Bugfix on 0.2.0.x.
13281 - Fix code used to find strings within buffers, when those strings
13282 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
13283 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
13284 - Add a new __HashedControlSessionPassword option for controllers
13285 to use for one-off session password hashes that shouldn't get
13286 saved to disk by SAVECONF --- Vidalia users were accumulating a
13287 pile of HashedControlPassword lines in their torrc files, one for
13288 each time they had restarted Tor and then clicked Save. Make Tor
13289 automatically convert "HashedControlPassword" to this new option but
13290 only when it's given on the command line. Partial fix for bug 586.
13292 o Minor features (performance):
13293 - Tune parameters for cell pool allocation to minimize amount of
13295 - Add OpenBSD malloc code from phk as an optional malloc
13296 replacement on Linux: some glibc libraries do very poorly
13297 with Tor's memory allocation patterns. Pass
13298 --enable-openbsd-malloc to get the replacement malloc code.
13299 - Add a --with-tcmalloc option to the configure script to link
13300 against tcmalloc (if present). Does not yet search for
13301 non-system include paths.
13302 - Stop imposing an arbitrary maximum on the number of file descriptors
13303 used for busy servers. Bug reported by Olaf Selke; patch from
13306 o Minor features (other):
13307 - When SafeLogging is disabled, log addresses along with all TLS
13309 - When building with --enable-gcc-warnings, check for whether Apple's
13310 warning "-Wshorten-64-to-32" is available.
13311 - Add a --passphrase-fd argument to the tor-gencert command for
13314 o Minor bugfixes (memory leaks and code problems):
13315 - We were leaking a file descriptor if Tor started with a zero-length
13316 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
13317 - Detect size overflow in zlib code. Reported by Justin Ferguson and
13319 - We were comparing the raw BridgePassword entry with a base64'ed
13320 version of it, when handling a "/tor/networkstatus-bridges"
13321 directory request. Now compare correctly. Noticed by Veracode.
13322 - Recover from bad tracked-since value in MTBF-history file.
13323 Should fix bug 537.
13324 - Alter the code that tries to recover from unhandled write
13325 errors, to not try to flush onto a socket that's given us
13326 unhandled errors. Bugfix on 0.1.2.x.
13327 - Make Unix controlsockets work correctly on OpenBSD. Patch from
13328 tup. Bugfix on 0.2.0.3-alpha.
13330 o Minor bugfixes (other):
13331 - If we have an extra-info document for our server, always make
13332 it available on the control port, even if we haven't gotten
13333 a copy of it from an authority yet. Patch from mwenge.
13334 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
13335 - Directory mirrors no longer include a guess at the client's IP
13336 address if the connection appears to be coming from the same /24
13337 network; it was producing too many wrong guesses.
13338 - Make the new hidden service code respect the SafeLogging setting.
13339 Bugfix on 0.2.0.x. Patch from Karsten.
13340 - When starting as an authority, do not overwrite all certificates
13341 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
13342 - If we're trying to flush the last bytes on a connection (for
13343 example, when answering a directory request), reset the
13344 time-to-give-up timeout every time we manage to write something
13345 on the socket. Bugfix on 0.1.2.x.
13346 - Change the behavior of "getinfo status/good-server-descriptor"
13347 so it doesn't return failure when any authority disappears.
13348 - Even though the man page said that "TrackHostExits ." should
13349 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
13350 - Report TLS "zero return" case as a "clean close" and "IO error"
13351 as a "close". Stop calling closes "unexpected closes": existing
13352 Tors don't use SSL_close(), so having a connection close without
13353 the TLS shutdown handshake is hardly unexpected.
13354 - Send NAMESERVER_STATUS messages for a single failed nameserver
13357 o Code simplifications and refactoring:
13358 - Remove the tor_strpartition function: its logic was confused,
13359 and it was only used for one thing that could be implemented far
13363 Changes in version 0.2.0.19-alpha - 2008-02-09
13364 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
13365 handshake, makes path selection for relays more secure and IP address
13366 guessing more robust, and generally fixes a lot of bugs in preparation
13367 for calling the 0.2.0 branch stable.
13370 - Do not include recognizeable strings in the commonname part of
13371 Tor's x509 certificates.
13374 - If we're a relay, avoid picking ourselves as an introduction point,
13375 a rendezvous point, or as the final hop for internal circuits. Bug
13376 reported by taranis and lodger. Bugfix on 0.1.2.x.
13377 - Patch from "Andrew S. Lists" to catch when we contact a directory
13378 mirror at IP address X and he says we look like we're coming from
13379 IP address X. Bugfix on 0.1.2.x.
13381 o Minor features (security):
13382 - Be more paranoid about overwriting sensitive memory on free(),
13383 as a defensive programming tactic to ensure forward secrecy.
13385 o Minor features (directory authority):
13386 - Actually validate the options passed to AuthDirReject,
13387 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
13388 - Reject router descriptors with out-of-range bandwidthcapacity or
13389 bandwidthburst values.
13391 o Minor features (controller):
13392 - Reject controller commands over 1MB in length. This keeps rogue
13393 processes from running us out of memory.
13395 o Minor features (misc):
13396 - Give more descriptive well-formedness errors for out-of-range
13397 hidden service descriptor/protocol versions.
13398 - Make memory debugging information describe more about history
13399 of cell allocation, so we can help reduce our memory use.
13401 o Deprecated features (controller):
13402 - The status/version/num-versioning and status/version/num-concurring
13403 GETINFO options are no longer useful in the v3 directory protocol:
13404 treat them as deprecated, and warn when they're used.
13407 - When our consensus networkstatus has been expired for a while, stop
13408 being willing to build circuits using it. Fixes bug 401. Bugfix
13410 - Directory caches now fetch certificates from all authorities
13411 listed in a networkstatus consensus, even when they do not
13412 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
13413 - When connecting to a bridge without specifying its key, insert
13414 the connection into the identity-to-connection map as soon as
13415 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
13416 - Detect versions of OS X where malloc_good_size() is present in the
13417 library but never actually declared. Resolves bug 587. Bugfix
13419 - Stop incorrectly truncating zlib responses to directory authority
13420 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
13421 - Stop recommending that every server operator send mail to tor-ops.
13422 Resolves bug 597. Bugfix on 0.1.2.x.
13423 - Don't trigger an assert if we start a directory authority with a
13424 private IP address (like 127.0.0.1).
13425 - Avoid possible failures when generating a directory with routers
13426 with over-long versions strings, or too many flags set. Bugfix
13428 - If an attempt to launch a DNS resolve request over the control
13429 port fails because we have overrun the limit on the number of
13430 connections, tell the controller that the request has failed.
13431 - Avoid using too little bandwidth when our clock skips a few
13432 seconds. Bugfix on 0.1.2.x.
13433 - Fix shell error when warning about missing packages in configure
13434 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
13435 - Do not become confused when receiving a spurious VERSIONS-like
13436 cell from a confused v1 client. Bugfix on 0.2.0.x.
13437 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
13438 introduction points for a hidden service have failed. Patch from
13439 Karsten Loesing. Bugfix on 0.2.0.x.
13441 o Code simplifications and refactoring:
13442 - Remove some needless generality from cpuworker code, for improved
13444 - Stop overloading the circuit_t.onionskin field for both "onionskin
13445 from a CREATE cell that we are waiting for a cpuworker to be
13446 assigned" and "onionskin from an EXTEND cell that we are going to
13447 send to an OR as soon as we are connected". Might help with bug 600.
13448 - Add an in-place version of aes_crypt() so that we can avoid doing a
13449 needless memcpy() call on each cell payload.
13452 Changes in version 0.2.0.18-alpha - 2008-01-25
13453 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
13454 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
13455 that can warn or reject connections to ports generally associated with
13456 vulnerable-plaintext protocols.
13458 o New directory authorities:
13459 - Set up dannenberg (run by CCC) as the sixth v3 directory
13463 - Fix a major memory leak when attempting to use the v2 TLS
13464 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
13465 - We accidentally enabled the under-development v2 TLS handshake
13466 code, which was causing log entries like "TLS error while
13467 renegotiating handshake". Disable it again. Resolves bug 590.
13468 - We were computing the wrong Content-Length: header for directory
13469 responses that need to be compressed on the fly, causing clients
13470 asking for those items to always fail. Bugfix on 0.2.0.x; partially
13474 - Avoid going directly to the directory authorities even if you're a
13475 relay, if you haven't found yourself reachable yet or if you've
13476 decided not to advertise your dirport yet. Addresses bug 556.
13477 - If we've gone 12 hours since our last bandwidth check, and we
13478 estimate we have less than 50KB bandwidth capacity but we could
13479 handle more, do another bandwidth test.
13480 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
13481 Tor can warn and/or refuse connections to ports commonly used with
13482 vulnerable-plaintext protocols. Currently we warn on ports 23,
13483 109, 110, and 143, but we don't reject any.
13486 - When we setconf ClientOnly to 1, close any current OR and Dir
13487 listeners. Reported by mwenge.
13488 - When we get a consensus that's been signed by more people than
13489 we expect, don't log about it; it's not a big deal. Reported
13493 - Don't answer "/tor/networkstatus-bridges" directory requests if
13494 the request isn't encrypted.
13495 - Make "ClientOnly 1" config option disable directory ports too.
13496 - Patches from Karsten Loesing to make v2 hidden services more
13497 robust: work even when there aren't enough HSDir relays available;
13498 retry when a v2 rend desc fetch fails; but don't retry if we
13499 already have a usable v0 rend desc.
13502 Changes in version 0.2.0.17-alpha - 2008-01-17
13503 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
13506 - Make the tor-gencert man page get included correctly in the tarball.
13509 Changes in version 0.2.0.16-alpha - 2008-01-17
13510 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
13511 Loesing, and generally cleans up a lot of features and minor bugs.
13513 o New directory authorities:
13514 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
13517 o Major performance improvements:
13518 - Switch our old ring buffer implementation for one more like that
13519 used by free Unix kernels. The wasted space in a buffer with 1mb
13520 of data will now be more like 8k than 1mb. The new implementation
13521 also avoids realloc();realloc(); patterns that can contribute to
13522 memory fragmentation.
13525 - Configuration files now accept C-style strings as values. This
13526 helps encode characters not allowed in the current configuration
13527 file format, such as newline or #. Addresses bug 557.
13528 - Although we fixed bug 539 (where servers would send HTTP status 503
13529 responses _and_ send a body too), there are still servers out
13530 there that haven't upgraded. Therefore, make clients parse such
13531 bodies when they receive them.
13532 - When we're not serving v2 directory information, there is no reason
13533 to actually keep any around. Remove the obsolete files and directory
13534 on startup if they are very old and we aren't going to serve them.
13536 o Minor performance improvements:
13537 - Reference-count and share copies of address policy entries; only 5%
13538 of them were actually distinct.
13539 - Never walk through the list of logs if we know that no log is
13540 interested in a given message.
13543 - When an authority has not signed a consensus, do not try to
13544 download a nonexistent "certificate with key 00000000". Bugfix
13545 on 0.2.0.x. Fixes bug 569.
13546 - Fix a rare assert error when we're closing one of our threads:
13547 use a mutex to protect the list of logs, so we never write to the
13548 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
13549 bug 575, which is kind of the revenge of bug 222.
13550 - Patch from Karsten Loesing to complain less at both the client
13551 and the relay when a relay used to have the HSDir flag but doesn't
13552 anymore, and we try to upload a hidden service descriptor.
13553 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
13555 - Do not try to download missing certificates until we have tried
13556 to check our fallback consensus. Fixes bug 583.
13557 - Make bridges round reported GeoIP stats info up to the nearest
13558 estimate, not down. Now we can distinguish between "0 people from
13559 this country" and "1 person from this country".
13560 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
13561 - Avoid possible segfault if key generation fails in
13562 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
13563 - Avoid segfault in the case where a badly behaved v2 versioning
13564 directory sends a signed networkstatus with missing client-versions.
13566 - Avoid segfaults on certain complex invocations of
13567 router_get_by_hexdigest(). Bugfix on 0.1.2.
13568 - Correct bad index on array access in parse_http_time(). Bugfix
13570 - Fix possible bug in vote generation when server versions are present
13571 but client versions are not.
13572 - Fix rare bug on REDIRECTSTREAM control command when called with no
13573 port set: it could erroneously report an error when none had
13575 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
13576 compressing large objects and find ourselves with more than 4k
13577 left over. Bugfix on 0.2.0.
13578 - Fix a small memory leak when setting up a hidden service.
13579 - Fix a few memory leaks that could in theory happen under bizarre
13581 - Fix an assert if we post a general-purpose descriptor via the
13582 control port but that descriptor isn't mentioned in our current
13583 network consensus. Bug reported by Jon McLachlan; bugfix on
13586 o Minor features (controller):
13587 - Get NS events working again. Patch from tup.
13588 - The GETCONF command now escapes and quotes configuration values
13589 that don't otherwise fit into the torrc file.
13590 - The SETCONF command now handles quoted values correctly.
13592 o Minor features (directory authorities):
13593 - New configuration options to override default maximum number of
13594 servers allowed on a single IP address. This is important for
13595 running a test network on a single host.
13596 - Actually implement the -s option to tor-gencert.
13597 - Add a manual page for tor-gencert.
13599 o Minor features (bridges):
13600 - Bridge authorities no longer serve bridge descriptors over
13601 unencrypted connections.
13603 o Minor features (other):
13604 - Add hidden services and DNSPorts to the list of things that make
13605 Tor accept that it has running ports. Change starting Tor with no
13606 ports from a fatal error to a warning; we might change it back if
13607 this turns out to confuse anybody. Fixes bug 579.
13610 Changes in version 0.1.2.19 - 2008-01-17
13611 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
13612 exit policy a little bit more conservative so it's safer to run an
13613 exit relay on a home system, and fixes a variety of smaller issues.
13616 - Exit policies now reject connections that are addressed to a
13617 relay's public (external) IP address too, unless
13618 ExitPolicyRejectPrivate is turned off. We do this because too
13619 many relays are running nearby to services that trust them based
13620 on network address.
13623 - When the clock jumps forward a lot, do not allow the bandwidth
13624 buckets to become negative. Fixes bug 544.
13625 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13626 on every successful resolve. Reported by Mike Perry.
13627 - Purge old entries from the "rephist" database and the hidden
13628 service descriptor database even when DirPort is zero.
13629 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13630 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13631 crashing or mis-answering these requests.
13632 - When we decide to send a 503 response to a request for servers, do
13633 not then also send the server descriptors: this defeats the whole
13634 purpose. Fixes bug 539.
13637 - Changing the ExitPolicyRejectPrivate setting should cause us to
13638 rebuild our server descriptor.
13639 - Fix handling of hex nicknames when answering controller requests for
13640 networkstatus by name, or when deciding whether to warn about
13641 unknown routers in a config option. (Patch from mwenge.)
13642 - Fix a couple of hard-to-trigger autoconf problems that could result
13643 in really weird results on platforms whose sys/types.h files define
13644 nonstandard integer types.
13645 - Don't try to create the datadir when running --verify-config or
13646 --hash-password. Resolves bug 540.
13647 - If we were having problems getting a particular descriptor from the
13648 directory caches, and then we learned about a new descriptor for
13649 that router, we weren't resetting our failure count. Reported
13651 - Although we fixed bug 539 (where servers would send HTTP status 503
13652 responses _and_ send a body too), there are still servers out there
13653 that haven't upgraded. Therefore, make clients parse such bodies
13654 when they receive them.
13655 - Run correctly on systems where rlim_t is larger than unsigned long.
13656 This includes some 64-bit systems.
13657 - Run correctly on platforms (like some versions of OS X 10.5) where
13658 the real limit for number of open files is OPEN_FILES, not rlim_max
13659 from getrlimit(RLIMIT_NOFILES).
13660 - Avoid a spurious free on base64 failure.
13661 - Avoid segfaults on certain complex invocations of
13662 router_get_by_hexdigest().
13663 - Fix rare bug on REDIRECTSTREAM control command when called with no
13664 port set: it could erroneously report an error when none had
13668 Changes in version 0.2.0.15-alpha - 2007-12-25
13669 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
13670 features added in 0.2.0.13-alpha.
13673 - Fix several remotely triggerable asserts based on DirPort requests
13674 for a v2 or v3 networkstatus object before we were prepared. This
13675 was particularly bad for 0.2.0.13 and later bridge relays, who
13676 would never have a v2 networkstatus and would thus always crash
13677 when used. Bugfixes on 0.2.0.x.
13678 - Estimate the v3 networkstatus size more accurately, rather than
13679 estimating it at zero bytes and giving it artificially high priority
13680 compared to other directory requests. Bugfix on 0.2.0.x.
13683 - Fix configure.in logic for cross-compilation.
13684 - When we load a bridge descriptor from the cache, and it was
13685 previously unreachable, mark it as retriable so we won't just
13686 ignore it. Also, try fetching a new copy immediately. Bugfixes
13688 - The bridge GeoIP stats were counting other relays, for example
13689 self-reachability and authority-reachability tests.
13692 - Support compilation to target iPhone; patch from cjacker huang.
13693 To build for iPhone, pass the --enable-iphone option to configure.
13696 Changes in version 0.2.0.14-alpha - 2007-12-23
13698 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
13699 without a datadirectory from a previous Tor install. Reported
13701 - Fix a crash when we fetch a descriptor that turns out to be
13702 unexpected (it used to be in our networkstatus when we started
13703 fetching it, but it isn't in our current networkstatus), and we
13704 aren't using bridges. Bugfix on 0.2.0.x.
13705 - Fix a crash when accessing hidden services: it would work the first
13706 time you use a given introduction point for your service, but
13707 on subsequent requests we'd be using garbage memory. Fixed by
13708 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
13709 - Fix a crash when we load a bridge descriptor from disk but we don't
13710 currently have a Bridge line for it in our torrc. Bugfix on
13714 - If bridge authorities set BridgePassword, they will serve a
13715 snapshot of known bridge routerstatuses from their DirPort to
13716 anybody who knows that password. Unset by default.
13719 - Make the unit tests build again.
13720 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
13721 - Make PublishServerDescriptor default to 1, so the default doesn't
13722 have to change as we invent new directory protocol versions.
13723 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
13724 be included unless sys/time.h is already included. Fixes
13725 bug 553. Bugfix on 0.2.0.x.
13726 - If we receive a general-purpose descriptor and then receive an
13727 identical bridge-purpose descriptor soon after, don't discard
13728 the next one as a duplicate.
13731 - If BridgeRelay is set to 1, then the default for
13732 PublishServerDescriptor is now "bridge" rather than "v2,v3".
13733 - If the user sets RelayBandwidthRate but doesn't set
13734 RelayBandwidthBurst, then make them equal rather than erroring out.
13737 Changes in version 0.2.0.13-alpha - 2007-12-21
13738 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
13739 Goodell, fixes many more bugs, and adds a lot of infrastructure for
13742 o New directory authorities:
13743 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
13747 - Only update guard status (usable / not usable) once we have
13748 enough directory information. This was causing us to always pick
13749 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
13750 causing us to discard all our guards on startup if we hadn't been
13751 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
13752 - Purge old entries from the "rephist" database and the hidden
13753 service descriptor databases even when DirPort is zero. Bugfix
13755 - We were ignoring our RelayBandwidthRate for the first 30 seconds
13756 after opening a circuit -- even a relayed circuit. Bugfix on
13758 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13759 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13760 crashing or mis-answering these types of requests.
13761 - Relays were publishing their server descriptor to v1 and v2
13762 directory authorities, but they didn't try publishing to v3-only
13763 authorities. Fix this; and also stop publishing to v1 authorities.
13765 - When we were reading router descriptors from cache, we were ignoring
13766 the annotations -- so for example we were reading in bridge-purpose
13767 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
13768 - When we decided to send a 503 response to a request for servers, we
13769 were then also sending the server descriptors: this defeats the
13770 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
13773 - Bridge relays now behave like clients with respect to time
13774 intervals for downloading new consensus documents -- otherwise they
13775 stand out. Bridge users now wait until the end of the interval,
13776 so their bridge relay will be sure to have a new consensus document.
13777 - Three new config options (AlternateDirAuthority,
13778 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
13779 user selectively replace the default directory authorities by type,
13780 rather than the all-or-nothing replacement that DirServer offers.
13781 - Tor can now be configured to read a GeoIP file from disk in one
13782 of two formats. This can be used by controllers to map IP addresses
13783 to countries. Eventually, it may support exit-by-country.
13784 - When possible, bridge relays remember which countries users
13785 are coming from, and report aggregate information in their
13786 extra-info documents, so that the bridge authorities can learn
13787 where Tor is blocked.
13788 - Bridge directory authorities now do reachability testing on the
13789 bridges they know. They provide router status summaries to the
13790 controller via "getinfo ns/purpose/bridge", and also dump summaries
13791 to a file periodically.
13792 - Stop fetching directory info so aggressively if your DirPort is
13793 on but your ORPort is off; stop fetching v2 dir info entirely.
13794 You can override these choices with the new FetchDirInfoEarly
13798 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
13799 consensus documents when there are too many relays at a single
13800 IP address. Now clear it in v2 network status documents too, and
13801 also clear it in routerinfo_t when the relay is no longer listed
13802 in the relevant networkstatus document.
13803 - Don't crash if we get an unexpected value for the
13804 PublishServerDescriptor config option. Reported by Matt Edman;
13805 bugfix on 0.2.0.9-alpha.
13806 - Our new v2 hidden service descriptor format allows descriptors
13807 that have no introduction points. But Tor crashed when we tried
13808 to build a descriptor with no intro points (and it would have
13809 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
13810 by Karsten Loesing.
13811 - Fix building with dmalloc 5.5.2 with glibc.
13812 - Reject uploaded descriptors and extrainfo documents if they're
13813 huge. Otherwise we'll cache them all over the network and it'll
13814 clog everything up. Reported by Aljosha Judmayer.
13815 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
13816 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
13817 - When the DANGEROUS_VERSION controller status event told us we're
13818 running an obsolete version, it used the string "OLD" to describe
13819 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
13820 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
13821 - If we can't expand our list of entry guards (e.g. because we're
13822 using bridges or we have StrictEntryNodes set), don't mark relays
13823 down when they fail a directory request. Otherwise we're too quick
13824 to mark all our entry points down. Bugfix on 0.1.2.x.
13825 - Fix handling of hex nicknames when answering controller requests for
13826 networkstatus by name, or when deciding whether to warn about unknown
13827 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
13828 - Fix a couple of hard-to-trigger autoconf problems that could result
13829 in really weird results on platforms whose sys/types.h files define
13830 nonstandard integer types. Bugfix on 0.1.2.x.
13831 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
13832 - Don't crash on name lookup when we have no current consensus. Fixes
13833 bug 538; bugfix on 0.2.0.x.
13834 - Only Tors that want to mirror the v2 directory info should
13835 create the "cached-status" directory in their datadir. (All Tors
13836 used to create it.) Bugfix on 0.2.0.9-alpha.
13837 - Directory authorities should only automatically download Extra Info
13838 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
13841 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
13842 consumers. (We already do this on HUP.)
13843 - Authorities and caches fetch the v2 networkstatus documents
13844 less often, now that v3 is encouraged.
13845 - Add a new config option BridgeRelay that specifies you want to
13846 be a bridge relay. Right now the only difference is that it makes
13847 you answer begin_dir requests, and it makes you cache dir info,
13848 even if your DirPort isn't on.
13849 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
13850 ask about source, timestamp of arrival, purpose, etc. We need
13851 something like this to help Vidalia not do GeoIP lookups on bridge
13853 - Allow multiple HashedControlPassword config lines, to support
13854 multiple controller passwords.
13855 - Authorities now decide whether they're authoritative for a given
13856 router based on the router's purpose.
13857 - New config options AuthDirBadDir and AuthDirListBadDirs for
13858 authorities to mark certain relays as "bad directories" in the
13859 networkstatus documents. Also supports the "!baddir" directive in
13860 the approved-routers file.
13863 Changes in version 0.2.0.12-alpha - 2007-11-16
13864 This twelfth development snapshot fixes some more build problems as
13865 well as a few minor bugs.
13868 - Make it build on OpenBSD again. Patch from tup.
13869 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
13870 package-building for Red Hat, OS X, etc.
13872 o Minor bugfixes (on 0.1.2.x):
13873 - Changing the ExitPolicyRejectPrivate setting should cause us to
13874 rebuild our server descriptor.
13876 o Minor bugfixes (on 0.2.0.x):
13877 - When we're lacking a consensus, don't try to perform rendezvous
13878 operations. Reported by Karsten Loesing.
13879 - Fix a small memory leak whenever we decide against using a
13880 newly picked entry guard. Reported by Mike Perry.
13881 - When authorities detected more than two relays running on the same
13882 IP address, they were clearing all the status flags but forgetting
13883 to clear the "hsdir" flag. So clients were being told that a
13884 given relay was the right choice for a v2 hsdir lookup, yet they
13885 never had its descriptor because it was marked as 'not running'
13887 - If we're trying to fetch a bridge descriptor and there's no way
13888 the bridge authority could help us (for example, we don't know
13889 a digest, or there is no bridge authority), don't be so eager to
13890 fall back to asking the bridge authority.
13891 - If we're using bridges or have strictentrynodes set, and our
13892 chosen exit is in the same family as all our bridges/entry guards,
13893 then be flexible about families.
13896 - When we negotiate a v2 link-layer connection (not yet implemented),
13897 accept RELAY_EARLY cells and turn them into RELAY cells if we've
13898 negotiated a v1 connection for their next step. Initial code for
13902 Changes in version 0.2.0.11-alpha - 2007-11-12
13903 This eleventh development snapshot fixes some build problems with
13904 the previous snapshot. It also includes a more secure-by-default exit
13905 policy for relays, fixes an enormous memory leak for exit relays, and
13906 fixes another bug where servers were falling out of the directory list.
13909 - Exit policies now reject connections that are addressed to a
13910 relay's public (external) IP address too, unless
13911 ExitPolicyRejectPrivate is turned off. We do this because too
13912 many relays are running nearby to services that trust them based
13913 on network address. Bugfix on 0.1.2.x.
13916 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13917 on every successful resolve. Reported by Mike Perry; bugfix
13919 - On authorities, never downgrade to old router descriptors simply
13920 because they're listed in the consensus. This created a catch-22
13921 where we wouldn't list a new descriptor because there was an
13922 old one in the consensus, and we couldn't get the new one in the
13923 consensus because we wouldn't list it. Possible fix for bug 548.
13924 Also, this might cause bug 543 to appear on authorities; if so,
13925 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
13927 o Packaging fixes on 0.2.0.10-alpha:
13928 - We were including instructions about what to do with the
13929 src/config/fallback-consensus file, but we weren't actually
13930 including it in the tarball. Disable all of that for now.
13933 - Allow people to say PreferTunnelledDirConns rather than
13934 PreferTunneledDirConns, for those alternate-spellers out there.
13937 - Don't reevaluate all the information from our consensus document
13938 just because we've downloaded a v2 networkstatus that we intend
13939 to cache. Fixes bug 545; bugfix on 0.2.0.x.
13942 Changes in version 0.2.0.10-alpha - 2007-11-10
13943 This tenth development snapshot adds a third v3 directory authority
13944 run by Mike Perry, adds most of Karsten Loesing's new hidden service
13945 descriptor format, fixes a bad crash bug and new bridge bugs introduced
13946 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
13947 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
13948 addresses many more minor issues.
13950 o New directory authorities:
13951 - Set up ides (run by Mike Perry) as the third v3 directory authority.
13954 - Allow tunnelled directory connections to ask for an encrypted
13955 "begin_dir" connection or an anonymized "uses a full Tor circuit"
13956 connection independently. Now we can make anonymized begin_dir
13957 connections for (e.g.) more secure hidden service posting and
13959 - More progress on proposal 114: code from Karsten Loesing to
13960 implement new hidden service descriptor format.
13961 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
13962 accommodate the growing number of servers that use the default
13963 and are reaching it.
13964 - Directory authorities use a new formula for selecting which nodes
13965 to advertise as Guards: they must be in the top 7/8 in terms of
13966 how long we have known about them, and above the median of those
13967 nodes in terms of weighted fractional uptime.
13968 - Make "not enough dir info yet" warnings describe *why* Tor feels
13969 it doesn't have enough directory info yet.
13972 - Stop servers from crashing if they set a Family option (or
13973 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
13975 - Make bridge users work again -- the move to v3 directories in
13976 0.2.0.9-alpha had introduced a number of bugs that made bridges
13977 no longer work for clients.
13978 - When the clock jumps forward a lot, do not allow the bandwidth
13979 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
13981 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
13982 - When the consensus lists a router descriptor that we previously were
13983 mirroring, but that we considered non-canonical, reload the
13984 descriptor as canonical. This fixes bug 543 where Tor servers
13985 would start complaining after a few days that they don't have
13986 enough directory information to build a circuit.
13987 - Consider replacing the current consensus when certificates arrive
13988 that make the pending consensus valid. Previously, we were only
13989 considering replacement when the new certs _didn't_ help.
13990 - Fix an assert error on startup if we didn't already have the
13991 consensus and certs cached in our datadirectory: we were caching
13992 the consensus in consensus_waiting_for_certs but then free'ing it
13994 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
13995 Request) if we need more v3 certs but we've already got pending
13996 requests for all of them.
13997 - Correctly back off from failing certificate downloads. Fixes
13999 - Authorities don't vote on the Running flag if they have been running
14000 for less than 30 minutes themselves. Fixes bug 547, where a newly
14001 started authority would vote that everyone was down.
14003 o New requirements:
14004 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
14005 it, it had no AES, and it hasn't seen any security patches since
14009 - Clients now hold circuitless TLS connections open for 1.5 times
14010 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14011 rebuild a new circuit over them within that timeframe. Previously,
14012 they held them open only for KeepalivePeriod (5 minutes).
14013 - Use "If-Modified-Since" to avoid retrieving consensus
14014 networkstatuses that we already have.
14015 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14016 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14017 we start knowing some directory caches.
14018 - When we receive a consensus from the future, warn about skew.
14019 - Improve skew reporting: try to give the user a better log message
14020 about how skewed they are, and how much this matters.
14021 - When we have a certificate for an authority, believe that
14022 certificate's claims about the authority's IP address.
14023 - New --quiet command-line option to suppress the default console log.
14024 Good in combination with --hash-password.
14025 - Authorities send back an X-Descriptor-Not-New header in response to
14026 an accepted-but-discarded descriptor upload. Partially implements
14028 - Make the log message for "tls error. breaking." more useful.
14029 - Better log messages about certificate downloads, to attempt to
14030 track down the second incarnation of bug 546.
14032 o Minor features (bridges):
14033 - If bridge users set UpdateBridgesFromAuthority, but the digest
14034 they ask for is a 404 from the bridge authority, they now fall
14035 back to trying the bridge directly.
14036 - Bridges now use begin_dir to publish their server descriptor to
14037 the bridge authority, even when they haven't set TunnelDirConns.
14039 o Minor features (controller):
14040 - When reporting clock skew, and we know that the clock is _at least
14041 as skewed_ as some value, but we don't know the actual value,
14042 report the value as a "minimum skew."
14045 - Update linux-tor-prio.sh script to allow QoS based on the uid of
14046 the Tor process. Patch from Marco Bonetti with tweaks from Mike
14050 - Refuse to start if both ORPort and UseBridges are set. Bugfix
14051 on 0.2.0.x, suggested by Matt Edman.
14052 - Don't stop fetching descriptors when FetchUselessDescriptors is
14053 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
14054 reported by tup and ioerror.
14055 - Better log message on vote from unknown authority.
14056 - Don't log "Launching 0 request for 0 router" message.
14058 o Minor bugfixes (memory leaks):
14059 - Stop leaking memory every time we parse a v3 certificate. Bugfix
14061 - Stop leaking memory every time we load a v3 certificate. Bugfix
14062 on 0.2.0.1-alpha. Fixes bug 536.
14063 - Stop leaking a cached networkstatus on exit. Bugfix on
14065 - Stop leaking voter information every time we free a consensus.
14066 Bugfix on 0.2.0.3-alpha.
14067 - Stop leaking signed data every time we check a voter signature.
14068 Bugfix on 0.2.0.3-alpha.
14069 - Stop leaking a signature every time we fail to parse a consensus or
14070 a vote. Bugfix on 0.2.0.3-alpha.
14071 - Stop leaking v2_download_status_map on shutdown. Bugfix on
14073 - Stop leaking conn->nickname every time we make a connection to a
14074 Tor relay without knowing its expected identity digest (e.g. when
14075 using bridges). Bugfix on 0.2.0.3-alpha.
14077 - Minor bugfixes (portability):
14078 - Run correctly on platforms where rlim_t is larger than unsigned
14079 long, and/or where the real limit for number of open files is
14080 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
14081 particular, these may be needed for OS X 10.5.
14084 Changes in version 0.1.2.18 - 2007-10-28
14085 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
14086 hidden service introduction that were causing huge delays, and a big
14087 bug that was causing some servers to disappear from the network status
14088 lists for a few hours each day.
14090 o Major bugfixes (crashes):
14091 - If a connection is shut down abruptly because of something that
14092 happened inside connection_flushed_some(), do not call
14093 connection_finished_flushing(). Should fix bug 451:
14094 "connection_stop_writing: Assertion conn->write_event failed"
14095 Bugfix on 0.1.2.7-alpha.
14096 - Fix possible segfaults in functions called from
14097 rend_process_relay_cell().
14099 o Major bugfixes (hidden services):
14100 - Hidden services were choosing introduction points uniquely by
14101 hexdigest, but when constructing the hidden service descriptor
14102 they merely wrote the (potentially ambiguous) nickname.
14103 - Clients now use the v2 intro format for hidden service
14104 connections: they specify their chosen rendezvous point by identity
14105 digest rather than by (potentially ambiguous) nickname. These
14106 changes could speed up hidden service connections dramatically.
14108 o Major bugfixes (other):
14109 - Stop publishing a new server descriptor just because we get a
14110 HUP signal. This led (in a roundabout way) to some servers getting
14111 dropped from the networkstatus lists for a few hours each day.
14112 - When looking for a circuit to cannibalize, consider family as well
14113 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14114 circuit cannibalization).
14115 - When a router wasn't listed in a new networkstatus, we were leaving
14116 the flags for that router alone -- meaning it remained Named,
14117 Running, etc -- even though absence from the networkstatus means
14118 that it shouldn't be considered to exist at all anymore. Now we
14119 clear all the flags for routers that fall out of the networkstatus
14120 consensus. Fixes bug 529.
14123 - Don't try to access (or alter) the state file when running
14124 --list-fingerprint or --verify-config or --hash-password. Resolves
14126 - When generating information telling us how to extend to a given
14127 router, do not try to include the nickname if it is
14128 absent. Resolves bug 467.
14129 - Fix a user-triggerable segfault in expand_filename(). (There isn't
14130 a way to trigger this remotely.)
14131 - When sending a status event to the controller telling it that an
14132 OR address is reachable, set the port correctly. (Previously we
14133 were reporting the dir port.)
14134 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14135 command. Bugfix on 0.1.2.17.
14136 - When loading bandwidth history, do not believe any information in
14137 the future. Fixes bug 434.
14138 - When loading entry guard information, do not believe any information
14140 - When we have our clock set far in the future and generate an
14141 onion key, then re-set our clock to be correct, we should not stop
14142 the onion key from getting rotated.
14143 - On some platforms, accept() can return a broken address. Detect
14144 this more quietly, and deal accordingly. Fixes bug 483.
14145 - It's not actually an error to find a non-pending entry in the DNS
14146 cache when canceling a pending resolve. Don't log unless stuff
14147 is fishy. Resolves bug 463.
14148 - Don't reset trusted dir server list when we set a configuration
14149 option. Patch from Robert Hogan.
14150 - Don't try to create the datadir when running --verify-config or
14151 --hash-password. Resolves bug 540.
14154 Changes in version 0.2.0.9-alpha - 2007-10-24
14155 This ninth development snapshot switches clients to the new v3 directory
14156 system; allows servers to be listed in the network status even when they
14157 have the same nickname as a registered server; and fixes many other
14158 bugs including a big one that was causing some servers to disappear
14159 from the network status lists for a few hours each day.
14161 o Major features (directory system):
14162 - Clients now download v3 consensus networkstatus documents instead
14163 of v2 networkstatus documents. Clients and caches now base their
14164 opinions about routers on these consensus documents. Clients only
14165 download router descriptors listed in the consensus.
14166 - Authorities now list servers who have the same nickname as
14167 a different named server, but list them with a new flag,
14168 "Unnamed". Now we can list servers that happen to pick the same
14169 nickname as a server that registered two years ago and then
14170 disappeared. Partially implements proposal 122.
14171 - If the consensus lists a router as "Unnamed", the name is assigned
14172 to a different router: do not identify the router by that name.
14173 Partially implements proposal 122.
14174 - Authorities can now come to a consensus on which method to use to
14175 compute the consensus. This gives us forward compatibility.
14178 - Stop publishing a new server descriptor just because we HUP or
14179 when we find our DirPort to be reachable but won't actually publish
14180 it. New descriptors without any real changes are dropped by the
14181 authorities, and can screw up our "publish every 18 hours" schedule.
14183 - When a router wasn't listed in a new networkstatus, we were leaving
14184 the flags for that router alone -- meaning it remained Named,
14185 Running, etc -- even though absence from the networkstatus means
14186 that it shouldn't be considered to exist at all anymore. Now we
14187 clear all the flags for routers that fall out of the networkstatus
14188 consensus. Fixes bug 529; bugfix on 0.1.2.x.
14189 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
14190 extrainfo documents and then discard them immediately for not
14191 matching the latest router. Bugfix on 0.2.0.1-alpha.
14193 o Minor features (v3 directory protocol):
14194 - Allow tor-gencert to generate a new certificate without replacing
14196 - Allow certificates to include an address.
14197 - When we change our directory-cache settings, reschedule all voting
14198 and download operations.
14199 - Reattempt certificate downloads immediately on failure, as long as
14200 we haven't failed a threshold number of times yet.
14201 - Delay retrying consensus downloads while we're downloading
14202 certificates to verify the one we just got. Also, count getting a
14203 consensus that we already have (or one that isn't valid) as a failure,
14204 and count failing to get the certificates after 20 minutes as a
14206 - Build circuits and download descriptors even if our consensus is a
14207 little expired. (This feature will go away once authorities are
14210 o Minor features (router descriptor cache):
14211 - If we find a cached-routers file that's been sitting around for more
14212 than 28 days unmodified, then most likely it's a leftover from
14213 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
14215 - When we (as a cache) download a descriptor because it was listed
14216 in a consensus, remember when the consensus was supposed to expire,
14217 and don't expire the descriptor until then.
14219 o Minor features (performance):
14220 - Call routerlist_remove_old_routers() much less often. This should
14221 speed startup, especially on directory caches.
14222 - Don't try to launch new descriptor downloads quite so often when we
14223 already have enough directory information to build circuits.
14224 - Base64 decoding was actually showing up on our profile when parsing
14225 the initial descriptor file; switch to an in-process all-at-once
14226 implementation that's about 3.5x times faster than calling out to
14229 o Minor features (compilation):
14230 - Detect non-ASCII platforms (if any still exist) and refuse to
14231 build there: some of our code assumes that 'A' is 65 and so on.
14233 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
14234 - Make the "next period" votes into "current period" votes immediately
14235 after publishing the consensus; avoid a heisenbug that made them
14236 stick around indefinitely.
14237 - When we discard a vote as a duplicate, do not report this as
14239 - Treat missing v3 keys or certificates as an error when running as a
14240 v3 directory authority.
14241 - When we're configured to be a v3 authority, but we're only listed
14242 as a non-v3 authority in our DirServer line for ourself, correct
14244 - If an authority doesn't have a qualified hostname, just put
14245 its address in the vote. This fixes the problem where we referred to
14246 "moria on moria:9031."
14247 - Distinguish between detached signatures for the wrong period, and
14248 detached signatures for a divergent vote.
14249 - Fix a small memory leak when computing a consensus.
14250 - When there's no concensus, we were forming a vote every 30
14251 minutes, but writing the "valid-after" line in our vote based
14252 on our configured V3AuthVotingInterval: so unless the intervals
14253 matched up, we immediately rejected our own vote because it didn't
14254 start at the voting interval that caused us to construct a vote.
14256 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
14257 - Delete unverified-consensus when the real consensus is set.
14258 - Consider retrying a consensus networkstatus fetch immediately
14259 after one fails: don't wait 60 seconds to notice.
14260 - When fetching a consensus as a cache, wait until a newer consensus
14261 should exist before trying to replace the current one.
14262 - Use a more forgiving schedule for retrying failed consensus
14263 downloads than for other types.
14265 o Minor bugfixes (other directory issues):
14266 - Correct the implementation of "download votes by digest." Bugfix on
14268 - Authorities no longer send back "400 you're unreachable please fix
14269 it" errors to Tor servers that aren't online all the time. We're
14270 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
14272 o Minor bugfixes (controller):
14273 - Don't reset trusted dir server list when we set a configuration
14274 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
14275 - Respond to INT and TERM SIGNAL commands before we execute the
14276 signal, in case the signal shuts us down. We had a patch in
14277 0.1.2.1-alpha that tried to do this by queueing the response on
14278 the connection's buffer before shutting down, but that really
14279 isn't the same thing at all. Bug located by Matt Edman.
14281 o Minor bugfixes (misc):
14282 - Correctly check for bad options to the "PublishServerDescriptor"
14283 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
14284 - Stop leaking memory on failing case of base32_decode, and make
14285 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
14286 - Don't try to download extrainfo documents when we're trying to
14287 fetch enough directory info to build a circuit: having enough
14288 info should get priority. Bugfix on 0.2.0.x.
14289 - Don't complain that "your server has not managed to confirm that its
14290 ports are reachable" if we haven't been able to build any circuits
14291 yet. Bug found by spending four hours without a v3 consensus. Bugfix
14293 - Detect the reason for failing to mmap a descriptor file we just
14294 wrote, and give a more useful log message. Fixes bug 533. Bugfix
14297 o Code simplifications and refactoring:
14298 - Remove support for the old bw_accounting file: we've been storing
14299 bandwidth accounting information in the state file since
14300 0.1.2.5-alpha. This may result in bandwidth accounting errors
14301 if you try to upgrade from 0.1.1.x or earlier, or if you try to
14302 downgrade to 0.1.1.x or earlier.
14303 - New convenience code to locate a file within the DataDirectory.
14304 - Move non-authority functionality out of dirvote.c.
14305 - Refactor the arguments for router_pick_{directory_|trusteddir}server
14306 so that they all take the same named flags.
14309 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
14310 Unix users an easy way to script their Tor process (e.g. by
14311 adjusting bandwidth based on the time of the day).
14314 Changes in version 0.2.0.8-alpha - 2007-10-12
14315 This eighth development snapshot fixes a crash bug that's been bothering
14316 us since February 2007, lets bridge authorities store a list of bridge
14317 descriptors they've seen, gets v3 directory voting closer to working,
14318 starts caching v3 directory consensus documents on directory mirrors,
14319 and fixes a variety of smaller issues including some minor memory leaks.
14321 o Major features (router descriptor cache):
14322 - Store routers in a file called cached-descriptors instead of in
14323 cached-routers. Initialize cached-descriptors from cached-routers
14324 if the old format is around. The new format allows us to store
14325 annotations along with descriptors.
14326 - Use annotations to record the time we received each descriptor, its
14327 source, and its purpose.
14328 - Disable the SETROUTERPURPOSE controller command: it is now
14330 - Controllers should now specify cache=no or cache=yes when using
14331 the +POSTDESCRIPTOR command.
14332 - Bridge authorities now write bridge descriptors to disk, meaning
14333 we can export them to other programs and begin distributing them
14336 o Major features (directory authorities):
14337 - When a v3 authority is missing votes or signatures, it now tries
14339 - Directory authorities track weighted fractional uptime as well as
14340 weighted mean-time-between failures. WFU is suitable for deciding
14341 whether a node is "usually up", while MTBF is suitable for deciding
14342 whether a node is "likely to stay up." We need both, because
14343 "usually up" is a good requirement for guards, while "likely to
14344 stay up" is a good requirement for long-lived connections.
14346 o Major features (v3 directory system):
14347 - Caches now download v3 network status documents as needed,
14348 and download the descriptors listed in them.
14349 - All hosts now attempt to download and keep fresh v3 authority
14350 certificates, and re-attempt after failures.
14351 - More internal-consistency checks for vote parsing.
14353 o Major bugfixes (crashes):
14354 - If a connection is shut down abruptly because of something that
14355 happened inside connection_flushed_some(), do not call
14356 connection_finished_flushing(). Should fix bug 451. Bugfix on
14359 o Major bugfixes (performance):
14360 - Fix really bad O(n^2) performance when parsing a long list of
14361 routers: Instead of searching the entire list for an "extra-info "
14362 string which usually wasn't there, once for every routerinfo
14363 we read, just scan lines forward until we find one we like.
14365 - When we add data to a write buffer in response to the data on that
14366 write buffer getting low because of a flush, do not consider the
14367 newly added data as a candidate for immediate flushing, but rather
14368 make it wait until the next round of writing. Otherwise, we flush
14369 and refill recursively, and a single greedy TLS connection can
14370 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
14372 o Minor features (v3 authority system):
14373 - Add more ways for tools to download the votes that lead to the
14375 - Send a 503 when low on bandwidth and a vote, consensus, or
14376 certificate is requested.
14377 - If-modified-since is now implemented properly for all kinds of
14378 certificate requests.
14380 o Minor bugfixes (network statuses):
14381 - Tweak the implementation of proposal 109 slightly: allow at most
14382 two Tor servers on the same IP address, except if it's the location
14383 of a directory authority, in which case allow five. Bugfix on
14386 o Minor bugfixes (controller):
14387 - When sending a status event to the controller telling it that an
14388 OR address is reachable, set the port correctly. (Previously we
14389 were reporting the dir port.) Bugfix on 0.1.2.x.
14391 o Minor bugfixes (v3 directory system):
14392 - Fix logic to look up a cert by its signing key digest. Bugfix on
14394 - Only change the reply to a vote to "OK" if it's not already
14395 set. This gets rid of annoying "400 OK" log messages, which may
14396 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
14397 - When we get a valid consensus, recompute the voting schedule.
14398 - Base the valid-after time of a vote on the consensus voting
14399 schedule, not on our preferred schedule.
14400 - Make the return values and messages from signature uploads and
14401 downloads more sensible.
14402 - Fix a memory leak when serving votes and consensus documents, and
14403 another when serving certificates.
14405 o Minor bugfixes (performance):
14406 - Use a slightly simpler string hashing algorithm (copying Python's
14407 instead of Java's) and optimize our digest hashing algorithm to take
14408 advantage of 64-bit platforms and to remove some possibly-costly
14410 - Fix a minor memory leak whenever we parse guards from our state
14411 file. Bugfix on 0.2.0.7-alpha.
14412 - Fix a minor memory leak whenever we write out a file. Bugfix on
14414 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14415 command. Bugfix on 0.2.0.5-alpha.
14417 o Minor bugfixes (portability):
14418 - On some platforms, accept() can return a broken address. Detect
14419 this more quietly, and deal accordingly. Fixes bug 483.
14420 - Stop calling tor_strlower() on uninitialized memory in some cases.
14421 Bugfix in 0.2.0.7-alpha.
14423 o Minor bugfixes (usability):
14424 - Treat some 403 responses from directory servers as INFO rather than
14425 WARN-severity events.
14426 - It's not actually an error to find a non-pending entry in the DNS
14427 cache when canceling a pending resolve. Don't log unless stuff is
14428 fishy. Resolves bug 463.
14430 o Minor bugfixes (anonymity):
14431 - Never report that we've used more bandwidth than we're willing to
14432 relay: it leaks how much non-relay traffic we're using. Resolves
14434 - When looking for a circuit to cannibalize, consider family as well
14435 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14436 circuit cannibalization).
14438 o Code simplifications and refactoring:
14439 - Make a bunch of functions static. Remove some dead code.
14440 - Pull out about a third of the really big routerlist.c; put it in a
14441 new module, networkstatus.c.
14442 - Merge the extra fields in local_routerstatus_t back into
14443 routerstatus_t: we used to need one routerstatus_t for each
14444 authority's opinion, plus a local_routerstatus_t for the locally
14445 computed consensus opinion. To save space, we put the locally
14446 modified fields into local_routerstatus_t, and only the common
14447 stuff into routerstatus_t. But once v3 directories are in use,
14448 clients and caches will no longer need to hold authority opinions;
14449 thus, the rationale for keeping the types separate is now gone.
14450 - Make the code used to reschedule and reattempt downloads more
14452 - Turn all 'Are we a directory server/mirror?' logic into a call to
14454 - Remove the code to generate the oldest (v1) directory format.
14455 The code has been disabled since 0.2.0.5-alpha.
14458 Changes in version 0.2.0.7-alpha - 2007-09-21
14459 This seventh development snapshot makes bridges work again, makes bridge
14460 authorities work for the first time, fixes two huge performance flaws
14461 in hidden services, and fixes a variety of minor issues.
14463 o New directory authorities:
14464 - Set up moria1 and tor26 as the first v3 directory authorities. See
14465 doc/spec/dir-spec.txt for details on the new directory design.
14467 o Major bugfixes (crashes):
14468 - Fix possible segfaults in functions called from
14469 rend_process_relay_cell(). Bugfix on 0.1.2.x.
14471 o Major bugfixes (bridges):
14472 - Fix a bug that made servers send a "404 Not found" in response to
14473 attempts to fetch their server descriptor. This caused Tor servers
14474 to take many minutes to establish reachability for their DirPort,
14475 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
14476 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
14477 users configure that and specify a bridge with an identity
14478 fingerprint, now they will lookup the bridge descriptor at the
14479 default bridge authority via a one-hop tunnel, but once circuits
14480 are established they will switch to a three-hop tunnel for later
14481 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
14483 o Major bugfixes (hidden services):
14484 - Hidden services were choosing introduction points uniquely by
14485 hexdigest, but when constructing the hidden service descriptor
14486 they merely wrote the (potentially ambiguous) nickname.
14487 - Clients now use the v2 intro format for hidden service
14488 connections: they specify their chosen rendezvous point by identity
14489 digest rather than by (potentially ambiguous) nickname. Both
14490 are bugfixes on 0.1.2.x, and they could speed up hidden service
14491 connections dramatically. Thanks to Karsten Loesing.
14493 o Minor features (security):
14494 - As a client, do not believe any server that tells us that an
14495 address maps to an internal address space.
14496 - Make it possible to enable HashedControlPassword and
14497 CookieAuthentication at the same time.
14499 o Minor features (guard nodes):
14500 - Tag every guard node in our state file with the version that
14501 we believe added it, or with our own version if we add it. This way,
14502 if a user temporarily runs an old version of Tor and then switches
14503 back to a new one, she doesn't automatically lose her guards.
14505 o Minor features (speed):
14506 - When implementing AES counter mode, update only the portions of the
14507 counter buffer that need to change, and don't keep separate
14508 network-order and host-order counters when they are the same (i.e.,
14509 on big-endian hosts.)
14511 o Minor features (controller):
14512 - Accept LF instead of CRLF on controller, since some software has a
14513 hard time generating real Internet newlines.
14514 - Add GETINFO values for the server status events
14515 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
14518 o Removed features:
14519 - Routers no longer include bandwidth-history lines in their
14520 descriptors; this information is already available in extra-info
14521 documents, and including it in router descriptors took up 60%
14522 (!) of compressed router descriptor downloads. Completes
14523 implementation of proposal 104.
14524 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
14525 and TorControl.py, as they use the old v0 controller protocol,
14526 and are obsoleted by TorFlow anyway.
14527 - Drop support for v1 rendezvous descriptors, since we never used
14528 them anyway, and the code has probably rotted by now. Based on
14529 patch from Karsten Loesing.
14530 - On OSX, stop warning the user that kqueue support in libevent is
14531 "experimental", since it seems to have worked fine for ages.
14534 - When generating information telling us how to extend to a given
14535 router, do not try to include the nickname if it is absent. Fixes
14536 bug 467. Bugfix on 0.2.0.3-alpha.
14537 - Fix a user-triggerable (but not remotely-triggerable) segfault
14538 in expand_filename(). Bugfix on 0.1.2.x.
14539 - Fix a memory leak when freeing incomplete requests from DNSPort.
14540 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
14541 - Don't try to access (or alter) the state file when running
14542 --list-fingerprint or --verify-config or --hash-password. (Resolves
14543 bug 499.) Bugfix on 0.1.2.x.
14544 - Servers used to decline to publish their DirPort if their
14545 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
14546 were below a threshold. Now they only look at BandwidthRate and
14547 RelayBandwidthRate. Bugfix on 0.1.2.x.
14548 - Remove an optimization in the AES counter-mode code that assumed
14549 that the counter never exceeded 2^68. When the counter can be set
14550 arbitrarily as an IV (as it is by Karsten's new hidden services
14551 code), this assumption no longer holds. Bugfix on 0.1.2.x.
14552 - Resume listing "AUTHORITY" flag for authorities in network status.
14553 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
14555 o Code simplifications and refactoring:
14556 - Revamp file-writing logic so we don't need to have the entire
14557 contents of a file in memory at once before we write to disk. Tor,
14559 - Turn "descriptor store" into a full-fledged type.
14560 - Move all NT services code into a separate source file.
14561 - Unify all code that computes medians, percentile elements, etc.
14562 - Get rid of a needless malloc when parsing address policies.
14565 Changes in version 0.1.2.17 - 2007-08-30
14566 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
14567 X bundles. Vidalia 0.0.14 makes authentication required for the
14568 ControlPort in the default configuration, which addresses important
14569 security risks. Everybody who uses Vidalia (or another controller)
14572 In addition, this Tor update fixes major load balancing problems with
14573 path selection, which should speed things up a lot once many people
14576 o Major bugfixes (security):
14577 - We removed support for the old (v0) control protocol. It has been
14578 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
14579 become more of a headache than it's worth.
14581 o Major bugfixes (load balancing):
14582 - When choosing nodes for non-guard positions, weight guards
14583 proportionally less, since they already have enough load. Patch
14585 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14586 will allow fast Tor servers to get more attention.
14587 - When we're upgrading from an old Tor version, forget our current
14588 guards and pick new ones according to the new weightings. These
14589 three load balancing patches could raise effective network capacity
14590 by a factor of four. Thanks to Mike Perry for measurements.
14592 o Major bugfixes (stream expiration):
14593 - Expire not-yet-successful application streams in all cases if
14594 they've been around longer than SocksTimeout. Right now there are
14595 some cases where the stream will live forever, demanding a new
14596 circuit every 15 seconds. Fixes bug 454; reported by lodger.
14598 o Minor features (controller):
14599 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14600 is valid before any authentication has been received. It tells
14601 a controller what kind of authentication is expected, and what
14602 protocol is spoken. Implements proposal 119.
14604 o Minor bugfixes (performance):
14605 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
14606 greatly speeding up loading cached-routers from disk on startup.
14607 - Disable sentinel-based debugging for buffer code: we squashed all
14608 the bugs that this was supposed to detect a long time ago, and now
14609 its only effect is to change our buffer sizes from nice powers of
14610 two (which platform mallocs tend to like) to values slightly over
14611 powers of two (which make some platform mallocs sad).
14613 o Minor bugfixes (misc):
14614 - If exit bandwidth ever exceeds one third of total bandwidth, then
14615 use the correct formula to weight exit nodes when choosing paths.
14616 Based on patch from Mike Perry.
14617 - Choose perfectly fairly among routers when choosing by bandwidth and
14618 weighting by fraction of bandwidth provided by exits. Previously, we
14619 would choose with only approximate fairness, and correct ourselves
14620 if we ran off the end of the list.
14621 - If we require CookieAuthentication but we fail to write the
14622 cookie file, we would warn but not exit, and end up in a state
14623 where no controller could authenticate. Now we exit.
14624 - If we require CookieAuthentication, stop generating a new cookie
14625 every time we change any piece of our config.
14626 - Refuse to start with certain directory authority keys, and
14627 encourage people using them to stop.
14628 - Terminate multi-line control events properly. Original patch
14630 - Fix a minor memory leak when we fail to find enough suitable
14631 servers to choose a circuit.
14632 - Stop leaking part of the descriptor when we run into a particularly
14633 unparseable piece of it.
14636 Changes in version 0.2.0.6-alpha - 2007-08-26
14637 This sixth development snapshot features a new Vidalia version in the
14638 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
14639 the ControlPort in the default configuration, which addresses important
14642 In addition, this snapshot fixes major load balancing problems
14643 with path selection, which should speed things up a lot once many
14644 people have upgraded. The directory authorities also use a new
14645 mean-time-between-failure approach to tracking which servers are stable,
14646 rather than just looking at the most recent uptime.
14648 o New directory authorities:
14649 - Set up Tonga as the default bridge directory authority.
14652 - Directory authorities now track servers by weighted
14653 mean-times-between-failures. When we have 4 or more days of data,
14654 use measured MTBF rather than declared uptime to decide whether
14655 to call a router Stable. Implements proposal 108.
14657 o Major bugfixes (load balancing):
14658 - When choosing nodes for non-guard positions, weight guards
14659 proportionally less, since they already have enough load. Patch
14661 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14662 will allow fast Tor servers to get more attention.
14663 - When we're upgrading from an old Tor version, forget our current
14664 guards and pick new ones according to the new weightings. These
14665 three load balancing patches could raise effective network capacity
14666 by a factor of four. Thanks to Mike Perry for measurements.
14668 o Major bugfixes (descriptor parsing):
14669 - Handle unexpected whitespace better in malformed descriptors. Bug
14670 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
14673 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14674 GETINFO for Torstat to use until it can switch to using extrainfos.
14675 - Optionally (if built with -DEXPORTMALLINFO) export the output
14676 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14680 - Do not intermix bridge routers with controller-added
14681 routers. (Bugfix on 0.2.0.x)
14682 - Do not fail with an assert when accept() returns an unexpected
14683 address family. Addresses but does not wholly fix bug 483. (Bugfix
14685 - Let directory authorities startup even when they can't generate
14686 a descriptor immediately, e.g. because they don't know their
14688 - Stop putting the authentication cookie in a file called "0"
14689 in your working directory if you don't specify anything for the
14690 new CookieAuthFile option. Reported by Matt Edman.
14691 - Make it possible to read the PROTOCOLINFO response in a way that
14692 conforms to our control-spec. Reported by Matt Edman.
14693 - Fix a minor memory leak when we fail to find enough suitable
14694 servers to choose a circuit. Bugfix on 0.1.2.x.
14695 - Stop leaking part of the descriptor when we run into a particularly
14696 unparseable piece of it. Bugfix on 0.1.2.x.
14697 - Unmap the extrainfo cache file on exit.
14700 Changes in version 0.2.0.5-alpha - 2007-08-19
14701 This fifth development snapshot fixes compilation on Windows again;
14702 fixes an obnoxious client-side bug that slowed things down and put
14703 extra load on the network; gets us closer to using the v3 directory
14704 voting scheme; makes it easier for Tor controllers to use cookie-based
14705 authentication; and fixes a variety of other bugs.
14707 o Removed features:
14708 - Version 1 directories are no longer generated in full. Instead,
14709 authorities generate and serve "stub" v1 directories that list
14710 no servers. This will stop Tor versions 0.1.0.x and earlier from
14711 working, but (for security reasons) nobody should be running those
14714 o Major bugfixes (compilation, 0.2.0.x):
14715 - Try to fix Win32 compilation again: improve checking for IPv6 types.
14716 - Try to fix MSVC compilation: build correctly on platforms that do
14717 not define s6_addr16 or s6_addr32.
14718 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
14721 o Major bugfixes (stream expiration):
14722 - Expire not-yet-successful application streams in all cases if
14723 they've been around longer than SocksTimeout. Right now there are
14724 some cases where the stream will live forever, demanding a new
14725 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
14726 reported by lodger.
14728 o Minor features (directory servers):
14729 - When somebody requests a list of statuses or servers, and we have
14730 none of those, return a 404 rather than an empty 200.
14732 o Minor features (directory voting):
14733 - Store v3 consensus status consensuses on disk, and reload them
14736 o Minor features (security):
14737 - Warn about unsafe ControlPort configurations.
14738 - Refuse to start with certain directory authority keys, and
14739 encourage people using them to stop.
14741 o Minor features (controller):
14742 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14743 is valid before any authentication has been received. It tells
14744 a controller what kind of authentication is expected, and what
14745 protocol is spoken. Implements proposal 119.
14746 - New config option CookieAuthFile to choose a new location for the
14747 cookie authentication file, and config option
14748 CookieAuthFileGroupReadable to make it group-readable.
14750 o Minor features (unit testing):
14751 - Add command-line arguments to unit-test executable so that we can
14752 invoke any chosen test from the command line rather than having
14753 to run the whole test suite at once; and so that we can turn on
14754 logging for the unit tests.
14756 o Minor bugfixes (on 0.1.2.x):
14757 - If we require CookieAuthentication but we fail to write the
14758 cookie file, we would warn but not exit, and end up in a state
14759 where no controller could authenticate. Now we exit.
14760 - If we require CookieAuthentication, stop generating a new cookie
14761 every time we change any piece of our config.
14762 - When loading bandwidth history, do not believe any information in
14763 the future. Fixes bug 434.
14764 - When loading entry guard information, do not believe any information
14766 - When we have our clock set far in the future and generate an
14767 onion key, then re-set our clock to be correct, we should not stop
14768 the onion key from getting rotated.
14769 - Clean up torrc sample config file.
14770 - Do not automatically run configure from autogen.sh. This
14771 non-standard behavior tended to annoy people who have built other
14774 o Minor bugfixes (on 0.2.0.x):
14775 - Fix a bug with AutomapHostsOnResolve that would always cause
14776 the second request to fail. Bug reported by Kate. Bugfix on
14778 - Fix a bug in ADDRMAP controller replies that would sometimes
14779 try to print a NULL. Patch from tup.
14780 - Read v3 directory authority keys from the right location.
14781 - Numerous bugfixes to directory voting code.
14784 Changes in version 0.1.2.16 - 2007-08-01
14785 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
14786 remote attacker in certain situations to rewrite the user's torrc
14787 configuration file. This can completely compromise anonymity of users
14788 in most configurations, including those running the Vidalia bundles,
14789 TorK, etc. Or worse.
14791 o Major security fixes:
14792 - Close immediately after missing authentication on control port;
14793 do not allow multiple authentication attempts.
14796 Changes in version 0.2.0.4-alpha - 2007-08-01
14797 This fourth development snapshot fixes a critical security vulnerability
14798 for most users, specifically those running Vidalia, TorK, etc. Everybody
14799 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
14801 o Major security fixes:
14802 - Close immediately after missing authentication on control port;
14803 do not allow multiple authentication attempts.
14805 o Major bugfixes (compilation):
14806 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
14809 o Minor features (performance):
14810 - Be even more aggressive about releasing RAM from small
14811 empty buffers. Thanks to our free-list code, this shouldn't be too
14812 performance-intensive.
14813 - Disable sentinel-based debugging for buffer code: we squashed all
14814 the bugs that this was supposed to detect a long time ago, and
14815 now its only effect is to change our buffer sizes from nice
14816 powers of two (which platform mallocs tend to like) to values
14817 slightly over powers of two (which make some platform mallocs sad).
14818 - Log malloc statistics from mallinfo() on platforms where it
14822 Changes in version 0.2.0.3-alpha - 2007-07-29
14823 This third development snapshot introduces new experimental
14824 blocking-resistance features and a preliminary version of the v3
14825 directory voting design, and includes many other smaller features
14829 - The first pieces of our "bridge" design for blocking-resistance
14830 are implemented. People can run bridge directory authorities;
14831 people can run bridges; and people can configure their Tor clients
14832 with a set of bridges to use as the first hop into the Tor network.
14833 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
14835 - Create listener connections before we setuid to the configured
14836 User and Group. Now non-Windows users can choose port values
14837 under 1024, start Tor as root, and have Tor bind those ports
14838 before it changes to another UID. (Windows users could already
14840 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14841 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14842 on "vserver" accounts. (Patch from coderman.)
14843 - Be even more aggressive about separating local traffic from relayed
14844 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
14846 o Major features (experimental):
14847 - First cut of code for "v3 dir voting": directory authorities will
14848 vote on a common network status document rather than each publishing
14849 their own opinion. This code needs more testing and more corner-case
14850 handling before it's ready for use.
14853 - Directory authorities now call routers Fast if their bandwidth is
14854 at least 100KB/s, and consider their bandwidth adequate to be a
14855 Guard if it is at least 250KB/s, no matter the medians. This fix
14856 complements proposal 107. [Bugfix on 0.1.2.x]
14857 - Directory authorities now never mark more than 3 servers per IP as
14858 Valid and Running. (Implements proposal 109, by Kevin Bauer and
14860 - Minor change to organizationName and commonName generation
14861 procedures in TLS certificates during Tor handshakes, to invalidate
14862 some earlier censorware approaches. This is not a long-term
14863 solution, but applying it will give us a bit of time to look into
14864 the epidemiology of countermeasures as they spread.
14866 o Major bugfixes (directory):
14867 - Rewrite directory tokenization code to never run off the end of
14868 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
14870 o Minor features (controller):
14871 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
14872 match requests to applications. (Patch from Robert Hogan.)
14873 - Report address and port correctly on connections to DNSPort. (Patch
14874 from Robert Hogan.)
14875 - Add a RESOLVE command to launch hostname lookups. (Original patch
14876 from Robert Hogan.)
14877 - Add GETINFO status/enough-dir-info to let controllers tell whether
14878 Tor has downloaded sufficient directory information. (Patch
14880 - You can now use the ControlSocket option to tell Tor to listen for
14881 controller connections on Unix domain sockets on systems that
14882 support them. (Patch from Peter Palfrader.)
14883 - STREAM NEW events are generated for DNSPort requests and for
14884 tunneled directory connections. (Patch from Robert Hogan.)
14885 - New "GETINFO address-mappings/*" command to get address mappings
14886 with expiry information. "addr-mappings/*" is now deprecated.
14889 o Minor features (misc):
14890 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
14892 - The tor-gencert tool for v3 directory authorities now creates all
14893 files as readable to the file creator only, and write-protects
14894 the authority identity key.
14895 - When dumping memory usage, list bytes used in buffer memory
14897 - When running with dmalloc, dump more stats on hup and on exit.
14898 - Directory authorities now fail quickly and (relatively) harmlessly
14899 if they generate a network status document that is somehow
14902 o Traffic load balancing improvements:
14903 - If exit bandwidth ever exceeds one third of total bandwidth, then
14904 use the correct formula to weight exit nodes when choosing paths.
14905 (Based on patch from Mike Perry.)
14906 - Choose perfectly fairly among routers when choosing by bandwidth and
14907 weighting by fraction of bandwidth provided by exits. Previously, we
14908 would choose with only approximate fairness, and correct ourselves
14909 if we ran off the end of the list. [Bugfix on 0.1.2.x]
14911 o Performance improvements:
14912 - Be more aggressive with freeing buffer RAM or putting it on the
14914 - Use Critical Sections rather than Mutexes for synchronizing threads
14915 on win32; Mutexes are heavier-weight, and designed for synchronizing
14918 o Deprecated and removed features:
14919 - RedirectExits is now deprecated.
14920 - Stop allowing address masks that do not correspond to bit prefixes.
14921 We have warned about these for a really long time; now it's time
14922 to reject them. (Patch from croup.)
14924 o Minor bugfixes (directory):
14925 - Fix another crash bug related to extra-info caching. (Bug found by
14926 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
14927 - Directories no longer return a "304 not modified" when they don't
14928 have the networkstatus the client asked for. Also fix a memory
14929 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
14930 - We had accidentally labelled 0.1.2.x directory servers as not
14931 suitable for begin_dir requests, and had labelled no directory
14932 servers as suitable for uploading extra-info documents. [Bugfix
14935 o Minor bugfixes (dns):
14936 - Fix a crash when DNSPort is set more than once. (Patch from Robert
14937 Hogan.) [Bugfix on 0.2.0.2-alpha]
14938 - Add DNSPort connections to the global connection list, so that we
14939 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
14941 - Fix a dangling reference that could lead to a crash when DNSPort is
14942 changed or closed (Patch from Robert Hogan.) [Bugfix on
14945 o Minor bugfixes (controller):
14946 - Provide DNS expiry times in GMT, not in local time. For backward
14947 compatibility, ADDRMAP events only provide GMT expiry in an extended
14948 field. "GETINFO address-mappings" always does the right thing.
14949 - Use CRLF line endings properly in NS events.
14950 - Terminate multi-line control events properly. (Original patch
14951 from tup.) [Bugfix on 0.1.2.x-alpha]
14952 - Do not include spaces in SOURCE_ADDR fields in STREAM
14953 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
14956 Changes in version 0.1.2.15 - 2007-07-17
14957 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
14958 problems, fixes compilation on BSD, and fixes a variety of other
14959 bugs. Everybody should upgrade.
14961 o Major bugfixes (compilation):
14962 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
14964 o Major bugfixes (crashes):
14965 - Try even harder not to dereference the first character after
14966 an mmap(). Reported by lodger.
14967 - Fix a crash bug in directory authorities when we re-number the
14968 routerlist while inserting a new router.
14969 - When the cached-routers file is an even multiple of the page size,
14970 don't run off the end and crash. (Fixes bug 455; based on idea
14972 - Fix eventdns.c behavior on Solaris: It is critical to include
14973 orconfig.h _before_ sys/types.h, so that we can get the expected
14974 definition of _FILE_OFFSET_BITS.
14976 o Major bugfixes (security):
14977 - Fix a possible buffer overrun when using BSD natd support. Bug
14979 - When sending destroy cells from a circuit's origin, don't include
14980 the reason for tearing down the circuit. The spec says we didn't,
14981 and now we actually don't. Reported by lodger.
14982 - Keep streamids from different exits on a circuit separate. This
14983 bug may have allowed other routers on a given circuit to inject
14984 cells into streams. Reported by lodger; fixes bug 446.
14985 - If there's a never-before-connected-to guard node in our list,
14986 never choose any guards past it. This way we don't expand our
14987 guard list unless we need to.
14989 o Minor bugfixes (guard nodes):
14990 - Weight guard selection by bandwidth, so that low-bandwidth nodes
14991 don't get overused as guards.
14993 o Minor bugfixes (directory):
14994 - Correctly count the number of authorities that recommend each
14995 version. Previously, we were under-counting by 1.
14996 - Fix a potential crash bug when we load many server descriptors at
14997 once and some of them make others of them obsolete. Fixes bug 458.
14999 o Minor bugfixes (hidden services):
15000 - Stop tearing down the whole circuit when the user asks for a
15001 connection to a port that the hidden service didn't configure.
15004 o Minor bugfixes (misc):
15005 - On Windows, we were preventing other processes from reading
15006 cached-routers while Tor was running. Reported by janbar.
15007 - Fix a possible (but very unlikely) bug in picking routers by
15008 bandwidth. Add a log message to confirm that it is in fact
15009 unlikely. Patch from lodger.
15010 - Backport a couple of memory leak fixes.
15011 - Backport miscellaneous cosmetic bugfixes.
15014 Changes in version 0.2.0.2-alpha - 2007-06-02
15015 o Major bugfixes on 0.2.0.1-alpha:
15016 - Fix an assertion failure related to servers without extra-info digests.
15017 Resolves bugs 441 and 442.
15019 o Minor features (directory):
15020 - Support "If-Modified-Since" when answering HTTP requests for
15021 directories, running-routers documents, and network-status documents.
15022 (There's no need to support it for router descriptors, since those
15023 are downloaded by descriptor digest.)
15025 o Minor build issues:
15026 - Clear up some MIPSPro compiler warnings.
15027 - When building from a tarball on a machine that happens to have SVK
15028 installed, report the micro-revision as whatever version existed
15029 in the tarball, not as "x".
15032 Changes in version 0.2.0.1-alpha - 2007-06-01
15033 This early development snapshot provides new features for people running
15034 Tor as both a client and a server (check out the new RelayBandwidth
15035 config options); lets Tor run as a DNS proxy; and generally moves us
15036 forward on a lot of fronts.
15038 o Major features, server usability:
15039 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15040 a separate set of token buckets for relayed traffic. Right now
15041 relayed traffic is defined as answers to directory requests, and
15042 OR connections that don't have any local circuits on them.
15044 o Major features, client usability:
15045 - A client-side DNS proxy feature to replace the need for
15046 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15047 for DNS requests on port 9999, use the Tor network to resolve them
15048 anonymously, and send the reply back like a regular DNS server.
15049 The code still only implements a subset of DNS.
15050 - Make PreferTunneledDirConns and TunnelDirConns work even when
15051 we have no cached directory info. This means Tor clients can now
15052 do all of their connections protected by TLS.
15054 o Major features, performance and efficiency:
15055 - Directory authorities accept and serve "extra info" documents for
15056 routers. These documents contain fields from router descriptors
15057 that aren't usually needed, and that use a lot of excess
15058 bandwidth. Once these fields are removed from router descriptors,
15059 the bandwidth savings should be about 60%. [Partially implements
15061 - Servers upload extra-info documents to any authority that accepts
15062 them. Authorities (and caches that have been configured to download
15063 extra-info documents) download them as needed. [Partially implements
15065 - Change the way that Tor buffers data that it is waiting to write.
15066 Instead of queueing data cells in an enormous ring buffer for each
15067 client->OR or OR->OR connection, we now queue cells on a separate
15068 queue for each circuit. This lets us use less slack memory, and
15069 will eventually let us be smarter about prioritizing different kinds
15071 - Use memory pools to allocate cells with better speed and memory
15072 efficiency, especially on platforms where malloc() is inefficient.
15073 - Stop reading on edge connections when their corresponding circuit
15074 buffers are full; start again as the circuits empty out.
15076 o Major features, other:
15077 - Add an HSAuthorityRecordStats option that hidden service authorities
15078 can use to track statistics of overall hidden service usage without
15079 logging information that would be very useful to an attacker.
15080 - Start work implementing multi-level keys for directory authorities:
15081 Add a standalone tool to generate key certificates. (Proposal 103.)
15084 - Directory authorities now call routers Stable if they have an
15085 uptime of at least 30 days, even if that's not the median uptime
15086 in the network. Implements proposal 107, suggested by Kevin Bauer
15089 o Minor fixes (resource management):
15090 - Count the number of open sockets separately from the number
15091 of active connection_t objects. This will let us avoid underusing
15092 our allocated connection limit.
15093 - We no longer use socket pairs to link an edge connection to an
15094 anonymous directory connection or a DirPort test connection.
15095 Instead, we track the link internally and transfer the data
15096 in-process. This saves two sockets per "linked" connection (at the
15097 client and at the server), and avoids the nasty Windows socketpair()
15099 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15100 for every single inactive connection_t. Free items from the
15101 4k/16k-buffer free lists when they haven't been used for a while.
15103 o Minor features (build):
15104 - Make autoconf search for libevent, openssl, and zlib consistently.
15105 - Update deprecated macros in configure.in.
15106 - When warning about missing headers, tell the user to let us
15107 know if the compile succeeds anyway, so we can downgrade the
15109 - Include the current subversion revision as part of the version
15110 string: either fetch it directly if we're in an SVN checkout, do
15111 some magic to guess it if we're in an SVK checkout, or use
15112 the last-detected version if we're building from a .tar.gz.
15113 Use this version consistently in log messages.
15115 o Minor features (logging):
15116 - Always prepend "Bug: " to any log message about a bug.
15117 - Put a platform string (e.g. "Linux i686") in the startup log
15118 message, so when people paste just their logs, we know if it's
15119 OpenBSD or Windows or what.
15120 - When logging memory usage, break down memory used in buffers by
15123 o Minor features (directory system):
15124 - New config option V2AuthoritativeDirectory that all directory
15125 authorities should set. This will let future authorities choose
15126 not to serve V2 directory information.
15127 - Directory authorities allow multiple router descriptors and/or extra
15128 info documents to be uploaded in a single go. This will make
15129 implementing proposal 104 simpler.
15131 o Minor features (controller):
15132 - Add a new config option __DisablePredictedCircuits designed for
15133 use by the controller, when we don't want Tor to build any circuits
15135 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15136 so we can exit from the middle of the circuit.
15137 - Implement "getinfo status/circuit-established".
15138 - Implement "getinfo status/version/..." so a controller can tell
15139 whether the current version is recommended, and whether any versions
15140 are good, and how many authorities agree. (Patch from shibz.)
15142 o Minor features (hidden services):
15143 - Allow multiple HiddenServicePort directives with the same virtual
15144 port; when they occur, the user is sent round-robin to one
15145 of the target ports chosen at random. Partially fixes bug 393 by
15146 adding limited ad-hoc round-robining.
15148 o Minor features (other):
15150 - Add a new AutomapHostsOnResolve option: when it is enabled, any
15151 resolve request for hosts matching a given pattern causes Tor to
15152 generate an internal virtual address mapping for that host. This
15153 allows DNSPort to work sensibly with hidden service users. By
15154 default, .exit and .onion addresses are remapped; the list of
15155 patterns can be reconfigured with AutomapHostsSuffixes.
15156 - Add an "-F" option to tor-resolve to force a resolve for a .onion
15157 address. Thanks to the AutomapHostsOnResolve option, this is no
15158 longer a completely silly thing to do.
15159 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15160 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15161 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15162 minus 1 byte: the actual maximum declared bandwidth.
15164 o Removed features:
15165 - Removed support for the old binary "version 0" controller protocol.
15166 This has been deprecated since 0.1.1, and warnings have been issued
15167 since 0.1.2. When we encounter a v0 control message, we now send
15168 back an error and close the connection.
15169 - Remove the old "dns worker" server DNS code: it hasn't been default
15170 since 0.1.2.2-alpha, and all the servers seem to be using the new
15173 o Minor bugfixes (portability):
15174 - Even though Windows is equally happy with / and \ as path separators,
15175 try to use \ consistently on Windows and / consistently on Unix: it
15176 makes the log messages nicer.
15177 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15178 - Read resolv.conf files correctly on platforms where read() returns
15179 partial results on small file reads.
15181 o Minor bugfixes (directory):
15182 - Correctly enforce that elements of directory objects do not appear
15183 more often than they are allowed to appear.
15184 - When we are reporting the DirServer line we just parsed, we were
15185 logging the second stanza of the key fingerprint, not the first.
15187 o Minor bugfixes (logging):
15188 - When we hit an EOF on a log (probably because we're shutting down),
15189 don't try to remove the log from the list: just mark it as
15190 unusable. (Bulletproofs against bug 222.)
15192 o Minor bugfixes (other):
15193 - In the exitlist script, only consider the most recently published
15194 server descriptor for each server. Also, when the user requests
15195 a list of servers that _reject_ connections to a given address,
15196 explicitly exclude the IPs that also have servers that accept
15197 connections to that address. (Resolves bug 405.)
15198 - Stop allowing hibernating servers to be "stable" or "fast".
15199 - On Windows, we were preventing other processes from reading
15200 cached-routers while Tor was running. (Reported by janbar)
15201 - Make the NodeFamilies config option work. (Reported by
15202 lodger -- it has never actually worked, even though we added it
15204 - Check return values from pthread_mutex functions.
15205 - Don't save non-general-purpose router descriptors to the disk cache,
15206 because we have no way of remembering what their purpose was when
15208 - Add even more asserts to hunt down bug 417.
15209 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
15210 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
15211 Add a log message to confirm that it is in fact unlikely.
15213 o Minor bugfixes (controller):
15214 - Make 'getinfo fingerprint' return a 551 error if we're not a
15215 server, so we match what the control spec claims we do. Reported
15217 - Fix a typo in an error message when extendcircuit fails that
15218 caused us to not follow the \r\n-based delimiter protocol. Reported
15221 o Code simplifications and refactoring:
15222 - Stop passing around circuit_t and crypt_path_t pointers that are
15223 implicit in other procedure arguments.
15224 - Drop the old code to choke directory connections when the
15225 corresponding OR connections got full: thanks to the cell queue
15226 feature, OR conns don't get full any more.
15227 - Make dns_resolve() handle attaching connections to circuits
15228 properly, so the caller doesn't have to.
15229 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
15230 - Keep the connection array as a dynamic smartlist_t, rather than as
15231 a fixed-sized array. This is important, as the number of connections
15232 is becoming increasingly decoupled from the number of sockets.
15235 Changes in version 0.1.2.14 - 2007-05-25
15236 Tor 0.1.2.14 changes the addresses of two directory authorities (this
15237 change especially affects those who serve or use hidden services),
15238 and fixes several other crash- and security-related bugs.
15240 o Directory authority changes:
15241 - Two directory authorities (moria1 and moria2) just moved to new
15242 IP addresses. This change will particularly affect those who serve
15243 or use hidden services.
15245 o Major bugfixes (crashes):
15246 - If a directory server runs out of space in the connection table
15247 as it's processing a begin_dir request, it will free the exit stream
15248 but leave it attached to the circuit, leading to unpredictable
15249 behavior. (Reported by seeess, fixes bug 425.)
15250 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15251 to corrupt memory under some really unlikely scenarios.
15252 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15253 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15256 o Major bugfixes (security):
15257 - When choosing an entry guard for a circuit, avoid using guards
15258 that are in the same family as the chosen exit -- not just guards
15259 that are exactly the chosen exit. (Reported by lodger.)
15261 o Major bugfixes (resource management):
15262 - If a directory authority is down, skip it when deciding where to get
15263 networkstatus objects or descriptors. Otherwise we keep asking
15264 every 10 seconds forever. Fixes bug 384.
15265 - Count it as a failure if we fetch a valid network-status but we
15266 don't want to keep it. Otherwise we'll keep fetching it and keep
15267 not wanting to keep it. Fixes part of bug 422.
15268 - If all of our dirservers have given us bad or no networkstatuses
15269 lately, then stop hammering them once per minute even when we
15270 think they're failed. Fixes another part of bug 422.
15273 - Actually set the purpose correctly for descriptors inserted with
15274 purpose=controller.
15275 - When we have k non-v2 authorities in our DirServer config,
15276 we ignored the last k authorities in the list when updating our
15278 - Correctly back-off from requesting router descriptors that we are
15279 having a hard time downloading.
15280 - Read resolv.conf files correctly on platforms where read() returns
15281 partial results on small file reads.
15282 - Don't rebuild the entire router store every time we get 32K of
15283 routers: rebuild it when the journal gets very large, or when
15284 the gaps in the store get very large.
15287 - When routers publish SVN revisions in their router descriptors,
15288 authorities now include those versions correctly in networkstatus
15290 - Warn when using a version of libevent before 1.3b to run a server on
15291 OSX or BSD: these versions interact badly with userspace threads.
15294 Changes in version 0.1.2.13 - 2007-04-24
15295 This release features some major anonymity fixes, such as safer path
15296 selection; better client performance; faster bootstrapping, better
15297 address detection, and better DNS support for servers; write limiting as
15298 well as read limiting to make servers easier to run; and a huge pile of
15299 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15301 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15302 of the Freenode IRC network, remembering his patience and vision for
15303 free speech on the Internet.
15306 - Fix a memory leak when we ask for "all" networkstatuses and we
15307 get one we don't recognize.
15308 - Add more asserts to hunt down bug 417.
15309 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15312 Changes in version 0.1.2.12-rc - 2007-03-16
15314 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
15315 directory information requested inside Tor connections (i.e. via
15316 begin_dir cells). It only triggered when the same connection was
15317 serving other data at the same time. Reported by seeess.
15320 - When creating a circuit via the controller, send a 'launched'
15321 event when we're done, so we follow the spec better.
15324 Changes in version 0.1.2.11-rc - 2007-03-15
15325 o Minor bugfixes (controller), reported by daejees:
15326 - Correct the control spec to match how the code actually responds
15327 to 'getinfo addr-mappings/*'.
15328 - The control spec described a GUARDS event, but the code
15329 implemented a GUARD event. Standardize on GUARD, but let people
15330 ask for GUARDS too.
15333 Changes in version 0.1.2.10-rc - 2007-03-07
15334 o Major bugfixes (Windows):
15335 - Do not load the NT services library functions (which may not exist)
15336 just to detect if we're a service trying to shut down. Now we run
15337 on Win98 and friends again.
15339 o Minor bugfixes (other):
15340 - Clarify a couple of log messages.
15341 - Fix a misleading socks5 error number.
15344 Changes in version 0.1.2.9-rc - 2007-03-02
15345 o Major bugfixes (Windows):
15346 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
15347 of the usual GCC "%llu". This prevents a bug when saving 64-bit
15348 int configuration values: the high-order 32 bits would get
15349 truncated. In particular, we were being bitten by the default
15350 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
15351 and maybe also bug 397.)
15353 o Minor bugfixes (performance):
15354 - Use OpenSSL's AES implementation on platforms where it's faster.
15355 This could save us as much as 10% CPU usage.
15357 o Minor bugfixes (server):
15358 - Do not rotate onion key immediately after setting it for the first
15361 o Minor bugfixes (directory authorities):
15362 - Stop calling servers that have been hibernating for a long time
15363 "stable". Also, stop letting hibernating or obsolete servers affect
15364 uptime and bandwidth cutoffs.
15365 - Stop listing hibernating servers in the v1 directory.
15367 o Minor bugfixes (hidden services):
15368 - Upload hidden service descriptors slightly less often, to reduce
15369 load on authorities.
15371 o Minor bugfixes (other):
15372 - Fix an assert that could trigger if a controller quickly set then
15373 cleared EntryNodes. Bug found by Udo van den Heuvel.
15374 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
15376 - Fix a potential race condition in the rpm installer. Found by
15378 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
15379 of 2 as indicating that the server is completely bad; it sometimes
15380 means that the server is just bad for the request in question. (may fix
15381 the last of bug 326.)
15382 - Disable encrypted directory connections when we don't have a server
15383 descriptor for the destination. We'll get this working again in
15387 Changes in version 0.1.2.8-beta - 2007-02-26
15388 o Major bugfixes (crashes):
15389 - Stop crashing when the controller asks us to resetconf more than
15390 one config option at once. (Vidalia 0.0.11 does this.)
15391 - Fix a crash that happened on Win98 when we're given command-line
15392 arguments: don't try to load NT service functions from advapi32.dll
15393 except when we need them. (Bug introduced in 0.1.2.7-alpha;
15395 - Fix a longstanding obscure crash bug that could occur when
15396 we run out of DNS worker processes. (Resolves bug 390.)
15398 o Major bugfixes (hidden services):
15399 - Correctly detect whether hidden service descriptor downloads are
15400 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
15402 o Major bugfixes (accounting):
15403 - When we start during an accounting interval before it's time to wake
15404 up, remember to wake up at the correct time. (May fix bug 342.)
15406 o Minor bugfixes (controller):
15407 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15408 clear the corresponding on_circuit variable, and remember later
15409 that we don't need to send a redundant CLOSED event. Resolves part
15411 - Report events where a resolve succeeded or where we got a socks
15412 protocol error correctly, rather than calling both of them
15414 - Change reported stream target addresses to IP consistently when
15415 we finally get the IP from an exit node.
15416 - Send log messages to the controller even if they happen to be very
15419 o Minor bugfixes (other):
15420 - Display correct results when reporting which versions are
15421 recommended, and how recommended they are. (Resolves bug 383.)
15422 - Improve our estimates for directory bandwidth to be less random:
15423 guess that an unrecognized directory will have the average bandwidth
15424 from all known directories, not that it will have the average
15425 bandwidth from those directories earlier than it on the list.
15426 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15427 and hup, stop triggering an assert based on an empty onion_key.
15428 - On platforms with no working mmap() equivalent, don't warn the
15429 user when cached-routers doesn't exist.
15430 - Warn the user when mmap() [or its equivalent] fails for some reason
15431 other than file-not-found.
15432 - Don't warn the user when cached-routers.new doesn't exist: that's
15433 perfectly fine when starting up for the first time.
15434 - When EntryNodes are configured, rebuild the guard list to contain,
15435 in order: the EntryNodes that were guards before; the rest of the
15436 EntryNodes; the nodes that were guards before.
15437 - Mask out all signals in sub-threads; only the libevent signal
15438 handler should be processing them. This should prevent some crashes
15439 on some machines using pthreads. (Patch from coderman.)
15440 - Fix switched arguments on memset in the implementation of
15441 tor_munmap() for systems with no mmap() call.
15442 - When Tor receives a router descriptor that it asked for, but
15443 no longer wants (because it has received fresh networkstatuses
15444 in the meantime), do not warn the user. Cache the descriptor if
15445 we're a cache; drop it if we aren't.
15446 - Make earlier entry guards _really_ get retried when the network
15448 - On a malformed DNS reply, always give an error to the corresponding
15450 - Build with recent libevents on platforms that do not define the
15451 nonstandard types "u_int8_t" and friends.
15453 o Minor features (controller):
15454 - Warn the user when an application uses the obsolete binary v0
15455 control protocol. We're planning to remove support for it during
15456 the next development series, so it's good to give people some
15458 - Add STREAM_BW events to report per-entry-stream bandwidth
15459 use. (Patch from Robert Hogan.)
15460 - Rate-limit SIGNEWNYM signals in response to controllers that
15461 impolitely generate them for every single stream. (Patch from
15462 mwenge; closes bug 394.)
15463 - Make REMAP stream events have a SOURCE (cache or exit), and
15464 make them generated in every case where we get a successful
15465 connected or resolved cell.
15467 o Minor bugfixes (performance):
15468 - Call router_have_min_dir_info half as often. (This is showing up in
15469 some profiles, but not others.)
15470 - When using GCC, make log_debug never get called at all, and its
15471 arguments never get evaluated, when no debug logs are configured.
15472 (This is showing up in some profiles, but not others.)
15475 - Remove some never-implemented options. Mark PathlenCoinWeight as
15477 - Implement proposal 106: Stop requiring clients to have well-formed
15478 certificates; stop checking nicknames in certificates. (Clients
15479 have certificates so that they can look like Tor servers, but in
15480 the future we might want to allow them to look like regular TLS
15481 clients instead. Nicknames in certificates serve no purpose other
15482 than making our protocol easier to recognize on the wire.)
15483 - Revise messages on handshake failure again to be even more clear about
15484 which are incoming connections and which are outgoing.
15485 - Discard any v1 directory info that's over 1 month old (for
15486 directories) or over 1 week old (for running-routers lists).
15487 - Do not warn when individual nodes in the configuration's EntryNodes,
15488 ExitNodes, etc are down: warn only when all possible nodes
15489 are down. (Fixes bug 348.)
15490 - Always remove expired routers and networkstatus docs before checking
15491 whether we have enough information to build circuits. (Fixes
15493 - Put a lower-bound on MaxAdvertisedBandwidth.
15496 Changes in version 0.1.2.7-alpha - 2007-02-06
15497 o Major bugfixes (rate limiting):
15498 - Servers decline directory requests much more aggressively when
15499 they're low on bandwidth. Otherwise they end up queueing more and
15500 more directory responses, which can't be good for latency.
15501 - But never refuse directory requests from local addresses.
15502 - Fix a memory leak when sending a 503 response for a networkstatus
15504 - Be willing to read or write on local connections (e.g. controller
15505 connections) even when the global rate limiting buckets are empty.
15506 - If our system clock jumps back in time, don't publish a negative
15507 uptime in the descriptor. Also, don't let the global rate limiting
15508 buckets go absurdly negative.
15509 - Flush local controller connection buffers periodically as we're
15510 writing to them, so we avoid queueing 4+ megabytes of data before
15513 o Major bugfixes (NT services):
15514 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15515 command-line flag so that admins can override the default by saying
15516 "tor --service install --user "SomeUser"". This will not affect
15517 existing installed services. Also, warn the user that the service
15518 will look for its configuration file in the service user's
15519 %appdata% directory. (We can't do the 'hardwire the user's appdata
15520 directory' trick any more, since we may not have read access to that
15523 o Major bugfixes (other):
15524 - Previously, we would cache up to 16 old networkstatus documents
15525 indefinitely, if they came from nontrusted authorities. Now we
15526 discard them if they are more than 10 days old.
15527 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
15529 - Detect and reject malformed DNS responses containing circular
15531 - If exits are rare enough that we're not marking exits as guards,
15532 ignore exit bandwidth when we're deciding the required bandwidth
15534 - When we're handling a directory connection tunneled over Tor,
15535 don't fill up internal memory buffers with all the data we want
15536 to tunnel; instead, only add it if the OR connection that will
15537 eventually receive it has some room for it. (This can lead to
15538 slowdowns in tunneled dir connections; a better solution will have
15539 to wait for 0.2.0.)
15541 o Minor bugfixes (dns):
15542 - Add some defensive programming to eventdns.c in an attempt to catch
15543 possible memory-stomping bugs.
15544 - Detect and reject DNS replies containing IPv4 or IPv6 records with
15545 an incorrect number of bytes. (Previously, we would ignore the
15547 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
15548 in the correct order, and doesn't crash.
15549 - Free memory held in recently-completed DNS lookup attempts on exit.
15550 This was not a memory leak, but may have been hiding memory leaks.
15551 - Handle TTL values correctly on reverse DNS lookups.
15552 - Treat failure to parse resolv.conf as an error.
15554 o Minor bugfixes (other):
15555 - Fix crash with "tor --list-fingerprint" (reported by seeess).
15556 - When computing clock skew from directory HTTP headers, consider what
15557 time it was when we finished asking for the directory, not what
15559 - Expire socks connections if they spend too long waiting for the
15560 handshake to finish. Previously we would let them sit around for
15561 days, if the connecting application didn't close them either.
15562 - And if the socks handshake hasn't started, don't send a
15563 "DNS resolve socks failed" handshake reply; just close it.
15564 - Stop using C functions that OpenBSD's linker doesn't like.
15565 - Don't launch requests for descriptors unless we have networkstatuses
15566 from at least half of the authorities. This delays the first
15567 download slightly under pathological circumstances, but can prevent
15568 us from downloading a bunch of descriptors we don't need.
15569 - Do not log IPs with TLS failures for incoming TLS
15570 connections. (Fixes bug 382.)
15571 - If the user asks to use invalid exit nodes, be willing to use
15573 - Stop using the reserved ac_cv namespace in our configure script.
15574 - Call stat() slightly less often; use fstat() when possible.
15575 - Refactor the way we handle pending circuits when an OR connection
15576 completes or fails, in an attempt to fix a rare crash bug.
15577 - Only rewrite a conn's address based on X-Forwarded-For: headers
15578 if it's a parseable public IP address; and stop adding extra quotes
15579 to the resulting address.
15582 - Weight directory requests by advertised bandwidth. Now we can
15583 let servers enable write limiting but still allow most clients to
15584 succeed at their directory requests. (We still ignore weights when
15585 choosing a directory authority; I hope this is a feature.)
15588 - Create a new file ReleaseNotes which was the old ChangeLog. The
15589 new ChangeLog file now includes the summaries for all development
15591 - Check for addresses with invalid characters at the exit as well
15592 as at the client, and warn less verbosely when they fail. You can
15593 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
15594 - Adapt a patch from goodell to let the contrib/exitlist script
15595 take arguments rather than require direct editing.
15596 - Inform the server operator when we decide not to advertise a
15597 DirPort due to AccountingMax enabled or a low BandwidthRate. It
15598 was confusing Zax, so now we're hopefully more helpful.
15599 - Bring us one step closer to being able to establish an encrypted
15600 directory tunnel without knowing a descriptor first. Still not
15601 ready yet. As part of the change, now assume we can use a
15602 create_fast cell if we don't know anything about a router.
15603 - Allow exit nodes to use nameservers running on ports other than 53.
15604 - Servers now cache reverse DNS replies.
15605 - Add an --ignore-missing-torrc command-line option so that we can
15606 get the "use sensible defaults if the configuration file doesn't
15607 exist" behavior even when specifying a torrc location on the command
15610 o Minor features (controller):
15611 - Track reasons for OR connection failure; make these reasons
15612 available via the controller interface. (Patch from Mike Perry.)
15613 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15614 can learn when clients are sending malformed hostnames to Tor.
15615 - Clean up documentation for controller status events.
15616 - Add a REMAP status to stream events to note that a stream's
15617 address has changed because of a cached address or a MapAddress
15621 Changes in version 0.1.2.6-alpha - 2007-01-09
15623 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
15624 connection handles more than 4 gigs in either direction, we crash.
15625 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
15626 advertised exit node, somebody might try to exit from us when
15627 we're bootstrapping and before we've built our descriptor yet.
15628 Refuse the connection rather than crashing.
15631 - Warn if we (as a server) find that we've resolved an address that we
15632 weren't planning to resolve.
15633 - Warn that using select() on any libevent version before 1.1 will be
15634 unnecessarily slow (even for select()).
15635 - Flush ERR-level controller status events just like we currently
15636 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15637 the controller from learning about current events.
15639 o Minor features (more controller status events):
15640 - Implement EXTERNAL_ADDRESS server status event so controllers can
15641 learn when our address changes.
15642 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
15643 can learn when directories reject our descriptor.
15644 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
15645 can learn when a client application is speaking a non-socks protocol
15647 - Implement DANGEROUS_SOCKS client status event so controllers
15648 can learn when a client application is leaking DNS addresses.
15649 - Implement BUG general status event so controllers can learn when
15650 Tor is unhappy about its internal invariants.
15651 - Implement CLOCK_SKEW general status event so controllers can learn
15652 when Tor thinks the system clock is set incorrectly.
15653 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
15654 server status events so controllers can learn when their descriptors
15655 are accepted by a directory.
15656 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
15657 server status events so controllers can learn about Tor's progress in
15658 deciding whether it's reachable from the outside.
15659 - Implement BAD_LIBEVENT general status event so controllers can learn
15660 when we have a version/method combination in libevent that needs to
15662 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
15663 and DNS_USELESS server status events so controllers can learn
15664 about changes to DNS server status.
15666 o Minor features (directory):
15667 - Authorities no longer recommend exits as guards if this would shift
15668 too much load to the exit nodes.
15671 Changes in version 0.1.2.5-alpha - 2007-01-06
15673 - Enable write limiting as well as read limiting. Now we sacrifice
15674 capacity if we're pushing out lots of directory traffic, rather
15675 than overrunning the user's intended bandwidth limits.
15676 - Include TLS overhead when counting bandwidth usage; previously, we
15677 would count only the bytes sent over TLS, but not the bytes used
15679 - Support running the Tor service with a torrc not in the same
15680 directory as tor.exe and default to using the torrc located in
15681 the %appdata%\Tor\ of the user who installed the service. Patch
15683 - Servers now check for the case when common DNS requests are going to
15684 wildcarded addresses (i.e. all getting the same answer), and change
15685 their exit policy to reject *:* if it's happening.
15686 - Implement BEGIN_DIR cells, so we can connect to the directory
15687 server via TLS to do encrypted directory requests rather than
15688 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15689 config options if you like.
15691 o Minor features (config and docs):
15692 - Start using the state file to store bandwidth accounting data:
15693 the bw_accounting file is now obsolete. We'll keep generating it
15694 for a while for people who are still using 0.1.2.4-alpha.
15695 - Try to batch changes to the state file so that we do as few
15696 disk writes as possible while still storing important things in
15698 - The state file and the bw_accounting file get saved less often when
15699 the AvoidDiskWrites config option is set.
15700 - Make PIDFile work on Windows (untested).
15701 - Add internal descriptions for a bunch of configuration options:
15702 accessible via controller interface and in comments in saved
15704 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15705 NNTP by default, so this seems like a sensible addition.
15706 - Clients now reject hostnames with invalid characters. This should
15707 avoid some inadvertent info leaks. Add an option
15708 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15709 is running a private network with hosts called @, !, and #.
15710 - Add a maintainer script to tell us which options are missing
15711 documentation: "make check-docs".
15712 - Add a new address-spec.txt document to describe our special-case
15713 addresses: .exit, .onion, and .noconnnect.
15715 o Minor features (DNS):
15716 - Ongoing work on eventdns infrastructure: now it has dns server
15717 and ipv6 support. One day Tor will make use of it.
15718 - Add client-side caching for reverse DNS lookups.
15719 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15720 - When we change nameservers or IP addresses, reset and re-launch
15721 our tests for DNS hijacking.
15723 o Minor features (directory):
15724 - Authorities now specify server versions in networkstatus. This adds
15725 about 2% to the size of compressed networkstatus docs, and allows
15726 clients to tell which servers support BEGIN_DIR and which don't.
15727 The implementation is forward-compatible with a proposed future
15728 protocol version scheme not tied to Tor versions.
15729 - DirServer configuration lines now have an orport= option so
15730 clients can open encrypted tunnels to the authorities without
15731 having downloaded their descriptors yet. Enabled for moria1,
15732 moria2, tor26, and lefkada now in the default configuration.
15733 - Directory servers are more willing to send a 503 "busy" if they
15734 are near their write limit, especially for v1 directory requests.
15735 Now they can use their limited bandwidth for actual Tor traffic.
15736 - Clients track responses with status 503 from dirservers. After a
15737 dirserver has given us a 503, we try not to use it until an hour has
15738 gone by, or until we have no dirservers that haven't given us a 503.
15739 - When we get a 503 from a directory, and we're not a server, we don't
15740 count the failure against the total number of failures allowed
15741 for the thing we're trying to download.
15742 - Report X-Your-Address-Is correctly from tunneled directory
15743 connections; don't report X-Your-Address-Is when it's an internal
15744 address; and never believe reported remote addresses when they're
15746 - Protect against an unlikely DoS attack on directory servers.
15747 - Add a BadDirectory flag to network status docs so that authorities
15748 can (eventually) tell clients about caches they believe to be
15751 o Minor features (controller):
15752 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15753 - Reimplement GETINFO so that info/names stays in sync with the
15755 - Implement "GETINFO fingerprint".
15756 - Implement "SETEVENTS GUARD" so controllers can get updates on
15757 entry guard status as it changes.
15759 o Minor features (clean up obsolete pieces):
15760 - Remove some options that have been deprecated since at least
15761 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15762 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15763 to set log options.
15764 - We no longer look for identity and onion keys in "identity.key" and
15765 "onion.key" -- these were replaced by secret_id_key and
15766 secret_onion_key in 0.0.8pre1.
15767 - We no longer require unrecognized directory entries to be
15770 o Major bugfixes (security):
15771 - Stop sending the HttpProxyAuthenticator string to directory
15772 servers when directory connections are tunnelled through Tor.
15773 - Clients no longer store bandwidth history in the state file.
15774 - Do not log introduction points for hidden services if SafeLogging
15776 - When generating bandwidth history, round down to the nearest
15777 1k. When storing accounting data, round up to the nearest 1k.
15778 - When we're running as a server, remember when we last rotated onion
15779 keys, so that we will rotate keys once they're a week old even if
15780 we never stay up for a week ourselves.
15782 o Major bugfixes (other):
15783 - Fix a longstanding bug in eventdns that prevented the count of
15784 timed-out resolves from ever being reset. This bug caused us to
15785 give up on a nameserver the third time it timed out, and try it
15786 10 seconds later... and to give up on it every time it timed out
15788 - Take out the '5 second' timeout from the connection retry
15789 schedule. Now the first connect attempt will wait a full 10
15790 seconds before switching to a new circuit. Perhaps this will help
15791 a lot. Based on observations from Mike Perry.
15792 - Fix a bug on the Windows implementation of tor_mmap_file() that
15793 would prevent the cached-routers file from ever loading. Reported
15797 - Fix an assert failure when a directory authority sets
15798 AuthDirRejectUnlisted and then receives a descriptor from an
15799 unlisted router. Reported by seeess.
15800 - Avoid a double-free when parsing malformed DirServer lines.
15801 - Fix a bug when a BSD-style PF socket is first used. Patch from
15803 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
15804 to resolve an address at a given exit node even when they ask for
15806 - Servers no longer ever list themselves in their "family" line,
15807 even if configured to do so. This makes it easier to configure
15808 family lists conveniently.
15809 - When running as a server, don't fall back to 127.0.0.1 when no
15810 nameservers are configured in /etc/resolv.conf; instead, make the
15811 user fix resolv.conf or specify nameservers explicitly. (Resolves
15813 - Stop accepting certain malformed ports in configured exit policies.
15814 - Don't re-write the fingerprint file every restart, unless it has
15816 - Stop warning when a single nameserver fails: only warn when _all_ of
15817 our nameservers have failed. Also, when we only have one nameserver,
15818 raise the threshold for deciding that the nameserver is dead.
15819 - Directory authorities now only decide that routers are reachable
15820 if their identity keys are as expected.
15821 - When the user uses bad syntax in the Log config line, stop
15822 suggesting other bad syntax as a replacement.
15823 - Correctly detect ipv6 DNS capability on OpenBSD.
15825 o Minor bugfixes (controller):
15826 - Report the circuit number correctly in STREAM CLOSED events. Bug
15827 reported by Mike Perry.
15828 - Do not report bizarre values for results of accounting GETINFOs
15829 when the last second's write or read exceeds the allotted bandwidth.
15830 - Report "unrecognized key" rather than an empty string when the
15831 controller tries to fetch a networkstatus that doesn't exist.
15834 Changes in version 0.1.1.26 - 2006-12-14
15835 o Security bugfixes:
15836 - Stop sending the HttpProxyAuthenticator string to directory
15837 servers when directory connections are tunnelled through Tor.
15838 - Clients no longer store bandwidth history in the state file.
15839 - Do not log introduction points for hidden services if SafeLogging
15843 - Fix an assert failure when a directory authority sets
15844 AuthDirRejectUnlisted and then receives a descriptor from an
15845 unlisted router (reported by seeess).
15848 Changes in version 0.1.2.4-alpha - 2006-12-03
15850 - Add support for using natd; this allows FreeBSDs earlier than
15851 5.1.2 to have ipfw send connections through Tor without using
15852 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15855 - Make all connections to addresses of the form ".noconnect"
15856 immediately get closed. This lets application/controller combos
15857 successfully test whether they're talking to the same Tor by
15858 watching for STREAM events.
15859 - Make cross.sh cross-compilation script work even when autogen.sh
15860 hasn't been run. (Patch from Michael Mohr.)
15861 - Statistics dumped by -USR2 now include a breakdown of public key
15862 operations, for profiling.
15865 - Fix a major leak when directory authorities parse their
15866 approved-routers list, a minor memory leak when we fail to pick
15867 an exit node, and a few rare leaks on errors.
15868 - Handle TransPort connections even when the server sends data before
15869 the client sends data. Previously, the connection would just hang
15870 until the client sent data. (Patch from tup based on patch from
15872 - Avoid assert failure when our cached-routers file is empty on
15876 - Don't log spurious warnings when we see a circuit close reason we
15877 don't recognize; it's probably just from a newer version of Tor.
15878 - Have directory authorities allow larger amounts of drift in uptime
15879 without replacing the server descriptor: previously, a server that
15880 restarted every 30 minutes could have 48 "interesting" descriptors
15882 - Start linking to the Tor specification and Tor reference manual
15883 correctly in the Windows installer.
15884 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15885 Tor/Privoxy we also uninstall Vidalia.
15886 - Resume building on Irix64, and fix a lot of warnings from its
15887 MIPSpro C compiler.
15888 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
15889 when we're running as a client.
15892 Changes in version 0.1.1.25 - 2006-11-04
15894 - When a client asks us to resolve (rather than connect to)
15895 an address, and we have a cached answer, give them the cached
15896 answer. Previously, we would give them no answer at all.
15897 - We were building exactly the wrong circuits when we predict
15898 hidden service requirements, meaning Tor would have to build all
15899 its circuits on demand.
15900 - If none of our live entry guards have a high uptime, but we
15901 require a guard with a high uptime, try adding a new guard before
15902 we give up on the requirement. This patch should make long-lived
15903 connections more stable on average.
15904 - When testing reachability of our DirPort, don't launch new
15905 tests when there's already one in progress -- unreachable
15906 servers were stacking up dozens of testing streams.
15908 o Security bugfixes:
15909 - When the user sends a NEWNYM signal, clear the client-side DNS
15910 cache too. Otherwise we continue to act on previous information.
15913 - Avoid a memory corruption bug when creating a hash table for
15915 - Avoid possibility of controller-triggered crash when misusing
15916 certain commands from a v0 controller on platforms that do not
15917 handle printf("%s",NULL) gracefully.
15918 - Avoid infinite loop on unexpected controller input.
15919 - Don't log spurious warnings when we see a circuit close reason we
15920 don't recognize; it's probably just from a newer version of Tor.
15921 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15922 Tor/Privoxy we also uninstall Vidalia.
15925 Changes in version 0.1.2.3-alpha - 2006-10-29
15927 - Prepare for servers to publish descriptors less often: never
15928 discard a descriptor simply for being too old until either it is
15929 recommended by no authorities, or until we get a better one for
15930 the same router. Make caches consider retaining old recommended
15931 routers for even longer.
15932 - If most authorities set a BadExit flag for a server, clients
15933 don't think of it as a general-purpose exit. Clients only consider
15934 authorities that advertise themselves as listing bad exits.
15935 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15936 headers for content, so that we can work better in the presence of
15937 caching HTTP proxies.
15938 - Allow authorities to list nodes as bad exits by fingerprint or by
15941 o Minor features, controller:
15942 - Add a REASON field to CIRC events; for backward compatibility, this
15943 field is sent only to controllers that have enabled the extended
15944 event format. Also, add additional reason codes to explain why
15945 a given circuit has been destroyed or truncated. (Patches from
15947 - Add a REMOTE_REASON field to extended CIRC events to tell the
15948 controller about why a remote OR told us to close a circuit.
15949 - Stream events also now have REASON and REMOTE_REASON fields,
15950 working much like those for circuit events.
15951 - There's now a GETINFO ns/... field so that controllers can ask Tor
15952 about the current status of a router.
15953 - A new event type "NS" to inform a controller when our opinion of
15954 a router's status has changed.
15955 - Add a GETINFO events/names and GETINFO features/names so controllers
15956 can tell which events and features are supported.
15957 - A new CLEARDNSCACHE signal to allow controllers to clear the
15958 client-side DNS cache without expiring circuits.
15960 o Security bugfixes:
15961 - When the user sends a NEWNYM signal, clear the client-side DNS
15962 cache too. Otherwise we continue to act on previous information.
15965 - Avoid sending junk to controllers or segfaulting when a controller
15966 uses EVENT_NEW_DESC with verbose nicknames.
15967 - Stop triggering asserts if the controller tries to extend hidden
15968 service circuits (reported by mwenge).
15969 - Avoid infinite loop on unexpected controller input.
15970 - When the controller does a "GETINFO network-status", tell it
15971 about even those routers whose descriptors are very old, and use
15972 long nicknames where appropriate.
15973 - Change NT service functions to be loaded on demand. This lets us
15974 build with MinGW without breaking Tor for Windows 98 users.
15975 - Do DirPort reachability tests less often, since a single test
15976 chews through many circuits before giving up.
15977 - In the hidden service example in torrc.sample, stop recommending
15978 esoteric and discouraged hidden service options.
15979 - When stopping an NT service, wait up to 10 sec for it to actually
15980 stop. Patch from Matt Edman; resolves bug 295.
15981 - Fix handling of verbose nicknames with ORCONN controller events:
15982 make them show up exactly when requested, rather than exactly when
15984 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
15985 printing a duplicate "$" in the keys we send (reported by mwenge).
15986 - Correctly set maximum connection limit on Cygwin. (This time
15988 - Try to detect Windows correctly when cross-compiling.
15989 - Detect the size of the routers file correctly even if it is
15990 corrupted (on systems without mmap) or not page-aligned (on systems
15991 with mmap). This bug was harmless.
15992 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15993 to open a stream fails; now we do in more cases. This should
15994 make clients able to find a good exit faster in some cases, since
15995 unhandleable requests will now get an error rather than timing out.
15996 - Resolve two memory leaks when rebuilding the on-disk router cache
15997 (reported by fookoowa).
15998 - Clean up minor code warnings suggested by the MIPSpro C compiler,
15999 and reported by some Centos users.
16000 - Controller signals now work on non-Unix platforms that don't define
16001 SIGUSR1 and SIGUSR2 the way we expect.
16002 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16003 values before failing, and always enables eventdns.
16004 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16005 Try to fix this in configure.in by checking for most functions
16006 before we check for libevent.
16009 Changes in version 0.1.2.2-alpha - 2006-10-07
16011 - Make our async eventdns library on-by-default for Tor servers,
16012 and plan to deprecate the separate dnsworker threads.
16013 - Add server-side support for "reverse" DNS lookups (using PTR
16014 records so clients can determine the canonical hostname for a given
16015 IPv4 address). Only supported by servers using eventdns; servers
16016 now announce in their descriptors whether they support eventdns.
16017 - Specify and implement client-side SOCKS5 interface for reverse DNS
16018 lookups (see doc/socks-extensions.txt).
16019 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
16020 connect to directory servers through Tor. Previously, clients needed
16021 to find Tor exits to make private connections to directory servers.
16022 - Avoid choosing Exit nodes for entry or middle hops when the
16023 total bandwidth available from non-Exit nodes is much higher than
16024 the total bandwidth available from Exit nodes.
16025 - Workaround for name servers (like Earthlink's) that hijack failing
16026 DNS requests and replace the no-such-server answer with a "helpful"
16027 redirect to an advertising-driven search portal. Also work around
16028 DNS hijackers who "helpfully" decline to hijack known-invalid
16029 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16030 lets you turn it off.
16031 - Send out a burst of long-range padding cells once we've established
16032 that we're reachable. Spread them over 4 circuits, so hopefully
16033 a few will be fast. This exercises our bandwidth and bootstraps
16034 us into the directory more quickly.
16036 o New/improved config options:
16037 - Add new config option "ResolvConf" to let the server operator
16038 choose an alternate resolve.conf file when using eventdns.
16039 - Add an "EnforceDistinctSubnets" option to control our "exclude
16040 servers on the same /16" behavior. It's still on by default; this
16041 is mostly for people who want to operate private test networks with
16042 all the machines on the same subnet.
16043 - If one of our entry guards is on the ExcludeNodes list, or the
16044 directory authorities don't think it's a good guard, treat it as
16045 if it were unlisted: stop using it as a guard, and throw it off
16046 the guards list if it stays that way for a long time.
16047 - Allow directory authorities to be marked separately as authorities
16048 for the v1 directory protocol, the v2 directory protocol, and
16049 as hidden service directories, to make it easier to retire old
16050 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16051 to continue being hidden service authorities too.
16052 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16054 o Minor features, controller:
16055 - Fix CIRC controller events so that controllers can learn the
16056 identity digests of non-Named servers used in circuit paths.
16057 - Let controllers ask for more useful identifiers for servers. Instead
16058 of learning identity digests for un-Named servers and nicknames
16059 for Named servers, the new identifiers include digest, nickname,
16060 and indication of Named status. Off by default; see control-spec.txt
16061 for more information.
16062 - Add a "getinfo address" controller command so it can display Tor's
16063 best guess to the user.
16064 - New controller event to alert the controller when our server
16065 descriptor has changed.
16066 - Give more meaningful errors on controller authentication failure.
16068 o Minor features, other:
16069 - When asked to resolve a hostname, don't use non-exit servers unless
16070 requested to do so. This allows servers with broken DNS to be
16071 useful to the network.
16072 - Divide eventdns log messages into warn and info messages.
16073 - Reserve the nickname "Unnamed" for routers that can't pick
16074 a hostname: any router can call itself Unnamed; directory
16075 authorities will never allocate Unnamed to any particular router;
16076 clients won't believe that any router is the canonical Unnamed.
16077 - Only include function names in log messages for info/debug messages.
16078 For notice/warn/err, the content of the message should be clear on
16079 its own, and printing the function name only confuses users.
16080 - Avoid some false positives during reachability testing: don't try
16081 to test via a server that's on the same /24 as us.
16082 - If we fail to build a circuit to an intended enclave, and it's
16083 not mandatory that we use that enclave, stop wanting it.
16084 - When eventdns is enabled, allow multithreaded builds on NetBSD and
16085 OpenBSD. (We had previously disabled threads on these platforms
16086 because they didn't have working thread-safe resolver functions.)
16088 o Major bugfixes, anonymity/security:
16089 - If a client asked for a server by name, and there's a named server
16090 in our network-status but we don't have its descriptor yet, we
16091 could return an unnamed server instead.
16092 - Fix NetBSD bug that could allow someone to force uninitialized RAM
16093 to be sent to a server's DNS resolver. This only affects NetBSD
16094 and other platforms that do not bounds-check tolower().
16095 - Reject (most) attempts to use Tor circuits with length one. (If
16096 many people start using Tor as a one-hop proxy, exit nodes become
16097 a more attractive target for compromise.)
16098 - Just because your DirPort is open doesn't mean people should be
16099 able to remotely teach you about hidden service descriptors. Now
16100 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16102 o Major bugfixes, other:
16103 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
16104 - When a client asks the server to resolve (not connect to)
16105 an address, and it has a cached answer, give them the cached answer.
16106 Previously, the server would give them no answer at all.
16107 - Allow really slow clients to not hang up five minutes into their
16108 directory downloads (suggested by Adam J. Richter).
16109 - We were building exactly the wrong circuits when we anticipated
16110 hidden service requirements, meaning Tor would have to build all
16111 its circuits on demand.
16112 - Avoid crashing when we mmap a router cache file of size 0.
16113 - When testing reachability of our DirPort, don't launch new
16114 tests when there's already one in progress -- unreachable
16115 servers were stacking up dozens of testing streams.
16117 o Minor bugfixes, correctness:
16118 - If we're a directory mirror and we ask for "all" network status
16119 documents, we would discard status documents from authorities
16120 we don't recognize.
16121 - Avoid a memory corruption bug when creating a hash table for
16123 - Avoid controller-triggered crash when misusing certain commands
16124 from a v0 controller on platforms that do not handle
16125 printf("%s",NULL) gracefully.
16126 - Don't crash when a controller sends a third argument to an
16127 "extendcircuit" request.
16128 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16129 response; fix error code when "getinfo dir/status/" fails.
16130 - Avoid crash when telling controller stream-status and a stream
16132 - Patch from Adam Langley to fix assert() in eventdns.c.
16133 - Fix a debug log message in eventdns to say "X resolved to Y"
16134 instead of "X resolved to X".
16135 - Make eventdns give strings for DNS errors, not just error numbers.
16136 - Track unreachable entry guards correctly: don't conflate
16137 'unreachable by us right now' with 'listed as down by the directory
16138 authorities'. With the old code, if a guard was unreachable by
16139 us but listed as running, it would clog our guard list forever.
16140 - Behave correctly in case we ever have a network with more than
16141 2GB/s total advertised capacity.
16142 - Make TrackExitHosts case-insensitive, and fix the behavior of
16143 ".suffix" TrackExitHosts items to avoid matching in the middle of
16145 - Finally fix the openssl warnings from newer gccs that believe that
16146 ignoring a return value is okay, but casting a return value and
16147 then ignoring it is a sign of madness.
16148 - Prevent the contrib/exitlist script from printing the same
16149 result more than once.
16150 - Patch from Steve Hildrey: Generate network status correctly on
16151 non-versioning dirservers.
16152 - Don't listen to the X-Your-Address-Is hint if you did the lookup
16153 via Tor; otherwise you'll think you're the exit node's IP address.
16155 o Minor bugfixes, performance:
16156 - Two small performance improvements on parsing descriptors.
16157 - Major performance improvement on inserting descriptors: change
16158 algorithm from O(n^2) to O(n).
16159 - Make the common memory allocation path faster on machines where
16160 malloc(0) returns a pointer.
16161 - Start remembering X-Your-Address-Is directory hints even if you're
16162 a client, so you can become a server more smoothly.
16163 - Avoid duplicate entries on MyFamily line in server descriptor.
16165 o Packaging, features:
16166 - Remove architecture from OS X builds. The official builds are
16167 now universal binaries.
16168 - The Debian package now uses --verify-config when (re)starting,
16169 to distinguish configuration errors from other errors.
16170 - Update RPMs to require libevent 1.1b.
16172 o Packaging, bugfixes:
16173 - Patches so Tor builds with MinGW on Windows.
16174 - Patches so Tor might run on Cygwin again.
16175 - Resume building on non-gcc compilers and ancient gcc. Resume
16176 building with the -O0 compile flag. Resume building cleanly on
16178 - Run correctly on OS X platforms with case-sensitive filesystems.
16179 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
16180 - Add autoconf checks so Tor can build on Solaris x86 again.
16183 - Documented (and renamed) ServerDNSSearchDomains and
16184 ServerDNSResolvConfFile options.
16185 - Be clearer that the *ListenAddress directives can be repeated
16189 Changes in version 0.1.1.24 - 2006-09-29
16191 - Allow really slow clients to not hang up five minutes into their
16192 directory downloads (suggested by Adam J. Richter).
16193 - Fix major performance regression from 0.1.0.x: instead of checking
16194 whether we have enough directory information every time we want to
16195 do something, only check when the directory information has changed.
16196 This should improve client CPU usage by 25-50%.
16197 - Don't crash if, after a server has been running for a while,
16198 it can't resolve its hostname.
16201 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16202 - Don't crash when the controller receives a third argument to an
16203 "extendcircuit" request.
16204 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16205 response; fix error code when "getinfo dir/status/" fails.
16206 - Fix configure.in to not produce broken configure files with
16207 more recent versions of autoconf. Thanks to Clint for his auto*
16209 - Fix security bug on NetBSD that could allow someone to force
16210 uninitialized RAM to be sent to a server's DNS resolver. This
16211 only affects NetBSD and other platforms that do not bounds-check
16213 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16214 methods: these are known to be buggy.
16215 - If we're a directory mirror and we ask for "all" network status
16216 documents, we would discard status documents from authorities
16217 we don't recognize.
16220 Changes in version 0.1.2.1-alpha - 2006-08-27
16222 - Add "eventdns" async dns library from Adam Langley, tweaked to
16223 build on OSX and Windows. Only enabled if you pass the
16224 --enable-eventdns argument to configure.
16225 - Allow servers with no hostname or IP address to learn their
16226 IP address by asking the directory authorities. This code only
16227 kicks in when you would normally have exited with a "no address"
16228 error. Nothing's authenticated, so use with care.
16229 - Rather than waiting a fixed amount of time between retrying
16230 application connections, we wait only 5 seconds for the first,
16231 10 seconds for the second, and 15 seconds for each retry after
16232 that. Hopefully this will improve the expected user experience.
16233 - Patch from Tup to add support for transparent AP connections:
16234 this basically bundles the functionality of trans-proxy-tor
16235 into the Tor mainline. Now hosts with compliant pf/netfilter
16236 implementations can redirect TCP connections straight to Tor
16237 without diverting through SOCKS. Needs docs.
16238 - Busy directory servers save lots of memory by spooling server
16239 descriptors, v1 directories, and v2 networkstatus docs to buffers
16240 as needed rather than en masse. Also mmap the cached-routers
16241 files, so we don't need to keep the whole thing in memory too.
16242 - Automatically avoid picking more than one node from the same
16243 /16 network when constructing a circuit.
16244 - Revise and clean up the torrc.sample that we ship with; add
16245 a section for BandwidthRate and BandwidthBurst.
16248 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16249 split connection_t into edge, or, dir, control, and base structs.
16250 These will save quite a bit of memory on busy servers, and they'll
16251 also help us track down bugs in the code and bugs in the spec.
16252 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16253 or later. Log when we are doing this, so we can diagnose it when
16254 it fails. (Also, recommend libevent 1.1b for kqueue and
16255 win32 methods; deprecate libevent 1.0b harder; make libevent
16256 recommendation system saner.)
16257 - Start being able to build universal binaries on OS X (thanks
16259 - Export the default exit policy via the control port, so controllers
16260 don't need to guess what it is / will be later.
16261 - Add a man page entry for ProtocolWarnings.
16262 - Add TestVia config option to the man page.
16263 - Remove even more protocol-related warnings from Tor server logs,
16264 such as bad TLS handshakes and malformed begin cells.
16265 - Stop fetching descriptors if you're not a dir mirror and you
16266 haven't tried to establish any circuits lately. [This currently
16267 causes some dangerous behavior, because when you start up again
16268 you'll use your ancient server descriptors.]
16269 - New DirPort behavior: if you have your dirport set, you download
16270 descriptors aggressively like a directory mirror, whether or not
16271 your ORPort is set.
16272 - Get rid of the router_retry_connections notion. Now routers
16273 no longer try to rebuild long-term connections to directory
16274 authorities, and directory authorities no longer try to rebuild
16275 long-term connections to all servers. We still don't hang up
16276 connections in these two cases though -- we need to look at it
16277 more carefully to avoid flapping, and we likely need to wait til
16278 0.1.1.x is obsolete.
16279 - Drop compatibility with obsolete Tors that permit create cells
16280 to have the wrong circ_id_type.
16281 - Re-enable per-connection rate limiting. Get rid of the "OP
16282 bandwidth" concept. Lay groundwork for "bandwidth classes" --
16283 separate global buckets that apply depending on what sort of conn
16285 - Start publishing one minute or so after we find our ORPort
16286 to be reachable. This will help reduce the number of descriptors
16287 we have for ourselves floating around, since it's quite likely
16288 other things (e.g. DirPort) will change during that minute too.
16289 - Fork the v1 directory protocol into its own spec document,
16290 and mark dir-spec.txt as the currently correct (v2) spec.
16293 - When we find our DirPort to be reachable, publish a new descriptor
16294 so we'll tell the world (reported by pnx).
16295 - Publish a new descriptor after we hup/reload. This is important
16296 if our config has changed such that we'll want to start advertising
16297 our DirPort now, etc.
16298 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16299 - When we have a state file we cannot parse, tell the user and
16300 move it aside. Now we avoid situations where the user starts
16301 Tor in 1904, Tor writes a state file with that timestamp in it,
16302 the user fixes her clock, and Tor refuses to start.
16303 - Fix configure.in to not produce broken configure files with
16304 more recent versions of autoconf. Thanks to Clint for his auto*
16306 - "tor --verify-config" now exits with -1(255) or 0 depending on
16307 whether the config options are bad or good.
16308 - Resolve bug 321 when using dnsworkers: append a period to every
16309 address we resolve at the exit node, so that we do not accidentally
16310 pick up local addresses, and so that failing searches are retried
16311 in the resolver search domains. (This is already solved for
16312 eventdns.) (This breaks Blossom servers for now.)
16313 - If we are using an exit enclave and we can't connect, e.g. because
16314 its webserver is misconfigured to not listen on localhost, then
16315 back off and try connecting from somewhere else before we fail.
16318 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
16319 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16320 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16321 when the IP address is mapped through MapAddress to a hostname.
16322 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16323 useless IPv6 DNS resolves.
16324 - Patch suggested by Karsten Loesing: respond to SIGNAL command
16325 before we execute the signal, in case the signal shuts us down.
16326 - Clean up AllowInvalidNodes man page entry.
16327 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16328 - Add more asserts to track down an assert error on a windows Tor
16329 server with connection_add being called with socket == -1.
16330 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16331 - Fix misleading log messages: an entry guard that is "unlisted",
16332 as well as not known to be "down" (because we've never heard
16333 of it), is not therefore "up".
16334 - Remove code to special-case "-cvs" ending, since it has not
16335 actually mattered since 0.0.9.
16336 - Make our socks5 handling more robust to broken socks clients:
16337 throw out everything waiting on the buffer in between socks
16338 handshake phases, since they can't possibly (so the theory
16339 goes) have predicted what we plan to respond to them.
16342 Changes in version 0.1.1.23 - 2006-07-30
16344 - Fast Tor servers, especially exit nodes, were triggering asserts
16345 due to a bug in handling the list of pending DNS resolves. Some
16346 bugs still remain here; we're hunting them.
16347 - Entry guards could crash clients by sending unexpected input.
16348 - More fixes on reachability testing: if you find yourself reachable,
16349 then don't ever make any client requests (so you stop predicting
16350 circuits), then hup or have your clock jump, then later your IP
16351 changes, you won't think circuits are working, so you won't try to
16352 test reachability, so you won't publish.
16355 - Avoid a crash if the controller does a resetconf firewallports
16356 and then a setconf fascistfirewall=1.
16357 - Avoid an integer underflow when the dir authority decides whether
16358 a router is stable: we might wrongly label it stable, and compute
16359 a slightly wrong median stability, when a descriptor is published
16361 - Fix a place where we might trigger an assert if we can't build our
16362 own server descriptor yet.
16365 Changes in version 0.1.1.22 - 2006-07-05
16367 - Fix a big bug that was causing servers to not find themselves
16368 reachable if they changed IP addresses. Since only 0.1.1.22+
16369 servers can do reachability testing correctly, now we automatically
16370 make sure to test via one of these.
16371 - Fix to allow clients and mirrors to learn directory info from
16372 descriptor downloads that get cut off partway through.
16373 - Directory authorities had a bug in deciding if a newly published
16374 descriptor was novel enough to make everybody want a copy -- a few
16375 servers seem to be publishing new descriptors many times a minute.
16377 - Fix a rare bug that was causing some servers to complain about
16378 "closing wedged cpuworkers" and skip some circuit create requests.
16379 - Make the Exit flag in directory status documents actually work.
16382 Changes in version 0.1.1.21 - 2006-06-10
16383 o Crash and assert fixes from 0.1.1.20:
16384 - Fix a rare crash on Tor servers that have enabled hibernation.
16385 - Fix a seg fault on startup for Tor networks that use only one
16386 directory authority.
16387 - Fix an assert from a race condition that occurs on Tor servers
16388 while exiting, where various threads are trying to log that they're
16389 exiting, and delete the logs, at the same time.
16390 - Make our unit tests pass again on certain obscure platforms.
16393 - Add support for building SUSE RPM packages.
16394 - Speed up initial bootstrapping for clients: if we are making our
16395 first ever connection to any entry guard, then don't mark it down
16397 - When only one Tor server in the network is labelled as a guard,
16398 and we've already picked him, we would cycle endlessly picking him
16399 again, being unhappy about it, etc. Now we specifically exclude
16400 current guards when picking a new guard.
16401 - Servers send create cells more reliably after the TLS connection
16402 is established: we were sometimes forgetting to send half of them
16403 when we had more than one pending.
16404 - If we get a create cell that asks us to extend somewhere, but the
16405 Tor server there doesn't match the expected digest, we now send
16406 a destroy cell back, rather than silently doing nothing.
16407 - Make options->RedirectExit work again.
16408 - Make cookie authentication for the controller work again.
16409 - Stop being picky about unusual characters in the arguments to
16410 mapaddress. It's none of our business.
16411 - Add a new config option "TestVia" that lets you specify preferred
16412 middle hops to use for test circuits. Perhaps this will let me
16413 debug the reachability problems better.
16415 o Log / documentation fixes:
16416 - If we're a server and some peer has a broken TLS certificate, don't
16417 log about it unless ProtocolWarnings is set, i.e., we want to hear
16418 about protocol violations by others.
16419 - Fix spelling of VirtualAddrNetwork in man page.
16420 - Add a better explanation at the top of the autogenerated torrc file
16421 about what happened to our old torrc.
16424 Changes in version 0.1.1.20 - 2006-05-23
16426 - Downgrade a log severity where servers complain that they're
16428 - Avoid a compile warning on FreeBSD.
16429 - Remove string size limit on NEWDESC messages; solve bug 291.
16430 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
16431 more thoroughly when we're running on windows.
16434 Changes in version 0.1.1.19-rc - 2006-05-03
16436 - Regenerate our local descriptor if it's dirty and we try to use
16437 it locally (e.g. if it changes during reachability detection).
16438 - If we setconf our ORPort to 0, we continued to listen on the
16439 old ORPort and receive connections.
16440 - Avoid a second warning about machine/limits.h on Debian
16442 - Be willing to add our own routerinfo into the routerlist.
16443 Now authorities will include themselves in their directories
16444 and network-statuses.
16445 - Stop trying to upload rendezvous descriptors to every
16446 directory authority: only try the v1 authorities.
16447 - Servers no longer complain when they think they're not
16448 registered with the directory authorities. There were too many
16450 - Backport dist-rpm changes so rpms can be built without errors.
16453 - Implement an option, VirtualAddrMask, to set which addresses
16454 get handed out in response to mapaddress requests. This works
16455 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16458 Changes in version 0.1.1.18-rc - 2006-04-10
16460 - Work harder to download live network-statuses from all the
16461 directory authorities we know about. Improve the threshold
16462 decision logic so we're more robust to edge cases.
16463 - When fetching rendezvous descriptors, we were willing to ask
16464 v2 authorities too, which would always return 404.
16467 - Stop listing down or invalid nodes in the v1 directory. This will
16468 reduce its bulk by about 1/3, and reduce load on directory
16470 - When deciding whether a router is Fast or Guard-worthy, consider
16471 his advertised BandwidthRate and not just the BandwidthCapacity.
16472 - No longer ship INSTALL and README files -- they are useless now.
16473 - Force rpmbuild to behave and honor target_cpu.
16474 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16475 - Start to include translated versions of the tor-doc-*.html
16476 files, along with the screenshots. Still needs more work.
16477 - Start sending back 512 and 451 errors if mapaddress fails,
16478 rather than not sending anything back at all.
16479 - When we fail to bind or listen on an incoming or outgoing
16480 socket, we should close it before failing. otherwise we just
16481 leak it. (thanks to weasel for finding.)
16482 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
16483 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
16484 - Make NoPublish (even though deprecated) work again.
16485 - Fix a minor security flaw where a versioning auth dirserver
16486 could list a recommended version many times in a row to make
16487 clients more convinced that it's recommended.
16488 - Fix crash bug if there are two unregistered servers running
16489 with the same nickname, one of them is down, and you ask for
16490 them by nickname in your EntryNodes or ExitNodes. Also, try
16491 to pick the one that's running rather than an arbitrary one.
16492 - Fix an infinite loop we could hit if we go offline for too long.
16493 - Complain when we hit WSAENOBUFS on recv() or write() too.
16494 Perhaps this will help us hunt the bug.
16495 - If you're not a versioning dirserver, don't put the string
16496 "client-versions \nserver-versions \n" in your network-status.
16497 - Lower the minimum required number of file descriptors to 1000,
16498 so we can have some overhead for Valgrind on Linux, where the
16499 default ulimit -n is 1024.
16502 - Add tor.dizum.com as the fifth authoritative directory server.
16503 - Add a new config option FetchUselessDescriptors, off by default,
16504 for when you plan to run "exitlist" on your client and you want
16505 to know about even the non-running descriptors.
16508 Changes in version 0.1.1.17-rc - 2006-03-28
16510 - Clients and servers since 0.1.1.10-alpha have been expiring
16511 connections whenever they are idle for 5 minutes and they *do*
16512 have circuits on them. Oops. With this new version, clients will
16513 discard their previous entry guard choices and avoid choosing
16514 entry guards running these flawed versions.
16515 - Fix memory leak when uncompressing concatenated zlib streams. This
16516 was causing substantial leaks over time on Tor servers.
16517 - The v1 directory was including servers as much as 48 hours old,
16518 because that's how the new routerlist->routers works. Now only
16519 include them if they're 20 hours old or less.
16522 - Resume building on irix64, netbsd 2.0, etc.
16523 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
16525 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16526 and it is confusing some users.
16527 - Mirrors stop caching the v1 directory so often.
16528 - Make the max number of old descriptors that a cache will hold
16529 rise with the number of directory authorities, so we can scale.
16530 - Change our win32 uname() hack to be more forgiving about what
16531 win32 versions it thinks it's found.
16534 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
16536 - When the controller's *setconf commands fail, collect an error
16537 message in a string and hand it back to the controller.
16538 - Make the v2 dir's "Fast" flag based on relative capacity, just
16539 like "Stable" is based on median uptime. Name everything in the
16540 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
16541 - Log server fingerprint on startup, so new server operators don't
16542 have to go hunting around their filesystem for it.
16543 - Return a robots.txt on our dirport to discourage google indexing.
16544 - Let the controller ask for GETINFO dir/status/foo so it can ask
16545 directly rather than connecting to the dir port. Only works when
16546 dirport is set for now.
16548 o New config options rather than constants in the code:
16549 - SocksTimeout: How long do we let a socks connection wait
16550 unattached before we fail it?
16551 - CircuitBuildTimeout: Cull non-open circuits that were born
16552 at least this many seconds ago.
16553 - CircuitIdleTimeout: Cull open clean circuits that were born
16554 at least this many seconds ago.
16557 Changes in version 0.1.1.16-rc - 2006-03-18
16558 o Bugfixes on 0.1.1.15-rc:
16559 - Fix assert when the controller asks to attachstream a connect-wait
16560 or resolve-wait stream.
16561 - Now do address rewriting when the controller asks us to attach
16562 to a particular circuit too. This will let Blossom specify
16563 "moria2.exit" without having to learn what moria2's IP address is.
16564 - Make the "tor --verify-config" command-line work again, so people
16565 can automatically check if their torrc will parse.
16566 - Authoritative dirservers no longer require an open connection from
16567 a server to consider him "reachable". We need this change because
16568 when we add new auth dirservers, old servers won't know not to
16570 - Let Tor build on Sun CC again.
16571 - Fix an off-by-one buffer size in dirserv.c that magically never
16572 hit our three authorities but broke sjmurdoch's own tor network.
16573 - If we as a directory mirror don't know of any v1 directory
16574 authorities, then don't try to cache any v1 directories.
16575 - Stop warning about unknown servers in our family when they are
16576 given as hex digests.
16577 - Stop complaining as quickly to the server operator that he
16578 hasn't registered his nickname/key binding.
16579 - Various cleanups so we can add new V2 Auth Dirservers.
16580 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16581 reflect the updated flags in our v2 dir protocol.
16582 - Resume allowing non-printable characters for exit streams (both
16583 for connecting and for resolving). Now we tolerate applications
16584 that don't follow the RFCs. But continue to block malformed names
16587 o Bugfixes on 0.1.0.x:
16588 - Fix assert bug in close_logs(): when we close and delete logs,
16589 remove them all from the global "logfiles" list.
16590 - Fix minor integer overflow in calculating when we expect to use up
16591 our bandwidth allocation before hibernating.
16592 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
16593 there are multiple SSLs installed with different versions.
16594 - When we try to be a server and Address is not explicitly set and
16595 our hostname resolves to a private IP address, try to use an
16596 interface address if it has a public address. Now Windows machines
16597 that think of themselves as localhost can work by default.
16600 - Let the controller ask for GETINFO dir/server/foo so it can ask
16601 directly rather than connecting to the dir port.
16602 - Let the controller tell us about certain router descriptors
16603 that it doesn't want Tor to use in circuits. Implement
16604 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
16605 - New config option SafeSocks to reject all application connections
16606 using unsafe socks protocols. Defaults to off.
16609 Changes in version 0.1.1.15-rc - 2006-03-11
16610 o Bugfixes and cleanups:
16611 - When we're printing strings from the network, don't try to print
16612 non-printable characters. This protects us against shell escape
16613 sequence exploits, and also against attacks to fool humans into
16614 misreading their logs.
16615 - Fix a bug where Tor would fail to establish any connections if you
16616 left it off for 24 hours and then started it: we were happy with
16617 the obsolete network statuses, but they all referred to router
16618 descriptors that were too old to fetch, so we ended up with no
16619 valid router descriptors.
16620 - Fix a seg fault in the controller's "getinfo orconn-status"
16621 command while listing status on incoming handshaking connections.
16622 Introduce a status name "NEW" for these connections.
16623 - If we get a linelist or linelist_s config option from the torrc
16624 (e.g. ExitPolicy) and it has no value, warn and skip rather than
16625 silently resetting it to its default.
16626 - Don't abandon entry guards until they've been down or gone for
16628 - Cleaner and quieter log messages.
16631 - New controller signal NEWNYM that makes new application requests
16632 use clean circuits.
16633 - Add a new circuit purpose 'controller' to let the controller ask
16634 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
16635 controller command to let you specify the purpose if you're
16636 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
16637 command to let you change a circuit's purpose after it's been
16639 - Accept "private:*" in routerdesc exit policies; not generated yet
16640 because older Tors do not understand it.
16641 - Add BSD-style contributed startup script "rc.subr" from Peter
16645 Changes in version 0.1.1.14-alpha - 2006-02-20
16646 o Bugfixes on 0.1.1.x:
16647 - Don't die if we ask for a stdout or stderr log (even implicitly)
16648 and we're set to RunAsDaemon -- just warn.
16649 - We still had a few bugs in the OR connection rotation code that
16650 caused directory servers to slowly aggregate connections to other
16651 fast Tor servers. This time for sure!
16652 - Make log entries on Win32 include the name of the function again.
16653 - We were treating a pair of exit policies if they were equal even
16654 if one said accept and the other said reject -- causing us to
16655 not always publish a new descriptor since we thought nothing
16657 - Retry pending server downloads as well as pending networkstatus
16658 downloads when we unexpectedly get a socks request.
16659 - We were ignoring the IS_FAST flag in the directory status,
16660 meaning we were willing to pick trivial-bandwidth nodes for "fast"
16662 - If the controller's SAVECONF command fails (e.g. due to file
16663 permissions), let the controller know that it failed.
16666 - If we're trying to be a Tor server and running Windows 95/98/ME
16667 as a server, explain that we'll likely crash.
16668 - When we're a server, a client asks for an old-style directory,
16669 and our write bucket is empty, don't give it to him. This way
16670 small servers can continue to serve the directory *sometimes*,
16671 without getting overloaded.
16672 - Compress exit policies even more -- look for duplicate lines
16674 - Clients now honor the "guard" flag in the router status when
16675 picking entry guards, rather than looking at is_fast or is_stable.
16676 - Retain unrecognized lines in $DATADIR/state file, so that we can
16677 be forward-compatible.
16678 - Generate 18.0.0.0/8 address policy format in descs when we can;
16679 warn when the mask is not reducible to a bit-prefix.
16680 - Let the user set ControlListenAddress in the torrc. This can be
16681 dangerous, but there are some cases (like a secured LAN) where it
16683 - Split ReachableAddresses into ReachableDirAddresses and
16684 ReachableORAddresses, so we can restrict Dir conns to port 80
16685 and OR conns to port 443.
16686 - Now we can target arch and OS in rpm builds (contributed by
16687 Phobos). Also make the resulting dist-rpm filename match the
16689 - New config options to help controllers: FetchServerDescriptors
16690 and FetchHidServDescriptors for whether to fetch server
16691 info and hidserv info or let the controller do it, and
16692 PublishServerDescriptor and PublishHidServDescriptors.
16693 - Also let the controller set the __AllDirActionsPrivate config
16694 option if you want all directory fetches/publishes to happen via
16695 Tor (it assumes your controller bootstraps your circuits).
16698 Changes in version 0.1.0.17 - 2006-02-17
16699 o Crash bugfixes on 0.1.0.x:
16700 - When servers with a non-zero DirPort came out of hibernation,
16701 sometimes they would trigger an assert.
16703 o Other important bugfixes:
16704 - On platforms that don't have getrlimit (like Windows), we were
16705 artificially constraining ourselves to a max of 1024
16706 connections. Now just assume that we can handle as many as 15000
16707 connections. Hopefully this won't cause other problems.
16709 o Backported features:
16710 - When we're a server, a client asks for an old-style directory,
16711 and our write bucket is empty, don't give it to him. This way
16712 small servers can continue to serve the directory *sometimes*,
16713 without getting overloaded.
16714 - Whenever you get a 503 in response to a directory fetch, try
16715 once more. This will become important once servers start sending
16716 503's whenever they feel busy.
16717 - Fetch a new directory every 120 minutes, not every 40 minutes.
16718 Now that we have hundreds of thousands of users running the old
16719 directory algorithm, it's starting to hurt a lot.
16720 - Bump up the period for forcing a hidden service descriptor upload
16721 from 20 minutes to 1 hour.
16724 Changes in version 0.1.1.13-alpha - 2006-02-09
16725 o Crashes in 0.1.1.x:
16726 - When you tried to setconf ORPort via the controller, Tor would
16727 crash. So people using TorCP to become a server were sad.
16728 - Solve (I hope) the stack-smashing bug that we were seeing on fast
16729 servers. The problem appears to be something do with OpenSSL's
16730 random number generation, or how we call it, or something. Let me
16731 know if the crashes continue.
16732 - Turn crypto hardware acceleration off by default, until we find
16733 somebody smart who can test it for us. (It appears to produce
16734 seg faults in at least some cases.)
16735 - Fix a rare assert error when we've tried all intro points for
16736 a hidden service and we try fetching the service descriptor again:
16737 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
16740 - Fix a major load balance bug: we were round-robining in 16 KB
16741 chunks, and servers with bandwidthrate of 20 KB, while downloading
16742 a 600 KB directory, would starve their other connections. Now we
16743 try to be a bit more fair.
16744 - Dir authorities and mirrors were never expiring the newest
16745 descriptor for each server, causing memory and directory bloat.
16746 - Fix memory-bloating and connection-bloating bug on servers: We
16747 were never closing any connection that had ever had a circuit on
16748 it, because we were checking conn->n_circuits == 0, yet we had a
16749 bug that let it go negative.
16750 - Make Tor work using squid as your http proxy again -- squid
16751 returns an error if you ask for a URL that's too long, and it uses
16752 a really generic error message. Plus, many people are behind a
16753 transparent squid so they don't even realize it.
16754 - On platforms that don't have getrlimit (like Windows), we were
16755 artificially constraining ourselves to a max of 1024
16756 connections. Now just assume that we can handle as many as 15000
16757 connections. Hopefully this won't cause other problems.
16758 - Add a new config option ExitPolicyRejectPrivate which defaults to
16759 1. This means all exit policies will begin with rejecting private
16760 addresses, unless the server operator explicitly turns it off.
16763 - Clients no longer download descriptors for non-running
16765 - Before we add new directory authorities, we should make it
16766 clear that only v1 authorities should receive/publish hidden
16767 service descriptors.
16770 - As soon as we've fetched some more directory info, immediately
16771 try to download more server descriptors. This way we don't have
16772 a 10 second pause during initial bootstrapping.
16773 - Remove even more loud log messages that the server operator can't
16775 - When we're running an obsolete or un-recommended version, make
16776 the log message more clear about what the problem is and what
16777 versions *are* still recommended.
16778 - Provide a more useful warn message when our onion queue gets full:
16779 the CPU is too slow or the exit policy is too liberal.
16780 - Don't warn when we receive a 503 from a dirserver/cache -- this
16781 will pave the way for them being able to refuse if they're busy.
16782 - When we fail to bind a listener, try to provide a more useful
16783 log message: e.g., "Is Tor already running?"
16784 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
16785 Goldberg can prove things about our handshake protocol more
16787 - MaxConn has been obsolete for a while now. Document the ConnLimit
16788 config option, which is a *minimum* number of file descriptors
16789 that must be available else Tor refuses to start.
16790 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16791 if you log to syslog and want something other than LOG_DAEMON.
16792 - Make dirservers generate a separate "guard" flag to mean,
16793 "would make a good entry guard". Make clients parse it and vote
16794 on it. Not used by clients yet.
16795 - Implement --with-libevent-dir option to ./configure. Also, improve
16796 search techniques to find libevent, and use those for openssl too.
16797 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
16798 - Only start testing reachability once we've established a
16799 circuit. This will make startup on dirservers less noisy.
16800 - Don't try to upload hidden service descriptors until we have
16801 established a circuit.
16802 - Fix the controller's "attachstream 0" command to treat conn like
16803 it just connected, doing address remapping, handling .exit and
16804 .onion idioms, and so on. Now we're more uniform in making sure
16805 that the controller hears about new and closing connections.
16808 Changes in version 0.1.1.12-alpha - 2006-01-11
16809 o Bugfixes on 0.1.1.x:
16810 - The fix to close duplicate server connections was closing all
16811 Tor client connections if they didn't establish a circuit
16812 quickly enough. Oops.
16813 - Fix minor memory issue (double-free) that happened on exit.
16815 o Bugfixes on 0.1.0.x:
16816 - Tor didn't warn when it failed to open a log file.
16819 Changes in version 0.1.1.11-alpha - 2006-01-10
16820 o Crashes in 0.1.1.x:
16821 - Include all the assert/crash fixes from 0.1.0.16.
16822 - If you start Tor and then quit very quickly, there were some
16823 races that tried to free things that weren't allocated yet.
16824 - Fix a rare memory stomp if you're running hidden services.
16825 - Fix segfault when specifying DirServer in config without nickname.
16826 - Fix a seg fault when you finish connecting to a server but at
16827 that moment you dump his server descriptor.
16828 - Extendcircuit and Attachstream controller commands would
16829 assert/crash if you don't give them enough arguments.
16830 - Fix an assert error when we're out of space in the connection_list
16831 and we try to post a hidden service descriptor (reported by weasel).
16832 - If you specify a relative torrc path and you set RunAsDaemon in
16833 your torrc, then it chdir()'s to the new directory. If you HUP,
16834 it tries to load the new torrc location, fails, and exits.
16835 The fix: no longer allow a relative path to torrc using -f.
16838 - Implement "entry guards": automatically choose a handful of entry
16839 nodes and stick with them for all circuits. Only pick new guards
16840 when the ones you have are unsuitable, and if the old guards
16841 become suitable again, switch back. This will increase security
16842 dramatically against certain end-point attacks. The EntryNodes
16843 config option now provides some hints about which entry guards you
16844 want to use most; and StrictEntryNodes means to only use those.
16845 - New directory logic: download by descriptor digest, not by
16846 fingerprint. Caches try to download all listed digests from
16847 authorities; clients try to download "best" digests from caches.
16848 This avoids partitioning and isolating attacks better.
16849 - Make the "stable" router flag in network-status be the median of
16850 the uptimes of running valid servers, and make clients pay
16851 attention to the network-status flags. Thus the cutoff adapts
16852 to the stability of the network as a whole, making IRC, IM, etc
16853 connections more reliable.
16856 - Tor servers with dynamic IP addresses were needing to wait 18
16857 hours before they could start doing reachability testing using
16858 the new IP address and ports. This is because they were using
16859 the internal descriptor to learn what to test, yet they were only
16860 rebuilding the descriptor once they decided they were reachable.
16861 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
16862 to download certain server descriptors, throw them away, and then
16863 fetch them again after 30 minutes. Now mirrors throw away these
16864 server descriptors so clients can't get them.
16865 - We were leaving duplicate connections to other ORs open for a week,
16866 rather than closing them once we detect a duplicate. This only
16867 really affected authdirservers, but it affected them a lot.
16868 - Spread the authdirservers' reachability testing over the entire
16869 testing interval, so we don't try to do 500 TLS's at once every
16873 - If the network is down, and we try to connect to a conn because
16874 we have a circuit in mind, and we timeout (30 seconds) because the
16875 network never answers, we were expiring the circuit, but we weren't
16876 obsoleting the connection or telling the entry_guards functions.
16877 - Some Tor servers process billions of cells per day. These statistics
16878 need to be uint64_t's.
16879 - Check for integer overflows in more places, when adding elements
16880 to smartlists. This could possibly prevent a buffer overflow
16881 on malicious huge inputs. I don't see any, but I haven't looked
16883 - ReachableAddresses kept growing new "reject *:*" lines on every
16885 - When you "setconf log" via the controller, it should remove all
16886 logs. We were automatically adding back in a "log notice stdout".
16887 - Newly bootstrapped Tor networks couldn't establish hidden service
16888 circuits until they had nodes with high uptime. Be more tolerant.
16889 - We were marking servers down when they could not answer every piece
16890 of the directory request we sent them. This was far too harsh.
16891 - Fix the torify (tsocks) config file to not use Tor for localhost
16893 - Directory authorities now go to the proper authority when asking for
16894 a networkstatus, even when they want a compressed one.
16895 - Fix a harmless bug that was causing Tor servers to log
16896 "Got an end because of misc error, but we're not an AP. Closing."
16897 - Authorities were treating their own descriptor changes as cosmetic,
16898 meaning the descriptor available in the network-status and the
16899 descriptor that clients downloaded were different.
16900 - The OS X installer was adding a symlink for tor_resolve but
16901 the binary was called tor-resolve (reported by Thomas Hardly).
16902 - Workaround a problem with some http proxies where they refuse GET
16903 requests that specify "Content-Length: 0" (reported by Adrian).
16904 - Fix wrong log message when you add a "HiddenServiceNodes" config
16905 line without any HiddenServiceDir line (reported by Chris Thomas).
16908 - Write the TorVersion into the state file so we have a prayer of
16909 keeping forward and backward compatibility.
16910 - Revive the FascistFirewall config option rather than eliminating it:
16911 now it's a synonym for ReachableAddresses *:80,*:443.
16912 - Clients choose directory servers from the network status lists,
16913 not from their internal list of router descriptors. Now they can
16914 go to caches directly rather than needing to go to authorities
16916 - Directory authorities ignore router descriptors that have only
16917 cosmetic differences: do this for 0.1.0.x servers now too.
16918 - Add a new flag to network-status indicating whether the server
16919 can answer v2 directory requests too.
16920 - Authdirs now stop whining so loudly about bad descriptors that
16921 they fetch from other dirservers. So when there's a log complaint,
16922 it's for sure from a freshly uploaded descriptor.
16923 - Reduce memory requirements in our structs by changing the order
16925 - There used to be two ways to specify your listening ports in a
16926 server descriptor: on the "router" line and with a separate "ports"
16927 line. Remove support for the "ports" line.
16928 - New config option "AuthDirRejectUnlisted" for auth dirservers as
16929 a panic button: if we get flooded with unusable servers we can
16930 revert to only listing servers in the approved-routers file.
16931 - Auth dir servers can now mark a fingerprint as "!reject" or
16932 "!invalid" in the approved-routers file (as its nickname), to
16933 refuse descriptors outright or include them but marked as invalid.
16934 - Servers store bandwidth history across restarts/crashes.
16935 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16936 get a better idea of why their circuits failed. Not used yet.
16937 - Directory mirrors now cache up to 16 unrecognized network-status
16938 docs. Now we can add new authdirservers and they'll be cached too.
16939 - When picking a random directory, prefer non-authorities if any
16941 - New controller option "getinfo desc/all-recent" to fetch the
16942 latest server descriptor for every router that Tor knows about.
16945 Changes in version 0.1.0.16 - 2006-01-02
16946 o Crash bugfixes on 0.1.0.x:
16947 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16948 corrupting the heap, losing FDs, or crashing when we need to resize
16949 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16950 - It turns out sparc64 platforms crash on unaligned memory access
16951 too -- so detect and avoid this.
16952 - Handle truncated compressed data correctly (by detecting it and
16954 - Fix possible-but-unlikely free(NULL) in control.c.
16955 - When we were closing connections, there was a rare case that
16956 stomped on memory, triggering seg faults and asserts.
16957 - Avoid potential infinite recursion when building a descriptor. (We
16958 don't know that it ever happened, but better to fix it anyway.)
16959 - We were neglecting to unlink marked circuits from soon-to-close OR
16960 connections, which caused some rare scribbling on freed memory.
16961 - Fix a memory stomping race bug when closing the joining point of two
16962 rendezvous circuits.
16963 - Fix an assert in time parsing found by Steven Murdoch.
16965 o Other bugfixes on 0.1.0.x:
16966 - When we're doing reachability testing, provide more useful log
16967 messages so the operator knows what to expect.
16968 - Do not check whether DirPort is reachable when we are suppressing
16969 advertising it because of hibernation.
16970 - When building with -static or on Solaris, we sometimes needed -ldl.
16971 - When we're deciding whether a stream has enough circuits around
16972 that can handle it, count the freshly dirty ones and not the ones
16973 that are so dirty they won't be able to handle it.
16974 - When we're expiring old circuits, we had a logic error that caused
16975 us to close new rendezvous circuits rather than old ones.
16976 - Give a more helpful log message when you try to change ORPort via
16977 the controller: you should upgrade Tor if you want that to work.
16978 - We were failing to parse Tor versions that start with "Tor ".
16979 - Tolerate faulty streams better: when a stream fails for reason
16980 exitpolicy, stop assuming that the router is lying about his exit
16981 policy. When a stream fails for reason misc, allow it to retry just
16982 as if it was resolvefailed. When a stream has failed three times,
16983 reset its failure count so we can try again and get all three tries.
16986 Changes in version 0.1.1.10-alpha - 2005-12-11
16987 o Correctness bugfixes on 0.1.0.x:
16988 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16989 corrupting the heap, losing FDs, or crashing when we need to resize
16990 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16991 - Stop doing the complex voodoo overkill checking for insecure
16992 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16993 - When we were closing connections, there was a rare case that
16994 stomped on memory, triggering seg faults and asserts.
16995 - We were neglecting to unlink marked circuits from soon-to-close OR
16996 connections, which caused some rare scribbling on freed memory.
16997 - When we're deciding whether a stream has enough circuits around
16998 that can handle it, count the freshly dirty ones and not the ones
16999 that are so dirty they won't be able to handle it.
17000 - Recover better from TCP connections to Tor servers that are
17001 broken but don't tell you (it happens!); and rotate TLS
17002 connections once a week.
17003 - When we're expiring old circuits, we had a logic error that caused
17004 us to close new rendezvous circuits rather than old ones.
17005 - Fix a scary-looking but apparently harmless bug where circuits
17006 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17007 servers, and never switch to state CIRCUIT_STATE_OPEN.
17008 - When building with -static or on Solaris, we sometimes needed to
17010 - Give a useful message when people run Tor as the wrong user,
17011 rather than telling them to start chowning random directories.
17012 - We were failing to inform the controller about new .onion streams.
17014 o Security bugfixes on 0.1.0.x:
17015 - Refuse server descriptors if the fingerprint line doesn't match
17016 the included identity key. Tor doesn't care, but other apps (and
17017 humans) might actually be trusting the fingerprint line.
17018 - We used to kill the circuit when we receive a relay command we
17019 don't recognize. Now we just drop it.
17020 - Start obeying our firewall options more rigorously:
17021 . If we can't get to a dirserver directly, try going via Tor.
17022 . Don't ever try to connect (as a client) to a place our
17023 firewall options forbid.
17024 . If we specify a proxy and also firewall options, obey the
17025 firewall options even when we're using the proxy: some proxies
17026 can only proxy to certain destinations.
17027 - Fix a bug found by Lasse Overlier: when we were making internal
17028 circuits (intended to be cannibalized later for rendezvous and
17029 introduction circuits), we were picking them so that they had
17030 useful exit nodes. There was no need for this, and it actually
17031 aids some statistical attacks.
17032 - Start treating internal circuits and exit circuits separately.
17033 It's important to keep them separate because internal circuits
17034 have their last hops picked like middle hops, rather than like
17035 exit hops. So exiting on them will break the user's expectations.
17037 o Bugfixes on 0.1.1.x:
17038 - Take out the mis-feature where we tried to detect IP address
17039 flapping for people with DynDNS, and chose not to upload a new
17040 server descriptor sometimes.
17041 - Try to be compatible with OpenSSL 0.9.6 again.
17042 - Log fix: when the controller is logging about .onion addresses,
17043 sometimes it didn't include the ".onion" part of the address.
17044 - Don't try to modify options->DirServers internally -- if the
17045 user didn't specify any, just add the default ones directly to
17046 the trusted dirserver list. This fixes a bug where people running
17047 controllers would use SETCONF on some totally unrelated config
17048 option, and Tor would start yelling at them about changing their
17050 - Let the controller's redirectstream command specify a port, in
17051 case the controller wants to change that too.
17052 - When we requested a pile of server descriptors, we sometimes
17053 accidentally launched a duplicate request for the first one.
17054 - Bugfix for trackhostexits: write down the fingerprint of the
17055 chosen exit, not its nickname, because the chosen exit might not
17057 - When parsing foo.exit, if foo is unknown, and we are leaving
17058 circuits unattached, set the chosen_exit field and leave the
17059 address empty. This matters because controllers got confused
17061 - Directory authorities no longer try to download server
17062 descriptors that they know they will reject.
17064 o Features and updates:
17065 - Replace balanced trees with hash tables: this should make stuff
17066 significantly faster.
17067 - Resume using the AES counter-mode implementation that we ship,
17068 rather than OpenSSL's. Ours is significantly faster.
17069 - Many other CPU and memory improvements.
17070 - Add a new config option FastFirstHopPK (on by default) so clients
17071 do a trivial crypto handshake for their first hop, since TLS has
17072 already taken care of confidentiality and authentication.
17073 - Add a new config option TestSocks so people can see if their
17074 applications are using socks4, socks4a, socks5-with-ip, or
17075 socks5-with-hostname. This way they don't have to keep mucking
17076 with tcpdump and wondering if something got cached somewhere.
17077 - Warn when listening on a public address for socks. I suspect a
17078 lot of people are setting themselves up as open socks proxies,
17079 and they have no idea that jerks on the Internet are using them,
17080 since they simply proxy the traffic into the Tor network.
17081 - Add "private:*" as an alias in configuration for policies. Now
17082 you can simplify your exit policy rather than needing to list
17083 every single internal or nonroutable network space.
17084 - Add a new controller event type that allows controllers to get
17085 all server descriptors that were uploaded to a router in its role
17086 as authoritative dirserver.
17087 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17088 tor-doc-server.html, and stylesheet.css in the tarball.
17089 - Stop shipping tor-doc.html in the tarball.
17092 Changes in version 0.1.1.9-alpha - 2005-11-15
17093 o Usability improvements:
17094 - Start calling it FooListenAddress rather than FooBindAddress,
17095 since few of our users know what it means to bind an address
17097 - Reduce clutter in server logs. We're going to try to make
17098 them actually usable now. New config option ProtocolWarnings that
17099 lets you hear about how _other Tors_ are breaking the protocol. Off
17101 - Divide log messages into logging domains. Once we put some sort
17102 of interface on this, it will let people looking at more verbose
17103 log levels specify the topics they want to hear more about.
17104 - Make directory servers return better http 404 error messages
17105 instead of a generic "Servers unavailable".
17106 - Check for even more Windows version flags when writing the platform
17107 string in server descriptors, and note any we don't recognize.
17108 - Clean up more of the OpenSSL memory when exiting, so we can detect
17109 memory leaks better.
17110 - Make directory authorities be non-versioning, non-naming by
17111 default. Now we can add new directory servers without requiring
17112 their operators to pay close attention.
17113 - When logging via syslog, include the pid whenever we provide
17114 a log entry. Suggested by Todd Fries.
17116 o Performance improvements:
17117 - Directory servers now silently throw away new descriptors that
17118 haven't changed much if the timestamps are similar. We do this to
17119 tolerate older Tor servers that upload a new descriptor every 15
17120 minutes. (It seemed like a good idea at the time.)
17121 - Inline bottleneck smartlist functions; use fast versions by default.
17122 - Add a "Map from digest to void*" abstraction digestmap_t so we
17123 can do less hex encoding/decoding. Use it in router_get_by_digest()
17124 to resolve a performance bottleneck.
17125 - Allow tor_gzip_uncompress to extract as much as possible from
17126 truncated compressed data. Try to extract as many
17127 descriptors as possible from truncated http responses (when
17128 DIR_PURPOSE_FETCH_ROUTERDESC).
17129 - Make circ->onionskin a pointer, not a static array. moria2 was using
17130 125000 circuit_t's after it had been up for a few weeks, which
17131 translates to 20+ megs of wasted space.
17132 - The private half of our EDH handshake keys are now chosen out
17133 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17135 o Security improvements:
17136 - Start making directory caches retain old routerinfos, so soon
17137 clients can start asking by digest of descriptor rather than by
17138 fingerprint of server.
17139 - Add half our entropy from RAND_poll in OpenSSL. This knows how
17140 to use egd (if present), openbsd weirdness (if present), vms/os2
17141 weirdness (if we ever port there), and more in the future.
17143 o Bugfixes on 0.1.0.x:
17144 - Do round-robin writes of at most 16 kB per write. This might be
17145 more fair on loaded Tor servers, and it might resolve our Windows
17146 crash bug. It might also slow things down.
17147 - Our TLS handshakes were generating a single public/private
17148 keypair for the TLS context, rather than making a new one for
17149 each new connections. Oops. (But we were still rotating them
17150 periodically, so it's not so bad.)
17151 - When we were cannibalizing a circuit with a particular exit
17152 node in mind, we weren't checking to see if that exit node was
17153 already present earlier in the circuit. Oops.
17154 - When a Tor server's IP changes (e.g. from a dyndns address),
17155 upload a new descriptor so clients will learn too.
17156 - Really busy servers were keeping enough circuits open on stable
17157 connections that they were wrapping around the circuit_id
17158 space. (It's only two bytes.) This exposed a bug where we would
17159 feel free to reuse a circuit_id even if it still exists but has
17160 been marked for close. Try to fix this bug. Some bug remains.
17161 - If we would close a stream early (e.g. it asks for a .exit that
17162 we know would refuse it) but the LeaveStreamsUnattached config
17163 option is set by the controller, then don't close it.
17165 o Bugfixes on 0.1.1.8-alpha:
17166 - Fix a big pile of memory leaks, some of them serious.
17167 - Do not try to download a routerdesc if we would immediately reject
17169 - Resume inserting a newline between all router descriptors when
17170 generating (old style) signed directories, since our spec says
17172 - When providing content-type application/octet-stream for
17173 server descriptors using .z, we were leaving out the
17174 content-encoding header. Oops. (Everything tolerated this just
17175 fine, but that doesn't mean we need to be part of the problem.)
17176 - Fix a potential seg fault in getconf and getinfo using version 1
17177 of the controller protocol.
17178 - Avoid crash: do not check whether DirPort is reachable when we
17179 are suppressing it because of hibernation.
17180 - Make --hash-password not crash on exit.
17183 Changes in version 0.1.1.8-alpha - 2005-10-07
17184 o New features (major):
17185 - Clients don't download or use the directory anymore. Now they
17186 download and use network-statuses from the trusted dirservers,
17187 and fetch individual server descriptors as needed from mirrors.
17188 See dir-spec.txt for all the gory details.
17189 - Be more conservative about whether to advertise our DirPort.
17190 The main change is to not advertise if we're running at capacity
17191 and either a) we could hibernate or b) our capacity is low and
17192 we're using a default DirPort.
17193 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
17195 o New features (minor):
17196 - Try to be smart about when to retry network-status and
17197 server-descriptor fetches. Still needs some tuning.
17198 - Stop parsing, storing, or using running-routers output (but
17199 mirrors still cache and serve it).
17200 - Consider a threshold of versioning dirservers (dirservers who have
17201 an opinion about which Tor versions are still recommended) before
17202 deciding whether to warn the user that he's obsolete.
17203 - Dirservers can now reject/invalidate by key and IP, with the
17204 config options "AuthDirInvalid" and "AuthDirReject". This is
17205 useful since currently we automatically list servers as running
17206 and usable even if we know they're jerks.
17207 - Provide dire warnings to any users who set DirServer; move it out
17208 of torrc.sample and into torrc.complete.
17209 - Add MyFamily to torrc.sample in the server section.
17210 - Add nicknames to the DirServer line, so we can refer to them
17211 without requiring all our users to memorize their IP addresses.
17212 - When we get an EOF or a timeout on a directory connection, note
17213 how many bytes of serverdesc we are dropping. This will help
17214 us determine whether it is smart to parse incomplete serverdesc
17216 - Add a new function to "change pseudonyms" -- that is, to stop
17217 using any currently-dirty circuits for new streams, so we don't
17218 link new actions to old actions. Currently it's only called on
17219 HUP (or SIGNAL RELOAD).
17220 - On sighup, if UseHelperNodes changed to 1, use new circuits.
17221 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17222 OpenSSL. Also, reseed our entropy every hour, not just at
17223 startup. And entropy in 512-bit chunks, not 160-bit chunks.
17225 o Fixes on 0.1.1.7-alpha:
17226 - Nobody ever implemented EVENT_ADDRMAP for control protocol
17227 version 0, so don't let version 0 controllers ask for it.
17228 - If you requested something with too many newlines via the
17229 v1 controller protocol, you could crash tor.
17230 - Fix a number of memory leaks, including some pretty serious ones.
17231 - Re-enable DirPort testing again, so Tor servers will be willing
17232 to advertise their DirPort if it's reachable.
17233 - On TLS handshake, only check the other router's nickname against
17234 its expected nickname if is_named is set.
17236 o Fixes forward-ported from 0.1.0.15:
17237 - Don't crash when we don't have any spare file descriptors and we
17238 try to spawn a dns or cpu worker.
17239 - Make the numbers in read-history and write-history into uint64s,
17240 so they don't overflow and publish negatives in the descriptor.
17242 o Fixes on 0.1.0.x:
17243 - For the OS X package's modified privoxy config file, comment
17244 out the "logfile" line so we don't log everything passed
17246 - We were whining about using socks4 or socks5-with-local-lookup
17247 even when it's an IP in the "virtual" range we designed exactly
17249 - We were leaking some memory every time the client changes IPs.
17250 - Never call free() on tor_malloc()d memory. This will help us
17251 use dmalloc to detect memory leaks.
17252 - Check for named servers when looking them up by nickname;
17253 warn when we'recalling a non-named server by its nickname;
17254 don't warn twice about the same name.
17255 - Try to list MyFamily elements by key, not by nickname, and warn
17256 if we've not heard of the server.
17257 - Make windows platform detection (uname equivalent) smarter.
17258 - It turns out sparc64 doesn't like unaligned access either.
17261 Changes in version 0.1.0.15 - 2005-09-23
17262 o Bugfixes on 0.1.0.x:
17263 - Reject ports 465 and 587 (spam targets) in default exit policy.
17264 - Don't crash when we don't have any spare file descriptors and we
17265 try to spawn a dns or cpu worker.
17266 - Get rid of IgnoreVersion undocumented config option, and make us
17267 only warn, never exit, when we're running an obsolete version.
17268 - Don't try to print a null string when your server finds itself to
17269 be unreachable and the Address config option is empty.
17270 - Make the numbers in read-history and write-history into uint64s,
17271 so they don't overflow and publish negatives in the descriptor.
17272 - Fix a minor memory leak in smartlist_string_remove().
17273 - We were only allowing ourselves to upload a server descriptor at
17274 most every 20 minutes, even if it changed earlier than that.
17275 - Clean up log entries that pointed to old URLs.
17278 Changes in version 0.1.1.7-alpha - 2005-09-14
17279 o Fixes on 0.1.1.6-alpha:
17280 - Exit servers were crashing when people asked them to make a
17281 connection to an address not in their exit policy.
17282 - Looking up a non-existent stream for a v1 control connection would
17284 - Fix a seg fault if we ask a dirserver for a descriptor by
17285 fingerprint but he doesn't know about him.
17286 - SETCONF was appending items to linelists, not clearing them.
17287 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
17288 out and refuse the setconf if it would fail.
17289 - Downgrade the dirserver log messages when whining about
17293 - Add Peter Palfrader's check-tor script to tor/contrib/
17294 It lets you easily check whether a given server (referenced by
17295 nickname) is reachable by you.
17296 - Numerous changes to move towards client-side v2 directories. Not
17299 o Fixes on 0.1.0.x:
17300 - If the user gave tor an odd number of command-line arguments,
17301 we were silently ignoring the last one. Now we complain and fail.
17302 [This wins the oldest-bug prize -- this bug has been present since
17303 November 2002, as released in Tor 0.0.0.]
17304 - Do not use unaligned memory access on alpha, mips, or mipsel.
17305 It *works*, but is very slow, so we treat them as if it doesn't.
17306 - Retry directory requests if we fail to get an answer we like
17307 from a given dirserver (we were retrying before, but only if
17308 we fail to connect).
17309 - When writing the RecommendedVersions line, sort them first.
17310 - When the client asked for a rendezvous port that the hidden
17311 service didn't want to provide, we were sending an IP address
17312 back along with the end cell. Fortunately, it was zero. But stop
17314 - Correct "your server is reachable" log entries to indicate that
17315 it was self-testing that told us so.
17318 Changes in version 0.1.1.6-alpha - 2005-09-09
17319 o Fixes on 0.1.1.5-alpha:
17320 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
17321 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
17322 - Fix bug with tor_memmem finding a match at the end of the string.
17323 - Make unit tests run without segfaulting.
17324 - Resolve some solaris x86 compile warnings.
17325 - Handle duplicate lines in approved-routers files without warning.
17326 - Fix bug where as soon as a server refused any requests due to his
17327 exit policy (e.g. when we ask for localhost and he tells us that's
17328 127.0.0.1 and he won't do it), we decided he wasn't obeying his
17329 exit policy using him for any exits.
17330 - Only do openssl hardware accelerator stuff if openssl version is
17333 o New controller features/fixes:
17334 - Add a "RESETCONF" command so you can set config options like
17335 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17336 a config option in the torrc with no value, then it clears it
17337 entirely (rather than setting it to its default).
17338 - Add a "GETINFO config-file" to tell us where torrc is.
17339 - Avoid sending blank lines when GETINFO replies should be empty.
17340 - Add a QUIT command for the controller (for using it manually).
17341 - Fix a bug in SAVECONF that was adding default dirservers and
17342 other redundant entries to the torrc file.
17344 o Start on the new directory design:
17345 - Generate, publish, cache, serve new network-status format.
17346 - Publish individual descriptors (by fingerprint, by "all", and by
17348 - Publish client and server recommended versions separately.
17349 - Allow tor_gzip_uncompress() to handle multiple concatenated
17350 compressed strings. Serve compressed groups of router
17351 descriptors. The compression logic here could be more
17353 - Distinguish v1 authorities (all currently trusted directories)
17354 from v2 authorities (all trusted directories).
17355 - Change DirServers config line to note which dirs are v1 authorities.
17356 - Add configuration option "V1AuthoritativeDirectory 1" which
17357 moria1, moria2, and tor26 should set.
17358 - Remove option when getting directory cache to see whether they
17359 support running-routers; they all do now. Replace it with one
17360 to see whether caches support v2 stuff.
17363 - Dirservers now do their own external reachability testing of each
17364 Tor server, and only list them as running if they've been found to
17365 be reachable. We also send back warnings to the server's logs if
17366 it uploads a descriptor that we already believe is unreachable.
17367 - Implement exit enclaves: if we know an IP address for the
17368 destination, and there's a running Tor server at that address
17369 which allows exit to the destination, then extend the circuit to
17370 that exit first. This provides end-to-end encryption and end-to-end
17371 authentication. Also, if the user wants a .exit address or enclave,
17372 use 4 hops rather than 3, and cannibalize a general circ for it
17374 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
17375 controller. Also, rotate dns and cpu workers if the controller
17376 changes options that will affect them; and initialize the dns
17377 worker cache tree whether or not we start out as a server.
17378 - Only upload a new server descriptor when options change, 18
17379 hours have passed, uptime is reset, or bandwidth changes a lot.
17380 - Check [X-]Forwarded-For headers in HTTP requests when generating
17381 log messages. This lets people run dirservers (and caches) behind
17382 Apache but still know which IP addresses are causing warnings.
17384 o Config option changes:
17385 - Replace (Fascist)Firewall* config options with a new
17386 ReachableAddresses option that understands address policies.
17387 For example, "ReachableAddresses *:80,*:443"
17388 - Get rid of IgnoreVersion undocumented config option, and make us
17389 only warn, never exit, when we're running an obsolete version.
17390 - Make MonthlyAccountingStart config option truly obsolete now.
17392 o Fixes on 0.1.0.x:
17393 - Reject ports 465 and 587 in the default exit policy, since
17394 people have started using them for spam too.
17395 - It turns out we couldn't bootstrap a network since we added
17396 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17397 has never gone down. Add an AssumeReachable config option to let
17398 servers and dirservers bootstrap. When we're trying to build a
17399 high-uptime or high-bandwidth circuit but there aren't enough
17400 suitable servers, try being less picky rather than simply failing.
17401 - Our logic to decide if the OR we connected to was the right guy
17402 was brittle and maybe open to a mitm for unverified routers.
17403 - We weren't cannibalizing circuits correctly for
17404 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17405 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17406 build those from scratch. This should make hidden services faster.
17407 - Predict required circuits better, with an eye toward making hidden
17408 services faster on the service end.
17409 - Retry streams if the exit node sends back a 'misc' failure. This
17410 should result in fewer random failures. Also, after failing
17411 from resolve failed or misc, reset the num failures, so we give
17412 it a fair shake next time we try.
17413 - Clean up the rendezvous warn log msgs, and downgrade some to info.
17414 - Reduce severity on logs about dns worker spawning and culling.
17415 - When we're shutting down and we do something like try to post a
17416 server descriptor or rendezvous descriptor, don't complain that
17417 we seem to be unreachable. Of course we are, we're shutting down.
17418 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17419 We don't use them yet, but maybe one day our DNS resolver will be
17420 able to discover them.
17421 - Make ContactInfo mandatory for authoritative directory servers.
17422 - Require server descriptors to list IPv4 addresses -- hostnames
17423 are no longer allowed. This also fixes some potential security
17424 problems with people providing hostnames as their address and then
17425 preferentially resolving them to partition users.
17426 - Change log line for unreachability to explicitly suggest /etc/hosts
17427 as the culprit. Also make it clearer what IP address and ports we're
17428 testing for reachability.
17429 - Put quotes around user-supplied strings when logging so users are
17430 more likely to realize if they add bad characters (like quotes)
17432 - Let auth dir servers start without specifying an Address config
17434 - Make unit tests (and other invocations that aren't the real Tor)
17435 run without launching listeners, creating subdirectories, and so on.
17438 Changes in version 0.1.1.5-alpha - 2005-08-08
17439 o Bugfixes included in 0.1.0.14.
17441 o Bugfixes on 0.1.0.x:
17442 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17443 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17444 it would silently using ignore the 6668.
17447 Changes in version 0.1.0.14 - 2005-08-08
17448 o Bugfixes on 0.1.0.x:
17449 - Fix the other half of the bug with crypto handshakes
17451 - Fix an assert trigger if you send a 'signal term' via the
17452 controller when it's listening for 'event info' messages.
17455 Changes in version 0.1.1.4-alpha - 2005-08-04
17456 o Bugfixes included in 0.1.0.13.
17459 - Improve tor_gettimeofday() granularity on windows.
17460 - Make clients regenerate their keys when their IP address changes.
17461 - Implement some more GETINFO goodness: expose helper nodes, config
17462 options, getinfo keys.
17465 Changes in version 0.1.0.13 - 2005-08-04
17466 o Bugfixes on 0.1.0.x:
17467 - Fix a critical bug in the security of our crypto handshakes.
17468 - Fix a size_t underflow in smartlist_join_strings2() that made
17469 it do bad things when you hand it an empty smartlist.
17470 - Fix Windows installer to ship Tor license (thanks to Aphex for
17471 pointing out this oversight) and put a link to the doc directory
17473 - Explicitly set no-unaligned-access for sparc: it turns out the
17474 new gcc's let you compile broken code, but that doesn't make it
17478 Changes in version 0.1.1.3-alpha - 2005-07-23
17479 o Bugfixes on 0.1.1.2-alpha:
17480 - Fix a bug in handling the controller's "post descriptor"
17482 - Fix several bugs in handling the controller's "extend circuit"
17484 - Fix a bug in handling the controller's "stream status" event.
17485 - Fix an assert failure if we have a controller listening for
17486 circuit events and we go offline.
17487 - Re-allow hidden service descriptors to publish 0 intro points.
17488 - Fix a crash when generating your hidden service descriptor if
17489 you don't have enough intro points already.
17491 o New features on 0.1.1.2-alpha:
17492 - New controller function "getinfo accounting", to ask how
17493 many bytes we've used in this time period.
17494 - Experimental support for helper nodes: a lot of the risk from
17495 a small static adversary comes because users pick new random
17496 nodes every time they rebuild a circuit. Now users will try to
17497 stick to the same small set of entry nodes if they can. Not
17498 enabled by default yet.
17500 o Bugfixes on 0.1.0.12:
17501 - If you're an auth dir server, always publish your dirport,
17502 even if you haven't yet found yourself to be reachable.
17503 - Fix a size_t underflow in smartlist_join_strings2() that made
17504 it do bad things when you hand it an empty smartlist.
17507 Changes in version 0.1.0.12 - 2005-07-18
17508 o New directory servers:
17509 - tor26 has changed IP address.
17511 o Bugfixes on 0.1.0.x:
17512 - Fix a possible double-free in tor_gzip_uncompress().
17513 - When --disable-threads is set, do not search for or link against
17514 pthreads libraries.
17515 - Don't trigger an assert if an authoritative directory server
17516 claims its dirport is 0.
17517 - Fix bug with removing Tor as an NT service: some people were
17518 getting "The service did not return an error." Thanks to Matt
17522 Changes in version 0.1.1.2-alpha - 2005-07-15
17523 o New directory servers:
17524 - tor26 has changed IP address.
17526 o Bugfixes on 0.1.0.x, crashes/leaks:
17527 - Port the servers-not-obeying-their-exit-policies fix from
17529 - Fix an fd leak in start_daemon().
17530 - On Windows, you can't always reopen a port right after you've
17531 closed it. So change retry_listeners() to only close and re-open
17532 ports that have changed.
17533 - Fix a possible double-free in tor_gzip_uncompress().
17535 o Bugfixes on 0.1.0.x, usability:
17536 - When tor_socketpair() fails in Windows, give a reasonable
17537 Windows-style errno back.
17538 - Let people type "tor --install" as well as "tor -install" when
17540 want to make it an NT service.
17541 - NT service patch from Matt Edman to improve error messages.
17542 - When the controller asks for a config option with an abbreviated
17543 name, give the full name in our response.
17544 - Correct the man page entry on TrackHostExitsExpire.
17545 - Looks like we were never delivering deflated (i.e. compressed)
17546 running-routers lists, even when asked. Oops.
17547 - When --disable-threads is set, do not search for or link against
17548 pthreads libraries.
17550 o Bugfixes on 0.1.1.x:
17551 - Fix a seg fault with autodetecting which controller version is
17555 - New hidden service descriptor format: put a version in it, and
17556 let people specify introduction/rendezvous points that aren't
17557 in "the directory" (which is subjective anyway).
17558 - Allow the DEBUG controller event to work again. Mark certain log
17559 entries as "don't tell this to controllers", so we avoid cycles.
17562 Changes in version 0.1.0.11 - 2005-06-30
17563 o Bugfixes on 0.1.0.x:
17564 - Fix major security bug: servers were disregarding their
17565 exit policies if clients behaved unexpectedly.
17566 - Make OS X init script check for missing argument, so we don't
17567 confuse users who invoke it incorrectly.
17568 - Fix a seg fault in "tor --hash-password foo".
17569 - The MAPADDRESS control command was broken.
17572 Changes in version 0.1.1.1-alpha - 2005-06-29
17574 - Make OS X init script check for missing argument, so we don't
17575 confuse users who invoke it incorrectly.
17576 - Fix a seg fault in "tor --hash-password foo".
17577 - Fix a possible way to DoS dirservers.
17578 - When we complain that your exit policy implicitly allows local or
17579 private address spaces, name them explicitly so operators can
17581 - Make the log message less scary when all the dirservers are
17582 temporarily unreachable.
17583 - We were printing the number of idle dns workers incorrectly when
17587 - Revised controller protocol (version 1) that uses ascii rather
17588 than binary. Add supporting libraries in python and java so you
17589 can use the controller from your applications without caring how
17590 our protocol works.
17591 - Spiffy new support for crypto hardware accelerators. Can somebody
17595 Changes in version 0.0.9.10 - 2005-06-16
17596 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17597 - Refuse relay cells that claim to have a length larger than the
17598 maximum allowed. This prevents a potential attack that could read
17599 arbitrary memory (e.g. keys) from an exit server's process
17603 Changes in version 0.1.0.10 - 2005-06-14
17604 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
17605 libevent before 1.1a.
17608 Changes in version 0.1.0.9-rc - 2005-06-09
17610 - Reset buf->highwater every time buf_shrink() is called, not just on
17611 a successful shrink. This was causing significant memory bloat.
17612 - Fix buffer overflow when checking hashed passwords.
17613 - Security fix: if seeding the RNG on Win32 fails, quit.
17614 - Allow seeding the RNG on Win32 even when you're not running as
17616 - Disable threading on Solaris too. Something is wonky with it,
17617 cpuworkers, and reentrant libs.
17618 - Reenable the part of the code that tries to flush as soon as an
17619 OR outbuf has a full TLS record available. Perhaps this will make
17620 OR outbufs not grow as huge except in rare cases, thus saving lots
17621 of CPU time plus memory.
17622 - Reject malformed .onion addresses rather then passing them on as
17623 normal web requests.
17624 - Adapt patch from Adam Langley: fix possible memory leak in
17625 tor_lookup_hostname().
17626 - Initialize libevent later in the startup process, so the logs are
17627 already established by the time we start logging libevent warns.
17628 - Use correct errno on win32 if libevent fails.
17629 - Check and warn about known-bad/slow libevent versions.
17630 - Pay more attention to the ClientOnly config option.
17631 - Have torctl.in/tor.sh.in check for location of su binary (needed
17633 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
17634 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
17635 HttpProxyAuthenticator
17636 - Stop warning about sigpipes in the logs. We're going to
17637 pretend that getting these occassionally is normal and fine.
17638 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
17640 installer screens; and don't put stuff into StartupItems unless
17641 the user asks you to.
17642 - Require servers that use the default dirservers to have public IP
17643 addresses. We have too many servers that are configured with private
17644 IPs and their admins never notice the log entries complaining that
17645 their descriptors are being rejected.
17646 - Add OSX uninstall instructions. An actual uninstall script will
17650 Changes in version 0.1.0.8-rc - 2005-05-23
17652 - It turns out that kqueue on OS X 10.3.9 was causing kernel
17653 panics. Disable kqueue on all OS X Tors.
17654 - Fix RPM: remove duplicate line accidentally added to the rpm
17656 - Disable threads on openbsd too, since its gethostaddr is not
17658 - Tolerate libevent 0.8 since it still works, even though it's
17660 - Enable building on Red Hat 9.0 again.
17661 - Allow the middle hop of the testing circuit to be running any
17662 version, now that most of them have the bugfix to let them connect
17663 to unknown servers. This will allow reachability testing to work
17664 even when 0.0.9.7-0.0.9.9 become obsolete.
17665 - Handle relay cells with rh.length too large. This prevents
17666 a potential attack that could read arbitrary memory (maybe even
17667 keys) from the exit server's process.
17668 - We screwed up the dirport reachability testing when we don't yet
17669 have a cached version of the directory. Hopefully now fixed.
17670 - Clean up router_load_single_router() (used by the controller),
17671 so it doesn't seg fault on error.
17672 - Fix a minor memory leak when somebody establishes an introduction
17673 point at your Tor server.
17674 - If a socks connection ends because read fails, don't warn that
17675 you're not sending a socks reply back.
17678 - Add HttpProxyAuthenticator config option too, that works like
17679 the HttpsProxyAuthenticator config option.
17680 - Encode hashed controller passwords in hex instead of base64,
17681 to make it easier to write controllers.
17684 Changes in version 0.1.0.7-rc - 2005-05-17
17686 - Fix a bug in the OS X package installer that prevented it from
17687 installing on Tiger.
17688 - Fix a script bug in the OS X package installer that made it
17689 complain during installation.
17690 - Find libevent even if it's hiding in /usr/local/ and your
17691 CFLAGS and LDFLAGS don't tell you to look there.
17692 - Be able to link with libevent as a shared library (the default
17693 after 1.0d), even if it's hiding in /usr/local/lib and even
17694 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17695 assuming you're running gcc. Otherwise fail and give a useful
17697 - Fix a bug in the RPM packager: set home directory for _tor to
17698 something more reasonable when first installing.
17699 - Free a minor amount of memory that is still reachable on exit.
17702 Changes in version 0.1.0.6-rc - 2005-05-14
17704 - Implement --disable-threads configure option. Disable threads on
17705 netbsd by default, because it appears to have no reentrant resolver
17707 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
17708 release (1.1) detects and disables kqueue if it's broken.
17709 - Append default exit policy before checking for implicit internal
17710 addresses. Now we don't log a bunch of complaints on startup
17711 when using the default exit policy.
17712 - Some people were putting "Address " in their torrc, and they had
17713 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17714 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17715 LOCALSTATEDIR/tor instead.
17716 - Fix fragmented-message bug in TorControl.py.
17717 - Resolve a minor bug which would prevent unreachable dirports
17718 from getting suppressed in the published descriptor.
17719 - When the controller gave us a new descriptor, we weren't resolving
17720 it immediately, so Tor would think its address was 0.0.0.0 until
17721 we fetched a new directory.
17722 - Fix an uppercase/lowercase case error in suppressing a bogus
17723 libevent warning on some Linuxes.
17726 - Begin scrubbing sensitive strings from logs by default. Turn off
17727 the config option SafeLogging if you need to do debugging.
17728 - Switch to a new buffer management algorithm, which tries to avoid
17729 reallocing and copying quite as much. In first tests it looks like
17730 it uses *more* memory on average, but less cpu.
17731 - First cut at support for "create-fast" cells. Clients can use
17732 these when extending to their first hop, since the TLS already
17733 provides forward secrecy and authentication. Not enabled on
17735 - When dirservers refuse a router descriptor, we now log its
17736 contactinfo, platform, and the poster's IP address.
17737 - Call tor_free_all instead of connections_free_all after forking, to
17738 save memory on systems that need to fork.
17739 - Whine at you if you're a server and you don't set your contactinfo.
17740 - Implement --verify-config command-line option to check if your torrc
17741 is valid without actually launching Tor.
17742 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
17743 rather than just rejecting it.
17746 Changes in version 0.1.0.5-rc - 2005-04-27
17748 - Stop trying to print a null pointer if an OR conn fails because
17749 we didn't like its cert.
17751 - Switch our internal buffers implementation to use a ring buffer,
17752 to hopefully improve performance for fast servers a lot.
17753 - Add HttpsProxyAuthenticator support (basic auth only), based
17754 on patch from Adam Langley.
17755 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17756 the fast servers that have been joining lately.
17757 - Give hidden service accesses extra time on the first attempt,
17758 since 60 seconds is often only barely enough. This might improve
17760 - Improve performance for dirservers: stop re-parsing the whole
17761 directory every time you regenerate it.
17762 - Add more debugging info to help us find the weird dns freebsd
17763 pthreads bug; cleaner debug messages to help track future issues.
17766 Changes in version 0.0.9.9 - 2005-04-23
17767 o Bugfixes on 0.0.9.x:
17768 - If unofficial Tor clients connect and send weird TLS certs, our
17769 Tor server triggers an assert. This release contains a minimal
17770 backport from the broader fix that we put into 0.1.0.4-rc.
17773 Changes in version 0.1.0.4-rc - 2005-04-23
17775 - If unofficial Tor clients connect and send weird TLS certs, our
17776 Tor server triggers an assert. Stop asserting, and start handling
17777 TLS errors better in other situations too.
17778 - When the controller asks us to tell it about all the debug-level
17779 logs, it turns out we were generating debug-level logs while
17780 telling it about them, which turns into a bad loop. Now keep
17781 track of whether you're sending a debug log to the controller,
17782 and don't log when you are.
17783 - Fix the "postdescriptor" feature of the controller interface: on
17784 non-complete success, only say "done" once.
17786 - Clients are now willing to load balance over up to 2mB, not 1mB,
17787 of advertised bandwidth capacity.
17788 - Add a NoPublish config option, so you can be a server (e.g. for
17789 testing running Tor servers in other Tor networks) without
17790 publishing your descriptor to the primary dirservers.
17793 Changes in version 0.1.0.3-rc - 2005-04-08
17794 o Improvements on 0.1.0.2-rc:
17795 - Client now retries when streams end early for 'hibernating' or
17796 'resource limit' reasons, rather than failing them.
17797 - More automated handling for dirserver operators:
17798 - Automatically approve nodes running 0.1.0.2-rc or later,
17799 now that the the reachability detection stuff is working.
17800 - Now we allow two unverified servers with the same nickname
17801 but different keys. But if a nickname is verified, only that
17802 nickname+key are allowed.
17803 - If you're an authdirserver connecting to an address:port,
17804 and it's not the OR you were expecting, forget about that
17805 descriptor. If he *was* the one you were expecting, then forget
17806 about all other descriptors for that address:port.
17807 - Allow servers to publish descriptors from 12 hours in the future.
17808 Corollary: only whine about clock skew from the dirserver if
17809 he's a trusted dirserver (since now even verified servers could
17810 have quite wrong clocks).
17811 - Adjust maximum skew and age for rendezvous descriptors: let skew
17812 be 48 hours rather than 90 minutes.
17813 - Efficiency improvements:
17814 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17815 it much faster to look up a circuit for each relay cell.
17816 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17817 since they're eating our cpu on exit nodes.
17818 - Stop wasting time doing a case insensitive comparison for every
17819 dns name every time we do any lookup. Canonicalize the names to
17820 lowercase and be done with it.
17821 - Start sending 'truncated' cells back rather than destroy cells,
17822 if the circuit closes in front of you. This means we won't have
17823 to abandon partially built circuits.
17824 - Only warn once per nickname from add_nickname_list_to_smartlist
17825 per failure, so an entrynode or exitnode choice that's down won't
17827 - Put a note in the torrc about abuse potential with the default
17829 - Revise control spec and implementation to allow all log messages to
17830 be sent to controller with their severities intact (suggested by
17831 Matt Edman). Update TorControl to handle new log event types.
17832 - Provide better explanation messages when controller's POSTDESCRIPTOR
17834 - Stop putting nodename in the Platform string in server descriptors.
17835 It doesn't actually help, and it is confusing/upsetting some people.
17837 o Bugfixes on 0.1.0.2-rc:
17838 - We were printing the host mask wrong in exit policies in server
17839 descriptors. This isn't a critical bug though, since we were still
17840 obeying the exit policy internally.
17841 - Fix Tor when compiled with libevent but without pthreads: move
17842 connection_unregister() from _connection_free() to
17844 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
17845 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
17846 when we look through the connection array, we'll find any of the
17847 cpu/dnsworkers. This is no good.
17849 o Bugfixes on 0.0.9.8:
17850 - Fix possible bug on threading platforms (e.g. win32) which was
17851 leaking a file descriptor whenever a cpuworker or dnsworker died.
17852 - When using preferred entry or exit nodes, ignore whether the
17853 circuit wants uptime or capacity. They asked for the nodes, they
17855 - chdir() to your datadirectory at the *end* of the daemonize process,
17856 not the beginning. This was a problem because the first time you
17857 run tor, if your datadir isn't there, and you have runasdaemon set
17858 to 1, it will try to chdir to it before it tries to create it. Oops.
17859 - Handle changed router status correctly when dirserver reloads
17860 fingerprint file. We used to be dropping all unverified descriptors
17861 right then. The bug was hidden because we would immediately
17862 fetch a directory from another dirserver, which would include the
17863 descriptors we just dropped.
17864 - When we're connecting to an OR and he's got a different nickname/key
17865 than we were expecting, only complain loudly if we're an OP or a
17866 dirserver. Complaining loudly to the OR admins just confuses them.
17867 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17868 artificially capped at 500kB.
17871 Changes in version 0.0.9.8 - 2005-04-07
17872 o Bugfixes on 0.0.9.x:
17873 - We have a bug that I haven't found yet. Sometimes, very rarely,
17874 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17875 thinks of itself as idle. This meant that no new circuits ever got
17876 established. Here's a workaround to kill any cpuworker that's been
17877 busy for more than 100 seconds.
17880 Changes in version 0.1.0.2-rc - 2005-04-01
17881 o Bugfixes on 0.1.0.1-rc:
17882 - Fixes on reachability detection:
17883 - Don't check for reachability while hibernating.
17884 - If ORPort is reachable but DirPort isn't, still publish the
17885 descriptor, but zero out DirPort until it's found reachable.
17886 - When building testing circs for ORPort testing, use only
17887 high-bandwidth nodes, so fewer circuits fail.
17888 - Complain about unreachable ORPort separately from unreachable
17889 DirPort, so the user knows what's going on.
17890 - Make sure we only conclude ORPort reachability if we didn't
17891 initiate the conn. Otherwise we could falsely conclude that
17892 we're reachable just because we connected to the guy earlier
17893 and he used that same pipe to extend to us.
17894 - Authdirservers shouldn't do ORPort reachability detection,
17895 since they're in clique mode, so it will be rare to find a
17896 server not already connected to them.
17897 - When building testing circuits, always pick middle hops running
17898 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
17899 bug. (This is a kludge; it will go away when 0.0.9.x becomes
17901 - When we decide we're reachable, actually publish our descriptor
17903 - Fix bug in redirectstream in the controller.
17904 - Fix the state descriptor strings so logs don't claim edge streams
17905 are in a different state than they actually are.
17906 - Use recent libevent features when possible (this only really affects
17907 win32 and osx right now, because the new libevent with these
17908 features hasn't been released yet). Add code to suppress spurious
17910 - Prevent possible segfault in connection_close_unattached_ap().
17911 - Fix newlines on torrc in win32.
17912 - Improve error msgs when tor-resolve fails.
17914 o Improvements on 0.0.9.x:
17915 - New experimental script tor/contrib/ExerciseServer.py (needs more
17916 work) that uses the controller interface to build circuits and
17917 fetch pages over them. This will help us bootstrap servers that
17918 have lots of capacity but haven't noticed it yet.
17919 - New experimental script tor/contrib/PathDemo.py (needs more work)
17920 that uses the controller interface to let you choose whole paths
17922 "<hostname>.<path,separated by dots>.<length of path>.path"
17923 - When we've connected to an OR and handshaked but didn't like
17924 the result, we were closing the conn without sending destroy
17925 cells back for pending circuits. Now send those destroys.
17928 Changes in version 0.0.9.7 - 2005-04-01
17929 o Bugfixes on 0.0.9.x:
17930 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17931 - Compare identity to identity, not to nickname, when extending to
17932 a router not already in the directory. This was preventing us from
17933 extending to unknown routers. Oops.
17934 - Make sure to create OS X Tor user in <500 range, so we aren't
17935 creating actual system users.
17936 - Note where connection-that-hasn't-sent-end was marked, and fix
17937 a few really loud instances of this harmless bug (it's fixed more
17941 Changes in version 0.1.0.1-rc - 2005-03-28
17943 - Add reachability testing. Your Tor server will automatically try
17944 to see if its ORPort and DirPort are reachable from the outside,
17945 and it won't upload its descriptor until it decides they are.
17946 - Handle unavailable hidden services better. Handle slow or busy
17947 hidden services better.
17948 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17950 - New exit policy: accept most low-numbered ports, rather than
17951 rejecting most low-numbered ports.
17952 - More Tor controller support (still experimental). See
17953 http://tor.eff.org/doc/control-spec.txt for all the new features,
17954 including signals to emulate unix signals from any platform;
17955 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17956 closestream; closecircuit; etc.
17957 - Make nt services work and start on startup on win32 (based on
17958 patch by Matt Edman).
17959 - Add a new AddressMap config directive to rewrite incoming socks
17960 addresses. This lets you, for example, declare an implicit
17961 required exit node for certain sites.
17962 - Add a new TrackHostExits config directive to trigger addressmaps
17963 for certain incoming socks addresses -- for sites that break when
17964 your exit keeps changing (based on patch by Mike Perry).
17965 - Redo the client-side dns cache so it's just an addressmap too.
17966 - Notice when our IP changes, and reset stats/uptime/reachability.
17967 - When an application is using socks5, give him the whole variety of
17968 potential socks5 responses (connect refused, host unreachable, etc),
17969 rather than just "success" or "failure".
17970 - A more sane version numbering system. See
17971 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17972 - New contributed script "exitlist": a simple python script to
17973 parse directories and find Tor nodes that exit to listed
17975 - New contributed script "privoxy-tor-toggle" to toggle whether
17976 Privoxy uses Tor. Seems to be configured for Debian by default.
17977 - Report HTTP reasons to client when getting a response from directory
17978 servers -- so you can actually know what went wrong.
17979 - New config option MaxAdvertisedBandwidth which lets you advertise
17980 a low bandwidthrate (to not attract as many circuits) while still
17981 allowing a higher bandwidthrate in reality.
17983 o Robustness/stability fixes:
17984 - Make Tor use Niels Provos's libevent instead of its current
17985 poll-but-sometimes-select mess. This will let us use faster async
17986 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
17988 - pthread support now too. This was forced because when we forked,
17989 we ended up wasting a lot of duplicate ram over time. Also switch
17990 to foo_r versions of some library calls to allow reentry and
17992 - Better handling for heterogeneous / unreliable nodes:
17993 - Annotate circuits w/ whether they aim to contain high uptime nodes
17994 and/or high capacity nodes. When building circuits, choose
17996 - This means that every single node in an intro rend circuit,
17997 not just the last one, will have a minimum uptime.
17998 - New config option LongLivedPorts to indicate application streams
17999 that will want high uptime circuits.
18000 - Servers reset uptime when a dir fetch entirely fails. This
18001 hopefully reflects stability of the server's network connectivity.
18002 - If somebody starts his tor server in Jan 2004 and then fixes his
18003 clock, don't make his published uptime be a year.
18004 - Reset published uptime when you wake up from hibernation.
18005 - Introduce a notion of 'internal' circs, which are chosen without
18006 regard to the exit policy of the last hop. Intro and rendezvous
18007 circs must be internal circs, to avoid leaking information. Resolve
18008 and connect streams can use internal circs if they want.
18009 - New circuit pooling algorithm: make sure to have enough circs around
18010 to satisfy any predicted ports, and also make sure to have 2 internal
18011 circs around if we've required internal circs lately (and with high
18012 uptime if we've seen that lately too).
18013 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18014 which describes how often we retry making new circuits if current
18015 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18016 how long we're willing to make use of an already-dirty circuit.
18017 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18018 circ as necessary, if there are any completed ones lying around
18019 when we try to launch one.
18020 - Make hidden services try to establish a rendezvous for 30 seconds,
18021 rather than for n (where n=3) attempts to build a circuit.
18022 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
18023 "ShutdownWaitLength".
18024 - Try to be more zealous about calling connection_edge_end when
18025 things go bad with edge conns in connection.c.
18026 - Revise tor-spec to add more/better stream end reasons.
18027 - Revise all calls to connection_edge_end to avoid sending "misc",
18028 and to take errno into account where possible.
18031 - Fix a race condition that can trigger an assert, when we have a
18032 pending create cell and an OR connection fails right then.
18033 - Fix several double-mark-for-close bugs, e.g. where we were finding
18034 a conn for a cell even if that conn is already marked for close.
18035 - Make sequence of log messages when starting on win32 with no config
18036 file more reasonable.
18037 - When choosing an exit node for a new non-internal circ, don't take
18038 into account whether it'll be useful for any pending x.onion
18039 addresses -- it won't.
18040 - Turn addr_policy_compare from a tristate to a quadstate; this should
18041 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18042 for google.com" problem.
18043 - Make "platform" string in descriptor more accurate for Win32 servers,
18044 so it's not just "unknown platform".
18045 - Fix an edge case in parsing config options (thanks weasel).
18046 If they say "--" on the commandline, it's not an option.
18047 - Reject odd-looking addresses at the client (e.g. addresses that
18048 contain a colon), rather than having the server drop them because
18050 - tor-resolve requests were ignoring .exit if there was a working circuit
18051 they could use instead.
18052 - REUSEADDR on normal platforms means you can rebind to the port
18053 right after somebody else has let it go. But REUSEADDR on win32
18054 means to let you bind to the port _even when somebody else
18055 already has it bound_! So, don't do that on Win32.
18056 - Change version parsing logic: a version is "obsolete" if it is not
18057 recommended and (1) there is a newer recommended version in the
18058 same series, or (2) there are no recommended versions in the same
18059 series, but there are some recommended versions in a newer series.
18060 A version is "new" if it is newer than any recommended version in
18062 - Stop most cases of hanging up on a socks connection without sending
18066 - Require BandwidthRate to be at least 20kB/s for servers.
18067 - When a dirserver causes you to give a warn, mention which dirserver
18069 - New config option DirAllowPrivateAddresses for authdirservers.
18070 Now by default they refuse router descriptors that have non-IP or
18071 private-IP addresses.
18072 - Stop publishing socksport in the directory, since it's not
18073 actually meant to be public. For compatibility, publish a 0 there
18075 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18076 smart" value, that is low for servers and high for clients.
18077 - If our clock jumps forward by 100 seconds or more, assume something
18078 has gone wrong with our network and abandon all not-yet-used circs.
18079 - Warn when exit policy implicitly allows local addresses.
18080 - If we get an incredibly skewed timestamp from a dirserver mirror
18081 that isn't a verified OR, don't warn -- it's probably him that's
18083 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18084 cookies to disk and doesn't log each web request to disk. (Thanks
18085 to Brett Carrington for pointing this out.)
18086 - When a client asks us for a dir mirror and we don't have one,
18087 launch an attempt to get a fresh one.
18088 - If we're hibernating and we get a SIGINT, exit immediately.
18089 - Add --with-dmalloc ./configure option, to track memory leaks.
18090 - And try to free all memory on closing, so we can detect what
18092 - Cache local dns resolves correctly even when they're .exit
18094 - Give a better warning when some other server advertises an
18095 ORPort that is actually an apache running ssl.
18096 - Add "opt hibernating 1" to server descriptor to make it clearer
18097 whether the server is hibernating.
18100 Changes in version 0.0.9.6 - 2005-03-24
18101 o Bugfixes on 0.0.9.x (crashes and asserts):
18102 - Add new end stream reasons to maintainance branch. Fix bug where
18103 reason (8) could trigger an assert. Prevent bug from recurring.
18104 - Apparently win32 stat wants paths to not end with a slash.
18105 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18106 blowing away the circuit that conn->cpath_layer points to, then
18107 checking to see if the circ is well-formed. Backport check to make
18108 sure we dont use the cpath on a closed connection.
18109 - Prevent circuit_resume_edge_reading_helper() from trying to package
18110 inbufs for marked-for-close streams.
18111 - Don't crash on hup if your options->address has become unresolvable.
18112 - Some systems (like OS X) sometimes accept() a connection and tell
18113 you the remote host is 0.0.0.0:0. If this happens, due to some
18114 other mis-features, we get confused; so refuse the conn for now.
18116 o Bugfixes on 0.0.9.x (other):
18117 - Fix harmless but scary "Unrecognized content encoding" warn message.
18118 - Add new stream error reason: TORPROTOCOL reason means "you are not
18119 speaking a version of Tor I understand; say bye-bye to your stream."
18120 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18121 into the future, now that we are more tolerant of skew. This
18122 resolves a bug where a Tor server would refuse to cache a directory
18123 because all the directories it gets are too far in the future;
18124 yet the Tor server never logs any complaints about clock skew.
18125 - Mac packaging magic: make man pages useable, and do not overwrite
18126 existing torrc files.
18127 - Make OS X log happily to /var/log/tor/tor.log
18130 Changes in version 0.0.9.5 - 2005-02-22
18131 o Bugfixes on 0.0.9.x:
18132 - Fix an assert race at exit nodes when resolve requests fail.
18133 - Stop picking unverified dir mirrors--it only leads to misery.
18134 - Patch from Matt Edman to make NT services work better. Service
18135 support is still not compiled into the executable by default.
18136 - Patch from Dmitri Bely so the Tor service runs better under
18137 the win32 SYSTEM account.
18138 - Make tor-resolve actually work (?) on Win32.
18139 - Fix a sign bug when getrlimit claims to have 4+ billion
18140 file descriptors available.
18141 - Stop refusing to start when bandwidthburst == bandwidthrate.
18142 - When create cells have been on the onion queue more than five
18143 seconds, just send back a destroy and take them off the list.
18146 Changes in version 0.0.9.4 - 2005-02-03
18147 o Bugfixes on 0.0.9:
18148 - Fix an assert bug that took down most of our servers: when
18149 a server claims to have 1 GB of bandwidthburst, don't
18151 - Don't crash as badly if we have spawned the max allowed number
18152 of dnsworkers, or we're out of file descriptors.
18153 - Block more file-sharing ports in the default exit policy.
18154 - MaxConn is now automatically set to the hard limit of max
18155 file descriptors we're allowed (ulimit -n), minus a few for
18157 - Give a clearer message when servers need to raise their
18158 ulimit -n when they start running out of file descriptors.
18159 - SGI Compatibility patches from Jan Schaumann.
18160 - Tolerate a corrupt cached directory better.
18161 - When a dirserver hasn't approved your server, list which one.
18162 - Go into soft hibernation after 95% of the bandwidth is used,
18163 not 99%. This is especially important for daily hibernators who
18164 have a small accounting max. Hopefully it will result in fewer
18165 cut connections when the hard hibernation starts.
18166 - Load-balance better when using servers that claim more than
18167 800kB/s of capacity.
18168 - Make NT services work (experimental, only used if compiled in).
18171 Changes in version 0.0.9.3 - 2005-01-21
18172 o Bugfixes on 0.0.9:
18173 - Backport the cpu use fixes from main branch, so busy servers won't
18174 need as much processor time.
18175 - Work better when we go offline and then come back, or when we
18176 run Tor at boot before the network is up. We do this by
18177 optimistically trying to fetch a new directory whenever an
18178 application request comes in and we think we're offline -- the
18179 human is hopefully a good measure of when the network is back.
18180 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18181 long as you keep using them; actually publish hidserv descriptors
18182 shortly after they change, rather than waiting 20-40 minutes.
18183 - Enable Mac startup script by default.
18184 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18185 - When you update AllowUnverifiedNodes or FirewallPorts via the
18186 controller's setconf feature, we were always appending, never
18188 - When you update HiddenServiceDir via setconf, it was screwing up
18189 the order of reading the lines, making it fail.
18190 - Do not rewrite a cached directory back to the cache; otherwise we
18191 will think it is recent and not fetch a newer one on startup.
18192 - Workaround for webservers that lie about Content-Encoding: Tor
18193 now tries to autodetect compressed directories and compression
18194 itself. This lets us Proxypass dir fetches through apache.
18197 Changes in version 0.0.9.2 - 2005-01-04
18198 o Bugfixes on 0.0.9 (crashes and asserts):
18199 - Fix an assert on startup when the disk is full and you're logging
18201 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18202 style address, then we'd crash.
18203 - Fix an assert trigger when the running-routers string we get from
18204 a dirserver is broken.
18205 - Make worker threads start and run on win32. Now win32 servers
18207 - Bandaid (not actually fix, but now it doesn't crash) an assert
18208 where the dns worker dies mysteriously and the main Tor process
18209 doesn't remember anything about the address it was resolving.
18211 o Bugfixes on 0.0.9 (Win32):
18212 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18213 name out of the warning/assert messages.
18214 - Fix a superficial "unhandled error on read" bug on win32.
18215 - The win32 installer no longer requires a click-through for our
18216 license, since our Free Software license grants rights but does not
18218 - Win32: When connecting to a dirserver fails, try another one
18219 immediately. (This was already working for non-win32 Tors.)
18220 - Stop trying to parse $HOME on win32 when hunting for default
18222 - Make tor-resolve.c work on win32 by calling network_init().
18224 o Bugfixes on 0.0.9 (other):
18225 - Make 0.0.9.x build on Solaris again.
18226 - Due to a fencepost error, we were blowing away the \n when reporting
18227 confvalue items in the controller. So asking for multiple config
18228 values at once couldn't work.
18229 - When listing circuits that are pending on an opening OR connection,
18230 if we're an OR we were listing circuits that *end* at us as
18231 being pending on every listener, dns/cpu worker, etc. Stop that.
18232 - Dirservers were failing to create 'running-routers' or 'directory'
18233 strings if we had more than some threshold of routers. Fix them so
18234 they can handle any number of routers.
18235 - Fix a superficial "Duplicate mark for close" bug.
18236 - Stop checking for clock skew for OR connections, even for servers.
18237 - Fix a fencepost error that was chopping off the last letter of any
18238 nickname that is the maximum allowed nickname length.
18239 - Update URLs in log messages so they point to the new website.
18240 - Fix a potential problem in mangling server private keys while
18241 writing to disk (not triggered yet, as far as we know).
18242 - Include the licenses for other free software we include in Tor,
18243 now that we're shipping binary distributions more regularly.
18246 Changes in version 0.0.9.1 - 2004-12-15
18247 o Bugfixes on 0.0.9:
18248 - Make hibernation actually work.
18249 - Make HashedControlPassword config option work.
18250 - When we're reporting event circuit status to a controller,
18251 don't use the stream status code.
18254 Changes in version 0.0.9 - 2004-12-12
18256 - Clean up manpage and torrc.sample file.
18257 - Clean up severities and text of log warnings.
18259 - Make servers trigger an assert when they enter hibernation.
18262 Changes in version 0.0.9rc7 - 2004-12-08
18263 o Bugfixes on 0.0.9rc:
18264 - Fix a stack-trashing crash when an exit node begins hibernating.
18265 - Avoid looking at unallocated memory while considering which
18266 ports we need to build circuits to cover.
18267 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18268 we shouldn't hold-open-until-flush if the eof arrived first.
18269 - Fix a bug with init_cookie_authentication() in the controller.
18270 - When recommending new-format log lines, if the upper bound is
18271 LOG_ERR, leave it implicit.
18273 o Bugfixes on 0.0.8.1:
18274 - Fix a whole slew of memory leaks.
18275 - Fix isspace() and friends so they still make Solaris happy
18276 but also so they don't trigger asserts on win32.
18277 - Fix parse_iso_time on platforms without strptime (eg win32).
18278 - win32: tolerate extra "readable" events better.
18279 - win32: when being multithreaded, leave parent fdarray open.
18280 - Make unit tests work on win32.
18283 Changes in version 0.0.9rc6 - 2004-12-06
18284 o Bugfixes on 0.0.9pre:
18285 - Clean up some more integer underflow opportunities (not exploitable
18287 - While hibernating, hup should not regrow our listeners.
18288 - Send an end to the streams we close when we hibernate, rather
18289 than just chopping them off.
18290 - React to eof immediately on non-open edge connections.
18292 o Bugfixes on 0.0.8.1:
18293 - Calculate timeout for waiting for a connected cell from the time
18294 we sent the begin cell, not from the time the stream started. If
18295 it took a long time to establish the circuit, we would time out
18296 right after sending the begin cell.
18297 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18298 of * as always matching, so we were picking reject *:* nodes as
18299 exit nodes too. Oops.
18302 - New circuit building strategy: keep a list of ports that we've
18303 used in the past 6 hours, and always try to have 2 circuits open
18304 or on the way that will handle each such port. Seed us with port
18305 80 so web users won't complain that Tor is "slow to start up".
18306 - Make kill -USR1 dump more useful stats about circuits.
18307 - When warning about retrying or giving up, print the address, so
18308 the user knows which one it's talking about.
18309 - If you haven't used a clean circuit in an hour, throw it away,
18310 just to be on the safe side. (This means after 6 hours a totally
18311 unused Tor client will have no circuits open.)
18314 Changes in version 0.0.9rc5 - 2004-12-01
18315 o Bugfixes on 0.0.8.1:
18316 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18317 - Let resolve conns retry/expire also, rather than sticking around
18319 - If we are using select, make sure we stay within FD_SETSIZE.
18321 o Bugfixes on 0.0.9pre:
18322 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
18323 but doesn't seem to be currently; thanks to Ilja van Sprundel for
18325 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
18326 instead. Impose minima and maxima for all *Period options; impose
18327 even tighter maxima for fetching if we are a caching dirserver.
18328 Clip rather than rejecting.
18329 - Fetch cached running-routers from servers that serve it (that is,
18330 authdirservers and servers running 0.0.9rc5-cvs or later.)
18333 - Accept *:706 (silc) in default exit policy.
18334 - Implement new versioning format for post 0.1.
18335 - Support "foo.nickname.exit" addresses, to let Alice request the
18336 address "foo" as viewed by exit node "nickname". Based on a patch
18338 - Make tor --version --version dump the cvs Id of every file.
18341 Changes in version 0.0.9rc4 - 2004-11-28
18342 o Bugfixes on 0.0.8.1:
18343 - Make windows sockets actually non-blocking (oops), and handle
18344 win32 socket errors better.
18346 o Bugfixes on 0.0.9rc1:
18347 - Actually catch the -USR2 signal.
18350 Changes in version 0.0.9rc3 - 2004-11-25
18351 o Bugfixes on 0.0.8.1:
18352 - Flush the log file descriptor after we print "Tor opening log file",
18353 so we don't see those messages days later.
18355 o Bugfixes on 0.0.9rc1:
18356 - Make tor-resolve work again.
18357 - Avoid infinite loop in tor-resolve if tor hangs up on it.
18358 - Fix an assert trigger for clients/servers handling resolves.
18361 Changes in version 0.0.9rc2 - 2004-11-24
18362 o Bugfixes on 0.0.9rc1:
18363 - I broke socks5 support while fixing the eof bug.
18364 - Allow unitless bandwidths and intervals; they default to bytes
18366 - New servers don't start out hibernating; they are active until
18367 they run out of bytes, so they have a better estimate of how
18368 long it takes, and so their operators can know they're working.
18371 Changes in version 0.0.9rc1 - 2004-11-23
18372 o Bugfixes on 0.0.8.1:
18373 - Finally fix a bug that's been plaguing us for a year:
18374 With high load, circuit package window was reaching 0. Whenever
18375 we got a circuit-level sendme, we were reading a lot on each
18376 socket, but only writing out a bit. So we would eventually reach
18377 eof. This would be noticed and acted on even when there were still
18378 bytes sitting in the inbuf.
18379 - When poll() is interrupted, we shouldn't believe the revents values.
18381 o Bugfixes on 0.0.9pre6:
18382 - Fix hibernate bug that caused pre6 to be broken.
18383 - Don't keep rephist info for routers that haven't had activity for
18384 24 hours. (This matters now that clients have keys, since we track
18386 - Never call close_temp_logs while validating log options.
18387 - Fix backslash-escaping on tor.sh.in and torctl.in.
18390 - Implement weekly/monthly/daily accounting: now you specify your
18391 hibernation properties by
18392 AccountingMax N bytes|KB|MB|GB|TB
18393 AccountingStart day|week|month [day] HH:MM
18394 Defaults to "month 1 0:00".
18395 - Let bandwidth and interval config options be specified as 5 bytes,
18396 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18397 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18398 get back to normal.)
18399 - If your requested entry or exit node has advertised bandwidth 0,
18401 - Be more greedy about filling up relay cells -- we try reading again
18402 once we've processed the stuff we read, in case enough has arrived
18403 to fill the last cell completely.
18404 - Apply NT service patch from Osamu Fujino. Still needs more work.
18407 Changes in version 0.0.9pre6 - 2004-11-15
18408 o Bugfixes on 0.0.8.1:
18409 - Fix assert failure on malformed socks4a requests.
18410 - Use identity comparison, not nickname comparison, to choose which
18411 half of circuit-ID-space each side gets to use. This is needed
18412 because sometimes we think of a router as a nickname, and sometimes
18413 as a hex ID, and we can't predict what the other side will do.
18414 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18415 write() call will fail and we handle it there.
18416 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18417 and smartlist_len, which are two major profiling offenders.
18419 o Bugfixes on 0.0.9pre5:
18420 - Fix a bug in read_all that was corrupting config files on windows.
18421 - When we're raising the max number of open file descriptors to
18422 'unlimited', don't log that we just raised it to '-1'.
18423 - Include event code with events, as required by control-spec.txt.
18424 - Don't give a fingerprint when clients do --list-fingerprint:
18425 it's misleading, because it will never be the same again.
18426 - Stop using strlcpy in tor_strndup, since it was slowing us
18428 - Remove warn on startup about missing cached-directory file.
18429 - Make kill -USR1 work again.
18430 - Hibernate if we start tor during the "wait for wakeup-time" phase
18431 of an accounting interval. Log our hibernation plans better.
18432 - Authoritative dirservers now also cache their directory, so they
18433 have it on start-up.
18436 - Fetch running-routers; cache running-routers; compress
18437 running-routers; serve compressed running-routers.z
18438 - Add NSI installer script contributed by J Doe.
18439 - Commit VC6 and VC7 workspace/project files.
18440 - Commit a tor.spec for making RPM files, with help from jbash.
18441 - Add contrib/torctl.in contributed by Glenn Fink.
18442 - Implement the control-spec's SAVECONF command, to write your
18443 configuration to torrc.
18444 - Get cookie authentication for the controller closer to working.
18445 - Include control-spec.txt in the tarball.
18446 - When set_conf changes our server descriptor, upload a new copy.
18447 But don't upload it too often if there are frequent changes.
18448 - Document authentication config in man page, and document signals
18450 - Clean up confusing parts of man page and torrc.sample.
18451 - Make expand_filename handle ~ and ~username.
18452 - Use autoconf to enable largefile support where necessary. Use
18453 ftello where available, since ftell can fail at 2GB.
18454 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18455 log more informatively.
18456 - Give a slightly more useful output for "tor -h".
18457 - Refuse application socks connections to port 0.
18458 - Check clock skew for verified servers, but allow unverified
18459 servers and clients to have any clock skew.
18460 - Break DirFetchPostPeriod into:
18461 - DirFetchPeriod for fetching full directory,
18462 - StatusFetchPeriod for fetching running-routers,
18463 - DirPostPeriod for posting server descriptor,
18464 - RendPostPeriod for posting hidden service descriptors.
18465 - Make sure the hidden service descriptors are at a random offset
18466 from each other, to hinder linkability.
18469 Changes in version 0.0.9pre5 - 2004-11-09
18470 o Bugfixes on 0.0.9pre4:
18471 - Fix a seg fault in unit tests (doesn't affect main program).
18472 - Fix an assert bug where a hidden service provider would fail if
18473 the first hop of his rendezvous circuit was down.
18474 - Hidden service operators now correctly handle version 1 style
18475 INTRODUCE1 cells (nobody generates them still, so not a critical
18477 - If do_hup fails, actually notice.
18478 - Handle more errnos from accept() without closing the listener.
18479 Some OpenBSD machines were closing their listeners because
18480 they ran out of file descriptors.
18481 - Send resolve cells to exit routers that are running a new
18482 enough version of the resolve code to work right.
18483 - Better handling of winsock includes on non-MSV win32 compilers.
18484 - Some people had wrapped their tor client/server in a script
18485 that would restart it whenever it died. This did not play well
18486 with our "shut down if your version is obsolete" code. Now people
18487 don't fetch a new directory if their local cached version is
18489 - Make our autogen.sh work on ksh as well as bash.
18492 - Hibernation: New config option "AccountingMaxKB" lets you
18493 set how many KBytes per month you want to allow your server to
18494 consume. Rather than spreading those bytes out evenly over the
18495 month, we instead hibernate for some of the month and pop up
18496 at a deterministic time, work until the bytes are consumed, then
18497 hibernate again. Config option "MonthlyAccountingStart" lets you
18498 specify which day of the month your billing cycle starts on.
18499 - Control interface: a separate program can now talk to your
18500 client/server over a socket, and get/set config options, receive
18501 notifications of circuits and streams starting/finishing/dying,
18502 bandwidth used, etc. The next step is to get some GUIs working.
18503 Let us know if you want to help out. See doc/control-spec.txt .
18504 - Ship a contrib/tor-control.py as an example script to interact
18505 with the control port.
18506 - "tor --hash-password zzyxz" will output a salted password for
18507 use in authenticating to the control interface.
18508 - New log format in config:
18509 "Log minsev[-maxsev] stdout|stderr|syslog" or
18510 "Log minsev[-maxsev] file /var/foo"
18513 - DirPolicy config option, to let people reject incoming addresses
18514 from their dirserver.
18515 - "tor --list-fingerprint" will list your identity key fingerprint
18517 - Add "pass" target for RedirectExit, to make it easier to break
18518 out of a sequence of RedirectExit rules.
18519 - Clients now generate a TLS cert too, in preparation for having
18520 them act more like real nodes.
18521 - Ship src/win32/ in the tarball, so people can use it to build.
18522 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
18524 - New "router-status" line in directory, to better bind each verified
18525 nickname to its identity key.
18526 - Deprecate unofficial config option abbreviations, and abbreviations
18527 not on the command line.
18528 - Add a pure-C tor-resolve implementation.
18529 - Use getrlimit and friends to ensure we can reach MaxConn (currently
18530 1024) file descriptors.
18532 o Code security improvements, inspired by Ilja:
18533 - Replace sprintf with snprintf. (I think they were all safe, but
18535 - Replace strcpy/strncpy with strlcpy in more places.
18536 - Avoid strcat; use snprintf or strlcat instead.
18537 - snprintf wrapper with consistent (though not C99) overflow behavior.
18540 Changes in version 0.0.9pre4 - 2004-10-17
18541 o Bugfixes on 0.0.9pre3:
18542 - If the server doesn't specify an exit policy, use the real default
18543 exit policy, not reject *:*.
18544 - Ignore fascistfirewall when uploading/downloading hidden service
18545 descriptors, since we go through Tor for those; and when using
18546 an HttpProxy, since we assume it can reach them all.
18547 - When looking for an authoritative dirserver, use only the ones
18548 configured at boot. Don't bother looking in the directory.
18549 - The rest of the fix for get_default_conf_file() on older win32.
18550 - Make 'Routerfile' config option obsolete.
18553 - New 'MyFamily nick1,...' config option for a server to
18554 specify other servers that shouldn't be used in the same circuit
18555 with it. Only believed if nick1 also specifies us.
18556 - New 'NodeFamily nick1,nick2,...' config option for a client to
18557 specify nodes that it doesn't want to use in the same circuit.
18558 - New 'Redirectexit pattern address:port' config option for a
18559 server to redirect exit connections, e.g. to a local squid.
18562 Changes in version 0.0.9pre3 - 2004-10-13
18563 o Bugfixes on 0.0.8.1:
18564 - Better torrc example lines for dirbindaddress and orbindaddress.
18565 - Improved bounds checking on parsed ints (e.g. config options and
18566 the ones we find in directories.)
18567 - Better handling of size_t vs int, so we're more robust on 64
18569 - Fix the rest of the bug where a newly started OR would appear
18570 as unverified even after we've added his fingerprint and hupped
18572 - Fix a bug from 0.0.7: when read() failed on a stream, we would
18573 close it without sending back an end. So 'connection refused'
18574 would simply be ignored and the user would get no response.
18576 o Bugfixes on 0.0.9pre2:
18577 - Serving the cached-on-disk directory to people is bad. We now
18578 provide no directory until we've fetched a fresh one.
18579 - Workaround for bug on windows where cached-directories get crlf
18581 - Make get_default_conf_file() work on older windows too.
18582 - If we write a *:* exit policy line in the descriptor, don't write
18583 any more exit policy lines.
18586 - Use only 0.0.9pre1 and later servers for resolve cells.
18587 - Make the dirservers file obsolete.
18588 - Include a dir-signing-key token in directories to tell the
18589 parsing entity which key is being used to sign.
18590 - Remove the built-in bulky default dirservers string.
18591 - New config option "Dirserver %s:%d [fingerprint]", which can be
18592 repeated as many times as needed. If no dirservers specified,
18593 default to moria1,moria2,tor26.
18594 - Make moria2 advertise a dirport of 80, so people behind firewalls
18595 will be able to get a directory.
18596 - Http proxy support
18597 - Dirservers translate requests for http://%s:%d/x to /x
18598 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18599 be routed through this host.
18600 - Clients ask for /tor/x rather than /x for new enough dirservers.
18601 This way we can one day coexist peacefully with apache.
18602 - Clients specify a "Host: %s%d" http header, to be compatible
18603 with more proxies, and so running squid on an exit node can work.
18606 Changes in version 0.0.8.1 - 2004-10-13
18608 - Fix a seg fault that can be triggered remotely for Tor
18609 clients/servers with an open dirport.
18610 - Fix a rare assert trigger, where routerinfos for entries in
18611 our cpath would expire while we're building the path.
18612 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18613 - Fix a rare seg fault for people running hidden services on
18614 intermittent connections.
18615 - Fix a bug in parsing opt keywords with objects.
18616 - Fix a stale pointer assert bug when a stream detaches and
18618 - Fix a string format vulnerability (probably not exploitable)
18619 in reporting stats locally.
18620 - Fix an assert trigger: sometimes launching circuits can fail
18621 immediately, e.g. because too many circuits have failed recently.
18622 - Fix a compile warning on 64 bit platforms.
18625 Changes in version 0.0.9pre2 - 2004-10-03
18627 - Make fetching a cached directory work for 64-bit platforms too.
18628 - Make zlib.h a required header, not an optional header.
18631 Changes in version 0.0.9pre1 - 2004-10-01
18633 - Stop using separate defaults for no-config-file and
18634 empty-config-file. Now you have to explicitly turn off SocksPort,
18635 if you don't want it open.
18636 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18637 - Improve man page to mention more of the 0.0.8 features.
18638 - Fix a rare seg fault for people running hidden services on
18639 intermittent connections.
18640 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18642 - Fix more dns related bugs: send back resolve_failed and end cells
18643 more reliably when the resolve fails, rather than closing the
18644 circuit and then trying to send the cell. Also attach dummy resolve
18645 connections to a circuit *before* calling dns_resolve(), to fix
18646 a bug where cached answers would never be sent in RESOLVED cells.
18647 - When we run out of disk space, or other log writing error, don't
18648 crash. Just stop logging to that log and continue.
18649 - We were starting to daemonize before we opened our logs, so if
18650 there were any problems opening logs, we would complain to stderr,
18651 which wouldn't work, and then mysteriously exit.
18652 - Fix a rare bug where sometimes a verified OR would connect to us
18653 before he'd uploaded his descriptor, which would cause us to
18654 assign conn->nickname as though he's unverified. Now we look through
18655 the fingerprint list to see if he's there.
18656 - Fix a rare assert trigger, where routerinfos for entries in
18657 our cpath would expire while we're building the path.
18660 - Clients can ask dirservers for /dir.z to get a compressed version
18661 of the directory. Only works for servers running 0.0.9, of course.
18662 - Make clients cache directories and use them to seed their router
18663 lists at startup. This means clients have a datadir again.
18664 - Configuration infrastructure support for warning on obsolete
18666 - Respond to content-encoding headers by trying to uncompress as
18668 - Reply with a deflated directory when a client asks for "dir.z".
18669 We could use allow-encodings instead, but allow-encodings isn't
18670 specified in HTTP 1.0.
18671 - Raise the max dns workers from 50 to 100.
18672 - Discourage people from setting their dirfetchpostperiod more often
18673 than once per minute.
18674 - Protect dirservers from overzealous descriptor uploading -- wait
18675 10 seconds after directory gets dirty, before regenerating.
18678 Changes in version 0.0.8 - 2004-08-25
18679 o Port it to SunOS 5.9 / Athena
18682 Changes in version 0.0.8rc2 - 2004-08-20
18683 o Make it compile on cygwin again.
18684 o When picking unverified routers, skip those with low uptime and/or
18685 low bandwidth, depending on what properties you care about.
18688 Changes in version 0.0.8rc1 - 2004-08-18
18689 o Changes from 0.0.7.3:
18691 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18692 don't put it into the client dns cache.
18693 - If a begin failed due to exit policy, but we believe the IP address
18694 should have been allowed, switch that router to exitpolicy reject *:*
18695 until we get our next directory.
18697 - Clients choose nodes proportional to advertised bandwidth.
18698 - Avoid using nodes with low uptime as introduction points.
18699 - Handle servers with dynamic IP addresses: don't replace
18700 options->Address with the resolved one at startup, and
18701 detect our address right before we make a routerinfo each time.
18702 - 'FascistFirewall' option to pick dirservers and ORs on specific
18703 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18704 which ports are open. (Defaults to 80,443)
18705 - Be more aggressive about trying to make circuits when the network
18706 has changed (e.g. when you unsuspend your laptop).
18707 - Check for time skew on http headers; report date in response to
18709 - If the entrynode config line has only one node, don't pick it as
18711 - Add strict{entry|exit}nodes config options. If set to 1, then
18712 we refuse to build circuits that don't include the specified entry
18714 - OutboundBindAddress config option, to bind to a specific
18715 IP address for outgoing connect()s.
18716 - End truncated log entries (e.g. directories) with "[truncated]".
18718 o Patches to 0.0.8preX:
18720 - Patches to compile and run on win32 again (maybe)?
18721 - Fix crash when looking for ~/.torrc with no $HOME set.
18722 - Fix a race bug in the unit tests.
18723 - Handle verified/unverified name collisions better when new
18724 routerinfo's arrive in a directory.
18725 - Sometimes routers were getting entered into the stats before
18726 we'd assigned their identity_digest. Oops.
18727 - Only pick and establish intro points after we've gotten a
18730 - AllowUnverifiedNodes config option to let circuits choose no-name
18731 routers in entry,middle,exit,introduction,rendezvous positions.
18732 Allow middle and rendezvous positions by default.
18733 - Add a man page for tor-resolve.
18736 Changes in version 0.0.7.3 - 2004-08-12
18737 o Stop dnsworkers from triggering an assert failure when you
18738 ask them to resolve the host "".
18741 Changes in version 0.0.8pre3 - 2004-08-09
18742 o Changes from 0.0.7.2:
18743 - Allow multiple ORs with same nickname in routerlist -- now when
18744 people give us one identity key for a nickname, then later
18745 another, we don't constantly complain until the first expires.
18746 - Remember used bandwidth (both in and out), and publish 15-minute
18747 snapshots for the past day into our descriptor.
18748 - You can now fetch $DIRURL/running-routers to get just the
18749 running-routers line, not the whole descriptor list. (But
18750 clients don't use this yet.)
18751 - When people mistakenly use Tor as an http proxy, point them
18752 at the tor-doc.html rather than the INSTALL.
18753 - Remove our mostly unused -- and broken -- hex_encode()
18754 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18755 for pointing out this bug.)
18756 - Rotate onion keys every 12 hours, not every 2 hours, so we have
18757 fewer problems with people using the wrong key.
18758 - Change the default exit policy to reject the default edonkey,
18759 kazaa, gnutella ports.
18760 - Add replace_file() to util.[ch] to handle win32's rename().
18762 o Changes from 0.0.8preX:
18763 - Fix two bugs in saving onion keys to disk when rotating, so
18764 hopefully we'll get fewer people using old onion keys.
18765 - Fix an assert error that was making SocksPolicy not work.
18766 - Be willing to expire routers that have an open dirport -- it's
18767 just the authoritative dirservers we want to not forget.
18768 - Reject tor-resolve requests for .onion addresses early, so we
18769 don't build a whole rendezvous circuit and then fail.
18770 - When you're warning a server that he's unverified, don't cry
18771 wolf unpredictably.
18772 - Fix a race condition: don't try to extend onto a connection
18773 that's still handshaking.
18774 - For servers in clique mode, require the conn to be open before
18775 you'll choose it for your path.
18776 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
18777 end relay cell, etc.
18778 - Measure bandwidth capacity over the last 24 hours, not just 12
18779 - Bugfix: authoritative dirservers were making and signing a new
18780 directory for each client, rather than reusing the cached one.
18783 Changes in version 0.0.8pre2 - 2004-08-04
18784 o Changes from 0.0.7.2:
18786 - Check directory signature _before_ you decide whether you're
18787 you're running an obsolete version and should exit.
18788 - Check directory signature _before_ you parse the running-routers
18789 list to decide who's running or verified.
18790 - Bugfixes and features:
18791 - Check return value of fclose while writing to disk, so we don't
18792 end up with broken files when servers run out of disk space.
18793 - Log a warning if the user uses an unsafe socks variant, so people
18794 are more likely to learn about privoxy or socat.
18795 - Dirservers now include RFC1123-style dates in the HTTP headers,
18796 which one day we will use to better detect clock skew.
18798 o Changes from 0.0.8pre1:
18799 - Make it compile without warnings again on win32.
18800 - Log a warning if you're running an unverified server, to let you
18801 know you might want to get it verified.
18802 - Only pick a default nickname if you plan to be a server.
18805 Changes in version 0.0.8pre1 - 2004-07-23
18807 - Made our unit tests compile again on OpenBSD 3.5, and tor
18808 itself compile again on OpenBSD on a sparc64.
18809 - We were neglecting milliseconds when logging on win32, so
18810 everything appeared to happen at the beginning of each second.
18812 o Protocol changes:
18813 - 'Extend' relay cell payloads now include the digest of the
18814 intended next hop's identity key. Now we can verify that we're
18815 extending to the right router, and also extend to routers we
18816 hadn't heard of before.
18819 - Tor nodes can now act as relays (with an advertised ORPort)
18820 without being manually verified by the dirserver operators.
18821 - Uploaded descriptors of unverified routers are now accepted
18822 by the dirservers, and included in the directory.
18823 - Verified routers are listed by nickname in the running-routers
18824 list; unverified routers are listed as "$<fingerprint>".
18825 - We now use hash-of-identity-key in most places rather than
18826 nickname or addr:port, for improved security/flexibility.
18827 - To avoid Sybil attacks, paths still use only verified servers.
18828 But now we have a chance to play around with hybrid approaches.
18829 - Nodes track bandwidth usage to estimate capacity (not used yet).
18830 - ClientOnly option for nodes that never want to become servers.
18831 - Directory caching.
18832 - "AuthoritativeDir 1" option for the official dirservers.
18833 - Now other nodes (clients and servers) will cache the latest
18834 directory they've pulled down.
18835 - They can enable their DirPort to serve it to others.
18836 - Clients will pull down a directory from any node with an open
18837 DirPort, and check the signature/timestamp correctly.
18838 - Authoritative dirservers now fetch directories from other
18839 authdirservers, to stay better synced.
18840 - Running-routers list tells who's down also, along with noting
18841 if they're verified (listed by nickname) or unverified (listed
18843 - Allow dirservers to serve running-router list separately.
18844 This isn't used yet.
18845 - ORs connect-on-demand to other ORs
18846 - If you get an extend cell to an OR you're not connected to,
18847 connect, handshake, and forward the create cell.
18848 - The authoritative dirservers stay connected to everybody,
18849 and everybody stays connected to 0.0.7 servers, but otherwise
18850 clients/servers expire unused connections after 5 minutes.
18851 - When servers get a sigint, they delay 30 seconds (refusing new
18852 connections) then exit. A second sigint causes immediate exit.
18853 - File and name management:
18854 - Look for .torrc if no CONFDIR "torrc" is found.
18855 - If no datadir is defined, then choose, make, and secure ~/.tor
18857 - If torrc not found, exitpolicy reject *:*.
18858 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18859 - If no nickname is defined, derive default from hostname.
18860 - Rename secret key files, e.g. identity.key -> secret_id_key,
18861 to discourage people from mailing their identity key to tor-ops.
18862 - Refuse to build a circuit before the directory has arrived --
18863 it won't work anyway, since you won't know the right onion keys
18865 - Try other dirservers immediately if the one you try is down. This
18866 should tolerate down dirservers better now.
18867 - Parse tor version numbers so we can do an is-newer-than check
18868 rather than an is-in-the-list check.
18869 - New socks command 'resolve', to let us shim gethostbyname()
18871 - A 'tor_resolve' script to access the socks resolve functionality.
18872 - A new socks-extensions.txt doc file to describe our
18873 interpretation and extensions to the socks protocols.
18874 - Add a ContactInfo option, which gets published in descriptor.
18875 - Publish OR uptime in descriptor (and thus in directory) too.
18876 - Write tor version at the top of each log file
18877 - New docs in the tarball:
18879 - Document that you should proxy your SSL traffic too.
18882 Changes in version 0.0.7.2 - 2004-07-07
18883 o A better fix for the 0.0.0.0 problem, that will hopefully
18884 eliminate the remaining related assertion failures.
18887 Changes in version 0.0.7.1 - 2004-07-04
18888 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18889 since internally we use 0.0.0.0 to signify "not yet resolved".
18892 Changes in version 0.0.7 - 2004-06-07
18893 o Updated the man page to reflect the new features.
18896 Changes in version 0.0.7rc2 - 2004-06-06
18897 o Changes from 0.0.7rc1:
18898 - Make it build on Win32 again.
18899 o Changes from 0.0.6.2:
18900 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18904 Changes in version 0.0.7rc1 - 2004-06-02
18906 - On sighup, we were adding another log without removing the first
18907 one. So log messages would get duplicated n times for n sighups.
18908 - Several cases of using a connection after we'd freed it. The
18909 problem was that connections that are pending resolve are in both
18910 the pending_resolve tree, and also the circuit's resolving_streams
18911 list. When you want to remove one, you must remove it from both.
18912 - Fix a double-mark-for-close where an end cell arrived for a
18913 resolving stream, and then the resolve failed.
18914 - Check directory signatures based on name of signer, not on whom
18915 we got the directory from. This will let us cache directories more
18918 - Crank up some of our constants to handle more users.
18921 Changes in version 0.0.7pre1 - 2004-06-02
18922 o Fixes for crashes and other obnoxious bugs:
18923 - Fix an epipe bug: sometimes when directory connections failed
18924 to connect, we would give them a chance to flush before closing
18926 - When we detached from a circuit because of resolvefailed, we
18927 would immediately try the same circuit twice more, and then
18928 give up on the resolve thinking we'd tried three different
18930 - Limit the number of intro circuits we'll attempt to build for a
18931 hidden service per 15-minute period.
18932 - Check recommended-software string *early*, before actually parsing
18933 the directory. Thus we can detect an obsolete version and exit,
18934 even if the new directory format doesn't parse.
18935 o Fixes for security bugs:
18936 - Remember which nodes are dirservers when you startup, and if a
18937 random OR enables his dirport, don't automatically assume he's
18938 a trusted dirserver.
18940 - Directory connections were asking the wrong poll socket to
18941 start writing, and not asking themselves to start writing.
18942 - When we detached from a circuit because we sent a begin but
18943 didn't get a connected, we would use it again the first time;
18944 but after that we would correctly switch to a different one.
18945 - Stop warning when the first onion decrypt attempt fails; they
18946 will sometimes legitimately fail now that we rotate keys.
18947 - Override unaligned-access-ok check when $host_cpu is ia64 or
18948 arm. Apparently they allow it but the kernel whines.
18949 - Dirservers try to reconnect periodically too, in case connections
18951 - Fix some memory leaks in directory servers.
18952 - Allow backslash in Win32 filenames.
18953 - Made Tor build complain-free on FreeBSD, hopefully without
18954 breaking other BSD builds. We'll see.
18956 - Doxygen markup on all functions and global variables.
18957 - Make directory functions update routerlist, not replace it. So
18958 now directory disagreements are not so critical a problem.
18959 - Remove the upper limit on number of descriptors in a dirserver's
18960 directory (not that we were anywhere close).
18961 - Allow multiple logfiles at different severity ranges.
18962 - Allow *BindAddress to specify ":port" rather than setting *Port
18963 separately. Allow multiple instances of each BindAddress config
18964 option, so you can bind to multiple interfaces if you want.
18965 - Allow multiple exit policy lines, which are processed in order.
18966 Now we don't need that huge line with all the commas in it.
18967 - Enable accept/reject policies on SOCKS connections, so you can bind
18968 to 0.0.0.0 but still control who can use your OP.
18971 Changes in version 0.0.6.2 - 2004-05-16
18972 o Our integrity-checking digest was checking only the most recent cell,
18973 not the previous cells like we'd thought.
18974 Thanks to Stefan Mark for finding the flaw!
18977 Changes in version 0.0.6.1 - 2004-05-06
18978 o Fix two bugs in our AES counter-mode implementation (this affected
18979 onion-level stream encryption, but not TLS-level). It turns
18980 out we were doing something much more akin to a 16-character
18981 polyalphabetic cipher. Oops.
18982 Thanks to Stefan Mark for finding the flaw!
18983 o Retire moria3 as a directory server, and add tor26 as a directory
18987 Changes in version 0.0.6 - 2004-05-02
18988 [version bump only]
18991 Changes in version 0.0.6rc4 - 2004-05-01
18992 o Update the built-in dirservers list to use the new directory format
18993 o Fix a rare seg fault: if a node offering a hidden service attempts
18994 to build a circuit to Alice's rendezvous point and fails before it
18995 reaches the last hop, it retries with a different circuit, but
18997 o Handle windows socket errors correctly.
19000 Changes in version 0.0.6rc3 - 2004-04-28
19001 o Don't expire non-general excess circuits (if we had enough
19002 circuits open, we were expiring rendezvous circuits -- even
19003 when they had a stream attached. oops.)
19004 o Fetch randomness from /dev/urandom better (not via fopen/fread)
19005 o Better debugging for tls errors
19006 o Some versions of openssl have an SSL_pending function that erroneously
19007 returns bytes when there is a non-application record pending.
19008 o Set Content-Type on the directory and hidserv descriptor.
19009 o Remove IVs from cipher code, since AES-ctr has none.
19010 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
19011 o We were using an array of length zero in a few places.
19012 o win32's gethostbyname can't resolve an IP to an IP.
19013 o win32's close can't close a socket.
19016 Changes in version 0.0.6rc2 - 2004-04-26
19017 o Fix a bug where we were closing tls connections intermittently.
19018 It turns out openssl keeps its errors around -- so if an error
19019 happens, and you don't ask about it, and then another openssl
19020 operation happens and succeeds, and you ask if there was an error,
19021 it tells you about the first error. Fun fun.
19022 o Fix a bug that's been lurking since 27 may 03 (!)
19023 When passing back a destroy cell, we would use the wrong circ id.
19024 'Mostly harmless', but still worth fixing.
19025 o Since we don't support truncateds much, don't bother sending them;
19026 just close the circ.
19027 o check for <machine/limits.h> so we build on NetBSD again (I hope).
19028 o don't crash if a conn that sent a begin has suddenly lost its circuit
19029 (this was quite rare).
19032 Changes in version 0.0.6rc1 - 2004-04-25
19033 o We now rotate link (tls context) keys and onion keys.
19034 o CREATE cells now include oaep padding, so you can tell
19035 if you decrypted them correctly.
19036 o Add bandwidthburst to server descriptor.
19037 o Directories now say which dirserver signed them.
19038 o Use a tor_assert macro that logs failed assertions too.
19041 Changes in version 0.0.6pre5 - 2004-04-18
19042 o changes from 0.0.6pre4:
19043 - make tor build on broken freebsd 5.2 installs
19044 - fix a failed assert when you try an intro point, get a nack, and try
19045 a second one and it works.
19046 - when alice uses a port that the hidden service doesn't accept,
19047 it now sends back an end cell (denied by exit policy). otherwise
19048 alice would just have to wait to time out.
19049 - fix another rare bug: when we had tried all the intro
19050 points for a hidden service, we fetched the descriptor
19051 again, but we left our introcirc thinking it had already
19052 sent an intro, so it kept waiting for a response...
19053 - bugfix: when you sleep your hidden-service laptop, as soon
19054 as it wakes up it tries to upload a service descriptor, but
19055 socketpair fails for some reason (localhost not up yet?).
19056 now we simply give up on that upload, and we'll try again later.
19057 i'd still like to find the bug though.
19058 - if an intro circ waiting for an ack dies before getting one, then
19060 - we were reusing stale service descriptors and refetching usable
19064 Changes in version 0.0.6pre4 - 2004-04-14
19065 o changes from 0.0.6pre3:
19066 - when bob fails to connect to the rendezvous point, and his
19067 circ didn't fail because of the rendezvous point itself, then
19068 he retries a couple of times
19069 - we expire introduction and rendezvous circs more thoroughly
19070 (sometimes they were hanging around forever)
19071 - we expire unattached rendezvous streams that have been around
19072 too long (they were sticking around forever).
19073 - fix a measly fencepost error that was crashing everybody with
19077 Changes in version 0.0.6pre3 - 2004-04-14
19078 o changes from 0.0.6pre2:
19079 - make hup work again
19080 - fix some memory leaks for dirservers
19081 - allow more skew in rendezvous descriptor timestamps, to help
19082 handle people like blanu who don't know what time it is
19083 - normal circs are 3 hops, but some rend/intro circs are 4, if
19084 the initiator doesn't get to choose the last hop
19085 - send acks for introductions, so alice can know whether to try
19087 - bob publishes intro points more correctly
19088 o changes from 0.0.5:
19089 - fix an assert trigger that's been plaguing us since the days
19090 of 0.0.2prexx (thanks weasel!)
19091 - retry stream correctly when we fail to connect because of
19092 exit-policy-reject (should try another) or can't-resolve-address
19093 (also should try another, because dns on random internet servers
19095 - when we hup a dirserver and we've *removed* a server from the
19096 approved-routers list, now we remove that server from the
19097 in-memory directories too
19100 Changes in version 0.0.6pre2 - 2004-04-08
19101 o We fixed our base32 implementation. Now it works on all architectures.
19104 Changes in version 0.0.6pre1 - 2004-04-08
19106 - Hidden services and rendezvous points are implemented. Go to
19107 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
19108 hidden services. (This only works via a socks4a proxy such as
19109 Privoxy, and currently it's quite slow.)
19112 Changes in version 0.0.5 - 2004-03-30
19113 [version bump only]
19116 Changes in version 0.0.5rc3 - 2004-03-29
19117 o Install torrc as torrc.sample -- we no longer clobber your
19119 o Re-enable recommendedversion checking (we broke it in rc2, oops)
19120 o Add in a 'notice' log level for things the operator should hear
19121 but that aren't warnings
19124 Changes in version 0.0.5rc2 - 2004-03-29
19125 o Hold socks connection open until reply is flushed (if possible)
19126 o Make exit nodes resolve IPs to IPs immediately, rather than asking
19127 the dns farm to do it.
19128 o Fix c99 aliasing warnings in rephist.c
19129 o Don't include server descriptors that are older than 24 hours in the
19131 o Give socks 'reject' replies their whole 15s to attempt to flush,
19132 rather than seeing the 60s timeout and assuming the flush had failed.
19133 o Clean automake droppings from the cvs repository
19136 Changes in version 0.0.5rc1 - 2004-03-28
19137 o Fix mangled-state bug in directory fetching (was causing sigpipes).
19138 o Only build circuits after we've fetched the directory: clients were
19139 using only the directory servers before they'd fetched a directory.
19140 This also means longer startup time; so it goes.
19141 o Fix an assert trigger where an OP would fail to handshake, and we'd
19142 expect it to have a nickname.
19143 o Work around a tsocks bug: do a socks reject when AP connection dies
19144 early, else tsocks goes into an infinite loop.
19147 Changes in version 0.0.4 - 2004-03-26
19148 o When connecting to a dirserver or OR and the network is down,
19152 Changes in version 0.0.3 - 2004-03-26
19153 o Warn and fail if server chose a nickname with illegal characters
19154 o Port to Solaris and Sparc:
19155 - include missing header fcntl.h
19156 - have autoconf find -lsocket -lnsl automatically
19157 - deal with hardware word alignment
19158 - make uname() work (solaris has a different return convention)
19159 - switch from using signal() to sigaction()
19160 o Preliminary work on reputation system:
19161 - Keep statistics on success/fail of connect attempts; they're published
19162 by kill -USR1 currently.
19163 - Add a RunTesting option to try to learn link state by creating test
19164 circuits, even when SocksPort is off.
19165 - Remove unused open circuits when there are too many.
19168 Changes in version 0.0.2 - 2004-03-19
19169 - Include strlcpy and strlcat for safer string ops
19170 - define INADDR_NONE so we compile (but still not run) on solaris
19173 Changes in version 0.0.2pre27 - 2004-03-14
19175 - Allow internal tor networks (we were rejecting internal IPs,
19176 now we allow them if they're set explicitly).
19177 - And fix a few endian issues.
19180 Changes in version 0.0.2pre26 - 2004-03-14
19182 - If a stream times out after 15s without a connected cell, don't
19183 try that circuit again: try a new one.
19184 - Retry streams at most 4 times. Then give up.
19185 - When a dirserver gets a descriptor from an unknown router, it
19186 logs its fingerprint (so the dirserver operator can choose to
19187 accept it even without mail from the server operator).
19188 - Inform unapproved servers when we reject their descriptors.
19189 - Make tor build on Windows again. It works as a client, who knows
19191 - Clearer instructions in the torrc for how to set up a server.
19192 - Be more efficient about reading fd's when our global token bucket
19193 (used for rate limiting) becomes empty.
19195 - Stop asserting that computers always go forward in time. It's
19197 - When we sent a cell (e.g. destroy) and then marked an OR connection
19198 expired, we might close it before finishing a flush if the other
19199 side isn't reading right then.
19200 - Don't allow dirservers to start if they haven't defined
19201 RecommendedVersions
19202 - We were caching transient dns failures. Oops.
19203 - Prevent servers from publishing an internal IP as their address.
19204 - Address a strcat vulnerability in circuit.c
19207 Changes in version 0.0.2pre25 - 2004-03-04
19209 - Put the OR's IP in its router descriptor, not its fqdn. That way
19210 we'll stop being stalled by gethostbyname for nodes with flaky dns,
19213 - If the user typed in an address that didn't resolve, the server
19217 Changes in version 0.0.2pre24 - 2004-03-03
19219 - Fix an assertion failure in dns.c, where we were trying to dequeue
19220 a pending dns resolve even if it wasn't pending
19221 - Fix a spurious socks5 warning about still trying to write after the
19222 connection is finished.
19223 - Hold certain marked_for_close connections open until they're finished
19224 flushing, rather than losing bytes by closing them too early.
19225 - Correctly report the reason for ending a stream
19226 - Remove some duplicate calls to connection_mark_for_close
19227 - Put switch_id and start_daemon earlier in the boot sequence, so it
19228 will actually try to chdir() to options.DataDirectory
19229 - Make 'make test' exit(1) if a test fails; fix some unit tests
19230 - Make tor fail when you use a config option it doesn't know about,
19231 rather than warn and continue.
19232 - Make --version work
19233 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
19236 Changes in version 0.0.2pre23 - 2004-02-29
19238 - Print a statement when the first circ is finished, so the user
19239 knows it's working.
19240 - If a relay cell is unrecognized at the end of the circuit,
19241 send back a destroy. (So attacks to mutate cells are more
19243 - New config option 'excludenodes' to avoid certain nodes for circuits.
19244 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
19245 so you can collect coredumps there.
19247 - Fix a bug in tls flushing where sometimes data got wedged and
19248 didn't flush until more data got sent. Hopefully this bug was
19249 a big factor in the random delays we were seeing.
19250 - Make 'connected' cells include the resolved IP, so the client
19251 dns cache actually gets populated.
19252 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19253 - When we time-out on a stream and detach from the circuit, send an
19254 end cell down it first.
19255 - Only warn about an unknown router (in exitnodes, entrynodes,
19256 excludenodes) after we've fetched a directory.
19259 Changes in version 0.0.2pre22 - 2004-02-26
19261 - Servers publish less revealing uname information in descriptors.
19262 - More memory tracking and assertions, to crash more usefully when
19264 - If the default torrc isn't there, just use some default defaults.
19265 Plus provide an internal dirservers file if they don't have one.
19266 - When the user tries to use Tor as an http proxy, give them an http
19267 501 failure explaining that we're a socks proxy.
19268 - Dump a new router.desc on hup, to help confused people who change
19269 their exit policies and then wonder why router.desc doesn't reflect
19271 - Clean up the generic tor.sh init script that we ship with.
19273 - If the exit stream is pending on the resolve, and a destroy arrives,
19274 then the stream wasn't getting removed from the pending list. I
19275 think this was the one causing recent server crashes.
19276 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19277 - When it couldn't resolve any dirservers, it was useless from then on.
19278 Now it reloads the RouterFile (or default dirservers) if it has no
19280 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19281 many users don't even *have* a /usr/local/sbin/.
19284 Changes in version 0.0.2pre21 - 2004-02-18
19286 - There's a ChangeLog file that actually reflects the changelog.
19287 - There's a 'torify' wrapper script, with an accompanying
19288 tor-tsocks.conf, that simplifies the process of using tsocks for
19289 tor. It even has a man page.
19290 - The tor binary gets installed to sbin rather than bin now.
19291 - Retry streams where the connected cell hasn't arrived in 15 seconds
19292 - Clean up exit policy handling -- get the default out of the torrc,
19293 so we can update it without forcing each server operator to fix
19295 - Allow imaps and pop3s in default exit policy
19297 - Prevent picking middleman nodes as the last node in the circuit
19300 Changes in version 0.0.2pre20 - 2004-01-30
19302 - We now have a deb package, and it's in debian unstable. Go to
19303 it, apt-getters. :)
19304 - I've split the TotalBandwidth option into BandwidthRate (how many
19305 bytes per second you want to allow, long-term) and
19306 BandwidthBurst (how many bytes you will allow at once before the cap
19307 kicks in). This better token bucket approach lets you, say, set
19308 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19309 performance while not exceeding your monthly bandwidth quota.
19310 - Push out a tls record's worth of data once you've got it, rather
19311 than waiting until you've read everything waiting to be read. This
19312 may improve performance by pipelining better. We'll see.
19313 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19314 from failed circuits (if they haven't been connected yet) and attach
19316 - Expire old streams that haven't managed to connect. Some day we'll
19317 have them reattach to new circuits instead.
19320 - Fix several memory leaks that were causing servers to become bloated
19322 - Fix a few very rare assert triggers. A few more remain.
19323 - Setuid to User _before_ complaining about running as root.
19326 Changes in version 0.0.2pre19 - 2004-01-07
19328 - Fix deadlock condition in dns farm. We were telling a child to die by
19329 closing the parent's file descriptor to him. But newer children were
19330 inheriting the open file descriptor from the parent, and since they
19331 weren't closing it, the socket never closed, so the child never read
19332 eof, so he never knew to exit. Similarly, dns workers were holding
19333 open other sockets, leading to all sorts of chaos.
19334 - New cleaner daemon() code for forking and backgrounding.
19335 - If you log to a file, it now prints an entry at the top of the
19336 logfile so you know it's working.
19337 - The onionskin challenge length was 30 bytes longer than necessary.
19338 - Started to patch up the spec so it's not quite so out of date.
19341 Changes in version 0.0.2pre18 - 2004-01-02
19343 - Fix endian issues with the 'integrity' field in the relay header.
19344 - Fix a potential bug where connections in state
19345 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19348 Changes in version 0.0.2pre17 - 2003-12-30
19350 - Made --debuglogfile (or any second log file, actually) work.
19351 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19352 adversary could force us into an infinite loop.
19355 - Each onionskin handshake now includes a hash of the computed key,
19356 to prove the server's identity and help perfect forward secrecy.
19357 - Changed cell size from 256 to 512 bytes (working toward compatibility
19359 - Changed cell length to 2 bytes, and moved it to the relay header.
19360 - Implemented end-to-end integrity checking for the payloads of
19362 - Separated streamid from 'recognized' (otherwise circuits will get
19363 messed up when we try to have streams exit from the middle). We
19364 use the integrity-checking to confirm that a cell is addressed to
19366 - Randomize the initial circid and streamid values, so an adversary who
19367 breaks into a node can't learn how many circuits or streams have
19371 Changes in version 0.0.2pre16 - 2003-12-14
19373 - Fixed a bug that made HUP trigger an assert
19374 - Fixed a bug where a circuit that immediately failed wasn't being
19375 counted as a failed circuit in counting retries.
19378 - Now we close the circuit when we get a truncated cell: otherwise we're
19379 open to an anonymity attack where a bad node in the path truncates
19380 the circuit and then we open streams at him.
19381 - Add port ranges to exit policies
19382 - Add a conservative default exit policy
19383 - Warn if you're running tor as root
19384 - on HUP, retry OR connections and close/rebind listeners
19385 - options.EntryNodes: try these nodes first when picking the first node
19386 - options.ExitNodes: if your best choices happen to include any of
19387 your preferred exit nodes, you choose among just those preferred
19389 - options.ExcludedNodes: nodes that are never picked in path building
19392 Changes in version 0.0.2pre15 - 2003-12-03
19393 o Robustness and bugfixes:
19394 - Sometimes clients would cache incorrect DNS resolves, which would
19395 really screw things up.
19396 - An OP that goes offline would slowly leak all its sockets and stop
19398 - A wide variety of bugfixes in exit node selection, exit policy
19399 handling, and processing pending streams when a new circuit is
19401 - Pick nodes for a path only from those the directory says are up
19402 - Choose randomly from all running dirservers, not always the first one
19403 - Increase allowed http header size for directory fetch.
19404 - Stop writing to stderr (if we're daemonized it will be closed).
19405 - Enable -g always, so cores will be more useful to me.
19406 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19409 - Wrote a man page. It lists commonly used options.
19412 - Change default loglevel to warn.
19413 - Make PidFile default to null rather than littering in your CWD.
19414 - OnionRouter config option is now obsolete. Instead it just checks
19416 - Moved to a single unified torrc file for both clients and servers.
19419 Changes in version 0.0.2pre14 - 2003-11-29
19420 o Robustness and bugfixes:
19421 - Force the admin to make the DataDirectory himself
19422 - to get ownership/permissions right
19423 - so clients no longer make a DataDirectory and then never use it
19424 - fix bug where a client who was offline for 45 minutes would never
19425 pull down a directory again
19426 - fix (or at least hide really well) the dns assert bug that was
19427 causing server crashes
19428 - warnings and improved robustness wrt clockskew for certs
19429 - use the native daemon(3) to daemonize, when available
19430 - exit if bind() fails
19431 - exit if neither socksport nor orport is defined
19432 - include our own tor_timegm (Win32 doesn't have its own)
19433 - bugfix for win32 with lots of connections
19434 - fix minor bias in PRNG
19435 - make dirserver more robust to corrupt cached directory
19438 - Wrote the design document (woo)
19440 o Circuit building and exit policies:
19441 - Circuits no longer try to use nodes that the directory has told them
19443 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19444 bitcounts (18.0.0.0/8).
19445 - Make AP connections standby for a circuit if no suitable circuit
19446 exists, rather than failing
19447 - Circuits choose exit node based on addr/port, exit policies, and
19448 which AP connections are standing by
19449 - Bump min pathlen from 2 to 3
19450 - Relay end cells have a payload to describe why the stream ended.
19451 - If the stream failed because of exit policy, try again with a new
19453 - Clients have a dns cache to remember resolved addresses.
19454 - Notice more quickly when we have no working circuits
19457 - APPort is now called SocksPort
19458 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19460 - RecommendedVersions is now a config variable rather than
19461 hardcoded (for dirservers)
19462 - Reloads config on HUP
19463 - Usage info on -h or --help
19464 - If you set User and Group config vars, it'll setu/gid to them.
19467 Changes in version 0.0.2pre13 - 2003-10-19
19468 o General stability:
19469 - SSL_write no longer fails when it returns WANTWRITE and the number
19470 of bytes in the buf has changed by the next SSL_write call.
19471 - Fix segfault fetching directory when network is down
19472 - Fix a variety of minor memory leaks
19473 - Dirservers reload the fingerprints file on HUP, so I don't have
19474 to take down the network when I approve a new router
19475 - Default server config file has explicit Address line to specify fqdn
19478 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19479 - Make listener connections not ever alloc bufs
19481 o Autoconf improvements:
19482 - don't clobber an external CFLAGS in ./configure
19483 - Make install now works
19484 - create var/lib/tor on make install
19485 - autocreate a tor.sh initscript to help distribs
19486 - autocreate the torrc and sample-server-torrc with correct paths
19488 o Log files and Daemonizing now work:
19489 - If --DebugLogFile is specified, log to it at -l debug
19490 - If --LogFile is specified, use it instead of commandline
19491 - If --RunAsDaemon is set, tor forks and backgrounds on startup